Probably related to the borked rawhide, but I'll post what I'm seeing because "--skip-broken" usually allows the update to proceed... On an updated f10 laptop, switched repos to just rawhide, updated yum* successfully. Now, yum -y --skip-broken update: --> Finished Dependency Resolution dejavu-fonts-experimental-2.26-2.fc10.noarch from installed has depsolving probl ems --> Missing Dependency: dejavu-fonts = 2.26-2.fc10 is needed by package dejavu -fonts-experimental-2.26-2.fc10.noarch (installed) evolution-2.24.2-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement evolution-data-server >= 2.24.1 for evolution-2.2 4.2-1.fc10.i386 (installed) ekiga-3.0.1-4.fc10.i386 from installed has depsolving problems --> Unresolvable requirement evolution-data-server for ekiga-3.0.1-4.fc10.i386 (installed) evolution-webcal-2.23.91-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement evolution-data-server >= 1.1.0 for evolution-webc al-2.23.91-1.fc10.i386 (installed) evolution-2.24.2-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement libcamel-1.2.so.14 for evolution-2.24.2-1.fc10.i3 86 (installed) hal-cups-utils-0.6.17-4.fc10.i386 from installed has depsolving problems --> Unresolvable requirement cups for hal-cups-utils-0.6.17-4.fc10.i386 (insta lled) 7:kdegraphics-4.1.3-2.fc10.i386 from installed has depsolving problems --> Unresolvable requirement cups for 7:kdegraphics-4.1.3-2.fc10.i386 (install ed) libgnomecups-0.2.3-4.fc10.i386 from installed has depsolving problems --> Unresolvable requirement cups for libgnomecups-0.2.3-4.fc10.i386 (installe d) totem-pl-parser-2.24.2-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement libcamel-1.2.so.14 for totem-pl-parser-2.24.2-1.f c10.i386 (installed) redhat-lsb-3.2-2.fc10.i386 from installed has depsolving problems --> Unresolvable requirement /usr/bin/lpr for redhat-lsb-3.2-2.fc10.i386 (inst alled) gnome-panel-2.24.2-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement evolution-data-server >= 1.9.1 for gnome-panel-2. 24.2-1.fc10.i386 (installed) bluez-cups-4.19-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement cups for bluez-cups-4.19-1.fc10.i386 (installed) evolution-2.24.2-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement libcamel-provider-1.2.so.14 for evolution-2.24.2- 1.fc10.i386 (installed) redhat-lsb-3.2-2.fc10.i386 from installed has depsolving problems --> Unresolvable requirement /usr/bin/lp for redhat-lsb-3.2-2.fc10.i386 (insta lled)
... and the above loops continuously.
jerry
Jerry Amundson wrote:
Probably related to the borked rawhide, but I'll post what I'm seeing because "--skip-broken" usually allows the update to proceed... On an updated f10 laptop, switched repos to just rawhide, updated yum* successfully. Now, yum -y --skip-broken update: --> Finished Dependency Resolution dejavu-fonts-experimental-2.26-2.fc10.noarch from installed has depsolving probl ems --> Missing Dependency: dejavu-fonts = 2.26-2.fc10 is needed by package dejavu -fonts-experimental-2.26-2.fc10.noarch (installed) evolution-2.24.2-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement evolution-data-server >= 2.24.1 for evolution-2.2 4.2-1.fc10.i386 (installed) ekiga-3.0.1-4.fc10.i386 from installed has depsolving problems --> Unresolvable requirement evolution-data-server for ekiga-3.0.1-4.fc10.i386 (installed) evolution-webcal-2.23.91-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement evolution-data-server >= 1.1.0 for evolution-webc al-2.23.91-1.fc10.i386 (installed) evolution-2.24.2-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement libcamel-1.2.so.14 for evolution-2.24.2-1.fc10.i3 86 (installed) hal-cups-utils-0.6.17-4.fc10.i386 from installed has depsolving problems --> Unresolvable requirement cups for hal-cups-utils-0.6.17-4.fc10.i386 (insta lled) 7:kdegraphics-4.1.3-2.fc10.i386 from installed has depsolving problems --> Unresolvable requirement cups for 7:kdegraphics-4.1.3-2.fc10.i386 (install ed) libgnomecups-0.2.3-4.fc10.i386 from installed has depsolving problems --> Unresolvable requirement cups for libgnomecups-0.2.3-4.fc10.i386 (installe d) totem-pl-parser-2.24.2-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement libcamel-1.2.so.14 for totem-pl-parser-2.24.2-1.f c10.i386 (installed) redhat-lsb-3.2-2.fc10.i386 from installed has depsolving problems --> Unresolvable requirement /usr/bin/lpr for redhat-lsb-3.2-2.fc10.i386 (inst alled) gnome-panel-2.24.2-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement evolution-data-server >= 1.9.1 for gnome-panel-2. 24.2-1.fc10.i386 (installed) bluez-cups-4.19-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement cups for bluez-cups-4.19-1.fc10.i386 (installed) evolution-2.24.2-1.fc10.i386 from installed has depsolving problems --> Unresolvable requirement libcamel-provider-1.2.so.14 for evolution-2.24.2- 1.fc10.i386 (installed) redhat-lsb-3.2-2.fc10.i386 from installed has depsolving problems --> Unresolvable requirement /usr/bin/lp for redhat-lsb-3.2-2.fc10.i386 (insta lled)
... and the above loops continuously.
jerry
File a bug against yum see what Seth has to say..
Came across this in F9 cycle I think.,
You might need to "help" yum a bit..
yum -y update --skip-broken -x package
Start with the first then continue adding -x package until you hit the one(s) causing this..
Then mentioned the package(s) that causes this on your bug report.
JBG
On Mon, 1 Dec 2008, "Jóhann B. Guðmundsson" wrote:
File a bug against yum see what Seth has to say..
Came across this in F9 cycle I think.,
You might need to "help" yum a bit..
yum -y update --skip-broken -x package
Start with the first then continue adding -x package until you hit the one(s) causing this..
Then mentioned the package(s) that causes this on your bug report.
Actually, Tim does most of the skip-broken spelunking. Credit where it is due.
Also before filing a bug - get yum 3.2.20-4.fc9 from updates-testing and try it there. It might still fail but the debugging from that version should be better.
Thanks, -sv
Seth Vidal wrote:
On Mon, 1 Dec 2008, "Jóhann B. Guðmundsson" wrote:
File a bug against yum see what Seth has to say..
Came across this in F9 cycle I think.,
You might need to "help" yum a bit..
yum -y update --skip-broken -x package
Start with the first then continue adding -x package until you hit the one(s) causing this..
Then mentioned the package(s) that causes this on your bug report.
Actually, Tim does most of the skip-broken spelunking. Credit where it is due.
Also before filing a bug - get yum 3.2.20-4.fc9 from updates-testing and try it there. It might still fail but the debugging from that version should be better.
Thanks, -sv
Please install the 3.2.20-4.fc9 from updates-testing, if it fails then make a bugzilla report and attach the output from 'yum -d7 --skip-broken update'
Tim
Tim Lauridsen wrote:
Seth Vidal wrote:
On Mon, 1 Dec 2008, "Jóhann B. Guðmundsson" wrote:
File a bug against yum see what Seth has to say..
Came across this in F9 cycle I think.,
You might need to "help" yum a bit..
yum -y update --skip-broken -x package
Start with the first then continue adding -x package until you hit the one(s) causing this..
Then mentioned the package(s) that causes this on your bug report.
Actually, Tim does most of the skip-broken spelunking. Credit where it is due.
Also before filing a bug - get yum 3.2.20-4.fc9 from updates-testing and try it there. It might still fail but the debugging from that version should be better.
Thanks, -sv
Please install the 3.2.20-4.fc9 from updates-testing, if it fails then make a bugzilla report and attach the output from 'yum -d7 --skip-broken update'
Tim
Guys any reason why he cant use 3.2.20-4.fc10 build instead of 3.2.20-4.fc9 since he's on a F10 system? Any differences between these builds?
JBG
On Tue, Dec 2, 2008 at 1:47 AM, Tim Lauridsen tim.lauridsen@googlemail.com wrote:
Please install the 3.2.20-4.fc9 from updates-testing, if it fails then make a bugzilla report and attach the output from 'yum -d7 --skip-broken update'
https://bugzilla.redhat.com/show_bug.cgi?id=474189
jerry