[Bug 2229282] Review Request: yosyshq-abc - Sequential logic synthesis and formal verification (replacement for abc-* fedora package)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=2229282



--- Comment #5 from Jerry James <loganjerry@xxxxxxxxx> ---
(In reply to Gabriel Somlo from comment #4)
> The way I'm reading the instructions at
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-
> replacing-existing-packages , it should be:
> 
>     Provides: oldpackagename = $provEVR
> 
> where "$provEVR refers to an (Epoch-)Version-Release tuple the original
> unchanged package would have had if it had been version or release bumped."
> 
> In other words, the obsoleted package's "next-up" EVR, not the
> "%{version}-%{release}" of the *new* package. That makes sense to me,
> intuitively, as the new package should be an "update" for the obsoleted one.
> 
> Let me know what you think.

Right, but it also says:

"You usually use macros here because the provides EVR should continue to go up
as the renamed package advances in version and release."

And if you look down further at the first example, it has:

Provides: foo = 2:%{version}-%{release}

Because %version and %release are handy macros for continuing that upward
motion of the provides EVR.  In this case, the new package's EVR is higher than
the obsoleted package's EVR, which makes %version and %release useable for this
purpose.  You are free to use some other macro or macros if that makes sense to
you, but they need to increase in value every time either Version or Release
increases.

> I was plannin on F38 and rawhide, but if you want me to do f37 as well, I
> can -- please advise! :)

I asked because for Rawhide we can simply retire the existing abc package and
build cvc5 against this package.  I'm not sure how to handle F38, frankly.  I'd
be happy to avoid changing F37 at this point in its lifecycle.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2229282

Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202229282%23c5
_______________________________________________
package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite Conditions]     [KDE Users]

  Powered by Linux