Re: Bug#1035904: dpkg currently warning about merged-usr systems (revisited)
On May 17 2023, Andrea Pappacoda wrote: > Hi all, > > first of all thank you for this great thread. While I could feel some tension > while > reading it, it's completely normal and I've learned a lot. > > I have a question though: if /lib64/ld-linux-x86-64.so.2 is already a symlink > on > non-merged-/usr systems, pointing to > /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2, why would > it be an issue to have /lib64/ld-linux-x86-64.so.2 point to > /usr/lib64/ld-linux-x86-64.so.2? I don't think it would be, and I don't think anyone else is saying it would be. > Why do we want binaries to look for the loader in > /usr/lib64/ld-linux-x86-64.so.2 if that would still be a symlink to > /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2? My understanding is that there is a desire for the /lib64 symlink not to be needed, because it would simplify bootstrapping new systems. Best, Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
Re: Automating signing of DKMS modules with machine owner key
On Aug 05 2020, Jeremy Stanley wrote: > On 2020-08-05 20:30:59 +0100 (+0100), Nikolaus Rath wrote: >> On Aug 04 2020, Jeremy Stanley wrote: >> > Okay, so for systems to which a malicious party may gain physical >> > access (or remote console access) there's sort of a third risk this >> > addresses. A special case of the second risk really. *If* you're >> > also encrypting the filesystem on which that signing key resides >> > (via LUKS or similar) then this might keep you safe from someone >> > with access to replace the kernel or initrd on the unencrypted boot >> > partition... but only if they can't unlock the decryption key for >> > the FS which holds the signing key of course. >> >> Wouldn't such an attacker simply modify the (necessarily unencrypted) >> initrd such that it stores the decryption key for the attacker the next >> time you enter it? > > How would this attacker generate the new initrd signature so that it > still validates correctly? I didn't know this was validated these days. Still, couldn't they just reconfigure/reinstall Grub so that it doesn't validate the initrd? Best -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Automating signing of DKMS modules with machine owner key
On Aug 04 2020, Jeremy Stanley wrote: > Okay, so for systems to which a malicious party may gain physical > access (or remote console access) there's sort of a third risk this > addresses. A special case of the second risk really. *If* you're > also encrypting the filesystem on which that signing key resides > (via LUKS or similar) then this might keep you safe from someone > with access to replace the kernel or initrd on the unencrypted boot > partition... but only if they can't unlock the decryption key for > the FS which holds the signing key of course. Wouldn't such an attacker simply modify the (necessarily unencrypted) initrd such that it stores the decryption key for the attacker the next time you enter it? Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Heads up: persistent journal has been enabled in systemd
On Feb 05 2020, Scott Kitterman wrote: > On February 5, 2020 12:35:45 PM UTC, Ansgar wrote: >>On Wed, 2020-02-05 at 07:44 +, Scott Kitterman wrote: >>> Do syslog facilities really have to be addressed by number rather >>than name? That seems like a horrible interface. >> >>Currently yes. There is an upstream bug asking for a way to specify >>them by name[1], but nobody implemented it yet. >> >>I think a `--facility` option should be fairly easy to implement. Just >>adapt some code from the existing `--identifier` and `--priority` >>options, there is already a method to translate facility names to >>numbers (see calls to `log_facility_unshifted_from_string`). >> >>Ansgar >> >> [1]: https://github.com/systemd/systemd/issues/9716 > > Thanks. That seems like a pretty basic feature. > > My impression so far is that the journalctl interface is a regression from > what we have > now in every way I care about. I would venture that for every user who is grateful that /var/log/mail.log collects all the various mail-related logs, there is another user that curses about non being able to separate (out of the box) the logs from all the programs that consider themselves mail-related, and another user who struggles to remember in which logfile $DIFFICULT_TO_CLASSIFY_PROGRAM might be writing its logs. The former use-case is well served by having the current set of logfiles, the latter will be much happier with being able to use journalctl. So this doesn't strike me as a strong argument in either direction. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Adding security features
On Feb 05 2020, Anthony DeRobertis wrote: > On February 5, 2020 9:49:36 AM UTC, Nikolaus Rath wrote: >>On Feb 04 2020, Anthony DeRobertis wrote: >>> Google has at some point had results from >>> Gmail in the web search results (no idea if they currently do). >> >>Would you have a reference for this please? > > Here is a news report from when they were testing it: > > https://www.pcworld.com/article/260600/google_tries_showing_gmail_emails_in_search_results.html > > > Not sure what came of it. I think it's worth pointing out that this was an experimental feature that users explicitly had to opt into. The original statement feels misleading to me. Best -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Adding security features
On Feb 04 2020, Anthony DeRobertis wrote: > Google has at some point had results from > Gmail in the web search results (no idea if they currently do). Would you have a reference for this please? Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted s3ql 3.3.2+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Oct 2019 12:01:04 +0100 Source: s3ql Architecture: source Version: 3.3.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Changes: s3ql (3.3.2+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: ff54baeb997659a33af0d874c83a219335b2f1e1 2943 s3ql_3.3.2+dfsg-1.dsc 99cffd92cef82c663664b1a1d874e1835c2b6de5 616740 s3ql_3.3.2+dfsg.orig.tar.xz 9d1a1f408ab4069d98cd72be6688864b98d88263 13848 s3ql_3.3.2+dfsg-1.debian.tar.xz Checksums-Sha256: 15817f284ca9505b157de397a62f68b0e03018ff4f3dc774e0cf7fac67bd2565 2943 s3ql_3.3.2+dfsg-1.dsc d181f5529dd5b69dc9a51ea548de9efc758f8363dc2a5d0198ba92cd93201164 616740 s3ql_3.3.2+dfsg.orig.tar.xz 73d348ed210c5a2680c0f4a4f09b066a2d69b56643c1f0832cc5e42b92b74116 13848 s3ql_3.3.2+dfsg-1.debian.tar.xz Files: caa541c048e51cff0640449e521a0d56 2943 misc optional s3ql_3.3.2+dfsg-1.dsc 01766f52398d6a3d80fde9a95ead90eb 616740 misc optional s3ql_3.3.2+dfsg.orig.tar.xz 2541b5ba5aaa14e11752866ff5890fd5 13848 misc optional s3ql_3.3.2+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAl2sP8tfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8Tlmf7zMP/1+TSA5lsKeP2mYWSVc3tgmntMMZUPKzq+iwDmyltGqEthJR M6RcadfIvu+frRbHuCTBEXpAg6u4WTh40dvKK3ZkePqy4jOYS76RsMCLiq37MSni Qg8ri1imGkVk0SwhzrENmLhAClZfBkZD/tSxiePwP7UuBQlRQmTH23jDJF9cl15+ kQyrn4Idv378V1UlqaRGSSa2oQiAmRcUwNkee4T6/1cXz2G+sZ8hhrdhi7UMZdEo AW9kyAtbCF4OqMT5Sde2g2PLK1g3igYtvbahpn/MWKCNeqXrFRGKGgShDR3rZQmT Hcm0IiPy9AbXdV4UlLZe9ryqFovnhyHfuBfJOe5vbAhHJAcOsKahfO/4cfzmIiuh VZM+dIhZCu70JgzcCytzEW/Vhq1/qLgvlPgTbKA0Dk8U/1ciL/g4AJ3/QO1/bEMk dzfpbqxanBqm1igm/VDpDlLyE/AkDI6SDE54j6xzRh8Ust2BLquuzlW5aHQ7AX7D kT36nnslRNlcVUACG37Lims+nBCxYIi6T0CrFFxlXqlZGgF3ZP0HB07c7KAeJJkY eALI1zwuaYONRMXFkEB/zF0Gzyreb94xudwp1Rz9SzUvoKi5kU9x9+jcIfNtkwPo REczmDu4d4opagCJpR+4+3lLKhdQJj0L/DbH+/HQVv50Hv95lirO1dYCVPd2 =93Pz -END PGP SIGNATURE-
Re: Git Packaging Round 2: When to Salsa
On Sep 08 2019, Sam Hartman wrote: > Hopefully you will choose to monitor merge requests for your > repository. If not, turn off merge requests. Monitor *and respond to* might be a better phrasing..? Best, Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted s3ql 3.3+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 08 Sep 2019 15:58:56 +0100 Source: s3ql Architecture: source Version: 3.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Changes: s3ql (3.3+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 198704fa1f5b872395f6dbfdbe7272dccb46e943 2927 s3ql_3.3+dfsg-1.dsc 5af27ea20d682dd5768599d77e526484ca36605d 616068 s3ql_3.3+dfsg.orig.tar.xz 78fdf3c42bc5739b799ffa8515b943d7102f2c5f 13832 s3ql_3.3+dfsg-1.debian.tar.xz Checksums-Sha256: c056b2a5ce0e6466cf3a4da6660394bb15ecc47c02c2ad23141365d6222ecd85 2927 s3ql_3.3+dfsg-1.dsc 54e23f83a3df94c5d219f8733d17442754f45acab46b5d83efc9f41cf7f97785 616068 s3ql_3.3+dfsg.orig.tar.xz 572af2e539494cf107c5f63936d9b168bf653db3f5f3cc2f0bf80a5fc600bb57 13832 s3ql_3.3+dfsg-1.debian.tar.xz Files: 387542277559135d6aa5e786a30d40ef 2927 misc optional s3ql_3.3+dfsg-1.dsc dda778e6d324ea8cdc69b384fc4a4aa4 616068 misc optional s3ql_3.3+dfsg.orig.tar.xz 899f287ee1e089bae1be1d2f96d09875 13832 misc optional s3ql_3.3+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAl11GEdfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfrtUQAMfH1ANV3hPaX/AaxTN2ckpFfCIpnUwmXVSdhienIi0hqmZE 8avFfbHNkxX1TyWu0PUgfIPNKMQM+KtNVE0UlLMmsDd30n3YcmsKecp6Amcfz9lL ZRflFkqOyYz6eIboy+tXaDcJj+Ct5DPi6Ps0+4VF6jjDKpEhqKMCE1EHy5SDDtbB 071PW1voEU9e/QjCkN3X0y1A2LSTB1zS9xvqppO2bq9M7xHOOqY7bNQo9oM1qNLx QdRBn1PRoGBQ60InESURuas+y8bUfw2YeYSLIxV8NDaCaIpd8sLtRbCr4me8MgBs G4MM5CsSKLy3ZSHd8hP5u5BF+P0MrbGc5Inck32J95OL9l1IBSPw0O3gQLf6qhxc HkNZ/jNvjSJu7uA/lFNYxlGNCxGAY0zHa2tZcLwfdpwvaUh/fdyXAskDeIuTN5BK 4hCFfBd+9KRXkxncXRmM8zu8J/KGKHWcVYV4w5X5xqO57qUdtSM1omqPqIEDlftQ oSx/Vlx5hHsc/1NpwiCCApn8sgRg+FgS9TQLzK/rGNZue8iTi0/b1HEw6p8j5HB1 lzOmutTFlqVaFILDLGC5zwDyzoAytnoaOqoWC2xRqBocsCDo/t188Pa2eXeJRZDH jQwd/5hw7wC2+nk6ho/uZCdxoX28AvRfB1FU/hvkELS+WpM6gCT6htuB/wkp =aG+/ -END PGP SIGNATURE-
Accepted s3ql 3.2+dfsg-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Aug 2019 11:22:40 +0200 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Closes: 933558 Changes: s3ql (3.2+dfsg-3) unstable; urgency=medium . * Gracefully cope with coarse system clock (Closes: #933558). Checksums-Sha1: 73c30355cc614ec796beeddbe6b0d9e8a73c6f66 2927 s3ql_3.2+dfsg-3.dsc 72d01e447852abcb03ec3c0c943971e94172d6e0 14020 s3ql_3.2+dfsg-3.debian.tar.xz Checksums-Sha256: 85edf703d8ab38721033b6230bcf7145dd42a108aaf4b6e39a398b43b555d385 2927 s3ql_3.2+dfsg-3.dsc 149ff46015f71454c0ff76b57ba7cf30bbd4a73b9a7c287285e7f45b9ba4b952 14020 s3ql_3.2+dfsg-3.debian.tar.xz Files: e8b5cffef8de338d44cacec79696642f 2927 misc optional s3ql_3.2+dfsg-3.dsc e5b54f7344721e845659720d12c77db3 14020 misc optional s3ql_3.2+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAl1EAVZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmflwQP/3Z3s1LcUIzX7ihOJO0RWwsXYb+cAwCpZy78lno2oh5gzHJk bU6t5MVngYJKHM4a0YpTPdlRSlVWSZznTOpnFTbwcVfQX2i+b+5X+OkmUMQ4JsKd 3XoFHwu/F7A0c/kOQgTEPuqsp7lHg7i3XtPHeQkr737dkxd3CDmzoXOS5qox6lhb W2Du6pa3JC9LlqmpWC41vISWuBWfqDarS7nbYy4UBsY6cnpGMh2zKzIV18YU/EdV 8snnclbxIvctiEexkwQxOiN5xPF0cnDRj9qvqkp8Se4AT6Rv5OidHX0myJCigH2O 6/rKvfh/alY2s8aBBzoE0gRPou+J5HTQfoYoRw2rj8iLOr2hGITKlZ1ynC9IpLID d7e5H7lhadFwADsmy2kT8qvh6tEWHeU1QXjFoaCQwJscy1gmtFxG2FlGhP/tklfo VIk1g/dNe+j482mPJbo1wo+vAm6uaXdPpTbgG1+VD+adgx+MEvmddnvx/aCSji0X RxIMeCLtnXmigdWX4yM6rq3mJkQsuBewwlgKpRaDRD4b4j9g+a63HvO42O3Qdcv3 GJXhptafeCEfhRN695ct5udgRpOQG+vbaiQsZ7SEjKSSRB48r6pctNHwEsvtv6Ee FYuBsw+U760eOdczRXW06hQ9I9YHjuhAWbpcZcvpNnLyyt1NVQTcLWL9GfRe =6Fi7 -END PGP SIGNATURE-
Accepted s3ql 3.2+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 31 Jul 2019 11:29:32 +0200 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Closes: 932544 Changes: s3ql (3.2+dfsg-2) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. * Depend on texlive-plain-generic instead of obsolete texlive-generic-extra (Closes: #932544). Checksums-Sha1: cea25daeb3a72f8539d69eb53da2d96a1d785a5f 2927 s3ql_3.2+dfsg-2.dsc 08222c2d6e94df123aaea22879116ae83b03ddad 13636 s3ql_3.2+dfsg-2.debian.tar.xz Checksums-Sha256: 866d15134bed4a9baaff1b96b52734ffccb7fba48a9d5573ce488e2583d087c7 2927 s3ql_3.2+dfsg-2.dsc 438a7abfd818fc851786c499c2a721273dd84944c11e10f2871fb33fb926c504 13636 s3ql_3.2+dfsg-2.debian.tar.xz Files: 9770ad0c32972c986dca4f88124c7248 2927 misc optional s3ql_3.2+dfsg-2.dsc a9e632cffbb511d8fc9375ac7682a1d6 13636 misc optional s3ql_3.2+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAl1BX9RfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfVoEP/1Z0X0BWuodCU0Zx2QHcF9S4dF+V59VKzX8ZbvaaUUkksoZy +bMuLLJjCnxTe4BiO5RDSEioBB55ogB8PqaA1tkhSy51rOt+Xlf9f+4vZyrA9E9c Nz7udoPoD/Sygi0rIla5xSlmtOdbL+e3VbWPx/ZxisQOe9Oc2pl8k5b4isu08DnX wL5kwcqITYpGRHrWmKjQ4eHGCJ59+6H7yU/Mxd8Q3xfeqkm4qq+4edtKlBNU6YpX hxXhZsu2X1/0QppQGy3tQazx3M6I8O+toUHHhTw9752plHVYNtBKiRAbcGJ85qy8 Os1EJsQmw4qpU94ylZWCzVKf2is/YITA/NfIdrzlV0dBy/YDqyVRcNJQL8PouDdc BV0pr26GZrC8Nb7iMvWZeOeTi5s4oOk96dicYfTwchsBvCSbJn3vGuq1HDJJbY1h FM5uWxTjL6oiXB3p8tZwwfUnIQS2RxzSgtwRgEhVIqs1S5CPwonNr68cG+f+Ib2G BXaj1O4DXOVnVu+pCAfsT96DUJvxRrLzT0TJ43yGUqVJg9Vrkevdzdwz5a9NviSh 7xWvlYyoG+Y2+IC7h7FO9EZEXl9ehCU/tRq5vQtlIvyZlXafYHe2YE32OwsosCP3 06ipj199SMljUKE/5l9UgNJf2OFUbUi3xHgKDV6HU143SpRZCAqJ9GJ2rtan =sfoE -END PGP SIGNATURE-
Accepted s3ql 3.2+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Jul 2019 16:54:35 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (3.2+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 76dd6051072fa1608e67fa29ad4f8b801e3b24f7 2921 s3ql_3.2+dfsg-1.dsc f529e3fbda5973831373cc9b0528b374b3b79106 761291 s3ql_3.2+dfsg.orig.tar.gz ab5c09f9c775ae8df0ed0d50a2cb103756343fd6 13608 s3ql_3.2+dfsg-1.debian.tar.xz Checksums-Sha256: 392092a1386b69ee49bb2e5be57d0b5df93e893aae68fb7d1917881561ff38ad 2921 s3ql_3.2+dfsg-1.dsc 757a67daa5ac3a79fda43ceca144aa4bb0c21b1346e1bc9cd3acd46ea8c8065e 761291 s3ql_3.2+dfsg.orig.tar.gz 5c3f72aca094862f2eb21ea8a87209de86eede31e35ab8d0e93f0502cca79ebd 13608 s3ql_3.2+dfsg-1.debian.tar.xz Files: c0398a9c653be54f45fd2236a6a36a8a 2921 misc optional s3ql_3.2+dfsg-1.dsc cd69e21e925e4051a5ce414cbe12b0ec 761291 misc optional s3ql_3.2+dfsg.orig.tar.gz 82da75ee64c27a042e3a5f5972f6dea5 13608 misc optional s3ql_3.2+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAl0vRgBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfyQIP/2hXt/2TQtw5n91aYGeYeKhzlV6Nq28+gYjkK0PCjzAKlFeA rMykyvZ7c5zhMgKSDm0d+T8j3l0oJQzSo1J2DWh34kOiifGsvI7hEtSDPGvMHHof XW1c0zab11tB+wuGtGWHZ1XnodFTuE1kxjaws4K5ZlfMXzOal3qfUrHvQ1XnLcUo FUkjKg6FAum4SMywX56dwxeWUNjoXE53BpxcIxaOMpbhBe41Oyka9l+VpRIofDEx pQE3/l/efbNO8kVg3uiQs2bb2T0F49db0X7tYEE3LSKYZ35amLTS17SNQtPUgM/p bEqH8YEY34gcYUfmw2OLbzF6/VWurCvpoVxnbSQ9klvCkQyqB+/PaOXB0DZ2dMCf YiBfpME2o5QXZHGt9luEhmxXhWkR/EBWoisrFKBaxBAfqpxVZcdwTyhOj8rjEpim /LvSLAmZNL4NLzRHB9hMdapXDSTeEdJLBvLPXxF7PjuPWn+Nhn54zQ6fglrsJlXN xDr4+fhQZ2ukiRE02XOSQ4kZnFDJz5QCPZzA6i5/+sFl1QymP//9xAJvtZQh58Or gdcEsuHqPpTJfvz9w5C9VhnB6rbun1LfGBFDc83jUnaHpXs3jSPqef3vZqH1kfMN L/gyoLc9v1LB/HGJYUHNGaP5leVl5jv3MtrNG0HfRQC7j/0XjCSvX/WfL36r =vra4 -END PGP SIGNATURE-
Re: dgit advocacy again (Re: Survey results: git packaging practices / repository format)
On Jul 03 2019, Andreas Tille wrote: >> > That's the case for me. I need to admit that I did not used dgit. The >> > reason is that I'm working in teams who all have Git repositories on >> > Salsa that more or less are following what was described in the Perl >> > team policy. I live under the impression that dgit is a tool that I do >> > not need in this case - thus I did not spent any time to learn it. >> >> People like you are precisely the intended users of "dgit push --gbp". >> >> I think if you used it you would help Debian users and contributors. >> (You would slightly improve your own life too, but maybe not by enough >> to be worth the bother of learning a new tool.) > > May be we should sit down next to each other at DebConf for one hour and > you watch my workflow and tell me what can be enhanced by dgit. Chiming in as someone who only maintains a few trivial packages: the amount of time that you have spent on asking about dgit may already be much bigger than the amount of time it would take you to just use it. At least for me, I was able to simply run 'dgit --gbp build-source && dgit --gpm push' instead of 'sbuild && dput '. Mission accomplished. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Survey: git packaging practices / repository format
On May 29 2019, Sam Hartman wrote: > I'm certainly going to look at dck-buildpackage now, because what he > describes is a workflow I'd like to be using within Debian. > > For some projects I want to ignore orig tarballs as much as I can. I'm > happy with native packages, or 3.0 quilt with single-debian-patch. > I don't want merge artifacts from Debian packaging on my branches. > I'm happy to need to give the system an upstream tag. > I'm happy for a dsc to fall out the bottom, and so long as it > corresponds to my git tree I don't care how that happens. > I have a slight preference for 3.0 format over 1.0 format packages. 3.0 > makes it possible to deal with binaries, better compression and a couple > of things like that. The quilt bits are (in this workflow) an annoyance > to be conquered, not a value. > > The thing his approach really seems to have going for it is that he > gives up on the debian history fast forwarding and instead rebases a lot > for a cleaner history. > If we could figure out a way to collaborate on something like that well, > it might be a very interesting tool to have. This sounds similar to the (now unmaintained) git-dpm to me. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted s3ql 3.1+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Apr 2019 21:42:10 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (3.1+dfsg-2) unstable; urgency=medium . * Added dependency on python3-google-auth * Added patch to make dependency on python3-google-auth-oauthlib optional. Checksums-Sha1: c53a26007b86971532e61e9b42b0b9a227b77d4e 2924 s3ql_3.1+dfsg-2.dsc e15a0a2f2ad330de0b15ebc6442ea02b53608c0c 13596 s3ql_3.1+dfsg-2.debian.tar.xz Checksums-Sha256: ff420503dd946901f45d9c168e12cd30d464d687eec78df442f9c9bb6e118835 2924 s3ql_3.1+dfsg-2.dsc f2ce2fdce159f62b8424d430c1ebd1e0a620ad3e9a0ce7e0c56550b60b174789 13596 s3ql_3.1+dfsg-2.debian.tar.xz Files: bc533cec4a0291677181b3bd6fc41e86 2924 misc optional s3ql_3.1+dfsg-2.dsc adbe13a00e380f1e7ba102941f694cca 13596 misc optional s3ql_3.1+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlyuVX9fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfDRIP/iptlAYd1iHgpkZbDZIYujMOfe9lX+KBgIwWYDeC0tj0uYkH S77EfC7MsjpTfueGPJjCMbe+CWV8G6JnjNaaSxAJG5+/QSf/ttiXqjed9WhDgVIf iTX4eMv8AMUjw2uS2tkHYupKJ1buTLjNI6b3tfsiEJT4/ahwSuxqvieLKFtd2zi1 YCEqEtB/CHddRoZN1Wxq/DcYRv8rGZRrPcHSgygS8mLpoUJYui2KBZ4Nj1Gex3aL mMXvBXLboQdyuwVPC62Q+zpkdYJc+zDmr1g2PAoIrWSR5emOdlYKLw7YlyuUKFrt zowk1O74Neslg0bwwtr2yQUsOa7iirTHYiNr+dY9oovq3tav3MpXqE1xJoHgLLMF 1Z33/jhS3wYOGhw8bYs+XeUll5RZqclnt787VgHO+OmutU9ss4DlKv9PfcQBrGwy yKin7okjKbJD9SEBlkmmtadU3NqtIKWeknTWxneRCxFPZom8OXoNqpB36EeOqqTd qIrPP0HcrXoH9ycc+fKGLp/0R4EP3NWaMWyd53AFDCacAYw87RP4x41E2RoROdUZ sbE49UqhNA/VlKMXFOlGctzzGfAux6E0fUGuGg/wiGTVmPl5JhblVsuZ+2xdj8Cu fHMWoztg+v9EO5XKquGPGRBQ8t4p6ZxirsnxWd7e2wHQSTFGmrYkvqhLmutW =syZS -END PGP SIGNATURE-
Accepted s3ql 3.1+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Apr 2019 16:28:05 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (3.1+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 141349da6b918f58ae62fd21635781fc667dffc6 2903 s3ql_3.1+dfsg-1.dsc 59754f3f5688b9f9de075ab2d48b57067e00fb91 667710 s3ql_3.1+dfsg.orig.tar.bz2 4b5c0c01561ce9a378ba1faf84f7c3a49094d2e2 13360 s3ql_3.1+dfsg-1.debian.tar.xz Checksums-Sha256: da531401855e90c924cacf1e2b58d6a5b7a281aefd2a2ba5c362a3c9d262b036 2903 s3ql_3.1+dfsg-1.dsc 965ee3238eb3e949de9fb2475d1645d8babee9ee2639c078f96e830e155e664d 667710 s3ql_3.1+dfsg.orig.tar.bz2 9e8200805532b067f80c2247f405f6fda13d1a478b49f9f4af5204b71a3f5370 13360 s3ql_3.1+dfsg-1.debian.tar.xz Files: f523d0b1bc5237d46b93e99acca25f1e 2903 misc optional s3ql_3.1+dfsg-1.dsc 02063d3261eed66c5a501fd45faad700 667710 misc optional s3ql_3.1+dfsg.orig.tar.bz2 75d7e6d5e65cee1eb8dafc789bebbb91 13360 misc optional s3ql_3.1+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlyox2JfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8Tlmfs/UQAKOd/xEtmpfbrf3frrv7scD1P3okqnZaebaejQIE9vHxEMIw fEB1vCPLuNp7YoZhj+Twrrp+7hni5OhXqYv9Np8kkGsBapq/h3K5WwQ62m+D+rKa rePNAgWaNBf9JgYRWn4RW4i2D2W62igF/e833XPNZT0Tv7cWQlgNqoL7LpfdDrnA rDbpeItgTGk+W1phBgYUIU4JMJKglJEj7+zzTfVOdIzlOcREHkoznHfj1eduyTPn M1qWiPOWxDW2kT6hv9fU5MwMnctjT8GEP27HpoPYd0WzI0wrxStWprP1ZDskMx/s uVyFGaVffG/Jqix50pe38YW3HrhdLeb2AsxxzZz0yVfndx9b66f2MFSW2AdT2eoL 6E11spnOiMAuhOMRW2ra8Z8bj1APkkxPgyvTFH5yHoc8zDfzdcUKqxXdRbxf3cEu 6J1iovmviseJ9u50gGd0sKjXvIKyxJar6F8b0EDzRKup2NEjP5m2idteNqAkn1dz sBftzV8sIhgVOptdrszlb6oA2AD6puyNlIb31VRoJhYfDdTyZ3yrac+N8wPoNKY4 YfpVYet7uhwY8FwMjRmP4XdGgL4LFWhhRFeXC0xJWwBFjxK0mZE5WDAOjXrQIMSp LPOBZFP+NOuhwlmUWbbUlWgSzxafHIaiLCO+jzHBq0egU0l3eFxQWZAVjaPS =c9oj -END PGP SIGNATURE-
Accepted python-llfuse 1.3.6+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Feb 2019 13:00:32 + Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3.6+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Changes: python-llfuse (1.3.6+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 0a21b7ee16b5bb2000347f3759d1d6aa0c4b0a38 3053 python-llfuse_1.3.6+dfsg-1.dsc 6b8898fea911eb5fb91f537ac6e6ba0e1e47a008 215780 python-llfuse_1.3.6+dfsg.orig.tar.bz2 69195081dcfd9f959b5f4ba61aecc4214c22deb7 139804 python-llfuse_1.3.6+dfsg-1.debian.tar.xz Checksums-Sha256: c84606cd29608c7633e80cea1bd5e566842836e9c1c93b89ffb46ec4de8fb3e0 3053 python-llfuse_1.3.6+dfsg-1.dsc 89820f9fe79a30d596558f8eeb1ea79c1a789cc44be1a6a03cd16a08cc52eef8 215780 python-llfuse_1.3.6+dfsg.orig.tar.bz2 c9d36a362cdd884dd23f3035a2de9ad3118850ec161adc44713bb6f309426a71 139804 python-llfuse_1.3.6+dfsg-1.debian.tar.xz Files: 1577bce4210b9159ef62ca273bae0b46 3053 python optional python-llfuse_1.3.6+dfsg-1.dsc 8323ed3ec19768a831374d6cec71a503 215780 python optional python-llfuse_1.3.6+dfsg.orig.tar.bz2 1b3c94f61084fdef3f9bbe90c0d300f5 139804 python optional python-llfuse_1.3.6+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlxlaFFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfAmEQAKtYthl5sJH30zsVdoWUjCbj/cx0ROpVqT55fXKUw69rOHO2 UJfYc8Y38KNKeE1+ZmZUMtVNVsGekHv4YvqDSIYGqzuZq+jhdyA3vicpn/cvs3Gp gp4GqO72utyIb/lWhR+yiBGDhXqQn0LOVYNpBkl5gMyDvEc6q0mJOmfzOU92eJfd 0McURC8c9c2RKKLAx6zoRB5arYluTzpR1+p/N+WAAaGr1HIj1htGgxZkQxLnKClA U9iT77TH6X3uaihm9jS2UpOjq9syJw/tnpqNNr/ni5IE3yiiQIOITki5dDrpXWjb qx9hKZSCXbHW/u+3vaBWKxq6W44jEXFVGXnXfPlxzyY1wxwcthL2qAyKa3xe8Fdw tsofqTGov8U7nOXopDF66wmGCUE5DMihCeyXRAHnUvIgWSeBxs5GTfVlBBw21ofN NZi8u0cYpIiFeyx4KGDyrkikO/gvNUs8C0H0Rhagv1NpqRnF6sgTIidsw4qbmuCc +FVgN6/d+VcQMUHnaWB5N8d3nNpDAY2GrHOvKw4wV3dHSgZaXZ57Nws+xzh+j11n wftIVyQ9P9XSVBGPLOVGYytpSAkOmA1iDfjWy5pLzsxNAQwyTl/r0eDNLCSIO7na RsZ8wEpTWWazCmLnOiwNqDpguz/Yuo/5YVqyjoDrVqNsAXOWNO6YZmNGpF2g =zqpM -END PGP SIGNATURE-
Accepted s3ql 3.0+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Feb 2019 10:09:05 + Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (3.0+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 9c5d1575ce4c1f9582f389ef6c33b89d0774d315 2903 s3ql_3.0+dfsg-1.dsc 92d78f158e026a7bef00fbdbc9928615a47f3b29 661776 s3ql_3.0+dfsg.orig.tar.bz2 11db042c24cc0c6df721199a997431fffe308889 13148 s3ql_3.0+dfsg-1.debian.tar.xz Checksums-Sha256: 0f868efc793086da5b239a4f08bda61d5384ac31f7e17375c3db3408a589e867 2903 s3ql_3.0+dfsg-1.dsc 839d4137dad98eff2891cf1099c6a7ec69e1426a5ee5538867951d9b6cd6876d 661776 s3ql_3.0+dfsg.orig.tar.bz2 9be1285a28398c154059a71a1da72767332baec332c7752af184733b360a4048 13148 s3ql_3.0+dfsg-1.debian.tar.xz Files: cebb20bee4f05043d0f4fcc9ec44e46e 2903 misc optional s3ql_3.0+dfsg-1.dsc f74af38b9834509cffef50f0dc427676 661776 misc optional s3ql_3.0+dfsg.orig.tar.bz2 81ef4fa7bb7ee47b2742ce8e6e534a79 13148 misc optional s3ql_3.0+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlxeqAZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmffH4QAKLPScmD7ojXGP1DNHXcEFkP+vafGvE3Z8NW77VFgN9IdSWd GtOJzvya4pW8LFVfUbRw/A+uYiIYQku2Ci6KVTGqZKEZE/ZLAOSdoyii47C1/y1M z/BcT6G5C5vmUUOX3EkYd3Pr6ASrG1JZRiZgJ3ZbAdkDYXoz/tEiS2a5z0NbjMqN WBuKkscsZcGRvgjkMV8XavsrM5sFNwYuc++y0AlZbRJ/f0PT1J7kb8tmcrbmRa/X 1N4npTLhPC2fvTXCpWakAs6cHrCB5slxhcdQq/7rP5R1xWnhT4Nt83hC36Tu/tAM 0KcN4IEMWAZDCdqoE+Ii/1FSNBBnnLmuDhLKl3fsqOCjTf/STpUNu1q07BRbbAEQ noj4UloU1gsLQVi0YisrpRtLkG+3dh0Git3T8ykDY6VMmzoFtmMwwRSmrhqrywDf vARpaaluZM0Lnx4XiORGZ4pbSB5txxnK1E1JY85x0XUhWzojev25S0xbNam8r/72 Vs7aaQCXDYQPe7NElVoNfY3OVpFDbDrc8gQYtdeUBfOyeOeSokoJRR2OC1UGaGMc jTZ5fcA4srWphRO87G5jEVVsRDi1A6aTo1H132JLUJP86VdAvTddQuJaTgCuhooK SDdgNd/r2cLiUkjbBvWNzLg9SlZnZ4RVlvbNx/+P5EsVYeiaGYnPS5TlAlBu =dzeD -END PGP SIGNATURE-
Accepted python-dugong 3.7.4+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 Jan 2019 15:45:15 + Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.4+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: python-dugong-doc - HTTP 1.1 client module for Python (documentation) python3-dugong - HTTP 1.1 client module for Python Changes: python-dugong (3.7.4+dfsg-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Remove ancient X-Python3-Version field * Convert git repository from git-dpm to gbp layout . [ Nikolaus Rath ] * New upstream release. Checksums-Sha1: 51c8ef35c1bb9fdea5d2476857ef5e11157db92d 2588 python-dugong_3.7.4+dfsg-1.dsc 9b77dea4eebd09e14a468ec84e9686c72cdb055b 51655 python-dugong_3.7.4+dfsg.orig.tar.bz2 838bdfdfaf6c6667e01f89d397af844fd9eaf835 133676 python-dugong_3.7.4+dfsg-1.debian.tar.xz Checksums-Sha256: 015fee466d23bb81d5c9d0a3ca11fbf15b7f88c7c60695881ab3c63761347f3e 2588 python-dugong_3.7.4+dfsg-1.dsc f968a30024f1c6b9cfad33766b38822b656aac9841cf5397e75fcb8ca508b742 51655 python-dugong_3.7.4+dfsg.orig.tar.bz2 bb4b0d54b567532aceca58b5960aac82936f3aa398fd52f8d44465ef7ec824dc 133676 python-dugong_3.7.4+dfsg-1.debian.tar.xz Files: 2a0c192499872ef9e616e1cb50b0d3a3 2588 python optional python-dugong_3.7.4+dfsg-1.dsc ddf62cd7311e16fe466afd42364c18df 51655 python optional python-dugong_3.7.4+dfsg.orig.tar.bz2 75e25660b8e74c5d5c94e6f75edb3d4f 133676 python optional python-dugong_3.7.4+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlxDRvpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfzEQP/1vHA/GaZG1ABFb61/u5L028WRF2liajyTlx69ZdxizTQiPu IHOgo+8+4xC3EukkzpXQfSxzYacBxhkciZkH9kg8kClXRR92sKkFt48aVUBRO39/ ofaQTwAQbPonUcBkWistD2Fc8045FbYiIM1flK3lpx3iytKFsJH4bpeXkgpebwwX n3qshLon3gzcOkPFKpIGByPZdOfc3nhCZcDX58w/AGuZgKGBdN7iPLhpoEh5NNnu CObHCIMufv57yiP3jzBg4IrE5Jogr0ufwzBdx4Ui2M/R2nw8/skJoS2weeaNkC5L HfuGKx1xo+SrOGDpdsqAhJuKl84qqzeIO4pE0teZ+JfuFXkxr6OWktq37KkgVtQu ArFMkvm2BV7IZgqY5CxMXVJ7Fv3XgutetrTq8CZdYf/z2ojHrSaipSIHvCnUq/64 1mRkpmQlDspAnrRW5Vp7RdAN0cLPk5ayXdE8zjv/s8qzTF6obxVepaLTgrVAXRwR +6sMz+cNcnZNJOUlgG29/NyfFsxfb6MpbyoL+jqLpu0yVOr7ntZoCMBCU3hmU2fx h0QJKp9Brf5W9ir0cwe1jJM1Ws7ah9/g6jdAjQxC9WIXj+SRNLSp/MBA9wb9HgOM LHFhvMVRIJJTCiDKooSoXvkyh7pU5iTk1CD/kcEwZ/iq4WW46pEqGD4iWm9v =6MsX -END PGP SIGNATURE-
Re: Bits from the DPL (December 2018)
On Jan 01 2019, Chris Lamb wrote: > Hi Nikolaus, > >> > * Followed-up on progress regarding potential new "Member Benefits" >> >[9] and ensured that some previously-promised reports for events >> >funded by Debian ended up appearing on Planet [10]. >> > >> >I also provided solicited (!) advice to a few other developers on >> >conference booths and suitable/alternative conferences they may >> >wish to attend instead. >> >> Is there something missing here? Attend instead of what, and how does >> that relate to member benefits? > > I don't believe anything is missing; these are two standalone > sentences on different topics. ("X conference? Thought about Y > conference instead?") Then maybe a missing bullet point for the second paragraph? But even with that I remain rather confused. What is the conference for which these developers wanted an alternative, and why? (I'm just very curious) Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: fuse -> fuse3
On Dec 25 2018, "Theodore Y. Ts'o" wrote: > On Fri, Dec 21, 2018 at 11:03:34PM +0100, Oibaf wrote: >> The package fuse3 is available since awhile in sid/buster. >> Their users however are still using old fuse (v2), e.g. sshfs-fuse. >> According to this: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912528 >> fuse3 is not co-installable with fuse, but a patch is available. >> >> So is there a chance this get fixed and sshfs-fuse and other package can be >> updated to use fuse3 for buster? > > Thanks for mentioning it! I didn't even *know* about the existence of > fuse3. Is libfuse3 API compatible with fuse2? No, but in most cases the necessary changes are not too invasive. > P.S. If fuse3 and fuse are not co-installable, we really should have > managed this as a formal buster migration earlier. They are co-installable in principle, this is just a bug in packaging. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Bits from the DPL (December 2018)
On Dec 31 2018, Chris Lamb wrote: > * Followed-up on progress regarding potential new "Member Benefits" >[9] and ensured that some previously-promised reports for events >funded by Debian ended up appearing on Planet [10]. > >I also provided solicited (!) advice to a few other developers on >conference booths and suitable/alternative conferences they may >wish to attend instead. Is there something missing here? Attend instead of what, and how does that relate to member benefits? Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted s3ql 2.33+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 28 Dec 2018 20:04:28 + Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.33+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (2.33+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 15fc569b84b1745ba5b02307db7f209cade828d8 2905 s3ql_2.33+dfsg-1.dsc 13f2f163d30c54d5e0297b74f1f3d879c71dada5 657770 s3ql_2.33+dfsg.orig.tar.bz2 9ed524db64308e305b83d58c113e34187e8476fa 13140 s3ql_2.33+dfsg-1.debian.tar.xz Checksums-Sha256: e4e8b6b916f41ca37084048499941cb0d4425dceff01640d6ec008465302f9fa 2905 s3ql_2.33+dfsg-1.dsc 44c9adc0a1e200c85426e6614d8926049a1a3ecbfe24de35d56da597b33b0f77 657770 s3ql_2.33+dfsg.orig.tar.bz2 3f1a28572654c23f66d2db9b63cbd34ff21855332601f5000e197c0e47177862 13140 s3ql_2.33+dfsg-1.debian.tar.xz Files: d5d0f9436ed8b0b389248633fba6ae77 2905 misc optional s3ql_2.33+dfsg-1.dsc 9cc6a36e2fd99c2e6919882191ede395 657770 misc optional s3ql_2.33+dfsg.orig.tar.bz2 636ac977afba12b10b358b8ce827dcc2 13140 misc optional s3ql_2.33+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlwmgiBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfzCgP/3Cj1uDF7lUVg4hm55LlLK6llmGlJPFkWhXjzfmcF8mbP2mS Xe2YymRWEDCsWoabscxKaTs+iyyfpAO/HgaWXh0FwbBcfRkzUWnEnd3y64qbySek 1OJaoqnBnsbEjV2gyUYBUBgCwZrD3+jYeGVNdYqPaADqKhM1SwTUOj7mIDNhNOlF zhDm3pgK1JzVs9heSr2IrhB8Ywd5m3+kzeX1U88WxNBS12fokuKeZSeTEGpcYNOa +IdE8Cgk509zG26U2jL8Gb3dOwbp3R1CH7Xv7rtMX+4M2QGj4dyrGh3uS6xW1S5e kgZD89bjPgcBBflsVPnGBd0uGUV+Eza8vhFoOmGU0Qq5fQjRZZyf00nBzND9OJwF BCBv962b2NIOvJZ0YqupVgqCDbPkY5LmMHrAE5s29XbWRrHvxUXss3XFbNHcy/qQ qQ5rgkLAIqeuC3XlktcjCUAsrpkZnxyIIiCRzREktst1eXqka3phD1Hvix7RQsNK zrBlpbixvD60mlpXaQ40z5hV7VSaVoktaxH3ial9GmK4ZbN7DSJXtiGDuNT8DX1x GUc784V5qUt3rtt4PCDOtzAs2aAQdKN/myt5rAOPSLyMa6oxbNdtmS724d4UF13o AjuU8DMPgiFHiMsKZ0EeVpdKD1k/QPd+zuLmj6b3SeCrh4l/afweb+GtcywB =xncQ -END PGP SIGNATURE-
Accepted s3ql 2.32+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Nov 2018 19:40:48 + Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.32+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (2.32+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 79f0bbdc167c135aaf32855bda665cffd48068e1 2905 s3ql_2.32+dfsg-1.dsc c16250a6a6403108e14276e72798f627fbbaedbc 703451 s3ql_2.32+dfsg.orig.tar.bz2 9257c0a30b06a71f9192eed26fe3af7396c1fcab 13468 s3ql_2.32+dfsg-1.debian.tar.xz Checksums-Sha256: 1b44cd957333c56e575987a86b55ca0c4a619a6f54fb046e8ad26e2c378b8dc7 2905 s3ql_2.32+dfsg-1.dsc b678c28ca0de11273ed02bb238fb911091626613c7b68c28507cd44d54a00eed 703451 s3ql_2.32+dfsg.orig.tar.bz2 331467d3384571025f889eabbc416a7f635b6e5ef8d92742ccea3493264bf7fc 13468 s3ql_2.32+dfsg-1.debian.tar.xz Files: d4a4a4291b6350ac1bf4b83fe53cdbf4 2905 misc optional s3ql_2.32+dfsg-1.dsc bea4fadebaf069c3e8268abde7d3b07c 703451 misc optional s3ql_2.32+dfsg.orig.tar.bz2 9506adc6415ed2f683ee53dda697959f 13468 misc optional s3ql_2.32+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlvh7rpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfBe0QAIMrCAF6AH0kOcNI5upUxUA2OmQmDAHHFwiDyXEdaOdUm9+i nYH4KZ+N0Hh8DZkBuq6udHfiZcNj1AnCM2Q/wSsfIuXAjzbfG7QV9zVS8Cmq1DxR Wf0n+nhpc8BqJkv/SyWugzod+fGQOS3fxoq9qCek/oWoiuB8n6pMTk/wyBklI7LQ Uo0MRtjAjeUI7gSfrqvakG1t/Tl1ze20fDm4rYTf4EUI/n2dSVElq4zqWSVblbWW Fmygsj7ZRrt4ZUjvElirRMfBHeCz3yhYHRIgfOC8F3cFedJkAEllexydZGMqycs7 c8UCX+BDvJuH8ulaVgJYK2RHGUBuPFWVPBELODhhXO72bsPFr+DFZuCtTnHZx9sG V3MyE80k5lHZzUWmKAz3rTeUZnqA2mu1i08O1H2cbStM2dAN8e95m6Jg/XCGiagK nVgKFvMUePRePIsbWpqfwFPvzac6TuEOlQ7PKX8LV9xgIocyq24PuLAuMgnIIGrd quwKjNa/7pCZCXeNCMubQUzrtusMPPQC794Hd9j8OT6PaInV09S7Bb2cysdCYK5a pKypGUayPPLw9HIznGPyvmKL16gNYWN72LXvodFofHOpf+x/dCXDbQ8H2XDuUkhz qUGNdLXvJ6xSGLlxC0YzR1XZRQiidCHHs4r1G3/rEpEHIUB+U2TzCn43MAh5 =NZQn -END PGP SIGNATURE-
Bug#912752: ITP: pyfuse3 -- Python 3 bindings for libfuse 3 using asynchronous I/O
Package: wnpp Severity: wishlist Owner: Nikolaus Rath * Package name: pyfuse3 Version : 1.1 Upstream Author : Nikolaus Rath * URL : https://github.com/libfuse/pyfuse3 * License : LGPL Programming Lang: Python Description : Python 3 bindings for libfuse 3 using asynchronous I/O pyfuse3 is a set of Python 3 bindings for libfuse 3. It provides an asynchronous API compatible with Trio. The package will be maintained inside the Python modules team. There are a number of Python bindings for libfuse, but most are not compatible with libfuse3 and none supports asynchronous I/O. I intend to upload the package as soon as someone decides to package Trio (https://github.com/python-trio/trio).
Accepted s3ql 2.30+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 02 Sep 2018 12:48:32 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.30+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (2.30+dfsg-1) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Removing redundant Priority field in binary package * d/rules: Remove trailing whitespaces * Convert git repository from git-dpm to gbp layout . [ Nikolaus Rath ] * New upstream release. Checksums-Sha1: 0c14740897211f77412d5212122fbc80b960bddd 2905 s3ql_2.30+dfsg-1.dsc 82ad7bd1d4bca574d548f91ff5a3fea639d02ce1 608412 s3ql_2.30+dfsg.orig.tar.bz2 dba6c260e919ae403c3c679edbd8fbcefa47a52d 13076 s3ql_2.30+dfsg-1.debian.tar.xz Checksums-Sha256: a636800825a1c5e3d910211fcaa970baf2ed403cffd1dc97761af78eb03d7312 2905 s3ql_2.30+dfsg-1.dsc 2eba9a6783eeae4ea70cced50cfb41fb037831f05313eaaf2ad78f1736c4acd1 608412 s3ql_2.30+dfsg.orig.tar.bz2 25305385ae1d8cbaf56e7a224fa1772b13e5124218dc9f4b2d5dea623e8044ff 13076 s3ql_2.30+dfsg-1.debian.tar.xz Files: 3c84cf3f924411e839a91980bf3899a8 2905 misc optional s3ql_2.30+dfsg-1.dsc 3f7de8b870ada44dd987bf381d75c0c7 608412 misc optional s3ql_2.30+dfsg.orig.tar.bz2 d009e54a0cd77869fe6a0902cc637c2b 13076 misc optional s3ql_2.30+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAluL3FpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfudYP+gIgHFUddr3/taHfbetLjabp3yfNqeTtxXlCEP16fIrLBwMM oLBIRJvBD6zAa33xWS9+/bJMxP6VKwKA9dGmdQTMY7N8u0hyI6GUSqtPWKvxgE3G KRqqt4Iv0Vl6h6Ow7JtgFimvM3ORM+neYmwLrdOAkTNUJRbwGmBtT2I1ebI+d7Ox vYY01dgzm5sCB1ytvOiHF2mH+/F3WUYqxrI4mkSl9p17YHENaNW9205MpMG2+t1S wN1f8EFRDKrsbsA8YC8xJmqCpWSfAcLQnGrApkiw4oMP/inE/iaOr8KEXDbraM3s rF0eBzBbN8U5vhXP/bFkXE8hpw63MYuuOV8/VZkkt3ycDwm6QoUuWCLOydfjuv/u cOXprWO/vRtAlm2i4LoyNH7VNZopP46mUV3f4qmHdw6vCeIHnngArhRyL3GRl5Wr O/5sK3V7Tcf8ANq9W7l9Q4ssXhHYS8Rg5GzY/zgv3XQFIbKudBKlq2bkaGTW+sn0 BISc9673a1/vDlUKLAzrumhluR1vNjc29myYMYu7r1sJ2FXKb/aOrCzK/VfFM/xC F1Tcp3Y8VoUhptdzBVcUMryUBugAshGOw8r09skEkQeAgAZnuW4EOEV2GHt52ohi ZCcX/mWXkGbR58vXBDKHpwhQujEPbvn5k5yoPshTRXy1zO3+U3VX0Xxgw0Zt =VZKn -END PGP SIGNATURE-
Accepted python-llfuse 1.3.5+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 30 Aug 2018 20:24:40 +0200 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3.5+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Closes: 906080 Changes: python-llfuse (1.3.5+dfsg-1) unstable; urgency=medium . [ Ondřej Nový ] * Convert git repository from git-dpm to gbp layout . [ Nikolaus Rath ] * python3-llfuse-dbg: recommend python3-dbg, not python-dbg. Closes: #906080. * New upstream release. Checksums-Sha1: 7a43f83814bf3990003d24eade456e6ca3423344 3052 python-llfuse_1.3.5+dfsg-1.dsc 48212db32efac147a68ba190c32183e8e01669ac 216547 python-llfuse_1.3.5+dfsg.orig.tar.bz2 ffb9df0538ed3610e8d65dc140b3d9e30afd9463 139800 python-llfuse_1.3.5+dfsg-1.debian.tar.xz Checksums-Sha256: 94ce336cb96a0b2ae8d74acdb1005861faea7aa4e4a4e8aa176547f478a0a8f7 3052 python-llfuse_1.3.5+dfsg-1.dsc a3066eaf2013c47099669f5066ad556cbce91210edd51ed11c6a67859b682803 216547 python-llfuse_1.3.5+dfsg.orig.tar.bz2 13b428b7e594a413195c39aea874764ce9eb39cc79e734b56bf9aa5c2fe2 139800 python-llfuse_1.3.5+dfsg-1.debian.tar.xz Files: b6971b2f51859a976c95f8af0184115f 3052 python optional python-llfuse_1.3.5+dfsg-1.dsc e83d29433fcbe4de5a02478fe2b009fd 216547 python optional python-llfuse_1.3.5+dfsg.orig.tar.bz2 a5c69dca5f93ea34e0394e8a2643c95f 139800 python optional python-llfuse_1.3.5+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAluIPaVfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmftFEQAKWvfUti+wWzJ8lRmpbirnfABW1ZyZCFOBd5xz1H3tyGkXUZ e3cXThRocPN258Cwvl2WgYQx2ZfE/OENEZiBLxvD12htlttG9lauFh8oK5fjVKPD kRjbGKCmcNNnAL+vdjL48bNTsijGpEWg/cwo+Jm8PQM52X65jnS2IkhIz2JtxbAE ex4hTkUduchPcYk8zn7PNzIeMpcLdTQicjZUDEdGwSTxSIKVvswEwQR8YO5mibuN Mk/STNOYHTQM7W5gYJSUDdM64VjCcD9/HsCGAll0rGCYA6h+v9CDikIcrfmJ55Td cfgQOBmEzJcv1TFhyaSk1YM8wdsvxwC1eVaC4lIQUMSxMMoctM21ymD6Op2kwN77 089q+AoCC+KfalZ9gea5kNwTVpk+3i2824WAJDNK6hNzFZy8AXI9pdjRdqkTVDfR s4k4O6T/AX3UWBsxet7ckqaimIxY3gv7Zb4xikAw+jaFNC6n3cbV/oFDD4mEnZoc eA7rOg8CtoPLY2gN0z5G9SqGURKZv2U9d02Izw1rf/zDhBtVhqNj+zTJYpA8ST36 9YjS82mHtHjuUuqU3Km8MA+IzfKncZ3NueiaiPJMSO4+uAoQAvUhs/8hayVP0LcR H6Ioj/HcNoo4n/oAYNEzS1aZhHyylD/JeN7FKkOzSoASSXGIdKcjjboQe5t5 =Wf/D -END PGP SIGNATURE-
Accepted s3ql 2.29+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Aug 2018 11:13:54 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.29+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (2.29+dfsg-2) unstable; urgency=medium . * No-change re-upload. Previous version somehow didn't make it into the archive. . s3ql (2.29+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: cc1fa2e5dd86275698a41083ca90c77f7bd16de5 2905 s3ql_2.29+dfsg-2.dsc 2047bff0d23110cd76c4d581d356ecb8b6a17052 13316 s3ql_2.29+dfsg-2.debian.tar.xz c7425cda60fef8e5ee6d16d872b7107158b24ef2 601608 s3ql_2.29+dfsg.orig.tar.bz2 Checksums-Sha256: 3d2e4c9140e323a1d1de280b66db2822933639618154bb638177821c3e141442 2905 s3ql_2.29+dfsg-2.dsc 94e7d76bb80e8ccc19bc339b994df84d62c0581b91eaf50ff60e4e635acd42b3 13316 s3ql_2.29+dfsg-2.debian.tar.xz 9498f7316b4f83826149a6ab0f09760dae9bbe8e6ffca26ca6d0d5c5b032ced5 601608 s3ql_2.29+dfsg.orig.tar.bz2 Files: c8fbfad57c4a4af412ee8e9543bbcf81 2905 misc optional s3ql_2.29+dfsg-2.dsc ce95686a46a5e115a3ff87ed45489cab 13316 misc optional s3ql_2.29+dfsg-2.debian.tar.xz 61cd54564e137fe389abc1559a087aad 601608 misc optional s3ql_2.29+dfsg.orig.tar.bz2 -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAltmzhZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfoxoP/ibE98DBIpzaZAoxJkkRWvgIkR1SU4OGiGpClEl01bSYfoLN irYc8mA/GM/5EdpQnKhh585GpZkMQ67TdxFCmwBUGB0grnUGO3kdOGt5NBmPwr40 QuvymSrTFmt6twJ39+3zggxm8PLSY0E91abZ12ONe1FUzy/M+1HOKisJZdWpo4CT dPNmC/9xgxp3KnFuAAaAWyUlRODKDxPvVmM7aYY5cq7bKigwNF1UnspETzEwOhNi +6c7netPO9J/I0muomWHnK8GgBZGBZpULdOXOTUSx3l/fIIoD5WOgdjaeiDxI4GQ cfUs+oJYt2MPVdgH0t3lpfX4LQECTiqRPa847dLrt42MNVUpbUnCf6x9YhDMeRYD gO0S+PDQcW2kbxNeHertjNjRZKYMNPbOxdRh3w/1pjxloZjNdzPkyrImcKswb++y 9+JlTEwgLaA+sPEN1JtdXZ44mJzS7UiOBT/5tWEaf6x5K2zSh3lMFKlUo6cOBmoS 0XS550FvpHtk+c59B/oAudlBH6Ajk0rhQ9J96sNwjRjQmM+E+i/raLL6So7NV38b +xNWb1DChD+mED8XPV2eFMJLc9r2f3w3QdUO2S/w9ZqKNi+YI1PT78WT4R2QIoEB NN/0IaR8s04Ets45UtPaari9xFkdLm/JCXeOwXUBN3wpNCeC7P83qTwCrNbJ =fKeM -END PGP SIGNATURE-
Re: Should the weboob package stay in Debian?
On Jul 26 2018, Adam Borowski wrote: >> Promoting objectification of half of the world's population doesn't >> count as constructive social interaction in my understanding. > > That "objectification" is an invention of your particular religion[1]. I honestly don't see any connection to religion here. Even if we assume that Christianity has a problem with sex (I believe this is what you have in mind), this has no relevance to the fact that being objectified does not create a welcoming environment for the affected people. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted python-llfuse 1.3.3+dfsg-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 02 Jul 2018 16:59:10 +0100 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3.3+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Changes: python-llfuse (1.3.3+dfsg-4) unstable; urgency=medium . [ Nikolaus Rath ] * Do not modify proxy settings in integration tests, this change was actually meant for a different package. . [ Ondřej Nový ] * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field . [ Nikolaus Rath ] * Drop -Werror=conversion, causes build failure with new Cython (or maybe new GCC?) Checksums-Sha1: d853c52a17ff2bfbf5f48eb1666aaebb95530f32 3049 python-llfuse_1.3.3+dfsg-4.dsc 5d92566c5984a49007bee495b80249b0286c2840 140372 python-llfuse_1.3.3+dfsg-4.debian.tar.xz Checksums-Sha256: 2ee2e3211126d3fffeb74a0139d63738d43a8c80005d6795d94e76338b9a9d90 3049 python-llfuse_1.3.3+dfsg-4.dsc ea777cfa3bbef232de0cab5021084a0fff0c51d6577a3781841813e17628ac68 140372 python-llfuse_1.3.3+dfsg-4.debian.tar.xz Files: 62db3d0a7a4098ffea62654ed7cc9deb 3049 python optional python-llfuse_1.3.3+dfsg-4.dsc d3770186baae9f7f7506fd53d47e00a0 140372 python optional python-llfuse_1.3.3+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAls6TQ9fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfnwUQAI9wvZZ60ZBP2XpbEdPlBCjKDY4TyLYwfSiWUZhxV5xB8N/R lgEQt1cMsQ2909rxybJtyf+r5cEeC79I23tbUDiviAphHfJnvfO58El+3yvsejwt Ap4k6Lbu2Y4MD9ihNQfHREPSTR9dyAXGy9+1spjfyyLdxSmbDRfSMlTrkxU0c0o6 i0MALElGJOpfldzPxY18AwOjt87/4GCSyAjT3XVZ/IvQlPElcyr/KEiirkACDdk8 SeHt2/CcGGFrsmCA0nSrIcUURsw8LwrSkOmAZUmFTqlm10gwhb9fOhzkC+LA6CZh qAsGBEEHLQhGSvQh+NUYKvzHHFrAiKzIz2a3weldebCiMY4eWxsMNV9sf+jt0tws +4GG18lZUIXxSMV8K+Y3xa2dO7+d0fiekcPza+Kqf7EcQcJH3vcXdddpfCybSHR/ rq0pFt42eXT09qZeKFYUc5cjjZbqKj/4leQ8jH+4nBlqgh1VBayP8PREXZe0mE65 zittd8weXnm1iXr9l5iwuTqqcPjwjtxcg5K2teE+qsHeZNRoyMVWg6wLrZRLZk3g z8T6qUsVIffIzEPnqs58ZUP+l36RFm0UXcs2Owmi4b6GkdyCFwSQi22c0F/bp4TF bLzcqyRhDUakMgxrY3F0lWQKa1nLoTh6qKh7JERq+TQ8s3Zj5Zep7jLUmwya =i/O3 -END PGP SIGNATURE-
How to help getting libfuse updated?
control: retitle 840075 "Please package libfuse 3" thanks Hi Laszlo, What kind of help would be needed to move this forward? libfuse 3 has been released in 2016, and this bug has been open for even longer (giving advance notice and referring to a pre-release for testing) with no update. It is important for me (as upstream and user) to see this fixed before buster. It also blocks the upload of SSHFS 3. Please let me know if there is anything I can do. If you absolutely don't have time for this I could create and maintain a completely separate libfuse3 package . I think this would require some nasty use of dpkg-divert to handle conflicting files though, and having separate maintainers for libfuse2 and libfuse3 doesn't sound great either. I'd much prefer if I could somehow help you with this. Cc'ing debian-devel in case there's some mail delivery problem or someone else has a suggestion what to do. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted s3ql 2.28+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Jun 2018 12:19:15 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.28+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (2.28+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 2b59e75bd1ab79cc3672977186cfc92148315f85 2897 s3ql_2.28+dfsg-1.dsc 1650ed626fd9857156dfc87ead2a76357e0ba755 598527 s3ql_2.28+dfsg.orig.tar.bz2 8b6e132e4529691480fc52134aa480c53f4a09c5 13256 s3ql_2.28+dfsg-1.debian.tar.xz Checksums-Sha256: fd2299c86e86d4a3cec38f361119ef299d6540400612328c3e7af4c3e9cc0ae8 2897 s3ql_2.28+dfsg-1.dsc 025ddcb3ff41e4535422c15bf2ce6e23311b19b480288e9c300372afa28801e8 598527 s3ql_2.28+dfsg.orig.tar.bz2 b614f4fcf6c5691a52af300d6c5a04c5906962de15685e806aa75cedece7c03d 13256 s3ql_2.28+dfsg-1.debian.tar.xz Files: 40fd5e9c21fc596a7dd72cf54b832111 2897 misc optional s3ql_2.28+dfsg-1.dsc 856e408b7081566b258b158845fad024 598527 misc optional s3ql_2.28+dfsg.orig.tar.bz2 1e07d4e390786908dc893fc23b9ff974 13256 misc optional s3ql_2.28+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlsiT1lfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8Tlmf6mgP/1dLwf8LAJJoYA1inIqLgtNr2zUAk6CYUt+X22hl7PGikjtF FPX4qarl8SxSNpVNAvXztDPgtqwhZj6SLMJqwijb9XCcUG6PENLDCHehSCG+PVGb oawLvuufe3QGuMNXGUZl1GW8fxThAV4HKDV7bZ7l6pVR0dZQiDe0eHzkymh9zFmw kHh/KlmLx8EzquJw/+aWXL73Vzh7vodtfLzjg8bqb4IdbbWUdY2cziZ3tIc6hBcX eNrSaE0kDxF0ltNPgG7Pf0ra7WpOu78J30EtMfFqeN/U1PskLXZoRqoM4xDrrkiH dvMVqTVVUlkol0juJlIV1ulzy5SBaSVBlyj/IOWjcQ+eh5AebUOYktdyOpweGlbE gxai5GQCFWNSgnh7FEgp3Ul7T5RZfd2Au2MJo17h84Xb4rrL9mEuA8nFqMrkOeMM +6U5RDa3waPdBHh/3Q+3PQxr6z4H/AxozESFA47G40wgxaRf/MNvh8AQgVCSF0zE 3OYfv1mcWhxtNbKkUIUm4UtVBpijLuuGwZpT3mVU6nXVQAihFV/gxZOhyhdNtkF+ Xu8kDn4aR/IripinEqNMIB64BTeDwd0xrSVR/j93K8Zwpx89MxbGtWFp3UkBoyxX Ym84bqy0hLsTDSb4DQTDzbin9lR+GNbg+8aWW3uvwnJV4WbuB5bR6b2wGhT9 =lnYT -END PGP SIGNATURE-
Accepted s3ql 2.27.1+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Jun 2018 12:05:27 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.27.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Closes: 851375 Changes: s3ql (2.27.1+dfsg-1) unstable; urgency=medium . * Sporadic test failure in t3_verify.py fixed upstream. Closes: #851375. * new upstream version Checksums-Sha1: 0efa58d2eb6a5ca03aa8b7ab97ef20ba6110256e 2913 s3ql_2.27.1+dfsg-1.dsc 780c5c6715b0c1202d8f50b2d8765f2fef4b7f16 597087 s3ql_2.27.1+dfsg.orig.tar.bz2 20e76658f50456c769dc73ee3ead258dca62cb6d 13240 s3ql_2.27.1+dfsg-1.debian.tar.xz Checksums-Sha256: e30c3c6d7d71a5bd22e9d3078c5554c5e32e17bee3f92ac9f46b190e687a8e6d 2913 s3ql_2.27.1+dfsg-1.dsc 5653bdb84142f002081369ec7825b76fcb88ea4b62a7d5f78df15de6aeb807e6 597087 s3ql_2.27.1+dfsg.orig.tar.bz2 9e5fdf5d6599a41bc14aca16d433a5c84d6dc5e6124353ca497cd0620c718822 13240 s3ql_2.27.1+dfsg-1.debian.tar.xz Files: 4b233b81fa0542b7c090b196110a1955 2913 misc optional s3ql_2.27.1+dfsg-1.dsc abb61f287217304b955fc0e3dd4d18e1 597087 misc optional s3ql_2.27.1+dfsg.orig.tar.bz2 7b8e33ac20b98d659cd16114c743f6de 13240 misc optional s3ql_2.27.1+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlsbth5fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfgxoP/ROpr1rbDYT436Qvv5GDNkuV4RNQj5iLqyYFe5pfWQptBz9C iuQw9ZIVurjYY41uVbcVj0aycyII4flYRaYTAH8RwEWdcvVbv0qk89A2vEVainrL B9Eq5LZSvhEtuMg2lor2R1w/r4oImOJtiD49boZg03S5znqtY/C3r7esE0VyvEPp PD/uL33BJSvJYvs62WimF3448N4MBoLJEnVuv6wMSlXv3bntwT3e4dysk77h3L5d jxaI9TEV/8CJ6tCxxAjbo4yom3+x6RHyKvG0aLUWvvD1VQfbWMmbkJwZ0OtJqHco tAvZ3IvLbPXOUikioyypLGSl2N17gLPh0tSDeYCctFmb/OBw3ph3oAY2dALYZkaF prz5D8M5fqM0mQn/jrKj6JFwCP5pgA7ZEY9NVp1XkzkxMmvBLACW1wIycxoYuZhe VTClmNSK75YemOEf1Ij7difkoBRwGhjKFlr34mn6CMhOxxBx7DZYwjL77RdGG/6r 8wQbQ8Y4JnNYuigceU/AGYc7v2Zvi3N8iaWYC8noMKPHQR9Vu2/JaNpmunxQi4a6 TEtLsH0ABzr8OaliOG03POnW2HxVyfKChGd5k4aCyGibgBK03xvu47iFz7rzD6D+ XSAgwAbvjWLZ9bwN3XkjpvIyV+BqmMco9Ne9wGsCtJ2XWi6QEhqtlE2FwrIb =Xmza -END PGP SIGNATURE-
Accepted python-dugong 3.7.3+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Apr 2018 19:09:23 +0100 Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-dugong-doc - HTTP 1.1 client module for Python (documentation) python3-dugong - HTTP 1.1 client module for Python Changes: python-dugong (3.7.3+dfsg-1) unstable; urgency=medium . * New upstream version. Checksums-Sha1: a9f9228e2e1cbae709b811e197b7a12d87c1ef9c 2586 python-dugong_3.7.3+dfsg-1.dsc 0f83814c6e7866b10eb901bd49b53c52e21f5462 51513 python-dugong_3.7.3+dfsg.orig.tar.bz2 d7aebf00bfa5e088333d90025fcc0b032566d69e 133844 python-dugong_3.7.3+dfsg-1.debian.tar.xz Checksums-Sha256: 687b76ab0c6bca0cd1280f54b53422ea8f7a3b0f9f5aa894eb5ee9b7fbbe0c8a 2586 python-dugong_3.7.3+dfsg-1.dsc a883cd4280e2c1ebe437cc0a9006193420ef09b3b479292bd664349b4722 51513 python-dugong_3.7.3+dfsg.orig.tar.bz2 0aebf23844067be9983841a99cd85b8b41c3293c7de4ee7198de8cb059dba6d1 133844 python-dugong_3.7.3+dfsg-1.debian.tar.xz Files: 299032f0e2e109f3b8862dab6b0ccff6 2586 python optional python-dugong_3.7.3+dfsg-1.dsc cae40e5566ecc297fe92dac2ca070449 51513 python optional python-dugong_3.7.3+dfsg.orig.tar.bz2 c16183ce531f482871576342ebe1c5a2 133844 python optional python-dugong_3.7.3+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlrmCnlfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfzRgP/id6h3LPDSBHFmO9cA91PTDVSJT5M0uJ2PDuLP51pftEFL2M LEHlMmEwPdiB/SldyWgFehPEvcnL+X5ixHAeicPOSlgEirjqQYFd6Xy9PNwTgoFl LlPpxu2ASN25Z91rxQnVWIoRmeAeIbsa4yJ/7eNVfkBUCAyvTnqij02attQAalGO v7pbAGtmXwzuPrYjqr+eUVde3enk88ESmqlicOS4OkDkOvXEXQIFcuTWixLlYoEL k80QrflwyuhMGjw6+6vJQpQ9hGv6WvCT9SergIZp1HfkNfziwOY+zcANUZDoaUFQ kbddGbv1oV3pUc4B7ELjfbJgnicnzYriu//Sb2ROgbsw+rr3xNk67rqFAoW6d1ZQ 2JTFqKB71sHlG21Qr9lHGwBXaWI/mU8NuwceabYlwsbIL+VGH00vkdSMUftuqCcD Vlx7gAQNRlZJpf7v8/3NiJnscb7Oc4cKTX6BrBIHMzioVDxkRhxKA8ldZ1XGblAZ I+WIFPzpN8m5c62i014xVwcNgSCSw6K3xHNGn3z34ysQUkVQLNP1iuOTKFwP2Iva tuXPAE5SJ7YO7GkNjH/WBGABP6F9iO/0FoSMyuuo0KRuU1zxwvYv9g2xV5pQkT5m rT1k+JM06/xljfmwKaeGZvMuXw6N3Hn8dvTtcuW3QgwxHwGP9izOWc1fYODH =NHKr -END PGP SIGNATURE-
Accepted s3ql 2.26+dfsg-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 Apr 2018 20:05:17 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.26+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (2.26+dfsg-4) unstable; urgency=medium . * Disable http + https proxy in tests (previously only the http_proxy environment variable has unset). Checksums-Sha1: e14940c1c791740694ad5c99104a74cdc04cd578 2894 s3ql_2.26+dfsg-4.dsc 11bd9da00ee087b6eb8899bf5ed70abc436ad479 13560 s3ql_2.26+dfsg-4.debian.tar.xz Checksums-Sha256: 10c03aae7014aef02ba9c839dc0b0e179056a000ac1d9e770f8227bfec50b3a7 2894 s3ql_2.26+dfsg-4.dsc 0dfd7b0ffc9217307d220cfb5f8915c51e65e4fdb52b6cc4edc53570d351cdb1 13560 s3ql_2.26+dfsg-4.debian.tar.xz Files: deccef102b05c8aa14a8261e8de948c2 2894 misc optional s3ql_2.26+dfsg-4.dsc 38cd7af898ecad3aa0455d47aa5c4138 13560 misc optional s3ql_2.26+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlrJFptfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfXj0P/2mLUCSUtqvk6IC1ZfqoP10MXBvFQt2Wf6X3aYiAcelHgTHE xPOox1QaK930bbq0LivO05yXF78BNTlvgP+uXJs4ZDeV/hgbRS046nUL1fpfodV6 yGjnf10K2hMWz+TCUxkScQls4mRQxZyPFIWHqEZVNb7EPTEL5VwOjiDAKqBh1bP7 ahuv1HzNliACWtn4A2Gf/HtM7aa2pqV4jNANu036j3+A2pp4rbXTpOfdGYKvKAov rBT1mmGmzhGQMQfaZrwYbaLCAbbLnt/z2snT2LE2tmhfyQJWUWe7hQboIaHE9ctE VDKNi5RD+NOWuNLyTzpjq/JmzbvtYAUSvw1Gq/d5JpKUMfCvAUjj6MOvjzAJwyXu zDfp4fJ1nu38orUDmiNycRpx+cVeiuEH9CY842trx4nPTsaUezUIA7vwQ+fSA3Cj NqFM2tf4wqVAOgy8efjkv5mx0N0fRGhxNNP9NGfNjS096cD626zbQYPyjx+gaBW1 b2cRk78tbFhF5axsoQ6dqaGwa3yqUY02+FZn50ZJIC2rzufIazkZ090rBThVngjz JWSRNqraAv/b267RQHEqnwwj6JMkbI4yRx9rcxtNLHj5+mg6Udx+p77E0mwpYpQ9 TAdlRUW/GE7B38+L018Yy7dKFF3ywGoEUwj5g9CaQXw9naOLZM0CKA0N2HlS =NUi0 -END PGP SIGNATURE-
Accepted s3ql 2.26+dfsg-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Apr 2018 14:55:21 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.26+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (2.26+dfsg-3) unstable; urgency=medium . * Disable proxy in integration tests. Checksums-Sha1: 9f3179510daa736cdcfe690a0a490fe76de1a2a0 2894 s3ql_2.26+dfsg-3.dsc 5b77b8d7ed6f7bd9d90f6f81b825b4b8b6917fd3 13516 s3ql_2.26+dfsg-3.debian.tar.xz Checksums-Sha256: 52d65befd79cd53e41296ea13ced02d27439b03aa970112cbfa6dfacadc87049 2894 s3ql_2.26+dfsg-3.dsc 172434600ce3597b75972f397137f4de69e6652d082ea31907c93306058784e9 13516 s3ql_2.26+dfsg-3.debian.tar.xz Files: f0cd13498601c90ab01f2f03ffdce4e9 2894 misc optional s3ql_2.26+dfsg-3.dsc c935b1399d047b95dc0cbd11aec40a32 13516 misc optional s3ql_2.26+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlrE2WxfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfPaEP/j4X0ZXroimDsIZHtHnDWSjRCu1Vd/XI7RI+/2LfwN2tpBju jxIyvb5o3NgrBftYHqbTeGeCfaic8f/X8VBdONXYxv3OlPDAv0+aTat+d9tkfQlP hsLnrGRS0U4SzKsiSeRQiCcInhTAZ/E4JZCUkNb08tcZmp65tGHgULBxqiuLgM9b +NH3ypJt7r72z7kM6HW098PIMdiL3Cqecq+6gyhe/7l8+mZ02raEJtT06bI0R+Dw gyoohf9aeqLAMdjAIT8d4hbVBZuMXK8SgphKnut1EHea6/7nay7NWxKhhqsX/qK5 oBLnZC30Q2bXh9TA7IJbn9IuH8oXbdG+8EzT8xR5Ivmqkrxcc6Zl6mdknL919EQl BEiCOCfCPjr1YjeSdlSpcpKX+7oeStq2p92BTHAAiJW9uskXv9QYQlE4MTpD/qxR CA8tlZLqiC0QFR8oSKEVu9auT2iM4Fv7F148Ckd5qgebkD22u3LsoH0PoKfqC1Tk iE9fCmuobw9LPb3lqAY7u8LUJmvaYprrjMyy53J+csXhrwPSYyNbLxWo3S5q6ViO hzUiSI2X3QL8cc4Nj8WpXwqaeViRej/g9k/86CsMZZOrpjt5iA2Hg2qissu8Isdm Q3NJBmy3eW81fBd/KBoHsGWkyWGKQ5FgNh+FmTTuWVSFgZ0yAsy9Xt+v/IUY =itsd -END PGP SIGNATURE-
Accepted s3ql 2.26+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Apr 2018 09:51:16 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.26+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Closes: 894717 Changes: s3ql (2.26+dfsg-2) unstable; urgency=medium . * Drop pytest-catchlog dependency in favor of pytest >= 3.3. Closes: #894717. Checksums-Sha1: 8e08c13b829fbd140455046d96228cdeac8ff46e 2894 s3ql_2.26+dfsg-2.dsc a8e3498accc1c21b63565d7102d58126cffe7464 13368 s3ql_2.26+dfsg-2.debian.tar.xz Checksums-Sha256: e16107779a6131e4f619a5f3e6a7f2b2e347ab5cdc0aba7307897fb6b1cb62a0 2894 s3ql_2.26+dfsg-2.dsc d3928b8dbfcc4139a85534c474767c0a4f36db1ae23a7b50966df531385c785f 13368 s3ql_2.26+dfsg-2.debian.tar.xz Files: 28e108aa01b58eaff21181cb7cdadf02 2894 misc optional s3ql_2.26+dfsg-2.dsc 940d98f7c70d6214d47e76e347aa63d7 13368 misc optional s3ql_2.26+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlrEkiNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfGXUQAMg2h9VfrmpKXOYGl/tfVB3zsj3ZPpCXrGKaFa90NbYHEHfo /0p0QfefRE/IVhu26iooiYYST9d39rvjkBkes0ZQ0h83azkGYALA+woN3zjq4rWv v5Qku4x7l+GBqDUPqAFlAuEjJliUWamAy8UtXO1RG922aMEOnL7fFwQsPbD+Gllz MVCr6O/TtIht71dhrGxrv7IvshEg69t4sfV1rDhcso892xjkqfa9dc73g0LsuZxX 1BkMxeVzP0B04ipiKw0YVjxfSLrNpy+fAfgv4MJoE2vkjKMvl9f8G3w0Yg6DrMRg R1OcRxzG/U5GVtbHRxr/nXzQXEPSeCpgBqt7KuXDtP0yf2GARcBgRbIrGTbr1ObR 84f1zF30xPX11Tub7Ddvok1xqrY4scO5lMBtRsiSd/ClcdxOEUg4Hn49tlYZlp/P AqNmU9v8+l7b5Izp0Hci4DthI70y2zUpXZHFLT13byduIuJvYSMnFvHVoIpolnQD wTHYgVP0ou9P5uw+63dstyVyeFGLohgiJxWhPCQEoVj3RSGnCNE3VTfXU8d2udDH WV+XZ3qSg6gkoW+V0rUgoKb2WIOJlJAvzQSR4gjmv9Cw4zJcmzu0Eewc/B7RIOmT mT7Qvmmx1rsR30+uwWeKhypcN4Z2IahKP9OtflIuJcmrATFCP6KGS1CZ1FNl =Zft4 -END PGP SIGNATURE-
Accepted python-llfuse 1.3.3+dfsg-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Apr 2018 09:47:38 +0100 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3.3+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Closes: 894716 Changes: python-llfuse (1.3.3+dfsg-3) unstable; urgency=medium . * Get rid of python-catchlog dependency for integration tests as well. Closes: #894716. * Disable proxy in integration tests. Checksums-Sha1: 9fa82f666d5c58e70b87e564623b2ad5612dc70a 3049 python-llfuse_1.3.3+dfsg-3.dsc 948dd5c056d08c6a57abb90fbb10cfbd7e07bc15 140112 python-llfuse_1.3.3+dfsg-3.debian.tar.xz Checksums-Sha256: 9d68fb8e30dc6a32c656102dcdf42a265fe5bb9b057f9708450dd4da3992ab6c 3049 python-llfuse_1.3.3+dfsg-3.dsc 81c6eacd16e5c7b36be501bf5ee97b06ffc45e7bbd87f60032956dcfd4400739 140112 python-llfuse_1.3.3+dfsg-3.debian.tar.xz Files: 35cf1d75a68f0473e96c9a0c6e1de619 3049 python optional python-llfuse_1.3.3+dfsg-3.dsc b169b83f5b2066034195ac1881db6541 140112 python optional python-llfuse_1.3.3+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlrEkV1fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfbLcQAMiH/fprxX2GlIbeWUnCV+nR/iLtJrw14qF69KBEzyQaBNDP r4LId/OLuiP7aKLjS3rLJS7QogBd3MpZ7OzzSprRAM0qnqkM80b/Pfqz8ei5ZVcd xwbVmu+uIdizbxWa+KKSAtFC24EUrQZJJZ3W7u5IS1PZPVQH2CmG1Sjah07+I7jP vzJQs1bIlDcGS0lbAuvQcC2cJ6PTo/wBGrdZdYKiHdRiAIW0JLHPGoqj3jRwyFyT K1L2Cnk6UiP77FAOpBbdzaNgBBe8qKJ8XL9cIYSQuI/KXG+6OjBpZfYdOu0mS/Xh UtDWg9Br+PV/dzrfhZOLW96raEqWPItzMZxLuexDii/e6wVyOkaxTNmPbSJnAl0X bDybRHaXrLquX6OlCk2NCCkRik+r43feyTayeACzLcSA8KTebGHGtC+FY0hqQnbc 1O/WP6bjlSO21JVo9WuokUSWcLnO+MkK8DjrOSPbRHZJMDMfaNWzM2aXyQ5VNDbf KVEJ5qvpozMBhDio8FcoV8FYf1cMGck2fwgYr7pzvUMfftVXIsdzXUTm/fpqngSI YWWUqV1ZT0zaikg5YQ6nBPw5K0Zm6ytCKbUvDV3cD3tVLlXLcib4pM9s9s8lUwqs JjYz0Azd9x3ciPWVLKhtzK2Sl/Vk139IHMlaNnd+qiHUPpjcRewBjmVsif8l =g8gE -END PGP SIGNATURE-
Accepted python-dugong 3.7.2+dfsg-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Apr 2018 10:05:59 +0100 Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-dugong-doc - HTTP 1.1 client module for Python (documentation) python3-dugong - HTTP 1.1 client module for Python Closes: 894714 Changes: python-dugong (3.7.2+dfsg-3) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field . python-dugong (3.7.2+dfsg-2) unstable; urgency=medium . * Drop pytest-catchlog dependency in favor of pytest >= 3.3. Closes: #894714. Checksums-Sha1: 9b7ebee79cd6abf63b7d572d37aacfeb051522be 2586 python-dugong_3.7.2+dfsg-3.dsc c2f8ed27b5c54c63c0c7036dbef874a8e265d5bb 133860 python-dugong_3.7.2+dfsg-3.debian.tar.xz Checksums-Sha256: 41b8d1a1d27d174be640b07ab2d14a4a990c7294f7f70b9a0c916f97da1f28c8 2586 python-dugong_3.7.2+dfsg-3.dsc 11da4d67193dd946d3fb7fe70e9ddd706eca37acd13b9bfa7fc3eebb526e596d 133860 python-dugong_3.7.2+dfsg-3.debian.tar.xz Files: 825321cf487780ce7a2c8e06ff75bd48 2586 python optional python-dugong_3.7.2+dfsg-3.dsc 88fc2d418d1039eb749fe313d782135e 133860 python optional python-dugong_3.7.2+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlrElZNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmffgoP/0s6gEniZCtrwntH/Uv/AnrKC5fhUEmLB9uaAgpAG0swoq34 Mb7yiGZphNfgDKT780WWJHhXjyX8d0CUtAa7FPAL/Yb6nLt7ZiuuePD+sug55ASG tCQBOL8VB75FQ0CSKW9r3AKYx8X18j9d999jSkfIqphNfiykUF/B3Y+dCpwDtqGV geRzMpa4wWKbQsjmiiRGEBX7H/EHJEbde2FZSAft+YINhFLfZRkvgz3dEkhB7aBZ ya9LXQOUf4+87C2M1eKkKGLgJoOKVZ/Sc6nLviQbHw/fbQpB6TRbET+5ZmzP5UeO uXko7lxs1tI/R9u6eP7tWzS286opIUN8sj/25Ct5gfJvjg9oCYZxjqFk/lYk4d9Y /YismlM5DQ+zqiRC047iKzCyQ+doG1wZp8tiUa+AJgvgpys66kp+0l2ns5292gj6 wG9dtC3A6McCyadxElV+sA2vMywXC0TJLasgfqrZR5XF5eQr9nIAgHmI0AXwFT4N IVZNvyCdmTlz9Q4ID98GRbOOSOWCUBbVuz+fd35cM947L2skgOZ0nvldV7ZVw7L7 IJl2Dn4++AqrDG0hc1YtlUTIbRrMwOOxcEQH+xyqLic1dSjQKIB9VcBGXyXp1ni5 dqySbmO4jKpTua32Y9xC8JZGAGaN5MmXrS1DH5KbAA/6z7L7pqio+Axsowlf =mcvr -END PGP SIGNATURE-
Accepted python-dugong 3.7.2+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Apr 2018 09:53:12 +0100 Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-dugong-doc - HTTP 1.1 client module for Python (documentation) python3-dugong - HTTP 1.1 client module for Python Closes: 894714 Changes: python-dugong (3.7.2+dfsg-2) unstable; urgency=medium . * Drop pytest-catchlog dependency in favor of pytest >= 3.3. Closes: #894714. Checksums-Sha1: dcba603fb047b5a04b4fd8218131ccd3ecbeb9a7 2611 python-dugong_3.7.2+dfsg-2.dsc b9640e60fe6ef0230f50b300dd4631821fa83530 133796 python-dugong_3.7.2+dfsg-2.debian.tar.xz Checksums-Sha256: 04c342894e2cd19138049da98945728cf6a6fb68895f8b425960ab102c67d3b0 2611 python-dugong_3.7.2+dfsg-2.dsc eb08d19dc5c7ca02e3a5d7809bb531f869473e47c82608d0496d2dfbceb28008 133796 python-dugong_3.7.2+dfsg-2.debian.tar.xz Files: 2a526f715beaf63d3db883a53ab216f0 2611 python optional python-dugong_3.7.2+dfsg-2.dsc e6907f364203ac073b908e361c98ce1c 133796 python optional python-dugong_3.7.2+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlrEkptfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfLJgQAIMLinqS8Iuw9OH7KNUPkdPuBdp+R8p5Uvgu8SG5ZlZooVqx HwDni7Uwq4+jVb3IkzhgJB4xwdt/xHsPW+t7gxtgD6Px2sHs9wuS+Pfwe/erC+pV VfFBQBqAd+Njl2y2V9qokz/bKzpkJ4rPRUqSvdbl5K0m0YS0qCf+1cahyubGYwgs K+Al3paDuN0DbifK9NaRptGLC7973Uiup+6xDI0LBxHRGjySEX/xSmBuZjeNaA/M JrZPoQpU4MNb62Pedvd4Y5ksnGvoBePHhlrhN07Ti3IlZy8Cg//0VYXoZVV8t1NW 8mN8ie8EcVyWpL7vTBZxXqxvwyva/HsfdzDTZlyrKlznCtaNj8V2YZGjbE0MIvSS lIkhgVa+MFzDStnIwoemDtdSlZZMzgjdQHwIH0C5Z8QyyQnl8wN1Fkf6KWAkeNyV 1thuKUDXSUeRgrBFEzIKvca9uaiqM/NXPh1jlgaZOpHhsBOfCO5OZml0cEaLaCMq 3OD4NQFt/1HCzpOo+PUY98Yzn+yW1rdbkJ1EihYQzOzAoU5aKWWypPtKI9UwKdrA /YfyxVYWxrWlqEKsYcNRkTSNfhayycG14WH92a8xTcQFgIsKW8E0pcuJdE7A+u0E aKp38Rg1Zx7uvPwTntkSwh9Shb/Y+4zbEHYHzQpT7p9GU49C6D2NQzK0OajZ =hwjD -END PGP SIGNATURE-
Accepted python-llfuse 1.3.3+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 03 Apr 2018 21:19:02 +0100 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3.3+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Closes: 894716 Changes: python-llfuse (1.3.3+dfsg-2) unstable; urgency=medium . * Fully drop pytest-catchlog dependency (previous upload only dropped dependency for Python 3 by accident). Closes: #894716. Checksums-Sha1: 15426edd3b055493c6f78da12e6c94812c2bb12c 3098 python-llfuse_1.3.3+dfsg-2.dsc 96f98dd3f6b9f1b6554b955c7d07190ad88964c2 139936 python-llfuse_1.3.3+dfsg-2.debian.tar.xz Checksums-Sha256: d2de51ccc019ff7fc504c2b5f08f5580312af8eee051b79807357f9780103b26 3098 python-llfuse_1.3.3+dfsg-2.dsc 3f55d6fd9bc1f0981ba38b18849cd2bf371645ba5a0f33b71453365487af5483 139936 python-llfuse_1.3.3+dfsg-2.debian.tar.xz Files: 83b13c59c882ae8c02f64d8dc8527023 3098 python optional python-llfuse_1.3.3+dfsg-2.dsc cea44f05fccc5faa9e2f000bb7bb1652 139936 python optional python-llfuse_1.3.3+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlrD4fJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfbLoQAM6UTJ8A9zZQmrJYFhf8BRIcW9WAsR1ZnoRnLjRr3szcUQvL +WfBS4cA0hkX3M6gy4Irs8lTWtzq8VK4uS/VFw+FepYZwdKppj77sbuwquHXm0+3 q7kQPg1JT8x31mBmx56VNtKbU3mXDCghJ3yIqTtuG5/bnP8asa4Tk/GQaXfb+LXL MjDgrlm1PQ47KmGH0f7ej4nM16kP3gMhrAS5utzFJ3K6sXDGEWUCuCSVMdOczy0S N2ol1QzFmulizBH5F9yZunTJTaXjwqbjGkZOsF7pcTkJCm7IMOn0EBI8UmoMQ2ll 7PAKwRLmj6UDe+CbdDR0SVkbn7/35kOJ5f7skRPET+qMaAs7/BLBL+0JwxirxegE qKUYJVV1/gN79le4r25jcf6sbjuAe1POvL8I137QkYkLGlZWGumNBzdPHWNdvTaO 1miZ3Djhz+bxIaDoE63GVT5dlDsBe6oy5t+4+X8Qxg8VkYVJtNmXFc5OnUKUNXH3 bmIhY5UrAxB5PnNN6+BxEuS5eRhUtKunL2K9bJmQSJf79w8HCtQDOsjkul8Cv7DQ kQAMUOovIm8TXSdQ5Kkn9ysNW1TrJu11i5WqsU9biR5deSTV5NTLdzRU/bLthFMB QFkfpOnlR/bjm4nNI/+phX9u5xZucOgCm6sRFBllT/x36NC+Xbf8gA1VnhVZ =rH6P -END PGP SIGNATURE-
Accepted python-llfuse 1.3.3+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 31 Mar 2018 12:51:40 +0100 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Closes: 892616 Changes: python-llfuse (1.3.3+dfsg-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field * d/control: Deprecating priority extra as per policy 4.0.1 * d/changelog: Remove trailing whitespaces * d/control: Remove trailing whitespaces . [ Nikolaus Rath ] * New upstream release. * Dropped pytest-catchlog dependency, depend on py.test 3.3 instead. Closes: #892616. Checksums-Sha1: 7fef427495428a56ca4035112efc962b10b3a822 3122 python-llfuse_1.3.3+dfsg-1.dsc 4dff46935080614ff607c647038c79e3c47fe74d 277442 python-llfuse_1.3.3+dfsg.orig.tar.gz 6c3fa3936aec1c545e53259eec2042976ab03424 139860 python-llfuse_1.3.3+dfsg-1.debian.tar.xz Checksums-Sha256: 424eb5e1a9ec4fec8fd9d8e39a6e5184275afafdd8cb775f300c355c0c69e36d 3122 python-llfuse_1.3.3+dfsg-1.dsc 0e2ddc562f7d90977739d0165394cdab57f1f882e1f1331e48a16368e63c72b0 277442 python-llfuse_1.3.3+dfsg.orig.tar.gz 638c8c655ca7c9fcc17baa59397bce47359082e9ce4f572fc42359062cdab671 139860 python-llfuse_1.3.3+dfsg-1.debian.tar.xz Files: 46f7940543b457b32a0fdd5713335190 3122 python optional python-llfuse_1.3.3+dfsg-1.dsc 693da4fa91efaf56ca5164b940ba5fe5 277442 python optional python-llfuse_1.3.3+dfsg.orig.tar.gz fe501a7588bf774df1ddff02e623708d 139860 python optional python-llfuse_1.3.3+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlq/dnBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfzZgQAJHKPRKEjRG2GkiWV6/dplJEoeFF2X4M3+k3Ud6NhehxEFrq w4E7+XKBuGyi7rrdtHDgWVGz0suz1NfQdN5n3aKPILwFwSwwmU+BHF/OLltx8LvO 74gros412sQPLEbegrE1+uejusQtDLLEVTZJhTctyUa/fj7dtcrcWf3Z3qPXraQC Yit4KSyYwq1HQO+PZboi75EmN6ikU4e5aI6euwpqlFAU6NtuJV6HQDxfQPm7fkE6 37qSouvosZqZKKBsFM2hn6di0v5raBDO2Zv9UTzYcfoSwvzUhEQJ1CBsR9BpN+wM Q/hgdUHxmQx4N06DGBU++8V2HpXMcSFtbrV+tJE/XEuHGvsksA2jNUCXy8uu4oji j8G3+JyTTSgwK4An9Wb8oNqAU5KGD54xcwhEgIX7Sj2Dwr+Z21bjEc/zkKleQFzW l94/o+T5doZsctBFN/oQPLgtFAJmWdKicF04xOcermxL6LH04ZPv3fw2D2lVdstg UrOrnb77P+SPGdjWf83liouDD9mrDxDTl/UtYyaQ0oQYmXmJ8SUb/o3XIF/vbqOg HUD7kZ+KIJgH2v58F2y9V5+U/4So4TaYAuyqApbxl+7K+mFigsScrOa7q2ZiJuHB kxtOioz4iXpFBhPrHzrahk6itge+GovGeUQKfIG25wnhC44Umr+TwKecKgy2 =ihb1 -END PGP SIGNATURE-
Re: New lintian warning: vcs-deprecated-in-debian-infrastructure
On Mar 23 2018, Ben Finneywrote: >> You need online access to make use of the above information in any >> way. >> >> 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. Are that practical concerns or theoretical objections to the generality of the statement? You can still compose the email message, you'll just add the recipient address later once you have internet. Yeah, you can't bookmark the URL - but why would you? Just "bookmark" the name of the package, and once you have internet access use the (pre-existing) bookmark to the site that will give you a link to the upstream homepage. >> etc. > > So, there are plenty of uses for information that do not require > internet access *at the time of using* the information. Does "plenty" refer to the two examples you gave? Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted s3ql 2.26+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Mar 2018 11:39:35 + Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.26+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Closes: 887375 Changes: s3ql (2.26+dfsg-1) unstable; urgency=medium . * Added Depends: procps. Closes: #887375. * New upstream version. Checksums-Sha1: 2a23b5ad76ff6b72542bb9155c393a911f7c1e43 2944 s3ql_2.26+dfsg-1.dsc d72c164f0ff3017b7dc96951b423d307f5c62a88 680665 s3ql_2.26+dfsg.orig.tar.gz b5aefb5bf8c87b3faae0a1011c08f73a03b4e394 13316 s3ql_2.26+dfsg-1.debian.tar.xz Checksums-Sha256: a0b5451fa44db71cbbdeff7bed162ecbf9208e97b15cffc669587671bbe54190 2944 s3ql_2.26+dfsg-1.dsc 9b4f67af524f6167f46bd9779dcb1dc9f3648c6bbfd712e5ad87fdd413fce13d 680665 s3ql_2.26+dfsg.orig.tar.gz 0515fffcb845ffe05ea0f3521c6c979638de2ec14e827ad557efcf6d8750c961 13316 s3ql_2.26+dfsg-1.debian.tar.xz Files: 1bb1886d802f5ff11787199ebba8045a 2944 misc optional s3ql_2.26+dfsg-1.dsc a2e8f4f064f95f8845bbd582754a0a21 680665 misc optional s3ql_2.26+dfsg.orig.tar.gz add377a5885a1b1d7e2320e6b759cf32 13316 misc optional s3ql_2.26+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlqb3H9fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfNwwQAK0i9/V2fn0tV2W+3m+tBO1BXo7MrwjgWdTX7NDwd9dxy6m9 Z743nRISSyy5XravH6/dRo3ZuMqwsqt2GX0HIsR2gxYtaYDdKL1RWW1dGZzlK5pw Z/JImKcbukJMwbXybXQkL34weXIFf6dxf1SWsxY2oNdYiqPrVsSO2b0IBrUBLKx+ XpdFCtCJgw9RXo2JfqAkWtGNJ5v6ZbRreozQ5q+FtAQpBJaf7dFMl5AluR1Q+cb1 mlhvtGZrKqsD/x/hRiVd7rkhl/G17W/QK2vg0iwax7qgiEJGltsaoWc3xgqIktmn t/hgftrQZvhyu+Mq306WlRqLZIp4lNO+GGgcXmsTYoWgb7/CqtO5cvYtMVnE7U0v ekU0MJz2UNyQEd66XljMimYqGn40JJWasGAr+UaUrv2I5V3AvITzWpsFp1wQSvc3 keJF0jDJ6E7q/evyFk1Rdi38sAgXpweNoXMiIZMCC+adJX0MQVwms0N61J6wiVUK NTzAIqbWqaHv4yUTASYyEU3TA/sb4BTWwSo9tA1JUjTL8P1kgZtxqzb7FBpAAWSq GRxMjL7WRvC4FIab1gaqvkF8LCrRhdiPcRIyp8CnQYichgiXokEp8mqCUsQDOGMG +UhB+DOrMFg9p52Fi+xpycmUjVFcP9ImF71XfEIwXatQxt/sbT/7WY/oKSqk =TeYW -END PGP SIGNATURE-
Accepted python-dugong 3.7.2+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 11 Feb 2018 16:09:49 + Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-dugong-doc - HTTP 1.1 client module for Python (documentation) python3-dugong - HTTP 1.1 client module for Python Changes: python-dugong (3.7.2+dfsg-1) unstable; urgency=medium . * python-dugong-doc is now Multi-Arch: foreign. * New upstream version. Checksums-Sha1: a2aa3af3c089c281ebcdea2145a048a98e0e4f9a 2661 python-dugong_3.7.2+dfsg-1.dsc a043171414ad939c75ed0ae6f3d8526d66cc4af8 51260 python-dugong_3.7.2+dfsg.orig.tar.bz2 41981c341ceb466f4ebe67db1dbd2a3f7422d4a1 133740 python-dugong_3.7.2+dfsg-1.debian.tar.xz Checksums-Sha256: 323ddfed844ec52f934f009e63390f7063a5766c2b944cbe8a800b86ecdbae72 2661 python-dugong_3.7.2+dfsg-1.dsc f6fe289ef415d734ae713d013c698806fa473b3a928835aee016f82ed367eda2 51260 python-dugong_3.7.2+dfsg.orig.tar.bz2 59c0631553a0b3581bc58eccb9f1a6875d54c2e63ff52303330d2a2b25e0fa56 133740 python-dugong_3.7.2+dfsg-1.debian.tar.xz Files: 150f518bd26d59d8e98520a152383795 2661 python optional python-dugong_3.7.2+dfsg-1.dsc c3927c575945c38ed7c6ebf9f84e066b 51260 python optional python-dugong_3.7.2+dfsg.orig.tar.bz2 16bcc3a59a421a837a109fc8e82c2774 133740 python optional python-dugong_3.7.2+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlqAbR1fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfAgIP/RJssrIQtohfXA9Gi3ch/+Sx1IR9eM843I7RSaRZcW7+UY37 65tseCynWMrMXIkEtR6CKNx5dGV/UkYZPPpWfHbxfYO2W3enK03PV2cTZ+kYzEIv TSIqKJ6lP+xcy/h+UfJgN5g/LwESAfS7P/NEsADv48W90ceF4eYMBEM+wpynP8Bz MmBDdi41GOxfnfTHpKSjCKZNnYt9bghohyEfd9q5ktYhLtZBhEzn4n+yabao+WU6 +zgamUDb5JPCoeuySkLqaXimnbjqNhq8fcz+Cq/rYWYhCaA61YYIuK8qVk2N7bBC p5IBuJv5WsvIuuzuuw7nvaYoRg/E1tcPM4wyYqUqgRC0C/E77TpO8xli0/YSxHV4 CRmC3QuvzQUuX5i2bSUryPsdvg1n46FEJkXs34NG9An2e5s+pju0DVsGn0A5DkDn x6cFuhRSqYCT618yCOahF1njLi+Tzu9ZoqVXdozet892lY6cl01QMumpUDZnoHnc H9ocl12lxwqRML9eUfHefnk2tWj07h6UjPD4q7MBp7ZTeOxAG1c5KUe9kAZ/luSU i6bXVmiaaHr00D4Iww9orIIvWyF83Mo54qL/F6HDpZdszxYPLP7WdqSZ19VE3eKU Zeon8itVWM396pJ9JJtzdZ2NpE7H0a0wJxvxGxitsCvR7lEh6iTo5QSuOXX4 =txg1 -END PGP SIGNATURE-
Effect of build profiles
On Jan 11 2018, Johannes Schauerwrote: > We can check whether two binary packages built with a different set of > build profiles active are actually the same by using the tools from > the reproducible builds project. Now I'm mightily confused. What's the point of build profiles if they result in identical binary packages? It seems to me in that case we could just always use the "simplest" build profile. I guess with "the same" you must mean something other than "bitwise identical" - but it's not clear to me what. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted s3ql 2.25+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jan 2018 12:05:16 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.25+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (2.25+dfsg-1) unstable; urgency=medium . * New upstream version Checksums-Sha1: fcec261551ad98273d6b0eda3b5a089f5e6591d8 2944 s3ql_2.25+dfsg-1.dsc 8411d9e75bb9de898a0a186304544e353aec9f89 678044 s3ql_2.25+dfsg.orig.tar.gz 984b99b079d3198d7428b4c4448a0ab028df975b 13252 s3ql_2.25+dfsg-1.debian.tar.xz Checksums-Sha256: 004cef69d4a699bec23aebd4c91f63bb43b30543d3e4fd9a15532563b6032b6f 2944 s3ql_2.25+dfsg-1.dsc f3551a2e17e5610f8ecc9835139b33022063a46e2e908b458042e5ca3ac24483 678044 s3ql_2.25+dfsg.orig.tar.gz aeca7176f10d8b6a5ac4f200acd4828a09da13d834ff8d9b6d41aa2a68e3aeb3 13252 s3ql_2.25+dfsg-1.debian.tar.xz Files: 9e48c1729c7e5b2f7f5ab976c222f851 2944 misc optional s3ql_2.25+dfsg-1.dsc 0bec0260418951e394432588267b3b54 678044 misc optional s3ql_2.25+dfsg.orig.tar.gz a0eb7fcd28579934f7bcc1ace8380084 13252 misc optional s3ql_2.25+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlpPYahfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfNn0P/0/r09GObV4aOIJ0UyXO1rGQuoDZoILtVQ6BfPjPf4F+GVq2 kvreeZd3jC/Nf6EnsYm1PSqSQdqY4pjdGAHr0J6mgmYrI+4hi9BVnQPlVkz/GbDU GwBgEhxJsM9g1nATMPmElpgVhrK97ZExv8ulNFUxM0j9iyVCaO2A5pCa797xepeF 9o9lccLVBWaVEWClNyN2cXQ5Q2nbtFVa3zu9tI9glTe0aagPEPxKJBxn9v88ID06 n9a10OF4GftjAcfeK9yb04i32/FiYl7NBqxma9SEipKOtbm2iDSdTutJ+upNeiXZ AsKUAYl1mnYZM4O4WCXrsFyVI+8ilVe7WBIHT1nYs6P4amGw0dUx3x7n6rnTtRoW KOMUPtzkSRyXerx1ZCeqgSk2zPLj810QxdgUaPmN8/V9XE2jWNJPyZ74UaNQzkBB 2vJ+jcxZCpjDk55RA465bNq0BQgP8qKP01r85i1sFN8Cm0RKh0a+5F1jFbOhCE4o T2hwXxa5cUFSiWDeqpwfjQ6rHwXz9kdutnCA+D6lr3cXhJmVsr4inNyDteF113ZJ PO2Hs5cTYtV+UiF+1FT3OINrc+C482FSm+yshlQDQf5GXLmENk4yZXaAzkOoCDd0 1zYpZjOYNBW+H7bZtsu8CY2ISaqauipfDJw6I4Kzf6Rwak9oUreiN2bj6Vpp =pX08 -END PGP SIGNATURE-
Accepted python-llfuse 1.3.2+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 13 Nov 2017 14:03:03 + Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Changes: python-llfuse (1.3.2+dfsg-2) unstable; urgency=medium . * Fixed up patches/mips_dev_t.diff (missing file) Checksums-Sha1: 0ee2ff3c89e144f5fa7e95bb5fb441465dd78e20 3166 python-llfuse_1.3.2+dfsg-2.dsc 65732b7a0cdcf401bb5b2beca3bba6e3a0a799d2 139728 python-llfuse_1.3.2+dfsg-2.debian.tar.xz Checksums-Sha256: 73ee3cfdd8d7d3f18dad457ddad41e4bc1bff92a00e86be7cd16fd98e971b56a 3166 python-llfuse_1.3.2+dfsg-2.dsc 6f78bf1aafdc947d90c46cef96f94afd11aba634b404ac2ef3c40353eeb6d789 139728 python-llfuse_1.3.2+dfsg-2.debian.tar.xz Files: a5d8e13b6af040241b3ba48f976f9dac 3166 python optional python-llfuse_1.3.2+dfsg-2.dsc b0efd6441c699e3e05140e429d04dd7e 139728 python optional python-llfuse_1.3.2+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAloJqrdfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfHcQP/032MeJE6sVf336rv35aXV4XwavsrVP2w+5d8/hFSfV1Wvc5 ZUE8T6xGUmea53prAFIDe+olXOQbit1esP3lmcED4VhQRuyBRWy0bueR+qMN0EPG h2vXSl6cRclTu7Z3ZqQMYIoxay8Lv7O00WDalzJUMf5ZVo5xpZ5LlaBNiTAyOaUG v2d0gYsO61N/fNTqobMY/zPYG4Gign55KjKGQTkGUC25SvLbbDri6G8smfd0qH85 dLbdqT5wb5+xoeMoRimardp1TfsfqjNtHKvurZWGKqLsat8dWuatwhi2qTelvhSs GyA0sq0rdxg0yNvnz3yfV/bX+uchY8v9ccGvJyRvM0WdcuzfrG6jFBMOesGpmZMM GeUWc6kzAWUd1cDtWdKNY42BZys3Fr275tTqbM3uWKbhiKYTHBdsEcnU+mxWnyEk xuCgZBhR+91Sr6zsVBsBbDJgJ0YVPHowY7M69IINoZnxpuhpRVynjQuLK90o++ON K4fghTT8vx3V/GZiuBw4vaf8IP3ag7GpRweU/yNuFUrH6BeOnQAz+L089tOykI9m 4Ek8j+2+6r1H3si31gdPK8g+7WwhXaFfGoXE3Ndm8yAKcAQYNtPFV4UrARMGjTfQ hOBuBJlkMa5idFhrx59LKrC/ZgFpyVUKtB7kADT1MzVLeu5Sl8MMh7S5m53m =6Qer -END PGP SIGNATURE-
Accepted python-llfuse 1.3.2+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 13 Nov 2017 12:51:16 + Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Closes: 877500 Changes: python-llfuse (1.3.2+dfsg-1) unstable; urgency=medium . * New upstream version. * Don't apply dev_t fix to mips64 (just mips and mipsel). Closes: #877500 Checksums-Sha1: 36e23aa75e3fb3b91c3f4bf6db3ac684ff9bf34d 3166 python-llfuse_1.3.2+dfsg-1.dsc 671f1fbd7195ec5989fa24112e93d5ec0774ef2e 276475 python-llfuse_1.3.2+dfsg.orig.tar.gz e9dfc57c0bf4852a9b2952177525ec33a884b8ce 139416 python-llfuse_1.3.2+dfsg-1.debian.tar.xz Checksums-Sha256: de26f492218ef3d306311cd7f4267ab27f964384bee5bfee0f1d730a78136ff9 3166 python-llfuse_1.3.2+dfsg-1.dsc 01eef1bff51563399b6de9390fe092b8bf283f21133658d6bc3b918a6ef3c956 276475 python-llfuse_1.3.2+dfsg.orig.tar.gz 73283c1bd5a51f037dba147063f6062ff557c192919bb75efe6d1102461480b4 139416 python-llfuse_1.3.2+dfsg-1.debian.tar.xz Files: 57007d173d9b40adabc7d433651f7c54 3166 python optional python-llfuse_1.3.2+dfsg-1.dsc c19a3cb3a6199b82fc8460a700a5e303 276475 python optional python-llfuse_1.3.2+dfsg.orig.tar.gz 497a89009f111ea47fca2f1b0bc21a83 139416 python optional python-llfuse_1.3.2+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAloJlX1fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfOwAP/jWD1XkGLtwO3DGHAUFQN4ZMf0lcLQJOJ0iwKz6RvzrxlJ81 liGn/Z5mz8srydVx7GwIh9sXHDoAiQqojR08BjzF86QgS1zwScpGCWvJvQqtslzN ghzNSnWHwL2YEEN8JUl5hkPajHGtG4s7ZlkuTD9IEy2UFPWY4/ZVZK6rLJ/Zg3T2 FJbOKKqAU6YE/4ci0zrKwb1OA0ng09hPhFsXeGBa83iuMXmT3LUvWb6EWcYQBbus lz0WoNSx6PAvGDJwt1cpK8e5/UpUkEF3vGOf1EKy7fLlN/3P55MnnTXHffaZMnNj Ygiq42Q3SSykdSQ8Ex0sl6ZDbPNEzmMAH2/MBuqkAYLP2GXIgNmdNJAcoizQFcZm yKOO3vfQJ7yNrLgNFufafMtV56ttvIEZ+cEN+ARs4iQZCzFBv4Wr1aZOYWMdgVfM oC02QVgi7kVDzP9F5StZ8NtHmMIjlhaQvOgmfne/ax+QY+NCJkP4Z/MmbjQ1zJQT Y5JET06SNw4zDnK7YIeg3QIHXRBhNH+hj/gCjJGgcP3rLxrau8zQSKnoo0jyIXMS 2a1oU51RI4rANXXYmzmj+Sfu4lGpp0Njcdqz/wMfuOz0v9qNvWqGG6Z0B1tiJYGF rhdrBdCmr0PZdjuI5CuijZ8GtSVNE3R9wkuy030PF3SyGUAnGv5yVJXzBt92 =ORCV -END PGP SIGNATURE-
Accepted s3ql 2.24+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Nov 2017 14:04:39 + Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.24+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Closes: 877204 Changes: s3ql (2.24+dfsg-1) unstable; urgency=medium . * New upstream release. * Fixed bogus test failure. Closes: #877204 * Bumped standards version to 4.1.1 * Added support for 'nodoc' build option. * Marked s3ql-doc as Multi-Arch: same * Changed package section from extra to optional Checksums-Sha1: 2e0ad497056d99682081707d38741345e50e0bb9 2944 s3ql_2.24+dfsg-1.dsc f3dc898e0d0a186b12c63c1ba74450c0deb353f0 679375 s3ql_2.24+dfsg.orig.tar.gz 1d9cf1cf53c432c1864c17241931a451f93223be 14036 s3ql_2.24+dfsg-1.debian.tar.xz Checksums-Sha256: 211835b77d2100bdb559bd0d082e125bba595759f3c10b6ab3b5d8d985b06d06 2944 s3ql_2.24+dfsg-1.dsc 5007a415f08551a6b4ed184c2596f14fa204c7fbacb3c35f2dfb633591ea8725 679375 s3ql_2.24+dfsg.orig.tar.gz cc0b7e3fa0c9334247ffc0113df317b9d36497b600f3b088ddfe953a821f5d6d 14036 s3ql_2.24+dfsg-1.debian.tar.xz Files: d90879c9ccd82c5de7778e8bf1137456 2944 misc optional s3ql_2.24+dfsg-1.dsc c1f75171442087a085054b50ffdad5f6 679375 misc optional s3ql_2.24+dfsg.orig.tar.gz 4e32a44869ff403126b1e33c44d84b95 14036 misc optional s3ql_2.24+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAln9yU1fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfHhQP/3iQzaTf1wBJNtqqF6Q+PNQ6iZ+gM5RbuxupBEX/HE8Frwex LKo3LGk/sWT+1bvuMlADpZzJ1FY6y6V8If8iieG/9/5MOSjoSxNKbfnPWv8y2PO4 fQfAV59zMMRVivA1IPWNhYb5oQMNbUuR+fFYqbruUkOVP/NeigBNFxnHPHK/rUls X5A6vNxOpcMUxYEHQt30NQHlIbjVU/hZ2HhsWkk5tfUPa5E/SFCMSfPRFaDenf0Q FkxOhMR1eqn1jOUdCFVh0YPMMXK9S2ztjYkG71FMcR0KP+jzm2yIyPzVZQqGjmKZ w0OJZozv8nxM/FG+DMuyBElwsMjZOxuPuNNk8wE7QheGyVE8IN3ZqEDueJhnOZLI Ri2The/5zcuTsjJnTK9B3iq8d5VQWaGT/cH5ocBgATZDKX0eXR2t3qQUr3vZuzH5 g/UvXdj+W2UBOozX/89COw5qXN0r2iJqnphHkvVwYHZCJOZbhJ76nI1ge367A2hG GZX0JHKQcpN6axcfbvArOGbDJ5l50R+SQ79DMNJD2yFLbTxfUX1Mfzd9dFzmpTXG //BPQ9zEzYaNN8rgE/RSZ32BE6i0YqUI7hrQhdr6UiR59SUd24uNGdC7AxvvwlMH bFRwHb/y21Db40t903Vf7IbDMh6FQuQgZo6AFZzKW59iB8nuw1lXn1WE0j2l =WK0+ -END PGP SIGNATURE-
Accepted python-llfuse 1.3+dfsg-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 01 Oct 2017 15:21:45 +0100 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Changes: python-llfuse (1.3+dfsg-3) unstable; urgency=medium . * Updated standards version to 4.1.1 * Added support for 'nodoc' in DEB_BUILD_OPTIONS. * python-llfuse-doc is now Multi-Arch: foreign * Fixed mips_dev_t.diff one more time. One mips, dev_t is unsigned and we have to apply the match for mips, not just mips64. Checksums-Sha1: 0200bc895404377829f63bcbe8ceda80b79fe7f2 3150 python-llfuse_1.3+dfsg-3.dsc ccd30bce950a63c04f4557b0aa2afaa4a07f14ee 139540 python-llfuse_1.3+dfsg-3.debian.tar.xz Checksums-Sha256: b89ec1c3147613bd10d841638455ea0becdfc3ae10c0d2f882209ab51ab4f066 3150 python-llfuse_1.3+dfsg-3.dsc fb49fc9db1232904e5920863ae62803fac8c38433703d637ddedffd1c179d81b 139540 python-llfuse_1.3+dfsg-3.debian.tar.xz Files: dc8b01a6e42544c92a46367eb65c4e39 3150 python optional python-llfuse_1.3+dfsg-3.dsc ce07941f62f68c63a36973a702f24c53 139540 python optional python-llfuse_1.3+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlnQ+xFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmffygQANMdtg2VY5FpcrT4JT9n84OL+yOnDwFR9xaQlS/gjbj0p+Qc 5tBVQQPngprqT5qV49owRVTNx/aw4uEU6dc151RcS0zA49oJKIArhBRSFM9kqTv2 QonCT6z7Y3i84OTeowI6kajKBZTVtgIps8wVxLpqCK9NLHC7prqXdZ6NPIPUoxUI pRFEJDfwd31wQO+CFjBvF/NLw6c553djjUJm4HoZhZyZMf5KITvnojmGRfjW/Hpy aihDBaDXVsZ1SJC73EG0uJ4AfibXfwfvsNp7XdXh+av8jj2s1xdkMW62vDUjo37p iLfbECTUl+EArmFL/Cb9dU78iA/TOwYGyuJWI+yI/WzvutfQLFu3LCV15A+2Dd7H Z401wQQSyZHyHlNExGSXmLKa7LFLeTUyScxn0AxyyuCmGaMKz9+QdL14VSuVoYbW d+pSaHEvGKI2SQMEArDz7oz8ggqubsdIO6+KJmLHRGl+uyKEniqpGWHsWdSuwr6B Cb5ggBcPaY2r6IMmbHBSCFBNdZfPKKKeSg2tl7SwVuVLSnNyf4bT69D8fxS7lFu3 MYcow7AJ8wmwXMAM4NJaCd/2Tv6yyWLcoG+blKUSUuP90HP6+H991eT9GvYM3OhP Xks1JL70fiouTNAEygd/t60tPXgh+x+w5hSCNTJnfFvgOlcQhBO6YCk9T7Js =JoEu -END PGP SIGNATURE-
Accepted python-dugong 3.7.1+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 01 Oct 2017 13:12:07 +0100 Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-dugong-doc - HTTP 1.1 client module for Python (documentation) python3-dugong - HTTP 1.1 client module for Python Changes: python-dugong (3.7.1+dfsg-2) unstable; urgency=medium . * Updated standards version to 4.1.1 * Added support for 'nodoc' in DEB_BUILD_OPTIONS. Checksums-Sha1: bd86b4781af485a81882c77563a4258713e1ed9b 2658 python-dugong_3.7.1+dfsg-2.dsc 17bbcfba80e741583f13d10b6b752f0db16b 133716 python-dugong_3.7.1+dfsg-2.debian.tar.xz Checksums-Sha256: 4d79b3a292d22af0ab6cfdfc24ee04d722468a665dc847a60518385444bc2a97 2658 python-dugong_3.7.1+dfsg-2.dsc 766641b77193f73ed2bc9ffb6463276400cf3098dfa44e1f8b4df254c17242e0 133716 python-dugong_3.7.1+dfsg-2.debian.tar.xz Files: d00827560a562b377f254aa67cc538e1 2658 python optional python-dugong_3.7.1+dfsg-2.dsc 3ac961de090fd8f40667d5163bfddf06 133716 python optional python-dugong_3.7.1+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlnQ27ZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8TlmfSDsP/1We0/B0cJA03+q0FamsZ14dY0waw4KP39lrwVk7VIPlVoyL uZJo064e7qfBQFtKZN665eQmfTE9LAVT3tFao9eK5g/RC+dJQ3GydXcv3GHCh5gV C0Gbbi2B/LxDFZAC0h2xhgKptkVl6jkc9cvLJNCqdvXNE93ndH6eDKvaI9RLPL1S +PU0oHtU67NZRahxTSaDoJv9QQO5HPMD7HjBfjAZhccluMu0MGubwo2ymW6o9XVG 9fdD90Coo0ExwXLqtFf48aKt7r844eoUHTL2aOi00CsEa5rEzmh3hxsJ3XponalR R1JH0+LysoV66ceWT+L17Cn+noK6rSfjCndzypr4FPqpySud7TMDpdrIwNsGMJsP sLuvWb4L6Xv3AuWAIjPbWMjrBiwWEhifble2wX5TtX4hmfdu6ORFgPeCheNBSzDg BNnU6IMUsQAnTUAEIkqZ/6IgDHuBPq2JpW3uUQWAblBOECMuCeK8tR2w86tW6RLo gwLkW1uOSakK06sm8ssgz0ZZWVphklL/wIEDK0wToDhfqzGcNWLh7iLbQKamLQAi CbJ4NQFt2pRIRH+aKDG1nJ2/uc00e39sEKuNjZ9gcZOAV0ITnMPT2NeXocDQmc1H rUcxkev07Ev29B1gPBVk7Cp3p/36UFDT1r6mF5zF0LsIgfd0fMYU5K0q61b7 =8Rp1 -END PGP SIGNATURE-
Accepted python-llfuse 1.3+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Sep 2017 14:58:36 +0100 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Changes: python-llfuse (1.3+dfsg-2) unstable; urgency=medium . * Fix build for mips Checksums-Sha1: b8a8580ebb74a77e8c45d2788ed139c6c50f9a61 3150 python-llfuse_1.3+dfsg-2.dsc 8cb00b706505aafbdfa0f4adb181b1a19fdea21a 139420 python-llfuse_1.3+dfsg-2.debian.tar.xz Checksums-Sha256: 6aede93ccc004c7f86cd90722e3baa35f72e783ad9d37c2a01a286f346030e19 3150 python-llfuse_1.3+dfsg-2.dsc ade76293af094222f6c671ae6e809c011137a64426436c677aec22977b4938cc 139420 python-llfuse_1.3+dfsg-2.debian.tar.xz Files: 464379caa3406329ded469bb8c51f485 3150 python optional python-llfuse_1.3+dfsg-2.dsc 44427b2dae553cc291d1fe866f5bb6c5 139420 python optional python-llfuse_1.3+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlm73K5fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8Tlmf4I0P+wRuTZNadEINxC2w0NGQmPfh9JnhFoEbO18SZaeNjTxRJHE4 0fGAXuA32+BZB3th7hfoBx1inGmR7Vd7WQO7/BqimJNQ/KqU2kYEqYgwgp+kdJ+N HzQM/PQQNtcVFlnda/2fXEM2gqy+JyBP7As258N3+lQTUlC+uvFHEgePip+ryMz4 o8iX6/MrzQtgUICalVjA5RO8VjHuQ0L8PuEm/f/bO8+5lqh14CUX+uUjtI1PjggJ G+Apx/GX8tOaq5gt+ImGg+QC/Y2Az5iMEU3MjmzfY1FobcQcHQcZBom3JsFPTf5+ ktS6l7Elxm3tuak3TNiCVUkEtz6JDdIVsjvUnYngP1TuHgX5cK91NsiybtOnI8uJ 0td+4TpUXsamgRzm1O43tFo3jX1ZEb0WAgPEU7iOcCHI2fRrX97kqroA4k9gBI5S NCGRmi4wnS0lCcwEl8MYvhrWWE5BtdVTxTTdOXb/QQQ0otmlhVKkxPi53Yptnm5n VplM+CcYxfExQcqxFpR7bxZzugnnPbaJFLR8v5HyGfKFaG4E2hP0Gr4WL+5sRubF aMPWzAz30mz1Ah0YgK4Cdn+td+eqQO8Bg2TO5x5FSzwbNPH610EwF6POUEBHRADX 1nc0BB7x2c4P3Ep9pMtSf6kQAJtumlP1kRGoiaDQbaoQpO0KSyP15GRWm5F6 =8ta7 -END PGP SIGNATURE-
Accepted python-llfuse 1.3+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Sep 2017 11:30:10 +0100 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Changes: python-llfuse (1.3+dfsg-1) unstable; urgency=medium . * new upstream release Checksums-Sha1: ce5918ba8afb723b952f5b692ecd2bab4765a345 3150 python-llfuse_1.3+dfsg-1.dsc bddf00cd4c2362a38f9be353de0f8be20129626d 275086 python-llfuse_1.3+dfsg.orig.tar.gz bf818aab1225ebaf4be8105439d966dee51754a3 139176 python-llfuse_1.3+dfsg-1.debian.tar.xz Checksums-Sha256: 971a6b4eb587ce53a012d7889aa5f44f037541ded6450016f140b6520a2d 3150 python-llfuse_1.3+dfsg-1.dsc 04c4c9481c643cef7a0e16b9c515b767fbf49742284b674d80b44e69b7464565 275086 python-llfuse_1.3+dfsg.orig.tar.gz 5a5455901d23f45d34c1f9f3935739fcae18885bc12d710e6926ef919739888f 139176 python-llfuse_1.3+dfsg-1.debian.tar.xz Files: 1f506675cd8ea01e0bde0ff137ff0171 3150 python optional python-llfuse_1.3+dfsg-1.dsc 7572211ec121f3ca291c84f508e429c7 275086 python optional python-llfuse_1.3+dfsg.orig.tar.gz d5cfebbab60e735428cf9d198bbcf7af 139176 python optional python-llfuse_1.3+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlm7rohfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8Tlmfr8kQAIrNqv99NQk43vn5zqEvYDt0KZcTcVFl97SUDwWqcw7iNUY9 5pE7rpBPox9QMsmDJJH9DfoxUwkpyIuNfdQjQePamVR8H8K2E9cLBG3j6X6fTFDb ec/57qWhgbKc8Az1wp5sawOC9/LhH8RuRwFi6AOXqrgA1bYnSA4QgmixvYFAOqSr TxC0qGpbnDbkPzoMVzu5uCphY7zBuqfGkn8tnlD4GbYMygOyBZ/Dwm0tRbSLD0wU cbbrEjJnETtmGtvkZ/svqf/9Ntickn0eqoiFiRTH9eqMRoN3iElBhGWdo8aGRbaL HBgUAyKc2HU9JbbAR+snK6H6n9DZ4/UNiCtM/+ydf0DGI6Lh+CC97dTyzIS7F62i /WNPv2P3Zg7YxeEKlxgRzQfvTi7yT36TwkUsXzbxHwGSwTk3OSfC4omuVcPVP0nm zXZdMfqX3B9NxsvCm0VAqtWwG6OOTPlErMg8qY+sT8mxsxOgz+31gzqqKz+Ug1KY tzkURsDvL5+e7qe3Wn4x1jzqJAki5wHAQgZ2w/e9KFwm2VmLfgwPbey9m+sWGx8w NuPmkNIXkmaRWPP+0poKjliKuVd0aTzhE0oN4yg9OQjT3NcvZDcdecbxvV9Ja1ud o+3GqQqiNKlxfdEABSFBOdDSfegdgI26r8MQA6q9QmuSwCe8hiHKJEmU2vQ/ =7xcD -END PGP SIGNATURE-
Re: Whether remotely running software is considered "software" for Debian.
On Aug 28 2017, Andrey Rahmatullinwrote: > My position is that it should acceptable for a program in main to require > a non-free service, or data, or whatever, as long as that program itself > is free and running it doesn't compromise the freedom of the user. > contrib should be for wrappers, downloaders etc. The policy uses the word > "supplemental". If this is your position, then your position on the unrar scenario should logically be that putting the non-free components on a server somewhere is sufficient to allow unrar into main. If not, please explain. >> Finally, for the third time, please explain your position on my hypothetical >> unrar-nonfree scenario. > > I don't have a position in that scenario because I don't intend to dig it > and examine it. There is no need to dig and examine. Bas has provided all the context that is necessary. > I don't know why are you counting times unless you view this > discussion as a battle between you and the world. I probably share your point of view rather than Bas', but the way you represent it is a disservice. It makes you look silly and for some reason unwilling to address Bas core argument. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted s3ql 2.23+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 Aug 2017 14:38:51 +0200 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.23+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (2.23+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: b8c25f637ffcd3d8aac5cf867317917ead42f154 2941 s3ql_2.23+dfsg-1.dsc adb683a0268fd0843f3ce39d6d2e1a524386090b 674783 s3ql_2.23+dfsg.orig.tar.gz c7860f1aebf9d9b52e5e0b691a6b42d6485a6831 13560 s3ql_2.23+dfsg-1.debian.tar.xz Checksums-Sha256: dce228a958b711f17b85418bbdcaac35c252435411d7dbef7c93839d51388cc7 2941 s3ql_2.23+dfsg-1.dsc 55680203bac2488df08b992e4ff5be4d7888696dd72ba3a9d7bc569b5e9a04f2 674783 s3ql_2.23+dfsg.orig.tar.gz 169409f1f8511a0b22c0f92c63927da7d0fca1dbe9b8e9ccdd043b9443769c3e 13560 s3ql_2.23+dfsg-1.debian.tar.xz Files: 1adf1512a6b520a2d04efc8de96d81bb 2941 misc optional s3ql_2.23+dfsg-1.dsc b957c288b0f44df32234c69f16593b2f 674783 misc optional s3ql_2.23+dfsg.orig.tar.gz d1d5fb3089f7928f1570e94acaf194d9 13560 misc optional s3ql_2.23+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQLKBAEBCgC0FiEE7TF5GyxcFhOvOIuK0RP8rDxOWZ8FAlmYM8lfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVE MzE3OTFCMkM1QzE2MTNBRjM4OEI4QUQxMTNGQ0FDM0M0RTU5OUYjGmh0dHA6Ly93 d3cucmF0aC5vcmcvZ3BncG9saWN5Lmh0bWwSHG5pa29sYXVzQHJhdGgub3JnAAoJ ENET/Kw8Tlmf298QAKWOM7UCRzr7nMeH26BimxDJ/R5PGjtKaxw7lphzo8sGoHEx xUX/A6iEEN4J60JKq3GqRXuI5PisW6WFbTKpZSQjvlwJDogKStNmFWj/pgU/AqBa 26XBtRRxzVs0eptbKm7v/US/r4tZ6VaderUCcMlou+iBlSrWypy2+Rr0NhLBmiQl rFg8Qi7BqLFzibmucthnfRn1GaNQwbP9SI21HAFfZ0xICicStpzR+Kr+/qlu/5p1 0avxI5JusG0SlCHorawCwuM4YRokJLpgbDGsCj8PFFiYj3zlS0vkgV1CfWoqXb3I 85Nii268PFHpqlex6JnxakEIeLb2BLuKa/5mdV6QQ0415Ex/wPNvvspJcwFy5qyb 8exWH7FxKWAgvFZ/tnuKA1iija1+A3w+/Uusfu8MOb4+RqxDEBJYne4DUgP2FbbX VIco95IPm8MBUpote1O8uDeaien4Dz19QDXgUCGqPmAcOuz5uXvPBfBz+qRMQ4Fx c2/tSYXgSoH1SAYnWh7ItKTSIaDW9ad0ZtR0WUvyrs1zBpaRamCb2d5c1doNUpHl 4CbNbpjFVWwJvwv8VJZrG2YfjPew5DXJ0pPe4OgtLukjT9eQyehI64+ifp92sYNp yBE7ae6qB2ImALF9RO3P4SrKDZFv6J+p7OTxkeaVhkYJ4sivQsytiSsL4EBS =lwLY -END PGP SIGNATURE-
Re: Embedded library copies - mergerfs
On Aug 07 2017, Antonio SJ Musumeciwrote: [libfuse] > There are secondary issues related to v2 being no longer maintained What makes you think so? I'm not adding new features, but it's definitely still being maintained. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Embedded library copies - mergerfs
On Aug 07 2017, Ben Finneywrote: > By your description, the upstream code doesn't do that. One obvious > workaround is to remove the embedded library in the Debian ‘mergerfs’ > package ‘clean’ target, patch the software to instead use Debian's > packaged ‘libfuse’ library, and maintain that patch in the Debian > ‘mergerfs’ package, indefinitely. > > There may be some upstream changes that you could suggest which would > make that easier. Could a bit of refactoring in ‘mergerfs’ allow for an > easily configurable ‘libfuse’ location? Could those changes be made > acceptable by the upstream developer? libfuse upstream here. I am not aware of any open (non documentation-) bugs reported by mergefs people. So by that criterion mergefs should work just fine with the packaged libfuse. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Naming of network devices - how to improve it in buster
On Jul 11 2017, Simon McVittiewrote: > On Tue, 11 Jul 2017 at 13:45:25 +0200, Bjørn Mork wrote: >> I got to ask: Why? We do not have stable names for e.g. disks. Why do >> we need it for network devices? > > We do have stable names for disks: look in /dev/disk/by-* and you'll see > a bewildering variety of ways to refer to the same disk or partition. I wonder if anyone actually uses /dev/disk/by-path? > The thing that is different for network devices is that network > devices are not files (device nodes), so udev cannot create a symlink > /dev/network/by-mac/01:23:45:67:89:ab -> /dev/network/eth0 or whatever. > Network devices are (as far as I know) the only class of device managed by > udev that is not backed by a device node, which means udev cannot provide > multiple equivalent names for the same device, and is forced to choose > exactly one of those names, and rename the device if the chosen name > is not the kernel-generated one. That is why naming network devices is, > and has always been, more controversial than naming disks: they are the > one device class in Linux that violates the Unix design rule-of-thumb > "everything is a file". > > If network devices were files, udev wouldn't have a configurable > NamePolicy to rename them: it would just provide symlinks for all the > possible naming policies, and let the sysadmin use any, all or none of > those names when configuring tools like ifupdown. Unfortunately, that > isn't possible. Independent of the current discussion: why not? Is there something that would prevent the kernel from starting to provide network device nodes in /dev in some future release? It seems to me that providing a file in /dev and internally mapping this to the old device name shouldn't be that big a thing... Curious, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Naming of network devices - how to improve it in buster
On Jul 11 2017, Michael Bieblwrote: > Am 11.07.2017 um 12:14 schrieb Guus Sliepen: >> Ok, it should be clear now that the new way of naming interfaces is not >> ideal, but the older ways weren't either. Let's have a look at what we >> want: >> >> - A simple name for systems with a single Ethernet and/or Wireless >> interface (the simple desktop/laptop scenario). > > How would you determine that a system will only ever have a single > interface? I don't think it's necessary to do that automatically. On most systems with multiple interfaces of the same kind, the admin will know about it and can explicitly enable the extra functionality that is needed to get stable names in that situation. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted s3ql 2.22+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 23 Jun 2017 09:53:10 -0700 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.22+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Changes: s3ql (2.22+dfsg-1) unstable; urgency=medium . * Dropped jessie compatibility patches. * New upstream release Checksums-Sha1: 1b42c6a9a8ad46e5dee5ae4f2057fc28e4a49945 2822 s3ql_2.22+dfsg-1.dsc 60e31d4d4d24c53598ad03d6eb65e93f5914fd41 650427 s3ql_2.22+dfsg.orig.tar.gz ec71ec3195349e4f6cb71712345e4a2173999317 13596 s3ql_2.22+dfsg-1.debian.tar.xz Checksums-Sha256: 5c6fc61e43215de63271616bca64d56f05280509f39920c54202dcf1b67dbe9d 2822 s3ql_2.22+dfsg-1.dsc 59be5628f6a03e4ae1feffcd6607af333e1bf27b35de6e697782b50b359e4573 650427 s3ql_2.22+dfsg.orig.tar.gz 378d543c8c6b8ddce3a74d63d918223f261a6e76274c881d4a3fa2a090237142 13596 s3ql_2.22+dfsg-1.debian.tar.xz Files: 38a6c9ae8503341e0787433f2757934f 2822 misc optional s3ql_2.22+dfsg-1.dsc d9326447ee0f6ca9acbf5cccb3a93a39 650427 misc optional s3ql_2.22+dfsg.orig.tar.gz 058a4373645bf5b72d57b970795007c7 13596 misc optional s3ql_2.22+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQKgBAEBCgCKBQJZTUlMXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRDMxNzkxQjJDNUMxNjEzQUYzODhCOEFE MTEzRkNBQzNDNEU1OTlGIxpodHRwOi8vd3d3LnJhdGgub3JnL2dwZ3BvbGljeS5o dG1sAAoJENET/Kw8TlmfqugQANNxvgtVheoFcyeBw5ax5sbR5SOibxOsi9ky8Q7R RB6dN6HcakYM3z+g28vLSoa+WPGwav82UWk/kNdhYoq6Jt/wkI/SCpzMnWOKn/N0 FfCjLcVujMnO9a+7IPjcvOFGA9v3y055GH5skPA2J+RzJtJ6U2CSLt+IW7X2sYi7 ei0dyf4nRwLm19USmpf/phOBfil/Fiiawlu+CMdmSn1MRugRtTTU6+lUuB3kdXVn e1wc9E+xlavcnTfD4OlyyHR5rWlyokHHzWyDvl3Qh7NQOLhuIQa1SjQaa0y2HhLI dH7MJzR7WN7qzvBxzUkpzHBC0eQ6DgxhzQbqDq1ktq2CWS0UIY27l/tRWyc0Ru0u jmmwUOqn0lB3e+CEB9dvmdLfBtHgBwDcTcyQUUiaIgekP3bqCGsI/UswnJ7yWShF v9sHDs8JW43ZVIG95MY5YgXFd/otT97iZze43OdgeKSjK9/zVi1BN85p+oNylPIz lVx6n3UMnjhkUh0ki5uf6O2m0QJDyRXvBR901UGYZ6Q8TL1RKKOLnMsRKT5+VzRD gl8B7sH6FDV3jwf0rQfUSsOCTlVPz4ba1jH2/wLVLbl24sqMbqM3H8A7586hX5yr +g7BPk8RhfCEfNCiiZ/wvWKwS4fdqbuMhIDdQKYaTYjeEGmLu8fvV/ecgOtiXB/V Ex+x =XjJt -END PGP SIGNATURE-
Re: What HN would like to see in buster
On Jun 20 2017, Sean Whittonwrote: > While browsing the thread, I was struck by the number of requests for > tools and features that we already have -- things like checkinstall, > reportbug, dgit and continued support for sysvinit. > > I don't know how we could better go about advertising such things, but > it's somewhat tragic that features into which so much volunteer effort > has been poured are, apparently, barely accessible to outsiders. Not just outsiders. There is a number of tools that provide what I'd consider important, core distribution features, yet I only learned about them because they were mentioned in passing on debian-devel. Apologies for not being more constructive. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted python-dugong 3.7.1+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 15 Jun 2017 10:39:56 -0700 Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-dugong-doc - HTTP 1.1 client module for Python (documentation) python3-dugong - HTTP 1.1 client module for Python Changes: python-dugong (3.7.1+dfsg-1) unstable; urgency=medium . * new upstream release Checksums-Sha1: 5eba70770e09c4214e723dc9483141d7bba5d254 2560 python-dugong_3.7.1+dfsg-1.dsc 603112d9155955c4acbd5899ad91ffed31f30bbe 59577 python-dugong_3.7.1+dfsg.orig.tar.gz 6009e622bcfafe76a11bd008b80cb09a8ab3eb2a 133696 python-dugong_3.7.1+dfsg-1.debian.tar.xz Checksums-Sha256: b8f0a4ce72aaa7e01da5b5f70947f1847731f0d41b05cace372148bafb7b133d 2560 python-dugong_3.7.1+dfsg-1.dsc 59802f4981dc119488431cf581b8c09ed024acd5ccb49e79a9a9c5f7bbfea3d8 59577 python-dugong_3.7.1+dfsg.orig.tar.gz 6d5abf42592b57c9ad1774715a05acb618d68082c7e9d05977deffc31b106619 133696 python-dugong_3.7.1+dfsg-1.debian.tar.xz Files: 899d1afb61c9814db815d75ca3301195 2560 python optional python-dugong_3.7.1+dfsg-1.dsc 6084ced73d3e7f8200b63ac3a8d325df 59577 python optional python-dugong_3.7.1+dfsg.orig.tar.gz e5fc295c408bb2ffe31f760e37e67bd2 133696 python optional python-dugong_3.7.1+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQKgBAEBCgCKBQJZQskwXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRDMxNzkxQjJDNUMxNjEzQUYzODhCOEFE MTEzRkNBQzNDNEU1OTlGIxpodHRwOi8vd3d3LnJhdGgub3JnL2dwZ3BvbGljeS5o dG1sAAoJENET/Kw8TlmfUUsP/0/+7Vn3WUzIFjDdVVHPrLDOD/QLn+QJPyWVDP4V SW2z3cbX+lQbeCc53Uta/nB2HZskYjZY34LjoOXkrTtpI87tHVn8mMzA+H8wAi2k 6Ibay/fJkvZIdXxbs84AlyaNjTEh5uUYxNpNn0R+Lw0sC7kWk5O79kyfX7wqHGwE HqlS7cG6Q5ovoOkmzEgyvgMvgxrIt5RCnjInToMrBlV3RyGzSiF8zFfklv/M6QIT R/JJ7HIZQyQ3NxPALrdROoeDOztoXsN4VSSgOHLOnuHWo+W/mufZvUQ3jm2s7GXd P0dYMRaM3cjnsy2f6CmD46xI9nIeDdJImB6Dn2y4kQb1g+UcSkJbpFlS2H5hWhiQ eO73rvWcI6eYFuEVCjA4TcuJVEqxCfFHQLh2zrEwLT98vqcNwbiQnRvWtc1B6YNQ QBUi0C9YhdcLUGut86zMksBVPWXVa0AFMay4b+749qeVKIeMlqNd8m1VWSWSm0aQ 8mQ2l/yAESPcQaGTbD9/ynzEY1RfR0BLEngO+yGVC3SRQUogZz2kDzziceEfDjPn n6A9NS4nh/a+Ear3mfUxLyCM6JQjs8PZxwzyr0sesBskdXISOCXglCMfUu82CdJK M4P7+2PTq2d8eOAJOg+Mc8ZihJeefl3hcSuGeJWLZwCPRfJylQrMs9Q7uJWBPiqF 3u6T =CK9t -END PGP SIGNATURE-
Re: Too many Recommends (in particular on mail-transport-agent)
On Jun 08 2017, Adrian Bunkwrote: > On Wed, Jun 07, 2017 at 03:26:35PM +0200, Christian Seiler wrote: >>... >> - You install package A, which Recommends: B, but you don't >>want B, notice that at the time, and either remove B >>afterwards, or install A with --no-install-recommends. But >>then you install package C at a later point in time, which >>actually depends on B. You notice that C is not what you >>wanted, purge it again, but apt-get autoremove will _not_ >>remove B, even though it's automatically installed, because >>A recommends it. >> >>So basically, the following command sequence may or may not >>leave your system in an identical state, depending on the >>packages that previously have been installed on your system: >> >> apt-get install A >> apt-get purge A >> apt-get autoremove --purge >> >>Unfortunately, I don't see a good solution to this problem, >>and I've thought about this a lot in the past. >>... > > apt-get blacklist-from-recommends-install B > (or a similar entry in a configuration file) I might be able to get this today when using debfoster ("negative keepers"). Best, Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Switch default installation image link?
On Jun 06 2017, Steve McIntyrewrote: > I'm *also* tempted to switch from the netinst to the first DVD image > instead - network connections have improved a lot. Why is that relevant? Is installing+downloading the DVD image faster than downloading netint + installing from network? Personally, I would only ever download a DVD image if I was on a *slow* connection and knew that I had to install to multiple machines. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: A proposal for a tool to build local testing debs
On May 25 2017, Sean Whittonwrote: > Then in dgit-user(7), the SUMMARY would become > > SUMMARY >(These runes will be discussed later.) > >% dgit clone glibc jessie,-security >% cd glibc >% wget > 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=28250;mbox=yes;msg=89' | > patch -p1 -u >% git commit -a -m 'Fix libc lost output bug' >% sudo apt-get build-dep glibc I think the last line should better be $ mk-build-deps -i ..in that case you won't get bitten if the build deps of the new package differ from the build deps of the package in the archive. Does build-dep require deb-src in sources.list? If so, the above removes that requirement as well. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)
On May 15 2017, Adam Borowskiwrote: >> https://www.debian.org/ > > Not that different from Gentoo's. What's the problem you're seeing? I think this is one of the those situations where if you don't see it yourself right away, you'll just have to take other people's word for it. It may not be that different for you, but there's a big difference for at least some other people. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Moving away from (unsupportable) FusionForge on Alioth?
On May 15 2017, gregor herrmannwrote: > On Mon, 15 May 2017 14:43:56 +0200, Johannes Schauer wrote: > >> Quoting Jonathan Dowland (2017-05-15 10:25:30) >> > ^ how many of these are from teams (like pkg-gnome, at one point at least) >> > who want to switch to git but lack the time or person-power or motivation >> > to >> > perform the task? > >> The top 10 teams with packages in SVN are: > […] >> 285 Debian Perl Group >> [...] >> 140 Debian Python Modules Team >> > > The Debian Perl Group switched from svn to git in Summer 2011. Same for the Debian Python Modules Team. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: "Ask HN: What do you want to see in Ubuntu 17.10?"
On Apr 08 2017, Wouter Verhelstwrote: >> - Airplane-mode Hotkey (especially hard apparently) >> - Volume Hotkeys >> - Brightness Hotkeys >> - Suspend/hibernate hotkeys > > These are all implemented by ACPI on modern hardware. You need to have > something that turns the ACPI events into something useful. > > If you have acpid installed, it usually turns the ACPI events into X11 > key events, [...] The "usually" is the problem :-). >> - Hot-plug of external monitor > > Haven't gotten that to do anything useful, but then I also don't want it > to (I just run xrander and tell it what I want changed). That's what I mean. But again, xrandr doesn't always see a monitor when you plug it in. And at the moment my X11 crashes when I unplug the HDMI connection without first explicitly turning it off. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: "Ask HN: What do you want to see in Ubuntu 17.10?"
On Apr 06 2017, Gunnar Wolf <gw...@debian.org> wrote: > Nikolaus Rath dijo [Wed, Apr 05, 2017 at 03:18:57PM -0700]: >> >> I have a very different perception >> > >> > Me too. I guess it depends very much on whether one can afford to buy >> > a good laptop which works well with Linux. >> >> I think there's a pre-requisite that's much harder for a lot of people: >> finding out what laptop works well with Linux. This is the stage where I >> have repeatedly failed - the differences in model numbers are just too >> tiny and subtle, and typically things that work well are no longer sold >> commercially. > > FWIW it's been a long time since I had any problems in this regard, > and I'm surprised it's still an issue among knowledgeable people by > 2017! Maybe I'm just exceedingly unlucky, but I have yet to find a laptop where all of the following works: - Suspend - Hibernate - Airplane-mode Hotkey (especially hard apparently) - Volume Hotkeys - Brightness Hotkeys - Suspend/hibernate hotkeys - Hot-plug of external monitor >From memory, some of the models I tried and found lacking: Asus EeePC, Lenovo Carbon X1, HP Elitebook from ~3 years ago, HP Elitebook from just now. Suggestions for the next purchase are welcome :-). (but probably better off-list) Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: "Ask HN: What do you want to see in Ubuntu 17.10?"
On Apr 05 2017, Ian Jacksonwrote: > Florian Lohoff writes ("Re: "Ask HN: What do you want to see in Ubuntu > 17.10?""): >> On Wed, Apr 05, 2017 at 02:56:04PM +1000, Russell Stuart wrote: >> > As far as I can tell, for laptop's rebooting is a non-issue mainly >> > because suspend is not reliable enough to use safely [0] - so they are >> > rebooted every day. Ergo just fixing bug #744753 would be the cure if >> > it is indeed the problem - but it doesn't sound like it to me as this >> > isn't a suspend issue. >> >> I have a very different perception > > Me too. I guess it depends very much on whether one can afford to buy > a good laptop which works well with Linux. I think there's a pre-requisite that's much harder for a lot of people: finding out what laptop works well with Linux. This is the stage where I have repeatedly failed - the differences in model numbers are just too tiny and subtle, and typically things that work well are no longer sold commercially. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Help requested: Packages which FTBFS randomly
On Feb 21 2017, Vincent Bernat <ber...@debian.org> wrote: > ❦ 21 février 2017 09:48 -0800, Nikolaus Rath <nikol...@rath.org> : > >>> Your chosen build environment is not common [...] >> >> This has come up a few times now. Could someone explain what is so odd >> about his envirnoment? It does not look unusual to me. > > Official buildd have several CPU. Most "important" downstream > distribution builders have several CPU. [...] Yes, but last time I checked a "apt-get source && debuild -us -uc" still defaults to using just a single CPU unless you explicitly set DEB_BUILD_OPTIONS=parallel. So if this causes the build to fail, it will directly affect those users least able to figure out what may be wrong. > Accomodating for all build environments is a slippery slope. In my opinion there is a big difference between asking builds to work with a single CPU, and supporting "all build environments". Best, -Nikoalus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Help requested: Packages which FTBFS randomly
> Your chosen build environment is not common [...] This has come up a few times now. Could someone explain what is so odd about his envirnoment? It does not look unusual to me. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Git hosting for code that provides Debian services
On Jan 30 2017, Lars Wirzeniuswrote: > I personally don't find "open core" projects to be fully free > software, even if they follow current DFSG, OSI, and FSF criteria. This strikes me as a little odd, though. So if the company that sells the "closed shell" goes bust, would that turn the remaining core into free software for you? Or, to put it differently, is an orphaned project with no maintainer to accept patches preferable to a project with an active maintainer who rejects some useful patches (because he wants to sell them), but accepts others? Curious, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted python-llfuse 1.2+dfsg-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 22 Jan 2017 14:42:22 -0800 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Changes: python-llfuse (1.2+dfsg-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 0092dc1bcd61565524cce1bd0b41decf3ab26530 3007 python-llfuse_1.2+dfsg-1.dsc 82aa6395d0e82eeb19752e2d9c82cd2e982b47cf 257820 python-llfuse_1.2+dfsg.orig.tar.gz 0d113679a4be868191a7e136675743619d21ce2e 141696 python-llfuse_1.2+dfsg-1.debian.tar.xz Checksums-Sha256: 19d05aaddeb0b7a669a507d887447146b9d2cec93369b268935797ee26f1f78c 3007 python-llfuse_1.2+dfsg-1.dsc dd7870d12e1479a8ecee7ec20bccef15e45b4902d081af400972ca9e9ed088f9 257820 python-llfuse_1.2+dfsg.orig.tar.gz 549524baf8e3bf54c3118adb0fb5aba2234e5bd12fd68450f058ca501fc82c60 141696 python-llfuse_1.2+dfsg-1.debian.tar.xz Files: ed72644c85cbe2637c65bfa66b0f2ba6 3007 python optional python-llfuse_1.2+dfsg-1.dsc d9d2ae12506d887a0a81a1ffa3c1afd9 257820 python optional python-llfuse_1.2+dfsg.orig.tar.gz 1a8826a35b12d5a0b8baae37a64cfa00 141696 python optional python-llfuse_1.2+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQKgBAEBCgCKBQJYhTgRXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRDMxNzkxQjJDNUMxNjEzQUYzODhCOEFE MTEzRkNBQzNDNEU1OTlGIxpodHRwOi8vd3d3LnJhdGgub3JnL2dwZ3BvbGljeS5o dG1sAAoJENET/Kw8Tlmf0UgP/iCEWCLDi18TJiQLZQezH9GkvaNsiBkFZqA1N3qc dkUMFJCSYjmdrjyw2HTYN2LMF+Cbhc5aonh/A6sJJq3JOk+/pMz7nHA4c8ZXBcK5 ynANhKeY+RyEgMx29DL1uUl8PR42dKspRTVU0ZnBnpli9OcNWSC+xZa82FR1XdPL rp2yz1Ze0wmkhK8Yupjo8L4Uk2Qqst348iNqx0BBA7ek7fIGnkYVdWh0CnFq0SPm v/k97gdRmjMFwi+8j/E/unn4+AZDBJlDvjMOjEicII4zRnUBTn3ZUqf+mL6hf/0d E4iE0E28YuYLntQurmldjr3g32nuc4EehGLuCe7d6H/VMeCHFgQ0rQplsfXPlcH3 UyLXqnYfVbU6YrunskqKknsc+E2h80EVuK1WGJxGjxUW5qq0G9aje29wmlB8tS9w HjQZ2QM9fxlPtrlg5VWjwU5pdykvcdOxCbKlUclzhZtw6AcF3a+80+7/2sruYtd7 PMHajANDxhxhGdNixD4FePY0pibwoS+4I3D2JnSEd8+Bip98sHaVXwUpf0atzFpD rBKCnoZjZposl9L1AzJxpYrJLLYd3BFYNewtyvYie3GIStJwKJdPrluVZjQhJOQF 1ZR7X7ZtpvDOmSf92VkcHqFdECU4Ym5wBl0zb5EFonrkJ6GDO83DDYb0k4IK85+B X+eA =jBS8 -END PGP SIGNATURE-
Accepted python-llfuse 1.1.1+dfsg-7 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 22 Jan 2017 09:54:54 -0800 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.1.1+dfsg-7 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Changes: python-llfuse (1.1.1+dfsg-7) unstable; urgency=medium . * Fix syntax error introduced with new Debian patch in -6. Checksums-Sha1: 9ff075ad9bcb66bd741c344f171e0a966541e7bb 2899 python-llfuse_1.1.1+dfsg-7.dsc 34ce9ef6060a36260dc53e0f1ef632657a494441 142752 python-llfuse_1.1.1+dfsg-7.debian.tar.xz Checksums-Sha256: 85895575004b594bfb03353a9e677c76342a63b50b96178c5eed8deb770f9374 2899 python-llfuse_1.1.1+dfsg-7.dsc 752b47d8b07f94e229ac46bfd87d56bb2f0b96e8e69b91c462e7be6d9313138a 142752 python-llfuse_1.1.1+dfsg-7.debian.tar.xz Files: ae9cd5694f577230c3eb998a91ea3c47 2899 python optional python-llfuse_1.1.1+dfsg-7.dsc d158476d9fbee161659ba99d820e53aa 142752 python optional python-llfuse_1.1.1+dfsg-7.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQKgBAEBCgCKBQJYhQTZXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRDMxNzkxQjJDNUMxNjEzQUYzODhCOEFE MTEzRkNBQzNDNEU1OTlGIxpodHRwOi8vd3d3LnJhdGgub3JnL2dwZ3BvbGljeS5o dG1sAAoJENET/Kw8Tlmf9oAQAJHaQsLcZGZvZkWkHFKHsHxy0XGofZ4tUIfz0V0e RmkCkeaq2AUueXtmDohdqNuyWkoBnSr/FbMKCrPlNgi7XnrHfTLjO5imzZlZfhjU LNCquKWO2vpFxdmtn0CEJYuBeZoA+pNFtRMmyR5ubVmxJb1Qii3Us6sR3kPxC0gb tKTo8mQK9vYU/L8BIoD5LdNmbUs1gncBA5Mhua76P7uUJePCWtx1SPoekzHWachg 4XPHudRlW9tXKRW7Ir39LqAxTbGfRxN9ICK07Vdmwh/cUtUWXX+e6yZUqMt0xHlV KL6/r7gWYQZF3Gr0k+7wj+Qaxx5xAENMC5Bf3YWrOhcZeH78JxL552ePQTMGRxYg QaHaDjFrm3ocfmEbft3A5gICJ1ToS+C0gSjqUvFrklRMG22s6dq4/DjUhrzoBpqb OhUpve2cEIqi92AYqHHnU8U1EvUx0MUcf4xIOiifRN+/c8lGFtpup0RA4st+uv8l yKqhbgaqQ5aGripgmeNEDH5UYfupBH3AYCSVP7qD2Xt/36TUE51jvys55pTjZagJ U2bCqyty5EQls1Cjzpsmy78iL4O1HP3XuPiVDEioca+4NmkMqwbdodsndkjlJqpN sOF13wJ6tDRkzkF88XgMGN54Ht0ZD6IsB6LaenaagIrS9bCTopO33hFiGXtOeiGy RJax =S73A -END PGP SIGNATURE-
Accepted python-llfuse 1.1.1+dfsg-6 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2017 16:36:43 -0800 Source: python-llfuse Binary: python-llfuse python-llfuse-dbg python3-llfuse python3-llfuse-dbg python-llfuse-doc Architecture: source Version: 1.1.1+dfsg-6 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3-llfuse - Python 3 bindings for the low-level FUSE API python3-llfuse-dbg - Python 3 bindings for the low-level FUSE API (debugging symbols) Closes: 851724 Changes: python-llfuse (1.1.1+dfsg-6) unstable; urgency=medium . * Ignore exceptions during interpreter shutdown . These can most likely be ignored in general. In the specific case that we are addressing with this, they also seem to be caused by a bug in Python. Closes: #851724. Checksums-Sha1: 61c713cc736b95c2c52fca150719641356863ee0 3023 python-llfuse_1.1.1+dfsg-6.dsc 75fb2a111030842e70351dc1bb146159503b60ae 142464 python-llfuse_1.1.1+dfsg-6.debian.tar.xz Checksums-Sha256: 71d92d938edfb48b9e3d2c7d4176580560a401d630b43a4c0e6df7411051d402 3023 python-llfuse_1.1.1+dfsg-6.dsc 715fe12290859a0f21af128f4e48e2ba300cd3f32adbf59dd74f351847cd83ee 142464 python-llfuse_1.1.1+dfsg-6.debian.tar.xz Files: 36d1800d098a643ae391454c0d1ffb82 3023 python optional python-llfuse_1.1.1+dfsg-6.dsc 0227f0eca5e801f0ee4a28509147bfa1 142464 python optional python-llfuse_1.1.1+dfsg-6.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQKgBAEBCgCKBQJYhAD7XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRDMxNzkxQjJDNUMxNjEzQUYzODhCOEFE MTEzRkNBQzNDNEU1OTlGIxpodHRwOi8vd3d3LnJhdGgub3JnL2dwZ3BvbGljeS5o dG1sAAoJENET/Kw8Tlmfv90QAJBtqBI7uZlI6W4XZgZMbX6Xc5GpSF7vXlMx7D2Z bQbJ/kKt1mfcI6BQsOX3vm014xgzX6MEAxBjWbuZmQBm2gQAbHaFUgADi+YaPwBu Tw9gQPDYhLIQ+jnq1oB9cHptyhn9uredrZvPZzFvZfq91en/UjWMAkr0I4HcCqb1 m0i9RfwngSUpwpLXcg33p0rRb7zFg2oMoBBY9GRAGJ8egc4Q9o2Jaf1ZzmTz4PDL b4HiJ5NL/wx9hriUVKJG9yg1qyW3TmNh/0G0+ht2tz9aky0ePoz8ZhTXoFT/5ts5 YRWZArJfqvrgIFJcpeQlRaV7Nxsb9RC95CT6C++wbSlGB6+/0gazzPAu8b3f39U8 UHk0vrjzv2QtmmNlVJ0R51RiigOEYv0eFiJ/mFh6hg85kZYvIYhVsKv88s/Qeu+o CvVIJWwoeyR7K6b13GtNhanqRoBT7P+if0gIJBdyRVoNpRYvG9+Rd2U1N33ThpAS AewbB7xbCqiB6QO9OSF9uPIr8iKW4stt2aHnZlJNqjms903b1n2xEOPgHIzc/KXC vyekwiNQ8bN559zQUqVQCmXVA5KwLpiQnhkv56gqCNjMokj5mACFTJ9b58Auo7C2 bJ+JpmuUv5XVa/+b1S0utF+PjJzjOJEuf2lI95cO14sW5nw3FEPsiuRVyrbHm0aS kkkW =stNZ -END PGP SIGNATURE-
Accepted s3ql 2.21+dfsg-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Jan 2017 20:35:21 -0800 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.21+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Closes: 851375 Changes: s3ql (2.21+dfsg-3) unstable; urgency=medium . * Expect test_verify() to fail during build. There is a race condition in the test that still needs to be fixed, but this should not cause the build to fail. Closes: #851375. Checksums-Sha1: a71abdbba19224fe4f0ccc5d5b6c29bdec2c357b 2822 s3ql_2.21+dfsg-3.dsc 8e0ec81ed3ca10840e45d4d0d4f750d15ea818f1 21248 s3ql_2.21+dfsg-3.debian.tar.xz Checksums-Sha256: f7d2c3355ad7b4407a16c13514527174721a01ca93fc2f999d83e1bf696361e6 2822 s3ql_2.21+dfsg-3.dsc 69e888b4db8364e3eca0ebf05fda34981b856f71c84b710fa420e8fb74eebbc0 21248 s3ql_2.21+dfsg-3.debian.tar.xz Files: c3d7db479e4216226f5d6ded878c7223 2822 misc optional s3ql_2.21+dfsg-3.dsc 5e8d150027cb783610b481361332ccbd 21248 misc optional s3ql_2.21+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQKgBAEBCgCKBQJYfvFbXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRDMxNzkxQjJDNUMxNjEzQUYzODhCOEFE MTEzRkNBQzNDNEU1OTlGIxpodHRwOi8vd3d3LnJhdGgub3JnL2dwZ3BvbGljeS5o dG1sAAoJENET/Kw8Tlmfc64P/A0sgJpFl0v2ZzK2eI0oUexPl2o/vQb9E9wKbZef xQiWn/vHfyPQm0Oqhi3SAv28yL47LXDSgaRF6MPdJd+l1hq4uIxmLX9LUcw5i632 KrxO6p/olhnHYDyg55hvFwwdiNNafzUnNDHvPDHaiHFvy6XfAkb/1HqqshMgORup YezWi3eM78+lFCbGnIt8DGl5MIEHim6oTf5lVkWBIcp/DR+ZtyiH5w3g4FGMzHbK OwUk/4xMZogQIZlcShsI7fK1qg6uSxrqyEkqLo/4sg2xVG2vsMxHGg9XGR41BwUm O2UICGy8H2j+C10uWSCLsCgKr1DG/Ryj00TpyLXznvDs8zUOfruJTFlLm22UWRvF rWk2awRdedT6hdkTwrdX/HTADFfQxQ5yKfBc0yWrdcOU9gEJnF4cHT8WIB1gjyWf wg6c/jA0tj9iViqn/fywc6TxAaLHAVT5bu6a3hKmW8GvXzSWBUQjGQWpPs48pOYy LgMlD1K9+whWNpWdMzNIvDPTfyyU24Rw8vKuvGcd+p3s9a8HSRm/IhOOWsg0hYBM OdUGEQFKiramzo1LWmWtSFllNXDr74CqnTRNIvXeFPceWFLVjpbKVDBQnHaE/Pxa ioQ5VbCeIrH4VGrO5kUry+fqahs9zJ23iMz/672Op3duRDhIXg45/jg9Noom9L72 LRwf =Qh+3 -END PGP SIGNATURE-
Re: Feedback on 3.0 source format problems
On Jan 10 2017, Guido Günther <a...@sigxcpu.org> wrote: > On Wed, Jan 04, 2017 at 04:38:11PM -0800, Nikolaus Rath wrote: >> On Jan 05 2017, Brian May <b...@debian.org> wrote: >> > Vincent Bernat <ber...@debian.org> writes: >> > >> >> There have been a lot of complaints about it. For me, it is a pain to >> >> use. Its integration with gbp is poor, it produces a messy history when >> >> you are working on your patches and I often run into problems with >> >> .debian/.git-dpm file it maintains (import a new upstream, make some >> >> changes, notice that somebody else also pushed a change, pull --rebase, >> >> everything is broken). Since we started using it, we opened a lot of bug >> >> reports and not a single one of them has been fixed. I think that nobody >> >> wants to work on it because it is an extremely fragile tool and the >> >> first one to try to fix it will inherit of all the problems to solve. >> > >> > It also has a number of bugs that are not getting fixed. >> >> Yeah, I think we heard before that git-dpm is not being maintained. I >> said it, Vincent said it in his reply, and now you are saying it >> again. No one is disputing the point. >> >> > Plus if conflicts occur because multiple people unexpectedly make >> > changes at the same time it (i.e. you can't push because somebody else >> > already pushed changes) can be a world of confusion trying to sort out >> > the mess. >> >> Yes, it is a mess. But I don't think it's any worse than having to >> resolve conflicts in debian/patches/, which is the equivalent problem >> when multiple people use gbp at the same time. > > When this happens you do a "gbp pq import" and have the full power of > git rebas at your hands. Are you sure? The problem we're talking about is when two conflicting changes to debian/patches have been committed. I think in that case you first have to solve the git conflict before you can call gbp pq - or can gbp pq import really deal with conflict markers *inside the patch*? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Feedback on 3.0 source format problems
On Jan 07 2017, Thibaut Paumardwrote: > Well, just to say, I'm personally quite happy with '3.0 (quilt)'. I try > to maintain all my packages in git in unapplied state, because in my > opinion this is the sensible thing to do. When I do a > git diff upstream master > I want to see only debian/ in there. What's the point of that? If the only difference is the addition of the debian/ directory, you can simply look at the debian directory. There's no need to use git. > I much prefer to check a diff of diff over a simple diff, Wow, ok. That is astonishing to hear, but I'll take your word for it. > For me the patch is the final product, I like the clear separation > between upstream and debian/, so it's for me a very appealing design to > have individual patches in debian/patches. I use git to keep the history > of the patch, not to manage it. And so is this. Well, I definitely learned something new in this thread. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Converting to dgit
On Jan 06 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: > Hello Nikolaus, > > On Thu, Jan 05, 2017 at 03:59:40PM -0800, Nikolaus Rath wrote: >> On Jan 05 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: >> > On Thu, Jan 05, 2017 at 12:39:25PM -0800, Nikolaus Rath wrote: >> >> But, as far as I can tell, doing this work up-front is much easier: >> > >> > Yes, but you have to do it every single time you make changes that you >> > want to be able to push (i.e. more than once per upload). >> >> What do you mean with "it"? You don't have to resolve any conflicts >> unless you update to a new upstream that conflicts with your patches, or >> unless you change a patch in such a way that it conflicts with a >> different patch. > > Sorry to have been unclear. I meant the `gbp import`, (at a minimum) > check things are right, `gbp export` dance. > > This is a lot more work than `git commit`! Aeh, what? If you make changes to debian/, you need only 'git commit'. If you change something in the upstream source (aka, add a new patch), the "dance" is: $ gbp pq import $ # make changes $ git commit; gbp pq export And similarly for git-dpm. Surely typing these two extra commands is not "a lot more work", is it? Note that they will succeed without interaction. If you want to edit an existing patch, you need to add one "git rebase -i" command. I would maybe count that as "more work", but certainly not as "a lot more". Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Accepted s3ql 2.21+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 Jan 2017 11:29:24 -0800 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.21+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: s3ql - Full-featured file system for online data storage s3ql-dbg - Full-featured file system for online data storage (debugging symb Closes: 850458 Changes: s3ql (2.21+dfsg-2) unstable; urgency=medium . * Bumped python3-pytest dependency to minimum version required by upstream. * Added build-dependency on procps. Closes: #850458 Checksums-Sha1: 78a0ddfd635939a619717deb90aa066fd9cdb50c 2755 s3ql_2.21+dfsg-2.dsc 3f81de09617f0725d701b23f68ad72780cd5fd9d 20948 s3ql_2.21+dfsg-2.debian.tar.xz Checksums-Sha256: 6a6e93fcfe4762e274f302623ff00abbb654499209ca1ffa3eb29826c8cac016 2755 s3ql_2.21+dfsg-2.dsc 4474bb4c8a4b7baa36db11f0464b52ef49534a48b9a60354dd8062bd17977cc5 20948 s3ql_2.21+dfsg-2.debian.tar.xz Files: a85fdfc4433f4185c6daa99e94fe4086 2755 misc optional s3ql_2.21+dfsg-2.dsc acbc728cce19c177e478e3b8de9f320a 20948 misc optional s3ql_2.21+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQKgBAEBCgCKBQJYcBjtXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRDMxNzkxQjJDNUMxNjEzQUYzODhCOEFE MTEzRkNBQzNDNEU1OTlGIxpodHRwOi8vd3d3LnJhdGgub3JnL2dwZ3BvbGljeS5o dG1sAAoJENET/Kw8TlmfW+kP/RS1PpdaVRGNIUCcMxiaaE4usiVLrO2OV6U9Xnrm 8nzkyPm7M2tJ232a9ig7Un/q6MlkxraC1VBxwaltjjQipelxwj2k9jL3EVwQhhV+ hxyRppWjyu0dJNJxzgFRiKuo/eVCceUllIe51/uf43JniGpare37zae+By3osS11 9El3aVdkQ2Uhyh4VP8VnVVPexb+nWhgSYHCDAxik+1CAnZZoAYaNucWbmRVd3UUA eCsnROyyIC++2kzqhzXfJiv+MshYU6dGIRcMPJRC6NmbRebunWigfI0jpJbq9Roa XYxVf88vD/tOJ4pccuZOYYzTinKTa9mnJA+DF2ac/3ksx3I62597gCj9/SEwcfyS d+aWxnD1PQFTDWjOndcW4onXa3bFwQEfUY6gJZQArFVC/XWkfDSEkV/HJodBUo8B Y4j6/ndk7E5f0CLu0eVAy9udGC2Ebm8tEazIWWi0ybd1x+2R6B1WqirctkUqwn4l tgwFts7Nj8fl3H/XwZUFz9mB+iWibkhjgsrscjIhtKUh96L++BX6dB7xcMO9NXWM pRbP82KrkDb30+pSx7X1JGYRR84nwel1cm8kks6ZzNJBF0/U+A41Brs6YlqCGoBE 8Y0Sstzz5CFJq0+shoc5rxXFTZWHZDpJJLJWD4jRLZHbGWR72Hlstr8Kj45KMUnN 11/H =1P0/ -END PGP SIGNATURE-
Re: unattended-upgrades by default
On Jan 06 2017, Santiago Vilawrote: > If we want to be the Universal OS, we can't assume that any time > (not chosen by the user) is ok to do an upgrade. If we want to be the Universal OS, we can't assume that users will explicitly trigger an install of security upgrades either. Nor can we assume that running without security updates is acceptable. What now? (Sorry for not being constructive, but these "Universal OS" arguments can really be used to argue for and against anything). Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Converting to dgit
On Jan 05 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: > On Thu, Jan 05, 2017 at 12:39:25PM -0800, Nikolaus Rath wrote: >> But, as far as I can tell, doing this work up-front is much easier: > > Yes, but you have to do it every single time you make changes that you > want to be able to push (i.e. more than once per upload). What do you mean with "it"? You don't have to resolve any conflicts unless you update to a new upstream that conflicts with your patches, or unless you change a patch in such a way that it conflicts with a different patch. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Converting to dgit
On Jan 05 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: > Dear Nikolaus, > > On Wed, Jan 04, 2017 at 09:44:14AM -0800, Nikolaus Rath wrote: >> No, that's a misunderstanding. >> >> "The information I need" is the Debian-specific modifications to the >> current upstream source, separated into logically independent patches. >> >> Having separate patches in debian/patches gives me this information very >> quickly. >> >> Having to run git log, and then to manually merge the the commits gives >> me the same information, but it is not "very quickly". >> >> >> This is the drawback of the single-debian-patch approach. The fact that >> the patches are available in individual Git commits no longer helps >> after a few merges. > > Thanks for your reply. I see what you mean. > > The difference between our approachs seems to be whether we do the > semantic work up front, when making an upload, or later, when extracting > information by means of `git log` and `git diff`. But, as far as I can tell, doing this work up-front is much easier: When using git-dpm or gbp-pq, the tool will present you with the conflicts separately for each Debian-modification that is being rebased. Resolving the conflicts is the only work you have to do. If you do the work later, then you start with a bunch of commits, any of which potentially contains parts of multiple Debian modifications. It is not clear how me how you would go about untangling them in a systematic way. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« signature.asc Description: PGP signature
Re: Feedback on 3.0 source format problems
On Jan 05 2017, Brian Maywrote: > Vincent Bernat writes: > >> There have been a lot of complaints about it. For me, it is a pain to >> use. Its integration with gbp is poor, it produces a messy history when >> you are working on your patches and I often run into problems with >> .debian/.git-dpm file it maintains (import a new upstream, make some >> changes, notice that somebody else also pushed a change, pull --rebase, >> everything is broken). Since we started using it, we opened a lot of bug >> reports and not a single one of them has been fixed. I think that nobody >> wants to work on it because it is an extremely fragile tool and the >> first one to try to fix it will inherit of all the problems to solve. > > It also has a number of bugs that are not getting fixed. Yeah, I think we heard before that git-dpm is not being maintained. I said it, Vincent said it in his reply, and now you are saying it again. No one is disputing the point. > Plus if conflicts occur because multiple people unexpectedly make > changes at the same time it (i.e. you can't push because somebody else > already pushed changes) can be a world of confusion trying to sort out > the mess. Yes, it is a mess. But I don't think it's any worse than having to resolve conflicts in debian/patches/, which is the equivalent problem when multiple people use gbp at the same time. > I have had to sort out the mess when the Debian package upload > did not match my git tree because another maintainer didn't correctly > merge in my changes. I don't understand... how does a Debian package upload affect any of the work on your git-dpm tree? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Feedback on 3.0 source format problems
On Jan 04 2017, Vincent Bernat <ber...@debian.org> wrote: > ❦ 4 janvier 2017 09:47 -0800, Nikolaus Rath <nikol...@rath.org> : > >>>>>> It's surprisingly awkward, and, at least for me, it turns out that >>>>>> externalizing my rebased branch as a patch series solves many of >>>>>> problems surprisingly well. All the other solutions I can think of >>>>>> require one or more things I don't really want to do: rebase the >>>>>> debian/master branch, not be able to run dpkg-buildpackage from the >>>>>> debian/master branch easily, or require that dpkg-buildpackage do >>>>>> more mucking about with source control than I want it to. >>>>> >>>>>I believe the git-dpm approach would give you everything you want. The >>>>>explanation on http://git-dpm.alioth.debian.org/ is pretty good. >>>>> >>>>>I personally think that technically git-dpm's approach is the best - >>>>>but >>>>>unfortunately the program itself is effectively unmaintained and >>>>>apparently/consequently not used by many people. >>>> >>>> The Debian Python Modules Team (DPMT) has about 1,000 packages with >>>> git-dpm repositories. While it took a bit of getting used to and >>>> there have been a few problems, overall I think it's worked very well. >>>> It's biggest problem is the lack of a maintainer. >>> >>> There have been a lot of complaints about it. For me, it is a pain to >>> use. Its integration with gbp is poor, >> >> Well, I think that is because it is mostly an *alternative* to >> gbp. Other than gbp dch (which I think should work fine), what features >> of gbp would you like to use with git-dpm? > > gbp import-orig --uscan (the whole import with git-dpm is flawed, there > are too many ways to fail, like a patch that cannot be rebased and the > pristine-tar branch is not updated, like the previous upstream was not > tagged because not released [and git-dpm only tags upstream when master > is tagged] and it fails in the middle of the process, gbp rollbacks when > there is a problem). I agree that's a mess. But I would much rather see the git-dpm import fixed than interoperability with gbp increased. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Feedback on 3.0 source format problems
On Jan 04 2017, Vincent Bernatwrote: > ❦ 4 janvier 2017 04:52 GMT, Scott Kitterman : > It's surprisingly awkward, and, at least for me, it turns out that externalizing my rebased branch as a patch series solves many of problems surprisingly well. All the other solutions I can think of require one or more things I don't really want to do: rebase the debian/master branch, not be able to run dpkg-buildpackage from the debian/master branch easily, or require that dpkg-buildpackage do more mucking about with source control than I want it to. >>> >>>I believe the git-dpm approach would give you everything you want. The >>>explanation on http://git-dpm.alioth.debian.org/ is pretty good. >>> >>>I personally think that technically git-dpm's approach is the best - >>>but >>>unfortunately the program itself is effectively unmaintained and >>>apparently/consequently not used by many people. >> >> The Debian Python Modules Team (DPMT) has about 1,000 packages with >> git-dpm repositories. While it took a bit of getting used to and >> there have been a few problems, overall I think it's worked very well. >> It's biggest problem is the lack of a maintainer. > > There have been a lot of complaints about it. For me, it is a pain to > use. Its integration with gbp is poor, Well, I think that is because it is mostly an *alternative* to gbp. Other than gbp dch (which I think should work fine), what features of gbp would you like to use with git-dpm? > Since we started using it, we opened a lot of bug reports and not a > single one of them has been fixed. I think that nobody wants to work > on it because it is an extremely fragile tool and the first one to try > to fix it will inherit of all the problems to solve. Yes, I think that falls under "lack of a maintainer". > > Isn't "gbp pq" a correct execution of the same principles? No, absolutely not. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Converting to dgit
On Jan 04 2017, Sean Whittonwrote: >> > I also read Russ's e-mail, but I'm not yet convinced that powerful tools >> > like `git diff` and `git log` won't be able to give you the information >> > you need pretty quickly. >> >> Can you give an example? Eg if I have to Debian patched that both >> produced merge conflicts at some point, how do I disentangle them into >> two separate patches with just git log and git diff? > > Use the `git log` command I gave previously, and cherry-pick the commits > you want. Thanks to the merges, they won't apply cleanly, and you'll > have to manually resolve the cherry-picks. However, as evidenced by > Russ's examples, manual resolution will always be required in these > sorts of cases, and git minimises the amount of it you have to do. No, that's a misunderstanding. "The information I need" is the Debian-specific modifications to the current upstream source, separated into logically independent patches. Having separate patches in debian/patches gives me this information very quickly. Having to run git log, and then to manually merge the the commits gives me the same information, but it is not "very quickly". This is the drawback of the single-debian-patch approach. The fact that the patches are available in individual Git commits no longer helps after a few merges. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Converting to dgit
On Jan 03 2017, Russ Allbery <r...@debian.org> wrote: > Nikolaus Rath <nikol...@rath.org> writes: > >> The thing that's delivered to users in 99% of the cases is the binary >> package. In the (comparatively) rare cases where the user is retrieving >> the source, I am not convinced that most of these users truly prefer a >> Debian-specific source package with patches in debian/patches over a >> standard Git repository with patches as commits. > > Speaking as a Debian user who frequently has to apply local patches or > produce local versions of Debian packages for my job (usually weird > backports or bizarre local requirements), I cannot express to you how much > I prefer a Debian source package with patches in debian/patches over a Git > repository with patches as commits. Yeah, but I was not talking about the strength of preferences but the number of users that have them :-). Also, you happen to be a Debian developer and are therefore already familiar with the Debian source format... Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Feedback on 3.0 source format problems
On Jan 04 2017, Paul Wisewrote: > On Mon, Jan 2, 2017 at 1:21 AM, Guillem Jover wrote: > >> I'm interested in what things people still find so off-putting to the >> point of not wanting to use the new 3.0 source formats. > > I've been reading this thread and keep being reminded of our > discussion on #debian-dpkg a while ago. > > I think most of the complaints about Debian source package formats are > rooted in a design mistake made early on. The debian/ directory. The > debian/ dir controls the upstream source but is in a subdirectory of > the upstream source. The directory hierarchy is an inverse of the > relationship between its parts. The debian/patches/ dir is another > layering violation on top of that. That is a point I very much agree with in principle. But I am not sure if a package structure like mypkg/upstream/* mypkg/debian/* mypkg/patches/* (?) would have any *practical* benefits over the current situation, because this transformation could be trivially automated in either direction. Or did you have something else in mind? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Feedback on 3.0 source format problems
On Jan 03 2017, Russ Allberywrote: > It's surprisingly awkward, and, at least for me, it turns out that > externalizing my rebased branch as a patch series solves many of these > problems surprisingly well. All the other solutions I can think of > require one or more things I don't really want to do: rebase the > debian/master branch, not be able to run dpkg-buildpackage from the > debian/master branch easily, or require that dpkg-buildpackage do much > more mucking about with source control than I want it to. I believe the git-dpm approach would give you everything you want. The explanation on http://git-dpm.alioth.debian.org/ is pretty good. I personally think that technically git-dpm's approach is the best - but unfortunately the program itself is effectively unmaintained and apparently/consequently not used by many people. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: "not authorised" doing various desktoppy things
On Jan 03 2017, Ian Jacksonwrote: > Recently, my nm-applet can no longer control my network-manager > daemon. I get a message saying[1]: > > "org.freedesktop.NetworkManager.network-control-request failed: not > authorized" > > I think this is related to a similar problem in *-power-manager, > #848623. > > I am running: > * sysvinit > * lightdm > * systemd-logind > * vtwm > * my own xsession script > I thought I was running systemd-shim but I don't appear to be. > > Can someone please help explain to me how these things are supposed to > work ? I can't explain, but just a datapoint, the following similar stack works fine: * systemd * lightdm * i3 (executed via custom .xsession) Maybe that helps to find the crucial difference. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Converting to dgit
On Jan 04 2017, Scott Kittermanwrote: >>Curating a patch series is only 5% slower than commiting directly to >>the Git repository to me. I just have to remember to gbp pq import >>before making new changes, gbp pq export when I'm done, and once in a >>great while I have to do a small bit of rebasing to merge changes back >>into other patches. It's quite easy for someone who is very familiar >>with Git, using good tools. That 5% would be even less if I did it >>more often. >> >>I'm unconvinced that any of that work would really be avoided via other >>mechanisms. The most time-consuming part is rebasing and squashing >>related changes together into one coherent diff, but that's going to be >>just as hard with any of these tools since the hard work is semantic >>and >>requires thought, not just repository manipulation. > > And the thing that gets source delivered to users is the source > package, not a git repository. A proper set of patches is far more > understandable than an undifferentiated pile of diff. The thing that's delivered to users in 99% of the cases is the binary package. In the (comparatively) rare cases where the user is retrieving the source, I am not convinced that most of these users truly prefer a Debian-specific source package with patches in debian/patches over a standard Git repository with patches as commits. > Sometimes I feel like people lose track of the fact that the VCS is a > means to an end and not the end target of the work we're doing. I think it's rather that people have different views of what the desired end is. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Converting to dgit
On Jan 03 2017, Russ Allbery <r...@debian.org> wrote: > Sean Whitton <spwhit...@spwhitton.name> writes: >> On Tue, Jan 03, 2017 at 10:36:22AM -0800, Nikolaus Rath wrote: > >>> I still haven't really made up my mind if I want to use git-maint-merge >>> or git-dpm. Russ recently raised a valid point with the Debian >>> modifications over-time becoming all tangled up and impossible to >>> separate. > >> I also read Russ's e-mail, but I'm not yet convinced that powerful tools >> like `git diff` and `git log` won't be able to give you the information >> you need pretty quickly. It might take a little time to craft the right >> command, but that is easily outweighed by the time saved curating a >> patch series. > > Curating a patch series is only 5% slower than commiting directly to the > Git repository to me. I just have to remember to gbp pq import before > making new changes, gbp pq export when I'm done, and once in a great while > I have to do a small bit of rebasing to merge changes back into other > patches. It's quite easy for someone who is very familiar with Git, using > good tools. That 5% would be even less if I did it more often. When talking about percentages, I think it's worth keeping in mind the 1000% longer that it takes to comprehend a diff of two patches-unapplied trees (as gbp produces them) over a diff of two patches-applied trees (as git-dpm and dgit with maint-merge workflow produce). I don't understand how gbp became so much more popular than git-dpm. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Converting to dgit
On Jan 03 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: > On Tue, Jan 03, 2017 at 10:36:22AM -0800, Nikolaus Rath wrote: >> I still haven't really made up my mind if I want to use git-maint-merge >> or git-dpm. Russ recently raised a valid point with the Debian >> modifications over-time becoming all tangled up and impossible to >> separate. > > I also read Russ's e-mail, but I'm not yet convinced that powerful tools > like `git diff` and `git log` won't be able to give you the information > you need pretty quickly. Can you give an example? Eg if I have to Debian patched that both produced merge conflicts at some point, how do I disentangle them into two separate patches with just git log and git diff? > It might take a little time to craft the right > command, but that is easily outweighed by the time saved curating a > patch series. Well - that is obviously very much dependent on the git-fu of the person doing the work. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Feedback on 3.0 source format problems
On Jan 03 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: > Hello, > > On Tue, Jan 03, 2017 at 10:39:33AM -0800, Nikolaus Rath wrote: >> > >> > git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian' >> >> Yes, but that's not as useful as what git-debcherry produces. >> >> For example, if you get a merge conflict when rebasing, the above >> incantation will list two commits: the original debian commit and the >> merge commit. git-debcherry, on the other hand, will synthesize one >> patch, consisting of the original Debian commit, but modified to include >> the *relevant parts* of the merge commit. > > That's a good point. In this context, `git debcherry` is a tool to > filter and neaten a git history. However, it inserts another step > between upstream, and powerful tools like git-cherry-pick and > git-bisect. Upstream now has to know that Debian has orig.tars and > various ways of representing changes to them. > > If I were a busy upstream, I would much rather `git fetch` my Debian > maintainer's branches, and then immediately set to work cherry-picking > and bisecting. I don't need any Debian-specific knowledge, except that > which is relevant to the bug I'm trying to fix -- I don't need to know > what an orig.tar is. This is worth having to look at a few merge > commits. Are there really upstreams that do that? I'd expect that the primary consumer of Debian patches are other distributions, downstreams, and users. I'd think that anything that's relevant for upstream development is forwarded to upstream by the maintainer in whatever format upstream prefers. This requires extra time, but I would be surprised to hear if there are maintainers that have sufficient time to create patches that are suitable for upstream, but don't have the little extra time to send them upstream. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Feedback on 3.0 source format problems
On Jan 03 2017, Nikolaus Rath <nikol...@rath.org> wrote: > On Jan 03 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: >> Hello Russ, >> >> On Mon, Jan 02, 2017 at 09:29:24AM -0800, Russ Allbery wrote: >>> Furthermore, it forces a rebased, clean representation of the patches, >>> which I for one hugely prefer to the mess that you get if someone was >>> packaging in Git and just randomly commits things directly to the >>> packaging branch intermixed with merges from upstream. A few releases >>> done that way will leave you almost completely unable to extract a rebased >>> patch set against the current upstream source. (I have made this mistake >>> so many times with my own packages.) >> >> Aside from `git debcherry`, which was already mentioned, git itself can >> get you this information. For example: >> >> git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian' >> >> This will get you all commits which touched the upstream source that >> have not been merged upstream. There can be as many merge commits as >> you like in between. > > Yes, but that's not as useful as what git-debcherry produces. > > For example, if you get a merge conflict when rebasing, the above [...] This should of course have been "...merge conflict when merging in a new upstream version". Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« signature.asc Description: PGP signature
Re: Feedback on 3.0 source format problems
On Jan 03 2017, Russ Allbery <r...@debian.org> wrote: > Nikolaus Rath <nikol...@rath.org> writes: > >> For example, if you get a merge conflict when rebasing, the above >> incantation will list two commits: the original debian commit and the >> merge commit. git-debcherry, on the other hand, will synthesize one >> patch, consisting of the original Debian commit, but modified to include >> the *relevant parts* of the merge commit. > > Okay, yes, that sounds pretty awesome. That may entirely remove my > concerns about keeping the patches always rebased. Well, as I said in my other mail: the big drawback is that even with a small test tree running git-debcherry is already slow enough for the user to ponder the implications of it being a 300 line bash script... Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«
Re: Feedback on 3.0 source format problems
On Jan 03 2017, Sean Whittonwrote: > Hello Russ, > > On Mon, Jan 02, 2017 at 09:29:24AM -0800, Russ Allbery wrote: >> Furthermore, it forces a rebased, clean representation of the patches, >> which I for one hugely prefer to the mess that you get if someone was >> packaging in Git and just randomly commits things directly to the >> packaging branch intermixed with merges from upstream. A few releases >> done that way will leave you almost completely unable to extract a rebased >> patch set against the current upstream source. (I have made this mistake >> so many times with my own packages.) > > Aside from `git debcherry`, which was already mentioned, git itself can > get you this information. For example: > > git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian' > > This will get you all commits which touched the upstream source that > have not been merged upstream. There can be as many merge commits as > you like in between. Yes, but that's not as useful as what git-debcherry produces. For example, if you get a merge conflict when rebasing, the above incantation will list two commits: the original debian commit and the merge commit. git-debcherry, on the other hand, will synthesize one patch, consisting of the original Debian commit, but modified to include the *relevant parts* of the merge commit. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« signature.asc Description: PGP signature