tag 685865 +moreinfo
thanks
Some questions that occur are:
1.) What version are you upgrading from?
2.) Have you tried using apt rather than synaptic? (So yes I better have
a play with synaptic but I cannot just now).
3.) Can you try breaking down the process so we can pinpoint more
exactly wh
severity 685072 normal
tag -confirmed +unreproducible
thanks
I have been unable to reproduce this consistently. When I did it was a
different message from what was originally reported. I have tried going
back in time with snapshots.debian.org and I cannot reproduce it.
It occurs to me that my i
severity 685072 normal
tag -confirmed +unreproducible
thanks
I have been unable to reproduce this consistently. When I did it was a
different message from what was originally reported. I have tried going
back in time with snapshots.debian.org and I cannot reproduce it.
It occurs to me that my i
I was investigating this further. After doing a general upgrade I can no
longer reproduce this. I have tried recreating the situation in a
schroot but failed. Amy more information would be appreciated.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsu
I was investigating this further. After doing a general upgrade I can no
longer reproduce this. I have tried recreating the situation in a
schroot but failed. Amy more information would be appreciated.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubs
Sorry wrong bug.
On 19/08/12 14:58, Nicholas Bamber wrote:
> I was investigating this further. After doing a general upgrade I can no
> longer reproduce this. I have tried recreating the situation in a
> schroot but failed. Amy more information would be ap
I was investigating this further. After doing a general upgrade I can no
longer reproduce this. I have tried recreating the situation in a
schroot but failed. Amy more information would be appreciated.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsu
tag 685072 -moreinfo -unreproducible +confirmed
thanks
I can confirm this now. The steps to reproduce (on a sid machine) are:
1.) Download the 5.5.24+dfsg-5 binaries from snapshot.debian.org into a
directory
2.) su
3.) Establish the original context 'dpkg -B -i *.deb'
4.) either 'apt-get install
tag 685072 -moreinfo -unreproducible +confirmed
thanks
I can confirm this now. The steps to reproduce (on a sid machine) are:
1.) Download the 5.5.24+dfsg-5 binaries from snapshot.debian.org into a
directory
2.) su
3.) Establish the original context 'dpkg -B -i *.deb'
4.) either 'apt-get install
tag 685072 +unreproducible +moreinfo
thanks
I have not managed to reproduce this. I have tried piuparts in three
ways and a direct -6 to -7 upgrade. I have not had time to do a -5 to -7
upgrade as I did not have the -5 debs lying around.
I probably won't have time for a day or two to get them fro
tag 685072 +unreproducible +moreinfo
thanks
I have not managed to reproduce this. I have tried piuparts in three
ways and a direct -6 to -7 upgrade. I have not had time to do a -5 to -7
upgrade as I did not have the -5 debs lying around.
I probably won't have time for a day or two to get them fro
severity 685072 grave
thanks
fair enough. I put quite a lot of effort into working out how to run
piuparts with mysql, and to automating it. However all that effort was
going into the post wheezy release. I didn't think to apply it to the
recent releases because we were only making small changes,
severity 675005 important
thanks
I don't see why this situation is any different from the maintainer
being MIA. He did not reply to an earlier email so from my point of view
he is. Hence I am downgrading the bug report.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a
severity 675005 important
thanks
I don't see why this situation is any different from the maintainer
being MIA. He did not reply to an earlier email so from my point of view
he is. Hence I am downgrading the bug report.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Package: xshisen
Version: 1:1.51-4
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
I am looking at RC bugs in Debian during the freeze.
I did contact the maintainer earlier but got no reply.
I have no long t
-testsuite-5.5 mysql-source-5.5
Architecture: amd64
Version: 5.5.24+dfsg-7
Distribution: sid
Urgency: low
Maintainer: amd64 Builddd Daemon (barber)
Changed-By: Nicholas Bamber
Description:
libmysqlclient-dev - MySQL database development files
libmysqlclient18 - MySQL database client library
ranslation (Closes: #683733)
+ * Use xz compression for binary packages (Closes: #684146)
+
+ -- Nicholas Bamber Sat, 11 Aug 2012 21:02:27 +0100
+
mysql-5.5 (5.5.24+dfsg-6) unstable; urgency=low
* Updated Czech debconf translation (Closes: #681711)
diff -Nru mysql-5.5-5.5.24+dfsg/debian/po/tr.po
ranslation (Closes: #683733)
+ * Use xz compression for binary packages (Closes: #684146)
+
+ -- Nicholas Bamber Sat, 11 Aug 2012 21:02:27 +0100
+
mysql-5.5 (5.5.24+dfsg-6) unstable; urgency=low
* Updated Czech debconf translation (Closes: #681711)
diff -Nru mysql-5.5-5.5.24+dfsg/debian/po/tr.po
-testsuite-5.5 mysql-source-5.5
Architecture: source all i386
Version: 5.5.24+dfsg-7
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers
Changed-By: Nicholas Bamber
Description:
libmysqlclient-dev - MySQL database development files
libmysqlclient18 - MySQL database client library
tag 684566 +pending
thanks
This has been checked into the git repository. I won't put it into
5.5.24+dfsg-7 but it might still manage to get into wheezy in a later
upload.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
On 10/08/12 09:23, Ansgar Burchardt wrote:
> On 08/08/2012 10:43 PM, Nicholas Bamber wrote:
>> I have not finished testing your patch but I have a few questions.
>>
>> Firstly it raises a new lintian error requiring a Pre-Depends on dpkg
>> (=> 1.15.6~).
On 10/08/12 09:23, Ansgar Burchardt wrote:
> On 08/08/2012 10:43 PM, Nicholas Bamber wrote:
>> I have not finished testing your patch but I have a few questions.
>>
>> Firstly it raises a new lintian error requiring a Pre-Depends on dpkg
>> (=> 1.15.6~).
Ansgar,
I have not finished testing your patch but I have a few questions.
Firstly it raises a new lintian error requiring a Pre-Depends on dpkg
(=> 1.15.6~). I know that this is more of an issue for Ubuntu and that
Ubuntu won't in this case be syncing from wheezy, so I guess we ca
Ansgar,
I have not finished testing your patch but I have a few questions.
Firstly it raises a new lintian error requiring a Pre-Depends on dpkg
(=> 1.15.6~). I know that this is more of an issue for Ubuntu and that
Ubuntu won't in this case be syncing from wheezy, so I guess we ca
Ansgar,
I have not finished testing your patch but I have a few questions.
Firstly it raises a new lintian error requiring a Pre-Depends on dpkg
(=> 1.15.6~). I know that this is more of an issue for Ubuntu and that
Ubuntu won't in this case be syncing from wheezy, so I guess we ca
Ansgar,
I have not finished testing your patch but I have a few questions.
Firstly it raises a new lintian error requiring a Pre-Depends on dpkg
(=> 1.15.6~). I know that this is more of an issue for Ubuntu and that
Ubuntu won't in this case be syncing from wheezy, so I guess we ca
Lisandro,
Thansk very much for closing the bug yourself. ;-)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 06/08/12 22:54, Steven Ayre wrote:
> Please run the following command on your system as root:
> date -s "`date`"
>
> A few weeks ago there was a leap second, which triggered a bug in a
> timer in the Linux kernel, the effect of which is that programs using
> the affected timer experience very h
ranslation (Closes: #681711)
+
+ -- Nicholas Bamber Sun, 29 Jul 2012 13:04:46 +0100
+
mysql-5.5 (5.5.24+dfsg-5) unstable; urgency=medium
* Spanish debconf translation (Closes: #679053)
diff -Nru mysql-5.5-5.5.24+dfsg/debian/po/cs.po mysql-5.5-5.5.24+dfsg/debian/po/cs.po
--- mysql-5.5-5.5.24+dfsg
ranslation (Closes: #681711)
+
+ -- Nicholas Bamber Sun, 29 Jul 2012 13:04:46 +0100
+
mysql-5.5 (5.5.24+dfsg-5) unstable; urgency=medium
* Spanish debconf translation (Closes: #679053)
diff -Nru mysql-5.5-5.5.24+dfsg/debian/po/cs.po mysql-5.5-5.5.24+dfsg/debian/po/cs.po
--- mysql-5.5-5.5.24+dfsg
-testsuite-5.5 mysql-source-5.5
Architecture: source all i386
Version: 5.5.24+dfsg-6
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers
Changed-By: Nicholas Bamber
Description:
libmysqlclient-dev - MySQL database development files
libmysqlclient18 - MySQL database client library
Package: wnpp
Severity: wishlist
Owner: Nicholas Bamber
* Package name: mysqlreport
Version : 3.5
Upstream Author : Daniel Nichter
* URL : http://hackmysql.com/mysqlreport
* License : GPL
Programming Lang: Perl
Description : friendly report of
Package: wnpp
Severity: wishlist
Owner: Nicholas Bamber
* Package name: mysqlreport
Version : 3.5
Upstream Author : Daniel Nichter
* URL : http://hackmysql.com/mysqlreport
* License : GPL
Programming Lang: Perl
Description : friendly report of
Package: wnpp
Severity: wishlist
Owner: Nicholas Bamber
* Package name: mysqlreport
Version : 3.5
Upstream Author : Daniel Nichter
* URL : http://hackmysql.com/mysqlreport
* License : GPL
Programming Lang: Perl
Description : friendly report of
On 23/07/12 18:39, Clint Byrum wrote:
>>
>> 3.) The output of "licensecheck --copyright --recursive *' is not
>> actually enough. We need to find every executable file with a shebang as
>> the first line and check that individually. Again this would be more
>> easily fixed in licensecheck, but.
owner 597861 nicho...@periapt.co.uk
thanks
I have a plan for this.
1.) A new script built on top of licensecheck that will compare the
output of licensecheck with debian/copyight. Ideally this should all be
factored back into licensecheck itself but the devscripts package seems
to move very slowl
On 23/07/12 14:47, Antti-Juhani Kaijanaho wrote:
>> If you still have the old innodb files, I believe there are some tools
>> for reading them which might be interesting.
>
> Yes, I have the tarball I made before recovering. I have also set up a wheezy
> VM in the broken state
I was thinking of
tag 660087 +pending
tag 660164 +pending
thanks
This is checked in the new git repository:
http://anonscm.debian.org/gitweb/?p=pkg-mysql/packages/mysql.git;a=summary.
and
http://anonscm.debian.org/gitweb/?p=pkg-mysql/packages/innotop.git;a=summary.
--
To UNSUBSCRIBE, email to debian-wnpp-requ.
tag 660087 +pending
tag 660164 +pending
thanks
This is checked in the new git repository:
http://anonscm.debian.org/gitweb/?p=pkg-mysql/packages/mysql.git;a=summary.
and
http://anonscm.debian.org/gitweb/?p=pkg-mysql/packages/innotop.git;a=summary.
--
To UNSUBSCRIBE, email to debian-bugs-dist-
severity 682232 important
thanks
Antti-Juhani,
Thanks for your cooperation.
Since you have managed to recover I feel fully justified in downgrading
to important. The information you have sent from the logs is very good,
but so far no different from any other innodb corruption.
severity 682232 important
thanks
Antti-Juhani,
Thanks for your cooperation.
Since you have managed to recover I feel fully justified in downgrading
to important. The information you have sent from the logs is very good,
but so far no different from any other innodb corruption.
Moritz,
Do you still see any reason to keep this bug report open?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Moritz,
Do you still see any reason to keep this bug report open?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
tag 317934 +pending
tag 511438 +pending
thanks
This is checked in the new git repository:
http://anonscm.debian.org/gitweb/?p=pkg-mysql/packages/mysql.git;a=summary.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas..
Package: mysql-5.5
Severity: normal
Dear Maintainer,
Firstly the file debian/copyright does not contain any copyright attributions
for teh debian/* files
which could be deduced from the debian/changelog as the Debian Perl Group does.
Secondly the file debian/additions/mysqlreport has some speci
>
> -- Configuration Files:
> /etc/logcheck/ignore.d.paranoid/mysql-server-5_5 [Errno 13] Permission
> denied: u'/etc/logcheck/ignore.d.paranoid/mysql-server-5_5'
> /etc/logcheck/ignore.d.server/mysql-server-5_5 [Errno 13] Permission denied:
> u'/etc/logcheck/ignore.d.server/mysql-server-5_5'
>
>
> -- Configuration Files:
> /etc/logcheck/ignore.d.paranoid/mysql-server-5_5 [Errno 13] Permission
> denied: u'/etc/logcheck/ignore.d.paranoid/mysql-server-5_5'
> /etc/logcheck/ignore.d.server/mysql-server-5_5 [Errno 13] Permission denied:
> u'/etc/logcheck/ignore.d.server/mysql-server-5_5'
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 13 Jul 2012 23:02:23 +0100
Source: brewtarget
Binary: brewtarget
Architecture: source i386
Version: 1.2.4+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Philip G. Lee
Changed-By: Nicholas Bamber
Description
Package: lintian
Version: 2.5.8
Severity: wishlist
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
The Debian MySQL team has decided to move to an unversioned source package:
"mysql".
I guess the simplest thing is simply to
Package: lintian
Version: 2.5.8
Severity: wishlist
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
The Debian MySQL team has decided to move to an unversioned source package:
"mysql".
I guess the simplest thing is simply to
tag 664639 -pending
thanks
As discussed in
http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2012-July/005096.html
I have backed out the main bit of this change in the new git repository.
This is what will get uploaded to experimental next. The logrotate
change is retained.
--
To UNSUBSC
On 16/07/12 11:26, Bjoern Boschman wrote:
> Hi Nicholas,
>
> the basic problem can be reproduced as follows:
>
> configure error logging:
>
> [mysqld]
> log-error = /var/log/mysql/error.log
>
> and restart mysql-server
>
> chown root /var/log/mysql/error.log
> mysqladmin --defaults-file=/etc/m
On 14/07/12 21:00, Cyril Brulebois wrote:
> Nicholas Bamber (14/07/2012):
>> The Spanish translation has been uploaded. The diff is attached.
>> Please could we have a freeze exception for this.
>
>> diff -Nru mysql-5.5-5.5.24+dfsg/debian/changelog
>> mysql-5.
On 14/07/12 21:00, Cyril Brulebois wrote:
> Nicholas Bamber (14/07/2012):
>> The Spanish translation has been uploaded. The diff is attached.
>> Please could we have a freeze exception for this.
>
>> diff -Nru mysql-5.5-5.5.24+dfsg/debian/changelog
>> mysql-5.
On 14/07/12 02:17, Cyril Brulebois wrote:
> Nicholas Bamber (13/07/2012):
>> This vesion is not ready yet. So far it just consists of a
>> single Spanish debconf translation (#679053). I am holding off
>> uploading in case something else turns up. Christian Perrier
>>
On 14/07/12 02:17, Cyril Brulebois wrote:
> Nicholas Bamber (13/07/2012):
>> This vesion is not ready yet. So far it just consists of a
>> single Spanish debconf translation (#679053). I am holding off
>> uploading in case something else turns up. Christian Perrier
>>
-testsuite-5.5 mysql-source-5.5
Architecture: source all i386
Version: 5.5.24+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Nicholas Bamber
Description:
libmysqlclient-dev - MySQL database development files
libmysqlclient18 - MySQL database client
h (it will be completely ready in another
> hour), or should I let you take care of it?
>
> On Sat, Jul 14, 2012 at 10:00 AM, Nicholas Bamber
> mailto:nicho...@periapt.co.uk>> wrote:
>
> Phillip,
> I only just realized you have picked it up again. Sorry.
h (it will be completely ready in another
> hour), or should I let you take care of it?
>
> On Sat, Jul 14, 2012 at 10:00 AM, Nicholas Bamber
> mailto:nicho...@periapt.co.uk>> wrote:
>
> Phillip,
> I only just realized you have picked it up again. Sorry.
h (it will be completely ready in another
> hour), or should I let you take care of it?
>
> On Sat, Jul 14, 2012 at 10:00 AM, Nicholas Bamber
> mailto:nicho...@periapt.co.uk>> wrote:
>
> Phillip,
> I only just realized you have picked it up again. Sorry.
to bring the NMU forward as fast as possible and hopefully the
release team would accept it in wheezy. That way you have more time to
make the next release and you can throw away or incorporate my changes
as you wish.
On 14/07/12 08:41, Nicholas Bamber wrote:
> Phillip,
> If the cop
to bring the NMU forward as fast as possible and hopefully the
release team would accept it in wheezy. That way you have more time to
make the next release and you can throw away or incorporate my changes
as you wish.
On 14/07/12 08:41, Nicholas Bamber wrote:
> Phillip,
> If the cop
to bring the NMU forward as fast as possible and hopefully the
release team would accept it in wheezy. That way you have more time to
make the next release and you can throw away or incorporate my changes
as you wish.
On 14/07/12 08:41, Nicholas Bamber wrote:
> Phillip,
> If the cop
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
This vesion is not ready yet. So far it just consists of a single Spanish
debconf translation (#679053).
I am holding off uploading in case something else turns up. Christian Perri
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package brewtarget
An NMU for #679437 is in preparation. It turns out that the problematic images
are easily replaced.
I'll attach a debdiff a soon as the NMU is up
On 11/07/12 23:56, Nicholas Bamber wrote:
> On 11/07/12 21:31, Nicholas Bamber wrote:
>> On 11/07/12 20:45, Julien Cristau wrote:
>>> On Tue, Jun 5, 2012 at 09:29:55 +0100, Nicholas Bamber wrote:
>>>
>>>> There was a mistake in the slibs for mysql 5.5.24+d
I've raised #627174 to request this package's removal.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I've raised #627174 to request this package's removal.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: release.debian.org
Severity: wishlist
The Debian/upstream maintainer says:
"SD has fallen from my priorities, and to have it be worth keeping in
Debian at this point, I think someone else will need to step up and work
on maintenance upstream."
I've asked in #debian-perl but noone has ex
Package: release.debian.org
Severity: wishlist
The Debian/upstream maintainer says:
"SD has fallen from my priorities, and to have it be worth keeping in
Debian at this point, I think someone else will need to step up and work
on maintenance upstream."
I've asked in #debian-perl but noone has ex
On 11/07/12 21:31, Nicholas Bamber wrote:
> On 11/07/12 20:45, Julien Cristau wrote:
>> On Tue, Jun 5, 2012 at 09:29:55 +0100, Nicholas Bamber wrote:
>>
>>> There was a mistake in the slibs for mysql 5.5.24+dfsg-1 and
>>> asteisk built against it. Once 5.5.24
On 11/07/12 20:45, Julien Cristau wrote:
> On Tue, Jun 5, 2012 at 09:29:55 +0100, Nicholas Bamber wrote:
>
>> There was a mistake in the slibs for mysql 5.5.24+dfsg-1 and
>> asteisk built against it. Once 5.5.24+dfsg-2 has finished
>> building asterisk should be built
Bjorn,
I am afraid I really do not clearly understand what is really going on
with your issue. I cannot reproduce it and reading your reports more
carefully I see that you do not get it on all machines. So I wonder if
the root cause may have been some admin action as root on the affected
bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 665296 debhelper
thanks
On 09/07/12 01:41, Cyril Brulebois wrote:
> Nicholas Bamber (03/07/2012):
>> This is one I raised and people are asking me to upgrade the w3c
>> stuff which requires fixing it. It probably just requi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 665296 debhelper
thanks
On 09/07/12 01:41, Cyril Brulebois wrote:
> Nicholas Bamber (03/07/2012):
>> This is one I raised and people are asking me to upgrade the w3c
>> stuff which requires fixing it. It probably just requi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 665296 debhelper
thanks
On 09/07/12 01:41, Cyril Brulebois wrote:
> Nicholas Bamber (03/07/2012):
>> This is one I raised and people are asking me to upgrade the w3c
>> stuff which requires fixing it. It probably just requi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/12 01:44, Cyril Brulebois wrote:
> Hello,
>
> Nicholas Bamber (03/07/2012):
>> I cannot reproduce the crash but there is a patch if someone
>> can. Else can this bug be downgraded to important.
>>
>> I w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/12 01:44, Cyril Brulebois wrote:
> Hello,
>
> Nicholas Bamber (03/07/2012):
>> I cannot reproduce the crash but there is a patch if someone
>> can. Else can this bug be downgraded to important.
>>
>> I w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/12 01:44, Cyril Brulebois wrote:
> Hello,
>
> Nicholas Bamber (03/07/2012):
>> I cannot reproduce the crash but there is a patch if someone
>> can. Else can this bug be downgraded to important.
>>
>> I w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 08 Jul 2012 18:40:50 +0100
Source: crashme
Binary: crashme
Architecture: source i386
Version: 2.4-11
Distribution: unstable
Urgency: low
Maintainer: Nicholas Bamber
Changed-By: Nicholas Bamber
Description:
crashme
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 08 Jul 2012 14:44:56 +0100
Source: crashme
Binary: crashme
Architecture: source i386
Version: 2.4-10
Distribution: unstable
Urgency: low
Maintainer: Nicholas Bamber
Changed-By: Nicholas Bamber
Description:
crashme
retitle 677765 ITP: crashme -- Stress tests operating system stability
owner 677765 nicho...@periapt.co.uk
thanks
There is actually a new upstream an a new version, 2.6. Still looks
somewhat inactive though. http://crashme.codeplex.com/
--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.deb
retitle 677765 ITP: crashme -- Stress tests operating system stability
owner 677765 nicho...@periapt.co.uk
thanks
There is actually a new upstream an a new version, 2.6. Still looks
somewhat inactive though. http://crashme.codeplex.com/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@list
tag 630625 -pending +confirmed +upstream
thanks
Linking against openssl is not on the cards. yaSSL is considering
addressing this issue as per
http://www.yassl.com/forums/topic70-certificate-chain-verification.html.
To what extent this will flow down to MySQL is of course an open question.
--
Bjoern,
Can I just check that all the Host values in your mysql.user table are
IP addresses or localhost. I wonder if this also precludes '%'. Of
course it could raise the question of what the option actually does.
" --skip-name-resolve
Do not resolve host names when checking client conne
forwarded 664846 http://bugs.mysql.com/bug.php?id=64885
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
forwarded 568498 http://bugs.mysql.com/bug.php?id=44278
tag 535493 +wontfix
thanks
This doesn't appear to be Ubuntu any more and does not strike me as
especially compelling. I'm marking it as wontfix for now.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
Brian,
I tried to reproduce this but failed. Could you send an strace or core
dump?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Brian,
I tried to reproduce this but failed. Could you send an strace or core
dump?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
tags 679350 +moreinfo +unreproducible
thanks
I cannot reproduce the crash but there is a patch if someone can. Else
can this bug be downgraded to important.
I was thinking of raising an NMU but I'm not sure if I feel comfortable
for just one bug.
And of course I have copied the maintainer.
-
tags 679350 +moreinfo +unreproducible
thanks
I cannot reproduce the crash but there is a patch if someone can. Else
can this bug be downgraded to important.
I was thinking of raising an NMU but I'm not sure if I feel comfortable
for just one bug.
And of course I have copied the maintainer.
-
tags 679350 +moreinfo +unreproducible
thanks
I cannot reproduce the crash but there is a patch if someone can. Else
can this bug be downgraded to important.
I was thinking of raising an NMU but I'm not sure if I feel comfortable
for just one bug.
And of course I have copied the maintainer.
--
Zak,
I see you have three RC bugs and at least one upload prepared. Would
you like my sponsorship for the three RC bugs?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Zak,
I see you have three RC bugs and at least one upload prepared. Would
you like my sponsorship for the three RC bugs?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
The broken packages have been removed from arm* testing.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
The broken packages have been removed from arm* testing.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Peter,
So yes the file is distributable. Can we close the bug then?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Peter,
So yes the file is distributable. Can we close the bug then?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
The broken packages have been removed from arm* testing.
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ff3489b.7040...@periapt.co.uk
This is one I raised and people are asking me to upgrade the w3c stuff
which requires fixing it. It probably just requires a slight application
of xargs, but the XML world in Debian is pretty dead and quite a lot is
going on already and XML is not my top focus. So altogether I would
rather look at
501 - 600 of 2256 matches
Mail list logo