Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#48254 - [deepin-wm] request to change deepin packages source location

Attached to Project: Community Packages
Opened by Kevin Mihelich (kmihelich) - Friday, 19 February 2016, 19:47 GMT
Last edited by Ivy Foster (escondida) - Thursday, 10 October 2019, 04:25 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


The git repository is wildly unreliable, or outright unreachable. They maintain a mirror of those git sources on github[1], and as a bonus, github offers the ability to download tarball snapshots of tagged releases[2].

Switching to point to github instead of their server would make building the packages far more reliable, and using the tarball snapshots would additionally speed source retrieval. Thoughts?

This task depends upon

Closed by  Ivy Foster (escondida)
Thursday, 10 October 2019, 04:25 GMT
Reason for closing:  Implemented
Additional comments about closing:  Current deepin (1.9.38) is sourced from github rather than, as requested.
Comment by Felix Yan (felixonmars) - Saturday, 20 February 2016, 06:46 GMT
I switched to use because their GitHub sync was frequently broken and new code and tags were not available in GitHub for some days after each new release.
Comment by Kevin Mihelich (kmihelich) - Saturday, 20 February 2016, 07:00 GMT
Github appeared to be in sync with all the recent changes to packages, and their servers are reliable. If works for you, you can stick with that.

This is just a request because these packages aren't building as is for Arch Linux ARM due to being basically useless, and it jams up the builders for hours until git inevitably times out. With the current sources, I'll just end up dropping the entire suite of packages since it's not worth the time and resources.
Comment by Felix Yan (felixonmars) - Saturday, 20 February 2016, 07:26 GMT
It is in sync currently, but not always. I am also building the packages in DE or FR servers, not sure why it didn't work well for you.
Comment by Kevin Mihelich (kmihelich) - Saturday, 20 February 2016, 07:58 GMT
USA for me, and even now it's not connecting for me from both here and the Netherlands. Currently, I'm showing only 48% build completion on the suite across all 4 architectures. It's no big deal, just wanted to ask before I took any actions on my side.