For now I've gotten rid of off the globs/excludes but this really needs to
be fixed somehow...
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
On Tue, 2019-01-15 at 10:40 -0600, Richard Shaw wrote:
> Ooooaaa...
>
> So this has been around since at least 2017 and there's no fix?
Much longer than that. At least since 2012, probably earlier.
%exclude is discouraged, which is why it doesn't seem to have higher
priority. See also:
Ooooaaa...
So this has been around since at least 2017 and there's no fix?
Is there an option to make it a warning again instead of an error?
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
On Tue, Jan 15, 2019 at 7:42 AM Richard Shaw wrote:
> Is the %exclude just not working for the build-ids? That's all I can come up
> with.
See:
https://bugzilla.redhat.com/show_bug.cgi?id=878863
https://bugzilla.redhat.com/show_bug.cgi?id=1482698
--
Jerry James
http://www.jamezone.org/
On 15/01/2019 14:41, Richard Shaw wrote:
Is the %exclude just not working for the build-ids? That's all I can
come up with.
Well it is working, but it doesn't exclude them because they
don't match any of the patterns.
Those excludes only match files in %{_libdir} not in the .build-id
I'm working on the recent release of mythtv and everything compiled fine
until I got to the rpm packaging part which I got the following output:
File listed twice:
/usr/lib/.build-id/01/02700911bb4fe728258f16703a35d816ddb31f
File listed twice:
