Red Hat Bugzilla – Bug 152853
up2date not work for SRPMS
Last modified: 2008-05-01 11:38:06 EDT
I just switched to download.fedoralegacy.org for my FC1 updates and can't seem
to get around this error:
Testing package set / solving RPM inter-dependencies...
cups-1.1.19-13.2.legacy.src There was a fatal error communicating with the
server. The message was:
An HTTP error occurred:
Status Code: 404
Error Message: Not Found
The problem appears to be that
http://download.fedoralegacy.org/fedora/1/updates/i386//SRPMS is missing. When
look at some of the mirrors I used prior to switching to
download.fedoralegacy.org they all have both .../updates/SRPMS and
.../updates/i386/SRPMS, whereas download.fedoralegacy.org and its mirrors only
------- Additional Comments From email@example.com 2005-02-22 16:04:21 ----
I'm not an up2date user so I can't check this, but can you confirm that you have
followed the instructions at
------- Additional Comments From firstname.lastname@example.org 2005-02-22 18:04:28 ----
Yes, I have followed the instructions at
http://www.fedoralegacy.org/docs/up2date-fc1-reconfigure.php and RPM updates do
work. It is only the SRPM updates that don't work and I am quite sure it is due
to the missing SRPMS directory/sym-link that is missing.
------- Additional Comments From email@example.com 2005-03-07 07:26:46 ----
I don't think I want to do this, as it will break people who are wgetting or
syncing that directory. I'm sure they aren't expecting SRPMS inside an RPM
directory. I never have liked the SRPMS inside the binary package directory
A better solution is just to post how people can alter their up2date settings
------- Bug moved to this database by firstname.lastname@example.org 2005-03-30 18:29 -------
This bug previously known as bug 2281 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".
The original reporter of this bug does not have
an account here. Reassigning to the person who moved
it here, email@example.com.
Previous reporter was firstname.lastname@example.org.
Setting qa contact to the default for this product.
This bug either had no qa contact or an invalid one.