Coder Social home page Coder Social logo

ustclug / mirrorhelp Goto Github PK

View Code? Open in Web Editor NEW
431.0 28.0 141.0 11.44 MB

Documents about how to use repos on mirrors.ustc.edu.cn.

Home Page: https://mirrors.ustc.edu.cn/help/

License: Other

Makefile 8.00% Python 88.80% HTML 3.20%
mirror documentation hacktoberfest

mirrorhelp's People

Contributors

allanzyne avatar berlin2123 avatar bobby285271 avatar cloudfstrife avatar cuihaoleo avatar fz0000 avatar gaoyifan avatar gloit042 avatar hmsjy2017 avatar hosiet avatar ibug avatar jyhi avatar knight42 avatar ksqsf avatar l2dy avatar liyishuai avatar lovenemesis avatar lwintermelon avatar nicball avatar red54 avatar rewqazxv avatar taoky avatar volltin avatar xuehaipan avatar yangxuan8282 avatar yewq avatar ykla avatar yuanyiwei avatar zaoqi avatar zhsj avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mirrorhelp's Issues

Fedora 帮助文档两处问题

  1. Fedora 33中的baseurl 是 http://download.example/pub/fedora/linux是这样的形式,比如 /etc/yum.repos.d/fedora-updates.repo的内容
[updates]
name=Fedora $releasever - $basearch - Updates
#baseurl=http://download.example/pub/fedora/linux/updates/$releasever/Everything/$basearch/
metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releasever&arch=$basearch

所以目前sed的匹配模式不符合

sudo sed -e 's|^metalink=|#metalink=|g' \
         -e 's|^#baseurl=http://download.fedoraproject.org/pub/fedora/linux|baseurl=https://mirrors.ustc.edu.cn/fedora|g' \
         -i.bak \
         /etc/yum.repos.d/fedora.repo \
         /etc/yum.repos.d/fedora-modular.repo \
         /etc/yum.repos.d/fedora-updates.repo \
         /etc/yum.repos.d/fedora-updates-modular.repo
  1. USTC LUG的Fedora源没有updates-modular-source,即https://mirrors.ustc.edu.cn/fedora/updates/$releasever/Modular/SRPMS/无效

考虑关闭travis-ci对PR的触发

由于环境变量中包含同步密码,如果将.travis.yml改为类似:

script:
    - echo $RSYNC_PASSWORD

则会直接将同步密码打印在日志中,存在较大的安全隐患。

@zhsj 是否考虑关掉对PR的触发?

`Homebrew Bottles 源使用帮助` 疑问

  1. homebrew/homebrew-core写法是否错误?homebrew-core不应该在homebrew-bottles里的。
    From: http://mirrors.ustc.edu.cn/help/homebrew-bottles.html
    homebrew-core是否应该是这个? http://mirrors.ustc.edu.cn/help/homebrew-core.git.html

  2. 收录仓库 更新
    另外,这个https://mirrors.ustc.edu.cn/homebrew-bottles/bottles/ 文件太多打不开,不确定收录仓库是否准确,可否更新收录仓库列表或者打开https预览?

收录仓库
homebrew/homebrew-core
homebrew/homebrew-dupes
homebrew/homebrew-php
homebrew/homebrew-science
homebrew/homebrew-nginx
homebrew/homebrew-apache
homebrew/homebrew-portable

HOMEBREW_BREW_GIT_REMOTE 不能解决 brew 首次安装慢的问题

hello,我这边通过设置 HOMEBREW_BREW_GIT_REMOTE 变量,首次安装时,并不能从 https://mirrors.ustc.edu.cn/brew.git 镜像地址 clone。我看执行过程的提示,依然是从 https://github.com/Homebrew/brew 地址 clone。HOMEBREW_BREW_GIT_REMOTE 只是在下载完毕后,执行 brew.sh 的时候生效,并将远程仓库地址修改为 https://mirrors.ustc.edu.cn/brew.git(后面使用 brew update 可以正常使用 ustc 的源)。所以个人认为使用 HOMEBREW_BREW_GIT_REMOTE 并不能解决首次安装慢的问题。

下面是我安装的代码。
HOMEBREW_BREW_GIT_REMOTE=https://mirrors.ustc.edu.cn/brew.git HOMEBREW_CORE_GIT_REMOTE=https://mirrors.ustc.edu.cn/homebrew-core.git bash install.sh

本人还是小白一枚,如有不对还请多多指正。

最近从学校的源更新anaconda会出错

有两个包更新不了,换了官方的源(https://repo.anaconda.com/pkgs/free/),才更新成功。不知道是哪里出了问题。

Downloading and Extracting Packages
icc_rt-2019.0.0 | 9.4 MB | | 0%
conda-4.5.12 | 1.1 MB | | 0%

CondaHTTPError: HTTP 404 NOT FOUND for url https://mirrors.ustc.edu.cn/anaconda/pkgs/main/win-64/icc_rt-2019.0.0-h0cc432a_1.tar.bz2
Elapsed: 00:00.147089

An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.

CondaHTTPError: HTTP 404 NOT FOUND for url https://mirrors.ustc.edu.cn/anaconda/pkgs/main/win-64/conda-4.5.12-py37_0.tar.bz2
Elapsed: 00:00.099316

An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.

Unable to access to the rust crates repository

The attempting of creating connection to the "crates.mirrors.ustc.edu.cn" is refused.

Here is the output messages for cargo build --verbose

    Updating registry `git://crates.mirrors.ustc.edu.cn/index`
warning: spurious network error (2 tries remaining): [2/-1] Failed to connect to crates.mirrors.ustc.edu.cn: No route to host
warning: spurious network error (1 tries remaining): [2/-1] Failed to connect to crates.mirrors.ustc.edu.cn: No route to host
error: failed to load source for a dependency on `rand`

Caused by:
  Unable to update registry https://github.com/rust-lang/crates.io-index

Caused by:
  failed to update replaced source `registry https://github.com/rust-lang/crates.io-index`

Caused by:
  failed to fetch `git://crates.mirrors.ustc.edu.cn/index`

Caused by:
  [2/-1] Failed to connect to crates.mirrors.ustc.edu.cn: No route to host

Git access to crates.mirrors.ustc.edu.cn is also refused.

> git clone git://crates.mirrors.ustc.edu.cn/index
Cloning into 'index'...
fatal: unable to connect to crates.mirrors.ustc.edu.cn:
crates.mirrors.ustc.edu.cn[0: 202.141.160.110]: errno=Connection refused
crates.mirrors.ustc.edu.cn[1: 2001:da8:d800:931::153]: errno=No route to host
crates.mirrors.ustc.edu.cn[2: 2001:da8:d800:95::110]: errno=No route to host

Configuration:

  • cargo: cargo 0.13.0 (eca9e15 2016-11-01)
  • rust: rustc 1.13.0
  • git: git version 2.10.2
  • os: Darwin XXXX-MBP 16.1.0 Darwin Kernel Version 16.1.0: Thu Oct 13 21:26:57 PDT 2016; root:xnu-3789.21.3~60/RELEASE_X86_64 x86_64
  • ~/.cargo/config:
[source.crates-io]
registry = "https://github.com/rust-lang/crates.io-index"
replace-with = 'ustc'
[source.ustc]
registry = "git://crates.mirrors.ustc.edu.cn/index"

树莓派系统源错误

如题,apt update错误如下:

命中:1 https://mirrors.ustc.edu.cn/raspbian/raspbian stretch InRelease
忽略:2 https://mirrors.ustc.edu.cn/archive.raspberrypi.org stretch InRelease
错误:3 https://mirrors.ustc.edu.cn/archive.raspberrypi.org stretch Release
404 Not Found
正在读取软件包列表... 完成
E: 仓库 “https://mirrors.ustc.edu.cn/archive.raspberrypi.org stretch Release” 不再含有 Release 文件。
N: 无法安全地用该源进行更新,所以默认禁用该源。
N: 参见 apt-secure(8) 手册以了解仓库创建和用户配置方面的细节。
您在 /var/mail/pi 中有新邮件

Stackage源配置方法失效

setup-info这一行配置方法失败了,显示说无法解析,应当是一个对象。
我修改成了这样就成功了:

setup-info-locations:
- http://mirrors.ustc.edu.cn/stackage/stack-setup.yaml

另外,urls中的lts-build-plansnightly-build-plans则是给出了警告,说是无法识别。

snullp 大叔开发的 配置生成器 URL形式的使用规则?

建议提供微软产品的镜像源

微软现在有很多产品已经可以跨平台部署 支持各种linux发布版本,比如 sql-server 和 dot net
相信不少人已经在用这些产品

微软软件源入口:https://packages.microsoft.com

比如: centos-7 dotnet的repo文件:

[packages-microsoft-com-prod]
name=packages-microsoft-com-prod
baseurl= https://packages.microsoft.com/yumrepos/microsoft-rhel7.3-prod
enabled=1
gpgcheck=1
gpgkey=https://packages.microsoft.com/keys/microsoft.asc

比如 sqlserver 的repo文件:

[packages-microsoft-com-mssql-server]
name=packages-microsoft-com-mssql-server
baseurl=https://packages.microsoft.com/rhel/7/mssql-server/
enabled=1
gpgcheck=1
gpgkey=https://packages.microsoft.com/keys/microsoft.asc#

是否可支持BLFS包?

BLFS 页面的BLFS HTTP/FTP Sites是有ftp/http发布BLFS包的,我曾经下载过7.6的BLFS完整镜像,大小为3.75G。

Debian Multimedia镜像使用帮助页面“手动更新 deb-multimedia-keyring”需更新

Debian Multimedia镜像使用帮助

06/02/2015 :
Maybe I went too quickly to my new GPG key.
If apt-get don't find the new key, do that :
wget https://www.deb-multimedia.org/pool/main/d/deb-multimedia-keyring/deb-multimedia-keyring_2015.6.1_all.deb
sudo dpkg -i deb-multimedia-keyring_2015.6.1_all.deb
apt-get update
apt-get should be happy now.

这一部分,现在Multimedia官网deb-multimedia-keyring已经更新了,需要改为deb-multimedia-keyring_2016.8.1_all.deb

更新时使用PR?

我看了一下commit记录,最近我和 @knight42 添加的帮助文档都经过多处二次修改。要不我们统一通过PR更新sphinx,确认没有问题后再合并到sphinx分支?

@zhsj 你愿意成为主要审核者吗?

error: failed to run custom build command for `onig_sys v69.2.0`

Problem

error: failed to run custom build command for `onig_sys v69.2.0`

Caused by:
  process didn't exit successfully: `/tmp/cargo-installHUeMVH/release/build/onig_sys-adaa23e8f89af810/build-script-build` (exit code: 101)
--- stdout
cargo:warning=couldn't execute `llvm-config --prefix` (error: No such file or directory (os error 2))
cargo:warning=set the LLVM_CONFIG_PATH environment variable to a valid `llvm-config` executable

--- stderr
thread 'main' panicked at 'Unable to find libclang: "couldn\'t find any valid shared libraries matching: [\'libclang.so\', \'libclang-*.so\', \'libclang.so.*\'], set the `LIBCLAN a path where one of these files can be found (invalid: [])"', src/libcore/result.rs:1165:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

warning: build failed, waiting for other jobs to finish...
error: failed to compile `bat v0.12.1`, intermediate artifacts can be found at `/tmp/cargo-installHUeMVH`

Caused by:
  build failed

Steps

[root@docker opt]# cat Dockerfile 
FROM rust:latest
MAINTAINER [email protected]
RUN cargo -V  && cargo install bat
[root@docker opt]# docker build -t lgd/rust:latest -f Dockerfile .

Notes

Output of cargo version:

cargo 1.40.0 (bc8e4c8be 2019-11-22)

can you help me ? please

Docker-CE的使用说明文档有误

文档中讲,只要把 官方安装过程中的
download.docker.com 改为 mirrors.ustc.edu.cn/docker-ce
这个不是关键

官方的安装过程是从download.docker.com下载repo文件,而mirrors.ustc.edu.cn/docker-ce是从官方同步过来的,repo文件内容是一样的,不论我从哪边下载这个repo文件,其实没区别

repo文件下载下来后,里面的baseurl还是官方路径download.docker.com,而这个应该为mirrors.ustc.edu.cn/docker-ce

所以帮助文档应该改成,将下载下来的repo中的url替换,而不是把官方安装手册中的url替换

或者请提供 类似 epel帮助文档中的 sed命令,多谢

dockerhub 源不能用?

dockerhub 的源到底是哪一个:
https://docker.mirrors.ustc.edu.cn/ 还是 https://mirrors.ustc.edu.cn/dockerhub/

最近这两个似乎都不能用了?

404?

我想问一下,按照文档提示
我设置了pacman.conf而且是添加,但是貌似没用,生成了pacman -Sy archlinux-keyring,全部404了

镜像分类

目前LUG wiki上分类为:

  • 反向代理
  • 桌面环境镜像
  • 语言镜像
  • 软件镜像
  • Git 仓库镜像
  • 发行版镜像
  1. 考虑到桌面环境镜像只有KDE和gnome两个仓库,建议取消这个大类,建议并入”软件仓库“。
  2. “反向代理”与修饰语(如“语言”,“发行版”)不是同一类属性,不宜放在同一个分类层级下。如:crates.io既属于反向代理,也属于语言镜像,无法做单一划分。建议取消“反向代理”分类。另一个原因是,用户在找帮助时,并不清楚这个仓库是完整镜像还是反向代理,因此“反向代理”分类对用户查找仓库而言并没有什么帮助。
  3. 建议删除“git仓库镜像”分类,理由与取消“反向代理”类似。“git”描述的是仓库的管理工具,而“发行版“,”语言“ 描述的是仓库的内容。不宜放在一起描述。

分类方法一:

  • 发行版及软件包镜像:debian, debian-cd, ubuntu, centos, AOSP...
  • 编程语言及软件包镜像:pypi, ruby, rubygems, node, rust-static, crates.io....
  • 第三方软件包镜像(不针对特定软件): cygwin, brew.git, homebrew-bottles, macports, elrepo, epel ...
  • 软件镜像(针对特定软件):CTAN, eclipse, ros, mariadb, linux.git ...
  • 其他:fonts.gstatic.com, infinality-bundle...

大家觉得这种分类有没有什么问题? 或者某个仓库无法分类?

分类方法二:

按照类似tag的**,不做唯一性分类,给不同的镜像贴标签。比如可以检索既与”树莓派“相关,也与"发行版”相关的仓库(结果是raspbian)。
不知道rst/sphinx是否方便实现? @zhsj

大家有什么想法么?

Cargo.io mirrors error

 cargo build
    Updating `https://mirrors.ustc.edu.cn/crates.io-index` index
warning: spurious network error (2 tries remaining): [28] Timeout was reached (Failed to connect to crates-io.proxy.ustclug.org port 443: Timed out)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (Failed to connect to crates-io.proxy.ustclug.org port 443: Timed out)
warning: spurious network error (2 tries remaining): [28] Timeout was reached (Failed to connect to crates-io.proxy.ustclug.org port 443: Timed out)

建议增加贡献者指南

刚刚提了个 PR,增加了 EPEL 和 MariaDB 的帮助文档。由于没接触过 SphinxreStructureText ,很是费了一番功夫。

希望提供一份贡献者指南,以帮助初学者快速入门,并保证文档风格的统一。

建议包含以下内容:

  • 如何在本地预览文档(环境要求,安装依赖)
  • 如何添加一个新文档(文件位置、名称,添加后要相应修改哪些地方)
  • 帮助文档的结构(需包含那些部分)
  • 统一风格,比如
    • 各级标题分别使用哪种标识符(= - ` : ' " ~ ^ _ * + # < >),长度多少(目前很多 "WARNING: Title underline too short")
    • Code block 的标识符(::)是单独写在一行,还是写在前一句的末尾?偏爱前者,以免在中文中混入英文冒号
    • 支持多个发行版、同一发行版的多个版本的源,“使用说明”一节是列出所有组合下的配置文件内容,还是提供命令修改默认的配置文件(比如我提的 PR 中对 EPEL 的处理),亦或说明一下原理,让用户自己手动处理?
    • “相关链接”一节使用 Field List,还是无序列表并且使用 Embedded URL 形式不直接显示链接地址。偏爱后者,以免标题、链接过长时分行显示,不美观

这个Rust crate源响应的有问题!

使用官方配置:

[source.crates-io]
replace-with = 'ustc'
[source.ustc]
registry = "git://mirrors.ustc.edu.cn/crates.io-index"
$ cargo build
Screenshot from 2019-10-02 17-50-42

使用github源:

[source.crates-io]
registry = "https://github.com/rust-lang/crates.io-index"
$ cargo build
Screenshot from 2019-10-02 17-51-02

OS:ubuntu 18.04
Cargo version: 1.38.0-nightly
还是国内源的速度快,github可以下载但速度还是比较慢的,希望官方能修复下这个问题。

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.