Hi Michael,
Michael Shuler wrote:
> Thanks for the details. #895473 reported a similar error on locally
> installed CA certificates, which I think may be related.
That other bug report indeed looks similar albeit not identical.
> I've tried a number of upgrades from a March 29 unstable chroot, as well
> as from stretch to unstable on openstack instances, on both amd64 and
> i386 (I don't think arch is dependent), and I've been unable to get a
> similar error to present itself.
Doesn't surprise me. From about ten machines with Debian unstable, I
only ran into that issue on two machines, one amd64 and one i386.
> Each way I've tried, I get the package-removed certificates prefixed
> properly and no errors, so haven't been able to reproduce this, yet. I
> will keep trying with different options and see if I can figure out
> where the problem is. If someone has a good way to reproduce, I'd
> appreciate it!
Sorry, can't help there at the moment as I have no idea what makes the
two machines, on which I ran into it, so special. I just wanted to add
some more facts:
Downgrading ca-certificates to the version from testing (20170717)
fixes the issue and seems to clean up the broken files, symlinks, …
well.
On all machines I ran into that issue I was no more able to run "apt
update" or similar, since I use HTTPS in my sources.list and
certificate validation failed and hence I was unable to download new
package lists and hence unable to download any package updates, too.
(That's why I've now downgraded ca-certificates on my two affected
machines.)
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
