Request advice on a package for Aladdin eToken (TM) support
Hi, I've made a package for supporting the Aladdin eToken PRO smartcard. There is some info hero [1]. The deb I've prepared is only free software, basically a bundle of tools like openssl, opensc etc. However, without the proprietary drivers from Aladdin it is not much use. So that would make it a candidate for contrib, if I understand the rules correctly. The software is very specific for this particular device, so it is not general-purpose. I've tested it on Debian 4, Ubuntu 6.06 and 7.04. I would like some advice on how to proceed; is there a chance that the package will ever be accepted into Debian? Are there terrible mistakes I've made in the packaging? For those interested the package is temporarily found on my web pages[2]. 1. http://www.nikhef.nl/pub/projects/grid/gridwiki/index.php/Using_an_Aladdin_eToken_PRO_to_store_grid_certificates 2. http://www.nikhef.nl/~dennisvd/etoken/ Regards, Dennis van Dok -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.vl-e.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Request advice on a package for Aladdin eToken (TM) support
Andreas Barth schreef: * Dennis van Dok ([EMAIL PROTECTED]) [070609 01:40]: I've made a package for supporting the Aladdin eToken PRO smartcard. I think it is a very good idea to make a package to make using this device easier, but: I doubt it is a good idea to just bundle all of the different source packages together. For example, we have opensc 0.11.2 already in Debian. Of course, it might end up that there is one package where you need a very specific version, but in the general case, "Depends" should be enough. (And, BTW, once this is done I'm interessted in sponsoring it.) I agree completely, but there is a catch. We had some trouble getting the stuff to work at all; it turned out to boil down to this exact mix of versions. But that is not the only thing. - An openssl patch to create short-lived grid proxies allows a HH:MM specification for the validity. - An engine_pkcs11 patch allows PINs longer than 12 characters - A Debian specific patch for libltdl seems to cause an error with pkcs11-tool. I didn't install the full packages, just the minimal set of files needed. And everything in /opt/etoken-pro as the package is not currently in Debian. I would be willing to give it a try, I mean repackaging with just the Depends: on the needed packages. The openssl patch I'll keep, though. I'm not sure where to start. Should I set up a chroot and debootstrap Debian unstable, to see if something works with the packages already there? Regards, Dennis -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.vl-e.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Request advice on a package for Aladdin eToken (TM) support
Bernd Zeimetz wrote: Hi, - An openssl patch to create short-lived grid proxies allows a HH:MM specification for the validity. - An engine_pkcs11 patch allows PINs longer than 12 characters does the openssl upstream know about these patches? Yes, the openssl patch was offered upstream; the engine_pkcs11 patch I'll look into. Dennis van Dok -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.vl-e.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: etoken-pro-support
Dear mentors, I am looking for a sponsor for my package "etoken-pro-support". * Package name: etoken-pro-support Version : 0.0.1 Upstream Author : me/myself/I (this is a Debian native package) * URL : * License : LGPL Section : contrib/utils It builds these binary packages: etoken-pro-support - Aladdin eToken PRO support package The package is lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/contrib/e/etoken-pro-support - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/contrib/e/etoken-pro-support/etoken-pro-support_0.0.1.dsc This software helps with getting the Aladdin eToken PRO to work as a PKCS#11 device; you need the proprietary drivers from Aladdin in addition to this package. If you don't have an eToken PRO this sofware is not much use. See http://www.nikhef.nl/pub/projects/grid/gridwiki/index.php/Using_an_Aladdin_eToken_PRO_to_store_grid_certificates I would be glad if someone uploaded this package for me. Kind regards Dennis van Dok -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.vl-e.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: etoken-pro-support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Barth wrote: > * Dennis van Dok ([EMAIL PROTECTED]) [070613 00:51]: >> The package can be found on mentors.debian.net: >> - URL: http://mentors.debian.net/debian/pool/contrib/e/etoken-pro-support >> - Source repository: deb-src http://mentors.debian.net/debian unstable >> main contrib non-free >> - dget >> http://mentors.debian.net/debian/pool/contrib/e/etoken-pro-support/etoken-pro-support_0.0.1.dsc > > this doesn't look too good: > lrwxrwxrwx 1 aba aba41 Jun 13 09:29 COPYING -> > /home/dennisvd/share/automake-1.9/COPYING > lrwxrwxrwx 1 aba aba41 Jun 13 09:29 INSTALL -> > /home/dennisvd/share/automake-1.9/INSTALL > lrwxrwxrwx 1 aba aba44 Jun 13 09:29 install-sh -> > /home/dennisvd/share/automake-1.9/install-sh > lrwxrwxrwx 1 aba aba41 Jun 13 09:29 missing -> > /home/dennisvd/share/automake-1.9/missing OOPS! I guess lintian is not failsafe either ;-) I will quickly fix this and upload a new version. Dennis - -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.vl-e.nl Phone +31 20 592 50 12 :: Google Agenda on http://www.nikhef.nl/~dennisvd/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFGb+oHIITq5lEwLHcRAnMRAKC8UOJqK2UUx0QHYGZH5RCV1ZEtQACfUWMz a4ROd+vzbfYTEao10w5NB/k= =WDPW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: etoken-pro-support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Barth schreef: > * Andreas Barth ([EMAIL PROTECTED]) [070613 11:27]: >> Otherwise, it looks much better than the initial version - I'll give you >> some more comments this evening (or otherwise soon). > > Some more in-detail comments now: > - mkproxy seems to be a bit too generic name for me - how about > etoken-mkproxy? OK; (good point, considering this is going to be in /usr/bin!) > - why does the source package contain both mkproxy.1 and mkproxy.1.in? A mistake. The former is autogenerated. > - why does restart in etokend not delete /var/tmp/.etokend (but stop > does)? (same comment for etsrvd) Although there appears to be no apparent need (these files are sockets) removing them can't harm. I'll add that. > - please remove the commands in dh_* you don't need. OK. > - I don't see the reason why you use automake (or even have any makefile > at all). You could probably install everything with just using > dh_install (at least debian-specific packages usually could). Yeah, I can see that now. For me it was an exercise to start using automake, but it doesn't really pay off. Nevertheless, I got it working now so I'm not going to mess with it any more. > > Please don't take my comments too bad - the first package is always the > hardest :), and the package now looks to be in good shape for me (and is > considerable better then the earlier version). Thanks! This has been fun, I've been building RPMs for over a year, which is very different. I can now say that I appreciate the approach Debian takes towards packaging. Dennis - -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.vl-e.nl -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGcF4XIITq5lEwLHcRAkE7AKCFN7S3UTIhtiAzwrKmXFbLUXZVfgCgqZgV D31dbzby20WHuSugOKzfg5w= =XNpu -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: not-yet-commons-ssl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Mentors, I am looking for a sponsor for my package "not-yet-commons-ssl". * Package name: not-yet-commons-ssl Version : 0.3.9-1 Upstream Author : Julius Davies * URL : http://juliusdavies.ca/commons-ssl/ * License : Apache 2.0 Section : java It builds those binary packages: libnot-yet-commons-ssl-java - Not-yet-commons-SSL is a library to make SSL and Java easier To access further information about this package, please visit the following URL: http://mentors.debian.net/package/not-yet-commons-ssl Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/not-yet-commons-ssl/not-yet-commons-ssl_0.3.9-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Dennis van Dok - - -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ - -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8gF1QACgkQIITq5lEwLHd9vgCdF5Bi80VWWwTPSiMjI41fhq6b 2VkAnRlQqiqeUIYO5TljhdapO6U0tJ6c =3O7S - -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8gcHQACgkQIITq5lEwLHfDuQCfRVwdiduLa2uC1F8xpVrlWxSS CKMAn0gDBBvMnp2VenDjKKvCq3V3N9kg =6kkT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f20707c.7020...@nikhef.nl
RFS: not-yet-commons-ssl (repeat)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, my previous mail may have gone unnoticed as I made a copy/paste error with the GPG signature. Is there anyone willing to check out this package? This is the first in a bunch of java packages that I'm trying to do. * Package name: not-yet-commons-ssl Version : 0.3.9-1 Upstream Author : Julius Davies * URL : http://juliusdavies.ca/commons-ssl/ * License : Apache 2.0 Section : java It builds those binary packages: libnot-yet-commons-ssl-java - Not-yet-commons-SSL is a library to make SSL and Java easier To access further information about this package, please visit the following URL: http://mentors.debian.net/package/not-yet-commons-ssl Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/not-yet-commons-ssl/not-yet-commons-ssl_0.3.9-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Dennis van Dok - -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8ofCoACgkQIITq5lEwLHcTIACeNgRYOXtxHvRlE4DJxU+wHosi IwwAoJ33lvzIUS547h09EDlBTfEw0yJY =Slsd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f287c30.2070...@nikhef.nl
Bug#664165: RFS: not-yet-commons-ssl/0.3.9-2 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "not-yet-commons-ssl" * Package name: not-yet-commons-ssl Version : 0.3.9-2 Upstream Author : Julius Davies * URL : http://juliusdavies.ca/commons-ssl/ * License : Apache 2 Section : java It builds those binary packages: libnot-yet-commons-ssl-java - Not-yet-commons-SSL is a library to make SSL and Java easier To access further information about this package, please visit the following URL: http://mentors.debian.net/package/not-yet-commons-ssl Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/not-yet-commons-ssl/not-yet-commons-ssl_0.3.9-2.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * extended copyright details after contacting upstream author * removed duplicate cdbs build dependency * updated copyright header * updated to Debian policy 3.9.3 * added version control reference fields Regards, Dennis van Dok -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120315232653.3531.9046.reportbug@localhost6.localdomain6
Bug#664181: RFS: trustmanager/3.0.5-1 [ITP]
Package: sponsorship-requests Severity: wishlist Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "trustmanager" * Package name: trustmanager Version : 3.0.5-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License : [fill in] Section : java It builds those binary packages: libtrustmanager-java - Java TrustManager interface with grid features libtrustmanager-java-doc - Java TrustManager interface with grid features To access further information about this package, please visit the following URL: http://mentors.debian.net/package/trustmanager Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/t/trustmanager/trustmanager_3.0.5-1.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * Initial release. (Closes: #656389) Regards, Dennis van Dok -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120316085620.9304.90425.reportbug@localhost6.localdomain6
Bug#664181: Info received (RFS: trustmanager/3.0.5-1 [ITP])
Sorry for not filling the template properly. Here's the details: * Package name: trustmanager Version : 3.0.5-1 Upstream Author : Joni Hahkala * URL : https://twiki.cern.ch/twiki/bin/view/EGEE/TrustManager * License : Apache 2 Section : java Dennis -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f630100.50...@nikhef.nl
Bug#664165: RFS: not-yet-commons-ssl/0.3.9-2 [ITP]
Op 16-03-12 00:26, I wrote: > > More information about hello can be obtained from http://www.example.com. I overlooked this snippet from the RFS template. You won't find much information there :-). The obvious place to look is of course: http://juliusdavies.ca/commons-ssl/ Cheers, Dennis van Dok -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6303d1.6040...@nikhef.nl
building for more than one distribution
Hi, this may not be the perfect place to ask, but... The pbuilder-tricks wiki[1] describes very nicely how to set up builds for more than one distribution. I've started to use this to build our software stack for squeeze and ubuntu, so our customers don't have to wait for inclusion in Debian proper. 1. http://wiki.debian.org/PbuilderTricks I'm also happily using cowpoke as this streamlines a lot of the work. The snag I'm hitting is that a build for, say, squeeze-i386 results in a changes file that has "Distribution: unstable" in it. And mini-dinstall will oblige and put it in /var/cache/archive/unstable instead of /var/cache/archive/squeeze. Now I can think of several ways to fix this: - use something other than dinstall - change the .changes file before using dput (breaks signing) - use --debbuildopts=--changes-option=-Ddistribution=squeeze Any hint is appreciated! Thanks, Dennis -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f69c002.1070...@nikhef.nl
Re: building for more than one distribution
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 21-03-12 23:13, gregor herrmann schreef: > On Wed, 21 Mar 2012 12:48:18 +0100, Dennis van Dok wrote: > >> Now I can think of several ways to fix this: >> >> - use something other than dinstall - change the .changes file >> before using dput (breaks signing) - use >> --debbuildopts=--changes-option=-Ddistribution=squeeze > > - change the distribution in debian/changelog before building: > "debchange -D $dist " Thanks, but this complicates my procedures. After calling debchange I'm left with a modified tree and svn-buildpackage will complain I have uncommitted changes. Consider that this has to be done for some 5 or 6 distributions (including the Ubuntu ones). I found that reprepro handles things a little better than mini-dinstall; it comes with changestool which can manipulate changes. At the moment I'm favoring passing -Ddistribution= to the build. Cheers, Dennis - -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9qVlYACgkQIITq5lEwLHd+agCeNR0U9xix4Jh64oX4t2cOVlG4 XH8An2muIFeYr6lIOk0mgNy5l7lv4YtR =QfkG -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6a565c.5040...@nikhef.nl
Re: building for more than one distribution
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 22-03-12 00:04, gregor herrmann schreef: > On Wed, 21 Mar 2012 23:29:48 +0100, Dennis van Dok wrote: >> I'm left with a modified tree and svn-buildpackage will complain >> I have uncommitted changes. > > Hm yeah; using --svn-ignore (or putting svn-ignore in > ~/.svn-buildpackage.conf) might work around that. It's a matter of personal taste, but I use --svn-ignore-new only while tinkering until I'm convinced the build works. After that, I try to keep things clean, version-control-wise. Thanks, Dennis - -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9qYbUACgkQIITq5lEwLHd6eACfVsbQdhNIeve2EldR28hEw4fm 2uQAoItcZJlH/AOJk9pXQkyTx7j57L/5 =3AT1 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6a61bc.6010...@nikhef.nl
Re: building for more than one distribution
Op 22-03-12 12:20, Ansgar Burchardt schreef: > sbuild has a "-d" option that I believe also changes the field in the > .changes. It also has options to append a suffix to the version which > you need if you want to keep binary packages built for multiple > distributions in the same archive. Thanks; I wasn't aware of sbuild but I've looked it up now. The docs suggest that it's covering the same functionality as pbuilder, so one would naturally choose one or the other, not both. Or am I wrong? Cheers, Dennis -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6f7e56.7070...@nikhef.nl
Bug#670254: RFS: lcmaps/1.5.5-1 [ITP] -- I'm looking for a sponsor.
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "lcmaps" * Package name: lcmaps Version : 1.5.5-1 Upstream Author : Nikhef Grid Security Middleware Team https://wiki.nikhef.nl/grid/Site_Access_Control * License : Apache 2 Section : libs It builds those binary packages: lcmaps-basic-interface - LCMAPS header files for basic interfaces lcmaps-globus-interface - LCMAPS header files for Globus interfaces lcmaps-openssl-interface - LCMAPS header files for OpenSSL interfaces liblcmaps-dev - LCMAPS development libraries liblcmaps-without-gsi-dev - LCMAPS development libraries (Without GSI) liblcmaps-without-gsi0 - Grid mapping service without GSI liblcmaps0 - Grid (X.509) and VOMS credentials to local account mapping servic To access further information about this package, please visit the following URL: http://mentors.debian.net/package/lcmaps Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/l/lcmaps/lcmaps_1.5.5-1.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: New upstream release. Fixes out-of-source build failure with --disable-gsi-mode. It now builds both with and without GSI mode libraries in one package. Regards, Dennis van Dok -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f96a256.7070...@nikhef.nl
Bug#664165: RFS: not-yet-commons-ssl/0.3.9-2 [ITP]
Op 04-08-12 07:45, Bart Martens schreef: > Hi Dennis, > > The package at mentors is no longer there. What happened ? Are you still > working on not-yet-commons-ssl, and do you still need a sponsor ? Hi Bart, I guess it was autoremoved after 20 weeks of not finding a sponsor. I've uploaded it again; I'm still looking for a sponsor. The packaging of not-yet-commons-ssl is part of a larger work to include a bunch of software that my team at Nikhef is developing as part of the European Grid Infrastructure middleware. Cheers, Dennis -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/501eebc2.9050...@nikhef.nl
Bug#684102: RFS: igtf-policy-bundle/1.46-1 [ITP] Profiles for Authority Root Certificates
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "igtf-policy-bundle" * Package name: igtf-policy-bundle Version : 1.46-1 Upstream Author : David Groep * URL : http://www.igtf.net/ * License : Apache 2 Section : misc It builds those binary packages: igtf-policy-classic - IGTF classic profile for Authority Root Certificates igtf-policy-experimental - IGTF experimental Authority Root Certificates igtf-policy-mics - IGTF MICS profile for Authority Root Certificates igtf-policy-slcs - IGTF SLCS profile for Authority Root Certificates igtf-policy-unaccredited - IGTF unaccredited Authority Root Certificates To access further information about this package, please visit the following URL: http://mentors.debian.net/package/igtf-policy-bundle Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/igtf-policy-bundle/igtf-policy-bundle_1.46-1.dsc More information about The IGTF can be obtained from http://www.igtf.net/ Regards, Dennis van Dok -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120806220128.28634.64652.reportbug@localhost6.localdomain6
RFS: lcmaps
Dear mentors, I am looking for a sponsor for my package "lcmaps". * Package name: lcmaps Version : 1.4.31-1 Upstream Author : MW Security developers at Nikhef * URL : https://www.nikhef.nl/pub/projects/grid/gridwiki/index.php/Site_Access_Control * License : Apache License 2.0 Section : libs It builds those binary packages: lcmaps-basic-interface - LCMAPS header files for plug-in development lcmaps-globus-interface - LCMAPS header files for plug-in development lcmaps-openssl-interface - LCMAPS header files for plug-in development liblcmaps-dev - LCMAPS development libraries liblcmaps0 - Grid (X.509) and VOMS credentials to local account mapping servic To access further information about this package, please visit the following URL: http://mentors.debian.net/package/lcmaps Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/l/lcmaps/lcmaps_1.4.31-1.dsc I would be glad if someone uploaded this package for me, or gave me feedback on the packaging. Kind regards, Dennis van Dok -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6d3805.8090...@nikhef.nl
Re: RFS: lcmaps
Op 12-09-11 15:41, David Bremner schreef: > On Mon, 12 Sep 2011 00:36:53 +0200, Dennis van Dok wrote: >> lcmaps-basic-interface - LCMAPS header files for plug-in development >> lcmaps-globus-interface - LCMAPS header files for plug-in development >> lcmaps-openssl-interface - LCMAPS header files for plug-in development >> liblcmaps-dev - LCMAPS development libraries >> liblcmaps0 - Grid (X.509) and VOMS credentials to local account mapping > > Hi Dennis, > > Thanks for the contribution, but what is it? > > Seriously, you are more likely to attract sponsor interest if you give > at least the package long description in your RFS. Perhaps the short > descriptions could be improved as well. Oops, you're right, this isn't very informative at all. I copied the RFS template and forgot to fill in a full description. The short descriptions have been fixed in the control file so that will be in the next version. LCMAPS is middleware for the Grid; it is a pluggable framework that takes credentials as input (X.509 proxy certificates with VOMS extensions) and outputs the user and group identity to use with the credentials. This allows for multi-domain user authentication and mapping. To use LCMAPS you need at least a client application (such as a Globus Toolkit gridftp daemon) and one or more plugins (packaged separately). For more information see https://www.nikhef.nl/pub/projects/grid/gridwiki/index.php/Site_Access_Control How about that? Is that a reasonable description? Cheers, Dennis -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6e17c5.8060...@nikhef.nl
RFS: lcmaps
Dear mentors, I am looking for a sponsor for my package "lcmaps". * Package name: lcmaps Version : 1.4.31-1 Upstream Author : grid-mw-secur...@nikhef.nl * URL : https://www.nikhef.nl/pub/projects/grid/gridwiki/index.php/Site_Access_Control * License : Apache License 2.0 Section : libs It builds those binary packages: lcmaps-basic-interface - LCMAPS header files for basic interfaces lcmaps-globus-interface - LCMAPS header files for Globus Toolkit interfaces lcmaps-openssl-interface - LCMAPS header files for OpenSSL interfaces liblcmaps-dev - LCMAPS development libraries liblcmaps0 - Grid (X.509) and VOMS credentials to local account mapping service LCMAPS is middleware for the Grid; it is a pluggable framework that takes credentials as input (X.509 proxy certificates with VOMS extensions) and outputs the user and group identity to use with the credentials. This allows for multi-domain user authentication and mapping. To use LCMAPS you need at least a client application (such as a Globus Toolkit gridftp daemon) and one or more plugins (packaged separately). This is my first package; overall the site access control suite consists of some 20 packages. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/lcmaps Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/l/lcmaps/lcmaps_1.4.31-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Dennis van Dok -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e71cbb7.1080...@nikhef.nl
preserving user changes while managing configuration files
Dear mentors,
I have a question regarding configuration file changes.
I've written a utility to manage a fairly complicated configuration
file. The utility is used in the postinst script, and debconf feeds it
the right parameters. The utility can also be used stand-alone by the
administrator.
Of course the administrator can edit the file by hand, and the Debian
policy clearly states that the maintainer scripts should not overwrite
such changes.
The way I've addressed this is by adding a special marker containing a
warning near the top of the configuration file ('warning: this file is
maintained by foo-configure; remove this line when editing.'), and the
utility tests if this line is present before overwriting the file.
My question is whether this method sufficiently implements the policy,
or if there are other ways to go about it.
Thanks,
Dennis
--
D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl
Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4eccac38.6000...@nikhef.nl
Re: preserving user changes while managing configuration files
Op 23-11-11 11:20, Gergely Nagy wrote: > I'd like to propose two other options: [...] > In case a sensible default is not possible, then ship without a config > file, and offer to generate one based on debconf answers if the file > does not exist. This sounds like a reasonable approach. I should probably do this with ucf as Alexander suggested. Many thanks, Dennis -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecccf7a.6000...@nikhef.nl
Re: preserving user changes while managing configuration files
On 23-11-11 10:27, Joseph Gunn wrote: > A popular way of accomplishing the task is to support "configuration > subdirectories" > > It includes all "configuration files" in that directory. If you publish a > name that > you will _never_ use then people can add that one "as they wish". Dear Joseph, I'm not sure I'm getting the gist of your suggestion; do you mean the use of /etc/mypackage/conf.d/ or some such? I'm afraid this would require some heavy patching of the upstream code for reading configuration files. Dennis -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eccd09a.6080...@nikhef.nl
Re: preserving user changes while managing configuration files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23-11-11 14:34, Arno Töll wrote: > please mind the exact wording here. A "configuration file" is not > the same as a "conffile" in Debian. Note, you are not allowed to > modify a conffile at any time. In the context of the maintainer scripts, I take it. ;-) [...] > If you want to modify the configuration of your package at > installation time, you can do so by creating a configuration file > your program expects _at installation time_ in the maintainer > script but it must not be part of the package itself. To preserve > user changes or do a graceful updates of your dynamically created > configuration files, you may then manage your changes through ucf > as Alexander suggested. OK, thanks. Just to be clear, running dpkg-reconfigure *will* rewrite the configuration if the admin never touched the configuration file, is that correct? I'm going to try my hand at using ucf now. Cheers, Dennis - -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7NBhIACgkQIITq5lEwLHcbfACdFpzL8n6s6wl8uBBjvsMmWaZk g+AAniPf6x75oTKvxW5vGQlD2XvusWBc =qTqW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecd061a.6060...@nikhef.nl
Bug#702328: RFS: lcmaps-plugins-jobrep/1.5.2-1 -- job repository plugin for the LCMAPS framework
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "lcmaps-plugins-jobrep" * Package name: lcmaps-plugins-jobrep Version : 1.5.2-1 Upstream Author : MW security developers at Nikhef * URL : https://wiki.nikhef.nl/grid/LCMAPS * License : Apache 2 Section : libs It builds those binary packages: lcmaps-plugins-jobrep - Jobrepository plugin for the LCMAPS authorization framework lcmaps-plugins-jobrep-admin - Jobrepository database setup tools To access further information about this package, please visit the following URL: http://mentors.debian.net/package/lcmaps-plugins-jobrep Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/l/lcmaps-plugins-jobrep/lcmaps-plugins-jobrep_1.5.2-1.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * New upstream release (closes: #701555) This release closes a bug about bashishms in the admin tools. Regards, Dennis van Dok -- D.H. van Dok :: Software Engineer :: www.nikhef.nl/grid :: Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5135c2be.4070...@nikhef.nl
Bug#702329: RFS: igtf-policy-bundle/1.52-1 [ITP] -- The International Grid Trust Federation CA distribution
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "igtf-policy-bundle" * Package name: igtf-policy-bundle Version : 1.52-1 Upstream Author : David Groep * URL : http://dist.eugridpma.info/distribution/igtf/ * License : Apache 2 Section : misc It builds those binary packages: igtf-policy-classic - IGTF classic profile for Authority Root Certificates igtf-policy-experimental - IGTF experimental Authority Root Certificates igtf-policy-mics - IGTF MICS profile for Authority Root Certificates igtf-policy-slcs - IGTF SLCS profile for Authority Root Certificates igtf-policy-unaccredited - IGTF unaccredited Authority Root Certificates To access further information about this package, please visit the following URL: http://mentors.debian.net/package/igtf-policy-bundle Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/igtf-policy-bundle/igtf-policy-bundle_1.52-1.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * New upstream version This package contains a collection of CAs that are not in the ca-certificates package, but which are regularly used in the context of grid computing. The IGTF bundles the forces of three policy management authorities, the EUGridPMA, the TAGPMA and APGridPMA. The packages are bundled according to the profiles defined by the IGTF. I've implemented integration with the ca-certificates packages and admins can choose to whitelist or blacklist certain CAs. Regards, Dennis van Dok -- D.H. van Dok :: Software Engineer :: www.nikhef.nl/grid :: Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5135c574.5090...@nikhef.nl
Bug#702329: template text
I seem to consistently leave template text in these ITPs and RFSs I fill in... Please ignore the 'hello' part. For more information see http://www.igtf.net/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/513650f2.70...@nikhef.nl
Bug#702329: RFS update
Dear mentors, I am once again looking for a sponsor for my package "igtf-policy-bundle" * Package name: igtf-policy-bundle Version : 1.53-1 Upstream Author : David Groep * URL : http://dist.eugridpma.info/distribution/igtf/ * License : Apache 2 Section : misc It builds those binary packages: igtf-policy-classic - IGTF classic profile for Authority Root Certificates igtf-policy-experimental - IGTF experimental Authority Root Certificates igtf-policy-mics - IGTF MICS profile for Authority Root Certificates igtf-policy-slcs - IGTF SLCS profile for Authority Root Certificates igtf-policy-unaccredited - IGTF unaccredited Authority Root Certificates To access further information about this package, please visit the following URL: http://mentors.debian.net/package/igtf-policy-bundle Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/igtf-policy-bundle/igtf-policy-bundle_1.53-1.dsc More information about the igtf CA distribution can be obtained from http://www.igtf.net/ Changes since the last upload: * New upstream version This package contains a collection of CAs that are not in the ca-certificates package, but which are regularly used in the context of grid computing. The IGTF bundles the forces of three policy management authorities, the EUGridPMA, the TAGPMA and APGridPMA. The packages are bundled according to the profiles defined by the IGTF. I've implemented integration with the ca-certificates packages and admins can choose to whitelist or blacklist certain CAs. Regards, Dennis van Dok -- D.H. van Dok :: Software Engineer :: www.nikhef.nl/grid :: Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c2cc8b@nikhef.nl
Re: Delaying an RFS: Close or Leave Open?
On 19-06-13 02:42, Bill Blough wrote: > > I have two ITA packages, both with RFS bugs created. > > Based on the review and comments on one package, I realized that the other > package needs a lot more work before uploading it. So, in hindsight, I > shouldn't have opened an RFS for it yet. > > But since I did, what is the preferred way to handle this? > > Should I close the RFS until I feel the package is ready for review? If > this is the case, when I'm ready to RFS, should I start a new one, or > reopen the closed one? (disclaimer: I'm not a DD.) In my experience, uploads that do not get sponsored are automatically purged after 20 weeks. And the RFS is closed as well. I think entering a comment in the RFS about the status is helpful; you should also close it now and reopen it when you've updated the package. This way the RFS won't show up in the list for people doing sponsoring work. Cheers, Dennis -- D.H. van Dok :: Software Engineer :: www.nikhef.nl/grid :: Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c2cdbe.7010...@nikhef.nl
Bug#702329: RFS update
On 20-06-13 13:04, Ansgar Burchardt wrote: > Hi, > > I don't plan to sponsor this package, but here is one comment: > > On 06/20/2013 11:34, Dennis van Dok wrote: >> igtf-policy-classic - IGTF classic profile for Authority Root Certificates >> igtf-policy-experimental - IGTF experimental Authority Root Certificates >> igtf-policy-mics - IGTF MICS profile for Authority Root Certificates >> igtf-policy-slcs - IGTF SLCS profile for Authority Root Certificates >> igtf-policy-unaccredited - IGTF unaccredited Authority Root Certificates > > Why are these multiple binary packages? I would assume they should just > be installed into different locations. The full collection contains certificates for CAs that are not accredited (yet), so typically you don't want them installed at all. The distinction between classic, MICS (member-integrated) and SLCS (short-lived credentials) is the profile as defined by the IGTF. The admin should be aware of the differences in these policies. Although there is an option to exclude certain CAs from being trusted, the default is to trust all (accredited) CAs that are installed. > A sponsor should check the integrity of the certificates. How could he > do this? I can bring the sponsor in personal contact with David Groep, who is a member of the IGTF and upstream distributor. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c2ebf1.6040...@nikhef.nl
Bug#702329: [UPDATE] RFS: igtf-policy-bundle/1.54-1 [ITP] -- The International Grid Trust Federation CA distribution
Dear mentors, this is to let you know I've updated the igtf-policy-bundle package on mentors.debian.org. I would be very grateful it someone would sponsor this package, or generally give feedback. * Package name: igtf-policy-bundle Version : 1.54-1 Upstream Author : David Groep * URL : http://dist.eugridpma.info/distribution/igtf/ * License : Apache 2 Section : misc It builds those binary packages: igtf-policy-classic - IGTF classic profile for Authority Root Certificates igtf-policy-experimental - IGTF experimental Authority Root Certificates igtf-policy-mics - IGTF MICS profile for Authority Root Certificates igtf-policy-slcs - IGTF SLCS profile for Authority Root Certificates igtf-policy-unaccredited - IGTF unaccredited Authority Root Certificates To access further information about this package, please visit the following URL: http://mentors.debian.net/package/igtf-policy-bundle Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/igtf-policy-bundle/igtf-policy-bundle_1.54-1.dsc More information about the IGTF distribution can be obtained from http://www.igtf.net/ Changes since the last upload: * New upstream release: - Extended life time of Grid-KA CA (dd4b34ea) (DE) - Added new CERN hierarchy for CERN IT/IS CA (SHA2 migration) (CH) - Updated metadata for GridGermany DFN-CERT CAs (DE) - Updated contact metadata for KEK (JP) - Updated contact metadata for HKU (HK) - Updated contact metadata for AIST (JP) Regards, Dennis van Dok -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51caca11.3080...@nikhef.nl
Bug#702329: Updated RFS
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "igtf-policy-bundle" * Package name: igtf-policy-bundle Version : 1.55-1 Upstream Author : David Groep * URL : http://dist.eugridpma.info/distribution/igtf/ * License : Apache 2 Section : misc It builds those binary packages: igtf-policy-classic - IGTF classic profile for Authority Root Certificates igtf-policy-experimental - IGTF experimental Authority Root Certificates igtf-policy-mics - IGTF MICS profile for Authority Root Certificates igtf-policy-slcs - IGTF SLCS profile for Authority Root Certificates igtf-policy-unaccredited - IGTF unaccredited Authority Root Certificates To access further information about this package, please visit the following URL: http://mentors.debian.net/package/igtf-policy-bundle Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/igtf-policy-bundle/igtf-policy-bundle_1.55-1.dsc More information about hello can be obtained from http://www.igtf.net/. Changes since the last upload: * New upstream release: - New root certificate with extended life time for NorduGrid CA 1f0e8352 (DK) - Updated contact metadata for all RENATER Grid-FR related CAs (FR) - Updated CRL URL and metadata for IHEP 2013 CA 39d30eba (CN) - New root certificates for NCSA CA re-key: MyProxy CA 2013 c36f6349/7aa2b7bd and Two Factor CA 2013 ca157cee/48c8f10a (US) - New root certificate for EGI catch-all CA "SEEGRID-CA-2013" 772dbd1c (GR) - Removed AIST Grid CA (JP) - Discontinued IUCC CA (6fee79b0) following migration to TCS (IL) - Suspended JUnet-CA (b3222f9e) (JO) - Removed expired unaccredited CAs (misc) - Added unaccredited worthless NL e-Infra Zero tutorial CA 338a3561 (NL) Regards, Dennis van Dok -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52a04333.1010...@nikhef.nl
how do I upload a package where the last changelog entry is by a co-maintainer?
Hi, my colleague has updated some of the packages for which I am the maintainer, and he is an uploader. The last changelog entry is by him. When I tried to upload to mentors, the package was refused and my colleague got e-mail from mentors stating that the (his) e-mail address was not found. Indeed he does not have a mentors account. I re-signed the changes file with my key and re-uploaded, but the result was the same. Does mentors only consider the name in the last changelog entry to see whose package it is? If he signs up for an account, will the package show up in my list of packages or his? Thanks, Dennis van Dok -- D.H. van Dok :: System administrator :: www.nikhef.nl/grid :: Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52dd0ba2.7020...@nikhef.nl
Re: how do I upload a package where the last changelog entry is by a co-maintainer?
On 20-01-14 13:20, Kumar Appaiah wrote: > Try using dch -r. That should update the timestamp, and put your name > there. OK; I've hit another snag. As the packages were already uploaded, my fixed upload shows up under the same package as a separate version. The first 'uploader' is still the owner of the packages, though. So now I've asked him to delete all the packages. I'll upload them anew with a fixed changelog signature. Thanks, Dennis -- D.H. van Dok :: System administrator :: www.nikhef.nl/grid :: Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52dd3977.60...@nikhef.nl
Bug#997021: RFS: igtf-policy-bundle/1.113-1~bpo11+1 -- IGTF experimental Certificate Authorities
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "igtf-policy-bundle". The package is already in stable and buster-backerports. It is NEW for bullseye backports and I would like to maintain updating it there. The package has regular (~monthly) updates of the trust anchors which is why it makes sense to also keep backporting it. * Package name: igtf-policy-bundle Version : 1.113-1~bpo11+1 Upstream Author : IGTF * URL : http://www.igtf.net/ * License : CC-BY-3.0, MPL-1.1 * Vcs : https://github.com/dvandok/igtf-policy-bundle Section : misc It builds those binary packages: igtf-policy-classic - IGTF classic profile for Certificate Authorities igtf-policy-mics - IGTF MICS profile for Certificate Authorities igtf-policy-slcs - IGTF SLCS profile for Certificate Authorities igtf-policy-iota - IGTF IOTA profile for Certificate Authorities igtf-policy-unaccredited - IGTF unaccredited Certificate Authorities igtf-policy-experimental - IGTF experimental Certificate Authorities To access further information about this package, please visit the following URL: https://mentors.debian.net/package/igtf-policy-bundle/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/i/igtf-policy-bundle/igtf-policy-bundle_1.113-1~bpo11+1.dsc Changes since the last upload: igtf-policy-bundle (1.113-1~bpo11+1) bullseye-backports; urgency=medium . * Rebuild for bullseye-backports. . igtf-policy-bundle (1.113-1) unstable; urgency=medium . * New upstream release: * [Changes from 1.112 to 1.113 (4 October 2021)] * Suspended MD-GRID CA due to network resolution issues (MD) * [Changes from 1.111 to 1.112 (16 August 2021)] * Updated ANSPGrid CA with extended validity date (BR) * [Changes from 1.110 to 1.111 (24 May 2021)] * Removed discontinued NERSC-SLCS CA (US) * Removed discontinued MYIFAM CA (MY) * [Changes from 1.109 to 1.110 (22 March 2021)] * Removed INFN-CA-2015 that has disappeared operationally (IT) Regards, -- Dennis van Dok
