Package Details: certbot-git 2.8.0.r6.g926d0c7e0-1

Git Clone URL: https://aur.archlinux.org/certbot-git.git (read-only, click to copy)
Package Base: certbot-git
Description: Tool to automatically receive and install X.509 certificates to enable TLS on servers
Upstream URL: https://certbot.eff.org/
Keywords: ACME letsencrypt protocol python2
Licenses: Apache
Conflicts: certbot, letsencrypt
Provides: certbot, letsencrypt
Replaces: letsencrypt-git
Submitter: edh
Maintainer: edh
Last Packager: edh
Votes: 26
Popularity: 0.000000
First Submitted: 2016-04-18 15:47 (UTC)
Last Updated: 2024-01-07 23:47 (UTC)

Required by (41)

Sources (1)

Latest Comments

1 2 3 Next › Last »

edh commented on 2021-02-23 21:14 (UTC)

@lindsm Thanks for the heads-up! I updated the package according to the new setup.py's in the repository. Plus, I added a couple of entries to my watch-list so that I will hopefully be able to respond quicker next time when upstream introduces these kinds of changes.

P.S. the package was actually missing another dependency as well and quite a few of the previous dependencies could be dropped. Overall your analysis though is correct.

lindsm commented on 2021-02-23 20:15 (UTC) (edited on 2021-02-23 20:18 (UTC) by lindsm)

There hasn't been any comments on this in a while, so not sure if this is package is still active. But I wanted to share my install experiences with this recently. If there is a more appropriate place, or I need to provide more info, by all means, let me know.

I'm using Garuda linux, output of lsb_release -a;

Distributor ID: Garuda
Description:    Garuda Linux
Release:    Soaring
Codename:   n/a

Error Message when running certbot --help;

  File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
    module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 790, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/usr/lib/python3.9/site-packages/certbot/main.py", line 2, in <module>
    from certbot._internal import main as internal_main
  File "/usr/lib/python3.9/site-packages/certbot/_internal/main.py", line 10, in <module>
    import josepy as jose
ModuleNotFoundError: No module named 'josepy'

Using pyenv, but defaulted to system python. Output of python --version && which python;

Python 3.9.1
/home/username/.pyenv/shims/python

Installing josepy fixed it, cmd performed pip3 install josepy;

certbot --version
certbot 1.13.0.dev0

And just because I'm new to arch linux and linux as a desktop in general, here is the version I installed;

aur/certbot-git 1.0.0.r23.gceea41c1e-1 (+26 0.00) (Installed: 1.12.0.r19.g0f3f07b5c-1)
    A tool to automatically receive and install X.509 certificates to enable TLS on servers. The client will interoperate with the Let’s Encrypt CA which will be issuing browser-trusted certificates for free.

I wanted to make an issue or a MR, but not sure how to do either. Please let me know if there is some place I could do such a thing. Not really knowing anything about package building for arch, I assume I could just edit PKGBUILD and add josepy to this block, like so;

depends=('ca-certificates' 'python-acme-git' 'python-configargparse' 'python-configobj'
        'python-cryptography' 'python-pyopenssl' 'python-mock' 'python-parsedatetime'
        'python-psutil' 'python-pyrfc3339' 'python-pythondialog' 'python-pytz'
        'python-requests' 'python-setuptools' 'python-six' 'python-zope-component'
        'python-zope-interface' 'python-josepe')

Hopefully all my markdown works :D

edh commented on 2017-06-09 18:11 (UTC)

@yan12125 Thanks for the hint. I guess there is no good reason to stick to python2. I updated the packages accordingly.

yan12125 commented on 2017-06-09 06:40 (UTC)

The official package has moved from Python 2 to Python 3. [1] How about doing the same for this package? [1] https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/certbot&id=084909ebf576b7a6f2828820639bc40fe2bfe46e

edh commented on 2017-05-08 18:51 (UTC)

@fordprefect Thanks for the hint, done.

fordprefect commented on 2017-05-07 21:45 (UTC)

please change upstream url from letsencrypt.org to certbot.eff.org developement and maintenance has shifted to the eff.

edh commented on 2016-04-18 18:44 (UTC) (edited on 2016-04-21 20:27 (UTC) by edh)

Please switch to the certbot-git package [1]! Let’s Encrypt is in the transition of being renamed to (probably) certbot. Although until now (2016-04-18) there is no new version available with this name, it is still already being used at the master branch of the git project [2]. The change was announced a couple of weeks ago at their blog [3] unfortunately the sudden rename at github is not mentioned there. Since this package fetches the last revision from github it is already affected by this name change. The new package [1] is a complete redesign and should be much more lightweight. Furthermore I have splitted the package into several small one, to give you more control over which plugins or helpers you actually want to use. As always you can track any progress at my github repo [4]. [1] https://aur.archlinux.org/packages/certbot-git/ [2] https://github.com/letsencrypt/letsencrypt [3] https://letsencrypt.org/2016/03/09/le-client-new-home.html [4] https://github.com/Edenhofer/abs

edh commented on 2015-12-16 18:24 (UTC) (edited on 2015-12-16 18:25 (UTC) by edh)

@gabx I am still pretty cautious about adding a service and timer file for this program since it is not contained in the github repo itself and would therefore require a patch for a package which is just working fine. The developers are already aware of this issue [0] and currently there is no real need for it because the certificates are valid for 3 months. I believe that this should be added upstream I am currently against fixing it down the line since I assume it to be implemented within the validity of your first certificate. [0] https://github.com/letsencrypt/letsencrypt/issues/880

gabx commented on 2015-12-16 18:02 (UTC)

FYI, it is possible to create a service + timer file to renew automatically the certificates using webroot.

1 2 3 Next › Last »