Activity log for bug #1583705

Date Who What changed Old value New value Message
2016-05-19 16:53:24 Jared Fernandez bug added bug
2016-05-20 10:06:20 Robie Basak tags xenial bitesize xenial
2016-05-20 10:06:27 Robie Basak bug added subscriber Ubuntu Server Team
2017-03-22 12:40:06 Christian Ehrhardt  bug added subscriber ChristianEhrhardt
2017-06-08 17:59:23 Nish Aravamudan tags bitesize xenial bitesize upstream-report-needed xenial
2017-08-28 13:15:09 Launchpad Janitor logwatch (Ubuntu): status New Confirmed
2017-08-29 21:03:23 Andreas Hasenack logwatch (Ubuntu): status Confirmed Triaged
2017-08-29 21:03:27 Andreas Hasenack logwatch (Ubuntu): importance Undecided Low
2019-06-03 16:42:49 Bryce Harrington logwatch (Ubuntu): assignee Bryce Harrington (bryce)
2020-04-24 04:01:52 Bryce Harrington summary unmatched entries for postfix [SRU] unmatched entries for postfix
2020-04-24 04:02:02 Bryce Harrington logwatch (Ubuntu): importance Low Medium
2020-08-18 02:27:22 Bryce Harrington nominated for series Ubuntu Xenial
2020-08-18 02:27:22 Bryce Harrington bug task added logwatch (Ubuntu Xenial)
2020-08-18 02:27:22 Bryce Harrington nominated for series Ubuntu Groovy
2020-08-18 02:27:22 Bryce Harrington bug task added logwatch (Ubuntu Groovy)
2020-08-18 02:27:22 Bryce Harrington nominated for series Ubuntu Bionic
2020-08-18 02:27:22 Bryce Harrington bug task added logwatch (Ubuntu Bionic)
2020-08-18 02:27:22 Bryce Harrington nominated for series Ubuntu Focal
2020-08-18 02:27:22 Bryce Harrington bug task added logwatch (Ubuntu Focal)
2020-08-18 02:32:33 Bryce Harrington logwatch (Ubuntu Xenial): status New Triaged
2020-08-18 02:32:36 Bryce Harrington logwatch (Ubuntu Xenial): importance Undecided Medium
2020-08-21 02:00:15 Launchpad Janitor merge proposal linked https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/389633
2020-08-26 19:54:42 Launchpad Janitor logwatch (Ubuntu Groovy): status Triaged Fix Released
2020-09-02 17:50:12 Bryce Harrington attachment added Sample log entries for testing the backwards-compatible postfix issue https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+attachment/5407064/+files/unmatched-entries-postfix%3Amail.log
2020-09-03 00:18:39 Bryce Harrington description Under the "Postfix" heading, the following lines appear as unmatched: **Unmatched Entries** 1 May 18 16:58:35 Hostname postfix[4027]: Postfix is running with backwards-compatible default settings 1 May 18 16:58:35 Hostname postfix[4027]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload" 1 May 18 16:58:35 Hostname postfix[4027]: See http://www.postfix.org/COMPATIBILITY_README.html for details 1 May 18 16:57:12 Hostname postgrey[2173]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 ----------------------------------------------------------------- Description: Ubuntu 16.04 LTS Release: 16.04 logwatch: Installed: 7.4.2-1ubuntu1 Candidate: 7.4.2-1ubuntu1 Version table: *** 7.4.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status postfix: Installed: 3.1.0-3 Candidate: 3.1.0-3 Version table: *** 3.1.0-3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status [Impact] Postfix backwards-compatibility notices aren't handled by logwatch, and thus end up in the "Unmatched Entries" section, one per event. These informational messages clutters up the logwatch reports unnecessarily. [Test Case] $ export CODENAME="focal" $ lxc launch ubuntu:${CODENAME} test-logwatch $ lxc exec test-logwatch -- bash # apt-get update # apt-get dist-upgrade -y # apt-get install -y logwatch # wget https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+attachment/5407064/+files/unmatched-entries-postfix%3Amail.log # cat unmatched-entries-postfix%3Amail.log >> /var/log/mail.log # logwatch --detail High --service all --range all --output stdout Without the fix, there will be unmatched entries regarding backwards-compatibility; with the fix there will be a simpler notice that Postfix is running in backwards compatible mode. (Note: For testing it's not really necessary to trigger the original condition that produces the log entry, since for Logwatch the purpose is more about making sure the entry is detected and processed appropriately.) [Regression Potential] Since logwatch filters logs for errors pertinent to administrators, standard things to watch out for are undesired changes in this filtering behavior, such as flagging or failing to flag issues differently than before, other than the specific messages being filtered with this change. [Fix] [Discussion] [Original Report] Under the "Postfix" heading, the following lines appear as unmatched: **Unmatched Entries**       1 May 18 16:58:35 Hostname postfix[4027]: Postfix is running with backwards-compatible default settings       1 May 18 16:58:35 Hostname postfix[4027]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"       1 May 18 16:58:35 Hostname postfix[4027]: See http://www.postfix.org/COMPATIBILITY_README.html for details       1 May 18 16:57:12 Hostname postgrey[2173]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 ----------------------------------------------------------------- Description: Ubuntu 16.04 LTS Release: 16.04 logwatch:   Installed: 7.4.2-1ubuntu1   Candidate: 7.4.2-1ubuntu1   Version table:  *** 7.4.2-1ubuntu1 500         500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages         500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages         100 /var/lib/dpkg/status postfix:   Installed: 3.1.0-3   Candidate: 3.1.0-3   Version table:  *** 3.1.0-3 500         500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages         100 /var/lib/dpkg/status
2020-09-03 00:33:13 Bryce Harrington description [Impact] Postfix backwards-compatibility notices aren't handled by logwatch, and thus end up in the "Unmatched Entries" section, one per event. These informational messages clutters up the logwatch reports unnecessarily. [Test Case] $ export CODENAME="focal" $ lxc launch ubuntu:${CODENAME} test-logwatch $ lxc exec test-logwatch -- bash # apt-get update # apt-get dist-upgrade -y # apt-get install -y logwatch # wget https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+attachment/5407064/+files/unmatched-entries-postfix%3Amail.log # cat unmatched-entries-postfix%3Amail.log >> /var/log/mail.log # logwatch --detail High --service all --range all --output stdout Without the fix, there will be unmatched entries regarding backwards-compatibility; with the fix there will be a simpler notice that Postfix is running in backwards compatible mode. (Note: For testing it's not really necessary to trigger the original condition that produces the log entry, since for Logwatch the purpose is more about making sure the entry is detected and processed appropriately.) [Regression Potential] Since logwatch filters logs for errors pertinent to administrators, standard things to watch out for are undesired changes in this filtering behavior, such as flagging or failing to flag issues differently than before, other than the specific messages being filtered with this change. [Fix] [Discussion] [Original Report] Under the "Postfix" heading, the following lines appear as unmatched: **Unmatched Entries**       1 May 18 16:58:35 Hostname postfix[4027]: Postfix is running with backwards-compatible default settings       1 May 18 16:58:35 Hostname postfix[4027]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"       1 May 18 16:58:35 Hostname postfix[4027]: See http://www.postfix.org/COMPATIBILITY_README.html for details       1 May 18 16:57:12 Hostname postgrey[2173]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 ----------------------------------------------------------------- Description: Ubuntu 16.04 LTS Release: 16.04 logwatch:   Installed: 7.4.2-1ubuntu1   Candidate: 7.4.2-1ubuntu1   Version table:  *** 7.4.2-1ubuntu1 500         500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages         500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages         100 /var/lib/dpkg/status postfix:   Installed: 3.1.0-3   Candidate: 3.1.0-3   Version table:  *** 3.1.0-3 500         500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages         100 /var/lib/dpkg/status [Impact] Postfix backwards-compatibility notices aren't handled by logwatch, and thus end up in the "Unmatched Entries" section, one per event. These informational messages clutters up the logwatch reports unnecessarily. [Test Case] $ export CODENAME="focal" $ lxc launch ubuntu:${CODENAME} test-logwatch $ lxc exec test-logwatch -- bash # apt-get update # apt-get dist-upgrade -y # apt-get install -y logwatch # wget https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+attachment/5407064/+files/unmatched-entries-postfix%3Amail.log # cat unmatched-entries-postfix%3Amail.log >> /var/log/mail.log # logwatch --detail High --service all --range all --output stdout Without the fix, there will be unmatched entries regarding backwards-compatibility; with the fix there will be a simpler notice that Postfix is running in backwards compatible mode. (Note: For testing it's not really necessary to trigger the original condition that produces the log entry, since for Logwatch the purpose is more about making sure the entry is detected and processed appropriately.) [Regression Potential] Since logwatch filters logs for errors pertinent to administrators, standard things to watch out for are undesired changes in this filtering behavior, such as flagging or failing to flag issues differently than before, other than the specific messages being filtered with this change. [Original Report] Under the "Postfix" heading, the following lines appear as unmatched: **Unmatched Entries**       1 May 18 16:58:35 Hostname postfix[4027]: Postfix is running with backwards-compatible default settings       1 May 18 16:58:35 Hostname postfix[4027]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"       1 May 18 16:58:35 Hostname postfix[4027]: See http://www.postfix.org/COMPATIBILITY_README.html for details       1 May 18 16:57:12 Hostname postgrey[2173]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 ----------------------------------------------------------------- Description: Ubuntu 16.04 LTS Release: 16.04 logwatch:   Installed: 7.4.2-1ubuntu1   Candidate: 7.4.2-1ubuntu1   Version table:  *** 7.4.2-1ubuntu1 500         500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages         500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages         100 /var/lib/dpkg/status postfix:   Installed: 3.1.0-3   Candidate: 3.1.0-3   Version table:  *** 3.1.0-3 500         500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages         100 /var/lib/dpkg/status
2020-09-03 04:35:46 Launchpad Janitor merge proposal linked https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390212
2020-09-03 04:39:09 Launchpad Janitor merge proposal linked https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390213
2020-09-03 04:39:53 Launchpad Janitor merge proposal linked https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390214
2020-09-04 00:19:39 Launchpad Janitor merge proposal unlinked https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390212
2020-09-08 23:31:01 Bryce Harrington logwatch (Ubuntu Xenial): status Triaged In Progress
2020-09-08 23:31:04 Bryce Harrington logwatch (Ubuntu Bionic): status New In Progress
2020-09-08 23:31:06 Bryce Harrington logwatch (Ubuntu Focal): status New In Progress
2020-09-08 23:31:08 Bryce Harrington logwatch (Ubuntu Bionic): importance Undecided Medium
2020-09-08 23:31:10 Bryce Harrington logwatch (Ubuntu Focal): importance Undecided Medium
2020-09-08 23:31:12 Bryce Harrington logwatch (Ubuntu Focal): assignee Bryce Harrington (bryce)
2020-09-08 23:31:14 Bryce Harrington logwatch (Ubuntu Bionic): assignee Bryce Harrington (bryce)
2020-09-08 23:31:16 Bryce Harrington logwatch (Ubuntu Xenial): assignee Bryce Harrington (bryce)
2020-09-15 18:44:37 Brian Murray logwatch (Ubuntu Focal): status In Progress Fix Committed
2020-09-15 18:44:40 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2020-09-15 18:44:45 Brian Murray bug added subscriber SRU Verification
2020-09-15 18:44:50 Brian Murray tags bitesize upstream-report-needed xenial bitesize upstream-report-needed verification-needed verification-needed-focal xenial
2020-09-15 18:51:43 Brian Murray logwatch (Ubuntu Bionic): status In Progress Fix Committed
2020-09-15 18:51:51 Brian Murray tags bitesize upstream-report-needed verification-needed verification-needed-focal xenial bitesize upstream-report-needed verification-needed verification-needed-bionic verification-needed-focal xenial
2020-09-15 19:03:45 Brian Murray logwatch (Ubuntu Xenial): status In Progress Fix Committed
2020-09-15 19:03:53 Brian Murray tags bitesize upstream-report-needed verification-needed verification-needed-bionic verification-needed-focal xenial bitesize upstream-report-needed verification-needed verification-needed-bionic verification-needed-focal verification-needed-xenial xenial
2020-09-29 01:59:25 Bryce Harrington description [Impact] Postfix backwards-compatibility notices aren't handled by logwatch, and thus end up in the "Unmatched Entries" section, one per event. These informational messages clutters up the logwatch reports unnecessarily. [Test Case] $ export CODENAME="focal" $ lxc launch ubuntu:${CODENAME} test-logwatch $ lxc exec test-logwatch -- bash # apt-get update # apt-get dist-upgrade -y # apt-get install -y logwatch # wget https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+attachment/5407064/+files/unmatched-entries-postfix%3Amail.log # cat unmatched-entries-postfix%3Amail.log >> /var/log/mail.log # logwatch --detail High --service all --range all --output stdout Without the fix, there will be unmatched entries regarding backwards-compatibility; with the fix there will be a simpler notice that Postfix is running in backwards compatible mode. (Note: For testing it's not really necessary to trigger the original condition that produces the log entry, since for Logwatch the purpose is more about making sure the entry is detected and processed appropriately.) [Regression Potential] Since logwatch filters logs for errors pertinent to administrators, standard things to watch out for are undesired changes in this filtering behavior, such as flagging or failing to flag issues differently than before, other than the specific messages being filtered with this change. [Original Report] Under the "Postfix" heading, the following lines appear as unmatched: **Unmatched Entries**       1 May 18 16:58:35 Hostname postfix[4027]: Postfix is running with backwards-compatible default settings       1 May 18 16:58:35 Hostname postfix[4027]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"       1 May 18 16:58:35 Hostname postfix[4027]: See http://www.postfix.org/COMPATIBILITY_README.html for details       1 May 18 16:57:12 Hostname postgrey[2173]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 ----------------------------------------------------------------- Description: Ubuntu 16.04 LTS Release: 16.04 logwatch:   Installed: 7.4.2-1ubuntu1   Candidate: 7.4.2-1ubuntu1   Version table:  *** 7.4.2-1ubuntu1 500         500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages         500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages         100 /var/lib/dpkg/status postfix:   Installed: 3.1.0-3   Candidate: 3.1.0-3   Version table:  *** 3.1.0-3 500         500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages         100 /var/lib/dpkg/status [Impact] Postfix backwards-compatibility notices aren't handled by logwatch, and thus end up in the "Unmatched Entries" section, one per event. These informational messages clutters up the logwatch reports unnecessarily. [Test Case] $ export CODENAME="focal" $ lxc launch ubuntu:${CODENAME} test-logwatch $ lxc exec test-logwatch -- bash # apt-get update # apt-get dist-upgrade -y # apt-get install -y postfix # apt-get install -y logwatch # wget https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+attachment/5407064/+files/unmatched-entries-postfix%3Amail.log # cat unmatched-entries-postfix:mail.log >> /var/log/mail.log # logwatch --detail High --service all --range all --output stdout Without the fix, there will be unmatched entries regarding backwards-compatibility; with the fix there will be a simpler notice that Postfix is running in backwards compatible mode. (Note: For testing it's not really necessary to trigger the original condition that produces the log entry, since for Logwatch the purpose is more about making sure the entry is detected and processed appropriately.) [Regression Potential] Since logwatch filters logs for errors pertinent to administrators, standard things to watch out for are undesired changes in this filtering behavior, such as flagging or failing to flag issues differently than before, other than the specific messages being filtered with this change. [Original Report] Under the "Postfix" heading, the following lines appear as unmatched: **Unmatched Entries**       1 May 18 16:58:35 Hostname postfix[4027]: Postfix is running with backwards-compatible default settings       1 May 18 16:58:35 Hostname postfix[4027]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"       1 May 18 16:58:35 Hostname postfix[4027]: See http://www.postfix.org/COMPATIBILITY_README.html for details       1 May 18 16:57:12 Hostname postgrey[2173]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 ----------------------------------------------------------------- Description: Ubuntu 16.04 LTS Release: 16.04 logwatch:   Installed: 7.4.2-1ubuntu1   Candidate: 7.4.2-1ubuntu1   Version table:  *** 7.4.2-1ubuntu1 500         500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages         500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages         100 /var/lib/dpkg/status postfix:   Installed: 3.1.0-3   Candidate: 3.1.0-3   Version table:  *** 3.1.0-3 500         500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages         100 /var/lib/dpkg/status
2020-09-29 17:37:40 Bryce Harrington tags bitesize upstream-report-needed verification-needed verification-needed-bionic verification-needed-focal verification-needed-xenial xenial bitesize upstream-report-needed verification-done verification-done-bionic verification-done-focal verification-done-xenial xenial
2020-09-29 21:09:19 Launchpad Janitor logwatch (Ubuntu Focal): status Fix Committed Fix Released
2020-09-29 21:09:39 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2020-10-06 23:37:09 Launchpad Janitor logwatch (Ubuntu Bionic): status Fix Committed Fix Released
2020-10-06 23:37:54 Launchpad Janitor logwatch (Ubuntu Xenial): status Fix Committed Fix Released
2021-02-23 19:18:46 Launchpad Janitor merge proposal linked https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/398554