I retried testcase (b) in an up-to-date focal, and it still happens.
It's been a long while since I touched this package and I don't remember
the details anymore. Since I'm no longer working on this, I'll mark the
bug status accordingly.
** Changed in: base-files (Ubuntu Xenial)
Status: In
I think the remaining scenario is (b) (look up in the bug description),
and (c) is just a wildcard scenario ("anything else I didn't think of").
For (b), I think the more likely case would be another base-files SRU without
the fix from this bug here, and where the user would have:
- base-files
debootstrap never installs packages from updates: due to a longstanding
design limitation, it can only install from a single pocket, so
debootstrap always uses the release pocket and images are upgraded
afterwards.
Given this limitation, is there actually any impact to users of stable
releases
This bug was fixed in the package base-files - 11ubuntu13
---
base-files (11ubuntu13) groovy; urgency=medium
* Fix handling of /e/d/motd-news.wasremoved (LP: #1895302):
- d/postinst.in: check if ubuntu-server is installed before creating
the .wasremoved file
-
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/390863
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/390864
** Merge proposal linked:
** Description changed:
[Impact]
A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
[Impact]
A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
[Impact]
A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
[Impact]
A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
[Impact]
- A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
[Impact]
A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
[Impact]
+ A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
+ [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
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/390766
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895302
Title:
groovy
Nor the upgrade after that, ugh. Fixing.
** Changed in: base-files (Ubuntu)
Importance: Undecided => High
** Changed in: base-files (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: base-files (Ubuntu)
Status: New => In Progress
--
You received this
I think this postinst bit never considered the fresh install case:
# special case of having /etc/default/motd-news removed by hand
# signal the motd-news-config package that this happened, so that
# it does not put back the file with default contents which would
# re-enable motd-news
16 matches
Mail list logo
