2:55 a.m.
Hello good people!
I would like to thanx to everybody for amazing work in fedora, for keeping it alive, and
updatable.
In friday I had found an old laptop running f22 and decided to try a leap update to f34.
It was not just default inntall, there was vlc and much more "unknown"
comonents.
Well, transaction failed on python stack, but no surprise here (f31 ahd
python2->python3?).
So random bisetct, leap update to f27. Needed --nogpgcheck[1]. Wou. Transaction passed.
Update passed, and system started and was alive. Although the system was behaving terribly
(there were experiemtnal patches in graphic drivers and also
gnomeshell was weird, not speaking about wayalnd), it was stable enough to make another
huge leap. F27->f31 faile dagain on pythn stack, but only because of four packages.
f27->f30 passed again. UNluckily --nogpg check was no longer transferable from download
to reboot+update. But gpgcheck=1 in active repos fixed it.[1] in and in the morning a
running shining smooth quick and super stbale system was there.
f30-> f34 died again on python stack.. (yah, dnf and freinds should stop using that or
keep embedded interpreter....)
f30->31 passed again to even more shining and more working system.
f31->f33 (yup, that was typo, but found it to late in trasnaction) passed again withot
issues.
Thanx a lot! II was never expecting such leaps would work so smoothly!
J.
[1] https was a culprint herem causing the keys impossible to downlaod. in f31, gpgcheck
could be enabled again.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
3:34 a.m.
Happy to read this :)
Congrats, man :)
I will do soon an f33 - f34 - f35 journey
Jiri Vanek a écrit :
Hello good people!
I would like to thanx to everybody for amazing work in fedora, for keeping it alive, and
updatable.
In friday I had found an old laptop running f22 and decided to try a leap update to f34.
It was not just default inntall, there was vlc and much more "unknown"
comonents.
Well, transaction failed on python stack, but no surprise here (f31 ahd
python2->python3?).
So random bisetct, leap update to f27. Needed --nogpgcheck[1]. Wou.
Transaction passed. Update passed, and system started and was alive.
Although the system was behaving terribly (there were experiemtnal patches
in graphic drivers and also gnomeshell was weird, not speaking about
wayalnd), it was stable enough to make another huge leap. F27->f31 faile
dagain on pythn stack, but only because of four packages.
f27->f30 passed again. UNluckily --nogpg check was no longer transferable from
download to reboot+update. But gpgcheck=1 in active repos fixed it.[1] in and in the
morning a running shining smooth quick and super stbale system was there.
f30-> f34 died again on python stack.. (yah, dnf and freinds should stop using that or
keep embedded interpreter....)
f30->31 passed again to even more shining and more working system.
f31->f33 (yup, that was typo, but found it to late in trasnaction) passed again withot
issues.
Thanx a lot! II was never expecting such leaps would work so smoothly!
J.
[1] https was a culprint herem causing the keys impossible to downlaod. in f31, gpgcheck
could be enabled again.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
--
GnuPG: AE157E0B29F0BEF2 at keys.openpgp.org
CA Cert: https://dl.casperlefantom.net/pub/ssl/root.der
Jabber/XMPP Messaging: casper(a)casperlefantom.net
4:44 a.m.
On Mon, 2021-10-11 at 10:34 +0200, Casper wrote:
Happy to read this :)
Congrats, man :)
I will do soon an f33 - f34 - f35 journey
F33 -> F35 should work (update) directly
Jiri Vanek a écrit :
> Hello good people!
>
> I would like to thanx to everybody for amazing work in fedora, for
> keeping it alive, and updatable.
>
> In friday I had found an old laptop running f22 and decided to try
> a leap update to f34. It was not just default inntall, there was
> vlc and much more "unknown" comonents.
> Well, transaction failed on python stack, but no surprise here (f31
> ahd python2->python3?).
> So random bisetct, leap update to f27. Needed --nogpgcheck[1]. Wou.
> Transaction passed. Update passed, and system started and was
> alive.
> Although the system was behaving terribly (there were experiemtnal
> patches
> in graphic drivers and also gnomeshell was weird, not speaking
> about
> wayalnd), it was stable enough to make another huge leap. F27->f31
> faile
> dagain on pythn stack, but only because of four packages.
> f27->f30 passed again. UNluckily --nogpg check was no longer
> transferable from download to reboot+update. But gpgcheck=1 in
> active repos fixed it.[1] in and in the morning a running shining
> smooth quick and super stbale system was there.
> f30-> f34 died again on python stack.. (yah, dnf and freinds should
> stop using that or keep embedded interpreter....)
> f30->31 passed again to even more shining and more working system.
> f31->f33 (yup, that was typo, but found it to late in trasnaction)
> passed again withot issues.
>
> Thanx a lot! II was never expecting such leaps would work so
> smoothly!
>
> J.
>
>
> [1] https was a culprint herem causing the keys impossible to
> downlaod. in f31, gpgcheck could be enabled again.
> --
> Jiri Vanek Mgr.
> Principal QA Software Engineer
> Red Hat Inc.
> +420 775 39 01 09
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Sérgio M. B.
7:18 a.m.
On 10/11/21 12:28, Petr Pisar wrote:
V Mon, Oct 11, 2021 at 09:55:05AM +0200, Jiri Vanek napsal(a):
> f30-> f34 died again on python stack.. (yah, dnf and freinds should stop
> using that or keep embedded interpreter....)
DNF 5 is going be written in C++ without any Python.
with all its pros and cons :)
-- Petr
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
7:48 a.m.
Nice. I did an update from F26-F33 last year doing one version at time
instead of jumping more than one version... and had no major issues. I
wonder how far back its possible to start from and walk through the version
updates.
On Mon, Oct 11, 2021 at 3:55 AM Jiri Vanek <jvanek(a)redhat.com> wrote:
Hello good people!
I would like to thanx to everybody for amazing work in fedora, for keeping
it alive, and updatable.
In friday I had found an old laptop running f22 and decided to try a leap
update to f34. It was not just default inntall, there was vlc and much
more "unknown" comonents.
Well, transaction failed on python stack, but no surprise here (f31 ahd
python2->python3?).
So random bisetct, leap update to f27. Needed --nogpgcheck[1]. Wou.
Transaction passed. Update passed, and system started and was alive.
Although the system was behaving terribly (there were experiemtnal patches
in graphic drivers and also
gnomeshell was weird, not speaking about wayalnd), it was stable enough to
make another huge leap. F27->f31 faile dagain on pythn stack, but only
because of four packages.
f27->f30 passed again. UNluckily --nogpg check was no longer transferable
from download to reboot+update. But gpgcheck=1 in active repos fixed it.[1]
in and in the morning a running shining smooth quick and super stbale
system was there.
f30-> f34 died again on python stack.. (yah, dnf and freinds should stop
using that or keep embedded interpreter....)
f30->31 passed again to even more shining and more working system.
f31->f33 (yup, that was typo, but found it to late in trasnaction) passed
again withot issues.
Thanx a lot! II was never expecting such leaps would work so smoothly!
J.
[1] https was a culprint herem causing the keys impossible to downlaod. in
f31, gpgcheck could be enabled again.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
8:24 a.m.
On 11/10/2021 13:48, JT wrote:
Nice. I did an update from F26-F33 last year doing one version at
time
instead of jumping more than one version... and had no major issues. I
wonder how far back its possible to start from and walk through the
version updates.
I recently did F15-F34 though I did do it two versions at a time
for the most part.
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
8:32 a.m.
I think if you jump more than 2 versions at a time the packages obsoleted
by fedora-obsolete-packages might not be picked up properly because it only
holds packages for about 2 versions before they are removed from it. So
jumping from F26 to F33 directly might miss the obsoletes from F27-F31ish.
-Ian
On Mon, Oct 11, 2021 at 1:49 PM JT <jt(a)obs-sec.com> wrote:
Nice. I did an update from F26-F33 last year doing one version at
time
instead of jumping more than one version... and had no major issues. I
wonder how far back its possible to start from and walk through the version
updates.
On Mon, Oct 11, 2021 at 3:55 AM Jiri Vanek <jvanek(a)redhat.com> wrote:
> Hello good people!
>
> I would like to thanx to everybody for amazing work in fedora, for
> keeping it alive, and updatable.
>
> In friday I had found an old laptop running f22 and decided to try a leap
> update to f34. It was not just default inntall, there was vlc and much
> more "unknown" comonents.
> Well, transaction failed on python stack, but no surprise here (f31 ahd
> python2->python3?).
> So random bisetct, leap update to f27. Needed --nogpgcheck[1]. Wou.
> Transaction passed. Update passed, and system started and was alive.
> Although the system was behaving terribly (there were experiemtnal patches
> in graphic drivers and also
> gnomeshell was weird, not speaking about wayalnd), it was stable enough
> to make another huge leap. F27->f31 faile dagain on pythn stack, but only
> because of four packages.
> f27->f30 passed again. UNluckily --nogpg check was no longer transferable
> from download to reboot+update. But gpgcheck=1 in active repos fixed it.[1]
> in and in the morning a running shining smooth quick and super stbale
> system was there.
> f30-> f34 died again on python stack.. (yah, dnf and freinds should stop
> using that or keep embedded interpreter....)
> f30->31 passed again to even more shining and more working system.
> f31->f33 (yup, that was typo, but found it to late in trasnaction) passed
> again withot issues.
>
> Thanx a lot! II was never expecting such leaps would work so smoothly!
>
> J.
>
>
> [1] https was a culprint herem causing the keys impossible to downlaod.
> in f31, gpgcheck could be enabled again.
> --
> Jiri Vanek Mgr.
> Principal QA Software Engineer
> Red Hat Inc.
> +420 775 39 01 09
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
8:11 a.m.
You are right. I'm supper wondering it did as great job :)
On 10/11/21 15:32, Ian McInerney via devel wrote:
I think if you jump more than 2 versions at a time the packages
obsoleted by fedora-obsolete-packages might not be picked up properly because it only
holds packages for about 2 versions before they are removed from it. So jumping from F26
to F33 directly might miss the obsoletes from F27-F31ish.
-Ian
On Mon, Oct 11, 2021 at 1:49 PM JT <jt(a)obs-sec.com <mailto:jt@obs-sec.com>>
wrote:
Nice. I did an update from F26-F33 last year doing one version at time instead of
jumping more than one version... and had no major issues. I wonder how far back its
possible to start from and walk through the version updates.
On Mon, Oct 11, 2021 at 3:55 AM Jiri Vanek <jvanek(a)redhat.com
<mailto:jvanek@redhat.com>> wrote:
Hello good people!
I would like to thanx to everybody for amazing work in fedora, for keeping it
alive, and updatable.
In friday I had found an old laptop running f22 and decided to try a leap update
to f34. It was not just default inntall, there was vlc and much more "unknown"
comonents.
Well, transaction failed on python stack, but no surprise here (f31 ahd
python2->python3?).
So random bisetct, leap update to f27. Needed --nogpgcheck[1]. Wou. Transaction
passed. Update passed, and system started and was alive. Although the system was behaving
terribly (there were experiemtnal patches in graphic drivers
and also
gnomeshell was weird, not speaking about wayalnd), it was stable enough to make
another huge leap. F27->f31 faile dagain on pythn stack, but only because of four
packages.
f27->f30 passed again. UNluckily --nogpg check was no longer transferable from
download to reboot+update. But gpgcheck=1 in active repos fixed it.[1] in and in the
morning a running shining smooth quick and super stbale system was
there.
f30-> f34 died again on python stack.. (yah, dnf and freinds should stop using
that or keep embedded interpreter....)
f30->31 passed again to even more shining and more working system.
f31->f33 (yup, that was typo, but found it to late in trasnaction) passed
again withot issues.
Thanx a lot! II was never expecting such leaps would work so smoothly!
J.
[1] https was a culprint herem causing the keys impossible to downlaod. in f31,
gpgcheck could be enabled again.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
<mailto:devel@lists.fedoraproject.org>
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
<mailto:devel-leave@lists.fedoraproject.org>
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
<https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
<https://fedoraproject.org/wiki/Mailing_list_guidelines>
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
<https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure <https://pagure.io/fedora-infrastructure>
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
<mailto:devel@lists.fedoraproject.org>
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
<mailto:devel-leave@lists.fedoraproject.org>
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
<https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
<https://fedoraproject.org/wiki/Mailing_list_guidelines>
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
<https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
<https://pagure.io/fedora-infrastructure>
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
928
days inactive
929
days old
8 comments
7 participants
participants (7)
-
Casper -
Ian McInerney -
Jiri Vanek -
JT -
Petr Pisar -
Sérgio Basto -
Tom Hughes