LMDE BREAKAGES - tracking TESTING

[xircon]

Ran an update:

Code: Select all

The following packages will be REMOVED:
  libavcodec-dev libavfilter-dev libxvidcore4-dev
The following packages have been kept back:
  libavdevice52 libavdevice53
The following packages will be upgraded:
  libxvidcore4
1 upgraded, 0 newly installed, 3 to remove and 2 not upgraded.
Need to get 298 kB of archives.
After this operation, 10.9 MB disk space will be freed.


Will ignore it for the time being.

Steve

[viking777]

My version of that package was updated without problem this morning. However I don't have any of those -dev packages installed. Do you need them? If so then waiting is a good idea, if not, allow them to be removed.

[xircon]

I probably did need them, may still need them, but can't remember why I installed them

[viking777]

I probably did need them, may still need them, but can't remember why I installed them

I am not unfamiliar with that feeling

[secipolla]

You only need them if you build something from source that depends on them. So you can remove them and install them again if you need them to build something.

[GeneC]

Gene, i saw in the other thread that you have already solved your theme-quest (and good looking ) but, today was mint-x theme that got gtk3 compatibility and not orta (although they are similar)

Hey "ZZ"

Yes, new themes that work with both GTK2 and GTK3 can be easily found and new ones are appearing daily

On the GTK3 theme thread, "MeV" did a nice job of changing the blue highlights in the dark ATOLM theme to Minty green. I works very nicely with Mint.
http://forums.linuxmint.com/viewtopic.php?f=141&t=78268&start=20#p458161

"Minty_Freshness" theme by "Skies of Ezekial" also works nicely.
http://forums.linuxmint.com/viewtopic.php?f=141&t=78268&start=20#p458030

Thanks for all your hard work, and good job as new moderator!

[DoNotUnderstand]

Went to run an update today got the following

Code: Select all

The following packages will be REMOVED:
  mythtv mythtv-backend mythtv-frontend mythtv-themes
The following packages have been kept back:
  libavdevice52 libavdevice53 libmyth-0.24-0
The following packages will be upgraded:
  ffmpeg libavcodec52 libavcodec53 libavfilter1 libavfilter2 libavformat52
  libavformat53 libavutil50 libavutil51 libmythavcodec52 libmythavcore0
  libmythavformat52 libmythavutil50 libmythpostproc51 libmythswscale0
  libpostproc51 libswscale0 libswscale2 libx264-116 libxvidcore4
  live-installer-slideshow mint-translations mint-x-theme mythtv-common
  mythtv-database mythtv-doc python-mythtv
27 upgraded, 0 newly installed, 4 to remove and 3 not upgraded.

I'm not actually using Mythtv any more, otherwise I might be a little worried.

[viking777]

Went to run an update today got the following

Code: Select all

The following packages will be REMOVED:
  mythtv mythtv-backend mythtv-frontend mythtv-themes
The following packages have been kept back:
  libavdevice52 libavdevice53 libmyth-0.24-0
The following packages will be upgraded:
  ffmpeg libavcodec52 libavcodec53 libavfilter1 libavfilter2 libavformat52
  libavformat53 libavutil50 libavutil51 libmythavcodec52 libmythavcore0
  libmythavformat52 libmythavutil50 libmythpostproc51 libmythswscale0
  libpostproc51 libswscale0 libswscale2 libx264-116 libxvidcore4
  live-installer-slideshow mint-translations mint-x-theme mythtv-common
  mythtv-database mythtv-doc python-mythtv
27 upgraded, 0 newly installed, 4 to remove and 3 not upgraded.

I'm not actually using Mythtv any more, otherwise I might be a little worried.

But you didn't tell us if you actually went ahead with it or not?
If you don't use mythtv any more then I would think that is perfectly OK to do so.

[Gerd50]

viking777 wrote:

Are you using apt-listbugs?

Yes i do. And you are right, sometimes it's better not to know, how buggy packages are. Mostly i don't care of it. Since i have
LMDE it never happened that sth was as buggy, that important things didn't work or there wasn't a fix. For now i'll stay with
apt-listbugs, because it gives me a reference point of what might be wrong if sth should really be broken.

[anticapitalista]

Don't want to appear overtly negative, but 48 pages of " LMDE BREAKAGES" isn't a good advert for LMDE IMO.

[GeneC]

Don't want to appear overtly negative, but 48 pages of " LMDE BREAKAGES" isn't a good advert for LMDE IMO.

You haven't read through the posts (cant blame you there).
Most of the posts are just for minor things and chit-chat.
I have been running LMDE since the 64 bit version came out last Dec.
There really have been very few problems that I can speak too.

And Yes, I do check your forum (ANTIX)
http://antix.freeforums.org/sid-upgraders-f5.html
Where you report breakages.
Thanks for that.

I am a Linux Newbie and have to say that i find LMDE easy to use and keep running.

[viking777]

Don't want to appear overtly negative, but 48 pages of " LMDE BREAKAGES" isn't a good advert for LMDE IMO.

Most of it has nothing to do with breakages - exactly like your post - and my reply

[kmb42vt]

Don't want to appear overtly negative, but 48 pages of " LMDE BREAKAGES" isn't a good advert for LMDE IMO.

That's why Clem and Co have completely redone LMDE's updating system and has a new LMDE respin currently being tested (soon to be released). These "48 pages of "LMDE BREAKAGES" is currently being used for those testers who have their main update repository still pointed toward 'Debian Testing' and not the new debian.linuxmint 'Incoming' or 'Latest' repos. What problems we find here in this thread we can report to the devs giving them a "heads up" as to what's coming their way in the form buggy updates coming directly from 'Debian Testing'. This (hopefully) helps them during the building of the next 'Incoming' Update Pack. That's one of the reasons anyway. Troubleshooting these problems and finding solutions is the other which also helps out the developers (besides the obvious reason of helping each other out).

In short, this is a testers thread and the LMDE build we're all testing here was a "proof of concept" release for the most part. Once the respin is released with the new update system already incorporated then at that point LMDE will be a bit more ready for prime time than it is now so to speak.

[DoNotUnderstand]

Went to run an update today got the following

Code: Select all

The following packages will be REMOVED:
  mythtv mythtv-backend mythtv-frontend mythtv-themes
The following packages have been kept back:
  libavdevice52 libavdevice53 libmyth-0.24-0
The following packages will be upgraded:
  ffmpeg libavcodec52 libavcodec53 libavfilter1 libavfilter2 libavformat52
  libavformat53 libavutil50 libavutil51 libmythavcodec52 libmythavcore0
  libmythavformat52 libmythavutil50 libmythpostproc51 libmythswscale0
  libpostproc51 libswscale0 libswscale2 libx264-116 libxvidcore4
  live-installer-slideshow mint-translations mint-x-theme mythtv-common
  mythtv-database mythtv-doc python-mythtv
27 upgraded, 0 newly installed, 4 to remove and 3 not upgraded.

I'm not actually using Mythtv any more, otherwise I might be a little worried.

But you didn't tell us if you actually went ahead with it or not?
If you don't use mythtv any more then I would think that is perfectly OK to do so.

Sorry, Yes I did the update - seems to work ok, except for no MythTv (which I don't use)

[secipolla]

BTW, if the Mint repos (latest/incoming) prove to work well (as they should) then Wheezy users and of its derivatives like antiX may want to point their sources.list to it.
Then better people donate to not overload the servers (or the community may have to ask the universities to mirror them too).

[zerozero]

even if i will make the breakage thread bigger, and bring more bad publicity to LMDE , Clem is already working in mirroring the new repos

The next step is already in progress and it consists in developing a network of mirrors for the new Debian repositories.

http://blog.linuxmint.com/?p=1799

[kmb42vt]

even if i will make the breakage thread bigger, and bring more bad publicity to LMDE , Clem is already working in mirroring the new repos

The next step is already in progress and it consists in developing a network of mirrors for the new Debian repositories.

http://blog.linuxmint.com/?p=1799

Yeah there ZZ, you and your bad publicity. Ought to be ashamed of yourself, making LMDE look bad like that.

[anticapitalista]

Hey I'm not doubting Clem's ability to 'tame' Testing (when/if needed).

I'm just pointing out that a new user to LMDE might get a bit 'worried' or get the wrong impression if they see a 48 page thread titled LMDE BREAKAGES.

Anyhow, good luck with the project.

[Techslave]

dnet-common victim here also .

Today's update brought this dnet-common along as a dependency of libdnet, which in turn was brought by libroar1. After the update my wireless network dropped. I tried to reinstall the wl module by following the how-to on the forum, but no success. I tried several reboots, wireless was still not working.

Then I looked closer at /var/log/aptitude and checked the bug reports for dnet-common. Sure enough there was one that's quite recent. This confirmed to me that indeed, dnet-common was the cause for my wireless network card not working.

After I uninstalled dnet-common, the wireless network started working again.

So, the moral of the story is: don't install dnet-common unless you know what you're doing (as stated in the above mentioned bug report).

I got hit with this same issue updating today, I tried to skip configuring since I had no idea what it was trying to do. It snagged and changed the MAC addresses for both my ethernet cards. Unfortunately, uninstalling dnet-common and dpkg -P haven't recovered it. Fortunately I have static IPs and it didn't mess with my wifi MAC. Gotta reboot into the new kernel anyhow, so hopefully a restart will fix it.

I wonder if this being included in the updates is caused by a naming assumption - this is from apt-cache show libdnet:

Code: Select all

 If you're looking for libdnet, the "dumb" networking library from
 libdnet.sf.net by Dug Song then you should install libdumbnet instead.
 Sorry for any confusion caused!


Anyhow, off to see if a reboot doesn't bring up more 'Monday Madness'.

[thatmexi]

*edit

disregard that, I was doing it wrong

everytime I do a major update I have to rerun the script detailed here:

http://community.linuxmint.com/tutorial/view/161

Thanks to Gramps!