Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Maybe a bad Debian package for 64-bit Wheezy/M12?

Post Reply
Message
Author
User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15657
Joined: Fri Dec 15, 2006 8:07 pm

Maybe a bad Debian package for 64-bit Wheezy/M12?

#1 Post by Stevo » Mon Apr 13, 2015 9:16 pm

http://forums.debian.net/viewtopic.php? ... 78#p574078

With a temporary fix. If it appears for 32-bit, the same type of fix should work, though the debs will be i386 instead of amd64.

User avatar
mmikeinsantarosa
Forum Guide
Forum Guide
Posts: 2270
Joined: Thu May 01, 2014 10:12 am

Re: Maybe a bad Debian package for 64-bit Wheezy/M12?

#2 Post by mmikeinsantarosa » Mon Apr 13, 2015 10:22 pm

They claim this after removing cairo-dock and requesting

Code: Select all

apt-get upgrade
I just installed our latest cairo-dock-3.40 on an MX14-4 VM that needed updates, ran it, removed cairo-dock then, performed the upgrade no problem. Maybe it's only for 64 bits or my timing is off.
LT: MX17.1 Quad Core model: Intel Core i7-6820HQ Kernel: 4.16.0-12.1-liquorix-amd64 (64 bit)
DT: Intel(R) Core i5-3.1GHz Kernel~3.9-1-mepis64 x86_64

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15657
Joined: Fri Dec 15, 2006 8:07 pm

Re: Maybe a bad Debian package for 64-bit Wheezy/M12?

#3 Post by Stevo » Mon Apr 13, 2015 10:45 pm

It's not really anything to do with cairo-dock, except that it uses a library that many other packages do, and it has to do with this particular version on 64-bit: libxrender1 (= 1:0.9.7-1+deb7u1+b1)

32-bit upgraded without a problem, so it's just 64-bit. That's a bit worrisome, since a packaging file install error in the build should have affected all platforms, so maybe just the 64-bit package was corrupted. It does not seem that the apt system does any checksums or checks the hashes of the files.

User avatar
mmikeinsantarosa
Forum Guide
Forum Guide
Posts: 2270
Joined: Thu May 01, 2014 10:12 am

Re: Maybe a bad Debian package for 64-bit Wheezy/M12?

#4 Post by mmikeinsantarosa » Mon Apr 13, 2015 10:57 pm

[quote='steveo"]and it has to do with this particular version on 64-bit: libxrender1 (= 1:0.9.7-1+deb7u1+b1)[/quote] Well my m12 64bit desktop has that same package and a 32 bit version libxrender1:i386 and they are both looking to be updated.
I think I'll wait.
LT: MX17.1 Quad Core model: Intel Core i7-6820HQ Kernel: 4.16.0-12.1-liquorix-amd64 (64 bit)
DT: Intel(R) Core i5-3.1GHz Kernel~3.9-1-mepis64 x86_64

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15657
Joined: Fri Dec 15, 2006 8:07 pm

Re: Maybe a bad Debian package for 64-bit Wheezy/M12?

#5 Post by Stevo » Mon Apr 13, 2015 11:49 pm

Or that command I posted in the Debian thread will get past it.

User avatar
mmikeinsantarosa
Forum Guide
Forum Guide
Posts: 2270
Joined: Thu May 01, 2014 10:12 am

Re: Maybe a bad Debian package for 64-bit Wheezy/M12?

#6 Post by mmikeinsantarosa » Tue Apr 14, 2015 12:41 pm

darn the torpedoes. m12 64 updated no problemo.
LT: MX17.1 Quad Core model: Intel Core i7-6820HQ Kernel: 4.16.0-12.1-liquorix-amd64 (64 bit)
DT: Intel(R) Core i5-3.1GHz Kernel~3.9-1-mepis64 x86_64

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15657
Joined: Fri Dec 15, 2006 8:07 pm

Re: Maybe a bad Debian package for 64-bit Wheezy/M12?

#7 Post by Stevo » Tue Apr 14, 2015 2:16 pm

Yes, the packagers pushed another update to 1:0.9.7-1+deb7u2 that fixes the issue.

Move along, nothing to see here.

Post Reply

Return to “Mepis 12 Beta”