severity 938407 serious
block 938816 by 938407
thanks
routes build-depends on python-webtest, which depends on python-waitress, which
is no longer built by the waitress source package.
Package: python-msrest
Version: 0.5.5-1
Tags: bullseye
python-msrest in testing build-depends on the python-httpretty binary package,
which is no longer built by the python-httpretty source package, and has been
completely removed from testing/unstable.
Furthermore the python-msrest binary pac
severity 936665 serious
thanks
grokmirror depends on the python-git binary package, which has already been
dropped by the python-git source package.
Hi.
As I posted earlier nototools build-depends on python-fonttools which is no
longer built by the fonttools source package. Since this package turned out not
to be eligable for autoremoval I decided to take a slightly deeper look.
nototools builds a single binary package, python-nototools wh
Package: nbdkit
Version: 1.14.2-2
I noticed that nbdkit failed to build on raspbian because the iso plugin had
not been built, further investigation indicated this was because genisoimage
was not installed.
It seems that on Debian this gets pulled in indirectly, while on raspbian it
doesn't,
severity 937855 serious
thanks
python-jsonext depends on the python-arrow binary package, which has already
been dropped by the python-arrow source package.
Package: repmgr
Version: 4.2.0-2
Severity: serious
postgresql-12 recently took over a bunch of library packages from
postgresql-11. This seems to have caused repmgr's autopkgtest to fail with a
bunch of undefined symbol errors.
This can be seen with both testings version (tested as part of the
Package: kio
While trying to install a kde app for a foreign architecture. I noticed that
while libkf5declarative5 is multi-arch: same it can only be installed for one
architecture at a time, because it depends on kio and kio has no multi-arch
field.
Unfortunately it seems kio contains a bunc
Disabling the PROJ support was not an option as it was for vtk6. You may
want to reinstate the embedded copy and use that instead.
It looks like a commit doing this was made on salsa on august 6th
https://salsa.debian.org/science-team/vtk7/commit/19d6e5e2e02cbd10404dd96e750370546feaa82b
Is ther
Package: check-manifest
Version: 0.39-1
Severity: serious
The release team have decreed that non-buildd binaries can no longer migrate to
testing, please make a source-only upload so your package can migrate.
severity 937162 serious
thanks
nototools depends on python-fonttools which has already been dropped by the
fonttools source package.
severity 937727 serious
thanks
python-enable depends on python-fonttools which has already been dropped by the
fonttools source package.
severity 936684 serious
thanks
h5py build-depends on the python-pkgconfig binary package, which is no longer
built by the python-pkgconfig source package. The binary package is still
present in unstable as a cruft package, but is completely gone from testing.
Package: rustc
Version: 1.37.0+dfsg1-1
I recently tried to crossbuild rust for Debian armhf on Debian bullseye amd64.
To build I used the command
CONFIG_SITE=/etc/dpkg-cross/cross-config.armhf dpkg-buildpackage -a armhf
-Pcross,nocheck 2>&1 | tee ../rustc-debarmhf.log
Unfortunately it failed
Package: check-manifest
Version: 0.37-1
Tags: bullseye, sid
Severity: serious
x-debbugs-cc: b...@packages.debian.org
bzr recently became a transitional package to breezy (a fork of bzr),
unfortunately this is causing the autopkgtest of check-manifest to fail.
==
Package: ftp.debian.org
x-debbugs-cc: b...@packages.debian.org
Hi,
The most recent upload of bzr dropped the python-bzrlib and python-bzrlib-dbg binary packages.
However they do not seem to be showing up in the "cruft report", and britney thinks the
package is "out of date" on all architecture
package: rust-sha1-asm
version: 0.4.3-2
The rust-sha1-asm upstream code outright refuses to build on anything other
than x86 and x86_64 . During the debian package build the upstream code is only
actually built as part of running the testsuite, not as part of making the
package (since Debian r
Package: python-pyramid-zcml
Version: 1.0.0-1.1
Severity: serious
x-debbugs-cc: w...@debian.org
The release-team have decreed that non-buildd binaries cannot migrate to
testing, please make a source-only upload to the package can migrate.
Package: python-pyramid-tm
Version: 0.5-1.1
Severity: serious
x-debbugs-cc: w...@debian.org
The release team have decreed that non-buildd binaries cannot migrate to
testing, please make a source-only upload so the package can migrate.
severity 937244 serious
thanks
paste depends on the python-tempita binary package, which has already been
dropped by the python-tempita source package.
Package: ufolib2
Version: 0.4.0+dfsg1-2
Severity: serious
The release-team have decreed that non-buildd binaries can no longer migrate to
testing, please make a source-only upload so your package can migrate.
On 24/09/2019 03:55, kpcyrd wrote:
On Sun, Sep 22, 2019 at 11:07:57PM +0100, peter green wrote:
Package: rust-sha-1
Version: 0.8.1-2
Severity: serious
If rust-sha-1 is re-built, the version mentioned in virtual package names in the provides changes from
"0.4" to "0.8&qu
found 940717 3.8.5-1
tags 940717 +bullseye
tags 940717 +sid
Since the version of default-d-compiler which uses gdc on armhf migrated to
testing, gtk-d also fails to build on armhf in testing.
Severity 936359 serious
Thanks
python-cylc depends on python-cherrypy3 which is no longer built by the
cherrypy3 source package.
Severity 936282 serious
Thanks
ceph depends on python-cherrypy3 which has already been dropped by the
cherrypy3 source package.
severity 936270 serious
thanks
calibre depends on python-cherrypy3 which has already been dropped by the
cherrypy3 source package.
Package: loggerhead
Version: 1.19~bzr479+dfsg-3
Severity: serious
Loggerhead has multiple dependency issues.
The loggerhead source package build-depends on python-subunit which is no
longer built by the subunit source package.
The loggerhead source package build-depends on python-bzrlib.tests
Package: rust-sha-1
Version: 0.8.1-2
Severity: serious
If rust-sha-1 is re-built, the version mentioned in virtual package names in the provides changes from
"0.4" to "0.8", but the version mentioned in the virtual package names in the depends
stays at "0.4", thus breaking dependencies between
Package: gtk-d
Version: 3.9.0-1
Severity: serious
the new gtk-d upload failed to build on armhf, the dependencies install gdc but
the package tries to build with ldc.
I presume this was triggered by the change in default d compiler on armhf from
ldc to gdc. The changelog mentions building with
severity 938816 serious
thanks
python-webtest depends on python-waitress, which has already been dropped from
the waitress source package.
Package: breezy
Severity: serious
Version: 3.0.1-2
Breezy (both versions 3.0.1-2 and 3.0.1-4) build-depends on python-subunit
which is no longer built by the subunit source package.
Package: lava-server
Version: 2019.01-5
Severity: serious
Tags: bullseye, sid
lava depends on gunicorn3 which is no longer built by the gunicorn source package.
I belive you need to change your dependency to gunicorn, possiblly with a version
constraint of >= 19.9.0-4
Package: dhcpig
Version: 1.5-2
Severity: serious
Tags: bullseye, sid
dhcpig depends on python-scapy which is no longer built by the scapy source
package.
If you want your package to remain around you probably need to migrate to
python 3.
On 16/09/2019 10:38, Andreas Tille wrote:
Hi Peter,
On Sun, Sep 15, 2019 at 02:47:50PM +0100, peter green wrote:
tmp = rt.encrypt('Cycle{}'.format(pickle.dumps(objSave)))
Thanks to this hint
This hint was *wrong*, it will introduce garbage into the string and the
"rotor&q
Package: matplotlib2
Version: 2.2.4-1
Severity: serious
matplotlib2 build-depends on python-cxx-dev, this package is no longer built by
the pycxx source package. It is still present in unstable as a cruft package,
but is completely gone from testing.
> tmp = rt.encrypt('Cycle{}'.format(pickle.dumps(objSave)))
Thanks to this hint
This hint was *wrong*, it will introduce garbage into the string and the
"rotor" code is clearly designed to work with byte strings, not unicode strings.
Change it to
"tmp=rt.encrypt( b'Cycle'+pickle.dumps(objSave
Package: zope.testing
Version: 4.6.2-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/z/zope.testing/2966135/log.gz
autopkgtest [06:13:32]: test all: [---
Traceback (most recent call last):
File "/usr/bin/zope-testrunner", line 9, in
load_ent
Package: zope.testrunner
Version: 4.4.9-3
Severity: serious
autopkgtest [06:13:47]: test all-2: [---
bash: /tmp/autopkgtest-lxc.v65a_j_9/downtmp/build.cMu/src/debian/tests/all-2:
/usr/bin/python: bad interpreter: No such file or directory
autopkgtest [06:13:47]: test all-2:
Package: neo
Version: 0.7.2-1
Severity: serious
The release team have decreed that non-buildd binaries can no longer migrate to
testing. Please make a source-only upload so your package can migrate.
Package: python3-osprofiler
Version: 2.6.0-1
Severity: grave
python3-osprofiler fails to install, I first noticed this in an autopkgtest,
but I was able to reproduce it in a local sid chroot too.
Setting up python3-osprofiler (2.6.0-1) ...
update-alternatives: error: alternative path /usr/bin/
severity 938804 serious
thanks
python-vtk6 depends on the python-autobahn binary package which has already
been dropped by the python-autobahn source package.
Package: distro-info
Version: 0.21
Severity: serious
Tags: bullseye, sid
pylint has been migrated from python 2 to python 3. This seems to be causing an
autopkgtest failure in your package. Can you fix it so that pylint can migrate
to testing?
severity 938255 serious
thanks
python-watchdog depends on the python-pathtools binary package which has
already been dropped by the python-pathtools source package.
severity 938215 serious
thanks
python-testtools depends on the python-extras binary package which is no longer
built by the python-extras source package.
but this leads later to
Traceback (most recent call last):
File "cycle.py", line 83, in OnCloseWindow
Save_Cycle(cycle.name, cycle.passwd, cycle.file)
File "/home/andreas/debian-maintain/salsa/med-team/cycle/save_load.py", line
46, in Save_Cycle
tmp=rt.encrypt( 'Cycle'+pickle.dum
Package: srslte
Version: 3.14.1.0-2
Severity: serious
srslte FTBFS in bullseye and sid due to the new versions of bladerf and uhd
changing some data types. I patched the errors and was able to get a successful
build in raspbian bullseye which I uploaded to the raspbian archive, I have not
test
severity 938919 serious
thanks
python-zope.testrunner in testing depends on python-zope.exceptions which has
already been dropped by the zope.exceptions source package.
This has been addressed in unstable by dropping the python-zope.testrunner
binary package, however that fix cannot currently
severity 937518 serious
thanks
python-pyramid-jinja2 depends on python-zope.deprecation which has already been
dropped by the zope.deprecation source package.
severity 938089 serious
thanks
python-pyramid depends on python-zope.deprecation which has already been
dropped by the zope.deprecation source package.
severity 937593 serious
thanks
python-aws-xray-sdk depends on the python-wrapt binary package which has
already been dropped by the python-wrapt source package.
severity 938133 serious
thanks
python-repoze.tm2 depends on python-transaction which has already been dropped
by the transaction source package.
severity 782951 serious
thanks
This package depends on python-transaction which is no longer built by the
transaction source package.
Hi
Over 5 months ago an upload of pywps was made to switch it from python 2 to
python 3 (and hence unblock removal of at least two other python 2 packages).
This upload went to new as it changed the list of binary packages. It seems it
has been there ever since.
Is there a problem with the up
tags 939561 +fixed-upstream
tags 939561 +patch
thanks
Some googling revealed that upstream had fixed this issue
https://github.com/pothosware/SoapyBladeRF/pull/19 . I was able to take the
upstream pull request, turn it into a patch series and apply it to the Debian
package.
I have uploaded my
Severity 938551 serious
Thanks
spyder-kernels (build-)depends on python-cloudpickle which has already been
dropped by the cloudpickle source package.
Severity 938550 serious
Thanks
spyder (build-)depends on python-cloudpickle which has already been dropped by
the cloudpickle source package.
Severity 938494 serious
Thanks
skimage (build-)depends on python-cloudpickle which has already been dropped by
the cloudpickle source package.
Package: sdaps
Version: 1.9.7-0.1
Severity: serious
sdaps build-depends on texlive-generic-recommended which is no longer built by
texlive-base. The old texlive-generic-recommended is still present in unstable
as a cruft package, but is completely gone from testing.
Please update your build-de
Package: gr-radar
Version: 0.0.0.20180308-1
Severity: serious
Tags: bullseye, sid
gr-radar failed to build with the following errors when an attempt was made to
binnmu it for the new gnuradio.
CMake Error at CMakeLists.txt:120 (find_package):
Could not find a configuration file for package
Package: gr-limesdr
Version: 0.9~beta-1+b2
Severity: serious
Tags: bullseye, sid
gr-limesdr failed to build with the following errors when an attempt was made
to binnmu it for the new gnuradio.
-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY MPIR_INCLUDE_DIR)
CMake Error at
/usr/
Package: gr-gsm
Version: 0.42.2-1
Severity: serious
Tags: bullseye, sid
gr-gsm failed to build with the following errors when an attempt was made to
binnmu it for the new gnuradio.
CMake Warning at CMakeLists.txt:135 (find_package):
Found package configuration file:
/usr/lib/x86_64-li
severity 937988 serious
thanks
python-osprofiler depends on the python-oslo.concurrency binary package which
has already been dropped by the python-oslo.concurrency source package.
Package: gnss-sdr
Version: 0.0.11-1
Severity: serious
gnss-sdr seems to have recently started failing to build with the following
error.
cd /build/1st/gnss-sdr-0.0.11/obj-x86_64-linux-gnu/src/utils/front-end-cal && /usr/bin/c++
-DBOOST_GREATER_1_65 -DGNSSSDR_INSTALL_DIR=\"/usr\" -DGNSS_SDR_V
Package: metview
Version: 5.6.1-3
Severity: serious
It seems metview has recently started to fail to build on 32-bit,
/<>/atlas/src/tests/mesh/test_halo.cc: In function 'void
atlas::test::traced_test_105(std::string&, int&, int)':
/<>/atlas/src/tests/mesh/test_halo.cc:142:40: error: narrowing
tags 939419 +patch
thanks
On 04/09/2019 20:45, Andrew Bartlett wrote:
On Wed, 2019-09-04 at 19:59 +0100, plugwash wrote:
I see two possible fixes.
1. Avoid using version numbers for the samba package that will trigger
this issue.
2. Change the logic that generates the version numbers for the
l
Package: sbcl
Version: 2:1.5.6-1
Severity: serious
sbcl build-depends on texlive-generic-recommended which is no longer built by
texlive-base. The old texlive-generic-recommended is still present in unstable
as a cruft package, but is completely gone from testing.
Please update your build-depe
Package: gdcm-doc
Version: 2.8.8-9
Severity: serious
Tags: bullseye, sid
gdcm-doc depends on vtk6-doc which is no longer built by the vtk6 source
package.
Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests. Please stop using Python2
I was looking at removing python2 support from pigpio and that brought gpiozero
to my attention. I found that I had typod the recommends/suggests in the
python3-gpiozero packa
On 28/08/2019 09:12, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the virtualenvwrapper package:
#933822: virtualenvwrapper depends on cruft package python-stevedore
Is there a reason that the fix was only uploaded to expe
Package: python-ceilometerclient
Version: 2.9.0-2
Severity: serious
Tags: bullseye, sid
The python-ceilometerclient binary package depends on and the
python-ceilometerclient binary package build-depends on a number of python 2
binary packages that are no longer built by their corresponding sour
Found 935015 0.11.2-2
Thanks
This bug also affects the version in testing.
Package: rust-pangocairo
Version: 0.6.0-1
Severity: serious
Tags: sid
According to wanna-build rust-pangocairo's build-dependencies are
unsatisfiable. It looks like librust-cairo-rs-0.5+default-dev has been replaced
with librust-cairo-rs-0.7+default-dev .
It looks like that class was dropped from vala-panel in
https://gitlab.com/vala-panel-project/vala-panel/commit/87493a6dfab9868f77b7b19b57fca40a06fe80af
Unfortunately the commit message doesn't give any clues to what if-anything it
should be replaced with.
If a proper fix cannot be found then
Package: haskell-blaze-html
Version: 0.9.1.1-3
Severity: serious
Tags: sid
haskell-blaze-html build-depends on libghc-quickcheck2-dev (< 2.12) but
unstable now has version 2.12.6.1-2
Package: fmcs
Version: 1.0-1
Severity: serious
Tags: bullseye, sid
python-fmcs depends on and the fmcs source package build-depends on
python-rdkit which is no longer built by the rdkit source package.
If you want to keep this package around then you need to migrate to python 3
Package: octave-octclip
Version: 1.0.8-6
Severity: serious
It seems that the new octave-octclip FTBFS in bullseye. I initially noticed
this in Raspbian, but it's also appearing on the reproducible builds site so it
doesn't seem to be raspbian specific.
fgeneral.c: In function 'Minimo':
fgener
Package: kazoo
Version: 2.6.1-1
Severity: serious
python-kazoo depends on and the kazoo source package build-depends on the
python-eventlet binary package which is no longer built by the python-eventlet
source package.
It's probably time to drop python 2 support from this package.
Package: goopg
Version: 0.3.1-9
Severity: serious
goopg depends on the python-oauth2client binary package which is no longer
built by the python-oauth2client source package.
If you want your package to be in bullseye you need to migrate to python 3 (and
fix the other rc bug)
severity 935015 serious
tags 935015 +bullseye
tags 935015 +sid
thanks
The python-fasteners source package has dropped the python-fastners binary
package. So this package needs to migrate to python 3 only if it is going to
stay around for bullseye.
Package: presentty
Version: 0.2.0-1
Severity: serious
Tags: bullseye, sid
Presentty (build-)depends on the python-pbr binary package which is no longer
built by the corresponding source package.
There is a bug report questioning whether said dependency is really necessary (
https://bugs.debian
Package: planet-venus
Version: 0~git9de2109-4.2
Severity: serious
Tags: bullseye, sid
planet-venus depends on python-portalocker which is no longer built by the
portalocker source package.
If you want your package to stay around you probably need to migrate to python
3.
Package: python-novnc
Version: 1:1.0.0-1
Severity: serious
Tags: bullseye, sid
The python-novnc package depends on the python-oslo.config binary package which
is no longer built by the corresponding source package.
As far as I can tell if you want to keep novnc around you will need to migrate
Package: m2crypto
Version: 0.31.0-5
Severity: serious
The release team have decreed that binaries not built on a buildd can no longer
migrate to testing. Please make a source-only upload so your package can
migrate.
Package: printrun
Version: 1.6.0-2
Severity: serious
Tags: bullseye, sid
printrun depends on python-cairosvg which is no longer built by the cairosvg
source package.
If you want your package to stay around you probably need to migrate to python
3.
Package: design-desktop-graphics
Version: 3.0.13
Severity: serious
design-desktop-graphics depends on python-cairosvg which is no longer built by
the cairosvg source package.
Looking at the stated intent of this package and the content of the packages
built by the cairosvg source package I bel
Package: python-trezor
Severity: serious
Version: 0.9.0-1
Tags: bullseye, sid
python-trezor (build-)depends on the python-ecdsa binary package which is no
longer built by the corresponding source package.
It's probablly time to drop python 2 support.
Package: sshpubkeys
Severity: serious
Version: 3.1.0-1
Tags: bullseye, sid
The python-sshpubkeys package depends on and the sshpubkeys source package
build-depends on the python-ecdsa binary package which is no longer built by
the corresponding source package.
It's probablly time to drop pytho
Package: python-keepkey
Severity: serious
Version: 0.7.3-1
Tags: bullseye, sid
python-keepkey depends on the python-ecdsa binary package which is no longer
built by the corresponding source package.
If you want your package to stay around you need to migrate to python 3.
So the libvpx transition prompted me to take a look at this, I added some code
to debian/rules to create a fake homedir, use it for the build and remove it in
the clean target.
Unfortunately I then ran into another failure.
/firefox-esr/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp
Package: gst-plugins-good1.0
Version: 1.16.0-2
Severity: serious
The release team have decreed that non-buildd binaries can no longer migrate to
testing, please make a source-only upload so your package can migrate.
Severity 929949 serious
Thanks.
Upstream rolled out a 0.8 version which is finally compatible with
python3, it would be nice to have it uploaded to Debian
The python-monotonic and python-fasteners packages have now dropped support for
python2, so if duplicity is going to stay around it needs t
Package: rekall
Severity: serious
x-debbugs-cc: sa...@debian.org
x-debbugs-cc: ben...@debian.org
While sending https://lists.debian.org/debian-python/2019/08/msg00072.html I got
forensics-de...@lists.alioth.debian.org
(generated fromrek...@packages.debian.org)
host alioth-lists-mx.debi
(note for people reading on bug 934333, the start of this thread can be found
at https://lists.debian.org/debian-python/2019/08/msg00070.html )
On 13/08/2019 11:54, Andrey Rahmatullin wrote:
This is worrying, a package with revdeps shouldn't have been dropped.
AIUI a "go cleanly" approach was
Package: heudiconv
Severity: serious
Version: 0.5.3-1
heudiconv build-depends on the python-datalad binary package which in turn
depends on the python-fasteners binary package, which in turn depends on the
python-monotonic binary package which is no longer built by the
python-monotonic source
Package: python-os-win
Version: 4.0.0-3
Severity: serious
Tags: bullseye
Python-os-win in testing (build-)depends on a number of python2 packages that
are no longer built by the corresponding source packages.
This is already fixed in unstable, by dropping python 2 support, but the
unstable ver
Severity: serious
i'm not entirely convinced on the severity, IIRC established practice in Debian
is that arch all packages need to be buildable on at least one release
architecture, not all release architectures.
python-os-win/experimental FTBFS on i386 while building the (arch:all)
package
Package: openstack-deploy
Version: 0.25
Severity: serious
Tags: bullseye, sid
openstack-deploy depends on the python-keystoneclient binary package which is
no longer built by the corresponding source package.
Should this dependency be changed to python3-keystoneclient ?
Package: django-oauth-toolkit
Version: 1.2.0-1
Severity: serious
The release team have decreed that non-buildd binaries can no longer migrate to
testing. Please make a source-only upload so this package can migrate.
Package: getdp
Version:3.0.4+dfsg1-1
Severity: serious
Tags: patch, bullseye, sid
getdp build-depends on texlive-generic-recommended which is no longer built by
texlive-base. Please update your build-dependency to texlive-plain-generic.
Package: python-gabbi
Version: 1.40.0-4
Severity: serious
Tags: bullseye, sid
python-gabbi (build-)depends on the python-jsonpath-rw-ext binary package which
is no longer built by the corresponding source package.
It's probably time to drop python 2 support from this package.
901 - 1000 of 2788 matches
Mail list logo
