Debian repository layout
Michael_E_Brown at Dell.com
Michael_E_Brown at Dell.com
Tue May 22 10:50:15 CDT 2007
Sadhana,
Did you run the dpkg-scanpackages utility to generate the repository metadata? I have not done this on the current humbolt repo, as I was leaving that open for you to write.
--
Michael
-----Original Message-----
From: firmware-tools-devel-bounces at lists.us.dell.com on behalf of Sadhana_B at dell.com
Sent: Tue 5/22/2007 9:31 AM
To: martin.pitt at ubuntu.com; Brown, Michael E
Cc: firmware-tools-devel at lists.us.dell.com; Shandilya, Sandeep K; scott at ubuntu.com
Subject: Debian repository layout
Hi martin,
I've been trying to create a debian repository layout with the firmware
packages. I used the debian-repository how-to documentation and also
tried the reprepro package. But nothing seems to work. I don't know what
I am missing out. Even the repository layout proposed by michael on
humbolt is not working on my synaptic. Guess there is a packages.gz file
missing here. But even if I use the dpkg-scanpackages and generate a
packages.gz file(on a repository on my machine), I'm not able to get
synaptic to show me the packages in this repository. I get the same
error message: "got a single header line over 360 chars".
Can you help me with the repository layout?
Regards,
Sadhana
-----Original Message-----
From: Martin Pitt [mailto:martin.pitt at ubuntu.com]
Sent: Friday, May 18, 2007 1:07 PM
To: Brown, Michael E
Cc: firmware-tools-devel at lists.us.dell.com; Scott James Remnant; B,
Sadhana - Authorized Dell Representative; Shandilya, Sandeep K; Martin
Pitt
Subject: Re: review request: firmware-tools, ubuntu/debian sponsor
needed
Hi Michael,
Michael E Brown [2007-05-17 23:48 -0500]:
> > ==== firmware-addon-dell ====
> > | +Package: firmware-addon-dell
> > | +Architecture: any
> >
> > There is nothing platform dependent in the package, so this should
> > be 'all'.
>
> Well, this was a major discussion point for fedora.
> Firmware-addon-dell depends on libsmbios. The libsmbios package is
> only available/applicable for i386, x86_64, and ia64.
>
> If it is available in all arches it creates an incomplete dependency
> tree for all other arches.
>
> Comments? Is making this *all* still the right answer considering
this?
Right, of course we have the same problem, but 'any' is the wrong
solution anyway. Either it is 'i386 amd64 ia64' or stays at arch:all.
Of course the latter will produce some uninstallable packages on the
other architectures, but *shrug*. There is no clear policy about that,
so it's mainly a matter of taste, I'd say.
Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
_______________________________________________
firmware-tools-devel mailing list
firmware-tools-devel at lists.us.dell.com
http://lists.us.dell.com/mailman/listinfo/firmware-tools-devel
More information about the firmware-tools-devel
mailing list