[DRE-maint] Bug#983924: GitLab 13.7.7: ERROR in <ttf-font-file> 1:0 Module parse failed: Unexpected character '' (1:0)

Pirate Praveen praveen at onenetbeyond.org
Thu Mar 4 16:36:53 GMT 2021



On 2021, മാർച്ച് 4 9:31:42 PM IST, Mike Gabriel <mike.gabriel at das-netzwerkteam.de> wrote:
>Control: tags -1 patch
>
>Hi Praveen,
>
>On  Mi 03 Mär 2021 16:12:47 CET, Pirate Praveen wrote:
>
>> On 2021, മാർച്ച് 3 8:17:44 PM IST, Mike Gabriel  
>> <mike.gabriel at das-netzwerkteam.de> wrote:
>>> Hi Praveen,
>>>
>>> On  Mi 03 Mär 2021 15:38:46 CET, Pirate Praveen wrote:
>>>
>>>> On 2021, മാർച്ച് 3 7:54:13 PM IST, Mike Gabriel
>>>> <mike.gabriel at das-netzwerkteam.de> wrote:
>>>>> Package: gitlab
>>>>> Version: 13.7.7-2~fto10+1
>>>>> Severity: serious
>>>>>
>>>>> Hi Praveen,
>>>>>
>>>>> I can't upgrade gitlab from 13.4.7-2~fto10+1, I get the below error
>>>>> messages (webpack and ttf fonts). Don't wonder about the /srv/gitlab
>>>>> paths, I have symlinked /var/lib/gitlab to /srv/gitlab (which always
>>>>> worked in the past) for better storage management.
>>>>
>>>> Can you share output of /usr/share/gitlab/node_modules ?
>>>>
>>>> It should be pointing to /var/lib/gitlab/node_modules.
>>>
>>> It does.
>>>
>>>> There was some changes in node_modules path to adapt to yarn 2.0 and
>>>> node-modules plugin instead of yarn 1.0.
>>>
>>> Hmmm... How can I check this. If the symlink points to
>>> /var/lib/gitlab/node_modules, then everything is fine? Or are more
>>> checks required?
>>
>> See if old directory /var/lib/gitlab/.node_modules is still present,  
>> if yes, that should be removed.
>>
>> If that does not fix, backup yarn.lock and truncate -s0 yarn.lock to  
>> regenerate it.
>>
>> Try manually running yarnpkg install (see  
>> /usr/lib/gitlab/scripts/rake-tasks.sh ) and webpack.
>>
>> Another think you can do is to remove node_modules and let yarnpkg  
>> recreate it.
>
>I have now tracked this down entirely, see MR!7 on Salsa [1]. Now, the  
>gitlab pkg's postinst ran through fine.

I will check it soon.

>I can access my Git repos again, now, except from the source tree not  
>being rendered (I see the circling circle and nothing happens). Shall  
>I open a new bug for this?

That looks like an issue with newer versions of ruby-rugged. Please open a bug.

>Greets,
>Mike
>
>[1] https://salsa.debian.org/ruby-team/gitlab/-/merge_requests/7

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.



More information about the Pkg-ruby-extras-maintainers mailing list