Bug#956036: RM: mpich -- ROM; Bad soversion, blocking a transition
On 4/6/20 4:47 PM, Alastair McKinstry wrote: > On 06/04/2020 14:54, Adam D. Barratt wrote: >> On Mon, 2020-04-06 at 15:23 +0200, Sebastiaan Couwenberg wrote: >>> On 4/6/20 3:05 PM, Alastair McKinstry wrote: Package: ftp.debian.org Severity: normal mpich-3.4a4-2 has a problem due to a silent SOVERSION change in upstream; (SOVERSION set to 0). It must not progress to testing. A new release will be done based on the previous upstream release (ie 3.3.2-3 will be uploaded when 3.4~a2-2 is removed). >>> Why are asking the ftp team to remove the package entirely? >> It also won't help, as the version in the archive can't go backwards >> (modulo epochs etc) and some people will already have the broken >> version installed. >> >> You want a fixed upload with either epoch or +really ASAP, and possibly >> an RC bug in the meantime. > > Thanks, I've uploaded a +really version. Then you should close this RM bug to prevent it from inadvertently being removed from unstable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#956036: RM: mpich -- ROM; Bad soversion, blocking a transition
On 06/04/2020 14:54, Adam D. Barratt wrote: > On Mon, 2020-04-06 at 15:23 +0200, Sebastiaan Couwenberg wrote: >> On 4/6/20 3:05 PM, Alastair McKinstry wrote: >>> Package: ftp.debian.org >>> Severity: normal >>> >>> mpich-3.4a4-2 has a problem due to a silent SOVERSION change in >>> upstream; >>> (SOVERSION set to 0). It must not progress to testing. >>> A new release will be done based on the previous upstream release >>> (ie 3.3.2-3 will be uploaded when 3.4~a2-2 is removed). >> Why are asking the ftp team to remove the package entirely? > It also won't help, as the version in the archive can't go backwards > (modulo epochs etc) and some people will already have the broken > version installed. > > You want a fixed upload with either epoch or +really ASAP, and possibly > an RC bug in the meantime. Thanks, I've uploaded a +really version. Alastair > Regards, > > Adam > -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered.
Bug#956036: RM: mpich -- ROM; Bad soversion, blocking a transition
On Mon, 2020-04-06 at 15:23 +0200, Sebastiaan Couwenberg wrote: > On 4/6/20 3:05 PM, Alastair McKinstry wrote: > > Package: ftp.debian.org > > Severity: normal > > > > mpich-3.4a4-2 has a problem due to a silent SOVERSION change in > > upstream; > > (SOVERSION set to 0). It must not progress to testing. > > A new release will be done based on the previous upstream release > > (ie 3.3.2-3 will be uploaded when 3.4~a2-2 is removed). > > Why are asking the ftp team to remove the package entirely? It also won't help, as the version in the archive can't go backwards (modulo epochs etc) and some people will already have the broken version installed. You want a fixed upload with either epoch or +really ASAP, and possibly an RC bug in the meantime. Regards, Adam
Bug#956036: RM: mpich -- ROM; Bad soversion, blocking a transition
On 4/6/20 3:05 PM, Alastair McKinstry wrote: > Package: ftp.debian.org > Severity: normal > > mpich-3.4a4-2 has a problem due to a silent SOVERSION change in upstream; > (SOVERSION set to 0). It must not progress to testing. > A new release will be done based on the previous upstream release > (ie 3.3.2-3 will be uploaded when 3.4~a2-2 is removed). Why are asking the ftp team to remove the package entirely? To revert the package in unstable to 3.3.2 you should upload a +really revision: https://www.debian.org/doc/debian-policy/ch-controlfields.html#epochs-should-be-used-sparingly Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#956036: RM: mpich -- ROM; Bad soversion, blocking a transition
Package: ftp.debian.org Severity: normal mpich-3.4a4-2 has a problem due to a silent SOVERSION change in upstream; (SOVERSION set to 0). It must not progress to testing. A new release will be done based on the previous upstream release (ie 3.3.2-3 will be uploaded when 3.4~a2-2 is removed). Regards Alastair McKinstry
