-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, I have now updated net-snmp to use the new style teams. You'll see that the control file is now:
Maintainer: Debian SNMP Team <team+s...@tracker.debian.org> Uploaders: Craig Small <csm...@debian.org>, Thomas Anders <tand...@users.sourceforge.net>, Noah Meyerhans <no...@debian.org> You can use the same maintainer if you like, its a generic SNMP team rather than net-snmp specific, though of course at the moment its the only package in that team. The uploaders of course would be different for your package. - Craig - -- Craig Small https://dropbear.xyz/ csmall at : dropbear.xyzDebian GNU/Linux https://www.debian.org/ csmall at : debian.orgGPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 On 2021-08-09 at 11:25, csm...@dropbear.xyz wrote: > On 2021-08-03 at 08:48, t...@debian.org wrote: > > > Best of course would be that the packages would be team maintained, > > so I'm wondering if the net-snmp would be open to the idea to expand > their > > scope to handle also such packages. > > Hi Tobi, > I don't think there really is much of a team. Not sure what happened (my > working theory is they all finally understood how to read ASN.1 and went > mad in the process). > I think I'm all that's left as far as active maintainers. The email list > has 5 members. > > However, I'm willing to help. There's probably some overlap in the strange > sort of bugs snmp can bring. > The other complexity is that net-snmp uses the old style type of team, see > https://wiki.debian.org/Alioth/MailingListContinuation . Looking into it, > I really should move it to the new-style team maintainership (like how the > Python team works). > I don't think it would be a good idea to make a new package use an > old-style team. > > I'm not sure of your timings, but I probably should actually start to move > net-snmp onto the new style team. It would have been nice to do this before > the freeze but we are here now. > > - Craig -----BEGIN PGP SIGNATURE----- Version: FlowCrypt Email Encryption 8.1.3 Comment: Seamlessly send and receive encrypted email wsFzBAEBCgAGBQJhSHVHACEJEAIhZsD/PITjFiEEXT3w9TizJ8CqeneiAiFm wP88hON1+A//Us0cDz7Gal+NZq8sYXUvLE8QM8++gD+lmT/z+5oLU6E9RA1s +4qq/tJ/OeKB0KawxO7z6SbztE7Jb+qFQF9tRuz38sy9+Y0VFJuw3qRYYm3c QAIC4/rDEyPz34IUdLoZlwH8HsVPgcb3xeG0N0ylk3kNSPqml/Y6VzAzsAw+ t82KctEC89OqS0xAsubCqS28qBWg3TAYsmTba3fKXpxHSe3OVJpdcyUf+3xf b4Z0YQpCjwmghSlBPBfoZazUOwLWC3ffNhYmKMXNM6SjqtMs02MZCTG5ggMF iLkwu1NmbKt6isdEaMmuGUno14GwdqrFaniHaY6x67De5XxRYjMmIe8ZFdrx +ZEbuKQ1Z1UBbYuAoSC0moX8gehqn5g0me5Se3BAvyT/W7DOGr0b+GREvIbo LDEfKITsYgteyI16mYxbYJgz0gvCU7QASSDY2/k982Elp9/UglcfDnfv4FgW vnEmDcxktcgDRDCOdmoAgiYpKjFbZi04nu2Ye++T/h7WoRTDcjTkyexbzj9B oDkt/O55vJ/T/JjLASmN9G4m247rkU/2wdswHkCObFJtLMn2AWqEcjaFXcWM cwRj+ojudCsi9O2veFHEAGJqaLLddXGYylXW8sXkP2nyhTrWE3+J7CfJpXe3 bZpZ8W580vDBzgvQt3MzWz0IR7p2+Q9B1z8= =/At5 -----END PGP SIGNATURE-----