Steven Chamberlain | 30 Sep 00:00 2014

Re: Bug#755105: kadu: no longer builds on kfreebsd-*

tags 755105 + patch
user debian-bsd <at> lists.debian.org
usertags 755105 + kfreebsd
thanks

Hi,

The shared library libantistring.so seems to be built fine on kfreebsd,
and the build system gives it a multiarch path.  But dh_install later
looks for it in the wrong place...

> /usr/bin/c++  -fPIC -std=c++0x -O3 -DNDEBUG   -shared -Wl,-soname,libantistring.so -o
libantistring.so CMakeFiles/antistring.dir/antistring.cpp.o
CMakeFiles/antistring.dir/antistring-configuration.cpp.o
CMakeFiles/antistring.dir/antistring-configuration-ui-handler.cpp.o
CMakeFiles/antistring.dir/antistring-notification.cpp.o
CMakeFiles/antistring.dir/antistring-plugin.cpp.o
CMakeFiles/antistring.dir/antistring_automoc.cpp.o ../../kadu-core/libkadu.so
-lQtDeclarative -lQtScript -lQtSvg -lQtWebKit -lQtXmlPatterns -lQtGui -lQtDBus -lQtXml -lQtSql
-lQtNetwork -lQtCore 
[...]
> -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-kfreebsd-gnu/kadu/plugins/libantistring.so
[...]
> dh_install -s
> cp: cannot stat 'debian/tmp/debian/tmp/usr/lib/kadu/plugins/libantistring.so': No such file or directory
> dh_install: cp -a debian/tmp/debian/tmp/usr/lib/kadu/plugins/libantistring.so
debian/kadu//usr/lib/kadu/plugins/ returned exit code 1

This is apparently due to some workaround that was added to debian/rules
but is now not needed.  Please see attached patch fixing this.
(Continue reading)

Debian testing watch | 29 Sep 18:39 2014
Picon

partman-zfs 38 MIGRATED to testing

FYI: The status of the partman-zfs source package
in Debian's testing distribution has changed.

  Previous version: 37
  Current version:  38

--

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

Jörg Frings-Fürst | 28 Sep 10:02 2014
Picon

KFreebsd-* and linux/usbdevice_fs.h

Hello,

on KFreebsd-* I have a bug[1] because the source need the
linux/usbdevice_fs.h, which not exist.

Is there a other package that implant the requested functions?

Or any other hint?

Many thanks.

CU
Jörg

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762773

--

-- 
pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8  EBCB 422B 44B0 BE58 1B6E
pgp Key: BE581B6E
CAcert Key S/N: 0E:D4:56

Jörg Frings-Fürst
D-54526 Niederkail

Threema: SYR8SJXB

IRC: j_f-f <at> freenode.net
     j_f-f <at> oftc.net

(Continue reading)

Steven Chamberlain | 28 Sep 03:01 2014

Bug#763126: efl: [kfreebsd] testsuite sometimes fails

Package: efl
Version: 1.8.6-2.1
Severity: important
User: debian-bsd <at> lists.debian.org
Usertags: kfreebsd

Hi,

The efl testsuite fails occasionally, most often on kfreebsd with:

https://buildd.debian.org/status/fetch.php?pkg=efl&arch=kfreebsd-i386&ver=1.8.6-2.1&stamp=1411656315https://buildd.debian.org/status/fetch.php?pkg=efl&arch=kfreebsd-i386&ver=1.8.6-2.1&stamp=1411656315
| FAIL: tests/ecore/ecore_suite
| =============================
| 
| Running suite(s): Ecore
| count_res: 6
| Client with ip 127.0.0.1, port 51294, connected = 1!
| Lost client with ip 127.0.0.1!
| Client was connected for 10.003 seconds.
| ERR<2889>:ecore_con lib/ecore_con/ecore_con_dns.c:90 _ecore_con_dns_check() resolve failed: No
such file or directory
| 95%: Checks: 21, Failures: 1, Errors: 0
| tests/ecore/ecore_test_ecore_con.c:88:F:Ecore_Con:ecore_test_ecore_con_server:0: Failed

I'm not sure what it tries to resolve, exactly.  A similar problem may
have been seen once before here on s390x:

https://buildd.debian.org/status/fetch.php?pkg=efl&arch=s390x&ver=1.8.3-1&stamp=1389286137
| FAIL: tests/ecore/ecore_suite
| =============================
(Continue reading)

Steven Chamberlain | 28 Sep 02:39 2014

Re: Bug#756916: vice: FTBFS[kfreebsd-amd64,powerpc]: error while opening "src/arch/win32/res.rc.po.c" for reading: No such file or directory

unarchive 725629
reopen 725629 =
notfixed 725629 vice/2.4.dfsg+2.4.6-1
retitle 725629 vice: sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading:
No such file or directory
retitle 756916 vice: sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading:
No such file or directory
forcemerge 756916 725629
thanks

Hi,

This bug is the same as http://bugs.debian.org/725629, apparently
not really fixed.  That was seen on s390, and this has happened
more recently on powerpc too:
https://buildd.debian.org/status/logs.php?pkg=vice&arch=powerpc

I think it it is some kind of Makefile parallelism issue.  Compare
successful case:

https://buildd.debian.org/status/fetch.php?pkg=vice&arch=kfreebsd-amd64&ver=2.4.dfsg%2B2.4.6-2&stamp=1400020850
| Making all in po
| make[2]: Entering directory '/«BUILDDIR»/vice-2.4.dfsg+2.4.6/po'
| gcc -I.. -I../intl -g -O3   -Wall -Wno-inline ./intl2po.c -o intl2po
| ( if test 'x.' != 'x.'; then \
|     posrcprefix='../'; \
|   else \
|     posrcprefix="../"; \
|   fi; \
|   rm -f POTFILES-t POTFILES \
(Continue reading)

Jan Henke | 27 Sep 19:33 2014
Picon

Kernel packages in the installer

Hi folks,

I have been talking with Christoph on IRC about the kernel installation
story. Right now there are several kernel packages in the archive. The
installer currently installs kfreebsd-image-$KERNEL_MAJOR-$ARCH
(http://anonscm.debian.org/cgit/d-i/base-installer.git/tree/kernel/kfreebsd-amd64.sh),
which is e.g. kfreebsd-image-10-amd64 currently with testing. But there
are also the kfreebsd-image-{amd64, 686, 486} packages, which just
depend on the respective major version image package.

It seems possible for the future to make distribution updates easier, if
the installer does not install a major version image packet directly,
but if it installs the meta packet only and via dependency the current
major version image packet is pulled. That obviously does not help with
current installations, but it would prevent a similar problem in the future.

So I propose to change the Debian installer to install the version
agnostic (wonderful word, thanks Christoph) meta-package and let the
dependency resolution pull in the correct kernel image. How is the
general feeling about this?
--

-- 
Best regards,
Jan

Steven Chamberlain | 27 Sep 14:33 2014

Re: Bug#610885: default install fails on kfreebsd-amd64

Source-Version: 165

This was fixed in wheezy!

Regards,
--

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

Steven Chamberlain | 27 Sep 14:12 2014

Re: Bug#753773: consolekit: FTBFS on kfreebsd-any

reassign 753773 src:kfreebsd-kernel-headers
affects 753773 consolekit
found 753773 kfreebsd-kernel-headers/9.2~8
fixed 753773 kfreebsd-kernel-headers/10.0-7
close 753773
user debian-bsd <at> lists.debian.org
usertags 753773 + kfreebsd
thanks

Hi,

This was a problem in kfreebsd-kernel-headers fixed long ago.  Built
successfully when given back for rebuild.

Regards,
--

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

Steven Chamberlain | 27 Sep 03:35 2014

Please give back consolekit on kfreebsd-*

Hi,

Please give back consolekit to build on kfreebsd-amd64 and
kfreebsd-i386;  it had a kfreebsd-kernel-headers problem (Bug #753773)
which I think was fixed already in 10.0 userland.  I was able to
build 0.4.6-5 locally.

Thanks,
Regards,
--

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

Steven Chamberlain | 27 Sep 03:17 2014

Re: Bug#728223: dime: FTBFS on kFreeBSD: libtool can't build shared libraries

tags 728223 + patch
thanks

Hi,

The minimal patch below will fix the FTBFS on kfreebsd:

--- configure.orig
+++ configure
 <at>  <at>  -6614,7 +6614,7  <at>  <at> 
   esac
   ;;

-gnu*)
+k*bsd*gnu|gnu*)
   version_type=linux
   need_lib_prefix=no
   need_version=no

Although, really it should be regenerating ./configure as part of the
build.  (That is #727358 I think)

Thanks,
Regards,
--

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

Steven Chamberlain | 27 Sep 00:52 2014

Please give back dime on kfreebsd-*

Hi,

Please give back dime to build on kfreebsd-amd64 and kfreebsd-i386;  it
had some autotools issues but seems to build okay for me right now.

If it does build, #728223 can be closed, it can migrate and escape
autoremoval.  In any case there is still #727358 open suggesting the use
of dh-autoreconf.

Thanks,
Regards,
--

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


Gmane