Am Donnerstag, den 14.02.2019, 14:41 +0100 schrieb Fabio Valentini:
> On Thu, Feb 14, 2019 at 2:29 PM Miro Hrončok
> wrote:
> > On 04. 02. 19 21:48, Mohan Boddu wrote:
> > > Hi all,
> > >
> > > Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora
> > > 30
> > > on Jan 31st 2019. We
On Thu, Feb 14, 2019 at 2:29 PM Miro Hrončok wrote:
>
> On 04. 02. 19 21:48, Mohan Boddu wrote:
> > Hi all,
> >
> > Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
> > on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the changes
> > listed in:
> >
> > https://pagure
On 04. 02. 19 21:48, Mohan Boddu wrote:
Hi all,
Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the changes listed in:
https://pagure.io/releng/issue/8086
Mass rebuild was done in a side tag (f30-rebuild) and are n
Anderson, Charles R wrote:
> On Mon, Feb 04, 2019 at 03:48:59PM -0500, Mohan Boddu wrote:
>> Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
>> on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the changes
>> listed in:
>>
>> https://pagure.io/releng/issue/8086
>>
>
On Wednesday, 06 February 2019 at 20:37, Kevin Fenzi wrote:
> On 2/6/19 9:07 AM, Vít Ondruch wrote:
> > Dne 06. 02. 19 v 17:58 Kevin Fenzi napsal(a):
[...]
> >> Our autosigning machine seems to have a failed tpm in it, which has
> >> caused signing to fail to work. ;(
> >>
> >> We are working on ge
On 2/6/19 11:49 AM, Chris Murphy wrote:
> On Wed, Feb 6, 2019 at 9:59 AM Kevin Fenzi wrote:
>>
>> On 2/6/19 7:23 AM, Vít Ondruch wrote:
>>>
>>> Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
On 2/5/19 3:50 AM, Peter Robinson wrote:
>> There seems to be an issue with moving builds over. Eve
On Wed, Feb 6, 2019 at 9:59 AM Kevin Fenzi wrote:
>
> On 2/6/19 7:23 AM, Vít Ondruch wrote:
> >
> > Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
> >> On 2/5/19 3:50 AM, Peter Robinson wrote:
> There seems to be an issue with moving builds over. Everything seems to
> be stuck in f30-pen
On 2/6/19 9:07 AM, Vít Ondruch wrote:
>
> Dne 06. 02. 19 v 17:58 Kevin Fenzi napsal(a):
>> On 2/6/19 7:23 AM, Vít Ondruch wrote:
>>> Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
On 2/5/19 3:50 AM, Peter Robinson wrote:
>> There seems to be an issue with moving builds over. Everything see
On Wed, 2019-02-06 at 08:58 -0800, Kevin Fenzi wrote:
> This is really a anoying time for hardware to die, but of course
> sometimes it seems like it _knows_ when that is so it can fail.
This is the beginning of the rise of the machines.
signature.asc
Description: This is a digitally signed mess
On Wed, 6 Feb 2019 at 11:15, Vít Ondruch wrote:
>
>
> Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
>
> On 2/5/19 3:50 AM, Peter Robinson wrote:
>
> There seems to be an issue with moving builds over. Everything seems to be
> stuck in f30-pending and not getting tagged with f30.
>
> That'll be th
Dne 06. 02. 19 v 17:58 Kevin Fenzi napsal(a):
> On 2/6/19 7:23 AM, Vít Ondruch wrote:
>> Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
>>> On 2/5/19 3:50 AM, Peter Robinson wrote:
> There seems to be an issue with moving builds over. Everything seems to
> be stuck in f30-pending and not g
On 2/6/19 7:23 AM, Vít Ondruch wrote:
>
> Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
>> On 2/5/19 3:50 AM, Peter Robinson wrote:
There seems to be an issue with moving builds over. Everything seems to be
stuck in f30-pending and not getting tagged with f30.
>>> That'll be the signing
Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
> On 2/5/19 3:50 AM, Peter Robinson wrote:
>>> There seems to be an issue with moving builds over. Everything seems to be
>>> stuck in f30-pending and not getting tagged with f30.
>> That'll be the signing queue
> Yeah, it wasn't processing these corr
On 2/6/19 02:27, Kevin Fenzi wrote:
On 2/5/19 3:36 PM, Kalev Lember wrote:
Is there any chance releng could figure out the list of packages
affected once the signing/tagging is finished and fix all of them? I can
already tell that it's affecting at least 40-50 GNOME builds done in
that time fram
On 2/5/19 3:36 PM, Kalev Lember wrote:
>
> On 2/5/19 21:19, Kevin Fenzi wrote:
>> Yes, thats a danger... we will have to retag those on a case by case
>> basis. The script releng uses to merge side tags won't merge a build if
>> there is a newer one, so those should be fine, it's just if the mass
On 2/5/19 21:19, Kevin Fenzi wrote:
Yes, thats a danger... we will have to retag those on a case by case
basis. The script releng uses to merge side tags won't merge a build if
there is a newer one, so those should be fine, it's just if the mass
rebuild build was added and then also someone did
On Tue, 2019-02-05 at 12:06 +, Anderson, Charles R wrote:
> On Mon, Feb 04, 2019 at 03:48:59PM -0500, Mohan Boddu wrote:
> > Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora
> > 30
> > on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the
> > changes
> > listed in:
> >
On 2/5/19 3:50 AM, Peter Robinson wrote:
>> There seems to be an issue with moving builds over. Everything seems to be
>> stuck in f30-pending and not getting tagged with f30.
>
> That'll be the signing queue
Yeah, it wasn't processing these correctly I'm afraid.
I did add the mass rebuild side
On Mon, Feb 04, 2019 at 03:48:59PM -0500, Mohan Boddu wrote:
> Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
> on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the changes
> listed in:
>
> https://pagure.io/releng/issue/8086
>
> Mass rebuild was done in a side tag
> There seems to be an issue with moving builds over. Everything seems to be
> stuck in f30-pending and not getting tagged with f30.
That'll be the signing queue
> I'm also concerned that once the signing queue starts moving, it's going to
> tag older packages over the new builds that have happ
No. If count as many times as many maintainers it has it will be about
3300 fails.
вт, 5 февр. 2019 г. в 14:32, Vít Ondruch :
>
>
> Dne 04. 02. 19 v 21:48 Mohan Boddu napsal(a):
>
> Hi all,
>
> Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
> on Jan 31st 2019. We did a mass
Dne 04. 02. 19 v 21:48 Mohan Boddu napsal(a):
> Hi all,
>
> Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
> on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the changes
> listed in:
>
> https://pagure.io/releng/issue/8086
>
> Mass rebuild was done in a side tag (f3
There seems to be an issue with moving builds over. Everything seems to be stuck in f30-pending and not getting tagged with f30. I'm also concerned that once the signing queue starts moving, it's going to tag older packages over the new builds that have happened in the mean time. Pete 05.02.2019,
Hi all,
Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the changes
listed in:
https://pagure.io/releng/issue/8086
Mass rebuild was done in a side tag (f30-rebuild) and are now getting moved
over to f30.
Failures ca
Hi all,
Fedora 30 Mass Rebuild will start in few minutes. We are preparing for the
final steps and will run mass rebuild once everything is in place.
On Wed, Jan 30, 2019 at 4:02 AM Mohan Boddu wrote:
> Hi all,
>
> Per the Fedora 30 schedule[1] we are supposed to start the mass reb
Hi all,
Per the Fedora 30 schedule[1] we are supposed to start the mass rebuild on
Jan 30th 2019, but due to known bug with gcc it got pushed by a day and
will start on Jan 31st 2019[2]. We are doing a mass rebuild for Fedora 30 for
all the changes listed in
https://pagure.io/releng/issue/8086
T
26 matches
Mail list logo
