Holger Levsen:
> On Tue, Feb 14, 2017 at 08:44:00PM +, Ximin Luo wrote:
>> I do think it's OK to try to support diffoscope 67 for 2 years because it's
>> been quite well tested.
>
> well, yes… but…
>
>> I understand that 77 fixes quite a lot of bugs over 67…
>
> 77 *exists* and is quite
On Tue, Feb 14, 2017 at 08:44:00PM +, Ximin Luo wrote:
> I do think it's OK to try to support diffoscope 67 for 2 years because it's
> been quite well tested.
well, yes… but…
> I understand that 77 fixes quite a lot of bugs over 67…
77 *exists* and is quite probably a lot better than 67,
Holger Levsen:
> On Tue, Feb 14, 2017 at 09:38:51AM +1300, Chris Lamb wrote:
>>> what did you plan on to do with diffoscope in regard to Debian's
>>> stretch when you decided to work on it
>> I didn't decide anything at all; I was enjoying the coding, adding
>> features, tests, squashing bugs...
>
On Tue, Feb 14, 2017 at 09:38:51AM +1300, Chris Lamb wrote:
> > what did you plan on to do with diffoscope in regard to Debian's
> > stretch when you decided to work on it
> I didn't decide anything at all; I was enjoying the coding, adding
> features, tests, squashing bugs...
you decided to put
On Mon, Feb 13, 2017 at 01:56:42PM -0800, Vagrant Cascadian wrote:
> They've always been against backporting versions not present in testing,
> but I haven't seen a response like that to what I proposed, and don't
> see it listed anywhere on:
>
> https://backports.debian.org/Contribute/
On 2017-02-13, Mattia Rizzolo wrote:
> On Mon, Feb 13, 2017 at 01:32:55PM -0800, Vagrant Cascadian wrote:
>> The other obvious option is to not ship a version in stretch and rely on
>> stretch-backports, if diffoscope development hasn't yet settled down
>> enough (will it ever) for a Debian stable
On Mon, Feb 13, 2017 at 01:32:55PM -0800, Vagrant Cascadian wrote:
> The other obvious option is to not ship a version in stretch and rely on
> stretch-backports, if diffoscope development hasn't yet settled down
> enough (will it ever) for a Debian stable release cycle...
THAT'S NOT POSSIBLE.
On 2017-02-13, Chris Lamb wrote:
> Mattia Rizzolo wrote:
>> Then, if the unblock is accepted, I'd say we should either freeze
>> diffoscope development […]
>
> Strongly against this. :)
>
>> or stop uploading to unstable
>
> We can always upload to experimental to keep release momentum. Or just
>
Mattia Rizzolo wrote:
> > Let's first try an unblock as that's cleaner and less hassle.
>
> I agree, would you proceed to file the unblock?
Sure.
> Then, if the unblock is accepted, I'd say we should either freeze
> diffoscope development […]
Strongly against this. :)
> or stop uploading to
On Tue, Feb 14, 2017 at 09:45:41AM +1300, Chris Lamb wrote:
> Let's first try an unblock as that's cleaner and less hassle.
I agree, would you proceed to file the unblock? As I said, I'm not up
for it myself for this case¹ :)
Then, if the unblock is accepted, I'd say we should either freeze
Mattia Rizzolo wrote:
> What do you think we should do to fix the RC in stretch? It's IMHO
> either convince the RT of making v77 migrate, or propose a t-p-u.
Let's first try an unblock as that's cleaner and less hassle.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'`
On Tue, Feb 14, 2017 at 09:38:51AM +1300, Chris Lamb wrote:
> I didn't decide anything at all; I was enjoying the coding, adding
> features, tests, squashing bugs...
Heh :)
> (However, whatever version ends up in stretch will surely become pretty
> outdated that we will be sending people to
Mattia Rizzolo wrote:
> what did you plan on to do with diffoscope in regard to Debian's
> stretch when you decided to work on it
I didn't decide anything at all; I was enjoying the coding, adding
features, tests, squashing bugs...
(However, whatever version ends up in stretch will surely
So, today I uploaded diffoscope v77, fixing the security bug introduced
in v67 (in stretch), plus hopefully fixing for good the tests.
The diff between v67 and v77 is *huge*, this is according to git:
161 files changed, 4247 insertions(+), 1324 deletions(-)
For a project the size of diffoscope
14 matches
Mail list logo
