Hello, (Back from family vacation with lots of camping in the sunny (yes!) Baltics…)
The SVN mechanism is really inefficient, it relies on an "svn export" run on every commit on the server side (the repository as you know is huge), nor does the versioning add anything practical (backups should be done with rsync if anything, release publishing integrity should be accomplished with something else..). I'd prefer uploads over SSH. Can you provide a SSH key for a SCP-only "fileserver" upload account? (the same one used for nightly builds) Best, Martin On Aug 6, 2011, at 4:49 PM, Ludovic Rousseau wrote: > Hello, > > I just released a new version of pam-pkcs11. I added the file > pam_pkcs11-0.6.7.tar.gz in the SVN repository at > https://www.opensc-project.org/svnp/files/trunk/pam_pkcs11 > But I can't see the new file on the web site at > http://www.opensc-project.org/files/pam_pkcs11/ > I can see it at https://www.opensc-project.org/svnp/files/trunk/pam_pkcs11/ > > Do I need to do something else? > A configuration on the server must be changed/updated? > Should I use the "new" URL only? > https://www.opensc-project.org/svnp/files/trunk/pam_pkcs11/ > > Thanks, > > -- > Dr. Ludovic Rousseau > _______________________________________________ > opensc-devel mailing list > opensc-devel@lists.opensc-project.org > http://www.opensc-project.org/mailman/listinfo/opensc-devel -- @MartinPaljak.net +3725156495
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
