Re: [GNC-dev] Building debian files within Docker

[Dale Phurrough via gnucash-devel]

Good news :-) Next? I recommend the setup and quick start at
https://github.com/diablodale/gnucash-dev-docker
If you encounter problems following that, please do loop me in. I want to
fix it/be more clear while balancing with brevity.

Yes, the build/test containers are themselves many distros of Linux.
They've been building and testing 3 branches of Gnucash on 14 of the major
distros for two months https://diablodale.github.io/gnucash-dev-docker/
You can click on any of the badges to see the log of the build and test
process for that specific distro/branch.
The docker-compose in the git repo has all the distros you mention except
for cosmic (18.10).
Probably trivial to add cosmic. Edit docker-compose.yml, make a copy of the
19.04 section that is already in there to make a new section for 18.10
while changing the four occurrences in that new section from "19.04" to
"18.10"

Happy hacking!
--Dale


On Thu, Sep 12, 2019 at 6:27 PM Stephen M. Butler  wrote:

> On 9/12/19 5:49 AM, Dale Phurrough wrote:
> > I'm not the best source for supporting Ubuntu.
>
> Better than I am!!
>
> > Ubuntu has rich communities that are better suited to support ubuntu
> > and apt.
> >
> https://www.google.com/search?q=Invalid+response+from+proxy%3A+HTTP%2F1.0+403+CONNECT+denied+(ask+the+admin+to+allow+HTTPS+tunnels)+%5BIP%3A+127.0.0.1+3142%5D=Invalid+response+from+proxy%3A+HTTP%2F1.0+403+CONNECT+denied+(ask+the+admin+to+allow+HTTPS+tunnels)+%5BIP%3A+127.0.0.1+3142%5D=chrome..69i57.4253j0j4=chrome=UTF-8
> >
>
> I searched my package list and see that apt-cacher-ng is installed.  I
> presume that is the package you meant to mention.  I made the change for
> the "Passthru" entry (it was commented out in the config file).  That
> allowed the add-apt-repository to work.  I now have the engine installed
> and wondering what is next?
>
> >
> >
> > After you get apt running, and then Docker is install, happy to help
> > with the dev-docker containers. :-)
> >
> > --Dale
> >
> OK.  I think I'm ready.  Not sure how many of these containers I need.
> Mostly interested in building .deb files for Ubuntu (disco and bionic --
> maybe need cosmic).
>
> How good is this for non-Ubuntu but debian based distros?  Cross build I
> mean (buster, stretch?).
>
> Thanks,
>
> --Steve
>
> --
> Stephen M Butler, PMP, PSM
> stephen.m.butle...@gmail.com
> kg...@arrl.net
> 253-350-0166
> ---
> GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8
>
>
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Building debian files within Docker

[Stephen M. Butler]

On 9/12/19 5:49 AM, Dale Phurrough wrote:
> I'm not the best source for supporting Ubuntu.

Better than I am!!

> Ubuntu has rich communities that are better suited to support ubuntu
> and apt.
> https://www.google.com/search?q=Invalid+response+from+proxy%3A+HTTP%2F1.0+403+CONNECT+denied+(ask+the+admin+to+allow+HTTPS+tunnels)+%5BIP%3A+127.0.0.1+3142%5D=Invalid+response+from+proxy%3A+HTTP%2F1.0+403+CONNECT+denied+(ask+the+admin+to+allow+HTTPS+tunnels)+%5BIP%3A+127.0.0.1+3142%5D=chrome..69i57.4253j0j4=chrome=UTF-8
>

I searched my package list and see that apt-cacher-ng is installed.  I
presume that is the package you meant to mention.  I made the change for
the "Passthru" entry (it was commented out in the config file).  That
allowed the add-apt-repository to work.  I now have the engine installed
and wondering what is next?

>
>
> After you get apt running, and then Docker is install, happy to help
> with the dev-docker containers. :-)
>
> --Dale
>
OK.  I think I'm ready.  Not sure how many of these containers I need. 
Mostly interested in building .deb files for Ubuntu (disco and bionic --
maybe need cosmic). 

How good is this for non-Ubuntu but debian based distros?  Cross build I
mean (buster, stretch?).

Thanks,

--Steve

-- 
Stephen M Butler, PMP, PSM
stephen.m.butle...@gmail.com
kg...@arrl.net
253-350-0166
---
GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Building debian files within Docker

[Dale Phurrough via gnucash-devel]

I'm not the best source for supporting Ubuntu. Ubuntu has rich communities
that are better suited to support ubuntu and apt.
https://www.google.com/search?q=Invalid+response+from+proxy%3A+HTTP%2F1.0+403+CONNECT+denied+(ask+the+admin+to+allow+HTTPS+tunnels)+%5BIP%3A+127.0.0.1+3142%5D=Invalid+response+from+proxy%3A+HTTP%2F1.0+403+CONNECT+denied+(ask+the+admin+to+allow+HTTPS+tunnels)+%5BIP%3A+127.0.0.1+3142%5D=chrome..69i57.4253j0j4=chrome=UTF-8


Though...reading the error message, it suggests that you have a http proxy
somewhere between the 'apt' and the deb repository. And that this proxy
isn't configured to allow the needed connectivity.
Also in the error message is port 3142. Cross-referencing that port and
some of the above google results
are you using apt-catcher or apt-catcher-ng or something like it? That
port, with that software, with that error appears several times with
google. Below link writes specific configuration is needed with that
software.
https://blog.packagecloud.io/eng/2015/05/05/using-apt-cacher-ng-with-ssl-tls/#ssltls-https-setup

https://github.com/sameersbn/docker-apt-cacher-ng/issues/10

After you get apt running, and then Docker is install, happy to help with
the dev-docker containers. :-)

--Dale

On Thu, Sep 12, 2019 at 12:25 AM Stephen M. Butler  wrote:

> I tried.  Got rid of the snap version of docker and then hung up on this
> step:
>
> sudo add-apt-repository \
> >"deb [arch=amd64] https://download.docker.com/linux/ubuntu \
> >$(lsb_release -cs) \
> >stable"
> Err:1 https://download.docker.com/linux/ubuntu disco InRelease
>   Invalid response from proxy: HTTP/1.0 403 CONNECT denied (ask the
> admin to allow HTTPS tunnels) [IP: 127.0.0.1 3142]
> Hit:2 http://archive.canonical.com/ubuntu disco
>
> InRelease
>
> Hit:3 http://archive.ubuntu.com/ubuntu disco
>
> InRelease
>
> Hit:4 http://us.archive.ubuntu.com/ubuntu disco
> InRelease
> Hit:5 http://security.ubuntu.com/ubuntu disco-security
> InRelease
> Hit:6 http://ppa.launchpad.net/malteworld/ppa/ubuntu bionic
> InRelease
> Hit:7 http://us.archive.ubuntu.com/ubuntu disco-updates
> InRelease
> Hit:8 http://ppa.launchpad.net/subsurface/subsurface/ubuntu disco
> InRelease
> Hit:9 http://us.archive.ubuntu.com/ubuntu disco-backports InRelease
> Hit:10 http://ppa.launchpad.net/teejee2008/ppa/ubuntu disco InRelease
> Reading package lists... Done
> W: Failed to fetch
> https://download.docker.com/linux/ubuntu/dists/disco/InRelease  Invalid
> response from proxy: HTTP/1.0 403 CONNECT denied (ask the admin to allow
> HTTPS tunnels) [IP: 127.0.0.1 3142]
> W: Some index files failed to download. They have been ignored, or old
> ones used instead.
>
> So, how do I allow HTTPS tunnels?
>
> --Steve
>
> On 9/10/19 6:27 PM, Dale Phurrough wrote:
> > I'm not a good resource to troubleshoot snap. In the error message you
> > got, it gave a url. I clicked and there's a lot of information at that
> > post on the topic. Perhaps it can help you.
> >
> > Meanwhile, the stable docker 19.03 just appeared today on Docker's
> > official package repos. And it supports Ubuntu Disco. You can use
> > https://get.docker.com/ if you want for easy install. Or follow the
> > written instructions
> > at https://docs.docker.com/install/linux/docker-ce/ubuntu/
> >
> > Timing! ;-)
> >
> > --Dale
> >
> >
> >
> >
> > On Wed, Sep 11, 2019 at 12:23 AM Stephen M. Butler  > > wrote:
> >
> > Dale,
> >
> > I got the message about missing /snap/bin in the Path, but it is
> > there.
> > Any ideas on how to proceed?
> >
> > steve@SteveLaptop:~$ sudo snap install docker
> > Connect docker:firewall-control to core:firewall-control
> >  Warning: /snap/bin was not found in your $PATH. If you've
> not
> > restarted your session since you
> >  installed snapd, try doing that. Please see
> > https://forum.snapcraft.io/t/9469 for more
> >  details.
> >
> > docker 18.06.1-ce from Canonical✓ installed
> >
> > steve@SteveLaptop:~$ echo $PATH
> >
>  
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
> >
> > steve@SteveLaptop:~$ snap version
> > snap2.41
> > snapd   2.41
> > series  16
> > ubuntu  19.04
> > kernel  5.0.0-27-generic
> >
> > steve@SteveLaptop:~$ cat /etc/os-release
> > NAME="Ubuntu"
> > VERSION="19.04 (Disco Dingo)"
> > ID=ubuntu
> > ID_LIKE=debian
> > PRETTY_NAME="Ubuntu 19.04"
> > VERSION_ID="19.04"
> > HOME_URL="https://www.ubuntu.com/;
> > SUPPORT_URL="https://help.ubuntu.com/;
> > BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
> > PRIVACY_POLICY_URL="
> https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
> > VERSION_CODENAME=disco
> > UBUNTU_CODENAME=disco
> >
> > steve@SteveLaptop:~$ ps
> >   PID TTY  TIME CMD
> >  2746 pts/000:00:00 bash
> >  4469 pts/000:00:00 ps

Re: [GNC-dev] Build error with scm-engine on current master

[Geert Janssens]

Hi Christian,

With the last commit on master it works here now.

Can you retry ?

Geert

Op donderdag 12 september 2019 09:47:43 CEST schreef Geert Janssens:
> Hi Christian,
> 
> Thanks to your detailed description I can now reproduce the problem when
> building master with "make" rather than "ninja".
> 
> Turns out there's a hidden circular dependency between engine.scm and
> engine- utilities.scm via the call to
> (gnc:module-begin-syntax (gnc:module-load "gnucash/engine" 0))
> 
> I have a fix ready for this particular case, but there are more of these so
> I'm still working through the others.
> 
> Regards,
> 
> Geert
> 
> Op donderdag 12 september 2019 00:46:13 CEST schreef Christian Gruber:
> > This thread is related to the build issue I encountered when finally
> > building PR #574  locally.
> > 
> > Invoking "make all" on current master lead to the following build error
> > when compiling libgnucash/engine/engine-utilities.scm:
> > 
> > Backtrace:1 (primitive-load-path
> > "gnucash/engine/gnc-numeric") In ice-9/boot-9.scm:752:25  0
> > (dispatch-exception _ _ _) ice-9/boot-9.scm:752:25: In procedure
> > dispatch-exception: In procedure primitive-load-path: Unable to find
> > file "gnucash/engine/gnc-numeric" in load path
> > 
> > File libgnucash/engine/engine-utilities.scm is built with target
> > scm-engine-1, therefore the same build error can be reproduced by
> > invoking "make scm-engine-1" or "make scm-engine" as well.
> > 
> > According to PR #574   I
> > can preclude, that this is due to reusing a maint build directory, since
> > I built in a clean and fresh build dir.
> > 
> > Next I tried to build again after moving directories
> > /usr/lib/x86_64-linux-gnu/gnucash/gnucash and files
> > /usr/lib/x86_64-linux-gnu/gnucash/libgnc*.so.
> > 
> > After that I uninstalled my GnuCash 3.5, which was installed before from
> > distros package manager.
> > 
> > Finally I searched my whole system for gnucash directories and removed
> > them in /usr/local/... where I previously installed GnuCash built from
> > source repo.
> > 
> > Everytime I built in a clean and fresh build dir, but the build error
> > was always the same.
> > 
> > Finally I further investigated sources and found a maybe important
> > change in file libgnucash/engine/engine.scm made in commit 53f59f7.
> > Therefore I tried two builds at the end, one with commit 53f59f7 and the
> > second with commit cb50f7a, which is one commit before 53f59f7. The
> > result was, that commit 53f59f7 leads to the mentioned build error, but
> > commit cb50f7a could successfully be built.
> > 
> > Any ideas?
> > 
> > Christian
> > 
> > ___
> > gnucash-devel mailing list
> > gnucash-devel@gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel




___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Build error with scm-engine on current master

[Geert Janssens]

Hi Christian,

Thanks to your detailed description I can now reproduce the problem when 
building master with "make" rather than "ninja".

Turns out there's a hidden circular dependency between engine.scm and engine-
utilities.scm via the call to
(gnc:module-begin-syntax (gnc:module-load "gnucash/engine" 0))

I have a fix ready for this particular case, but there are more of these so 
I'm still working through the others.

Regards,

Geert

Op donderdag 12 september 2019 00:46:13 CEST schreef Christian Gruber:
> This thread is related to the build issue I encountered when finally
> building PR #574  locally.
> 
> Invoking "make all" on current master lead to the following build error
> when compiling libgnucash/engine/engine-utilities.scm:
> 
> Backtrace:1 (primitive-load-path
> "gnucash/engine/gnc-numeric") In ice-9/boot-9.scm:752:25  0
> (dispatch-exception _ _ _) ice-9/boot-9.scm:752:25: In procedure
> dispatch-exception: In procedure primitive-load-path: Unable to find
> file "gnucash/engine/gnc-numeric" in load path
> 
> File libgnucash/engine/engine-utilities.scm is built with target
> scm-engine-1, therefore the same build error can be reproduced by
> invoking "make scm-engine-1" or "make scm-engine" as well.
> 
> According to PR #574   I
> can preclude, that this is due to reusing a maint build directory, since
> I built in a clean and fresh build dir.
> 
> Next I tried to build again after moving directories
> /usr/lib/x86_64-linux-gnu/gnucash/gnucash and files
> /usr/lib/x86_64-linux-gnu/gnucash/libgnc*.so.
> 
> After that I uninstalled my GnuCash 3.5, which was installed before from
> distros package manager.
> 
> Finally I searched my whole system for gnucash directories and removed
> them in /usr/local/... where I previously installed GnuCash built from
> source repo.
> 
> Everytime I built in a clean and fresh build dir, but the build error
> was always the same.
> 
> Finally I further investigated sources and found a maybe important
> change in file libgnucash/engine/engine.scm made in commit 53f59f7.
> Therefore I tried two builds at the end, one with commit 53f59f7 and the
> second with commit cb50f7a, which is one commit before 53f59f7. The
> result was, that commit 53f59f7 leads to the mentioned build error, but
> commit cb50f7a could successfully be built.
> 
> Any ideas?
> 
> Christian
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel




___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel