On Thu, 2013-05-09 at 16:39 +0200, Samuel Thibault wrote:
> Svante Signell, le Thu 09 May 2013 16:25:46 +0200, a écrit :
> > Why do you expect anything to be different now compared when the freeze
> > happened, _several months ago_, in zero time?
>
> Please avoid this level of language, it can't b
Svante Signell, le Thu 09 May 2013 16:25:46 +0200, a écrit :
> Why do you expect anything to be different now compared when the freeze
> happened, _several months ago_, in zero time?
Please avoid this level of language, it can't bring anything good to the
discussion.
Samuel
--
To UNSUBSCRIBE,
On Mon, 2013-05-06 at 21:47 +0100, Steven Chamberlain wrote:
> Hi Samuel,
>
> On 06/05/13 21:35, Samuel Thibault wrote:
> > Steven Chamberlain, le Mon 06 May 2013 21:20:57 +0100, a écrit :
> >> In that case would there be 150-200 RC-severity bugs introduced right
> >> away by its inclusion?
> >
>
Steven Chamberlain, le Wed 08 May 2013 18:36:33 +0100, a écrit :
> My idea would be to look at the (I estimate) 90+ packages that are
> out-of-date in sid on GNU/Hurd but not other arches, and were not
> already removed by #704477. This includes some important ones like
> gcc-4.8, gdb.
gcc-4.8 wa
On 08/05/13 16:52, Cyril Brulebois wrote:
> Samuel Thibault (08/05/2013):
>> I'm afraid I'll still not be able to explain people when they ask me
>> why hurd-i386 is not in testing, except vague reasons.
>
> For the record, and speaking only for myself, I'd love to see a proper
> architecture qua
Cyril Brulebois, le Wed 08 May 2013 17:52:13 +0200, a écrit :
> Now, I think everyone having actually worked on the release would
> enjoy (and probably deserve) a few days/weeks of rest before resuming
> release duties, which include:
I was also thinking the same when I saw the issue popping up al
Samuel Thibault (08/05/2013):
> I'm afraid I'll still not be able to explain people when they ask me
> why hurd-i386 is not in testing, except vague reasons.
For the record, and speaking only for myself, I'd love to see a proper
architecture qualification process, rather than Neil's “approach” to
Sorry to clutter the mailing list.
But as a long time lurker at the mailing list I would just like to thank the
"Hurd team" for all your efforts!
@Samuel, I totally agree with you on your points.
I have been happily running Hurd on my (reasonably new) core 2 computer for a
year. It wasn't hard
Neil McGovern, le Wed 08 May 2013 16:07:26 +0100, a écrit :
> No, just something that works for the majority of our users. I'm fairly
> sure things like SATA and USB is considered essential.
SATA, yes. USB, less.
> > > > > d) VMWare/VBox etc.
> > > >
> > > > This already works.
> > >
> > > Just
On Wed, May 08, 2013 at 04:33:03PM +0200, Samuel Thibault wrote:
> Neil McGovern, le Wed 08 May 2013 11:35:52 +0100, a écrit :
> > But not tested - how about USB - did that ever get sorted?
>
> We have not worked on it.
>
> > How about things like wireless drivers, raid controllers,
> > suspend/r
Neil McGovern, le Wed 08 May 2013 11:35:52 +0100, a écrit :
> > About disk support, I happen to have right now a few days of holiday
> > with no RL plans (at last!), so I'll work on the SATA driver. Having it
> > working within a month should just happen.
>
> But not tested - how about USB - did t
On Wed, May 08, 2013 at 01:07:42AM +0200, Samuel Thibault wrote:
> Neil McGovern, le Tue 07 May 2013 11:14:01 +0100, a écrit :
> > On Mon, May 06, 2013 at 10:27:54PM +0200, Samuel Thibault wrote:
> > > We have not worked too much on the hardware support in the past months,
> > > so it is basically
Paul Wise, le Wed 08 May 2013 12:06:01 +0800, a écrit :
> On Wed, May 8, 2013 at 8:21 AM, Samuel Thibault wrote:
> > We haven't worked on microcode upload, since we don't necessarily target
> > non-freeness...
>
> So, someday the Hurd will need support for microcode upload.
Well, I haven't said w
On Wed, May 8, 2013 at 8:21 AM, Samuel Thibault wrote:
> We haven't worked on microcode upload, since we don't necessarily target
> non-freeness...
I'm not sure where Hurd is at with wireless drivers, but there is some
GPLed WiFi firmware out there:
http://linuxwireless.org/en/users/Drivers/carl
Steven Chamberlain, le Wed 08 May 2013 00:59:19 +0100, a écrit :
> > Neil McGovern, le Tue 07 May 2013 11:14:01 +0100, a écrit :
> >> a) A HP DL360 or similar
>
> The chipset has changed a bit between generations:
>
> G1: eepro (Linux) or fxp (*BSD) driver, requiring non-free microcode
We haven'
Steven Chamberlain, le Wed 08 May 2013 00:59:19 +0100, a écrit :
> >> d) VMWare/VBox etc.
> >
> > This already works.
> >
> > Also, Xen support just works [...]
>
> With network connectivity?
Sure.
> If so which NIC do they emulate? (rtl8139?)
They don't emulate a nic, it's ParaVirtualizatio
On 08/05/13 00:07, Samuel Thibault wrote:
> I don't know what ethernet driver these would need.
Should probably start a GNU/Hurd hardware status page on the Wiki...
> Neil McGovern, le Tue 07 May 2013 11:14:01 +0100, a écrit :
>> a) A HP DL360 or similar
The chipset has changed a bit between gen
Neil McGovern, le Tue 07 May 2013 11:14:01 +0100, a écrit :
> On Mon, May 06, 2013 at 10:27:54PM +0200, Samuel Thibault wrote:
> > We have not worked too much on the hardware support in the past months,
> > so it is basically network board drivers from linux 2.6.32, and IDE
> > disk support. I for
On Mon, May 06, 2013 at 10:27:54PM +0200, Samuel Thibault wrote:
> We have not worked too much on the hardware support in the past months,
> so it is basically network board drivers from linux 2.6.32, and IDE
> disk support. I for instance installed it on my Dell D430, and network
> just works fin
Well maybe that was a poor choice of words. I don't even quite understand what
some of the columns
mean, to be honest. But a visceral response to all of the red and yellow
blocks was kind of sad
knowing how much you all (and myself to a MUCH lesser degree) have put into it
over the last couple
Steven Chamberlain, le Mon 06 May 2013 21:47:00 +0100, a écrit :
> On 06/05/13 21:35, Samuel Thibault wrote:
> > Steven Chamberlain, le Mon 06 May 2013 21:20:57 +0100, a écrit :
> >> In that case would there be 150-200 RC-severity bugs introduced right
> >> away by its inclusion?
> >
> > I would r
Hi Samuel,
On 06/05/13 21:35, Samuel Thibault wrote:
> Steven Chamberlain, le Mon 06 May 2013 21:20:57 +0100, a écrit :
>> In that case would there be 150-200 RC-severity bugs introduced right
>> away by its inclusion?
>
> I would rather say simply dropping them, as already requested in
> Bug#704
Steven Chamberlain, le Mon 06 May 2013 21:20:57 +0100, a écrit :
> On 06/05/13 20:27, Joerg Jaspert wrote:
> > Adding it and then keeping it out of the usual migration rules is asking
> > for failure from the beginning, accumulating cruft. Not a way to go, IMO.
>
> In that case would there be 150-
Joerg Jaspert, le Mon 06 May 2013 21:27:46 +0200, a écrit :
> Adding it and then keeping it out of the usual migration rules is asking
> for failure from the beginning, accumulating cruft. Not a way to go, IMO.
Excluding from the migration rules would probably become a headache,
yes. But wouldn't
Barry deFreese, le Mon 06 May 2013 13:32:04 -0400, a écrit :
> Fair enough and no offense taken. As I said, I haven't been contributing for
> quite a while now so
> they were more questions for myself than anything. Niels actually showed me
> the graph and it is a
> bit sadder than I had hoped.
Neil McGovern, le Mon 06 May 2013 17:15:45 +0100, a écrit :
> On Mon, May 06, 2013 at 09:36:55AM -0400, Barry deFreese wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > OK, I have been significantly out of the loop for a while now but what
> > do you base that on?
> >
> > What requirements are we
On 06/05/13 20:27, Joerg Jaspert wrote:
> Adding it and then keeping it out of the usual migration rules is asking
> for failure from the beginning, accumulating cruft. Not a way to go, IMO.
In that case would there be 150-200 RC-severity bugs introduced right
away by its inclusion? (Packages whi
>> with all the others (probably as a technology preview)...
>> So, release people: How likely is it that Hurd gets added to jessie?
> If added as a 'technology preview', what does that mean exactly?
Note that the tech preview was a softening of a requirement to get added
to wheezy. Which didn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fair enough and no offense taken. As I said, I haven't been contributing for
quite a while now so
they were more questions for myself than anything. Niels actually showed me
the graph and it is a
bit sadder than I had hoped. :( Though we do have a
On Mon, May 06, 2013 at 09:36:55AM -0400, Barry deFreese wrote:
> -BEGIN PGP SIGNED MESSAGE-
> OK, I have been significantly out of the loop for a while now but what
> do you base that on?
>
> What requirements are we still falling short on?
>
Percentage built, percentage up to date, and
On 05/05/13 16:07, Joerg Jaspert wrote:
> ...released together
> with all the others (probably as a technology preview)...
> So, release people: How likely is it that Hurd gets added to jessie?
If added as a 'technology preview', what does that mean exactly?
Would Hurd-specific RC-severity bug
On Mon, May 06, 2013 at 05:15:44PM +0100, Neil McGovern wrote:
> Percentage built, percentage up to date, and (as far as I know) a
> working port and installer for a modern desktop machine?
>
Um, having read back the above, it may have sounded a bit more curt than
I was expecting, apologies! Thos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, I have been significantly out of the loop for a while now but what do you
base that on?
What requirements are we still falling short on?
Thanks,
Barry deFreese
On 5/6/2013 7:08 AM, Neil McGovern wrote:
> On Sun, May 05, 2013 at 05:07:13PM +020
On Sun, May 05, 2013 at 05:07:13PM +0200, Joerg Jaspert wrote:
> So, release people: How likely is it that Hurd gets added to jessie?
> Within the next one or two months I mean, not "maybe in a years
> time". :)
>
I don't see it happening, to be honest.
Neil
--
signature.asc
Description: Digi
Hi
From our FTPMaster meeting 2011 minutes[1]:
--88---
- In a discussion with the Debian Hurd porters it was decided that the
Hurd port stays on FTPMaster until Wheezy is released. Should they
have managed to get the port into a state
35 matches
Mail list logo
