Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

2019-04-13 Thread Joerg Jaspert
On 15371 March 1977, Aurelien Jarno wrote: How is the move to debian-ports supposed to happen? I won't have the time to do anything about it within the 2 weeks. The process to inject all packages to debian-ports is to get all the deb, udeb and buildinfo files from the archives (main and

Re: guruplug doesn't boot after upgrade kernel

2019-04-13 Thread Lieven Baes
On Sat, Apr 13, 2019 at 12:13 PM Martin Michlmayr wrote: > * Ian Campbell [2019-04-13 11:07]: > > > [0.00] Kernel command line: $(bootargs_console) > earlyprintk=serial,ttyS0,115200 > > > > Looks like `$(bootargs_console)` isn't actually being substituted. Are > > you sure the `$(...)`

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

2019-04-13 Thread Philipp Kern
On 4/13/2019 12:49 PM, Aurelien Jarno wrote: > The process to inject all packages to debian-ports is to get all the > deb, udeb and buildinfo files from the archives (main and debug) and > associate them with the .changes files that are hosted on coccia. We'll > also need to fetch all the

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

2019-04-13 Thread Aurelien Jarno
On 2019-04-12 23:01, Samuel Thibault wrote: > Hello, > > Joerg Jaspert, le ven. 12 avril 2019 22:48:42 +0200, a ecrit: > > back in August 2018 we discussed architecture inclusion into > > unstable/experimental. > > > > Today we had our regular FTPMaster meeting and discussed hurd and both > >

Re: guruplug doesn't boot after upgrade kernel

2019-04-13 Thread Martin Michlmayr
* Ian Campbell [2019-04-13 11:07]: > > [0.00] Kernel command line: $(bootargs_console) > > earlyprintk=serial,ttyS0,115200 > > Looks like `$(bootargs_console)` isn't actually being substituted. Are > you sure the `$(...)` syntax is correct? Vendor u-boots sometime > deviate a bit but

Re: guruplug doesn't boot after upgrade kernel

2019-04-13 Thread Ian Campbell
On Thu, 2019-04-11 at 17:06 +0200, Lieven Baes wrote: > [0.00] Kernel command line: $(bootargs_console) > earlyprintk=serial,ttyS0,115200 Looks like `$(bootargs_console)` isn't actually being substituted. Are you sure the `$(...)` syntax is correct? Vendor u-boots sometime deviate a bit

Re: guruplug doesn't boot after upgrade kernel

2019-04-13 Thread Martin Michlmayr
* Lieven Baes [2019-04-12 10:33]: > Martin, do you need to change this on your guruplugs-webpage by adding that > console-argument? If someone can explain to me what's going on, I can update the docs if required. But your u-boot variables specify console=ttyS0,115200, so I don't know why it's