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
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.
package: vmtk
severity: serious
version: 1.3+dfsg-2.3
vmtk build-depends on libvtk6-java which is no longer built by the vtk6
source package.
package: libgeotiff\
version: 1.5.1-1
severity: serious
tags: bullseye
Hi, libgeotiff just failed to build in raspbian bullseye with the
following message.
Running ../test/testlistgeo using ../bin/listgeo:
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
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
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: python-os-net-config
Version: 0.1.0-1
Severity: serious
Tags: bullseye, sid
python-os-net-config (build-)depends on the python-oslo.config binary
package which is no longer built by the corresponding source package.
I see no reverse-depends, should this package simply be removed?
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':
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)
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: 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 (
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
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
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.
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.
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
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
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.
Package: python-etcd3gw
Version: 0.2.1-1
Severity: serious
Tags: patch, bullseye, sid
python-etcd3gw (build-)depends on the python-futurist binary package which is
no longer built by the corresponding source package.
It's probably time to drop python 2 support from this package. I notice that
Package: python-shade
Version: 1.30.0-2
Severity: serious
Tags: bullseye, sid
python-shade (build-)depends on the python-os-client-config and
python-openstacksdk binary packages which are no longer built by the
corresponding source packages.
It looks like it's time to drop python2 support
Package: python-cutadapt
Severity: serious
Version: 2.4-1
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: python-dnaio
Severity: serious
Version: 0.3-1
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: python-os-testr
Version: 1.0.0-4
Severity: serious
Tags: bullseye, sid
The python-os-testr source package build-depends on the python-stestr binary
package and the python-os-testdir binary package depends on it. The
python-stestr binary package is no longer built by the python-stestr
Package: python-tuskarclient
Severity: serious
Version: 0.1.18-1
Tags: bullseye, sid
python-tuskarclient depends on the python-cliff, python-keystoneclient,
python-openstackclient and python-stevedore binary packages which are no
longer built by the corresponding source packages.
If this is
Package: firefox-esr
Version: 60.8.0esr-1
Severity: serious
x-debbugs-cc: pkg-rust-maintain...@alioth-lists.debian.net
While trying to update firefox-esr in raspbian bullseye I ran into a
"failed to open: /sbuild-nonexistent/.cargo/.package-cache" error. The
failure also shows up on the
Package: mini-buildd
Version: 1.0.41
Severity: serious
python-mini-buildd depends on and the mini-buildd source package
build-depends on the python-django-registration binary package which is
no longer built by the python-django-registration source package.
I notice this already seems to be
Package: oz
Version: 0.16.0-2
Severity: serious
Tags: bullseye, sid
oz depends on the python-monotonic binary package which is no longer
built by the python-monotonic source package.
Package: lua-geoip
Version: 0.1.2+git20160613-3
Severity: serious
Tags: bullseye, sid
lua-geoip depends on geoip-database-extra which is no longer built by
the geoip-database source package.
Package: python-os-cloud-config
Severity: serious
Tags: bullseye, sid
python-os-cloud-config depends on a number of binary packages that are
no longer built by their corresponding source packages, including
python-glanceclient
python-ironicclient
python-keystoneclient
python-neutronclient
Package: d-shlibs
Version: 0.85
Severity: serious
The release team have decreed that binaries not built on buildds can no
longer migrate to testing. Please make a source only upload so the fix
for 932632 can migrate to testing.
Tags 914151 +patch
Thanks
This turned out to be a simple case of a missing include, a debdiff can be
found at
https://debdiffs.raspbian.org/main/d/dlz-ldap-enum/dlz-ldap-enum_1.1.0-1%2Brpi1.debdiff
. No intent to NMU in Debian.
Package: quagga
Version: 1.2.4-3
Tags: bullseye, sid, patch
Severity: serious
quagga build-depends on texlive-generic-reccomended which is no longer built by
the texlive-base source package. Please build-depend on texlive-plain-generic
instead.
Package: octave
Version: 3.5.2-1
Tags: bullseye, sid, patch
Severity: serious
octave build-depends on texlive-generic-reccomended which is no longer built by
the texlive-base source package. Please build-depend on texlive-plain-generic
instead.
Package: r-base
Version: 3.5.2-1
Tags: bullseye, sid, patch
Severity: serious
r-base build-depends on texlive-generic-reccomended which is no longer built by
the texlive-base source package. Please build-depend on texlive-plain-generic
instead.
Package: pspp
Version: 3.5.2-1
Tags: bullseye, sid, patch
Severity: serious
pspp build-depends on texlive-generic-reccomended which is no longer built by
the texlive-base source package. Please build-depend on texlive-plain-generic
instead.
Package: gri
Version: 3.5.2-1
Tags: bullseye, sid, patch
Severity: serious
gri build-depends on texlive-generic-reccomended which is no longer built by
the texlive-base source package. Please build-depend on texlive-plain-generic
instead.
Package: vistrails
Severity: serious
Version: 2.2.4-1
Tags: bullseye, sid
vistrails depends on python-usagestats which is no longer built by the
usagestats source package.
If you want your Package to remain in Debian you probablly need to migrate to
python3.
Package: librust-docopt-dev
Version: 1.0.2-1
Severity: serious
Tags: buster, sid
librust-docopt-dev depends on the virtual package
librust-strsim-0.7+default-dev which is no longer provider by
librust-strsim-dev. The virtual package seems to have been renamed to
Package: swift-bench
Severity: serious
Tags: bullseye, sid
swift-bench (build-)depends on the python-swiftclient binary package which is
no longer built by the python-swiftclient source package.
You probably need to migrate to python3
Package: swauth
Severity: serious
Tags: bullseye, sid
swauth (build-)depends on the python-swiftclient binary package which is no
longer built by the python-swiftclient source package.
You probably need to migrate to python3
Package: s3ql
Version: 3.2+dfsg-1
Severity: serious
Tags: patch
s3ql build-depends on the obsolete transitional package texlive-generic-extra ,
please build-depend on texlive-plain-generic instead.
I have succesfully built a package for raspbian bullseye with this change. A
debdiff should
package: python-crontab
severity: serious
version: 1.9.3-2
tags: bullseye,sid
python-crontab (build-)depends on the python-croniter binary package which is
no longer built by the python-croniter source package.
It's probablly time to drop python 2 support from your package.
Package: elastalert
Version: 0.1.29-1
Severity: serious
Tags: bullseye, sid
elastalert (build-)depends on the python-croniter binary package which is no
longer built by the python-croniter binary package.
If you want to keep your package in Debian you will probablly need to migrate
to python
package: kombu
severity: serious
tags: bullseye , sid
python-kombu depends on and kombu build-depends on the python-aqmp binary
package which is no longer built by the python-aqmp source package.
package: firefox-esr
version: 60.8.0esr-1
severity: serious
While trying to update firefox-esr in raspbian bullseye I ran into a "possible zip
bomb" error. The failure also shows up on the reproducible builds site for i386 and
arm64 so it's not raspbian specific.
warning
retitle 932186 mediawiki2latex depends on cruft package.
thanks
(sorry for screwing up the mail subject)
On 16/07/2019 18:48, Dirk Hünniger wrote:
I can take care of the issue. There is a list of required LaTeX packages in the
INSTALL file in the root directory of the package. Still to do
Package: stex
Version: 1.2.1+git20171204.g5e4f0ca-3
Tags: bullseye, sid
Severity: serious
stex depends on texlive-generic-recommended which is no longer built by
texlive-base. texlive-generic-reccomended seems to be a transitional package so
presumablly you just need to update your dependency.
Package: stex
Version: 1.2.1+git20171204.g5e4f0ca-3
Tags: bullseye, sid
Severity: serious
stex depends on texlive-generic-recommended which is no longer built by
texlive-base. texlive-generic-reccomended seems to be a transitional package so
presumablly you just need to update your dependency.
Package: mediawiki2latex
Version: 7.33-1
Tags: bullseye, sid
Severity: serious
mediawiki2latex depends on texlive-generic-recommended which is no longer built
by texlive-base. texlive-generic-reccomended seems to be a transitional package
so presumablly you just need to update your dependency.
Package: djangorestframework-gis
Severity: serious
Tags: buster, sid
djangorestframework-gis build-depends on python-django-filters and
python-djangorestframework-gis depends on it. python-django-filters is no
longer built by the django-filter source package.
It's probably time to drop
On 13/06/19 10:00, Thomas Calderon wrote:
Hi there,
It's unfortunate that OCaml has removed the support for ocamlopt for armel, it
sounds like CamlCrush will not be able to ship for armel.
Is it required that I create an updated Debian release excluding armel as a
target or as you said,
nput sanitization in
the next couple of days.
G'luck,
Peter
--
Peter Pentchev roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
signature.asc
Description: PGP signature
package: node-regexpu-core
version: 4.4.0+ds-1
severity: serious
node-regexpu-core build-depends on node-unicode-11.0.0 which is no
longer built by source package node-unicode-data. It appears to have
been replaced by node-unicode-12.0.0
package: node-regenerate-unicode-properties
version: 7.0.0+ds-1
severity: serious
node-regenerate-unicode-properties build-depends on node-unicode-11.0.0
which is no longer built by source package node-unicode-data. It appears
to have been replaced by node-unicode-12.0.0
package: acorn
version: 5.5.3+ds3-2
severity: serious
acorn build-depends on node-unicode-11.0.0 which is no longer built by
source package node-unicode-data. It appears to have been replaced by
node-unicode-12.0.0
eing overloaded by people pointing their CI at it, by
jigdo using it as it primary backends, and other abuses.
We are, in our limited time, trying to keep it working, but we don't
always succeed.
--
| .''`. ** Debian **
Peter Palfrader | : :' :
(note: I'm just someone taking a look to see what is blocking the unicode-data
"transition", i'm not a maintainer of this package or a member of the release
team).
unicode-data 12.0.0 is now in unstable/testing (Buster).
gucharmap FTBFS with this;
It seems upstream have updated gucharmap
On Thu, 09 May 2019, Peter Palfrader wrote:
> I plan to revert the -5 change from this bug which has also been
> reverted in the stretch upload.
uploaded to delayed 5.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
+in 1.36-3+deb9u2.
+There is no point in creating a /var/run/postgrey/ to hold the pidfile
+as using /var/run/postgrey.pid seems to work just fine.
+
+ -- Peter Palfrader Thu, 09 May 2019 13:35:38 +0200
+
postgrey (1.36-5) unstable; urgency=medium
* debian/postgrey.init: create
So,
since this bug has been reopened without comments, here's what appears
to be the status:
currently stretch has 1.36-3+deb9u2 and sid has 1.36-5.
According to the changelog, stretch get a patch in -3+deb9u1 which was
reverted in -3+deb9u2.
sid got that patch in -5, no revert.
--
Peter
Could you please check if it is still valid and happening in Debian
unstable there has had several updates MariaDB client libraries /
connector C libraries recently?
According to
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/opensips.html
it is still failing in the same
Am 01.04.19 um 12:40 schrieb Frank Neuber:
Dear Peter,
this bug is fixed in SP13.
The version in the debian repo is SP9 and quite old.
http://support.reiner-sct.de/downloads/LINUX/V3.99.5_SP13/pcsc-cyberjack_3.99.5final.SP13.tar.gz
http://support.reiner-sct.de/downloads/LINUX/V3.99.5_SP13
/LudovicRousseau/PCSC/issues/22
and (in German)
https://forum.reiner-sct.com/index.php?/topic/3728-failed_to_transmit_control_command_to_the_terminal
Both references point to a patch for this problem.
Peter
-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4
Package: matrix-synapse
Version: 0.99.2-2
Followup-For: Bug #920339
Still exists in the recent version. It seems that the server is spawned and
disowned, and the configure script waits forever for some return value which
never
comes.
Also this output is not really happy:
Setting up
ave forgotten how to switch to a shell when d-i is
running on a serial port :-D, so I gave up. It worked perfectly up until
that moment.
HTH,
Peter.
--
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is avail
Package: oggvideotools
Version: 0.9.1-4.1
Severity: serious
Tags: patch
oggvideotools FTBFS in buster. I first noticed this in raspbian, but it's also
visible on the reproducible builds tests.
http://buildd.raspbian.org/status/fetch.php?pkg=oggvideotools=armhf=0.9.1-4.1=1552572977
stly, I would prefer some kind of change in init-functions that
would let me continue to use the LSB shell functions. Even if it means
passing an additional argument to killproc to make it use --exec, this
would still be an acceptable divergence from upstream for me.
> > This bug is current
the new 4.9.144-3.1.
Thanks,
Peter.
-- System Information:
Debian Release: 9.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 4.9.0-8-armmp (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap
Control: tag -1 pending
Hello,
Bug #919340 in fenix-plugins reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: rust-ripgrep
Version: 0.10.0-1
Severity: serious
While performing a test build on s390x to see if bug 916615 was actually fixed
I ran into a new error. I then did a test build on amd64 and was able to reduce
the same testsuite failure, so this doesn't seem to be architecture specific.
uests/1
I also submitted another merge request to import the ppp-2.4.7 upstream
tarball's data into the pristine-tar branch:
https://salsa.debian.org/debian/ppp/merge_requests/2
Thanks to everyone for taking care of ppp in Debian!
G'luck,
Peter
--
Peter Pentchev roam@{ringlet.net,debian.org
) UNRELEASED; urgency=medium
+
+ * Use a temporary directory under the package build directory
+(avoids issues when multiple people build the package on the same machine)
+
+ -- Peter Michael Green Thu, 07 Feb 2019 22:48:11 +
+
rust-ripgrep (0.10.0-1) unstable; urgency=medium
* Package
Since upstream claimed this issue could not be reproduced, I decided to run a
test on zelenka.debian.org
The build did fail with a testsuite failure, but it looked nothing like the one in the
buildd log. Rather than most tests passing and a few failing most tests failed, I looked
at a few of
/changelog 2019-01-26 08:36:22.0 +
+++ ntopng-3.8+dfsg1/debian/changelog 2019-02-04 01:10:39.0 +
@@ -1,3 +1,10 @@
+ntopng (3.8+dfsg1-2.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Add build-depends on libssl-dev (Closes: 920648)
+
+ -- Peter Michael Green
tags 919742 +patch
thanks
Since this seemed to be the last thing blocking the dcmtk transition in
raspbian buster I decided to take a look.
It seems that orthanc-wsi has an embedded copy of an old version orthanc, it
also build-depends on orthanc-dev,
I am not sure if the system orthanc is
+(keep it in python3-gpiozero package) (Closes: #919617)
+ * Fix misspelling in package discrptions Raspoberry -> Raspberry
+
+ -- Peter Michael Green Thu, 24 Jan 2019 14:45:24 +
+
gpiozero (1.4.1-1) unstable; urgency=medium
* Move to Salsa.
diff -Nru gpiozero-1.4.1/debian/control g
tags 856413 +pending
tags 919617 +patch +pending
tags 919620 +patch +pending
thanks
I have now prepared a NMU for gpiozero addressing bugs 856413, 919617 and
919620. I have uploaded this NMU to delayed/10. A debdiff is attatched to this
mail.
Please tell me if you see any issues with this NMU
Package: sagemath
Version: 8.4-2
Severity: serious
sagemath versions from 8.4-2 through to 8.6-2 have failed to build on mipsel
and mips64el.
mipsel is failing with
Success: 42 tests failed, up to 90 failures are tolerated
Error: critical test failures (e.g. timeout, segfault, etc.)
make[2]:
package: ntomng
version: 2.4+dfsg1-4
severity: serious
ntopng fails to build from source with the new ndpi, which recently migrated to testing.
This affects both the version in buster (as evidenced by the raspbian binnmu
Control: tag -1 pending
Hello,
Bug #917493 in fenix reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: libreoffice
Version: 1:6.1.4-1
Severity: serious
The arch all build for libreoffice 1:6.1.5~rc1-1 (
https://buildd.debian.org/status/fetch.php?pkg=libreoffice=all=1%3A6.1.5%7Erc1-1=1547977527=0
) failed with
javadoc: error - The code being documented uses modules but the packages
Package: mariadb-10.1
Version: 1:10.1.37-3
Severity: serious
During rebuilds for the jemalloc transition mariadb-10.1 failed to build on
most architectures with the following error on most architectures ().
Completed: Failed 2/4906 tests, 99.96% were successful.
Failing test(s):
Package: orthanc-wsi
Severity: serious
Version: 0.5-2
orthanc-wsi fails to build in unstable, I presume this was triggered by the
dcmtk transition.
https://buildd.debian.org/status/fetch.php?pkg=orthanc-wsi=amd64=0.5-2%2Bb3=1547409452=0
Package: dicomscope
Version: 3.6.0-19
Severity: serious
dicomscope FTBFS in sid, I presume this is the result of the dcmtk transition
but I am not 100% positive.
/<>/interface/libsrc/DVInterface.cpp: In function '_jstring*
Java_J2Ci_jDVInterface_getTargetCipherSuite(JNIEnv*, jobject,
801 - 900 of 3600 matches
Mail list logo