Tino Mettler wrote:
> The exact problem was this build failure:
> https://buildd.debian.org/status/fetch.php?pkg=syncevolution&arch=kfreebsd-amd64&ver=1.4.99.4-1&stamp=1414299789
>
> I don't know if SOCK_CLOEXEC is just unavailable on Debian/kFreeBSD (as
> stock FreeBSD seems to support it), or if
On Tue, Nov 04, 2014 at 20:41:44 +, Steven Chamberlain wrote:
> Hi Tino,
>
> Tino Mettler wrote:
> > I also was bugged by a sockopt related FTBFS on kFreeBSD last weekend.
>
> Which package is that? I didn't notice anything like that on
> buildd status pages.
Hi,
the package was syncevolut
Hi Tino,
Tino Mettler wrote:
> I also was bugged by a sockopt related FTBFS on kFreeBSD last weekend.
Which package is that? I didn't notice anything like that on
buildd status pages.
> I tried my luck on #debian-kbsd which I was pointed to on a wiki page.
> It was rather silent, though.
I pe
(dropping -devel)
Tino Mettler writes ("Re: A small thanks to the kFreeBSD porters"):
> On Tue, Oct 28, 2014 at 12:36:26 +, Ian Jackson wrote:
> > While fixing the bug on a porterbox I got very helpful IRC support
>
> Hi Ian,
>
> did you get this on a p
On Tue, Oct 28, 2014 at 12:36:26 +, Ian Jackson wrote:
[...]
> While fixing the bug on a porterbox I got very helpful IRC support
Hi Ian,
did you get this on a particular channel? If yes, what channel?
I also was bugged by a sockopt related FTBFS on kFreeBSD last weekend.
I tried my luck o
I would like to share a good experience I had with the kFreeBSD porter
team. On Sunday afternoon I foolishly uploaded a package which, if I
had thought about it, I ought to have known would FTBFS on FreeBSD.
Less than 4 hours later I had a bug report (#766913) from Steven
Chamberlain, who had tri
6 matches
Mail list logo
