Hi Andy,
Am 29.08.2015 um 02:46 schrieb Andy Valencia:
---
I do not think that there is anything else that udev can do, since the
check is done in udev.preinst.
I hope you might consider talking to the apt folks. At least under a
dist-upgrade it seems like this failure could
---
I do not think that there is anything else that udev can do, since the
check is done in udev.preinst.
I hope you might consider talking to the apt folks. At least under a
dist-upgrade it seems like this failure could be detected sooner rather
than later. It's not like udev is
Package: udev
Version: 175-7.2
Severity: serious
Justification: Policy 7.2
Dear Maintainer,
* What led up to the situation?
Upgrading my armhf system Wheezy-Jessie. Did the usual searches for
dependencies and what-not. Did a pre-download, then ran the upgrade.
About half the packages were
Control: severity 797131 minor
On Aug 28, Andy Valencia ajv-691-118-1...@vsta.org wrote:
If the kernel is not acceptable for the upgrade, it should be detected
before the upgrade starts. The kernel check should not happen after the
filesystem has been modified with some upgraded content. An
4 matches
Mail list logo
