Új hozzászólás Aktív témák

• Crvsh3R senior tag

  #10798

  #10797 ubyegon2

  2025-08-13 20:35:22

  Új Válasz

  Új hozzászólás

  Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra

  

  Crvsh3R

  senior tag

  #10797 ubyegon2

  #10797 ubyegon2

  A nala tart vissza csomagokat, ez normális.

  Trixie béta utolsó frissítésekor a nala visszatartotta az RC3 új kernelét, ezért az apt-tal raktam fel.

  Ezt értem, csak azt nem, hogy Bookworm esetén miért működött és most miért nem. Annál simán felrakta.

  Update:
  Közben meg lett a megfejtés, Bookworm-on 13.2 telepítette a default repoból, 14-tól változott a default behavior:

  "This is going to be quite a long explanation. In order to understand why this is, there are some things about apt that you have to know first.
  There are 3 modes to an upgrade with apt.
  Only upgrade packages, Do not install or remove any packages. (apt-get upgrade)Upgrade and Install NEW packages if required, but don't remove any (apt upgrade)Upgrade and install NEW packages and Remove packages if necessary (apt/apt-get full-upgrade/dist-upgrade)
  Now that we have explained this, we can start talking about Nala. Nala uses python-apt in order to do the apt things. Python-apt has support for upgrade modes 1 and 3, but not 2 which is what apt upgrade uses.
  before v0.14.0 Nala defaulted to full-upgrade, option 3. There have been many bug reports of upgrades breaking stuff for users of Sid or Ubuntu Devel releases, or sometimes distros who do not manage their repos very well. So with 0.14.0 we changed the default upgrade mode to option 1. I would have used 2, but it's not available to us, and will be available if I ever finish rewritting it in rust.
  This is why you're seeing the discrepancy between nala and apt. If you compare what nala upgrade is going to do vs apt-get upgrade, You should see that they are the same.
  Now, there is a configuration option in /etc/nala/nala.conf which you can switch the default back to option 3 if you choose too.
  Simply go into that file, and change the following option to true, and it will be like Nala was before.
  # Set to true to make full-upgrade the default full_upgrade = false
  If you don't want to change the config you can use nala upgrade --full and it will be like the old functionality. We also have two aliases for this nala full-upgrade and nala dist-upgrade, but note there is a bug where the aliases won't automatically update the package lists for you. If you use the config option or nala upgrade --full then it still will. This bug will be fixed in the next release.
  I think that should be about it, if it's still unclear or you have any further questions, please feel free to ask."

  Source

Új hozzászólás Aktív témák