Bug#1028246: transition: liquid-dsp

On Sun, Jan 08, 2023 at 11:47:42PM +0200, Adrian Bunk wrote: > On Sun, Jan 08, 2023 at 10:11:46PM +0100, Andreas Bombe wrote: > >... > > i386 only, where some > > floats don't match exactly, which I'm still investigating. > >... > > That's "better" results due to x87 excess precison. > > The

Re: SONAME bumps (transitions) always via experimental

> "Graham" == Graham Inggs writes: Graham> Hi All Graham> On Fri, 6 Jan 2023 at 00:33, Bastian Blank wrote: Graham> Would it be a bad thing to require all uploads that need to Graham> go through NEW (source and binary) to target experimental? Graham> I have been doing

Processed: tagging 1028052

Processing commands for cont...@bugs.debian.org: > tags 1028052 + confirmed Bug #1028052 [release.debian.org] transition: pcl Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1028052:

Bug#1009659: bullseye-pu: package spyder/4.2.1+dfsg1-3

On Sat, May 28, 2022 at 08:45:28PM +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Wed, 2022-04-13 at 19:46 +0100, Julian Gilbey wrote: > > The bug is reported in https://bugs.debian.org/989660 > > I didn't spot it at the time because I'm only an uploader, not the > > named

Bug#1027686: transition: rakudo

I missed the detail that the compiler ID even changes for different architecture.. which may not be good. Is it possible for us to slightly modify the postinst script to recompile the cache locally when the compiler id mismatches? The fallback script rakudo-helper.pl can at least make sure a

Bug#1027746: transition: log4cxx

Hi Sebastian, thanks for the go ahead! On Wed, 4 Jan 2023 19:42:13 +0100 Sebastian Ramacher wrote: > Control: tags -1 confirmed > > Please go ahead. Uploaded to unstable and it has been built on all archs already… :) I guess it is ready to schedule the binNMUs :) -- Cheers, tobi

Processed: bullseye-pu: package isc-dhcp/4.4.1-2.3+deb11u2

Processing control commands: > affects -1 + src:isc-dhcp Bug #1028313 [release.debian.org] bullseye-pu: package isc-dhcp/4.4.1-2.3+deb11u2 Added indication that 1028313 affects src:isc-dhcp -- 1028313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028313 Debian Bug Tracking System Contact

Bug#1028313: bullseye-pu: package isc-dhcp/4.4.1-2.3+deb11u2

Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: isc-d...@packages.debian.org Control: affects -1 + src:isc-dhcp [ Reason ] Under not completely understood conditions, dhclient completely removes IPv6 addresses

Re: transition: pandas 1.3 -> 1.5

Hi Rebecca On Fri, 6 Jan 2023 at 10:30, Rebecca N. Palmer wrote: > Should this go ahead before the freeze? I think yes if the new dask > works, but am open to disagreement. Please go ahead. With numpy 1:1.24.1-2 built on all release architectures, now is a good time. Regards Graham

Bug#1028286: transition: xml-security-c

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear Release Team, In a recent message [1] Shibboleth upstream strongly recommended building xml-security-c without Xalan support to reduce the attack surface of Shibboleth

Bug#1028283: transition: qtbase-abi-5-15-8

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Forwarded: https://release.debian.org/transitions/html/qtbase-abi-5-15-8.html Control: affects -1 + src:qtbase-opensource-src Dear Release team, As we discussed in #1025863, let's try

Processed: transition: qtbase-abi-5-15-8

Processing control commands: > affects -1 + src:qtbase-opensource-src Bug #1028283 [release.debian.org] transition: qtbase-abi-5-15-8 Added indication that 1028283 affects src:qtbase-opensource-src -- 1028283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028283 Debian Bug Tracking System

Re: Bug#1022571: transition: pandas 1.3 -> 1.5

skbio is fixed, ulmo is maybe fixed but untested. dask is unclear (see #1027254 for details): it looks like it's probably fixable, but I don't have an actual working fix yet. There has been no response from its maintainers.