home.social

#dpkg — Public Fediverse posts

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

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

    askubuntu.com/q/1566463/612

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

    askubuntu.com/q/1566463/612

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

    askubuntu.com/q/1566463/612

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

    askubuntu.com/q/1566463/612

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

    askubuntu.com/q/1566463/612

  6. @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.

  7. @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.

  8. @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.

  9. @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.

  10. @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

  11. @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

  12. @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

  13. @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

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

    #Linux

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

    #Linux

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

    #Linux

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

    #Linux

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

    #Linux

  19. @Gottox
    Ich hab dieses Verhalten aber noch nie bei #apk #dpkg oder #xbps gesehen - Zufall oder Chiffre?! 😉

  20. @Gottox
    Ich hab dieses Verhalten aber noch nie bei #apk #dpkg oder #xbps gesehen - Zufall oder Chiffre?! 😉

  21. @Gottox
    Ich hab dieses Verhalten aber noch nie bei #apk #dpkg oder #xbps gesehen - Zufall oder Chiffre?! 😉

  22. @Gottox
    Ich hab dieses Verhalten aber noch nie bei #apk #dpkg oder #xbps gesehen - Zufall oder Chiffre?! 😉

  23. @Gottox
    Ich hab dieses Verhalten aber noch nie bei #apk #dpkg oder #xbps gesehen - Zufall oder Chiffre?! 😉

  24. CW: CW Debian 13 deb822

    @unixtippse I think the format is as old as #dpkg itself, so circa 1994.

    So, yes, it predates XML (1996), JSON (2000) and YAML (2001), but not Windows INI.

  25. CW: CW Debian 13 deb822

    @unixtippse I think the format is as old as #dpkg itself, so circa 1994.

    So, yes, it predates XML (1996), JSON (2000) and YAML (2001), but not Windows INI.