Help with resolving an issue with wxwidgets3.2
Hi Release Team, In order to resolve an issue with wxWidgets 3.2 and packages that use wxWidgets OpenGL support (wxGLCanvas), I need to rebuild wxWidgets with GLX support instead of EGL support, as unfortunately, most of the companion OpenGL packages (e.g., glew, pyglet) are not ready for EGL support (for example, hugin uses wxWidgets[EGL] and glew[GLX] for its OpenGL support -> which currently fails, see bug #1020640). Unfortunately, rebuilding wxWidgets with GLX instead of EGL support results in an ABI change for the libwx_gtk3u_gl library. Thus, I can see two ways to resolve this: 1) Rebuild wxWidgets and then binNMU all packages that link with libwx_gtk3u_gl library (about a dozen packages). 2) Rebuild wxWidgets with soname bump and then rebuild all packages that use wx (about 67 packages). What do you think is the best way to proceed? Thanks, Scott
Bug#1024184: transition: alkimia
On Tue, Nov 15, 2022 at 10:09:46PM +0100, Hefee wrote: >... > The new version of alkimia depends on serveral new libriaries, it is > hard to say if the new version will compile on all archs as before. It > seems like the last Qt transition is still challangeing some buildds. So > we may loose some archs with this transtion. It built on all release architectures, which should be all that matters for the release team. > hefee >... cu Adrian
Bug#1024178: marked as done (RM: pypy-stem/1.8.0-3.1)
Your message dated Tue, 15 Nov 2022 22:56:27 +0100 with message-id and subject line Re: Bug#1024178: RM: pypy-stem/1.8.0-3.1 has caused the Debian Bug report #1024178, regarding RM: pypy-stem/1.8.0-3.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm X-Debbugs-Cc: he...@debian.org, pkg-privacy-maintain...@alioth-lists.debian.net The pypy-stem package is broken, as pypy is a Python 2 interpreter and stem code is written for Pythno 3 only. Additionally Pypy is marked for removal #1011926. The new python-stem version 1.8.1-1.1 is not building pypy-stem anymore. So the removal of pypy-stem in testing would enable the migration of python-stem and would untangle it from pypy removal. And would finally help the new onionshare version to migrate to testing, as it depends on the new version of python3-stem. hefee --- End Message --- --- Begin Message --- On 2022-11-15 23:43:37 +0200, Adrian Bunk wrote: > On Tue, Nov 15, 2022 at 10:25:21PM +0100, Sebastian Ramacher wrote: > > Control: tags -1 moreinfo > > > > Hi Hefee > > > > On 2022-11-15 21:53:23 +0100, Hefee wrote: > > > Package: release.debian.org > > > Severity: normal > > > User: release.debian@packages.debian.org > > > Usertags: rm > > > X-Debbugs-Cc: he...@debian.org, > > > pkg-privacy-maintain...@alioth-lists.debian.net > > > > > > The pypy-stem package is broken, as pypy is a Python 2 interpreter and > > > stem code is written for Pythno 3 only. Additionally Pypy is marked for > > > removal #1011926. The new python-stem version 1.8.1-1.1 is not building > > > pypy-stem > > > anymore. So the removal of pypy-stem in testing would enable the > > > migration of python-stem and would untangle it from pypy removal. > > > > > > And would finally help the new onionshare version to migrate to > > > testing, as it depends on the new version of python3-stem. > > > > Migration of python-step is currently blocked as removal of pypy-stem > > would render vanguards uninstallable. So what's the plan regarding > > vanguards? > > vanguards is already on the autoremoval list due to pypy > (and might even get removed before stem through python-setuptools). > > Making #932820 RC might be a good idea? Done > IMHO just waiting until autoremovals sort everything out > might then be good enough? Or let's just remove it now. It does not look like it has an active maintainer anyway. Cheers -- Sebastian Ramacher--- End Message ---
Bug#1024178: RM: pypy-stem/1.8.0-3.1
On Tue, Nov 15, 2022 at 10:25:21PM +0100, Sebastian Ramacher wrote: > Control: tags -1 moreinfo > > Hi Hefee > > On 2022-11-15 21:53:23 +0100, Hefee wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: rm > > X-Debbugs-Cc: he...@debian.org, > > pkg-privacy-maintain...@alioth-lists.debian.net > > > > The pypy-stem package is broken, as pypy is a Python 2 interpreter and > > stem code is written for Pythno 3 only. Additionally Pypy is marked for > > removal #1011926. The new python-stem version 1.8.1-1.1 is not building > > pypy-stem > > anymore. So the removal of pypy-stem in testing would enable the > > migration of python-stem and would untangle it from pypy removal. > > > > And would finally help the new onionshare version to migrate to > > testing, as it depends on the new version of python3-stem. > > Migration of python-step is currently blocked as removal of pypy-stem > would render vanguards uninstallable. So what's the plan regarding > vanguards? vanguards is already on the autoremoval list due to pypy (and might even get removed before stem through python-setuptools). Making #932820 RC might be a good idea? IMHO just waiting until autoremovals sort everything out might then be good enough? > Cheers cu Adrian
Bug#1024178: RM: pypy-stem/1.8.0-3.1
Control: tags -1 moreinfo Hi Hefee On 2022-11-15 21:53:23 +0100, Hefee wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: rm > X-Debbugs-Cc: he...@debian.org, > pkg-privacy-maintain...@alioth-lists.debian.net > > The pypy-stem package is broken, as pypy is a Python 2 interpreter and > stem code is written for Pythno 3 only. Additionally Pypy is marked for > removal #1011926. The new python-stem version 1.8.1-1.1 is not building > pypy-stem > anymore. So the removal of pypy-stem in testing would enable the > migration of python-stem and would untangle it from pypy removal. > > And would finally help the new onionshare version to migrate to > testing, as it depends on the new version of python3-stem. Migration of python-step is currently blocked as removal of pypy-stem would render vanguards uninstallable. So what's the plan regarding vanguards? Cheers -- Sebastian Ramacher
Processed: Re: Bug#1024178: RM: pypy-stem/1.8.0-3.1
Processing control commands: > tags -1 moreinfo Bug #1024178 [release.debian.org] RM: pypy-stem/1.8.0-3.1 Added tag(s) moreinfo. -- 1024178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024184: transition: alkimia
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: he...@debian.org, pkg-kde-t...@lists.alioth.debian.org A easy transition as it has only one package depdens on alkimia: kmymoney (successfully builds with old and new version of alkimia). The new version of alkimia depends on serveral new libriaries, it is hard to say if the new version will compile on all archs as before. It seems like the last Qt transition is still challangeing some buildds. So we may loose some archs with this transtion. hefee Ben file: title = "alkimia"; is_affected = .depends ~ "libalkimia5-7" | .depends ~ "libalkimia5-8"; is_good = .depends ~ "libalkimia5-8"; is_bad = .depends ~ "libalkimia5-7";
Bug#1024178: RM: pypy-stem/1.8.0-3.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm X-Debbugs-Cc: he...@debian.org, pkg-privacy-maintain...@alioth-lists.debian.net The pypy-stem package is broken, as pypy is a Python 2 interpreter and stem code is written for Pythno 3 only. Additionally Pypy is marked for removal #1011926. The new python-stem version 1.8.1-1.1 is not building pypy-stem anymore. So the removal of pypy-stem in testing would enable the migration of python-stem and would untangle it from pypy removal. And would finally help the new onionshare version to migrate to testing, as it depends on the new version of python3-stem. hefee
Processed: python3-coverage: Python 3.11 support incomplete due to ignored error during build
Processing control commands: > block 1021984 by -1 Bug #1021984 [release.debian.org] (some kind of) transition: add python3.11 as a supported python3 version 1021984 was blocked by: 1023965 1021871 1023986 1023039 1023972 1021984 was not blocking any bugs. Added blocking bug(s) of 1021984: 1024148 -- 1021984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021984 1024148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021984: (some kind of) transition: add python3.11 as a supported python3 version
Hi Bas On Tue, 15 Nov 2022 at 09:15, Sebastiaan Couwenberg wrote: > Please also binNMU gdal & python-shapely in experimental: > > nmu gdal_3.6.0+dfsg-1~exp1 . ANY . experimental . -m "Rebuild with > Python 3.11 as supported" > nmu python-shapely_2.0~b2-1~exp1 . ANY . experimental . -m "Rebuild > with Python 3.11 as supported" Scheduled, thanks. Regards Graham
Bug#1021984: (some kind of) transition: add python3.11 as a supported python3 version
Please also binNMU gdal & python-shapely in experimental: nmu gdal_3.6.0+dfsg-1~exp1 . ANY . experimental . -m "Rebuild with Python 3.11 as supported" nmu python-shapely_2.0~b2-1~exp1 . ANY . experimental . -m "Rebuild with Python 3.11 as supported" Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: block 1021984 with 1023986
Processing commands for cont...@bugs.debian.org: > block 1021984 with 1023986 Bug #1021984 [release.debian.org] (some kind of) transition: add python3.11 as a supported python3 version 1021984 was blocked by: 1021871 1023972 1023039 1023965 1021984 was not blocking any bugs. Added blocking bug(s) of 1021984: 1023986 > thanks Stopping processing here. Please contact me if you need assistance. -- 1021984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
