Bug#896910: O: libdigidoc -- DigiDoc digital signature library
On 2020-12-30, Andrej Shadura wrote: > On Wed, 30 Dec 2020, at 09:14, Andrej Shadura wrote: >> On Wed, 30 Dec 2020, at 08:31, Vagrant Cascadian wrote: >> > I'd like to do a QA upload to fix a reproducible builds issue (#978064) >> > and other basic package maintenance as I'm able without disturbing the >> > package too much, but the above makes it a little unclear how to >> > proceed... I'd rather just use dgit than subscribe to another salsa >> > team. >> >> Sure, please go ahead with dgit (--gbp iirc), I'll push to Salsa myself. > > Actually, I also went ahead and added the debian group to the ACL of this > repository only so you should be able to push too. Oh, the permissions do not seem quite right: remote: GitLab: You are not allowed to push code to protected branches on this project. To salsa.debian.org:eidas-team/libdigidoc.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'g...@salsa.debian.org:eidas-team/libdigidoc.git' Will upload with dgit anyways, and maybe you can sort out how to merge it into salsa for the moment. live well, vagrant signature.asc Description: PGP signature
Bug#896910: O: libdigidoc -- DigiDoc digital signature library
On 2020-12-30, Andrej Shadura wrote: > And yet another mail from me. > > On Wed, 30 Dec 2020, at 09:14, Andrej Shadura wrote: >> On Wed, 30 Dec 2020, at 08:31, Vagrant Cascadian wrote: >> > I'd like to do a QA upload to fix a reproducible builds issue (#978064) >> > and other basic package maintenance as I'm able without disturbing the >> > package too much, but the above makes it a little unclear how to >> > proceed... I'd rather just use dgit than subscribe to another salsa >> > team. >> >> Sure, please go ahead with dgit (--gbp iirc), I'll push to Salsa myself. > > Actually, I also went ahead and added the debian group to the ACL of > this repository only so you should be able to push too. Ok, I'll add a lintian override for that, since you've added the debian group to the ACL, the QA team is able to upload using that. I'll also upload with the uploaders field removed; it makes the orphaned status ambiguous, which kind of defeats the purpose of orphaning. Easy enough to add it back once it is adopted again. :) live well, vagrant signature.asc Description: PGP signature
Bug#896910: O: libdigidoc -- DigiDoc digital signature library
And yet another mail from me. On Wed, 30 Dec 2020, at 09:14, Andrej Shadura wrote: > On Wed, 30 Dec 2020, at 08:31, Vagrant Cascadian wrote: > > I'd like to do a QA upload to fix a reproducible builds issue (#978064) > > and other basic package maintenance as I'm able without disturbing the > > package too much, but the above makes it a little unclear how to > > proceed... I'd rather just use dgit than subscribe to another salsa > > team. > > Sure, please go ahead with dgit (--gbp iirc), I'll push to Salsa myself. Actually, I also went ahead and added the debian group to the ACL of this repository only so you should be able to push too. -- Cheers, Andrej
Bug#896910: O: libdigidoc -- DigiDoc digital signature library
Hello again, On Wed, 30 Dec 2020, at 08:31, Vagrant Cascadian wrote: > On 2018-04-25, Andrej Shadura wrote: > > I intend to orphan libdigidoc. This library is a part of a bigger software > > suite for Estonian eID. My current eID is expiring this month, and since I > > never used it for anything serious and probably don’t intend to, I won’t be > > renewing it. Not being a user, maintaining it in Debian doesn’t seem right > > or fair. > The status of libdigidoc seems half-way a QA package, and half-way > maintained by Andrej Shadura. > Since it was orphaned, several uploads have been done, including a > switch to using the eidas-team salsa repository. Previously dgit URLs > were in Vcs-*. A clarification: libdigidoc is mostly needed to enable working with the legacy digitally-signed container format developed in Estonia, while libdigidocpp (not packaged yet) enables support for the Estonian flavour of the interoperable format. Earlier this year I realised libdigidocpp is the only non-Java non-C# library for the format while also not being a monstrous suite of unrelated software, so I thought I probably should package at least those parts of the Estonian eID suite to enable working with eIDAS-compliant files — but libdigidoc is still needed for it, and its similar to the Slovak legacy "ZEP" digitally-signed container format so that I might be able to extend it to work with those files too. When I find time to get back to those things, the package will be maintained under the eIDAS team (currently it’s just myself), but until that happened, it’s only halfway there since nothing currently depends on it yet. -- Cheers, Andrej
Bug#896910: O: libdigidoc -- DigiDoc digital signature library
On Wed, 30 Dec 2020, at 08:31, Vagrant Cascadian wrote: > I'd like to do a QA upload to fix a reproducible builds issue (#978064) > and other basic package maintenance as I'm able without disturbing the > package too much, but the above makes it a little unclear how to > proceed... I'd rather just use dgit than subscribe to another salsa > team. Sure, please go ahead with dgit (--gbp iirc), I'll push to Salsa myself. -- Cheers, Andrej
Bug#896910: O: libdigidoc -- DigiDoc digital signature library
On 2018-04-25, Andrej Shadura wrote: > I intend to orphan libdigidoc. This library is a part of a bigger software > suite for Estonian eID. My current eID is expiring this month, and since I > never used it for anything serious and probably don’t intend to, I won’t be > renewing it. Not being a user, maintaining it in Debian doesn’t seem right > or fair. The status of libdigidoc seems half-way a QA package, and half-way maintained by Andrej Shadura. Notably, a few lintian issues make the current status a bit unclear: https://lintian.debian.org/sources/libdigidoc/3.10.5-1.html E uploaders-in-orphan W no-qa-in-changelog W orphaned-package-maintained-in-private-space Vcs-Git https://salsa.debian.org/eidas-team/libdigidoc.git Since it was orphaned, several uploads have been done, including a switch to using the eidas-team salsa repository. Previously dgit URLs were in Vcs-*. I'd like to do a QA upload to fix a reproducible builds issue (#978064) and other basic package maintenance as I'm able without disturbing the package too much, but the above makes it a little unclear how to proceed... I'd rather just use dgit than subscribe to another salsa team. live well, vagrant signature.asc Description: PGP signature
Bug#896910: O: libdigidoc -- DigiDoc digital signature library
Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I intend to orphan libdigidoc. This library is a part of a bigger software suite for Estonian eID. My current eID is expiring this month, and since I never used it for anything serious and probably don’t intend to, I won’t be renewing it. Not being a user, maintaining it in Debian doesn’t seem right or fair. Unfortunately for me, this software is not compatible with the Slovak eID which I actually use to run a business, not even for viewing or verifying the signed documents. If you have an Estonian eID and would like to package the rest of the Estonian eID suite, feel free to take this package over. Description: DigiDoc is an XML file format for documents with digital signatures in use by the Estonian ID card infrastructure. This library allows for creation and reading of DigiDoc files. . This library implements a subset of the XAdES digital signature standard on top of Estonian-specific .ddoc container format. -BEGIN PGP SIGNATURE- iQExBAEBCAAbBQJa4L3nFBxhbmRyZXdzaEBkZWJpYW4ub3JnAAoJEF5AjNkc2DnS zjgH/RL46ZBrJ7xR7xDLQwijgaxvcw0nWPwMPIja+RIwUHij8bKEfmflkys0zW2I PiYgEbUUukFaArMyTE9bL038bKc+4UvkdFTka1GUO4HWrprHOWra6FoMJRpJFInm UWOdrNlQvMMYMMqgos2/eDYi9yvx9fU5bRO0HEZ4M1OmRY78rnXdPbhUP3Yk70zz ug21uzxqQXbS+bGgvRELWGrrZshZJHSuGq3e0txXAi/NuXifYhsWgsz/ugWuG9pl C7DkcHv+9dVVaFSPUv6TUMCqhoamWzUqqaHAeiL7dtNOJiOnBcNzFxxZzxDrWs0k H7wCPNg9gozLLyNePqO/hyh21NM= =R5UP -END PGP SIGNATURE-
