On 28. 02. 20 23:49, Miro Hrončok wrote:
A follow-up observation, btw: can we exclude things from
pyproject_buildrequires ? (whether that's done at the level of the
dynamic build generation process itself, or within the pyproject
macro/tool I don't care - but I couldn't find any docs indicating i
On 28. 02. 20 23:36, Adam Williamson wrote:
On Fri, 2020-02-28 at 23:06 +0100, Miro Hrončok wrote:
I assume there's an extra "not" here. On that assumption - I understand
the problem, but if you check the history of my builds in EPEL, I'm
definitely not in that group of people :P
Cool, sorry
On Fri, 2020-02-28 at 23:06 +0100, Miro Hrončok wrote:
>
> > I assume there's an extra "not" here. On that assumption - I understand
> > the problem, but if you check the history of my builds in EPEL, I'm
> > definitely not in that group of people :P
>
> Cool, sorry for that assumption, it sounde
On 28. 02. 20 22:21, Neal Gompa wrote:
On Fri, Feb 28, 2020 at 4:13 PM Adam Williamson
wrote:
On Fri, 2020-02-28 at 20:42 +0100, Miro Hrončok wrote:
* ...the Shiny New Stuff does not appear to be available on EPEL *at
all* yet - not even EPEL 8. This makes it a bit of a non-starter if you
w
On 28. 02. 20 22:12, Adam Williamson wrote:
On Fri, 2020-02-28 at 20:42 +0100, Miro Hrončok wrote:
* ...the Shiny New Stuff does not appear to be available on EPEL *at
all* yet - not even EPEL 8. This makes it a bit of a non-starter if you
want to use the same spec file bits across Fedora and
On Fri, Feb 28, 2020 at 4:13 PM Adam Williamson
wrote:
>
> On Fri, 2020-02-28 at 20:42 +0100, Miro Hrončok wrote:
> >
> > > * ...the Shiny New Stuff does not appear to be available on EPEL *at
> > > all* yet - not even EPEL 8. This makes it a bit of a non-starter if you
> > > want to use the same
On Fri, 2020-02-28 at 20:42 +0100, Miro Hrončok wrote:
>
> > * ...the Shiny New Stuff does not appear to be available on EPEL *at
> > all* yet - not even EPEL 8. This makes it a bit of a non-starter if you
> > want to use the same spec file bits across Fedora and EPEL. I realize
> > it may be impr
On 28. 02. 20 17:58, Adam Williamson wrote:
On Tue, 2020-01-14 at 01:29 +0100, Miro Hrončok wrote:
On 13. 01. 20 22:54, Adam Williamson wrote:
On Sun, 2020-01-12 at 23:24 +0100, Miro Hrončok wrote:
Please don't mention it as required or even necessarily recommended, as
it may not be. I intenti
On Tue, 2020-01-14 at 01:29 +0100, Miro Hrončok wrote:
> On 13. 01. 20 22:54, Adam Williamson wrote:
> > On Sun, 2020-01-12 at 23:24 +0100, Miro Hrončok wrote:
> > > > Please don't mention it as required or even necessarily recommended, as
> > > > it may not be. I intentionally set up my projects s
On 13. 01. 20 22:54, Adam Williamson wrote:
On Sun, 2020-01-12 at 23:24 +0100, Miro Hrončok wrote:
Please don't mention it as required or even necessarily recommended, as
it may not be. I intentionally set up my projects such that tox is
appropriate for upstream CI, not distribution package ch
On Sun, 2020-01-12 at 23:24 +0100, Miro Hrončok wrote:
>
> > Please don't mention it as required or even necessarily recommended, as
> > it may not be. I intentionally set up my projects such that tox is
> > appropriate for upstream CI, not distribution package checking, and
> > intend distributio
On 12. 01. 20 16:47, Adam Williamson wrote:
On Sun, 2020-01-12 at 10:02 +0100, Dominik 'Rathann' Mierzejewski
wrote:
On Tuesday, 07 January 2020 at 14:32, Fabio Valentini wrote:
On Tue, Jan 7, 2020 at 2:18 PM Miro Hrončok wrote:
On 07. 01. 20 14:06, Fabio Valentini wrote:
- python / pypi wor
On 12. 01. 20 10:02, Dominik 'Rathann' Mierzejewski wrote:
On Tuesday, 07 January 2020 at 14:32, Fabio Valentini wrote:
On Tue, Jan 7, 2020 at 2:18 PM Miro Hrončok wrote:
On 07. 01. 20 14:06, Fabio Valentini wrote:
- python / pypi works great for %build and %install, but until testing
with t
On Sun, 2020-01-12 at 10:02 +0100, Dominik 'Rathann' Mierzejewski
wrote:
> On Tuesday, 07 January 2020 at 14:32, Fabio Valentini wrote:
> > On Tue, Jan 7, 2020 at 2:18 PM Miro Hrončok wrote:
> > > On 07. 01. 20 14:06, Fabio Valentini wrote:
> > > > - python / pypi works great for %build and %insta
On Tuesday, 07 January 2020 at 14:32, Fabio Valentini wrote:
> On Tue, Jan 7, 2020 at 2:18 PM Miro Hrončok wrote:
> >
> > On 07. 01. 20 14:06, Fabio Valentini wrote:
> > > - python / pypi works great for %build and %install, but until testing
> > > with tox is automated in packaging macros, %check
On Tue, Jan 7, 2020 at 2:18 PM Miro Hrončok wrote:
>
> On 07. 01. 20 14:06, Fabio Valentini wrote:
> > - python / pypi works great for %build and %install, but until testing
> > with tox is automated in packaging macros, %check has to be specified
> > manually since upstream projects do different
On 07. 01. 20 14:06, Fabio Valentini wrote:
- python / pypi works great for %build and %install, but until testing
with tox is automated in packaging macros, %check has to be specified
manually since upstream projects do different things there.
generate_buildrequires also works nicely here.
See
17 matches
Mail list logo
