Control: tags -1 + moreinfo
On Wed, 2024-05-15 at 22:10 +1000, Joris van der Geer wrote:
> package:libc6-dev
> version: 2.36
There's no such version of the package. However, assuming you mean the
package in bookworm (2.36-9+deb12u5),
> Libc6 omits thr ‘bits’ directory, rendering glibc
On Mon, 2024-05-06 at 13:02 +0200, Jan Krčmář wrote:
> Package: libc6
> Version: 2.28-10+deb10u3
>
> Upgrading the system (Debian 10/Buster) causes corrupted system,
> ending with kernel panic and unbootable system.
>
[...]
> The following packages will be upgraded:
> apt apt-transport-https
On Fri, 2024-02-16 at 17:35 +, Jonathan Wiltshire wrote:
> The next point release for "bookworm" (12.6) is scheduled for
> Saturday, April 6th. Processing of new uploads into bookworm-
> proposed-updates will be frozen during the preceeding weekend.
Due to recent events, the point release has
Hi,
The next point release for "bullseye" (11.9) is scheduled for Saturday,
February 10th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bookworm" (12.5) is scheduled for Saturday,
February 10th. Processing of new uploads into bookworm-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bookworm" (12.3) is scheduled for Saturday,
December 9th. Processing of new uploads into bookworm-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.7) is scheduled for Saturday,
April 29th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.6) is scheduled for Saturday,
December 17th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next - and final - point release for "buster" (10.13) is scheduled
for Saturday, September 10th. Processing of new uploads into buster-
proposed-updates will be frozen during the weekend of August 27th.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.5) is scheduled for Saturday,
September 10th. Processing of new uploads into bullseye-proposed-
updates will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.4) is scheduled for Saturday,
July 9th. Processing of new uploads into bullseye-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.12) is scheduled for Saturday,
March 26th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.3) is scheduled for Saturday,
March 26th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.2) is scheduled for Saturday,
December 18th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The first point release for "bullseye" (11.1) is scheduled for
Saturday, October 9th. Processing of new uploads into bullseye-
proposed-updates will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.11) is scheduled for Saturday,
October 9th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.10) is scheduled for Saturday
June 19th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.9) is scheduled for Saturday
March 27th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.8) is scheduled for Saturday
February 6th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.7) is scheduled for Saturday
December 5th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.6) is scheduled for Saturday
September 26th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
On Sun, 2020-07-12 at 15:37 +0100, Adam D. Barratt wrote:
> On Sat, 2020-06-27 at 14:35 +0100, Adam D. Barratt wrote:
> > The next point release for "buster" (10.5) is scheduled for
> > Saturday July 18th. Processing of new uploads into buster-proposed-
> >
Hi,
On Sat, 2020-06-27 at 14:35 +0100, Adam D. Barratt wrote:
> The next point release for "buster" (10.5) is scheduled for Saturday
> July 18th. Processing of new uploads into buster-proposed-updates
> will be frozen during the preceding weekend.
Unfortunately this ha
Hi,
The next point release for "buster" (10.5) is scheduled for Saturday
July 18th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next - and final - point release for "stretch" (9.13) is scheduled
for Saturday, July 18th. Processing of new uploads into stretch-
proposed-updates will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.4) is scheduled for Saturday,
May 9th. Processing of new uploads into buster-proposed-updates will be
frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.12) is scheduled for Saturday,
February 8th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.3) is scheduled for Saturday,
February 8th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.2) is scheduled for Saturday,
November 16th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The first point release for "buster" (10.1) is scheduled for Saturday,
September 7th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.10) is scheduled for Saturday,
September 7th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.9) is scheduled for Saturday,
April 27th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.8) is scheduled for Saturday,
February 16th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.6) is scheduled for Saturday,
November 10th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Fri, 2018-06-29 at 11:44 +0100, Luke Kenneth Casson Leighton wrote:
[...]
> On Fri, Jun 29, 2018 at 10:35 AM, Adam D. Barratt
> wrote:
>
> > > what is the reason why that package is not moving forward?
> >
> > I assume you're referring to the dpkg upload t
On Fri, 2018-06-29 at 10:20 +0100, Luke Kenneth Casson Leighton wrote:
[...]
> debian-riscv has been repeatedly asking for a single zero-impact
> line
> to be included in *one* file in *one* dpkg-related package which
> would
> allow riscv to stop being a NMU architecture and become part of
>
Hi,
The next point release for "stretch" (9.5) is scheduled for Saturday,
July 14th. Processing of new uploads into stretch-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.4) is scheduled for Saturday,
March 10th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Control: tags -1 + pending
On Sun, 2018-01-14 at 11:52 +0100, Aurelien Jarno wrote:
> On 2018-01-13 17:26, Julien Cristau wrote:
> > Control: tag -1 confirmed
> >
> > On Sat, Dec 9, 2017 at 14:22:45 +0100, Aurelien Jarno wrote:
> >
> > > Unfortunately it didn't make in 9.3 due to the
Control: tags -1 + pending
On Fri, 2017-12-01 at 21:15 +0100, Aurelien Jarno wrote:
> On 2017-12-01 19:49, Cyril Brulebois wrote:
> > Adam D. Barratt <a...@adam-barratt.org.uk> (2017-11-24):
> > > This looks OK to me, but will need a KiBi-ack; CCing.
> >
>
Control: tags -1 + confirmed d-i
On Wed, 2017-11-22 at 18:02 +0100, Aurelien Jarno wrote:
> On 2017-11-19 18:36, Aurelien Jarno wrote:
[...]
> > I would like to upload a new glibc package for the next stretch
> > release.
> > It mostly consists in pulling the release/2.24/master upstream
> >
Hi,
The next point release for "jessie" (8.10) is scheduled for Saturday,
December 9th. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.3) is scheduled for Saturday,
December 9th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The first point release for "stretch" (9.1) is scheduled for Saturday,
July 22nd. Processing of new uploads into stretch-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "jessie" (8.9) is scheduled for Saturday,
July 22nd. Processing of new uploads into jessie-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "jessie" (8.8) is scheduled for Saturday, May
6th. Processing of new uploads into jessie-proposed-updates will be
frozen during the preceding weekend.
Regards,
Adam
On Sat, 2016-11-26 at 01:02 -0600, Steve M. Robbins wrote:
> The following packages have unmet dependencies:
> cli-common : Depends: perl but it is not going to be installed
> libc6 : Breaks: libc6:i386 (!= 2.24-7) but 2.24-5 is to be installed
> libc6:i386 : Breaks: libc6 (!= 2.24-5) but
Hi,
The next point release for "jessie" (8.6) is scheduled for Saturday,
September 17th. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "jessie" (8.4) is scheduled for Saturday,
April 2nd. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "wheezy" (7.10) is scheduled for Saturday,
April 2nd. Processing of new uploads into wheezy-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "jessie" (8.3) is scheduled for Saturday,
January 23rd. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for wheezy (7.9) is scheduled for Saturday,
September 5th. Processing of new uploads into wheezy-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
signature.asc
Description: This is a digitally signed message part
Hi,
The next point release for jessie (8.2) is scheduled for Saturday,
September 5th. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
signature.asc
Description: This is a digitally signed message part
Hi,
The first point release for jessie (8.1) is scheduled for Saturday,
June 6th. Stable NEW will be frozen during the preceding weekend.
Regards,
Adam
signature.asc
Description: This is a digitally signed message part
Hi,
The next point release for wheezy (7.8) is scheduled for Saturday,
January 10th. Stable NEW will be frozen during the preceding weekend.
Regards,
Adam
signature.asc
Description: This is a digitally signed message part
Hi,
The next point release for wheezy (7.7) is scheduled for Saturday,
October 18th. Stable NEW will be frozen during the preceding weekend.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
The next point release for wheezy (7.6) is scheduled for Saturday,
July 12th. Stable NEW will be frozen during the preceding weekend.
As usual, base-files can be uploaded at any point before the freeze.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
Hi,
The next (and final) point release for squeeze (6.0.10) is scheduled
for Saturday, July 19th. Oldstable NEW will be frozen during the
preceding weekend.
As usual, base-files can be uploaded at any point before the freeze.
Regards,
Adam
--
To UNSUBSCRIBE, email to
Hi,
The next point release for wheezy (7.5) is scheduled for Saturday,
April 26th. Stable NEW will be frozen during the preceding weekend.
As usual, base-files can be uploaded at any point before the freeze.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
Hi,
The next point release for wheezy (7.4) is scheduled for Saturday
February 8th. Stable NEW will be frozen during the preceding weekend.
As usual, base-files can be uploaded at any point before the freeze.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
Hi,
The next point release for squeeze (6.0.9) is scheduled for Saturday
February 15th. Stable NEW will be frozen during the preceding weekend.
As usual, base-files can be uploaded at any point before the freeze.
Regards,
Adam
--
To UNSUBSCRIBE, email to
On Tue, 2014-01-21 at 19:00 +0100, intrigeri wrote:
Julien Cristau wrote (04 Dec 2013 14:00:10 GMT) :
On Wed, Oct 2, 2013 at 16:44:41 +0100, Adam D. Barratt wrote:
[...]
If someone puts together a debdiff including them, I'm more than
happy to look at that and we can make a call from
On Tue, 2014-01-21 at 12:23 -0700, Adam Conrad wrote:
On Tue, Jan 21, 2014 at 06:52:31PM +, Adam D. Barratt wrote:
I suspect all of the changes made it in to the 2.13-38+deb7u1 upload,
but confirmation of that would be appreciated.
Yeah, I'm inclined to say that upload covered
On 2013-10-02 16:14, Adam Conrad wrote:
On Tue, Oct 01, 2013 at 10:23:22PM +0100, Adam D. Barratt wrote:
That looks okay. In terms of the other suggested updates, as a
non-release architecture for wheezy, hurd-specific patches aren't
really
appropriate for a stable update.
Perhaps
Hi,
Apologies for the delay in getting back to you about this.
On Fri, 2013-06-21 at 14:15 +0200, Petr Salinger wrote:
One more problem popped up - #712196
The fix is one-liner:
--- kfreebsd/syscalls.list
+++ kfreebsd/syscalls.list
-sys_ktimer_settime - ktimer_settime
On Thu, 2013-09-26 at 12:31 -0500, Matthew P Zagrabelny wrote:
It looks like tzdata was updated in wheezy/updates from 2013c-0wheezy1
to 2013d-0wheezy1. This looks to break tzdata-java:
(Small but important point - you mean wheezy-updates; wheezy/updates
would be part of a security.d.o path.)
On Fri, 2012-10-19 at 19:04 +0200, Aurelien Jarno wrote:
On Fri, Oct 19, 2012 at 05:06:15PM +0100, Adam D. Barratt wrote:
On 19.10.2012 15:43, Aurelien Jarno wrote:
I have uploaded a new version of tzdata to both wheezy (2012g-1) and
squeeze (2012g-0squeeze1). This upload has been triggered
On 19.10.2012 15:43, Aurelien Jarno wrote:
I have uploaded a new version of tzdata to both wheezy (2012g-1) and
squeeze (2012g-0squeeze1). This upload has been triggered by a DST
change this week-end in some parts of Brazil (see bug#690606), but I
have realized at the same occasion that both
reassign 669858 src:eglibc
tags 669858 + wheezy sid
found 669858 2.13-30
thanks
On Sat, 2012-04-21 at 13:07 +0100, peter green wrote:
Package: eglibc
Severity: serious
Thanks for filing this and other FTBFS reports recently. A couple of
comments / requests:
Please include version information
On Sat, 2012-02-25 at 12:20 +, Robert Millan wrote:
660403: cdparanoia: FTFBS on kfreebsd-*
- Unless there's further activity I recommend removing of kfreebsd-*
binaries from testing. See
http://bugs.debian.org./cgi-bin/bugreport.cgi?bug=660403#12
That doesn't work. The choices would be
On Tue, 2012-02-14 at 12:54 +0100, Bernhard R. Link wrote:
* Adam D. Barratt a...@adam-barratt.org.uk [120212 22:06]:
As I mentioned previously: Bernhard, JBK (and anyone else affected and
watching the bugs) - once the package is available for your architecture
via proposed-updates, please
tag 658424 + pending
thanks
On Sun, 2012-02-12 at 20:38 +0100, Aurelien Jarno wrote:
On Sat, Feb 11, 2012 at 11:09:49AM +, Adam D. Barratt wrote:
That's unfortunate, but I'm not sure we should let it block getting the
fix to stable users any further. Please go ahead with the upload
tag 658424 + confirmed squeeze
thanks
On Tue, 2012-02-07 at 22:48 +0100, Aurelien Jarno wrote:
On Tue, Feb 07, 2012 at 09:45:12PM +, Adam D. Barratt wrote:
On Thu, 2012-02-02 at 23:11 +0100, Aurelien Jarno wrote:
eglibc 2.11.3-2 shipped in Debian Squeeze 6.0.4 suffers from
On Wed, 2011-12-14 at 07:54 +0100, Aurelien Jarno wrote:
On Tue, Dec 13, 2011 at 06:41:54PM +, Adam D. Barratt wrote:
On Tue, 2011-12-13 at 17:55 +0100, Aurelien Jarno wrote:
Would it be possible to upload this, and do a call for test for people
wanting to test it before the actual
On Tue, 2011-12-13 at 17:55 +0100, Aurelien Jarno wrote:
I have attached a new version of what we plan to upload. It includes a
few more fixes backported from the unstable version (look at the end of
the changelog), and also a few more fixes from upstream (no new stable
version have been
On Sun, 2011-10-30 at 19:27 +0100, Aurelien Jarno wrote:
On Sun, Oct 30, 2011 at 05:36:27PM +, Adam D. Barratt wrote:
Did the 2.11.4 release happen? I'm conscious of the fact that we're now
a little way past 6.0.3; apologies for not following up again sooner.
I have asked
On Tue, 2011-11-01 at 00:10 +0100, Aurelien Jarno wrote:
As part of the weekly tzdata upload (well I hope things will slow down
soon), I have just uploaded tzdata 2011n to both lenny-volatile and
squeeze. It includes DST fixes for:
- Cuba.
- Fidji.
- Pridnestrovian Moldavian Republic.
On Sat, 2011-09-10 at 22:53 +0200, Aurelien Jarno wrote:
The status is that glibc 2.11.4 will be released when Debian feels it
is ready, as we are the main testers here. I am planning to do some more
testing of the current SVN on more machines, and everything seems fine
around the release of
On Tue, 25 Oct 2011 21:22:57 +0100, Adam D. Barratt wrote:
On Tue, 2011-10-25 at 21:27 +0200, Aurelien Jarno wrote:
On Tue, Oct 25, 2011 at 07:22:37PM +0100, Adam D. Barratt wrote:
On Tue, 2011-10-25 at 05:39 +0200, Aurelien Jarno wrote:
I have just uploaded tzdata 2011m to both lenny
On Tue, 2011-10-25 at 05:39 +0200, Aurelien Jarno wrote:
I have just uploaded tzdata 2011m to both lenny-volatile and squeeze.
Thanks. fwiw, it's also transitioned to testing. (although I'm not
convinced that it justified urgency=critical, with four days before
the new changes take effect :P)
On Tue, 2011-10-25 at 21:27 +0200, Aurelien Jarno wrote:
On Tue, Oct 25, 2011 at 07:22:37PM +0100, Adam D. Barratt wrote:
On Tue, 2011-10-25 at 05:39 +0200, Aurelien Jarno wrote:
I have just uploaded tzdata 2011m to both lenny-volatile and squeeze.
[...]
I'm hoping to get the VUA for lenny
On Wed, 2011-10-19 at 09:04 +0200, Aurelien Jarno wrote:
On Wed, Oct 19, 2011 at 07:49:50AM +0100, Adam D. Barratt wrote:
On Mon, 17 Oct 2011 22:17:48 +0200, Aurelien Jarno wrote:
Due to change in one of the Brazilian timezone last week-end, I have
uploaded version 2011l-0squeeze1 of tzdata
On Mon, 17 Oct 2011 22:17:48 +0200, Aurelien Jarno wrote:
Due to change in one of the Brazilian timezone last week-end, I have
uploaded version 2011l-0squeeze1 of tzdata to
stable-proposed-updates.
For the record, I pushed this via squeeze-updates overnight (see
SUA17-1).
Technically only
On Sun, 2011-09-18 at 23:52 +0200, Aurelien Jarno wrote:
On my side can only confirm that upgrading from 2011d to 2011h indeed
changes the Egyptian timezone. So maybe we can simply push it to
proposed-updates.
Assuming squeeze-updates, I'll have a look at that in the next day or
so.
Anyway
On Wed, 2011-09-14 at 16:40 +0200, Youssef Eldakar wrote:
On 01/-10/-28163 09:59 PM, Adam D. Barratt wrote:
On Fri, 2011-09-02 at 17:23 +0400, Eugene Barbashin wrote:
[Russian law changes on October 30th]
For the record, after some discussion with the maintainers on IRC and as
the next
On Mon, 2011-09-12 at 20:27 +0200, Julien Cristau wrote:
On Sat, Sep 10, 2011 at 22:53:15 +0200, Aurelien Jarno wrote:
The status is that glibc 2.11.4 will be released when Debian feels it
is ready, as we are the main testers here. I am planning to do some more
testing of the current SVN
On Fri, 2011-09-02 at 17:23 +0400, Eugene Barbashin wrote:
I don't think there is a real need to push to to -updates. Nobody
requested about this changes in lenny or squeeze, so I guess they are
not that important.
It's very important update for everyone using debian in Russia, so
please,
On Mon, 2011-08-29 at 23:30 +0200, Aurelien Jarno wrote:
On Mon, Aug 29, 2011 at 04:30:41PM +0100, Adam D. Barratt wrote:
On Sat, 2011-08-13 at 14:47 +0200, Aurelien Jarno wrote:
On Fri, Jun 17, 2011 at 10:48:51AM +0100, Adam D. Barratt wrote:
Given the timescales of the upcoming 6.0.2
On Sat, 2011-08-13 at 14:47 +0200, Aurelien Jarno wrote:
On Fri, Jun 17, 2011 at 10:48:51AM +0100, Adam D. Barratt wrote:
[...]
Thanks. From what I've seen, I'd be interested in seeing the fixes
applied to p-u.
Given the timescales of the upcoming 6.0.2 and the larger-than-usual
size
On Sat, 2011-06-11 at 21:27 +0200, Aurelien Jarno wrote:
On Wed, Jun 08, 2011 at 07:12:57PM +0200, Philipp Kern wrote:
Aurelien,
On Sun, Jun 05, 2011 at 12:23:51PM +0200, Aurelien Jarno wrote:
I am therefore thinking about uploading the next upstream stable version
(2.11.4 is
On Wed, 2011-03-23 at 19:31 +0100, Aurelien Jarno wrote:
On Tue, Mar 22, 2011 at 01:26:41PM +0100, Philipp Kern wrote:
we just received the following request for 2011d in lenny-volatile and
squeeze-updates. Could you prepare the uploads?
I should have a bit of time tonight to work on
On Fri, 2011-03-11 at 20:07 +, Adam D. Barratt wrote:
Assuming everything goes according to plan (adding packages to
squeeze-updates hasn't actually been tested yet) I'm planning on pushing
the tzdata update in tomorrow morning.
Unfortunately, that didn't happen yet. Adding packages
On Sat, 2011-03-12 at 12:09 +, Adam D. Barratt wrote:
On Fri, 2011-03-11 at 20:07 +, Adam D. Barratt wrote:
Assuming everything goes according to plan (adding packages to
squeeze-updates hasn't actually been tested yet) I'm planning on pushing
the tzdata update in tomorrow morning
On Fri, 2011-03-11 at 16:54 -0300, Henrique de Moraes Holschuh wrote:
On Fri, 11 Mar 2011, Martin Zobel-Helas wrote:
On Fri Mar 11, 2011 at 13:11:52 -0600, Gunnar Wolf wrote:
Chile was supposed to leave the Summer daylight savings period this
coming weekend, but it was pushed to April
On Fri, 2011-03-11 at 13:54 -0600, Gunnar Wolf wrote:
Martin Zobel-Helas dijo [Fri, Mar 11, 2011 at 08:31:36PM +0100]:
Chile was supposed to leave the Summer daylight savings period this
coming weekend, but it was pushed to April 2nd. The fixes have been
accepted to the package in Sid,
tag 611629 + moreinfo
thanks
On Mon, January 31, 2011 12:46, Teodor wrote:
An almost up-to-date system upgraded last week cannot be upgraded today
due to
libc6 configuration errors:
Looking at the log, it doesn't appear the errors are actually due to
libc6, however. This section suggests a
user release.debian@packages.debian.org
usertag 611411 + squeeze-can-defer
tag 611411 + squeeze-ignore
thanks
On Sat, 2011-01-29 at 01:08 +0100, Jakub Wilk wrote:
glibc-doc-reference FTBFS in a clean squeeze chroot. Tail of the build
log:
| texi2dvi --pdf libc.texinfo
| make[1]: ***
On Tue, 2011-01-11 at 21:35 +0100, Florian Weimer wrote:
I would like to make an upload of eglibc to address DSA-2122-2 (the
first round of patches for the $ORIGIN/LD_AUDIT issue does not cover
all corner cases, unfortunately).
[...]
Should I push this through testing-security,
On Thu, 2010-11-18 at 15:31 +0100, Jan Rasche wrote:
tzdata tries to execute stuff under /tmp during install. As lot of people
used to mount /tmp
noexec for security reasons this will raise errors.
tzdata does no such thing. The culprit is clearly visible:
[...]
Can't exec
Hi,
On Mon, 2009-10-12 at 11:10 +0200, Aurelien Jarno wrote:
Would it be possible to do a stable upload to fix this problem (see
below)?
From the bug log I'd say this should indeed be fixed in stable. Please
could you supply the proposed debdiff for confirmation?
Thanks,
Adam
--
To
1 - 100 of 110 matches
Mail list logo