Following is the list of topics that will be discussed in the
FESCo meeting Friday at 15:00UTC in #fedora-meeting on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2019-06-07 15:00 UTC'
Links to all issues to be di
On Mon, Jun 3, 2019 at 12:24 PM Jerry James wrote:
> Noted. I will probably get all these packages built on Wednesday or
> Thursday of this week. If that turns out to be a bad time for you, please
> let me know and I will postpone the builds. Regards,
>
I got about half of the builds done. U
On Thu, Jun 6, 2019 at 3:08 PM Dennis Gilmore wrote:
>
> On Thu, Jun 6, 2019 at 7:11 AM Neal Gompa wrote:
> >
> > On Thu, Jun 6, 2019 at 7:53 AM Florian Weimer wrote:
> > >
> > > Is there a reason why we do not tag dist-git commits, using a name which
> > > is derived from the NEVR from a Koji b
On Thu, Jun 6, 2019 at 7:11 AM Neal Gompa wrote:
>
> On Thu, Jun 6, 2019 at 7:53 AM Florian Weimer wrote:
> >
> > Is there a reason why we do not tag dist-git commits, using a name which
> > is derived from the NEVR from a Koji build?
> >
> > How well does Git scale with thousands of tags?
> >
>
* Thomas Moschny:
> Am Do., 6. Juni 2019 um 14:12 Uhr schrieb Pierre-Yves Chibon
> :
>>
>> On Thu, Jun 06, 2019 at 01:52:20PM +0200, Florian Weimer wrote:
>> > Is there a reason why we do not tag dist-git commits, using a name which
>> > is derived from the NEVR from a Koji build?
>>
>> One of the
Hi,
I'd like also update opencv to 3.4.6 on stable branches but due
possible ABI breakage [1]. We might should rebuild all dependent
software . Personally I think we do not have to follow all the advice
of dist.abicheck , opencv have a lot of stuff , if one symbol is
removed , doesn't meant that
Am Do., 6. Juni 2019 um 14:12 Uhr schrieb Pierre-Yves Chibon
:
>
> On Thu, Jun 06, 2019 at 01:52:20PM +0200, Florian Weimer wrote:
> > Is there a reason why we do not tag dist-git commits, using a name which
> > is derived from the NEVR from a Koji build?
>
> One of the issue is that currently tags
On Thu, Jun 6, 2019 at 5:01 AM Miro Hrončok wrote:
>
> I remember readingsomething about podcast interviews. Are those available as
> well, or was this not implemented after all?
>
Unfortunately, we ended up not having enough time to do this. For the
next cycle, I'm going to work with x3mboy to se
On Thu, Jun 6, 2019 at 1:55 AM Igor Gnatenko
wrote:
>
> there is some misconfiguration in elections app. For FESCo elections,
> it is written "Here are the candidates for the 1 seat(s) open:" while
> there are 4 seats.
>
Fixed! This does not impact how votes are accepted or counted.
--
Ben Cotto
On Thu, Jun 6, 2019 at 7:53 AM Florian Weimer wrote:
>
> Is there a reason why we do not tag dist-git commits, using a name which
> is derived from the NEVR from a Koji build?
>
> How well does Git scale with thousands of tags?
>
We used to back in the CVS days, because we needed it for plague. K
On Thu, Jun 06, 2019 at 01:52:20PM +0200, Florian Weimer wrote:
> Is there a reason why we do not tag dist-git commits, using a name which
> is derived from the NEVR from a Koji build?
One of the issue is that currently tags are not immutable, ei packagers could
override them.
Pierre
We actually talked about this on oSC19 with Neal Gompa and Florian
Festi. And we'd need it for automation we are planning to work on...
Then I spoke to pingou and he told me that tags are easy to delete and
you need some special hook to prevent that...
I did not have time to look at it though.
On
Is there a reason why we do not tag dist-git commits, using a name which
is derived from the NEVR from a Koji build?
How well does Git scale with thousands of tags?
Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe s
On 06. 06. 19 12:55, Petr Stodulka wrote:
Hi guys,
I have one curious question about the current situation around git-remote-hg.
To put you into the context, the solution was originally part of the git
upstream itself and several years ago has been split into the own upstream [0].
After a time,
Hi guys,
I have one curious question about the current situation around git-remote-hg.
To put you into the context, the solution was originally part of the git
upstream itself and several years ago has been split into the own upstream [0].
After a time, the upstream[0] did last commit in Sep27 201
On Wed, Jun 05, 2019 at 10:48:32PM -0600, Chris Murphy wrote:
> I've filed a bug about this, but I'm not sure what else to test or add
> to demonstrate where the problem is coming from. It's some combination
> of squashfs + ext4 overhead I'm guessing, but then also the perf
> report output on the p
On Wed, 2019-06-05 at 16:38 -0600, Chris Murphy wrote:
> Jun 05 15:53:25 fmac.local kernel: random: crng init done
> Jun 05 15:53:25 fmac.local kernel: random: 7 urandom warning(s)
> missed
> due to ratelimiting
> Jun 05 15:53:25 fmac.local wpa_supplicant[1000]: random: Cannot read
> from /dev/rand
On 06. 06. 19 2:03, Ben Cotton wrote:
Voting is now open for the Fedora 30 election cycle. You can vote in
the Elections app[1]. Interviews with candidates are available on the
Fedora Community Blog[2], with links available in the Elections app.
Voting ends at 23:59 UTC on 20 June.
I remember r
18 matches
Mail list logo
