<?xml version="1.0" ?>
<rss version="2.0">
  <channel>
    <title>HyperTask </title>
    <lastBuildDate>Sat, 27 Jun 2026 20:02:21 +0000</lastBuildDate>
    <description>software</description>
    <link>https://issues.hyperbola.info/</link>
        <item>
      <title>FS#761: Develop a BSD descendant kernel for HyperbolaBSD</title>
      <author>André Silva</author>
      <pubDate>Mon, 04 Jun 2018 23:15:08 +0000</pubDate>
      <description><![CDATA[
<p>
Develop HyperBK (Hyper Berkeley Kernel), a BSD descendant kernel with <acronym title="GNU General Public License">GPL</acronym>-compatible licenses preserved, non-compatible ones removed, and new code written under <acronym title="GNU General Public License">GPL</acronym>-3 for HyperbolaBSD.
</p>

<p>
TODO:
</p>
<ul>
<li class="level1"><div class="li"> Download OpenBSD kernel source code from <a href="https://ftp.openbsd.org/pub/OpenBSD/" class="urlextern" title="https://ftp.openbsd.org/pub/OpenBSD/"  rel="nofollow">OpenBSD site</a><a href="https://wiki.hyperbola.info/" class="internallink"></a> → <strong>DONE</strong></div>
</li>
</ul>
<ul>
<li class="level1"><div class="li"> Download LibertyBSD scripts to deblob and rebrand kernel from <a href="https://git.hyperbola.info:50100/kernels/libertybsd-scripts.git/" class="urlextern" title="https://git.hyperbola.info:50100/kernels/libertybsd-scripts.git/"  rel="nofollow">their scripts</a><a href="https://wiki.hyperbola.info/" class="internallink"></a>. → <strong>DONE</strong></div>
</li>
</ul>
<ul>
<li class="level1"><div class="li"> Create a new project in <a href="https://git.hyperbola.info" class="urlextern" title="https://git.hyperbola.info"  rel="nofollow">Hyperbola Git</a><a href="https://wiki.hyperbola.info/" class="internallink"></a> called hyperbk. → <strong><a href="https://git.hyperbola.info:50100/hyperbolabsd/hyperbk.git/" class="urlextern" title="https://git.hyperbola.info:50100/hyperbolabsd/hyperbk.git/"  rel="nofollow">DONE</a><a href="https://wiki.hyperbola.info/" class="internallink"></a></strong></div>
</li>
</ul>
<ul>
<li class="level1"><div class="li"> Push source to HyperBK&#8217;s project. → <strong>DONE</strong></div>
</li>
</ul>
<ul>
<li class="level1"><div class="li"> Rebrand OpenBSD kernel to HyperbolaBSD with LibertyBSD scripts. → <strong>DONE</strong></div>
</li>
</ul>
<ul>
<li class="level1"><div class="li"> Rebrand entire code (functions, variable, pointers, etc) under HyperbolaBSD → <strong>DONE</strong></div>
</li>
</ul>
<ul>
<li class="level1"><div class="li"> Remove files under non <acronym title="GNU General Public License">GPL</acronym>-compatible licenses → <strong>DONE</strong></div>
</li>
</ul>
<ul>
<li class="level1"><div class="li"> Import code from another BSD systems under <acronym title="GNU General Public License">GPL</acronym>-compatible licenses → <strong>IN PROGRESS</strong></div>
</li>
</ul>
<ul>
<li class="level1"><div class="li"> Remove <a href="https://notabug.org/jadedctrl/libertybsd-scripts-mirror/issues/5" class="urlextern" title="https://notabug.org/jadedctrl/libertybsd-scripts-mirror/issues/5"  rel="nofollow">remaining nonfree files don&#039;t found from LibertyBSD scripts</a><a href="https://wiki.hyperbola.info/" class="internallink"></a> → <strong>IN PROGRESS</strong></div>
</li>
</ul>
<ul>
<li class="level1"><div class="li"> Write new code under <acronym title="GNU General Public License">GPL</acronym>-3 → <strong>IN PROGRESS</strong></div>
</li>
</ul>
<ul>
<li class="level1"><div class="li"> Package HyperBK for HyperbolaBSD.</div>
</li>
</ul>

<p>
 <strong>PATCHING NOTE</strong>
</p>
<pre class="code">
When the check concerns kernel, we obviously want to match with HyperbolaBSD.

Example of triplet check:	hyperbolabsd)
Example of uname -s check:	HyperbolaBSD)
Example of uname -r check:	0.1)
Example of C macro check:	defined(__HyperbolaBSD__)
</pre>
]]></description>
      <link>https://issues.hyperbola.info/index.php?do=details&amp;task_id=761</link>
      <guid>https://issues.hyperbola.info/index.php?do=details&amp;task_id=761</guid>
    </item>
        <item>
      <title>FS#1567: [chroot-nspawn] Create mount points if mountpoint exit code is different to zero</title>
      <author>David P.</author>
      <pubDate>Sat, 03 Jul 2021 03:03:46 +0000</pubDate>
      <description><![CDATA[
<p>
The actual behavior is to create mount points if mountpoint exits with exit status 1, however it may also exit with code 32 and thus creating a real mess: 
</p>
<pre class="code">$ sudo chroot-nspawn
Spawning container megver83 on /var/lib/archbuild/chroot1/megver83
Press ^] three times within 1s to kill container.
mount: /sys/fs/cgroup: mount point does not exist.
mkdir: cannot create directory &#039;/sys/fs/cgroup/blkio&#039;: No such file or directory
ln: failed to create symbolic link &#039;/sys/fs/cgroup/cpu&#039;: No such file or directory
ln: failed to create symbolic link &#039;/sys/fs/cgroup/cpuacct&#039;: No such file or directory
mkdir: cannot create directory &#039;/sys/fs/cgroup/cpu,cpuacct&#039;: No such file or directory
mkdir: cannot create directory &#039;/sys/fs/cgroup/cpuset&#039;: No such file or directory
mkdir: cannot create directory &#039;/sys/fs/cgroup/devices&#039;: No such file or directory  
mkdir: cannot create directory &#039;/sys/fs/cgroup/freezer&#039;: No such file or directory
mkdir: cannot create directory &#039;/sys/fs/cgroup/memory&#039;: No such file or directory
ln: failed to create symbolic link &#039;/sys/fs/cgroup/net_cls&#039;: No such file or directory
mkdir: cannot create directory &#039;/sys/fs/cgroup/net_cls,net_prio&#039;: No such file or directory
ln: failed to create symbolic link &#039;/sys/fs/cgroup/net_prio&#039;: No such file or directory
mkdir: cannot create directory &#039;/sys/fs/cgroup/pids&#039;: No such file or directory
mkdir: cannot create directory &#039;/sys/fs/cgroup/systemd&#039;: No such file or directory
mount: /sys/fs/cgroup/blkio: mount point does not exist.
mount: /sys/fs/cgroup/cpuset: mount point does not exist.
mount: /sys/fs/cgroup/devices: mount point does not exist.
mount: /sys/fs/cgroup/freezer: mount point does not exist.
mount: /sys/fs/cgroup/memory: mount point does not exist.
mount: /sys/fs/cgroup/pids: mount point does not exist.</pre>

<p>
 So I created a patch to fix this.
</p>

<p>
P.S.: although I can git clone the repo with ssh access, whenever I do a push I get:
</p>
<pre class="code">error: remote unpack failed: unable to create temporary object directory
To ssh://git.hyperbola.info:51100/~git/software/chroot-nspawn.git
 ! [remote rejected] master -&gt; master (unpacker error)
error: failed to push some refs to &#039;ssh://git.hyperbola.info:51100/~git/software/chroot-nspawn.git&#039;</pre>

<p>
 Do I have the permission to write in this repo? If not, I&#8217;d like it, as I&#8217;m planning to improve this great script<br />
</p>
]]></description>
      <link>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1567</link>
      <guid>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1567</guid>
    </item>
        <item>
      <title>FS#1572: [Website] Rework for the onion-page</title>
      <author>Tobias Dausend</author>
      <pubDate>Tue, 27 Jul 2021 21:32:02 +0000</pubDate>
      <description><![CDATA[
<p>
As proposed in a separate thread (<a href="https://forums.hyperbola.info/viewtopic.php?id=573" class="urlextern" title="https://forums.hyperbola.info/viewtopic.php?id=573"  rel="nofollow">https://forums.hyperbola.info/viewtopic.php?id=573</a><a href="https://wiki.hyperbola.info/" class="internallink"></a>): The navigation-bar needs a rework when accessing the website about the onion-protocol.<br />
</p>
]]></description>
      <link>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1572</link>
      <guid>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1572</guid>
    </item>
        <item>
      <title>FS#1528: CardBook addon make icedove crash wen adding or editing a new contact </title>
      <author>anonymous</author>
      <pubDate>Fri, 18 Dec 2020 19:57:27 +0000</pubDate>
      <description><![CDATA[
<p>
the cardbook version is 30.9 i tried with vcard 4.0 and vcard 3.0 same issue editing or creating a contact makes<br />icedove-uxp crash!<br />
</p>
]]></description>
      <link>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1528</link>
      <guid>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1528</guid>
    </item>
        <item>
      <title>FS#1099: Swiftdove-UXP theme for Icedove-UXP</title>
      <author>André Silva</author>
      <pubDate>Sun, 15 Jul 2018 22:16:56 +0000</pubDate>
      <description><![CDATA[
<p>
Description:<br />Historically, Swiftdove was a Thunderbird-based application built on <acronym title="XML User Interface Language">XUL</acronym> platform around 2007 and abandoned in 2010. It was optimized for several architectures using the following methods such as the Profile-Guided Optimization (PGO) and binary code optimization for computers with limited resources.
</p>

<p>
Since FossaMail may potentially be revived on UXP in the future <a href="https://www.fossamail.org/" class="urlextern" title="https://www.fossamail.org/"  rel="nofollow"> [0] </a><a href="https://wiki.hyperbola.info/" class="internallink"></a> and Swiftdove contains non-trademarked graphics and logos, we could port Swiftdove to UXP platform as theme for Icedove-UXP.<br />
</p>
]]></description>
      <link>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1099</link>
      <guid>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1099</guid>
    </item>
        <item>
      <title>FS#1098: Swiftweasel-UXP theme for Iceweasel-UXP</title>
      <author>André Silva</author>
      <pubDate>Sun, 15 Jul 2018 21:55:39 +0000</pubDate>
      <description><![CDATA[
<p>
Description:<br />Historically, Swiftweasel was a Firefox-based application built on <acronym title="XML User Interface Language">XUL</acronym> platform around 2007 and abandoned in 2010. It was optimized for several architectures using the following methods such as the Profile-Guided Optimization (PGO) and binary code optimization for computers with limited resources.
</p>

<p>
Since <a href="https://forums.hyperbola.info/viewtopic.php?id=104" class="urlextern" title="https://forums.hyperbola.info/viewtopic.php?id=104"  rel="nofollow"> there are users encouraging us develop a Palemoon-based application </a><a href="https://wiki.hyperbola.info/" class="internallink"></a>, and Swiftweasel contains non-trademarked graphics and logos, we could port Swiftweasel to UXP platform as theme for Iceweasel-UXP.<br />
</p>
]]></description>
      <link>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1098</link>
      <guid>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1098</guid>
    </item>
        <item>
      <title>FS#1338: RISC-V (riscv64) porting + multilib support</title>
      <author>André Silva</author>
      <pubDate>Thu, 10 Jan 2019 23:37:52 +0000</pubDate>
      <description><![CDATA[
<p>
The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the <a href="https://www.fsf.org/blogs/licensing/intel-me-and-why-we-should-get-rid-of-me" class="urlextern" title="https://www.fsf.org/blogs/licensing/intel-me-and-why-we-should-get-rid-of-me"  rel="nofollow"> Intel Management Engine </a><a href="https://wiki.hyperbola.info/" class="internallink"></a>, as well as nonfree boot firmware. This means that users can&#8217;t gain full control over their computers, even if they install a free operating system such as <a href="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbola_gnu_linux-libre" class="urlextern" title="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbola_gnu_linux-libre"  rel="nofollow"> Hyperbola GNU/Linux-libre </a><a href="https://wiki.hyperbola.info/" class="internallink"></a>.
</p>

<p>
Hyperbola is working hard to fix these issues and getting closer every day, but for the time being, this is why many current Respects Your Freedom (RYF) offerings are refurbished older devices.
</p>

<p>
For the future of free computing, we need support architectures that do not come with such malware pre-installed, and RISC-V promises to be a great architecture example for low-power computers, laptops and embedded systems, also as ARM architecture replacement.
</p>

<p>
Devices like this are the future of computing that Respects Your Freedom and for that reason it&#8217;s a high priority for Hyperbola port all packages for the RISC-V architecture (riscv64) with multilib support.
</p>

<p>
<strong>NOTE</strong>: RISC-V porting is focused only for <a href="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbola_gnu_linux-libre" class="urlextern" title="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbola_gnu_linux-libre"  rel="nofollow"> Hyperbola GNU/Linux-libre </a><a href="https://wiki.hyperbola.info/" class="internallink"></a>.<br />
</p>
]]></description>
      <link>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1338</link>
      <guid>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1338</guid>
    </item>
        <item>
      <title>FS#1337: ARM (aarch and armv7h) porting</title>
      <author>winter</author>
      <pubDate>Wed, 09 Jan 2019 04:09:54 +0000</pubDate>
      <description><![CDATA[
<p>
The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the <a href="https://www.fsf.org/blogs/licensing/intel-me-and-why-we-should-get-rid-of-me" class="urlextern" title="https://www.fsf.org/blogs/licensing/intel-me-and-why-we-should-get-rid-of-me"  rel="nofollow"> Intel Management Engine </a><a href="https://wiki.hyperbola.info/" class="internallink"></a>, as well as nonfree boot firmware. This means that users can&#8217;t gain full control over their computers, even if they install a free operating system such as <a href="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbola_gnu_linux-libre" class="urlextern" title="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbola_gnu_linux-libre"  rel="nofollow"> Hyperbola GNU/Linux-libre </a><a href="https://wiki.hyperbola.info/" class="internallink"></a>.
</p>

<p>
Hyperbola is working hard to fix these issues and getting closer every day, but for the time being, this is why many current Respects Your Freedom (RYF) offerings are refurbished older devices.
</p>

<p>
For the future of free computing, we need support architectures that do not come with such malware pre-installed, and ARM A7/A53 promises to be a great architecture example for low-power computers, laptops and embedded systems.
</p>

<p>
<strong>NOTE</strong>: ARM porting is focused only for <a href="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbolabsd" class="urlextern" title="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbolabsd"  rel="nofollow"> HyperbolaBSD </a><a href="https://wiki.hyperbola.info/" class="internallink"></a>.<br />
</p>
]]></description>
      <link>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1337</link>
      <guid>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1337</guid>
    </item>
        <item>
      <title>FS#1336: POWER (ppc64le) porting</title>
      <author>André Silva</author>
      <pubDate>Wed, 09 Jan 2019 01:23:12 +0000</pubDate>
      <description><![CDATA[
<p>
The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the <a href="https://www.fsf.org/blogs/licensing/intel-me-and-why-we-should-get-rid-of-me" class="urlextern" title="https://www.fsf.org/blogs/licensing/intel-me-and-why-we-should-get-rid-of-me"  rel="nofollow"> Intel Management Engine </a><a href="https://wiki.hyperbola.info/" class="internallink"></a>, as well as nonfree boot firmware. This means that users can&#8217;t gain full control over their computers, even if they install a free operating system such as <a href="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbola_gnu_linux-libre" class="urlextern" title="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbola_gnu_linux-libre"  rel="nofollow"> Hyperbola GNU/Linux-libre </a><a href="https://wiki.hyperbola.info/" class="internallink"></a>.
</p>

<p>
Hyperbola is working hard to fix these issues and getting closer every day, but for the time being, this is why many current Respects Your Freedom (RYF) offerings are refurbished older devices.
</p>

<p>
For the future of free computing, we need support architectures that do not come with such malware pre-installed, and the Power9-based <a href="https://raptorcs.com/TALOSII/" class="urlextern" title="https://raptorcs.com/TALOSII/"  rel="nofollow"> Talos II </a><a href="https://wiki.hyperbola.info/" class="internallink"></a> promises to be a great architecture example for workstations and servers environments where Hyperbola is focused since is a <a href="https://wiki.hyperbola.info/doku.php?id=:en:start#if_hyperbola_is_a_fully_free_distribution_is_it_following_the_gnu_free_system_distribution_guidelines_gnu_fsdg" class="urlextern" title="https://wiki.hyperbola.info/doku.php?id=:en:start#if_hyperbola_is_a_fully_free_distribution_is_it_following_the_gnu_free_system_distribution_guidelines_gnu_fsdg"  rel="nofollow"> fully free </a><a href="https://wiki.hyperbola.info/" class="internallink"></a> <a href="https://wiki.hyperbola.info/doku.php?id=:en:start#what_is_long_term_support_lts" class="urlextern" title="https://wiki.hyperbola.info/doku.php?id=:en:start#what_is_long_term_support_lts"  rel="nofollow"> long-term support </a><a href="https://wiki.hyperbola.info/" class="internallink"></a> distribution.
</p>

<p>
Devices like this are the future of computing that Respects Your Freedom and for that reason it&#8217;s a high priority for Hyperbola port all packages for the POWER architecture (power64le).
</p>

<p>
<strong>NOTE</strong>: POWER porting is focused only for <a href="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbola_gnu_linux-libre" class="urlextern" title="https://wiki.hyperbola.info/doku.php?id=en:main:nomenclatures#hyperbola_gnu_linux-libre"  rel="nofollow"> Hyperbola GNU/Linux-libre </a><a href="https://wiki.hyperbola.info/" class="internallink"></a>.<br />
</p>
]]></description>
      <link>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1336</link>
      <guid>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1336</guid>
    </item>
        <item>
      <title>FS#1151: Request browser add-on: FireGestures</title>
      <author>out-of-project-please-delete-this-account</author>
      <pubDate>Wed, 29 Aug 2018 03:52:23 +0000</pubDate>
      <description><![CDATA[
<p>
<strong></strong>Name:<strong></strong> FireGestures<br /><strong></strong>Version:<strong></strong> 1.11.1 (compatible Firefox version 52)<br /><strong>Source code:</strong> Github<br /><strong>Description:</strong> A customizable mouse gestures extension which enables to execute various commands and user scripts with six types of gestures.
</p>

<p>
<a href="https://github.com/gomita/firegestures/" class="urlextern" title="https://github.com/gomita/firegestures/"  rel="nofollow">https://github.com/gomita/firegestures/</a>
</p>

<p>
<a href="https://addons.mozilla.org/en-US/firefox/addon/firegestures/" class="urlextern" title="https://addons.mozilla.org/en-US/firefox/addon/firegestures/"  rel="nofollow">https://addons.mozilla.org/en-US/firefox/addon/firegestures/</a> 
</p>
]]></description>
      <link>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1151</link>
      <guid>https://issues.hyperbola.info/index.php?do=details&amp;task_id=1151</guid>
    </item>
      </channel>
</rss>
