1:37 a.m.
Hey folks! As we just hit a branch point, here's a refresher on what
this means for folks who've been running Rawhide.
If you want to keep running Rawhide, which will now contain packages
tracked for Fedora *22*, you don't need to do anything: just keep
updating. From tomorrow onwards, you'll start getting '.fc22' packages,
tracked for Fedora 22.
If you want to follow Fedora 21, you'll want to either remove the
'fedora-repos-rawhide' package (that replaced fedora-release-rawhide
today), or disable the Rawhide repository using a graphical repo config
manager or 'yum-config-manager' from yum-utils:
sudo yum-config-manager --disable rawhide
then you'll want to *enable* the regular Fedora repositories:
sudo yum-config-manager --enable fedora
and, optionally, enable updates-testing:
sudo yum-config-manager --enable updates-testing
if you miss the branch point and wind up on Rawhide (F22) but you want
to switch to F21, you'll want to do all the above, then do this:
sudo yum --releasever=21 distro-sync
which should get you back to F21. Note that as I write this, it seems
that mirrormanager needs an update for F21 - right now when you try to
use F21 repos, you'll see an error like this:
fedora/21/x86_64/metalink | 28 kB 00:00
Could not parse metalink
https://mirrors.fedoraproject.org/metalink?repo=fedora-21&arch=x86_64 error was
No repomd file
I expect that'll get cleaned up pretty soon, so just hang tight.
Stay safe out there, intrepid pre-release-nauts!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
6:11 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/10/2014 02:37 AM, Adam Williamson wrote:
Hey folks! As we just hit a branch point, here's a refresher on
what this means for folks who've been running Rawhide.
If you want to keep running Rawhide, which will now contain
packages tracked for Fedora *22*, you don't need to do anything:
just keep updating. From tomorrow onwards, you'll start getting
'.fc22' packages, tracked for Fedora 22.
If you want to follow Fedora 21, you'll want to either remove the
'fedora-repos-rawhide' package (that replaced
fedora-release-rawhide today), or disable the Rawhide repository
using a graphical repo config manager or 'yum-config-manager' from
yum-utils:
sudo yum-config-manager --disable rawhide
then you'll want to *enable* the regular Fedora repositories:
sudo yum-config-manager --enable fedora
and, optionally, enable updates-testing:
sudo yum-config-manager --enable updates-testing
if you miss the branch point and wind up on Rawhide (F22) but you
want to switch to F21, you'll want to do all the above, then do
this:
sudo yum --releasever=21 distro-sync
which should get you back to F21. Note that as I write this, it
seems that mirrormanager needs an update for F21 - right now when
you try to use F21 repos, you'll see an error like this:
fedora/21/x86_64/metalink | 28
kB 00:00 Could not parse metalink
https://mirrors.fedoraproject.org/metalink?repo=fedora-21&arch=x86_64
error was No repomd file
I expect that'll get cleaned up pretty soon, so just hang tight.
Stay safe out there, intrepid pre-release-nauts!
One thing I discovered last night. There's a bug with the new
fedora-release packages and yum/dnf are kind of arbitrarily picking
from fedora-release-[standard|cloud|server|workstation] to install if
you just update. (This is in large part because these are just
placeholder packages and don't have any content in them yet).
To avoid issues going forward, before you do the distro-sync above,
you probably want to 'yum install fedora-release-$something' where
$something is either 'standard' (for non-productized Fedora) or one of
the Products, which your environment will evolve more into the closer
we get to Alpha.
I'll try to work out what we need to do to make that transition
cleaner from F20->F21, but for Rawhide->F21 it's going to be a bit
manual for a while.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlO+dN0ACgkQeiVVYja6o6P6jgCbBZHPpQj6s6OnNSGxm6hAol8l
puoAniWV9dRrSjEehWBXwHakn61lYvLI
=dvSE
-----END PGP SIGNATURE-----
10:45 a.m.
On 10.07.2014 13:11, Stephen Gallagher wrote:
One thing I discovered last night. There's a bug with the new
fedora-release packages and yum/dnf are kind of arbitrarily picking
from fedora-release-[standard|cloud|server|workstation] to install if
you just update. (This is in large part because these are just
placeholder packages and don't have any content in them yet).
To avoid issues going forward, before you do the distro-sync above,
you probably want to 'yum install fedora-release-$something' where
$something is either 'standard' (for non-productized Fedora) or one of
the Products, which your environment will evolve more into the closer
we get to Alpha.
I'll try to work out what we need to do to make that transition
cleaner from F20->F21, but for Rawhide->F21 it's going to be a bit
manual for a while.
# grep fedora-release /var/log/yum.log
... Updated: fedora-release-21-0.9.noarch
... Erased: fedora-release-rawhide-21-0.7.noarch
Is this enough to stay on F21 or I still need e.g. 'fedora-release-standard' for
non-product-specific, that is as we use now on Fedora 20?
poma
11:31 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/10/2014 11:45 AM, poma wrote:
On 10.07.2014 13:11, Stephen Gallagher wrote:
> One thing I discovered last night. There's a bug with the new
> fedora-release packages and yum/dnf are kind of arbitrarily
> picking from fedora-release-[standard|cloud|server|workstation]
> to install if you just update. (This is in large part because
> these are just placeholder packages and don't have any content in
> them yet).
>
> To avoid issues going forward, before you do the distro-sync
> above, you probably want to 'yum install
> fedora-release-$something' where $something is either 'standard'
> (for non-productized Fedora) or one of the Products, which your
> environment will evolve more into the closer we get to Alpha.
>
> I'll try to work out what we need to do to make that transition
> cleaner from F20->F21, but for Rawhide->F21 it's going to be a
> bit manual for a while.
# grep fedora-release /var/log/yum.log ... Updated:
fedora-release-21-0.9.noarch ... Erased:
fedora-release-rawhide-21-0.7.noarch
Is this enough to stay on F21 or I still need e.g.
'fedora-release-standard' for non-product-specific, that is as we
use now on Fedora 20?
You'll want to install fedora-release-standard manually right now to
make sure you have the right version going forward.
We're working to figure out how to get that to install by default on
upgrades.
(Alternately, feel free to use -server or -workstation as well, if you
want to move towards that environment going forward).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlO+v9EACgkQeiVVYja6o6MljQCfVIJIkDciuOTuF6KpS4oJfeI2
8vgAoKpAYPpJZ91bQ4HqgQy4mfmcheFd
=MKnn
-----END PGP SIGNATURE-----
1:38 p.m.
On 10.07.2014 18:31, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/10/2014 11:45 AM, poma wrote:
> On 10.07.2014 13:11, Stephen Gallagher wrote:
>
>> One thing I discovered last night. There's a bug with the new
>> fedora-release packages and yum/dnf are kind of arbitrarily
>> picking from fedora-release-[standard|cloud|server|workstation]
>> to install if you just update. (This is in large part because
>> these are just placeholder packages and don't have any content in
>> them yet).
>>
>> To avoid issues going forward, before you do the distro-sync
>> above, you probably want to 'yum install
>> fedora-release-$something' where $something is either 'standard'
>> (for non-productized Fedora) or one of the Products, which your
>> environment will evolve more into the closer we get to Alpha.
>>
>> I'll try to work out what we need to do to make that transition
>> cleaner from F20->F21, but for Rawhide->F21 it's going to be a
>> bit manual for a while.
>
> # grep fedora-release /var/log/yum.log ... Updated:
> fedora-release-21-0.9.noarch ... Erased:
> fedora-release-rawhide-21-0.7.noarch
>
> Is this enough to stay on F21 or I still need e.g.
> 'fedora-release-standard' for non-product-specific, that is as we
> use now on Fedora 20?
>
You'll want to install fedora-release-standard manually right now to
make sure you have the right version going forward.
Done deal, thanks.
We're working to figure out how to get that to install by default
on
upgrades.
Good luck with that!
(Alternately, feel free to use -server or -workstation as well, if
you
want to move towards that environment going forward).
Those two goes camping in virtwood. :)
poma
6 p.m.
I'm ready to start my application testing on a Fedora 21 virtual
machine. What's the quickest way for me to get one built? Is there a
'net install' ISO file somewhere I can use?
On Thu, Jul 10, 2014 at 11:38 AM, poma <pomidorabelisima(a)gmail.com> wrote:
On 10.07.2014 18:31, Stephen Gallagher wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/10/2014 11:45 AM, poma wrote:
>>
>> On 10.07.2014 13:11, Stephen Gallagher wrote:
>>
>>> One thing I discovered last night. There's a bug with the new
>>> fedora-release packages and yum/dnf are kind of arbitrarily
>>> picking from fedora-release-[standard|cloud|server|workstation]
>>> to install if you just update. (This is in large part because
>>> these are just placeholder packages and don't have any content in
>>> them yet).
>>>
>>> To avoid issues going forward, before you do the distro-sync
>>> above, you probably want to 'yum install
>>> fedora-release-$something' where $something is either 'standard'
>>> (for non-productized Fedora) or one of the Products, which your
>>> environment will evolve more into the closer we get to Alpha.
>>>
>>> I'll try to work out what we need to do to make that transition
>>> cleaner from F20->F21, but for Rawhide->F21 it's going to be a
>>> bit manual for a while.
>>
>>
>> # grep fedora-release /var/log/yum.log ... Updated:
>> fedora-release-21-0.9.noarch ... Erased:
>> fedora-release-rawhide-21-0.7.noarch
>>
>> Is this enough to stay on F21 or I still need e.g.
>> 'fedora-release-standard' for non-product-specific, that is as we
>> use now on Fedora 20?
>>
>
> You'll want to install fedora-release-standard manually right now to
> make sure you have the right version going forward.
Done deal, thanks.
> We're working to figure out how to get that to install by default on
> upgrades.
Good luck with that!
> (Alternately, feel free to use -server or -workstation as well, if you
> want to move towards that environment going forward).
Those two goes camping in virtwood. :)
poma
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
--
Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick
http://j.mp/CompJournoStickOverview
You can catch more flies with a sticky tongue than you can with vinegar.
10:57 p.m.
On Thu, 2014-07-10 at 16:00 -0700, M. Edward (Ed) Borasky wrote:
I'm ready to start my application testing on a Fedora 21 virtual
machine. What's the quickest way for me to get one built? Is there a
'net install' ISO file somewhere I can use?
https://dl.fedoraproject.org/pub/fedora/linux/development/21/x86_64/os/im...
should be an F21 boot.iso. entirely untested, and you will need to boot the installed
system with 'enforcing=0' or do an autorelabel on first boot, due to
https://bugzilla.redhat.com/show_bug.cgi?id=1116450 .
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
10:07 a.m.
On Wed, Jul 09, 2014 at 23:37:39 -0700,
Adam Williamson <adamwill(a)fedoraproject.org> wrote:
sudo yum-config-manager --enable fedora
and, optionally, enable updates-testing:
sudo yum-config-manager --enable updates-testing
The updates-testing repo isn't there yet. I am hoping we get empty
repos created for both updates and updates-testing now. (updates-testing
will be getting used soon, and having an empty updates repo is useful
for avoiding configuration changes between switching to branched and
the release.)
3613
days inactive
3614
days old
7 comments
5 participants
participants (5)
-
Adam Williamson -
Bruno Wolff III -
M. Edward (Ed) Borasky -
poma -
Stephen Gallagher