(CC initramfs-tools@packages, context is flash-kernel invocation not
being deferred via triggers during upgrade and ultimately running
several times in a dist-upgrade)
On Sat, 2015-04-04 at 10:49 +0100, Ian Campbell wrote:
At first glance it seems like invocations via the initramfs-tools hooks
On Sat, 2015-04-04 at 14:13 +0200,
debbug.jessie.upgradereport.nospam@sub.noloop.net wrote:
On Sat, Apr 04, 2015 at 10:52:35 +0100, Ian Campbell wrote:
On Thu, 2015-04-02 at 13:04 +0200, reportbug wrote:
** error: apt-get dist-upgrade broke during a flash-kernel
This happened on
Hello,
With regard to:
** odd entry in dmesg: alg: hash: Test 3 failed for mv-sha1
dmesg reveals some slightly concerning messages:
[ 35.120866] alg: hash: Test 3 failed for mv-sha1
[ 35.120895] : 10 bf d7 00 71 0b bb 83 3a 26 d0 97 13 05 99 f5
[ 35.120910] 0010: 3a 92 53 3c
On Thu, 2015-04-02 at 13:04 +0200, reportbug wrote:
** error: apt-get dist-upgrade broke during a flash-kernel
This happened on the two QNAP TS-419P+ devices but not on the QNAP
TS-219P II Turbo device. The apt-get dist-upgrade stage aborted in
a flash-kernel trigger that failed, because
Package: upgrade-reports
Severity: important
Hello, I performed a wheezy-jessie upgrade on 3 different armel
devices yesterday.
Here are a few notes about some speed bumps that cropped up.
The devices in question are:
* Two QNAP TS-419P+ Turbo devices
* One QNAP TS-219P II Turbo device
I
5 matches
Mail list logo
