codecs.... they arnt working

Trust me. If libdvdcss was updated it would be all over the forums, all over slashdot, all over the web. Its highly unlikely one will miss that and to keep a VLC repos with hundreds of other packages in the repos that can conflict with packman, for the reason one might catch an update to libdvdcss which occurs less than once/blue-moon reason makes absolutely no sense to me.

oldcpu wrote:

> Trust me. If libdvdcss was updated it would be all over the forums, all
> over slashdot, all over the web.

I don’t want to keep track of software updates for software, that’s why we
have repositories.

> and to keep a VLC repos with hundreds of other packages in the repos
> that can conflict with packman, for the reason one might catch an update
> to libdvdcss which occurs less than once/blue-moon reason makes
> absolutely no sense to me.

If it could cause conflicts it wouldn’t make sense to me also.
But if you setup your repo’s right it just won’t.
I get libdvdcss from the videolan repo and nothing else, ever…

I’m not saying you have to setup your repo’s my way, that’s your choiche.
But it’s simply not true that you’ll get conflicts just for having the
videolan and packman repo enabled.
Yast can take care of this, opensuse developers worked hard on getting the
packagemanagement as good as it is today, and i’m using the functionality it
provides.


Chris Maaskant

Akoellh wrote:

> Of course you are right, but in this case here, one might start with
> the most simple approach.

Yeah, i never knew updates for libdvdcss were so rare.
So it seems harmless to disable the vlc repo.

But setting up the repo’s right isn’t magic either.
Just click “switch system packages” in the right order.

> The OP does not even seem to be familiar with the most basic rules of
> using the package manager and repos, considering the first repo list
> posted with a wild mixture of 11.2, 11.0 and even Factory.

It was/is a mess agreed!
I’m wondering if this was the result of one-click installs, which makes
absolutely no sense to me at all.
I think we would see a lot less newbie problems without it.


Chris Maaskant

Well, the chances of you being right on that are certainly higher than 90% (estimated value on reading several fora).

ACK.

I would sign that statement (with blood if necessary).

The problem here is that the Packman and Videolan packagers can not agree on the location where codecs are to be located. Hence if you mistakenly (which is EASY for new users to do) install Videolan packaged codecs then packman packaged media players may not function, and visa vesa. **So yes it is true **.

And when it comes to repository proliferation, this is ONLY the tip of the iceburg.

But don’t believe me. Please do go ahead and install a zillion repositories because the “opensuse developers worked hard on getting the package management as good as it is today, and i’m using the functionality it provides.” and I wish you all the best.

Needless to say I think very little of that viewpoint.

But it’s simply not true that you’ll get conflicts just for having the
videolan and packman repo enabled.

I could agree with this - I assume you are using the switcher functionality.

But I also agree with @oldcpu and don’t recommend it!

I could use the VideoLan repo and manage it but I don’t. There is no benefit in doing so.
As and far as new users are concerned, it’s out of the question. IMO. If that’s worth anything.

oldcpu wrote:

>
> Chris Maaskant;2148094 Wrote:
>>
>> But it’s simply not true that you’ll get conflicts just for having
>> the videolan and packman repo enabled.
> The problem here is that the Packman and Videolan packagers can not
> agree on the location where codecs are to be located.

Wich doesn’t mean shit if you set up your repo’s right!

> Hence if you mistakenly (which is EASY for new users to do) install
> Videolan packaged codecs then packman packaged media players may not
> function, and visa vesa. *So yes it is true *.

Ah that’s logical, if a newbie can mess it up it will always be messed up.
That would explain why it’s working perfectly for me :s
>
> But don’t believe me.

Don’t worry, i don’t, my system proves it.

> Please do go ahead and install a zillion
> repositories because the “-opensuse developers worked hard on getting
> the package management as good as it is today, and i’m using the
> functionality it provides-.” and I wish you all the best.

Yeah the opensuse developers are realy dumb to work so long for a system not
to work, i’m just so stupid to use it and lucky to have it working with no
effort at all :s
>
> Needless to say I think very little of that viewpoint.
>
Maybe you shouldn’t be using anything at all.
Nothing works by your logic.


Chris Maaskant

caf4926 wrote:

>
>> But it’s simply not true that you’ll get conflicts just for having the
>> videolan and packman repo enabled.
> I could agree with this - I assume you are using the switcher
> functionality.

Yep i do.

> But I also agree with @oldcpu and don’t recommend it!

That’s fair.
I never said it should be one method or the other.
>
> I could use the VideoLan repo and manage it but I don’t. There is no
> benefit in doing so.
> As and far as new users are concerned, it’s out of the question. IMO.
> If that’s worth anything.
>
Yes it worth something, you are doing a good job helping a newbie out.
Just wanted to point out that with all the work that has being done with
zypper and yast it’s possible to control your repo’s perfectly without the
need to remove anything.


Chris Maaskant

@Chris Maaskant
I guess I’m a bit of a hypocrite. Because it’s do as I say not as I do. I have quite list of Factory repo’s.
A case of having to wear two hats:)

Take it easy.

Chris Maaskant this thread is not to help you.

Its to help a new user.

If you go add your viewpoints without proper consideration of the experience level of the users who are asking for help you will make it very difficult for them.

Your help is valued, but please not in a thread like this were such advice as you provided will cause more harm than good.

You can try to resolve that conflict by removing the vlc/libdvdcss repository, then going to the packman repository, click on “switch to this repository” at the top, then click on “Accept” at the bottom and then confirm any changes.

oldcpu wrote:

> If you go add your viewpoints without proper consideration of the
> experience level of the users who are asking for help you will make it
> very difficult for them.

Never ment to confuse the OP.
That’s why i never replied to his/her posts but to the experienced users
like yourself.
I was hoping you guys would consider my aproach next time a user asks for
help.

> Your help is valued, but please not in a thread like this were such
> advice as you provided will cause more harm than good.
>
If i did, then i’m sorry about that, it wasn’t my intension.


Chris Maaskant

| Alias | Name | Enabled | Refresh | Priority | Type | URI

–±----------------------±----------------------±--------±--------±---------±-------±---------------------------------------------------------------
1 | NVIDIA Repository | NVIDIA Repository | Yes | Yes | 99 | rpm-md | ftp://download.nvidia.com/opensuse/11.2/
2 | Packman Repository | Packman | Yes | Yes | 99 | rpm-md | http://packman.mirrors.skynet.be/pub/packman/suse/11.2
3 | openSUSE-11.2-Non-Oss | openSUSE-11.2-Non-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/11.2/repo/non-oss
4 | openSUSE-11.2-Oss | openSUSE-11.2-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/11.2/repo/oss
5 | repo-source | openSUSE-11.2-Source | Yes | Yes | 99 | yast2 | Index of /source/distribution/11.2/repo/oss
6 | repo-update | openSUSE-11.2-Update | Yes | Yes | 99 | rpm-md | Index of /update/11.2

Okay there is the new list… Hmmm seems iv started an interesting discussion. OpenSUSE has alot of people who know what there doing. Linux Mint is alot smaller…

OK, so did you do this:
http://tinyurl.com/yejwull

You need to be using kde to do that or have switched gnomes UI for yast to the QT version.

Another method is

zypper dup -r 2

But it might give conflicts that we need to work out

Problem: nothing provides glitz-devel needed by cairo-devel-1.8.8-30.pm.30.1.i586
Problem: nothing provides imlib2 needed by libcaca0-0.99.beta17-0.pm.1.1.i586
Problem: nothing provides liblapack.so.3 needed by python-numpy-1.3.0-0.pm.3.1.i586
Problem: nothing provides transmission-ui = 1.76 needed by transmission-common-1.76-0.pm.1.2.noarch
Problem: nothing provides libodbc.so.1 needed by wxWidgets-compat-2.8.10.1-2.pm.3.1.i586
Problem: nothing provides librdf.so.0 needed by libslv2-9-0.6.6-0.pm.1.1.i586
Problem: gstreamer-0_10-plugins-bad-lang-0.10.18-999.pm.1000.1.noarch requires gstreamer-0_10-plugins-bad = 0.10.18, but this requirement cannot be provided

Problem: nothing provides glitz-devel needed by cairo-devel-1.8.8-30.pm.30.1.i586
Solution 1: keep cairo-devel-1.8.8-2.1.i586
Solution 2: break cairo-devel by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c]

Thats what it gave me… so what do I do?

Oh and I did the same thing earlier and just said continue… Thats probably a bad thing… hmmm… There were alot of more problems

Those errors do not make sense to me, as those should be in OSS repository.

This makes me think the server was done when you tried.

Try again later.

Same exact problem… an hour later

Looking at your IP address, you are in a location where I would think you should not have a problem with a server.

But it appears either you have a problem with a server, or you have a problem with your openSUSE internet connection. Have you disabled ipv6 ?

What happens if you enter

ipv6.disable=1

in the GRUB boot/splash screen option line when you reboot, and then try?

If you look at the OSS repository contents for a 32-bit PC:
Index of /distribution/11.2/repo/oss/suse/i586 you will see those applications are there.

I recommend you disable repo#5 (source repos). You should not need that.

Okay I manually installed 3 of the packages it had problems with. They were in the OS repos
heres whats left
4 Problems:
Problem: nothing provides transmission-ui = 1.76 needed by transmission-common-1.76-0.pm.1.2.noarch
Problem: nothing provides libodbc.so.1 needed by wxWidgets-compat-2.8.10.1-2.pm.3.1.i586
Problem: nothing provides librdf.so.0 needed by libslv2-9-0.6.6-0.pm.1.1.i586
Problem: gstreamer-0_10-plugins-bad-lang-0.10.18-999.pm.1000.1.noarch requires gstreamer-0_10-plugins-bad = 0.10.18, but this requirement cannot be provided

Problem: nothing provides transmission-ui = 1.76 needed by transmission-common-1.76-0.pm.1.2.noarch
Solution 1: Following actions will be done:
keep transmission-common-1.74-4.7.1.noarch
keep transmission-gtk-1.74-4.7.1.i586
Solution 2: break transmission-common by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c):
I dont know what to do