Can we go back to DPMT/PAPT workflow? Git vs. Bzr vs. Hg war is not
that relevant (and we already know which VCS won, at least in Debian ;P)
Can we focus on what we want (without taking VCS into account if
possible) so that those who will propose workflow/tools/do the initial
migration can start w
On 02/21/2013 04:55 PM, Piotr Ożarowski wrote:
> Can we go back to DPMT/PAPT workflow? Git vs. Bzr vs. Hg war is not
> that relevant (and we already know which VCS won, at least in Debian ;P)
>
> Can we focus on what we want (without taking VCS into account if
> possible) so that those who will pro
[Thomas Goirand, 2013-02-21]
> git-buildpackage takes some time to learn.
>
> I think it might be worth trying git-stuff (eg: the package).
> I know few people who use it and are happy with it.
sure, I will try it. Migrate packages and describe the workflow on wiki
and I will test it.
How about
Am 19.02.2013 23:34, schrieb Jakub Wilk:
> * Cornelius Kölbel , 2013-02-18, 18:05:
>
> Why do you include compressed README and changelog in debian? :/
> You probably should use dh_installdoc and dh_installchangelog to
> install them, not dh_install.
Hi Jakub,
I managed to use debian/python-qrcod
* Cornelius Kölbel , 2013-02-21, 18:15:
I am not sure how to add the upstream changelog without change the
default simple debian/rules file?
Adding something like this (untested) to debian/rules should do the
trick:
override_dh_installchangelogs:
dh_installchangelogs CHANGES.rst
--
Am 21.02.2013 19:08, schrieb Jakub Wilk:
> * Cornelius Kölbel , 2013-02-21, 18:15:
>> I am not sure how to add the upstream changelog without change the
>> default simple debian/rules file?
>
> Adding something like this (untested) to debian/rules should do the
> trick:
>
> override_dh_installchan
Am 21.02.2013 20:09, schrieb Cornelius Kölbel:
> Am 21.02.2013 19:08, schrieb Jakub Wilk:
>> * Cornelius Kölbel , 2013-02-21, 18:15:
>>> I am not sure how to add the upstream changelog without change the
>>> default simple debian/rules file?
>> Adding something like this (untested) to debian/rules
* 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:
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
>>
Hi,
As discussed yesterday on IRC, nose's /usr/bin/nosetests-3.x scripts are
broken (provided only for python3 version(s) that was/were default on
build time), and instead of writing hacks to fix that we have decided to
instead remove those scripts and make packages use
"python3.x /usr/bin/nosetes
On 02/21/2013 01:59 AM, Scott Kitterman wrote:
> I don't keep local copies of things I don't work on regularly, so for team
> packages I would be downloading all of it.
I thought about it for a long time. Then I tried again today, and now,
I don't buy into this "it takes too much time to download
[Thomas Goirand, 2013-02-22]
> From a server in a data center in Seattle, it took me 90 seconds
> to download the packaging sources of python-eventlet. Compare
> this to the 4 seconds it takes me to clone python-warlock from
> Alioth, upstream source included !!!
your data is wrong (see below). I
12 matches
Mail list logo
