Turns out the issue wasn't a bug, but a leftover file on my machine. Sorry for the inconvenience, and please close this report.
On Fri, 12 Apr 2019 18:45:44 -0400 roranicus <rorani...@posteo.net> wrote: > Package: profanity > Version: 0.6.0-1 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > I tried to start profanity > * What exactly did you do (or not do) that was effective (or > ineffective)? > I tried to uninstall and reinstall the package, same thing with libcurl. > * What was the outcome of this action? > Nothing changed. > * What outcome did you expect instead? > I wanted Profanity to start > > *** End of the template - remove these template lines *** > > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages profanity depends on: > ii libassuan0 2.5.2-1 > ii libatk1.0-0 2.30.0-2 > ii libc6 2.28-8 > ii libcairo2 1.16.0-4 > ii libcurl3-gnutls 7.64.0-2 > ii libfontconfig1 2.13.1-2 > ii libfreetype6 2.9.1-3 > ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 > ii libglib2.0-0 2.58.3-1 > ii libgpg-error0 1.35-1 > ii libgpgme11 1.12.0-6 > ii libgtk2.0-0 2.24.32-3 > ii libncursesw6 6.1+20181013-2 > ii libnotify4 0.7.7-4 > ii libotr5 4.1.1-3 > ii libpango-1.0-0 1.42.4-6 > ii libpangocairo-1.0-0 1.42.4-6 > ii libpangoft2-1.0-0 1.42.4-6 > ii libpython3.7 3.7.3~rc1-1 > ii libreadline7 7.0-5 > ii libstrophe0 0.9.2-2 > ii libtinfo6 6.1+20181013-2 > ii libx11-6 2:1.6.7-1 > ii libxss1 1:1.2.3-1 >
0x9A84C39E7DDC5A4F.asc
Description: application/pgp-keys
