On 08/04/2018 09:05 AM, Ruben Undheim wrote:
> Hi,
>
>>> 2/ Ondrej Novy will do a mass-change from git-dpm to gbp on team packages.
>>> Related to this, Piotr will review and amend the team policy if necessary,
>>> as
>>> well as work on the pipeline to make sure the policy gets published from
>>>
On Aug 08 2018, Thomas Goirand wrote:
> On 08/04/2018 09:05 AM, Ruben Undheim wrote:
>> Hi,
>>
2/ Ondrej Novy will do a mass-change from git-dpm to gbp on team packages.
Related to this, Piotr will review and amend the team policy if necessary,
as
well as work on the pipeline
Hi,
> The problem with git-debrebase will be the same as with git-dpm. As soon
> as you try to upgrade / merge a new upstream release, you dive into a
> rebase/conflict nightmare.
So in other words, you prefer to solve the same conflicts manually with
quilt/quilt refresh or get similar but worse
Hi,
pá 3. 8. 2018 v 5:06 odesílatel Ondrej Novy napsal:
> 1. convert git-dpm -> gbp
>
this is done.
--
Best regards
Ondřej Nový
Email: n...@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
On 08/08/2018 01:38 PM, Nikolaus Rath wrote:
> That doesn't make sense to me. git-dpm maintains (and rebases) Debian
> patches separately, so upgrading to a new upgrade release can
> principally not be any harder than with gbp.
It is a nightmare when patches are conflicting.
> The problems with g
On 08/08/2018 03:55 PM, Ruben Undheim wrote:
> Hi,
>
>> The problem with git-debrebase will be the same as with git-dpm. As soon
>> as you try to upgrade / merge a new upstream release, you dive into a
>> rebase/conflict nightmare.
>
> So in other words, you prefer to solve the same conflicts man
On Aug 08 2018, Thomas Goirand wrote:
> On 08/08/2018 01:38 PM, Nikolaus Rath wrote:
>> That doesn't make sense to me. git-dpm maintains (and rebases) Debian
>> patches separately, so upgrading to a new upgrade release can
>> principally not be any harder than with gbp.
>
> It is a nightmare when
Nikolaus Rath writes:
> The problems with git-dpm are the implementation and lack of
> maintenance, not the way the Debian changes are managed.
git-dpm requires that you always use its tools. If another maintainer
got confused and used another toolset to upgrade the upstream version,
things cou
Ruben Undheim writes:
> There is no nightmare unless there are patch conflicts.
The one case where you could have a "nightmare" is:
1. Maintainer A updates package to latest upstream version.
2. Maintainer A uploads packages to Debian, and it is accepted.
3. Maintainer A forgets to push changes
9 matches
Mail list logo
