On Tue, Aug 23, 2016 at 12:48:40PM -0500, Jason L Tibbitts III wrote:
> > "ZJ" == Zbigniew Jędrzejewski-Szmek writes:
>
> ZJ> %changelog would have to be stored separately. This would apply even
> ZJ> for qthe case when no "external" changes were made — just normal updates
> ZJ> by the packag
> "ZJ" == Zbigniew Jędrzejewski-Szmek writes:
ZJ> %changelog would have to be stored separately. This would apply even
ZJ> for qthe case when no "external" changes were made — just normal updates
ZJ> by the package managers — since there's no way for pyp2rpm to know
ZJ> what happened in the p
On Tue, Aug 23, 2016 at 11:10:08AM -0500, Jason L Tibbitts III wrote:
> > "PV" == Petr Viktorin writes:
>
> PV> - Make it standard practice in Fedora to use this data and treat the
> PV> spec file as an immutable generated artifact.
>
> If you're saying that any changes which are made to the
> "PV" == Petr Viktorin writes:
PV> - Make it standard practice in Fedora to use this data and treat the
PV> spec file as an immutable generated artifact.
If you're saying that any changes which are made to the spec file (say,
by release engineering doing a rebuild or by someone tweaking the
On 08/17/2016 06:52 PM, Nick Coghlan wrote:
On 15 August 2016 at 19:42, Igor Gnatenko wrote:
It can't track/change BR/R's as RPM is Turing complete and impossible to parse.
Imagine, we have pythonXdist(foo) extracted from PyPI metadata, but in
Fedora we still need to add some more BR for that,
