Control: fixed -1 13.4.6-1 On 2020, ഡിസംബർ 3 4:26:15 AM IST, Carlos Pasqualini <pasquali...@fcal.uner.edu.ar> wrote: >Package: gitlab >Version: 13.3.9-1 >Severity: important > >Dear Maintainer, > >I am unable to install latest gitlab from unstable. Is there any >workaround to get this working? > > * What led up to the situation? > The server was working on buster, and updated to testing (another > service on same server) broke gitlab. > Trying to upgrade to a new (working) version. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > Try to install latest gitlab from unstable: > ># LANG=C apt -t unstable install gitlab >Reading package lists... Done >Building dependency tree >Reading state information... Done >gitlab is already the newest version (13.3.9-1). >The following package was automatically installed and is no longer required: > libgumbo1 >Use 'apt autoremove' to remove it. >0 upgraded, 0 newly installed, 0 to remove and 104 not upgraded. >1 not fully installed or removed. >After this operation, 0 B of additional disk space will be used. >Do you want to continue? [Y/n] >Setting up gitlab (13.3.9-1) ... >fatal: not a git repository (or any of the parent directories): .git >fatal: not a git repository (or any of the parent directories): .git >Could not find gem 'faraday (~> 0.12)' in any of the gem sources listed in >your Gemfile.
You need to install gitlab 13.4.6 from experimental. It will be uploaded to unstable soon. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.