Skip to content

add Date field to Release file #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Conversation

AtnNn
Copy link

@AtnNn AtnNn commented Dec 7, 2015

We've been using freight to manage the RethinkDB apt repo, but it seems to be incompatible with the newest version of apt. This simple patch seems to fix the issue.

Originally reported here rethinkdb/rethinkdb#5174:

With the new release of apt-1.1, the apt repositories at http://download.rethinkdb.com/apt/ are failing to update..

$ apt update
...
W: Failed to fetch http://download.rethinkdb.com/apt/dists/stretch/Release  Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/download.rethinkdb.com_apt_dists_stretch_Release
E: Some index files failed to download. They have been ignored, or old ones used instead.

@mmoll
Copy link

mmoll commented Dec 15, 2015

@rcrowley any opinion on that? As Debian/stretch and Ubuntu/xenial use apt 1.1.x now, this is starting to hit more and more people...

@stahnma
Copy link

stahnma commented Dec 16, 2015

Does having date in there just end up as noop for older versions of apt?

@AtnNn
Copy link
Author

AtnNn commented Dec 16, 2015

@stahnma I believe so. There's a Date field here: http://ftp.ca.debian.org/debian/dists/oldoldstable/Release

@mattock
Copy link

mattock commented Dec 31, 2015

We're also experiencing this exact issue. I can test the proposed fix if that helps get a fixed release out.

We've also received reports of similar, but different issue, which I reported here: #66.

@mattock
Copy link

mattock commented Mar 10, 2016

As already mentioned in issue #70, there's a maintained fork of freight here. We've just made the first release (0.3.6).

@danielmewes
Copy link

It looks like this is fixed in the new repository https://github.com/freight-team/freight/blob/master/lib/freight/apt.sh#L176 . Should this be closed?

@AtnNn AtnNn closed this Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants