| 2018-08-10 16:03:40 |
mkurz |
bug |
|
|
added bug |
| 2018-08-13 13:24:36 |
Robie Basak |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894501 |
|
| 2018-08-13 13:24:36 |
Robie Basak |
bug task added |
|
exim4 (Debian) |
|
| 2018-08-13 13:24:43 |
Robie Basak |
exim4 (Ubuntu): status |
New |
Triaged |
|
| 2018-08-13 13:28:19 |
Robie Basak |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-08-13 13:28:19 |
Robie Basak |
bug task added |
|
exim4 (Ubuntu Bionic) |
|
| 2018-08-13 13:28:22 |
Robie Basak |
exim4 (Ubuntu Bionic): status |
New |
Triaged |
|
| 2018-08-13 13:28:25 |
Robie Basak |
exim4 (Ubuntu): status |
Triaged |
Fix Released |
|
| 2018-08-13 13:28:30 |
Robie Basak |
tags |
|
bitesize server-next |
|
| 2018-08-15 16:51:43 |
Bug Watch Updater |
exim4 (Debian): status |
Unknown |
Fix Released |
|
| 2018-10-10 18:28:56 |
Andreas Hasenack |
exim4 (Ubuntu Bionic): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2018-10-10 18:29:00 |
Andreas Hasenack |
exim4 (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2018-10-10 18:29:03 |
Andreas Hasenack |
exim4 (Ubuntu Bionic): importance |
Undecided |
Low |
|
| 2018-10-10 19:28:22 |
Andreas Hasenack |
description |
Already fixed upstream and in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894501
Fix is easy:
https://git.exim.org/exim.git/blobdiff/d51252ebebd7744dd218c4af965ca3d5424648cc..44de51a174765f7f5ecb250638cdb3fe64ec67dc:/src/src/eximstats.src
Please backport to Bionic.
Thanks! |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original description]
Already fixed upstream and in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894501
Fix is easy:
https://git.exim.org/exim.git/blobdiff/d51252ebebd7744dd218c4af965ca3d5424648cc..44de51a174765f7f5ecb250638cdb3fe64ec67dc:/src/src/eximstats.src
Please backport to Bionic.
Thanks! |
|
| 2018-10-10 19:44:38 |
Andreas Hasenack |
description |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original description]
Already fixed upstream and in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894501
Fix is easy:
https://git.exim.org/exim.git/blobdiff/d51252ebebd7744dd218c4af965ca3d5424648cc..44de51a174765f7f5ecb250638cdb3fe64ec67dc:/src/src/eximstats.src
Please backport to Bionic.
Thanks! |
[Impact]
The eximstats tool, when not given any command line parameters, prints out a (harmless) warning:
# eximstats
Use of uninitialized value $ARGV[0] in string eq at /usr/sbin/eximstats line 563.
Problem is that this tool is used in a cron job which, if enabled, will print output to stderr and that is enough for cron to email an admin, which is annoying.
The fix is simple and is applied upstream:
-if ($ARGV[0] eq '--version') {
+if (@ARGV and $ARGV[0] eq '--version') {
[Test Case]
On Bionic:
* Install exim4:
sudo apt update
sudo apt install exim4
* Run eximstats with no arguments, which will block (it's waiting for stdin) but print the warning:
ubuntu@bionic-eximstats:~$ eximstats
Use of uninitialized value $ARGV[0] in string eq at /usr/sbin/eximstats line 563.
* To observe the effect this has in the cron job, edit /etc/cron.daily/exim4-base and set E4BCD_DAILY_REPORT_TO near the top of the file to "ubuntu@localhost", like this:
E4BCD_DAILY_REPORT_TO="ubuntu@localhost"
* Then run these commands and observe that the cron script prints out the same warning, which, if ran by cron, would have been emailed to the admin:
$ echo hello | mail -s hello ubuntu@localhost
$ sudo /etc/cron.daily/exim4-base
Use of uninitialized value $ARGV[0] in string eq at /usr/sbin/eximstats line 563.
With the updated packages, eximstats with no arguments will just block, waiting for data on stdin, and not print the warning. The cron job test will also be silent.
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original description]
Already fixed upstream and in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894501
Fix is easy:
https://git.exim.org/exim.git/blobdiff/d51252ebebd7744dd218c4af965ca3d5424648cc..44de51a174765f7f5ecb250638cdb3fe64ec67dc:/src/src/eximstats.src
Please backport to Bionic.
Thanks! |
|
| 2018-10-10 19:46:34 |
Andreas Hasenack |
description |
[Impact]
The eximstats tool, when not given any command line parameters, prints out a (harmless) warning:
# eximstats
Use of uninitialized value $ARGV[0] in string eq at /usr/sbin/eximstats line 563.
Problem is that this tool is used in a cron job which, if enabled, will print output to stderr and that is enough for cron to email an admin, which is annoying.
The fix is simple and is applied upstream:
-if ($ARGV[0] eq '--version') {
+if (@ARGV and $ARGV[0] eq '--version') {
[Test Case]
On Bionic:
* Install exim4:
sudo apt update
sudo apt install exim4
* Run eximstats with no arguments, which will block (it's waiting for stdin) but print the warning:
ubuntu@bionic-eximstats:~$ eximstats
Use of uninitialized value $ARGV[0] in string eq at /usr/sbin/eximstats line 563.
* To observe the effect this has in the cron job, edit /etc/cron.daily/exim4-base and set E4BCD_DAILY_REPORT_TO near the top of the file to "ubuntu@localhost", like this:
E4BCD_DAILY_REPORT_TO="ubuntu@localhost"
* Then run these commands and observe that the cron script prints out the same warning, which, if ran by cron, would have been emailed to the admin:
$ echo hello | mail -s hello ubuntu@localhost
$ sudo /etc/cron.daily/exim4-base
Use of uninitialized value $ARGV[0] in string eq at /usr/sbin/eximstats line 563.
With the updated packages, eximstats with no arguments will just block, waiting for data on stdin, and not print the warning. The cron job test will also be silent.
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original description]
Already fixed upstream and in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894501
Fix is easy:
https://git.exim.org/exim.git/blobdiff/d51252ebebd7744dd218c4af965ca3d5424648cc..44de51a174765f7f5ecb250638cdb3fe64ec67dc:/src/src/eximstats.src
Please backport to Bionic.
Thanks! |
[Impact]
The eximstats tool, when not given any command line parameters, prints out a (harmless) warning:
# eximstats
Use of uninitialized value $ARGV[0] in string eq at /usr/sbin/eximstats line 563.
Problem is that this tool is used in a cron job which, if enabled, will print output to stderr and that is enough for cron to email an admin, which is annoying.
The fix is simple and is applied upstream:
-if ($ARGV[0] eq '--version') {
+if (@ARGV and $ARGV[0] eq '--version') {
[Test Case]
On Bionic:
* Install exim4:
sudo apt update
sudo apt install exim4
* Run eximstats with no arguments, which will block (it's waiting for stdin) but print the warning:
ubuntu@bionic-eximstats:~$ eximstats
Use of uninitialized value $ARGV[0] in string eq at /usr/sbin/eximstats line 563.
* To observe the effect this has in the cron job, edit /etc/cron.daily/exim4-base and set E4BCD_DAILY_REPORT_TO near the top of the file to "ubuntu@localhost", like this:
E4BCD_DAILY_REPORT_TO="ubuntu@localhost"
* Then run these commands and observe that the cron script prints out the same warning, which, if ran by cron, would have been emailed to the admin:
$ echo hello | mail -s hello ubuntu@localhost
$ sudo /etc/cron.daily/exim4-base
Use of uninitialized value $ARGV[0] in string eq at /usr/sbin/eximstats line 563.
With the updated packages, eximstats with no arguments will just block, waiting for data on stdin, and not print the warning. The cron job test will also be silent.
[Regression Potential]
I can't imagine a regression with this change, other than the usual fact the the updated package is a rebuild, and it might link with different libraries since bionic was released.
[Other Info]
Were it not for the cron job, this update would probably not be worth it.
[Original description]
Already fixed upstream and in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894501
Fix is easy:
https://git.exim.org/exim.git/blobdiff/d51252ebebd7744dd218c4af965ca3d5424648cc..44de51a174765f7f5ecb250638cdb3fe64ec67dc:/src/src/eximstats.src
Please backport to Bionic.
Thanks! |
|
| 2018-10-10 20:42:57 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/exim4/+git/exim4/+merge/356433 |
|
| 2018-10-10 20:44:21 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/exim4/+git/exim4/+merge/356435 |
|
| 2018-10-10 20:45:40 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/exim4/+git/exim4/+merge/356437 |
|
| 2018-10-10 20:47:54 |
Andreas Hasenack |
merge proposal unlinked |
https://code.launchpad.net/~ahasenack/ubuntu/+source/exim4/+git/exim4/+merge/356433 |
|
|
| 2018-10-23 23:02:03 |
Brian Murray |
exim4 (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-10-23 23:02:06 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-10-23 23:02:09 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2018-10-23 23:02:14 |
Brian Murray |
tags |
bitesize server-next |
bitesize server-next verification-needed verification-needed-bionic |
|
| 2018-10-26 17:01:53 |
Andreas Hasenack |
tags |
bitesize server-next verification-needed verification-needed-bionic |
bitesize server-next verification-done-bionic verification-needed |
|
| 2018-12-13 08:40:27 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-12-13 08:40:25 |
Launchpad Janitor |
exim4 (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
