On Sat, Aug 31, 2019 at 7:04 PM John Harris wrote:
>
> On Friday, August 30, 2019 5:16:25 AM MST Nico Kadel-Garcia wrote:
> > > On Aug 29, 2019, at 9:41 PM, John Harris wrote:
> > >
> > >
> > >> On Thursday, August 29, 2019 8:12:22 AM MST Dan Book wrote:
> > >> I would agree, but people do instal
On Friday, August 30, 2019 5:40:22 AM MST Gerald B. Cox wrote:
> You just explained exactly why it was different ;-)
I'm sorry if you believe that to be the case, but it is not. I explained that
you can mute on both platforms, if you choose to do so.
--
John M. Harris, Jr.
Splentity
https
On Friday, August 30, 2019 5:16:25 AM MST Nico Kadel-Garcia wrote:
> > On Aug 29, 2019, at 9:41 PM, John Harris wrote:
> >
> >
> >> On Thursday, August 29, 2019 8:12:22 AM MST Dan Book wrote:
> >> I would agree, but people do install multiple desktops after installing
> >> a
> >> spin. Such a us
On Friday, August 30, 2019 12:35:34 PM MST mcatanz...@gnome.org wrote:
> On Wed, Aug 28, 2019 at 7:46 PM, Christopher
> wrote:
>
> > Yeah, I also don't want a complicated installer. I just don't see this
> > disagreement going anywhere without some sort of compromise, and I
> > can't think of an
On Friday, August 30, 2019 4:33:11 AM MST Björn Persson wrote:
> John Harris wrote:
> > Thing is, binding a port and expecting it to be open to every network
> > interface you've got are two very different things.
>
> Once again John Harris is completely wrong. The bind system call is
> precisely
On 8/31/19 11:49 AM, Miro Hrončok wrote:
On 31. 08. 19 20:38, Kevin Fenzi wrote:
Which way are you doing the upgrade? just a distro-sync?
Yes:
$ sudo dnf --releasever=31 --setopt=module_platform_id=platform:f31
--enablerepo=updates-testing distro-sync
To be clear, I'm not yet doing the upd
On 22. 08. 19 15:15, Honza Horak wrote:
Cassandra has been originally packaged by folks in our team, in the time we had
some stakes there. Since then, priorities changed and also people involved are
not in our team any more. We tried to keep it packaged in Fedora with reasonable
effort, but tur
On Sat, Aug 31, 2019 at 8:45 PM Kevin Fenzi wrote:
> So, we are moving it one minute earlier? If it's listed as tuesday on
> the schedule it should be 23:59 on tuesday at least. :)
>
> I would still like a bit earlier so releng folks don't need to work at
> night. Perhaps 20UTC could be a ok comp
On Sat, Aug 31, 2019 at 8:45 PM Kevin Fenzi wrote:
> On 8/31/19 1:52 AM, Kalev Lember wrote:
> > On Sat, Aug 31, 2019, 10:46 Zbigniew Jędrzejewski-Szmek <
> zbys...@in.waw.pl>
> > wrote:
> >
> >> On Sat, Aug 31, 2019 at 10:22:32AM +0200, Kevin Kofler wrote:
> >>> Chris Murphy wrote:
> 2400 i
On 31. 08. 19 20:38, Kevin Fenzi wrote:
On 8/30/19 1:18 PM, Miro Hrončok wrote:
On 30. 08. 19 18:25, Adam Williamson wrote:
Not. If you're getting it on an installed system that you're upgrading,
you probably need to manually switch the libgit2 module from the 0.27
stream to the 0.28 stream, th
On 8/31/19 1:52 AM, Kalev Lember wrote:
> On Sat, Aug 31, 2019, 10:46 Zbigniew Jędrzejewski-Szmek
> wrote:
>
>> On Sat, Aug 31, 2019 at 10:22:32AM +0200, Kevin Kofler wrote:
>>> Chris Murphy wrote:
2400 is totally confusing, I'm only finding it used in military
contexts and even there i
On 8/30/19 1:18 PM, Miro Hrončok wrote:
> On 30. 08. 19 18:25, Adam Williamson wrote:
>> Not. If you're getting it on an installed system that you're upgrading,
>> you probably need to manually switch the libgit2 module from the 0.27
>> stream to the 0.28 stream, that should clear it up.
>
> I'm h
OLD: Fedora-31-20190829.n.0
NEW: Fedora-31-20190831.n.0
= SUMMARY =
Added images:3
Dropped images: 1
Added packages: 2
Dropped packages:5
Upgraded packages: 7
Downgraded packages: 0
Size of added packages: 949.00 KiB
Size of dropped packages:26.63 MiB
No missing expected images.
Failed openQA tests: 14/142 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora-31-20190829.n.0):
ID: 439268 Test: x86_64 Server-dvd-iso install_repository_hd_variation
URL: https://openqa.fedoraproject.org/tests/439268
ID: 439321 Test: x86_64 K
Announcing the creation of a new nightly release validation test event
for Fedora 31 Branched 20190831.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
OLD: Fedora-Rawhide-20190830.n.0
NEW: Fedora-Rawhide-20190831.n.0
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 8
Dropped packages:6
Upgraded packages: 102
Downgraded packages: 0
Size of added packages: 2.46 MiB
Size of dropped packages
No missing expected images.
Compose FAILS proposed Rawhide gating check!
10 of 45 required tests failed, 6 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Unsatisfied gating requirements that could not be mapped to openQA tests:
FAILED: compose.cl
On Sat, Aug 31, 2019, 10:46 Zbigniew Jędrzejewski-Szmek
wrote:
> On Sat, Aug 31, 2019 at 10:22:32AM +0200, Kevin Kofler wrote:
> > Chris Murphy wrote:
> > > 2400 is totally confusing, I'm only finding it used in military
> > > contexts and even there it seems to be vernacular. I'd rather be
> > >
On Sat, Aug 31, 2019 at 10:22:32AM +0200, Kevin Kofler wrote:
> Chris Murphy wrote:
> > 2400 is totally confusing, I'm only finding it used in military
> > contexts and even there it seems to be vernacular. I'd rather be
> > surprised if military police use it.
>
> Then just write 23:59 instead.
On Fri, 30 Aug 2019 11:19:37 -0700
Kevin Fenzi wrote:
> On 8/28/19 2:13 PM, Peter Lemenkov wrote:
> > Hello All,
> >
> > I've just got hit by this again - lockups on s390. Looks like I have
> > 100% reproducer (just try to build Erlang and it will stuck
> > eventually).
> >
> > * https://koji.f
Chris Murphy wrote:
> 2400 is totally confusing, I'm only finding it used in military
> contexts and even there it seems to be vernacular. I'd rather be
> surprised if military police use it.
Then just write 23:59 instead.
> My suggestion would be, without respect to preference, 0015 UTC, 0030
>
21 matches
Mail list logo
