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,
Holger Levsen wrote:
On Donnerstag, 13. November 2014, Steven Chamberlain wrote:
Please consider this change to use SIGINT for up to 10 seconds,
then SIGKILL only if it's still running after that:
Holger Levsen wrote:
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.
Aha yes it does set +e inside that function. But code before and
after it does ignore
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 Holger,
Holger Levsen wrote:
I don't understand why getting the preseed file then fails...
https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_sid_daily_kfreebsd/433/screenshot/full
After I started at the error message long enough, it finally hit me,
and it's kind of
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,
Hi Holger,
I think I must have broken it:
https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_sid_daily_kfreebsd/433/console
device-mapper: remove ioctl on failed: Device or resource busy
Unable to deactivate jenkins01-debian_sid_daily_kfreebsd (253:2)
Unable to
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,
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
Holger Levsen wrote:
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...
I think we're missing some
Sorry for asking,
I have a kfreebsd image in qemu, currently not running (being a little
lazy). Do kfreebsd use eudev/udev, or something else for creating
devices?
Thanks!
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
failed with:
+ sudo qemu-system-x86_64 -display vnc=localhost:1 -enable-kvm -cpu host -
cdrom /var/lib/jenkins/jobs/g-i-
installation_debian_sid_daily_kfreebsd/workspace/debian-testing-kfreebsd-
amd64-netinst.iso -boot d -drive
Hi Steven,
I've merged your patches now and pushed and deployed them and just triggered
https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_kfreebsd/429/
- I'm curious how it goes :-)
(forgot to press send on this one... sorry for the noise)
cheers,
Holger
Hi Steven,
On Mittwoch, 12. November 2014, Steven Chamberlain wrote:
Thanks for committing, and the test-run; I can see much better now how
it's supposed to work.
yay! https://jenkins.debian.net/view/g-i-installation/job/g-i-
installation_debian_sid_daily_kfreebsd/431/screenshot/ also looks
Hi,
https://jenkins.debian.net/view/g-i-installation/job/g-i-
installation_debian_sid_daily_kfreebsd/431/screenshot/ fails again, because it
cannot download the preseed file, despite it's there. At first I thought
QEMU_NET_OPTS is probably not set, but it is, so hmmm. Maybe the video will
give
Holger Levsen wrote:
yay! https://jenkins.debian.net/view/g-i-installation/job/g-i-
installation_debian_sid_daily_kfreebsd/431/screenshot/ also looks much better
now :-))
It's alive!
merged them all and then fixed a trivial syntax error you introduced :)
Sorry! Future idea would be to
Hi,
On Mittwoch, 12. November 2014, Steven Chamberlain wrote:
Sorry!
np, really...
Future idea would be to split out some functions so that I
can at least dry-run them from a basic shell without Jenkins...
I'll shortly replace g-i-i.sh with something based on libvirt-cucumber+sakuli,
so
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 installer, but
the d-i syslog will probably explain what the problem
Steven Chamberlain, le Wed 12 Nov 2014 19:26:14 +, a écrit :
Maybe hurd also could redirect syslog there to help debug the issue
you're seeing.
Indeed.
Unless there's a convenient kernel parameter to send console messages
there,
There is: console=com0, it'd only redirect the kernel
Hi!
On Mon, 10 Nov 2014, Steven Chamberlain wrote:
Among users and potential contributors, what sounds good? On a scale
of 0 (= no interest) through 9 (= would like to have / help with):
[ ] trying to support it like a stable release alongside Debian jessie
I think having a jessie
Hi.
[ ] trying to support it like a stable release alongside Debian jessie
See also announce for unofficial (linux-)amd64 sarge release.
https://lists.debian.org/debian-devel-announce/2005/06/msg5.html
The benefit might be to have security support for non altered packages, etc.
I
On Tue, Nov 11, 2014 at 01:30:16 +, Steven Chamberlain wrote:
I've had opinions for a while that Debian freeze policy has some flaws,
concerning not just kfreebsd but the rest of the distro. An unfortunate
consequence of having a fixed freeze date, is that many big changes
are rushed in
On 10/11/14 at 23:01 +, Steven Chamberlain wrote:
I guess snapshots.d.o would still have copies of the last packages that
were _in_ testing?
Yes
But won't have the indices _for_ testing.
It has them as well. See e.g.
On 10/11/14 at 22:09 +, Steven Chamberlain wrote:
Petr Salinger wrote:
Jonathan Wiltshire wrote:
[...] though we do hope that the
porters will be able to make a simultaneous unofficial release.
It is unclear, what we have to duplicate. Do we stay in testing ?
I'd like to know
Hi,
Among users and potential contributors, what sounds good? On a scale
of 0 (= no interest) through 9 (= would like to have / help with):
[9] making any kind of unofficial kfreebsd release at all
[7] trying to support it like a stable release alongside Debian jessie
[5] trying to
Hi,
Peter Palfrader wrote:
I think having a jessie kfreebsd release is a prerequisite for keeping
the debian.org machine resources (buildds, porterboxes).
The buildds and porterboxes serve unstable. Removing it from there
would be even more devastating than being dropped from the official
Hi!
Steven Chamberlain ste...@pyro.eu.org writes:
DSA can't
maintain rolling releases or testing systems for any length of time.
I'm not quite sure what you mean; particularly how those involve DSA.
What systems would you need to maintain besides the buildds for sid?
It means we need a
Lucas Nussbaum wrote:
[...] if that's helpful, Debian funds could be allocated to
that effect. (Note that, concretely, I don't really see how Debian funds
could help here; but you might have more ideas)
Thanks Lucas; I think there are places where Debian funds or resources
could be useful -
Christoph Egger wrote:
It means we need a stable release of some sort to keep DSA provided
hardware. That's currently buildds and porterboxes.
That's annoying.
To provide stable/security support ourselves, it seemed we'd need an
unofficial repo, and that doesn't sound like something DSA could
Hi!
Steven Chamberlain ste...@pyro.eu.org writes:
Christoph Egger wrote:
It means we need a stable release of some sort to keep DSA provided
hardware. That's currently buildds and porterboxes.
That's annoying.
To provide stable/security support ourselves, it seemed we'd need an
unofficial
Steven Chamberlain, le Tue 11 Nov 2014 12:05:06 +, a écrit :
Although, how is that handled for hurd-i386? I assume it has no
security support, there may be some unofficial packages used; are
therefore none of their machines DSA?
We are still stuck in the not released arch = no DSA
On Tue, 11 Nov 2014, Samuel Thibault wrote:
Steven Chamberlain, le Tue 11 Nov 2014 12:05:06 +, a écrit :
Although, how is that handled for hurd-i386? I assume it has no
security support, there may be some unofficial packages used; are
therefore none of their machines DSA?
We are
Christoph Egger wrote:
weasel christoph: the ftp-folks wouldn't mind having a jessie-kfreebsd
suite in the main archive.
With our own acceptance policy I guess (like backports has different
people accepting and stuff) and DSA would sure be willing to use
that.
Oooh that does actually
On Tue, 11 Nov 2014, Steven Chamberlain wrote:
Lucas Nussbaum wrote:
[...] if that's helpful, Debian funds could be allocated to
that effect. (Note that, concretely, I don't really see how Debian funds
could help here; but you might have more ideas)
Thanks Lucas; I think there are
Peter Palfrader, le Tue 11 Nov 2014 13:39:02 +0100, a écrit :
On Tue, 11 Nov 2014, Samuel Thibault wrote:
Steven Chamberlain, le Tue 11 Nov 2014 12:05:06 +, a écrit :
Although, how is that handled for hurd-i386? I assume it has no
security support, there may be some unofficial
On Tue, 11 Nov 2014, Samuel Thibault wrote:
Peter Palfrader, le Tue 11 Nov 2014 13:39:02 +0100, a écrit :
On Tue, 11 Nov 2014, Samuel Thibault wrote:
We are still stuck in the not released arch = no DSA machine = not
released arch loop.
Except that it's not a loop. DSA has indicated
Peter Palfrader wrote:
On Tue, 11 Nov 2014, Samuel Thibault wrote:
We are still stuck in the not released arch = no DSA machine = not
released arch loop.
Except that it's not a loop. DSA has indicated time and time again that
if an arch qualifies for a release in all other aspects, we'd
Steven Chamberlain, le Tue 11 Nov 2014 13:41:18 +, a écrit :
Practically it would be an 'official Debian port', and we'd have all the
usual things like install media.
I wouldn't call it official, but I agree on the rest. Getting hurt
by sid bugs is always a pain, and you can not have users
Hello,
2014-11-11 14:41 GMT+01:00 Steven Chamberlain ste...@pyro.eu.org:
Peter Palfrader wrote:
On Tue, 11 Nov 2014, Samuel Thibault wrote:
Anyway, I'm really hopeful now. weasel suggested a 'jessie-kfreebsd'
suite could still be supported by FTP team. (Actually, could that be
named
Hi Steven,
On Montag, 10. November 2014, Steven Chamberlain wrote:
So - while I disagree with the release team's decision - being an
unofficial release doesn't have to be a bad thing for us. It actually
gives us freedom to make improvements as we see fit. And it could be a
lot of fun.
I
Hi,
On Dienstag, 11. November 2014, Holger Levsen wrote:
about https://jenkins.debian.net/view/g-i-installation/job/g-i-
installation_debian_sid_daily_kfreebsd/ (and jessie and wheezy)
- I will need to fix the missing preseed file
done that, now it hangs like in
Hi Holger!
Thanks for your help with this. Automated d-i testing was
probably the first thing I wanted to do as we begin to put an
unofficial release together.
Holger Levsen wrote:
this is probably not the right way to boot the kfreebsd iso, which is it?
Hi Steven,
On Dienstag, 11. November 2014, Steven Chamberlain wrote:
Thanks for your help with this. Automated d-i testing was
probably the first thing I wanted to do as we begin to put an
unofficial release together.
yay!
To automatically boot an .iso, we'd need to edit the grub.cfg
On 11/11/14 18:05, Holger Levsen wrote:
On Dienstag, 11. November 2014, Steven Chamberlain wrote:
To automatically boot an .iso, we'd need to edit the grub.cfg inside of
it somehow.
The easiest alternative - something I emailed to you a while ago but I
didn't really get finished
right, I
Hi,
On Dienstag, 11. November 2014, Steven Chamberlain wrote:
You gave me feedback but I didn't come back to you yet with the changes
you suggested...
ah :)
I started over, amending the existing g-i-installation.sh instead of
trying to create a separate one; I've put it in a kfreebsd
Hei hei,
Am 2014-11-10 00:15, schrieb Steven Chamberlain:
Jonathan Wiltshire wrote:
We discussed kfreebsd at length, but are not satisfied that a
release with Jessie will be of sufficient quality. We are dropping
it as an official release architecture,
I hope we can come up with a
Jonathan Wiltshire wrote:
We discussed kfreebsd at length, but are not satisfied that a
release with Jessie will be of sufficient quality. We are dropping
it as an official release architecture,
:-(
I think we could support the kfreebsd core packages for an unofficial
stable release, but
Petr Salinger wrote:
Jonathan Wiltshire wrote:
[...] though we do hope that the
porters will be able to make a simultaneous unofficial release.
It is unclear, what we have to duplicate. Do we stay in testing ?
I'd like to know this as soon as possible as it affects our planning.
Thanks.
If
* Steven Chamberlain (ste...@pyro.eu.org) [141110 23:10]:
Petr Salinger wrote:
Jonathan Wiltshire wrote:
[...] though we do hope that the
porters will be able to make a simultaneous unofficial release.
It is unclear, what we have to duplicate. Do we stay in testing ?
I'd like to
Hi,
Andreas Barth wrote:
* Steven Chamberlain (ste...@pyro.eu.org) [141110 23:10]:
Petr Salinger wrote:
It is unclear, what we have to duplicate. Do we stay in testing ?
I'd like to know this as soon as possible as it affects our planning.
Thanks.
If we don't stay in testing,
Hi everyone,
I'd really like to hear others' thoughts on my ideas in this thread.
This can only happen with many people working together, so I need to
know which ideas from my brainstorming seem outlandish/crazy, which
are appealing, and who'd like to be involved.
Among users and potential
Hi all!
First, I do not really know enough about release workflow I guess to
know what -release@ does not want to do for kfreebsd apart from stamping
it as an official release so some of my whishes may be totally
reasonable or way of -- please tell me!
Steven Chamberlain ste...@pyro.eu.org
On 10 November 2014 00:15:36 CET, Steven Chamberlain ste...@pyro.eu.org wrote:
Jonathan Wiltshire wrote:
We discussed kfreebsd at length, but are not satisfied that a
release with Jessie will be of sufficient quality. We are dropping
it as an official release architecture,
Hi, long time lurker
Christoph Egger wrote:
Steven Chamberlain ste...@pyro.eu.org writes:
But certainly for unofficial releases, a supplemental repository would
be great for us. We can bypass usual freeze policy to fix bugs we think
are important, which may not have got an unblock.
I guess we need that
Eirik Schwenke wrote:
Finally, allow me to express my gratitude to everyone, both the release team
and the kfreebsd team, for all the hard work!
Thank you too! For pretty much perfectly summarising my own thoughts
with your mail. Especially the significance of the decision on the
distro
Sorry, actually meant to take -release@ out of Cc: for that mail.
Please follow up to -bsd@ if you have comments on it. Thanks.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Jonathan Wiltshire wrote:
We discussed kfreebsd at length, but are not satisfied that a
release with Jessie will be of sufficient quality. We are dropping
it as an official release architecture,
I hope we can come up with a suitable plan in response to this.
Here are some rather disorganised
On 2014-11-10 7:05, Andrew McGlashan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Steven,
On 10/11/2014 10:15 AM, Steven Chamberlain wrote:
Jonathan Wiltshire wrote:
We discussed kfreebsd at length, but are not satisfied that a
release with Jessie will be of sufficient quality.
58 matches
Mail list logo
