Bug#1024695: Merge request
Hello, At least a few of the warnings will be fixed by this merge request: https://salsa.debian.org/emacsen-team/debian-el/-/merge_requests/6 Can we consider merging it? Thanks! Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6
Bug#994666: RFS: python-mockito/1.2.2-2 -- Spying framework for Python - documentation
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-mockito". It has already been uploaded with binary packages to unstable. To reach testing (bookworm), it needs this source-only upload, which is why I need a sponsor. * Package name: python-mockito Version : 1.2.2-2 Upstream Author : https://github.com/kaste/mockito-python/issues * URL : https://github.com/kaste/mockito-python * License : Expat * Vcs : https://salsa.debian.org/python-team/packages/python-mockito Section : python It builds those binary packages: python-mockito-doc - Spying framework for Python - documentation python3-mockito - Spying framework for Python To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-mockito/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-mockito/python-mockito_1.2.2-2.dsc Changes since the last upload: python-mockito (1.2.2-2) unstable; urgency=medium . * Source-only upload. Thanks in advance! Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6
Bug#989486: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x
Nilesh Patra writes: > * The pristine tar contained .tar.gz.*, it should > instead contain .orig.tar.gz for origtargz both for the sake of > consistency and for origtargz to run fine Oops, OK, I have just re-run pristine-tar on the .orig file and committed. > * We are in freeze time, and a new version upload unless absolutely > necessary isn't appropriate[2]. This package does not seem to have any > (RC) bug or affecting any package that a version bump would be > desired. > > Hence, this should be uploaded after bullseye release. Feel free to > ping me then, and I'll happily sponsor. Also, please take a look at my > commits in salsa. > > [2]: https://release.debian.org/testing/freeze_policy.html I'm fine with waiting. After the freeze, I think it will be ready for uploading (I don't want to spam mentors.d.o during the freeze). Thanks a lot for your help! Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6
Bug#989581:
Tags: patch I humbly propose this change: >From 4de312af857234e20b5e01b5b2fa61fa50496995 Mon Sep 17 00:00:00 2001 From: Fabrice Bauzac Date: Tue, 8 Jun 2021 00:00:38 +0200 Subject: [PATCH] autopkgtest: mark ADTTMP as obsolete, replaced with AUTOPKGTEST_TMP Closes: #989581. --- autopkgtest.md | 19 ++- debian/changelog | 4 2 files changed, 14 insertions(+), 9 deletions(-) diff --git a/autopkgtest.md b/autopkgtest.md index c984a23..1480ba7 100644 --- a/autopkgtest.md +++ b/autopkgtest.md @@ -30,10 +30,11 @@ If the file to be executed has no execute bits set, `chmod a+x` is applied to it (this means that tests can be added in patches without the need for additional chmod; contrast this with debian/rules). -During execution of the test, the environment variable `$ADTTMP` will +During execution of the test, the environment variable +`$AUTOPKGTEST_TMP` (previously named `$ADTTMP`, now obsolete) will point to a directory for the execution of this particular test, which -starts empty and will be deleted afterwards (so there is no need for the -test to clean up files left there). +starts empty and will be deleted afterwards (so there is no need for +the test to clean up files left there). If tests want to create artifacts which are useful to attach to test results, such as additional log files or screenshots, they can put them @@ -166,13 +167,13 @@ Defined restrictions running the tests. However, the tests are *not* entitled to assume that the source package's build dependencies will be installed when the test is run. - Please use this considerately, as for large builds it unnecessarily builds - the entire project when you only need a tiny subset (like the tests/ + Please use this considerately, as for large builds it unnecessarily builds the + entire project when you only need a tiny subset (like the tests/ subdirectory). It is often possible to run `make -C tests` instead, or copy - the test code to `$ADTTMP` and build it there with some custom commands. This - cuts down the load on the Continuous Integration servers and also makes tests - more robust as it prevents accidentally running them against the built source - tree instead of the installed packages. + the test code to `$AUTOPKGTEST_TMP` and build it there with some custom + commands. This cuts down the load on the Continuous Integration servers and + also makes tests more robust as it prevents accidentally running them against + the built source tree instead of the installed packages. - **allow-stderr** diff --git a/debian/changelog b/debian/changelog index c4cc189..426a931 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,9 +1,13 @@ debian-policy (4.5.1.1) UNRELEASED; urgency=medium + [ Sean Whitton ] * 4.4: Fix changelog format: needs an extra space before sign-off (Closes: #976301). Thanks to Anatoli Babenia for reporting the problem. + [ Fabrice Bauzac-Stehly ] + * autopkgtest: mark ADTTMP as obsolete, replaced with AUTOPKGTEST_TMP. +Closes: #989581. -- Sean Whitton Tue, 19 Jan 2021 13:47:45 -0700 -- 2.30.2
Bug#989486: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-click-log": * Package name: python-click-log Version : 0.3.2-1 Upstream Author : [fill in name and email of upstream] * URL : https://github.com/click-contrib/click-log * License : Expat * Vcs : https://salsa.debian.org/python-team/packages/python-click-log Section : python It builds those binary packages: python3-click-log - Logging integration for Click - Python 3.x To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-click-log/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-click-log/python-click-log_0.3.2-1.dsc Changes since the last upload: python-click-log (0.3.2-1) unstable; urgency=medium . [ Debian Janitor ] * Bump debhelper from old 10 to 12. * Set upstream metadata fields: Bug-Database, Repository, Repository- Browse. * Remove constraints unnecessary since stretch: + Build-Depends: Drop versioned constraint on dh-python. . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Fabrice Bauzac-Stehly ] * New upstream release. * Upgrade d/watch to version 4. * Upgrade the Standards-Version to 4.5.1. * Declare Rules-Requires-Root: no. Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6
Bug#987264: git-el: fails to install with xemacs21
For what it's worth, here's a patch for git-el to have the directory created, after Agustin's suggestion. diff -Naur git-2.30.2/debian/git-el.dirs git_2.30.2-1.1/debian/git-el.dirs --- git-2.30.2/debian/git-el.dirs 1970-01-01 01:00:00.0 +0100 +++ git_2.30.2-1.1/debian/git-el.dirs 2021-05-22 23:52:16.409330369 +0200 @@ -0,0 +1 @@ +usr/share/emacs/site-lisp
Bug#793675: hplip-gui: No system tray detected
Hello, "Richard B. Kreckel" writes: > Running version 3.21.2+dfsg1-2 of package hplip-gui, the annoying > message still pops up after each login. Version 3.21.2+dfsg1-2 does not contain the change to /etc/xdg/autostart/hplip-systray.desktop, so I expect that you get the annoying message. The fixed version is 3.21.2+dfsg1-2+exp0. > I have checked that /etc/xdg/autostart/hplip-systray.desktop indeed > contains the line saying NoShowIn=GNOME; Have you modified it manually? > It does not seem to suppress the popup. There is no other > "hplip-systray.desktop". I wonder if anybody has tried if this works? > If so, please speak up. I use GNOME and I can confirm that the fix works for me: 3.21.2+dfsg1-2 shows the popup, 3.21.2+dfsg1-2+exp0 does not. The change only fixes GNOME users; if you use a different desktop environment, it will do nothing for you. Do you use GNOME? Cinnamon? Any other derivatives? KDE?... Thanks. Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6 old PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#793675: hplip-gui: No system tray detected
This affects a number of operating system packages of hplip. See this upstream bug: https://bugs.launchpad.net/hplip/+bug/1714659 Concerning the idea of forcing a dependency on sni-qt, it looks like this package does not exist (anymore?). Concerning the need to add a "sleep" before starting hp-systray, this is not useful anymore as the program now does this sleep (for up to 60 seconds), waiting for a system tray to be available. About the idea of installing gnome-shell-extension-top-icons-plus, I can confirm that it does not solve the issue for my GNOME environment. To summarize, hplip provides several tools, among which there is hp-systray which handles a system tray functionality. However, system trays are now replaced with "Notifications" in GNOME, and the system tray functionality is simply absent nowadays in GNOME. The message from GNOME is that applications should stop relying on this (old) way of doing things. I'm not sure what functionality the hp-systray provides, but if it makes sense the hplip team would have to create a new tool based on "Notifications" that would provide the same functionality. I doubt we can remove hp-systray; it may be useful for users of desktop environments other than GNOME that still have a system tray. To fix this issue which, as far as I know, only hit GNOME users, I suggest to add this line to /etc/xdg/autostart/hplip-systray.desktop: NotShowIn=GNOME; So that the issue stops annoying GNOME users. -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6 old PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#985449: python2 virtualenv pip install: can't find '__main__' module in .../pep517/_in_process.py
Package: python3-virtualenv Version: 20.4.0+ds-1 Hello, Installing a PEP-517-compliant package within a Python2 virtualenv fails on bullseye. On buster, it works. With Python3, it works. I'm not sure whether this bug comes from python3-virtualenv or python or something else... Assigning to python3-virtualenv for starting the investigation. The error message is: Processing /tmp/test Installing build dependencies ... done Getting requirements to build wheel ... error ERROR: Command errored out with exit status 1: command: /tmp/tmp.OUKYNjB68J/bin/python /usr/share/python-wheels/pep517-0.9.1-py2.py3-none-any.whl/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmpctQDX6 cwd: /tmp/pip-req-build-mhIcBE Complete output (1 lines): /tmp/tmp.OUKYNjB68J/bin/python: can't find '__main__' module in '/usr/share/python-wheels/pep517-0.9.1-py2.py3-none-any.whl/pep517/_in_process.py' ERROR: Command errored out with exit status 1: /tmp/tmp.OUKYNjB68J/bin/python /usr/share/python-wheels/pep517-0.9.1-py2.py3-none-any.whl/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmpctQDX6 Check the logs for full command output. See the attached tarball for reproducing the issue. test.tar.gz Description: Tarball to reproduce the issue -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6 old PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#985236: RFS: python-mockito/1.2.2-1 [ITP] -- Spying framework for Python
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-mockito": * Package name: python-mockito Version : 1.2.2-1 Upstream Author : https://github.com/kaste/mockito-python/issues * URL : https://github.com/kaste/mockito-python * License : Expat * Vcs : https://salsa.debian.org/python-team/packages/python-mockito Section : python It builds these binary packages: python3-mockito - Spying framework for Python python-mockito-doc - Spying framework for Python - documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-mockito/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-mockito/python-mockito_1.2.2-1.dsc Changes since the last upload: python-mockito (1.2.2-1) unstable; urgency=low . * Initial release. Closes: #981067 Thanks! Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6 old PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#983705: RFS: python-mockito/1.2.2-1 [ITP] -- Spying framework for Python - documentation
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-mockito": * Package name: python-mockito Version : 1.2.2-1 Upstream Author : https://github.com/kaste/mockito-python/issues * URL : https://github.com/kaste/mockito-python * License : Expat * Vcs : https://salsa.debian.org/python-team/packages/python-mockito Section : python It builds those binary packages: python-mockito-doc - Spying framework for Python - documentation python3-mockito - Spying framework for Python To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-mockito/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-mockito/python-mockito_1.2.2-1.dsc Changes since the last upload: python-mockito (1.2.2-1) unstable; urgency=low . * Initial release. Closes: #981067 Best regards -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6 old PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#981067: ITP: python-mockito -- Spying framework for Python
Package: wnpp Owner: Fabrice BAUZAC-STEHLY Severity: wishlist * Package name: python-mockito Version : 1.2.2 Upstream Author : Szczepan Faber, Serhiy Oplakanets, Herr Kaste, Justin Hopper * URL or Web page : https://github.com/kaste/mockito-python * License : Expat Description : Spying framework for Python -- Fabrice Bauzac-Stehly PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6 old PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#971289: beaker: Switch to python3-pycryptodome
I think there are several issues: The first issue is the mere presence of tests. The source package has code to run the upstream tests (via "nose"); that is precisely one of the reasons for the Build-Depends on python3-crypto. However, these tests are not run (anymore) because upstream now strips the "tests/" subdirectory from their PyPI tarball. We should instead use the github tarball, which contains the tests: see merge request [1]. The alternative would be to give up trying to run tests, in which case we could already remove the test dependencies including the one on python3-crypto, fixing this bug. But it is preferable to continue running the tests and ensure the quality of the package. Then, to fix the current bug, we should migrate to python3-pycryptodome instead of using python3-crypto. Here is some context and information: The http://www.pycryptodome.org/ project is a fork of venerable PyCrypto (which provides "import Crypto"). pycryptodome.org provides two PyPI packages: cryptodome and cryptodomex. - cryptodome is a drop-in replacement for PyCrypto: it also provides "import Crypto". However, this also means that it cannot be installed at the same time as PyCrypto. - cryptodomex is a "clean" alternative to PyCrypto: it provides the same features but as "import Cryptodome", so it can be installed side-by-side with PyCrypto. The beaker upstream uses cryptodome, but there is no Debian package for that. There is only Debian package python3-pycryptodome, which provides cryptodomex. So there is some work involved to make a patch so that beaker switches to using "import Cryptodome" instead of "import Crypto". I propose this merge request [2]. [1] https://salsa.debian.org/python-team/packages/beaker/-/merge_requests/1 [2] https://salsa.debian.org/python-team/packages/beaker/-/merge_requests/2
Bug#975465: RFS: python-opentracing/2.4.0-1 -- opentracing interface for Python - documentation
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-opentracing": * Package name: python-opentracing Version : 2.4.0-1 Upstream Author : opentrac...@googlegroups.com * URL : https://github.com/opentracing/opentracing-python * License : Apache-2.0, Expat * Vcs : https://salsa.debian.org/python-team/packages/python-opentracing Section : python It builds those binary packages: python-opentracing-doc - opentracing interface for Python - documentation python3-opentracing - opentracing interface for Python To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-opentracing/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-opentracing/python-opentracing_2.4.0-1.dsc Changes since the last upload: python-opentracing (2.4.0-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Fabrice BAUZAC ] * Switch to debhelper 13. * New upstream version 2.4.0. * Disable the tests of the gevent scope manager until #974051 is fixed. Best regards -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#974051: Checking for upstream fixed for #974051
t;/home/noon/git/python-gevent-20.9.0/deps/c-ares" && if [ -r ares_build.h ];
then cp ares_build.h ares_build.h.orig; fi && sh ./configure
--disable-dependency-tracking -C CFLAGS="-Wno-unused-result -Wsign-compare -g
-Og -Wall -g -Og -fstack-protector-strong -Wformat -Werror=format-security
-g -Og -fstack-protector-strong -Wformat -Werror=format-security -g -O2
-fdebug-prefix-map=/home/noon/git/python-gevent-20.9.0=.
-fstack-protector-strong -Wformat -Werror=format-security" && cp ares_config.h
ares_build.h "$OLDPWD" && cat ares_build.h && if [ -r ares_build.h.orig ];
then mv ares_build.h.orig ares_build.h; fi) > configure-output.txt' returned
non-zero exit status 1.
E: pybuild pybuild:353: build: plugin distutils failed with: exit code=1:
/usr/bin/python3-dbg setup.py build
dh_auto_build: error: pybuild --build -i python{version}-dbg -p "3.9 3.8"
returned exit code 13
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 13
Thanks!
Best regards
--
Fabrice BAUZAC-STEHLY
PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#973162: Cannot reproduce the 8 failures
I can reproduce the SEGV, but not the 8 failures. Was it transient?
Bug#973162: Info received (python-opentracing: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)
I have investigated the SEGV issue and it is not specific to python-opentracing. I have created a specific bugreport for it: 974051 https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=yes=974051 -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#973162: python-opentracing: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Tags: confirmed dh_auto_test -O--buildsystem=pybuild I: pybuild base:232: cd /build/python-opentracing-2.3.0/.pybuild/cpython3_3.9_opentracing/build; python3.9 -m pytest tests = test session starts == platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0 rootdir: /build/python-opentracing-2.3.0 collected 122 items tests/mocktracer/test_tracer.py .. [ 65%] tests/scope_managers/test_asyncio.py . [ 72%] tests/scope_managers/test_contextvars.py . [ 80%] tests/scope_managers/test_gevent.py Segmentation fault E: pybuild pybuild:353: test: plugin distutils failed with: exit code=139: cd /build/python-opentracing-2.3.0/.pybuild/cpython3_3.9_opentracing/build; python3.9 -m pytest tests I can see two issues to fix: - The 8 test failures in test_asyncio.py - The segmentation fault in test_gevent.py -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#953333: RFS: python-opentracing/2.3.0-1 [ITP] -- opentracing interface for Python
Note that 2.2.0-1 is still in the NEW queue: https://ftp-master.debian.org/new/python-opentracing_2.2.0-1.html
Bug#953333: RFS: python-opentracing/2.3.0-1 -- opentracing interface for Python
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-opentracing" * Package name: python-opentracing Version : 2.3.0-1 Upstream Author : The OpenTracing Authors. * URL : https://github.com/opentracing/opentracing-python * License : Expat and Apache-2.0 * Vcs : https://salsa.debian.org/python-team/modules/python-opentracing Section : python It builds those binary packages: python3-opentracing - opentracing interface for Python python-opentracing-doc - opentracing interface for Python - documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-opentracing Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-opentracing/python-opentracing_2.3.0-1.dsc Changes since the last upload: * New upstream release 2.3.0. Regards, -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#951804: RFS: golang-github-jfrog-gofrog/1.0.5-1 [ITP] -- Gofrog collection of go utilities (library)
Package: sponsorship-requests Severity: wishlist Dear Mentors and Go Packaging Team, I am looking for a sponsor for my package "golang-github-jfrog-gofrog": * Package name: golang-github-jfrog-gofrog Version : 1.0.5-1 Upstream Author : 2016 JFrog Ltd. * URL : https://github.com/jfrog/gofrog * License : Apache-2.0 * Vcs : https://salsa.debian.org/go-team/packages/golang-github-jfrog-gofrog Section : devel It builds those binary packages: golang-github-jfrog-gofrog-dev - Gofrog collection of go utilities (library) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/golang-github-jfrog-gofrog Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/golang-github-jfrog-gofrog/golang-github-jfrog-gofrog_1.0.5-1.dsc Changes since the last upload: * Initial release (closes: 950588) Thanks! Best regards -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#951734: ITP: golang-github-jfrog-gofrog -- The gofrog collection of go utilities
Package: wnpp Severity: wishlist Owner: Fabrice BAUZAC * Package name: golang-github-jfrog-gofrog Version : 1.0.5-1 Upstream Author : JFrog Ltd. * URL : https://github.com/jfrog/gofrog * License : Apache-2.0 Programming Lang: Go Description : A collection of go utilities Description: The gofrog collection of go utilities (library) This collection from JFrog contains modules for: * Running tasks in parallel * Caches following the Least-recently-used policy * Running commands and reading their output * Creating random files * A reader that publishes to multiple consumers * Basic AES encryption/decryption Note: my ultimate goal is to package the JFrog-CLI commandline tool [1] (Apache-2.0 license). golang-github-jfrog-gofrog is one of its dependencies, and I have run dh-make-golang to help me make it. [1] https://jfrog.com/getcli/ -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#943718: reportbug-gtk is reporting that up-to-date software is out-of-date
Hello Jason, I think you are mistaken in the way version numbers are compared in Debian. Version 7.5.3 is really considered newer than 7.5.3~deb10u1 (beware, it is a tilde, not a dash): # ge = "greater or equal" $ dpkg --compare-versions 7.5.3 ge "7.5.3~deb10u1"; echo $? 0 # means "true" Indeed, according to the Debian Policy [1]: The lexical comparison is a comparison of ASCII values modified so that all the letters sort earlier than all the non-letters and so that a tilde sorts before anything, even the end of a part. For example, the following parts are in sorted order from earliest to latest: ‘~~’, ‘~~a’, ‘~’, the empty part, ‘a’. Therefore I guess this bugreport can be closed as invalid, but I prefer to let others decide. [1] https://www.debian.org/doc/debian-policy/ch-controlfields.html#version Thanks! Best regards -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#709862: reportbug: GTK interface crashes on continue from package selection
Hello, Do you still have this issue? Otherwise, can we close it? Thanks! Best regards -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#945178: RFS: opentracing-python/2.2.0-1 [ITP] -- opentracing interface for Python
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "opentracing-python" * Package name: opentracing-python Version : 2.2.0-1 Upstream Author : The OpenTracing Authors. * URL : https://github.com/opentracing/opentracing-python * License : Expat and Apache-2.0 * Vcs : https://salsa.debian.org/python-team/modules/opentracing-python Section : python It builds those binary packages: python3-opentracing - opentracing interface for Python python-opentracing-doc - opentracing interface for Python - documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/opentracing-python Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/opentracing-python/opentracing-python_2.2.0-1.dsc Changes since the last upload: [ Fabrice BAUZAC ] * Initial release, closes: #942069. Thanks! Best regards -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#944562: Patch available
tags 944562 + patch thanks Merge request created: https://salsa.debian.org/reportbug-team/reportbug/merge_requests/38 -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#944515: Merge request created
tags 944515 + patch thanks Installing reportbug-gtk fixes the issue. So we need to fix the error message. Created merge request that fixes the error message [1]. [1] https://salsa.debian.org/reportbug-team/reportbug/merge_requests/37 -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#942759: [PATCH] handling of 0-width terminals
forwarded 942759 https://github.com/liske/needrestart/issues/166 tags 942759 + upstream fixed-upstream thanks A fix [1] has just been merged upstream. There is no upstream release yet. [1] https://github.com/liske/needrestart/pull/167 -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#942069: ITP: python-opentracing
retitle 942069 ITP: python-opentracing -- Python interface to the OpenTracing.io API owner 942069 ! thanks I think I'm ready to package it. -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Bug#942759: [PATCH] handling of 0-width terminals
tags 942759 + patch
thanks
Hello,
Here is how to get a terminal that indicates width=0:
- In Emacs
- C-x d /su:root@localhost: RET
- M-x shell RET, select a shell, enter the root password
- stty --all
The last command prints "columns 0".
I suggest the below fix: if the width is 0, then use a sane default. I
have submitted it upstream:
https://github.com/liske/needrestart/pull/167
diff --git a/perl/lib/NeedRestart/UI.pm b/perl/lib/NeedRestart/UI.pm
index 1e6a2f4..3d7c69e 100644
--- a/perl/lib/NeedRestart/UI.pm
+++ b/perl/lib/NeedRestart/UI.pm
@@ -127,13 +127,25 @@ sub _progress_inc {
$self->_progress_out();
}
+# my $columns = &_get_columns;
+# Return the number of columns to use for output.
+sub _get_columns {
+my $default_columns = 80; # Sane default
+if (-t *STDOUT) {
+($columns) = GetTerminalSize(\*STDOUT);
+
+# Cope with 0-width terminals.
+# See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942759
+return $columns == 0? $default_columns: $columns;
+}
+else {
+return $default_columns;
+}
+}
+
sub _progress_out {
my $self = shift;
-my $columns = 80;
-
-($columns) = GetTerminalSize(\*STDOUT) if (-t *STDOUT);
-
-$columns -= 3;
+my $columns = _get_columns;
my $wmsg = int($columns * 0.7);
$wmsg = length($self->{progress}->{msg})
if(length($self->{progress}->{msg}) < $wmsg);
my $wbar = $columns - $wmsg - 1;
@@ -143,12 +155,10 @@ sub _progress_out {
sub _progress_fin {
my $self = shift;
- my $columns = 80;
+ my $columns = _get_columns;
$self->{progress}->{count} = 0;
- ($columns) = GetTerminalSize(\*STDOUT) if (-t *STDOUT);
-
print $self->{progress}->{msg}, ' ' x ($columns -
length($self->{progress}->{msg})), "\n";
}
Thanks!
Best regards
--
Fabrice Bauzac-Stehly
PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
