Dear Michael Biebl, you wrote:
> Am 18.12.2015 um 15:59 schrieb Frank B. Brokken:
> > Is there a way to determine that? What I do to upgrade the system is run
> > 'aptitude update' and then 'aptitude upgrade'. Is there a log somewhere that
> > tells me what packages and versions were updated at what moments in time?
> 
> /var/log/dpkg.log is a low-level log.
> 
> and then there is one for aptitude at /var/log/aptitude

Thanks: I made the logs available at https://www.icce.rug.nl/systemd


> ...
> Btw, you mentioned that this happened after an upgrade. Which previous
> version did you run which worked fine? Which other packages were
> upgraded along with it?

Tue, Dec  1 2015 14:07:23 +0100: 
    the aptitude log shows an upgrade from systemd 227-2 to 228-2 

dpkg log: 2015-12-01 14:08:42 upgrade systemd:i386 227-2 228-2

dpkg log: 2015-12-03 08:30:01 upgrade systemd:i386 228-2 215-17+deb8u2

Thu, Dec  3 2015 08:31:37 +0100
    the aptitude log shows an upgrade from systemd 215-17+deb8u2 -> 228-2

dpkg log: 2015-12-03 08:31:40 upgrade systemd:i386 215-17+deb8u2 228-2

and then, recently, by me trying to downgrade:

dpkg log: 2015-12-17 12:59:12 upgrade systemd:i386 228-2 228-2
dpkg log: 2015-12-18 16:15:37 upgrade systemd:i386 228-2 215-17+deb8u2
dpkg log: 2015-12-18 16:17:11 upgrade systemd:i386 215-17+deb8u2 228-2

Before Dec 1 no updates were recorded for systemd or udev, and until the
upgrades early December everything ran fine.




> If you downgrade systemd/udev, does the problem go away?

As I feared, downgrading is difficult because of the many reverse
dependencies. 

I looked at 

    ftp://ftp.de.debian.org/debian/pool/main/s/systemd/

which is the mirror I usually use for earlier .deb files, but the one before
228-2 is 215-17, and 227-2 is only available as source archives and not AFAICS
as .deb packages.

I'll add the debug entry next (cf. your mail from Date: Fri, 18 Dec 2015
03:15:15 +0100) and let you know the results.


-- 
    Frank B. Brokken
    Center for Information Technology, University of Groningen
    (+31) 50 363 9281 
    Public PGP key: http://pgp.surfnet.nl
    Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA

Attachment: signature.asc
Description: PGP signature

Reply via email to