|
Software Development | General | Bug Report | Medium | Critical | [xenocara] Server is not able to be started via xdm | Unconfirmed | |
Task Description
With the newest package-update the xserver xenocara has missing dependencies towards adobe-fonts and twm.
|
|
Software Development | HyperTools | Implementation Request | Low | Low | [hypertools] create libretools replacement for Hyperbol... | Deferred | |
Task Description
Create hypertools to replace libretools package for HyperbolaBSD and GNU/Linux
It’s long period to develop this package. For now, a systemd-nspawn wrapper is being developed for “libretools”[0]
[0]:https://issues.hyperbola.info/index.php?do=details&task_id=86
|
|
Software Development | chroot-nspawn | Bug Report | Medium | Medium | [chroot-nspawn] Create mount points if mountpoint exit ... | Unconfirmed | |
Task Description
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:
$ 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 '/sys/fs/cgroup/blkio': No such file or directory
ln: failed to create symbolic link '/sys/fs/cgroup/cpu': No such file or directory
ln: failed to create symbolic link '/sys/fs/cgroup/cpuacct': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/cpu,cpuacct': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/cpuset': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/devices': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/freezer': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/memory': No such file or directory
ln: failed to create symbolic link '/sys/fs/cgroup/net_cls': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/net_cls,net_prio': No such file or directory
ln: failed to create symbolic link '/sys/fs/cgroup/net_prio': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/pids': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/systemd': 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.
So I created a patch to fix this.
P.S.: although I can git clone the repo with ssh access, whenever I do a push I get:
error: remote unpack failed: unable to create temporary object directory
To ssh://git.hyperbola.info:51100/~git/software/chroot-nspawn.git
! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'ssh://git.hyperbola.info:51100/~git/software/chroot-nspawn.git'
Do I have the permission to write in this repo? If not, I’d like it, as I’m planning to improve this great script
|
|
Packages | Testing | Bug Report | High | Critical | Runit errors, | Unconfirmed | |
Task Description
/sbin/openrc-run: bad interpreter: No such file or directory
I get this error whenever I try to start dhcpcd with sv /etc/runit/
And for sndiod I get this doing the same guide,
warning: sndiod: unable to open supervise/ok: file does not exist
Although rather ironically, If I type sndiod or dhcpcd into root, it works just fine.
Maybe its an FHS issue or possibly, I am screwing up? I am not sure. Feedback is welcome.
This is what I did:
=⇒ Add a service:
ln -s /etc/sv/<service> /var/service
==> Start/stop/restart a service:
sv <start/stop/restart> <service>
more or less, I used this guide.
|
|
Software Development | General | Implementation Request | Defer | Critical | RISC-V (riscv64) porting + multilib support | Deferred | |
Task Description
The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the Intel Management Engine , as well as nonfree boot firmware. This means that users can’t gain full control over their computers, even if they install a free operating system such as Hyperbola GNU/Linux-libre .
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.
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.
Devices like this are the future of computing that Respects Your Freedom and for that reason it’s a high priority for Hyperbola port all packages for the RISC-V architecture (riscv64) with multilib support.
NOTE: RISC-V porting is focused only for Hyperbola GNU/Linux-libre .
|
|
Software Development | General | Implementation Request | Very High | Critical | POWER (ppc64le) porting | Deferred | |
Task Description
The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the Intel Management Engine , as well as nonfree boot firmware. This means that users can’t gain full control over their computers, even if they install a free operating system such as Hyperbola GNU/Linux-libre .
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.
For the future of free computing, we need support architectures that do not come with such malware pre-installed, and the Power9-based Talos II promises to be a great architecture example for workstations and servers environments where Hyperbola is focused since is a fully free long-term support distribution.
Devices like this are the future of computing that Respects Your Freedom and for that reason it’s a high priority for Hyperbola port all packages for the POWER architecture (power64le).
NOTE: POWER porting is focused only for Hyperbola GNU/Linux-libre .
|
|
Software Development | HyperBK | Implementation Request | Very High | Critical | Develop a BSD descendant kernel for HyperbolaBSD | In Progress | |
Task Description
Develop HyperBK (Hyper Berkeley Kernel), a BSD descendant kernel with GPL-compatible licenses preserved, non-compatible ones removed, and new code written under GPL-3 for HyperbolaBSD.
TODO:
Download OpenBSD kernel source code from OpenBSD site → DONE
Download LibertyBSD scripts to deblob and rebrand kernel from their scripts. → DONE
Remove files under non GPL-compatible licenses → DONE
Import code from another BSD systems under GPL-compatible licenses → IN PROGRESS
Write new code under GPL-3 → IN PROGRESS
PATCHING NOTE
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__)
|
|
Software Development | General | Implementation Request | Very High | Critical | ARM (aarch and armv7h) porting | Deferred | |
Task Description
The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the Intel Management Engine , as well as nonfree boot firmware. This means that users can’t gain full control over their computers, even if they install a free operating system such as Hyperbola GNU/Linux-libre .
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.
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.
NOTE: ARM porting is focused only for HyperbolaBSD .
|