I think that my summary speaks for itself. I think that you should be GPG
signing packages. And I'm somebody who has the option checked off for
downloading source packages along with binaries, so I think that should be
available, too (it was with Fedora Core and many of the other repositories that
------- Additional Comments From firstname.lastname@example.org 2004-12-16 15:11:28 ----
We do sign packages, using the GPG key advertised on the web site
If you think we have missed signing any packages please provide specific details.
------- Additional Comments From email@example.com 2004-12-16 15:12:15 ----
P.S. Source packages are available from our apt repository which you can browse at
------- Bug moved to this database by firstname.lastname@example.org 2005-03-30 18:30 -------
This bug previously known as bug 2320 at https://bugzilla.fedora.us/
Originally filed under the Fedora Legacy product and General component.
Unknown priority P2. Setting to default priority "normal".
Unknown platform PC. Setting to default platform "All".
Unknown severity minor. Setting to default severity "normal".
Setting qa contact to the default for this product.
This bug either had no qa contact or an invalid one.
I figured out the problem with the GPG signatures. You need to make your
documentation for up2date as complete as it is for yum and apt, and add the step
about downloading the GPG key.
As for the SRPMs, what is the problem with making them available via up2date?
up2date in Fedora Core uses yum as a backend, or apt. Yum in FC 1 does not
support downloading of source packages, therefor up2date when used with a yum
backend cannot either. Configure up2date to use apt as your backend, and then
you can gather srpms through up2date.
Closing this as notabug.
Up2date has to support downloading of source packages because the Fedora Core
update service uses a yum repository and I can download source packages through
WHich version of Fedora Cre are you referencing? THe yum in FC1 that we use
does not support srpm repositories.
With Fedora Core 1's up2date I downloaded every single SRPM for every offical
Fedora Core update that came out since I installed it. They are still on my
hard drive, I would be happy to show them to you. I even used mirrors for most
of them (since the Red Hat server was too slow) and the SRPMs still downloaded.
And yes, the configuration lines for those started with yum http:// or ftp:// I
forget which I'm booted into windows right now. Try it for yourself, get a
fresh install of Fedora Core 1, configure up2date to download source packages,
and watch it work. Although again I suggest changing the
/etc/sysconfig/rhn/sources file to look at an official mirror rather than Red
Hat itself, or you will be in a mess. I've used Duke and NCSU. I used to use
Virginia Tech but they changed something on their server and I'm not sure if
they are continuing to mirror.
I may be mistaken then on the FC1. RHL9 was not possible. I'll look into
generating metadata in the srpm directories.
headers for SRPMS are now populated. You'll have to add a line for the srpms
repository. I'm keeping them seperated so that users that don't want srpms
don't have to download the package information and header cache for them.
I don't seem to have separate headers for the source packages from the updates
that I have received from Red Hat. I don't think that this is actually going to