Steps to repro
1 grab http://arm.koji.fedoraproject.org/repos/dist-f14-build/latest/arm/repodata/p... 2 bzip2 -d primary.sqlite.bz2 3 sqlite 3 primary.sqlite 4 select location_base, location_href from packages where location_base not like 'http://arm.koji%' ;
You'll be greeted by a longish list (432) of packages with a bogus url, all of them on "http://hongkong/yum/base/12/arm".
Perhaps these could be purged? They aren't entries built in koji - and it breaks the OLPC image build :-/
thanks!
m
On Mon, Jul 25, 2011 at 10:17 PM, Martin Langhoff <martin.langhoff@gmail.com
wrote:
Steps to repro
1 grab http://arm.koji.fedoraproject.org/repos/dist-f14-build/latest/arm/repodata/p... 2 bzip2 -d primary.sqlite.bz2 3 sqlite 3 primary.sqlite 4 select location_base, location_href from packages where location_base not like 'http://arm.koji%' ;
You'll be greeted by a longish list (432) of packages with a bogus url, all of them on "http://hongkong/yum/base/12/arm".
Perhaps these could be purged? They aren't entries built in koji - and it breaks the OLPC image build :-/
Its a known issue, I thought it had been resolved though.
Peter
On Tue, Jul 26, 2011 at 4:01 AM, Peter Robinson pbrobinson@gmail.com wrote:
You'll be greeted by a longish list (432) of packages with a bogus url, all of them on "http://hongkong/yum/base/12/arm".
Its a known issue, I thought it had been resolved though.
Looks like it's still there. Who can fix it? How to fix it?
cheers,
m
On Tue, 2011-07-26 at 09:59 -0400, Martin Langhoff wrote:
On Tue, Jul 26, 2011 at 4:01 AM, Peter Robinson pbrobinson@gmail.com wrote:
You'll be greeted by a longish list (432) of packages with a bogus url, all of them on "http://hongkong/yum/base/12/arm".
Its a known issue, I thought it had been resolved though.
Looks like it's still there. Who can fix it? How to fix it?
Hongkong is the true hostname of a.k.fp.o and those packages were imported way back ... What we should probably do is rebuild those packages, since they're imported from the previous F12 effort Should be a relatively straightforward rebuild, unless they're FTBFS, in which case we should know about and fix that, too.
(Any volunteers?)
-Chris
Chris Tyler píše v Út 26. 07. 2011 v 10:26 -0400:
On Tue, 2011-07-26 at 09:59 -0400, Martin Langhoff wrote:
On Tue, Jul 26, 2011 at 4:01 AM, Peter Robinson pbrobinson@gmail.com wrote:
You'll be greeted by a longish list (432) of packages with a bogus url, all of them on "http://hongkong/yum/base/12/arm".
Its a known issue, I thought it had been resolved though.
Looks like it's still there. Who can fix it? How to fix it?
Hongkong is the true hostname of a.k.fp.o and those packages were imported way back ... What we should probably do is rebuild those packages, since they're imported from the previous F12 effort Should be a relatively straightforward rebuild, unless they're FTBFS, in which case we should know about and fix that, too.
wouldn't be a full rebuild of the repository information sufficient (if possible)? koji does only incremental changes to the existing repo AFAIK
Dan
On Tuesday, July 26, 2011 09:46:17 AM Dan Horák wrote:
Chris Tyler píše v Út 26. 07. 2011 v 10:26 -0400:
On Tue, 2011-07-26 at 09:59 -0400, Martin Langhoff wrote:
On Tue, Jul 26, 2011 at 4:01 AM, Peter Robinson pbrobinson@gmail.com
wrote:
You'll be greeted by a longish list (432) of packages with a bogus url, all of them on "http://hongkong/yum/base/12/arm".
Its a known issue, I thought it had been resolved though.
Looks like it's still there. Who can fix it? How to fix it?
Hongkong is the true hostname of a.k.fp.o and those packages were imported way back ... What we should probably do is rebuild those packages, since they're imported from the previous F12 effort Should be a relatively straightforward rebuild, unless they're FTBFS, in which case we should know about and fix that, too.
wouldn't be a full rebuild of the repository information sufficient (if possible)? koji does only incremental changes to the existing repo AFAIK
Dan
The issue is that the external repo si configured to not use a FQDN, which is somethning that should never ever be done, regardless its done, at some point we need to just drop that external repo. its not referenced and the packages pulled in from it are not in the Real repos. im not sure what tools your using martin, a workaround would be to just use a alias in /etc/hosts.
We really at this point should just drop the external repo and deal with the consequences.
anything pulled in from the external repository does need to be built. ive changed the url n koji. to use the fqdn. ill mark the current repos as invalid so that the repo metadata is rebuilt from scratch.
Dennis
-
Chris Tyler -
Dan Horák -
Dennis Gilmore -
Martin Langhoff -
Peter Robinson