{"id":531,"date":"2014-01-30T10:03:36","date_gmt":"2014-01-30T15:03:36","guid":{"rendered":"http:\/\/blog.fritzhardy.com\/?p=531"},"modified":"2014-06-24T11:27:09","modified_gmt":"2014-06-24T15:27:09","slug":"fedora-upgrade-f19-f20","status":"publish","type":"post","link":"https:\/\/blog.fritzhardy.com\/?p=531","title":{"rendered":"Fedora Upgrade: F19 -> F20"},"content":{"rendered":"<p>First ensuring I was running fedup-0.8 to avoid the <a href=\"https:\/\/fedoraproject.org\/wiki\/Common_F20_bugs#fedup-07-fail\">fedup-0.7 upgrade bug<\/a>, this <a href=\"https:\/\/blog.fritzhardy.com\/?p=27\" title=\"upgrade\">Fedora upgrade<\/a> was off to the races with <code>fedup --network 20<\/code>.  Unfortunately, after rebooting to the upgrade, my machine ended up wedged at the following:<\/p>\n<pre>systemd[1]: Failed to initialize SELinux context: No such file or directory<\/pre>\n<p>This <a href=\"https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=1044484\">fedup selinux bug<\/a> is easily worked around with <code>selinux=0 enforcing=0<\/code> on the kernel command-line.  Afterwards, the upgrade completed without issue.  I am also pleased to see that one particular <a href=\"https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=1009674\" title=\"bug\">Pidgin bug<\/a> that plagued me throughout Fedora 19 seems to be fixed.<\/p>\n<p>Meanwhile, an unrelated fedup upgrade I conducted on a laptop required that I work around <a href=\"https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=968540\">some<\/a> <a href=\"https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=974000\">bugs<\/a> related to finding my encrypted root partition, by specifying rd.luks.uuid=&lt;uuid&gt; in grub.  I find myself wondering if we as an industry are making adequate progress reconciling and mitigating the increasing problems that come with increasing technical complexity.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>First ensuring I was running fedup-0.8 to avoid the fedup-0.7 upgrade bug, this Fedora upgrade was off to the races with fedup &#8211;network 20. Unfortunately, after rebooting to the upgrade, my machine ended up wedged at the following: systemd[1]: Failed to initialize SELinux context: No such file or directory This fedup selinux bug is easily [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-531","post","type-post","status-publish","format-standard","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/blog.fritzhardy.com\/index.php?rest_route=\/wp\/v2\/posts\/531","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.fritzhardy.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.fritzhardy.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.fritzhardy.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.fritzhardy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=531"}],"version-history":[{"count":10,"href":"https:\/\/blog.fritzhardy.com\/index.php?rest_route=\/wp\/v2\/posts\/531\/revisions"}],"predecessor-version":[{"id":547,"href":"https:\/\/blog.fritzhardy.com\/index.php?rest_route=\/wp\/v2\/posts\/531\/revisions\/547"}],"wp:attachment":[{"href":"https:\/\/blog.fritzhardy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=531"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.fritzhardy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=531"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.fritzhardy.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=531"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}