Don't worry, I'm not dropping the bug. I just want to understand why Debian
decided a "suggests" was enough. I will follow up on that.
On Tue, May 22, 2018, 18:40 Casey & Gina <1772...@bugs.launchpad.net>
wrote:
> Does this mean that you don't consider this to be a bug with the
> packaging?
Turns out the missing dependencies are "suggestions" in the fence-agents
packaging:
root@xenial-fence-agent:~# dpkg -s fence-agents|grep -E "(suds|requests)"
Suggests: python-requests, python-suds
Same in Cosmic, just for python3:
root@cosmic-fence-agents:~# dpkg -s fence-agents|grep -E
** Changed in: fence-agents (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to fence-agents in Ubuntu.
https://bugs.launchpad.net/bugs/1772096
Title:
fence_vmware_soap is not working after
This was fixed in debian in apache 2.4.4-3, and Ubuntu has had 2.4.7
since trusty, so I'm going to mark this as fix released.
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is
I'm sorry this bug stayed open for so long without further comments.
That being said, the affected versions have long since been in a end-of-
life state. I'm going to mark this as "invalid" because of the lack of
further information.
** Changed in: apache2 (Ubuntu)
Status: Confirmed =>
Upstream says it's fixed in samba 4.8, which Cosmic will likely have.
** Changed in: samba (Ubuntu)
Status: New => Triaged
** Changed in: samba (Ubuntu)
Importance: Undecided => Low
** Changed in: samba4 (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug
Upstream marked this as fixed in 2.2.28, which is from the Ubuntu
precise timeframe. Trusty already ships 2.4.7, so marking this fix
released.
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This is showing up in our pending merges report:
http://reqorts.qa.ubuntu.com/reports/ubuntu-server/merges.html
** Changed in: openipmi (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to openipmi in
Hi @manjo,
do you need sponsoring for this SRU? To upload the package, I mean
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1716517
Title:
[arm64/ppc64le] load ipmi_ssif/ipmi_powernv
This needs troubleshooting. The mysql logs have a bunch of these:
2018-05-21T01:01:35.759204Z 0 [ERROR] InnoDB: The error means the system cannot
find the path specified.
And dmesg shows many apparmor denied errors:
[ 5343.367505] audit: type=1400 audit(1526864499.821:48): apparmor="DENIED"
Do a list of all exim packages:
dpkg -l|grep exim4
(make sure they are exim packages, and not just some package that
happens to have "exim" in the description)
Then you can try a few things:
sudo apt -f install
sudo apt purge
It could be that you would have to use dpkg with a --force option,
Sorry to have taken so long to get to this bug, it fell through the
cracks. It's understandable if you have since moved on. I'll close it as
"invalid" because 16.10 is no longer supported.
** Changed in: docker.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification
No reply since more than a year ago, and but expiration isn't working
because of the linked debian and github issues. Closing as invalid for
now. If new information is obtained, please reopen the bug.
** Changed in: docker.io (Ubuntu)
Status: Incomplete => Invalid
--
You received this
I suspect when people abort the installation and try again, that's when
they hit #1769911
** Summary changed:
- package docker.io 1.12.1-0ubuntu13~16.04.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
+ Hangs when searching for a subnet
*** This bug is a duplicate of bug 1724353 ***
https://bugs.launchpad.net/bugs/1724353
** This bug is no longer a duplicate of bug 1767617
package docker.io (not installed) failed to install/upgrade: installed
docker.io package post-removal script subprocess returned error exit status 127
*** This bug is a duplicate of bug 1724353 ***
https://bugs.launchpad.net/bugs/1724353
** This bug has been marked a duplicate of bug 1724353
cannot purge docker.io due to a bashism in nuke-graph-directory
--
You received this bug notification because you are a member of Ubuntu
Server,
Probably caused by people aborting an installation attempt due to
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1628053 and
then trying again, but by then the group already exists. Just an idea, I
haven't debugged it.
--
You received this bug notification because you are a member of
It's showing up in our pending merges report, so should be picked up
soon:
http://reqorts.qa.ubuntu.com/reports/ubuntu-server/merges.html
** Changed in: clamav (Ubuntu)
Status: New => Triaged
** Changed in: clamav (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug
Thanks for filing a bug in Ubuntu.
This is the error log:
Job for amavis.service failed because the control process exited with error
code. See "systemctl status amavis.service" and "journalctl -xe" for details.
invoke-rc.d: initscript amavis, action "start" failed.
[0;1;31m●[0m amavis.service
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/dovecot/+git/dovecot/+merge/345759
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1638865
Title:
dovecot
20 matches
Mail list logo
