Ralf Corsepius:
> That's what I call superflous bureaucracy beyond reason.
No, it's merely logical.??
Yes.
If it's not available, *and* we're not aware
that it's available, it's not released.?? It's as simple as that.
It was available, it just had not formally been announced and the test
On Sat, 2019-05-04 at 00:28 +0930, Tim via users wrote:
> On 3/5/19 10:00 pm, Tom H wrote:
> > If we could accept that some people ask for help about a test release here
> > without pointing them to the etst list,
>
> I really do not see why people are so against that.?? I think it's common
> se
On 3/5/19 10:00 pm, Tom H wrote:
If we could accept that some people ask for help about a test release here
without pointing them to the etst list,
I really do not see why people are so against that.?? I think it's common
sense to let someone know they're asking the wrong people to for help i
Tim:
>> My vote is:?? Until it's officially announced AND released, it ain't
a release.
>> Even though we could all be expecting it on a prearranged date, it could
>> be deliberately delayed by circumstances.
Ralf Corsepius:
> That's what I call superflous bureaucracy beyond reason.
No, i
On Thu, May 2, 2019 at 11:06 PM Matthew Miller wrote:
> On Thu, May 02, 2019 at 08:47:29PM +0100, Patrick O'Callaghan wrote:
>>>
>>> We should unify the two lists so as not to have these delirious
>>> threads on an almost twice-yearly basis.
>>
>> I used to read the Test list as well as this one b
On Thu, May 2, 2019 at 9:48 PM Patrick O'Callaghan
wrote:
> On Thu, 2019-05-02 at 18:40 +0200, Tom H wrote:
>> On Thu, May 2, 2019 at 1:55 PM Patrick O'Callaghan
>> wrote:
>>> On Thu, 2019-05-02 at 12:35 +0200, Tom H wrote:
On Thu, May 2, 2019 at 11:46 AM Patrick O'Callaghan
wrote:
>
On 5/3/19 1:51 PM, Ralf Corsepius wrote:
> Nobody will listen nor respond.
It would be really nice to not have to read about this any longer. (He says,
with full
knowledge of the irony.)
--
Right: I dislike the default color scheme Wrong: What idiot picked the default
color scheme
___
On 5/3/19 6:51 AM, Tim via users wrote:
Allegedly, on or about 2 May 2019, Ed Greshko sent:
When is jury selection?
I imagine there must be an upcoming trial to address this travesty.
:-)
My vote is: Until it's officially announced AND released, it ain't a
release. Even though we could a
Allegedly, on or about 2 May 2019, Tom H sent:
> We should unify the two lists so as not to have these delirious
> threads on an almost twice-yearly basis.
There would be too much noise.
--
[tim@localhost ~]$ uname -rsvp
Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64
B
Allegedly, on or about 2 May 2019, Ed Greshko sent:
> When is jury selection?
>
> I imagine there must be an upcoming trial to address this travesty.
>:-)
My vote is: Until it's officially announced AND released, it ain't a
release. Even though we could all be expecting it on a prearranged
dat
Neal Becker wrote:
> Sjoerd Mullender wrote:
>
>> On 02/05/2019 08.30, Samuel Sieb wrote:
>>> On 5/1/19 9:56 AM, Sjoerd Mullender wrote:
On 01/05/2019 17.50, Neal Becker wrote:
> It's too bad you can't get a bash prompt during the upgrade so you
> could run
> ps or something. My
We could always have a policy of adding the Fedora version in the subject line.
Something like "F30: Query here"
On May 2, 2019 9:40:27 AM MST, Tom H wrote:
>On Thu, May 2, 2019 at 1:55 PM Patrick O'Callaghan
> wrote:
>> On Thu, 2019-05-02 at 12:35 +0200, Tom H wrote:
>>> On Thu, May 2, 2019 at
On Thu, May 02, 2019 at 08:47:29PM +0100, Patrick O'Callaghan wrote:
> > We should unify the two lists so as not to have these delirious
> > threads on an almost twice-yearly basis.
> I used to read the Test list as well as this one but stopped a couple
> of years ago when I realised I wasn't getti
On Thu, 2019-05-02 at 18:40 +0200, Tom H wrote:
> On Thu, May 2, 2019 at 1:55 PM Patrick O'Callaghan
> wrote:
> > On Thu, 2019-05-02 at 12:35 +0200, Tom H wrote:
> > > On Thu, May 2, 2019 at 11:46 AM Patrick O'Callaghan
> > > wrote:
> > > > I pointed out that a post relating to unreleased softwar
On Thu, May 2, 2019 at 1:55 PM Patrick O'Callaghan
wrote:
> On Thu, 2019-05-02 at 12:35 +0200, Tom H wrote:
>> On Thu, May 2, 2019 at 11:46 AM Patrick O'Callaghan
>> wrote:
>>> I pointed out that a post relating to unreleased software should
>>> go on the Test list. That is the official policy
On Thu, 2019-05-02 at 12:35 +0200, Tom H wrote:
> On Thu, May 2, 2019 at 11:46 AM Patrick O'Callaghan
> wrote:
> > I pointed out that a post relating to unreleased software should go on
> > the Test list. That is the official policy of this list.
>
> AFAIK, it's from time that this email [1] is s
On Thu, 2019-05-02 at 18:40 +0800, Ed Greshko wrote:
> When is jury selection?
>
> I imagine there must be an upcoming trial to address this travesty.
Quite.
poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to us
Sjoerd Mullender wrote:
> On 02/05/2019 08.30, Samuel Sieb wrote:
>> On 5/1/19 9:56 AM, Sjoerd Mullender wrote:
>>> On 01/05/2019 17.50, Neal Becker wrote:
It's too bad you can't get a bash prompt during the upgrade so you
could run
ps or something. My laptop doesn't have a disk ac
When is jury selection?
I imagine there must be an upcoming trial to address this travesty.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfe
On Thu, May 2, 2019 at 11:46 AM Patrick O'Callaghan
wrote:
>
> I pointed out that a post relating to unreleased software should go on
> the Test list. That is the official policy of this list.
AFAIK, it's from time that this email [1] is sent that the "users"
list is ok, not from the time that th
On Thu, 2019-05-02 at 08:49 +0200, Ralf Corsepius wrote:
> On 5/2/19 8:32 AM, Samuel Sieb wrote:
> > On 4/30/19 8:33 PM, Ralf Corsepius wrote:
> > > You redirected the OP to test@, at a point in time, when - though fc30
> > > had not been formally announced - fc30 already had been in place on
> >
On 02/05/2019 08.30, Samuel Sieb wrote:
> On 5/1/19 9:56 AM, Sjoerd Mullender wrote:
>> On 01/05/2019 17.50, Neal Becker wrote:
>>> It's too bad you can't get a bash prompt during the upgrade so you
>>> could run
>>> ps or something. My laptop doesn't have a disk activity light, so
>>> there's
>>>
On 5/2/19 8:32 AM, Samuel Sieb wrote:
On 4/30/19 8:33 PM, Ralf Corsepius wrote:
You redirected the OP to test@, at a point in time, when - though fc30
had not been formally announced - fc30 already had been in place on
the download servers.
That said, you were just behaving bureaucratic and n
On 4/30/19 8:33 PM, Ralf Corsepius wrote:
You redirected the OP to test@, at a point in time, when - though fc30
had not been formally announced - fc30 already had been in place on the
download servers.
That said, you were just behaving bureaucratic and nit-picking, IMHO.
Even though it had
On 5/1/19 9:56 AM, Sjoerd Mullender wrote:
On 01/05/2019 17.50, Neal Becker wrote:
It's too bad you can't get a bash prompt during the upgrade so you could run
ps or something. My laptop doesn't have a disk activity light, so there's
no way to tell if it's doing anything.
I've been able to go
On 01/05/2019 17.50, Neal Becker wrote:
> It's too bad you can't get a bash prompt during the upgrade so you could run
> ps or something. My laptop doesn't have a disk activity light, so there's
> no way to tell if it's doing anything.
I've been able to go to another virtual terminal by type Ct
Ulf Volmer wrote:
> On 29.04.19 15:43, Neal Becker wrote:
>> I just attempted update f29->f30 using
>> sudo dnf system-upgrade download --refresh --releasever=30
>>
>> After reboot
>> sudo dnf system-upgrade reboot
>>
>> The system got to
>> running transaction
>>
>> But then seemed to hang. I
On Tue, Apr 30, 2019 at 8:12 PM Sam Varshavchik wrote:
>
> Chris Murphy writes:
>
> > On Tue, Apr 30, 2019 at 9:53 AM Sjoerd Mullender wrote:
> > >
> > > Now that the release announcement has been done, I can say that
> > > upgrading for me (on a VM) also failed. After the final reboot, I just
>
On 4/30/19 8:25 PM, Patrick O'Callaghan wrote:
On Tue, 2019-04-30 at 18:50 +0200, Ralf Corsepius wrote:
On 4/30/19 6:40 PM, Patrick O'Callaghan wrote:
On Tue, 2019-04-30 at 17:34 +0200, Ulf Volmer wrote:
On 29.04.19 17:51, Patrick O'Callaghan wrote:
On Mon, 2019-04-29 at 09:43 -0400, Neal Bec
Chris Murphy writes:
On Tue, Apr 30, 2019 at 9:53 AM Sjoerd Mullender wrote:
>
> Now that the release announcement has been done, I can say that
> upgrading for me (on a VM) also failed. After the final reboot, I just
> got a grub prompt.
It could be this:
https://fedoraproject.org/wiki/Commo
On Tue, Apr 30, 2019 at 9:53 AM Sjoerd Mullender wrote:
>
> Now that the release announcement has been done, I can say that
> upgrading for me (on a VM) also failed. After the final reboot, I just
> got a grub prompt.
It could be this:
https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_men
On 30.04.19 21:14, Sjoerd Mullender wrote:
> On 30/04/2019 18.48, Ulf Volmer wrote:
>> Which hypervisor are you using? Is your disk visible in the grub shell?
> Earlier I had accidentally replied directly instead of to the list.
>
> To answer the question publicly, I'm using KVM. The guest is an
On 30/04/2019 18.48, Ulf Volmer wrote:
> On 30.04.19 17:53, Sjoerd Mullender wrote:
>> Now that the release announcement has been done, I can say that
>> upgrading for me (on a VM) also failed. After the final reboot, I just
>> got a grub prompt.
>
> No issues here. Two physical systems running f
On Tue, 2019-04-30 at 18:50 +0200, Ralf Corsepius wrote:
> On 4/30/19 6:40 PM, Patrick O'Callaghan wrote:
> > On Tue, 2019-04-30 at 17:34 +0200, Ulf Volmer wrote:
> > > On 29.04.19 17:51, Patrick O'Callaghan wrote:
> > > > On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
> > > > > I just attem
On 4/30/19 5:53 PM, Sjoerd Mullender wrote:
Now that the release announcement has been done, I can say that
upgrading for me (on a VM) also failed. After the final reboot, I just
got a grub prompt.
So far, the upgrade went fine on 2 out of 3 systems. On the 3rd system,
I am also stuck with a
On 4/30/19 6:40 PM, Patrick O'Callaghan wrote:
On Tue, 2019-04-30 at 17:34 +0200, Ulf Volmer wrote:
On 29.04.19 17:51, Patrick O'Callaghan wrote:
On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
I just attempted update f29->f30 using
sudo dnf system-upgrade download --refresh --releasever
On 30.04.19 18:40, Patrick O'Callaghan wrote:
> On Tue, 2019-04-30 at 17:34 +0200, Ulf Volmer wrote:
>> https://fedoramagazine.org/announcing-fedora-30/
>
> That announcement is dated today. My reply was yesterday.
My apologies.
Best regards
Ulf
___
u
On 30.04.19 17:53, Sjoerd Mullender wrote:
> Now that the release announcement has been done, I can say that
> upgrading for me (on a VM) also failed. After the final reboot, I just
> got a grub prompt.
No issues here. Two physical systems running f30 now, both using UEFI.
Which hypervisor are y
On Tue, 2019-04-30 at 17:34 +0200, Ulf Volmer wrote:
> On 29.04.19 17:51, Patrick O'Callaghan wrote:
> > On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
> > > I just attempted update f29->f30 using
> > > sudo dnf system-upgrade download --refresh --releasever=30
> >
> > F30 has not been rel
On 29.04.19 15:43, Neal Becker wrote:
> I just attempted update f29->f30 using
> sudo dnf system-upgrade download --refresh --releasever=30
>
> After reboot
> sudo dnf system-upgrade reboot
>
> The system got to
> running transaction
>
> But then seemed to hang. I waited about 15 minutes. T
Now that the release announcement has been done, I can say that
upgrading for me (on a VM) also failed. After the final reboot, I just
got a grub prompt.
On 30/04/2019 17.34, Ulf Volmer wrote:
> On 29.04.19 17:51, Patrick O'Callaghan wrote:
>> On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
On 29.04.19 17:51, Patrick O'Callaghan wrote:
> On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
>> I just attempted update f29->f30 using
>> sudo dnf system-upgrade download --refresh --releasever=30
>
> F30 has not been released yet. This should be reported on the Fedora
> Test list, not h
On Mon, 2019-04-29 at 09:43 -0400, Neal Becker wrote:
> I just attempted update f29->f30 using
> sudo dnf system-upgrade download --refresh --releasever=30
F30 has not been released yet. This should be reported on the Fedora
Test list, not here.
poc
__
43 matches
Mail list logo
