On Aug 06, 2014, at 02:28 PM, Dimitri John Ledkov wrote:
I am on the edge. I prefer dgit, as it's the only one the guarantees
round-trip save with the archive even when someone NMUs things without using
dgit.
From this description, it sounds like dgit is the closest equivalent to Ubuntu
On Aug 06, 2014, at 04:08 PM, Piotr Ożarowski wrote:
and I would love to try them all before we make a decision¹
Me too.
Should we relax the team preference for one vcs to rule them all, at least for
a period of experimentation and experience sharing? I still *really* want to
end up in a
On Aug 09, 2014, at 06:02 PM, Brian May wrote:
At the moment, in subversion, we only store the debian/* directory. Is
there any requirement/benefit in putting the full upstream source in git
too?
If it were well integrated with quilt, I think it would be fine to have
source-full branches. I
On Aug 19, 2014, at 11:14 AM, Barry Warsaw wrote:
I usually don't care much about preserving local intra-upload vcs history
Ah, except for the case where I want to collaborate with someone on the new
version, e.g. to get a code review of some packaging change *before* it gets
uploaded. This is
On 08/06/2014 10:08 PM, Piotr Ożarowski wrote:
I am on the edge. I prefer dgit
and I would love to try them all before we make a decision¹
If one wants us to consider XYZ, please send a link to test repo and a
list of commands that will let us deal f.e. with such problems:
* how can I
On Wed, 13 Aug 2014, Piotr Ożarowski wrote:
[Raphael Hertzog, 2014-08-13]
* old patch needs an update, what should I do?
(quilt edit? quilt refresh? XYZ rebase on a different branch?)
* new patch is needed, how can I add it?
(quilt new? another branch?)
I don't see the need
So let me give my own answer to some of the questions asked here.
On Wed, 06 Aug 2014, Dimitri John Ledkov wrote:
However, it does not integrate with git-dpm at the moment and there is
no clear conversion / vcs history import available. Do we care about
preserving vcs history for our packages?
[Raphael Hertzog, 2014-08-13]
* old patch needs an update, what should I do?
(quilt edit? quilt refresh? XYZ rebase on a different branch?)
* new patch is needed, how can I add it?
(quilt new? another branch?)
I don't see the need for the team to impose anything here. patches are
Raphael Hertzog hert...@debian.org writes:
So let me give my own answer to some of the questions asked here.
These questions would best be answered in a ‘debian/README.source’
document giving all the information needed to work with the Debian
source for the package.
--
\ “You can be a
On 7 August 2014 00:08, Piotr Ożarowski pi...@debian.org wrote:
I am on the edge. I prefer dgit
and I would love to try them all before we make a decisionน
Would be interested in a brief summary of the different workflows possible,
and a comparison. I have not been keeping up.
At the
Hi,
On Tue, 05 Aug 2014, Matthew Vernon wrote:
https://git.csx.cam.ac.uk/x/ucs/u/mcv21/django-grappelli.git
https://git.csx.cam.ac.uk/x/ucs/u/mcv21/django-stronghold.git
[...]
Naturally, I'd like to upload these as maintained by
python-modules-t...@lists.alioth.debian.org. Is that going to be
On Aug 06, 2014, at 08:47 AM, Raphael Hertzog wrote:
(That said I'm also rather annoyed by the fact that the team hasn't switched
to git yet.)
We've had these discussions on this mailing list before, but I think we should
discuss it at Debconf. While obviously we won't have full representation
On 6 August 2014 14:18, Barry Warsaw ba...@debian.org wrote:
On Aug 06, 2014, at 08:47 AM, Raphael Hertzog wrote:
(That said I'm also rather annoyed by the fact that the team hasn't switched
to git yet.)
We've had these discussions on this mailing list before, but I think we should
discuss it
I am on the edge. I prefer dgit
and I would love to try them all before we make a decision¹
If one wants us to consider XYZ, please send a link to test repo and a
list of commands that will let us deal f.e. with such problems:
* how can I fetch foo sources? what about updating all packages in
On 06/08/14 04:25, Brian May wrote:
On 6 August 2014 03:11, Matthew Vernon matt...@debian.org
mailto:matt...@debian.org wrote:
I've packaged up django-grappelli and django-stronghold (since we have
need for them at work). I think my debianisations are sane, but I've
done them in
Hi,
On 06/08/14 07:47, Raphael Hertzog wrote:
Hi,
On Tue, 05 Aug 2014, Matthew Vernon wrote:
https://git.csx.cam.ac.uk/x/ucs/u/mcv21/django-grappelli.git
https://git.csx.cam.ac.uk/x/ucs/u/mcv21/django-stronghold.git
[...]
Naturally, I'd like to upload these as maintained by
Hi Matthew,
On Wed, 06 Aug 2014, Matthew Vernon wrote:
Is 1.7 released yet? At least Grappelli only aims to work with released
versions, so I think it's currently only 1.6-compatible. I'd expect
1.7-support to be along once that's been out for a bit.
1.7 will be out in a few days/weeks and we
Hi,
I've packaged up django-grappelli and django-stronghold (since we have
need for them at work). I think my debianisations are sane, but I've
done them in git not subversion. Repos:
https://git.csx.cam.ac.uk/x/ucs/u/mcv21/django-grappelli.git
On 6 August 2014 03:11, Matthew Vernon matt...@debian.org wrote:
I've packaged up django-grappelli and django-stronghold (since we have
need for them at work). I think my debianisations are sane, but I've
done them in git not subversion. Repos:
Please make sure these work with Django 1.7 in
19 matches
Mail list logo
