Am 24.06.2012 03:31, schrieb Pierre Bernhardt:
> Am 23.06.2012 14:13, schrieb Touko Korpela:
>> On Sat, Jun 23, 2012 at 01:13:04PM +0200, Pierre Bernhardt wrote:
>>> Package: initramfs-tools
>>> Version: 0.106
>>> Severity: critical
>>> Tags: upstream
>>> Justification: breaks the whole system
> 
>> This lists both 2.6.32-5 and 3.2.0-2 kernels.
>> What kernel version do you try to boot, and is its initramfs updated?
> 3.2.0-2 is normally the one I start the system.
> 
>> By default only most recent kernel does have initramfs updated when updating
>> packages.
>> Your setup has many moving parts that can go wrong.
>> Please list versions of mdadm, dmsetup, libdevmapper*, *cryptsetup*
> root@nihilnihil:~# dpkg -l mdadm dmsetup libdevmapper* cryptsetup
> Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
> | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
>          Halb installiert/Trigger erWartet/Trigger anhängig
> |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
> ||/ Name                            Version                         
> Beschreibung
> +++-===============================-===============================-==============================================================================
> ii  cryptsetup                      2:1.1.3-4squeeze2               
> configures encrypted block devices
> ii  dmsetup                         2:1.02.74-4                     Linux 
> Kernel Device Mapper userspace library
> un  libdevmapper1.02                <keine>                         (keine 
> Beschreibung vorhanden)
> ii  libdevmapper1.02.1:amd64        2:1.02.74-4                     Linux 
> Kernel Device Mapper userspace library
> ii  mdadm                           3.2.5-1                         tool to 
> administer Linux MD arrays (software RAID)
> 
> Hopefully this whill help
cryptsetup was the problem. After installing cryptsetup from the testing
release 2:1.4.3-2 and rerunning update-initramfs -k all -u the problem has been
gone.

I found the solution by comparing the installed package source with sent
apt-cache policy command.

So you're right because it looks like a broken dependency or not exitend
dependency. In cryptset there is only shown an suggestion to initramfs-tools.

So I guess it is not a problem of initramfs-tools, more like a problem
between cryptsetup and another packages?


Cheers...
Pierre






--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to