Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #9210 > unrolled thread

python-django-mptt

Started byBrian May <brian@linuxpenguins.xyz>
First post2017-02-01 03:30 +0100
Last post2017-02-02 22:20 +0100
Articles 5 — 3 participants

Back to article view | Back to linux.debian.maint.python


Contents

  python-django-mptt Brian May <brian@linuxpenguins.xyz> - 2017-02-01 03:30 +0100
    Re: python-django-mptt Brian May <brian@linuxpenguins.xyz> - 2017-02-01 03:40 +0100
      Re: python-django-mptt Brian May <brian@linuxpenguins.xyz> - 2017-02-01 03:50 +0100
        Re: python-django-mptt Thomas Goirand <zigo@debian.org> - 2017-02-01 13:40 +0100
          Re: python-django-mptt Brian May <bam@debian.org> - 2017-02-02 22:20 +0100

#9210 — python-django-mptt

FromBrian May <brian@linuxpenguins.xyz>
Date2017-02-01 03:30 +0100
Subjectpython-django-mptt
Message-ID<t5SQh-8rf-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hello All, 

Why didn't the upload of python-django-mptt automatically close #828669?


Too late now, it was removed from testing and I think it is too late to
re-add. I don't think it is important. 

However I just wondered why this bug didn't get closed. 

(I thought I also responded to that last email too, but will have to
double check this) 

https://anonscm.debian.org/cgit/python-modules/packages/python-django-mptt.git/tree/debian/changelog


Regards

  

[toc] | [next] | [standalone]


#9211

FromBrian May <brian@linuxpenguins.xyz>
Date2017-02-01 03:40 +0100
Message-ID<t5SZX-8uj-11@gated-at.bofh.it>
In reply to#9210

[Multipart message — attachments visible in raw view] — view raw

On 2017-02-01 13:22, Brian May wrote:

> Why didn't the upload of python-django-mptt automatically close #828669? 
> 
> Too late now, it was removed from testing and I think it is too late to re-add. I don't think it is important. 
> 
> However I just wondered why this bug didn't get closed. 
> 
> (I thought I also responded to that last email too, but will have to double check this) 
> 
> https://anonscm.debian.org/cgit/python-modules/packages/python-django-mptt.git/tree/debian/changelog

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_0.8.5-0.1_changelog


I will close the bug report manually.

  

[toc] | [prev] | [next] | [standalone]


#9212

FromBrian May <brian@linuxpenguins.xyz>
Date2017-02-01 03:50 +0100
Message-ID<t5T9D-5K-3@gated-at.bofh.it>
In reply to#9211

[Multipart message — attachments visible in raw view] — view raw

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_0.8.5-0.1_changelog 
> 
> I will close the bug report manually.

Actually better clarify with the uploader first. 

Thomas, did you fix #828669 when you uploaded version 0.8.5-0.1 [1] to
Debian? The version uploaded doesn't have the following line in the
changelog:

    Add patch to fix FTBFS in Django 1.10 (Closes: #828669):
    0001-django-1.10-Prepare-the-manager-using-code-for-Djang.patch

So it looks like you didn't fix this FTBFS, but I thought that was the
point of making this upload?

  

Links:
------
[1]
http://metadata.ftp-master.debian.org/changelogs/main/p/python-django-mptt/python-django-mptt_0.8.5-0.1_changelog

[toc] | [prev] | [next] | [standalone]


#9213

FromThomas Goirand <zigo@debian.org>
Date2017-02-01 13:40 +0100
Message-ID<t62mC-5Z6-25@gated-at.bofh.it>
In reply to#9212
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_0.8.5-0.1_changelog
>>
>> I will close the bug report manually.
>>
>>  
>>
> Actually better clarify with the uploader first.
> 
>  
> 
> Thomas, did you fix #828669 when you uploaded version 0.8.5-0.1
> <http://metadata.ftp-master.debian.org/changelogs/main/p/python-django-mptt/python-django-mptt_0.8.5-0.1_changelog> to
> Debian? The version uploaded doesn't have the following line in the
> changelog:
> 
>     Add patch to fix FTBFS in Django 1.10 (Closes: #828669):
>     0001-django-1.10-Prepare-the-manager-using-code-for-Djang.patch
> 
> So it looks like you didn't fix this FTBFS, but I thought that was the point of making this upload?

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 push to
Git? :/

Cheers,

Thomas Goirand (zigo)

[toc] | [prev] | [next] | [standalone]


#9214

FromBrian May <bam@debian.org>
Date2017-02-02 22:20 +0100
Message-ID<t6wXn-Rp-9@gated-at.bofh.it>
In reply to#9213
Thomas Goirand <zigo@debian.org> 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 push to
> Git? :/

Ok, so it looks like the patch was applied, however the changelog entry
was not updated.

However I still can't get it to build.

So keeping the RC bug open is still appropriate.

I tried updating to the latest upstream version (see git) however now I
can't see how to run the tests (the supplied mptt/settings.py file is
insufficient).

It is not really important enough for me to worry much more.
-- 
Brian May <bam@debian.org>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web