On Saturday 18 August 2018 12:27:53 pm Slávek
Banko wrote:
On Saturday 18 of August 2018 18:29:52 Michael
wrote:
On Friday 17 August 2018 02:18:41 pm deloptes
wrote:
> Michael wrote:
> > Whatever the correct instructions are, is being forced to
> > upgrade from say ‘7.x - wheezy’ to ‘9.x - stretch’ accurate?
> > But, that does seem to directly conflict with the information
> > presented in “1.1 R14.0.x series,” which implies I can stay on
> > ‘7.x - wheezy’ and install R14x.
>
> Hi,
> you can use TDE 14.X with whatever underlaying linux
> distribution. The condition is that tde should be compiled
> against the packages/libraries of this distribution.
> So watch out to add the correct sources to the source lists.
>
> As far as upgrade is concerned in debian it is not safe to skip a
> version - example wheezy -> stretch is risky and not recommended.
> What debian recommends is wheezy -> jessie -> stretch.
>
> Whatever you do - the TDE source list should match the distro
> version.
>
> I hope it helps
>
> regards
>
> PS: regarding changing wiki - if you don't want or don't have
> permissions to do it, provide detailed instruction what you think
> needs to be changed. I couldn't understand exactly what you mean
> at first reading.
Hi Del,
I can change the wiki, I don't know what to change it to ;)
My background is 95% CentOS with 5% Ubuntu 14.04 as a test of a
'more convenient' working environment.
Based upon what you've said, then yes there is a serious problem
with the Debian wiki page as the instructions as given (AKAIU) are
going to upgrade their distribution instead of just upgrading their
TDE version.
This section from the Debian Aptitude instruction page, also
explicitly states not to use 'full-upgrade,' so again the
instructions on TDE Debian Wiki are almost guaranteed to be
'wrong.'
https://wiki.debian.org/Aptitude
How to upgrade your distribution
Upgrading from one stable release to the next (e.g. Lenny to
Squeeze) is done by following the release notes for your
architecture. For most people with 32 bit systems that means the
Release Notes for Intel x86. For most with 64 bit systems that
means the Release Notes for AMD64.
Using full-upgrade in the regular course of events is no longer the
recommended practice (unless you are running sid, in which case you
should not need to be reading this.)
Minor release upgrades (e.g. from lenny 5.0.1 to 5.0.2) and
security updates are done with safe-upgrade.
Find out the current version of Debian that you are running:
$ cat /etc/debian_version
Example for upgrading from, e.g., etch 4.0r1 to 4.0r2 ...etc., or
applying security upgrades:
# aptitude update
# aptitude safe-upgrade
Looking at the Ubuntu page, the same 'error' has been published:
https://wiki.trinitydesktop.org/Ubuntu_Trinity_Repository_Installat
ion_ Instructions 6.2 Upgrading from an existing R14.0.x or
v3.5.13.x installation sudo aptitude full-upgrade
# # # # #
At my level of 'aptitude' knowledge, I can tell the instructions as
given are almost guaranteed to be erroneous, and very liable to
cause some serious ill will, but what the correct instructions for
'aptitude' systems should be is beyond me. Therefore:
Would someone go 'fix' all the TDE 'aptitude' Wiki pages?
Or, if the TDE instructions as given are correct, then explain the
discrepancies with published 'aptitude' sources?
Best and Thanks,
Michael
Your information here looks very confusing.
Using aptitude full-upgrade does not mean that it cause update from
one version of distribution to another. Using aptitude full-upgrade
certainly does not mean that it would cause that Debian 7.x will be
updated to Debian 9.x. It always depends on what version is listed in
sources.list!
If wheezy is listed in source.list then aptitude full-upgrade will
only update packages within Debian 7.x. No Debian 9.x package comes
on board. You must have your sources.list in order. For example, you
can not use TDE packages for Stretch if your distribution is Wheezy.
The use of aptitude full-upgrade is quite right here, because in the
case of update from TDE 3.5.13.x to TDE R14.0.x, there is a great
change to the version and installation of many new packages. For this
case, aptitude safe-upgrade is unusable.
In case of updating to R14.0.5 from previous R14.0.x here is a new
package tdebase-tdeio-smb-trinity, which will be separated from
package tdebase-tdeio-plugins-trinity. That's why it's good to use
aptitude full-upgrade for upgrade to R14.0.5.
That's why I do not see anything wrong with the instructions on the
Wiki. Using aptitude full-upgrade is definitely not an error. On the
contrary, sometimes it is necessary. The warnings placed on the wiki
therefore seem to me very confusing and wrong.
Cheers
Hi Slávek,
Apologies if my lack of knowledge of aptitude based distributions is
hindering this discussion.
So, let’s see if I can shorten this to just 3 yes/no questions for
foundation clarity...
Doesn’t full-upgrade upgrade the distribution to
the next major
version?
Reference:
https://debian-handbook.info/browse/stable/sect.apt-get.html
“such as the change from one major Debian version to the next, you need
to use apt full-upgrade”
By using “sudo aptitude full-upgrade” for
“Upgrading from an existing
R14.0.x” will it not upgrade both TDE and also distribution upgrade
Ubuntu?
Context:
https://wiki.trinitydesktop.org/Ubuntu_Trinity_Repository_Installation_
Instructions#Upgrading_from_an_existing_R14.0.x_or_v3.5.13.x_installatio
n
If both answers are yes, then the TDE ‘aptitude’ wiki pages are
erroneous as written. (As they are telling the user to both upgrade
TDE and to do a distribution major version upgrade, when the user may
only wish to upgrade TDE.)
Doesn’t Debian specifically say not to use
full-upgrade for a
distribution
upgrade?
Reference:
https://wiki.debian.org/Aptitude
“Upgrading from one stable release to the next (e.g. Lenny to Squeeze)
is done by following the release notes for your architecture.”
“Using full-upgrade in the regular course of events is no longer the
recommended practice”
Okay, this is a bit contradictory to the prior Debian handbook
information, but if this answer is yes, then again the wiki pages are
erroneous as written. As they should have links to the various
distribution release notes.
# # #
The answers to those 3 questions will give us a mutual foundation for
me to clarify what I’m trying address.
Best,
Michael
PS: If the answers are no, then my entire understanding of
dist-upgrade (now an alias for full-upgrade) seems to be erroneous, as
doesn’t the dist-upgrade/full-upgrade process itself update your
source.list to the next major distribution version so it can do the
distribution upgrade?
Hi Michael,
1) aptitude full-upgrade (or dist-upgrade) does not make any changes to
sources.list. If you do not make the change yourself, no distribution
version change will be made.
2) The aptitude documentation says that when you change the distribution
version (which must be done by the user itself), it is necessary to use
aptitude full-upgrade. But that does not mean that aptitude full-upgrade
can not be used in other situations.
3) The recommendation to use aptitude full-upgrade on TDE Wiki is
perfectly fine. This will not cause a change of distribution version, but
will provide an easy transition when renaming packages, split packages,
and so on.
Cheers