• Husky Project Compile on Debian 11 and/or AlmaLinux/RockyLinux 8

    From Eric Renfro@1:135/371 to All on Saturday, February 12, 2022 09:04:06
    So, I've been having some major issues trying to migrate from CentOS 7 to either AlmaLinux 8, Rocky Linux 8, or even more preferred at this stage, Debian
    11, with trying to get the Husky Tools project to even compile, let alone compile into preferred native packages for these distributions.

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

    The debian/* structure is so outdated it's not even funny. debian/compat is non-existant, and setup as DH_COMPAT in debian/rules, to a long since unsupported version 4, to make things difficult on Debian's side of things.

    I'm trying to ultimately move away from CentOS 7 before it becomes unsupported in 2024. I'm prefering the Debian way of things, even though for decades, I've never liked the .deb package format, but I have always appreciated the rest of the setup for servers, the modular design it's always had. And I finally FINALLY figured out how to create a debian repository. ;)

    So, any help on this from anyone would be greatly appreciated.
    ===
    )))[Psi-Jack -//- Decker]
    --- SBBSecho 3.08-Linux
    * Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)
  • From Michael Dukelsky@2:5020/1042 to Eric Renfro on Saturday, February 12, 2022 18:09:26
    Hello Eric,

    Saturday February 12 2022, Eric Renfro wrote to All:

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

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

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

    The debian/* structure is so outdated it's not even funny.
    debian/compat is non-existant, and setup as DH_COMPAT in debian/rules,
    to a long since unsupported version 4, to make things difficult on Debian's side of things.

    I'm trying to ultimately move away from CentOS 7 before it becomes unsupported in 2024. I'm prefering the Debian way of things, even
    though for decades, I've never liked the .deb package format, but I
    have always appreciated the rest of the setup for servers, the modular design it's always had. And I finally FINALLY figured out how to
    create a debian repository. ;)

    If you could write a script producing .deb similar to the one producing .rpm, it would be nice.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)
  • From Eric Renfro@1:135/371 to Michael Dukelsky on Saturday, February 12, 2022 12:34:52
    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

    Hello Eric,

    Saturday February 12 2022, Eric Renfro wrote to All:

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

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

    Please send me your huskymak.cfg and build log on Rocky Linux to my email 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)
  • From Michael Dukelsky@2:5020/1042 to Eric Renfro on Saturday, February 12, 2022 21:56:22
    Hello Eric,

    Saturday February 12 2022, Eric Renfro wrote to Michael Dukelsky:


    So, I've been having some major issues trying to migrate from
    CentOS 7 to either AlmaLinux 8, Rocky Linux 8

    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

    Fixed.

    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.

    Is the list of the packages to install on Ubuntu (in INSTALL.asciidoc) coincides with the list of the packages you have installed on Debian 11?

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)
  • From Eric Renfro@1:135/371 to Michael Dukelsky on Sunday, February 13, 2022 09:18:18
    Re: Husky Project Compile on Debian 11 and/or AlmaLinux/RockyLinux 8
    By: Michael Dukelsky to Eric Renfro on Sat Feb 12 2022 09:56 pm

    Hello Eric,

    Saturday February 12 2022, Eric Renfro wrote to Michael Dukelsky:


    So, I've been having some major issues trying to migrate from
    CentOS 7 to either AlmaLinux 8, Rocky Linux 8

    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

    Fixed.

    And indeed, it was in the spec_configure. As I was trying to rpm-build manually
    I'd noticed this. Next up, is with msged specifically being unable to find libhusky.so, and this is with DYNLIBS=0, though I'd prefer packaged, to use DYNLIBS=1.

    Yes, actually! In this that list seems complete enough at first look. The CentOS one was actually more trialing because texinfo is not in base/core, not in epel, but in powertools repo in AlmaLinux 8 and RockyLinux 8, and in completely different repo that you have to, of course, Subscribe to in RHEL 8 actual (I don't use RHEL, just saying. ;)
    ===
    )))[Psi-Jack -//- Decker]
    --- SBBSecho 3.08-Linux
    * Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)
  • From Michael Dukelsky@2:5020/1042 to Eric Renfro on Sunday, February 13, 2022 21:41:04
    Hello Eric,

    Sunday February 13 2022, Eric Renfro wrote to Michael Dukelsky:

    And indeed, it was in the spec_configure. As I was trying to rpm-build manually I'd noticed this. Next up, is with msged specifically being unable to find libhusky.so, and this is with DYNLIBS=0, though I'd
    prefer packaged, to use DYNLIBS=1.

    Sorry, I don't understand. Do you encounter this issue now? On what OS? I don't
    see it on CentOS 7, Rocky Linux 8 and Fedora 34.

    Yes, actually! In this that list seems complete enough at first look.
    The CentOS one was actually more trialing because texinfo is not in base/core, not in epel, but in powertools repo in AlmaLinux 8 and RockyLinux 8, and in completely different repo that you have to, of course, Subscribe to in RHEL 8 actual (I don't use RHEL, just saying.
    ;)

    And in Rocky Linux the soft link /etc/mock/default.cfg points to epel-8-x86_64.cfg instead of rocky-8-x86_64.cfg.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)
  • From Eric Renfro@1:135/371 to Michael Dukelsky on Sunday, February 13, 2022 17:05:32
    Re: Husky Project Compile on Debian 11 and/or AlmaLinux/RockyLinux 8
    By: Michael Dukelsky to Eric Renfro on Sun Feb 13 2022 09:41 pm

    Hello Eric,

    Sunday February 13 2022, Eric Renfro wrote to Michael Dukelsky:

    And indeed, it was in the spec_configure. As I was trying to
    rpm-build manually I'd noticed this. Next up, is with msged
    specifically being unable to find libhusky.so, and this is with
    DYNLIBS=0, though I'd prefer packaged, to use DYNLIBS=1.

    Sorry, I don't understand. Do you encounter this issue now? On what OS? I don't see it on CentOS 7, Rocky Linux 8 and Fedora 34.

    Correct, on a clean system it fails to build msged because it somehow cannot find libhusky.so.1.9.20220208 specifically during the linker process of building. This is with Rocky Linux 8, Alma Linux 8. I haven't tested CentOS 7 as I'm trying to get away from 7 as it will EOL sooner than later. And Fedora EOL's every year, so not ideal either.


    Also correct, because mock comes from epel specifically. I modified epel-8-x86_64.cfg to use appropriately Rocky Linux or Alma Linux includes while
    maintaining the specific use of EPEL-8.
    ===
    )))[Psi-Jack -//- Decker]
    --- SBBSecho 3.08-Linux
    * Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)
  • From Michael Dukelsky@2:5020/1042 to Eric Renfro on Monday, February 14, 2022 20:54:58
    Hello Eric,

    Sunday February 13 2022, Eric Renfro wrote to Michael Dukelsky:

    on a clean system it fails to build msged because it somehow
    cannot find libhusky.so.1.9.20220208 specifically during the linker process of building.

    Fixed.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)
  • From Eric Renfro@1:135/371 to Michael Dukelsky on Monday, February 14, 2022 19:07:58
    Re: Husky Project Compile on Debian 11 and/or AlmaLinux/RockyLinux 8
    By: Michael Dukelsky to Eric Renfro on Mon Feb 14 2022 08:54 pm

    on a clean system it fails to build msged because it somehow
    cannot find libhusky.so.1.9.20220208 specifically during the linker
    process of building.

    Fixed.

    I am still seeing it. It's in the %install portion of the spec when it's preparing installation.

    for f in fconf2aquaed.1.gz fconf2areasbbs.pl.1.gz fconf2binkd.1.gz fconf2dir.1.gz fconf2fidogate.1.gz fconf2golded.1.gz fconf2msged.1.gz fconf2na.pl.1.gz fconf2squish.1.gz fconf2tornado.1.gz
    fecfg2fconf.1.gz; do ln -s -f fconf2.1.gz $f; done
    cd /builddir/build/BUILDROOT/husky-1.9.20220208-1.x86_64/usr/share/man/man1; \ for f in fconf2aquaed.1.gz fconf2areasbbs.pl.1.gz fconf2binkd.1.gz fconf2dir.1.gz fconf2fidogate.1.gz fconf2golded.1.gz fconf2msged.1.gz fconf2na.pl.1.gz fconf2squish.1.gz fconf2tornado.1.gz
    fecfg2fconf.1.gz; do ln -s -f fconf2.1.gz $f; done
    cd /builddir/build/BUILDROOT/husky-1.9.20220208-1.x86_64/usr/share/man/man1; \ for f in fconf2aquaed.1.gz fconf2areasbbs.pl.1.gz fconf2binkd.1.gz fconf2dir.1.gz fconf2fidogate.1.gz fconf2golded.1.gz fconf2msged.1.gz fconf2na.pl.1.gz fconf2squish.1.gz fconf2tornado.1.gz
    fecfg2fconf.1.gz; do ln -s -f fconf2.1.gz $f; done
    echo "DO NOT WORRY ABOUT WARNINGS ABOUT no matching charset!"
    DO NOT WORRY ABOUT WARNINGS ABOUT no matching charset!
    cd msged/maps/ && ../../msged/Build/obj/makemaps CP437 437 850_ibm.chs ibm_850.chs 866_koi.chs is5_asc.chs nor_ibm.chs prt_ibm.chs is5_1125.chs 1125_asc.chs is5_866.chs 865_866.chs frn_ibm.c
    hs mac_iso.chs 865_ibm.chs uk_ibm.chs itl_ibm.chs 1125_866.chs ibm_vt1.chs iso_mac.chs 866_is5.chs iso_asc.chs fin_ibm.chs iso_ibm.chs mac_850.chs 850_asc.chs 850_865.chs 866_1125.chs 1125_is
    5.chs 866_ibm.chs 1125_ibm.chs 865_iso.chs mac_ibm.chs grm_ibm.chs swe_ibm.chs 865_asc.chs ibm_asc.chs koi_866.chs 850_iso.chs ibm_swe.chs swi_ibm.chs 865_850.chs dut_ibm.chs ibm_mac.chs spn_
    ibm.chs 866_865.chs koi_1125.chs ibm_iso.chs can_ibm.chs 1125_koi.chs ibm_865.chs iso_865.chs koi_asc.chs iso_850.chs 866_asc.chs ../../msged/Build/obj/makemaps: error while loading shared libraries: libhusky.so.1.9.20220208: cannot open shared object file: No such file or directory
    make: *** [msged/maps/makefile.husky:126: /builddir/build/BUILDROOT/husky-1.9.20220208-1.x86_64/usr/share/doc/husky/msged
    -6.3.20220208/writmaps.437] Error 127
    make: *** Waiting for unfinished jobs....
    ===
    )))[Psi-Jack -//- Decker]
    --- SBBSecho 3.08-Linux
    * Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)
  • From Michael Dukelsky@2:5020/1042 to Eric Renfro on Tuesday, February 15, 2022 11:25:40
    Hello Eric,

    Monday February 14 2022, Eric Renfro wrote to Michael Dukelsky:

    on a clean system it fails to build msged because it somehow
    cannot find libhusky.so.1.9.20220208 specifically during the
    linker process of building.

    Fixed.

    I am still seeing it. It's in the %install portion of the spec when
    it's preparing installation.

    Looks like you somehow have leftovers from previous builds. Please run `mock --clean` and start from `init_rpm_build`. After you change DYNLIBS to 1 in huskymak.rpm.cfg, you may run `./build_rpm -n`.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)