Groups > linux.debian.maint.python > #14451

Re: RFS: tpm2-pytss

From	Carsten Schoenert <c.schoenert@t-online.de>
Newsgroups	linux.debian.maint.python
Subject	Re: RFS: tpm2-pytss
Date	2022-09-08 17:30 +0200
Message-ID	<F3rDz-6dey-11@gated-at.bofh.it> (permalink)
References	(2 earlier) <F0OmZ-4wWQ-5@gated-at.bofh.it> <F1vrX-4YAd-1@gated-at.bofh.it> <F2joK-5ta2-9@gated-at.bofh.it> <F2pNv-5wVn-7@gated-at.bofh.it> <F3o2Z-6aWf-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

RFS: tpm2-pytss Claudius Heine <ch@denx.de> - 2022-09-01 08:50 +0200
  Re: RFS: tpm2-pytss Carsten Schoenert <c.schoenert@t-online.de> - 2022-09-01 11:00 +0200
    Re: RFS: tpm2-pytss Claudius Heine <ch@denx.de> - 2022-09-01 11:10 +0200
      Re: RFS: tpm2-pytss Carsten Schoenert <c.schoenert@t-online.de> - 2022-09-03 09:10 +0200
        Re: RFS: tpm2-pytss Claudius Heine <ch@denx.de> - 2022-09-05 14:30 +0200
          Re: RFS: tpm2-pytss Carsten Schoenert <c.schoenert@t-online.de> - 2022-09-05 21:20 +0200
            Re: RFS: tpm2-pytss Claudius Heine <ch@denx.de> - 2022-09-08 13:40 +0200
              Re: RFS: tpm2-pytss Carsten Schoenert <c.schoenert@t-online.de> - 2022-09-08 17:30 +0200

csiph-web