Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Justin C. Sherrill
On Sat, January 3, 2009 1:05 pm, Matthew Dillon wrote: > I'm strongly considering delaying 2.2 until the end of January. > I am nowhere near done with the hammer fsck directive. That would > give us a chance to rebuild Q4 ? Assuming these building issues are fixed, it'd take about a w

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Justin C. Sherrill
On Sat, January 3, 2009 8:13 pm, Simon 'corecode' Schubert wrote: > Justin C. Sherrill wrote: >> On the plus side, the version of DragonFly on pkgbox is new enough to (I >> think) avoid the hal issues, but old enough to avoid the reentrancy >> issues. It's more than 3/4 of the way through a bulk b

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Joerg Sonnenberger
On Sat, Jan 03, 2009 at 03:35:55PM +0100, Simon 'corecode' Schubert wrote: > -100, neg, horrible solution. can't let changes in world be dictated > by whatever in pkgsrc. Right, just lets randomly change ABIs of system libraries. Oh wait. Joerg

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Simon 'corecode' Schubert
Justin C. Sherrill wrote: On the plus side, the version of DragonFly on pkgbox is new enough to (I think) avoid the hal issues, but old enough to avoid the reentrancy issues. It's more than 3/4 of the way through a bulk build, so we should have a newer batch of packages to use. Maybe not exactl

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Justin C. Sherrill
On Sat, January 3, 2009 8:07 am, Hasso Tepper wrote: > Pkgsrc 2008Q4 will be branched/released any minute now, but the state of > it in DragonFly is quite sad. > > Most of gnome and a lot of other packages fail to build on DragonFly 2.0 > due to brokeness of hal and some other stuff on it. I failed

Re: Out of date mirrors

2009-01-03 Thread Matthias Schmidt
Hi, * Jeremy C. Reed wrote: > > If nobody, then I will handle the ISC mirror to make sure it is > up-to-date. I sent an email to mirr...@isc some time ago, but nobody responded :/ Feel free to update the mirror. Matthias

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Matthew Dillon
:Can't Peter deal with those in the same way like with the database :functions? :... : :I think between now and our RELEASE this should be fixed by backing out :stuff the same way as you did for the db funcs. : :It would be disappointing if we can't use Q4 for 2.2. : :Sascha : :-- :http://yoyody

Re: Drop ISA and EISA NICs support

2009-01-03 Thread Matthew Dillon
: :Sascha Wildner schrieb: :> Hey cool idea. Generally my plan was to wait until after 2.2 and then :> drop support for all ISA drivers that need a physical ISA card and all :> EISA drivers. Making 2.0 the last release to support ISA. : :Making 2.2 the last release to support ISA I meant. : :Sas

Re: Out of date mirrors

2009-01-03 Thread Jeremy C. Reed
On Sat, 3 Jan 2009, Matthias Schmidt wrote: > I had a quick look over our mirrors page and noticed that some of them > are either down or badly out-of-date. The affected mirrors are: > > - ISC Who at DragonFly is responsible for this? If nobody, then I will handle the ISC mirror to make sure

Trying to run in Bangho TN120R

2009-01-03 Thread Sdävtaker
hey, I installed DFBSD2.0.1 and i get this message all the time: ACPI Error (psargs-0459): [\\_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND ACPI Error (psparse-0638): Method parse/execution failed [\\_SB_.AC__.ADJP] (Node 0xc5aca674), AE_NOT_FOUND ACPI Error (psparse-0638): Method parse/

Out of date mirrors

2009-01-03 Thread Matthias Schmidt
Hi, I had a quick look over our mirrors page and noticed that some of them are either down or badly out-of-date. The affected mirrors are: - startkast.net - ISC - Joergs pkgsrc-box - boulder.tele.dk Could the admins please speak up if they are willing to update the mirrors or not. In the latte

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Matthias Schmidt
* Simon 'corecode' Schubert wrote: > Matthias Schmidt wrote: > > We should adopt the following policy: Before someone commits some big > > diff (like the mentioned one) or some stuff that breaks the > > API/whatever, the diff should be applied to clean machine which runs a > > full pkgsrc bulk bu

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Sascha Wildner
Simon 'corecode' Schubert schrieb: Matthias Schmidt wrote: We should adopt the following policy: Before someone commits some big diff (like the mentioned one) or some stuff that breaks the API/whatever, the diff should be applied to clean machine which runs a full pkgsrc bulk build. If the bui

Re: Drop ISA and EISA NICs support

2009-01-03 Thread Sascha Wildner
Matthias Schmidt schrieb: Following NIC drivers' ISA part: an, ar, cs, ed, ep, ex, fe, sn Not sure about ed(4). This driver is often used in virtualization software. At least it was used in qemu some time ago, but I'm not sure if its still used today. Can somebody comment on that? It's use

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Simon 'corecode' Schubert
Matthias Schmidt wrote: > We should adopt the following policy: Before someone commits some big > diff (like the mentioned one) or some stuff that breaks the > API/whatever, the diff should be applied to clean machine which runs a > full pkgsrc bulk build. If the build fails, there is enough time

Re: Drop ISA and EISA NICs support

2009-01-03 Thread Matthias Schmidt
Hi, * Sepherosa Ziehau wrote: > Hi all, > > I plan to drop > > Following NIC drivers' ISA part: > an, ar, cs, ed, ep, ex, fe, sn Not sure about ed(4). This driver is often used in virtualization software. At least it was used in qemu some time ago, but I'm not sure if its still used today. C

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Sascha Wildner
Hasso Tepper schrieb: A lot of 2008Q4 is broken with master as well. With brought in reentrant user/group database access functions (getpwnam_r etc) too much stuff was broken (starting from core X) and because it was incomplete as well, I committed the hack to make these unusable for now. But t

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Matthias Schmidt
Hi, * Hasso Tepper wrote: > > A lot of 2008Q4 is broken with master as well. With brought in reentrant > user/group database access functions (getpwnam_r etc) too much stuff was > broken (starting from core X) and because it was incomplete as well, I > committed the hack to make these unusable

Re: Drop ISA and EISA NICs support

2009-01-03 Thread Sascha Wildner
Sascha Wildner schrieb: Hey cool idea. Generally my plan was to wait until after 2.2 and then drop support for all ISA drivers that need a physical ISA card and all EISA drivers. Making 2.0 the last release to support ISA. Making 2.2 the last release to support ISA I meant. Sascha -- http://

Re: The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Sepherosa Ziehau
On Sat, Jan 3, 2009 at 9:07 PM, Hasso Tepper wrote: > Pkgsrc 2008Q4 will be branched/released any minute now, but the state of > it in DragonFly is quite sad. > > Most of gnome and a lot of other packages fail to build on DragonFly 2.0 > due to brokeness of hal and some other stuff on it. I failed

Re: Drop ISA and EISA NICs support

2009-01-03 Thread Sascha Wildner
Sepherosa Ziehau schrieb: Hi all, I plan to drop Following NIC drivers' ISA part: an, ar, cs, ed, ep, ex, fe, sn Following NIC drivers' EISA part: ep, vx Following NIC drivers will be complete dropped (ISA only): el, ie, le, rdp, wl If no objection comes within next three days, I will start

Drop ISA and EISA NICs support

2009-01-03 Thread Sepherosa Ziehau
Hi all, I plan to drop Following NIC drivers' ISA part: an, ar, cs, ed, ep, ex, fe, sn Following NIC drivers' EISA part: ep, vx Following NIC drivers will be complete dropped (ISA only): el, ie, le, rdp, wl If no objection comes within next three days, I will start the dropping. Best Regards,

The state of DragonFly and pkgsrc 2008Q4

2009-01-03 Thread Hasso Tepper
Pkgsrc 2008Q4 will be branched/released any minute now, but the state of it in DragonFly is quite sad. Most of gnome and a lot of other packages fail to build on DragonFly 2.0 due to brokeness of hal and some other stuff on it. I failed to find a time to care about 2.0 (backporting changes etc)