El vie, 14-12-2018 a las 20:33 +0100, Igor Gnatenko escribió:
> Hello folks,
>
> for long time we have problem if you have some arch-specific
> BuildRequires, you still get one src.rpm from one of arches (not sure
> how koji chooses that one) which might not work for your
> architecture.
>
> For
On 12/14/18 10:20 PM, Neal Gompa wrote:
On Fri, Dec 14, 2018 at 3:09 PM Igor Gnatenko
wrote:
That makes sense that we can do something like this from DNF code..
However, it would be kinda hard to do any dependency resolution
checks..
Although we already have one which is module(platform:$PLAT
On 12/14/18 12:33 PM, Igor Gnatenko wrote:
Hello folks,
for long time we have problem if you have some arch-specific
BuildRequires, you still get one src.rpm from one of arches (not sure
how koji chooses that one) which might not work for your architecture.
For example if you have following in
On Friday, December 14, 2018 2:33:36 PM EST Igor Gnatenko wrote:
> Hello folks,
>
> for long time we have problem if you have some arch-specific
> BuildRequires, you still get one src.rpm from one of arches (not sure
> how koji chooses that one) which might not work for your architecture.
>
> For
On 14. 12. 18 22:38, Kevin Fenzi wrote:
On 12/14/18 11:33 AM, Igor Gnatenko wrote:
Hello folks,
for long time we have problem if you have some arch-specific
BuildRequires, you still get one src.rpm from one of arches (not sure
how koji chooses that one) which might not work for your architectur
On 12/14/18 11:33 AM, Igor Gnatenko wrote:
> Hello folks,
>
> for long time we have problem if you have some arch-specific
> BuildRequires, you still get one src.rpm from one of arches (not sure
> how koji chooses that one) which might not work for your architecture.
>
> For example if you have f
Le ven. 14 déc. 2018 à 20:34, Igor Gnatenko
a écrit :
>
> Hello folks,
>
> for long time we have problem if you have some arch-specific
> BuildRequires, you still get one src.rpm from one of arches (not sure
> how koji chooses that one) which might not work for your architecture.
>
> For example i
On Fri, Dec 14, 2018 at 3:09 PM Igor Gnatenko
wrote:
>
> That makes sense that we can do something like this from DNF code..
> However, it would be kinda hard to do any dependency resolution
> checks..
>
> Although we already have one which is module(platform:$PLATFORM_ID)
> which is automatically
That makes sense that we can do something like this from DNF code..
However, it would be kinda hard to do any dependency resolution
checks..
Although we already have one which is module(platform:$PLATFORM_ID)
which is automatically populated from os-release by libdnf. Which is
actually causing pro
On Fri, Dec 14, 2018 at 2:50 PM Igor Gnatenko
wrote:
>
> On Fri, Dec 14, 2018 at 8:45 PM Neal Gompa wrote:
> >
> > On Fri, Dec 14, 2018 at 2:34 PM Igor Gnatenko
> > wrote:
> > >
> > > Hello folks,
> > >
> > > for long time we have problem if you have some arch-specific
> > > BuildRequires, you s
On Fri, Dec 14, 2018 at 8:45 PM Neal Gompa wrote:
>
> On Fri, Dec 14, 2018 at 2:34 PM Igor Gnatenko
> wrote:
> >
> > Hello folks,
> >
> > for long time we have problem if you have some arch-specific
> > BuildRequires, you still get one src.rpm from one of arches (not sure
> > how koji chooses tha
On Fri, Dec 14, 2018 at 2:34 PM Igor Gnatenko
wrote:
>
> Hello folks,
>
> for long time we have problem if you have some arch-specific
> BuildRequires, you still get one src.rpm from one of arches (not sure
> how koji chooses that one) which might not work for your architecture.
>
> For example if
Hello folks,
for long time we have problem if you have some arch-specific
BuildRequires, you still get one src.rpm from one of arches (not sure
how koji chooses that one) which might not work for your architecture.
For example if you have following in spec:
%ifarch %{ldc_arches}
BuildRequires: ld
13 matches
Mail list logo
