** Changed in: pax (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pax in Ubuntu.
https://bugs.launchpad.net/bugs/1527882
Title:
package pax 1:20120606-2+deb7u1 failed to install/upgrade:
Hi Canonical Server Team, on another distro with a previous version of
multipath-tools (0.4.9) I can not see this misbehaviour.
Although 0.5.0 isn't that new, I don't know of another distro for s390x with
0.5.0 where I could check this.
--
You received this bug notification because you are a
** Package changed: ubuntu => multipath-tools (Ubuntu)
--
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/1540407
Title:
multipathd drops paths of a temporarily lost device
To
Try:
sudo dpkg -a --configure
Or:
sudo dpkg -i /var/cache/apt/archives/pax_*.deb
Or:
sudo apt-get install --reinstall pax
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pax in Ubuntu.
https://bugs.launchpad.net/bugs/1527882
'
then you can check if there is output for:
# snmpwalk -v3 -u icinga -l authPriv -a SHA -A 'P1' -x AES -X 'P2' localhost
Kind regards,
Thorsten
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net
Yes, the new “pax” archive format, and some of the new -o options, are
not supported. This utility is compatible with an older version of
POSIX.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pax in Ubuntu.
Public bug reported:
The regex on line 12 in /etc/logcheck/ignore.d.server/dhclient needs
updating since it does not match the current output from dhclient
The current line (12) as included in version 1.3.16 of logcheck-database looks
like this:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
Public bug reported:
service scripts for bacula-director, bacula-sd und bacula-fd don't stop,
reload or give status when the respective daemon is launched on a
different port (directive dirport, sdport, fdport).
The cause is that the start script generates a PID file with the port
number in its
The bug is also occuring in 14.04.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1320906
Title:
Bacula init scripts don't stop, status, reload
To manage notifications about this
Also seen on OMAP4 Pandaboard with Ubuntu 13.10 (GNU/Linux 3.5.0-236-omap4
armv7l)
CPU Usage is not a problem until irqbalance has eaten almost all ram.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
Public bug reported:
TI Omap4 Pandaboard rev a3
Ubuntu 3.5.0-235.51-omap4 3.5.7.23
Uptime 4 days, irqbalance memory consumption equals 228MB and growing. Memory
usage grows until system goes unstable.
dpkg -l irqbalance | grep -E ^ii | tr -s ' ' | cut -d' ' -f3
1.0.6-2
irqbalance -d -f
This
** Changed in: setserial (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to setserial in Ubuntu.
https://bugs.launchpad.net/bugs/179497
Title:
use of deprecated update-modules command in
Ah right, there would be the usecase of LDAP with SSL used by
non-GPL-compatible programmes.
So the proper fix is to have three sets of LDAP (client) libraries. The rest of
the packages (server
and utilities) can then be built against whatever of those the maintainers see
best fit.
--
You
** Also affects: openldap (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #658739
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658739
** Also affects: gnutls26 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658739
Hi all,
this bug has been brought to my attention by my boss today.
If I understand the situation correctly, the problem is:
• OpenLDAP links against GnuTLS (gnutls26)
• gnutls26 links against gcrypt, which has the bug
• gnutls28 links against nettle, but also gmp which is LGPLv3+
• OpenLDAP
mailman and openssh-server are the two failing packages
** Also affects: mailman (Ubuntu)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gforge (Ubuntu)
Status: New = Invalid
--
You received this
not in Fusionforge but in BIND
** Package changed: gforge (Ubuntu) = bind9 (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/765897
Title:
package gforge-dns-bind9 4.8.2-1
ssh-vulnkey and ssh’ing out WFM too. Thanks!
--
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/713002
Title:
Impossible to disable IPv4
--
Ubuntu-server-bugs mailing list
Public bug reported:
Regression in hardy-proposed: ssh-vulnkey disappeared:
openssh (1:4.7p1-8ubuntu2) hardy-proposed; urgency=low
* Backport from upstream:
- Only listen for IPv6 connections on AF_INET6 sockets (LP: #713002).
-- Colin Watson cjwat...@ubuntu.com Tue, 08 Feb 2011
Yeah, works for me, thanks!
tgl...@tglase:~ $ sudo env LC_ALL=C apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Starting
Starting 2
Done
Done
The following packages will be upgraded:
apache2 apache2-doc
As you can see in LP: #583698, helping out in testing does not get us bugs
fixed,
au contraire, it raises the level of annoyance at people ignoring the bugs
reported.
Anyway, I’m only tunning on proposed because then I can catch things like this
before they affect my cow-orkers… no Sybase here.
Public bug reported:
Binary package hint: php5
$ apt-cache policy php5-cli
php5-cli:
Installed: 5.2.4-2ubuntu5.11
Candidate: 5.2.4-2ubuntu5.11
Version table:
*** 5.2.4-2ubuntu5.11 0
100 /var/lib/dpkg/status
Thank you *VERY MUCH* for breaking a lot of our computers now.
Now I know why we’re still using Kubuntu. /sarcasm
The priority of this bug ought to be raised to critical now, as the
next upgrade on many of our machines will fail:
r...@bkix:~ # apt-cache policy apache2.2-common
Can’t have been this hard… the attached debdiff fixes the issue for me.
I’ve deployed that in our internal repo right now, thanks again for all
the breakage.
** Patch added: debdiff fixing this issue, for Hardy, tested
Hrm, so now how do I set the severity in LP? This is critical.
If this wents from proposed to updates, we have a problem.
--
hardy-proposed (2.2.8-1ubuntu0.16) uninstallable
https://bugs.launchpad.net/bugs/583698
You received this bug notification because you are a member of Ubuntu
Server Team,
@Dave: Old install of hardy (these are our desktop systems at work), which got
upgraded (as it is, daily).
My machine has proposed in sources.list as I’m the admin in charge of them.
@Colin: Yes, -x’ing apache was intentional, to have it installed/usable
but not enabled by default.
** Changed
@Dave: I agree, but please make sure that the package version which gives me
the issue
does not propagate to hardy-updates because otherwise I may have several dozen
angry
people on me.
Changing the affected line to
chmod `dpkg-statoverride --list /usr/sbin/apache2 | cut -d' ' -f 3`
Considering I mentioned hardy-backports, and the filename of the debdiff is
http://launchpadlibrarian.net/39211564/kvm_84+dfsg-0ubuntu12.4~hardy1tarent1.debdiff
that should’ve been obvious ;-)
We’re using hardy with hardy-backports.
** Changed in: kvm (Ubuntu)
Status: Incomplete = New
--
** Patch added: debdiff fixing this issue
http://launchpadlibrarian.net/39211564/kvm_84%2Bdfsg-0ubuntu12.4%7Ehardy1tarent1.debdiff
--
fails to install due to differing kernel versions between installer and
installee
https://bugs.launchpad.net/bugs/522074
You received this bug notification
Public bug reported:
Binary package hint: kvm-source
The version of the kernel used by the Kubuntu Installer and the version of the
kernel
that actually gets installed differ. When adding kvm-source during the
installation,
for example via a preseed late-command using in-target, it fails to
Public bug reported:
Both hardy-updates and hardy-security contain libsasl2-modules
2.1.22.dfsg1-18ubuntu2.1
whereas hardy contained libsasl2-modules 2.1.22.dfsg1-18ubuntu2 (according to
a-c policy).
When installing a fresh system with security already included (after all, no
need to first
31 matches
Mail list logo
