Bug#827618: similar bug w/ linux-image-4.7.0-1-amd64{,-unsigned}

2016-09-22 Thread Ben Hutchings
On Thu, 2016-09-22 at 16:28 +0200, Felix C. Stegerman wrote:
> Hi,
> 
> This time I replaced linux-image-4.7.0-1-amd64 w/
> linux-image-4.7.0-1-amd64-unsigned.  Then I ran:
> 
> $ sudo aptitude purge ~c
> ...
> Purging configuration files for linux-image-4.7.0-1-amd64 (4.7.2-1+s1) ...
> ...
> rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty
> ...
> 
> Not only did this cause dpkg to fail, it also removed modules.alias
> etc.  So replacing the signed kernel package with the unsigned one
> still causes some problems.

I think I misunderstood this bug originally.  However it was reported
again as #836282 and I think it's really fixed in version 4.7.4-1.

Ben.

-- 
Ben Hutchings
A free society is one where it is safe to be unpopular. - Adlai
Stevenson

signature.asc
Description: This is a digitally signed message part


Bug#827618: similar bug w/ linux-image-4.7.0-1-amd64{,-unsigned}

2016-09-22 Thread Felix C. Stegerman
Hi,

This time I replaced linux-image-4.7.0-1-amd64 w/
linux-image-4.7.0-1-amd64-unsigned.  Then I ran:

$ sudo aptitude purge ~c
...
Purging configuration files for linux-image-4.7.0-1-amd64 (4.7.2-1+s1) ...
...
rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty
...

Not only did this cause dpkg to fail, it also removed modules.alias
etc.  So replacing the signed kernel package with the unsigned one
still causes some problems.

- Felix


signature.asc
Description: PGP signature