Re: rawhide report: 20070919 changes

[Antonio Olivares]

----- Original Message ----
From: Build System 
To: [e-mail]; [e-mail]
Sent: Wednesday, September 19, 2007 5:59:53 AM
Subject: rawhide report: 20070919 changes

Broken deps for i386
----------------------------------------------------------
    Miro - 0.9.8.1-2.fc7.i386 requires firefox = 0:2.0.0.5
    Miro - 0.9.8.1-2.fc7.i386 requires libboost_python.so.2
    claws-mail-plugins - 3.0.0-1.fc8.i386 requires claws-mail-plugins-spamreport = 0:3.0.0-1.fc8
    csync2 - 1.33-5.fc7.i386 requires libsqlite.so.0
    digikam - 0.9.2-4.fc8.i386 requires libkexiv2.so.1
    digikam - 0.9.2-4.fc8.i386 requires libkdcraw.so.1
    gambas-gb-db - 1.0.19-1.fc8.2.i386 requires libsqlite.so.0
    kipi-plugins - 0.1.4-2.fc8.i386 requires libkexiv2.so.1
    kipi-plugins - 0.1.4-2.fc8.i386 requires libkdcraw.so.1

rawhide report: 20070919 changes

[David]

on 9/19/2007 8:15 AM, Antonio Olivares wrote:
> ----- Original Message ----
> From: Build System 
> To: [e-mail]; [e-mail]
> Sent: Wednesday, September 19, 2007 5:59:53 AM
> Subject: rawhide report: 20070919 changes
> Broken deps for i386
> Miro - 0.9.8.1-2.fc7.i386 requires firefox = 0:2.0.0.5
> Miro - 0.9.8.1-2.fc7.i386 requires libboost_python.so.2
> claws-mail-plugins - 3.0.0-1.fc8.i386 requires claws-mail-plugins-spamreport = 0:3.0.0-1.fc8
> csync2 - 1.33-5.fc7.i386 requires libsqlite.so.0
> digikam - 0.9.2-4.fc8.i386 requires libkexiv2.so.1
> digikam - 0.9.2-4.fc8.i386 requires libkdcraw.so.1
> gambas-gb-db - 1.0.19-1.fc8.2.i386 requires libsqlite.so.0
> kipi-plugins - 0.1.4-2.fc8.i386 requires libkexiv2.so.1
> kipi-plugins - 0.1.4-2.fc8.i386 requires libkdcraw.so.1

yum install skip-broken

yum --skip-broken update

rawhide report: 20070919 changes

[Antonio Olivares]

--- David Boles  wrote:
> on 9/19/2007 8:15 AM, Antonio Olivares wrote:
> > ----- Original Message ----
> > From: Build System 
> > To: [e-mail];
>
> [e-mail]
> > Sent: Wednesday, September 19, 2007 5:59:53 AM
> > Subject: rawhide report: 20070919 changes
> >
> > Broken deps for i386

----------------------------------------------------------
> > Miro - 0.9.8.1-2.fc7.i386 requires firefox =
>
> 0:2.0.0.5
> > Miro - 0.9.8.1-2.fc7.i386 requires
>
> libboost_python.so.2
> > claws-mail-plugins - 3.0.0-1.fc8.i386 requires
>
> claws-mail-plugins-spamreport = 0:3.0.0-1.fc8
> > csync2 - 1.33-5.fc7.i386 requires
>
> libsqlite.so.0
> > digikam - 0.9.2-4.fc8.i386 requires
>
> libkexiv2.so.1
> > digikam - 0.9.2-4.fc8.i386 requires
>
> libkdcraw.so.1
> > gambas-gb-db - 1.0.19-1.fc8.2.i386 requires
>
> libsqlite.so.0
> > kipi-plugins - 0.1.4-2.fc8.i386 requires
>
> libkexiv2.so.1
> > kipi-plugins - 0.1.4-2.fc8.i386 requires
>
> libkdcraw.so.1
>
> yum install skip-broken
>
> yum --skip-broken update
>
> --
>
> David
> > --
>
> fedora-test-list mailing list
> [e-mail]
> To unsubscribe:

Thanks David for trying to help. Been there done that:

[olivares@localhost ~]$ su -
Password: 
[root@localhost ~]# yum install skip-broken
Loading "refresh-updatesd" plugin
development                                           
         7.6 kB 00:00 
http://fedora.mirror.facebook.com/linux/development/i386/os/repodata/repomd....:
[Errno -1] Error importing repomd.xml for development:
Damaged repomd.xml file
Trying other mirror.
development               100%
|=========================| 2.1 kB    00:00     
texlive                   100%
|=========================|  951 B    00:00     
Setting up Install Process
Parsing package install arguments
Nothing to do
[root@localhost ~]# yum install skip-broken
Loading "refresh-updatesd" plugin
Setting up Install Process
Parsing package install arguments
Nothing to do
[root@localhost ~]# yum clean all
Loading "refresh-updatesd" plugin
Existing lock /var/run/yum.pid: another copy is
running as pid 13466.
Another app is currently holding the yum lock; waiting
for it to exit...
Cleaning up Everything
[root@localhost ~]# yum install skip-broken
Loading "refresh-updatesd" plugin
development               100%
|=========================| 2.1 kB    00:00     
primary.sqlite.bz2        100%
|=========================| 5.1 MB    00:02     
texlive                   100%
|=========================|  951 B    00:00     
primary.xml.gz            100%
|=========================| 7.6 kB    00:00     
texlive   :
##################################################
25/25
Setting up Install Process
Parsing package install arguments
Nothing to do

[root@localhost ~]# yum --skip-broken update
Loading "refresh-updatesd" plugin
Usage: yum [options] < grouplist, localinstall,
groupinfo, localupdate, resolvedep, erase, deplist,
groupremove, makecache, upgrade, provides, shell,
install, whatprovides, groupinstall, update, repolist,
groupupdate, info, search, check-update, list, remove,
clean, grouperase >

Command line error: no such option: --skip-broken
[root@localhost ~]#

Regards,

Antonio

____________________________________________________________________________________
Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos.
http://autos.yahoo.com/index.html

rawhide report: 20070919 changes

[Chuck Ebbert]

On 09/19/2007 05:52 PM, Antonio Olivares wrote:
> Thanks David for trying to help. Been there done that:
>
> [olivares@localhost ~]$ su -
> Password: 
> [root@localhost ~]# yum install skip-broken

that's

# yum install yum-skip-broken

rawhide report: 20070919 changes

[Antonio Olivares]

--- Chuck Ebbert  wrote:
> On 09/19/2007 05:52 PM, Antonio Olivares wrote:
> > Thanks David for trying to help. Been there done
>
> that:
> > [olivares@localhost ~]$ su -
> > Password: 
> > [root@localhost ~]# yum install skip-broken
>
> that's
>
> # yum install yum-skip-broken
>
> --

Thank you very much, Chuck.  I always wondered why it
did not work as I have tried to install this plugin
several times.

Regards,

Antonio

____________________________________________________________________________________
Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos.
http://autos.yahoo.com/index.html

rawhide report: 20070919 changes

[Mike Chambers]

On Wed, 2007-09-19 at 15:39 -0700, Antonio Olivares wrote:
> Thank you very much, Chuck.  I always wondered why it
> did not work as I have tried to install this plugin
> several times.

If in doubt, can also use wild cards too.

Yum install *skip-broken* or *skip*broken* to help get you what you
want.

rawhide report: 20070919 changes

[Antonio Olivares]

--- Chuck Ebbert  wrote:
> On 09/19/2007 05:52 PM, Antonio Olivares wrote:
> > Thanks David for trying to help. Been there done
>
> that:
> > [olivares@localhost ~]$ su -
> > Password: 
> > [root@localhost ~]# yum install skip-broken
>
> that's
>
> # yum install yum-skip-broken
>
> --

Even with the skip-broken option after it was
installed:

Updating fails:

Running rpm_check_debug
ERROR with rpm_check_debug vs depsolve:
Package devhelp needs libgtkembedmoz.so, this is not
available.
Package yelp needs libgtkembedmoz.so, this is not
available.
Package yelp needs libxpcom_core.so, this is not
available.
Package devhelp needs gecko-libs = 1.8.1.6, this is
not available.
Package yelp needs gecko-libs = 1.8.1.6, this is not
available.
Package digikam needs libkexiv2.so.1, this is not
available.
Package digikam needs libkdcraw.so.1, this is not
available.
Complete!

[root@localhost ~]# rpm -qa yum-skip-broken
yum-skip-broken-1.1.7-1.fc8
[root@localhost ~]#

Regards,

Antonio

____________________________________________________________________________________
Pinpoint customers who are looking for what you sell. 
http://searchmarketing.yahoo.com/

rawhide report: 20070919 changes

[David]

on 9/19/2007 6:24 PM, Chuck Ebbert wrote:
> On 09/19/2007 05:52 PM, Antonio Olivares wrote:
> > Thanks David for trying to help. Been there done that:
> >
> > [olivares@localhost ~]$ su -
> > Password: 
> > [root@localhost ~]# yum install skip-broken
>
> that's
>
> # yum install yum-skip-broken

Chuck is correct here. My mistake completely.

This is what I get for replying as I am going out the door for a meeting.

I am sorry about this.

Good luck with your testing.

rawhide report: 20070919 changes

[Antonio Olivares]

--- David Boles  wrote:
> on 9/19/2007 6:24 PM, Chuck Ebbert wrote:
> > On 09/19/2007 05:52 PM, Antonio Olivares wrote:
> > > Thanks David for trying to help. Been there done
>
> that:
> > > [olivares@localhost ~]$ su -
> > > Password: 
> > > [root@localhost ~]# yum install skip-broken
> >
> > that's
> >
> > # yum install yum-skip-broken
>
> Chuck is correct here. My mistake completely.
>
> This is what I get for replying as I am going out
> the door for a meeting.
>
> I am sorry about this.
> Good luck with your testing.
>
> David
> > --

Do not worry David.  It happens to us all.  It was an
honest mistake.  Still even with the skip-broken
plugin, updating fails.

Regards,

Antonio

____________________________________________________________________________________
Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545469

rawhide report: 20070919 changes

[Jim Cornette]

Antonio Olivares wrote:
> Do not worry David.  It happens to us all.  It was an
> honest mistake.  Still even with the skip-broken
> plugin, updating fails.
>
> Regards,
>
> Antonio

Yum update --skip-broken
aborted for me also. I had to remove digikam and  kipi-plugins because 
of the libkdcraw.so.1 and libkexiv2.so.1 requirements.

I save the cache for yum so rpm -Fvh *.rpm installed all of the packages 
that were downloaded using --skip-broken.

Just one possible option,

Jim

rawhide report: 20070919 changes

[David]

on 9/19/2007 8:34 PM, Jim Cornette wrote:
> Antonio Olivares wrote:
> > Do not worry David.  It happens to us all.  It was an
> > honest mistake.  Still even with the skip-broken
> > plugin, updating fails.
> >
> > Regards,
> >
> > Antonio
>
> Yum update --skip-broken
> aborted for me also. I had to remove digikam and  kipi-plugins because 
> of the libkdcraw.so.1 and libkexiv2.so.1 requirements.
>
> I save the cache for yum so rpm -Fvh *.rpm installed all of the packages 
> that were downloaded using --skip-broken.
>
> Just one possible option,

Not sure, exactly, what you are saying here. Remove is not normally
necessary. Just exclude the packages that are causing the problems with
some of the packages in the update.

rawhide report: 20070919 changes

[Jim Cornette]

David Boles wrote:
> Not sure, exactly, what you are saying here. Remove is not normally
> necessary. Just exclude the packages that are causing the problems with
> some of the packages in the update.

Since the plugin did not exclude packages that were "broken", I am not 
sure why an additional step of using exclude in tandem would be needed.

skip broken downloaded the rpms but bailed before installation of the 
rpms. Yum is now out of the equation and rpm directly is the solution. 
rpm complains about digikam and the kde related plugin. I read their 
descriptions and though digikam sounded interesting, I never used it to 
date, The plugin was never used as far as I recall. At least I never 
intervened in the process.

As a note, skip-broken did exclude xurlrunner from the downloaded cache.

I believe that I am catching on to what skip-broken does. It excludes 
pulling in new packages with dependency problems. It does not exclude 
package conflicts due to packages already installed.

So what would the right command to get the packages installed without 
conflict be? Would it be something like below? Or would simply 
determining your need for the conflicting package and removing it be a 
better alternative?

yum -y --skip-broken --exclude=digikam

Jim

rawhide report: 20070919 changes

[David]

on 9/19/2007 10:41 PM, Jim Cornette wrote:
> David Boles wrote:
> > Not sure, exactly, what you are saying here. Remove is not normally
> > necessary. Just exclude the packages that are causing the problems with
> > some of the packages in the update.
>
> Since the plugin did not exclude packages that were "broken", I am not 
> sure why an additional step of using exclude in tandem would be needed.
>
> skip broken downloaded the rpms but bailed before installation of the 
> rpms. Yum is now out of the equation and rpm directly is the solution. 
> rpm complains about digikam and the kde related plugin. I read their 
> descriptions and though digikam sounded interesting, I never used it to 
> date, The plugin was never used as far as I recall. At least I never 
> intervened in the process.
>
> As a note, skip-broken did exclude xurlrunner from the downloaded cache.
>
> I believe that I am catching on to what skip-broken does. It excludes 
> pulling in new packages with dependency problems. It does not exclude 
> package conflicts due to packages already installed.
>
> So what would the right command to get the packages installed without 
> conflict be? Would it be something like below? Or would simply 
> determining your need for the conflicting package and removing it be a 
> better alternative?
>
> yum -y --skip-broken --exclude=digikam

I am *not* an expert here. Only an old time user. The plugins are
'painless'. I have never had one of them cause problems. Fail? Sometimes
maybe. But not break anything. As well as yum.

Rpm is what can do, if you really do 'bad things' with it without knowing
exactly what you are doing, will break things.

Your example, from above, 'might' work. Or it 'might not' work. It might
take some tweaks. But it would not break anything. 'Excluding' means don't
do anything with this. 'Force' and 'nodeps' are the really bad commands
for the uneducated users.

Computers are different. Installed packages are different. Many things are
different. That is why 'it works for me' and it might not 'work for you'
happens.

Another thing to consider. Sometimes mirrors are not updated just when you
connect. Try later works more times than people like to admit.  :-)

rawhide report: 20070919 changes

[Jim Cornette]

David Boles wrote:
> I am *not* an expert here. Only an old time user. The plugins are
> 'painless'. I have never had one of them cause problems. Fail? Sometimes
> maybe. But not break anything. As well as yum.

Trying to install it now with yum fails with the below.

yum install kipi-plugins
Loading "skip-broken" plugin
Loading "refresh-updatesd" plugin
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package kipi-plugins.i386 0:0.1.4-2.fc8 set to be updated
--> Processing Dependency: libkexiv2.so.1 for package: kipi-plugins
--> Processing Dependency: libkdcraw.so.1 for package: kipi-plugins
--> Finished Dependency Resolution
Error: Missing Dependency: libkexiv2.so.1 is needed by package kipi-plugins
Error: Missing Dependency: libkdcraw.so.1 is needed by package kipi-plugins
[root@HP-JCF7 ~]# locate libkexiv2.so
/usr/lib/libkexiv2.so.1
/usr/lib/libkexiv2.so.1.1.1
[root@HP-JCF7 ~]# rpm -q --whatprovides /usr/lib/libkexiv2.so.1
error: file /usr/lib/libkexiv2.so.1: No such file or directory
[root@HP-JCF7 ~]# rpm -q --whatprovides /usr/lib/libkexiv2.so.1.1.1
error: file /usr/lib/libkexiv2.so.1.1.1: No such file or directory
[root@HP-JCF7 ~]# updatedb
[root@HP-JCF7 ~]# locate libkexiv2.so
/usr/lib/libkexiv2.so.3
/usr/lib/libkexiv2.so.3.0.0
[root@HP-JCF7 ~]# rpm -q --whatprovides /usr/lib/libkexiv2.so.3
libkexiv2-0.1.6-1.fc8
> Rpm is what can do, if you really do 'bad things' with it without knowing
> exactly what you are doing, will break things.

The previous removal was just using rpm -e. Both digikam and 
kipi-plugins were successfully removed. I could have used yum -y update 
--skip-broken successfully after removing the packages, but it seemed 
like overkill to use yum, since it already pulled in the packages to cache.
> Your example, from above, 'might' work. Or it 'might not' work. It might
> take some tweaks. But it would not break anything. 'Excluding' means don't
> do anything with this. 'Force' and 'nodeps' are the really bad commands
> for the uneducated users.

I believe running yum with those parameters would have failed anyway 
with the prior example. Yum could not do anything about the updated 
libkexiv2 package which caused problems with the two rpms.

Related to rpm and its powers. I know to try to stay in its conventional 
options for the most part. Tomboy did get booted with extreme options 
though. Mono then removed properly with yum remove.
> Computers are different. Installed packages are different. Many things are
> different. That is why 'it works for me' and it might not 'work for you'
> happens.

I believe most errors now are legitimate since Robert is seeing the same 
errors. yum exclude for the libkexiv2 package and skip-broken for the 
xurl* problem would probably work.
> Another thing to consider. Sometimes mirrors are not updated just when you
> connect. Try later works more times than people like to admit.  :-)

The requested updates matched this rawhide report now and at the time 
the problem was originally discussed. Mirror sync problems are something 
to take into consideration though with update retrieval.

Jim
>

rawhide report: 20070919 changes

[David]

on 9/20/2007 6:53 AM, Jim Cornette wrote:
> David Boles wrote:
> > I am *not* an expert here. Only an old time user. The plugins are
> > 'painless'. I have never had one of them cause problems. Fail? Sometimes
> > maybe. But not break anything. As well as yum.
>
> Trying to install it now with yum fails with the below.
>
> yum install kipi-plugins
> Loading "skip-broken" plugin
> Loading "refresh-updatesd" plugin
> Setting up Install Process
> Parsing package install arguments
> Resolving Dependencies
> --> Running transaction check
> ---> Package kipi-plugins.i386 0:0.1.4-2.fc8 set to be updated
> --> Processing Dependency: libkexiv2.so.1 for package: kipi-plugins
> --> Processing Dependency: libkdcraw.so.1 for package: kipi-plugins
> --> Finished Dependency Resolution
> Error: Missing Dependency: libkexiv2.so.1 is needed by package kipi-plugins
> Error: Missing Dependency: libkdcraw.so.1 is needed by package kipi-plugins
> [root@HP-JCF7 ~]# locate libkexiv2.so
> /usr/lib/libkexiv2.so.1
> /usr/lib/libkexiv2.so.1.1.1
> [root@HP-JCF7 ~]# rpm -q --whatprovides /usr/lib/libkexiv2.so.1
> error: file /usr/lib/libkexiv2.so.1: No such file or directory
> [root@HP-JCF7 ~]# rpm -q --whatprovides /usr/lib/libkexiv2.so.1.1.1
> error: file /usr/lib/libkexiv2.so.1.1.1: No such file or directory
> [root@HP-JCF7 ~]# updatedb
> [root@HP-JCF7 ~]# locate libkexiv2.so
> /usr/lib/libkexiv2.so.3
> /usr/lib/libkexiv2.so.3.0.0
> [root@HP-JCF7 ~]# rpm -q --whatprovides /usr/lib/libkexiv2.so.3
> libkexiv2-0.1.6-1.fc8
> > Rpm is what can do, if you really do 'bad things' with it without knowing
> > exactly what you are doing, will break things.
>
> The previous removal was just using rpm -e. Both digikam and 
> kipi-plugins were successfully removed. I could have used yum -y update 
> --skip-broken successfully after removing the packages, but it seemed 
> like overkill to use yum, since it already pulled in the packages to cache.
> > Your example, from above, 'might' work. Or it 'might not' work. It might
> > take some tweaks. But it would not break anything. 'Excluding' means don't
> > do anything with this. 'Force' and 'nodeps' are the really bad commands
> > for the uneducated users.
>
> I believe running yum with those parameters would have failed anyway 
> with the prior example. Yum could not do anything about the updated 
> libkexiv2 package which caused problems with the two rpms.
>
> Related to rpm and its powers. I know to try to stay in its conventional 
> options for the most part. Tomboy did get booted with extreme options 
> though. Mono then removed properly with yum remove.
> > Computers are different. Installed packages are different. Many things are
> > different. That is why 'it works for me' and it might not 'work for you'
> > happens.
>
> I believe most errors now are legitimate since Robert is seeing the same 
> errors. yum exclude for the libkexiv2 package and skip-broken for the 
> xurl* problem would probably work.
> > Another thing to consider. Sometimes mirrors are not updated just when you
> > connect. Try later works more times than people like to admit.  :-)
>
> The requested updates matched this rawhide report now and at the time 
> the problem was originally discussed. Mirror sync problems are something 
> to take into consideration though with update retrieval.

The skip-broken plugin defaults to 'off'. To use it you must 'switch' it
on. Like this:

yum --skip-broken update            <<  note the --skip-broken part.

Another nice plugin is yum-merge-config.

rawhide report: 20070919 changes

[Horst H. von Brand]

Jim Cornette  wrote:
> David Boles wrote:
> > Not sure, exactly, what you are saying here. Remove is not normally
> > necessary. Just exclude the packages that are causing the problems with
> > some of the packages in the update.

[...]
> So what would the right command to get the packages installed without
> conflict be? Would it be something like below? Or would simply
> determining your need for the conflicting package and removing it be a
> better alternative?
>
> yum -y --skip-broken --exclude=digikam

I'd vote for axing yum-skip-broken. It has *never* worked.

rawhide report: 20070919 changes

[David]

on 9/20/2007 2:46 AM, Horst H. von Brand wrote:
> Jim Cornette  wrote:
> > David Boles wrote:
> > > Not sure, exactly, what you are saying here. Remove is not normally
> > > necessary. Just exclude the packages that are causing the problems with
> > > some of the packages in the update.
>
> [...]
> > So what would the right command to get the packages installed without
> > conflict be? Would it be something like below? Or would simply
> > determining your need for the conflicting package and removing it be a
> > better alternative?
> >
> > yum -y --skip-broken --exclude=digikam
>
> I'd vote for axing yum-skip-broken. It has *never* worked.

In a different post I noted that you have to turn on the plugin for it to
work since it defaults to off.

yum --skip-broken update     for example

rawhide report: 20070919 changes

[Horst H. von Brand]

David Boles  wrote:
> on 9/20/2007 2:46 AM, Horst H. von Brand wrote:
> > Jim Cornette  wrote:
> > > David Boles wrote:
> > > > Not sure, exactly, what you are saying here. Remove is not normally
> > > > necessary. Just exclude the packages that are causing the problems with
> > > > some of the packages in the update.
> >
> > [...]
> > > So what would the right command to get the packages installed without
> > > conflict be? Would it be something like below? Or would simply
> > > determining your need for the conflicting package and removing it be a
> > > better alternative?
> > >
> > > yum -y --skip-broken --exclude=digikam
> >
> > I'd vote for axing yum-skip-broken. It has *never* worked.
> In a different post I noted that you have to turn on the plugin for it to
> work since it defaults to off.
>
> yum --skip-broken update     for example

Or "yum update --skip-broken". Both bomb out here when there is some
conflict, updating nothing whatsoever.

rawhide report: 20070919 changes

[Tim Lauridsen]

Horst H. von Brand wrote:
> Jim Cornette  wrote:
> > David Boles wrote:
> > > Not sure, exactly, what you are saying here. Remove is not normally
> > > necessary. Just exclude the packages that are causing the problems with
> > > some of the packages in the update.
>
> [...]
> > So what would the right command to get the packages installed without
> > conflict be? Would it be something like below? Or would simply
> > determining your need for the conflicting package and removing it be a
> > better alternative?
> >
> > yum -y --skip-broken --exclude=digikamhttp://
>
> I'd vote for axing yum-skip-broken. It has *never* worked.

The current 1.1.7 should work, but it cant solve all issues (The have 
some issues because the yum depsolver has been a moving target)
Here is a little explanation of how it works.
for each package in the yum transaction
    make a new yum transaction with only this package
    run the yum depsolver on the transaction
    if it fails then put it on the bad list
remove the packages on the bad list from the original transaction and 
run the normal yum depsolve.

so it will only find the problems found in the depsolve process, not the 
ones in the test transaction.
There have been some problems lately, because there have been some issue 
with clearing the depsolve between check of each package, but as far as 
i know it should the current 1.1.7 release be working with yum 3.2.5.

Tim

rawhide report: 20070919 changes

[Rahul Sundaram]

Tim Lauridsen wrote:
> >
>
> The current 1.1.7 should work, but it cant solve all issues (The have 
> some issues because the yum depsolver has been a moving target)

IMO, you should try and convince Seth Vidal to integrate this plugin to 
yum core itself if there is reasonable hope that it will work for most 
instances now. I think he said he was open to that in yum-devel list before.

Rahul

rawhide report: 20070919 changes

[Tim Lauridsen]

Rahul Sundaram wrote:
> Tim Lauridsen wrote:
> > >
> >
> > The current 1.1.7 should work, but it cant solve all issues (The have 
> > some issues because the yum depsolver has been a moving target)
>
> IMO, you should try and convince Seth Vidal to integrate this plugin 
> to yum core itself if there is reasonable hope that it will work for 
> most instances now. I think he said he was open to that in yum-devel 
> list before.
>
> Rahul

It is on my list, i was just waiting for the depsolver changes to calm 
down a little, We have discussed the issue on yum-devel and it on the 
yum todo list [1].

Tim

[1] : http://wiki.linux.duke.edu/YumTodo

rawhide report: 20070919 changes

[David]

on 9/19/2007 7:32 PM, Antonio Olivares wrote:
> --- David Boles  wrote:
> > on 9/19/2007 6:24 PM, Chuck Ebbert wrote:
> > > On 09/19/2007 05:52 PM, Antonio Olivares wrote:
> > > > Thanks David for trying to help. Been there done
> >
> > that:
> > > > [olivares@localhost ~]$ su -
> > > > Password: 
> > > > [root@localhost ~]# yum install skip-broken
> > >
> > > that's
> > >
> > > # yum install yum-skip-broken
> >
> > Chuck is correct here. My mistake completely.
> >
> > This is what I get for replying as I am going out
> > the door for a meeting.
> >
> > I am sorry about this.
> > Good luck with your testing.
> >
> > David
> > > --
>
> Do not worry David.  It happens to us all.  It was an
> honest mistake.  Still even with the skip-broken
> plugin, updating fails.

First. Do you have any 'other than Fedora' packages installed? That can,
and usually does, cause problems.

For me it worked this time. It, the plugin, works most of the time.

I have a script that works when this plugin does not work. It is not too
large but I would not post it for you here because some users have
download size limits.

If you would like to try it, it has never caused me any problems, I would
email it to you privately. It is slow when you compare it to a normal
update but it will skip any packages that have problems.

rawhide report: 20070919 changes

[Antonio Olivares]

--- David Boles  wrote:
> on 9/19/2007 7:32 PM, Antonio Olivares wrote:
> > --- David Boles  wrote:
> > > on 9/19/2007 6:24 PM, Chuck Ebbert wrote:
> > > > On 09/19/2007 05:52 PM, Antonio Olivares wrote:
> > > > > Thanks David for trying to help. Been there
>
> done
> > > that:
> > > > > [olivares@localhost ~]$ su -
> > > > > Password: 
> > > > > [root@localhost ~]# yum install skip-broken
> > > >
> > > > that's
> > > >
> > > > # yum install yum-skip-broken
> > >
> > > Chuck is correct here. My mistake completely.
> > >
> > > This is what I get for replying as I am going out
> > > the door for a meeting.
> > >
> > > I am sorry about this.
> > > Good luck with your testing.
> > >
> > > David
> > > > --
> >
> > Do not worry David.  It happens to us all.  It was
>
> an
> > honest mistake.  Still even with the skip-broken
> > plugin, updating fails.
>
> First. Do you have any 'other than Fedora' packages
> installed? That can,
> and usually does, cause problems.
>
> For me it worked this time. It, the plugin, works
> most of the time.
>
> I have a script that works when this plugin does not
> work. It is not too
> large but I would not post it for you here because
> some users have
> download size limits.
>
> If you would like to try it, it has never caused me
> any problems, I would
> email it to you privately. It is slow when you
> compare it to a normal
> update but it will skip any packages that have
> problems.
> --
>
> David
> > --

Thanks, I would appreciate if you sent your script. 
using the skip-broken plugin plus the --exclude option
is not working:

Transaction Summary
=============================================================================
Install      4 Package(s)         
Update      97 Package(s)         
Remove       2 Package(s)

Total download size: 171 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
ERROR with rpm_check_debug vs depsolve:
Package devhelp needs libgtkembedmoz.so, this is not
available.
Package yelp needs libgtkembedmoz.so, this is not
available.
Package yelp needs libxpcom_core.so, this is not
available.
Package devhelp needs gecko-libs = 1.8.1.6, this is
not available.
Package yelp needs gecko-libs = 1.8.1.6, this is not
available.
Package digikam needs libkexiv2.so.1, this is not
available.
Package digikam needs libkdcraw.so.1, this is not
available.
Complete!
[root@localhost ~]# yum --skip-broken update
--exclude=digikam --exclude=kipi* -[root@localhost ~]#
yum --skip-broken update --exclude=digikam
--exclude=kipi* [olivares@localhost ~]$

I do not want to eliminate digikam, or yelp.  Maybe
Robert is also interested in your script.

Regards,

Antonio

____________________________________________________________________________________
Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/

rawhide report: 20070919 changes

[Jeff Needle]

> Cannot update.  Cannot get by the following dependency.
>
> Error: Unresolvable requirement gecko-libs = 1.8.1.6 for yelp
> Error: Missing Dependency: libkexiv2.so.1 is needed by package digikam
> Error: Unresolvable requirement libgtkembedmoz.so for yelp
> Error: Unresolvable requirement gecko-libs = 1.8.1.6 for devhelp
> Error: Unresolvable requirement libgtkembedmoz.so for devhelp
> Error: Unresolvable requirement libxpcom_core.so for yelp
> Error: Missing Dependency: libkdcraw.so.1 is needed by package digikam

Looks like you need to exclude xulrunner until it gets back in synch with 
firefox.

j.