You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
our developers are using yarn for their daily business and it is standard to mirror remote repositories to minimize traffic and ensure offline availability.
For normal Debian repositories we are using apt-mirror. Those are our connectionstrings:
# cat /etc/apt/mirror.list
[...]
deb-amd64 http://dl.yarnpkg.com/debian/ stable main
deb-i386 http://dl.yarnpkg.com/debian/ stable main
[...]
Unfortunately apt-get on our desktop clients reports missing all-binaries.
# apt-get update
[...]
E: Fehlschlag beim Holen von http://internalmirror.fqdn.de/mirror/dl.yarnpkg.com/debian/dists/stable/main/binary-all/Packages 404 Not Found
[...]
This behavior is already known from other repositories mirrored by us. In those cases we use rsync. But dl.yarnpkg.com does not offer rsync for mirroring. So thats exactly what I ask for. Could you offer rsync for syncing?
Thanks in advance,
Erik
The text was updated successfully, but these errors were encountered:
And then periodically run git pull to get the latest changes.
Also for what it's worth, I'm using apt-cacher-ng and don't have any issues with hitting the Yarn repo. I have apt-cacher-ng configured as a proxy server.
Uh oh!
There was an error while loading. Please reload this page.
Hi guys,
our developers are using yarn for their daily business and it is standard to mirror remote repositories to minimize traffic and ensure offline availability.
For normal Debian repositories we are using apt-mirror. Those are our connectionstrings:
Unfortunately apt-get on our desktop clients reports missing all-binaries.
This behavior is already known from other repositories mirrored by us. In those cases we use rsync. But dl.yarnpkg.com does not offer rsync for mirroring. So thats exactly what I ask for. Could you offer rsync for syncing?
Thanks in advance,
Erik
The text was updated successfully, but these errors were encountered: