Dear mentors,
I am looking for a sponsor for my package "acsccid".
* Package name: acsccid
Version : 1.0.3-1
Upstream Author : Advanced Card Systems Ltd.
* URL : http://acsccid.sourceforge.net/
* License : LGPL-2.1+
Section : libs
It builds those b
Dear Kilian
Finally, my package "acsccid 1.0.3-1" had been reviewed by Paul and I had
modified the package according to his comment.
You may be busy at this moment. Please take a look of my package as soon as
possible. I would be glad if you uploaded my package for me.
Regards
Godfrey
On Fri, Jan 27, 2012 at 11:33 PM, Godfrey Chung wrote:
> I sent the e-mail to Secure Testing Team at home tonight. Hope that they can
> receive my e-mail. Thanks!
I've added your changes to SVN.
If yourself or anyone else wants to get involved in tracking security
issues in Debian, please take a
Dear Paul
I sent the e-mail to Secure Testing Team at home tonight. Hope that they can
receive my e-mail. Thanks!
Regards
Godfrey
Dear Paul
I cannot send the e-mail to the following address. It seems that our SMTP
server cannot do the identity verification. Can you help me to forward the
e-mail to Secure Testing Team?
---
Dear Secure Testing Team
I would like to add the following entries to the embedded-code-copies file.
acsccid is a fork of ccid and is based on ccid 1.3.11.
acsccid
- ccid 1.3.11 (fork)
ccid
- openct (modified-embed)
- towitoko (modified-embed)
Please correct me if the syntax is w
On Thu, Jan 26, 2012 at 6:02 PM, Godfrey Chung wrote:
> I think the upstream will use it if openct exports this useful internal
> function from the library and the upstream author did not want to reinvent
> the wheel.
Please contact the openct upstream about that.
> acsccid is a fork of ccid but
Dear Paul
Why do you duplicate src/92_pcscd_acsccid.rules as
debian/libacsccid1.udev? I would suggest deleting
debian/libacsccid1.udev and just using the upstream file.
Done. I created a symbolic link to upstream file.
Why? Isn't the existing file installed by the upstream build system?
If
On Thu, Jan 26, 2012 at 3:24 PM, Godfrey Chung wrote:
>> Why do you duplicate src/92_pcscd_acsccid.rules as
>> debian/libacsccid1.udev? I would suggest deleting
>> debian/libacsccid1.udev and just using the upstream file.
>
> Done. I created a symbolic link to upstream file.
Why? Isn't the existi
Dear Paul
Thank you for your review.
I filed #657110 on lintian to check for commented out Vcs-* fields
pointing at collab-maint (which is created by dh_make). Please
consider implementing a patch for it so that others don't make the
same mistake.
Done. I removed the comment.
You might want
Here is a review of your package:
I filed #657110 on lintian to check for commented out Vcs-* fields
pointing at collab-maint (which is created by dh_make). Please
consider implementing a patch for it so that others don't make the
same mistake.
You might want to run wrap-and-sort -s so diffs on d
Dear Kilian,
Thank you for reviewing and uploading my first package "acsccid". Recently, I
have updated the package with new upstream. acsccid 1.0.3 added more ACS CCID
smart card readers support as well as legacy smart card readers such as ACR38
running proprietary protocol (non-CCID). It also
Dear mentors,
I am looking for a sponsor for my package "acsccid". acsccid 1.0.3 added more
ACS CCID smart card readers support as well as legacy smart card readers such
as ACR38 running proprietary protocol (non-CCID). It also improved card
protocol parameters handling so that the optimal baud
13 matches
Mail list logo
