Re: [opensuse] Smart failes to upgrade amarok
Reply on 03-01-2007 13:40:55 <<< Just because something is not comming from packman and/or guru does NOT Mean it is not an RPM for SUSE Linux.
That's absolutely not what I meant.
Ok, I maybe, but it was the way it was readable from your mail. I appologize for this then.
The point is that the mad library used to be packaged as "mad" on SUSE (until SUSE 9.2) and that it is a rather well-known fact that Packman provides that package already -- at least to somewhat more experienced SUSE users.
so: once wrong, always wrong? Probably the easiest to solve this conflict is to add a Provides: mad to the package at videolan.org
Experienced SUSE packagers (some people from the Packman project) already package vlc and its dependencies for SUSE Linux, so why not just reference that repository on the videolan website.
As I wrote in the previous post, the link WAS there, with the comment they looked for an 'own' packager. By investigating it came out that they tried to 'cooperate' with DQ, but apparently had some 'communication problems'. I can't tell you the whole story, as I don't know it... but if you want I'm sure I can figure it out for you.
So: start looking further than your nose. And help users in a constructive way. Not everybody wants to have their system killed / in an unsupported way by adding a repo that replaces system libs (like alsa for example). There are users that would like to stay on the 'supported' level.
Uh, well, it's your choice whether you upgrade alsa or not.
Well that's one thing. But IMO the right approach would have been to discuss it properly with the Packman team to see what the most appropriate solution would be. It would certainly make more sense to just copy the relevant Packman RPMs into a separate repository at videolan.org instead of building
packages from scratch again -- especially when they conflict with
Yes: for me it's not a problem. I can download the few RPMs I want from the website and install them. The avarage user adds the repos, sees: 'uh.. a bunch of updates... newer = better so let's install'.. and only later he runs in a problem and will NEVER be able to associate it to the fact of a PM package.. there were even already some threads on the ML regarding such packages. the the
most used community package repository.
The solution of packaging on their own is probably to better suit the needs / demands of the users in the IRC, ML and Forum. Now they can say: this feature is missing? We tell OUR packager to fix it. Before they could just say: Somebody packaged it and we can try to get in touch with him. what do you think do users favour? Cheers & Prosit Neujahr! Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 1/3/07, Dominique Leuenberger <Dominique.Leuenberger@tmf-group.com> wrote:
Reply on 03-01-2007 13:40:55 <<< Just because something is not comming from packman and/or guru does NOT Mean it is not an RPM for SUSE Linux.
That's absolutely not what I meant.
Ok, I maybe, but it was the way it was readable from your mail. I appologize for this then.
I started feeling that Smart and Packman are kind of painful topics and next time I'll be more careful asking such questions... :-( Just wanted to pay attention that the libraries are actually different (at least the files libmad.so.0.2.1 in two packages have different sizes). So it's good that Smart complained. YaST installed amarok and just replaced the previously installed library without warning. This seems quite problematic. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Goldstein wrote:
On 1/3/07, Dominique Leuenberger <Dominique.Leuenberger@tmf-group.com> wrote:
Reply on 03-01-2007 13:40:55 <<< Just because something is not comming from packman and/or guru does NOT mean it is not an RPM for SUSE Linux.
That's absolutely not what I meant.
Ok, I maybe, but it was the way it was readable from your mail. I apologize for this then.
I started feeling that Smart and Packman are kind of painful topics and next time I'll be more careful asking such questions... :-(
They're only painful to a few people.
Just wanted to pay attention that the libraries are actually different (at least the files libmad.so.0.2.1 in two packages have different sizes). So it's good that Smart complained. YaST installed amarok and
The different size is probably because they didn't strip the binaries. This happens automatically on SUSE >= 9.3 when you build a -debuginfo package (where debugging symbols are stripped out and stored into the - -debuginfo package, where the stripping out means a significant downsizing of the package).
just replaced the previously installed library without warning. This seems quite problematic.
That could be problematic, indeed. YaST2 must have detected the conflicting files too and just silently "upgraded" mad to libmad -- or was it the opposite ? For the amarok package, it would be pretty much the same as it doesn't explicitly require the "mad" package but instead requires "libmad.so.X" My amarok builds are an exception because they explicitly require the package "mad" -- although it is bad practice, I chose to do so in this case because it makes it easier to just install my amarok RPMs and everything that's needed for complete codec support is pulled from my repository and from Packman. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFm77Sr3NMWliFcXcRAptxAJ0SwmtqYUR0fB34PeN64LC/U7uabQCeJHmQ sMhEyUgCQk4NAn0eVMtP5Mo= =VCa3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 1/3/07, Pascal Bleser <pascal.bleser@skynet.be> wrote:
The different size is probably because they didn't strip the binaries. This happens automatically on SUSE >= 9.3 when you build a -debuginfo package (where debugging symbols are stripped out and stored into the - -debuginfo package, where the stripping out means a significant downsizing of the package).
I though about this option. Actually, it looks vise versa. Library from mad package is 200228 bytes long and the one from libmad was 92000+ (I removed it, so can't say for sure). If I'm using strip libmad.so.0.2.1 on mad version, I'm getting resulting file of 92276 bytes. But I doubt YaST is "smart" enough to check this kind of things.
That could be problematic, indeed. YaST2 must have detected the conflicting files too and just silently "upgraded" mad to libmad -- or was it the opposite ?
I had libmad before and YaST replaced it with mad version. Thanks & regards, -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Dominique Leuenberger -
Mark Goldstein -
Pascal Bleser