[Pkg-chromium-maint] chromium-browser_37.0.2062.120-1_amd64.changes REJECTED

[Michael Gilbert]

On Sun, Sep 21, 2014 at 1:07 PM, Giuseppe Iuculano wrote:
> Il 21/09/2014 15:25, Michael Gilbert ha scritto:
>> I apologize for not pushing often enough lately.  In experimental, I
>> had been avoiding dealing with git for a while since things were in
>> too much of a working state.
>
> So, do you think that working on experimental for months and push an
> unique commit like this is "a working state" ?
>
> http://anonscm.debian.org/cgit/pkg-chromium/pkg-chromium.git/commit/?id=a7456245602faacbe7f9c30dedb2215116e37e54

Like I had stated early on while I was working on those experimental
changes, git was slowing me down, so I was avoiding it while doing
rapid releases.  All of that was experiment, and not intended to go
into unstable without more thought/consideration.  In the meantime
unstable was maintained concurrently and kept up to date in git.

Plus the archive acts as a (coarse) vcs anyway.

>> Although that was not the case last night; I did the upload finally
>> after almost a day of work then went to bed and was going to push
>> changes in the morning.  Since it was lintian rejected, that means I
>> have work to do before pushing, and I will do that.
>>
>> I would really like to work together, so again I apologize.  I too was
>> blocked, and it took hard work to get unblocked.  It was not the state
>> of the repository itself causing any blocking, it was a matter of
>> figuring out how to get the package building again given upstream's
>> often breaking changes.
>>
>> So, I guess my message is that I think the animosity is directed at me
>> both fairly and unfairly, especially since I did put in a ton of
>> effort to get the packaging back to a working state.
>
>
> Ok, so you think the correct way to maintain the chromium browser is
> doing a lot of work for months and no push in git (with a lot of
> reminder in email, "Michael please push your changes").

Sometimes git just gets in the way, so not using it at times makes
sense to me, but I would only ever consider doing that in
experimental.

Best wishes,
Mike