On Tue, 24 Jan 2012 16:10:50 -0500 Konstantin Ryabitsev icon@fedoraproject.org wrote:
Hi, all:
Two developments in the last couple of days:
Firstly, I re-converted the tree from SVN to git again. Back in 2005 I was trying to switch epylog to using kid templates and branched the stable sources into STABLE-1_0 subversion branch. As I didn't complete the template work, that resulted in subversion trunk being very badly broken, to the point of not being useful. It's my fault that I didn't advertise this fact very publicly.
When Seth converted from subversion to git, he didn't import the STABLE-1_0 branch, so the git tree didn't have the actually working code any more. :) Thankfully, he still had the subversion tree stashed away, so after some git wrangling I was able to re-convert the project and push it back to the git repository (spamming the world in the process, sorry!).
You can browse the git tree here: http://git.fedorahosted.org/git/?p=epylog.git
So, as things are right now:
1. yay for new releases 1b. yay for me not having to do them!
- Add gpg encryption of email reports. Signing also works, though
there appear to be a few kinks, as evolution pretends that it's not a valid format (thunderbird and mutt have no problem, on the other hand). I will note that gpg-signing is added for completeness and requires personal paranoia level set firmly on 11.
If you want to not have to deal with any of this - don't email the reports at all. Just use the file outputter and mail the url to the report.
Then host the report on an ssl'd webserver protected by whatever authN you'd like.
It is possible someone could modify the report on the webserver but at that point you have a compromised box which would, effectively, defeat signing/encrypting from that same host, too.
-sv