Your message dated Fri, 23 Aug 2019 12:07:24 -0400
with message-id <[email protected]>
and subject line Bug#931806: fixed in xca 2.1.2-1
has caused the Debian Bug report #931806,
regarding ITS: xca
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.)
--
931806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931806
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: xca
Severity: important
X-Debbugs-CC: [email protected]
The xca source package has not been updated in some time, and more
recent bugs have NOT received a reply from the maintainer on the BTS nor
any activity on the maintainer's behalf. This is evidenced by the
following items to be used as justification:
---
=== BUG HANDLING ===
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863412 - as stated in
here, RFC 5280 is not precise about UTF8 or PRINTABLESTRING and
therefore the statement of "sorry for the noise" by the bug submitter
suggests that this is no longer an issue - this should've been closed by
maintainer, back in 2017.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928678 - my bug from
May indicating two additional packages needing added to enable Remote DB
support has received no reply from the Maintainer, though via direct
email they indicated "I will reply to your bug" and never did.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927233 - also my bug
but back in April, regardless of Debian being in freeze, the maintainer
never acknowledged this bug. Nor has there been any movement on the
package since November of 2018 generally.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896891 from April 2018
received no responses or acknowledgement from the Maintainer. It also
contains a patch which was never acted on to fix a
cross-build-from-source problem which resulted in an FTBFS due to
hardcoded pkg-config in configure.ac.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815548 from 2016 never
received a response either from the maintainer, and Maintainer was
'active' during that time. This also includes a *patch* for the old
version with this problem and that was NEVER addressed.
=== Upstream Versions Not Uploaded in Debian ===
The last actual upload of XCA to the Debian repositories of Unstable was
done in July of 2018. It then migrated two weeks later to Testing,
however there was later an upstream release in November of 2018 that was
never updated to.
=== Packaging Problems Unresolved ===
As shown in packages.qa.debian.org and tracker.debian.org, vcswatch
can't reach the 'git' repository in use by Tino. This 404s perpetually
and suggests that Tino is not updating the packaging to reflect changes
in their Git repository functionalities.
DUCK confirms this, that Vcs-Git is bad and the repository is
nonexistent. This has been failing since at least June. This package
may also be a prime candidate to be included in Salsa as well.
Further, this VCS repository is NOT the proper Upstream VCS repository -
Upstream has a VCS repository on GitHub that should be used here:
https://github.com/chris2511/xca/
The package as-is is also using an out of date Homepage entry. XCA
upstream has indicated that https://hohnstaedt.de/xca/ is the proper
Home Page now.
=== Minimal or No Response to Inquiries ===
A couple of months ago, I reached out to the MIA team and Tino. From my
initial inqurity on May 8, 2019, it took a *second* email that was CC'd
to the MIA team to get Tino to reply to me on May 20th, when they
promised to address the bugs I indicated. It is now July 10th, almost 2
months later, without any acknowledgement on bugs, nor any follow-up
contacts.
---
Given this list of problems identified in the xca source package AND the
nonresponsiveness of Tino in this matter, I would like to propose that
this package is in need of Salvaging, and would like to take over
maintainership of this package, or if Tino still desires to maintain
this package, to become co-maintainer of this package if possible. (I
have included the MIA team in the CC because I believe Tino is not
active enough to continue maintainership of this package)
Please note that downstream in a PPA I have also updated the XCA
packaging [1] and source from upstream and it works without issues, if
you need evidence that I am alive, active, and indeed can maintain the
package myself.
My keys are not yet in Debian's keyrings; therefore I would be having
any uploads I utilize sponsored initially. If necessary, I can find a
sponsor for this. I can also get this NMU'd and sponsored if needed,
containing the newer upstream revisions and also the proper packaging
changes to make this package 'clean' and to address some of the other
warnings.
(NOTE: This email has been SIGNED with my Public PGP Key ending in
C26ADDDD and that can be obtained from the SKS Key Servers shortly as it
has just been uploaded to the keyservers, or from the Ubuntu Key Server
[2].)
Thomas Ward
[1]: https://launchpad.net/~teward/+archive/ubuntu/xca
[2]:
https://keyserver.ubuntu.com/pks/lookup?fingerprint=on&op=index&search=0x5792F66164D057EFC6D06FAF5B8AD6F4C26ADDDD
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: xca
Source-Version: 2.1.2-1
We believe that the bug you reported is fixed in the latest version of
xca, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Ward <[email protected]> (supplier of updated xca 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 13 Jul 2019 18:17:10 -0400
Source: xca
Architecture: source
Version: 2.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Thomas Ward <[email protected]>
Changed-By: Thomas Ward <[email protected]>
Closes: 927233 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927233>
928678 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928678>
Changes:
xca (2.1.2-1) unstable; urgency=medium
.
* New upstream version. (Closes: #927233
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927233>)
* d/watch: Update watch file to track upstream xca repository on Github.
* d/compat: Update Debhelper compatibility to latest (12)
* d/control:
- New maintainer (Closes #931806)
- Update Standards-Version to 4.4.0
- Update Homepage to proper Upstream URL
- Update Vcs-Git to point at Debian Salsa. Package now uses a
git-buildpackage (gbp) workflow.
- Add Vcs-Browser field.
- Reorganize Build-Depends to be more readable.
- Remove dh-autoreconf build depends.
- Update debhelper build depends (compat is 12, so use debhelper >= 12)
- Make requisite changes to adjust xca built by the packages to enable
Remote DB support in xca: (Closes: #928678
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928678>)
- Add libqt5sql5 Build-Depends for Remote DB support.
- Add Recommends on libqt5sql5-{mysql,postgresql} to xca package.
* d/patches/0001-Remove-misc-Info.plist-in-clean-target.patch: Refresh
patch to remove fuzz.
* d/copyright: Update copyright file to be Machine-readable per
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Checksums-Sha1:
f46c62e09898999231b9ed32cc9549892ab704b9 1914 xca_2.1.2-1.dsc
6af45c25e075c519ba6936e992a455336ff92f80 1048019 xca_2.1.2.orig.tar.gz
fbbe30bc031ca17cf72e5c2718d1813758137a99 5444 xca_2.1.2-1.debian.tar.xz
Checksums-Sha256:
b39e6c32a7e090a07e47e45f79e923db3038f7f32473da76282de3bf8a99b42d 1914
xca_2.1.2-1.dsc
19da0b19e5d3b145f630e9b18b3e29d5a569495d6dd3ab927f41e6b490a99cec 1048019
xca_2.1.2.orig.tar.gz
edd58372cda9255ee7ccd1e88b30664a283643bf36e8cdbaaea8faf950ffacc6 5444
xca_2.1.2-1.debian.tar.xz
Files:
51f8ec5a59346e0a10019b8b57b1f579 1914 x11 optional xca_2.1.2-1.dsc
3cacc38e8e087a82279647a083d9d0d0 1048019 x11 optional xca_2.1.2.orig.tar.gz
bcb25f4f22087f92b9daed8c6b269a77 5444 x11 optional xca_2.1.2-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJDBAEBCAAtFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAl1fkPMPHGJhcnRtQGtu
YXJzLmJlAAoJEDNV9NY7WCHMJOsP/3BLZPbZ6KA9oKtol4Os6lc/o9+DKVyXWvAK
5kWguOq44E8l6TnNyRV8akllDN9wF0EOVqARkhao7ZbisObQ+XSs+hLxkNgDV83K
Hr4+/+i0L5szQYJ7fbyifoNOLyOIFl1zeVq7SJ3cusXgFcwnVrG1IAj1QitJL1mP
XLe2lFym1naA0ZZmH9fnK5QFUwzb7LJJ/XmzslGZDkgW09YvjVvZZjeK8+rFAh9J
h++hLBu2rLDYJibx7yGFFQll30cyFsG/FEkIk09J6GH4S2x3KhDLDD5bBT4z9J8t
stBoP/UVE2AmrsfxuYV1t/b5Rpzt2NLHXTtcnG4DiN2IUXvnHCEZQPBOapRXxqgD
lAvpMSvM2lJ4A4Nv+yw3DfLgnlGTpLLosLc6HJKM7cWnF5TcRqEINz0AoDhMnLE+
kKZULYzmJzlKUCVY6gl3wzytKUdNImVInYCE9Kyh60Br5CSwZ9vd3izJIB1xC5QS
c1T6OLj8sogbQpmwecU+NRo0pTiWoZEQghIHCTqKJikbBjCZhZelnPkzUmykEm3Z
R+Rg8nAOeUfPOqs3VX9rv7fqmya9Ar4ljxCylOu2TSGOBUI1IJns5gGQ4lcWIhQE
sSFHE5cCiHT2Ycdwu714M48H8l2eBnOPfYOg1WkFeIpUctSiaQiwSk4bE6Ks88u4
FBAOajOw
=8NeO
-----END PGP SIGNATURE-----
--- End Message ---
