El dom, 22-10-2017 a las 11:39 -0400, Randy Barlow escribió:
> On 10/22/2017 09:04 AM, Dennis Gilmore wrote:
> > updates does not have composes it has mashes, the behaviour is
> > expected
> > to be different, the problem boils down to the fact that if a
> > package
> > is made multilib
On 10/22/2017 09:04 AM, Dennis Gilmore wrote:
> updates does not have composes it has mashes, the behaviour is expected
> to be different, the problem boils down to the fact that if a package
> is made multilib indirectly, i.e. it is only pulled in because some
> external package that is multilib
El jue, 19-10-2017 a las 19:29 +0200, Florian Weimer escribió:
> On 10/19/2017 06:42 PM, Dennis Gilmore wrote:
>
> > There is long standing 8+ year old bugs we have never gotten around
> > to
> > to ensure multilib is correct in all cases. It is unfortuantly
> > expected
> > sometimes, it
On 10/19/2017 06:42 PM, Dennis Gilmore wrote:
There is long standing 8+ year old bugs we have never gotten around to
to ensure multilib is correct in all cases. It is unfortuantly expected
sometimes, it probably has happened a lot over the yearsm, but since
defaulting to turning off installing
El lun, 16-10-2017 a las 18:06 +0200, Florian Weimer escribió:
> Are there currently bugs in composes for x86-64 for F26/F27? We had
> one
> case for F27 where the compose was demonstrably broken because it
> lacked
> a required multilib:
>
>https://pagure.io/releng/issue/7071
>
> We
Are there currently bugs in composes for x86-64 for F26/F27? We had one
case for F27 where the compose was demonstrably broken because it lacked
a required multilib:
https://pagure.io/releng/issue/7071
We received a report on an issue which looks similar, this time on F26:
