Re: Call for testing

2016-03-30 Thread Tobias Geerinckx-Rice
Hullo Ludo', On 29/03/2016, Ludovic Courtès wrote: > Tobias Geerinckx-Rice skribis: >> I spent most of my time so far reverse-engineering my machine's >> firmware to re-enable the well-hidden CPU virtualisation support >> required to even build the installer. > > Uh. What machine is this? (So

Re: Call for testing

2016-03-29 Thread Leo Famulari
On Tue, Mar 29, 2016 at 08:30:22AM +0200, Tobias Geerinckx-Rice wrote: > On 28/03/2016, Leo Famulari wrote: > > I first tried to install on a btrfs filesystem but the partition could > > not be found by its label upon rebooting. Well, the manual did warn me > > about this ;) > > I hope to send a

Re: Call for testing

2016-03-29 Thread Daniel Pimentel
I did upgrade on my computers (x86 and i386(thinkpad)) to new GuixSD version with GNOME and it works! Thanks for all :) -- Daniel Pimentel (d4n1)

Re: Call for testing

2016-03-29 Thread Ludovic Courtès
Tobias Geerinckx-Rice skribis: > On 28/03/2016, Leo Famulari wrote: >> I first tried to install on a btrfs filesystem but the partition could >> not be found by its label upon rebooting. Well, the manual did warn me >> about this ;) > > I hope to send a rough series of patches for btrfs root sup

Re: Call for testing

2016-03-28 Thread Tobias Geerinckx-Rice
On 28/03/2016, Leo Famulari wrote: > I first tried to install on a btrfs filesystem but the partition could > not be found by its label upon rebooting. Well, the manual did warn me > about this ;) I hope to send a rough series of patches for btrfs root support soon, for unknown values of soon. I

Re: Call for testing

2016-03-28 Thread Jan Nieuwenhuizen
Ludovic Courtès writes: >> - Please provide and suggest tested desktop.scm and server.scm > > Yeah, though each person has their own idea of what “server” or > “desktop” means Sure, it would help with bug reports like mine... Can you try the plain xxx.scm? >> It would be nice if an install

Re: Call for testing

2016-03-28 Thread Ludovic Courtès
Jan Nieuwenhuizen skribis: > I tried this. > > + Booting and instructions are great > - Please provide and suggest tested desktop.scm and server.scm Yeah, though each person has their own idea of what “server” or “desktop” means (to me “desktop” means ratpoison, but I’ve heard about that GNO

Re: Call for testing

2016-03-28 Thread Ludovic Courtès
Leo Famulari skribis: > I built an i686 installer against 36c2c8c8 (gnu: beets: Run tests with > python-nose.) and used that. > > Do you think the motd should suggest that the user runs `guix pull`? > It's not necessary now, but in a couple months it would be helpful. I thought we’d need a bette

Re: Call for testing

2016-03-28 Thread Leo Famulari
On Fri, Mar 25, 2016 at 11:12:35AM +0100, Ludovic Courtès wrote: > Hello! > > Please consider the following GuixSD installation image for testing, and > report any issues or successes! I built an i686 installer against 36c2c8c8 (gnu: beets: Run tests with python-nose.) and used that. Do you thin

Re: Call for testing

2016-03-27 Thread Jan Nieuwenhuizen
Ludovic Courtès writes: Hi, > Please consider the following GuixSD installation image for testing, and > report any issues or successes! > > > https://www.fdn.fr/~lcourtes/software/guix/guixsd-usb-install-0.10.0pre.x86_64-linux.xz I tried this. + Booting and instructions are great - Plea

Re: Call for testing

2016-03-25 Thread Tobias Geerinckx-Rice
Woo! On 25/03/2016, Ludovic Courtès wrote: > As you can see, due to popular demand ;-), the minor version number has > been bumped. I think it makes sense. I'll take an extra laptop along for Easter dinner... :-) Thanks to all contributors, T G-R

Re: Call for testing!

2015-11-07 Thread Ludovic Courtès
Adam Pribyl skribis: > 1) doc: I would suggest to put in the doc (on tty2) to put the > commands that should be used during installation on the separate lines > > e.g.: > " > o install the system, you would: > > Configure the network, by running ifconfig eno1 up && dhclient eno1 > " > should

Re: Call for testing!

2015-11-05 Thread Adam Pribyl
On Tue, 3 Nov 2015, Ludovic Courtès wrote: Hi! Please test the USB installation image at: http://www.fdn.fr/~lcourtes/software/guix/guixsd-usb-install-0.9.0pre.x86_64-linux.xz SHA1: 0d7f37d5b18f7b4437b447fc8a90b44c470f6e99 http://www.fdn.fr/~lcourtes/software/guix/guixsd-usb-install-0.9.0

Re: Call for testing!

2015-11-04 Thread Ludovic Courtès
宋文武 skribis: > Hi! I test this install image using qemu by: > > qemu-system-x86-64 -enable-kvm -m 512 -hda guixsd-usb-install* -hdb > disk.img > > Follow the manual to setup encryted root, using the desktop.scm > template, but > at the final step, it failed with: > > Path '/mnt/boot/grub' is

Re: Call for testing!

2015-11-03 Thread 宋文武
On 2015-11-03 22:17, l...@gnu.org wrote: Hi! Please test the USB installation image at: http://www.fdn.fr/~lcourtes/software/guix/guixsd-usb-install-0.9.0pre.x86_64-linux.xz SHA1: 0d7f37d5b18f7b4437b447fc8a90b44c470f6e99 http://www.fdn.fr/~lcourtes/software/guix/guixsd-usb-install-0.9.0pre.

Re: Call for testing : guix-tox, a version of tox that uses "guix environment".

2015-07-10 Thread Ludovic Courtès
Amirouche Boubekki skribis: > On 2015-07-10 03:38, Christopher Allan Webber wrote: [...] >>> I intend to propose a 20 minute talk about >>> guix-tox at the next PyConFR. > > Nice! \o/ >> This is great! I've also been very interested in "guix environment" as >> a universal virtualenv. Replac

Re: Call for testing : guix-tox, a version of tox that uses "guix environment".

2015-07-09 Thread Amirouche Boubekki
On 2015-07-10 03:38, Christopher Allan Webber wrote: Cyril Roelandt writes: Hey! Those of who you write Python code probably know tox[1], a tool used to manage tests/builds for Python. It uses virtualenv[2], which allows developers to create "isolated" environments and install packages witho

Re: Call for testing : guix-tox, a version of tox that uses "guix environment".

2015-07-09 Thread Christopher Allan Webber
Cyril Roelandt writes: > Hey! > > Those of who you write Python code probably know tox[1], a tool used to > manage tests/builds for Python. It uses virtualenv[2], which allows > developers to create "isolated" environments and install packages > without polluting their systems. > > I hacked tox to