Copy: [email protected] (Debian Mentors)

Nicholas,

On 2024-09-01 04:52, Phil Wyett wrote:

2. Lintian [3]: Issue

I: electrum-nmc source: uses-deprecated-python-stdlib chunk (deprecated
in
Python 3.11, removed in Python 3.13)

In a previous review it was mentioned that the >"uses-deprecated-python-stdlib" lintian output was "Information only,
future for upstream." To clarify, is this still the case, or has it been >long enough for it to become an issue?

It is not a problem for packaging this right now, as Debian currently has Python 3.12. But, this lintian tag was added now because a lot of these changes require upstream to alter the program, so everyone needs to start working on it now. If this isn’t fixed when Python 3.13 because the default in
Debian, the program will cease to function.

So, you don’t need to worry about it for the sponsorship of this package now,
but you do need to start working with upstream to get it fixed soon.

4. Watch file [uscan --force-download]: Issue

philwyett@ks-tarkin:~/Development/builder/debian/mentoring/electrum-nmc-
4.0.6$ uscan --force-download
Newest version of electrum-nmc on remote site is 4.0.6.4.0.6, local
version
is 4.0.6

Newer package available from:

=>
https://www.namecoin.org/files/electrum-nmc/electrum-nmc-4.0.6/Electrum-NMC->>sourceonly-4.0.6.tar.gz
gpgv: Signature made Fri Dec 22 05:51:24 2023 GMT
gpgv: using EDDSA key
A0BE08C865661A9316E0A7FF762ED28DA5C007DA
gpgv: Good signature from "Jeremy Rand (Namecoin Electrum-NMC Binary
Signing
Key) <[email protected]>"
Successfully renamed ../Electrum-NMC-sourceonly-4.0.6.tar.gz to
../electrum-
nmc_4.0.6.4.0.6.orig.tar.gz.

Would it not be easier to pull from the GitHub tags of the package?

Is this uscan confusion (4.0.6.4.0.6) a problem? If so I suppose I could >indeed pull from GitHub.

I didn’t take a look at your debian/watch file, but I can do so if you still need help.

As mentioned in the comment on Mentors[1], I would recommend you include the package under the Debian Cryptocoin Team. If you would like to do so, please let me know what your Salsa name is and I will create a repository and share it with you.

I don’t typically like to go any further with sponsorship reviews until they have passed all of Phil’s triage tests. I’ll look forward to his review of
your second upload.

[1] https://mentors.debian.net/package/electrum-nmc/

--
Soren Stoutner
[email protected]
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmbjcFoACgkQwufLJ66w tgPZ0w//RU6SV47FxVMSw+vpo0Lpwmxv8K3DWhMpP+lmVfWZ+1ypy7k7jvcCwgNp Xih2kxeSziANsuuVz76GDl7Afs+KrD3BeEsrLjJh451R6zxZOFRFvu+wIBzFilXq x8nZ+/obVmLWivupHtU7xuw8oKl4NJ2wceRgp9MYXDAEBiW6q2IwmeKOZmk/vjrb k3lZcYuh+5ZKkeM15noeMusAVz7jRfS0aj3xO28NUD1NjnwrDZ288SennAWytuli XiEj0OgXXd6fHu/nC3zSMxhP45iktaA4z2AsaPNTq82Xt5JhjLoTMBlYucR3NWBa et9gjPpswMzbP9VrFqdarc5hjD472Ofia9bAIyvNd0YwExiPJ7jpV9JgwGiOFynt olZO/HpqNUA4OrYSLHKxJse9qkYokWuaGSHK7elDsY0Ul88bxBSiqQjDIHL0MlzG SPlGayV8se0+M7kfnjY5FAs1zmNnmmk8BeORi3ZAlQ0sQNxaMI0PT5GOhazASbNC PiY2kCI31Rhxu5S+xfBCGRGSBRrbwV1WxlmCHY1VxkPVt1RFV2Haw3PZBhawGElT Ze5JkQq+gGxA88lshNptFQyfhs9fS4JXLDywgSUtOU1Fl3dvsklqxKA3QbuyRFZO pci/Th8VHGCpEp3V6AoL3rD7cdZauyK9w9FmVjcFRQGTr/XYESY=
=eOoL
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Phil,

Would you be willing to run your suite of triage tests against the most recent upload of electrum-nmc?

On Thursday, September 12, 2024 3:51:06 PM MST Soren Stoutner wrote:

Nicholas,

On 2024-09-01 04:52, Phil Wyett wrote:

2. Lintian [3]: Issue

I: electrum-nmc source: uses-deprecated-python-stdlib chunk (deprecated
in
Python 3.11, removed in Python 3.13)

In a previous review it was mentioned that the >"uses-deprecated-python-stdlib" lintian output was "Information only, >future for upstream." To clarify, is this still the case, or has it been >long enough for it to become an issue?

It is not a problem for packaging this right now, as Debian currently has Python 3.12. But, this lintian tag was added now because a lot of these changes require upstream to alter the program, so everyone needs to start working on it now. If this isn’t fixed when Python 3.13 because the default
in Debian, the program will cease to function.

So, you don’t need to worry about it for the sponsorship of this package

now,

but you do need to start working with upstream to get it fixed soon.

4. Watch file [uscan --force-download]: Issue

philwyett@ks-tarkin:~/Development/builder/debian/mentoring/electrum-nmc- >> 4.0.6$ uscan --force-download
Newest version of electrum-nmc on remote site is 4.0.6.4.0.6, local
version
is 4.0.6

Newer package available from:

=>

https://www.namecoin.org/files/electrum-nmc/electrum-nmc-4.0.6/Electrum-NMC

sourceonly-4.0.6.tar.gz gpgv: Signature made Fri Dec 22 05:51:24 2023 >> GMT

gpgv: using EDDSA key
A0BE08C865661A9316E0A7FF762ED28DA5C007DA
gpgv: Good signature from "Jeremy Rand (Namecoin Electrum-NMC Binary
Signing
Key) <[email protected]>"
Successfully renamed ../Electrum-NMC-sourceonly-4.0.6.tar.gz to
../electrum-
nmc_4.0.6.4.0.6.orig.tar.gz.

Would it not be easier to pull from the GitHub tags of the package?

Is this uscan confusion (4.0.6.4.0.6) a problem? If so I suppose I could >indeed pull from GitHub.

I didn’t take a look at your debian/watch file, but I can do so if you still
need help.

As mentioned in the comment on Mentors[1], I would recommend you include the package under the Debian Cryptocoin Team. If you would like to do so,

please

let me know what your Salsa name is and I will create a repository and share it with you.

I don’t typically like to go any further with sponsorship reviews until they
have passed all of Phil’s triage tests. I’ll look forward to his review of
your second upload.

[1] https://mentors.debian.net/package/electrum-nmc/

--
Soren Stoutner
[email protected]
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmboaH8ACgkQwufLJ66w tgPLrQ//fhIFS+QVcdjZixEWk0X7IwSQCnXxZ7RepJo6OnYTcFxqc4shUPHRWLC0 snm5TZ2eIne0CYhnynb2mvBFy8sq6hbbx5OpyYKLuqEfSL9z8MZQfxYAWfyzs1bE O0rQC/3uB1uxGVNkXSXJ0DgWidKQxKZiq/zLAO15tMuGpOKs8/0sXAm4dRK9YUvE xaPoAl4oUjlIsxVkc6BePNIgwzljWmiw5G21QVmEyTt+op/ieVWoJKw5/nOup9pm KmlNXksNJ+QtqMlqE4inrxhMrO7iZdORzAOxu1xXQxkMenBTZB5NSjv3bQArtgcX s8kPoTYNFiNW1WEWD9HTmNQr6Nb7UksgypfMbsHm/daXtFb1cTj87d9EL6RE8nFi 5ECS1AMMuo9FnHddAi/la235lR+ihvkQSw6DlZVNg7bFUMIvH7sEKYXoDs8vQQUB Dd3s/mZ0QmNH2mweyrjLZFaE2BClZCYPWz5bOAT2W51xzkH3/sHyurLwYH2DDmNc F8DgXh9RIsfLGV/1PGoYvMpsGwoRPY/ydWWIks8hJbjmrU27pdf+gKJalXoUDoRi aZQtPnyDAINQPRE3kMIl688RuIwOMo3chquoRtv5x/uAj3w8Px5gsvBJQ6LwhyPE 2EZNDmCNSjDYZQvhQzyAujigDRWb02mJQthNIumRNiuaHNIpTtU=
=jvX/
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Copy: [email protected] (Soren Stoutner)

Nicholas,

On Thursday, September 12, 2024 3:51:06 PM MST Soren Stoutner wrote:

As mentioned in the comment on Mentors[1], I would recommend you include the package under the Debian Cryptocoin Team. If you would like to do so,

please

let me know what your Salsa name is and I will create a repository and share it with you.

Did you see this question about packaging under the Debian Cryptocoin Team?

--
Soren Stoutner
[email protected]
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmbofPIACgkQwufLJ66w tgN/JQ//eHCgq6IBicnW/S8DrXUsXr/9xo3Gpc2am7EhOiwxcq7WyIdcjVP0HTh/ k85NvD9PGH+oBZ+dEHZ8VRBvC3eAd0MblrrQC2gi00ET9Ngn2T9au28mZ35XjEJ3 LV9zJRHzPb2/pv5y08RYWOiyMS9hdwGzNfVYGJj+Hqg/esVJTPBVMEYP5pEINLdJ BVpfrS/1TQtsEeW0CzRvC00xx3WvBLzqp7h9bb6ONtBOmIihFVkGjlQZItXtgp7C LtqpaVSheSW309Nz17lUv4wTV9KS5fIODQaxanC5O2BIYzyI6DXgQ7nhIkGjAxsi LOhPtJTl8u2Md71py+cCVKz30cfEac9Sg4Mz9jq2ID/rbZunAUe2aqbaX+hxLwK4 xqOB5WcbnnHx0Uvywx9qKBmcMd1jd2oxYT5xGidUlZj6B0LNEO2vPf1J9vx+XTJK b8mDsIQ+KHHdWlAlvjgAnWYPv/NYeJvre5aPfytKj24vg2pCnxBMI+oTy6em5nT7 sDEAgEAU25yC+yORDunExOL69YJ0mjMLlCflPEZHOPtePUfmpA7JIEuPGxHLRbRr ykt3+eM03gcKO85raRBW1sfsghKf2OMZCIwQlzvg/uII8L0r8+sRk3GcpCpmcqGM DDMEk42bxdkShBtlprdtMTfpFi5jnrZpJNuxTjDuh0rPFlIOMyk=
=mOjK
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Soren,

Done. You will see it appear on the RFS below very soon.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080242

All good, needs package reverting back to '-1', see 'Additional...' section.

Regards

Phil



On Mon, 2024-09-16 at 10:18 -0700, Soren Stoutner wrote:

Phil,

Would you be willing to run your suite of triage tests against the most recent
upload of electrum-nmc?

On Thursday, September 12, 2024 3:51:06 PM MST Soren Stoutner wrote:

Nicholas,

On 2024-09-01 04:52, Phil Wyett wrote:

2. Lintian [3]: Issue

I: electrum-nmc source: uses-deprecated-python-stdlib chunk (deprecated in
Python 3.11, removed in Python 3.13)

In a previous review it was mentioned that the "uses-deprecated-python-stdlib" lintian output was "Information only, future for upstream." To clarify, is this still the case, or has it been long enough for it to become an issue?

It is not a problem for packaging this right now, as Debian currently has Python 3.12. But, this lintian tag was added now because a lot of these changes require upstream to alter the program, so everyone needs to start working on it now. If this isn’t fixed when Python 3.13 because the default
in Debian, the program will cease to function.

So, you don’t need to worry about it for the sponsorship of this package

now,

but you do need to start working with upstream to get it fixed soon.

4. Watch file [uscan --force-download]: Issue

philwyett@ks-tarkin:~/Development/builder/debian/mentoring/electrum-nmc-
4.0.6$ uscan --force-download
Newest version of electrum-nmc on remote site is 4.0.6.4.0.6, local version
is 4.0.6

Newer package available from:

=>

https://www.namecoin.org/files/electrum-nmc/electrum-nmc-4.0.6/Electrum-NMC

sourceonly-4.0.6.tar.gz gpgv: Signature made Fri Dec 22 05:51:24 2023

GMT
gpgv: using EDDSA key A0BE08C865661A9316E0A7FF762ED28DA5C007DA
gpgv: Good signature from "Jeremy Rand (Namecoin Electrum-NMC Binary Signing
Key) <[email protected]>"
Successfully renamed ../Electrum-NMC-sourceonly-4.0.6.tar.gz to ../electrum-
nmc_4.0.6.4.0.6.orig.tar.gz.

Would it not be easier to pull from the GitHub tags of the package?

Is this uscan confusion (4.0.6.4.0.6) a problem? If so I suppose I could indeed pull from GitHub.

I didn’t take a look at your debian/watch file, but I can do so if you still
need help.

As mentioned in the comment on Mentors[1], I would recommend you include the
package under the Debian Cryptocoin Team. If you would like to do so,

please

let me know what your Salsa name is and I will create a repository and share
it with you.

I don’t typically like to go any further with sponsorship reviews until they
have passed all of Phil’s triage tests. I’ll look forward to his review of
your second upload.

[1] https://mentors.debian.net/package/electrum-nmc/

--

"I play the game for the game’s own sake"

Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans

--

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

Internet Relay Chat (IRC): kathenas

Matrix: #kathenas:matrix.org

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Threads: https://www.threads.net/@kathenasorg

--







-----BEGIN PGP SIGNATURE-----

iQJOBAABCgA4FiEEcKCsRax3nv6E9jrtckqptS8CTIsFAmbodmkaHHBoaWxpcC53 eWV0dEBrYXRoZW5hcy5vcmcACgkQckqptS8CTItsxw//S8egZcET9hhUC4klNkTL k42JAYkXx7fXyo7INHDJXcGgia6he3cJ0kpdUjnbrQBNccY5Bnze2td7d+Fsyyyg wROxsh3kIwCjGnP5SFpDO5w6lq3kgsDvNSkm1vumuqladVCuMxGSe7l70Ib1399n fQ/6HcdIshuQT5jwE3mfusajLGcfpdlXzchWgbgH6gRhoZfSR4IuGXRb21MqPhIY +Wmm6Gk8Cfxoq8ltjOKYUD2szE91uQe2jziwNhSIQ1YNRt5zvgAH57auYBeThsgH ITM7gCY0qs7Lo9bChPpFSsdt9dnL7XT9t7glpsQEXJ4SColX4+Mgl2ry0LLT6Q5Z VqWe/XhZzLur5xTjI7jt56GmEV/Q9iQH3dfOyDrRDDGmmGsxXozyLPSXjGxN0lV+ p9ckkxC1BusTqtCb0VJNA76p6I2I2mxTocW3jh/WbDdHv2vG79PsSrHKb