Fair enough. I'll workaround it by recommending to remove the manual provides.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1166#issuecomment-610901737_
Closed #1166.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1166#event-3213673962___
Rpm-maint mailing list
Rpm-maint@lists.r
Merging manual provides with automatic provides (with manual ones
overriding automatic ones) would prevent us to detect manual provides that
can be removed b/c the automation took care of it…
Le mar. 7 avr. 2020 à 13:09, Miro Hrončok a
écrit :
> Would it be to hackish to merge 0 with whatever is
And as a side note, I suppose I cannot read the existing provides from the
dependency generator?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1166#issuecomment-6103288
Would it be to hackish to merge 0 with whatever is generated by generators,
preserving 0 (as in: the manual one wins over the generated one).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-ma
This is an old problem, not specific to 4.16 at all. Those provides will have
different flags in them, which prevents them from being merged (in existing
implementation). Similarly this will create three different requires:
```
Requires: /bin/sh
Requires(post): /bin/sh
Requires(pre): /bin/sh
```
