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"
ector, in preference to a mess of APT sources
> - place to run c-i testing, QA tools
> - infrequent archive-wide rebuilds
Use the existing infrastructure.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The
ildds and porterboxes close to the release. And, TTBOMK, the release
team has so far accepted that. IOW the fact that hurd is not being
released with jessie is not due to not having d.o systems.
--
| .''`. ** Debian **
Peter Pal
ing a jessie kfreebsd release is a prerequisite for keeping
the debian.org machine resources (buildds, porterboxes). DSA can't
maintain rolling releases or testing systems for any length of time.
Cheers,
--
| .''`. ** Debian **
Peter Palfr
ld that enables or disables features based on the
running kernel is broken anyway.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `-htt
Package: type-handling
Version: 0.2.23
Severity: important
Hi,
as discussed on IRC, type-handling provides not+gnu-linux on linux
hosts, such as zelenka (s390/lenny) and quantz (amd64/squeeze).
I noticed because some of our hosts started pulling in type-handling
rather than installing the d.o-li
On Sun, 22 Aug 2010, Adam D. Barratt wrote:
> On Thu, 2010-08-05 at 22:41 +0200, Peter Palfrader wrote:
> > > > So, what do you think is still missing? What would we need to
> > > > communicate
> > > > as a disclaimer to the users if releasing kFreeBSD i
unless => "/bin/sh -c '! [ -e $linkto ] || ! [ -e
/etc/alternatives/$name ] || ([ -L /etc/alternatives/$name ] && [
/etc/alternatives/$name -ef $linkto ])'"
}
}
...
set_alternatives {
"editor":
linkto => "/usr/b
On Thu, 05 Aug 2010, Lucas Nussbaum wrote:
> On 05/08/10 at 22:41 +0200, Peter Palfrader wrote:
> > On Wed, 04 Aug 2010, Aurelien Jarno wrote:
> >
> > > > So, what do you think is still missing? What would we need to
> > > > communicate
> >
at I'm not entirely happy with what
we have so far.
The biggest pain for us currently is that puppet just does not work
reliably on kfreebsd (both i386 and amd64). This may be a ruby bug, but
it's still really, really annoying.
weasel
--
| .'
On Tue, 03 Aug 2010, Steve M. Robbins wrote:
> Can I use the official Debian developer machines for this task?
As long as you do it manually.
Maybe an alternative is to upload packages to experimental.
--
| .''`. ** Debian GNU/Linux **
Pe
-security/sys linsysfs
rw 0 2
However, /home does not get mounted when the system boots.
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `'
Package: freebsd-utils
Version: 8.0-10
Severity: normal
Hi,
for some reason fasch.d.o (our amd64 kfreebsd buildd) now fails to mount
/home.
fstab has, among others, these:
| /dev/ufsid/4b5a0084c7a8d5ad /srv ufs rw 0 2
| /srv/home /home nullfs rw 0 0
During boot we see 'mount_nu
ocessor : 1
> | processor : 2
> | processor : 3
> `
Probably two single-core CPUs times two for hyperthreading. I don't
think it has 4 cores.
Cheers,
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The univ
On Thu, 11 Feb 2010, Craig Small wrote:
> On Thu, Feb 11, 2010 at 01:48:07AM +0100, Peter Palfrader wrote:
> > | wea...@field:~$ cat /proc/uptime ; grep 'cpu ' /proc/stat ; cat
> > /proc/uptime
> > | 188847.15 673325.21
> > | cpu 119994 4473784 3539322 274662
debian-po...@lists.debian.org as user.
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `-http://www.debian
On Wed, 29 Mar 2006, Robert Millan wrote:
> Brian already answered about macros, but anyway, I was wondering: why not
> something like this instead?:
>
> #if HAVE_SYS_LIMITS_H
> #include
> #elif HAVE_MACHINE_LIMITS_H
> #include
> #endif
I don't know. I guess the rationale was that "if it's t
On Wed, 29 Mar 2006, Brian M. Carlson wrote:
> > It seems the Debian/KFreeBSD port doesn't have __FreeBSD__ define.
>
> That is correct.
>
> > Is __FreeBSD__ only for the Real FreeBSD, and if yes, what should the
> > code check for instead or in addition?
> To answer your question in this case,
Hey,
one of my packages checks whether __FreeBSD__ is defined[1] and if that
is the case i then avoids including machine/limits.h as this only causes
noise on FreeBSD[0].
It seems the Debian/KFreeBSD port doesn't have __FreeBSD__ define.
Is __FreeBSD__ only for the Real FreeBSD, and if yes, what
19 matches
Mail list logo
