Re: Introducing myself

2013-06-17 Thread Etienne Millon 
* Jakub Wilk  [130617 08:32]:
> * Etienne Millon , 2013-06-14, 15:37:
> >I recently offered to help Carlos Galisteo with feedparser (a
> >dependency of rss2email which I maintain), and he proposed me to
> >take care of the package within the DPMT (see #664199 and
> >#711916).
> 
> I had a look at the NMU you proposed:
> 
> Did you mean "Convert to dh" instead of "Convert to dh_python2"? The
> package in unstable already uses dh_python2... But anyway, "changing
> the packaging style in NMUs is discouraged" (DevRef ยง5.11.1).
> 
> Now that you're going to become a (co-)maintainer, you can of course
> make any changes you want, so I'm mentioning it here only as word of
> advice for the future. :)

About the changelog, I agree that it consists in porting to dh; I
picked the wording from the Ubuntu changes.

As for the packaging changes, I thought that cherry-picking from
Ubuntu was a way of improving the packaging too, but you're right it
should be left to the maintainer.

> >Right now I've sent a request to join the team on alioth (login:
> >emillon-guest)
> 
> Welcome to the team!

Thanks ! I'll prepare an upload soon.

-- 
Etienne Millon


-- 
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/20130617174043.GA14786@klow

Re: RFS: python-keyring 1.4-1

2013-06-17 Thread Sebastian Ramacher 
On 2013-06-14 14:55:58, Dmitry Shachnev wrote:
> Thanks for your review.
> 
> On Wed, Jun 12, 2013 at 2:34 AM, Sebastian Ramacher
>  wrote:
> > I'd put the script in /usr/share/doc/python-keyring or
> > /usr/share/python-keyring. There's no need to put it in /usr/bin.
> 
> It's now in /usr/share/python-keyring.

I think lines 48 and 49 can be removed too.

> > Also, I wouldn't copy the the master password from the old keyring to the
> > new one. If the user already created a new Crypto keyring with a different
> > password, this would destroy it. I'd also make it more explicit when asking
> > for the password that it's the password for the old keyring.
> 
> Fixed.
> 
> >> Note that it fails to build when python3-secretstorage is installed
> >> (see upstream #102), but there is no problem when you are building in
> >> chroot.
> >
> > So either
> >  - get ImportKiller fixed,
> >  - disable ImportKiller based tests for Python 3.3 for now or
> >  - add python3-secretstorage and python3-gi to Build-Conflicts.
> 
> ImportKiller is fixed now.
> 
> > What's the status of all the other tests? Many tests are skipped because
> > of missing dependencies.
> 
> Gnome-keyring-daemon refuses to run in xvfb. As I do not know other
> Secret Service implementations, it's currently impossible to test
> GNOME and Secret Service backends (libsecret's upstream testsuite has
> some code for mocking Secret Service, but I didn't yet have time to
> test it).

If we can't run them reliably I'd rather see them disabled.

> Python-fs is too old in Debian (python-keyring needs at least 0.4), so
> this test can't be run also.

What about the gdata tests?


It currently FTBFS twice in a row:
| dpkg-source: info: local changes detected, the modified files are:
|  python-keyring-1.4/keyring.egg-info/PKG-INFO
|  python-keyring-1.4/keyring.egg-info/SOURCES.txt
|  python-keyring-1.4/keyring.egg-info/dependency_links.txt
|  python-keyring-1.4/keyring.egg-info/entry_points.txt
|  python-keyring-1.4/keyring.egg-info/requires.txt
|  python-keyring-1.4/keyring.egg-info/top_level.txt

Regards
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature

Re: Joining Python Modules Packaging Team

2013-06-17 Thread Brian May 
On 9 June 2013 08:56, Jakub Wilk  wrote:

> Speaking of which, django-ajax-selects debian/rules does this:
>
> cp -r ajax_select/static debian/django-ajax-selects/**
> usr/share/pyshared/ajax_select
>
> /usr/share/pyshared is an implementation detail of Python helpers; you
> should not rely on its existence. (In fact, now that we support only one
> Python version, I hope we get rid of it soon.)


Hmm. Looks like I don't need that line any more anyway, these files get
appear to be installed automatically, presumably by dh_python2 (as they
belong in the same directory as the python code).
-- 
Brian May