Upgraded Apt requests the InRelease file

[adamar]

Hi,

A new version of Apt appears to be looking for the InRelease file in the freight repo.

Reading package lists...
E: Failed to fetch InRelease
E: Some index files failed to download. They have been ignored, or old ones used instead.
Ran apt-get update returned 100

I've created a basic example PR as a guide for what I believe the PGP command should be.

[mmoll]

@adamar which APT version are you referring to? I'm using 1.6~beta1 and don't see such messages with my frieght generated repository...

[miroR]

$ apt --version
apt 1.6~beta1 (amd64)
$

as I'm running unstable Devuan Ceres (is made from unstable Debian or so).
And ir was when I tried to apt-get update that I saw that message.

Details (ample for clarity):
Get:42 tor+https://pkgmaster.devuan.org/merged testing-security/main amd64 Packages [341 kB]
Get:43 tor+https://pkgmaster.devuan.org/merged testing-updates/main amd64 Packages [9,064 B]
Get:44 tor+https://packages.devuan.org/merged ceres/contrib amd64 Packages [61.9 kB]
Get:45 tor+https://packages.devuan.org/merged ceres/non-free amd64 Packages [82.3 kB]
Get:46 tor+https://pkgmaster.devuan.org/merged jessie-proposed-updates/main amd64 Packages [160 kB]
Get:47 tor+https://pkgmaster.devuan.org/merged jessie-security/main amd64 Packages [468 kB]
Get:48 tor+https://pkgmaster.devuan.org/merged jessie-updates/main amd64 Packages [20.6 kB]
Fetched 28.5 MB in 30s (949 kB/s)
Reading package lists...

[...]

E: Failed to fetch https://www.CroatiaFidelis.hr/foss/dev1miro/dists/ceres/InRelease  
E: Some index files failed to download. They have been ignored, or old ones used instead.

I created it myself manually, and it is now possible (although, I'm afraid, must partly be done manually, but that's so for other reasons) to:
apt-get install palemoon
or
apt-get source palemoon
as I explained in:
A repo serving Pale Moon
https://dev1galaxy.org/viewtopic.php?id=1972

[miroR]

Just a digression if it is allowed, and since I posted about this exact non-created at this time by Freight InRelease. That repo I was only able to put together to successfully serve both binary-amd64 and sources after I:

• created separately the binary package by freight add'ing it and freight cache'ing on it
• cp'ing that freight repo manually for later manipulation
• starting anew to freight add the sources and and freight cache on them
• mixing, with understanding, the two
• posting the result, that is currently available at:
  https://www.croatiafidelis.hr/foss/dev1miro/

Freight 0.3.11 (was capable of adding) but wasn't capable of 'freight cache' creating both my binary and the sources of my NMU palemoon package.
And also I had to hack apt.sh to add sources... Freight 0.3.11 current apt.sh couldn't do that... Give me time to show it in my forked Freight repo how I did that, and hopefully come back with a pull request...

[miroR]

My first today's post was all correct, but the missing non-created by Freight InRelease of my dev1miro repo is better visible in (after more fiddling with it) the log after that one posted:

Hit:9 tor+https://pkgmaster.devuan.org/merged ceres InRelease
Hit:10 tor+https://pkgmaster.devuan.org/devuan sid InRelease

[...]

Hit:18 tor+https://pkgmaster.devuan.org/merged jessie InRelease
Hit:19 tor+https://pkgmaster.devuan.org/merged jessie-backports InRelease
Hit:20 tor+https://pkgmaster.devuan.org/devuan jessie-proposed InRelease
Hit:21 tor+https://pkgmaster.devuan.org/devuan jessie-proposed-backports InRelease

[...]

E: Failed to fetch https://www.CroatiaFidelis.hr/foss/dev1miro/dists/ceres/InRelease  
E: Some index files failed to download. They have been ignored, or old ones used instead.

[miroR]

Sorry about the mess. Untill I inserted newlines, the string InRelease, present in the first post (so first post was all correct completely all the time) evaded the focus of my eyeballs, and now I duplicated the information... But at least it's clearer now...

[mmoll]

@adamar @miroR could you please test GH-79?

[miroR]

I sure will! And with a real project, where I seem to be getting approval for work:
A Pale Moon repo for Devuan/Debian
https://forum.palemoon.org/viewtopic.php?f=37&t=18805
as soon as I get the pass for my mozconfig, which I hope is not much longer from now.

[miroR]

Took me a while. I can confirm that:
#79
creates InRelease file correctly for my Pale Moon newly-compiled package, binary-amd64 (not yet in the repo https://www.CroatiaFidelis.hr/foss/dev1miro/ at the time of this writing, the old is).
However, while it may do so for sources as well otherwise, for sources without '~repack' and with two '_' in their name, this other bug --which is yet to open an issue about-- (according to my testing; will provide more info if not a pull request, in another while) is preventing Freight updated with your two latest pull requests/commits from your repo, to do so.
While apt cache'ing, I get only:

# [freight] skipping invalid Debian source package palemoon_27.8.3~repack-4.dsc

and nothing whatsoever is created in /var/cache/dev1miro