Re: RFS: tpm2-pytss
Hi, On 2022-09-05 21:18, Carsten Schoenert wrote: Hello Claudius, Am 05.09.22 um 14:26 schrieb Claudius Heine: The link I posted is already in the DPT namespace: https://salsa.debian.org/python-team/packages/tpm2-pytss Since I am no a member of the team, I wanted to move it over, but it already existed, but was completely empty. So I just pushed my changes there. ahh, o.k, I haven't seen this. I've take now this repo as base for the initial upload, now we need to wait for the ftpmaster to process this package. https://ftp-master.debian.org/new/tpm2-pytss_1.2.0-1.html Thanks! Related to this, I would like to update the tpm2-pkcs11 package, which is not part of the DPT, but the new version depends on that package. Do I need to wait until the tpm2-pytss package is available on unstable before doing this, or can this be done in parallel? regards, Claudius
Re: RFS: tpm2-pytss
Hello Claudius, Am 08.09.22 um 13:37 schrieb Claudius Heine: Related to this, I would like to update the tpm2-pkcs11 package, which is not part of the DPT, but the new version depends on that package. Do I need to wait until the tpm2-pytss package is available on unstable before doing this, or can this be done in parallel? from a technical side it would be no problem, the buildd's simply couldn't build this package due the dep chain. But I try to avoid such uploads and wait for required depending packages. First, it helps me to have some better overview of my or team related packages. If the package isn't visible here I know there is some work left. Second, other user who doesn't know all related things might wondering why the uploaded new version isn't build. This can be confusing. And third, in this case here, the upload would be a NMU if the maintainer of tpm2-pkcs11 [1] might not react on bug reports or emails. So, a general suggestion in my eyes is to get always in contact with the package maintainers of tpm2-pkcs11, which you have done so far through #1011376 [2]. You can prepare and provide an MR on Salsa so the package could be easy updated by the original maintainers and write about within the issue tracking. [1] https://tracker.debian.org/pkg/tpm2-pkcs11 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011376 -- Regards Carsten
