Fixed in commit 34b61a1f82f6f9b675ab4ca820b6255af63680f1
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #114.
--
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/114#event-975735400___
Rpm-maint mailing list
I've nothing against adding more brp-scripts as such, I haven't looked at this
in any detail but there seems to be useful stuff in there.
Enabling such a big pile of new stuff by default is a wholly different
question, but lets not get hung up on that. The other complaint wrt enablement
is
Closed #161.
--
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/pull/161#event-975960965___
Rpm-maint mailing list
Thanks for the patches. Merged.
--
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/pull/161#issuecomment-282279613___
Rpm-maint mailing
Closed #160.
--
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/pull/160#event-975961542___
Rpm-maint mailing list
Added as part of #161
--
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/pull/160#issuecomment-282279690___
Rpm-maint mailing list
While there is a real issue here. The proposed solution is not quite right.
Making commenting out a multiline macro illegal is kida silly. Still this need
some solution. We opened #158 for discussing this issue and to come up with a
better solution.
Still thank you very much for your work and
Closed #124.
--
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/pull/124#event-975979205___
Rpm-maint mailing list
I really don't see the point of this when one could just add the file as a
source. Yes, may be you need one more line in the spec but then you do not have
one more special thing.
There may be a legitimate need for a mechanism to allow using files from the
build root that are not available at
Closed #69.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/69#event-976000682___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
Closed #25.
--
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/pull/25#event-975970213___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
Closed #96.
--
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/pull/96#event-975970943___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
See #25
--
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/pull/96#issuecomment-282281248___
Rpm-maint mailing list
I really don't see us add Python as part of the spec file language. The trend
is rather to reduce dependencies. Also it raises the whole "What version of
Python?" question which was deliberately avoided by using lua.
--
You are receiving this because you are subscribed to this thread.
Reply
As long as high end tools cannot be sure that the data they are looking at are
actually the ones they are interested in but some random, similar looking data
added for a completely different purpose, this is of no use. Closing.
--
You are receiving this because you are subscribed to this
Closed #107.
--
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/pull/107#event-976010362___
Rpm-maint mailing list
On 24 February 2017 at 11:32, Panu Matilainen
wrote:
> I've nothing against adding more brp-scripts as such, I haven't looked at
> this in any detail but there seems to be useful stuff in there.
>
> Enabling such a big pile of new stuff by default is a wholly different
```
error: invalid dependency (bad format): (crate(spin) >= 0.4.0 with crate(spin)
< 0.5.0)
```
I know that `with` is not something what RPM supports, but I suspect that any
other rich dep will cause same error.
RPM is 4.13.0.1.
--
You are receiving this because you are subscribed to this
`parseDep()` from `build/rpmfc.c` does it's own parser, so I think if I will
reuse `rpmrichParse()` from `lib/rpmds.h`, we will construct full string, then
pass constructed information to `rpmdsSinglePool()` and finally call
`rpmfcAddFileDep()` on newly created rpmds.
I suppose this should
20 matches
Mail list logo