Re: Updating python-django-tagging (0.4.1 -> 0.4.3)
Hello, On Wed, May 11, 2016 at 12:30:59PM +0100, Christopher Baines wrote: Hey, Is anyone available to review and upload a new version of python-django-tagging [1][2]? The changelog is: * New upstream release * Convert debian/copyright to the DEP-5 format * Add myself as an uploader * Remove the fix_calc_tag_weight patch, as this has been merged upstream * Remove the fix-testsuite patch, as this is unnecessary Thanks, Chris 1: https://anonscm.debian.org/cgit/python-modules/packages/python-django-tagging.git/ 2: https://tracker.debian.org/pkg/python-django-tagging It's been a while. I have pushed an update since a new version is out (0.4.5) and a smaller set of fixes. I plan to upload it in sid in a day or two. So, anyone interested, please take a look. Since python-django-tagging is removed from testing and currently no re-entries are allowed, stretch might be released without the package. Ufortunately this affects graphite-web which depends on python-django-tagging. But, I assume that we can ask for an exception from the release team. Either way, uploading to sid is a first step.
Updating python-django-tagging (0.4.1 -> 0.4.3)
Hey, Is anyone available to review and upload a new version of python-django-tagging [1][2]? The changelog is: * New upstream release * Convert debian/copyright to the DEP-5 format * Add myself as an uploader * Remove the fix_calc_tag_weight patch, as this has been merged upstream * Remove the fix-testsuite patch, as this is unnecessary Thanks, Chris 1: https://anonscm.debian.org/cgit/python-modules/packages/python-django-tagging.git/ 2: https://tracker.debian.org/pkg/python-django-tagging signature.asc Description: OpenPGP digital signature
Re: Updating python-django-tagging
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 signature.asc Description: OpenPGP digital signature
Re: Updating python-django-tagging
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 pgpfNJKylJROt.pgp Description: OpenPGP digital signature
Re: Updating python-django-tagging
Barry Warsaw 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
Re: Updating python-django-tagging
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 pgpNZJLDfuqc9.pgp Description: OpenPGP digital signature
Updating python-django-tagging
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 signature.asc Description: OpenPGP digital signature
