-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 27 Sep 2005 22:22:09 +0200
Source: belpic
Binary: libbelpic0 libeid0 belpic eidviewer libbelpic0-dev libeid0-dev
Architecture: source powerpc
Version: 2.3.13.full-1
Distribution: unstable
Urgency: low
Maintainer: Wouter Verhelst <[EMAIL PROTECTED]>
Changed-By: Wouter Verhelst <[EMAIL PROTECTED]>
Description: 
 belpic     - SmartCard utilities from the OpenSC project, compiled against lib
 eidviewer  - application to read out information from the Belgian electronic I
 libbelpic0 - belgian eID PKCS11 library
 libbelpic0-dev - belgian eID PKCS11 library, development files
 libeid0    - library to read identity information from the Belgian electronic 
 libeid0-dev - library to read identity information from the Belgian electronic 
Changes: 
 belpic (2.3.13.full-1) unstable; urgency=low
 .
   * Found a license in a _different_ .zip on the same upstream download site,
     with a reference to the "Belgian eID runtime" (i.e., _this_ code),
     claiming it covers that code. Added it to the packages' debian/copyright,
     with explanation. The license for the belpic-specific code is
     special-case, but (in my judgement) passes the DFSG. Whee.
   * Since this clarifies the (previously blurry) licensing situation of
     libeid and the eidviewer, build and include those too, now.
   * This makes for a lot of "new" files in the .orig.tar.gz (those that I
     previously excluded, thinking they had no license). Hence, upstream
     version number is now 2.3.13.full rather than 2.3.13. Broken, broken
     katie.
   * It also makes for a few new packages: libeid (maybe to be renamed libbeid
     sometime soon to avoid namespace clashing, but I can't do that just yet;
     at least not without upstream's consent) and its -dev package, plus the
     eidviewer (an application to view the data on the card). Enjoy!
   * Redid some of upstream's build scripts to use automake/autoconf/libtool
     rather than some home-brewn semi-makefiles. They're not Great yet, but
     they should work better than Upstream's build system (which mixes .a files
     with -fPIC binaries in the same .so -- no, that will not work!).
Files: 
 5e4885a508a73dccec5e370a921c56c0 757 - extra belpic_2.3.13.full-1.dsc
 36628dca4aa1981e44738b2c7ea76a31 1074494 - extra belpic_2.3.13.full.orig.tar.gz
 5096b26bdc4881bf44b561f2825ea519 5188536 - extra belpic_2.3.13.full-1.diff.gz
 08735fa7b91da23c1b80cbf3f3053224 285194 libs extra 
libbelpic0_2.3.13.full-1_powerpc.deb
 aaff1d856728fb543d6549ad76b462b4 509896 libdevel extra 
libbelpic0-dev_2.3.13.full-1_powerpc.deb
 4096c697ccf282c9d5b52e377953f432 90674 utils extra 
belpic_2.3.13.full-1_powerpc.deb
 e42156addf5efd516627e59e1d760413 173406 libs extra 
libeid0_2.3.13.full-1_powerpc.deb
 c3a538d35b56e9f72d57b4f0db15628b 242424 libdevel extra 
libeid0-dev_2.3.13.full-1_powerpc.deb
 56e38a30b7b004b300b21051df6dc2fd 168830 utils extra 
eidviewer_2.3.13.full-1_powerpc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDcKPcPfwsYq950p4RAk/lAJwMAR5daIVEjbOMWiX85DQ/fKH33ACgiL8J
EaMyiIoBJfRlKegFJcEYSTA=
=DCA3
-----END PGP SIGNATURE-----


Accepted:
belpic_2.3.13.full-1.diff.gz
  to pool/main/b/belpic/belpic_2.3.13.full-1.diff.gz
belpic_2.3.13.full-1.dsc
  to pool/main/b/belpic/belpic_2.3.13.full-1.dsc
belpic_2.3.13.full-1_powerpc.deb
  to pool/main/b/belpic/belpic_2.3.13.full-1_powerpc.deb
belpic_2.3.13.full.orig.tar.gz
  to pool/main/b/belpic/belpic_2.3.13.full.orig.tar.gz
eidviewer_2.3.13.full-1_powerpc.deb
  to pool/main/b/belpic/eidviewer_2.3.13.full-1_powerpc.deb
libbelpic0-dev_2.3.13.full-1_powerpc.deb
  to pool/main/b/belpic/libbelpic0-dev_2.3.13.full-1_powerpc.deb
libbelpic0_2.3.13.full-1_powerpc.deb
  to pool/main/b/belpic/libbelpic0_2.3.13.full-1_powerpc.deb
libeid0-dev_2.3.13.full-1_powerpc.deb
  to pool/main/b/belpic/libeid0-dev_2.3.13.full-1_powerpc.deb
libeid0_2.3.13.full-1_powerpc.deb
  to pool/main/b/belpic/libeid0_2.3.13.full-1_powerpc.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to