HyperTask https://issues.hyperbola.info/ software 2022-11-09T15:35:07Z FS#1567: [chroot-nspawn] Create mount points if mountpoint exit code is different to zero https://issues.hyperbola.info/index.php?do=details&task_id=1567 2022-11-09T15:35:07Z David 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: $ 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 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

]]> FS#1099: Swiftdove-UXP theme for Icedove-UXP https://issues.hyperbola.info/index.php?do=details&task_id=1099 2022-07-31T23:05:06Z André Silva Description:Historically, Swiftdove was a Thunderbird-based application built on XUL 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. Since FossaMail may potentially be revived on UXP in the future [0] and Swiftdove contains non-trademarked graphics and logos, we could port Swiftdove to UXP platform as theme for Icedove-UXP. Description:
Historically, Swiftdove was a Thunderbird-based application built on XUL 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.

Since FossaMail may potentially be revived on UXP in the future [0] and Swiftdove contains non-trademarked graphics and logos, we could port Swiftdove to UXP platform as theme for Icedove-UXP.

]]> FS#1098: Swiftweasel-UXP theme for Iceweasel-UXP https://issues.hyperbola.info/index.php?do=details&task_id=1098 2022-07-31T23:04:16Z André Silva Description:Historically, Swiftweasel was a Firefox-based application built on XUL 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. Since there are users encouraging us develop a Palemoon-based application , and Swiftweasel contains non-trademarked graphics and logos, we could port Swiftweasel to UXP platform as theme for Iceweasel-UXP. Description:
Historically, Swiftweasel was a Firefox-based application built on XUL 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.

Since there are users encouraging us develop a Palemoon-based application , and Swiftweasel contains non-trademarked graphics and logos, we could port Swiftweasel to UXP platform as theme for Iceweasel-UXP.

]]> FS#1338: RISC-V (riscv64) porting + multilib support https://issues.hyperbola.info/index.php?do=details&task_id=1338 2022-07-12T22:48:37Z André Silva 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 . 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 .

]]> FS#1337: ARM (aarch and armv7h) porting https://issues.hyperbola.info/index.php?do=details&task_id=1337 2022-07-12T22:47:40Z winter 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 . 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 .

]]> FS#1336: POWER (ppc64le) porting https://issues.hyperbola.info/index.php?do=details&task_id=1336 2022-07-12T22:47:03Z André Silva 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 . 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 .

]]> FS#1151: Request browser add-on: FireGestures https://issues.hyperbola.info/index.php?do=details&task_id=1151 2022-07-12T22:34:48Z out-of-project-please-delete-this-account Name: FireGesturesVersion: 1.11.1 (compatible Firefox version 52)Source code: GithubDescription: A customizable mouse gestures extension which enables to execute various commands and user scripts with six types of gestures. https://github.com/gomita/firegestures/ https://addons.mozilla.org/en-US/firefox/addon/firegestures/ Name: FireGestures
Version: 1.11.1 (compatible Firefox version 52)
Source code: Github
Description: A customizable mouse gestures extension which enables to execute various commands and user scripts with six types of gestures.

https://github.com/gomita/firegestures/

https://addons.mozilla.org/en-US/firefox/addon/firegestures/

]]> FS#1131: Request browser add-on: New Tab Tools https://issues.hyperbola.info/index.php?do=details&task_id=1131 2022-07-12T22:31:35Z belette Name: New Tab ToolsVersion: 81 (compatible Firefox version 52)Source code: GithubDescription: Customize Firefox’s. Tabs Page https://github.com/darktrojan/newtabtools https://addons.mozilla.org/en-US/firefox/addon/new-tab-tools/ Name: New Tab Tools
Version: 81 (compatible Firefox version 52)
Source code: Github
Description: Customize Firefox’s. Tabs Page

https://github.com/darktrojan/newtabtools

https://addons.mozilla.org/en-US/firefox/addon/new-tab-tools/

]]> FS#1599: [xenocara] Server is not able to be started via xdm https://issues.hyperbola.info/index.php?do=details&task_id=1599 2022-07-12T22:28:51Z Tobias Dausend With the newest package-update the xserver xenocara has missing dependencies towards adobe-fonts and twm. With the newest package-update the xserver xenocara has missing dependencies towards adobe-fonts and twm.

]]> FS#1593: [Hyperbola GNU/Linux-libre 0.4] Reworking xenocara and dbus-dependencies https://issues.hyperbola.info/index.php?do=details&task_id=1593 2022-07-12T15:24:17Z Tobias Dausend Within the concurrent version of xenocara for version 0.4 there is a problem in vesa, generating the error-message “V_BIOS address 0×0 out of range”. It is a known old bug that was fixed when D-Bus arrived by default. This issue is oriented onto to document the steps to test further solutions and rework the x-server. Within the concurrent version of xenocara for version 0.4 there is a problem in vesa, generating the error-message “V_BIOS address 0×0 out of range”. It is a known old bug that was fixed when D-Bus arrived by default.

This issue is oriented onto to document the steps to test further solutions and rework the x-server.

]]>