close 907618 0.4-6
thanks
On Mon 2018-09-17 10:14:31 +0200, Jonas Meurer wrote:
> yesterday, Thunderbird 1:60.0-2~deb9u1 got uploaded to Stretch (via
> security). This thunderbird version breaks enigmail (<< 2:2~), which
> leads to uninstallable/unusable Enigmail in Debian Stretch.
>
> May I suggest to backport Enigmail 2.0
On Sat 2018-09-15 09:09:58 +0300, Adrian Bunk wrote:
> It also needs a proper narrowly versioned dependency.
while irssi packaging doesn't release the ABI, i still want
irssi-plugin-xmpp to work for now. So I've added a (fairly brittle)
build-dep and runtime versioning limits to irssi-plugin-xmpp
close 881397 0.19.1-2
thanks
On Sun 2017-11-12 15:45:26 +0100, Ondřej Surý wrote:
> Control: forwarded -1
> https://gitlab.labs.nic.cz/knot/knot-resolver/issues/272
>
> dkg, I told you :)
I don't think this is the same problem. knot-resolver 1.5.0-1 already
patches around the upstream problem Ondřej points to with:
htt
On Sun 2017-11-12 17:59:47 +0100, Kurt Roeckx wrote:
> On Mon, Nov 13, 2017 at 12:09:05AM +0800, Daniel Kahn Gillmor wrote:
>> On Sun 2017-11-12 15:45:26 +0100, Ondřej Surý wrote:
>> > Control: forwarded -1
>> > https://gitlab.labs.nic.cz/knot/knot-resolver/issues/27
On Tue 2016-10-11 23:48:15 -0400, Daniel Kahn Gillmor wrote:
> Those patches are posted here:
>
> https://github.com/bestpractical/gnupg-interface/pull/1
>
> I'd like to upload them to debian as well, though they are *not*
> interoperable with versions of GnuPG prior t
this analysis is wrong and
can help me see what the right evaluation is.
> Severity set RC, since this prevents testing migration of gpgme1.0
Agreed that this migration blocker is serious.
Regards,
--dkg
From 5a82ee9d8562d5481a24dd651a2c0dd8ce7ffe32 Mon Sep 17 00:00:00 2001
From: Dani
Control: retitle 846232 openvas should depend on libgpgme-dev instead of
libgpgme11-dev
On Wed 2016-11-30 14:16:20 -0500, Adrian Bunk wrote:
> I wondered the same before writing the bug.
>
> The answer I got on #debian-devel is that this is one case where the
> policy document is outdated (suppo
On Mon 2019-02-25 13:33:57 +0100, Werner Koch wrote:
> On Sun, 24 Feb 2019 16:56, joshud...@gmail.com said:
>
>> gpg-agent --server or directly from .profile (ssh sessions) by
>> gpg-agent --daemon.
>
> FWIW, actually gpg-agent is started on-demand from all tools requiring
> it. To explicitly star
Control: 920695 fixed 3.2.1-1
I'm able to rebuild knot-resolver just fine on stretch, when i build
3.2.1-1 against a backported knot 2.7.6-2. I'll be uploading those to
stretch-backports shortly, but they can't go in until they've reached
testing.
But knot won't go into testing untlik knot-resol
Control: severity 920695 important
On Thu 2019-02-28 22:06:09 -0500, Daniel Kahn Gillmor wrote:
> So i'm marking #920695 as fixed in 3.2.1-1 with the hope of getting all
> of these migrations to move forward.
I've tagged the shared git repo for both knot-dns and for knot-resolve
On Wed 2017-02-15 12:09:54 -0500, Roger Shimizu wrote:
> On Thu, Feb 16, 2017 at 1:36 AM, James Cowgill wrote:
>> On 15/02/17 11:24, Roger Shimizu wrote:
>>> On Wed, Feb 15, 2017 at 7:51 PM, James Cowgill wrote:
So do you know why the tests only pass when using 2 CPUs? That seems
p
On Thu 2017-02-23 08:28:03 -0500, Lucas Nussbaum wrote:
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on amd64.
here's the actual relevant part:
FAIL: test-22_TLS_reverse_proxy_crl_revoke.bash
FAIL: test-21_TLS_reverse_proxy_
ached patches, which i'll push to salsa as well
shortly.
--dkg
From c442b9a28ba78241d4da5f051529e1d87141b00b Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Thu, 30 Aug 2018 14:46:25 -0400
Subject: [PATCH 1/7] point Vcs-* to salsa
---
debian/control | 4 ++--
1 file changed
On Thu 2018-08-30 15:25:49 -0400, Daniel Kahn Gillmor wrote:
> the NMU uses the attached patches, which i'll push to salsa as well
> shortly.
The changes are available on salsa at
https://salsa.debian.org/lua-team/lua-sec/merge_requests/1.
They also merge in upstream's git histo
On Thu 2018-08-30 15:38:50 -0400, Daniel Kahn Gillmor wrote:
> On Thu 2018-08-30 15:25:49 -0400, Daniel Kahn Gillmor wrote:
>> the NMU uses the attached patches, which i'll push to salsa as well
>> shortly.
>
> The changes are available on salsa at
> https://sals
Control: tags 795639 + moreinfo
Control: reassign 795639 gnupg2 2.1.7-2
Control: affects 795639 assword
Hi Russ--
On Sun 2015-08-16 01:03:16 +0200, Russ Allbery wrote:
> strace seems to back that up. It chats with the agent for a bit, and
> then it fails. See the partial trace below. It seems
On Sun 2015-08-16 02:55:43 +0200, Russ Allbery wrote:
> Daniel Kahn Gillmor writes:
>
>> does this succeed with gpg2 --decrypt as well, or just gpg --decrypt?
>
> Aha. Here's a problem:
>
> mithrandir:~/private/db$ gpg2 --decrypt personal
> gpg: error re
Control: retitle 795639 automated secret key import process for gpg2.1 skips
some keys
On Sun 2015-08-16 19:16:03 +0200, Russ Allbery wrote:
> Daniel Kahn Gillmor writes:
>> do you see
>> ~/.gnupg/private-keys-v1.d/FD1DA474D3DF3C728C54F9E479EDFC5BBE2E14EA.key
>> ?
>
On Wed 2017-01-04 09:27:16 -0500, intrigeri wrote:
> Daniel Kahn Gillmor:
>> I've been able to replicate the problems described by intrigeri in
>> https://bugs.debian.org/849845; i'm preparing an update to gpg with
>> cherry-picked patches that resolves most of t
Control: fowarded 849845 https://bugs.gnupg.org/gnupg/issue2902
On Thu 2017-01-05 08:15:06 -0500, intrigeri wrote:
> Daniel Kahn Gillmor:
>> The remaining problem for me ws that when i use tor, if i get back
>> records, the connections fail, but the IPv6 records are not marked
On Fri 2017-01-06 12:49:32 -0500, Jaden Peterson wrote:
> I have no place in the topic of this bug, but I installed the patches
> you provided on January 5th onto my Debian Testing system. I would like
> to notify you that gpgv2 depends on gpgv version 2.1.17-3 or greater,
> which is not provide
On Fri 2017-01-06 14:47:46 -0500, shirish शिरीष wrote:
> I can confirm Jaden's findings. Perhaps the content hasn't reached his
> mirror yet. It's same thing at my end. I just updated to see if the
> new version has come up at my end. (not even in sid/unstable)
>
> [$] apt-cache policy gpgv
>
On Fri 2017-01-06 17:49:04 -0500, shirish शिरीष wrote:
> But issue is still continuing -
>
> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197
>
> [4:22:18]
> gpg: keyserver receive failed: No keyserver available
>
> I tried multiple times with various other keys but didn't succeed.
Have you r
Control: tags 850708 + moreinfo unreproducible
Hi Vincent--
On Mon 2017-01-09 10:02:20 -0500, Vincent Lefevre wrote:
> Since the latest upgrade:
>
> * When I open a .gpg file with Emacs:
>
> * With "gpg -d note.gpg", same errors:
>
> gpg: AES encrypted data
> gpg: cancelled by user
> gpg: encrypt
Control: reassign 850708 pinentry-gtk-2
On Mon 2017-01-09 22:08:09 -0500, Vincent Lefevre wrote:
> On 2017-01-09 18:00:14 -0500, Daniel Kahn Gillmor wrote:
>> what pinentry are you using?
>
> pinentry-gtk-2
>
> No problems with pinentry-curses.
I've reassigned this bu
Control: retitle 850708 pinentry-gtk-2 frequently fails to grab the keyboard
under fvwm
Control: affects 850708 + fvwm
On Tue 2017-01-10 20:58:16 -0500, Vincent Lefevre wrote:
> On 2017-01-10 18:26:57 -0500, Daniel Kahn Gillmor wrote:
>> what window manager are you using?
>
>
Control: forcemerge 849845 850606
Hi Ximin--
Your recently-filed debian bug 850606 is a duplicate of 849845 so i'm
merging the two.
On Sun 2017-01-08 07:31:11 -0500, Ximin Luo wrote:
> Since dirmngr is very stupid in how it deals with DNS pools, one workaround
> that users can do, is to keep kil
Control: severity 841208 important
On Mon 2016-12-12 19:16:24 -0500, Daniel Kahn Gillmor wrote:
> thanks for the notes. the issue is now entropy starvation during
> "monkeysphere gen-subkey" in the test suite. I'm not sure what the
> right thing to do is here, other tha
In https://bugs.debian.org/1034558, Salvatore Bonaccorso wrote:
> Source: rnp
> Version: 0.16.2-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
Thanks for tracking this in the BTS, Salvatore.
I aim to h
On Wed 2023-05-24 07:32:31 +0200, Salvatore Bonaccorso wrote:
> Thanks! Note the deadline for unblock requests will be on 28th. So the
> unblock needs to be granted by then so we have the fixes in bookworm.
The associated unblock request for 1034558 is #1036721
--dkg
signature.asc
Descript
Control: clone 1034065 -1
Control: reassign -1 python3-argparse-manpage
Control: affects -1 src:sasl-xoauth2
Control: retitle -1 argparse-manpage doesn't run unless python3-setuptools is
installed
On Fri 2023-04-07 22:14:44 +0200, Andreas Beckmann wrote:
> sasl-xoauth2/experimental FTBFS on all a
e's the patch against v4.3 that i intend to send to
bullseye-security:
From: Daniel Kahn Gillmor
Date: Thu, 1 Jun 2023 16:12:50 -0400
Subject: Resolve CVE-2023-30570
see https://libreswan.org/security/CVE-2023-30570/CVE-2023-30570.txt
This patch was ported from
https://libreswan.org/secur
Hi Salvatore--
On Fri 2023-06-02 21:20:50 +0200, Salvatore Bonaccorso wrote:
> Thanks for having a closer look and for your assessment. Then I
> believe we can have a fix scheduled via respective point releases, I
> do not see an urgency for it requiring a DSA. Initially I was not
> completely sur
Hi Andreas--
Thank you for addressing this problem, it is much appreciated!
--dkg
On Sun 2023-03-26 14:00:17 +0200, Andreas Metzler wrote:
> On 2023-03-18 Jonathan Wiltshire wrote:
>> Source: gnupg2
>> Version: 2.2.40-1
>> Severity: important
>> Tags: patch
>> X-Debbugs-Cc: j...@debian.or
Hi Paul--
On Sat 2019-06-22 20:51:00 +0200, Paul Gevers wrote:
> On Tue, 14 May 2019 06:18:31 +0000 Daniel Kahn Gillmor
> wrote:
>> gnupg2 (2.2.13-2) unstable; urgency=medium
>> .
>>* Correct gpg-wks-server manpage (Closes: #927431) Thanks, ju xor!
>>*
On Thu 2021-06-03 01:37:25 +0300, Adrian Bunk wrote:
> Overall it feels like a package with high CVE risk and 0 users
> in bullseye.
I agree with Jason that some people may use non-standard, older kernels
with bullseye, so there is some value in continuing to provide
wireguard-dkms in bullseye to
Control: severity 989406 normal
Control: retitle 989406 wireguard-dkms is unneeded for stock kernels > 5.6
I'm downgrading the severity to keep wireguard-dkms in bullseye -- we
can increase it again once bullseye is released to keep wireguard-dkms
out of bookworm.
Adrian or others, if you would p
Control: affects 975480 debcargo
On Sun 2020-11-22 19:21:45 +0100, Paul Gevers wrote:
> autopkgtest [09:47:16]: test librust-bzip2-sys-dev:
> /usr/share/cargo/bin/cargo-auto-test bzip2-sys 0.1.9+1.0.8 --all-targets
> --no-default-features
> autopkgtest [09:47:16]: test librust-bzip2-sys-dev: [
Package: rnp
Version: 0.14.0-5
Severity: critical
Control: forwarded -1 https://github.com/rnpgp/rnp/issues/1436
RNP's test suites are failing on all of the 32-bit platforms in debian.
I've reported this upstream so that hopefully it can be resolved.
It should not migrate into testing in this cur
Thanks Paul for reviewing this, and Robert for looking into it further.
I think my conclusions differ a little bit from Robert's.
On Thu 2021-02-11 22:22:18 -0500, Robert Edmonds wrote:
> I have investigated this report. The purpose of the dns-root-data
> package is to ship, as static content, the
Package: rust-sha1collisiondetection
Version: 0.2.2-1
Severity: critical
Control: forwarded -1
https://gitlab.com/sequoia-pgp/sha1collisiondetection/-/issues/1
Looks like rust-sha1collisiondetection code isn't as portable as
upstream expected it to be. It is failing on platforms with an unsigned
Control: affects 862071 + src:gnupg2
Upstream's recommendation is currently to use a temporary $GNUPGHOME
(with a short path) for test suites which depend on GnuPG with an
ephemeral homedir.
--dkg
signature.asc
Description: PGP signature
On Mon 2017-05-01 10:11:51 +0200, Salvatore Bonaccorso wrote:
>> HOME=/home/lamby
>> LOGNAME=lamby
>> SHLVL=1
>> PWD=/home/lamby/temp/cdt.20170430222311.WuN76MAfhh.db.libgnupg-interface-perl/libgnupg-interface-perl-0.52
>> OLDPWD=/home/lamby/temp/cdt.20170430222311.WuN76MAfhh.db.libgnupg-interface-
On Thu 2017-05-25 18:35:13 +0200, Chris Lamb wrote:
> Daniel Kahn Gillmor wrote:
>
>> The failures on repeat are presumably because of something related to
>> the gpg-agent daemon persisting across the tests.I'll look into
>> invoking "gpgconf --kill all"
On Thu 2017-05-25 13:13:43 -0400, Daniel Kahn Gillmor wrote:
> On Thu 2017-05-25 18:35:13 +0200, Chris Lamb wrote:
>> Daniel Kahn Gillmor wrote:
>>
>>> The failures on repeat are presumably because of something related to
>>> the gpg-agent daemon persisting ac
Hi there--
On Sun 2017-05-28 19:54:33 +0200, Ivo De Decker wrote:
> On Sun, May 28, 2017 at 02:39:00PM +0200, Jan Niehusmann wrote:
>> May I suggest only removing runit-init from the runit source package, if
>> the bug can't be fixed in time for the stretch release?
>
> Sure. That just needs some
On Sun 2017-05-28 15:14:24 -0400, Daniel Kahn Gillmor wrote:
> On Sun 2017-05-28 19:54:33 +0200, Ivo De Decker wrote:
>> If this bug can be fixed by removing runit-init, the removal of the other
>> packages isn't necessary, but please note that this would need to happen very
&g
Hi all--
On Tue 2017-05-30 13:07:01 -0400, Daniel Kahn Gillmor wrote:
> I've now done this NMU, and filed #863732 to unblock the upload.
>
> I've pushed the changes in a git branch to
> https://anonscm.debian.org/git/collab-maint/runit.git, which is forked
> from of https
On Fri 2017-06-02 02:53:47 +0200, Michael Biebl wrote:
> Seems like you want a Breaks/Replaces: runit-init in runit to ensure the
> package is properly upgraded for users who have already runit-init
> installed.
good call, thanks for the reminder. I'll do that in 2.1.2-9.2, which
i'll upload shor
On Sat 2017-04-22 18:48:00 +, Niels Thykier wrote:
> On Sun, 26 Mar 2017 23:06:51 +0300 Sami Liedes wrote:
>> $ apt-get source gmime-bin
>> $ cd gmime-2.6.22/tests/
>> $ mkdir attachments
>> $ cd attachments
>> $ cat ../message-partial.* ../*.eml |ripmime -i -
>> $ ls -l *.jpg
>> -rw--- 1
Package: src:gmime
Version: 2.6.21-1
Severity: serious
Control: found -1 2.6.22+dfsg1-1
On Wed 2017-04-26 06:00:10 +, Chris Lamb wrote:
> Not 100% sure but is that a bunch of non DFSG-compliant stuff in
> tests/data/mbox/input/jwz.mbox? Either way, please clarify in
> debian/copyright.
> For
Hey Aaron--
On Wed 2017-04-26 10:17:56 -0400, Aaron M. Ucko wrote:
> Builds of hddemux in minimal environments (as on the autobuilders)
> have been failing:
>
> make[1]: pkg-config: Command not found
> [...]
> ./hddemux.c:378: undefined reference to `uv_stop'
> [...]
> ./hddemux.c:409: u
Source: wireguard
Version: 0.0.20161223-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Wireguard appears to be stable and reliable enough to distribute in
debian unstable, to get more widespread testing than would arise from
distribution in experimental alone.
However, t
close 844971 0.41-1
thanks
debian/changelog for 0.41-1 included the wrong bug number in one
entry, and should have mentioned Closes: #844971. the changelog will
be corrected in the next release.
Hi Thomas--
On Sat 2016-12-03 10:33:11 -0500, Thomas Leonard wrote:
> I can reproduce this on sid. It appears that GnuPG has started
> reporting incorrect error values. I have reported it here:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846834
>
> If that doesn't get fixed soon, I cou
Hi Adam, Julien--
On Mon 2016-12-05 18:23:14 -0500, Adam Borowski wrote:
> Same if you have a running X session but try to sign from the console;
> killing the gpg-agent doesn't help.
Please see https://bugs.debian.org/842015 for a very lengthy discussion
of this issue. I think this is the same
interesting, i see you're not using dbus or gnome3 at all, Adam.
On Mon 2016-12-05 22:45:19 -0500, Adam Borowski wrote:
> Curiously, after I logged in via vnc (pinentry did pop up in that session)
> then killed vnc, pinentry on ssh started working again. I expect this will
> stop once I restart t
Version: 0.9.6-1
https://bugs.debian.org/750521 has been resolved for a while, but the
BTS was confused about it. this e-mail should correct that.
--dkg
Control: severity 845565 normal
Please avoid severity inflation! "grave" means "makes the package in
question unusable by most or all users", and i don't believe that is the
case. Most users can use pinentry successfully, we're just establishing
the specific use cases where y'all are seeing fail
Hi Santiago--
thanks for the reportbacks-
On Mon 2016-12-12 18:17:37 +0100, Santiago Vila wrote:
> Hello. Sorry for the reopening but this issue is still happening in
> this version. I attach two different build logs.
thanks for the notes. the issue is now entropy starvation during
"monkeyspher
Control: reassign 868631 libcryptokit-ocaml-dev 1.11-1
Control: affects 868631 sks
On Mon 2017-07-17 04:22:35 +0300, Adrian Bunk wrote:
> Some recent change in unstable makes sks FTBFS:
>
> https://tests.reproducible-builds.org/debian/history/sks.html
> https://tests.reproducible-builds.org/debian
Control: affects 869774 + thunderbird
Control: retitle 869774 thunderbird 52 needs enigmail 1.9.8.1 or later
Control: forwarded 869774 https://sourceforge.net/p/enigmail/bugs/687/
Hi there--
On Thu 2017-07-27 12:42:26 +0300, Adrian Bunk wrote:
> After a short look at [1] there seem to be problems
On Thu 2017-07-27 16:21:21 +0200, Moritz Muehlenhoff wrote:
> We can provide a fixed 1.9.8.1-1 via jessie-security/stretch-security,
I've uploaded 1.9.8.1-1~deb8u1 for jessie-security and 1.9.8.1-1~deb9u1
for stretch-security, thanks! They're also available on the "jessie"
and "stretch" branches
On Thu 2017-07-27 17:23:25 +0200, Paul van der Vlis wrote:
> On Thu, 27 Jul 2017 09:59:46 -0400 Daniel Kahn Gillmor
> wrote:
>
>> I can confirm that enigmail 2:1.9.8.1-1 (from debian testing) installs
>> successfully on jessie and that it appears to fix the underlyi
On Thu 2017-07-27 21:41:18 +0200, Salvatore Bonaccorso wrote:
> On Thu, Jul 27, 2017 at 03:00:28PM -0400, Daniel Kahn Gillmor wrote:
>> On Thu 2017-07-27 16:21:21 +0200, Moritz Muehlenhoff wrote:
>> > We can provide a fixed 1.9.8.1-1 via jessie-security/stretch-security,
&g
On Sat 2017-07-29 16:20:09 +0200, Paul van der Vlis wrote:
> I've tried today the upgrade, but there was no new version.
>
> When I look at the end of this page:
> https://packages.debian.org/jessie/enigmail
>
> Then I see architecture "all" with version 2:1.9.8.1-1~deb8u1, and e.g.
> architecture
Control: reassign 849845 tor
Control: forcemerge 851798 849845
I believe that the only remaining problems with dirmngr and keyserver
resolution over Tor have to do with IPv6Traffic being set to "off" in
the standard tor configuration. So this isn't really a bug in dirmngr
(other than weak error
Package: gnupg-agent
Version: 2.1.17-2
Severity: grave
Justification: renders package unusable
Control: fixed -1 2.1.18-2
There is a crash in gpg-agent under heavily concurrent use.
See:
https://lists.gnupg.org/pipermail/gnupg-devel/2017-January/032499.html
This is reproducible on debian with:
close 852608 2.1.18-2
thanks
Control: affects 853935 + src:gnupg2
Hi folks--
On Thu 2017-02-02 05:37:30 -0500, Axel Beckert wrote:
> It seems that rephrase is incompatible or at least not yet ported to
> GnuPG 2.x.
>
> Trying to use it on Sid or Stretch causes one pinentry window popup per
> guessed try (i.e. potentially tho
Control: clone 836862 -1
Control: reassign -1 src:strongswan
Control: retitle -1 strongswan-starter should Provide: ike-server, not
strongswan-charon
On Tue 2016-09-06 11:46:29 -0400, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'ex
On Fri 2017-02-03 14:46:43 -0500, Axel Beckert wrote:
> The attached patch works for me with gpg aka gpg2.
>
> I'd also upload it as NMU in case I don't hear from the Debian
> Forensics team in time before a potential removal from testing (or if
> the team prefers the NMU).
Awesome. This is very
close 851384 0.8.2-1
thanks
This error in ocsp testing for mod_gnutls was dealt with upstream in
version 0.8.2. Sorry i didn't mention it in debian/changelog during
the upload!
--dkg
Hi all--
On Sat 2017-02-04 18:25:52 -0500, Cyril Brulebois wrote:
> I'm adding gnupg maintainers in cc since they might have interesting
> tips for the implementation. Context: we need to replace apt-key add
> calls with dropping files under the appropriate names for extra
> repositories in a Deb
On Sat 2017-02-04 19:35:58 -0500, Daniel Kahn Gillmor wrote:
> Over in #831409, i mentioned this simple pipeline to perform the actual
> transformation:
>
> awk '/^$/{ x = 1; } /^[^=-]/{ if (x) { print $0; } ; }' | base64 -d
>
> Unfortunately, it looks to me
On Sat 2017-02-04 19:48:54 -0500, Cyril Brulebois wrote:
> I'm fine with (discovering and) following best practices.
:)
> [ dkg wrote: ]
>> Regardless of the choice of filesystem location (fragment directory or
>> elsewhere), gpgv does want to see the curated keyrings it depends on
>> in binary f
Control: tags 854616 + moreinfo
Hi Anarcat--
thanks for all this documentation on #854616. I'd like to try to
differentiate this report from #854005.
#854005 is about problems with smartcards more generally.
The new bug, #845616, should be focused specifically on the use case
where pcscd is *n
y
>
> On Tue, 2017-02-07 at 11:14 -0500, Daniel Kahn Gillmor wrote:
>> On Tue 2017-02-07 10:49:39 -0500, Daniel Kahn Gillmor wrote:
>> > git clone https://0xacab.org/dkg/debian-bug-854421
>> > cd debian-bug-854421
>> > make
>>
>> inte
On Wed 2017-02-08 16:15:21 -0500, NIIBE Yutaka wrote:
> No, this is not a hack. This is a configuration needed.
>
> It seems for me that Yubico has been recommended use of PC/SC service.
> Since no one has reported for use of internal CCID driver, there is no
> entry for Yubikey in /lib/udev/rules
On Mon 2017-02-06 04:49:44 -0500, Vincent Lefevre wrote:
> On 2017-02-02 19:29:19 +0100, Vincent Bernat wrote:
>> Index: pinentry-1.0.0/gtk+-2/pinentry-gtk-2.c
>> ===
>> --- pinentry-1.0.0.orig/gtk+-2/pinentry-gtk-2.c
>> +++ pinentry-1
4c91bae777022f7ffd2ac4fa69837d59653eeb8f
Author: Daniel Kahn Gillmor
Date: Mon Feb 13 09:41:56 2017 -0500
prepare new debian release
diff --git a/debian/changelog b/debian/changelog
index edd953b..bca7302 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+gnupg2 (2.1.18-5) unstable; urgency=medium
reassign 841103 dirmngr
close 841103 2.1.15-6
forcemerge 840680 841103
thanks
https://bugs.debian.org/841103 is the same issue as
https://bugs.debian.org/840680
Control: affects 84 + gnupg
On Wed 2016-11-16 03:42:14 +0900, Jonas Smedegaard wrote:
> Package: parcimonie
> Version: 0.10.2-4
> Severity: serious
> Justification: Policy 3.5
>
> parcimonie depends on gnupg-curl, but that package is no longer available
> in the Debian unstable archive.
parci
Hi there Stiepan--
On Wed 2017-08-09 01:21:38 +0200, Stiepan Aurélien Kovac wrote:
> seems to have broken enigmail support, at least on the ppc (powerpc64) arch.
I don't think this is a ppc-specific issue -- nothing in the current
version of enigmail is debian-specific. I also think your issue h
On Fri 2017-08-11 10:38:10 +0200, Adrian Ban wrote:
> Yesterday after upgrading my Laptop and a VM both on Debian Sid I've
> notice exactly the same issues mentioned here.
> .
> In the begging I thought is my Laptop issue
> but after checking the VM I've notice that is a Thunderbird/system issu
On Fri 2017-03-03 16:38:15 +0800, Chris Lamb wrote:
> I just ACCEPTed python-pgpy from NEW but noticed it was missing
> attribution in debian/copyright for at least gentoo/pgpy-0.4.0.ebuild.
I'm a bit confused by this bug report, because it seems to be captured
correctly by debian/copyright to me
close 871128 3.21-1
thanks
This FTBFS bug was addressed by libreswan upstream, and the fix was
included in 3.21.
Control: retitle 871465 python3-gpg package should ship tofu module
On Tue 2017-08-08 12:51:59 +0300, Adrian Bunk wrote:
> On Tue, Aug 08, 2017 at 03:11:40AM -0400, Jonathan Carter wrote:
>>...
>> File "/usr/lib/python3/dist-packages/gpg/constants/__init__.py", line
>> 28, in
>> from . impo
b5f7cb174d80d3e252f947d6790f3e01f91ffa9e
Author: Daniel Kahn Gillmor
Date: Thu Aug 17 22:17:18 2017 -0400
prepare debian release
diff --git a/debian/changelog b/debian/changelog
index 3958fa8..4bc0875 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+gpgme1.0 (1.9.0-3) unstable; urgency=medium
close 871904 2.1.23-2
thanks
On Fri 2017-08-18 10:02:49 +0300, Adrian Bunk wrote:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-archive-keyring.html
>
> ...
> gpg --no-options --no-default-keyring --no-auto-check-trustdb --trustdb-name
> ./trustdb.gpg \
> --keyring keyrings/team-members.gpg
Hi all--
On Tue 2016-10-11 16:44:28 -0400, gregor herrmann wrote:
> On Mon, 10 Oct 2016 23:10:30 +0300, Niko Tyni wrote:
>
>> Help untangling this mess would be very welcome, as both Dominic and I
>> are rather short on time. Tagging and copying possible candidates :)
>
> Good news: I got the pack
Control: reopen 840575
Control: found 840575 0.71.0-2
Control: retitle 840575 sbuild should Depends: gnupg (>= 2.1)
Control: affects 840575 src:gnupg2
On Wed 2016-10-12 18:07:39 -0400, James Clarke wrote:
> Bugs in backported packages should not be sent to the BTS, but to
> debian-backports (CC'ed
Control: tags 840680 + unreproducible moreinfo
Control: severity 840680 important
hi Shengjing--
Thanks for this report. it sounds frustrating! I hope we can debug it:
On Thu 2016-10-13 15:12:44 -0400, Shengjing Zhu wrote:
> After upgrade to 2.1.15-4, I find dirmngr is not always responding
>
On Fri 2016-10-14 01:36:56 -0400, Johannes Schauer wrote:
> - it is a feature of sbuild since version 0.67.0 (I corrected the wiki page
>accordingly) to *not* require signing of the internal dummy repository (and
>thus you don't need to run sbuild-update --keygen anymore) and that
awesome
464ddb58d795924c588e064bdd5d5d7d479c413a
Author: Daniel Kahn Gillmor
Date: Wed Oct 26 17:44:47 2016 -0400
prepare new bugfix release
diff --git a/debian/changelog b/debian/changelog
index 8c5a15c..923636c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+gnupg2 (2.1.15-6) unstable; urgency=medium
Hi Dhole and Craig--
Thanks for your reports of dirmngr not responding. I've tried to
reproduce this bug, and actually found it easiest to reproduce with:
GNUPGHOME=$(mktemp -d) gpg-connect-agent --dirmngr
This should produce the following debugging info, followed by a "> "
prompt:
gp
6a4d35e3e3514bd1910362ad7ea744feb5933db8
Author: Daniel Kahn Gillmor
Date: Tue Nov 1 04:25:18 2016 -0400
prepare release
diff --git a/debian/changelog b/debian/changelog
index e26f89b..b02bfd4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+gpgme1.0 (1.7.1-3) experimental; urgency=medium
+
+ [ Sandro
1 - 100 of 454 matches
Mail list logo
