apt-get and security updates

  • terminalcafe
Posted: Sat, 09/01/2007 - 13:38
Hello...I'm still a fairly new linux user that has fallen in love with 64 studio. Before your distro I was using mostly debian so the idea of still being able to use regular debian packages is tremendously appealing. I've recently upgraded from 1.0 to 2.0 and have the stable 64studio repository in my current sources.list . I will soon be adding an etch repository because I'm an icewm geek and there are so many other cool things I love about debian packages. In the past on my straight debian systems I would simply setup my sources for the stable repository and security.debian.org and then issue as root the commands... apt-get update apt-get upgrade This worked like a charm in that context. Will it be best to have ONLY the 64 studio stable repository in my sources.list for purposes of security updates or is it good practice to have 64 studio stable, etch and security.debian.org there? Furthermore...are the previously mentioned commands in apt-get the best way to avoiding breaking things in 64 studio? Am I on the wrong track entirely? peace, James Lovell
‹ jack runs at 44099 instead of 44100 64studio 3.0 beta3 - how to attach Debian Lenny DVDs to Synaptic/apt? ›

As I said, it will also tell

  • crysty4ever
  • 08/06/09
  • Thu, 08/06/2009 - 14:12
  • Copy comment link
As I said, it will also tell you if the package isn't signed by someone you trust. It wouldn't be much good to only verify package integrity. Trust is a much more important part of the picture. EDIT: When did you say it? - Admin

Upgrades

  • Quentin Harley
  • 05/24/07
  • Mon, 01/19/2009 - 21:48
  • Copy comment link
I think that is an old comment of mine ;-) It would now apply to "Lenny". Etch is fine to keep while upgrading as the 64studio packages are newer than the "etch" ones and will be prefered by synaptic. I would recommend using the 64 Studio 2.1 "testing" repository. It is quite stable and has new features. You could also try upgrading the the 3.0 "alpha" if you feel brave, or you can wait for the official release later. Cheers, Q

Repos

  • Quentin Harley
  • 05/24/07
  • Thu, 01/01/2009 - 20:45
  • Copy comment link
These should be ok... Q

bump... Or should I move

  • terminalcafe
  • 09/01/07
  • Thu, 01/01/2009 - 17:38
  • Copy comment link
bump... Or should I move this to the user list?

The new safe w/ 2.1

  • terminalcafe
  • 09/01/07
  • Tue, 12/16/2008 - 00:33
  • Copy comment link
So I still like to apt-get my way to 64 Studio nirvana and oh do I still love to use those same two old magical commands I've been using for a few years now...I upgraded to 2.1 following instructions provided by the maintainers of the distro but that was some time ago. Are these the most current safe as milk repos to use to make sure you don't break 64 Studio? deb http://www.mirrorservice.org/sites/64studio.com/apt/ 64studio main deb http://security.debian.org/ etch/updates main contrib non-free I remain as always...easily confused but thankful for help. peace, James

Do not use the backports repository

  • Free
  • 05/22/07
  • Mon, 09/10/2007 - 09:02
  • Copy comment link
Hi Malte, you should NOT use the backports repository, which is experimental. If you want to stick to 64 Studio stable (the latest 2.0 release) just use: http://apt.64studio.com/64studio/stable/ 64studio main or if you want to try the testing branch (the forthcoming 2.1 release), use: http://apt.64studio.com/64studio/testing/ 64studio main

following are

  • HerrSteiner
  • 07/28/07
  • Mon, 09/10/2007 - 08:45
  • Copy comment link
following are active: http://apt.64studio.com/64studio/stable/ 64studio main http://apt.64studio.com/backports/ etch main cheers, Malte

What repos are you using?

  • Free
  • 05/22/07
  • Fri, 09/07/2007 - 15:24
  • Copy comment link
No, it's not a good thing.. Which APT repositories are active?

gnome-core

  • HerrSteiner
  • 07/28/07
  • Fri, 09/07/2007 - 12:08
  • Copy comment link
At the moment I hesitate to upgrade, it always suggested to remove gnome-core and nautilus. Is this a good thing to do?? Cheers, Malte

Don't forget Synaptic

  • Daniel
  • 05/22/07
  • Wed, 09/05/2007 - 10:29
  • Copy comment link
If you are GUI-minded, you can use the Reload and Mark all upgrades buttons in Synaptic to achieve the same effect.

You can use the command

  • deadgobby
  • 09/01/07
  • Sat, 09/01/2007 - 22:56
  • Copy comment link
You can use the command instead of apt-get sudu aptitude upgrade sudo aptitude update YOu can use aptitude to install deb packages as well. It grabs any depends that a deb package may have. Gobby

So this should be safe?

  • terminalcafe
  • 09/01/07
  • Sat, 09/01/2007 - 21:55
  • Copy comment link
If I leave these two repos in my sources.list ... deb http://apt.64studio.com/64studio/stable 64studio main deb http://security.debian.org/ etch/updates main contrib non-free ...then it should be fairly hard for me to break something, right? I just want to confirm that I have not further confused myself somewhere along the way before I run those two wondrous commands... apt-get update apt-get upgrade Coming to you directly from the Department of Redundancy Department, James

Safe as houses

  • Quentin Harley
  • 05/24/07
  • Sun, 09/02/2007 - 15:43
  • Copy comment link
... If you live in a non earthquake or tornado ridden area , that is.

Updates

  • Quentin Harley
  • 05/24/07
  • Sat, 09/01/2007 - 20:13
  • Copy comment link
Hi James, The best way to make sure everything stays as intended is to only enable your 64studio repo and the debian updates before you run the aforementioned commands. You can install anything from etch, no problems there, but disable the etch repo before upgrading. PS: Do try the 64studio testing repository. It is still based on etch, but with some packages backported to sort out some application bugs, and to support newer features. I run testing, and I find it even better than 64studio stable at the moment. Cheers, Quentin

Updates

  • svenoxtoby
  • 06/20/07
  • Mon, 01/19/2009 - 21:05
  • Copy comment link
"The best way to make sure everything stays as intended is to only enable your 64studio repo and the debian updates before you run the aforementioned commands. You can install anything from etch, no problems there, but disable the etch repo before upgrading." Thank you Quentin. I've been doing this as well so I feel reassured now. The manual at http://www.64studio.com/manual/configuration_guide seems to describe an even slicker way whereby one would, I think, upgrade with the etch repo enabled: "First we go to Settings > Preferences; in the Distribution tab change Package Upgrade Behaviour (default distribution) to Prefer versions from: 64studio and click OK." but on my synaptic, I cannot choose to prefer versions from 64 studio, only from "stable", whether I have the debian etch repo added or not. Does anyone else here observe this behaviour?