bug#30589: serial login not working

On 02/23/2018 at 21:19 George myglc2 Clemmer writes: > The recent move of agetty-service into #base-services caused serial > login to stop working here. I can confirm that reverting ... 7e0a6fac0 * services: mingetty: Move tty optionality to agetty. 5a9902c8a * services: agetty: Add agetty

bug#30644: Cuirass runs out of build users

Oops, I had an old bin/evaluate . bin/evaluate.in doesn't contain it anymore. My bad... So please disregard. Anyway, sqlite contains some cool stuff to find out who's locking it. But as things are it seems that sqlite access is now done only by one thread. How can it then be locked?

bug#30644: Cuirass runs out of build users

As for what's causing this, cuirass's bin/evaluate seems to connect to the sqlite database and then write stuff into it. If a query is being done by the http server at the same time, you are going to be really careful with the sqlite open mode. There would be ways to still be able to do this,

bug#30644: Cuirass runs out of build users

Hi Ludo, > > 69:18 2 (%sqlite-exec _ _ . _) > > In ice-9/eval.scm: > >293:34 1 (_ #(#(# #< ?))) > > 619:8 0 (_ #(#(#(#(# #) #) 5) 5)) > > ice-9/eval.scm:619:8: Throw to key `sqlite-error' with args `(#f 5 > > "database is locked")'. > > Bah. :-/ sqlite3.h

bug#30644: Cuirass runs out of build users

Andreas Enge skribis: > Right now, I do not seem to be running out of build users, but I think > that cuirass nevertheless behaves strangely; so I am asking here instead > of opening a new bug (maybe there is no bug, actually). Good. :-) > There is still one occurrence of

bug#30580: request for improvement - web site - packages list - letter selection menu on top

On 01/03/18 08:41, Ludovic Courtès wrote: Hi David, David Pirotte skribis: I think it would be nice to also offer the letter selection menu on top of each package list page on the web site... Yes, you’re not the first person asking this. WDYT, sirgazil? I agree it

bug#30710: guix graph gives duplicate nodes

Hello, Hartmut Goebel skribis: >> This is expected. Strictly speaking, we’re talking about two different >> package objects, hence the different IDs. > > I wonder > > a) whether it is useful to have different graph nodes for the same package. > > This is about