Re: [Enigmail] jsunit updates and distribution

Patrick Brunschwig <[email protected]> Tue, 17 Sep 2019 17:17:26 +0200
Newsgroups	gmane.comp.mozilla.enigmail.general
Message-ID	<[email protected]>
Daniel Kahn Gillmor wrote on 17.09.2019 15:58:
> Hi Patrick, and other enigmail folks--
> 
> I'm trying to sort out enigmail 2.1 for debian with tbird 68.
> 
> i note that to properly test the new enigmail, i need a newer version of
> jsunit for the testing, so i'd like to ship that in debian too.  at
> https://www.enigmail.net/jsunit/ i see that jsunit 0.2.2 is available.
> 
> i notice a few things that seem amiss with jsunit distribution.  I've
> ordered them from highest priority to lowest priority as i see it -- but
> if you can fix any of them, that would be great:
> 
>  * The git repo at https://git.code.sf.net/u/pbrunschwig/jsunit/source
>    has no tags for anything after jsunit-0.2.0, even though
>    https://www.enigmail.net/jsunit/ lists 0.2.1 and 0.2.2.

0.2.1 can safely be ignored. It was required for some beta version of
TB, but changes in TB 68 forced me to create 0.2.2. I deleted 0.2.1 from
the downloads as it's plain useless.

>  * The git tags that i do see don't appear to be signed.  Please sign
>    any new tags you create!

I created (and pushed) a signed 0.2.2 tag :-)

>  * The git repo at https://git.code.sf.net/u/pbrunschwig/jsunit/source
>    has an erroneous tag jsunit-1.1.2 -- maybe you want to clean that up
>    with something like (untested, i know this syntax works with
>    branches, but i don't know about tags):
> 
>        git push origin :jsunit-1.1.2

That's a wrong tag indeed - I deleted it

>  * The "file not found" situation below https://www.enigmail.net/jsunit/
>    is weird.  Rather than giving a 404 return code, a request for a
>    missing URL gives a series of HTTP redirections which culminate in an
>    HTTP 200 at https://www.enigmail.net/index.php/en/error-404 (that
>    page *says* "Error 404 - Page not Found" in the text, but it's
>    actually an HTTP 200 OK response!).
> 
>    This confuses debian's automatic upstream retrieval scripts ("uscan")
>    when they hunt around for trial signatures.  In particular, uscan
>    tests the URL at https://www.enigmail.net/jsunit/jsunit-0.2.2.xpi.asc
>    and then thinks that maybe a signature is available, because it
>    follows the chain of redirects.

Yes, I created a jsunit-0.2.2.xpi.asc file

>    The easiest way to avoid confusing uscan in the short term is just to
>    ship .asc OpenPGP signatures alongside the .xpi bundles.  but fixing
>    the overall 404 handler would probably be a good thing at some point
>    too.

Yes, I'll have to convince Joomla to do the correct thing...

-Patrick

_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
signature.asc (application/pgp-signature, 833 B)