Re: Sent out a pull-request to upgrade the packaging system....
Is it a problem with the Solaris port for the 4.5.* version related ambind ? We have never seen this problem in older versions. Let me know if more debugging is needed. Have you been able to reproduce the error ? Thanks Gunnar Skickat från min iPhone > 23 mars 2022 kl. 17:42 skrev Chris Hassell : > > My guess from the manpage of sendmsg() is that this applies. The > SOCK_DGRAM may not working as a transport. > > to specify the size. The length of the message is supplied by the len > parameter. For socket types such as SOCK_DGRAM and SOCK_RAW that > require atomic messages, the error EMSGSIZE is returned and the message > is not transmitted when it is too long to pass atomically through the > underlying protocol. The same restrictions do not apply to SOCK_STREAM > sockets. > > So as we never use or verify the datagram protocol ourselves. I have > wondered how fast it streams from a big client. > > I am guessing here that some problem shows up whence we're sending longer > packets than the 1460 or so that can be supported? > >> -Original Message- >> From: Gunnarsson, Gunnar >> Sent: Tuesday, March 22, 2022 9:30 AM >> To: Chris Hassell ; li...@xunil.at; ? amanda users >> >> Subject: SV: Sent out a pull-request to upgrade the packaging system >> >> WARNING: This email originated from outside of BETSOL. Do not click links or >> open attachments unless you recognize the sender and know the content is >> safe. >> >> >> Hi, >> >> I'm testing the amanda-3_5-packaging-upgrade-wip and now it builds on my >> solaris 11.4 system. >> Amrecover fails to connect to the amindexd server see trace from below. >> Complains about too big message size see trace below. >> Server works if the amrecover client is 3.4.5 and the backup client seems to >> be >> working using th 3.4.5 version. >> >> Thanks Gunnar >> >> Tue Mar 22 15:42:21.445289090 2022: pid 11472: thd-100124a00: amindexd: pid >> 11472 ruid 91 euid 91 version 3.5.1+233: start at Tue Mar 22 15:4 >> 2:21 2022 >> Tue Mar 22 15:42:21.445353790 2022: pid 11472: thd-100124a00: amindexd: >> version 3.5.1+233 >> >> 11484/2:setsockopt(4, SOL_SOCKET, SO_REUSEADDR, >> 0x7E8FB07C, 4, SOV_DEFAULT) = 0 >> 11484/2:setsockopt(4, SOL_SOCKET, SO_KEEPALIVE, 0x7E8FB07C, >> 4, SOV_DEFAULT) = 0 >> 11484/2:so_socket(PF_UNIX, SOCK_DGRAM|SOCK_NONBLOCK, 0, NULL, >> SOV_XPG4_2) = 5 >> 11484/2:so_socket(PF_UNIX, SOCK_DGRAM|SOCK_NONBLOCK, 0, NULL, >> SOV_XPG4_2) = 6 >> 11484/2:so_socketpair(5, 6) = 0 >> 11484/2:pipe() = 7 [8] >> 11484/2:lwp_suspend(1) = 0 >> 11484/2:forkx(0)= 11487 >> 11487: forkx() (returning as child of pid 11484) = 0 >> 11484/2:lwp_continue(1) = 0 >> 11487: getpid()= 11487 [11484] >> 11484/2:lwp_sigmask(SIG_SETMASK, 0x, 0x, >> 0x, 0x) = 0xFFBFFEFF [0x] >> 11487: lwp_self() = 2 >> 11484/2:close(6)= 0 >> 11484/2:close(8)= 0 >> 11487: lwp_sigmask(SIG_SETMASK, 0x, 0x, 0x, >> 0x) = 0xFFBFFEFF [0x] >> 11484/2:sendmsg(5, 0x7E8F8E48, MSG_XPG4_2) Err#97 >> EMSGSIZE >> >> ^ >> ^^^ >> 11487: schedctl() = 0x7F5E4000 >> 11484/2:shutdown(5, SHUT_RDWR, SOV_DEFAULT) = 0 >> 11484/2:close(5)= 0 >> 11484/2:close(7)= 0 >> 11487: close(5)= 0 >> 11484/2:close(4)= 0 >> 11484/2:getpid()= 11484 >> [11483] >> 11487: fcntl(8, F_DUP2FD, 0x0002) = 2 >> 11484/2:write(10, 0x100147A64, 124) = 124 >> 11484/2: r e c o v e r : a m b i n d f a i l e d : s e n d m >> s g >> 11484/2: f a i l e d A : M e s s a g e t o o l o n g\n\n >> 11487: fcntl(0, F_GETFD) = 0 >> 11484/2:getpid()= 11484 >> [11483] >> 11487: fcntl(1, F_GETFD) = 0 >> 11484/2:write(10, 0x100147A64, 130) = 130 >> 11484/2: T u e M a r 2 2 1 5 : 4 4 : 5 4 . 0 4 9 9 5 3 7 3 0 >> 2 0 >> 11484/2: 2 2 : p i d 1 1 4 8 4 : t h d - 1 0 0 1 5 5 0 0 0 : >> a m >> 11484/2: r e c o v e r
RE: Sent out a pull-request to upgrade the packaging system....
My guess from the manpage of sendmsg() is that this applies. The SOCK_DGRAM may not working as a transport. to specify the size. The length of the message is supplied by the len parameter. For socket types such as SOCK_DGRAM and SOCK_RAW that require atomic messages, the error EMSGSIZE is returned and the message is not transmitted when it is too long to pass atomically through the underlying protocol. The same restrictions do not apply to SOCK_STREAM sockets. So as we never use or verify the datagram protocol ourselves. I have wondered how fast it streams from a big client. I am guessing here that some problem shows up whence we're sending longer packets than the 1460 or so that can be supported? > -Original Message- > From: Gunnarsson, Gunnar > Sent: Tuesday, March 22, 2022 9:30 AM > To: Chris Hassell ; li...@xunil.at; ? amanda users > > Subject: SV: Sent out a pull-request to upgrade the packaging system > > WARNING: This email originated from outside of BETSOL. Do not click links or > open attachments unless you recognize the sender and know the content is safe. > > > Hi, > > I'm testing the amanda-3_5-packaging-upgrade-wip and now it builds on my > solaris 11.4 system. > Amrecover fails to connect to the amindexd server see trace from below. > Complains about too big message size see trace below. > Server works if the amrecover client is 3.4.5 and the backup client seems to > be > working using th 3.4.5 version. > > Thanks Gunnar > > Tue Mar 22 15:42:21.445289090 2022: pid 11472: thd-100124a00: amindexd: pid > 11472 ruid 91 euid 91 version 3.5.1+233: start at Tue Mar 22 15:4 > 2:21 2022 > Tue Mar 22 15:42:21.445353790 2022: pid 11472: thd-100124a00: amindexd: > version 3.5.1+233 > > 11484/2:setsockopt(4, SOL_SOCKET, SO_REUSEADDR, > 0x7E8FB07C, 4, SOV_DEFAULT) = 0 > 11484/2:setsockopt(4, SOL_SOCKET, SO_KEEPALIVE, 0x7E8FB07C, > 4, SOV_DEFAULT) = 0 > 11484/2:so_socket(PF_UNIX, SOCK_DGRAM|SOCK_NONBLOCK, 0, NULL, > SOV_XPG4_2) = 5 > 11484/2:so_socket(PF_UNIX, SOCK_DGRAM|SOCK_NONBLOCK, 0, NULL, > SOV_XPG4_2) = 6 > 11484/2:so_socketpair(5, 6) = 0 > 11484/2:pipe() = 7 [8] > 11484/2:lwp_suspend(1) = 0 > 11484/2:forkx(0)= 11487 > 11487: forkx() (returning as child of pid 11484) = 0 > 11484/2:lwp_continue(1) = 0 > 11487: getpid()= 11487 [11484] > 11484/2:lwp_sigmask(SIG_SETMASK, 0x, 0x, > 0x, 0x) = 0xFFBFFEFF [0x] > 11487: lwp_self() = 2 > 11484/2:close(6)= 0 > 11484/2:close(8)= 0 > 11487: lwp_sigmask(SIG_SETMASK, 0x, 0x, 0x, > 0x) = 0xFFBFFEFF [0x] > 11484/2:sendmsg(5, 0x7E8F8E48, MSG_XPG4_2) Err#97 > EMSGSIZE > > ^ > ^^^ > 11487: schedctl() = 0x7F5E4000 > 11484/2:shutdown(5, SHUT_RDWR, SOV_DEFAULT) = 0 > 11484/2:close(5)= 0 > 11484/2:close(7)= 0 > 11487: close(5)= 0 > 11484/2:close(4)= 0 > 11484/2:getpid()= 11484 > [11483] > 11487: fcntl(8, F_DUP2FD, 0x0002) = 2 > 11484/2:write(10, 0x100147A64, 124) = 124 > 11484/2: r e c o v e r : a m b i n d f a i l e d : s e n d m > s g > 11484/2: f a i l e d A : M e s s a g e t o o l o n g\n\n > 11487: fcntl(0, F_GETFD) = 0 > 11484/2:getpid()= 11484 > [11483] > 11487: fcntl(1, F_GETFD) = 0 > 11484/2:write(10, 0x100147A64, 130) = 130 > 11484/2: T u e M a r 2 2 1 5 : 4 4 : 5 4 . 0 4 9 9 5 3 7 3 0 > 2 0 > 11484/2: 2 2 : p i d 1 1 4 8 4 : t h d - 1 0 0 1 5 5 0 0 0 : > a m > 11484/2: r e c o v e r : s t r e a m _ c l i e n t : C o u l d > n o > 11484/2: t b i n d t o p o r t i n r a n g e 5 1 2 - 1 > 0 2 3 > 11484/2: .\n > 11487: fcntl(2, F_GETFD) = 0 > 11484/2:getpid()= 11484 > [11483] > 11487: close(3)= 0 > 11484/2:write(10, 0x100147A64, 185)
SV: Sent out a pull-request to upgrade the packaging system....
Hi, I'm testing the amanda-3_5-packaging-upgrade-wip and now it builds on my solaris 11.4 system. Amrecover fails to connect to the amindexd server see trace from below. Complains about too big message size see trace below. Server works if the amrecover client is 3.4.5 and the backup client seems to be working using th 3.4.5 version. Thanks Gunnar Tue Mar 22 15:42:21.445289090 2022: pid 11472: thd-100124a00: amindexd: pid 11472 ruid 91 euid 91 version 3.5.1+233: start at Tue Mar 22 15:4 2:21 2022 Tue Mar 22 15:42:21.445353790 2022: pid 11472: thd-100124a00: amindexd: version 3.5.1+233 11484/2:setsockopt(4, SOL_SOCKET, SO_REUSEADDR, 0x7E8FB07C, 4, SOV_DEFAULT) = 0 11484/2:setsockopt(4, SOL_SOCKET, SO_KEEPALIVE, 0x7E8FB07C, 4, SOV_DEFAULT) = 0 11484/2:so_socket(PF_UNIX, SOCK_DGRAM|SOCK_NONBLOCK, 0, NULL, SOV_XPG4_2) = 5 11484/2:so_socket(PF_UNIX, SOCK_DGRAM|SOCK_NONBLOCK, 0, NULL, SOV_XPG4_2) = 6 11484/2:so_socketpair(5, 6) = 0 11484/2:pipe() = 7 [8] 11484/2:lwp_suspend(1) = 0 11484/2:forkx(0)= 11487 11487: forkx() (returning as child of pid 11484) = 0 11484/2:lwp_continue(1) = 0 11487: getpid()= 11487 [11484] 11484/2:lwp_sigmask(SIG_SETMASK, 0x, 0x, 0x, 0x) = 0xFFBFFEFF [0x] 11487: lwp_self() = 2 11484/2:close(6)= 0 11484/2:close(8)= 0 11487: lwp_sigmask(SIG_SETMASK, 0x, 0x, 0x, 0x) = 0xFFBFFEFF [0x] 11484/2:sendmsg(5, 0x7E8F8E48, MSG_XPG4_2) Err#97 EMSGSIZE 11487: schedctl() = 0x7F5E4000 11484/2:shutdown(5, SHUT_RDWR, SOV_DEFAULT) = 0 11484/2:close(5)= 0 11484/2:close(7)= 0 11487: close(5)= 0 11484/2:close(4)= 0 11484/2:getpid()= 11484 [11483] 11487: fcntl(8, F_DUP2FD, 0x0002) = 2 11484/2:write(10, 0x100147A64, 124) = 124 11484/2: r e c o v e r : a m b i n d f a i l e d : s e n d m s g 11484/2: f a i l e d A : M e s s a g e t o o l o n g\n\n 11487: fcntl(0, F_GETFD) = 0 11484/2:getpid()= 11484 [11483] 11487: fcntl(1, F_GETFD) = 0 11484/2:write(10, 0x100147A64, 130) = 130 11484/2: T u e M a r 2 2 1 5 : 4 4 : 5 4 . 0 4 9 9 5 3 7 3 0 2 0 11484/2: 2 2 : p i d 1 1 4 8 4 : t h d - 1 0 0 1 5 5 0 0 0 : a m 11484/2: r e c o v e r : s t r e a m _ c l i e n t : C o u l d n o 11484/2: t b i n d t o p o r t i n r a n g e 5 1 2 - 1 0 2 3 11484/2: .\n 11487: fcntl(2, F_GETFD) = 0 11484/2:getpid()= 11484 [11483] 11487: close(3)= 0 11484/2:write(10, 0x100147A64, 185) = 185 11484/2: T u e M a r 2 2 1 5 : 4 4 : 5 4 . 0 5 0 0 8 5 5 1 0 2 0 11484/2: 2 2 : p i d 1 1 4 8 4 : t h d - 1 0 0 1 5 5 0 0 0 : a m 11484/2: r e c o v e r : s e c u r i t y _ s e t e r r o r ( h a n d l 11484/2: e = 1 0 0 1 5 6 4 0 0 , d r i v e r = f f f f f f f f 7 1 3 9 11484/2: 2 f 4 0 ( B S D T C P ) e r r o r = s e n d m s g f a i l 11484/2: e d A : M e s s a g e t o o l o n g\n )\n -Ursprungligt meddelande- Från: Chris Hassell Skickat: den 21 mars 2022 20:37 Till: li...@xunil.at; ? amanda users ; Gunnarsson, Gunnar Ämne: RE: Sent out a pull-request to upgrade the packaging system NOTE: it seems at least gcc 7 is a good idea for the Solaris build. Autoconf 2.69 seems to be the minimal level. To start from a clean set of source. % git clean -dfx % ./autogen ( Not sure if autogen is necessary any more. It can be done automatically in the scripts. ) To build binaries and packages in the top directory (where the source is) ... depending what you are running on. [Same dir setup as old]. % ./packaging/rpm/build client % ./packaging/deb/build client % ./packaging/sun-pkg/build client To build current working dirs in a subdirectory
RE: Sent out a pull-request to upgrade the packaging system....
Info for Solaris in specific …. The Solaris 10 build needs a lot of downloads from "pkgutil", but folks may be used to these distributed packages. SUNWgcc SUNWhea SUNWlibstdcxx4 SUNWarc SUNWzlib SUNWlibm SUNWcsu SUNWlxml SUNWgnu-gettext SUNWgnome-common-devel SUNWgnome-common-devel-share SUNWgnome-base-libs SUNWgnome-base-libs-devel SUNWgnome-base-libs-devel-share SUNWlxsl SUNWgmake SUNWopenssl-include SUNWgnutls-devel SUNWlibgcrypt-devel SUNWsmbac SUNWsmbau CSWlibtool CSWgmake CSWflex CSWbison CSWautoconf CSWautomake CSWcurl CSWlibcurl-dev CSWlibssl1-0-0 CSWlibncurses5 CSWlibreadline_dev CSWdocbooksxsl CSWlibxsl CSWfakeroot CSWgit CSWlibtool CSWswig CSWgnuplot CSWmtx CSWpkgutil CSWbash CSWggrep CSWgsed Solaris 11 requires (from a while ago??) at least these using “pkg install” (maybe more likely to be installed already) and their depends: gcc-c gnu-binutils gnu-gettext gnu-make gnu-m4 gnu-tar libtool autoconf automake bison flex swig glib2 json-glib readline curl openssl ncurses perl-common mtx libsmbclient gnuplot CSWcoreutils CSWfindutils CSWbash CSWfakeroot CSWgmake I haven’t de-installed everything CSW from Solaris 11, as their “pkgs” repos have become much stronger over the last two years. I’m pretty sure most of the above is correct.. at least to use fakeroot. > -Original Message- > From: Stefan G. Weichinger > Sent: Friday, March 18, 2022 3:31 AM > To: Chris Hassell ; ? amanda users us...@amanda.org> > Subject: Re: Sent out a pull-request to upgrade the packaging system > > WARNING: This email originated from outside of BETSOL. Do not click links or > open attachments unless you recognize the sender and know the content is safe. > > > Am 17.03.22 um 22:28 schrieb Chris Hassell: > > First of many. It is not configured-and-tested as is but it is very > > close to our working version. > > > > -Versioning based on tags from git > > > > -An in-directory build as well as below-directory package build > > > > -Solaris 10 and Solaris 11 packages > > > > -Better handling of pre/post scripts (may need to update Debian > > ones??) > > > > -Systemd services are included as well. > > > > If I can get someone to look over it and give it a spin I’d really > > appreciate it. > > > > I have more fixes for the installcheck directory to allow some good > > and solid self-tests. > > Nice to see progress. > > I assume you want us to try to build the code in that PR? > > pls point to some howto, I can't remember the procedure anymore (autoconf? > etc) > > I can test on Debian 11, for example. Confidentiality Notice | The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, re-transmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.
RE: Sent out a pull-request to upgrade the packaging system....
NOTE: it seems at least gcc 7 is a good idea for the Solaris build. Autoconf 2.69 seems to be the minimal level. To start from a clean set of source. % git clean -dfx % ./autogen ( Not sure if autogen is necessary any more. It can be done automatically in the scripts. ) To build binaries and packages in the top directory (where the source is) ... depending what you are running on. [Same dir setup as old]. % ./packaging/rpm/build client % ./packaging/deb/build client % ./packaging/sun-pkg/build client To build current working dirs in a subdirectory (rpmbuild, debbuild or pkgbuild) and keep the top clear. % ./packaging/rpm/buildpkg client % ./packaging/rpm/buildpkg client % ./packaging/sun-pkg/buildpkg client The Solaris 11 wasn't fully going until today when I adjusted where the license is installed. > -Original Message- > From: Stefan G. Weichinger > Sent: Friday, March 18, 2022 3:31 AM > To: Chris Hassell ; ? amanda users us...@amanda.org> > Subject: Re: Sent out a pull-request to upgrade the packaging system > > WARNING: This email originated from outside of BETSOL. Do not click links or > open attachments unless you recognize the sender and know the content is safe. > > > Am 17.03.22 um 22:28 schrieb Chris Hassell: > > First of many. It is not configured-and-tested as is but it is very > > close to our working version. > > > > -Versioning based on tags from git > > > > -An in-directory build as well as below-directory package build > > > > -Solaris 10 and Solaris 11 packages > > > > -Better handling of pre/post scripts (may need to update Debian > > ones??) > > > > -Systemd services are included as well. > > > > If I can get someone to look over it and give it a spin I’d really > > appreciate it. > > > > I have more fixes for the installcheck directory to allow some good > > and solid self-tests. > > Nice to see progress. > > I assume you want us to try to build the code in that PR? > > pls point to some howto, I can't remember the procedure anymore (autoconf? > etc) > > I can test on Debian 11, for example. Confidentiality Notice | The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, re-transmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.
SV: Sent out a pull-request to upgrade the packaging system....
Hi, I had missed some packets but know autogen works. I'm getting this error. Thanks Gunnar libtool: link: gcc -Wall -Wextra -Wparentheses -Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat -Wformat-security -Wsign-compare -Wfloat-equal -Wold-style-definition -Wno-strict-aliasing -Wno-unknown-pragmas -Wno-deprecated-declarations "-DAMANDA_FILE=\"amflock-test.o\"" -g -O2 -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -o .libs/amflock-test amflock-test.o -L/usr/lib/64 ./.libs/libamanda.so -L/usr/lib/sparcv9 ./.libs/libtestutils.a -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lsocket -lnsl -lresolv -lintl -lssl -lcrypto -R/opt/lib/amanda ld: fatal: symbol 'tu_debugging_enabled' is multiply-defined: (file amflock-test.o type=OBJT; file ./.libs/libtestutils.a(testutils.o) type=OBJT); collect2: error: ld returned 1 exit status gmake[3]: *** [Makefile:2371: amflock-test] Error 1 gmake[3]: Leaving directory '/root/amanda_compile/amanda-3_5-packaging-upgrade-wip/amanda/common-src' gmake[2]: *** [Makefile:2171: all] Error 2 gmake[2]: Leaving directory '/root/amanda_compile/amanda-3_5-packaging-upgrade-wip/amanda/common-src' gmake[1]: *** [Makefile:1737: all-recursive] Error 1 gmake[1]: Leaving directory '/root/amanda_compile/amanda-3_5-packaging-upgrade-wip/amanda' gmake: *** [Makefile:1661: all] Error 2 -Ursprungligt meddelande- Från: owner-amanda-us...@amanda.org För Gunnarsson, Gunnar Skickat: den 19 mars 2022 11:58 Till: li...@xunil.at; Chris Hassell ; ? amanda users Ämne: SV: Sent out a pull-request to upgrade the packaging system Hi, git clone -b 3_5-packaging-upgrade-wip https://github.com/zmanda/amanda.git git branch * 3_5-packaging-upgrade-wip On solaris these packages are needed pkg install git automake autoconf pkg:/developer/build/libtool gcc cd Amanda ./autogen + set -x + /usr/bin/autoconf configure.ac:25: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. + die 'autoconf [default autoconf version] failed' + echo 'autoconf [default autoconf version] failed' autoconf [default autoconf version] failed + exit 1 This works on the master branch ? Thanks Gunnar -Ursprungligt meddelande- Från: owner-amanda-us...@amanda.org För Stefan G. Weichinger Skickat: den 18 mars 2022 10:31 Till: Chris Hassell ; ? amanda users Ämne: Re: Sent out a pull-request to upgrade the packaging system Am 17.03.22 um 22:28 schrieb Chris Hassell: > First of many. It is not configured-and-tested as is but it is very > close to our working version. > > -Versioning based on tags from git > > -An in-directory build as well as below-directory package build > > -Solaris 10 and Solaris 11 packages > > -Better handling of pre/post scripts (may need to update Debian > ones??) > > -Systemd services are included as well. > > If I can get someone to look over it and give it a spin I’d really > appreciate it. > > I have more fixes for the installcheck directory to allow some good > and solid self-tests. Nice to see progress. I assume you want us to try to build the code in that PR? pls point to some howto, I can't remember the procedure anymore (autoconf? etc) I can test on Debian 11, for example.
SV: Sent out a pull-request to upgrade the packaging system....
Hi, git clone -b 3_5-packaging-upgrade-wip https://github.com/zmanda/amanda.git git branch * 3_5-packaging-upgrade-wip On solaris these packages are needed pkg install git automake autoconf pkg:/developer/build/libtool gcc cd Amanda ./autogen + set -x + /usr/bin/autoconf configure.ac:25: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. + die 'autoconf [default autoconf version] failed' + echo 'autoconf [default autoconf version] failed' autoconf [default autoconf version] failed + exit 1 This works on the master branch ? Thanks Gunnar -Ursprungligt meddelande- Från: owner-amanda-us...@amanda.org För Stefan G. Weichinger Skickat: den 18 mars 2022 10:31 Till: Chris Hassell ; ? amanda users Ämne: Re: Sent out a pull-request to upgrade the packaging system Am 17.03.22 um 22:28 schrieb Chris Hassell: > First of many. It is not configured-and-tested as is but it is very > close to our working version. > > -Versioning based on tags from git > > -An in-directory build as well as below-directory package build > > -Solaris 10 and Solaris 11 packages > > -Better handling of pre/post scripts (may need to update Debian > ones??) > > -Systemd services are included as well. > > If I can get someone to look over it and give it a spin I’d really > appreciate it. > > I have more fixes for the installcheck directory to allow some good > and solid self-tests. Nice to see progress. I assume you want us to try to build the code in that PR? pls point to some howto, I can't remember the procedure anymore (autoconf? etc) I can test on Debian 11, for example.
Re: Sent out a pull-request to upgrade the packaging system....
Am 17.03.22 um 22:28 schrieb Chris Hassell: First of many. It is not configured-and-tested as is but it is very close to our working version. -Versioning based on tags from git -An in-directory build as well as below-directory package build -Solaris 10 and Solaris 11 packages -Better handling of pre/post scripts (may need to update Debian ones??) -Systemd services are included as well. If I can get someone to look over it and give it a spin I’d really appreciate it. I have more fixes for the installcheck directory to allow some good and solid self-tests. Nice to see progress. I assume you want us to try to build the code in that PR? pls point to some howto, I can't remember the procedure anymore (autoconf? etc) I can test on Debian 11, for example.
Sent out a pull-request to upgrade the packaging system....
First of many. It is not configured-and-tested as is but it is very close to our working version. -Versioning based on tags from git -An in-directory build as well as below-directory package build -Solaris 10 and Solaris 11 packages -Better handling of pre/post scripts (may need to update Debian ones??) -Systemd services are included as well. If I can get someone to look over it and give it a spin I’d really appreciate it. I have more fixes for the installcheck directory to allow some good and solid self-tests. n CH Confidentiality Notice | The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, re-transmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.
