On 8/1/07, Luk Claes <[EMAIL PROTECTED]> wrote:
> Removal hint added.
Thanks!
--
Martín Ferrari
Martín Ferrari wrote:
> Hi,
>
> This is a new package I created a few days ago, it was NEW on the
> 20th. Yesterday I found and fixed a bug in memory allocation that
> could trigger some memory corruption (and in my testing an immediate
> abort). I think it's very unlikely to be a security problem
Aníbal Monsalve Salazar wrote:
> On Sat, Jul 21, 2007 at 11:19:14PM +0200, Frans Pop wrote:
>> On Saturday 21 July 2007 19:47, Joerg Jaspert wrote:
>>> rdate is in NEW and has a udeb added. Accept/Reject?
>> Please accept.
>
> Please allow rdate in testing. It has been discussed in
> debian-boot a
On Sat, Jul 21, 2007 at 11:19:14PM +0200, Frans Pop wrote:
>On Saturday 21 July 2007 19:47, Joerg Jaspert wrote:
>>rdate is in NEW and has a udeb added. Accept/Reject?
>
>Please accept.
Please allow rdate in testing. It has been discussed in
debian-boot and the recent D-I meeting.
Muy cordialment
Hi,
This is a new package I created a few days ago, it was NEW on the
20th. Yesterday I found and fixed a bug in memory allocation that
could trigger some memory corruption (and in my testing an immediate
abort). I think it's very unlikely to be a security problem, and if it
were, you should have
libglew has been changed to libglew1.4, the following depending package still
needs to be updated, on all archs:
rss-glx_0.8.1-6, rebuild against libglew1.4, 1, alpha, amd64, arm, hppa, i386,
ia64, m68k, mips, mipsel, powerpc, s390, sparc
I tested the build locally and it works fine.
Thanks, J
Hi,
As already discussed on IRC, we plan to update tzdata in Etch using a
new upstream database. This will be done in two steps:
- upload to volatile to have an update now for those who use volatile ;
- upload to stable to have an update for Etch r2.
Please find below the corresponding changelo
Andreas Barth <[EMAIL PROTECTED]> wrote:
Hi,
> The release goal includes BTW all that strange things. Up to now, IPv6
> crept somehow into Debian, without anyone coordinating. As these days,
Well, there has been a somewhat coordinated effort a couple of years
ago, with a webapp tracking the stat
* Tomas Pospisek ([EMAIL PROTECTED]) [070731 00:54]:
> IPv6 is set as a release goal.
>
> Is having Debian CDs work out of the box for the average user plugging
> into an everyday ISP also a release goal?
That's not a release goal, but a necessarity.
The release goal includes BTW all that stran
* Mike Hommey ([EMAIL PROTECTED]) [070730 22:55]:
> IPv6 enabled by default in a IPv4-only environment is a PitA. And this
> is probably impossible to fix.
We could (by default / sensible probing / ...) blacklist the
ipv6-module. I'm though not sure if this is the right thing to do.
Cheers,
Andi
On Mon, Jul 30, 2007 at 07:52:47PM +0200, Tomas Pospisek wrote:
> * ask the user at install time whether he wants IPv6 on
Without arguing for or against ipv6, asking user at install
time is the worst solution.
1) it adds a extra step in installer for everyone
2) most endusers won't understand the
On Tue, Jul 31, 2007 at 11:13:42AM +0200, Wouter Verhelst wrote:
> before A is the recommended way of resolving a domain name. Not
> doing so would make us not RFC-compliant, which is not the way to go
> IMO.
Could this ipv6 primer be taken to a more appropriate list, please? -devel,
perhap
On Mon, Jul 30, 2007 at 11:26:20AM -0700, Mike Bird wrote:
> I would add only one point to Tomas Pospisek's excellent
> analysis. Without diligent precautions, IPv6 is horribly
> insecure. You thought your firewall protected you, but
> now "apt-get dist-upgrade" will open your protected apps
> to
On Mon, Jul 30, 2007 at 07:52:47PM +0200, Tomas Pospisek wrote:
> * Software that binds to the first socket found
> Then there's software that binds to the first port it gets and is
> difficult to teach not to do so. [2]
There is nothing like a "first socket". Software either binds to any
addr
On Tue, Jul 31, 2007 at 11:13:42AM +0200, Wouter Verhelst wrote:
> In all other cases, your machine should do the resolving, try to
> connect, _immediately_ get a "no route to host", and fall back to v4. I
> don't see the problem?
Issues imposed by high latency, high packet loss or slow DNS s
On Mon, Jul 30, 2007 at 07:52:47PM +0200, Tomas Pospisek wrote:
> Hallo Release Team,
>
> I've read in the release goals:
>
>> RELEASE GOALS
>> =
>>
>> * full IPv6 support
>> Advocate: Martin Zobel-Helas
>
> and wrote to Martin Zobel-Helas who redirected me here.
>
> My experience with
Hi stable release managers,
Would you accept a fix for bug#426000 in Etch? The patch comes from
upstream CVS, and the diff could be found here:
http://sourceware.org/cgi-bin/cvsweb.cgi/libc/stdio-common/vfscanf.c.diff?cvsroot=glibc&r1=1.110.2.6&r2=1.110.2.7
Cheers,
Aurelien
--
.''`. Aurelie
17 matches
Mail list logo
