{"id":1054,"date":"2014-02-18T10:21:30","date_gmt":"2014-02-18T10:21:30","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=1054"},"modified":"2014-02-18T10:21:30","modified_gmt":"2014-02-18T10:21:30","slug":"arm-the-secret-is-out-pidora-2014-is-here","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=1054","title":{"rendered":"ARM &#8211; The Secret is Out &#8211; &#8216;Pidora 2014&#8217; is Here.."},"content":{"rendered":"<p>Thanks to invaluable information from <strong>Mace Moneta<\/strong>, I have now been able to find the location of the (recent) release of Pidora 20 &#8212; now, for some reason, known as &#8216;<strong>Pidora 2014<\/strong>&#8216;..<\/p>\n<p>For details and links, see the comments section at the bottom of my previous article: <a title=\"https:\/\/rglinuxtech.com\/?p=1048\" href=\"https:\/\/rglinuxtech.com\/?p=1048\" target=\"_blank\">https:\/\/rglinuxtech.com\/?p=1048<\/a><\/p>\n<p>I started the upgrade (from Pidora 19), which took several hours after the downloads had finished, and showed just how <span style=\"text-decoration: underline;\">slow<\/span> the Pi is!<\/p>\n<p>After the download had completed, the first attempt to upgrade failed:<\/p>\n<pre><strong>Running transaction check<\/strong>\r\n<strong>Running transaction test<\/strong>\r\n\r\n<strong>Transaction check error:<\/strong>\r\n<strong>\u00a0 file \/usr\/share\/pixmaps\/poweredby.png conflicts between attempted installs of pidora-logos-1-5.rpfr20.noarch and fedora-logos-httpd-21.0.1-1.fc20.noarch<\/strong><\/pre>\n<p>So.. I re-ran the upgrade, as follows:<\/p>\n<pre><strong># yum --nogpgcheck distro-sync --exclude=pidora-logos<\/strong><\/pre>\n<p>Many warning messages scrolled by:<\/p>\n<pre><strong>.......<\/strong>\r\n<strong>\/sbin\/ldconfig: libraries libgpg-error.so.0.9.0 and libgpg-error.so.0.10.0 in directory \/lib have same soname but different type.<\/strong>\r\n<strong>\u00a0 Updating\u00a0\u00a0 : 2:libogg-1.3.0-6.fc20.armv6hl\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 101\/2042 <\/strong>\r\n<strong>\/sbin\/ldconfig: libraries libfreetype.so.6.10.0 and libfreetype.so.6.10.2 in directory \/lib have same soname but different type.<\/strong>\r\n<strong>\/sbin\/ldconfig: libraries libgpg-error.so.0.9.0 and libgpg-error.so.0.10.0 in directory \/lib have same soname but different type.<\/strong>\r\n<strong>\u00a0 Updating\u00a0\u00a0 : libtevent-0.9.19-1.fc20.armv6hl\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 102\/2042 <\/strong>\r\n<strong>\/sbin\/ldconfig: libraries libfreetype.so.6.10.0 and libfreetype.so.6.10.2 in directory \/lib have same soname but different type.<\/strong>\r\n<strong>\/sbin\/ldconfig: libraries libgpg-error.so.0.9.0 and libgpg-error.so.0.10.0 in directory \/lib have same soname but different type.<\/strong>\r\n<strong>.........\u00a0 etc...<\/strong><\/pre>\n<p>But &#8211; finally &#8211; the upgrade completed..<\/p>\n<p>Then, any attempt to do a <strong><em># y<\/em><\/strong><em><strong>um update<\/strong><\/em> failed, due to the previous conflict:<\/p>\n<pre><strong>Transaction check error:<\/strong>\r\n<strong>\u00a0 file \/usr\/share\/pixmaps\/poweredby.png from install of pidora-logos-1-5.rpfr20.noarch conflicts with file from package fedora-logos-httpd-21.0.1-1.fc20.noarch<\/strong><\/pre>\n<p>The usual <span style=\"font-family: courier new,courier;\"><em><strong># yum -y update &#8211;nogpgcheck\u00a0 &#8211;skip-broken<\/strong><\/em><\/span>\u00a0 doesn&#8217;t fix this, and this conflict stops any further yum updates from completing&#8230;<\/p>\n<p>So&#8230;\u00a0 I manually downloaded the <strong>pidora-logos-1-5.rpfr20.noarch<\/strong> rpm, from <a title=\"http:\/\/koji.pidora.ca\/koji\/buildinfo?buildID=77112\" href=\"http:\/\/koji.pidora.ca\/koji\/buildinfo?buildID=77112\" target=\"_blank\">http:\/\/koji.pidora.ca\/koji\/buildinfo?buildID=77112<\/a>, and &#8216;forced&#8217; the install, using<\/p>\n<pre><strong>rpm -ivh &lt;rpm file&gt; --nodeps --force..<\/strong><\/pre>\n<p>Finally!<\/p>\n<pre><strong>Pidora release 2014 (Raspberry Pi Fedora Remix)<\/strong>\r\n<strong>Kernel 3.13.3+ on an armv6l (ttyAMA0)<\/strong><\/pre>\n<p>&#8211; and Yum works OK, now..<\/p>\n<p>After all the hard work that has gone in to producing this Pidora distro, I can&#8217;t understand why the release is so badly publicised..\u00a0\u00a0 The &#8216;Pidora&#8217; Wiki hasn&#8217;t been updated for months, and still just refers to &#8216;Pidora 18&#8217;, as does the entry on the Raspberry Pi website itself..\u00a0\u00a0 Hopefully this will change, soon..<\/p>\n<p><em>Robert Gadsdon.\u00a0\u00a0 February 18, 2014.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Thanks to invaluable information from Mace Moneta, I have now been able to find the location of the (recent) release of Pidora 20 &#8212; now, for some reason, known as &#8216;Pidora 2014&#8216;.. For details and links, see the comments section at the bottom of my previous article: https:\/\/rglinuxtech.com\/?p=1048 I started the upgrade (from Pidora 19), which took <span class=\"excerpt-dots\">&hellip;<\/span> <a class=\"more-link\" href=\"https:\/\/rglinuxtech.com\/?p=1054\"><span class=\"more-msg\">Continue reading &rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[5,6,11,16,794,704,707],"tags":[807,805,806,306,313,1175,381,418],"class_list":["post-1054","post","type-post","status-publish","format-standard","hentry","category-compilation","category-crash-and-burn","category-hacks","category-linux-arm","category-odroid","category-pidora-2","category-repo-problems","tag-kernel-3-13-3","tag-pidora-20","tag-pidora-2014","tag-problems","tag-raspberry-pi-2","tag-success","tag-upgrade","tag-workaround"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1054","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1054"}],"version-history":[{"count":1,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1054\/revisions"}],"predecessor-version":[{"id":1055,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1054\/revisions\/1055"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1054"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1054"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1054"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}