On Sun, Aug 17, 2014 at 11:52:42PM +0300, Niko Tyni wrote:
On Sat, Aug 16, 2014 at 12:26:15PM +0300, Niko Tyni wrote:
Package: libnet-arp-perl
Version: 1.0.8-1
Severity: serious
Rebuilding this package against Perl 5.20 failed on the kfreebsd-* buildds:
cc -c -D_REENTRANT
Hi guys,
This is my first post.
I'm trying to install Yunohost (A very nice install and play, debian
based hosting distribution : https://yunohost.org/ ) in a jail Debian
kFreeBSD.
You can download the ISO or install with a script from a fresh Debian.
I know the product is not support
On Tue, 19 Aug 2014, pentako...@openmailbox.org wrote:
Hi guys,
This is my first post.
I'm trying to install Yunohost (A very nice install and play, debian based
hosting distribution : https://yunohost.org/ ) in a jail Debian kFreeBSD.
You can download the ISO or install with a script
On Tue, 19 Aug 2014 21:49, pentako...@openmailbox.org said:
In the installation i have this message and fail :
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
Well, read the FAQ - although I am not sure that our new FAQ still has
an
Hi,
On Tue, 19 Aug 2014 21:49, pentako...@openmailbox.org said:
I know the product is not support under Debian / kFreeBSD but i would
try :
That will be interesting; it is surprising that some applications work
on GNU/kFreeBSD although the developer didn't try it.
gpg: WARNING: using
On 19/08/14 00:40, Cyril Brulebois wrote:
[ I'm adding -release@ to the loop. I tried to refrain from mentioning
my concerns in the Jessie Beta 1 announce, that's why I used a quite
neutral wording, but let's be honest: kfreebsd-* is looking bad right
now. ]
I was drafting a quite long reply
On 14/08/14 18:32, Cyril Brulebois wrote:
Now, I think there are several questions to answer:
1. What were the reasons for having arch-dependent dhcp clients?
I'd speculate because udhcpc from busybox is very small, and
isc-dhcp-client-udeb was about 2 MiB. It targets (currently only builds
Taking a very critical view to kfreebsd's available time and resources,
we might leave this totally unaddressed for jessie and leave it as an
errata again. Yes that's shoddy, but it is a mostly cosmetic issue.
It happens due to CAM changes in kfreebsd-9 and later. I think the only
serious
Steven Chamberlain ste...@pyro.eu.org (2014-08-20):
On 14/08/14 18:32, Cyril Brulebois wrote:
Now, I think there are several questions to answer:
1. What were the reasons for having arch-dependent dhcp clients?
I'd speculate because udhcpc from busybox is very small, and
On 14/08/14 18:15, Cyril Brulebois wrote:
[...] If a
single extra udeb (or udeb size increase, which happens from time to
time) is going to break kfreebsd-*, it seems to me that their status
is far too brittle.
The fixed-size d-i initrds had to be carefully sized for kfreebsd wheezy.
We
Processing control commands:
severity -1 important
Bug #750836 [kfreebsd-kernel-headers] machine/atomic.h broken, missing
__compiler_membar macro
Severity set to 'important' from 'serious'
--
750836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750836
Debian Bug Tracking System
Contact
Control: severity -1 important
tcpdump has kindly worked around this; I can't find other packages
blocked by it, so I don't think this is RC-severity any more, but still
important nonetheless.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to
Control: severity -1 important
libpcap has kindly worked around this; I can't find other packages
blocked by it, so I don't think this is RC-severity any more, but still
important nonetheless.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to
Processing control commands:
severity -1 important
Bug #756553 [kfreebsd-kernel-headers] kfreebsd-kernel-headers missing
/usr/include/net/if_pflog.h
Severity set to 'important' from 'serious'
--
756553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756553
Debian Bug Tracking System
Contact
Steven Chamberlain ste...@pyro.eu.org (2014-08-20):
On 14/08/14 18:15, Cyril Brulebois wrote:
[...] If a
single extra udeb (or udeb size increase, which happens from time to
time) is going to break kfreebsd-*, it seems to me that their status
is far too brittle.
The fixed-size d-i
On 20/08/14 01:49, Cyril Brulebois wrote:
If you're trying to insinuate I/we deliberately broke kfreebsd-* by
introducing partman-iscsi, [...]
No, I was not insinuating that.
But I am still asking: how is it that partman-iscsi is being installed
into a kfreebsd d-i image (by APT I believe)?
Steven Chamberlain ste...@pyro.eu.org (2014-08-20):
On 20/08/14 01:49, Cyril Brulebois wrote:
If you're trying to insinuate I/we deliberately broke kfreebsd-* by
introducing partman-iscsi, [...]
No, I was not insinuating that.
But I am still asking: how is it that partman-iscsi is
Steven Chamberlain ste...@pyro.eu.org (2014-08-20):
But I am still asking: how is it that partman-iscsi is being installed
into a kfreebsd d-i image (by APT I believe)? I'd expect it to be
uninstallable due to missing dependencies. Could that be a bug, or is
it a known limitation?
Thanks.
Steven Chamberlain ste...@pyro.eu.org (2014-08-20):
But it *is* also relevant here. Each udeb in our image takes up space
for the extracted files, but also I suspect _considerable_ space in
cdebconf data. Addressing this may already fix the ENOSPC error, and if
we can keep the anna excludes
Package: xserver-xorg-video-nv
Version: 1:2.1.20-2
Severity: grave
Justification: renders package unusable
Hi,
your package needs an update for the transition to xorg-server 1.16
which happened in July.
https://packages.qa.debian.org/x/xserver-xorg-video-nv/news/20140715T163918Z.html
Your
Petr Salinger petr.salin...@seznam.cz (2014-07-15):
Nearer the time, if we still only have a BETA or RC in sid and serious
bugs, we may decide to just stay with 10.0. If a BETA or RC is
*already* in testing, we may want to ask the release time about getting
a pre-approved unblock when the
On Tue, Aug 19, 2014 at 8:10 PM, Cyril Brulebois wrote:
Steven Chamberlain ste...@pyro.eu.org (2014-08-20):
On 14/08/14 18:32, Cyril Brulebois wrote:
Now, I think there are several questions to answer:
1. What were the reasons for having arch-dependent dhcp clients?
I'd speculate because
22 matches
Mail list logo
