Bug#935686: RM: python-translitcodec -- RoM; no Python 3 support and no reverse deps; low popcon
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal The current upstream code claims to support Python 3. Popcon is 14. Reverse deps checked with dak rm -Rnb python-translitcodec -- WBR, wRAR signature.asc Description: PGP signature
Bug#935450: Please port to Python 3 or remove
Package: src:thumbor Version: 6.7.0-1 Severity: important User: debian-pyt...@lists.debian.org Usertag: py2removal py2leaf py3noport py2rm As we are trying to remove Python 2 from unstable, and this package is a leaf package with popcon of 1 and many Python 2 deps/build-deps, it will be removed in a not very distant future (assuming the B-D on python-celery is fixed) unless it's ported to Python 3, which, according to https://github.com/thumbor/thumbor/issues/1004 , didn't happen yet. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#935449: Build-Depends on removed python-celery
Package: src:thumbor Version: 6.7.0-1 Severity: serious python-celery was recently removed and so this package cannot be built anymore. I don't see why that B-D is needed though. -- WBR, wRAR signature.asc Description: PGP signature
Bug#935447: Please drop the Python 2 subpackage
Package: src:python-raven Version: 6.3.0-2 Severity: serious User: debian-pyt...@lists.debian.org Usertag: py2removal py2leaf py3available python-celery was recently removed so python-raven can't be installed and the package can't be built. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#935446: RM: flower -- RoQA; orphaned; RC-buggy; low popcon; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal The package is Python 2 only and depends on celery which is Python 3 only. It also depends on libjs-twitter-bootstrap which will be removed too (#908424). The upstream code supports Python 3. Reverse deps checked with dak rm -Rnb python-flower -- WBR, wRAR signature.asc Description: PGP signature
Bug#935438: Please update to Python 3 or remove
Package: src:chaussette Version: 1.3.0-1 Severity: serious User: debian-pyt...@lists.debian.org Usertag: py2removal py2leaf py2rm According to #855671 this package doesn't seem to be working for the last 2.5 years, has popcon of 3, doesn't have Python 3 support and depends on a lot of Python 2 module packages, so it will most likely be removed from Debian in some not very distant future unless it's fixed and switched to Python 3.
Bug#935380: Please drop the Python 2 subpackage
Package: src:pyramid-jinja2 Version: 2.7+dfsg-1 Severity: important User: debian-pyt...@lists.debian.org Usertag: py2removal py2leaf py3available As a part of removing Python 2 from unstable we would like to remove python- pyramid, and python-pyramid-jinja2 blocks that. Please drop the Python 2 subpackage when possible.
Bug#935381: Please drop the Python 2 subpackage
Package: src:python-pyramid-multiauth Version: 0.8.0-1 Severity: important User: debian-pyt...@lists.debian.org Usertag: py2removal py2leaf py3available As a part of removing Python 2 from unstable we would like to remove python- pyramid, and python-pyramid-multiauth blocks that. Please drop the Python 2 subpackage when possible.
Bug#782951: Please provide a python3 module
Control: user -1 debian-pyt...@lists.debian.org Control: usertag -1 + py2removal py2leaf py3available Control: retitle -1 Please replace with a python3 module or remove the package Control: severity -1 important As a part of removing Python 2 from unstable we would like to remove python-pyramid, and python-pyramid-tm and python-pyramid-zcml block that. If it's possible please repackage them as Python 3 modules or remove them. Thank you. -- WBR, wRAR signature.asc Description: PGP signature
Bug#935335: Depends on removed python-zbar
Package: src:monkeysign Version: 2.2.4 Severity: serious As Python 2 versions of zbar and zbarpygtk were removed, this package should be updated to use Python 3 or removed. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#935331: RM: libavg -- RoQA; orphaned; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal I couldn't find if the upstream source supports Python 3. Reverse deps checked with dak rm -Rnb python-libavg -- WBR, wRAR signature.asc Description: PGP signature
Bug#935322: ITP: pytest-twisted -- Twisted plugin for py.test
Package: wnpp Severity: wishlist Owner: Andrey Rahmatullin * Package name: pytest-twisted Version : 1.11 Upstream Author : Kyle Altendorf et al. * URL : https://github.com/pytest-dev/pytest-twisted * License : BSD-3 Programming Lang: Python Description : Twisted plugin for py.test pytest-twisted is a plugin for pytest, which allows to test code, which uses the twisted framework. This will be used by future python-scrapy tests.
Bug#908819: Please package new upstream version
Control: tags -1 + pending On Fri, Sep 14, 2018 at 02:30:11PM +0200, Enrico Zini wrote: > The current version in Debian seems to be two major releases behind > upstream. Could you please package a newer version? I've done the update, it waits for when sybil passes NEW. -- WBR, wRAR signature.asc Description: PGP signature
Bug#935131: RM: xpyb -- RoQA; orphaned; RC-buggy; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal No upstream releases since the last packaged one in 2012. python3-xcffib description says "This package is intended to be a (mostly) drop-in replacement for xpyb. xpyb has an inactive upstream, several memory leaks, is python2 only and doesn't have pypy support." Reverse deps checked with dak rm -Rnb python-xpyb -- WBR, wRAR signature.asc Description: PGP signature
Bug#935129: RM: python-uniconvertor -- RoQA; orphaned; RC-buggy; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal Looks like it doesn't work at all in the current state. Reverse deps checked with dak rm -Rn python-uniconvertor -- WBR, wRAR signature.asc Description: PGP signature
Bug#935130: RM: pyvtk -- RoQA; orphaned; ancient; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal The latest upstream code at https://github.com/pearu/pyvtk seems to support Python 3, but the Debian package contains code from 2007. Reverse deps checked with dak rm -Rnb python-pyvtk -- WBR, wRAR signature.asc Description: PGP signature
Bug#935125: RM: pyexcelerator -- RoQA; orphaned; ancient; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal Last release in 2009. Reverse deps checked with dak rm -Rnb python-excelerator -- WBR, wRAR signature.asc Description: PGP signature
Bug#935122: RM: optcomplete -- RoQA; orphaned; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal Upstream Python 3 bugreport: https://bitbucket.org/blais/optcomplete/issues/2/python3-compatibility Reverse deps checked with dak rm -Rnb python-optcomplete -- WBR, wRAR signature.asc Description: PGP signature
Bug#935124: RM: pyao -- RoQA; orphaned; ancient; dead upstream; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal There is some Py3 fork at https://github.com/tynn/PyAO Reverse deps checked with dak rm -Rn pyao -- WBR, wRAR signature.asc Description: PGP signature
Bug#935123: RM: m2ext -- RoQA; orphaned; ancient; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal Last upstream commit in 2012. Reverse deps checked with dak rm -Rnb python-m2ext -- WBR, wRAR signature.asc Description: PGP signature
Bug#935120: RM: jabber.py -- RoQA; orphaned; ancient; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal Last release in 2003. Reverse deps checked with dak rm -Rnb python-jabber -- WBR, wRAR signature.asc Description: PGP signature
Bug#915895: python-limits FTBFS: ERROR: Failure: ImportError (cannot import name b)
Control: reassign -1 src:redis-py-cluster/1.3.3-1 Control: severity -1 grave Control: forwarded -1 https://github.com/Grokzen/redis-py-cluster/issues/295 Control: affects -1 src:python-limits On Sat, Feb 09, 2019 at 06:57:54PM +0100, Slavko wrote: > while this of course affects the python-limits build, it is not its > bug. As one can see, it is caused in test by importing rediscluster: Exactly. Fixing the bug metadata accordingly. Work in progress is at https://github.com/Grokzen/redis-py-cluster/pull/296 and looks promising. -- WBR, wRAR signature.asc Description: PGP signature
Bug#934832: RM: pygpiv -- RoQA; orphaned; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal User: debian-pyt...@lists.debian.org Usertag: py2removal No upstream releases since 2009. Reverse deps checked with dak rm -Rnb python-gpiv -- WBR, wRAR signature.asc Description: PGP signature
Bug#934831: RM: pylibssh2 -- RoQA; orphaned; dead upstream; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal Last upstream release in 2011, http://www.wallix.org/pylibssh2-project/ doesn't work. Reverse deps checked with dak rm -Rnb python-libssh2
Bug#934637: RM: python-django-shorturls -- RoQA; orphaned; outdated; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal Latest upstream source supports Python 3. Reverse deps checked by dak rm -Rnb python-django-shorturls
Bug#934407: RM: elixir -- ROM; no Python 3 support and no reverse deps
Control: tags -1 - moreinfo On Sun, Aug 11, 2019 at 02:08:11AM -0400, Scott Kitterman wrote: > > Reverse deps checked by dak rm -Rnb python-elixir > > I guess that doesn't catch build-depends: It does, but... > Checking reverse dependencies... > # Broken Build-Depends: > rabbitmq-server: elixir (>= 1.6.6) The source package is elixir, the binary package is python-elixir. Here the binary package is elixir, its source package is elixir-lang. -- WBR, wRAR signature.asc Description: PGP signature
Bug#934447: RM: ricky -- ROM; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal Development stopped 5 years ago. Reverse deps checked by dak rm -Rnb python-ricky
Bug#934431: RM: pyprotocols -- RoQA; orphaned; ancient; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal The code is from 2007. Reverse deps checked by dak rm -Rnb python-protocols
Bug#934430: RM: pyflot -- ROM; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal Project is old and dead. Reverse deps checked by dak rm -Rnb python-pyflot
Bug#934429: RM: pycaptcha -- ROM; RC-buggy; very old; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal There is only one release of this software, in 2006. Reverse deps checked by dak rm -Rnb python-captcha
Bug#934427: RM: pychef -- RoQA; orphaned; RC-buggy; no Python 3 subpackage and no reverse deps
Package: ftp.debian.org Severity: normal The upstream code is old but seems to support Python 3. Reverse deps checked by dak rm -Rnb python-chef
Bug#934425: RM: pmock -- ROM; dead upstream; effectively orphaned; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal Reverse deps checked by dak rm -Rnb python-pmock
Bug#934414: RM: pastewebkit -- ROM; obsolete; dead upstream; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal Related to the obsolete Pylons stack. Reverse deps checked by dak rm -Rnb python-pastewebkit
Bug#934412: RM: myghtyutils -- ROM; orphaned; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal Related to the obsolete Pylons stack. Reverse deps checked by dak rm -Rnb python-myghtyutils
Bug#934411: RM: louie -- RoQA; orphaned; dead upstream; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal No upstream releases after the Debian upload. https://11craft.github.io/louie/ is 404 Reverse deps checked by dak rm -Rnb python-louie
Bug#934410: RM: loofah -- ROM; RC-buggy; requires mongodb; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal Reverse deps checked by dak rm -Rnb python-loofah
Bug#934407: RM: elixir -- ROM; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal The latest upstream code at https://github.com/Didacti/elixir seems to support Python 3. Reverse deps checked by dak rm -Rnb python-elixir
Bug#934403: RM: cf-python -- ROM; outdated; RC-buggy; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal The Debian package is old, the current upstream code at https://cfpython.bitbucket.io seems to support Python 3. Reverse deps checked by dak rm -Rn cf-python
Bug#934401: RM: bunch -- ROM; orphaned; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal There is some support for Python 3 but the upstream code is 8 years old. Reverse deps checked by dak rm -Rnb python-bunch
Bug#934402: RM: creoleparser -- ROM; dead upstream; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal https://creoleparser.googlepages.com/ is dead. Current upstream release was uploaded in 2012. Reverse deps checked by dak rm -Rnb python-creoleparser
Bug#934400: RM: breadability -- ROM; mostly dead upstream; no Python 3 subpackage and no reverse deps
Package: ftp.debian.org Severity: normal "I'm not even sure if this code is currently Python 3 compatible.": https://github.com/bookieio/breadability/issues/36 Reverse deps checked by dak rm -Rnb python-breadability
Bug#934399: RM: bjsonrpc -- ROM; no Python 3 subpackage and no reverse deps
Package: ftp.debian.org Severity: normal The latest upstream code, 4 years old, claims to support Python 3. Reverse deps checked by dak rm -Rnb python-bjsonrpc
Bug#934398: RM: beanstalkc -- ROM; no Python 3 subpackage and no reverse deps
Package: ftp.debian.org Severity: normal The code seems to support Python 3 but there is no subpackage. Reverse deps checked by dak rm -Rnb python-beanstalkc
Bug#934396: RM: argvalidate -- ROM; dead upstream; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal http://code.sp-its.at/projects/argvalidate is dead, PyPI has the same 10 year old release as we have. Reverse deps checked by dak rm -Rnb python-argvalidate
Bug#934392: RM: pyres -- ROM; NPOASR; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal The source supports Python 3 but there is no subpackage. The upstream development stopped in 2015. There is one reverse dep, python-remotecv, its RM bug is #934391 Reverse deps checked by dak rm -Rn remotecv pyres
Bug#934391: RM: remotecv -- ROM; NPOASR; no Python 3 support and no reverese deps
Package: ftp.debian.org Severity: normal Unclear if the source supports Python 3 but there is no Python 3 subpackage. Reverse deps checked with dak rm -Rnb python-remotecv
Bug#934362: RM: trollius-redis -- ROM; no Python 3 subpackage and no reverse deps
Package: ftp.debian.org Severity: normal The code claims to support Python 3 but there is no subpackage. Reverse deps checked by dak rm -Rnb python-trollius-redis
Bug#934361: RM: pyxmpp -- ROM; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal The upstream has only one commit after 2011 and obviously no Python 3 support. Reverse deps checked by dak rm -Rn pyxmpp
Bug#934355: RM: pywbem -- ROM; outdated; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal The latest upstream release supports py3, I didn't check the version in Debian which is very old. Reverse deps checked by dak rm -Rnb python-pywbem
Bug#934352: RM: gnukhata-core -- ROM; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal The package description says * This package is Python2 as was gnukhata-core-engine. Upstream has no plan to make a Python3 version, but we intend to raise the question and we hope a Python3 release will appear before the end of life of Python2 in Debian. In the meantime, it's better to have an up-to-date release of gnukhata-core. I don't see any upstream discussions on this. Removing gnukhata-core unblocks removal of at least python-natsort and 6 Pyramid-related packages.
Bug#926543: lintian: Deadlock in source-copyright check on source:khronos-opencl-man/1.0~svn33624-4
On Fri, Aug 09, 2019 at 08:37:48AM -0700, Felix Lechner wrote: > > It's the same with lintian from sid (2.16.0) on xhtml2pdf 0.2.2-2 and > > 0.2.2-3. > I do not see any issues terminating locally. I used both Lintian > master and 2.16.0 on the xhtml2pdf source packages, per below. I also > tried, locally, the more complex command from above on > khronos-opencl-man_1.0~svn33624-4.dsc. Attached please find the log > showing that success, as well. > > Can your errors be reproduced locally, or are they limited to lindsay? I tried xhtml2pdf only locally. -- WBR, wRAR signature.asc Description: PGP signature
Bug#926543: lintian: Deadlock in source-copyright check on source:khronos-opencl-man/1.0~svn33624-4
It's the same with lintian from sid (2.16.0) on xhtml2pdf 0.2.2-2 and 0.2.2-3. -- WBR, wRAR signature.asc Description: PGP signature
Bug#934305: Drop Pylons support
Package: src:turbogears2 Version: 2.3.12+really2.3.7-1 Severity: important While we are working on dropping Python 2, and there is already #880154 that asks about providing Python 3 support, dropping Pylons is a separate task and it will help with dropping a bunch of obsolete Python 2-only packages, so please drop the Pylons support from this package. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-trunk-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#934296: RM: fookebox -- RoQA; orphaned; uses obsolete libs
Package: ftp.debian.org Severity: normal This package is the only package in the archive using the Pylons library which is Py2-only and will be removed. It is orphaned and no upstream development happened since 2015.
Bug#934263: RM: pyrrd -- ROM; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal No upstream activity at https://launchpad.net/pyrrd since the last package upload. No Python 3 support. RFH #876679. Reverse deps checked by dak rm -Rnb python-pyrrd
Bug#934262: RM: pylogsparser -- RoQA; orphaned; dead upstream; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal http://www.wallix.org/pylogsparser-project/ is dead. https://pypi.org/project/pylogsparser/ has a newer version than in the package but still 7 years old. Reverse deps checked by dak rm -Rnb python-logsparser
Bug#934260: RM: pykickstart -- ROM; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal The package is 5 years old, the new version at https://github.com/dcantrell/pykickstart supports Python 3. Reverse deps checked by dak rm -Rnb python-pykickstart
Bug#934259: RM: epsilon -- ROM; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal No Python 3 support even in the new upstream at https://github.com/twisted/epsilon The only reverse dep is python-axiom, whose RM bug is #934176. Reverse deps checked by dak rm -Rnb python-epsilon
Bug#934257: RM: python-shogun -- RoQA; orphaned; no Python 3 subpackage and no reverse deps
Package: ftp.debian.org Severity: normal Source seems to support Python 3 in some form but this is not used in the package, some related packaging parts exist but are commented out. The version in Debian is 5 years old, the upstream is active. It also depends on shogun which is currently orphaned and RC-buggy too, but that RC bug looks like it will be fixed soon. Reverse deps checked by dak rm -Rnb python-shogun. There is one reverse Recommends, from python-mvpa2. It is Python 2-only itself, RC-buggy and without reverse deps (but not under DPMT so I'm not touching it).
Bug#934255: RM: python-jsonrpc2 -- ROM; dead upstream; no Python 3 subpackage and no reverse deps
Package: ftp.debian.org Severity: normal Source claims to support Python 3.4 but there is no Python 3 subpackage. https://github.com/aodag/jsonrpc2 has no updates since the packaged version (5 years ago). Reverse deps checked by dak rm -Rnb python-jsonrpc2
Bug#934176: RM: python-axiom -- ROM; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal Upstream Python 3 support is only proposed: https://github.com/twisted/axiom/issues/106 Reverse deps checked by dak rm -Rnb python-axiom
Bug#934175: RM: moksha.hub -- ROM; dead upstream; no Python 2 support and no reverse deps
Package: ftp.debian.org Severity: normal The source doesn't support Python 2, http://mokshaproject.net/ redirects to https://reactdom.com/graphql and I couldn't find a new upstream location. Reverse deps checked with dak rm -Rnb python-moksha.hub
Bug#933983: RM: storm/0.19-2 -- RoQA; orphaned; no Py3 and no revdeps
On Mon, Aug 05, 2019 at 07:39:54PM +0100, Adam D. Barratt wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: rm > > > > Orphaned, doesn't support Python 2, doesn't have revdeps (checked > > with `dak rm > > -Rn storm`). > > > > No Py3 support upstream either: https://bugs.launchpad.net/storm/+bug > > /1530734 > > From which suite? From unstable please. -- WBR, wRAR signature.asc Description: PGP signature
Bug#933984: RM: pyramid-beaker/0.6.1+ds1-1 -- RoM; no Py3 and no revdeps
Removal from unstable. -- WBR, wRAR signature.asc Description: PGP signature
Bug#933984: RM: pyramid-beaker/0.6.1+ds1-1 -- RoM; no Py3 and no revdeps
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm No Python 3 support. No revdeps (checked with dak rm -Rn pyramid-beaker). Newer upstream versions declare Python 3.2 compatibility. Last release in 2013.
Bug#933983: RM: storm/0.19-2 -- RoQA; orphaned; no Py2 and no revdeps
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Orphaned, doesn't support Python 2, doesn't have revdeps (checked with `dak rm -Rn storm`). No Py3 support upstream either: https://bugs.launchpad.net/storm/+bug/1530734
Bug#933723: Make APT::Keep-Downloaded-Packages configurable
On Mon, Aug 05, 2019 at 11:22:50AM +0200, Johannes Schauer wrote: > Control: tag -1 + newcomer > > Hi, > > Quoting Andrey Rahmatullin (2019-08-02 15:14:23) > > Currently sbuild sets APT::Keep-Downloaded-Packages to false and it doesn't > > look configurable. If sbuild is used with a persistent package cache (e.g. > > bind-mounting the host one) this setting should be set to true to skip > > downloading the same packages on each build. > > I guess an entry for your ~/.sbuildrc would be sufficient and you don't need > this as a command line argument? Definitely. -- WBR, wRAR signature.asc Description: PGP signature
Bug#915219: ITP: python-sybil -- Automated testing for the examples in your documentation
Control: owner -1 ! As agreed on IRC, I'll work on this ITP. I'm almost finished already. -- WBR, wRAR signature.asc Description: PGP signature
Bug#933723: Make APT::Keep-Downloaded-Packages configurable
Package: sbuild Version: 0.78.1-2 Severity: wishlist Currently sbuild sets APT::Keep-Downloaded-Packages to false and it doesn't look configurable. If sbuild is used with a persistent package cache (e.g. bind-mounting the host one) this setting should be set to true to skip downloading the same packages on each build. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-trunk-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sbuild depends on: ii adduser 3.118 ii libsbuild-perl 0.78.1-2 ii perl5.28.1-6 Versions of packages sbuild recommends: ii autopkgtest 5.10 ii debootstrap 1.0.115 ii schroot 1.6.10-6+b1 Versions of packages sbuild suggests: ii deborphan 1.7.31 ii e2fsprogs 1.45.3-3 ii kmod 26-1 ii wget 1.20.3-1 -- no debconf information
Bug#932618: transition: librsync
On Wed, Jul 31, 2019 at 12:35:56PM +, Holger Levsen wrote: > > > > > src:librsync is currently still to be removed from bullseye on August > > > > > 9th, because #776246 was only fixed in experimental... > > > > In experimental and unstable. > > > > > > not according to the bts which only knows 1.0.0-1~exp1 as fixed which is > > > not (and never was) in unstable. > > That's not what I see: the default picture doesn't show even 1.0.0-1~exp1 > > while the "Don't ignore boring" one shows the version in sid as fixed (I > > don't know why it is not marked "unstable" though). > > ignore the fancy picture and look at the words on > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776246 > > Found in versions librsync/0.9.7-10, librsync/0.9.7-1 > Fixed in version 1.0.0-1~exp1 Those are just user-set headers. BTS reads changelogs to infer fixed/not fixed status for versions. Oh, and BTS doesn't show the fixed version on the picture because only librsync1 is affected, not librsync2. I'm still not sure why are you writing this, and why are you writing it in the transition bug. -- WBR, wRAR signature.asc Description: PGP signature
Bug#932618: transition: librsync
On Wed, Jul 31, 2019 at 11:28:46AM +, Holger Levsen wrote: > > > src:librsync is currently still to be removed from bullseye on August > > > 9th, because #776246 was only fixed in experimental... > > In experimental and unstable. > > not according to the bts which only knows 1.0.0-1~exp1 as fixed which is > not (and never was) in unstable. That's not what I see: the default picture doesn't show even 1.0.0-1~exp1 while the "Don't ignore boring" one shows the version in sid as fixed (I don't know why it is not marked "unstable" though). -- WBR, wRAR signature.asc Description: PGP signature
Bug#932618: transition: librsync
On Wed, Jul 31, 2019 at 02:06:50AM +, Holger Levsen wrote: > > Turns out I had some extra time for this flying back from DebConf and it > > needed changes to only one file for this, so new rdiff-backup with > > librsync2 was uploaded yesterday... > > src:librsync is currently still to be removed from bullseye on August > 9th, because #776246 was only fixed in experimental... In experimental and unstable. -- WBR, wRAR signature.asc Description: PGP signature
Bug#932618: transition: librsync
librsync2 is available in unstable, please binNMU burp, csync2 and duplicity. From https://lists.debian.org/debian-python/2019/07/msg00093.html I guess Otto (Cced) is interested in keeping rdiff-backup? In that case, Otto, please prepare an upload with a fix. -- WBR, wRAR signature.asc Description: PGP signature
Bug#932618: transition: librsync
On Mon, Jul 29, 2019 at 10:36:57AM +0200, Otto Kekäläinen wrote: > > librsync2 is available in unstable, please binNMU burp, csync2 and > > duplicity. > > > > From https://lists.debian.org/debian-python/2019/07/msg00093.html I guess > > Otto (Cced) is interested in keeping rdiff-backup? In that case, Otto, > > please prepare an upload with a fix. > > Yes, I am working on it. I need to get both the library bumped and > whole code base from Python 2 to Python 3. It will take some weeks.. Do you think the python3 change is necessary right now? -- WBR, wRAR signature.asc Description: PGP signature
Bug#932795: Ethics of FTBFS bug reporting
On Tue, Jul 23, 2019 at 01:54:10PM +0200, Santiago Vila wrote: > * Because this is a violation of a Policy "must" directive, I consider > the downgrade to be a tricky way to modify Debian Policy without > following the usual Policy decision-making procedure. Please also note that https://release.debian.org/bullseye/rc_policy.txt defines bug severities, not the Policy directly. For example, while the Policy says that a package in main "must not require or recommend a package outside of main", the RC policy says ""Recommends:" lines do not count". > Surely, the end user *must* be able to build the package as well, must > they not? I also guess it's not the only case when the buildd infra does things differently, the best known example is ignoring B-D alternatives. -- WBR, wRAR signature.asc Description: PGP signature
Bug#932618: transition: librsync
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition The librsync library changed the ABI and also some parts of API, the API change impacts only rdiff-backup, for which #928885 is filed with no reaction so far. I've tested all revdeps, they rebuild cleanly apart from rdiff-backup. https://release.debian.org/transitions/html/auto-librsync.html looks correct. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-trunk-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#928885: FTBFS with librsync 2
Control: severity -1 serious Control: block 776246 by -1 As the buster is released I'm bumping the severity. -- WBR, wRAR signature.asc Description: PGP signature
Bug#776246: MD4 collision/preimage attacks (CVE-2014-8242)
On Wed, Jul 10, 2019 at 11:45:53AM +0200, Laurent Bigonville wrote: > Now that buster has been released, do you think we could move forward with > uploading the last version of librsync in unstable? Yes, I plan to proceed with this soon. > I tried to rebuild duplicity and it's building fine. I tried rebuilding all revdeps some time ago, only rdiff-backup failed. -- WBR, wRAR signature.asc Description: PGP signature
Bug#930539: [Pkg-utopia-maintainers] Bug#930539: upowerd cannot start due to searching the wrong libssl version
On Tue, Jul 02, 2019 at 11:50:00PM +0200, Andreas von Heydwolff wrote: > On 02.07.19 07:20, Andrey Rahmatullin wrote: > > Doing anything with libimobiledevice4 packages won't touch your locally > > installed bad library. You should remove it, and any other locally > > installed libraries, and never do such installs again, at least while you > > don't fully understand the consequences. > > Agreed, although I am not sure what bad library means in this context. A library linked with libssl you don't have. > I did not compile anything from source Then why you have binaries in /usr/local? -- WBR, wRAR signature.asc Description: PGP signature
Bug#930539: [Pkg-utopia-maintainers] Bug#930539: upowerd cannot start due to searching the wrong libssl version
Doing anything with libimobiledevice4 packages won't touch your locally installed bad library. You should remove it, and any other locally installed libraries, and never do such installs again, at least while you don't fully understand the consequences. -- WBR, wRAR signature.asc Description: PGP signature
Bug#930539: upowerd cannot start due to searching the wrong libssl version
On Fri, Jun 14, 2019 at 10:16:50PM +0200, A. Heydwolff wrote: > Jun 14 21:10:58 karfiol upowerd[15367]: /usr/lib/upower/upowerd: error while > loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No > such file or directory Note that /usr/lib/upower/upowerd isn't linked to libssl directly, and, at least in sid, not even indirectly. This means there is some problem with one of the libraries it loads and, I suspect, it's a library installed locally. You can start debugging this with ldd (or just looking into /usr/local). > Installed are > -rw-r--r-- 1 root root 349K Oct 7 2017 libssl3.so > -rw-r--r-- 1 root root 422K Feb 27 21:58 libssl.so.1.0.2 > -rw-r--r-- 1 root root 576K Apr 16 21:31 libssl.so.1.1 > > I created a 1.0.0 symlink to 1.0.2 Never do this. -- WBR, wRAR signature.asc Description: PGP signature
Bug#928885: FTBFS with librsync 2
Package: src:rdiff-backup Version: 1.2.8-7 Severity: normal Tags: upstream We plan upgrading librsync to 2.0.2 after the buster release, see #776246. This version is not API-compatible with 0.9.7 but it seems the only package that breaks is rdiff-backup: x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix- map=/build/python2.7-IbFBHb/python2.7-2.7.16=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c _librsyncmodule.c -o build/temp.linux-x86_64-2.7/_librsyncmodule.o _librsyncmodule.c: In function ‘_librsync_new_sigmaker’: _librsyncmodule.c:63:17: error: ‘RS_DEFAULT_STRONG_LEN’ undeclared (first use in this function); did you mean ‘RS_DEFAULT_BLOCK_LEN’? (size_t)RS_DEFAULT_STRONG_LEN); ^ RS_DEFAULT_BLOCK_LEN _librsyncmodule.c:63:17: note: each undeclared identifier is reported only once for each function it appears in _librsyncmodule.c:62:17: error: too few arguments to function ‘rs_sig_begin’ sm->sig_job = rs_sig_begin((size_t)blocklen, ^~~~ In file included from _librsyncmodule.c:25: /usr/include/librsync.h:397:11: note: declared here rs_job_t *rs_sig_begin(size_t new_block_len, size_t strong_sum_len, ^~~~ Please do something with this. New librsync is available in experimental. This bug report will be upgraded to RC once the freeze ends. -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-trunk-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#928518: RM: electrum -- RoQA; Actively exploited for phishing
On Mon, May 06, 2019 at 12:00:22PM -0400, Sam Hartman wrote: > Package: ftp.debian.org > Severity: normal > > Hi. As discussed in > https://cointelegraph.com/news/phishing-attack-on-electrum-wallet-nets-hacker-almost-1-million-in-hours-report > the version of electrum in sid is vulnerable to mallware and has been > disabled by the electrum servers. So basically the version in sid is > only useful for getting your bitcoin phished. At least until this > version is updated it should be removed. See #921688 for details. > > I understand that removing electrum means that it will need to take a > trip through new once fixed. > I think in this instance given that we haven't fixed such a critical issue in > months, it is justified. Note that it doesn't help with already installed packages. -- WBR, wRAR signature.asc Description: PGP signature
Bug#926915: RFS: fossology/3.5.0-1 [ITP] -- OSS license compliance tool
On Mon, Apr 15, 2019 at 06:40:41AM +, Mishra, Gaurav wrote: > FOSSology currently supports Debian Jessie and Stretch both. And Jessie still > have a year left to meet its end of life that is the reason we still support > it. And that is the reason php5-cli is still there. Please keep in the official packages only stuff needed by the official packages. You will need to maintain a separate changelog anyway. > And for Stretch, we have added the regex `php5-cli|php7.0-cli|php7.2-cli` in > the control file. It's not a regex. And only the first alternative is considered by the official buildds. -- WBR, wRAR signature.asc Description: PGP signature
Bug#926839: RFS: fossology/3.4.0-2 [ITP]
On Thu, Apr 11, 2019 at 08:16:06AM +, Mishra, Gaurav wrote: > > Changes since the last upload: > > * First release as a Debian package. > * Closes: bug#924659 If it's a first release it shouldn't have 2 as the Debian version. -- WBR, wRAR signature.asc Description: PGP signature
Bug#924848: telegram-cli: FTBFS: build-dependency not installable: libwolfssl-dev
libwolfssl was removed from testing due to #918952. The shared lib was removed but this package was not, because it doesn't depend on the lib. Maybe the B-D can be safely removed. -- WBR, wRAR signature.asc Description: PGP signature
Bug#926327: qgit: Crash on some malformed git repositories
Control: tags -1 + upstream Please forward it to https://github.com/tibirna/qgit/issues, ideally with instructions how to create such repo. -- WBR, wRAR signature.asc Description: PGP signature
Bug#924765: unblock: pygnuplot/0.11.16-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pygnuplot This fixes FTBFS #924341. diff -Nru pygnuplot-0.11.16/debian/changelog pygnuplot-0.11.16/debian/changelog --- pygnuplot-0.11.16/debian/changelog 2019-01-05 22:07:29.0 +0500 +++ pygnuplot-0.11.16/debian/changelog 2019-03-17 14:00:05.0 +0500 @@ -1,3 +1,10 @@ +pygnuplot (0.11.16-2) unstable; urgency=medium + + * Team upload. + * Fix the build dependency on debhelper (Closes: #924341). + + -- Andrey Rahmatullin Sun, 17 Mar 2019 14:00:05 +0500 + pygnuplot (0.11.16-1) unstable; urgency=medium * Initial release (Closes: #910437) diff -Nru pygnuplot-0.11.16/debian/control pygnuplot-0.11.16/debian/control --- pygnuplot-0.11.16/debian/control2019-01-05 22:07:29.0 +0500 +++ pygnuplot-0.11.16/debian/control2019-03-17 14:00:05.0 +0500 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian Python Modules Team Uploaders: Josue Ortega -Build-Depends: debhelper (= 12), +Build-Depends: debhelper (>= 12), dh-python, python3-all, python3-setuptools unblock pygnuplot/0.11.16-2
Bug#924329: xastir: FTBFS (magick/image-private.h: No such file or directory)
On Mon, Mar 11, 2019 at 05:09:58PM +, Santiago Vila wrote: > In file included from /usr/include/GraphicsMagick/magick/analyze.h:18, > from /usr/include/GraphicsMagick/magick/api.h:55, > from map_geo.c:137: > /usr/include/GraphicsMagick/magick/image.h:1108:10: fatal error: > magick/image-private.h: No such file or directory > #include "magick/image-private.h" > ^~~~ src/map_geo.c: """ #ifdef HAVE_GRAPHICSMAGICK /*#include */ /* Define MAGICK_IMPLEMENTATION to access private interfaces * such as DestroyImagePixels(). This may not be a good thing, * but DestroyImagePixels() has been in this code for a long * time. Defining MAGIC_IMPLEMENTATION eliminates the warning that is * now (9/28/2010) being seen on some distros (Ubuntu 10.04 and * OpenSuSE-11.3) */ #define MAGICK_IMPLEMENTATION #include """ Haha NOPE. -- WBR, wRAR signature.asc Description: PGP signature
Bug#924383: ruby-coveralls: FTBFS (dh_installman: Cannot find "debian/coveralls.1")
On Tue, Mar 12, 2019 at 09:43:22AM +, Santiago Vila wrote: > TZ=UTC ronn --roff debian/coveralls.mkd > roff: debian/coveralls.mkd.1 [...] > dh_installman: Cannot find (any matches for) "debian/coveralls.1" (tried in > ., debian/tmp) So a change in ronn, I guess. The package in sid wasn't built on buildds so nothing to compare with. -- WBR, wRAR signature.asc Description: PGP signature
Bug#923719: celery: FTBFS ("Download error", probably because of missing build-depends)
On Mon, Mar 04, 2019 at 11:16:02AM +, Santiago Vila wrote: > Searching for billiard<3.6.0,>=3.5.0.2 It's 3.6.0.0 in sid (was 3.5.0.4 when this package was uploaded). -- WBR, wRAR signature.asc Description: PGP signature
Bug#923529: giada: FTBFS (error: expected ')' before '*' token)
The code giving the errors is actually from juce-modules-source. The version used for building the current sid giada package is 5.3.2~repack-1, while the version in sid (which causes FTBFS) is 5.4.1+really5.4.1~repack-2. This seems to be related to #913915, I have no idea how can the current sid version work as some things in juce_VSTPluginFormat.cpp are not defined anywhere. -- WBR, wRAR signature.asc Description: PGP signature
Bug#923454: renderdoc: FTBFS (error: braces around scalar initializer for type 'int')
The problem here is the API compatibility break in glslang, described in https://github.com/KhronosGroup/glslang/issues/1538#issuecomment-431643795 Changes related to the new glslang version seem to be bundled in https://github.com/baldurk/renderdoc/commit/2ea6174c83c3c55f504c107303991d9bb2aa9af3 (I see 3 source files changed there). -- WBR, wRAR signature.asc Description: PGP signature
Bug#923466: lammps: FTBFS (dh_auto_configure fails)
The actual error message is """ CMake Error at CMakeLists.txt:298 (message): MPIIO package needs LAMMPS to be build with MPI Call Stack (most recent call first): CMakeLists.txt:304 (pkg_depends) """ It seems to mean MPI is not found. After removing QUIET from find_package(MPI): -- Found MPI_C: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so (found version "3.1") -- Found MPI_CXX: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so (found version "3.1") -- Could NOT find MPI_Fortran (missing: MPI_Fortran_WORKS) -- Could NOT find MPI (missing: MPI_Fortran_FOUND) (found version "3.1") CMake Error at CMakeLists.txt:298 (message): MPIIO package needs LAMMPS to be build with MPI Call Stack (most recent call first): CMakeLists.txt:304 (pkg_depends) The package B-D on fortran-compiler. The package is virtual, and we see here why is that considered a problem to B-D on a virtual package. Previously gfortran was installed during the build, now flang07 is installed. Yet mpif90 says "The Open MPI wrapper compiler was unable to find the specified compiler gfortran in your PATH." Install gfortran fixes this problem. -- WBR, wRAR signature.asc Description: PGP signature
Bug#923341: Doesn't depend on -dev it uses
Package: libradare2-dev Version: 3.2.1+dfsg-4 Severity: serious Control: block 923321 by -1 At least libuv and liblz4 are listed in Requires.private of the .pc files yet the -dev package doesn't depend on their -dev packages. This leads to pkg-config --cflags r_core failing. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Versions of packages libradare2-dev depends on: ii libcapstone-dev 4.0.1-3 ii libmagic-dev 1:5.35-2 ii libradare2-3.2 3.2.1+dfsg-4 libradare2-dev recommends no packages. libradare2-dev suggests no packages. -- WBR, wRAR signature.asc Description: PGP signature
Bug#923319: dynalogin: FTBFS (Makefile:366: pam_dynalogin_la-pam_dynalogin.lo)
On Tue, Feb 26, 2019 at 11:18:18AM +, Santiago Vila wrote:
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
> -DSYSCONFDIR='"/etc"' -I./../libdynaloginclient -Wdate-time
> -D_FORTIFY_SOURCE=2 -pthread -DLINUX -D_REENTRANT -D_GNU_SOURCE
> -I/usr/include/apr-1.0 -I/usr/include/liboath -c -o
> pam_dynalogin_la-pam_dynalogin.lo `test -f 'pam_dynalogin.c' || echo
> './'`pam_dynalogin.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/etc\"
> -I./../libdynaloginclient -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DLINUX
> -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -I/usr/include/liboath -c
> pam_dynalogin.c -fPIC -DPIC -o .libs/pam_dynalogin_la-pam_dynalogin.o
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\"/etc\"
> -I./../libdynaloginclient -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DLINUX
> -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-1.0 -I/usr/include/liboath -c
> pam_dynalogin.c -o pam_dynalogin_la-pam_dynalogin.o >/dev/null 2>&1
> make[3]: *** [Makefile:366: pam_dynalogin_la-pam_dynalogin.lo] Error 1
I have no idea why libtool seems to call gcc twice, the first time
correctly, the second time without -DPIC and suppressing the output, but
the second command fails with the following output:
"""
pam_dynalogin.c:327:8: error: variable ‘_pam_dynalogin_modstruct’ has
initializer but incomplete type
struct pam_module _pam_dynalogin_modstruct = {
^~
pam_dynalogin.c:328:3: warning: excess elements in struct initializer
"pam_dynalogin",
^~~
pam_dynalogin.c:328:3: note: (near initialization for
‘_pam_dynalogin_modstruct’)
pam_dynalogin.c:329:3: warning: excess elements in struct initializer
pam_sm_authenticate,
^~~
pam_dynalogin.c:329:3: note: (near initialization for
‘_pam_dynalogin_modstruct’)
pam_dynalogin.c:330:3: warning: excess elements in struct initializer
pam_sm_setcred,
^~
pam_dynalogin.c:330:3: note: (near initialization for
‘_pam_dynalogin_modstruct’)
pam_dynalogin.c:331:3: warning: excess elements in struct initializer
NULL,
^~~~
pam_dynalogin.c:331:3: note: (near initialization for
‘_pam_dynalogin_modstruct’)
pam_dynalogin.c:332:3: warning: excess elements in struct initializer
NULL,
^~~~
pam_dynalogin.c:332:3: note: (near initialization for
‘_pam_dynalogin_modstruct’)
pam_dynalogin.c:333:3: warning: excess elements in struct initializer
NULL,
^~~~
pam_dynalogin.c:333:3: note: (near initialization for
‘_pam_dynalogin_modstruct’)
pam_dynalogin.c:334:3: warning: excess elements in struct initializer
NULL
^~~~
pam_dynalogin.c:334:3: note: (near initialization for
‘_pam_dynalogin_modstruct’)
pam_dynalogin.c:327:19: error: storage size of ‘_pam_dynalogin_modstruct’ isn’t
known
struct pam_module _pam_dynalogin_modstruct = {
^~~~
"""
This seems to be a direct consequence of missing -DPIC (via #ifndef PIC
#define PAM_STATIC).
--
WBR, wRAR
signature.asc
Description: PGP signature
Bug#921762: need help
On Tue, Feb 26, 2019 at 05:23:13PM +0800, Yanhao Mo wrote: > Control: tags -1 + pending > > Andrey Rahmatullin writes: > > > Control: tags -1 + upstream fixed-upstream > > > > On Wed, Feb 13, 2019 at 09:21:17PM +0800, Yanhao Mo wrote: > >> Control: tags -1 + confirmed help > > This seems to be fixed upstream: > > https://github.com/teejee2008/timeshift/issues/375 > > I see, thanks for reminding, new version will soon be uploaded. Please mind the freeze policy. -- WBR, wRAR signature.asc Description: PGP signature
Bug#921762: need help
Control: tags -1 + upstream fixed-upstream On Wed, Feb 13, 2019 at 09:21:17PM +0800, Yanhao Mo wrote: > Control: tags -1 + confirmed help This seems to be fixed upstream: https://github.com/teejee2008/timeshift/issues/375 -- WBR, wRAR signature.asc Description: PGP signature
Bug#923011: nuxwdog: FTBFS (/usr/include/keyutils.h:204:48: error: expected ',' or '...' before 'private')
On Fri, Feb 22, 2019 at 10:53:47PM +, Santiago Vila wrote: > In file included from src/com/redhat/nuxwdog/wdpwd.cpp:37: > /usr/include/keyutils.h:204:48: error: expected ',' or '...' before 'private' > extern long keyctl_dh_compute_kdf(key_serial_t private, key_serial_t prime, > ^~~ https://bugzilla.redhat.com/show_bug.cgi?id=1629878 https://lkml.org/lkml/2018/8/28/1051 (linked from there) -- WBR, wRAR signature.asc Description: PGP signature
Bug#923049: tg.controllers.decoratedcontroller requires newer python-crank
Package: python-turbogears2 Version: 2.3.12-1 Severity: important Control: block 922263 by -1 /usr/lib/python2.7/dist-packages/tg/controllers/decoratedcontroller.py in () 12 from tg.predicates import NotAuthorizedError, not_anonymous 13 ---> 14 from crank.util import get_params_with_argspec, flatten_arguments 15 16 from tg.flash import flash ImportError: cannot import name flatten_arguments flatten_arguments was added in python-crank 0.8.0 and the setup.py install_requires has 'crank >= 0.8.0, < 0.9.0'. This also breaks building turbogears2-doc (#922263) which is definitely RC but I don't know if this can be considered RC for python-turbogears2 itself. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Versions of packages python-turbogears2 depends on: ii python 2.7.15-4 ii python-babel 2.6.0+dfsg.1-1 ii python-crank 0.7.2-4 ii python-genshi0.7.1-5 ii python-markupsafe1.1.0-1 ii python-pylons1.0.3-1 ii python-repoze.lru0.7-1 ii python-repoze.tm22.0-1 ii python-toscawidgets 0.9.7.2-3 ii python-weberror 0.13.1+dfsg-1 ii python-webflash 0.1a9-5 ii python-webob 1:1.8.5-1 Versions of packages python-turbogears2 recommends: pn python-pysqlite2 pn python-tg.devtools Versions of packages python-turbogears2 suggests: pn python-elixir -- debconf-show failed -- WBR, wRAR signature.asc Description: PGP signature
