+
+ * Non-maintainer upload.
+ * Rebuild for bookworm.
+
+ -- Adrian Bunk Fri, 29 Mar 2024 22:52:55 +0200
+
+gross (1.0.2-4.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * CVE-2023-52159: Stack-based buffer overflow (Closes: #1067115)
+
+ -- Adrian Bunk Sat, 23 Mar 2024 23:23:34 +0200
--- gross-1.0.2/debian/changelog2014-10-25 11:20:12.0 +0300
+++ gross-1.0.2/debian/changelog2024-03-29 23:02:44.0 +0200
@@ -1,3 +1,17 @@
+gross (1.0.2-4.1~deb11u1) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bullseye.
+
+ -- Adrian Bunk
On Mon, Mar 04, 2024 at 09:52:14AM +0100, Gerardo Ballabio wrote:
> Gianluca Renzi wrote:
> > The same here. We never used the d-i but we are using Debian systems
> > (kernel and root file system) as daily bases of our line of products
> > embedded systems. Hundred of thousands of boards are
On Sat, Mar 02, 2024 at 02:16:59PM +0100, Sebastian Ramacher wrote:
> On 2024-03-02 15:06:15 +0200, Adrian Bunk wrote:
> > On Fri, Mar 01, 2024 at 11:10:22PM -0800, Steve Langasek wrote:
> > >...
> > > This needs to be built with dpkg-dev (>= 1.5.22), ...
> &g
On Fri, Mar 01, 2024 at 11:10:22PM -0800, Steve Langasek wrote:
>...
> This needs to be built with dpkg-dev (>= 1.5.22), ...
>...
The correct version is 1.22.5 (and >= 1.5.22 therefore a nop).
cu
Adrian
On Sun, Jan 21, 2024 at 06:55:31PM -0500, Andres Salomon wrote:
>...
> b) Backport the profiler patch to bookworm's rustc, and do a s-p-u update to
> Bookworm's rustc. Since this adds a new feature, I don't view it as too
> risky, but the release team or rust team may feel differently. The main
>
On Sun, Jan 21, 2024 at 06:58:37PM -0500, Mo Zhou wrote:
>
> On 1/21/24 10:54, Sebastian Ramacher wrote:
> > Control: tags -1 confirmed
> > Should those that are not part of the transition tracker use the shared
> > library or not?
> flatbuffers is like protobuf. I'm not sure how many rdeps among
On Fri, Jan 19, 2024 at 11:43:11AM +0100, Andreas Beckmann wrote:
>...
> And having openjdk-8-* installed manually should not satisfy the openjdk
> (build) dependency of any package in the archive via virtual packages.
We already have two OpenJDK version (17 and 21) in bookworm.
Everything
On Thu, Jan 11, 2024 at 11:28:19AM +0100, Bastian Blank wrote:
>...
> On Thu, Jan 11, 2024 at 09:48:34AM +, Dimitri John Ledkov wrote:
> > Disabling debug symbols, enabling debug symbol zstd compression, using
> > split debug symbols (disabled BTF usage) should help here.
>
> Okay, maybe more
On Sat, Dec 23, 2023 at 03:55:15PM -0700, Soren Stoutner wrote:
>...
> In a hypothetical world where Qt 6.2 LTS had shipped with bookworm, we could
> build any Qt WebEngine from 6.2, 6.3, or 6.4 against it without problem.
> Initially it might seem best to build the highest possible, but because
On Sat, Dec 16, 2023 at 04:33:58PM -0700, Soren Stoutner wrote:
> On Saturday, December 16, 2023 4:10:42 PM MST Adrian Bunk wrote:
> > On Sat, Dec 16, 2023 at 01:22:13PM -0700, Soren Stoutner wrote:
> > > Bookworm released with qtwebengine-opensource-src 5.15.8+dfsg-1, but
&g
On Sat, Dec 16, 2023 at 01:22:13PM -0700, Soren Stoutner wrote:
>...
> Bookworm released with qtwebengine-opensource-src 5.15.8+dfsg-1, but
> 5.15.13+dfsg-1~deb12u1 was later uploaded.
>...
That's not true, bookworm released with 5.15.13+dfsg-1~deb12u1.
> At this point, the biggest remaining
On Thu, Dec 14, 2023 at 05:29:43PM -0700, Soren Stoutner wrote:
> On Thursday, December 14, 2023 4:19:17 PM MST Adrian Bunk wrote:
>
> > Non-LTS oldstable is the 3rd year of stable security support,
> > this is required for giving users time to schedule the invasive
> >
On Thu, Dec 14, 2023 at 12:48:08PM -0700, Soren Stoutner wrote:
>...
> This plan does not address oldstable security support.
>...
Non-LTS oldstable is the 3rd year of stable security support,
this is required for giving users time to schedule the invasive
upgrades to a new Debian stable at a
On Wed, Dec 13, 2023 at 08:49:55PM -0700, Soren Stoutner wrote:
>...
> Currently there is no real security support for Qt WebEngine in stable, which
> is an oversight that might surprise many Debian users. The purpose of this
> discussion is to figure out the best way to change that.
This is
On Wed, Dec 13, 2023 at 02:19:04PM -0700, Soren Stoutner wrote:
>...
> How feasible would it be to make sure that stable always ships with paired
> LTS releases of
> KDE and Qt? As you point out above, those release windows might not line up
> exactly with
> Debian’s release window, but it
On Wed, Dec 13, 2023 at 11:43:56AM +0100, Andreas Tille wrote:
>...
> I'm worried
> about issues in r-rcan-rmarkdown[3] and r-cran-flextable[4] which are
> caused by pandoc errors on ppc64el architecture *only*. That's really
> strange and might mean that pandoc on this architecture is broken?
On Thu, Dec 07, 2023 at 09:38:47PM +0100, Salvatore Bonaccorso wrote:
>...
> Hmm technically likely right, but in security we cannot very well
> handle the binNMUs (only if the source is already present there,
> otherwise ftp-masters need to inject the sources first).
>
> This is related to
>
On Thu, Dec 07, 2023 at 04:09:28PM +0100, Andreas Tille wrote:
>...
> Am Thu, Dec 07, 2023 at 01:37:02PM -0100 schrieb Graham Inggs:
>...
> > Also, why do r-bioc-netsam and r-bioc-org.hs.eg.db not even appear on
> > the tracker?
>
> I was always wondering about this but I have no clue.
On Thu, Dec 07, 2023 at 01:56:34PM +, Adam D. Barratt wrote:
>...
> Relatedly, if a binary upload was performed to the security archive
> then any binNMUs should likely happen there and then be synced across
> to stable, otherwise we're only resolving part of the issue.
I'd start one step
On Thu, Dec 07, 2023 at 11:18:42AM +0100, Paul Gevers wrote:
> Hi,
Hi Paul,
> On 07-12-2023 10:48, Adrian Bunk wrote:
> > unfortunately not, I noticed nagios-plugins-contrib on the buildds and
> > checked a few of the results after looking for "amd64" and "a
On Thu, Dec 07, 2023 at 10:17:35AM +0100, Matthias Klose wrote:
> Control: reopen -1
>
> please don't close issues that are only fixed in experimental. These should
> stay on radar for the transition.
Sounds like tooling that does still not know about version tracking.
My guess would be that
On Mon, Dec 04, 2023 at 05:59:44PM +, Holger Levsen wrote:
> Hi Adrian,
Hi Holger,
> thanks for bringing this to our attention!
>
> On Sun, Dec 03, 2023 at 11:27:04PM +0200, Adrian Bunk wrote:
>...
> > There are other packages with the same issue in bookworm,
> &g
On Sun, Dec 03, 2023 at 05:32:38PM +, Alastair McKinstry wrote:
> Hi,
Hi Alastair,
>...
> How do I do such a transition? I can't easily test as I lack 32-bit
> hardware. It _should_ be fine as MPICH builds and works
>...
Every amd64 hardware is also i386 hardware,
debootstrap --arch=i386
On Sun, Dec 03, 2023 at 10:59:44AM +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Mon, 2023-10-23 at 13:19 +0200, Jan Wagner wrote:
> > As reported in #1033791, check_running_kernel fails to find version
> > on bookworm/(arm64|armhf).
>
> Please go ahead.
Architecture:
On Sun, Dec 03, 2023 at 09:51:38PM +0100, Paul Gevers wrote:
>...
> And it also means that r-bioc-biocgenerics is now blocked on the haskell
> transition. Lovely. Good thing that pandoc is supposed to be the last piece
> in that several months long transition.
It's only blocked by the pandoc part
On Sun, Dec 03, 2023 at 09:46:31AM -0100, Graham Inggs wrote:
>...
> This is probably a good example for why new packages should be
> uploaded to experimental first, instead of directly to unstable.
>...
Not really.
It is rare that a new source package takes over a binary package from
another
of this
+plugin shipped by gimp itself since 2.10.10. (Closes: #1057149)
+
+ -- Adrian Bunk Sat, 02 Dec 2023 16:47:53 +0200
+
gimp (2.10.22-4+deb11u1) bullseye-security; urgency=high
* Non-maintainer upload by the Security Team.
diff -Nru gimp-2.10.22/debian/control gimp-2.10.22/debian
of this
+plugin shipped by gimp itself since 2.10.10. (Closes: #1057149)
+
+ -- Adrian Bunk Sat, 02 Dec 2023 15:31:27 +0200
+
gimp (2.10.34-1+deb12u1) bookworm-security; urgency=high
* Non-maintainer upload by the Security Team.
diff -Nru gimp-2.10.34/debian/control gimp-2.10.34/debian/control
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Salvatore Bonaccorso
* Add Conflicts+Replaces: gimp-dds to remove old versions of this
plugin shipped by gimp itself since 2.10.10. (Closes: #1057149)
On Sun, Nov 19, 2023 at 09:34:40AM +0100, Paul Gevers wrote:
>...
> On 19-11-2023 09:06, Sebastiaan Couwenberg wrote:
>...
> > grass-core in testing depends on the old libgdal33, hence the need to
> > also get grass and libgdal-grass from unstable when running autopkgtest
> > with gdal from
permitted
by the dependencies.
And this is not just a test issue:
On Sun, Nov 19, 2023 at 01:54:02PM +0100, Hilmar Preuße wrote:
> On 11/19/23 00:40, Adrian Bunk wrote:
>...
> > And it also might affects users directly, without proper dependencies
> > e.g. a bookworm -&g
On Mon, Nov 20, 2023 at 12:05:46AM +0100, Hilmar Preuße wrote:
> On 11/19/23 00:40, Adrian Bunk wrote:
>
> Hi Adrian,
Hi Hilmar,
> > A proper fix would be either to:
> > 1. patch the version check out of texlive-bin (preferred), or
> >
> Did so, see [1]. I did n
On Sun, Nov 19, 2023 at 01:54:02PM +0100, Hilmar Preuße wrote:
>...
> I can patch out that version check as found by Samuel, but I don't see how
> that would solve the core dump or the SIGABRT, which was reported. I hope
> lua_error(L) is not the equivalent of "exit with SIGABRT". ;-)
>...
It is.
On Sat, Nov 18, 2023 at 11:51:15PM +0100, Hilmar Preuße wrote:
> Control: severity -1 important
> Control: block 1056183 by -1
>
> On 11/18/23 20:18, Samuel Thibault wrote:
>
> Hi Samuel,
>
> >
> > nmu texlive-bin_2023.20230311.66589-7 . ANY . unstable . -m "Rebuild
> > against new zlib"
> >
On Fri, Nov 17, 2023 at 05:22:35PM +0100, Sebastian Andrzej Siewior wrote:
>...
> I'm now curious to learn what could be the best way to move forward. I
> have a few ideas:
> - NMU #1055416, allow the transition to happen.
>
> - NMU also #1052470 in order to allow an OpenSSL 3.1.4 upload. This
>
On Fri, Oct 27, 2023 at 10:55:48AM +0200, Bastian Blank wrote:
> On Fri, Oct 27, 2023 at 08:43:46AM +0200, Julian Andres Klode wrote:
> > > > ## Image packages contains more version info
> > > >
> > > > Example: linux-image-6.5.3-cloud-arm64
> > >
> > > > It will not longer be possible to
On Sat, Oct 21, 2023 at 07:08:34PM +0200, Sebastian Ramacher wrote:
> Hi Adrian
Hi Sebastian,
> On 2023-10-20 08:30:21 +0200, Sebastian Ramacher wrote:
> > On 2023-10-19 18:00:29 +0300, Ilias Tsitsimpis wrote:
> > > > Do you need help from us?
> > >
> > > Can you please schedule the necessary
On Wed, Oct 18, 2023 at 10:46:13PM -0400, Scott Talbert wrote:
> On Thu, 19 Oct 2023, Cyril Brulebois wrote:
>
> > Scott Talbert (2023-10-17):
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian@packages.debian.org
> > > Usertags: binnmu
> > > X-Debbugs-Cc:
On Sat, Oct 07, 2023 at 03:33:16PM -0400, Boyuan Yang wrote:
>...
> (2) Fix current jpeg-xl in Sid properly. That won't be too trivial since the
> new
> testing error is likely triggered by some unclear changes in
> build-dependencies over
> the past several months.
>...
Fix below, only tested
On Wed, Oct 04, 2023 at 03:23:46PM -0400, David James wrote:
> Hi Anton,
>
> Is there anything I can do to help this transition along? I wish to
> package software that does not build on 1.74, but does on 1.81 and 1.82.
> If there's anyway I can assist with bumping boost-defaults to 1.81 or 1.82
On Tue, Oct 03, 2023 at 07:30:49PM +0200, Bastian Blank wrote:
>...
> The core problem is that people assume they can get headers matching the
> currently running kernel, without upgrading first, see also the parallel
> thread.
>...
If the new kernel has a regression that affects the user, the
On Tue, Jul 25, 2023 at 11:39:38PM +0200, Guilhem Moulin wrote:
>...
> The Security Team decided not to issue a DSA for that CVE, but it's now fixed
> in
> buster-security (2.2.1-3+deb10u1) as well as sid (2.17.1.1-2), so it makes
> sense
> to fix it via (o)s-pu too.
>...
In all 3 distributions
for bookworm.
+
+ -- Adrian Bunk Sat, 30 Sep 2023 15:52:45 +0300
+
+rmlint (2.9.0-2.5) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Add upstream fix for GUI startup failure with recent python3.11.
+(Closes: #1040940)
+
+ -- Adrian Bunk Sat, 05 Aug 2023 17:16:05 +0300
+
+rmlint
7.1~deb11u1) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bullseye.
+
+ -- Adrian Bunk Sat, 30 Sep 2023 15:18:55 +0300
+
+cpio (2.13+dfsg-7.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Suggest libarchive-dev (Closes: #662718).
+ * d/copyright: Conv
On Sat, Sep 09, 2023 at 10:15:59AM +0200, Salvatore Bonaccorso wrote:
>...
> Note that the last time the problem arised already earlier in
> experimental and Ben workarounded it there with
> https://salsa.debian.org/kernel-team/linux/-/commit/9dfe6d33a4fd220394228b30cbbfdb3b444d36ec
> We probably
On Mon, Sep 11, 2023 at 10:36:00AM +0100, Simon McVittie wrote:
> On Sat, 19 Aug 2023 at 10:39:44 +0200, Sylvestre Ledru wrote:
> > llvm-defaults has been pointing to 16 in experimental for quite sometime.
> > Opening this transition to make sure it is on your radar! :)
> >
> > I opened bug
On Sat, Sep 09, 2023 at 10:15:59AM +0200, Salvatore Bonaccorso wrote:
>...
> - Relese the DSA without armel builds. This is not optimal and for the point
> release
> we need to have to have all builds, but this gives people who still are
> interested
> in this architecture to step up and
On Wed, Aug 30, 2023 at 04:54:01PM +0100, Simon McVittie wrote:
>...
> However, if I understand correctly, Luca has been told that some official
> mips64el buildds are running mipsel user-space on mips64el hardware which
> only works with the buster kernel,
>...
> Is this true?
Yes:
On Wed, Aug 02, 2023 at 10:58:17AM +0200, Drew Parsons wrote:
> On 2023-07-31 21:30, Sebastian Ramacher wrote:
> > >
> > > combblas: 1.16.0 → 2.0.0
> > > superlu:5 → 6
> > > hypre: 2.26.0 → 2.28.0
> > > mumps:5.5 → 5.6
> >
> > Please go ahead.
>
> combblas and superlu are
On Fri, Jul 14, 2023 at 11:03:39AM +0100, Adam D. Barratt wrote:
> Hi Adrian,
Hi Adam,
> While checking the status of the linux upload to proposed-updates this
> morning, I noticed that the packages for mipsel and mips64el were still
> in the BD-Uninstallable state, whereas those for some other
On Thu, Jul 13, 2023 at 09:16:15PM +0200, Bastian Blank wrote:
>...
> ### NMU
>
> Can be easily added back by adding "bX" or so to the ABI.
That would be confusing, bX is naming convention for binNMUs in Debian
revisions.
> ### BinNMU
>
> Is impossible to support. The version change requires
On Sun, Jul 09, 2023 at 01:13:55AM +0300, Michael Tokarev wrote:
>...
> I'll see what can be done tomorrow. Apparently it might be better to revert
> this keyring change for bookworm and fix it for good in trixie first.
>...
And BTW, manually linking with libatomic is the correct fix here for
On Sun, Jul 09, 2023 at 01:13:55AM +0300, Michael Tokarev wrote:
> 09.07.2023 01:01, Adrian Bunk wrote:
> > This does apparently need the -latomic workaround from 2:4.18.3+dfsg-3:
> > https://buildd.debian.org/status/package.php?p=samba=bookworm
>
> Sigh!
> This is the ke
This does apparently need the -latomic workaround from 2:4.18.3+dfsg-3:
https://buildd.debian.org/status/package.php?p=samba=bookworm
cu
Adrian
bunk@coccia:~$ cat
/srv/ftp-master.debian.org/queue/reject/nvidia-cuda-toolkit_11.8.0-5~deb12u1_amd64-buildd.changes.reason
Version check failed:
Your upload included the binary package nvidia-openjdk-8-jre, version
9.+8u372-ga-1~11.8.0-5~deb12u1, for amd64,
however experimental already has
On Tue, May 16, 2023 at 05:28:11PM +0300, Timo Aaltonen wrote:
> Timo Aaltonen kirjoitti 16.5.2023 klo 10.12:
> > Markus Koschany kirjoitti 13.5.2023 klo 23.38:
> > > Hi Salvatore,
> > >
> > > adding Timo Aaltonen, maintainer of dogtag-pki and tomcatjss, to CC
> > >
> > > Am Samstag, dem
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Control: block 1034224 by -1
nmu pvpgn_1.8.5-3 . ANY . unstable . -m "Rebuild with fixed debhelper
installing pvpgn.service to the correct place"
Files in second .deb but not in first
On Sun, Mar 26, 2023 at 03:23:58PM +0200, Markus Koschany wrote:
> Am Sonntag, dem 26.03.2023 um 12:15 +0300 schrieb Timo Aaltonen:
> > Markus Koschany kirjoitti 24.3.2023 klo 15.35:
> > > Am Freitag, dem 24.03.2023 um 09:21 +0200 schrieb Timo Aaltonen:
> > > > Markus Koschany kirjoitti 23.3.2023
Package: release.debian.org
Severity: normal
Suggestions for both
https://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList
https://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList/BookwormCheckList
Before the release
Add "Notify the LTS team of the new debian-archive-keyring"
After
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu libewf_20171104-1 . ANY . experimental . -m "Rebuild against libssl3"
nmu libre_2.0.1-1 . ANY . experimental . -m "Rebuild against libssl3"
nmu psi-plus_1.4.1456-2 . ANY . experimental .
On Fri, Mar 10, 2023 at 09:27:30AM +, Adam D. Barratt wrote:
> On Sat, 2023-03-04 at 16:03 +0200, Adrian Bunk wrote:
> > On Sat, Mar 04, 2023 at 01:33:13PM +, Adam D. Barratt wrote:
> > > SRM is considering using an ed25519 GPG key for bookworm. Does
> > >
On Sat, Mar 04, 2023 at 01:33:13PM +, Adam D. Barratt wrote:
>...
> Hi,
Hi Adam,
> SRM is considering using an ed25519 GPG key for bookworm. Does anyone
> see any issues with that?
>...
> We know that GPG(V) 1.X can't handle EC keys,
>...
in all releases from stretch to bookworm:
Package:
Package: release.debian.org
Severity: normal
The s390x binary no longer builds and has been removed (see #1025884),
but due to binary-any + binary-all the autopkgtest is still attempted
and runs into the same build error.
Package: release.debian.org
Severity: normal
With the bookworm-ignore for #994758, bullseye and bookworm
will ship libsgutils2-2 packages with different so-name.
This means mixing bullseye/bookworm libsgutils2-2 and rdeps
would be brokwn in either direction.
My plan to resolve this is:
1. RC
Package: release.debian.org
Severity: normal
Mixing of testing/unstable upstream-ontologist/lintian-brush in either
direction gives a test-only failure due to a test adapted to changed output.
lintian-brush/unstable with upstream-ontologist/testing:
On Fri, Feb 24, 2023 at 12:27:35PM +0100, Emilio Pozuelo Monfort wrote:
> On 24/02/2023 09:48, Adrian Bunk wrote:
> > On Fri, Feb 24, 2023 at 09:19:40AM +0100, Emilio Pozuelo Monfort wrote:
> > > ...
> > > Also note that one of the concerns was for armhf, which is now b
On Fri, Feb 24, 2023 at 09:19:40AM +0100, Emilio Pozuelo Monfort wrote:
>...
> Also note that one of the concerns was for armhf, which is now being built
> from arm64 buildds.
>...
On armhf there is a 4 GB FTBFS for the future (like on i386),
and a 3 GB FTBFS today that still seems to be present
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: Maintainers of Mozilla-related packages
Control: block 1021810 982794 992150 993659 993660 by -1
popcon is no longer a criteria for key packages, which makes
firefox-esr subject to autoremoval that would be permanent
for bookworm at
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: Dominic Hargreaves , Debian Request Tracker Group
Control: block 1030749 by -1
https://release.debian.org/testing/freeze_policy.html#soft
...
Dropping or adding binary packages to a source package, moving binaries between
source
On Fri, Feb 17, 2023 at 09:28:59PM -0500, Theodore Ts'o wrote:
> On Fri, Feb 17, 2023 at 10:34:29PM +0200, Adrian Bunk wrote:
> >
> > The same general problem applies in various "building non-Debian
> > embedded Linux filesystem on Debian" situations where the tar
On Fri, Feb 17, 2023 at 02:08:28PM -0500, Theodore Ts'o wrote:
>...
> So enabling what may be
> convenient, but ultimately an anti-pattern is something that hopefully
> in the long-term Debian should be striving towards. Yes, it's
> annoying and and extra work. So is using build chroots if we
On Thu, Feb 16, 2023 at 03:05:06PM -0800, Russ Allbery wrote:
>...
> Each time you change the defaults in a way that could be
> backward-incompatible, you could capture those new defaults in a
> permanently-fixed label of, say, 20230616, which is the defaults on that
> date. Probably in the
On Thu, Feb 16, 2023 at 05:24:04PM -0500, Theodore Ts'o wrote:
>...
> and that moving forward, we make it the image building tools
> problem if they want to support this highly dubious practice of using
> Debian N+X's mkfs to build images for Debian N.
>...
That's what they already have to do for
On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
>...
> Instead, turning on this feature should be postponed for the next release
> cycle
> where a proper transition can be done.
>...
On Thu, Feb 16, 2023 at 08:02:11PM +0100, Daniel Leidert wrote:
>...
> You completely miss the
Disclaimer:
Like everyone else except Sebastian who commented in this bug so far,
I am not a member of the release team.
Below is my attempt to give an overview of the situation,
feel free to amend/correct if anything is missing or wrong.
1. Image creation tools need special cases for older
On Thu, Feb 16, 2023 at 08:02:11PM +0100, Daniel Leidert wrote:
>...
> Most server providers have exctly *one*
> rescue system from where I can do a clean installation with deboostrap
> (and that even usually is a Debian). I cannot choose to use one that
> hasn't an e2fsprogs that has this
On Thu, Feb 16, 2023 at 05:48:22PM +0100, Daniel Leidert wrote:
> Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk:
> > On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
> > > ...
> > > Reasons:
> > > ...
> > > - - the cha
On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
>...
> Reasons:
>...
> - - the change makes it impossible to create filesystems with this version of
> e2fsprogs and then run a grub-install from a target system that does not
> cope
> with that feature; basically breaking the
On Wed, Feb 15, 2023 at 09:05:28PM +0800, Shengjing Zhu wrote:
> On Wed, Feb 15, 2023 at 8:53 PM Shengjing Zhu wrote:
> >
> > On Wed, Feb 15, 2023 at 7:56 PM Adrian Bunk wrote:
> > >
> > > On Wed, Feb 15, 2023 at 11:58:54AM +0800, Shengjing Zhu wrote:
> &g
On Wed, Feb 15, 2023 at 08:53:13PM +0800, Shengjing Zhu wrote:
> On Wed, Feb 15, 2023 at 7:56 PM Adrian Bunk wrote:
> >
> > On Wed, Feb 15, 2023 at 11:58:54AM +0800, Shengjing Zhu wrote:
> > >...
> > > The package currently FTBFS on i386/exp
On Wed, Feb 15, 2023 at 11:58:54AM +0800, Shengjing Zhu wrote:
>...
> The package currently FTBFS on i386/experimental but it won't be problem on
> unstable.
> The dep-resolver (aspcud) in experimental chooses gccgo to bootstrap,
> which has a bug https://github.com/golang/go/issues/51850.
> But
On Tue, Feb 14, 2023 at 08:46:53PM -0500, Theodore Ts'o wrote:
>...
> I will draw the analogy of building a program which links against
> glibc for Bookworm resulting in a binary that will not run on Buster.
> We expect that, and we tell people to use build chroots. This is not
> something which
On Tue, Feb 14, 2023 at 11:56:40AM +, Peter Green wrote:
> I recently became aware that mumble's build-dependencies were no longer
> satisfiable on armhf due to a missing zeroc-ice. I looked at the build
> logs for zeroc-ice and all were green. So I looked at the removal log
> and found the
Package: release.debian.org
Severity: normal
The s390x autopkgtest is very slow recently, below is the list
of packages that would miss bookworm only due to that.
It would be good it packages would not miss bookworm only due to
autopkgtest slowness.
# 2 of 2 days old after the s390x autopkgtest
Package: release.debian.org
Severity: normal
When packages disappear in one Debian release that were in the
previous one, that's a regression for users who were using them.
In many cases this is not avoidable, but it is suboptimal if age
in unstable was the only blocker from having a package that
On Sat, Feb 11, 2023 at 08:48:55AM +0100, Paul Gevers wrote:
> Hi,
>
> Disclaimer, I may be misunderstanding how things work, because I only judge
> it on observations and some comments in threads here and there.
>
> On 11-02-2023 00:43, Adrian Bunk wrote:
> > I
On Fri, Feb 10, 2023 at 11:32:21AM +0100, Jonas Smedegaard wrote:
>...
> Reduced size in the archive: Avoids multiple identical copies of library
> source code
>...
I remember the 1990s when archive size was a problem, but a few
years ago we had the first file > 2 GB in the archive (AFAIR an
s just
> containing crate source code), then moving from arch any to arch all
> makes things significantly more difficult for SRM, RT, security team,
> and people doing QA woork.
> I'd definitely recommend reaching out to Adrian Bunk on this issue.
Built-Using in binary-all packages is a
Package: release.debian.org
Severity: normal
binary-all packages are not installable on arm64,
where agda does FTBFS.
Package: release.debian.org
Severity: normal
Migration status for pyatem (- to 0.8.2-1): BLOCKED: Rejected/violates
migration policy/introduces a regression
Issues preventing migration:
∙ ∙ openswitcher/arm64 has unsatisfiable dependency
∙ ∙ openswitcher-proxy/arm64 has unsatisfiable dependency
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: Andreas Beckmann
# Qt
nmu linphone-desktop_5.0.2-2 . ANY . experimental . -m "Rebuild against
qtbase-abi-5-15-18"
nmu mediastreamer2_1:5.2.0+dfsg-1 . ANY . experimental . -m
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: Jochen Sprickerhof , Drew Parsons
nmu pyfai_0.21.3+dfsg1-2 . ANY . unstable . -m "Rebuild to pick up python3-h5py
dependency (see #1030220)"
nmu unifrac_1.2-3 . ANY .
On Sat, Feb 04, 2023 at 09:59:23AM -0500, Roberto C. Sánchez wrote:
>...
> If that is the case, then I am puzzled how intelrdfpmath would have
> migrated to testing without being able to build on mips64el/mipsel
intelrdfpmath having never been built on mips* is not an RC bug or
testing migration
Package: release.debian.org
Severity: normal
Issues preventing migration:
∙ ∙ spring-javaai/arm64 has unsatisfiable dependency
Package: spring-javaai
Architecture: all
Depends:
...
spring (>= ${source:Version}),
Package: spring
Architecture: amd64 i386
The package was removed from testing in
Control: tags -1 ftbfs
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Control: reassign -2 src:gcc-10-cross
Control: retitle -2 gcc-10-cross: source and binary version go out of sync
Control: reassign -3 src:gcc-10-cross-ports
Control: retitle -3 gcc-10-cross-ports: source and binary version go out
On Fri, Jan 20, 2023 at 08:34:23PM +0100, Sebastian Ramacher wrote:
> On 2023-01-20 21:29:30 +0200, Adrian Bunk wrote:
> > On Fri, Jan 20, 2023 at 08:16:29PM +0100, Sebastian Ramacher wrote:
> > > Hi
> > >
> > > On 2023-01-20 18:29:37 +0100
On Fri, Jan 20, 2023 at 08:16:29PM +0100, Sebastian Ramacher wrote:
> Hi
>
> On 2023-01-20 18:29:37 +0100, Dominique Dumont wrote:
> > Hi
> >
> > Nothing is happening in rakudo transition [1], no package are rebuilt.
> >
> > Is there a way to unblock this transition ?
>
> I've now scheduled
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 patch below fixes the tests for me.
cu
Adrian
--- debian/rules.old2023-01-08
On Fri, Jan 06, 2023 at 10:18:16AM +0100, Moritz Muehlenhoff wrote:
>...
> We might consider to set some expectation for oldstable-security, though e.g
> state that
> oldstable-security updates stop three months after the release of stable or
> so.
>
> Chromium is very fast-paced in toolchain
1 - 100 of 749 matches
Mail list logo
