signond_8.60-3_source.changes ACCEPTED into unstable

Sandro Knauß hefee at debian.org
Sat Nov 7 19:48:27 GMT 2020


Hey,

> The multi-arch changes were proposed by the Debian Janitor which uses hints
> from the multi-arch hinter AFAIK. 

> >   * Remove the wrong Multi-Arch: same fields from signon-plugin-password,
> >     signon-plugin-ssotest, and signond-dev, as they depend on signond
> >     which cannot be Multi-Arch: same.

I discussed this already once with Helmut Grohne, who is mostly driving the 
muti-arch initiative in Debian, when I had the same issue, that there were 
several packages that could be marked as multi-arch:same but all of them 
depend on one, that is not multi-arch ready. Helmut said, still it makes sense 
to add the multi-arch metadata, if they are correct, because it helps the 
cross compile initiative. As they see: signond is a blocker but the other 
packages are fine. So lets check what is holding back signond to be multi-arch 
ready. 
In the end there is no reason to not set multi-arch:same for those packages, 
that depends on signond. And adding the metadata data give the hinter new data 
to check other parts. That's at least what I understood from the discussion 
with Helmut.

hefee
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20201107/010765c4/attachment.sig>


More information about the pkg-kde-talk mailing list