Bug#669598: RFS: python-django-djblets/0.6.17-1 [ITP] -- Collection of useful extensions for Django
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-django-djblets" Package name: python-django-djblets Version : 0.6.17-1 Upstream Author : Christian Hammond, David Trowbridge, Micah Dowty URL : https://github.com/djblets/djblets License : MIT Section : python It builds those binary packages: python-django-djblets - Collection of useful extensions for Django To access further information about this package, please visit the following URL: http://mentors.debian.net/package/python-django-djblets Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/python-django-djblets/python-django-djblets_0.6.17-1.dsc This package is a dependency of ReviewBoard that I'm packaging. ReviewBoard is a tool for Web-based code reviews. More information about ReviewBoard is available at http://www.reviewboard.org/ djblets was present in Debian some times ago but was removed together with ReviewBoard. I'm trying to reintroduce it in Debian. -- WBR, Dmitry -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120420095531.GA20484@laptop.local
Bug#669599: RFS: python-django-evolution/0.6.7-1 [ITP] -- Schema evolution for the Django web framework
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-django-evolution" * Package name: python-django-evolution Version : 0.6.7-1 Upstream Author : Christian Hammond, Russell Keith-Magee, Ben Khoo * URL : http://code.google.com/p/django-evolution/ * License : BSD Section : python It builds those binary packages: python-django-evolution - Implementation of schema evolution for the Django web framework To access further information about this package, please visit the following URL: http://mentors.debian.net/package/python-django-evolution Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/python-django-evolution/python-django-evolution_0.6.7-1.dsc Package has one pedantic lintian warning (no-upstream-changelog). It was overridden since upstream currently doesn't provide any changelog at all. This package is a dependency of ReviewBoard that I'm packaging. ReviewBoard is a tool for Web-based code reviews. More information about ReviewBoard is available at http://www.reviewboard.org/ -- WBR, Dmitry -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120420103909.GA24849@laptop.local
Bug#669720: RFS/Review: reviewboard/1.6.5-1 [ITP] -- Web-based code review tool
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "reviewboard" * Package name: reviewboard Version : 1.6.5-1 Upstream Author : Christian Hammond, David Trowbridge * URL : http://reviewboard.org/ * License : MIT Section : devel It builds those binary packages: reviewboard - Web-based code review tool reviewboard-doc - ReviewBoard documentation To access further information about this package, please visit the following URL: http://mentors.debian.net/package/reviewboard Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/r/reviewboard/reviewboard_1.6.5-1.dsc Package has a few overridden pedantic/experimental lintian warnings mostly because it has some test data in source tarball (that is not distributed within binary packages). Otherwise it seems to be lintian-clean ReviewBoard is powerful web-based code review tool. It allows one developers to publish code review request either using web browser or special post-review tool for compatible VCS (that is already packaged in python-rbtools package). Other developers can look though changes using web browser, post comments, etc. One of the coolest feature is ability to do some kind of "incremental" reviews: reviewers can display only portion of diff changed since previous review for same patch. More information about ReviewBoard is available at http://reviewboard.org/ Looks like currently Debian archive lacks such tools at all. PS. This package depends on two other packages with python modules that are not currently in Debian. I've already filled RFS for them: python-django-djblets/0.6.17-1 -- #669598 python-django-evolution/0.6.7-1 -- #669599 So until they are uploaded, this is mostly request for review. -- WBR, Dmitry -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120421110719.GA30827@laptop.local
Bug#669598: RFS: python-django-djblets/0.6.17-1 [ITP] -- Collection of useful extensions for Django
On Sun, Apr 22, 2012 at 12:43:42PM +0200, Holger Levsen wrote: > Hi Dmitry, > > On Freitag, 20. April 2012, Dmitry Nezhevenko wrote: > > dget -x > > http://mentors.debian.net/debian/pool/main/p/python-django-djblets/python-d > > jango-djblets_0.6.17-1.dsc > > a quick review reveals that you modified the upstream orig.tar.gz, yet you > don't document this (and why). Please either document this or do'nt do it. Oops. Yes. It was done initially (actually converted from downloaded zip at github). There are no actual changes to upstream sources except that. Anyway I've switched to upstream tarball for it and md5 for orig.tar.gz matches to upstream: http://downloads.reviewboard.org/releases/Djblets/0.6/Djblets-0.6.17.tar.gz I've uploaded fixed pkg to mentors: dget -x http://mentors.debian.net/debian/pool/main/p/python-django-djblets/python-django-djblets_0.6.17-1.dsc Thanks -- WBR, Dmitry signature.asc Description: Digital signature
Re: Help needed [Was: Bug#667325: plink: ftbfs with GCC-4.7]
On Sun, Apr 22, 2012 at 09:45:42PM +0200, Andreas Tille wrote:
> Hi,
>
> I tried to follow the hints to fix this problem but failed.
> Any more skilled C++ programmer than me who might have a clue?
Hi,
It's just incorrect code (sets.cpp):
703 for (int i=0; i count;
708 vector acount;
...
771 vector::iterator i = PP->sample.begin();
772 while ( i != PP->sample.end() )
773 {
774 (*i)->missing = (*i)->flag;
775 ++i;
776 }
As you can see, there is nested declaration here. It's wrong. Looks like
this code was working due to some GCC bug. Other compilers forbids this
too. So just change lines 771-776 to use some other variable name.
Regards
--
WBR, Dmitry
signature.asc
Description: Digital signature
Bug#670204: RFS: pylucene/3.5.0-1 ITA -- Python extension for accessing Java Lucene
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pylucene" * Package name: pylucene Version : 3.5.0-1 Upstream Author : Apache Lucene developers * URL : http://lucene.apache.org/pylucene/ * License : Apache-2 Section : python It builds those binary packages: python-lucene - Python extension for accessing Java Lucene python-lucene-dbg - debugging symbols for python-lucene To access further information about this package, please visit the following URL: http://mentors.debian.net/package/pylucene Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/pylucene/pylucene_3.5.0-1.dsc More information about pylucene is available at http://lucene.apache.org/pylucene/ Current version of pylucene in debian is sid is not installable at all (it still depends on python 2.5). I've asked current maintainer and Jeff agreed that I can take care of it: http://lists.debian.org/debian-devel/2012/04/msg00464.html As about my motivation, I need this package as optional dependency for ReviewBoard package. There are a few issues that I'm unsure how to currently solve: - upstream tarball contains full source of original Java-based lucene, compiles it. Upstream makefile compiles it. Currently debian has no lucene3 at all (there is another ITP for this: #594027), but once it'll be ready, it should be possible to just build-depends on it - package still uses rpath since it needs to be linked to jvm libraries that are actually private. Nothing change here since latest upload. I know that it's bad but another solution is to provide ld.so.conf.d entry that will contains something like /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server. But for me this looks even uglier. - since it links to jvm libraries, it can't be used with java implementations other than default-jre Changes since the last upload: * New maintainer (closes: 670179) * New upstream release * Switch to dpkg-source 3.0 (quilt) format * Switch to machine-readable debian/copyright * Bump debian/compat to 8, drop debian/pycompat * Switch from cdbs to dh * Add watch file * Build for all supported versions of python2 (closes: 581198, 632240) * Rename binary package to python-lucene (closes: 581197) * Add -dbg package -- WBR, Dmitry -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120423230145.GA14135@laptop.local
Bug#669598: RFS: python-django-djblets/0.6.17-1 [ITP] -- Collection of useful extensions for Django
On Wed, Apr 25, 2012 at 01:17:08AM +0200, Jakub Wilk wrote: > (I don't intend to sponsor this package.) Thanks for your comments. I'll try to fix issues > > * Dmitry Nezhevenko , 2012-04-22, 14:03: > >dget -x > >http://mentors.debian.net/debian/pool/main/p/python-django-djblets/python-django-djblets_0.6.17-1.dsc > > "Files: media/js/jquery*" - did you mean "Files: > djblets/media/js/jquery*"? More importantly, I don't see source for > some of these files. Yes. Will fix. But how can I handle these js files? There are actually three versions of "minified" jQuery: jquery-1.3.2.min.js jquery-ui-1.6rc2.min.js jquery-ui-1.6rc5.min.js Looks like only 1.3.2 is used so probably I can drop others. I'll try to use package with jquery from libjs-jquery package (that is version 1.7 in sid) and if I'm lucky probably it will work. If it will work, is it enough to just not use/remove these embedded versions? Or I should repack upstream tarball? > Upstream provides a test suite. Please run it at build time, against > all supported Python versions. Some of these tests are known-to-fail outside of specially configured environment. How this should be handled? -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#669598: RFS: python-django-djblets/0.6.17-1 [ITP] -- Collection of useful extensions for Django
On Wed, Apr 25, 2012 at 12:15:23PM +0200, Jakub Wilk wrote:
> You have the following options:
> 1) Repack the tarball.
> 2) Include the source somewhere in debian/ (in that case please
> mention the fact in the copyright file; otherwise ftp-masters might
> miss it while reviewing the .orig.tar!).
> 3) Ask upstream to provide the source in their tarballs.
>
> Option 3 is preferable, but it also might be the hardest one.
>
> jQuery UI has also a different copyright holder than jQuery proper,
> so if you choose 2) to 3), you need to reflect that in the copyright
> file.
>
> Oh, and looking again at jQuery UI, it's even worse than "just"
> missing source: it's undistributable. The license is GPL or MIT. The
> GPL requirements are obviously not satisfied. The MIT requirements
> ("The above copyright notice and this permission notice shall be
> included in all copies or substantial portions of the Software.")
> are not satisfied either.
Thanks a lot!. I've created bugreport in upstream tracker. And for now
I'll repack tarball and remove these files at all.
> Is it feasible to create such specially configured environment in
> debian/rules? If yes, do it. :)
Well. All failed tests are actually upstream issues. Some files required
for them are not present in orig tarball at all. I've reported this to
upstream. Also one test is probably outdated. For now I think that it's
better to not enable tests until they are fixed.
Thanks a lot for your feedback
--
WBR, Dmitry
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120425111652.GB2859@laptop.local
Re: Bug#670204: RFS: pylucene/3.5.0-1 ITA -- Python extension for accessing Java Lucene
On Wed, Apr 25, 2012 at 12:55:47PM +0200, Jakub Wilk wrote: > (I don't indend to sponsor this package.) > Could you build a transitional package to allow smooth pylucene -> > python-lucene upgrades? Is it needed at all? Looks like package is only present in sid: http://packages.debian.org/search?keywords=pylucene At the same time it's impossible to install it due to python2.5 dependency. I can do this if needed, but is it neede to add transition package that nobody will use? > Out of curiosity, what is NUM_FILES variable for? pylucene is python native python extension (.so) that is generated from java sources. NUM_FILES specifies how much of .cpp files to generate. Thanks for review. I'll fix issues. -- WBR, Dmitry -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120425112235.GC2859@laptop.local
Re: Bug#669598: RFS: python-django-djblets/0.6.17-1 [ITP] -- Collection of useful extensions for Django
On Fri, Apr 20, 2012 at 12:55:36PM +0300, Dmitry Nezhevenko wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "python-django-djblets" > > Package name: python-django-djblets > Version : 0.6.17-1 > Upstream Author : Christian Hammond, David Trowbridge, Micah Dowty > URL : https://github.com/djblets/djblets > License : MIT > Section : python > > It builds those binary packages: > > python-django-djblets - Collection of useful extensions for Django > > To access further information about this package, please visit the > following URL: > > http://mentors.debian.net/package/python-django-djblets > > Alternatively, one can download the package with dget using this > command: > I've addressed all issues reported by Jakub except tests one: - upstream tarball is now repacked with all JQuery files removed. - changed debhelper dependency to > 8 - changed package priority to optional - Use Expat license instead of MIT in debian/copyright, added feedparser license - Removed --buildsystem=python_distutils Running test suite is not currently possible. Issues reported to upstream. Once they will be fixed, I'll try to run them. Updated package: dget -x http://mentors.debian.net/debian/pool/main/p/python-django-djblets/python-django-djblets_0.6.17+dfsg-1.dsc Thanks -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#669599: RFS: python-django-evolution/0.6.7-1 [ITP] -- Schema evolution for the Django web framework
On Wed, Apr 25, 2012 at 01:33:13AM +0200, Jakub Wilk wrote: > (I don't intend to sponsor this package.) > > * Dmitry Nezhevenko , 2012-04-20, 13:39: > >http://mentors.debian.net/debian/pool/main/p/python-django-evolution/python-django-evolution_0.6.7-1.dsc > > Why priority extra? fixed. Should be optional > > I'd use "debhelper (>= 8)" instead of "debhelper (>= 8.0.0)", for > easier backporting. done > > What is python-feedparser dependency for? removed. It's mistake > > AFAICS you don't need --buildsystem=python_distutils, dh will detect it > automatically. removed > > Upstream provides a test suite. Please run it at build time, against all > supported Python versions. > done. I've reuploaded package to mentors. Same URL: dget -x http://mentors.debian.net/debian/pool/main/p/python-django-evolution/python-django-evolution_0.6.7-1.dsc -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#670204: RFS: pylucene/3.5.0-1 ITA -- Python extension for accessing Java Lucene
On Wed, Apr 25, 2012 at 12:55:47PM +0200, Jakub Wilk wrote: > (I don't indend to sponsor this package.) > > * Dmitry Nezhevenko , 2012-04-24, 02:01: > >http://mentors.debian.net/debian/pool/main/p/pylucene/pylucene_3.5.0-1.dsc > > I'd use "debhelper (>= 8)" instead of "debhelper (>= 8.0.0)". added > > Could you build a transitional package to allow smooth pylucene -> > python-lucene upgrades? I'm not sure that it's really needed, but added > Please trap errors from "make clean" in debian/rules. done > > PYTHON_DEFAULT, USR_SHARE and PYTHON_SHAREDDIR variables appear to > be unused. Removed > > Out of curiosity, what is NUM_FILES variable for? Added comment > AFAIK dh_installchangelog installs CHANGES file automatically, so > the override is not needed. > removed I've reuploaded package to mentors dget -x http://mentors.debian.net/debian/pool/main/p/pylucene/pylucene_3.5.0-1.dsc -- WBR, Dmitry signature.asc Description: Digital signature
Bug#670619: RFS: django-pipeline/1.2.2.1-1 [ITP] -- Asset packaging library for Django
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "django-pipeline" * Package name: django-pipeline Version : 1.2.2.1-1 Upstream Author : Andreas Pelme, Timothée Peignier * URL : https://github.com/cyberdelia/django-pipeline * License : MIT/Expat Section : python It builds those binary packages: python-django-pipeline - Asset packaging library for Django python-django-pipeline-doc - Documentation for Django Pipeline library To access further information about this package, please visit the following URL: http://mentors.debian.net/package/django-pipeline Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/d/django-pipeline/django-pipeline_1.2.2.1-1.dsc This is a required dependency for next version of ReviewBoard that I'm trying to package. -- WBR, Dmitry -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120427112206.GA27109@laptop.local
Re: Bug#669598: RFS: python-django-djblets/0.6.17-1 [ITP] -- Collection of useful extensions for Django
On Fri, Apr 20, 2012 at 12:55:36PM +0300, Dmitry Nezhevenko wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "python-django-djblets" > > Package name: python-django-djblets > Version : 0.6.17-1 > Upstream Author : Christian Hammond, David Trowbridge, Micah Dowty > URL : https://github.com/djblets/djblets > License : MIT > Section : python > > It builds those binary packages: > > python-django-djblets - Collection of useful extensions for Django Hi, I've addressed latest issue reported by Jakub Wilk. Also I've renamed source package to djblets to match upstream name. Binary package is still named python-django-djblets to match python policy. Unfortunately I've found that latest stable release of ReviewBoard doesn't work with Django >= 1.4 so I've decided to package 0.7 development snapshot that works pretty well. And this version requires development version of Djblets. Also I've added running of available test during build time. That is now possible with version 0.7 So updated package is available at: http://mentors.debian.net/package/djblets Or dget: dget -x http://mentors.debian.net/debian/pool/main/d/djblets/djblets_0.7~git20120402+dfsg-1.dsc But now it depends on django-pipeline that I've packaged and looking for sponsor too (RFS: #670619) Thanks -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#669599: RFS: python-django-evolution/0.6.7-1 [ITP] -- Schema evolution for the Django web framework
On Fri, Apr 20, 2012 at 01:39:13PM +0300, Dmitry Nezhevenko wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "python-django-evolution" > > * Package name: python-django-evolution >Version : 0.6.7-1 >Upstream Author : Christian Hammond, Russell Keith-Magee, Ben Khoo > * URL : http://code.google.com/p/django-evolution/ > * License : BSD >Section : python > > It builds those binary packages: > >python-django-evolution - Implementation of schema evolution for the > Django web framework > I've renamed source package to match upstream name and addressed all issues reported here before: - priority is changed to optional - fixed debhelper dependency (now its >= 8 instead of 8.0.0) - removed unused python-feedparser dependency. - removed --buildsystem=python_distutils - test suite is executed during package build So new package is available at: http://mentors.debian.net/package/django-evolution or using dget: http://mentors.debian.net/debian/pool/main/d/django-evolution/django-evolution_0.6.7-1.dsc Thanks -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#669720: RFS/Review: reviewboard/1.6.5-1 [ITP] -- Web-based code review tool
On Sat, Apr 21, 2012 at 02:07:22PM +0300, Dmitry Nezhevenko wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "reviewboard" > > * Package name: reviewboard >Version : 1.6.5-1 >Upstream Author : Christian Hammond, David Trowbridge > * URL : http://reviewboard.org/ > * License : MIT >Section : devel > > It builds those binary packages: > >reviewboard - Web-based code review tool >reviewboard-doc - ReviewBoard documentation > Hi, It was observed that current release of ReviewBoard doesn't work well with Django >= 1.4. The most important issue is that admin interface doesn't work at all. So I've decided to upgrade debian package to latest snapshot of dev. version 1.7. Anyway even upstream uses it as their production ReviewBoard instance Also I've reworked package to address various issues that I've found: - repackage archive to remove non-DFSG JavaScript files from them - python modules are now installed to /usr/share/reviewboard - priority in debian/control is set to optional - python dependency is changed from python-all to python - added python-lucene to Suggests: - use sphinxdoc helper - updated debian/copyright - most of javascript files are now symlinks to corresponding libjs-* packages Updated package is available at: http://mentors.debian.net/package/reviewboard or using dget: http://mentors.debian.net/debian/pool/main/r/reviewboard/reviewboard_1.7~git20120425+dfsg-1.dsc -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#669598: RFS: python-django-djblets/0.6.17-1 [ITP] -- Collection of useful extensions for Django
On Fri, Apr 27, 2012 at 03:46:09PM +0200, Jakub Wilk wrote: > * Dmitry Nezhevenko , 2012-04-27, 15:31: > >I've renamed source package to djblets to match upstream name. > >Binary package is still named python-django-djblets to match > >python policy. > > Erm, in accordance with Python Policy §2.2, the binary package name > should be python-djblets, NOT python-django-djblets. Yes. I know. But at the same time it looks like this is a common practice to name packages for django as python-django. apt-cache search python-django shows something around 60 packages named as python-django. Anyway I can rename it if needed. > > > dget -x > > http://mentors.debian.net/debian/pool/main/d/djblets/djblets_0.7~git20120402+dfsg-1.dsc > > This re-introduces the minified JavaScript code. Oops. Sorry. will take a look... -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#670619: RFS: django-pipeline/1.2.2.1-1 [ITP] -- Asset packaging library for Django
On Fri, Apr 27, 2012 at 04:02:19PM +0200, Jakub Wilk wrote: > * Dmitry Nezhevenko , 2012-04-27, 14:22: > > dget -x > > http://mentors.debian.net/debian/pool/main/d/django-pipeline/django-pipeline_1.2.2.1-1.dsc > > As per Python Policy §2.2, the binary package name should be > python-pipeline. Except that this name (not only Debian package > name, but also Python module name) is already taken. Oops! Hmm. How I should handle it? > > lintian4python reports (among others): > > e: django-pipeline source: python-module-but-no-python-depends > python-django-pipeline I'll take a look to this and other lintian4python errors thanks -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#670619: RFS: django-pipeline/1.2.2.1-1 [ITP] -- Asset packaging library for Django
On Fri, Apr 27, 2012 at 05:20:30PM +0200, Jakub Wilk wrote: > * Dmitry Nezhevenko , 2012-04-27, 17:09: > >>> dget -x > >>> http://mentors.debian.net/debian/pool/main/d/django-pipeline/django-pipeline_1.2.2.1-1.dsc > >>As per Python Policy §2.2, the binary package name should be > >>python-pipeline. Except that this name (not only Debian package > >>name, but also Python module name) is already taken. Oops! > >Hmm. How I should handle it? > > Ask upstream to rename the module to something less generic. I've asked both upstreams: http://code.google.com/p/python-pipeline/issues/detail?id=1 https://github.com/cyberdelia/django-pipeline/issues/101 But I'm not sure that this will be solved such way... -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#670619: RFS: django-pipeline/1.2.2.1-1 [ITP] -- Asset packaging library for Django
On Fri, Apr 27, 2012 at 04:02:19PM +0200, Jakub Wilk wrote: > * Dmitry Nezhevenko , 2012-04-27, 14:22: > > dget -x > > http://mentors.debian.net/debian/pool/main/d/django-pipeline/django-pipeline_1.2.2.1-1.dsc > > e: django-pipeline source: python-module-but-no-python-depends > python-django-pipeline > This one is fixed. I've reuploaded package. Not sure for now how to deal with name change. Waiting for upstream feedback -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#669598: RFS: python-django-djblets/0.6.17-1 [ITP] -- Collection of useful extensions for Django
On Fri, Apr 27, 2012 at 03:46:09PM +0200, Jakub Wilk wrote: > * Dmitry Nezhevenko , 2012-04-27, 15:31: > >I've renamed source package to djblets to match upstream name. > >Binary package is still named python-django-djblets to match > >python policy. > > Erm, in accordance with Python Policy §2.2, the binary package name > should be python-djblets, NOT python-django-djblets. I've renamed binary package to python-djblets. > > > dget -x > > http://mentors.debian.net/debian/pool/main/d/djblets/djblets_0.7~git20120402+dfsg-1.dsc > > This re-introduces the minified JavaScript code. > Fixed it again. It was mistake in get-git-snapshot-source step. Sorry. Reuploaded package to mentors. Should be same dget url. -- WBR, Dmitry signature.asc Description: Digital signature
Re: Bug#669599: RFS: python-django-evolution/0.6.7-1 [ITP] -- Schema evolution for the Django web framework
On Fri, Apr 27, 2012 at 03:35:16PM +0200, Jakub Wilk wrote: > * Dmitry Nezhevenko , 2012-04-27, 15:47: > > http://mentors.debian.net/debian/pool/main/d/django-evolution/django-evolution_0.6.7-1.dsc > > lintian4python reports (among others): > e: python-django-evolution: pyflakes-undefined-name > usr/share/pyshared/django_evolution/evolve.py:72: sql_file_name I've sent patch to upstream and uploaded new package. Looks like other pyflakes warnings are less important. dget url should be same -- WBR, Dmitry signature.asc Description: Digital signature
Bug#832934: RFS: pylucene/4.10.1+dfsg-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pylucene" * Package name: pylucene Version : 4.10.1+dfsg-1 Upstream Author : The Apache Software Foundation * URL : http://lucene.apache.org/pylucene/ * License : Apache-2.0 Section : python It builds those binary packages: python-lucene - Python extension for accessing Java Lucene To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pylucene Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pylucene/pylucene_4.10.1+dfsg-1.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: * New upstream release (Closes: #740992) * Repack upstream tarball to get rid of minified JS code and embedded JAR files * Bump debian/compat to 9, no changes required * Bump Standards-Version to 3.9.8, no changes required * Remove old pylucene transition package * Drop obsolete X-Python-Version * Drop embedded copy of lucene-java-4.10 in binary package (add Depends: liblucene4.10-java) * Drop unique_classes.patch patch (not needed anymore) * Enable tests * Apply security hardening in build flags (Closes: #740994) * Switch to -dbgsym package for debug symbols * Configure 'uscan(1)' to verify upstream signature on source releases (thanks to Ben Finney) (Closes: #741062, #741063) This upload will close followed bugs: #740992 (wishlist): src:pylucene: New upstream version available, 4.6.1 #740994 (normal): src:pylucene: Apply security hardening in build flags #741062 (minor): src:pylucene: Add program to fetch upstream signing keyring #741063 (minor): src:pylucene: Configure 'uscan(1)' to verify upstream signature on source releases -- WBR, Dmitry
Bug#832934: RFS: pylucene/4.10.1+dfsg-1
On Sat, Jul 30, 2016 at 08:49:06AM +, Gianfranco Costamagna wrote: > I'm willing to sponsor this, but I have some questions/showstoppers: Thanks a lot! > > 1) licenses: some licenses are BSD, and there are some missing copyrights. > please add them (grep -Ri license and grep -Ri copyright might give you a > start, > and licensecheck might help too) I'll check. > 2) why can't you use lucene from Debian? sounds like an embedded copy, even if > I stopped looking at the name, not the content > we have liblucene*-java > 5) > +Build-Depends: debhelper (>= 9), dh-python, ant, curl, jcc, default-jdk, > python-setuptools (>= 0.6b3), python-all-dev (>= 2.6.6-3), > + antlr3, liblucene4.10-java, libasm4-java Now (new version) actually uses liblucene4.10-java from Debian both as Build-Depends and runtime dependency. And that's actually why I've added more Build-Depends. lucene-java-4.10.1 is just there because it's in upstream tarball. I was trying to avoid repackaging of upstream tarball (until I found minified JS files). It should be possible to completely exclude whole 'lucene-java-4.10.1' directory (and probably embedded copy of jcc source) from repacked orig.tar.gz. Should I do this? > 3) snowball, can you please try to use the system snowball? > note: I tried with my lucene++ package, and I failed because of patches As far as I understand, pylucene don't use it (at least directly). Since it's inside lucene-java-4.10.1 that is completely not used. > + > 4) > pylucene-4.10.1+dfsg/debian/source/include-binaries ^^ please remove ok > please document why you have added a lot of new build-dependencies > I've mentioned about liblucene4.10-java in changelog: * Drop embedded copy of lucene-java-4.10 in binary package (add Depends: liblucene4.10-java) Is it enough? Will check other dependencies -- WBR, Dmitry signature.asc Description: PGP signature
Bug#832934: RFS: pylucene/4.10.1+dfsg-1
On Sat, Jul 30, 2016 at 09:56:30AM +, Gianfranco Costamagna wrote: > I usally prefer to avoid a repack wheneveer possible, but since you already > did > it I would just remove that too. Removed both of them. > c) about additional dependencies I see added: > Build-Depends: dh-python, curl, antlr3, liblucene4.10-java, libasm4-java > > I understand dh-python, liblucene4.10-java, but I don't see a rationale for > the others. curl removed. antlr3 and libasm4-java are really needed. Shipped in upstream tarball: ./lucene-java-4.10.1/lucene/expressions/lib/asm-4.1.jar ./lucene-java-4.10.1/lucene/expressions/lib/antlr-runtime-3.5.jar ./lucene-java-4.10.1/lucene/expressions/lib/asm-commons-4.1.jar As far as I understand they are needed by JCC to properly generate python wrappers. > you seem to have an embedded jcc copy... > not sure if possible, but dropping it brings the orig tarball size around 60KB > (the build is good after dropping it removed. > e) > python-lucene: broken-symlink > /usr/lib/python2.7/dist-packages/lucene/extensions.jar -> > /build/pylucene-E6rl3V/pylucene-4.10.1+dfsg/debian/python-lucene/usr/share/python-lucene/extensions.jar > > you seem to have a broken symlink. fixed I've uploaded fixed version of pylucene package to mentors: https://mentors.debian.net/package/pylucene dget -x https://mentors.debian.net/debian/pool/main/p/pylucene/pylucene_4.10.1+dfsg-1.dsc Thanks a lot! -- WBR, Dmitry signature.asc Description: PGP signature
