| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
VirtualBox is now imported and subsequent fetches shouldn't take
nearly as long. Therefore the timeout can be set back to 2 hours.
This reverts commit 0545234fd11d303be0410c101e9671fc2f806eb5.
|
|
|
|
|
|
|
|
|
|
| |
The virtualbox svn lorry is having a little trouble bootstrapping.
The logs indicate the issue could be the `git svn fetch` task is
timing out. This is because the timeout is currently set to 2 hours,
but the task appears to take in the region of 10 hours to complete.
This change increases the timeout to 16 hours from 2 hours.
This ought to be ample time to complete the inital fetch of VirtualBox.
|
|
|
|
|
|
|
|
| |
This change introduces a lorry file for mirroring the upstream virtualbox sources.
Virtualbox is a massive codebase which takes a long time to clone.
The fact it uses SVN makes it yet more cumbersome to deal with from a developer perspective.
By providing a git mirror, we make the sources easier to consume and hack upon.
|
| |
|
|
|
| |
This reverts commit 924322a8cff67c75fb4a489b5926c765375c0d21
|
|
|
|
|
|
|
|
| |
The fpc mirror stopped updating in 2017, apparently because git-svn
doesn't follow redirections. The current timeout of 7200 seconds (= 2
hours) is not long enough for Lorry to catch up. Change it to 28800
seconds (= 8 hours) which I estimate will be long enough to do so.
We can change this back later.
|
|
|
|
|
| |
pexpect's git repository was already mirrored as
python-packages/pexpect so we don't need pexpect-git.
|
|
|
|
|
|
|
|
|
| |
nohands hasn't been updated since 2010, so it's very unlikely to be
updated and it won't be usable with current Bluez. The current mirror
on git.baserock.org also can't be updated as some of the git-svn
metadata has been lost (maybe due to CodethinkLabs/lorry/lorry#8).
Mark it as obsolete, in preparation for disabling it.
|
|
|
|
|
| |
The 'compile' branch no longer exists upstream, so Lorry fails to
push it to the public mirror.
|
|
|
|
|
|
| |
Some branches outside of refs/heads/wip have been rebased in the
upstream Git repository, and Lorry fails to push them to the public
mirror. Add refspecs to enable force-pushing all branches.
|
|
|
|
|
|
| |
Some branches outside of refs/heads/wip have been rebased in the
upstream Git repository, and Lorry fails to push them to the public
mirror. Change the refspecs to enable force-pushing all branches.
|
|
|
|
|
|
| |
Some branches outside of refs/heads/wip have been rebased in the
upstream Git repository, and Lorry fails to push them to the public
mirror. Change the refspecs to enable force-pushing all branches.
|
|
|
|
|
| |
The 'snap' branch no longer exists upstream, so Lorry fails to push it
to the public mirror.
|
|
|
|
|
|
| |
All of these have changed version control system or otherwise become
obsolete. Their descriptions have already been set to mark them as
such.
|
|
|
|
|
| |
HTTP is unauthenticated and so subject to man-in-the-middle attacks.
Use https for these.
|
|
|
|
|
| |
HTTP is unauthenticated and so subject to man-in-the-middle attacks.
Use https for these.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
The documented HTTP path for git access on this server doesn't work,
so use cgit's smart HTTP support.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The svn native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for this.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these. Also change
git.0pointer.de to git.0pointer.net, which is its canonical hostname
and the only name in the TLS certificate.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
|
| |
HTTP is unauthenticated and so subject to man-in-the-middle attacks.
Use the deb.debian.org CDN and https for these. (Other mirrors
generally don't support https.)
|
|
|
|
|
|
| |
HTTP is unauthenticated and so subject to man-in-the-middle attacks.
Use https for these. Also use the canonical hostname
cpan.metacpan.org.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
| |
HTTP and the git native protocol are unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these. Also change the
hostname from git.qemu-project.org to the canonical git.qemu.org.
|
|
|
|
|
|
|
|
| |
HTTP and the git and svn native protocols are unauthenticated and so
subject to man-in-the-middle attacks. Use https for these.
Unfortunately we can't do this for Mercurial repositories, as the https
service for them currently requires authentication.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
| |
HTTP and the git native protocol are unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|
|
|
|
|
| |
The git native protocol is unauthenticated and so subject to
man-in-the-middle attacks. Use https for these.
|