Bug#1068439: systemd-cron: cron-update causes re-run of some past timers

So, should this issue be forwarded/moved to systemd then?

Bug#1068439: systemd-cron: cron-update causes re-run of some past timers

Thanks for your quick reply. Am 06.04.24 um 06:37 schrieb Alexandre Detiste: Can you please try to reproduce the problem without systemd-cron involved; by copying the .timer / .service / .sh triplet from /run/systemd/generator into /etc/systemd/system and see what happens when you do manually

Bug#1068439: systemd-cron: cron-update causes re-run of some past timers

Package: systemd-cron Version: 2.3.4-1 Severity: normal Dear Maintainer, Today I noticed that a run of cron-update.service apparently causes some past cron jobs to re-run. In particular, I have a cron job of "5 5 5 * *" which correctly executed this morning at 2024-04-05T05:05:08.401635+02:00.

Bug#1067225: equivs-build fails due to duplicate debhelper compat level

Package: equivs Version: 2.3.1 Severity: normal Dear Maintainer, I tried to install all build dependencies given in a control file using `mk-build-deps -ir` from devscripts. However, equis-build of the package fails: > dh: error: debhelper compat level specified both in debian/compat and via >

Bug#1065421: extrepo-offline-data: Gitlab GPG key is expired

Hello Juri, Awesome, thanks! Best Maximilian

Bug#1065421: extrepo-offline-data: Gitlab GPG key is expired

Package: extrepo-offline-data Version: 1.0.4 Severity: normal Dear Maintainer, The GPG key of the Gitlab repository is expired since March 1st. The new one can be downloaded at [1]. Best Maximilian [1]: https://packages.gitlab.com/gpg.key

Bug#1060918: extrepo-offline-data: anydesk GPG key is expired

Package: extrepo-offline-data Version: 1.0.4 Severity: normal Dear Maintainer, The anydesk key included in the extrepo repo is expired since 2023-12-17. The updated key can be fetched from the same URL as commented in the yaml file [1]. Best, Maximilian [1]:

Bug#1036891: texlive-binaries: Error "attempt to call method 'read' (a nil value)" makes lualatex unusable

> LaTeX2e <2018-12-01> > ...-dist/tex/luatex/luaotfload/luaotfload-configuration.lua:292: attempt to cal > l method 'read' (a nil value) I am seeing the exact same issue. Downgrading "texlive-binaries" to "2018.20181218.49446-1" has fixed it for me (while leaving all other packages up to

Bug#1028460: extrepo-offline-data: gitlab_ce repo appears empty

Package: extrepo-offline-data Version: 1.0.3 Severity: normal Dear Maintainer, Apperently, the repository gitlab_ce is empty. According to the website of the Gitlab CE repository [1], there are only packages for buster and bullseye available currently. Should the suite then be fixed to

Bug#1025001: gitlab: Some UI elements, including buttons, are replaced with "undefined"

Dear Maintainer, I am indeed experiencing the same issues since the last upgrade. I noticed, however, that some buttons are still there and useable, but they are simply invisible unless hovered or clicked (i.e., they only lack text). Especially modal dialogs are entirely unusable, though.

Bug#1018935: kwin-x11: kwin_x11 crashing periodically while rendering a popup notification

> I have now, on 2 occasions, had a crash in kwin while rendering a popup > notification. > I am seeing kwin crashes when a notification popup appears, too. In many cases, plasmashell becomes unresponsive, too, so I need to restart them both.

Bug#1019731: gitlab: failed to fetch comments in merge requests (500 Internal Server Error)

> My bad, I mixed things up: the 500 error I am experiencing is the one from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019403 (undefined method `h' for LabelsHelper:Module). Yeah, these two seem quite similar. The workaround for 1019403 has to be repeated after every update, though,

Bug#1022972: konsole: Konsole does not handle arrow keys correctly anymore

On Thu, 03 Nov 2022 10:07:47 +0100 Jonas =?ISO-8859-1?Q?Sch=E4fer?= wrote: > Max, Nathanael, could you confirm that you're too using Neo2, or similarly > "exotic" layouts? Otherwise we're probably looking at different issues. I can confirm that. I am using Neo2, too, with "Default (XFree

Bug#1023291: gitlab-sidekiq spamming logs after upgrade to gitlab 15.4.2

On Tue, 01 Nov 2022 20:59:49 +0100 Ondrej Zary wrote: > after upgrading gitlab to 15.4.2, gitlab-sidekiq is spamming logs like this: > > gitlab-sidekiq[311326]: Passing the timeout as a positional argument is deprecated, it should be passed as a keyword argument: > gitlab-sidekiq[311326]:

Bug#1019731: gitlab: failed to fetch comments in merge requests (500 Internal Server Error)

Control: forwarded -1 https://gitlab.com/gitlab-org/gitlab/-/issues/374174 Hi there, As discussed in the upstream Gitlab bug report [1], apparently the package `ruby-activerecord` in version 6.1.6.1 (2:6.1.6.1+dfsg-3~fto11+1) is broken as it appears to contain file from version 6.1.6

Bug#1019731: gitlab: failed to fetch comments in merge requests (500 Internal Server Error)

> Some time after upgrading to 15.3.2 (but not from the beginning), > loading of comments in merge requests started to fail. Apparently, only merge requests with annotations in the diff view are affected. That's why I didn't notice the issue from the beginning.

Bug#988908: plantuml: Can plantuml work with default-jre-headless?

> Would it be possible to change this to also accept the headless version, > ie 'default-jre | default-jre-headless'? It would reduse the apt > download by 21.4 MiB and the disk footprint by 214 MiB. I'd like to second this. According to the PlantUML FAQ (https://plantuml.com/en/faq)

Bug#1019731: gitlab: failed to fetch comments in merge requests (500 Internal Server Error)

Package: gitlab Version: 15.3.2+ds1-1~fto11+1 Severity: normal Dear Maintainer, Some time after upgrading to 15.3.2 (but not from the beginning), loading of comments in merge requests started to fail. This sounds similar to #1019403, but I believe it is a different issue. While loading a merge

Bug#1019430: New release in preparation

Apparently, the KDE team is preparing a new release of Krusader [1], that includes the fix for this bug (among many others). [1]: https://invent.kde.org/utilities/krusader/-/issues/22

Bug#1019430: krusader: Cannot extract archive anymore

Package: krusader Version: 2:2.7.2-2 Severity: normal Dear Maintainer, Krusader offers options to extract an archive in the right click menu. Unfortunately, these buttons do not work, simply nothing happens (no error message etc.). I believe this is the same bug which is reported and marked

Bug#1019403: gitlab: failed to fetch comments in issue (500 Internal Server Error)

Package: gitlab Version: 15.3.2+ds1-1~fto11+1 Severity: normal Tags: patch Dear Maintainer, After upgrading Gitlab, issue comments failed to fetch. I got the following log entries: Completed 500 Internal Server Error in 234ms (ActiveRecord: 154.4ms | Elasticsearch: 0.0ms | Allocations:

Bug#1017701: gitlab: Upgrade to 15.2.2: Error installing prometheus-client-mmap in configuration

Package: gitlab Version: 15.2.2+ds1-2~fto11+1 Severity: important Dear Maintainer, Unfortunately, upgrading to 15.2.2+ds1-2~fto11+1 fails for me since a ruby extension cannot be built: Building native extensions. This could take a while... ERROR: Error installing

Bug#1015301: gitlab: Upgrade to 15.0.4 fails because BackgroundMigrations could not finalize

On Tue, 19 Jul 2022 19:22:02 +0200 Antoine Le Gonidec wrote: > I could work around the failure to execute the last remaining migration using the attached patch. > > This patch is provided only for helping in diagnosing the underlying issue, I would not suggest applying it as-is. Thanks

Bug#1015303: gitlab: updating labels and assignee of issues/merge requests causes error messages

Update from upstream maintainer [1]: The file /etc/gitlab/cable.yml should be set to production:  adapter: redis  url: redis://localhost:6379 This way, also setting the assignee works correctly. [1] https://gitlab.com/gitlab-org/gitlab/-/issues/362266#note_1030743220

Bug#1015302: Upgrading 14.10.5 to 15.0.4 aborts on db:migrate

Hi Jakob, After reading around the docs Patrick linked, I noticed that both Feature.enabled?(:execute_batched_migrations_on_schedule) and Feature.enabled?(:optimize_batched_migrations) returned false. I just checked these settings for me and both returned true. I manually restarted the

Bug#1015301: Status of background jobs

Update on the background migrations: All except one background migrations finished successfully, leaving only "BackfillIntegrationsTypeNew: integrations " stuck at failed. This one is exactly the migration mentioned in [1], so I guess this

Bug#1015303: Possible issue in Debian package only?

Apparently, this file is generated automatically by upstream Gitlab [1], so this might have gotten lost somewhere in packaging? [1]: https://gitlab.com/gitlab-org/gitlab/-/issues/362266#note_1030722428

Bug#1015302: Upgrading 14.10.5 to 15.0.4 aborts on db:migrate

Hi Patrick, Your issue seems to be the same as Bug#1015301 that I just filed earlier today. I actually shared a workaround that allowed me to finish the upgrade by temporarily marking the failed background migrations as successful in the database. Maybe you wanna have a look there:

Bug#1015303: gitlab: updating labels and assignee of issues/merge requests causes error messages

Package: gitlab Version: 14.10.5+ds1-1~fto11+1 Severity: normal Tags: patch Dear Maintainer, In versions 14.10.5 and 15.0.4 I experienced an annoying issue when updating the assignee or labels of issues and merge requests: After doing the change, an error message pops up, however, the change

Bug#1015301: gitlab: Upgrade to 15.0.4 fails because BackgroundMigrations could not finalize

Package: gitlab Version: 15.0.4+ds1-1~fto11+2 Severity: important Dear Maintainer, I just tried to upgrade to Gitlab 15.0.4 on my two instances. While I had no issues in my smaller instance, my bigger one had some issues. First, postinst failed with the message

Bug#960489: mosquitto: Logrotate still reporting gzip errors

Package: mosquitto Version: 2.0.11-1 Followup-For: Bug #960489 Dear Maintainer, I can still observe these error messages in version 2.0.11-1. They are AFAIK caused by a missing `delaycompress` stanza in `/etc/logrotate.d/mosquitto`. Without `delaycompress` logrotate always tries to compress

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

Thanks for confirmation. Closing this bug. I just tested your new version 14.8.5+ds1-1~fto11+2. Unfortunately, in the gitlab-rake command script, the export of GEM_HOME is missing, causing the script to fail. After adding GEM_HOME to the list of exports, I can run commands like gitlab-rake

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

So I will wait if anyone else can confirm or reproduce this issue before adding GEM_PATH. Did you have GEM_HOME set in /etc/gitlab/gitlab-debian.conf ? No, actually not. I now tested with   GEM_HOME=/var/lib/gitlab/.gem and I can confirm that this alone suffices. So, setting GEM_PATH is

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

Run 'gem env gempath' and set GEM_PATH variable with this value and /var/lib/gitlab/.gem added in /etc/gitlab/gitlab-debian.conf I will try to do this automatically too. This has indeed worked immediately. Thank you very much for the fast support! Best Maximilian OpenPGP_signature

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

A little addition: To also get gitlab-rake working, I needed to add GEM_PATH to the list of exported variables in /usr/sbin/gitlab-rake. Best, Maximilian OpenPGP_signature Description: OpenPGP digital signature

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

Package: gitlab Version: 14.7.7+ds1-2~fto11+2 Severity: normal Dear Maintainer, Recently, I tried to upgrade Gitlab to 14.7.7+ds1-2~fto11+2. Unfortunately, gitlab-sidekiq does not start afterwards but fails as it cannot find graphiql-rails: gitlab-sidekiq[8334]: Could not find gem

Bug#1006610: gnucash: Crash with std::bad_alloc when trying to create any report

Dear Yuta, Thanks for your suggestion. Indeed, both 2.34.5-1 and 2.34.6-1 worked fine for me! Should wo forward this report to the maintainers of libwebkit2gtk-4.0-37 then? Best, Maximilian OpenPGP_signature Description: OpenPGP digital signature

Bug#1006610: gnucash: Crash with std::bad_alloc when trying to create any report

Package: gnucash Version: 1:4.8-1 Severity: important Dear Maintainer, Since recently, Gnucash crashes with an std::bad_alloc exception whenever I try to open a report. I am unsure whether this bug is related to #851783. This is the valgrind output in the moment I try to open a report:

Bug#996260: Bug#998693: btrbk: Regression with security mitigation for CVE-2021-38173

On 23.11.21 16:30, Thorsten Alteholz wrote: Hi Bart, oh, no, I didn't know of that regression, sorry. There is a new package [1] available. Can you please test whether things are better with it?   Thorsten [1]

Bug#996260: Acknowledgement (btrbk: Regression with security mitigation for CVE-2021-38173)

This issue was fixed upstream in version 0.29.1. Is there a chance to get this patch into stable? Line 165 just needed to be changed to:     allow_exact_cmd "${sudo_prefix}btrfs subvolume (show|list)( ${option_match})* ${file_match}"; OpenPGP_signature Description: OpenPGP digital

Bug#998693: gitlab: Upgrade to 14.2.6 fails with undefined method `install_monkey_patches'

I got the transaction_metrics.rb error during the upgrade of ./play.it forge, but not the gitlab-sidekiq one. I suspect they are unrelated, and it might be worth opening a dedicated issue for the gitlab-sidekiq/sudo error to make it easier to find by other people. Yeah, you are right, this

Bug#999739: fai-setup-storage: BTRFS-RAID on NVMe fails to install

Package: fai-setup-storage Version: 5.8.4 Severity: normal Tags: patch Dear Maintainer, I observed an issue trying to setup an BTRFS RAID on NVMe disks. I have used FAI version 5.8.4, however, I think that the bug is still present in version 5.10.3. My disk configuration (I deliberately have

Bug#998693: gitlab: Upgrade to 14.2.6 fails with undefined method `install_monkey_patches'

Unfortunately, now gitlab-sidekiq fails to start since it is apparently trying to run a command with `sudo`: I noticed that it's the `ExecStartPre=` that fails. Maybe the behaviour of `bundle` has changed recently? Running   sudo -u git bundle install --local in /usr/share/gitlab fails

Bug#998693: gitlab: Upgrade to 14.2.6 fails with undefined method `install_monkey_patches'

> Remove this initializer. I have added rm_conffile to remove this automatically in debian/gitlab.maintscript but it seems to be not working. Thanks for the prompt response, removing /usr/share/gitlab/config/initializers/transaction_metrics.rb did the trick. The installation finishes now.

Bug#998693: gitlab: Upgrade to 14.2.6 fails with undefined method `install_monkey_patches'

Package: gitlab Version: 14.2.6+ds1-2~fto11+1 Severity: important Dear Maintainer, Today I tried to upgrade from gitlab version 14.1.7+ds1-2~fto11+1 to 14.2.6+ds1-3~fto11+1. This failed unfortunately (see log below). Best, Maximilian rake aborted! NoMethodError: undefined method

Bug#996260: btrbk: Regression with security mitigation for CVE-2021-38173

Package: btrbk Version: 0.27.1-1+deb10u1 Severity: normal Dear Maintainer, In the security upload for CVE-2021-38173 the ssh_filter_btrbk.sh script was changed. This, however, introduced a regression for me as my btrbk clients use the command sudo -n btrfs subvolume list -a -c -u -q -R

Bug#995400: fcopy: allow conjunction of classes for file selection

Package: fai-client Version: 5.10.3 Severity: wishlist Dear Maintainer, When installing files with fcopy, I frequently struggle how to require multiple classes for a certain file to match, e.g. for a file in /etc/apt/preferences which I want to install ONLY for a certain debian version AND a

Bug#991979: python3: SSL errors trigger asyncio loop exceptions

Package: python3 Version: 3.7.3-1 Severity: normal Dear Maintainer, I noticed an issue using aiohttp with Python 3.7.3 in Debian Buster. When a request fails due to SSL certificate problems there are asyncio loop exceptions triggered — although my code is wrapped in a try-except-block, mwe:

Bug#990103: gitlab: Conflicting dependencies on google-protobuf prevent package configuration during update

Hi, ruby-google-protobuf package no longer works and we need to install google-protobuf from rubygems.org now. This is documented in https://wiki.debian.org/gitlab Thank you very much, this actually works! Best, Maximilian OpenPGP_signature Description:

Bug#990103: gitlab: Conflicting dependencies on google-protobuf prevent package configuration during update

Package: gitlab Version: 13.12.3+ds1-4~fto10+1 Severity: important Dear Maintainer, Unfortunately, upgrade to Gitlab 13.12.3+ds1-4~fto10+1 and gitaly 13.12.1+dfsg-4~fto10+1 fails since dependencies on google-protobuf are conflicting apperently:

Bug#988108: gitlab: Repeated issues resolving dependencies on upgrade

Hi, We cannot support more than one version of gitlab at any time. Gitlab by nature has fast releases and only way to keep up is keep updating gitlab. Only if upstream provides a long term supported version, we can support a gitlab version for longer than a month. Currently our goal is to go

Bug#988108: gitlab: Repeated issues resolving dependencies on upgrade

Hi, You should be installing gitlab 13.11.2. You need to add contrib section to people.debian.org/~praveen/gitaly. This is mentioned in https://wiki.debian.org/gitlab/#New_changes All dependencies are compatible with this version. Thanks for the hint, I hadn't gotton this. However, this

Bug#988108: gitlab: Repeated issues resolving dependencies on upgrade

Package: gitlab Version: 13.9.6+ds1-1~fto10+1 Severity: important Dear Maintainer, unfortunately, I have repeatedly issues when upgrading gitlab to a new version. My system is basically as recommended in the Debian Wiki with Buster as basis plus Backports and Fasttrack. However, I am often

Bug#985057: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

apt install ruby-doorkeeper=5.3.0-2~bpo10+1 should fix it and I will be uploading gitlab 13.9.3 to fasttrack soon, which will fix this. Awesome, thanks a lot! OpenPGP_signature Description: OpenPGP digital signature

Bug#985057: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

This matching is expected. Can you share the error message? ruby-doorkeeper 5.3 to 5.5 update is not supposed to break gitlab. Basically, the rake commands (check, backup, ...) started to fail: $ gitlab-rake gitlab:check :( Check if Gitlab is configured correctly... fatal: Kein

Bug#985057: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Package: gitlab-apt-pin-preferences Version: 2021.03.09 Severity: normal Dear Maintainer, I am experimenting with gitlab-apt-pin-preferences to get Gitlab's dependencies right. However, I noticed that now ruby-doorkeeper breaks Gitlab. In /etc/apt/preferences.d/99gitlab ruby-doorkeeper is

Bug#962259: ruby-rqrcode 1.1.2-3 breaks 2FA settings page

Hi, I actually found the culprit — it's actually ruby-rqrcode. Downgrading to 0.4.2-3 fixed the issue of the 2FA page. I also found this in my logs: Started GET "/-/profile/two_factor_auth" for 10.32.5.1 at 2021-02-22 17:25:44 +0100 Processing by Profiles::TwoFactorAuthsController#show as

Bug#982903: gitlab: Internal error caused by missing gitaly-git2go binary

You will need to regenerate Gemfile.lock. See the wiki page for steps. It saves the exact versions used during installation in Gemfile.lock It is supposed to be handled automatically for most gems, but it does not work for native gems. There is an open bug about it.

Bug#982903: gitlab: Internal error caused by missing gitaly-git2go binary

Uploaded gitaly 13.7.5 to fasttrack-staging. If someone can confirm this, I will move it to fasttrack. Hi, I can confirm that gitaly-git2go is now present, however gitlab now refuses to start since it's missing gitaly-13.6.5. So I cannot confirm that gitaly-git2go is actually working.

Bug#962259: Creating Webhooks fails and returns error 500

This issue should have been fixed by ruby-attr-encrypted 3.1.0-3~bpo10+1 from buster-backports. See the following bug report for more details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968971 This is weird, it still fails for me. I tested on two independent instances both using

Bug#982903: gitlab: Internal error caused by missing gitaly-git2go binary

Hi, This particular binary is built using go build tags, which I'm not able integrate into dh-golang workflow yet. I'm trying. I was able to build it once in the past but I don't seem to have committed it. I was actually able to build it from the debian source package. I installed the

Bug#981124: incron: Zombie processes still piling up

Package: incron Version: 0.5.12-1+deb10u1 Severity: important Dear Maintainer, I have been using incron version 0.5.12-1+deb10u1 on Debian Buster and still observe the issue in bug #930526. I also tried 0.5.12-2 and still see zombie processes piling up. Moreover, I also occasionally get a

Bug#972754: Bug fixed in 13.5.7-1

Dear Maintainer, In package version 13.5.7-1, this issue is still present. When I try to upload a JPG file to an issue, the upload fails unless I manually install libimage-exiftool-perl. Best Maximilian OpenPGP_signature Description: OpenPGP digital signature

Bug#968626: Error 500 during CI artifacts upload from gitlab-runner

Hi! same for me: after upgrading to 13.5.6, the artifacts upload works even after reverting my local manual workaround (see "etag.patch" above). I can confirm that the artifact upload works again without "etag.patch" in Gitlab 13.5.7-1, so I think that this issue can be closed now. Best

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

Someone affected should confirm it, I confirmed issue pages that was broken is fixed. My broken pages are actually fixed with Gitlab 13.5.7-1. So for my side, this issue can be closed. Thanks a lot for debugging & fixing! Best Maximilian OpenPGP_signature Description: OpenPGP

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

Someone else reported the artifacts issue was resolved in 13.5.6. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968626#40 Oh, sorry, i didn't mean artifact upload (bug 968626), but the Gitlab internal artifacts that are missing from bug 977701 and break some pages.

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

Some good news finally. After I switched to using only yarn for all modules (use unpatched package.json) webpack is working fine. Now I will try to add back the packaged modules one by one so we can know which module broke it. This is indeed great news! I will upload 13.5.7 to fasttrack

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

> Try copying that directory from older versions ? I tried copying from 13.4.7-1, unfortunately without success. The issue boards and other resources stay empty. I guess that older versions won't work because the database might have been changed incompatibly, or? OpenPGP_signature Description:

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

Is there anything else that we could try to workaround the issues? OpenPGP_signature Description: OpenPGP digital signature

Bug#872773: ITP: firefox-passff -- pass manager extension for Firefox

On Sun, 4 Feb 2018 10:34:31 +0100 Michael Meskes wrote:   > Where do we stand with this effort. I'd love to see passff in Debian. As an > alternative browserpass seems to work with both, Firefox and Chrome. Has there been any progress on packaging passff? I'd love to see it in Debian, too.

Bug#968626: Patch is not working

>I have used the patch from Maximilian Stein, but I got the same error. Have you tried to debug the exact cause of the failure in your case? In my message above I outlined how I debugged the issue — maybe that helps to investigate your situation. Best, Maximilian

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

>I tried the same and this does not fix the bug either. Same here, just finished testing.

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

So, I got the asset compilation running, but I had to workaround some issues, including broken symlinks to js libs:_ cd /usr/share/gitlab # move locale.static elsewhere mv app/assets/javascripts/locale.static . mv

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

>Unfortunately updating css-loader and postcss did not fix this issue :( Can I somehow help to untangle this issue? Are there any workarounds maybe? Best, Maximilian

Bug#968626: gitlab: Error 500 during CI artifacts upload from gitlab-runner

Hi folks, I just found a workaround for that issue. Apparently, the issue is a missing type check/type confusion in "etag" (or in the invocation of this lib). With the patch attached to this mail, artifacts can be uploaded again. To debug the issue, I added a begin/resuce block around the

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

I tried to revert the webpack.config.js and the package.json to the version from 13.4.7-1 and re-ran postinst, but with no success either. OpenPGP_signature Description: OpenPGP digital signature

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

Indeed, I also notices some minor issues like that one after I upgraded to 13.4.7-2~fto10+1. For me, e.g., the issue boards stay empty. In my browser's web console I see two error messages among many warnings: Loading module from

Bug#977636: gitlab: Package upgrade hangs indefinitely and consumes all CPU/memory

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

Bug#977636: gitlab: Package upgrade hangs indefinitely and consumes all CPU/memory

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

Bug#966653: same version of grpc rubygem from rubygems.org works

Has there actually been any progress on these issues? With the latest update of gitlab I'm now forced to use the flawed versions of ruby-google-protobuf and ruby-grpc that keep on crashing ruby and rake processes... Before, I used to downgrade these packages after each upgrade as described

Bug#972754: gitlab: Uploading images to issues fails due to missing dependency on libimage-exiftool-perl

Package: gitlab Version: 13.2.10-1+fto10+1 Severity: normal Dear Maintainer, After upgrading to version 13.2.10-1+fto10+1 I could no longer upload images to issues in the issue tracker. A quick [search on the internet][1] pointed me to a missing dependency on `libimage-exiftool-perl`. Installing

Bug#968626: gitlab: Error 500 during CI artifacts upload from gitlab-runner

Package: gitlab Version: 13.2.3-2+fto10+1 Severity: normal Dear Maintainer, Since the upgrade to above mentioned version, artifact uploads from gitlab runners fail with an error 500. Snippet from the job log: --- Uploading artifacts... time="2020-08-18T19:42:06+02:00" level=error msg="Docker

Bug#964097: gitlab: "git push" fails with a stacktrace in gitlab code due to outdated ruby version

> > We discussed this in the ruby team [1] and preferred method is to > patch gitlab to work with ruby 2.5, but we will need some volunteers > for that. I will try add ruby 2.7 in fasttrack if we see a lot of > issues with ruby 2.5. > Ok, I see. I'll of course continue to report issues that I

Bug#942545: gitlab: Issue still present in 13.1.1-1+fto10+1

Source: gitlab Version: 13.1.1-1+fto10+1 Followup-For: Bug #942545 Dear Maintainer, After upgrading to 13.1.1-1+fto10+1 I noticed that this issue is still present. I had to change owner and group of the directories `cache` and `uploads` in /var/lib/gitlab/shared/artifacts/tmp manually in order

Bug#964097: gitlab: "git push" fails with a stacktrace in gitlab code due to outdated ruby version

Source: gitlab Version: 13.1.1-1+fto10+1 Severity: important Dear Maintainer, After upgrade to above mentioned version, `git push`es started to fail on my repositories (while `git pull`s continued working). Investigating the issue I noticed that there were stack traces logged into

Bug#961127: fai-client: Error in class definition script does not stop installation

Package: fai-client Version: 5.8.4~bpo9+2 Severity: normal Dear Maintainer, Today I discovered that a task error raised in a class definition script does not stop the installation/softupdate. In my example (see log excerpt below) the class script /var/lib/fai/config/class/95-dep.sh sets an

Bug#959232: linux-image-5.5.0-2-amd64: system freeze after suspend-to-ram: potentially IRQ-related issue

Package: src:linux Version: 5.5.17-1 Severity: normal Dear maintainer, Occasionally my system freezes after waking up from suspend-to-ram. More precisely, the KDE lock screen appears, I can type my passphrase, but then the screen just stays black leaving me movable mouse. I neither can switch to

Bug#954440: linux-image-amd64: Dependency missing

Package: linux-image-amd64 Version: 4.19+105+deb10u3~bpo9+1 Severity: grave Justification: renders package unusable Dear Maintainer, I am using the version of linux-image-amd64 available on backports. Unfortunately, upgrading from 4.19+105+deb10u1~bpo9+1 to the current version

Bug#899143: strace

On Tue, 18 Jun 2019 08:44:38 +0200 Martin Dosch wrote: > I also have this problem in sid. As a user I get this error: Hey, I actually got the same issue on my machine after having updated to bullseye/testing. Man pages were only viewable as root. I noticed that this behaviour originates from

Bug#939858: cryptsetup-initramfs not installed by debian installer

Package: cryptsetup-initramfs Severity: normal Tags: d-i Dear Maintainer, Recently, I installed a machine using the "Debian Bullseye Official Snapshot amd64 DVD Binary-1 20190805-04:11". I chose to use an encrypted LVM using the entire disk and continued to install the system. Unfortunately,

Bug#930410: scribus: Security-Update of Ghostscript 9.26a~dfsg-0+deb9u3 breaks scribus in Debian Stretch

Dear Maintainer, I can confirm this behaviour. Import of PS/EPS/PDF files in scribus fails with ghostscript errors: > PostScript import failed when calling gs as: > -q -dNOPAUSE -dNODISPLAY -dBATCH -dDELAYBIND -g3368x2384 -r288 -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -c 0 0 translate

Bug#922070: gitlab: no diffs visible in merge requests and log

> You can wait till it reaches the archive (max by 24 hours I think) or add the following to your sources.list > deb http://incoming.debian.org/debian-buildd buildd-stretch-backports main contrib > and apt -t buildd-stretch-backports install ruby-grape Thanks! I just installed gitlab

Bug#922070: gitlab: no diffs visible in merge requests and log

tretch-backports/main amd64 Packages     100 /var/lib/dpkg/status 0.16.2-2 990     990 http://deb.debian.org/debian stretch/main amd64 Packages Will these dependencies be available in stretch-backports, too? Best, Maximilian Maximilian Stein E-Mail: m...@steiny.biz &l

Bug#922070: gitlab: no diffs visible in merge requests and log

Source: gitlab Version: 11.2.8+dfsg-2~bpo9+2 Severity: normal Tags: upstream Dear Maintainer, Since I upgraded my Gitlab installation to 11.2.8, I cannot see any diffs anymore (e.g., in merge requests and the log). Instead, it always says "This source diff could not be displayed because it is

Bug#914360: Bug #914360: tinc: Random segfault after connection drop

Dear Bernhard, Thanks for your analysis! In the meanwhile I have installed systemd-coredump, so I hope to be able to provide more details in case tincd crashes again. Indeed, I am running an unmodified version of the package from buster, so your analysis should be correct. Maybe the connection

Bug#914360: tinc: Random segfault after connection drop

Package: tinc Version: 1.0.35-1 Severity: normal Dear Maintainer, One instance of the tinc daemon crashed after running for quite a while. Syslog shows a peer's connection had dropped immediately before the crash: Nov 22 10:08:38 hostname tincd[691]: Flushing meta data to abcd (1.2.3.4 port

Bug#899102: Cross-submit on Github

Hey, in the meantime, I cross-submitted this bug to the upstream Github project: https://github.com/imaplib2/imaplib2/issues/3 Best, Maximilian Stein E-Mail: m...@steiny.biz <mailto:m...@steiny.biz> signature.asc Description: OpenPGP digital signature

Bug#899102: python3-imaplib2: connection to IMAP-SSL host fails on armhf

Package: python3-imaplib2 Version: 2.57-1 Severity: important Dear Maintainer, Unfortunately, imaplib2 can only connect to an IMAP/IMAP-SSL host on amd64 but not on armhf. The behavior is consistent in 2.57-1 and 2.55-1+deb9u1. In the python interactive interpreter: >>> import imaplib2 >>>

Bug#898409: virtualbox-ext-pack: postinst script interferes with firejail

Package: virtualbox-ext-pack Version: 5.2.10-4~bpo9+1 Severity: normal Dear Maintainer, I installed firejail which includes firecfg(1) to setup symbolic links in /usr/local/bin/ to run the linked programs in the firejail sandbox. Among the configured programs is wget(1) which is then restricted

Bug#891455: fai-setup-storage: Allow mount binds

> I'm not sure when you really need the bind mounts during > installation. If they are only needed when the customization scripts > are executed, you could use ainsl(1) in one of your scripts and then > add the admin user. > > If you really need the bind mounts before, go and use a hook. This is

  1   2   >