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



--- Comment #12 from Susi Lehtola <[email protected]> ---
Upstream has a weird attitude about only building from their release tarballs
due to bad experiences (i) a long time ago (ii) without standard build
infrastucture. If you look at the log, the build silently uses developer mode
since it detects .devel. Since there are no nightly release builds, it's
impossible to build the state-of-the-art software without doing this. The
latest stable release has several bugs and defects that prevent its use in
packages, e.g. the lack of a proper python build.

As to the versioning guidelines, it appears those have changed over the years;
when I started doing Fedora packaging almost 20 years ago the releases were
marked in the release tag. Like I said, the package is not going to be imported
until the 3.0.0 release is minted upstream, and according to Fedora policy, it
is perfectly alright to reset the changelog and version history upon inclusion
in Fedora.

Thank you for pointing out the missing metadata and explaining why it matters;
I will look into patching this upstream.

PS. there's a world of difference between pregeneration that takes days (libxc)
and pregeneration that takes fractions of a millisecond (trexio).


-- 
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=2529728

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202529728%23c12

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to