le: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Date: Fri, 27 Mar 2020 21:26:21 +
From: Steven Chamberlain
Subject: Add extra libs required to build aicasm
--- a/sys/dev/aic7xxx/aicasm/Makefile
+++ b/sy
severity 868929 important
thanks
(linux-)amd64 is not in this package's Architectures: field, therefore
FTBFS on that arch cannot be a RC bug? (Though I'd be interested in
fixing it someday).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Package: libblkmaker
Version: 0.5.3-1
Severity: grave
Tags: fixed-upstream
Hi,
The version of libblkmaker in sid/stretch supports bitcoin blocks up to
version 4 only:
http://sources.debian.net/src/libblkmaker/0.5.3-1/blkmaker.h/#L15
But since early 2016, the tip of the blockchain uses predemonan
sonal interactions beyond that, is just too
much. That is the real "debacle"; it is not surprising to me now, that
this did not happen yet in 10 years, or that no enthusiastic new
contributor had already done this.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Descr
Bastian Blank wrote:
> On Tue, Feb 28, 2017 at 10:00:01PM +0000, Steven Chamberlain wrote:
> > That differs from the latest version of my patch, and from what I sent
> > earlier today to the release team when asking about a potential unblock:
> > https://lists.debian.org/d
ebian.org/debian-release/2017/02/msg01033.html
I think we should wait for them to answer before doing anything else.
Based on KiBi's feedback I thought it better to swap sum[0] and sum[1],
and remove the SHA1 parsing also.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Descri
Control: tags -1 + patch
Hi,
The attached patch is based on having
libdebian-installer_bug856210_v3.patch applied:
* libdebian-installer4-dev would not change its name
* sum[1] is already empty/unusable
* sum[0] would become the sha256 field
Thanks,
Regards,
--
Steven Chamberlain
ste
Updated patch, which assumes the libdebian-installer4-dev package will
not be renamed. Build-Depend on a recent enough version that provides
sha256 fields.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index d6682ca..20e33a0 100644
--- a
Steven Chamberlain wrote:
> replace sum[0] with sha256 and leave sum[1] empty;
> [...] (we would drop the MD5- and SHA1-parsing code
> and make absolutely sure nobody is still using those).
The new patch attached would do that, and it remains otherwise
ABI-compatible.
It aims to be
Thanks for your comments!
Cyril Brulebois wrote:
> Steven Chamberlain (2017-02-27):
> > (If we really wanted, we could maybe avoid the ABI bump: [...]
>
> Given the number of reverse dependencies, I doubt this is worth abusing
> md5 storage for sha256 things.
Maybe I should
which remains the same length). The
dynamically-sized buffer it points to, would change from storing an MD5
to a SHA256 hash, and would only cause a regression where something is
still trying to validate MD5).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/configure.ac b/configure.ac
Steven Chamberlain wrote:
> Attached is [...]
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/anna.c b/anna.c
index 4b68816..e03d34a 100644
--- a/anna.c
+++ b/anna.c
@@ -318,8 +318,8 @@ install_modules(di_packages *status, di_packages *packages) {
}
}
-
ncrease it if changing SHA256 to SHA512 in the future. A
more thorough rework of this code might store the hash type (as an enum)
and length, in the di_package struct instead.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
entation needed
to change then.
In the ideal world, the code itself would be the clear, authoritative
reference of what it is doing. I wish that we can remove all references
to md5 and sha1 there.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
hed log.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
/usr/bin/sha256sum /tmp/net-retriever-1817-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/md5sum /var/cache/a
Hi,
Bastian Blank wrote:
> This change breaks the existing ABI and therefor needs an ABI bump, but
> it is missing from the patch.
I agree, that should be done. Thanks.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
bizarre that we've published SHA256 sums in the
archive since 2007 and *still* don't use them here. I think there is a
greater risk that we forget, or be too lazy, than we do this 'too soon'.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
t use
the md5sums field, and the struct size is not changing); though if they
do use, I'd prefer they FTBFS so that we find out.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
nd the testsuite to check parsing of the
SHA256 fields; that also would result in a larger diff however.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index 3dd29e1..1b7fcd8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,16 @@
l
9
if (item->sum[1])
return check_sum (target, "sha1sum", item->sum[1], buf_name);
if (item->sum[0])
return check_sum (target, "md5sum", item->sum[0], buf_name);
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/Insta
p (buf, sum, 32))
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
supported release until 2022. So
I'm tentatively filing this bug as RC-severity.
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
until 2022. So
I'm tentatively filing this bug as RC-severity.
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
lerDebacle
This bug is not itself RC, but it will be a blocking issue for RC bugs
I'm about to file.
I intend to submit a patch for this shortly.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
m_bus_socket: No such file or directory)
Did you try rebooting the machine before starting Xorg? Perhaps you
could find something relevant in your logs with:
$ cd /var/log && sudo grep dbus dpkg.log syslog
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
27;t yet have arm64 support; that
will happen in time.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
(again) to build it on linux.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
or is fatal, and
causes a "fail-whale" with only an option to log out.
Probably GNOME is not suitable for that hardware, then. It was a really
unfortunate experience for the (first-time) user, though.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Package: src:mame
Version: 0.178-1
Severity: serious
Justification: FTBFS, but built successfully in the past
Hi,
On linux-arm64, mame since 0.176-3 FTBFS, because:
https://buildd.debian.org/status/fetch.php?pkg=mame&arch=arm64&ver=0.178-1&stamp=1475578747
| Compiling src/emu/emumem.cpp...
| g++
nything using it; it's really a
standalone tool for developers (or could make a good Debian c-i test
someday).
Ironically, there is the same name conflict in upstream FreeBSD:
http://www.freebsd.org/cgi/man.cgi?query=ztest
(the only manpage found, refers to zutils' ztest).
Regards,
--
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u3
Severity: grave
Tags: security
https://security.FreeBSD.org/advisories/FreeBSD-SA-16:19.sendmsg.asc
Incorrect argument handling in the socket code allows malicious local
user to overwrite large portion of the kernel memory.
This affects
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u3
Severity: grave
Tags: security
https://security.FreeBSD.org/advisories/FreeBSD-SA-16:18.atkbd.asc
Incorrect signedness comparison in the ioctl(2) handler allows a
malicious local user to overwrite a portion of the kernel memory.
This aff
tag 820947 pending
thanks
Hello,
Bug #820947 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
http://git.debian.org/?p=pkg-samba/samba.git;a=commitdiff;h=6e1e21e
---
commit 6e1e21e8e6a41d5267d41519bccee87011684b
g reliably on
kfreebsd. Thanks!
(There is still other madness, such as sub-makes seemingly hiding
stdout, only showing stderr and not the actual commands run).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--- debian/rules.orig 2016-04-11 20:28:53.529023000 +0100
+++ debian/rules 2016-04-11 21:34
1284_find_ports in -lieee1284... yes
And now of course the build only runs configure once, so it uses only
the unpatched configure.ac
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
.h.patch
> dpkg-source: info: applying revert_upstream_lib64.patch
> dpkg-source: info: applying fix-timestamp-race.patch
It patches vice-2.3.dfsg/configure.proto (what is that?) and not
configure.ac; and I imagine the latter one is being used now.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Package: xscreensaver
Version: 5.34-1
Severity: grave
Tags: upstream
Hi,
The upstream maintainer of xscreensaver has explicitly asked Debian
to stop shipping it, which is a shame of course:
https://www.jwz.org/blog/2016/04/i-would-like-debian-to-stop-shipping-xscreensaver/
It *is* still a free s
Package: haskell-http2
Version: 1.5.3-2
Severity: serious
X-Debbugs-Cc: debian-...@lists.debian.org
Hi,
Wookey wrote:
> +++ Steven Chamberlain [2016-04-01 10:31 +0100]:
> > Currently haskell-http2 FTBFS on only armel:
> > https://buildd.debian.org/status/package.php?p=hask
Oh sorry, I've just noticed the comment:
Debian Bug Tracking System wrote:
> # unconfuse bts
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Hi Andreas,
Debian Bug Tracking System wrote:
> > notfixed 814631 1:1.7.8-1
> Bug #814631 {Done: Steven Chamberlain }
> [src:xserver-xorg-video-siliconmotion] xserver-xorg-video-siliconmotion:
> FTBFS: src/smi.h:224:5: error: unknown type name 'IOADDRESS'
> No longer
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u2
Severity: grave
Tags: upstream patch
A local unprivileged user could trigger a kernel panic or DoS attack
on kfreebsd-amd64 via sysarch(2) sysctls:
https://security.freebsd.org/advisories/FreeBSD-SA-16:15.sysarch.asc
This affects kfreebs
severity 720378 important
user debian-...@lists.debian.org
usertags 720378 + kfreebsd
thanks
Hi,
Sorry, I did not see this bug. It should have been downgraded because
kfreebsd and hurd are not release architectures.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description
Version: 10.3~svn296373-1
st above should be
employed.
One solution would be:
#define _DEFAULT_SOURCE /* for timegm() */
#define _XOPEN_SOURCE /* for strptime(), strdup() */
but with glibc >= 2.19 it is easier to define _GNU_SOURCE, which implies
both of those, and would be consistent with other source files
tags 815712 + patch
thanks
Hi Mathieu!
Would you like to try my patches (attached) to fix the testsuite on
32-bit x86? Possibly some other 32-bit systems will need to be listed,
although ARM seemed to be unaffected so far.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
Subject
t I'm working on a
patch.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
g from
libbsd-dev; this should be fairly straightforward to fix.
Thanks for the report,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u1
Severity: grave
Tags: security upstream
Control: found -1 10.1~svn274115-10
kfreebsd's TCP stack is vulnerable to local (and possibly remote under
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u1
Severity: grave
Tags: security upstream
Control: found -1 10.1~svn274115-10
kfreebsd's Linux binary compatibility layer (linux.ko module) may
vulne
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u1
Severity: grave
Tags: security upstream
Control: found -1 10.1~svn274115-10
kfreebsd's Linux binary compatibility layer (linux.ko module) may be
vu
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u1
Severity: grave
Tags: security upstream
Control: found -1 10.1~svn274115-10
Specially crafted SCTP packets via IPv6 can trigger remote denial of
se
P software, freely available from
| <http://www.php.net/software/>".
The statement is reproduced in the Debian copyright file, and it seems
valid, if it really does include PHP software as claimed by upstream.
[0]: https://github.com/stefanesser/suhosin/issues/48
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
g/712848) but that may be fixed in a few days.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Package: kglobalaccel
Version: 5.13.0-1
Severity: serious
Hi,
kglobalaccel/5.13.0-1 FTBFS on a few architectures:
kfreebsd-i386, ppc64, and x32 for example:
| The following configuration files were considered but not accepted:
|/usr/lib/i386-kfreebsd-gnu/cmake/KF5Crash/KF5CrashConfig.cmake,
Package: kfreebsd-10
Version: 10.1~svn274115-9
Severity: grave
Tags: security upstream patch
Hi,
Local users can trigger a kernel panic, or possibly escalate privileges,
by exploiting a flaw in the IRET handler in kfreebsd-9 and -10:
https://www.freebsd.org/security/advisories/FreeBSD-SA-15:21.am
nks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
pis.com/auth/chromewebstore"; and
talking about "silent installation". It relates to Cast API and
hopefully is unused in Debian builds (I don't see this file in the
Debian package build logs).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Steven Chamberlain wrote:
> would the
> DFSG chromium browser be 'more' free if it disabled NaCl?
Actually, in the build log I see disable_nacl=1
I'm confused that hotword-x86-64.nexe is "a NaCl module" [0], even
though Debian's chromium is built with NaCl &#x
#x27;s still no single sign of properly visible announcements to
> user what might have happened here. :(
The bug made it to Hacker News, so that has been accomplished now
to some extent. Thanks Chris for speaking up about this.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Paul Wise wrote:
> On Sun, 14 Jun 2015 15:07:01 +0100 Steven Chamberlain wrote:
> > I think we should rather be using if=virtio now anyway. Could we try
> > to switch falla to that, and hopefully the issue might go away?
>
> Switched to that:
>
> gnt-instance shut
Julien Cristau wrote:
> On Sun, Jun 14, 2015 at 15:07:01 +0100, Steven Chamberlain wrote:
> > I'm just curious what qemu-kvm version is used on falla's KVM host?
> > As 1.1.2+dfsg-6+deb7u8 in wheezy had some issues.
> >
> It's 1:2.1+dfsg-12+deb8u1.
Thanks.
help for issues like this.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Steven Chamberlain wrote:
> Paul Wise wrote:
> > The VM console looks like this afterwards:
> > https://people.debian.org/~pabs/tmp/falla.png
>
> Very helpful, thanks. It's a disk I/O problem (with emulated IDE
> disks); vfs is unable to flush I/O to ada0s1.
I thi
at doesn't look related to the kernel messages pabs showed (though the
effect on sshd is the same). I have seen it long ago with kfreebsd-9:
https://bugs.debian.org/705126
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
e (vm_fault)
and that also suggests there was memory pressure that maybe contributed
to this bug occurring.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
/network/interfaces (em0 -> vtnet0).
I think we ought to do this anyway for the buildds and porterboxes?
Furthermore it may avoid the stability issue (if that was related
to the emulated IDE disk or e1000 NIC).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
rted before kfreebsd-10; grub2 still needs a
patch to install to the latter as a boot disk).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ng,
or something else? Does it still respond to pings, does sshd still
respond, etc.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
sc
There were changes in that header for arch-specific handling of outb()
and friends. This could be a regression; or possibly wrong definitions
were used before (allowing it to build when it should not have).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE,
been running kfreebsd-9 with these patches for some weeks, and
they are applied already to kfreebsd-10 in sid/jessie-kfreebsd.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff -Nru kfreebsd-9-9.0/debian/changelog kfreebsd-9-9.0/debian/changelog
--- kfreebsd-9-9.0/debian/changelog 20
27;s s390x
porterbox, which successfully compiles a small C or C++ executable now.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
From: Steven Chamberlain
Date: Sun, 10 May 2015 19:46:59 +0100
Subject: support Debian s390x multiarch paths
--- a/clang/lib/Driver/ToolChains.cpp
+++ b/clang/
ll have a jessie-kfreebsd suite, where we patch this
package to do exactly that.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
bian-style multiarch
paths in this later section:
https://sources.debian.net/src/llvm-toolchain-3.5/1:3.5-10/clang/lib/Driver/ToolChains.cpp/#L2899
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
found 779195 kfreebsd-10/10.1~svn274115-3
notfixed 779195 kfreebsd-10/10.1~svn274115-3
thanks
A new version of the patch was issued in revision 1.1 of the advisory.
It seems the original patch did not entirely fix the bug.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE
Package: src:kfreebsd-10
Version: 10.1~svn274115-3
Severity: grave
Tags: security
Hi,
A local-network DoS was reported in the IPv6 stack of FreeBSD:
https://www.freebsd.org/security/advisories/FreeBSD-SA-15:09.ipv6.asc
(the same issue as CVE-2015-2922 on Linux).
This affects all our kfreebsd-8,
ture@lz4_compress=enabled -m none spool mirror /dev/sde
> /dev/sdf
Where did you find these daily installer builds with ZFS support? And
what instructions did you follow? (The documentation should be updated
with the information above).
I'll be committing a fix for #775395 in partman-zfs s
Package: src:kfreebsd-10
Version: 10.1~svn274115-2
Severity: grave
Tags: security upstream patch
Hi,
A remote DoS was reported in FreeBSD's IGMP packet handling:
https://www.freebsd.org/security/advisories/FreeBSD-SA-15:04.igmp.asc
This affects all our kfreebsd-8, -9, -10 and -11 packages.
I do
Package: src:kfreebsd-10
Version: 10.1~svn274115-2
Severity: grave
Tags: security upstream patch
Control: found -1 kfreebsd-10/10.0-3
Hi,
An unprivileged local user can trigger an out-of-bounds memory
access in the kernel via an ioctl to vt(4) (aka. newcons).
https://security.FreeBSD.org/patches/
Since this is a kfreebsd-any package, and we're not part of the
official stable release, I have to lower this to non-RC severity.
We should still fix it for the GNU/kFreeBSD release though.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-re
efault to using
"-d" (disabling new features including LZ4 metadata compression).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: kfreebsd-10
Version: 10.1~svn274115-1
Severity: grave
Tags: security patch
Hi,
A unprivileged local DoS was reported in the FreeBSD kernel
implementation of SCTP:
https://security.freebsd.org/advisories/FreeBSD-SA-15:03.sctp.asc
This only affects systems serving SCTP connections. A pat
Package: kfreebsd-10
Version: 10.1~svn274115-1
Severity: grave
Tags: security patch
Hi,
A kernel memory disclosure/corruption vulnerability was announced,
in the FreeBSD kernel's implementation of SCTP:
https://security.FreeBSD.org/advisories/FreeBSD-SA-15:02.kmem.asc
This could affect the kfree
imposter would simply attach an old, legitimately signed mail from
the sender to be spoofed, and enigmail would make the whole mail appear
to be genuine.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: OpenPGP digital signature
kfreebsd-8 (= 8.3-6+deb7u1), kfreebsd-9 (= 9.0-10+deb70.7)
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
is https://bugs.debian.org/594684
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Steven Chamberlain wrote:
> For FreeBSD I came up with the attached, hackish workaround
> using SO_TYPE (widely available), and out of the available
> protocols in PF_LOCAL (= AF_UNIX), assume that only
> SOCK_{DGRAM,SEQPACKET,STREAM} are candidates for fd passing.
Actually it
Linux and Solaris.
For FreeBSD I came up with the attached, hackish workaround
using SO_TYPE (widely available), and out of the available
protocols in PF_LOCAL (= AF_UNIX), assume that only
SOCK_{DGRAM,SEQPACKET,STREAM} are candidates for fd passing.
Perhaps someone has a better idea?
Regards,
--
nd fixing so quickly.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: src:kfreebsd-9
Version: 9.0-10+deb70.7
Severity: grave
Tags: security patch upstream
Hi,
kfreebsd 9.0 (not officially supported upstream) seems vulnerable to an
issue just announced in 9.1 and later:
http://security.FreeBSD.org/advisories/FreeBSD-SA-14:25.setlogin.asc
kfreebsd-8 8.3 in
tags 766250 + wheezy
thanks
Hi,
There seems to be no problem with this on a jessie system. I'm
still leaving this 'gift' bug if someone would like practice at
simple debugging on kfreebsd.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to
>&1
You may want to pipe that through `gzip --best` and attach it to this
bug report. Thanks.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
forwarded 767583 freebsd-driv...@lists.freebsd.org
thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RSION_9* macros, prefixed the chipset numbers with the
abbreviated name of the manufacturer (AR or QCA), I think we'd have all
that's needed to still compile the FreeBSD driver.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@
tags 767287 + patch
thanks
Hi,
Arno Töll wrote:
> On 30.10.2014 00:10, Steven Chamberlain wrote:
> > I guess the .install file may have some kind syntax to mark that file
> > [linux-any]?
>
> Sadly not. However, we may find another way to get it build on kfreebsd.
Then h
* ToDo: Linux specific */
| #include
| #include
I guess the .install file may have some kind syntax to mark that file
[linux-any]?
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: OpenPGP digital signature
suite=unstable
I don't think it has ever built before on kfreebsd so, I don't think
that could be an RC bug either?
https://buildd.debian.org/status/logs.php?pkg=jinput&arch=kfreebsd-amd64
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-re
a47c62
>
> I can try to confirm if that was the fix for the problem, else I guess
> we can assume that the problem was in a build dependency.
I don't think it matters; I don't see much point keeping the bug open,
unless the problem comes back?
Regards,
--
Steven Chamberl
Package: chiark-utils
Version: 4.4.0
Severity: serious
Hi,
chiark-utils fails to build acctdump.c on kfreebsd because:
* #include on kfreebsd must be preceded by
#include (for some integer typedefs)
* kfreebsd's acct.h does not have a struct acct_v3 anyway,
that is Linux-specific
Package: owfs
Version: 2.9p8-3
Severity: serious
Tags: patch
Hi,
owfs still FTBFS on kfreebsd...
In freebsd.patch, the #ifdefs need to be __FreeBSD_kernel__ instead.
Please see attached. Then it builds fine on kfreebsd-amd64.
(You have only 15 minutes left until dinstall though).
-- System In
1 - 100 of 718 matches
Mail list logo
