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

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

Updating python-django-tagging

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

Contents

  Updating python-django-tagging Christopher Baines <chris@cbaines.net> - 2016-03-06 14:20 +0100
    Re: Updating python-django-tagging Barry Warsaw <barry@debian.org> - 2016-03-07 00:00 +0100
      Re: Updating python-django-tagging Brian May <bam@debian.org> - 2016-03-07 00:30 +0100
        Re: Updating python-django-tagging Barry Warsaw <barry@debian.org> - 2016-03-07 01:00 +0100
    Re: Updating python-django-tagging Christopher Baines <chris@cbaines.net> - 2016-03-20 18:50 +0100

#8278 — Updating python-django-tagging

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

Hello,

I have been looking at updating the python-django-tagging package, as it
currently fails to build from source, and there is a new upstream
release available (that I believe will fix this).

However, git-dpm keeps complaining in different ways when I try to do
this (and I have tried a few different ways). I think the source of the
issues I am having could be that the debian/.git-dpm file is out of sync
with the rest of the repository (it seems to still refer to the 0.3.1
version, whereas the current version is 0.4).

What is the best approach here if I am trying to update the package? I
can try and fix the debian/.git-dpm file (manually or using some tool?),
or I could just avoid using git-dpm (but I do need to do some patch
changes)?

Thanks,

Chris

[toc] | [next] | [standalone]

#8279

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

On Mar 06, 2016, at 01:12 PM, Christopher Baines wrote:

>However, git-dpm keeps complaining in different ways when I try to do
>this (and I have tried a few different ways). I think the source of the
>issues I am having could be that the debian/.git-dpm file is out of sync
>with the rest of the repository (it seems to still refer to the 0.3.1
>version, whereas the current version is 0.4).
>
>What is the best approach here if I am trying to update the package? I
>can try and fix the debian/.git-dpm file (manually or using some tool?),
>or I could just avoid using git-dpm (but I do need to do some patch
>changes)?

I don't really have any good suggestions.  I've had some weird problems with
git-dpm occasionally and no real solutions.  For example, it kept wanting to
turn a certain git commit in the patched branch into a double quilt patch, and
nothing I did seemed to work (I ended up giving up).

In some of my non-team packages I've been trying to use gbp-pq more.  It seems
not terrible, and at least it's maintained.  Is it time to consider switching?
Perhaps just on a trial basis?  When git-dpm works, it does work well.

Cheers,
-Barry

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

#8280

Barry Warsaw <barry@debian.org> writes:

> In some of my non-team packages I've been trying to use gbp-pq more.  It seems
> not terrible, and at least it's maintained.  Is it time to consider switching?
> Perhaps just on a trial basis?  When git-dpm works, it does work well.

I really like the work flow of git-dpm. Think it is much better then
gbp-pq, which IIRC stores and distributes the patch files in git.

Shame it isn't better maintained. As a result, seems it is very easy to
get it in a confused state (e.g. by not noticing the local upstream
branch needs a fast forward) and doesn't handle merging of branches.
-- 
Brian May <bam@debian.org>

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

#8281

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

On Mar 07, 2016, at 10:24 AM, Brian May wrote:

>I really like the work flow of git-dpm. Think it is much better then
>gbp-pq, which IIRC stores and distributes the patch files in git.
>
>Shame it isn't better maintained. As a result, seems it is very easy to
>get it in a confused state (e.g. by not noticing the local upstream
>branch needs a fast forward) and doesn't handle merging of branches.

Just to be clear, I agree on all your points.  When git-dpm works, it works
great and you almost don't even have to think about.  I like tools that don't
make me think. :)

Cheers,
-Barry

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

#8307

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

On 06/03/16 13:12, Christopher Baines wrote:
> I have been looking at updating the python-django-tagging package, as it
> currently fails to build from source, and there is a new upstream
> release available (that I believe will fix this).
> 
> However, git-dpm keeps complaining in different ways when I try to do
> this (and I have tried a few different ways). I think the source of the
> issues I am having could be that the debian/.git-dpm file is out of sync
> with the rest of the repository (it seems to still refer to the 0.3.1
> version, whereas the current version is 0.4).
> 
> What is the best approach here if I am trying to update the package? I
> can try and fix the debian/.git-dpm file (manually or using some tool?),
> or I could just avoid using git-dpm (but I do need to do some patch
> changes)?

To try and move this forward, I have made an attempt at fixing the metadata.

I have not updated the python modules team remote just yet, but you can
find the updates here [1], and the specific commit for the metadata here
[2].

If I hear no objections in the next couple of days, I'll update the
repository on git.debian.org.

1: http://git.cbaines.net/python-django-tagging/
2:
http://git.cbaines.net/python-django-tagging/commit/?id=2e528690df8792b2e70248ce18712ca653ede12b

[toc] | [prev] | [standalone]

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

csiph-web