On Tue, 09 May 2017 at 11:11:15 -0400, Ryan Kavanagh wrote:
> If I correctly interpreted the following,
> /var/log/dpkg.log.4.gz:2017-01-24 15:51:39 upgrade nodm:amd64 0.12-1.1
> 0.13-1
> I appear to be upgrading from 0.12-1.1, which was installed 2017-01-23.
I think you would have
found 861771 0.12-1.1
thanks
On Mon, May 08, 2017 at 08:14:28PM +0100, Simon McVittie wrote:
> On Wed, 03 May 2017 at 16:13:25 -0400, Ryan Kavanagh wrote:
> > nodm fails to install/upgrade.
>
> What version did you upgrade from, and how long had you had that version
> installed before upgrading?
Control: found 861771 0.13-1
Control: tags 861771 + patch
On Mon, 08 May 2017 at 20:14:28 +0100, Simon McVittie wrote:
> If you try to downgrade to 0.13-1 (in testing), do you still get this?
I can reproduce this with 0.13-1, so it should not block migration.
> I think the attached patch should
On Wed, 03 May 2017 at 16:13:25 -0400, Ryan Kavanagh wrote:
> nodm fails to install/upgrade.
What version did you upgrade from, and how long had you had that version
installed before upgrading?
If you try to downgrade to 0.13-1 (in testing), do you still get this?
If you do, please mark this bug
Package: nodm
Version: 0.13-1.2
Severity: grave
nodm fails to install/upgrade. Please see the attached output from
journalctl -xe. I marked the severity as grave because the package fails
to install/upgrade, thus rendering it unusable to (all?) users.
5 matches
Mail list logo
