Jessie-[Testing] explodes into life!!!

Hungry ghost · 05-13-2013, 11:50 AM

Quote:

Originally Posted by 273

Some of my packages have been updated to 8.0.5-4+b1 I went into Synaptic to see whether I can fix things as I sometimes have more luck than with apt, however it seems that some of the packages that need upgrading are broken.

Code:

E: /var/cache/apt/archives/libgl1-mesa-dri_8.0.5-4+b1_amd64.deb: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:amd64
E: /var/cache/apt/archives/libgl1-mesa-glx_8.0.5-4+b1_i386.deb: trying to overwrite shared '/usr/share/doc/libgl1-mesa-glx/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-glx:i386
E: /var/cache/apt/archives/libglapi-mesa_8.0.5-4+b1_amd64.deb: trying to overwrite shared '/usr/share/doc/libglapi-mesa/changelog.Debian.gz', which is different from other instances of package libglapi-mesa:amd64

I had a similar issue with the upgrades today, and I fixed it by forcing the installation of these packages (however, in my case, the problem was related to libglapi-mesa, libgl1-mesa-dri, and libglu1-mesa). Since what was being rewritten were simple changelog files and not a crucial library or something important, I guessed there wouldn't be a problem with overwriting these files (YMMV, though). To force the installation of these packages, simply execute the following:

Code:

dpkg --force-overwrite -i /var/cache/apt/archives/libgl1-mesa-dri_8.0.5-4+b1_amd64.deb

(and so on with the remaining packages).

You can also wait one or two days for things in the repos to settle down, if you want to play on the safe side.

273 · 05-13-2013, 12:05 PM

Quote:

Originally Posted by odiseo77

I had a similar issue with the upgrades today, and I fixed it by forcing the installation of these packages (however, in my case, the problem was related to libglapi-mesa, libgl1-mesa-dri, and libglu1-mesa). Since what was being rewritten were simple changelog files and not a crucial library or something important, I guessed there wouldn't be a problem with overwriting these files (YMMV, though). To force the installation of these packages, simply execute the following:

Code:

dpkg --force-overwrite -i /var/cache/apt/archives/libgl1-mesa-dri_8.0.5-4+b1_amd64.deb

(and so on with the remaining packages).

You can also wait one or two days for things in the repos to settle down, if you want to play on the safe side.

Thanks, that's sorted it out. I thought there was something I had done when I ran into a similar issue with testing but couldn't recall what it was.

goumba · 05-13-2013, 12:20 PM

I had big issues with deb-multimedia at times, a version conflict wanting to remove tons of packages, even GNOME. Unfortunately those are the risks you take when using third party repos and it was the source of a lot of nastiness on the Debian mailing list, because people were filing bugs against the official packages.

The only solution for now is to wait until you can get a version that doesn't conflict, unfortunately.

273 · 05-13-2013, 12:27 PM

I don't think I've had problems with deb-multimedia before -- I think the official Sid repositories do a good enough job of suggesting removing the entire system by themselves

.
I take it for granted that when running Sid sometimes you have to hold off for updates or temporarily remove a program and I can live with that fine. On one occasion I've even ended up making a simlink to a lib file to stop apt-get complaining. All part of the fun.
Edit: On this occasion the problems weren't deb-multimedia either.

Hungry ghost · 05-13-2013, 12:33 PM

Yeah, running Sid is way fun and educational

widget · 05-13-2013, 01:33 PM

Quote:

Originally Posted by odiseo77

Yeah, running Sid is way fun and educational

That is why, though I prefer running testing (for some reason), I use Sid as my back up OS.

One of the buggers will generally be working no matter what.

Hungry ghost · 05-13-2013, 02:07 PM

Quote:

Originally Posted by widget

That is why, though I prefer running testing (for some reason), I use Sid as my back up OS.

One of the buggers will generally be working no matter what.

Yes, that's a good practice. I have a laptop with Debian Testing which I rarely use and my desktop with Debian Sid, which is what I use most. I'm thinking it would probably be a good idea to install a secondary -- and more stable -- Linux OS in the desktop, just in case something breaks badly in Sid and I need my desktop urgently. This would also be good to recover Sid, in case something goes wrong.

widget · 05-13-2013, 06:40 PM

Quote:

Originally Posted by odiseo77

Yes, that's a good practice. I have a laptop with Debian Testing which I rarely use and my desktop with Debian Sid, which is what I use most. I'm thinking it would probably be a good idea to install a secondary -- and more stable -- Linux OS in the desktop, just in case something breaks badly in Sid and I need my desktop urgently. This would also be good to recover Sid, in case something goes wrong.

I have a LOT of installs (on an external - run with the internals disabled in bios) so that I can abuse the buggers.

I try to keep this install of testing and the Sid install that shares /home running.

I have Squeeze installed set up for security that is my ultimate backup. Seldom use it for anything but financial transactions. Just too boringly reliable. But it is there if I ever need it. Used it for a whole 5 days during the Wheezy as testing cycle. MY fault that I broke both Wheezy AND Sid.

What a maroon as Bugs Bunny would say.

I was pretty hot stuff running Windows. You can pretty easily be that. Will never live long enough to be much with Linux. Have never gotten over the first excitement of being in that much control of your OS. I have to have victim installs to mess with. Break the buggers all the time. Try to learn to fix them. Getting better all the time. Just too much to learn for a grumpy geezer.

Doesn't mean I can't try. Never surrender, never give up. (Yes I love stupid movies).

EDDY1 · 05-14-2013, 02:05 AM

Quote:

Originally Posted by odiseo77

Yes, that's a good practice. I have a laptop with Debian Testing which I rarely use and my desktop with Debian Sid, which is what I use most. I'm thinking it would probably be a good idea to install a secondary -- and more stable -- Linux OS in the desktop, just in case something breaks badly in Sid and I need my desktop urgently. This would also be good to recover Sid, in case something goes wrong.

I keep an external hdd with debian on it, as long as the computer I want o repair boots from usb I'm good. For linux computers I just boot from extetrnal run update-grub to make entry in grub which will boot os in most cases, remove external install grub.

k3lt01 · 05-14-2013, 04:22 AM

Quote:

Originally Posted by widget

Doesn't mean I can't try. Never surrender, never give up. (Yes I love stupid movies).

Take a look here then.

widget · 05-14-2013, 07:47 AM

Quote:

Originally Posted by k3lt01

Take a look here then.

That is kind of sad.

EDDY1 · 05-15-2013, 07:24 PM

Finally put my main machine back online & upgrading it to jessie after updating the wheezy installation, the upgrade to jessie is only 177 packages, hopefully I don't have to reinstall NVIDIA modules(fat chance).

EDDY1 · 05-17-2013, 11:42 AM

Quote:

Originally Posted by EDDY1

Finally put my main machine back online & upgrading it to jessie after updating the wheezy installation, the upgrade to jessie is only 177 packages, hopefully I don't have to reinstall NVIDIA modules(fat chance).

After upgrade machine was in fallback mode so I downloaded the latest nvidia driver & installed it, now it's working fine.