<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to tickets</title><link>https://sourceforge.net/p/archopenrc/tickets/</link><description>Recent changes to tickets</description><atom:link href="https://sourceforge.net/p/archopenrc/tickets/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 20 Jun 2017 19:11:26 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/archopenrc/tickets/feed.rss" rel="self" type="application/rss+xml"/><item><title>#2 armhf eudev / openrc packages missing</title><link>https://sourceforge.net/p/archopenrc/tickets/2/?limit=250#559e</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;i am now extremely puzzled as to how i ever managed to get openrc, eudev and nosystemd up and running on an armv7h system at all!  i do not recall ever doing a package build!&lt;/p&gt;
&lt;p&gt;aaditya: i did the initial armv7h bootstrap via a complex process of downloading a live boot parabola iso image, running that under qemu, activating nfs client to mount a filesystem on my laptop as well as setting up an http and dns proxy on the laptop, then i followed the standard parabola / archlinux armv7h bootstrap instructions &lt;em&gt;inside qemu&lt;/em&gt; which &lt;em&gt;involved installing and running qemu under qemu&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;whilst you may not need to go to the extreme lengths of running qemu-arm under qemu-x86 as i did you can simply run qemu-arm from a native system (as long as you have an armv7h rootfs already).&lt;/p&gt;
&lt;p&gt;parabola does not have an armv7h iso but archlinux almost certainly does.&lt;/p&gt;
&lt;p&gt;so it is therefore quite easy - if you know what you are doing - to compile packages for armv7h within qemu-arm, in fact the firefox package was prepared last year in this way.  the only thing to watch out for is never to use swap space within qemu-arm.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Luke Kenneth Casson Leighton</dc:creator><pubDate>Tue, 20 Jun 2017 19:11:26 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net939eae2c50adbaa5481747146f63b32131ac9175</guid></item><item><title>#2 armhf eudev / openrc packages missing</title><link>https://sourceforge.net/p/archopenrc/tickets/2/?limit=25#dc8d</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I have a raspberry pi 3 on which I tested compiling some OpenRC packages, but could not finish it due to lack of time.&lt;/p&gt;
&lt;p&gt;What is needed I guess is to add 'armv7' arch (or other arm architectures to build for) to the PKGBUILDS, build and test the packages, and upload them to the repo.&lt;/p&gt;
&lt;p&gt;I have also read about cross compiling arm packages on x86_64; if a system for that could be setup that could be helpful as well.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br/&gt;
Aaditya&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Aaditya Bagga</dc:creator><pubDate>Tue, 20 Jun 2017 17:16:55 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net32758c7e7bd891fb284a1f8f9bb5821cd1be18fb</guid></item><item><title>#2 armhf eudev / openrc packages missing</title><link>https://sourceforge.net/p/archopenrc/tickets/2/?limit=25#6927</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I have a raspberry pi 3 on which I tested compiling some OpenRC packages, but could not finish it due to lack of time.&lt;/p&gt;
&lt;p&gt;What is needed I guess is to add 'armv7' arch (or other arm architectures to build for) to the PKGBUILDS, build and test the packages, and upload them to the repo.&lt;/p&gt;
&lt;p&gt;I have also read about cross compiling arm packages on x86_64; if a system for that could be setup that could be helpful as well.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br/&gt;
Aaditya&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Aaditya Bagga</dc:creator><pubDate>Tue, 20 Jun 2017 17:16:35 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net72ab27d0d2b67b160d12880c3771642266c20d75</guid></item><item><title>#2 armhf eudev / openrc packages missing</title><link>https://sourceforge.net/p/archopenrc/tickets/2/?limit=100#a76c</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Sadly, there has never been an ARM port... We are just a couple of people doing most of the work and none of us owns an ARM box, not to mention our serious lack of free time. You are very welcome to take over the ARM port and/or help with the OpenRC/eudev project in general.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nous</dc:creator><pubDate>Tue, 20 Jun 2017 13:16:26 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net9c79fb22b9d53c30972b789bae1f559322c9306e</guid></item><item><title>armhf eudev / openrc packages missing</title><link>https://sourceforge.net/p/archopenrc/tickets/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;hi, i started a crowdfunding campaign to provide an armhf eco-conscious computer, i have something like 200 people to provide parabola gnu/linux-libre to them.  in june-august 2016 eudev, openrc and nosystemd were installed successfully (systemd will not be distributed to them as its entire development and deployment has been done unethically).&lt;/p&gt;
&lt;p&gt;so the arm port of eudev and openrc is critical to the project's success.&lt;/p&gt;
&lt;p&gt;on returning to the root image in order to perform an upgrade it would appear that the arm port is entirely missing... or that i can no longer find it.  any clues?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Luke Kenneth Casson Leighton</dc:creator><pubDate>Tue, 20 Jun 2017 11:49:05 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net67f4d75438d2e3c7a9640428cd439bb6d273be38</guid></item><item><title>#1 openrc</title><link>https://sourceforge.net/p/archopenrc/tickets/1/?limit=100#3741</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nous</dc:creator><pubDate>Sun, 14 Feb 2016 16:38:29 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5e1b5576423eaec284cc51c0b7e4e4331bcad6ab</guid></item><item><title>#1 openrc</title><link>https://sourceforge.net/p/archopenrc/tickets/1/?limit=100#1690</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The respective PKGBUILD sources /etc/os-release, there's no need to hardcode anything. The reason "Manjaro" was compiled-in is that probably compiled it on a &lt;em&gt;Manjaro&lt;/em&gt; box, after all (I no longer use Arch in new installations). It skipped my attention because I use extensively TuxOnIce hibernation and I haven't rebooted my boxes for several weeks. Anyway, I've uploaded an updated package (x86_64 only).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nous</dc:creator><pubDate>Sun, 14 Feb 2016 16:33:50 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net250f9aad46ab8c18df93f683a4acc6004aa6d891</guid></item><item><title>#1 openrc</title><link>https://sourceforge.net/p/archopenrc/tickets/1/?limit=25#6fe6</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I was having a look at the code upstream at the manjaro github. In /openrc/src/rc/version.h there is a string called "BRANDING", that is what is displayed when openrc starts. Somehow this got changed to "Manjaro" instead of "Arch linux", however since I compiled from upstream the string is set to "Arch linux" even though it is the majaro github. So that is why it fixed it when I compiled it. Just a simple change to "Arch linux" and this will be fixed.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Cromer</dc:creator><pubDate>Sun, 14 Feb 2016 16:18:52 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net913855199b9dffcb5a910fcfba631856cf340419</guid></item><item><title>#1 openrc</title><link>https://sourceforge.net/p/archopenrc/tickets/1/?limit=100#4f8e</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Actually, it &lt;em&gt;was&lt;/em&gt; compiled on an Arch box, obviously lacking /etc/os-release. I'll try to fix our build script soon.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nous</dc:creator><pubDate>Sun, 14 Feb 2016 14:16:55 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netcfe044bcf2450c8b745fd1667d3601c089550106</guid></item><item><title>openrc</title><link>https://sourceforge.net/p/archopenrc/tickets/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;There is tiny problem with openrc-0.20.4-1-x86_64.pkg.tar.xz. When it was compiled, it was compiled on a manjaro box, not on an arch linux box. This causes it to say "OpenRC is starting Manjaro" on my arch linux machine. I downloaded the source, compiled it, and installed it to get rid of that manjaro text while booting. However that is only a temp solution since I am using this repo and surely it will at some point appear again when I update via pacman.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Cromer</dc:creator><pubDate>Sat, 13 Feb 2016 02:14:03 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net6b069f652e7f3ebbde14f8d1483be325f382e81c</guid></item></channel></rss>