All Projects

Hey, there's no desktop file in /usr/share/applications for Zandronum, launching from the terminal is kinda a pain in the ass.

AUR package phrasendrescher fails to build when OpenSSL 1.1.0 is installed because SSL_library_init() was replaced with OPENSSL_init_ssl(). See https://wiki.openssl.org/index.php/Library_Initialization#Autoconf for a potential fix.

work with co-maintainers to trim-down to a more lightweight build, do some ARM detection, etc.

Change the date formating in the README file to conform with ISO 8601

Hi, i keep getting a build error after the latest update of the mondo package: make[2]: Leaving directory '/tmp/yaourt-tmp-user/aur-mondo/src/mondo-3.2.2/test' make[2]: Entering directory '/tmp/yaourt-tmp-user/aur-mondo/src/mondo-3.2.2' make[2]: No rule to make target 'docs/man/mondoarchive.8', needed by 'all-am'. Stop. make[2]: Leaving directory '/tmp/yaourt-tmp-user/aur-mondo/src/mondo-3.2.2' make[1]: [Makefile:480: all-recursive] Error 1 make[1]: Leaving directory '/tmp/yaourt-tmp-user/aur-mondo/src/mondo-3.2.2' make: *** [Makefile:371: all] Error 2 ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build mondo. Looks like line 3 is the most striking one. It doesn't matter if package build takes place with or without pacaur. Any idea? System is a current up to date Arch Linux running kernel 4.19 LTS, KDE Plasma 5, platform: Lenovo T510 with a Core i5 M520, 8 GByte RAM Cheers

per Foxboron in #archlinux today around 1704EST5EDT, should be more PEP8 compliant. should be a simple fix; just try chucking through autopep8 first and then see if ERIC IDE complains further (it does some additional syntax checking beyond PEP8).

Would it be possible to use google groups as a mailing for discussions instead of Arch's.

found error while running aif

  File "/usr/lib/python3.6/shutil.py", line 257, in copy2

    copyfile(src,dst,follow_symlinks=follow_symlinks)

  File "/usr/lib/python3.6/shutil.py", line 104, in copyfile

    raise SameFileError("{!r} and {!r} are the same file".format(src, dist))

shutil.SameFileError: '/mnt/boot/vmlinuz-linux' and '/mnt/boot/vmlinuz-llinux'

NOTE: this ticket has been requested to be closed:

"Reason for request: Problem was cause of trailing slash, can be fixed by removing it. removing trailing slash needs to be added in source code for AIF-NG to make it more rebust "

AIF should be modified to use os.path.join() wherever possible.

#archlinux on 06.21.2017 (times in EST5EDT):

17:04:21 < Foxboron> r00t^2: It's unmaintable inn the current state :p 200 lines methods needs to be gone. Follow PEP8
...
17:05:29 < r00t^2> Foxboron: hrm. yeah, i can separate it out into something more modular for the client, but my reasoning for keeping it in a single script was mainly to aid releng

so split large methods into smaller ones, and use more wrapper funcs.

(recv'd via email)

currently if a download fails, one has to scrap the download and start anew.

see if urllib supports byteranges and if it does, we need to figure out the best way to manage a failed download from a process standpoint.

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

Please make it so bdisk will run without root.

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 think i need to re-examine some of my imports. namely, e.g. don't import gpgme if gpg's disabled in the config, etc.

the majority (with the exception of centos not having libisoburn?) of other distros should work just fine assuming all the prereqs are installed.

however, it'd be useful to see if we could get freebsd native support- or at least test it. i doubt it'd work because of the chroot pivoting in bchroot.py, but it'd be interesting to see.

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 mini-howto under the Advanced Customization section on how to provide a manually/externally-downloaded tarball.