FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User
Reload this Page Problems with update -- redhat-lsb conflicts

 
Page 3 of 3 < 12 3
 
LinkBack Thread Tools
 
Old 06-25-2012, 08:32 PM
Joe Zeff
 
Default Problems with update -- redhat-lsb conflicts
On 06/25/2012 01:12 PM, Reindl Harald wrote:

--skip-broken tends generally to fail on multilib in a way that
it pulls i686 deps if they seem to satisfy deps by version
on a pure x86_64 system as long you do not "exclude=*.i686"


I'm not sure that that's --skip-broken's fault; it sounds more like a
problem with how the deps are defined, or possibly how they're evaluated.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 06-25-2012, 08:35 PM
Michael Schwendt
 
Default Problems with update -- redhat-lsb conflicts
On Mon, 25 Jun 2012 22:12:50 +0200, Reindl Harald wrote:

> --skip-broken tends generally to fail on multilib in a way that
> it pulls i686 deps if they seem to satisfy deps by version
> on a pure x86_64 system as long you do not "exclude=*.i686"

That's something different and the reason why packagers make more
dependencies arch-specific. (For the depsolver, the older i686 packages
are sufficient when resolving dependencies.)

For the redhat-lsb breakage, Yum could notice that redhat-lsb.x86_64
cannot be updated (because of the "protected multilib versions" error) and
exclude it, then proceed and manage to apply other updates.

It might be that it doesn't handle "protected multilib versions" errors
it its --skip-broken mode.

--
Fedora release 17 (Beefy Miracle) - Linux 3.4.3-1.fc17.x86_64
loadavg: 0.21 0.21 0.41
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 06-25-2012, 08:57 PM
Reindl Harald
 
Default Problems with update -- redhat-lsb conflicts
Am 25.06.2012 22:32, schrieb Joe Zeff:
> On 06/25/2012 01:12 PM, Reindl Harald wrote:
>> --skip-broken tends generally to fail on multilib in a way that
>> it pulls i686 deps if they seem to satisfy deps by version
>> on a pure x86_64 system as long you do not "exclude=*.i686"
>
> I'm not sure that that's --skip-broken's fault; it sounds more like a problem with how the deps are defined, or
> possibly how they're evaluated

irrelevant, the question was

>>> Do you mean that --skip-broken fails for *any*
>>> "protected multilib versions" error in general?

and yes it does all the time

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 06-25-2012, 09:09 PM
Michael Schwendt
 
Default Problems with update -- redhat-lsb conflicts
On Mon, 25 Jun 2012 22:57:41 +0200, Reindl Harald wrote:

>
>
> Am 25.06.2012 22:32, schrieb Joe Zeff:
> > On 06/25/2012 01:12 PM, Reindl Harald wrote:
> >> --skip-broken tends generally to fail on multilib in a way that
> >> it pulls i686 deps if they seem to satisfy deps by version
> >> on a pure x86_64 system as long you do not "exclude=*.i686"
> >
> > I'm not sure that that's --skip-broken's fault; it sounds more like a problem with how the deps are defined, or
> > possibly how they're evaluated
>
> irrelevant, the question was

Not really.

> >>> Do you mean that --skip-broken fails for *any*
> >>> "protected multilib versions" error in general?
>
> and yes it does all the time

Yes, it does not recognize those errors at all and hence cannot make
anything worse. Yum terminates before trying to skip anything.

Since I've earlier asked for the full Yum output, here it is, reproduced
by downgrading a few packages. Output of "yum update" and "yum update
--skip-broken" is exactly the same:

# yum update
Loaded plugins: auto-update-debuginfo, langpacks, presto, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package gtk2.x86_64 0:2.24.10-1.fc17 will be updated
---> Package gtk2.x86_64 0:2.24.10-2.fc17 will be an update
---> Package gtk2-immodule-xim.x86_64 0:2.24.10-1.fc17 will be updated
---> Package gtk2-immodule-xim.x86_64 0:2.24.10-2.fc17 will be an update
---> Package redhat-lsb.x86_64 0:4.0-11.fc17 will be updated
---> Package redhat-lsb.x86_64 0:4.1-4.fc17 will be an update
--> Processing Dependency: redhat-lsb-printing = 4.1 for package: redhat-lsb-4.1-4.fc17.x86_64
--> Processing Dependency: redhat-lsb-languages = 4.1 for package: redhat-lsb-4.1-4.fc17.x86_64
--> Processing Dependency: redhat-lsb-desktop(x86-64) = 4.1 for package: redhat-lsb-4.1-4.fc17.x86_64
--> Processing Dependency: redhat-lsb-cxx(x86-64) = 4.1 for package: redhat-lsb-4.1-4.fc17.x86_64
--> Processing Dependency: redhat-lsb-core(x86-64) = 4.1 for package: redhat-lsb-4.1-4.fc17.x86_64
--> Running transaction check
---> Package redhat-lsb-core.x86_64 0:4.1-4.fc17 will be installed
--> Processing Dependency: redhat-lsb-submod-security(x86-64) = 4.1 for package: redhat-lsb-core-4.1-4.fc17.x86_64
---> Package redhat-lsb-cxx.x86_64 0:4.1-4.fc17 will be installed
---> Package redhat-lsb-desktop.x86_64 0:4.1-4.fc17 will be installed
--> Processing Dependency: redhat-lsb-submod-multimedia(x86-64) = 4.1 for package: redhat-lsb-desktop-4.1-4.fc17.x86_64
--> Processing Dependency: qt3(x86-64) for package: redhat-lsb-desktop-4.1-4.fc17.x86_64
--> Processing Dependency: qt-x11(x86-64) for package: redhat-lsb-desktop-4.1-4.fc17.x86_64
--> Processing Dependency: qt(x86-64) for package: redhat-lsb-desktop-4.1-4.fc17.x86_64
---> Package redhat-lsb-languages.x86_64 0:4.1-4.fc17 will be installed
--> Processing Dependency: perl(Test::Simple) for package: redhat-lsb-languages-4.1-4.fc17.x86_64
--> Processing Dependency: perl(Test::Harness) for package: redhat-lsb-languages-4.1-4.fc17.x86_64
--> Processing Dependency: perl(Pod::Plainer) for package: redhat-lsb-languages-4.1-4.fc17.x86_64
--> Processing Dependency: perl(ExtUtils::MakeMaker) for package: redhat-lsb-languages-4.1-4.fc17.x86_64
--> Processing Dependency: perl(CPAN) for package: redhat-lsb-languages-4.1-4.fc17.x86_64
--> Processing Dependency: perl(CGI) for package: redhat-lsb-languages-4.1-4.fc17.x86_64
---> Package redhat-lsb-printing.x86_64 0:4.1-4.fc17 will be installed
--> Running transaction check
---> Package perl-CGI.noarch 0:3.52-212.fc17 will be installed
--> Processing Dependency: perl(FCGI) for package: perl-CGI-3.52-212.fc17.noarch
---> Package perl-CPAN.noarch 0:1.9600.01-212.fc17 will be installed
--> Processing Dependency: perl(HTTP::Tiny) >= 0.005 for package: perl-CPAN-1.9600.01-212.fc17.noarch
--> Processing Dependency: perl(Digest::SHA) for package: perl-CPAN-1.9600.01-212.fc17.noarch
---> Package perl-ExtUtils-MakeMaker.noarch 0:6.62-2.fc17 will be installed
--> Processing Dependency: perl(ExtUtils::Packlist) for package: perl-ExtUtils-MakeMaker-6.62-2.fc17.noarch
--> Processing Dependency: perl(ExtUtils::Manifest) for package: perl-ExtUtils-MakeMaker-6.62-2.fc17.noarch
--> Processing Dependency: perl(ExtUtils::Installed) for package: perl-ExtUtils-MakeMaker-6.62-2.fc17.noarch
--> Processing Dependency: perl(ExtUtils::Install) for package: perl-ExtUtils-MakeMaker-6.62-2.fc17.noarch
---> Package perl-Pod-Plainer.noarch 0:1.03-1.fc17 will be installed
---> Package perl-Test-Harness.noarch 0:3.23-212.fc17 will be installed
--> Processing Dependency: perl-devel for package: perl-Test-Harness-3.23-212.fc17.noarch
---> Package perl-Test-Simple.noarch 0:0.98-212.fc17 will be installed
---> Package qt.x86_64 1:4.8.2-2.fc17 will be installed
--> Processing Dependency: qt-settings for package: 1:qt-4.8.2-2.fc17.x86_64
---> Package qt-x11.x86_64 1:4.8.2-2.fc17 will be installed
---> Package qt3.x86_64 0:3.3.8b-41.fc17 will be installed
---> Package redhat-lsb-submod-multimedia.x86_64 0:4.1-4.fc17 will be installed
---> Package redhat-lsb-submod-security.x86_64 0:4.1-4.fc17 will be installed
--> Running transaction check
---> Package perl-Digest-SHA.x86_64 1:5.61-212.fc17 will be installed
---> Package perl-ExtUtils-Install.noarch 0:1.56-212.fc17 will be installed
---> Package perl-ExtUtils-Manifest.noarch 0:1.60-1.fc17 will be installed
---> Package perl-FCGI.x86_64 1:0.74-2.fc17 will be installed
---> Package perl-HTTP-Tiny.noarch 0:0.012-212.fc17 will be installed
---> Package perl-devel.x86_64 4:5.14.2-212.fc17 will be installed
--> Processing Dependency: systemtap-sdt-devel for package: 4erl-devel-5.14.2-212.fc17.x86_64
--> Processing Dependency: perl(ExtUtils::ParseXS) for package: 4erl-devel-5.14.2-212.fc17.x86_64
---> Package qt-settings.noarch 0:4.8-15.fc17 will be installed
--> Running transaction check
---> Package perl-ExtUtils-ParseXS.noarch 1:2.2210-212.fc17 will be installed
---> Package systemtap-sdt-devel.x86_64 0:1.8-1.fc17 will be installed
--> Finished Dependency Resolution
Error: Protected multilib versions: redhat-lsb-4.1-4.fc17.x86_64 != redhat-lsb-4.0-11.fc17.i686


--
Fedora release 17 (Beefy Miracle) - Linux 3.4.3-1.fc17.x86_64
loadavg: 0.63 0.55 0.51
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 06-25-2012, 09:09 PM
Michael Schwendt
 
Default Problems with update -- redhat-lsb conflicts
On Mon, 25 Jun 2012 13:32:13 -0700, Joe Zeff wrote:

> On 06/25/2012 01:12 PM, Reindl Harald wrote:
> > --skip-broken tends generally to fail on multilib in a way that
> > it pulls i686 deps if they seem to satisfy deps by version
> > on a pure x86_64 system as long you do not "exclude=*.i686"
>
> I'm not sure that that's --skip-broken's fault; it sounds more like a
> problem with how the deps are defined, or possibly how they're evaluated.

I tend to agree. --skip-broken would first need to recognize something as
"broken", such as a dep that cannot be resolved. Only then it would
exclude the package and try to resolve deps again.

The typical case where an update on x86_64 pulls in lots of unwanted i686
packages is when an update "takes away" something that is still needed by
other [installed] packages. The depsolver finds [possibly older] i686
packages that still provide the needed things and can be used to resolve
the non-arch-specific deps.

--
Fedora release 17 (Beefy Miracle) - Linux 3.4.3-1.fc17.x86_64
loadavg: 0.14 0.48 0.56
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Page 3 of 3 < 12 3

Thread Tools




All times are GMT. The time now is 08:44 AM.

VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org

Contact Us - Linux Archive - Archive - Top -