I just removed Spamassassin --purge. Sould'nt report error anymore!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1256087
Title:
package spamassassin (not installed) failed to
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1256087
Title:
package spamassassin (not installed) failed to install/upgrade: le
sous-pr
Public bug reported:
This bug happens since 13.04.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: spamassassin (not installed)
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
Date: Thu Nov
This bug was fixed in the package apache2 - 2.4.6-2ubuntu4
---
apache2 (2.4.6-2ubuntu4) trusty; urgency=low
* d/p/ignore-quilt-dir, d/p/itk-rerun-configure.patch: adjust build system so
that it does not use files find inside the .pc directory. This stops a
double module load
** Description changed:
+ [Impact]
+
+ The Apache ChrootDir doesn't work, causing Apache to fail if you try to
+ use it. This means that it is not possible to run Apache in a chroot,
+ which is a regression from 13.04.
+
+ [Development Fix]
+
+ Adjust build system to not use things inside .pc/.
As 2.4.6-4 hasn't been uploaded to Debian yet, and fixing Trusty blocks
fixing Saucy, I've verified the problem with a dep8 test, verified
Stefan's patch with it and uploaded the fix to Trusty. Thanks!
** Changed in: apache2 (Ubuntu)
Status: Triaged => Fix Committed
** Also affects: apache
** Description changed:
- The radosgw upstart configurations started shipping in 13.10; however
- one namespace conflicts with the radosgw init script but does not do the
- same thing; so upgrades will break.
+ [Impact]
+ RADOS Gateway users upgrading from raring that rely on the init script to
s
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: open-vm-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member o
** Changed in: mongodb (Ubuntu)
Importance: Undecided => Low
** Changed in: mongodb (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1242237
T
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration problem
** Changed in: juju-core (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1208430
Title:
mongodb runs as root user
To manage notifications ab
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-13.11:
SRU for juju-core 1.16.3 into saucy: INPROGRESS
Work items for ubuntu-13.12:
- Create juju-mongodb package from mongodb: TODO
+ Create juju-mongodb package from mongodb: INPROGRESS
[racb] Enable mongodb/li
Blueprint changed by James Page:
Assignee: Ubuntu Server Team => James Page
--
Juju activities for Trusty
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-juju
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://l
Blueprint changed by James Page:
Drafter: James Page => Ubuntu Server Team
--
Juju activities for Trusty
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-juju
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://li
** Changed in: mdbtools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mdbtools in Ubuntu.
https://bugs.launchpad.net/bugs/1227033
Title:
mdb-sql crashed with SIGSEGV in _IO_vfpr
** Changed in: mdbtools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mdbtools in Ubuntu.
https://bugs.launchpad.net/bugs/390730
Title:
mdb-export prints binary for OLE fields.
I presume documentation is addressed in the upstream project?
** Package changed: maas (Ubuntu) => maas
** Summary changed:
- Documentation needs to cover configuring MAAS for tftp boot
+ Documentation does not cover configuring MAAS for tftp boot
--
You received this bug notification because
I have to clarify that I'm not sure that this has something to do with
KVM, QEMU and the like.
I think is more a problem of the linux bridge driver since It fails even
if you don't have any vm running. Yes, it takes more time to fail but
this can be because not enough traffic to make it fail.
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libmongodb-perl (Ubuntu Raring)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libmongodb-perl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libmongodb-perl (Ubuntu Saucy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchp
alrighty, the transition is now done and 1.11.2-1 built against the new
samba, so seeding it should succeed now
--
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/903752
Title:
[MIR] sssd
22 matches
Mail list logo