Re: bug#22883: Authenticating Git checkouts: step #1

2019-12-28 Thread Efraim Flashner
On Sat, Dec 28, 2019 at 06:45:34PM -0800, Vagrant Cascadian wrote: > On 2019-12-27, Ricardo Wurmus wrote: > >> b3011dbbd2 doc: Mention "make authenticate". > >> 787766ed1e git-authenticate: Keep a local cache of > >> previously-authenticated commits. > >> 785af04a75 git: 'commit-difference'

Re: bug#22883: Authenticating Git checkouts: step #1

2019-12-28 Thread Vagrant Cascadian
On 2019-12-27, Ricardo Wurmus wrote: >> b3011dbbd2 doc: Mention "make authenticate". >> 787766ed1e git-authenticate: Keep a local cache of >> previously-authenticated commits. >> 785af04a75 git: 'commit-difference' takes a list of excluded commits. >> 1e43ab2c03 Add 'build-aux/git-authenti

Re: [PATCH 1/2] Support publishing build events

2019-12-28 Thread Christopher Baines
I've finally got back around to looking at this again, I've sent a new v4 version which is a slimmed down version of the previous patch. The events table itself is now used as the queue, with sent events being deleted. The table is also only populated if the --record-events option is set when runn

[PATCH v4 1/2] Support publishing build events

2019-12-28 Thread Christopher Baines
Add a table to store events, which have a type and a JSON blob. These can be used to record changes, this commit inserts events when new builds are created, and when the status of builds change. The EventsOutbox table is then used to track when events have been sent out. This is done through the n

[PATCH v4 2/2] Support publishing evaluation events

2019-12-28 Thread Christopher Baines
* src/cuirass/database.scm (db-add-evaluation): Record the creation of new evaluations as events. (db-set-evaluation-done): Record when evaluations finish as an event. * src/cuirass/http.scm (url-handler): Add a new /api/evaluation-events page. --- src/cuirass/database.scm | 13 +++-- 1 fi

[PATCH v3 1/2] Support publishing build events

2019-12-28 Thread Christopher Baines
Add a table to store events, which have a type and a JSON blob. These can be used to record changes, this commit inserts events when new builds are created, and when the status of builds change. The EventsOutbox table is then used to track when events have been sent out. This is done through the n

[PATCH v3 2/2] Support publishing evaluation events

2019-12-28 Thread Christopher Baines
* src/cuirass/database.scm (db-add-evaluation): Record the creation of new evaluations as events. (db-set-evaluation-done): Record when evaluations finish as an event. * src/cuirass/http.scm (url-handler): Add a new /api/evaluation-events page. --- src/cuirass/database.scm | 13 +++-- 1 fi

System monitoring

2019-12-28 Thread Pjotr Prins
I was looking to deploy Nagios on our servers, but I am discouraged by its architecture. I would like something minimalistic that can run anywhere (including small routers). System monitoring has a number of important components, but they could all be simple and written in guile: 1. a (small) m

right location for gitlab-runner

2019-12-28 Thread Reza Alizadeh Majd
Hi, I had prepare a package for `gitlab-runner`: https://docs.gitlab.com/runner/ but I'm not sure about the right place to submit regarding patch. is the `gnu/packages/ci.scm` is a good location to submit this package? -- Regards Reza Alizadeh Majd PantherX Team

Re: Packaging Jami progress

2019-12-28 Thread Jan
On Sat, 28 Dec 2019 10:53:33 +0100 Pierre Neidhardt wrote: > Allow me to explain a little more: > > Binaries embed a value called RPATH which points to the locations > where to load dynamic libraries (also called "shared objects"). > > When building a binary, Guix automatically sets the RPATH

Re: Packaging Jami progress

2019-12-28 Thread Jan
On Sat, 28 Dec 2019 10:40:09 +0100 Pierre Neidhardt wrote: > This is indeed your problem, I suspect that something broke the > wrapper somehow. > Can you share your patch set again? I can have a look. I didn't really break anything - it works when launching Jami normally or using the ring.cx scr

Re: [Proposal] The Formal Methods in GNU Guix Working Group

2019-12-28 Thread Vicente Eduardo
I'm interested on this topic and I will try to help as much as I can. The original idea of Brett is very interesting. In my case I would do the base compiler implemented in C and using yacc (for example) to implement the grammar. But it won't make sense in a community like Guix where most people k

Re: Packaging Jami progress

2019-12-28 Thread Pierre Neidhardt
Allow me to explain a little more: Binaries embed a value called RPATH which points to the locations where to load dynamic libraries (also called "shared objects"). When building a binary, Guix automatically sets the RPATH to that of the required inputs. Jami (indirectly) depends on both sqlit

Re: Packaging Jami progress

2019-12-28 Thread Jan Wielkiewicz
I managed to debug jami client properly, the cause of the gdb error was the "jami-gnome" file, which is acutally just a bash script, exporting the path: #!/gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash export LD_LIBRARY_PATH="/gnu/store/dha6b5g3kjqw2vfdbhv43sfnpa5d0m5v-sq