Bug#1144194: RFS: python-petl/1.7.23-1 [ITA] -- Python Extract Transform and Load Tables of Data
Lester Guerzon <[email protected]>
| Newsgroups | gmane.linux.debian.devel.mentors |
|---|---|
| Message-ID | <6644594e-928f-4116-a39a-a949b98e3cd1__35183.0758781702$1786729054$gmane$org@guerzon.net> |
Hi Dustin, Thanks for the review. > debian/changelog has UNRELEASED as the distribution: This was intentional, as documented here: https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst?ref_type=heads&plain=1#L85. I'm actually unsure at what point I should update the distribution to 'unstable'. I was hoping that when a sponsor reviews and is happy with the changes, that they would ask me to go ahead and change it to 'unstable' right before they upload it. For the rest of the reviews - I have noticed the lintian warnings and haven't investigated the Python test failures (thanks for your findings, btw), but decided to leave them as-is since, as you mentioned, they exist in 1.7.20-1. Since this is my first-ever package, I wanted to focus on getting the experience and confidence of building a package, familiarizing myself with the workflow, then getting a sponsorship. I hoped the bare-minimum changes (as you can tell, mostly housekeeping-related :)) with an ITA would be acceptable. Thanks again. -- Regards, Lester [email protected] OpenPGP: 107B6026A82D044C97D7D8B92100C145E0F3655E
OpenPGP_0x2100C145E0F3655E.asc
(application/pgp-keys, 1.1 KB)
-----BEGIN PGP PUBLIC KEY BLOCK----- xjMEaiVauxYJKwYBBAHaRw8BAQdAlfmlljkvJIxG7dUta7Ycl8cxsnEk0dtFggcD x2/lAJLNI0xlc3RlciBHdWVyem9uIDxsZXN0ZXJAZ3Vlcnpvbi5uZXQ+wooEExYK ADICGwMCHgECF4AWIQQQe2AmqC0ETJfX2LkhAMFF4PNlXgUCaiZbawMLCQcDFQgK AxYBAgAKCRAhAMFF4PNlXpfnAP47Y5scesKd72OK3jPdy6IxId0EXqfdTWYdzkk/ nMnPxQEAywYKos7n3Gg6eEolEkkuAIulqZRy1bud9NG3gLwG4QfCkAQTFgoAOBYh BBB7YCaoLQRMl9fYuSEAwUXg82VeBQJqJVq7AhsDBQsJCAcCBhUKCQgLAgQWAgMB Ah4BAheAAAoJECEAwUXg82VeWygA/3zeGgARsSInxZddazLoydd2TzYl2SQetsFE JXJdPSFMAP9vi5GXjPzfxyaw7fk/K8/2ne/ufd6anRj5YHoTCo+bAs0iTGVzdGVy IEd1ZXJ6b24gPGd1ZXJ6b25AcHJvdG9uLm1lPsKQBBMWCgA4FiEEEHtgJqgtBEyX 19i5IQDBReDzZV4FAmp4uRQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQ IQDBReDzZV7y0gEAnoDYPneaCKt7ba2UXqFpRLmYF3VgdzGdaYkLoU/ZWqsA/jD4 Jm5UfCeAAoJKMwNm/kYZhhHUez7Q0kDpib70zmIKzjgEaiVauxIKKwYBBAGXVQEF AQEHQAFDGUOs7PEChUbpAbFc4xFdYJAst+SNOYkZq05Xa9ILAwEIB8J4BBgWCgAg FiEEEHtgJqgtBEyX19i5IQDBReDzZV4FAmolWrsCGwwACgkQIQDBReDzZV7YhQEA 7kqJddbXDRzlTpRFRCOrfOXjDAkyLjhJdDx/GNWYNIsA/RFA5j6x3YaqJbP/zuN3 XWUiWC/UKM1G1bJaw9B+Xb0N =jZ9x -----END PGP PUBLIC KEY BLOCK-----
OpenPGP_signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQQQe2AmqC0ETJfX2LkhAMFF4PNlXgUCan9QVAAKCRAhAMFF4PNl XtEaAP4nKBoZqVj2kwbzPbOt5BwoclxyZ5Dh5m4BHAAC0xQ+zAD8CtvYbqp8vNy5 SISIB4DBfPtneviTvaaok2VhM/k57AQ= =rqWQ -----END PGP SIGNATURE-----