Red Hat Bugzilla – Bug 152858
up2date does not handle apt-mirror's
Last modified: 2007-04-18 13:22:27 EDT
This bug is listed as Fedora Core 2 on the Red Hat Bugzilla, but I think that it
might be affecting Fedora Core 1 as well. I've been experiencing similar
problems to what this person has described on the Fedora Developers' mailing
list when using the Planet CCRMA repositories
<http://ccrma.stanford.edu/planetccrma/software/>. His original message does
not seem to be in the archives yet, but here it is copy-and-pasted from the
-------- Original Message --------
From: Jos Vos <firstname.lastname@example.org>
Subject: APT repository problems with up2date
Before I start digging in the up2date code myself, maybe someone
can comment on this:
I have a problem when using up2date up2date with my self-created
APT repositories. When updating, it complains about conflicting
files: it just thinks that a long list of directories that are
shared among packages conflict with each other.
Apt-get itself (and synaptic) seems to work fine with the same
repository, only with up2date there is a problem. Also, up2date
with a yum repository of then same package set works fine, as
does yum itself.
FWIW: I generate my APT repositories with --flat --bloat.
-- Jos Vos <email@example.com>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
fedora-devel-list mailing list
However, my tests have shown that the same problems exist when accessing both
the Yum and APT repositories on this site using Up2Date, so I am not certain of
the exact cause of these errors. However, both APT and Yum seem to work fine
without bringing up these irrelevant "file conflicts," so it would seem that
either Up2Date has bugs or is otherwise very picky about how the repository
headers describe the packages. Since Up2Date has not been well documented
(release notes only) since the addition of Yum and APT capabilities, and I don't
think that the developers really know what to do either since they are not
saying anything on the list about it, I really didn't know what else to do other
than bring up this person's findings and his patch on The Fedora Legacy
------- Additional Comments From firstname.lastname@example.org 2004-11-27 21:13:35 ----
Someone on the Fedora Developer's list finally pointed out another bug report
that covers the same issue. I'm trying to get communication between the two
------- Bug moved to this database by email@example.com 2005-03-30 18:29 -------
This bug previously known as bug 2306 at https://bugzilla.fedora.us/
Originally filed under the Fedora Legacy product and General component.
Unknown priority P3. Setting to default priority "normal".
Unknown platform PC. Setting to default platform "All".
Unknown severity blocker. 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.
This is outside of the scope of Fedora Legacy. However, bug #106123 deals with
this for FC devel -- marking duplicate.
*** This bug has been marked as a duplicate of 106123 ***