On Sat, Apr 13, 2019 at 09:31:46AM +0200, Samuel Thibault wrote:
> Samuel Thibault, le sam. 13 avril 2019 00:11:15 +0200, a ecrit:
> > Joerg Jaspert, le ven. 12 avril 2019 23:30:31 +0200, a ecrit:
> > > It seems to exist there, so probably someone who can upload there and
> > > is interested in
On Fri, Oct 19, 2018 at 11:35:54AM +0200, Martin Steigerwald wrote:
> A minority? Yes. But a sizable one.
It doesn't matter how many people use it, if noone is willing to maintain
it. *If* people are maintaining it, it also doesnt matter how many people
are using it :)
*Someone* needs to do the
On Sat, Oct 13, 2018 at 06:01:43AM +0100, Ben Hutchings wrote:
> > Has policy changed regarding support for multiple inits, or is it just that
> > no one is maintaining the shim and sysvinit-core?
>
> The latter. systemd-shim has been orphaned for over 2 years, and has
> RC bugs. sysvinit
thanks to everyone explaining arch:any to me :)
--
cheers,
Holger
signature.asc
Description: Digital signature
On Sun, Jun 05, 2016 at 01:26:39PM +0200, John Paul Adrian Glaubitz wrote:
> ppc64:
>
> This architecture is basically on par with the release architectures. We have
> over
> 11.000 packages installed
[...]
> sparc64:
> We are close to 11.000 installed packages.
I'm not sure whether you are
package: www.debian.org
x-debbugs-cc: debian-hurd@lists.debian.org
Hi,
https://www.debian.org/ports/hurd/ contains the following:
"We hope to be able to release Debian GNU/Hurd for wheezy."
As you might be aware, wheezy has been released and so has jessie, so
you might want to update the text
On Freitag, 21. November 2014, Samuel Thibault wrote:
I'm fixing it by uploading a build of perl without the couple of failing
tests.
Thanks Holger and Gabriele for having worked on this, it is indeed very
useful to quickly catch installability issues.
nice! :-)
thanks for the feedback!
Hi Steven,
On Donnerstag, 13. November 2014, Steven Chamberlain wrote:
I think we're missing some data from the end of the serial.log;
probably due to some buffering, and qemu being sent SIGKILL.
Please consider this change to use SIGINT for up to 10 seconds,
then SIGKILL only if it's still
Hi,
On Freitag, 14. November 2014, Steven Chamberlain wrote:
Are you thinking of -e (exit on error)?
yes
g-i-installation.sh doesn't
seem to run in that mode, actually it ignores some failing commands
already during cleanup steps.
yes, but during cleanup +e is explicitly set, I think.
Oh,
Hi Steven,
On Freitag, 14. November 2014, Steven Chamberlain wrote:
Aha yes it does set +e inside that function. But code before and
after it does ignore + have to handle fatal errors itself.
The code I added shouldn't return false, except maybe a race between
'ps' and 'kill' (if the
Hi Steven,
On Freitag, 14. November 2014, Steven Chamberlain wrote:
After I started at the error message long enough, it finally hit me,
and it's kind of amusing. If you could please fix my silly mistake:
hehe, I know that feeling... :-)
merged + triggered etc.. - thanks!
cheers,
On Freitag, 14. November 2014, Steven Chamberlain wrote:
Firstly could someone please tell me what display manager this is?
https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debia
n_sid_daily_hurd_lxde/70/artifact/results//snapshot_008244.png
xdm
signature.asc
Hi,
On Samstag, 15. November 2014, Samuel Thibault wrote:
See the preseed file: we force the use of xdm, I guess because lightdm
doesn't work yet.
do git blame on that line, it's an ancient choice... probably better now to
not force any specific dm and just choose a de.
Holger
Hi,
On Mittwoch, 12. November 2014, Samuel Thibault wrote:
Maybe hurd also could redirect syslog there to help debug the issue
you're seeing.
Indeed.
actually, all installs can probably benefit from this :)
There is: console=com0, it'd only redirect the kernel messages though
(which can
Hi,
On Mittwoch, 12. November 2014, Steven Chamberlain wrote:
Holger Levsen wrote:
in the video there is no IP address to be seen. em0 gets a link, but
thats all.
Later 'network autoconfiguration succeeded', so DHCP probably worked;
the IP address isn't usually mentioned within the GUI
Hi,
https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_sid_daily_kfreebsd/432/artifact/results/serial.log
is there now and it shows how the right IP is received. I don't understand why
getting the preseed file then fails...
cheers,
Holger
signature.asc
Hi,
On Mittwoch, 23. Oktober 2013, Stewart Smith wrote:
Jenkins can have slaves on remote hosts, via SSH. It runs a small java
app there, so as long as the arch has a JVM then you're pretty right.
that JVM is not even needed, just schedule jobs via ssh and be done.
cheers,
Holger
Hi,
On Montag, 4. Juni 2012, Svante Signell wrote:
One issue is how to encourage more people trying Hurd out, when it is
not in testing.
I honestly don't think that's the main blocker trying out hurd. Lack of SATA,
and USB support are the blocker, I think. And probably also missing meaningful
On Montag, 4. Juni 2012, Svante Signell wrote:
Do you mean gnome3 and KDE4/5 here, or maybe DRM?
DRM
No, this time the work is based on the DDE framework, recently
successfully implemented for network drivers. Ask Samuel Thibault for
more details if interested, he is the person in charge.
Hi Samuel,
On Samstag, 19. Mai 2012, Samuel Thibault wrote:
Concerning hardware support, Linux 2.6.32 network drivers are now
included and will be used by default in the coming days. That provides
a fairly good coverage of not too-new hardware. We are working on
integrating the linux
20 matches
Mail list logo