On 2020, ഡിസംബർ 18 4:05:56 PM IST, Maximilian Stein wrote:
>Am 18.12.20 um 09:44 schrieb Pirate Praveen:
>> One possibility is sassc, but it was affecting only unstable. See in the
>> wiki.
>>
>> Another thing I noticed, webpack takes more resources than earlier. Try
>> adding more swap and u
Am 18.12.20 um 09:44 schrieb Pirate Praveen:
One possibility is sassc, but it was affecting only unstable. See in the wiki.
Another thing I noticed, webpack takes more resources than earlier. Try adding
more swap and upgrade again.
This seems to be the issue here. Indeed, I had version 3.6.4-3
On 2020, ഡിസംബർ 18 3:19:55 AM IST, Maximilian Stein wrote:
>Package: gitlab
>Version: 13.4.7-2~fto10+1
>Severity: important
>
>Dear Maintainer,
>
>During an upgrade to version 13.4.7-1~fto10+1 or 13.4.7-2~fto10+1
>there is a rake process in the postinst script that consumes 100 % cpu
>and takes
Package: gitlab
Version: 13.4.7-2~fto10+1
Severity: important
Dear Maintainer,
During an upgrade to version 13.4.7-1~fto10+1 or 13.4.7-2~fto10+1
there is a rake process in the postinst script that consumes 100 % cpu
and takes up a lot of memory but never finishes, even not after hours.
I finally
4 matches
Mail list logo
