"No Hash entry in Release file" failure on apt-1.1

[mattock]

We're using freight to manage our apt repositories and have recently received reports that the repos don't work on Debian Jessie or Ubuntu Trusty if apt-1.1 is installed. Here's an example error:

# apt-get -qq update
W: Failed to fetch http://swupdate.openvpn.net/apt/dists/trusty/Release  No Hash entry in
 Release file /var/lib/apt/lists/swupdate.openvpn.net_apt_dists_trusty_Release, which is
 considered strong enough
 for security purposes
E: Some index files failed to download. They have been ignored, or old ones used instead.

This issue was originally reported to our forums. We're using the latest freight release available in the freight apt repos for Ubuntu 12.04 (=0.3.5-1) Let me know if you need more information to resolve this.

[mmoll]

like #65 this needs to get implemented into freight

[mattock]

I setup a freight repo based on uwabami-freight and could not reproduce this problem on Ubuntu 16.04 alpha 1 updated to the most recent packages. The apt version on that platform is 1.1.10, which is the most recent stable release of apt, according to Git tags in https://github.com/Debian/apt.

I also tested the repo on Debian 7 which has apt 0.9.7.9 and it still worked, so there's probably no horrible regression there.

The uwabami-freight fork contains three commits of interest:

• "Add Date:, Valid-Until"
• "support debian.tar.xz"
• "Add support {,.orig,.debian}.tar.xz"

This means that it fixes the issue discussed in pull request https://github.com/rcrowley/freight/pull/65.

With stock freight 0.3.5-1 freight + Ubuntu 16.04 alpha 1 I got the same failure as shown in the previous comment ("No hash entry...").

[JulesAU]

I can confirm the same result as @mattock; the uwabami-freight fork fixes it for Debian sid and stretch.

Looks like the freight project may have been abandoned?

[mmoll]

If that should really be the case (@rcrowley?), a "canonical fork"[tm] would be very good to have.

[mattock]

I sent email to @rcrowley suggesting asking if he'd be willing to grant other people permissions to the project.

[mmoll]

Moving to an own GH organization might also be an option.

[mmoll]

regarding the original problem: which version of freight are you using? this seems to have been fixed by #52, which came in after 0.3.5 was tagged and released.

[mattock]

I was using the latest Ubuntu 12.04 package (0.3.5-1).

[mmoll]

@mattock then you definitely need the patch in #52 and uwabami/freight@08c87d9

[mattock]

There has been no response to my email sent on 8th Feb from @rcrowley . I checked if an organization called "freight" could be created, but that user/organization name has already been taken.

[mmoll]

@mattock "apt-freight" or "freight-apt" maybe?

[domcleal]

I'd like to switch the RPMs in Fedora to point at a well-maintained fork too, rather than carrying the patches above (and also #69). I'd be happy to help with maintenance.

[mattock]

@domcleal : I sent you an invite the GitHub organization called freight-team I forked the main freight repository there, and so now we need to start cherry-picking the useful patches.

@mmoll : shall I make you a team member also?

I will ask if our company could host the Debian packages for freight. Apparently the current ones have been generated with FPM.

[domcleal]

@mattock thanks, all received. It might be good to enable issues on that repo so we have somewhere to discuss things. I opened a PR for the date/valid-until fix discussed above, then we'll have to see about tidying up and cutting a release.

[mmoll]

@mattock I'd be delighted :)