On Fri, 15 Jun 2012 22:35:32 +0100, John Austin wrote:

> I believe this is just a repo problem
> The i686 and x86_64 versions are now available
>
>
> ja@avon ~ 1$ rpm -qa|grep redhat-lsb
> redhat-lsb-core-4.1-4.fc17.i686
> redhat-lsb-cxx-4.1-4.fc17.i686
> redhat-lsb-submod-multimedia-4.1-4.fc17.x86_64
> redhat-lsb-languages-4.1-4.fc17.x86_64
> redhat-lsb-4.1-4.fc17.i686
> redhat-lsb-submod-security-4.1-4.fc17.i686
> redhat-lsb-printing-4.1-4.fc17.x86_64
> redhat-lsb-4.1-4.fc17.x86_64
> redhat-lsb-submod-security-4.1-4.fc17.x86_64
> redhat-lsb-desktop-4.1-4.fc17.x86_64
> redhat-lsb-core-4.1-4.fc17.x86_64
> redhat-lsb-desktop-4.1-4.fc17.i686
> redhat-lsb-submod-multimedia-4.1-4.fc17.i686
> redhat-lsb-cxx-4.1-4.fc17.x86_64

The i686 build is gone on dl.fedoraproject.org again:
http://dl.fedoraproject.org/pub/fedora/linux/updates/17/x86_64/

$ host dl.fedoraproject.org
dl.fedoraproject.org has address 209.132.181.23
dl.fedoraproject.org has address 209.132.181.27
dl.fedoraproject.org has address 209.132.181.24
dl.fedoraproject.org has address 209.132.181.25
dl.fedoraproject.org has address 209.132.181.26
--
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

On Sat, 16 Jun 2012 12:41:08 -0700, Jonathan Ryshpan wrote:

> > > Still doesn't seem to be in the repos.
> >
> > I've reported it just in case:
> > https://fedorahosted.org/rel-eng/ticket/5220
>
> Thanks. Should I have done this myself? What's the relation between
> tickets on this "Hosted" page and bugs reported on the Redhat bugzilla?

The ticket system I've used is the one for Fedora Release Engineering:

http://fedoraproject.org/wiki/ReleaseEngineering

The individual packager(s) usually do not have intimate knowledge of the
repo compose process, the multiarch repo compose strategy and any bugs in
this. The people that are in charge of the repos could more easily tell
whether redhat-lsb.i686 is supposed to appear in the x86_64 repo and then
figure out why it's missing for the update. Occasionally, users ask about
other "protected multilib version" errors when trying to update, and it's
not normal that the i686 build of a multiarch package appears later in a
repo than the x86_64 build since the are expected to enter the repo at the
same time. [There's a small chance that fundamental changes in the
redhat-lsb packaging influenced the multiarch repo composing. Its package
changelog doesn't mention anything obvious, however.]
--
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

> [There's a small chance that fundamental changes in the
> redhat-lsb packaging influenced the multiarch repo composing. Its package
> changelog doesn't mention anything obvious, however.]

I've now also filed https://bugzilla.redhat.com/832771

The new redhat-lsb moved /lib64/ld-lsb-x86-64.so.3 from redhat-lsb to the
redhat-lsb-core subpackage. I think this affects the multiarch repo compose.
--
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

On Sun, 2012-06-17 at 11:42 +0200, Michael Schwendt wrote:
> On Fri, 15 Jun 2012 22:35:32 +0100, John Austin wrote:
>
> > I believe this is just a repo problem
> > The i686 and x86_64 versions are now available
> >
> >
> > ja@avon ~ 1$ rpm -qa|grep redhat-lsb
> > redhat-lsb-core-4.1-4.fc17.i686
> > redhat-lsb-cxx-4.1-4.fc17.i686
> > redhat-lsb-submod-multimedia-4.1-4.fc17.x86_64
> > redhat-lsb-languages-4.1-4.fc17.x86_64
> > redhat-lsb-4.1-4.fc17.i686
> > redhat-lsb-submod-security-4.1-4.fc17.i686
> > redhat-lsb-printing-4.1-4.fc17.x86_64
> > redhat-lsb-4.1-4.fc17.x86_64
> > redhat-lsb-submod-security-4.1-4.fc17.x86_64
> > redhat-lsb-desktop-4.1-4.fc17.x86_64
> > redhat-lsb-core-4.1-4.fc17.x86_64
> > redhat-lsb-desktop-4.1-4.fc17.i686
> > redhat-lsb-submod-multimedia-4.1-4.fc17.i686
> > redhat-lsb-cxx-4.1-4.fc17.x86_64
>
> The i686 build is gone on dl.fedoraproject.org again:
> http://dl.fedoraproject.org/pub/fedora/linux/updates/17/x86_64/
>
> $ host dl.fedoraproject.org
> dl.fedoraproject.org has address 209.132.181.23
> dl.fedoraproject.org has address 209.132.181.27
> dl.fedoraproject.org has address 209.132.181.24
> dl.fedoraproject.org has address 209.132.181.25
> dl.fedoraproject.org has address 209.132.181.26



Hmmm

Was it ever in
http://dl.fedoraproject.org/pub/fedora/linux/updates/17/x86_64/ ??

I "accidentally" by-passed the problem!

I maintain a partial updates repo (ie only updates of the packages
installed on my machines)

I brute force down loaded redhat-lsb-4.1-4.fc17.i686 from
http://dl.fedoraproject.org/pub/fedora/linux/updates/17/i386/
and stuck it in my repo

createrepo -q --update $local_repos/$installed_release

yum update

I had/have very little knowledge of "multiarch repo compose"

I initially reported the problem here
https://bugzilla.redhat.com/show_bug.cgi?id=824305
but then back tracked as I thought it was my finger trouble

John



--
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

On Sun, 17 Jun 2012 11:22:50 +0100, John Austin wrote:

> On Sun, 2012-06-17 at 11:42 +0200, Michael Schwendt wrote:
> > On Fri, 15 Jun 2012 22:35:32 +0100, John Austin wrote:
> >
> > > I believe this is just a repo problem
> > > The i686 and x86_64 versions are now available
> > >
> > >
> > > ja@avon ~ 1$ rpm -qa|grep redhat-lsb
> > > redhat-lsb-core-4.1-4.fc17.i686
> > > redhat-lsb-cxx-4.1-4.fc17.i686
> > > redhat-lsb-submod-multimedia-4.1-4.fc17.x86_64
> > > redhat-lsb-languages-4.1-4.fc17.x86_64
> > > redhat-lsb-4.1-4.fc17.i686
> > > redhat-lsb-submod-security-4.1-4.fc17.i686
> > > redhat-lsb-printing-4.1-4.fc17.x86_64
> > > redhat-lsb-4.1-4.fc17.x86_64
> > > redhat-lsb-submod-security-4.1-4.fc17.x86_64
> > > redhat-lsb-desktop-4.1-4.fc17.x86_64
> > > redhat-lsb-core-4.1-4.fc17.x86_64
> > > redhat-lsb-desktop-4.1-4.fc17.i686
> > > redhat-lsb-submod-multimedia-4.1-4.fc17.i686
> > > redhat-lsb-cxx-4.1-4.fc17.x86_64
> >
> > The i686 build is gone on dl.fedoraproject.org again:
> > http://dl.fedoraproject.org/pub/fedora/linux/updates/17/x86_64/
> >
> > $ host dl.fedoraproject.org
> > dl.fedoraproject.org has address 209.132.181.23
> > dl.fedoraproject.org has address 209.132.181.27
> > dl.fedoraproject.org has address 209.132.181.24
> > dl.fedoraproject.org has address 209.132.181.25
> > dl.fedoraproject.org has address 209.132.181.26
>
>
>
> Hmmm
>
> Was it ever in
> http://dl.fedoraproject.org/pub/fedora/linux/updates/17/x86_64/ ??

Probably not. I guess I was confused by your post and mistakingly
spotted the redhat-lsb-core.i686 package as redhat-lsb.i686.

The new subpackages are available for i686, but much of this is
questionable, too. (nothing obsoletes redhat-lsb-graphics either, btw)

# yum list redhat-lsb*|grep i6
redhat-lsb.i686 4.0-11.fc17 fedora
redhat-lsb-core.i686 4.1-4.fc17 updates
redhat-lsb-cxx.i686 4.1-4.fc17 updates
redhat-lsb-desktop.i686 4.1-4.fc17 updates
redhat-lsb-graphics.i686 4.0-11.fc17 fedora
redhat-lsb-languages.i686 4.1-4.fc17 updates
redhat-lsb-printing.i686 4.1-4.fc17 updates
redhat-lsb-submod-multimedia.i686 4.1-4.fc17 updates
redhat-lsb-submod-security.i686 4.1-4.fc17 updates
redhat-lsb-trialuse.i686 4.1-4.fc17 updates
--
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

On Fri, Jun 15, 2012 at 4:15 PM, Jonathan Ryshpan <jonrysh@pacbell.net> wrote:
> Yum upgrade reports that redhat-lsb needs to be updated, but can't
> because of a an error, to wit:
>> Protected multilib versions: redhat-lsb-4.1-4.fc17.x86_64 != redhat-lsb-4.0-11.fc17.i686
> What's going on? *Can I fix it, or must I wait on the repo managers? *If
> the repo managers, when will a fix be available?

I'm still seeing this - should I remove/re-install Chrome as someone
suggested, or just wait it out?

--
-jayson
--
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

On Sun, 2012-06-17 at 12:02 +0200, Michael Schwendt wrote:
> > [There's a small chance that fundamental changes in the
> > redhat-lsb packaging influenced the multiarch repo composing. Its package
> > changelog doesn't mention anything obvious, however.]
>
> I've now also filed https://bugzilla.redhat.com/832771
>
> The new redhat-lsb moved /lib64/ld-lsb-x86-64.so.3 from redhat-lsb to the
> redhat-lsb-core subpackage. I think this affects the multiarch repo compose.

It's still there, after today's burst of updates. Thanks for filing the
bug.

jon


--
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

On Mon, 18 Jun 2012 19:48:37 -0400, Jayson Rowe wrote:

> On Fri, Jun 15, 2012 at 4:15 PM, Jonathan Ryshpan wrote:
> > Yum upgrade reports that redhat-lsb needs to be updated, but can't
> > because of a an error, to wit:
> >> Protected multilib versions: redhat-lsb-4.1-4.fc17.x86_64 != redhat-lsb-4.0-11.fc17.i686
> > What's going on? *Can I fix it, or must I wait on the repo managers? *If
> > the repo managers, when will a fix be available?
>
> I'm still seeing this - should I remove/re-install Chrome as someone
> suggested, or just wait it out?

Well, do whatever works for you. "yum remove redhat-lsb.i686" should
give a hint what would happen. If any package actually *strictly* (!) requires
redhat-lsb.i686 (with exactly that arch) you still won't be able to update
afterwards. Fixing the redhat-lsb breakage has been put onto the shoulders
of the redhat-lsb packager(s) as one can read in the Fedora releng ticket #5220
(as they think the update is not really suitable for a stable release).

--
Fedora release 17 (Beefy Miracle) - Linux 3.4.2-4.fc17.x86_64
loadavg: 0.43 0.61 0.58
--
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

On Wed, 2012-06-20 at 20:17 +0200, Michael Schwendt wrote:
> On Mon, 18 Jun 2012 19:48:37 -0400, Jayson Rowe wrote:
>
> > On Fri, Jun 15, 2012 at 4:15 PM, Jonathan Ryshpan wrote:
> > > Yum upgrade reports that redhat-lsb needs to be updated, but can't
> > > because of a an error, to wit:
> > >> Protected multilib versions: redhat-lsb-4.1-4.fc17.x86_64 != redhat-lsb-4.0-11.fc17.i686
> > > What's going on? Can I fix it, or must I wait on the repo managers? If
> > > the repo managers, when will a fix be available?
> >
> > I'm still seeing this - should I remove/re-install Chrome as someone
> > suggested, or just wait it out?
>
> Well, do whatever works for you. "yum remove redhat-lsb.i686" should
> give a hint what would happen. If any package actually *strictly* (!) requires
> redhat-lsb.i686 (with exactly that arch) you still won't be able to update
> afterwards. Fixing the redhat-lsb breakage has been put onto the shoulders
> of the redhat-lsb packager(s) as one can read in the Fedora releng ticket #5220
> (as they think the update is not really suitable for a stable release).

It looks like I need this package. Here's an rpm log:

# rpm --erase --test redhat-lsb-4.0-11.fc17.x86_64 redhat-lsb-4.0-11.fc17.i686
error: Failed dependencies:
lsb >= 3.2 is needed by (installed) google-earth-stable-6.0.3.2197-0.x86_64
lsb >= 3.2 is needed by (installed) google-earth-stable-6.0.3.2197-0.x86_64

and google-earth (despite being proprietary) is one of my favorite
applications.

jon


--
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

On Thu, 2012-06-21 at 11:25 -0700, Jonathan Ryshpan wrote:
> On Wed, 2012-06-20 at 20:17 +0200, Michael Schwendt wrote:
> > On Mon, 18 Jun 2012 19:48:37 -0400, Jayson Rowe wrote:
> >
> > > On Fri, Jun 15, 2012 at 4:15 PM, Jonathan Ryshpan wrote:
> > > > Yum upgrade reports that redhat-lsb needs to be updated, but can't
> > > > because of a an error, to wit:
> > > >> Protected multilib versions: redhat-lsb-4.1-4.fc17.x86_64 != redhat-lsb-4.0-11.fc17.i686
> > > > What's going on? Can I fix it, or must I wait on the repo managers? If
> > > > the repo managers, when will a fix be available?
> > >
> > > I'm still seeing this - should I remove/re-install Chrome as someone
> > > suggested, or just wait it out?
> >
> > Well, do whatever works for you. "yum remove redhat-lsb.i686" should
> > give a hint what would happen...
>
> It looks like I need this package...

How can I tell apper not to check for updates to redhat-lsb? Currently
the icon indicating updates are ready is on all the time, making it
useless.



--
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