1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL

  • What to do with merged /usr and dpkg-fsys-usrunmess

    From Krzysztof Sobiecki@21:1/5 to All on Wed Apr 6 12:10:01 2022
    Hi,
    I saw warning and it advised me to use dpkg-fsys-usrunmess:
    But now I see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008486
    And even without that there are problems with that tool: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991218 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991192 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008316 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008478

    Now what I'm supposed to do? Wait for dpkg-fsys-usrunmess-unmess?
    Is my system broken because I have used dpkg-fsys-usrunmess(that dpkg
    advised me to do?).
    As a Debian user I'm confused and a bit angry.

    What is way forward?

    Thanks
    Krzysztof Sobiecki

    <div dir="ltr"><div>Hi,</div><div>
    I saw warning and it advised me to use dpkg-fsys-usrunmess:<br>
    But now I see: <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008486">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008486</a><br>
    And even without that there are problems with that tool:<br>
    <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991218">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991218</a><br>
    <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991192">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991192</a><br>
    <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008316">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008316</a><br>
    <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008478">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008478</a><br>

    Now what I&#39;m supposed to do? Wait for dpkg-fsys-usrunmess-unmess?<br>
    Is my system broken because I have used dpkg-fsys-usrunmess(that dpkg advised me to do?).<br>
    As a Debian user I&#39;m confused and a bit angry. <br></p><p>What is way forward?<br><br></p>

    </div><div>Thanks</div><div>Krzysztof Sobiecki<br></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam Borowski@21:1/5 to Krzysztof Sobiecki on Wed Apr 6 13:10:01 2022
    On Wed, Apr 06, 2022 at 12:03:55PM +0200, Krzysztof Sobiecki wrote:
    Hi,
    I saw warning and it advised me to use dpkg-fsys-usrunmess:
    But now I see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008486
    And even without that there are problems with that tool: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991218 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991192 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008316 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008478

    Now what I'm supposed to do? Wait for dpkg-fsys-usrunmess-unmess?
    Is my system broken because I have used dpkg-fsys-usrunmess(that dpkg
    advised me to do?).
    As a Debian user I'm confused and a bit angry.

    For an user: these boats are currently unstable, it's best to sit tight --
    they topple only if you move around, especially when jumping between them.

    What is way forward?

    That's the subject of a series of flamewars second in length and intensity
    only to the systemd debacle. You don't want to go there.

    The usrmerged state, while wished for by some, is currently pretty broken unless you refrain from a number of actions that are natural for packagers (inside and outside Debian) and users to do, this is considered unacceptable
    by the dpkg maintainer and eg. me.

    There is a proposal for a constructive patch set to dpkg that _may_ resolve this without nasty hacks everywhere; the patches themselves haven't been
    AFAIK implemented yet but there is much hope.

    If that fails, the drama will resume, with the big question being "WHY?".


    Meow!
    --
    ⢀⣴⠾⠻⢶⣦⠀ Eight legs good, four legs bad! -- when your drider pwns a
    ⣾⠁⢠⠒⠀⣿⡁ smelly goodie centaur.
    ⢿⡄⠘⠷⠚⠋⠀ Rearkick OP -- my grandpa's brother-in-law got one-shotted
    ⠈⠳⣄⠀⠀⠀⠀ from full hp in RL, please nerf!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco d'Itri@21:1/5 to Krzysztof Sobiecki on Wed Apr 6 14:40:02 2022
    On Apr 06, Krzysztof Sobiecki <sobkas@gmail.com> wrote:

    Now what I'm supposed to do? Wait for dpkg-fsys-usrunmess-unmess?
    Install the usrmerge package and hopefully everything will be fixed.

    Is my system broken because I have used dpkg-fsys-usrunmess(that dpkg
    advised me to do?).
    Maybe.

    As a Debian user I'm confused and a bit angry.
    And you have every right to be. Sorry, blame the dpkg maintainer.

    What is way forward?
    Merged /usr.

    --
    ciao,
    Marco

    -----BEGIN PGP SIGNATURE-----

    iHUEABYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCYk2JnQAKCRDLPsM64d7X gaqtAQDYMgAFApLvlLHGBPD1mVCg6sOoSK+67l0sSaYLbfvsGAEA367Sk1ygqsyi at57oJAys8ngd/jGDTIUwe4w6IB9LQg=
    =UY9V
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?utf-8?Q?Bj=C3=B8rn_Mork?=@21:1/5 to Marco d'Itri on Wed Apr 6 16:10:01 2022
    Marco d'Itri <md@Linux.IT> writes:

    Sorry, blame the dpkg maintainer.

    Is that how we discuss technical issues around here?


    Bjørn

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rahmatullin@21:1/5 to All on Wed Apr 6 16:10:01 2022
    On Wed, Apr 06, 2022 at 04:02:23PM +0200, Bjørn Mork wrote:
    Sorry, blame the dpkg maintainer.

    Is that how we discuss technical issues around here?
    This is not a technical issue.

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmJNnmgtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh Ts0P/i8omFpwTuOO4A0Ohj1TOH2HxtkPekWgroNgSO/kG5KPKLXE8rlP8wLPnMaE rTxuquJxUYgFBvJrr99i5mBfr4Aq331wYyubzeg1dCnmOMv8yA1SbaWTSgmyLtzB tDpvhQrIG0ZIr23q7Lggan/prgRe08aVcjQJGhh7yAh698ia+usQQTma6iSqmpbH nKtOuyC9bBQz4sCI5X+G8DCsNUmSdDiE9Ws09pLY//AJyuDBJfRtl0ugtaf9Vy8t K7R/zSsnGWlrxGa6RFafnewPSDDfiQzuO9cogbF4u/5mLr1DqebTjnD3y+ut+t+h 0pop1rxuAuiPmGKw53i0byqKVH59uIOqvvWj9zmXFeMoCb09xgozgLFUwZ+NLUhj hDgomp6iTB3O46FNU344Y34fPhTZZdnpOyp413s0FVcRrn+dpamjxsn2glGP2UDd ygsjj/ATogrRPItjoZ0KqzmirDOENld5vgyqfBNAGuRkpPmdYKSiHeKwxjM6CtoI UUUCFWrb6Ao2VeiC59gLLzAucX3wLVcVmgd+KLRvk/RHgoyPezvpo71uDA2LUw1m xO02LgWdYcwvPhgCrKEeVLk8Uq4l3XyHUZMj6kE8MSCIeUaM0snt20hax2tcOdZC /Imi9RHnKkiK/mpPueXldyNp0BAcm1WczLtDbfn0bDDTl8rH
    =iiid
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?utf-8?Q?Bj=C3=B8rn_Mork?=@21:1/5 to Andrey Rahmatullin on Wed Apr 6 16:30:02 2022
    Andrey Rahmatullin <wrar@debian.org> writes:
    On Wed, Apr 06, 2022 at 04:02:23PM +0200, Bjørn Mork wrote:
    Sorry, blame the dpkg maintainer.

    Is that how we discuss technical issues around here?
    This is not a technical issue.

    Ah, sorry. I mistook this for the "Discussion about technical
    development topics" list. My fault


    Bjørn

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Darrah@21:1/5 to Krzysztof Sobiecki on Thu Apr 7 04:30:01 2022
    On Wed, 2022-04-06 at 03:04 -0700, Krzysztof Sobiecki wrote:
    Hi,
    I saw warning and it advised me to use dpkg-fsys-usrunmess:
    But now I see:
    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008486

    From the link above:

    "
    Hi,

    the `dpkg-fsys-usrunmess` program should include a warning that it
    will convert the system into a state that will no longer be supported
    in the future by Debian.

    Ansgar
    "

    Here's hoping I don't have to reinstall soon.

    (Running up-to-date 'testing')

    -- john

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)