Bug#970777: Acknowledgement (fish: tty settings are not resetted on exit)

On Mon, 28 Sep 2020 at 02:56, Boyuan Yang wrote: > Please let me know if this will be handled in the near future. If not > (or if there's no reply within 1 week), I plan to do a NMU stable > upload and contact the Release Team about this stable upload. I can't take care of this right now, so

Bug#969225: python3-electrum: Please relax dependency on python3-qdarkstyle

On Sat, 29 Aug 2020 at 16:45, wrote: > On top of that, since 4.0.2-1, python3-electrum has "Depends: > python3-qdarkstyle". Is this absolute dependency needed? > (See Policy 7.2¹ for details.) This dependency was picked up mostly by accident; upstream specifies a dependency on qdarkstyle in

Bug#968780: ratt outputs thousands of warnings

Package: ratt Version: 0.0~git20180127.c44413c-2+b10 Severity: normal I have a multiarch amd64 system with i386 active. This causes around 30,000 lines of warnings like this to be output by ratt: (W)Packages: Ignoring Package (python3-pyzfs,0.8.4-2,i386) : architecture: i386 is not included in

Bug#968666: electrum: exception which prevents startup "Non keyword-only attributes not allowed after..."

On Wed, 19 Aug 2020 at 19:28, Luke Kenneth Casson Leighton wrote: > > On Wed, 19 Aug 2020 at 14:48, lkcl wrote: > > > > > > ValueError: Non keyword-only attributes are not allowed after a > > > keyword-only attribute. Attribute in question: Attribute(name='invoice', > > > default=NOTHING,

Bug#968666: electrum: exception which prevents startup "Non keyword-only attributes not allowed after..."

Control: tags -1 - upstream Control: forcemerge 968563 -1 On Wed, 19 Aug 2020 at 14:48, lkcl wrote: > > ValueError: Non keyword-only attributes are not allowed after a keyword-only > attribute. Attribute in question: Attribute(name='invoice', default=NOTHING, > validator=None, repr=True,

Bug#968410: Patch

Control: tags -1 + patch Attached patch fixes this. From 46f86fdd03d77d6d2a6d4f0fc3f64c447093bae7 Mon Sep 17 00:00:00 2001 From: Tristan Seligmann Date: Sat, 15 Aug 2020 11:28:42 +0200 Subject: [PATCH] Install _distutils_hack. Closes: #968410. --- debian/changelog | 7

Bug#968303: fish-common: pkgconfig lists /usr/local

On Thu, 13 Aug 2020 at 10:11, David Adam wrote: > > Futhermore, the variable $fish_completion_path still lists loads of > > flatpak directories, which are not available in Debian, and should > > preferrably be removed. > > Do you mean $fish_complete_path? My guess is that those directories have >

Bug#968150: lintian-brush: Failure to fix public-upstream-key-not-minimal

Package: lintian-brush Version: 0.74 Severity: normal This is happening to me with src:anorack. lintian: I: anorack source: public-upstream-key-not-minimal upstream/signing-key.asc has 3 extra signature(s) for keyid 2D4EB3A6015475F5 lintian-brush: Fixer 'public-upstream-key-not-minimal' made

Bug#967241: RM: twistedchecker/experimental -- ROM; Not in unstable, irrelevant for Debian

Package: ftp.debian.org Severity: normal This package does not really belong in Debian and has never been in unstable.

Bug#966485: git-buildpackage: [gbp pull] git merge invoked without --ff

Package: git-buildpackage Version: 0.9.20 Severity: normal gbp invokes git merge expecting the default behaviour of -ff; however, my global config sets --no-ff as default so I end up with unexpected merge commits. gbp should explicitly pass --ff to git merge and git pull in order to get the

Bug#965179: ITP: hypothesis-auto -- Extends Hypothesis to add fully automatic testing of type annotated functions

Package: wnpp Severity: wishlist Owner: Tristan Seligmann * Package name    : hypothesis-auto   Version         : 1.1.4   Upstream Author : Timothy Crosley * URL             : https://pypi.org/project/hypothesis-auto/ * License         : MIT   Programming Lang: Python   Description

Bug#961263: nvidia-cuda-dev: File collision

Package: nvidia-cuda-dev Version: 10.1.168-10 Severity: important dpkg: error processing archive /var/cache/apt/archives/nvidia-cuda-dev_10.1.168-10_amd64.deb (--unpack): trying to overwrite '/usr/include/ansidecl.h', which is also in package binutils-dev 2.34-8 -- System Information: Debian

Bug#892264: Hy 0.17.0

Go for it! Maintainer should probably be DPMT anyway. On Sat, 17 Aug 2019 at 01:31, Tianon Gravi wrote: > On Tue, 4 Jun 2019 at 16:59, Tianon Gravi wrote: > > I've updated Git with what I think is finally successful packaging of > > a newer Hy version (0.17.0 ATM). It requires updated

Bug#921688: NMU Diff

Thank you for taking care of this; I plan to package a new upstream version when I can, but the need to package new dependencies makes this non-trivial and due to personal circumstances I have not yet had the opportunity to handle this. On Tue, 7 May 2019 at 04:30, Sam Hartman wrote: > > Dear

Bug#924650: epsilon: diff for NMU version 0.7.1-1.1

Thanks! On Sat, 6 Apr 2019 at 13:12, Tobias Frost wrote: > Control: tags 924650 + pending > > > Dear maintainer, > > I've prepared an NMU for epsilon (versioned as 0.7.1-1.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. > > Regards. > > --

Bug#918476: ITS: fish

b1 > X-Debbugs-CC: Tristan Seligmann > > Hi Tristan, > > fish is my default login shell and I wish to use fish 3.0 and push > fish 3.0.X into Buster. So following the ITS process I'm filing this > bug. > > > https://www.debian.org/doc/manuals/developers-reference/ch

Bug#916682: python-cryptography: build from source fails with libssl-dev_1.1.0j-1~deb9u1 amd64

I suspect this is fixed upstream but I am unable to take care of uploading a new version for the next few weeks. An NMU / team upload would be appreciated!

Bug#902327: isort: diff for NMU version 4.3.4+ds1-1.1

On Wed, 8 Aug 2018 at 08:45 Niels Thykier wrote: > I've prepared an NMU for isort (versioned as 4.3.4+ds1-1.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. > Patch looks good to me, thanks for taking care of this.

Bug#902553: Bug#902592: [Help] Potential Cython issue with new version of h5py (Was: Bug#902592: New version does not build)

On Fri, 29 Jun 2018 at 14:40 Andreas Tille wrote: > Would you mind filing an according bug report we could refer to? > I've filed this as #902784 although I haven't had the chance to investigate the cause further. (Probably some minor packaging error)

Bug#902784: cython-dbg: StringIOTree debug module missing

Package: cython-dbg Version: 0.28.2-4 Severity: important cython ships a StringIOTree extension module: /usr/lib/python2.7/dist-packages/Cython/StringIOTree.x86_64-linux-gnu.so However, cython-dbg is missing the debug version of this module. This results in import errors when using the debug

Bug#902553: [Help] Potential Cython issue with new version of h5py (Was: Bug#902592: New version does not build)

On Fri, 29 Jun 2018 at 14:20 Andreas Tille wrote: > Hi Tristan, > > On Fri, Jun 29, 2018 at 01:31:31PM +0200, Tristan Seligmann wrote: > > This is a cython bug; cython-dbg fails to ship the StringIOTree extension > > module, so the regular non-debug module is found whe

Bug#902553: [Help] Potential Cython issue with new version of h5py (Was: Bug#902592: New version does not build)

This is a cython bug; cython-dbg fails to ship the StringIOTree extension module, so the regular non-debug module is found when doing a debug build but fails to load. On Fri, 29 Jun 2018 at 13:18 Andreas Tille wrote: > Control: tags -1 help > > I agree with Ghislain that the issue below might

Bug#884484: python-cryptography-vectors/2.2.2-1 appears to break python-cryptography in testing

On Mon, 11 Jun 2018 at 09:15 Paul Gevers wrote: > Hi Tristan, > > On 11-06-18 02:49, Tristan Seligmann wrote: > > On Sun, 10 Jun 2018 at 21:57 Paul Gevers > did you ever > > considered to add these vectors (as a second tar ball in the source 3 > >

Bug#884484: python-cryptography-vectors/2.2.2-1 appears to break python-cryptography in testing

On Sun, 10 Jun 2018 at 21:57 Paul Gevers wrote: > Hi > > On 10-06-18 21:34, Tristan Seligmann wrote: > > -vectors exists purely for the benefit of the tests, nothing outside the > > tests uses the vectors. If you are not running the tests, having a > > mismatched ve

Bug#884484: python-cryptography-vectors/2.2.2-1 appears to break python-cryptography in testing

On Sun, 10 Jun 2018 at 21:06 Paul Gevers wrote: > need to stay in lock step. In this bug (#884484) the solution was to > tighten the test dependencies, which is one way to achieve this (albeit > it will only work for the next time without the help of the RT or me), > but I wonder if this

Bug#892112: python-cryptography appears to intend to install python-cffi as a dependency, but it isn't installed

On Mon, 5 Mar 2018 at 20:12 Corey Bryant wrote: >Installation of python-cryptography doesn't install python-cffi. This >is on Ubuntu Bionic. The following bug has some more details: > > https://bugs.launchpad.net/ubuntu/+source/python-cryptography/+bug/1752660

Bug#884417: python-trezor v0.9.0 tagged - next steps?

I have a fixed version prepared in git now, but it looks like we need to wait for Electrum 3.1.0 to be released as 3.0.6 is not compatible with python-trezor 0.9.0 On Tue, 27 Feb 2018 at 06:55 Jonathan Cross wrote: > > I'll try to take care of it this week. > > Fantastic,

Bug#884417: python-trezor v0.9.0 tagged - next steps?

On Mon, 26 Feb 2018 at 21:20 Andreas Beckmann wrote: > This is what I understood from reading debian/{changelog,control} and > the upload notifications on the qa page [1]: the package was split with > the 0.7.16-1 upload, but lacks proper Breaks+Replaces for the files > being

Bug#888303: zbar: Ship python3-zbar package

Source: zbar Version: 0.10+doc-10.1+b1 Severity: wishlist Electrum has python3-zbar as an optional dependency now since the move to Python 3, but this does not actually exist in Debian yet. Could you add it? -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT

Bug#887582: FTBFS: test suite failures on 32-bit arches

Source: fish Version: 2.7.1-2 Severity: serious Tags: upstream Justification: FTBFS The test suite is failing on 32-bit arches in a somewhat inscrutable way. I am investigating this but filing a bug to track the status so long. -- System Information: Debian Release: buster/sid APT prefers

Bug#777089: Next python-mote pre-condition test issue: python-jsondiff trows ModuleNotFoundError: No module named 'nose_random'

On Tue, 16 Jan 2018 at 22:45 Andreas Tille wrote: > My web search for a module named 'nose_random' remained empty. > I found this package, which seems to match, from the same organization: https://github.com/ZoomerAnalytics/nose-random Unfortunately it seems to be unreleased,

Bug#886683: [Pkg-bitcoin-devel] Bug#886683: electrum: Security vulnerability in electrum

On Tue, 16 Jan 2018 at 09:09 Salvatore Bonaccorso <car...@debian.org> wrote: > Hi, > > On Tue, Jan 16, 2018 at 06:56:19AM +, Tristan Seligmann wrote: > > On Mon, 15 Jan 2018 at 22:21 Moritz Mühlenhoff <j...@inutil.org> wrote: > > > > > Ok, I'll upda

Bug#887415: RM: electrum/1.9.8-4

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm The same as #887412, this version of Electrum is no longer able to connect to the network. It is unaffected by the security issue, but we should remove it to avoid user confusion. -- System

Bug#886683: [Pkg-bitcoin-devel] Bug#886683: electrum: Security vulnerability in electrum

On Mon, 15 Jan 2018 at 22:21 Moritz Mühlenhoff wrote: > Ok, I'll update the Debian Security Tracker accordingly, but we also should > remove the package in the next stable point release. > Can you please also file a bug? (reportbug release.debian.org -> "rm") > Yes, good point;

Bug#887412: RM: electrum/2.7.9-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Unfortunately due to protocol changes Electrum 2.7.9 (the version in stretch) is unable to connect to the Electrum servers. Backporting the changes would require extensive/invasive changes to

Bug#777089: Please help with test suite error and installation problem of python-aws-xray-sdk (Was: If there is no response in debian-python then debian-science might be the right team)

On Mon, 15 Jan 2018 at 13:59 Andreas Tille wrote: >SyntaxError: invalid syntax > !!! Interrupted: 4 errors during collection > > All of these syntax errors relate to syntax that only exist on Python 3, thus I would conclude that this

Bug#886810: yubioath-desktop: New upstream release: 4.3.2

Package: yubioath-desktop Version: 3.0.1-2 Severity: wishlist There is a new upstream version available. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture:

Bug#886683: [Pkg-bitcoin-devel] Bug#886683: electrum: Security vulnerability in electrum

Control: found -1 2.4.2+dfsg1-1 Control: fixed -1 3.0.5-1 On Tue, 9 Jan 2018 at 00:21 Daniel Koszta wrote: > A new, fixed version is already available in debian unstable, but it > should be included in stable and testing as soon as possible. > Unfortunately the version

Bug#883717: Oops, correct patch

On Wed, 6 Dec 2017 at 23:56 Tristan Seligmann <mithra...@mithrandi.net> wrote: > On Wed, 6 Dec 2017 at 23:52 Thomas Goirand <z...@debian.org> wrote: > >> The OpenStack team doesn't need this package anymore, and it'd be nice >> to have it within the DPMT instead.

Bug#884064: ITP: jsonrpclib-pelix -- This project is an implementation of the JSON-RPC v2.0 specification (backwards-

Package: wnpp Severity: wishlist Owner: Tristan Seligmann <mithra...@debian.org> * Package name: jsonrpclib-pelix Version : 0.3.1 Upstream Author : Thomas Calmant <thomas.calmant+git...@gmail.com> * URL : http://github.com/tcalmant/jsonrpcli

Bug#883717: Oops, correct patch

On Wed, 6 Dec 2017 at 23:52 Thomas Goirand wrote: > The OpenStack team doesn't need this package anymore, and it'd be nice > to have it within the DPMT instead. Would you like to do that work? > I'm still happy to adopt the package; it looks like upstream does not actually

Bug#881703: Please package Electrum 3.0.2 -- updates after segwit softfork

Hi all, I am currently doing final testing on an Electrum 3.0.2 package for Debian; however I will need to wait for python3-jsonrpclib-pelix to go through NEW before I can upload (upstream is using a jsonrpclib fork to get Python 3 support) so it may still be a little while before this lands in

Bug#883717: Oops, correct patch

Oops. Actually correct patch attached this time. >From e08d824f98d32e13c8252eae05afa96356c1d995 Mon Sep 17 00:00:00 2001 From: Tristan Seligmann <mithra...@mithrandi.net> Date: Wed, 6 Dec 2017 21:02:34 +0200 Subject: [PATCH] Add Python 3 package --- debian/con

Bug#883717: python-jsonrpclib: Please package python3-jsonrpclib

: systemd (via /run/systemd/system) -- no debconf information >From 467016f79243b4d3704fb721a3b8229a687a49a4 Mon Sep 17 00:00:00 2001 From: Tristan Seligmann <mithra...@mithrandi.net> Date: Wed, 6 Dec 2017 21:02:34 +0200 Subject: [PATCH] Add Python 3 package --- 0001-Add-Python-3-package.p

Bug#882170: python-cryptography: missing dependency on python-cffi

Control: retitle -1 python-cryptography: extraneous setuptools dependency on cffi Control: tags -1 + pending Argh! This is caused by an incomplete fix for #882011 of course. On Sun, 19 Nov 2017 at 22:45 Adrian Bunk wrote: > pkg_resources.DistributionNotFound: The 'cffi>=1.7'

Bug#881458: hlint fails to run

Package: hlint Version: 2.0.9-1+b1 Severity: important hlint fails to run on everything with this error: hlint: user error (Failed to find requested hint files: /usr/share/hlint/hlint.yaml ) That file does indeed not exist (and is not

Bug#871994: python-cryptography FTBFS: TypeError: putenv() argument 2 must be string without null bytes, not str

On Sun, 13 Aug 2017 at 14:36 Adrian Bunk wrote: > Some recent change in unstable makes python-cryptography FTBFS: > Control: reassign -1 python-pytest Control: affects -1 python-cryptography Control: tags -1 + upstream fixed-upstream This is caused by an upstream bug in

Bug#870091: ITP: pyaes -- Pure-Python Implementation of the AES block-cipher and common modes of operation

Package: wnpp Severity: wishlist Owner: Tristan Seligmann <mithra...@mithrandi.net> * Package name: pyaes Version : 1.6.0 Upstream Author : Richard Moore <py...@ricmoo.com> * URL : https://github.com/ricmoo/pyaes * License : License :: OSI App

Bug#866668: src:python-cryptography: Misbuild with more than one supported python3 version

Control: severity -1 important On Fri, 30 Jun 2017 at 19:33 Scott Kitterman wrote: > Technically, it builds, but in a way that's not useful. It would actually > be > better if it had failed (I noticed this from reviewing build logs after the > python3 interpreter depends

Bug#866553: python-cryptography FTBFS with python 3.6

On Fri, 30 Jun 2017 at 04:45 Adrian Bunk wrote: > File "/usr/lib/python3/dist-packages/cffi/api.py", line 56, in __init__ > import _cffi_backend as backend > ModuleNotFoundError: No module named '_cffi_backend' > The cause of this error is that Python 3.6 was just added

Bug#862277: python-cryptography: Importing the cryptography.hazmat.backends module is very slow

On Wed, 10 May 2017 at 16:36 David Douard wrote: > the loading of the cryptography.hazmat.backends module is very slow on > my stretch machine: > This is ultimately caused by pkg_resources doing slow things at import time: https://github.com/pypa/setuptools/issues/510

Bug#850003: jessie-pu: package python-cryptography/0.6.1-1+deb8u1

. Barratt wrote: > > Control: tags -1 + confirmed > > > > On Tue, 2017-01-03 at 06:09 +0200, Tristan Seligmann wrote: > > > Backport the fix for CVE-2016-9243 which was deemed not severe enough > for a > > > DSA. I've attached a full debdiff, the patch is quite small

Bug#857278: python-nacl: sodium_init() fails because already initialized.

On Wed, 15 Mar 2017 at 07:39 wrote: > This patch is no longer required now as this issue has been fixed with > the new release 1.1.0 in upstream. > Thanks for tracking / following up on this issue; I have been paying attention despite the silence from my side, and it is

Bug#857006: python-urllib3: Missing version constraint for six

On Wed, 8 Mar 2017 at 02:11 Daniele Tricoli wrote: > I will add the >= 1.10.0, on the next upload. I plan to upload > urllib 1.20 to experimental soon. > > Should I need to backport this also for Stretch? > I think it's not critical to backport it; CCing hlieberman for a

Bug#857006: python-urllib3: Missing version constraint for six

Package: python-urllib3 Version: 1.19.1-1 Severity: important setup.py does not have a version constraint on six as it is vendored upstream, but since we are unvendoring it in Debian, we need a version constraint. This is made trickier by the fact that upstream won't be tracking the minimum

Bug#850003: jessie-pu: package python-cryptography/0.6.1-1+deb8u1

an empty byte string +for small key sizes). + * Fix FTBFS due to SSL2 method detection. + + -- Tristan Seligmann <mithra...@debian.org> Sun, 01 Jan 2017 22:19:17 +0200 + python-cryptography (0.6.1-1) unstable; urgency=medium * New upstream release. diff -Nru python-cryptography

Bug#849379: whalebuilder: Relax dependency on docker.io

Package: whalebuilder Version: 0.4.1 Severity: wishlist I'd like to be able to use this package with the upstream Docker packages instead of the Debian ones (since I need the former installed for other reasons, and they can't be installed simultaneously); what about relaxing the dependency to

Bug#848065: python-cryptography: renders ansible unusable

Control: notfound -1 1.5.3-1 You have an installation of PyOpenSSL in /home/pjs/.local/lib/python2.7/site-packages that is not compatible with Cryptography 1.5.3; removing or upgrading this should solve your problem. To avoid this kind of problem in future, I would recommend using virtualenv

Bug#843631: Root cause

Control: retitle 843631 Downstream incompatibilities due to SSL_ST_* constants not defined in OpenSSL 1.1.0 I think I have it figured out now: OpenSSL 1.1.0 was uploaded to unstable recently, which no longer defines (some of?) these SSL_ST_* constants. python-cryptography 1.5.2 was uploaded and

Bug#843631: AttributeError: 'module' object has no attribute 'SSL_ST_INIT'

again once I track down the root cause of the problem. commit c551c1690dc2ec0a12f779eaab780da45e40d1c6 Author: Tristan Seligmann <mithra...@debian.org> Date: Tue Nov 8 05:34:19 2016 +0200 Import python-cryptography_1.5.3.orig.tar.gz diff --git a/CHANGELOG.rst b/CHANGELOG.rst index

Bug#835543: python-pip-whl: Unable to create virtualenv

Package: python-pip-whl Version: 8.1.2-2 Severity: important File "/usr/share/python-wheels/pip-8.1.2-py2.py3-none-any.whl/pip/__init__.py", line 21, in from pip._vendor.requests.packages.urllib3.exceptions import DependencyWarning ImportError: cannot import name 'DependencyWarning'

Bug#833679: BitPaddedInt import error

Control: reassign -1 picard Control: forwarded -1 http://tickets.musicbrainz.org/browse/PICARD-833 Your hypothesis was correct: `mutagen.id3.BitPaddedInt`used to be imported from `mutagen._id3util.BitPaddedInt` in `mutagen.id3`; however, `id3` was turned into a package, so now the import doesn't

Bug#802582: [Python-apps-team] Bug#802582: isort: Missing isort for python2

On Tue, 19 Jul 2016 at 19:58 Sandro Tosi wrote: > any update on this? i have pylint which depends on isort now, and I > cant package it because isort doesnt expose a python2 package - please > have a look at it asap, thanks! > Sorry, I pretty much forgot about this bug.

Bug#828518:

Control: tag -1 + pending upstream Upstream have OpenSSL 1.1.0 support nearly ready to go, basically just waiting on the final 1.1.0 release to be out. See: https://github.com/pyca/cryptography/milestones/1.1.0%20Support

Bug#820962: ruby: File conflict between ruby 1:2.3.0+3 and ruby-dev 1:2.3.0+1

Package: ruby Version: 1:2.3.0+3 Severity: serious Justification: Policy 7.6.1 Unpacking ruby (1:2.3.0+3) over (1:2.3.0+1) ... dpkg: error processing archive /var/cache/apt/archives/ruby_1%3a2.3.0+3_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/ruby.pc', which

Bug#816063: SNI

The reason https://self-signed.badssl.com works is because Emacs 24 does not do SNI; badssl.com serves up a cert valid for "*.badssl.com" in the absence of SNI, which is perfectly valid for self-signed.badssl.com. This is apparently fixed upstream already:

Bug#816735: python-flake8: Missing dependency on python-pep8

Package: python-flake8 Version: 2.2.2-1 Severity: important There is a dependency on pep8, but this is not sufficient (pep8 only pulls in python3-pep8): mithrandi@lorien ~> flake8 --version Traceback (most recent call last): File "/usr/bin/flake8", line 5, in from pkg_resources import

Bug#816043: pypy: bsddb module is broken

Package: pypy Version: 4.0.1+dfsg-1 Severity: normal The extension module seems to be missing: Python 2.7.10 (4.0.1+dfsg-1, Nov 20 2015, 19:46:58) [PyPy 4.0.1 with GCC 5.2.1 20151028] on linux2 Type "help", "copyright", "credits" or "license" for more information. import bsddb Traceback

Bug#808433: nethogs: diff for NMU version 0.8.1-0.3

Control: tags 808433 + patch Dear maintainer, I've prepared an NMU for nethogs (versioned as 0.8.1-0.3). The diff is attached to this message. (This is just Arnout Engelen's package from mentors, with a tiny tweak to the changelog) Regards. diff -Nru nethogs-0.8.0/Changelog

Bug#815654: dh-python: dh_python does not understand environment markers

On Tue, 23 Feb 2016 at 14:12 Piotr Ożarowski <pi...@debian.org> wrote: > [Tristan Seligmann, 2016-02-23] > > As per subject; this may be a bit tricky to solve, > > I will not even try to support PEPs that are changed or replaced by > another one every few months (i.e. most

Bug#815654: dh-python: dh_python does not understand environment markers

Package: dh-python Version: 2.20151103 Severity: normal As per subject; this may be a bit tricky to solve, -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64)

Bug#815387: ITP: python-attrs -- Python attributes without boilerplate

Package: wnpp Severity: wishlist Owner: Tristan Seligmann <mithra...@mithrandi.net> * Package name: python-attrs Version : 15.2.0 Upstream Author : Hynek Schlawack <h...@ox.cx> * URL : https://github.com/hynek/attrs * License : MIT Programming

Bug#815385: python-service-identity: Missing dependency on python-attrs

Package: python-service-identity Version: 16.0.0-1 Severity: grave Justification: renders package unusable service_identity 16.0.0-1 requires python-attrs (upstream switched from characteristic to attrs), but the Depends: is missing. Also, it would be unsatisfiable due to attrs not being

Bug#815090: python-hypothesis: Fails to build reproducibly

Source: python-hypothesis Version: 1.11.0-1 Severity: minor Tags: upstream setup.py calculates the "all" extra in a way that depends on dict ordering, thus the setuptools-constructed requires.txt is not reproducible. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug

Bug#811172: Fixed upstream

This is fixed in e7316a1 [1] upstream, may be worth backporting that patch. [1] https://bitbucket.org/durin42/hg-git/commits/e7316a1

Bug#811386: ITP: python-genty -- Python library for test generation

Package: wnpp Severity: wishlist Owner: Tristan Seligmann <mithra...@mithrandi.net> * Package name: python-genty Version : 1.3.0 Upstream Author : Box <o...@box.com> * URL : https://github.com/box/genty * License : Apache 2.0 Programming

Bug#810643: python-axiom: FTBFS: test_sequence.TestSequenceOperations.test_slices: Second list contains 3 additional elements.

Control: forwarded -1 https://github.com/twisted/axiom/issues/56 These test failures are caused by sqlite3 3.10.0-1 being built with the SQLITE_LIKE_DOESNT_MATCH_BLOBS compile-time option activated, which breaks startswith/endswith on blob columns. I've opened an issue upstream to deal with this,

Bug#808763: Running pytest

If you want to run pytest with a particular version of python, then "pythonX.Y -m pytest" is a much better way than relying on the py.test-X.Y scripts.

Bug#808605: ITP: python-flaky -- Plugin for nose or py.test that automatically reruns flaky tests

Package: wnpp Severity: wishlist Owner: Tristan Seligmann <mithra...@mithrandi.net> * Package name: python-flaky Version : 3.0.1 Upstream Author : Box <o...@box.com> * URL : https://github.com/box/flaky * License : Apache License Programming

Bug#807681: python3-pkg-resources: UnicodeDecodeError when parsing egg-info files with non-ASCII content

Package: python3-pkg-resources Version: 18.7-1 Severity: important An example of such a file can be found in python3-dialog (the Description contains UTF-8 encoded non-breaking spaces), but I am sure there are others. The failure traceback looks as follows (from trying to run an unrelated

Bug#807681: Further investigation

Upon further investigation, it seems this error is caused by something (git-buildpackage?) setting LC_ALL=POSIX (which also overrides any LANG setting); forcing LC_ALL to a UTF-8 locale solves the issue. So I guess this is not a pkg_resources bug, but I'm not sure exactly where to reassign it to.

Bug#805388: libcuda1: Multi-arch file mismatch

Package: libcuda1 Version: 352.55-3 Severity: serious Justification: Policy 7.4 libcuda1 declares Multi-Arch: same; libcuda1:amd64 and libcuda1:i386 are not co-installable in experimental due to differing file contents: Preparing to unpack .../libcuda1_352.55-3_i386.deb ... Unpacking

Bug#803949: electrum: Electrum unable to start; Cannot read config file

On Tue, 3 Nov 2015 at 17:09 Zachary Peterson wrote: > File "/usr/lib/python2.7/dist-packages/electrum/simple_config.py", line > 157, in read_user_config > raise IOError("Cannot read config file.") > IOError: Cannot read config file. This error is raised if an exception

Bug#803422: electrum: missing Dependency on python-qt4

On Fri, 30 Oct 2015 at 01:57 Sebastian Kuzminsky wrote: > I'm not sure why ${python:Depends} didnt pick it up. I manually added > python-qt4 to the Depends line and now it's fine. > ${python:Depends} doesn't include it because setup.py doesn't declare a dependency on qt as

Bug#802638: [pkg-ntp-maintainers] Bug#802638: ntpd fails to start with "Cannot find user ID 113"

On Thu, 22 Oct 2015 at 09:07 Kurt Roeckx <k...@roeckx.be> wrote: > On Thu, Oct 22, 2015 at 01:40:06AM +0200, Tristan Seligmann wrote: > > Package: ntp > > Version: 1:4.2.8p4+dfsg-1 > > Severity: grave > > Justification: renders package unusable > > > >

Bug#802730: ITP: python-setuptools-scm -- Handles managing your python package versions in scm metadata.

Control: forcemerge 797915 -1 On Fri, 23 Oct 2015 at 00:51 Brian May wrote: > * Package name: python-setuptools-scm > Already packaged, see #797915.

Bug#802638: ntpd fails to start with "Cannot find user ID 113"

Package: ntp Version: 1:4.2.8p4+dfsg-1 Severity: grave Justification: renders package unusable As per subject. This may well be a duplicate of #793745, however: - I am using the default ntp.conf shipped with the package, including the "rlimit memlock 0" line. - Downgrading to 4.2.8p3+dfsg-1

Bug#801801: ITP: python-phpserialize -- Python port of PHP's serialize and unserialize functions

Package: wnpp Severity: wishlist Owner: Tristan Seligmann <mithra...@mithrandi.net> * Package name: python-phpserialize Version : 1.3 Upstream Author : Armin Ronacher <armin.ronac...@active-4.com> * URL : https://github.com/mitsuhiko/phpseriali

Bug#801796: nikola: New upstream release: 7.7.2

Package: nikola Version: 7.6.4-1 Severity: wishlist There is a new upstream release available; please package it.

Bug#799694: Not just ppc64

Control: severity -1 serious This appears to be happening on all arches, not just ppc64. See, for example: https://buildd.debian.org/status/fetch.php?pkg=healpy=amd64=1.8.1-1%2Bb2=1444131922

Bug#789670: Dropping python-pies2overrides

Since frosted is the only reverse dep of python-pies, and it can use python3-pies instead, how about just dropping python-pies/python-pies2overrides completely?

Bug#799278: python-cffi: Non-deterministic results with anonymous unions/structs

Package: python-cffi Version: 1.1.2-1 Severity: minor Tags: upstream fixed-upstream When an anonymous union or struct is encountered, for example the union in: typedef struct { union { int a; char b; } u } mystruct; CFFI internally gives this a name like "$1". However,

Bug#798691: Reproducible in sid

Note that this problem is reproducible in unstable, as well. (glibc in unstable is using gcc 4.8 as well, so I guess this is not surprising at all) python-cffi_1.1.2-1_i386-20150914-0052.build Description: Binary data

Bug#797977: pytest: Provide pypy package

Source: pytest Version: 2.7.2-2 Severity: wishlist This would involve a pypy-pytest package, as well as possibly a py.test-pypy binary or something like this (not sure exactly what to call it). I would like this to be able to run py.test-based test suites in various pypy-* packages. -- System

Bug#792231: electrum

Great news! I'm currently testing a 2.4.1 Debian package and so far everything looks good; assuming nothing else turns up, I will be uploading the new version within a few days. On Tue, 18 Aug 2015 at 11:41 Thomas Voegtlin thom...@electrum.org wrote: Please note that the tlslite the dependency

Bug#792231: This needs examined as soon as possible

Unfortunately there are some significant challenges with 2.0+. The primary issue is the dependency on tlslite, which was removed from Debian previously due to being insecure and unmaintained. In addition, quite a bit of the certificate handling code does things incorrectly (see eg. the certificate

Bug#792231: electrum

On Mon, 3 Aug 2015 at 20:27 Thomas Voegtlin thom...@electrum.org wrote: On 08/03/2015 10:41 AM, Tristan Seligmann wrote: In addition, quite a bit of the certificate handling code does things incorrectly (see eg. the certificate chain verification code[1] that does not check

Bug#793822: fish is not added to /etc/shells

Control: tag -1 + pending Thanks for the report! In fact, this was supposed to be already done, but the maintainer scripts got messed up at some point, resulting in this functionality being broken. I'll fix this in the next upload. On Mon, 27 Jul 2015 at 22:12 Judicaël Grasset

Bug#785432:

Control: tag -1 + help The only requirement is that *some* GStreamer audiosink is installed, in order for Quod Libet to send audio to it. Depending on gstreamer1.0-pulseaudio doesn't seem reasonable since it would force pulseaudio to be pulled in even on systems that are not using it (and then

Bug#789768: python-cryptography: Upstream version is 0.9.1

The new version requires python-idna (which is through NEW), and python-ipaddress (which is still in NEW). I am planning to upload a new python-cryptography once python-ipaddress makes it out of NEW. On Wed, 24 Jun 2015 at 11:51 Sebastien Delafond s...@debian.org wrote: Source:

  1   2   3   >