13 ms·

Will it take some time to propagate? Using the omnibus AMI on ubuntu and doing sudo apt-get update / sudo apt-get install gitlab-ce doesn't pull the update.

jobvandervoort 11y ago
It should work! I double checked and upgraded my personal instance and it works here. Did apt-get update complete succesfully? Repo is here for double checking: https://packages.gitlab.com/gitlab/gitlab-ce https://packages.gitlab.com/gitlab/gitlab-ce
- netcraft 11y ago
  It looks like everything is working properly, this is what I get if you are interested: https://gist.github.com/anonymous/4792e387f33155308ddf https://gist.github.com/anonymous/4792e387f33155308ddf
  - jobvandervoort 11y ago
    I think our package repo is not in your sources.list! To add it: `curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh https://packages.gitlab.com/install/repositories/gitlab/gitl... | sudo bash`
    - netcraft 11y ago
      I had to curl that file down and then pipe it in in a separate step, but it looks to be working. Thanks for your help!
      - sytse 11y ago
        You're welcome.
    - stephenr 11y ago
      Wow that's not terrifying advice at all. /sarcasm If you expect someone to run their own git & ci server, is it so hard to give them a couple of dot-point instructions: - create a .list file with these two lines: <blah> - add the GPG key for Apt - run aptitude/apt-get update Sure enough, you're already listed on curl|sh (http://curlpipesh.tumblr.com http://curlpipesh.tumblr.com), which also includes a link to the https://packages.gitlab.com/gitlab/gitlab-ce/install https://packages.gitlab.com/gitlab/gitlab-ce/install page which has a "manual" tab. Even with "manual" selected, you still insist that people should make a http request to your server, to generate a .list file, even though the only variables are local variables, which you send as part of the request anyway: distro ID (e.g. Debian, Ubuntu, etc) and release codename (Wheezy, Jessie, etc). The most ominous thing to me is that you send the result of `hostname -f` to your server. Even bigger WHY!?
      - sytse 11y ago
        We want to make it as easy and fast as possible to start with GitLab, hence the curl from https. But feel free to send a merge request to improve the download page with the instructions you would like to see and we can discuss. Sending the hostname is default Packagecloud.io behaviour.
        stephenr 11y ago
        > Sending the hostname is default Packagecloud.io behaviour Your own download page states: We recommend you set the name to the fqdn of the target node (the value of hostname -f on linux), but you can set it to whatever you want If your company is recommending something, shouldn't you have a good reason why?
        sytse 11y ago
        Can you link to the page where you found this? I can't find it on https://about.gitlab.com/downloads/#debian8 https://about.gitlab.com/downloads/#debian8 This seems like setup instructions for GitLab and I think it is unrelated.

jobvandervoort 11y ago

It should work! I double checked and upgraded my personal instance and it works here. Did apt-get update complete succesfully? Repo is here for double checking: https://packages.gitlab.com/gitlab/gitlab-ce https://packages.gitlab.com/gitlab/gitlab-ce

netcraft 11y ago
It looks like everything is working properly, this is what I get if you are interested: https://gist.github.com/anonymous/4792e387f33155308ddf https://gist.github.com/anonymous/4792e387f33155308ddf
- jobvandervoort 11y ago
  I think our package repo is not in your sources.list! To add it: `curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh https://packages.gitlab.com/install/repositories/gitlab/gitl... | sudo bash`
  - netcraft 11y ago
    I had to curl that file down and then pipe it in in a separate step, but it looks to be working. Thanks for your help!
    - sytse 11y ago
      You're welcome.
  - stephenr 11y ago
    Wow that's not terrifying advice at all. /sarcasm If you expect someone to run their own git & ci server, is it so hard to give them a couple of dot-point instructions: - create a .list file with these two lines: <blah> - add the GPG key for Apt - run aptitude/apt-get update Sure enough, you're already listed on curl|sh (http://curlpipesh.tumblr.com http://curlpipesh.tumblr.com), which also includes a link to the https://packages.gitlab.com/gitlab/gitlab-ce/install https://packages.gitlab.com/gitlab/gitlab-ce/install page which has a "manual" tab. Even with "manual" selected, you still insist that people should make a http request to your server, to generate a .list file, even though the only variables are local variables, which you send as part of the request anyway: distro ID (e.g. Debian, Ubuntu, etc) and release codename (Wheezy, Jessie, etc). The most ominous thing to me is that you send the result of `hostname -f` to your server. Even bigger WHY!?
    - sytse 11y ago
      We want to make it as easy and fast as possible to start with GitLab, hence the curl from https. But feel free to send a merge request to improve the download page with the instructions you would like to see and we can discuss. Sending the hostname is default Packagecloud.io behaviour.
      - stephenr 11y ago
        > Sending the hostname is default Packagecloud.io behaviour Your own download page states: We recommend you set the name to the fqdn of the target node (the value of hostname -f on linux), but you can set it to whatever you want If your company is recommending something, shouldn't you have a good reason why?
        sytse 11y ago
        Can you link to the page where you found this? I can't find it on https://about.gitlab.com/downloads/#debian8 https://about.gitlab.com/downloads/#debian8 This seems like setup instructions for GitLab and I think it is unrelated.