Bug#1042095: python3-sphinx-press-theme: static/ directory is missing
Package: python3-sphinx-press-theme Version: 0.8.0-2 Severity: important X-Debbugs-Cc: none, Salman Mohammadi Dear Maintainer, The static/[1] directory is missing in the installed package therefore the built html does not contain css and js files. 1: https://salsa.debian.org/python-team/packages/sphinx-press-theme/-/tree/master/sphinx_press_theme/static -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-sphinx-press-theme depends on: ii python3 3.11.2-1+b1 ii python3-sphinx 5.3.0-4 python3-sphinx-press-theme recommends no packages. python3-sphinx-press-theme suggests no packages. -- no debconf information
Bug#999040: myspell-fa: missing required debian/rules targets build-arch and/or build-indep
On Tue, 09 Nov 2021 22:28:16 +0100 Lucas Nussbaum wrote:> Source: myspell-fa > Version: 0.20070816-3.1 > Severity: important > Justification: Debian Policy section 4.9 > Tags: bookworm sid > User: debian...@lists.debian.org > Usertags: missing-build-arch-indep > > Dear maintainer, > > Your package does not include build-arch and/or build-indep targets in > debian/rules. This is required by Debian Policy section 4.9, since 2012. > https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules > > Please note that this is also a sign that the packaging of this software > could benefit from a refresh. For example, packages using 'dh' cannot be > affected by this issue. > > This mass bug filing was discussed on debian-devel@ in > https://lists.debian.org/debian-devel/2021/11/msg00052.html . > The severity of this bug will be changed to 'serious' after a month. > > Best, > > Lucas > > Hey Lucas, The package is not in Salsa but is there a way that I can help keeping this package? Cheers, Salman
Bug#992401: debianutils: warning message: /usr/bin/which: this version of 'which' is deprecated and should not be used.
Package: debianutils Version: 5.0.1-1 Severity: normal X-Debbugs-Cc: none, sal...@smoha.org, Salman Mohammadi Dear Maintainer(s), Running `which` in the commandline throws the following warning message: /usr/bin/which: this version of 'which' is deprecated and should not be used. Could it be due to this commit? (which: punctuation fix) https://salsa.debian.org/debian/debianutils/-/commit/a92d15b24071cf2105c85daf4d27326dd6443732 Thanks, Salman -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debianutils depends on: ii libc6 2.31-15 debianutils recommends no packages. debianutils suggests no packages. -- no debconf information
Bug#991543: python-xe: python2 dependency. Shouldn't it get removed from Experimental?
Package: python-xe Severity: normal X-Debbugs-Cc: none, sal...@smoha.org, Salman Mohammadi Dear Maintainers, This package, python-xe, is a python2 module which has been removed from Debian Sid. I suppose this package should also get removed from Experimental. Thanks, Salman -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#991098: python3-django: RemovedInDjango40Warning: django-admin.py is deprecated in favor of django-admin
Package: python3-django Version: 2:3.2.5-1 Severity: normal X-Debbugs-Cc: none, sal...@smoha.org, Salman Mohammadi Dear Maintainers, I get the following error when running `$ django-admin startproject testproject` command. /usr/bin/django-admin:17: RemovedInDjango40Warning: django-admin.py is deprecated in favor of django-admin. warnings.warn( I installed python3-django from experimental repo. Thanks, Salman -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-django depends on: ii python3 3.9.2-3 ii python3-asgiref 3.3.1-1 ii python3-sqlparse 0.4.1-1 ii python3-tz 2021.1-1 Versions of packages python3-django recommends: ii libjs-jquery 3.5.1+dfsg+~3.5.5-7 Versions of packages python3-django suggests: pn bpython3 pn geoip-database-contrib ii gettext 0.21-4 ii ipython3 7.20.0-1 pn libgdal20 ii libsqlite3-mod-spatialite 5.0.1-2 ii python-django-doc 2:3.2.5-1 ii python3-bcrypt 3.1.7-4 pn python3-flup ii python3-memcache 1.59-5 ii python3-mysqldb 1.4.4-2+b3 ii python3-pil 8.1.2+dfsg-0.2 ii python3-psycopg2 2.8.6-2 pn python3-selenium pn python3-sqlite ii python3-yaml 5.3.1-5 -- no debconf information
Bug#963509: prospector: Version 1.3.1 now available
On Fri, 6 Nov 2020 19:59:43 -0300 =?utf-8?Q?Rog=C3=A9rio?= Brito wrote: > Package: prospector > Version: 1.1.7-2 > Followup-For: Bug #963509 > X-Debbugs-Cc: team+pyt...@tracker.debian.org, locutusofb...@debian.org, mat...@debian.org, czc...@debian.org > > Hi. > > There is a new version of prospector upstream at > > https://pypi.org/project/prospector/ > > that is supposed to fix all the problems that are currently in debian (read: > prospector doesn't work at all). > > I'm including in the CC some of the people that last touched the package (at > least according to changelog.Debian.gz in my system). If anybody could fix > it, that would be awesome. > > > Thanks, > > Rogério Brito. > Hi dear maintainers, I would be happy to give a hand to upgrade this package and its orphaned dependencies. What can I do to help? Thanks, Salman
Bug#988982: apt-utils: does not sort the numbers correctly. Should be smallest to largest.
Hi Nicholas, On 5/23/21 5:21 PM, Nicholas D Steeves wrote: On Sat, 22 May 2021 at 10:51, David Bremner <mailto:da...@tethera.net>> wrote: > > Salman Mohammadi mailto:sal...@smoha.org>> writes: > > > the command `apt-utils-search` does not sort the numbers based on integer value > > from smallest to largest. > > > > How to reproduce: > > - > > 1. M-x apt-utils-search > > 2. Search packages for regexp: google-android-platform > > Since the function does not promise any particular order, and the order > matches "apt search" on the command line, this seems more like a request > for an enhancement. I guess sorting by version might be possible, > although not trivial due to versions being complicated. Sorting by some > number embedded in the package name sounds messy. Salman, are you asking for a natural short, like piping a newline separated list to "sort -V" would provide? I think this is what you're asking for. David, AFAIK Emacs doesn't yet provide a natural sort algorithm, but is there any reason why it wouldn't be a good idea to pass the data to "sort -V" before outputting to the *APT package info* buffer? I guess there's also the question of if a non-interactive call to apt-utils-search should return a natural sorted list... But isn't the big question: If a user-friendly natural sorted list is a reasonable expectation, shouldn't "apt (and aptitude) search" do this directly? Better to fix it there, rather than in a way specific to debian-el, no? Cheers, Nicholas I didn't mean exactly something like "sort -V" but an order in which something-here-24 does not fall behind something-here-3. My mistake was that I hadn't checked `apt search` for this behavior before filing a bug here. Apt gives the same order. Here is the related bug, https://bugs.debian.org/681164 and already labeled as 'wontfix'. Thanks, Salman
Bug#988982: apt-utils: does not sort the numbers correctly. Should be smallest to largest.
Package: elpa-debian-el Version: 37.10 Severity: normal X-Debbugs-Cc: sal...@smoha.org Dear Maintainer, the command `apt-utils-search` does not sort the numbers based on integer value from smallest to largest. How to reproduce: - 1. M-x apt-utils-search 2. Search packages for regexp: google-android-platform The current sorted result: - google-android-platform-10-installer - Google's Android SDK Platform 10 Installer google-android-platform-11-installer - Google's Android SDK Platform 11 Installer google-android-platform-12-installer - Google's Android SDK Platform 12 Installer google-android-platform-13-installer - Google's Android SDK Platform 13 Installer google-android-platform-14-installer - Google's Android SDK Platform 14 Installer google-android-platform-15-installer - Google's Android SDK Platform 15 Installer google-android-platform-16-installer - Google's Android SDK Platform 16 Installer google-android-platform-17-installer - Google's Android SDK Platform 17 Installer google-android-platform-18-installer - Google's Android SDK Platform 18 Installer google-android-platform-19-installer - Google's Android SDK Platform 19 Installer google-android-platform-2-installer - Google's Android SDK Platform 2 Installer google-android-platform-20-installer - Google's Android SDK Platform 20 Installer google-android-platform-21-installer - Google's Android SDK Platform 21 Installer google-android-platform-22-installer - Google's Android SDK Platform 22 Installer google-android-platform-23-installer - Google's Android SDK Platform 23 Installer google-android-platform-24-installer - Google's Android SDK Platform 24 Installer google-android-platform-3-installer - Google's Android SDK Platform 3 Installer google-android-platform-4-installer - Google's Android SDK Platform 4 Installer google-android-platform-5-installer - Google's Android SDK Platform 5 Installer google-android-platform-6-installer - Google's Android SDK Platform 6 Installer google-android-platform-7-installer - Google's Android SDK Platform 7 Installer google-android-platform-8-installer - Google's Android SDK Platform 8 Installer google-android-platform-9-installer - Google's Android SDK Platform 9 Installer The expected sorted result: --- google-android-platform-2-installer - Google's Android SDK Platform 2 Installer google-android-platform-3-installer - Google's Android SDK Platform 3 Installer google-android-platform-4-installer - Google's Android SDK Platform 4 Installer google-android-platform-5-installer - Google's Android SDK Platform 5 Installer google-android-platform-6-installer - Google's Android SDK Platform 6 Installer google-android-platform-7-installer - Google's Android SDK Platform 7 Installer google-android-platform-8-installer - Google's Android SDK Platform 8 Installer google-android-platform-9-installer - Google's Android SDK Platform 9 Installer google-android-platform-10-installer - Google's Android SDK Platform 10 Installer google-android-platform-11-installer - Google's Android SDK Platform 11 Installer google-android-platform-12-installer - Google's Android SDK Platform 12 Installer google-android-platform-13-installer - Google's Android SDK Platform 13 Installer google-android-platform-14-installer - Google's Android SDK Platform 14 Installer google-android-platform-15-installer - Google's Android SDK Platform 15 Installer google-android-platform-16-installer - Google's Android SDK Platform 16 Installer google-android-platform-17-installer - Google's Android SDK Platform 17 Installer google-android-platform-18-installer - Google's Android SDK Platform 18 Installer google-android-platform-19-installer - Google's Android SDK Platform 19 Installer google-android-platform-20-installer - Google's Android SDK Platform 20 Installer google-android-platform-21-installer - Google's Android SDK Platform 21 Installer google-android-platform-22-installer - Google's Android SDK Platform 22 Installer google-android-platform-23-installer - Google's Android SDK Platform 23 Installer google-android-platform-24-installer - Google's Android SDK Platform 24 Installer Thanks, Salman -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-debian-el depends on: ii bzip2 1.0.8-4 ii dh-elpa-helper 2.0.8 ii dpkg1.20.9 ii emacsen-common 3.0.4 ii reportbug 7.10.3 ii xz-utils5.2.5-2 Versions of packages elpa-debian-el recommends: ii emacs 1:27.1+1-3.1 ii emacs-gtk [emacs] 1:27.1+1-3.1 ii wget 1.21-1+b1 elpa-debian-el suggests no packages.
Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.
Hi Nicholas, On 5/17/21 7:11 AM, Nicholas D Steeves wrote: Hi Salman, Salman Mohammadi writes: I could reproduce this bug under this environment: 1. clean install debian stable in a vm 2. upgrade debian to sid 3. install emacs and debian-el: $ sudo apt -y install emacs elpa-debian-el Now, M-x debian-bug command does not work correctly. I think there's something missing from your steps to reproduce. I tried this: 1. With a clean chroot, 'sudo apt install emacs-nox elpa-debian-el' * Given that Emacs was not installed in the stable VM until post-upgrade, I don't think my digression is a relevant variable. 2. Start Emacs 3. M-x debian-bug 4. Everything appears to work fine. After composing the full text of the bug, I hit C-c C-c, and then see the *Emacs Mail Setup Help* window appear, along with a minibuffer prompt. From the original bug report email it sounds like this is farther along then you were able to get? a. My hostname is a real FQDN (however no longer functional due to expired dyndns subscription--post-Oracle acquisition is a rip-off). It's possible that this bug only exists on hosts that don't have a FQDN hostname. b. Reportbug has not been configured. Regards, Nicholas what makes me wonder is that the same procedure works on Debian 10 but not on Debian Sid. To clarify the encountered bug, I once recorded my screen on a clean installed Debain 10 (which works fine). https://peertube.nogafa.org/videos/watch/9156c6dd-a46a-436a-9ba3-527c97c2ea71 and also on a clean installed Debian Sid (which doesn't work). https://peertube.nogafa.org/videos/watch/7f8a31ec-52d8-42ac-8a01-2e2a92dae592 Regards, Salman
Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.
On 5/16/21 3:04 PM, David Bremner wrote: Salman Mohammadi writes: I have no .reportbugrc bit instead use the following configuration in my .emacs: (setq user-mail-address "sal...@smoha.org" user-full-name "Salman Mohammadi") (setq send-mail-function 'mailclient-send-it) I tried setting send-mail-function to mailclient-send-it (which by the way tends to mangle attachements, but I guess that's not the issue here) I still can't duplicate your issue. You can try duplicating the problem with "emacs -q". You will need to run M-x load-library debian-el-autoloads . If that works, then your issue is most likely an interaction with some other emacs addon package. You can try removing them one by one, or loading them manually into emacs -q. Dear David, I could reproduce this bug under this environment: 1. clean install debian stable in a vm 2. upgrade debian to sid 3. install emacs and debian-el: $ sudo apt -y install emacs elpa-debian-el Now, M-x debian-bug command does not work correctly. Thanks, Salman
Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.
On 5/16/21 1:31 PM, David Bremner wrote: Control: tag -1 unreproducible Control: severity -1 normal Salman Mohammadi writes: Package: elpa-debian-el Version: 37.10 Severity: grave Justification: renders package unusable X-Debbugs-Cc: sal...@smoha.org Dear Maintainer, I cannot report any bugs using M-x debian-bug at all. After entering the bug summary, I get the following error message, and cannot correctly reach the page where I should write the actual bug report. Getting package information from reportbug... debian-bug-prefill-report: Reportbug did not produce expected output! Bailing out. Reportbug may have sent an empty report! I can't reproduce this behaviour. I guess it might be related to something in your reportbug configuration. Can you share your .reportbugrc? By the way, this bug by itself does not "render package unusable", since the package provides other functionality. I have no .reportbugrc bit instead use the following configuration in my .emacs: (setq user-mail-address "sal...@smoha.org" user-full-name "Salman Mohammadi") (setq send-mail-function 'mailclient-send-it) I had no problem in Debian 10 (stable) but as I upgraded to Sid, I get the mentioned error message. Thanks, Salman
Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.
Package: elpa-debian-el Version: 37.10 Severity: grave Justification: renders package unusable X-Debbugs-Cc: sal...@smoha.org Dear Maintainer, I cannot report any bugs using M-x debian-bug at all. After entering the bug summary, I get the following error message, and cannot correctly reach the page where I should write the actual bug report. Getting package information from reportbug... debian-bug-prefill-report: Reportbug did not produce expected output! Bailing out. Reportbug may have sent an empty report! Thanks, Salman -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-debian-el depends on: ii bzip2 1.0.8-4 ii dh-elpa-helper 2.0.8 ii dpkg1.20.9 ii emacsen-common 3.0.4 ii reportbug 7.10.3 ii xz-utils5.2.5-2 Versions of packages elpa-debian-el recommends: ii emacs 1:27.1+1-3.1 ii emacs-gtk [emacs] 1:27.1+1-3.1 ii wget 1.21-1+b1 elpa-debian-el suggests no packages.
Bug#985018: python3-django-haystack: SyntaxWarning during package installation
> during a test with piuparts I noticed your package emits a SyntaxWarning > during installation: > > Setting up python3-django-haystack (3.0-1) ... > /usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py:734: SyntaxWarning: "is" with a literal. Did you mean "=="? > if value is None or len(value) is 0: > > > Andreas > > This SyntaxWarning has been resolved in upstream code. https://github.com/django-haystack/django-haystack/commit/fed2621dee77f74464febc0290218f5f6b6fa6d6#diff-9038404f6e9df0a87187fc4deb3be7d1a5ebcd49e346ad6207978f602d71e57d Cheers, Salman
Bug#975473: gnome-shell-extensions-gpaste: package name does not coincide with gnome extensions naming pattern
Package: gnome-shell-extensions-gpaste Version: 3.30.2-1 Severity: normal Dear Maintainer, `gnome-shell-extensions-gpaste` does not coincide with the naming pattern of other gnome extensions where all of them are named like this: gnome-shell-extension-something-here so, this package should be renamed to, gnome-shell-extension-gpaste (extension instead of extensions) Cheers, Salman -- System Information: Debian Release: 10.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell-extensions-gpaste depends on: ii gir1.2-gpaste-1.0 3.30.2-1 ii gnome-shell 3.30.2-11~deb10u2 ii gpaste 3.30.2-1 gnome-shell-extensions-gpaste recommends no packages. gnome-shell-extensions-gpaste suggests no packages. -- no debconf information
Bug#975278: ruby-asciidoctor-pdf: ruby-rouge should we introduced as a suggested package
Package: ruby-asciidoctor-pdf Version: 1.5.0~alpha.17.dev-5 Severity: normal Dear Maintainer, The package `ruby-rouge` can enhance ruby-asciidoctor-pdf by using `:source-highlighter: rouge` in the source code of the asciidoc file. So it should be introduced a suggested package. Cheers, Salman -- System Information: Debian Release: 10.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-asciidoctor-pdf depends on: ii ruby 1:2.5.1 ii ruby-asciidoctor 2.0.10-2~bpo10+1 ii ruby-concurrent 1.0.5-3 ii ruby-prawn 2.2.0+dfsg-1 ii ruby-prawn-icon 2.3.0-4 ii ruby-prawn-svg 0.28.0-3 ii ruby-prawn-table 0.2.2-1 ii ruby-safe-yaml 1.0.4-2 ii ruby-thread-safe 0.3.6-1 ii ruby-treetop 1.6.8-1 ruby-asciidoctor-pdf recommends no packages. ruby-asciidoctor-pdf suggests no packages. -- no debconf information
Bug#974822: python3-django: bash-completion is not working for django-admin commands
Package: python3-django Version: 2:2.2.17-1~bpo10+1 Severity: normal Dear Maintainer, django-admin commands cannot be autocompleted using TAB. The following file also exist, /usr/share/bash-completion/completions/django_bash_completion Cheers, Salman -- System Information: Debian Release: 10.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-django depends on: ii python3 3.7.3-1 ii python3-sqlparse 0.2.4-1 ii python3-tz 2019.1-1 Versions of packages python3-django recommends: ii libjs-jquery 3.5.1+dfsg-4~bpo10+1 Versions of packages python3-django suggests: pn bpython3 pn geoip-database-contrib ii gettext 0.19.8.1-9 ii ipython3 5.8.0-1 ii libgdal20 2.4.0+dfsg-1+b1 ii libsqlite3-mod-spatialite 4.3.0a-5+b2 ii python-django-doc 2:2.2.17-1~bpo10+1 ii python3-bcrypt 3.1.6-1 pn python3-flup ii python3-memcache 1.59-1 pn python3-mysqldb ii python3-pil 5.4.1-2+deb10u2 ii python3-psycopg2 2.7.7-1 ii python3-selenium 3.14.1+dfsg1-1 pn python3-sqlite ii python3-yaml 3.13-2 -- no debconf information
Bug#972628: python3-mysqldb: backporting python3-mysqldb not to break backported python3-django
Package: python3-mysqldb Version: 1.3.10-2 Severity: wishlist Dear Maintainer(s), I would kindly ask if it is possible to backport python3-mysqldb from Bullseye to Buster-backports not break the backported python3-django. The backported version of python3-django has this line Breaks: ... , python3-mysqldb (<< 1.3.13) which could be solved by backporting python3-mysqldb. Regards, Salman -- System Information: Debian Release: 10.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-mysqldb depends on: ii libc6 2.28-10 ii libmariadb3 1:10.3.25-0+deb10u1 ii libssl1.1 1.1.1d-0+deb10u3 ii python3 3.7.3-1 ii zlib1g 1:1.2.11.dfsg-1 python3-mysqldb recommends no packages. Versions of packages python3-mysqldb suggests: pn default-mysql-server | virtual-mysql-server pn python-egenix-mxdatetime pn python3-mysqldb-dbg -- no debconf information
Bug#972626: python3-mysqldb: backporting python3-mysqldb not to break backported python3-django
Package: python3-mysqldb Version: 1.3.10-2 Severity: wishlist Dear Maintainer(s), I would kindly ask if it is possible to backport python3-mysqldb from Bullseye to Buster-backports not break the backported python3-django. The backported version of python3-django has this line Breaks: ... , python3-mysqldb (<< 1.3.13) which could be solved by backporting python3-mysqldb. Regards, Salman -- System Information: Debian Release: 10.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-mysqldb depends on: ii libc6 2.28-10 ii libmariadb3 1:10.3.25-0+deb10u1 ii libssl1.1 1.1.1d-0+deb10u3 ii python3 3.7.3-1 ii zlib1g 1:1.2.11.dfsg-1 python3-mysqldb recommends no packages. Versions of packages python3-mysqldb suggests: pn default-mysql-server | virtual-mysql-server pn python-egenix-mxdatetime pn python3-mysqldb-dbg -- no debconf information
Bug#966141: black: syntax error during installation
On Thu, 23 Jul 2020 18:32:35 +0200 Diego Roversi wrote:> Package: black > Version: 18.9b0-1-6 > Severity: important > > Hello, > > during installation it gives me this error: > > Setting up black (18.9b0-1-6) ... > -V is ignored in pypycompile > Failed to byte-compile /usr/lib/python3/dist-packages/black.py: File > "/usr/lib/python3/dist-packages/black.py", line 128 > ) -> "FileMode": > ^ > SyntaxError: invalid syntax > > > -- System Information: > Debian Release: 10.4 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386, arm64 > > Kernel: Linux 5.6.14+ (SMP w/4 CPU cores) > Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages black depends on: > ii python3 3.7.3-1 > ii python3-appdirs 1.4.3-1 > ii python3-attr 18.2.0-1 > ii python3-click 7.0-1 > ii python3-pkg-resources 40.8.0-1 > ii python3-toml 0.10.0-1 > > black recommends no packages. > > Versions of packages black suggests: > pn python-black-doc > > -- debconf-show failed > > > > I can also confirm this bug but as it can be seen it is related to pypy3 and not CPython (default implementation of Python). Cheers, Salman
Bug#971712: python3-docker: packaging python-docker-doc
Package: python3-docker Version: 3.4.1-4 Severity: wishlist Dear Maintainer, I was wondering if it possible to package python-docker-doc which resides here: https://github.com/docker/docker-py/tree/master/docs Cheers, Salman -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-docker depends on: ii python3 3.7.3-1 ii python3-dockerpycreds 0.3.0-1 ii python3-requests 2.21.0-1 ii python3-six 1.12.0-1 ii python3-websocket 0.53.0-1 python3-docker recommends no packages. python3-docker suggests no packages. -- no debconf information
Bug#971610: uwsgi: packaging uwsgi-doc
Package: uwsgi Version: 2.0.18-1 Severity: wishlist Dear Maintainer, I was wondering if it possible to package uwsgi-doc which resides here: https://github.com/unbit/uwsgi-docs Cheers, Salman -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages uwsgi depends on: ii lsb-base 10.2019051400 ii uwsgi-core 2.0.18-1 uwsgi recommends no packages. uwsgi suggests no packages. -- no debconf information
Bug#971444: emacs: cannot set a custom theme using only the menu bar
Package: emacs Version: 1:26.1+1-3.2+deb10u1 Severity: normal Dear Rob, It is not possible to set a custom theme using only the menu bar and without setting it by hand in init file. The theme will be applied but after restarting Emacs, it won't be loaded automatically. This bug only applies to the themes which are not shipped with Emacs but can be installed from Debian repos. These are steps to reproduce: 1. Install Emacs from Debian repos ($ sudo apt install emacs) 2. Install an Emacs theme from Debian repos. For instance Monokai ($ sudo apt install elpa-monokai-theme) 3. Go to Options > Customize Emacs > Custom Themes 4. Choose monokai 5. Click on Save Theme Settings 6. Restart Emacs Workaround: Adding package initialize and loading the theme manually solves the bug. (package-initialize) (load-theme 'monokai t) Cheers, Salman -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages emacs depends on: ii emacs-gtk 1:26.1+1-3.2+deb10u1 emacs recommends no packages. emacs suggests no packages. -- no debconf information
Bug#971214: elpy: FTBFS: tests failed
Hi, What I can see is that > (error "Elpy error: black not installed") Is *black* already installed? Cheers, Salman On Sun, 27 Sep 2020 21:06:17 +0200 Lucas Nussbaum wrote: > Source: elpy > Version: 1.34.0-2 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200926 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > dh_auto_build > > I: pybuild base:217: /usr/bin/python3 setup.py build > > running build > > running build_py > > creating /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/jedibackend.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/refactor.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/__init__.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/__main__.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/pydocutils.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/blackutil.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/yapfutil.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/compat.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/auto_pep8.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/rpc.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > copying elpy/server.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy > > creating /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/test_server.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/test_rpc.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/support.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/test_yapf.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/__init__.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/test_pydocutils.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/test_auto_pep8.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/test_refactor.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/test_jedibackend.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/compat.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/test_black.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > copying elpy/tests/test_support.py -> /<>/.pybuild/cpython3_3.8_elpy/build/elpy/tests > > running egg_info > > creating elpy.egg-info > > writing elpy.egg-info/PKG-INFO > > writing dependency_links to elpy.egg-info/dependency_links.txt > > writing requirements to elpy.egg-info/requires.txt > > writing top-level names to elpy.egg-info/top_level.txt > > writing manifest file 'elpy.egg-info/SOURCES.txt' > > reading manifest file 'elpy.egg-info/SOURCES.txt' > > reading manifest template 'MANIFEST.in' > > writing manifest file 'elpy.egg-info/SOURCES.txt' > > PYTHONPATH=. python3 -m sphinx -N -bman docs/ build/man > > Running Sphinx v3.2.1 > > making output directory... done > > building [mo]: targets for 0 po files that are out of date > > building [man]: all manpages > > updating environment: [new config] 9 added, 0 changed, 0 removed > > reading sources... [ 11%] FAQ
Bug#966828: emacs: Fatal error 11: Segmentation fault
Package: emacs Version: 1:26.3+1-2 Severity: grave Dear Maintainer, I cannot run emacs at all and I get the following error message: Fatal error 11: Segmentation fault Backtrace: emacs[0x5111be] emacs[0x4f6ead] emacs[0x50f63e] emacs[0x50f86d] emacs[0x50f8e9] /lib/x86_64-linux-gnu/libpthread.so.0(+0x14140)[0x7f29d6abd140] emacs[0x4d94b0] emacs[0x4d9897] emacs[0x4da4df] emacs[0x56dc2c] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x56f90b] emacs[0x56dc2c] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x5a74c0] emacs[0x56dbab] emacs[0x5a74c0] emacs[0x570726] emacs[0x56fcc6] emacs[0x571c1c] emacs[0x56cd7e] emacs[0x4f8470] emacs[0x56cced] emacs[0x4f71f8] emacs[0x4fc2b3] emacs[0x4fc5f8] emacs[0x41a5c2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7f29d67ddcca] emacs[0x41b29a] Segmentation fault Regards, Salman -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages emacs depends on: ii emacs-gtk 1:26.3+1-2 emacs recommends no packages. emacs suggests no packages. -- no debconf information
Bug#940660: elpa-elpy: add Suggests: python3-rope to refactor code
On 1/20/20 1:09 AM, Nicholas D Steeves wrote: P.P.S. Please don't top post. http://www.idallen.com/topposting.html Yeah, okay :)
Bug#949162: pyspread: pyspread does not start
Package: pyspread Version: 1.99.0.1-1 Severity: grave Dear Maintainer, After installing pysread I cannot run it. I get the following message when I try to run the software from terminal: Traceback (most recent call last): File "/usr/bin/pyspread", line 58, in from src.workflows import Workflows File "/usr/share/pyspread/src/workflows.py", line 55, in from src.dialogs import DiscardChangesDialog, FileOpenDialog, GridShapeDialog File "/usr/share/pyspread/src/dialogs.py", line 1377, in class TutorialDialog(HelpDialogBase): File "/usr/share/pyspread/src/dialogs.py", line 1381, in TutorialDialog baseurl = str(path.parent) + '/' AttributeError: 'str' object has no attribute 'parent' -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pyspread depends on: ii python3 3.7.5-3 ii python3-numpy 1:1.17.4-5 ii python3-pyqt5 5.14.1+dfsg-2 ii python3-pyqt5.qtsvg 5.14.1+dfsg-2 Versions of packages pyspread recommends: ii python3-enchant 2.0.0-2 ii python3-matplotlib 3.1.2-1 pyspread suggests no packages. -- no debconf information
Bug#948569: elpa-elpy: elpy-find-file: Symbol’s value as variable is void: ffip-prune-patterns
Dear Nicholas, sorry, I had two mistakes in my previous bug report, Steps to reproduce: 1. install the needed packages in Debian Sid: $ sudo apt install elpa-elpy elpa-find-file-in-project 2. open emacs and activate python-mode M-x python-mode 3. activate elpy-mode M-x elpy-mode 4. run the following command C-c C-f On 1/12/20 11:20 PM, Nicholas D Steeves wrote: Control: tags -1 + moreinfo unreproducible Hi Salman, Thanks for the follow-up. Salman Mohammadi writes: Dear Nicholas, I mentioned in the previous bug report how to reproduce this message, but it was not clear, sorry. Steps to reproduce: 1. install the needed packages in Debian Sid: $ sudo apt install elpa-elpy elpa-find-file-in-project 2. open emacs and activate python-mode M-x python-mode 3. run the following command C-x C-f and you now get the mentioned error message. This sequence doesn't activate Elpy; it activates python-mode, and C-x C-f runs the built-in 'find-file'. At this time the bug remains unreproducible with the provided information, and it seems like something in your Emacs config is causing this issue; Please do not modify the state of the unreproducible tag. When sufficient information has been provided to reproduce this issue I will drop that tag. I am prioritising #948567, and hope you will do the same. Previously this bug (#948569) seemed to have been most likely caused by #948567, but that isn't the case with the step 1. you just provided. eg: if elpy was upgraded, and the user had custom ffip config, then the user ran apt autoremove, the result would be "Symbol’s value as variable is void: ffip-prune-patterns". #948567 has at least two clear avenues of resolution, whereas this one has none at this time, thus the former is a better use of free time. Best, Nicholas
Bug#948569: elpa-elpy: elpy-find-file: Symbol’s value as variable is void: ffip-prune-patterns
Dear Nicholas, I mentioned in the previous bug report how to reproduce this message, but it was not clear, sorry. Steps to reproduce: 1. install the needed packages in Debian Sid: $ sudo apt install elpa-elpy elpa-find-file-in-project 2. open emacs and activate python-mode M-x python-mode 3. run the following command C-x C-f and you now get the mentioned error message. On 1/11/20 10:34 PM, Nicholas D Steeves wrote: Control: tags -1 + moreinfo Dear Salman, Salman Mohammadi writes: after installing elpa-find-file-in-project, running the command C-c C-f shows us the following error message: elpy-find-file: Symbol’s value as variable is void: ffip-prune-patterns Please provides steps to reproduce. Here is what I see in the minibuffer after installing Elpy into a clean schroot, elpy-enable, opening a python file, and then C-c C-f: `elpy-find-file' necessitates `projectile' or `find-file-in-project' to be installed This appears in the minibuffer and is consistent with upstream's claim that ffip is no longer required (eg: it now gracefully handles missing ffip). They dropped the dependency because an ido user complained that ffip, and thus Ivy, was cruft. How were you able to trigger behaviour that differs from what you reported in #948567? ffip-5.7.7 has 'ffip-prune-patterns' debcheckout find-file-in-project ag ffip-prune-patterns find-file-in-project Regards, Nicholas
Bug#948569: elpa-elpy: elpy-find-file: Symbol’s value as variable is void: ffip-prune-patterns
Package: elpa-elpy Version: 1.32.0-1 Severity: important Dear Nicholas, after installing elpa-find-file-in-project, running the command C-c C-f shows us the following error message: elpy-find-file: Symbol’s value as variable is void: ffip-prune-patterns The package elpa-find-file-in-project is version: 5.7.7-1 and maybe a new release of this package in Debian Sid is necessary. cheers, Salman -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-elpy depends on: ii dh-elpa-helper 2.0.2 ii elpa-company 0.9.9-2 ii elpa-highlight-indentation 0.7.0-4 ii elpa-pyvenv 1.21-1 ii elpa-s 1.12.0-3 ii elpa-yasnippet 0.13.0-3 ii emacsen-common 3.0.4 ii flake8 3.7.9-1 ii libjs-sphinxdoc 1.8.5-4 ii python3 3.7.5-3 ii python3-flake8 3.7.9-1 ii sphinx-rtd-theme-common 0.4.3+dfsg-2 Versions of packages elpa-elpy recommends: ii emacs 1:26.3+1-1 ii emacs-gtk [emacs] 1:26.3+1-1 ii python3-jedi 0.15.2-1 Versions of packages elpa-elpy suggests: ii black 19.10b0-1 pn elpa-pip-requirements ii ipython3 7.11.0-2 ii jupyter-console 6.0.0-2 ii python3-autopep8 1.4.4-3 ii python3-pip 18.1-5 ii yapf3 0.28.0-2 -- no debconf information
Bug#948567: elpa-elpy: elpa-find-file-in-project will not be automatically installed
Package: elpa-elpy Version: 1.32.0-1 Severity: normal Dear Nicholas, A fresh installation of elpa-elpy does not install elpa-find-file-in-project automatically and running the command C-c C-f shows us this warning message: elpy-find-file: ‘elpy-find-file’ necessitates ‘projectile’ or ‘find-file-in-project’ to be installed. But as I checked the control file, elpa-find-file-in-project is in Build-Depends. Cheers, Salman -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-elpy depends on: ii dh-elpa-helper 2.0.2 ii elpa-company 0.9.9-2 ii elpa-highlight-indentation 0.7.0-4 ii elpa-pyvenv 1.21-1 ii elpa-s 1.12.0-3 ii elpa-yasnippet 0.13.0-3 ii emacsen-common 3.0.4 ii flake8 3.7.9-1 ii libjs-sphinxdoc 1.8.5-4 ii python3 3.7.5-3 ii python3-flake8 3.7.9-1 ii sphinx-rtd-theme-common 0.4.3+dfsg-2 Versions of packages elpa-elpy recommends: ii emacs 1:26.3+1-1 ii emacs-gtk [emacs] 1:26.3+1-1 ii python3-jedi 0.15.2-1 Versions of packages elpa-elpy suggests: ii black 19.10b0-1 pn elpa-pip-requirements ii ipython3 7.11.0-2 ii jupyter-console 6.0.0-2 ii python3-autopep8 1.4.4-3 ii python3-pip 18.1-5 ii yapf3 0.28.0-2 -- no debconf information
Bug#945282: python3-tables: getting a SyntaxWarning during installation
Package: python3-tables
Version: 3.5.2-4
Severity: normal
Dear Maintainer,
During python3-tables upgrade, I get the following warning message:
Setting up python3-tables (3.5.2-4) ...
/usr/lib/python3/dist-packages/tables/scripts/pttree.py:318:
SyntaxWarning: "is" with a literal. Did you mean "=="?
if path is '/':
/usr/lib/python3/dist-packages/tables/scripts/pttree.py:327:
SyntaxWarning: "is not" with a literal. Did you mean "!="?
if path is not '/':
After looking at the source code, these lines are causing this warning:
else:
# natural order
if path is '/':
# root is not in root._v_children
pretty[path].sort_by = 0
else:
pretty[path].sort_by = list(parent._v_children.values(
)).index(node)
and
if path is not '/':
# create a PrettyTree for the parent of this node, if one
# doesn't exist already
if parent_path not in pretty:
pretty.update({parent_path: PrettyTree()})
Regards,
Salman
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-tables depends on:
ii python-tables-data 3.5.2-4
ii python3 3.7.5-3
ii python3-numexpr 2.7.0-1+b1
ii python3-numpy 1:1.17.4-3
ii python3-six 1.13.0-1
ii python3-tables-lib 3.5.2-4
python3-tables recommends no packages.
Versions of packages python3-tables suggests:
pn python-tables-doc
pn python3-netcdf4
pn vitables
-- no debconf information
Bug#942535: telegram-desktop: use Desktop Notifications instead of custom notification
Package: telegram-desktop Version: 1.8.15-1 Severity: wishlist Dear Maintainer, It would be nice if you change the notification system from the custom one to Desktop Notifications Specification so the notification could be integrated with the default Desktop Environment notification system. Cheers, Salman -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages telegram-desktop depends on: ii libavcodec58 7:4.1.4-1+b3 ii libavformat58 7:4.1.4-1+b3 ii libavutil56 7:4.1.4-1+b3 ii libc6 2.29-2 ii libgcc1 1:9.2.1-9 ii libglib2.0-0 2.62.1-1 ii liblz4-1 1.9.1-2 ii liblzma5 5.2.4-1+b1 ii libminizip1 1.1-8+b1 ii libopenal1 1:1.19.1-1+b1 ii libopus0 1.3-1+b1 ii libqt5core5a [qtbase-abi-5-11-3] 5.11.3+dfsg1-4 ii libqt5dbus5 5.11.3+dfsg1-4 ii libqt5gui5 5.11.3+dfsg1-4 ii libqt5network5 5.11.3+dfsg1-4 ii libqt5widgets5 5.11.3+dfsg1-4 ii librlottie0-1 0~git20190721.24346d0+dfsg-2+b1 ii libssl1.1 1.1.1d-2 ii libswresample3 7:4.1.4-1+b3 ii libswscale5 7:4.1.4-1+b3 ii libx11-6 2:1.6.8-1 ii libxxhash0 0.7.2-1 ii qt5-image-formats-plugins 5.11.3-2 ii zlib1g 1:1.2.11.dfsg-1+b1 Versions of packages telegram-desktop recommends: ii fonts-open-sans 1.11-1 telegram-desktop suggests no packages. -- no debconf information
Bug#942534: ardour: Ardour GUI cannot be maximized
Package: ardour Version: 1:5.12.0-3 Severity: normal Dear Maintainer, I'm not able to maximze Ardour either by double clicking or by right clicking on the top bar. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ardour depends on: ii ardour-data 1:5.12.0-3 ii jackd 5+nmu1 ii libarchive13 3.4.0-1 ii libasound2 1.1.8-2 ii libatkmm-1.6-1v5 2.28.0-2 ii libaubio5 0.4.9-2 ii libc6 2.29-2 ii libcairo2 1.16.0-4 ii libcairomm-1.0-1v5 1.12.2-4 ii libcurl3-gnutls 7.66.0-1 ii libcwiid1 0.6.00+svn201-4 ii libfftw3-single3 3.3.8-2 ii libfluidsynth1 1.1.11-4 ii libfontconfig1 2.13.1-2+b1 ii libgcc1 1:9.2.1-9 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-1 ii libglib2.0-0 2.62.1-1 ii libglibmm-2.4-1v5 2.62.0-1 ii libgtk2.0-0 2.24.32-4 ii libgtkmm-2.4-1v5 1:2.24.5-4 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2+b1 ii liblilv-0-0 0.24.4~dfsg0-1 ii liblo7 0.30-3 ii liblrdf0 0.6.1-1+b1 ii libltc11 1.3.1-1 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-0 1.42.4-7 ii libpangoft2-1.0-0 1.42.4-7 ii libpangomm-1.4-1v5 2.42.0-2 ii libqm-dsp0 1.7.1-4 ii librubberband2 1.8.2-1 ii libsamplerate0 0.1.9-2 ii libsigc++-2.0-0v5 2.10.2-1 ii libsndfile1 1.0.28-6 ii libstdc++6 9.2.1-9 ii libsuil-0-0 0.10.4-2 ii libtag1v5 1.11.1+dfsg.1-0.3+b1 ii libusb-1.0-0 2:1.0.23-1 ii libvamp-hostsdk3v5 2.7.1~repack0-1+b1 ii libvamp-sdk2v5 2.7.1~repack0-1+b1 ii libx11-6 2:1.6.8-1 ii libxml2 2.9.4+dfsg1-7+b3 Versions of packages ardour recommends: ii ardour-video-timeline 1:5.12.0-3 ii chromium [www-browser] 76.0.3809.100-1 ii firefox [www-browser] 69.0.2-1 Versions of packages ardour suggests: pn jamin ii qjackctl 0.5.9-1 -- no debconf information
Bug#617958: libnotify-bin: Critical notifications should not expire
Dear Maintainer(s), I cannot reproduce this bug. Running the following command, $ notify-send --urgency=critical "Low battery" persists until I manually click on it. Regards
Bug#941044: elpa-elpy: creating the elpy-doc package
Package: elpa-elpy Version: 1.31.0-1 Severity: wishlist Dear Nicholas, It would be nice if you create the package `elpy-doc` alongside elpa-elpy to manage html docs separately. If you want, I can also offer my help, in form of an MR, to reduce the time you need to invest on this matter Regards, Salman -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-elpy depends on: ii dh-elpa-helper 2.0.2 ii elpa-company 0.9.9-2 ii elpa-find-file-in-project 5.7.7-1 ii elpa-highlight-indentation 0.7.0-4 ii elpa-pyvenv 1.20-2 ii elpa-s 1.12.0-3 ii elpa-yasnippet 0.13.0-3 ii emacsen-common 3.0.4 ii flake8 3.7.8-3 ii python3 3.7.3-1 ii python3-flake8 3.7.8-3 Versions of packages elpa-elpy recommends: ii emacs 1:26.3+1-1 ii emacs-gtk [emacs] 1:26.3+1-1 ii libjs-sphinxdoc 1.8.5-3 ii python3-jedi 0.14.1-1 Versions of packages elpa-elpy suggests: ii black 19.3b0-1 pn elpa-pip-requirements ii python3-autopep8 1.4.4-1 ii python3-jupyter-console 5.2.0-1 ii python3-pip 18.1-5 ii yapf3 0.28.0-1 -- no debconf information
Bug#940660: elpa-elpy: add Suggests: python3-rope to refactor code
Hi David, Yeah, I would update the MR to use Bowler <https://pybowler.io>, but currently Bowler is not in the repos. Regards On Sat, 21 Sep 2019 14:33:45 -0400 Nicholas D Steeves wrote: > Control: forwarded -1 https://github.com/jorgenschaefer/elpy/issues/1449 > > Hi Salman and David, > > On Wed, Sep 18, 2019 at 01:54:17PM -0300, David Bremner wrote: > > Salman Mohammadi writes: > > > > > Package: elpa-elpy > > > Version: 1.31.0-1 > > > Severity: normal > > > > > > Dear Nicholas, > > > > > > Adding this entry `Suggests: python3-rope` to debian/control ensures > > > that we can refactor the code without error messages like this: > > > > > > elpy-rpc--default-error-callback: Elpy error: rope not installed, cannot > > > refactor code. > > > > > > > Thank you for filing this bug, much appreciated. I've set the > forwarded URL to the preexisting upstream issue on the removal of > Rope. If upstream changes its mind about the removal. The current > upstream maintainer doesn't use this functionality, so it's > effectively unmaintained. To avoid deprecating your contribution, > would you please update your MR to use Bowler if upstream switches to > it? > > > Just for the record, Suggests won't cause it to be installed > > automatically for many (most?) users. > > Thanks for the reminder ;-) Salman initially proposed a Recommends, > which I NACKed, (see above paragraph and URL, esp previous > maintainer's NACK of Rope usage for rationale), and also because IIRC > Antoine (anarcat) said he didn't use it either in his initial RFP. I > also use Elpy without rope. > > > Cheers, > Nicholas
Bug#940924: python3-rope: the license has been changed without the main author's consent
Package: python3-rope Version: 0.10.5-3 Severity: grave Dear Maintainer, As can be seen here[1], the license of this package has been changed from GPL to LGPL without the consent of the main author. [1] https://github.com/python-rope/rope/pull/266 I don't know, if it is still relevant to keep this orphaned package in Debian anymore. Regards, Salman -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-rope depends on: ii python3 3.7.3-1 Versions of packages python3-rope recommends: ii git [git-core] 1:2.23.0-1 ii mercurial 5.1.1-1 ii python3-svn 1.9.9-1+b1 python3-rope suggests no packages. -- no debconf information
Bug#940843: python-sympy-doc: \(\LaTeX\) is not parsed; latex exited with error [stdout]
Package: python-sympy-doc
Version: 1.3-2
Severity: normal
Dear Maintainer,
There exist a section in the doc, this term `\(\LaTeX\)`, which is not
correctly parsed, and it
shows the following error message:
System Message: WARNING/2 (\LaTeX)
latex exited with error [stdout] This is pdfTeX, Version
3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded
format=latex) restricted \write18 enabled. entering extended mode
(./math.tex LaTeX2e <2018-12-01>
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls Document
Class: article 2018/09/03 v1.4i Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo))
(/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/ucs/utf8x.def))
(/usr/share/texlive/texmf-dist/tex/latex/ucs/ucs.sty
(/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-global.def))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty For
additional information on amsmath, use the `?' option.
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amscls/amsthm.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
(/usr/share/texlive/texmf-dist/tex/latex/anyfontsize/anyfontsize.sty)
(/usr/share/texlive/texmf-dist/tex/latex/tools/bm.sty) (./math.aux)
(/usr/share/texlive/texmf-dist/tex/latex/ucs/ucsencs.def)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsb.fd) ! You can't
use `\spacefactor' in math mode. \@->\spacefactor \@m {} l.13
\fontsize{12}{14}\selectfont $\LaTeX $ [1] (./math.aux) ) (see the
transcript file for additional information) Output written on math.dvi
(1 page, 324 bytes). Transcript written on math.log.
Steps to view this error message:
1. install python-sympy-doc package
$ sudo apt install python-sympy-doc
2. open the following link, in your web-browser of choice
file:///usr/share/doc/python-sympy-doc/html/install.html
here is the correctly parsed doc online:
https://docs.sympy.org/1.3/install.html
Regards,
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
python-sympy-doc depends on no packages.
python-sympy-doc recommends no packages.
Versions of packages python-sympy-doc suggests:
pn python-sympy
-- no debconf information
Bug#940712: obs-studio: wrong version number in title bar and about dialog
Package: obs-studio Version: 23.2.1+dfsg1-1 Severity: normal Dear Maintainer, the version number which is shown in the title bar and about dialog is set to 0.0.1 while the current version number in sid 23.2.1 Regards, Salman -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages obs-studio depends on: ii libavcodec58 7:4.1.4-1+b2 ii libavformat58 7:4.1.4-1+b2 ii libavutil56 7:4.1.4-1+b2 ii libc6 2.29-1 ii libcurl3-gnutls 7.66.0-1 ii libgcc1 1:9.2.1-8 ii libluajit-5.1-2 2.1.0~beta3+dfsg-5.1 ii libobs0 23.2.1+dfsg1-1 ii libpython3.7 3.7.4-4 ii libqt5core5a 5.11.3+dfsg1-4 ii libqt5gui5 5.11.3+dfsg1-4 ii libqt5svg5 5.11.3-3 ii libqt5widgets5 5.11.3+dfsg1-4 ii libqt5x11extras5 5.11.3-2 ii libstdc++6 9.2.1-8 ii obs-plugins 23.2.1+dfsg1-1 obs-studio recommends no packages. obs-studio suggests no packages. -- no debconf information
Bug#940660: elpa-elpy: add Suggests: python3-rope to refactor code
Package: elpa-elpy Version: 1.31.0-1 Severity: normal Dear Nicholas, Adding this entry `Suggests: python3-rope` to debian/control ensures that we can refactor the code without error messages like this: elpy-rpc--default-error-callback: Elpy error: rope not installed, cannot refactor code. Regards -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-elpy depends on: ii dh-elpa-helper 2.0.2 ii elpa-company 0.9.9-2 ii elpa-find-file-in-project 5.7.7-1 ii elpa-highlight-indentation 0.7.0-4 ii elpa-pyvenv 1.20-2 ii elpa-s 1.12.0-3 ii elpa-yasnippet 0.13.0-3 ii emacsen-common 3.0.4 ii flake8 3.7.8-3 ii python3 3.7.3-1 ii python3-flake8 3.7.8-3 Versions of packages elpa-elpy recommends: ii emacs 1:26.1+1-4 ii emacs-gtk [emacs] 1:26.1+1-4 ii libjs-sphinxdoc 1.8.5-3 ii python3-jedi 0.14.1-1 Versions of packages elpa-elpy suggests: pn black pn elpa-pip-requirements pn python3-autopep8 pn python3-jupyter-console ii python3-pip 18.1-5 pn yapf3 -- no debconf information
Bug#935444: freecad: Freecad crashes when trying to open an IFC file
Package: freecad Version: 0.18.3+dfsg1-1 Severity: normal Dear Maintainer, When trying to open an IFC file in Freecad it crashes and I get the following error message in the terminal, Traceback (most recent call last): File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 299, in onChanged val = str(obj.Color[:3]) : maximum recursion depth exceeded while getting the str of an object Fatal Python error: Cannot recover from stack overflow. Current thread 0x7f15da6ff9c0 (most recent call first): File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 299 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 270 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 270 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File "/usr/share/freecad/Mod/Arch/ArchMaterial.py", line 333 in onChanged File
Bug#812609: tracker.debian.org: wrong versioned links for security versions
On Mon, 25 Jan 2016 16:43:38 +0100 Ricardo Mones wrote: > > The links to .dsc file wich appear on versioned links panel for security > versions are using httpredir.d.o, which always gives 40x errors for those > package versions. Example: https://tracker.debian.org/pkg/claws-mail > (3.8.1-2+deb7u1 and 3.11.1-3+deb8u1 dsc links) > Dear Recardo, I couldn't reproduce this bug in the package that you have mentioned. Are there any other packages that have this issue?
Bug#926511: jcal: migration to Salsa
Package: jcal Version: 0.4.1-2+b1 Severity: wishlist Dear Maintainer, This Debian package does not use VCS (while upstream uses git) and I would like to offer my help to migrate this package to Salsa. Is there a way that I can give a hand on this issue? Sincerely yours, Salman Mohammadi -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages jcal depends on: ii libc6 2.28-8 ii libjalali0 0.4.1-2+b1 jcal recommends no packages. jcal suggests no packages. -- no debconf information
Bug#926336: tracker.debian.org: changing the sphinx theme from default to sphinx_rtd_theme
Package: tracker.debian.org Severity: wishlist Dear Maintainer, It would be nice if we changed the documentation (sphinx) theme from *default* to *sphinx_rtd_theme*. I suppose it is more visually appealing. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#926273: tracker.debian.org: adding comments to apache and nginx samples to include let's encrypt
Package: tracker.debian.org Severity: wishlist Dear Maintainer, It would be nice if we added commented lines to the Apache vhost and NginX Server Block samples, which are residing in *debian/* to demonstrate a sample usage of Let's Encrypt. Nginx: - # If you are using Let's Encrypt, you may use the following: # ssl_certificate /etc/letsencrypt/live/domain_name.tld/fullchain.pem; # ssl_certificate_key /etc/letsencrypt/live/domain_name.tld/privkey.pem; Apache: -- # If you are using Let's Encrypt, you may use the following: # SSLCertificateFile /etc/letsencrypt/live/domain_name.tld/fullchain.pem # SSLCertificateKeyFile /etc/letsencrypt/live/domain_name.tld/privkey.pem -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#925933: mixxx: menu bar goes black after making the software full screen
Package: mixxx Version: 2.2.0~dfsg-1 Severity: normal Dear Maintainer, After making the software full screen, the menu bar goes black and it is barely visible. Even after reverting the size, the color does not change to its initial state. Steps to reproduce: --- - Press *F11* or click on *View > Full Screen* -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mixxx depends on: ii libc6 2.28-8 ii libchromaprint1 1.4.3-3 ii libebur128-1 1.2.4-2 ii libflac8 1.3.2-3 ii libgcc1 1:8.3.0-2 ii libgl1 1.1.0-1 ii libglib2.0-0 2.58.3-1 ii libhidapi-libusb0 0.8.0~rc1+git20140818.d17db57+dfsg-2 ii libid3tag0 0.15.1b-14 ii liblilv-0-0 0.24.2~dfsg0-2 ii libmad0 0.15.1b-10 ii libogg0 1.3.2-1+b1 ii libopusfile0 0.9+20170913-1 ii libportaudio2 19.6.0-1 ii libportmidi0 1:217-6 ii libprotobuf-lite17 3.6.1.3-1 ii libqt5concurrent5 5.11.3+dfsg1-1 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5dbus5 5.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5network5 5.11.3+dfsg1-1 ii libqt5opengl5 5.11.3+dfsg1-1 ii libqt5script5 5.11.3+dfsg-3 ii libqt5scripttools5 5.11.3+dfsg-3 ii libqt5sql5 5.11.3+dfsg1-1 ii libqt5sql5-sqlite 5.11.3+dfsg1-1 ii libqt5svg5 5.11.3-2 ii libqt5widgets5 5.11.3+dfsg1-1 ii libqt5x11extras5 5.11.3-2 ii libqt5xml5 5.11.3+dfsg1-1 ii librubberband2 1.8.1-7 ii libshout3 2.4.1-2 ii libsndfile1 1.0.28-6 ii libsoundtouch1 2.1.2+ds1-1 ii libsqlite3-0 3.27.2-1 ii libstdc++6 8.3.0-2 ii libtag1v5 1.11.1+dfsg.1-0.3 ii libupower-glib3 0.99.10-1 ii libusb-1.0-0 2:1.0.22-2 ii libvorbis0a 1.3.6-2 ii libvorbisenc2 1.3.6-2 ii libvorbisfile3 1.3.6-2 ii libx11-6 2:1.6.7-1 ii mixxx-data 2.2.0~dfsg-1 mixxx recommends no packages. Versions of packages mixxx suggests: ii evince [pdf-viewer] 3.30.2-3 -- no debconf information
Bug#925589: reportbug: reporting bugs to gitlab
Package: reportbug Version: 7.5.2 Severity: wishlist Dear Maintainer, It would be nice if we could add a feature to be able to optionally report bugs to gitlab instead of debbugs. I would like to volunteer to work on this feature but I need to familiarize myself first with reportbug code. considerations: - Reporting a bug needs a username on salsa - Extra dependencies that will be introduced: python3-gitlab -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages reportbug depends on: ii apt 1.8.0 ii python3 3.7.2-1 ii python3-reportbug 7.5.2 ii sensible-utils 0.0.12 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums ii dlocate 1.07+nmu1 pn emacs24-bin-common | emacs25-bin-common ii exim4-daemon-light [mail-transport-agent] 4.92-2 ii file 1:5.35-4 ii gnupg 2.2.12-1 pn python3-urwid pn reportbug-gtk ii xdg-utils 1.1.3-1 Versions of packages python3-reportbug depends on: ii apt 1.8.0 ii file 1:5.35-4 ii python3 3.7.2-1 ii python3-apt 1.8.4 ii python3-debian 0.1.34 ii python3-debianbts 2.8.2 ii python3-requests 2.21.0-1 python3-reportbug suggests no packages. -- no debconf information
Bug#925459: yelp: xkbcommon: ERROR: Key "" added to modifier map for multiple modifiers; Using Control, ignoring Lock
Package: yelp Version: 3.31.90-1 Severity: normal Dear Maintainer, Running *yelp* from the command line, throws the following error message: xkbcommon: ERROR: Key "" added to modifier map for multiple modifiers; Using Control, ignoring Lock xkbcommon: ERROR: Key "" added to modifier map for multiple modifiers; Using Control, ignoring Lock -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages yelp depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii libc6 2.28-8 ii libglib2.0-0 2.58.3-1 ii libgtk-3-0 3.24.5-1 ii libwebkit2gtk-4.0-37 2.22.6-1 ii libyelp0 3.31.90-1 ii man-db 2.8.5-2 ii python3-distro 1.3.0-1 ii yelp-xsl 3.31.90-1 Versions of packages yelp recommends: ii fonts-dejavu 2.37-1 yelp suggests no packages. -- no debconf information
Bug#925423: elpa-debian-el: unable to report a bug in package reportbug
On Sun, 24 Mar 2019 22:19:58 -0300 David Bremner wrote: > If possible, I'd suggest using a different value of > message-send-mail-function (I think it's initialized from > send-mail-function). > > d > > Dear David, I assigned *message-smtpmail-send-it* to the variable and I could send the message with no problem without using an external mail client.
Bug#925423: elpa-debian-el: unable to report a bug in package reportbug
Dear David, The content of the variable *message-send-mail-function* as you have correctly guessed is *message-send-mail-with-mailclient*. I don't know how to test this feature (e.g. sending using smtp) without spamming BTS. I should also add that I have this bug only with *reportbug* package and not other packages, that I have previously tried. On Sun, 24 Mar 2019 22:19:58 -0300 David Bremner wrote: > Salman Mohammadi writes: > > > Package: elpa-debian-el > > Version: 37.8 > > Severity: important > > > > Dear Maintainer, > > > > I'm unable to report a bug which is affecting the package *reportbug*. > > > > Steps to reproduce: > > > > 1. M-x debian-bug > > 2. Report a bug for a [P]ackage or [F]ile: P > > 3. package name: reportbug > > 4. Severity: normal > > 5. (Very) brief summary of problem: dummy bug > > > > > > but When I click on *Send Message*, a new window in Mozilla Thunderbird > > will be shown with the following content: > > > > > > --=-=-= > > Content-Type: text/plain > > > > Package: reportbug > > Version: 7.5.2 > > Severity: normal > > This seems to be an upstream bug in emacs. What is your setting of the > variable message-send-mail-function (you can check with C-h v)? > > If, as I suspect, it is message-send-mail-with-mailclient, then I think > I understand the problem you are seeing. Basically that function only > supports text/plain messages, while debian-bug sends it MIME. > > If possible, I'd suggest using a different value of > message-send-mail-function (I think it's initialized from > send-mail-function). > > d > >
Bug#925423: elpa-debian-el: unable to report a bug in package reportbug
Package: elpa-debian-el Version: 37.8 Severity: important Dear Maintainer, I'm unable to report a bug which is affecting the package *reportbug*. Steps to reproduce: 1. M-x debian-bug 2. Report a bug for a [P]ackage or [F]ile: P 3. package name: reportbug 4. Severity: normal 5. (Very) brief summary of problem: dummy bug but When I click on *Send Message*, a new window in Mozilla Thunderbird will be shown with the following content: --=-=-= Content-Type: text/plain Package: reportbug Version: 7.5.2 Severity: normal Dear Maintainer, -- Package-specific info: --=-=-= Content-Type: text/plain Content-Disposition: attachment Content-Description: Bug script output ** /home/salman/.reportbugrc: reportbug_version "7.5.2" mode novice ui text realname "Salman Mohammadi" email "sal...@smoha.org" --=-=-= Content-Type: text/plain *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** which makes it unable to send the message, because of the header. I get the following message as the error message from BTS: >Your message didn't have a Package: line at the very first line of the >mail body (part of the pseudo-header), or didn't have a Package: line >at all. Unfortunatly, this means that your message has been ignored >completely. > >Without this information we are unable to categorise or otherwise deal >with your problem report. Please _resubmit_ your report to >sub...@bugs.debian.org and tell us which package the >report is for. For help, check out >https://www.debian.org/Bugs/Reporting. > >Your message was dated Sun, 24 Mar 2019 22:39:07 +0100 and had >message-id >and subject reportbug: SOMETHING-HERE. >The complete text of it is attached to this message. > >If you need any assistance or explanation please contact >ow...@bugs.debian.org and include the the attached >message. > >If you didn't send the attached message (spam was sent forging your >from address), we apologize; please disregard this message -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-debian-el depends on: ii bzip2 1.0.6-9 ii dpkg 1.19.5 ii emacsen-common 3.0.4 ii reportbug 7.5.2 ii xz-utils 5.2.4-1 Versions of packages elpa-debian-el recommends: ii emacs 1:26.1+1-3.2 ii emacs-gtk [emacs] 1:26.1+1-3.2 ii wget 1.20.1-1 elpa-debian-el suggests no packages. -- no debconf information --=-=-=--
Bug#925422: reportbug: suggesting non-existent emacs24-bin-common or emacs25-bin-common
Package: reportbug Version: 7.5.2 Severity: normal Dear Maintainer, *reportbug* suggests installing *emacs24-bin-common* or *emacs25-bin-common* which are both currently non-existent in Buster. Could replacing *emacs24-bin-common | emacs25-bin-common* with *emacs-bin-common* be an option? -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages reportbug depends on: ii apt 1.8.0 ii python3 3.7.2-1 ii python3-reportbug 7.5.2 ii sensible-utils 0.0.12 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums ii dlocate 1.07+nmu1 pn emacs24-bin-common | emacs25-bin-common ii exim4-daemon-light [mail-transport-agent] 4.92-2 ii file 1:5.35-4 ii gnupg 2.2.12-1 pn python3-urwid pn reportbug-gtk ii xdg-utils 1.1.3-1 Versions of packages python3-reportbug depends on: ii apt 1.8.0 ii file 1:5.35-4 ii python3 3.7.2-1 ii python3-apt 1.8.4 ii python3-debian 0.1.34 ii python3-debianbts 2.8.2 ii python3-requests 2.21.0-1 python3-reportbug suggests no packages. -- no debconf information
Bug#925277: freecad: there's no manpage entry
Package: freecad Version: 0.18~pre1+dfsg1-5 Severity: normal Dear Maintainer, There is no manpage entry after installing freecad but there is one here *debian/freecad.1*, which needs to be updated. But I suppose having an old manpage which misses some options is better than having no manpage. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages freecad depends on: ii freecad-python3 0.18~pre1+dfsg1-5 Versions of packages freecad recommends: ii calculix-ccx 2.11-1+b3 ii graphviz 2.40.1-5+b2 Versions of packages freecad suggests: pn freecad-doc pn povray pn python-collada -- no debconf information
Bug#925220: vlc: QObject::~QObject: Timers cannot be stopped from another thread
Package: vlc Version: 3.0.6-1 Severity: normal Dear Maintainer, I was streaming a video from youtube using *Media > Open Network Stream* and then closed VLC using the close button. Now I cannot open vlc by clicking on *VLC Media Player* from menu and I have to open it from terminal. If I open vlc from terminal, after closing VLC, I get this message: QObject::~QObject: Timers cannot be stopped from another thread -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vlc depends on: ii vlc-bin 3.0.6-1 ii vlc-plugin-base 3.0.6-1 ii vlc-plugin-qt 3.0.6-1 ii vlc-plugin-video-output 3.0.6-1 Versions of packages vlc recommends: ii vlc-l10n 3.0.6-1 ii vlc-plugin-notify 3.0.6-1 ii vlc-plugin-samba 3.0.6-1 ii vlc-plugin-skins2 3.0.6-1 ii vlc-plugin-video-splitter 3.0.6-1 ii vlc-plugin-visualization 3.0.6-1 vlc suggests no packages. Versions of packages libvlc-bin depends on: ii libc6 2.28-8 ii libvlc5 3.0.6-1 Versions of packages libvlc5 depends on: ii libc6 2.28-8 ii libvlccore9 3.0.6-1 Versions of packages libvlc5 recommends: ii libvlc-bin 3.0.6-1 Versions of packages vlc-bin depends on: ii libc6 2.28-8 ii libvlc-bin 3.0.6-1 ii libvlc5 3.0.6-1 Versions of packages vlc-plugin-base depends on: ii liba52-0.7.4 0.7.4-19 ii libaom0 1.0.0-3 ii libarchive13 3.3.3-4 ii libaribb24-0 1.0.3-2 ii libasound2 1.1.8-1 ii libass9 1:0.14.0-2 ii libavahi-client3 0.7-4+b1 ii libavahi-common3 0.7-4+b1 ii libavc1394-0 0.5.4-5 ii libavcodec58 7:4.1.1-1 ii libavformat58 7:4.1.1-1 ii libavutil56 7:4.1.1-1 ii libbasicusageenvironment1 2018.11.26-1 ii libbluray2 1:1.1.0-1 ii libc6 2.28-8 ii libcairo2 1.16.0-4 ii libcddb2 1.3.2-6 ii libchromaprint1 1.4.3-3 ii libcrystalhd3 1:0.0~git20110715.fdd2f19-13 ii libdbus-1-3 1.12.12-1 ii libdc1394-22 2.2.5-1 ii libdca0 0.0.6-1 ii libdvbpsi10 1.3.2-1 ii libdvdnav4 6.0.0-1 ii libdvdread4 6.0.1-1 ii libebml4v5 1.3.6-2 ii libfaad2 2.8.8-1 ii libflac8 1.3.2-3 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3 ii libfribidi0 1.0.5-3.1 ii libgcc1 1:8.3.0-2 ii libgcrypt20 1.8.4-5 ii libglib2.0-0 2.58.3-1 ii libgnutls30 3.6.6-2 ii libgpg-error0 1.35-1 ii libgroupsock8 2018.11.26-1 ii libharfbuzz0b 2.3.1-1 ii libixml10 1:1.8.4-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libkate1 0.4.1-9 ii liblirc-client0 0.10.1-5 ii liblivemedia64 2018.11.26-1 ii liblua5.2-0 5.2.4-1.1+b2 ii libmad0 0.15.1b-10 ii libmatroska6v5 1.4.9-1 ii libmicrodns0 0.0.10-1 ii libmpcdec6 2:0.1~r495-1+b2 ii libmpeg2-4 0.5.1-8 ii libmpg123-0 1.25.10-2 ii libmtp9 1.1.16-2 ii libncursesw6 6.1+20181013-2 ii libnfs12 3.0.0-2 ii libogg0 1.3.2-1+b1 ii libopenmpt-modplug1 0.4.3-1 ii libopus0 1.3-1 ii libpng16-16 1.6.36-5 ii libpostproc55 7:4.1.1-1 ii libprotobuf-lite17 3.6.1.3-1 ii libpulse0 12.2-4 ii libraw1394-11 2.1.2-1+b1 ii libresid-builder0c2a 2.1.1-15 ii librsvg2-2 2.44.10-1 ii libsamplerate0 0.1.9-2 ii libsdl-image1.2 1.2.12-10 ii libsdl1.2debian 1.2.15+dfsg2-4 ii libsecret-1-0 0.18.7-1 ii libshine3 3.1.1-2 ii libshout3 2.4.1-2 ii libsidplay2 2.1.1-15 ii libsndio7.0 1.5.0-3 ii libsoxr0 0.1.2-3 ii libspatialaudio0 0.3.0+git20180730+dfsg1-2 ii libspeex1 1.2~rc1.2-1+b2 ii libspeexdsp1 1.2~rc1.2-1+b2 ii libssh2-1 1.8.0-2 ii libstdc++6 8.3.0-2 ii libswscale5 7:4.1.1-1 ii libsystemd0 241-1 ii libtag1v5 1.11.1+dfsg.1-0.3 ii libtheora0 1.1.1+dfsg.1-15 ii libtinfo6 6.1+20181013-2 ii libtwolame0 0.3.13-4 ii libudev1 241-1 ii libupnp13 1:1.8.4-2 ii libusageenvironment3 2018.11.26-1 ii libva-drm2 2.4.0-1 ii libva2 2.4.0-1 ii libvlccore9 [vlc-plugin-abi-3-0-0f] 3.0.6-1 ii libvorbis0a 1.3.6-2 ii libvorbisenc2 1.3.6-2 ii libx264-155 2:0.155.2917+git0a84d98-2 ii libx265-165 2.9-4 ii libxcb-keysyms1 0.4.0-1+b2 ii libxcb1 1.13.1-2 ii libxml2 2.9.4+dfsg1-7+b3 ii libzvbi0 0.2.35-16 ii vlc-data 3.0.6-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages vlc-plugin-base recommends: ii xdg-utils 1.1.3-1 Versions of packages vlc-plugin-base suggests: pn libdvdcss2 Versions of packages vlc-plugin-notify depends on: ii libc6 2.28-8 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-1 ii libgtk-3-0 3.24.5-1 ii libnotify4 0.7.7-4 ii libvlccore9 [vlc-plugin-abi-3-0-0f] 3.0.6-1 Versions of packages vlc-plugin-qt depends on: ii libc6 2.28-8 ii libgcc1 1:8.3.0-2 ii libqt5core5a 5.11.3+dfsg-5 ii libqt5gui5 5.11.3+dfsg-5 ii libqt5svg5 5.11.3-2 ii libqt5widgets5 5.11.3+dfsg-5 ii libqt5x11extras5 5.11.3-2 ii libstdc++6 8.3.0-2 ii libvlccore9 [vlc-plugin-abi-3-0-0f] 3.0.6-1 ii libwayland-client0 1.16.0-1 ii libx11-6 2:1.6.7-1 Versions of packages vlc-plugin-qt recommends: ii vlc-bin 3.0.6-1 Versions of packages vlc-plugin-skins2 depends on: ii fonts-freefont-ttf 20120503-9 ii libc6 2.28-8 ii libfreetype6 2.9.1-3 ii
Bug#886955: gedit: gedit does not share clipboard with other applications, such as google chrome, gnome terminal
Hi, I also couldn't reproduce this bug on Debian Stretch (gedit = 3.22.0-2) or Debian Buster (gedit = 3.30.2-2). On Thu, 11 Jan 2018 13:59:17 -0500 Dongliang Mu wrote: > Package: gedit > Version: 3.22.1-2 > Severity: important > Tags: upstream > > As the title shows, gedit does not share clipboard with other applications. > When I copy some text from gedit with "Ctrl+C" or right click of mouse, and > paste it to gnome terminal or google chrome, the text does not show up in the > application. > > > > -- Package-specific info: > Active plugins: > - 'docinfo' > - 'spell' > - 'filebrowser' > - 'modelines' > - 'time' > > No plugin installed in $HOME. > > Module versions: > - glib 2.54.2 > - gtk+ 3.22.26 > - gtksourceview > - pygobject > - enchant > - iso-codes 3.77 > > > -- System Information: > Debian Release: buster/sid > APT prefers testing-debug > APT policy: (500, 'testing-debug'), (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages gedit depends on: > ii gedit-common 3.22.1-2 > ii gir1.2-glib-2.0 1.54.1-4 > ii gir1.2-gtk-3.0 3.22.26-2 > ii gir1.2-gtksource-3.0 3.24.6-1 > ii gir1.2-pango-1.0 1.40.14-1 > ii gir1.2-peas-1.0 1.22.0-2 > ii gsettings-desktop-schemas 3.24.1-2 > ii iso-codes 3.77-1 > ii libatk1.0-0 2.26.1-2 > ii libc6 2.25-5 > ii libcairo-gobject2 1.15.8-3 > ii libcairo2 1.15.8-3 > ii libenchant1c2a 1.6.0-11.1 > ii libgdk-pixbuf2.0-0 2.36.11-1 > ii libgirepository-1.0-1 1.54.1-4
Bug#924204: persepolis: the packaged version is outdated
Dear Moein, Would you please specify what the problem is? I could create the deb package and then successfully installed it, and also checked new features like downloading from youtube, and it was working for me. To build the deb package I used $ dpkg-buildpackage -b -rfakeroot -us -uc On Sun, 10 Mar 2019 23:41:18 +0100 Moein Alinaghian wrote: > Dear Salman, > > The problem is the incompatibility of the setup.py and debianhelper. > It can be solved either with a patch in the Debian Package or directly > in upstream. Solving it in the upstream is definitely a better idea, > but it requires to test it in different operating systems, as it > suppose to work in another operating systems as well. > > The best help would be rewriting a compatible setup.py and send it to > the upstream. > > -- > Sincerely yours, > Moein Alinaghian > >
Bug#840336: elpa-markdown-mode: Freezes Emacs when using TeX input mode in a header
Dear Maintainer, I cannot reproduce this bug on Debian Buster. Would you please check if the current issue is still valid? A newer version of markdown-mode is in the repository and it seems that this bug has been resolved in newer versions. On Mon, 10 Oct 2016 20:00:46 +0200 Christophe Troestler wrote: > Package: elpa-markdown-mode > Version: 2.1-1 > Severity: normal > > Dear Maintainer, > > Markdown mode makes Emacs use 100% CPU and be unresponsive (C-g has no > effect) when using TeX input method in a header followed by an URL. > > Steps to reproduce: > > - Run: emacs -q > - Execute: > > (load > "/usr/share/emacs/site-lisp/elpa-src/markdown-mode-2.1/markdown-mode.el") > > - Create a file, say a.md, containing > > # > > http:// > > - Place the cursor after "#". > > - Switch to TeX input method (C-\ and select TeX) > > - Type \ (then Emacs freezes) > > > emacs-25.1.50.1 and emacs-26.0.50.1 (compiled from the Git repository) > have the same problem. > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (900, 'testing'), (400, 'unstable'), (200, 'stable'), > (100, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.7.3 (SMP w/8 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages elpa-markdown-mode depends on: > ii emacs 46.1 > ii emacs24 [emacsen] 24.5+1-7 > ii emacsen-common 2.0.8 > > elpa-markdown-mode recommends no packages. > > elpa-markdown-mode suggests no packages. > > -- no debconf information > >
Bug#924297: elpa-eshell-git-prompt: missing-powerline-fonts
Package: elpa-eshell-git-prompt Version: 0.1.2-2 Severity: normal Dear Maintainer, choosing powerline theme for the eshell requires the package `fonts-powerline` otherwise the intended symbols in the eshell prompt could not be shown. I suggest you use `fonts-powerline` as a recommendation for this package. Steps to reproduce: 1. Install elpa-eshell-git-prompt from the repo 2. use the following line of code in the init file (eshell-git-prompt-use-theme 'powerline) 3. run eshell -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-eshell-git-prompt depends on: ii elpa-dash 2.14.1+dfsg-1 ii emacsen-common 3.0.4 Versions of packages elpa-eshell-git-prompt recommends: ii emacs 1:26.1+1-3.2 ii emacs-gtk [emacs] 1:26.1+1-3.2 elpa-eshell-git-prompt suggests no packages. -- no debconf information
Bug#923347: No sensible security support due to Oracle's policies
Dear Mortiz, There is also another Python connector for MariaDB/MySQL in the repos, `python3-mysqldb` and `python-mysqldb`. This is not a pure python package but a wrapper around C module. On Tue, 26 Feb 2019 20:32:06 +0100 Moritz Muehlenhoff wrote: > - Aside from the packaged software and given that this is the only Python > binding for mysql/mariadb. > > Cheers, > Moritz
Bug#923465: fixed in freecad 0.18~pre1+dfsg1-5
Dear Maintainer, I could install this package (0.18~pre1+dfsg1-4) with no problem and this bug seems to be resolved. But on the tracker page, this package has been marked for autoremoval on 29 March, with this message: Version 0.18~pre1+dfsg1-4 of freecad is marked for autoremoval from testing on Fri 29 Mar 2019. It is affected by #923465. You should try to prevent the removal by fixing these RC bugs. $ freecad FreeCAD 0.18, Libs: 0.18R © Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2019 # ### # # # # # # # ## # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # ## ## ## # # ### # # ## ## ## [Errno 2] No such file or directory: '/usr/share/freecad/examples' On Sat, 02 Mar 2019 10:20:00 + Kurt Kremitzki wrote: > Source: freecad > Source-Version: 0.18~pre1+dfsg1-5 > > We believe that the bug you reported is fixed in the latest version of > freecad, which is due to be installed in the Debian FTP archive. > > A summary of the changes between this version and the previous one is > attached. > > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to 923...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Kurt Kremitzki (supplier of updated freecad package) >
Bug#820453: paraview: "Help -> ParaView Guide" gives error
Package: paraview Version: 5.4.1+dfsg4-3.1+b2 Severity: normal Dear Anton, Do you still consider 200 MB inappropriate for Debian? The generated PDF is around 50 MB and we currently have doc packages in Debian which have a large size, like gnome-users-docs (Installed-Size: 58.0 MB), python-sympy-doc (Installed-Size: 60.6 MB), texlive-pstricks-doc (Installed-Size: 318 MB) > User Guide is a separate project [1]. I would not upload it > to Debian because of its size (about 200Mb). Will probably > try to provide a download link. > [1] https://gitlab.kitware.com/paraview/paraview-guide-ce > Anton -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages paraview depends on: ii libavcodec58 7:4.1.1-1 ii libavformat58 7:4.1.1-1 ii libavutil56 7:4.1.1-1 ii libc6 2.28-7 ii libcgns3.3 3.3.0-6+b2 ii libexpat1 2.2.6-1 ii libfreetype6 2.9.1-3 ii libgcc1 1:8.3.0-2 ii libgl1 1.1.0-1 ii libgl2ps1.4 1.4.0+dfsg1-2 ii libglew2.1 2.1.0-4 ii libhdf5-103 1.10.4+repack-10 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libjsoncpp1 1.7.4-3 ii libnetcdf13 1:4.6.2-1 ii libogg0 1.3.2-1+b1 ii libopenmpi3 3.1.3-10 ii libpng16-16 1.6.36-5 ii libprotobuf17 3.6.1.3-1 ii libpython2.7 2.7.16~rc1-1 ii libqt5core5a 5.11.3+dfsg-5 ii libqt5gui5 5.11.3+dfsg-5 ii libqt5help5 5.11.3-4 ii libqt5network5 5.11.3+dfsg-5 ii libqt5widgets5 5.11.3+dfsg-5 ii libqt5x11extras5 5.11.3-2 ii libstdc++6 8.3.0-2 ii libswscale5 7:4.1.1-1 ii libtheora0 1.1.1+dfsg.1-15 ii libtiff5 4.0.10-4 ii libx11-6 2:1.6.7-1 ii libxml2 2.9.4+dfsg1-7+b3 ii libxt6 1:1.1.5-1 ii python-autobahn 17.10.1+dfsg1-3 ii python-matplotlib 2.2.3-6 ii python-mpi4py 2.0.0-3+b3 ii python-six 1.12.0-1 ii python-twisted 18.9.0-3 ii tcl [tclsh] 8.6.9+1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages paraview recommends: ii mpi-default-bin 1.13 ii paraview-doc 5.4.1+dfsg4-3.1 ii paraview-python 5.4.1+dfsg4-3.1+b2 Versions of packages paraview suggests: pn h5utils ii hdf5-tools 1.10.4+repack-10 -- no debconf information
Bug#924204: persepolis: the packaged version is outdated
Package: persepolis Version: 3.0.1-1 Severity: normal Dear Maintainer, The new version of Persepolis has been released a year ago. If there's anything which stops you from updating the packaged version, I would be happy to give a hand. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages persepolis depends on: ii aria2 1.34.0-3 ii libnotify-bin 0.7.7-4 ii libqt5svg5 5.11.3-2 ii python3 3.7.2-1 ii python3-pyqt5 5.11.3+dfsg-1+b3 ii python3-requests 2.21.0-1 Versions of packages persepolis recommends: ii pulseaudio 12.2-4 ii python3-psutil 5.5.1-1 ii python3-setproctitle 1.1.10-1+b2 ii sound-theme-freedesktop 0.8-2 persepolis suggests no packages. -- no debconf information
Bug#924196: paraview: warning on wayland, Use QT_QPA_PLATFORM=wayland
Package: paraview Version: 5.4.1+dfsg4-3.1+b2 Severity: normal Dear Maintainer, When I invoke `paraview` from the shell prompt it prints the following message: $ paraview Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages paraview depends on: ii libavcodec58 7:4.1.1-1 ii libavformat58 7:4.1.1-1 ii libavutil56 7:4.1.1-1 ii libc6 2.28-7 ii libcgns3.3 3.3.0-6+b2 ii libexpat1 2.2.6-1 ii libfreetype6 2.9.1-3 ii libgcc1 1:8.3.0-2 ii libgl1 1.1.0-1 ii libgl2ps1.4 1.4.0+dfsg1-2 ii libglew2.1 2.1.0-4 ii libhdf5-103 1.10.4+repack-10 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libjsoncpp1 1.7.4-3 ii libnetcdf13 1:4.6.2-1 ii libogg0 1.3.2-1+b1 ii libopenmpi3 3.1.3-10 ii libpng16-16 1.6.36-5 ii libprotobuf17 3.6.1.3-1 ii libpython2.7 2.7.16~rc1-1 ii libqt5core5a 5.11.3+dfsg-5 ii libqt5gui5 5.11.3+dfsg-5 ii libqt5help5 5.11.3-4 ii libqt5network5 5.11.3+dfsg-5 ii libqt5widgets5 5.11.3+dfsg-5 ii libqt5x11extras5 5.11.3-2 ii libstdc++6 8.3.0-2 ii libswscale5 7:4.1.1-1 ii libtheora0 1.1.1+dfsg.1-15 ii libtiff5 4.0.10-4 ii libx11-6 2:1.6.7-1 ii libxml2 2.9.4+dfsg1-7+b3 ii libxt6 1:1.1.5-1 ii python-autobahn 17.10.1+dfsg1-3 ii python-matplotlib 2.2.3-6 ii python-mpi4py 2.0.0-3+b3 ii python-six 1.12.0-1 ii python-twisted 18.9.0-3 ii tcl [tclsh] 8.6.9+1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages paraview recommends: ii mpi-default-bin 1.13 ii paraview-doc 5.4.1+dfsg4-3.1 ii paraview-python 5.4.1+dfsg4-3.1+b2 Versions of packages paraview suggests: pn h5utils ii hdf5-tools 1.10.4+repack-10 -- no debconf information
