Bug#992759: nmu: tagua_1.0~alpha2-16-g618c6a0-3

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: debian-qt-...@lists.debian.org Hi, please rebuild tagua in unstable against the libkdegames recently uploaded. tagua builds fine with the newer libkdegames. nmu tagua_1.0~alph

Bug#992758: nmu: calamares_3.2.36-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: debian-qt-...@lists.debian.org Hi, please rebuild calamares in unstable against the newer kpmcore recently uploaded. calamares builds fine with the newer kpmcore. nmu calamare

Bug#992757: nmu: qtwebview-opensource-src_5.15.2-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: debian-qt-...@lists.debian.org Hi, please rebuild qtwebview-opensource-src in unstable for the new qtwebengine 5.15.5 recently uploaded, so it depends on the new internal ABI d

Re: careless upload of Erlang v24 without a transition tracking with the release team (was: rabbitmq-server fails to start after erlang v24 update)

On 8/22/21 8:57 PM, Adrian Bunk wrote: > On Sun, Aug 22, 2021 at 07:14:16PM +0200, Thomas Goirand wrote: >> ... >> On 8/22/21 6:14 PM, Sergei Golovan wrote: >> ... >>> I've uploaded Erlang 24 to experimental months ago. If you know that >>> your software breaks on Erlang upgrade, you could do somet

Bug#992693: bullseye-pu: package glibc/2.31-13+deb11u1

Hi, On 22-08-2021 14:58, Aurelien Jarno wrote: > The alternative is to read the release notes and upgrade openssh-server > before upgrading the full system. That would be this paragraph: https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#ssh-not-available It woul

Re: careless upload of Erlang v24 without a transition tracking with the release team (was: rabbitmq-server fails to start after erlang v24 update)

On Sun, Aug 22, 2021 at 07:14:16PM +0200, Thomas Goirand wrote: >... > On 8/22/21 6:14 PM, Sergei Golovan wrote: >... > > I've uploaded Erlang 24 to experimental months ago. If you know that > > your software breaks on Erlang upgrade, you could do something > > already. > > Just uploading to Exper

Bug#992028: transition: libidn

> Please go ahead Thank you -- I have uploaded it now. When it is a good time to close this bug? I don't see anything on https://wiki.debian.org/Teams/ReleaseTeam/Transitions - should I keep it open until the entire transition has been completed? /Simon

Bug#992570: marked as done (nmu: rebuild on buildd for testing migration)

Your message dated Sun, 22 Aug 2021 19:30:36 +0200 with message-id and subject line Re: Bug#992570: nmu: rebuild on buildd for testing migration has caused the Debian Bug report #992570, regarding nmu: rebuild on buildd for testing migration to be marked as done. This means that you claim that th

Re: careless upload of Erlang v24 without a transition tracking with the release team (was: rabbitmq-server fails to start after erlang v24 update)

Hi Sergei, Thanks for your quick reply. On 8/22/21 6:14 PM, Sergei Golovan wrote: > Hi Thomas, > > On Sun, Aug 22, 2021 at 6:55 PM Thomas Goirand wrote: >> >> Hi Damir, Sergei, the release team, >> >> First of all, thanks for your bug report, Damir. >> >> Debian Bullseye was released on the 14t

Re: careless upload of Erlang v24 without a transition tracking with the release team (was: rabbitmq-server fails to start after erlang v24 update)

Hi Thomas, On Sun, Aug 22, 2021 at 6:55 PM Thomas Goirand wrote: > > Hi Damir, Sergei, the release team, > > First of all, thanks for your bug report, Damir. > > Debian Bullseye was released on the 14th of Aug. Then Erlang v24 was > uploaded on the 17th. Looking at: > > https://release.debian.org

Bug#992028: transition: libidn

On 2021-08-22 15:47:43 +0200, Simon Josefsson wrote: > > Please go ahead > > Thank you -- I have uploaded it now. When it is a good time to close > this bug? I don't see anything on > https://wiki.debian.org/Teams/ReleaseTeam/Transitions - should I keep > it open until the entire transition has

Re: careless upload of Erlang v24 without a transition tracking with the release team (was: rabbitmq-server fails to start after erlang v24 update)

Hi Damir, Sergei, the release team, First of all, thanks for your bug report, Damir. Debian Bullseye was released on the 14th of Aug. Then Erlang v24 was uploaded on the 17th. Looking at: https://release.debian.org/transitions/ I cannot see any transition thingy opened for Erlang. This means th

Processed: Re: Bug#992028: transition: libidn

Processing control commands: > tags -1 confirmed Bug #992028 [release.debian.org] transition: libidn Added tag(s) confirmed. -- 992028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#992028: transition: libidn

Control: tags -1 confirmed Hi Simon On 2021-08-09 13:22:49, Simon Josefsson wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: transition > > Hello, > > I want to transition libidn to a newer upstream version, and they > API/ABI bumped. This is my f

Bug#992693: bullseye-pu: package glibc/2.31-13+deb11u1

Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: debian-gl...@lists.debian.org [ Reason ] During the upgrade from Buster to Bullseye, the SSH server is not restarted following the libc6 upgrade, causing new SSH conn

Bug#992688: marked as done (nmu: tor_0.4.5.10-1)

Your message dated Sun, 22 Aug 2021 14:24:31 +0200 with message-id <77dfda1d-505c-51d2-84f7-e508bdd3b...@thykier.net> and subject line Re: nmu: tor_0.4.5.10-1 has caused the Debian Bug report #992688, regarding nmu: tor_0.4.5.10-1 to be marked as done. This means that you claim that the problem ha

Bug#992688: nmu: tor_0.4.5.10-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu tor_0.4.5.10-1 . ANY . unstable . -m "Rebuild against new debhelper (cf: #992554)." Please rebuild tor in unstable with debhelper >= 13.4.1 to actually fix (the fallout of) #992554 (de