Unowned Files after purge

2014-11-27 Thread Ross Gammon
Hi,

I recently switched the gramps package to python 3, and now it seems
that the prerm removal of __pycache__ etc. provided automatically by
dh_python is not working:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771095

A quick search on the net revealed that gramps is not the only package
in this situation.

Is this likely to be a bug in dh_python that I should report, or is it
something already known that I missed?

Cheers,

Ross


-- 
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/54776cc4.5000...@the-gammons.net



Re: Unowned Files after purge

2014-11-29 Thread Ross Gammon
On 11/28/2014 12:11 AM, Piotr Ożarowski wrote:
> [Piotr Ożarowski, 2014-11-28]
>> [Ross Gammon, 2014-11-27]
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771095
>> 
>> "docgen.gpr.py"? seriously?
>> 
>> Yes, it's a "bug" in py3clean. I will fix it before Jessie
> 
> or rather in Python 3 itself¹. I guess I will have to add a hack
> to py3clean anyway (to clean after it)
> 
> [¹] $ touch foo.bar.py $ python3 -m py_compile foo.bar.py $ test -f
> __pycache__/foo.cpython-34.pyc && echo 'huh?'
> 

Thank Piotr for investigating that so fast. I will submit a bug so
that there is one less thing for you to do.

Cheers,

Ross


-- 
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/547a0f70.2010...@the-gammons.net



Re: Unowned Files after purge

2014-11-29 Thread Ross Gammon
On 11/29/2014 07:30 PM, Piotr Ożarowski wrote:
> [Ross Gammon, 2014-11-29]
>> Thank Piotr for investigating that so fast. I will submit a bug so
>> that there is one less thing for you to do.
> 
> no need, I already reported it upstream¹ and added a workaround to py3clean²
> 
> [¹] http://bugs.python.org/issue22966
> [²] 
> https://alioth.debian.org/scm/loggerhead/pkg-python/python3-defaults-debian/revision/320
> 

Just in time :-) Thanks again.


-- 
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/547a1224.80...@the-gammons.net



Re: Bug#770149: python-instagram

2015-04-11 Thread Ross Gammon
Hi Jörg,

I am glad to see you working on this, as one of my packages will
eventually depend on python-instagram!

On 04/06/2015 11:31 PM, Jörg Frings-Fürst wrote:

> 
> 
> Please can someone review this package[1].
> 
> Thanks.
> 
> CU
> Jörg
> 
> [1] 
> http://mentors.debian.net/debian/pool/main/p/python-instagram/python-instagram_1.3.0+git20150406~e885e7d-1.dsc
> 
> 

Therefore, I thought I would give you a review for what it is worth (I
am not a DD so I cannot sponsor it):

- The package builds fine in a chroot and the clean target is working fine.
- piuparts reports no problems.
- Lintian is happy.
- The watch file is not working, but that is okay as upstream do not do
releases or tags.

I am wondering why d/control has "Provides: ${python:Provides}"? Python
Policy mentions it (and generally discourages its use). Mainly I am
curious about it.

One minor comment about d/copyright is that according to the upstream
README & LICENSE files, the copyright says "2014, Facebook, Inc." (not
Instagram, and not in 2015)

I also noticed that setup.py still says MIT (not reflecting the recent
change to BSD). You might want to report that upstream.

Here's hoping you find a sponsor soon.

Regards,

Ross




signature.asc
Description: OpenPGP digital signature


Re: python-support removal effort

2015-09-22 Thread Ross Gammon
On 09/03/2015 08:26 PM, Andrey Rahmatullin wrote:
> We are down to slightly more than 100 bugs (that includes several packages
> that are RC-buggy and dozen or two packages in open transitions, so there
> is slightly less things to work on right now) and we need YOUR help.
> 
> For majority of packages the work is simple and doesn't require Python
> packaging knowledge. The full procedure is documented on wiki but in the
> reality most packages just need B-D adjustment and adding --with python2,
> replacing dh_pysupport with dh_python2 or removing
> DEB_PYTHON_SYSTEM=pysupport (and some trivial debdiff checking and
> testing). You can skip packages that are more complicated than that.
> 

My first python-support NMU is ready for sponsorship on mentors:
http://mentors.debian.net/package/prelude-notify

I have sent an nmudiff to the bug, and also put the mentors link on the
whiteboard.

I will try and tick a few off here and there over the next weeks. Is it
enough if I just put the mentors link on the whiteboard? If required I
will file RFS bugs, but filling in the bug metadata takes time!

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature


Moving dominate to DPMT

2017-03-16 Thread Ross Gammon

Hi All,

This is just a courtesy note that I plan to move dominate from 
collab-maint to the DPMT repository.


It was my original plan to have it in DPMT, but my sponsor was keen to 
upload before I had my request to join the team approved. It was set up 
following the DPMT wiki - so it uses git-dpm.


It will be targeted at experimental due to the freeze.

Regards,

Ross