r00t^2_projects::BUGS:: r00t^2_projects::BUGS::BDisk: Recently opened tasks https://bugs.square-r00t.net/ 2018-03-05T00:30:10Z FS#42: OibMku <a href="http://ycaakxndukvt.com/">ycaakxndukvt</a>, [url=http://lxinzicivvoa.com/]lxinziciv 2018-03-05T00:30:10Z 2018-03-05T00:30:10Z

OibMku ycaakxndukvt, [url=http://lxinzicivvoa.com/]lxinzicivvoa[/url], [link=http://ryrexkeqsdmt.com/]ryrexkeqsdmt[/link], http://evrvmugggtur.com/

anonymous https://bugs.square-r00t.net/:42
FS#41: Feature Request/Design Element: Move to profile based config 2018-02-10T22:09:26Z 2018-02-10T21:59:46Z

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.


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

GI Jack: All American zero https://bugs.square-r00t.net/:41
FS#40: Feature Request: add ISO overlay 2018-01-16T05:36:50Z 2018-01-16T05:36:50Z

I have a feature request, add an overlay for the iso file system. Needed to support memtest86+, intel microcode and other boot time options.

GI Jack: All American zero https://bugs.square-r00t.net/:40
FS#39: UEFI broken 2018-01-14T08:48:58Z 2018-01-14T08:48:58Z

can no longer find loader.efi. probably some change made upstream in the systemd-boot package or whatever it's called that contains it.

brent s. https://bugs.square-r00t.net/:39
FS#38: Add [system] section in bdisk.ini 2018-01-04T22:18:50Z 2018-01-04T22:09:40Z

Add a [system] section to build.ini for base system configuration

GI Jack: All American zero https://bugs.square-r00t.net/:38
FS#37: Remove bdisk.png hardcoded copy from build.py 2018-01-04T22:20:13Z 2018-01-04T18:52:53Z

Build fails when I remove bdisk.png. Found its hardcoded and hardfails when not present.


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

anonymous https://bugs.square-r00t.net/:37
FS#36: modify pkglist parsing of comments 2018-01-14T08:45:55Z 2018-01-04T05:09:10Z

modify pkg list parsing to support inline commenting


(old content:

tail -f chroot_install.log

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

anonymous https://bugs.square-r00t.net/:36
FS#35: variablize kernel name in build.ini 2018-01-14T08:46:30Z 2018-01-04T02:50:20Z

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

anonymous https://bugs.square-r00t.net/:35
FS#34: Add build time support for only completeing single phase of build at a time 2018-01-04T22:25:56Z 2018-01-04T02:42:16Z

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

anonymous https://bugs.square-r00t.net/:34
FS#33: Remove dirrect AUR support 2018-01-04T02:42:42Z 2018-01-04T02:24:35Z

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.

anonymous https://bugs.square-r00t.net/:33