Your message dated Wed, 23 Feb 2022 00:52:27 +0530
with message-id <YhU382q7AqPoXGw6@debian>
and subject line Re: aerc: please update Homepage (and probably 
debian/copyright URIs as well)
has caused the Debian Bug report #1003773,
regarding aerc: please update Homepage (and probably debian/copyright URIs as 
well)
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 [email protected]
immediately.)


-- 
1003773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003773
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aerc
Version: 0.7.1-1
Severity: normal

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

Homepage is listed as https://aerc-mail.org which points to
https://git.sr.ht/~sircmpwn/aerc for its source and currently lists
0.5.2 as its latest release.

But the Debian package mysteriously has 0.7.0 as latest release - how?

Seems the package tracks a fork of aerc at
https://git.sr.ht/~rjarry/aerc - please reflect that in the various
packaging metadata (I only checked and got mislead by the Homepage URI -
don't know if other hints like those in debian/copyright are similarly
misleading).

Kind regards, and thanks for maintaining this wonderful piece of code,

 - Jonas

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHi9kcACgkQLHwxRsGg
ASECFw/9HCSWSLGn5rzqlm27w4XPn870F6M8KsCHaUPY78AVljDmapVagXRXaoxD
q4k5Nq7uTgIi+089VcDnUdqgWNuF0a6PjitqjUDxPEzmYpYI3fUZRHGazqqThHxV
hkCXvVh4gPrk4+GeQZ3knXfK5Ns8lAGiHEUqYya7RJOIR7lZ+59CFoi74qRYmuiS
SiDcuu6La73YIz1vjIWXi8YqW8+pfvr9dJDPcFjeceHAXzWrez8zAuKJvntofQgc
Sz25yPOxfEUtCmNLvR6DvX+Yqvm0C5E76//sOwRgaRELZbKlyV6yuTn+HnO88/sy
Qn8KE37q4e9+uHy3LdJH0+HzNNy32j+bc7MZJoFPVUhRXwgEelKlrwD7iLfFDYgs
uBG09mA54rn9KLllGBDXscg/sTzPi5YsAWsUAW8hYA3TfwRJsaTrBfNauk+OROWT
c7Qw4dxZi+Oi/KRgFOnni73A2D7z6Gejudmx4ofkoXVAQ+eQZGhVr3/SuWoEzyGM
kTUiM0lW6X3DIRpn1B6LSB30JUOAKn21PQuonQu8gMrEeUheWkaNEDCQ4nACdnmR
Mag0CwuaLKt+eRRb4vsAO9y8KDL3ChBxnxzqjHCQWJH35RRCi5jAH3gvjJj6PHpN
49mQZn/XwMJDgtV1lWUKq7BrM0I5rPpMHuCj6ucB3+rBVcmw0Pk=
=CtPG
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
On Mon, 21 Feb 2022 23:02:36 +0530 Nilesh Patra <[email protected]> wrote:
> On Sat, 15 Jan 2022 17:28:59 +0100 Jonas Smedegaard <[email protected]> wrote:
> > Homepage is listed as https://aerc-mail.org which points to
> > https://git.sr.ht/~sircmpwn/aerc for its source and currently lists
> > 0.5.2 as its latest release.
> 
> That link points to the correct source code URL link i.e. 
> https://git.sr.ht/~rjarry/aerc
> Maybe this was updated there after you filed this bug report.
> 
> But in any case, this bug report is no longer valid. If you agree,
> please close this.

Jonas, since this is clearly a non-bug, I am closing it. Feel free to re-open 
and inform
me about it if something is off

Regards,
Nilesh

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to