[DRE-maint] Bug#919060: same problem here...

[Pirate Praveen]

On 2019, ജനുവരി 13 11:26:54 PM IST, Dragos Jarca <dragos.jarca at dynamicpuzzle.ro> wrote:
>after apt-get update and apt-get dist-upgrade...
>
>now gitlab cannot be used...

This is a different issue, please open a new bug.

>cannot upgrade to experimental to...
>
>root at omv:/usr/share/gitlab# apt-get install ruby-gitaly=1.5.0+dfsg-1 
>ruby-responders ruby-default-value-for=3.1.1-1 ruby-devise 
>ruby-doorkeeper ruby-doorkeeper-openid-connect ruby-recaptcha 
>ruby-devise-two-factor ruby-browser ruby-graphiql-rails 
>ruby-acts-as-taggable-on ruby-redis-rails ruby-asana=0.8.1-1 
>ruby-kubeclient=4.2.0-1 ruby-webpack-rails ruby-sass-rails 
>ruby-font-awesome-rails ruby-premailer-rails ruby-rails-i18n=5.1.2-1 
>ruby-peek ruby-peek-gc ruby-peek-pg ruby-peek-rblineprof
>ruby-peek-redis 
>ruby-lograge ruby-actionmailer=2:5.2.2+dfsg-1 
>ruby-actionpack=2:5.2.2+dfsg-1 ruby-actionview=2:5.2.2+dfsg-1 
>ruby-activemodel=2:5.2.2+dfsg-1 ruby-activerecord=2:5.2.2+dfsg-1 
>ruby-activesupport=2:5.2.2+dfsg-1 ruby-activestorage ruby-actioncable 
>ruby-activejob=2:5.2.2+dfsg-1 ruby-railties=2:5.2.2+dfsg-1 
>ruby-sprockets-rails ruby-rack=2.0.6-3 ruby-rails=2:5.2.2+dfsg-1 
>gitlab-common=11.6.0+dfsg-1 ruby-rails-dom-testing=2.0.3-3 
>ruby-arel=9.0.0-2 ruby-http=3.3.0-1 ruby-http-form-data=2.1.0-1 
>rails=2:5.2.2+dfsg-1 gitlab=11.6.0+dfsg-1 gitaly=1.12.0+debian-1 
>ruby-actionpack-xml-parser=2.0.1-1 redmine
>ruby-protected-attributes=1.1.4-2
>Reading package lists... Done
>Building dependency tree
>Reading state information... Done
>ruby-sprockets-rails is already the newest version (2.3.2-1).
>ruby-sprockets-rails set to manually installed.
>ruby-graphiql-rails is already the newest version (1.4.10-1).
>ruby-graphiql-rails set to manually installed.
>redmine is already the newest version (3.4.6-1).
>ruby-acts-as-taggable-on is already the newest version (5.0.0-2).
>ruby-acts-as-taggable-on set to manually installed.
>ruby-browser is already the newest version (2.5.3-1).
>ruby-browser set to manually installed.
>ruby-devise is already the newest version (4.5.0-1).
>ruby-devise set to manually installed.
>ruby-devise-two-factor is already the newest version (3.0.3-1).
>ruby-devise-two-factor set to manually installed.
>ruby-doorkeeper is already the newest version (4.4.2-1).
>ruby-doorkeeper set to manually installed.
>ruby-doorkeeper-openid-connect is already the newest version (1.5.2-1).
>ruby-doorkeeper-openid-connect set to manually installed.
>ruby-font-awesome-rails is already the newest version (4.7.0.4-1).
>ruby-font-awesome-rails set to manually installed.
>ruby-lograge is already the newest version (0.10.0-1).
>ruby-lograge set to manually installed.
>ruby-peek is already the newest version (1.0.1-1).
>ruby-peek set to manually installed.
>ruby-peek-gc is already the newest version (0.0.2-1).
>ruby-peek-gc set to manually installed.
>ruby-peek-pg is already the newest version (1.3.0-1).
>ruby-peek-pg set to manually installed.
>ruby-peek-rblineprof is already the newest version (0.2.0-1).
>ruby-peek-rblineprof set to manually installed.
>ruby-peek-redis is already the newest version (1.2.0-1).
>ruby-peek-redis set to manually installed.
>ruby-premailer-rails is already the newest version (1.9.7-1).
>ruby-premailer-rails set to manually installed.
>ruby-protected-attributes is already the newest version (1.1.4-2).
>ruby-protected-attributes set to manually installed.
>ruby-recaptcha is already the newest version (4.11.1-1).
>ruby-recaptcha set to manually installed.
>ruby-redis-rails is already the newest version (5.0.2-3).
>ruby-redis-rails set to manually installed.
>ruby-responders is already the newest version (2.4.0-3).
>ruby-responders set to manually installed.
>ruby-sass-rails is already the newest version (5.0.6-2).
>ruby-sass-rails set to manually installed.
>ruby-webpack-rails is already the newest version (0.9.11+git-1).
>ruby-webpack-rails set to manually installed.
>Some packages could not be installed. This may mean that you have
>requested an impossible situation or if you are using the unstable
>distribution that some required packages have not yet been created
>or been moved out of Incoming.
>The following information may help to resolve the situation:
>
>The following packages have unmet dependencies:
>  ruby-protected-attributes : Depends: ruby-activemodel (< 2:5.0) but 
>2:5.2.2+dfsg-1 is to be installed
>E: Unable to correct problems, you have held broken packages.
>root at omv:/usr/share/gitlab#
>
>Seems that is a incopatibility between gitlab and redmine...
>
>I try to use in production and now my team cannot commit changes.

This is because we could not get gitlab working with rails 5.2 in time for uploading rails 5.2 to unstable. Since transitions freeze was approaching, we did not have a choice to wait for gitlab, as gitlab will not be in buster anyway.

Rails 5.2 support is in progress by upstream, and as soon as it is complete we will upload it to unstable.

unstable is expected to have such temporary breakages from time to time and is not a good choice for production. I myself use stretch-backports for our gitlab instance. During buster we are hoping to provide a dedicated repo for fast moving software like gitlab, which can be used in combination with -backports.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.