NEW changes in oldstable-new
Processing changes file: ca-certificates-java_20190909+deb11u1_all-buildd.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_all-buildd.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_amd64-buildd.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_arm64-buildd.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_armel-buildd.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_armhf-buildd.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_i386-buildd.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_mips64el-buildd.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_mipsel-buildd.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_ppc64el-buildd.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_s390x-buildd.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: ca-certificates-java_20190909+deb11u1_source.changes ACCEPT Processing changes file: gss_1.0.3-6+deb11u1_source.changes ACCEPT
Processed: ca-certificates-java 20190909+deb11u1 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 1040930 = bullseye pending Bug #1040930 [release.debian.org] bullseye-pu: package ca-certificates-java/20190909+deb11u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040930: ca-certificates-java 20190909+deb11u1 flagged for acceptance
package release.debian.org tags 1040930 = 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: ca-certificates-java Version: 20190909+deb11u1 Explanation:
Processed: gss 1.0.3-6+deb11u1 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 1037236 = bullseye pending Bug #1037236 [release.debian.org] bullseye-pu: package gss/1.0.3-6+deb11u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037236: gss 1.0.3-6+deb11u1 flagged for acceptance
package release.debian.org tags 1037236 = 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: gss Version: 1.0.3-6+deb11u1 Explanation: add Breaks+Replaces: libgss0 (<< 0.1)
Bug#1040930: bullseye-pu: package ca-certificates-java/20190909+deb11u1
On 23/07/2023 15.01, Jonathan Wiltshire wrote: On Wed, Jul 12, 2023 at 04:11:04PM +0200, Andreas Beckmann wrote: The bullseye-security upload of openjdk-17 broke the very fragile assumption in ca-certificates-java that a jre can be used even before it was configured for the first time. As a result new installations of openjdk-17-jre-headless from bullseye-security (or -pu) (and its circular dependency ca-certificates-java from bookworm) will fail, #1039472, (but upgrades seem to work fine, since the jre has been configured at least once in the past). Please go ahead. Should it be published even before the next point release is scheduled? Uploaded. As this only affects new installs (and a specific configuration order of the packages within the dependency loop) but not upgrades, this probably does not need to be pushed to bullseye-updates. AFAIK there haven't been any user bug reports about this issue, yet, since the breakage happened 4 weeks ago. @doko: branch bullseye and signed tag are available in g...@salsa.debian.org:anbe/ca-certificates-java.git Andreas
Processed: Re: Bug#1037188: bullseye-pu: package git/2.30.2-1+deb11u3
Processing control commands: > tag -1 - moreinfo Bug #1037188 [release.debian.org] bullseye-pu: package git/2.30.2-1+deb11u3 Removed tag(s) moreinfo. -- 1037188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037188: bullseye-pu: package git/2.30.2-1+deb11u3
Control: tag -1 - moreinfo On 08/07/2023 19.25, Adam D. Barratt wrote: It looks like not all of the postinst was removed - was that intentional? It's presumably harmless, but now leads to a lintian warning, which is why I noticed. :-) That git-el.postinst code was already removed by c4b054cf0e debian: drop support for upgrades from pre-1.7.9.5 versions (Mon Dec 28 20:13:48 2020 -0800) and I missed the opportunity to simply delete the whole file when I backported 67b73aadeb debian: remove git-el package (Mon May 31 15:03:12 2021 -0700). The remaining bits should be harmless (it's a postinst script for a package no longer in d/control), but if you prefer, I can reupload with the cruft bits removed, too. Should save a few brain cycles on future updates ;-) Andreas
Bug#1040498: Please give preference to this package (Was: r-bioc-densvis_1.10.2+dfsg-1_amd64.changes is NEW)
Hi ftpmasters, this package is needed to complete the Transitions r-api-bioc-3.17[1] since it is a new dependency of package r-bioc-scater. Thanks a lot in advance for processing this package quickly Andreas. [1] https://release.debian.org/transitions/html/r-api-bioc-3.17.html Am Thu, Jul 27, 2023 at 07:52:54AM + schrieb Debian FTP Masters: > binary:r-bioc-densvis is NEW. > binary:r-bioc-densvis is NEW. > source:r-bioc-densvis is NEW. > > Your package has been put into the NEW queue, which requires manual action > from the ftpteam to process. The upload was otherwise valid (it had a good > OpenPGP signature and file hashes are valid), so please be patient. > > Packages are routinely processed through to the archive, and do feel > free to browse the NEW queue[1]. > > If there is an issue with the upload, you will receive an email from a > member of the ftpteam. > > If you have any questions, you may reply to this email. > > [1]: https://ftp-master.debian.org/new.html > or https://ftp-master.debian.org/backports-new.html for *-backports > > ___ > R-pkg-team mailing list > r-pkg-t...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team > -- http://fam-tille.de
NEW changes in oldstable-new
Processing changes file: lapack_3.9.0-3+deb11u1_mips64el-buildd.changes ACCEPT Processing changes file: protobuf_3.12.4-1+deb11u1_mips64el-buildd.changes ACCEPT
Bug#1040842: transition: libfm-qt
On Thu, Jul 27, 2023 at 12:30:58AM +0200, Sebastian Ramacher wrote:
> Please go ahead.
All packages have been uploaded to unstable, thanks for the help.
https://release.debian.org/transitions/html/auto-libfm-qt.html
--
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
https://czchen.org/
Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B
signature.asc
Description: PGP signature
NEW changes in oldstable-new
Processing changes file: protobuf_3.12.4-1+deb11u1_mipsel-buildd.changes ACCEPT
Processed: Transition blocked by new package
Processing control commands: > block -1 by 1042368 Bug #1040498 [release.debian.org] transition: r-bioc-biocgenerics 1040498 was blocked by: 1041598 1040498 was not blocking any bugs. Added blocking bug(s) of 1040498: 1042368 -- 1040498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040498: Transition blocked by new package
Control: block -1 by 1042368 -- http://fam-tille.de
Processed: found 1041493 in 0.15.1-6, severity of 1041493 is serious, block 1041667 with 1041493
Processing commands for cont...@bugs.debian.org: > found 1041493 0.15.1-6 Bug #1041493 [src:wlroots] wlroots: FTBFFS with ffmpeg 6.0 Marked as found in versions wlroots/0.15.1-6. > severity 1041493 serious Bug #1041493 [src:wlroots] wlroots: FTBFFS with ffmpeg 6.0 Severity set to 'serious' from 'important' > block 1041667 with 1041493 Bug #1041667 [release.debian.org] transition: ffmpeg 1041667 was blocked by: 1041666 1041506 1041637 1041380 1041665 1041382 1041636 1041507 1041379 1041505 1041504 1041664 1041492 1041401 1041376 1041356 1041400 1041402 1041378 1041377 1041375 1041667 was not blocking any bugs. Added blocking bug(s) of 1041667: 1041493 > thanks Stopping processing here. Please contact me if you need assistance. -- 1041493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041493 1041667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028436: marked as done (transition: re2)
Your message dated Thu, 27 Jul 2023 09:11:12 +0200 with message-id and subject line Re: Bug#1028436: transition: re2 has caused the Debian Bug report #1028436, 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.) -- 1028436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028436 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: r...@packages.debian.org Control: affects -1 + src:re2 Sorry for a last minute request. I was just looking through my packages on the weekend and noticed that re2 had tagged a new release, but I hadn't seen it due to the GitHub layout change last year. This is a very minor ABI break in the C++ library, caused by changing class layout. The in the 6 months since the previous release, they've only made 22 commits. Which also means that if it misses the freeze, it's probably not a big deal. The new version is currently sitting in experimental bin-NEW. I've test-built the reverse dependencies, they all build, except for unrelated failures: $ grep ^Status *.build chromium_amd64.build:Status: successful clickhouse_amd64.build:Status: successful dnsdist_amd64.build:Status: successful effcee_amd64.build:Status: attempted grpc_amd64.build:Status: successful inspircd_amd64.build:Status: successful libphonenumber_amd64.build:Status: successful libpog_amd64.build:Status: successful libre-engine-re2-perl_amd64.build:Status: successful libvmod-re2_amd64.build:Status: successful node-re2_amd64.build:Status: successful pytorch-text_amd64.build:Status: given-back qt6-webengine_amd64.build:Status: successful qtwebengine-opensource-src_amd64.build:Status: attempted re2_20221201+dfsg-1_amd64.build:Status: successful ruby-re2_amd64.build:Status: successful sphinxsearch_amd64.build:Status: successful effcee: FTBFS with GCC-11: #984048 pytorch-text: FTBFS with Python 3.10 (yes 3.10, not 3.11): #1008924 qtwebengine-opensource-src: FTBFS with Python 3.11 (fixed in 5.15.12+dfsg-1 in experimental) Ben file: title = "re2"; is_affected = .depends ~ "libre2-9" | .depends ~ "libre2-10"; is_good = .depends ~ "libre2-10"; is_bad = .depends ~ "libre2-9"; Thanks for the consideration! Stefano --- End Message --- --- Begin Message --- On 2023-06-14 02:58:04 +, stefa...@debian.org wrote: > Hi Sebastian (2023.06.13_21:42:46_+) > > Please go ahead with the upload to unstable. > > Uploaded, thanks! The old binaries got removed from testing. Closing. Cheers -- Sebastian Ramacher--- End Message ---
