Bug#1029105: /usr/bin/getmails: 32: Bad substitution

Package: getmail6 Version: 6.18.11-1 Severity: normal X-Debbugs-Cc: rharw...@club.cc.cmu.edu Dear Maintainer, When running getmails, I get this: $ getmails /usr/bin/getmails: 32: Bad substitution $ and it bails out without downloading any mail. Of course it's still possible to run

Bug#1021846: [programmer11...@programist.ru: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem]

Steve McIntyre writes: > Hi all! > > программист некто (in CC) reported this bug a few weeks back in > Debian. Since I applied the bundle of filesystem bounds-checking fixes > a few months back, he can't run grub-install. He's done the work to > determine that the patch that breaks things for

Bug#1007226: GLib:ERROR:../../../glib/gtimezone.c:2051:g_time_zone_new_offset: assertion failed: (tz != NULL)

Package: libglib2.0-0 Version: 2.70.4-1 Followup-For: Bug #1007226 X-Debbugs-Cc: rharw...@club.cc.cmu.edu The crash seems to be triggered by one particular message, which I've uploaded in case it helps: https://gist.github.com/frozencemetery/cc73375f628c6dbfdbb4834396db9a63 Be well, --Robbie

Bug#1007226: GLib:ERROR:../../../glib/gtimezone.c:2051:g_time_zone_new_offset: assertion failed: (tz != NULL)

Package: libglib2.0-0 Version: 2.70.4-1 Followup-For: Bug #1007226 X-Debbugs-Cc: rharw...@club.cc.cmu.edu > I think we will really need a backtrace with at least GLib debug symbols, > and preferably GMime too, so that we can tell what identifier we're trying > to parse here. (Or you could try

Bug#1007226: GLib:ERROR:../../../glib/gtimezone.c:2051:g_time_zone_new_offset: assertion failed: (tz != NULL)

Package: libglib2.0-0 Version: 2.71.3-1 Severity: normal X-Debbugs-Cc: rharw...@club.cc.cmu.edu Dear Maintainer, When running `notmuch new`, I get this error: ** GLib:ERROR:../../../glib/gtimezone.c:2051:g_time_zone_new_offset: assertion failed: (tz != NULL) Bail out!

Bug#988817: fwupd: Recommends on nonexistent package secureboot-db

Package: fwupd Version: 1.7.4-2 Followup-For: Bug #988817 X-Debbugs-Cc: rharw...@club.cc.cmu.edu It's been rather a while, so I no longer remember, but it may have just been my own curiosity. I did check again and none of the apt* that I use seem to complain. Be well, --Robbie

Bug#995084: mnemosyne: missing dependency on python3-argon2

Package: mnemosyne Version: 2.8+ds1-1 Followup-For: Bug #995084 X-Debbugs-Cc: rharw...@club.cc.cmu.edu Control: tag -1 patch Dear Maintainer, mnemosyne needs to depend on python3-argon2. Without that, it will fail with the traceback (duplicated in popup): An unexpected error has occurred.

Bug#994507: O: gssproxy -- Privilege separation daemon for GSSAPI

Package: wnpp Severity: normal X-Debbugs-Cc: rharw...@club.cc.cmu.edu Control: affects -1 src:gssproxy I intend to orphan the gssproxy package. The package description is: Applications can choose to use GSS-Proxy for GSSAPI credential management, which means that they will not have direct

Bug#994508: O: python-gssapi -- Python 3 interface to GSSAPI

Package: wnpp Severity: normal X-Debbugs-Cc: rharw...@club.cc.cmu.edu Control: affects -1 src:python-gssapi I intend to orphan the python-gssapi package. The package description is: Python3 Bindings for GSSAPI. These bindings are for both RFC 2743/2744 and many extensions. They are native

Bug#989021: rxvt-unicode: new usptream version available: 9.26

Source: rxvt-unicode Severity: normal X-Debbugs-Cc: rharw...@club.cc.cmu.edu Dear Maintainer, Version 9.26 is available upstream: http://dist.schmorp.de/rxvt-unicode/ (This isn't particularly high priority for me since you've already patched the recent CVE.) Thanks, --Robbie

Bug#988817: fwupd: Recommends on nonexistent package secureboot-db

Package: fwupd Version: 1.5.7-3 Severity: minor X-Debbugs-Cc: rharw...@club.cc.cmu.edu Dear Maintainer, fwupd currently has: Recommends: python3, bolt, dbus, secureboot-db, udisks2, fwupd-signed but there is no package called secureboot-db. May you be well, --Robbie -- System

Bug#988816: fwupd: cannot install with fwupd-amd64-signed

Package: fwupd Version: 1.5.7-3 Severity: normal X-Debbugs-Cc: rharw...@club.cc.cmu.edu Dear Maintainer, It's not currently possible to update to fwupd-1.5.7-3: fwupd-amd64-signed : Depends: fwupd (= 1.5.7-3) but 1.5.7-4 is to be installed >From the outside it looks like these two need to

Bug#985744: libapache2-mod-auth-gssapi: Upstream repo has moved

Package: libapache2-mod-auth-gssapi Severity: normal X-Debbugs-Cc: rharw...@club.cc.cmu.edu Dear Maintainer, We've moved the repo for mod_auth_gssapi to https://github.com/gssapi/mod_auth_gssapi . GitHub should redirect everything, but just in case. Thanks, --Robbie -- System Information:

Bug#978931: gssproxy: CVE-2020-12658

Package: gssproxy Followup-For: Bug #978931 X-Debbugs-Cc: rharw...@club.cc.cmu.edu Control: severity -1 minor Control: close -1 Hi, I (upstream and downstream maintainer) do not believe this is CVE-worthy and have filed dispute claim with Mitre. The code change in question only happens in a

Bug#966640: build-depends: debhelper-compat (= 13) cannot be satisfied

Control: reassign -1 aptitude Aha, makes sense. Sorry to bother! Thanks, --Robbie

Bug#963949: aptitude: "search aborted by fatal exception" during upgrade

Package: aptitude Version: 0.8.13-1+b1 Severity: normal Dear Maintainer, ``` frozencemetery@kirtar:~$ sudo aptitude full-upgrade The following NEW packages will be installed: libmfx1{a} libpocketsphinx3{a} librabbitmq4{a} libsphinxbase3{a} libsrt1-gnutls{a} The following packages will be

Bug#959186: gssproxy: kerberos credentials not looked into the classical file

Hi Vincent, I disagree about "usually", but I have a larger question, which is: why are you using gssproxy if you want the credentials in an easily accessible location? The entire point of the daemon is privilege separation. Thanks, --Robbie On April 30, 2020 10:48:29 AM EDT, Vincent Danjean

Bug#959190: gssproxy: Log flooded by gssproxy

Hi Vincent, Please see `man gssproxy.conf` for logging options. You probably want to set debug_level to 0 to disable logging. Thanks, --Robbie On April 30, 2020 11:03:29 AM EDT, Vincent Danjean wrote: >Package: gssproxy >Version: 0.8.0-1.1 >Severity: important > > Hi, > > On a system with

Bug#955011: Fwd: Bug#955011: imap-dl: depends explicitly on python3-gssapi

on the library's presence. Patch for that attached. Thanks, --Robbie signature.asc Description: PGP signature >From 2a6d814dbe9976e55edd152982e60d1111a6ce61 Mon Sep 17 00:00:00 2001 From: Robbie Harwood Date: Fri, 27 Mar 2020 13:46:42 -0400 Subject: [PATCH] imap-dl: Fix failure wh

Bug#950514: gssproxy: Provided conf file ignored due to bad naming

Control: reassign -1 libini-config5

Bug#950514: gssproxy: Provided conf file ignored due to bad naming

Control: reassign -1 libini_config5 I believe this is https://pagure.io/SSSD/ding-libs/3182 Thanks, --Robbie

Bug#928356: elpa-magit: diff buffer when committing is often useless/wrong

Package: elpa-magit Version: 2.90.1-2 Severity: normal Dear Maintainer, When committing changes without using staging (i.e., with `git commit -a` or `git commit explicit/path/to/files`), the magit-diff buffer which is spawned shows the diff for the most recent commit to master - not the proposed

Bug#924418: libvirt-daemon-system: apparmor prevents libvirtd from spawning VMs

Package: libvirt-daemon-system Version: 5.0.0-1 Severity: important Dear Maintainer, When I attempt to spawn a QEMU/kvm VM (sudo virsh start vmname), it fails with: error: Failed to start domain 7-1 error: internal error: Process exited prior to exec: libvirt: error : unable to set

Bug#870428: libverto1: Upstream has moved

Sam Hartman writes: > I apologize for dropping the ball on this so long. > It looks like there is a 0.3.0 release of verto, which was folded into > krb5. > However, It looks like there's not an upstream tarball on github for > anything past 0.2.6. I'm confused by this comment. I've definitely

Bug#922627: linux-image-4.19.0-2-rt-amd64: Crash on boot on Lenovo T530

Package: src:linux Version: 4.19.16-1 Severity: normal Dear Maintainer, While attempting to boot, the kernel failed to boot ending in stacktrace: http://www.club.cc.cmu.edu/~rharwood/tmp/panic1.jpg Apologies for not providing more logs, but shift-pageup doesn't appear to scroll this console.

Bug#920770: ping: Lacking privilege for raw socket

Control: close -1 You're right, it lost setuid bit. Fixed by reinstall. Thanks, --Robbie

Bug#921124: elpa-git-commit: bad interaction with worktree/branch renaming

Package: elpa-git-commit Version: 2.90.1-1 Followup-For: Bug #921124 Thanks for your patience while I investigated a bit further. It appears that this is related to worktrees and branch migration. I can reproduce like so: # set up repo git init testrepo cd testrepo # make HEAD

Bug#921124: elpa-git-commit: magit components can't handle - character

Package: elpa-git-commit Version: 2.90.1-1 Severity: important Dear Maintainer, elpa-git-commit and magit's interactive rebase mode don't seem to be able to handle the - character in pathnames/branches. I wish I could provide a more helpful error, but the result is that when I try to type in

Bug#920770: ping: Lacking privilege for raw socket

Package: inetutils-ping Version: 2:1.9.4-5 Severity: important Dear Maintainer, Non-root users seem unable to ping: frozencemetery@kirtar:~$ ping 1.1.1.1 ping: Lacking privilege for raw socket. frozencemetery@kirtar:~$ Nothing appears in the logs, so I'm unclear why this doesn't

Bug#919323: msmtp: apparmor blocks reading configuration file ~/.msmtprc

Package: msmtp Version: 1.8.1-2 Severity: important Dear Maintainer, Trying to send mail with msmtp after upgrading, it fails with "no configuration file available". The audit line is: audit: type=1400 audit(1547504604.078:263): apparmor="DENIED" operation="open" profile="/usr/bin/msmtp"

Bug#916564: python-pyte: new upstream version: 0.8.0

Package: python3-pyte Version: 0.4.8-1 Severity: normal Dear Maintainer, Currently pyte is on version 0.4.8 - which was released in January of 2014. Please update to something newer, like the 0.8.0 that was released in April of this year. Thanks, --Robbie -- System Information: Debian Release:

Bug#915780: krb5: New upstream version: 1.16.2

Source: krb5 Version: 1.16.1-1 Severity: normal Dear Maintainer, A new upstream version is available. There are 29 commits from 1.16.1 to 1.16.2 (not including release goo), which include several documentation fixes, two memory leak fixes, and a fix for concurrent use of MEMORY ccaches.

Bug#907568: dmesg: bad localization on --help

Package: util-linux Version: 2.32.1-0.1 Severity: normal Dear Maintainer, In non-english locales, the help appears to have been over-localized. For instance: # LC_ALL=es_US.utf8 dmesg --help | grep -- --color -L, --color[=] colorea los mensajes (auto, siempre o nunca) # but:

Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed

Package: libpam-systemd Version: 238-5 Severity: grave Justification: renders package unusable Dear Maintainer, (This bug has been reported also against systemd-shim: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 ) libpam-systemd requires systemd-shim version >=10-4~. No such

Bug#899249: ncmpcpp: symbol lookup error on launch - boost related?

Package: ncmpcpp Version: 0.8.1-1+b1 Severity: important Dear Maintainer, This may be the same bug as #899163 so feel free to handle appropriately, but I didn't perform any forcing. This just happened during an upgrade. Anyway, whenever I try to launch ncmpcpp, it fails like so:

Bug#895836: flex: Upgrading from 2.6.1-1.3 to 2.6.4-6 breaks apache module loading

Thanks Adrian! Timo, this is fixed in upstream PR 179. Thanks, --Robbie

Bug#895836: flex: Upgrading from 2.6.1-1.3 to 2.6.4-6 breaks apache module loading

Package: flex Version: 2.6.4-6 Severity: important Dear Maintainer, After upgrading the version of flex, mod_auth_gssapi (in Debian, libapache2-mod-auth-gssapi) can no longer be used. In particular, apache fails with: apache2: Syntax error on line 78 of

Bug#892779: libu2f-udev: Please support non-systemd

Package: libu2f-udev Version: 1.1.4-1 Severity: normal Dear Maintainer, The provided udev rules don't work if the system isn't running systemd. Instead, we have to do something like: ATTRS{idVendor}=="1050", GROUP="plugdev", MODE="0660" ATTRS{idVendor}=="2581", ATTRS{idProduct}=="f1d0",

Bug#880599: python-requests-kerberos: New upstream versions available - up to 0.11.0

Package: python-requests-kerberos Version: 0.7.0-3 Severity: normal Dear Maintainer, Version 0.7.0 was released in mid-2015. Please update to a new version of this module so that we can use the newer features added. Thanks! -- System Information: Debian Release: buster/sid APT prefers

Bug#880446: GitPython: new upstream version 2.1.7

Package: python-git Version: 2.1.6-1 Severity: normal Dear Maintainer, A new upstream version of GitPython is available (2.1.7), released three days after 2.1.6. Among other things, this version contains fixes for working worktrees. I would appreciate if you could package this. Thanks! --

Bug#872365: python-cysignals-pari: Makes sagemath uninstallable, but sagemath depends on python-cysignals-pari

Package: python-cysignals-pari Version: 1.6.5+ds-1 Severity: important Dear Maintainer, sagemath depends on python-cysignals-pari. However, python-cysignals-pari has: Breaks: sagemath (< 8.0~), sagemath:i386 (< 8.0~) Since the only version of sagemath avaioable is 7.6, this makes sagemath

Bug#871601: ansible-2.3.1.0+dfsg-1 is uninstallable

Package: ansible Version: 2.3.1.0+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, ansible-2.3.1.0+dfsg-1 depends on python-jinja2 < 2.9. However, this is not available in testing/unstable/experimental. As a result, ansible-2.3.1.0+dfsg-1 is uninstallable, and

Bug#870428: libverto1: Upstream has moved

Package: libverto1 Version: 0.2.4-2.1 Severity: normal Dear Maintainer, Since Fedorahosted isn't around anymore, we've moved the libverto upstream to https://github.com/latchset/libverto . I also notice that the Debian package is 0.2.4 while we have released 0.2.6 upstream. I am happy to help

Bug#870008: qemu-launcher: where is your upstream?

Package: qemu-launcher Severity: normal Dear Maintainer, In debian/control, there is no `Homepage`, `Vcs-Git`, or `Vcs-Browser` set. Additionally, there are no results from search engines that seem to relate to this project. Please set these fields in control so that we can find this

Bug#864377: docker.io: Failure to install (cannot start daemon)

Package: docker.io Version: 1.13.1~ds1-2 Followup-For: Bug #864377 Well, perhaps. The problem is that I can reproduce this on a fresh system installation by just triggering a reinstall: rharwood@seton:~$ sudo aptitude reinstall docker.io The following packages will be REINSTALLED:

Bug#866530: pyrad: New upstream version - 2.1

Source: pyrad Severity: normal Dear Maintainer, A new version of pyrad is avilable upstream (2.1)[1]. Please package it. Thanks, --Robbie 1: https://github.com/wichert/pyrad/releases/tag/2.1 -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (600,

Bug#849240: auto-complete-el: ac-menu-delete setq of 1 arg

Package: auto-complete-el Version: 1.3.1-2 Followup-For: Bug #849240 Dear Maintainer, This bug has been reported upstream as https://github.com/auto-complete/auto-complete/issues/466 (more information on failure) and https://github.com/auto-complete/auto-complete/pull/424 (contains fix). Please

Bug#864377: docker.io: Failure to install (cannot start daemon)

Package: docker.io Version: 1.13.1~ds1-2 Severity: grave Justification: renders package unusable Dear Maintainer, During a system upgrade, I got the following: Setting up docker.io (1.13.1~ds1-2) ... [] Starting Docker: dockerinvoke-rc.d: initscript docker, action "start" failed. dpkg:

Bug#862978: zsh: `kill -L` doesn't work

Package: zsh Version: 5.3.1-4+b1 Severity: minor Dear Maintainer, As per kill(1), -L should generate a pretty list of signals and values. Like this: rharwood@thriss:~$ /bin/kill -L 1 HUP 2 INT 3 QUIT 4 ILL 5 TRAP 6 ABRT 7 BUS 8 FPE 9 KILL10

Bug#861266: cmocka: Please package new upstream version

Source: cmocka Version: 1.0.1-3 Severity: wishlist Dear Maintainer, Versions 1.1.1 has been released upstream early this month. Thanks! -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (600, 'unstable-debug'), (600, 'testing-debug'), (600, 'unstable'),

Bug#860342: [Python-modules-team] Bug#860342: python3-taglib: Newer upstream releases available since Jan 21, 2014

Brian May <b...@debian.org> writes: > Robbie Harwood <rharw...@club.cc.cmu.edu> writes: > >> Please update to a newer version of the package. This looks >> unmaintained and I would have filed an RM request save that there are >> packages that depend on th

Bug#860342: python3-taglib: Newer upstream releases available since Jan 21, 2014

Package: python3-taglib Severity: grave Justification: renders package unusable Dear Maintainer, Please update to a newer version of the package. This looks unmaintained and I would have filed an RM request save that there are packages that depend on this in the archive. Thanks. -- System

Bug#756400: pytaglib: Please include a python2 package

Source: pytaglib Followup-For: Bug #756400 Dear Maintainer, Upstream is capable of both python2 and python3. I would really like to not have to make my code care, or install from pip. Thanks. -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (600,

Bug#852395: unblock: gssproxy/0.5.1-2

Niels Thykier writes: > Ok - as I understand it, what we are dealing with here is: > > * systemd: You can get gssproxy + NFS and it "just works(tm)" if >you install gssproxy. Otherwise you get svcgssd + NFS. >(This is how I understood Neil Brown) > * sysvinit:

Bug#859968: qt5-qmake: man page for qmake-qt5 has wrong HTML doc path

Package: qt5-qmake Version: 5.7.1+dfsg-3+b1 Severity: minor Dear Maintainer, qmake-qt5(1), which I assume was ported over from qmake-qt4(1), mentions the path /usr/share/qt5/doc/html/qmake-manual.html in the "SEE ALSO" section. The correct path is /usr/share/qt5/doc/qmake/qmake-manual.html

Bug#852395: unblock: gssproxy/0.5.1-2

Niels Thykier writes: > NeilBrown: >> On Sun, Mar 05 2017, Daniel Pocock wrote: >> >> The systemd unit files are designed so that svcgssd will only be >> started if gssproxy didn't start - and gssproxy is tried first. >> >> If you use something other than systemd, similar

Bug#856965: gssproxy: GSS-Proxy is not supported by this kernel

Laurent Bonnaud writes: > I installed gssproxy on this system and saw the following error > message in the logs: > > Mar 6 16:59:15 irancy gssproxy[23024]: GSS-Proxy is not supported by > this kernel since file /proc/net/rpc/use-gss-proxy could not be found: > 2 (No such

Bug#857065: gmrun: Segfault after recent upgrades

Package: gmrun Version: 0.9.2-2.1+b2 Severity: grave Followup-For: Bug #857065 Raising severity to "grave" since it is usable becuse it segfaults every time we try to launch it. -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (600, 'unstable-debug'), (600,

Bug#855079: Acknowledgement (weechat-curses: Screen redraw on terminal resize is slow after upgrade)

After some digging, I believe this is caused by this issue: https://github.com/weechat/weechat/issues/902 which was fixed upstream. signature.asc Description: PGP signature

Bug#855079: weechat-curses: Screen redraw on terminal resize is slow after upgrade

Package: weechat-curses Version: 1.7-1 Severity: minor Dear Maintainer, After upgraing to unstable, I'm noticing that weechat-curses takes 2-3 seconds to repaint when I resize the terminal. Normal repaints, such as switching channel buffers, are as fast as before, and other curses applications

Bug#852719: sssd-common: `service sssd restart` hangs

Package: sssd-common Version: 1.15.0-1 Severity: normal Tags: patch Dear Maintainer, /etc/default/sssd has -i present in DAEMON_OPTS. This causes sssd to not disown its processes on service start, and as a result `service sssd restart` will hang. To fix, replace -i with -D. Thanks! -- System

Bug#852395: unblock: gssproxy/0.5.1-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gssproxy gssproxy has been 10 days in unstable, and allowing it to migrate will fix bug#848306 (severity: important) in nfs-common. gssproxy is a new package in

Bug#833114: "RuntimeError: OrderedDict mutated during iteration" on some feeds

Package: rss2email Version: 1:3.9-2 Followup-For: Bug #833114 Here is the commit to fix it from upstream: https://github.com/wking/rss2email/commit/60870d9ff7f23441919df79d710ad49ecbcedf73 -- System Information: Debian Release: stretch/sid APT prefers testing-debug APT policy: (600,

Bug#807311: init-d-script: do_reload_sigusr1 sends sighup, not sigusr1

Petter Reinholdtsen writes: > Renaming the function will break anyone doing the 'alias' trick, so any > changes should be done in a backwards compatible way, I believe. > > Patches welcome. :) The approach I was suggesting would look like this: + Enable this using +

Bug#807311: init-d-script: do_reload_sigusr1 sends sighup, not sigusr1

Petter Reinholdtsen <p...@hungry.com> writes: > [Robbie Harwood] >> It's pretty common for SIGHUP to reload config as well as SIGUSR1. >> >> So, my suggestion would be define a new way of doing this, file bugs >> with patches against anyone using d

Bug#807311: init-d-script: do_reload_sigusr1 sends sighup, not sigusr1

It's pretty common for SIGHUP to reload config as well as SIGUSR1. So, my suggestion would be define a new way of doing this, file bugs with patches against anyone using do_reload_sigusr1, and then remove do_reload_sigusr1. One way that might be nice is to make a function do_reload_signal, which

Bug#847681: packaging repository and sid diverging? Various fixes needed.

Sven Geggus writes: > Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 11:01 Uhr: > >> Would you consider uploading it or proposing it in mentors.debian.net? >> Please also send details on the gss-proxy ITP bug. > > Robbie is the one with the ITP bug, not me :)

Bug#847140: xdm: should install exececutable in /usr/sbin

Package: xdm Version: 1:1.1.11-3 Severity: normal Dear Maintainer, Binaries should be in the sbin, not the plain bin, directory when only root wants to run them. For instance: $ xdm Only root wants to run xdm $ echo $? 1 Thanks! -- System Information: Debian Release:

Bug#847009: amanda: please make the build reproducible (shell)

anda could not be built reproducibly. The attached patch stops the shell value at build-time from leaking into processed shell scripts. Once applied, amanda should be able to be built reproducibly in our current framework. Thanks! [1]: https://wiki.debian.org/ReproducibleBuilds Author: Robbie Harw

Bug#846971: maildrop: Fix reproducible build issue in package

) Author: Robbie Harwood <rharw...@club.cc.cmu.edu> Description: For reproducibility, do not use build-time shell in scripts --- a/libs/maildir/sharedindexinstall.in +++ b/libs/maildir/sharedindexinstall.in @@ -1,4 +1,4 @@ -#! @SHELL@ +#!/bin/sh # # Copyright 2004 Double Precision, Inc. # See C

Bug#846894: bgoffice-computer-terms: VCS links are dead

Package: bgoffice-computer-terms Severity: normal Dear Maintainer, The VCS links for this package have stopped working. Please update them to your actual VCS. Thanks! -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (600, 'testing'), (400, 'unstable'),

Bug#846885: paxrat: Vcs-Git is incorrect

Package: paxrat Severity: minor Tags: patch Dear Maintainer, The `Vcs-git:` field should point to a URL that can be checked out. For this package, the correct remote would be https://anonscm.debian.org/git/collab-maint/paxrat.git Thanks! -- System Information: Debian Release: stretch/sid

Bug#832962: reprotest fails to build properly on jessie

Package: reprotest Followup-For: Bug #832962 So it will need to build against backports because it requires diffoscope. Most of the build can occur with minor changes to dependencies (vim-common for xxd, python-tox for tox, fixing version in setup.py). However, the test suite does not seem to

Bug#846857: git-pbuilder: does not call pbuilder and no flag to change this

Package: git-buildpackage Version: 0.8.7 Severity: normal Dear Maintainer, Based on the name, I would have expected pbuilder to call out to pbuilder, not cowbuilder. It is also difficult to change this behavior from a `gbp buildpackage` invocation since there are no flags for it. Thanks! --

Bug#846535: openssl: 1.1.0c cannot decrypt files created by older versions of openssl

Package: openssl Version: 1.1.0c-2 Severity: critical Justification: causes serious data loss Dear Maintainer, After upgrading to a newer version of OpenSSL, I cannot decrypt a file that was encrypted using the OpenSSL in Stable (and had been decryptable until very recently). To reproduce:

Bug#838282: ITP: gssproxy -- A privilege separation daemon for GSSAPI

Package: wnpp Followup-For: Bug #838282 Owner: Robbie Harwood <rharw...@club.cc.cmu.edu> Control: retitle -1 ITP: gssproxy -- A privilege separation daemon for GSSAPI * Package name: gssproxy Version : 0.5.1 Upstream Author : The GSS-PROXY contributors * URL :

Bug#842393: thefuck: Missing dependency on python-pkg-resources

Package: thefuck Version: 3.11-2 Severity: important Dear Maintainer, When run on a system without python-pkg-resources, running `eval "$(thefuck --alias)` produces the following traceback: > Traceback (most recent call last): > File "/usr/bin/thefuck", line 6, in > from pkg_resources

Bug#842291: notmuch processes frequently stuck in select()

David Bremner writes: > 1) Can you duplicate the problem with non-encrypted messages? Not sure. Most of the time it's inconsistent what messages it happens for (and it's hard to see whether the message is encrypted when notmuch won't show it to me). I'll update with a

Bug#842291: notmuch processes frequently stuck in select()

Package: notmuch Version: 0.23.1-1 Severity: important Dear Maintainer, Frequently the processes notmuch-emacs spawns to view messages never finish returning the message data. Sometimes this is deterministic and the message is never viewable; other times, spawning more of the same process

Bug#839844: freeipa-client: Uninstallable due to unsatisfiable Depends:

Package: freeipa-client Version: 4.3.2-2 Severity: grave Justification: renders package unusable Dear Maintainer, freeipa-client currently cannot be installed due to the following nonexistent dependencies: Depends: freeipa-common (= 4.3.2-2) which is a virtual package and is not

Bug#829749: krb5-kdc-ldap: kerberos.schema.gz is a config file

Package: krb5-kdc-ldap Severity: normal Dear Maintainer, When deploying an LDAP KDC, the LDAP configuration needs the kerberos schema file. However, this file is treated as documentation and therefore is compressed. This means that when deploying, it must be extracted somewhere (probably

Bug#825749: xul-ext-foxyproxy-standard: foxyproxy cannot be installed if icedove 45 is present

Package: xul-ext-foxyproxy-standard Version: 4.5.6-debian-1 Severity: important Dear Maintainer, It is currently not possible to have both xul-ext-foxyproxy-standard and icedove 45.1.0-1 (i.e., the icedove from sid) present on the same system: ``` $ aptitude -s install -t unstable icedove The

Bug#821844: elpa-magit: [RFE] Please include magit subcomponents

Package: elpa-magit Version: 2.6.1-1 Severity: wishlist Dear Maintainer, I'm primarily interested in magit-stgit here, though there are other git component integrations that upstream has available[0]. Since we have stgit and magit both available, it would be great if the integration glue were

Bug#722017: xfonts-terminus: iso10646 font is unusable with xterm

Package: xfonts-terminus Version: 4.39-1 Followup-For: Bug #722017 Dear Maintainer, This issue also manifests in other programs, such as xmobar and dzen2 (and GUI emacs, if you believe stack overflow). I noticed this issue on upgrade from stable, where it was previously working. Please fix

Bug#812131: krb5: Please package 1.14 (willing to provide assistance)

Sam Hartman writes: > Hi. > I hope to get to this in the next week or so; sorry about the delay. Sounds good. Thanks for doing it! signature.asc Description: PGP signature

Bug#812131: krb5: Please package 1.14 (willing to provide assistance)

Source: krb5 Severity: important Dear Maintainer, As per http://web.mit.edu/kerberos/ krb5-1.14 has been available since 2015-11-20. Please consider packaging this new version, even if only in experimental. If it would be helpful, I am willing to provide labor. I maintain an rdependency

Bug#810923: virtinst: virt-install fails to create working ppc64 (& other non-native) VMs

Package: virtinst Version: 1:1.2.1-4 Severity: important Dear Maintainer, When following the normal process for creating a ppc64 VM (e.g., https://rwmj.wordpress.com/2015/04/15/virt-builder-fedora-21-ppc64-and-ppc64le-images/ ), it will fail complaining about vmport. I believe this is this bug:

Bug#808576: [Pkg-rust-maintainers] Bug#808576: rustc cannot compile programs: "unrecognized relocation in section"

Sylvestre Ledru writes: > Le 21/12/2015 14:02, Luca Bruno a écrit : >> On Monday 21 December 2015 12:27:47 Luca Bruno wrote: >> >>> For reference, current working sid toolchain is ld 2.25.90.20151209 and gcc >>> 5.3.1-4. >> >> Similarly, I tried in a fresh stretch

Bug#808576: rustc cannot compile programs: "unrecognized relocation in section"

Package: rustc Version: 1.5.0+dfsg1-1 Severity: important Dear Maintainer, When I try to build any rust program, the following occurs: $ cat > main.rs fn main() { print!("Hello, world!\n"); } $ rustc main.rs error: linking with `cc` failed: exit code: 1 note: "cc" "-Wl,--as-needed" "-m64"

Bug#807963: virt-viewer: Segmentation fault on connection to spice vm

Package: virt-viewer Version: 1.0-1 Severity: important Dear Maintainer, When attempting to connect to VMs over SPICE, virt-viewer will consistently segfault as so: $ gdb -q virt-viewer Reading symbols from virt-viewer...(no debugging symbols found)...done. (gdb) set args --connect

Bug#798899: vlc: Segmentation fault when playing video

Package: vlc Version: 2.2.1-3 Severity: important Dear Maintainer, When trying to open certain video files, vlc segfaults. Traceback follows: GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Bug#783224: boinctui segmentation fault on start

Sergey Suslov writes: > Thanks for bug report. Unfortunately, I can't reproduce this bug on my > configuration (i386 instead x86_64, all other like as your). Can you > try to start boinctui without ~/.boinctui.cfg file (remove or rename)? Turns out my .boinctui.cfg file

Bug#796287: openrc: Please package new version

Package: openrc Version: 0.13.1-4 Severity: normal Dear Maintainers, A new version of this package is available upstream. Please, please package it in testing/unstable. Thanks! -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (800, 'stable-updates'), (800,

Bug#794980: ITP: python-gssapi, python3-gssapi -- Python Python3 interfaces to GSSAPI

Package: wnpp Version: N/A; reported 2015-08-08 Severity: wishlist * Package name : python-gssapi, python3-gssapi Version : 1.1.2 Upstream Author : The Python GSSAPI Team * URL : https://github.com/pythongssapi/python-gssapi/ * License : ISC

Bug#794042: hydrogen: Hydrogen segfault on adding from sound library

Package: hydrogen Version: 0.9.6.1-1 Severity: important Dear Maintainer, Sporadically, hydrogen will crash. This seems to be co-incident with adding instruments to the current loop. Here is a traceback: Program received signal SIGABRT, Aborted. 0x73b2d107 in __GI_raise

Bug#790055: msmtp: Please compile with GSSAPI support

Robbie Harwood rharw...@club.cc.cmu.edu writes: Package: msmtp Version: 1.4.32-2+b1 Severity: normal Dear Maintainer, When attempting to use GSSAPI for authentication with msmtp, the following message is returned: msmtp: support for authentication method GSSAPI is not compiled

Bug#790055: msmtp: Please compile with GSSAPI support

Package: msmtp Version: 1.4.32-2+b1 Severity: normal Dear Maintainer, When attempting to use GSSAPI for authentication with msmtp, the following message is returned: msmtp: support for authentication method GSSAPI is not compiled in Please compile with GSSAPI support. Thanks! -- System

Bug#783224: boinctui segmentation fault on start

Package: boinctui Version: 2.3.5-1 Severity: important Dear Maintainer, Boinctui was previously operational. However, when I try to start it now, it clears the screen and then prints Segmentation fault. Reproducing the crash in gdb produces (gdb) bt #0 0x0041a1a3 in ?? ()

Bug#771770: haskell-mode copiously displays its documentation

David Bremner da...@tethera.net writes: Robbie Harwood rharw...@club.cc.cmu.edu writes: Makes sense. The problem I'm having is that it's not clear how to turn it off, especially since I don't want any indentation. I think what you want then is to turn off electric-indent-mode, perhaps

Bug#771770: haskell-mode copiously displays its documentation

David Bremner da...@tethera.net writes: Robbie Harwood rharw...@club.cc.cmu.edu writes: Package: haskell-mode Version: 13.10-3 Severity: important Dear Maintainer, When a newline is entered into a buffer in Haskell mode, the view is split and a *Help* buffer appears displaying

  1   2   >