Re: Future of django-pagination in Debian

[Paul Wise]

On Wed, Feb 12, 2014 at 11:02 AM, Andrew Starr-Bochicchio wrote:

> Any one have any opinions?

How does the upstream Django community recommend to do pagination?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
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/CAKTje6EzdGGZ-860=3eRC=5rn-oztuxbdajex3pok7ohx_7...@mail.gmail.com

Future of django-pagination in Debian

[Andrew Starr-Bochicchio]

The Debian package of django-pagination was orphaned last year. [0] I
hadn't noticed until someone stepped up and actually filed an orphan
bug just the other week. [1] I intend to adopt it for the DPMT, and I
have a release ready to upload in the team's svn repo.

In the process of preparing the upload, I came across the fork you did
incorporating bug fixes and translations the the original maintainer
had left sitting around. [2] As upstream hasn't made a commit in ~4
years, your work it probably the best way forward.

I wanted to solicit your (and the DPMT's) opinion on how to best
handle this from the Debian side. There are a few options. The first
is simply upgrading to your fork directly, which would be the most
user friendly. Though the top level package name was changed from
`pagination` to `linaro-django-pagination`. [3] That would suggest
that a new source package would be in order. If I packaged
linaro-django-pagination, should we just ask for the removal of
django-pagination, or keep it around?

Any one have any opinions?


[0] http://packages.qa.debian.org/d/django-pagination/news/20130505T150425Z.html
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737294
[2] https://github.com/zyga/django-pagination
[3] https://pypi.python.org/pypi/linaro-django-pagination/

Thanks!

-- Andrew Starr-Bochicchio

   Ubuntu Developer 
   Debian Developer 
   PGP/GPG Key ID: D53FDCB1


-- 
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/cal6k_aweynfsjscfcz+-u4tephw5z-ugdhg7wydyqoyk5pg...@mail.gmail.com

Introductions

[Michael Hall]

Hello list,

I am a python developer with a large focus on webapps (Django
specifically), as well as a long history of working on Ubuntu webapp
projects.  I recently started to contribute to the debian-newmaint
project, and am working on packaging the Django testing add-on Model
Mommy for use in adding unit tests to the website.

I currently work for Canonical on the Community team, hence my interest
in a community-focused project in Debian as opposed to something more
technical/infrastructure related.  I'm looking forward to being more
involved in the Debian community and community processes.

-- 
Michael Hall
mhall...@gmail.com


-- 
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/52fa70bb.3040...@gmail.com

Handling a package compatible with Python 3.3 but not 3.4

[Barry Warsaw]

A long while back we had several discussions about the possibility that a
package installed into /usr/lib/python3 would support one version of Python 3
but not all of them.  IIRC, we never came to any good solution.

Now I have both a test case and a crappy solution. ;)

Genshi 0.7 supports Python 3.3 but not 3.4 yet because of
.  While we're waiting for upstream to
release a compatible version, I've done the following in Ubuntu, and in the
DPMT svn for genshi (not yet uploaded).

-d/control-
X-Python3-Version: >= 3.3, << 3.4
-d/control-

This is needed to even build the package when 3.3 and 3.4 is supported.
Without this, the test suite failure causes the package to ftbfs.

But this isn't quite enough because although the package builds and installs,
it *also* is importable in Python 3.4, though of course it will not work.  So
I also added the following quilt patch:

-d/p/disable-python34.patch-
Description: Raise an ImportError when trying to import genshi in a
  Python > 3.3, since it is not yet compatible with Python 3.4.
  Remove this when upstream ticket 582 is resolved.
  http://genshi.edgewall.org/ticket/582
Author: Barry Warsaw 
Forwarded: not-needed

--- a/genshi/__init__.py
+++ b/genshi/__init__.py
@@ -22,5 +22,9 @@
 __docformat__ = 'restructuredtext en'
 __version__ = '0.7'
 
+import sys
+if not sys.version_info < (3,4):
+raise ImportError('See http://genshi.edgewall.org/ticket/582')
+
 from genshi.core import *
 from genshi.input import ParseError, XML, HTML
-d/p/disable-python34.patch-

Yes, I hate myself for this, but absent any principled way of handling this
(i.e. simple to set up using the appropriate Python helpers without making
d/rules a horrible mess, and easy to undo), I think this is a workable
solution.  I consider this temporary, and it will be quite easy to back out
once upstream is compatible with Python 3.4.

Before I upload, I wanted to get your feedback.

Cheers,
-Barry


signature.asc
Description: PGP signature

Re: HELP: something other than dh_python2 fails to install files if an additional binary package is added

[Andrew Starr-Bochicchio]

On Tue, Feb 11, 2014 at 4:21 AM, Andreas Tille  wrote:
> On Tue, Feb 11, 2014 at 09:48:43AM +0100, Piotr Ożarowski wrote:
>> [Andreas Tille, 2014-02-11]
>> > directory.  I can reproduce this behavious by simply deleting the
>> > python-pysam-tests paragraph in debian/control.
>>
>> this part is very important
>
> Obviously.
>
>> > It seems that there is some problem in dh_python (or a related tool
>>
>> argh! dh_python2 doesn't install files :-P
>
> So what exactly *stopped* installing files since a new binary package
> was added?

Normally, when you produce a single binary package, the things get
installed into debian/$package_name. If you create a second binary
package by creating a new paragraph in debian/control and doing
nothing else, the files are installed into debian/tmp. So you then
need to move the files that you want to end up in each package to the
corresponding directories.

>From `man dh_install`:

> maybe you have a large package that builds multiple binary packages. You can
> use the upstream Makefile to install it all into debian/tmp, and then use 
> dh_install
> to copy directories and files from there into the proper package build 
> directories.

What it means by "the proper package build directories" is that by the
end of the build process, everything that will be in the resulting
foo.deb will be found in debian/foo. The files that will end up in
foo-data.deb will be found in debian/foo-data.

-- Andrew Starr-Bochicchio

   Ubuntu Developer 
   Debian Developer 
   PGP/GPG Key ID: D53FDCB1


--
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/cal6k_aypeww6ltta00afky2wccevvl4rrmstejjazu2wiwf...@mail.gmail.com

Re: HELP: dh_python2 fails to install files if an additional binary package is added

[Nicolas CANIART]

I think this is what the PYBUILD_NAME variable is for. Set it to "pysam"
(pybuild handles the python3?- prefix for you).

Or use a .install file. I think that you must omit the python3?- prefix
here either. I realize just now that this may be the problem I faces
yesterday. Can someone confirm.

Regards.

Le 11 févr. 2014 09:39, "Andreas Tille"  a écrit :

> Hi,
>
> I'm working on python-pysam in the Debian Med team at
>
>git://anonscm.debian.org/debian-med/pysam.git
>
> The package was created nicely until I added an additional binary
> package python-pysam-tests covering the test data in a separate file
> (since it us usually not needed but might be helpful to test the data).
>
> Once I have added the additional paragraph
>
>   Package: python-pysam-tests
>   ...
>
> the main package python-pysam remains empty (except of the
>/usr/share/doc/python-pysam
> directory.  I can reproduce this behavious by simply deleting the
> python-pysam-tests paragraph in debian/control.
>
> It seems that there is some problem in dh_python (or a related tool
> which gets disturbed if you add an "unexpected" binary package not
> covering any Python modules.
>
> I'd like to discuss this here before filing a stupid bug report.
>
> Any idea what might have happened?
>
> Kind regards
>
>  Andreas.
>
> --
> http://fam-tille.de
>
>
> --
> 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/20140211083811.gb6...@an3as.eu
>

Re: HELP: something other than dh_python2 fails to install files if an additional binary package is added

[Andreas Tille]

Hi Piotr,

On Tue, Feb 11, 2014 at 10:21:43AM +0100, Piotr Ożarowski wrote:
> > this part is very important
> > 
> > > It seems that there is some problem in dh_python (or a related tool
> > 
> > argh! dh_python2 doesn't install files :-P
> 
> `echo '/usr/lib/python2.*/*' >> debian/python-pysam.install` fixes it,

Thanks.

> PS please fix clean target, it's hard to debug if you cannot build a
> package twice in a row

Sorry, it was on my agenda to keep the Cython created files from the
original tarball and move them back.  I just took over some preliminary
packaging and I'm slowly fighting through.  This issue is solved now.

I'm not yet really happy with the clean target, since it needs a quilt
patch to be applied (do_not_use_distribute_setup.patch) to run smoothly
since otherwise it insists on downloading distribute-0.6.34.tar.gz.
Is there any suggested trick to even prevent this?

Thanks for your always prompt help

  Andreas.

-- 
http://fam-tille.de


-- 
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/20140211103907.gg6...@an3as.eu

Re: HELP: something other than dh_python2 fails to install files if an additional binary package is added

[Andreas Tille]

On Tue, Feb 11, 2014 at 09:48:43AM +0100, Piotr Ożarowski wrote:
> [Andreas Tille, 2014-02-11]
> > directory.  I can reproduce this behavious by simply deleting the
> > python-pysam-tests paragraph in debian/control.
> 
> this part is very important

Obviously.
 
> > It seems that there is some problem in dh_python (or a related tool
> 
> argh! dh_python2 doesn't install files :-P

So what exactly *stopped* installing files since a new binary package
was added?

Kind regards

Andreas. 

-- 
http://fam-tille.de


-- 
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/20140211092137.gc6...@an3as.eu

Re: HELP: something other than dh_python2 fails to install files if an additional binary package is added

[Piotr Ożarowski]

[Piotr Ożarowski, 2014-02-11]
> [Andreas Tille, 2014-02-11]
> > directory.  I can reproduce this behavious by simply deleting the
> > python-pysam-tests paragraph in debian/control.
> 
> this part is very important
> 
> > It seems that there is some problem in dh_python (or a related tool
> 
> argh! dh_python2 doesn't install files :-P

`echo '/usr/lib/python2.*/*' >> debian/python-pysam.install` fixes it,
please read `man dh_install` if you want to know why files ended in
debian/tmp

PS please fix clean target, it's hard to debug if you cannot build a
package twice in a row
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645


-- 
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/20140211092143.gc3...@sts0.p1otr.com

Re: HELP: something other than dh_python2 fails to install files if an additional binary package is added

[Piotr Ożarowski]

[Andreas Tille, 2014-02-11]
> directory.  I can reproduce this behavious by simply deleting the
> python-pysam-tests paragraph in debian/control.

this part is very important

> It seems that there is some problem in dh_python (or a related tool

argh! dh_python2 doesn't install files :-P
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645


-- 
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/20140211084843.gb3...@sts0.p1otr.com

HELP: dh_python2 fails to install files if an additional binary package is added

[Andreas Tille]

Hi,

I'm working on python-pysam in the Debian Med team at

   git://anonscm.debian.org/debian-med/pysam.git

The package was created nicely until I added an additional binary
package python-pysam-tests covering the test data in a separate file
(since it us usually not needed but might be helpful to test the data).

Once I have added the additional paragraph

  Package: python-pysam-tests
  ...

the main package python-pysam remains empty (except of the
   /usr/share/doc/python-pysam
directory.  I can reproduce this behavious by simply deleting the
python-pysam-tests paragraph in debian/control.

It seems that there is some problem in dh_python (or a related tool
which gets disturbed if you add an "unexpected" binary package not
covering any Python modules.

I'd like to discuss this here before filing a stupid bug report.

Any idea what might have happened?

Kind regards

 Andreas.

-- 
http://fam-tille.de


-- 
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/20140211083811.gb6...@an3as.eu