[DRE-maint] Bug#977701: gitlab: Missing assets, breaking some functionalities
Dave
dave at dotslashplay.it
Sun Jan 10 18:43:11 GMT 2021
On Sat, 19 Dec 2020 07:03:18 +0100 Antoine Le Gonidec <debian+bugs at dotslashplay.it> wrote:
> Package: gitlab
> Version: 13.4.7-2~fto10+1
> Severity: important
>
> On a Debian Buster using the buster-fasttracks, the update from 13.4.7-1~fto10+1 to 13.4.7-2~fto10+1 included some changes in the assets generation process, that broke some parts of the JavaScript interactions with GitLab.
>
> Two examples allowing to observe this issue:
> - From a merge request edition form, the target branch can not be changed
> - From the list of merge requests in a user dashboard, the top right green menu supposed to allow the creation of a new merge request show an ininfinite spinning animation instead
>
> I suspect this is related to a 404 error I get when trying to fetch /assets/webpack/components/app.vue
> There is indeed no such file generated in /usr/share/gitlab/public
>
> Reverting the gitlab package to 13.4.7-1~fto10+1 did not fix the issue. I have yet to try a full update of the update I did that included this package, here are the details according to APT history:
>
> Start-Date: 2020-12-18 22:00:20
> Commandline: apt install gitlab node-autosize/buster-backports fonts-font-awesome/buster-backports node-uuid/buster-backports node-request/buster-backports
> Install: fonts-katex:amd64 (0.10.2+dfsg-4~bpo10+1, automatic), node-match-at:amd64 (0.1.1-1, automatic), katex:amd64 (0.10.2+dfsg-4~bpo10+1, automatic), libjs-katex:amd64 (0.10.2+dfsg-4~bpo10+1, automatic), node-mermaid:amd64 (8.7.0+ds+~cs27.17.17-2~bpo10+1, automatic)
> Upgrade: fonts-font-awesome:amd64 (5.0.10+really4.7.0~dfsg-1, 5.0.10+really4.7.0~dfsg-4~bpo10+1), node-autosize:amd64 (4.0.2~dfsg1-3, 4.0.2~dfsg1-5~bpo10+1), node-request:amd64 (2.88.1-2, 2.88.1-5~bpo10+1), gitlab:amd64 (13.4.7-1~fto10+1, 13.4.7-2~fto10+1), node-uuid:amd64 (3.3.2-2, 8.3.2+~8.3.0-1~bpo10+1)
> Error: Sub-process /usr/bin/dpkg returned an error code (1)
> End-Date: 2020-12-18 22:21:04
>
> The dpkg error code is actually a recurring issue I have that does not seem to be related to the issue at hand, and is always fixed by running `dpkg --configure -a`.
>
> -- System Information:
> Debian Release: 10.7
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable'), (150, 'buster-fasttrack'), (150, 'buster-backports'), (110, 'testing'), (100, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages gitlab depends on:
> ii asciidoctor 2.0.10-2~bpo10+1
> ii bc 1.07.1-2+b1
> ii bundler 2.1.4-2~bpo10+1
> ii bzip2 1.0.6-9.2~deb10u1
> ii dbconfig-pgsql 2.0.11+deb10u1
> ii debconf [debconf-2.0] 1.5.71
> ii fonts-font-awesome [node-font-awesome] 5.0.10+really4.7.0~dfsg-4~bpo10+1
> ii gitlab-common 13.4.6+dfsg1-2~fto10+1
> ii gitlab-workhorse 8.46.0+debian-1~bpo10+1
> ii katex [node-katex] 0.10.2+dfsg-4~bpo10+1
> ii libjs-bootstrap4 [node-bootstrap] 4.3.1+dfsg2-1
> ii libjs-codemirror [node-codemirror] 5.54.0-2~bpo10+1
> ii libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3~bpo10+1
> ii libjs-popper.js [node-popper.js] 1.14.6+ds2-1
> ii libjs-uglify 2.8.29-6
> ii libruby2.7 [ruby-json] 2.7.1-3+fto10+2
> ii lsb-base 10.2019051400
> ii nginx 1.14.2-2+deb10u3
> ii nginx-full [nginx] 1.14.2-2+deb10u3
> ii node-autosize 4.0.2~dfsg1-5~bpo10+1
> ii node-axios 0.17.1+dfsg-2
> ii node-babel-loader 8.2.2-1~bpo10+1
> ii node-babel7 7.4.5+~cs7.3.8-1~bpo10+1
> ii node-brace-expansion 1.1.8-1
More information about the Pkg-ruby-extras-maintainers
mailing list