On Mon, Oct 09, 2006 at 03:54:48PM +0200, Michael Schmitz wrote:
> > the xfree86 stable-security build failed after 26 hours due to a lack of
> > free disk space (as opposed to firefox, where the build wasn't even started
> > at all in the dpkg-source stage. Please free more diskspace and restart
>
On Mon, Oct 09, 2006 at 05:18:15PM +0200, Michael Schmitz wrote:
> > > Perhaps the uploads failed for some reason, or the upload was rejected?
> > > Can you compile a list for me to check?
> > I'm watching this occasionally:
> > http://buildd.debian.org/~jeroen/status/architecture.php?a=m68k
> OK.
> > 2.6.17 without ADB seems pretty solid to me except for the genrtc problems
> > (I do have two nice panic logs on that issue, but these rather look like
> > the genrtc module itself is borked, as gen_rtc_ioctl+0x12a trips over a
> > NULL PC...) and the time lagging back more than one day by now.
> > Perhaps the uploads failed for some reason, or the upload was rejected?
> > Can you compile a list for me to check?
>
> I'm watching this occasionally:
> http://buildd.debian.org/~jeroen/status/architecture.php?a=m68k
OK. Part of my problems seem to originate from a borked reply address on
spi
Hi,
On Mon, 9 Oct 2006, Michael Schmitz wrote:
> > BTW what's up with all the packages hanging around in the Maybe-Successful
> > state, some even for two weeks?
>
> Perhaps the uploads failed for some reason, or the upload was rejected?
> Can you compile a list for me to check?
I'm watching th
> the xfree86 stable-security build failed after 26 hours due to a lack of
> free disk space (as opposed to firefox, where the build wasn't even started
> at all in the dpkg-source stage. Please free more diskspace and restart
> ASAP, if it's delaying things for too long I'll release without m68k.
> BTW what's up with all the packages hanging around in the Maybe-Successful
> state, some even for two weeks?
Perhaps the uploads failed for some reason, or the upload was rejected?
Can you compile a list for me to check?
> The most important one is java-gcj-compat, so xulrunner can be finally
>
Hi,
BTW what's up with all the packages hanging around in the Maybe-Successful
state, some even for two weeks?
The most important one is java-gcj-compat, so xulrunner can be finally
compiled and Dep-Wait becomes a lot smaller.
bye, Roman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
Hi,
On Mon, 9 Oct 2006, Michael Schmitz wrote:
> qt4 needs inotify support to build. Did that come with a recent
> kernel-headers update, or do we still need a patch there?
It seems it doesn't even look at the system header, I reported a bug for
it (#391902).
bye, Roman
--
To UNSUBSCRIBE, e
> > I have no idea what kind of machine this happened on. If it's not Sonic or
> > IIfx, locking or interrupt reentry seems most likely. The 5380 driver of
> > old mostly relies on interrupts being masked on entry, and the big kernel
> > lock held.
>
> I hadn't looked at it that closely. However, t
> > the more RAM you gives to Linux the more it will like you, won't it? ;-)
>
> Sure, but are not we limited to about 128Mb of RAM by the plateform ?
> This is not much by current standard.
Do tell that to my Falcon/CT60. What did I buy the 512 MB RAM stick for?
:-)))
> I have still not figured
Hi,
qt4 needs inotify support to build. Did that come with a recent
kernel-headers update, or do we still need a patch there?
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
12 matches
Mail list logo
