Processed: RFS: doxygen/1.8.15-1 [ITA]
Processing control commands: > severity 921295 important Bug #921295 [src:wcslib] wcslib: FTBFS with upcoming doxygen 1.8.15 Severity set to 'important' from 'serious' > severity -1 normal Bug #919413 [sponsorship-requests] RFS: doxygen/1.8.15-1 [ITA] Severity set to 'normal' from 'important' -- 919413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919413 921295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921176: redis-server service is failing to start in buster lxc container
On 2019, ഫെബ്രുവരി 4 1:20:11 PM IST, Chris Lamb wrote: >Hi, > >> redis-server service is failing to start in buster lxc container > >Any update on this? :) I'm traveling. hopefully tonight or tomorrow night I can try. Adding Raju, and Abhijith, who may be able to try this before. > >Regards, -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#918623: dizzy: Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT
Hi Florian, > It's probably a bit late in the release cycle to "just find out" by > uploading a -2 with that modified patch. ... but its even worse to do nothing since this is an RC bug and this package as well as its rdepends would be excluded from next release if the bug is not fixed. Kind regards Andreas. -- http://fam-tille.de
Bug#921320: ruby-rspec-rails build depends on ruby-capybara (>= 2.15~) that is currently not in buster
Source: ruby-rspec-rails Version: 3.8.1-2 Severity: serious Tags: ftbfs Control: block -1 by 900156 ruby-rspec-rails build depends on ruby-capybara (>= 2.15~) that is currently not in buster due to #900156.
Bug#921315: samtools: baseline violation on i386
On Mon, 04 Feb 2019 08:43:08 +0200 Adrian Bunk wrote: > Source: samtools > Version: 1.9-2 > Severity: serious > Tags: patch > > SSE is not part of the i386 baseline, fix: > > --- debian/rules.old 2019-02-03 20:43:51.747130097 + > +++ debian/rules 2019-02-03 20:44:04.383129977 + > @@ -5,7 +5,7 @@ > > export DEB_BUILD_MAINT_OPTIONS=hardening=+all > ifneq (,$(filter $(DEB_HOST_ARCH),i386 kfreebsd-i386 hurd-i386)) > - export DEB_CFLAGS_MAINT_APPEND=-msse -mfpmath=sse > + export DEB_CFLAGS_MAINT_APPEND=-ffloat-store Very cool, I did not know about this option; thank you! > endif > > %: > >
Bug#921316: python3-sqt: Depends: python3 (< 3.6) but 3.7.2-1 is to be installed
Hi Adrian, On Mon, Feb 04, 2019 at 09:01:55AM +0200, Adrian Bunk wrote: > The following packages have unmet dependencies: > python3-sqt : Depends: python3 (< 3.6) but 3.7.2-1 is to be installed > > Was this binary built in an old/outdated chroot with Python 3.6 > as default? I'm always using up to date chroot. The only reason might be that I accidentally have build for stretch backport? Just re-uploading. Thanks a lot for your extremely valuable QA work Andreas. -- http://fam-tille.de
Processed: ruby-rspec-rails build depends on ruby-capybara (>= 2.15~) that is currently not in buster
Processing control commands: > block -1 by 900156 Bug #921320 [src:ruby-rspec-rails] ruby-rspec-rails build depends on ruby-capybara (>= 2.15~) that is currently not in buster 921320 was not blocked by any bugs. 921320 was not blocking any bugs. Added blocking bug(s) of 921320: 900156 and 907022 -- 921320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921316: marked as done (python3-sqt: Depends: python3 (< 3.6) but 3.7.2-1 is to be installed)
Your message dated Mon, 04 Feb 2019 08:45:01 + with message-id and subject line Bug#921316: fixed in python-sqt 0.8.0-3 has caused the Debian Bug report #921316, regarding python3-sqt: Depends: python3 (< 3.6) but 3.7.2-1 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-sqt Version: 0.8.0-2 Severity: serious The following packages have unmet dependencies: python3-sqt : Depends: python3 (< 3.6) but 3.7.2-1 is to be installed Was this binary built in an old/outdated chroot with Python 3.6 as default? --- End Message --- --- Begin Message --- Source: python-sqt Source-Version: 0.8.0-3 We believe that the bug you reported is fixed in the latest version of python-sqt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-sqt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Feb 2019 09:14:28 +0100 Source: python-sqt Binary: python3-sqt Architecture: source Version: 0.8.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: python3-sqt - SeQuencing Tools for biological DNA/RNA high-throughput data Closes: 921316 Changes: python-sqt (0.8.0-3) unstable; urgency=medium . * Team upload. * Rebuild Closes: #921316 Checksums-Sha1: 2f0ba898482da437210f481f80b323550468e1f6 2136 python-sqt_0.8.0-3.dsc d933efea03a4bbdce2aa7dee1fe794bb32919909 4828 python-sqt_0.8.0-3.debian.tar.xz Checksums-Sha256: b709d5d9969246b6518351b142a39d87a79eefadbd554caaadae8c6587177ef8 2136 python-sqt_0.8.0-3.dsc 8b0b49efc4d139f9c9fb6270e78058892bb5c6504679d9e608e84092ffd8948e 4828 python-sqt_0.8.0-3.debian.tar.xz Files: 16a70a7ab570f9b4585756f6ea8a4be5 2136 science optional python-sqt_0.8.0-3.dsc 991501ebdbcd8365618c1714017bcf3d 4828 science optional python-sqt_0.8.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxX9gYRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGvqw/+PG1RMSWLqPcA6Q6h155Jw22qzma21U4e L9y8p+LV1b7q57lSTMUkjkK5v7xa0VI3PFcldE6BlMZ1nkkf2AJCN0RLBBSGEBP4 +4G9bkqC9ZvtMJVM/QmUhemXGOvVMQaQeSitqauYK8f3uTmB8Bwre2ND21fsctiG 4u4GpO/w1Z89w6gp5CAfo6rsseix7s7cf1bLkI30Gj/aN1itKLNC7rnbQZme/HjT Pgr5UVSDsHb7zojVScclrqdrks0xRvZ70DFeU7yGBATPA5Htj6aJTecGo0GDwT+/ Dg05ApSpFP9tE3sGP8CS+h6YYOI8hJiBTs4IvrHc3EbLtog7lIm3/rvx3V+bD2V9 0Ja7kqYMuAxl96AFhWiTLj3TPPLQfHkPWjdN98P46rb7YdbyvYV6AoKrMJsKkjp6 lPXT250vBCA7sT2/9sueU66+ZBfhEe0ptSZf1n1BNHLFbCd+maI0gVkun+iwj+6F aw79qy38N20Brw3/i39esTqH0LgqDrWov9SeOSi7NSYppJfKfWycfLAaczZCSxbr YdbyCKj8hRquB6ia4YzH2zgXfqZERN4ykcT5LqIpdxz9Ydr1nXSM6YBRiIBb0SiW sdfaHUehWeopi5kGWDedJQzPWmiMHFfUw8Bj7DyTwn5yj+PX32crDwZZDduzQvxR BRsUbZ5abYA= =05yJ -END PGP SIGNATURE End Message ---
Bug#915266: marked as done (python-wither FTBFS with Pyrhon 3.7)
Your message dated Mon, 04 Feb 2019 08:45:07 +
with message-id
and subject line Bug#915266: fixed in python-wither 1.1-2
has caused the Debian Bug report #915266,
regarding python-wither FTBFS with Pyrhon 3.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
915266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-wither
Version: 1.1-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-wither.html
...
cd . && python3 setup.py build
--build-base="/build/1st/python-wither-1.1/./build"
Warning: 'classifiers' should be a list, got type 'NoneType'
Traceback (most recent call last):
File "setup.py", line 75, in
cmdclass = {'test': PyTest},
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 140, in
setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3.7/distutils/core.py", line 108, in setup
_setup_distribution = dist = klass(attrs)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 370, in
__init__
k: v for k, v in attrs.items()
File "/usr/lib/python3.7/distutils/dist.py", line 267, in __init__
getattr(self.metadata, "set_" + key)(val)
File "/usr/lib/python3.7/distutils/dist.py", line 1215, in set_classifiers
self.classifiers = _ensure_list(value, 'classifiers')
File "/usr/lib/python3.7/distutils/dist.py", line 40, in _ensure_list
value = list(value)
TypeError: 'NoneType' object is not iterable
make: *** [/usr/share/cdbs/1/class/python-distutils.mk:78:
debian/python-module-stampdir/python3-wither] Error 1
--- End Message ---
--- Begin Message ---
Source: python-wither
Source-Version: 1.1-2
We believe that the bug you reported is fixed in the latest version of
python-wither, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated python-wither package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 04 Feb 2019 09:13:09 +0100
Source: python-wither
Binary: python3-wither
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Mike Gabriel
Description:
python3-wither - XML/HTML Generation DSL (Python 3)
Closes: 915266
Changes:
python-wither (1.1-2) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/control: Set Vcs-* to salsa.debian.org
* d/copyright: Use https protocol in Format field
* d/watch: Use https protocol
* d/control: Remove ancient X-Python3-Version field
.
[ Mike Gabriel ]
* debian/patches:
+ Add 1001_fix-ftbfs-py3-7.patch. Fix FTBFS against recent distutils in
Python 3.7. (Closes: #915266).
* debian/control:
+ Bump Standards-Version: to 4.3.0. No changes needed.
Checksums-Sha1:
a25d61dd97d64d56655869aa586ac64e89d93a17 2079 python-wither_1.1-2.dsc
5ca03aada01719e411b9b172b62bb555c7c2c7c0 2840 python-wither_1.1-2.debian.tar.xz
f8d47419dcc0232a4b17a8b5c806104ff78f80d8 6773
python-wither_1.1-2_source.buildinfo
Checksums-Sha256:
8314b8d5f4ee3d51e8327e78deb080c9eab5f753703b0ad1c75e12707dd870ce 2079
python-wither_1.1-2.dsc
c6159e170b3cefc92a6e3f2f1e044a2d9c364510991e579af830aa9ba622a34b 2840
python-wither_1.1-2.debian.tar.xz
2318e2227f10844b8b0a8329c73cce8c1dd800187120698a4a541caaeeaeac00 6773
python-wither_1.1-2_source.buildinfo
Files:
efb355361d5825bc6b6563ff66a63d33 2079 python optional python-wither_1.1-2.dsc
564d92766b1892140facee29ee96f63e 2840 python optional
python-wither_1.1-2.debian.tar.xz
aafba4882307f40d5dcbe96b50a2d42f 6773 python optional
python-wither_1.1-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAlxX9I8VHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxSD4P/jTnAaYXeZloxBc7t/fYkXC1x/Hp
Fk/yBw2ZwP0igwBmKVC6t+O81qKCmAUI0khp0sHnz9qwBc/HmHPmttihSQjc9T8d
qLITU/I58P0DXWHvP97SGNVze9N7jrgmrOJAibDKmFRNTd8UnQ18ffvEKKZ8EdUb
IEuJMD1IEVDU/nJS139skSG9TjWAh2Pc2drrMiFph5aoTyDTuS0ZJuyqfGM7nRpn
daaY/MtDvyXdRZ6MzmDLrLi0F+BeycZU9XWMWWW23
Bug#919189: Fwd: probabel FTBFS on arm64, likely due to Eigen 3 NEON code
Dear all, As one of the developers of ProbABEL I can confirm this is a rounding error. We have had similar problems in the past. The test run by make is simply diff-ing the output of a test run with a 'known good' file. Back when ProbABEL was still actively developed, I tried my best to maintain accuracy across the platforms I knew were being actively used by our users. ARM and PPC where never among those, neither did I have access to machines with that architecture. All in all I think either of Andreas' proposed solutions is fine. Best regards, Lennart. On 02-02-19 12:19, Andreas Tille wrote: > On Sat, Feb 02, 2019 at 11:56:50AM +0100, Thierry fa...@linux.ibm.com wrote: >> Hi, >> >> Thanks for pointing out that my analysis wasn't good - the arm patch >> doesn't change anything for ppc64el (which make sense whatsoever) - the >> problem on ppc64el is similar to the one on arm except the test value >> are opposite ! ( which was confusing). >> So what do we need to do ? expect that someone with a better expertise >> help going though it ? ( can you confirm we stay with that bug for both >> arch or do we need to open one for ppc64el ?) > > As long as we are sure that its just a rounding error I think an apropriate > solution would be to ignore the error for ppc64el (either exclude the test > or run > > dh_auto_test || true > > to be able to inspect the log. > > Do you think that's in your interest? > > Kind regards > > Andreas. > -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* L.C. Karssen 's-Hertogenbosch The Netherlands lenn...@karssen.org http://blog.karssen.org GPG key ID: A88F554A -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- signature.asc Description: OpenPGP digital signature
Bug#921324: astropy-healpix FTBFS on i386: test filure
Source: astropy-healpix
Version: 0.4-4
Severity: serious
Tags: ftbfs patch
https://buildd.debian.org/status/fetch.php?pkg=astropy-healpix&arch=i386&ver=0.4-4&stamp=1548693347&raw=0
...
=== FAILURES ===
___ test_boundaries
@given(nside_pow=integers(0, 29), step=integers(1, 10), nest=booleans(),
> frac=floats(0, 1, allow_nan=False,
> allow_infinity=False).filter(lambda x: x < 1))
astropy_healpix/tests/test_healpy.py:185:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/hypothesis/core.py:519: in execute
result = self.test_runner(data, run)
/usr/lib/python3/dist-packages/hypothesis/executors.py:58: in
default_new_style_executor
return function(data)
/usr/lib/python3/dist-packages/hypothesis/core.py:517: in run
return test(*args, **kwargs)
astropy_healpix/tests/test_healpy.py:185: in test_boundaries
frac=floats(0, 1, allow_nan=False, allow_infinity=False).filter(lambda x: x
< 1))
/usr/lib/python3/dist-packages/hypothesis/core.py:464: in test
result = self.test(*args, **kwargs)
astropy_healpix/tests/test_healpy.py:190: in test_boundaries
b1 = hp_compat.boundaries(nside, pix, step=step, nest=nest)
astropy_healpix/healpy.py:152: in boundaries
lon, lat = boundaries_lonlat(pix, step, nside, order='nested' if nest else
'ring')
astropy_healpix/core.py:673: in boundaries_lonlat
lon, lat = healpix_to_lonlat(healpix_index.ravel(), nside, dx.ravel(),
dy.ravel(), order=order)
astropy_healpix/core.py:393: in healpix_to_lonlat
lat = Latitude(lat, unit=u.rad, copy=False)
/usr/lib/python3/dist-packages/astropy/coordinates/angles.py:514: in __new__
self._validate_angles()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
angles =
def _validate_angles(self, angles=None):
"""Check that angles are between -90 and 90 degrees.
If not given, the check is done on the object itself"""
# Convert the lower and upper bounds to the "native" unit of
# this angle. This limits multiplication to two values,
# rather than the N values in `self.value`. Also, the
# comparison is performed on raw arrays, rather than Quantity
# objects, for speed.
if angles is None:
angles = self
lower = u.degree.to(angles.unit, -90.0)
upper = u.degree.to(angles.unit, 90.0)
if np.any(angles.value < lower) or np.any(angles.value > upper):
raise ValueError('Latitude angle(s) must be within -90 deg <= angle
<= 90 deg, '
>'got {0}'.format(angles.to(u.degree)))
E ValueError: Latitude angle(s) must be within -90 deg <= angle <= 90
deg, got [ 0.-41.8103149 -90.-41.8103149] deg
/usr/lib/python3/dist-packages/astropy/coordinates/angles.py:531: ValueError
-- Hypothesis --
Falsifying example: test_boundaries(nside_pow=0, frac=0.,
step=1, nest=False)
1 failed, 124 passed in 24.30 seconds =
/usr/lib/python3/dist-packages/astropy/config/configuration.py:536:
ConfigurationMissingWarning: Configuration defaults will be used due to
FileNotFoundError:2 on None
warn(ConfigurationMissingWarning(msg))
make[1]: *** [debian/rules:17: test-python3.7] Error 1
Fix:
--- debian/rules.old2019-02-04 09:12:02.674701984 +
+++ debian/rules2019-02-04 09:13:52.286700939 +
@@ -9,6 +9,10 @@
# Astropy-affiliated packages do.
export PYBUILD_AFTER_INSTALL := find {destdir} -name '*.c' -delete
+ifeq ($(DEB_HOST_ARCH),i386)
+ export DEB_CFLAGS_MAINT_APPEND=-ffloat-store
+endif
+
%:
dh $@ --with python3 --buildsystem=pybuild
Bug#921185: marked as done (picard-tools should become Architecture: amd64)
Your message dated Mon, 04 Feb 2019 09:20:37 + with message-id and subject line Bug#921185: fixed in picard-tools 2.18.25+dfsg-2 has caused the Debian Bug report #921185, regarding picard-tools should become Architecture: amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: picard-tools Version: 2.18.25+dfsg-1 Severity: serious The dependency libgkl-java is amd64-only, and the easiest way to fix testing migration as well as being generally correct (what's the point of binary-all when it is only installable on 1 architecture?) is Architecture: all -> amd64 for all packages. --- End Message --- --- Begin Message --- Source: picard-tools Source-Version: 2.18.25+dfsg-2 We believe that the bug you reported is fixed in the latest version of picard-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated picard-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 Feb 2019 08:53:09 +0100 Source: picard-tools Binary: picard-tools libpicard-java libpicard-java-doc Architecture: source Version: 2.18.25+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libpicard-java - Java library to manipulate SAM and BAM files libpicard-java-doc - Documentation for the java picard library picard-tools - Command line tools to manipulate SAM and BAM files Closes: 921185 Changes: picard-tools (2.18.25+dfsg-2) unstable; urgency=medium . * Architecture amd64 (for libpicard-java and picard-tools) Closes: #921185 * Remove trailing whitespace in debian/changelog Checksums-Sha1: e0d87e4ffe0219d2e604c05287d79f75f6f79b4f 2683 picard-tools_2.18.25+dfsg-2.dsc cd5ea0798af010b10eb4554ecb8aea2d38d9b4f6 16836 picard-tools_2.18.25+dfsg-2.debian.tar.xz 30f64bae65f61b4f94b2cf07cd312fc11c737949 21707 picard-tools_2.18.25+dfsg-2_source.buildinfo Checksums-Sha256: 2bfc5cc0be341179e210df23b8533a9be31e3cb378c5f34924d61a7f4ac2e353 2683 picard-tools_2.18.25+dfsg-2.dsc d58ec215994012cf765d26a4278fa475ab563f40ae46e05c3633db46f6f9e479 16836 picard-tools_2.18.25+dfsg-2.debian.tar.xz 183e052b91a13201cd483443f2e1d94d578a00f5d6667961ffbfed4a0ae5cbac 21707 picard-tools_2.18.25+dfsg-2_source.buildinfo Files: 626563e068dab1b2433975ac382b6900 2683 science optional picard-tools_2.18.25+dfsg-2.dsc 1e1029fc6189984cd60a2c1963dbea9b 16836 science optional picard-tools_2.18.25+dfsg-2.debian.tar.xz 564e48e41bddf601afb4aa3556edc8ac 21707 science optional picard-tools_2.18.25+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxYABoOHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtHvHw/+LcvEeWgJUXRVUE7brSMck6oJWmRY9r+RfPDM LJi3GXaLibKMQuaC+ZVhVdvj+ov0xp5l+ox+8R7Nh6RV6vA1p4kiIATiI96lLGto 572cLUqZQO9aFY3X+/4WM9dETVfePOu+fWj1N31CkeKJeSNZ1XWgsBM3QDfISWVa yEuneKqWr97306nnzxkTGcgXVm8vKvAamGRiHolH2V6tSoHPk8atB9zPWmK4w3NG 192xDHXWKBxCuCVJ5vgutCadjmA6fgZ3yWqzQXZDhZcCqXtcCmEJCFa5eLuHDO95 HKR6DFwHiYOM4aUg/DO1e/aGRE7+vmMKus+xtIzcsDoA5nVvE2i0WbAS++CHlWPq usx7nf9rNeZXIzzRj/EYOTxbBLH0JVp9lw94G+/WQi8h4KXpFmCbMxfK4bYxYMF5 J4jds+yGA+KBDbEItSG342L0wbZnq63CAmzJ/6HG4mKrAAM4DiFxsQDP/Ms24NCT u4uDBT/mrqr1Ro0af4fFIFpReCvaiqUsD8v3bxIhtwrSKbEu7a4EJ3JdD8tVKPTB DI17yvn9NKA2YYvHit3xFzjutlUCl1Q70usaw3Zl2WohwoCgX/dE19YYVpX3BfAe dlRGTrbgCN4D2KZVTAXK1ZXRPO6uTWpA4CiBwAP8A8WKjGfts7ZM8EPqbhaVl66F A6WW96Y= =Wt1C -END PGP SIGNATURE End Message ---
Bug#921271: marked as done (buildbot: CVE-2019-7313: CRLF injection in Buildbot login and logout redirect code)
Your message dated Mon, 04 Feb 2019 09:34:23 + with message-id and subject line Bug#921271: fixed in buildbot 2.0.0-1 has caused the Debian Bug report #921271, regarding buildbot: CVE-2019-7313: CRLF injection in Buildbot login and logout redirect code to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: buildbot Version: 1.8.0-1 Severity: grave Tags: security upstream Hi, The following vulnerability was published for buildbot. CVE-2019-7313[0]: | www/resource.py in Buildbot before 1.8.1 allows CRLF injection in the | Location header of /auth/login and /auth/logout via the redirect | parameter. This affects other web sites in the same domain. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-7313 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7313 [1] https://github.com/buildbot/buildbot/wiki/CRLF-injection-in-Buildbot-login-and-logout-redirect-code Regards, Salvatore --- End Message --- --- Begin Message --- Source: buildbot Source-Version: 2.0.0-1 We believe that the bug you reported is fixed in the latest version of buildbot, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robin Jarry (supplier of updated buildbot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Feb 2019 10:06:17 +0100 Source: buildbot Architecture: source Version: 2.0.0-1 Distribution: unstable Urgency: high Maintainer: Python Applications Packaging Team Changed-By: Robin Jarry Closes: 920542 920710 920979 921089 921155 921271 Changes: buildbot (2.0.0-1) unstable; urgency=high . [ Robin Jarry ] * Set buildbot-doc as Multi-Arch: foreign * New upstream version 2.0.0 * [CVE-2019-7313] Fix CRLF injection bug (Closes: #921271) * d/patches: remove 0005-tests-use-explicit-python-executable-path . [ Adriano Rafael Gomes ] * Add debconf translations: Brazilian Portuguese (Closes: #920542) . [ Jean-Pierre Giraud ] * Add debconf translations: French (Closes: #920710) . [ Yangfl ] * Add debconf translations: Chinese (Closes: #920979) . [ Frans Spiesschaert ] * Add debconf translations: Dutch (Closes: #921089) . [ victory ] * Add debconf translations: Japanese (Closes: #921155) Checksums-Sha1: 98fc2eb6a716d89f858b54c3427b1f86877e1a15 3180 buildbot_2.0.0-1.dsc b02205197a239a232060bd84163e370047845d7e 3941061 buildbot_2.0.0.orig.tar.gz 71f7b8d29cf0c8ae00b714e94b45f2f4fd1804be 537 buildbot_2.0.0.orig.tar.gz.asc fca8fc65b45fb75ccedc311df1374b1a55dd6fae 25652 buildbot_2.0.0-1.debian.tar.xz 411d8814e0451f76c434a6259227876f1c4e0597 10290 buildbot_2.0.0-1_amd64.buildinfo Checksums-Sha256: 0afff54741fd4a996c7ee727ab54dc9165efb780ca2a0c00169fccb63cd61dd4 3180 buildbot_2.0.0-1.dsc 51b3e839bf31edada6764d015c1172acef40c10687b350b0dc4338e909e0c586 3941061 buildbot_2.0.0.orig.tar.gz 5a0cb5266e47bdece8106f74c8c8218650682284a180a63e01ba615f38717851 537 buildbot_2.0.0.orig.tar.gz.asc 1b3c02283df6852ae5796918581ce871c48b16424c612f0f42a2598978737aa6 25652 buildbot_2.0.0-1.debian.tar.xz b240e511ea5444a5b7273ff5c4a4f850019bc2caad868c7aea2d9ec93185d827 10290 buildbot_2.0.0-1_amd64.buildinfo Files: bd7f930f2c086dcc794ec38f13272a2f 3180 devel optional buildbot_2.0.0-1.dsc 080faea77fb0427494ef638237025b50 3941061 devel optional buildbot_2.0.0.orig.tar.gz 5d4019019229fbc3789c04e6844a1061 537 devel optional buildbot_2.0.0.orig.tar.gz.asc 8be0875351ffb77f77c5c5d6691ae4a0 25652 devel optional buildbot_2.0.0-1.debian.tar.xz deadd749fe9dc090ab773fb7723ad629 10290 devel optional buildbot_2.0.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlxYAw0ACgkQCBa54Yx2 K608xg//R/eTIrIVL5NlcwPkmimtIR6AZ9yMZt10EL9HbIOjFlM+YS2gYBQo6Y6k QEooy5ZoP5D4jF8eHy93Kym4ulm4q/rePjTdnRNfx+0LKCdPc
Bug#921296: ccfits: FTBFS with upcoming doxygen 1.8.15
On 2019-02-04 01:04, Paolo Greppi wrote: > Source: ccfits > Severity: serious > > Dear Maintainer, > > I tested your package against a draft package for doxygen 1.8.15: > https://bugs.debian.org/919413 > > and it FTBFS with this error: > make[2]: *** [Makefile:8: refman.pdf] Error 1 > That actually looks like a bug in doxygen. CCfits depends on doxygen-latex, which according to its description should provide everything needed: | Package: doxygen-latex | ... | Description-en: Documentation system for C, C++, Java, Python and other languages | Doxygen is a documentation system for C, C++, Java, Objective-C, Python, IDL | and to some extent PHP, C#, and D. It can generate an on-line class browser | (in HTML) and/or an off-line reference manual (in LaTeX) from a set of | documented source files. | . | This dependency package adds dependencies for all LaTeX packages required | to build documents using the default stylesheet. ccfits doesn't do anything fancy, it just generates the latex file using doxygen and then run pdflatex on it. If a dependency is missing for that, it should be added to doxygen-latex. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: retitle 921324 to astropy-healpix FTBFS on i386: test failure
Processing commands for cont...@bugs.debian.org: > retitle 921324 astropy-healpix FTBFS on i386: test failure Bug #921324 [src:astropy-healpix] astropy-healpix FTBFS on i386: test filure Changed Bug title to 'astropy-healpix FTBFS on i386: test failure' from 'astropy-healpix FTBFS on i386: test filure'. > thanks Stopping processing here. Please contact me if you need assistance. -- 921324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#879937: marked as done (libqtdbustest: FTBFS: unit test fails with BadAddress DBusException)
Your message dated Mon, 04 Feb 2019 10:04:17 + with message-id and subject line Bug#879937: fixed in libqtdbustest 0.2+bzr42+repack1-5 has caused the Debian Bug report #879937, regarding libqtdbustest: FTBFS: unit test fails with BadAddress DBusException to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 879937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libqtdbustest Version: 0.2+bzr42+repack1-1 Severity: important Tags: upstream Justification: fails to build from source Builds of libqtdbustest for most architectures failed: [ PASSED ] 4 tests. [ FAILED ] 2 tests, listed below: [ FAILED ] TestDBusTestRunner.StartsSessionService [ FAILED ] TestQProcessDBusService.WaitsForServiceAppeared 2 FAILED TESTS These tests all encountered stack traces along the lines of Traceback (most recent call last): File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib/python3/dist-packages/dbusmock/__main__.py", line 81, in bus = dbusmock.testcase.DBusTestCase.get_dbus(args.system) File "/usr/lib/python3/dist-packages/dbusmock/testcase.py", line 150, in get_dbus return dbus.bus.BusConnection(os.environ['DBUS_SESSION_BUS_ADDRESS']) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.BadAddress: '=' character not found or has no value following it unknown file: Failure C++ exception with description "Process [/usr/bin/python3] for service [test.session.name] failed to appear on bus" thrown in the test body. though in some cases the error was instead dbus.exceptions.DBusException: org.freedesktop.DBus.Error.BadAddress: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") This latter variant occurred for StartsSessionService on armel and for WaitsForServiceAppeared on s390x, as respectively detailed at https://buildd.debian.org/status/fetch.php?pkg=libqtdbustest&arch=armel&ver=0.2%2Bbzr42%2Brepack1-1&stamp=1509080424&raw=0 https://buildd.debian.org/status/fetch.php?pkg=libqtdbustest&arch=s390x&ver=0.2%2Bbzr42%2Brepack1-1&stamp=1509012596&raw=0 I also see errors along these lines in ThrowsErrorForFailToStart, which I suspect is succeeding for the wrong reason. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu --- End Message --- --- Begin Message --- Source: libqtdbustest Source-Version: 0.2+bzr42+repack1-5 We believe that the bug you reported is fixed in the latest version of libqtdbustest, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 879...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated libqtdbustest package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Feb 2019 09:57:33 +0100 Source: libqtdbustest Binary: libqtdbustest1 libqtdbustest1-dev qtdbustest-runner Architecture: source Version: 0.2+bzr42+repack1-5 Distribution: unstable Urgency: medium Maintainer: The Ayatana Packagers Changed-By: Mike Gabriel Description: libqtdbustest1 - Library for testing DBus interactions using Qt libqtdbustest1-dev - Library for testing DBus interactions using Qt (development files qtdbustest-runner - Library for testing DBus interactions using Qt (test runner execu Closes: 879937 Changes: libqtdbustest (0.2+bzr42+repack1-5) unstable; urgency=medium . * debian/control: + Update Vcs-*: fields. Packaging Git has been migrated to salsa.debian.org. * debian/rules: + Ignore test failures. Locally, tests always succeed. Only on Debian's buildd infrastructure, test failures can be observed at random. This is not beautiful, but alas. (Closes:
Bug#917143: t-coffee autopkgtest regression
Hi Andreas, On Sun, 27 Jan 2019 at 16:23, Andreas Tille wrote: > Control: tags -1 help upstream > Control: forwarded -1 https://github.com/cbcrg/tcoffee/issues/13 > > Hi Liubov, > > On Sun, Jan 27, 2019 at 04:06:51PM +0100, Liubov Chuprikova wrote: > > I was trying to figure out the reason for the failure but without any > > success. It appeared that the error is reproducible with the upstream's > > source version, so I have just opened an issue [1] to inform the upstream > > about this bug. > > > > [1] https://github.com/cbcrg/tcoffee/issues/13 > > Thanks a lot, > > Andreas. > I have just pushed a fix of this! The problem was with two processes competing for the same temporary file, as the tempfile names were defined static. With regards, Liubov
Bug#921291: openhft-chronicle-bytes: FTBFS on i386
On Mon, Feb 04, 2019 at 12:37:03AM +0100, Andreas Beckmann wrote: > Package: openhft-chronicle-bytes > Version: 1.16.25-1 > Severity: serious > Justification: fails to build from source > > Hi, > > openhft-chronicle-bytes FTBFS in a i386 pbuilder chroot, while it builds > successfully in an amd64 pbuilder chroot. Why is FTBFS on a binary-all package on !amd64 itself an RC bug? I see the point that it might be considered RC if the package is completely broken. > Andreas cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#921176: redis-server service is failing to start in buster lxc container
On തി, ഫെബ്രു 4, 2019 at 1:26 വൈകു, Pirate Praveen wrote: On 2019, ഫെബ്രുവരി 4 1:20:11 PM IST, Chris Lamb wrote: Hi, redis-server service is failing to start in buster lxc container Any update on this? :) I'm traveling. hopefully tonight or tomorrow night I can try. Adding Raju, and Abhijith, who may be able to try this before. I found some time to test. With the changes you suggested, the error message is gone, but it still fails to start. I tried updating kernel from 4.16 to 4.19 and lxc version from 2.x to 3.x. I also tried to create a fresh buster chroot, but in all cases it failed. Though Abhijith was not able to reproduce it in another machine. Regards, -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#917143: marked as done (t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: COREDUMP)
Your message dated Mon, 04 Feb 2019 10:50:33 + with message-id and subject line Bug#917143: fixed in t-coffee 12.00.7fb08c2-2 has caused the Debian Bug report #917143, regarding t-coffee breaks libbio-tools-run-alignment-tcoffee-perl autopkgtest: COREDUMP to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: t-coffee, libbio-tools-run-alignment-tcoffee-perl Control: found -1 t-coffee/12.00.7fb08c2-1 Control: found -1 libbio-tools-run-alignment-tcoffee-perl/1.7.4-1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of t-coffee the autopkgtest of libbio-tools-run-alignment-tcoffee-perl fails in testing when that autopkgtest is run with the binary packages of t-coffee from unstable. It passes when run with only packages from testing. In tabular form: passfail t-coffeefrom testing12.00.7fb08c2-1 libbio-tools-run-alignment-tcoffee-perl from testing1.7.4-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is contributing to the delay of the migration of t-coffee to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=t-coffee https://ci.debian.net/data/autopkgtest/testing/amd64/libb/libbio-tools-run-alignment-tcoffee-perl/1569594/log.gz autopkgtest [04:38:41]: test autodep8-perl-build-deps: [--- t/TCoffee.t .. ok 1 - An object of class 'Bio::Tools::Run::Alignment::TCoffee' isa 'Bio::Tools::Run::Alignment::TCoffee' ok 2 - set factory parameter ok 3 - get factory parameter ok 4 - Code tested only on t_coffee versions > 1.22 ok 5 ok 6 ok 7 * *FULL TRACE BACK PID: 14398 14420 -- ERROR: COREDUMP: T-COFFEE Version_12.00.7fb08c2 (2018-12-11 09:27:12 - Revision 7fb08c2 - Build 211) * ** * Abnormal Termination * Job NOT Completed:[T-COFFEE, Version_12.00.7fb08c2] * Please CHECK: * -1 The format of your Input Files * -2 The parameters * -3 The use of special characters in sequence names: *(@, |, %...) * -4 The Online Doc (http://www.tcoffee.org) * -5 re-run your CL (see below) with the -debug option. This will produce a debug file you can send us. * * NO * to: * cedric.notred...@gmail.com * If you run T-Coffee over the WEB: * Windows Cut and Paste is sometimes erratic and * it can loose carriage returns. If you suspect this, * try to cut and paste through an intermediate application * (word pad) and inspect the results * CONFIDENTIALITY: * The File NO may contain your personal DATA * Remove ALL confidential DATA from this file BEFORE sending it ** # Command Line: /usr/bin/t_coffee -profile KIQgXqyCHN -seq qjNOX7wp3O -matrix blosum -method lalign_id_pair clustalw_pair -ktuple 3 -outfile /tmp/notSa_tL8M/WVVAoNGLR6 -output clustalw -quiet [PROGRAM:T-COFFEE] # TERMINATION STATUS: FAILURE [PROGRAM: T-COFFEE pid 14398 ppid 14316 #CL: /usr/bin/t_coffee -profile KIQgXqyCHN -seq qjNOX7wp3O -matrix blosum -method lalign_id_pair clustalw_pair -ktuple 3 -outfile /tmp/notSa_tL8M/WVVAoNGLR6 -output clustalw -quiet ERROR: /var/tmp/tco/tco1xsm09w014398/3127314418402 FILE is NOT a supported format [ERROR] not ok 8 # Failed test at t/TCoffee.t line 74. # died: # - EXCEPTION - # MSG: TCoffee call crashed: 256 [command /usr/bin/t_coffee -profile=KIQgXqyCHN -seq=qjNOX7wp3O -m
Bug#919415: marked as done (isight-firmware-tools: Build-Depends on cruft package libgcrypt11-dev)
Your message dated Mon, 04 Feb 2019 10:49:47 + with message-id and subject line Bug#919415: fixed in isight-firmware-tools 1.6-4 has caused the Debian Bug report #919415, regarding isight-firmware-tools: Build-Depends on cruft package libgcrypt11-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: isight-firmware-tools Version: 1.6-3 Severity: serious Justification: fails to build from source (but built successfully in the past) isight-firmware-tools build-depends on libgcrypt11-dev. This was a transitional package, please use libgcrypt20-dev instead. Andreas --- End Message --- --- Begin Message --- Source: isight-firmware-tools Source-Version: 1.6-4 We believe that the bug you reported is fixed in the latest version of isight-firmware-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nobuhiro Iwamatsu (supplier of updated isight-firmware-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Jan 2019 12:12:57 +0900 Source: isight-firmware-tools Binary: isight-firmware-tools isight-firmware-tools-dbgsym Architecture: source amd64 Version: 1.6-4 Distribution: unstable Urgency: medium Maintainer: Debian Mactel Changed-By: Nobuhiro Iwamatsu Description: isight-firmware-tools - tools for dealing with Apple iSight firmware Closes: 767486 919415 Changes: isight-firmware-tools (1.6-4) unstable; urgency=medium . * Add Danish debconf templates translation. (Closes: #767486) Thanks to Frans Spiesschaert. * Fix FTBFS, use libgcrypt20-dev instead. (Closes: #919415) Thanks to Andreas Henriksson. Checksums-Sha1: 625b526f2f198bc94e9c7370a749ad2658d223be 2154 isight-firmware-tools_1.6-4.dsc 560772ff8cb3877533576a8ebe56c42366944de4 15780 isight-firmware-tools_1.6-4.debian.tar.xz eab548895f37079d9e3adafb63bc46181fe8c699 34088 isight-firmware-tools-dbgsym_1.6-4_amd64.deb 41d8685764125ed4f87904c906fe354183b2806e 7518 isight-firmware-tools_1.6-4_amd64.buildinfo 1eb4f7855ab228cc0ae52a9933a5a983cb5989db 30272 isight-firmware-tools_1.6-4_amd64.deb Checksums-Sha256: 8c831d136de2b84de338354949dadd6f49dc3c5b3aed6473a11979e4971bd675 2154 isight-firmware-tools_1.6-4.dsc f37457e00e2dfcddd543b83fe06268fefe80826f26780f92471a6b5a5fda546d 15780 isight-firmware-tools_1.6-4.debian.tar.xz 4a198e0adc62c9701de3ea482d89826a3aeb00a7d9e9b15793bc37419324dbf8 34088 isight-firmware-tools-dbgsym_1.6-4_amd64.deb ae16a99129af0b859302362538783b9e4ec91400bbe8723046c942932ffa34df 7518 isight-firmware-tools_1.6-4_amd64.buildinfo d5d503758f07cf6016daa014e5f65c0e45b20e2c7b33cb1f362ee5e048ee0f94 30272 isight-firmware-tools_1.6-4_amd64.deb Files: 37fe09e6c667a2747b9eccc582a342c4 2154 contrib/graphics optional isight-firmware-tools_1.6-4.dsc ce35e66daa8df6562be8cfd050ec5d58 15780 contrib/graphics optional isight-firmware-tools_1.6-4.debian.tar.xz ad10e05c921cbb43f651776121047366 34088 contrib/debug optional isight-firmware-tools-dbgsym_1.6-4_amd64.deb cb1f15517851638f50af3e1cb5857996 7518 contrib/graphics optional isight-firmware-tools_1.6-4_amd64.buildinfo c1a86323eabb18fa8c7f6ebcb355add6 30272 contrib/graphics optional isight-firmware-tools_1.6-4_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAlxYEsQACgkQMiR/u0Ct H6b6qg/+LuX2wQj4E5Q5QpIvWtg5OE3Rke+zEpm6hyaIM6og2n5zCadfxkppFh9c BwmH+k0UgA21h1BeYi//AJcjok1vF0V7gHscMUrpSLFcjq4k0CL6nChti+JmdRND VZ6ViqrUkLNvntdoWyOtlRHX2zmp+kcSzEH/od7yS78bGsSBTq2PYuk7sWM5/7LE YaNCSs3AxIPHrvwILyzvKkMGfInL+G51l6+S89k78ts9opa21mw7CUlZyT57k6FU 29Lt7VV6vau+F4ruzzOijRnPd7Iy8zfUmuhLi9JiGBnvmBcev2QmG8+ir4chWeaU WHAvpio49Jz0Lv+sxvmFSVMvbPENG1573oIZ8XPE9X7hTQ1VP1rMozktJoGtMvm6 TT9nXg/Vp402d92bKP+Lijr8q8p74NnqjbnCbQ297f0RKX80glZMvQTyTYLdO1Ys oS7vWodzJq6mcg+do0piq3P+SNBeZ2hjrNafBCV0bR+c7ZulHCLrXvH4qmAqcvkD HzmSUOPoK9yJCHHQxpPwIvt9PTZfoFFs+IOyjRRMrdIqxdGVBhjzZdBcyo+GAAWW mCNlid5uF0L7ztoktcXIS+05W3clJJD3HCKjBDsoIAS5IUXUln5wv6Z9jq+Qt7uE Denqr9E8JcISJ
Bug#917719: marked as done (libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Mon, 04 Feb 2019 10:50:33 + with message-id and subject line Bug#917143: fixed in t-coffee 12.00.7fb08c2-2 has caused the Debian Bug report #917143, regarding libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbio-tools-run-alignment-tcoffee-perl Version: 1.7.4-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > t/00-compile.t ... > 1..1 > ok 1 - Bio/Tools/Run/Alignment/TCoffee.pm loaded ok > ok > t/author-eol.t ... skipped: these tests are for testing by the author > t/author-mojibake.t .. skipped: these tests are for testing by the author > t/author-no-tabs.t ... skipped: these tests are for testing by the author > t/author-pod-coverage.t .. skipped: these tests are for testing by the author > t/author-pod-syntax.t skipped: these tests are for testing by the author > > > * > *FULL TRACE BACK PID: 16494 > > 16518 -- ERROR: COREDUMP: T-COFFEE Version_12.00.7fb08c2 (2018-12-11 09:27:12 > - Revision 7fb08c2 - Build 211) > * > > ** > * Abnormal Termination > * Job NOT Completed:[T-COFFEE, Version_12.00.7fb08c2] > * Please CHECK: > * -1 The format of your Input Files > * -2 The parameters > * -3 The use of special characters in sequence names: > *(@, |, %...) > * -4 The Online Doc (http://www.tcoffee.org) > * -5 re-run your CL (see below) with the -debug option. This will > produce a debug file you can send us. > * > * NO > * to: > * cedric.notred...@gmail.com > * If you run T-Coffee over the WEB: > * Windows Cut and Paste is sometimes erratic and > * it can loose carriage returns. If you suspect this, > * try to cut and paste through an intermediate application > * (word pad) and inspect the results > > > * CONFIDENTIALITY: > * The File NO may contain your personal DATA > * Remove ALL confidential DATA from this file BEFORE sending it > ** > # Command Line: /usr/bin/t_coffee -profile C3uHd27Vnl -seq rKVo1aRtb4 -matrix > blosum -method lalign_id_pair clustalw_pair -ktuple 3 -outfile > /tmp/D_LRrJQoYx/TbKy3eG8L7 -output clustalw -quiet [PROGRAM:T-COFFEE] > > # TERMINATION STATUS: FAILURE [PROGRAM: T-COFFEE pid 16494 ppid 16412 > #CL: /usr/bin/t_coffee -profile C3uHd27Vnl -seq rKVo1aRtb4 -matrix blosum > -method lalign_id_pair clustalw_pair -ktuple 3 -outfile > /tmp/D_LRrJQoYx/TbKy3eG8L7 -output clustalw -quiet > ERROR: /var/tmp/tco/tcouusjjsfj16494/9295616514392 FILE is NOT a supported > format [ERROR] > # Failed test at t/TCoffee.t line 74. > # died: > # - EXCEPTION - > # MSG: TCoffee call crashed: 256 [command /usr/bin/t_coffee > -profile=C3uHd27Vnl -seq=rKVo1aRtb4 -matrix=blosum > -method=lalign_id_pair,clustalw_pair -ktuple=3 > -outfile=/tmp/D_LRrJQoYx/TbKy3eG8L7 -output=clustalw -quiet] > # > # STACK Bio::Root::RootI::warn /usr/share/perl5/Bio/Root/RootI.pm:150 > # STACK Bio::Tools::Run::Alignment::TCoffee::_run > /<>/blib/lib/Bio/Tools/Run/Alignment/TCoffee.pm:272 > # STACK Bio::Tools::Run::Alignment::TCoffee::profile_align > /<>/blib/lib/Bio/Tools/Run/Alignment/TCoffee.pm:198 > # STACK Test::Exception::lives_ok t/TCoffee.t:74 > # STACK toplevel t/TCoffee.t:74 > # - > # Failed test 'no T-COFFEE errors' > # at t/TCoffee.t lin
Bug#918566: Lost of code copies of MurmurHash3 (Was: Bug#918566: mash FTBFS on big endian: test failures)
As promised, I pushed my packaging attempt. However, I didn't manage to create a repository under med-team, thus it is under my account [1]. Best Fabian 1: https://salsa.debian.org/kloetzl-guest/libmurmurhash
Bug#820308: marked as done (qiime: many unsatisfiable dependencies)
Your message dated Mon, 04 Feb 2019 11:06:36 + with message-id and subject line Bug#820308: fixed in qiime 2019.1.0-1 has caused the Debian Bug report #820308, regarding qiime: many unsatisfiable dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 820308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qiime Version: 1.9.1+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: qiime/amd64 unsatisfiable Depends: python-burrito-fillings (>= 0.1.1) qiime/amd64 unsatisfiable Depends: qiime-default-reference qiime/amd64 unsatisfiable Depends: emperor (>= 0.9.51) qiime/i386 unsatisfiable Depends: python-burrito-fillings (>= 0.1.1) qiime/i386 unsatisfiable Depends: qiime-default-reference qiime/i386 unsatisfiable Depends: bwa qiime/i386 unsatisfiable Depends: emperor (>= 0.9.51) qiime/i386 unsatisfiable Depends: swarm qiime/i386 unsatisfiable Depends: vsearch (>= 1.1.1) qiime/arm64 unsatisfiable Depends: python-burrito-fillings (>= 0.1.1) qiime/arm64 unsatisfiable Depends: qiime-default-reference qiime/arm64 unsatisfiable Depends: bwa qiime/arm64 unsatisfiable Depends: emperor (>= 0.9.51) qiime/arm64 unsatisfiable Depends: infernal qiime/arm64 unsatisfiable Depends: raxml qiime/arm64 unsatisfiable Depends: sortmerna qiime/arm64 unsatisfiable Depends: swarm qiime/arm64 unsatisfiable Depends: vsearch (>= 1.1.1) ... Cheers, Andreas --- End Message --- --- Begin Message --- Source: qiime Source-Version: 2019.1.0-1 We believe that the bug you reported is fixed in the latest version of qiime, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 820...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated qiime package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Feb 2019 11:37:46 +0100 Source: qiime Binary: qiime Architecture: source Version: 2019.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: qiime - Quantitative Insights Into Microbial Ecology Closes: 820308 Changes: qiime (2019.1.0-1) unstable; urgency=medium . [ Andreas Tille ] * Switch to Qiime2 Closes: #820308 - Adapt watch file - Point Homepage to Qiime2 * debhelper 12 * Architecture: all . [ Liubov Chuprikova ] * Make .egg-info available for build time tests * Adapt d/copyright to Qiime2 * Standards-Version: 4.3.0 Checksums-Sha1: d98b1cb94bf632502a037c05dee15f10b317fcb2 2116 qiime_2019.1.0-1.dsc ea88e2e6728e2cb71089221afe560bc15fe6a74e 372278 qiime_2019.1.0.orig.tar.gz 5165aebf057b3b17ed523520cacfc5869c81f27e 12328 qiime_2019.1.0-1.debian.tar.xz Checksums-Sha256: 8a37a9598d218b13cf7c06848d47f0786873c6875848e52c4437c0245923 2116 qiime_2019.1.0-1.dsc 2c8cb4d6ea4a9dbc5876005b75b0d922ed6c861601002d340c2b991af28097b9 372278 qiime_2019.1.0.orig.tar.gz cb650a12880d9b917e32157f7ce9072ddf66513838de0633a4f3c56eb08b95dc 12328 qiime_2019.1.0-1.debian.tar.xz Files: faaeeacf85e7c5824abacd76611dd3ae 2116 science optional qiime_2019.1.0-1.dsc 703ad2e99df8c415a9304d62c508c7c8 372278 science optional qiime_2019.1.0.orig.tar.gz 22236139939f87eca3bc64a21a2d6282 12328 science optional qiime_2019.1.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxYF0ERHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEx1w/+Pi/1AmdKHyXpznmlRUJ00srk28s/Bxz6 WK0Pee4P2VEy49/X7j182uW1CweKTFRK/49DN2sOtsVwSxiEKKfkJD6yIQr81psu DQDBdap93F2/4LentmN6mNDDXWmv87t1U27DLnIUAOc8g2UXJt4WVVsDgTozgZmu gh953/P2IQYX6MocEErYca/GX3lAoI+5WiHq4uia+51FH2GBhEZChihy0yOWZB2A qkkim5YcVFIjhosxVVPjanUpwx7yTt9innPz4A8Hc3/Ti6LrBExoN7MPUs21HWpI u3Hd6DVLKIxH8ympCUhMkuxtQMbB35OcPhhbvet5MNjiEVMscnTfxwZCuMt2wC+F oOH/DQxHy3De7V4NZhGLkI2R9kGBw3vA9x2Snxe7mHSbIl4EyLtmrBckYkh92j7F m2KEAkqfsapEv+AxQ8zdbEJOUTuQVKlDw3blG+k6siA8v45jtyGx3qstoE3MvUAW TjJApUlWpSB0gmbhDUYLhRDzXHbRZETAfWBwFzemqWEVe01lBkhk1AEjCmeE6XUW mxVbGDiJZYa+BHZlChLh
Bug#896494: Bug #896494 in libqtdbusmock marked as pending
Control: tag -1 pending Hello, Bug #896494 in libqtdbusmock 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: https://salsa.debian.org/debian-ayatana-team/libqtdbusmock/commit/05980cbb68c845c53141fc04966dd62d7f5bdcfc debian/rules: Ignore test failures. Tests succeed during local sbuild based builds, but fail on Debian buildd infrastructure. Ignoring these. (Closes: #896494). (this message was generated automatically) -- Greetings https://bugs.debian.org/896494
Bug#902525: Bug #902525 in xorg-gtest marked as pending
Control: tag -1 pending Hello, Bug #902525 in xorg-gtest 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: https://salsa.debian.org/debian-ayatana-team/xorg-gtest/commit/d43df71418ae89fa1b9700a412e28a9d51662126 debian/rules: Ignore unit test failures. They don't appear in local sbuild runs. Only on Debian infrastructure. (Closes: #902525). (this message was generated automatically) -- Greetings https://bugs.debian.org/902525
Bug#909071: marked as done (pbbam: FTBFS on every release architecture where it previously built)
Your message dated Mon, 04 Feb 2019 11:23:34 +
with message-id
and subject line Bug#909071: fixed in pbbam 0.19.0+dfsg-3
has caused the Debian Bug report #909071,
regarding pbbam: FTBFS on every release architecture where it previously built
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
909071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pbbam
Version: 0.18.0+dfsg-1
Severity: serious
Hi,
The pbbam package FTBFS on every release architecture. The following
snippet is from the arm64 build:
"""
# Fix broken PATH
synthetic_movie_all_path=`find $PWD -name synthetic_movie_all.subreadset.xml` ;
\
sed -i -e
"s?.GENERATEDDATADIR/synthetic_movie_all.subreadset.xml?${synthetic_movie_all_path}?"
tests/src/cram/pbbamify*
BINDIR=`dirname $(find $PWD -name pbmerge -type f -executable)`; \
LIBDIR=`find $PWD -name lib -type d`; \
PATH="$BINDIR:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
LD_LIBRARY_PATH="$LIBDIR:" \
cram -v tests/src/cram/pbmerge_pacbio_ordering.deb.t
tests/src/cram/pbmerge_mixed_ordering.deb.t
tests/src/cram/pbmerge_aligned_ordering.deb.t
tests/src/cram/pbindexdump_json.deb.t tests/src/cram/pbindexdump_cpp.deb.t
tests/src/cram/pbmerge_fofn.deb.t tests/src/cram/pbbamify.deb.t
tests/src/cram/pbmerge_dataset.deb.t
tests/src/cram/pbmerge_pacbio_ordering.deb.t: failed
--- tests/src/cram/pbmerge_pacbio_ordering.deb.t
+++ tests/src/cram/pbmerge_pacbio_ordering.deb.t.err
@@ -14,444 +14,104 @@
Sanity Check:
$ samtools view -H $HQREGION_BAM
- @HD\tVN:1.1\tSO:unknown\tpb:3.0.1 (esc)
-
@RG\tID:ca75d884\tPL:PACBIO\tDS:READTYPE=HQREGION;DeletionQV=dq;DeletionTag=dt;InsertionQV=iq;MergeQV=mq;SubstitutionQV=sq;SubstitutionTag=st;Ipd:Frames=ip;PulseWidth:Frames=pw;PkMid=pm;PkMean=pa;LabelQV=pq;AltLabel=pt;AltLabelQV=pv;PulseMergeQV=pg;PulseCall=pc;PrePulseFrames=pd;PulseCallWidth=px;BINDINGKIT=100372700;SEQUENCINGKIT=100356200;BASECALLERVERSION=0.1;FRAMERATEHZ=100.00\tPU:ArminsFakeMovie
(esc)
- @PG\tID:baz2bam-0.15.0\tPN:baz2bam\tVN:0.15.0 (esc)
- @PG\tID:bazFormat-0.3.0\tPN:bazFormat\tVN:0.3.0 (esc)
- @PG\tID:bazwriter-0.15.0\tPN:bazwriter\tVN:0.15.0 (esc)
+ [E::hts_open_format] Failed to open file
/<>/pbbam-0.18.0/tests/data/polymerase/internal.hqregions.bam
+ samtools view: failed to open
"/<>/pbbam-0.18.0/tests/data/polymerase/internal.hqregions.bam" for
reading: No such file or directory
+ [1]
$ samtools view $HQREGION_BAM | cut -f 1
- ArminsFakeMovie/10/2659_7034
+ [E::hts_open_format] Failed to open file
/<>/pbbam-0.18.0/tests/data/polymerase/internal.hqregions.bam
+ samtools view: failed to open
"/<>/pbbam-0.18.0/tests/data/polymerase/internal.hqregions.bam" for
reading: No such file or directory
[...]
"""
Thanks,
~Niels
--- End Message ---
--- Begin Message ---
Source: pbbam
Source-Version: 0.19.0+dfsg-3
We believe that the bug you reported is fixed in the latest version of
pbbam, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated pbbam package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 04 Feb 2019 11:50:20 +0100
Source: pbbam
Binary: pbbamtools libpbbam0.19.0 libpbbam-dev
Architecture: source
Version: 0.19.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Tille
Description:
libpbbam-dev - Pacific Biosciences binary alignment/map (BAM) library (headers)
libpbbam0.19.0 - Pacific Biosciences binary alignment/map (BAM) library
pbbamtools - processing Pacific Biosciences binary alignment/map files
Closes: 909071
Changes:
pbbam (0.19.0+dfsg-3) unstable; urgency=medium
.
* Team upload.
.
[ Steve Langasek ]
* Fix build dir name for tests
Closes: #909071
Checksums-Sha1:
b940ff1dbb072b37efa5a51268a9ca16ccdcb833 2304 pbbam_0.19.0+dfsg-3.dsc
5fe73e3a2c680540769b762f8750ad1a6bdac088 7124 pbbam_0.19.0+dfsg-3.debian.tar.xz
64248c4f0b9ebbce20a5852ff6996c98166bf99a 14679
pbbam_0.19.0+dfsg-3
Bug#896494: marked as done (FTBFS: test-suite failures)
Your message dated Mon, 04 Feb 2019 11:35:44 +
with message-id
and subject line Bug#896494: fixed in libqtdbusmock 0.7+bzr49+repack1-3
has caused the Debian Bug report #896494,
regarding FTBFS: test-suite failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
896494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libqtdbusmock
Version: 0.7+bzr49+repack1-2
Severity: serious
Hi,
libqtdbusmock fails to pass its test-suite, resulting in a FTBFS:
https://buildd.debian.org/status/package.php?p=libqtdbusmock
/usr/bin/ctest --force-new-ctest-process -j4
Test project /<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu
Start 1: unit-tests
1/1 Test #1: unit-tests ...***Failed 60.84 sec
[==] Running 8 tests from 1 test case.
[--] Global test environment set-up.
[--] 8 tests from TestDBusMock
[ RUN ] TestDBusMock.StartsDBusMockSession
Traceback (most recent call last):
File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/lib/python3/dist-packages/dbusmock/__main__.py", line 81, in
bus = dbusmock.testcase.DBusTestCase.get_dbus(args.system)
File "/usr/lib/python3/dist-packages/dbusmock/testcase.py", line 151, in
get_dbus
return dbus.bus.BusConnection(os.environ['DBUS_SESSION_BUS_ADDRESS'])
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 122, in __new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.BadAddress: Could not
parse server address: Unknown address type (examples of valid types are "tcp"
and on UNIX "unix")
unknown file: Failure
C++ exception with description "Process [python3] for service [test.name]
failed to appear on bus" thrown in the test body.
[ FAILED ] TestDBusMock.StartsDBusMockSession (14810 ms)
[ RUN ] TestDBusMock.StartsDBusMockSystem
[ OK ] TestDBusMock.StartsDBusMockSystem (222 ms)
[ RUN ] TestDBusMock.StartsDBusMockWithNM
1524175942.996 emit org.freedesktop.DBus.ObjectManager.InterfacesAdded
"/org/freedesktop/NetworkManager" {"org.freedesktop.NetworkManager":
{"ActiveConnections": [], "Devices": [], "NetworkingEnabled": True,
"Connectivity": 4, "State": 70, "Startup": False, "Version": "0.9.6.0",
"WimaxEnabled": True, "WimaxHardwareEnabled": True, "WirelessEnabled": True,
"WirelessHardwareEnabled": True, "WwanEnabled": False, "WwanHardwareEnabled":
True}}
1524175942.997 emit org.freedesktop.DBus.ObjectManager.InterfacesAdded
"/org/freedesktop/NetworkManager/Settings"
{"org.freedesktop.NetworkManager.Settings": {"Hostname": "hostname",
"CanModify": True, "Connections": []}}
1524175943.011 emit org.freedesktop.DBus.ObjectManager.InterfacesAdded
"/org/freedesktop/NetworkManager/Devices/device"
{"org.freedesktop.NetworkManager.Device.Wireless": {"HwAddress":
"11:22:33:44:55:66", "PermHwAddress": "11:22:33:44:55:66", "Bitrate": 5400,
"Mode": 2, "WirelessCapabilities": 255, "AccessPoints": []},
"org.freedesktop.NetworkManager.Device": {"ActiveConnection": "/",
"AvailableConnections": [], "AutoConnect": False, "Managed": True, "Driver":
"dbusmock", "DeviceType": 2, "State": 20, "Interface": "eth1", "IpInterface":
"eth1"}}
1524175943.011 Get org.freedesktop.NetworkManager.Devices
1524175943.011 GetAll org.freedesktop.NetworkManager
1524175943.011 Set org.freedesktop.NetworkManager.Devices
["/org/freedesktop/NetworkManager/Devices/device"]
1524175943.011 emit org.freedesktop.DBus.Properties.PropertiesChanged
"org.freedesktop.NetworkManager" {"Devices":
["/org/freedesktop/NetworkManager/Devices/device"]} []
1524175943.012 emit org.freedesktop.NetworkManager.DeviceAdded
"/org/freedesktop/NetworkManager/Devices/device"
1524175943.019 GetDevices
[ OK ] TestDBusMock.StartsDBusMockWithNM (209 ms)
[ RUN ] TestDBusMock.StartsDBusMockTemplateParameters
1524175943.218 Get org.freedesktop.UPower.DaemonVersion
1524175943.218 GetAll org.freedesktop.UPower
1524175943.219 Get org.freedesktop.UPower.OnBattery
1524175943.219 GetAll org.freedesktop.UPower
[ OK ] TestDBusMock.StartsDBusMockTemplateParameters (197 ms)
[ RUN ] TestDBusMock.StartsDBusMockWithTemplate
1524175943.402 emit org.freedesktop.DBus.ObjectManager.InterfacesAdded
"/org/freedesktop/NetworkManager" {"org.freedesktop.NetworkManager":
{"ActiveConnections": [], "Devices": [], "NetworkingEnabled": True,
Bug#918566: Lost of code copies of MurmurHash3 (Was: Bug#918566: mash FTBFS on big endian: test failures)
Hi Fabian, thanks a lot. I've moved it to med-team and fixed Vcs fields. If you issue an ITP I can sponsor the package immediately. Thanks for your work on this Andreas. On Mon, Feb 04, 2019 at 12:02:37PM +0100, Fabian Klötzl wrote: > As promised, I pushed my packaging attempt. However, I didn't manage to > create a repository under med-team, thus it is under my account [1]. > > Best > Fabian > > 1: https://salsa.debian.org/kloetzl-guest/libmurmurhash > > > -- http://fam-tille.de
Bug#921291: openhft-chronicle-bytes: FTBFS on i386
On 2019-02-04 11:13, Adrian Bunk wrote: >> openhft-chronicle-bytes FTBFS in a i386 pbuilder chroot, while it builds >> successfully in an amd64 pbuilder chroot. > > Why is FTBFS on a binary-all package on !amd64 itself an RC bug? I haven looked in detail in the FTBFS. It just smells fishy ... Feel free to downgrade ... Andreas
Bug#918566: Lost of code copies of MurmurHash3 (Was: Bug#918566: mash FTBFS on big endian: test failures)
Another comment: For libsmithwaterman I added a patch for automake including pkg-config input. I'd consider it more flexible than a fixed Makefile. On Mon, Feb 04, 2019 at 12:02:37PM +0100, Fabian Klötzl wrote: > As promised, I pushed my packaging attempt. However, I didn't manage to > create a repository under med-team, thus it is under my account [1]. > > Best > Fabian > > 1: https://salsa.debian.org/kloetzl-guest/libmurmurhash > > > -- http://fam-tille.de
Bug#902525: marked as done (xorg-gtest only succeeds its tests in a minimal)
Your message dated Mon, 04 Feb 2019 11:53:45 + with message-id and subject line Bug#902525: fixed in xorg-gtest 0.7.1-5 has caused the Debian Bug report #902525, regarding xorg-gtest only succeeds its tests in a minimal to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 902525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xorg-gtest Version: 0.7.1-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh build-indep --with autoreconf dh_update_autotools_config -i dh_autoreconf -i examples/Makefile.am:35: warning: source file '$(top_srcdir)/gtest/src/gtest-all.cc' is in a subdirectory, examples/Makefile.am:35: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. [... snipped ...] [ OK ] ProcessValgrindArgsWrapper.ValgrindWrapperWithArgs/1 (36 ms) [ RUN ] ProcessValgrindArgsWrapper.ValgrindWrapperWithArgs/2 [ OK ] ProcessValgrindArgsWrapper.ValgrindWrapperWithArgs/2 (36 ms) [--] 3 tests from ProcessValgrindArgsWrapper (108 ms total) [--] Global test environment tear-down [==] 16 tests from 3 test cases ran. (306 ms total) [ PASSED ] 15 tests. [ FAILED ] 1 test, listed below: [ FAILED ] Process.ChildTearDown 1 FAILED TEST FAIL process-test (exit status: 1) Testsuite summary for X.org Testing Environment for Google Test 0.7.1 # TOTAL: 3 # PASS: 2 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See test/test-suite.log Makefile:900: recipe for target 'test-suite.log' failed make[5]: *** [test-suite.log] Error 1 make[5]: Leaving directory '/<>/test' Makefile:1006: recipe for target 'check-TESTS' failed make[4]: *** [check-TESTS] Error 2 make[4]: Leaving directory '/<>/test' Makefile:1093: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 make[3]: Leaving directory '/<>/test' Makefile:465: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory '/<>' dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 debian/rules:24: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' debian/rules:7: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The above is how the build ends in my autobuilder and it's not necessarily the relevant part. The failure is not, however, related to using dpkg-buildpackage -A, as it also fails in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xorg-gtest.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the page for this package. Thanks. --- End Message --- --- Begin Message --- Source: xorg-gtest Source-Version: 0.7.1-5 We believe that the bug you reported is fixed in the latest version of xorg-gtest, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 902...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated xorg-gtest package) (This message was generated automatically at their request; if you believe that there is a
Bug#921338: r-cran-taxize: autopkgtest regression
Source: r-cran-taxize
Version: 0.9.5+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 0.9.5+dfsg-1 to unstable, r-cran-taxize has been
failing its own autopkgtests [1] with the following error:
> library("taxize")
> test_check("taxize")
Error in library("vcr") : there is no package called 'vcr'
Calls: test_check ... source_dir -> lapply -> FUN -> eval -> eval -> library
Execution halted
This appears to be a missing test dependency on r-cran-vcr, however a
similar error occurred in r-cran-natserv (#921211) and perhaps the
solution is for r-cran-natserv to depend on r-cran-vcr.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-taxize/unstable/amd64/
Bug#921216: marked as done (circlator should become Architecture: amd64 to allow testing migration)
Your message dated Mon, 04 Feb 2019 12:04:17 + with message-id and subject line Bug#921216: fixed in circlator 1.5.5-3 has caused the Debian Bug report #921216, regarding circlator should become Architecture: amd64 to allow testing migration to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: circlator Version: 1.5.5-2 Severity: serious There is no point in a package being binary-all when it has multiple amd64-only dependencies, and this is also currently blocking testing migration. --- End Message --- --- Begin Message --- Source: circlator Source-Version: 1.5.5-3 We believe that the bug you reported is fixed in the latest version of circlator, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated circlator package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Feb 2019 09:32:42 +0100 Source: circlator Binary: circlator Architecture: source Version: 1.5.5-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: circlator - circularize genome assemblies Closes: 921216 Changes: circlator (1.5.5-3) unstable; urgency=medium . * Team upload. * Architecture amd64 only Closes: #921216 * debhelper 12 * Standards-Version: 4.3.0 Checksums-Sha1: 693a94d197c065d88d1f386c9bbe3e1995335d6e 2206 circlator_1.5.5-3.dsc 24d16fbed21c266cd48f4cec335ac6fd939ef90d 3396 circlator_1.5.5-3.debian.tar.xz Checksums-Sha256: a7ecb23bd5736d9545fefeef9068c7d92de1a184acfd6d077358683c46861954 2206 circlator_1.5.5-3.dsc cea9c644ccd4f8e8e3f10062f0bcdf09d8a7d47fc4e87c1a517b5e191017fece 3396 circlator_1.5.5-3.debian.tar.xz Files: aabda33d18546088768a2653b7b8c6df 2206 science optional circlator_1.5.5-3.dsc 70eaff442f7ea23fddccb03498b70cc1 3396 science optional circlator_1.5.5-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxX/NURHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHdog//c0c/j4H4PqoB0QrgaJjHJkdEO9wExSre s0TpOPzxMO5bL00OL+voIJZ7zQSv8txc2gvoTGVyK/V16nD4jMovp2J83JDYRfIx ksl12YhvLDcStfXjhZzBwneiKmG7kwFByuZHe51pxB6lh24HdKpG9O0jNrBOE9VY mh2+jYvjyKOLonlTkrqg+iKKV6+S/NyN2nj9Ip/7kt9gM9qgV0YQJwQDw6ekdHZN TwrjSWSu2C4G4e1hiVF7fa5Bz1GGWeYz2Ny6B6X1sLNkfUQENY71wvvdoyaWSgxL DzARIXdB5umUBN3nvZZuecpwutFWrFJSyvZJcJ5ie3alAcZmbOPUri5MY3Vz6Wx3 zxSLA7+XjmeXShfdXUK+cxhiVB0ttRa/3/cXADWVZGYgknyBDOU6NqmUbOLzW1R1 E1s6zoTazTQJ0phmMUw+h3AQte6hL6XKUH+9bkI2j+Eu8LiySw8g4f0Cy9sxTds1 NgdVg/CUdnlA53VpmU8JBGQDxFGvmsTJ8HAMevtnXbAZYnSHne1vy6Y7aazBTGkS 4j8LtqZmai+ZwHTXku+r/BP6gdOfnr8DokGo+ztySizt9DgNw43MnFVdQWNEayZ3 /UZL4g0pHv7fmUABCQpAvJtWiM0vmPRpdEmKBEhLUxrC3FWen0ujUMFaIWqLPXI1 jY6rxYiTnWM= =JIyU -END PGP SIGNATURE End Message ---
Processed: Re: Bug#920250: python-pysam ftbfs from source (test failures)
Processing control commands: > forwarded -1 https://github.com/pysam-developers/pysam/issues/761 Bug #920250 [src:python-pysam] python-pysam ftbfs from source (test failures) Set Bug forwarded-to-address to 'https://github.com/pysam-developers/pysam/issues/761'. > tags -1 upstream help Bug #920250 [src:python-pysam] python-pysam ftbfs from source (test failures) Added tag(s) help and upstream. -- 920250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 921266 is serious
Processing commands for cont...@bugs.debian.org: > severity 921266 serious Bug #921266 [linphone] linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 921266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920250: python-pysam ftbfs from source (test failures)
Control: forwarded -1 https://github.com/pysam-developers/pysam/issues/761 COntrol: tags -1 upstream help
Bug#920250: python-pysam ftbfs from source (test failures)
Hi Michael,
are you aware that it seems that your latest change
htslib (1.9-10) unstable; urgency=medium
* Bring the libdeflate, GCS, and S3 updates back to unstable.
-- Michael R. Crusoe Wed, 16 Jan 2019 05:23:22
-0800
seems to have broken python-pysam? I have reported this to upstream[1]
but I have no idea whether your change might be responsible for the
break or not.
Kind regards
Andreas.
[1] https://github.com/pysam-developers/pysam/issues/761
On Wed, Jan 23, 2019 at 10:44:51AM +0100, Matthias Klose wrote:
> Package: src:python-pysam
> Version: 0.15.2+ds-1
> Severity: serious
> Tags: sid buster
>
> === FAILURES
> ===
> _ TestIndexing.test_indexing_to_custom_location_works
> __
>
> self = testMethod=test_indexing_to_custom_location_works>
>
> def test_indexing_to_custom_location_works(self):
> '''test indexing a file with a non-default location.'''
>
> index_path = get_temp_filename(suffix='custom.tbi')
> pysam.tabix_index(self.tmpfilename, preset="gff",
> index=index_path, force=True)
> > self.assertTrue(checkBinaryEqual(index_path, self.filename_idx))
> E AssertionError: False is not true
>
> tests/tabix_test.py:89: AssertionError
> TestIndexing.test_indexing_with_explict_columns_works
> _
>
> self = testMethod=test_indexing_with_explict_columns_works>
>
> def test_indexing_with_explict_columns_works(self):
> '''test indexing via preset.'''
>
> pysam.tabix_index(self.tmpfilename,
> seq_col=0,
> start_col=3,
> end_col=4,
> line_skip=0,
> zerobased=False)
> self.assertTrue(checkBinaryEqual(
> > self.tmpfilename + ".tbi", self.filename_idx))
> E AssertionError: False is not true
>
> tests/tabix_test.py:102: AssertionError
> _ TestIndexing.test_indexing_with_preset_works
> _
>
> self =
>
> def test_indexing_with_preset_works(self):
> '''test indexing via preset.'''
>
> pysam.tabix_index(self.tmpfilename, preset="gff")
> self.assertTrue(checkBinaryEqual(
> > self.tmpfilename + ".tbi", self.filename_idx))
> E AssertionError: False is not true
>
> tests/tabix_test.py:81: AssertionError
> === warnings summary
> ===
> /usr/lib/python2.7/dist-packages/Cython/Compiler/Main.py:367
> /usr/lib/python2.7/dist-packages/Cython/Compiler/Main.py:367: FutureWarning:
> Cython directive 'language_level' not set, using 2 for now (Py2). This will
> change in a later release! File:
> /<>/python-pysam-0.15.2+ds/.pybuild/cpython2_2.7_pysam/build/tests/_compile_test.pyx
> tree = Parsing.p_module(s, pxd, full_module_name)
>
> .pybuild/cpython2_2.7_pysam/build/tests/AlignmentFile_test.py::TestTruncatedBAM::testTruncatedBamIterator
>
> /<>/python-pysam-0.15.2+ds/.pybuild/cpython2_2.7_pysam/build/tests/AlignmentFile_test.py:1459:
> UserWarning: no BGZF EOF marker; file may be truncated
> ignore_truncation=True)
>
> -- Docs: https://docs.pytest.org/en/latest/warnings.html
> 3 failed, 906 passed, 17 skipped, 2 warnings in 60.36 seconds
> =
> E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
> /<>/python-pysam-0.15.2+ds/.pybuild/cpython2_2.7_pysam/build;
> python2.7 -m pytest tests
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
> exit code 13
> make[1]: *** [debian/rules:32: override_dh_auto_test] Error 25
> make[1]: Leaving directory '/<>/python-pysam-0.15.2+ds'
> make: *** [debian/rules:24: build-arch] Error 2
> dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
> status 2
>
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
--
http://fam-tille.de
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > severity 921015 normal Bug #921015 [kamailio] kamailio 5.2 invalid permissions at run dir cuases several issues Severity set to 'normal' from 'grave' > --- Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 921015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Restoring old title, not really related to chroot being minimal or not
Processing commands for cont...@bugs.debian.org:
> retitle 902525 FTBFS in buster/sid (failing tests)
Bug #902525 {Done: Mike Gabriel } [src:xorg-gtest]
xorg-gtest only succeeds its tests in a minimal
Changed Bug title to 'FTBFS in buster/sid (failing tests)' from 'xorg-gtest
only succeeds its tests in a minimal'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
902525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 921247 is serious
Processing commands for cont...@bugs.debian.org: > severity 921247 serious Bug #921247 [libboost1.67-dev] Boost.Compute users FTBFS with GCC 8 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 921247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902525: Restoring old title, not really related to chroot being minimal or not
retitle 902525 FTBFS in buster/sid (failing tests) thanks Note: I can offer ssh access to a machine where this happens all the time using sbuild if you like (please contact me privately for details). Thanks.
Processed: severity of 921224 is serious
Processing commands for cont...@bugs.debian.org: > severity 921224 serious Bug #921224 [anki] anki: Syncing to AnkiWeb fails with Unknown response code: 400 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 921224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 921224 is important
Processing commands for cont...@bugs.debian.org: > severity 921224 important Bug #921224 [anki] anki: Syncing to AnkiWeb fails with Unknown response code: 400 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 921224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#849390: marked as done (google-android-ndk-installer: Superseded by google-android-installers?)
Your message dated Mon, 04 Feb 2019 12:34:11 + with message-id and subject line Bug#849390: fixed in google-android-installers 1472023576+nmu2 has caused the Debian Bug report #849390, regarding google-android-ndk-installer: Superseded by google-android-installers? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 849390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: google-android-ndk-installer Version: 13b Severity: serious google-android-ndk-installer was removed from unstable and testing in Sepember because it's been replaced by google-android-installers. See https://bugs.debian.org/838653 google-android-ndk-installer was recently re-introduced but the binary package (13b) has a lower number than the google-android-ndk-installer provided by google-android-installers (1472023576). I recommend either: 1) remove the google-android-ndk-installer source package again, or 2) remove google-android-ndk-installer from google-android-installers and use an epoch in the google-android-ndk-installer binary package. Note that it's possible to have an epoch for the binary but not for the source. There's an example at https://sources.debian.net/src/iproute2/4.9.0-1/debian/rules/?hl=35#L35 Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Source: google-android-installers Source-Version: 1472023576+nmu2 We believe that the bug you reported is fixed in the latest version of google-android-installers, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 849...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Helge Kreutzmann (supplier of updated google-android-installers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 Feb 2019 12:25:36 +0100 Source: google-android-installers Architecture: source Version: 1472023576+nmu2 Distribution: unstable Urgency: medium Maintainer: Android tools Maintainer Changed-By: Helge Kreutzmann Closes: 849390 914169 915657 Changes: google-android-installers (1472023576+nmu2) unstable; urgency=medium . * Non-maintainer upload * Explicitly increment version numbers. Closes: #915657. * No longer build google-android-ndk-installer. Closes: #849390. * Add Russian debconf translation, thanks to Lev Lamberov, Closes: #914169. Checksums-Sha1: fcaf650a3b8d0b7ff1a5ac24372566215bd6344e 5165 google-android-installers_1472023576+nmu2.dsc e113b63fd4a5edced79da9128013daae5f8129a2 16980 google-android-installers_1472023576+nmu2.tar.xz dc0c769753a36b839137f3e46f7cbbe80b81b78f 16535 google-android-installers_1472023576+nmu2_amd64.buildinfo Checksums-Sha256: 9b0d2d07f14ea76e912fb301999b3cb3d3dcb91ae03faaf80f914085092b9c08 5165 google-android-installers_1472023576+nmu2.dsc 41f325b69c08e6ac460adc20b7e0dbae43922a7f88a16d22c7851d46c394f57d 16980 google-android-installers_1472023576+nmu2.tar.xz 5f3d13f266fc6400fbb48260af401d5709f50c3e5e8d218699743c9355c0435f 16535 google-android-installers_1472023576+nmu2_amd64.buildinfo Files: bc9de377db1039fac6197c7a5c0bacb1 5165 contrib/devel optional google-android-installers_1472023576+nmu2.dsc 340d589b756d39dbce740a909eb42be4 16980 contrib/devel optional google-android-installers_1472023576+nmu2.tar.xz 5d9d314cec13ba5d72c7dbc3868ee56f 16535 contrib/devel optional google-android-installers_1472023576+nmu2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlxYLfEACgkQEwLx8Dbr 6xlYgQ/+OD5f5JNMLYlNZBPV6uYtqytTH/3aTXz7kSzDPBUWFl3boWi5HMLCyL1x EBKsERlYz2IB3wE19CFFFsc9MddLOnAlHqwXTw9VTaNU9bxViVvRsKXqteHGc2SQ H8oAMBYAMoN79wawcc8GEPFp75qQ51K5uBDZxwEufGUQyktO0WPQsIKkinscypdZ euSEUanKjWBeO4reQTGCbb/EkqOvSHzZyl2X3hQ6B4ffvO7O7nwptZggCwtf2hKZ FBGnIKmVImyvlusQK05THhCGjZya7aeCyQoK7nrc0zmFpaxuYJLJeWloykhbhVCe OKZ/nrnuaqYaJBsVKW1hynvNAiScNShHlHHvKcMTjzx/UgCqmiLhXV2obbDXZTsH l38YSQfX72HhOAQAGBgXG4yquHN/ItfcVDnzVOv8AMXH8lHPyC8MPL0HhXG8A4RR SLQnYrwYXnaRodULBPTwsTEbUPxar/pepXZbSOs50Gsgz/kLruAZEuSHpoO1ghSt GxgNHlB6+lkETmCtLSOrVFEp4Lbh7U3T2yNDAXFsfxZxaWyOmh/5j6clkJPRhUK7 mbNjulfcpnhhAN94FSDRW08271AcqpIHfmo0WvIpCXZtdnPc
Bug#915657: marked as done (google-android-installers NMU binaries cannot be installed due to unchanged version of the binary packages)
Your message dated Mon, 04 Feb 2019 12:34:11 + with message-id and subject line Bug#915657: fixed in google-android-installers 1472023576+nmu2 has caused the Debian Bug report #915657, regarding google-android-installers NMU binaries cannot be installed due to unchanged version of the binary packages to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: google-android-installers Version: 1472023576+nmu1 Severity: serious Your upload included the binary package google-android-platform-21-installer, version 21+r02, for all, however stable already has version 21+r02. --- End Message --- --- Begin Message --- Source: google-android-installers Source-Version: 1472023576+nmu2 We believe that the bug you reported is fixed in the latest version of google-android-installers, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Helge Kreutzmann (supplier of updated google-android-installers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 Feb 2019 12:25:36 +0100 Source: google-android-installers Architecture: source Version: 1472023576+nmu2 Distribution: unstable Urgency: medium Maintainer: Android tools Maintainer Changed-By: Helge Kreutzmann Closes: 849390 914169 915657 Changes: google-android-installers (1472023576+nmu2) unstable; urgency=medium . * Non-maintainer upload * Explicitly increment version numbers. Closes: #915657. * No longer build google-android-ndk-installer. Closes: #849390. * Add Russian debconf translation, thanks to Lev Lamberov, Closes: #914169. Checksums-Sha1: fcaf650a3b8d0b7ff1a5ac24372566215bd6344e 5165 google-android-installers_1472023576+nmu2.dsc e113b63fd4a5edced79da9128013daae5f8129a2 16980 google-android-installers_1472023576+nmu2.tar.xz dc0c769753a36b839137f3e46f7cbbe80b81b78f 16535 google-android-installers_1472023576+nmu2_amd64.buildinfo Checksums-Sha256: 9b0d2d07f14ea76e912fb301999b3cb3d3dcb91ae03faaf80f914085092b9c08 5165 google-android-installers_1472023576+nmu2.dsc 41f325b69c08e6ac460adc20b7e0dbae43922a7f88a16d22c7851d46c394f57d 16980 google-android-installers_1472023576+nmu2.tar.xz 5f3d13f266fc6400fbb48260af401d5709f50c3e5e8d218699743c9355c0435f 16535 google-android-installers_1472023576+nmu2_amd64.buildinfo Files: bc9de377db1039fac6197c7a5c0bacb1 5165 contrib/devel optional google-android-installers_1472023576+nmu2.dsc 340d589b756d39dbce740a909eb42be4 16980 contrib/devel optional google-android-installers_1472023576+nmu2.tar.xz 5d9d314cec13ba5d72c7dbc3868ee56f 16535 contrib/devel optional google-android-installers_1472023576+nmu2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlxYLfEACgkQEwLx8Dbr 6xlYgQ/+OD5f5JNMLYlNZBPV6uYtqytTH/3aTXz7kSzDPBUWFl3boWi5HMLCyL1x EBKsERlYz2IB3wE19CFFFsc9MddLOnAlHqwXTw9VTaNU9bxViVvRsKXqteHGc2SQ H8oAMBYAMoN79wawcc8GEPFp75qQ51K5uBDZxwEufGUQyktO0WPQsIKkinscypdZ euSEUanKjWBeO4reQTGCbb/EkqOvSHzZyl2X3hQ6B4ffvO7O7nwptZggCwtf2hKZ FBGnIKmVImyvlusQK05THhCGjZya7aeCyQoK7nrc0zmFpaxuYJLJeWloykhbhVCe OKZ/nrnuaqYaJBsVKW1hynvNAiScNShHlHHvKcMTjzx/UgCqmiLhXV2obbDXZTsH l38YSQfX72HhOAQAGBgXG4yquHN/ItfcVDnzVOv8AMXH8lHPyC8MPL0HhXG8A4RR SLQnYrwYXnaRodULBPTwsTEbUPxar/pepXZbSOs50Gsgz/kLruAZEuSHpoO1ghSt GxgNHlB6+lkETmCtLSOrVFEp4Lbh7U3T2yNDAXFsfxZxaWyOmh/5j6clkJPRhUK7 mbNjulfcpnhhAN94FSDRW08271AcqpIHfmo0WvIpCXZtdnPcghyejbFA+c10uzXo xP8zwdoCb5rJtX87scTx1tiQdW0j7FWwlCzCoD9kNJ4ftc/yZT8= =oE2e -END PGP SIGNATURE End Message ---
Bug#914537: openmw: segfault at start
On Sun, 25 Nov 2018 20:15:08 +0100 bret curtis wrote: > Thanks Fred! > > We're tracking it upstream. Will keep this bug posted with results. > > https://gitlab.com/OpenMW/openmw/issues/4737 Hello Bret, we are running out of time for Debian 10 "Buster" because the soft freeze starts next week. Do you think you can prepare an update in the next few days to get this fixed? I could sponsor the upload. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#915739: marked as done (openjdk-8-jre-dcevm still uses GCC 7 to build)
Your message dated Mon, 04 Feb 2019 13:23:21 + with message-id and subject line Bug#921217: Removed package(s) from unstable has caused the Debian Bug report #915739, regarding openjdk-8-jre-dcevm still uses GCC 7 to build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:openjdk-8-jre-dcevm Version: 8u181-1 Severity: serious Tags: sid buster Please use the default GCC for the package so that we can remove GCC 7 for the buster release. --- End Message --- --- Begin Message --- Version: 8u181-1+rm Dear submitter, as the package openjdk-8-jre-dcevm has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/921217 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#915540: marked as done (openjdk-8-jre-dcevm should likely not be in buster)
Your message dated Mon, 04 Feb 2019 13:23:21 + with message-id and subject line Bug#921217: Removed package(s) from unstable has caused the Debian Bug report #915540, regarding openjdk-8-jre-dcevm should likely not be in buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openjdk-8-jre-dcevm Version: 8u181-1 Severity: serious With OpenJDK 8 not supported in Debian this version is likely not suitable for buster. The OpenJDK 11 version seems to be at https://github.com/HotswapProjects/openjdk-jdk11u --- End Message --- --- Begin Message --- Version: 8u181-1+rm Dear submitter, as the package openjdk-8-jre-dcevm has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/921217 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#921338: marked as done (r-cran-taxize: autopkgtest regression)
Your message dated Mon, 04 Feb 2019 13:20:22 +
with message-id
and subject line Bug#921338: fixed in r-cran-taxize 0.9.5+dfsg-2
has caused the Debian Bug report #921338,
regarding r-cran-taxize: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
921338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-taxize
Version: 0.9.5+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 0.9.5+dfsg-1 to unstable, r-cran-taxize has been
failing its own autopkgtests [1] with the following error:
> library("taxize")
> test_check("taxize")
Error in library("vcr") : there is no package called 'vcr'
Calls: test_check ... source_dir -> lapply -> FUN -> eval -> eval -> library
Execution halted
This appears to be a missing test dependency on r-cran-vcr, however a
similar error occurred in r-cran-natserv (#921211) and perhaps the
solution is for r-cran-natserv to depend on r-cran-vcr.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-taxize/unstable/amd64/
--- End Message ---
--- Begin Message ---
Source: r-cran-taxize
Source-Version: 0.9.5+dfsg-2
We believe that the bug you reported is fixed in the latest version of
r-cran-taxize, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-taxize package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 04 Feb 2019 13:50:49 +0100
Source: r-cran-taxize
Binary: r-cran-taxize
Architecture: source
Version: 0.9.5+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Description:
r-cran-taxize - GNU R taxonomic information from around the web
Closes: 921338
Changes:
r-cran-taxize (0.9.5+dfsg-2) unstable; urgency=medium
.
* Test-Depends: r-cran-vcr
* Set LC_ALL=C.UTF-8 in autopkgtest
Closes: #921338
Checksums-Sha1:
b064d5f67efb71d34ed678c58a6c37e9f0ce6bd6 2436 r-cran-taxize_0.9.5+dfsg-2.dsc
aa54616f3b24e39824247bea8bd60d7cbcda18c0 3580
r-cran-taxize_0.9.5+dfsg-2.debian.tar.xz
Checksums-Sha256:
87c750a8c9492fa0bce8173ee3da4f797feff0df07d5fb39f131803685120013 2436
r-cran-taxize_0.9.5+dfsg-2.dsc
82c2918cfcac9ca34e1a7a6a3f801f018f08f79539ecb5a6549c337b1b0724e2 3580
r-cran-taxize_0.9.5+dfsg-2.debian.tar.xz
Files:
151a8858c375ecca45677605f83e7077 2436 gnu-r optional
r-cran-taxize_0.9.5+dfsg-2.dsc
e1b1d83c92dfbebbfb68cf7fde00c40f 3580 gnu-r optional
r-cran-taxize_0.9.5+dfsg-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxYNi8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEfMg//XH6QxL68+VNLgNkbOB8BccMVOp6qYyrt
WdBIgZXz1wGh3HZUzvr+8pWDTVYy9aGA6QdZIpVjkXsLouIJvhCYDFW2jHmzMZOG
EgiulD7ZdmEYCBAh0A5V9iQCOiAI5rI9ADlgUro8R+aUaazdNcGrRGhunOyMFzVk
5ERxi8rtW3EtJe7Kf1HJItTc9mRV9wxf0EjJY/7FfXZNuGjmVoXPbQSv4uLjvEru
f1Vai68IjgVf7S599lj0FhKllYcEf3zwdXZaGfNgKvSRpYc1RBeqRnhk8bysNrHD
823sdVKpDI69UO8KkHFn88CLi2N/mXG0LtHb1E+irrfmHR0PRPQ8uTpEoZgnep1v
gy2izh7WPlpONq2wBBQ7xGqui93fq5qI7jf+0KFw+Nz03IA88z6NtTZVJxFpYssn
fyvLUGYH0/k7/0Pl0Y5l1zw/YuKrkJYhafursxClDdkfHkoTd4CYcKNmpduA/2Aj
QgZspUi3FjDzqVa8N+bzQGYcLtJaPojdnd8aknlKV1VpsK47q3ZFa2vxZHs9t/x6
SUP3qJ/tl6YkAdMa0/kbp7fgu/g3uwzjqWNUYIAMvYlD2ym/Ij5PI/tdtPvbYG1Z
MwqYQ/YEZ7iYXlDFckKcQbP67zd+Gs+K6b5VLr6y//6BpStbBd1W500eOlNrdM3A
r8MOP9I6tvo=
=HNCG
-END PGP SIGNATURE End Message ---
Bug#914537: openmw: segfault at start
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Markus, as it turns out, we're about to have another release 0.45 that has been in 'the-works' for the past month. It's been ready for awhile, we've just been waiting on PR to make a release video and finish up a write-up. I'll ask the team if they feel comfortable with a release on Debian (and eventually Ubuntu) before it's made official. What is my drop-dead date for getting this in? Cheers, Bret -BEGIN PGP SIGNATURE- Version: FlowCrypt 6.6.1 Gmail Encryption Comment: Seamlessly send and receive encrypted email wsFcBAEBCAAGBQJcWD6TAAoJEMI3e31YTLkwpUYP/2sXgb1p46eRXz0lJVh0 uYfEYnnxUtpsO0WAs1nR5YIytIrC5LtqseQllRbT4VuIFkEyYPuSAVOrDnS/ Pi8KEdxsAGcjuQr/yoidwbWu/cBsIz62JGx9xIjnUi+dyasuPjdPKUOL+WeF X9j1PnRm06B0Yt8331rA5KiYpNybg1sqwReD7a/BH+4E8+iSkL3lECrb9FHs bllA4jjqFy+EYEHkCOpbfgoBhGCwkzoayqxGrFb48by7eFF7KnxJR7Kw0su8 K2SNSOJWt0UN2NqQTKPrpr7eCwkDvG6EJwmazarHyqwDlCpS19IOQWPORNnE qclwwfBQUtDZpsTJS+EI+hhOt0xp06PK5fdSj274pYFrsHsiHlj4n1nGv0Gt fTNX3SpwAl3sKn9dmlAWDBd3RuF9y4+u9UwATwJzD3CuH/4S6AxDqfD5CLqb 228t8d5Si2RzC095W5PZFsGziKUe3EL79Rmwoj3RSWu7cWT8WKvBCR4xJyeD DyX/iaL70h85F59dGigqaYcH+yGa1BNtUkeocvihpr2qeDsDgHzZi1olqNyw Gs97YagH6sOgW8yZErwT0e7C7EKckJ/xfrHTMj0hAuQdXSudFgpmgvlfelUW UNO/ewKkmv/4D1njejL3Fsp9JVzDVmq5yqMPV2SURt+DjI6nK44k/Q2x1qFm oxb3 =eEHN -END PGP SIGNATURE-
Processed: severity of 872439 is serious
Processing commands for cont...@bugs.debian.org: > severity 872439 serious Bug #872439 [libsoc-dev] libsoc-dev: libsoc_gpio.h is missing stdlib.h include Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 872439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914537: openmw: segfault at start
Am 04.02.19 um 14:31 schrieb psi...@gmail.com: > Hello Markus, > > as it turns out, we're about to have another release 0.45 that has been in > 'the-works' for the past month. It's been ready for awhile, we've just been > waiting on PR to make a release video and finish up a write-up. > > I'll ask the team if they feel comfortable with a release on Debian (and > eventually Ubuntu) before it's made official. > > What is my drop-dead date for getting this in? > > Cheers, > Bret The soft freeze starts at 12.02.2019 and openmw must be in testing by this date. Wednesday, maybe Thursday, is the deadline. https://release.debian.org/buster/freeze_policy.html Cheers, Markus signature.asc Description: OpenPGP digital signature
Bug#918807: marked as done (taurus: FTBFS with Sphinx 1.8: No module named pngmath)
Your message dated Mon, 04 Feb 2019 13:50:37 + with message-id and subject line Bug#918807: fixed in taurus 4.5.0+dfsg-1 has caused the Debian Bug report #918807, regarding taurus: FTBFS with Sphinx 1.8: No module named pngmath to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: taurus Version: 4.0.3+dfsg-1 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.8 Dear Maintainer, taurus fails to build with Sphinx 1.8, currently available in experimental: Running Sphinx v1.8.3 [...] Extension error: Could not import extension sphinx.ext.pngmath (exception: No module named pngmath) The pngmath extension was deprecated in Sphinx 1.4 and has been removed [1] in Sphinx 1.8. The recommended alternative is sphinx.ext.imgmath [2] which also has SVG support in addition to PNG. However, it looks like taurus is using no math directives or roles, so the pngmath extension can be simply removed. Upstream has already done it in [3]. [1]: https://github.com/sphinx-doc/sphinx/pull/4702 [2]: https://www.sphinx-doc.org/en/1.8/usage/extensions/math.html [3]: https://github.com/taurus-org/taurus/commit/8a5fb0772f734f45 -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: taurus Source-Version: 4.5.0+dfsg-1 We believe that the bug you reported is fixed in the latest version of taurus, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carlos Pascual (supplier of updated taurus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 30 Jan 2019 10:52:00 + Source: taurus Binary: python-taurus python-taurus-doc Architecture: source Version: 4.5.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Carlos Pascual Description: python-taurus - Framework for scientific/industrial CLIs and GUIs - Python2 python-taurus-doc - Framework for scientific/industrial CLIs and GUIs - Documentation Closes: 849617 875202 918807 Changes: taurus (4.5.0+dfsg-1) unstable; urgency=medium . * New upstream version 4.5.0 (closes: #875202, #918807 ) * Suggest python-taurus-doc in bin packages (closes: #849617 ) * Standards-Version bump to 4.3.0 (nothing to do) * Make debian/watch file a dummy one * Drop existing quilt patch queue * Remove existing local-options * Remove .tangorc * Update d/copyright * Update depend and add cpascual as uploader * Update doc-base metadata * Fix various lintian warnings * Add patch to avoid privacy-breach lintian error Checksums-Sha1: 8edd6f2ab741544483462eea6ab094eab13b16f1 2547 taurus_4.5.0+dfsg-1.dsc 7be5b0c9a3c586e2df2695ffbfa492b37e63a64d 7064244 taurus_4.5.0+dfsg.orig.tar.xz ba0b64b1acdac40c31f4957ffa0fa036f9a18226 17916 taurus_4.5.0+dfsg-1.debian.tar.xz Checksums-Sha256: 1a75c80e4bd657035ac8058f88599873fea9b6308693fa0acecf8b175550c015 2547 taurus_4.5.0+dfsg-1.dsc bb36d57c64aff9dbca4a6f9c39ccdf7a10ef98e597d10d4b348cdf7ce144bc09 7064244 taurus_4.5.0+dfsg.orig.tar.xz ed7dc3442aa2a6be9ea99aa2b9ccd0ca6b04cc7fab15220a774b48306ca1e253 17916 taurus_4.5.0+dfsg-1.debian.tar.xz Files: e7f6b811e1a65e2a5fecbb0cead4543c 2547 science optional taurus_4.5.0+dfsg-1.dsc 1c1ece1083e043bf7b63f5c10dc60257 7064244 science optional taurus_4.5.0+dfsg.orig.tar.xz 15ab20f6e4a152b25cae0f92c100663d 17916 science optional taurus_4.5.0+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE6S5+bp6dprGqMTncVjKQb0aW4BUFAlxYQBoRHHBpY2NhQGRl Ymlhbi5vcmcACgkQVjKQb0aW4BW1nA/8DZOX6dAZJn6ReqT5oKpR/i53C5JsBYQL YNbbDTu9/vJP/SB+81+fAo5NxtTgpNaMy7mx43xMqvy+q8vaM7iywaKW4IrXM0Sc bJVpVc5HrFMo3LyI0XoT4XzfCzHrUAwZKS8nnZOsKltSjo8Xm9eTVgTA7cPlhbpF YyNABQV2MS94vTGdNSaSYOtHLI58D3SYZTgJ83d25NgBMzIiypU5eFhIqiVGCDz3 pnFA5sgXXyfvpUr/4zssMeCzytnu4ZcGDGS5I1KowqNV3uCYnm8H+aNErLCXgMdS eR+YZFGFVPWKZmt2YM6/u2tMcUGd8bCGq0Muw6OyxNtifiGefSYZpHMBgKQr8phL VJ3M1tdZqCyaZwl5q
Bug#921183: marked as done (python3-surfer: missing Breaks+Replaces: python-surfer (<< 0.9.0))
Your message dated Mon, 04 Feb 2019 13:50:07 + with message-id and subject line Bug#921183: fixed in pysurfer 0.9.0-2 has caused the Debian Bug report #921183, regarding python3-surfer: missing Breaks+Replaces: python-surfer (<< 0.9.0) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-surfer Version: 0.9.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces From the attached log (scroll to the bottom...): Preparing to unpack .../python3-surfer_0.9.0-1_all.deb ... Unpacking python3-surfer (0.9.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-surfer_0.9.0-1_all.deb (--unpack): trying to overwrite '/usr/bin/pysurfer', which is also in package python-surfer 0.7-2.1 Errors were encountered while processing: /var/cache/apt/archives/python3-surfer_0.9.0-1_all.deb cheers, Andreas python-surfer=0.7-2.1_python3-surfer=0.9.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: pysurfer Source-Version: 0.9.0-2 We believe that the bug you reported is fixed in the latest version of pysurfer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated pysurfer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Feb 2019 14:26:38 +0100 Source: pysurfer Binary: python-surfer python3-surfer Architecture: source Version: 0.9.0-2 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Andreas Tille Description: python-surfer - visualize Freesurfer's data in Python2 python3-surfer - visualize Freesurfer's data in Python3 Closes: 921183 Changes: pysurfer (0.9.0-2) unstable; urgency=medium . * Team upload * Add NEWS.Debian about the move of the executable * Breaks / Replaces: python-surfer (<= 0.7-1) Closes: #921183 Checksums-Sha1: 7ad7f8f3cf927a977a88f3e04dfec4383541b5c7 2321 pysurfer_0.9.0-2.dsc a31a60109b58fbe95b742d3b1e4d186c1256bac6 4304 pysurfer_0.9.0-2.debian.tar.xz 10ce28bea6fe4372e0419dc260580b827806feda 17407 pysurfer_0.9.0-2_source.buildinfo Checksums-Sha256: 8615a6ae294348c1a03790a4d89d5e73ce8e9ac912edbaf583299b770914c6b4 2321 pysurfer_0.9.0-2.dsc b402c372d4d5c3e52624d68292f1ccaafe7ec1c29781cc3d03efff8e9d8f6b07 4304 pysurfer_0.9.0-2.debian.tar.xz 0e75de49aede9891b33b21e2f071abde686d4e327c19a27fa2b90b3a0b504606 17407 pysurfer_0.9.0-2_source.buildinfo Files: e3bf445cb2ae520e6211f93abf02f9c8 2321 python optional pysurfer_0.9.0-2.dsc e02f260bc571a37ab0ca2a774bd579fb 4304 python optional pysurfer_0.9.0-2.debian.tar.xz 725b0fefe0b22ae9e3a491475d8911a1 17407 python optional pysurfer_0
Processed: severity of 873719 is serious
Processing commands for cont...@bugs.debian.org: > severity 873719 serious Bug #873719 [libsc-dev] /usr/bin/sc-libtool: Command not found Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 873719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897945: [Openjdk] Bug#920037: Bug#897945: #897945 still present/breaks with Java 8
On 2/1/19 11:20 AM, Matthias Klose wrote: > On 01.02.19 10:03, Emmanuel Bourg wrote: >> This is an excellent suggestion. We should file a bug for openjdk-8 to >> implement that. > please attach the patch. Sure, I should be able to write something up. Forbear my ignorance: should I use debconf to show the message or what do you think would be right approach? (I haven't been involved at this level in Debian since I stepped down as package maintainer 15 years ago. :) Best regards, Per
Bug#897945: [Openjdk] Bug#920037: Bug#897945: #897945 still present/breaks with Java 8
Am 04.02.19 um 14:56 schrieb Per Lundberg: > On 2/1/19 11:20 AM, Matthias Klose wrote: >> On 01.02.19 10:03, Emmanuel Bourg wrote: > >>> This is an excellent suggestion. We should file a bug for openjdk-8 to >>> implement that. >> please attach the patch. > > Sure, I should be able to write something up. Forbear my ignorance: > should I use debconf to show the message or what do you think would be > right approach? (I haven't been involved at this level in Debian since I > stepped down as package maintainer 15 years ago. :) > > Best regards, > Per > Hi, I would add a NEWS file to OpenJDK 8 and explain the situation and in addition create a wrapper around the OpenJDK 8 java command that prints out a message and quits. javac shall continue to work because it is needed to build some packages. The debconf approach could also work but it is a bit more work to implement. Then we also announce it via release news. Just some thoughts. Best, Markus signature.asc Description: OpenPGP digital signature
Bug#911507: marked as done (offlineimap: fails to load imaplib2)
Your message dated Mon, 4 Feb 2019 16:04:52 +0200 with message-id <20190204140452.GA10852@localhost> and subject line Re: Bug#911507: offlineimap: fails to load imaplib2 has caused the Debian Bug report #911507, regarding offlineimap: fails to load imaplib2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 911507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: offlineimap Version: 7.0.12+dfsg1-2 Severity: grave Justification: renders package unusable Dear Maintainer, calling offlineimap stops reporting Error while trying to import system imaplib2: name '__revision__' is not defined Traceback (most recent call last): File "/usr/bin/offlineimap", line 20, in from offlineimap import OfflineImap File "/usr/share/offlineimap/offlineimap/__init__.py", line 20, in from offlineimap.init import OfflineImap File "/usr/share/offlineimap/offlineimap/init.py", line 29, in import offlineimap.virtual_imaplib2 as imaplib File "/usr/share/offlineimap/offlineimap/virtual_imaplib2.py", line 43, in from offlineimap.bundled_imaplib2 import * ImportError: No module named bundled_imaplib2 looks like to be related to the 'new' python-imaplib2 (2.57-5) -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.14.70-sunxi (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages offlineimap depends on: ii python 2.7.13-2 ii python-imaplib2 2.55-1+deb9u1 ii python-six 1.10.0-3 Versions of packages offlineimap recommends: pn python-socks Versions of packages offlineimap suggests: pn python-kerberos -- no debconf information --- End Message --- --- Begin Message --- On Sun, Jan 27, 2019 at 05:23:04PM +0100, Hans-Joachim wrote: > Hello, > > after your mail, I've reactivated the offlineimap script. > > Now all works fine. Thank you Thanks, closing. > Best, > > Hans-Joachim cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Processed: tagging 917083
Processing commands for cont...@bugs.debian.org: > tags 917083 + confirmed Bug #917083 [mysql-workbench] mysql-workbench: Cannot Connect to Database: Unsupported option provided to mysql_options() Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 917083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 917083
Processing commands for cont...@bugs.debian.org: > tags 917083 + upstream help Bug #917083 [mysql-workbench] mysql-workbench: Cannot Connect to Database: Unsupported option provided to mysql_options() Added tag(s) upstream and help. > thanks Stopping processing here. Please contact me if you need assistance. -- 917083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 917083 is forwarded to https://bugs.mysql.com/bug.php?id=78947
Processing commands for cont...@bugs.debian.org: > forwarded 917083 https://bugs.mysql.com/bug.php?id=78947 Bug #917083 [mysql-workbench] mysql-workbench: Cannot Connect to Database: Unsupported option provided to mysql_options() Set Bug forwarded-to-address to 'https://bugs.mysql.com/bug.php?id=78947'. > thanks Stopping processing here. Please contact me if you need assistance. -- 917083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921349: frr: build dependency problems
Source: frr Version: 6.0.2-1 Severity: serious Tags: ftbfs Build-Depends: ... libjson0 | libjson-c2 | libjson-c3, libjson0-dev | libjson-c-dev, ... There are two bugs: 1. build depending on the shared library package is usually a bug, the -dev should pull in everything 2. the unstable buildds only consider the first alternative libjson-c-dev is even in oldstable, so can replace all of the above.
Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init
On Sun, Feb 3, 2019 at 6:41 PM Felipe Sateler wrote: > Control: forwarded -1 https://github.com/systemd/systemd/issues/11645 > > I have forwarded the bug upstream, and proposed two solutions. If upstream > likes one, we can apply that in the debian package. > > Upstream asks if cgroup is in v2-mode in the affected systems. This might cause the detection logic to get tripped. If you can report back whether that is the case, preferably directly on the upsteam issue, it would be great. -- Saludos, Felipe Sateler
Bug#921351: prometheus-postfix-exporter: Init script missing
Package: prometheus-postfix-exporter Version: 0.1.2-1 Severity: serious Justification: Policy 9.11 Excerpt from policy 9.11: However, any package integrating with other init systems must also be backwards-compatible with sysvinit by providing a SysV- style init script with the same name as and equivalent functionality to any init-specific job, as this is the only start-up configuration method guaranteed to be supported by all init implementations. The package violates a policy must by not providing s sysvint init script. Scott K
Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init
Hi Felipe, Felipe Sateler wrote: > Upstream asks if cgroup is in v2-mode in the affected systems. How do I recognize this? I have no idea of how to check that. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init
On Mon, Feb 4, 2019 at 11:34 AM Axel Beckert wrote: > Hi Felipe, > > Felipe Sateler wrote: > > Upstream asks if cgroup is in v2-mode in the affected systems. > > How do I recognize this? I have no idea of how to check that. > With `findmnt -R /sys/fs/cgroup`. It should list controllers in the cgroup or cgroup2 filesystems. -- Saludos, Felipe Sateler
Bug#921247: marked as done (Boost.Compute users FTBFS with GCC 8)
Your message dated Mon, 04 Feb 2019 14:45:32 +
with message-id
and subject line Bug#921247: fixed in boost1.67 1.67.0-13
has caused the Debian Bug report #921247,
regarding Boost.Compute users FTBFS with GCC 8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
921247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libboost1.67-dev
Version: 1.67.0-12
Control: tags -1 fixed-upstream patch
Control: affects -1 src:arrayfire
In GCC 8, #including svm_ptr.hpp (including via other Boost.Compute
headers, and whether or not it is actually used) is an error, as GCC 8
rejects known non-instantiable templates even if the program doesn't
actually try to instantiate them:
https://gcc.gnu.org/gcc-8/porting_to.html#hypothetical-instantiation
This causes at least arrayfire (#897707) to FTBFS.
Fix:
Description: Fix FTBFS when svm_ptr is #included (e.g. arrayfire)
Author: Pradeep "9prady9"
Origin: upstream https://github.com/boostorg/compute/pull/776
Bug-Debian: https://bugs.debian.org/
--- a/libs/compute/include/boost/compute/memory/svm_ptr.hpp
+++ b/libs/compute/include/boost/compute/memory/svm_ptr.hpp
@@ -126,7 +126,7 @@ public:
return m_ptr - other.m_ptr;
}
-context& get_context() const
+const context& get_context() const
{
return m_context;
}
--- End Message ---
--- Begin Message ---
Source: boost1.67
Source-Version: 1.67.0-13
We believe that the bug you reported is fixed in the latest version of
boost1.67, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Anton Gladky (supplier of updated boost1.67 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 04 Feb 2019 15:25:45 +0100
Source: boost1.67
Binary: libboost1.67-dev libboost1.67-tools-dev libboost1.67-all-dev
libboost1.67-doc libboost-atomic1.67.0 libboost-atomic1.67-dev
libboost-chrono1.67.0 libboost-chrono1.67-dev libboost-container1.67.0
libboost-container1.67-dev libboost-context1.67.0 libboost-context1.67-dev
libboost-contract1.67.0 libboost-contract1.67-dev libboost-coroutine1.67.0
libboost-coroutine1.67-dev libboost-date-time1.67.0 libboost-date-time1.67-dev
libboost-exception1.67-dev libboost-fiber1.67.0 libboost-fiber1.67-dev
libboost-filesystem1.67.0 libboost-filesystem1.67-dev libboost-graph1.67.0
libboost-graph1.67-dev libboost-graph-parallel1.67.0
libboost-graph-parallel1.67-dev libboost-iostreams1.67.0
libboost-iostreams1.67-dev libboost-locale1.67.0 libboost-locale1.67-dev
libboost-log1.67.0 libboost-log1.67-dev libboost-math1.67.0
libboost-math1.67-dev libboost-mpi1.67.0 libboost-mpi1.67-dev
libboost-mpi-python1.67.0 libboost-mpi-python1.67-dev libboost-numpy1.67.0
libboost-numpy1.67-dev
libboost-program-options1.67.0 libboost-program-options1.67-dev
libboost-python1.67.0 libboost-python1.67-dev libboost-random1.67.0
libboost-random1.67-dev libboost-regex1.67.0 libboost-regex1.67-dev
libboost-serialization1.67.0 libboost-serialization1.67-dev
libboost-signals1.67.0 libboost-signals1.67-dev libboost-stacktrace1.67.0
libboost-stacktrace1.67-dev libboost-system1.67.0 libboost-system1.67-dev
libboost-test1.67.0 libboost-test1.67-dev libboost-thread1.67.0
libboost-thread1.67-dev libboost-timer1.67.0 libboost-timer1.67-dev
libboost-type-erasure1.67.0 libboost-type-erasure1.67-dev libboost-wave1.67.0
libboost-wave1.67-dev
Architecture: source
Version: 1.67.0-13
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team
Changed-By: Anton Gladky
Description:
libboost-atomic1.67-dev - atomic data types, operations, and memory ordering
constraints
libboost-atomic1.67.0 - atomic data types, operations, and memory ordering
constraints
libboost-chrono1.67-dev - C++ representation of time duration, time point, and
clocks
libboost-chrono1.67.0 - C++ representation of time duration, time point, and
clocks
libboost-container1.67-dev - C++ library that implements several well-known
containers - dev f
libboost-container1.67.0 - C++ libr
Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init
Hi Felipe, Felipe Sateler wrote: > > > Upstream asks if cgroup is in v2-mode in the affected systems. > > > > How do I recognize this? I have no idea of how to check that. > > With `findmnt -R /sys/fs/cgroup`. It should list controllers in the cgroup > or cgroup2 filesystems. Thanks! This currently looks like this now (after I have uninstalled cgroupfs-mount): → findmnt -R /sys/fs/cgroup TARGET SOURCE FSTYPE OPTIONS /sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,mode=755 ├─/sys/fs/cgroup/unified cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate └─/sys/fs/cgroup/elogind cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/elogind But I have to assume that these mount points where at least present before I uninstalled cgroupfs-mount, too. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#917676: marked as done (hkl: FTBFS: ../../hkl/ccan/generator/generator.h:23:2: error: #error Generators require coroutines)
Your message dated Mon, 04 Feb 2019 14:48:42 + with message-id and subject line Bug#916867: fixed in hkl 5.0.0.2456-1 has caused the Debian Bug report #916867, regarding hkl: FTBFS: ../../hkl/ccan/generator/generator.h:23:2: error: #error Generators require coroutines to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hkl Version: 5.0.0.2449-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o generator/generator.lo generator/generator.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I../.. -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c > generator/generator.c -fPIC -DPIC -o generator/.libs/generator.o > In file included from generator/generator.c:8: > ../../hkl/ccan/generator/generator.h:23:2: error: #error Generators require > coroutines > #error Generators require coroutines > ^ > make[5]: *** [Makefile:605: generator/generator.lo] Error 1 The full build log is available from: http://aws-logs.debian.net/2018/12/29/hkl_5.0.0.2449-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: hkl Source-Version: 5.0.0.2456-1 We believe that the bug you reported is fixed in the latest version of hkl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Picca Frédéric-Emmanuel (supplier of updated hkl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Feb 2019 15:31:54 +0100 Source: hkl Binary: ghkl libhkl5 libhkl-dev libhkl-dbg libhkl-doc gir1.2-hkl-5.0 Architecture: source Version: 5.0.0.2456-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Picca Frédéric-Emmanuel Description: ghkl - diffractometer computation control application gir1.2-hkl-5.0 - diffractometer computation control library - gir binding libhkl-dbg - diffractometer computation control library - debug symbols libhkl-dev - diffractometer computation control library - development files libhkl-doc - diffractometer computation control library - documentation libhkl5- diffractometer computation control library Closes: 916867 Changes: hkl (5.0.0.2456-1) unstable; urgency=medium . * New upstream version 5.0.0.2456 * Use secure URI in Homepage field. * d/control - Build-Depends: - Added: elpa-htmlize thanks to Sean Whitton (Closes: #916867) - Droped: dh-autoconf. - Bump Standards-Version to 4.2.1 (nothing to do) * d/rules: run autogen.sh via dh_override_autoreconf * d/watch: Use the git mode * d/gitlab-ci.yml: Added for salsa CI. Checksums-Sha1: 2c6bca1cdf40c4736e25143c919d041147d57326 2675 hkl_5.0.0.2456-1.dsc 9e4d7ec1f930b8c67d41d64e240bc169db232bc4 11630716 hkl_5.0.0.2456.orig.tar.xz 7b6200b295ceba6278f54df5b839b18c52f85eee 9908 hkl_5.0.0.2456-1.debian.tar.xz Checksums-Sha256: 69af79b2a68a834065e993ca2fc5fc347bd5ef526ae9deb73ec933b7cbdc3db1 2675 hkl_5.0.0.2456-1.dsc 42e228968178153e3ca6318505768e222c725727ad6ec30ce6e7e16c2a7950f0 11630716 hkl_5.0.0.2456.orig.tar.xz 03f9dd4dd745d19c8657ca0845a0dd26f7fd536b7d6088db88b2af2cafa5f5c4 9908 hkl_5.0.0.2456-1.debian.tar.xz Files: 07d77d0a763b5b233d5629a501
Bug#907148: marked as done (kmail: FTBFS in buster/sid (invalid use of incomplete type 'class QButtonGroup'))
Your message dated Mon, 04 Feb 2019 15:44:29 +0100 with message-id <1891567.C0YfhY37kB@tuxin> and subject line done with 4:18.07.90-1 has caused the Debian Bug report #907148, regarding kmail: FTBFS in buster/sid (invalid use of incomplete type 'class QButtonGroup') to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kmail Version: 4:17.12.3-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.pl --with=kf5,pkgkde-symbolshelper dpkg-buildflags --export=make > debian/dhmk_env.mk /usr/bin/make -f debian/rules dhmk_run_configure_commands DHMK_TARGET="configure" make[1]: Entering directory '/<>' dh_testdir # [-i] dh_auto_configure '--buildsystem=kf5' --parallel # [-i] cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON .. -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done [... snipped ...] /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note: forward declaration of 'class QButtonGroup' class QButtonGroup; ^~~~ /<>/src/configuredialog/configuresecuritypage.cpp:432:54: error: invalid use of incomplete type 'class QButtonGroup' QButtonGroup *bgHTTPProxy = new QButtonGroup(this); ^ In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qcheckbox.h:44, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QCheckBox:1, from /<>/obj-x86_64-linux-gnu/src/ui_securitypagegeneraltab.h:16, from /<>/src/configuredialog/configuresecuritypage.h:23, from /<>/src/configuredialog/configuresecuritypage.cpp:18: /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note: forward declaration of 'class QButtonGroup' class QButtonGroup; ^~~~ /<>/src/configuredialog/configuresecuritypage.cpp:433:16: error: invalid use of incomplete type 'class QButtonGroup' bgHTTPProxy->addButton(mWidget->honorHTTPProxyRB); ^~ In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qcheckbox.h:44, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QCheckBox:1, from /<>/obj-x86_64-linux-gnu/src/ui_securitypagegeneraltab.h:16, from /<>/src/configuredialog/configuresecuritypage.h:23, from /<>/src/configuredialog/configuresecuritypage.cpp:18: /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note: forward declaration of 'class QButtonGroup' class QButtonGroup; ^~~~ /<>/src/configuredialog/configuresecuritypage.cpp:434:16: error: invalid use of incomplete type 'class QButtonGroup' bgHTTPProxy->addButton(mWidget->useCustomHTTPProxyRB); ^~ In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qcheckbox.h:44, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QCheckBox:1, from /<>/obj-x86_64-linux-gnu/src/ui_securitypagegeneraltab.h:16, from /<>/src/configuredialog/configuresecuritypage.h:23, from /<>/src/configuredialog/configuresecuritypage.cpp:18: /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note: forward declaration of 'class QButtonGroup' class QButtonGroup; ^~~~ make[4]: *** [src/CMakeFiles/kmailprivate.dir/build.make:1174: src/CMakeFiles/kmailprivate.dir/configuredialog/configuresecuritypage.cpp.o] Error 1 make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[3]: *** [CMakeFiles/Makefile2:2965: src/CMakeFiles/kmailprivate.dir/all] Error 2 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [Makefile:144: all] Error 2 make[2]:
Bug#907230: marked as done (kmail-account-wizard: FTBFS with Qt 5.11)
Your message dated Mon, 04 Feb 2019 15:45:19 +0100 with message-id <2801459.TEKKCr9l1F@tuxin> and subject line Done with 4:18.07.90-1 has caused the Debian Bug report #907230, regarding kmail-account-wizard: FTBFS with Qt 5.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kmail-account-wizard Version: 4:17.12.3-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch /usr/bin/make -f debian/rules dhmk_run_configure_commands DHMK_TARGET="configure" make[1]: Entering directory '/<>' dh_testdir # [-a] dh_auto_configure '--buildsystem=kf5' --parallel # [-a] cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON .. -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done [... snipped ...] static bool disconnect(const QObject *sender, const char *signal, ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:337:17: note: no known conversion for argument 1 from 'QAction*' to 'const QObject*' /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:339:17: note: candidate: 'static bool QObject::disconnect(const QObject*, const QMetaMethod&, const QObject*, const QMetaMethod&)' static bool disconnect(const QObject *sender, const QMetaMethod &signal, ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:339:17: note: no known conversion for argument 1 from 'QAction*' to 'const QObject*' /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:341:17: note: candidate: 'bool QObject::disconnect(const char*, const QObject*, const char*) const' inline bool disconnect(const char *signal = nullptr, ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:341:17: note: candidate expects 3 arguments, 4 provided /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:344:17: note: candidate: 'bool QObject::disconnect(const QObject*, const char*) const' inline bool disconnect(const QObject *receiver, const char *member = nullptr) const ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:344:17: note: candidate expects 2 arguments, 4 provided /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:346:17: note: candidate: 'static bool QObject::disconnect(const QMetaObject::Connection&)' static bool disconnect(const QMetaObject::Connection &); ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:346:17: note: candidate expects 1 argument, 4 provided /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:353:24: note: candidate: 'template static bool QObject::disconnect(const typename QtPrivate::FunctionPointer::Object*, Func1, const typename QtPrivate::FunctionPointer::Object*, Func2)' static inline bool disconnect(const typename QtPrivate::FunctionPointer::Object *sender, Func1 signal, ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:353:24: note: template argument deduction/substitution failed: /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 'template static bool QObject::disconnect(const typename QtPrivate::FunctionPointer::Object*, Func1, const typename QtPrivate::FunctionPointer::Object*, Func2) [with Func1 = int; Func2 = int]': /<>/src/dialog.cpp:112:77: required from here /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:353:24: error: no type named 'Object' in 'struct QtPrivate::FunctionPointer' /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:370:24: note: candidate: 'template static bool QObject::disconnect(const typename QtPrivate::FunctionPointer::Object*, Func1, const QObject*, void**)' static inline bool disconnect(const typename QtPrivate::
Bug#907154: marked as done (akonadi-import-wizard: FTBFS in buster/sid (invalid use of incomplete type 'class QAction'))
Your message dated Mon, 04 Feb 2019 15:50:21 +0100 with message-id <2412149.45o5CatmPR@tuxin> and subject line Done with 4:18.07.90-1 has caused the Debian Bug report #907154, regarding akonadi-import-wizard: FTBFS in buster/sid (invalid use of incomplete type 'class QAction') to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:akonadi-import-wizard Version: 4:17.12.3-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch /usr/bin/make -f debian/rules dhmk_run_configure_commands DHMK_TARGET="configure" make[1]: Entering directory '/<>' dh_testdir # [-a] dh_auto_configure '--buildsystem=kf5' --parallel # [-a] cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON .. -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done [... snipped ...] cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -DKDE_UIC_EXECUTABLE:FILEPATH=/usr/lib/qt5/bin/uic -DKDE_UIC_FILE:FILEPATH=/<>/src/ui/autodetect/importsettingpage.ui -DKDE_UIC_H_FILE:FILEPATH=/<>/obj-x86_64-linux-gnu/src/ui_importsettingpage.h -DKDE_UIC_BASENAME:STRING=importsettingpage -P /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/kf5i18nuic.cmake [ 25%] Generating ui_selectcomponentpage.h cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -DKDE_UIC_EXECUTABLE:FILEPATH=/usr/lib/qt5/bin/uic -DKDE_UIC_FILE:FILEPATH=/<>/src/ui/autodetect/selectcomponentpage.ui -DKDE_UIC_H_FILE:FILEPATH=/<>/obj-x86_64-linux-gnu/src/ui_selectcomponentpage.h -DKDE_UIC_BASENAME:STRING=selectcomponentpage -P /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/kf5i18nuic.cmake /<>/src/ui/autodetect/selectcomponentpage.ui: Warning: Z-order assignment: 'verticalSpacer' is not a valid widget. /<>/src/ui/autodetect/selectcomponentpage.ui: Warning: Z-order assignment: 'horizontalSpacer_2' is not a valid widget. [ 26%] Generating ui_importfinishpage.h cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -DKDE_UIC_EXECUTABLE:FILEPATH=/usr/lib/qt5/bin/uic -DKDE_UIC_FILE:FILEPATH=/<>/src/ui/autodetect/importfinishpage.ui -DKDE_UIC_H_FILE:FILEPATH=/<>/obj-x86_64-linux-gnu/src/ui_importfinishpage.h -DKDE_UIC_BASENAME:STRING=importfinishpage -P /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/kf5i18nuic.cmake [ 27%] Generating ui_importcalendarpage.h cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -DKDE_UIC_EXECUTABLE:FILEPATH=/usr/lib/qt5/bin/uic -DKDE_UIC_FILE:FILEPATH=/<>/src/ui/autodetect/importcalendarpage.ui -DKDE_UIC_H_FILE:FILEPATH=/<>/obj-x86_64-linux-gnu/src/ui_importcalendarpage.h -DKDE_UIC_BASENAME:STRING=importcalendarpage -P /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/kf5i18nuic.cmake [ 28%] Generating ui_manualimportmailpage.h cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -DKDE_UIC_EXECUTABLE:FILEPATH=/usr/lib/qt5/bin/uic -DKDE_UIC_FILE:FILEPATH=/<>/src/ui/manual/manualimportmailpage.ui -DKDE_UIC_H_FILE:FILEPATH=/<>/obj-x86_64-linux-gnu/src/ui_manualimportmailpage.h -DKDE_UIC_BASENAME:STRING=manualimportmailpage -P /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/kf5i18nuic.cmake cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/src /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src /<>/obj-x86_64-linux-gnu/src/CMakeFiles/akonadiimportwizard.dir/DependInfo.cmake --color= Scanning dependencies of target akonadiimportwizard make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f src/CMakeFiles/akonadiimportwizard.dir/build.make src/CMakeFiles/akonadiimportwizard.dir/build make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 29%] Building CXX object src/CMakeFiles/akonadiimportwizard.dir/main.cpp.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DBUILD_TESTING -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB -DQT_
Bug#888903: marked as done (jsbeautifier,node-js-beautify: both ship /usr/bin/js-beautify)
Your message dated Mon, 04 Feb 2019 15:06:40 + with message-id and subject line Bug#60: fixed in node-js-beautify 1.7.5+dfsg-2 has caused the Debian Bug report #60, regarding jsbeautifier,node-js-beautify: both ship /usr/bin/js-beautify to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 60: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=60 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jsbeautifier,node-js-beautify Severity: serious Tags: buster sid User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 1.6.4-6 Control: found -1 1.7.5+dfsg-1 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package node-js-beautify. Preparing to unpack .../12-node-js-beautify_1.7.5+dfsg-1_all.deb ... Unpacking node-js-beautify (1.7.5+dfsg-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Vb7dNE/12-node-js-beautify_1.7.5+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/bin/js-beautify', which is also in package jsbeautifier 1.6.4-6 Errors were encountered while processing: /tmp/apt-dpkg-install-Vb7dNE/12-node-js-beautify_1.7.5+dfsg-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/js-beautify This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. If this is a source package rename, you'll need a ftp.d.o RM request for the old package and Breaks+Replaces in the new one. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html jsbeautifier=1.6.4-6_node-js-beautify=1.7.5+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: node-js-beautify Source-Version: 1.7.5+dfsg-2 We believe that the bug you reported is fixed in the latest version of node-js-beautify, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paolo Greppi (supplier of updated node-js-beautify package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Feb 2019 13:57:47 +0100 Source: node-js-beautify Binary: node-js-beautify Architecture: source Version: 1.7.5+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Xavier Guimard Changed-By: Paolo Greppi Closes: 60 915100 Description: node-js-beautify - beautifier.io for node Changes: node-js-beautify (1.7.5+dfsg-2) unstable; urgency=medium . * Team upload. . [ Paolo Greppi ] * Bump standard version * Bump debhelper compat * Fix nodejs binary * Remove /usr/bin/js-beautify link (Closes: #60) . [ Xavier Guimard ] * Add tests * Fix install * Add jsbeautifier in recommended dependencies * Add upstream/metadata * Update lintian-overrides * Update homepage * Add node-sigmund and node-semver in dependencies (Closes: #915100) Checksums-Sha1: 73f76bc1fc6cea612eb4a0ad2e709b23dbcf4d0d 2205 node-js-beautify_1.7.5+dfsg-2.dsc 72e0aa31678c300c53bcf0740e1863bf2c0c8b00 19
Bug#916576: marked as done (pbdagcon: FTBFS pbdata/Types.h: No such file or directory)
Your message dated Mon, 04 Feb 2019 15:06:46 + with message-id and subject line Bug#916576: fixed in pbdagcon 0.3+git20161121.000+ds-1 has caused the Debian Bug report #916576, regarding pbdagcon: FTBFS pbdata/Types.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pbdagcon Version: 0.3+20161121+ds-1 Severity: serious Justification: fails to build from source (but built successfully in the past) User: debian...@lists.debian.org Usertags: piuparts Hi, pbdagcon FTBFS in a current pbuilder sid environment https://buildd.debian.org/status/package.php?p=pbdagcon&suite=unstable g++ -g -O2 -fdebug-prefix-map=/<>/pbdagcon-0.3+20161121+ds=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11 -Wall -Wuninitialized -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -MMD -MP -I/<>/pbdagcon-0.3+20161121+ds/DAZZ_DB -I/<>/pbdagcon-0.3+20161121+ds/DALIGNER -I/usr/include/pbseq/alignment -I/usr/include/pbseq/pbdata -I/usr/include/pbseq/hdf -isystem.//third-party -c -o main.o main.cpp In file included from main.cpp:23: /usr/include/pbseq/alignment/tuples/TupleMetrics.hpp:4:10: fatal error: pbdata/Types.h: No such file or directory #include ^~~~ compilation terminated. make[2]: *** [: main.o] Error 1 Andreas --- End Message --- --- Begin Message --- Source: pbdagcon Source-Version: 0.3+git20161121.000+ds-1 We believe that the bug you reported is fixed in the latest version of pbdagcon, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated pbdagcon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Feb 2019 15:36:14 +0100 Source: pbdagcon Binary: pbdagcon Architecture: source Version: 0.3+git20161121.000+ds-1 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: pbdagcon - sequence consensus using directed acyclic graphs Closes: 916576 Changes: pbdagcon (0.3+git20161121.000+ds-1) unstable; urgency=low . * Team upload . [ Afif Elghraoui ] * Add README.source . [ Andreas Tille ] * d/watch: use git mode to detect new upstream commit * Reimport old source with version number fitting git mode * d/get-orig-source: checkout submodules for code copy of DALIGNER and DAZZ_DB which are specific adaptations to pbdagcon * debhelper 12 * Point Vcs fields to salsa.debian.org * Standards-Version: 4.3.0 * Build-Depends: libpbdata-dev Closes: #916576 * Secure URI in copyright format Checksums-Sha1: 055db3f40a2c2bd84701e6c93350ee16553675e0 2206 pbdagcon_0.3+git20161121.000+ds-1.dsc 8dc13b1a5104ff9ef7f630285f7dbd4b891967af 256458 pbdagcon_0.3+git20161121.000+ds.orig.tar.gz 8bcbe0442648d3f04e02f9b1ae41b964418c4ec8 5840 pbdagcon_0.3+git20161121.000+ds-1.debian.tar.xz Checksums-Sha256: 8b1186ba209faea2769b2f256c79a23070ddba07ea1abd2a429cfa252b48cf2d 2206 pbdagcon_0.3+git20161121.000+ds-1.dsc 897b6210e2abf6d15ba7ad9718aa21527bcbd7540e307882e1688abddd8eca17 256458 pbdagcon_0.3+git20161121.000+ds.orig.tar.gz 76e4561c6e77f2f8ea00fbce8136bae3015e6757f6035951c6d59ecd179b0c14 5840 pbdagcon_0.3+git20161121.000+ds-1.debian.tar.xz Files: 4bb6e0529588d9efaa6f6fe6ef3f66d9 2206 science optional pbdagcon_0.3+git20161121.000+ds-1.dsc b48d97cf670cab6322024e4b9e3949ec 256458 science optional pbdagcon_0.3+git20161121.000+ds.orig.tar.gz d7b3d481912a532e2c307097900cba3f 5840 science optional pbdagcon_0.3+git20161121.000+ds-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxYT+0RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEfsw/6AxzE6UOENZlsKQ94vHJVZNu1sknRNe/a 9uhLHfswG8kZL6niZe7+5kZDqI07dmpUQKycJ0lTO+23D8KZYwLR1Z4rfhS3BbGH h4SBXCBjHvC9PrKbCFg4PXFmPOcWVdgbdNT9AiwlqTHuZgqgiNP2MHs74BbMkP84 xKNR5WWyYVQ2LrNpTfGsAac901LI4lnO+EmxTcnq/jfjg5g+5f32mvVyNvVwN
Bug#921119: marked as done (libdfp: missing build-dependency on python3)
Your message dated Mon, 04 Feb 2019 15:06:34 + with message-id and subject line Bug#921119: fixed in libdfp 1.0.13-3 has caused the Debian Bug report #921119, regarding libdfp: missing build-dependency on python3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 921119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdfp Version: 1.0.13-2 Severity: serious Tags: patch Justification: FTBFS User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch Hi Frédéric, In libdfp 1.0.13-2 you've ported the package to use python3 by default instead of python (thanks!), but you do not have a build-dependency on python3. Therefore the package fails to build: [...] dh_auto_test -a make -j8 check VERBOSE=1 make[1]: Entering directory '/<>' [...] /usr/bin/env: 'python3': No such file or directory make[1]: *** [Makefile:388: libdfp-test-ulps.h] Error 127 make[1]: *** Waiting for unfinished jobs make[1]: Leaving directory '/<>' dh_auto_test: make -j8 check VERBOSE=1 returned exit code 2 make: *** [debian/rules:15: build-arch] Error 2 [...] (https://buildd.debian.org/status/fetch.php?pkg=libdfp&arch=ppc64el&ver=1.0.13-2&stamp=1548954631&raw=0) This is fixable by adding python3 to the Build-Depends, since python3 is not guaranteed to be installed in the build environment by default. See attached patch. Even after fixing this bug however, the package still fails to build in Ubuntu with the following error: [...] LC_ALL=C gawk -f scripts/localplt.awk libdfp.so.jmprel | \ LC_ALL=C gawk -f scripts/check-localplt.awk ./sysdeps/generic/localplt.data - \ > check-localplt.out make[1]: *** [Makefile:445: check-localplt.out] Error 1 make[1]: *** Waiting for unfinished jobs [...] (https://launchpad.net/ubuntu/+source/libdfp/1.0.13-2ubuntu1) I haven't investigated any further. Hope that helps, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru libdfp-1.0.13/debian/control libdfp-1.0.13/debian/control --- libdfp-1.0.13/debian/control2019-01-31 07:40:39.0 -0800 +++ libdfp-1.0.13/debian/control2019-02-01 10:32:24.0 -0800 @@ -2,7 +2,7 @@ Priority: optional Maintainer: Frédéric Bonnard Uploaders: Matthias Klose , Dimitri John Ledkov -Build-Depends: debhelper (>= 11~), gawk +Build-Depends: debhelper (>= 11~), gawk, python3 Standards-Version: 4.3.0 Homepage: https://github.com/libdfp/libdfp Vcs-Git: https://salsa.debian.org/debian/libdfp.git --- End Message --- --- Begin Message --- Source: libdfp Source-Version: 1.0.13-3 We believe that the bug you reported is fixed in the latest version of libdfp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Frédéric Bonnard (supplier of updated libdfp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Feb 2019 15:36:11 +0100 Source: libdfp Architecture: source Version: 1.0.13-3 Distribution: unstable Urgency: medium Maintainer: Frédéric Bonnard Changed-By: Frédéric Bonnard Closes: 921119 Changes: libdfp (1.0.13-3) unstable; urgency=medium . * Fix 2 FTBFS. Thanks to Steve Langasek for the bug report, and test on Ubuntu (Closes: #921119) Checksums-Sha1: 1ff19ce0ffba14c7e559bfca3bd5d3bb781615a6 2068 libdfp_1.0.13-3.dsc 581b46afc011796b0c17afa808426a4804009d28 7444 libdfp_1.0.13-3.debian.tar.xz fd17f2f8d9d1ecab0d353f3c56e3e0e2291709b9 6198 libdfp_1.0.13-3_ppc64el.buildinfo Checksums-Sha256: d51702fb5a5aaec1a5d3807b81b65d005bed909a88a472312e23f8b885b509a2 2068 libdfp_1.0.13-3.dsc aa8ea62389a160bb79b6f38b53ec49b3c8a7e728ebf85a819c3a4fdb998ee5b0 7444 libdfp_1.0.13-3.debian.tar.xz dcd8be83211511a1c41118e578d1e0ccc5e8e1034c66d91771415c79c1b5bfca 6198 libdfp_1.0.13-3_ppc64el.buildinfo Fi
Bug#888860: marked as done (node-js-beautify: cannot install: wants to overwrite /usr/bin/js-beautify from package jsbeautifier)
Your message dated Mon, 04 Feb 2019 15:06:40 + with message-id and subject line Bug#60: fixed in node-js-beautify 1.7.5+dfsg-2 has caused the Debian Bug report #60, regarding node-js-beautify: cannot install: wants to overwrite /usr/bin/js-beautify from package jsbeautifier to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 60: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=60 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-js-beautify Version: 1.7.5+dfsg-1 Severity: serious Justification: Policy 10.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 node-js-beautify tries to overwrite the file /usr/bin/js-beautify, which (when installed) is already provided by the package jsbeautifier. Please see Debian Policy §10.1 for ways to solve this: file:///usr/share/doc/debian-policy/policy.html/ch-files.html#binaries - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlpwtDEACgkQLHwxRsGg ASEQzg//Wz255p1CMXS3YGJ0ehkUzmI6Gpcr5lIEcLmf1jy0tF7ejm0rEE9znvj9 tMqGxzU1kscGKypEA90owxt1BgerziyBtl/l1K6vnupRv6L+EnMxleX1ACDdAMhN b3E78A74lhGx5D+xXzCxwROvf70MdZ5Nfw7EEWIJ3Ejj8J/mHGa6e3cTJw01rnQF +udaiQ3Oqbun2ji9cAud9SzXyyKHZQV9YwjhpLqps+Xvd+23TWy6WiIzxeiQreFh VwMpCUnDbvGESkbgidXkF1s10a2dY0vhDJBlYdOSX4XmSVnrYrQ/LHlONtASc7Rv Kzo+EK/uo1V1177z1zmQZApEGBDk2oVjYLWUYuIsZDulaGsSJ+Yy+737f2mOUVjf +qKEW5zQBJy6hlkmabnj81zagC5i+GXtugqkYkLBMtEojMnU8BXlqWh/ZzUbCJCG KVTZOH20ee90v1FhJwe4Ql2UBTvDsuSgcyfrd29Qts2WMgEJgjhNdW/Jf0DzDSeh 2u82IaTRDmmvrmIEu0dOR2wM1phjWeNXJDe9CLVCpOWCco2kqh29ZMamM+0I1TyL /wCJ3ICElZLCkfMp/0ZcWWPNwEZ/bgFDwP+BnsChs2CtQXqWH7G/1BNdMYPrIJ8L fEHq8KFEbQ57+NN1J3snFtHl0h6mQ02FWTxyeG+G8JdnPbqC01Q= =f92K -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: node-js-beautify Source-Version: 1.7.5+dfsg-2 We believe that the bug you reported is fixed in the latest version of node-js-beautify, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paolo Greppi (supplier of updated node-js-beautify package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Feb 2019 13:57:47 +0100 Source: node-js-beautify Binary: node-js-beautify Architecture: source Version: 1.7.5+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Xavier Guimard Changed-By: Paolo Greppi Closes: 60 915100 Description: node-js-beautify - beautifier.io for node Changes: node-js-beautify (1.7.5+dfsg-2) unstable; urgency=medium . * Team upload. . [ Paolo Greppi ] * Bump standard version * Bump debhelper compat * Fix nodejs binary * Remove /usr/bin/js-beautify link (Closes: #60) . [ Xavier Guimard ] * Add tests * Fix install * Add jsbeautifier in recommended dependencies * Add upstream/metadata * Update lintian-overrides * Update homepage * Add node-sigmund and node-semver in dependencies (Closes: #915100) Checksums-Sha1: 73f76bc1fc6cea612eb4a0ad2e709b23dbcf4d0d 2205 node-js-beautify_1.7.5+dfsg-2.dsc 72e0aa31678c300c53bcf0740e1863bf2c0c8b00 19512 node-js-beautify_1.7.5+dfsg-2.debian.tar.xz Checksums-Sha256: e1016918e2bce1d10b2fb6c651b97b7fc88a1b65ed58ba4b0d6b6e305cc5b799 2205 node-js-beautify_1.7.5+dfsg-2.dsc 8eaabe88a1b6c676f6bee754719fb36180291b78d7b7a22cfc83fdf33ed09c66 19512 node-js-beautify_1.7.5+dfsg-2.debian.tar.xz Files: c2d9111927fe0fdb390f6145ffd51c25 2205 javascript optional node-js-beautify_1.7.5+dfsg-2.dsc 10c82866ab6f44ca372e8e8d9609b227 19512 javascript optional node-js-beautify_1.7.5+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxYUBoACgkQ9tdMp8mZ 7umSOBAAkGr5Raoh0Iy7fSDbDzjpBNEx/YxFPpfA+his3d2iznAm+fGavFBWWNUE PO9OtOSZPtEWY+Oex400WBvFhqfEbxvGBCorP4wtMroMd+9GdZWgFZSlLzsFldtB kWLLr6h0CgSJlf77VDj4x+mCWY1gM3FI6YaCZXj4aiKq0vNcX6yaeKLyo3W9nWs4 oGll6Wqn7c8Pk9Q4D0HuDXUxMbgiqvMT1pQIwPn2xJ+26nZEMwXeALATyRsL/+gg VF1QhcHmSCucf//QyUr3/JQbQDJDj6s9v+U9ov55rPjlbYnG7SrgNKM8T6D9f9Z+ eP4ncJSEl3sobqioNO0d44IWEJrec7oeejjsEjBIMTRmAN/UpRkYlCARgwrgpffr celdbfm1Fjz2SRCbhFg2mtAAVxUCkON2z0ZGHC+Xy6T8yRYUy
Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init
> This currently looks like this now (after I have uninstalled > cgroupfs-mount): > > → findmnt -R /sys/fs/cgroup > TARGET SOURCE FSTYPE OPTIONS > /sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,mode=755 > ├─/sys/fs/cgroup/unified cgroup2 cgroup2 > rw,nosuid,nodev,noexec,relatime,nsdelegate > └─/sys/fs/cgroup/elogind cgroup cgroup > rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/elogind > > But I have to assume that these mount points where at least present > before I uninstalled cgroupfs-mount, too. > > Regards, Axel I can say I've always had this issue with only cgroup2 mounted and no cgroup (what you might call "v1")
Bug#921352: gmsh: breaks octave-msh autopkgtest
Source: gmsh
Version: 4.1.3+ds1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks
Hi Maintainer
The recent upload of gmsh 4.1.3+ds1-1 to unstable breaks the autopkgtest
of octave-msh 1.0.10-6 in testing with the following error:
[inst/msh2m_gmsh.m]
> /tmp/autopkgtest-lxc.pwwni_ng/downtmp/build.loD/src/inst/msh2m_gmsh.m
* test
fid = fopen("circle.geo","w");
fprintf(fid,"Point(1) = {0, 0, 0, 1};\n");
fprintf(fid,"Point(2) = {1, 0, 0, 1};\n");
fprintf(fid,"Point(3) = {-1, 0, 0, 1};\n");
fprintf(fid,"Circle(1) = {3, 1, 2};\n");
fprintf(fid,"Circle(2) = {2, 1, 3};\n");
fprintf(fid,"Line Loop(4) = {2, 1};\n");
fprintf(fid,"Plane Surface(4) = {4};");
fclose(fid);
mesh = msh2m_gmsh("circle","v",0);
system("rm circle.geo");
nnodest = length(unique(mesh.t));
nnodesp = columns(mesh.p);
assert(nnodest,nnodesp);
warning: tmpnam is obsolete and will be removed from a future version of
Octave, please use tempname instead
! test failed
load: unable to determine file format of '/tmp/oct-j8087D_p.txt'
Regards
Graham
[1] https://ci.debian.net/packages/o/octave-msh/testing/amd64/
Bug#909071: pbbam: FTBFS on every release architecture where it previously built (fwd)
Hi Adrian, On Mon, Feb 04, 2019 at 01:06:35PM +0200, Adrian Bunk wrote: > >Bug#916576: pbdagcon: FTBFS pbdata/Types.h: No such file or directory > > > > I need to make some noise in the team since I'm definitely overworked > > with these pb* packages. It might be that we will loose these for > > Buster. :-( > > the patches for pbbam and pbdagcon should sort out most of the issues. I've now uploaded the old upstream version of pbdagcon. Unfortunately I can not see that pbbam has fixed the build issues[1] - thus I think #909071 needs to be re-opened. Steve, since you suggested the patch - am I missing something? Kind regards Andreas. [1] https://buildd.debian.org/status/package.php?p=pbbam -- http://fam-tille.de
Bug#918830: marked as done (sardana: FTBFS with Sphinx 1.8: No module named pngmath)
Your message dated Mon, 04 Feb 2019 16:10:34 + with message-id and subject line Bug#918830: fixed in sardana 2.6.1+dfsg-1 has caused the Debian Bug report #918830, regarding sardana: FTBFS with Sphinx 1.8: No module named pngmath to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sardana Version: 2.2.2-3 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.8 Dear Maintainer, sardana fails to build with Sphinx 1.8, currently available in experimental: make[1]: Entering directory '/<>' PYTHONPATH=. sphinx-build -N -bhtml doc/source build/html # HTML generator Running Sphinx v1.8.3 Extension error: Could not import extension sphinx.ext.pngmath (exception: No module named pngmath) make[1]: *** [debian/rules:15: override_dh_sphinxdoc] Error 2 The pngmath extension was deprecated in Sphinx 1.4 and has been removed [1] in Sphinx 1.8. The recommended alternative is sphinx.ext.imgmath [2] which also has SVG support in addition to PNG. Upstream has already updated their conf.py file in [3]. [1]: https://github.com/sphinx-doc/sphinx/pull/4702 [2]: https://www.sphinx-doc.org/en/1.8/usage/extensions/math.html [3]: https://github.com/sardana-org/sardana/commit/5a532b161f86b5af -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: sardana Source-Version: 2.6.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of sardana, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carlos Pascual (supplier of updated sardana package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Feb 2019 15:47:31 +0100 Source: sardana Binary: python-sardana python-sardana-doc Architecture: source Version: 2.6.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Carlos Pascual Description: python-sardana - instrument control and data acquisition system - library python-sardana-doc - instrument control and data acquisition system - documentation Closes: 918830 Changes: sardana (2.6.1+dfsg-1) unstable; urgency=medium . * New upstream version 2.6.1 (closes: #918830 ) * Standards-Version bump to 4.3.0 (nothing to do) * Update upstream info in d/copyright * Make debian/watch file a dummy one * Drop existing quilt patch queue * Add patch to avoid privacy-breach lintian error * Fix various minor lintian errors * Enable Salsa-Pipeline for building and testing packages Checksums-Sha1: cbfa24e02ea45743a6a77efc3d938526e5a8ff59 2472 sardana_2.6.1+dfsg-1.dsc 822953cc323fb4b8f599b747ab9a76989a6cef4a 12358346 sardana_2.6.1+dfsg.orig.tar.gz 72e3cf114cde9b5c12f57b18de83ec2bd741fda3 10956 sardana_2.6.1+dfsg-1.debian.tar.xz Checksums-Sha256: 744dd717256a97d53b3b4be368d0c29c32366766747d12ff829ee9c7b672 2472 sardana_2.6.1+dfsg-1.dsc 233d01e15293de5846f38831d5c543030a030d489a332b88906e83baca6befa4 12358346 sardana_2.6.1+dfsg.orig.tar.gz d3fd472e98e16ed0de43d06ae6625545c62f75bb7d406a371289bdec8a8dbee3 10956 sardana_2.6.1+dfsg-1.debian.tar.xz Files: ea94d2f9b577308d3589649739cfa169 2472 science optional sardana_2.6.1+dfsg-1.dsc 294ada48ba40b54b6e2c1fa403954ef3 12358346 science optional sardana_2.6.1+dfsg.orig.tar.gz d15ce94709fc8241897e2cf7fc25797c 10956 science optional sardana_2.6.1+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE6S5+bp6dprGqMTncVjKQb0aW4BUFAlxYXjgRHHBpY2NhQGRl Ymlhbi5vcmcACgkQVjKQb0aW4BVuUA//ajjpz/ZpfRJ7MFa+SS+DLkq2ScB9Atvv oBkmymaA49A/fierCIs7uYSKqHinBfOtbaBAjkGdDba2Nny+7ZyRcC6seByNa6mV BM0L1tk11efRmNlkSiZznB4WH+IiYX6lGnszyOgtBTvMmoEqSvQv7OKJRWyxJYj2 zmY60qvFg4LXBuyhkS8Byd2VkvnN29Mo16OmcAWNiFw3gW+HJROB3jmNHdPVofzl yWkume2cWHzwgHWXsh4gCfVWvDnlccTutl2dJlJW24NeYbP/KV/XfzgbYeeXVFTs g5Jg8lWehKUJDMLVlpx7WWSYlIZSyapKQtjdoTAKMcXIVRNABbgUjt78aZ1AHQHx y/xCFXvfNzz+uG+DLJAOP/4W3r5NgJkwj7vewv+zcSorkwpF4i16Zb08stbjE/p9 z13Ng
Bug#918566: Lost of code copies of MurmurHash3 (Was: Bug#918566: mash FTBFS on big endian: test failures)
Hi Andreas, So I improved the upstream libmurmurhash, adapted the package and filed an ITP (#921353). I even managed to locally build mash against the new package. So hereby I kindly ask you to fix the last lintian issue about NMU which I don't fully understand and then maybe sponsor an upload. Best Fabian
Bug#921355: libpng1.6: CVE-2019-7317: use-after-free in png_image_free in png.c
Source: libpng1.6 Version: 1.6.36-3 Severity: grave Tags: security upstream Forwarded: https://github.com/glennrp/libpng/issues/275 Control: found -1 1.6.28-1 Control: found -1 1.6.36-2 Hi, The following vulnerability was published for libpng1.6. CVE-2019-7317[0]: | png_image_free in png.c in libpng 1.6.36 has a use-after-free because | png_image_free_function is called under png_safe_execute. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-7317 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7317 [1] https://github.com/glennrp/libpng/issues/275 Regards, Salvatore
Processed: libpng1.6: CVE-2019-7317: use-after-free in png_image_free in png.c
Processing control commands: > found -1 1.6.28-1 Bug #921355 [src:libpng1.6] libpng1.6: CVE-2019-7317: use-after-free in png_image_free in png.c Marked as found in versions libpng1.6/1.6.28-1. > found -1 1.6.36-2 Bug #921355 [src:libpng1.6] libpng1.6: CVE-2019-7317: use-after-free in png_image_free in png.c Marked as found in versions libpng1.6/1.6.36-2. -- 921355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921356: Not suitable for buster, package probably unmaintained
Package: node-tinycolor Version: 0.0.1~git20130725-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-tinycolor depends on: ii nodejs 4.8.2~dfsg-1 node-tinycolor recommends no packages. node-tinycolor suggests no packages.
Bug#921359: Not suitable for buster, package probably unmaintained
Package: node-security Version: 1.0.0~git20130515-2 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-security depends on: ii nodejs 4.8.2~dfsg-1 node-security recommends no packages. node-security suggests no packages.
Bug#921362: Not suitable for buster, package unmaintained
Source: bignumber.js Version: 1.3.0+dfsg-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921358: Not suitable for buster, package probably unmaintained
Package: node-yajsml Version: 1.1.5-2 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-yajsml depends on: ii nodejs 4.8.2~dfsg-1 node-yajsml recommends no packages. Versions of packages node-yajsml suggests: ii libjs-jquery 3.1.1-2 ii libjs-underscore 1.8.3~dfsg-1 -- no debconf information
Bug#921361: Not suitable for buster, package probably unmaintained
Source: node-clean-css Version: 1.0.12-2 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921360: No suitable for buster, package probably unmaintained
Package: node-base64id Version: 0.1.0-3 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-base64id depends on: ii nodejs 4.8.2~dfsg-1 node-base64id recommends no packages. node-base64id suggests no packages. -- no debconf information
Bug#921357: Not suitable for buster, package probably unmaintained
Package: node-dequeue Version: 1.0.5-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-dequeue depends on: ii nodejs 4.8.2~dfsg-1 node-dequeue recommends no packages. node-dequeue suggests no packages. -- no debconf information
Bug#921363: Not suitable for buster, package unmaintained
Source: ejs.js Version: 1.0.0+dfsg1-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921368: Not suitable for buster, package probably unmaintained
Package: node-base64id Version: 0.1.0-3 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-base64id depends on: ii nodejs 4.8.2~dfsg-1 node-base64id recommends no packages. node-base64id suggests no packages. -- no debconf information
Bug#921364: Not suitable for buster, package unmaintained
Package: node-active-x-obfuscator Version: 0.0.2-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-active-x-obfuscator depends on: pn node-zeparser ii nodejs 4.8.2~dfsg-1 node-active-x-obfuscator recommends no packages. node-active-x-obfuscator suggests no packages.
Bug#921366: Not suitable for buster, package probably unmaintained
Source: zeparser.js Version: 0.0.7+dfsg-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921365: Not suitable for buster, package probably unmaintained
Package: node-async-stacktrace Version: 0.0.2-2 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-async-stacktrace depends on: ii nodejs 4.8.2~dfsg-1 node-async-stacktrace recommends no packages. node-async-stacktrace suggests no packages. -- no debconf information
Bug#921369: Not suitable for buster, package probably unmaintained
Package: node-xmlhttprequest Version: 1.6.0-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-xmlhttprequest depends on: ii nodejs 4.8.2~dfsg-1 node-xmlhttprequest recommends no packages. node-xmlhttprequest suggests no packages. -- no debconf information
Bug#921367: Not suitable for buster, package probably unmaintained
Source: unorm.js Version: 1.0.5-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921370: Not suitable for buster, package probably unmaintained
Source: yamm3 Version: 1.1.0+dfsg1-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#921371: Not suitable for buster, package probably unmaintained
Package: node-log4js Version: 0.6.18-1 Severity: serious Dear all, In 2016/12 I removed my name from this package's Uploaders: field. It hasn't been touch sinced then and seems unmaintained. Due to this, the package might not be suitable for the Debian buster release. This needs to be checked by someone with more involvement in Javascript packaging than me. Thanks! light+love, Mike -- System Information: Debian Release: 9.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages node-log4js depends on: ii node-async 0.8.0-1 ii nodejs 4.8.2~dfsg-1 node-log4js recommends no packages. node-log4js suggests no packages. -- no debconf information
