Bug#781165: ITP: prospector -- Python code analysis tool

2015-08-25 Thread Daniel Stender
http://mentors.debian.net/debian/pool/main/p/prospector/prospector_0.10.1+git20150706.a00e191-1.dsc Prospector is in NEW. Thanks everybody for sponsoring and by-packaging. DS -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8

Bug#781165: ITP: prospector -- Python code analysis tool

2015-08-08 Thread Daniel Stender
No, I've got that wrong, the tests don't demand these packages. Thus, looks good everything, as soon as the blocks are resolved the package is going to be uploaded to Mentors. Cheers, DS -- http://www.danielstender.com/entwicklerblog GnuPG key: 4096R/DF5182C8 -- To UNSUBSCRIBE, email to debi

Bug#781165: ITP: prospector -- Python code analysis tool

2015-08-07 Thread Daniel Stender
Prospector is very close. The situation on the packages: A NMU for the pep8 update is in deferred uploads, pylint-celery is in NEW. Pylint 1.4 is in unstable (thanks very much!), and that would be it for the depends. Coming back to the recommends, Vulture is RFS [1], Frosted hangs in unstable wa

Bug#781165: ITP: prospector -- Python code analysis tool

2015-07-25 Thread Daniel Stender
Prospector is just around the corner. The state of requirements is: dodgy in, pylint-celery in, thanks for sponsoring. Pylint-common in the staging area. Missing just: 1) Please update pep8: https://bugs.debian.org/788117 2) Pylint >= 1.4 in experimental DS -- http://www.danielstender.com/blo

Bug#781165: ITP: prospector -- Python code analysis tool

2015-07-18 Thread Daniel Stender
Status update, in the missing packages we're further down, it remains solely: 1) pylint-celery: RFS: https://bugs.debian.org/789712 2) pylint-common: http://anonscm.debian.org/cgit/python-modules/packages/pylint-common.git (sponsoring ready) 3) please update pep8: https://bugs.debian.org/78811

Bug#781165: ITP: prospector -- Python code analysis tool

2015-06-29 Thread Daniel Stender
On 29.06.2015 14:34, Daniel Stender wrote: > build Prospector in Sid ... meaning fulfilling _INSTALL_REQUIRES incl. full running tests. All that needed to run, anyway ... DS -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0

Bug#781165: ITP: prospector -- Python code analysis tool

2015-06-29 Thread Daniel Stender
Status update (counting from now on only what's missing to build Prospector in Sid): 1) setoptconf: RFS: https://bugs.debian.org/789520 2) dodgy: RFS: https://bugs.debian.org/789617 3) pylint-celery: RFS: https://bugs.debian.org/789712 4) pylint-common: http://anonscm.debian.org/cgit/python-mo

Bug#781165: ITP: prospector -- Python code analysis tool

2015-06-24 Thread Daniel Stender
Update, 1) requirements-detector: RFS: https://bugs.debian.org/789497 2) setoptconf: RFS: https://bugs.debian.org/789520 3) dodgy: RFS: https://bugs.debian.org/789617 4) pep8-naming: RFS: https://bugs.debian.org/789680 5) pylint-celery: RFS: https://bugs.debian.org/789712 6) pylint-common: IT

Bug#781165: ITP: prospector -- Python code analysis tool

2015-06-23 Thread Daniel Stender
Some progress, pep257 is already unstable. The status is, 1) requirements-detector: RFS: https://bugs.debian.org/789497 2) setoptconf: RFS: https://bugs.debian.org/789520 3) dodgy: RFS: https://bugs.debian.org/789617 4) pep8-naming: RFS: https://bugs.debian.org/789680 5) pylint-celery: RFP: ht

Bug#781165: ITP: prospector -- Python code analysis tool

2015-06-22 Thread Daniel Stender
Progress update, 1) requirements-detector: RFS: https://bugs.debian.org/789497 2) setoptconf: RFS: https://bugs.debian.org/789520 3) pep257: RFS: https://bugs.debian.org/789595 4) dodgy: RFS: https://bugs.debian.org/789617 5) pep8-naming: ITP: https://bugs.debian.org/788234 6) pylint-celer

Bug#781165: ITP: prospector -- Python code analysis tool

2015-06-21 Thread Daniel Stender
Prospector packaging project status update: 1) requirements-detector: RFS: https://bugs.debian.org/789497 2) setoptconf: RFS: https://bugs.debian.org/789520 3) pep257: ITP: https://bugs.debian.org/726704 4) dodgy: ITP: https://bugs.debian.org/788206 5) pep8-naming: ITP: https://bugs.debian.o

Bug#781165: ITP: prospector -- Python code analysis tool

2015-06-11 Thread Daniel Stender
On 12.06.2015 07:43, Joseph Herlant wrote: > Hi Daniel, > > FYI pylint-django and pylint-plugins-utils are now in unstable. > > Joseph GREAT! That's really great news! Thank you very much! Best, Daniel -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB

Bug#781165: ITP: prospector -- Python code analysis tool

2015-06-11 Thread Joseph Herlant
Hi Daniel, FYI pylint-django and pylint-plugins-utils are now in unstable. Joseph -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAPQicOwqqn9x0QP-1DZsSC8cmW_VudDJz

Bug#781165: ITP: prospector -- Python code analysis tool

2015-06-09 Thread Daniel Stender
I've worked through the requirements of Prospector, looks good! Status tracker: *** required 1) requirements-detector >= 0.4: ITP (owned by me): https://bugs.debian.org/788208 2) setoptconf >= 0.2.0: ITP (owned by me): https://bugs.debian.org/788212 3) pyyaml: available 4) pep257 >= 0.3.2: I