Using Synaptic to “Lock” package

Forum Forums General Software Using Synaptic to “Lock” package

  • This topic has 3 replies, 2 voices, and was last updated Jan 1-6:42 pm by seaken64.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #31365
    Member
    seaken64

      Once I use Synaptic to “Lock” a package do I have to use Synaptic only for updates? I’m asking because when I run “sudo apt-get dist-upgrade” now, like is my habit, I see the SeaMonkey package on the list of packages to be upgraded. But that is the package that I locked in Synaptic. I thought by locking it it would be ignored by apt-get. Apparently not.

      Is there a way to lock the package directly in apt-get or apt? Or do I have to use Synaptic for updates to avoid the latest SeaMonkey?

      Seaken64

      #31366
      Member
      seaken64
        Helpful
        Up
        0
        ::

        I found this command

        sudo apt-mark hold seamonkey

        That did it. The seamonkey package now shows on the end of the report as “kept back” and it does not attempt to upgrade it.

        But I thought Synaptic would do that for me, that is modify the package database on my behalf.

        Seaken64

        #31373
        Anonymous
          Helpful
          Up
          0
          ::

          As you have discovered, settings (preferences) elected from within synaptic usually are not consulted during non-synaptic operations (commandline apt-get, aptitude, packageinstaller)

          #31374
          Member
          seaken64
            Helpful
            Up
            0
            ::

            Yes, I learned the lesson. It’s a good thing I was a good boy and read thru the pre-launch report before blindly clicking on Yes.

            I also went thru the cli-aptiX package manager. I could not find anything that allowed me to lock or hold a package.

            I tend to upgrade with apt-get from the terminal. But this is the first time I have ever kept back a package. I’m learning.

            Thanks,
            Seaken64

          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.