On Thu, Dec 21, 2023 at 02:42:56PM +, Matthew Vernon wrote:
> On 21/12/2023 09:41, Helmut Grohne wrote:
> > Is it ok to call upgrade scenarios failures that cannot be reproduced
> > using apt unsupported until we no longer deal with aliasing?
>
> I incline towards "no"; if an upgrade has
On Thu, Dec 21, 2023 at 03:31:55PM +0100, Marc Haber wrote:
> On Thu, Dec 21, 2023 at 11:19:48AM -0300, Antonio Terceiro wrote:
> > On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote:
> > > Is it ok to call upgrade scenarios failures that cannot be reproduced
> > > using apt unsupported
Am 21.12.23 um 11:50 schrieb Christoph Berg:
Re: Helmut Grohne
Is it ok to call upgrade scenarios failures that cannot be reproduced
using apt unsupported until we no longer deal with aliasing?
If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug)
with no action calling the
On Thu, 21 Dec 2023 at 15:31:55 +0100, Marc Haber wrote:
> Do those GUI frontends that work via packagekit or other frameworks
> count as "using apt"?
Managing apt/dpkg packages via packagekit uses libapt-pkg6.0 (via
/usr/lib/*/packagekit-backend/libpk_backend_apt.so). I don't know whether
that's
Hi folks
The repository for the Linux kernel in Debian currently makes heavy use
of merges, which will always conflict due to changelog changes. This
constitutes high cognitive busy load, for pretty small gains.
After already removing the manually modified abiname, we can drop more
manual work
Hi,
On 21/12/2023 09:41, Helmut Grohne wrote:
Is it ok to call upgrade scenarios failures that cannot be reproduced
using apt unsupported until we no longer deal with aliasing?
I incline towards "no"; if an upgrade has failed part-way (as does
happen), people may then reasonably use dpkg
On Thu, Dec 21, 2023 at 11:19:48AM -0300, Antonio Terceiro wrote:
> On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote:
> > Is it ok to call upgrade scenarios failures that cannot be reproduced
> > using apt unsupported until we no longer deal with aliasing?
>
> I think so, yes. I
On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote:
> ## Upgrading using dpkg directly?
>
> We already have quite a number of packages that use Conflicts to prevent
> file loss in upgrades in a very similar way to #1058937 (Ben's
> libnfsidmap1 bug) even in released versions of Debian.
Hello,
I am unsure if this is the right place to ask.
I am trying to build the upstream mainline kernel (6.7-rc6) as
instructed at https://wiki.debian.org/BuildingKernelFromUpstreamSources
for troubleshooting purposes.
The build and installation were successful, but when I try to boot the
Re: Helmut Grohne
> Is it ok to call upgrade scenarios failures that cannot be reproduced
> using apt unsupported until we no longer deal with aliasing?
>
> If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug)
> with no action calling the scenario unsupported.
I think we
Hello,
I am unsure if this is the right place to ask.
I am trying to build the upstream mainline kernel (6.7-rc6) as
instructed at https://wiki.debian.org/BuildingKernelFromUpstreamSources
for troubleshooting purposes.
The build and installation were successful, but when I try to boot the
Hi,
this installment serves a dual purpose. Let me first give an update of
the status quo and then pose a consensus question on how we want to deal
with a particular problem.
I Cc d-release@l.d.o as upgrades are an integral part of releases.
I Cc d-ctte@l.d.o for advisory feedback with
12 matches
Mail list logo
