>> Are there any tests that actually use the uid/gid of the current user?
>> Compress will no read them by itself, so the only place things could
>> fail was if we used native tar to create an archive. Is there such a
>> test? If so we could try to adapt the test in question.
On 2021-07-10, Henr
>
> > On a Mac that used LDAP, user ids and groups are 'long':
> > henri.biestro@L-HBIESTRO-1 commons-compress % id
> > uid=1447288081(henri.biestro) gid=1024222515
>
> Didn't know that.
>
Neither did I!
>
> Are there any tests that actually use the uid/gid of the current user?
> Compress
On 2021-07-10, Henri Biestro wrote:
> Side note whilst trying to validate RC1:
> On a Mac that used LDAP, user ids and groups are 'long':
> henri.biestro@L-HBIESTRO-1 commons-compress % id
> uid=1447288081(henri.biestro) gid=1024222515
Didn't know that.
> A lot of tar tests will fail in this (p
FWIW, I set the date in changes.xml so that it goes with the RC git tag
which then becomes the release tag. If the RC fails, then I update the
date, so we have a clear record, YMMV.
Gary
On Sat, Jul 10, 2021, 06:12 Stefan Bodewig wrote:
> On 2021-07-10, Bruno P. Kinoshita wrote:
>
> > The RELEA
On 2021-07-10, Bruno P. Kinoshita wrote:
> The RELEASE-NOTES.txt for 1.21 starts with "Compress 1.20 now at least
> requires Java 8 to build and run." which is a bit confusing, but not a
> major issue. (Maybe it would be better to say "Compress 1.20 and later
> require Java 8..."?)
It is going to
