Bug#983702: voltron: Update package with new upstream release

2021-03-21 Thread Thomas Nyberg
m patch On Sun, Feb 28, 2021 at 05:52:23PM +0100, Thomas Nyberg wrote: The reason seems to be that the debian testing packaged version of werkzeug is 1.0.1 while the packaged version of voltran does not support it. There is a commit in the upstream repo that solves this problem: https://g

Bug#983702: voltron: Update package with new upstream release

2021-02-28 Thread Thomas Nyberg
Package: voltron Version: 0.1.7+git20200109-1 Severity: grave Justification: renders package unusable Dear Maintainer, Trying to use the packaged voltron version with the current debian testing does not work. Trying to use e.g. `import voltron` or putting `source /usr/lib/python3/dist-

Bug#854099: cinnamon: Date and Time Settings --> Network Time fails (silently) without installing ntp

2017-02-03 Thread Thomas Nyberg
Package: cinnamon Version: 2.2.16-5 Severity: normal Dear Maintainer, * What led up to the situation? My clock was displaying the wrong time. * What exactly did you do (or not do) that was effective (or ineffective)? First I set the Date and Time Settings to use Network Time, but it

Bug#852867: icedove: debuild fails because mozilla build system requires SHELL env var set

2017-01-27 Thread Thomas Nyberg
Package: icedove Version: 1:45.6.0-1~deb8u1 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) Dear Maintainer, * What led up to the situation? I tried building the package to investigate some segfaults, but was unable to build it with

Bug#837187: This is not a bug with debian

2017-01-10 Thread Thomas Nyberg
I ran into this problem again and this time found the following bug report against cpython: https://bugs.python.org/issue24875 That is exactly this issue. I just wanted to update the bug report. Cheers, Thomas

Bug#837187: python3-venv: Using --system-site-packages causes wrong `pip` to be used

2016-09-09 Thread Thomas Nyberg
Package: python3-venv Version: 3.4.2-2 Severity: important Dear Maintainer, I'm trying to mimic the behavior of --system-site-packages in python2's virtualenv package in python3's venv package. The following should demonstrate the problem: $ python2 -m virtualenv --system-site-packages venv2