[Bug 1287193] Review Request: letsencrypt - A free, automated certificate authority

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=1287193



--- Comment #7 from James Hogarth <james.hogarth@xxxxxxxxx> ---
(In reply to Till Maas from comment #3)
> (In reply to James Hogarth from comment #2)
> > Following from the discussion in the other bug wouldn't this be better named
> > python-letsencrypt to follow the general python naming guidelines?
> 
> AFAIK the python-* naming is meant for modules not tools. For example dnf is
> also packaged in dnf but it also builds a sub-package with only the python
> modules in it. This would be an option if letsencrypt supports both python3
> and python2, then there could be a python2 subpackage with only the python2
> module files for letsencrypt.
> 
> Btw. as far as I understood there were also plans to make letsencrypt
> available on EPEL but the spec does not yet support EPEL. Do you not want to
> maintain letsencrypt on EPEL?

To simplify this somewhat and cut down effort and time to get it into Fedora as
the primary concern the plan is to get this reviewed for rawhide and tested in
there.

Once we are happy with it working properly there (to clarify standalone, manual
and webroot will be supported initially as I've had reports of the apache
plugin not playing nicely with Fedora as it was written with Debian in mind and
would like to take a better look at that in due course) Nick and I will work
together on a separated spec to avoid messing this up with conditionals and
will file bugs as required to get the dependencies in EPEL7 (and after that EL6
if it's feasible).

As it stands right now the SRPM cannot be built for EPEL7 (or even f23) due to
various dependencies either outright missing or needing an update.

I've split the spec up to letsencrypt and python2-letsencrypt with the docs and
%{_bindir} files in the former and the libraries in the latter with the idea of
starting it separated this way to make a clean transition to
python3-letsencrypt when upstream support that in due course.

That new spec will be uploaded a little later on today when I've had a chance
to test a bit more.

I've requested the rawhide git for python-acme so give it 24 hours or so and we
should have that in rawhide and fedora-review against this will be possible.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review




[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]