Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Re: Dimitri Fontaine > Thanks again folks, I really appreciate the time and effort you're putting > into this, and of course the good results! I got it working, including a workaround that will automatically downgrade scram-sha-256 to md5 on the older distributions where cl-postmodern doesn't understand the newer hash yet. Thanks! Sébastien: The cl-uax-15 autopkgtest is failing: https://qa.debian.org/excuses.php?package=cl-uax-15 (I can reproduce the clisp error here, but not the segfault.) Christoph
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Thanks again folks, I really appreciate the time and effort you're putting into this, and of course the good results! Cheers, happy festivities, -- Dimitri Fontaine d...@tapoueh.org Author of “The Art of PostgreSQL”, https://theartofpostgresql.com On Mon, Dec 20, 2021, at 22:54, Christoph Berg wrote: > Re: Sébastien Villemot >> I’ve uploaded a new cl-esrap. It seems pgloader builds again. > > Merci! I'll try to polish the package over the next days. > > Christoph
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Re: Sébastien Villemot > I’ve uploaded a new cl-esrap. It seems pgloader builds again. Merci! I'll try to polish the package over the next days. Christoph
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Le vendredi 10 décembre 2021 à 10:27 +0100, Sébastien Villemot a écrit : > > The problem seems again related to cl-esrap. I noticed that the Debian > package tracks an old (dead) upstream, while there is a new alive fork. > I’ll take over that package and hopefully fix the problem. I’ve uploaded a new cl-esrap. It seems pgloader builds again. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Le jeudi 09 décembre 2021 à 16:10 +0100, Christoph Berg a écrit :
> Re: To Sébastien Villemot
> > Unfortunately, pgloader still doesn't compile:
>
> > While evaluating the form starting at line 21, column 0
> > of
> > #P"/srv/projects/postgresql/pgloader/pgloader/dumper-2SKVI5f7.lisp":Fatal
> > SIMPLE-ERROR:
> > Compilation failed: * is not permitted as an argument to the FUNCTION
> > type specifier in /usr/share/common-lisp/source/esrap/src/evaluator.lisp
>
> Looking around for something else I discovered #999625 in cl-esrap
> which fixes this problem. I uploaded the fix in an NMU. (I guess you
> might also take over that package?)
>
> But pgloader still doesn't build: :(
>
> ; wrote
> /srv/projects/postgresql/pgloader/pgloader/debian/home/.cache/common-lisp/sbcl-2.1.11.debian-linux-x64/usr/share/common-lisp/source/abnf/abnf-tmp5FHTGX61.fasl
> ; compilation finished in 0:00:00.080
> While evaluating the form starting at line 21, column 0
> of
> #P"/srv/projects/postgresql/pgloader/pgloader/dumper-2SKVI5f7.lisp":Fatal
> TYPE-ERROR:
> The values
> (# :IN
>
> "/srv/projects/postgresql/pgloader/pgloader/debian/home/.cache/common-lisp/sbcl-2.1.11.debian-linux-x64/usr/share/common-lisp/source/abnf/abnf.fasl")
> {53C1EADB}>
> NIL NIL)
>
> are not of type
> (VALUES FUNCTION )
The problem seems again related to cl-esrap. I noticed that the Debian
package tracks an old (dead) upstream, while there is a new alive fork.
I’ll take over that package and hopefully fix the problem.
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name
⠈⠳⣄ https://www.debian.org
signature.asc
Description: This is a digitally signed message part
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Re: To Sébastien Villemot > Unfortunately, pgloader still doesn't compile: > While evaluating the form starting at line 21, column 0 > of > #P"/srv/projects/postgresql/pgloader/pgloader/dumper-2SKVI5f7.lisp":Fatal > SIMPLE-ERROR: > Compilation failed: * is not permitted as an argument to the FUNCTION type > specifier in /usr/share/common-lisp/source/esrap/src/evaluator.lisp Looking around for something else I discovered #999625 in cl-esrap which fixes this problem. I uploaded the fix in an NMU. (I guess you might also take over that package?) But pgloader still doesn't build: :( ; wrote /srv/projects/postgresql/pgloader/pgloader/debian/home/.cache/common-lisp/sbcl-2.1.11.debian-linux-x64/usr/share/common-lisp/source/abnf/abnf-tmp5FHTGX61.fasl ; compilation finished in 0:00:00.080 While evaluating the form starting at line 21, column 0 of #P"/srv/projects/postgresql/pgloader/pgloader/dumper-2SKVI5f7.lisp":Fatal TYPE-ERROR: The values (# NIL NIL) are not of type (VALUES FUNCTION ) (DUMPER518::BACKTRACE-AS-LIST) ; ; compilation unit aborted ; caught 1 fatal ERROR condition ; caught 51 STYLE-WARNING conditions ; printed 4719 notes Christoph
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Re: Sébastien Villemot > The updated cl-postmodern just entered unstable. Salut Sébastien, that is excellent news, thanks! Unfortunately, pgloader still doesn't compile: ; compiling file "/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp" (written 12 OCT 2021 03:11:59 PM): ; file: /usr/share/common-lisp/source/cl-asdf/build/asdf.lisp ; in: DEFUN CALL-WITH-OUTPUT ; (WITH-OUTPUT-TO-STRING (STREAM NIL :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE) ; (FUNCALL FUNCTION STREAM)) ; --> LET ; ==> ; (MAKE-STRING 31 :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE) ; ; note: could not stack allocate: ;(WITH-OUTPUT-TO-STRING (STREAM NIL :ELEMENT-TYPE ELEMENT-TYPE) ; (FUNCALL FUNCTION STREAM)) ; in: DEFUN SLURP-STREAM-STRING ; (WITH-OUTPUT-TO-STRING ; (UIOP/STREAM::OUTPUT NIL :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE) ; (UIOP/STREAM:COPY-STREAM-TO-STREAM UIOP/STREAM::INPUT UIOP/STREAM::OUTPUT ; :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE)) ; --> LET ; ==> ; (MAKE-STRING 31 :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE) ; ; note: could not stack allocate: ;(WITH-OUTPUT-TO-STRING (OUTPUT NIL :ELEMENT-TYPE ELEMENT-TYPE) ; (COPY-STREAM-TO-STREAM INPUT OUTPUT :ELEMENT-TYPE ELEMENT-TYPE)) ; wrote /srv/projects/postgresql/pgloader/pgloader/debian/home/.cache/common-lisp/sbcl-2.1.11.debian-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf-tmpGHU3ALSV.fasl ; compilation finished in 0:00:05.412 ; ; compilation unit finished ; printed 2 notes ;; loading file #P"/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp" ;; loading system "asdf-finalizers" ;; loading system "asdf-system-connections" ;; loading system "cffi" ;; loading system "cl+ssl" ;; loading system "mssql" ;; loading file #P"/srv/projects/postgresql/pgloader/pgloader/src/hooks.lisp" ;; loading system "pgloader" Fatal SIMPLE-ERROR: Compilation failed: * is not permitted as an argument to the FUNCTION type specifier in /usr/share/common-lisp/source/esrap/src/evaluator.lisp cat buildapp.log ;; loading file #P"/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp" ;; loading #P"/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp" ;; # ;; # ;; (:ASDF3.3 :ASDF3.2 :ASDF3.1 :ASDF3 :ASDF2 :ASDF :OS-UNIX :NON-BASE-CHARS-EXIST-P :ASDF-UNICODE :X86-64 :GENCGC :64-BIT :ANSI-CL ... ; processing (DEFVAR *CURRENT-RULE* ...) ; processing (DEFUN COMPILE-RULE ...) ; processing (DEFUN EVAL-EXPRESSION ...) ; processing (DECLAIM (FTYPE # ...)) While evaluating the form starting at line 21, column 0 of #P"/srv/projects/postgresql/pgloader/pgloader/dumper-2SKVI5f7.lisp":Fatal SIMPLE-ERROR: Compilation failed: * is not permitted as an argument to the FUNCTION type specifier in /usr/share/common-lisp/source/esrap/src/evaluator.lisp (DUMPER518::BACKTRACE-AS-LIST) ; wrote /srv/projects/postgresql/pgloader/pgloader/debian/home/.cache/common-lisp/sbcl-2.1.11.debian-linux-x64/usr/share/common-lisp/source/esrap/src/evaluator-tmpT2G5POAL.fasl ; compilation finished in 0:00:00.144 ; ; compilation unit aborted ; caught 2 fatal ERROR conditions ; caught 48 STYLE-WARNING conditions ; printed 4591 notes I have to admit that I have no clue where to even start debugging this, there is no file called "dumper" in the source tree. Would it be possible that you could have a look? Christoph
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Le mardi 02 novembre 2021 à 17:07 +0100, Christoph Berg a écrit : > Re: Sébastien Villemot > > I am going to package cl-uax-15 and cl-global-vars (ITPs are marked as > > blocking the present bug), and then upgrade cl-postmodern. > > That sounds excellent, merci! The updated cl-postmodern just entered unstable. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Re: Sébastien Villemot > I am going to package cl-uax-15 and cl-global-vars (ITPs are marked as > blocking the present bug), and then upgrade cl-postmodern. That sounds excellent, merci! Christoph
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Hi Christoph, Le mercredi 06 octobre 2021 à 23:14 +0200, Christoph Berg a écrit : > Package: pgloader > Version: 3.6.2-1 > Severity: grave > Tags: ftbfs > > pgloader is currently not supporting PG14's new default of scram > authentication: > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/pgloader/15809976/log.gz > > KABOOM! > FATAL error: Failed to connect to pgsql at "localhost" (port 5433) as user > "postgres": 10 fell through ECASE expression. Wanted one of (0 2 3 4 5 6 7 8). > Date/time: 2021-10-06-16:12! > An unhandled error condition has been signalled: >Failed to connect to pgsql at "localhost" (port 5433) as user "postgres": > 10 fell through ECASE expression. Wanted one of (0 2 3 4 5 6 7 8). > > To fix this, cl-postmodern needs upgrading, but the new version > requires (at least) the yet-unpackaged "uax-15" and "global-vars" CL > modules. I am going to package cl-uax-15 and cl-global-vars (ITPs are marked as blocking the present bug), and then upgrade cl-postmodern. Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Package: pgloader Version: 3.6.2-1 Severity: grave Tags: ftbfs pgloader is currently not supporting PG14's new default of scram authentication: https://ci.debian.net/data/autopkgtest/testing/amd64/p/pgloader/15809976/log.gz KABOOM! FATAL error: Failed to connect to pgsql at "localhost" (port 5433) as user "postgres": 10 fell through ECASE expression. Wanted one of (0 2 3 4 5 6 7 8). Date/time: 2021-10-06-16:12! An unhandled error condition has been signalled: Failed to connect to pgsql at "localhost" (port 5433) as user "postgres": 10 fell through ECASE expression. Wanted one of (0 2 3 4 5 6 7 8). To fix this, cl-postmodern needs upgrading, but the new version requires (at least) the yet-unpackaged "uax-15" and "global-vars" CL modules. An easy workaround would be to include `-i '--auth-local=peer --auth-host=md5'` in debian/tests/ssl, but currently pgloader does not compile: ;; loading system "pgloader" Fatal TYPE-ERROR: The values (# NIL NIL) are not of type (VALUES FUNCTION ) I'm giving up at this point, can anyone from the Lisp team help? (Is buildapp still the way to go to build lisp apps?) Thanks, Christoph
