On 07/24/2014 01:56 AM, Adam Williamson wrote:
Hi, folks. Just a note for those following 21 (Branched) or 22 (Rawhide): I noticed today that several of my /etc/yum.repos.d/*.repo files had .rpmnew versions, including my fedora.repo and fedora-updates-testing.repo and fedora-rawhide.repo ,
Hi Adam,
you must have enabled only one repo at a time among these 2 - fedora.repo + fedora-updates-testing.repo OR fedora-rawhide.repo ? What I know is if we need F21 disable the Rawhide repository and enable the regular Fedora repositories + enable updates-testing AND
for F22 enable fedora-rawhide.repo. Thanks & Regards, Amita
even though I didn't recall manually editing them. This meant the metadata_expire setting for my fedora.repo was 7d, so I wasn't seeing any F21 updates. So keep an eye out, and copy the .rpmnew version into production if necessary. Also note that the F21 repo definitions already have 'gpgcheck=1', even though the F21 packages won't be consistently signed until Bodhi use kicks in for F21. So you'll need to pass --nogpgcheck on the command line for now (or edit the repos, but then you'll get rpmnew files again in future...)
-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
