r00t^2_projects::BUGS:: https://bugs.square-r00t.net/ r00t^2_projects::BUGS::BDisk: Recently opened tasks 2018-02-10T22:09:26Z FS#41: Feature Request/Design Element: Move to profile based config https://bugs.square-r00t.net/index.php?do=details&task_id=41 2018-02-10T22:09:26Z GI Jack: All American zero As current, bdisk is configured to expect one build configuration per system. This is terrible for both workflow and for sharing your configurations. Suggestion is to move to an instanced profile based solution. i.e. move /var/lib/bdisk to /usr/share/bdisk/defaultprofile move /etc/bdisk/build.ini to /usr/share/bdisk/defaultprofile each profile is and instance of this template, with build.ini in the root. default libs are in the same dir as build.ini This allows for many profiles, and profiles to be shared and worked on on git. When bdisk becomes multi-staged. There should be an option for bdisk --init-profile [directory] which creates a new project profile at specified directory, $PWD if blank
Suggestion is to move to an instanced profile based solution.

i.e.

move /var/lib/bdisk to /usr/share/bdisk/defaultprofile

move /etc/bdisk/build.ini to /usr/share/bdisk/defaultprofile

each profile is and instance of this template, with build.ini in the root. default libs are in the same dir as build.ini

This allows for many profiles, and profiles to be shared and worked on on git.

When bdisk becomes multi-staged. There should be an option for bdisk --init-profile [directory] which creates a new project profile at specified directory, $PWD if blank]]>
FS#40: Feature Request: add ISO overlay https://bugs.square-r00t.net/index.php?do=details&task_id=40 2018-01-16T05:36:50Z GI Jack: All American zero I have a feature request, add an overlay for the iso file system. Needed to support memtest86+, intel microcode and other boot time options. I have a feature request, add an overlay for the iso file system. Needed to support memtest86+, intel microcode and other boot time options.

]]>
FS#39: UEFI broken https://bugs.square-r00t.net/index.php?do=details&task_id=39 2018-01-14T08:48:58Z brent s. can no longer find loader.efi. probably some change made upstream in the systemd-boot package or whatever it's called that contains it. can no longer find loader.efi. probably some change made upstream in the systemd-boot package or whatever it's called that contains it.

]]>
FS#38: Add [system] section in bdisk.ini https://bugs.square-r00t.net/index.php?do=details&task_id=38 2018-01-04T22:18:50Z GI Jack: All American zero Add a [system] section to build.ini for base system configuration https://pastebin.com/Rt6x879q https://pastebin.com/Rt6x879q]]> FS#37: Remove bdisk.png hardcoded copy from build.py https://bugs.square-r00t.net/index.php?do=details&task_id=37 2018-01-04T22:20:13Z anonymous Build fails when I remove bdisk.png. Found its hardcoded and hardfails when not present. <p> *facepalm* Pls remove this https://pastebin.com/Nn92vqJi Build fails when I remove bdisk.png. Found its hardcoded and hardfails when not present.
<p>

*facepalm*

Pls remove this https://pastebin.com/Nn92vqJi

]]>
FS#36: modify pkglist parsing of comments https://bugs.square-r00t.net/index.php?do=details&task_id=36 2018-01-14T08:45:55Z anonymous modify pkg list parsing to support inline commenting   (old content: tail -f chroot_install.log Hangs here: Log: https://pastebin.com/UaSJGznh) modify pkg list parsing to support inline commenting

 

(old content:

tail -f chroot_install.log

Hangs here: Log: https://pastebin.com/UaSJGznh)

]]>
FS#35: variablize kernel name in build.ini https://bugs.square-r00t.net/index.php?do=details&task_id=35 2018-01-14T08:46:30Z anonymous Make the name of the kernel a variable in build.ini. This allows for custom kernels. related patch from Ninja OS: https://gitlab.com/ninjaos/ninjaos-ng/commit/32c84056234768777bedbf62cb9f058d7eee65ea Make the name of the kernel a variable in build.ini. This allows for custom kernels.
related patch from Ninja OS: https://gitlab.com/ninjaos/ninjaos-ng/commit/32c84056234768777bedbf62cb9f058d7eee65ea

]]>
FS#34: Add build time support for only completeing single phase of build at a time https://bugs.square-r00t.net/index.php?do=details&task_id=34 2018-01-04T22:25:56Z anonymous Add a build time option for only completing one phase of the build process at a time For example: I would like be able to build the chroot without compiling the final .iso. I would also like to compile the final .iso from a previously build chroot without having to re-install the chroot. I would like to do this so I can work on the overlay without having to do a re-install. This would greatly speed up testing and debugging. Also, being able to install the base chroot without compiling the rest would aid in development. Just a design time decision to consider Add a build time option for only completing one phase of the build process at a time
For example: I would like be able to build the chroot without compiling the final .iso. I would also like to compile the final .iso from a previously build chroot without having to re-install the chroot. I would like to do this so I can work on the overlay without having to do a re-install. This would greatly speed up testing and debugging. Also, being able to install the base chroot without compiling the rest would aid in development. Just a design time decision to consider

]]>
FS#33: Remove dirrect AUR support https://bugs.square-r00t.net/index.php?do=details&task_id=33 2018-01-04T02:42:42Z anonymous I know this is likely a hard one, but you absolutely most remove direct support for AUR packages. Reason: Its dangerous makepkg by default refuses to run as root. bdisk needs to run as root. This feature is a serious security and/or bug problem. At very least, with makepkg, build(), package(), etc... functions run shell commands directly on the system not in a chroot. a poorly written PKGBUILD can fuck up a system if run as root, and a malicious one guarantees system compromise. If users need packages they should compile their own, make a repo, and then use that. It is easy enough.
Reason: Its dangerous

makepkg by default refuses to run as root. bdisk needs to run as root. This feature is a serious security and/or bug problem.

At very least, with makepkg, build(), package(), etc... functions run shell commands directly on the system not in a chroot. a poorly written PKGBUILD can fuck up a system if run as root, and a malicious one guarantees system compromise.

If users need packages they should compile their own, make a repo, and then use that. It is easy enough.]]>
FS#32: Add user groups to jinja profile https://bugs.square-r00t.net/index.php?do=details&task_id=32 2018-01-03T17:46:22Z anonymous related from Ninja OS https://gitlab.com/ninjaos/ninjaos-ng/commit/5d97755a726673faca398e098b75c1161aab8abc adds a groups = option under [user] for UNIX groups.
https://gitlab.com/ninjaos/ninjaos-ng/commit/5d97755a726673faca398e098b75c1161aab8abc

adds a groups = option under [user] for UNIX groups.]]>