The official way to upgrade F18 to F19

[Dario Lesca]

What is the official way to upgrade F18 to F19 (for now beta)?
I would do some test..
Thanks
-- 
Dario Lesca - sip:[e-mail]
(Inviato dal mio Linux Fedora18+Gnome3)

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/29/2013 08:48 AM, Dario Lesca wrote:
>  What is the official way to upgrade F18 to F19 (for now beta)? I
>  would do some test.. Thanks
>   
http://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedU...
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.13 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlGl+ewACgkQeiVVYja6o6OA3QCghWVAXCEB7cDv+JETSXOWi2V/
> aQEAn2Uy0gn7mqQRVeQV2vRHUOxsCpZ9
> =EEJl
> -----END PGP SIGNATURE-----

[Nikos Roussos]

Stephen Gallagher <sgallagh(a)redhat.com&gt; wrote:
> On 05/29/2013 08:48 AM, Dario Lesca wrote:
> > What is the official way to upgrade F18 to F19 (for now beta)? I
> > would do some test.. Thanks
> > 
>
> http://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedU... 
Is there any plan currently for a GUI frontend for FedUp?

[Dario Lesca]

Il giorno mer, 29/05/2013 alle 08.51 -0400, Stephen Gallagher ha
scritto:
>  On 05/29/2013 08:48 AM, Dario Lesca wrote:
>  > What is the official way to upgrade F18 to F19 (for now beta)? I
>  > would do some test.. Thanks
>  > 
>  
>  http://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedU... 
I have follow the instruction, but:

>  [root@dodo:~]# LANG=C yum --enablerepo=updates-testing install fedup
>  Loaded plugins: fastestmirror, langpacks, presto
>  ......
>  Package fedup-0.7.3-4.fc18.noarch already installed and latest version
>  Nothing to do 
and

>  [root@dodo:~]# fedup-cli --network 19
>  setting up repos...
>  adobe-linux-x86_64                                                                       
>        |  951 B  00:00:00     
>  adobe-linux-x86_64/primary                                                               
>        | 1.2 kB  00:00:00     
>  default-installrepo/metalink                                                             
>        |  26 kB  00:00:00     
>  Could not parse metalink
> https://mirrors.fedoraproject.org/metalink?repo=fedora-install-19&arc... error
> was 
>  No repomd file
>  fedora/19/x86_64/metalink                                                                
>        |  24 kB  00:00:00     
>  fedora/19/x86_64                                                                         
>        | 4.2 kB  00:00:00     
>  fedora/primary_db                                                                        
>        |  17 MB  00:00:26     
>  playonlinux                                                                              
>        |  951 B  00:00:00     
>  playonlinux/primary                                                                      
>        | 4.4 kB  00:00:00     
>  rpmfusion-free/19/x86_64                                                                 
>        | 3.3 kB  00:00:00     
>  rpmfusion-free/primary_db                                                                
>        | 445 kB  00:00:00     
>  rpmfusion-free-updates/19/x86_64                                                         
>        | 1.2 kB  00:00:00     
>  rpmfusion-free-updates/primary                                                           
>        |  204 B  00:00:00     
>  rpmfusion-nonfree/19/x86_64                                                              
>        | 3.3 kB  00:00:00     
>  rpmfusion-nonfree/primary_db                                                             
>        | 150 kB  00:00:00     
>  rpmfusion-nonfree-updates/19/x86_64                                                      
>        | 1.2 kB  00:00:00     
>  rpmfusion-nonfree-updates/primary                                                        
>        |  204 B  00:00:00     
>  updates/19/x86_64/metalink                                                               
>        |  29 kB  00:00:00     
>  updates/19/x86_64                                                                        
>        | 3.4 kB  00:00:00     
>  updates/primary_db                                                                       
>        | 1.2 kB  00:00:00     
>  Error: can't get boot images.
>  The installation repo isn't available.
>  You need to specify one with --instrepo. 
Some suggest?

-- 
Dario Lesca - sip:[e-mail]
(Inviato dal mio Linux Fedora18+Gnome3)

[Jeffrey Bastian]

On Wed, May 29, 2013 at 06:16:11PM +0200, Dario Lesca wrote:
>  > The installation repo isn't available.
>  > You need to specify one with --instrepo.
>  
>  Some suggest? 

I used this command over this past weekend:

fedup --network 19 --debuglog=/var/log/fedupdebug.log \
  --instrepo http://dl.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/

Jeff

[Kevin Fenzi]

On Wed, 29 May 2013 11:27:04 -0500
Jeffrey Bastian <jbastian(a)redhat.com&gt; wrote:

>  On Wed, May 29, 2013 at 06:16:11PM +0200, Dario Lesca wrote:
>  > > The installation repo isn't available.
>  > > You need to specify one with --instrepo.
>  > 
>  > Some suggest?
>  
>  
>  I used this command over this past weekend:
>  
>  fedup --network 19 --debuglog=/var/log/fedupdebug.log \
>    --instrepo
>  http://dl.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/ 
Right. You cannot just specify 19 because Fedora 19 is not yet out,
it's only Beta. 

kevin

[Dario Lesca]

Il giorno mer, 29/05/2013 alle 10.37 -0600, Kevin Fenzi ha scritto:
>  On Wed, 29 May 2013 11:27:04 -0500
>  Jeffrey Bastian <jbastian(a)redhat.com&gt; wrote:
>  
>  > On Wed, May 29, 2013 at 06:16:11PM +0200, Dario Lesca wrote:
>  > > > The installation repo isn't available.
>  > > > You need to specify one with --instrepo.
>  > > 
>  > > Some suggest?
>  > 
>  > 
>  > I used this command over this past weekend:
>  > 
>  > fedup --network 19 --debuglog=/var/log/fedupdebug.log \
>  >   --instrepo
>  > http://dl.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/
>  
>  Right. You cannot just specify 19 because Fedora 19 is not yet out,
>  it's only Beta. 
>   
Ok, thanks.

-- 
Dario Lesca - sip:[e-mail]
(Inviato dal mio Linux Fedora18+Gnome3)

[Adam Williamson]

On Wed, 2013-05-29 at 18:55 +0200, Dario Lesca wrote:
>  Il giorno mer, 29/05/2013 alle 10.37 -0600, Kevin Fenzi ha scritto:
>  > On Wed, 29 May 2013 11:27:04 -0500
>  > Jeffrey Bastian <jbastian(a)redhat.com&gt; wrote:
>  > 
>  > > On Wed, May 29, 2013 at 06:16:11PM +0200, Dario Lesca wrote:
>  > > > > The installation repo isn't available.
>  > > > > You need to specify one with --instrepo.
>  > > > 
>  > > > Some suggest?
>  > > 
>  > > 
>  > > I used this command over this past weekend:
>  > > 
>  > > fedup --network 19 --debuglog=/var/log/fedupdebug.log \
>  > >   --instrepo
>  > > http://dl.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/
>  > 
>  > Right. You cannot just specify 19 because Fedora 19 is not yet out,
>  > it's only Beta. 
>  > 
>  
>  Ok, thanks. 
I usually point people to:

https://fedoraproject.org/wiki/QA:Testcase_upgrade_fedup_cli_previous_des...

which includes the instructions for explicitly specifying a repo, for
the upgrade-to-Branched case. Though I'm sure fedup could avoid the need
for it...
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

[Kevin Fenzi]

On Wed, 29 May 2013 10:05:37 -0700
Adam Williamson <awilliam(a)redhat.com&gt; wrote:

>  On Wed, 2013-05-29 at 18:55 +0200, Dario Lesca wrote:
>  > Il giorno mer, 29/05/2013 alle 10.37 -0600, Kevin Fenzi ha scritto:
>  > > On Wed, 29 May 2013 11:27:04 -0500
>  > > Jeffrey Bastian <jbastian(a)redhat.com&gt; wrote:
>  > > 
>  > > > On Wed, May 29, 2013 at 06:16:11PM +0200, Dario Lesca wrote:
>  > > > > > The installation repo isn't available.
>  > > > > > You need to specify one with --instrepo.
>  > > > > 
>  > > > > Some suggest?
>  > > > 
>  > > > 
>  > > > I used this command over this past weekend:
>  > > > 
>  > > > fedup --network 19 --debuglog=/var/log/fedupdebug.log \
>  > > >   --instrepo
>  > > > http://dl.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/
>  > > 
>  > > Right. You cannot just specify 19 because Fedora 19 is not yet
>  > > out, it's only Beta. 
>  > > 
>  > 
>  > Ok, thanks.
>  
>  I usually point people to:
>  
>  https://fedoraproject.org/wiki/QA:Testcase_upgrade_fedup_cli_previous_des...
>  
>  which includes the instructions for explicitly specifying a repo, for
>  the upgrade-to-Branched case. Though I'm sure fedup could avoid the
>  need for it... 
Indeed it can, and now it should. 

fedup looks for a special mirrormanager target to find the install repo
for that version. We didn't update this for f19, so it was just not
finding it. Dennis just updated things so now it will. Apparently in
f18 we also set it up before release so it would just work. 

If folks think we shouldn't make 'fedup --network 19' work now to
upgrade people to branched/prerelease, please scream. ;) Otherwise it
will be the case from now on. 

kevin

[Ravindra Kumar]

>  If folks think we shouldn't make 'fedup --network 19'
> work now to
>  upgrade people to branched/prerelease, please scream. ;) Otherwise it
>  will be the case from now on.  
Probably, 'fedup --network 19' should not install alpha/beta
releases automatically, instead a switch to specifically select
a prerelease would be a better choice. That gives more control
to the user. I mean 19 should mean Fedora 19 and may be you
could use something like 19a/19alpha, 19b/19beta etc for alpha,
beta releases respectively. Or, just 19pre for latest prerelease
to be simpler.

Thanks,
Ravindra

[Adam Williamson]

On Wed, 2013-05-29 at 18:20 -0700, Ravindra Kumar wrote:
>  > If folks think we shouldn't make 'fedup --network
> 19' work now to
>  > upgrade people to branched/prerelease, please scream. ;) Otherwise it
>  > will be the case from now on. 
>  
>  Probably, 'fedup --network 19' should not install alpha/beta
>  releases automatically, instead a switch to specifically select
>  a prerelease would be a better choice. That gives more control
>  to the user. I mean 19 should mean Fedora 19 and may be you
>  could use something like 19a/19alpha, 19b/19beta etc for alpha,
>  beta releases respectively. Or, just 19pre for latest prerelease
>  to be simpler. 
I think that level of 'protection' might be going too far. You'd have to
be pretty dim to run an upgrade to a pre-release without knowing what
you were doing.

If we had a GUI tool or a notification thing, sure, it'd make sense to
'hide' pre-releases in those. But I don't think it's really necessary to
do this in a CLI tool where you already have to explicitly specify the
version you're updating to.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

[Nathanael D. Noblet]

On 05/29/2013 07:12 PM, Kevin Fenzi wrote:
>  If folks think we shouldn't make 'fedup --network 19'
> work now to
>  upgrade people to branched/prerelease, please scream. ;) Otherwise it
>  will be the case from now on. 
Hello,

   I usually upgrade my main laptop and workstation to Fedora Beta X. 
This time around I tried in vain to find the magic incantation via 
google. So I downloaded the ISO, and did an ISO update then yum 
distro-sync. I would *love* if fedup allowed us to use a Alpha or Beta 
without knowing the incantation.

   I'm indifferent to the 'should we protect users'. I wouldn't 
necessarily say its needed, and I'd prefer to not have to know the 
'magic' name F19Beta or 19-beta or whatever. If its decided to protect 
users I'd go for a command line switch --allow-pre-release or something. 
Mainly because then fedup -h would display it and then the default could 
be left as is to only use released branches.

   Either way though consider this a scream for it to allow upgrades to 
prereleases...!!!

-- 
Gnat