Denis Barbier a écrit :
On Wed, Mar 01, 2006 at 03:22:50PM +0100, Aurelien Jarno wrote:
Lionel Elie Mamane a écrit :
- glibc maintainers, would you approve of such an update to a point
release of sarge?
I am *one* of the glibc maintainer, and I agree in principle with such a
change,
On Thu, 16 Mar 2006, Aurelien Jarno wrote:
Well I am currently trying to split the glibc to not have libraries and
binaries in the same package (that will be a problem for multiarch).
While I am doing that, I can also put the timezone data in a separate
package.
Please do. That will be a
On Thu, Mar 16, 2006 at 10:56:36AM +0100, Aurelien Jarno wrote:
Denis Barbier a écrit :
Ditto, but this should be done for all sarge stable releases, which is a
lot of work. IMO splitting timezone data into a seperate package in
the next sarge release would help future releases, if this is
On Wed, Mar 01, 2006 at 03:22:50PM +0100, Aurelien Jarno wrote:
Lionel Elie Mamane a écrit :
- glibc maintainers, would you approve of such an update to a point
release of sarge?
I am *one* of the glibc maintainer, and I agree in principle with such a
change, though I haven't look very
Lionel Elie Mamane a écrit :
On Thu, Feb 09, 2006 at 07:42:25PM +0900, GOTO Masanori wrote:
To get things rolling, I have prepared an updated glibc for sarge with
just the timezone data updated to the latest upstream upstream. It is
at http://people.debian.org/~lmamane/glibc/ . Technically right
On Thu, Feb 09, 2006 at 07:42:25PM +0900, GOTO Masanori wrote:
At Tue, 7 Feb 2006 14:30:01 +1100,
Anand Kumria wrote:
On Thu, Feb 02, 2006 at 11:42:31PM +0100, Lionel Elie Mamane wrote:
I just realised that the timezone data in glibc is taken from an
upstream database (namely
Am 2006-02-07 14:40:52, schrieb Ian Jackson:
2. The package fixes a critical bug which can lead into data loss,
data corruption, or an overly broken system, or the package is broken
or not usable (anymore).
That seems to be true in this case. I think a system which gets the
clock wrong
On Thu, Feb 09, 2006 at 07:42:25PM +0900, GOTO Masanori wrote:
At Tue, 7 Feb 2006 14:30:01 +1100,
Anand Kumria wrote:
On Thu, Feb 02, 2006 at 11:42:31PM +0100, Lionel Elie Mamane wrote:
I just realised that the timezone data in glibc is taken from an
upstream database (namely
At Tue, 7 Feb 2006 14:30:01 +1100,
Anand Kumria wrote:
On Thu, Feb 02, 2006 at 11:42:31PM +0100, Lionel Elie Mamane wrote:
Hi,
I just realised that the timezone data in glibc is taken from an
upstream database (namely ftp://elsie.nci.nih.gov/pub/). This data
sometimes changes, more
* Anand Kumria ([EMAIL PROTECTED]) [060207 04:34]:
I also think volatile is precisely the wrong place to put this kind of
data -- it isn't part of the default apt.sources for one thing; and it
places an extra burden on the maintainer(s) (who know have to track
three different upgrade paths,
On Tue, Feb 07, 2006 at 09:13:07AM +0100, Andreas Barth wrote:
* Anand Kumria ([EMAIL PROTECTED]) [060207 04:34]:
I also think volatile is precisely the wrong place to put this kind of
data -- it isn't part of the default apt.sources for one thing; and it
places an extra burden on the
[ debian-volatile dropped ]
Hi Daniel,
On Mon, Feb 06, 2006 at 11:41:26PM -0500, Daniel Jacobowitz wrote:
On Tue, Feb 07, 2006 at 02:30:01PM +1100, Anand Kumria wrote:
But that doesn't mean that we can issue an update to a stable package.
Currently they are mainly done for security
* Anand Kumria ([EMAIL PROTECTED]) [060207 09:52]:
On Tue, Feb 07, 2006 at 09:13:07AM +0100, Andreas Barth wrote:
* Anand Kumria ([EMAIL PROTECTED]) [060207 04:34]:
I also think volatile is precisely the wrong place to put this kind of
data -- it isn't part of the default apt.sources for
On Tue, Feb 07, 2006 at 07:52:15PM +1100, Anand Kumria wrote:
On Tue, Feb 07, 2006 at 09:13:07AM +0100, Andreas Barth wrote:
* Anand Kumria ([EMAIL PROTECTED]) [060207 04:34]:
I also think volatile is precisely the wrong place to put this kind of
data -- it isn't part of the default
2006/2/7, Anand Kumria [EMAIL PROTECTED]:
It's not us, but the stable maintainer, that you'd have to talk to;
he has traditionally not been interested in these sorts of updates to
stable as far as I know.
Well, perhaps a first start is creating the package for stable-updates;
would it be
* Martijn van Oosterhout ([EMAIL PROTECTED]) [060207 14:09]:
ISTM the d-volatile is the right place for this. However, in the mean
time I think someone should send a message to debian-announce that
anyone running a debian machine with an Australian (or other affected)
timezone needs to get
* Ian Jackson wrote:
Martijn van Oosterhout writes:
The requirements for getting into a stable release update are not
black magic, they're quite well known:
http://people.debian.org/~joey/3.1r1/
2. The package fixes a critical bug which can lead into data loss,
data corruption, or an
Martijn van Oosterhout writes (Re: timezone data packaged separately and in
volatile?):
The requirements for getting into a stable release update are not
black magic, they're quite well known:
http://people.debian.org/~joey/3.1r1/
2. The package fixes a critical bug which can lead
Hi Daniel,
On Monday, 06 Feb 2006, you wrote:
On Tue, Feb 07, 2006 at 02:30:01PM +1100, Anand Kumria wrote:
But that doesn't mean that we can issue an update to a stable package.
Currently they are mainly done for security purposes -- but stable updates
should not be confined to only
On Tue, Feb 07, 2006 at 09:57:54AM +0100, Andreas Barth wrote:
* Anand Kumria ([EMAIL PROTECTED]) [060207 09:52]:
On Tue, Feb 07, 2006 at 09:13:07AM +0100, Andreas Barth wrote:
* Anand Kumria ([EMAIL PROTECTED]) [060207 04:34]:
I also think volatile is precisely the wrong place to put
On Thu, Feb 02, 2006 at 11:42:31PM +0100, Lionel Elie Mamane wrote:
Hi,
I just realised that the timezone data in glibc is taken from an
upstream database (namely ftp://elsie.nci.nih.gov/pub/). This data
sometimes changes, more rapidly than our release cycle (and than any
release cycle we
On Tue, Feb 07, 2006 at 02:30:01PM +1100, Anand Kumria wrote:
But that doesn't mean that we can issue an update to a stable package.
Currently they are mainly done for security purposes -- but stable updates
should not be confined to only that. They should be done to keep the
system
On Thu, 02 Feb 2006, Lionel Elie Mamane wrote:
I just realised that the timezone data in glibc is taken from an
upstream database (namely ftp://elsie.nci.nih.gov/pub/). This data
sometimes changes, more rapidly than our release cycle (and than any
release cycle we can reasonable have).
See
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/03/2006 12:35 AM, Henrique de Moraes Holschuh wrote:
On Thu, 02 Feb 2006, Lionel Elie Mamane wrote:
I just realised that the timezone data in glibc is taken from an
upstream database (namely ftp://elsie.nci.nih.gov/pub/). This data
sometimes
On Fri, Feb 03, 2006 at 02:08:52AM -0200, Felipe Augusto van de Wiel (faw)
wrote:
On 02/03/2006 12:35 AM, Henrique de Moraes Holschuh wrote:
On Thu, 02 Feb 2006, Lionel Elie Mamane wrote:
I just realised that the timezone data in glibc is taken from an
upstream database (namely
25 matches
Mail list logo
