This bug was fixed in the package update-notifier - 3.168.15
---
update-notifier (3.168.15) xenial; urgency=medium
* debian/control: add lsb-release to the update-notifier-common depends as
it is used by apt-cdrom-check. (LP: #1927996)
* data/apt_check.py
- Only show esm-a
This bug was fixed in the package update-notifier - 3.192.1.11
---
update-notifier (3.192.1.11) bionic; urgency=medium
* debian/control: add lsb-release to the update-notifier-common depends as
it is used by apt-cdrom-check. (LP: #1927996)
* data/apt_check.py
- Only show e
This bug was fixed in the package update-notifier - 3.192.30.8
---
update-notifier (3.192.30.8) focal; urgency=medium
* debian/control: add lsb-release to the update-notifier-common depends as
it is used by apt-cdrom-check. (LP: #1927996)
* data/apt_check.py
- Only show es
This bug was fixed in the package update-notifier - 3.192.40.3
---
update-notifier (3.192.40.3) hirsute; urgency=medium
* debian/control: add lsb-release to the update-notifier-common depends as
it is used by apt-cdrom-check. (LP: #1927996)
* data/apt_check.py
- Only show
Hi Lukasz, those instructions were created before the package was
uploaded into ṕroposed. In the script I have used to test this bug, I
have used the proposed package.
But if needed, I can update the instructions to use the proposed
packages instead
--
You received this bug notification because
Hey Lucas! What package versions did you use? Were those from the ubuntu
archives? Since I see the instructions still mention using the PPA while
for testing we need to use the archive packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Also, regarding the autopkgtest failures we are seeing, they seem related to
this update-manager bug:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1929865
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.
To perform the verification I have used the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-dev
function generate_motd_message() {
message=$1
Hello Aaron, or anyone else affected,
Accepted update-notifier into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.192.1.11 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
Hello Aaron, or anyone else affected,
Accepted update-notifier into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.192.30.8 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. Se
Hello Aaron, or anyone else affected,
Accepted update-notifier into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.192.40.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Description changed:
- Starting with update-notifier-common 3.192.30.7 (focal), my up-to-date
- systems are showing this MOTD on login:
+ [Impact]
+ On a system without updates to be installed, not showing any message in motd
feels that something went wrong in the backend. Also, currently we a
** Also affects: update-notifier (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: update-notifier (Ubuntu Focal)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
This bug was fixed in the package update-notifier - 3.192.44
---
update-notifier (3.192.44) impish; urgency=medium
[ Lucas Moura ]
* data/apt_check.py
- Show esm-apps status header when running on LTS distro that
has not yet entered Extended Security Maintenance
-- Bri
This fix is currently stuck in -proposed for impish but should be
released shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926819
Title:
Empty MOTD on up-to-date systems (includes fix)
To m
** Tags added: fr-1400
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926819
Title:
Empty MOTD on up-to-date systems (includes fix)
To manage notifications about this bug go to:
https://bugs.launch
SRU template verification
[Impact]
On a system without updates to be installed, not showing any message in motd
feels that something went wrong in the backend. Also, currently we are printing
unwanted white spaces in that scenario, which is not a good user experience
here.
[Test case]
To repr
** Changed in: update-notifier (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926819
Title:
Empty MOTD on up-to-date systems (includes fix)
To m
https://code.launchpad.net/~lamoura/update-notifier/+git/update-
notifier/+merge/402163
** Changed in: update-notifier (Ubuntu)
Status: Confirmed => In Progress
** Changed in: update-notifier (Ubuntu)
Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)
--
You rec
There is still value in a "you are fully up to date" message, and I
would expect such a behaviour change to be optional. This has not been
announced and I find myself unable to opt out. Offering users more
choice is great, but, I have no choices here. That doesn't sit right.
--
You received this
I agree with Aaron and Daniel. I have a custom MOTD generation script
that uses the output of updater-notifier `head -qn 2 /var/lib/update-
notifier/updates-available`. Not having any text in that file if there
are no updates available breaks the layout of the MOTD output.
Regardless of my custom
Seconding what Aaron said, it looks weird and makes it seem that
something went wrong, causing me to wrack my brain and try to figure out
if I broke something across multiple servers, lol.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Thanks for the response Lucas. I would prefer to see something to the
effect that the system is up to date, because that at least tells me
that update-notifier-common is there and working. But if the decision is
to not write anything in that case, then I strongly agree with Daniel.
The 3 blank line
It looks weird without the update notification stuff and the large(ish)
whitespace instead, can something be done about that? Alternatively, is
it possible to make the suppression of 'no info' optional?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Thank you for raising this. The change was made intentionally to reduce
noise to users when there wasn't anything to act upon. We're always
keeping an eye out for improving things and will keep this open as we
discuss ways we can make things better.
--
You received this bug notification because y
** Tags added: regression-update rls-ff-incoming
** Changed in: update-notifier (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926819
Title:
Empty MOTD on
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: update-notifier (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926819
Tit
The attachment "0001-apt_check.py-Fix-empty-output-in-the-no-ESM-up-to-
da.patch" seems to be a patch. If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message per
28 matches
Mail list logo
