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
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
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
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 yu
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 subscr
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
> > multip
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. Altho
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 fedu
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 unsubsc
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
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.
T
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 relia
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.
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
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 ap
15 matches
Mail list logo