aptitude safe-upgrade '?version(4:3.5.13)'
if 4:3.5.13 is currently installed version.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
aptitude safe-upgrade '?version(4:3.5.13)'
if 4:3.5.13 is currently installed version.
Simplest? sudo apt-get dist-upgrade
Now that's probably not the safest way to do it; can someone else suggest a safer method for end-users?
This also sounds like something that should be on our Wiki.
Thanks!
Tim
Now that's probably not the safest way to do it; can someone else suggest a safer method for end-users? This also sounds like something that should be on our Wiki.
Before releasing v14.0.0 we should make sure we address this. I have added a note on the Release Checklist (http://trinity.etherpad.trinitydesktop.org/37)
Michele
I would add LinuxQuestions to the list of places you would send the release announcement to if I were you. It probably has the biggest user group of any dedicates Linux forum.
As for updating from 3.5.13 to 14 these things are never easy and, for Debian based distros, I would normally recommend a clean install after a proper backup is done. I know with the MATE Desktop Environment, which I also use, each upgrade has teething problems when upgrades are done but are do not occur with clean installs. That is why when I finally release Cobber (about 1 months time hopefully) what I release Cobber Stable with is what it will remain released with but I may backport newer releases for those who are willing to work through teething problems.
Cheers. Michael.
On 21 May 2014 14:22, Michele Calgaro michele.calgaro@yahoo.it wrote:
Now that's probably not the safest way to do it; can someone else suggest a safer method for end-users? This also sounds like something that should be on our Wiki.
Before releasing v14.0.0 we should make sure we address this. I have added a note on the Release Checklist ( http://trinity.etherpad.trinitydesktop.org/37)
Michele
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Wed, May 21, 2014 at 1:15 AM, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
aptitude safe-upgrade '?version(4:3.5.13)'
if 4:3.5.13 is currently installed version.
Simplest? sudo apt-get dist-upgrade
dist-upgrade upgrades ALL packages. This is a level harder!
On Wednesday 21 May 2014 10:53:38 Aleksey Midenkov wrote:
On Wed, May 21, 2014 at 1:15 AM, Timothy Pearson
kb9vqf@pearsoncomputing.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
aptitude safe-upgrade '?version(4:3.5.13)'
if 4:3.5.13 is currently installed version.
Simplest? sudo apt-get dist-upgrade
dist-upgrade upgrades ALL packages. This is a level harder!
If one is asking aptitude to upgrade a particular version of a particular package, surely one has to name the package as well as the version? And the version one wants, not the version one has??
Lisi
If you are only going to upgrade one package just name the package, I don't remember ever having to give a version number with aptitude. If you are going to upgrade a chosen selection of packages you may as well use a GUI (synaptic) and select them visually.
On 21 May 2014 20:18, Lisi Reisz lisi.reisz@gmail.com wrote:
On Wednesday 21 May 2014 10:53:38 Aleksey Midenkov wrote:
On Wed, May 21, 2014 at 1:15 AM, Timothy Pearson
kb9vqf@pearsoncomputing.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
aptitude safe-upgrade '?version(4:3.5.13)'
if 4:3.5.13 is currently installed version.
Simplest? sudo apt-get dist-upgrade
dist-upgrade upgrades ALL packages. This is a level harder!
If one is asking aptitude to upgrade a particular version of a particular package, surely one has to name the package as well as the version? And the version one wants, not the version one has??
Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Wed, May 21, 2014 at 2:18 PM, Lisi Reisz lisi.reisz@gmail.com wrote:
On Wednesday 21 May 2014 10:53:38 Aleksey Midenkov wrote:
On Wed, May 21, 2014 at 1:15 AM, Timothy Pearson
kb9vqf@pearsoncomputing.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
aptitude safe-upgrade '?version(4:3.5.13)'
if 4:3.5.13 is currently installed version.
Simplest? sudo apt-get dist-upgrade
dist-upgrade upgrades ALL packages. This is a level harder!
If one is asking aptitude to upgrade a particular version of a particular package, surely one has to name the package as well as the version? And the version one wants, not the version one has??
Man, my message was not just 'a guess'. It was real command that was really run and really brought good result. I've done upgrade with it.
On Thursday 22 May 2014 12:13:16 Aleksey Midenkov wrote:
Man, my message was not just 'a guess'. It was real command that was really run and really brought good result. I've done upgrade with it.
More explanation and less high horse might have been helpful.
Lisi
On Thu, May 22, 2014 at 5:27 PM, Lisi Reisz lisi.reisz@gmail.com wrote:
On Thursday 22 May 2014 12:13:16 Aleksey Midenkov wrote:
Man, my message was not just 'a guess'. It was real command that was really run and really brought good result. I've done upgrade with it.
More explanation and less high horse might have been helpful.
'?version(X)' selects all packages whose version contains substring X for upgrade. 'safe-upgrade' does 'lazy' upgrade. I.e. it will not select anything additional unless required by the selected packages. 'aptitude' by itself resolves conflicts more intelligently than 'apt-get'. So, that's it -- just one command and whole KDE3 is upgraded without any PIA!
Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Tuesday 27 May 2014 18:06:11 Aleksey Midenkov wrote:
On Thu, May 22, 2014 at 5:27 PM, Lisi Reisz lisi.reisz@gmail.com wrote:
On Thursday 22 May 2014 12:13:16 Aleksey Midenkov wrote:
Man, my message was not just 'a guess'. It was real command that was really run and really brought good result. I've done upgrade with it.
More explanation and less high horse might have been helpful.
'?version(X)' selects all packages whose version contains substring X for upgrade. 'safe-upgrade' does 'lazy' upgrade. I.e. it will not select anything additional unless required by the selected packages. 'aptitude' by itself resolves conflicts more intelligently than 'apt-get'. So, that's it -- just one command and whole KDE3 is upgraded without any PIA!
Thanks! Lisi
safe-upgrade only upgrades packages that don't require any new packages to be installed or any old ones to be removed. If you want a full upgrade you must either use apt-get upgrade or apt-get dist-upgrade.
On 21 May 2014 19:53, Aleksey Midenkov midenok@gmail.com wrote:
On Wed, May 21, 2014 at 1:15 AM, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
aptitude safe-upgrade '?version(4:3.5.13)'
if 4:3.5.13 is currently installed version.
Simplest? sudo apt-get dist-upgrade
dist-upgrade upgrades ALL packages. This is a level harder!
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Wednesday 21 May 2014 11:22:02 Michael . wrote:
On 21 May 2014 19:53, Aleksey Midenkov midenok@gmail.com wrote:
aptitude safe-upgrade '?version(4:3.5.13)'
if 4:3.5.13 is currently installed version.
I was referring specifically to Aleksey Midenkov's email.
Lisi
On Wed, May 21, 2014 at 2:22 PM, Michael . keltoiboy@gmail.com wrote:
safe-upgrade only upgrades packages that don't require any new packages to be installed or any old ones to be removed.
Not true. Just try 'man aptitude'.
Not true. Just try 'man aptitude'.
From aptitudes man page
Upgrades installed packages to their most recent version. Installed packages will not be removed unless they are unused (see the section “Managing Automatically Installed Packages” in the *aptitude* reference manual). Packages which are not currently installed may be installed to resolve dependencies unless the *--no-new-installs* command-line option is supplied
While it wasn't totally accurate it is reality that it will NOT remove packages. Also the phrase "Packages which are not currently installed MAY be installed to resolve dependencies ..." Does not say they WILL be installed. Apt is not perfect and I have seen instances where packages that are not removed cause problems I have also seen cases where dependency issues are not resolvable easily so nothing new is installed.
Anyway your initial question is not actually a question instead it is a statement so I am wondering what your point really is.
On 22 May 2014 21:07, Aleksey Midenkov midenok@gmail.com wrote:
On Wed, May 21, 2014 at 2:22 PM, Michael . keltoiboy@gmail.com wrote:
safe-upgrade only upgrades packages that don't require any new packages
to
be installed or any old ones to be removed.
Not true. Just try 'man aptitude'.
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Here the most simple way is considered the way least likely to cause problems.
Time to upgrade my main Wheezy install to R14. This went simply, flawlessly and quickly:
1. Change TDE sources to R14
2. apt-get update && apt-get dist-upgrade -d
3. Close X (service kdm-trinity stop) and login as root to console
4. apt-get dist-upgrade
5. Reboot to R14! (probably enough to: service tdm-trinity start)
Some post-upgrade cleanups (do this in X):
There will be quite a few TDE "transitional" packages which can now be removed.
dpkg -l|grep trinity|grep "This can be safely removed"|awk '{print $2}'
/tmp/transitional_packages
(su) or (sudo su)
for i in $(cat /tmp/transitional_packages); do apt-get -y --force-yes purge $i; done
Now, there may be some marked as "automatically installed and no longer required" that you want to keep. This will be shown in the terminal. To change their status do, e.g. "apt-mark manual package1 package2 package3"
Job done, everything is nice and clean.
NOTES:
Someone suggested "apt-get upgrade". This is *not* correct (read man apt-get). Some essential packages might get held back, leaving a broken system.
Do "apt-get dist-upgrade -d" first: if anything is wrong with the mirrors things can break. This has happened before.
I'm finding Slavek's mirror faster than than "nightlies"
Major upgrades while X is running or using GUI package managers: If you really must, good luck to you, you may need it.
There is normally no reason why a Debian system should ever need to be reinstalled.
No comment on aptitude, I don't normally use it.
Regards,
David
Time to upgrade my main Wheezy install to R14. This went simply, flawlessly and quickly:
Thanks David, this is a very useful email. I think it will be an excellent starting point for a wiki page about 'how to upgrade to v14.0.0'.
Cheers Michele
On 25/05/14 13:14, Michele Calgaro wrote:
Time to upgrade my main Wheezy install to R14. This went simply, flawlessly and quickly:
Thanks David, this is a very useful email. I think it will be an excellent starting point for a wiki page about 'how to upgrade to v14.0.0'.
Cheers Michele
Pleased to help, since Debian is my OS of choice and TDE my DE of choice.
Some will disagree. The issue of major upgrades in X has been thrashed 1001 times. My suggestions are based on experience of maintaining all flavours of Debian since Sarge (and the mistakes learned!)
Another observation: If you use another DE (I use also xfce), post-upgrade you might want to run "update-alternatives --all" to make sure everything is how you want it. Here xfce had taken over a few (e.g. x-terminal-emulator). Available choices are mostly obvious and simple to adjust.
hal-trinity libqt3-mt were marked as "automatically installed and are no longer required" Can someone please confirm they can be safely purged?
Someone else did mention what I forgot: do a backup before any major upgrade!
David
Pleased to help, since Debian is my OS of choice and TDE my DE of choice.
Good combination, looks like mine :-) (even though I am on D/testing and TDE/git sources)
hal-trinity libqt3-mt were marked as "automatically installed and are no longer required" Can someone please confirm they can be safely purged?
On v14.0.0 they are no longer required. Actually on Debian/testing hal is no longer provided at all for Linux (only for *bsd). qt3 has also been replaced by tqt3.
Someone else did mention what I forgot: do a backup before any major upgrade
Always a good point.
Cheers Michele
On Sunday 25 May 2014 05:40:36 you wrote:
On 25/05/14 13:14, Michele Calgaro wrote:
Time to upgrade my main Wheezy install to R14. This went simply, flawlessly and quickly:
Thanks David, this is a very useful email. I think it will be an excellent starting point for a wiki page about 'how to upgrade to v14.0.0'.
Cheers Michele
Pleased to help, since Debian is my OS of choice and TDE my DE of choice.
Some will disagree. The issue of major upgrades in X has been thrashed 1001 times. My suggestions are based on experience of maintaining all flavours of Debian since Sarge (and the mistakes learned!)
Another observation: If you use another DE (I use also xfce), post-upgrade you might want to run "update-alternatives --all" to make sure everything is how you want it. Here xfce had taken over a few (e.g. x-terminal-emulator). Available choices are mostly obvious and simple to adjust.
hal-trinity libqt3-mt were marked as "automatically installed and are no longer required" Can someone please confirm they can be safely purged?
Debian Squeeze LTS: apt-get -s purge libqt3-mt: The following packages will be REMOVED: basket-kontact-integration-trinity* kdepim-trinity* kleopatra-trinity* kmail-trinity* kmailcvt-trinity* kontact-trinity* libavahi-qt3-1* libdbus-qt-1-1c2* libpoppler-qt2* libqt-perl* libqt3-mt* pinentry-qt* qca-tls* tdepim-trinity*
libavahi-qt3-1 unused removed.
Someone else did mention what I forgot: do a backup before any major upgrade!
David
I do not normally upgrade from an X session, should this be the Trinity position ? I have not, probably will not, test gui package managers, though asking users to exit X (ctl+alt+F?), stoping the X session, seems iffy for most folks I know.
For those who boot to a grub screen selecting the 'recovery mode' is a good option for using the cli to upgrade. I was suprised how well my upgrade went using a terminal my TDE DE, lucky or a viable option?
? 1. click on the Konsole icon
On Sunday 25 May 2014 12:16:00 David Hare wrote:
There is normally no reason why a Debian system should ever need to be reinstalled.
I would like to upgrade, without reinstalling, from Wheezy to Jessie and 3.5.13.2 to 3.5.14. Would I be better to upgrade TDE and let it settle, then upgrade Debian, or the other way round? Or ought I to wait? That is a tempting possibility given that I love what I have got!
No comment on aptitude, I don't normally use it.
I use what the release notes recommend for an upgrade, but am still using aptitude for every day. An old dog can learn new tricks - but may still be more comfortable with the old ones. ;-)
Lisi
On Sunday 25 May 2014 11:11:21 you wrote:
On Sunday 25 May 2014 12:16:00 David Hare wrote:
There is normally no reason why a Debian system should ever need to be reinstalled.
I would like to upgrade, without reinstalling, from Wheezy to Jessie and 3.5.13.2 to 3.5.14. Would I be better to upgrade TDE and let it settle, then upgrade Debian, or the other way round? Or ought I to wait? That is a tempting possibility given that I love what I have got!
My experience, I initially regreted upgrading from Squeeze to Wheezy...everthing just worked. I tell myself there has to be a compelling reason to upgrade and since I mange my main apps outside of the Debian repo's, it should of simplifed the decison, it never does. TDE apps and Apache Openoffice are the main stays of my business.. they do not require OS changes. I use Iceweasel and the Debian Mozilla team maintains this app.
No comment on aptitude, I don't normally use it.
I use what the release notes recommend for an upgrade, but am still using aptitude for every day. An old dog can learn new tricks - but may still be more comfortable with the old ones. ;-)
Lisi
I noticed 3.5.14 is available for Squeeze, Wheezy and Jessie.
Someone suggested "apt-get upgrade". This is *not* correct (read man
apt-get). Some essential packages might get held back, leaving a broken system.
I said it could be used, and it can in various circumstances, I didn't suggest it was the optimal method. I have upgraded Debian (starting with Lenny) and Ubuntu (7.04 to 11.10 and as a development tester from 10.04 to 11.10) from one version to another with every method available (including apt-get upgrade after adjusting sources.list) and believe, and stated clearly in my first reply, the best way is to do a backup of must have settings-files-etc etc etc and then do a complete clean install. That way you have a clean system, you have your settings, and you have up to date software.
Cheers. Michael.
On 25 May 2014 21:16, David Hare davidahare@gmail.com wrote:
Here the most simple way is considered the way least likely to cause problems.
Time to upgrade my main Wheezy install to R14. This went simply, flawlessly and quickly:
Change TDE sources to R14
apt-get update && apt-get dist-upgrade -d
Close X (service kdm-trinity stop) and login as root to console
apt-get dist-upgrade
Reboot to R14! (probably enough to: service tdm-trinity start)
Some post-upgrade cleanups (do this in X):
There will be quite a few TDE "transitional" packages which can now be removed.
dpkg -l|grep trinity|grep "This can be safely removed"|awk '{print $2}' > /tmp/transitional_packages
(su) or (sudo su)
for i in $(cat /tmp/transitional_packages); do apt-get -y --force-yes purge $i; done
Now, there may be some marked as "automatically installed and no longer required" that you want to keep. This will be shown in the terminal. To change their status do, e.g. "apt-mark manual package1 package2 package3"
Job done, everything is nice and clean.
NOTES:
Someone suggested "apt-get upgrade". This is *not* correct (read man apt-get). Some essential packages might get held back, leaving a broken system.
Do "apt-get dist-upgrade -d" first: if anything is wrong with the mirrors things can break. This has happened before.
I'm finding Slavek's mirror faster than than "nightlies"
Major upgrades while X is running or using GUI package managers: If you really must, good luck to you, you may need it.
There is normally no reason why a Debian system should ever need to be reinstalled.
No comment on aptitude, I don't normally use it.
Regards,
David
To unsubscribe, e-mail: trinity-users-unsubscribe@ lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists. pearsoncomputing.net Read list messages on the web archive: http://trinity-users. pearsoncomputing.net/ Please remember not to top-post: http://trinity. pearsoncomputing.net/mailing_lists/#top-posting
"David" == David Hare davidahare@gmail.com writes:
Here the most simple way is considered the way least likely to cause problems. Time to upgrade my main Wheezy install to R14. This went simply, flawlessly and quickly:
What about:
1. Modify Change the sources.list file
- Close X (service kdm-trinity stop) and login as root to console
- apt-get update && apt-get dist-upgrade -d
sudo apt-get purge desktop-base-trinity kde-trinity
(I still have 3.5.12 installed and in the installation instructions the core command was: sudo apt-get install desktop-base-trinity kde-trinity)
3. Reboot!
sudo apt-get update
sudo apt-get install kubuntu-default-settings-trinity kubuntu-desktop-trinity
Uwe Brauer
On Tuesday 20 May 2014 01:15:03 pm you wrote:
aptitude safe-upgrade '?version(4:3.5.13)'
if 4:3.5.13 is currently installed version.
Simplest? sudo apt-get dist-upgrade
Now that's probably not the safest way to do it; can someone else suggest a safer method for end-users?
This also sounds like something that should be on our Wiki.
Thanks!
Tim
My experience with Debian . Freeze the release, test it for as long as it takes..which includes finding the clean upgrade path, if possible, and writing the release notes, read the release notes :-)
There are lots of upgrade tools as others have indicated, which ones and in what sequence are revealed through thorough testing.
One good point: there may not be a clean upgrade path for TDE 14 since all the naming changes have happened...I have not upgraded an install yet. I intend to have a local mirror of R14 which will make clean installs or upgrades easy and fast.
One comment on clean installs, the home directory stays the same which includes all the user/application settings and info.
-
Aleksey Midenkov -
David Hare -
Greg Madden -
Lisi Reisz -
Michael . -
Michele Calgaro -
Timothy Pearson -
Uwe Brauer