Hello all,
Fedora 36 mass rebuild is done and FTBFS tickets [0] are filed. Some
of the tickets that got filed for ppc64le failures might have been
fixed in the recent resubmission of the failed tasks. If you notice
any of those tickets, please verify if it is fixed and if it is fixed,
you can just
Seems like rebuilds is done? got like 2000 package updates today
On Thu, Jan 27, 2022 at 3:37 PM Michael Schwendt
wrote:
> On Thu, 27 Jan 2022 15:06:31 +0100, František Šumšal wrote:
>
> > I've indeed noticed the other warnings. However, given this mass rebuild
> was
> > done with a new snapshot
On Thu, 27 Jan 2022 15:06:31 +0100, František Šumšal wrote:
> I've indeed noticed the other warnings. However, given this mass rebuild was
> done with a new snapshot of gcc-12, the error is probably related to that,
> that's why I pointed out the most severe issue (since it's an error, not
> a war
On 1/27/22 14:58, Michael Schwendt wrote:
On Thu, 27 Jan 2022 14:01:40 +0100, František Šumšal wrote:
Looks like the culprit is:
You may have noticed that there are many more compiler errors in the build.log,
but it seems you've missed that the src.rpm builds fine for all other archs.
What gi
On Thu, 27 Jan 2022 14:01:40 +0100, František Šumšal wrote:
> Looks like the culprit is:
You may have noticed that there are many more compiler errors in the build.log,
but it seems you've missed that the src.rpm builds fine for all other archs.
What gives?
___
On Thu, Jan 27, 2022 at 02:01:40PM +0100, František Šumšal wrote:
> Looks like the culprit is:
>
> In file included from common/mptPathString.cpp:13:
> ./src/mpt/uuid/uuid.hpp: In constructor 'constexpr
> mpt::mpt_libopenmpt::UUID::UUID()':
> ./src/mpt/uuid/uuid.hpp:195:17: error: 'goto' is not a
Looks like the culprit is:
In file included from common/mptPathString.cpp:13:
./src/mpt/uuid/uuid.hpp: In constructor 'constexpr
mpt::mpt_libopenmpt::UUID::UUID()':
./src/mpt/uuid/uuid.hpp:195:17: error: 'goto' is not a constant expression
195 | return;
|
On Tue, 25 Jan 2022 10:04:32 -0800, Kevin Fenzi wrote:
> After that we will be done and it will be on maintainers to sort out
> FTBFS issues.
What's up with the armv7hl arch being _the only one_ (!) that failed?
https://koji.fedoraproject.org/koji/taskinfo?taskID=81787304
___
On Tue, Jan 25, 2022 at 08:39:31PM +0100, Iñaki Ucar wrote:
> On Tue, 25 Jan 2022 at 19:13, Kevin Fenzi wrote:
> >
> > Greetings.
> >
> > The mass rebuild finished it's first pass on saturday morning, leaving
> > 3448 failed builds.
> >
> > We then did a second pass yesterday ( 2022-01-24 ) of all
On Tue, 25 Jan 2022 at 19:13, Kevin Fenzi wrote:
>
> Greetings.
>
> The mass rebuild finished it's first pass on saturday morning, leaving
> 3448 failed builds.
>
> We then did a second pass yesterday ( 2022-01-24 ) of all failed builds,
> and that resulted in 1282 failed builds.
>
> The f36-rebui
Greetings.
The mass rebuild finished it's first pass on saturday morning, leaving
3448 failed builds.
We then did a second pass yesterday ( 2022-01-24 ) of all failed builds,
and that resulted in 1282 failed builds.
The f36-rebuild tag is being merged now, but unfortunately our SOP had
it merg
11 matches
Mail list logo
