Request to join the team
Dear all, some of you may have noticed my e-mail about approaching the recent "Attempt to unlock mutex that was not locked"-issue that several (Python) applications encounter [1]. Anyways, after several years of using Debian --and always returning from straying toward derived distros-- I would like to start giving something back and start packaging myself. My current interest lies with RabbitVCS [2] and especially its client for the filemanager "nemo". Since there already exists some package for Linux Mint, I consider this task to be a useful exercise for focusing on the process of packaging. Furthermore, I am in touch with the upstream developers of RabbitVCS and would like to strengthen the cooperation with this project for the good of both Debian and the project itself. Vincent offered me to sponsor a nemo-rabbitvcs package. Please add me to Alioth group for write access to the svn so that I can go ahead and upload. Regards Torsten [1] https://lists.debian.org/debian-python/2014/10/msg4.html [2] http://www.rabbitvcs.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/543b0bd8.8010...@matbox.de
Re: DPMT membership request for randall-guest
On 03/01/17 23:21, Piotr Ożarowski wrote: > [Lee Garrett, 2016-12-23] >> I would like to join the DPMT. I plan on working on modules mainly used for >> Ansible (I'm currently updating pywinrm). I have read and accept the DPMT >> policy found at [1]. >> >> My Alioth account is 'randall-guest'. > > welcome :) > > (sorry for the delay) > Thanks a bunch! Pushing the pywinrm changes now.
Re: [DPMT] radical changes: automation, carrot and stick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-02 18:12, Nikolaus Rath wrote: > On Oct 02 2015, Piotr Ożarowski wrote: >> I think that the main problem of our team is that we have over >> 300 members and only few people contribute to packages they >> didn't inject to the repo (some people do not care even about >> those). > > I always assumed that it was generally preferred to have Python > packages be maintained in the Python team, even if the maintainer > has little interest or time in contributing to other Python > packages. > > Did I get the wrong impression? this was also my impression and the main reason why i joined the team. i brought in 3 packages needed as a dependency for some other package maintained by pkg-multimedia; the 3 modules are general purpose, so it makes little sense to maintain them in pkg-multimedia - DPMT seemed to be the right place. as others have mentioned, i also set DPMT as "maintainer", in order to not keep anybody from contributing (and not because I wanted to unload the packaging burden on the team). fgmasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWEkhCAAoJELZQGcR/ejb41YgP/3n5Ji/EUuzUhHI3+MRHMa6I etTAP3KJkKtKipKOdgnmUDn4XLLM+aM4M3V2Y1O/FOu+R/dJc/+ynnGZS47twLJm edjFNSRhjiLDGTk4Io0m7jgV80YCr+5MfCe2/dnrIE4mEM4z69Cjo6cR+G2adz8f EhoScamtuhkyJ26fH3OMgBTWJLMwP1zUilhySSCxvRf8U7mSBHH2ugNdu7ph7t1N EL4e2ySvV0JNA2Pd6PQG/6vL8/EvMpzLXBBeLAAAm63kT2UhLryb5yTABFIxyz3d odn+hVFHhJuoTRxYiH6apTr/RxX1za7lYAY7aXcsIt1h/jL3uy6L4vm3XtJReAaR 6FWqVjoJdHzn/NUID3bgHTv4L2csolKI+TPcnvpzR0VYMOtcNfIVhkKEthTP0ybC D7iPKtqtK/idM34Oc7cZnF0Abk4LWr9kakgt816mNsm4/GI9e1ipqwyQNx/21eF0 cBVfjX1+xQohRP+7Lw58+RTVHPUp05Z5ld8qD0XrNwMWjF3HiASo65HVUVVy0cph lYwPgG8mk46a+Bsxy4Kjvi4LAY33MeUphbsGfgqMA11eUF9zHtbPIBetxh1+Ip46 geU06DiPsX4CE70WLnAZoQQujANG/haSI1/ULF19pouC7L7sLN711PuQ4WvEh5M6 foeUUpjt2NzuFvR2KCbF =n8eR -END PGP SIGNATURE-
Re: Git migration schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-04 23:06, Stefano Rivera wrote: > Hi Sandro (2015.10.04_21:31:07_+0200) >> sorry, i forgot to ask another question: how will the packages >> already maintained in git be handled? > > Up to their maintainers (assuming they're following team > standards). If people only have one git package, for testing, each, > then this shouldn't be an issue :) what does this mean in practice? what if people have more than one git package, not only for "testing" purposes? fgmd IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWEkviAAoJELZQGcR/ejb4zdkP/2o10WRkf8ErOTloLo2myUb4 BoL3KX2xLKTQ4TZZfXlXKdRig2T9lLLIHZGsDDHmqRO9lrsCe8AbNQBLYvBtgCtI VkJ/83CGGS8d3qiVGs5neeHl281aWyO4fDImyntHDxqRAa3zaIbZ3PeH6hvt3Mu/ Wk3KGBZuQ66yFBDMjBMATbhFDB0H/03wDA5f3pU7RJuAwdn9PjZfmSgJ4giHZ8cS HhIIhxy+Kka8VkmpUT6xMx/LFEIviUHUi9y2IqMpgzGFcXNH/xRIVEWA5pRcrHzS On5kM+sPwFwaAoy0A/OWyxzOcsPmdQV3lkbvYixH4FeWDX6kqpzynryCABh3eQ31 6MScD4SXtu0zpjlz7FvFhYB/cAkXJduWBwgfnHp4ikZopTlHEKD6gVV2rDBVUgXn Ne5zlJfOBXEED4RWO4pWRM79qRjofjIjbNcSKHyDe5612C2wKBrUyFnYDTMahRbE 8+BbQJANKYhPGmX92TGO3gTHEMsDwGZ4sJmFuCGFwA4xfGtniPae+ciseUR/dPIC uBlEmlAwVzKn0cXpJSSEuhxcQ5fvjWPG5dkFrj4NduMJ5VB2bH6aDuLqs4OgMKs4 wdLOTXtxvELBZ98hHlMsVsipeeALyl8ZxygNv57OXlbcwvk1AyGkgBiiGZHYqnQ2 BvSu38QmpsCRz7YWO+N8 =83EB -END PGP SIGNATURE-
Re: [DPMT] radical changes: automation, carrot and stick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-02 10:30, Piotr Ożarowski wrote: > it's 3 months to contribute to other packages (the ones where > you're not listed in Maintainer). hmm. if i - hypthotically, because i really currently do not - cared a so much about e.g. 30 DPMT packages¹ that i have added myself to the Uploaders and which have active upstreams and thus require a fair amount of regular maintainance work, then i would need to do to *another* contribution each month in order to not get kicked out of the team? sounds a bit like penalizing the wrong ones to me. fgamsdr IOhannes ¹ just made up numbers; assuming only a single real person is in "Uploaders/Maintainers"; and that the 16 team members listed in https://wiki.debian.org/Teams/PythonModulesTeam are the only really active ones; and that all other 300 members only injected a single package into the current 779 ones; gives the active members about 30 packages each on average. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWElJMAAoJELZQGcR/ejb4vwsP/0xbLTgajbmg7AyJzeStWulR 5ggQQx1L853ER69sqR9Kfmv9+cBo2ijl39m+libY8o20QUyglM4+/QKNYA2mto5X izcPA+ZD0RFePA5z9yCHZNBUQnLpNX9C8+N0qAWAdeVO7fYUbkr3plBvaP+CvdLc Fv8OQ0t5dNYnmnMV3T6BYmCxqJMido0FM78n8xhE+A1XSs+saBjA3JlXyyNxy7MC V3K0/SYtV0db4rhboTrrGRaDv6ZQMIlL+czEWfDgwBqnWVtK3AdZSLZdJRF9JeN8 CWjv4CjEADeI2vtt38dYvj8GVlm5G6b528bP/ABrbCVPm4DO18zjpnIxILFPnGcg 0C07nWtcnceRW2mcR/tFERTTtWfa8l77cpf4VknKb9dCKfiHn9buB1YLFfWKi9wm l8ZvyTg74apMpX583bdOvlAkzVp+nGv7TYUxxdntKj2/H/Phwz1cbb68vQ5onhNP B7JZMlJPao3PrEqKnv6ftBR8AO1/WD6aEeJRlBBHQjONCSeQZuERMv8CWWSoUt2J Zy0Ak4TuGvzsuik6nQhszVV48G/h9vlWJPeHhfddJPrQPLhA+u9zKqLumB2QipoD 5lb5BcPEUzszvi3Lw56vSTkMTqJ88GE+zC2GeILFP5aS+uRJ9Yihcd0D1ZzXoLoV MjEfLMt/EDZmmzQTO22p =6kim -END PGP SIGNATURE-
Re: Git migration schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-05 23:24, Barry Warsaw wrote: > On Oct 05, 2015, at 10:36 PM, Stefano Rivera wrote: > >> How about: We move away existing repositories, and put the >> migrated ones in the /packages/ path. If people have existing >> repositories, that they'd prefer to use, they can move the >> migrated ones out the way, and theirs back. But they have to opt >> in to this. sounds good. in my case, i have (to admit that i have) 3(!) git repos for which there is no svn repo at all. so there won't be any clash during migration, and moving them away would not be strictly necessary. for the sake of simplicity, i guess that they probably should be moved away in any case. >> This means some (work done on pre-migration git packaging) >> history gets temporarily "lost". the cue point here is "temporarily". > But ensures that everything is the same layout. And >> that any deviation was intentional, not accidental. > > I think it would be okay. It's only a minor inconvenience, > although the git remotes of the packages that get moved would also > be temporarily incorrect. +1 i don't know how long you expect the migration to run; but even though there are *many* repopsitories to migrate i don't think that it will last longer than...2 days? fgmasdr IOhannes PS: have i told you already how excited i am that this is finally happening! big thanks for all the preparation work ♥ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWE3iwAAoJELZQGcR/ejb431sP/27eSQpArjlAk27zGlXDZiMy 4mF4LnYgBXMOORnReSnTRqIksr3CC9ZImM3XUbDEcloQaGqFZln18MZeMRFlquKK 7KS95nfSP49D8+aPhSlAfPuSMcFdMg0Nu0FX534HCJ/qXPLT67dZA+H1BH3kEGmg knNaV5etaUCXU4QaiAThZMTUbzs30nqduMBqU5FtqJhubPwTEJ0COplDenglRtHx DJSQSgC3KPiwy/ehOdR4kttojGQ7yjXiPIa8rRS9RmSGdYOwA5QPx+eQNnDwD1w+ vSMKAuUlKKPFysABus0VVMdhP+U88J7PieWH299HfiWnuxwWrYQnXD5O6pfb5+oE ++WhVMq2s/jNT4CqnyCQCaLW3EM5vrK7pl7TujynC3IsZxzeHXkZMfojsOjMCfYP Sfn/lTak1cYFgGU6+LFhaHzWIFWULE/TiE1zQePGbAcMGkLqGSmbT/H/ma3fFGnG ghiVqrX5FYvi3BkUUeDtLHYgsS1oGR3hHYrA6rEVl/4jxg4LT03DI7nSK0yQFyJW JgKVvTYrzdoFyzCASoEVuwN9i5kKN72QxfeZa/q3WP5E3+ZcWGcyadQsnwDke0gh Q1p5lSeKv3vaNMvQFyJmSSb1cCcMGpb5MViFJ41rdGEQdNz2ZRgvkQsXDmnl859q cLVzk4YvL1annB/4UdlD =/CdQ -END PGP SIGNATURE-
Re: [DPMT] radical changes: automation, carrot and stick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-07 14:18, Piotr Ożarowski wrote: > I no longer think requiring contribution (the 3 months thing) is a > good idea for DPMT (might be for a new team). > > I assume you all like other ideas, like no team in Maintainer, > right? if that's the new policy to be, i'm all happy with it. fgks IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWFRA4AAoJELZQGcR/ejb4dswP/1/xeEirq5bDspvNRKKZE935 UOu5PSQgpxMVRUJB04FwtwKfFA0eaHSHlIaHO/X7cZ2TVRTQZgxD2hMI4CiSVx04 VDtf7rp7L4DsQtxv8j6ujI60Tu2a3iatedbfSeKdUKOGwakjL8CGG+/QNxGWZzkL U7VnBOe3lQqDMd9mZoo/La9wguvkFzia72g/QtazORhRuKw5+6h6j2ZFUpac5278 35mbQYrnj4IlSUKinMXj3QNzuLWsVJR4RIpaYLp46DvknDBoW86fDKhfBcl7vFgT HkZYqAHxw3E1hiyTFBPfkQaUWetk8oBoURVjknH9c/pPMw8ig+ALLvbGjqHlr2a3 AGjSPAJ5/C1UDyyaP2jFtQKYQiUsrQp+xeX2zYvWJc6Z+hg/zKRs/qfFVgNaJS8b GR/qs4+aFKH2hifFfMga1PKMRgIOpo4kqo245ujnjk9A9Uze8/v46lZOOMTeZmED v0UInsg52B9/r0qJtle9o518qO+kSQR9ogM42yamG2RUleJhrM7UOjDCvL03JVBl POpfQGeo2DPJjhLhuDfKHTggjDUZuk18bBUmF539ggOf45zaCnW57DSQDbGAL1N+ Jpse9rxmECI6hR3Wb/zsbu9HrnlrJykagN1Eje5SsPck//lm4gUQKuFZPs+R0IqQ NHCtEkEmqaOA/AC5FL3i =d+wY -END PGP SIGNATURE-
Re: packages missing from https://anonscm.debian.org/cgit/python-modules/packages/
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-12 08:56, Brian May wrote: > Hello, > > Why are packages missing from anonscm.debian.org which are on > git.debian.org? > > e.g. > > https://anonscm.debian.org/cgit/python-modules/packages/django-model-u tils.git > > > https://anonscm.debian.org/cgit/python-modules/packages/django-xmlrpc. git > > I note these packages don't have the required VCS-* headers, > however I expected to be able to see the above URLs to confirm I > got the correct link before fixing it. afaict, these files are missing because the .git/config file is not readable by the webserver: $ ls -l django-xmlrpc.git/config django-tables.git/config - -rwxrwxr-x+ 1 stefanor scm_python-modules [...] django-tables.git/config - -rw-rw+ 1 bam scm_python-modules [...] django-xmlrpc.git/config $ while i don't think that the executable bit is needed, the readable bit probably is and no, i don't know enough about cgit to know *why* it actually requires read access. (i also don't know why the repositories that *I* (umlaeute) created are owned by stefanor, whereas the repository that you (bam) created are owned by yourself) gsdft IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWG4xyAAoJELZQGcR/ejb4HrMP/iE/NgavCeuOMb2j23J0o7av B5gSDMf9cDUW6LHGgbWhoCFlRGPrOSpXF6uhnaL1zf9FilnCeALiE4C6POFexpJP WU+SAMTxoXW74rPDWIMVXQEJEIp0eB5PDgQlKylMnBPFV+NFgVuH0PeNYLrfc7yU lA2oCbtCidSrk1N9OZsUs3Eo7q85+Cv69qfm7SxAsNqArC5wKJUvTGEjgeSQwT8j 4Yf9KTkD4d9ggQKRcxf0VLDxtBINXHOnpYEoVtevDABsG8Gth6o/x8zxAgtFOwjV mOJKk/VUgOEOxV0Qpywr20qfdp7/sa81gRbpjYXE8NXAuqgX5ifLVy3vEEMy7GBt TTbB3W4D2BHW3xIR7jZPGSiQZa95/TRU6VelibmiRUyY20SEL16rF/Iz5CXzDQ9y wvKpuiEKQlBao8UWVno/LH0hbqptd9+DScmEaIhK+d5W1rixxjqVvitNY3sLES5J Mldxbqy1Xc6DkaGGJ2p+2ft1DgNhQJj71FF3zu4C6kxws+n/Ry7LUpNa1vztWEgp q0BZNrUTrRoxC6zvu0PSM2FBxlXlQT2wJZT9S9K51LEApfIgtI0EiC+1GrZzyozB l+uzQxfQ0yjKRwlMuogIBGNO6YnH3oSPibZA9E7+QKqL0KN4ifSwQdaOSCr0tQQU T0P9WM7fGP+5XXyN+/ZW =fDfT -END PGP SIGNATURE-
git instead of svn in policy (was Re: team vs individual as maintainer)
On 10/16/2015 11:53 PM, Piotr Ożarowski wrote: > (it still clearly states we use SVN only, though!) since you have already mentioned this a few times: how about changing the policy then, to clearly state that we use GIT only? as you haven't done that yet, i guess there is some catch; but since i only joined the team a few months ago i might have missed that. (might be that the catch is simply one of priviliges to modify the policy) mdsar IOhannes signature.asc Description: OpenPGP digital signature
Re: Python Policy
thanks a lot for preparing all this. On 10/20/2015 10:53 PM, Barry Warsaw wrote: > +DPMT requires upstream tarballs; releases cannot be made from upstream git > +repositories directly. This is because PyPI contains upstream tarballs, and > +tarballs are what we upload to the Debian archive. i find the justification a bit weird: "no releases can be made from upstream git because some upstreams use tarballs"? in any case, i don't think that there is actually a need for the policy to justify the decision to require tarballs (let's put that in the wiki for those interested). gfmsadr IOhannes signature.asc Description: OpenPGP digital signature
Re: Python Policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-21 02:17, Ben Finney wrote: > "IOhannes m zmölnig (Debian/GNU)" writes: > >> thanks a lot for preparing all this. >> >> On 10/20/2015 10:53 PM, Barry Warsaw wrote: >>> +DPMT requires upstream tarballs; releases cannot be made from >>> upstream git +repositories directly. This is because PyPI >>> contains upstream tarballs, and +tarballs are what we upload to >>> the Debian archive. >> >> i find the justification a bit weird: "no releases can be made >> from upstream git because some upstreams use tarballs"? > > Yes, that is weird, and it's not what you quoted. I don't know how > you get that meaning from the text you quoted it's not what i quoted, but it's what i read in the quote. it says "releases cannot be made from upstream git repositories directly. This is because PyPI contains upstream tarballs [...]". i fail to see what this "this" in the second sentence refers to if it was not for the statement in the first sentence. thus creating a cause-effect statement "pypi contains upstream tarballs -> releases cannot be made from upstream git". i think this logic is plain wrong. for one thing, pypi - while being the most prominent source - is probably *not* the only source for python modules. (that's why my interpretation says "some upstreams"). furthermore, pypi is *not* upstream itself. it's a distribution channel. an upstream (author) might as well do releases using git-tags on github in addition to uploading the tarballs to pypi. in this case, releases *can* (technically) be made from git tags. it also says "[...] and tarballs are what we upload to the Debian archive.". which is true, but it's true for any Debian package (even those that use upstream git or zip). so what's the point? so: if my upstream does not use pypi (or i'm not aware of upstream using pypi), does "tarballs required" policy still apply to me? i think yes (but then i don't understand why there's a rationale if it does not apply) > This is because PyPI contains upstream tarballs, and tarballs are > what we upload to the Debian archive. > >> in any case, i don't think that there is actually a need for the >> policy to justify the decision to require tarballs (let's put >> that in the wiki for those interested). > > On the contrary, I think the Policy document should document the > rationale for contingent decisions like this. When it is > inevitably discussed again in the future, it is always better to > know the intent of the authors. that's why i said that the rationale should be documented in the wiki (as opposed to the policy). the policy did not contain a rationale why we chose svn. the policy doesn't contain a rationale why we chose git. (well, the decision for git will probably go unquestioned, but:) the policy doesn't contain a rationale why we chose git-dpm (not even a shallow one as "we need *a single* standard", let alone one that is based on actual technical merits). TL;DR i am not a native speaker. so i might get things wrong. but i'm not the only non-native English speaker in Debian. therefore, i *strongly* suggest that the policy should be written in a style that non-natives can understand it - without getting the impression that considerable parts of the policy are only relevant for specific setups (and not for them). mfgsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWJ0P+AAoJELZQGcR/ejb4XtsQAIKQXQZxlzSgJF6zOi6NTgX8 Yq/y3mgvOZkWwsgOSqZKFVEnSsPQdBDptywSqV1Fm1Dy/6MS68jy03JRP+zWBUV1 n0Hr2NiMYzQxGBOhmIIrR7WtdEvxXhOs1Z1A3Nv5Tq4lJYX0XBPfAxOus/jdii6g w84EIACtR6unvhGEcbABx8jNAecX73azN0Uni0S4BCYpczHgSEghulBu5FK4FT1M 22ZKA40S9kvq4naLg43A/hGjXsLvd//6Bfn5Cufu3YaAXugSaqIz16cNlzTKZDRq F3NUtUtLD6RdjkCtzpAIo4WoUMZcvprXh34EVctj7uJ+tSYDi17J1dUO8HOTq3UI EOEDFOscQvQZ+6h//89W6QjDdK8wW2C4jnspOQx6ZD4dJKa6r0qCKvBgx/E2fnmX rb568XMXErGcjdLRAAyJj50UYud3uqNdRvjg6mrgQdRPghSFAQXz4jjx9W0y2bh8 MrC7BaaLA9nS3XdSMVwQWGMQJ4Nn+LTrWtBhnjLAEee1pWg5x4wdamLAPGKCyWN2 NYHweYdcGuEAeoYr5T9tpEsnRZQo6kIE+jRKp0IX88JGLqdv1eyy+/gk+mYtSkTY Qie0dvzTUs4btwI3To1g2X6oCRaBMabm0sZ4/yLZBqpSC9NdrB3YAsBRX3xWMgEg 2DCyuPCVFKHWUp1Pz++T =sKPF -END PGP SIGNATURE-
Re: Python Policy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-10-20 22:53, Barry Warsaw wrote:
> +Any·Debian·developer·who·wishes·to·integrate·his·packages·in·the·team
·can·do
>
>
+so·without·requesting·access·(as·the·repository·is·writable·by·all·DD).
·If·one
> wants·to·be·more·involved·in·the·team,·we·still·recommend·requesting_·
access
that's
>
something else i wonder whether we shouldn't drop it, as i
don't quite understand why it has to be in the policy.
i *think* it's supposed to urge DDs into becoming team members, even
though they can ("are able to") already write to the repos without
asking for permissions.
but in fact for me it conveys the complete opposite: DDs can ("are
welcome to") add stuff to the repo, and they should only "request" if
they want to commit themselves to the team.
...which is probably a (not so) good loophole for any DD who just want
their python packages under the DMPT umbrella without getting too
involved (e.g. no sponsoring, maybe not even obey the the policy,...) :-
(
fgmasdr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCAAGBQJWKKg0AAoJELZQGcR/ejb4GjAP/iTM+RxdQhuS9UqqnsMfLp36
f8BRMHoNm8CBnDBoWoYHGnSc3VshnL2Tzea2aSawW3KKcvf0b4/Hvta3gcqg/OHt
QHeNEJX+PPgJqo/5m+k+jbdB4QeIy5zGwcCxcLnhCdY53x1bCrQMytaMYZy3K+Qy
8eO/wRmKJHBlnoH1DF7KIBwj78bS/rmcHcCw16YzN2RuQQwpBaPwz9HmlkAK4TY/
QqjS9s7Hm80zD5VdzYsIluBoLgaIrbPfaL81YGpY98I56nVGcWd1FhP5BaRlmxyV
LDRPH7CT+AfEmUqAVKnuUWkEAKKz8vzA2imE+QTlrfZ3GAXZUgTw9FEazO9F4Asq
j+b6nSlwyt+B5iLjbjdtMtNTaZdA/OD4jwYt8DfT/aLDrgKcL1byjGjmIzSGIrS+
tX44kJSqN7Bo84Ax7rXRVfC0iAqXQiu/yNQb11dQhXjPGZuREKEXz2WS4zxM7e8Z
GAi3MT41s2zqtSxyU2u8tsV02YreI4shjPpw2PHE11xvy17rFXn678QxXS9iCxr0
tWRLWxLhxHD41UDip+Ir01UWF7LATMpBKVt34ZPUukytLCf109vmEzcX3EoiYXIT
JuYa11KYfGsHI5VkHt3JhraNfprSe/TlGQ+1V899rijpkrftlFgp2iBUi21yPxGB
ET79wfUpZkH3r5u8dHb8
=aAVW
-END PGP SIGNATURE-
Re: Python Policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-20 22:53, Barry Warsaw wrote: > +Any·Debian·developer·who·wishes·to·integrate·his·packages·in·the·team ·can·do > > +so·without·requesting·access·(as·the·repository·is·writable·by·all·DD). ·If·one > wants·to·be·more·involved·in·the·team,·we·still·recommend·requesting_· access > > - -so·that·he·appears·in·the·public·member·list·displayed·on·Alioth's·proj ect·page. > +so·that·they·appear·in·the·public·member·list·displayed·on·Alioth's·p roject > > thanks for gender neutral wording. however, you missed one "his" in the first sentence (probably more in other paragraphs). gamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWKKjwAAoJELZQGcR/ejb4Qj0P/0E3cTOaFvxmot2l8yGS2nyC O2ucectYPcIPWkXscX35hm7cA6tttWbfkldifwxVVDXo2XLB8ByI1hdCzyQeEJgI HRmJAkmCyi6e1FG6q5QgGKQCqBWz81BTIABVzfqMR3g5fL7OSqPTmA2VXmeVxUOI e05ImbOg8fP4kTILfI+6peeiLMZ90sihrOFIO4aYUhkBKGLyGoZz6OMrd7OijwRJ AEBAJ0MYPPqng5qYsMsVBxhjivBpjPfy8/5oseRdd0wvm6estsn3Zcfk7msymSAf WU8DvcvWJ0GmWyGae87dLHb5olWhRH3jrKTFDTPHyiMT61RtLPrwN3YZJuxSE6zv 4mVlDJRontM+FS8jPRWL4OaurArOVzJujHiauSbJ3S1SwyjrsnD0rta7Nw06lUpV uuRtWGNhGFc5cYJbDRdxAE0NeG2L3wwqRDpE6yXyBlwqzngoWlTA0hPWWTFhmbD3 YANWgfdB93Q6MftuEYbRXEvUYxeufqGb4pYNWykcw9xt5UfBxd0ECK4Qk9NK2bm6 Pa9yNUxt6fwezxy3N53NFCgi+6Qz2HjvrqTDtHk+3BYetPDl0DBggoB11YaiAwMd Igm6amDC4X5NuDl0JVuNEvZsnflnNFd3UvjvnfVF52E5qyQnV2YYnliC9Ys1bGWE 49IHlnGyStuD7VddBe1S =xhi5 -END PGP SIGNATURE-
Re: Python Policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-21 15:54, Barry Warsaw wrote: > Hopefully, the latest changes (see previous follow up) are both > more concise and coherent. maybe. i have to admit i'm not totally used to an reviewing git patches per mailinglists, and in this case i got lost a little bit what the current draft is. would it be possible to put a complete draft online somewhere (maybe even as an r/o git), in addition to posting the patches on the ml. fg,asdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWKKtpAAoJELZQGcR/ejb4IAoP/iawsZNZApH4TsalsLOUe2I5 HVO9N0/KpmiJZtHWLdj0kfzbdiffb7GCcpDggZgzX3sZiWzQgMJAprqi8zX66hqR txIIPMDehm/QrxS7Gc1Ul6X/hpiaB/j4ROHjzzHoWrNsyXPaOCrOJ/I6nEwCh5Qb BGnHkYbIYd1yqJzkPVcGRedwrWcsjOh4AiodxQMk8TDxnz/dcjc2BBQqx0cyCAIX GW4P3RE0Tzf/K0327eQgA3hUTZnCB4IBHl1Z4Fo6Eb24MjuU0eE2LY1nOFXOwqYX hwTNZ40X/yBjj9YI3rBNYb7Z+PThKWnP4dBHtaBUNfVeb0X+8MOlmB03RW5oVKA4 DmOCOEBWngCTcybXV7xsmyXkfa8ZxK/WE98nfNhVX2kVc5O3DAiiTAwpKTTqzLL4 3wUtbT/F7cPmju6GwyU3BVt/edazpzd6ovGJc7KVdqaDJ5YNvf1KPQNcO0PevMwF wArJD7JH3+qdd5dpTaZYJY+Ej1SBDkKT0BYtJa2H5EsU7OVZ+XBh39lqmtzUWPIY On1NfhmfuMQ1Zl0P1woOVvXtFv8AJQEY2uVmNzP50dyKq+4qLmFNNmocWEf3QI2I emp16RgczBi6eiJbu+1xnGlhv3ygi4coH/QiWzgIvtjp3PmvTXBZThtrXdwQ3QMa PX8qDp/tQqEk/MNMRpSl =u0vU -END PGP SIGNATURE-
Re: DPMT Policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-22 11:30, Piotr Ożarowski wrote: >> i have to admit i'm not totally used to an reviewing git patches >> per mailinglists, and in this case i got lost a little bit what >> the current draft is. would it be possible to put a complete >> draft online somewhere (maybe even as an r/o git), in addition to >> posting the patches on the ml. > > git clone > git://anonscm.debian.org/python-modules/tools/python-modules.git -b > git-policy barry-policy && less barry-policy/policy.rst or > http://anonscm.debian.org/cgit/python-modules/tools/python-modules.git /tree/policy.rst?h=git-policy > > doh, thanks. (i actually had the repo cloned already but failed to see the `git-policy` branch :-() fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWKLhhAAoJELZQGcR/ejb4kDcP/ArjYABIju910SROwY1PUtd4 HQhYlUHW+7V+DlsK7rVRgBJGrHXWAVDq0ySOl5e/15jixwxgsezAOK0jDv7bjvsW pYJX3wRR88TiQqKNhaka0S4LiHm/3cdeISk7mnzKEOGsgD+7+KNVvAWrfVTeFuD2 8jCF8rPBODEAckyC0PblykONstQc9NMvYx7TnlcSb/xWWAiUQFvxEu+ZEFtU5VqZ rP4L3MN2fdZemwVeAEzIImnlZTL9l9h0J0+6czTMa8oR3hWlS+Ef+7mmKLusJitR Rmg14gmge+R0RBtlvHVk328grGZAxOYXWhNf8xOOt1IutCEqU8421GLUbGJF340W sDyQ8YKisYbqqrdQUDf65zwMAxXMxa/2u2Zm36Gxt46c6gD+wtzlGBtqfrWVHjyz SlbdlwTMu7N14vXmUCAvdp7qRuw20YbyVkkqTJNqWyIcX7Il0WlqwqOHMOh0wtY4 cApGAjeRvILXLlTbRs34lj4OTwFJvJTkbp3QLw8XM8hO84ZfPENKRtYv6r6vnrpw EefCdJ9FrH7kRI0m3AHIvDHnUnLDECp9sAY2ijPskBGj7AE2akCU1sVMy1eaBBtE J9eh74UYyuPLJFL4xKG+2N56Ju4joV8JnSL2EKBPxrr0jnSNbUCwojAk/sFD/ill rD0t0urXQ97b+JmFhpdT =bH0k -END PGP SIGNATURE-
Re: Pushing a bunch of packages to jessie-backports
On 2015-11-26 09:32, Piotr Ożarowski wrote: > PS I didn't "kick" him, i think the kick in question is not your disapproval of the current affair, but referring to past action <560c3acd.9000...@debian.org>. fgmasdr IOhannes
Bug#836163: ITP: python-bottle-cork -- authentication for the bottle web framework
Package: wnpp Severity: wishlist Owner: "IOhannes m zmölnig (Debian/GNU)" * Package name: python-bottle-cork Version : 0.12.0 Upstream Author : Federico Ceratto * URL : http://cork.firelet.net/ * License : LGPL Programming Lang: Python Description : authentication for the bottle web framework Cork provides a simple set of methods to implement Authentication and Authorization in web applications based on Bottle. . It is designed to stay out of the way and let you focus on what your application should do. I intend to maintain this package (and a few other bottle-related packages) within the Debian Python Modules Team.
Bug#836165: ITP: python-bottle-sqlite -- SQLite3 database integration for Bottle.
Package: wnpp Severity: wishlist Owner: "IOhannes m zmölnig (Debian/GNU)" * Package name: python-bottle-sqlite Version : 0.1.3 Upstream Author : Marcel Hellkamp * URL : http://bottlepy.org/docs/dev/plugins/sqlite.html * License : MIT Programming Lang: Python Description : SQLite3 database integration for Bottle. Bottle-sqlite is a plugin that integrates SQLite3 with your Bottle application. It automatically connects to a database at the beginning of a request, passes the database handle to the route callback and closes the connection afterwards. . To automatically detect routes that need a database connection, the plugin searches for route callbacks that require a db keyword argument (configurable) and skips routes that do not. This removes any overhead for routes that don’t need a database connection. I intend to maintain this package (and a few other bottle-related packages) within the Debian Python Modules Team.
Re: pypi2deb 1.20160809 and --profile dpmt
On 08/09/2016 09:27 PM, Piotr Ożarowski wrote: > > FYI: I just uploaded pypi2deb 1.20160809 which initializes all the git-dpm > stuff if you invoke py2dsp with --profile dpmt option OMG: i just discovered pypi2deb and its wonderful. unfortunately i missed this mail when it was sent (or - more likely - forgot about it), and while i was desparately looking really hard for something that would take care of setting up git-dpm, i was unable to find it. pretty please, could you improve the (currently absymal¹) documentation? pypi2deb deserves it gfmdsar IOhannes ¹ as in: no manpages, an empty /usr/share/doc (apart from the required changelog©right) and a very cryptic "--help" signature.asc Description: OpenPGP digital signature
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT
On 08/13/2016 12:39 AM, Barry Warsaw wrote: > just wish it had something like > `pull-and-update-all-branches` since it's a bit of a PITA to update the > pristine-tar branch. isn't this what `gbp pull` is supposed to do? gfdsar IOhannes signature.asc Description: OpenPGP digital signature
Re: Issue on setup.py with imports
On 2016-09-03 10:18, Marcos wrote: > I'm migrating Gufw [1] from python2 to python3 and honestly I'm stuck > with an error from the setup.py: Python module controller not found: > > costales@dev:~/Desktop/16.10$ sudo python3 setup.py install --prefix=/usr > ERROR: Python module controller not found > running install > running build > running build_py > running build_scripts > running build_i18n > intltool-update -p -g gufw > running build_icons > running build_help > running install_lib > running install_scripts > changing mode of /usr/bin/gufw to 755 > changing mode of /usr/bin/gufw-pkexec to 755 > running install_data > running install_egg_info > Removing /usr/lib/python3.5/site-packages/gufw-16.10.0-py3.5.egg-info > Writing /usr/lib/python3.5/site-packages/gufw-16.10.0-py3.5.egg-info > costales@dev:~/Desktop/16.10$ so the "error" is non-fatal and the installation proceeds. i fail to see the problem. fgmasdr IOhannes
Re: Bug#837805: Acknowledgement (ITP: python-can -- Controller Area Network interface module for Python)
Control: retitle -1 ITP: python-can -- Controller Area Network interface module for Python Thanks. Ooops, seems like i forgot the subject in this ITP On Wed, Sep 14, 2016 at 08:09:05PM +, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > debian-python@lists.debian.org, debian-de...@lists.debian.org > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > w...@debian.org > IOhannes m zmölnig (Debian/GNU) > > If you wish to submit further information on this problem, please > send it to 837...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 837805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837805 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Re: policy question: tag format for patch-less packages
On 11/16/2016 06:07 AM, chrysn wrote: > Should git-dpm be used even though no patches are present? how do you make sure that you will never need patches? (unless this is a native package) gfmards IOhannes signature.asc Description: OpenPGP digital signature
Re: Binary naming for Django Related Packages
On 2017-01-18 07:46, Scott Kitterman wrote: > +··named·django_packagename·upstream.··These·are·then·packaged·as > +··python3-django-package·and please use "package" vs "packagename" consistently. e.g. an upstream named "django_packagename" should be packaged as "python3-django-packagename". It's kind of obvious, but I think the policy should be precise. (and probably use "" or "$packagename" or something else to mark it as variable) gfmadr IOhannes
Re: How to split modules in multiple deb packages
On 2017-02-18 09:16, Simone Rossetto wrote: > One of the module is specific for Raspberry Pi, it adds some > functionalities, but > the daemon itself doesn't require a Pi hardware and can still do its job > without that module even on a Pi. What I want to do is to split the modules > in two deb packages, one with all the modules except rpi.py and one with only > rpi.py (setting the appropriate dependencies, i.e. python3-gpiozero, etc). > > How can I do that? why would you want to do that? i mean: what harm comes from shipping the rpi.py file on non-rpi systems? is that file exposed to the user or is it just internally used? is the system failing gracefully if it is there but not really usable, because you are missing hardware? (if so, there is no need to split). is the system failing gracefully if it is missing on systems that would normally use it? (if not, then splitting could actually be harmful). also, Debian has no notion of "packages only for the Raspberry", as there is no architecture specific to the RPi (only). So most likely you will end up with a package called "mypackage-rpi" that can be installed on any old s390x cpu, creating even more confusion. fgamsdr IOhannes
Re: [Python-modules-team] python-pip ancient version 1.5 for Debian 8
On 06/08/2017 01:08 PM, Brian May wrote: > CCing to correct mailing list. debian-python@lists.debian.org > > I don't actually understand the issue. jessie: python-pip_1.5.6-5 stretch: python-pip_9.0.1-2 no backports. i guess the OP has problems using pip as packaged in jessie with newer repositories (which i haven't tried, so i cannot confirm any problem) @clark: when reporting bugs, please use the 'reportbug' tool, which will properly create a ticket in our bug-tracking-system and eventually contain additional helpful information in assessing your problem. > > Clark Knøsen writes: > >> python-pip is no longer compatible with newer installations/repos like >> >> # pip install pyvirtualdisplay selenium >> >> python-pip installs 1.5 and the current version i 9.0 signature.asc Description: OpenPGP digital signature
Re: DPMT and git workflows
On 01/19/2018 12:45 PM, Simon McVittie wrote: > On Fri, 19 Jan 2018 at 14:25:57 +0300, Dmitry Shachnev wrote: >> I think for new packages it is better to use gbp-pq based workflow: >> https://wiki.debian.org/Python/GitPackagingPQ > > Is there consensus that the gbp-pq workflow is now allowed? I only > maintain one package in DPMT (tap.py) and every time I upload it I have > to remind myself how git-dpm works, so I'd like to switch it over to > gbp-pq as soon as I can. > > Relatedly, Alioth is going to be shut down at some point, with git > repositories frozen and made read-only, so it would seem a good idea to > start migrating git packaging to salsa.debian.org before that happens. > python-modules-team and python-apps-team groups, perhaps? I can create > a python-modules-team group and migrate tap.py as a sample if people > would like to see an example package. > should we keep the structure of putting all packages into a separate subdir (aka "sub-group"). i was also thinking about creating a single python-team group with a PAPT and a DPMT subgroup, but apart from aesthetics i cannot think of any good reason to do so. it probably creates more trouble than it is worth. gfards IOhannes signature.asc Description: OpenPGP digital signature
Re: Move to salsa? Team structure preview ready
thanks for taking the lead. On 2018-02-08 15:16, Ondrej Novy wrote: > > But I don't think all DD are masters in our team. This is true only > for 'Debian' team. Even if you are DD, you need to join team or > subteam to have commit access to it. i think this is true. at least i had to request membership explicitely for all teams but "debian" (fka "collab-maint"), > > I disabled "request to join" feature. To join DPMT/PAPT you need to send > email to debian-python and agree with policy. We already ignored alioth > join requests. [...] > > maybe we can cleanup member list and don't do migration at all. So > require explicit request to join. I don't have to process it. i'm confused. how do i become member of the salsa group? automatically, by taking the alioth group? manually, by re-requesting access (to cleanup the team of those who no longer have interest in the team)? will DDs and guest accounts be handled differently? do i have to send a formal email to request membership *again*? fgamsdr IOhannes PS: there's numerous scripts out their to help the migration. here's the one i was using to migrate the Pd-packages into the multimedia-team/pd/ subgroup (and is based on the script that migrated the remaining ~400 packages for the multimedia-team without subgroups). it automatically registers email-notifications (via tracker.d.o) and pending-uploads tags, and (by default) irker notifications. it has a number of options. https://salsa.debian.org/umlaeute/multimedia-cli
Re: pyapi-gitlab vs python-gitlab
On 02/09/2018 05:19 AM, Paul Wise wrote: > On Fri, Feb 9, 2018 at 11:17 AM, Scott Kitterman wrote: > >> I'd encourage you to work with the upstreams to deconflict the namespace. >> This isn't really a problem Debian should solve. > > Good point, I've contacted them via email and will file tickets if > there is no response. > i've contacted them in 2017-12 (via github), and afaict both projects acknowleged the problem and rejected a solution :-( https://github.com/pyapi-gitlab/pyapi-gitlab/issues/263 https://github.com/python-gitlab/python-gitlab/issues/385 gfsmdr IOhannes signature.asc Description: OpenPGP digital signature
Re: RFS: wikitrans/1.1-1 [NEW]
Quack, On 2018-08-27 00:20, أحمد المحمودي wrote: Please sponsor the upload of the new package python-uinput I'm on it. Upstream is releasing at a fast pace: uscan: Newest version of wikitrans on remote site is 1.2, local version is 1.1 The manpage you created could be suggested to be added upstream. I can't build the package: gbp:error: Error creating wikitrans_1.1.orig.tar.gz: Pristine-tar couldn't checkout "wikitrans_1.1.orig.tar.gz": fatal: Path 'wikitrans_1.1.orig.tar.gz.delta' does not exist in 'refs/heads/pristine-tar' Be sure to push all branches when you're done working. TBC \_o<
Re: RFS: wikitrans/1.1-1 [NEW]
Coin, All clear! \_o<
pybuild mysteriously does not copy all testfiles
updating one of my packages (python-can), the test-suite started to
fail, with an error-code 5, indicating that "no tests have been run".
since there *are* tests to be run, i investigated and - after scratching
my head - found that 'pybuild' did not fully copy the test-directory
from the source-directory to the build directory.
The sources "test/" directory contains:
```
test/serial_test.py
test/test_slcan.py
test/test_cyclic_socketcan.py
test/data/logfile.blf
test/data/__init__.py
test/data/example_data.py
test/data/logfile.asc
test/test_bit_timing.py
test/zero_dlc_test.py
test/test_systec.py
test/open_vcan.sh
test/message_helper.py
test/contextmanager_test.py
test/test_detect_available_configs.py
test/test_message_sync.py
test/notifier_test.py
test/config.py
test/simplecyclic_test.py
test/test_scripts.py
test/logformats_test.py
test/listener_test.py
test/back2back_test.py
test/test_message_class.py
test/__init__.py
test/test_message_filtering.py
test/test_socketcan.py
test/test_kvaser.py
test/test_viewer.py
test/network_test.py
test/test_vector.py
test/test_socketcan_helpers.py
test/test_load_file_config.py
```
However, ".pybuild/cpython3_3.7_can/build/test/" contains only: (after
dh_auto_test failed):
```
test/data/__init__.py
test/data/example_data.py
```
d/rules is pretty standard:
```
#! /usr/bin/make -f
export PYBUILD_NAME=can
include /usr/share/dpkg/default.mk
export DEB_VERSION_UPSTREAM
%:
dh $@ --with python3,sphinxdoc --buildsystem=pybuild
override_dh_clean:
dh_clean
rm -f test.asc test.csv
rm -rf .pytest_cache/
override_dh_auto_build:
dh_auto_build
python3 -m sphinx -E -T -b html doc .pybuild/docs/html/
override_dh_auto_install:
dh_auto_install
-for f in debian/*/usr/bin/*.py; do mv $$f $${f%.py}; done
-rm -f debian/*/usr/lib/python*/dist-packages/test.???
```
and the package does not contain d/pybuild.testfiles or similar.
Now if I add a file from tests (say "test/network_test.py") to
d/pybuild.testfiles, that file is copied (although into
.pybuild/cpython3_3.7_can/build/ rather than into
.pybuild/cpython3_3.7_can/build/test/) and runs correctly.
adding "test/" to d/pybuild.testfiles (with or without the trailing
slash) did not do anything (apart from the original behaviour of only
copying 2 files).
doing something like "find test -type f > d/pybuild.testfiles" copied
all files, however the directory structure was lost (all files ended up
in .pybuild/cpython3_3.7_can/build/), and the tests started to fail as
they didn't find files in the subdirectories as expected.
i'm totally stumified.
an intermediate hack i found to work is to manually copy the "test/"
directoy into the build-dir, using:
export PYBUILD_BEFORE_TEST=cp -r {dir}/test {build_dir}
but that seems extraordinarily clumsy. esp. since pybuild(1) says:
> By default only test and tests directories are copied to build
> directory.
any ideas what does wrong?
mgfdsar
IOhannes
signature.asc
Description: OpenPGP digital signature
Re: pybuild mysteriously does not copy all testfiles
On 10.09.19 16:14, Ole Streicher wrote: > Hi IOhannes, > > I have basically the same problem, funnily with almost the same subject: which was entirely intentional :-) i decided to start a new thread because i'm not sure whether the problem is really the same. but i guess, i'll just file a bug against dh-python... dfasdr IOhannes
Re: debian/watch: How to watch version tags and what to capture?
On 9/17/23 10:41, c.bu...@posteo.jp wrote: Hello, maybe it depends on my non-nativ English that I'm not able to make myself clear. On 2023-09-17 09:56 Mechtilde Stehmann wrote: What do you expect? As I told. Information just in time. Within in a delay of 1 or 2 hours the tracker/dashboard should inform about the new release. hmm. how is "1 or 2 hours" more *just in time* than "1 or 2 days"? i get your point that you want the information fast, but it seems you are just using some arbitrary constraint that fits your personal need. it appears that for "most" Debian maintainers a lag of "1 or 2 days" is just as well (i assume that it is indeed "most" maintainers, as I don't see many complaints; for my *personal* workflow i'm very sure that I do not care to be informed about whether a new release has been made withing the last 2 hours, as I pretend that I like to let the dust settle a bit before starting *my* work). If this is not possible because of technical reasons (server load, etc) then indicate exactly that with a timestamp to make the reader able to validate the information in time. i find the suggestion to add a timestamp on when a given piece of information was updated last in the tracker very useful. possibly as a mouse-over or somesuch, in order to not clutter the already rather full page with even more information that is *usually* not important at all. What do you mean is unprofessional? That the information the "Debian system" is out dated. I personally feat at unease when people call other people "unprofessional" like this. such accusations just feel... unprofessional :-) Try to step into the role of a (new) user or a possible contributor. the tracker's audience is really Debian maintainers, not users. i don't know what the average user expects, but I assume that they are good enough with the information about what Debian actually *ships* (as in: what is packaged; and more likely: what is packaged in Debian/stable or even Debian/testing, and less so Debian/unstable) rather than whether "Debian" has been made aware that there is a new release minutes after it has been made available to the public. as for Debian maintainers: if they need super-short notice of a new package, then I do not see why they cannot track upstream themselves. after all, d/watch files tend to be buggy as well and give false information (or: upstream decided to switch to some new release scheme which simply breaks the existing d/watch) making them only so useful. in any case: why do *you* think it of utmost importance to be informed of a new release on this very page? Most of the maintainers are volunteers and work on packaging in their free time. Why do we have to increase the volume of the list with that topic? Can we just discuss this on an issue tracker about the tracker? ;) fair enough. however, it seems i cannot find your bug report (i checked both the BTS and your emails, but there is no indication of any existing bug report) gcmas IOhannes
Zope in Potato ?
Anybody thinking of adding zope www.zope.org into Potato ? -=Francois=-
python-clamav_0.4.1-2_i386.changes ACCEPTED into unstable
Accepted: python-clamav_0.4.1-2.debian.tar.gz to main/p/python-clamav/python-clamav_0.4.1-2.debian.tar.gz python-clamav_0.4.1-2.dsc to main/p/python-clamav/python-clamav_0.4.1-2.dsc python-clamav_0.4.1-2_i386.deb to main/p/python-clamav/python-clamav_0.4.1-2_i386.deb Override entries for your package: python-clamav_0.4.1-2.dsc - source python python-clamav_0.4.1-2_i386.deb - optional python Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 524645 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1p2rhh-0007iy...@franck.debian.org
Processing of python-pandocfilters_1.2.1-1_amd64.changes
python-pandocfilters_1.2.1-1_amd64.changes uploaded successfully to localhost along with the files: python-pandocfilters_1.2.1-1_all.deb python3-pandocfilters_1.2.1-1_all.deb python-pandocfilters_1.2.1-1.dsc python-pandocfilters_1.2.1.orig.tar.gz python-pandocfilters_1.2.1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xa1dd-0001px...@franck.debian.org
python-pandocfilters_1.2.1-1_amd64.changes is NEW
binary:python-pandocfilters is NEW. binary:python3-pandocfilters is NEW. source:python-pandocfilters is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will recieve an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xa1pb-0003c1...@franck.debian.org
python-pandocfilters_1.2.1-1_amd64.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 30 Jun 2014 10:04:06 +0200 Source: python-pandocfilters Binary: python-pandocfilters python3-pandocfilters Architecture: source all Version: 1.2.1-1 Distribution: unstable Urgency: low Maintainer: Debian Python Team Changed-By: Sebastian Humenda Description: python-pandocfilters - python bindings for Pandoc's filters python3-pandocfilters - python3 bindings for Pandoc's filters Closes: 746745 Changes: python-pandocfilters (1.2.1-1) unstable; urgency=low . * Initial release (Closes: #746745) Checksums-Sha1: 5ef67f503f87bd286c7a8dbe1477ba4df5c91612 2161 python-pandocfilters_1.2.1-1.dsc 6abe48f6ba5b1746c919a3464179d1a242613d4e 7310 python-pandocfilters_1.2.1.orig.tar.gz 7f61654efd7580b28aadcdf69db61bf8171e9e35 2244 python-pandocfilters_1.2.1-1.debian.tar.xz 0e8696b3ed592708360cce31a88920d21a797e76 10290 python-pandocfilters_1.2.1-1_all.deb 7b9a5699cf56d99907b7152780183c9eb75de2bf 10370 python3-pandocfilters_1.2.1-1_all.deb Checksums-Sha256: 541d84dab540a53bc50269806acea5139dd23293ae0a3bb36e20df6cb1785a38 2161 python-pandocfilters_1.2.1-1.dsc 83dc6e837f0101477b1f8f3e184bf764686b3175e515e3c4ea8525b4ae485f74 7310 python-pandocfilters_1.2.1.orig.tar.gz c9bae6d4548bfa2e6a965925ec23442bdf985abc6aaca427776dda68c990f73b 2244 python-pandocfilters_1.2.1-1.debian.tar.xz b78b4642a1b938b9aa8db1d4f890aaf53fe981b621d0defbb6e34cba5756955b 10290 python-pandocfilters_1.2.1-1_all.deb 927f5bbd4682119912bbcf867e78ddb10a901d6420e5056b021d97a3de4ecca2 10370 python3-pandocfilters_1.2.1-1_all.deb Files: 5f897bec618189b41d67a31c5a8de640 10290 python optional python-pandocfilters_1.2.1-1_all.deb e34b8d1193599e6e11953342f4e97906 10370 python optional python3-pandocfilters_1.2.1-1_all.deb 86eb42c9d7dfbc843f0fe4919208708e 2161 python optional python-pandocfilters_1.2.1-1.dsc a83eeccd0df79c0f3cf91e0af949a367 7310 python optional python-pandocfilters_1.2.1.orig.tar.gz d6793f016f4727631982acd3cbd0ef2a 2244 python optional python-pandocfilters_1.2.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT0AO/AAoJEBH0lP5vGG7N1lIP/Ri4EbWvE8ZVijEPRgmCd9xd a5RVETIGdqosgncg3mF/LwHyAnyAyw0fLq5cyzNhg4DfUXZG8kPIGt0K9RF5Zd4h Rwhmum51FapH9/hOIl39J3rJjGcQRlc8W+iB3go8HdGo2sz4rXHLrsAv1lTHEfxR ThwY1iT1HP4KBU7Eee25J/yo+pzJwlo+/laDeaaQcLvuS8Xy5zIQARsHODSM1NUq 5FGqJ371SngnbwNtMQNobivGsBjDXeVhWt82fw2bwNOEHEx3qgxWtUnlrJ8qhy2j cstQc0Hr9oupFXgajmndtOWLsKP1TPeb/Mp6WW4EE7LmNX5JdbLKlx0TCMh6aUqk xj0DCCY4WWm6YN+LeWBnyWe/7GQ2CTWmCvv/w/DeuRVf3gJB87LuBHeXeg+glkre Up5bjQ18YG7Xo6BIONApnqf9WN5onsbiHzRslOZvbIYBvAS/KpSV8ADI1apltc1h j1PtHnC6cajJ2GjFQzxk4TgTpDmSPzqPpRmlOWN+WyAsXHaZnS4VW/vJk78w4aRt mAiwrgvgRJR214OKbpGazxYadr2auqOIQsz1EWtQSh5Z9uUP9teTSKtcihEiRDs/ u8BI1gwWuur2UhDizciJsGEeVr1zlXGrHYe8XRK9vT9aYk81iHFy5uBXYKFZmBZB V0z5OtiZoTuexKgBWb3X =P0ZL -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xbjb7-00074w...@franck.debian.org
Processing of khard_0.16.1-1_source.changes
khard_0.16.1-1_source.changes uploaded successfully to localhost along with the files: khard_0.16.1-1.dsc khard_0.16.1.orig.tar.gz khard_0.16.1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
khard_0.16.1-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Apr 2020 10:05:57 +0200 Source: khard Architecture: source Version: 0.16.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Félix Sipma Closes: 942416 Changes: khard (0.16.1-1) unstable; urgency=medium . * New upstream version 0.16.1 (Closes: #942416) * move the package to Debian Python Team * update B-D, add: - python3-sphinx-autodoc-typehints - python3-sphinx-autoapi - python3-astroids * docs: remove AUTHORS file * khard.examples: remove misc/khard * khard.doc-base: update index path * update patches * bump Standards-Version to 4.5.0 Checksums-Sha1: 5d118c0de53fbf531bb6c64e945afc9aa2ff5479 1680 khard_0.16.1-1.dsc 236c06ad9c4ef2629617772cdccf4dd55546b86b 577538 khard_0.16.1.orig.tar.gz 4da10c05179540344d6a55d0b03d877cc7ae008f 4964 khard_0.16.1-1.debian.tar.xz Checksums-Sha256: 99436155dda2dcb5b00e3eedac729f9c2bbaa5b27a181f05a7b303dfa1849d81 1680 khard_0.16.1-1.dsc 9a50273bc827da99afc4dc8840be02dc37a22c2bfc88a04ed348f60389f14f2e 577538 khard_0.16.1.orig.tar.gz b2b8d00529cf4affcf74433b02728d25496802f65e3f4c0dc7ac0eaa7d26ad38 4964 khard_0.16.1-1.debian.tar.xz Files: b2f4d2430201b15533daef4ccaded2e8 1680 utils optional khard_0.16.1-1.dsc 2d17f791b46ae6fb26ee820495084363 577538 utils optional khard_0.16.1.orig.tar.gz 513a09f3e14f73b8d8e72a35876e216d 4964 utils optional khard_0.16.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQR6zeIsS8L0XLQfqiQBpfxHUdFE8AUCXqG/4QAKCRABpfxHUdFE 8Kz0AP9bV/BlefuTLkF/Voj+lPLTxFJkfDszr0No/UCfmle7HAEAvAmbhESrLtCS t1WtFBITZJmYC0m7BMGC2i4Mc3+H+QY= =nBwe -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of todoman_3.7.0-2_source.changes
todoman_3.7.0-2_source.changes uploaded successfully to localhost along with the files: todoman_3.7.0-2.dsc todoman_3.7.0-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
todoman_3.7.0-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 23 Apr 2020 18:39:20 +0200 Source: todoman Architecture: source Version: 3.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Félix Sipma Changes: todoman (3.7.0-2) unstable; urgency=medium . * move the package to Debian Python Team * bump Standards-Version to 4.5.0 (no change required) * make use of dh_sphinxdoc Checksums-Sha1: c9a5a6c19949ea901dd18fb506f443dc815f744a 1905 todoman_3.7.0-2.dsc a7d48bdd9e3704782b607f79426dea4cb0e74b51 8792 todoman_3.7.0-2.debian.tar.xz Checksums-Sha256: 2c37c319760bf289400d8897a4028470b464539585bb463c9a4af34832c57640 1905 todoman_3.7.0-2.dsc d9c343a2dea2f39a77505820cfb169de104d4ca2efa0d8691c070114ab92a1db 8792 todoman_3.7.0-2.debian.tar.xz Files: ecc64aedae81de7c17e81acb0b8e71fb 1905 utils optional todoman_3.7.0-2.dsc a512649e075c04c069d0b89a5f7b854c 8792 utils optional todoman_3.7.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQR6zeIsS8L0XLQfqiQBpfxHUdFE8AUCXqHF1AAKCRABpfxHUdFE 8PDNAQCP/CRZt73P/FkX+uyurE9roJULZbLHtJb3aPZmktRAoQEAhgihrb3OY7qs fF8bbfnzAy6uyQ62FvzWQGdI/85k5QQ= =fWLV -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of python-strictyaml_1.1.1-1_source.changes
python-strictyaml_1.1.1-1_source.changes uploaded successfully to localhost along with the files: python-strictyaml_1.1.1-1.dsc python-strictyaml_1.1.1.orig.tar.gz python-strictyaml_1.1.1-1.debian.tar.xz python-strictyaml_1.1.1-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
python-strictyaml_1.1.1-1_source.changes REJECTED
Source-only uploads to NEW are not allowed. binary:python3-strictyaml is NEW. source:python-strictyaml is NEW. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
Processing of mathlibtools_1.0.0-1_amd64.changes
mathlibtools_1.0.0-1_amd64.changes uploaded successfully to localhost along with the files: mathlibtools_1.0.0-1.dsc mathlibtools_1.0.0.orig.tar.gz mathlibtools_1.0.0-1.debian.tar.xz mathlibtools_1.0.0-1_all.deb mathlibtools_1.0.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
mathlibtools_1.0.0-1_amd64.changes is NEW
binary:mathlibtools is NEW. binary:mathlibtools is NEW. source:mathlibtools is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
mathlibtools_1.0.0-1_amd64.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 Aug 2021 08:05:31 +0100 Source: mathlibtools Binary: mathlibtools Architecture: source all Version: 1.0.0-1 Distribution: unstable Urgency: low Maintainer: Debian Python Team Changed-By: Christopher Hoskin Description: mathlibtools - supporting tool for Lean mathlib Closes: 991923 Changes: mathlibtools (1.0.0-1) unstable; urgency=low . * source package automatically created by stdeb 0.10.0 * Add copyright * Set DEP-14 debian branch in gbp.conf * Update watch * Bump debhelper compat from 9 to 13 * Add descriptions to control * Change section to math, rename as executable package * Remove white space from rules * Declare Rules-Requires-Root: no * Add upstream metadata * Bump Standards-Version from 3.9.6 to 4.5.1 (no change required) * Add elan as a Recommends * Add mathlibtools.egg-info to clean * Add VCS to control * Set Maintainer to python team * Initial release. (Closes: #991923: ITP: mathlibtools -- supporting tool for Lean mathlib) Checksums-Sha1: 4d64e4e926855f4471570c52fff0f35d9b1635e2 2023 mathlibtools_1.0.0-1.dsc c31b530e9123aa1d9f148453db445c91f90daefb 24840 mathlibtools_1.0.0.orig.tar.gz 4873dd9c58640da60c16df41918a6ad2501080ff 2088 mathlibtools_1.0.0-1.debian.tar.xz d9f58e083b6277a50a0190532d39fb968bf907fc 17636 mathlibtools_1.0.0-1_all.deb 986a352345a42dc366815032d8955de05bed6b3c 6306 mathlibtools_1.0.0-1_amd64.buildinfo Checksums-Sha256: 9a8362411e6f582207c74fa9d38f2753b29e0257da58a23c560f12d9af9fa4dc 2023 mathlibtools_1.0.0-1.dsc 4280d331cdafa7899aa79b3312d2f3521f911e3b952cb509e259fced8d712481 24840 mathlibtools_1.0.0.orig.tar.gz ac37db71becd470f3ed2ccc1bbc9fd18cc8eef35c2ddb7d14a1458b6f8744f78 2088 mathlibtools_1.0.0-1.debian.tar.xz 2aedc06dae97f6e01633facd0dd8724e65c05fa48e281a0ea7431cfc26f9baf0 17636 mathlibtools_1.0.0-1_all.deb 616a87492e5d2d987f9dace852a5d79f230b143387d42c92b8d91a813157ae06 6306 mathlibtools_1.0.0-1_amd64.buildinfo Files: 25fcb4aa28881ec62c455b20e62a67ac 2023 math optional mathlibtools_1.0.0-1.dsc 2e543ab49b4135667ce37f6f4405c201 24840 math optional mathlibtools_1.0.0.orig.tar.gz 20a6d8949a1692aea202219fe6bff5a8 2088 math optional mathlibtools_1.0.0-1.debian.tar.xz b0b3d958a5fe9ef45aca9f4026470675 17636 math optional mathlibtools_1.0.0-1_all.deb 56b5be13e7d98a7aea2ef48e8ca5daeb 6306 math optional mathlibtools_1.0.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEbctJ5K6JlvFsvhGhf6qUsnUUSpoFAmEM37gACgkQf6qUsnUU Spriig/+Ncelh1Mi7QlaoCEpMMpP0oDfYxz7BAGdYmmQnljw3oyCwdAaQtAKl5dC G1l+WsripbYU4kpNePFZdCuWlQ8HvGDJp2w5ldeOko5ds/qDujgotRC6aZiLWXGB a4uv2td6cD2P8IoCv4JVllBIuTU3FS963s7+u1Gk2XNNnQbJSPShcB/8u2//FDhz QKzuTAK5E5tMidLkjVE4ebNoTtKWKDEZm+d5F06291nt9nrONL8KAAedelC37rM0 DXn9rIklqtl8aVU0HrL3wqa3LgE0Ffu67owRkAgYVX7FFTu0s7J9VhasyvoNrKVG 1+AbUNyKC0/PQsKKiNJpCdbBd+SEwjMybAXG4YHP53a4Psbnt2DYmmjMaW1CPJyA DZvMxQHcouoPJP0IoDIH2UinOR8BffSKmDeBMI/wpxZPzh+Am+N/kpZuuzeRlryV e1nHpTUqo2j7mhsW14KvbABnbSIBfs9uF6VchlJHe/+p08BwCpO1rR7flhuchSY7 JuWzQoD35L1L2EwD7L9vpAiOmG89kXOO9vu4UnPrcKRo+gktN6Bwd6kSjD6MufOe ZxAGhMyWt+62xVNRke+CRNqf4QQgMtCcBe2aJivvud78fnoYyHsVYhBqwzzptqM9 8utkDug41Nb1nQNlfC/aS7UinltTjJc61HmRqjJENLI3sbJ6RLw= =G2Ue -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of python-softlayer_5.9.8-1_source.changes
python-softlayer_5.9.8-1_source.changes uploaded successfully to localhost along with the files: python-softlayer_5.9.8-1.dsc python-softlayer_5.9.8.orig.tar.gz python-softlayer_5.9.8-1.debian.tar.xz python-softlayer_5.9.8-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
python-softlayer_5.9.8-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 04 Feb 2022 10:24:57 + Source: python-softlayer Architecture: source Version: 5.9.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Ana Custura Changes: python-softlayer (5.9.8-1) unstable; urgency=medium . [ Ondřej Nový ] * Bump Standards-Version to 4.4.1. . [ Ana Custura ] * New upstream version 5.9.8 * Refresh patch for new version * Upate debian/control fields with Python Team details * Bump debhelper-compat version to 13 * Add Rules-Requires-Root: no to debian/control Checksums-Sha1: f33dfa719f400a306d7bf5580639b2fc689c808b 2173 python-softlayer_5.9.8-1.dsc b72b3ccfebc853da488c2240667a5fd3a0e34213 489563 python-softlayer_5.9.8.orig.tar.gz 5aabdce93e734f252ec3142f57dfc20b44407612 4452 python-softlayer_5.9.8-1.debian.tar.xz 434f297613a3273f1e3d255c14959021c9cb564b 6697 python-softlayer_5.9.8-1_amd64.buildinfo Checksums-Sha256: 5420c0a9b0556f80c1063f59196bebad4cb24f42a4d27bc5bfb00c6e54aa8474 2173 python-softlayer_5.9.8-1.dsc 4231e6629eaffdd9adf7fc1076e30bd0580232a068f3963e73dec88cabb06ee5 489563 python-softlayer_5.9.8.orig.tar.gz 9fcfc6d350f8d9ec27dc0b1a4be9b87a9cc642fcdd96316774b08a6f5ff1adc7 4452 python-softlayer_5.9.8-1.debian.tar.xz b6603b760026534a33fc02371b3eea31cd90cb075923d9b27916f1dc11c6bce7 6697 python-softlayer_5.9.8-1_amd64.buildinfo Files: 23b60193a6d4867746cdbe310393bf65 2173 python optional python-softlayer_5.9.8-1.dsc 68609b60602f910fb6e38ac8bd1bbdb8 489563 python optional python-softlayer_5.9.8.orig.tar.gz 1e06147a91d66eac6786aa63425edfe8 4452 python optional python-softlayer_5.9.8-1.debian.tar.xz 82742b7f9909e35cdece0f2625f0f84e 6697 python optional python-softlayer_5.9.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEMEVxS8/NmLlMBvgk0AURaWEueyoFAmH8/5sACgkQ0AURaWEu eypwExAAi16fTL5P0kC24NugwidRhXuyTLOnsBqKE7034EziV0PQP5Z0eU055TG2 6Z0FqcCPCeA00loDwjGGnsBGS2yoKJmFWv/fGauWIkAnu4yeROdFV111wJWUaX0Q NVLrMKBhTzhiqIDHfLUC0LXyRxWBK4hP9qwbMs/OeKOsCX7dnQyP6+HHX/F96lBH Qy9xIgv9+UVmVcwoIN6fdkOxCJs83siRZMwr/OvZE3eix6gIn1rUQnEuF3LoVnPm JC2UUSb/ZoNvYh55cktPKbpLjZV8mba7mw8AXs4PxR1ponIY59xK//TZmIBLmNPT Jihk+6PZzXs1RdMpCr2mBJo3ERkt2J9hOQrEogYlKvVmrh53z4NRYXefO+r0dX9T jr4nX0oX/GK0ddwrJwkQGCiAhmcOrLd0QlD+nuSRA53NF9XJAYYQyVdw97RLPcII 5quc1QA1BV3y+Wt49OmG4W4rLbJFlcGc/FI7+Wf07tvsOu8UBSYObQrijPvIN7E8 kjnWUHZ8hQ7lHmHUz3uhuYBIyUaFEHtHzBzNBM1ZI2WjzSTl2+L7AqpGVqzgjPrX wJ8eoapDii6dR/oP6IponpsZMjkJmEQmAj/JFeA77PJPNgyC7HVTp8/b4OvyEMHf Ss0joky9GsLZUfYkdnEBsx4ek70Xkh2ikjP+/33Atdut31k373s= =HKxR -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#386211: Info received (Who is supposed to remove the .pyc files? (see #386211))
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Ludovic Rousseau <[EMAIL PROTECTED]> If you wish to continue to submit further information on this problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#386211: Info received (Bug#386211: Who is supposed to remove the .pyc files? (see #386211))
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Ludovic Rousseau <[EMAIL PROTECTED]> If you wish to continue to submit further information on this problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#547565: Info received (python-central NMU (python2.6 related))
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Matthias Klose If you wish to submit further information on this problem, please send it to 547...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 547565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#834809: Info received (Bug#834809: dh-python: requires.txt versions ignored when writing control)
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Piotr Ożarowski If you wish to submit further information on this problem, please send it to 834...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 834809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#834809: dh-python: requires.txt versions ignored when writing control
Processing control commands: > tags -1 wontfix Bug #834809 [dh-python] dh-python: requires.txt versions ignored when writing control Added tag(s) wontfix. -- 834809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#122653 acknowledged by developer (Bug#67644: fixed)
This is an automatic notification regarding your Bug report #122653: zope-worldpilot keep python packages out of testing, which was filed against the ftp.debian.org package. It has been closed by one of the developers, namely Debian Archive Maintenance <[EMAIL PROTECTED]>. Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact the developer, by replying to this email. Debian bug tracking system administrator (administrator, Debian Bugs database) Received: (at 67644-close) by bugs.debian.org; 7 Apr 2003 11:23:06 + >From [EMAIL PROTECTED] Mon Apr 07 06:23:05 2003 Return-path: <[EMAIL PROTECTED]> Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 192UiP-0002jM-00; Mon, 07 Apr 2003 06:23:05 -0500 Received: from troup by auric.debian.org with local (Exim 3.35 1 (Debian)) id 192Ud7-0003JM-00; Mon, 07 Apr 2003 07:17:37 -0400 From: Debian Archive Maintenance <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: melanie $Revision: 1.37 $ Subject: Bug#67644: fixed Message-Id: <[EMAIL PROTECTED]> Sender: James Troup <[EMAIL PROTECTED]> Date: Mon, 07 Apr 2003 07:17:37 -0400 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: zope-worldpilot |1.0.4-1 | source, all Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are never removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED] This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED] Debian distribution maintenance software pp. James Troup (the ftpmaster behind the curtain)
Bug#67644 acknowledged by developer (Bug#67644: fixed)
This is an automatic notification regarding your Bug report #67644: Dependency error in zope-worldpilot, which was filed against the ftp.debian.org package. It has been closed by one of the developers, namely Debian Archive Maintenance <[EMAIL PROTECTED]>. Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact the developer, by replying to this email. Debian bug tracking system administrator (administrator, Debian Bugs database) Received: (at 67644-close) by bugs.debian.org; 7 Apr 2003 11:23:06 + >From [EMAIL PROTECTED] Mon Apr 07 06:23:05 2003 Return-path: <[EMAIL PROTECTED]> Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 192UiP-0002jM-00; Mon, 07 Apr 2003 06:23:05 -0500 Received: from troup by auric.debian.org with local (Exim 3.35 1 (Debian)) id 192Ud7-0003JM-00; Mon, 07 Apr 2003 07:17:37 -0400 From: Debian Archive Maintenance <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: melanie $Revision: 1.37 $ Subject: Bug#67644: fixed Message-Id: <[EMAIL PROTECTED]> Sender: James Troup <[EMAIL PROTECTED]> Date: Mon, 07 Apr 2003 07:17:37 -0400 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: zope-worldpilot |1.0.4-1 | source, all Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are never removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED] This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED] Debian distribution maintenance software pp. James Troup (the ftpmaster behind the curtain)
Processed: Re: RFP: python-kiwi reopen
Processing commands for [EMAIL PROTECTED]: > noowner 171950 Bug#171950: RFP: python-kiwi -- a graphical framework to construct simple UI Removed annotation that Bug was owned by [EMAIL PROTECTED] > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#370833: Info received (FTWCA python-central vs pyhton-support)
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Joey Hess <[EMAIL PROTECTED]> If you wish to continue to submit further information on your problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#375936: Info received (New debhelper update)
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Joey Hess <[EMAIL PROTECTED]> If you wish to continue to submit further information on your problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#374776: Info received (New debhelper update)
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Joey Hess <[EMAIL PROTECTED]> If you wish to continue to submit further information on your problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#375948: Info received (New debhelper update)
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Joey Hess <[EMAIL PROTECTED]> If you wish to continue to submit further information on your problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#375576: Info received (New debhelper update)
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Joey Hess <[EMAIL PROTECTED]> If you wish to continue to submit further information on your problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
joining the team
hi all, i would like to join the python modules team, mainly to maintain a few python-modules (who would have guessed that?), that I need as dependencies for other packages I maintain. I'm a long-term Debian user, and have become involved in packaging as late as ~2010, when I joined the pkg-multimedia team; since 2014 i'm a DD. I'm currently maintaining a few python related packages, namely: - assimp (an 3d-model importer library that also provides python bindings) - pysoundfile (libsndfile wrapper for python/python3) I'm currently trying to get python-easywebdav (ITP #790872) into Debian, and would like to do this under the python-modules team umbrella. my alioth username is "umlaeute". fgmrds IOhannes signature.asc Description: OpenPGP digital signature
DPMT: server-side git hooks
hi all, while toying around with managing a few python packages in git, i noticed that the post-receive hook installed by the "setup-repository" script is not working as advertised. for one thing, it complains that "dam.homelinux.net:9418" is unreachable (and indeed that name cannot be resolved via DNS). this is one of the KGB bot servers, configured for all repositories in /git/python-modules/kgb-client.conf. according to Gregor Herrmann of the KGB team¹, that host has "changed quite some time ago", with the new name being kgb.ktnx.org, as documented on https://kgb.alioth.debian.org/alioth.html. maybe some of the admins can update the kgb-configuration. another problem is a spurious complaint about "Invalid revision range 00..". i haven't been able to track that down yet, but will report back if i find something. fgmar IOhannes ¹ here's transcript of my conversation with gregor: 21:56 < umlaeute> gregoa: the python-modules team uses dam.homelinux.net:9418 as one of the KGB-servers, which is non-responding 21:56 < umlaeute> actually it doesn't resolve 21:56 < umlaeute> i've been told that you might be in the know 21:57 < umlaeute> or should that server not be used at all? 21:58 < gregoa> umlaeute: the servername changed quite some time ago. the current one(s) are here: https://kgb.alioth.debian.org/alioth.html 21:58 < gregoa> umlaeute: dam.homelinux.net -> kgb.ktnx.org 22:03 < umlaeute> gregoa: thx 22:04 < gregoa> np signature.asc Description: OpenPGP digital signature
I think you should
Our online University degree selection is coming to an end. Over 400 degrees have been sent out in just under 3 months. As of now we have only 20 degrees available and we are still using work experience and past knowledge as our basis for acceptance. If you or a family member thinks they may qualify for our 2 week, no study University degrees then call our Faculty department to find out. Faculty Department Number: 1-206-984-1178 Note: Upon qualification we will need 1-2 weeks to send out transcripts and diploma. Margo Trent BSc Information Systems Faculty Assessment Office -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
