Re: What is "Migration-Toool" for?
Knurpht <[email protected]> Tue, 28 Jul 2026 01:49:40 +0200
| Newsgroups | gmane.linux.suse.general |
|---|---|
| Message-ID | <[email protected]> |
--nextPart3JkpJRsqQ-SJvKEZqcrnnQ Content-Type: multipart/alternative; boundary="nextPartEHwnLAXRQX-BqvzR0IKadQ"; protected-headers="v1" Content-Transfer-Encoding: 7Bit From: Knurpht <[email protected]> To: [email protected] Subject: Re: What is "Migration-Toool" for? Date: Tue, 28 Jul 2026 01:49:40 +0200 Message-ID: <[email protected]> In-Reply-To: <[email protected]> MIME-Version: 1.0 This is a multi-part message in MIME format. --nextPartEHwnLAXRQX-BqvzR0IKadQ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Op maandag 27 juli 2026 23:13:58 Midden-Europese zomertijd schreef Darryl G= regorash=20 via openSUSE Users: > Nowhere have I ever seen instructions to remove wicked and use network > manager instead. I've used the tool on dozens of migrations, and yes, wicked was replaced by= NM, but .........=20 wired did not require new settings/confirmation, wifi connections worked as= before.=20 On 7/27/26 4:13 PM, Darryl Gregorash via openSUSE Users wrote: > > I wondered about that. I'm currently running TW without NM and with=20 > Wicked -- and it works fine.=20 > I do like the fact that the new migration tool also supports:=20 > Leap =E2=86=92 Tumbleweed or Slowroll All said and done, I watched Lubo=C5=A1 develop the tool and helped testing= it. Also helped=20 diagnose the issues people had with it. That all boiled down to involvement= of non-distro=20 repos. It is pretty simple, when developing such a tool, you cannot include all th= e (currently > 8K=20 of) home:user repos for upgrading (from 15.x) to 16.x or whatever version o= f whatever=20 packages.=20 ( Things to think about: =2D Are those packages still maintained upstream? =2D Does the packager build the 15.x packages for 16.whatever? =2D + 100 more ) To create a healthy upgrade result doing so would require a very lengthy p= rocedure,=20 which would still result in a by no means tested OS.=20 A couple of years ago I began to restrict my "customers" to distro repos ( = since 15.6 even=20 Packman and videolan went out ), and ( thanks to that ) the opensuse-migra= tion-tool did=20 what it should do. And, from own testing in VMs I can tell that the upgrade= s to SR and TW=20 worked fine too.=20 @Carlos: are you aware that what you call "your method" basically is what t= he tool does?=20 And that your method will fail big time, the same way if the home:user:pack= age: $releasever is not there or has deps that are not available?=20 =2D-=20 Gertjan Lettink a.k.a. Knurpht openSUSE Mods Team openSUSE Membership Officials https://en.opensuse.org/User:Knurpht --nextPartEHwnLAXRQX-BqvzR0IKadQ Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8" <html> <head> <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8"> </head> <body><p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0= ;">Op maandag 27 juli 2026 23:13:58 Midden-Europese zomertijd schreef Darry= l Gregorash via openSUSE Users:</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">>= ; Nowhere have I ever seen instructions to remove wicked and use network</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">>= ; manager instead.</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">I'v= e used the tool on dozens of migrations, and yes, wicked was replaced by NM= , but ......... wired did not require new settings/confirmation, wifi conne= ctions worked as before. </p> <p> </p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><sp= an style=3D"color:#fcfcfc;"><span style=3D"font-family:Noto Sans;"><span st= yle=3D"background-color:#1b1e20;">On 7/27/26 4:13 PM, Darryl Gregorash via = openSUSE Users wrote:</span></span></span></p> <br /><p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0= ;"><span style=3D"color:#fcfcfc;">><br />> <span style=3D"background-= color:#1b1e20;">I wondered about that. I'm currently running TW without NM = and with=C2=A0</span></span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><sp= an style=3D"color:#fcfcfc;"><span style=3D"background-color:#1b1e20;">> = Wicked -- and it works fine. </span></span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><sp= an style=3D"color:#fcfcfc;"><span style=3D"background-color:#1b1e20;">> = I do like the fact that the new migration tool also supports: </span></span= ></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><sp= an style=3D"color:#fcfcfc;"><span style=3D"background-color:#1b1e20;">>= =C2=A0=C2=A0Leap =E2=86=92 Tumbleweed or Slowroll</p> <p> </span></span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><sp= an style=3D"color:#fcfcfc;"><span style=3D"background-color:#1b1e20;">All s= aid and done, I watched Lubo=C5=A1 develop the tool and helped testing it.&= nbsp; Also helped diagnose the issues people had with it. That all boiled d= own to involvement of non-distro repos.<br />It is pretty simple, when deve= loping such a tool, you cannot include all the (currently > 8K of) home:= user repos for upgrading (from 15.x) to 16.x or whatever version of whateve= r packages. <br />( Things to think about:<br />- Are those packages still = maintained upstream?<br />- Does the packager build the 15.x packages for 1= 6.whatever?<br />- + 100 more</span></span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><sp= an style=3D"color:#fcfcfc;"><span style=3D"background-color:#1b1e20;">)<br = /> To create a healthy upgrade result doing so would require a very le= ngthy procedure, which would still result in a by no means tested OS. </spa= n></span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">A c= ouple of years ago I began to restrict my "customers" to distro r= epos ( since 15.6 even Packman and videolan went out ), and ( thanks = to that ) the opensuse-migration-tool did what it should do. And, from own = testing in VMs I can tell that the upgrades to SR and TW worked fine too. <= /p> <p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-righ= t:0;">@Carlos: are you aware that what you call "your method" bas= ically is what the tool does? And that your method will fail big time, the = same way if the home:user:package:$releasever is not there or has deps that= are not available? </p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">-- = </p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Ger= tjan Lettink a.k.a. Knurpht</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">ope= nSUSE Mods Team</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">ope= nSUSE Membership Officials</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">htt= ps://en.opensuse.org/User:Knurpht</p> </body> </html> --nextPartEHwnLAXRQX-BqvzR0IKadQ-- --nextPart3JkpJRsqQ-SJvKEZqcrnnQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQFPBAABCAA5FiEEl2l29K1ByrFyKJqGh6Garzp7PkgFAmpn7pQbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwyAAoJEIehmq86ez5Id54IALfm2s0wHYmdmmMMPnUs u4wQliFxeM2na68qH4Y/Y78k/uazljn/2WXK1wCoDsoAapLoWq4kXZIVp1xqTC0t 1Y80/veo4dapMeddBFTjs/pvZ2SDtjdT68ylt5NHi0LYV5NL8blrx+oiL/062Wq3 l0pibm1vAnlQr/ftRkeO97mU5hD5KAl7h7pYl/ru7DIrTGq2P02r/dWKl5rsMBA1 xt6lJWhnHQ1+Jyw0KKr8meGyCgN9szXnJfQDs/9fLxKyLgVyArRTyQdU/+9yjs/R 2HtReK2NaM1BgQZc611M68k/46IEmfHX1/ptKbbOr7T3yJxUNfJaUb+zTliyVwan 2WY= =hi84 -----END PGP SIGNATURE----- --nextPart3JkpJRsqQ-SJvKEZqcrnnQ--