For those in testing who came up on the libmspack install that affects cabextract, what I have done is as root
echo cabextract hold | dpkg --set-selections
according to http://osdir.com/ml/general/2015-01/msg07784.html
it should clear up soon. When it does
echo cabextract install | dpkg --set-selections
Last edited by paxmark1 (2015-01-26 01:39:26)
Jean Vanier wrote "Being Human" and "A Short History of Progress" by Ronald Wright. Gotta love the Massey Lectures.
Not only cabextract, dpkg has been nearly a week that is shown with a serious bug same as cabextract, they both appear on my terminal a week ago. Both on hold btw...
The following packages will be upgraded: dpkg dpkg-dev libdpkg-perl 3 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 5,545 kB of archives. After this operation, 401 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ftp.us.debian.org/debian/ jessie/main dpkg i386 1.17.23 [2,941 kB] Get:2 http://ftp.us.debian.org/debian/ jessie/main dpkg-dev all 1.17.23 [1,539 kB] Get:3 http://ftp.us.debian.org/debian/ jessie/main libdpkg-perl all 1.17.23 [1,065 kB] Fetched 5,545 kB in 10s (516 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done serious bugs of dpkg (1.17.22 → 1.17.23) <Outstanding> b1 - #774794 - dpkg: Add breaks for new trigger cycles b2 - #775124 - dpkg-statoverride with unknown group breaks any subsequent package installation Summary: dpkg(2 bugs) Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
Deb Devs seems too slow to adjust them, both packages have really serious for not says critical bug issue. I wish they'll run faster.
Well done to make aware people on testing/sid regarding these bugs.
Thanks for the 'heads-up' on these packages... New upgrade to Jessie this last weekend.
Ready to start fixing and tweaking system if needed...
Intel Pentium 4 150 GB HDD 4 GB RAM
Do i need "cabextract" at all? his new "libmspack0" which is parked for a long time in transition on jessie.
I just want to know do i really need to have both cabextract/libmspack0 on my system, can i safely remove?
Cabextract is a program which unpacks cabinet (.cab) files, which are a form of archive Microsoft uses to distribute their software and things like Windows Font Packs.
The purpose of libmspack is to provide both compression and decompression of some loosely related file formats used by Microsoft. The intention is to support all of the following formats: COMPRESS.EXE [SZDD], Microsoft Help (.HLP), COMPRESS.EXE [KWAJ], Microsoft Cabinet (.CAB), HTML Help (.CHM), Microsoft eBook (.LIT), Windows Imaging Format (.WIM), Exchange Offline Address Book (.LZX).
I never use any those things like .wim, cab chm, lit etc...
Edit: got rid the cabextract because I have not any interest to use it. Thanks to paxmark1 for describing some info.
Thanks in advance,
Last edited by Nili (2015-02-03 07:33:03)
I didn't remove cabextract because i have reading around needed for some Microsoft's TrueType fonts like Arial , Verdana etc... I want to use these fonts so i didn't remove cabext.... Today transition for cabextract/libmspack0 ended too much time run but ended. In Jessie the libmspack0 is fixed.
Start-Date: 2015-02-08 08:59:18 Commandline: apt-get dist-upgrade Install: libmspack0:i386 (0.5-1, automatic) Upgrade: cabextract:i386 (1.4-4+b1, >1.4-5) End-Date: 2015-02-08 08:59:22
Now remain only a fix for dpkg which still is in transition.
cabextract: Installed: 1.4-5 Candidate: 1.4-5 Version table: *** 1.4-5 0 500 http://ftp.us.debian.org/debian/ jessie/main i386 Packages 100 /var/lib/dpkg/status
dpkg 1.17.24 [FIXED][SOLVED] too by debian.
Last edited by Nili (2015-03-29 06:54:23)