On Wed, Nov 22, 2017 at 5:20 AM, Mathias <1658...@bugs.launchpad.net> wrote:
> Bionic includes the /etc/apache2/mods-available/proxy_http2.load file,
> but the module mod_proxy_http2.so has been removed.
>
> Is it a mistake?
>
> Suite: Ubuntu 18.04 (bionic)
> https://packages.ubuntu.com/bionic/amd6
This is now enabled in bionic.
** Changed in: apache2 (Ubuntu)
Status: Triaged => Fix Released
--
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/1658469
Title:
[FFe] mod_http2 is
** Description changed:
[Impact]
+ The logrotate script that is responsible for updating awstats statistics does
not run because the www-data user that it runs as does not have a valid shell.
- * An explanation of the effects of the bug on users and
-
- * justification for backporting the
** Changed in: awstats (Ubuntu Xenial)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: awstats (Ubuntu Artful)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: awstats (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: awstat
There won't be time to SRU this for zesty before its EOL.
** Changed in: awstats (Ubuntu Zesty)
Status: Triaged => Won't Fix
--
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/1708665
@kirkland: accumulated justifications:
1) no python3 support (not possible? per c#1) -- which implies we'd
remove it eventually anyways
2) no reverse-depends (no consumers)
3) not in Debian, so it's purely technical debt?
I haven't looked to see if there have been many/any bugs over the years,
I'm +1 for demoting to universe. I don't yet see enough justification
for removing it from Ubuntu entirely, though.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tickcount in Ubuntu.
https://bugs.launchpad.net/bugs/1740160
Title:
That is expected, see comment #8. Unless your apt operation exited with
a status code other than zero, i.e., apt or dpkg actually finished with
an error.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launc
None of the log files correspond to the failure you had yesterday (Jan
4th, 2018).
Please show the output of these commands:
sudo systemctl status smbd nmbd winbind samba-ad-service
sudo systemctl restart smbd nmbd
Also please attach /var/log/syslog, and if something new was logged to
/var/log/
