Re: python-modules-team moderation bankruptcy

[Jakub Wilk]

* Jakub Wilk , 2013-04-11, 13:15:
I'll discard all the messages older than a month, and start moderation 
anew.


This is now done.

--
Jakub Wilk


--
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/20130416102659.ga8...@jwilk.net

Re: RFR: python-qrcode -- native python module to generate QR codes

[Hans-Christoph Steiner]

On 04/15/2013 04:26 AM, Cornelius Kölbel wrote:
> Am 15.04.2013 03:15, schrieb Hans-Christoph Steiner:
>> On 04/14/2013 03:10 AM, Cornelius Kölbel wrote:
>>> Am 13.04.2013 05:46, schrieb Hans-Christoph Steiner:
 On 02/21/2013 03:34 PM, Cornelius Kölbel wrote:
> Am 21.02.2013 20:42, schrieb Jakub Wilk:
>> * Cornelius Kölbel , 2013-02-21, 20:14:
 http://mentors.debian.net/debian/pool/main/q/qrcode/qrcode_2.4.2-1.dsc
>>> Great. The mentors site suddenly gives me lintian warnings, that were
>>> not there earlier and that did give the linitan on my debian
>>> experimental. :-(
>> There's only one lintian warning:
>>
>> W: qrcode source: debhelper-overrides-need-versioned-build-depends (>=
>> 7.0.50~)
>>
>> This tag was been retired in Lintian 2.5.11, because stable has a
>> newer debhelper version, and oldstable is not supported anymore. (I
>> would have preferred if the tag was made pedantic rather than removed,
>> but oh well...)
>>
>> The remaining tags are informative:
>>
>> I: qrcode source: quilt-patch-missing-description add-man-page
>> I: python-qrcode: hyphen-used-as-minus-sign usr/share/man/man1/qr.1.gz:7
>> I: python-qrcode: hyphen-used-as-minus-sign usr/share/man/man1/qr.1.gz:13
>> I: python-qrcode: hyphen-used-as-minus-sign usr/share/man/man1/qr.1.gz:19
>>
> Anyway.
> ...and again I upload a hopefully again nicer version.
> I hope the next package will be less complicated...
 I'm interesting in sponsoring this package and uploading it, if no one else
 has claimed it.  Cornelius, do you have a git or svn repo for this package
 yet?  If not, I can set up a git repo on collab-maint.

 .hc

>>> Hello Hans-Christoph,
>>>
>>> to my knowledge till now noone has claimed the package.
>>> So I would very much appreciate, if you would sponsor this package.
>>>
>>> There is the git repo of the upstream package, which is located here:
>>>
>>> https://github.com/lincolnloop/python-qrcode
>>>
>>> As part of an internal git I have my addons (Makefile to download, patch
>>> and build the package) in this repository.
>>> So if this should be in a public git, we should move it there, yes, thanks!
>>>
>>> There is one thing for me to do:
>>> The upstream was updated to 2.5.1, and I would have to build a new
>>> package from this.
>>>
>>> Thanks a lot and kind regards
>>> Cornelius
>> There is a new style of organizing git repos for packages that have
>> upstream git repos that I want to try.  It allows you to have the
>> upstream history, the tarball/release history, and the debian
>> packaging history all in one repo, all while being easily buildable
>> using git-buildpackage.
>>
>> http://www.eyrie.org/~eagle/journal/2013-04/001.html
>> 
>>
>> So if you don't mind, I'd like to merge in the commits from your git
>> into a new repo that I build up.
>>
>> .hc
> Hello Hans-Christoph,
>
> I am fine with that.
> I have a Makefile, that downloads the upstream package, quilts it and
> builds it... ;-)
>
> The code is part of a larger internal git and there are only 4 or 5
> changes. So I guess extracting it from the git is not worth the effort.
> I could either send you the Makefile and the debian Directory or I can
> add them to the git.
>
> Kind regards
> Cornelius

Ok, here's the repo:

http://anonscm.debian.org/gitweb/?p=collab-maint/python-qrcode.git

Sign up for an account on alioth, then you can commit directly using the
git+ssh URL.  I added some updates, including renaming the source package to
python-qrcode since qrcode just seemed too generic and likely to conflict with
other potential packages.  I also updated the package to v2.5.

Here's the workflow for updating a new upstream version.  First, set up the
git remote for the upstream git repo (you need git-buildpackage
v0.6.0~git20120324 or better. If you're on Debian/stable, get a newer version,
I just grabbed the one from testing).

 sudo apt-get install git-buildpackage
 gbp-clone git+ssh://git.debian.org/git/collab-maint/python-qrcode.git
 cd python-qrcode
 git remote add upstream https://github.com/lincolnloop/python-qrcode

Now your local repo should be all set to work with.  Now you can try updating
to a new release:

 git fetch upstream
 git fetch upstream --tags
 wget https://pypi.python.org/packages/source/q/qrcode/qrcode-2.6.tar.gz
 git-import-orig --pristine-tar --upstream-vcs-tag=v2.6 qrcode-2.6.tar.gz

Now you'll have the debian packaging commits and the upstream commits all
synced up together.  Its pretty slick :)

.hc



signature.asc
Description: OpenPGP digital signature