On 06/17/2016 05:19 AM, Petter Reinholdtsen wrote:
> I tried to add udev setup as you proposed, ran 'service udev reload' and
> tested by unplugging and plugging in the smart card reader, without any
> luck.
I think that there is some problem for udev. When udev works, we can
see followng (my dev
On 06/17/2016 10:38 PM, Petter Reinholdtsen wrote:
> Here is the same output from 'gpg2 --card-status' on a amd64 machine:
Thanks a lot. OK, it works on amd64 machine with PC/SC service.
> 2016-06-17 15:34:07 scdaemon[8236] DBG: ccid-driver: using CCID reader 0
> (ID=08E6:3438:X:0)
> 2016-06-17
OK, I located the issue for ccid-driver. It is fixed in our
repository.
master:
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=971064f8b7ad676326b2a468f688037a303717df
2.0.x:
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=c68d39f7114623075c0b407b05927b61b190a377
Sorry for the trouble because of my subkey.
In my file, the subkey packet in question is like following:
---
# ctb=b8 tag=14 hlen=2 plen=79
:public sub key packet:
version 4, algo 19, created 1389837376, expires 0
pkey[0]: [48 bits] secp256k1 (1.3.132.0.10)
On 06/28/2016 02:43 AM, Daniel Kahn Gillmor wrote:
> On Mon 2016-06-27 02:25:33 -0400, NIIBE Yutaka wrote:
>> Sorry for the trouble because of my subkey.
>
> thank you for being the experimental subject on whome the bugs are
> found, gniibe :)
Thanks, it's my pleasure. :-
On 06/26/2016 07:22 PM, Kurt Roeckx wrote:
> Source: libopkele
> Version: 2.0.4-8.1
> Severity: important
> Control: block 827061 by -1
>
> Hi,
>
> OpenSSL 1.1.0 is about to released. During a rebuild of all packages using
> OpenSSL this package fail to build. A log of that build can be found a
On 04/25/2016 04:48 AM, John David Anglin wrote:
On 2016-04-24, at 12:57 PM, John David Anglin wrote:
It looks like this was introduced by the following change:
diff --git
a/debian/patches/0006-fix-Solaris-and-HPPA-this-is-a-collection-of-upstrea.patch
b/debian/patches/0006-fix-Solaris-and-
On 03/31/2016 04:56 PM, Petter Reinholdtsen wrote:
[Petter Reinholdtsen]
My only ideas is something is wrong with the armel architecture
support of some of the packages involved, or the Raspberry Pi is
unable to provide enough power to the smart card reader and smart card
for the smart card to w
On 04/27/2016 01:10 AM, Daniel Kahn Gillmor wrote:
i'm still seeing the doubled GET parameters caused by mod_auth_openid
that are described in https://bugs.debian.org/634800
The patch supplied at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634800#45 applies with
a very small fuzz, and reso
Hello,
On 2014-07-03 at 22:48 -0400, Daniel Kahn Gillmor wrote:
> I just tried to do this for powerpc (from x86-64) and didn't manage to
> create a powerpc executable for gen-posix-lock-obj. I'm not sure what
> i'm doing wrong, but below is a transcript of the full attempt,
> including a demonstr
Hello,
I had same issue.
On Sat, 04 Jul 2015 21:19:11 +0200 Yves-Alexis Perez wrote:
> Well, this variable is not set by default, and the code explicitly
> checks for TRUE so you seem to had it set to TRUE somewhere.
> >
> > So, xfce4-session is clearly stomping on the toes of
> > /etc/X11/Xses
On 07/09/2015 01:29 AM, Kurt Roeckx wrote:
> 16:25:44.564660 gettimeofday({1436372744, 564670}, NULL) = 0
> 16:25:44.564689 getrusage(RUSAGE_SELF, {ru_utime={0, 0}, ru_stime={1,
> 964000}, ...}) = 0
> 16:25:44.564740 clock_gettime(CLOCK_PROCESS_CPUTIME_ID, {1, 965043294}) = 0
> 16:25:46.513466 tim
Hello,
This is reply to old bug report to GnuPG 1.4. Sorry, it took so long
time to looking into detail.
I tried to reproduce the bug with recent implementations (GnuPG 1.4,
2.0, and 2.1), but I couldn't. Since importing secret key
automatically creates corresponding public key, something stran
On 05/08/2015 02:58 PM, NIIBE Yutaka wrote:
> Please let us know reproducible scenario if it still exists in current
> gpg 1.4. If it is not reproducible, I wonder if we can close this bug?
Finally, I managed to reproduce this bug. Here is my scenario.
(1) With --gen-key, generate DSA+E
On 05/08/2015 04:51 PM, NIIBE Yutaka wrote:
> Finally, I managed to reproduce this bug. Here is my scenario.
>
> (1) With --gen-key, generate DSA+Elgamal key
> (2) make a encrypted file using (1)
> (3) make a copy of .gnupg/secring.gpg
> (4) With --edit-key, delkey Elgamal
On 05/31/2015 06:25 PM, Moritz Muehlenhoff wrote:
> I've configured it on my notebooks for a while now:
>
> If you install the attached unit file to /usr/lib/systemd/user
> the unit can be activated on a per-user basis with
> "systemctl --user enable gpg-agent.service"
>
> (Of course, following t
On 11/29/2014 04:35 AM, Pandu Rao wrote:
> Both /dev/random and /dev/urandom seem to work fine.
Thanks for your checking.
It would be good if you have a small test case which can reproduce the
failure. I tried duplicity with scp myself, but I couldn't reproduce
the bug.
The error occured with t
Thank you for your report.
On 12/11/2014 10:05 AM, David Z wrote:
> Created a new keypair today. Was unable to add a subkey, even though all keys
> involved are within expected limits (4096 bit RSA).
>
> Dies at:
>
> gpg: writing key binding signature
> gpg: out of secure memory while allocating
Thank you. It is now reproducible for me (i386 and amd64) with
gnupg 1.4.12-7+deb7u6.
I think that the combination of:
Your configuration of: s2k-cipher-algo S10
Adding RSA-4096 subkey for sign
RSA Blinding
... are things to cause the issue.
I don't have a solution/work
On 12/11/2014 11:29 PM, David Z wrote:
> Would increasing the amount of secure memory that's allocated be a
> reasonable fix?
Right. That would make sense, given the condition: Something like
that has been introduced in the Debian build of gnupg 1.4.x for jessie
(the forthcoming release).
But I
Thank you for your report.
On 01/17/2015 08:55 PM, Luca Bruno wrote:
> With the latest gnupg2 package targeted for the Jessie, defaulting hashing
> algorithm has been changed to SHA256. This broke my smartcard setup using a
> cryptostick/nitrokey (storage version, latest 0.18 firmware) as signing
On 12/19/2014 05:47 PM, Joshua Rogers wrote:
> Package: gnupg2
> Version: 2.1.1
> Severity: normal
>
> in app-nks.c on line 1242, data is assigned the memory of 'datalen',
> which is calculated using oldpinlen + newpinlen.
> The problem is, it doesn't account for the terminating null byte, so
> it
On 12/20/2014 09:38 AM, Joshua Rogers wrote:
> Inside the get_public_key function, 'fp' was opened using popen, but
> incorrectly closed using fclose.
>
> From pclose(2):
>The return value from popen() is a normal standard I/O stream in
>all respects save that it must be closed wi
Hello,
While my debugging of gnupg-agent, I found that I couldn't attach
gpg-agent to GDB any more.
Now, the kernel default seems to be kernel.yama.ptrace_scope = 0
$ cat /proc/sys/kernel/yama/ptrace_scope
0
For debugging, now, I need to change this setting of kernel. Given
this recent
Hello,
Thanks for your reviewing and reporting.
On 12/20/2014 02:19 AM, Joshua Rogers wrote:
> Package: gnupg2
> Version: 2.1.1
> Severity: normal
[...]
> On line 204 of crlfetch.c 'hd' is run through http_get_status_code,
> but it is possible for 'hd' not to be set, if opt.disable_http is
> true
Hello,
Thanks for your reviewing and reporting.
On 12/19/2014 10:04 PM, Joshua Rogers wrote:
> Package: gnupg2
> Version: 2.1.1
> Severity: normal
[...]
> on line 253 of ecdh.c, memset is called with a 0 fill value, which
> will do nothing. what's the point?
Well, I guess that the intention of t
Hello,
Thanks for your reviewing and reporting. This message is Cc-ed to
gnupg-devel.
On 12/19/2014 09:56 PM, Joshua Rogers wrote:
> Package: gnupg2
> Version: 2.1.1
> Severity: normal
[...]
> In ks-engine-hkp.c on line 509 'reftbl' is freed, but it is then
> used on line 511. I'm guessing this
Hello,
Thanks for your reviewing and reporting. This message is Cc-ed to
gnupg-devel.
On 12/19/2014 07:24 PM, Joshua Rogers wrote:
> Package: gnupg2
> Version: 2.1.1
> Severity: normal
>
> in dirmngr/ldap.c on line 617, argv may be overflowed.
>
> 617: argv[argc++] = url;
>
> a check is made
On 01/07/2015 02:54 PM, NIIBE Yutaka wrote:
> Here's my fix. I'm going to apply this change since it's obvious
> simple fix and there will be no conflict.
>
> diff --git a/dirmngr/ldap.c b/dirmngr/ldap.c
> index 478fdfd..00df167 100644
> --- a/dirmngr/ldap.c
&
On 01/07/2015 05:22 PM, Werner Koch wrote:
> But there is a portability problem. From libgcrypt's rndunix.c:
Thanks for your information, I see. I also checked gnulib and found
there are other issues for popen/pclose. In future, in case we want
to improve OpenPGPcard v1.0 support, we should thi
On 01/07/2015 01:58 PM, NIIBE Yutaka wrote:
> Here is my fix along with other fixes in map_host function.
[...]
> @@ -504,9 +506,11 @@ map_host (ctrl_t ctrl, const char *name, int
> force_reselect,
>hi->pool = xtryrealloc (reftbl, (refidx+1) * sizeof *reftbl);
>
On 01/18/2015 07:19 PM, Frederik Himpe wrote:
> It looks like I'm hitting exactly the same issue:
> Jan 18 09:19:49 Error: = Begin GnuPG log =
> Jan 18 09:19:49 Error: *** buffer overflow detected ***: gpg terminated
> Jan 18 09:19:49 Error: === Backtrace: =
Thank you for your
Hello,
On 04/14/2015 09:38 PM, Josselin Mouette wrote:
> Sorry, I was under the impression this was a discussion about actually
> improving the situation, not about Debian being used as a playground for
> petty complaints about other upstreams.
>
> If you want to disable this functionality on yo
is a diff to current gnupg package.
--
>From 31e844a58dc9cd8f562316f1a7a72a3db2dcbe11 Mon Sep 17 00:00:00 2001
From: NIIBE Yutaka
Date: Fri, 2 Oct 2015 10:24:00 +0900
Subject: [PATCH] Add important fixes from upstream
---
.../patches/0008-po-Fix-Spanish-translation.patch |
Hello,
On 09/14/2015 10:27 PM, Yuri D'Elia wrote:
> ssh-agent support seems to be broken in 2.1.8.
[...]
> which seems to be just one byte longer than 2.1.8.
I think that you are using ed25519 key.
It is fixed in 2.1.9, but you need to remove corresponding private key
at first and to register yo
Hello,
I think that this bug is fixed in 2.1.9. Please confirm.
Thank you for your bug reports.
--
Hello,
I think that this bug is fixed in 2.1.9. Please confirm.
--
On 07/01/2015 07:37 AM, Daniel Kahn Gillmor wrote:
> we checked with Q_, who looked at the buildd, and it's definitely
> hanging running agent/t-protect: the process is in R (running) state.
>
> agent/t-protect.c is pretty simple, and it's not hanging on other
> architectures. I'm perplexed as to
On 2014-09-09 at 23:09 -0400, Daniel Dickinson wrote:
> The GPME library returned an unexpected error at keytable.c:150. The was:
> Unsupported certificate
I think that it is GNOME keyring which gets the connection to
gpg-agent (and produced the error).
Please see the message below and try to di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/10/2014 01:58 PM, Daniel Dickinson wrote:
> On 09/09/14 11:23 PM, NIIBE Yutaka wrote:
>> On 2014-09-09 at 23:09 -0400, Daniel Dickinson wrote:
>>> The GPME library returned an unexpected error at
>>> keytable.c
On 08/31/2014 07:46 AM, Niko Tyni wrote:
> The problem, of course, is that libperl.so moved from /usr/lib/libperl.so
> to /usr/lib//libperl.so, so it looks like debian/rules needs
> to be updated accordingly. Patch attached, this makes it build for me.
Thank you for your patch. I changed debian/r
Hello, Frederic,
Thank you for your report. I'll include your change and upload new
version this week.
On 10/25/2014 12:06 AM, Frederic Bonnard wrote:
I had it working all the time in a ppc64el UP chroot. I guessed it's
something to do with threading.
Just FYI. Around the time of gauche 0.9
On 11/28/2014 10:51 AM, Pandu Rao wrote:
> Package: gnupg
> Version: 1.4.18-4
> Severity: normal
[...]
> *** buffer overflow detected ***: gpg terminated
> === Backtrace: =
> /lib/x86_64-linux-gnu/libc.so.6(+0x7303f)[0x7f581fd9d03f]
> /lib/x86_64-linux-gnu/libc.so.6(
Ian Jackson wrote:
>gpg --ignore-time-conflict
> --no-options
> --no-default-keyring
> --homedir
> /tmp/apt-key-gpghome.yLlu1bwwPI
> --no-auto-check-trustdb
> --trust-model
> always
> --batch
> --import
Thank you for minimizing. I'd like to clarif
intrigeri wrote:
> So I'm reassigning this to gnupg-agent, where the root cause of the
> problem seems to live.
It seems for me that gpg-agent can not do anything for this bug.
I tried to locate the invocation of "gpg" from seahorse. I figured out
that when this issue occurred (replacing gpg by
Control: reassign -1 gcr
NIIBE Yutaka wrote:
> Now, I guess that the problem is in the implementaiton of libgcr library.
>
> While I'm reading gcr-3.20.0/gcr/gcr-gnupg-process.c, getting the source
> by apt source libgcr-base-3-1, I suspect the function
> _gcr_gnupg_proc
Ian Jackson wrote:
>> The invocation of gpg-agent by gpg frontend has an inherent race in the
>> current implementation; When gpg frontend invokes gpg-agent, after
>> spawning gpg-agent, gpg frontend tries to connect five times with one
>> second intervals. When a machine is busy enough and sched
Osamu Aoki wrote:
> If what NOKUBI Takatsugu's comment is correct, I wonder why anthy is
> upgraded without coordinating with key users:
> ibus
> uim
> fcitx
>
> (Please note these have many dependence packages so the testing
> migration is slow if package version dependency is correctly record
Ian Jackson wrote:
> I tried this. I applied this change and I can confirm that I have
> seen this message in all the failing tests I looked at.
OK.
> With that patch, I can still reproduce the failure. The passing tests
> succeed and exit, leaving a failing test (so far, only one out of a
> t
cry_mpi_ec_mul_point for concrete example for those
routines. That's for constant-time computation.
Debian-bug-id: 866964
Suggested-by: Mark Wooding
Signed-off-by: NIIBE Yutaka
(backport from master commit:
5feaf1cc8f22c1f8d19a34850d86fe190f1432e2)
1 file changed, 1 insertion(+), 1 deletion(-
Hello,
intrig...@debian.org writes:
> gpg-agent[11835]: DBG: error calling pinentry: Inappropriate ioctl for
> device
This error message is related to DISPLAY or GPG_TTY.
I guess that pinentry is invoked with no DISPLAY and no GPG_TTY. It
failed to open window, and then, it failed at isatty
Thanks for your reply.
intrigeri wrote:
> Anything else I should try? Something about $GPG_TTY, or starting
> Seahorse from GNOME Terminal (instead of the GNOME Overview), perhaps?
It seems that the most likely case is the following scenario:
(1) Upon login, gpg-agent is invoked with no DISPL
On 08/03/2016 09:03 PM, Petter Reinholdtsen wrote:
> Thank you. I just tested on a Raspberry Pi using the gnupg2/scdaemon
> version 2.1.14-2 in Debian experimental, and this now segfaults when I
> try 'gpg2 --card-status'. But for some reason I can't get info from
> valgrind, so here is the backt
On 08/03/2016 10:10 PM, Petter Reinholdtsen wrote:
> My original test was done using a Freedombox image, which was armel.
>
> Todays test was done using some random RPi and SD card I found on my
> desk and I did not notice it was using a different architecture. I can
> try again on armel, if you
On 08/05/2016 09:01 PM, Petter Reinholdtsen wrote:
> I decided to test again using an FreedomBox image to reduce the
> difference since my initial testing. First I tested using version
> 2.1.11-7 in Debian testing, and then using version 2.1.14-1 in Debian
> experimental. Both fail. First the tes
On 08/05/2016 10:52 PM, Petter Reinholdtsen wrote:
> fbx@freedombox:~$ sudo chmod a+rw /dev/bus/usb/001/00*
> fbx@freedombox:~$ gpg2 --card-status
> Reader ...: 08E6:3438:C4CC14F3:0
> Application ID ...: D27600012401020100054202
> Version ..: 2.1
> Manufacturer .: ZeitCo
Hello,
I am reading GNU C library manual.
24.7.2 Signal Sets:
https://www.gnu.org/software/libc/manual/html_node/Signal-Sets.html
All functions have MT-Safe | AS-Safe | AC-Safe attributes.
So, I wonder what your problem is, and what you are suggesting.
> This code is not properly reent
Ian Jackson wrote:
> I think that at least my patch
> [PATCH 4/4] gpg agent lockup fix: Interrupt main loop when
> active_connections_value==0
> is very likely a fix to an actual race.
[...]
> I would like this bug fixed in stretch.
I think that this issue is a bug in the patches of
debian/pat
Hello,
I'm sorry I didn't put the context. I am a developer of GnuPG and nPth.
I join the Debian GnuPG mailing list, so that development can go well.
Thus, I receive your bug report. (I also maintain some packages in
Debian but most are not related to GnuPG.)
Since I felt that there is a kind o
Daniel Kahn Gillmor wrote:
> fwiw, i don't want the behavior to be exactly the same as upstream -- i
> don't want gpg-agent to wake up every few seconds on platforms where it
> shouldn't need to, for example :/
Yes, I understand your purpose. +1 from me. Actually, I was inspired
by your patches
Hello,
Thanks to dkg to explicitly CC me.
On Thu 2017-02-02 17:54:26 -0500, Wouter Verhelst wrote:
> Since a recent upgrade, gnupg-agent no longer finds the authentication
> (SSH) key on my OpenPGP smartcard:
>
> wouter@gangtai:~$ gpg --card-status
It should be an issue of scdaemon. For 2.1.18,
Wouter Verhelst wrote:
> wouter@gangtai:~$ cat .gnupg/scdaemon.conf
> reader-port O2 Micro Oz776 01 00
> log-file /home/wouter/.gnupg/scdaemon.log
> pcsc-driver libpcsclite.so
Ah... I think that I enbugged a bug for PC/SC, and scdaemon with PC/SC
is somehow broken in 2.1.18. Please try with inte
NIIBE Yutaka wrote:
> Ah... I think that I enbugged a bug for PC/SC, and scdaemon with PC/SC
> is somehow broken in 2.1.18. Please try with internal CCID driver of
> GnuPG. I mean, don't use PC/SC service.
Or, please add:
disable-ccid
in your scdaemon.conf if you wan
Shin Ice writes:
> Package: gnupg2
> Version: 2.1.18-3
> Severity: important
>
> --- Please enter the report below this line. ---
>
> Hi,
>
> after upgrading gnupg2 (and related) to version 2.1.18-3 the yubikey 4
> can't be used. On a different system (still sid) with version 2.1.16-3
> all works
On 11/29/2016 06:46 AM, Hans Freitag wrote:
> Exporting ssh2 keys is not working with gnupg 2.1.16
>
> $ gpg2 --export-ssh-key SOMEKEYID
> gpg: O j: Assertion "ret_found_key == NULL || ret_keyblock != NULL"
> in lookup failed (../../g10/getkey.c:3677)
> Abgebrochen
Thank you for bug repo
Package: emacs25-common
Version: 25.1+1-3
Severity: important
Dear Maintainer,
I did clean install of Debian Stretch and found that M-x info doesn't
work well (because of empty dir entries). That's because install-info
was not installed when I installed Emacs25 (so, I manually installed
install-
On 10/10/2016 10:11 PM, Petter Reinholdtsen wrote:
> Hi. I got a smart card reader from Fujitsu Siemens that is not
> recognized by scdaemon. Perhaps it should be added to the udev rules.d
> file?
Thanks for the report. If it works well, it should be added.
> Perhaps it is better to try to rec
Package: modemmanager
Version: 1.6.2-1
Severity: normal
Dear Maintainer,
I develop/use/sell USB TRNG (True Random Number Generator) device
which works as an USB CDC/ACM device.
The intention is that users can get the random bytes from /dev/ttyACM0
with no drivers installed. Unfortunately modemm
I replied only to the pkg-gnupg-maint list. I send again to the bug
tracker.
On 10/03/2016 06:44 AM, Kevin Gallagher wrote:
> I updated packages at some point and now my smartcards don't work,
> because scdaemon has disappeared.
In the migration of gnupg2 to gnupg, scdaemon'
Hello,
YunQiang Su wrote:
> gpg: error writing public keyring '[keyboxd]': Attempt to write a
> readonly SQL database
> Key generation failed: Attempt to write a readonly SQL database
I can't replicate this issue on my system. With a new user I created
for the test, I had no problem; The direct
Hello, again,
YunQiang Su wrote:
> gpg: error writing public keyring '[keyboxd]': Attempt to write a
> readonly SQL database
> Key generation failed: Attempt to write a readonly SQL database
NIIBE Yutaka wrote:
> I can't replicate this issue on my system. With a n
Hello,
Julian Wollrath wrote:
> after updating to 2.2.43 I cannot use a key stored on a Yubikey (with
> KDF enabled, not sure, if that matters) anymore, since the PIN is
> rejected:
> gpg-agent[38887]: detected card with S/N XXX
> gpg-agent[38889]: scdaemon[38889]: sending signal 12 to client 388
Hello,
For your information, let me explain about regexp support.
Daniel Kahn Gillmor wrote:
> regexp/_unicode_mapping.c | 284 +
[...]
> Maybe the right (and more up-to-date) solution is to build-depend on
> unicode-data, strip both this file and UnicodeData.txt in
>
Package: wnpp
Severity: wishlist
Owner: NIIBE Yutaka
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: sp800-90b-entropy-assessment
Version : 1.1.5
Upstream Contact: Chris Celi
* URL : https://github.com/usnistgov/SP800-90B_EntropyAssessment
* License
NIIBE Yutaka wrote:
> I'm going to backport the improvement to my branch of tmp-gniibe-v2.4
> for Debian.
I backported and pushed my changes to tmp-gniibe-v2.4.
https://salsa.debian.org/gniibe/gnupg2
This is Debian compatible version of GnuPG 2.4.1.
--
Hello,
NIIBE Yutaka wrote:
> I backported and pushed my changes to tmp-gniibe-v2.4.
>
> https://salsa.debian.org/gniibe/gnupg2
>
> This is Debian compatible version of GnuPG 2.4.1.
Today, I merged 2.4.3 from Andreas Metzler's tmp-ametzler-v2.4 branch.
This is Debian c
Hello,
Andreas Metzler wrote:
> On 2023-04-30 Andreas Metzler wrote:
> [...]
>> However I have updated the GIT branches to 2.4.1 today.
>
> Now at 2.4.3.
Based on your work of tmp-ametzler-v2.4 branch, I created my own fork.
My hope is that the migration from 2.4 won't introduce (much) surpris
NIIBE Yutaka wrote:
> Based on your work of tmp-ametzler-v2.4 branch, I created my own fork.
>
> My hope is that the migration from 2.4 won't introduce (much) surprise
> to Debian users.
>
>https://salsa.debian.org/gniibe/gnupg2/-/tree/tmp-gniibe-v2.4
>
> This wo
NIIBE Yutaka wrote:
> Besides, in my opinion, the agent_cache_housekeeping function makes less
> sense (it's totally OK to only check the expiration on its use). Having
> expired entries on memory is no problem at all, than running gpg-agent
> process periodically; memory is
Bjarni Ingi Gislason wrote:
> Package: gpgrt-tools
> Version: 1.47-2
> Severity: normal
>
> Dear Maintainer,
>
> The following are issues that yat2m needs to correct when producing
> man-page formatted manuals.
>
> The example is from "gpg(1)".
Thank you for your bug report and good descript
NIIBE Yutaka wrote:
> I was wrong. The ticket for agent_cache_housekeeping is:
>
> https://dev.gnupg.org/T3829
>
> It was introduced because of some risk keeping passphrase.
>
> I'd like to consider to improve the implementation of cache and
> expiration, n
Andreas Metzler wrote:
> Package: gnupg2
> Version: 2.4.5-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>From GnuPG, I factored out spawn functions into libgpg-error (mainly for
support of Windows 64-bit). Since libgpg-error
retitle 462492 ITP: Foreign Function Interface for Gauche to C-based libraries
owner 462492 NIIBE Yutaka <[EMAIL PROTECTED]>
thanks
I'll package it soon.
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
retitle 452026 ITA: golly -- Game of Life simulator using hashlife algorithm
thanks
I will do the packaging soon.
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
retitle 461663 ITP: ngetty -- one single daemon for all consoles
owner 461663 NIIBE Yutaka <[EMAIL PROTECTED]>
thanks
I'll package it in a week or so.
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
retitle 411710 ITP: libqrencode -- A C library for encoding data in a QR Code
symbol
owner 411710 NIIBE Yutaka <[EMAIL PROTECTED]>
thanks
I will package it in a month or so. If not, please do it.
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
Package: wnpp
Severity: wishlist
Owner: NIIBE Yutaka <[EMAIL PROTECTED]>
* Package name: tomoe
Version : 0.6.0
Upstream Author :
Takuro Ashie <[EMAIL PROTECTED]>
HIGUCHI Daisuke <[EMAIL PROTECTED]>
Juernjakob Harder <[EMAIL PROTECT
Daniel Kahn Gillmor wrote:
I see that in february, this ITP for libapache2-mod-auth-openid was
claimed to be fixed by a package in the NEW queue, but now (nearly 6
months later) nothing has even shown up in unstable or experimental.
What's the status on this package?
I once built the package a
Just a quick replay,
Daniel Kahn Gillmor wrote:
> Would you mind publishing your packaging details? I'd be willing to
> try to switch TLS implementations if that's a possiblity. i'd very
> much like to see this functionality be easily accessible in debian.
Here it is:
http://www.gniib
Michael Schutte wrote:
> severity 494428 important
[...]
> libdb-ruby has migrated, I’m thus raising the severity of this issue.
> Yutaka, Yasuhiro, I’ll prepare an NMU to include the patch submitted in
> the original message if you do not object.
Please go ahead, and do NMU.
Now, I am talking to
Package: libccid
Version: 1.3.8-1
Severity: normal
Hi, there.
I think that current implementation for ICCD version A does not work
well. While I am implementing ICCD device, I found some problems.
(Note that I don't have any ICCD version A device other than my own
development device. So, my un
Junichi Uekawa wrote:
> You've been sitting on this ITP for half-an-year, unless you already
> have got a package to upload, please give up and hand the package over
> to someone responsible.
It just need some time, that's the situation. I mean, I am
responsible.
After I submitted ITP, it found
Package: gauche
Version: 0.8.7-3
Severity: important
gauche-gl package cannot be built with new version 0.8.7.
It is because new version quotes much more than needed.
Could you please consider to include following patch in gauche?
This problem has been reported to upstream already.
You can repro
I think that the problem is modifying the variable LOAD_PATH
(in treil.rb). When ruby tries to load cairo.rb, it loads
cairo.so, that's the issue.
Commenting out that line, it works fine for me.
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
Ahmed El-Mahmoudy wrote:
Package: gplcver
Version: 2.11a-3
Hello,
I was trying GPL Cver 2.11a on a verilog module that has
multi-dimensional arrays (the module is attached with this email), and
it gave the error below:
I think that multi-dimensional arrays is not the supported feature
Package: wnpp
Severity: wishlist
Owner: NIIBE Yutaka <[EMAIL PROTECTED]>
* Package name: verilog-mode
Version : 357
Upstream Author : Michael McNamara <[EMAIL PROTECTED]>
* URL : http://www.verilog.com
* License : GPL
Programming Lang
I think that the cause of this bug is the use of BSD pty.
Currently in debian/rules, ttyrec is compiled for BSD standard
(deprecated, I think).
I think following patch should apply for Debian build.
--
--- rules.orig 2007-08-25 16:16:16.0 +0900
+++ rules 2
We have now version 0.6 at:
http://www.a-k-r.org/htree/
Please update the package.
If you don't have time, I would like to take over.
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: audit
Version: 1.7.13-1
Severity: normal
I sent a bug report to upstream (linux-au...@redhat.com), but it seems
it doesn't work. So, I am filing the bug report into Debian BTS.
I am using audit-1.7.13 on Debian. Using the tool auditctl, I got an
error when I tried to specify inode with
Hello,
How's it going? If you are busy, I would like to package it up,
because I would like to use newer elfsh.
Could you please let me know the status of your packaging?
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
101 - 200 of 302 matches
Mail list logo
