On 4/7/20 6:18 PM, Thierry Vignaud wrote:
Le lun. 23 mars 2020 à 15:47, Panu Matilainen <pmati...@redhat.com <mailto:pmati...@redhat.com>> a écrit :


    On 3/23/20 3:22 PM, Panu Matilainen wrote:
     >
     > So soon you say? Well, its almost a year since 4.15 alpha and annual
     > release schedule isn't *that* fast. More like trying to get back on
     > track with this release stuff after some erratic years.
     >
     > Anyway, here goes. The two major themes here are: preparing to
    finally
     > kick Berkeley DB out, and (conditional) macro expressions. If you
    ever
     > thought %{?foo:bar} is too limited, this one is for you.

    So this is what I get for trying to cut a release on Monday: the
    originally linked rpm-4.15.90-git14970 snapshot has a buggy rpm.pc file
    which prevents using it for linking. Since an important aspect of alpha
    testing is testing other software... duh.

    Just pushed a new snapshot (rpm-4.15.90-git14971) to fix that and
    updated the download links + hashes, but if you were eager enough to
    have grabbed the first snapshot then you'll want to update.

     >
     > Highlights include:
     > - Powerful macro and %if expressions including ternary operator
     > - New sqlite and read-only BDB backends, NDB promoted to stable
     > - Automatic SSD detection and optimization on Linux

    Seems I also forgotten some highlights as well:

    - Support for dependency generation with parametric macros
    - Support for dependency generation based on MIME types

    The details and download info still at

    https://rpm.org/wiki/Releases/4.16.0

    Apologies for the confusion,


Another regression is in rpmbuild:
$ rpmbuild -ba ~/rpmbuild/SPECS/foobar.spec
error: line 5: Tag takes single token only: Release:        %{mkrel 1}
This basically breaks building all of 13 000 packages in Mageia because all of them use this:
Release: %mkrel 1

Which expands to a nicely formatted release number according to the distro version (similar to %{dist} in Fedora).
Can you please rollback that change?

https://github.com/rpm-software-management/rpm/issues/1167

This appears to be a build configuration issue rather than an rpm regression. Further updates to the ticket, thanks.

        - Panu -

_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to