Re: Package uploads silently discarded: how to investigate?
Andrey Rahmatullin writes: > On Mon, Jun 27, 2022 at 09:02:30AM +1000, Ben Finney wrote: > > In this thread I want to discover: How can I find out what's > > happening and why the Debian archive is no longer sending me any > > email messages about my package uploads? > You should check usper.debian.org:/srv/upload.debian.org/queued/run/log Thank you, that has the information I need, and now I successfully diagnosed what was wrong with a couple of uploads. As to how someone can know this in future: "IOhannes m zmölnig (Debian/GNU)" writes: > as i've wondered myself about this in the past (not for some time > though, since i no longer update my keys just-in-time): would it be > possible to list reasons for (silent) discards on a prominent page? > (e.g. somewhere on https://ftp-master.d.o¹). Yes, please. I think your suggestions are a good starting point. -- \ “Airports are ugly. Some are very ugly. Some attain a degree of | `\ugliness that can only be the result of a special effort.” | _o__) —Douglas Adams, _The Long Dark Tea-Time of the Soul_, 1988 | Ben Finney
Re: Package uploads silently discarded: how to investigate?
Russ Allbery writes: > Ben Finney writes: > > > The trouble is, I can only guess, because there are no messages from > > anything in the Debian archive telling me what went wrong. > > My recollection is that if the signature on the upload is invalid, we > intentionally delete the upload with no notice (because we have no > confirmed knowledge of who to notify). So, the question remains: How can I, the person responsible for uploading this to the queue, find out (not guess based on absence of any message) what the error was that caused the submission to fail? -- \ “Our urge to trust our senses overpowers what our measuring | `\ devices tell us about the actual nature of reality.” —Ann | _o__) Druyan, _Cosmos_, 2014 | Ben Finney
Package uploads silently discarded: how to investigate?
Howdy all, For many weeks, my package uploads have been silently discarded. I have some guesses as to why but I can't find any concrete report saying so. Typically I'll receive an email message to my maintainer email address saying the package is being processed, and later a message saying it's succeeded or failed. By “silently discarded”, I mean that an upload of a package – whether source package or binary package, and whether using ‘dput’ or FTP commands directly – succeeds, then soon afterward the files no longer appear in the ‘/pub/UploadQueue/’ directory; then there is no further communication from the Debian archive infrastructure. My guess is that this is something to do with an update to the signing GnuPG key expiry date. I can get into that in a different thread if needed. The trouble is, I can only guess, because there are no messages from anything in the Debian archive telling me what went wrong. In this thread I want to discover: How can I find out what's happening and why the Debian archive is no longer sending me any email messages about my package uploads? -- \ “The enjoyment of one's tools is an essential ingredient of | `\ successful work.” —Donald Knuth, _The Art of Computer | _o__) Programming_ | Ben Finney
Re: Project to improve Debian support model
Howdy Katy, Katy Tolsen <2ndlifek...@gmail.com> writes: > I've started a project with the aim to improve Debian's support > model > […] I see that in the intervening time, the project repository has moved away from GitHub (thank you!) and to this URL: https://git.fosscommunity.in/kathryntolsen/diss/> > For consideration of our developers, I ask for your input on this > matter […] The wiki content there has an overview of the intended architecture. Core Components of the Debian Integrated Software System * DISS Bot * DISS Chat Client * DISS Client * DISS Diagnostic Trees * DISS Tracker https://git.fosscommunity.in/kathryntolsen/diss/-/wikis/home> As you state on the wiki, many of those pages are without content. To help get an informal idea, can you describe briefly each of those components? -- \“Consider the daffodil. And while you're doing that, I'll be | `\ over here, looking through your stuff.” —Jack Handey | _o__) | Ben Finney signature.asc Description: PGP signature
Re: Project to improve Debian support model
Howdy Katy, Katy Tolsen <2ndlifek...@gmail.com> writes: > I've started a project with the aim to improve Debian's support model > […] I see that in the intervening time, the project repository has moved away from GitHub (thank you!) and to this URL: https://git.fosscommunity.in/kathryntolsen/diss/> > For consideration of our developers, I ask for your input on this > matter […] The wiki content there has an overview of the intended architecture. Core Components of the Debian Integrated Software System * DISS Bot * DISS Chat Client * DISS Client * DISS Diagnostic Trees * DISS Tracker https://git.fosscommunity.in/kathryntolsen/diss/-/wikis/home> As you state on the wiki, many of those pages are without content. To help get an informal idea, can you describe briefly each of those components? -- \ “Teach a man to make fire, and he will be warm for a day. Set a | `\ man on fire, and he will be warm for the rest of his life.” | _o__) —John A. Hrastar | Ben Finney
Accepted pysha3 1.0.2-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 19 Jan 2020 20:43:49 +1100 Source: pysha3 Architecture: source Version: 1.0.2-4 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 937534 Changes: pysha3 (1.0.2-4) unstable; urgency=medium . * Declare Debhelper compatibility using ‘debhelper-compat’ dependency. * Remove obsolete dependency on ‘python-setuptools’. Closes: bug#937534. Thanks to Sandro Tosi for the follow-up notice. * Specify the package build system does not require root privilege. Checksums-Sha1: 232a232c397190741a62a0578ed922d85bf1fa05 1982 pysha3_1.0.2-4.dsc 4cbff7e92462cf993d84bd66bf9b4642c2e82063 8972 pysha3_1.0.2-4.debian.tar.xz 9c176784837094b748a8d893180ca7ecba994509 7732 pysha3_1.0.2-4_amd64.buildinfo Checksums-Sha256: a322048343eb591eb2d03308a0a21f49641f5efc69a13fff733c8a6002c4b843 1982 pysha3_1.0.2-4.dsc f93c1cc0af4a737d6ca07058980ff616b7e3af071855516f2530af1ada1e3bd6 8972 pysha3_1.0.2-4.debian.tar.xz a49ce00449f989e885568358f4b805f313a6d64d71972b1ad9ad512040402716 7732 pysha3_1.0.2-4_amd64.buildinfo Files: 8382f9ebf3bd4003ca6d01428a98b01e 1982 python optional pysha3_1.0.2-4.dsc 56aa91815304b17ccb1cfc65705233f7 8972 python optional pysha3_1.0.2-4.debian.tar.xz 1a31e928280c8e13b9c770c9c30c8a3b 7732 python optional pysha3_1.0.2-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl4kK5kACgkQkgn6QYDP /G+gGA//cYsGPRAqE2648M6N11ZSjV/0Rdql8QoMviFMavROlESg32Itnkc2/lbU Jgr92YUGa97Nk6YCLM+55QBH+SoHxbEFhDQOwim1sgv1CM9tIKMesq+ztuoiAvtp E9JEHsXIVKWhjhcx+o58+IAHvGTChxELo8eDge6ragbqmbwlcV5m+Z/tupMjvfbi PjTfZY9niuvDlPmFL8b/opJeuBM5uMHqT55lsRC4xaZLb4eyqGIG0aZqBBhoRlyc uLT5VmfxiA8R11CDzG7ly3E4ZKa8etUIhhTAeX2Y9bJk0iNpxzWHoV38+zdijL9y ExqL1sGk3MCO4dUJj2SWjN1BKGQJGkX1wtKx+ELt739qQTxXRQIcxq5vu0ydjOIF nhCDbUVKkJdK0RS5EA0PkgI7fh2JBi88yUwfaHD1lo7lQQ/iqLSuIoH4EgJcgB0P H1L8XwTjV8PWdSkD9TJjJqT2WZkpCY083WmFrPH2sdzVUVUDqivwxmD4rgKZhRUx azroO3A/L/TMbdZiJAlACZb/hk/dCaCz4nrMlSzOAp3AvlIB1X5rR7hIQG2YDR8R z+mY+Zk2mizjJLBGqOAAwLpQ2JzCYp1GssER5fXNBDbaW98IbeIZFJUs/aGtSpD7 e67oWo6Vax7oPlaxsm/ul47mvoeFC5kmxp0XW3iiJKVO1p3l450= =e+1/ -END PGP SIGNATURE-
Accepted python-irc 8.5.3+dfsg-5 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 14 Jan 2020 00:47:15 +1100 Source: python-irc Architecture: source Version: 8.5.3+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 937845 948421 Changes: python-irc (8.5.3+dfsg-5) unstable; urgency=medium . * The “Hiroshi Tanaka” release. . [ Ben Finney ] * Use current HTTPS URL for copyright format declaration. * Declare conformance to “Standards-Version: 4.4.1”. * Declare Debhelper compatibility level 12. * debian/compat: * Remove obsolescent configuration file. * Remove redundant dependency on ‘debhelper’. The ‘debhelper-compat’ dependency brings the correct packages. * Update copyright years for Debian packaging work. * Release Debian packaging work under terms of GPLv3. * Update copyright years for upstream work. * Update URL for homepage of upstream project. * Update VCS URLs for Debian packaging. * Describe current source package management in ‘README.source’. * Update years of publication in Debian package copyright notices. * Record upstream metadata in a DEP-12 format document. * Don't build the Python 2 binary package. Closes: bug#937845. * Remove Python 2 build dependencies. * Update patch for removal of ‘hgtools’ support. * Add patch to correct obsolete name for tool configuration section. Closes: bug#948421. * Move Git-BuildPackage specific option to its configuration file. * Specify the current compression for the upstream source tarball. * debian/source/options: * Remove empty configuration file. * Specify the package build system does not require root privilege. . [ Ondřej Nový ] * Remove specification of minimum Python versions. These are now satisfied by all currently supported Debian releases. * Use HTTPS URL for PyPI redirector. Checksums-Sha1: 5325f7eef3b8009a4ec23195f99e50686596fac0 1988 python-irc_8.5.3+dfsg-5.dsc b0e743490d25c1b36638eb01139360498ac65291 7460 python-irc_8.5.3+dfsg-5.debian.tar.xz fe8a9bf50650bbf27acab6fac329f98460b89e39 6850 python-irc_8.5.3+dfsg-5_amd64.buildinfo Checksums-Sha256: 9b05ee13721cb5fac127aee52251b6cd549b2f36908123e90558ef592a1df430 1988 python-irc_8.5.3+dfsg-5.dsc 6f90a1d92fc6a807084132a1bdb2480e73a358ca0bed7601a8e9abca578e2d85 7460 python-irc_8.5.3+dfsg-5.debian.tar.xz 1e37d07fab71c354dbbaaec2fc55b185da635a63eb3ae750c346c40c2604e6f6 6850 python-irc_8.5.3+dfsg-5_amd64.buildinfo Files: 220992f47c4b6d0308f3285c6070bae2 1988 python optional python-irc_8.5.3+dfsg-5.dsc cfa00f321b1f4630c164ecf634adaf8a 7460 python optional python-irc_8.5.3+dfsg-5.debian.tar.xz 84e5ead4cb388394ecc61385afca4232 6850 python optional python-irc_8.5.3+dfsg-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl4cdh0ACgkQkgn6QYDP /G/Sew//WsMBEUVnheiAJhrDJuHi9ekCWhb1B/kVPX/0Yk4FNMx2txHuiuTtdPUQ g6f1miuYW7HPDv6BgLPrIC7rwoikc6ngo3J74e6pMqGa/jqo7yLT9mV19EH+t/GF oWtvTNPnlr0zqp9pTrQhEdgBZtzpLhXlTMNSpPv7e0KfXK02JtOdI8LM63LmZAWI WPMHKw0ANp7/wQn9l1umr8eAsnn1vTxDgPBUtpQdWnnjQNZnleCnG2IS96sGbHKA c+SchMSQNp/xg44hCq8BSaRIP10ixrj1lZHbAEGBFD6hqqd5LBD2q6Px+YzRm0Qx I0JadUQwtS9PEkOqBAFyNgcoBZ5UNlXIynF3RZ6PjXla12gx9v+DUHZek7fqou3m 6Dpy1bjeVUBInckH4Cjo81r0Z9cPz8EHBhsE8HHbmYrj20I3oBMsAWgQtv9n7YxY vYxwoCYr2v4c/hjo1weQyhbQEE5Qp4uKmCnI4KCMW3gOioUDiHGBLg3rrKob9U3n kF35xAakC9A812OeDiPAmGRMd6qsEOHOYEEWQKkCmpehGuwpgqCRLUaKJpkF9Po3 yiIriiZcqkJCyzkC5G9LBP1bU0XhBQyJahr2KN+Z9skDksY1QskSFvnXrwsUR8NR DtsrAAVisxLVnGKlAoGHol1TLVwZU+2jCHjoVHnZgcOzxEsKmBU= =+ziq -END PGP SIGNATURE-
Accepted python-tinyrpc 0.6-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Nov 2019 10:15:37 +1100 Source: python-tinyrpc Architecture: source Version: 0.6-3 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 945285 Changes: python-tinyrpc (0.6-3) unstable; urgency=medium . * Remove obsolete smoke test program for Python 2. Closes: bug#945285. Thanks to Matthias Klose for the report. * Correct executable mode for smoke test program for Python 3. * Tell DebHelper where to insert Sphinx binary dependencies. * Specify the package build system does not require root privilege. Checksums-Sha1: 988ce3572e1fb4e3a0e904a4e8ac60cdf7144a62 2206 python-tinyrpc_0.6-3.dsc efc12afef3c36766913ea4e95b8c33cba400afb3 5784 python-tinyrpc_0.6-3.debian.tar.xz 35a5e1729989d00d9d79094dcd688f962b53cae2 7970 python-tinyrpc_0.6-3_amd64.buildinfo Checksums-Sha256: 6f0d74c84cc18a41e4a735c3edd7770c7f46eaed57ac6d9524e82e0c0976ad7a 2206 python-tinyrpc_0.6-3.dsc bfc3603a23d8632301a723f4e66a793a4cc6fae84290fe47646a8640b3bf6bdd 5784 python-tinyrpc_0.6-3.debian.tar.xz a1c1614fae02eb4b30c12544f475086a8ab7a48e70702a212046f272d86e52a4 7970 python-tinyrpc_0.6-3_amd64.buildinfo Files: 28708d595dd78dd39491dc93f226276b 2206 python optional python-tinyrpc_0.6-3.dsc 72a4cbf8eca408001625c2d8ec6692fc 5784 python optional python-tinyrpc_0.6-3.debian.tar.xz ae3a014a1e2aea444a8aef7a55f3e19a 7970 python optional python-tinyrpc_0.6-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl3c87wACgkQkgn6QYDP /G82+w//eM6INyoUCQk7Sqo8wlJhXe1uafADu/H4kVN9WxLRkXultI+P+GyaGrCp GUZ+J4WIl3eNIaHEfahTW0Jxw76sThaD3kuc2AJCFNg8V+I3W7M7EstyfI12yHFV WU6mfJsMOLWTTper2wPVZC6wm7if5GN3NvQ4itUZ+Y9gSJppUzQnQ4v2m9br2KpQ tzY4lAYwIecs1crEecC43fIujMbiy2vgaXHfEv/Xtf0f8VAmo7WQ7uNy+RCqyAI0 2At+9fDTAYSbuuE30smtD19MRnRcfT5hqMoFX1JgHHfkh1Ak21v14j/iyoVmosi3 pMzGw59oQFWnvEPKxIkYLvvLzJFhyn2sm31Roy2mb4xDdgbTWmJjFoyqJtU8t7Nn Xu7KzAC1Vd4bYh+8cdvwwGzQNeV3UnKOkntThKxkBvUTyTplUiCJGT9mPwF0uB6E c/Fe1Baf5cKJoClGUrWChB3qZcyUuFFiDQt2I7qMgP1lGjkkhORUruItfkanEciL AzLp7UxOar4c2W+B4EqD9+TxPcsJxmn5pODMAnbUggaNswJcajJ4WVUX+RwMKYtC 7x4qVlO22ttrPWpQHY5UVarp+4QKQExUVFm0fm6N5grxZpo9TI/f4azOl6elrH2S AsvlAIr0XCZc8vwDuDU1xt2vps7CjLB9lJoDYXiJBJ6yzC9aZqg= =inS3 -END PGP SIGNATURE-
Accepted python-coverage 4.5.2+dfsg.1-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 11 Nov 2019 10:20:28 +1100 Source: python-coverage Architecture: source Version: 4.5.2+dfsg.1-4 Distribution: unstable Urgency: high Maintainer: Ben Finney Changed-By: Ben Finney Changes: python-coverage (4.5.2+dfsg.1-4) unstable; urgency=high . * Urgency “high” to restore dependency for other Python 2 packages. See bug#937665 discussion. * Build Python 2 and PyPy 2 binary packages. These still have reverse dependencies, during the Python 2 removal. * Exercise Python 2 and PyPy 2 packages in autopkgtest. Checksums-Sha1: 21462eef08bf0271bc8e0c79c98410a6aabd8a0e 2484 python-coverage_4.5.2+dfsg.1-4.dsc c0053ec888b15a02b615feb8507850a229eea2e5 21084 python-coverage_4.5.2+dfsg.1-4.debian.tar.xz a48d94486a993cbd4ccdd900ad8c828c0992a314 10205 python-coverage_4.5.2+dfsg.1-4_amd64.buildinfo Checksums-Sha256: 2283d496a1d262faff664ba41e1599a862ab7a8c5a21a7ef7c23d231859cb174 2484 python-coverage_4.5.2+dfsg.1-4.dsc 297de45884e5194d460c21b97c424dc621977098ee2ae0f8e9371bb7fb93e889 21084 python-coverage_4.5.2+dfsg.1-4.debian.tar.xz 748a64aa1a836294473f6b197618dc28dd8c9b01e599bb006fc9f6ee353f964a 10205 python-coverage_4.5.2+dfsg.1-4_amd64.buildinfo Files: fb1a26dd756457d5fa9baa1204ae89bf 2484 python optional python-coverage_4.5.2+dfsg.1-4.dsc 0933fd34844910b6dffa4eb7f046ae54 21084 python optional python-coverage_4.5.2+dfsg.1-4.debian.tar.xz 4ceaeb149d27e007621b98080d7bc266 10205 python optional python-coverage_4.5.2+dfsg.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl3IpnoACgkQkgn6QYDP /G/AYw//R/3UD51onYShbqD1qC/IxWIUdeEeLrg709/nHE+aRZM3txvXhqM7QOH1 H5exiijuKm+S9TN2mPcqCjhnUN+Wksp/goIodS+HmAs4sIffXT8koT9l5sExF/Td LkR7Peqzb5Sv5glhhgsg2nvEPOLEevsA0uh1rmWuxss+TtyJpRpP7z1m6WuHDyFy p9qsn/fqkE0edo0fiuOz4uEzn2hxvos6g8epd190wutSS0J2a4+NSuu0vJ1N7iiF HlNQSo+USaMishBScf3HHVehYAOy1869hMkKt+uyOo4pXLGXYd5oHBaTzpH4yTpz 2eP3jU0AePlTIn3IZRfdMukuVgBRIh9mtU/q37Lkvut7uMDjjNXUsh0qeen4kfuo jNlrB+IAnAiAjz3uQNKCtQZjtuMmgxlyyrBhWwq20XYsJpQ5n5hwH/ksjVwJo9Cj 2iAjBuVvFfQfEVNYIRkUUNmOzkFRhxeiILUru4ZJ+fnJkqP0SnbaEqB76veQwlld sDM9sFkF/BWtFIwCYReEHcZDmBILQ1SBwVOHF/9XfXihkcoKy9sB/51uP5KdMUL9 NGHms345hRVPD1iHUDDJMDih0ywpGujbsiazFBS2BFGYjS41Ozg+qH13aMPPzHQu pG7glOOm7Ui/a+7mhIbnMBlL4B2geqJhD0sT6gum8iadlG1GwqE= =mJ4e -END PGP SIGNATURE-
Accepted python-coverage 4.5.2+dfsg.1-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 05 Nov 2019 11:10:34 +1100 Source: python-coverage Architecture: source Version: 4.5.2+dfsg.1-3 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 944076 Changes: python-coverage (4.5.2+dfsg.1-3) unstable; urgency=medium . * Specify the package build system does not require root privilege. * Specify that the documentation must be built to autopkgtest it. * Update the expected directory where documentation is installed. Closes: bug#944076. Thanks to Paul Gevers for the report and trouble-shooting. Checksums-Sha1: df06533cf36e7c210b94efbb62db20e397a98c85 2258 python-coverage_4.5.2+dfsg.1-3.dsc dd8491a196be8a751a25ccbbcab417fed9c93571 20240 python-coverage_4.5.2+dfsg.1-3.debian.tar.xz 538f467b35ef62df33427b4470edceddf5cd5f7f 8538 python-coverage_4.5.2+dfsg.1-3_amd64.buildinfo Checksums-Sha256: 3350b34023a094f9d9b903056354cf36cb9f006375e724804460a0400d992050 2258 python-coverage_4.5.2+dfsg.1-3.dsc 415b5b6c17898d9034c258682414bf516a92cd36d83394dba87585ac190422cf 20240 python-coverage_4.5.2+dfsg.1-3.debian.tar.xz 2f02e9ae81265da7a836e2e92ccebb6bd922e4fc3a6b9e19e23926bdde458beb 8538 python-coverage_4.5.2+dfsg.1-3_amd64.buildinfo Files: a00d03edca0d444876e3471160d8649d 2258 python optional python-coverage_4.5.2+dfsg.1-3.dsc 2e603d42479db5f113d9ebd507c3bb71 20240 python optional python-coverage_4.5.2+dfsg.1-3.debian.tar.xz 99365b56716506ac2352905f35ffd8b5 8538 python optional python-coverage_4.5.2+dfsg.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl3Awk0ACgkQkgn6QYDP /G/QKw//Q58z8CpSj1Ysj4XygjYSyiO+T/nqID5AoBsYXN3m4ChUpVeKNAAFfFmQ tppCgbEuWewYnok5jH6ANcPG/PIN9fOFHZRBw9vKrIumPi40EwhfJ+C9XRlGneWG XOerxHrmYYMEzNF0gQZqwT4/Eew0MhOl7UEZHuH/ykNO/eXKbyYsgDZLIQh5TAC1 krPv2q6z18XPw0DRJs1RNyng0H4DBhiUfs6zcog27NnX1PcPCCuHxBgkMyMYKqWL 34ORuu2BNHt3Ed6mYx1uSBIHW/yn67h6faZLf+RHPrbB0VtQSYYjYgtd0g6qTRk6 hhg11HTUNhzAWua7fhifzmr2XubsxGMjuaQ+qzuJjorESc4K8FWxqFnJlArrNjgF TJ8ZGvrNUXgzkIMnnwnkohksc+BYnfJ+OAW1L/h1tqepzpbzUh4tjKik+ebKK3HP MrYUDGgjD1AyvrwRoZPR7BgUeiQfEChy/EOujvkEQJRNf+bUisDfdh7HnJ0xP4Fo qBXnGNcEGmG3g7Rwr1QW39zGxrNH8NhpaFmlsB5mlMrhqAkh+gQ6kcESYqgrmEQl dY5pBIjbCD4wpT7az+Fk50aL1pB1bC+TJpF29LRj+XpSmdJ+Yr/N5cLZvULQP5sV oS5mjQ0I9SA7ZVM59xzP05eNPZcKfwbJUDyrRTdOgrsV6QFRfGA= =EjMi -END PGP SIGNATURE-
Accepted gandi-cli 1.5-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 28 Oct 2019 11:31:00 +1100 Source: gandi-cli Architecture: source Version: 1.5-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 923084 Changes: gandi-cli (1.5-1) unstable; urgency=medium . * The “Hideki Hashimoto” release. * New upstream version. Highlights since previous release: * Bug fixes for argument parsing to some sub-commands. * debian/rules: * Correctly specify the Python build output directory for ‘dh_python3’ to read. Thanks to Unit 193 for the description and solution. Closes: bug#923084. * debian/control: * Remove redundant enumeration of dependency Python packages. * Declare conformance to “Standards-Version: 4.4.1”. * Remove redundant dependency on ‘debhelper’. The ‘debhelper-compat’ dependency brings in the required package. * Specify the package build system does not require root privilege. Checksums-Sha1: 6486f5081d976bcfab9613883f47c48b01d08a1f 2004 gandi-cli_1.5-1.dsc 08aa0eab92fc0d680bcf5e0c1312f036d08e375b 179987 gandi-cli_1.5.orig.tar.gz 3fe18fd028ad7e9d79875bc0b5ccbc594619c3c8 5544 gandi-cli_1.5-1.debian.tar.xz ca89861eb35493dd231f336c3cd2154047dae770 6566 gandi-cli_1.5-1_amd64.buildinfo Checksums-Sha256: 0ffc770c5ae0d601f4ddfabf8154f8c890954ea7f9636e1637110dd18a2de6b4 2004 gandi-cli_1.5-1.dsc a575be04fd373d4798ae16f6cbe03e8ed16255043788fb3de13bebfe7e621c84 179987 gandi-cli_1.5.orig.tar.gz 0adbc2f0bcbbe4d034709f157640b95c87f5e7a94a85a2fe42d44ef6977e2ec5 5544 gandi-cli_1.5-1.debian.tar.xz a7719153202eb721247669a02692bdf044b4f7008baeeb4ed5356bc3a1b2f5b1 6566 gandi-cli_1.5-1_amd64.buildinfo Files: e79651d5f456469b2b753dd6eb59c9a1 2004 utils optional gandi-cli_1.5-1.dsc 9f42c70d8655dd07899a590f038c9980 179987 utils optional gandi-cli_1.5.orig.tar.gz c3227bae984d5f690480538adc913bcf 5544 utils optional gandi-cli_1.5-1.debian.tar.xz b3fb2f3971a0b5ce29f925a561c20a95 6566 utils optional gandi-cli_1.5-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl22OScACgkQkgn6QYDP /G9iiA/9HkPdYjHFC9KTZGOOUwhHHDxWMGhRTEXZIpK9fxk1E0p50cs+LpWGV2h/ 33l5l7vRdZ5RJi5emu7vxNtHb06UiwXQQ7PmtKnYNJpUj3FPrAmnRW0BuCUWcllT BUWl3SvuU2LuncCNWJAlDGi+M6BCqiI7gn6N7F4Vzi1HvuzhNITjy2Jg5o4BERQb 19qnofO04P+HLVHWwQo89+BVn3ItWpep0kqrZ9nQvh3/9mUmbyh8uwhHzl+NWtAV AX6ja4TjOi/FAam/uqZ0T1XTDia8VkYqBtkAZZYxLxkex46uqmjItvCmZSk+/pni 9Ex3Ydtr9R3qf4VBG6KEraTHPCWhvyvQK41rp8d5NWoV4Wi6TgSWAAqTN9uQH8ft V/1c6fikX4crWnNJ+eOxtJ+opPmhj1vcnBsIv53507IN20F8VGqACobIgRFHZacA 9AQD4vwZWp3UWqaePGDsT1aAyRdN/OtkO5mSp1UXcgCU4zk20haPJT6cvvpSMgX6 iTuug7HN6op4rPtTV+Uj1BfTY6qrZKmQLAH8ujm9nuTrikx1EPxYlQMAipdLycH2 BH8u8O68r/prUA8/NcbLr9VkfQuqvpIAm5B+aaKUdeo0xXu0/PcNlFV05TKtv4mh OGp9u0maQQWah0Ht6JKuWUEWZ/6I3e9ddjI7tyx8LE601QvCvhQ= =Q2k1 -END PGP SIGNATURE-
Accepted python-daemon 2.2.4-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 28 Oct 2019 10:16:51 +1100 Source: python-daemon Architecture: source Version: 2.2.4-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 937684 Changes: python-daemon (2.2.4-1) unstable; urgency=medium . * The “Doris Rivett” release. * New upstream version. Highlights since previous release: * Improve speed to close open file descriptors, in conditions where maximum file descriptors is large. * Catch some error conditions creating the socket. * Update build dependencies to allow for Twine. * Specify commands to run the upstream test suite. * Remove redundant dependency on ‘debhelper’. The ‘debhelper-compat’ dependency brings the correct packages. * Declare conformance to “Standards-Version: 4.4.1”. * Remove the autopkgtest for Python 2 binary package. * Don't build the Python 2 binary package. Closes: bug#937684. * Remove Python 2 build dependencies. * Specify the package build system does not require root privilege. Checksums-Sha1: 675327773a4d1e5bcea6e788862d31074ac79f81 2384 python-daemon_2.2.4-1.dsc 14a86a2088915edb8f8651629d3ebe94749029eb 80775 python-daemon_2.2.4.orig.tar.gz 61f3fe9459586d03f5d1ca098e75038ef04b8638 833 python-daemon_2.2.4.orig.tar.gz.asc 3844dd4ee30081b1fa86c9ec68006181548a5517 31204 python-daemon_2.2.4-1.debian.tar.xz 6978f07465575ab0e0b77f162b1ac706670751dd 7533 python-daemon_2.2.4-1_amd64.buildinfo Checksums-Sha256: e00f5fab5257d85f83e8f5bbeb38e36489c2ba1ce9913ad9c5c3902ddd4f3a28 2384 python-daemon_2.2.4-1.dsc 57c84f50a04d7825515e4dbf3a31c70cc44414394a71608dee6cfde469e81766 80775 python-daemon_2.2.4.orig.tar.gz aa3c5b3531b0d621cf1b8527a164819f51b85eae88b056fc7a2bff29d22991f5 833 python-daemon_2.2.4.orig.tar.gz.asc fb7abd1ae34e5b5d3a13294decabc9142144050bb20326cdaeb82bbb41f1d4b7 31204 python-daemon_2.2.4-1.debian.tar.xz 1537c6caacb9971743cbc355d65eb59465a23d736676f5ade9e7cab816f0024b 7533 python-daemon_2.2.4-1_amd64.buildinfo Files: 90fd5d61242be400b4c3ca0b406a1b22 2384 python optional python-daemon_2.2.4-1.dsc 922f2ce6ae9790994557c38faea75788 80775 python optional python-daemon_2.2.4.orig.tar.gz 336f4a10fdeec2524864be1a51206a68 833 python optional python-daemon_2.2.4.orig.tar.gz.asc 8b1a7755c51b861e0093248e6e3011e7 31204 python optional python-daemon_2.2.4-1.debian.tar.xz 222e13f4df89d3ed7d364cd112a06d08 7533 python optional python-daemon_2.2.4-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl22Mk4ACgkQkgn6QYDP /G/kZQ/+IjkwCURfE/OW43EBBhjTodSiLizGU+ukqAt6d3BLL9/LWiK67tejsdzq m0XcWBPn2FL0qEKTVXbXCMY2TNDOBoX9xhhNFyMg3OIKoEVsLUpv5/FcdhKJmbuU wmfIGiGvX5emX1jtvAnz9BGtOE18GnFngIWqfZUZ2E2GD7+HzMsb8PygmunqpLlW 6gon9tECe2/Pl9pNxOqZZ6iAKpKxb++U9GeVkw+bYmGdzDLiNFCQu8nmBiDkBV87 1e2vqQQi1GvK+002ZFRIryJR86ob3YjloJZxidAXIk2L1ksLnFLTU+2RkceLQG8v 6amA2uU0janXrNzcY/pDa6iQyI6X71J1sxPyT8TlbN/vHnf7jQPcr1kvQkHuniwt KpsKQCecdZreOR2mSt+AAf6U+CSfhJf7sLv3Y+Xk0molU8g4jYgz8q1b+qT8rdpq oGkwoZhJjSJ1myqtK84cJ16CLA2P/cF2fLkhiRNM8PQ3lpa85cG7xfd7KCM7F56l vHOeKdecAn60ydAHn+AOLaW4s6t/J75vMZWsPK44YxiVeppV1whr/eEhQiBgd+Fz 9+Ssc7w5g3/qy8B8P+IV5HIy6fKzG/IsEXzzZXAP88B9NDNhSwJ3a8cYTfxX2tWd 375Kc9ncIa+aSHhO2TctFpHHkiF8Dh5wHS/3oGZH+wNsWat8ILc= =3bQa -END PGP SIGNATURE-
Accepted python-coverage 4.5.2+dfsg.1-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 27 Oct 2019 13:57:10 +1100 Source: python-coverage Architecture: source Version: 4.5.2+dfsg.1-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 937665 Changes: python-coverage (4.5.2+dfsg.1-2) unstable; urgency=medium . [ Ben Finney ] * Declare conformance to “Standards-Version: 4.4.1”. No additional changes required. * Remove declaration of minimum Python 2 versions. These are now satisfied by all currently supported Debian releases. * Declare Debhelper compatibility level 12. * debian/compat: * Remove obsolescent configuration file. * Don't build Python 2 or PyPy 2 binary packages. Closes: bug#937665. * Remove Python 2 and PyPy 2 autopkgtest code. * Remove build dependencies for Python environments not supported. . [ Ondřej Nový ] * Build docs with Sphinx by using system Python. Checksums-Sha1: a56232b3b3cd58388d90afdc59e9cc9261e19afa 2258 python-coverage_4.5.2+dfsg.1-2.dsc 2227a0bf720aabed10f5c9c70b1ae873c20c3ab0 20136 python-coverage_4.5.2+dfsg.1-2.debian.tar.xz 21ea0a6d221c0fa3fa08d11d982909a90991aa21 8624 python-coverage_4.5.2+dfsg.1-2_amd64.buildinfo Checksums-Sha256: d84b8a847945cdbec0628c5d59e6541e137e473595e7236b6c1336cb9c906de6 2258 python-coverage_4.5.2+dfsg.1-2.dsc 492daa9ece3c9a506f722e0a644a493eff2dd78bb335c3e273ad3e462c839a2b 20136 python-coverage_4.5.2+dfsg.1-2.debian.tar.xz 992d0e7dab2a49be0262f4807afa7a337517bb62d1ef2716fd0a74b56a18e2e0 8624 python-coverage_4.5.2+dfsg.1-2_amd64.buildinfo Files: 3b8ff77ea9c4f3d343440374531de438 2258 python optional python-coverage_4.5.2+dfsg.1-2.dsc 271cc20e686902b9b6cd21b5d9e4a9b4 20136 python optional python-coverage_4.5.2+dfsg.1-2.debian.tar.xz a9a4cc711ed8877ea29855269ed2a978 8624 python optional python-coverage_4.5.2+dfsg.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl21DDEACgkQkgn6QYDP /G9NiA//QEre8nzv6O7XCOEibFNZEDfLDTybFNfC2h/0uq7WRyiUMnqTa0LAfNpT 9lsB0hSexQ/vXRVwN/raZmx1OOL/CTzKwcAQKIsyqFW4kX0Xq6tHg6epzKuOwp/u jUq0eQyhbR/La+axDuCuzMSLD+SQTWQ2n9tXFCy0+jSviBdQdoClH1VEvPTQQRgv S9ajAhGK1uuupoT2m1GkdQ4CQUadqRv1zA4HRFKWjpKT0rmHbBmCe6/fmYqYlqHW d8JXDm58Xcjs978t3a0WmDWsq+J57vo9RPLZEuE1xcZNnHpLbOfE77O5H98bNZ+m 8lkmF7veCfFOHjFH1DdwP2OypqmSJN0mAJoj9xubGdQGBpRw9H7f0oNhyKg8es7c PuuRGLX/DGHyFEuXWkM0Sv0vVeWSntRr5ljkkiEiY3oVnsuVP04TIFf312DGdRLv 9SQnD62mCLTVMVI2Vy0VSh5vL/dpW45vKeXAb3kzgPhiSO7R4i9OF64Lb7OVv+dU 2M45qGeOkCiHxkuVDcZC3/KnWMV8egVVdPBZOBciNNCx/mqVc2ztTcFEoHQ+pAUu 0FrEML8QwHgxNxNOKe9VMMYFdphop1OppPjyjpXf0MCrKNNiCI5y2FCxvLfzJ2fz 6kqqmmuRV/bt5hkAB0pT2zAqtXouR9JLB6Deez0331sy+5Dq5Rg= =SIzd -END PGP SIGNATURE-
Accepted pyethash 0.1.27-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 27 Oct 2019 10:47:27 +1100 Source: pyethash Architecture: source Version: 0.1.27-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 937432 Changes: pyethash (0.1.27-2) unstable; urgency=medium . [ Ben Finney ] * Declare conformance to “Standards-Version: 4.4.1”. * Use a null command for ‘clean’ during ‘Git-BuildPackage’. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Remove obsolete control field for Python 2 version. * Remove declaration for minimum Python 3 version. Python >= 3.4 is now in all supported Debian releases. * Declare Debhelper compatibility level 12. * debian/compat: * Remove obsolescent configuration file. * Specify VCS URLs for current Debian package VCS hosting. * Record upstream metadata in DEP-12 document. . [ Sandro Tosi ] * Remove autopkgtest smoke test for Python 2. * Don't build Python 2 binary packages. * Remove support for Python 2. Closes: bug#937432. Checksums-Sha1: 2ae70c462db7c75e2ace919fbcdef2a4e473b061 1945 pyethash_0.1.27-2.dsc 3a033445b26301e16837cdd4dd4282ff10bf36a2 7472 pyethash_0.1.27-2.debian.tar.xz 53bd9f1126566a18931b38bf06449f78d13bdf1d 6667 pyethash_0.1.27-2_amd64.buildinfo Checksums-Sha256: ad650ed27dfaa26b06a9d8dc486632adf4e4667486337c55dc99a3cc515cd629 1945 pyethash_0.1.27-2.dsc 8fd221bfd4b282585d319107c0d043ce970747513ce8ff461c49ea8fde570707 7472 pyethash_0.1.27-2.debian.tar.xz 66b355bb3b70e307cf7f6aeeed5775dfcb5d1b1d9ea9c6fdf10f22903d938192 6667 pyethash_0.1.27-2_amd64.buildinfo Files: e20cf71567ea1287f106acb37d52fd0f 1945 python optional pyethash_0.1.27-2.dsc 09d8d731b2f1b2cdf200533f58a50d36 7472 python optional pyethash_0.1.27-2.debian.tar.xz f97635db7d92f1a41aa7bd9cee680c8e 6667 python optional pyethash_0.1.27-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl204vcACgkQkgn6QYDP /G9Whg//VAGjPrGWP4I4gZMqN8ZVi5P7ADK7+5DCZBM1zk1KDlG+rYntF+EGY86e H4aCIF94JlWwsAXpDJwxsP8/9/NrJTfaMX0cVZwOynfxW7blxtcL4WmRgAnJYdcZ 7JEXxIBR9DJfMZe+WYe3X/JzrmXZKHACVJOiZqYJ+s9BjDjuCTyuWSO5xJdwt9Uj BIJZ6c8pphca1AFuJCvoQuObhEYI6pei2/XG3PnZSw1lPz1HSFZ7XO7f6HOAXG3h PB8nTBn3f7yyIi9HHe8bPhBsTiMyv+Py59uq9vVPtTiMrpMRW1oCP4JGy4nXRP7G N9eP+SDgXbOWEuA/quNIz7upFU4EUUd57sUE/gaDhklAR5gu0mEHhEU0w0oXx3gL md+nKXGx4m9DdeaakykFx3OyjUiDzyMomjB+nkC7qLkXW/YNgqG2NGq9nX8orsUq PYfJSMoBms4Qb771G/7NLzhpO9oXO6K9YutwRH3OEqDc4JwvjGogCUDe30sRPZo0 kSBhMPXwFZ7XthbqWbDZ75FiFdW55Ritvwo8z8vhZUrvfw0IeB3wBFo70PNmtOfn WuhMqf6ISTjNxxIZzV/VN2SKuxJ9uAOsm3ueYnZrDWsMxqb7eGH7w8X+Doc0d6vo 2aGenYLyQ5CFXFwMIf8rjeZtxI/xYWXFTue8WPGKrRG+Jhlea0A= =SJ0S -END PGP SIGNATURE-
Accepted python-jsonext 0.4.2-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Oct 2019 12:25:12 +1100 Source: python-jsonext Architecture: source Version: 0.4.2-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 937855 Changes: python-jsonext (0.4.2-1) unstable; urgency=medium . [ Ben Finney ] * New upstream version. Now includes user documentation. * Declare conformance to “Standards-Version: 4.4.1”. * Specify HTTPS URL for upstream source repository. * Improve consistency of copyright grant in Debian packaging. * Use a null command for ‘clean’ during ‘Git-BuildPackage’. * Declare Debhelper compatibility level 12. * debian/compat: * Remove obsolescent configuration file. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Update copyright years for Debian packaging. * Specify current VCS for Debian packaging work. * Remove ‘debian/patches/migrate-from-times-to-arrow.patch’, now applied upstream. * Remove obsolete control field for Python 2 version. * Remove declaration for minimum Python 3 version. Python >= 3.4 is now in all supported Debian releases. * Record upstream metadata in DEP-12 document. . [ Sandro Tosi ] * Remove autopkgtest smoke test for Python 2. * Don't build Python 2 binary packages. * Remove support for Python 2. Closes: bug#937855. Checksums-Sha1: 89f704062a200a2d4451a0cb6a1c82ed276df03a 2053 python-jsonext_0.4.2-1.dsc 7770c7e91644587238ee2177d97461a7c123c794 9574 python-jsonext_0.4.2.orig.tar.gz 7660bc331021ba14a4d5f79df70990a02c93be4f 5572 python-jsonext_0.4.2-1.debian.tar.xz 071c09e501486eff6e85c06568d34e01919c5573 6373 python-jsonext_0.4.2-1_amd64.buildinfo Checksums-Sha256: 27d01cdf07731792cdda67988249e2a0d1a2f2fb7950ca96ffe682deaf30cc30 2053 python-jsonext_0.4.2-1.dsc e7634e0b8d1a668bd2c92db5498f6162573feb72ac050c4415384e773b1ea091 9574 python-jsonext_0.4.2.orig.tar.gz 85f700906b23eb56a980ae010634af5589cdbae65165dd1d05c26d47f62b3535 5572 python-jsonext_0.4.2-1.debian.tar.xz 84b5353926e69a825501948bf08dd31f02483b7330a6392ceac84f4e4616b39a 6373 python-jsonext_0.4.2-1_amd64.buildinfo Files: f8fd7a5277a2bb73b19e2b23cf597cca 2053 python optional python-jsonext_0.4.2-1.dsc 59207a244eba23bf628ed24935e4eee7 9574 python optional python-jsonext_0.4.2.orig.tar.gz 3364f1e72c954ab8fabc4100f08378fc 5572 python optional python-jsonext_0.4.2-1.debian.tar.xz 5f325bcbe6ee84abb99dcada1b7dbea1 6373 python optional python-jsonext_0.4.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl2zo8QACgkQkgn6QYDP /G8sHRAAh+ypJI+58ufnFF0fTTW58JSzC36/jL+FszD0fJqNGufskavCePCB5Byz M9aSjTBuMeji53r5qkj1UpXFmLFaP0kmKfI9b1TS906MTS81Nd1qNp6RS6Evav0f M43zBqiQV6EIVmTqyU7l5FEcv8T4I+xf4SY2m/+qni5IUwYIHzth5lz6E4eDyBHC TjGZKYsjasmNE5kmwNR6C10zcRnea7Su4iOGLNbXai8qv5ubkQNOyilHHqGVJJpp 4eYlOhZ3ZuTYuBogdDRptIuTayWVKl3lE3RY4kdU25r2Ugc+1A2cuX4AdoQT0wPG eNdOetdZaNoRpyTo6plKkA73Z8I9XFTw1/krbpcQIh00w97awjMs6YBf3iJnpSnC I9wA9dBC2SSBUcpGbCml9pnTdkWq9L6vPE7AsaCuNeWV2GEz+o6Ma1uXEtEUGrnb S/f0YNf++UJ1hOEAHJcuUBkri1xjNK37/ogpioOTSIr6JFgz9RhLfiAcv/CzAoJx afhcVnhi62TDaOOzdu29UihJ8+IG9tUkpuOzuXxBnR9ZdA0w8gUSS1+w8Nfni08g HlENmQlxk7sXqq8bNMEjF1RqtCv9tUnWXl5fQk3+zUyPC2STaZX/iP1fVF3wRPXP UhkV1KtvsoLPzkt3pJ3Frb9kyEdcEt6sZlLBvoAxJgBNqPL7/2I= =cOfy -END PGP SIGNATURE-
Accepted editorconfig-core-py 0.12.2-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Oct 2019 11:03:13 +1100 Source: editorconfig-core-py Architecture: source Version: 0.12.2-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 936468 Changes: editorconfig-core-py (0.12.2-2) unstable; urgency=medium . [ Ben Finney ] * Declare conformance to “Standards-Version: 4.4.1”. * Remove redundant dependency on ‘debhelper’. The ‘debhelper-compat’ dependency brings in the required package. . [ Sandro Tosi ] * Remove autopkgtest smoke test for Python 2. * Don't build Python 2 binary packages. * Remove support for Python 2. Closes: bug#936468. Checksums-Sha1: 40bc82c34f24ea815c97f04d292f27d83f9568a5 2099 editorconfig-core-py_0.12.2-2.dsc ca45de7ed86b381ac21281c4039d595d90c4ffd9 8980 editorconfig-core-py_0.12.2-2.debian.tar.xz d2845ff62f31fe0f91a93f7adce05d5bda733d2d 6293 editorconfig-core-py_0.12.2-2_amd64.buildinfo Checksums-Sha256: 23d66bfd91187bf9af111b9301b5961ff604a840ffb03ffd7d71fe6303669fa4 2099 editorconfig-core-py_0.12.2-2.dsc 89ca17c3db85765b8cf12e7b6a3b47241beff0502c7c27e57291b625f27966cf 8980 editorconfig-core-py_0.12.2-2.debian.tar.xz 8fe263fdfc525f469ab21e038af41359bcbd6b3fbabee2f5e6770f9db13eda8a 6293 editorconfig-core-py_0.12.2-2_amd64.buildinfo Files: f1c2f059d4e6b92c63b24acc1a4633be 2099 python optional editorconfig-core-py_0.12.2-2.dsc 6858f196067162fe03478a347f297ef7 8980 python optional editorconfig-core-py_0.12.2-2.debian.tar.xz b3075bc7d4ea523bec0f9803b9d91d78 6293 python optional editorconfig-core-py_0.12.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl2zj1YACgkQkgn6QYDP /G83DQ//V7B0XNVHhvN+s9z7mwEWjCeLUzn86zTtolbBzo4SQ6tWmjoUCZgLWcWJ ndDCGJmkbY9Lqkz1HLGPghOPdFsa3bh5chNx3rNrTM+1e9XfwxzWjX6J2pDaOugr y1KlKDPKH1iJCFQhrhZfN9vOGogrb8qixAlr6/JPECK/bumaW/mEA/R0p8Ma7N4F 7ABRyEzdXJ+E7Yrx9GCHtpBn9dghswSr2/hOspu9MWDIQQ1DrMphVoM0ElDkatlQ RrQ5IAi25qZ3RzVzaFIfZLyYqp26w2rzqnvzkcOFZtRf3TWMHn66Y41gYVJENgaz RO8Iuj2ZWSDGXm9suEj0wiVr0LjZfuM6/zUsrjSMtMzFzHoVKOIP7YijYVLpTVbm 98BO7gDvcUyAoPTM03ODV0hFvsPauzRe8s+ffYdqWj+x9/X2B8mInKNqRkfspan8 W16vBIT1YT/Sk48gQ+q2o7wg2oabo1+TpoS5+0M5ybC59jMcgxREg/JjqZZDGztZ wepCE+I4RpsrMNb2KJdurXCc67H3yyT/kNtYM5fKHO8uVPqFR9nMQQXGB/Qd4DI0 d7Rq+Yghr/eqrcse3XtfbFghLzp1KYWyTOsObcs1Jwv+PsQ5stbBRkI4F1fHBA0+ 47Mq7Bz18xzsBFRgWuDsSnJVaPltM+x5sXpPJQbZ4hYSRmV7pWA= =oK4D -END PGP SIGNATURE-
Accepted python-tinyrpc 0.6-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Oct 2019 10:33:45 +1100 Source: python-tinyrpc Architecture: source Version: 0.6-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 938218 Changes: python-tinyrpc (0.6-2) unstable; urgency=medium . [ Ben Finney ] . * Declare conformance to “Standards-Version: 4.4.1”. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Specify VCS URLs for current Debian package VCS hosting. * Remove obsolete control field for Python 2 version. * Remove declaration for minimum Python 3 version. Python >= 3.4 is now in all supported Debian releases. * Declare Debhelper compatibility level 12. * debian/compat: * Remove obsolescent configuration file. * Record upstream metadata in DEP-12 document. * Use a null command for ‘clean’ during ‘Git-BuildPackage’. . [ Sandro Tosi ] . * Remove support for Python 2. Closes: bug#938218. Checksums-Sha1: 92c35b7d360fc4a2f4ce90d0d04e78844a6decfb 2244 python-tinyrpc_0.6-2.dsc 9850ff58cfd60afd1b1dd87d55ef69531f943fca 5684 python-tinyrpc_0.6-2.debian.tar.xz e863d063617abc79f7d0ec7bc6011cc0825485e2 7992 python-tinyrpc_0.6-2_amd64.buildinfo Checksums-Sha256: 1cc66b13b7f2bcc001a8aef7392bf0bbb44396d67279dd583446456072b411a7 2244 python-tinyrpc_0.6-2.dsc c650b7eb6926271fbd454d265fea17554f9643d59bfbaabba808e59f3a6dcc21 5684 python-tinyrpc_0.6-2.debian.tar.xz 7e8beb912bf36fedd178b5df56980768e06e83026d10bdceb28744dc8a349e75 7992 python-tinyrpc_0.6-2_amd64.buildinfo Files: c0062bd895c0c0593117d6c8ead6c107 2244 python optional python-tinyrpc_0.6-2.dsc c62d30ec8f47087cfa11d49052cff4cb 5684 python optional python-tinyrpc_0.6-2.debian.tar.xz 4636e9e2ac5c380d676232ab6777bfba 7992 python optional python-tinyrpc_0.6-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl2ziQIACgkQkgn6QYDP /G/3LxAAg2u9sD2ZjKQey9JMg7URbAMSl86VvDaQjXIHQQpkILWJn5pnkEmxNfvj eawVMjh4ZteTR/Wv0q8UAiOk47/yHnHaIK3y5JK/oXgYXXtLLfqkz/p0v+1tXQVi PJ7NqVhzH3XqMWknNvRut+Ps26j7yjBjRKV3e5gg7wugA0ANmE70wkaC2v9Sqnrj kgiqG36tSAnaJFMkXjs36cd+/+6Cc8hD5P4zOwrt8zSPpce232E7Nstx4JhVXb9G pulqkSzriypATwytLkHDVMdt6S20vIvoaR86Y9xswGEhBURkRhq+AIwS+59P406N 9rB7buDbznQFnFp/ph7kcfdhC4tOgfCxxXcVbFL0K4olLe3+0vC1jdgRvDX2fpl9 MdDaSajk4MAYc/ChXr93W55FXwsWscyCsFi5/DiIon2DphP5nCvT/jDaIESwPkeJ Fb5vHBzcmhGGDhq0sSaWcNtADYPCyEuzH0TEd8EWbgmtyB2Tfm/t7MxNn0bwuaD2 /pNyhRJTcaZGJ0L9+8Zzv+HTpl5TbLeTkx61FBy8Zg6TCPkcNUKNVFPfDN5MZmFU os1/P34mLW8M1Xs9PG3L+lI8a9RyMbStfqLU7mbC0/lNzvkWfw6oLxnn48/TUcib q8ylszDGvlx6H09CFTUMH/RHw4zIFmKICWHkBfSvjePyJCloPOc= =POTE -END PGP SIGNATURE-
Accepted pysha3 1.0.2-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 25 Oct 2019 22:48:30 +1100 Source: pysha3 Architecture: source Version: 1.0.2-3 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 937534 Changes: pysha3 (1.0.2-3) unstable; urgency=medium . [ Ben Finney ] . * Upload to “unstable”. * Declare conformance to “Standards-Version: 4.4.1”. * Specify VCS URLs for current Debian package VCS hosting. * Specify HTTPS URL for copyright format. * Grant license in Debian package under condition of GPL-3+. * Separate architecture-dependent build dependencies to “Build-Depends-Arch”. * Use a null command for ‘clean’ during ‘Git-BuildPackage’. * Declare Debhelper compatibility level 12. * debian/compat: * Remove obsolescent configuration file. * Record upstream metadata in DEP-12 document. * Remove obsolete control field for Python 2 version. * Remove declaration for minimum Python 3 version. Python >= 3.4 is now in all supported Debian releases. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. . [ Sandro Tosi ] . * Remove support for Python 2. Closes: bug#937534. Checksums-Sha1: 0dc281c4069ab660020bc92b894f7403d6b3721e 1996 pysha3_1.0.2-3.dsc fca2bdf07caa2eab069c10990ce4009b58112d3a pysha3_1.0.2-3.debian.tar.xz fb54db8a23d580fa12322e83240276b978703300 7812 pysha3_1.0.2-3_amd64.buildinfo Checksums-Sha256: dcfa31b4355683372fbba8883c25bfb02405435ea1e993a11effc113e2b301e8 1996 pysha3_1.0.2-3.dsc ddeb0fdbb68c52efdf6d288aef3e39cbab6ddc14c789b57f4ceac129c589beba pysha3_1.0.2-3.debian.tar.xz b8580b05de4cc0904af45e29125f739e82a68711fe78bc05dd0312fa8bdabaed 7812 pysha3_1.0.2-3_amd64.buildinfo Files: d8a4d9205d09bc3850bd369da253c7b8 1996 python optional pysha3_1.0.2-3.dsc 403565c72c4aa55684625548b1cff0bd python optional pysha3_1.0.2-3.debian.tar.xz eea88495e6159ea165c82b16edd3d639 7812 python optional pysha3_1.0.2-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdN8hqSSdpNPGgGg3kgn6QYDP/G8FAl2y4hwACgkQkgn6QYDP /G/1Kg//ZLMt65cNlqH+oV8UGGjGIlblDT6dicJtvjhXLHwzGP7/Jn8Z2TTJF8ZB dm6wilwY4oD3RRhJlSo8OnHCVqnmAD402qVYkgEg+/YX1EqU1fODbmDSliG/2T4A VVknIYYb7thUjHFrth4I147VBfxxlUZfajOQwHZriFt+oAcpvy1P/yR3sHxPAsag WYRP1r6mtuTA3t3+fZuNdZNjnmHGygsuAJ9MSPL3nITLl8+DaolnYIh3U9RohZj7 jxPko3O9NuoWy4pcx0+9Ss1WiD+8LdvRSTxvSdGYUSfOXGcZaCQMBg6dMEgP45KJ gP6Hf0LdddjtzkyOTUi0zdYDsEmDx7BXwUf+7tb3nAsEDKmMhU1ZWIlFpESCUx5T YKftyY0B2FeG70e9Jl34oMcjyVhFDjgUPyjlqkYcCYbMg6LwhRLMzbGMQZZ4YQn8 qQPWfu+rpLFRwXg0K1qMS8ahHRMEs9ayWJgoWV5OmChe0vnm17Zo2qXjqrNHdA5G Lma6O0kCLnxO9Zu+/iCaYidwBdJeTZG31483yZj05TMzU9ryc1R4ei3UcTLCRVkL +2wvxvkoZjpNQ25odZqFpbn9v/nV31kYvPe5JlEkkMp/Zc1He6soTZquzkul2vQ4 8hLyP5uF0YuupXJyk2SWTwwNw23KVEhH2kxGuVw5j7V4CvjFzYI= =BN1u -END PGP SIGNATURE-
Re: Survey results: git packaging practices / repository format
Sean Whitton writes: > I don't think the comment about quilt is unreasonable, because it seems > like you've just been lucky in not having to use quilt, or similar, yet. > "Never having a Debian delta" would seem to be a property of packages, > not workflows. There's some conflation here between “never had a need for additional tools like Quilt” with “never needing a Debian packaging delta”. I've never needed the former, and always needed the latter. I don't think the latter at all implies the former. -- \ “People demand freedom of speech to make up for the freedom of | `\ thought which they avoid.” —Soren Aabye Kierkegaard (1813–1855) | _o__) | Ben Finney
Re: Survey results: git packaging practices / repository format
Ian Jackson writes: > What should another Debian contributor do, who wants to make a change > to the upstream source, but wants to do so in your own git workflow > and collaborate via your git branch, rather than by uploading a .dsc ? I'm increasingly baffled here. Why does anyone need anything but the existing VCS tools (to work with upstream's VCS) and the DEP-3 patch format (to represent the changes in Debian packaging) for this? > I think they would need to use quilt[1]. Are we talking here about the “3.0 (quilt)” package source format? I don't consider that “using Quilt” because no maintainer of the package needs to even know what Quilt is, let alone use it, for that format to work. If someone finds Quilt makes the job easier, more power to them; but I don't see it as any kind of requirement in the workflow. Not even noteworthy in discussing the packaging workflow. > So that explains why your branch format is listed in that table as > requiring quilt. Unless there's something I'm missing here, I think that's just a false statement. -- \ “I have a large seashell collection, which I keep scattered on | `\the beaches all over the world. Maybe you've seen it.” —Steven | _o__) Wright | Ben Finney
Re: Survey results: git packaging practices / repository format
Russ Allbery writes: > Ben Finney writes: > > > It may be “bare debian” is meant to cover this; but I don't > > recognise the comment “requires use of quilt and similar tools” > > because I've never needed to use Quilt for this. > > How do you handle needed changes to the upstream source? * Use whatever VCS is published by upstream, to implement the change. * Preferably do this in a local fork, because: * Rebase the branch as necessary while the change is not yet merged upstream. * Export that change as a series of patches. * Those patches become DEP-3 files in ‘debian/patches/’ of the Debian package. So the VCS tools themselves, and the DEP-3 format, completely (?) obviate the need for any human to touch Quilt. > Or do you just never make any changes to the upstream source? We are rarely that lucky! Changes to upstream are very often needed. That's a good reason to maintain a local clone of the upstream VCS repository. And with a good Distributed VCS (like Git) resolving divergent upstream development while you wait for them to (if ever) accept the changes upstream, patches are relatively easy to keep clean. -- \ “Oh, I realize it's a penny here and a penny there, but look at | `\ me: I've worked myself up from nothing to a state of extreme | _o__) poverty.” —Groucho Marx | Ben Finney
Re: dgit advocacy again (Re: Survey results: git packaging practices / repository format)
Ian Jackson writes: > I have said before that I think using "dgit push" (where possible) is > an ethical imperative. (I should clarify that I *don't* mean that > people who aren't using "dgit push" yet are bad people. Life is so > full of ethical imperatives that no real human could meet them all, > and of course Debian's right to call on volunteer effort is limited.) Perhaps “ethical imperative” isn't what you mean, then? I understand an ethical imperative to be instruction demanded ethically (e.g. “don't trade people as property”). If one fails to dobey an ethical imperative, one *is* necessarily a bad person. Certainly I hope you don't consider that anyone who chooses not to use ‘dgit’ is thereby an ethical villain; and so I hope you'll avoid the term “ethical imperative” for your instruction there. Your meaning seems better expressed by an “ethical virtue”; some instruction (e.g. “donate time at a homeless shelter”) which when a person follows it makes that person praiseworthy, but which we do not condemn every person who fails to follow it. -- \ “I have never made but one prayer to God, a very short one: ‘O | `\ Lord, make my enemies ridiculous!’ And God granted it.” | _o__) —Voltaire | Ben Finney
Re: Survey results: git packaging practices / repository format
Ian Jackson writes: > Please let us know if we have missed one. It is probably better if > you ask us rather than just adding it, unless you're sure that what > you are adding isn't the same as one of the existing ones. In > particular it seems that "unapplied" is used by a large number of > people with disjoint tooling and disjoint terminology. I don't recognise the repository structure that was raised by myself and some others: A VCS repository that contains only the Debian packaging files, which at build time is then exported to a non-VCS working tree and moerged with the upstream source. It may be “bare debian” is meant to cover this; but I don't recognise the comment “requires use of quilt and similar tools” because I've never needed to use Quilt for this. > I hope you all won't mind too much that Sean and I have privileged our > own point of view, in the columns which contain value judgements, and > that we hope to retain that property of the page. The page admonishes that we not edit ithe “value judgement” fields; but the same page offers no clear alternative forum to achieve changes there. -- \“If you ever drop your keys into a river of molten lava, let | `\ 'em go, because, man, they're gone.” —Jack Handey | _o__) | Ben Finney
Re: Survey: git packaging practices / repository format
Ian Jackson writes: > Can you please look through the table below and see if I have covered > everything you do ? You have covered the workflows I set up where I have the choice. Thanks. -- \ “I am amazed, O Wall, that you have not collapsed and fallen, | `\since you must bear the tedious stupidities of so many | _o__) scrawlers.” —anonymous graffiti, Pompeii, 79 CE | Ben Finney
Re: Difficult Packaging Practices
Sam Hartman writes: > If you just want to get upstream's idea of their package onto a system > with their release schedule and their recommended dependency versions, > there are better ways than getting a package into Debian. In the Debian mentors forum (that is, the chat channel, the mailing list, etc.) we make a point of saying: that's fine! Not every package needs to be in Debian, for its users to install that package. Someone who wants what you describe above can learn how to make a Debian package that will only be side-loaded from that community's own repository, or whatever. Perhaps that needs to be stated louder or more consistently? -- \ “Truth is stranger than fiction, but it is because fiction is | `\ obliged to stick to possibilities, truth isn't.” —Mark Twain, | _o__) _Following the Equator_ | Ben Finney
Re: dgit FAQ
Sean Whitton writes: > This now exists: https://wiki.debian.org/DgitFAQ Thank you. One issue I noticed: git-buildpackage and git-dpm users are fully supported […] That seems to contradict earlier statements that “separate Debian-packaging-only repository” workflow (which is supported by Git-BuildPackage) is currently not supported by DGit. Is the DGit FAQ wrong on that point? -- \ “Pinky, are you pondering what I'm pondering?” “I think so, | `\ Brain, but if they called them ‘Sad Meals’, kids wouldn't buy | _o__)them!” —_Pinky and The Brain_ | Ben Finney
Re: Preferred git branch structure when upstream moves from tarballs to git
Ian Jackson writes: > So far I have gained the impression that the kind of people who are > using packaging-only git trees tend to be very conservative, and very > comfortable with .dsc/tarball/patch/quilt based tools, and not really > convinced of the usefulness of git. Let me counter that impression, then: I am well convinced of the usefulness of Git, both generally and for Debian packaging in particular. I use it every day for all manner of development work. What I remain unconvinced of is the worth of abandoning the clean separation between an upstream source repository (whether Git repository or not) and a VCS repository for Debian packaging (typically in Git). The worth of such a clean separation is that it does not run afoul of the often wide differences between upstream developer team workflow and Debian package maintainer team workflow. So it's not conservatism or unwillingness to learn, in my case at least. I don't see that there's sufficient benefit to be had trying to weld their work together into one Git repository, when we have existing tools and workflows that don't demand that conflation. I believe I've made an informed assessment of the benefits and costs of a combined-upstream-with-Debian-packaging single VCS repository, and tentatively rejected it. That choice is not irrevocable and I could be convinced by sufficient benefit, but AFAICT the costs remain what they are. > I have even experienced what feels to me like significant hostility. Yes, I've seen that at times. I'm sure you get more that I haven't seen. It's sad to see when it happens. > If I am wrong and there are more users to be had by implementing this > feature then I will definitely consider giving it a higher priority. I'll try to find time to respond on the bug report you cited. > BTW, dgit is capitalised thus. Can't promise I'll remember that; as with DPut, it's easier to see the portmanteau term with distinct capitalisation, in my opinion. -- \ “Advertising is the price companies pay for being unoriginal.” | `\—Yves Béhar, _New York Times_ interview 2010-12-30 | _o__) | Ben Finney
Re: Preferred git branch structure when upstream moves from tarballs to git
Ian Jackson writes: > […] I have not taught dgit how to convert [separate Debian > packaging-only repository and upstream source repository] into a git > tree that contains the [combined] source code. One interpretation of “convert [separate repositories] into [one Git tree]” is that it's a flag-day, point of no return conversion that precludes the separate-Debian-packaging-repository workflow from that point forward. If so, that wouldn't be enough to convince me to use DGit, because I consider the separate-Debian-packaging-repository workflow superior for many cases. Contrariwise, on the assumption we are instead talking about a “conversion to a Git tree” that would seamlessly let DGit support the ongoing workflow of Debian packaging in a repository separate from any upstream code: > That feature would be the wishlist bug > #903392 "want support for packaging-only maintainer views" > which I've already mentioned once in this thread, where I explained > why implementing it is a low priority. While acknowledging you are under no obligation to implement features demanded by others, I'll point out that for as long as DGit lacks support for that workflow, you won't get much user feedback from people whose Debian packages need that workflow and therefore are not knowledgeable DGit users. So for as long as that persists, it will take special consious effort to remember that there's a class of Debian package maintainers who would like to become knowledgeable about DGit but can't yet; that the current DGit user base is not representative of that class of potential user. I trust you already know this, but it bears explicit expression from time to time :-) -- \ “Our task must be to free ourselves from our prison by widening | `\our circle of compassion to embrace all humanity and the whole | _o__) of nature in its beauty.” —Albert Einstein | Ben Finney
Re: Preferred git branch structure when upstream moves from tarballs to git
Sean Whitton writes: > Hello, > > On Tue 30 Apr 2019 at 08:05AM +02, Ansgar wrote: > > > As an example: to update to a new upstream release, I ideally just > > have to drop the new upstream tarball, update d/changelog and am > > done. > > As a package maintainer, if you don't keep the whole source package in > git, you're giving up on a lot of the power of git. I can't speak for Ansgar, but “you don't keep the whole source package in Git” is not implied by keeping Debian packaging separate. It's not accurate to the workflow, at least as I described (I don't know Ansgar's case, but nothing he described implies that either). Rather, I keep the Debian packaging source separate from the upstream source. That doesn't preclude Git access to the upstream source, and I frequently use a Git repository cloned from upstream for that. So, the Debian-packaging-in-a-separate-repository does not give up any of the power of Git. > The most significant thing is that you cannot manipulate quilt patches > as commits on a branch. It is also much more involved to cherry pick > commits from upstream branches, and quickly obtain diffs between > Debian's version of the code and arbitrary other branches, to mention > a few other things. The full power of Git is available when I manipulate upstream source to refresh my Debian patches. Indeed, it's even neater to refresh those patches by going straight from the only-upstream-source repository. > I also think that you're doing a disservice to downstream users. If > you're trying to fix a bug in the packaged version of some software on > your computer, you don't care about the distinction between Debian's > packaging scripts and the upstream code. It's all going to be turned > into a .deb once you've fixed your problem. You want the history of > the whole thing. Thus, a git history that contains both the upstream > git history and the Debian maintainer's changes to the packaging > scripts is going to be very useful. A git history of only the Debian > packaging scripts is much less useful. Conversely, I think it does a disservice to downstream users to mix in Debian packaging changes with upstream changes. The separation is useful and much easier to maintain when the repositories are separate. -- \ “Time is the great legalizer, even in the field of morals.” | `\ —Henry L. Mencken | _o__) | Ben Finney
Re: Preferred git branch structure when upstream moves from tarballs to git
Gard Spreemann writes: > Recently, upstream has finally started using git. What is the > recommended way for me to maintain a sane branch structure for the > packaging repository while starting to use upstream's git master as > the upstream branch to follow? My opinionated recommendation: Track the Debian packaging in a separate repository (which contains only the ‘debian/’ directory tree). When it's time to build the Debian source package for testing, export the upstream source to a temporary build directory and export the Debian packaging onto that. Build the Debian source package from the result. (Of course, Git-BuildPackage supports this workflow, with the ‘--export’ and related options.) Insulation from the kind of changes in upstream publishing that you describe, is a significant advantage of this Debian packaging workflow. -- \ “My girlfriend has a queen sized bed; I have a court jester | `\ sized bed. It's red and green and has bells on it, and the ends | _o__) curl up.” —Steven Wright | Ben Finney
Bug#927454: ITP: towncrier -- compiler for project news file
Package: wnpp Owner: Ben Finney Severity: wishlist * Package name: towncrier Version : 19.2.0 Upstream Author : Amber Brown and Contributors * URL or Web page : https://pypi.org/project/towncrier/ * License : Expat Description : compiler for project news file Towncrier is a utility to produce useful, summarised news files for your project. Rather than reading the VCS history as some newer tools do, or having one single file which developers all write to, towncrier reads “news fragments” which contain information *useful to end users*. . towncrier delivers the news which is convenient to those that hear it, not those that write it. . That is, a “news fragment” (a small file containing just enough information to be useful to end users) can be written that summarises what has changed from the “developer log” (which may contain complex information about the original issue, how it was fixed, who authored the fix, and who reviewed the fix). By compiling a collection of these fragments, towncrier can produce a digest of the changes which is valuable to those who may wish to use the software. -- \ “Often, the surest way to convey misinformation is to tell the | `\ strict truth.” —Mark Twain, _Following the Equator_ | _o__) | Ben Finney signature.asc Description: PGP signature
Bug#927453: ITP: towncrier -- compiler for project news file
Package: wnpp Owner: Ben Finney Severity: wishlist * Package name: towncrier Version : 19.2.0 Upstream Author : Amber Brown and Contributors * URL or Web page : https://pypi.org/project/towncrier/ * License : Expat Description : compiler for project news file Towncrier is a utility to produce useful, summarised news files for your project. Rather than reading the VCS history as some newer tools do, or having one single file which developers all write to, towncrier reads “news fragments” which contain information *useful to end users*. . towncrier delivers the news which is convenient to those that hear it, not those that write it. . That is, a “news fragment” (a small file containing just enough information to be useful to end users) can be written that summarises what has changed from the “developer log” (which may contain complex information about the original issue, how it was fixed, who authored the fix, and who reviewed the fix). By compiling a collection of these fragments, towncrier can produce a digest of the changes which is valuable to those who may wish to use the software. -- \ “Often, the surest way to convey misinformation is to tell the | `\ strict truth.” —Mark Twain, _Following the Equator_ | _o__) | Ben Finney
Re: [Idea] Debian User Repository? (Not simply mimicing AUR)
Vincent Bernat writes: > ❦ 8 avril 2019 14:46 +10, Ben Finney : > > >> yes, it can be done, but it is a lot more work for individual > >> packagers. > > > > Sure. And, on the other hand, providing an APT repository for arbitrary > > packages of unknown copyright status is also a lot of work to expect > > disinterested volunteers to do without motivation. > > Disinterested volunteers are never forced to work for Debian. Yes, that's why I said “expect” and not “force”. > What is the point of being so negative? Not sure who you're addressing here, and I'm sorry if the discussion appears negative to you. -- \ “When I get real bored, I like to drive downtown and get a | `\ great parking spot, then sit in my car and count how many | _o__) people ask me if I'm leaving.” —Steven Wright | Ben Finney
Re: [Idea] Debian User Repository? (Not simply mimicing AUR)
Ben Finney writes: > Peter Silva writes: > > > With debian, it's kind of all or nothing. Etiher you're in Debian, > > and it gets built on every platform using the build farm, or it's > > not, so you get no help at all. > > That doesn't seem accurate. Have people tried setting up an APT > repository and got “no help at all”? Does the maintenance of the > packages to run an APT repository, and instructions on how to do it, not > count as help in doing that? As for the build farm: the parties who donate those to Debian did so on the understanding that they took on the load of building only the official Debian archive. Opening the gates to even unofficial Debian packages would be a significant increase in that burden on many of those donated machines. I think it's good to keep the distinction between official Debian archive (which is built on the official Debian build farm) versus unofficial packages (which need someone else with their own reasons to donate resources to build them). -- \ “The generation of random numbers is too important to be left | `\to chance.” —Robert R. Coveyou | _o__) | Ben Finney
Re: [Idea] Debian User Repository? (Not simply mimicing AUR)
Peter Silva writes: > On Sun, Apr 7, 2019 at 11:10 PM Ben Finney wrote: > > > If one needs to keep a close eye on changes to make sure they can > > still be installed even on a years-old OS, the resulting packages > > can be placed in a custom repository set up with the instructions at > > https://wiki.debian.org/DebianRepository/Setup>. What am I > > missing? > yes, it can be done, but it is a lot more work for individual > packagers. Sure. And, on the other hand, providing an APT repository for arbitrary packages of unknown copyright status is also a lot of work to expect disinterested volunteers to do without motivation. So it sounds like you know of at least enough individual developers that you have a group motivated to maintain an unofficial APT repository. That seems like an appropriate model: groups who want to make unofficial packages available can put in the sys-admin effort to run an unofficial APT repository with the existing tools. The Debian project does not (and, I believe, should not) need to be the home of third-party unofficial repositories; the tools to provide those are already in the hands of anyone who wants to provide them. > With debian, it's kind of all or nothing. Etiher you're in Debian, and > it gets built on every platform using the build farm, or it's not, so > you get no help at all. That doesn't seem accurate. Have people tried setting up an APT repository and got “no help at all”? Does the maintenance of the packages to run an APT repository, and instructions on how to do it, not count as help in doing that? > Launchpad gives a nice middle road that suits us right now, > and if something similar were available for debian, it would provide a > stepping stone to being in Debian proper. Conversely, I would argue that providing an APT repository for the unofficial packages they want available is a way for grroups to, on their own steam, provide that stepping stone. -- \“Beware of bugs in the above code; I have only proved it | `\ correct, not tried it.” —Donald Knuth, 1977-03-29 | _o__) | Ben Finney
Re: [Idea] Debian User Repository? (Not simply mimicing AUR)
Peter Silva writes: > […] the launchpad.net model, which supports backporting seamlesslly > and allows to support the same version on all distro versions, works > better for us. This is something a debian version of launchpad would > get us. How does it handle “seamlessly” changes that make a package incompatible with the already-released Debian stable? If it doesn't handle that, is it right to call that seamless? If one needs to keep a close eye on changes to make sure they can still be installed even on a years-old OS, the resulting packages can be placed in a custom repository set up with the instructions at https://wiki.debian.org/DebianRepository/Setup>. What am I missing? -- \ “I think Western civilization is more enlightened precisely | `\ because we have learned how to ignore our religious leaders.” | _o__)—Bill Maher, 2003 | Ben Finney
Re: [Idea] Debian User Repository? (Not simply mimicing AUR)
Peter Silva writes: > One thing that dampens our enthusiasm for that at the moment is that > our packages are still very unstable […], but if it gets baked into > debian, then we need to support some random old version for many > years. By that description it is not a good candidate for putting into Debian the operating system. If the upstream project is not going to support specific releases for years, that puts the onus on Debian package maintainers to choose a version for support during the lifetime of a Debian release. So would you agree, then, that the barrier to entry to the Debian system is appropriate in this case? -- \ “I don't want to live peacefully with difficult realities, and | `\ I see no virtue in savoring excuses for avoiding a search for | _o__)real answers.” —Paul Z. Myers, 2009-09-12 | Ben Finney
Accepted gandi-cli 1.4-2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Apr 2019 16:26:36 +1100 Source: gandi-cli Binary: gandi-cli Architecture: source all Version: 1.4-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Description: gandi-cli - command-line interface for Gandi service Changes: gandi-cli (1.4-2) unstable; urgency=medium . [ Unit 193 ] * Build package for all Python 3 versions in Debian. * Restrict ‘click’ dependencies to match upstream package. * Install upstream's script for Bash command completion. Checksums-Sha1: 4016f3cdafa705bacfdd8ed709176b02a35e6784 2024 gandi-cli_1.4-2.dsc 21d4f631c8d5968a53c092095c6aeb9681f12161 5316 gandi-cli_1.4-2.debian.tar.xz 4ad05cc4365922dc33c846e3e287578b5219fef3 114580 gandi-cli_1.4-2_all.deb ecdcc249f827649eecf05e47a169d2f0a5a45b3c 6347 gandi-cli_1.4-2_amd64.buildinfo Checksums-Sha256: 2852ab9f1375d4c28286913691a05e938796ebf9d40bdb8dbfa2f1ab83a064a5 2024 gandi-cli_1.4-2.dsc 5c0b4cae60dc91d59d261621d84f499adfd2001c8c91c1bae1f5531cc3a735c1 5316 gandi-cli_1.4-2.debian.tar.xz 2422067a578567414f93babb88e01f9ebc300892b058c70e51191714dc198454 114580 gandi-cli_1.4-2_all.deb 4c31cab44dcd2bfe130e3e1c4651ee60758ea46d5bb8034dfa0e913c796f2700 6347 gandi-cli_1.4-2_amd64.buildinfo Files: 9411abbc0a40d2796c2a8a53d81d2218 2024 utils optional gandi-cli_1.4-2.dsc e35cec77ec31e7adf9ac2a553439fba2 5316 utils optional gandi-cli_1.4-2.debian.tar.xz a29a71ff4191d055ceede6a8ed365895 114580 utils optional gandi-cli_1.4-2_all.deb 19e51a02f63c7e9962260b313b69fa38 6347 utils optional gandi-cli_1.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEUXzxS7LzmLDLNUhVuLJMBqwShAUFAlykVBwACgkQuLJMBqwS hAWIchAAhE1f5KSxQ5UcnftlvzrSwrhLfd/BOodm8N79ZJzeBqdYIBsc8CG4WsU9 hKKOui6bamyzMTjT2ESIpVkanKnWyVBLAsBENmIm8DoCABm33kC2EwOAOaSyp42k mnYl8F8cGzQOjwd6YuCjfEcQsreP/eGH2G6b4L8iOHfIW438dA0BeHRbuyaqmY4m tqKDb5yqAr2l3537sLybzdYc2Db5Y5oKQ5ehEgk7qisyWLjShCt+N68Pn6wPY/ud 6wQvLW8LRMvCFg0U2lnnFKYhkTYgwzsWG0BAyqmm/36r5lIPzpZBed/byQshE6vW oxYXPR+ShaJB0jZo+tMpQq09BfK88KnInNHXtGXl8jethCVw4J1MOR4Hja+U8dmj tomuMxx0w6yA2EkGfrhXdcbeM3IY/jMIcwgdzyQZhymLqNgII3h9WqppYwKkyO8v FSKZ/nwk/UzxI40e4v0Xnn1/qV2clSFNCNfICMJJjM1IPBuvyurIyAP9fRp7kzCQ F980XuXH3npDMmvuf1xG/nYoDe14OAUM1wOt/JsPOra3WtnW5WVbkCkClCXKvCPX jXobz0qHqxbFG+zyPPKWfyk/dUI5j0JUL9YQlVrLahoB5jz4LbVIAuEZd3No+b12 fHUBEZE4Z4vXJQ/p6Rg9eT43bX5QwXd0B8KJ0oY2xO7j3PCXQ4Y= =cggf -END PGP SIGNATURE-
Accepted editorconfig-core-py 0.12.2-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 08 Mar 2019 21:08:28 +1100 Source: editorconfig-core-py Binary: python-editorconfig python3-editorconfig Architecture: source all Version: 0.12.2-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Description: python-editorconfig - library for working with EditorConfig — Python 2 python3-editorconfig - library for working with EditorConfig — Python 3 Changes: editorconfig-core-py (0.12.2-1) unstable; urgency=medium . [ Ben Finney ] * New upstream version. Highlights since previous release: * Support Python 3 up to 3.6. * Clarify aggregate license is PSF license conditions. * Update publication years in copyright notices. * Update copyright information for upstream license changes. * Correct the Git-BuildPackage configuration for this packaging style. * Use a null command for ‘clean’ during Git-BuildPackage. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Declare “Standards-Version: 4.3.0”. No additional changes required. * Record upstream metadata in DEP-12 document. * Remove custom Debian source compression option. * Declare Debhelper compatibility level 12. * debian/compat: * Remove obsolescent configuration file. . [ Ondřej Nový ] * Remove specification of minimum Python versions. The required versions are now in all supported Debian releases. * Use HTTPS URL for PyPI redirector. Checksums-Sha1: 268ed04f08ea09829d2c18b368649fb9c081f9a4 2257 editorconfig-core-py_0.12.2-1.dsc 2a382d04ee96250215907ce51a3673702aa3f283 13485 editorconfig-core-py_0.12.2.orig.tar.gz 75fcd3aa5ad2f94b770eadf89616c1b8e734c444 8948 editorconfig-core-py_0.12.2-1.debian.tar.xz a00beff84f480020eb6a27dfaf5d30e7bf4a2e00 6765 editorconfig-core-py_0.12.2-1_amd64.buildinfo b548df348c99791ba30c233f94bf008c32ce082c 13780 python-editorconfig_0.12.2-1_all.deb 2a4f30523521e50b80a697c0e7cb14f2998b74cf 13848 python3-editorconfig_0.12.2-1_all.deb Checksums-Sha256: b480324e7b58e927d03ede9f00fcc1837833edb66e1012fbba8b5ed30b57392e 2257 editorconfig-core-py_0.12.2-1.dsc 1b0ef345f9c3a673e492cfe608ed644b236139f7fceab5c6f513a71bcaf8a56c 13485 editorconfig-core-py_0.12.2.orig.tar.gz e4a33fedb2ead48bb648b360537444a4ace5eae270c9fb748b4618d188a605e1 8948 editorconfig-core-py_0.12.2-1.debian.tar.xz 63a69c1b123cbda19268bf873bdb91f26bc0cb51b276d496f659ac9649511fa8 6765 editorconfig-core-py_0.12.2-1_amd64.buildinfo f9313ae11fb51618b5c3901889342604771d0a48b572027050ba7e4a0152be0a 13780 python-editorconfig_0.12.2-1_all.deb d7c5979ca822830e97fc1629c97c009302343ab119a246f29c1fcbb48c9a4d43 13848 python3-editorconfig_0.12.2-1_all.deb Files: fe4773a944ff7c712485aa851d3b5492 2257 python optional editorconfig-core-py_0.12.2-1.dsc 12671d6fbadb20f3b1474d9d32b7fb43 13485 python optional editorconfig-core-py_0.12.2.orig.tar.gz 6d8d14139a20c44b9ddd339c54599a57 8948 python optional editorconfig-core-py_0.12.2-1.debian.tar.xz f01e2491f2328736bbafd692fd01b002 6765 python optional editorconfig-core-py_0.12.2-1_amd64.buildinfo 0a478df5edeb45e34f8411cf12c4efcf 13780 python optional python-editorconfig_0.12.2-1_all.deb 266fb86bafee7603b7ffad8a6e4b82ad 13848 python optional python3-editorconfig_0.12.2-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEUXzxS7LzmLDLNUhVuLJMBqwShAUFAlyEYRwACgkQuLJMBqwS hAXpCQ/6Aitneqou/9HGZbDEcNzi6XnbXivLAicRL57gYmFAPJQbunjhi94EC0XR czk2h166w4SyRyrfrkskawx2OKZX9klYk3j8mGagfD+T7A+SW1ihodrdRral8Zb8 NlgZEkE+09zLICx8QbwGajHbjHRTj6J4CoT4u6lYt+mrRUpO4H3TliqvwLQ/iSAX h62uk+6m0+KTVnUbzX+EUZsH3Rq0OdgV1bWjT+ejykgytjy9LfiV9PJlTPQmsW74 anZogjwPJDYu6Zcu50AndMSMSREI5pVx7FjXFV9XyqJ5p9XyZ5yOH/PqmJv/4MTU vg+M7vDyJl3o5wNBQr0H/uCL7AWsx1Mr8SAvoqITxo1qxdvOFh6N9IAPUlJh3jdd tNrVvoWTcEsbSM8KMApLgfkhuEY7iDjkK0rzMS7bMh12bNXWdsQRiW1u/v/8ylMk 2Q+1yLG0q1nQzKiFwSTONYuYACY3SI8hydcDYG44QdgPXo9tXY6B/jRObFa76P9L 6msbcrT+UiNhZuDdGiBkKsfnwRG6QeX2o2CB88DlNAcckJfqSczSmC6gr6XZOkyw wrpJVPyzDjjd4K006/vG3Ie528qY7DSFwCkA30ZG0aeYj1cWULNiJUXRidUo+9zC Kds/O1Jhwy6BQD2qhwj7+Z+ezS/QMA0CmSfCyT1zgaYEvtYc7sc= =kUe4 -END PGP SIGNATURE-
Accepted gandi-cli 1.4-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 16 Feb 2019 14:47:39 +1100 Source: gandi-cli Binary: gandi-cli Architecture: source all Version: 1.4-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Description: gandi-cli - command-line interface for Gandi service Changes: gandi-cli (1.4-1) unstable; urgency=medium . * The “Cristian Rossi” release. . [ Ben Finney ] * New upstream version. Highlights since previous release: * Add support of Python 3.7. * Drop support of Python <= 2.6 and Python <= 3.3. * Add support of DNSSEC. * Declare “Standards-Version: 4.3.0”. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Declare to PyBuild the main Python package name. * Remove specification of minimum Python versions. The required versions are now in all supported Debian releases. * Use a null command for ‘clean’ during ‘Git-BuildPackage’. * Update publication years in Debian packaging copyright notices. * Refine README.source to describe current packaging source maintenance. * Record upstream metadata in DEP-12 document. * Specify that build dependencies are architecture-independent. * Declare Debhelper compatibility level 12. * debian/compat: * Migrate Debhelper compatibility level declaration to build dependency. * Declare binary package dependencies explicitly. . [ Ondřej Nový ] * Remove specification of minimum Python versions. The required versions are now in all supported Debian releases. Checksums-Sha1: d788286f2e54aaa1fce7c55ab1fd70adcf613fbc 1994 gandi-cli_1.4-1.dsc 739dc18981809088797095a846a9611d7898c300 179273 gandi-cli_1.4.orig.tar.gz 2262cc91b6f2e468677bd127af3282dacef52bd8 5172 gandi-cli_1.4-1.debian.tar.xz 0f079ccb341c80d1048f2fdabf3fb8278f537327 113924 gandi-cli_1.4-1_all.deb 337ddca66af42501fe47213f95e1bbf131f6a9be 6306 gandi-cli_1.4-1_amd64.buildinfo Checksums-Sha256: bb7c6692175f87cdf54ffd21f9ef92166f2543bedf6059fc03f20ddd714327b8 1994 gandi-cli_1.4-1.dsc 93abd2f47f1d89186bba5d28d3b02d43cea0e231b564c869f836a5796d59dbd1 179273 gandi-cli_1.4.orig.tar.gz e3bbde3fb98f60b89b9e485c3b3a7ca799de7946e9526f7d77517aaa71962646 5172 gandi-cli_1.4-1.debian.tar.xz 1cac10d11b0d083a724a60cb33b29176031e8e2591245c181ebfd6f4e1b582be 113924 gandi-cli_1.4-1_all.deb c3f21cd04b50fc55d57b84ee5bd1f7ca090bbae531373fbbea647e794cb08f09 6306 gandi-cli_1.4-1_amd64.buildinfo Files: e9bea65fbfd0829253886d2f35b47464 1994 utils optional gandi-cli_1.4-1.dsc dbb7f192a8fa2ae9a9dcc28c6d7bb586 179273 utils optional gandi-cli_1.4.orig.tar.gz 24429da84d518ea0f7de9325daaca967 5172 utils optional gandi-cli_1.4-1.debian.tar.xz 13526d126ab4869b33ede2707ef59b99 113924 utils optional gandi-cli_1.4-1_all.deb deda8a5ae71878bfa51e89eb9751f41f 6306 utils optional gandi-cli_1.4-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEUXzxS7LzmLDLNUhVuLJMBqwShAUFAlxnkBcACgkQuLJMBqwS hAX01g/7Bf4AIugI5Xf5yGx0YyyChGhm8sKmq44KRcX0bKSl6f36rc4PdKVEW2IJ eGzHlcetLm2UOuHQYsc2a61koKP7R+5MYn1zYpK6wHMvBi7188m90/h5hLAX9x3p noGp5KwqzvdYIRwsN/CeXlvYu2NyUiAEwCD5Z9q9ump4G/TeToNklpirUwORBeNb u041H61zmMlR1UyQVDoU21ShhPDi74EOLZiROuAUbSBfQKL7ZpAoknO3JApPJK1Q sa63dGMwppzLP7fymqXUBmMe2FvZFOl0G++FJsUTTTxywmApi4YnW4M0Uuv+Heg6 1JBH+CtjsbjiDRuBKplfE/PTx0zVnu4oh+dpQuScKq2U2Vy3QAH5AmWsFWEQqXNo oaoy3BRYbGN9J9nqWzV2iS5mCh8+IeEck7DYc5CUVpmw5khQvVHfElzKXPz0Xwz4 mtBZilZfzHmNka8jwXn/gksaCd6RrrSycbL7k2jqkYf46lpXAdO24qHRmUkfnZM8 +sdF2iH9BKCIUWzRO+oDzdRwyT1vlvYI07uSq/T7A9UdEPc2ZT2r5+znkASdUN+g bkngyy7ZBYGTFDZ/2X8KiV+FI13tPi1DnLVcFggIpDhNkCz+86VHBqda1Y/RPGRv 6/4nVEE9GBru8j790KmpiCAFMHoopfDfzj2AoLWhutJblX/R5Yk= =uchS -END PGP SIGNATURE-
Accepted inform6-library 6.12.2+dfsg.1-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 Feb 2019 18:52:05 +1100 Source: inform6-library Binary: inform6-library Architecture: source all Version: 6.12.2+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Description: inform6-library - Inform 6 interactive fiction language — standard library Closes: 826899 Changes: inform6-library (6.12.2+dfsg.1-1) unstable; urgency=medium . * The “Humayun Azad” release. * New upstream version. Highlights since previous release: * Project repository moved to GitLab hosting. * Numerous bugs fixed. Closes: bug#826899. * Update copyright information. * Update my email address for Debian work. * Declare “Standards-Version: 4.3.0”. * Specify current VCS for Debian packaging work. * Declare Debhelper compatibility level 12. * debian/compat: * Remove obsolescent configuration file. * Remove special handling for version-specific changelog. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Specify current HTTPS URL for copyright format declaration. * Specify current HTTPS URL for upstream source. * Specify how to create source package with Debian packaging overlay. * Configure UScan to poll current upstream project repository. * Record upstream metadata in a DEP-12 format document. Checksums-Sha1: df51c27f5c87ec0ae6fdd0c56bc6b2d9a543497f 1975 inform6-library_6.12.2+dfsg.1-1.dsc 5e4aeda5cf4baaa9edb1d77b5c95a087858e1ec3 128212 inform6-library_6.12.2+dfsg.1.orig.tar.gz 1ca66ec68df2db5d8108980d8fa0019da4c32892 8956 inform6-library_6.12.2+dfsg.1-1.debian.tar.xz d6a43da9faf0224c44e268eb939686d4644cf0db 112360 inform6-library_6.12.2+dfsg.1-1_all.deb d0b3c2281002367752648197820e88784b34b75d 5534 inform6-library_6.12.2+dfsg.1-1_amd64.buildinfo Checksums-Sha256: 0c0e4bd931a6a744b9c30770d9f68c665a1e1acc47f07e2a07631e9949c34e77 1975 inform6-library_6.12.2+dfsg.1-1.dsc cc1ab954b4690b308bc803905eb215ac8e278807541b7759f0ede4fbdb955327 128212 inform6-library_6.12.2+dfsg.1.orig.tar.gz a20f2882ef90c37380912d49d894af8c4840c5f3f25f34def704be05e645f977 8956 inform6-library_6.12.2+dfsg.1-1.debian.tar.xz b358e864007a2b0be60e6ed0f1be41ea6a9404c5481da63bc06398a524094533 112360 inform6-library_6.12.2+dfsg.1-1_all.deb b2822f928e831b7edeceaaf24d93dc8b419cff0f627aad3cd2c6ea9988cb4c7a 5534 inform6-library_6.12.2+dfsg.1-1_amd64.buildinfo Files: 64a6bc89796479a199462e1e19860077 1975 devel optional inform6-library_6.12.2+dfsg.1-1.dsc ed5aa8b52e9f50ba4bb734d0d1483828 128212 devel optional inform6-library_6.12.2+dfsg.1.orig.tar.gz f47709f338738b4083a6f6adfa9f6f13 8956 devel optional inform6-library_6.12.2+dfsg.1-1.debian.tar.xz 36835c4451d660641a0e3199137a6811 112360 devel optional inform6-library_6.12.2+dfsg.1-1_all.deb db2891577858471285662836e3305ed9 5534 devel optional inform6-library_6.12.2+dfsg.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEUXzxS7LzmLDLNUhVuLJMBqwShAUFAlxWnugACgkQuLJMBqwS hAVYFg//ZT1NAQp7WQLe+wSoGEoq6BS9JHmXkIPVVqi+vPyTd3RN/78FSHex1/9K AwUWSTcREsV7fostdHktJVlT+1X4jq2MX55JOymHc91LyWRbRofhK8st72Vvp3kC Q3n0NJ/oHk0VB0JcyQ/SCbVSUp1gLOdrp6/1vDSa2gZIEERD7O+ha9B4Jq7TKkmr hthrzau0s0Qp3SvnuBC80r8uixz+ZmnDvv0QnAkI1OgY2Volbkuwjq9caDq+3Z5x Ygc6OQkwDsh3lr75ULdzQOwjl/L4ecPR0LepMO6prRzf7Xe/z7fOHmioert692SF OR70rN0quHkzyczpELQNa5fgt1yLqeJtS55OvMApLS/78mwai349Fk+PCyUd0dj3 uELm05xfAwk9KR6M0RG4uvGT3BlVkn5oYxUj0oIEvb1Am0+pNg2gqXi4AFMAXwT/ jHmXUJvybcXKLu50gVwvCWsQi2HGMavKI8vc3GnHAUf/kmt6Q7uqKhnzRUpJl2SB Uo2v9RlL0Bec1KTEx18DBD8KLbezP+Cd2ZFt6g/Er4QwP5eQ8QdQaS/qFKB6y2zq CTDUoETJm6acVblfd/wSZAWN4RZXdF9kqzO5KizBxVaIpE123z8fj8TOMSW8SnLm TWONOJTUw5rQXzy5GMGsqyBxE7XnGwq5Q7jJXgCqsgnmacVH+Aw= =kEnU -END PGP SIGNATURE-
Accepted dput 1.0.3 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 25 Jan 2019 22:06:32 +1100 Source: dput Binary: dput Architecture: source all Version: 1.0.3 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Description: dput - Debian package upload tool Changes: dput (1.0.3) unstable; urgency=medium . * The “سعد راشد محمد الفقيه (Sa'ad Rashed Mohammad al-Faqih)” release. . [ Ben Finney ] * Specify current VCS for this code base. * Declare “Standards-Version: 4.3.0”. No additional changes needed. * Declare Debhelper compatibility level 12. * debian/compat: * Remove obsolescent configuration file. * Update publication years in copyright notices. . [ Ondřej Nový ] * Remove specification of minimum Python versions. The required versions are now in all supported Debian releases. Checksums-Sha1: b2b23cc9aab190657958274b7e3b107f6b7d1089 1751 dput_1.0.3.dsc 32be7c2bea67107ffe5dac04dbed0d851a9da3ad 103652 dput_1.0.3.tar.xz 30aa8dae0b225708ed9a1ac5c635c2767917d225 54464 dput_1.0.3_all.deb 23cc923522b3997f80549b337435eb99bede37b0 7249 dput_1.0.3_amd64.buildinfo Checksums-Sha256: 9905e67996b900db43346436091fd551cab6d28d263fbd448ec52db5885ab9ac 1751 dput_1.0.3.dsc 981455c6403132e050917d55baf93e54ea77c9f89f96982ecf446a88dafc3bbf 103652 dput_1.0.3.tar.xz 2cb5ba392ae890322f6eed52d97f76a3c3c47ea100478e2b486ec8b58f6269bf 54464 dput_1.0.3_all.deb 0b53ed0a4e0ce143d80dd2b786b2bf03c45cf1006b1e54acef53ce7601e1bcd8 7249 dput_1.0.3_amd64.buildinfo Files: 6d0f29cc581335a55c60a2df88e27b1b 1751 devel optional dput_1.0.3.dsc bf525a37ac4bfe1851584d7b843717ec 103652 devel optional dput_1.0.3.tar.xz 020a6e5bd011a4af7fd7c09a342613d2 54464 devel optional dput_1.0.3_all.deb f460a3b674dbbab9809c25735b84bcb1 7249 devel optional dput_1.0.3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEUXzxS7LzmLDLNUhVuLJMBqwShAUFAlxK8V4ACgkQuLJMBqwS hAXoBg//aRzT5M3sHiw27dm+LD6KUwYYoxb/wKzAea2fua+R13OieqsrLMLHhVr5 5XJLqieEKxLT5nTf7dS2WRB5dk8ozF20z4YNcobPnJyplinVgOu950agiS9WTJK8 InTm+H0rdNkqinAR/V3facjBqtDic/YF1iiYkhxS1NYUl1s3QtgGtBO4t+UdpcT9 0mw7b6/q3aJLz4cHVTQhRz5N0qhd712eGcgMDPj/kNP+yeTGzk5iRkv2xM44oqY7 nmcmAIBJWI5wEPscCfQjhgeZneHupVnWBpR56Uyc31wGyTPR/mqP9ScsoB3DtHUy KReKnEWa0B9RKX0TSx4cNUmR7rYeUyOJfDCJbLIoIjGYw4i0oIrrQ/WHV4D/kTQp rQYzi6V5LMG9y9VNMbSuaJXlnNnzTJ0DPB/htOLWz0dt78umWfObqz6bhWxK6wxC UJXtP7i1202rN60xdJcJjDlkH07sCcuXC0IKWTqdBFOW6jfOy0Jr4GR5iliQt99N 5Nojlp0JRkL1kOuNF09KZiOylZfEmGGya6Doze9aSgtulhdq6MXYnVdWameLqvbM cfapIUsmAd9UiQWTacxu/OJMcZWvJssfETjB9NxGWJ9o09xfwdQTNT1yXYTS/FG6 PU2yYOzIdhqTp5uzdpPPCgGg/YvdaHXEZ0c4rnFMpPNd4mp6U/A= =L/YH -END PGP SIGNATURE-
Accepted python-coverage 4.5.2+dfsg.1-1 (source all amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 25 Jan 2019 11:58:58 +1100 Source: python-coverage Binary: pypy-coverage python-coverage python-coverage-dbgsym python-coverage-doc python3-coverage python3-coverage-dbgsym Architecture: source all amd64 Version: 4.5.2+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Description: pypy-coverage - code coverage tool for Python 2 PyPy python-coverage - code coverage tool for Python 2 python-coverage-doc - code coverage tool for Python — documentation python3-coverage - code coverage tool for Python 3 Closes: 915133 Changes: python-coverage (4.5.2+dfsg.1-1) unstable; urgency=medium . * The “وليد أبوالخير (Waleed Sami Abulkhair)” release. * New upstream version. Highlights since previous release: * Upstream development hosting moved. * Namespace packages are supported on Python 3.7, where they used to cause TypeErrors about path being None. * Extend supported Python versions to include Python 3.8. * Update publication years for Debian packaging in copyright notices. * Update package source documentation for standard packaging tools. * debian/repack, debian/source_package_build.bash: * Remove unused custom ‘repack’ program. * Declare AutoPkgTest dependency on all relevant CPython packages. Closes: bug#915133. Thanks to Paul Gevers for the report. * Update Lintian override for new Python-version-specific filenames. * Declare “Standards-Version: 4.3.0”. No additional changes required. * Record upstream metadata in DEP-12 document. Checksums-Sha1: c9a835808de047b2820615e1d7b03cf2406c7fb2 2549 python-coverage_4.5.2+dfsg.1-1.dsc 6d89845c11cc73395b6c9d9022a66b34e95d4fe1 269064 python-coverage_4.5.2+dfsg.1.orig.tar.xz 1eabb653e76ca73ea3c605bd25586a55a52f070f 20784 python-coverage_4.5.2+dfsg.1-1.debian.tar.xz db613117c3b7ff1a746ca04a653db0f7e885a2f2 133728 pypy-coverage_4.5.2+dfsg.1-1_all.deb cb02eaee97c485e4037f0bf419ee614f911e79f8 28660 python-coverage-dbgsym_4.5.2+dfsg.1-1_amd64.deb c97b190cf87ccda92ff5a09dac408b2f6358abde 135212 python-coverage-doc_4.5.2+dfsg.1-1_all.deb 13c59c537c066bbcf46fbf89cde635173aaf2881 10115 python-coverage_4.5.2+dfsg.1-1_amd64.buildinfo 49db13843fd49ece7c04ede3bdc403a84e32da6a 144468 python-coverage_4.5.2+dfsg.1-1_amd64.deb 2d27b6656437ae38a5b20eafb90adb9df309f0c7 34428 python3-coverage-dbgsym_4.5.2+dfsg.1-1_amd64.deb 213177de144eb14ff75f3b1c694dfa7f89b562f9 143940 python3-coverage_4.5.2+dfsg.1-1_amd64.deb Checksums-Sha256: f1b95b16d0d26443ae3bbd936773854f5daff9f252dea768ba7c186dd9a5881d 2549 python-coverage_4.5.2+dfsg.1-1.dsc 9fe2409018fe2baa40267d88dfd665e5a89c72eaf6eae99d6bfa39e7840bed4a 269064 python-coverage_4.5.2+dfsg.1.orig.tar.xz 84361c02e69a14cc1e83f2ad36bae6455d7fe54f69c6dd7c2b2f269aa0c6ffb0 20784 python-coverage_4.5.2+dfsg.1-1.debian.tar.xz 41502048b958e244a8aef165b3cf6a54a6829ee534728f55ff33238f31f5abfd 133728 pypy-coverage_4.5.2+dfsg.1-1_all.deb 8bb741a23373352de339f39b09b6b50861a74be9b97529e056359d4eec0e5e15 28660 python-coverage-dbgsym_4.5.2+dfsg.1-1_amd64.deb a3a3b85e3c790cf6345a74d5b4df61ae0447b703c63ce2664587ce16726e170f 135212 python-coverage-doc_4.5.2+dfsg.1-1_all.deb 1ad254c0dfa6307a509195300bbb35f4818ea3f2b136c0072a003ca19abc6c7e 10115 python-coverage_4.5.2+dfsg.1-1_amd64.buildinfo 436a373b9a17d74734bd2d0b07cb231f9dc522736fa1cfe1018e291f13e82313 144468 python-coverage_4.5.2+dfsg.1-1_amd64.deb 6f2dead4f37c7a7f1d3c1e820ca8dfd5d6e5bc28e2f5957a6ba74827ac0f8433 34428 python3-coverage-dbgsym_4.5.2+dfsg.1-1_amd64.deb e4119e6d0f61dd78574270ce81e4423b85c7316728e4466d24610f565372cff2 143940 python3-coverage_4.5.2+dfsg.1-1_amd64.deb Files: 8d067d33571ae5b52e4fbb46f31f5c6b 2549 python optional python-coverage_4.5.2+dfsg.1-1.dsc c0f6be7604de86b89a390eb799d2c6cc 269064 python optional python-coverage_4.5.2+dfsg.1.orig.tar.xz 4dc4ae51afbd278876727b509c78663b 20784 python optional python-coverage_4.5.2+dfsg.1-1.debian.tar.xz 5ba10050119ae4dce58794ae7fad4d56 133728 python optional pypy-coverage_4.5.2+dfsg.1-1_all.deb d6ce5336a886f455b7325fd32b6cf26e 28660 debug optional python-coverage-dbgsym_4.5.2+dfsg.1-1_amd64.deb c24cf5729804c96aa5a05d97848d1893 135212 doc optional python-coverage-doc_4.5.2+dfsg.1-1_all.deb 3a6c9342f1245bb45214f70f4eaac67d 10115 python optional python-coverage_4.5.2+dfsg.1-1_amd64.buildinfo 240ef7a76a26e427f002b1b6c7cea1d7 144468 python optional python-coverage_4.5.2+dfsg.1-1_amd64.deb e680722207cf51c853e0f36f180306f0 34428 debug optional python3-coverage-dbgsym_4.5.2+dfsg.1-1_amd64.deb b2dd895f67fbfdc4a460f5a75803bf10 143940 python optional python3-coverage_4.5.2+dfsg.1-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEUXzxS7LzmLDLNUhVuLJMBqwShAUFAlxKYN0ACgkQuLJMBqwS hAWLCw//fLPaSJ+C0+7gfwNhKVGh7fCWcgH5sFRP4nmsxAVzUZZutjXoGHSXOKQU lapRUGj/bhQHCgIW3OzJiUZnlx9uY4uiUamBPoLbwqG9AtkHwTGpEO6kM/akirZa
Accepted python-daemon 2.2.3-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 21 Jan 2019 16:32:55 +1100 Source: python-daemon Binary: python-daemon python3-daemon Architecture: source all Version: 2.2.3-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Description: python-daemon - library for making a Unix daemon process — Python 2 python3-daemon - library for making a Unix daemon process — Python 3 Closes: 891543 Changes: python-daemon (2.2.3-1) unstable; urgency=medium . [ Ben Finney ] * The “Maria Rivoli” release. * New upstream version. Highlights since previous release: * Improve performance of `daemon.close_all_open_files`. * Promote the warning for `runner` module to a `DeprecationWarning`. This has been an unofficial example module from the beginning, and it will be removed in a future version. * Refresh patches for upstream changes. * Use HTTPS URL for copyright format reference. * Update publication years in copyright notices. * Correct grant of license in Debian packaging copyright. * Declare “Standards-Version: 4.3.0”. * Declare Debhelper compatibility level 12. * debian/compat: * Remove obsolescent configuration file. * Change to current VCS URL for Debian packaging source. * Update description of source package for current VCS workflow. * Update Git-Buildpackage configuration for current VCS workflow. * Declare build dependencies specifically for arch-independent build. * Patch build system to remove build-only dependency ‘docutils’. Closes: bug#891543. Thanks to Benjamin Drung for the report. * Use helpful substitutions provided by UScan. * Narrow the upstream version mangling pattern. * Use UScan specification of upstream release signature URL. * Use a null command for ‘clean’ during ‘Git-BuildPackage’. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Override the Pybuild build system detection. The presence of a Makefile confuses Pybuild. * Declare upstream metadata in DEP-12 format. * Change to a minimal export of the public key for upstream. . [ Ondřej Nový ] * Remove specification of minimum Python versions. These are now satisfied by all currently supported Debian releases. * Use HTTPS URL for Debian mirror of PyPI service. Checksums-Sha1: 08837c90fdc854ebcde56ae7744c82b6e2c1c411 2663 python-daemon_2.2.3-1.dsc 748f7f06664bccc2945b8493a7c6aea00176fb97 79314 python-daemon_2.2.3.orig.tar.gz 92aff01acdd1b7083da9b4a590a0d9605cc06e60 833 python-daemon_2.2.3.orig.tar.gz.asc ee36a5d8c4ae03773f62bfff7dc3afd75d173ad2 30872 python-daemon_2.2.3-1.debian.tar.xz 8789d5194ab8eab9d352c8fae2843bdcb84caa8d 24836 python-daemon_2.2.3-1_all.deb 00a103348eeb40632b2d92f41d66c8befedcae31 7674 python-daemon_2.2.3-1_amd64.buildinfo d9d388ce09deedc4328d8f830478100ceb09c320 24912 python3-daemon_2.2.3-1_all.deb Checksums-Sha256: d66b4bfe563f8778b2e5914074182a3902e7b0d447276b64b292813d7f15fede 2663 python-daemon_2.2.3-1.dsc affeca9e5adfce2666a63890af9d6aff79f670f7511899edaddca7f96593cc25 79314 python-daemon_2.2.3.orig.tar.gz 1f0aea40fd53e67b1856be10b25f8343823e13521292810f86928de36e15381c 833 python-daemon_2.2.3.orig.tar.gz.asc 6df074fb2b125e94f2ff6184eb70ec3f50fa7b6ab46e2f6decf54db4f8c5ce3b 30872 python-daemon_2.2.3-1.debian.tar.xz c370258a71e6c0d8d4ca23490ce1ebd76b2a46c47fa534af33bb43e8b787cac3 24836 python-daemon_2.2.3-1_all.deb 7ac4776ebdd3c5dfa537d8f075433d673ed6c511fe0b80360ab5326a15ca04d3 7674 python-daemon_2.2.3-1_amd64.buildinfo d43375df0dc845c144ad837e4ec6d0bd213eb2630be7466180d76ff15953a449 24912 python3-daemon_2.2.3-1_all.deb Files: dd8ffcbc2eda90546c2ee12d61694bd6 2663 python optional python-daemon_2.2.3-1.dsc 3ab10a93472201214cd95c05f1923af6 79314 python optional python-daemon_2.2.3.orig.tar.gz a03e13c5f44aa4c3a31a17a93a8dc6c2 833 python optional python-daemon_2.2.3.orig.tar.gz.asc 4d2f19a447e78dcca2f43ded91a547f3 30872 python optional python-daemon_2.2.3-1.debian.tar.xz 0460d69792a7577b6268153dde0eab9b 24836 python optional python-daemon_2.2.3-1_all.deb c1c9ce417743e204d44c0528a109d8eb 7674 python optional python-daemon_2.2.3-1_amd64.buildinfo fad8fea4200da121d95d8067e54d4ec3 24912 python optional python3-daemon_2.2.3-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEUXzxS7LzmLDLNUhVuLJMBqwShAUFAlxFWxYACgkQuLJMBqwS hAUQhBAAmwNI3OhHxDipn1MHEoLSGCSs+U6fk5TmynM5N915oIs9KngyllUYWtQC AMR1a0HdzqosCmxNnpwc9KozzqBhhHJsvpfJMnQflveSfZXT7U8YyooDTKKZL/RH 6it0Pc6v9wr5OmOuZWLIS1Pi/7QE6toaV7jVE/LMWdjKQx9qCC3A2YselR3Gbk5A ccQKVNO2jJ4GirYFvLo1PyWBRpeKc2Shqher+r+m4CZ9dQ/RKiN78OY2XKfJsa0r /nOHcUfGykFojFvPlsVFoeRYTsYrf2+hwxjrNlO96FzpKpILR1tjhq3705pSKQvm kRGlaoLVN97o+cvGAMsMJHQ4axBOJGZMUD/xPlBKf6CbWv+7jsQhqQ+LuuJLHRtb uCcY6maH5vDQMHBhcCjUbekNPMFFo/KIIj6NjHSLY3LGFTcs+bMNb4A+ZrFcpU55 bbatdbT/WvguWD5UcQkd6
Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]
Ian Jackson writes: > Adrian Bunk writes: > > I thought this would would have been less offensive than the normal > > "This is a lie." > > You should never accuse someone of lying unless you are sure that they > know that what they are saying is wrong. For Adrian (since you acknowledged non-native English language status): Ian is pointing out the distinction between “That is a lie” (asserting the person knowingly intended to communicate a falsehood), versus alternatives like “That is false” or “That is not true” (which carries no implication of the person's intention or state of mind). > If you can prove that someone is deliberately saying untrue things on > Debian lists, that is abuse which should be reported and stopped. If you don't want to support a claim that someone is lying, you can avoid that implication: Just point out that the statement is not true (and then do as you (Adrian) did to show how you know it's not true). I hope that helps! -- \“Considering the current sad state of our computer programs, | `\ software development is clearly still a black art, and cannot | _o__) yet be called an engineering discipline.” —Bill Clinton | Ben Finney
Corresponding source for a machine-learning data set (was: Concerns to software freedom when packaging deep-learning based appications.)
Ian Jackson writes: > […] In the case of a pretrained neural network, the source code is the > training data. > > In fact, they are probably not redistributable unless all the training > data is supplied, since the GPL's definition of "source code" is the > "preferred form for modification". For a pretrained neural network > that is the training data. One hopeful sign is that people are addressing the need for the source form of a machine-learning product. In this case, it's by offering a version control system customised to machine-learning data. https://blog.dataversioncontrol.com/data-version-control-tutorial-9146715eda46> Is that an approach we can recommend to upstream developers who publish machine-learning data sets? -- \ “A child of five could understand this. Fetch me a child of | `\ five.” —Groucho Marx | _o__) | Ben Finney
Re: Concerns to software freedom when packaging deep-learning based appications.
Ian Jackson writes: > Things in Debian main shoudl be buildable *from source* using Debian > main. In the case of a pretrained neural network, the source code is > the training data. > > In fact, they are probably not redistributable unless all the training > data is supplied, since the GPL's definition of "source code" is the > "preferred form for modification". For a pretrained neural network > that is the training data. The above (with which I agree completely) puts me in mind of this article from O'Reilly Media: Compilers automated the process of writing machine code. Scripting languages automate many mundane tasks by gluing together larger, more complex programs. Software testing tools, automated deployment tools, containers, and container orchestration systems are all tools for automating the process of developing, deploying, and managing software systems. None of these take advantage of machine learning, but that is certainly the next step. […] We’ve seen research suggesting that neural networks can create new programs by combining existing modules. The system is trained using execution traces from other programs. […] Thinking more systematically, Peter Norvig has argued that machine learning can be used to generate short programs (but not long ones) from training data; to optimize small parts of larger programs, but not the entire program; and possibly to (with the help of humans) be better tutors to beginning programmers. https://www.oreilly.com/ideas/what-machine-learning-means-for-software-development> This thread will be just one of many we will need to have, to determine how best to preserve software freedom as the practice of developing software changes fundamentally. -- \“I always had a repulsive need to be something more than | `\ human.” —David Bowie | _o__) | Ben Finney
Accepted python-coverage 4.5.1+dfsg.1-1 (source all amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Jul 2018 12:25:30 +1000 Source: python-coverage Binary: python3-coverage pypy-coverage python-coverage python-coverage-doc Architecture: source all amd64 Version: 4.5.1+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Description: pypy-coverage - code coverage tool for Python 2 PyPy python-coverage - code coverage tool for Python 2 python-coverage-doc - code coverage tool for Python — documentation python3-coverage - code coverage tool for Python 3 Closes: 901114 Changes: python-coverage (4.5.1+dfsg.1-1) unstable; urgency=medium . * The “Ahmedur Rashid Chowdhury” release. * New upstream version. Highlights since previous release: none documented. * Consolidate the ‘override_dh_auto_build’ packaging target. * Use a null command for ‘clean’ during ‘Git-BuildPackage’. * Correct build dependencies for both arch-dependent and -independent. Closes: bug#901114. Thanks to Santiago Vila for the report. * Declare “Standards-Version: 4.1.5”. * Specify current URL for upstream source repository. * Improve consistency of copyright grant in Debian packaging. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Use standard Debian packaging tools to repack upstream source. * Convert UScan configuration to format version 4. * Remove specification of minimum Python versions. These are now satisfied by all currently supported Debian releases. Checksums-Sha1: b1ca6ef3ed9776dd903c68c45bfac88e392b902a 2549 python-coverage_4.5.1+dfsg.1-1.dsc 6e801b1a2e099ff11a96d472b29a098293000c6d 338890 python-coverage_4.5.1+dfsg.1.orig.tar.gz dca11b38f5d5eaf5b977c8f17396e660448c3923 21272 python-coverage_4.5.1+dfsg.1-1.debian.tar.xz 1a0fec3f9fb60fb08cab298c844ef4fc8674b02d 131940 pypy-coverage_4.5.1+dfsg.1-1_all.deb 9db5bf64d83470595def137a0e9a24237bcf9e8f 25852 python-coverage-dbgsym_4.5.1+dfsg.1-1_amd64.deb 21bcd8dafd335d2d3d7816f6384dfdb20e49d7bc 134388 python-coverage-doc_4.5.1+dfsg.1-1_all.deb 7ef940ce334ba618da454a74f4a3bd137462e853 10629 python-coverage_4.5.1+dfsg.1-1_amd64.buildinfo eee097084063cea389e2d800ca156ef77766 142524 python-coverage_4.5.1+dfsg.1-1_amd64.deb 0bba4afb122b244d109841f65df8cc62d5b2a345 56616 python3-coverage-dbgsym_4.5.1+dfsg.1-1_amd64.deb 1e955b4133bb777b6ad6d475307e2393dd28a431 142336 python3-coverage_4.5.1+dfsg.1-1_amd64.deb Checksums-Sha256: cf7bafb3ce5b52cab1db3b34eb837536762c86e63bbb1daf7221ef490aa13714 2549 python-coverage_4.5.1+dfsg.1-1.dsc 2b398decd97ae3048bc1c71a466df1b0742b11782d9b6d734c081b044d771758 338890 python-coverage_4.5.1+dfsg.1.orig.tar.gz 820a5dedcc170b715fbe5b90f7070f4e56314991da4f94bc999b8b3c9adce01c 21272 python-coverage_4.5.1+dfsg.1-1.debian.tar.xz 887f7cea5dd0939dbf564f04160b18378dfff2be02b5947e3d546ba194fe184c 131940 pypy-coverage_4.5.1+dfsg.1-1_all.deb bb35825bfb427db6c6afcbaecf167191217ad8e416ae44381cdf0eb25535fdb9 25852 python-coverage-dbgsym_4.5.1+dfsg.1-1_amd64.deb 56c1deba41c437c8b65181f5a8c8079120797d69631dd1be5a2a3df87a7bda50 134388 python-coverage-doc_4.5.1+dfsg.1-1_all.deb fc2022b24b94f70a0ac272c26abaa6e5d7ee673f37c8b919fee2c4a252a1348b 10629 python-coverage_4.5.1+dfsg.1-1_amd64.buildinfo dcc033941cde5d45c9ae6b6562c08971169ae0f2d1245ed7b0041e0017cac227 142524 python-coverage_4.5.1+dfsg.1-1_amd64.deb eb8c7416636edda189cdd179143bdb1ffe41af9a9ed6f17da0b129a951f2f24d 56616 python3-coverage-dbgsym_4.5.1+dfsg.1-1_amd64.deb 8f859a8e447666b7e5812cc8ee626d8dae50f8b459c3313b4f867967fce9f578 142336 python3-coverage_4.5.1+dfsg.1-1_amd64.deb Files: a8d1dcf0fa23e7292d31656eec41ed79 2549 python optional python-coverage_4.5.1+dfsg.1-1.dsc 6d505de54a772aa64a4a0bb5160ad2f1 338890 python optional python-coverage_4.5.1+dfsg.1.orig.tar.gz b6a9833b2e5e2c8a4ee653837a777ccf 21272 python optional python-coverage_4.5.1+dfsg.1-1.debian.tar.xz ebcf4f382ed941fbb3f6461fe3b87039 131940 python optional pypy-coverage_4.5.1+dfsg.1-1_all.deb f313d0a316469d44c53704320dbf111f 25852 debug optional python-coverage-dbgsym_4.5.1+dfsg.1-1_amd64.deb b13c5ab0462f958180c073cd0b3c8150 134388 doc optional python-coverage-doc_4.5.1+dfsg.1-1_all.deb 3e266d324d6f5974ace3f7ccfd6a723d 10629 python optional python-coverage_4.5.1+dfsg.1-1_amd64.buildinfo 7db17771fa5fd8843a4836446bf6714e 142524 python optional python-coverage_4.5.1+dfsg.1-1_amd64.deb 20233e895feab7059e8a6a7821df5cf2 56616 debug optional python3-coverage-dbgsym_4.5.1+dfsg.1-1_amd64.deb e7f43bbbfde2107521261375d3462099 142336 python optional python3-coverage_4.5.1+dfsg.1-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAltKz6MACgkQDqWsb2XR 8fedvRAAsODxKu6LGuCDkg7EOLQBsULxl2SeLYVgzKlKmxoLWsofAd0rGAqKtUsL YArIQKLgEJmoTW0XS6Is0TZSC42fqxilFm0COQ6TGNMdkRgpSQ0vQnRDxBft1/Gu uBs
Accepted comixcursors 0.9.1-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 14 Jul 2018 23:20:49 +1000 Source: comixcursors Binary: comixcursors-righthanded comixcursors-lefthanded comixcursors-righthanded-opaque comixcursors-lefthanded-opaque Architecture: source all Version: 0.9.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Description: comixcursors-lefthanded - X11 mouse pointer themes with a comic art feeling (LH, translucen comixcursors-lefthanded-opaque - X11 mouse pointer themes with a comic art feeling (LH, opaque) comixcursors-righthanded - X11 mouse pointer themes with a comic art feeling (RH, translucen comixcursors-righthanded-opaque - X11 mouse pointer themes with a comic art feeling (RH, opaque) Changes: comixcursors (0.9.1-1) unstable; urgency=medium . * The “Vincenzo D'Allestro” release. * New upstream version. * Configure Git-BuildPackage for this Debian source package. * Update copyright years. * Configure UScan for new upstream release tarball URLs. * Specify current VCS for Debian packaging work. * Declare “Standards-Version: 4.1.5”. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Declare Debhelper compatibility level 11. Checksums-Sha1: bbc8c08136777aca193200e4e8ba80eb495c6de3 2198 comixcursors_0.9.1-1.dsc e7dea6eca5163eb694abbb1ec47e6d24b1d1a80f 74736 comixcursors_0.9.1.orig.tar.bz2 1dd07d5bb0a5b1beb0c1265c902b13a52ea90fa5 9900 comixcursors_0.9.1-1.debian.tar.xz e3d3ba587ce4c63e6de4d76f22dff24ed18b9c54 955712 comixcursors-lefthanded-opaque_0.9.1-1_all.deb 52f7e8a6f9498ca91cb3fd61147225a30f4a620d 1042376 comixcursors-lefthanded_0.9.1-1_all.deb 9e3961f02c460462aa454292e2bfa8c7304d1e8e 940556 comixcursors-righthanded-opaque_0.9.1-1_all.deb 420c61c1e5afd05af10a75e3302a8d43f98d8dbb 1031616 comixcursors-righthanded_0.9.1-1_all.deb fa119d6116d0ba1970acf0f878170a14e713e8a1 10742 comixcursors_0.9.1-1_amd64.buildinfo Checksums-Sha256: 7eef05098cd47393d4573024f5ab21d41d44728f38f5fe8e142d45c6860e694e 2198 comixcursors_0.9.1-1.dsc 7248f2da98fea475e590aa657d8581593516530d014a9ddbac8667d1b5f3a02b 74736 comixcursors_0.9.1.orig.tar.bz2 f9db1d4289bc2958b3610925409bcbbb1b225415b01f9ac0f4bba821fe8ef142 9900 comixcursors_0.9.1-1.debian.tar.xz 43f017a38787b84c3d529a8c27294bca4737d33e0a68d65898ee978546814a59 955712 comixcursors-lefthanded-opaque_0.9.1-1_all.deb cf4576f2f235788406ca8d813752a966feb39921c34c97ee5d84036fa82fd2db 1042376 comixcursors-lefthanded_0.9.1-1_all.deb 0d8475253ce958d552c07cea2a7d64b8daf28d9e06f5d4ce9be2847bb335e14f 940556 comixcursors-righthanded-opaque_0.9.1-1_all.deb fe4656f3bc37faec8c7f1908099b39530cf3130b54c2880a391f25bfd0526f6d 1031616 comixcursors-righthanded_0.9.1-1_all.deb b0cf4b12ef1bcc0dbe0d873a05a3bf9ce31f6e777a50d61ec8d49c16477a66f2 10742 comixcursors_0.9.1-1_amd64.buildinfo Files: 8ed343ff14eda998396ccb18f1f98ccc 2198 x11 optional comixcursors_0.9.1-1.dsc 7a02291e67ac270ae32bd35fc948001a 74736 x11 optional comixcursors_0.9.1.orig.tar.bz2 000a7e294f84fdfaf401de4703f87db1 9900 x11 optional comixcursors_0.9.1-1.debian.tar.xz eb64898a1ac6e32d52549737ecc63e82 955712 x11 optional comixcursors-lefthanded-opaque_0.9.1-1_all.deb 287ee166cb2ec32eb858b4d77e54bade 1042376 x11 optional comixcursors-lefthanded_0.9.1-1_all.deb b3644c3f40e6bc80a5d5a70d7a7487f3 940556 x11 optional comixcursors-righthanded-opaque_0.9.1-1_all.deb 081693a021d6833fb52985441f18e149 1031616 x11 optional comixcursors-righthanded_0.9.1-1_all.deb a1775b8b926f70c1fdbc1f1ba3b72461 10742 x11 optional comixcursors_0.9.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAltKmqIACgkQDqWsb2XR 8feh6RAApudC5xP2ZTSEg4buoJl8znx0M09IlmVjKHxJhRP8WQMtHexSCoWhQsUB UmMr9Whry2pxsPotVma55pHgZnes52QMDd/B+Dk7UnpZ1wGx+UbfPOeNduxyP0BD wvqkCjR1SrXVoG3HFLFPm/QIhrqotZCxNu/yehsKgKlVri1WgaLyWtcKsqZOX2r6 mJQ5Iy3IEwxZFdoHZfKRXLCOutKuuVid3hTmT7Bidn84QMBXyYncqoJ6g9Dq5G9+ Gd03hkCvLh2C/e/QMKQLRFAoomzW15UbU3F9LXKQiV/sx8BTrWEAI1+6z8vghfWz JJDBa1lcD6Y9VdZwD4gFbcAlpY+ZSp0RATcCa/5V7OkYRrdk6A2bKenx+RCqHMOr HyaWOJTeCmIEE20sSycyflfasNkPYogv62qmDw/Ku5zDt3jbhYLCxpRGDzzAB5e6 ZxXag4eEapbzFkVyUW/2xbp1r6UmAT09D7u0AKR7HkbfDedSZVeKC65jeEQ2lJCB kKH7PNPiyRO6dBtVWkjLWI9urpFdxVZ86OOLEBGsmcsziAqF5BUiCF4qM4zhQhf4 aSOIEVOAMMFlBo9B0FrORwC2fsRk4421h48RUyjnNd+E5pNJKfevTE8AClzMLp98 GZCWVsNkhA1rf+9M29URkGQuHdpRT+R1HUHhghXvaDaokkmw7JY= =rDNz -END PGP SIGNATURE-
Re: get-orig-source and standardized source repacking
Simon McVittie writes: > The only times repacking the orig tarball is required are: > > […] > - it isn't available in a format supported by dpkg (with the extreme case > of this being that there is no orig tarball at all, only a VCS repository) A case more extreme: the work is not distributed upstream as tarball nor as VCS. It is available upstream only as disparate files, not from any single URL. (For a simple example of that, see the ‘lojban-common’ package.) -- \“I don't accept the currently fashionable assertion that any | `\ view is automatically as worthy of respect as any equal and | _o__) opposite view.” —Douglas Adams | Ben Finney
Accepted xkcdpass 1.16.5+dfsg.1-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 10 Apr 2018 05:36:46 +1000 Source: xkcdpass Binary: xkcdpass Architecture: source all Version: 1.16.5+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: xkcdpass - secure passphrase generator inspired by XKCD 936 Closes: 851144 Changes: xkcdpass (1.16.5+dfsg.1-1) unstable; urgency=medium . * The “Mong Shwe Lung Marma” release. * New upstream version. Highlights since previous release: * Correct the assumption about Python interpreter program name. * Add option ‘--case’ to specify case of words in passphrase. * Add option ‘--separator’ to specify separator between words. * Correct an editor hint. Closes: bug#851144. Thanks to Edward Betts for the report. * debian/patches/use-current-interpreter-name.patch: * Drop the patch, now applied upstream. * Declare Debhelper compatibility level 11. * Declare “Standards-Version: 4.1.4”. * Specify current VCS for Debian packaging work. * Update copyright years for Debian packaging. * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets. These are no longer mentioned in Debian Policy 4.1.4 and later. * Update manual page for changes in command interface. Checksums-Sha1: 428bd9fb163d0c79f6d1bf4d29968166003d1157 1990 xkcdpass_1.16.5+dfsg.1-1.dsc 08b18132b87a76aaaeb3ddc50c7e1dc8b8161442 1018222 xkcdpass_1.16.5+dfsg.1.orig.tar.gz 8eba1907e722e328d3cc6f17d38a9e29c01dde44 12028 xkcdpass_1.16.5+dfsg.1-1.debian.tar.xz cf8e9303ac98df6bb95e3f677fc6db3236e98471 749508 xkcdpass_1.16.5+dfsg.1-1_all.deb ab42d363f1e0a795d2588755dc96a3a68bcc271e 6363 xkcdpass_1.16.5+dfsg.1-1_amd64.buildinfo Checksums-Sha256: f15f9619959471e721ee9ac26b95d5dfa7bd03b348e4a9b534a07f744d24f41e 1990 xkcdpass_1.16.5+dfsg.1-1.dsc 121fb6192649581160e2d2e4e5be5116230be1e5b1bd477ced182f1ed7b743b0 1018222 xkcdpass_1.16.5+dfsg.1.orig.tar.gz 0da0d880fb8057570a1dd14036f1123981e80353d011b559b37e16c2bca0de71 12028 xkcdpass_1.16.5+dfsg.1-1.debian.tar.xz 4d1eda2c4e2ae163d3822db5ee9b98b15457d738d49ee42b33d7f3f6bbfca75d 749508 xkcdpass_1.16.5+dfsg.1-1_all.deb 25c34fb8b09fe6313e5f753a3f8c6c4ecab2c757e2b90128e32e03809707d5bc 6363 xkcdpass_1.16.5+dfsg.1-1_amd64.buildinfo Files: d1120c2a39e5b672d09e4de619e4856d 1990 admin optional xkcdpass_1.16.5+dfsg.1-1.dsc 118c573105680478606dcbfa4217b7a6 1018222 admin optional xkcdpass_1.16.5+dfsg.1.orig.tar.gz 05eabcb1d661f5ba7bfa615ded6b2d41 12028 admin optional xkcdpass_1.16.5+dfsg.1-1.debian.tar.xz 82dcd33acf2c29ff8b3762354d173aba 749508 admin optional xkcdpass_1.16.5+dfsg.1-1_all.deb 366a9857e310508e2265518189bba4a3 6363 admin optional xkcdpass_1.16.5+dfsg.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlrQY/sACgkQDqWsb2XR 8ffvIBAAnZRfVgL7XZIlknK/fUmpp+FLY8i2LvKSLYz2mV7GQ79AQ5v1N8WIroSd qZKvlviLqXdNJMT/9SJAHtG2zFINXswPht5QPeouHvuM2H8K/1HyxP0iToTjeqyG r2f0ClxKdhNqiTiCqMltoybt4Bv4rEByk22dIqNa4kGzp1C86cVNDIQ+pqhhff9/ 1ZaiC9SvuTUvW9qhDawHWFLOipduF9aQCkhm180WIuErh0oNfKOWSU9IIR2E+saX rAxcSZZceVNiM9NndE3Skz5nV395d2qeY1pZoQ6cErSLAVeNbFxwQa3Zafyq6h7z niE1A5yaWnjxXmTAdZe/T4uyMNDRCkIbtQg0KKsjmUyfXReFwLoiLlqvfnU3txgg 7UpEJdUxvudlF72wx4N5/vaQb782ALvcWT088uyDIMaq1yBFP2Wq0H1NbuqTuofy 7tqLhOJfY+Tq3ql6Y3aomdkJe77YRbGpIl25MkUG/E2Ate6EaR7yraX9n2EEpV4z vOALEelT3+QHL4O8BV2FHpmAvJUb2/MSeM327of2Wgn1DSf052tT6iQAv4h8VvSR NvJG7WximLZ7awlKUZlL6Ur2eeYgGecBqj9QRGoF9Vt8rW9edX9cn7w6gR7MzuJt hz8nZd1Ml0E2nlG8Ie8xQieSrQB8JHft+5Q6FaBAxgtzKo+3M34= =FS+k -END PGP SIGNATURE-
Re: Debian Policy 4.1.4.0 released
Sean Whitton <spwhit...@spwhitton.name> writes: > I just pushed Debian Policy 4.1.4.0 to sid. Thank you to the ~20 > people who contributed to this release, which includes several first > time contributors of patches. > […] > > 4.9 > The ``get-orig-source`` rules target has been removed. Packages > should use ``debian/watch`` and uscan instead. Especially for this, my ‘debian/rules’ files thank you. -- \“Institutions will try to preserve the problem to which they | `\ are the solution.” —Clay Shirky, 2012 | _o__) | Ben Finney
Re: New lintian warning: vcs-deprecated-in-debian-infrastructure
Adam Borowski <kilob...@angband.pl> writes: > but pray tell, what will you do with that URL? Visit it later, when I *do* have internet access. Many people have internet connections that are unreliable, slow, expensive, arbitrarily blocked, or some combination of all those. We should not assume that “has internet access” is a binary, all-or-nothing property; and we should not dismiss the use cases of people who are between those extremes. -- \“Pinky, are you pondering what I'm pondering?” “Wuh, I think | `\ so, Brain, but wouldn't anything lose its flavor on the bedpost | _o__) overnight?” —_Pinky and The Brain_ | Ben Finney
Re: New lintian warning: vcs-deprecated-in-debian-infrastructure
Markus Koschany <a...@debian.org> writes: > Am 22.03.2018 um 15:40 schrieb Guillem Jover: > > I'd very strongly object to completely moving those fields out of > > the source packages [&.3] I'll happily take outdated data than no > > data any day, because usually you can use that outdated data to > > trace your way to the current one, not so if it's missing. > > You need online access to make use of the above information in any > way. That's not true; you are incorrect in thinking that exhausts the common uses of that information. For example: > If you want to contact the maintainer you need internet access With the maintainer email address, I do not need internet access to compose an email message. Without that information I can't. > if you want to visit the upstream homepage you need internet access With the upstream home page URL, I do not need internet access to bookmark a URL. Without that URL I can't. > etc. So, there are plenty of uses for information that do not require internet access *at the time of using* the information. Yes, some uses do require internet access; that doesn't eliminate all usefulness of the information. So, I concur with Guillem: This information is closely tied to the source package, and the source package becomes less useful (lack of imagination notwithstanding :-) by taking that information away from the source package. There may be good arguments for removing that information from the source package. But let's dispose now of the “it's no use” claim; that's simply false, so some other justification will be needed. -- \ “If consumers even know there's a DRM, what it is, and how it | `\ works, we've already failed.” —Peter Lee, Disney corporation, | _o__) 2005 | Ben Finney
Accepted gandi-cli 1.2-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 18 Mar 2018 12:36:45 +1100 Source: gandi-cli Binary: gandi-cli Architecture: source all Version: 1.2-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: gandi-cli - command-line interface for Gandi service Closes: 764342 Changes: gandi-cli (1.2-1) unstable; urgency=medium . * The “Yuko Sakai” release. * Initial Debian release. (Closes: bug#764342) Checksums-Sha1: 6163d96c2fec8137cdba923f31bfd209e1ab3a06 1949 gandi-cli_1.2-1.dsc 9322d1e60f860a7c45b50f2fb178aaac2b1a2115 159352 gandi-cli_1.2.orig.tar.gz 1e193025aadd04a2c1e69487522e309404449655 4212 gandi-cli_1.2-1.debian.tar.xz 76d6333b27b08d2370dd24289f19d71c8497f61a 112012 gandi-cli_1.2-1_all.deb 2b40421174502518160f1b2d3a05eea06a7b355b 6523 gandi-cli_1.2-1_amd64.buildinfo Checksums-Sha256: 2c00908d5b7dd091751ced28505387d23d55c352a85afefb6c43d6149530a598 1949 gandi-cli_1.2-1.dsc 51b5287a285bf665446d7ff47ed9cb447caa79ab8504d29e4212ae825e27086e 159352 gandi-cli_1.2.orig.tar.gz 3807ec6a8bc82c4c51a29e1774ab25a9112986114c468f6c1c96ccbff1d3330a 4212 gandi-cli_1.2-1.debian.tar.xz f8d3f09b21dfbee21b2f615d3e1938169db69574a5e8d64ebb73a6ffbe2ff9de 112012 gandi-cli_1.2-1_all.deb f2f1151afe0a77d26ad614e5a2f7e675e1067daf89db0db5e37e651a793739e3 6523 gandi-cli_1.2-1_amd64.buildinfo Files: bc740a9dc04952862fd53c47f3ac05c3 1949 utils optional gandi-cli_1.2-1.dsc a69de243ff5bda0ddd41bc5971368db7 159352 utils optional gandi-cli_1.2.orig.tar.gz fb0567eeede61e0e249dc78629c50b57 4212 utils optional gandi-cli_1.2-1.debian.tar.xz b21c5888fea5e69ad7245d534fd1a96b 112012 utils optional gandi-cli_1.2-1_all.deb 1515cba414cfff68f1fb3345daa45d92 6523 utils optional gandi-cli_1.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlqtxhAACgkQDqWsb2XR 8ffJBxAApLBkOY12cyIW6/KajDydIn7INtrMPyUpJZmBLK+rBAoj3BNdcPKNpPnd 9mG2sloWN/cVkMd9NbK9StswJY4pX68Scv2IiBOf7wz9OGKIXwr//2hROPumoThT mRY9QaOVFy1m0akdzy4mDQwPwFkTDkwzxiFSJP6h0fplvs+SjQviilGRVGs7f4aU 4+qPr/nV55S9GeTgODqtD/xrwPlIRCd2o1CGdngFWRf/dCPk7fcSSjF94vQguYf9 N3e4oq7jXRPIdX1CqgrrN5N64I9o9rgya8HTKZiNntikuVwb6IogOlWMImx/Bgdw CsatztuxX8xjNB72chTwFZV5AlyMKUQ8nb1C/RsaENl3ApO7R8lzHV6gMmB6lUMA KCwX4dm1f3Pq/TbXjmiGBk0xsy4FkHNHqPUdnrwS+zFKCbjy/W+XwrUYz7JEF4fD PYTsWb49c0SfRVjbweOD55fLpI8QAAlPH2LiUB/oYW8Q2BDUsFxZbKb5LmXC8a0Y dF6IYKaNxiCnoXkhc0qwa3Kj+jjGYvDxa9Sluj8eCYZD8KBk4MXROFiCmKy1gMSM RRyUsvLoLIt2ZxIAvZ0utJvWh9odTtdAKVEoC//miPFRbSGXcOng22B4+r21KUxv HHY/M9LZBu1vGyZWSTxqKYPcxq/hiqJVQ/bepcUKu+EcE87FkEI= =fNMh -END PGP SIGNATURE-
Re: Bug#880014: Technical committee appointment
Gunnar Wolf <gw...@debian.org> writes: > I have to pick a nit here - I know this mail probably comes from a > template and you are repeating what used to be true here. But, > according to GR 003 in 2016¹, Didier is the "Chair" of the Technical > Committee, not the "Chairman". Thank you, this was a well worded correction that avoided any accusation or shame. These corrections are always worthwhile, for improving the welcoming culture of the Debian community. -- \“If you continue running Windows, your system may become | `\unstable.” —Microsoft, Windows 95 bluescreen error message | _o__) | Ben Finney
Re: Updated proposal for improving the FTP NEW process
Gert Wollny <gw.foss...@gmail.com> writes: > […] simply asking the peers doesn't make the process very public. That is, IIUC, by design and for good reason. Before a review of the copyright status of the work is done, we don't have confidence the Debian Project has permission to redistribute it publicly. If it turns out the work is not redistributable by the Debian Project, it is then too late; and the case could be made that we should not allow that situation to arise (i.e. we should not redistribute before we have confidence the work can legally be permitted by us). So, putting it up on some public Debian infrastructure before it passes review is, IIUC, problematic for that reason at least. -- \ “Please leave your values at the front desk.” —hotel, Paris | `\ | _o__) | Ben Finney
Salsa issue tracker disabled for Debian group (was: A proposal for improving transparency of the FTP NEW process)
Thomas Goirand <z...@debian.org> writes: > Also, I would really have preferred if Salsa's issue tracker feature > was simply removed/desactivated, because every other day, there's > someone proposing to replace debbug with it. Thanks but no thanks. As best I can tell, any project created in the Debian group <URL:https://salsa.debian.org/debian/> already has the Issues permission off, without anything else needing to be done. That seems entirely appropriate, for a Debian packaging project, for the reason you state (any Debian package should have bugs reported to the Debian BTS). Does that meet the preference you expressed above? -- \ “I distrust those people who know so well what God wants them | `\to do to their fellows, because it always coincides with their | _o__) own desires.” —Susan Brownell Anthony, 1896 | Ben Finney
Re: A proposal for improving transparency of the FTP NEW process
Paul Gevers <elb...@debian.org> writes: > Hi, > > On 03-03-18 11:57, Ben Finney wrote: > > A large code base with complex interacting works of copyright can be > > broken into smaller packages, that are each individually easier to > > review and pass through NEW; either built as separate source > > packages, or combined at build time. > > Except if there is one upstream tar ball. Do you really suggest we > should repack one upstream tar ball into multiple smaller tar balls > just for the review process? To say “should” is rather too strong. I'm presenting it as one option to try, for those who are frustrated at the slow review process for a large, complex source package with complex copyright interactions: Break it into more easily-reviewed pieces. The review process is an acknowledged bottleneck for NEW queue processing, and we've seen stated that large, complex source packages are especially difficult to get through. I'm proposing that the same code base as a set of smaller source packages will get through that bottleneck easier; I don't say that as a recommendation nor a “should”, but as an option to try, for those of us who not FTPmaster and are looking for ways to work better with the process. -- \ “Whenever you read a good book, it's like the author is right | `\ there, in the room talking to you, which is why I don't like to | _o__) read good books.” —Jack Handey | Ben Finney
Re: A proposal for improving transparency of the FTP NEW process
Lars Wirzenius <l...@liw.fi> writes: > Admittedly, it is quite a small package, but that's kind-of my point. > Making it easy for others to do the thing you need them to do is what > you can do to make things easier for you. Asking them to do more work, > or to change how they do their thing, is less likely to go well. > > The Linux kernel maintainers flat-out reject large patches that dump > big changes without prior discussion. This is because it's easier for > them to digest changes in smaller chunks, and they put the > responsibility for presenting the changes that way on the people > producing the patches. > > For Debian, I think we should have the same approach. […] Your recounted experience suggests another way (compatible with the ways you discussed) to reduce the work of reviewing a code base with complex copyright interactions: A large code base with complex interacting works of copyright can be broken into smaller packages, that are each individually easier to review and pass through NEW; either built as separate source packages, or combined at build time. Will that work for every large package? Maybe that's too much to hope for. But in those cases where the maintainers are frustrated that the NEW queue processing takes a long time to pass their new package: isn't it worth the effort to try making it easier to review by breaking the package into smaller more easily-reviewed chunks? A maintainer (or a team) who tries that might find it's not so hard; and having done that, it becomes that much easier to understand not only the copyright status of each smaller package, but for a newcomer to understand how to maintain it. This is a benefit not only in getting the package reviewed through the NEW queue, but also for attracting additional co-maintainers. Breaking large complex tangles into smaller manageable pieces is thus, I'd suggest, an investment in reducing the overall work of Debian package maintenance. > There may be other reasons why some packages stay in NEW for a long > time. Getting information from ftp masters about the reasons why, and > a discussion of how we can make easier for them to make NEW review > easier would, I feel, take us forward better than another than us > complaining that things are taking too long. Thanks for keeping the options open. -- \ Contentsofsignaturemaysettleduringshipping. | `\ | _o__) | Ben Finney
Accepted python-daemon 2.1.2-2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Feb 2018 09:07:48 +1100 Source: python-daemon Binary: python-daemon python3-daemon Architecture: source all Version: 2.1.2-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-daemon - library for making a Unix daemon process — Python 2 python3-daemon - library for making a Unix daemon process — Python 3 Closes: 891543 Changes: python-daemon (2.1.2-2) unstable; urgency=medium . * The “Maria Rivoli” release. * Use HTTPS URL for copyright format reference. * Declare “Standards-Version: 4.1.3”. No additional changes needed. * Declare Debhelper compatibility level 11. * Change to current VCS URL for Debian packaging source. * Update description of source package for current VCS workflow. * Update Git-Buildpackage configuration for current VCS workflow. * Patch build system to remove build-only dependency ‘docutils’. Closes: bug#891543. Thanks to Benjamin Drung for the report. * Use helpful substitutions provided by UScan. Checksums-Sha1: f6fd4ce2f5d9a150883e70dc9e077d631fa25011 2356 python-daemon_2.1.2-2.dsc d2af7536013f67e04e3f3b2b0e19f6575e1c7ef5 88272 python-daemon_2.1.2-2.debian.tar.xz 0534b1eb359ef5d1d041e635f2d17ae28df0b606 22476 python-daemon_2.1.2-2_all.deb bb71c7e9528dc3e1bb241d3902bc75cb583a3342 7743 python-daemon_2.1.2-2_amd64.buildinfo 76270fbd1018a85fbbf7cfbe3e0e72245c10e7a0 22540 python3-daemon_2.1.2-2_all.deb Checksums-Sha256: 4fd18d697cefb135bf8a36e28f2987ea382d40c769f05db76e31b3ea2df317f2 2356 python-daemon_2.1.2-2.dsc 3e67365d8542c383d9d58c267d29cfd0b003718e2b19b4b7a103c8634391c6cf 88272 python-daemon_2.1.2-2.debian.tar.xz cc0cfbf0a34e5ad2c6a0fe612e30f250d87604dfdb2cb44a28be85cbdb3d0b93 22476 python-daemon_2.1.2-2_all.deb c4445f63d4885ba0076370bf3a562ebb9683c22e002b65b82dc36702d517e604 7743 python-daemon_2.1.2-2_amd64.buildinfo 94c31227c899406eedc3c6abec27f371892bd5508a29c6de3b9895d5af4b4b85 22540 python3-daemon_2.1.2-2_all.deb Files: cfbeb8fa16dfc4f634f1d508660fd28a 2356 python optional python-daemon_2.1.2-2.dsc 78708c0dba0935ba2bd90e2bba38ac4b 88272 python optional python-daemon_2.1.2-2.debian.tar.xz 58a4b8675239afb125a42b7260961db3 22476 python optional python-daemon_2.1.2-2_all.deb 34f5694653578a5486393bbc94403920 7743 python optional python-daemon_2.1.2-2_amd64.buildinfo b106b5e9a1a88080dce8ed39f583ae02 22540 python optional python3-daemon_2.1.2-2_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlqWDP8ACgkQDqWsb2XR 8fcYTQ//Uxa+0qLSRA6dV3/qtHVDKAtu6DEHm3Cxb7R1U9qUAG8MwjjQOzsYOEay ThKZXfPHz5TB9nU41uc4UJyNpi75C4+5J6MfC9u/KiA6h4XDT/zYLUWsHVDHQ8t6 ty9i5RNCJ+icd+IPRCe0MNduj7MSRU3lu7b/ZH8o7JI7WqmK7/gsdto+9hbCZI7+ mf3AEC7TPctHiHouMvZB137tecg6XuxEenabHu9TrYcVbn1EZHgJ/g0kdrKph0zx thHr4MCixnOKRUzsjI6wEYR++xfYabFZcYzU5alnTBuyRb64+5qm0bjXFniE/krg ClDqPf4t6Bb2BImBZL89ttSxnZGBZMha2QpJXJ4S/VEAqOWyufe0/iLvy97L+BIx lz8L2qox+aLh5rRYVdyIP34Q38aMGO92jWsnfYaLTFKGCRj99uYlIdXPD//S5tjv N+JKDzmXrCgzaBoUaHszvvxjTbuuv0sk/ras26gFTeBuFExCa/VOx48Jzcd1Frmf 62ZaeTNGU+ltAA9w9/zApcp3GZFuFv7UcLIiRHahfKSpX/VxJNFxj3xNFROggoyj AAv5K/pR1rpepaYMZJFON2EAKCf9cxHV46J2oR+Oq+JwsOqVivtct8HWA8XUbE/w +4faA1hyi8WeK8dpmFm7XxmjCfE2s/PnYfOX9+iJUQz/0jwmueY= =CTed -END PGP SIGNATURE-
Accepted jquery-at.js 1.5.4+dfsg.1-2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Feb 2018 23:09:42 +1100 Source: jquery-at.js Binary: libjs-jquery-atwho Architecture: source all Version: 1.5.4+dfsg.1-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: libjs-jquery-atwho - library to autocomplete references in text fields Closes: 890391 Changes: jquery-at.js (1.5.4+dfsg.1-2) unstable; urgency=medium . * The “Ananda Gopal Ganguly” release. * Patch the CSS to correct an invalid font declaration. * Use helpful substitution markers in UScan configuration. * Patch Gulp build system to remove unused actions. * Use the Gulp build system to compile CoffeeScript source. Closes: bug#890391. Thanks to Pirate Praveen for the report and assistance in packaging the changes. * Use the Gulp build system to compile the library. Checksums-Sha1: 5c9d8deace9c67beaf34b9d07d93d19794da0c7d 2006 jquery-at.js_1.5.4+dfsg.1-2.dsc 80343c0f5ee09b2e7f34b6802ff258a70be37b14 6792 jquery-at.js_1.5.4+dfsg.1-2.debian.tar.xz f08a660ad115a6e8957424d2dd637a07ae2157b0 13657 jquery-at.js_1.5.4+dfsg.1-2_amd64.buildinfo fdfc51becc8ae9eac539603d7623cf328389c58e 21472 libjs-jquery-atwho_1.5.4+dfsg.1-2_all.deb Checksums-Sha256: f2cbfcbaa4ad991173cf9ad67082296c246f861537485c6d261a721876304da5 2006 jquery-at.js_1.5.4+dfsg.1-2.dsc 38e40773c2523de669eff291a20cda17ad9f3344af211465b60fa58d040ec799 6792 jquery-at.js_1.5.4+dfsg.1-2.debian.tar.xz c77d00daa0bdcc641bcd4ac6ad32dfc874c88dd670eff7030df8be02c4920a39 13657 jquery-at.js_1.5.4+dfsg.1-2_amd64.buildinfo b7b27b6e40555f064289f3832449bb17ce86b7e1216af68d6335037beffa1fbc 21472 libjs-jquery-atwho_1.5.4+dfsg.1-2_all.deb Files: de14a7284e5177abd69cf8ec1897e4d6 2006 javascript optional jquery-at.js_1.5.4+dfsg.1-2.dsc b9e0bc99e1a29cc520bf24c498d2 6792 javascript optional jquery-at.js_1.5.4+dfsg.1-2.debian.tar.xz 7e2a45a6fc9c8cbc8a99b09b5604d0c4 13657 javascript optional jquery-at.js_1.5.4+dfsg.1-2_amd64.buildinfo 7f756f2bab085af0c05080f9e2324dd0 21472 javascript optional libjs-jquery-atwho_1.5.4+dfsg.1-2_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlqSqQIACgkQDqWsb2XR 8fcKOQ//VEdX24zeKtbuqnnSPDq4L0DycdaT8UunTweHJblnVc5iOd0O3bYWF3PK e+BFaqplZQyzd9AcrjQGG4I46yZze0dafsF56fB8vphqjU2pukO7mrgBy/lL2K+y hoiBsbXsF+vc6eAKDY7YzrfhpqpRz2NdvXJ8OPCAdIPOJUh5kVp25oe1uRn/zlyf Y2q/DueYDQtiIoMZQO7Xx7lr2iVhednXVpX0jGmWzML0sz+4wwKjoxmo+Hv7Ydux cTsppK9S3QShK9lUzQjOl0TNxMBlANhjLbVWrJxtsdUa/HYe1k7U74CT5gIT7N/h RCW/ZPPVIUPdRVzSLWHDeLFi3UkdQttQXYWgF0OHjgZMAr93UMkJYTcnpbvcbKVj PHKYW2IITcMCKTLoZpuCzLFrKTHMHw+fkQ0Xp8YHDnAVbkhG+lOVgoFO2bUGcM+N 9xKsMwbHnnH7lpFppBexx2OVNAv/pmbBB/LlqfIbSwrRINxYP3wbKs5ef5DRK/KK 1wIYYaopWHade9UVLBpv5g/KQNoSvFDbeCsy+85aQ1gN2Ck294V1GWzsRv6rxCsE DcTqzSPV4jlfxQsFNuOsDm9ZHgXxoVrfww+aaIaMdtpidw2UpVdnsIfofvka+GiE PGX5L0HYjS6JYdrqEeDAmsMqsD6+XKP5kw+bNNQzEvp+DATElNY= =Nc6f -END PGP SIGNATURE-
Accepted jquery-caret.js 0.3.1+dfsg.1-2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Feb 2018 13:16:51 +1100 Source: jquery-caret.js Binary: libjs-jquery-caret.js Architecture: source all Version: 0.3.1+dfsg.1-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: libjs-jquery-caret.js - library to query input caret position Closes: 890875 Changes: jquery-caret.js (0.3.1+dfsg.1-2) unstable; urgency=medium . * Upload to “unstable”. Closes: bug#890875. Thanks to Pirate Praveen for the report. Thanks to Balasankar C for the verifiable test case. * Use current HTTPS URL for copyright format declaration. * Specify current VCS for Debian packaging work. * Update description of source package for current VCS workflow. * Update Git-Buildpackage configuration for current VCS workflow. * Declare Debhelper compatibility level 11. * Move package to new “Section: javascript”. * Declare “Standards-Version: 4.1.3”. Checksums-Sha1: 3a1d8bee6c31aa91ef67ee19dede138c1ef072bb 1989 jquery-caret.js_0.3.1+dfsg.1-2.dsc 6c166ad2fcd0bcf2e8d9a801dff2d11e1822c7c3 4756 jquery-caret.js_0.3.1+dfsg.1-2.debian.tar.xz c0c995a38bd737b2bf70b9f9a55824c5f6e702b6 7277 jquery-caret.js_0.3.1+dfsg.1-2_amd64.buildinfo a7c193b169faf150cd7f1bac0a8c28075200bba3 8780 libjs-jquery-caret.js_0.3.1+dfsg.1-2_all.deb Checksums-Sha256: b1e63fdeffce6477376e60fc48e816c9d0da748047f907cc4765c166938c13c0 1989 jquery-caret.js_0.3.1+dfsg.1-2.dsc d0d72808f56713c4798e10b91184d9dca9dea13aa8e7e0c5623efa071e727ee5 4756 jquery-caret.js_0.3.1+dfsg.1-2.debian.tar.xz be2ac38895bc4b8695ad3265d1e97682de211c43aced4e9f96a59c44abeb0011 7277 jquery-caret.js_0.3.1+dfsg.1-2_amd64.buildinfo 629e85998788af6a364a1b78da1107972414c31deff36ff3aaeb630721c2ecc3 8780 libjs-jquery-caret.js_0.3.1+dfsg.1-2_all.deb Files: b47ce78bdf8c73f03196a3d75f4d0918 1989 javascript optional jquery-caret.js_0.3.1+dfsg.1-2.dsc 1c326774dc8972fa65e969082d5b4097 4756 javascript optional jquery-caret.js_0.3.1+dfsg.1-2.debian.tar.xz ec82c3f3c67e9b157ac73555c4c53b6d 7277 javascript optional jquery-caret.js_0.3.1+dfsg.1-2_amd64.buildinfo 31e5d3f3b563cee471a7454363c7bf53 8780 javascript optional libjs-jquery-caret.js_0.3.1+dfsg.1-2_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlqSHZUACgkQDqWsb2XR 8fc0SA/+OmsdJttbZpjeJ0PP1uq/iJvOpEqLM9QS3BPQC9hllueuLN9chiTe9hKG udJZWX8Q1J1S1EOvk/CEzjT36doBy80UByIcyVPJtAY/g4+m2iPodxPbu3de392V SKwfyhzuBnUXqDAkh6UCOoJ2w1rciqgE0atacPFGQnGEcgON19Lkzm5BtYmEXbxz 0ISD0Q9n5Ns29DvZOB+CbqApiVSDMyLz35xTbduj2/kQlqA4pr/uBiiIwzb5VolQ F6eSe/wkUmbdRW1Ma43bfjDt507YlWSClhbfsJYdpe0EexIWFGWw7D4572aCPO1y MTfto02ZNV43Hydco2eh7wpuiTV+MIAmc4c3/yI17c/nJRxPOsCPGFG5TlZsunvD KZD+y1BPi3/HHL82p7bbQ6aQHlIADBZKHtn27AS07SR5tIyyn/e7IV1Rv317EWtI qydRvXSoEnLw8yea2w3FEeklskP6RmYzXYWzbc/ngAenfuPSS6Tnu0MG9HEeMV2G DA0feebLSBi9XFQhmZ4n6UP4/6PwRDWpciesMxf2zumY7y5Y14wEWZjygjHMqSZO mKnLccpjSg8WgAiiI0OgFARqTBsQQUNHnZirQhRZHrMD69lWU84mDT7jC+3JFUrD msY5UYLu5vtGCktc/Olh4xWo7YBLya9SsWCF5oCDsavHgxeXEeA= =9lLx -END PGP SIGNATURE-
Accepted dput 1.0.2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Feb 2018 11:07:14 +1100 Source: dput Binary: dput Architecture: source all Version: 1.0.2 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: dput - Debian package upload tool Closes: 876382 891268 Changes: dput (1.0.2) unstable; urgency=medium . * The “Rezaul Karim Siddique” release. * Parse custom port value as integer from FQDN value text. Closes: bug#876382. Thanks to Marc Haber for the report. * Declare “Standards-Version: 4.1.3”. No additional changes needed. * Declare Debhelper compatibility level 11. * Update copyright years. * Update reference URLs to HTTPS scheme, where appropriate. * Define custom report behaviour for Reportbug. * Declare EditorConfig settings for the code base. * Change ‘incoming’ for ‘mentors’ host in default configuration. Closes: bug#891268. Thanks to Mattia Rizzolo for the report and patch. Checksums-Sha1: a734260ee68d738951edbe82938ebb75ced44713 1764 dput_1.0.2.dsc 14903b834dd67f28ff03c5fc8ef2128e0ed11640 103476 dput_1.0.2.tar.xz eba7cd55f2490796fef2093cf8bd7764be6c4ee7 55240 dput_1.0.2_all.deb 8db929b78276530ffe1efff89f16e718f5568ae9 7406 dput_1.0.2_amd64.buildinfo Checksums-Sha256: e0f12dabfcc174168a9908ee4d24a0cff143456472c3db65575a666b2bd18a18 1764 dput_1.0.2.dsc cdbd4ad0f75e68e5516908e2e6e7c3be6135a1bcc363920d758ed6f88c6e0a3d 103476 dput_1.0.2.tar.xz 42dea553392137c7ff08efa5139bf53adc3a5c9ccdb5c0942746768ba14ac88a 55240 dput_1.0.2_all.deb de1266d4fea092f0a193cad27da1252f28a41c5513e2b342fe4aee000154c520 7406 dput_1.0.2_amd64.buildinfo Files: 9fc66d9d8125207bb51d41376cba6cc4 1764 devel optional dput_1.0.2.dsc 67924fcbb7cb17f3344dd3696f1c2619 103476 devel optional dput_1.0.2.tar.xz 04ac0cbc4b01fe5a4d247b298c18bd73 55240 devel optional dput_1.0.2_all.deb cdf295e0659ee20a3afffcaaa0091a37 7406 devel optional dput_1.0.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlqSACgACgkQDqWsb2XR 8ff5+w/7B18YnfkKRrvD90K1eXbtKjpAwLNy+fOWyoA3MpUyLFoUxb/QOypoA5qo tkhTgovzIU7C4ZDgfQzy0mC3RBWX6+eCa0G4qu158YdTddQu3vLSJHNX6pksTYK7 vr+cd6t6n/WyJVQvnpywza8ddig4DlVcj1MaIgBB84Z5iLYT65rKxDC0ibGTCm21 zwHbwFW2aCRFWN6en4T4TqOn2u9ez0pcoKZUnMY0scNpq9vNKoW4gyzLoLa1oGdb sGo+rQvpoJZw39KHLXwPv2t9SIp992h+zFeUeYPwaiPZqxMwIj4sKELf1eUmx2EU 17tYn02btaxRhB+H+eHKz+1SIKLFwTXtOjAPrKry6nJgaXXKMY9MJ3KINavZtrlG ukByIjnV2D2tlIaOS6cxienuh34FqXL1OxgZ5dg9w6wMaEALZBrjDNchJ6NJlPhu afh6viJYuQgAyUtFuPsgOVvRJxFgwGNNMbqM/tP5Sv8L0EU+9YGJRe3OTKEmaXAK FHlB6tgbIRVU7jiqEsEFzaLOhsTdYLsxus5eD9j+/+woKOkn2TR5rdM+HkMXnk7C mVK5R+p8xKa8YwWhxddoR073/RQLCm7TTQEJVK7BsdHzfxaO4cS5iAgwQfMu+B9b 8BVZx3/B9O+9J+Dmo5bC72SwZMW1B2vM3cLAY9Jk19YFFfPscU0= =j1OZ -END PGP SIGNATURE-
Accepted python-coverage 4.5+dfsg.1-3 (source all amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Feb 2018 17:33:50 +1100 Source: python-coverage Binary: python3-coverage pypy-coverage python-coverage python-coverage-doc Architecture: source all amd64 Version: 4.5+dfsg.1-3 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: pypy-coverage - code coverage tool for Python 2 PyPy python-coverage - code coverage tool for Python 2 python-coverage-doc - code coverage tool for Python — documentation python3-coverage - code coverage tool for Python 3 Closes: 890578 Changes: python-coverage (4.5+dfsg.1-3) unstable; urgency=medium . * The “Simona Monti” release. * Document copyright information for bundled files in source: * jquery.hotkeys.js * jquery.isonscreen.js Closes: bug#890578. Thanks to Chris Lamb for the report. Checksums-Sha1: 89b45101c55cc69cf7f4627c951fc2e349dbad98 2554 python-coverage_4.5+dfsg.1-3.dsc 8b75dc4206da96fbeb08a9c50b4b5834784edb40 21196 python-coverage_4.5+dfsg.1-3.debian.tar.xz 9bca38af8f69c932da29d10379ef277d2f17aed0 131028 pypy-coverage_4.5+dfsg.1-3_all.deb 18db4da98679e79a199bf7f601917e925e89d563 26072 python-coverage-dbgsym_4.5+dfsg.1-3_amd64.deb 242257f89c74c2c11bd1b9ad63c38364ce9f10b4 132788 python-coverage-doc_4.5+dfsg.1-3_all.deb ecc3df69b3e55eea9ec700adbcf366f70d159d2a 9927 python-coverage_4.5+dfsg.1-3_amd64.buildinfo f1b3879e3249a51abd2f7e22bcbed27568d70f29 141684 python-coverage_4.5+dfsg.1-3_amd64.deb 8f68b8962a023376a20082eb899d442510905d87 29868 python3-coverage-dbgsym_4.5+dfsg.1-3_amd64.deb c5e313104573583876790643d91a06ad18c74c08 141140 python3-coverage_4.5+dfsg.1-3_amd64.deb Checksums-Sha256: 674c3ecb4328b1ec57f46ddaf30e9ae6b2d5defc46c09521c79409f77f8e9071 2554 python-coverage_4.5+dfsg.1-3.dsc bc969efe651fb9a83754d4644d0cd49de4f652310ce64a727ee30bb598bfd3db 21196 python-coverage_4.5+dfsg.1-3.debian.tar.xz e46a029e9869fbf8623ec1884495eeb1f99091fbc3f3da9b13e5888d9aaf753a 131028 pypy-coverage_4.5+dfsg.1-3_all.deb 0d652dc1dc58db00e2d59b82da7dac761949044159f63404e86a2e9015406557 26072 python-coverage-dbgsym_4.5+dfsg.1-3_amd64.deb a928cdd4c01895b70aec7d96736a80a65814e36896c6056b6aae4cad0da93034 132788 python-coverage-doc_4.5+dfsg.1-3_all.deb 644c556eb86762250db6b0aad8b8564caeeae7e9abe1158fee6c1eb8b3c6573e 9927 python-coverage_4.5+dfsg.1-3_amd64.buildinfo 169ca5210fa3e29ca775c6cf6a4b6e55158128f5cad11fea35b32151a1170619 141684 python-coverage_4.5+dfsg.1-3_amd64.deb a7e928105ee5317fe4786cfff44fcd0718a9fbbff7a7866ba5ab25f33b708450 29868 python3-coverage-dbgsym_4.5+dfsg.1-3_amd64.deb 588d49cfb04b4869ca445e8c278742b7791266fdfc905818b97a86250ddbb202 141140 python3-coverage_4.5+dfsg.1-3_amd64.deb Files: a29a71cf89a7b48062b441dfee3f9789 2554 python optional python-coverage_4.5+dfsg.1-3.dsc 9f8ba66586a9596f31f866f8d7267eb6 21196 python optional python-coverage_4.5+dfsg.1-3.debian.tar.xz b6821ed926e07beac7a9583bbfe3aa43 131028 python optional pypy-coverage_4.5+dfsg.1-3_all.deb 85c90bbecab81892ff47833ae283600f 26072 debug optional python-coverage-dbgsym_4.5+dfsg.1-3_amd64.deb 8755b4bee9e029db85756abfe49f3e0f 132788 doc optional python-coverage-doc_4.5+dfsg.1-3_all.deb 47b49de56edd3dc8fd7d57919569f1e4 9927 python optional python-coverage_4.5+dfsg.1-3_amd64.buildinfo 6a7bc836bbb41e4e1bcb01ab890659c8 141684 python optional python-coverage_4.5+dfsg.1-3_amd64.deb 94435ee0c4ba9d78935b5f7e2dc69af2 29868 debug optional python3-coverage-dbgsym_4.5+dfsg.1-3_amd64.deb 4243917adc16c6b79aa558bcc45cf462 141140 python optional python3-coverage_4.5+dfsg.1-3_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlqNGvsACgkQDqWsb2XR 8fcQIQ/+MVgs4a6uvBU0UGioa/pzoS0zRK/JXXW45URWGUulT/8rqs9fnySnERNj OmxBSS6ZKVUWFpgSCVJhEEsDzNau80Er9iAdcJaTsxeInqfzE9oNrpokfoRRD1cU YVbEFa6pWTHmgvCqM9x03ZHtihk0xVfwYOS9ByY4hmTwyPTzD53jVs9eEFg2SmUS FQV2PuLM8ZNuT9wpIFmt72GAaBVPLXSdrXJUNGHStb8ql7c6MZ4xVIu4fW51NFCs ml2gsf/ZMcU/WjYJGGccndIALtKUfr4vof4kn1S5Fa2okxkAfHQV1ZyCDwzU+M98 /NcE/ayRGHqZHt865wmDA2oCeG8qcMi4yufdDUR1IrlzLqwYiwlsvA1Ute5pRn1U T75gAkX/i6D1IO7K7z9DFmHm1yOB9jeAY70K3948zbZ0ruF9bK/F1K68cZEcEO79 dBNoesA88VKWb5pf7Kr/QliXBh9k0Aw5Ncf7zrgo7NSoEa6jSy7wwcc1DUbWrRYp m2lTX3ltE+myc72rDkiroO6oCvnDJ/KnPUVCPIjl+AU8oAgaoKeHwme2KxrjhHHj GnUQsapKljF9T2HMFgQFZsaowutgeyGx3SmuOo/eobCaVqwUZX19VEwPXxYgOz6+ zc2bFcuTZGDCwuA+g7cxydE9yN9/hSYPBJRaZ7vWP5EtAN/fUfo= =q68M -END PGP SIGNATURE-
Accepted python-coverage 4.5+dfsg.1-2 (source all amd64) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 16 Feb 2018 11:56:06 +1100 Source: python-coverage Binary: python3-coverage pypy-coverage python-coverage python-coverage-doc Architecture: source all amd64 Version: 4.5+dfsg.1-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: pypy-coverage - code coverage tool for Python 2 PyPy python-coverage - code coverage tool for Python 2 python-coverage-doc - code coverage tool for Python — documentation python3-coverage - code coverage tool for Python 3 Closes: 889823 890560 Changes: python-coverage (4.5+dfsg.1-2) unstable; urgency=medium . * The “Nadia Benedetti” release. * Build ‘pypy-coverage’ binary package. Closes: bug#889823. Thanks to Ondřej Nový for the report and patch. * Correct install directory in Debian rules. Closes: bug#890560. Thanks to Chris Lamb for the report and patch. Checksums-Sha1: 2f6b33222168c6ad74bcef5cb44dc25da80bfda0 2554 python-coverage_4.5+dfsg.1-2.dsc 1fa6af1d1925bab7b8a22a8b141c6a7b5eec6988 20516 python-coverage_4.5+dfsg.1-2.debian.tar.xz a596038299145d3676d1fb62180bf78f4e13f9ff 130340 pypy-coverage_4.5+dfsg.1-2_all.deb fd2218e9dfa4836ba2f4648ce512e7070aa5c4b5 26068 python-coverage-dbgsym_4.5+dfsg.1-2_amd64.deb 69e49fbd26ef7c421971e61bb2efeefdb014b001 132012 python-coverage-doc_4.5+dfsg.1-2_all.deb da6a2124724897ecf1efc009c7e4dcca5de03fa1 9928 python-coverage_4.5+dfsg.1-2_amd64.buildinfo ac45b7a3fb6faff71aec0897f32957994d198b03 140940 python-coverage_4.5+dfsg.1-2_amd64.deb a52d7a207410c44fc4f365c003d433800879d4fe 29876 python3-coverage-dbgsym_4.5+dfsg.1-2_amd64.deb fea17afcba2d3e6ec6dbcd1aaed00d948065079b 140476 python3-coverage_4.5+dfsg.1-2_amd64.deb Checksums-Sha256: b082ae07edba93e886698fe0025f737ef1c290aba08fa56b586e562d687ae990 2554 python-coverage_4.5+dfsg.1-2.dsc a474ab8e9a1a98ae8fd70ab9f7db2c1d1091f30b571cb6e192ad3e296d727cd1 20516 python-coverage_4.5+dfsg.1-2.debian.tar.xz 96058e22b074c0b1b2083104f613f714b14a58493a3a7f66b6d7f365ff66efae 130340 pypy-coverage_4.5+dfsg.1-2_all.deb 1b4b58752b19f3f228ed9e73c6031e873de84bda1980faf4a4bbc53892d65ca0 26068 python-coverage-dbgsym_4.5+dfsg.1-2_amd64.deb 089baee773ef94efe399dedfb94650bfaaf246785db72ec1dbb7a2fd9d1d5b6d 132012 python-coverage-doc_4.5+dfsg.1-2_all.deb 4a0148ce49f411c4ecf62731c6c1aed533dd410c9d44903349b1e72e2deee001 9928 python-coverage_4.5+dfsg.1-2_amd64.buildinfo d6677e8c3f5822f0abea697c9bbb9876b41e081a3c4bd0e3bbb951f77e02febb 140940 python-coverage_4.5+dfsg.1-2_amd64.deb dba671dc4798f4570b025a1c70c565b137a284765a43dfead679c88e9e706cf7 29876 python3-coverage-dbgsym_4.5+dfsg.1-2_amd64.deb 8715658e7c2a531c02671dc03ffe75c88cef78ecc52df2febdd59fc03756d870 140476 python3-coverage_4.5+dfsg.1-2_amd64.deb Files: c689effe8a0da102b591736ad9d65942 2554 python optional python-coverage_4.5+dfsg.1-2.dsc ec69fcbbeefd2fa21c15f49ef2adf0df 20516 python optional python-coverage_4.5+dfsg.1-2.debian.tar.xz cbc4c5b3d5eddb627b96591e6ab75f83 130340 python optional pypy-coverage_4.5+dfsg.1-2_all.deb fb9146fa4c336634d7a27b965ec43446 26068 debug optional python-coverage-dbgsym_4.5+dfsg.1-2_amd64.deb bfba40edc9478a4bfe0058a7b6331394 132012 doc optional python-coverage-doc_4.5+dfsg.1-2_all.deb 7439ef6f2c0671e2fd426afbac45806a 9928 python optional python-coverage_4.5+dfsg.1-2_amd64.buildinfo 3dc15f0dd0a6d18a4cb6f064f4886e35 140940 python optional python-coverage_4.5+dfsg.1-2_amd64.deb c608cf7d9236b80cf3857e7ca1903196 29876 debug optional python3-coverage-dbgsym_4.5+dfsg.1-2_amd64.deb 01d62478895823689a9e7f306124d505 140476 python optional python3-coverage_4.5+dfsg.1-2_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlqGMc4ACgkQDqWsb2XR 8fcnPA/6A1gBXtgA6Ojr6E6IlTN0MuCuXqocNQUogcmitvdBmFuVwuSKEKEcVQlg EwLFcItVLLXdbp1Vg+SoYmUp1EtQX2NW94fHPIe97LIBE9cq2+z/pU71hEF2eCUu 9n3eHIXPOW3lO/IMvZhqZeI/PlYYnzxSHksY/5Jr//wiw1xRUkamBr03rQlI7ZVy l+uhlgT8RVYGhrK+2GoqUs6JEp+jreZo9nVCo6ongw/9Wgo/6wCPkfpnbVvrVrkx 9BqcSQu0KjTGHoshnFZcA6KIGwgiTeeVRigQrCnbTTtJuydt36K3Ryur6KRqzmU/ 6FNe0v+QfLZwIz+XZ2IkgvDDPm7NwPU6UBKv3Ds7sgAip/mshKv80iLCoeHMBckk WOz+SqAAokTR0yttG9DGeZ1QmKW+p0JDnggrxhISk7OKWP531VO62GATPNv58kC1 1TIwrrLn4cWB52mrFLXwwJguBuOyYcko5udUQIjvC9z8Hhu9aMHxvwTKTY1WwxfO HFMMoIaxzNIKq78U86CZ0B2oAMolqV4S5oq/Rxqnx13vpWydZ1g/5mSmB+4cR1HT tUvSN6HpCwp80U3BOU4x/BQ4/iZBRsTTz6HP2j8H7SyAnxTEO9IjD3w+1je5IM3p uFDKbT71jeieCGchxRy6qJUtILFJUdpLybtV8ghQVdUVYIskrbg= =pMen -END PGP SIGNATURE-
Accepted jquery-at.js 1.5.4+dfsg.1-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 16 Feb 2018 11:41:34 +1100 Source: jquery-at.js Binary: libjs-jquery-atwho Architecture: source all Version: 1.5.4+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: libjs-jquery-atwho - library to autocomplete references in text fields Closes: 878478 Changes: jquery-at.js (1.5.4+dfsg.1-1) unstable; urgency=medium . * The “Nikhil Joarder” release. * New upstream version. Highlights since previous release: * Restores ‘functionOverrides’ setting. * Correct declaration of Source URL. * Correct URL for copyright file format. * Update description of source package for current VCS workflow. * Update Git-Buildpackage configuration for current VCS workflow. * Correct “Section: javascript”. Closes: bug#878478. * Declare architecture-independent build dependencies. * Upgrade Debhelper dependency to version 11. * Declare “Standards-Version: 4.1.3”. * Specify current VCS for Debian packaging work. * Correct filesystem permissions for ‘debian/rules’. Checksums-Sha1: a1526a8cd8258e0812d9d3e26b7b9346feb2cd2e 1962 jquery-at.js_1.5.4+dfsg.1-1.dsc f2d80344cf108ae6fb269e58fea875ddec7f 29461 jquery-at.js_1.5.4+dfsg.1.orig.tar.gz ff3f2404c82dc2b1537d818f3f0d3215f0214c96 5288 jquery-at.js_1.5.4+dfsg.1-1.debian.tar.xz 027f581fbb86e81640d0abfee6f1a5636e68587e 7229 jquery-at.js_1.5.4+dfsg.1-1_amd64.buildinfo be8586992de536f39311d3383cf3f5d70a1cc53b 21440 libjs-jquery-atwho_1.5.4+dfsg.1-1_all.deb Checksums-Sha256: d05a6191eeaae5cdcc348c0fc6a77e6ec06fcd8617d3fca39e8024de930e93f7 1962 jquery-at.js_1.5.4+dfsg.1-1.dsc 6c90a91c72668bf39a6aeae709457831483d521a9d58de19d0301fe928234c83 29461 jquery-at.js_1.5.4+dfsg.1.orig.tar.gz 5f55a3ab58c6ff169944e716d098350df755e76bce2d9b0e8e8f49ed35500e2f 5288 jquery-at.js_1.5.4+dfsg.1-1.debian.tar.xz 9cd5f91784834595bedc85c687ac7df6068abb94a863dea976e0251087f8ecc7 7229 jquery-at.js_1.5.4+dfsg.1-1_amd64.buildinfo 8b37398580b7098a798c8d9b489ca09c5c24d4fdb7b5e920b076c1ee1dcb6261 21440 libjs-jquery-atwho_1.5.4+dfsg.1-1_all.deb Files: b0447fabee3f2701757c764a0ef8daf0 1962 javascript optional jquery-at.js_1.5.4+dfsg.1-1.dsc 002d6560db5cc5e5c9d6471627b66c9b 29461 javascript optional jquery-at.js_1.5.4+dfsg.1.orig.tar.gz f3682597297353eca8e1b09fbd98ad42 5288 javascript optional jquery-at.js_1.5.4+dfsg.1-1.debian.tar.xz cd5870384765fc8163e398376cc2a80a 7229 javascript optional jquery-at.js_1.5.4+dfsg.1-1_amd64.buildinfo 248bb3ce62b4e4c8a9ac0634a3e08f8e 21440 javascript optional libjs-jquery-atwho_1.5.4+dfsg.1-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlqGK4YACgkQDqWsb2XR 8fcOGxAAiQCjWIkC+8wPoeC0Iy1JUerhJYUcCbNATIrnlloJ8KMB5ijXBhqObcFZ BkQvlwzow00yVvLnnE8CDl3ofOXA+gCk2W6NiuW2Ti7zuEnSbTbvV0WedWuXbbSK gaNpsens5PZV22GoKYwqQm0/theLB3fGsAsy3SGdpIIQJRZUEL6IHdzO7T+emXLj SgH+7cK3+avWddBEy2AZuqt/qeoYjnmzSYzQBfJzzN7b8GW0JU0iVGFCuoCydy2D VyXMKq2b9+U3H/4lCwR9nIFJ5y+Xpqy5rUnBVplyQLANc7o7vG8S2hZ1Z0JJHW67 MZ14tzUzrQykfcYWX6CGYTD0N1kHJ4IJRr8TXEnVyvxiZ63/KjIJMhExn3ZquNYA iNWuk1TApD06ttLjoA/x7gdCj9KkkGO2EjqRr6g1nfP5FpXColw4IZ2PtlAYN269 bB/cIFxSc9vO+eIUCjajBihVEa53Q0W6cXgBZg0NNgJM9XhICSHUMcZPB5YSyiLv hTKGUzD3JnEe3jxZ35w6ob2maChc27koN4BdYOwnf0HNnHyeg31K6IByYAdr07mk U7y9/WkFzl4JiiVzn/fwN+vrJLw7/LPRNtgHtsd7yRj7csJX9r4TykupIjzO5Poi y3OrzeUKYC4WFoJHTC96LrRePvDzH6NwoHbYgFQCCOYwa0SmLW4= =tEld -END PGP SIGNATURE-
Accepted python-coverage 4.5+dfsg.1-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 14 Feb 2018 17:12:22 +1100 Source: python-coverage Binary: python3-coverage python-coverage python-coverage-doc Architecture: source all Version: 4.5+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-coverage - code coverage tool for Python 2 python-coverage-doc - code coverage tool for Python — documentation python3-coverage - code coverage tool for Python 3 Changes: python-coverage (4.5+dfsg.1-1) unstable; urgency=medium . * The “Zakir Hossain Shaon” release. * New upstream version. Highlights since previous release: * Support for plug-ins to alter Coverage.py configuration. * Corrected behaviour of ‘include’ and ‘omit’ options. * Specify current VCS for Debian packaging work. * Update description of source package for current VCS workflow. * Update Git-Buildpackage configuration for current VCS workflow. * Override the Pybuild build system detection. The presence of a Makefile confuses Pybuild. Checksums-Sha1: ec7003d936c95dea87016569c540f4456fdcb2ae 2426 python-coverage_4.5+dfsg.1-1.dsc 72cbed57dc41e3729a8730a834377afc1307cd10 340322 python-coverage_4.5+dfsg.1.orig.tar.gz be38700a5349395a919940c99494c6867376f056 20224 python-coverage_4.5+dfsg.1-1.debian.tar.xz da61febf11c6af811be3e929bae6b07f70c26c7e 131928 python-coverage-doc_4.5+dfsg.1-1_all.deb 3e21e43d160dc5e7aaf8cf664166a87ae436f55d 7727 python-coverage_4.5+dfsg.1-1_all.buildinfo Checksums-Sha256: f3fb50ddebf6591cad894009d73f6b294d577914b0bb22a18a17784098cab756 2426 python-coverage_4.5+dfsg.1-1.dsc 11f0384cbd8b06b84e96ce4a1860fa698297623a5444a4b63ce686a067753fbc 340322 python-coverage_4.5+dfsg.1.orig.tar.gz 01fac089c5785e5f71281b76bdacbcfaddbf5dda56384898ff1723f5217af238 20224 python-coverage_4.5+dfsg.1-1.debian.tar.xz cd3ab89aac0fa0a787793d0f460acaa5c5f321d9532caf6aeeb7dfd02411d1b3 131928 python-coverage-doc_4.5+dfsg.1-1_all.deb 322a06eb2fd82d426575c5ddb1351ee0b5c67ad5ba0b96977e48070ebda2fab9 7727 python-coverage_4.5+dfsg.1-1_all.buildinfo Files: 604ceb024910a9a51d276eb402d43523 2426 python optional python-coverage_4.5+dfsg.1-1.dsc b506fb08f9f2a23e47938862c0398998 340322 python optional python-coverage_4.5+dfsg.1.orig.tar.gz 8786e17b8ba31f46fbafc37821edf9a0 20224 python optional python-coverage_4.5+dfsg.1-1.debian.tar.xz 6748d36dcae5159fc804c9dc78fcc3b7 131928 doc optional python-coverage-doc_4.5+dfsg.1-1_all.deb 1831c1701f1beb10a3f23742ccd624b1 7727 python optional python-coverage_4.5+dfsg.1-1_all.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlqD6RoACgkQDqWsb2XR 8feZFQ//QlIuvaHQ0q4XwxO9csxM7YUGNkEd7S563zac9sCCteY/yqiGOy0EBWqX jW8qZ2vnMXOi2z854bHNUvjDuzliLVHG4r9i6jfClCncbTCIXTesFXhdjWzqCSeO jDvk3Juseo7Z9R4AH+DWaSNcfUPpoBkX5CCrY3VPYr1rNlmKkphpzuBKIqNB5WYl p/LPqZJb67d67i9doESVbLPD54gF4wgLGY0ltti9Cv6nQ4AFUfOOxX3P4XRjrlv2 rY6vHlnx+7VpOrAHGWQfQRrtN6a8CAk24kfaA6n4F4CGveDQqRFPIPLmK9ZEiMGI r0P1cXgls4IQxbkqZH5cJlxk1nmdpjpKq4NHVwSsjKqQtNLzWqvEiji5VVdhtkxO cKEU10Ha5viPtkV72VBjy1s9/vDj9ICcmI7GTgHms/5kQSXPaRSNF4KMzb79qGno 07NZHEMxG4Yo9lrqux5NfRRksu/4RIMvv2H3BO3vMGKv2ZCqBsVgfIB6Tw2kYMuS qInqFu5qIASAeeOXbGYJubL2nmFpKpx+hXKMt1XWdD6i8JOs8v3M8jKjpCxFtihd 2Z0dQgAE/SS26Yu2rSHwesubY/i7Q2u1ltFICOdvttsvUpVByytXiSAVx1ZXu+qQ scprqAiOSzcyHHWZxQSkRFXRevVfo/QekB0LTPsZwaYqRI6LASk= =KPzg -END PGP SIGNATURE-
Accepted editorconfig-core-py 0.12.1-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 06 Feb 2018 10:25:22 +1100 Source: editorconfig-core-py Binary: python3-editorconfig python-editorconfig Architecture: source all Version: 0.12.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-editorconfig - library for working with EditorConfig — Python 2 python3-editorconfig - library for working with EditorConfig — Python 3 Closes: 889694 Changes: editorconfig-core-py (0.12.1-1) unstable; urgency=medium . * Initial Debian release. Closes: bug#889694. Checksums-Sha1: e374f77221ba71fbd42b7f92b7871cf7d0caf05a 2218 editorconfig-core-py_0.12.1-1.dsc c5057a20dd8f3af3136679e88057de9f6284b46a 19282 editorconfig-core-py_0.12.1.orig.tar.gz 52c104af3dc8d22862fc7e19989e61260aa56b57 8696 editorconfig-core-py_0.12.1-1.debian.tar.xz 0a6ffe759dacaf2954a31494817e22776ad867f2 6830 editorconfig-core-py_0.12.1-1_amd64.buildinfo 99e049d4e093e9dd6979f1c2e32b280b658a6e4d 18384 python-editorconfig_0.12.1-1_all.deb 69876ac35440b531fefb558c916e74165ce45c3d 18456 python3-editorconfig_0.12.1-1_all.deb Checksums-Sha256: bd2a3516266e9a486b82e77c6ec1095219137c7460b29e6dca5cccbd098f7c46 2218 editorconfig-core-py_0.12.1-1.dsc 8b53c857956194a21043753c9adca5a5b0eaef6cf1db3273a362ddec78f2b8e3 19282 editorconfig-core-py_0.12.1.orig.tar.gz 368425c617257e453377c34605bea4b4c552865702bc626cb3765fdaf5f7755b 8696 editorconfig-core-py_0.12.1-1.debian.tar.xz 2e5819f728174be1ca66c18ad33eb6af081be90154c34b48ea6b5dfc0a6384f0 6830 editorconfig-core-py_0.12.1-1_amd64.buildinfo 26bb1f9d7511e2068d8b81ce8e77944e79dcee74b180cc3f635194a353857236 18384 python-editorconfig_0.12.1-1_all.deb 292690482998cd42e6fc7902fcb4f5e43006b4e9318809f6164371e7d508d27e 18456 python3-editorconfig_0.12.1-1_all.deb Files: c31564efaaa15132cbf4e8a9d43aeca1 2218 python optional editorconfig-core-py_0.12.1-1.dsc d9178fe1da74601b02a68a6310eca804 19282 python optional editorconfig-core-py_0.12.1.orig.tar.gz 61b556b5a6f97e27c2fcaeb75d5a71c5 8696 python optional editorconfig-core-py_0.12.1-1.debian.tar.xz 69b19e607a0711d2ae053ba893e0b99a 6830 python optional editorconfig-core-py_0.12.1-1_amd64.buildinfo ad5bb7e5da5e0b314afda27fb0d08d86 18384 python optional python-editorconfig_0.12.1-1_all.deb 52f1a10e1b51858774e43e9440042189 18456 python optional python3-editorconfig_0.12.1-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlp6SJ0ACgkQDqWsb2XR 8fc/Dw//Q6zPLhveVOj1KrnFQLgBm00KsabEXNakux+1ybxTJyouKNu1Tp+3wVRa ZtAys672CEZeKSWMqEuqhPMixMvFg6AsMJV6/fAol8HgOf3xnN2BThtcADACVysC hpJGVgQ766Mtk/nrFpF2xD4cwiy3U0syrfOp4IQy0Wl2LB8AeRes64NyskgOcyBr 2u2ZL4347xBrYgSwZE9y3lGVk2JjxbW8uZ+Ub4JDQ01GzyTh3JghlmLQs+lzKNUO m2YMFUwRxMZqQWTOY4t515pQSqc4Hu3RXRsJptQv+Rx7Ozs7YR639sGchPnPLUJQ CvuHjwKCElUdlZ6Hz+w5/9+0tQFPGFoJ3+c1XWPVnspJ0sAO/fpD/5KIYW5J/Ru5 3aHZuSiPfkGiLRLefHKAymIzSdwnZxkq9A6XczptxeJreSEYOvglmX5afozc6EGs RzY+f/6f2sWWIXsjSuuzlFa9XN1mT6JF27YoiVT/j+9L+N5fSOTyLDCik4v3vjXu b0ayCUuSPdCsAZqnciHToXkdIIadxHtA8+QUmkzpnQp17Gn3gWASzd7MKA97gW+v 05mSq7CshYRkS1hWrJCN9gWbPp/XKLofK1Ygl3GKe8zoXuLpqkKylorGsqLuoKqo AsYBQuPiVj0LFJEyLinMIPBtqRPWnOK0vXKQpx5/2LknnfpJjx4= =1xnr -END PGP SIGNATURE-
Bug#889696: ITP: editorconfig-gedit -- EditorConfig support for GEdit
Package: wnpp Severity: wishlist Owner: Ben Finney <bign...@debian.org> * Package name: editorconfig-gedit Version : 0.5.3 Upstream Author : EditorConfig Team * URL : https://github.com/editorconfig/editorconfig-gedit/ * License : BSD-2-clause Programming Lang: Python Description : EditorConfig support for GEdit EditorConfig makes it easy to maintain the correct coding style when switching between different text editors and between different projects. . This package installs the plug-in for GEdit to support EditorConfig settings. -- \ “I'm a born-again atheist.” —Gore Vidal | `\ | _o__) | Ben Finney <bign...@debian.org> signature.asc Description: PGP signature
Bug#889694: ITP: editorconfig-core-py -- Python library for working with EditorConfig
Package: wnpp Severity: wishlist Owner: Ben Finney <bign...@debian.org> * Package name: editorconfig-core-py Version : 0.12.1 Upstream Author : EditorConfig Team * URL : https://pypi.org/project/EditorConfig/ * License : PSF-2 Programming Lang: Python Description : Python library for working with EditorConfig EditorConfig makes it easy to maintain the correct coding style when switching between different text editors and between different projects. . When developing an editor plugin for reading EditorConfig files, the EditorConfig core code can be used to locate and parse these files. . This package is the Python library of EditorConfig Core. This is a dependency for the ‘editorconfig-gedit’ package. -- \ 德不孤、必有鄰。 (The virtuous are not abandoned, | `\ they shall surely have neighbours.) | _o__)—孔夫子 Confucius (551 BCE – 479 BCE) | Ben Finney <bign...@debian.org> signature.asc Description: PGP signature
Re: proposal: ITR (was Re: Removing packages perhaps too aggressively?)
Adam Borowski <kilob...@angband.pl> writes: > One issue: on a small screen, crap font and no glasses, "ITR" looks similar > to "ITP", an alternate acronym could be better. RFI (Request for Interest) RFU (Request for Users) POLL (Participate Or Let's Lose this) -- \“Politics is not the art of the possible. It consists in | `\ choosing between the disastrous and the unpalatable.” —John | _o__)Kenneth Galbraith, 1962-03-02 | Ben Finney
GitLab repository logo customisation
Howdy all, Jeremy Bicha has a short post describing how a repository on Debian's GitLab can customise its avatar or logo. There’s a useful under-documented feature I found. If you place a logo.png in the root of your repository, it will be automatically used as the default “avatar” for your project (in other words, the logo that shows up on the web page next to your project). <URL:https://jeremy.bicha.net/2018/01/30/default-avatar-for-gitlab-repos/> -- \ “The great thing about science is we can test our ideas.… But | `\ until we do, until we have data, it is just one more proposal.” | _o__) —Darren Saunders, 2015-12-02 | Ben Finney
Accepted python-coverage 4.4.2+dfsg.1-1 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 20 Jan 2018 18:39:57 +1100 Source: python-coverage Binary: python3-coverage python-coverage python-coverage-doc Architecture: source amd64 all Version: 4.4.2+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-coverage - code coverage tool for Python 2 python-coverage-doc - code coverage tool for Python — documentation python3-coverage - code coverage tool for Python 3 Closes: 887780 Changes: python-coverage (4.4.2+dfsg.1-1) unstable; urgency=medium . * The “Saiful Islam Chowkidar” release. * New upstream version. Highlights since previous release: * Support for Python 3.7. * Fixed a race condition when saving data. * Tilde expansion in file paths for configuration options. * Declare “Standards-Version: 4.1.3”. No additional changes required. * debian/patches/03.remove-hotkeys.patch: * Consolidate hunks, to avoid multiple patches of any one file. Closes: bug#887780. Thanks to Jeffrey Cliff for the report. * Update Lintian overrides for current Python versions. * Use HTTPS URL for PyPI redirector. * Update Debhelper compatibility level to 11. * debian/tests/control: * Update for new filesystem location of documentation. * Override erroneous ‘missing-notice-file-for-apache-license’. Checksums-Sha1: e706290136a92f077c93866e06f42d4418bd678c 2481 python-coverage_4.4.2+dfsg.1-1.dsc 5815499b95c7f49e667b5a87af040f8e7fb2287a 335980 python-coverage_4.4.2+dfsg.1.orig.tar.gz ba0dff1ff1694df21a1a7acaadc0ce257a3df88c 22044 python-coverage_4.4.2+dfsg.1-1.debian.tar.xz c669f69c028898809b87453cff54b4ef55868841 26068 python-coverage-dbgsym_4.4.2+dfsg.1-1_amd64.deb 1a0cc724c3acf9e7bf9bb5df98861c1067dd3f7e 129760 python-coverage-doc_4.4.2+dfsg.1-1_all.deb 10c6ca5f0c54b7ece92d41b1dfcc7e460bb66906 9558 python-coverage_4.4.2+dfsg.1-1_amd64.buildinfo 2fb45c6a53d6626dc2b1bc6bcc74858c487ed147 139180 python-coverage_4.4.2+dfsg.1-1_amd64.deb f5b9c8759edcb24138c1f70496a1e2e5199f7313 29848 python3-coverage-dbgsym_4.4.2+dfsg.1-1_amd64.deb 023e548f01f7f4a109a92f8e79219da661c3021f 138684 python3-coverage_4.4.2+dfsg.1-1_amd64.deb Checksums-Sha256: 2afdc18b0dfb0fab19a9ecb2538c21cd30c9b62e32aba38ec70152f731fe 2481 python-coverage_4.4.2+dfsg.1-1.dsc d9cc97ef3cfc450f73b24754585949fa393d18eaa9a0b38167df6f2253188901 335980 python-coverage_4.4.2+dfsg.1.orig.tar.gz 34d93bfcf52c9dc53aa21c31faa9ae308af16062d146035e2690da2589b2ad1b 22044 python-coverage_4.4.2+dfsg.1-1.debian.tar.xz fcf18de9c5ece8c6d85e27de7648872f11f68f4f7e5ac04a28dcbc3ee71f003f 26068 python-coverage-dbgsym_4.4.2+dfsg.1-1_amd64.deb 9ca9e0df398660a4ba0186e44cd0a2d704a62a038f4afc92a68899588819ec39 129760 python-coverage-doc_4.4.2+dfsg.1-1_all.deb 67571d4630b8d6cac4abb75e398c7e07da98854a775f46d01db4bd28eb768682 9558 python-coverage_4.4.2+dfsg.1-1_amd64.buildinfo 60e375326334540d903bb5657f12c86a4e58a8b6695714a857b871fb1f47dd82 139180 python-coverage_4.4.2+dfsg.1-1_amd64.deb 6050e1b579ed3f7ec200ceadcb2d4b9b28131b4a2949c722b6e5d2110fd41b91 29848 python3-coverage-dbgsym_4.4.2+dfsg.1-1_amd64.deb 48751c902b928e08713d074a3f4cde96700c5701d21e4135ef5fa1e7f169d34e 138684 python3-coverage_4.4.2+dfsg.1-1_amd64.deb Files: 0657a8c68785b485f3ce68598ee78699 2481 python optional python-coverage_4.4.2+dfsg.1-1.dsc e9ea082a12d0bd8afda325b50a617b14 335980 python optional python-coverage_4.4.2+dfsg.1.orig.tar.gz 57e86b94e0dfde81dd9e90ce21008b2c 22044 python optional python-coverage_4.4.2+dfsg.1-1.debian.tar.xz 601bbb5ebd488fb97af2155e3ab213dc 26068 debug optional python-coverage-dbgsym_4.4.2+dfsg.1-1_amd64.deb 64a2eb840e1844388b344c219e989ff7 129760 doc optional python-coverage-doc_4.4.2+dfsg.1-1_all.deb fbc4bfa5c6d16a22d6c3ecba88807d85 9558 python optional python-coverage_4.4.2+dfsg.1-1_amd64.buildinfo b9fd90840048ee3440f1de23cd28d164 139180 python optional python-coverage_4.4.2+dfsg.1-1_amd64.deb efee7321f9ccc706918b33e62a73 29848 debug optional python3-coverage-dbgsym_4.4.2+dfsg.1-1_amd64.deb 2a6594c9f8b3fdb5a7274b029825a1dc 138684 python optional python3-coverage_4.4.2+dfsg.1-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlpkJL0ACgkQDqWsb2XR 8feYsg//dHO6+0hya4Sq27wdtwYVdel/TyK/cXEahYavu8bQC+6eYncEFrjTC5uD DqMwIA3Ql53MW+qQZD7dhKUCccTqcYwpRghj3axFKcw7bG7j+IYEIqAOi6Icw+tG GdjVyz5hwVuYUp16I3GXTWGBYHU3shcdjS0wwIqK1aZkgo9jTXPSxGps1bSrW+5I YEzQyfILk4vkK4sA/Md3+1DHwGVw1+K8K7y/1WKdEdLahR6heu0gthYys4a9sOFd XUR40GLU5lTRc7pYry24RM+nSv36zcgdplXBJX9QtvzyXjTmgCozcnB4aTUPujaL 261ZmnrWHVwRvp9mhAgxpqI3JdTlLozR6jW6Z2as4UeKUQnhfACQiqCl7UiUD/qo 6U+URWzCyRFKxIRyaTlKCIgkwIsadm50He+CyjLbPqcvSM+ubd06/T2pBeCmKEAc UZyXlx4GRsqcONnURT78cvemre3u8wWp25PMG6mjme9BQM/SZw9Ye6uoxOHlBewC xWUamOcocOJERmZh1kCj/u0hi/2/LrXnwuD66gV3oZGo6MccHwxFI5W0Yrkhs
Serving repos from salsa, via ‘anonscm.debian.org’ URLs (was: salsa.debian.org (git.debian.org replacement) going into beta)
Guillem Jover <guil...@debian.org> writes: > But this still leaves all checkouts that will also need to be updated, > which is way way worse than the changes required in debian/control, > documentation, wiki, etc. :( I also mentioned this when we moved from > git.d.o to anonscm.d.o. This is an issue I haven't seen addressed with a solution, so far. We're being asked to migrate repositories, published at ‘anonscm.debian.org’ URLs, to a host that won't serve those same URLs. People who have ‘anonscm.debian.org’ as a remote URL should not, IMO, be expected to know about this move; nor event to check a website prior to the move (because there's no indication, from accessing that repository with Git, that anything is expwected to move anywhere). As Guillen points out, having the existing URL serve a moribund repository, while the repository continues development somewhere else, can be avoided – the domains are both in Debian Project control – and should be avoided if feasible, IMO. So it's important to keep ‘anonscm.debian.org’ working to access the same repository at the same URL, after it moves to ‘salsa’. What is the prospect, having migrated a repository to the salsa.debian.org host, to continuing to serve the repository at the published ‘anonscm.debian.org’ URL? -- \“A right is not what someone gives you; it's what no one can | `\ take from you.” —Ramsey Clark | _o__) | Ben Finney
Re: Why do we list individual copyright holders?
Marc Haber <mh+debian-de...@zugschlus.de> writes: > On Mon, 18 Dec 2017 20:01:12 -0500, Jeremy Bicha <jbi...@ubuntu.com> > wrote: > >I was forced to spend a few hours doing a thorough copyright file > >earlier this year for mozjs52 which is simply the JavaScript engine > >from Firefox 52 ESR. I first tried copying the Firefox 52 ESR's > >copyright file (removing the extra lines that didn't apply to this > >more minimal source) but it wasn't complete enough. (mozjs52 is > >essential for GNOME Shell 3.26.) > > In the long run, this is going to keep big software packages from > being packaged for Debian. We (the Debian Project) don't have to accept being the *only* ones shouldering this burden. Large upstream organisations have large shoulders. Surely a team responsible for a large code base also must – to avoid self-delusion – confront the need to know, with confidence that comes from standard, verifiable documentation, the provenance of works from which their code base is derived. This is quite apart from any requirements the Debian Project has; it is part of distributing any work that derives from many copyright holders over a log history of changes. Our conversations about this with upstream maintainers can, I think, more often be collaborative in nature. Instead of appealing to only one party's policy, appeal rather to the common need for this knowledge to be gathered, and maintained, and recorded somewhere, in a standard format for reference by anyone when needed. -- \ “The process by which banks create money is so simple that the | `\ mind is repelled.” —John Kenneth Galbraith, _Money: Whence It | _o__) Came, Where It Went_, 1975 | Ben Finney
Re: Has Copyright summarizing outlived its usefulness?
Simon McVittie <s...@debian.org> writes: > On Wed, 13 Dec 2017 at 23:10:51 +1100, Ben Finney wrote: > > expecting to find “complete copyright holder information” such > > that we can be confident it *is* complete, solely in the upstream source > > is a folly, in my experience. > > Given that, on what basis can a user of the package gain value from > our claim that the complete list of copyright holders is present in > debian/copyright? Because that file is typically a record of a specific effort to *acquire* that information, and to document it for people who are careful about the provenance and grant of license in the work. The upstream source typically does not have that property, which is why I'm saying ‘debian/copyright’ is valuable for that in a way that can't be had from a typical upstream source work. > For non-trivial packages it almost certainly isn't, because if the > upstream maintainers (who gate all contributions) don't know the > complete list In my experience the information can be had from the upstream people, in many cases where it simply isn't recorded reliably or coherently in the source work. The distinction I'm drawing is in response to proposals in this thread, to declare the record in ‘debian/copyright’ to be obsolete. Some proposals have advocated that we rely on finding that information solely in the upstream work. I'm pointing out that's comparatively unreliable, by comparison to the current – admittedly under-resourced – concerted effort to find and gather and standardise and maintain that information for the benefit of people who want to quickly find the freedoms granted and who specifically grants those freedoms. > > This effort is rarely undertaken to completion in the general > > free-software community. > > Yes, and rather than seeing that as a source of disappointment with > the general free software community and demanding that our volunteers > spend heroic amounts of effort on doing it ourselves, perhaps we > should consider why it's rarely done, and spend our volunteers' time > more wisely? I agree that the burden falls unfairly on Debian Project volunteers. I prefer to have our volunteers push that responsibility upstream more often, making it a norm beyond our project and into the broader community, to expect that the information can be found. And gently, diplomatically, promoting the importance to any potential free software recipient of knowing the provenance of a work's copyright status and provenance. > Linux distributions exist, they don't attempt to list every copyright > holder on the Linux kernel, and in practice this is fine, which > suggests that this is an ocean we're trying to boil as a weird Debian > thing rather than because we actually need to. It's fine to have weird > Debian things that we do because we're Debian rather than because we > absolutely need to do them - but when we do, we should be clear about > why, so that we can stop enforcing them if the cost (mostly in > maintainer time and motivation, our most valuable commodities) exceeds > the benefit. I agree with the need to be clear about why. I hope this and other expressions in this thread have helped make it clearer. As you describe, the Debian Project has a long history in the free software community of leading by persistent example, on a basis of well-reasoned principle and informed by fact. I think this can continue. -- \ “If consumers even know there's a DRM, what it is, and how it | `\ works, we've already failed.” —Peter Lee, Disney corporation, | _o__) 2005 | Ben Finney
Re: Has Copyright summarizing outlived its usefulness?
Steve Robbins <st...@sumost.ca> writes: > On Sunday, December 10, 2017 11:11:20 PM CST gregor herrmann wrote: > > My understanding is that a license without any information who puts > > the software under this license (i.e. who is the copyright holder > > who can grant these rights) is incomplete. > > OK, but surely it is up to Debian to choose the form of such > information. For instance: each binary package is unambiguously linked > to a source package; said source package is easy to locate and > contains the complete copyright holder information. That last point – whether it is easy or even feasible to locate the complete copyright holder information merely by inspecting the upstream source work alone – seems to be a particular issue in this discussion. While the upstream source work is easy to locate for a Debian package, the difficult task is locating *within* that upstream source work the complete set of license grants that apply for the recipient. If you're claiming that the *complete* copyright holder information is to be found there: that is rarely the case, in my experience. Perhaps for some simple, young, small, one-person works, written entirely without deriving from any other work, by someone diligent about recording their specific copyright information. With works more complex than that, or those that have some history, or some combination of existing works, or even those developed in the “throw it online and copyright be damned” world we increasingly seem to inhabit, expecting to find “complete copyright holder information” such that we can be confident it *is* complete, solely in the upstream source is a folly, in my experience. The frustrations expressed by many in this thread are keenly felt by those who interact with copyright, and not just by Debian package maintainers. It is a lot of effort for a software project, open to collaboration from the public at large, to record tracks carefully enough to show the specific copyright holders and license grants, and therefore to show provenance of the claimed grant of license in the work, to some later recipient who needs to be sure of their status under the law in most jurisdictions, and who may not have easy access to contact the copyright holders even if they could know who those are. This effort is rarely undertaken to completion in the general free-software community. The effort of figuring out who holds copyright in a typical published software work by the time it gets to the Intent To Package for Debian, is therefore difficult. It remains a significant effort after that, to keep the information updated as the upstream maintainers continue to make changes that potentially affect the copyright status of the work. I assume we're agreed that it is necessary, in order that the Debian Project can be confident we know the provenance of that work; which itself is necessary to justify our claim to have received from the specific copyright holders of the work some specific grant of license (which we then grant, in turn, to Debian users). To my mind, that effort – a precondition of confidently asserting the copyright information and license we intend to grant to Debian users of that software work – results in valuable and hard-won information typically found in no single organised place. As such, that information should not go unrecorded, it should be in a standard location for the purpose of viewing the asserted copyright status and enabling future verification of those claims. That IMO is a principal value of recording the license grants, and the collated information about the copyright holders, in the file ‘debian/copyright’ in a package. > In the medical device industry, regulators allow vendors to use the > "least burdensome" means of complying with a given regulation. At the > risk of sounding naive, why can't apply this principle to copyright? A naive answer might be: Because upstream copyright holders frequently do not provide, in the work itself, sufficient nor complete nor standardised documentation for us to use in complying with those requirements. So we present in a more standard (“least burdensome”, for the community members who want assurance of compliance) format, our best understanding of what evidence we have of our claim to the copyright information. -- \ “I knew things were changing when my Fraternity Brothers threw | `\ a guy out of the house for mocking me because I'm gay.” | _o__) —postsecret.com, 2010-01-19 | Ben Finney
Which files should go in ‘/usr/share/common-licenses/’? (was: Has Copyright summarizing outlived its usefulness?)
Wookey <woo...@wookware.org> writes: > On 2017-12-08 01:42 +0100, Markus Koschany wrote: > > Why don't we add all DFSG-free licenses to > > /usr/share/common-licenses or /usr/share/free-licenses instead? > > I would second this. It seems odd that we only have a small subset in > common-licences so I often end up finding/copying in a copy to the > copyright file by hand. This seems like makework. I am sympathetic to this. There is significant value in being able to put a “License: GPL-3” paragraph that doesn't repeat the entire GPL v3, and instead refers the reader to ‘/usr/share/common-licenses/GPL-3’. The files in ‘/usr/share/common-licenses/’ get installed on every Debian system, by the ‘base-files’ package. This is needed because that allows ‘/usr/share/doc/…/copyright’ to refer to a file there, knowing it will be available. If I understand correctly, the justification of putting a file there must include that it is overwhelmingly more likely to save *storage space* overall (by reducing the space in a corresponding number of ‘/usr/share/doc/…/copyright’ files), especially on machines that have low disk space in ‘/usr/share/’. So I think we should specifically ask the position of people who have expertise maintaining machines with very small disk space: How to judge which files should be unilaterally installed in that directory, in the hope of saving not only the efforts of package maintainers, but also the storage requirements on storage-constrained systems. -- \ “It seems intuitively obvious to me, which means that it might | `\ be wrong.” —Chris Torek | _o__) | Ben Finney
Re: Has Copyright summarizing outlived its usefulness?
Ian Jackson <ijack...@chiark.greenend.org.uk> writes: > From what I've seen of the ftp review process, the file-by-file > information is invaluable to ftpmaster review. As in, the ftpmaster > review would probably be impractical without it. ftpmaster review > necessarily focuses on the contents of the source package. It is also invaluable, from what I can tell, as a common reference point between what the *actual* copyright information of the work is – something that can only be inferred, and that can change as the work changes – versus what the maintainer *has inferred* as the copyright information of the work. Without that, it's very hard to talk about differences between what the maintainer thinks is the case, versus what information is actually in the upstream work. > That the information for ftpmaster review has ended up being shipped > as the user-facing copyright notice in the binary is arguably not > ideal for some of the reasons we have explored here. Agreed. Though I don't know of a better way, today, to serve the purposes described above. > So we go with what we have, and what we already have a mechanism for > auditing. Thanks for expressing this succinctly, Ian. -- \ “It’s a great idea to come in unencumbered by dogma but you | `\can’t also be unencumbered by evidence.” —Darren Saunders, | _o__) 2015-12-02 | Ben Finney
Re: Debian Stretch new user report (vs Linux Mint)
Jonathan Dowland <j...@debian.org> writes: > On Sun, Dec 03, 2017 at 09:17:59PM +0100, Thomas Goirand wrote: > >I at least, and probably a lot of Debian contributors, would start > >hating Debian for promoting hardware that needs non-free drivers if > >the non-free ISO was the default one. > > Are we promoting hardware that *doesn't* require non-free firmware > (not drivers, there is an important distinction) at the moment? I don't know what is meant (in either message) by “promoting hardware”. What does an assertion of “yes, we promote such-and-so hardware” imply? The implication that seems most sensible – we promote hardware to the extent that we produce the Debian operating system supporting it – would mean, AFAICT, that the Debian Project does not promote hardware that needs non-free drivers (because the Debian system does not provide such non-free drivers); and the Debian Project promotes hardware that doesn't require non-free firmware (because the Debian system by default needs no extra drivers for that hardware). > I don't think so. Where are we prominently explaining the problem? > Where are the links to the unencumbered hardware that people > could/should be using instead? This rhetorical question suggests that it's not the place of the Debian Project to promote specific hardware. I agree with that. On the other hand, we recognise, and can certainly draw attention to, hardware that works with entirely free software; and we can refuse to lend our effort to any reduction of software freedom for our users. > Are *you* using non-free firmware? The machines sold by, for example, ThinkPenguin, work with the latest Debian release, without non-free software. There's one example, which responds to the rhetoric of that question. That distinction – there is hardware which works with entirely free software, and we work to keep it so – is one of the most valuable things the Debian Project does, and is why I work for the Debian Project. There are, of course, hardware vendors that expend a lot of effort in opposition to that goal. That does not justify the Debian Project retreating from that goal. > I can understand the discomfort of grasping this nettle. Likewise, the nettle of pressing for increased software freedom is difficult to grasp, but IMO core to the Debian Project. > But are you completely closed to the idea of revisiting our core value > documents at all? The Social Contract and DFSG were written a long > time ago. Should the project not be open to looking at what our > collective values are today, or are we beholden to the terms layed > down by braver people, all those years ago? Any idea is open to examination, I'd say. But this thread has not presented any salient reason to retreat from the core values of the project. Indeed, the facts presented in this thread cast into sharp relief the urgency of recognising and pressing for software freedom. -- \ “I have a large seashell collection, which I keep scattered on | `\the beaches all over the world. Maybe you've seen it.” —Steven | _o__) Wright | Ben Finney
Accepted xkcdpass 1.14.2+dfsg.1-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 02 Dec 2017 16:36:45 +1100 Source: xkcdpass Binary: xkcdpass Architecture: source all Version: 1.14.2+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: xkcdpass - secure passphrase generator inspired by XKCD 936 Changes: xkcdpass (1.14.2+dfsg.1-1) unstable; urgency=medium . * The “Xulhaz Mannan” release. * New upstream version. Highlights since previous release: * Improved robustness of interactive mode. * Switch to EFF Dice-Generated Passphrases wordlist as default. * Add word lists for Spanish, Finnish. * Repack upstream source to avoid files not known to be DFSG-free. * Specify current VCS for Debian packaging work. * Specify the HTTPS URL for copyright file format. * Declare “Standards-Version: 4.1.2”. * Declare Debhelper compatibility level 10. * Correct the ‘dh_auto_build’ invocation. * Switch Git-Buildpackage to building source package from VCS overlay. * Convert UScan configuration to format version 4. * debian/patches/use-current-interpreter-name.patch: * Correct the assumption about Python interpreter program name. * Update Debian packaging license grant to GPL v3 or later. Checksums-Sha1: 2dcfd6b9d9b60f5ff7916bc5e4b4ca6955a5d067 2028 xkcdpass_1.14.2+dfsg.1-1.dsc 2866a841747210ef721bb40b6e12d2fd65195373 980268 xkcdpass_1.14.2+dfsg.1.orig.tar.gz 1a2f68069afd446dc51b1884efe6c8d63515fa4a 12536 xkcdpass_1.14.2+dfsg.1-1.debian.tar.xz c2df46b20366c2d3defe716187e0aee6117092ff 710728 xkcdpass_1.14.2+dfsg.1-1_all.deb 1082a656d3f38ce7d8b6eed814076704d8c9133d 6237 xkcdpass_1.14.2+dfsg.1-1_amd64.buildinfo Checksums-Sha256: 104cca6c5ded482d65485b140c607f22afbb30afe6fdd1fb45b312cc0a93b475 2028 xkcdpass_1.14.2+dfsg.1-1.dsc 1502f3822140edc36fef8e8bb309fb5a2eacfd831bf21989672066d0809237a5 980268 xkcdpass_1.14.2+dfsg.1.orig.tar.gz ae0670d91023a96702b50dade6abfefbe8fcf3c8523c870ecbeafd730a3508e7 12536 xkcdpass_1.14.2+dfsg.1-1.debian.tar.xz 81edfebe14b57828d668e34f393432d51da11fac1728c967f9c9857264d54176 710728 xkcdpass_1.14.2+dfsg.1-1_all.deb b6df4a8b0ebb24183224834b5ab5fbc4d59a3ed0649c083dd7886e608ab55988 6237 xkcdpass_1.14.2+dfsg.1-1_amd64.buildinfo Files: 096f4b812f3dc66440417d6e43b3b185 2028 admin optional xkcdpass_1.14.2+dfsg.1-1.dsc 1b13632a9c562ce1190248da727bfd77 980268 admin optional xkcdpass_1.14.2+dfsg.1.orig.tar.gz 5c2556bc695619193f3acf4ea8573d8e 12536 admin optional xkcdpass_1.14.2+dfsg.1-1.debian.tar.xz 2bf66cc61284e6cdc2d76de7c61949a9 710728 admin optional xkcdpass_1.14.2+dfsg.1-1_all.deb 58f2cc67ba8e914eaaa1f3b2d59727ac 6237 admin optional xkcdpass_1.14.2+dfsg.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAloiaagACgkQDqWsb2XR 8fezGA/+NVnhXPRagZOhoMib3cHLkp8IbH6p6x1W1JP0s2/XioI7iZoSSbaJgRyx JQxUGHormCroGImX+G0fPRnUfBJkzce2KrS+5tKVIQF3xDwyDlFZiVuQGNPrc2Bl aNVZ72GfS+89iQ5rsS+zhgHfGK/ZRUhrlVzoRAIA+fmg5LrD5LsMj1rjmB8LXkyS iAXGbqjNW+jB4eyzcxBXgcorYloHKsFXKJOELT3+a/iYE/ck65wKzrnCBCfxdzZk wRraoFX9Bi5k+a1D2ZHwTnuDGZvy0iK/dMcukPIMl9KrwY9uCdimMHBqzCQ6nfQ8 nNcp9sckUM/FfwYj7iAOQvqLgEem1KYfznxevwy1rTWK8aVJLi3VFFAyKmnKB7+Z vEUBv8obaqnITR/x09SaxD0eZFuyAxly2wsnOAPkqcGmNfKUzjdIUO/patDmlMh+ rKlCqbaw2jEzhfC/oUXvkAB+jv2MzSXMFsfjT8Z6+0ac8RNhYd3N6xHuBzPah/RX UEuU3y+3Ywy1YKBC7/Ol3sKcnLS1WJzbt2ukZENigXnBD1tU9ecEsptFdIAbBmHa mi3QPbCqGH4ov4fZw//j53H4FgnoZ+puyYJHSyAA1LI+1S3PoEEBt0gH6ZiDIdby HDQnBlG2/VxVzEYU/iaOqiL2Dn4hOgz9XcbVF6K6QO8tkrGKoeE= =Z+Qk -END PGP SIGNATURE-
Accepted pyethash 0.1.27-1 (source amd64) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Sep 2017 15:53:58 +1000 Source: pyethash Binary: python3-pyethash python-pyethash Architecture: source amd64 Version: 0.1.27-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-pyethash - Ethash proof-of-work algorithm — Python 2 python3-pyethash - Ethash proof-of-work algorithm — Python 3 Closes: 872602 Changes: pyethash (0.1.27-1) unstable; urgency=medium . * The “محمد صالح البجادي (Mohammed Saleh al-Bejadi)” release. * Initial release. Closes: bug#872602. Checksums-Sha1: 99fd91567cea0bf584b642779f08e8dde07956b2 2092 pyethash_0.1.27-1.dsc 819a514a11f2e58444b322598247fb21c677cd1d 38652 pyethash_0.1.27.orig.tar.gz aae9d7d5eeb9f25ced1f8c9185390e591842d867 7272 pyethash_0.1.27-1.debian.tar.xz f29b14eb3d0b6cbedb435e2cbf5bb63fa2d95769 7718 pyethash_0.1.27-1_amd64.buildinfo eab51b64f2490245d083cb2ca9e1d16693213b0d 28064 python-pyethash-dbgsym_0.1.27-1_amd64.deb f0c9fe49e37915c3fa761b9bf484ef75d069c77b 20628 python-pyethash_0.1.27-1_amd64.deb 09f72502d8db934615e2a5a77a56b6835913e85a 50384 python3-pyethash-dbgsym_0.1.27-1_amd64.deb 436610d3652a65b3c66bb19f62caef4774efdda0 20886 python3-pyethash_0.1.27-1_amd64.deb Checksums-Sha256: c8cf63abd35f0762d7de36290293f7497236ad367fd14350a5f8ab4ec960f215 2092 pyethash_0.1.27-1.dsc ff66319ce26b9d77df1f610942634dac9742e216f2c27b051c0a2c2dec9c2818 38652 pyethash_0.1.27.orig.tar.gz 9fe216bc1120d5b4370ecbba3cf181eaa27b5964c62721d1b7107912844cd02a 7272 pyethash_0.1.27-1.debian.tar.xz a0a15debd8bee6cf3d07b34aac868e7bf53c07d8c055f94cc1400f75539c2f98 7718 pyethash_0.1.27-1_amd64.buildinfo 78cb8bd8a6953c6888cd4b94b520db2e7ec4dda1437d6abf7d790e0b6baf8ec5 28064 python-pyethash-dbgsym_0.1.27-1_amd64.deb 6fe4dfdebafcd4a410965554def1d58eed958fddae0729cd85daa3dd2a683cc3 20628 python-pyethash_0.1.27-1_amd64.deb f58d9ea52e23f1b510789a966f9310a0b6a5ed7999cc4c16ea887bbce9aa8486 50384 python3-pyethash-dbgsym_0.1.27-1_amd64.deb 45e04d33eb8a5a24ba5cd5fe3d227d5fc3ec17f4514113fc27fa102a6d20db65 20886 python3-pyethash_0.1.27-1_amd64.deb Files: 91e8d4c669536215b60f03faf08a5df3 2092 python optional pyethash_0.1.27-1.dsc 0ede7aff7f9279b2451ecdb187b91590 38652 python optional pyethash_0.1.27.orig.tar.gz 51aa0c739ab5bcf0efdc12ddece6a0c3 7272 python optional pyethash_0.1.27-1.debian.tar.xz dc7d9baea92241a8abd69f0ff6df5ee7 7718 python optional pyethash_0.1.27-1_amd64.buildinfo ccc58e033d926c25fe6b0a2b107520cc 28064 debug optional python-pyethash-dbgsym_0.1.27-1_amd64.deb af26f5e6d6b501a2a1d269e16f673f5f 20628 python optional python-pyethash_0.1.27-1_amd64.deb 26f29082d22db55ece49ebdc463c67d3 50384 debug optional python3-pyethash-dbgsym_0.1.27-1_amd64.deb a2278f7d8fa04994ecc245c07447a7b5 20886 python optional python3-pyethash_0.1.27-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlm3jpkACgkQDqWsb2XR 8fdu2Q/+PyXJXJ+LlcJVPyQqLs/X7OP9gaZ0EhC0W1sQOIinlNd9Yw+TKjAPA3NO LN7aTFkosKFrZ7t0JcBEr3dvt4Tancjrp/dQDiNvMsrCRluEZRhnmXMaOJ4FKeN5 zfb4k7hpl8EBx6w4NGO8pVHYt0KAleLIm7/8cGARgtAm8tExT14/qhjxoY3gTqec maaXkxaXNmTqBP8i9qdh65GY71CuoKoEPeCUk/g/ETm3CkvqxDt/dN8wTyW5nv3R 0HQwBciRGnMvz/9H27bJrnd0grsrQXz+GBssYUhmd0gfeAcNBTX0avKEKojGmWjG 05j2N/ANl1C1os06R+z5Xn+HvOC4+VSkAWlvsD/vMR7Pb8Zf2aabvcSS+mLkVUO3 noN5UaCVs/W2zoQHsXUTE1A1hna2HAjGBbL6nb2vKKH1luROmlw8904RiD6KUGTy ncPyjmlYEsIM0uWTykmjQgf1YStOBvMdeNUlFOsFHlU6z9uUCMgyclPMmAVhculS MOYludWMu4REK6/08O2b94dgH9PhELFNhwEwrL93U9JR4Qf0HKz+gTEgYQfCpU/O JDkhGAi9cVjM/vZmtjv0rpYq+oTec43zTxB89oKiopJQ/1vt9uh9/Xt6TsqL1i5m KxqXU+j3q2dO77xt5+1ijxufevxJRVEndqmR3rALT8P+wRMMSwg= =3sO5 -END PGP SIGNATURE-
Accepted pybitcointools 1.1.42-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Sep 2017 07:42:39 +1000 Source: pybitcointools Binary: python3-bitcoin python-bitcoin pybtctool Architecture: source all Version: 1.1.42-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: pybtctool - command interface for Bitcoin signatures and transactions python-bitcoin - library for cryptocurrency transactions — Python 2 python3-bitcoin - library for cryptocurrency transactions — Python 3 Closes: 866519 Changes: pybitcointools (1.1.42-1) unstable; urgency=medium . * The “Rabiul Karim” release. * Initial release. Closes: bug#866519. Checksums-Sha1: 985918836b883423105052248e6edccab61b0626 2259 pybitcointools_1.1.42-1.dsc 9a1261b55abdbc607bf8373b383dc8de839bb997 46029 pybitcointools_1.1.42.orig.tar.gz 785f0d673792946022c340e31d12294a6035edf2 7476 pybitcointools_1.1.42-1.debian.tar.xz 3d4612882048b21f0e7f7eec0be5d6e4468ee788 7011 pybitcointools_1.1.42-1_amd64.buildinfo 3e7bf454b3fac829a9dd3501428595c7ab53 5394 pybtctool_1.1.42-1_all.deb 298cc159ee36ed3a7f8fce8c8f53d3e5ea5a 30176 python-bitcoin_1.1.42-1_all.deb 6966b3e6ed40bac05096f0dc0609b4b9f0847f1b 30202 python3-bitcoin_1.1.42-1_all.deb Checksums-Sha256: e294aa2d61331fa5410b82eed7413b7218fda22fc3af78fbbf62bc5da01fe364 2259 pybitcointools_1.1.42-1.dsc 05479068e0b580d338433d2a41d7f5851bfdd631d1d456e507c1f2500be3 46029 pybitcointools_1.1.42.orig.tar.gz f06b29745c1af2578b0c9e87c453ad0efbf62745c713ce3c17e76be2312a2425 7476 pybitcointools_1.1.42-1.debian.tar.xz b95ec7939231de1e42f2b8f4fe4ee6d3c1fcbae35e6f3d4927719b1c8ef9497b 7011 pybitcointools_1.1.42-1_amd64.buildinfo affde3602e85618e72b4133c1c8f1d13363df3432558378e607bd76b1c3943b7 5394 pybtctool_1.1.42-1_all.deb 9ea7bbe306d2976b905fcaceb65e7039e8825c160d961b52e1e31f69db48ba60 30176 python-bitcoin_1.1.42-1_all.deb 6d6fd8d251922732a2a87fc3ef1c0eab8ea523c3e75d9c728fe5a9b1cbc37390 30202 python3-bitcoin_1.1.42-1_all.deb Files: f70c402293984b05fcbfc272e08a7b20 2259 python optional pybitcointools_1.1.42-1.dsc 53aa81c54f64c36f8fd13ad16a25b220 46029 python optional pybitcointools_1.1.42.orig.tar.gz 1c844254da59a4b34cc40dd382e6eaf5 7476 python optional pybitcointools_1.1.42-1.debian.tar.xz 4a362c0491ea5ac181a9db8a3b5a6c55 7011 python optional pybitcointools_1.1.42-1_amd64.buildinfo 55bc37dc83ac516db800ee79cf6f61f5 5394 utils optional pybtctool_1.1.42-1_all.deb 43fa2001d3b1316f8918a45e6a72547a 30176 python optional python-bitcoin_1.1.42-1_all.deb d61d3b80c5dbc1d77b16049b0d80008e 30202 python optional python3-bitcoin_1.1.42-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlm0bfMACgkQDqWsb2XR 8fdVnw/+MIxpFAF9HEvfJUnYJ0FsYFTHvoGRV19ZB66fXM2rx4d39PWPVOBRUMa0 6+45R+jdSX8kkxDGDDN4ijBM6lYNUSpwiEnVOyEjRJXXtZ2LXfzfCCQ+6PtnjzTK zXN1f1/fPW9tDBog5dA4nNzRtJtr7GuVGXRiZaeAMWttHroTDMP9sqac28WMpzVA HVKbnASATkGCz1ohvh81FJq4KRPFw4rjo8GlANEgmHdf+v5wWwqLf7bol4ZBFri6 6Xz10YtElbghU9CeQ3+Z9SwTnYfnrzAkZ6xZ6/6K0GFAYA0unYLzkpxBzPYS6otA WCQoR9Z5ojSklnuUAYpe55yIUM2SP7N4T7x0pyU8K/XYzt2HL0pcTKqkOAo0A31F XfEEkOCNEy5k2z/6dMb82tcrDKXxR4E66RKUf2nB+tUTwQmPTqIzY3u6KzfE3s4T NjivH+fujH1K20B5g3Vv4PsqJ1BZP/bcc372XusBfWnv4e14oypH+7449bN7BhZM SJVqDWBQW4pp7ThpiomZEmTZYhYiC4fEV+nfIOIU1pzfCXiRkYZV0jzKuqx0cM02 96JySnGsWG5uGKXayr6Xc3FuG/rOz51AoNmv2a8y64CsNAPv2X3P6UE1WZPYOWEz /qs7LgP8P5rHLSAiYRtIft5eY49Jr9s2R6bTFVRxsg3ispZaFiM= =DQ6t -END PGP SIGNATURE-
Accepted python-jsonext 0.4.1-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Aug 2017 21:11:04 +1000 Source: python-jsonext Binary: python3-jsonext python-jsonext Architecture: source all Version: 0.4.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-jsonext - serialisation to/from JSON for extra types — Python 2 python3-jsonext - serialisation to/from JSON for extra types — Python 3 Closes: 873285 Changes: python-jsonext (0.4.1-1) unstable; urgency=medium . * The “علي محمد باقر النمر (Ali Mohammed Baqir al-Nimr)” release. * Initial release. Closes: bug#873285. Checksums-Sha1: d39577962d5ae3d883bda35e808b03bab4e31fa0 2261 python-jsonext_0.4.1-1.dsc 8cf3d14158d56363d26457fabe5472387a48709b 2573 python-jsonext_0.4.1.orig.tar.gz ccc8082df202265de26b3d70e02145e100ba4cba 5540 python-jsonext_0.4.1-1.debian.tar.xz 2436f1a900370a6085ac6353f38ce7b88075b8d7 4658 python-jsonext_0.4.1-1_all.deb 3e3f033c9931890a43cc8e62eec0cbd31405e6cc 7001 python-jsonext_0.4.1-1_amd64.buildinfo 9bfa6415f7f4c031929dd8bdc8488847816c3177 4744 python3-jsonext_0.4.1-1_all.deb Checksums-Sha256: 9b403d74643ff3e4ad73b0ef8f1f6106e88f5207b5845ccf1a97de077ab939ee 2261 python-jsonext_0.4.1-1.dsc 7b2d30762d7009d43804a20681c132cebad40c60382c774efc1b065f76aafbad 2573 python-jsonext_0.4.1.orig.tar.gz 99d80da711c896346e148bc32aef2334deafa712102118ce6fa248726bfa08b8 5540 python-jsonext_0.4.1-1.debian.tar.xz 183616c255469c167e5188f35e003a7878b09e1753c612db9d944928ecf8831c 4658 python-jsonext_0.4.1-1_all.deb e6cd24ac4111f6660d1773de9a1cd2f04c7a1bdd2c38dd3a3d87eea7f3afa5bc 7001 python-jsonext_0.4.1-1_amd64.buildinfo 8a1541c46120a5817b110b77ea9ac22794540017a0cdb73b848262057af38eef 4744 python3-jsonext_0.4.1-1_all.deb Files: b7023cba010d1cd3aa24448ae2a828b4 2261 python optional python-jsonext_0.4.1-1.dsc 50c8dc87004355a8123c52aba2ee3914 2573 python optional python-jsonext_0.4.1.orig.tar.gz cdfce54c52ab4dcf30c1aac61f9171aa 5540 python optional python-jsonext_0.4.1-1.debian.tar.xz 7c9bfaa9b538da441bcd768c0bf8a866 4658 python optional python-jsonext_0.4.1-1_all.deb baaf7ae2df70547b49fb6ff84b755500 7001 python optional python-jsonext_0.4.1-1_amd64.buildinfo 89b0ef64275816b99269a99679569b42 4744 python optional python3-jsonext_0.4.1-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlmhbZgACgkQDqWsb2XR 8fcQ9xAAja0X2Vc+h2NoxgKcrxUg9SKq1vCmelC071fBNuHSqskXPhxLzj5aitup ZshUo6cs6e1TGMi3Khl8xYQb5E5LB0gm41OvOKQn6E9RkvMBR4Vf7x+hF8/bm7Q1 Zt+5k2wZG+Xz9GKv9xptEukOmmjmBDuxlqNvVSTm7qP8Opup5yITgua2De97JTcz GFroaqrvWbZ3vuXSS5Vnj77Whf0uF7yRdiEAU58+quVjYJGgVqcNe85zEFoatJhV yHP42JetLzsYXWT6aHZ7/QuDTQu5+mVw1KCsyQjcuedlkN+rrNWg630VNuIFbhk4 iviH4tIqx7cfkTEuELyxMl8sTSPnNtBmIzwTotiEShqrzyOditcWaY7cPNh6Yk2n 6bpOr4AyNnjEse13E/wTYP+jY9wphhX36/t5LNbDnnfmB/2zvk7MP5u2bu0pmHrU 94rlqrk5OGzLvbQdgxZpVWo43C8xOVl9X5Y0AIrzUw3bapHLsdrcoyowbl5/b6Em 5kNCny9+SFOEWAuZKog+lwkdhs55loaTcM4M3o9eeZ7aBWo6q0Po7RlvgHu/2viM lTvpspA4L5fupUJoTZskDTFvNZxP3DUPMSt6wruBdqPlcDLi1WdcV6fqHDpZbLKg lk5H+Yn6x/7EIkof16ws4A++CfKYoL4t+wU+sasYVDeAeqOxO64= =EE9O -END PGP SIGNATURE-
Easy discovery of ‘debian/rules’ build problems (was: Unsustainable debian/rules as official build entry point?)
Ian Jackson <ijack...@chiark.greenend.org.uk> writes: > After there is only one consumer [of the package-provided > ‘debian/rules’ build interface], it will be somewhat easier to change > [the policy so that interface is not the standard]. >From the rest of your message I infer that the mention of “one consumer” there refers to (current or future) ‘dpkg-buildpackage’, is that correct? > Important consequences of my views include: > > * The package-provided rules interface needs to remain managed as part > of policy (and to continue to have a controlled approach to updates, > etc.). > > * The interface is not *defined by* dpkg-buildpackage: ie it is still > possible for dpkg-buildpackage to have a bug where it does not > implement the de-jure interface. > > * Packages may still need to work around bugs in old versions of > dpkg-buildpackage; conversely, new versions of dpkg-buildpackage may > need to work around bugs in old packages. > > * For a long time, packages should try to be compatible with old > builders which invoke rules directly, even old builders other than > dpkg-buildpackage. I had been under the impression the build tools (SBuild, PBuilder, etc.) invoke ‘debian/rules’ directly, and so are a good way to test that compatibility. Evidently that impression is wrong, and the use of those build tools is not helping to find such bugs. What tools exist to allow package maintainers – as many as possible – to get easy (automatic?) notification when the package they maintain is not presenting a compatible ‘debian/rules’ build interface? -- \ “Very few things happen at the right time, and the rest do not | `\ happen at all. The conscientious historian will correct these | _o__) defects.” —Mark Twain, _A Horse's Tale_ | Ben Finney
Accepted dput 1.0.1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Sep 2017 18:51:25 +1000 Source: dput Binary: dput Architecture: source all Version: 1.0.1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: dput - Debian package upload tool Changes: dput (1.0.1) unstable; urgency=medium . * Upload to “unstable”. Thanks to testers of the Python 3 migration. * Declare “Standards-Version: 4.1.0”. No additional changes needed. * Use current HTTPS URL for copyright format reference. * Remove declaration of Python 2 support. Checksums-Sha1: e8c169ab0af43ffda10712404faa9a14026a49a7 1764 dput_1.0.1.dsc a89c6b992bde4a97d83864a135660d797729d71d 102196 dput_1.0.1.tar.xz a44c5a3f93e064a50f4395500bcf381cb29a4358 54704 dput_1.0.1_all.deb ac80eda8599cb6c50a8a16ee732490f59dd5a9f4 7233 dput_1.0.1_amd64.buildinfo Checksums-Sha256: 21c115d99dfbe09d4b27437ecbe729a93acbda9d5eb15f70de3ec0f8e61d005d 1764 dput_1.0.1.dsc 5c882d8d42857e643ea348c64c310b58844e479157fd68ceee6828a2d53f8b0f 102196 dput_1.0.1.tar.xz 465b05bd0a8c8fdd1809dd336bd65842c65614e5f44c4465ee719adfdab977d4 54704 dput_1.0.1_all.deb 0f4554e57591019848c6ca25303be645ff11068cddeac3e6e16938fc11cc7e58 7233 dput_1.0.1_amd64.buildinfo Files: 6943cc16613b6ac0b47be1474847e34c 1764 devel optional dput_1.0.1.dsc 8114e320dfe219d7f8f7ab8ac3974aee 102196 devel optional dput_1.0.1.tar.xz 1d57cea6df7539c3f8e6336e2a9cd544 54704 devel optional dput_1.0.1_all.deb b28ef2de826d493806c3fe7f6b17a6da 7233 devel optional dput_1.0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlmzsrwACgkQDqWsb2XR 8fdK3hAAjpNSaUcu+QnH0Ly6t3ssA394xDyU316Wphy4H4hyYLbSyV/Pk1VZNbj+ ubhX9NXMqokR71usyJ8PsmRS9aquNHR3MzhQF6OL4o05e6qwcBAYgXuMZlbgDGnh fFezc2nf6XB6G08qwKxi/twe9qy4QN1kdmLmq2AqELb6CJkgZI0vG9Ny96FPkM1T M2qgpqfTyREmb+28/gEKQmVdV2T2LVtRR5/ff08zMd9lxNAcnOsFarrzMV6F8ka4 3/p6kfmlVuAAb211RuL6FKybQew2PTTAEIunSfEuKJFXUx25ozzRisKp7wQChLDA jnWDvweH4oTfnqm9HgkzZoHOYqbGKpMPiOsL4wNpYeUToeZm7nPbhfpQ4NgZX0ln R4Hm6OyjljtuH74EDPF27iblS7HlOIZ1EYvL3Y8PadCt9LQ6iAlcyfHIeW7+4j7J Nbyr0w4106nG4flwviw3kSrWpviLAS3WdRhAD6ihL6GXncNsyQ27iop5iWyb8uL2 JlKRU1UbDOUeO0hzEsj/TKTIjwjUuVmjNSCIxSDG87w6uXYW/AfEi3PfSmo7Wp+e yWyPi/MvUdj+ZpDQwQtP7Pk9gz3AAqra7D2kQeRG8XoECgLHyY6Hw31KpAFwj9Dn NWCBWzJBfLkkUVAim1x3WwrQOGdiXuGnJ4J7ull+frH62NCSGsI= =Mh2P -END PGP SIGNATURE-
Accepted python-coverage 4.4.1+dfsg.1-1 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Sep 2017 17:59:17 +1000 Source: python-coverage Binary: python3-coverage python-coverage python-coverage-doc Architecture: source amd64 all Version: 4.4.1+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-coverage - code coverage tool for Python 2 python-coverage-doc - code coverage tool for Python — documentation python3-coverage - code coverage tool for Python 3 Changes: python-coverage (4.4.1+dfsg.1-1) unstable; urgency=medium . * The “Jogeshwar Roy” release. * Upload to “unstable” suite. * New upstream version. Highlights since previous release: * Some warnings can now be individually disabled. * Plugins can now choose to find unexecuted files. * Errors now go to the standard error stream. * Refresh patches for new upstream version. * Use current HTTPS URL for copyright format reference. * Declare “Standards-Version: 4.1.0”. No additional changes required. * Update copyright years in Debian packaging. * Grant a uniform license for Debian packaging work. * Enable smoke test of installed Python scripts in autopkgtest. Checksums-Sha1: e848576dda94cfbc0d6b83f668df458286e94454 2480 python-coverage_4.4.1+dfsg.1-1.dsc 80984ec22088092e1141ddec170691e7d3b01b79 332320 python-coverage_4.4.1+dfsg.1.orig.tar.gz 0d138d745863bb01916d4d596578a988fd1fe41b 2 python-coverage_4.4.1+dfsg.1-1.debian.tar.xz a912e2acc5d66261f67d202474817ac72cc0a219 25950 python-coverage-dbgsym_4.4.1+dfsg.1-1_amd64.deb 3c873eb38c4f3e0615d8099cd27c66692542da1f 127954 python-coverage-doc_4.4.1+dfsg.1-1_all.deb a5f3981ec1678632d849f5e51dba405572d9cf1d 9713 python-coverage_4.4.1+dfsg.1-1_amd64.buildinfo 4f3189bc719e55c593ed32fe2adb876ed8b079e7 137426 python-coverage_4.4.1+dfsg.1-1_amd64.deb 3e5305c9b0109ca6f83dc81b46f37aad4f233957 55022 python3-coverage-dbgsym_4.4.1+dfsg.1-1_amd64.deb 4791b6f91274b1565cc5d451e2eb05a097e49d16 137240 python3-coverage_4.4.1+dfsg.1-1_amd64.deb Checksums-Sha256: 1eca9e54645d566e2d2d9208738b6a697b8122fb98eb76e0fdbdd476eac9cf77 2480 python-coverage_4.4.1+dfsg.1-1.dsc d49f41fbd9ef91c1f3467c073a3e7ddfb2645f53f20cd05db8abf37cde844249 332320 python-coverage_4.4.1+dfsg.1.orig.tar.gz 62ee7c5d72ff5532d52373aca25c800d14acc311a68643f94149ba2fa86a87a5 2 python-coverage_4.4.1+dfsg.1-1.debian.tar.xz 4294b060bc4f7cc58a95bc29ce7fe70f51bfad98ee5bd46fd806abec080e435f 25950 python-coverage-dbgsym_4.4.1+dfsg.1-1_amd64.deb 4af5123b0b9228222cebc08847be06671ba8ac80c73f21d736ffcc922a468e7d 127954 python-coverage-doc_4.4.1+dfsg.1-1_all.deb a4c6b2630fe5aca2c902f19bc746252b9b2fd768e37ff4059bafe82279277209 9713 python-coverage_4.4.1+dfsg.1-1_amd64.buildinfo bb070a318fced7ee6d195b5c8c0bd26530ff5375988e4405ab369a9423f0a1da 137426 python-coverage_4.4.1+dfsg.1-1_amd64.deb 9d4af6a2a75cb1b04dd9722cf6d994898342a750fec635667a68c2ba6960a47f 55022 python3-coverage-dbgsym_4.4.1+dfsg.1-1_amd64.deb 1d5a1e305acc6bdf6ca1575cdc8f87e15d64613fc5ccb52c96a34aed759402d5 137240 python3-coverage_4.4.1+dfsg.1-1_amd64.deb Files: b09e706d1bcaa6fc5659ec7136d551e9 2480 python optional python-coverage_4.4.1+dfsg.1-1.dsc 7768a136b73c4c1c499c2233d1547241 332320 python optional python-coverage_4.4.1+dfsg.1.orig.tar.gz c31502ab1771c3ab7284abb499dea02a 2 python optional python-coverage_4.4.1+dfsg.1-1.debian.tar.xz fd9beffa15241a87919a58cc42ba0bd2 25950 debug extra python-coverage-dbgsym_4.4.1+dfsg.1-1_amd64.deb 7b2cb63284888ce72358a09cceb0d208 127954 doc optional python-coverage-doc_4.4.1+dfsg.1-1_all.deb 37efd36239a8dcf191da5e500c1df690 9713 python optional python-coverage_4.4.1+dfsg.1-1_amd64.buildinfo 329ff8de1553bf0abb0e9ee6c4e3892d 137426 python optional python-coverage_4.4.1+dfsg.1-1_amd64.deb ccb982a1387c919d31b27946d9f173c1 55022 debug extra python3-coverage-dbgsym_4.4.1+dfsg.1-1_amd64.deb 74066e7432930ee53ae70eb8e14c5026 137240 python optional python3-coverage_4.4.1+dfsg.1-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlmzpKQACgkQDqWsb2XR 8ffWGQ//evALGCiSGR6JhFmupUPIm5mRReNnPQpKW6mqxxNK2sD/ae1BAKell8mL 0HRKmJc0jD1cLvE41XJeSwzxD/Xq6JcTvkx55Fc1gY5QVwAvROvwT6upvpWfCH9Y Y7jNyyto68ZQqriQaAivqOTIUATbO6PQS90TDYkxESaULx/OPJaSBLlhVvCz3RBF 7C2qVfgLM2yeUWphKLJU8dVpaqVhYndGsGxEW1GprQbLomx61rP5TXJs1pHrU9CT 82ZM5m4DByAP+ukHoUGDbaoBptunr7AV8ruHyxm0qRqVDVOkpqINqPfMn9WDuaNR 4nogDrQWDHuF1Zw2PA+EqDkR3KenhMDIC6WpYMR8ix8HgAFg1PpM21ESlfkjVrQt JI8vxmfJB08oHO+TpYuOcmvLifgRaOKvrCsME0H3eUS6jwiYQ91U78A/I0/qqjRl 9Fn0C0dFctHmC4BuElX4SdjWUt3JkZjP0T2w1D1jcfVUX7x9FAu5ER1LwrHyGMC0 l+D5vq3uphDoJag6Yzh/5FpqI9ix8sq6f6+VOln1vuBzqIIyhvsMfDOtc6bo3u66 R1ZZGfbjieZMcAlJ7iwtASz6XqQQGt3PSmhU+HXuuDLNwBivvCgaDeumhU69nhpF 0w3aX5H5BkO37uRWIla42P+00hiLgGhwMFN1+UZL7YiBZ3XBnUE= =BwnI -END PGP SIGNATURE-
Accepted pyrlp 0.5.1-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Jul 2017 05:25:42 +1000 Source: pyrlp Binary: python3-rlp python-rlp python-rlp-doc Architecture: source all Version: 0.5.1-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-rlp - Recursive Length Prefix (RLP) library — Python 2 python-rlp-doc - Recursive Length Prefix (RLP) library — documentation python3-rlp - Recursive Length Prefix (RLP) library — Python 3 Closes: 866168 Changes: pyrlp (0.5.1-1) unstable; urgency=medium . * The “Zuhair Kutbi” release. * Initial release. Closes: bug#866168. Checksums-Sha1: b749fec7eb96af2d9a51b4ea42c89b1d52166e28 2252 pyrlp_0.5.1-1.dsc aa12ae1a2e29c011bf94242a6c445223da6792b2 31299 pyrlp_0.5.1.orig.tar.gz 2dca7441f0a72d208a393535cb6ce564874126d5 5204 pyrlp_0.5.1-1.debian.tar.xz c04855dbdb989a744ece91eb5c089ad49a311156 8195 pyrlp_0.5.1-1_amd64.buildinfo dbbb323bb3ea5eaa0a2ea5f6dd62bd5c9e4a0991 36320 python-rlp-doc_0.5.1-1_all.deb c6817e0283857422126e5094a392ae28f0f6e092 13454 python-rlp_0.5.1-1_all.deb 3e99011e4ab623fe21b17e4bae272d2d82264838 13538 python3-rlp_0.5.1-1_all.deb Checksums-Sha256: c67feca528366ae64ee3edeb9bcec124eebcbd689e3197a29c7336864b742afb 2252 pyrlp_0.5.1-1.dsc 651e253abfea0ab280b24621b4a5ecf0c5d8057fc1f2aaac0a2739ad819fe6b6 31299 pyrlp_0.5.1.orig.tar.gz e599e75db6d6cf10e5fa35cbb4e0646d144fa74578c9b41a5ba24ae31ca0c599 5204 pyrlp_0.5.1-1.debian.tar.xz e1d6c7496b53aa80040f598ae4036bd15b92821f3d327e97a9094b2a28993634 8195 pyrlp_0.5.1-1_amd64.buildinfo f412952bc50c161c699343c8f0280b10cf79bf6dd1cc2df36fed97ab74bdfcf3 36320 python-rlp-doc_0.5.1-1_all.deb b7685f1a47bdc0696d5ea8390c543531150897b82d8183681442c8ae2b5d61b2 13454 python-rlp_0.5.1-1_all.deb 87eb41c9359710a2b8a3abfaa14ec13fddd5e99e4e185b4a50693371f00d70b9 13538 python3-rlp_0.5.1-1_all.deb Files: 7edad6450905db04f898f479035d5969 2252 python optional pyrlp_0.5.1-1.dsc 4b2dfa70d2af7522c2ec71232f95b905 31299 python optional pyrlp_0.5.1.orig.tar.gz d305171dd5102f20021246d89685c073 5204 python optional pyrlp_0.5.1-1.debian.tar.xz 07cb86537dfa2835cfaf7f67eb825fc0 8195 python optional pyrlp_0.5.1-1_amd64.buildinfo c600849cfd9a8b6fc1ebe5184a739867 36320 doc optional python-rlp-doc_0.5.1-1_all.deb 102c2ca185ff20fdb2e675de4910e635 13454 python optional python-rlp_0.5.1-1_all.deb 8145b27e048d93ecc561a9b1b6eebb4f 13538 python optional python3-rlp_0.5.1-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAllpIssACgkQDqWsb2XR 8ffihg//Sn2z8GhkaEqgsInOAjq/g+S6mMdv0RLCU/0QVjfz7vG8tzdRX80WqQm5 f7OaqLVFoKBrPKcqN9pIMPHQlKT+pXcRjoxgCbWam8HbonForbQChuv75jenJ5UV pTIVmSegtoHTRf0cUrBVZns8pmnnLSlAUMTbAsmmJ+LL8Ny4XzeKlndW5IjnarIP H93MKgh6o1lTIiB2/LR29bXv5Gqh7lxwQYbVoccSTOwcC+6aDWbEsi/EcIEcN90V tvQUTaJptqLHBRR32Peu11VuYwGs/Jk2tv7XtfK7rAdb0JIh8G643RjOhbJb1NB9 jYAlqHM8oE3H00MmOt2ub9aI1vsAgeLxOOtnmrnC4BxPmtizq2EWNUE4pfNIzl31 0VJcpVr0F71z0uWJGaT2Ujidz9WeuTW7r8GCTSEUck1/JzXPQLSrOmm44RVWyTJI 37CBIMBZ46lw/YHEF+1zULk2mcVCZybaV4toczlOUR6MpRdABKGBJMiG2BEGZ6KI gMu2ZovwjzssI6MD4n8IkwabEpXulkQqw80aOtYhd3VMTWBX45yEJCjWHj297djK T/5VmVSAjsK3uDsoRmtQPnPVKOEcAaArKW4JhZFVMeaZboic63jeMIXtPmQdWK97 VcfJOeMCUQuhYdG6KtxUscXWAoHJ4/cn033cMfSliy2LQgwQwg0= =4JmP -END PGP SIGNATURE-
Re: Whether remotely running software is considered "software" for Debian.
Andrey Rahmatullin <w...@debian.org> writes: > On Wed, Aug 30, 2017 at 01:51:16AM -0400, Anthony DeRobertis wrote: > > Policy is not the Social Contract, Policy is not the Constitution. > > Policy can be relatively easily changed and is supposed to largely > > document actual practices. So really, Policy needs to be amended. > > And attempting to language-lawyer Policy like this is pointless. > I don't it *needs* to be amended as there is no data that the current > policy language cause problems. Yes, I'm in agreement that the Policy wording has not been demonstrated to cause the alleged problems. I'm also in agreement with Anthony that, *if* the Policy wording is in conflict with agreed consensus practice, in that hypothetical scenario that would mean it is Policy that need to change. -- \ “A thing moderately good is not so good as it ought to be. | `\Moderation in temper is always a virtue; but moderation in | _o__) principle is always a vice.” —Thomas Paine | Ben Finney
Re: Whether remotely running software is considered "software" for Debian.
Anthony DeRobertis <anth...@derobert.net> writes: > Policy is not the Social Contract, Policy is not the Constitution. > Policy can be relatively easily changed and is supposed to largely > document actual practices. So really, Policy needs to be amended. And > attempting to language-lawyer Policy like this is pointless. Thank you, that's all well put. -- \ “I love and treasure individuals as I meet them, I loathe and | `\ despise the groups they identify with and belong to.” —George | _o__) Carlin, 2007 | Ben Finney
Accepted python-tinyrpc 0.6-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 27 Aug 2017 18:44:10 +1000 Source: python-tinyrpc Binary: python3-tinyrpc python-tinyrpc python-tinyrpc-doc Architecture: source all Version: 0.6-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-tinyrpc - small, modular RPC library — Python 2 python-tinyrpc-doc - small, modular RPC library — documentation python3-tinyrpc - small, modular RPC library — Python 3 Closes: 866515 Changes: python-tinyrpc (0.6-1) unstable; urgency=medium . * The “خالد الجهني (Khaled Al-Jehani)” release. * Initial release. Closes: bug#866515. Checksums-Sha1: c13a0155d31e9a11af93f4845b3d7b200f6b71da 2492 python-tinyrpc_0.6-1.dsc f634735907c14fa8ed0a23a896893847078337a0 33316 python-tinyrpc_0.6.orig.tar.gz eb6be61147a337483dee47c0462d5efe188a56d2 5480 python-tinyrpc_0.6-1.debian.tar.xz 6a3ce58758cdeecae6e5e4080c5995f39ecf4306 25232 python-tinyrpc-doc_0.6-1_all.deb 0b61d5bbeffce16deec045677e2d55beea1c3d0d 16754 python-tinyrpc_0.6-1_all.deb 11fd70acd410a8159c204b1d39f5286488b51680 8965 python-tinyrpc_0.6-1_amd64.buildinfo 1c9f737670753686f68e7aea9ab68fdc15915eee 16838 python3-tinyrpc_0.6-1_all.deb Checksums-Sha256: 322d6ffac9995ebb499eda1a7a3df4db0ef8eb4878f342c989aa159a81f5424b 2492 python-tinyrpc_0.6-1.dsc c8a9b51ec7b388a2fb30a996d4c1634ede4e78c19455d249571c2f4e881194e8 33316 python-tinyrpc_0.6.orig.tar.gz d85d311746a300488d87b7f2dc766a24e70544a1b5ed7ecab50f852f06f50648 5480 python-tinyrpc_0.6-1.debian.tar.xz 30e9257f13c5d982c9540e740a82297a48e6bc808f6d598796e865b7784c7fa0 25232 python-tinyrpc-doc_0.6-1_all.deb b6429859cba4b2b6c79a150ea1dd5444579af416f2c1262d9e472991fb1eed38 16754 python-tinyrpc_0.6-1_all.deb 286c652c12c156981bf7b1b42ba59049267f9edb92f5004dd73aa3ea23fdb08e 8965 python-tinyrpc_0.6-1_amd64.buildinfo ca7c257cae7297dfdb8d64bbcec5327dd6d801e185e0425312856d9061281ea4 16838 python3-tinyrpc_0.6-1_all.deb Files: d862ff3d05ed531d4746b429ae89f306 2492 python optional python-tinyrpc_0.6-1.dsc 2e6405c26fa392a32c548741bf38aa61 33316 python optional python-tinyrpc_0.6.orig.tar.gz 3137a52e176e0fe986ebf0972f2dfca1 5480 python optional python-tinyrpc_0.6-1.debian.tar.xz baa2bd1deff20770b646a7409319 25232 doc optional python-tinyrpc-doc_0.6-1_all.deb 36b0061eabc96b9e01a415602ece9d8d 16754 python optional python-tinyrpc_0.6-1_all.deb 5e03ebf86e48c9daca4d807d6787f429 8965 python optional python-tinyrpc_0.6-1_amd64.buildinfo 69262cd94506768b65cdf9138520a8d2 16838 python optional python3-tinyrpc_0.6-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlmiiYYACgkQDqWsb2XR 8fczfg//ZcVWWpeljLZ0vL+epxgNB2Cv6a6vNsUudZzobkAWXp29MTFTi9WCQm5B h2XcUZYfKvfu0lZmcA+ranPPmntDlDq8dT6vdsu7s0RCzfq38SoeErVDymu3Om87 Vmp1+CmcLZux1XHwMurqptSUztfeZk+LXUcHjOU4Oy+OXN5zJmFTc1KlfNK/KhRg bwGCIVs0nlxxz+XhzjfqB6Yavmtud8ilnLHlJvBLY1j9NhvHOWTRRg/uI6xzgkyl JN/LfF9/hQ9ulKoB/QekCIwtViKCpD+IMZXkv700R5rWJldz7PDSTu8il6A+DDk1 rImyLeqD50ruv8uziNlO1xu/yXGy1K4gCItRf4YKAMyxyR9M3G+YVm/1q1mIZMq0 7MSLTXZ6qit9HnuwxiMP17L2+rBLIcLMA1Sn4rqwyFjglW/8R6Pk7cYoE40YRPhJ 0nmeXB2P1d1eSbrI8WnoVGNJOBTIChIEj06AQYzcs0xcEEuhPVldGAHp7ZJjdfDS uDtt1CL3ql5hC5OCkhZOYHe0Bplw4+KTYZDzgNWmipEvm8zxyybJqAc0SPImtD1S nVetV3YMv7uRFnB4rxrqIceG9FVSg4D2N6haeE63xQsf0CXnsmTNyI4RAabzeJJU aEWyw3hpHyS0ePecdEM8n6N2grTyApcpNBDKpfa1hROUqv4Umu0= =FsgQ -END PGP SIGNATURE-
Re: Whether remotely running software is considered "software" for Debian.
Carsten Leonhardt <l...@debian.org> writes: > Actually, I haven't seen anyone citing the following part of policy > 2.2.1: "None of the packages in the main archive area require software > outside of that area to function." Yes, that's been raised. I've responded to that at <URL:https://lists.debian.org/msgid-search/851sodkbsc@benfinney.id.au>. -- \ “Software patents provide one more means of controlling access | `\ to information. They are the tool of choice for the internet | _o__) highwayman.” —Anthony Taylor | Ben Finney
Accepted comixcursors 0.9-2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Aug 2017 04:03:25 +1000 Source: comixcursors Binary: comixcursors-righthanded comixcursors-lefthanded comixcursors-righthanded-opaque comixcursors-lefthanded-opaque Architecture: source all Version: 0.9-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: comixcursors-lefthanded - X11 mouse pointer themes with a comic art feeling (LH, translucen comixcursors-lefthanded-opaque - X11 mouse pointer themes with a comic art feeling (LH, opaque) comixcursors-righthanded - X11 mouse pointer themes with a comic art feeling (RH, translucen comixcursors-righthanded-opaque - X11 mouse pointer themes with a comic art feeling (RH, opaque) Changes: comixcursors (0.9-2) unstable; urgency=medium . * The “Ishrat Akhond” release. * Use current HTTPS URL for copyright format reference. * Update copyright years. * Specify current VCS for Debian packaging work. * Add build targets recommended by Debian Policy §4.9. * Update UScan configuration for upstream source URLs. * Declare “Standards-Version: 4.0.1”. No additional changes required. Checksums-Sha1: 4b5d2a6a63f095c395e475b1b62af3ba7f3d265d 2226 comixcursors_0.9-2.dsc db2fe3a844e57869ec84d120f5e84974b4e98dce 9880 comixcursors_0.9-2.debian.tar.xz 864f2472b2fe6942d0cb0f5ca831985741333287 995854 comixcursors-lefthanded-opaque_0.9-2_all.deb c1353d65a8071a97ea3c8d3f6b35210a4498904f 1106238 comixcursors-lefthanded_0.9-2_all.deb b481a121b0e2bdc86c5e72f7d0b27013fb23a074 965264 comixcursors-righthanded-opaque_0.9-2_all.deb fb7816efa4f8a9b0d8a86690d4fe4956f54d12e7 1081754 comixcursors-righthanded_0.9-2_all.deb 3a2529b7a0d5cf9e3157da7a5b8fdc0b45a4cf53 10282 comixcursors_0.9-2_amd64.buildinfo Checksums-Sha256: e75478e02eb6c66d261d9831e6c421824e4bd31a795507853c5e04109c2d4c5f 2226 comixcursors_0.9-2.dsc 5b8eb7a6625aabe4de25f149b6c300b503f3573dbb87217e4559893344cc05ac 9880 comixcursors_0.9-2.debian.tar.xz 7496dcd5e688c4a3c4b0a2f413e611aa4bec8ed29a8b5d8316ae5f4b3f446c5f 995854 comixcursors-lefthanded-opaque_0.9-2_all.deb 186f452ee02a1725309a73f71a7f704ddf97b125b65102f7497567d488864f20 1106238 comixcursors-lefthanded_0.9-2_all.deb 5cd76d7f99ce2b88b6d6eec0c9dfe4e44cd2240fbd9dee01290e5c67fde5251c 965264 comixcursors-righthanded-opaque_0.9-2_all.deb a819582f7f2fb3e8378c5b2c4b1da617203acf7f07b2c986732da5ccb5081649 1081754 comixcursors-righthanded_0.9-2_all.deb 9b1ebb014f15cc2737754cd617f30e886625b0990de286b76099a146d8adcd92 10282 comixcursors_0.9-2_amd64.buildinfo Files: a26f2d210f94ef10b27b767e8a0694fe 2226 x11 optional comixcursors_0.9-2.dsc 5842caea909ccd9355aa7a35a50e0c16 9880 x11 optional comixcursors_0.9-2.debian.tar.xz e9959eb681e48af6281f71beb2389b87 995854 x11 optional comixcursors-lefthanded-opaque_0.9-2_all.deb 00fc88e36237005790a9c3357181b25b 1106238 x11 optional comixcursors-lefthanded_0.9-2_all.deb 29d1298edba7f2be6479de16c7980d42 965264 x11 optional comixcursors-righthanded-opaque_0.9-2_all.deb 742103f496722a9c75b761f7d180b6a1 1081754 x11 optional comixcursors-righthanded_0.9-2_all.deb c834560d407c7e56924a2a6b218a0754 10282 x11 optional comixcursors_0.9-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlmgbbwACgkQDqWsb2XR 8fd2XA/+JXISMnBYyHY4pRkcTPs8XLGsGHt66CbEMr0FprkVg6B4GsIRW/d0GICe m1JoEdaa9TbcX7DKFziKr1IKRECgu3MLnPUYvW9EXyajDaCcczDxv9pGIEskzQR4 6hFpHYvXY+wuibNwHb9Y9KFApFx/Tv0mo5A+hrkGoSYQW+u+eehbagU6gSbmD1fn LMfSz/K2GcaG/Sg1cm5xdLSDvVV1e+xbpJRc6XrNX9UvkY5cV/5xyMh/qgtX3O+N fGW+suC9AxqFfC37cDoLtvfvQKk7jFg7tQ/vV8g6zLV8Md4HkgiZD+ZvereFuocy 2DVaegPuM3kqilhiMSi5YvuZskVrkq0clmsYSmKrAqnonorj83jHWUOKNwxiCX7/ s4ISPbHWznk1JBguEMfnSYWs2XcueluTJ5rvHC2+IBU9HxN4uJTj6qQ1Azb7xyme Nyfcay7D3ZGegUQ6ZGiW1QmmRQj88GFrkNVVaQeZlkWRes5Cvp3cAPbbOobqzpE3 GTf//WrQ+7kDBxg5YykHGfOTMUvVZHXB9Ka7xPLJn5Pr5nOhm/KTkGWwc2X9iCLo t97X7/gQvDLYCzbpOJ6WLgezvIud5fnvDnz7YSEEYygZwvsT0vD+c4JJVCXQXj3r QW4RKRbsfNOamabcJbm7cU7svdEc1K3QsrmU6dib76fxmwSrijQ= =CAUD -END PGP SIGNATURE-
Accepted pysha3 1.0.2-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Aug 2017 09:36:06 +1000 Source: pysha3 Binary: python3-sha3 python-sha3 Architecture: source amd64 Version: 1.0.2-2 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-sha3 - SHA-3 (Keccak) hash implementation — Python 2 python3-sha3 - SHA-3 (Keccak) hash implementation — Python 3 Changes: pysha3 (1.0.2-2) unstable; urgency=medium . * Correct VCS URL fields. * Remove suggestion for unrelated package. * Enable upstream test suite during build. Checksums-Sha1: 43ebae5c44b4097134fefdfc7fe0751abb9eaae1 2139 pysha3_1.0.2-2.dsc 32d87119588eb5b9cf2cdc0b6d8cff8a37e18877 8556 pysha3_1.0.2-2.debian.tar.xz 5cb0dda5d6db312002894ff02d11005f90ca77ea 8098 pysha3_1.0.2-2_amd64.buildinfo 462a4560e601f7eed05283fd43daa6dbfa7c2413 89562 python-sha3-dbgsym_1.0.2-2_amd64.deb 7223e7257ec6e049c321fc76e3b1fe45402fe345 42834 python-sha3_1.0.2-2_amd64.deb d2876b814a2be0aad0a96ff206e677d3a4d3bbbc 122580 python3-sha3-dbgsym_1.0.2-2_amd64.deb 63235c010f1b28310ad3ead0ddf3be404d3f2601 42980 python3-sha3_1.0.2-2_amd64.deb Checksums-Sha256: 6e9ddcc4988869c3e6fd73cdff7bd5f6ec33a6d5c083a1b85a848e339fa83d99 2139 pysha3_1.0.2-2.dsc c7b3320914058746622ed819bbb3a84e1c19482c4cbb53b1a2089affa4be7fbd 8556 pysha3_1.0.2-2.debian.tar.xz a573d2ec7bfa7b05842fc92723de653c385b81b964739cf3b9251b0a05afe39a 8098 pysha3_1.0.2-2_amd64.buildinfo 961fabfbe31c570bb3ec7e28c3a74f958b8a7ff0a39aed47e3150e3480b3ad9e 89562 python-sha3-dbgsym_1.0.2-2_amd64.deb 60b0bcd377717b4b6089d817eb69289b1bd2fa833359c24425148ef05c0c3352 42834 python-sha3_1.0.2-2_amd64.deb d24555be5619fdfb6cd83b14f0a0c100daab1e78da9cc423596a35e3c5cdff35 122580 python3-sha3-dbgsym_1.0.2-2_amd64.deb f39a546623aac94407e811f0cc4ccdb313efe35dd4deab61e89795afc130b796 42980 python3-sha3_1.0.2-2_amd64.deb Files: 084932367c3ed76017d277b091b8e311 2139 python optional pysha3_1.0.2-2.dsc 9bc53edc8244aaf0ac8e3beff1cc9105 8556 python optional pysha3_1.0.2-2.debian.tar.xz 9f99bf064a4a4dffb561f6fb00424900 8098 python optional pysha3_1.0.2-2_amd64.buildinfo 4a0ae70f3cf4e0a667fefa102863383b 89562 debug extra python-sha3-dbgsym_1.0.2-2_amd64.deb 75477513cd194cca1337a324667f4b45 42834 python optional python-sha3_1.0.2-2_amd64.deb e4f0e58e4d6fb15ba61d8c26890cb9c0 122580 debug extra python3-sha3-dbgsym_1.0.2-2_amd64.deb 72d0e1537d7b65b111ab5b380c1cae9c 42980 python optional python3-sha3_1.0.2-2_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlmde4gACgkQDqWsb2XR 8ffwBg//bDWcIWArtiz5jPkbVdjDqVw9ruhMTeJnoxloTdRYBHbsEU6R1GrAqbXf TAqOiE8CQq5kirG0ZbXsvpsE5tr/kcQPY4j1+FBmxxW0ZuBcJJnO9L7X2m6NfQY0 4VAtFhg+KLS/ZOV6XgotRoCzcqee0XFGBAWHL5b2Z6MVa2qf51uMjmBly3jIOunY GH4MVNdjqwmmBuLlEPilHRsvGElHx687WJ7kG0xAzSZA+wUv4NkGz88lEyCCoNsj YAs/q08KQfJgS8rraAD6QVeXGQOKcPNfzdPu6qkOnUJTQOBwaGp/TSgw1SrLDUqK zKFqln2CGvm3vBbfjI+XOdGFdzTf/gcJire6L6Q4H22BOO9LSaNNaKy84uXfD5FK VQ16YZrxlc+WhRmfzb1Xkt+rBrdP3o8GWIodgA53jjqqk94v5MZUYkssftgH3HkI aYaIhpaF+OC2C6SRUkc6qYsG5i2XtvlgNDhBHf4Prk+J6XLvwPj6IdVuAxVMDH8P h2ULzmUoQD5U/JpEArAgccMdrwdrfVaI9tbTVd1bHD8QviGYToXxxU2eA2nZKQ9e eqnwakfe+r/5zwZRVyfWh8zjQ7zizHfvWU5xD6mGcW75fHBqep/cSOf5eRDKDGVn zFAnScgWWe/gh7cd4kEfm6wmO+9BhN61U1jmWnb+UOzhnoEkZZo= =KH03 -END PGP SIGNATURE-
Re: Project and User creation is now disabled on alioth.d.o
Alexander Wirt <formo...@debian.org> writes: > as alioth is deprecated and will (more or less) get replaced with > other services soon I disabled user creation and project creation on > alioth. > > Please stay tuned for the results of our sprint at the weekend, an > announcement should come that week. How exciting! Thank you to all for working on Alioths successor, and for working to make a graceful transition. -- \ “We spend the first twelve months of our children's lives | `\ teaching them to walk and talk and the next twelve years | _o__) telling them to sit down and shut up.” —Phyllis Diller | Ben Finney
Accepted pysha3 1.0.2-1 (source amd64) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Aug 2017 22:59:19 +1000 Source: pysha3 Binary: python3-sha3 python-sha3 Architecture: source amd64 Version: 1.0.2-1 Distribution: unstable Urgency: medium Maintainer: Ben Finney <bign...@debian.org> Changed-By: Ben Finney <bign...@debian.org> Description: python-sha3 - SHA-3 (Keccak) hash implementation — Python 2 python3-sha3 - SHA-3 (Keccak) hash implementation — Python 3 Closes: 866518 Changes: pysha3 (1.0.2-1) unstable; urgency=medium . * The “سليمان الرشودي (Suliman Ibrahim al-Reshoudi)” release. * Initial release. Closes: bug#866518. Checksums-Sha1: 1c82c9ce6e7f42956a56ea9d79e0e4eec8238802 2179 pysha3_1.0.2-1.dsc 638d3d0a3545520dedbd91bcf8120bad1a89f74a 829192 pysha3_1.0.2.orig.tar.gz d1e0092a60a8f6e092e456571c2f89497ab3d93f 8516 pysha3_1.0.2-1.debian.tar.xz 7e453d0afbc6ef27733c83fa53aff91275cb2cfd 8325 pysha3_1.0.2-1_amd64.buildinfo cd5eab58e278c3e62d2af33e39861a8fe0f3d709 89590 python-sha3-dbgsym_1.0.2-1_amd64.deb c4eb9474d509333491e0910caddd9d1c518fe10a 42616 python-sha3_1.0.2-1_amd64.deb 9f6eced3f0aa78a5556e36a129bc07e5f0e06db7 122722 python3-sha3-dbgsym_1.0.2-1_amd64.deb 94615f3a2cf5038cda5c938f34902e0e8b601850 42828 python3-sha3_1.0.2-1_amd64.deb Checksums-Sha256: b933e28f714d603cd953675573eb553a6c01245c2e81874a8a1d79781e42ed0b 2179 pysha3_1.0.2-1.dsc fe988e73f2ce6d947220624f04d467faf05f1bbdbc64b0a201296bb3af92739e 829192 pysha3_1.0.2.orig.tar.gz 72a43deb02d728ac5801a593ae0f55225f3f75db4790004d0e9fd74fb74b9a6b 8516 pysha3_1.0.2-1.debian.tar.xz a81e8b20d01d8422340a87278b32bea4a8b301b7cbd7566dd2dc6877664bb87e 8325 pysha3_1.0.2-1_amd64.buildinfo f1e508292230f983423cdf537643cc6ebc608a6b430b631ac077ac11a238afb3 89590 python-sha3-dbgsym_1.0.2-1_amd64.deb 21bcc5f523a96023a6a14cdfafebe39139a0cf3123117ba1b29fb51ee01e7eca 42616 python-sha3_1.0.2-1_amd64.deb a55782826d818de7928857a4658a6b5e9fae3fc2f8117d49bcebbff287507237 122722 python3-sha3-dbgsym_1.0.2-1_amd64.deb c419b279750f201e7a71ab3839c33d02b27b189eb5b31533a67915368a8d065c 42828 python3-sha3_1.0.2-1_amd64.deb Files: 080b724c72d1be2fd84fc7df3eb7b58d 2179 python optional pysha3_1.0.2-1.dsc 59cd2db7a9988c1f3f6aee40145e0c96 829192 python optional pysha3_1.0.2.orig.tar.gz 4169fadc5ef4977e6c33e25b67656ef3 8516 python optional pysha3_1.0.2-1.debian.tar.xz ff5febe923c85739d802dbba0642b140 8325 python optional pysha3_1.0.2-1_amd64.buildinfo 1bb44abf396a169f9305b7c9da80641a 89590 debug extra python-sha3-dbgsym_1.0.2-1_amd64.deb c2343e626ebc4e45ef284aba8570aedd 42616 python optional python-sha3_1.0.2-1_amd64.deb 13887caeae004bdb9fc36ff09a445cac 122722 debug extra python3-sha3-dbgsym_1.0.2-1_amd64.deb a975e234a5ffd39862de9a9ad16575c4 42828 python optional python3-sha3_1.0.2-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoaELxsJFHaxC07KLDqWsb2XR8fcFAlmYPO8ACgkQDqWsb2XR 8fdfxQ//ZaWGXx0DF6XkAPXgMsnnHpevsKkRj+gin8yo7p5VA6wtYYpqGPU+qTB8 QJKAI+ARjL1DT4JxPtwJUdqLSQrRDG8zoY3IQoLCbH//4LKNTyfvJ6J/g4eNDoHK SoM5AKiwx80wN6jliiHJVEJnwp28ZYUfqEh38QkjTZ5i5mWyEd7W9z+wdJTJZezu 8ZwAFuIARDR6d12KaId53uoewJiaIcjHzjvblMGiBC4jO7FwpW2povuNLZ3E3l1A 9IvtErKdHMGMLt1dlVYROM2E1lNqp51PxzyaXMLdhGuqA3RukXPaucXZFPaj9dA0 dJbdopifchshJ8FQ6bmrrcmpO/R9BLLjdhmCmqT+LhCuG6jTK1Ssuip/CGKXVDyF 1XrMQC1cT/XP1ZTzQgsjVKrF/2QDfIGFCtM3/ly6J/6x2uCOmTtkj05CqhsrHtJg qiNID0jdRpa+8D8jUR2VVPAvZ6NWdcvruT+hP1YxtNdGJLfhhOKhlLBCaYBPXsgr lwyvG3da8alHd2Bpns9h4bE1btmiZxD+mINJov9hge8JKof4VlnfsaL/hrEj5DQM g3tcIJ51MgQF9jdyewnQL9IfpJnl8kjh9FWkpegYkAyt+lhT58BOgFPx35Gptro6 i6/Oe2dLF1l6j4K/puSEfsYp8CKAp58jMYCAExqRfRleS13QFU4= =iDdm -END PGP SIGNATURE-
Package Managers All the Way Down
Howdy all, I am catching up with the Linux.conf.au 2017 presentations, and have just watched “Package Managers All the Way Down” by Kristoffer Grönlund <URL:https://archive.org/details/lca2017-Package_Managers_all_the_way_down>, also discussed at LWN <URL:https://lwn.net/Articles/712318/>. The problems Kristoffer covered are ones that affect the Debian Project a lot, and his call for solutions is interesting. Are there any DebConf 2017 presentations or working groups that are tackling this? -- \“I'd take the awe of understanding over the awe of ignorance | `\ any day.” —Douglas Adams | _o__) | Ben Finney
Re: Whether remotely running software is considered "software" for Debian.
"Dr. Bas Wijnen" <wij...@debian.org> writes: > I'm referring to policy 2.2, which lists what software belongs in main > and what belongs in contrib. While this is not voted on and it does > not follow directly from the SC, I thought there was agreement that > what's in Policy 2.2 is a good way to determine where software should > go. In particular, if it is free, but requires software outside of > main to do its job, then it should go in contrib. The parts of Policy §2.2 relevant to this appear to be: §2.2.1 “The main archive area” […] In addition, the packages in _main_ * must not require or recommend a package outside of _main_ for compilation or execution (thus, the package must not declare a [dependency relationship] on a non-_main_ package) […] §2.2.2 “The contrib archive area” The _contrib_ archive area contains supplemental packages intended to work with the Debian distribution, but which require software outside of the distribution to either build or function. […] Examples of packages which would be included in _contrib_ are: * free packages which require _contrib_, _non-free_ packages or packages which are not in our archive at all for compilation or execution […] The language is clear that it is talking about dependency in the sense of requiring the program installed on the system in order for the program to build or execute. > People are arguing here that "It requires a network server that is not > in main" is fundamentally different from "it requires local software > that is not in main". I don't know of any program even proposed for Debian that would require a network server in order to build or execute that program. So yes, that is a distinction that is salient in the above Policy language. > I think they are equivalent; server software is still software and I > don't see why it running remotely suddenly makes it acceptable to > depend on it. You appear to be using “depend” here to mean “without this the program *is not useful*”. That is not a distinction relevant to the above Policy sections. They speak only to whether the program will build or execute. Whether the program does something useful is not relevant for the categorisation into different archive areas, as laid out in the above Policy sections. > Policy 2.2. So again, I'm not saying the rules apply to the external > software, I'm just saying that the external software is indeed > software and therefore depending on it requires a package to be moved > to contrib if the external software is not packaged in Debian (main). The text of the above Policy sections uses “depend” and “require” in the sense only for the cases they explicitly state: that of building the program or executing it. > Similarly, if a client program's purpose is to connect to a server > that is not in main, the server operator doesn't need to do anything, > but the fact that it is not in main means (IMO, but apparently that is > disputed) that the client must be in contrib. The language in Policy §2.2 does not relate to any program's purpose at all. Policy experts may correct me, but I find that your interpretation does not fit what is written there. -- \ “When I was born I was so surprised I couldn't talk for a year | `\and a half.” —Gracie Allen | _o__) | Ben Finney
Re: Whether remotely running software is considered "software" for Debian.
"Dr. Bas Wijnen" <wij...@debian.org> writes: > What seems to be the dispute is whether software that runs on a remote > system is still "software" for the purpose of our rules. That is not in dispute, it seems to me. The rules of the Debian Project can only bind what the Debian Project does. The Debian Project could moot rules about what the project will do with regard to software that runs on a remote system. While there are trends, I don't think such rules exist yet, or if they do you haven't shown us what rules you're referring to. The Debian Project does have rules about software *in Debian*, as described in, for example, our Social Contract. I hope we can agree that the Social Contract's rules about software in Debian do not have any power to restrict software running on remote systems (unless they also get their software from Debian). > I think [software that runs on a remote system] is [software for the > purpose of the Debian Project's rules], especially considering the > trend that almost everything is being moved into the cloud. Which of the Debian Project's rules are you referring to there? Can you show from where in those rules you draw this interpretation? > I believe Debian's philosophy should be that software running remotely > on behalf of the user should be considered part of the system By that philosophy, if person Foo connects to a system I am operating on the internet, the rules person Foo has chosen to accept are also binding on me? Even if I do not accept those rules? If not, please explain where that interpretation of your statement is inaccurate. > It seems clear to me that a program which is intended to interact with > server software does indeed require that server software to function. > So if there is no free implementation of the server, then the client > cannot be in main. Maybe so, but that appears to be a different position: that the Debian Project's rules apply to software in Debian which interacts with remote systems. That's very different from stating that the remote system's software is also part of Debian and therefore subject to the Debian Project's rules. Please help by clarifying which of those positions you hold. -- \ “One time I went to a drive-in in a cab. The movie cost me | `\ ninety-five dollars.” —Steven Wright | _o__) | Ben Finney