Hi folks,
since it seems the Release Team cannot find the time to review my big
debdiff and this bug should really not remain unfixed for so long, I
went ahead and uploaded the 1.2.1-2 version to unstable, which contains
just the backported fix for the security problem.
For convenience, I've adde
Hi Steven,
thanks for your comments.
the intent was to include version 1.2.2, I only included the debdiff for
1.2.1 since the final 1.2.2 release had not happened at that time.
It has now, so I'm preparing an updated debdiff right now.
> In which case perhaps you could attach a new debdiff? Yo
Hi Matthijs,
>From your diffs it seems to me the multiplay protocol version would be
1.2.2-RC1?
Does that mean clients running it would be still unable to connect to
the version 1.2.2 servers or vice-versa? These already seem to be the
relative majority (79 of them) according to the live server
On Sat, Aug 18, 2012 at 22:43:56 +0100, Steven Chamberlain wrote:
> Hi Matthijs,
>
> The debdiff is huge, which is probably why your mail went missing (maybe
> stuck in a queue for moderation?)
>
More likely dropped in a junk spool.
> Although, much of it is just strings/translation changes, wi
Hi Matthijs,
The debdiff is huge, which is probably why your mail went missing (maybe
stuck in a queue for moderation?)
Although, much of it is just strings/translation changes, with
particularly long lines.
Of course I cannot speak for the release team, but looking back, IMHO it
would have been
This is a resend of an earlier message that really didn't want to make
it through to the Debian servers. I've uploaded the debdiffs and
changelog here instead of attaching them:
http://www.stdout.nl/static/tmp/openttd-debdiffs/
Original message follows
---
Hi folks,
I've attached debdiffs for bo
Hi,
> Weird. It's really in my sent box, but it never ended up at bugs.d.o
> apparently. I'll resend the mail in a minute.
Apparently that didn't work either. My STMP logs show that bugs-master
accepted the resent message this morning, but then it got lost. I'll
contact the postmaster about that.
Hi Raphael,
> FWIW, I saw no debdiff on the list and there's no debdiff in
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683376 either.
>
> Are you sure you sent it to 683...@bugs.debian.org ?
Weird. It's really in my sent box, but it never ended up at bugs.d.o
apparently. I'll resend the ma
Hi,
On Fri, 17 Aug 2012, Matthijs Kooijman wrote:
> Hi folks,
>
> > I've attached debdiffs for both of the proposed options for review.
> I hate to nag, but upstream has released version 1.2.2 yesterday and I'd
> like to start packaging either option.
>
> Could someone have another look at this?
Hi folks,
> I've attached debdiffs for both of the proposed options for review.
I hate to nag, but upstream has released version 1.2.2 yesterday and I'd
like to start packaging either option.
Could someone have another look at this? Upstream has made no further
changes to 1.2.2 relative to 1.2.2-
Hi Niels,
> We cannot really make this decision without knowing what we are
> looking at.
> Please include a debdiff for each option showing the differences
> between the version in testing and the version that option would provide.
Ok, I'll do so as soon as upstream releases the 1.2.2 RC1, whi
tags 683376 + moreinfo
thanks
On 2012-07-31 10:47, Matthijs Kooijman wrote:
> Package: release.debian.org Severity: normal User:
> release.debian@packages.debian.org Usertags: unblock
>
> Please unblock package openttd. Recently, upstream developers have
> discovered a security problem in mo
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package openttd. Recently, upstream developers have
discovered a security problem in most versions of OpenTTD, including the
one in testing.
For squeeze/stable, a fixed packa
13 matches
Mail list logo