Thread: yum repo, pgloader
this question is mostly for devrim, who maintains the RHEL/CentOS/Fedora PGDG yum repositories... I note that pgloader is in the yum repo for Postgresql 9.2 on Centos 6, but not 9.3, 9.4, 9.5, wondering if there's a reason it was dropped? -- john r pierce, recycling bits in santa cruz
On 07/22/2016 05:24 PM, John R Pierce wrote: > this question is mostly for devrim, who maintains the RHEL/CentOS/Fedora > PGDG yum repositories... > > I note that pgloader is in the yum repo for Postgresql 9.2 on Centos 6, > but not 9.3, 9.4, 9.5, wondering if there's a reason it was dropped? If I where to hazard a guess it would have to do with pgloader migrating from being written in Python to being written in Common Lisp, that occurred at roughly the same time. > > > -- Adrian Klaver adrian.klaver@aklaver.com
On 7/22/2016 5:50 PM, Adrian Klaver wrote: > > If I where to hazard a guess it would have to do with pgloader > migrating from being written in Python to being written in Common > Lisp, that occurred at roughly the same time. ah, yer right, the one in the pg 9.2 repo is 2.3.x, and indeed, pgloader v2 was python. https://github.com/dimitri/pgloader/tree/pgloader-v2 I've spent all day trying to build the lisp code on centos 6 with a lot of frustration. last time I even sniffed around the edges of lisp was in the 1970s. I've successfully built sbcl 1.3, and it passes its self test. building pgloader, I'm currently stuck at... [package pgloader]................................ .................................................. .................................................. .........; ; caught ERROR: ; READ error during COMPILE-FILE: ; ; Symbol "*IXF-STREAM*" not found in the IXF package. ; ; Line: 70, Column: 25, File-Position: 2414 ; ; Stream: #<SB-INT:FORM-TRACKING-STREAM for "file /home/piercej/pgloader-3.2.2/src/sources/ixf/ixf-schema.lisp" {1006D2FDD3}> debugger invoked on a UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<THREAD "main thread" RUNNING {1002916D53}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "pgloader" "src" "sources" "ixf" "ixf-schema"> Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [RETRY ] Retry compiling #<CL-SOURCE-FILE "pgloader" "src" "sources" "ixf" "ixf-schema">. 1: [ACCEPT ] Continue, treating compiling #<CL-SOURCE-FILE "pgloader" "src" "sources" "ixf" "ixf-schema"> as having been successful. 2: Retry ASDF operation. 3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 4: [ABORT ] Give up on "pgloader" 5: [CONTINUE ] Ignore runtime option --eval "(ql:quickload \"pgloader\")". 6: Skip rest of --eval and --load options. 7: Skip to toplevel READ/EVAL/PRINT loop. 8: [EXIT ] Exit SBCL (calling #'EXIT, killing the process). (UIOP/LISP-BUILD:CHECK-LISP-COMPILE-RESULTS NIL T T "~/asdf-action::format-action/" ((#<ASDF/LISP-ACTION:COMPILE-OP > . #<ASDF/LISP-ACTION:CL-SOURCE-FILE"pgloader" "src" "sources" "ixf" "ixf-schema">))) 0] and have no idea how to proceed. btw, `make` processes that go and download huge chunks of code from 3rd party sites scare the bejeezzus out of me. maybe I'll dig out the v2 python code and try it. it should be a lot easier to deploy in our overseas manufacturing production data centers, anyways. -- john r pierce, recycling bits in santa cruz
On 07/22/2016 06:09 PM, John R Pierce wrote: > On 7/22/2016 5:50 PM, Adrian Klaver wrote: >> >> If I where to hazard a guess it would have to do with pgloader >> migrating from being written in Python to being written in Common >> Lisp, that occurred at roughly the same time. > > ah, yer right, the one in the pg 9.2 repo is 2.3.x, and indeed, pgloader > v2 was python. > > https://github.com/dimitri/pgloader/tree/pgloader-v2 > > I've spent all day trying to build the lisp code on centos 6 with a lot > of frustration. last time I even sniffed around the edges of lisp was > in the 1970s. I've successfully built sbcl 1.3, and it passes its self > test. building pgloader, I'm currently stuck at... > > [package pgloader]................................ > .................................................. > .................................................. > .........; > ; caught ERROR: > ; READ error during COMPILE-FILE: > ; > ; Symbol "*IXF-STREAM*" not found in the IXF package. > ; > ; Line: 70, Column: 25, File-Position: 2414 > ; > ; Stream: #<SB-INT:FORM-TRACKING-STREAM for "file > /home/piercej/pgloader-3.2.2/src/sources/ixf/ixf-schema.lisp" {1006D2FDD3}> > > debugger invoked on a UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread > #<THREAD "main thread" RUNNING {1002916D53}>: > COMPILE-FILE-ERROR while > compiling #<CL-SOURCE-FILE "pgloader" "src" "sources" "ixf" "ixf-schema"> > > Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. > > restarts (invokable by number or by possibly-abbreviated name): > 0: [RETRY ] Retry > compiling #<CL-SOURCE-FILE > "pgloader" "src" "sources" "ixf" "ixf-schema">. > 1: [ACCEPT ] Continue, treating > compiling #<CL-SOURCE-FILE > "pgloader" "src" "sources" "ixf" "ixf-schema"> > as having been successful. > 2: Retry ASDF operation. > 3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after > resetting the > configuration. > 4: [ABORT ] Give up on "pgloader" > 5: [CONTINUE ] Ignore runtime option --eval > "(ql:quickload \"pgloader\")". > 6: Skip rest of --eval and --load > options. > 7: Skip to toplevel READ/EVAL/PRINT loop. > 8: [EXIT ] Exit SBCL (calling #'EXIT, killing > the process). > > (UIOP/LISP-BUILD:CHECK-LISP-COMPILE-RESULTS NIL T T > "~/asdf-action::format-action/" ((#<ASDF/LISP-ACTION:COMPILE-OP > . > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "pgloader" "src" "sources" "ixf" > "ixf-schema">))) > 0] > > > and have no idea how to proceed. btw, `make` processes that go and > download huge chunks of code from 3rd party sites scare the bejeezzus > out of me. If it is any consolation I get the same error here compiling on openSUSE 13.2 with sbcl 1.2.3. Looking in the source(ixf-schema.lisp, ixf.lisp) I see the lower case version of *IXF-STREAM*. Not sure what is going on, will do some more digging later. > > maybe I'll dig out the v2 python code and try it. it should be a lot > easier to deploy in our overseas manufacturing production data centers, > anyways. > > -- Adrian Klaver adrian.klaver@aklaver.com
> On Jul 23, 2016, at 9:29 AM, Adrian Klaver <adrian.klaver@aklaver.com> wrote: > > If it is any consolation I get the same error here compiling on openSUSE 13.2 with sbcl 1.2.3. Looking in the source(ixf-schema.lisp,ixf.lisp) I see the lower case version of *IXF-STREAM*. Not sure what is going on, will do some moredigging later. See https://github.com/dimitri/pgloader/issues/296 John DeSoi, Ph.D.
On 07/23/2016 12:08 PM, John DeSoi wrote: > >> On Jul 23, 2016, at 9:29 AM, Adrian Klaver <adrian.klaver@aklaver.com> wrote: >> >> If it is any consolation I get the same error here compiling on openSUSE 13.2 with sbcl 1.2.3. Looking in the source(ixf-schema.lisp,ixf.lisp) I see the lower case version of *IXF-STREAM*. Not sure what is going on, will do some moredigging later. > > See > > https://github.com/dimitri/pgloader/issues/296 Just before you posted I found this issue: https://github.com/dimitri/pgloader/issues/357 and did what was suggested which was to download: http://pgloader.io/files/pgloader-bundle-3.3.0.50.tgz Doing so and running sbcl over the new files resulted in a successful pgloader compilation. > > John DeSoi, Ph.D. > > -- Adrian Klaver adrian.klaver@aklaver.com
On 7/22/2016 5:50 PM, Adrian Klaver wrote:
On 07/22/2016 05:24 PM, John R Pierce wrote:I note that pgloader is in the yum repo for Postgresql 9.2 on Centos 6,
but not 9.3, 9.4, 9.5, wondering if there's a reason it was dropped?
If I where to hazard a guess it would have to do with pgloader migrating from being written in Python to being written in Common Lisp, that occurred at roughly the same time.
While I could get the common lisp version working on my systems, I don't want to have to support it in our overseas factories where we need this functionality, so I'm trying to make a go of using the older v2, written in Python, as introducing a completely new language for a single tool in our production operations stack is untenable.
However, I can't seem to find any traces of the documentation for the python version other than the man page.
-- john r pierce, recycling bits in santa cruz
On 07/26/2016 12:54 PM, John R Pierce wrote: > On 7/22/2016 5:50 PM, Adrian Klaver wrote: >> On 07/22/2016 05:24 PM, John R Pierce wrote: >>> I note that pgloader is in the yum repo for Postgresql 9.2 on Centos 6, >>> but not 9.3, 9.4, 9.5, wondering if there's a reason it was dropped? >> >> If I where to hazard a guess it would have to do with pgloader >> migrating from being written in Python to being written in Common >> Lisp, that occurred at roughly the same time. > > While I could get the common lisp version working on my systems, I don't > want to have to support it in our overseas factories where we need this > functionality, so I'm trying to make a go of using the older v2, written > in Python, as introducing a completely new language for a single tool > in our production operations stack is untenable. Are the overseas systems running Centos 6 also? If so, can't you copy over the compiled pgloader binary from your machine to theirs? > > However, I can't seem to find any traces of the documentation for the > python version other than the man page. > > > -- > john r pierce, recycling bits in santa cruz > -- Adrian Klaver adrian.klaver@aklaver.com