Source: dput
Version: 1.0.2
Severity: serious
Tags: ftbfs
dput fails to build from source with sbuild in unstable/amd64. A buil
log ends with:
| ==
| ERROR: test_request_has_expected_fields
Source: debmake-doc
Version: 1.11-1
Severity: serious
Tags: ftbfs
debmake-doc randomly fails to build from source when performing a
parallel build (difficult to trigger). The issue lies in test case
debhello-3.0. Its Makefile says:
| all: data/hello.desktop po/ja.mo
|
| data/hello.desktop
On Wed, Oct 03, 2018 at 10:01:58PM +0200, Christoph Berg wrote:
> It is parsing the `free` output to probe available memory. The code is
> utterly wrong since free had been changed to output only two lines
> instead of three, so it looks at the amount of swap available. I
> haven't checked, but my
On Wed, Oct 03, 2018 at 02:37:23PM +0200, Frédéric Bonnard wrote:
> does this bug still appear for rebootstrap ?
> How can I simply reproduce it within rebootstrap ?
> Building inside sbuild works.
This is/was a native problem. It was filed against the natively built
ppc64el package (noticed as a
Source: cloud-init
Version: 0.7.9-5
Severity: serious
Tags: ftbfs
Building cloud-init in unstable on amd64 fails in sbuild. The build ends
with:
|debian/rules override_dh_auto_test
| make[1]: Entering directory '/<>'
| py3versions: no X-Python3-Version in control file, using supported
Source: bash-completion
Version: 1:2.8-1
Severity: serious
Tags: ftbfs
bash-completion randomly fails to build from source in a parallel
setting. The following log exhibits the failure:
| make[3]: Entering directory '/<>/completions'
| make[3]: Nothing to be done for 'install-exec-am'.
| for
Source: atdgen
Version: 1.9.1-2
Severity: serious
Tags: ftbfs
atdgen fails to build from source in unstable on amd64. A build log ends
with:
| /usr/bin/make atdgen.cma atdgen.run
| make[4]: Entering directory '/<>/src'
| ocamlfind ocamlc -dtypes -g -c -package "str atd biniou yojson"
.
+ * Explicitly choose where to use -msse2. (Closes: #-1)
+
+ -- Helmut Grohne Tue, 02 Oct 2018 19:01:09 +0200
+
libvidstab (1.1.0-1) unstable; urgency=low
* Upstream release 1.1.0 (Closes: #709193)
diff --minimal -Nru libvidstab-1.1.0/debian/rules libvidstab-1.1.0/debian/rules
--- libvidstab
Source: apertium-hbs-mkd
Version: 0.1.0~r76450-2
Severity: serious
Tags: ftbfs
apertium-hbs-mkd fails to build from source with sbuild on
unstable/amd64 when DEB_BUILD_OPTIONS is sufficiently parallel. A build
log ends with:
|dh_auto_build -O--fail-missing
| make -j8
| make[1]:
Source: afterburner.fx
Version: 1.7.0-1
Severity: serious
Tags: ftbfs
afterburner.fx fails to build in sbuild for unstable/amd64. A build log
ends with:
|dh_auto_build
| /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar
Source: aether-ant-tasks
Version: 1.0.1-2
Severity: serious
Tags: ftbfs
A native build of aether-ant-tasks with sbuild in unstable on amd64 ends
with:
|jh_classpath -O--buildsystem=maven
| error: Can't rename /usr/share/java/commons-lang3.jar as
/usr/share/java/commons-lang3.zbk Permission
make depends.
+ * Build libsasl2-modules-gssapi-heimdal against heimdal: (Closes: #880393)
++ Run dh_install before overwriting libgssapiv2.so* with the MIT
+ implementation.
+
+ -- Helmut Grohne Sat, 29 Sep 2018 12:08:59 +0200
+
cyrus-sasl2 (2.1.27~101-g0780600+dfsg-3.1) unstable
Control: severity -1 important
On Thu, Nov 09, 2017 at 04:11:00PM +0100, Andreas Beckmann wrote:
> The broken symlink has returned:
>
> 0m22.2s ERROR: FAIL: Broken symlinks:
> /usr/lib/x86_64-linux-gnu/libdevmapper-event-lvm2.so ->
> /lib/x86_64-linux-gnu/libdevmapper-event-lvm2.so.2.02
1.
Package: python3-alembic,python3-astroid
Severity: serious
When installing python3-alembic and python3-astroid in a fresh sid
chroot, this is what I get:
| ...
| Unpacking python3-sqlalchemy (1.2.8+ds1-1) ...
| Selecting previously unselected package python3-alembic.
| Preparing to unpack
Source: systemd
Version: 239-9
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: reassign 909440 meson
Control: tags 909440 + ftbfs
Control: affects 909440 + src:systemd
Control: block -1 by 909440
systemd presently fails to build from source. The immediate
Package: apt
Version: 1.7.0~rc1
Severity: serious
File: /usr/bin/apt-cache
If you do a fresh sid debootstrap and then you can get the following
interaction:
$ apt-cache show gcc-8-base=installed libgcc1=installed
Package: gcc-8-base
Source: gcc-8
Version: 8.2.0-7
Installed-Size: 244
Maintainer:
Package: libiptcdata0-dev
Version: 1.0.5-1
Severity: serious
Justification: makes tracker-miners ftbfs
Tags: ftbfs
Control: affects -1 + src:tracker-miners
libiptcdata.pc is now shipped in literally
/usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig. That is semantically
equivalent to it being absent.
Package: asttest
Version: 0.0.0+svn.5781-2
Severity: grave
The asttest package lacks the asttest binary mentioned in the package
description. In fact the asttest package is empty beyond a changelog and
a copyright file. It doesn't even have dependencies. It's useless as is.
Helmut
Control: retitle -1 unnecessary dependency on python3:any
Control: severity -1 wishlist
On Fri, Aug 24, 2018 at 05:35:09PM +0200, Helmut Grohne wrote:
> # apt-get install gir1.2-ibus-1.0:i386 python3-gi
Laurent explained to me that this is not how things are supposed to
work. For us
Package: gir1.2-ibus-1.0
Version: 1.5.18-1
Severity: serious
In a fresh sid amd64 chroot, I did:
# dpkg --add-architecture i386
# apt-get update
# apt-get install gir1.2-ibus-1.0:i386 python3-gi
I then tried to use ibus:
$ python3
Python 3.6.6+ (default, Aug 20 2018, 16:21:04)
[GCC 8.2.0] on
Source: sketch
Version: 1:0.3.7-6
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
sketch fails to build from source in unstable on amd64 when performing
an arch-only build. A log ends with:
| dh binary-arch
|dh_testroot -a
|dh_prep -a
|dh_auto_install -a
Source: libgd2
Version: 2.2.5-4
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
libgd2 fails to build from source on amd64 in unstable. A build ends
with:
|dh_auto_build
| make -j1
| make[1]: Entering directory '/<>'
| Making all in src
| make[2]:
Source: libtasn1-6
Version: 4.13-3
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Doing an arch-only build of libtasn1-6 on amd64 fails. A build log ends
with:
| make[3]: Entering directory '/<>/doc'
| restore=: && backupdir=".am$$" && \
| am__cwd=`pwd` &&
Source: ckermit
Version: 302-5.3
Severity: serious
Justification: policy section 4.6
Tags: upstream
ckermit does not trap errors from make. Failing to do so is prohibited
by the Debian policy section 4.6, because it can cause silent misbuilds
and makes debugging failures unnecessarily hard.
The
Source: moria
Version: 5.6.debian.1-2
Severity: serious
Justification: debian policy 4.6
The Debian policy requires that a build aborts on errors rather than
continuing. The moria package is interesting in this regard:
( cd build ; $(MAKE) )
It tries to cd to build and then runs make
On Wed, Aug 08, 2018 at 12:35:36PM +0300, Boris Pek wrote:
> Package src:qtkeychain is not FTBFS, so this tag is wrong. I am not sure
> which severity is better, but severity "serious" looks wrong to me.
The ftbfs tag was correct. The bug wasn't assigned to src:qtkeychain
(source package), but to
Source: psi-plus
Version: 1.3.384-1
Severity: serious
Tags: ftbfs
psi-plus fails to build from source in unstable on amd64. A build ends
with:
| /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wdate-time
e-3.11.0/debian/changelog
--- logrotate-3.11.0/debian/changelog 2017-01-07 19:54:50.0 +0100
+++ logrotate-3.11.0/debian/changelog 2018-08-06 20:54:00.0 +0200
@@ -1,3 +1,10 @@
+logrotate (3.11.0-0.2) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS: autore
Source: gcc-7
Version: 7.3.0-27
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Hi Matthias,
I'm not sure whether you're aware already, but I felt that it was best
to just document that gcc-7 fails to build against isl 0.20. I tried to
check the vcs on whether this
-2.7.6/debian/changelog2018-08-05 11:53:06.0 +0200
@@ -1,3 +1,10 @@
+patch (2.7.6-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS: dh_autoreconf (Closes: #-1)
+
+ -- Helmut Grohne Sun, 05 Aug 2018 11:53:06 +0200
+
patch (2.7.6-2) unstable; urgency=high
Control: tags -1 + patch
On Sun, Aug 05, 2018 at 08:55:32AM +0200, Helmut Grohne wrote:
> Scanning the recent upload history, automake-1.16 looks suspicious now.
Yes, it looks like a missing Makefile.am dependency. The attached patch
makes it build.
Helmut
--- libtextwrap-0.1.orig/Makefile
On Sun, Aug 05, 2018 at 07:31:55AM +0200, Helmut Grohne wrote:
> libtextwrap fails to build from source on amd64 in unstable. A build log
> ends with:
>
> | touch configure-stamp
> | dh_testdir
> | /usr/bin/make
> | make[1]: Entering directory '/<>'
> | /usr/bin/make
Source: libtextwrap
Version: 0.1-14.1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
libtextwrap fails to build from source on amd64 in unstable. A build log
ends with:
| touch configure-stamp
| dh_testdir
| /usr/bin/make
| make[1]: Entering directory '/<>'
|
Source: network-manager-strongswan
Version: 1.4.4-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
network-manager-strongswan fails to build from source. A build on amd64
ends with:
| libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time
-D_FORTIFY_SOURCE=2
Source: meson
Version: 0.47.1-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
While trying to sponsor 0.47.1-2 I noticed that the current and
prospective version fail to build from source. The build ends with:
| The Meson build system
| Version: 0.47.1
| Source
Source: stockfish
Version: 9-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
stockfish fails to build from source on armel, mips, mipsel, m68k,
powerpc, powerpcspe and sh4. A build log from mips ends with:
| g++ -o stockfish benchmark.o bitbase.o bitboard.o
On Sun, Jul 08, 2018 at 01:24:06PM +, Santiago Vila wrote:
> [...]
> debian/rules build-indep
> dh build-indep
>dh_update_autotools_config -i
>dh_autoreconf -i
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> dh_auto_build
> HOME=$(mktemp -d)
Source: bundler
Version: 1.16.1-2
Severity: serious
Tags: ftbfs
bundler fails to build from source since ronn got split out from
ruby-ronn into a separate package ronn. Fixing this problem will involve
adding ronn to Build-Depends as the build system tries to invoke ronn
with "ruby2.5 -S ronn".
Source: ledger-wallets-udev
Version: 0.1
Severity: serious
Since ronn got split out of ruby-ronn, ledger-wallets-udev fails to
build from source. It was not possible to have ruby-ronn temporarily
depend on ronn, because that would have created a dependency cycle.
Please update Build-Depends and
Source: r10k
Version: 2.6.2-2
Severity: serious
Since ronn got split out of ruby-ronn, r10k fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with ronn
Source: brutespray
Version: 1.6.0-1
Severity: serious
Since ronn got split out of ruby-ronn, brutespray fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: haproxyctl
Version: 1.3.0-2
Severity: serious
Since ronn got split out of ruby-ronn, haproxyctl fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: unburden-home-dir
Version: 0.4.1
Severity: serious
Since ronn got split out of ruby-ronn, unburden-home-dir fails to build
from source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and
Source: foodcritic
Version: 13.1.1-1
Severity: serious
Since ronn got split out of ruby-ronn, foodcritic fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: seqprep
Version: 1.3.2-2
Severity: serious
Since ronn got split out of ruby-ronn, seqprep fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: qiime
Version: 1.9.1+dfsg-2
Severity: serious
Since ronn got split out of ruby-ronn, qiime fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: ruby-coveralls
Version: 0.8.21-1
Severity: serious
Since ronn got split out of ruby-ronn, ruby-coveralls fails to build
from source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and
Source: python-base58
Version: 1.0.0-1
Severity: serious
Since ronn got split out of ruby-ronn, python-base58 fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: git-extras
Version: 4.5.0-1
Severity: serious
Since ronn got split out of ruby-ronn, git-extras fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Package: coquelicot
Version: 0.9.6-1
Severity: serious
Since ronn got split out of ruby-ronn, coquelicot fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: duc
Version: 1.4.3-3
Severity: serious
Since ronn got split out of ruby-ronn, duc fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with ronn
Source: slt
Version: 0.0.git20140301-4
Severity: serious
Since ronn got split out of ruby-ronn, slt fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: espeak-ng
Version: 1.49.2+dfsg-2
Severity: serious
Since ronn got split out of ruby-ronn, espeak-ng fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: foremancli
Version: 1.0-2
Severity: serious
Since ronn got split out of ruby-ronn, foremancli fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: shapelib
Version: 1.4.1-1
Severity: serious
Since ronn got split out of ruby-ronn, shapelib fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: git-lfs
Version: 2.4.2-1
Severity: serious
Since ronn got split out of ruby-ronn, git-lfs fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Package: curvedns
Version: 0.87-4
Severity: serious
Since ronn got split out of ruby-ronn, curvedns fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: decopy
Version: 0.2.3-2
Severity: serious
Since ronn got split out of ruby-ronn, decopy fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with
Package: dbab
Version: 1.3.2-1
Severity: serious
Since ronn got split out of ruby-ronn, dbab fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with
Control: tags -1 - moreinfo
On Wed, Jul 04, 2018 at 10:37:32PM +0200, Michael Biebl wrote:
> sound like an sbuild bug. Using pbuilder I have no problems building the
> gnupg2 package.
I kinda agree with you here. I actually ran into this bug a while
earlier:
Unlike systemd-sysv, systemd-shim
Package: libpam-systemd
Version: 239-4
Severity: critical
Justification: makes gnupg2 ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:gnupg2
A native(!) build of gnupg2 with sbuild and
--bd-uninstallable-explainer=apt fails. dose3 finds an installation set,
but it
On Tue, Jul 03, 2018 at 12:29:00PM +0200, Alberto Gonzalez Iniesta wrote:
> Have you tested your assertion? Because if ./configure fails, MCONFIG is
> not created and the build (make) fails:
That was a general statement. I think it doesn't really matter whether
it practically does cause
Source: libatomic-ops
Version: 7.6.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
libatomic-ops fails to build from source on amd64. The build ends with:
| dh_installdirs
Source: glibc
Version: 2.27-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
glibc fails to cross build from source. An arch-only build log (using
DEB_BUILD_OPTIONS=nocheck to speed things
Source: libseccomp
Version: 2.3.3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
libseccomp fails to build from source on amd64. The build ends with:
|dh_install
|dh_installdocs
Source: gfsview
Version: 20121130+dfsg-5
Severity: serious
Justification: missing source
While trying to fix gfsview, I noticed that the source of gfsview is
incomplete. debian/Makefile.in is quite obviously generated from
debian/Makefile.am, but debian/Makefile.am is missing. I'm not sure what
On Mon, Jun 18, 2018 at 06:10:04PM +0200, Roland Fehrenbacher wrote:
> >>>>> "HG" == Helmut Grohne writes:
> HG> You moved the programs and the corresponding manual pages, but
> HG> the development manual pages still live in libfabric1 and are
>
Hi Adrian,
On Sun, Jun 17, 2018 at 02:52:40PM +0300, Adrian Bunk wrote:
> do you plan to upload anything here?
No. At least not soon.
> I am a bit confused about a maintainer-upload versioned change saying
> "Non-maintainer upload." plus nothing uploaded to the archive so far.
That's an
Control: reopen -1
On Thu, May 31, 2018 at 09:03:09AM +, Debian Bug Tracking System wrote:
>* Add package libfabric-bin (Closes: #891395)
You moved the programs and the corresponding manual pages, but the
development manual pages still live in libfabric1 and are still
problematic for the
Source: gnushogi
Version: 1.4.2-3
Severity: serious
Justification: policy 4.6
Tags: upstream
If you run
grep '^\s*-' Makefile.in
you'll find a number of crucial make rules that ignore errors. In
particular the main build and install targets are among them. Thus
gnushogi continues building
Source: predict
Version: 2.2.3-4
Severity: serious
Justification: Debian policy section 4.6
predict's debian/rules chains commands with ";" in a lot of places. This
covers simply "cd something; execute something else", but also longer
chains involving autoconf or the like. Such practise is
On Sat, Jun 02, 2018 at 11:58:21AM +0300, Juhani Numminen wrote:
> On Fri, 1 Jun 2018 21:12:06 +0200 Sébastien Villemot
> wrote:
> > Package: src:rkward
> > Severity: serious
> For a build log of the failure, see the link "rbuild (41KB)" at [1].
>
> It seems that the cmake invocation is
Source: nss
Version: 2:3.37-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
nss fails to build from source on at least armel, armhf, mips and
mipsel. It fails linking libfreeblpriv3.so with lots of undefined
references. For build logs see e.g.
Source: rifiuti
Version: 20040505-1
Severity: serious
Justification: policy 4.6
The install target in src/Makefile chains commands with ";" and thus
does not abort on an error. This violates Debian policy section 4.6.
Helmut
Control: tags -1 - moreinfo
On Sat, May 26, 2018 at 05:27:20PM +0300, Adrian Bunk wrote:
> Where is the attachment?
Here you go.
Helmut
From: Helmut Grohne <hel...@subdivi.de>
Subject: make sh/autoconfall.sh work somewhat
Index: ncftp-3.2.5/sh/autoc
Source: bolt
Version: 0.3-3
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
bolt fails to build from source on unstable:
| dpkg-buildpackage: info: source package bolt
| dpkg-buildpackage: info: source version 0.3-3
| dpkg-buildpackage: info: source distribution
:04:03.0 +0100
+++ pasco-20040505/debian/changelog 2018-05-19 13:33:09.0 +0200
@@ -1,3 +1,10 @@
+pasco (20040505-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix the upstream Makefile. (Closes: #-1)
+
+ -- Helmut Grohne <hel...@subdivi.de> Sat, 19 May 2
Source: libtasn1-6
Version: 4.13-2
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
libtasn1-6 fails to build from source in unstable (full build).
| Making check in reference
| make check-TESTS
| make[5]: Entering directory '/<>/doc/reference'
| echo "#!/bin/sh -e"
Package: linux-libc-dev,libc6-dev
Severity: serious
Justification: makes systemd ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:systemd libmount-dev
systemd FTBFS here, because compiling load-fragment.c fails. I spent a while
minimizing that file and it boils down
Source: crystalhd
Version: 1:0.0~git20110715.fdd2f19-12
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap
I was trying to fix a cross compilation issue in crystalhd and noticed
that filters/gst/gst-plugin/src/Makefile.in would not be regenerated
from the corresponding Makefile.am.
On Sat, Apr 21, 2018 at 08:05:53PM -0400, Antoine Beaupre wrote:
> So I don't quite understand how this can possibly happen: setuptools is
> required to build the package in the first place, why can't dh-python
> figure that out on its own?
Thank you for your attention to detail.
I admit having
On Sat, Apr 21, 2018 at 04:01:46PM +0800, Shell Xu wrote:
> I don't use python-formalchemy for years, and even requested for adoption
> for years. But I guess I known how this is coming.
Thank you for replying anyway.
> According to this repo, the latest change is 1.5.3, been committed 3 years
>
Control: tags -1 - moreinfo
Control: severity -1 normal
On Sat, Apr 21, 2018 at 08:41:26AM +0200, Michael Biebl wrote:
> gi overrides are not supposed to be imported directly.
> Those overrides are in effect if the GObject Introspection machinery is
> in use, in which case the necessary python
Control: severity -1 normal
Control: tags -1 = upstream
On Sat, Apr 21, 2018 at 08:36:58AM +0200, Michael Biebl wrote:
> Afaiu, the idea behind this wrapper is, that it's up to the actual
> application to decide which implementation it wants, i.e. glib
> (python-gobject-2) or the gi based Glib
, Apr 21, 2018 at 09:47:59AM +1000, Brian May wrote:
> Helmut Grohne <hel...@subdivi.de> writes:
>
> > django.core.exceptions.ImproperlyConfigured: Requested setting
> > DEFAULT_INDEX_TABLESPACE, but settings are not configured. You must
> > either d
Control: severity -1 normal
On Sat, Apr 21, 2018 at 01:57:22AM +0200, Fabrizio Pollastri wrote:
> Since python-avc 0.8.3-1.1 supports different widget toolkits and
> the user is normally interested to only one toolkit among these, I
> preferred to set them as "suggested" (the list
Package: python-setuptools-scm
Version: 1.17.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-setuptools-scm importing the module setuptools_scm
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "",
Package: python3-spyder-line-profiler
Version: 0.1.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-spyder-line-profiler importing the module
spyder_line_profiler
into a python interpreter fails with the following error:
Traceback (most recent call
Package: python3-django-tables2
Version: 1.14.2-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-django-tables2 importing the module django_tables2
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "",
Package: python3-winrm
Version: 0.3.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-winrm importing the module winrm
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File
Package: python-django-cors-headers
Version: 2.1.0+github-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-django-cors-headers importing the module corsheaders
into a python interpreter fails with the following error:
Traceback (most recent call last):
Package: python3-mplexporter
Version: 0.0.1+20140921-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-mplexporter importing the module mplexporter
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "",
Package: python3-fiat
Version: 2017.2.0.0-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-fiat importing the module FIAT
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File
Package: python3-pymediainfo
Version: 2.2.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-pymediainfo importing the module pymediainfo
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1,
Package: python-brian
Version: 1.4.3-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-brian importing the module brian
into a python interpreter fails with the following error:
/usr/lib/python2.7/dist-packages/brian/__init__.py:46: UserWarning:
Package: python3-terminado
Version: 0.8.1-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-terminado importing the module terminado
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
Package: python3-django-cors-headers
Version: 2.1.0+github-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-django-cors-headers importing the module corsheaders
into a python interpreter fails with the following error:
Traceback (most recent call
Package: python3-pytest-runner
Version: 2.11.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-pytest-runner importing the module ptr
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
Package: python-bcolz
Version: 1.2.0+ds1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-bcolz importing the module bcolz
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File
Package: python3-lasagne
Version: 0.1+git20180322.37ca134-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-lasagne importing the module lasagne
into a python interpreter fails with the following error:
Traceback (most recent call last):
File
801 - 900 of 1547 matches
Mail list logo
