11 Dec
2014
11 Dec
'14
3:48 a.m.
The upgrade from 3.5.13.2 to R14 includes a lot of package
"renames".
After a clean i386 Wheezy 3.5.13.2 install of kde-trinity
is upgraded to R14 RC2, an "apt-get autoremove" removes
48 transitional dummy packages. This is good.
However there are still (roughly) 15 transitional dummy
packages whose descriptions say they can be safely
uninstalled. All that is preventing them from being
uninstalled is two meta packages - kde-trinity and
kde-core-trinity. And so the conscientious sysadmin
removes the two unnecessary meta packages and the
(roughly) 15 remaining transitional dummy packages.
And the next "apt-get autoremove" eats 290 packages
which is most of Trinity.
If you had less than a normal kde-trinity installation
of 3.5.13.2 this problem hits you much sooner and
without uninstalling any meta packages.
What to do? Something in the release notes?
--Mike
11 Dec
11 Dec
4:03 a.m.
New subject: [trinity-devel] Package renames and autoremove
On 2014/12/11 12:48 PM, Mike Bird wrote:
The upgrade from 3.5.13.2 to R14 includes a lot of
package
"renames".
After a clean i386 Wheezy 3.5.13.2 install of kde-trinity
is upgraded to R14 RC2, an "apt-get autoremove" removes
48 transitional dummy packages. This is good.
However there are still (roughly) 15 transitional dummy
packages whose descriptions say they can be safely
uninstalled. All that is preventing them from being
uninstalled is two meta packages - kde-trinity and
kde-core-trinity. And so the conscientious sysadmin
removes the two unnecessary meta packages and the
(roughly) 15 remaining transitional dummy packages.
And the next "apt-get autoremove" eats 290 packages
which is most of Trinity.
If you had less than a normal kde-trinity installation
of 3.5.13.2 this problem hits you much sooner and
without uninstalling any meta packages.
What to do? Something in the release notes?
--Mike
In the installation instructions for Debian/Ubuntu, it is recommended to
use aptitude instead of apt-get to upgrade.
It seems that using apt-get does not resolve all dependencies correctly
(see bug 2245 on bugszilla).
Do you have a change to retry using aptitude?
Cheers
Michele
4:14 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Thursday 11 of December 2014 04:48:43 Mike Bird wrote:
The upgrade from 3.5.13.2 to R14 includes a lot of
package
"renames".
After a clean i386 Wheezy 3.5.13.2 install of kde-trinity
is upgraded to R14 RC2, an "apt-get autoremove" removes
48 transitional dummy packages. This is good.
However there are still (roughly) 15 transitional dummy
packages whose descriptions say they can be safely
uninstalled. All that is preventing them from being
uninstalled is two meta packages - kde-trinity and
kde-core-trinity. And so the conscientious sysadmin
removes the two unnecessary meta packages and the
(roughly) 15 remaining transitional dummy packages.
And the next "apt-get autoremove" eats 290 packages
which is most of Trinity.
If you had less than a normal kde-trinity installation
of 3.5.13.2 this problem hits you much sooner and
without uninstalling any meta packages.
What to do? Something in the release notes?
Yes, there is a problem in that packages kde-trinity, kde-core-trinity and
kde-devel-trinity are not automatically replaced with new tde-trinity,
tde-core-trinity and tde-devel-trinity. The reason is that the previous KDE
meta-packages have different version numbers, and they were so far in advance
compared to the standard R14 numbering.
As you suggest, this would be good to mention in the instructions for
upgrading on Debian.
Incidentally, there are also general comments about the replacement packages
during upgrade - for example, replace kpowersave to tdepowersave and
knetworkmanager to tdenetworkmanager. This is independent of the
distribution. Where should we put these instructions?
--
Slávek
5:03 a.m.
New subject: [trinity-devel] Package renames and autoremove
On 2014/12/11 01:14 PM, Slávek Banko wrote:
Incidentally, there are also general comments about
the replacement packages
during upgrade - for example, replace kpowersave to tdepowersave and
knetworkmanager to tdenetworkmanager. This is independent of the
distribution. Where should we put these instructions?
Probably the best place is in the Release Notes.
If you can write a small paragraph with the required text, I can later
added to the wiki page.
Cheers
Michele
PS: Ubuntu instructions have been corrected.
8:37 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Wed December 10 2014 20:03:33 Michele Calgaro wrote:
In the installation instructions for Debian/Ubuntu, it
is recommended to
use aptitude instead of apt-get to upgrade.
It seems that using apt-get does not resolve all dependencies correctly
(see bug 2245 on bugszilla).
Do you have a change to retry using aptitude?
I would not recommend either apt-get or aptitude over the other as
one is worse in some cases and the other is worse in other cases.
Aptitude is maybe a bit smarter than apt-get and tends to autoremove
automatically which is a separate step with apt-get.
With a without-recommends standard install of 3.5.13.2 upgrade
to R14 R2 aptitude avoids the conflict mentioned in bug 2245
because aptitude autoremoves kdebase-kio-plugins-trinity during
the dist-upgrade, along with autoremoving roughly 47 other packages
that would be a separate step with apt-get.
When you try to purge the remaining roughly 15 dummy packages with
aptitude it is smart enough to figure out on its own that kde-trinity
and kde-core-trinity need to be removed ... but then you're in the
same position as with apt-get - most of Trinity is autoremoved.
//
The above considered only a standard install. Let's now compare
apt-get versus aptitude in the case of a small 3.5.13.2 install
of just "kdm-trinity kdevelop-trinity" along with their depends
but not their recommends.
With apt-get after the dist-upgrade some but not all of the
dummy packages are amenable to autoremove. Purging the remaining
dummy packages results in the entire Trinity install becoming
autoremovable.
With aptitude the dist-upgrade proceeds as with apt-get except
most of the dummy packages are autoremoved during the dist-upgrade.
The only two remaining dummy packages are kdm-trinity and
kdevelop-trinity. When aptitude is told to purge these two the
entire Trinity install is autoremoved.
//
My guess is that the transition packages should somehow transfer
their manual/auto state to the new packages but I don't know a
clean way of doing this.
--Mike
9:47 a.m.
New subject: [trinity-devel] Package renames and autoremove
On 2014/12/11 05:37 PM, Mike Bird wrote:
On Wed December 10 2014 20:03:33 Michele Calgaro
wrote:
Hi Mike,
I haven't (yet) tried an upgrade from 3.5.13.2 to r14.0.0 myself (I will
have to test on a VM sometime next week), but when you are going for the
dummy package removal, I suggest you try this: run aptitude in
interactive mode, select the dummy packages to remove, press 'g'. You
will have a screen with a summary of what packages are going to be
removed, which most likely will include most of TDE packages (based on
your mail) as "autodependency (A)". Mark tdebase, tdelibs and all other
"general" tde packages as "keep". This should possibly keep most of
TDE
installed, while allowing you to remove those dummy packages.
Having said that, I am going to try a similar upgrade as well, sometime
next week. If I find better ways, I will let you know.
Cheers
Michele
In the installation instructions for
Debian/Ubuntu, it is recommended to
use aptitude instead of apt-get to upgrade.
It seems that using apt-get does not resolve all dependencies correctly
(see bug 2245 on bugszilla).
Do you have a change to retry using aptitude?
I would not recommend either apt-get or aptitude over the other as
one is worse in some cases and the other is worse in other cases.
Aptitude is maybe a bit smarter than apt-get and tends to autoremove
automatically which is a separate step with apt-get.
With a without-recommends standard install of 3.5.13.2 upgrade
to R14 R2 aptitude avoids the conflict mentioned in bug 2245
because aptitude autoremoves kdebase-kio-plugins-trinity during
the dist-upgrade, along with autoremoving roughly 47 other packages
that would be a separate step with apt-get.
When you try to purge the remaining roughly 15 dummy packages with
aptitude it is smart enough to figure out on its own that kde-trinity
and kde-core-trinity need to be removed ... but then you're in the
same position as with apt-get - most of Trinity is autoremoved.
//
The above considered only a standard install. Let's now compare
apt-get versus aptitude in the case of a small 3.5.13.2 install
of just "kdm-trinity kdevelop-trinity" along with their depends
but not their recommends.
With apt-get after the dist-upgrade some but not all of the
dummy packages are amenable to autoremove. Purging the remaining
dummy packages results in the entire Trinity install becoming
autoremovable.
With aptitude the dist-upgrade proceeds as with apt-get except
most of the dummy packages are autoremoved during the dist-upgrade.
The only two remaining dummy packages are kdm-trinity and
kdevelop-trinity. When aptitude is told to purge these two the
entire Trinity install is autoremoved.
//
My guess is that the transition packages should somehow transfer
their manual/auto state to the new packages but I don't know a
clean way of doing this.
--Mike
9:58 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Thu December 11 2014 01:47:03 Michele Calgaro wrote:
I haven't (yet) tried an upgrade from 3.5.13.2 to
r14.0.0 myself (I will
have to test on a VM sometime next week), but when you are going for the
dummy package removal, I suggest you try this: run aptitude in
interactive mode, select the dummy packages to remove, press 'g'. You
will have a screen with a summary of what packages are going to be
removed, which most likely will include most of TDE packages (based on
your mail) as "autodependency (A)". Mark tdebase, tdelibs and all other
"general" tde packages as "keep". This should possibly keep most of
TDE
installed, while allowing you to remove those dummy packages.
Hi Michele,
I've been trying to figure out a simple way to protect
inexperienced users.
The safest approach I've found thus far is:
apt-get update
apt-get install tde-trinity
apt-get dist-upgrade
This is for Debian. Ubuntu may need a different second
step just as initial installs are different for Ubuntu.
I also tried this with aptitude but aptitude goes crazy.
--Mike
12 Dec
12 Dec
1:02 a.m.
New subject: [trinity-devel] Package renames and autoremove
On 12/11/2014 06:58 PM, Mike Bird wrote:
I've been trying to figure out a simple way to
protect
inexperienced users.
The safest approach I've found thus far is:
apt-get update
apt-get install tde-trinity
apt-get dist-upgrade
This is for Debian. Ubuntu may need a different second
step just as initial installs are different for Ubuntu.
I also tried this with aptitude but aptitude goes crazy.
--Mike
Thanks Mike, I agree with you that we need to find an easy and reproducible way to update,
then we can add an "update
from v3.5.13.2" to the wiki on the website.
Interesting is the fact that you and Slavek found different "good way", i.e.
Slavek had problem with apt-get while you
have problem with aptitude.
I am going to try both ways myself as well, then let's see what's the best we can
come up with.
Thanks for the feedback so far.
Cheers
Michele
1:29 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Friday 12 of December 2014 02:02:27 Michele Calgaro wrote:
On 12/11/2014 06:58 PM, Mike Bird wrote:
If I understand correctly, Mike did not have a problem with aptitude during
the upgrade, but only after upgrade when he tried to remove the original
kde-trinity / kde-core-trinity / kde-devel-trinity without also installed
their successors tde-trinity / tde-core-trinity / tde-devel-trinity.
While in my tests were fundamental problems during the upgrade with apt-get.
--
Slávek
I've been trying to figure out a simple way
to protect
inexperienced users.
The safest approach I've found thus far is:
apt-get update
apt-get install tde-trinity
apt-get dist-upgrade
This is for Debian. Ubuntu may need a different second
step just as initial installs are different for Ubuntu.
I also tried this with aptitude but aptitude goes crazy.
--Mike
Thanks Mike, I agree with you that we need to find an easy and reproducible
way to update, then we can add an "update from v3.5.13.2" to the wiki on
the website.
Interesting is the fact that you and Slavek found different "good way",
i.e. Slavek had problem with apt-get while you have problem with aptitude.
I am going to try both ways myself as well, then let's see what's the best
we can come up with. Thanks for the feedback so far.
Cheers
Michele
2:08 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Thu December 11 2014 17:29:10 Slávek Banko wrote:
If I understand correctly, Mike did not have a problem
with aptitude during
the upgrade, but only after upgrade when he tried to remove the original
kde-trinity / kde-core-trinity / kde-devel-trinity without also installed
their successors tde-trinity / tde-core-trinity / tde-devel-trinity.
While in my tests were fundamental problems during the upgrade with
apt-get.
That's correct. I don't know yet if the missing Conflicts which caused
a problem for apt-get is fixed in R14 Final.
There is something newer on the master server and now mirroring to
Copernicus that I could test but I don't yet know if it has finished
building.
--Mike
2:21 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Friday 12 of December 2014 03:08:02 Mike Bird wrote:
On Thu December 11 2014 17:29:10 Slávek Banko wrote:
For information, Conflicts is not missing - is present from November 25 -
commit 69b99797 (tde-packaging). But despite this Conflicts I observed
problems when using apt-get.
--
Slávek
If I understand correctly, Mike did not have a
problem with aptitude
during the upgrade, but only after upgrade when he tried to remove the
original kde-trinity / kde-core-trinity / kde-devel-trinity without also
installed their successors tde-trinity / tde-core-trinity /
tde-devel-trinity.
While in my tests were fundamental problems during the upgrade with
apt-get.
That's correct. I don't know yet if the missing Conflicts which caused
a problem for apt-get is fixed in R14 Final.
There is something newer on the master server and now mirroring to
Copernicus that I could test but I don't yet know if it has finished
building.
--Mike
2:42 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Thu December 11 2014 18:21:51 Slávek Banko wrote:
For information, Conflicts is not missing - is present
from November 25 -
commit 69b99797 (tde-packaging). But despite this Conflicts I observed
problems when using apt-get.
In roughly a dozen R14 RC2 test "apt-get dist-upgrade" from 3.5.13.2
I did not encounter the problem you had already fixed in 69b99797.
What I did encounter was the problem reported in bug 2245 for which
Michele suggested a fix in comment 2.
--Mike
3:51 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Friday 12 of December 2014 03:42:47 Mike Bird wrote:
On Thu December 11 2014 18:21:51 Slávek Banko wrote:
Moment, I do not understand here. In one sentence you say that you're not
encounter the problem solved by commit 69b99797, but then you say that you
encounter a problem described in bug 2245. But bug 2245 is just the problem
what "should" solve Conflict, which was set in commit 69b99797 :)
I reported that with apt-get upgrade just does not work correctly. So if I
understand correctly, you now confirm the same thing - that with apt-get
upgrade does not work properly. As I have right now tested, for solving
problem also for apt-get would probably suffice modify version to one from
the following:
<= 4:3.5.13.2+
<< 4:3.5.13.3~
<< 4:14.0.0~ (as suggested by Michele)
Tim, now it is probably too late for rebuild and publishing?
--
Slávek
For information, Conflicts is not missing - is
present from November 25 -
commit 69b99797 (tde-packaging). But despite this Conflicts I observed
problems when using apt-get.
In roughly a dozen R14 RC2 test "apt-get dist-upgrade" from 3.5.13.2
I did not encounter the problem you had already fixed in 69b99797.
What I did encounter was the problem reported in bug 2245 for which
Michele suggested a fix in comment 2.
--Mike
4:24 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Thu December 11 2014 19:51:46 Slávek Banko wrote:
Moment, I do not understand here. In one sentence you
say that you're not
encounter the problem solved by commit 69b99797, but then you say that you
encounter a problem described in bug 2245. But bug 2245 is just the problem
what "should" solve Conflict, which was set in commit 69b99797 :)
Maybe I misunderstand 69b99797 but it looks like a fix for the
packaging of libtdepim1a-trinity and libtdepim1-trinity-dev for
just three distros - Lenny, Squeeze, and Maverick - whereas bug
2245 concerns the packaging of tdelibs-data-trinity and my
testing has been exclusively with Wheezy and it looks like you
originally filed bug 2245 based on a problem with Wheezy.
--Mike
4:29 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Friday 12 of December 2014 05:24:20 Mike Bird wrote:
On Thu December 11 2014 19:51:46 Slávek Banko wrote:
Yeah, good point - should be mentioned commit eec4bd7f - November 17.
Perhaps I should go to sleep :)
--
Slávek
Moment, I do not understand here. In one sentence
you say that you're not
encounter the problem solved by commit 69b99797, but then you say that
you encounter a problem described in bug 2245. But bug 2245 is just the
problem what "should" solve Conflict, which was set in commit 69b99797 :)
Maybe I misunderstand 69b99797 but it looks like a fix for the
packaging of libtdepim1a-trinity and libtdepim1-trinity-dev for
just three distros - Lenny, Squeeze, and Maverick - whereas bug
2245 concerns the packaging of tdelibs-data-trinity and my
testing has been exclusively with Wheezy and it looks like you
originally filed bug 2245 based on a problem with Wheezy.
--Mike
4:39 a.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
On Thu December 11 2014 19:51:46 Slávek Banko wrote:
The structure of our Debian/Ubuntu packaging tree is that all Ubuntu
distributions are symlinked to the "maverick" folder, while all Debian
distributions are symlinked to the "squeeze" folder. This is due to the
fact that, at least for now, one set of packaging files works on all
supported versions. In the future this may change, hence the reason for
keeping the distribution names instead of one large "debian" or
"ubuntu"
folder.
Tim
Moment, I do not understand here. In one sentence
you say that you're
not
encounter the problem solved by commit 69b99797, but then you say that
you
encounter a problem described in bug 2245. But bug 2245 is just the
problem
what "should" solve Conflict, which was set in commit 69b99797 :)
Maybe I misunderstand 69b99797 but it looks like a fix for the
packaging of libtdepim1a-trinity and libtdepim1-trinity-dev for
just three distros - Lenny, Squeeze, and Maverick - whereas bug
2245 concerns the packaging of tdelibs-data-trinity and my
testing has been exclusively with Wheezy and it looks like you
originally filed bug 2245 based on a problem with Wheezy.
--Mike -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlSKcWQACgkQLaxZSoRZrGE+0gDgsrluUIokakjTE1BsiNpmRgaj
vrldlavC/5ndogDdHPNvxF6OBxGia8D/6oIFR/0l1b9vYMkTsRrGlg==
=ovJn
-----END PGP SIGNATURE-----
17 Dec
17 Dec
3:53 a.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2014/12/11 06:58 PM, Mike Bird wrote:
On Thu December 11 2014 01:47:03 Michele Calgaro
wrote:
Mike, Slavek, Tim,
I am doing testing on upgrading from 3.5.13.2 to R14.0.0 on a default
Wheezy installation. Using the "installation" instructions on the wiki
page fails, so we will probably need to update those pages and
differentiate between "new install" and "upgrade".
Given the slowness of package transfer (I am using the official
packages, not my own build, to avoid any possible mistake), I am still
testing various ways. I will update again later on.
Cheers
Michele
I haven't (yet) tried an upgrade from
3.5.13.2 to r14.0.0 myself
(I will have to test on a VM sometime next week), but when you
are going for the dummy package removal, I suggest you try this:
run aptitude in interactive mode, select the dummy packages to
remove, press 'g'. You will have a screen with a summary of what
packages are going to be removed, which most likely will include
most of TDE packages (based on your mail) as "autodependency
(A)". Mark tdebase, tdelibs and all other "general" tde packages
as "keep". This should possibly keep most of TDE installed, while
allowing you to remove those dummy packages.
Hi Michele,
I've been trying to figure out a simple way to protect
inexperienced users.
The safest approach I've found thus far is:
apt-get update apt-get install tde-trinity apt-get dist-upgrade
This is for Debian. Ubuntu may need a different second step just
as initial installs are different for Ubuntu.
I also tried this with aptitude but aptitude goes crazy.
--Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJUkP5UAAoJECp1t8qK3tXPDCUQALIOQiCWrzcDipJRMXwb4wmq
09+cA9O/jz/8LAmmk4QftwLWQL2lPtjdX8Lv7rlXOXueYpRHaZ3zkFbCaBNJAo4I
yTIOYGvwW+sVwKRoyn4QJOEIZvNzPQeqKaMB+QT0xfg3reaLCNL3alv4KBxUKs96
WFvZXvuAN0IiQwcsvepe6Z1bLijA9rkfsiWLUulbA5sqDgud6OaX3Aq0aciKXqsG
2o8eQPid+Zr+LArSEU850I63BjgVAvVuA9q/udWdrawG6AYb6HUgndNmb2IPS1Wt
YBNaMEYI4a37te1yhEKtKmwhtozJYx+E3ZS3k1hM/+wn/pNSHlv3ihsx/sV+mjki
gzUU1ZkXUCMJYEJOLS5YcIHdLBvCeDhtOcLa1vgY8y4STBn+lrmWB4j2iBoJIESK
KN2XULyo4lWGfvYrlNo0TtmP15OiG7Ckg8VmS5jscBH8RWhtm5oxGU4YkyN1cNur
KpgSnOuoxNbqTlq5IqZWDy+q2UOTwEmnwO/R4HZUvJSAHL5hjhPcbQB+pn6sXRho
MDs4h82D1IEhU4PaVyCWpLOtrEZNlzYTV//GG5OolbFVCfQT00B42tDnc19XRxRH
9yMY/RuupvbVfZyfAv11ntHxBtn3rjH8tQ/JdCqqSO8s25c76TjHtbDIVDuqfnfu
+vsGojMiE5D/Lh5F0kuo
=ZNMK
-----END PGP SIGNATURE-----
21 Dec
21 Dec
9:31 a.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2014/12/11 06:58 PM, Mike Bird wrote:
On Thu December 11 2014 01:47:03 Michele Calgaro
wrote:
If seems the download from the server/mirrors is more reliable now. I
gave up testing for a few days, but now it seems that the download is
(although slowly) progressing without timeout, 509 bandwidth
limitiation or error of sort. It is stalls occasionaly, but a stop-go
will resume it.
Cheers
Michele
I haven't (yet) tried an upgrade from
3.5.13.2 to r14.0.0 myself
(I will have to test on a VM sometime next week), but when you
are going for the dummy package removal, I suggest you try this:
run aptitude in interactive mode, select the dummy packages to
remove, press 'g'. You will have a screen with a summary of what
packages are going to be removed, which most likely will include
most of TDE packages (based on your mail) as "autodependency
(A)". Mark tdebase, tdelibs and all other "general" tde packages
as "keep". This should possibly keep most of TDE installed, while
allowing you to remove those dummy packages.
Hi Michele,
I've been trying to figure out a simple way to protect
inexperienced users.
The safest approach I've found thus far is:
apt-get update apt-get install tde-trinity apt-get dist-upgrade
This is for Debian. Ubuntu may need a different second step just
as initial installs are different for Ubuntu.
I also tried this with aptitude but aptitude goes crazy.
--Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJUlpN/AAoJECp1t8qK3tXP8K4QAMiy5fwQdP43t+3lJSpeueZe
o4PDVtx7v1aRWEjStSGNpNPu6B+7QGbkV7ZHNneVTAlwLORiheTvbKfxiKWMnVKR
x19ZzkKSsUYMa6w70zGdkCGKZIhc9JX2xpi+syEGsPelQQxE7jjeZ1F1498vcvEF
leF0sjfya62K5FgkLh4FhOb1nU7xkTxhbFb3sL/XWhEm//bDaLrI7oya0M9yk9U9
WanWi7g9a8UKanEjAGH+bBIks2874LIats7PoXUqhdeeMALykfUDu+f433Bb2YnC
xZnK+XZr6xcJpzJK/HWb9TtiPzBHYe0nfiCl2ZCwn0otRTTuco5xSY4cFvwFXcYh
0zCBGSU+ojI8auyoQFtahMBrwiUt8ipAX6KnJK9cLwRJEaqgY7aDk+H6mMMFKYlp
z78PeFYvoS85PLvp7VhYdP/FLyug5eDZ42bu6urWLRkJ5nnHRGu71kVKh00eHf6D
BguSyL3jr1uzkLDdKPFieQBJde6mo8U6gNzSJ9bBKKo3yX+y5wmbgawFoaGyyqBa
/rVkq6uIE3ay1RVe2FOkpNkbFO9QI3iGZb1xS3llLE3Kgce1PuJJ9RcS2Te4JYUI
wL3/t/EvSKLW37tScVWyz+gsj8JbXvMG9TUs4BUd+i4BFuuVf+Uk/0x1/rUAB8MG
Lq17AF6bAySE3qSGmh7W
=Jzgs
-----END PGP SIGNATURE-----
22 Dec
22 Dec
10:06 a.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2014/12/11 06:58 PM, Mike Bird wrote:
On Thu December 11 2014 01:47:03 Michele Calgaro
wrote:
Looks like the mirror is now fully working, since it takes less than
30 minutes to do a fully upgrade. So I have tested sevaral ways to
upgrade from a standard 3.5.13.2 install to 14.0.0.
The sequence suggested by Mike seems to be the most
reliable/reproducable, but with some tweeks.
1) apt-get update
2) apt-get install tde-trinity.
This fails at some point.
3) apt-get -f install.
This succeeded, but trying to login after this stage gives the error
"Could not start kstartupconfig...."
4) apt-get dist-upgrade
After this stage, I have a fully working TDE R14.0.0 system.
Running aptitude in CLI mode and pressing 'g', comes up with a list
of packages that can be deleted. This at times is most of the TDE
installation. To fix this do the following.
5) run 'aptitude', search tde-trinity (which should be shown as
*un*installed, mark as 'to install' and 'g'. This will make R14.0.0
stick in your system
6) running 'aptitude' and pressing 'g' again, comes up with a list of
packages that can be deleted. Proceed.
I have noticed over several upgrade runs, that the list of packages
that can be deleted is not always the same, not sure why although some
of the upgrade run were interrupted/resumed several times due to the
slow download bandwidth of previous days.
It seems that dummy packages have to be manually removed.
dpkg -l | grep -i dummy
gives a list of such packages.
I will modify the installation instructions adding an "Update from
3.5.13.2" section to it. If you have any specific comments that you
would like to add to the above, please let me know (once again :-) )
Cheers
Michele
I haven't (yet) tried an upgrade from
3.5.13.2 to r14.0.0 myself
(I will have to test on a VM sometime next week), but when you
are going for the dummy package removal, I suggest you try this:
run aptitude in interactive mode, select the dummy packages to
remove, press 'g'. You will have a screen with a summary of what
packages are going to be removed, which most likely will include
most of TDE packages (based on your mail) as "autodependency
(A)". Mark tdebase, tdelibs and all other "general" tde packages
as "keep". This should possibly keep most of TDE installed, while
allowing you to remove those dummy packages.
Hi Michele,
I've been trying to figure out a simple way to protect
inexperienced users.
The safest approach I've found thus far is:
apt-get update apt-get install tde-trinity apt-get dist-upgrade
This is for Debian. Ubuntu may need a different second step just
as initial installs are different for Ubuntu.
I also tried this with aptitude but aptitude goes crazy.
--Mike -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJUl+0bAAoJECp1t8qK3tXPXpAQAMPQOog25GsKqE7MBcSBSgu2
2J6ifvTaJHQrK+r0JYZe4Jc4h1ZfCF5vG/DDn2pDzsEwZl1r6WcBW2Ijb/vIg7Bo
rSQLiKI/rwItWL0ff/FRuP7LhJyVYxKq+7Soz2r81f1FnjGH9hsrGRNY5MbYe3tL
8cKkAklHCcD/IwpVvaNZZFGJgJIdLZMbRg/Pn4lIfPLwbLedyTF0L8HbNDxwQi1G
rvr2u6/LAnqCR3DlUSt5s5ptyNRhNg/xAbwK47s6ljcwhV/hAh8F5GeK0XKT3fNu
8K9SNxHexMn5BrgquooFfWQG/HAtbPDsb59GwBBfgeFEOpqFl51Pt9ckpJ3goAcz
YV2bje3aiUnJFvJReNBg8KTBE/FXZIeUlj5eAWwmfFvnQogDZzES0IYvGa06EXMH
+lJJmlA3Tx5fiB01WoZivBJG7m9YRGzWTp6MPu2IhzmSwqdLxE2FAxh+4YHx2R5Y
HhBhfZcZf6fMHM8rSinSBz8AlRlIIX2lLNtInP4lnQ7nuJCKqyPbMepfm4YckDWS
EKVBub/2777U6llwkoOCED5TNVjTQpbCex0CF8diAMENeTuhYVGmDl8zID9R6TRR
d4xtZWNH8mU19oHXmAWX7jxWG2ip/Shz9SnqwKmRuyN0sJF7TLVOSBkiEYJsKGIU
QYAtdRYrO8wgHrGVXh4G
=gNaz
-----END PGP SIGNATURE-----
10:26 a.m.
New subject: [trinity-devel] Package renames and autoremove
On Monday 22 of December 2014 11:06:20 Michele Calgaro wrote:
Looks like the mirror is now fully working, since it
takes less than
30 minutes to do a fully upgrade. So I have tested sevaral ways to
upgrade from a standard 3.5.13.2 install to 14.0.0.
The sequence suggested by Mike seems to be the most
reliable/reproducable, but with some tweeks.
1) apt-get update
2) apt-get install tde-trinity.
This fails at some point.
3) apt-get -f install.
This succeeded, but trying to login after this stage gives the error
"Could not start kstartupconfig...."
4) apt-get dist-upgrade
After this stage, I have a fully working TDE R14.0.0 system.
Running aptitude in CLI mode and pressing 'g', comes up with a list
of packages that can be deleted. This at times is most of the TDE
installation. To fix this do the following.
5) run 'aptitude', search tde-trinity (which should be shown as
*un*installed, mark as 'to install' and 'g'. This will make R14.0.0
stick in your system
6) running 'aptitude' and pressing 'g' again, comes up with a list of
packages that can be deleted. Proceed.
I have noticed over several upgrade runs, that the list of packages
that can be deleted is not always the same, not sure why although some
of the upgrade run were interrupted/resumed several times due to the
slow download bandwidth of previous days.
It seems that dummy packages have to be manually removed.
dpkg -l | grep -i dummy
gives a list of such packages.
I will modify the installation instructions adding an "Update from
3.5.13.2" section to it. If you have any specific comments that you
would like to add to the above, please let me know (once again :-) )
Cheers
Michele
I must again point out - if the user perform a manual selection of packages to
install, the process containing "apt-get install tde-trinity" is not an just
upgrade, but will install many other packages. Moreover, as you mention, this
step fails. That does not sound like a good way to upgrade.
Please, test this simple procedure:
1) apt-get update
2) aptitude dist-upgrade
As I've mentioned many times before, this procedure on all my test machines
ran smoothly - without any hitch - and it's "really just upgrade".
--
Slávek
5:33 p.m.
New subject: [trinity-devel] Package renames and autoremove
On Mon December 22 2014 02:26:11 Slávek Banko wrote:
As I've mentioned many times before, this
procedure on all my test machines
ran smoothly - without any hitch - and it's "really just upgrade".
Agreed that would be good, but what in your configuration
prevents autoremove from removing needed packages?
Did you originally perform a standard TDE install or did
you perform some kind of expert install that told aptitude
more about which packages you want to keep?
--Mike
6:57 p.m.
New subject: [trinity-devel] Package renames and autoremove
On Monday 22 of December 2014 18:33:06 Mike Bird wrote:
On Mon December 22 2014 02:26:11 Slávek Banko wrote:
On my usual machines I have installed only such packages that I need - without
use of metapackages. On the test machine with Ubuntu I used TDE LiveCD -
tde-3.5.13.2-ubuntu-12.04.2 - here is used metapackage trinity-livecd.
On my test machine with Debian Squeeze is therefore the difference
between 'apt-get install tde-trinity' and 'aptitude dist-upgrade'
abysmal:
apt-get install tde-trinity:
72 upgraded, 456 newly installed, 1 to remove and 31 not upgraded.
Need to get 339 MB of archives.
After this operation, 687 MB of additional disk space will be used.
aptitude dist-upgrade:
92 packages upgraded, 64 newly installed, 15 to remove and 0 not upgraded.
Need to get 137 MB of archives. After unpacking 63.8 MB will be used.
--
Slávek
As I've mentioned many times before, this
procedure on all my test
machines ran smoothly - without any hitch - and it's "really just
upgrade".
Agreed that would be good, but what in your configuration
prevents autoremove from removing needed packages?
Did you originally perform a standard TDE install or did
you perform some kind of expert install that told aptitude
more about which packages you want to keep?
--Mike
23 Dec
23 Dec
4:28 a.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/22/2014 07:26 PM, Slávek Banko wrote:
Please, test this simple procedure:
1) apt-get update 2) aptitude dist-upgrade
Ok, will test later and report back.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJUmO9dAAoJECp1t8qK3tXPpuYP/1pqCUhnHjSn8LGAQyuMo/va
Zuf41bcKmByp3ZspKc5o9i5Xf+W+1XgYuCE0NkKezDRsQf3K9/OjCS37q0qb5rgg
7exEkabU6ctk50o3+Jbw+yX4uE7vXH4EDkBa+s94B7haxquIMgBDFfEU7cl7pC/s
Pq77sLe6GtvmxfcLIqFOrqb2gQzBEdl1h18yd6lKv/zl5Nrap0kndc40J63aFPRo
4EiuGv5djCCG+pU7zfih3b9gtqHdELbd+PHMVvZ+d1kOr4tdf1oOqU6/MxFFxJpu
J7/bUzYjwGeZmnA0TP7dV4QMmdhiAD158q3ftRCnsrs4hPrKqV+vzWCAeHM8gJsJ
/Qi7+kn0uVbHNQbTmUbTlxnxqs+p6s8OUvK+MOPHUUTAN4+RApawHdbdt0gPT/Th
BvKeA9g0dmDrU86gIE1wbRZJTrQWi1zhQoWJTyewYKTaz33Ft1HhZ6/hAZUwwmRw
K4NlvGy/JpIp9KgLmX3i64rkXRNVvpC8c3+pUzL8aTNX4jZQ8wp40Oc17W0LsT/w
HpVAdXIS1iaTL74qvj3o1rYiIkuziNhtujYTm5nJCEHAxZdF1oBCb4f7wUYAS+Vb
X/ph7pka5BhEMQrbrdUuH0L7VRRX/EL/k8bpD1HZnwZ16d7kz9utg4+VYeCrC1tf
GGvJZ8pQZCcJwPfx7p3h
=jVV1
-----END PGP SIGNATURE-----
8:11 a.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2014/12/22 07:26 PM, Slávek Banko wrote:
On Monday 22 of December 2014 11:06:20 Michele Calgaro
wrote:
packages to
Looks like the mirror is now fully working, since
it takes less
than 30 minutes to do a fully upgrade. So I have tested sevaral
ways to upgrade from a standard 3.5.13.2 install to 14.0.0. The
sequence suggested by Mike seems to be the most
reliable/reproducable, but with some tweeks. 1) apt-get update 2)
apt-get install tde-trinity. This fails at some point. 3) apt-get
-f install. This succeeded, but trying to login after this stage
gives the error "Could not start kstartupconfig...." 4) apt-get
dist-upgrade After this stage, I have a fully working TDE R14.0.0
system. Running aptitude in CLI mode and pressing 'g', comes up
with a list of packages that can be deleted. This at times is
most of the TDE installation. To fix this do the following. 5)
run 'aptitude', search tde-trinity (which should be shown as
*un*installed, mark as 'to install' and 'g'. This will make
R14.0.0 stick in your system 6) running 'aptitude' and pressing
'g' again, comes up with a list of packages that can be deleted.
Proceed.
I have noticed over several upgrade runs, that the list of
packages that can be deleted is not always the same, not sure why
although some of the upgrade run were interrupted/resumed several
times due to the slow download bandwidth of previous days. It
seems that dummy packages have to be manually removed. dpkg -l |
grep -i dummy gives a list of such packages.
I will modify the installation instructions adding an "Update
from 3.5.13.2" section to it. If you have any specific comments
that you would like to add to the above, please let me know (once
again :-) )
Cheers Michele
I must again point out - if the user perform a manual selection of
install, the process containing "apt-get install
tde-trinity" is
not
an just
upgrade, but will install many other packages.
Moreover, as you
mention, this
step fails. That does not sound like a good way to
upgrade.
Please, test this simple procedure:
1) apt-get update 2) aptitude dist-upgrade
As I've mentioned many times before, this procedure on all my test
machines
ran smoothly - without any hitch - and it's
"really just upgrade".
Slavek,
I tested your way and the upgrade goes smooth. Nevertheless after the
process is completed a lot of dummy packages are still installed. Using
the following procedure gets rid of those dummy packages and leaves a
clean upgrade.
1) apt-get update
2) aptitude dist-upgrade
3) aptitude install tde-trinity -> then choose to resolve the conflict
by removing kde-trinity and kde-core-trinity
Can you test on your machines as well and let me know? If confirmed, I
will update the installation instructions.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJUmSPJAAoJECp1t8qK3tXPds0QAKgwCURrF2wopNLayGmDrusm
FOw91SgmAMRMHNU6Dy1IERc8SM6c8SSSgajZy1O3Wz6kISiQnU9iQF/F4MK0bKmH
B617En+cZkHe2hqbPk6QDBLXcvb9QBBd7s7hX/6EPFUoZ7y+6HRQ+uOv3oA41X+q
rQXjVG8eQb0nKjGjfkcevK0Hz26eDqX9dqXfKc6SK6LM3ca/+Wt7c5ukfNabXpg+
NaSxZJ/9kenPXHLWRMZDRVG+dQtQ3pWQVSaTiK5rSQ/ahgMO85QpYd9P+3ScsOT3
jVP/HYWtEcZjyplI623EKYgHob3QIyAuCYsk5ONL8juB+BvZSuAdfuTKA8HkSNTh
IW//DEaZNKRilMcOAKz018hUOpLZJfqOad8YGfxlPaE1NGCLcdU0qBgWLR3yA66M
gEAStMEtnoenLuwZwEYN/0PjPlv/RlUqRfpJiRlGGXEGSlMJoQj8jbEG9wMTYyj9
zDrGd5b7ZDNgobWJvoyPea5fBKIlMh90B21ECx34l4/DGPaXaHCd5nHdgY/CE9jn
hMmMB/vWFQD7G0mmDcKAgWVF3FmUWq2whPaK9CiPBWxbg4X9Kqq7QoNQYhC7oanl
KpTpirdIh0b2009IgkWm+fR40ELlYdYQP5cJpTPM80fiel3r+NkzN+ZIXxcCb4Np
Zcg+OhrWZTZrs0O0LShJ
=q8rf
-----END PGP SIGNATURE-----
9:02 p.m.
New subject: [trinity-devel] Package renames and autoremove
Hi Michele,
I think the answer is that for people who had in the past
done a standard Trinity install they should include the
"apt-get install tde-trinity" step to avoid autoremove
problems but that for experts such as Slávek who have
customized their installations and understand the
consequences then they can skip that step.
--Mike
24 Dec
24 Dec
6:48 a.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/24/2014 06:02 AM, Mike Bird wrote:
Hi Michele,
I think the answer is that for people who had in the past done a standard Trinity install
they should include the
"apt-get install tde-trinity" step to avoid autoremove problems but that for
experts such as Slávek who have
customized their installations and understand the consequences then they can skip that
step.
--Mike
Thanks Mike, makes a lot of sense. After all we are looking at providing a
procedure for "standard" users :-)
I will just wait for Slavek's test result first, since I understand that it can tests
repeatedly on the same computer.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJUmmG6AAoJECp1t8qK3tXP+lMQALV4rEwe88rExXneLhLyB+at
DvMVauGlOMt3PnbBpdxkGqlQTJ7R5vhNsekLSEyT3ttVnIXIVKvTLp3yYnDWXjx3
UcEI4kyudoHmUSzAcRY/0TNTUkw0XRxLVv/n+nJe1By2fIo6V395VzY83OANajsn
mgVbRMFcn2KHGVS97jmPV2AEcgPqhlmDOclakDKz4fC8kGq6xFtwjh4x3MQxS9lL
HsswkFx4pTi8+uDRIkWhMlgSmTnqUrFvHt8Wg++5QRPOghYfug7Mmpf3uTwDVo4h
J3H8xGToX+kcMP+RyaNTMZ2jtTPznRdfkpCV8c1HdhP+yH45Lw6eDf2yySAlH1Gv
8eHIgCjyixMUuiawu5KbBLwOHIhE5DVNEqDAEKbFeo4itCkE3lRoacPset4jJ6FH
PwJwhu5C3nywzuDarT9JxrHYKYDflrc6pKaoXvtJQcbs9LEP7D1EJYsbS6WoJJT4
jm2adcSzTGKdSrD0RBtWcfQ3jWnzoJOfDcPpqXlaWelaXWHq0XEd56X2shlvPaCw
nIU8kKP2OlQd210hNGXjZjdcjm+Of0Q1FueYauK2MyRKO4SfdUkqbiPn4QqhduMk
x+jieQokTlU+ZiUjVeeXSP4GFQCkm94eXg83IlOGSL7W1Y6Ml5Gw1EuFBgh9s4F3
BdFQi4LemJk9YlDVBw+U
=blhN
-----END PGP SIGNATURE-----
25 Dec
25 Dec
6:53 p.m.
New subject: [trinity-devel] Package renames and autoremove
On Wednesday 24 of December 2014 07:48:26 Michele Calgaro wrote:
On 12/24/2014 06:02 AM, Mike Bird wrote:
Yes, that's right - thanks to the use aufs I can run test on the same computer
again and again and again :)
--
Slávek
Hi Michele,
I think the answer is that for people who had in the past done a standard
Trinity install they should include the "apt-get install tde-trinity"
step to avoid autoremove problems but that for experts such as Slávek who
have customized their installations and understand the consequences then
they can skip that step.
--Mike
Thanks Mike, makes a lot of sense. After all we are looking at providing a
procedure for "standard" users :-) I will just wait for Slavek's test
result first, since I understand that it can tests repeatedly on the same
computer. Cheers
Michele
7:26 p.m.
New subject: [trinity-devel] Package renames and autoremove
On Tuesday 23 of December 2014 09:11:53 Michele Calgaro wrote:
On 2014/12/22 07:26 PM, Slávek Banko wrote:
No problems.
On Monday 22 of December 2014 11:06:20 Michele
Calgaro wrote:
packages to
Looks like the mirror is now fully working, since
it takes less
than 30 minutes to do a fully upgrade. So I have tested sevaral
ways to upgrade from a standard 3.5.13.2 install to 14.0.0. The
sequence suggested by Mike seems to be the most
reliable/reproducable, but with some tweeks. 1) apt-get update 2)
apt-get install tde-trinity. This fails at some point. 3) apt-get
-f install. This succeeded, but trying to login after this stage
gives the error "Could not start kstartupconfig...." 4) apt-get
dist-upgrade After this stage, I have a fully working TDE R14.0.0
system. Running aptitude in CLI mode and pressing 'g', comes up
with a list of packages that can be deleted. This at times is
most of the TDE installation. To fix this do the following. 5)
run 'aptitude', search tde-trinity (which should be shown as
*un*installed, mark as 'to install' and 'g'. This will make
R14.0.0 stick in your system 6) running 'aptitude' and pressing
'g' again, comes up with a list of packages that can be deleted.
Proceed.
I have noticed over several upgrade runs, that the list of
packages that can be deleted is not always the same, not sure why
although some of the upgrade run were interrupted/resumed several
times due to the slow download bandwidth of previous days. It
seems that dummy packages have to be manually removed. dpkg -l |
grep -i dummy gives a list of such packages.
I will modify the installation instructions adding an "Update
from 3.5.13.2" section to it. If you have any specific comments
that you would like to add to the above, please let me know (once
again :-) )
Cheers Michele
I must again point out - if the user perform a manual selection of install, the process containing "apt-get
install tde-trinity" is
not
an just
upgrade, but will install many other packages.
Moreover, as you
mention, this
step fails. That does not sound like a good way
to upgrade.
Please, test this simple procedure:
1) apt-get update 2) aptitude dist-upgrade
As I've mentioned many times before, this procedure on all my test
machines
ran smoothly - without any hitch - and it's
"really just upgrade".
Slavek,
I tested your way and the upgrade goes smooth. Nevertheless after the
process is completed a lot of dummy packages are still installed. Using
the following procedure gets rid of those dummy packages and leaves a
clean upgrade.
1) apt-get update 2) aptitude dist-upgrade
96 packages upgraded, 64 newly installed, 15 to remove and 0 not upgraded.
Need to get 147 MB of archives. After unpacking 63.7 MB will be used.
No problems.
3) aptitude install tde-trinity -> then choose to
resolve the conflict
by removing kde-trinity and kde-core-trinity
0 packages upgraded, 406 newly installed, 0 to remove and 0 not upgraded.
Need to get 231 MB of archives. After unpacking 626 MB will be used.
Oops, that's a bit much.
I think we could recommend something like this:
If you had installed metapackage kde-trinity, kde-core-trinity or
kde-devel-trinity, these are not updated automatically. For the update is
necessary to use one of the following:
aptitude install tde-trinity
aptitude install tde-core-trinity
aptitude install tde-devel-trinity
As I watched, there are several transitional dummy packages which would still
have had to be removed manually. For example kde-i18n-*, kio-locate,
kradio,... For such I would suggest the following:
4) Run aptitude in interactive mode, enter Limit Display '~i-trinity~ddummy"
and manually check and delete unneeded packages.
Can you test on your machines as well and let me know? If confirmed, I
will update the installation instructions.
Cheers
Michele
--
Slávek
26 Dec
26 Dec
1:25 p.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/26/2014 04:26 AM, Slávek Banko wrote:
Well, "too much" is subjective. Basically the "general" user is trying
to upgrade from a previous kde-install, so this
step is just installing whatever package was not upgraded from step 2.
On my wheezy installation steps 2 install about 250 packages and step 3 about 200 if my
memory is right. The total is
about 450, which is similar to the number you reported on a previous email
(http://trinity-devel.pearsoncomputing.net/?0::14312)
On Tuesday 23 of December 2014 09:11:53 Michele
Calgaro wrote:
Note: only 64 new packages installed.
On 2014/12/22 07:26 PM, Slávek Banko wrote:
No problems.
On Monday 22 of December 2014 11:06:20 Michele
Calgaro wrote:
packages to
Looks like the mirror is now fully working, since
it takes less than 30 minutes to do a fully upgrade. So I
have tested sevaral ways to upgrade from a standard 3.5.13.2 install to 14.0.0. The
sequence suggested by
Mike seems to be the most reliable/reproducable, but with some tweeks. 1) apt-get update
2) apt-get install
tde-trinity. This fails at some point. 3) apt-get -f install. This succeeded, but trying
to login after this
stage gives the error "Could not start kstartupconfig...." 4) apt-get
dist-upgrade After this stage, I have a
fully working TDE R14.0.0 system. Running aptitude in CLI mode and pressing 'g',
comes up with a list of
packages that can be deleted. This at times is most of the TDE installation. To fix this
do the following.
5) run 'aptitude', search tde-trinity (which should be shown as *un*installed,
mark as 'to install' and 'g'.
This will make R14.0.0 stick in your system 6) running 'aptitude' and pressing
'g' again, comes up with a
list of packages that can be deleted. Proceed.
I have noticed over several upgrade runs, that the list of packages that can be deleted
is not always the
same, not sure why although some of the upgrade run were interrupted/resumed several
times due to the slow
download bandwidth of previous days. It seems that dummy packages have to be manually
removed. dpkg -l | grep
-i dummy gives a list of such packages.
I will modify the installation instructions adding an "Update from 3.5.13.2"
section to it. If you have any
specific comments that you would like to add to the above, please let me know (once again
:-) )
Cheers Michele
I must again point out - if the user perform a manual selection of install, the process containing "apt-get
install tde-trinity" is not
an just
upgrade, but will install many other packages.
Moreover, as you
mention, this
step fails. That does not sound like a good way
to upgrade.
Please, test this simple procedure:
1) apt-get update 2) aptitude dist-upgrade
As I've mentioned many times before, this procedure on all my test
machines
ran smoothly - without any hitch - and it's
"really just upgrade".
Slavek, I tested your way and the upgrade goes smooth. Nevertheless after the process is
completed a lot of dummy
packages are still installed. Using the following procedure gets rid of those dummy
packages and leaves a clean
upgrade.
1) apt-get update 2) aptitude dist-upgrade
96 packages upgraded, 64 newly installed, 15 to remove and 0 not upgraded. Need to get
147 MB of archives. After
unpacking 63.7 MB will be used.
No problems. 3) aptitude
install tde-trinity -> then choose to resolve the conflict by removing kde-trinity
and
kde-core-trinity
0 packages upgraded, 406 newly installed, 0 to remove and 0 not upgraded. Need to get 231
MB of archives. After
unpacking 626 MB will be used.
Oops, that's a bit much.
I think we could recommend something like this:
If you had installed metapackage kde-trinity, kde-core-trinity or kde-devel-trinity,
these are not updated
automatically. For the update is necessary to use one of the following:
aptitude install tde-trinity aptitude install tde-core-trinity aptitude install
tde-devel-trinity
As I watched, there are several transitional dummy packages which would still have had to
be removed manually. For
example kde-i18n-*, kio-locate, kradio,... For such I would suggest the following:
4) Run aptitude in interactive mode, enter Limit Display '~i-trinity~ddummy" and
manually check and delete unneeded
packages.
>
> Can you test on your machines as well and let me know? If confirmed, I will update
the installation
> instructions. Cheers Michele
>
What about we propose two possibilities?
1) same as the one I proposed. This one would basically upgrade/install all TDE R14.0.0
and get rid of dummy packages.
This solution would be intended for "generic" users who want a simple way to
upgrade all TDE
2) same solution that you suggested, i.e. step 1 and step 2, then run aptitude in
interactive mode, enter Limit
Display '~i-trinity~ddummy" and manually check/delete unneeded packages and
install equivalent tde packages.
This would be intended for more expert users, who can choose what to install and what
not.
What do you think?
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJUnWHgAAoJECp1t8qK3tXPC3sP/Aj8lSJLMmhNyyHc81lDnp11
h9jWjDwUX9SI4nQzbqv7qvxrYeaA3dYaDxYmSirRdoy3ldfo2l+J7V2bmSM5BrXx
ivEyNbCKgBSwIxSH91doUc91NSbjtCHaWQs3+S5edj+k/V2Own4OWJaMiOov6ejC
0kndMrnkyM3XG1ulDrs8AvwAee9LytABqz4hVazQgpfwSmef/rJH9AoPzLhx9CY+
ls2/s7KBxlSgv/EWnFef1o/Vma5eOKiLkp0UzFaibEoB6tEM1ir/gRgJRVyIzCYx
2v/+aYHriHY5kyGiA6vcXrKe3VCImTNnhscDJkDaS20XYh86ftq4dQDkVmfw6x4k
+4qHRApcZhR4s30/ouoP+ypth1sknSYYeEOdQUK4kj/VBpoxufzvC6LX1VXHdW6f
OkHr6gXjLjSiz0VvtiWrjmPxIyyp3D/2u4CqNGDgPiH+LJsGmERhNhAsE2iM26i/
kMohN4VZaGYmC6YWCB4ONVH2jusWHPLmFgapQnIm0SWSSD3S3ixkZbuoefPTQ27d
7BL8zAaZq/+ubm15jY4MTHS8CiP54PXIkPu5gQI0/BLBzGtfhPSzwvv520S+Idsg
LTzfSUYUq4vgj+pSiJge+VYAWkvndCZDOM2wEIZ5bmHODEeAWXU9mWTpdZOO218d
468R4dNUAVeMSH3ESIFd
=uZg4
-----END PGP SIGNATURE-----
2:36 p.m.
New subject: [trinity-devel] Package renames and autoremove
On Friday 26 of December 2014 14:25:52 Michele Calgaro wrote:
Well, "too much" is subjective. Basically the "general" user is
trying to
upgrade from a previous kde-install, so this step is just installing
whatever package was not upgraded from step 2. On my wheezy installation
steps 2 install about 250 packages and step 3 about 200 if my memory is
right. The total is about 450, which is similar to the number you reported
on a previous email (http://trinity-devel.pearsoncomputing.net/?0::14312)
Essential however is that in step 2 are updated 'all installed' packages.
Regardless of how was installed the previous version of TDE - whether the
packages were selected individually (as is in my case) or meta-package was
used (as are ordinary users). The only packages that are not updated in the
previous step are kde-trinity, kde-core-trinity and kde-devel-trinity ... and
possibly their new dependencies => new packages.
Therefore 406 new packages from my example is simply much, because it causes
installation a lot of packages that "I did not want to have" => I did not
installed intentionally. Therefore my proposal from previous mail to the
reformulation of step 3 to optional => "If you have installed metapackage
kde..." - see paragraph below.
I think that the proposed procedures are not mutually exclusive, but
complementary => no problem to combine it into a single process:
Steps 1) and 2) are identical.
Step 3) is optional => for users that have previously installed meta-packages
kde-trinity / kde-core-trinity / kde-devel-trinity.
Step 4) is optional => for advanced users who wants to do more housekeeping.
--
Slávek
On 12/26/2014 04:26 AM, Slávek Banko wrote:
Yes, 64 is perfectly fine, because on this test machine is not
installed "everything", but substantial and potentially conflicting packages.
On Tuesday 23 of December 2014 09:11:53 Michele
Calgaro wrote:
Note: only 64 new packages installed.
On 2014/12/22 07:26 PM, Slávek Banko wrote:
No problems.
On Monday 22 of December 2014 11:06:20 Michele
Calgaro wrote:
> Looks like the mirror is now fully working, since it takes less than
> 30 minutes to do a fully upgrade. So I have tested sevaral ways to
> upgrade from a standard 3.5.13.2 install to 14.0.0. The sequence
> suggested by Mike seems to be the most reliable/reproducable, but with
> some tweeks. 1) apt-get update 2) apt-get install tde-trinity. This
> fails at some point. 3) apt-get -f install. This succeeded, but trying
> to login after this stage gives the error "Could not start
> kstartupconfig...." 4) apt-get dist-upgrade After this stage, I have a
> fully working TDE R14.0.0 system. Running aptitude in CLI mode and
> pressing 'g', comes up with a list of packages that can be deleted.
> This at times is most of the TDE installation. To fix this do the
> following. 5) run 'aptitude', search tde-trinity (which should be
> shown as *un*installed, mark as 'to install' and 'g'. This will make
> R14.0.0 stick in your system 6) running 'aptitude' and pressing 'g'
> again, comes up with a list of packages that can be deleted. Proceed.
>
> I have noticed over several upgrade runs, that the list of packages
> that can be deleted is not always the same, not sure why although some
> of the upgrade run were interrupted/resumed several times due to the
> slow download bandwidth of previous days. It seems that dummy packages
> have to be manually removed. dpkg -l | grep -i dummy gives a list of
> such packages.
>
> I will modify the installation instructions adding an "Update from
> 3.5.13.2" section to it. If you have any specific comments that you
> would like to add to the above, please let me know (once again :-) )
>
> Cheers Michele
I must again point out - if the user perform a manual selection of
packages to
install, the process containing "apt-get
install tde-trinity" is not
an just
upgrade, but will install many other packages.
Moreover, as you
mention, this
step fails. That does not sound like a good way
to upgrade.
Please, test this simple procedure:
1) apt-get update 2) aptitude dist-upgrade
As I've mentioned many times before, this procedure on all my test
machines
ran smoothly - without any hitch - and it's
"really just upgrade".
Slavek, I tested your way and the upgrade goes smooth. Nevertheless
after the process is completed a lot of dummy packages are still
installed. Using the following procedure gets rid of those dummy
packages and leaves a clean upgrade.
1) apt-get update 2) aptitude dist-upgrade
96 packages upgraded, 64 newly installed, 15 to remove and 0 not
upgraded. Need to get 147 MB of archives. After unpacking 63.7 MB will be
used.
No problems. 3) aptitude install tde-trinity -> then choose to
resolve the conflict
by removing kde-trinity and kde-core-trinity
0 packages upgraded, 406 newly installed, 0 to remove and 0 not upgraded.
Need to get 231 MB of archives. After unpacking 626 MB will be used.
Oops, that's a bit much. I think we
could recommend something like this:
If you had installed metapackage kde-trinity, kde-core-trinity or
kde-devel-trinity, these are not updated automatically. For the update is
necessary to use one of the following:
aptitude install tde-trinity aptitude install tde-core-trinity aptitude
install tde-devel-trinity
As I watched, there are several transitional dummy packages which would
still have had to be removed manually. For example kde-i18n-*,
kio-locate, kradio,... For such I would suggest the following:
4) Run aptitude in interactive mode, enter Limit Display
'~i-trinity~ddummy" and manually check and delete unneeded packages.
> Can you test on your machines as well and let me know? If confirmed, I
> will update the installation instructions. Cheers Michele
What about we propose two possibilities?
1) same as the one I proposed. This one would basically upgrade/install all
TDE R14.0.0 and get rid of dummy packages. This solution would be intended
for "generic" users who want a simple way to upgrade all TDE
2) same solution that you suggested, i.e. step 1 and step 2, then run
aptitude in interactive mode, enter Limit Display '~i-trinity~ddummy" and
manually check/delete unneeded packages and install equivalent tde
packages. This would be intended for more expert users, who can choose what
to install and what not.
What do you think?
Cheers
Michele
27 Dec
27 Dec
1:46 a.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/26/2014 11:36 PM, Slávek Banko wrote:
On Friday 26 of December 2014 14:25:52 Michele Calgaro
wrote:
Well, "too much" is subjective. Basically the "general" user is
trying to upgrade from a previous kde-install, so
this step is just installing whatever package was not upgraded from step 2. On my wheezy
installation steps 2
install about 250 packages and step 3 about 200 if my memory is right. The total is about
450, which is similar
to the number you reported on a previous email
(http://trinity-devel.pearsoncomputing.net/?0::14312)
Essential however is that in step 2 are updated 'all installed' packages.
Regardless of how was installed the
previous version of TDE - whether the packages were selected individually (as is in my
case) or meta-package was
used (as are ordinary users). The only packages that are not updated in the previous step
are kde-trinity,
kde-core-trinity and kde-devel-trinity ... and possibly their new dependencies => new
packages.
Therefore 406 new packages from my example is simply much, because it causes installation
a lot of packages that "I
did not want to have" => I did not installed intentionally. Therefore my proposal
from previous mail to the
reformulation of step 3 to optional => "If you have installed metapackage
kde..." - see paragraph below.
I think that the proposed procedures are not mutually exclusive, but complementary =>
no problem to combine it into
a single process:
Steps 1) and 2) are identical. Step 3) is optional => for users that have previously
installed meta-packages
kde-trinity / kde-core-trinity / kde-devel-trinity. Step 4) is optional => for
advanced users who wants to do more
housekeeping.
Ok, let's settle on this version then. I will update the installation pages early next
week.
Cheers
Michele
On 12/26/2014 04:26 AM, Slávek Banko wrote:
Yes, 64 is perfectly fine, because on this test machine is not installed
"everything", but substantial and
potentially conflicting packages.
On Tuesday 23 of December 2014 09:11:53 Michele
Calgaro wrote:
Note: only 64 new packages installed.
On 2014/12/22 07:26 PM, Slávek Banko wrote:
> On Monday 22 of December 2014 11:06:20 Michele Calgaro wrote:
>> Looks like the mirror is now fully working, since it takes less than 30 minutes
to do a fully upgrade. So
>> I have tested sevaral ways to upgrade from a standard 3.5.13.2 install to 14.0.0.
The sequence suggested
>> by Mike seems to be the most reliable/reproducable, but with some tweeks. 1)
apt-get update 2) apt-get
>> install tde-trinity. This fails at some point. 3) apt-get -f install. This
succeeded, but trying to login
>> after this stage gives the error "Could not start kstartupconfig...."
4) apt-get dist-upgrade After this
>> stage, I have a fully working TDE R14.0.0 system. Running aptitude in CLI mode
and pressing 'g', comes up
>> with a list of packages that can be deleted. This at times is most of the TDE
installation. To fix this
>> do the following. 5) run 'aptitude', search tde-trinity (which should be
shown as *un*installed, mark as
>> 'to install' and 'g'. This will make R14.0.0 stick in your system
6) running 'aptitude' and pressing 'g'
>> again, comes up with a list of packages that can be deleted. Proceed.
>>
>> I have noticed over several upgrade runs, that the list of packages that can be
deleted is not always the
>> same, not sure why although some of the upgrade run were interrupted/resumed
several times due to the
>> slow download bandwidth of previous days. It seems that dummy packages have to be
manually removed. dpkg
>> -l | grep -i dummy gives a list of such packages.
>>
>> I will modify the installation instructions adding an "Update from
3.5.13.2" section to it. If you have
>> any specific comments that you would like to add to the above, please let me know
(once again :-) )
>>
>> Cheers Michele
>
> I must again point out - if the user perform a manual selection of
packages to
> install, the process containing "apt-get install tde-trinity" is not
an just
> upgrade, but will install many other packages. Moreover, as you
mention, this
> step fails. That does not sound like a good way to upgrade.
>
> Please, test this simple procedure:
>
> 1) apt-get update 2) aptitude dist-upgrade
>
> As I've mentioned many times before, this procedure on all my test
machines
> ran smoothly - without any hitch - and it's "really just upgrade".
Slavek, I tested your way and the upgrade goes smooth. Nevertheless after the process is
completed a lot of
dummy packages are still installed. Using the following procedure gets rid of those dummy
packages and leaves
a clean upgrade.
1) apt-get update
No problems.
2) aptitude dist-upgrade
96 packages upgraded, 64 newly installed, 15 to remove and 0 not upgraded. Need to get
147 MB of archives.
After unpacking 63.7 MB will be used.
No problems. 3) aptitude install tde-trinity -> then choose to
resolve the conflict by removing kde-trinity and
kde-core-trinity
0 packages upgraded, 406 newly installed, 0 to remove and 0 not upgraded. Need to get 231
MB of archives. After
unpacking 626 MB will be used.
Oops, that's a bit much. I think
we could recommend something like this:
If you had installed metapackage kde-trinity, kde-core-trinity or kde-devel-trinity,
these are not updated
automatically. For the update is necessary to use one of the following:
aptitude install tde-trinity aptitude install tde-core-trinity aptitude install
tde-devel-trinity
As I watched, there are several transitional dummy packages which would still have had to
be removed manually.
For example kde-i18n-*, kio-locate, kradio,... For such I would suggest the following:
4) Run aptitude in interactive mode, enter Limit Display '~i-trinity~ddummy" and
manually check and delete
unneeded packages.
> Can you test on your machines as well and let me know? If confirmed, I will update
the installation
> instructions. Cheers Michele
What about we propose two possibilities?
1) same as the one I proposed. This one would basically upgrade/install all TDE R14.0.0
and get rid of dummy
packages. This solution would be intended for "generic" users who want a simple
way to upgrade all TDE
2) same solution that you suggested, i.e. step 1 and step 2, then run aptitude in
interactive mode, enter Limit
Display '~i-trinity~ddummy" and manually check/delete unneeded packages and
install equivalent tde packages. This
would be intended for more expert users, who can choose what to install and what not.
What do you think? Cheers Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJUng9tAAoJECp1t8qK3tXPVq8P/iJdcZ12xvRm4IAvJMbRE+c4
Vt1nIn4zpV1wA3zVxKkvU/RcErrEdaIldn2ypEH95+YR5WXhunlSTJyJKYy3FAix
VcG24q1k6XzpDaO5+YpUy2Tsn+lKSta6l6NHMUAlJl7tAwvA1F+IN9gF6mGvXK+0
53EVt51Ncd2pb8PAMQiJt6XiM8a9DOAi8abfuxQueRsrahcIW72bQ5xgsc6lqQYV
gm5zskvg1yVhDWxMGUrOfT0kibDpQ3Dyr8hvWWlxLGSr1qJBfzT7fhcmFOJ+YKsN
N9wEIqMOc3ZIVQpw/LsL8Iyp8vgJM/qmlUFa8a6O2wJhv/OgH9TiAuuveAKmpizJ
+rtgxh+k7K4XZO2qQjOED0tlb1ziQa5Hu/pnnH+JmwrGtPQbztcHZQoohe9kt2wJ
kbfxytMpsb9EwBhm1x/CGeATpn1idlBqDbfitXK4Ozvw+3SnWmXuPyvvWo0qrAfK
T/b2XQMQt3kgJavu+vMYNt0/adoxXmn0oVMRQzuKCXGzbdAAemcodgJEcymKdI+g
sgvSKnlZ8/rkO4Ivigi3b6uz/ZoBwBpcF1Bk59Jf5hz9EoGaGHNPtu1ZVJukRqi7
d+8IBxt8y5+46R5w+iSZ1gcerIwM6mdJ0ADyZdqrPXDNo96xSyJ2m4HYxWMk4Cgi
SQzSwa/4lQ7rRRWHbhrl
=2G9Y
-----END PGP SIGNATURE-----
29 Dec
29 Dec
3:01 a.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/26/2014 11:36 PM, Slávek Banko wrote:
On Friday 26 of December 2014 14:25:52 Michele Calgaro
wrote:
Well, "too much" is subjective. Basically the "general" user is
trying to upgrade from a previous kde-install, so
this step is just installing whatever package was not upgraded from step 2. On my wheezy
installation steps 2
install about 250 packages and step 3 about 200 if my memory is right. The total is about
450, which is similar
to the number you reported on a previous email
(http://trinity-devel.pearsoncomputing.net/?0::14312)
Essential however is that in step 2 are updated 'all installed' packages.
Regardless of how was installed the
previous version of TDE - whether the packages were selected individually (as is in my
case) or meta-package was
used (as are ordinary users). The only packages that are not updated in the previous step
are kde-trinity,
kde-core-trinity and kde-devel-trinity ... and possibly their new dependencies => new
packages.
Therefore 406 new packages from my example is simply much, because it causes installation
a lot of packages that "I
did not want to have" => I did not installed intentionally. Therefore my proposal
from previous mail to the
reformulation of step 3 to optional => "If you have installed metapackage
kde..." - see paragraph below.
I think that the proposed procedures are not mutually exclusive, but complementary =>
no problem to combine it into
a single process:
Steps 1) and 2) are identical. Step 3) is optional => for users that have previously
installed meta-packages
kde-trinity / kde-core-trinity / kde-devel-trinity. Step 4) is optional => for
advanced users who wants to do more
housekeeping.
Slavek,
I have updated both Debian and Ubuntu installation pages on the wiki.
If you compare the "Upgrade" section on both pages, you will see that
"Debian's point A" is not present in the Ubuntu
version. This is because the package names to install TDE in Ubuntu are different from
Debian.
I do not have an Ubuntu system to test on. Could you check and let me know if there is any
error or missing info
regarding the Ubuntu page? Thanks.
Cheers
Michele
On 12/26/2014 04:26 AM, Slávek Banko wrote:
Yes, 64 is perfectly fine, because on this test machine is not installed
"everything", but substantial and
potentially conflicting packages.
On Tuesday 23 of December 2014 09:11:53 Michele
Calgaro wrote:
Note: only 64 new packages installed.
On 2014/12/22 07:26 PM, Slávek Banko wrote:
> On Monday 22 of December 2014 11:06:20 Michele Calgaro wrote:
>> Looks like the mirror is now fully working, since it takes less than 30 minutes
to do a fully upgrade. So
>> I have tested sevaral ways to upgrade from a standard 3.5.13.2 install to 14.0.0.
The sequence suggested
>> by Mike seems to be the most reliable/reproducable, but with some tweeks. 1)
apt-get update 2) apt-get
>> install tde-trinity. This fails at some point. 3) apt-get -f install. This
succeeded, but trying to login
>> after this stage gives the error "Could not start kstartupconfig...."
4) apt-get dist-upgrade After this
>> stage, I have a fully working TDE R14.0.0 system. Running aptitude in CLI mode
and pressing 'g', comes up
>> with a list of packages that can be deleted. This at times is most of the TDE
installation. To fix this
>> do the following. 5) run 'aptitude', search tde-trinity (which should be
shown as *un*installed, mark as
>> 'to install' and 'g'. This will make R14.0.0 stick in your system
6) running 'aptitude' and pressing 'g'
>> again, comes up with a list of packages that can be deleted. Proceed.
>>
>> I have noticed over several upgrade runs, that the list of packages that can be
deleted is not always the
>> same, not sure why although some of the upgrade run were interrupted/resumed
several times due to the
>> slow download bandwidth of previous days. It seems that dummy packages have to be
manually removed. dpkg
>> -l | grep -i dummy gives a list of such packages.
>>
>> I will modify the installation instructions adding an "Update from
3.5.13.2" section to it. If you have
>> any specific comments that you would like to add to the above, please let me know
(once again :-) )
>>
>> Cheers Michele
>
> I must again point out - if the user perform a manual selection of
packages to
> install, the process containing "apt-get install tde-trinity" is not
an just
> upgrade, but will install many other packages. Moreover, as you
mention, this
> step fails. That does not sound like a good way to upgrade.
>
> Please, test this simple procedure:
>
> 1) apt-get update 2) aptitude dist-upgrade
>
> As I've mentioned many times before, this procedure on all my test
machines
> ran smoothly - without any hitch - and it's "really just upgrade".
Slavek, I tested your way and the upgrade goes smooth. Nevertheless after the process is
completed a lot of
dummy packages are still installed. Using the following procedure gets rid of those dummy
packages and leaves
a clean upgrade.
1) apt-get update
No problems.
2) aptitude dist-upgrade
96 packages upgraded, 64 newly installed, 15 to remove and 0 not upgraded. Need to get
147 MB of archives.
After unpacking 63.7 MB will be used.
No problems. 3) aptitude install tde-trinity -> then choose to
resolve the conflict by removing kde-trinity and
kde-core-trinity
0 packages upgraded, 406 newly installed, 0 to remove and 0 not upgraded. Need to get 231
MB of archives. After
unpacking 626 MB will be used.
Oops, that's a bit much. I think
we could recommend something like this:
If you had installed metapackage kde-trinity, kde-core-trinity or kde-devel-trinity,
these are not updated
automatically. For the update is necessary to use one of the following:
aptitude install tde-trinity aptitude install tde-core-trinity aptitude install
tde-devel-trinity
As I watched, there are several transitional dummy packages which would still have had to
be removed manually.
For example kde-i18n-*, kio-locate, kradio,... For such I would suggest the following:
4) Run aptitude in interactive mode, enter Limit Display '~i-trinity~ddummy" and
manually check and delete
unneeded packages.
> Can you test on your machines as well and let me know? If confirmed, I will update
the installation
> instructions. Cheers Michele
What about we propose two possibilities?
1) same as the one I proposed. This one would basically upgrade/install all TDE R14.0.0
and get rid of dummy
packages. This solution would be intended for "generic" users who want a simple
way to upgrade all TDE
2) same solution that you suggested, i.e. step 1 and step 2, then run aptitude in
interactive mode, enter Limit
Display '~i-trinity~ddummy" and manually check/delete unneeded packages and
install equivalent tde packages. This
would be intended for more expert users, who can choose what to install and what not.
What do you think? Cheers Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJUoMQjAAoJECp1t8qK3tXPaqAQAJCyURIHnlVKw7zCbkjKMRYP
3e+QsdWVAEIbKBvctHYTI2sJ7K7vWCsagg+Cx+cJFNUwTXiwsTa/sgvC2NkUn3uv
bE2ZZG5UbqmEcXqhesqc82r8KbixzT0hOXax3mLXxlPu0hY0FIklSvXHtT/B2361
6oOWxVNrl54RfDmALhLDyQqwhBEl5Ib7cy9CxUVJtcmhsPKV+x1ZtnaiAqVLUfh0
4asbkKqnBvWVJnCcwgjIx/C+6uAj+2oBG5STTKLgA8WG1TcaKlwb2b3jIwBv+B/P
YovHO3wi7bKgt4xpl/FBEoFyc9oJb8Yz6qLpUu6y3rD23ti0M/qiXFXQ36ZCHtg2
vm64mfaD5jz86PiOC0JwaW9R++aiZDgB2I9CBnukHZEz7Qm1+FeMM+z82d3TaEnh
EzSNBa/rhSPwSSK3+geSoE85H38FcHAX9A26Sqv/Aa30mvI32j8/mZeeY/hspW4f
QnmCbcCOme8PysTfs7w1xg1s9sqQDWdazFpJ7vJnMcCXjSMRVl5bH5bJBT+lC555
SDxJMFFtyP/f5h7BPpxW3uUH4ZEmBKLZk47qiWyerAC7NlDk6AdWj/84wLjYo6mX
+STT/lhAwBUDcMasy8JYvRqjT8EPs4epNuXhBACwhK+caYKLHp0EPqu2Nnq315cF
kTaGK1gVYUB896eTnaNM
=Nwgb
-----END PGP SIGNATURE-----
1 Jan
1 Jan
2:37 p.m.
New subject: [trinity-devel] Package renames and autoremove
On Monday 29 of December 2014 04:01:55 Michele Calgaro wrote:
On 12/26/2014 11:36 PM, Slávek Banko wrote:
I think it looks good, thank you.
By the way, on Ubuntu is not any package that should not be automatically
updated by step 2. Package trinity-rename-meta should take care of all
meta-packages. The only exceptions should be really just kde-trinity,
kde-core-trinity and kde-devel-trinity on Debian.
--
Slávek
On Friday 26 of December 2014 14:25:52 Michele
Calgaro wrote:
Essential however is that in step 2 are updated 'all installed' packages.
Regardless of how was installed the previous version of TDE - whether the
packages were selected individually (as is in my case) or meta-package
was used (as are ordinary users). The only packages that are not updated
in the previous step are kde-trinity, kde-core-trinity and
kde-devel-trinity ... and possibly their new dependencies => new
packages.
Therefore 406 new packages from my example is simply much, because it
causes installation a lot of packages that "I did not want to have" => I
did not installed intentionally. Therefore my proposal from previous mail
to the reformulation of step 3 to optional => "If you have installed
metapackage kde..." - see paragraph below.
I think that the proposed procedures are not mutually exclusive, but
complementary => no problem to combine it into a single process:
Steps 1) and 2) are identical. Step 3) is optional => for users that have
previously installed meta-packages kde-trinity / kde-core-trinity /
kde-devel-trinity. Step 4) is optional => for advanced users who wants to
do more housekeeping.
Slavek,
I have updated both Debian and Ubuntu installation pages on the wiki.
If you compare the "Upgrade" section on both pages, you will see that
"Debian's point A" is not present in the Ubuntu version. This is because
the package names to install TDE in Ubuntu are different from Debian. I do
not have an Ubuntu system to test on. Could you check and let me know if
there is any error or missing info regarding the Ubuntu page? Thanks.
Cheers
Michele
On 12/26/2014 04:26 AM, Slávek Banko wrote:
Yes, 64 is perfectly fine, because on this test machine is not installed
"everything", but substantial and potentially conflicting packages.
On Tuesday 23 of December 2014 09:11:53 Michele
Calgaro wrote:
> On 2014/12/22 07:26 PM, Slávek Banko wrote:
>> On Monday 22 of December 2014 11:06:20 Michele Calgaro wrote:
>>> Looks like the mirror is now fully working, since it takes less than
>>> 30 minutes to do a fully upgrade. So I have tested sevaral ways to
>>> upgrade from a standard 3.5.13.2 install to 14.0.0. The sequence
>>> suggested by Mike seems to be the most reliable/reproducable, but
>>> with some tweeks. 1) apt-get update 2) apt-get install tde-trinity.
>>> This fails at some point. 3) apt-get -f install. This succeeded, but
>>> trying to login after this stage gives the error "Could not start
>>> kstartupconfig...." 4) apt-get dist-upgrade After this stage, I have
>>> a fully working TDE R14.0.0 system. Running aptitude in CLI mode and
>>> pressing 'g', comes up with a list of packages that can be deleted.
>>> This at times is most of the TDE installation. To fix this do the
>>> following. 5) run 'aptitude', search tde-trinity (which should be
>>> shown as *un*installed, mark as 'to install' and 'g'. This
will make
>>> R14.0.0 stick in your system 6) running 'aptitude' and pressing
'g'
>>> again, comes up with a list of packages that can be deleted.
>>> Proceed.
>>>
>>> I have noticed over several upgrade runs, that the list of packages
>>> that can be deleted is not always the same, not sure why although
>>> some of the upgrade run were interrupted/resumed several times due
>>> to the slow download bandwidth of previous days. It seems that dummy
>>> packages have to be manually removed. dpkg -l | grep -i dummy gives
>>> a list of such packages.
>>>
>>> I will modify the installation instructions adding an "Update from
>>> 3.5.13.2" section to it. If you have any specific comments that you
>>> would like to add to the above, please let me know (once again :-) )
>>>
>>> Cheers Michele
>>
>> I must again point out - if the user perform a manual selection of
>
> packages to
>
>> install, the process containing "apt-get install tde-trinity" is not
>
> an just
>
>> upgrade, but will install many other packages. Moreover, as you
>
> mention, this
>
>> step fails. That does not sound like a good way to upgrade.
>>
>> Please, test this simple procedure:
>>
>> 1) apt-get update 2) aptitude dist-upgrade
>>
>> As I've mentioned many times before, this procedure on all my test
>
> machines
>
>> ran smoothly - without any hitch - and it's "really just upgrade".
>
> Slavek, I tested your way and the upgrade goes smooth. Nevertheless
> after the process is completed a lot of dummy packages are still
> installed. Using the following procedure gets rid of those dummy
> packages and leaves a clean upgrade.
>
> 1) apt-get update
No problems.
> 2) aptitude dist-upgrade
96 packages upgraded, 64 newly installed, 15 to remove and 0 not
upgraded. Need to get 147 MB of archives. After unpacking 63.7 MB will
be used.
No problems.
Note: only 64 new packages installed. > 3)
aptitude install tde-trinity -> then choose to resolve the
> conflict by removing kde-trinity and kde-core-trinity
0 packages upgraded, 406 newly installed, 0 to remove and 0 not
upgraded. Need to get 231 MB of archives. After unpacking 626 MB will
be used.
Oops, that's a bit much.
Well, "too much" is subjective. Basically the "general" user is
trying
to upgrade from a previous kde-install, so this step is just installing
whatever package was not upgraded from step 2. On my wheezy installation
steps 2 install about 250 packages and step 3 about 200 if my memory is
right. The total is about 450, which is similar to the number you
reported on a previous email
(http://trinity-devel.pearsoncomputing.net/?0::14312) I think
we could recommend something like this:
If you had installed metapackage kde-trinity, kde-core-trinity or
kde-devel-trinity, these are not updated automatically. For the update
is necessary to use one of the following:
aptitude install tde-trinity aptitude install tde-core-trinity aptitude
install tde-devel-trinity
As I watched, there are several transitional dummy packages which would
still have had to be removed manually. For example kde-i18n-*,
kio-locate, kradio,... For such I would suggest the following:
4) Run aptitude in interactive mode, enter Limit Display
'~i-trinity~ddummy" and manually check and delete unneeded packages.
> Can you test on your machines as well and let me know? If confirmed, I
> will update the installation instructions. Cheers Michele
What about we propose two possibilities?
1) same as the one I proposed. This one would basically upgrade/install
all TDE R14.0.0 and get rid of dummy packages. This solution would be
intended for "generic" users who want a simple way to upgrade all TDE
2) same solution that you suggested, i.e. step 1 and step 2, then run
aptitude in interactive mode, enter Limit Display '~i-trinity~ddummy"
and manually check/delete unneeded packages and install equivalent tde
packages. This would be intended for more expert users, who can choose
what to install and what not.
What do you think? Cheers Michele
2 Jan
2 Jan
3:08 a.m.
New subject: [trinity-devel] Package renames and autoremove
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 01/01/2015 11:37 PM, Slávek Banko wrote:
Hi Slavek,
thanks for checking :-)
Michele
Slavek,
> I have updated both Debian and Ubuntu installation pages on the wiki. If you compare
the "Upgrade" section on
> both pages, you will see that "Debian's point A" is not present in the
Ubuntu version. This is because the
> package names to install TDE in Ubuntu are different from Debian. I do not have an
Ubuntu system to test on.
> Could you check and let me know if there is any error or missing info regarding the
Ubuntu page? Thanks.
>
> Cheers Michele
>
I think it looks good, thank you.
By the way, on Ubuntu is not any package that should not be automatically updated by step
2. Package
trinity-rename-meta should take care of all meta-packages. The only exceptions should be
really just kde-trinity,
kde-core-trinity and kde-devel-trinity on Debian.
-- Slávek -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJUpgueAAoJECp1t8qK3tXPS74QAIOs1YjAz5VRar3PN+ZeXdNX
t1O+xQD4L24UraEsRxa+q/M0GOvpTms0JLodR1rgu0DlGIk3/KYB4RNPTodtGcHV
2f4rkn2+DPjq8wvsyrKGFrOKVx1ZMBvs2cIFjCN0YBOcNoxIX7QUUybQWmQTf7ny
3hnSD8mBYERxYP4Wwje8tTOjUp34EsHq4H12uDK5Eb3XDzfzsfvMSqzGTRCKEm2N
qv+AQmmoHma9IYNbEvZQCKTn5RLDRTFNz8IH2ipJtZ09YRZK0SevHxkJ2P/qlq51
N3a2/5+0dv9tpG921kDjFZrPqFLh/lnECJl6Vq3hjFEWaFGVTKBt9N6R2khbRbts
/gd3LQpkgELg7VD8woKqUlCIuvKeu29WVEKiu3mohsZz4MGEvWtzJz5th0ff439w
aTqBhpX6sHdDy64m2xCLq3wFGDcRD0HaYJnimDm68974rGrvppTNnkr4q+wyad9K
+IvDO5A5Fpa8trOjEIGBHlpdKQatk9S1pJaLcyS7cYqipVr0ODLlZo1wiP71Qu7B
esCtHrKM1xb7gAxvtqTio/99lmLCEM7GKTs7TCyWvUrIIWdijj0up1G4zndjO5tU
tNpCxTKTZ6DZMYO6Qsmlr0RCrQE7HN1aHI7d2Vt3FUBNSD4wJLZcJxsZanSlOkAF
7WHWZE5lSzo2AMqbrbsz
=EEgA
-----END PGP SIGNATURE-----
3413
days inactive
3435
days old
34 comments
4 participants
participants (4)
-
Michele Calgaro -
Mike Bird -
Slávek Banko -
Timothy Pearson