Hello,
On Wed 19 Jun 2019 at 11:51pm +0200, Wouter Verhelst wrote:
> On Mon, Jun 17, 2019 at 11:47:38AM +0100, Sean Whitton wrote:
>> We could try to write a tool which tries to guess and convert (e.g.) the
>> dgit view with your changes into a maintainer workflow, but there are
>> large obstacle
Ansgar Burchardt writes:
> On Thu, 2019-06-20 at 10:52 +0200, Enrico Zini wrote:
>> This reminds me of something that popped up in a dinner discussion a few
>> days ago: mandate documenting workflow in debian/README.source no matter
>> what, and allow to symlink that file to a repository in
>> /u
Hi Enrico,
> This reminds me of something that popped up in a dinner discussion a few
> days ago: mandate documenting workflow in debian/README.source no matter
> what, and allow to symlink that file to a repository in
> /usr/share/doc/somewhere/ as we do for common licenses.
I do like the symlin
On Thu, 2019-06-20 at 10:52 +0200, Enrico Zini wrote:
> This reminds me of something that popped up in a dinner discussion a few
> days ago: mandate documenting workflow in debian/README.source no matter
> what, and allow to symlink that file to a repository in
> /usr/share/doc/somewhere/ as we do
On Wed, Jun 19, 2019 at 11:51:14PM +0200, Wouter Verhelst wrote:
> What if you took away the necessary guesswork?
>
> Have dgit support a field in debian/control that, if it exists, explains
> to dgit (and any other tool that might care) what the workflow type is.
> This would require a categoriz
Russ Allbery writes:
> Colin Watson writes:
>> Is it at all likely that the ftpmaster api service might migrate away
>> from Let's Encrypt at this point? I would assume probably not. In that
>> case, you could at least make the situation substantially better with no
>> further DSA work required b
On Mon, Jun 17, 2019 at 11:47:38AM +0100, Sean Whitton wrote:
> We could try to write a tool which tries to guess and convert (e.g.) the
> dgit view with your changes into a maintainer workflow, but there are
> large obstacles to this working reliably. For example, there exist edge
> cases such th
Sam Hartman writes:
>> "Russ" == Russ Allbery writes:
> Russ> debian.org already publishes a CAA record, which conveys that
> Russ> information (although has its own verification concerns, but I
> Russ> think debian.org is using DNSSEC so you can verify the record
> Russ> tha
> "Russ" == Russ Allbery writes:
Russ> Colin Watson writes:
>> Is it at all likely that the ftpmaster api service might migrate
>> away from Let's Encrypt at this point? I would assume probably
>> not. In that case, you could at least make the situation
>> substantially
Colin Watson writes:
> Is it at all likely that the ftpmaster api service might migrate away
> from Let's Encrypt at this point? I would assume probably not. In that
> case, you could at least make the situation substantially better with no
> further DSA work required by pinning the appropriate
On Wed, Jun 19, 2019 at 01:57:39PM +0100, Ian Jackson wrote:
> FTAOD: I have a memory that in response to Hector Oron's message #20
> in that bug, I did try to have a conversation on debian-admin, but
> that I found that conversation very frustrating. I did not feel that
> the DSA members I was ta
Ian Jackson writes ("Re: The Difference between debcheckout and dgit and what
they try to accomplish"):
> Hector: If it would be useful to you, I could tell you a set of dgit
> configuration settings to have it use the apt repository fetching
> method. That would rely, therefo
> On Mon 17 Jun 2019 at 06:21pm +0200, Helmut Grohne wrote:
> > Presently, no. I attempted using it, but I feel that the extra
> > complexity did not help my use case. dgit solves a difficult problem and
> > that comes at a cost. Verification of source integrity is much more
> > difficult to unders
Hello Helmut,
On Mon 17 Jun 2019 at 06:21pm +0200, Helmut Grohne wrote:
> Presently, no. I attempted using it, but I feel that the extra
> complexity did not help my use case. dgit solves a difficult problem and
> that comes at a cost. Verification of source integrity is much more
> difficult to
Hi,
Let me try to answer multiple mails as one:
On Mon, Jun 17, 2019 at 07:44:39AM +0200, Andreas Tille wrote:
> In other words: If vcs-git would be uniform would this be more
> attractive to you?
Maybe. Uniformity certainly is an important property to me. Having to
figure out different workflow
Sean Whitton writes ("Re: The Difference between debcheckout and dgit and what
they try to accomplish"):
> It would seem, then, that what we want is merge requests against our
> interchange format: the source packages that actually get uploaded. Or,
> in other words, we
Sam Hartman writes ("Re: The Difference between debcheckout and dgit and what
they try to accomplish"):
> But my reading of the discussion so far is that people see getting
> patches actually integrated as a pain point.
...
> In the debian-vote discussion people were talking ab
Hello,
On Sun 16 Jun 2019 at 08:08pm -0400, Sam Hartman wrote:
> Dgit absolutely can be used to prepare a bunch of patches. But unless
> the maintainer actually uses dgit, it's not clear that the result is
> easier for the maintainer to merge than a well submitted patch via the
> bts produced fr
On 17.06.19 06:53, Helmut Grohne wrote:
> Whether I use apt-get source and debdiff or dgit
> and git format-patch is a detail on my side.
out of curiosity (and because i usually quite enjoy your patches): do
you do use dgit in *your* workflow?
fgmadsr
IOhannes
On Mon, Jun 17, 2019 at 06:53:05AM +0200, Helmut Grohne wrote:
>
> Still, vcs-git is not my preferred interface to the archive, because its
> lack of uniformity makes using it unproductive for me.
In other words: If vcs-git would be uniform would this be more
attractive to you?
Kind regards
Hi Sam,
On Sun, Jun 16, 2019 at 08:08:51PM -0400, Sam Hartman wrote:
> Ian> That depends, I think, on whether you are trying to (a) join a
> Ian> maintainer team, or do "maintainer-like" work; or, (b) do
> Ian> cross-archive work with small changes to many packages, or
> Ian> archi
When I outlined disadvantages and advantages I tried to follow what
people who have been participating in the discussion to date described
as advantages and disadvantages. For the things I listed I have high
confidence that the people involved understood the tools they were using
and their own nee
I haven't really organised my thoughts and have been travelling a lot
and am very tired, so this is a bit bitty. I may respond more
usefully in a day or two:
Sam Hartman writes ("The Difference between debcheckout and dgit and what they
try to accomplish"):
> Debcheckout all
I'm trying to organize my thoughts leading towards a discussion about
git on salsa.
Last month we had a wide ranging discussion that started from a
discussion of preferred formats for git branch structure.
During that discussion, we explored the differences in what a tool like
debcheckout gives
24 matches
Mail list logo
