LMDE BREAKAGES - tracking TESTING

[Gerd50]

What does it mean zerozero? Is there a difference between using mintupdate-debian or apt-get?

[dfx]

gstreamer0.10-lame seems to be obselete now

http://packages.debian.org/changelogs/p ... /changelog

gst-plugins-ugly0.10 (0.10.18-3) unstable; urgency=low
* Add lame to the ugly plugin set as it's available in Debian now (Closes: #636065).

-- Fabian Greffrath <fabian+debian@greffrath.com> Fri, 29 Jul 2011 13:33:09 +0200

[zerozero]

What does it mean zerozero? Is there a difference between using mintupdate-debian or apt-get?

what method you used to update the system? MU-debian? apt-get upgrade? apt-get dist-upgrade? synaptic?

[Gerd50]

I always use apt-get dist-upgrade. MU-debian is not installed.

[viking777]

gstreamer0.10-lame seems to be obselete now

http://packages.debian.org/changelogs/p ... /changelog

gst-plugins-ugly0.10 (0.10.18-3) unstable; urgency=low
* Add lame to the ugly plugin set as it's available in Debian now (Closes: #636065).

-- Fabian Greffrath <fabian+debian@greffrath.com> Fri, 29 Jul 2011 13:33:09 +0200

There must be something in this dfx. I just used ripperx to rip and encode an mp3 from a cd and it worked fine, listening to it now. So I don't seem to need the -lame plugin separately any more.

Thanks for the input.

So anyone who is holding the -ugly plugins might want to rethink that strategy.

[jompa89]

well, i saw the conflict this morning (5 a.m. just before go to work) and now 4 p.m it's still here (same as viking)

Code: Select all

Calculating upgrade... Done
The following packages will be REMOVED:
  gstreamer0.10-lame
The following packages will be upgraded:
  gstreamer0.10-plugins-really-bad gstreamer0.10-plugins-ugly liblzo2-2
  libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 policykit-1
7 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 1,411 kB of archives.
After this operation, 819 kB disk space will be freed.
Do you want to continue [Y/n]? n
Abort.
amadeu@amadeu ~ $ apt-cache policy gstreamer0.10-lame
gstreamer0.10-lame:
  Installed: 0.10.18-0.1
  Candidate: 0.10.18-0.1
  Version table:
 *** 0.10.18-0.1 0
        500 http://www.debian-multimedia.org/ testing/main amd64 Packages
        100 /var/lib/dpkg/status
amadeu@amadeu ~ $ apt-cache policy gstreamer0.10-plugins-ugly
gstreamer0.10-plugins-ugly:
  Installed: 0.10.18-1
  Candidate: 0.10.18-3
  Version table:
     0.10.18-3 0
        500 http://ftp.debian.org/debian/ testing/main amd64 Packages
 *** 0.10.18-1 0
        100 /var/lib/dpkg/status
amadeu@amadeu ~ $


post-edit: now i see why the differences here if you do apt-get upgrade this is what you get

Code: Select all

Reading state information... Done
The following packages have been kept back:
  gstreamer0.10-plugins-ugly
The following packages will be upgraded:
  gstreamer0.10-plugins-really-bad liblzo2-2 libpolkit-agent-1-0
  libpolkit-backend-1-0 libpolkit-gobject-1-0 policykit-1
6 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 924 kB of archives.
After this operation, 717 kB disk space will be freed.
Do you want to continue [Y/n]?


Does this mean that we'll get it later then? Since it is held back?

[wyrdoak]

I'm just doing the Mint testing. sudo apt-get upgrade All I got was the really bad one who comes up with these names?the ugly one is still 18-1.

[zerozero]

I always use apt-get dist-upgrade.

same as me. so, i don't get why the differences.

Does this mean that we'll get it later then? Since it is held back?

if you use apt-get dist-upgrade, you will, anyway you are not losing functionality, since it was enabled in ugly.
and you can see a bit more in the bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636065

[Gerd50]

Hi zerozero,

you wrote:

Gerd50 wrote:I always use apt-get dist-upgrade.

same as me. so, i don't get why the differences.

What i wonder about is, i didn't see this today on two systems:

Code: Select all

Calculating upgrade... Done
The following packages will be REMOVED:
  gstreamer0.10-lame

I only saw this:

Code: Select all

Reading state information... Done
The following packages have been kept back:
  gstreamer0.10-plugins-ugly

Maybe there is only a knot in my brain, because my english is really not the yellow of an egg
And it's not a big deal. As viking said, without the lame plugin, gstreamer is working fine

[nykur]

I always use apt-get dist-upgrade.

same as me. so, i don't get why the differences.

Does this mean that we'll get it later then? Since it is held back?

if you use apt-get dist-upgrade, you will, anyway you are not losing functionality, since it was enabled in ugly.
and you can see a bit more in the bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636065

So will MintUpdate not hold it back then? I've switched to MintUpdate instead of the normal apt-get since MintUpdate Debian came, even though I'm pointing to testing. It was my understanding this would probably become the default tool so I wanted to jump onboard I guess:-) But is it only to be default for those pointing to them update packs? For me it has worked more or less smoothly although I do have to leave the details window open for when prompted for confirmation. Guess there's no GUI for that yet.

I guess my question is: Is MintUpdate even intended for those pointed for testing? Or should I stop playing with it and stick to an apt-get terminal window? Or maybe one should not even update inside X anyway;-)

[AbeOwitz]

Hey there, trying to compile the Git version of Gimp, which requires a number of *dev files for libraries, but the available versions are behind the binaries, for example:

apt-get install libgdk-pixbuf2.0-dev

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libgdk-pixbuf2.0-dev : Depends: libgdk-pixbuf2.0-0 (= 2.23.5-1) but 2.23.5-3 is to be installed
Depends: gir1.2-gdkpixbuf-2.0 (= 2.23.5-1) but 2.23.5-3 is to be installed
E: Broken packages

Any way around this? Or did I goof in my repositories? (I tried both testing and incoming)

Code: Select all

# deb http://ftp.debian.org/debian testing main contrib non-free
deb http://security.debian.org/ testing/updates main contrib non-free
deb-src http://security.debian.org/ testing/updates main contrib non-free

deb http://packages.linuxmint.com/ debian main upstream import backport romeo
deb-src http://packages.linuxmint.com/ debian main upstream import backport romeo #Added by software-properties

#deb http://debian.linuxmint.com/latest testing main contrib non-free
#deb-src http://debian.linuxmint.com/latest testing main contrib non-free

deb http://debian.linuxmint.com/incoming testing main contrib non-free
deb-src http://debian.linuxmint.com/incoming testing main contrib non-free

deb http://www.debian-multimedia.org testing main non-free
deb-src http://www.debian-multimedia.org testing main non-free

Many thanks!

[mockturtl]

re: http://forums.linuxmint.com/viewtopic.php?f=141&t=67502&start=1000#p459814

@mads, afaik, you're tracking latest, can you please check what v. libcurl3-gnutls is in your system?

Code: Select all

libcurl3-gnutls:
  Installed: 7.21.7-1
  Candidate: 7.21.7-1
  Version table:
 *** 7.21.7-1 0
        500 http://ftp.debian.org/debian/ testing/main amd64 Packages
        100 /var/lib/dpkg/status


we may start having this kind of issues (dependencies problems) with multimedia repo in latest and incoming

incoming (Pack 2) has:

Code: Select all

$ apt-show-versions -a -p libcurl3-gnutls
libcurl3-gnutls 7.21.6-3 install ok installed
No stable version
libcurl3-gnutls 7.21.6-3 testing debian.linuxmint.com
libcurl3-gnutls 7.21.7-1 unknown ftp.debian.org
libcurl3-gnutls/testing uptodate 7.21.6-3

Just switched to the wheezy repo and I'm pulling down updates now; will report any problems.

EDIT: i686, amd64 machines both looking good after viking77's tip to remove/reinstall nvidia-kernel-dkms and nvidia-glx.
"Unsafe" updates are still available for:

• gstreamer0.10-plugins-ugly (0.10.18-1 --> 0.10.18-3)
• ntfs-3g (1:2011.1.15AR.4+2011.4.12-2 --> 1:2011.4.12AR.4-2)

(NB: to hide these, uncheck Preferences-->Update Method-->Include updates which require the installation or removal of other packages. Defaults to True; equivalently, apt-get dist-upgrade / aptitude full-upgrade)

One tip: if you're switching to wheezy from incoming, you might have 1 GB of updates to download! Watch your free space on your root partition (df -h), and run some housekeeping if you need room (aptitude clean).

[viking777]

I guess my question is: Is MintUpdate even intended for those pointed for testing?

Personally I don't think it is, certainly not the new version anyway and certainly not for the way I want to run my computer. I gave up on it quite a while back and now only use Synaptic or the command line. I have to say though that since I have not even seen the newer version of mintupdate my knowledge of this topic is less certain than others, so maybe wait for a few more comments before making up your mind.

[andrew5859]

Just my input on repositories.....when trying to ajust the repo's to point to squeeze & wheezy, this is what I get:

Could not download all repository indexes

The repository may no longer be available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and ensure the repository address in the preferences is correct.

"Failed to fetch http://www.debian-multimedia.org/dists/ ... 6/Packages 404 Not Found
Failed to fetch http://www.debian-multimedia.org/dists/ ... 6/Packages 404 Not Found
Some index files failed to download. They have been ignored, or old ones used instead."

Can anyone please explain this, why am I getting this message when squeeze is suppose to be a stable repo, or is it no longer relevant....thanks, cheers


Andrew

[tdockery97]

Make sure the entry in your sources.list conforms to this: http://debian-multimedia.org/.

[andrew5859]

So I should take out the "squeeze" repo's from update manager?

[viking777]

So I should take out the "squeeze" repo's from update manager?

Take it out or leave it in, that is up to you.

You just do what it says in the link that tdockery97 gave.

The address you are using is wrong.

[samriggs]

Hello all
Tried to do an update/upgrade todays on the wifes laptop and got a whole wack of errors
I added the list in file to make it easier.
Any help with this mess would be appreciates
Sam (and his wife who might hit in the head with the cast iron frying pan if it don't get fixed)

[andrew5859]

So I should take out the "squeeze" repo's from update manager?

Take it out or leave it in, that is up to you.

You just do what it says in the link that tdockery97 gave.

The address you are using is wrong.

Ok....that's all I needed to know...thanks viking

[zerozero]

Hey there, trying to compile the Git version of Gimp, which requires a number of *dev files for libraries, but the available versions are behind the binaries, for example:

have you already solved this?
because atm all those libs are in sinc
http://packages.debian.org/search?suite ... buf2.0-dev
http://packages.debian.org/search?suite ... ixbuf2.0-0
http://packages.debian.org/search?suite ... pixbuf-2.0

@Sam, if i remember correct, it's not the first time you get this error, and the other time around you reinstalled. what changed (what did you installed lately, what did you tweaked, anything(?), that brought that back?