Bug#1017740: transition: draco
Hi, On 06-09-2022 17:34, Timo Röhling wrote: Given that assimp was specifically binNMU-rebuilt for the new draco version, Sorry, I missed this part. Paul OpenPGP_signature Description: OpenPGP digital signature
NEW changes in stable-new
Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_source.changes ACCEPT
Bug#1019284: transition: linphone-stack
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear release team, I'm asking for permission for a small mostly self-contained transition of the whole linphone stack. It has been staged in experimental. Most of these libraries don't change SONAME, but upstream only supports staying within the same minor version. So there is a (>= | < ) dependency generated with shlibs and the stack will have to migrate in one go. bctoolbox 4.4.13-4 -> 5.0.37-2 belr 4.4.13-2 -> 5.0.37-1 bzrtp 4.4.13-2 -> 5.0.37-1 lime NEW in unstable bcmatroska2 NEW in unstable ortp 1:4.4.13-2 -> 1:5.0.37-1 belcard 4.4.13-2 -> 5.0.37-1 belle-sip 4.4.21+dfsg-2 -> 5.0.37+dfsg-2 mediastreamer2 1:4.4.21 -> 1:5.0.37+dfsg-3 linphone 4.4.21-2 -> 5.0.37-4 linphone-desktop 4.2.5-3 -> 4.3.2-1 only ortp has reverse dependencies outside of the linphone stack that will need a binNMU. They have been successfully built against the version in experimental. bcg729 trx libosmo-abis libosmo-netif osmo-bts Bernhard
Bug#1019243: libayatana-appindicator 0.5.5-2+deb11u2 flagged for acceptance
package release.debian.org tags 1019243 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: libayatana-appindicator Version: 0.5.5-2+deb11u2 Explanation: fix dependency versions
Processed: libayatana-appindicator 0.5.5-2+deb11u2 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 1019243 = bullseye pending Bug #1019243 [release.debian.org] bullseye-pu: package libayatana-appindicator/0.5.5-2+deb11u2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1019243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_s390x-buildd.changes ACCEPT
Bug#1009829: marked as done (release.debian.org: please add hint: 'allow-uninst cacti-spine/armel' to enable migration of cacti)
Your message dated Wed, 7 Sep 2022 00:55:59 +0200 with message-id and subject line Re: Bug#1009829: release.debian.org: please add hint: 'allow-uninst cacti-spine/armel' to enable migration of cacti has caused the Debian Bug report #1009829, regarding release.debian.org: please add hint: 'allow-uninst cacti-spine/armel' to enable migration of cacti 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.) -- 1009829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Dear colleagues, Several days ago, I uploaded a new version of cacti to unstable which has one arch:all binary. One of it's reverse dependencies is cacti-spine, which builds an arch:any binary. In my upload I changed the dependency of libjs-d3 to node-d3 as the latter is a much newer version of the same thing, which is more in line with cacti upstream. However, the node ecosystem is broken on armel, hence cacti doesn't migrate, as its migration would make cacti-spine not installable on armel. Given that the node failure on armel is long standing, I think it's acceptable to ignore it for cacti, so please add the following hint: allow-uninst cacti-spine/armel Paul --- End Message --- --- Begin Message --- On 2022-04-18 20:45:20 +0200, Paul Gevers wrote: > Package: release.debian.org > Severity: normal > > Dear colleagues, > > Several days ago, I uploaded a new version of cacti to unstable which > has one arch:all binary. One of it's reverse dependencies is > cacti-spine, which builds an arch:any binary. In my upload I changed > the dependency of libjs-d3 to node-d3 as the latter is a much newer > version of the same thing, which is more in line with cacti > upstream. However, the node ecosystem is broken on armel, hence cacti > doesn't migrate, as its migration would make cacti-spine not > installable on armel. Given that the node failure on armel is long > standing, I think it's acceptable to ignore it for cacti, so please > add the following hint: > > allow-uninst cacti-spine/armel cacti migrated in the meantime. So this override should no longer be necessary. Cheers -- Sebastian Ramacher--- End Message ---
Bug#1017740: marked as done (transition: draco)
Your message dated Wed, 7 Sep 2022 00:48:37 +0200 with message-id and subject line Re: Bug#1017740: transition: draco has caused the Debian Bug report #1017740, regarding transition: draco 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.) -- 1017740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017740 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 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear release team, I'd like to transition draco after its SONAME bump. The ben file looks good: https://release.debian.org/transitions/html/auto-draco.html All reverse dependencies build sucessfully on amd64. Cheers Timo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmL/20sACgkQ+C8H+466 LVluVwv/ZqAVTnKQPAl3V9qwU+9IilDYOuyUhDySmZVwXq79LlIWxTOgCpSHrxAX 4WxOVBUrfCSG7ZkOYvyJ/Do9B/mSI8K5kZ8P+gj8ot5vF+95aq3QftDw5csa3eEH yEGzdugc42qsKSA1wtNYE1cdC2n8UBTPCePY0OB86/6QHEXFUzhHaz+gGQooKNHd k8hsW3Z4941KespUyqWB+Qdc//E1BeTVAtzQ52yfTw0GKVMI83iPh2q0B4Umuqts 1Y0KlzijgBfCEUdoU7gqDZ6tYASFiDf7SxKeOPdaaX2o+ugKZO09M4fEAo5pjVKg j0JkLtjNCplNSm09mFVZXJsT0wv1/IrlJ4G1YYyY/cseB8wKgi5J7LfK8Bn1dT4L 0b3r2ldaq4y7ukyZg/d2Im10m3nOrv7kl8Y6xOTrRLgWpMfq7GkCLGM6g84+skKd /nCp0pPrd3YzDD/Nt1heUFAyFtmAakh1eV6flqIEuyQjqkSfU6YzN3+jd2mM/Vau tcstoFPF =X4pv -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On 2022-09-06 19:28:02 +0200, Paul Gevers wrote: > Hi, > > On 06-09-2022 17:34, Timo Röhling wrote: > > Given that assimp was specifically binNMU-rebuilt for the new draco > > version, > > Sorry, I missed this part. Hint added and draco migrated. This transition is done. Cheers -- Sebastian Ramacher--- End Message ---
Bug#1018876: marked as done (transition: ace)
Your message dated Wed, 7 Sep 2022 00:49:34 +0200 with message-id and subject line Re: Bug#1018876: transition: ace has caused the Debian Bug report #1018876, regarding transition: ace 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.) -- 1018876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018876 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 X-Debbugs-Cc: sudipm.mukher...@gmail.com Hi, Small transition with only two affected packages: diagnostics, ivtools. diagnostics already has a FTBFS due to #1012912, so could not test it. ivtools builds fine with ace 7.0.8+dfsg-1 version in experimental. The autogenerated ben tracker looks good. Please consider 'ace' for transition. Thanks in advance. -- Regards Sudip --- End Message --- --- Begin Message --- On 2022-09-02 15:03:59 +0200, Sebastian Ramacher wrote: > On 2022-09-02 11:05:59 +0100, Sudip Mukherjee wrote: > > On Thu, Sep 1, 2022 at 10:36 PM Sebastian Ramacher > > wrote: > > > > > > Control: tags -1 confirmed > > > > > > On 2022-09-01 10:53:10 +0100, Sudip Mukherjee wrote: > > > > Package: release.debian.org > > > > Severity: normal > > > > User: release.debian@packages.debian.org > > > > Usertags: transition > > > > X-Debbugs-Cc: sudipm.mukher...@gmail.com > > > > > > > > Hi, > > > > > > > > Small transition with only two affected packages: diagnostics, ivtools. > > > > > > > > diagnostics already has a FTBFS due to #1012912, so could not test it. > > > > ivtools builds fine with ace 7.0.8+dfsg-1 version in experimental. > > > > > > > > The autogenerated ben tracker looks good. Please consider 'ace' for > > > > transition. > > > > Thanks in advance. > > > > > > Please go ahead > > > > Thanks. Uploaded now. > > I have a fix for the diagnostics FTBFS also. Do you want me to upload > > it to DELAYED/1-day queue now or upload after this transition is over? > > As the package is currently not part of testing, it makes no difference > for the transition if you fix it now or later. ace migrated and the old binaries got removed. Cheers -- Sebastian Ramacher--- End Message ---
NEW changes in stable-new
Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_all-buildd.changes ACCEPT Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_amd64-buildd.changes ACCEPT Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_arm64-buildd.changes ACCEPT Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_armel-buildd.changes ACCEPT Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_armhf-buildd.changes ACCEPT Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_i386-buildd.changes ACCEPT Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_mips64el-buildd.changes ACCEPT Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_mipsel-buildd.changes ACCEPT Processing changes file: libayatana-appindicator_0.5.5-2+deb11u2_ppc64el-buildd.changes ACCEPT
Bug#1018912: marked as done (transition: bamtools)
Your message dated Tue, 6 Sep 2022 09:34:00 +0200 with message-id and subject line Re: Bug#1018912: transition: bamtools has caused the Debian Bug report #1018912, regarding transition: bamtools 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.) -- 1018912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018912 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 Dear Release Team, bamtools recently cleared New processing after an soversion bump from 2.5.1 to 2.5.2 and is now available in experimental. I verified the package builds properly on all architectures in testing. Pseudo-excuses are looking good[1], the ben tracker[2] too. Please kindly consider providing a transition slot when deemed appropriate. [1]: https://release.debian.org/britney/pseudo-excuses-experimental.html#bamtools [2]: https://release.debian.org/transitions/html/auto-bamtools.html Ben file: title = "bamtools"; is_affected = .depends ~ "libbamtools2.5.1" | .depends ~ "libbamtools2.5.2"; is_good = .depends ~ "libbamtools2.5.2"; is_bad = .depends ~ "libbamtools2.5.1"; Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/5, please excuse my verbosity. On air: Saga - Hot To Cold signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On 2022-09-05 20:11:25 +0200, Étienne Mollier wrote: > Hi Sebastian, > > Étienne Mollier, on 2022-09-02: > > Sebastian Ramacher, on 2022-09-01: > > > On 2022-09-01 23:01:04 +0200, Étienne Mollier wrote: > > > > Package: release.debian.org > > > > Severity: normal > > > > User: release.debian@packages.debian.org > > > > Usertags: transition > > > > > > > > Dear Release Team, > > > > > > > > bamtools recently cleared New processing after an soversion bump > > > > from 2.5.1 to 2.5.2 and is now available in experimental. I > > > > verified the package builds properly on all architectures in > > > > testing. Pseudo-excuses are looking good[1], the ben tracker[2] > > > > too. Please kindly consider providing a transition slot when > > > > deemed appropriate. > > > > > > Please go ahead > > > > bamtools uploaded, thanks! If I understood the procedure > > correctly, reverse dependencies may soon be binNMU'ed. > > The new library has migrated to testing along with reverse > dependencies, and the old one does not seem available there > anymore. The transition looks complete I believe. Indeed, closing. Cheers -- Sebastian Ramacher--- End Message ---
Bug#1019220: marked as done (nmu: bind-dyndb-ldap_11.10-1)
Your message dated Tue, 6 Sep 2022 09:33:09 +0200 with message-id and subject line Re: Bug#1019220: nmu: bind-dyndb-ldap_11.10-1 has caused the Debian Bug report #1019220, regarding nmu: bind-dyndb-ldap_11.10-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.) -- 1019220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019220 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: binnmu Hi, while Bug#1014503 is not fixed we need another binNMU of bind-dyndb-ldap against the new version of bind9 in unstable (accepted a few minutes ago) nmu bind-dyndb-ldap_11.10-1 . ANY . unstable . -m "Rebuild for bind9/1:9.18.6-2" Thanks, Bernhard --- End Message --- --- Begin Message --- On 2022-09-05 21:56:21 +0200, Bernhard Schmidt wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > Hi, > > while Bug#1014503 is not fixed we need another binNMU of bind-dyndb-ldap > against the new version of bind9 in unstable (accepted a few minutes ago) > > nmu bind-dyndb-ldap_11.10-1 . ANY . unstable . -m "Rebuild for > bind9/1:9.18.6-2" Scheduled Cheers -- Sebastian Ramacher--- End Message ---
Processed: Re: Bug#1019239: transition: coq (41 packages involved)
Processing control commands: > tags -1 confirmed Bug #1019239 [release.debian.org] transition: coq (41 packages involved) Added tag(s) confirmed. -- 1019239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019239: transition: coq (41 packages involved)
Control: tags -1 confirmed On 2022-09-06 07:14:25 +0200, Julien Puydt wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: jpu...@debian.org > X-Debbugs-Cc: Debian OCaml Maintainers > > Hi, > > I would like to upload coq 8.16.0+dfsg-1 to unstable ; that also means > uploading a number of new versions for other packages: > aac-tactics 8.16.0-1 > coq-bignums 8.16.0-1 > coq-dpdgraph 1.0+8.16-1 > coq-elpi 1.15.5-1 > coq-reduction-effects 0.1.4-2 > coq-hammer 1.3.2+8.16-1 > coq-unicoq 1.6-8.16-1 > paramcoq 1.1.3+coq8.16-1 > coq-hott 8.16-1 > coq-equations 1.3-8.16-1 > coq-gappa 1.5.2-4 > coq-hierarchy-builder 1.3.0-2 > coq-mtac2 1.4+8.16-1 > coq-simple-io 1.7.0-3 > coq-corn 8.16.0-1 > coq-quickchick 1.6.4-2 > mathcomp-analysis 0.5.3-2 > > and to just recompile a list of others : all 41 packages of the Coq > ecosystem are involved! > > I would like to dput all new package versions and let the buildd trigger > things in order. I checked all compilation would go well on my amd64 box. > > My experimental wanna-build script gave me something I'll paste below -- as > you can guess it's a bit long. > > Just waiting for a "Go!", Please go ahead and let me know once you're done with all the uploads. Cheers > > J.Puydt > > PS: > nmu coq-deriving_0.1.0-1+b1 . ANY . -m 'Rebuild due to coq=8.16.0+dfsg-1 > aac-tactics=8.16.0-1 coq-bignums=8.16.0-1 coq-dpdgraph=1.0+8.16-1 > coq-elpi=1.15.5-1 coq-reduction-effects=0.1.4-2 coq-hammer=1.3.2+8.16-1 > coq-unicoq=1.6-8.16-1 paramcoq=1.1.3+coq8.16-1 coq-hott=8.16-1 > coq-equations=1.3-8.16-1 coq-gappa=1.5.2-4 coq-hierarchy-builder=1.3.0-2 > coq-mtac2=1.4+8.16-1 coq-simple-io=1.7.0-3 coq-corn=8.16.0-1 > coq-quickchick=1.6.4-2 mathcomp-analysis=0.5.3-2' > dw coq-deriving_0.1.0-1+b1 . ANY . -m 'coq => 8.16.0+dfsg-1' > nmu coqeal_1.1.1-1+b1 . ANY . -m 'Rebuild due to coq=8.16.0+dfsg-1 > aac-tactics=8.16.0-1 coq-bignums=8.16.0-1 coq-dpdgraph=1.0+8.16-1 > coq-elpi=1.15.5-1 coq-reduction-effects=0.1.4-2 coq-hammer=1.3.2+8.16-1 > coq-unicoq=1.6-8.16-1 paramcoq=1.1.3+coq8.16-1 coq-hott=8.16-1 > coq-equations=1.3-8.16-1 coq-gappa=1.5.2-4 coq-hierarchy-builder=1.3.0-2 > coq-mtac2=1.4+8.16-1 coq-simple-io=1.7.0-3 coq-corn=8.16.0-1 > coq-quickchick=1.6.4-2 mathcomp-analysis=0.5.3-2' > dw coqeal_1.1.1-1+b1 . ANY . -m 'coq => 8.16.0+dfsg-1' > dw coqeal_1.1.1-1+b1 . ANY . -m 'paramcoq => 1.1.3+coq8.16-1' > dw coqeal_1.1.1-1+b1 . ANY . -m 'coq-bignums => 8.16.0-1' > nmu coq-ext-lib_0.11.7-1 . ANY . -m 'Rebuild due to coq=8.16.0+dfsg-1 > aac-tactics=8.16.0-1 coq-bignums=8.16.0-1 coq-dpdgraph=1.0+8.16-1 > coq-elpi=1.15.5-1 coq-reduction-effects=0.1.4-2 coq-hammer=1.3.2+8.16-1 > coq-unicoq=1.6-8.16-1 paramcoq=1.1.3+coq8.16-1 coq-hott=8.16-1 > coq-equations=1.3-8.16-1 coq-gappa=1.5.2-4 coq-hierarchy-builder=1.3.0-2 > coq-mtac2=1.4+8.16-1 coq-simple-io=1.7.0-3 coq-corn=8.16.0-1 > coq-quickchick=1.6.4-2 mathcomp-analysis=0.5.3-2' > dw coq-ext-lib_0.11.7-1 . ANY . -m 'coq => 8.16.0+dfsg-1' > nmu coq-extructures_0.3.1-2 . ANY . -m 'Rebuild due to coq=8.16.0+dfsg-1 > aac-tactics=8.16.0-1 coq-bignums=8.16.0-1 coq-dpdgraph=1.0+8.16-1 > coq-elpi=1.15.5-1 coq-reduction-effects=0.1.4-2 coq-hammer=1.3.2+8.16-1 > coq-unicoq=1.6-8.16-1 paramcoq=1.1.3+coq8.16-1 coq-hott=8.16-1 > coq-equations=1.3-8.16-1 coq-gappa=1.5.2-4 coq-hierarchy-builder=1.3.0-2 > coq-mtac2=1.4+8.16-1 coq-simple-io=1.7.0-3 coq-corn=8.16.0-1 > coq-quickchick=1.6.4-2 mathcomp-analysis=0.5.3-2' > dw coq-extructures_0.3.1-2 . ANY . -m 'coq => 8.16.0+dfsg-1' > dw coq-extructures_0.3.1-2 . ANY . -m 'coq-deriving => 0.1.0-1+b2' > nmu coq-interval_4.5.2-2 . ANY . -m 'Rebuild due to coq=8.16.0+dfsg-1 > aac-tactics=8.16.0-1 coq-bignums=8.16.0-1 coq-dpdgraph=1.0+8.16-1 > coq-elpi=1.15.5-1 coq-reduction-effects=0.1.4-2 coq-hammer=1.3.2+8.16-1 > coq-unicoq=1.6-8.16-1 paramcoq=1.1.3+coq8.16-1 coq-hott=8.16-1 > coq-equations=1.3-8.16-1 coq-gappa=1.5.2-4 coq-hierarchy-builder=1.3.0-2 > coq-mtac2=1.4+8.16-1 coq-simple-io=1.7.0-3 coq-corn=8.16.0-1 > coq-quickchick=1.6.4-2 mathcomp-analysis=0.5.3-2' > dw coq-interval_4.5.2-2 . ANY . -m 'coq => 8.16.0+dfsg-1' > dw coq-interval_4.5.2-2 . ANY . -m 'coq-bignums => 8.16.0-1' > nmu coq-iris_4.0.0-1 . ANY . -m 'Rebuild due to coq=8.16.0+dfsg-1 > aac-tactics=8.16.0-1 coq-bignums=8.16.0-1 coq-dpdgraph=1.0+8.16-1 > coq-elpi=1.15.5-1 coq-reduction-effects=0.1.4-2 coq-hammer=1.3.2+8.16-1 > coq-unicoq=1.6-8.16-1 paramcoq=1.1.3+coq8.16-1 coq-hott=8.16-1 > coq-equations=1.3-8.16-1 coq-gappa=1.5.2-4 coq-hierarchy-builder=1.3.0-2 > coq-mtac2=1.4+8.16-1 coq-simple-io=1.7.0-3 coq-corn=8.16.0-1 > coq-quickchick=1.6.4-2 mathcomp-analysis=0.5.3-2' > dw coq-iris_4.0.0-1 . ANY . -m 'coq => 8.16.0+dfsg-1' > nmu coq-math-classes_8.15.0-3 . ANY . -m 'Rebuild due to coq=8.16.0+dfsg-1 > aac-tactics=8.16.0-1 coq-bignums=8.16.0-1 coq-dpdgraph=1.0+8.16-1 > coq-elpi=1.15.5-1 coq-reduction-effects=0.1.4-2 coq-hammer=1.3.2+8.16-1
Bug#1019239: transition: coq (41 packages involved)
Le mardi 06 septembre 2022 à 09:41 +0200, Sebastian Ramacher a écrit : > Control: tags -1 confirmed > > Please go ahead and let me know once you're done with all the > uploads. "dput *_source.changes" in the directory where I prepared the new uploads just finished. Thanks, J.Puydt
Bug#1018945: transition: libbpf
On Fri, Sep 02, 2022 at 11:13:26AM +0100, Sudip Mukherjee wrote: > > The autogenerated ben tracker looks good. Please consider 'libbpf' for > transition. Ok, please dont consider it yet. As mentioned in https://github.com/libbpf/libbpf/issues/562#issuecomment-1237299951 libbpf has now added a hard dependency on v6.0+ kernel. -- Regards Sudip
Bug#1016706: transition: GNOME 43 mega libsoup3 transition
I have completed my sourceful uploads. Please schedule binnmus for the rest of: https://release.debian.org/transitions/html/auto-evolution-data-server.html I've also bumped the severity to serious for the bugs affecting the packages that will need to be removed from Testing to complete this transition. - chatty - feedreader - gnome-initial-setup - gnome-recipes - libgovirt - roger-router Thank you, Jeremy Bicha
Bug#1019258: nmu: xapian-core_1.4.20-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: o...@debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 nmu xapian-core_1.4.20-2 . ANY . unstable . -m "Rebuild with gcc 12" discussion: 03-09-2022 07:29:30 > bremner: olly: will there be a new version of xapian in Debian testing compiled with gcc 12? the current version complains about potential ABI mismatch 03-09-2022 15:40:40 < olly > i'm wondering about retiring that message - it seems to do more harm than good at this point 03-09-2022 15:42:00 < olly > in the ~GCC3 days you'd get weird link failures which people would waste time trying to debug, but the modern ABI changes all seem to be obscure corner cases 03-09-2022 15:42:08 < olly > and the ABI changes frequently 03-09-2022 15:48:43 < olly > bremner: if you want to make an nmu so it gets rebuilt with GCC 12 to sort it out for now that's fine with me 03-09-2022 15:49:15 > bremner: olly: that would just be a binNMU? 03-09-2022 15:49:50 < olly > : it certainly could be -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmMXM78ACgkQA0U5G1Wq FSEfRQ/+PjJIJjU//dhmdsUEqEQPwuyQYke4K/WVBOAAYezay52ibi4VAWUIrhNf KDcc6vXJ4NeXQS0iGpF6W03aUuQ009oUVno6r3wy+C5jhdewxUSmRdeS3D6fiqwt djHcua23JoVkpu85iJKerxPmpDooGcrjp1V9F9nzPPRSj2Rnj810iklQ8VAqoaqX JfcA91zadaqGmBS0WS0jzZimCcZt+sY1x8qKFH3pgckVhfSLz/LHOZ1pONMmX0LM VE6pOXhttZdJPy3oK3X8hqmujsY9nJtFQSFZZvnrSdYM1RebBjHc6jCxfs1tJlVL R70gDbg0vlxf+TzGGvVrf27rq8Fa531Zyv4+YHopQZA8ua7vciJbkNbwfVj+nZO2 WfWHt6Ck1gaVPDqCvKYMe05RV4lhu66cFtex4jx7Mx9T72SfDGR+MFzsrolnjWKl w9Wvyz4yQENr063BohXdB2/7g+jvQwK1WMwcBQGBQmFBQu85107VxTjzCP5VEB1c Vmn5hsOjqsxnfnUePNr5vJauQSqPlPbdrg9BzbisTE+UIgfH5XdUoFFCvDGTeMB1 nNMxZfdPweZRcUnxsUA4dQDpbADh0hW4+v1QRLXmZaCG0AG+kQzdykUPYWD722Nm OKCXss0/2AxTmqq3YuzCeFE+4+JzuF1YH0nSk4HZJFSr5mRzhRw= =puHs -END PGP SIGNATURE-
Bug#1017740: transition: draco
Hi Paul, * Paul Gevers [2022-09-05 21:31]: Do I understand correctly that you think this is a test-only issue? In other words, they can migrate together without breaking tests, but if somebody would do a partial upgrade (either one of the two), there is no issue? In even other words, there is no *versioned* relation (Depends/Breaks) missing? Given that assimp was specifically binNMU-rebuilt for the new draco version, I would assume they should migrate together. Do you have a scenario in mind where this would not work? Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
