Subj : Husky Project Compile on Debian 11 and/or AlmaLinux/RockyLinux 8
To   : Michael Dukelsky
From : Eric Renfro
Date : Sat Feb 12 2022 12:34 pm

  Re: Husky Project Compile on Debian 11 and/or AlmaLinux/RockyLinux 8
  By: Michael Dukelsky to Eric Renfro on Sat Feb 12 2022 06:09 pm

 MD> Hello Eric,

 MD> Saturday February 12 2022, Eric Renfro wrote to All:

 ER>> So, I've been having some major issues trying to migrate from CentOS
 ER>> 7 to either AlmaLinux 8, Rocky Linux 8, or even more preferred at
 ER>> this stage, Debian 11, with trying to get the Husky Tools project to
 ER>> even compile, let alone compile into preferred native packages for
 ER>> these distributions.

 ER>> I've tried the method of init_rpm_build on AlmaLinux/Rocky Linux,
 ER>> and even openSUSE 15.3 (to no availability of mock at all) and it
 ER>> always fails, specifically on systemd-nspawn part of mock.

 MD> Please send me your huskymak.cfg and build log on Rocky Linux to my email
 MD> in the tagline.

Building target platforms: x86_64
Building for target x86_64
error: Macro %huskylib_ver_major has empty body 
error: line 33: %global huskylib_ver_major 

Finish: rpmbuild -bs
Finish: buildsrpm
ERROR: Exception(husky/husky.spec) Config(epel-8-x86_64) 1 minutes 37 seconds
INFO: Results and/or logs in: ./result
INFO: Cleaning up build root ('cleanup_on_failure=True')
Start: clean chroot
Finish: clean chroot
ERROR: Command failed: 
 # /usr/bin/systemd-nspawn -q -M 282ec2cfd5b64c71a30d271a491c3be3 -D /var/lib/mock/epel-8-x86_64/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.2xp8ik0e:/etc/resolv.co
nf --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 -
-bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin 
--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$  --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c /usr/bin/rpmbuild -bs --target x86_64 --n
odeps /builddir/build/SPECS/husky.spec

I believe overall, this is where I was getting the most out of it, and I've seen that Macro %huskylib_ver_major in just trying manually to rpmbuild, so I'm 95% certain that's where the problem may be, looking further.


On that note, I've actually been trying the init_build and build.sh scripts, and those, on Debian 11, actually are working, when everything is installed that's needed. Lacking of course packaging itself, but it's progress eeven if not "installed", it could work for me if I setup a ~-run installation from source that's maintained that way. :)
===
)))[Psi-Jack -//- Decker]
--- SBBSecho 3.08-Linux
 * Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)

.