Hi,
I am not a member of the Python team and want to contribute a Debian
package for tpm2-pytss to help resolve #1011358 [1].
I am not sure how to proceed here. Do I need to become a member/contributor/maintainer of this package or will this package be collectively maintained by the python team afterwards?
I guess I need to be a member to create the repo on salsa. I already
have made an account there (@cmhe).
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011358
bts owner 1011358 ch@denx.de , retitle 1011358 "ITP: tpm2-pytss -- TPM2 TSS Python bindings"
Hello Claudius,
Am 24.08.22 um 15:00 schrieb Claudius Heine:
Hi,
I am not a member of the Python team and want to contribute a Debian
package for tpm2-pytss to help resolve #1011358 [1].
I am not sure how to proceed here. Do I need to become a
member/contributor/maintainer of this package or will this package be
collectively maintained by the python team afterwards?
this depends on you and your intentions.
If you want to maintain this package by your own you don't need to
become a member of the Python Packaging Team. But you will need a
sponsor for your uploads then.
One big advantage of team maintained package is that not only one
specific maintaining person (the Maintainer field in d/control) is
required and to be around. You still can add yourself to the Uploaders
field anyway.
Maintaining a package costs time and requires technical skills to
fulfill the Debian packaging policy. Ask yourself if you can ensure you
will have the required time to do the packaging work, especially if you
want to maintain the package alone by yourself, but also if you are interested in maintaining this package within the DPT.
It's not a good behavior to prepare a package, find a sponsor and then
the contributor isn't seen anymore afterwards. Other Debian maintainer
will need to take care on that package then.
I guess I need to be a member to create the repo on salsa. I already
have made an account there (@cmhe).
Yes, if you want to create a repo within the teams namespace.
But you can always create new repos within YOUR own namespace! The repo
could later easily transferred into the DPT space on Salsa once the
trees are ready and finished.
I'd suggest to start that way and ask here on the list once you feel
someone should review your work.
You can e.g. force push to your git tree as often you want to do so or
feel to need to do. Once the repo is within the DPT force pushing is a
no-go and is mostly disabled for good reason.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011358
If you are interested in showing that you are willing to do further work
on this issue you should take over the ownership for this issue and also
do a retitle of the bug report e.g. by using the 'bts' command. This is available locally once you have installed the package devscripts and
have setup a local MTA [1]. I personally use nullmailer for this job
You can then interact with the BTS and set the ownership.
bts owner 1011358 ch@denx.de , retitle 1011358 "ITP: tpm2-pytss --
TPM2 TSS Python bindings"
More explanations about controlling the BTS can be found here:
https://www.debian.org/Bugs/server-control
[1] https://wiki.debian.org/msmtp
https://wiki.debian.org/sSMTP
https://wiki.debian.org/nullmailer
I am not possessive about this package and would like to share maintainer-ship if possible. For me this is contract work, I am not
doing this for myself, but for a customer, which will continue to use
this and packages around it for rolling out Linux-based Desktop systems
for their employees. So I suspect that this will be used and maintained
in any case, even if not my me personally.
Debian already contains the tpm2-pkcs11 package, which in its newest
version (1.8.0) (see #1011376 [1]) will require tpm2-pytss (which this
is about). So I guess sooner or later (if tpm2-pkcs11 is still
maintained), someone will need to create tpm2-pytss as well.
tpm2-pkcs11 1.8.0 is required to fix bugs when used with openssl 3, that
are present in older versions (1.7.0).
My goal here mainly was to help and speed up the upgrade of tpm2-pkcs11
to 1.8.0 by supplying the tpm2-pytss package. Also of course avoiding low-quality and duplicate work by providing the packages to upstream Debian.
Yes, sure. I already started doing that as soon as my salsa account was approved:
https://salsa.debian.org/cmhe/tpm2-pytss
That should work already, but currently I am just adding salsa-ci
support, and possible fixing some metadata issues.
Hi,
Am 25.08.22 um 09:25 schrieb Claudius Heine:
I am not possessive about this package and would like to share
maintainer-ship if possible. For me this is contract work, I am not
doing this for myself, but for a customer, which will continue to use
this and packages around it for rolling out Linux-based Desktop systems
for their employees. So I suspect that this will be used and maintained
in any case, even if not my me personally.
well, if packaging work is covered any payed by the employee or
costumers than this is great as it also shows it's possible to earn
money with FOSS.
I just wanted to stress out that it's sometimes better to not start
packaging work if it's already recognizable that were will no time
afterwards to do the maintenance work, which is mostly more work than
the initial packaging. At some point almost every software will get some security update which needs to get incorporated into the package and the archive. As you work for DENX I'm quite sure what I mean. :-)
Debian already contains the tpm2-pkcs11 package, which in its newest
version (1.8.0) (see #1011376 [1]) will require tpm2-pytss (which this
is about). So I guess sooner or later (if tpm2-pkcs11 is still
maintained), someone will need to create tpm2-pytss as well.
tpm2-pkcs11 1.8.0 is required to fix bugs when used with openssl 3, that
are present in older versions (1.7.0).
My goal here mainly was to help and speed up the upgrade of tpm2-pkcs11
to 1.8.0 by supplying the tpm2-pytss package. Also of course avoiding
low-quality and duplicate work by providing the packages to upstream
Debian.
...
Yes, sure. I already started doing that as soon as my salsa account was
approved:
https://salsa.debian.org/cmhe/tpm2-pytss
That should work already, but currently I am just adding salsa-ci
support, and possible fixing some metadata issues.
I've take a look and opened up a MR to address some small things I've
noted. Your work looks good so far.
https://salsa.debian.org/cmhe/tpm2-pytss/-/merge_requests/2
Feel free to cherry-pick or merge in the modifications.
I haven't looked yet into potential copyright things, if some otherThat would be welcomed!
member would have time to have also a look at this that would be great.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 300 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 106:37:17 |
| Calls: | 6,700 |
| Files: | 12,232 |
| Messages: | 5,350,363 |