On 6/7/19 8:25 PM, Emmanuel Lécharny wrote:
> Hi !
> 
> As you have probably figured out, I'm in a ApacheDS bug parad atm. The
> idea is to check all of them (420 !) and more specifically those who are
> associated with 2.0.0.AM26 or lower, and that includes all the issues
> without any fix version (for a grand total of 175 issues) before cutting
> the 2.0.0.AM26 release.
> 
> Don't expect me to be able to get all of them fixed, I'm just trying to
> deal with the low hanging fruits, and there are many duplicates too.

C'mon ;)

> Anyway, there are a few issues that are related with packaging. There
> are 2 categories :
> - a pb in the scripts
> - a pb with the installers.
> 
> For the first set of issues, I think it's manageable. The second set of
> issue is more complex. We have 2 things to deal with :
> 
> 1) Windows 64 bit packages. The installer we use only support 32 bits,
> and we have to find a way to support 64 bits versions of the installer.
> 
> 2) Mac OSX: the PackageMaker utility is no longer existing. We have to
> find another mechanism. And there is the pb of having a signed package

And for Linux, as most distributions switched to systemd, this should
also be supported. But not too urgent as sysv init scripts are still
supported.

> I know that Studio is using a script to generate a DMG, and Stefan has
> requested and obtained a signing key for packages.
> 
> This is something I need to get too, but any direction would help me a
> lot (I have quite a limited time to deal with all those things...)

My journey is described here:
https://issues.apache.org/jira/browse/INFRA-16978

The agreements are here:
https://svn.apache.org/repos/private/committers/apple-app-store-code-signing

But now Apple also requires notarization on top...

> Any help is very welcome !
> 
> PS: I'll try to gather a list of packaging related issues and post it on
> this mailing list later on.
> 
> Thanks !


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to