Re: Embracing github.com

Excellent plan.  Done!

I've also created a PGP code signing key (not signed by anyone else,
but, better than nothing), pushed it to the key servers, and signed the
tarballs.

It's nice to learn from the experience of others.  Thanks!

Bryan

On Fri, Mar 23, 2018 at 08:51:49AM +0000, Stuart Henderson via users wrote:
> 
> I have a request (I maintain the conserver port on OpenBSD).
> 
> Would it be possible to add uploaded tarballs as "assets" to the github
> releases please?
> 
> The automatic "source code (tar.gz)" links on the releases page are to
> files which are automatically generated by git-archive and then cached
> for an unknown time. As confirmed by a github developer in private mail
> they're subject to change if they update their software stack, so aren't
> ideal for OS packagers who verify that downloaded files haven't changed.
> 
> In the past github tried to keep these a bit more stable (including
> locally backing out changes to software they use affecting the files)
> but they seem to have stopped this now, we've been seeing checksum
> failures quite often recently in files distributed this way (even with
> files downloaded at the same time, but presumably from different github
> clusters).
> 
> The manual method is on https://help.github.com/articles/creating-releases/
> (note step 7), it can be automated too - various examples of this are at
> https://gist.github.com/stefanbuck/ce788fee19ab6eb0b4447a85fc99f447 and
> https://stackoverflow.com/questions/40733692/github-upload-release-assets-with-bash
> 
> To show how it looks, here are a few other projects doing this:
> 
> https://github.com/libevent/libevent/releases
> https://github.com/jedisct1/libsodium/releases
> https://github.com/irssi/irssi/releases
> 
> Thanks
> Stuart <sthen@openbsd.org>
> _______________________________________________
> users mailing list
> users@conserver.com
> https://www.conserver.com/mailman/listinfo/users