Parabola Issue Tracker: Issueshttps://labs.parabola.nu/https://labs.parabola.nu/favicon.ico?15367742552024-03-27T19:51:10ZParabola Issue Tracker
Redmine Packages - Bug #3616 (unconfirmed): [qutebrowser] Wrongly pinned to 2.5.xhttps://labs.parabola.nu/issues/36162024-03-27T19:51:10ZThe-Compiler
<p>The PKGBUILD claims that:</p>
<blockquote>
<p>- freeze at v2.5.x (final releases with webkit support)</p>
</blockquote>
<p>This is incorrect. The current v3.1.0 release still supports QtWebKit.</p> Packages - Bug #3614 (unconfirmed): error starting apparmor https://labs.parabola.nu/issues/36142024-03-26T10:09:20ZCtIa
<p>I tried to start AppArmor on linux-libre-hardened, linux-libre, linux-libre-lts and linux-libre-zen with openrc but it fails with that error:<br /><pre>
[user@parabola ~]$ sudo rc-service apparmor start
doas (user@parabola) password:
* Starting AppArmor ...
* Loading AppArmor profiles ...
Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
Warning: unable to find a suitable fs in /proc/mounts, is it mounted?
Use --subdomainfs to override.
* At least one profile failed to load [ !! ]
</pre></p> Packages - Freedom Issue #3609 (open): List of core freedom issues affecting work in Parabola.https://labs.parabola.nu/issues/36092024-03-21T14:59:45ZGNUtooGNUtoo@cyberdimension.org
<p>This bug is meant to track freedom issues affecting core components in Parabola.</p>
<p>For instance Pacman is a core component in Parabola since almost anything else depend on it.</p>
<p>Libretools is also required for working on Parabola as well as package definitions.</p>
<p>While there are often freedom issues found in regular packages (for instance a game being nonfree) the impact of these is more limited because it only affect a subset of users and doesn't affect packages required to contribute to Parabola (which are needed to fix these issues in the first place). Some packages (like u-boot for instance) can be critical to some users or use cases but don't affect all the users and contributors to Parabola.</p> Packages - Freedom Issue #3608 (open): [libretools, devtools-par] librerelease has nonfree softwa...https://labs.parabola.nu/issues/36082024-03-21T14:46:44ZGNUtooGNUtoo@cyberdimension.org
<p>Hi,</p>
<p>While trying to package libretools in another FSDG distribution, I found that it actually depends on/contains nonfree software.</p>
<p>So far I only looked at librerelease as that's the software I'm most interested in packaging, but this has wider implications as lot more files are nonfree (more on that below).</p>
<p>The issue with librerelease from libretools is that it depends on lib/common.sh which comes from devtools-par. And that file has 'License: Unspecified'.</p>
A lot more files in devtools-par have 'License: Unspecified', here's the total number of files:
<ul>
<li>archbuild.in</li>
<li>archco.in</li>
<li>archrelease.in</li>
<li>archrm.in</li>
<li>bash_completion.in</li>
<li>checkpkg.in</li>
<li>commitpkg.in</li>
<li>crossrepomove.in</li>
<li>find-libdeps.in</li>
<li>finddeps.in</li>
<li>lddd.in</li>
<li>lib/archroot.sh</li>
<li>lib/common.sh</li>
<li>lib/valid-tags.sh</li>
<li>rebuildpkgs.in</li>
<li>zsh_completion.in</li>
</ul>
In addition the following files also lack a license:
<ul>
<li>.gitignore</li>
<li>Makefile</li>
<li>PKGBUILD.proto</li>
<li>makepkg-x86_64.conf</li>
<li>pacman-extra.conf</li>
<li>pacman-gnome-unstable.conf</li>
<li>pacman-kde-unstable.conf</li>
<li>pacman-multilib-staging.conf</li>
<li>pacman-multilib-testing.conf</li>
<li>pacman-multilib.conf</li>
<li>pacman-staging.conf</li>
<li>pacman-testing.conf</li>
<li>zsh_completion.in</li>
</ul>
Only these files have a valid free software license:
<ul>
<li>arch-nspawn.in</li>
<li>makechrootpkg.in</li>
<li>mkarchroot.in</li>
</ul> Packages - Packaging Request #3607 (open): dhcpcd-openrchttps://labs.parabola.nu/issues/36072024-03-20T22:28:56Znona
<ul>
<li>steps to reproduce:<br /><pre><code class="shell syntaxhl"> <span class="c"># pacman -S dhcpcd-openrc</span>
<span class="c"># rc-service dhcpcd start</span>
</code></pre></li>
</ul>
<ul>
<li>expected result:<br /><pre>
* Caching service dependencies ... [ ok ]
* Starting DHCP Client Daemon ...
</pre></li>
</ul>
<ul>
<li>actual result:<br /><pre>
error: target not found: dhcpcd-openrc
</pre></li>
</ul>
<ul>
<li>suggested workaround<br /><pre><code class="shell syntaxhl"><span class="nv">$ </span>wget https://gitea.artixlinux.org/packages/dhcpcd-openrc/src/branch/master/dhcpcd.initd
<span class="c"># mv dhcpcd.initd /etc/init.d/dhcpcd</span>
<span class="c"># chmod 755 /etc/init.d/dhcpcd</span>
<span class="c"># rc-service dhcpcd start</span>
</code></pre></li>
</ul> Packages - Bug #3604 (unconfirmed): segmentation fault with torsocks iceweaselhttps://labs.parabola.nu/issues/36042024-03-16T11:49:31Znona
<ul>
<li>steps to reproduce:<br /> <code>torsocks iceweasel</code></li>
</ul>
<ul>
<li>expected result:<br /> running window of iceweasel wrapped by torsocks</li>
</ul>
<ul>
<li>actual result:<br /> Segmentation fault</li>
</ul>
<p>iceweasel 1:123.0.1-1.parabola1<br />dbus 1.14.6-2.nonsystemd1<br />dbus-glib 0.112-3<br />dbus-openrc 20210418-2<br />libcloudproviders 0.3.5-1<br />ffmpeg 2:6.1.1-6<br />avahi 1:0.8+r194+g3f79789-1<br />gtk3 1:3.24.41-1<br />libcanberra 1:0.30+r2+gc0620e4-3<br />libpulse 17.0-3.nonsystemd1<br />libxss 1.2.4-1<br />libxt 1.3.0-1<br />libxtst 1.2.4-1<br />mailcap 2.1.54-1<br />jansson 2.14-2<br />libevent 2.1.12-4<br />nss 3.98-1<br />openssh 9.7p1-1<br />openssl 3.2.1-1<br />openssl-1.0 1.0.2.u-3<br />openssl-1.1 1.1.1.w-1<br />gnu-free-fonts 20120503-8</p> Packages - Packaging Request #3603 (open): request for wpa_guihttps://labs.parabola.nu/issues/36032024-03-15T21:26:21Znona
<p>Hi. I found wpa_gui <a class="external" href="https://w1.fi/wpa_supplicant/wpa_gui.html">https://w1.fi/wpa_supplicant/wpa_gui.html</a> . I think that it would make a nice addition for Parabola. Thanks.</p> Packages - Bug #3600 (forwarded upstream): gmtp: error while loading shared libraries: libFLAC.so.8https://labs.parabola.nu/issues/36002024-03-13T18:58:36Zprobiermas
<p>i686-system</p>
<p>steps to reproduce:<br /> 1) # pacman --debug -Syyuu base<br /> 2) # pacman -S gmtp<br /> 3) $ gmtp</p>
<p>expected result:<br /> Start screen of gmtp appears.</p>
<p>actual result:<br /> $ gmtp<br /> gmtp: error while loading shared libraries: libFLAC.so.8: cannot open shared object file: No such file or directory</p> Packages - Bug #3599 (unconfirmed): claws-mail: error while loading shared libraries: liblber-2.4...https://labs.parabola.nu/issues/35992024-03-13T18:49:05Zprobiermas
<p>steps to reproduce:<br /> 1) # pacman --debug -Syyuu base <br /> 2) # pacman -S claws-mail<br /> 3) $ claws-mail</p>
<p>expected result:<br /> splash screen of claws-mail client appears</p>
<p>actual result:</p>
<p>$ claws-mail<br />claws-mail: error while loading shared libraries: liblber-2.4.so.2: cannot open shared object file: No such file or directory</p> Packages - Bug #3592 (confirmed): [jami]: rebuild against latest qt5-base (x86_64)https://labs.parabola.nu/issues/35922024-03-03T21:07:08Zbill-auger
<pre>
$ jami
Using Qt runtime version: 6.6.2
Qt build version mismatch! 6.4.2
Aborted
</pre>
<p>so this should be pinned to 'qt5-base' and added to <a class="issue tracker-9 status-1 priority-3 priority-default parent" title="Housekeeping: [STICKY][qt5-base]: and friends (x86_64) (open)" href="https://labs.parabola.nu/issues/3421">#3421</a></p> Packages - Bug #3591 (unconfirmed): linux-libre & linux-libre-lts kernels- (Potenial bug causing ...https://labs.parabola.nu/issues/35912024-02-25T09:36:55Zryry
<p>Until recently on my armv7h devices, I was recently had been using for a while the linux-libre-vanilla kernel, which worked without issue.</p>
<p>After the recent updates to both the linux-libre and linux-libre-lts kernel I did a usual upgrade of pacman -Syu and updated all fine (though due to another know bug had to copy the vmlinuz for those two kernels). I started with the lts kernel and after within a day I got the following, (please note this is for the linux-libre kernel, but I was getting the same for the lts (which prompted me to switch to the linux-libre kernel to see if was a bug in that kernel or elsewhere.</p>
<p>Feb 22 06:55:10 myhostname kernel: INFO: task syncthing:1827 blocked for more than 120 seconds.<br />Feb 22 06:55:10 myhostname kernel: Tainted: G WC 6.6.8-gnu-1 <a class="issue tracker-1 status-2 priority-5 priority-high3 closed" title="Bug: [bugs/labs] Migrate bug tracker (fixed)" href="https://labs.parabola.nu/issues/1">#1</a><br />Feb 22 06:55:10 myhostname kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.</p>
<p>After which follows a exceptions etc, it did this several times and stops. I thought it might have been a hardware issue until it started doing it on my other armv7h device (a cubieboard) with a newer and bigger drive and to which isn't running syncthing (as i thought it was a bug there) and which had similar timeouts/blocks/hangs for postfix/kworker and systemd.</p>
<p>As a last attempt, I switched back to the linux-libre-vanilla kernel (on both devices) that I had been using before have given it some days to see if the problem reoccurred, it doesn't. Which leads me to reporting this to issue as it may involve the linux-libre and linux-libre-lts kernels or the way in which the interact with something else.</p>
<p>Hope this makes sense<br />Ry</p> Packages - Bug #3584 (forwarded upstream): armv7h packages fail to install - signing key is "unkn...https://labs.parabola.nu/issues/35842024-02-16T01:30:49ZGNUtooGNUtoo@cyberdimension.org
<p>In <a class="external" href="https://repo.parabola.nu/sources/parabola/">https://repo.parabola.nu/sources/parabola/</a> there is no archlinuxarm-keyring-20140119.tar.gz, though there are other packages in libre like hyperbola-keyring.</p>
<p>Unfortunately that source file is not upstream anymore either and Arch Linux ARM doesn't seem to have upgraded its keyring.</p>
<p>So I don't know what to do here.</p> Packages - Bug #3581 (confirmed): [nodejs-bower] TPPMhttps://labs.parabola.nu/issues/35812024-02-13T19:42:27Zwael
<p>Just as with all other TPPMs this has the same common problems. <br />Moreover, the repository is often badly managed, and has been in the news a few times for security breaches.</p> Packages - Housekeeping #3574 (open): [uboot-mx6_cubox-i] Updated versionhttps://labs.parabola.nu/issues/35742024-02-10T12:47:44Zryry
<p>Is it possible for parabola to provide a newer version of u-boot for mx6_cubox-i variants. With not being able to boot any other kernel with the current u-boot version which is quite old, there is no way to boot systems in parabola with any other kernel other than linux-libre and with the issues which are seemingly rectified by, but not pushed to the linux-libre kernel and others (only into the vanilla kernel) regarding some of the issues that it is having at the moment, but which appear fixed by bill-augers install hook, it would be useful to be able to boot other kernels and thus bootable systems again on this device.</p>
<p>I have tried this using the fairly recent u-boot version in trisquels packages, creating and changing the extlinux.conf file to match the correct folders and boot images in parabola and it works pretty much ok, booting vanilla linux-libre.</p>
<p>If not is there a way for me to build them for myself or can I even just use the trisquel one I have flashed to test?</p>
<p>Thanks<br />Ry</p> Installation Media - Housekeeping #3573 (in progress): drop parabolaiso and replace with archisohttps://labs.parabola.nu/issues/35732024-02-06T14:07:52ZMegver83megver83@parabola.nu
<p>parabolaiso, our downstream fork of archiso, is no longer needed. In the past, archiso used to have a build.sh script to build each ISO edition. This was a mess and its devs replaced this method with profiledef.sh, which contains the ISO metadata and centralized the building process in mkarchiso.</p>
<p>In the actual state of archiso, we could directly use it with our custom ISO profile definitions to install our packages and our branding. Plus, there are no freedom nor technical issues AFAIK, like before, were the build.sh script downloaded pre-built binaries of EFI Shell, for example; or support for OpenRC had to added to mkparabolaiso. Nowadays parabolaiso is basically the same as archiso, but with our custom profiles, dual ISO support, removed support for the (optional) proprietary microcode images (from the blacklisted *-ucode packages, so not a big deal, just like with <a href="https://labs.parabola.nu/issues/3562" class="external">mkinitcpio</a>, in Parabola they would never be installed) and armv7 cross-build support.</p>
<p>I just tested a build of Parabola baseline ISO with archiso and went flawlessly. However, if we do drop parabolaiso in favor of archiso, we should update the grub package to include sbat.csv and the en@quot locale, which are the only problems I've found so far when building an ISO with grub bootloader (see the <a href="https://gitlab.archlinux.org/archlinux/archiso/-/blob/5aac945f76d2bf8bb92ba16c9c1c08fc5cae5ab2/archiso/mkarchiso#L692" class="external">source</a>).</p>
<p>One "disadvantage" I see in this would be the loss of the ability to directly build armv7h rootfs from x86, since parabolaiso uses qemu-arm-static for this, like libretools. However, we could workaround this by building from an armv7h chroot. I'm sure a script can be written for this, if there isn't already one.</p>