On Tue, Sep 21, 2021 at 5:00 PM Antonio Terceiro wrote:
>
> On Mon, Sep 20, 2021 at 11:14:44AM -0400, Sandro Tosi wrote:
> > > That's because gbp does not use pristine-tar by default, and
> > > debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to
> > > fix that.
> >
> > I dont
On Mon, Sep 20, 2021 at 11:14:44AM -0400, Sandro Tosi wrote:
> > That's because gbp does not use pristine-tar by default, and
> > debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to
> > fix that.
>
> I dont think this is the right approach: the default options to work
> on DPT
On Mon, Sep 20, 2021 at 11:21 AM Andrey Rahmatullin wrote:
> On Mon, Sep 20, 2021 at 11:14:44AM -0400, Sandro Tosi wrote:
> > > That's because gbp does not use pristine-tar by default, and
> > > debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to
> > > fix that.
> > I dont thi
On 9/20/21 5:14 PM, Sandro Tosi wrote:
>> That's because gbp does not use pristine-tar by default, and
>> debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to
>> fix that.
>
> I dont think this is the right approach: the default options to work
> on DPT packages should be in gb
On Mon, Sep 20, 2021 at 11:14:44AM -0400, Sandro Tosi wrote:
> > That's because gbp does not use pristine-tar by default, and
> > debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to
> > fix that.
> I dont think this is the right approach: the default options to work
> on DPT pa
> That's because gbp does not use pristine-tar by default, and
> debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to
> fix that.
I dont think this is the right approach: the default options to work
on DPT packages should be in gbp default config file (or in another,
global, co
On Sun, Sep 19, 2021 at 10:56:33PM +0200, Carsten Schoenert wrote:
> Hi Antonio,
>
> thanks for your quick feedback!
>
> Am 19.09.21 um 21:24 schrieb Antonio Terceiro:
>
> > Looking from my side, the tarball from the archive (apt source
> > python-django-js-asset) and the one generated by pristi
On Sun, Sep 19, 2021 at 10:56:33PM +0200, Carsten Schoenert wrote:
> Hi Antonio,
>
> thanks for your quick feedback!
>
> Am 19.09.21 um 21:24 schrieb Antonio Terceiro:
>
> > Looking from my side, the tarball from the archive (apt source
> > python-django-js-asset) and the one generated by pristi
Hi Antonio,
thanks for your quick feedback!
Am 19.09.21 um 21:24 schrieb Antonio Terceiro:
Looking from my side, the tarball from the archive (apt source
python-django-js-asset) and the one generated by pristine-tar are
identical:
4b6a2c8625b8e96bbc4ff1588a27238d7d418b03
/tmp/python-django-
Hi,
On Sun, Sep 19, 2021 at 10:27:21AM +0200, Carsten Schoenert wrote:
> Hello Antonio,
>
> as you initially did the first upload for this package I'm now heading
> over to you.
>
> Am 19.09.21 um 09:48 schrieb Debian FTP Masters:
> >
> > python-django-js-asset_1.2.2-3.dsc: Invalid size hash fo
Thomas Goirand writes:
> I just tried to fix the FTBFS of a few pakcages last aug. after the
> Django 1.10 upload indeed. But I can't remember what I did for this
> package, for which I don't care much (I just tried to be helpful
> globally in Debian in this case). Did I forget to include what I
On 02/01/2017 03:39 AM, Brian May wrote:
> On 2017-02-01 13:34, Brian May wrote:
>
>> Ok, just noticed that the changelog in the uploaded package didn't
>> include this line to close the bug report.
>>
>> http://metadata.ftp-master.debian.org/changelogs/main/p/python-django-mptt/python-django-mptt
On Sun, 11 Oct 2015, Brian May wrote:
> Just noticed how it named the upstream branches.
>
> * [new branch] upstream-debian/experimental -> upstream-debian/experimental
> * [new branch] upstream-debian/jessie -> upstream-debian/jessie
> * [new branch] upstream-debian/sid -> upstream-debian/sid
>
On Sun, 11 Oct 2015, Brian May wrote:
> Just noticed how it named the upstream branches.
>
> * [new branch] upstream-debian/experimental -> upstream-debian/experimental
> * [new branch] upstream-debian/jessie -> upstream-debian/jessie
> * [new branch] upstream-debian/sid -> upstream-debian/sid
>
Hi,
On Sat, 10 Oct 2015, Barry Warsaw wrote:
> >And I would suggest that we generalize the DEP-14 naming scheme as part of
> >our git packaging policy...
>
> I'm all for standardization, but I do like the shorter names for the common
> case where you only need the unstable version. Certainly if
On Sun, 11 Oct 2015 at 13:50 Brian May
wrote:
> Unfortunately debian/sid does not build on sid, the tests fail:
> "IndexError: index 5 is out of bounds for axis 0 with size 2" - I don't
> think this is anything I did. It builds fine on Jessie.
>
Seems Django 1.7.x is incompatible with numpy 1.9
> > Christoph, can you confirm that upstream moved from bitbucket to
> > github? Seems to be here:
> > https://github.com/ubernostrum/django-contact-form
Yes, upstream now uses github. Bitbucket is not synced.
Christophe
On Sun, Oct 11, 2015 at 2:29 PM, W. Martin Borgert wrote:
> On 2015-10-11 16:49, Christophe Siraut wrote:
>> I do not intend to continue maintaining python-django-contact-form, I
>> just removed myself from the uploaders field, maintainer is DPMT.
>> Tests are currently failing and package fails t
On 2015-10-11 16:49, Christophe Siraut wrote:
> I do not intend to continue maintaining python-django-contact-form, I
> just removed myself from the uploaders field, maintainer is DPMT.
> Tests are currently failing and package fails to build from source.
> Upstream released a new version 3 months
On Sun, Oct 11, 2015 at 10:49 AM, Christophe Siraut wrote:
> I do not intend to continue maintaining python-django-contact-form, I
> just removed myself from the uploaders field, maintainer is DPMT.
> Tests are currently failing and package fails to build from source.
> Upstream released a new ver
On Sun, 11 Oct 2015 at 13:50 Brian May
wrote:
> I just converted and pushed these branches to git-dpm.
>
>
Just noticed how it named the upstream branches.
* [new branch] upstream-debian/experimental -> upstream-debian/experimental
* [new branch] upstream-debian/jessie -> upstream-debian/jessie
On Sun, 11 Oct 2015 at 11:40 Brian May
wrote:
> Should we convert all branches to git-dpm? Or forget the branches
> referring to obsolete distributions?
>
> Probably should do these:
>
> origin/debian/experimental
> origin/debian/jessie
> origin/debian/sid
>
I just converted and pushed these bra
Should we convert all branches to git-dpm? Or forget the branches referring
to obsolete distributions?
Probably should do these:
origin/debian/experimental
origin/debian/jessie
origin/debian/sid
Not sure about these
origin/debian/squeeze
origin/debian/wheezy
origin/debian/wheezy-backports
Of c
On Sat, 10 Oct 2015 at 09:54 Brian May
wrote:
> We can move the migrated version out of the way, restore the old version,
> and update it to the required standards (e.g. git-dpm). Is everyone happy
> with this approach?
>
Have moved the repository back. Should be usable exactly as before. Have
n
On Oct 10, 2015, at 09:13 AM, Raphael Hertzog wrote:
>Yes, except for the naming of branches where I would prefer to keep the
>DEP-14 naming scheme (we should just rename debian/sid into debian/master).
>
>http://dep.debian.net/deps/dep14/
>
>And I would suggest that we generalize the DEP-14 namin
Hi,
On Fri, 09 Oct 2015, Brian May wrote:
> We can move the migrated version out of the way, restore the old version,
> and update it to the required standards (e.g. git-dpm). Is everyone happy
> with this approach?
Yes, except for the naming of branches where I would prefer to keep
the DEP-14 na
On 5 July 2014 11:28, Brian May wrote:
> So I might just apply the patch and upload to Debian. Seems like the
> safest option.
>
> Shame though this won't work out of the box with the version in Pypi. Most
> of the changes involve tests only, so don't matter, there is one line that
> is for a non
On 4 July 2014 12:13, Brian May wrote:
> I tried to go back to the "correct" version, django-jsonfield. It doesn't
> appear to work properly with Python3, something that I require. It imports
> six, but this seems to be very much incomplete. The tests fail under
> Python3.
>
If I apply the follo
Hi.
Olivier Berger writes:
> Hi.
>
> I'm a bit puzzled by a Python version issue when backporting
> django-ldapdb to wheezy-backports.
>
> The repo is here :
> http://anonscm.debian.org/viewvc/python-modules/packages/django-ldapdb/branches/wheezy-bpo/
>
> I'm using dh-python and the d/control s
Hi.
I'm a bit puzzled by a Python version issue when backporting
django-ldapdb to wheezy-backports.
The repo is here :
http://anonscm.debian.org/viewvc/python-modules/packages/django-ldapdb/branches/wheezy-bpo/
I'm using dh-python and the d/control says :
Depends: ${misc:Depends}, ${python:Depe
On 25 September 2013 15:14, Brian May wrote:
> Guess I should file a bug report against python-django then...
>
Submitted as #724637
--
Brian May
On Wednesday 25 September 2013 15:14:27 Brian May wrote:
> Guess I should file a bug report against python-django then...
Upstream refactored the tests suite during the 1.6 development, so maybe you
could also check if the bug is already fixed and mention in the bug report.
Thanks!
Kind regards
On 24 September 2013 15:40, Chow Loong Jin wrote:
> grepping for johndoe shows one match in
> tests/regressiontests/utils/simplelazyobject.py, where the test case
> creates a
> johndoe user.
>
> I suspect the error comes from using unittest.TestCase instead of
> django.test.TestCase. The latter d
On Tue, Sep 24, 2013 at 02:11:56PM +1000, Brian May wrote:
> On 24 September 2013 13:16, Chow Loong Jin wrote:
>
> > Why don't you catch the AssertionError at this point and check what the
> > extra
> > User object is?
> >
>
> [, , ]
grepping for johndoe shows one match in
tests/regressiontest
On 24 September 2013 13:16, Chow Loong Jin wrote:
> Why don't you catch the AssertionError at this point and check what the
> extra
> User object is?
>
[, , ]
I just tried it on the same path as you used, but it worked for me. My /tmp
> is
> on tmpfs though.
>
Not surprised...
--
Brian May
On Tue, Sep 24, 2013 at 11:23:14AM +1000, Brian May wrote:
> Hello,
>
> >From a wheezy box, I am running the following commands:
>
> dget
> http://ftp.de.debian.org/debian/pool/main/p/python-django/python-django_1.5.4-1.dsc
> cd python-django-1.5.4
> dpkg-buildpackage -rfakeroot -sa 2>&1 | tee $l
36 matches
Mail list logo
