6:55 a.m.
I've been doing some testing using
up2date-3.9.13-2
Firstly an obvious should bail is:
up2date --get-source against a yum url, I believe yum-arch now indexes
headers of src.rpms but when running against fedora I get:
up2date --get-source synaptic
...
synaptic-0.43.1-0.fdr.1.rh90.93.src.rpm...
There was some sort of I/O error: HTTP Error 404: Not Found
Should we ignore src.rpm headers in yum archives as the path to them is
not necessarily obvious (parallel with yum directory, or a subdirectory,
etc).
This is better than with up2date-3.9.6-1 where it would download the
html error page :)
In addition I just tried to update to kernel test4 from arjanv's
repository (using apt up2date):
up2date --nox --force kernel
...
Test install failed because of package conflicts:
file /lib/modules from install of kernel-2.6.0-0.test4.1.32 conflicts
with file from package filesystem-2.2.1-4
rpm -qf /lib/modules/
filesystem-2.2.1-4
kernel-2.4.21-20.1.2024.2.1.nptl
kernel-2.6.0-0.test3.1.31
This seems odd to me as both kernel-2.4 spec and kernel 2.6 specs are
consistent in having /lib/modules in them, am I missing something
obvious as this should work.
Paul
12:48 p.m.
On Tue, Aug 26, 2003 at 12:55:42PM +0100, Paul Nasrat wrote:
I've been doing some testing using
up2date-3.9.13-2
Firstly an obvious should bail is:
up2date --get-source against a yum url, I believe yum-arch now indexes
headers of src.rpms but when running against fedora I get:
up2date --get-source synaptic
...
synaptic-0.43.1-0.fdr.1.rh90.93.src.rpm...
There was some sort of I/O error: HTTP Error 404: Not Found
Should we ignore src.rpm headers in yum archives as the path to them is
not necessarily obvious (parallel with yum directory, or a subdirectory,
etc).
Right now it guesses it's parallel with the yum directory,
since this seemed the most popular layout after a quick survery.
But yum doesnt indicate where SRPMS are stashed in any obvious
way, so it's currently a guess. If the SRPMS stuff gets standardized,
I can make it respect that.
In addition I just tried to update to kernel test4 from arjanv's
repository (using apt up2date):
up2date --nox --force kernel
...
Test install failed because of package conflicts:
file /lib/modules from install of kernel-2.6.0-0.test4.1.32 conflicts
with file from package filesystem-2.2.1-4
rpm -qf /lib/modules/
filesystem-2.2.1-4
kernel-2.4.21-20.1.2024.2.1.nptl
kernel-2.6.0-0.test3.1.31
This seems odd to me as both kernel-2.4 spec and kernel 2.6 specs are
consistent in having /lib/modules in them, am I missing something
obvious as this should work.
Odd to get a conflict on a dir... I'll investigate.
Adrian
2:24 p.m.
On Tue, 2003-08-26 at 13:48, Adrian Likins wrote:
On Tue, Aug 26, 2003 at 12:55:42PM +0100, Paul Nasrat wrote:
> I've been doing some testing using
>
> up2date-3.9.13-2
>
> Firstly an obvious should bail is:
>
> up2date --get-source against a yum url, I believe yum-arch now indexes
> headers of src.rpms but when running against fedora I get:
>
> up2date --get-source synaptic
> ...
> synaptic-0.43.1-0.fdr.1.rh90.93.src.rpm...
> There was some sort of I/O error: HTTP Error 404: Not Found
>
> Should we ignore src.rpm headers in yum archives as the path to them is
> not necessarily obvious (parallel with yum directory, or a subdirectory,
> etc).
>
Right now it guesses it's parallel with the yum directory,
since this seemed the most popular layout after a quick survery.
But yum doesnt indicate where SRPMS are stashed in any obvious
way, so it's currently a guess. If the SRPMS stuff gets standardized,
I can make it respect that.
You can't just use whatever the header.src.info points stuff to?
or is it the arch thing that's holding it up?
-sv
2:34 p.m.
On Tue, Aug 26, 2003 at 03:24:06PM -0400, seth vidal wrote:
On Tue, 2003-08-26 at 13:48, Adrian Likins wrote:
> On Tue, Aug 26, 2003 at 12:55:42PM +0100, Paul Nasrat wrote:
> > I've been doing some testing using
> >
> > up2date-3.9.13-2
> >
> > Firstly an obvious should bail is:
> >
> > up2date --get-source against a yum url, I believe yum-arch now indexes
> > headers of src.rpms but when running against fedora I get:
> >
> > up2date --get-source synaptic
> > ...
> > synaptic-0.43.1-0.fdr.1.rh90.93.src.rpm...
> > There was some sort of I/O error: HTTP Error 404: Not Found
> >
> > Should we ignore src.rpm headers in yum archives as the path to them is
> > not necessarily obvious (parallel with yum directory, or a subdirectory,
> > etc).
> >
> Right now it guesses it's parallel with the yum directory,
> since this seemed the most popular layout after a quick survery.
> But yum doesnt indicate where SRPMS are stashed in any obvious
> way, so it's currently a guess. If the SRPMS stuff gets standardized,
> I can make it respect that.
>
You can't just use whatever the header.src.info points stuff to?
How do I find the header.src.info file?
Adrian
2:53 p.m.
On Tue, Aug 26, 2003 at 03:41:39PM -0400, seth vidal wrote:
> > You can't just use whatever the header.src.info points
stuff to?
>
> How do I find the header.src.info file?
It's always in headers/ if the repository has had yum-arch -s run on it
(in yum 2.0.1 or better)
I'm not seeing that. I'm seeing it placed into the headers/
subdir of SRPMS, which doesnt really help me, since I dont know
how to find the SRPMS subdir (I don't specify them seperately
atm... I suppose I could, but I'm not sure how to handle old
non-src having yum repos). I would like to see the placement
of the RPMS/ and SRPMS dirs standardized (or pointed at by
some standard metadata file or whatever...). Basically, just
looking for a way to specify one url and be able to reliably
find src and bin.
Having a seperate repo type for yum-src seems a bit
odd as well. But I guess thats more inline with the way yum
does it with seperate repos for src and bin packages.
Adrian
7599
days inactive
7599
days old
5 comments
3 participants
participants (3)
-
Adrian Likins -
Paul Nasrat -
seth vidal