Bug#709279: astromenace: Fails to install on kfreebsd-i386: *** stack smashing detected ***: /usr/games/AstroMenace terminated

Package: astromenace
Severity: important
Version: 1.3.1+repack-1
User: debian-bsd <at> lists.debian.org
Usertags: kfreebsd

Hi,

installation of astromenace fails on kfreebsd-i386 Sid as follows:

Setting up astromenace (1.3.1+repack-1) ...
`/usr/share/fonts/truetype/freefont/FreeMonoBold.ttf' -> `RAW_VFS_DATA/FONT/FreeMonoBold.ttf'
`/usr/share/fonts/truetype/freefont/FreeSansBold.ttf' -> `RAW_VFS_DATA/FONT/FreeSansBold.ttf'
`/usr/share/fonts/truetype/freefont/FreeSerifBold.ttf' -> `RAW_VFS_DATA/FONT/FreeSerifBold.ttf'
`/usr/share/fonts/truetype/liberation/LiberationMono-Bold.ttf' -> `RAW_VFS_DATA/FONT/LiberationMono-Bold.ttf'
`/usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf' -> `RAW_VFS_DATA/FONT/LiberationSans-Bold.ttf'
`/usr/share/fonts/truetype/liberation/LiberationSerif-Bold.ttf' -> `RAW_VFS_DATA/FONT/LiberationSerif-Bold.ttf'
`/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf' -> `RAW_VFS_DATA/FONT/DejaVuSans.ttf'
AstroMenace 1.3.1 121212

Source Raw Folder: ./RAW_VFS_DATA/
VFS file was opened ./RAW_VFS_DATA/MODELS/models.pack
*** stack smashing detected ***: /usr/games/AstroMenace terminated
Aborted
dpkg: error processing astromenace (--configure):
 subprocess installed post-installation script returned error exit status 134
Errors were encountered while processing:
 astromenace

"uname -a" reports: GNU/kFreeBSD metisse 9.0-2-686 #0 Sat Nov 24

Upstart & kFreeBSD port for Debian

On 21 May 2013 21:53, Lucas Nussbaum <lucas <at> debian.org> wrote:
> Hi,
>
> On 20/05/13 at 18:19 +0200, Michael Stapelberg wrote:
>> Hello,
>>
> - Neither systemd nor upstart are likely to be ported to kfreebsd soon,
>   as they both rely on many Linux-specific features and interfaces.
>

Well, Colin Watson, Matthias Klose, Steve Langasek, James Hunt and I
have discussed the state of the kfreebsd possibility a few times over
the past year or so.

It boiled down to: if we have waitid & inotify it should be possible
to have a reasonable stab at doing a kfreebsd port for the system-wide
upstart init (with libnih and mountall). For session init we currently
do use prctl to set subreaper, but one can still have session upstart
init without that syscall.

Was there something else needed? Or can anyone else spot other "big
incompatible" chunks of code?

As it happens, waitid has been recently implemented in the FreeBSD 9.1
kernel [1]. While inotify is not-essential, it's still very nice to
have and it can be reasonably & sufficiently be implemented for
upstart's needs using FreeBSD's kqueue/kevent.

It was also roughly felt that code base can be kept reasonably tidy by
using weak symbols to encapsulate bsd/linux specific parts of the code

Bug#699208: some more

Hi!

  Just noticed: stopping mpd works fine *unless* it's during the
upgrade. I'll look into it.

  Christoph

Some more information:
--
christoph <at> mitoraj {1} ~ 
23:25 0 % sudo start-stop-daemon --stop --oknodo --retry 5 --pidfile /run/mpd/pid --exec /usr/bin/mpd 
No /usr/bin/mpd found running; none killed.
christoph <at> mitoraj {1} ~ 
23:25 0 % ps auxf | grep mpd
1000      5772  0.0  0.0   9108  1548 ?        S+   23:25   0:00              \_ grep mpd
mpd       4657  0.0  0.1 365148 15628 ?        Ss   23:24   0:00 /usr/bin/mpd /etc/mpd.conf
christoph <at> mitoraj {1} ~ 
23:25 0 % cat /run/mpd/pid
4657
--

Wild guess:

start-stop-daemon on bsd acting weird iff the actual binary on
/usr/bin/mpd (--exec) is not the same (inode-wise) as the running
one.

Open question:

Why does it work on linux just fine / is only mpd breaking on *kbsd

i386 install, Keyboard/Mouse unresponsive

Bug#709225: jail(8) manpage describes absent jls(8) utility

Package: freebsd-utils
Version: 9.0+ds1-10
Severity: minor
File: /usr/share/man/man8/jail.8.gz

which is unfortunate

FWIW jls is also provided by sleuthkit and obviously it has nothing to do with
bsd jails

-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 9.0-1-amd64
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages freebsd-utils depends on:
ii  libbsd0     0.4.2-1
ii  libc0.1     2.13-38
ii  libcam6     9.0+ds1-4
ii  libgeom1    9.0+ds1-4
ii  libjail1    9.0+ds1-4
ii  libkiconv4  9.0+ds1-4
ii  libkvm0     9.0+ds1-4
ii  libsbuf6    9.0+ds1-4
ii  libtirpc1   0.2.2-5
ii  lsb-base    4.1+Debian8
ii  zlib1g      1:1.2.7.dfsg-13

freebsd-utils recommends no packages.

Versions of packages freebsd-utils suggests:
pn  freebsd-hackedutils  <none>
ii  kbdcontrol           9.0+ds1-10
ii  vidcontrol           9.0+ds1-10

-- no debconf information

Bug#709219: /etc/pf.conf refers to non-existing /usr/share/examples/pf (should be /usr/share/doc/pf/examples/)

Package: pf
Version: 9.0+ds1-10
Severity: minor
File: /etc/pf.conf

cheers

-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 9.0-1-amd64
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pf depends on:
ii  libbsd0  0.4.2-1
ii  libc0.1  2.13-38

pf recommends no packages.

pf suggests no packages.

-- no debconf information

Bug#709183: librep: FTBFS on kfreebsd-amd64

Package: librep
Version: 0.90.2-1.3
Tags: patch
User: debian-bsd <at> lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-bsd <at> lists.debian.org
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

librep failed to build on kfreebsd-amd64 due to:

https://buildd.debian.org/status/fetch.php?pkg=librep&arch=kfreebsd-amd64&ver=0.90.2-1.3%2Bb1&stamp=1368142762
> checking for stack growth direction... upwards
[...]
>  ** error: --with-stack-direction is incorrect; it should be -1

The detection in ./configure can be wrong on amd64 or kfreebsd-amd64
depending on GCC version and optimisation level (especially gcc >= 4.7
and -O2).

debian/rules forces -O0 for (Linux) amd64, but not kfreebsd-amd64.
Please consider matching on HOST_CPU instead of just HOST, then it
will work for kFreeBSD as on Linux:

--- librep-0.90.2.orig/debian/rules     2013-05-21 12:26:06.000000000 +0100
+++ librep-0.90.2/debian/rules  2013-05-21 13:06:05.914135127 +0100
 <at>  <at>  -21,7 +21,7  <at>  <at> 
        CFLAGS = -Wall -g -O0
 endif

-ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH),amd64))
+ifeq ($(DEB_HOST_ARCH_CPU),$(findstring $(DEB_HOST_ARCH_CPU),amd64))
        CFLAGS = -Wall -g -O0
 endif

I've tested that this fixes the result of the configure test, and
results in a successful build.

Thank you.

-- System Information:
Debian Release: 7.0
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

buildd failure: /tmp full?

Hi Christoph,

Package wmnd had an interesting build failure on fano:

https://buildd.debian.org/status/fetch.php?pkg=wmnd&arch=kfreebsd-amd64&ver=0.4.17-1&stamp=1369120011
> checking for mawk... mawk
> ../configure: line 2984: cannot create temp file for here-document: No space left on device
> checking whether make sets $(MAKE)... no
> ../configure: line 3042: cannot create temp file for here-document: No space left on device
> ../configure: line 3047: cannot create temp file for here-document: No space left on device
> checking for gcc... gcc
> ../configure: line 3417: cannot create temp file for here-document: No space left on device

I think that relates to /tmp which is probably tmpfs?  Is it actually
full, or has it perhaps shrunk in size due to memory exhaustion?  That
sounds like bug #666747 could be affecting kfreebsd 8.1.

Not sure if unmounting/remounting /tmp would fix it or if a reboot is
necessary.  But please give back wmnd to rebuild sometime (was okay on
kfreebsd-i386).

Thanks!
Regards,
--

-- 
Steven Chamberlain
steven <at> pyro.eu.org

Re: [Openjdk] Bug#708818: Updated kFreeBSD support

Hi Matthias, hi kFreeBSD porters,

On Sun, May 19, 2013 at 12:38:50PM +0200, Matthias Klose wrote:
> Am 18.05.2013 19:36, schrieb Guido Günther:
> > Package: openjdk-7
> > Version: 7u21-2.3.9-4
> > Severity: wishlist
> > Tags: patch
> > 
> > Hi,
> > attached patch updates Damien's OpenJDK support for kFreeBSD. I'd be
> > great to have these available in the archive since it allows to run
> > kFreeBSD Jenkins slaves which hopefully will give us more automated
> > testing.

https://buildd.debian.org/status/fetch.php?pkg=openjdk-7&arch=kfreebsd-amd64&ver=7u21-2.3.9-5&stamp=1368925285

I can't reproduce the segfault on the buildd in a current kFreeBSD
chroot. The command only invokes ldd and readelf and looking at the
build machine it seems its glibc is outdated:

	libc-bin: already installed (2.13-38)

while sid has 2.17-3. 

 <at> porters: can the buildds be updated so we can respin the build?
Cheers,
 -- Guido

--

-- 
To UNSUBSCRIBE, email to debian-bsd-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org
Archive: http://lists.debian.org/20130520115914.GA18538 <at> bogon.sigxcpu.org

Re: Bug#704227: pu: freebsd-utils/9.0+ds1-11

"Adam D. Barratt" <adam <at> adam-barratt.org.uk> writes:
> On Sun, 2013-05-12 at 18:50 +0100, Steven Chamberlain wrote:
>> This went into sid with version 9.0+ds1-11 and has migrated to jessie.
>> 
>> For a pu upload, would the version number have to be 9.0+ds1-11+deb7u1 ?
>
> The version needs to be lower than that in testing, so either -10+deb7u1
> or -11~deb7u1.

Hi Steven!

  How's this going? Do you need someone to upload? Just trying to make
sure this doesn't become last minute for no reason 

   Christoph

--

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer

Bug#632832: ufsutils: growfs.ufs do not work

The same problems exists in ufsutils/8.2-3. Please find attached a patch
for the aforementioned version that addresses this issue.

Regards,
Nikos