Hi again! On Tue, 7 May 2019 02:24:59 -0400 Gabriel Filion <gabs...@lelutin.ca> wrote: > On Mon, 29 Apr 2019 15:44:39 +0200 Santiago Vila <sanv...@unex.es> wrote: > > On Mon, Apr 29, 2019 at 01:22:18PM +0000, Holger Levsen wrote: > > > if we now could please focus on #928172 and ignore #927450 for now, > > > that would be great. (and "ignoring #927450" also means not mixing them > > > up.) > > > > Let's focus on #928172 if you like. I try not to mix them up, but I > > believe they are strongly related in the sense that the reason #928172 > > is serious now is that the package in stable still has #927450. > > so, I'm currently in this situation where the package doesn't upgrade. > and nothing else upgrades either because of this. > > is there a known way to work around the issue that the hook encounters > in order to unblock my install?
I reveived some help from anarcat on irc to work around this issue and unblock upgrades on my system. While I think a fix would be nice for this issue, I'm reporting here how I got around this in case others end up in the same situation as I was and are looking to continue upgrading their sid machine: "apt remove debian-security-support" was triggering the hook and made it impossible to remove the package, but "apt purge ..." did work. so in order to unblock things one might want to run: apt purge debian-security-support apt update && apt upgrade apt install debian-security-support cheers!
signature.asc
Description: OpenPGP digital signature
