LMDE BREAKAGES - tracking TESTING

[gcp]

.
debian-multimedia.org considered harmful - redux

http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-April/026077.html

Source:
http://www.debian-news.net/2012/05/20/d ... 14th-2012/
... the relationship between pkg-multimedia maintainers team and the unofficial
debian-multimedia.org repository [18]....

Solution:
I removed the debian-multimedia repos, removed all dmo packages,
reinstalled needed packages from pure Debian.
All easily done with Synaptic.
(but Handbrake-gtk is lost for me)

[zerozero]

DebianMultimedia FAQ
Marillat provides a service that debian doesn't and can't provide.

[BostonPeng]

Thanks for that link, zero. It told me things I didn't even realize I should be asking about. I'm realizing my new laptop should be 32-bit rather than 64-bit just for compatibility with some 32-bit apps I need but once I rebuild the beastie I'm looking forward to getting back to tracking Testing.

[Chris M]

Sunday night, May 20, US East Cost minor UD hold back on LMDX x64:

libavcodec52 and libavformat52 updates are being held back

Forcing libavcodec52 would remove:

libavformat52
libmjpegtools-1.9
libquicktime1

Follow this link for explanation of problem - report.php?f=199&p=582026

Also, removal of libavcodec52 and the other 3 can be done safely, as their replacements are already installed.
I just went through this several hours ago.

craigevil, I set all to Pin-Priority: 500 (per zz' advice), and I had the mint repo commented out on this freshly installed LMDX x64.

I went to verify this, and did a DU (sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade), and now there are no hold backs. So it either required a re-boot (doubtful), or Debian must have done something.

Don't know, but the installed version of libavcodec52 is 5:0.6.3-0.0. Can't remember the versions I was dealing with last night.

libavcodec53 version 7:0.10.3-dmo1 is also installed.

Edit:

etc/apt/preferences is:

Code: Select all

Package: *
Pin: release o=linuxmint
Pin-Priority: 500

Package: *
Pin: origin packages.linuxmint.com
Pin-Priority: 500

Package: *
Pin: release o=Debian
Pin-Priority: 500

From the latest ISO install, there is no apt preferences reference to multimedia. If you want to use Debian Multimedia, do you have to establish it?

[viking777]

I find it difficult to understand why I am the only person reporting this, it must mean either that I am the only person still using gnome-shell on LMDE or it is something very specific to my machine, however after updating today, gnome shell has been almost completely trashed. It boots into fallback, but even that is corrupt. The top and bottom of the screen seem to be unused and the desktop has three of everything - three shutdown buttons, three desktop pagers, three clocks. I am sure you get the picture, and it isn't a pretty one

I reverted to a disk image from a week ago and retried the updates with gnome-shell pinned, along with clutter, mutter and various other things that wanted to remove the older version of gnome-shell, but the result was no different, complete rubbish.

It doesn't matter that much to me for a couple of reasons. Firstly I still have Fluxbox installed on LMDE and it works perfectly, secondly I have been anticipating this kind of breakage for some while now and months ago replaced LMDE with Debian Testing as my #1 distro (which works perfectly with the same/similar update). It just seems like this is the end of the road for those of us wanting to use gnome-shell on LMDE - my fault for not wanting to use Cinnamon I guess

I report it here in case someone else if experiencing similar problems, but I guess nobody is or I would have read it already. Not really looking for answers, I already have them - Fluxbox and Debian Testing. When I can get hold of Mint 13 I will probably replace LMDE with that anyway. I dont have the bandwidth to get it right now, I used two weeks worth of that messing around with updates for LMDE today.

LLAP

(The acronym is from Star Trek - work it out )

[GeneC]

LLAP

(The acronym is from Star Trek - work it out )

[zerozero]

it must mean either that I am the only person still using gnome-shell on LMDE or it is something very specific to my machine

you know you're not the only one using the shell with lmde, so must be something specific to your setup, because

so the question is (if you want )
- what the content of the preference file?
- what has been washed out in this particular install that hasn't been in debian proper? (and i have both installed here as well, they are both working, can't really tell the difference between one and the other)
- BUT lmde requires now that a few adjustments are made (the most important imo we talked about it here for ages now - the standard preferences file is fine for the latest/incoming setups, kills any setup different from that.

I reverted to a disk image from a week ago and retried the updates with gnome-shell pinned, along with clutter, mutter and various other things that wanted to remove the older version of gnome-shell, but the result was no different, complete rubbish.

you shouldn't need to pin anything, gtk3.4, clutter, cogl (the all gang ) are coming in and in the same way in wheezy or lmde, the transition is not perfect, but the system are stable (heck, as you can see in your testing partition).

i'm telling this for so long now: you (we) are not using lmde-standard anymore, so please adapt it (adapt yourselves) or else ...

google (and Gene ) know what LLAP is. YW

[GeneC]

............................................................
- BUT lmde requires now that a few adjustments are made (the most important imo we talked about it here for ages now - the standard preferences file is fine for the latest/incoming setups, kills any setup different from that.
......................
i'm telling this for so long now: you (we) are not using lmde-standard anymore, so please adapt it (adapt yourselves) or else ...

google (and Gene ) know what LLAP is. YW

Viking
Took me ages to get over my stubborness and change my apt-pinning (much to zz's shagrin. ).
Its really the only way to run LMDE Testing or SID. I am fully updated in SID, but waiting on a couple of Gnome 3.4 updates to come through before re-installing Shell

Dammit, Spock! I'm a doctor, not a Linux Geek!

[viking777]

Thanks Gene and zerozero. So apt-pinning is what makes it all work??

I guess you must be right, but I have never used it before and I don't think I want to start using it now. For that reason I haven't read a single word about the subject, in fact imho, if you have to start using apt pinning to make a distro work properly then that distro is already broken.

I will stick with my own solutions for now, I don't have the time or the bandwidth to sort out the inevitable mistakes if I start learning something new, so I will leave it till the autumn (that's 'fall' Gene ) or maybe I will leave it altogether.

Thank you both anyway.

[Chris M]

viking, I think Gene was verifying zz' recommendation to change your apt preferences file (etc/apt/preferences) settings if you're going to roll along in Testing.

clem's apt preferences settings work for his Latest scheme, but if you're going to go with pure Debian Testing (repos), clem's default Pin-Priority settings create issues.

If you go with the following, you should not have the types on problems that zz has spoken about before (and that you may be running into).

etc/apt/preferences for following Debian Testing should be:

Code: Select all

Package: *
Pin: release o=linuxmint
Pin-Priority: 500

Package: *
Pin: origin packages.linuxmint.com
Pin-Priority: 500

Package: *
Pin: release o=Debian
Pin-Priority: 500

I'm no guru, but I think this is what's at issue.

[GeneC]

Chris

Thanks for making that more clear, I should have done a better job myself.

Yes, Your just 'adjusting' Clem's default ect/apt/preferences so that Mint and Debian repos have equal preference. This allows some needed Debian packages to install so you can do full Distribution-Updates.

[zerozero]

From the latest ISO install, there is no apt preferences reference to multimedia. If you want to use Debian Multimedia, do you have to establish it?

i missed earlier this [edit], no, not as i see it, the debian 500 rule sets the right priority to debian-multimedia as well.

[...] So apt-pinning is what makes it all work??

[...]if you have to start using apt pinning to make a distro work properly then that distro is already broken.

not here, resetting the default pin priorities to zero (basically what we have done setting'em all to 500) is what makes it work, re. testing/sid.

and tbh we could as well just delete the file and be done with it the way we have to adjust it, it serves no purpose at all (it's just a legacy)

[viking777]

Thanks to everyone for putting me right about apt-pinning. I was under the misapprehension that you were doing something complicated with it, not simply making the priorities all equal (OK - I hadn't read the discussion at all ). That is no problem for me, and is already done. Of course it is a bit too late to repair the damage to gnome-shell, and like I said before, I don't have the bandwidth available right now to start again. However it is no hardship working with Fluxbox once again, in fact it is a positive joy to see it start up 20-30 seconds faster than gnome-shell (and the decrease in start up time is all after the login screen not before, so there is no doubt that gnome-shell is the culprit here). So I will just stick with Fluxbox for the time being and maybe the damage will sort itself out or maybe will have to wait till I get home and don't have to use mobile broadband.

Thanks again for the contributions.

[Lippy]

I've just chanced the upgrade of gtk3-engines-unico to 1.0.2 again, and it looks like whatever was causing those graphical glitches is gone now. Who knows; maybe it wasn't playing nice with GTK+ 3.2. Anyway, it's one less package to hold back.

[GregE]

Thanks to everyone for putting me right about apt-pinning. I was under the misapprehension that you were doing something complicated with it, not simply making the priorities all equal (OK - I hadn't read the discussion at all ). That is no problem for me, and is already done. Of course it is a bit too late to repair the damage to gnome-shell, and like I said before, I don't have the bandwidth available right now to start again. However it is no hardship working with Fluxbox once again, in fact it is a positive joy to see it start up 20-30 seconds faster than gnome-shell (and the decrease in start up time is all after the login screen not before, so there is no doubt that gnome-shell is the culprit here). So I will just stick with Fluxbox for the time being and maybe the damage will sort itself out or maybe will have to wait till I get home and don't have to use mobile broadband.

Thanks again for the contributions.

I am very much still a Gnome Shell user, but I have updated to Sid rather than testing. I lost my Gnome Shell a few weeks ago and had to use Xfce for a week. But I kept updating and eventually the Shell came back to life. The issues are caused by the 3.4 packages coming through and problems with libcogl.

I presume that this is what is happening to you, except delayed by a few weeks as the packages drift down from Sid to Testing. It should just get better.

I always have Xfce installed as a fallback. It barely takes up any room and is a tiny download - and is a bit more friendly than Fluxbox.



ps my solution to apt pinning is to just get rid of it altogether. Just delete /etc/apt/preferences and then everything is equal by default.

[iLobster]

Can't update evolution-data-server, evolution-data-server and libcamel-1.2-29.
Anybody know why? What exactly do they not like?

[zerozero]

the last updates i have related with those pkgs is from may/15, here viewtopic.php?f=198&t=67502&start=1780#p579740
are you trying to hold back cinnamon?

[iLobster]

the last updates i have related with those pkgs is from may/15, here viewtopic.php?f=198&t=67502&start=1780#p579740
are you trying to hold back cinnamon?

No, Cinnnamon installed as UP2 manually.

[viking777]

I am sure nobody is remotely interested, as I am seemingly the only victim of this LMDE bug:

viewtopic.php?f=198&t=67502&view=unread#p582341

However, in case I am wrong I will post my solution. It took me ages to find it because I have been trying to find differences between Debian Testing which works, and LMDE which doesn't, but I couldn't find any, so in the end I went back to the trusty sgfxi and installed the latest Nvidia driver (295.53). After that it all worked again. Simple solution but effective.

Llap.

viking.

[zerozero]

the last updates i have related with those pkgs is from may/15, here http://forum.linuxmint.com/viewtopic.ph ... 80#p579740
are you trying to hold back cinnamon?

No, Cinnnamon installed as UP2 manually.

iLobster, you need to be a tiny bitty littly more verbose about it (repos you are using, apt policy of the packages, full output of the dist-upgrade command- you know that kind of things ) otherwise our crystal balls won't work

I am sure nobody is remotely interested, as I am seemingly the only victim of this LMDE bug:

[...] so in the end I went back to the trusty sgfxi and installed the latest Nvidia driver (295.53). After that it all worked again. Simple solution but effective.

Llap.

viking.