** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2012-1012
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2012-1014
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2012-1015
--
You received this bug notification because you are a member
The root cause was in fact the lvm.conf filter, but explicitly not for
the reason you'd think.
The issue is that if I added a|.*| into regex array, it was ignoring
my 'sd[b-z]', loop and ram exclusions, both singly and in combination.
It seems to be an obscure issue with the use of square
On my server, the incorrect setting causes Postfix to fail to start.
Ubuntu 12.04
mail-stack-delivery 1:2.0.19-0ubuntu1
amavisd-new-postfix 1:2.6.5-0ubuntu3.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
Output from before and after commands is attached.
I'm pretty sure you're right about the LVM device filter; I figured that
setting the scsi-timeout to 90 seconds (being way longer than the TUR
path checker, which is scheduled every 20 seconds) should be enough to
handle the device failover.
It looks like all the /dev/mapper/mpathX targets, and the remaining 'sd'
unique paths (with one fabric disabled) were all readable after the path
shutdown, but the underlying LVs were somehow still deactivated when the
paths disappeared.
root@hostname-03:/srv/mysql# dmesg
snip
[1039812.298161]
This is a low priority issue due to the required privileges needed to
exploit it.
** Changed in: krb5 (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
To date, the issue hasn't been observed on the two physical hosts we
have running 10.04.1 LTS with the same multipath-tools version, which
certainly raises a flag.
They are being used as mission critical / production database servers so
I'm scheduling a window in which we will be able to confirm
** Attachment removed: strace_mpathd.log
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218020/+files/strace_mpathd.log
** Attachment added: strace_mpathd.log
-- lvm.conf blacklist should be fine, searches /dev but filters all
/dev/sd.*
I'll attach those files momentarily.
I didn't see any kpartx processes running at all; there wasn't anything
in an uninterruptable sleep state ('D') either.
Listing all kernel and some additional processes here
Storage devices:
$ sudo lsscsi
[0:0:0:0]cd/dvd TSSTcorp CDDVDW TS-L633F IT03 /dev/sr0
[4:2:0:0]diskIBM ServeRAID M5015 2.12 /dev/sda
[5:0:0:0]diskHITACHI OPEN-V 6008 /dev/sdb
[5:0:0:1]diskHITACHI OPEN-V 6008 /dev/sdc
[5:0:0:2]disk
I note this segfault has appeared in dmesg on the last couple of boots.
[ 304.214560] multipathd[3083]: segfault at a ip 7f5eb838798a sp
7fffb225ebb0 error 4 in libc-2.11.1.so[7f5eb831+17a000]
After adjusting the blacklist, updating initrd and rebooting, the same
behaviour is
** Attachment added: strace_mpathd_110712.log
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3219323/+files/strace_mpathd_110712.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Attachment added: multipathd_stdout_110712.log
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3219324/+files/multipathd_stdout_110712.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Hi Peter,
Thanks for picking this up.
Note: I ran an 'update-initramfs -u -k all' and rebooted just for good
measure before proceeding. There's some output regarding a missing
firmware file, I'm not sure it's relevant:
root@rgrprod-pmdh-proc-03:/etc# update-initramfs -u -k all
note: multipath_stderr.log exists, but is empty.
** Attachment added: multipathd_stdout.log
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218021/+files/multipathd_stdout.log
--
You received this bug notification because you are a member of Ubuntu
Server
user@hostname:~$ sudo dmsetup table
mpath2: 0 8388608 multipath 1 queue_if_no_path 0 1 1 round-robin 0 4 1 8:48
1000 8:96 1000 8:144 1000 8:192 1000
mpath1: 0 8388608 multipath 1 queue_if_no_path 0 1 1 round-robin 0 4 1 8:128
1000 8:32 1000 8:80 1000 8:176 1000
mpath0: 0 1048576000 multipath 1
** Attachment added: multipath.conf
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218022/+files/multipath.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
** Attachment added: lvm.conf
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1020436/+attachment/3218023/+files/lvm.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
note: /dev/sda is a raid volume used for the root vg; the filter is
actually r|/dev/sd[b-z]|
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1020436
Title:
Cannot read
** Summary changed:
- Multiple filesystems cannot read superblock after fibre path failover
+ Cannot read superblock after fibre path failover
** Summary changed:
- Cannot read superblock after fibre path failover
+ Cannot read superblock after FC multipath failover
--
You received this bug
Public bug reported:
This might not be multipath-tools, but it's the likeliest candidate.
If fibre channel connectivity is disrupted on an active path, I can see
the multipath daemon rejuggling active paths as expected. However
instead of utilising a new path, the server continues trying active
** Description changed:
This might not be multipath-tools, but it's the likeliest candidate.
If fibre channel connectivity is disrupted on an active path, I can see
the multipath daemon rejuggling active paths as expected. However
instead of utilising a new path, the server continues
I have serious misgivings about the particular approach taken here, in
SRU or otherwise. Why does mod-security.load need to hard-code
libxml2.so.2 *at all*? Isn't that why DSOs are dynamically linked to
their dependent libraries (which mod_security2.so is)? And why is
libxml2.so.2 being
I think there are the following possible valid end states that we want
to get to at the end of the postinst:
- we're not in a chroot. /dev/shm is bind mounted to /run/shm, with the
reboot script handling the fix-up to make /dev/shm a symlink to /run/shm before
next boot.
- we're in a chroot
If it does make sense, the implementation that follows is:
if mountpoint -q /dev mountpoint -q /dev/shm; then
compat_link /dev/shm /run/shm
else
[ -d /run/shm ] || mkdir -p /run/shm
mountpoint -q /dev/ || compat_link /run/shm /dev/shm
fi
BTW, I realize there's another possible scenario,
Chuck, please put SRU information in the bug description, not in a
comment - it becomes hard to find this information when there are a
dozen more comments from testers.
** Description changed:
+ ** Issue **
+
There is an issue with the way nova uses dnsmasq in VLAN mode. It starts
up a
Please also complete the test case with explicit information about how
users can verify the *fix* for this bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1006898
Title:
[SRU]
I'm afraid I also don't understand this problem statement:
There is an issue with the way nova uses dnsmasq in VLAN mode. It starts
up a single copy of dnsmasq for each vlan on the network host (or on
every host in multi_host mode). The problem is in the way that dnsmasq
binds to an ip
... and now I've reviewed the debdiff, and found it to not match the
upstream commit. This part of the patch to src/network.c is missing:
@@ -254,6 +261,7 @@ static int iface_allowed(struct irec **irecp, int if_index,
iface-addr = *addr;
iface-netmask = netmask;
Before the SRU team will reconsider an SRU for this, based on the above
I would also expect to see a regression test plan that accounts for
making sure dnsmasq continues to work correctly in configurations other
than the openstack one.
--
You received this bug notification because you are a
Hello Chuck, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Armando, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Pádraig, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Dan, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback will
Hello Renuka, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Eoghan, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Alvaro, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Joe, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback will
Hello Mandar, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Cor, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback will
Hello Mandar, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Peng, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello MotoKen, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Dan, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback will
Hello Brian, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Eric, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello justinsb, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Alvaro, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback
Hello Dan, or anyone else affected,
Accepted nova into precise-proposed. The package will build now and be
available in a few hours. Please help us by testing this new package.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Your feedback will
This is not a bug in the krb5 package; since you mention this happened
due to a power loss during upgrade, you will need to fix up the state of
the packaging system by hand.
This command will probably fix things up:
sudo apt-get install libgssapi-krb5-2:i386 libgssapi-krb5-2
** Changed in:
The parameter --capture-output lets glance-control fail on some distributions
(eg openSUSE) that do not have a /usr/bin/logger (but rather /bin/logger).
There is no point in opening a bug against the Ubuntu package for an
issue that has no impact in Ubuntu. That is not the intent of the SRU
This was fixed in version 2.4.25-4 of the openldap package in Debian, so
in Ubuntu is fixed for 12.04 and later.
** Changed in: openldap (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
*** This bug is a duplicate of bug 990742 ***
https://bugs.launchpad.net/bugs/990742
** This bug has been marked a duplicate of bug 990742
[SRU] slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 921489 ***
https://bugs.launchpad.net/bugs/921489
** This bug has been marked a duplicate of bug 921489
Segmentation fault in slapd (related to GSSAPI?)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Tags added: verification-done-lucid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/423252
Title:
NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2
** Changed in: nova (Ubuntu Oneiric)
Status: New = In Progress
** Changed in: nova (Ubuntu Precise)
Status: New = In Progress
** Changed in: nova (Ubuntu Oneiric)
Assignee: (unassigned) = Steve Beattie (sbeattie)
** Changed in: nova (Ubuntu Precise)
Assignee: (unassigned
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1010514
Title:
Source group based security group rule without
On Tue, Jun 05, 2012 at 02:25:02PM -, vagk wrote:
I changed the interfaces file to get static ip and retried.
This should not matter because dhclient doesn't return control to ifupdown
until it successfully acquires an IP.
It failed but for a different reason.
My /etc/yp.conf has no
On Tue, Jun 05, 2012 at 12:33:14PM -, alex wrote:
If I try to start ypbind:
# start ypbind
start: Job is already running: ypbind
When this happens, it may be useful to grab the output of 'status ypbind' as
well.
But regardless, your log shows the same hostname lookup failure, so we'll
Ok, here's the problem:
Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.910762] init: portmap main
process (524) became new process (527)
Jun 5 22:24:04 intwinxpubuntu6 kernel: [8.921625] init: portmap state
changed from spawned to post-start
Jun 5 22:24:04 intwinxpubuntu6 kernel: [
krb5-user : Depends: libkrb5-3 (= 1.10+dfsg~beta1-2) but
1.10+dfsg~beta1-2ubuntu0.1 is to be installed
You have a version of libkrb5-3 from precise-proposed installed, but the
precise-proposed repository is not enabled on your system. You need to
either enable precise-proposed and install the
I believe the right place to export ON_BOOT=y is part of the /etc/init
/portmap-wait.conf job. You should be able to confirm this locally by
changing this line:
start portmap || true
to:
start portmap ON_BOOT=y || true
I'll prepare an upload to fix this.
** Package changed: nis (Ubuntu)
On Mon, Jun 04, 2012 at 02:43:32PM -, vagk wrote:
I inserted
exec /var/log/nis-debug.log 21
in /etc/init/ypbind.conf after script line
That really shouldn't be necessary. You should be able to read the log
files from /var/log/upstart, without modifying the upstart job.
alex, do you
hi alex,
It would also be helpful to see the output of this command as root:
initctl list | grep yp
and to have the contents of /etc/default/nis attached.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu)
Importance: Undecided = Medium
** Changed in: upstart (Ubuntu)
Status: New = Triaged
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
**
** Changed in: upstart (Ubuntu Natty)
Status: New = Won't Fix
** Changed in: upstart (Ubuntu Oneiric)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
** Changed in: upstart (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: upstart (Ubuntu Precise)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
Unsubscribing motu-sru, which is no longer an active team. Please
follow the SRU process described at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mcollective in Ubuntu.
** No longer affects: resolvconf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/993794
Title:
Precise can't connect to a network guarded by an authentication
webserver
not committed until it's available in -proposed
** Changed in: libgcrypt11 (Ubuntu Lucid)
Status: Fix Committed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
Jeremy, any word on testing this nis SRU?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
To manage notifications about this bug
Hi there - we're affected by this bug in Lucid LTS (server) - is there
any chance of an SRU for 10.04? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/598385
Title:
[SRU]
I've confirmed this fix here. Prior to upgrade,
/var/log/upstart/resolvconf.log showed this error. After upgrade, the
error is no longer happening.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
(the error was reproducible for me because /usr is on a separate
partition)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/980682
Title:
postconf can't open main.cf with the result
This was fixed in oneiric with the introduction of openssl 1.0.0. On
precise:
$ openssl ciphers CAMELLIA
DHE-RSA-CAMELLIA256-SHA:DHE-DSS-CAMELLIA256-SHA:ADH-CAMELLIA256-SHA:CAMELLIA256-SHA:DHE-RSA-CAMELLIA128-SHA:DHE-DSS-CAMELLIA128-SHA:ADH-CAMELLIA128-SHA:CAMELLIA128-SHA
Marking this bug report
** Summary changed:
- Bind is not configured correctly on upgrade
+ Bind is not configured correctly on upgrade (resolvconf integration)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Not sure why this was assigned to mountall; mountall only parses
/etc/fstab at boot time, it certainly isn't going to be responsible for
writing to it. Reassigning to nautilus, which I guess is what would
have to provide an option to convert gvfs mounts into boot-time mounts
by adding them to the
I can confirm Serge's analysis here. I'm surprised that this hasn't
bitten us more severely before now, given that I see all my compat
symlinks are wrong in my (iteratively upgraded) precise chroots here;
apparently things really don't care so much about the compat these days.
We should
I just wanted to comment that I find it troubling that this bug is closed and
has low urgency. I am not a developer, just a user.
My company runs a small computer lab for our clients, it is used by 150+ users.
It uses NIS for it's logins and NFS for the user's home directories. Any time
I believe upstream attempted to address this in
https://github.com/cobbler/cobbler/commit/6d9167e5da44eca56bdf42b5776097a6779aaadf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/996088
Title:
Bind is not configured correctly on upgrade
To manage notifications about this bug go to:
** Description changed:
On an upgrade to Precise, bind was not correctly reconfigured, resulting
in a failure to resolve domain names.
- Solution was to reconfigure the bind9 package,
+ Solution was to dpkg-reconfigure the bind9 package, and turn off
+ resolvconf integration which was left
LaMont, this is related to bug #933723; we've turned resolvconf
integration off by default, but in the upgrade case it's still on, which
causes problems now that resolvconf is installed by default. Could we
include a one-time upgrade check when upgrading to the version in 12.04
that checks
But how was this inconsistancy possible?
Any idea, what I did wrong?
I don't think this is due to anything you did wrong; most likely, there
was simply a single-bit memory or disk error that broke the checksum of
your conffile.
Could I found this solution by myself?
Not easily, and for that
I can't reproduce this problem here.
Please show the output of the following command on your system:
dpkg-query -f='${PackageSpec}\t${Version}\n${Conffiles}\n' -W
'libldap-2.4-2:*'
** Package changed: ia32-libs (Ubuntu) = openldap (Ubuntu)
** Changed in: openldap (Ubuntu)
Status: New =
On Fri, May 04, 2012 at 07:49:55PM -, Ulli Horlacher wrote:
On Fri 2012-05-04 (19:22), Steve Langasek wrote:
I can't reproduce this problem here.
I can reproduce it on 3 Ubuntu 12.04 systems.
Please show the output of the following command on your system:
dpkg-query -f
On Fri, May 04, 2012 at 09:27:08PM -, Ulli Horlacher wrote:
Can you try running 'sudo apt-get install --reinstall libldap-2.4-2' to see
if that fixes the issue?
root@eduroam1:~# apt-get install --reinstall libldap-2.4-2
Reading package lists... Done
Building dependency tree
Reading
I don't think this analysis is correct. At the time the umountfs script
finishes, *all* filesystems are supposed to be unmounted. This includes
any mount points watched by autofs. So why is autofs still running at
this point in the shutdown? The autofs daemon should be shut down
*prior* to
That seems far removed from the original issue. What are the contents
of /etc/resolv.conf on your system? Where are your DNS servers being
configured? The /etc/network/interfaces from the original bug report
shows no dynamic or static sources of DNS, so installing resolvconf
(which is required,
** Bug watch added: Debian Bug tracker #988374
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988374
** Also affects: bridge-utils (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988374
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker
** No longer affects: openldap (Ubuntu)
** No longer affects: openldap (Ubuntu Karmic)
** No longer affects: openldap (Ubuntu Lucid)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
On Wed, Apr 25, 2012 at 09:14:58AM -, Howard Chu wrote:
I still don't see any technical merit in supporting anything besides
OpenSSL.
As soon as someone provides an OpenSSL that it's legal for us to link to in
a Linux OS product, instead of with a wink and a nod to the GPL, we'd be
elated
Package has been accepted into precise-proposed and should be copied to
-release before release once it's built. It's a sufficiently trivial
change that there's no reason to defer this to the SRU process.
** Changed in: horizon (Ubuntu)
Status: New = Fix Committed
--
You received this
Setting this back to 'triaged', which is the more-better bug state in
LP.
** Changed in: krb5 (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
facturlinex2 has been removed from precise, so this bug is resolved. If
someone wants to reintroduce the package in a later release, that should
be tracked as a separate issue.
** Changed in: facturlinex2 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification
Jamie, can I ask you to make a first pass at some text for this? I'm
not entirely sure what security groups means in this context.
** Changed in: ubuntu-release-notes/precise
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a
Hi,
Sorry for losing track of the issue.
I was getting corrupted headers where because one header had multiple
NULLs in it, when dovecot wrote the message back, it ended up dropping
that header and merging/corrupting another header. The example I came up
with was where the original message
sense to track these other issues as a separate bug,
rather than continuing to use this single bug report for every problem
related to the symptom of slow unmounts on shutdown.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set
Public bug reported:
The squid (v2) package had all of the hardening options enabled (see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542723) due to squid
receiving and parsing network input and the number of and severity of
prior security issues; however, with the transition to squid3 some
For more details on the hardening options, please see
http://wiki.debian.org/Hardening
Attached is a debdiff for precise-proposed SRU that addresses the issue
as well as fixes the file descriptor limit in bug 986159. I've built and
confirmed both issues locally, as well as performed a modicum of
501 - 600 of 1454 matches
Mail list logo
