Your message dated Tue, 02 Aug 2016 11:48:44 +0000
with message-id <e1buybg-0007tm...@franck.debian.org>
and subject line Bug#824928: fixed in letsencrypt.sh 0.2.0-1
has caused the Debian Bug report #824928,
regarding letsencrypt.sh: move the default position of the domains file to 
/etc/letsencrypt.sh/
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
824928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: letsencrypt.sh
Version: 0.1.0-2
Severity: wishlist

As I wrote in #822493#45:

> +Providing a list of domains to letsencrypt.sh
> +=============================================
> +If the parameter --domains is not given to letsencrypt.sh, it tries to
> get
> +a list of domains from the file /var/lib/letsencrypt.sh/domains.txt.
> 
> I've never noticed this (as I use -d in my own script), but imho we
> should put that file by default in /etc/letsencrypt.sh/domains.txt.
> Really /var should not be the place for things like this, whilst is
> totally fine for files like certs.
> What do you think?
> 
> IMHO the best way to accomplish this is to introduce a new conf entry
> pointing just to the domains file, and defaulting to
> "${BASEDIR}/domains.txt.  Just looking at the code and without trying
> seems like ${DOMAINS_TXT} does that; if that's the case it just need
> documenting in the example file.  This should be done upstream, of
> course, and I couldn't figure why he wouldn't like it.


Daniel: what are your thoughts on this?

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: letsencrypt.sh
Source-Version: 0.2.0-1

We believe that the bug you reported is fixed in the latest version of
letsencrypt.sh, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 824...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mattia Rizzolo <mat...@debian.org> (supplier of updated letsencrypt.sh package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 02 Aug 2016 11:16:55 +0000
Source: letsencrypt.sh
Binary: letsencrypt.sh letsencrypt.sh-apache2
Architecture: source
Version: 0.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Let's Encrypt <letsencrypt-devel@lists.alioth.debian.org>
Changed-By: Mattia Rizzolo <mat...@debian.org>
Description:
 letsencrypt.sh - ACME client implemented in Bash
 letsencrypt.sh-apache2 - letsencrypt.sh challenge response support for Apache2
Closes: 824928
Changes:
 letsencrypt.sh (0.2.0-1) unstable; urgency=medium
 .
   [ Mattia Rizzolo ]
   * Import new upstream release 0.2.0.
   * Install the new docs from upstream.
   * deiban/patches:
     + drop compatibility-with-pretty-json-fixes-202.patch: applied upstream
     + backport from upstream 
Make-location-of-domains.txt-configurable-204.patch
   * d/rules: drop unneeded override_dh_installchangelogs.
   * d/NEWS: document the PRIVATE_KEY → ACCOUNT_KEY rename.
 .
   [ Daniel Beyer ]
   * Change default location of domains file to /etc/letsencrypt.sh/domains.txt.
     Closes: #824928
   * Provide maintainer scripts in order to support 0.1.x configurations (in
     particular, old DOMAINS_TXT location, and old PRIVATE_KEY.
   * d/NEWS: document the DOMAINS_TXT location change.
Checksums-Sha1:
 84a737b87910492c2d06058b43f56a415766f054 2109 letsencrypt.sh_0.2.0-1.dsc
 b3aaee65c45a6f204fee7a17952fe98f58df9b5a 19314 letsencrypt.sh_0.2.0.orig.tar.gz
 345f0596e7bcb5f8803530ee70f7314cdec783da 7892 
letsencrypt.sh_0.2.0-1.debian.tar.xz
Checksums-Sha256:
 45ab53aafbda09abe28b628a53cf0b2bddbd323454033b7a2b536298284bfc82 2109 
letsencrypt.sh_0.2.0-1.dsc
 d6e25bbbfa14b87dea4999ecddfd441bbcdc1fd8b3160fa4c4a8ed412ee664e1 19314 
letsencrypt.sh_0.2.0.orig.tar.gz
 b8122a70f80f05db4a352e94e59e077a1d18abe3b856eaf9fcbf1637d41493ea 7892 
letsencrypt.sh_0.2.0-1.debian.tar.xz
Files:
 8b6e855285fd6203ca490e7b8888a7e0 2109 misc optional letsencrypt.sh_0.2.0-1.dsc
 74974ab79d6879b92ba353bbf3d1257e 19314 misc optional 
letsencrypt.sh_0.2.0.orig.tar.gz
 9e3b8b53cba94c244227aecd14f49873 7892 misc optional 
letsencrypt.sh_0.2.0-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJXoIXEAAoJEEsEP825REVAsYUP/1n/RiCN0vwZOut5lerDfuyY
P320UtKlwqgF9J5F43xjyuCECMeYLQ4GbVte8a98UJ9JmdxD5tEWz1XBiQWfCk8a
baL1n9m3ikgfc7EkOsSIGEX2rgm1fgbDa0SdYK8X2syJyTRNbz5ax+nS0uj2Z9pu
fVzpScQfCtEV/sP/fk/4bZORpMBBmPwO96q/JgBUga6+M8T9r7/o4xJT6FzQxb4V
2qJy2qv4ObDz/HvE6hx0RUVyYIj/yuoaOwRXZa4e7tNTzUPVMW1BRZsrmp5dWNKl
b02ZZ+UZmCCdHmSCOnzkRG2LnnjU1w4JK8lN1DPsOk2oTXBotNmzqSjdeQQrp2Wa
dqUAqBWFMrHC8rFgbu/KBOm2S5JMxjTEybpaCju9LZqi2W6LQIF12l0uSoY8zu/U
Mjhi6AQkljDdYxQ6WEi6ZTCI1sqWUyASjySKBylmLJB0wthDedNX+xeXngsXw1OB
PHNEW3Z1Na0Wq7WRQgJ7xfItTNSilwZoEiXxStYQbpM2w8VoUSpGu+5KDJfuqL/o
CDlQyrJRt1mTBnVszwb7HlEMRTtKK+pE8ea2z9wgpnV0tWbOedqfJvXilqOEj/Pv
wEAhrmwBydMHr66W+wLYBmTY4xRUHVUdFJcIIx9NpjVXMIEsTASRD0ekUxCRvOkE
mtD6hXKhl7oTaEzpEbmv
=AlHd
-----END PGP SIGNATURE-----

--- End Message ---
_______________________________________________
Letsencrypt-devel mailing list
Letsencrypt-devel@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel

Reply via email to