On Thu, Feb 29, 2024 at 06:53:56AM +0100, Paul Gevers wrote:
> Well, officially downgrading isn't supported (although it typically works)
> *and* losing files is one of the problems of our merged-/usr solution (see
> [1]). I *suspect* this might be the cause. We're working hard (well, helmut
> is)
Hi,
On Thu, Feb 29, 2024 at 9:32 AM Simon McVittie wrote:
>
> On Thu, 29 Feb 2024 at 08:40:28 -0300, Leandro Cunha wrote:
> > Jeremy uploaded glib 2.0 to experimental which fixes such problems
>
> libglib2.0-0t64 in experimental does not contain any changes that would
> intentionally fix this.
>
On Thu, 2024-02-29 at 06:53 +0100, Paul Gevers wrote:
> Well, officially downgrading isn't supported (although it typically
> works) *and* losing files is one of the problems of our merged-/usr
> solution (see [1]). I *suspect* this might be the cause. We're
> working
> hard (well, helmut is)
On Wed, 2024-02-28 at 21:57 -0800, Steve Langasek wrote:
> Furthermore, this is a downgrade from a replacing package to a
> replaced
> package. Unless you also --reinstall the package at the end, missing
> files
> are quite to be expected.
Shouldn't that case be something that DPKG could detect
On Thu, 29 Feb 2024 at 08:40:28 -0300, Leandro Cunha wrote:
> Jeremy uploaded glib 2.0 to experimental which fixes such problems
libglib2.0-0t64 in experimental does not contain any changes that would
intentionally fix this.
Upgrading to the experimental libglib2.0-0t64 probably fixes this as a
Hi
On Thu, Feb 29, 2024 at 12:51 AM Christoph Anton Mitterer
wrote:
>
> Package: libglib2.0-0t64
> Version: 2.78.4-2
> Severity: critical
> Justification: breaks unrelated software
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> Hey.
>
>
> CCing d-d since there seems some further deeper
On Thu, Feb 29, 2024 at 06:53:56AM +0100, Paul Gevers wrote:
> On 29-02-2024 4:47 a.m., Christoph Anton Mitterer wrote:
> > @d-d:
> > - How can it happen that purge *t64 packages and at the same time install
> >the previous package, and then the so file is missing?
> >I mean it's clear
Hi,
On 29-02-2024 4:47 a.m., Christoph Anton Mitterer wrote:
@d-d:
- How can it happen that purge *t64 packages and at the same time install
the previous package, and then the so file is missing?
I mean it's clear that they use the same name, but shouldn't DPKG handle
the cleanly?
Workaround for me was to reinstall gsettings-desktop-schemas:
# apt-get reinstall gsettings-desktop-schemas
I have circulated this rescue information to debian-devel and debian-users.
Cheers,
Ash.
Forwarded Message
Subject: Fwd: Fix for missing gsettings desktop schemas on
Attached is the aptitude log.
Cheers,
Chris.
Aptitude 0.8.13: log report
Thu, Feb 29 2024 02:17:21 +0100
IMPORTANT: this log only lists intended actions; actions which fail
due to dpkg problems may not be completed.
Will install 83 packages, and remove 21 packages.
471 kB of disk space will
Package: libglib2.0-0t64
Version: 2.78.4-2
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: debian-de...@lists.debian.org
Hey.
CCing d-d since there seems some further deeper problem with the t64
transition (namely lib files getting lost, when "downgrading" i.e.
11 matches
Mail list logo
