On Fri, Mar 08, 2024 at 07:38:01AM +0100, Rene Engelhard wrote:
> Hi,
>
> Am 08.03.24 um 00:12 schrieb Eric Valette:
> > On 07/03/2024 21:16, Rene Engelhard wrote:
> > ct more people.
> > >
> > > But not so much for dependency issues like this. Which is my sole
> > > point. In 99,9% of cases
On 08/03/2024 07:38, Rene Engelhard wrote:
Hi,
I did my part for example with this one, that maintainer denied first
but fixed later in his next upload as suggested...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065349
Well, you haven't seen the various discussion how to fix
Hi,
Am 08.03.24 um 00:12 schrieb Eric Valette:
On 07/03/2024 21:16, Rene Engelhard wrote:
ct more people.
But not so much for dependency issues like this. Which is my sole
point. In 99,9% of cases this won't even migrate to testing. And
unstable won't be released - testing will.
What is
Am 08.03.24 um 00:12 schrieb Eric Valette:
On 07/03/2024 21:16, Rene Engelhard wrote:
ct more people.
But not so much for dependency issues like this. Which is my sole
point. In 99,9% of cases this won't even migrate to testing. And
unstable won't be released - testing will.
What is your
On 07/03/2024 21:16, Rene Engelhard wrote:
ct more people.
But not so much for dependency issues like this. Which is my sole point.
In 99,9% of cases this won't even migrate to testing. And unstable won't
be released - testing will.
What is your point? Without known bugs or new versions
On Thu, Mar 07, 2024 at 09:16:10PM +0100, Rene Engelhard wrote:
> Hi,
>
> Am 07.03.24 um 21:07 schrieb Eric Valette:
> > On 07/03/2024 20:55, Rene Engelhard wrote:
> >
> > > unstable is unstable. Don't use it if you can't handle stuff like
> > > this. And yes, be it even for more days or however
Hi,
Am 07.03.24 um 21:07 schrieb Eric Valette:
On 07/03/2024 20:55, Rene Engelhard wrote:
unstable is unstable. Don't use it if you can't handle stuff like
this. And yes, be it even for more days or however it takes.
The usual mantra. However, if no one use unstable and debug it to make
On 07/03/2024 20:55, Rene Engelhard wrote:
unstable is unstable. Don't use it if you can't handle stuff like this.
And yes, be it even for more days or however it takes.
The usual mantra. However, if no one use unstable and debug it to make
it work correctly, maintainers will discover
Hi,
Am 07.03.24 um 20:33 schrieb Eric Valette:
On 07/03/2024 19:58, Rene Engelhard wrote:
> My point also was that your reopening of the bug is wrong since the
maintainer can't do anything about it.
E.g. if libreoffice wasn't rebuilt against most t64 r-deps since it a)
also has libraries
On Thu, Mar 07, 2024 at 12:20:22AM -0500, Theodore Ts'o wrote:
> > Aside from the libuuid1t64 revert, for which binNMUs have been scheduled, I
> > actually would expect unstable to be dist-upgradeable on non-32-bit archs:
> > either the existing non-t64 library will be kept installed because
On 07/03/2024 19:58, Rene Engelhard wrote:
I'm sure it will be done at some point. However, I just point out that
on amd64
Maybe, though in my sid VM with all tasks installed plasma-workspace
fails to upgrade, claiming about gdb-minmal | gdb not to be installed
whereas both of that install,
Am 07.03.24 um 19:21 schrieb Eric Valette:
On 07/03/2024 18:57, Rene Engelhard wrote:
That one is tracked and will get appropriate bin-NMUs from the
release team, I am sure.
It is right that this uninstallability is "being part of the normal
things due to transition".
I'm sure it will
On 07/03/2024 18:57, Rene Engelhard wrote:
That one is tracked and will get appropriate bin-NMUs from the release
team, I am sure.
It is right that this uninstallability is "being part of the normal
things due to transition".
I'm sure it will be done at some point. However, I just point
Am 07.03.24 um 09:55 schrieb Eric Valette:
On 07/03/2024 07:25, Kevin Bowling wrote:
As of this evening these are the packages that currently have broken
deps on amd64 for me:
gstreamer1.0-plugins-good gstreamer1.0-pulseaudio
libkf5akonadisearch-bin libkf5akonadisearch-plugins occt-misc
On 07/03/2024 07:25, Kevin Bowling wrote:
As of this evening these are the packages that currently have broken
deps on amd64 for me:
gstreamer1.0-plugins-good gstreamer1.0-pulseaudio
libkf5akonadisearch-bin libkf5akonadisearch-plugins occt-misc
Someone already opened a bug for
On Wed, Mar 6, 2024 at 4:18 PM Russ Allbery wrote:
>
> Eric Valette writes:
>
> > You can force the migration by explicitly adding the package that it
> > propose to remove (e.g gdb for libelf, ...)
>
> > I managed to upgrade all packages you mention in your mail that
> > way. Only
On Wed, Mar 06, 2024 at 12:33:08PM -0800, Steve Langasek wrote:
>
> Aside from the libuuid1t64 revert, for which binNMUs have been scheduled, I
> actually would expect unstable to be dist-upgradeable on non-32-bit archs:
> either the existing non-t64 library will be kept installed because nothing
Eric Valette writes:
> You can force the migration by explicitly adding the package that it
> propose to remove (e.g gdb for libelf, ...)
> I managed to upgrade all packages you mention in your mail that
> way. Only libkf5akonadisearch-bin libkf5akonadisearch-plugins
>
My current list of unupgradable packages on amd64 is:
gir1.2-gstreamer-1.0/unstable 1.24.0-1 amd64 [upgradable from: 1.22.10-1]
libegl-mesa0/unstable 24.0.2-1 amd64 [upgradable from: 24.0.1-1]
libgbm1/unstable 24.0.2-1 amd64 [upgradable from: 24.0.1-1]
libgl1-mesa-dri/unstable 24.0.2-1 amd64
Steve Langasek writes:
> So once the libuuidt64 revert is done (later today?), if apt
> dist-upgrade is NOT working, I think we should want to see some apt
> output showing what's not working.
My current list of unupgradable packages on amd64 is:
gir1.2-gstreamer-1.0/unstable 1.24.0-1 amd64
On 2024-03-06 12:53:02 -0800, Steve Langasek wrote:
> On Thu, Mar 07, 2024 at 01:43:11AM +0500, Andrey Rahmatullin wrote:
> > On Wed, Mar 06, 2024 at 12:33:08PM -0800, Steve Langasek wrote:
> > > > > Are there instructions on how to progress an unstable system through
> > > > > this, or is the
On Thu, Mar 07, 2024 at 01:43:11AM +0500, Andrey Rahmatullin wrote:
> On Wed, Mar 06, 2024 at 12:33:08PM -0800, Steve Langasek wrote:
> > > > Are there instructions on how to progress an unstable system through
> > > > this, or is the repo currently in a known inconsistent state? I have
> > > >
On Wed, Mar 06, 2024 at 12:33:08PM -0800, Steve Langasek wrote:
> > > Are there instructions on how to progress an unstable system through
> > > this, or is the repo currently in a known inconsistent state? I have
> > > tried upgrading various packages to work through deps but I am unable
> > >
On Thu, Mar 07, 2024 at 12:46:24AM +0500, Andrey Rahmatullin wrote:
> On Wed, Mar 06, 2024 at 12:26:17PM -0700, Kevin Bowling wrote:
> > Are there instructions on how to progress an unstable system through
> > this, or is the repo currently in a known inconsistent state? I have
> > tried
On Wed, Mar 06, 2024 at 12:26:17PM -0700, Kevin Bowling wrote:
> Are there instructions on how to progress an unstable system through
> this, or is the repo currently in a known inconsistent state? I have
> tried upgrading various packages to work through deps but I am unable
> to do a
Kevin Bowling writes:
> Are there instructions on how to progress an unstable system through
> this, or is the repo currently in a known inconsistent state? I have
> tried upgrading various packages to work through deps but I am unable to
> do a dist-upgrade for a while.
It doesn't look like
On Mon, Feb 26, 2024 at 4:21 PM Steve Langasek wrote:
>
> Dear developers,
>
> With the last known blockers resolved, I have now uploaded NMUs of the
> experimental versions of gcc-13 and gcc-14 to unstable, and a corresponding
> upload of dpkg changing the default build flags is expected to
27 matches
Mail list logo
