home.social

#dpkg — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dpkg, aggregated by home.social.

  1. After adding the repo thopiekar/openrgb, I am getting an Error from Sub-process /usr/bin/dpkg #apt #dpkg

    askubuntu.com/q/1566843/612

  2. After adding the repo thopiekar/openrgb, I am getting an Error from Sub-process /usr/bin/dpkg #apt #dpkg

    askubuntu.com/q/1566843/612

  3. After adding the repo thopiekar/openrgb, I am getting an Error from Sub-process /usr/bin/dpkg #apt #dpkg

    askubuntu.com/q/1566843/612

  4. After adding the repo thopiekar/openrgb, I am getting an Error from Sub-process /usr/bin/dpkg #apt #dpkg

    askubuntu.com/q/1566843/612

  5. After adding the repo thopiekar/openrgb, I am getting an Error from Sub-process /usr/bin/dpkg #apt #dpkg

    askubuntu.com/q/1566843/612

  6. openssh-server post-installation script error (exit status 10) and SSH not working #apt #dpkg #openssh

    askubuntu.com/q/1566463/612

  7. openssh-server post-installation script error (exit status 10) and SSH not working #apt #dpkg #openssh

    askubuntu.com/q/1566463/612

  8. openssh-server post-installation script error (exit status 10) and SSH not working #apt #dpkg #openssh

    askubuntu.com/q/1566463/612

  9. openssh-server post-installation script error (exit status 10) and SSH not working #apt #dpkg #openssh

    askubuntu.com/q/1566463/612

  10. openssh-server post-installation script error (exit status 10) and SSH not working #apt #dpkg #openssh

    askubuntu.com/q/1566463/612

  11. @attilakinali @nixCraft Actually you should be fine, but only if you apt-mark manual those libs that you needed for your custom packages.

    It's good hygiene to do this often. You can reinstall the missing libs if needed. And if you can't, you're sitting on a time bomb anyway.

    #dpkg #hygiene

    P.S. apt-find-foreign for even more clean systems after release upgrade.

  12. @attilakinali @nixCraft Actually you should be fine, but only if you apt-mark manual those libs that you needed for your custom packages.

    It's good hygiene to do this often. You can reinstall the missing libs if needed. And if you can't, you're sitting on a time bomb anyway.

    P.S. apt-find-foreign for even more clean systems after release upgrade.

  13. @attilakinali @nixCraft Actually you should be fine, but only if you apt-mark manual those libs that you needed for your custom packages.

    It's good hygiene to do this often. You can reinstall the missing libs if needed. And if you can't, you're sitting on a time bomb anyway.

    #dpkg #hygiene

    P.S. apt-find-foreign for even more clean systems after release upgrade.

  14. @attilakinali @nixCraft Actually you should be fine, but only if you apt-mark manual those libs that you needed for your custom packages.

    It's good hygiene to do this often. You can reinstall the missing libs if needed. And if you can't, you're sitting on a time bomb anyway.

    #dpkg #hygiene

    P.S. apt-find-foreign for even more clean systems after release upgrade.

  15. @Larvitz

    1.

    There may be equivalents to "pkg which" in some of the other package managers.

    2.

    "pw useradd" is not a straight exchange for shadow-utils useradd.

    The very annoying gotcha (which means that one cannot just write a pw() shell function that strips the command name) is that they do not agree on whether the options come before or after the username argument.

    #FreeBSD #pw #pkg #useradd #dpkg

  16. @Larvitz

    1.

    There may be equivalents to "pkg which" in some of the other package managers.

    2.

    "pw useradd" is not a straight exchange for shadow-utils useradd.

    The very annoying gotcha (which means that one cannot just write a pw() shell function that strips the command name) is that they do not agree on whether the options come before or after the username argument.

    #FreeBSD #pw #pkg #useradd #dpkg

  17. @Larvitz

    1.

    There may be equivalents to "pkg which" in some of the other package managers.

    2.

    "pw useradd" is not a straight exchange for shadow-utils useradd.

    The very annoying gotcha (which means that one cannot just write a pw() shell function that strips the command name) is that they do not agree on whether the options come before or after the username argument.

    #FreeBSD #pw #pkg #useradd #dpkg

  18. @Larvitz

    1.

    There may be equivalents to "pkg which" in some of the other package managers.

    2.

    "pw useradd" is not a straight exchange for shadow-utils useradd.

    The very annoying gotcha (which means that one cannot just write a pw() shell function that strips the command name) is that they do not agree on whether the options come before or after the username argument.

    #FreeBSD #pw #pkg #useradd #dpkg

  19. Finally facing the dreaded #dpkg Error 1. Time to wipe and reload.

    #Linux

  20. Finally facing the dreaded #dpkg Error 1. Time to wipe and reload.

    #Linux