Follow-up from “Dumbest Thing you have done distro-hopping?”.

Here’s mine - the laptop from which I’m typing right now has a broken touchpad that keeps jumping and clicking randomly, and does not work. Well, I can’t afford to fix it, but at the moment, I was so pissed off I punched the touchpad really hard, and the machine panicked with all the lights blinking. A few more revival abuses, and the machine was back to life, but since I was running a nixos-rebuild switch --upgrade in the background, I blew off my boot partition. I think I just broke the unbreakable distro.

  • boomzilla@programming.dev
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I just installed it but although informant check and informant read show me unread messages an update with pacman -Syu doesn’t show me the news. I also symlinked the hook via ln -s /usr/share/libalpm/hooks/00-informant.hook /etc/pacman.d/hooks/00-informant.hook (Wrong!). Do you have any idea?

    • corship@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      What.

      So no I do not have an idea since I know nothing about your system/setup.

      BUT

      I’d strongly recommend reading the documentation libalpm in regards to the nonsense symlink you created:

      Hooks are read from files located in the system hook directory /usr/share/libalpm/hooks, and additional custom directories specified in pacman.conf(5) (the default is /etc/pacman.d/hooks).

      • boomzilla@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Ok. Thanks for the nod to the wiki. I never used pacman hooks. Seems I misread informants github page. So the alpm conform way would be to copy (and not symlink) /usr/share/libalpm/00-informant.hook to /etc/pacman.d/hooks only if I would want to override it and other hooks are by default read from the /usr dir.

        The root of my problem was, that the hook is fired only after Pacman asks “Proceed with installation [Y/N]” and the user presses “Y”. Which I hadn’t tried. DOH!