Hi David, On 2021-07-29 12:58 a.m., David Wright wrote: > On Sun 25 Jul 2021 at 09:37:14 (-0400), Polyna-Maude Racicot-Summerside wrote: >>> On Sun, 25 Jul 2021, 04:41 Polyna-Maude Racicot-Summerside wrote: >>> On 2021-07-24 9:33 p.m., David Wright wrote: >>> > On Sat 24 Jul 2021 at 19:52:36 (-0400), Polyna-Maude Racicot-Summerside wrote: >>> >> Here are the message I get after my debmirror when I do apt-get update >>> >> >>> >> Err:31 file:/mnt/mirror/debian buster-updates/main amd64 Contents (deb) >>> >> File not found - >>> >> /mnt/mirror/debian/dists/buster-updates/main/Contents-amd64 (2: No such >>> >> file or directory) >>> >> Reading package lists... Done >>> >> E: Failed to fetch >>> >> file:/mnt/mirror/debian/dists/buster/main/Contents-amd64 File not found >>> >> - /mnt/mirror/debian/dists/buster/main/Contents-amd64 (2: No such file >>> >> or directory) >>> >> E: Failed to fetch >>> >> file:/mnt/mirror/debian/dists/buster-updates/main/Contents-amd64 File >>> >> not found - /mnt/mirror/debian/dists/buster-updates/main/Contents-amd64 >>> >> (2: No such file or directory) >>> >> >>> >> The command I used for creating the mirror is >>> >> >>> >> debmirror --all --progress --verbose --method=http >>> >> --dist=buster,buster-updates,buster-backports >>> >> --section=main,contrib,non-free --arch=amd64,i386 --rsync-extra=none >>> >> --source --i18n --keyring /usr/share/keyrings/debian-archive-keyring.gpg >>> >> --root=debian --host=debian.mirror.iweb.ca <http://debian.mirror.iweb.ca> /mnt/mirror/debian >>> >> >>> >> Got idea ? >>> > >>> > --getcontents ? >>> > >>> Giving this one a try.... >>> >> I'm not sure you have close to a clue what my problem is. >> Because when I simply change my repository to the usual Debian one, I >> can do my apt cache update properly. > > and then > > On Mon 26 Jul 2021 at 01:12:14 (-0400), Polyna-Maude Racicot-Summerside wrote: >>>>> >>>>> --getcontents ? >>>>> >>>> Giving this one a try.... >>>> >>>> >>> Gave this one a try and it worked. > > Difficult to keep up. > Difficult to keep up ? I'll give you a hint... --getcontents = option for debmirror And maybe I shall have only sent this message to the person who told me to try --getcontents. Only wanted to say thanks for the help. >>> Next step... >>> I'm setting up a Debian mirror (don't know if it will be very useful >>> because I already have one nearby (iweb.ca)... >>> >>> But as I'm only carrying Buster and Bullseye (possibly the next testing >>> too). >>> >> With only the security update mirror. >> Please don't write me (again) it's bad to create a local copy of >> security-update. >> >> Now getting this problem : >> >> E: The repository 'file:/mnt/mirror/security-debian buster/updates >> Release' does not have a Release file. >> N: Updating from such a repository can't be done securely, and is >> therefore disabled by default. > > Just copy the files *Release* from the website with wget? > (In no way condoning what you are attempting to do.) > Yes, just copy the *Release* file. But doing things like trained monkey doesn't go nowhere. There's a reason why it did work for the debian.org repository and not the security updates. First thing is understanding why, so that the choice I'll make will be based on fact to support them. Not based on "this seem like working". And it's related to the way the repository is maintained. So I went with using aptly to create a local repository, that I sign with my own key. This way, I keep it secure. One reason it is recommended not to make local copy of security-updates is because the repository is not signed. So it would be easy to compromise. As a fact, the Release file ain't present itself. But by making my own repository for security update and signing, I did get a safe local copy. > Cheers, > David. > -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature