On Mon, Apr 11, 2016 at 18:23:26 +0200, Guido Günther wrote:
> On Mon, Apr 11, 2016 at 05:21:39PM +0200, Michael Tautschnig wrote:
[...]
> > I'm afraid I don't fully understand. So, yes, I'm building using pbuilder
> > (and
> > I'm not aware of any reaso
Package: doxia
Version: 1.1.4-5
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
[INFO]
[INFO]
Hi,
On Mon, Apr 11, 2016 at 9:19:42 +0200, Guido Günther wrote:
[...]
> I think this only happens when pbuilder builds the source package. Building
> with "-nc" will work around this. It builds fine once you pass a clean
> source package to into the chroot.
I'm afraid I don't fully understand. S
Package: php-dompdf
Version: 0.6.2+dfsg-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
Copying /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf to
/srv/jenkins-sla
Package: libu2f-server
Version: 1.0.1-1.1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
make[2]: Entering directory
'/srv/jenkins-slave/workspace/sid-goto-cc-libu2
Package: python-cliff
Version: 1.15.0-3
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
dpkg-buildpackage: host architecture amd64
fakeroot debian/rules clean
pyvers
Package: libu2f-host
Version: 1.0.0-1.1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
make[3]: Entering directory
'/srv/jenkins-slave/workspace/sid-goto-cc-libu2f-
Package: python-sphinx
Version: 1.3.6-2
Severity: serious
Justification: breaks build of depending packages
While trying to build packages such as barbican or horizon in a clean chroot,
they would fail with:
debian/rules override_dh_sphinxdoc
make[1]: Entering directory
'/srv/jenkins-slave/wo
Package: cross-toolchain-base
Version: 9
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
debian/rules build
linux: 4.4.6-1 / 4.3.3-7cross2
glibc: 2.22-5 / 2.21-6cros
Package: cross-toolchain-base-ports
Version: 2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
debian/rules build
linux: 4.4.6-1 / 4.3.3-7cross2
glibc: 2.22-5 / 2.21
Package: uima-as
Version: 2.3.1-5
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
[ERROR] Failed to execute goal on project uimaj-as-core: Could not resolve
dependen
Package: virt-manager
Version: 1:1.3.2-3
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
I: Running /usr/bin/dpkg-buildpackage -rfakeroot -us -uc ${DEBBUILDOPTS}
dpkg
Package: comix
Version: 4.0.4-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
# Add here commands to install the package into debian/comix.
mkdir -p
/srv/jenkins-s
Package: r-cran-arm
Version: 1.8-6-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
dh_installdirs usr/lib/R/site-library
echo "R:Depends=r-base-core (>= 3.
Package: ruby-rspec-expectations
Version: 2.14.2-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
/usr/bin/ruby2.2 /usr/bin/gem2deb-test-runner
┌───
Package: ruby-rspec-core
Version: 2.14.7-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
/usr/bin/ruby2.2 /usr/bin/gem2deb-test-runner
┌───
Control: severity -1 wishlist
Hi Andreas,
On Fri, Jan 29, 2016 at 12:51:57 +0100, Andreas Beckmann wrote:
[...]
> I could not reproduce this either.
> This looks a bit fishy, mixing different server versions.
> Did you have stale process running before the test?
>
> $ grep -E 'redis-server|Conne
Package: ruby-celluloid-fsm
Version: 0.20.0-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
┌───
Package: haskell-stack
Version: 0.1.10.0-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Attempting to parse the build-deps
-> Considering build-dep debhelper
Package: haskell-cabal-install
Version: 1.22.6.0-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep libghc-zlib-dev (>= 0.5.3)
-> Trying l
Package: cabal-debian
Version: 4.31-4
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep libghc-optparse-applicative-dev (>= 0.11)
-> Trying
Package: pkg-haskell-tools
Version: 0.10.1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Attempting to parse the build-deps
-> Considering build-dep debhelper
Package: wayland-protocols
Version: 1.0-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
debian/rules build
dh build --with autoreconf
dh_testdir
dh_update_a
Package: civicrm
Version: 4.7.1+dfsg-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep php-htmlpurifier
-> Trying php-htmlpurifier
-> Co
Package: ruby-pygments.rb
Version: 0.5.4~ds1-3
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
===
Package: ruby-rspec-mocks
Version: 2.14.5-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
┌─
Package: ruby-test-unit-context
Version: 0.5.0-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
=
Package: python-whoosh
Version: 2.7.0-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
tests/test_sorting.py ..
tests/test_spans.py .
Package: ruby-redis-store
Version: 1.1.6-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
┌──
Hi again,
On Tue, Jan 26, 2016 at 1:25:14 +, Michael Tautschnig wrote:
[...]
> > Are you able to tell me what the environment variables LC_CTYPE and
> > LC_ALL are set to during the failed boot?
> >
> > If this is the case I can fix the problem by unsetting these b
Hi,
Thanks a lot for chasing this up so quickly!
On Tue, Jan 26, 2016 at 12:04:59 +1100, Brian May wrote:
> Hello,
>
> We have a theory that this is due to LC_CTYPE and LC_ALL environment
> being set to legacy values.
>
Yes, I did notice that discussion on d-devel:
> Are you able to tell me w
Package: node-redis
Version: 0.12.1-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
addr=127.0.0.1:34379 fd=126 name= age=3046349 idle=793 flags=N db=0 sub=0
psub=
Package: nurpawiki
Version: 1.2.3-8
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
ocamlfind ocamlc -thread -g -syntax camlp4o -package
threads,netstring,calendar,e
Package: nose2
Version: 0.5.0-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
==
ERROR: test_col
Package: nbibtex
Version: 0.9.18-11
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
rubber --warn=all --verbose --ps nbib.tex
compiling nbib.tex...
executing: latex \
Package: neutron-lbaas
Version: 2015.1.0-3
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
===> Testing with python2.7 (python2)
+ rm -rf .testrepository
+ testr-pyth
Package: nitime
Version: 0.5-3
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
/usr/bin/make -C doc html
make[2]: Entering directory
'/srv/jenkins-slave/workspace/si
Package: mysql-connector-java
Version: 5.1.38-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep default-jdk (>= 2:1.8)
Tried versions:
Package: mpgtx
Version: 1.3.1-5
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
make[1]: Entering directory
'/srv/jenkins-slave/workspace/sid-goto-cc-mpgtx/mpgtx-1.3
Package: mira
Version: 4.9.5-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error. It should be noted
right away that this may be one of first attempts building with flex 2.6.
N
Package: maven-scm
Version: 1.3-7
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
---
T E S T S
-
Package: maven2
Version: 2.2.1-28
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
[java] [ERROR] BUILD ERROR
[java] [INFO]
Package: doc-base
Version: 0.10.6
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
make[2]: Entering directory
'/srv/jenkins-slave/workspace/sid-goto-cc-doc-base/doc-
Package: djangorestframework
Version: 3.3.2-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
# Build the HTML documentation.
mkdir
/srv/jenkins-slave/workspace/sid-
Package: dsc-statistics
Version: 201203250530-2.1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
/usr/bin/pod2man --section=8 --release="DSC " --lax \
--center="Debi
Package: mailfilter
Version: 0.8.3-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
Making all in src
make[3]: Entering directory
'/srv/jenkins-slave/workspace/sid-
Package: debian-policy
Version: 3.9.6.1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
make[1]: Entering directory
'/srv/jenkins-slave/workspace/sid-goto-cc-debian-
Package: debian-parl
Version: 1.0.9
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
make[1]: Entering directory
'/srv/jenkins-slave/workspace/sid-goto-cc-debian-parl
Package: devscripts
Version: 2.15.10
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
test_debuild
ASSERT:standard output of debuild --no-conf --no-lintian --preserve-
Package: doxia
Version: 1.1.4-5
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
[INFO]
[INFO]
Package: astyle
Version: 2.04-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
dh binary
dh_testdir
dh_update_autotools_config
dh_auto_configure
debian/r
Package: feh
Version: 2.14-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
make[2]: Entering directory
'/srv/jenkins-slave/workspace/sid-goto-cc-feh/feh-2.14/man'
Package: dogecoin
Version: 1.8.0-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
g++ -DHAVE_CONFIG_H -I. -pthread -pthread -I../src/obj -pthread
-I/usr/includ
Package: bpython
Version: 0.15-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
running compile_catalog
Traceback (most recent call last):
File "setup.py", line 29
Package: horae
Version: 071~svn537-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
debian/rules build
dh_testdir
/usr/bin/perl Build.PL
destdir=/srv/jenkins-slave
Package: datanommer.consumer
Version: 0.6.1-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd
/srv/je
Package: astroquery
Version: 0.2.4+dfsg-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
ERRORS ===
Package: commons-beanutils
Version: 1.9.2-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were enc
Package: cpluff
Version: 0.1.3-3
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
-Wdat
Package: hugo
Version: 0.15+git20160109.147.dd1d655-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
github.com/spf13/hugo/helpers
github.com/spf13/hugo/source
githu
Package: jenkins-remoting
Version: 2.45-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
[INFO] Scanning for projects...
[INFO]
[INFO] --
Package: jgit
Version: 3.7.1-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
---
T E S T S
Package: debian-design
Version: 3.0.1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep boxer-data (>= 10.3)
-> Trying boxer-data
-> Consi
Package: gbirthday
Version: 0.6.7-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep python-support
-> Trying python-support
-> Can
Package: hexbox
Version: 1.5.0-4
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep mono-gmcs
-> Trying mono-gmcs
-> Cannot install m
Package: antlr
Version: 2.7.7+dfsg-6
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep libmono-winforms2.0-cil
-> Trying libmono-winforms2.
Package: cross-gcc-4.9-ppc64el
Version: 54
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep gcc-4.9-source (= 4.9.3-5)
Tried versions:
Package: janest-core
Version: 113.00.00-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep libcore-kernel-ocaml-dev
-> Trying libcore-kern
Package: libindicate
Version: 0.6.92-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-> Considering build-dep mono-gmcs
-> Trying mono-gmcs
-> Cannot ins
Package: libimager-perl
Version: 1.004+dfsg-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
ok 68 - check error message
ok
Use of uninitialized value $msg in concat
Package: libfreecontact-perl
Version: 0.08-4
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
make[1]: Leaving directory
'/srv/jenkins-slave/workspace/sid-goto-cc-lib
Package: libproxool-java
Version: 0.9.1-8
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
test:
[echo] Running tests, this can take a few minutes.
[java] ..
Package: libsdl2-ttf
Version: 2.0.12+dfsg1-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
make[1]: Entering directory
'/srv/jenkins-slave/workspace/sid-goto-cc-li
Package: libsdl2-image
Version: 2.0.0+dfsg-3
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
/bin/bash ./libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"\"
-
Package: libtm-perl
Version: 1.56-7
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
# Failed test 'assertions applying to identical topics are found'
# at t/043d
Package: libconfig-model-dpkg-perl
Version: 2.071
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
Warning in 'source Standards-Version' value '3.8.4': Current standar
Package: libembperl-perl
Version: 2.5.0-4
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
In file included from ep.h:174:0,
from Embperl.xs:16:
./Old
Package: ganglia
Version: 3.6.0-6
Usertags: goto-cc
Tags: patch
Severity: serious
Justification: FTBFS
As of its version 1.5.4-3, rrdtool no longer Provides: librrd2-dev from
librrd-dev. This breaks the build of ganglia. Changing the build-dependency to
librrd-dev fixes this first problem.
The bu
Package: ntop
Version: 3:5.0.1+dfsg1-2.1
Usertags: goto-cc
Severity: serious
Justification: FTBFS
As of its version 1.5.4-3, rrdtool no longer Provides: librrd2-dev from
librrd-dev. This breaks the build of ntop. Changing the build-dependency to
librrd-dev should fix the problem.
Best,
Michael
Control: tags -1 +pending
Hi Simon,
On Mon, Sep 21, 2015 at 11:56:55 +0100, Simon McVittie wrote:
[...]
> I've only recently resumed mass-bug-filing; everyone who has been
> helping with this transition seems to have become somewhat burned-out
> after the first month or so, so opening the last fe
Hi Simon,
On Mon, Sep 21, 2015 at 8:16:30 +0100, Simon McVittie wrote:
[...]
> Background[1]: libstdc++6 introduces a new ABI to conform to the
> C++11 standard, but keeps the old ABI to not break existing binaries.
> Packages which are built with g++-5 from experimental (not the one
> from testi
Control: tags 780199 +patch
Hello,
This is just to confirm that the build is broken due to the same include guards
being used in different header files, as identified by James earlier.
The attached patch fixes the problem, although the choice of include guard
amendment is somewhat arbitrary.
Be
Hi,
On Sat, Nov 08, 2014 at 12:52:13 -0500, Reinhard Tartler wrote:
> That doesn't sound like a bad idea at all. I'm not sure if going via unstable
> or experimental is best at this point, but either way, this would allow us
> preparing a package that links against the system picosat again.
>
On Sat, Nov 08, 2014 at 12:52:13 -0500, Reinhard Tartler wrote:
> That doesn't sound like a bad idea at all. I'm not sure if going via unstable
> or experimental is best at this point, but either way, this would allow us
> preparing a package that links against the system picosat again.
>
[...]
On Sat, Nov 08, 2014 at 16:37:18 +0100, Stefan Hengelein wrote:
> Hi,
>
> we have an in-tree variant of the PicoSAT because the newer, reentrant
> version of picosat is around 30% slower for our usage than the one
> we're currently using (936).
> However, the picomus export is done for compatibili
:
> On Fri, 2014-11-07 at 08:30:39 +0000, Michael Tautschnig wrote:
[...]
> > I do agree with all the dpkg reasoning and in a way I'm grateful that dpkg
> > made
> > this bug surface. But really there shouldn't be any such dependency on the
> > order
>
Guillem, KiBi,
(It may be worthwhile taking a moment to read the bug logs of #766459 and
#767999.)
On Fri, Nov 07, 2014 at 8:34:49 +0100, Guillem Jover wrote:
> Control: severity -1 serious
> Control: retitle -1 dpkg: Correct fix breaks bogus assumptions in old
> debootstrap
>
I'd say the bug
Hi,
On Fri, Nov 07, 2014 at 1:02:18 +0100, Adam Borowski wrote:
> On Thu, Nov 06, 2014 at 10:32:34PM +0000, Michael Tautschnig wrote:
> > > I tested your patch when debootstrapping from squeeze, it did work.
> > > Should
> > > I test some more scenarios (cde
Hi,
On Thu, Nov 06, 2014 at 22:44:40 +0100, Adam Borowski wrote:
> On Thu, Nov 06, 2014 at 02:06:07PM +0000, Michael Tautschnig wrote:
[...]
> > 1. Determine whether base-passwd is in line with policy on providing its
> > functionality as an "essential" package
[ BCC'ing Santiago, Holger, Adam, Cyril ]
Hi all,
I'm refraining from quoting the preceding mails as most of you will have those
in their inbox, and I'd rather summarise the situation right here:
At least Santiago's and my opinion diverge on whether base-passwd is presently
in line with policy o
Hi Santiago, All,
On Tue, Oct 28, 2014 at 13:39:06 +0100, Santiago Vila wrote:
[...]
> I already tried to fix this problem yesterday in base-files by making
> minor changes. It didn't work.
>
> And it didn't work because contrary to what some people in this thread
> has suggested, this issue has
On Mon, Oct 27, 2014 at 16:36:42 +0100, Santiago Vila wrote:
[...]
> For example, your interpretation would force base-passwd to lose its
> essential flag, because it can't provide its core functionality only
> when in unpacked state. Then, according to policy, base-files and
> *every* other packag
On Mon, Oct 27, 2014 at 12:07:24 +0100, Santiago Vila wrote:
> On Mon, 27 Oct 2014, Michael Tautschnig wrote:
>
> > I'm hoping this is not going to be too philosophical, so I'll enlist the
> > facts
> > first (please let me know if I got any of them wrong):
Apologies if I may be repeating information as we were concurrently working on
those messages.
On Mon, Oct 27, 2014 at 11:34:06 +0100, Santiago Vila wrote:
[...]
> I just expect debootstrap maintainers to cooperate with the release
> managers to ensure that the version in stable is able to deboots
ila wrote:
> I'm going to reply to Julien first, then to Michael.
>
> On Mon, 27 Oct 2014, Julien Cristau wrote:
>
> > On Mon, Oct 27, 2014 at 08:35:14 +, Michael Tautschnig wrote:
> > I agree this should be fixed in base-files.
>
> Bugs should be fixed wher
Hi all,
I'm being heavily bitten by this one as well and I'm mildly shocked to see it
crop up this late in the release cycle. I'm not going to hide that I believe
this ought to be reassigned to base-files. I'll try to elaborate below.
Santiago Vila wrote:
[...]
> In this particular case, I belie
Hi undertaker maintainers/uploaders,
[...]
> Here is a list of files that are known to be shared by both packages
> (according to the Contents file for sid/amd64, which may be
> slightly out of sync):
>
> /usr/bin/picomus
>
[...]
I wasn't even aware that undertaker was in Debian, and the same
Hi,
> hmm, that's weird. I used sbuild for the package, and it builds fine
> here (just tested again).
> I'm curious, what tool to you use to build?
>
> Anyway, I'll just export the variable all over the Makefile.
>
That's pbuilder, but maybe it's more about the environment that you are startin
Package: s3ql
Version: 2.11.1+dfsg-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
debian/rules override_dh_auto_test
make[1]: Entering directory
'/srv/jenkins-
Control: reopen -1
Control: found -1 1.1.0-2
Hi,
Please find the log of another failing build attached - I'm afraid you will need
to:
"* Force the locale to C.UTF-8 when invoking dh_auto_clean (Closes: #764979)"
do this for all the build steps.
Best,
Michael
pyacoustid-build-log.txt.gz
Desc
1 - 100 of 405 matches
Mail list logo
