-----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:
On 12/26/2014 04:26 AM, Slávek Banko wrote:
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.
Yes, 64 is perfectly fine, because on this test machine is not installed
"everything", but substantial and
potentially conflicting packages.
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)
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
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
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
-----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-----