[pkg-apparmor] Bug#983114: libapparmor1: After upgrade is the system not bootable. Init is complaining about incorrect apparmor version.

[Ďoďo]

Hi, yes, I do agree the problem is in libc dependencies. Yes, I am using
testing and I just did allow the apt to upgrade all the
recommended packages. It resulted in not booting system.

But after reading your email 2-3 times and then triple checking my
apt.sources I noticed something there. This is my cleaned apt source:
deb http://ftp.de.debian.org/debian/ stable main non-free contrib
deb http://ftp.de.debian.org/debian/ testing main non-free contrib
deb http://security.debian.org/debian-security stable/updates main contrib
non-free
deb http://ftp.de.debian.org/debian/ stretch-updates main contrib non-free

Is it possible that the forgotten stretch-updates is the trouble maker?
Otherwise I do not understand your comment about "running testing on
stretch system".
Thanks for your reply and sorry for very likely incorrect bug report

Jozef


On Fri, Apr 2, 2021 at 11:31 AM intrigeri <intrigeri at debian.org> wrote:

> Control: tag -1 + moreinfo
>
> Hi,
>
> Ivanecky Jozef (2021-02-19):
> > Package: libapparmor1
> > Version: 2.13.6-9
>
> > Debian Release: 9.8
> >   APT prefers oldstable-updates
> >   APT policy: (500, 'oldstable-updates'), (500, 'testing'), (500,
> 'stable')
>
> > Versions of packages libapparmor1 depends on:
> > ii  libc6  2.31-9
>
> It looks like you've upgraded key packages (libapparmor1, libc6) to
> the version from testing/sid on a Stretch system. Is this correct?
>
> This kind of setup is unsupported and I'm afraid there's little chance
> it'll work. I suspect the problem here is about the libc6 upgrade,
> rather than about AppArmor, by the way.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-apparmor-team/attachments/20210411/6279b244/attachment.htm>