Public bug reported:
dig, as supplied, will not validate a DNSSEC domain.
The +sigchase option should cause validation to occur but it does not.
As noted in http://bryars.eu/2010/08/validating-and-exploring-dnssec-
with-dig/ if a file called 'trusted-key.key' is present then dig will
use that.
** Changed in: urlgrabber (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to urlgrabber in Ubuntu.
https://bugs.launchpad.net/bugs/1200288
Title:
yum error in lxc-create -t fedora
To manage
The attachment 0001-Add-a-named.conf.keys-file-for-storing-various-
keys.patch seems to be a patch. If it isn't, please remove the patch
flag from the attachment, remove the patch tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed
This is filed against Raring. It needs to be checked and confirmed
against the latest releases in Trusty, Utopic, and Vivid. If this bug
is replicated in any of those versions of the nginx package in Ubuntu,
please change the bug status to New and provide details of how you
replicated this.
**
I have marked this as invalid against Vivid. In the latest merges, the
nginx-naxsi flavor and related packaging was removed as a result of
Debian dropping support for the naxsi packaging.
Notes to triagers and people looking to fix the bugs: The nginx-naxsi
package in Trusty and Utopic is
** Also affects: nginx (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: nginx (Ubuntu Precise)
Importance: Undecided = Low
** Changed in: nginx (Ubuntu Precise)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
I have marked this as invalid against Vivid. In the latest merges, the
nginx-naxsi flavor and related packaging was removed as a result of
Debian dropping support for the naxsi packaging.
Notes to triagers and people looking to fix the bugs: The nginx-naxsi
package in Trusty and Utopic is
The Boto S3Connection provides two methods to connect to a S3 bucket;
get_bucket() raises an exception if there is an issue, while lookup()
returns None if there is an error, hiding the cause of problem.
Duplicity uses the lookup() method and then raises this generic
exception (BackendException:
User kamalwanas recently vandalized this bug by changing the status from
confirmed to fix released, but I can't seem to change it back. I was
able to revert the vandalism by abnercontreras11 (change the package
back to initramfs-tools).
** Package changed: cloud-initramfs-tools (Ubuntu) =
Public bug reported:
After upgrade ubuntu version 14.04 to 14.10 i started to get this error
whenever i try install/remove a package
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: php5-cli 5.5.12+dfsg-2ubuntu4.1
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1406809
Title:
package php5-cli 5.5.12+dfsg-2ubuntu4.1 failed to install/upgrade:
subprocess
Public bug reported:
Enter mysql command line client and execute the following:
Drop Database test;
Create Database test;
USE test;
CREATE TABLE mrpatfl (
id int(10) unsigned NOT NULL auto_increment,
account int(10) unsigned default NULL,
PRIMARY KEY (id),
UNIQUE KEY dir1 (account)
)
Having issue with 5.5 when scripting updates to table structures.
In many cases, adding a new column will result in the xxx.ibd file left in
place and three #sqlx files.
And it is too much trouble to go through the innodb recovery process - so I
re-load the database(s).
I will create
13 matches
Mail list logo