| Summary: | net-irc/inspircd-3.4.0 stabilisation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andreas Sturmlechner <asturm> |
| Component: | Stabilization | Assignee: | Wade Cline <wadecline> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | proxy-maint |
| Priority: | Normal | Keywords: | STABLEREQ |
| Version: | unspecified | Flags: | stable-bot:
sanity-check+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: |
net-irc/inspircd-3.4.0
|
Runtime testing required: | --- |
|
Description
Andreas Sturmlechner
2019-06-27 16:59:25 UTC
Please note that 2.0.27 is currently the LTS version and 3.1.0 is the new, shiny, version,so it'd probably be best to stabilize both. Do you need me to do anything in particular here? I can confirm that both build on amd64. both doesn't make much sense imo, as soon as you stabilise 3.1.0, the reality is that 2.0.x will be skipped by everyone except a minority. Even 2.0.27 got only minor ~arch testing by the time 3.1.0 was added to tree. Arches please stabilise. An automated check of this bug failed - the following atom is unknown: net-irc/inspircd-3.1.0 Please verify the atom list. Waiting a few days for 3.2.0 then... amd64 stable 3.4.0 is merged and should fix a bug in the 'x86' architecture that prevented stabilization. How about stabilizing 3.4.0 now and then dropping 3.2.0? Restarting stabilization using newer version based on comment #7 x86 stable amd64 stable. Closing. Thank you! |