Adam Williamson composed on 2015-02-11 23:39 (UTC-0800): > On Thu, 2015-02-12 at 07:30 +0000, Russel Winder wrote: >> This morning's update included trying to switch me from Rawhide to >> Branched, is this normal immediately after a release branch? > I *think* that's what the fedora-release packager intended, yeah. I > don't think we did it before (though IMBW), but it's a reasonable > thing to do - it's safer than the alternative (because it's a bit > easier for people who want to be on Rawhide to get from Branched to > Rawhide than it is for people who want to be on Branched to get from > Rawhide to Branched). >> Fix was straightforward as the upgrade was sufficiently careful with >> my files in /etc/yum.repos.d, it just came as a bit of a surprise. > Just installing fedora-repos-rawhide should do the trick, I think. I don't think that agrees with https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum >> BTW Did someone intentional schedule the F22 branch to be a few days >> after the Linux 3.19 release? > Nope, that didn't have anything to do with the scheduling process, > just a pure coincidence. The kernel minor (.18, .19, whatever) that'll > be shipped with a release actually isn't usually set in stone until > Beta, though for F22 I'd expect it'll be 3.19 given how things have > worked out. I've been trying to get any existing installation onto the F22 branch since about 12 hours or so after the branching announcement here. It's been a nightmare. Eventually each time telling me configured repositories failed. This is the data and history on my latest failed attempt: # rpm -qa | grep fedora fedora-bookmarks-15-5.fc21.noarch fedora-icon-theme-1.0.0-16.fc21.noarch fedora-logos-21.0.3-1.fc21.i686 fedora-release-22-0.10.noarch fedora-release-nonproduct-22-0.10.noarch fedora-release-notes-21.08-1.fc21.noarch fedora-repos-22-0.2.noarch fedora-repos-rawhide-22-0.2.noarch # yum repolist Loaded plugins: langpacks, versionlock repo id repo name status fedora/22/i386 Fedora 22 - i386 disabled fedora-debuginfo/22/i386 Fedora 22 - i386 - Debug disabled fedora-source/22/i386 Fedora 22 - Source disabled rawhide/i386 Fedora - Rawhide - Development enabled: 37,264 rawhide-debuginfo/i386 Fedora - Rawhide - Debug disabled rawhide-source/i386 Fedora - Rawhide - Source disabled updates/22/i386 Fedora 22 - i386 - Updates disabled updates-debuginfo/22/i386 Fedora 22 - i386 - Updates - D disabled updates-source/22/i386 Fedora 22 - Updates Source disabled updates-testing/22/i386 Fedora 22 - i386 - Test Update disabled updates-testing-debuginfo/22/i386 Fedora 22 - i386 - Test Update disabled updates-testing-source/22/i386 Fedora 22 - Test Updates Sourc disabled repolist: 37,264 # yum-config-manager --disable rawhide # yum-config-manager --enable fedora updates updates-testing # yum repolist all Loaded plugins: langpacks, versionlock One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> 4. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true File /var/cache/yum/i386/22/fedora/metalink.xml does not exist Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-22&arch=i386 error was No repomd file # yum repolist disabled Loaded plugins: langpacks, versionlock repo id repo name fedora-debuginfo/22/i386 Fedora 22 - i386 - Debug fedora-source/22/i386 Fedora 22 - Source rawhide/i386 Fedora - Rawhide - Developmental packages for rawhide-debuginfo/i386 Fedora - Rawhide - Debug rawhide-source/i386 Fedora - Rawhide - Source updates-debuginfo/22/i386 Fedora 22 - i386 - Updates - Debug updates-source/22/i386 Fedora 22 - Updates Source updates-testing-debuginfo/22/i386 Fedora 22 - i386 - Test Updates Debug updates-testing-source/22/i386 Fedora 22 - Test Updates Source repolist: 0 With only rawhide enabled, I tried # yum --releasever=rawhide distro-sync --nogpgcheck That, like so many tries in past couple of days seemed to go OK for while, but eventually during installation/updating of packages, the process simply stops dead with no messages on the active tty. Last messages on tty10 currently are 4 rows of dbus[400]: [system] Reloaded configuration. Top is showing nothing actually using more than nominal CPU. Last listed package is currently rtkit, but in prior attempts I've seen avahi at least, if not others as the stopping point. What's it going to take to get onto the f22 branch? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
