summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Lorry Controller: increase timeout to 3 daysHEADrobjh/increase-timeoutmasterRobert J. Heywood2020-10-051-1/+1
| | | | | | | | Although running the `git svn fetch` command locally only took 12 hours, the lorry service appears to only get about half way through all of the revisions. This change drastically increases the time out to 3 days.
* Update url for urlgrabberBen Brown2020-10-031-1/+1
| | | | Project moved from yum source repositories to github.
* Lorry Controller: increase timeout to 16 hours.Rob J. Heywood2020-10-021-1/+1
| | | | | | | | | | 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.
* VirtualBox-svn: addedrobjh/add-vboxRobert J. Heywood2020-10-011-0/+7
| | | | | | | | 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.
* Lorry file from git repositoryFrancisco Redondo Marchena2020-09-252-0/+7
|
* Revert "Temporarily increase lorry-timeout to allow updating fpc mirror"revert-924322a8Ben Brown2020-09-171-1/+1
| | | This reverts commit 924322a8cff67c75fb4a489b5926c765375c0d21
* Temporarily increase lorry-timeout to allow updating fpc mirrorbwh/misc-fixesBen Hutchings2020-09-161-1/+1
| | | | | | | | 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.
* Delete duplicate pexpect mirrorBen Hutchings2020-09-161-6/+0
| | | | | pexpect's git repository was already mirrored as python-packages/pexpect so we don't need pexpect-git.
* Mark nohands as obsoleteBen Hutchings2020-09-161-1/+2
| | | | | | | | | 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.
* Update refspecs for Perlbwh/fix-refspecsBen Hutchings2020-09-141-1/+1
| | | | | The 'compile' branch no longer exists upstream, so Lorry fails to push it to the public mirror.
* Enable force-pushing all branches for HaskellBen Hutchings2020-09-141-1/+5
| | | | | | 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.
* Enable force-pushing all branches for GTKBen Hutchings2020-09-141-2/+1
| | | | | | 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.
* Enable force-pushing all branches for GLibBen Hutchings2020-09-141-2/+1
| | | | | | 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.
* Update refspecs for GitBen Hutchings2020-09-141-1/+1
| | | | | The 'snap' branch no longer exists upstream, so Lorry fails to push it to the public mirror.
* Disable various obsolete mirrorsbwh/disable-obsoleteBen Hutchings2020-09-1187-366/+430
| | | | | | All of these have changed version control system or otherwise become obsolete. Their descriptions have already been set to mark them as such.
* Use https: scheme instead of http: for various archivesbwh/use-httpsBen Hutchings2020-09-1152-53/+53
| | | | | HTTP is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme instead of http: for various repositoriesBen Hutchings2020-09-1111-16/+16
| | | | | HTTP is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for OpenSSHBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for BusyBoxBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for gccBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for ghostpdlBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for gdbmBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for moreutilsBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for muslBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for bareboxBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for PostgreSQLBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for cgitBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for pppBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for FFmpegBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for hostapBen Hutchings2020-09-111-1/+1
| | | | | | | | 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.
* Use https: scheme for XenBen Hutchings2020-09-111-1/+1
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for mpfrBen Hutchings2020-09-111-1/+1
| | | | | The svn native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for this.
* Use https: scheme for all repositories on git.alsa-project.orgBen Hutchings2020-09-112-2/+2
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories on git.samba.orgBen Hutchings2020-09-112-2/+2
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories on libvirt.orgBen Hutchings2020-09-112-2/+2
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories on git.0pointer.{de,net}Ben Hutchings2020-09-114-4/+4
| | | | | | | 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.
* Use https: scheme for all repositories on gnupg.orgBen Hutchings2020-09-114-4/+4
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all files in Debian archiveBen Hutchings2020-09-112-2/+2
| | | | | | 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.)
* Use https: scheme for all files on CPANBen Hutchings2020-09-116-70/+70
| | | | | | HTTP is unauthenticated and so subject to man-in-the-middle attacks. Use https for these. Also use the canonical hostname cpan.metacpan.org.
* Use https: scheme for all repositories on git.suckless.orgBen Hutchings2020-09-111-3/+3
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories on repo.or.czBen Hutchings2020-09-113-3/+3
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories on sourceware.orgBen Hutchings2020-09-115-5/+5
| | | | | HTTP and the git native protocol are unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories on git.qemu.orgBen Hutchings2020-09-118-8/+8
| | | | | | 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.
* Use https: scheme for active Git and Subversion repositories on SourceforgeBen Hutchings2020-09-116-6/+6
| | | | | | | | 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.
* Use https: scheme for all repositories on git.netfilter.orgBen Hutchings2020-09-1110-10/+10
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories on git.openwrt.orgBen Hutchings2020-09-111-5/+5
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories hosted by PepperfishBen Hutchings2020-09-113-22/+22
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories on git.xfce.orgBen Hutchings2020-09-111-16/+16
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories on git.kernel.orgBen Hutchings2020-09-1121-21/+21
| | | | | The git native protocol is unauthenticated and so subject to man-in-the-middle attacks. Use https for these.
* Use https: scheme for all repositories on SavannahBen Hutchings2020-09-1138-38/+38
| | | | | HTTP and the git native protocol are unauthenticated and so subject to man-in-the-middle attacks. Use https for these.