How to fix: update errors about Medibuntu

[karlchen]

Hello, jcoles.

The lines that start with "ign" can be safely ignored. They do not indicate any problems at all.
And no, there is no new default file /etc/apt/sources.list available for Mint 14, because it is the same as before. Only the line referring to "packages.medibuntu.org" has been commented out or removed completely.

Kind regards,
Karl

[nomko]

As far as i have understood this issue, the medibuntu repo is no longer added in the standard Mint 16 source list.

[xenopeek]

I've updated the first post to reflect feedback. I haven't touched the sources of my Linux Mint 15 Cinnamon install (final, not RC) and Medibuntu isn't there. Perhaps I'm seeing ghosts

[iowabeakster]

I've updated the first post to reflect feedback. I haven't touched the sources of my Linux Mint 15 Cinnamon install (final, not RC) and Medibuntu isn't there. Perhaps I'm seeing ghosts

That's kind of strange. I am using Mint 15 Cinnamon and Medibuntu was definitely part of the official mint repository list on mine too. Is there a prompt asking to add this during the installation process? I forget...

And this quote (below) from Plaster02 seems to indicate that the path to the official mint repository list is somewhat different between mint 14 and 15. Thanks for the feedback Plaster02. On my mint 15, /etc/apt/sources.list is a totally blank file. So obviously there are some differences amongst the various late releases of mint here.

For you mint 14 users try this:

--I posted this on one of the other threads to help out with this. Copied and pasted here (with a couple edits)--

On Mint 15 this is how to fix the Medibuntu update errors
(and I assume 14 too... feedback to confirm would be useful)

Thanks for posting these instructions, they helped me to solve the problem when updating using apt.
I have installed Linux Mint 14 Nadia and I used the following commands, they are a bit different from the ones you posted.

In a terminal I entered:

Code: Select all

gksudo gedit /etc/apt/sources.list

Then I removed the mediabuntu line:

deb http://packages.medibuntu.org/ quantal free non-free

... and added the following line for the libdvdcss package (as thebookkeeper mentioned):

deb ftp://ftp.videolan.org/pub/debian stable/

Saved the file and updated. After the update I got the following error:

W: GPG error: ftp://ftp.videolan.org stable/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6BCA5E4DB84288D9

... so I added the missing GPG key running the following command in a terminal:

Code: Select all

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6BCA5E4DB84288D9

Updated again and everything looks fine now.

Thanks to all of you that posted this solution.

[cef1000]

Been getting this since about last Thursday, that I noticed:

Failed to fetch http://packages.medibuntu.org/dists/raring/Release.gpg Something wicked happened resolving 'packages.medibuntu.org:http' (-11 - System error)
Failed to fetch http://packages.medibuntu.org/dists/raring/free/i18n/Translation-en_US Something wicked happened resolving 'packages.medibuntu.org:http' (-11 - System error)
Failed to fetch http://packages.medibuntu.org/dists/raring/free/i18n/Translation-en Something wicked happened resolving 'packages.medibuntu.org:http' (-11 - System error)
Failed to fetch http://packages.medibuntu.org/dists/raring/non-free/i18n/Translation-en_US Something wicked happened resolving 'packages.medibuntu.org:http' (-11 - System error)
Failed to fetch http://packages.medibuntu.org/dists/raring/non-free/i18n/Translation-en Something wicked happened resolving 'packages.medibuntu.org:http' (-11 - System error)
Failed to fetch http://packages.medibuntu.org/dists/raring/free/binary-i386/Packages Something wicked happened resolving 'packages.medibuntu.org:http' (-11 - System error)
Failed to fetch http://packages.medibuntu.org/dists/raring/non-free/binary-i386/Packages Something wicked happened resolving 'packages.medibuntu.org:http' (-11 - System error)
Some index files failed to download. They have been ignored, or old ones used instead.

Is this repository depricated; or just having issues, needed? not needed? any ideas???

Thanks in advance,

cef1000

[RobertLM78]

Greeting Cef, and welcome to the Mint Forums!

Please do read the entire thread, and you will have your answer .

[nomko]

Is this repository depricated; or just having issues, needed? not needed? any ideas???

Thanks in advance,

cef1000

Yes, remove the medibuntu repo from the source list. Medibuntu is no longer under development and/or maintained.

[marcomint2]

The gksudo gedit didn't work for me; the depository file does not open. But with
sudo vi /etc/apt/sources.list
I cold block the medibuntu depository. After I did that everything is working OK again.
Thanks for the responses that have helped me to get to the right direction.

[RobertLM78]

The gksudo gedit didn't work for me; the depository file does not open. But with
sudo vi /etc/apt/sources.list
I cold block the medibuntu depository. After I did that everything is working OK again.
Thanks for the responses that have helped me to get to the right direction.

Interesting - I was able to disable the repo by un-checking the box in software sources, although I did open the sources.list file with pluma (I'm using MATE) afterward to make sure that Medibuntu was commented out. You do have gedit installed right? (I'm not sure what other DE's are using as their default text editor, but it may be you don't have gedit installed.)

[tinker123]

I'm noting it here now because the past few days there have been multiple posts from users asking for help with errors they are getting during updating. While it had been announced earlier that the project was abandoned, it wasn't until last week I believe that the repository actually got shut down.

I did look at the daily posts, but forgot to check the "stickies", I see you noted it a day ahead of me noticing when updating my Mint 14.

What's the current list of active depositories Mint 13 and upward still use? I think I have them all, but not sure.

FWIW, I pasted my error message into Google and did not find this thread. I ended up finding it after I made my own duplicate thread, getting a snarky reply and then a helpful person gave me a link to this thread.

Maybe some SEO via changing the title or tags of this thread so Google searchers can find it? Yah, I don't know what the situation is with that. Thanks for the info in this thread either way.

[tinker123]

Q: What was the Medibuntu repository used for? Are there alternatives?
A: Medibuntu was used for just two packages (on 64 bit; I'm not sure about 32 bit as I don't have that here):

• libdvdcss2 - For playback of video DVDs;
• w64codecs - Codecs for certain RealPlayer 10 formats (RV30/40, COOK, and RealAudio).

Both will remain installed on your system, and are also installed on newer versions of Linux Mint. There is no need to use another repository but if you want to, you can. The VideoLAN developers have a repository for the libdvdcss and are maintaining it there: http://www.videolan.org/developers/libdvdcss.html

If we don't use another repository for libdvdcss2 and w64codecs, what happens when those libraries get updated and get updated out of a need?

Am I right in assuming that these libraries do not change all that often?

[xenopeek]

I don't know VideoLAN are the developers of libdvdcss so their new Debian/Ubuntu repository will suit the needs of those that need updates to this package.

The latest release of w64codecs seems to be from 2007 and as shared here earlier by somebody you can get the file from the deb-multimedia website also (http://www.deb-multimedia.org/dists/unstable/non-free/binary-amd64/package/w64codecs). The codecs are for MPlayer only AFAIK and are only for some RealPlayer formats (from 2007, so hopefully obsoleted by now).

[GSimpson]

A could not get any of the suggestions here to work. No access to software sources, software manager etc.

So my solution that worked for me
Mint 14 64 bit Mate
Use file manager to /etc/apt and right click sources.list
Select Open with Pluma
Open as administrator
Comment out medibuntu line
ie change deb to # deb

Save and things should work now including going to Software sources and deleting the offending medibuntu

[sprintcowboy]

There seems to be two deferent repositories that you can add to the sources list.
deb ftp://ftp.videolan.org/pub/debian stable/
or
deb http://download.videolan.org/pub/debian/stable/ /
Which is better to use?

[xenopeek]

Doesn't really matter, though HTTP is a slightly more efficient protocol than FTP. Not sure if that is humanly measurable for one repository though FTP vs HTTP efficiency: http://daniel.haxx.se/docs/ftp-vs-http.html

[nomko]

Doesn't really matter, though HTTP is a slightly more efficient protocol than FTP. Not sure if that is humanly measurable for one repository though FTP vs HTTP efficiency: http://daniel.haxx.se/docs/ftp-vs-http.html

Looking at the pro's listed in that comparison list/test, it looks like HTTP is faster due to the use of pipelining. But then again, I think it's more a user's experience. If someone has the feeling that FTP goes a bit faster, that user will in most cases use FTP for file transferring. Same goes for HTTP ofcourse.

But aren't we straying from the topic title now?

[xenopeek]

Speed difference I believe is mostly from the "no command/response flow minimizes extra round-trips" bit; less round-trips for initiating a download. Anyway, back on topic

[xenopeek]

If we don't use another repository for libdvdcss2 and w64codecs, what happens when those libraries get updated and get updated out of a need?

From Linux Mint 16 the libdvdcss2 packages will be kept in the Linux Mint extra repository: http://blog.linuxmint.com/?p=2469

[wbaldwin]

This was helpful. Thank you.

[igor83]

One of the things I like about Linux is that fixing this was a no-brainer. I did not even read this forum thread or get any advice. The error message pointed me in the right direction. I waited a couple times to make sure medibuntu was really dead and not just down temporarily. After a couple weeks, I scrutinized the error message the update manager was spitting out. It was pretty obvious all I had to do was open a terminal, change to /etc/apt, edit sources.list and remove the reference to medibuntu. After that smooth sailing, as everyone else has noted.