** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned) = Canonical Server Team (canonical-server)
--
Logic to determine expected number of running session wrong (regression in
hardy's open-iscsi 2.0.865-1ubuntu3.1)
https://bugs.launchpad.net/bugs/394398
You received this bug
(In the future, please just upload simple patches like that; it's easy
to reject them in the few cases where there aren't appropriate, and in
general having it in the queue already speeds things up)
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received
** Changed in: freeradius (Ubuntu Hardy)
Status: Confirmed = In Progress
** Changed in: freeradius (Ubuntu Hardy)
Assignee: (unassigned) = Thierry Carrez (ttx)
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification
Uploaded.
** Changed in: freeradius (Ubuntu Hardy)
Status: In Progress = Fix Committed
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius
lvm2 package should drop a hook for it's configuration in initramfs.
** Changed in: lvm2 (Ubuntu)
Importance: Undecided = High
** Changed in: lvm2 (Ubuntu)
Status: New = Confirmed
--
initramfs-tools lvm2-hookscript won't include lvm.conf and claim devices it
shouldn't
Please add
mkdir -p ${DESTDIR}/etc/lvm
cp -p /etc/lvm/lvm.conf ${DESTDIR}/etc/lvm/lvm.conf
to the lvm hook. This does no harm and helps a lot with drbd.
I have almost given up with drbd and ubuntu cause of this issue until i
was pointed to this bug entry.
Problem exists in jaunty (9.04) as
I've uploaded a fix for lvm2. I don't think initramfs-tools itself
requires any changes, so I'm marking that task Invalid.
** Changed in: initramfs-tools (Ubuntu)
Status: New = Invalid
--
initramfs-tools lvm2-hookscript won't include lvm.conf and claim devices it
shouldn't
This bug was fixed in the package lvm2 - 2.02.39-0ubuntu11
---
lvm2 (2.02.39-0ubuntu11) karmic; urgency=low
* Copy /etc/lvm/lvm.conf into the initramfs (LP: #246324).
-- Colin Watson cjwat...@ubuntu.com Wed, 15 Jul 2009 13:52:21 +0100
** Changed in: lvm2 (Ubuntu)
This bug was fixed in the package samba - 2:3.4.0-1ubuntu2
---
samba (2:3.4.0-1ubuntu2) karmic; urgency=low
* debian/control: Suggest ufw, (LP: #399468)
-- Chuck Short zul...@ubuntu.com Wed, 15 Jul 2009 10:01:41 -0400
** Changed in: samba (Ubuntu)
Status: Triaged = Fix
I ran slapd with -d any and figured out that the problem is in the
following lines in /etc/ldap/slapd.conf (it seems they were added by
package update script)
overlay syncprov
syncprov-checkpoint 100 10
syncprov-sessionlog 100
Unfortunately, I can't reproduce the exact error message - this slapd
Thank you for assigning this bug to someone. Is there any other info I
should provide?
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2
I cannot reproduce this; I can successfully install and upgrade
libsasl2-2 on intrepid, jaunty, and karmic.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Confirmed = Incomplete
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You received this bug
Kees, what do you use to perform the installation? Here, both APT and
aptitude fail as shown above, during an upgrade. This behavior is
verified on both Debian and Ubuntu, using APT and aptitude.
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You
Public bug reported:
Binary package hint: dovecot-common
/etc/dovecot/dovecot.conf and /usr/share/dovecot/dovecot.conf refer
users to /dev/dovecot/dovecot-postfix.conf instead of /etc/dovecot
/dovecot-postfix.conf.
** Affects: dovecot (Ubuntu)
Importance: Undecided
Status: New
--
Here is my intrepid machine upgrading libsasl2-2:
# lsb_release -d
Description:Ubuntu 8.10
# apt-cache policy libsasl2-2
libsasl2-2:
Installed: 2.1.22.dfsg1-21ubuntu2
Candidate: 2.1.22.dfsg1-21ubuntu2.1
Version table:
2.1.22.dfsg1-21ubuntu2.1 0
500 file:
I did run fsck with the drive mounted. Now installations and uninstallations
do not go smoothly. Pls how can I rectify that?
Arinze
On Thu, Jul 9, 2009 at 3:00 PM, Chuck Short chuck.sh...@canonical.comwrote:
Looking at the logs in this bug reports, it looks like you have some
dpkg database
Steve Beattie offered the following feedback on IRC:
sbeattie re samba; I ran the security team's qa-regression-tests
against it, but that doesn't say much about winbind.
This still leaves some risk of regression, but is better than what we
had; given the alignment with the 8.04.3 point release
This bug was fixed in the package samba - 3.0.28a-1ubuntu4.8
---
samba (3.0.28a-1ubuntu4.8) hardy-proposed; urgency=low
* Added debian/patches/fix-winbindd-crash-dc.patch:
- Fix winbindd crash when calling getent group on domain controller (LP:
#328874)
- upstream commit
I don't know surely, but samba depended on samba-common-bin before this
release and now only recommends
--
samba 3.4.0 depends on ufw
https://bugs.launchpad.net/bugs/399468
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Here is the virtual host config from the procedure documented in:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/394350/comments/15
It is file:
/etc/apache2/sites-available/default
** Attachment added: default
http://launchpadlibrarian.net/29096236/default
--
RLimitCPU has no
When I was testing I had forgotten that there had to be a local disk
present for open-iscsi to get loaded. I retested this morning with a
dummy hard disk in play and the install completed successfully. Thank
you all for your hard work on this one!
--
iSCSI install fails under hardy
What needs to be done to make the open-iscsi-udeb load earlier in the
install sequence so its block devices are available to disk-detect?
Sounds like the initramfs problem is solved.
As for blowing away the networking, one possible solution: if the
installer knows what interface the initiator
22 matches
Mail list logo
