Your message dated Sun, 21 Apr 2019 16:53:36 +0200 with message-id <20190421145336.GA22531@fama> and subject line Re: Bug#926970: profanity: Profanity tries to use libcurl3 which isn't included in the repository. has caused the Debian Bug report #926970, regarding profanity: Profanity tries to use libcurl3 which isn't included in the repository. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 926970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926970 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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 profanity recommends no packages. profanity suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On 2019-04-21 10:17, ror wrote: > Turns out the issue wasn't a bug, but a leftover file on my machine. > Sorry for the inconvenience, and please close this report. You can even do this by yourself: Just send an email to "bugnumber"[email protected], of course "bugnumber" replaced with 926970, which I have done now. Anyway, thanks for testing and re-testing! Even if this time it was a false alarm, I'm always grateful, if people test and create bug reports. I hope to get profanity with OMEMO support into Debian (experimental) soon and hope you can test this, too! Maybe in some days or a few weeks... So far, it crashes for me.
--- End Message ---
