Hello,
I have a python program that I package as as a debian package.
The debian directory can be found here.
https://github.com/privacyidea/privacyidea/tree/master/debian
I have a simple debian/rules file, that worked fine so far:
#!/usr/bin/make -f
%:
dh $@ --with python2 --buildsyste
On 30/08/14 10:50, Cornelius Kölbel wrote:
> But now my originial program package is empty and does not contain the
> python code.
> It looks like only the .install scripts are run, but obviously python
> setup.py install is not run anymore - so I guess something does not work
> right with the simp
On Aug 30, 2014, at 11:19 AM, Simon McVittie wrote:
>On 30/08/14 10:50, Cornelius Kölbel wrote:
>> But now my originial program package is empty and does not contain the
>> python code.
>> It looks like only the .install scripts are run, but obviously python
>> setup.py install is not run anymore
On Saturday, August 30, 2014 09:44:30 Barry Warsaw wrote:
> On Aug 30, 2014, at 11:19 AM, Simon McVittie wrote:
> >On 30/08/14 10:50, Cornelius Kölbel wrote:
> >> But now my originial program package is empty and does not contain the
> >> python code.
> >> It looks like only the .install scripts ar
On Aug 30, 2014, at 12:57 PM, Scott Kitterman wrote:
>I don't think that's the case for multiple binary packages.
Hmm. An example is enum34, which has python-enum34, python3-enum34, and
python-enum34-doc binary packages. I don't have any d/*.install files and
everything gets built correctly.
h
On Wed, Aug 27, 2014 at 04:24:29AM +0200, Stefano Rivera wrote:
> - Tag names:
> * Use the normal pristine-tar upstream/ for upstream tags
> * For debian tags corresponding to uploads: debian/ as
> "debcommit -r" does (please use "git tag -s" and sign your tags)
You can use "debcommit --si
On August 30, 2014 1:06:41 PM EDT, Barry Warsaw wrote:
>On Aug 30, 2014, at 12:57 PM, Scott Kitterman wrote:
>
>>I don't think that's the case for multiple binary packages.
>
>Hmm. An example is enum34, which has python-enum34, python3-enum34,
>and
>python-enum34-doc binary packages. I don't hav
[Scott Kitterman, 2014-08-30]
> Interesting. I've always had to add them.
export PYBUILD_NAME=foo
does the trick
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2
On Aug 30, 2014, at 09:00 PM, Piotr Ożarowski wrote:
>export PYBUILD_NAME=foo
Best thing *ever*. :)
-Barry
--
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/2014083
Thanks for sending out the minutes Stefano.
On Aug 27, 2014, at 04:24 AM, Stefano Rivera wrote:
>- Tag names:
> * Use the normal pristine-tar upstream/ for upstream tags
> * For debian tags corresponding to uploads: debian/ as
>"debcommit -r" does (please use "git tag -s" and sign your tags
On Aug 30, 2014, at 11:02 AM, Javi Merino wrote:
>You can use "debcommit --sign-tags -r" to sign your tags (or even
>better, set DEBCOMMIT_SIGN_TAGS=yes in ~/.devscripts).
You can also put this in your ~/.gbp.conf file:
[DEFAULT]
pristine-tar = True
[git-buildpackage]
sign-tags = True
ignore-ne
Several people mentioned dgit as something we should look at. I like the idea
of dgit as a "udd-killer" since I really like UDD in Ubuntu. Does anybody
have any experience with dgit for package maintenance?
-Barry
signature.asc
Description: PGP signature
On Sat, Aug 30, 2014 at 01:29:34PM -0700, Barry Warsaw wrote:
> Several people mentioned dgit as something we should look at. I like the idea
> of dgit as a "udd-killer" since I really like UDD in Ubuntu. Does anybody
> have any experience with dgit for package maintenance?
Relatively few at thi
Hi Sandro,
On Wed, Aug 27, 2014 at 09:13:32AM +0100, Sandro Tosi wrote:
> On Mon, Aug 25, 2014 at 10:00 PM, Barry Warsaw wrote:
> > Here's the page I mentioned regarding a *proposed* transition plan to using
> > git for team packages. It's more or less a brain dump right now, and don't
> > feel
14 matches
Mail list logo
