0.5.15lorg3.1 loses epochs on rh7.3/rh8.0/rh9 (promoteepoch?)

[Panu Matilainen]

Dag Wieers wrote:
> On Tue, 8 Aug 2006, Panu Matilainen wrote:
>
>> On Tue, 8 Aug 2006, Axel Thimm wrote:
>>
>> >   In this prehistoric time it was unceivable that a package would
>> >   have an epoch of "0". A missing epoch was indeed a missing epoch
>> >   and nothing more or less. Unepoched dependencies and
>> >   rpm-comparisons had a sick algorithm which depended on the package
>> >   being installed or not.
>> >
>> >   BUT:
>> >
>> >   There were no explicit zero-epoch packages, neither were there
>> >   explicit zero-epoch in dependencies.
>>
>> Yes, but createrepo injects artificial zero epochs *everywhere*, and
>> that's the sole reason for this madness. You need to use createrepo -n
>> switch for repositories requiring promoteepoch behavior, that way it
>> doesn't add the false epochs.
>
> Are there any plans to do the right thing in createrepo and make a
> distinction between epoch (none) and epoch 0. Are the Yum and Smart
> developers interested to fix their software to understand the difference ?

Considering the "enthusiasm" I received when raising the zero-vs-no epoch
issue on metadata list back in May, and that neither repomd-capable yum
nor smart even run on systems from the promoteepoch days, I don't think
they're interested at all. And I can hardly blame them...

Apt-rpm *can* now (after quite a bit of pain) support repomd on those
legacy systems as long as some care is taken when creating the repository,
and I'd rather leave it at that. Let the sleeping dogs lie, ok? :)

   - Panu -