Bug#960364: nmu: libalien-wxwidgets-perl_0.69+dfsg-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu libalien-wxwidgets-perl_0.69+dfsg-3 . ANY . unstable . -m "Rebuild for new wxwidgets3.0 3.0.5.1+dfsg release" -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: src:chromium: FTBFS with re2 20200501
Processing control commands: > block 960360 by -1 Bug #960360 [release.debian.org] transition: re2 960360 was not blocked by any bugs. 960360 was not blocking any bugs. Added blocking bug(s) of 960360: 960361 -- 960360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960360 960361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960360: transition: re2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Public ABI Breakage: Types changed from maps to vectors in a couple of functions. Nothing in Debian uses them. Public API Breakage: The deprecated RE2::Options::set_utf8 and RE2::Options::utf8 helper functions were removed from re2.h. https://github.com/google/re2/commit/58141dc9c92189ed8d046f494f5e034d5db91bea https://github.com/google/re2/commit/ac65d4531798ffc9bf807d1f7c09efb0eec70480 Reverse Dependencies: * Updated ruby-re2 to 1.2.0 to support this. * Chromium needs a patch: https://github.com/chromium/chromium/commit/ede390a0b18e4565abf8ac1e1ff717e1d43fc320 * Others build without error. Ben file: title = "re2"; is_affected = .depends ~ "libre2-6" | .depends ~ "libre2-7"; is_good = .depends ~ "libre2-7"; is_bad = .depends ~ "libre2-6"; https://release.debian.org/transitions/html/auto-re2.html LGTM SR
NEW changes in oldstable-new
Processing changes file: pcl_1.8.0+dfsg1-4+deb9u1_mipsel.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: iptables-persistent_1.0.4+nmu2+deb9u1_all.changes ACCEPT
Bug#954020: buster-pu: package zipios++/0.1.5.9+cvs.2007.04.28-10+deb10u1
Hello Georg, thanks a lot for your help. The packaging repo is: https://salsa.debian.org/mzf/zipios the branch for this buster patch is "fix_CVE-2019-13453_for_buster": https://salsa.debian.org/mzf/zipios/-/tree/fix_CVE-2019-13453_for_buster the last commit is: https://salsa.debian.org/mzf/zipios/-/commit/7bdc65a62cacea47e03c13e6d92157da3c11f6bd I can upload the package to mentors.d.n if needed. Just let me know. Best, François
NEW changes in oldstable-new
Processing changes file: iptables-persistent_1.0.4+nmu2+deb9u1_source.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: pcl_1.8.0+dfsg1-4+deb9u1_mips.changes ACCEPT
Bug#921319: iptables-persistent 1.0.4+nmu2+deb9u1 flagged for acceptance
package release.debian.org tags 921319 = stretch pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: iptables-persistent Version: 1.0.4+nmu2+deb9u1 Explanation: don't fail if modprobe does
Processed: iptables-persistent 1.0.4+nmu2+deb9u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 921319 = stretch pending Bug #921319 [release.debian.org] stretch-pu: package iptables-persistent/1.0.4+nmu2 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 921319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955711: marked as done (transition: schroedinger-maeparser)
Your message dated Mon, 11 May 2020 21:30:45 +0200 with message-id <20200511193045.ga816...@ramacher.at> and subject line Re: Bug#955711: schroedinger-maeparser tansition is complete has caused the Debian Bug report #955711, regarding transition: schroedinger-maeparser 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.) -- 955711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955711 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: transition Hello, I would like to request a transition slot for schroedinger-maeparser (experimental -> unstable) due to the changed binary package names. Current ben tracker [1] is fine. Affected packages: * openbabel * schroedinger-coordgenlibs * rdkit Affected packages will need source uploads to adjust their Depends line. I have successfully test rebuilt them. All the packages are team-maintained, so I will be able to perform the uploads myself. Thanks, Andrius [1] https://release.debian.org/transitions/html/auto-schroedinger-maeparser.html signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi On 2020-04-30 21:38:20 +0300, Andrius Merkys wrote: > Hello, > > schroedinger-maeparser transition seems to be complete. All related > packages had been rebuilt, and have already migrated to testing. I suppose > transition bug can now be closed. Indeed, closing. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#954288: marked as done (transition: re2)
Your message dated Mon, 11 May 2020 11:17:41 -0700 with message-id <20200511181741.l26yckdkytgii...@elgar.kardiogramm.net> and subject line Re: Bug#954288: transition: re2 has caused the Debian Bug report #954288, regarding transition: re2 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.) -- 954288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954288 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: transition C++. Lots of ABI breakage... Class members were reorganised, and mutability changed. Upstream chose to SONAME bump. https://github.com/google/re2/issues/243 In other news: Upstream is finally taking ownership of their soname \o/ https://release.debian.org/transitions/html/auto-re2.html looks good. I test built all of the rev-deps (on March 3rd) and they all built, except for clickhouse (known FTBFS: #950983). Ben file: title = "re2"; is_affected = .depends ~ "libre2-5" | .depends ~ "libre2-6"; is_good = .depends ~ "libre2-6"; is_bad = .depends ~ "libre2-5"; -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), LANGUAGE=en_ZA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- This transition was completed, now it's time for the next one :( SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272--- End Message ---
NEW changes in oldstable-new
Processing changes file: pcl_1.8.0+dfsg1-4+deb9u1_armhf.changes ACCEPT
Bug#960193: transition: icu
Hi, Il 11/05/20 14:26, Adrian Bunk ha scritto: > Is there a good reason why the boost 1.67 -> 1.71 transition has already > happened in Ubuntu but not yet in Debian? The reason I know about is that I am the only person working on it at the moment, and I don't have much time myself. I am filing bugs and patches for packages not building any more[1] and will request a transition once things seem to be ready. [1] https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=team%2Bboost%40tracker.debian.org=boost1.71 Giovanni. -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles signature.asc Description: OpenPGP digital signature
Bug#960193: transition: icu
On Mon, May 11, 2020 at 12:59:07PM +0100, Dimitri John Ledkov wrote: > On Mon, 11 May 2020 at 12:34, Adrian Bunk wrote: > > > > On Sun, May 10, 2020 at 03:40:43PM +0200, László Böszörményi wrote: > > > > > > Level 1.5 is needed for Boost packages to be binNMUed: > > > Both boost1.67 and boost1.71 build correctly. > > >... > > > > Changing the icu version changes the libboost_regex ABI. > > > > The libboost-regex*-icu* provides untangle icu transitions from boost > > transitions, but reverse dependencies of libboost-regex1.67.0 in buster > > depend on libboost-regex1.67.0 not libboost-regex1.67.0-icu63. > > If icu in unstable could add Breaks: libbost-regex1.67-0 (<< > 1.67.0-141) that should be sufficient to ensure upgrades happen the > right way around from buster. This is only true for upgrades from buster that happen after libbost-regex1.67-0 has been removed from unstable and testing. The safe way is: > Alternatively, we should work on removing boost1.67 in unstable & > testing. It should not ship. >... Is there a good reason why the boost 1.67 -> 1.71 transition has already happened in Ubuntu but not yet in Debian? > Regards, > > Dimitri. cu Adrian
Bug#960193: transition: icu
On Mon, 11 May 2020 at 12:59, Dimitri John Ledkov wrote: > > If icu in unstable could add Breaks: libbost-regex1.67-0 (<< > 1.67.0-141) that should be sufficient to ensure upgrades happen the should read (<< 1.67.0-14~)
Bug#960193: transition: icu
On Mon, 11 May 2020 at 12:34, Adrian Bunk wrote: > > On Sun, May 10, 2020 at 03:40:43PM +0200, László Böszörményi wrote: > > > > Level 1.5 is needed for Boost packages to be binNMUed: > > Both boost1.67 and boost1.71 build correctly. > >... > > Changing the icu version changes the libboost_regex ABI. > > The libboost-regex*-icu* provides untangle icu transitions from boost > transitions, but reverse dependencies of libboost-regex1.67.0 in buster > depend on libboost-regex1.67.0 not libboost-regex1.67.0-icu63. > If icu in unstable could add Breaks: libbost-regex1.67-0 (<< 1.67.0-141) that should be sufficient to ensure upgrades happen the right way around from buster. Alternatively, we should work on removing boost1.67 in unstable & testing. It should not ship. boost-regex*-icu* otherwise should be binNMU safe in testing/unstable otherwise. > This means one boost transition is needed before the untangling > is finished, and this has to happen before this icu transition. > boost1.67 should never be rebuilt with a more recent icu. > > Additionally, everything depending on libboost-regex1.67.0-icu63 > or libboost-regex1.71.0-icu63 is also part of this icu transition. yes -- Regards, Dimitri.
Bug#960193: transition: icu
On Sun, May 10, 2020 at 03:40:43PM +0200, László Böszörményi wrote: > > Level 1.5 is needed for Boost packages to be binNMUed: > Both boost1.67 and boost1.71 build correctly. >... Changing the icu version changes the libboost_regex ABI. The libboost-regex*-icu* provides untangle icu transitions from boost transitions, but reverse dependencies of libboost-regex1.67.0 in buster depend on libboost-regex1.67.0 not libboost-regex1.67.0-icu63. This means one boost transition is needed before the untangling is finished, and this has to happen before this icu transition. boost1.67 should never be rebuilt with a more recent icu. Additionally, everything depending on libboost-regex1.67.0-icu63 or libboost-regex1.71.0-icu63 is also part of this icu transition. cu Adrian
Re: Bug#953235: vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython'
On Mon, May 11, 2020 at 08:31:37AM +0200, Mathieu Malaterre wrote: > On Sun, May 10, 2020 at 10:01 PM Paul Gevers wrote: >... > > On 10-05-2020 15:25, Paul Gevers wrote: > > > I'm running another check on "cannot allocate memory in static TLS > > > block" now, will take a while. > > > > Also for this one, only vtkplotter showed up. > > Did you check #951704 ? This affect python3 package using jemalloc. I wrote earlier: On Thu, May 07, 2020 at 01:16:15PM +0300, Adrian Bunk wrote: >... > #951704 looks like a similar but unrelated problem with jemalloc. >... My current knowledge is: The jemalloc problem is a problem affecting all architectures, that will likely need a fix/workaround in jemalloc. The libgomp problem is a problem only on arm64/ppc64/ppc64el where upstreams seem to finally have agreed where it should be fixed (glibc). cu Adrian
Bug#954020: buster-pu: package zipios++/0.1.5.9+cvs.2007.04.28-10+deb10u1
Hi, On 20-05-10 09:00:59, Salvatore Bonaccorso wrote: > Thanks for considering sponsoring it. > > Note I'm not SRM, but the upload was acked in > https://bugs.debian.org/954020#24 ACK, I agree. > Thanks François for preparing the update! Thanks from my side as well. Could you provide me a link to the packaging repository, [1] gives 404. Alternatively, could you upload the relevant files to mentors.d.n? Cheers, Georg [1] https://anonscm.debian.org/cgit/collab-maint/zipios++.git
Processed: Re: Bug#960193: transition: icu
Processing control commands: > block -1 by 960236 960239 690240 690242 690243 960237 955114 Bug #960193 [release.debian.org] transition: icu 960193 was blocked by: 960263 960193 was not blocking any bugs. Added blocking bug(s) of 960193: 960236, 960239, 960241, 955114, and 960237 -- 960193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cyrus-imapd: FTBFS on arm*, i386, mipsel, ppc64el and s390x
Processing control commands: > block 960193 by -1 Bug #960193 [release.debian.org] transition: icu 960193 was not blocked by any bugs. 960193 was not blocking any bugs. Added blocking bug(s) of 960193: 960263 -- 960193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960193 960263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960193: transition: icu
Control: block -1 by 960236 960239 690240 690242 690243 960237 955114 On 2020-05-10 18:15:57 +0200, László Böszörményi (GCS) wrote: > Hi Sebastian, > > On Sun, May 10, 2020 at 4:09 PM Sebastian Ramacher > wrote: > > On 2020-05-10 15:40:43 +0200, László Böszörményi wrote: > > Have bugs been filed for those build issues? > Not yet - forgot to ask if I should do it immediately. It seems clear > Chromium will not make it in time (as noted it's two security releases > behind), while on the other hand this transition is the last step to > have Node.js 12.16 and its modules to Sid. But I will file those bugs > soon. I noticed that you already filed them. Thanks! I'm marking them as blocking this bug to keep track. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
NEW changes in oldstable-new
Processing changes file: pcl_1.8.0+dfsg1-4+deb9u1_mips64el.changes ACCEPT
Re: Bug#953235: vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython'
On Sun, May 10, 2020 at 10:01 PM Paul Gevers wrote: > > Hi Adrian, > > On 10-05-2020 15:25, Paul Gevers wrote: > > I'm running another check on "cannot allocate memory in static TLS > > block" now, will take a while. > > Also for this one, only vtkplotter showed up. Did you check #951704 ? This affect python3 package using jemalloc. > Paul > -- Mathieu
