On Wed, May 01, 2013 at 12:11:19AM -, Dmitrijs Ledkovs wrote:
To fix stateful re-execution in early boot, we need to serialise all
objects used by upstart which upstream has avoided to do so far. Also
it's questionable if stateful re-execution in early boot is a desired
requirement.
No,
** No longer affects: pam (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/117736
Title:
pam_mount unable to unmount needs root priv
To manage notifications about this bug
Hello Andres, or anyone else affected,
Accepted maas into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/maas/1.2+bzr1373+dfsg-
0ubuntu1~12.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Andres, or anyone else affected,
Accepted maas into quantal-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/maas/1.2+bzr1373+dfsg-
0ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I've reopened this as it still affects Fedora 18
** Changed in: tgt (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1073287
Title:
tgt-admin fails
Sorry, wrong bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1073287
Title:
tgt-admin fails to read configuration
To manage notifications about this bug go to:
Howdy,
I know that in my case, this was definitely an MTU problem, and it
exhibits exactly the behavior stated above.
to test this, call
ping -M do -s 1500 host
If it goes through, this is probably not your issue. If it does not, try
lowering the -s value until it does go through. If the
** Description changed:
[Impact]
As part of the MAAS Next Steps bluepring [1], we would like to SRU a new
version of MAAS to both Precise and Quantal.
For Quantal:
- - Fixes various issues
+ - Fixes various issues
https://launchpad.net/ubuntu/+source/maas/1.2+bzr1349+dfsg-0ubuntu1
Still occurs in Raring Daily release 2013-03-14
Happy pi day
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/1076290
Title:
cobbler-web throws 500 internal server error
To manage
xception, but this bug is linked from the SRU changelog and would
require direct verification. Please either complete the bug description
with a test case for this bug, or re-upload without a reference in the
changelog.
--
You received this bug notification because you are a member of Ubuntu
xception, but this bug is linked from the SRU changelog and would
require direct verification. Please either complete the bug description
with a test case for this bug, or re-upload without a reference in the
changelog.
--
You received this bug notification because you are a member of Ubuntu
The horizon SRU is a provisional micro-release exception, but this bug
is linked from the SRU changelog and would require direct verification.
Please either complete the bug description with a test case for this
bug, or re-upload without a reference in the changelog.
--
You received this bug
Public bug reported:
On a raring system, the dnsmasq instance spawned by libvirt is not
forwarding DNS requests to the upstream resolver. dnsmasq is run as:
/usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
The contents of default.conf are:
##WARNING: THIS IS AN
On Fri, Feb 15, 2013 at 06:35:40PM -, Simon Kelley wrote:
On 15/02/13 18:00, Steve Langasek wrote:
Public bug reported:
On a raring system, the dnsmasq instance spawned by libvirt is not
forwarding DNS requests to the upstream resolver. dnsmasq is run as:
/usr/sbin/dnsmasq --conf
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided = High
** Changed in: dnsmasq (Ubuntu)
Status: New = Triaged
--
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/1126488
Marc, any ETA for getting this fixed dnsmasq into raring?
--
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/1126488
Title:
libvirt instance of dnsmasq in raring fails to forward DNS
'mounted' events are handled synchronously in mountall, and the
'filesystem' isn't emitted until they're all done. Prelim tests seem to
confirm that this is working correctly (and if it wasn't that would be a
very bad bug, that I think we would have caught before now).
In a test instance from
On Tue, Feb 12, 2013 at 04:21:14PM -, Gunnar Hjalmarsson wrote:
On 2013-02-12 05:08, Steve Langasek wrote:
- As of the next upload of pam to raring, .pam_environment will not
be read by default at all by the pam_env module.
Currently that would break the locale environment for everyone
Having reviewed the proposed pam change at
https://code.launchpad.net/~gunnarhj/ubuntu/raring/pam/encrypted-
home/+merge/135021, I believe it's incorrect and that this needs to be
fixed in lightdm instead. Repeating my comment from the merge proposal:
- This is a change in behavior of
This problem also affects /etc/pam.d/atd, /etc/pam.d/sshd, and
/etc/pam.d/sudo in raring.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environment not parsed
Public bug reported:
After upgrade to raring, postfix is failing to update
/var/spool/postfix/etc/resolv.conf on DNS server changes (via
resolvconf). Since postfix invariably starts before network-manager on
my system, this means postfix never knows the DNS server so can't
resolve any
The cause of the failure in /etc/resolvconf/update-libc.d/postfix is
here:
QUEUEDIR=$(/usr/sbin/postconf2 -h queue_directory 2/dev/null || true)
# /usr/sbin/postconf2 -h queue_directory 2/dev/null
# echo $?
127
#
This is because:
# /usr/sbin/postconf2 -h queue_directory
bash:
** Changed in: network-manager (Ubuntu Precise)
Milestone: ubuntu-12.04.2 = ubuntu-12.04.3
--
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/1003842
Title:
dnsmasq sometimes fails
Thanks for confirming. Marking this invalid, then.
** Changed in: postfix (Ubuntu Raring)
Status: New = Invalid
--
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/1118549
Title:
I started using my employer's OpenVPN today and encountered name
resolution problems. From my research, this here bug appears to be
plaguing me, as well (I'm on 12.10). Commenting the line dns=dnsmasq in
/etc/NetworkManager/NetworkManager.conf does fix the problem. However,
_all_ DNS is routed out
As Clint says, this doesn't fit the SRU policy. If the raphael source
is already bundled in the maas source package in precise, we should keep
it this way; I don't see any reason that it's worth splitting this out,
clobbering the existing raphael package in precise, in an SRU when
keeping it in
Hello Mathieu, or anyone else affected,
Accepted dnsmasq into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/dnsmasq/2.59-4ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hi Christophe,
That worked great. Thank you!!
** Changed in: apache2 (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/873042
Title:
With the current mountall in precise, 2.36.3, yes - there shouldn't be
any further need to call 'start networking' directly. Are the symptoms
exactly the same as before the mountall fix?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
On Tue, Dec 25, 2012 at 02:08:37PM -, Borim wrote:
I checked the existence of the network-services event with Ubuntu 12.10
by starting Ubuntu with the debug switch. But I can not find the
network-services event in /var/log/dmesg where all triggered events are
listed.
This probably refers
That's not a bug in upstart. The interface failing to come up may be a
bug in your config, or it may be a bug in the scripts called by ifup.
Please attach the contents of /var/log/upstart/network-interface-
vlan3.log.
** Project changed: upstart = vlan (Ubuntu)
** Changed in: vlan (Ubuntu)
Public bug reported:
The fix that's been applied for bug #974509 checks for the presence of a
redirector by looking of three hostnames, and treating as invalid any
results pointing to a matching address:
- does-not-exist.example.com.
- example.invalid.
- a random, unqualified 32-character
FWIW, this would be more precise if it had a start condition of:
start on runlevel [06]
though it's unlikely that cloud users are going to make much use of
runlevels other than runlevel 2.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
=== Begin SRU Information ===
[Impact]
- * If an image does not have landscape-client installed inside it, and the
-user provided landscape config, then:
-a.) the landscape config file would be written with root:root permissions
-so that the user that
Hello Marti, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Scott, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Thomas, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Scott, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Scott, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Scott, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Chuck, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Andreas, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Scott, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Scott, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
... except that we can't actually call running-in-container reliably
this early in the boot process; /run is not guaranteed to be mounted (or
seen to be mounted) before /dev.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Have talked through this with hallyn in detail.
- we don't want to change MAKEDEV itself to not clobber existing device nodes,
because in other cases this makes recovery from broken /dev less reliable
- we can't side-step this by making /dev not be a mountpoint within the
container because in
** Changed in: mountall (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1075717
Title:
mounted-dev must not re-create consoles in a
qemu-kvm needs to depend on the udev package, to ensure the udev package
is configured first before the qemu-kvm package's maintainer script is
called.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
I think this is a duplicate of a bug that was already fixed in the cloud
images, but I don't remember where that fix happened. Reassigning to
cloud-init.
** Package changed: upstart (Ubuntu) = cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server
Bug in dpkg; fixed in the version of dpkg in raring. SRU needed.
** Bug watch added: Debian Bug tracker #684776
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684776
** Also affects: openldap (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684776
Importance: Unknown
The change that's been uploaded to precise for this is:
diff -u qemu-kvm-1.0+noroms/debian/qemu-kvm.postinst
qemu-kvm-1.0+noroms/debian/qemu-kvm.postinst
--- qemu-kvm-1.0+noroms/debian/qemu-kvm.postinst
+++ qemu-kvm-1.0+noroms/debian/qemu-kvm.postinst
@@ -16,2 +16,15 @@
-exit 0
+# if we just
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
Public bug reported:
Original post about this at: http://askubuntu.com/questions/202029/keep-
getting-smbd-errors-but-apport-asks-questions-i-cant-answer .
When I get smbd crashes on my system, apport tries to handle the
reporting, but starts off by trying to ask questions. I can't
So my proposal incorrect - better add pam_loginuid to ordinary
sessions and leave special sessions untouched.
Yep. This makes it non-trivial to do centrally; needs to be addressed
in the individual services unfortunately.
** Package changed: pam (Ubuntu) = openssh (Ubuntu)
** Also affects:
Tested quota 4.00-3ubuntu1 from precise-proposed. It's correctly
reporting NFS quotas.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quota in Ubuntu.
Public bug reported:
The openssh-client bundled with Ubuntu 12.04 fails to set the IP Type of
Service field to minimize delay (0x04) for interactive SSH sessions. Just
about any other flavor of Linux/UNIX does this without any trouble. Even if I
attempt to force the setting in
If I build openssh from source and try it, the ToS bit is set
appropriately:
2012-10-16 17:32:16.173736 IP (tos 0x10, ttl 64, id 38386, offset 0, flags
[DF], proto TCP (6), length 52)
1.1.1.1.36327 2.2.2.2.22: Flags [.], cksum 0x2dcd (incorrect -
0x8a18), seq 3101, ack 3736, win
will this package fix be added to the cloud repositories for ubuntu 12.04LTS
as well ?
i have exactly this issue on 12.04
--
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/1060336
Title:
Cheers James, thanks for the guidance,
I'd been using novncproxy in essex and did wonder why it seemed to be back in
folsom.
thanks for the clarification -
I can confirm nova-novncproxy installs without issues
thanks again
Steve a
--
You received this bug notification because you
Public bug reported:
I am creating a folsom multi server installation
I use the additopnal folsom cloud archives as described here to install
openstack-folsom on ubuntu server 12.04LTS.
http://docs.openstack.org/trunk/openstack-compute/install/apt/content/assumptions.html
I followed this
Public bug reported:
I am creating a multi server installation of openstack following this
documentation:
http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ch_installing-openstack-overview.html
I have added the required repos to install this on 12.04LTS
Ok, something's behaving very wrong here. apt claims it's going to
upgrade libkrb5-dev, then proceeds to try to configure the current
version whose dependencies aren't satisfied. Bouncing this over to apt.
** Package changed: krb5 (Ubuntu) = apt (Ubuntu)
** Changed in: apt (Ubuntu)
I don't understand the error here. It looks like the package manager is
trying to upgrade the right packages to make things consistent, but then
the dpkg log shows packages being configured out of order. Can you
please run ' sudo apt-get install -f' in a terminal, and attach the full
output here?
I'm seeing this issue as well when trying to get user home directory
quotas for NFS home directories.
Seems to be an upstream bug that's already been fixed. If I build quota
4.01-1 from Debian Sid on Precise, it works properly.
--
You received this bug notification because you are a member of
And here's the upstream commit that fixes it:
http://linuxquota.git.sourceforge.net/git/gitweb.cgi?p=linuxquota/linuxquota;a=commit;h=8b6ce13e1b196cb9d0cc5b24dfc75c97a9eb883d
Patch applies cleanly 4.00-3 and resolves the NFS quota issue.
Can we please get this SRUed for Precise?
** Patch
** Tags added: rls-q-tracking
** Tags removed: rls-q-tracking
** Tags added: rls-q-notfixing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1032322
Title:
Swap space allocation for
Thanks for reporting this, we are aware of it and are working on an
update. Marking as public.
** Changed in: bind9 (Ubuntu)
Importance: Undecided = High
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
* Install winbind upstart configuration file with --upstart-only option
for consistency with samba package.
Heh, this part is a wrong change. The upstart-only flag is for upstart
jobs which aren't replacing init scripts of the same name.
--
You received this bug notification because you are
The log for the container seems to show reasonable ordering for the
events. It also shows:
cloud-init-nonet waiting 120 seconds for a network device.
cloud-init-nonet gave up waiting for a network device.
6init: cloud-init-nonet main process (31) exited normally
6init: cloud-init-nonet goal
Attaching plaintext console log.
** Attachment added: console.log
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065/+attachment/3308428/+files/console.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init
network-interface (lo) is the only interface job shown, so either
something is going wrong when bringing up this interface that prevents
/etc/network/if-up.d/upstart from emitting the static-network-up event,
or there are other network interfaces configured in
/etc/network/interfaces that have no
Scott, can you please try a test package of mountall built from
lp:ubuntu/mountall? I think I have both the mounting and mounted events
handled correctly there (and in my tests, seemingly faster).
Testing in scenarios other than the cloud boot case would also certainly
be helpful.
--
You
Stéphane,
* Start vlan-network-interface in the background to avoid blocking the
rest of the udev events (most importantly the upstart one).
(LP: #1003656)
This doesn't appear to be a correct fix. I noticed here while working
on an unrelated boot issue that udev is now spitting
Hi James,
if status cups /dev/null ; then
start wait-for-state WAITER=smbd WAIT_FOR=cups
WAIT_STATE=running
fi
This solution has the effect that if the cups job is broken for any
reason, smbd will also not be started. I don't think that's desirable.
We've tried
Addressed in Ubuntu 12.10 with keystone
2012.2~rc1~20120906.2517-0ubuntu2.
** Changed in: keystone (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
This was fixed in Ubuntu 12.04 LTS in
http://www.ubuntu.com/usn/usn-1552-1/ but still needs to be fixed in
quantal (ubuntu 12.10). Attached is a debdiff to do so.
** Patch added: keystone_2012.2~f3-0ubuntu2.debdiff
** Changed in: keystone (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1040626
Title:
Update user's default tenant partially succeeds without
but having BIND server installed shouldn't be affecting the
local DNS lookups, it's a stand-alone bind server...
Yep, that sounds like my original guess:
probably a local DNS server that's installed and misconfigured
such that it's talking to resolvconf when it shouldn't be.
So this sounds
After reviewing the patches on bug #643289, I see that some further work
will be needed because those patches only adjust the 'mounting' event,
not the 'mounted' event. IMHO we should do both.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: cloud-init (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1031065
Title:
cloud-init-nonet runs 'start networking'
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2012-2094
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2012-2144
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
I'm seeing the same thing. Yes, my switch is configured for 802.3ad.
The bond comes up but drops 2pps consistently. I see the vast majority
of the drops on the bond0 interface, the underlying eth0 and eth1
interfaces each show much less loss than bond0.
bond0 Link encap:Ethernet HWaddr
Clint,
FYI, I slightly modified the patch headers to make them DEP-3 compliant
(added Subject: lines with brief descriptions of the issues they
address).
Unsubscribing ubuntu-security-sponsors since there is no more open tasks
for that team to undertake.
Thanks!
--
You received this bug
Clint,
Thanks, debdiff looks good. I'll push this out today.
** Changed in: juju (Ubuntu Precise)
Status: Confirmed = In Progress
** Changed in: juju (Ubuntu Precise)
Assignee: Clint Byrum (clint-fewbar) = Steve Beattie (sbeattie)
--
You received this bug notification because you
Dave, this was fixed for Ubuntu precise in
http://www.ubuntu.com/usn/usn-1466-1/ (2012.1-0ubuntu2.2). Thanks.
** Changed in: nova (Ubuntu Precise)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Agreed that this is more than just a wishlist. AIUI, for cloud compute
nodes this swap requirement can as much as double the local disk space
requirements, which is not an appropriate outcome. I think we really
need different recipes for server vs. desktop installs, here.
** Changed in:
Thanks Scott, I'm reviewing the natty, oneiric, and precise debdiffs
now.
** Changed in: clamav (Ubuntu Natty)
Assignee: (unassigned) = Steve Beattie (sbeattie)
** Changed in: clamav (Ubuntu Precise)
Assignee: (unassigned) = Steve Beattie (sbeattie)
** Changed in: clamav (Ubuntu
The error in the log is:
Voorbereiden om libk5crypto3 1.10+dfsg~beta1-2ubuntu0.2 te vervangen (door
.../libk5crypto3_1.10+dfsg~beta1-2ubuntu0.3_amd64.deb) ...
Uitpakken van vervangende libk5crypto3 ...
dpkg: fout bij afhandelen van libk5crypto3:i386 (--configure):
libk5crypto3:i386
The walinuxagent package in precise-proposed NEW queue is based on an
earlier version from quantal, so is missing this change:
* Restrict target architectures to i386 and amd64.
I assume that if this was worth an upload in quantal, we should have it
in the precise version as well, in which
Hello Ben, or anyone else affected,
Accepted walinuxagent into precise-proposed. The package will build now
and be available at
http://launchpad.net/ubuntu/+source/walinuxagent/1.0~git20120606.c16f5e9-0ubuntu2~12.04.1
in a few hours, and then in the -proposed repository.
Please help us by
This information does not belong in /etc/nsswitch.conf. nsswitch.conf
is a configuration file for libc, for selecting between NSS modules;
autofs should not be relying on being able to stick its own
configuration settings in this file. And base-files should not be
adding such non-standard config
*** This bug is a duplicate of bug 993291 ***
https://bugs.launchpad.net/bugs/993291
** This bug has been marked a duplicate of bug 993291
[SRU] package nis 3.17-32ubuntu1.2 failed to install/upgrade: invoke-rc.d:
unknown initscript, /etc/init.d/nis not found.
--
You received this bug
I'm marking this verification-failed on account of bug #993291, which is
fixed in precise and quantal but which is still present in the version
of the nis package in the -proposed queue.
** Tags removed: verification-done verification-needed
** Tags added: verification-failed
--
You received
Since bug #993291 only affects the upgrade path from a previous SRUed
version to a later version that includes this bug fix, it should only
impact the following upgrades:
lucid-precise
natty-oneiric
oneiric-precise
So the only supported upgrade path from lucid is the one to precise, and
)
Importance: Undecided = Medium
** Changed in: nis (Ubuntu Oneiric)
Assignee: (unassigned) = Steve Langasek (vorlon)
--
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/993291
Title
** Tags removed: verification-failed
** Tags added: verification-needed
--
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
401 - 500 of 1454 matches
Mail list logo
