Is it possible it could be because I put a package (I think it was a systemd package) on hold because apt warned me about a critical bug on systemd or udev about one week ago ?
2018-03-19 9:51 GMT+01:00 LEDUQUE Mickaël <mledu...@gmail.com>: > You're right, but honestly, I have no idea how this happened : > > $ dpkg -l systemd > Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder > | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/ > H=semi-installé/W=attend-traitement-déclenchements > |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) > ||/ Nom > Version Architecture > Description > +++-======================================================== > =========-=====================================-============ > =========================-================================== > ============================================================ > ========================================= > ii systemd:i386 > 238-2 i386 > system and service manager > > > 2018-03-18 23:20 GMT+01:00 Michael Biebl <bi...@debian.org>: > >> Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël: >> > No I don't think I have one >> > dpkg -l udev only shows udev and64 >> >> what about systemd? i386 or amd64 >> >> >> -- >> Why is it that all of the instruments seeking intelligent life in the >> universe are pointed away from Earth? >> >> >
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers