On 07/06/2015 08:50 PM, Allen wrote: > On Monday, July 06, 2015 07:40:27 PM Ben Stoutenburgh wrote: >> Judging from recent articles ( >> https://www.phoronix.com/scan.php?page=news_item&px=Fedora-Fedup-Being-Repla >> ced), I wouldn't trust FedUP for a couple more releases. >> > I've been doing Fedora upgrades-in-place for a long time. Most recently with > fedup and before that with preupgrade and I don't recall any problems. > > I read the Phoronix article you referenced and also the post in Fedora-devel > mailing list that the Phoronix article referenced. I don't understand what > problem they are referring to. I subscribe to Planet Fedora RSS feed and I > don't recall seeing anything about problems with fedup. Only thing I've > noticed is that there is a package cache in /var containing a gig or two that > becomes obsolete after the upgrade is complete yet is not automatically > removed.
The package cache doesn't automatically get flushed on Debian either, so I occasionally need to do "apt-get autoclean" or "apt-get clean". > Chris: I just upgraded from F21 -> F22 (using fedup). I use KDE as my desktop > environment. (I know that you use KDE). Ues I still run KDE. I gave up on KMail2 though, now using Icedove/Thunderbird. KMail2 went over to a back-end database system for showing the list of mail, and that's been giving me some problems. For whatever reason I occasionally get some mail that did not contain a Message-Id: header, and when that happens the mail doesn't ever show up in the list of mail in KMail2. Oh by the way mail from the 'caff' utility in the signing-party package (i.e. GPG signatures I get from Debian Developers) are the main ones that show up without a Message-Id. > F21 used KDE 4. F22 uses Plasma 5. > Most of my settings for KDE itself and for some KDE apps (e.g. Konsole, > Knotes) were lost. After the fact I read the F22 release notes, which said > that the KDE migration was supposed to be smooth. For Konsole, the config > settings transitioned to a new location, so they can be manually copied. I > haven't figured how to salvage Knotes. I had similar problems with the transition from KMail 1 -> KMail 2 and was not able to figure out a way around the problem there either. The upgrade process was supposed to index all the mail and import it into the database, and on an old P4 machine I use for mail backups, that took 72 hours and then the result was obviously missing a lot of mail, and repeated requests to re-index didn't help and I couldn't find a way to fix this. I'm now using 'archivemail' for long-term mail storage instead. I've never used KNotes so I'm not familiar with it in particular, but as it's part of the PIM module I believe it has the exact same back-end database issue. Look into the Akonadi subsystem. There are a number of backends available for Akonadi, the main one being MySQL. At the time the PostgreSQL subsystem was having issues but that should be worked out now, and the Sqlite subsystem on the KDE website had a big warning "you WILL have problems if you use the Sqlite backend". Look for the "akonadiconsole" which is a management and debugging console... that might help. The old KNotes data is likely still on the system, even though the new version of KNotes doesn't access that data. Hopefully you can find a way to trigger a re-import of the old data. (I was with KMail2, but it didn't seem to help.) -- Chris -- Chris Knadle [email protected] _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org https://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) Vassar College * Jul 8 - Mad Science Fair V @ Lourdes Aug 5 - Minimal Openstack @ Lourdes Sep 2 - Let'S Go Phishing
