Tags 944714 +patch
Thanks.
The easy fix here is to remove -Werror, in the long term of course migration to
a non-deprecated type should be considered but that is IMO an issue for
upstream not Debian.
I have tested said change and uploaded to raspbian, a debdiff sould appear soon
at
unblock 936745 by 936995
severity 936745 serious
thanks
matplotlib2 no longer has any dependencies or build-dependencies on packages
built from the ipywidgets source.
According to https://ftp-master.debian.org/users/dktrkranz/NBS ipywidgets has
dependencies or build-depdencies on several
Package: thonny
Version: 0.14.1-1
Severity: serious
Tags: bullseye, sid, patch
thonny depends and build-depends on the pylint3 binary package which is no
longer built by the pylint source package. The python 3 pylint functionality is
now in the pylint binary package.
These
Package: salt-pylint
Version: 0.14.1-1
Severity: serious
Tags: bullseye, sid, patch
python3-saltpylint depends on and the salt-pylint source package build-depends
on the pylint3 binary package which is no longer built by the pylint source
package. The python 3 pylint functionality is now in
Package: pytest-pylint
Version: 0.14.1-1Severity: serious
Tags: bullseye, sid, patch
python3-pytest-pylint depends on and the pytest-pylint source package
build-depends on the pylint3 binary package which is no longer built by the
pylint source package. The python 3 pylint functionality is now
Package: pylint-common
Version: 0.2.5-2
Severity: serious
Tags: bullseye, sid, patch
python3-plint-common depends on and the pylint-common source package
build-depends on the pylint3 binary package which is no longer built by the
pylint source package. The python 3 pylint functionlity is now
Package: pylint-celery
Version: 0.3-4
Severity: serious
Tags: bullseye, sid, patch
python3-plint-celery depends on and the pylint-celery source package
build-depends on the pylint3 binary package which is no longer built by the
pylint source package. The python 3 pylint functionlity is now in
severity 938572 serious
thanks
python-stfio depends on python-pandas which is no longer built by the pandas
source package.
Severity 937330 serious
thanks
psychopy depends on python-pandas which is no longer built by the pandas source
package.
severity 936190 serious
thanks
python-bcolz depends on python-pandas which is no longer built by the pandas
source package.
matplotlib2 seems to be an important node in the python2 removal/reduction
problem (and the qt4 removal problem). I have noticed there are a substantial
number of python module packages that it build-depends on but does not depend
on.
python-backports.functools-lru-cache
python-cairocffi
tags 922582 +patch
thanks
> gmic's cmake file needs to be updated for Opencv4
A bit more than just the cmake file needs to be updated.
I was able to get the package to build with the attached debdiff, I have upload
the changes to raspbian, no intent to NMU in Debian.
diff -Nru
severity 936745 serious
thanks
python-widgetsnbextension depends on python-notebook, which is no longer built
by the jupyter-notebook source package. python-ipywidgets in turn depends on
python-widgetsnbextension.
Unfortunately matplotlib2 build-depends (but does not depend) on
severity 938102 serious
thanks
python-pytest-cov depends on the python-pytest binary package, which is no
longer built by the python-pytest source package.
severity 937159 serious
thanks
python-nosexcover and python3-nosexcover depend on the python-coverage binary
package which is no longer built by the python-coverage source package.
severity 937666 serious
thanks
python-coverage-test-runner depends on the python-coverage binary package which
is no longer built by the python-coverage source package.
severity 937157 serious
thanks
python-nose2 depends on the python-coverage binary package which is no longer
built by the python-coverage source package.
severity 936335 serious
thanks
python-cov-core depends on the python-coverage binary package which is no
longer built by the python-coverage source package.
tags 943867 +patch
thanks
Since there was no maintainer response to this bug report, I decided to go
ahead and prepare a NMU. While testing for said NMU I found that the package's
clean target did not clean up properly. So I fixed it.
I have uploaded a NMU to delayed/5 with the attached
severity 937648 serious
thanks
python-click depends on the python-colorama binary package, which is no longer
built by the python-colorama source package.
package: libopencv-imgcodecs-dev
version: 4.1.2+dfsg-4
severity: serious
The libopencv-imgcodecs-dev binary package depends on and the opencv source
package build-depends on libgdcm2-dev which is no longer built by the gdcm
source package.
severity 936775 serious
thanks
python-notebook 5.7.8-1 in testing depends on python-terminado which is no
longer built by the terminado source package.
This is already fixed in unstable by dropping the python-notebook binary
package. Unfortunately the new version of jupyter-notebook has
Package: node-react
Version: 16.2.0-3
Severity: serious
node-react is currently blocked from migrating to testing because the release
team have decreed that only buildd-built binaries can migrate. Please make sure
your next upload is source-only.
Ideally one would deal with bug 933123 at the
Severity 937552 serious
Thanks
pysvn build-depends on the python-cxx-dev binary package, which is no longer
built by the the python-cxx-dev source package.
Severity 936207 serious
thanks
biosig4c++ build-depends on the python-pkgconfig binary package which is no
longer built by the python-pkgconfig source package.
Severity 937657 serious
thanks
python-colormap depends on the python-easydev binary package which is no longer
built by the python-easydev source package.
Package: python-easydev
Version: 0.9.38-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: squid
Version: 4.8-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.
I notice that in addition to the complaints about nettle deprecation there is
also a complaint about the use of memmove, unfortunately the compiler doesn't
say what exactly it doesn't like about the use of memmove.
In raspbian I decided to go ahead and remove -Werror, a debdiff doing that
tags 943566 +patch
thanks
Currently the nettle 3.5.1 transition is going on. I tried to binNMU
your package but it fails to build from source on all architectures.
I had a fiddle around with the order of includes and this led me to some
different error messages which led me to the real
Package: stressant
Version: 0.5.0
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 936704 serious
thanks
python-colormap depends on the python-easydev binary package which is no longer
built by the python-easydev source package.
severity 938573 serious
thanks
stressant depends on the python-colorlog binary package, which is no longer
built by the python-colorlog source package.
severity 937720 serious
thanks
python-easydev depends on the python-colorlog binary package which is no longer
built by the python-colorlog source package.
Package: google-cloud-print-connector
Version: 1.12.1
Severity: serious
Tags: bullseye, sid
After uploading my fix for 942331 to Raspbian bullseye I discovered another
problem. The dependency on libsnmp30 is hardcoded.
In raspbian I have just gone ahead and changed the dependency. a debdiff
tags 942331 +patch
thanks
Your package is part of the libsnmp transition. During a rebuild your package
FTBFS on all architectures.
Reading the log more thoroughly it seems the actual failure is cups related.
cgo-gcc-prolog:95:2: warning: ‘cupsGetPPD3’ is deprecated: Use cupsCopyDestInfo
Package: python-fabio
Version: 0.9.0+dfsg-2
Severity: serious
Python-fabio's autopkgtest is failing,
==
ERROR: testFullFormatName (fabio.test.testfabioconvert.TestFabioConvert)
On 20/10/2019 00:15, Robie Basak wrote:
On Sat, Oct 19, 2019 at 11:59:45PM +0200, Nicolas Dandrimont wrote:
2. while python3-trio has passed new, it's maintainer (Robie Basak) has filed a
RC bug saying he does not belive it is currently suitable for a stable release.
In part I just followed
Package: gtk-d
Version: 3.9.0-2
Severity: serious
The issue with gtk-d trying to build with the wrong compiler on gdc
architectures (most notablly armhf, which until recently was an ldc
architecture) has now been fixed, unfortunately it is still failling to build,
this time with a bunch of
On 17/10/2019 22:23, PICCA Frederic-Emmanuel wrote:
ok, but this packages comes from NEW.
So it would be nice if the process NEW -> unstable could be a source upload.
Ir is not possible to upload without the binary in New.
This processus necessitate two uploads if I understand correctly.
Package: repmgr
Version: 5.0.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 your package can migrate.
Package: sardana
Version: 3.0.0a+3.f4f89e+dfsg-1
Severity: serious
The release team have decreed that non-buildd binaries cannot migrate to
testing. Please make a source-only upload so your package can migrate.
severity 938500
thanks
smalr depends on python-h5py which has already been dropped by the h5py source
package.
severity 938481 serious
thanks
silx depends on python-h5py which has already been dropped by the h5py source
package.
severity 934868 serious
thanks
python-pynwb depends on python-h5py, which is no longer built by the h5py
source package.
unfortunately it seems hdmf is still stuck in new, can you go ahead with
uploading the python2 removal with the current version?
severity 937256 serious
thanks
python-pbh5tools depends on python-h5py which has already been dropped by the
h5py source package.
severity 937255 serious
thanks
python-pbgenomicconsensus depends on python-h5py which has already been dropped
by the h5py source package.
severity 937945 serious
thanks
python-neuroshare depends on python-h5py which has already been dropped by the
h5py source package.
severity 936797 serious
thanks
python-kineticstools depends on python-h5py which has already been dropped by
the h5py source package.
severity 937745 serious
thanks
python-fabio depends on python-h5py which has already been dropped by the h5py
source package.
severity 937258 serious
thanks
pbsuite depends on python-h5py which has already been dropped by the h5py
source package.
Severity 937253 serious
thanks
pbbarcode depends on python-h5py, which has already been dropped by the h5py
source package.
severity 938015 serious
block 938816 by 938015
thanks
python-pecan build-depends on python-webtest, which depends on python-waitress,
which is no longer built by the waitress source package.
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
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
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
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
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
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
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
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
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" code
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(
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
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
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(
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
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
801 - 900 of 2740 matches
Mail list logo
