Re: Steps to follow to not break gitlab and diaspora when dependencies are updated

On 2016, ജൂൺ 15 11:14:35 PM IST, Antonio Terceiro wrote: >I suffered with this for a long time with rails, vagrant, and redmine, >and maybe others, and realized that it's easier to just relax the >dependencies in the metadata with a Debian-specific patch and follow up >to

Re: Steps to follow to not break gitlab and diaspora when dependencies are updated

On Wed, Jun 15, 2016 at 12:04:24PM +0530, Pirate Praveen wrote: > Hi, > > Background: recent update of ruby-addressable broke gitlab. > > https://ci.debian.net/data/packages/unstable/amd64/g/gitlab/latest-autopkgtest/log.gz > > Could not find gem 'addressable (~> 2.3.8)' in any of the gem

Re: Steps to follow to not break gitlab and diaspora when dependencies are updated

Hi, On 15-06-16 08:34, Pirate Praveen wrote: > Hi, > > Background: recent update of ruby-addressable broke gitlab. > > https://ci.debian.net/data/packages/unstable/amd64/g/gitlab/latest-autopkgtest/log.gz > > Could not find gem 'addressable (~> 2.3.8)' in any of the gem sources > listed in

Re: Steps to follow to not break gitlab and diaspora when dependencies are updated

* Pirate Praveen [160615 08:35]: > Background: recent update of ruby-addressable broke gitlab. > > https://ci.debian.net/data/packages/unstable/amd64/g/gitlab/latest-autopkgtest/log.gz > > Could not find gem 'addressable (~> 2.3.8)' in any of the gem sources > listed

Steps to follow to not break gitlab and diaspora when dependencies are updated

Hi, Background: recent update of ruby-addressable broke gitlab. https://ci.debian.net/data/packages/unstable/amd64/g/gitlab/latest-autopkgtest/log.gz Could not find gem 'addressable (~> 2.3.8)' in any of the gem sources listed in your Gemfile or available on this machine. Reason: Declaring