Bug#977701: gitlab: Missing assets, breaking some functionalities

[Antoine Le Gonidec]

On Sat, 19 Dec 2020 07:03:18 +0100 Antoine Le Gonidec 
<debian+b...@dotslashplay.it> wrote:

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

End-Date: 2020-12-18  22:21:04

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)

Reverting this update did not fix the issue, I ended up restoring a server 
backup prior to it.

This update is the only difference I can see between the restored backup and 
the situation triggering the JavaScript-related issues, so I guess it applies 
some change than is not reverted by going back to the previous package versions.

OpenPGP_signature
Description: OpenPGP digital signature