[Python-modules-team] Bug#1063396: lircd systemd service times out
control: fixed -1 0.10.2-0.6 control: close -1 so lircd gets terminated despite everything being just fine. that's because the service type is specified as "notify", but clearly the daemon doesn't actually send a readiness notification. that's probably either because lirc was built without systemd support against intentions (missing build-dep?), or because it doesn't actually have support for systemd in the first place, and the service type should be "simple" (or maybe "exec", but nobody seems to use that). Please try newer version, yes the systemd support was accidentally dropped G. OpenPGP_signature.asc Description: OpenPGP digital signature ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#1062699: lirc: regression due to changed build dependencies in version 0.10.2-0.5
control: tags -1 patch pending --- lirc-0.10.2/debian/changelog2024-01-17 14:21:20.0 +0100 +++ lirc-0.10.2/debian/changelog2024-02-12 11:47:28.0 +0100 @@ -1,3 +1,9 @@ +lirc (0.10.2-0.6) unstable; urgency=medium + + * Add back libsystemd-dev (Closes: #1062699) + + -- Gianfranco Costamagna Mon, 12 Feb 2024 11:47:28 +0100 + lirc (0.10.2-0.5) unstable; urgency=medium * Non-maintainer upload. diff -Nru lirc-0.10.2/debian/control lirc-0.10.2/debian/control --- lirc-0.10.2/debian/control 2024-01-17 14:21:18.0 +0100 +++ lirc-0.10.2/debian/control 2024-02-12 11:47:26.0 +0100 @@ -21,6 +21,7 @@ libftdi1-dev, libpython3-dev (>= 3.5), systemd-dev [linux-any], + libsystemd-dev [linux-any], libudev-dev [linux-any], libusb-dev, libusb-1.0-0-dev, On Fri, 2 Feb 2024 19:46:05 +0100 Thomas Uhle wrote: Source: lirc Version: 0.10.2-0.5 Severity: serious X-Debbugs-CC: 1060...@bugs.debian.org Dear maintainers, dear Gianfranco, unfortunately, you have not exchanged systemd by systemd-dev but libsystemd-dev by systemd-dev instead. So libsystemd-dev is no longer a build dependency and so /usr/sbin/lircd is no longer build with libsystemd.so for instance. Could you please fix that. Thank you in advance! Best regards, Thomas Uhle ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#1060093: lirc: diff for NMU version 0.10.2-0.5
Package: lirc
Version: 0.10.2-0.4
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for lirc (versioned as 0.10.2-0.5) and
uploaded it1060...@bugs.debian.org.
Regards.
Gianfranco
diff -Nru lirc-0.10.2/debian/changelog lirc-0.10.2/debian/changelog
--- lirc-0.10.2/debian/changelog2024-01-08 16:30:19.0 +0100
+++ lirc-0.10.2/debian/changelog2024-01-17 14:21:20.0 +0100
@@ -1,3 +1,14 @@
+lirc (0.10.2-0.5) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Michael Biebl ]
+ * Update dependency to systemd-dev (Closes: #1060557)
+ [ Svante Signell, Samuel Thibault ]
+ * Fix build on hurd (Closes: #1060093)
+
+ -- Gianfranco Costamagna Wed, 17 Jan 2024
14:21:20 +0100
+
lirc (0.10.2-0.4) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru lirc-0.10.2/debian/control lirc-0.10.2/debian/control
--- lirc-0.10.2/debian/control 2024-01-08 16:30:19.0 +0100
+++ lirc-0.10.2/debian/control 2024-01-17 14:21:18.0 +0100
@@ -20,7 +20,7 @@
libasound2-dev [linux-any kfreebsd-any],
libftdi1-dev,
libpython3-dev (>= 3.5),
- libsystemd-dev [linux-any],
+ systemd-dev [linux-any],
libudev-dev [linux-any],
libusb-dev,
libusb-1.0-0-dev,
diff -Nru lirc-0.10.2/debian/patches/include_media_lirc.h.diff
lirc-0.10.2/debian/patches/include_media_lirc.h.diff
--- lirc-0.10.2/debian/patches/include_media_lirc.h.diff1970-01-01
01:00:00.0 +0100
+++ lirc-0.10.2/debian/patches/include_media_lirc.h.diff2024-01-17
14:21:20.0 +0100
@@ -0,0 +1,133 @@
+Description:
+ Lirc FTBFS on HURD
+ This is due to usage of __u32 (and __u16,__u64) in
+ include/media/lirc.h, which is not defined on GNU/Hurd. Additionally
+ inclusion of header files is ifdef-ed and config.h is included.
+
+Author: Svante Signell
+Bug-Debian: https://bugs.debian.org/1060093
+
+Index: lirc-0.10.2/include/media/lirc.h
+===
+--- lirc-0.10.2.orig/include/media/lirc.h
lirc-0.10.2/include/media/lirc.h
+@@ -6,8 +6,27 @@
+ #ifndef _LINUX_LIRC_H
+ #define _LINUX_LIRC_H
+
++#include "config.h"
++
++#ifdef HAVE_STDINT_H
++#include
++#endif
++
++#ifdef HAVE_LINUX_TYPES_H
+ #include
++#endif
++
++#ifdef HAVE_LINUX_IOCTL_H
+ #include
++#endif
++
++#ifdef HAVE_SYS_IOCTL_H
++#include
++#endif
++
++#ifdef __GNU__
++#include
++#endif
+
+ #define PULSE_BIT 0x0100
+ #define PULSE_MASK 0x00FF
+@@ -93,55 +112,55 @@
+
+ /*** IOCTL commands for lirc driver ***/
+
+-#define LIRC_GET_FEATURES _IOR('i', 0x, __u32)
++#define LIRC_GET_FEATURES _IOR('i', 0x, uint32_t)
+
+-#define LIRC_GET_SEND_MODE _IOR('i', 0x0001, __u32)
+-#define LIRC_GET_REC_MODE _IOR('i', 0x0002, __u32)
+-#define LIRC_GET_REC_RESOLUTION_IOR('i', 0x0007, __u32)
++#define LIRC_GET_SEND_MODE _IOR('i', 0x0001, uint32_t)
++#define LIRC_GET_REC_MODE _IOR('i', 0x0002, uint32_t)
++#define LIRC_GET_REC_RESOLUTION_IOR('i', 0x0007, uint32_t)
+
+-#define LIRC_GET_MIN_TIMEOUT _IOR('i', 0x0008, __u32)
+-#define LIRC_GET_MAX_TIMEOUT _IOR('i', 0x0009, __u32)
++#define LIRC_GET_MIN_TIMEOUT _IOR('i', 0x0008, uint32_t)
++#define LIRC_GET_MAX_TIMEOUT _IOR('i', 0x0009, uint32_t)
+
+ /* code length in bits, currently only for LIRC_MODE_LIRCCODE */
+-#define LIRC_GET_LENGTH_IOR('i', 0x000f, __u32)
++#define LIRC_GET_LENGTH_IOR('i', 0x000f, uint32_t)
+
+-#define LIRC_SET_SEND_MODE _IOW('i', 0x0011, __u32)
+-#define LIRC_SET_REC_MODE _IOW('i', 0x0012, __u32)
++#define LIRC_SET_SEND_MODE _IOW('i', 0x0011, uint32_t)
++#define LIRC_SET_REC_MODE _IOW('i', 0x0012, uint32_t)
+ /* Note: these can reset the according pulse_width */
+-#define LIRC_SET_SEND_CARRIER _IOW('i', 0x0013, __u32)
+-#define LIRC_SET_REC_CARRIER _IOW('i', 0x0014, __u32)
+-#define LIRC_SET_SEND_DUTY_CYCLE _IOW('i', 0x0015, __u32)
+-#define LIRC_SET_TRANSMITTER_MASK _IOW('i', 0x0017, __u32)
++#define LIRC_SET_SEND_CARRIER _IOW('i', 0x0013, uint32_t)
++#define LIRC_SET_REC_CARRIER _IOW('i', 0x0014, uint32_t)
++#define LIRC_SET_SEND_DUTY_CYCLE _IOW('i', 0x0015, uint32_t)
++#define LIRC_SET_TRANSMITTER_MASK _IOW('i', 0x0017, uint32_t)
+
+ /*
+ * when a timeout != 0 is set the driver will send a
+ * LIRC_MODE2_TIMEOUT data packet, otherwise LIRC_MODE2_TIMEOUT is
+ * never sent, timeout is disabled by default
+ */
+-#define LIRC_SET_REC_TIMEOUT _IOW('i', 0x0018, __u32)
++#define LIRC_SET_REC_TIMEOUT _IOW('i', 0x0018, uint32_t)
+
+ /* 1 enables, 0 disables timeout reports in MODE2 */
+-#define LIRC_SET_REC_TIMEOUT_REPORTS _IOW('i
[Python-modules-team] Bug#1060093: lirc: FTBFS on hurd-i386
Hello, > > We do want modinfo on the linux platform, please make this os- > > specific. > Thanks for having a look, feel free to NMU when you agree on the patch. Alec might be overbusy, I'm pretty sure he doesn't mind some extra help :) G. ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#1049614: lirc: Fails to build binary packages again after successful build
control: fixed -1 0.10.2-0.2 control: close -1 thanks G. On Wed, 16 Aug 2023 09:42:49 +0200 Lucas Nussbaum wrote: Source: lirc Version: 0.10.1-7.2 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successful build (dpkg-buildpackage ; dpkg-buildpackage -b). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -b > > > dpkg-buildpackage: info: source package lirc > dpkg-buildpackage: info: source version 0.10.1-7.2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Nilesh Patra > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > fakeroot debian/rules clean > dh clean --with python3 >dh_auto_clean >make -j8 distclean > make[1]: Entering directory '/<>' > Making distclean in lib > make[2]: Entering directory '/<>/lib' > test -z "input_map.inc lirc/input_map.inc config.h lirc/config.h paths.h config.py driver_api.dox lirc_client.dox" || rm -f input_map.inc lirc/input_map.inc config.h lirc/config.h paths.h config.py driver_api.dox lirc_client.dox > test -z "liblirc.la liblirc_client.la liblirc_driver.la libirrecord.la" || rm -f liblirc.la liblirc_client.la liblirc_driver.la libirrecord.la > rm -rf .libs _libs > rm -f *.o > rm -f *.lo > rm -f *.tab.c > test -z "" || rm -f > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > test . = "." || test -z "" || rm -f > rm -f ./so_locations > rm -f ./.deps/ciniparser.Plo > rm -f ./.deps/config_file.Plo > rm -f ./.deps/curl_poll.Plo > rm -f ./.deps/dictionary.Plo > rm -f ./.deps/driver.Plo > rm -f ./.deps/drv_admin.Plo > rm -f ./.deps/drv_enum.Plo > rm -f ./.deps/dump_config.Plo > rm -f ./.deps/input_map.Plo > rm -f ./.deps/ir_remote.Plo OpenPGP_signature.asc Description: OpenPGP digital signature ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#976778: Known upstream, fixed with upcoming new version
On Tue, 08 Dec 2020 08:49:45 +0100 Julien Puydt wrote:
> Hi,
>
> here is the upstream patch fixing the issue :
>
> https://github.com/fplll/fpylll/commit/ede1e459f0662a0940dca6366aba20d47183a4a0
>
> I tought they'd have already released the new version with this in, but
> I should have waited until that was done...
>
> And since this patch needs other changes to apply, I can't just add it.
>
> I'll work on it as soon as upstream will have released the new version.
>
> Sorry,
If you want, you can just use the Ubuntu patch
G.
diff -Nru fpylll-0.5.2+ds1/debian/changelog fpylll-0.5.2+ds1/debian/changelog
--- fpylll-0.5.2+ds1/debian/changelog 2020-10-12 22:44:41.0 +0200
+++ fpylll-0.5.2+ds1/debian/changelog 2020-12-09 12:29:50.0 +0100
@@ -1,3 +1,21 @@
+fpylll (0.5.2+ds1-2ubuntu1) hirsute; urgency=medium
+
+ * Fix ftbfs with fplll. Closes: #976778.
+
+ -- Matthias Klose Wed, 09 Dec 2020 12:29:50 +0100
+
+fpylll (0.5.2+ds1-2build2) hirsute; urgency=medium
+
+ * No-change rebuild to drop python3.8 extensions.
+
+ -- Matthias Klose Mon, 07 Dec 2020 18:23:00 +0100
+
+fpylll (0.5.2+ds1-2build1) hirsute; urgency=medium
+
+ * No-change rebuild for fplll soname change.
+
+ -- Matthias Klose Mon, 07 Dec 2020 17:30:07 +0100
+
fpylll (0.5.2+ds1-2) unstable; urgency=medium
[ Ondřej Nový ]
diff -Nru
fpylll-0.5.2+ds1/debian/patches/ede1e459f0662a0940dca6366aba20d47183a4a0.diff
fpylll-0.5.2+ds1/debian/patches/ede1e459f0662a0940dca6366aba20d47183a4a0.diff
---
fpylll-0.5.2+ds1/debian/patches/ede1e459f0662a0940dca6366aba20d47183a4a0.diff
1970-01-01 01:00:00.0 +0100
+++
fpylll-0.5.2+ds1/debian/patches/ede1e459f0662a0940dca6366aba20d47183a4a0.diff
2020-12-09 12:29:50.0 +0100
@@ -0,0 +1,222 @@
+--- a/setup.py
b/setup.py
+@@ -203,7 +203,6 @@ extensions = [
+ Extension("fpylll.fplll.enumeration",
["src/fpylll/fplll/enumeration.pyx"], fplll=True),
+ Extension("fpylll.fplll.svpcvp", ["src/fpylll/fplll/svpcvp.pyx"],
fplll=True),
+ Extension("fpylll.fplll.pruner", ["src/fpylll/fplll/pruner.pyx"],
fplll=True),
+-Extension("fpylll.fplll.sieve_gauss",
["src/fpylll/fplll/sieve_gauss.pyx"], fplll=True),
+ Extension("fpylll.util", ["src/fpylll/util.pyx"], fplll=True),
+ Extension("fpylll.io", ["src/fpylll/io.pyx"], fplll=True),
+ Extension("fpylll.config", ["src/fpylll/config.pyx"], fplll=True),
+--- a/src/fpylll/__init__.py
b/src/fpylll/__init__.py
+@@ -9,7 +9,6 @@ from .fplll.bkz_param import load_strate
+ from .fplll.svpcvp import SVP
+ from .fplll.svpcvp import CVP
+ from .fplll.pruner import Pruning
+-from .fplll.sieve_gauss import GaussSieve
+ from .util import ReductionError
+ from .util import FPLLL
+ __version__ = "0.5.2dev"
+--- a/src/fpylll/fplll/decl.pxd
b/src/fpylll/fplll/decl.pxd
+@@ -16,7 +16,6 @@ IF HAVE_QD:
+ from .fplll cimport dpe_t
+ from .fplll cimport Z_NR, FP_NR
+ from .fplll cimport ZZ_mat, MatGSOInterface, LLLReduction, BKZAutoAbort,
BKZReduction, Enumeration
+-from .fplll cimport GaussSieve
+ from .fplll cimport Evaluator, FastEvaluator, ErrorBoundedEvaluator,
FastErrorBoundedEvaluator, Pruner
+
+ from libcpp.vector cimport vector
+@@ -83,10 +82,6 @@ ctypedef union zz_mat_core_t:
+ ZZ_mat[mpz_t] *mpz
+ ZZ_mat[long] *long
+
+-ctypedef union gauss_sieve_core_t:
+-GaussSieve[mpz_t, FP_NR[double]] *mpz_d
+-GaussSieve[long, FP_NR[double]] *long_d
+-
+ IF HAVE_LONG_DOUBLE:
+ IF HAVE_QD:
+ # we cannot use a union because of non-trivial constructors
+--- a/src/fpylll/fplll/fplll.pxd
b/src/fpylll/fplll/fplll.pxd
+@@ -943,26 +943,6 @@ cdef extern from "fplll/pruner/pruner.h"
+ FT svp_probability[FT](const vector[double] )
+
+
+-
+-# Sieving
+-
+-cdef extern from "fplll/sieve/sieve_gauss.h" namespace "fplll":
+-cdef cppclass GaussSieve[ZT, FT]:
+-GaussSieve(ZZ_mat[ZT] , int algorithm, bool verbose, int seed)
+-
+-bool sieve(Z_NR[ZT] target_norm)
+-
+-void set_verbose(bool verbose)
+-bool verbose
+-
+-int alg
+-
+-# norms/listsize for all iterations
+-vector[Z_NR[ZT]] iters_norm
+-vector[long] iters_ls
+-
+-NumVect[Z_NR[ZT]] return_first()
+-
+ # Threads
+
+ cdef extern from "fplll/threadpool.h" namespace "fplll":
+--- a/src/fpylll/fplll/sieve_gauss.pxd
/dev/null
+@@ -1,9 +0,0 @@
+-# -*- coding: utf-8 -*-
+-
+-from fpylll.gmp.types cimport mpz_t
+-from .fplll cimport FP_NR, IntType
+-from .decl cimport gauss_sieve_core_t
+-
+-cdef class GaussSieve:
+-cdef IntType _type
+-cdef gauss_sieve_core_t _core
+--- a/src/fpylll/fplll/sieve_gauss.pyx
/dev/null
+@@ -1,137 +0,0 @@
+-# -*- coding: utf-8 -*-
+-"""
+-Gaussian sieving.
+-
+-.. moduleauthor:: Martin R. Albrecht
+-
+-Gaussian Sieving was proposed in Micciancio, D., & Voulgaris, P. (2010).
Faster exponential time
+-algorithms for the shortest vector problem. In M. Charika, 21st SODA (pp.
1468–1480). :
[Python-modules-team] Bug#962194: lintian-brush: autopkgtest failure on s390x
control: forwarded -1 https://sourceforge.net/p/ruamel-yaml/tickets/360/ G. ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#964093: kombu: please drop python3-importlib-metadata dependency
Source: kombu
Version: 4.6.11-2
Severity: normal
tags: patch
From Ubuntu:
kombu (4.6.7-1ubuntu1) focal; urgency=medium
* d/control: Move python3-importlib-metadata to Suggests since
/usr/lib/python3.8/importlib/metadata.py is provided by the Python 3.8
standard library and Python 3.8 will be the default for Ubuntu Focal.
The python3-importlib-metadata dependency can be dropped entirely once
Python 3.8 is the minimum available python version (LP: #1851393).
-- Corey Bryant Mon, 10 Feb 2020 09:18:35 -0500
Can you please apply too?
./requirements/default.txt:importlib-metadata>=0.18; python_version<"3.8"
./extra/requirements/default.txt:importlib-metadata>=0.18; python_version<"3.8"
trivial patch:
diff -Nru kombu-4.6.11/debian/control kombu-4.6.11/debian/control
--- kombu-4.6.11/debian/control 2020-07-01 07:14:18.0 +0200
+++ kombu-4.6.11/debian/control 2020-07-01 18:31:32.0 +0200
@@ -20,7 +20,6 @@
python3-botocore ,
python3-case ,
python3-django ,
- python3-importlib-metadata ,
python3-mock ,
python3-msgpack ,
python3-pymongo ,
@@ -70,7 +69,6 @@
Depends:
python3-amqp (>= 1.4.6),
python3-anyjson (>= 0.3.3),
- python3-importlib-metadata,
${misc:Depends},
${python3:Depends},
Recommends:
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#960899: paramiko: autopkgtests failures
Hello, after trying approach "b" > b) the autopkgtest needs to install recommends too I get some new autopkgtests failures such as: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/p/paramiko/20200518_022340_86e27@/log.gz (they are all new tests) G. ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#960899: paramiko: autopkgtests failures
Source: paramiko Version: 2.7.1-1 Severity: serious Hello, looks like the latest paramiko version is now failing its autopkgtests. Not sure if a) "invoke" should be moved from recommends to depends b) the autopkgtest needs to install recommends too c) something else Processing triggers for libc-bin (2.30-8) ... (Reading database ... 13936 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [19:10:54]: test upstream: [--- = test session starts == platform linux -- Python 3.8.3, pytest-4.6.9, py-1.8.1, pluggy-0.13.0 -- /usr/bin/python3 cachedir: .pytest_cache rootdir: /tmp/autopkgtest-lxc.5uagjxdu/downtmp/build.uH0/src, inifile: setup.cfg collecting ... collected 257 items / 1 errors / 256 selected ERRORS ERROR collecting tests/test_config.py _ ImportError while importing test module '/tmp/autopkgtest-lxc.5uagjxdu/downtmp/build.uH0/src/tests/test_config.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: tests/test_config.py:9: in from invoke import Result E ModuleNotFoundError: No module named 'invoke' !!! Interrupted: 1 errors during collection === 1 error in 0.59 seconds autopkgtest [19:10:55]: test upstream: ---] autopkgtest [19:10:55]: test upstream: - - - - - - - - - - results - - - - - - - - - - upstream FAIL non-zero exit status 2 autopkgtest [19:10:55]: summary cheers, Gianfranco ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#954441: automat: please call python2 in autopkgtests
Source: automat Version: 0.8.0-1 Severity: important Tags: patch Hello, please call python2 instead of python in autopkgtests, the python binary will be removed in the future --- automat-0.8.0/debian/tests/unit-tests-2 2020-03-18 22:47:32.0 +0100 +++ automat-0.8.0/debian/tests/unit-tests-2 2020-03-19 04:12:52.0 +0100 @@ -1,4 +1,4 @@ #!/bin/sh -e cd $AUTOPKGTEST_TMP -python -m twisted.trial automat +python2 -m twisted.trial automat G. ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#917652: pywavelets 0.5.1-1.1: FTBFS, alignment problem
control: severity -1 serious
control: tags -1 patch pending
Patch uploaded in sid, since the current NMU can't migrate due to this bug
G.
On Sat, 29 Dec 2018 19:23:33 + Steve McIntyre wrote:
> Source: pywavelets
> Version: 0.5.1-1.1
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: alignment
>
> Hi!
>
> I've been doing a full rebuild of the Debian archive, building all
> source packages targeting armel and armhf using arm64 hardware. We are
> planning in future to move all of our 32-bit armel/armhf builds to
> using arm64 machines, so this rebuild is to identify packages that
> might have problems with this configuration.
>
> A feature of the arm64 kernel is that it does *not* support fixing up
> code with broken alignment, so code that might have built and run OK
> on our older armel/armhf build machines due to kernel fixups will now
> fail.
>
> When building your package, I've found a bus error (aka alignment
> fault). The full log is online at
>
>
> https://www.einval.com/debian/arm/rebuild-logs/armel/FAIL/pywavelets_0.5.1-1.1_armel.log
>
> for reference
>
> I've done a quick bit of debugging to find the source of the
> bug. Here's a gdb stacktrace and variable printout to demonstrate the
> problem.
>
> (sid-armel)steve@maul:~/debian/build/pywavelets/pywavelets-0.5.1$ gdb
> /usr/bin/python2.7 core
> ...
> Reading symbols from /usr/bin/python2.7...(no debugging symbols found)...done.
> [New LWP 3291]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/arm-linux-gnueabi/libthread_db.so.1".
> Core was generated by `python2.7 -c import sys ; sys.path.insert(0,
> '/home/steve/debian/build/pywavele'.
> Program terminated with signal SIGBUS, Bus error.
> #0 double_downcoef_axis (input=0x1011b90, input_info=..., output=0xfe4500,
> output_info=..., wavelet=0x1161b78, axis=0, coef=COEF_APPROX,
> dwt_mode=MODE_SYMMETRIC, swt_level=0,
> transform=DWT_TRANSFORM) at pywt/_extensions/c/wt.template.c:100
> 100 temp_input[j] = *(TYPE *)(((char *) input) +
> input_offset
> (gdb) list
> 95
> 96 // Copy to temporary input if necessary
> 97 if (make_temp_input)
> 98 for (j = 0; j < input_info.shape[axis]; ++j)
> 99 // Offsets are byte offsets, to need to cast to char
> and back
> 100 temp_input[j] = *(TYPE *)(((char *) input) +
> input_offset
> 101 + j *
> input_info.strides[axis]);
> 102
> 103 // Select temporary or direct output and input
> 104 input_row = make_temp_input ? temp_input
> (gdb) p input
> $1 = (const double * const restrict) 0x1011b90
> (gdb) p input_offset
> $2 =
> (gdb) p j
> $3 =
>
> This is a classic pattern for alignment problems. You can't just cast
diff -Nru pywavelets-0.5.1/debian/changelog pywavelets-0.5.1/debian/changelog
--- pywavelets-0.5.1/debian/changelog 2019-12-13 19:37:57.0 +0100
+++ pywavelets-0.5.1/debian/changelog 2019-12-18 15:36:45.0 +0100
@@ -1,3 +1,11 @@
+pywavelets (0.5.1-1.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Grab patch from Ubuntu and Balint Reczey to fix an aligment problem on
+armhf (Closes: #917652)
+
+ -- Gianfranco Costamagna Wed, 18 Dec 2019
15:36:45 +0100
+
pywavelets (0.5.1-1.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru
pywavelets-0.5.1/debian/patches/03-Explicity-align-data-records-in-test_byte_offset.patch
pywavelets-0.5.1/debian/patches/03-Explicity-align-data-records-in-test_byte_offset.patch
---
pywavelets-0.5.1/debian/patches/03-Explicity-align-data-records-in-test_byte_offset.patch
1970-01-01 01:00:00.0 +0100
+++
pywavelets-0.5.1/debian/patches/03-Explicity-align-data-records-in-test_byte_offset.patch
2019-12-18 15:36:38.0 +0100
@@ -0,0 +1,25 @@
+From a2474a8d81a105c9abe525f5279568322f71a77c Mon Sep 17 00:00:00 2001
+From: Balint Reczey
+Date: Fri, 5 May 2017 11:51:14 +
+Subject: [PATCH] TST: Explicity align data records in test_byte_offset()
+
+Also use dict for dtype definition because list format
+ignores alignment. See https://github.com/numpy/numpy/issues/663
+---
+ pywt/tests/test_multidim.py | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+--- a/pywt/tests/test_multidim.py
b/pywt/tests/test_multidim.py
+@@ -86,8 +86,9 @@
+
+ for mode in pywt.Modes.modes:
+ expected = pywt.dwtn(data, wavelet)
+-padded = np.ones((3, 6), dtype=np.dtype([('data', data.dtype),
+- ('pad', 'byte')]))
++padded = np.ones((3, 6), dtype=np.dtype({'ddata': (data.dtype, 0),
++
[Python-modules-team] Bug#937730: python-apptools is now gone in sid
control: severity -1 serious Hello, python-apptools is now a cruft package, so this bug becomes RC now G. ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#946304: jsonpickle: FTBFS in sid
Source: jsonpickle
Version: 0.9.5-2
Severity: serious
Hello, looks like some Python3 updates made the package FTBFS in sid, due to
testsuite errors...
log following:
I: Running cd /build/jsonpickle-0.9.5/ && env
PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us
-uc -rfakeroot
dpkg-buildpackage: info: source package jsonpickle
dpkg-buildpackage: info: source version 0.9.5-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Sandro Tosi
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.8 setup.py clean
running clean
removing '/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build' (and everything
under it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.8' does not exist -- can't clean it
I: pybuild base:217: python3.7 setup.py clean
running clean
removing '/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build' (and everything
under it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.7' does not exist -- can't clean it
dh_clean -O--buildsystem=pybuild
dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building jsonpickle using existing
./jsonpickle_0.9.5.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building jsonpickle in jsonpickle_0.9.5-2.debian.tar.xz
dpkg-source: info: building jsonpickle in jsonpickle_0.9.5-2.dsc
debian/rules build
dh build --with python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:217: python3.8 setup.py config
running config
I: pybuild base:217: python3.7 setup.py config
running config
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3.8 setup.py build
running build
running build_py
creating /build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/tags.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/handlers.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/unpickler.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/compat.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/pickler.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/version.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/__init__.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/backend.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/util.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
creating /build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle/ext
copying jsonpickle/ext/numpy.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle/ext
copying jsonpickle/ext/__init__.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle/ext
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
running build_py
creating /build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/tags.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/handlers.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/unpickler.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/compat.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/pickler.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/version.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/__init__.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/backend.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/util.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
creating /build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle/ext
copying jsonpickle/ext/numpy.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle/ext
copying jsonpickle/ext/__init__.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle/ext
debian/rules override_dh_auto_test
make[1]: Entering directory '/build/jsonpickle-0.9.5'
PYBUILD_SYSTEM=custom \
PYBUILD_TEST_ARGS="PYTHONPATH={build_dir} {interpreter} tests/runtests.py"
dh_auto_test
I: pybuild base:217:
PYTHONPATH=/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build python3.8
tests/runtests.py
/build/jsonpickle-0.9.5/tests/backend_test.py:103: UserWarning:
[Python-modules-team] Bug#937552: Bug#937552: re: pysvn: Python2 removal in sid/bullseye
On Tue, 26 Nov 2019 17:21:41 + Scott Kitterman wrote: > No need to defer this. Please reschedule it to delay 0. > > Scott K > > Sorry Scott, but for some reasons I did a mistake in my reverse-depends command, I used -b instead of also trying without. reverse-depends -r sid python-svn Reverse-Recommends == * python-rope Reverse-Depends === * rabbitvcs-core * svn-workbench I'm deleting this from deferred for now, until reverse-dependencies are kicked out from testing or fixed G. ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#937552: re: pysvn: Python2 removal in sid/bullseye
Control: tags -1 patch pending
On Sat, 2 Nov 2019 15:47:09 + Peter Green
wrote:
> Severity 937552 serious
> Thanks
>
> pysvn build-depends on the python-cxx-dev binary package, which is no longer
> built by the the python-cxx-dev source package.
>
>
Please find the attached fix to drop the Python2 package, and uploaded in
DEFERRED/15
thanks
Gianfranco
diff -Nru pysvn-1.9.9/debian/changelog pysvn-1.9.9/debian/changelog
--- pysvn-1.9.9/debian/changelog2019-10-31 02:10:08.0 +0100
+++ pysvn-1.9.9/debian/changelog2019-11-26 09:58:21.0 +0100
@@ -1,3 +1,10 @@
+pysvn (1.9.9-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Drop python2 package (Closes: #937552)
+
+ -- Gianfranco Costamagna Tue, 26 Nov 2019
09:58:21 +0100
+
pysvn (1.9.9-2) unstable; urgency=medium
[ Ondřej Nový ]
diff -Nru pysvn-1.9.9/debian/control pysvn-1.9.9/debian/control
--- pysvn-1.9.9/debian/control 2019-10-31 02:10:08.0 +0100
+++ pysvn-1.9.9/debian/control 2019-11-26 09:56:25.0 +0100
@@ -10,10 +10,6 @@
libaprutil1-dev,
libneon27-gnutls-dev,
libsvn-dev (>= 1.8.10),
- python-all-dbg,
- python-all-dev (>= 2.7.8),
- python-cxx-dev (>= 7.0.1),
- python-setuptools,
python3-all (>= 3.4.2),
python3-all-dev (>= 3.4.2),
python3-setuptools (>= 5.5.1),
@@ -26,15 +22,6 @@
Vcs-Git: https://salsa.debian.org/python-team/modules/pysvn.git
Vcs-Browser: https://salsa.debian.org/python-team/modules/pysvn
-Package: python-svn
-Architecture: any
-Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
-Provides: python-pysvn
-Description: A(nother) Python interface to Subversion
- The pysvn module is a Python interface to the Subversion version
- control system. This API exposes client interfaces for managing a
- working copy, querying a repository, and synchronizing the two.
-
Package: python3-svn
Architecture: any
Depends: ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends}
diff -Nru pysvn-1.9.9/debian/python-svn.dirs pysvn-1.9.9/debian/python-svn.dirs
--- pysvn-1.9.9/debian/python-svn.dirs 2019-10-31 02:10:08.0 +0100
+++ pysvn-1.9.9/debian/python-svn.dirs 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/python2.7/dist-packages/pysvn
diff -Nru pysvn-1.9.9/debian/python-svn.doc-base
pysvn-1.9.9/debian/python-svn.doc-base
--- pysvn-1.9.9/debian/python-svn.doc-base 2019-10-31 02:10:08.0
+0100
+++ pysvn-1.9.9/debian/python-svn.doc-base 1970-01-01 01:00:00.0
+0100
@@ -1,12 +0,0 @@
-Document: pysvn
-Title: pysvn - Python interface to Subversion
-Author: Barry A. Scott
-Abstract: This document contains the pysvn Programmer's Guide (covering the
- use of pysvn in a tutorial style with lots of examples) and the pysvn
- Programmer's Reference (detailed descriptions of all the classes, functions
- and variables of pysvn).
-Section: Programming/Python
-
-Format: HTML
-Index: /usr/share/doc/python-svn/pysvn.html
-Files: /usr/share/doc/python-svn/*.html
diff -Nru pysvn-1.9.9/debian/python-svn.docs pysvn-1.9.9/debian/python-svn.docs
--- pysvn-1.9.9/debian/python-svn.docs 2019-10-31 02:10:08.0 +0100
+++ pysvn-1.9.9/debian/python-svn.docs 1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-Docs/*.html
-Docs/*.js
diff -Nru pysvn-1.9.9/debian/python-svn.examples
pysvn-1.9.9/debian/python-svn.examples
--- pysvn-1.9.9/debian/python-svn.examples 2019-10-31 02:10:08.0
+0100
+++ pysvn-1.9.9/debian/python-svn.examples 1970-01-01 01:00:00.0
+0100
@@ -1 +0,0 @@
-Examples/*
diff -Nru pysvn-1.9.9/debian/python-svn.install
pysvn-1.9.9/debian/python-svn.install
--- pysvn-1.9.9/debian/python-svn.install 2019-10-31 02:10:08.0
+0100
+++ pysvn-1.9.9/debian/python-svn.install 1970-01-01 01:00:00.0
+0100
@@ -1,2 +0,0 @@
-Source/pysvn/python2/__init__.py usr/lib/python2.7/dist-packages/pysvn/
-Source/pysvn/python2/_pysvn_2_7.so usr/lib/python2.7/dist-packages/pysvn/
diff -Nru pysvn-1.9.9/debian/rules pysvn-1.9.9/debian/rules
--- pysvn-1.9.9/debian/rules2019-10-31 02:10:08.0 +0100
+++ pysvn-1.9.9/debian/rules2019-11-26 09:58:21.0 +0100
@@ -8,27 +8,13 @@
DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
-PYVERS := $(shell pyversions -vr debian/control)
PY3VERS := $(shell py3versions -vr debian/control)
APR_INC= $(strip $(shell apr-config --includes | sed 's/-I//'))
-
-CONFIG_OPTS = --pycxx-src-dir=/usr/share/python${PYVERS}/CXX \
- --pycxx-dir=/usr/include/python${PYVERS} \
- --svn-lib-dir=/usr/lib/$(DEB_HOST_MULTIARCH) \
- --apr-inc-dir=$(APR_INC) \
- --apu-inc-dir=$(APR_INC) \
- --apr-lib-dir=/usr/lib/$(DEB_HOST_MULTIARCH) \
- --norpath \
- --platform=$(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
-
-
%:
- dh $@ --with=python2,python3 --buildsystem=pybuild
+
[Python-modules-team] Bug#945202: pytest-pylint: FTBFS in sid
Source: pytest-pylint Version: 0.14.1-2 Severity: serious Hello, your packages FTBFS with default Python3.8 in sid Can you please have a look? I: Running cd /build/pytest-pylint-0.14.1/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us -uc dpkg-buildpackage: info: source package pytest-pylint dpkg-buildpackage: info: source version 0.14.1-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Ond??ej Kobli??ek dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 dpkg-source: info: using options from pytest-pylint-0.14.1/debian/source/options: --extend-diff-ignore=^[^/]*[.]egg-info/ debian/rules clean dh clean --with python3 --buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild I: pybuild base:217: python3.8 setup.py clean running clean removing '/build/pytest-pylint-0.14.1/.pybuild/cpython3_3.8_pytest-pylint/build' (and everything under it) 'build/bdist.linux-amd64' does not exist -- can't clean it 'build/scripts-3.8' does not exist -- can't clean it I: pybuild base:217: python3.7 setup.py clean running clean removing '/build/pytest-pylint-0.14.1/.pybuild/cpython3_3.7_pytest-pylint/build' (and everything under it) 'build/bdist.linux-amd64' does not exist -- can't clean it 'build/scripts-3.7' does not exist -- can't clean it dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild dpkg-source -b . dpkg-source: info: using options from pytest-pylint-0.14.1/debian/source/options: --extend-diff-ignore=^[^/]*[.]egg-info/ dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building pytest-pylint using existing ./pytest-pylint_0.14.1.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: building pytest-pylint in pytest-pylint_0.14.1-2.debian.tar.xz dpkg-source: info: building pytest-pylint in pytest-pylint_0.14.1-2.dsc debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:217: python3.8 setup.py config running config I: pybuild base:217: python3.7 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:217: /usr/bin/python3.8 setup.py build running build running build_py copying pytest_pylint.py -> /build/pytest-pylint-0.14.1/.pybuild/cpython3_3.8_pytest-pylint/build I: pybuild base:217: /usr/bin/python3 setup.py build running build running build_py copying pytest_pylint.py -> /build/pytest-pylint-0.14.1/.pybuild/cpython3_3.7_pytest-pylint/build create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild debian/rules override_dh_auto_install make[1]: Entering directory '/build/pytest-pylint-0.14.1' dh_auto_install I: pybuild base:217: /usr/bin/python3.8 setup.py install --root /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint running install running build running build_py running install_lib creating /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr creating /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib creating /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.8 creating /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.8/dist-packages copying /build/pytest-pylint-0.14.1/.pybuild/cpython3_3.8_pytest-pylint/build/pytest_pylint.py -> /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.8/dist-packages byte-compiling /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.8/dist-packages/pytest_pylint.py to pytest_pylint.cpython-38.pyc running install_egg_info running egg_info creating pytest_pylint.egg-info writing pytest_pylint.egg-info/PKG-INFO writing dependency_links to pytest_pylint.egg-info/dependency_links.txt writing entry points to pytest_pylint.egg-info/entry_points.txt writing requirements to pytest_pylint.egg-info/requires.txt writing top-level names to pytest_pylint.egg-info/top_level.txt writing manifest file 'pytest_pylint.egg-info/SOURCES.txt' reading manifest file 'pytest_pylint.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'pytest_pylint.egg-info/SOURCES.txt' Copying pytest_pylint.egg-info to /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.8/dist-packages/pytest_pylint-0.14.0.egg-info Skipping SOURCES.txt running install_scripts I: pybuild base:217: /usr/bin/python3 setup.py install --root /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint running install running build running build_py running install_lib creating /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.7 creating /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.7/dist-packages copying
[Python-modules-team] Bug#944664: Bug#944664: pymodbus: please update to new 2.3.0 stable version
On Wed, 13 Nov 2019 18:07:03 -0300 Emmanuel Arias wrote: > Hi, > > I am trying to package v2.3.0 but we need upload python3-m2r to unstable. > > Pymodbus depends of m2r (2.3.0 and 2.2.0 too) for documentation. > > We should submit a bugs for m2r upload? > Hello, just to make sure you are aware... You might do an experimental upload if that one is the only missing dependency, so at least we can help in testing it? G. > Cheers, > Arias Emmanuel > @eamanu > http://eamanu.com > > El mi??., 13 de nov. de 2019 a la(s) 11:39, Gianfranco Costamagna > (locutusofb...@debian.org) escribi??: > > > > Source: pymodbus > > Version: 2.1.0+dfsg-2 > > Severity: normal > > > > Hello, can you please package 2.3.0 that is now stable? > > I personally need the new "register" feature of ModbusTcpClient class added > > probably in 2.2.0 > > > > thanks for maintaining it! > > > > Gianfranco > > > > ___ > > Python-modules-team mailing list > > Python-modules-team@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team > > ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#944664: pymodbus: please update to new 2.3.0 stable version
Source: pymodbus Version: 2.1.0+dfsg-2 Severity: normal Hello, can you please package 2.3.0 that is now stable? I personally need the new "register" feature of ModbusTcpClient class added probably in 2.2.0 thanks for maintaining it! Gianfranco ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#937120: nbsphinx: Python2 removal in sid/bullseye
control: fixed -1 0.4.2+ds-3 control: close -1 The latest upload closed an already closed bug :) G. On Fri, 30 Aug 2019 07:27:58 + Matthias Klose wrote: > Package: src:nbsphinx > Version: 0.4.2+ds-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > Your package either build-depends, depends on Python2, or uses Python2 > in the autopkg tests. Please stop using Python2, and fix this issue > by one of the following actions. > > - Convert your Package to Python3. This is the preferred option. In > case you are providing a Python module foo, please consider dropping > the python-foo package, and only build a python3-foo package. Please > don't drop Python2 modules, which still have reverse dependencies, > just document them. > > This is the preferred option. > > - If the package is dead upstream, cannot be converted or maintained > in Debian, it should be removed from the distribution. If the > package still has reverse dependencies, raise the severity to > "serious" and document the reverse dependencies with the BTS affects > command. If the package has no reverse dependencies, confirm that > the package can be removed, reassign this issue to ftp.debian.org, > make sure that the bug priority is set to normal and retitle the > issue to "RM: PKG -- removal triggered by the Python2 removal". > > - If the package has still many users (popcon >= 300), or is needed to > build another package which cannot be removed, document that by > adding the "py2keep" user tag (not replacing the py2remove tag), > using the debian-pyt...@lists.debian.org user. Also any > dependencies on an unversioned python package (python, python-dev) > must not be used, same with the python shebang. These have to be > replaced by python2/python2.7 dependencies and shebang. > > This is the least preferred option. > > If the conversion or removal needs action on another package first, > please document the blocking by using the BTS affects command, like > > affects + src:nbsphinx > > If there is no py2removal bug for that reverse-dependency, please file > a bug on this package (similar to this bug report). > > If there are questions, please refer to the wiki page for the removal: > https://wiki.debian.org/Python/2Removal, or ask for help on IRC > #debian-python, or the debian-pyt...@lists.debian.org mailing list. > > ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#939492: nbsphinx: testsuite failures with new pandoc
control: forwarded -1 https://github.com/spatialaudio/nbsphinx/issues/317 ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#939492: nbsphinx: testsuite failures with new pandoc
Source: nbsphinx Version: 0.4.2+ds-1 Severity: serious Hello, looks like the package is not able anymore to include svg into the pdf files... Look to the testsuite https://ci.debian.net/packages/n/nbsphinx/ This might be due to a regression/change in pandoc. cheers, Gianfranco ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#794866: webhelpers: plese override json evil lintian error
in deferred/10 G. diff -Nru webhelpers-1.3/debian/changelog webhelpers-1.3/debian/changelog --- webhelpers-1.3/debian/changelog 2012-07-08 22:27:47.0 +0200 +++ webhelpers-1.3/debian/changelog 2019-08-02 12:59:29.0 +0200 @@ -1,3 +1,10 @@ +webhelpers (1.3-4.1) unstable; urgency=medium + + * Non-maintainer upload + * Override json evil lintian error (Closes: #794866) + + -- Gianfranco Costamagna Fri, 02 Aug 2019 12:59:29 +0200 + webhelpers (1.3-4) unstable; urgency=low * Remove WebHelpers.egg-info in clean target (to make it build twice in a diff -Nru webhelpers-1.3/debian/source/lintian-overrides webhelpers-1.3/debian/source/lintian-overrides --- webhelpers-1.3/debian/source/lintian-overrides 1970-01-01 01:00:00.0 +0100 +++ webhelpers-1.3/debian/source/lintian-overrides 2019-08-02 12:59:27.0 +0200 @@ -0,0 +1 @@ +webhelpers source: license-problem-json-evil webhelpers/pylonslib/_jsmin.py ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#906400: pytest-qt: FTBFS in buster/sid (failing tests)
control: tags -1 patch pending.
Patch following:
diff -Nru pytest-qt-2.3.1/debian/changelog pytest-qt-2.3.1/debian/changelog
--- pytest-qt-2.3.1/debian/changelog2018-02-15 22:03:31.0 +0100
+++ pytest-qt-2.3.1/debian/changelog2018-09-27 12:40:39.0 +0200
@@ -1,3 +1,12 @@
+pytest-qt (2.3.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ [ Dmitry Shachnev ]
+ * Adapt for QTest.mouseEvent removing in PyQt v5.11.
+(Closes: #906400)
+
+ -- Gianfranco Costamagna Thu, 27 Sep 2018
12:40:39 +0200
+
pytest-qt (2.3.1-1) unstable; urgency=medium
[ Ondřej Nový ]
diff -Nru pytest-qt-2.3.1/debian/patches/Remove-mouseEvent-proxy-method.patch
pytest-qt-2.3.1/debian/patches/Remove-mouseEvent-proxy-method.patch
--- pytest-qt-2.3.1/debian/patches/Remove-mouseEvent-proxy-method.patch
1970-01-01 01:00:00.0 +0100
+++ pytest-qt-2.3.1/debian/patches/Remove-mouseEvent-proxy-method.patch
2018-09-27 12:40:36.0 +0200
@@ -0,0 +1,45 @@
+From: Dmitry Shachnev
+Date: Thu, 12 Jul 2018 15:59:53 +0300
+Subject: Remove mouseEvent proxy method
+
+QTest::mouseEvent is an internal Qt function, and it was removed in
+PyQt v5.11 which is causing test failures.
+
+Forwarded: https://github.com/pytest-dev/pytest-qt/pull/219
+---
+ pytestqt/qtbot.py | 2 --
+ tests/test_qtest_proxies.py | 1 -
+ 2 files changed, 3 deletions(-)
+
+diff --git a/pytestqt/qtbot.py b/pytestqt/qtbot.py
+index 7333f93..080dbc6 100644
+--- a/pytestqt/qtbot.py
b/pytestqt/qtbot.py
+@@ -96,7 +96,6 @@ class QtBot(object):
+
+ .. staticmethod:: mouseClick (widget, button[, stateKey=0[,
pos=QPoint()[, delay=-1]]])
+ .. staticmethod:: mouseDClick (widget, button[, stateKey=0[,
pos=QPoint()[, delay=-1]]])
+-.. staticmethod:: mouseEvent (action, widget, button, stateKey, pos[,
delay=-1])
+ .. staticmethod:: mouseMove (widget[, pos=QPoint()[, delay=-1]])
+ .. staticmethod:: mousePress (widget, button[, stateKey=0[,
pos=QPoint()[, delay=-1]]])
+ .. staticmethod:: mouseRelease (widget, button[, stateKey=0[,
pos=QPoint()[, delay=-1]]])
+@@ -549,7 +548,6 @@ class QtBot(object):
+
+ 'mouseClick',
+ 'mouseDClick',
+-'mouseEvent',
+ 'mouseMove',
+ 'mousePress',
+ 'mouseRelease',
+diff --git a/tests/test_qtest_proxies.py b/tests/test_qtest_proxies.py
+index 715f20f..980841f 100644
+--- a/tests/test_qtest_proxies.py
b/tests/test_qtest_proxies.py
+@@ -18,7 +18,6 @@ fails_on_pyqt = pytest.mark.xfail('not
qt_api.pytest_qt_api.startswith("pyside")
+
+ 'mouseClick',
+ 'mouseDClick',
+-'mouseEvent',
+ 'mouseMove',
+ 'mousePress',
+ 'mouseRelease',
diff -Nru pytest-qt-2.3.1/debian/patches/series
pytest-qt-2.3.1/debian/patches/series
--- pytest-qt-2.3.1/debian/patches/series 2018-02-15 22:03:31.0
+0100
+++ pytest-qt-2.3.1/debian/patches/series 2018-09-27 12:40:36.0
+0200
@@ -1 +1,2 @@
Skip-tests-requiring-a-window-manager.patch
+Remove-mouseEvent-proxy-method.patch
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#886291: Debian package transition: Rename package and reuse old name with new content
>I'm not sure of the transition policies when handling transitions on >testing and unstable only (ie: not involving stable). >But that should ensure there is no breakage between package in the archive. if you are just renaming a package,, and the reverse-deps are not too many, better avoid transitional packages, ask for a transition slot on release.d.o, open bugs (MBF?) with patches, and raise to serious once RT acks the transition. G. ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
