Re: FedUp: best plan?
Am 17.01.2013 17:29, schrieb Mark Eggers: > One thing I did notice is that I'm running grub2-2.00-15.fc18.x86_64 (at > least that's what RPM says) and I get the grub 2.00~beta4 screen on boot. > Do I need to reinstall grub2? yes, as also if your /boot is RAID1 you have to take care by yourself that GRUB is installed on all drives at updates grub is NEVER installed automatically and this is good - it would break many setups all over the time signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On Thu, 17 Jan 2013 07:26:33 -0500, Luan Minh Pham wrote: > On Wednesday, January 16, 2013 09:42:37 PM Matthew Miller wrote: >> > I would recommend not to use fedup. I'm facing a lot of troubles >> > after going the fedup route. Although not officially supported, you >> > could try upgrading via yum. It has been reliably working for people >> > across multiple releases. >> >> It would be very helpful if you could report those troubles. Otherwise, >> it's hard to make it better. > > For one Fedup doesn't download all the package it need, so in middle of > the upgrade system reboot. I could not even login to KDE desktop. So > I had to go to failsafe mode to finish the updatge. I ran into that problem, but in retrospect I should have expected it. I ran fedup against the install ISO since I have a laptop with only wireless right now. I didn't want to take a chance and lose wireless connectivity during the update. KDE was pretty borked after the initial update. Doing yum distro-sync fixed that. I had to manually update the rpmfusion repositories by using the command line procedure given on the rpmfusion web site. After rebooting (new kernel), I had a bunch of 32 bit updates to do (on a 64 bit machine - running Skype). Once I did all of that, everything was happily up and running (almost). Moving from httpd 2.2 to httpd 2.4 created some problems, but then again that's not a fedup issue. Recompiled a few modules, reworked the configuration, and all was good. VNC no longer works, but in retrospect this is expected. Gnome and KDE I guess now require 3D acceleration, which means I'll install Mate, LXDE, or XFCE for VNC. Yeah, I know - VNC to a laptop?? Most of the time I ssh in from my desktop. One thing I did notice is that I'm running grub2-2.00-15.fc18.x86_64 (at least that's what RPM says) and I get the grub 2.00~beta4 screen on boot. Do I need to reinstall grub2? One last thing - the new Gnome 3.6 screen saver on the login panel is a real pain with a laptop and a touch pad. . . . . just my two cents /mde/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On 01/16/2013 08:59 PM, Suvayu Ali wrote: On Thu, Jan 17, 2013 at 12:41:41AM +, Phil Dobbin wrote: Hi, all. I've been watching the developments regarding everybody trying to upgrade via FedUp & can anyone advise me whether issuing: 'sudo fedup-cli —network 18 —debuglog fedupdebug.log' is still the recommended way to approach the upgrade? I'm running a rock solid Fedora 17 with all updates applied & intend to disable any extra repos that I have personally added to sources by hand. I would recommend not to use fedup. I'm facing a lot of troubles after going the fedup route. Although not officially supported, you could try upgrading via yum. It has been reliably working for people across multiple releases. I might as well ask, even though it'll sound "stoopid" by this lists standards!: I am currently running Fedora 17 on my laptop, I remember upgrading from 14 to 15and from 15 to 16and then to 17, each time I had to re-install all my applications, their settings, and add-ons / extensions, only because I couldn't figure out how to upgrade and have everything "stay" on my system. So I am asking, _IS _there a way to run this "fedup" and have all my apps, and their settings / customizations, and add-ons remain? I realize I need to back up the entire system, and I have done that already, but it gets a bit wearisome having to re-install things all over againjust curious, and thanks for any help - advice given! EGO II -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On Wed, Jan 16, 2013 at 09:42:37PM -0500, Matthew Miller wrote: > On Thu, Jan 17, 2013 at 02:59:35AM +0100, Suvayu Ali wrote: > > I would recommend not to use fedup. I'm facing a lot of troubles after > > going the fedup route. Although not officially supported, you could try > > upgrading via yum. It has been reliably working for people across > > multiple releases. > > It would be very helpful if you could report those troubles. Otherwise, it's > hard to make it better. > I did plan to report it, but I have some questions before I collect all the information; maybe someone here can help. These are the issues I have: 1. I have been using grub. This ThinkPad have been upgraded through all the releases since F14, I didn't think worth the effort to switch to grub2 since everything worked well for me. After using fedup, I cannot edit the entries or the kernel arguments anymore. Trying to do that, corrupts the line (display only). I can't even move along the line consistently (cursor keys, home, end, nothing works). If I blindly type something and accept it with RET, it is ignored too. This makes debugging very inconvenient. 2. Apart from this I found fedup messed with a couple of daemons (which were working fine with F17), and now I am getting warning emails from systemd. Since most of these are non-critical I just turned them off. 3. With the F18 kernel (3.7.2-201.fc18.x86_64), my screen gets corrupted, and I can't see anything. I realise this is not a fedup issue, probably just a bad kernel. This is even before the gdm login screen appears. So far the only way to boot with this kernel is to use nomodeset (which comes with its own caveats of course). I have tried rebuilding the initrd with dracut with no luck. 4. Again, this is not a fedup issue; I'm having power management issues. For example, while waking up from sleep (by opening the lid) it sometime goes back to sleep again and I have to manually press the power button. Some of my power management settings about what to do when on AC power or battery are also ignored. Problem (2) is not important enough for me to investigate, but I consider (1) to be a severe regression. However I'm not sure how I can debug and add useful information to any bug report, the same goes for (3). With (4) it could just be an issue with the power management application for my desktop (XFCE). Any suggestions about how to go about debugging (1) and (3) are very welcome. Cheers, -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On Thursday, January 17, 2013 07:48:28 AM Phil Dobbin wrote: > If FedUp is as unreliable as you say, it's a pretty serious bug that > needs addressing as soon as possible. It more like server not totally sync yet. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On Wednesday, January 16, 2013 09:42:37 PM Matthew Miller wrote: > > I would recommend not to use fedup. I'm facing a lot of troubles after > > going the fedup route. Although not officially supported, you could try > > upgrading via yum. It has been reliably working for people across > > multiple releases. > > It would be very helpful if you could report those troubles. Otherwise, it's > hard to make it better. For one Fedup doesn't download all the package it need, so in middle of the upgrade system reboot. I could not even login to KDE desktop. So I had to go to failsafe mode to finish the updatge. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On Thursday, January 17, 2013 07:48:28 Phil Dobbin wrote: > Mmm. I'm not really sure about using yum. If FedUp is the approved > method, I'm at least going to try it. I just did it (F17 -> F18 via yum) without a hitch. I decided to go this way due to the problems being reported with FedUp. Although it took a long time (I'm on a slow DSL link), it really was quite a yawn. -- Garry T. Williams -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On 01/17/2013 01:59 AM, Suvayu Ali wrote: > On Thu, Jan 17, 2013 at 12:41:41AM +, Phil Dobbin wrote: >> Hi, all. >> >> I've been watching the developments regarding everybody trying to >> upgrade via FedUp & can anyone advise me whether issuing: >> >> 'sudo fedup-cli —network 18 —debuglog fedupdebug.log' >> >> is still the recommended way to approach the upgrade? >> >> I'm running a rock solid Fedora 17 with all updates applied & intend to >> disable any extra repos that I have personally added to sources by hand. > > I would recommend not to use fedup. I'm facing a lot of troubles after > going the fedup route. Although not officially supported, you could try > upgrading via yum. It has been reliably working for people across > multiple releases. Mmm. I'm not really sure about using yum. If FedUp is the approved method, I'm at least going to try it. I've been running several versions of 18 for quite some time now either on a physical machine or a virtual one without too many problems so I'll think I'll spin up another couple of KVM VMs & try using FedUp in them first & report my findings good or otherwise via the appropriate channels. If FedUp is as unreliable as you say, it's a pretty serious bug that needs addressing as soon as possible. Cheers, Phil... -- currently (ab)using CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical, Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On 01/16/2013 06:42 PM, Matthew Miller wrote: It would be very helpful if you could report those troubles. Otherwise, it's hard to make it better. And, unless people report these things, the devs won't know there's anything wrong. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On 01/17/2013 10:50 AM, Matthew Miller wrote: > On Thu, Jan 17, 2013 at 10:47:54AM +0800, Ed Greshko wrote: >> Quick question in respect to this >> Would you expect fedup to work in a Virtual Machine (Vbox) environment? >> I've had 2 failed updates, out of 2, but both were in a Vbox machine and >> both had a 3rd party MATE repository enabled. > There's no reason it shouldn't. I don't think Virtual Box VMS are an > official target, but we really should work everywhere reasonably possible. > > The 3rd party repo is a likely showstopper, though. > OK, I'll do some testing on other VMs without MATE. Thanks -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry Compiled -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On Thu, Jan 17, 2013 at 10:47:54AM +0800, Ed Greshko wrote: > Quick question in respect to this > Would you expect fedup to work in a Virtual Machine (Vbox) environment? > I've had 2 failed updates, out of 2, but both were in a Vbox machine and > both had a 3rd party MATE repository enabled. There's no reason it shouldn't. I don't think Virtual Box VMS are an official target, but we really should work everywhere reasonably possible. The 3rd party repo is a likely showstopper, though. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On 01/17/2013 10:42 AM, Matthew Miller wrote: > On Thu, Jan 17, 2013 at 02:59:35AM +0100, Suvayu Ali wrote: >> I would recommend not to use fedup. I'm facing a lot of troubles after >> going the fedup route. Although not officially supported, you could try >> upgrading via yum. It has been reliably working for people across >> multiple releases. > It would be very helpful if you could report those troubles. Otherwise, it's > hard to make it better. > Quick question in respect to this Would you expect fedup to work in a Virtual Machine (Vbox) environment? I've had 2 failed updates, out of 2, but both were in a Vbox machine and both had a 3rd party MATE repository enabled. -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry Compiled -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On Thu, Jan 17, 2013 at 02:59:35AM +0100, Suvayu Ali wrote: > I would recommend not to use fedup. I'm facing a lot of troubles after > going the fedup route. Although not officially supported, you could try > upgrading via yum. It has been reliably working for people across > multiple releases. It would be very helpful if you could report those troubles. Otherwise, it's hard to make it better. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: FedUp: best plan?
On Thu, Jan 17, 2013 at 12:41:41AM +, Phil Dobbin wrote: > Hi, all. > > I've been watching the developments regarding everybody trying to > upgrade via FedUp & can anyone advise me whether issuing: > > 'sudo fedup-cli —network 18 —debuglog fedupdebug.log' > > is still the recommended way to approach the upgrade? > > I'm running a rock solid Fedora 17 with all updates applied & intend to > disable any extra repos that I have personally added to sources by hand. I would recommend not to use fedup. I'm facing a lot of troubles after going the fedup route. Although not officially supported, you could try upgrading via yum. It has been reliably working for people across multiple releases. -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
FedUp: best plan?
Hi, all. I've been watching the developments regarding everybody trying to upgrade via FedUp & can anyone advise me whether issuing: 'sudo fedup-cli —network 18 —debuglog fedupdebug.log' is still the recommended way to approach the upgrade? I'm running a rock solid Fedora 17 with all updates applied & intend to disable any extra repos that I have personally added to sources by hand. Thanks for any pointers. Cheers, Phil... -- currently (ab)using CentOS 5.8 & 6.3, Debian Squeeze & Wheezy, Fedora Beefy & Spherical, Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise & Quantal GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
