Re: core-updates summer 2017

2017-07-12 Thread Leo Famulari
On Wed, Jul 12, 2017 at 08:22:37PM -0400, Leo Famulari wrote:
> On Mon, Jul 10, 2017 at 04:47:06PM -0400, Leo Famulari wrote:
> > Let's use this thread to discuss the state of the branch.
> 
> I've reconfigured and rebooted my x86_64-linux GuixSD system based on
> the latest core-updates (2f0d1b9dd2d75c5501767a15cf9b87fc057711c0).

I've also used `guix pull` to update my users's Guix installation to
core-updates, and updated my user's packages. So far, so good.

I haven't tested a graphical installation. Somebody who uses a GuixSD
desktop should try this once Hydra has built more packages (tomorrow?).


signature.asc
Description: PGP signature


Re: Substitute caching restored

2017-07-12 Thread Leo Famulari
On Wed, Jul 12, 2017 at 10:47:29PM +0200, Ludovic Courtès wrote:
> Hello Guix!
> 
> Tired of updating the list of substitutes?  I have some good news for
> you!
> 
> Since the switch to Guile 2.2.2, because of a bug (an otherwise known
> bug) in SRFI-19, ‘guix substitute’ would be storing the wrong date in
> cached narinfos in /var/guix/substitute/cache.  Consequently, we’d be
> updating most narinfos as soon as we had cached them!
> 
> Commit b547349d505c57fd679b6e48c472d8ab65469c96 fixes that and
> c96ed00910d9238a43469e5f00a8261253294257 updates the ‘guix’ package.

Ah, thank you for finding and fixing this!


signature.asc
Description: PGP signature


Re: ISO-9660 image working and ready

2017-07-12 Thread Danny Milosavljevic
Hi Ludo,

On Wed, 12 Jul 2017 23:20:26 +0200
l...@gnu.org (Ludovic Courtès) wrote:

> > It will work from CD and USB flash drive - that should cover all the 
> > options.  
> 
> Are you saying that the same image could be either dd’d to a USB key or
> burnt on an actual CD?

Yes.

> Are there any downsides to using ISO9660 as the file system for the
> media, like limitations on file names or file name lengths, restrictions
> on the type of files, etc.?  (That doesn’t seem to be the case, but I
> vaguely remember ISO9660 as having annoying limitations.)

It uses the Rock Ridge extension.  That means basenames are limited to 255 
characters at most, allowed are all characters except NUL and "/".

>   ./pre-inst-env guix system disk-image -t iso9660 gnu/system/install.scm
> 
> on v0.13.0-1321-gc96ed0091 (current master), booted it with QEMU,
> worked fine with ‘lsblk’ showing only /dev/{fd0,sr0}.   Woohoo!  \o/

Now try qemu ...  -hda thesamefile.iso :)

> The image has this 2KiB /boot.catalog file; is that expected?

Yeah, that's the El Torito specification for the first-stage bootloader.  It 
contains what system architectures are supported and what kind of weird boot 
emulation the BIOS is supposed to use (look like a floppy drive, look like a 
hard drive, just be yourself etc).

> Otherwise the file names look alright as if Joliet extensions were used,
> but maybe they are?

Rock Ridge :)

UNIX permissions work, too.

>  “guix gc --verify=contents” in the image is happy
> (and surprisingly fast).

> Anyway awesome work, and a great milestone.  Many users who had been
> complaining about the lack of ISOs will thank you!  :-)

Thanks for your help :)



Gexp news

2017-07-12 Thread Ludovic Courtès
Hello Guix!

Last week I fiddled with gexps:

  • I rebased ‘wip-build-systems-gexp’ on ‘core-updates’ and
improved/optimized a bunch of things.  It’s now close to ‘master’
performance-wise, which was the main blocker for this branch.
Hopefully I’ll look into it again next week or so.

There’s more work to do, such as adapting some of the newer build
systems, but the goal is to make it our next ‘core-updates’.

  • The ‘wip-gexp-hygiene’ branch makes gexps “hygienic”—i.e., gexps
cannot capture lexically-bound identifiers introduced by other
gexps, as in:

  (let* ((inner (lambda (x)
  #~(let ((x 40)) (+ x #$x
 (outer  #~(let ((x 2))
 #$(inner #~x
(primitive-eval (gexp->sexp* outer)))

This returns 42 because the ‘x’ in ‘inner’ does not shadow the ‘x’
in ‘outer’ (and neither shadows the ‘x’ that is the formal parameter
of ‘inner’.)  In current ‘master’ it returns 80.

It does so through a custom alpha-renaming phase inspired by
Kiselyov’s MetaScheme¹, similar to but much simpler than what the
macro expander does.  That needs a bit more testing, but I think we
can make probably try and add it on top of the above branch.

Feedback welcome!

Ludo’.

¹ http://okmij.org/ftp/meta-programming/#meta-scheme



Re: ISO-9660 image working and ready

2017-07-12 Thread Ludovic Courtès
Hey hey!

(This is a followup to .)

Danny Milosavljevic  skribis:

> If we want we can (in the future) provide only the iso9660 image on the 
> homepage (for x86_64).
>
> It will work from CD and USB flash drive - that should cover all the options.

Are you saying that the same image could be either dd’d to a USB key or
burnt on an actual CD?

Are there any downsides to using ISO9660 as the file system for the
media, like limitations on file names or file name lengths, restrictions
on the type of files, etc.?  (That doesn’t seem to be the case, but I
vaguely remember ISO9660 as having annoying limitations.)

> (Usually, ARM systems have a more involved boot process and will not work, 
> neither from SD card nor from CD-ROM - and booting from USB flash drive is 
> out of the question).
>
> Of course it would be nice if people could test the iso9660 image a bit 
> (especially on UEFI systems of which I have none).
>
> To generate one, for example do this:
>
> guix system disk-image -t iso9660 foo.scm # will print the name of the 
> directory that contains "guixsd.iso" in the end.

I’ve just built:

  ./pre-inst-env guix system disk-image -t iso9660 gnu/system/install.scm

on v0.13.0-1321-gc96ed0091 (current master), booted it with QEMU,
worked fine with ‘lsblk’ showing only /dev/{fd0,sr0}.   Woohoo!  \o/

The image has this 2KiB /boot.catalog file; is that expected?

Otherwise the file names look alright as if Joliet extensions were used,
but maybe they are?  “guix gc --verify=contents” in the image is happy
(and surprisingly fast).

Anyway awesome work, and a great milestone.  Many users who had been
complaining about the lack of ISOs will thank you!  :-)

Ludo’.



Substitute caching restored

2017-07-12 Thread Ludovic Courtès
Hello Guix!

Tired of updating the list of substitutes?  I have some good news for
you!

Since the switch to Guile 2.2.2, because of a bug (an otherwise known
bug) in SRFI-19, ‘guix substitute’ would be storing the wrong date in
cached narinfos in /var/guix/substitute/cache.  Consequently, we’d be
updating most narinfos as soon as we had cached them!

Commit b547349d505c57fd679b6e48c472d8ab65469c96 fixes that and
c96ed00910d9238a43469e5f00a8261253294257 updates the ‘guix’ package.

If you’re on GuixSD, ‘guix system reconfigure’ will give you the fix.
If you’re on a foreign distro and you used the binary installation
method, run “guix pull && guix package -u guix” as root.

Ludo’.

PS: No that doesn’t solve , so we’re still
updating the list of substitutes more than we’d like…



Automatically detect other OSs and generate grub entries

2017-07-12 Thread Arun Isaac

Instead of having to manually specify custom grub entries in config.scm,
can Guix use os-prober to automatically detect other operating system
and generate grub entries?

https://joeyh.name/code/os-prober/



Re: Graphical Installer - Call for Testing.

2017-07-12 Thread Danny Milosavljevic
> Also, what do you think of us providing a "guix system" command for this?

guix system disk-image -t iso9660 gnu/system/install.scm

Adapted for my purposes, from the manual :)



Re: self hosting hardware

2017-07-12 Thread Vincent Legoll
Hello,

On Wed, Jul 12, 2017 at 4:37 PM, Solène Rapenne  wrote:
> Je 2017-07-12 14:40, Pjotr Prins skribis:
>>
>> You should also take a look at ARM, such as Gigabyte MP30-AR1
>
> I wasn't aware of the availability of this hardware.

Is this still really available ? My 5 secs search found it looks out of stock.

I remember having seen some discussions on debian-arm ML with reports
of problematic firmware/BIOS...



Here it is:
https://lists.debian.org/debian-arm/2016/09/msg00022.html

> But it's pretty expensive, the motherboard with SoC processor costs ~450€.

No, that's cheap, really, have a look at that one:
https://www.crowdsupply.com/raptor-computing-systems/talos-secure-workstation

Tchuss

-- 
Vincent Legoll



Re: self hosting hardware

2017-07-12 Thread Solène Rapenne

Je 2017-07-12 14:40, Pjotr Prins skribis:

You should also take a look at ARM, such as Gigabyte MP30-AR1


I wasn't aware of the availability of this hardware.
But it's pretty expensive, the motherboard with SoC processor costs 
~450€.




Re: self hosting hardware

2017-07-12 Thread Ricardo Wurmus

Catonano  writes:

> Let's say I just want statiic web sites, a mail server and an IRC bouncher
>
> That is: let's talk about hardware. That's where I need help

I’m using a Samsung N148 netbook for elephly.net.  I don’t run a mail
server, but I use it for XMPP, IRC bouncer, static web sites, git
server, Tor, etc.

It’s small (thinner than my router), cheap (if you can still get it),
and it has an Intel Atom CPU, so it doesn’t consume much.  It’s i686
with limited RAM, so at the moment it’s barely enough to compile Guix,
but I hope we can fix this before the next release will be out.

The hardware works fine with GuixSD, as far as I can tell.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net




Re: RPC pipelining

2017-07-12 Thread Ricardo Wurmus

> Why does Guix need Shepherd?  And if it needs the (charting)
> module, why isn't guile-charting already an input?

Guile Charting is optional.  The error is misleadingly alarming.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net




Re: self hosting hardware

2017-07-12 Thread Pjotr Prins
You should also take a look at ARM, such as Gigabyte MP30-AR1




Re: self hosting hardware

2017-07-12 Thread Solène Rapenne

Je 2017-07-12 09:19, Catonano skribis:

In the next autumn/winter I would like to try to set up a self hosting 
solution


And I'd love it to be GuixSD based

I need some help with selecting the hardware that fits the goal
Hardware is not exactly my thing

A Beaglebone board (or equivalent) ? An Intel NUC (or equivalent) ?

It should probably serve a collection of static files over https, have 
a smtp server and an IRC bouncher.


Optionally I'd like it to run some bittorrent or rsync or synchthing or 
ipfs or DAT and a Gnunet node.


I'd love to be able to attach some external hard drives to it, both 
traditionl hard drives and SSDs.


In the last few years the ADSL that serves my apartment has improved 
dramatically


It used to be 300 Kb/s in upload for years

Now it's around 19 Mb/s

The optic fiber cord reached the cabinet just aside the building main 
entrance


The copper fragment is now only a few meters.

So I could use some hardware suggestions to set up such a solution 
based on GuixSD


It has to be cheap AND moderate in electricity consumption, possibly 
like a home router (or something)


Thanks for any hint


Hello,

if you have some space and you are not afraid by noise, I would go for a 
homemade computer.
That would allow you to add network cards if you need and lot of hard 
drives.


If you go for a NUC or a mini-itx computer, that will not allow you to 
upgrade, and you may be limited to

1x 2.5" disk + 1x SSD in m3 format.

You just need :

- a processor (pentium/celeron, cheap and works well, and won't consume 
much)

- hard drive
- motherboard (you can by a cheap motherboard, look at the number of 
SATA ports)

- case (cheapest possible)
- power supply (buy a good one but not with a lot of power, 80+ 
standards can help to choose)

- 2x memory (2/4/8 Gb as you want)



Re: Graphical Installer - Call for Testing.

2017-07-12 Thread Danny Milosavljevic
Hi Ludo,

> Yes.  At the REPL, you can do:
> 
>   ,use(guix)
>   ,run-in-store (system-disk-image installation-os)

I tried:

,use (gnu system vm)
,use (gnu system install)
,use (guix)
,run-in-store (system-disk-image installation-os)
(derivation->output-path $3)

and get

$3 = # 
/gnu/store/pjrkpnz4bgpiqgdix8ldz0psp53zr4kr-disk-image b0bbe60>
$5 = "/gnu/store/pjrkpnz4bgpiqgdix8ldz0psp53zr4kr-disk-image"

But /gnu/store/pjrkpnz4bgpiqgdix8ldz0psp53zr4kr-disk-image doesn't exist yet.

What should I do to make guix build the image?

Also, what do you think of us providing a "guix system" command for this?

It's kinda difficult to use otherwise...



Re: self hosting hardware

2017-07-12 Thread Catonano
2017-07-12 11:06 GMT+02:00 Solène Rapenne :

> Je 2017-07-12 09:19, Catonano skribis:
>
>
> In the next autumn/winter I would like to try to set up a self hosting
>> solution
>>
>> And I'd love it to be GuixSD based
>>
>> I need some help with selecting the hardware that fits the goal
>> Hardware is not exactly my thing
>>
>> A Beaglebone board (or equivalent) ? An Intel NUC (or equivalent) ?
>>
>> It should probably serve a collection of static files over https, have a
>> smtp server and an IRC bouncher.
>>
>> Optionally I'd like it to run some bittorrent or rsync or synchthing or
>> ipfs or DAT and a Gnunet node.
>>
>> I'd love to be able to attach some external hard drives to it, both
>> traditionl hard drives and SSDs.
>>
>> In the last few years the ADSL that serves my apartment has improved
>> dramatically
>>
>> It used to be 300 Kb/s in upload for years
>>
>> Now it's around 19 Mb/s
>>
>> The optic fiber cord reached the cabinet just aside the building main
>> entrance
>>
>> The copper fragment is now only a few meters.
>>
>> So I could use some hardware suggestions to set up such a solution based
>> on GuixSD
>>
>> It has to be cheap AND moderate in electricity consumption, possibly like
>> a home router (or something)
>>
>> Thanks for any hint
>>
>
> Hello,
>
> if you have some space and you are not afraid by noise, I would go for a
> homemade computer.
> That would allow you to add network cards if you need and lot of hard
> drives.
>
> If you go for a NUC or a mini-itx computer, that will not allow you to
> upgrade, and you may be limited to
> 1x 2.5" disk + 1x SSD in m3 format.
>
> You just need :
>
> - a processor (pentium/celeron, cheap and works well, and won't consume
> much)
> - hard drive
> - motherboard (you can by a cheap motherboard, look at the number of SATA
> ports)
> - case (cheapest possible)
> - power supply (buy a good one but not with a lot of power, 80+ standards
> can help to choose)
> - 2x memory (2/4/8 Gb as you want)
>


Ok, no exotic hardware

Thanks, Solène !


Re: RPC pipelining

2017-07-12 Thread Roel Janssen

Ludovic Courtès writes:

> Hi Roel,
>
> Roel Janssen  skribis:
>
>> substitute: guix substitute: warning: ACL for archive imports seems to be 
>> uninitialized, substitutes may be unavailable
>> substitute: ;;; Failed to autoload make-session in (gnutls):
>> substitute: ;;; ERROR: missing interface for module (gnutls)
>> substitute: Backtrace:
>> substitute:1 (primitive-load 
>> "/gnu/repositories/guix/scripts/guix")
>> substitute: In guix/ui.scm:
>> substitute:   1352:12  0 (run-guix-command _ . _)
>> substitute: 
>> substitute: guix/ui.scm:1352:12: In procedure run-guix-command:
>> substitute: guix/ui.scm:1352:12: In procedure module-lookup: Unbound 
>> variable: make-session
>> guix environment: error: build failed: writing to file: Broken pipe
>
> This is because ‘guix substitute’, called by ‘guix-daemon’, doesn’t find
> (gnutls) in its GUILE_LOAD_PATH.
>
> Use either “sudo -E ./pre-inst-env guix-daemon …” so that guix-daemon
> inherits GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH, or
> --no-substitutes.
>
> Thanks for testing!
>
> Ludo’.

Thanks for the pointer.  I think it was a bad idea to try it with the
pre-inst-env, because before it even got to this point I had to modify
the location of guile in the header of scripts/guix.

So, maybe I shouldn't be using the pre-inst-env at all and just
properly install the patched version.  I can always --roll-back anyway.

So I applied the patch, and ran:
make dist

Which produced a tarball.
I then modified the guix recipe to use the tarball instead of a git
checkout.  But unfortunately, building it is again troublesome:

...
  GUILEC   guix/scripts/import/gem.go
  GUILEC   guix/scripts/import/pypi.go
  GUILEC   guix/scripts/import/stackage.go
  GUILEC   guix/ssh.go
  GUILEC   guix/scripts/copy.go
  GUILEC   guix/store/ssh.go
  GUILEC   guix/scripts/offload.go
  GUILEC   guix/config.go
  GUILEC   guix/tests.go
  GUILEC   guix/tests/http.go
;;; Failed to autoload make-page-map in (charting):
;;; ERROR: missing interface for module (charting)
;;; Failed to autoload make-page-map in (charting):
;;; ERROR: missing interface for module (charting)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload exec-command in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
random seed for tests: 1499856249
;;; Failed to autoload make-page-map in (charting):
;;; ERROR: missing interface for module (charting)
;;; Failed to autoload make-page-map in (charting):
;;; ERROR: missing interface for module (charting)
;;; Failed to autoload make-page-map in (charting):
;;; ERROR: missing interface for module (charting)
guix/scripts/size.scm:211:2: warning: possibly unbound variable `make-page-map'
;;; Failed to autoload make-page-map in (charting):
;;; ERROR: missing interface for module (charting)
;;; Failed to autoload make-page-map in (charting):
;;; ERROR: missing interface for module (charting)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload exec-command in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload exec-command in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
gnu/build/shepherd.scm:98:13: warning: possibly unbound variable `read-pid-file'
gnu/build/shepherd.scm:159:32: warning: possibly unbound variable `exec-command'
gnu/build/shepherd.scm:170:14: warning: possibly unbound variable 
`read-pid-file'
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload exec-command in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload exec-command in (shepherd service):
;;; ERROR: missing interface for module (shepherd service)
;;; Failed to autoload read-pid-file in (shepherd service):
;;; ERROR: 

Re: cuirass evaluate

2017-07-12 Thread Mathieu Othacehe

Hi Ludo,

A cuirass question :

In src/cuirass/base.scm, you wrote the following comment :

--8<---cut here---start->8---
  ;; Register the results in the database.
  ;; XXX: The 'build-derivations' call is blocking so we end updating the
  ;; database potentially long after things have been built.
--8<---cut here---end--->8---

How would it be possible to be notified when a build succeeds, to update
the database asap ?

Thanks,

Mathieu



Re: self hosting hardware

2017-07-12 Thread Catonano
2017-07-12 10:03 GMT+02:00 ng0 :

> Catonano transcribed 0.4K bytes:
> > I forgot: I might want to run a Mastodon (or GNU Social) instance and a
> > Mediagoblin instance
>
> As you've noticed yourself when we had that conversation, GNU Social
> would be easier to get into Guix native than Mastodon.
>

Sorry, I didn't remember we already had this conversation


>
> While I was working on it (or occasionally do) I wonder why we have so
> little rails packages? What happened there?
>

Because I understand the woes of missing packages, I'd say: let's keep it
basic

Let's say I just want statiic web sites, a mail server and an IRC bouncher

That is: let's talk about hardware. That's where I need help

I get lost in the sea of boards and mini/micro servers
I don't know much abot architectures and their support in Guix


Re: Rails

2017-07-12 Thread ng0
Pjotr Prins transcribed 0.4K bytes:
> On Wed, Jul 12, 2017 at 08:03:48AM +, ng0 wrote:
> > While I was working on it (or occasionally do) I wonder why we have so
> > little rails packages? What happened there?
> 
> Ruby support is great in Guix. But we don't use Rails much, yet. Dave
> started packaging some time back, but not sure what happened. We also
> need it for Arvados - Fred is working on that.
> 
> Pj.
> 
> 
Ah! Good to know. I have some packages in a dirty branch, I just need to
figure out the right order. at the moment it's just one file and the top
view are about 40 rails packages I guess. I'm not sure how many will be
added in layers below.
Some already exist in Guix, but this is the list of gems I need:

gem ‘pkg-config’
gem ‘rails’, ‘~> 5.0.2’
gem ‘sass-rails’, ‘~> 5.0’
gem ‘uglifier’, ‘>= 1.3.0’
gem ‘jquery-rails’
gem ‘puma’
gem ‘hamlit-rails’
gem ‘pg’
gem ‘pghero’
gem ‘dotenv-rails’
gem ‘font-awesome-rails’
gem ‘best_in_place’, ‘~> 3.0.1’
gem ‘paperclip’, ‘~> 5.1’
gem ‘paperclip-av-transcoder’
gem ‘aws-sdk’, ‘>= 2.0’
gem ‘addressable’
gem ‘devise’
gem ‘devise-two-factor’
gem ‘doorkeeper’
gem ‘fast_blank’
gem ‘goldfinger’
gem ‘hiredis’
gem ‘htmlentities’
gem ‘http’
gem ‘http_accept_language’
gem ‘httplog’
gem ‘kaminari’
gem ‘link_header’
gem ‘nokogiri’
gem ‘oj’
gem ‘ostatus2’, ‘~> 1.1’
gem ‘ox’
gem ‘rabl’
gem ‘rack-attack’
gem ‘rack-cors’, require: ‘rack/cors’
gem ‘rack-timeout’
gem ‘rails-i18n’
gem ‘rails-settings-cached’
gem ‘redis’, ‘~>3.2’, require: [‘redis’, ‘redis/connection/hiredis’]
gem ‘rqrcode’
gem ‘ruby-oembed’, require: ‘oembed’
gem ‘sidekiq’
gem ‘sidekiq-unique-jobs’
gem ‘simple-navigation’
gem ‘simple_form’
gem ‘sprockets-rails’, :require => ‘sprockets/railtie’
gem ‘statsd-instrument’
gem ‘twitter-text’
gem ‘tzinfo-data’
gem ‘whatlanguage’
gem ‘react-rails’
gem ‘browserify-rails’
gem ‘autoprefixer-rails’
gem ‘rails_12factor’
gem ‘redis-rails’
gem ‘lograge’

The work will probably be an exercise in futility as the software
(Mastodon) will not be included in Guix as it requires a binary blob
with all the Nodejs packages, unless some of the people working on
nodejs has an epiphany or nodejs decides to become more accessible,
or hell freezes over, whatever happens first.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org


signature.asc
Description: PGP signature


Rails

2017-07-12 Thread Pjotr Prins
On Wed, Jul 12, 2017 at 08:03:48AM +, ng0 wrote:
> While I was working on it (or occasionally do) I wonder why we have so
> little rails packages? What happened there?

Ruby support is great in Guix. But we don't use Rails much, yet. Dave
started packaging some time back, but not sure what happened. We also
need it for Arvados - Fred is working on that.

Pj.



Re: self hosting hardware

2017-07-12 Thread ng0
Catonano transcribed 0.4K bytes:
> I forgot: I might want to run a Mastodon (or GNU Social) instance and a
> Mediagoblin instance

As you've noticed yourself when we had that conversation, GNU Social
would be easier to get into Guix native than Mastodon.

While I was working on it (or occasionally do) I wonder why we have so
little rails packages? What happened there?
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org


signature.asc
Description: PGP signature


Re: self hosting hardware

2017-07-12 Thread Catonano
I forgot: I might want to run a Mastodon (or GNU Social) instance and a
Mediagoblin instance


self hosting hardware

2017-07-12 Thread Catonano
In the next autumn/winter I would like to try to set up a self hosting
solution

And I'd love it to be GuixSD based

I need some help with selecting the hardware that fits the goal
Hardware is not exactly my thing

A Beaglebone board (or equivalent) ? An Intel NUC (or equivalent) ?

It should probably serve a collection of static files over https, have a
smtp server and an IRC bouncher.

Optionally I'd like it to run some bittorrent or rsync or synchthing or
ipfs or DAT and a Gnunet node.

I'd love to be able to attach some external hard drives to it, both
traditionl hard drives and SSDs.

In the last few years the ADSL that serves my apartment has improved
dramatically

It used to be 300 Kb/s in upload for years

Now it's around 19 Mb/s

The optic fiber cord reached the cabinet just aside the building main
entrance

The copper fragment is now only a few meters.

So I could use some hardware suggestions to set up such a solution based on
GuixSD

It has to be cheap AND moderate in electricity consumption, possibly like a
home router (or something)

Thanks for any hint


Re: core-updates summer 2017

2017-07-12 Thread Leo Famulari
On Mon, Jul 10, 2017 at 08:13:08PM -0400, Kei Kebreau wrote:
> Leo Famulari  writes:
> 
> > I just started a new evaluation of core-updates and am reconfiguring my
> > GuixSD system based on it.
> >
> > Let's use this thread to discuss the state of the branch.
> 
> Would this be the time to enable the ACL tests as previously discussed?

Hydra is building now. Let's see if we need to make more changes that
will cause lots of rebuilds. If so, we'll enable the ACL tests.
Otherwise, let's wait for the next one. Technically we are still in the
same cycle but I think a lot of us took a break in the middle of it.
Since it was still the "same one", I forgot to look at
core-updates-next.


signature.asc
Description: PGP signature


Re: core-updates summer 2017

2017-07-12 Thread Leo Famulari
On Mon, Jul 10, 2017 at 04:47:06PM -0400, Leo Famulari wrote:
> I just started a new evaluation of core-updates and am reconfiguring my
> GuixSD system based on it.
> 
> Let's use this thread to discuss the state of the branch.

The test suite of glib on x86_64-linux appeared to time out, so I
restarted it:

https://hydra.gnu.org/build/2178024


signature.asc
Description: PGP signature