... reply to me self:
!!! I was wrong, sorry !!!
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines:
maybe I can provide some info's regarding dates:
https://bugzilla.redhat.com/show_bug.cgi?id=1695701#c22
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: http
On Wed, 2019-04-10 at 12:20 -0600, Chris Murphy wrote:
> On Wed, Apr 10, 2019 at 11:09 AM Chris Murphy <
> li...@colorremedies.com> wrote:
> > I think this needs a bug report against grub2. Include the blscfg
> > debug info you provided. Also include the 'set' output, which are
> > environment vari
On Wed, Apr 10, 2019 at 11:09 AM Chris Murphy wrote:
>
> I think this needs a bug report against grub2. Include the blscfg
> debug info you provided. Also include the 'set' output, which are
> environment variables for GRUB. And also all of:
>
> /etc/default/grub
> /boot/grub2/grub.cfg
> /boot/gru
On Wed, Apr 10, 2019 at 5:48 AM Berend De Schouwer
wrote:
>
> On Tue, 2019-04-09 at 23:10 -0600, Chris Murphy wrote:
> > set debug=all
> > blscfg
>
> script/lexer.c:321: token 288 text [blscfg]
> script/lexer.c:321: token 259 text [
> ]
> script/lexer.c:321: token 0 text []
> error: ../../grub-co
On Tue, 2019-04-09 at 23:10 -0600, Chris Murphy wrote:
> On Tue, Apr 9, 2019 at 1:37 AM Berend De Schouwer
> > grub.cfg did contain:
> >
> > insmod blscfg
> > blscfg
> >
> > /boot/loader/entries has 5 .conf files and a rescue.conf
> >
> > grub gave no menus.
>
> That means GRUB can't find o
On Tue, 2019-04-09 at 23:10 -0600, Chris Murphy wrote:
> On Tue, Apr 9, 2019 at 1:37 AM Berend De Schouwer
> wrote:
> > grub.cfg did contain:
> >
> > insmod blscfg
> > blscfg
> >
> > /boot/loader/entries has 5 .conf files and a rescue.conf
> >
> > grub gave no menus.
>
> That means GRUB ca
On Tue, Apr 9, 2019 at 1:37 AM Berend De Schouwer
wrote:
>
> On Mon, 2019-04-08 at 23:26 -0700, ToddAndMargo wrote:
> > Well, this time it did the updates after rebooting, buttt
> > then I got:
> >
> >Minimal BASH-link line editing is supported. For the
> >first wo
On 4/9/19 12:36 AM, Berend De Schouwer wrote:
It seems to be a BLS problem.
Thank you! I will check it out tomorrow, time permitting.
Is there a bug ticket opened on this yet?
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe sen
On Mon, 2019-04-08 at 23:26 -0700, ToddAndMargo wrote:
> On 4/8/19 6:16 PM, sixpack13 wrote:
> > some days ago I did:
> >
> > 1.
> > sudo dnf upgrade --refresh
> >
> > 2.
> > sudo dnf install dnf-plugin-system-upgrade
> >
> > 3.
> > sudo dnf system-upgrade download --refresh --releasever=30
>
On Mon, 2019-04-08 at 18:45 -0700, ToddAndMargo wrote:
> On 4/8/19 6:04 PM, Adam Williamson wrote:
> > On Mon, 2019-04-08 at 17:13 -0700, ToddAndMargo wrote:
> > > Hi All,
> > >
> > > This is what I am running to upgrade from 29 to 30 beta:
> > >
> > > # rpm --rebuilddb
> > > # rpm -Va --nofiles
On 4/9/19 9:04 AM, Adam Williamson wrote:
> On Mon, 2019-04-08 at 17:13 -0700, ToddAndMargo wrote:
>> Hi All,
>>
>> This is what I am running to upgrade from 29 to 30 beta:
>>
>> # rpm --rebuilddb
>> # rpm -Va --nofiles --nodigest
>>if anything is too new, do a
>> # dnf downgrade offen
On Mon, 2019-04-08 at 23:26 -0700, ToddAndMargo wrote:
> On 4/8/19 6:16 PM, sixpack13 wrote:
> > some days ago I did:
> >
> > 1.
> > sudo dnf upgrade --refresh
> >
> > 2.
> > sudo dnf install dnf-plugin-system-upgrade
> >
> > 3.
> > sudo dnf system-upgrade download --refresh --releasever=30 --
On 4/8/19 6:16 PM, sixpack13 wrote:
some days ago I did:
1.
sudo dnf upgrade --refresh
2.
sudo dnf install dnf-plugin-system-upgrade
3.
sudo dnf system-upgrade download --refresh --releasever=30
--setopt='module_platform_id=platform:f30' --allowerasing
- the above is ONE line with a blank
On 4/8/19 6:04 PM, Adam Williamson wrote:
On Mon, 2019-04-08 at 17:13 -0700, ToddAndMargo wrote:
Hi All,
This is what I am running to upgrade from 29 to 30 beta:
# rpm --rebuilddb
# rpm -Va --nofiles --nodigest
if anything is too new, do a
# dnf downgrade offender(s) (no proble
some days ago I did:
1.
sudo dnf upgrade --refresh
2.
sudo dnf install dnf-plugin-system-upgrade
3.
sudo dnf system-upgrade download --refresh --releasever=30
--setopt='module_platform_id=platform:f30' --allowerasing
- the above is ONE line with a blank between "=30" and "--setopt" -
On Mon, 2019-04-08 at 17:13 -0700, ToddAndMargo wrote:
> Hi All,
>
> This is what I am running to upgrade from 29 to 30 beta:
>
> # rpm --rebuilddb
> # rpm -Va --nofiles --nodigest
>if anything is too new, do a
> # dnf downgrade offender(s) (no problems found)
>
> # dnf --enablere
Hi All,
This is what I am running to upgrade from 29 to 30 beta:
# rpm --rebuilddb
# rpm -Va --nofiles --nodigest
if anything is too new, do a
# dnf downgrade offender(s) (no problems found)
# dnf --enablerepo=* update --refresh
# dnf install python3-dnf-plugin-system-upgrade
# dnf
18 matches
Mail list logo
