Yes, it worked that way. Thank you!
For the record:
The most simple, currently working way to create a private, unsigned directory:
cd /srv/deb
apt-ftparchive packages . > Packages
apt-ftparchive release . > Release
Assuming that the document root of the HTTP server is /srv/ and deb is
the
That release file is sort of invalid, as we also need the uncompressed
Packages file hashed, because we check hashes after decompression too.
So usually you generate Packages, compress it (having both around), then
create Release file, and then delete the uncompressed Packages file if
you don't ne
I actually tried to add a Release file without signing it, because it
would be simple, only a single command:
apt-ftparchive release . > Release
But that did not work either. The apt update command exits with error:
root@pipa11:~# apt update
Hit:1 http://mirror.hk.leaseweb.net/ubuntu bionic In
I think the answer is simple: We should stop sending If-Modified-Since.
There's no advantage to sending that compared to getting back the same
release file, and it's a bad design.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
I guess that's good to know that it does not really work without a
release file now anyway, it is a good argument for removing support for
such repos completely. I made a plan a year or two ago, but have not
acted on it yet :/
Please add a Release file. It gives you download progress, hash checks,
This is a bug in 20.04 as well. I have no Release file, this is a
private, unsigned repository, only Packages.xz. On first run, apt update
first works. On the second run apt update issues a HTTP GET with an If-
Modified-Since header:
GET /deb/Packages.xz HTTP/1.1
Host: XXX
Cache-Control: max-age=0
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750625
Title:
update
I think a problem is that your Release file is missing a Date field. APT
should not be trying to redownload unmodified files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750625
Title:
update misi
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750625
Title:
update misinterprets 304 response on Packages.gz
To manage notifications about this bug go to:
https://bugs.launch
** Attachment added: "Minimal /dists folder for testing"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750625/+attachment/5059382/+files/freight.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
In trusty, this works as expected.
ii apt 1.0.1ubuntu2.1
amd64commandline package manager
ii apt-transport-https 1.0.1ubuntu2.1
amd64https download tran
Still occurring in xenial with apt 1.2.25
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750625
Title:
update misinterprets 304 response on Packages.gz
To manage notifications about this bug go to:
12 matches
Mail list logo
