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

2021-09-03 Thread Ďoďo
Hi, please read below. On Fri, Sep 3, 2021 at 10:15 AM intrigeri wrote: > Hi, > > Ďoďo (2021-09-03): > > Yesterday I noticed that some autoupgrade fully updated my TP. So I > removed > > testing, run dist-upgrade to current stable. (TP completely freeze > > during the systemd upgrade) Then I

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

2021-09-03 Thread intrigeri
Hi, Ďoďo (2021-09-03): > Yesterday I noticed that some autoupgrade fully updated my TP. So I removed > testing, run dist-upgrade to current stable. (TP completely freeze > during the systemd upgrade) Then I rebooted and exactly the same problem. I > finished the upgrade (due to previous crash)

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

2021-09-03 Thread Ďoďo
Hi, what a nice coincidence. Yesterday I noticed that some autoupgrade fully updated my TP. So I removed testing, run dist-upgrade to current stable. (TP completely freeze during the systemd upgrade) Then I rebooted and exactly the same problem. I finished the upgrade (due to previous crash) and

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

2021-09-03 Thread intrigeri
Hi, Ďoďo (2021-04-11): > Hi, yes, I do agree the problem is in libc dependencies. I'm glad we're on the same page here. > Yes, I am using testing and I just did allow the apt to upgrade all > the recommended packages. > […] > Otherwise I do not understand your comment about "running testing on

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

2021-04-11 Thread Ďoďo
ok, so I did remove stretch update from the sources. Then apt update, upgrade, reboot and crash again during the boot. On Sun, Apr 11, 2021 at 3:32 PM Ďoďo wrote: > 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

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

2021-04-11 Thread Ď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

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

2021-04-02 Thread intrigeri
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

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

2021-02-19 Thread Ivanecky Jozef
Package: libapparmor1 Version: 2.13.6-9 Severity: important X-Debbugs-Cc: dodo...@gmail.com Dear Maintainer, * What led up to the situation? apt update; apt upgrade * What exactly did you do (or not do) that was effective (or ineffective)? I am no more able to boot the system *