Re: Bug#1010660: britney: Crash with RecursionError: maximum recursion depth exceeded

Hi Christian, On Fri, 2022-05-06 at 12:41 +0200, Christian Marillat wrote: I'm using britney (last commit normally) 2ccce826090ebc3f2cbdb26df3c5b0817f7a7cc2 You can download data used for this crash here : https://www.deb-multimedia.org/tests/britney-2022-05-06.tar.xz Since may 2, 2022 I s

Bug#1012362: transition: luajit

Hi Mo, On 08-06-2022 16:16, M. Zhou wrote: https://qa.debian.org/excuses.php?package=luajit autopkgtest on ibm archs encountered somewhat regression, since I only removed Conflicts+Replaces from the src:luajit side. I think there one more *test* issue, the first test in src:luajit doens't exp

Bug#1012362: transition: luajit

Hi Mo, You may want to look at the FTBFS on mipsel for python-lupa. https://buildd.debian.org/status/fetch.php?pkg=python-lupa&arch=mipsel&ver=1.13%2Bdfsg-1%2Bb2&stamp=1654771416&raw=0 Paul OpenPGP_signature Description: OpenPGP digital signature

Bug#1012362: transition: luajit

Hi Mo, On 09-06-2022 13:58, Paul Gevers wrote: You may want to look at the FTBFS on mipsel for python-lupa. https://buildd.debian.org/status/fetch.php?pkg=python-lupa&arch=mipsel&ver=1.13%2Bdfsg-1%2Bb2&stamp=1654771416&raw=0 The maintainer of sysbench switched to luajit2

Bug#1012362: transition: luajit

Hi Mo, On 10-06-2022 08:00, M. Zhou wrote: There are some compilation flags tweakable. I'll try with qemu to see whether I can make it work. I tried to tweak some compilation flags, and did not manage to make it work on ppc64el (qemu), even if I use the -DLUAJIT_DISABLE_JIT macro. Segfault per

Bug#1012362: transition: luajit

Hi Mo, On 13-06-2022 05:20, M. Zhou wrote: So let's inform the reverse dependencies to remove ppc64el support, or switch back to lua. Just curious, have you already done so? If yes, care to share the bug report numbers? Otherwise I assume you expected me to file those bugs? Paul elbrus@coc

Bug#1011272: nvidia-graphics-drivers-legacy-390xx 390.151-1~deb10u1 flagged for acceptance

Dear Andreas, On 19-06-2022 18:54, Adam D Barratt wrote: The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: nvidia-graphics-drivers-legacy-390xx Versi

Bug#1014460: transition: php8.2

Control: forwarded -1 https://release.debian.org/transitions/html/php8.2.html Hi Ondřej, On 06-07-2022 16:05, Ondřej Surý wrote: to prevent the situation from the last time, I am kind of "starting" the transition to PHP 8.2 now with PHP 8.2.0~alpha2. I will be uploading packages to experiment

Bug#1016287: closed by Paul Gevers (Re: Bug#1016287: release.debian.org: autopkgtest 2 to 5 days since addition of armel)

Hi Jérémy. On 29-07-2022 22:17, Jérémy Lal wrote: I don't see how artificially adding migration days will improve debian quality in any way. We're not adding days, we're just not giving the bounty for success on all architectures where we run autopkgtests, which was the rule for the bounty.

Bug#1015270: transition: nodejs

Hi Jérémy. On 22-07-2022 14:51, Graham Inggs wrote: On Mon, 18 Jul 2022 at 19:09, Jérémy Lal wrote: nodejs 18.6.0 will soon be the active version of nodejs: https://nodejs.org/en/about/releases/ I rebuilt and checked all reverse-build-deps of libnode-dev/nodejs, and dealt with most of the reg

Bug#1015270: transition: nodejs

Hi Jérémy, On 29-07-2022 22:47, Jérémy Lal wrote: All seems to be well on its way, with the exception of the autopkgtest failure of node-babel7 on ppc64el. Did you already have a look at that? I can file the bug against node-babel7 if you want. v8 clearly crashes on ppc64el here w

Bug#1016287: closed by Paul Gevers (Re: Bug#1016287: release.debian.org: autopkgtest 2 to 5 days since addition of armel)

Control: reopen -1 Control: retitle -1 britney recursive installability test in autopkgtest Hi Yadd, On 30-07-2022 15:58, Yadd wrote: Node.js isn't available on armel, and the consequence will be to not fix some CVEs/BTS during freeze. Hope none of them will appear... For those we have unbloc

Bug#1016496: nmu: abinit_9.6.2-1

Hi Bas, On 01-08-2022 22:18, Bas Couwenberg wrote: nmu abinit_9.6.2-1 . ANY . unstable . -m "Rebuild with libnetcdff7 (>= 4.6.0+ds-1)" To resolve the autopkgtest failure reported in #1016414, the package needs to be rebuilt. That normally means it's papering over the real issue. Are you sur

Re: linux migration to testing

Hi Ben, On 01-08-2022 22:46, Ben Hutchings wrote: linux 5.18.14-1 is currently blocked from migration due to a test regression on some architectures. This is actually not a regression: there's a new test case, and it was defined wrongly for architectures other than amd64 and arm64. That should

Re: linux migration to testing

Hi Ben, On 01-08-2022 23:09, Ben Hutchings wrote: On Mon, 2022-08-01 at 22:53 +0200, Paul Gevers wrote: On 01-08-2022 22:46, Ben Hutchings wrote: Could you please allow this version to enter testing despite the test failures? If you promise to fix it in the next upload. Yes, the fix is

Re: linux migration to testing

Hi Ben, On 18-08-2022 23:09, Ben Hutchings wrote: For your info, s390x still fails: https://ci.debian.net/data/autopkgtest/testing/s390x/l/linux/24628411/log.gz Also for ppc64el. I noticed right after sending. These two are fixed by: https://salsa.debian.org/kernel-team/linux/-/commit/8d43

Re: Please assert severity of bug#1017441 (debhelper: building src:shadow wrongly makes passwd depend on systemd | systemd-tmpfiles)

Hi Niels, all, On 20-08-2022 16:52, Niels Thykier wrote: The question is whether you feel this is an RC bug and would like me to revert the change immediately / before the transition freeze?   The alternative is you do not feel this bug is concerning/RC in which case I will keep the current ve

Bug#1017926: RM: node-request-capture-har/1.2.2-2

Hi Yadd, On 22-08-2022 17:31, Yadd wrote: node-request-capture-har is a wrapper around deprecated node-request (#1002901). Its reverse-dependency (node-yarnpkg) has already been removed from testing. Could you remove it from testing ? Maybe elaborate why from testing only and not from unstabl

Bug#1017925: RM: node-request/2.88.1-5

Control: tags -1 moreinfo Hi Yadd, On 22-08-2022 17:26, Yadd wrote: could you remove node-request from testing ? Following #956423, it shouldn't be part of next stable release. All its reverse dependencies are already removed from testing (yarnpkg, node-matrix-sdk). node-request is a build-de

Bug#1010660: britney: Crash with RecursionError: maximum recursion depth exceeded

Hi, tl;dr: we need to cook up a similar patch as bd375fdd85b4e00b89fb087760369bb6f3df0a20 for the migration phase of britney. We recently experienced this problem in Debian too. Traceback (most recent call last): File "/srv/release.debian.org/britney/code/b2/britney.py", line 1586, in

Bug#1018076: transition: gjs and gnome-shell likely to be removed from armel

Hi Simon, all, On 30-08-2022 14:48, Simon McVittie wrote: If armel is a candidate for being a release architecture, then I think that leaves two-and-a-half options: In the last couple of releases, we have been bad at taking decisions on this front, so lets assume it is (although this issue is

Bug#1018076: transition: gjs and gnome-shell likely to be removed from armel

Hi, On 30-08-2022 22:20, Paul Gevers wrote: [...] For avoidance of doubt, I didn't ACK or NACK the transition. I just wanted to answer Simon's question about the course of solutions. Paul OpenPGP_signature Description: OpenPGP digital signature

Opinion on splitting official architecture (tiers)

Dear DSA, ftp-master, release team, As you are probably aware, architecture qualification is a notorious hard problem for the Release Team and the project. This year at DebConf, we have been discussing [1,2] a potential change in the way we look at the (release) architectures. Although my orig

Bug#1017740: transition: draco

Hi Timo, On 04-09-2022 22:41, Timo Röhling wrote: the draco transition looks stuck because of the failing autopkgtest with assimp from testing and draco from unstable. That failure is caused by the renamed CMake target for the draco library (now "draco::draco" instead of "draco_shared"). The ta

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

Re: Bug#1019335: Reconsider the egrep and fgrep deprecation

Hi all, For transparency I'm letting you know that, with my Release Team manager hat on, I have just added a migration block on grep. On Wed, 7 Sep 2022 17:39:45 +0200 Santiago Ruano =?iso-8859-1?Q?Rinc=F3n?= wrote: For the moment, I am waiting for (a final) upstream input about those warni

Re: Opinion on splitting official architecture (tiers)

Hi all, On 01-09-2022 14:18, Paul Gevers wrote: Of course there are details to figure out and agree on, but before diving into those I'd like to hear if you are open to support the idea (hopefully even in time for bookworm) or if there are already deep concerns (that would take lo

Re: Opinion on splitting official architecture (tiers)

Hi, On 08-09-2022 13:59, Sebastian Ramacher wrote: So, maybe my main question is: if we don't consider issues on these semi-supported architectures RC but they have a testing equivalent, why don't the other ports architectures get the same treatment? Fair question. One big reason is that the s

Re: Opinion on splitting official architecture (tiers)

Hi, On 08-09-2022 22:14, Pierre-Elliott Bécue wrote: Would tier II be exclusively composed of builders that are currently supported by DSA? My current proposal is ONLY about splitting the current release architectures. And for the future, my idea for tier II (or Best Effort) would indeed be

Re: Remove me from list

Hi, On 11-09-2022 17:16, bleisur wrote: Please remove my my email from your list ..thank you There's not many people that can do that, but you are one of them. The headers of e-mails to this list have this: List-Unsubscribe:

Re: Question about modsecurity-crs package upgrade

Hi, Sorry for the delay in responding. This list is very high volume (it receives bug reports too) and plain messages sometimes slip through. On 02-09-2022 14:35, Ervin Hegedüs wrote: *We need to know if we could add this patch to the existing packages (3.3 in both Debian 10 and Debian 11) wi

Re: Bug#1019724: warning: stray \ before - causes autopkgtest failure

Hi Santiago, Lucas, On 14-09-2022 17:31, Santiago Ruano Rincón wrote: Note that the release team issued a block for now: https://release.debian.org/britney/hints/jcristau and proposed to test with a archive rebuild before introducing it again. Dear Release Team, just to be sure of being on

Re: Bug#1019724: warning: stray \ before - causes autopkgtest failure

Hi all, On 15-09-2022 09:26, Paul Gevers wrote: I am trying to schedule autopkgtests in unstable on amd64 for all source packages that have one. And the first results are coming in. I'm not sure how to proceed though, see below. Lucas, are you in the position to do an archive rebui

Re: Bug#1019724: warning: stray \ before - causes autopkgtest failure

Hi Santiago, On 15-09-2022 09:26, Paul Gevers wrote: I am trying to schedule autopkgtests in unstable on amd64 for all source packages that have one. All results are now in. Only several test failed due this warning: the known dpkg and cjet and the newly found nagios-plugins-contrib

Re: Status of Debian Installer Bookworm Alpha 1: 2 blockers

Hi kibi, On 17-09-2022 01:41, Cyril Brulebois wrote: A few questions I can think of: - Is that a good idea in the first place? I think so, sidestepping temporary issues in unstable looks like a valid usecase? AFAIK that *is* the most common use of tpu these days (getting things into tes

Bug#1020413: nmu: bind-dyndb-ldap_11.6-3

Hi, On 22-09-2022 20:38, Salvatore Bonaccorso wrote: I honestly don't know because I don't use this package, but I think it might prevent the users using the bind-dyndb-ldap users from upgrading the bind9 package. Why is this binNMU actually needed? bind9-dyndb-ldap has the following: Depend

Re: Migration problem

Hi, On 11-10-2022 18:56, Adam D. Barratt wrote: * Replace component by dependency: cjs-module-lexer (Closes: #1019355) I have hinted node-cjs-module-lexer (as the test fails because of unavailable test dependency, which isn't something an arch:all package should fix) assuming that has the

Bug#1014460: transition: php8.2

Hi all, On 22-10-2022 16:25, David Prévot wrote: There are still over twenty packages that need fixing in the Horde camp, probably most of them could use a “Restrictions: allow-stderr” workaround in debian/tests/control. @horde team, do you think you can work on these deprecation warnings in

Re: Processed: autopkgtest regressions are RC (and this one also blocks the perl transition)

Hi Hilmar, On 23-10-2022 12:15, Hilmar Preuße wrote: Am 22.10.2022 um 10:21 teilte Debian Bug Tracking System mit: the breakage is not caused by the perl upload, but due to the latest TeX Live upload at the beginning of this month. Hence TL either does not migrate to testing (which is good in

Re: Processed: autopkgtest regressions are RC (and this one also blocks the perl transition)

Hi, On 24-10-2022 12:00, Adrian Bunk wrote: On Sun, Oct 23, 2022 at 12:35:41PM +0200, Paul Gevers wrote: We'll handle it somehow yes. It seems someone already handled it or it disappeared by itself. Yes, I scheduled the tests with *less* packages from unstable than britney and

Re: bullseye-ignore for embedding different paths if built on merged-/usr systems?

Hi, On 10-11-2022 11:45, Andreas Beckmann wrote: since bullseye mandates that buildd chroots are non-merged-/usr, can we tag bugs about binaries differing (by embedding different paths to "found binaries") when built on merged-/usr systems as bullseye-ignore? I think it depends. What happens

Re: bullseye-ignore for embedding different paths if built on merged-/usr systems?

Hi Andreas, On 10-11-2022 13:50, Andreas Beckmann wrote: On 10-11-2022 11:45, Andreas Beckmann wrote: since bullseye mandates that buildd chroots are non-merged-/usr, can we tag bugs about binaries differing (by embedding different paths to "found binaries") when built on merged-/usr systems a

Bug#1023787: transition: liblxqt

Dear LXQt maintainers, On 10-11-2022 07:56, plugwash wrote: It appears a liblxqt transition has started, possiblly inadvertantly. Back in June, Simon Quigley prepared an update of the lxqt stack. He announced that he intended to update the stack in unstable, but only actually did so in experime

Bug#1023495: transition: ruby3.1

Hi Lucas, On 22-11-2022 17:03, Lucas Kanashiro wrote: After discussing with Antonio, since our deadline to finish the transition is approaching, we decided to already enable ruby3.1 as the default and remove ruby3.0 in a single step. I may be remembering wrong (it's a bit late), but isn't the

Bug#1023787: transition: liblxqt

Hi, On 21-11-2022 01:05, ChangZhuo Chen (陳昌倬) wrote: All affected packages have been uploaded to unstable. Sorry for the mess. Thanks. Let's see if they can migrate on their own to testing in the following days. Paul OpenPGP_signature Description: OpenPGP digital signature

Bug#1023846: transition: gdal

Hi Bas, On 22-11-2022 11:26, Sebastiaan Couwenberg wrote: How can we schedule autopkgtest runs for testing with gdal & libgdal-grass from unstable? Most of the time britney and autopkgtest handle it automatically if dependencies are rightly versioned (although not ideally during transitions)

Bug#1023846: transition: gdal

Hi Bas, On 23-11-2022 05:28, Sebastiaan Couwenberg wrote: The libgdal-grass autopkgtest in testing is failing because it requires gdal, grass, and libgdal-grass from unstable.  https://qa.debian.org/excuses.php?package=gdal This combination needs to be tested to fix the regressions shown and

Re: Help understanding why a package isn't migrating

Hi Scott, On 23-11-2022 15:26, Scott Talbert wrote: Hi Release Team, I'm trying to understand why this package (haskell-copilot-theorem[1]) isn't migrating to testing.  It looks like it is saying that it is being blocked by haskell-what4, but haskell-what4 has already migrated to testing on

Bug#1023550: transition: qcustomplot

Hi On 24-11-2022 21:59, Filippo Rusconi wrote: It is weeks that I monitor the salsa stuff, but I do not understand what these tests mean. One example (bear with me): CMake Error at CMakeLists.txt:5 (FIND_PACKAGE):   By not providing "FindQt5PrintSupport.cmake" in CMAKE_MODULE_PATH this   pro

Bug#1023787: transition: liblxqt

Hi, On 28-11-2022 17:50, ChangZhuo Chen (陳昌倬) wrote: On Tue, Nov 22, 2022 at 09:58:48PM +0100, Paul Gevers wrote: Hi, On 21-11-2022 01:05, ChangZhuo Chen (陳昌倬) wrote: All affected packages have been uploaded to unstable. Sorry for the mess. Thanks. Let's see if they can migrate on

Bug#1023731: Any idea why debci picks old versions (Was: Bug#1023731: BioC Transition blocked by new dependencies)

Hi Andreas, On 28-11-2022 13:22, Andreas Tille wrote: I'm constantly checking the tracker page of r-bioc-biocgenerics[1] to follow the transition status. I realised that debci picks old, not yet fixed package versions like: r-bioc-biocfilecache/2.4.0+dfsg-1 while 2.4.0+dfsg-2 is in unstable

Bug#1022122: node-minimatch 3.0.4+~3.0.3-1+deb11u1 flagged for acceptance

Hi Yadd, On Sat, 26 Nov 2022 13:01:22 + Adam D Barratt wrote: 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: node-minimatch Version: 3.0.4

Bug#1023787: transition: liblxqt

Hi ChangZhuo, On 29-11-2022 06:29, ChangZhuo Chen (陳昌倬) wrote: Please help to migrate libfm-qt in new queue [0] so that we can prepare the migration. That's not under our control. You'll need to talk to ftp-master (typically a note with explanation on IRC helps). Paul OpenPGP_signature De

Bug#1023787: transition: liblxqt

Hi ChangZhuo, On 03-12-2022 17:19, ChangZhuo Chen (陳昌倬) wrote: On Tue, Nov 29, 2022 at 07:33:11PM +0100, Paul Gevers wrote: Do we need to submit transition for lxqt-globalkeys [0], which is totally covered by liblxqt transition? What we need is coordination, which is why transition bugs need

Bug#1023731: BioC Packages are now clean (one exception with RC bug filed) (Was: Bug#1023731: Any idea why debci picks old versions)

Hi Andreas, On 29-11-2022 10:26, Andreas Tille wrote: Now there is only one remaining one which is a real problem which I have reported upstream (see bug #1025045). If r-bioc-structuralvariantannotation would be removed from testing I do not see any blocker for the transition any more. I remo

Bug#1026199: release.debian.org: Is the toolchain list updated for bookworm

Dear Sam, On 16-12-2022 02:40, Sam Hartman wrote: I was looking at https://release.debian.org/testing/essential-and-build-essential.txt trying to figure out which packages I'm involved in are covered by the toolchain freeze. I am wondering what's still pulling libgssapi-krb5-2 and friends int

Bug#1026199: release.debian.org: Is the toolchain list updated for bookworm

Hi Holger, On 17-12-2022 12:50, Holger Levsen wrote: On Sat, Dec 17, 2022 at 08:42:18AM +0100, Paul Gevers wrote: I just refreshed the list, it's still there. I used a script on udd, essentially this: [...] query = "SELECT DISTINCT package FROM packages WHERE release = 

Re: Migrating golang-github-smallstep-certificates 0.19.0-1 to testing

Hi Peymaneh On 18-12-2022 22:06, Peymaneh wrote: I have uploaded 0.19.0-1 of golang-github-smallstep-certificates[1] to unstable which cannot move to testing, because its build dependencies[2][3] are stuck in unstable. Its build dependencies are stuck because they cause regressions for autopkg

Re: Migrating golang-github-smallstep-certificates 0.19.0-1 to testing

Hi, On 18-12-2022 22:35, Peymaneh wrote: Those are only autopkgtest regressions Manually scheduled. Paul OpenPGP_signature Description: OpenPGP digital signature

Bug#1022573: transition: procps

Dear Craig, ChangZhuo, This is a heads up that I just added a block against procps to prevent the package in unstable from migrating to testing too soon. The issue is that src:intel-gpu-tools is a key packages but currently unfixed. Having procps migrate to testing now would cause it to be i

Bug#1014460: [pkg-php-pear] Bug#1014460: transition: php8.2

Control: tags -1 confirmed Dear Ondřej, On 15-12-2022 20:15, Ondřej Surý wrote: I think everything is mostly ready in experimental. I'll try to sort out the rest of the missing extensions over the weekend (imagick, memcached, redis and maybe few others). Assuming this happened (more or less).

Bug#1022573: transition: procps

Hi, On 21-12-2022 21:42, Craig Small wrote: Is there something else you need? This one was one of the easier ones to fix. An actual upload. If the maintainer isn't doing it, I think an NMU is appropriate if you're sure of the fix. Paul OpenPGP_signature Description: OpenPGP digital signat

Bug#1022573: transition: procps

Hi Craig, On 22-12-2022 00:28, Craig Small wrote: BUT, procps is in transition and this linking needs to happen before the first freeze milestone so I will upload 20220525 linked to libproc2 if we get near to running out of time. That's (in general) sub-optimal for the release team. We try ha

Bug#1026794: nmu: logol_1.7.9+dfsg-6

Control: tag -1 moreinfo On 21-12-2022 09:49, Lev Lamberov wrote: Please, binNMU logol 1.7.9+dfsg-6 (currently in unstable) against swi-prolog 9.0.3+dfsg-1 (currently in unstable) to fix autopkgtests failures and make transition to testing possible. The version of logol in unstable passes its

Bug#1027022: RM: puppet-beaker/4.30.0-2

Hi Lucas, On 26-12-2022 14:55, Lucas Nussbaum wrote: Please remove puppet-beaker from testing. Normally that's handled by requesting removal from unstable as removal there is synced to testing. It is orphaned, broken, outdated compared to upstream, and blocks the migration of ruby-net-scp

Bug#1022573: transition: procps

Hi Craig, With procps migrated to testing, dose [1] is reporting two more packages that weren't on our radar: open-vm-tools and guymager. Can you have a look and help the maintainer with migrating to the new version of procps? open-vm-tools has a new version in unstable that's now unable to m

Re: Understanding what is blocking spamassassin 4.0.0 testing migration

Hi Andreas, On 29-12-2022 07:21, Andreas Metzler wrote: I do not understand why spamassassin 4.0.0 does not prpagate to testing. Tracker/excuses https://qa.debian.org/excuses.php?package=spamassassin says: Issues preventing migration: [...] removing spamassassin/4.0.0~rc4-1/amd64 from testi

Bug#1022573: transition: procps

Hi Craig, On 31-12-2022 06:45, Craig Small wrote: Looks like old dependencies so the removal of libprocps-dev from their build dependency line in control is all that is needed. I can do that, or the respective maintainers can. Thanks for updating the respective bugs (thanks to Peter). Paul

Bug#1027424: transition: libppd

Control: tag -1 moreinfo Hi Christoph, On 31-12-2022 10:06, Christoph Biedl wrote: possible this is not a regular transition, but in exchange I guess it should be pretty smooth and simple ... Inside the Debian archive maybe, but ... So src:libppd has been renamed to src:libppd-legacy, and h

extra irc meeting?

Dear colleagues, Some of us had the idea to plan an extra IRC meeting before the first milestone in the bookworm release. Finding a good slot is probably going to be awkward, but let's try. If I understood correctly, this week is not great for Sebastian and it's not great for me either. Which

Bug#1027856: RM: wesnoth-1.14/1:1.14.17-2

Hi Vincent, On 04-01-2023 07:47, Vincent Cheng wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm src:wesnoth-1.14 has been superseded by wesnoth-1.16; please remove the former from the archive. Thanks! If you want it removed from the

Bug#1027127: transition: zxing-cpp

Hi, On 03-01-2023 17:29, Andreas Beckmann wrote: nmu mediastreamer2_1:5.2.0+dfsg-1 . ANY . experimental . -m "Rebuild against libzxing2" scheduled. Paul OpenPGP_signature Description: OpenPGP digital signature

Bug#1014460: [pkg-php-pear] Bug#1014460: transition: php8.2

Hi Ondřej, On 21-12-2022 21:28, Paul Gevers wrote: The bump from 8.x to 8.2 is relatively painless, so can we schedule the transition in few days/weeks? Please go ahead. Ping. In a week from now, the Transition and Toolchain freeze starts [1]. The upload should happen before then

SONAME bumps (transitions) always via experimental

Dear all, The Release Team just asked ftp-master to hold of accepting SONAME bumps targeting unstable to ease the last days before the Transition and Toolchain Freeze. The Release Team would like to ask the ftp-masters to also by default reject SONAME bump NEW uploads to unstable during the w

Re: SONAME bumps (transitions) always via experimental

Hi, On 05-01-2023 14:13, Simon McVittie wrote: since passing NEW currently requires a source+binary upload but migrating to testing requires a follow-up source-only upload (same total number of uploads). To be fair, normal SONAME bump NEW uploads only need a arch:!all binary uploa

Bug#1026825: python3.11 as default

Hi, On 06-01-2023 07:39, Sebastiaan Couwenberg wrote: What's your plan to deal with these entanglements? I have bumped the priority of php8.2 on ppc64el and s390x as a start. Paul OpenPGP_signature Description: OpenPGP digital signature

Bug#1004441: unblocking chromium?

Dear Chromium team, Security team, On 27-01-2022 17:15, Moritz Muehlenhoff wrote: On Wed, Jan 26, 2022 at 09:38:42PM +0100, Paul Gevers wrote: So, I'm proposing the following: we unblock chromium from testing, with the understanding that prior to bookworm's release, we have a discu

Bug#1014460: [pkg-php-pear] Bug#1014460: transition: php8.2

Control: severity 1023370 serious Control: severity 1023381 serious Hi Ondřej, On 08-01-2023 07:38, Sebastiaan Couwenberg wrote: On 12/15/22 20:15, Ondřej Surý wrote: I think everything is mostly ready in experimental. I'll try to sort out the rest of the missing extensions over the weekend (i

Bug#1004441: unblocking chromium?

Control: close 1004441 Hi, On 10-01-2023 21:05, Moritz Mühlenhoff wrote: Sounds good! Can you add a README.Debian.security to the next unstable uploads which briefly documents that? When bookworm has been released we can also add a note to Chromium DSAs to give folks a headsup. So, it sounds

Bug#1014460: [pkg-php-pear] Bug#1014460: transition: php8.2

Hi Ondřej, On 11-01-2023 20:42, Ondřej Surý wrote: Now, what should I do about: • Not built on buildd: arch amd64 binaries uploaded by ondrej • Not built on buildd: arch all binaries uploaded by ondrej, a new source-only upload is needed to allow migration Do I really have to reuplo

Re: Bug#1020413: nmu: bind-dyndb-ldap_11.6-3

Hi, On 12-01-2023 09:12, Ondřej Surý wrote: as bind-dyndb-ldap would be removed on 25th of january, which then should unblock the bind9 situation for unstable/bookworm AFAIU, should we ask for removal already earlier? Should it be kept at all, is it used? (popcon seems quite low, but that is not

Bug#1014460: transition: php8.2

Hi Mike and other Horde maintainers, On 22-10-2022 17:31, Mike Gabriel wrote: For Horde, getting autopkgtests resolved (and packages migrate to testing) is one thing, but getting all of Horde deprecation-warnings-free with php8.2 at run time is a completely different cup of team. (Horde upstre

Bug#1028452: unblock: golang-1.19/1.19.5-1

Hi Shengjing, On 11-01-2023 09:32, Shengjing Zhu wrote: Please unblock package golang-1.19 But golang-1.19 is in sync between unstable and testing. This is a point release for golang 1.19 which happens today. I suspect you're asking for an exception as golang is on our toolchain list [0]?

Bug#1028452: unblock: golang-1.19/1.19.5-1

Hi Security team, We stumbled upon golang... On 12-01-2023 16:50, Shengjing Zhu wrote: But this bug report triggered me: did the golang security situation already improved during this release cycle. I may be misremembering, but I recall the problems on the security archive side haven't been fix

Re: Bug#1020413: nmu: bind-dyndb-ldap_11.6-3

Hi, On 13-01-2023 10:04, Ondřej Surý wrote: we should also remove bind-dyndb-ldap from stable and add `Breaks: bind-dyndb-ldap (<< 11.10-2~)` to the next src:bind9 stable upload. Please file a bug report with the right usertags (reportbug is your friend) such that our SRM don't forget to remo

Re: Bug#1028451: 2nd DisplayPort doesn't get video

Hi, On 17-01-2023 07:14, Salvatore Bonaccorso wrote: I will bite the bullet (taking full responsibility for it if necessary, don't blame the other kernel team members) and ask here now the release team: Can we let linux 6.1.4-1 despite the RC bug reported, migrate to testing, so we can move on t

Bug#1014460: [pkg-php-pear] Bug#1014460: transition: php8.2

Hi Ondřej, On 08-01-2023 22:41, Ondřej Surý wrote: The Breaks have been added there since the last transition - there was a tendency for the apt dependency solver to pick one package (say php-imagick) from old PHP version and other one from new PHP version (say php-mysql). The Breaks was the

Bug#1028452: unblock: golang-1.19/1.19.5-1

Hi, On 19-01-2023 03:17, Shengjing Zhu wrote: Sorry not to make it clear. It's a pre-approval request. Sorry from my side too, I forgot the context and only looked at the subject and my first reply... (There was an other unblock request that didn't require any action and I thought it was thi

Bug#1028452: unblock: golang-1.19/1.19.5-1

Dear Shengjing, On 11-01-2023 09:32, Shengjing Zhu wrote: This is a point release for golang 1.19 which happens today. Where can I find the upstream policy on point release updates? Or, if not documented in one place, can you describe it? Is 1.19 a bug-fix only branch already, or are new fea

Bug#1028915: [pre-approve] unblock: rustc/1.63.0+dfsg1-2

Control: tag -1 confirmed Hi Fabian, On 14-01-2023 22:39, Fabian Grünbichler wrote: This request is for pre-approval of a not-yet-uploaded fixed version of rustc. Please go ahead with uploading 1.63.0+dfsg1-2. Paul OpenPGP_signature Description: OpenPGP digital signature

Bug#1028452: unblock: golang-1.19/1.19.5-1

Control: tag -1 confirmed Hi, On 19-01-2023 10:22, Shengjing Zhu wrote: On Thu, Jan 19, 2023 at 4:55 PM Paul Gevers wrote: On 11-01-2023 09:32, Shengjing Zhu wrote: This is a point release for golang 1.19 which happens today. Where can I find the upstream policy on point release updates

Bug#931245: unblock: encoding-rs/0.8.15-2

reopen 931245 retitle 931245 buster-pu: package rust-encoding-rs/0.8.15-2~deb10u1 ? user release.debian@packages.debian.org usertags 931245 - unblock usertags 931245 pu thanks On Sat, 27 Jul 2019 08:44:16 +0200 Salvatore Bonaccorso wrote: > > I think you just can recycle this one (and update

Bug#933043: Acknowledgement (nmu: petsc_3.10.5+dfsg1-1)

Hi Drew, On 29-07-2019 21:11, Paul Gevers wrote: > On 28-07-2019 14:23, Drew Parsons wrote: >> nmu petsc_3.10.5+dfsg1-1 . ANY . unstable . -m "rebuild against hypre >> 2.16.0" >> >> and after that, >> >> nmu slepc_3.10.2+dfsg1-1 . ANY . unsta

Bug#933595: transition: pkg-js-tools

Control: tags -1 moreinfo Hi Xavier, On 31-07-2019 22:25, Xavier Guimard wrote: > pkg-js-tools provides a debhelper plugin that handles "dh --with > nodejs". Until 0.7, it was used for dh_auto_test. Since version 0.8.6, it > provides a dh_auto_install hooks that permits to automatically install >

Bug#903211: Checking for removal of BD [was Re: release.debian.org: How to handle unbuildable packages in buster]

Hi all, On Thu, 09 Aug 2018 09:32:00 + Niels Thykier wrote: > 3) Build-Depends are not enforced on removal. That is packages > /can/ be removed while packages are build depending on them. > > Limitation 2+3 are slightly more involved and may take quite a while for > us to implement. S

Re: Bits from the Release Team: ride like the wind, Bullseye!

Hi Stéphane, On 02-08-2019 05:38, Stéphane Glondu wrote: > Le 07/07/2019 à 03:47, Jonathan Wiltshire a écrit : >> No binary maintainer uploads for bullseye >> = >> >> The release of buster also means the bullseye release cycle is about to >> begin. >> From

Bug#933623: transition: petsc

Control: forwarded -1 https://release.debian.org/transitions/html/auto-petsc.html Control: tags -1 pending Hi Drew, On 01-08-2019 05:45, Drew Parsons wrote: > The hypre 2.16.0 upgrade revealed an incompatibility between petsc 3.10 > and hypre 2.16.0. PETSc upstream has dealt with the issue with

Re: Bits from the Release Team: ride like the wind, Bullseye!

Hi, On 07-08-2019 16:57, Ian Jackson wrote: > Lisandro Damián Nicanor Pérez Meyer writes ("Re: Bits from the Release Team: > ride like the wind, Bullseye!"): >> No, what I have been perceiving (and pretty please note that this is my >> personal "feeling") is that maintainers, specially library ma

Bug#933623: transition: petsc

Hi Esa, Drew, On 12-08-2019 14:40, Esa Peuha wrote: > This transition isn't quite complete yet; src:freefem++ still > build-depends on libpetsc-{real,complex}3.10-dev. This isn't something that the release team handles as this requires sourceful uploads. So, Drew, can you please handle this (I pr

Re: #932795 - Setting up minimum build system expectations?

Hi Gunnar, Disclaimer, I haven't discussed this with the team, so what I write here is my personal perception and opinion. On 11-08-2019 05:26, Gunnar Wolf wrote: > Dear Release Team members, I am reaching out to see what is your > position regarding bug #932795, which in turn references > #90782

<    2   3   4   5   6   7   8   9   10   11   >