[packman] libxine1/libxine1-codecs problems with conflict dialogs

[Martin Schlander]

Torsdag 05 februar 2009 15:12:30 skrev Cristian Morales Vega:
> 2009/2/5 Martin Schlander <martin.schlander at gmail.com>:
> > #### YaST2 conflicts list - generated 2009-02-05 13:35:35 ####
> >
> > libxine1-codecs-1.1.16.1-0.pm.1.i686 requires libxine1 = 1.1.16.1, but
> > this requirement cannot be provided
> > uninstallable providers: libxine1-1.1.16.1-0.pm.1.i586[Packman
> > Repository] libxine1-1.1.16.1-0.pm.1.i686[Packman Repository] [ ]
> > Following actions will be done:
> > do not install libxine1-1.1.15-20.8.i586
> > architecture change of libxine1-1.1.15-20.8.i586 to
> > libxine1-1.1.16.1-0.pm.1.i686
> > install libxine1-1.1.16.1-0.pm.1.i686 (with vendor change)
> >   openSUSE
> > -->
> >   packman.links2linux.de
> > architecture change of libxine1-pulse-1.1.15-20.8.i586 to
> > libxine1-pulse-1.1.16.1-0.pm.1.i686
> > install libxine1-pulse-1.1.16.1-0.pm.1.i686 (with vendor change)
> >   openSUSE
> > -->
> >   packman.links2linux.de
> > architecture change of libxine1-gnome-vfs-1.1.15-20.8.i586 to
> > libxine1-gnome-vfs-1.1.16.1-0.pm.1.i686
> > install libxine1-gnome-vfs-1.1.16.1-0.pm.1.i686 (with vendor change)
> >   openSUSE
> > -->
> >   packman.links2linux.de
> >     [ ] do not install libxine1-codecs-1.1.16.1-0.pm.1.i686
> >
> >     [ ] Ignore some dependencies of libxine1-codecs
> >
> >
> >
> >
> > #### YaST2 conflicts list END ###
>
> Well, YaST would complain anyway if there is a vendor change,
> wouldn't? Removing the arch change reduces the message length, but not
> the message itself.

It wouldn't ask about the vendor change if the packages are explicitly 
specified in the ymp as far as I can tell. When I tested my 1-clicks around 
11.1 release time they'd install the desired stuff in a working manor without 
asking "scary" and "difficult" questions.

Yesterday I was informed that my 1-click had conflicts, hard to say how long 
this has been the case.

> Also note that 1-Click isn't so reliable anyway:
> http://lists.opensuse.org/opensuse-softwaremgmt/2008-12/msg00001.html

I've maintained KDE multimedia 1-clicks for as long as the 1-click system has 
existed - and generally it works fine. Irregularities only occur when packman 
packages either want to replace existing libraries or change arch or if 
videolan and packman repo are both used at the same time - or if other similar 
"funny stuff" going on. 

Of course sometimes the solver has bugs too or acts a little too bitchy, but 
that's no different when doing manual installation.

As long as it's a simple case of installing a new package or updating an 
existing package to a newer - without "funny stuff" going on - it works 
nicely. 

As you say in the mail, it acts like the user adding a repo with default 
priority, and then installing one or more packages with yast - letting the 
solver select the (newest) version - in other words - it does exactly what 
goes on in 98% of manual installations with yast or zypper.