By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2201 - migratekde3 should be easier to find
Summary: migratekde3 should be easier to find
Status: VERIFIED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 wishlist
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2014-11-21 16:49 CST by mgb-trinity
Modified: 2018-08-02 09:40 CDT (History)
5 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mgb-trinity 2014-11-21 16:49:46 CST 
Upon logging into R14 I received a large warning telling me to run migratekde3 first.

However the message did not specify the full path to migratekde3, migratekde3 is not on my user's $PATH, there is no "man migratekde3", and "apt-cache search migratekde3" yields nothing.

Of course I eventually found it in package tdebase-trinity-bin and in directory /opt/trinity/bin but it should be easier to find, particularly as some TDE users may be less accustomed to command line work.
Comment 1 Timothy Pearson 2014-11-21 18:21:31 CST 
Adding Darrell to CC list as he was one of the major authors of those scripts and he could probably clean this up quicker than I could. :-)
Comment 2 Darrell 2014-11-21 22:15:26 CST 
>Upon logging into R14 I received a large warning telling me to run migratekde3 first.
The r14-xdg-update script is the only place with text dialog referencing migratekde3. The warning text to run migratekde3 does not appear unless $TDEHOME is a sym link.

The presumption with that snippet of script is somebody was using KDE3 and migrated to TDE back when the profile directories were compatible. That era was TDE 3.5.11 through 3.5.13. Backwards compatibility with profile directories stopped with 3.5.13.1 when renaming efforts began. Somebody reported they were using a linked profile directory because they did not want to manually recreate a working profile from KDE3. That is what motivated that sym link test in the r14-xdg-update script.

The migratekde3 script contains the same basic sym link test. When a user is still using a KDE3 profile, then migratekde3 is the better place to break the sym link to create a new $TDEHOME profile. After creating the new $TDEHOME from the older KDE3 profile, the r14-xdg-update script will still run the first time TDE is run, but a profile will then exist that is more compatible with TDE than KDE3.

The sym link test is not the most robust, but nobody but me (and I think Slavek) tested the migratekde3 script. Moreso, to find users still using KDE3 profiles is mildly surprising. :)

I am attaching a patch to bug 2202. The full path to migratekde3 should now appear in the warning text. I nominally tested the patch, but others should test as well.
Comment 3 Timothy Pearson 2014-11-25 17:05:00 CST 
Patch is in GIT at this time; see Bug 2202 for details.

@mgb-trinity, is this an acceptable solution or do you think the user experience needs more polish?

Thanks!
Comment 4 mgb-trinity 2014-11-25 17:28:19 CST 
(In reply to Timothy Pearson from comment #3)
> @mgb-trinity, is this an acceptable solution or do you think the user
> experience needs more polish?

When Wheezy RC2 is available I'll restore the /home on that test box (an old laptop) from pre-R14 backup and run the migration again and let you know.
Comment 5 mgb-trinity 2014-12-10 20:10:50 CST 
Fix verified in R14 RC2.

If you'd like to mark this RESOLVED FIXED I'll be happy to mark it VERIFIED.
Comment 6 Michele Calgaro 2018-08-02 09:28:09 CDT 
Thanks mgb-trinity@yosemite.net!
Comment 7 mgb-trinity 2018-08-02 09:40:18 CDT 
Verified.