[SOLVED] Problem with initramfs dependincies

[vilde]

stuck on this on d-u today,

Code: [Select]

Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 initramfs-tools-core : Breaks: initramfs-tools (< 0.121~) but 0.120+nmu1 is installedapt-get -f install doesn't solve it but I can'tget the output in english to work so I can't show it here

[musca]

Hello vilde,

did you put initramfs-tools on hold?

Both packages should be version 0.123,
but 0.120+nmu1 is an older fix from siduction extra repo.

Please check with "apt-mark showhold".

Greetings
musca

[vilde]

Hello vilde,

did you put initramfs-tools on hold?

Both packages should be version 0.123,
but 0.120+nmu1 is an older fix from siduction extra repo.

Please check with "apt-mark showhold".

Greetings
musca

Yes when I got this problem it reminded me that it had been hold back on d-u before. I did unhold it but the problem is there now anyway.

[vilde]

I did change my locales to English (so you can  read) and here is how it looks like now:

Code: [Select]

root@siductionbox:/home/media# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 initramfs-tools-core : Breaks: initramfs-tools (< 0.121~) but 0.120+nmu1 is installed
E: Unmet dependencies. Try using -f.
root@siductionbox:/home/media# apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  initramfs-tools
The following packages will be upgraded:
  initramfs-tools
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
Need to get 0 B/63.4 kB of archives.
After this operation, 132 kB disk space will be freed.
Do you want to continue? [Y/n]
Reading changelogs... Done
(Reading database ... 256214 files and directories currently installed.)
Preparing to unpack .../initramfs-tools_0.123_all.deb ...
dpkg: error processing archive /var/cache/apt/archives/initramfs-tools_0.123_all.deb (--unpack):
 too-long line or missing newline in '/var/lib/dpkg/info/initramfs-tools.triggers'
Errors were encountered while processing:
 /var/cache/apt/archives/initramfs-tools_0.123_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1) I also had other (don't know if they are related) issues on the d-u today and had to do a fchk on my root harddisk to be able to continue, maybe something happened then also?

[melmarker]

apt-mark showhold - remove any holds, if there are any - really, you should only use holds if you're absolutely sure that you know what you do. And be absolutely sure you can handle the results.

apt install initramfs-tools initramfs-tools-core

[vilde]

apt-mark showhold - remove any holds, if there are any - really, you should only use holds if you're absolutely sure that you know what you do. And be absolutely sure you can handle the results.

apt install initramfs-tools initramfs-tools-core

There was a problem for some time ago when it was advised to pot initramfs on hold, probably I did that, I have seen that it was hold back on my d-u:s, I thought it was apt who kept it back. Anyhow, I tried the suggested install but I get stuck on the same problem (I think) -f doesn't help either.

Code: [Select]

root@siductionbox:/home/media# apt install initramfs-tools initramfs-tools-core
Reading package lists... Done
Building dependency tree       
Reading state information... Done
initramfs-tools-core is already the newest version (0.123).
The following packages will be upgraded:
  initramfs-tools
1 upgraded, 0 newly installed, 0 to remove and 44 not upgraded.
3 not fully installed or removed.
Need to get 0 B/63.4 kB of archives.
After this operation, 132 kB disk space will be freed.
Do you want to continue? [Y/n]
Reading changelogs... Done
(Reading database ... 256214 files and directories currently installed.)
Preparing to unpack .../initramfs-tools_0.123_all.deb ...
dpkg: error processing archive /var/cache/apt/archives/initramfs-tools_0.123_all.deb (--unpack):
 too-long line or missing newline in '/var/lib/dpkg/info/initramfs-tools.triggers'
Errors were encountered while processing:
 /var/cache/apt/archives/initramfs-tools_0.123_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[der_bud]

   ... 

Code: [Select]

too-long line or missing newline in '/var/lib/dpkg/info/initramfs-tools.triggers'   ...

What does that mentioned file look like on your system? Here it's one line containing "interest update-initramfs" and a second (empty) newline.

[vilde]

@der-bud Yes, that file was a mess, I did something that maybe is stupid but I tok that file from another installation and copied it over the corrupt one and the I did what melmarker suggested

"apt install initramfs-tools initramfs-tools-core"

and that solved the problem, now I could do a real d-u.

BUT, I got some more messages that there where some files wrong

Code: [Select]

Processing triggers for libc-bin (2.22-1) ...
ldconfig: /usr/lib/libvorbisidec.so.1 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: /usr/lib/libvorbisidec.so.1.0.3 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: /usr/lib/libvcdinfo.so.0.2.0 is not an ELF file - it has the wrong magic bytes at the start.

ldconfig: /usr/lib/libvcdinfo.so.0 is not an ELF file - it has the wrong magic bytes at the start.
As I wrote before I had to repair the root file system so maybe/probably some more files are corrupted, anyhow the computer seems to work as it shall for the moment.

[vilde]

I will now mark this thread as solved

I did copy the rest of the faulty files from another installation.

All this was probably my fault, two things:

1 forgot that I put an application on hold,

2 Dont laugh to much
I was running this computer with a test ms-os on another hd, switched of the computer a pulled out the hd, pulled in my ordinary hd with siduction on and then I noticed that the computer was still running, probably some changes on the hd was done and therefore I had to run fsck with a lot of corrections needed. I was surprised that siduction started. Anyway this is a non important multimedia computer running my tv, no important files, and if more problems occur then I do a clean installation.

[musca]

You almost invented hotplug.

[vilde]

You almost invented hotplug.