Bug#948552: nmu: schroedinger-coordgenlibs_1.3-1
Control: severity -1 serious Control: reassign -1 libschroedinger-maeparser1 1.2.2-1 Control: retitle -1 libschroedinger-maeparser1: SONAME change without package name change On Fri, Jan 10, 2020 at 08:41:47PM +1100, Stuart Prescott wrote: > Hi Julien, > > On Friday, 10 January 2020 19:44:37 AEDT Julien Cristau wrote: > > On Fri, Jan 10, 2020 at 03:57:01PM +1100, Stuart Prescott wrote: > > > Package: release.debian.org > > > Severity: normal > > > User: release.debian@packages.debian.org > > > Usertags: binnmu > > > > > > nmu schroedinger-coordgenlibs_1.3-1 . ANY . unstable . -m "Rebuild against > > > libschroedinger-maeparser-dev >= 1.2.2-1" > > > > > > The binNMU of rdkit (#946247) did not fix #945985; it appears that it is > > > schroedinger-coordgenlibs that actually needs rebuilding to pick up the > > > new > > > filename of libmaeparser: > > > > > > $ ldd /usr/lib/x86_64-linux-gnu/libcoordgen.so.1.3 > > > > > > linux-vdso.so.1 (0x7fff9f9bd000) > > > libmaeparser.so.1.2 => not found > > > libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 > > > (0x7f5445999000) > > > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f5445854000) > > > libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > > > (0x7f544583a000) > > > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f544567a000) > > > /lib64/ld-linux-x86-64.so.2 (0x7f5445c12000) > > > > > > (rebuilding the package has the linking pick up libmaeparser.so.1 instead) > > > > That sounds wrong. If libmaeparser.so.1.2 was renamed to > > libmaeparser.so.1 then its package name should have changed? > > Yes, I'd say so. I'm guessing that libschroedinger-maeparser1 was the wrong > name to begin with or more likely that the "1.2" suffix was incorrect and > then > fixed; they are right(ish) now for that soname; I assume this was an > accidental > transition. > > Since there is only source package with a dependency on libschroedinger- > maeparser1 (this one), a binNMU seems like the simplest solution; it fixes > the > current packages and then lets me get on to the RC bugs I was actually trying > to fix... > Yeah, no, let's fix this properly in schroedinger-maeparser. Cheers, Julien
Processed: Re: Bug#948552: nmu: schroedinger-coordgenlibs_1.3-1
Processing control commands: > severity -1 serious Bug #948552 [release.debian.org] nmu: schroedinger-coordgenlibs_1.3-1 Severity set to 'serious' from 'normal' > reassign -1 libschroedinger-maeparser1 1.2.2-1 Bug #948552 [release.debian.org] nmu: schroedinger-coordgenlibs_1.3-1 Bug reassigned from package 'release.debian.org' to 'libschroedinger-maeparser1'. Ignoring request to alter found versions of bug #948552 to the same values previously set Ignoring request to alter fixed versions of bug #948552 to the same values previously set Bug #948552 [libschroedinger-maeparser1] nmu: schroedinger-coordgenlibs_1.3-1 Marked as found in versions schroedinger-maeparser/1.2.2-1. > retitle -1 libschroedinger-maeparser1: SONAME change without package name > change Bug #948552 [libschroedinger-maeparser1] nmu: schroedinger-coordgenlibs_1.3-1 Changed Bug title to 'libschroedinger-maeparser1: SONAME change without package name change' from 'nmu: schroedinger-coordgenlibs_1.3-1'. -- 948552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948552: nmu: schroedinger-coordgenlibs_1.3-1
Hi Julien, On Friday, 10 January 2020 19:44:37 AEDT Julien Cristau wrote: > On Fri, Jan 10, 2020 at 03:57:01PM +1100, Stuart Prescott wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: binnmu > > > > nmu schroedinger-coordgenlibs_1.3-1 . ANY . unstable . -m "Rebuild against > > libschroedinger-maeparser-dev >= 1.2.2-1" > > > > The binNMU of rdkit (#946247) did not fix #945985; it appears that it is > > schroedinger-coordgenlibs that actually needs rebuilding to pick up the > > new > > filename of libmaeparser: > > > > $ ldd /usr/lib/x86_64-linux-gnu/libcoordgen.so.1.3 > > > > linux-vdso.so.1 (0x7fff9f9bd000) > > libmaeparser.so.1.2 => not found > > libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 > > (0x7f5445999000) > > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f5445854000) > > libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > > (0x7f544583a000) > > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f544567a000) > > /lib64/ld-linux-x86-64.so.2 (0x7f5445c12000) > > > > (rebuilding the package has the linking pick up libmaeparser.so.1 instead) > > That sounds wrong. If libmaeparser.so.1.2 was renamed to > libmaeparser.so.1 then its package name should have changed? Yes, I'd say so. I'm guessing that libschroedinger-maeparser1 was the wrong name to begin with or more likely that the "1.2" suffix was incorrect and then fixed; they are right(ish) now for that soname; I assume this was an accidental transition. Since there is only source package with a dependency on libschroedinger- maeparser1 (this one), a binNMU seems like the simplest solution; it fixes the current packages and then lets me get on to the RC bugs I was actually trying to fix... cheers Stuart (who is just trying to fix Python 2 packages, not package libmaeparser) -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#948552: nmu: schroedinger-coordgenlibs_1.3-1
On Fri, Jan 10, 2020 at 03:57:01PM +1100, Stuart Prescott wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu schroedinger-coordgenlibs_1.3-1 . ANY . unstable . -m "Rebuild against > libschroedinger-maeparser-dev >= 1.2.2-1" > > The binNMU of rdkit (#946247) did not fix #945985; it appears that it is > schroedinger-coordgenlibs that actually needs rebuilding to pick up the new > filename of libmaeparser: > > $ ldd /usr/lib/x86_64-linux-gnu/libcoordgen.so.1.3 > linux-vdso.so.1 (0x7fff9f9bd000) > libmaeparser.so.1.2 => not found > libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 > (0x7f5445999000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f5445854000) > libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > (0x7f544583a000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f544567a000) > /lib64/ld-linux-x86-64.so.2 (0x7f5445c12000) > > (rebuilding the package has the linking pick up libmaeparser.so.1 instead) > That sounds wrong. If libmaeparser.so.1.2 was renamed to libmaeparser.so.1 then its package name should have changed? Cheers, Julien
Bug#948552: nmu: schroedinger-coordgenlibs_1.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu schroedinger-coordgenlibs_1.3-1 . ANY . unstable . -m "Rebuild against libschroedinger-maeparser-dev >= 1.2.2-1" The binNMU of rdkit (#946247) did not fix #945985; it appears that it is schroedinger-coordgenlibs that actually needs rebuilding to pick up the new filename of libmaeparser: $ ldd /usr/lib/x86_64-linux-gnu/libcoordgen.so.1.3 linux-vdso.so.1 (0x7fff9f9bd000) libmaeparser.so.1.2 => not found libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f5445999000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f5445854000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f544583a000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f544567a000) /lib64/ld-linux-x86-64.so.2 (0x7f5445c12000) (rebuilding the package has the linking pick up libmaeparser.so.1 instead) thanks Stuart
