Bug #17427

Failure to download IUKv2 from 4.2 to 4.2.1

Added by CyrilBrulebois 2020-01-11 19:11:13 . Updated 2020-01-11 20:49:55 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Initially, I supposed this might be a mirror sync issue, that I was filing anyway since I cannot test 4.2 to 4.2.1 because of that.

But then, looking at commit:b64fcee43755d997c30e6199fdb3bb85d80c2d83, I’m only seeing sha256 fields getting updated.

So this might be a network issue instead. I’ll retry.


Subtasks


History

#1 Updated by CyrilBrulebois 2020-01-11 19:20:32

  • Status changed from Confirmed to Rejected

Fine with a different attempt, closing.

#2 Updated by intrigeri 2020-01-11 19:33:56

FWIW, I did that test this morning and it worked for me back then; the UDFs did not change since. If I understand correctly, it worked for you too when you reported Bug #17425. This suggests it’s a temporary network problem (and Feature #15875 will fix most such problems). Fingers crossed!

If you can reproduce, then I’ll need the content of the Journal (but I can also reproduce and get it myself, it’ll only take longer).

> But then, looking at commit:b64fcee43755d997c30e6199fdb3bb85d80c2d83, I’m only seeing sha256 fields getting updated.

I was surprised too! But in hindsight, it’s not that surprising that the size did not change: the only change is UID:GID, and possibly these fields have a fixed size.

FWIW, I’ve just verified that the IUKs you’ve built in https://jenkins.tails.boum.org/view/RM/job/build_IUKs/45/ have indeed the same size as the ones I’ve (re)built locally this morning.

#3 Updated by CyrilBrulebois 2020-01-11 20:49:55

Yes, I was really hoping for a network issue while downloading; but this being the first one ever, right when I’m hitting other issues and we’re wandering outside known paths, I wanted to make sure I would not forget about it.