Processed: Re: Bug#858670: nmu: wxpython3.0_3.0.2.0+dfsg-3
Processing control commands: > tags -1 - moreinfo Bug #858670 [release.debian.org] nmu: wxpython3.0_3.0.2.0+dfsg-3 Removed tag(s) moreinfo. -- 858670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858670: nmu: wxpython3.0_3.0.2.0+dfsg-3
Control: tags -1 - moreinfo On Sat, 2017-03-25 at 11:39 -0400, Scott Talbert wrote: > On Sat, 25 Mar 2017, Adam D. Barratt wrote: > > >> wxwidgets3.0 was recently binNMU'd in stretch. wxpython3.0 needs to be > >> rebuilt to avoid a C++ ABI mismatch warning when all wxPython > >> applications are used. > > > > It was binNMUed _in unstable_, a month ago. If there's an issue, why > > wasn't it noticed earlier? > > I wasn't aware of the fact that wxWidgets was binNMUed until someone > reported a problem, as there isn't any sort of notification. In fact, I > can't even find a bug report that requested one. It's part of the process that starts being discussed at https://lists.debian.org/msgid-search/7507c8e4-870f-d67b-9284-fa4a5908e...@balintreczey.hu > > More specifically, I can only see one binNMU for wxpython3.0 having been > > performed in the past, in 2015. If the packages are so tightly coupled, > > shouldn't there have been far more frequent rebuilds in the past? (and > > how did the combination of wxwidgets3.0 uploaded on 2016-07-29 and > > wxpython3.0 uploaded on 2016-07-19 work?) > > The coupling is really only related to C++ ABI changes. As long as the > C++ ABI hasn't change, there isn't any problem. Ah, ok. So timing related. > >> nmu wxpython3.0_3.0.2.0+dfsg-3 . ANY . stretch . -m "Rebuild due to > >> wxWidgets C++ ABI change" > > > > That won't work, in any case - unstable and testing have the same binary > > version of the packages, so the binNMUs would have to be performed in > > unstable and then migrate (as testing can't have a higher version of the > > package than unstable). > > My bad, I'm relatively unfamiliar with the binNMU process. So it should > be: > > nmu wxpython3.0_3.0.2.0+dfsg-3 . ANY . unstable . -m "Rebuild due to > wxWidgets C++ ABI change" Yes, although the suite name can be omitted in this case. (The constraint isn't specific to binNMUs, fwiw - no package can have a higher version in testing than in unstable.) Scheduled: adsb@wuiet:~$ wb nmu wxpython3.0 . ANY . -m "Rebuild with gcc 6.3 to match wxwidgets3.0's C++ ABI" W: package wxpython3.0 is not installed on powerpcspe, can't binNMU. adsb@wuiet:~$ (powerpcspe is a ports architecture, so that warning isn't an issue for stretch.) > Does it then automatically migrate to testing, or does an unblock have to > be filed? binNMUs are automatically candidates for migration and don't need unblocking; successful migration still assumes that they don't end up with any dependency or installability issues. Regards, Adam
Bug#858670: nmu: wxpython3.0_3.0.2.0+dfsg-3
On Sat, 25 Mar 2017, Adam D. Barratt wrote: wxwidgets3.0 was recently binNMU'd in stretch. wxpython3.0 needs to be rebuilt to avoid a C++ ABI mismatch warning when all wxPython applications are used. It was binNMUed _in unstable_, a month ago. If there's an issue, why wasn't it noticed earlier? I wasn't aware of the fact that wxWidgets was binNMUed until someone reported a problem, as there isn't any sort of notification. In fact, I can't even find a bug report that requested one. More specifically, I can only see one binNMU for wxpython3.0 having been performed in the past, in 2015. If the packages are so tightly coupled, shouldn't there have been far more frequent rebuilds in the past? (and how did the combination of wxwidgets3.0 uploaded on 2016-07-29 and wxpython3.0 uploaded on 2016-07-19 work?) The coupling is really only related to C++ ABI changes. As long as the C++ ABI hasn't change, there isn't any problem. nmu wxpython3.0_3.0.2.0+dfsg-3 . ANY . stretch . -m "Rebuild due to wxWidgets C++ ABI change" That won't work, in any case - unstable and testing have the same binary version of the packages, so the binNMUs would have to be performed in unstable and then migrate (as testing can't have a higher version of the package than unstable). My bad, I'm relatively unfamiliar with the binNMU process. So it should be: nmu wxpython3.0_3.0.2.0+dfsg-3 . ANY . unstable . -m "Rebuild due to wxWidgets C++ ABI change" Does it then automatically migrate to testing, or does an unblock have to be filed?
Bug#858670: nmu: wxpython3.0_3.0.2.0+dfsg-3
Control: tags -1 + moreinfo On Fri, 2017-03-24 at 20:34 -0400, Scott Talbert wrote: > wxwidgets3.0 was recently binNMU'd in stretch. wxpython3.0 needs to be > rebuilt to avoid a C++ ABI mismatch warning when all wxPython > applications are used. It was binNMUed _in unstable_, a month ago. If there's an issue, why wasn't it noticed earlier? More specifically, I can only see one binNMU for wxpython3.0 having been performed in the past, in 2015. If the packages are so tightly coupled, shouldn't there have been far more frequent rebuilds in the past? (and how did the combination of wxwidgets3.0 uploaded on 2016-07-29 and wxpython3.0 uploaded on 2016-07-19 work?) > nmu wxpython3.0_3.0.2.0+dfsg-3 . ANY . stretch . -m "Rebuild due to wxWidgets > C++ ABI change" That won't work, in any case - unstable and testing have the same binary version of the packages, so the binNMUs would have to be performed in unstable and then migrate (as testing can't have a higher version of the package than unstable). Regards, Adam
Processed: Re: Bug#858670: nmu: wxpython3.0_3.0.2.0+dfsg-3
Processing control commands: > tags -1 + moreinfo Bug #858670 [release.debian.org] nmu: wxpython3.0_3.0.2.0+dfsg-3 Added tag(s) moreinfo. -- 858670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858670: nmu: wxpython3.0_3.0.2.0+dfsg-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi, wxwidgets3.0 was recently binNMU'd in stretch. wxpython3.0 needs to be rebuilt to avoid a C++ ABI mismatch warning when all wxPython applications are used. nmu wxpython3.0_3.0.2.0+dfsg-3 . ANY . stretch . -m "Rebuild due to wxWidgets C++ ABI change" -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
