Steven Chamberlain writes:
> Steven Chamberlain wrote:
>> Could someone with access to the hurd-i386 or kfreebsd porter boxes
>> try the attached patch please?
>
> Here's how to run that test on its own, verbosely, in an already-built
> Debian build tree:
>
> $ Build/bin/cmake "-DCMAKE_MODULE_
Hi
FWIW on the 3.2 build (with the patch) I started untill I noticed it
wasn't quite the right version
Steven Chamberlain writes:
> Andreas Beckmann wrote:
>> 292 - RunCMake.Configure (Failed)
>
> Could someone with access to the hurd-i386 or kfreebsd porter boxes
> try the attached patch p
Hi!
Steven Chamberlain 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
Package: src:pillow
Version: 2.3.0-2
Severity: normal
Tags: patch
Hi!
pillow currently does add multiarc paths on linux only. As a result,
no decoders are built. The patch below should also add these on the
other debian architectures.
--- pillow-2.3.0.orig/setup.py
+++ pillow-2.3.0/setup.py
@@
Hi!
Ondřej Surý writes:
> I don't really want to open another can of worms, but what's the opinion
> of non-Linux ports maintainers on default init?
Hm so why was none of the ports list Cc-ed on this mail? There is
active discussion [0] between hurd and bsd people were we want to go
now.
> Or
Hi,
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For kfreebsd-*, I
- test packages on this architecture
This includes running a Desktop (Notebook) System on testing and am
therefore testing the relevant stack
Christoph Egger writes:
> As suggested by Michael Banck on IRC I've been looking at Signals used
> by both parts to see if they e.g. battle over SIGUSR?. However libgc
> seems to use 32+{5,6} as signals on x86 FREEBSD __GLIBC__ at
> least. Petr, Steven: any idea why this is?
Hi!
As suggested by Michael Banck on IRC I've been looking at Signals used
by both parts to see if they e.g. battle over SIGUSR?. However libgc
seems to use 32+{5,6} as signals on x86 FREEBSD __GLIBC__ at
least. Petr, Steven: any idea why this is? Are these signals fine for
kfreebsd glibc (signa
Hi!
YunQiang Su writes:
> ifconfig em0.23 create
actually this seems to be enough already
Regards
Christoph
--
To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87l
YunQiang Su writes:
> On Thu, Sep 27, 2012 at 12:11 PM, Christoph Egger
> wrote:
>> YunQiang Su writes:
>>> I am trying to add VLAN (802.1q) support to netcfg, while I still confused
>>> by
>>> which command to use to configure vlan, ip or ipconfig
YunQiang Su writes:
> I am trying to add VLAN (802.1q) support to netcfg, while I still confused by
> which command to use to configure vlan, ip or ipconfig or something else.
ifconfig vlan0 create
ifconfig vlan0 vlan 23 vlandev em0
> Another problem is whether ifupdown support VLAN on kfreebsd
Package: src:qasmixer
Version: 0.14.0-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: linux-specific
X-Debbugs-Cc: debian-...@lists.debian.org, debian-hurd@lists.debian.org
Hi!
Your package seems to be specific to linux and won't work on
kfreebsd or hurd. Please consider settin
Package: src:gnome-alsamixer
Version: 0.9.7~cvs.20060916.ds.1-3
Severity: normal
User: debian-...@lists.debian.org
Usertags: linux-specific
X-Debbugs-Cc: debian-...@lists.debian.org, debian-hurd@lists.debian.org
Hi!
Your package seems to be specific to linux and won't work on
kfreebsd or hurd
Package: src:postfix
Version: 2.8.4-1
Severity: serious
X-Debbugs-Cc: debian-...@lists.debian.org,debian-hurd@lists.debian.org
Tags: sid wheezy
Justification: fails to build from source (but built successfully in the past)
Hi!
Your package failed to build on the kfreebsd and hurd buildds. For
kFr
14 matches
Mail list logo
