Bug#995903: marked as done (chromium: Download manager, bookmark manager and extension manager is not showing when on there tab)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:45:27 -0500
with message-id 
and subject line Re: Bug#995903: chromium: Download manager, bookmark manager 
and extension manager is not showing when on there tab
has caused the Debian Bug report #995903,
regarding chromium: Download manager, bookmark manager and extension manager is 
not showing when on there tab
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
995903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 93.0.4577.82-1
Severity: important
X-Debbugs-Cc: most_...@yahoo.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.14.0-10.1-liquorix-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  chromium-common93.0.4577.82-1
ii  libasound2 1.2.5.1-1
ii  libatk-bridge2.0-0 2.38.0-2
ii  libatk1.0-02.36.0-2
ii  libatomic1 11.2.0-8
ii  libatspi2.0-0  2.42.0-1
ii  libavcodec-extra58 [libavcodec58]  7:4.4-6+b2
ii  libavformat58  7:4.4-6+b2
ii  libavutil567:4.4-6+b2
ii  libc6  2.32-4
ii  libcairo2  1.16.0-5
ii  libcups2   2.3.3op2-7
ii  libdbus-1-31.12.20-2
ii  libdrm22.4.107-8
ii  libevent-2.1-7 2.1.12-stable-1
ii  libexpat1  2.4.1-2+b1
ii  libflac8   1.3.3-2
ii  libfontconfig1 2.13.1-4.2
ii  libfreetype6   2.10.4+dfsg-1
ii  libgbm121.2.3-2
ii  libgcc-s1  11.2.0-8
ii  libglib2.0-0   2.70.0-1+b1
ii  libharfbuzz0b  2.7.4-1
ii  libicu67   67.1-7
ii  libjpeg62-turbo1:2.0.6-4
ii  libjsoncpp24   1.9.4-5
ii  liblcms2-2 2.12~rc1-2
ii  libminizip11.1-8+b1
ii  libnspr4   2:4.32-1
ii  libnss32:3.70-1
ii  libopenjp2-7   2.4.0-3
ii  libopus0   1.3.1-0.1
ii  libpango-1.0-0 1.48.10+ds1-1
ii  libpng16-161.6.37-3
ii  libpulse0  15.0+dfsg1-2
ii  libre2-9   20210901+dfsg-1
ii  libsnappy1v5   1.1.8-1
ii  libstdc++6 11.2.0-8
ii  libwebp6   0.6.1-2.1
ii  libwebpdemux2  0.6.1-2.1
ii  libwebpmux30.6.1-2.1
ii  libx11-6   2:1.7.2-2+b1
ii  libxcb11.14-3
ii  libxcomposite1 1:0.4.5-1
ii  libxdamage11:1.1.5-2
ii  libxext6   2:1.3.4-1
ii  libxfixes3 1:5.0.3-2
ii  libxml22.9.12+dfsg-5
ii  libxrandr2 2:1.5.2-1
ii  libxshmfence1  1.3-1
ii  libxslt1.1 1.1.34-4
ii  zlib1g 1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  93.0.4577.82-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n93.0.4577.82-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.32-4
ii  libstdc++6  11.2.0-8
ii  libx11-62:1.7.2-2+b1
ii  libxext62:1.3.4-1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4.1
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox

Bug#1029369: marked as done (tpm2-tss: CVE-2023-22745)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 05:04:00 +
with message-id 
and subject line Bug#1029369: fixed in tpm2-tss 3.2.1-3
has caused the Debian Bug report #1029369,
regarding tpm2-tss: CVE-2023-22745
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1029369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tpm2-tss
Version: 3.2.1-2
Severity: normal
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for tpm2-tss.

CVE-2023-22745[0]:
| tpm2-tss is an open source software implementation of the Trusted
| Computing Group (TCG) Trusted Platform Module (TPM) 2 Software Stack
| (TSS2). In affected versions `Tss2_RC_SetHandler` and `Tss2_RC_Decode`
| both index into `layer_handler` with an 8 bit layer number, but the
| array only has `TPM2_ERROR_TSS2_RC_LAYER_COUNT` entries, so trying to
| add a handler for higher-numbered layers or decode a response code
| with such a layer number reads/writes past the end of the buffer. This
| Buffer overrun, could result in arbitrary code execution. An example
| attack would be a MiTM bus attack that returns 0x for the RC.
| Given the common use case of TPM modules an attacker must have local
| access to the target machine with local system privileges which allows
| access to the TPM system. Usually TPM access requires administrative
| privilege.

Given the context, usually TPM accessing already implying
administrative privilege, I guess we can consider the security impact
negligible or at least minor. Filling the bug mainly for tracking
downstream the issue.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-22745
https://www.cve.org/CVERecord?id=CVE-2023-22745
[1] 
https://github.com/tpm2-software/tpm2-tss/commit/306490c8d848c367faa2d9df81f5e69dab46ffb5
[2] 
https://github.com/tpm2-software/tpm2-tss/security/advisories/GHSA-4j3v-fh23-vx67

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: tpm2-tss
Source-Version: 3.2.1-3
Done: Ying-Chun Liu (PaulLiu) 

We believe that the bug you reported is fixed in the latest version of
tpm2-tss, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1029...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated tpm2-tss 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Feb 2023 12:18:52 +0800
Source: tpm2-tss
Architecture: source
Version: 3.2.1-3
Distribution: unstable
Urgency: low
Maintainer: Mathieu Trudel-Lapierre 
Changed-By: Ying-Chun Liu (PaulLiu) 
Closes: 1029369
Changes:
 tpm2-tss (3.2.1-3) unstable; urgency=low
 .
   * Backport upstream commit 306490c8d848c367
 - Fix CVE-2023-22745 (Closes: #1029369)
Checksums-Sha1:
 e4d346fedb6e4ea2038e5f12eac211198792eff6 2940 tpm2-tss_3.2.1-3.dsc
 991b6b4ba70bb0256c933fb996d4506808597205 17108 tpm2-tss_3.2.1-3.debian.tar.xz
 1df198428b50f97969a3ef75bcc752c153c033bf 7837 tpm2-tss_3.2.1-3_source.buildinfo
Checksums-Sha256:
 878d496e96fb79c19f950649e9a15552dc4fdab8f4ffb64140c2f7209be577e2 2940 
tpm2-tss_3.2.1-3.dsc
 f9fa77bd23c93bbed3152805f4662d91dbb08afe2cc65440f3c326efd697900d 17108 
tpm2-tss_3.2.1-3.debian.tar.xz
 3adf7a8b0d062fa461830dc5c06ea432b8eef29c470b563ae3ded253ca635e71 7837 
tpm2-tss_3.2.1-3_source.buildinfo
Files:
 f1e344efaa4e053087295eec1caff9f2 2940 libs optional tpm2-tss_3.2.1-3.dsc
 002de84fac56439ada544b6809bd1d1a 17108 libs optional 
tpm2-tss_3.2.1-3.debian.tar.xz
 5c5899e2c88189cf82beefb4363b1f9f 7837 libs optional 
tpm2-tss_3.2.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmPxqmkTHHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiBMYD/9V7D5vai3RJhIdBrOXKL1yd6sYfPRI
8RQmICeJWPgZKMc67qmNK9HhYR+Wdohsg+nGijPJ4xUe2j8/llPotZxZtnM6EmkW

Bug#1031427: marked as done (libomemo-c-dev: No version in pkgconf)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:50:23 +
with message-id 
and subject line Bug#1031427: fixed in libomemo-c 0.5.0-4
has caused the Debian Bug report #1031427,
regarding libomemo-c-dev: No version in pkgconf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libomemo-c-dev
Version: 0.5.0-2
Severity: normal
X-Debbugs-Cc: stefan.kr...@posteo.de

Dear Maintainer,

libomemo-c doesn't provide a modversion for pkg-config.

--
$ pkg-config --modversion libsignal-protocol-c
2.3.3
$ pkg-config --modversion libomemo-c

--

It seems the reason is Version: @SIGNAL_PROTOCOL_C_VERSION@ here:
https://sources.debian.org/src/libomemo-c/0.5.0-3/src/libomemo-c.pc.in/#L9

--
$ grep ^Version /usr/lib/x86_64-linux-gnu/pkgconfig/libsignal-protocol-c.pc 
Version: 2.3.3
$ grep ^Version /usr/lib/x86_64-linux-gnu/pkgconfig/libomemo-c.pc
Version:
--

The patch should fix the problem:

Index: libomemo-c/src/libomemo-c.pc.in
===
--- libomemo-c.orig/src/libomemo-c.pc.in
+++ libomemo-c/src/libomemo-c.pc.in
@@ -6,7 +6,7 @@ includedir=@INCLUDE_INSTALL_DIR@

 Name: @PROJECT_NAME@
 Description: OMEMO C Library
-Version: @SIGNAL_PROTOCOL_C_VERSION@
+Version: @OMEMO_C_VERSION@

 Requires:
 Libs: -L${libdir} -L${sharedlibdir} -l@PROJECT_NAME@


debuild with patch:
$ grep ^Version 
debian/libomemo-c-dev/usr/lib/x86_64-linux-gnu/pkgconfig/libomemo-c.pc
Version: 0.5.0

I will upload a patch on salsa.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libomemo-c-dev depends on:
ii  libomemo-c0  0.5.0-2

libomemo-c-dev recommends no packages.

libomemo-c-dev suggests no packages.

-- no debconf information
Thank you for using reportbug
--- End Message ---
--- Begin Message ---
Source: libomemo-c
Source-Version: 0.5.0-4
Done: Martin 

We believe that the bug you reported is fixed in the latest version of
libomemo-c, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin  (supplier of updated libomemo-c package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Feb 2023 01:31:53 +
Source: libomemo-c
Architecture: source
Version: 0.5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: Martin 
Closes: 1031427
Changes:
 libomemo-c (0.5.0-4) unstable; urgency=medium
 .
   * Add Stefan Kropp to Uploaders
   [Stefan Kropp]
   * Patch to fix Version in libomemo-c.pc.in (Closes: #1031427)
Checksums-Sha1:
 fd98c2394d0d86546e3bdc0e1c0003004af6248f 2092 libomemo-c_0.5.0-4.dsc
 7611da1e602a923041e11933b87daf7d468f0a2b 3576 libomemo-c_0.5.0-4.debian.tar.xz
 53aab402a27d178ec93f3920adf013e3097079c1 7486 
libomemo-c_0.5.0-4_amd64.buildinfo
Checksums-Sha256:
 74da4dd514cb2cf5924693bae8873ac40219a1668bee4f6f2bcc174a98b947f3 2092 
libomemo-c_0.5.0-4.dsc
 ef89511c5d2a8c6fcf31180d5a1f3223c07c4143835f086cff9f5b5dc7ce7c15 3576 
libomemo-c_0.5.0-4.debian.tar.xz
 7440a3ae8142502388841469f5eb649bc04524858d37d5f8419623e690be228e 7486 
libomemo-c_0.5.0-4_amd64.buildinfo
Files:
 2fdf59b1f8fca1d3e3e229703c9530b7 2092 devel optional libomemo-c_0.5.0-4.dsc
 bd03a909a27f370d346845025061ac75 3576 devel optional 
libomemo-c_0.5.0-4.debian.tar.xz
 7bce64e0b2bac8631280b1d25b64030b 7486 devel optional 
libomemo-c_0.5.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1031051: marked as done (librust-rustls-dev depends on librust-ring-dev which is missing on mips, ppc*, s390x, riscv, sparc64, c32)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:26:16 +
with message-id <21c0d351-0082-19dc-9469-4f892d44c...@debian.org>
and subject line re: librust-rustls-dev depends on librust-ring-dev which is 
missing on mips, ppc*, s390x, riscv, sparc64, c32
has caused the Debian Bug report #1031051,
regarding librust-rustls-dev depends on librust-ring-dev which is missing on 
mips, ppc*, s390x, riscv, sparc64, c32
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-rustls-dev
Version: 0.20.8-4
Severity: serious
X-Debbugs-Cc: n...@sail.ng

Dear maintainer,

Your package librust-rustls-dev depends on librust-ring-dev that fails to build
on mips, ppc, s390x, riscv, sparc64, c32. That renders librust-tokio-utils-dev
FTBFS on said archs, in turn librust-reqwest-0.11+rustls-tls-dev, in turn 
tealdeer.

-- 
Sdrager,
Blair Noctis


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

Your package librust-rustls-dev depends on librust-ring-dev that fails to build
on mips, ppc, s390x, riscv, sparc64, c32. That renders librust-tokio-utils-dev
FTBFS on said archs, in turn librust-reqwest-0.11+rustls-tls-dev, in turn 
tealdeer.

Arch all packages are not nessacerally expected to be installable on every
architecture (whether this package should be arch all is another matter).

The fact that ring is not available on all Debian release architectures is
a pain, but I don't think it is something we can or should attempt to fix
locally in Debian.

There seemed to be some activity on improving the architecture support
in ring upstream towards the end of last year, but it's gone quiet.

--- End Message ---

Bug#998193: marked as done (gitlab: dpkg --configure gitlab fails with NoMethodError: undefined method `build' for debian bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #998193,
regarding gitlab: dpkg --configure gitlab fails with NoMethodError: undefined 
method `build' for debian bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
998193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 14.1.7+ds1-2~fto11+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   Fresh installation of gitlab from fasttrack repository fails with the
   following error: 


Initializing database...
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:13: warning: already initialized 
constant Nokogiri::HTML5::HTML_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:227:
 warning: previous definition of HTML_NAMESPACE was here
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:14: warning: already initialized 
constant Nokogiri::HTML5::MATHML_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:228:
 warning: previous definition of MATHML_NAMESPACE was here
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:15: warning: already initialized 
constant Nokogiri::HTML5::SVG_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:229:
 warning: previous definition of SVG_NAMESPACE was here
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:16: warning: already initialized 
constant Nokogiri::HTML5::XLINK_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:230:
 warning: previous definition of XLINK_NAMESPACE was here
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:17: warning: already initialized 
constant Nokogiri::HTML5::XML_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:231:
 warning: previous definition of XML_NAMESPACE was here
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:18: warning: already initialized 
constant Nokogiri::HTML5::XMLNS_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:232:
 warning: previous definition of XMLNS_NAMESPACE was here
rake aborted!
NoMethodError: undefined method `build' for 
#
/var/lib/gems/2.7.0/gems/pg_query-2.1.1/lib/pg_query/pg_query_pb.rb:6:in `'
/var/lib/gems/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:332:in
 `require'
/var/lib/gems/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:332:in
 `block in require'
/var/lib/gems/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:299:in
 `load_dependency'
/var/lib/gems/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:332:in
 `require'
/var/lib/gems/2.7.0/gems/pg_query-2.1.1/lib/pg_query.rb:4:in `'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:66:in
 `require'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:66:in
 `block (2 levels) in require'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:61:in
 `each'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:61:in
 `block in require'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:50:in
 `each'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:50:in
 `require'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler.rb:173:in 
`require'
/usr/share/gitlab/config/application.rb:15:in `'
/usr/share/gitlab/Rakefile:9:in `require'
/usr/share/gitlab/Rakefile:9:in `'



-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gitlab depends on:
ii  apache2 [httpd] 2.4.51-1~deb11u1
ii  asciidoctor 

Bug#995073: marked as done (gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2".)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #995073,
regarding gitlab: yarnpkg fails with error An unexpected error occurred: 
"Release not found: 2.4.2".
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
995073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 13.12.9+ds1-1~fto10+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
installing gitlab 13.12.9+ds1-1~fto10+1 on buster amd64 fails with:

Installing node modules...
Resolving 2.4.2 to a url...
error An unexpected error occurred: "Release not found: 2.4.2".
info If you think this is a bug, please open a bug report with the information 
provided in "/var/lib/gitlab/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/policies for documentation about 
this command.


-- System Information:
Debian Release: 10.10
  APT prefers oldstable-proposed-updates-debug
  APT policy: (500, 'oldstable-proposed-updates-debug'), (500, 
'oldstable-debug'), (500, 'oldstable'), (100, 'buster-fasttrack'), (100, 
'buster-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-0.bpo.8-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages gitlab depends on:
ii  asciidoctor 2.0.10-2~bpo10+1
pn  bc  
ii  bundler 2.1.4-2~bpo10+1
ii  bzip2   1.0.6-9.2~deb10u1
pn  dbconfig-pgsql | dbconfig-no-t  
ii  debconf [debconf-2.0]   1.5.71
pn  gitlab-common   
pn  gitlab-workhorse
ii  libruby2.7 [ruby-rexml] 2.7.3-2~fto10+1
ii  lsb-base10.2019051400
ii  msmtp-mta [mail-transport-agen  1.8.3-1
ii  nginx-full [nginx]  1.14.2-2+deb10u4
pn  node-autosize   
pn  node-axios  
pn  node-babel-loader   
pn  node-babel-plugin-lodash
pn  node-babel7 
pn  node-bootstrap  
ii  node-brace-expansion1.1.8-1
ii  node-cache-loader   4.1.0-6~bpo10+1
pn  node-chart.js   
pn  node-clipboard  
pn  node-codemirror 
pn  node-compression-webpack-plugi  
pn  node-copy-webpack-plugin
ii  node-core-js3.6.1-2~bpo10+2
ii  node-css-loader 5.0.1+~cs14.0.5-1~bpo10+1
pn  node-d3 
pn  node-d3-scale   
pn  node-d3-selection   
pn  node-dateformat 
pn  node-exports-loader 
ii  node-file-loader6.2.0-2~bpo10+1
pn  node-font-awesome   
pn  node-fuzzaldrin-plus
ii  node-glob   7.1.6-1~bpo10+1
ii  node-imports-loader 0.8.0-2~bpo10+1
pn  node-jed
ii  node-jquery 3.5.1+dfsg-4~bpo10+1
pn  node-jquery-ujs 
pn  node-js-cookie  
ii  node-js-yaml3.13.1+dfsg-2~bpo10+1
pn  node-jszip  
pn  node-jszip-utils
pn  node-katex  
ii  node-lodash 4.17.21+dfsg+~cs8.31.189.20210220-1~bpo10+1
pn  node-marked 
pn  node-mermaid
ii  node-minimatch  3.0.4-3
pn  node-mousetrap  
pn  node-pdfjs-dist 
pn  node-popper.js  
pn  node-prismjs
pn  node-prosemirror-markdown   
pn  node-prosemirror-model  
pn  node-raven-js   
ii  node-raw-loader 4.0.2-2~bpo10+1
pn  node-style-loader   
pn  node-three-orbit-controls   
pn  node-three-stl-loader   
ii  node-timeago.js 4.0.2-2~bpo10+1
pn  node-underscore 
ii  node-url-loader 4.1.1-3~bpo10+1
ii  node-uuid   8.3.2+~8.3.0-1~bpo10+1
pn  node-vue
pn  node-vue-resource   
pn  node-vue-template-compiler  
pn  node-webpack-stats-plugin   
ii  node-worker-loader  3.0.5-2~bpo10+1
pn  node-xterm  
ii  nodejs  10.24.0~dfsg-1~deb10u1
pn  ohai

Bug#995906: marked as done (gitlab: Upgrading buster to bullseye needs some more gitlab-apt-pin-preferences adjustments)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #995906,
regarding gitlab: Upgrading buster to bullseye needs some more 
gitlab-apt-pin-preferences adjustments
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
995906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 14.1.7+ds1-2~fto11+1
Severity: important

Hi,

I am just upgrading our buster gitlab (13.12.8+ds1-1~fto10+1) to bullseye 
(14.1.7+ds1-2~fto11+1)
along with the whole system.
On upgrading I get some errors like:

Could not find gem 'bootsnap (~> 1.4)' in any of the gem sources listed in your 
Gemfile.
dpkg: Fehler beim Bearbeiten des Paketes gitlab (--configure):
 »installiertes gitlab-Skript des Paketes post-installation«-Unterprozess gab 
den Fehlerwert 1 zurück
gitaly (14.1.7+dfsg-1~fto11+1) wird eingerichtet ...
Could not find gem 'rbtrace' in any of the gem sources listed in your Gemfile.

or:

gitaly (14.1.7+dfsg-1~fto11+1) wird eingerichtet ...
Resolving dependencies...
Bundler could not find compatible versions for gem "ffi":
  In Gemfile:
rbtrace was resolved to 0.4.11, which depends on
  ffi (>= 1.0.6) x86_64-linux
Could not find gem 'ffi (>= 1.0.6)', which is required by gem 'rbtrace', in any 
of the sources.
dpkg: Fehler beim Bearbeiten des Paketes gitaly (--configure):

To solve it after the failed dist-upgrade I had to install the following 
versions:

  apt install ruby-bootsnap=1.4.6-1+b2 ruby-rbtrace=0.4.11-3+b3 
ruby-ffi=1.12.2+dfsg-2+b3 ruby-character-set/bullseye ruby-concurrent/bullseye 
ruby-concurrent-ext/bullseye ruby-enumerable-statistics/bullseye 
ruby-gpgme/bullseye ruby-grape-path-helpers=1.6.3-1~bpo11+1 
ruby-hitimes/bullseye ruby-js-regex/bullseye ruby-json/bullseye 
ruby-murmurhash3/bullseye ruby-pg/bullseye ruby-prof/bullseye ruby-re2/bullseye 
ruby-redcloth/bullseye ruby-rinku/bullseye ruby-stackprof/bullseye 
ruby-unf-ext/bullseye ruby-yajl/bullseye unicorn/bullseye

The main problem is, that most packages are not upgraded from the fto10 version 
to
the bullseye one, because the fto10 version was "higher".

Thanks for your great work :-)



-- System Information:
Debian Release: 11.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#992075: marked as done (gitlab: download button for 2fa recovery codes does not work (coping works))

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #992075,
regarding gitlab: download button for 2fa recovery codes does not work (coping 
works)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
992075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gitlab
Version: 13.12.9+ds1-2
Severity: important

The same feature works fine on gitlab.com so this looks something 
specific to the native package.
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#991744: marked as done (gitlab-workhorse: contains non-free image testdata/image.svg)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #991744,
regarding gitlab-workhorse: contains non-free image testdata/image.svg
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
991744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab-workhorse
Version: 8.54.2+debian-1
Severity: serious
Justification: Policy 2.3

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The SVG image testdata/image.svg in the source package declares in its
RDF metadata that http://www.w3.org/2007/10/sw-logos.html#LogoWithoutW3C
is its license.

That license is limited to non-commercial distribution.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmDpyLMACgkQLHwxRsGg
ASGBdRAAmD0wvZAnH9yX8nLap6C7EXlzoKMgCav0jBpojHx0lFOnoeUJlkNH9BMr
lUqjuWUfQ+K8JT86Sz723nsAmBYxMnvt/MbE67Jf60we2I0SHz5uX8d0kt27aSCb
sfBFAZlUepydxqUj7RPcFFB3IgUkA2TGerTSRmBk46M7voE+UItDaw0MQiY6CQTi
XtErbOVRuo1Dvla4A4o3EobHdJvrFxMAOxuhVElhHi4NlhhVB0tiXkuJWhNEdB01
8WR3g2eqVoo1gPBWWCllmWbZw99ZfYaN/lSnC40HA9EhpXLfOP7tDUZkRskuwUid
+ohHpDEEnRHtGIwbr66GOOzwQvn1WSsGlVlvkIUbINBgCsKpgtN/aauRvMS/OsKM
ssv9TcbwrSGG9F7virtBNRomNpE5EBPBjISf7gd4kX3zDHbMXJMiIJX7cgblKKa8
Osm3xI+HKfRn18Bx/4riuH8xY7qWOT8oxkMvOcCi9yReqEeQ/nO5I5OwSWom8Zsa
LXXGHCUg2VAKQtZvYcNGbl/W1mkmRbdqtMYq72ZcJocNHZwNhmAFcwSgyxod0gxJ
5eOpYnmzsXo7T+X5/PmnDLPNFcHy95JvB8Hq0THEYUm5NvewyNp6lmLICaIMTWev
f/Ie8+1AHbAkPtZKDa2RDfBPNYXehYqyxzDzQxRHrBNBDVBBu9c=
=C98+
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#989791: marked as done (gitlab: Some views broken by Rails 6.0.3.7 upgrade)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #989791,
regarding gitlab: Some views broken by Rails 6.0.3.7 upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
989791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 13.11.5+ds1-1~fto10+1
Severity: important

Since Rails 6.0.3.6 → Rails 6.0.3.7 upgrade, some views fail to load
with internal errors similar to this one:

ActionView::Template::Error (Please use symbols for polymorphic route 
arguments.):  
18:   %span.issuable-number= issuable.to_reference  
  
19: 
  
20: - labels.each do |label|
  
21:   = render_label(label.present(issuable_subject: project), link: 
polymorphic_path(issuable_type_args, { milestone_title: @milestone.title, 
label_na
me: label.title, state: 'all' }), small: true)  
  
22: 
  
23: %span.assignee-icon 
  
24:   - assignees.each do |assignee|
  

This is due to the following upstream change to polymorphic routes:
https://github.com/rails/rails/commit/c4c21a9f8d7c9c8ca6570bdb82d64e2dc860e62c

GitLab has been patched 2 weeks ago, but I think it would be worth to
backport this fix.

I am going to answer to this report with a suggested patch.

-- System Information:
Debian Release: 10.9
  APT prefers stable
  APT policy: (500, 'stable'), (100, 'buster-fasttrack'), (100, 
'buster-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.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 1.17.3-3+deb10u1
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-  5.0.10+really4.7.0~dfsg-4~bpo10+1
ii  gitlab-common   13.11.2+dfsg-2~fto10+1
ii  gitlab-workhorse13.11.5+ds1-1~fto10+1
ii  katex [node-katex]  0.10.2+dfsg-8~bpo10+1
ii  libjs-bootstrap4 [node-bootstr  4.3.1+dfsg2-1
ii  libjs-codemirror [node-codemir  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.j  1.16.1+ds-2~bpo10+1
ii  libruby2.7 [ruby-rexml] 2.7.3-2~fto10+1
ii  lsb-base10.2019051400
ii  nginx   1.14.2-2+deb10u4
ii  nginx-full [nginx]  1.14.2-2+deb10u4
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-babel-plugin-lodash3.3.4+~cs2.0.1-3~bpo10+1
ii  node-babel7 7.12.12+~cs150.141.84-2~bpo10+1
ii  node-brace-expansion1.1.8-1
ii  node-cache-loader   4.1.0-6~bpo10+1
ii  node-chart.js   2.7.3+dfsg-5
ii  node-clipboard  2.0.6+ds-1~bpo10+1
ii  node-compression-webpack-plugi  3.0.1-4~bpo10+1
ii  node-copy-webpack-plugin5.1.2+~cs9.0.2-4~bpo10+1
ii  node-core-js3.6.1-2~bpo10+2
ii  node-css-loader 5.0.1+~cs14.0.5-1~bpo10+1
ii  node-d3 5.16.0-1~bpo10+1
ii  node-d3-scale   2.2.2-2~bpo10+1
ii  node-d3-selection   1.4.0-3~bpo10+1
ii  

Bug#983924: marked as done (GitLab 13.7.7: ERROR in 1:0 Module parse failed: Unexpected character '' (1:0))

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #983924,
regarding GitLab 13.7.7: ERROR in1:0 Module parse failed: 
Unexpected character '' (1:0)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
983924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

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.


Greets,
Mike

```
[...]
WARNING in ./editor/editor_lite.js 62:13-29
Critical dependency: the request of a dependency is an expression
 @ ./vue_shared/components/editor_lite.vue?vue=script=js&  
(/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./vue_shared/components/editor_lite.vue?vue=script=js&)

 @ ./vue_shared/components/editor_lite.vue?vue=script=js&
 @ ./vue_shared/components/editor_lite.vue
 @  
/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./snippets/components/snippet_blob_edit.vue?vue=script=js&

 @ ./snippets/components/snippet_blob_edit.vue?vue=script=js&
 @ ./snippets/components/snippet_blob_edit.vue
 @  
/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./snippets/components/snippet_blob_actions_edit.vue?vue=script=js&
 @  
./snippets/components/snippet_blob_actions_edit.vue?vue=script=js&

 @ ./snippets/components/snippet_blob_actions_edit.vue
 @  
/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./snippets/components/edit.vue?vue=script=js&

 @ ./snippets/components/edit.vue?vue=script=js&
 @ ./snippets/components/edit.vue
 @ ./snippet/snippet_edit.js
 @ ./pages/snippets/new/index.js
 @ multi ./main ./pages/snippets/new/index.js

ERROR in  
/usr/share/gitlab/node_modules/katex/dist/fonts/KaTeX_Math-Italic.ttf  
1:0

Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently  
no loaders are configured to process this file. See  
https://webpack.js.org/concepts#loaders

(Source code omitted for this binary file)
 @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css  
(/srv/gitlab/node_modules/css-loader/dist/cjs.js??ref--9-1!/usr/share/gitlab/node_modules/katex/dist/katex.min.css)  
36:42-82

 @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css
 @ ./behaviors/markdown/render_math.js
 @ ./behaviors/markdown/render_gfm.js
 @  
/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./vue_shared/components/markdown/field.vue?vue=script=js&

 @ ./vue_shared/components/markdown/field.vue?vue=script=js&
 @ ./vue_shared/components/markdown/field.vue
 @  
/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./releases/components/app_edit_new.vue?vue=script=js&

 @ ./releases/components/app_edit_new.vue?vue=script=js&
 @ ./releases/components/app_edit_new.vue
 @ ./releases/mount_new.js
 @ ./pages/projects/releases/new/index.js
 @ multi ./main ./pages/projects/index.js  
./pages/projects/releases/new/index.js


ERROR in  
/usr/share/gitlab/node_modules/katex/dist/fonts/KaTeX_AMS-Regular.ttf  
1:0

Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently  
no loaders are configured to process this file. See  
https://webpack.js.org/concepts#loaders

(Source code omitted for this binary file)
 @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css  
(/srv/gitlab/node_modules/css-loader/dist/cjs.js??ref--9-1!/usr/share/gitlab/node_modules/katex/dist/katex.min.css)  
6:41-81

 @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css
 @ ./behaviors/markdown/render_math.js
 @ ./behaviors/markdown/render_gfm.js
 @  
/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./vue_shared/components/markdown/field.vue?vue=script=js&

 @ ./vue_shared/components/markdown/field.vue?vue=script=js&
 @ ./vue_shared/components/markdown/field.vue
 @  

Bug#990103: marked as done (gitlab: Conflicting dependencies on google-protobuf prevent package configuration during update)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #990103,
regarding gitlab: Conflicting dependencies on google-protobuf prevent package 
configuration during update
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
990103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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:

---

Setting up gitlab (13.12.3+ds1-4~fto10+1) ...
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Bundler could not find compatible versions for gem "google-protobuf":
  In Gemfile:
google-protobuf (~> 3.14)

grpc (~> 1.30, >= 1.30.2) was resolved to 1.30.2, which depends on
  google-protobuf (~> 3.12)

gitlab-labkit (~> 0.17.1) was resolved to 0.17.1, which depends on
  pg_query (~> 2.0) was resolved to 2.0.3, which depends on
google-protobuf (~> 3.15, >= 3.15.5)

Could not find gem 'google-protobuf (~> 3.15, >= 3.15.5)', which is required by 
gem 'pg_query (~> 2.0)', in any of the sources.
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned error 
exit status 1
Setting up gitaly (13.12.1+dfsg-4~fto10+1) ...
Resolving dependencies...
Bundler could not find compatible versions for gem "google-protobuf":
  In Gemfile:
grpc (~> 1.30, >= 1.30.2) was resolved to 1.30.2, which depends on
  googleapis-common-protos-types (~> 1.0) was resolved to 1.0.6, which 
depends on
google-protobuf (~> 3.14)

grpc (~> 1.30, >= 1.30.2) was resolved to 1.30.2, which depends on
  google-protobuf (~> 3.12)

gitlab-labkit (~> 0.17.1) was resolved to 0.17.1, which depends on
  pg_query (~> 2.0) was resolved to 2.0.3, which depends on
google-protobuf (~> 3.15, >= 3.15.5)
dpkg: error processing package gitaly (--configure):
 installed gitaly package post-installation script subprocess returned error 
exit status 6
Errors were encountered while processing:
 gitlab
 gitaly
E: Sub-process /usr/bin/dpkg returned an error code (1)



I tried to manually edit the Gemfile without success. How can I fix
the configuration?

Best,
Maximilian
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#988108: marked as done (gitlab: Repeated issues resolving dependencies on upgrade)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #988108,
regarding gitlab: Repeated issues resolving dependencies on upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
988108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
running in a situation that packages are actually *too new* and Gitlab
fails configuring because it expects a certain version of a package in
its Gemfile.

E.g., to upgrade to Gitlab version 13.9.6+ds1-1~fto10+1 today, I
iteratively *downgraded* ruby packages, re-run the Gitlab
installation, which then failed because another package was too new,
and so on. Finally, for 13.9.6+ds1-1~fto10+1, I needed to downgrade
these packages:

* ruby-autoprefixer-rails=10.2.4.0+dfsg1+~cs14.2.17-1
* ruby-devise-two-factor=3.1.0-2~bpo10+1
* ruby-fog-google=1.12.1-1~fto10+1
* ruby-discordrb-webhooks=3.3.0-1
* ruby-ruby-magic-static=0.3.5-1
* ruby-gitlab-labkit=0.15.0-1~fto10+2
* ruby-batch-loader=1.4.1+dfsg.1-3
* ruby-gitlab-experiment=0.4.9-1~fto10+1
* ruby-lockbox=0.3.5-2~bpo10+1
* ruby-rotp=2.1.1+dfsg-1

Of course, I need to hold them all, since they'd be upgraded
automatically otherwise.

One solution I could think of would be to provide a dependency-package
with hard version requirements. So, in contrast to
gitlab-apt-pin-preferences, such a package would directly depend on
all Gitlab-dependencies in their correct version for a particular
version of Gitlab. That way, I'd only need to pin a single package and
get a reproducible working installation. What do you think about that?

Best,
Maximilian
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#984828: marked as done (gitlab: code tree not rendered (circling circle instead))

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #984828,
regarding gitlab: code tree not rendered (circling circle instead)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gitlab
Version: 13.7.8+ds1-1~fto10+1
Severity: serious

Hi Praveen,

here comes the other issue I am facing. Occurred with 13.7.7 and also  
occurs with 13.7.8:


When I open a Git repository on my GitLab instance, I see a circling  
circle where the code files/dirs should actually be.


The JS console provides four error messages:

1.
Uncaught TypeError: o.a.fn.tooltip is undefined (with a backtrace I  
omit here for now).


2.
Source-Map-Fehler: Error: JSON.parse: unexpected character at line 1  
column 1 of the JSON data
Ressourcen-Adresse:  
https://gitlab.das-netzwerkteam.de/assets/webpack/runtime.2cbada1d.bundle.js

Source-Map-Adresse: runtime.2cbada1d.bundle.js.map

3.
Source-Map-Fehler: Error: JSON.parse: unexpected character at line 1  
column 1 of the JSON data
Ressourcen-Adresse:  
https://gitlab.das-netzwerkteam.de/assets/webpack/pages.projects.show.7aaabbab.chunk.js

Source-Map-Adresse: pages.projects.show.7aaabbab.chunk.js.map

4.
Source-Map-Fehler: Error: JSON.parse: unexpected character at line 1  
column 1 of the JSON data
Ressourcen-Adresse:  
https://gitlab.das-netzwerkteam.de/assets/webpack/pages.projects.show.7aaabbab.chunk.js

Source-Map-Adresse: pages.projects.show.7aaabbab.chunk.js.map


Any clue where else to look for error or log messages that might help  
to track down this issue?


I can push / pull to / from my GitLab server via the git command, only  
the rendering of code trees (and possibly other Javascript dependent  
functionalities) seem(s) to be broken.


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpwP1AqE2Gdh.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#982903: marked as done (gitlab: Internal error caused by missing gitaly-git2go binary)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #982903,
regarding gitlab: Internal error caused by missing gitaly-git2go binary
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
982903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 13.6.7-1~fto10+1
Severity: important

Dear Maintainer,

Since the update to gitlab 13.6.7-1~fto10+1 (Buster Fasttrack), newly
created merge requests fail to load fully due to some missing
/usr/bin/gitaly-git2go binary.

I guess this binary is supposed to be provided by the gitaly package,
but it is not included in its current 13.6.5+dfsg-1~fto10+1 version.

To reproduce, create a new merge request, when redirecting to its newly
created page it will show an error banner "Unable to load the merge
request widget. Try reloading the page." due to a 500 error when trying
to load https://${REPO_URL}/-/merge_requests/${MERGE_ID}/widget.json

Here is the error message logged in /var/log/gitlab/production.log when
trying to fetch this widget.json file:
GRPC::Internal (13:GitCommand: start [/usr/bin/gitaly-git2go conflicts -request 
${SOME_LONG_RANDOM_STRING}]: fork/exec /usr/bin/gitaly-git2go: no such file or 
directory. 
debug_error_string:{"created":"@1613462946.026695391","description":"Error 
received from peer 
unix:/run/gitlab/gitaly.socket","file":"src/core/lib/surface/call.cc","file_line":1055,"grpc_message":"GitCommand:
 start [/usr/bin/gitaly-git2go conflicts -request ${SOME_LONG_RANDOM_STRING}]: 
fork/exec /usr/bin/gitaly-git2go: no such file or directory","grpc_status":13}):

-- System Information:
Debian Release: 10.8
  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-14-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  bc1.07.1-2+b1
ii  bundler   2.1.4-2~bpo10+1
ii  bzip2 1.0.6-9.2~deb10u1
ii  dbconfig-pgsql2.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.6.5+dfsg-1~fto10+1
ii  gitlab-workhorse  8.54.2+debian-1~bpo10+1
ii  katex [node-katex]0.10.2+dfsg-8~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.16.1+ds-2~bpo10+1
ii  libruby2.7 [ruby-json]2.7.2-4~fto10+1
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-axios0.17.1+dfsg-2
ii  node-babel-loader 8.2.2-1~bpo10+1
ii  node-babel7   7.12.12+~cs150.141.84-2~bpo10+1
ii  node-brace-expansion  1.1.8-1
ii  node-cache-loader 4.1.0-6~bpo10+1
ii  node-chart.js 2.7.3+dfsg-5
ii  node-clipboard2.0.6+ds-1~bpo10+1
ii  node-compression-webpack-plugin   3.0.1-4~bpo10+1
ii  node-copy-webpack-plugin  5.1.2+~cs9.0.2-4~bpo10+1
ii  node-core-js  3.6.1-2~bpo10+2
ii  node-css-loader   5.0.1+~cs14.0.5-1~bpo10+1
ii  node-d3   5.16.0-1~bpo10+1
ii  node-d3-scale 2.2.2-2~bpo10+1
ii  node-d3-selection 1.4.0-3~bpo10+1
ii  node-dateformat   3.0.0-1
ii  node-exports-loader   0.7.0-2~bpo10+1
ii  node-file-loader  6.2.0-2~bpo10+1
ii  

Bug#981777: marked as done (gitlab: Install error in pdfjs-dist/build/pdf.js - module parse error)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #981777,
regarding gitlab: Install error in pdfjs-dist/build/pdf.js - module parse error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
981777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 13.5.7-1~fto+1
Severity: important

Dear Maintainer,

I have been unable to complete an install of gitlab:

# apt -t buster-backports install gitlab/buster-fasttrack
ruby-hamlit/buster-fasttrack ruby-sanitize/buster-fasttrack
ruby-gitaly/buster-fasttrack gitaly/buster-fasttrack

throws a


WARNING in ./editor/editor_lite.js 61:13-29
Critical dependency: the request of a dependency is an expression
 @ ./blob_edit/edit_blob.js
 @ ./blob_edit/blob_bundle.js
 @ ./pages/projects/tree/show/index.js
 @ multi ./main ./pages/projects/index.js
./pages/projects/tree/show/index.js

ERROR in /var/lib/gitlab/node_modules/pdfjs-dist/build/pdf.js 2413:45
Module parse failed: Unexpected token (2413:45)
You may need an appropriate loader to handle this file type, currently
no loaders are configured to process this file. See
https://webpack.js.org/concepts#loaders
| intent: renderingIntent,
| renderInteractiveForms: renderInteractiveForms === true,
>  annotationStorage: annotationStorage?.getAll() || null
|   });
| }
 @ ./pdf/index.vue?vue=script=js&
(/var/lib/gitlab/node_modules/babel-loader/lib??ref--1!/var/lib/gitlab/node_modules/vue-loader/lib??vue-loader-options!./pdf/index.vue?vue=script=js&)
6:0-44 43:4-12 52:13-21
 @ ./pdf/index.vue?vue=script=js&
 @ ./pdf/index.vue
 @
/var/lib/gitlab/node_modules/babel-loader/lib??ref--1!/var/lib/gitlab/node_modules/vue-loader/lib??vue-loader-options!./blob/pdf/pdf_viewer.vue?vue=script=js&
 @ ./blob/pdf/pdf_viewer.vue?vue=script=js&
 @ ./blob/pdf/pdf_viewer.vue
 @ ./blob/pdf/index.js
 @ ./blob/pdf_viewer.js
 @ ./blob/viewer/index.js
 @ ./pages/projects/show/index.js
 @ multi ./main ./pages/projects/index.js ./pages/projects/show/index.js
Child vs/editor/editor:
 2 assets
    Entrypoint main = editor.worker.js editor.worker.js.map
    [Zot9]
/var/lib/gitlab/node_modules/monaco-editor/esm/vs/editor/editor.worker.js
+ 31 modules 357 KiB {0} [built]
    |    32 modules
    [jXzn] (webpack)/buildin/global.js 472 bytes {0} [built]
    + 3 hidden modules
Child vs/language/css/cssWorker:
 2 assets
    Entrypoint main = css.worker.js css.worker.js.map
    [gSDr]
/var/lib/gitlab/node_modules/monaco-editor/esm/vs/language/css/css.worker.js
+ 72 modules 1.64 MiB {0} [built]
    |    73 modules
    [jXzn] (webpack)/buildin/global.js 472 bytes {0} [built]
    + 4 hidden modules
Child vs/language/html/htmlWorker:
 2 assets
    Entrypoint main = html.worker.js html.worker.js.map
    [jXzn] (webpack)/buildin/global.js 472 bytes {0} [built]
    [qe8o]
/var/lib/gitlab/node_modules/monaco-editor/esm/vs/language/html/html.worker.js
+ 63 modules 1.08 MiB {0} [built]
    |    64 modules
    + 4 hidden modules
Child vs/language/json/jsonWorker:
 2 assets
    Entrypoint main = json.worker.js json.worker.js.map
    [NPwF]
/var/lib/gitlab/node_modules/monaco-editor/esm/vs/language/json/json.worker.js
+ 56 modules 669 KiB {0} [built]
    |    57 modules
    [jXzn] (webpack)/buildin/global.js 472 bytes {0} [built]
    + 4 hidden modules
Child vs/language/typescript/tsWorker:
 2 assets
    Entrypoint main = ts.worker.js ts.worker.js.map
    [2FIe] (webpack)/buildin/harmony-module.js 573 bytes {0} [built]
    [RthD]
/var/lib/gitlab/node_modules/monaco-editor/esm/vs/language/typescript/ts.worker.js
+ 34 modules 1.47 MiB {0} [built]
    |    35 modules
    [jXzn] (webpack)/buildin/global.js 472 bytes {0} [built]
    + 4 hidden modules

[...]

Child worker:
 2 assets
    Entrypoint main = tree_worker.86041521.worker.js
tree_worker.86041521.worker.js.map
    [9ghR] (webpack)/buildin/module.js 497 bytes {0} [built]
    [H0Ny]
/var/lib/gitlab/node_modules/babel-loader/lib!./diffs/workers/tree_worker.js
+ 8 modules 73.5 KiB {0} [built]
    |
/var/lib/gitlab/node_modules/babel-loader/lib!./diffs/workers/tree_worker.js
460 bytes [built]
    | ./ide/stores/utils.js 9.48 KiB [built]
    | ./diffs/store/utils.js 26.2 KiB [built]
    | ./ide/constants.js 2.27 KiB [built]
    | ./lib/utils/url_utility.js 16.5 KiB [built]
    | ./lib/utils/text_utility.js 

Bug#981776: marked as done (gitlab: Install error in pdfjs-dist/build/pdf.js - module parse error)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #981776,
regarding gitlab: Install error in pdfjs-dist/build/pdf.js - module parse error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
981776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 13.5.7-1~fto+1
Severity: important

Dear Maintainer,

I have been unable to complete an install of gitlab:

# apt -t buster-backports install gitlab/buster-fasttrack 
ruby-hamlit/buster-fasttrack ruby-sanitize/buster-fasttrack 
ruby-gitaly/buster-fasttrack gitaly/buster-fasttrack

throws a 


WARNING in ./editor/editor_lite.js 61:13-29
Critical dependency: the request of a dependency is an expression
 @ ./blob_edit/edit_blob.js
 @ ./blob_edit/blob_bundle.js
 @ ./pages/projects/tree/show/index.js
 @ multi ./main ./pages/projects/index.js
./pages/projects/tree/show/index.js

ERROR in /var/lib/gitlab/node_modules/pdfjs-dist/build/pdf.js 2413:45
Module parse failed: Unexpected token (2413:45)
You may need an appropriate loader to handle this file type, currently
no loaders are configured to process this file. See
https://webpack.js.org/concepts#loaders
| intent: renderingIntent,
| renderInteractiveForms: renderInteractiveForms === true,
>  annotationStorage: annotationStorage?.getAll() || null
|   });
| }
 @ ./pdf/index.vue?vue=script=js&
(/var/lib/gitlab/node_modules/babel-loader/lib??ref--1!/var/lib/gitlab/node_modules/vue-loader/lib??vue-loader-options!./pdf/index.vue?vue=script=js&)
6:0-44 43:4-12 52:13-21
 @ ./pdf/index.vue?vue=script=js&
 @ ./pdf/index.vue
 @
/var/lib/gitlab/node_modules/babel-loader/lib??ref--1!/var/lib/gitlab/node_modules/vue-loader/lib??vue-loader-options!./blob/pdf/pdf_viewer.vue?vue=script=js&
 @ ./blob/pdf/pdf_viewer.vue?vue=script=js&
 @ ./blob/pdf/pdf_viewer.vue
 @ ./blob/pdf/index.js
 @ ./blob/pdf_viewer.js
 @ ./blob/viewer/index.js
 @ ./pages/projects/show/index.js
 @ multi ./main ./pages/projects/index.js ./pages/projects/show/index.js
Child vs/editor/editor:
 2 assets
Entrypoint main = editor.worker.js editor.worker.js.map
[Zot9]
/var/lib/gitlab/node_modules/monaco-editor/esm/vs/editor/editor.worker.js
+ 31 modules 357 KiB {0} [built]
|32 modules
[jXzn] (webpack)/buildin/global.js 472 bytes {0} [built]
+ 3 hidden modules
Child vs/language/css/cssWorker:
 2 assets
Entrypoint main = css.worker.js css.worker.js.map
[gSDr]
/var/lib/gitlab/node_modules/monaco-editor/esm/vs/language/css/css.worker.js
+ 72 modules 1.64 MiB {0} [built]
|73 modules
[jXzn] (webpack)/buildin/global.js 472 bytes {0} [built]
+ 4 hidden modules
Child vs/language/html/htmlWorker:
 2 assets
Entrypoint main = html.worker.js html.worker.js.map
[jXzn] (webpack)/buildin/global.js 472 bytes {0} [built]
[qe8o]
/var/lib/gitlab/node_modules/monaco-editor/esm/vs/language/html/html.worker.js
+ 63 modules 1.08 MiB {0} [built]
|64 modules
+ 4 hidden modules
Child vs/language/json/jsonWorker:
 2 assets
Entrypoint main = json.worker.js json.worker.js.map
[NPwF]
/var/lib/gitlab/node_modules/monaco-editor/esm/vs/language/json/json.worker.js
+ 56 modules 669 KiB {0} [built]
|57 modules
[jXzn] (webpack)/buildin/global.js 472 bytes {0} [built]
+ 4 hidden modules
Child vs/language/typescript/tsWorker:
 2 assets
Entrypoint main = ts.worker.js ts.worker.js.map
[2FIe] (webpack)/buildin/harmony-module.js 573 bytes {0} [built]
[RthD]
/var/lib/gitlab/node_modules/monaco-editor/esm/vs/language/typescript/ts.worker.js
+ 34 modules 1.47 MiB {0} [built]
|35 modules
[jXzn] (webpack)/buildin/global.js 472 bytes {0} [built]
+ 4 hidden modules

[...]

Child worker:
 2 assets
Entrypoint main = tree_worker.86041521.worker.js
tree_worker.86041521.worker.js.map
[9ghR] (webpack)/buildin/module.js 497 bytes {0} [built]
[H0Ny]
/var/lib/gitlab/node_modules/babel-loader/lib!./diffs/workers/tree_worker.js
+ 8 modules 73.5 KiB {0} [built]
|
/var/lib/gitlab/node_modules/babel-loader/lib!./diffs/workers/tree_worker.js
460 bytes [built]
| ./ide/stores/utils.js 9.48 KiB [built]
| ./diffs/store/utils.js 26.2 KiB [built]
| ./ide/constants.js 2.27 KiB [built]
| ./lib/utils/url_utility.js 16.5 KiB [built]
| 

Bug#977751: marked as done (gitlab: node-css-loader 4.x transition)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #977751,
regarding gitlab: node-css-loader 4.x transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gitlab
Version: 13.4.7-2
Severity: important
Control: block 977701 by -1

Updating node-css-loader to 4.x breaks gitlab functionaity.
See upstream ci failure https://gitlab.com/pravi/gitlab/-/jobs/922873794

This needs to be fixed before trying to migrate to node-css-loader 5.x 
which is required for postcss 8 (required by some plugins in unstable).
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#964218: marked as done (node-yarnpkg: autopkgtest fails with node-uuid 8.2 from experimental - "Cannot read property 'v4' of undefined")

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #964218,
regarding node-yarnpkg: autopkgtest fails with node-uuid 8.2 from experimental 
- "Cannot read property 'v4' of undefined"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
964218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: node-yarnpkg
Version: 1.22.4-3
Severity: important

Full build log is attached. This was run in a clean and uptodate lxc 
container using salsa.debian.org/ruby-team/meta/build script.



autopkgtest [18:26:50]: version 5.10
autopkgtest [18:26:50]: host ilvala2; command line: /usr/bin/autopkgtest --user debci --apt-upgrade --log-file=/tmp/node-uuid_8.2.0-1_amd64.Ix8K1VsEM6/autopkgtest/node-yarnpkg.log /home/pravi/forge/js-team/build-area/node-node-uuid_8.2.0-1_all.deb /home/pravi/forge/js-team/build-area/node-uuid_8.2.0-1_all.deb node-yarnpkg -- lxc --sudo autopkgtest-unstable-amd64
autopkgtest [18:27:02]:  test bed setup
Hit:1 http://deb.debian.org/debian unstable InRelease
Hit:2 http://incoming.debian.org/debian-buildd buildd-unstable InRelease
Hit:3 http://deb.debian.org/debian-debug unstable-debug InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
autopkgtest [18:27:05]: testbed dpkg architecture: amd64
autopkgtest [18:27:05]: testbed running kernel: Linux 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07)
autopkgtest [18:27:06]:  apt-source node-yarnpkg
Get:1 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (dsc) [7,508 B]
Get:2 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [6,144 B]
Get:3 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [2,652 B]
Get:4 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [7,888 B]
Get:5 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [2,432 B]
Get:6 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [14.8 kB]
Get:7 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [1,756 B]
Get:8 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [1,440 B]
Get:9 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [2,100 B]
Get:10 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [4,780 B]
Get:11 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [4,604 B]
Get:12 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [2,936 B]
Get:13 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [6,780 B]
Get:14 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [28.0 kB]
Get:15 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [3,212 B]
Get:16 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [6,864 B]
Get:17 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [5,516 B]
Get:18 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (tar) [72.9 MB]
Get:19 http://deb.debian.org/debian unstable/main node-yarnpkg 1.22.4-3 (diff) [12.1 kB]
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/debci/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Sat 02 May 2020 07:38:13 AM UTC
gpgv:using RSA key D30863E26020E543F4719A838F53E0193B294B75
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./node-yarnpkg_1.22.4-3.dsc
tar: Ignoring unknown extended header keyword 'NODETAR.depth'
tar: Ignoring unknown extended header keyword 'NODETAR.follow'
tar: Ignoring unknown extended header keyword 'NODETAR.ignoreFiles.0'
tar: Ignoring unknown extended header keyword 'NODETAR.ignoreFiles.1'
tar: Ignoring unknown extended header keyword 'NODETAR.ignoreFiles.2'
tar: Ignoring unknown extended header keyword 'NODETAR.package.name'
tar: Ignoring unknown extended header keyword 'NODETAR.package.version'
tar: Ignoring unknown extended header keyword 'NODETAR.package.description'
tar: Ignoring unknown extended header keyword 'NODETAR.package.keywords.0'
tar: Ignoring unknown extended header keyword 'NODETAR.package.keywords.1'
tar: Ignoring unknown extended header keyword 'NODETAR.package.license'
tar: 

Bug#975493: marked as done (gitlab: Gitlab install script not working)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #975493,
regarding gitlab: Gitlab install script not working
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
975493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 13.3.9-1+fto10+1
Severity: important

Hi,

Gitlab are not installing.

I doesn't know the reason, but when I try to install it through apt-get upgrade 
(following debian/gitlab page for upgrading), that's not working.

The log are the following:

Precompiling assets...
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Attention: used pure ruby version of MurmurHash3
/usr/share/gitlab/lib/gitlab.rb:38: warning: already initialized constant 
Gitlab::COM_URL
/usr/share/gitlab/lib/gitlab.rb:38: warning: previous definition of COM_URL was 
here
/usr/share/gitlab/lib/gitlab.rb:39: warning: already initialized constant 
Gitlab::STAGING_COM_URL
/usr/share/gitlab/lib/gitlab.rb:39: warning: previous definition of 
STAGING_COM_URL was here
/usr/share/gitlab/lib/gitlab.rb:40: warning: already initialized constant 
Gitlab::APP_DIRS_PATTERN
/usr/share/gitlab/lib/gitlab.rb:40: warning: previous definition of 
APP_DIRS_PATTERN was here
/usr/share/gitlab/lib/gitlab.rb:41: warning: already initialized constant 
Gitlab::SUBDOMAIN_REGEX
/usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of 
SUBDOMAIN_REGEX was here
/usr/share/gitlab/lib/gitlab.rb:42: warning: already initialized constant 
Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of VERSION was 
here
/usr/share/gitlab/lib/gitlab.rb:43: warning: already initialized constant 
Gitlab::INSTALLATION_TYPE
/usr/share/gitlab/lib/gitlab.rb:43: warning: previous definition of 
INSTALLATION_TYPE was here
/usr/share/gitlab/lib/gitlab.rb:44: warning: already initialized constant 
Gitlab::HTTP_PROXY_ENV_VARS
/usr/share/gitlab/lib/gitlab.rb:44: warning: previous definition of 
HTTP_PROXY_ENV_VARS was here
yarn install v1.22.4
[1/4] Resolving packages...
success Already up-to-date.
$ node ./scripts/frontend/postinstall.js
success Dependency postinstall check passed.
Done in 0.74s.
WARNING on line 297, column 11 of 
/usr/share/gitlab/app/assets/stylesheets/framework/common.scss:
Compound selectors may no longer be extended.
Consider `@extend .card, .card-body` instead.
See http://bit.ly/ExtendCompound for details.

WARNING on line 208, column 13 of 
/usr/share/gitlab/app/assets/stylesheets/framework/filters.scss:
Compound selectors may no longer be extended.
Consider `@extend .form-control, :hover` instead.
See http://bit.ly/ExtendCompound for details.

DEPRECATION WARNING on line 88 of 
/usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss:
The operation `#292961 plus 33` is deprecated and will be an error in future 
versions.
Consider using Sass's color functions instead.
https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions

DEPRECATION WARNING on line 88 of 
/usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss:
The operation `#4b4ba3 plus 33` is deprecated and will be an error in future 
versions.
Consider using Sass's color functions instead.
https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions

DEPRECATION WARNING on line 88 of 
/usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss:
The operation `#1a3652 plus 33` is deprecated and will be an error in future 
versions.
Consider using Sass's color functions instead.
https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions

DEPRECATION WARNING on line 88 of 
/usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss:
The operation `#2261a1 plus 33` is deprecated and will be an error in future 
versions.
Consider using Sass's color functions instead.
https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions

DEPRECATION WARNING on line 88 of 
/usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss:
The operation `#0d4524 plus 33` is deprecated and will be an error in future 
versions.
Consider using Sass's color functions instead.
https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions

DEPRECATION WARNING on line 88 of 

Bug#977636: marked as done (gitlab: Package upgrade hangs indefinitely and consumes all CPU/memory)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #977636,
regarding gitlab: Package upgrade hangs indefinitely and consumes all CPU/memory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 killed the process with a SIGKILL, and gitlab seems to work
afterwards.

This is the last output I get during the installation:

 snip --

yarn install v1.22.4
[1/4] Resolving packages...
success Already up-to-date.
$ node ./scripts/frontend/postinstall.js

 
success Dependency postinstall check passed.
Done in 1.90s.   
WARNING on line 297, column 11 of 
/usr/share/gitlab/app/assets/stylesheets/framework/common.scss:
Compound selectors may no longer be extended.
Consider `@extend .card, .card-body` instead.
See http://bit.ly/ExtendCompound for details.   
 
WARNING on line 208, column 13 of 
/usr/share/gitlab/app/assets/stylesheets/framework/filters.scss:
Compound selectors may no longer be extended.
Consider `@extend .form-control, :hover` instead.
See http://bit.ly/ExtendCompound for details.   
  
 
WARNING on line 31, column 13 of 
/usr/share/gitlab/app/assets/stylesheets/pages/help.scss:
Compound selectors may no longer be extended.
Consider `@extend .badge, .badge-pill` instead.
See http://bit.ly/ExtendCompound for details.

WARNING on line 665, column 13 of 
/usr/share/gitlab/app/assets/stylesheets/pages/issuable.scss:
Compound selectors may no longer be extended.
Consider `@extend a, :hover` instead.
See http://bit.ly/ExtendCompound for details.

WARNING on line 580, column 15 of 
/usr/share/gitlab/app/assets/stylesheets/pages/pipelines.scss:
Compound selectors may no longer be extended.
Consider `@extend .build-content, :hover` instead.
See http://bit.ly/ExtendCompound for details.

 snip --

Is there a known workaround for that issue?

Apparently, at least for me, a clean upgrade of gitlab is not possible
right now.

Best,
Maximilian
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#976879: marked as done (gitlab: Missing dependency on "file" (being used in postinst script))

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #976879,
regarding gitlab: Missing dependency on "file" (being used in postinst script)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 13.4.6-1~fto10+1
Severity: normal

Dear Maintainer,

there are two occurrences of "file" being called in the postinst script.

One example is the following:

> if [ "$(file /etc/gitlab/ssl/gitlab.crt|awk '{ print $NF }')" = 
> "/etc/letsencrypt/live/${GITLAB_HOST}/fullchain.pem" ]; then

Thus the gitlab package should probably depend on the "file" package.

Thank you for maintaining the gitlab package!

Cheers,
Lars
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#972754: marked as done (gitlab: Uploading images to issues fails due to missing dependency on libimage-exiftool-perl)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #972754,
regarding gitlab: Uploading images to issues fails due to missing dependency on 
libimage-exiftool-perl
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
972754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 the package manually indeed
fixed the issue and I can now upload images again.

Thanks for your commitment!

Best
Maximilian

[1]: https://gitlab.com/gitlab-org/gitlab-foss/-/issues/60853#note_165956481
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#968286: marked as done (gitlab: adding log rotation)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #968286,
regarding gitlab: adding log rotation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
968286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 13.1.6-1+fto10+1
Severity: wishlist
Tags: patch

Gitlab usage with tens of people specially with CI lead to huge log files which 
should be rotated. This feature does not exist for instance in 13.1.6-1+fto10+1 
version.

To achieve that I used the following configuration file located in 
/etc/logrotate.d/gitlab: 

/var/log/gitlab/*.log {
   daily
   rotate 15
   copytruncate
   delaycompress
   compress
   notifempty
   missingok
}

As I don't know how to tell gitlab to stop writing logs during rotation, I 
choose to inspire myself on postgresql configuration which handle that using 
copytruncate and delaycompress options.

This configuration should rotate log every day and purge logs older than 15 
days. You may want to tweak these parameters. 

Hopefully this will be helpfull,

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 10.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 
'buster-fasttrack'), (100, 'buster-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gitlab depends on:
ii  asciidoctor2.0.10-2~bpo10+1
ii  bc 1.07.1-2+b1
ii  bundler2.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  exim4-daemon-light [mail-transport-agent]  4.94-7~bpo10+1
ii  gitlab-common  13.1.0+dfsg-1~bpo10+1
ii  gitlab-workhorse   8.37.0+debian-1~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-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+deb10u2
ii  nginx-full [nginx] 1.14.2-2+deb10u2
ii  node-autosize  4.0.2~dfsg1-3
ii  node-axios 0.17.1+dfsg-2
ii  node-babel-loader  8.1.0-3~bpo10+1
ii  node-babel77.4.5+~cs7.3.8-1~bpo10+1
ii  node-brace-expansion   1.1.8-1
ii  node-cache-loader  4.1.0-1~bpo10+1
ii  node-chart.js  2.7.3+dfsg-5
ii  node-clipboard 2.0.6+ds-1~bpo10+1
ii  node-compression-webpack-plugin3.0.1-1~bpo10+1
ii  node-core-js   3.6.1-2~bpo10+2
ii  node-css-loader2.1.1-1~bpo10+1
ii  node-d35.16.0-1~bpo10+1
ii  node-d3-scale  2.2.2-2~bpo10+1
ii  node-d3-selection  1.4.0-3~bpo10+1
ii  node-dateformat3.0.0-1
ii  node-exports-loader0.7.0-2~bpo10+1
ii  node-fuzzaldrin-plus   0.5.0+dfsg-1
ii  node-glob  7.1.6-1~bpo10+1
ii  node-imports-loader0.8.0-2~bpo10+1
ii  node-jed   1.1.1-1
ii  node-jquery3.4.0+dfsg-1~bpo10+1
ii  node-jquery-ujs1.2.2-2
ii  node-js-cookie 2.2.0-2
ii  node-jszip 3.2.2+dfsg-1~bpo10+1
ii  node-jszip-utils   0.0.2+dfsg-1
ii  

Bug#964193: marked as done (gitlab: 500 Errrors at log in because of missing setting in gitlab.yml)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #964193,
regarding gitlab: 500 Errrors at log in because of missing setting in gitlab.yml
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
964193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 13.1.2-1+fto10+1
Severity: normal

I upgraded from 12.10.3-1+fto10+1 to 13.1.2-1+fto10+1 and when trying to
login after that, I got 500 errors.

Error from production log:

Settingslogic::MissingSetting (Missing setting 
'admin_area_protected_paths_enabled' in 'rack_attack' section in 
/etc/gitlab/gitlab.yml):

config/initializers/rack_attack_new.rb:18:in 
`should_use_omnibus_protected_paths?'
config/initializers/rack_attack_new.rb:11:in `protected_paths_enabled?'
config/initializers/rack_attack_new.rb:90:in `block in '
lib/gitlab/middleware/read_only/controller.rb:51:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/same_site_cookies.rb:27:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/middleware/handle_ip_spoof_attack_error.rb:25:in `call'
lib/gitlab/middleware/request_context.rb:23:in `call'
config/initializers/fix_local_cache_middleware.rb:9:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:60:in `call'
lib/gitlab/middleware/release_env.rb:12:in `call'


I hadd to add 
admin_area_protected_paths_enabled: true

to gitlab.yml to make it work.

/etc/gitlab/gitlab.yml.example does not contain this option, nor could I
find much information about this specific option documented online. This
should be at least in gitlab.yml.example.


-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'proposed-updates'), (640, 
'buster-backports'), (630, 'buster-fasttrack'), (600, 'oldstable'), (550, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'testing'), (200, 
'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  apache2 [httpd]2.4.38-3+deb10u3
ii  asciidoctor2.0.10-2~bpo10+1
ii  bc 1.07.1-2+b1
ii  bundler1.17.3-3
ii  bzip2  1.0.6-9.2~deb10u1
ii  dbconfig-pgsql 2.0.11+deb10u1
ii  debconf [debconf-2.0]  1.5.71
ii  gitlab-common  13.1.0+dfsg-1~bpo10+1
ii  gitlab-workhorse   8.36.0+debian-1~bpo10+1
ii  libjs-bootstrap4 [node-bootstrap]  4.3.1+dfsg2-1
ii  libjs-popper.js [node-popper.js]   1.14.6+ds2-1
ii  libjs-uglify   2.8.29-6
ii  lsb-base   10.2019051400
ii  node-autosize  4.0.2~dfsg1-3
ii  node-axios 0.17.1+dfsg-2
ii  node-babel-loader  8.1.0-3~bpo10+1
ii  node-babel77.4.5+~cs7.3.8-1~bpo10+1
ii  node-brace-expansion   1.1.8-1
ii  node-cache-loader  4.1.0-1~bpo10+1
ii  node-chart.js  2.7.3+dfsg-5
ii  node-clipboard 2.0.6+ds-1~bpo10+1
ii  node-compression-webpack-plugin3.0.1-1~bpo10+1
ii  node-core-js   3.6.5-1
ii  node-css-loader2.1.1-1~bpo10+1
ii  node-d3-scale  2.2.2-2
ii  node-d3-selection  1.4.0-5
ii  node-dateformat3.0.0-1
ii  node-exports-loader0.7.0-2~bpo10+1
ii  node-fuzzaldrin-plus   0.5.0+dfsg-1
ii  node-glob  7.1.6-1~bpo10+1
ii  node-imports-loader0.8.0-2~bpo10+1
ii  node-jed   1.1.1-1
ii  node-jquery3.5.1+dfsg-4
ii  node-jquery-ujs

Bug#958445: marked as done (gitlab: 500 error on two-factor auth page)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #958445,
regarding gitlab: 500 error on two-factor auth page
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
958445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 12.9.3+dfsg-1+fto10+1
Severity: normal

Dear Maintainer,

When opening /profile/two_factor_auth to set up 2FA on my account, I get
a 500 internal server error.

Log contains this:

Processing by Profiles::TwoFactorAuthsController#show as HTML
Completed 500 Internal Server Error in 176ms (ActiveRecord: 2.5ms | 
Elasticsearch: 0.0ms | Allocations: 14662)
  
NoMethodError (undefined method `set_attribute_was' for #
Did you mean?  custom_attributes):
  
app/controllers/profiles/two_factor_auths_controller.rb:8:in `show'
app/controllers/application_controller.rb:479:in `set_current_admin'
lib/gitlab/session.rb:11:in `with_session'
app/controllers/application_controller.rb:470:in `set_session_storage'
lib/gitlab/i18n.rb:55:in `with_locale'
lib/gitlab/i18n.rb:61:in `with_user_locale'
app/controllers/application_controller.rb:464:in `set_locale'
lib/gitlab/error_tracking.rb:34:in `with_context'
app/controllers/application_controller.rb:555:in `sentry_context'
lib/gitlab/application_context.rb:46:in `block in use'
lib/gitlab/application_context.rb:46:in `use'
lib/gitlab/application_context.rb:19:in `with_context'
app/controllers/application_controller.rb:455:in `set_current_context'
lib/gitlab/request_profiler/middleware.rb:17:in `call'
lib/gitlab/middleware/go.rb:20:in `call'
lib/gitlab/etag_caching/middleware.rb:13:in `call'
lib/gitlab/middleware/multipart.rb:122:in `call'
lib/gitlab/middleware/read_only/controller.rb:53:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/middleware/request_context.rb:23:in `call'
config/initializers/fix_local_cache_middleware.rb:9:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:49:in `call'
lib/gitlab/middleware/release_env.rb:12:in `call'


-- System Information:
Debian Release: 10.3
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'proposed-updates'), (640, 
'buster-backports'), (630, 'buster-fasttrack'), (600, 'oldstable'), (550, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'testing'), (200, 
'unstable'), (160, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  apache2 [httpd] 2.4.38-3+deb10u3
ii  asciidoctor 2.0.10-2~bpo10+1
ii  bc  1.07.1-2+b1
ii  bundler 1.17.3-3
ii  bzip2   1.0.6-9.2~deb10u1
ii  dbconfig-pgsql  2.0.11+deb10u1
ii  debconf [debconf-2.0]   1.5.71
ii  gitlab-common   12.9.3+dfsg-1~bpo10+1
ii  gitlab-workhorse8.30+debian-1~bpo10+1
ii  libjs-bootstrap4 [node-bootstrap]   4.3.1+dfsg2-1
ii  libjs-popper.js [node-popper.js]1.14.6+ds2-1
ii  libjs-uglify2.8.29-6
ii  lsb-base10.2019051400
ii  node-autosize   4.0.2~dfsg1-3
ii  node-axios  0.17.1+dfsg-2
ii  node-brace-expansion1.1.8-1
ii  node-chart.js   2.7.3+dfsg-5
ii  node-clipboard  2.0.6+ds-1~bpo10+1
ii  node-core-js3.6.1-3
ii  node-css-loader 1.0.1-1
ii  node-d3-scale   2.2.2-2
ii  node-d3-selection   1.4.0-5
ii  node-dateformat 3.0.0-1
ii  node-exports-loader 0.7.0-2~bpo10+1
ii  node-fuzzaldrin-plus0.5.0+dfsg-1
ii  node-glob   7.1.3-2
ii  node-imports-loader 0.8.0-2~bpo10+1
ii  node-jed1.1.1-1
ii  node-jquery 3.4.0+dfsg-1
ii  node-jquery-ujs 1.2.2-2
ii  node-js-cookie  2.2.0-2
ii  

Bug#955332: marked as done (gitlab : Gitlab systemdless / apache2)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #955332,
regarding gitlab : Gitlab systemdless / apache2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
955332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 12.6.8-1+fto10+1

I try to make gitlab running in a systemdless system and using apache2
instead of nginx.

I have this error :

Traceback (most recent call last):
13: from /usr/bin/unicorn_rails:209:in `'
12: from /usr/bin/unicorn_rails:209:in `new'
11: from /usr/lib/ruby/vendor_ruby/unicorn/http_server.
rb:77:in `initialize'
10: from /usr/lib/ruby/vendor_ruby/unicorn/http_server.
rb:77:in `new'
 9: from /usr/lib/ruby/vendor_ruby/unicorn/configurator
.rb:77:in `initialize'
 8: from /usr/lib/ruby/vendor_ruby/unicorn/configurator
.rb:92:in `reload'
 7: from /usr/bin/unicorn_rails:202:in `block in 
'
 6: from /usr/lib/ruby/2.5.0/fileutils.rb:193:in `mkdir
_p'
 5: from /usr/lib/ruby/2.5.0/fileutils.rb:193:in `each'

 4: from /usr/lib/ruby/2.5.0/fileutils.rb:208:in `block
 in mkdir_p'
 3: from /usr/lib/ruby/2.5.0/fileutils.rb:208:in `rever
se_each'
 2: from /usr/lib/ruby/2.5.0/fileutils.rb:210:in `block
 (2 levels) in mkdir_p'
 1: from /usr/lib/ruby/2.5.0/fileutils.rb:232:in `fu_mk
dir'
/usr/lib/ruby/2.5.0/fileutils.rb:232:in `mkdir': Permission den
ied @ dir_s_mkdir - tmp/cache (Errno::EACCES)
master failed to start, check stderr log for details

After search the error come from

ls -al /run/gitlab/
total 0
drwxr-xr-x  3 root root   60 mars  25 20:09 .
drwxr-xr-x 30 root root 1080 mars  30 00:50 ..
drwxr-xr-x  3 root root   60 mars  25 20:09 sockets

a chown look missing somewhere (or done in systemd unit)

chown gitlab:gitlab /run/gitlab/

after that a restart the directory look like that :

ls -al /run/gitlab/
total 12
drwxr-xr-x  6 gitlab gitlab  200 mars  30 02:27 .
drwxr-xr-x 30 root   root   1080 mars  30 00:50 ..
drwx--  2 gitlab gitlab   40 mars  30 02:23 cache
srwxrwxrwx  1 gitlab gitlab0 mars  30 02:27 gitlab.socket
-rw---  1 gitlab gitlab4 mars  30 02:27 gitlab-workhorse.pid
drwx--  2 gitlab gitlab   40 mars  30 02:23 pids
drwx--  2 gitlab gitlab   40 mars  30 02:23 sessions
-rw---  1 gitlab gitlab5 mars  30 02:27 sidekiq.pid
drwxr-xr-x  3 root   root 60 mars  25 20:09 sockets
-rw---  1 gitlab gitlab4 mars  30 02:23 unicorn.pid


but the check script

runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && .
/etc/gitlab/gitlab-debian.conf && export DB RAILS_ENV && bundle exec
rake gitlab:check RAILS_ENV=production'

shows :

Sidekiq: ... Running? ... no
  Try fixing it:
  sudo -u gitlab -H RAILS_ENV=production bin/background_jobs start
  For more information see:
  doc/install/installation.md in section "Install Init Script"
  see log/sidekiq.log for possible errors
  Please fix the error above and rerun the checks.

and the restart always output (service gitlab restart) :

The GitLab Workhorse is not running.

but at least web UI look good. I will try commit/push in few hours.


I also have a bunch of warning during check and not present in restart :

/usr/share/gitlab/lib/gitlab.rb:38: warning: already initialized
constant Gitlab::COM_URL
/usr/share/gitlab/lib/gitlab.rb:38: warning: previous definition of
COM_URL was here
/usr/share/gitlab/lib/gitlab.rb:39: warning: already initialized
constant Gitlab::APP_DIRS_PATTERN
/usr/share/gitlab/lib/gitlab.rb:39: warning: previous definition of
APP_DIRS_PATTERN was here
/usr/share/gitlab/lib/gitlab.rb:40: warning: already initialized
constant Gitlab::SUBDOMAIN_REGEX
/usr/share/gitlab/lib/gitlab.rb:40: warning: previous definition of
SUBDOMAIN_REGEX was here
/usr/share/gitlab/lib/gitlab.rb:41: warning: already initialized
constant Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of
VERSION was here
/usr/share/gitlab/lib/gitlab.rb:42: warning: already initialized
constant Gitlab::INSTALLATION_TYPE
/usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of
INSTALLATION_TYPE was here
/usr/share/gitlab/lib/gitlab.rb:43: warning: already initialized
constant Gitlab::HTTP_PROXY_ENV_VARS
/usr/share/gitlab/lib/gitlab.rb:43: warning: previous definition of
HTTP_PROXY_ENV_VARS was here
/usr/share/gitlab/config/initializers/2_app.rb:6: warning: already
initialized 

Bug#940709: marked as done (Possible improvements to gitlab init script)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #940709,
regarding Possible improvements to gitlab init script
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
940709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gitlab
version: 12.0.9-1
Severity: wishlist

1. Since gitaly has a sepatate init script, can't we declare a 
dependency on gitaly instead of starting it in gitlab?

2. Can we add postgres and nginx as dependencies?

--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#930404: marked as done ([Meta] move gitlab back to main from contrib)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #930404,
regarding [Meta] move gitlab back to main from contrib
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
930404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 11.8.10+dfsg-1
Severity: wishlist
Control: block -1 by 863293
Control: block -1 by 930372

This is a meta bug to track progress of packaging node dependencies.


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#915050: marked as done (Keep out of testing)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #915050,
regarding Keep out of testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
915050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab
Severity: serious

Gitlab is too fast-moving with weekly releases and backporting security fixes 
has already
failed us for stretch, keep it out of testing.

To meaningfully support it for use on stable, this would require some of the
infrastructure/policy changes discussed in the "What can Debian do to provide
complex applications to its users" thread from earlier the year on debian-devel.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#914159: marked as done (gitlab: Problem with GPG Keys)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #914159,
regarding gitlab: Problem with GPG Keys
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
914159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 11.1.8+dfsg-2
Severity: normal

After install 11.1.8, importing GPG keys isn't working.

This failure isn't present at 10.8 previous version on Testing.

When I try to upload my GPG key, gitlab gives a 500 internal server error. 
After reloading, key are added but without reading the complete key (I think, 
beucase gitlab only have detected one of the emails on the key).

Error message on production.log are:

Started POST "/profile/gpg_keys" for x.x.x.x at 2018-11-20 01:30:26 +0100
Processing by Profiles::GpgKeysController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]", 
"gpg_key"=>"[FILTERED]", "commit"=>"Add key"}
Completed 500 Internal Server Error in 82ms (ActiveRecord: 1.6ms)

GPGME::Error (Unsupported protocol):
  lib/gitlab/gpg.rb:15:in `fingerprints_from_key'
  lib/gitlab/gpg.rb:25:in `block in fingerprints_from_key'
  lib/gitlab/gpg.rb:93:in `optimistic_using_tmp_keychain'
  lib/gitlab/gpg.rb:75:in `block in using_tmp_keychain'
  lib/gitlab/gpg.rb:74:in `synchronize'
  lib/gitlab/gpg.rb:74:in `using_tmp_keychain'
  lib/gitlab/gpg.rb:24:in `fingerprints_from_key'
  app/models/gpg_key.rb:111:in `extract_fingerprint'
  app/services/gpg_keys/create_service.rb:4:in `execute'
  app/controllers/profiles/gpg_keys_controller.rb:10:in `create'
  lib/gitlab/i18n.rb:51:in `with_locale'
  lib/gitlab/i18n.rb:57:in `with_user_locale'
  app/controllers/application_controller.rb:362:in `set_locale'
  lib/gitlab/middleware/multipart.rb:97:in `call'
  lib/gitlab/request_profiler/middleware.rb:14:in `call'
  lib/gitlab/middleware/go.rb:17:in `call'
  lib/gitlab/etag_caching/middleware.rb:11:in `call'
  lib/gitlab/middleware/read_only/controller.rb:38:in `call'
  lib/gitlab/middleware/read_only.rb:16:in `call'
  lib/gitlab/request_context.rb:18:in `call'
  lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'
  lib/gitlab/middleware/release_env.rb:10:in `call'


Started GET "/favicon.ico" for x.x.x.x at 2018-11-20 01:30:26 +0100
Started POST "/profile/gpg_keys" for x.x.x.x at 2018-11-20 01:30:32 +0100
Processing by Profiles::GpgKeysController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]", 
"gpg_key"=>"[FILTERED]", "commit"=>"Add key"}
[ActiveJob] Enqueued ActionMailer::DeliveryJob (Job ID: 
10f8706f-4e6c-4218-ac69-db767782315a) to Sidekiq(mailers) with arguments: 
"Notify", "new_gpg_key_email", "deliver_now", 5
Redirected to https://git.example.com/profile/gpg_keys
Completed 302 Found in 1687ms (ActiveRecord: 184.4ms)

On 10.8 version, if I add my GPG key to my profile, I can see all my emails. 
Now, on 11.1, I only see one email. I've tested it with the same key always, 
but now I didn't have a 10.8 debian installation for re-testing and getting 
information from the logfile.

After searching for this bug on gitlab-ce official repository, I can only find 
cases with 9.5 version, when gitlab didn't support subkeys. Maybe that's a 
problem with the packaging.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  asciidoctor1.5.7.1-1
ii  bc 1.07.1-2+b1
ii  bundler1.16.1-3
ii  bzip2  1.0.6-9
ii  dbconfig-pgsql 2.0.10
ii  debconf [debconf-2.0]  1.5.69
ii  exim4-daemon-light [mail-transport-agent]  4.91-8+b1
ii  gitlab-common  11.1.8+dfsg-2
ii  gitlab-shell   7.2.0+dfsg-1
ii  gitlab-workhorse   5.2.0+debian-2
ii  lsb-base   9.20170808
ii  nginx  1.14.1-1
ii  nginx-full [nginx] 1.14.1-1
ii  nodejs

Bug#909630: marked as done (gitlab: no sysvinit scripts installed or available)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #909630,
regarding gitlab: no sysvinit scripts installed or available
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
909630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Severity: important


gitlab started up from "apt-get install gitlab" however it proved necessary
to kill the manually-started services that the postinst script had started.

when it came to restarting the unicorn, sidekiq etc. services it was only
then discovered that there was absolutely no way to do so.

it would be really helpful if people could stop assuming that everyone
forcibly fucking wants systemd shoved at them.  and no, ordering people
to go use freebsd or devuan is not acceptable.

for goodness sake please be a little more careful and considerate.
i'll try to track down some sysvinit scripts in a followup and post
them later.


-- System Information:
Debian Release: 8.1
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#901338: marked as done (gitlab: dependency on postgresql-contrib pulls in postgresql server)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #901338,
regarding gitlab: dependency on postgresql-contrib pulls in postgresql server
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
901338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 10.7.5+dfsg-2~bpo9+1
Severity: normal

Dear Maintainer,

gitlab depends on postgresql-client and postgresql-contrib. The latter
pulls in the postgresql server package, and because postgresql itself
already depends on postgresql-client, the explicit dependency on
postgresql-client in gitlab is actually useless.

Personally I already have a postgresql server running on another host,
which I want to use for gitlab, so I would prefer a suggest or recommend
dependency instead of a hard dependency.

-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (600, 'stable'), (550, 'proposed-updates'), (500, 'oldstable'), 
(450, 'oldstable-proposed-updates'), (420, 'testing'), (200, 'unstable'), (160, 
'experimental'), (150, 'oldoldstable'), (140, 'oldoldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  adduser3.115
ii  apache2 [httpd]2.4.25-3+deb9u4
ii  asciidoctor1.5.6.2-2~bpo9+1
ii  bc 1.06.95-9+b3
ii  bundler1.13.6-2
ii  dbconfig-pgsql 2.0.9~bpo9+1
ii  debconf [debconf-2.0]  1.5.61
ii  git1:2.17.1-1~bpo9+1
ii  gitlab-shell   7.1.2+dfsg-2~bpo9+1
ii  gitlab-workhorse   4.2.1+debian-2~bpo9+1
ii  init-system-helpers1.48
ii  lsb-base   9.20161125
ii  nodejs 8.11.1~dfsg-2~bpo9+1
ii  npm1.4.21+ds-2~bpo9+1
ii  openssh-client 1:7.4p1-10+deb9u3
ii  postfix [mail-transport-agent] 3.1.8-0+deb9u1
ii  postgresql-client  9.6+181+deb9u1
ii  postgresql-client-9.6 [postgresql-client]  9.6.7-0+deb9u1
ii  postgresql-contrib 9.6+181+deb9u1
ii  rake   12.3.1-1~bpo9+1
ii  redis-server   5:4.0.9-2~bpo9+1
ii  ruby   1:2.3.3
ii  ruby-ace-rails-ap  4.1.1-1
ii  ruby-acts-as-taggable-on   5.0.0-2~bpo9+1
ii  ruby-addressable   2.5.2-1~bpo9+1
ii  ruby-akismet   2.0.0-1
ii  ruby-allocations   1.0.3-1+b2
ii  ruby-arel  6.0.4-1~bpo9+1
ii  ruby-asana 0.6.0-1~bpo9+1
ii  ruby-asciidoctor-plantuml  0.0.8-1~bpo9+1
ii  ruby-asset-sync2.2.0-2~bpo9+1
ii  ruby-attr-encrypted3.1.0-1~bpo9+1
ii  ruby-babosa1.0.2-2
ii  ruby-base320.3.2-3
ii  ruby-batch-loader  1.2.1-1~bpo9+1
ii  ruby-bcrypt-pbkdf  1.0.0-1~bpo9+1
ii  ruby-bootstrap-form2.7.0-1~bpo9+1
ii  ruby-bootstrap-sass3.3.5.1-5
ii  ruby-browser   2.2.0-2
ii  ruby-carrierwave   1.2.2-1~bpo9+1
ii  ruby-charlock-holmes   0.7.5-1~bpo9+1
ii  ruby-chronic   0.10.2-3
ii  ruby-chronic-duration  0.10.6-1
ii  ruby-commonmarker  0.17.9-1~bpo9+1
ii  ruby-connection-pool   2.2.0-1
ii  ruby-creole0.5.0-2
ii  ruby-d3-rails  3.5.6+dfsg-1
ii  ruby-default-value-for 3.0.1-1
ii  ruby-devise4.4.3-1~bpo9+1
ii  ruby-devise-two-factor 3.0.0-2
ii  ruby-diffy   

Bug#909840: marked as done (gitlab: not suitable for stable Debian releases)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #909840,
regarding gitlab: not suitable for stable Debian releases
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
909840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Severity: serious

Looking at #909315 I doubt we can security support
gitlab in buster until the non-LTS EOL of buster mid-2022.
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#901379: marked as done (gitlab: postinst script should not call psql if database is not managed by dbconfig-common)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #901379,
regarding gitlab: postinst script should not call psql if database is not 
managed by dbconfig-common
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
901379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 10.7.5+dfsg-2~bpo9+1
Severity: normal

Dear Maintainer,

the gitlab.postinst script fails to enable the pg_trgm extension if
there is no locally running postgresql database:

Setting up gitlab (10.7.5+dfsg-2~bpo9+1) ...
Creating/updating gitlab user account...
Making gitlab owner of /var/lib/gitlab...
Creating runtime directories for gitlab...
Updating file permissions...
Configuring hostname and email...
Configuring nginx with HTTPS...
Configuring gitlab with HTTPS...
Updating gitlab_url in gitlab-shell configuration...
Registering /usr/lib/tmpfiles.d/gitlab.conf via ucf
/etc/systemd/system/gitlab-mailroom.service.d/override.conf already
exist
/etc/systemd/system/gitlab-unicorn.service.d/override.conf already exist
/etc/systemd/system/gitlab-sidekiq.service.d/override.conf already exist
/etc/systemd/system/gitlab-workhorse.service.d/override.conf already
exist
Registering /etc/gitlab-shell/config.yml via ucf
Registering /etc/gitlab/gitlab.yml via ucf
Registering /etc/gitlab/gitlab-debian.conf via ucf
dbconfig-common: writing config to /etc/dbconfig-common/gitlab.conf
dbconfig-common: flushing administrative password
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.5432"?
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned
 error exit status 2

I chose to not manage the postgresql database by dbconfig because I am using
an externally running database. In that case this command should not be run.


-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (600, 'stable'), (550, 'proposed-updates'), (500, 'oldstable'), 
(450, 'oldstable-proposed-updates'), (420, 'testing'), (200, 'unstable'), (160, 
'experimental'), (150, 'oldoldstable'), (140, 'oldoldstable-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  adduser3.115
ii  apache2 [httpd]2.4.25-3+deb9u4
ii  asciidoctor1.5.6.2-2~bpo9+1
ii  bc 1.06.95-9+b3
ii  bundler1.13.6-2
ii  dbconfig-pgsql 2.0.9~bpo9+1
ii  debconf [debconf-2.0]  1.5.61
ii  git1:2.17.1-1~bpo9+1
ii  gitlab-shell   7.1.2+dfsg-2~bpo9+1
ii  gitlab-workhorse   4.2.1+debian-2~bpo9+1
ii  init-system-helpers1.48
ii  lsb-base   9.20161125
ii  nodejs 8.11.1~dfsg-2~bpo9+1
ii  npm1.4.21+ds-2~bpo9+1
ii  openssh-client 1:7.4p1-10+deb9u3
ii  postfix [mail-transport-agent] 3.1.8-0+deb9u1
ii  postgresql-client  9.6+181+deb9u1
ii  postgresql-client-9.6 [postgresql-client]  9.6.7-0+deb9u1
ii  postgresql-contrib 9.6+181+deb9u1
ii  rake   12.3.1-1~bpo9+1
ii  redis-server   5:4.0.9-2~bpo9+1
ii  ruby   1:2.3.3
ii  ruby-ace-rails-ap  4.1.1-1
ii  ruby-acts-as-taggable-on   5.0.0-2~bpo9+1
ii  ruby-addressable   2.5.2-1~bpo9+1
ii  ruby-akismet   2.0.0-1
ii  ruby-allocations   1.0.3-1+b2
ii  ruby-arel  6.0.4-1~bpo9+1
ii  ruby-asana 0.6.0-1~bpo9+1
ii  ruby-asciidoctor-plantuml  

Bug#897444: marked as done (Gitlab: Change repository path does not work)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #897444,
regarding Gitlab: Change repository path does not work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
897444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 10.6.5+dfsg-1
Severity: normal

Changing gitlab repository path does not work.

Checking installation give this:

GitLab Shell version >= 6.0.4 ? ... OK (6.0.4)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by gitlab:root, or gitlab:gitlab?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ... 
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty
x / x ... repository is empty

Configuration changes:

/etc/gitlab/gitlab.yml

  #
  # 4. Advanced settings
  # ==

  ## Repositories settings
  repositories:
storages: # You must have at least a `default` storage path.
  default:
path: /home/repositories/
#path: /var/lib/gitlab/repositories/


/etc/gitlab-shell/config.yml

# Repositories path
# Give the canonicalized absolute pathname,
# REPOS_PATH MUST NOT CONTAIN ANY SYMLINK!!!
# Check twice that none of the components is a symlink, including "/home".
#repos_path: "/var/lib/gitlab/repositories"
repos_path: "/home/repositories"


/etc/gitaly/config.toml

[[storage]]
name = "default"
#path = "/var/lib/gitlab/repositories"
path = "/home/repositories"


Gitlab starts correctly. On Admin Area -> Overview -> Projects I can see all 
repositories with their size computed.
On Gitlab interface, entering any project I see message "No repository". At 
database level, "repository_storage" column contains "default", not any 
absolute path.
Entering on /home/repositories and going to some correct namespace (group / 
project) I can do a git log and see information.
Path are not a symlink. /home is a complete mount point and repositories is a 
folder inside it. Permission are correct (drwxrws--- 11 gitlab   gitlab
4096 Nov  4 20:01 repositories).

Where's the problem? Maybe I failed changing some configuration? I'm missing 
some file for detect it correctly?


Thanks for your help.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  adduser3.117
ii  asciidoctor1.5.6.2-2
ii  bc 1.07.1-2
ii  bundler1.16.1-1
ii  dbconfig-pgsql 2.0.9
ii  debconf [debconf-2.0]  1.5.66
ii  exim4-daemon-light [mail-transport-agent]  4.91-3
ii  git1:2.17.0-1
ii  gitlab-shell   6.0.4+dfsg-1
ii  gitlab-workhorse   4.0.0+debian-1
ii  lsb-base   9.20170808
ii  nginx  1.13.12-1
ii  nginx-full [nginx] 1.13.12-1
ii  nodejs 8.11.1~dfsg-2
ii  npm1.4.21+ds-2
ii  openssh-client 1:7.7p1-2
ii  

Bug#890399: marked as done (gitlab: override.conf in /etc/systemd/system/gitlab-*.service.d is not overwriten)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #890399,
regarding gitlab: override.conf in /etc/systemd/system/gitlab-*.service.d is 
not overwriten
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
890399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 9.5.4.+dfsg-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
another problem. 
If admin creates for example:
/etc/systemd/system/gitlab-sidekiq.service.d/override.conf
by hand, changing properties other than User, then postinst script fails to 
update User property.
My file is
#[Service]
#Restart=always

so no User to change by sed inside postinst.

I don't know if some debian policy on naming such override files exists, but 
can you use for example
gitlab(-user).conf ? It is also parsed and included by systemd.

Also systemd doesn't like
EnvironmentFile=-/etc/default/gitlab
in /lib/systemd/system/gitlab-unicorn.service

service doesn't start because of
Feb 14 12:35:41 ms-gitlab systemd[1]: gitlab-unicorn.service: Ignoring invalid 
environment assignment 'for i in $(grep -v '#' /etc/gitlab/gitlab-debian.conf | 
cut -d=-f 1)': /etc/default/gitlab


Thanks,
Libor

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlqEIHwVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOdhQQAJZ4dwoDavpwDz8m7+0JhbXyYOrz
CJYSC/Z9v5bQNvNqj771GXuWdwIxd3sAudwJShctYZWJA51d4gl9wPJ9WZf1FX70
kYrrsyWm48fyHv1BSsk4rbgbYGQ5Pc5yZx7L/ekbZohKf+2IR0fgg+nPxtJ5pxnG
g7/uIST+uQS3O66nRvkWccelnP/X0xIO/oiVAvCaI75Jj5YYx3ziyD9XyNx6NEoS
NwEy0QQdPvBfJvHq/qS30fDbtkMdP4YMi0mbqb32+FBq0yxt8MCKoYFWSBEqdPV+
VXyeFkMNXxJd6Z/lZoRDnVJXepmBdhowVDdj5a28EHrVra+8hCYiQO4/xurnEXPO
ACbFUFAgLOCC+9vyGe7fRZ2BpfeSmA/h1scPe9lXLE9WN2iyqlAmBO8RPLPTTcsd
VybEkzkb9RbpqFgrgbqfkBCcH7e+RAsySeJQiZA3XKcPG9VoefcqNq5rRSt5OxuI
0adii49pbRLjL493v73FdCC+6GnlDrdgi9XX6/jqwX6jg3ofwjXI5MCzWJ8jrdvW
94QX9qbs7NfY7EjBrKwrRnXzDRlMKAZENwCzoUYV8pR+FIRDOAiYCSdZT+48jdvQ
HPnCqSRNybeqMTTS1/yrMLZHtXDOtzP38nsVYFmsYZOQ5zMV7RGS84Pspf4aI6QV
DvgsPm8FpIEhPZ2e
=IcDF
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#886657: marked as done (gitlab postinst failing when 'apt-get install' or 'reconfigure' when CWD not accessible to gitlab user)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #886657,
regarding gitlab postinst failing when 'apt-get install' or 'reconfigure' when 
CWD not accessible to gitlab user
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
886657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.11+dfsg1-8
Severity: important

Dear Maintainer,

   * What led up to the situation?
   I am installing the gitlab package (and reconfiguring it) when in a specific 
directory /root/ or even a subdirectory therein which has rights : drwx-- 1 
root root
   In such a case the (re)configuration stops soon after finishing to ask 
questions, with an error :

root@test-stretch-bpo:~# ls -lad .
drwx-- 10 root root 4096 janv.  8 16:18 .

root@test-stretch-bpo:~# LANG=C dpkg-reconfigure gitlab
Creating/updating gitlab user account...
Making gitlab owner of /var/lib/gitlab...
Creating runtime directories for gitlab...
Updating file permissions...
fatal: Cannot come back to cwd: Permission denied

   When investigating the root cause of this crash I realised it happens in the 
postinst script of gitlab package a bit after line 124 (echo "Updating file 
permissions...") and I think it is on the 'runuser' call of line 132 ? 

   When, conversely, I run the same command (apt-get install or 
dpk-reconfigure) from within a «world readable directory '/tmp' or '/etc') 
everything goes ok.

   Thank you for finding a solution to this annoying bug, which prevent some 
automatic installation and (re)configuration of the gitlab package.

Sincerely,

Serge Cohen.

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-0.bpo.2-amd64 (SMP w/2 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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  adduser   3.115
ii  apache2 [httpd]   2.4.25-3+deb9u3
ii  asciidoctor   1.5.4-2
ii  bc1.06.95-9+b3
ii  bundler   1.13.6-2
ii  dbconfig-pgsql2.0.9~bpo9+1
ii  debconf [debconf-2.0] 1.5.61
ii  git   1:2.14.2-1~bpo9+1
ii  gitlab-shell  3.6.6-4
ii  gitlab-workhorse  0.8.5+debian-3+b2
ii  init-system-helpers   1.48
ii  libjs-chartjs 1.0.2-1
ii  libjs-clipboard   1.4.2-1
ii  libjs-fuzzaldrin-plus 0.3.1+git.20161008.da2cb58+dfsg-4
ii  libjs-graphael0.5+dfsg-1
ii  libjs-jquery-cookie   11-3
ii  libjs-jquery-history  11-3
ii  libjs-jquery-nicescroll   3.6.6-1
ii  lsb-base  9.20161125
ii  nodejs4.8.2~dfsg-1
ii  openssh-client1:7.4p1-10+deb9u2
ii  postfix [mail-transport-agent]3.1.6-0+deb9u1
ii  postgresql-client-9.6 [postgresql-client  9.6.6-0+deb9u1
ii  postgresql-contrib9.6+181+deb9u1
ii  rake  10.5.0-2
ii  redis-server  5:4.0.6-1~bpo9+1
ii  ruby  1:2.3.3
ii  ruby-ace-rails-ap 4.1.1-1
ii  ruby-activerecord-session-store   1.0.0-2
ii  ruby-acts-as-taggable-on  4.0.0-2
ii  ruby-addressable  2.4.0-1
ii  ruby-after-commit-queue   1.3.0-1
ii  ruby-akismet  2.0.0-1
ii  ruby-allocations  1.0.3-1+b2
ii  ruby-asana0.4.0-1
ii  ruby-attr-encrypted   3.0.1-2
ii  ruby-babosa   1.0.2-2
ii  ruby-base32   0.3.2-3
ii  ruby-bootstrap-sass   3.3.5.1-5
ii  ruby-browser  2.2.0-2
ii  ruby-cal-heatmap-rails3.6.0+dfsg-1
ii  ruby-carrierwave  0.10.0+gh-4
ii  ruby-charlock-holmes  

Bug#895648: marked as done ([gitlab] Add keyword that allows the inclusion of external YAML files)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #895648,
regarding [gitlab] Add keyword that allows the inclusion of external YAML files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
895648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Severity: normal

Hi, this feature is not included in the CE version. Here
https://gitlab.com/help/ci/yaml/README#include it says the following

```
Introduced in [GitLab Edition Premium](https://about.gitlab.com/gitlab-ee/) 
10.5.
Available for Starter, Premium and Ultimate
[versions](https://about.gitlab.com/products/) since 10.6.
```

The MR that adds this feature is here
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4262 and the related
issue https://gitlab.com/gitlab-org/gitlab-ce/issues/20868#note_14082877. As
you can see it says

"Since this is targeting larger organizations, it will be `EE Premium`."

Debian is a large organization... Can we ask for this feature as Debian Project
to Gitlab? or we have to patch it and maintain a fork of gitlab forever? I
understand that the policy is not patching gitlab if possible. But I think in
this case, it would be really useful for us. Because we are going to have
really similar pipelines between projects and I am sure we can unify this and
maintain one generic pipeline for most of the packages or at least per
maintainer. I already have two projects with the same CI pipeline at this
moment. I'll be migrating the rest of my packages and they will share the same
pipeline so I have to keep a copy updated on every project...

PS: I've created an issue on salsa[0] for this. I think it applies as a feature
request. Please let me know if here is the correct place to discuss this and
I'll close the issue on salsa.

[0] https://salsa.debian.org/salsa/support/issues/64

-- 
TiN
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#893450: marked as done (gitlab: fresh install have no root account, default root password does not work)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #893450,
regarding gitlab: fresh install have no root account, default root password 
does not work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 9.5.4+dfsg-7
Severity: normal

It is impossible to log in to fresh install of Gitlab using default root
password as per "/usr/share/doc/gitlab/README.md.gz" line 63.

Could it be because root account does not exist?

Although eventually it would be nice to fix the problem in the meantime
this issue should be documented in README.Debian...

Thanks,
  Dmitry Smirnov.
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#865105: marked as done (gitlab: leaves stale systemd service symlinks after purge)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #865105,
regarding gitlab: leaves stale systemd service symlinks after purge
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
865105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.11+dfsg1-8
Severity: normal

Hi,

Purging gitlab seems to leave some stale files in /etc/systemd/system.
These are usually removed automatically when dh_systemd is in use by a
small snippet inserted into the postrm file. It looks like this is not
being executed.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#862159: marked as done (gitlab: config.yml.example is not there)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #862159,
regarding gitlab: config.yml.example is not there
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
862159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.11+dfsg1-3
Severity: normal

Dear Maintainer,

When installing gitlab and with apt, on configuration it will fil as
there is no config.yml.example file. Once created and running apt-get
install -f to finalize the istallation everything will work fine and the
system will be up and running.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.4.30-mod-std-ipv6-64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  adduser   3.115
ii  asciidoctor   1.5.4-2
ii  bc1.06.95-9+b3
ii  bundler   1.13.6-2
ii  dbconfig-pgsql2.0.8
ii  debconf [debconf-2.0] 1.5.60
ii  exim4-daemon-heavy [mail-transport-agent  4.89-2
ii  git   1:2.11.0-2
ii  gitlab-shell  3.6.6-4
ii  gitlab-workhorse  0.8.5+debian-3+b1
ii  init-system-helpers   1.47
ii  libjs-chartjs 1.0.2-1
ii  libjs-clipboard   1.4.2-1
ii  libjs-fuzzaldrin-plus 0.3.1+git.20161008.da2cb58+dfsg-4
ii  libjs-graphael0.5+dfsg-1
ii  libjs-jquery-cookie   11-3
ii  libjs-jquery-history  11-3
ii  libjs-jquery-nicescroll   3.6.6-1
ii  lsb-base  9.20161125
ii  nginx 1.10.3-1
ii  nginx-full [nginx]1.10.3-1
ii  nodejs6.10.3-1nodesource1~jessie1
ii  openssh-client1:7.4p1-10
ii  postgresql-client-9.6 [postgresql-client  9.6.2-2
ii  postgresql-contrib9.6+181
ii  rake  10.5.0-2
ii  redis-server  3:3.2.6-1
ii  ruby  1:2.3.3
ii  ruby-ace-rails-ap 4.1.1-1
ii  ruby-activerecord-session-store   1.0.0-2
ii  ruby-acts-as-taggable-on  4.0.0-2
ii  ruby-addressable  2.4.0-1
ii  ruby-after-commit-queue   1.3.0-1
ii  ruby-akismet  2.0.0-1
ii  ruby-allocations  1.0.3-1+b2
ii  ruby-asana0.4.0-1
ii  ruby-attr-encrypted   3.0.1-2
ii  ruby-babosa   1.0.2-2
ii  ruby-base32   0.3.2-3
ii  ruby-bootstrap-sass   3.3.5.1-5
ii  ruby-browser  2.2.0-2
ii  ruby-cal-heatmap-rails3.6.0+dfsg-1
ii  ruby-carrierwave  0.10.0+gh-4
ii  ruby-charlock-holmes  0.7.3+dfsg-2+b3
ii  ruby-chronic  0.10.2-3
ii  ruby-chronic-duration 0.10.6-1
ii  ruby-coffee-rails 4.1.0-2
ii  ruby-coffee-script-source 1.10.0-1
ii  ruby-connection-pool  2.2.0-1
ii  ruby-creole   0.5.0-2
ii  ruby-d3-rails 3.5.6+dfsg-1
ii  ruby-default-value-for3.0.1-1
ii  ruby-devise   4.2.0-1
ii  ruby-devise-two-factor3.0.0-2
ii  ruby-diffy3.0.6-1
ii  ruby-doorkeeper   4.2.0-3
ii  ruby-dropzonejs-rails 0.7.1-1
ii  ruby-email-reply-parser   0.5.8-1
ii  ruby-fog-aws  0.12.0-1
ii  ruby-fog-azure0.0.2-1
ii  ruby-fog-core 1.42.0-1
ii  ruby-fog-google   0.3.2-1
ii  ruby-fog-local   

Bug#852787: marked as done (gitlab: systemd configuration for sidekiq tears down gitlab service)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #852787,
regarding gitlab: systemd configuration for sidekiq tears down gitlab service
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
we have low mem instance of gitlab - it used to have 2GB of ram, now it has 3GB.
Sometimes, it runs out of memory. (usually at 22:xx )
OOM killer usually kills one of sidekiq children.
It triggers restart of sidekiq, but also of other gitlab services.
But gitlab-sidekiq is the only one, which is started, other are left dead.

Can this be somehow addressed in systemd service dependecies?


Libor

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAliLGIQVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOcGgP/3eJAMqQoBWxG48YXLnfx1D6YZ6h
K4CLe0fpz8rFG87v4qsfyszA5WF3qY3QTffYKXxDJq5Z9QAaV2V+k5Jn0j0Sqhes
IsZqN5g4XvOdyYB6UEy6IGdDhiogiqCeHTz/gRL83WYDb2c+aIykZVYUWSS2MELl
fIpDyIn5FvlRs42VQu0u6x/Wi6b1+j55Y7KWo3j/bET+8MQzg5fOEdIO3qXGTGrf
A5wM0QQtFsOmcvQNWz7hWn7Lm4Fd5Q5U48O0MRiaJNTOUA/OOfoHgRBwHcBAUtvR
2alVQwb9FlH90wdRhUHARJEX10m2+duTvRw4KrP2PHaFcy5l/GJiVp8RV5NrAkHF
Fo9xDrmNjDnCAhjT54gOaudAYW5P9MpqJDHOtcaenvsoK8OHaEFh85kBxYhDj4DA
T8f7qnoHzBsHXzDr3zLMas8TGVfWRc/H7HhhL19WTDwCyXJfm+NBcwYd5RUXysl/
TdZE9K09uhxKtMNbnhAqfPk08XTmTRLObRGx/2U8wWaU8f3X1aZOJLANOQUKuq2Q
57eEIQ3Ed8eY8AUN95jfxq5s9QbgLhwGf8hl6eyzXKrAtHxq/coeN2rNzdaEYIac
A7VRgk4id1qnwqdAFgy6DoNTzqK2vcAjy5Ix+DmoFPHmaxqIuXj6O9pNr5+/9lL4
/0DxTlrb5zieOvBi
=h2TC
-END PGP SIGNATURE-
Jan 26 22:15:18 gitlab kernel: kworker/0:0 invoked oom-killer: 
gfp_mask=0x24200c2(GFP_HIGHUSER), order=0, oom_score_adj=0
Jan 26 22:15:18 gitlab kernel: kworker/0:0 cpuset=/ mems_allowed=0
Jan 26 22:15:18 gitlab kernel: CPU: 0 PID: 9360 Comm: kworker/0:0 Not tainted 
4.8.0-2-amd64 #1 Debian 4.8.15-2
Jan 26 22:15:18 gitlab kernel: Hardware name: VMware, Inc. VMware Virtual 
Platform/440BX Desktop Reference Platform, BIOS 6.00 04/14/2014
Jan 26 22:15:18 gitlab kernel: Workqueue: events_freezable vmballoon_work 
[vmw_balloon]
Jan 26 22:15:18 gitlab kernel:  0286 1c838855 
8831f925 972ef1ab3d08
Jan 26 22:15:18 gitlab kernel:  972f38b02080 881f7491 
0206 8818f2e9
Jan 26 22:15:18 gitlab kernel:  972f3fffccc0 000c0246 
972f2d66c080 972f38b02080
Jan 26 22:15:18 gitlab kernel: Call Trace:
Jan 26 22:15:18 gitlab kernel:  [] ? dump_stack+0x5c/0x77
Jan 26 22:15:18 gitlab kernel:  [] ? dump_header+0x59/0x1dc
Jan 26 22:15:18 gitlab kernel:  [] ? 
do_try_to_free_pages+0x269/0x350
Jan 26 22:15:18 gitlab kernel:  [] ? 
oom_kill_process+0x222/0x3e0
Jan 26 22:15:18 gitlab kernel:  [] ? out_of_memory+0x35c/0x3f0
Jan 26 22:15:18 gitlab kernel:  [] ? 
__alloc_pages_nodemask+0xd67/0xda0
Jan 26 22:15:18 gitlab kernel:  [] ? update_curr+0xe1/0x160
Jan 26 22:15:18 gitlab kernel:  [] ? 
alloc_pages_current+0x91/0x140
Jan 26 22:15:18 gitlab kernel:  [] ? 
vmballoon_work+0x47f/0x704 [vmw_balloon]
Jan 26 22:15:18 gitlab kernel:  [] ? 
process_one_work+0x160/0x410
Jan 26 22:15:18 gitlab kernel:  [] ? worker_thread+0x4d/0x480
Jan 26 22:15:18 gitlab kernel:  [] ? 
process_one_work+0x410/0x410
Jan 26 22:15:18 gitlab kernel:  [] ? kthread+0xcd/0xf0
Jan 26 22:15:18 gitlab kernel:  [] ? ret_from_fork+0x1f/0x40
Jan 26 22:15:18 gitlab kernel:  [] ? 
kthread_create_on_node+0x190/0x190
Jan 26 22:15:18 gitlab kernel: Mem-Info:
Jan 26 22:15:18 gitlab kernel: active_anon:98986 inactive_anon:102318 
isolated_anon:0
   active_file:23 inactive_file:47 
isolated_file:0
   unevictable:0 dirty:0 writeback:0 unstable:0
   slab_reclaimable:3358 slab_unreclaimable:9520
   mapped:1580 shmem:1984 pagetables:3919 
bounce:0
   free:14226 free_pcp:30 free_cma:0
Jan 26 22:15:18 gitlab kernel: Node 0 active_anon:395944kB 
inactive_anon:409272kB active_file:92kB inactive_file:188kB unevictable:0kB 
isolated(anon):0kB isolated(file):0kB mapped:6320kB dirty:0kB writeback:0kB 
shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 7936kB 
writeback_tmp:0kB unstable:0kB pages_scanned:0 all_unreclaimable? no
Jan 26 22:15:18 gitlab kernel: Node 0 DMA free:12136kB min:232kB 

Bug#851648: marked as done (gitlab-workhorse not logging to file on systemd)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #851648,
regarding gitlab-workhorse not logging to file on systemd
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,
just a little patch to enable logging of gitlab-workhorse on systemd.

Don't know, if it's useful, use it if you like it, drop if not.
Personaly i don't like the /bin/sh "hack"

Libor

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlh94pwVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOD4wP/0NTNHL79ykF6zgtQ7Iw9YQJqC9/
8FjaKM9Vr8l/9sfniBo9WLKFdTwMFy74YlFhcX1501qj0Vr+5k487PcYg3hzWKdt
Phgi+WOs1Ca88vew6eVhLTfJrkVU4AJkweobLpccOVIvLDkk7+Qqaoq7myGIeYVy
UKoPDqq41bBbwDWZVQ6t6C6fqFY5+bL4ZG221xFlpktE6xWKQhoSOI4z/g1Gq0Wn
lUEdibrhWll8dg9BSwi3zdXAbsGe1dtWBuTenqaNMk9ey/GI4TaqY1T4w619a9L/
XAwivqPClEjkHl3/2qm1vWpEQmrR98WAA+FxAc0CjoQVyhuWwId8RJJsfXGzjXCj
GTp6HsnLsAiSHsNV2lWnrN677wd0tRH9SCl836mpxZYkgJPTq8wPF8ovgZfzizsm
OX5Y0/NQymNJT+fcESXcvny033sVMrEeTi1NOrw1d4bLKGvmIyJ5OKj3u/JaGLm9
6MfiCbnYLbB1DlJqm/b+HCS6fygcigWHi4xYA03IrXglc1il05h7AO52XVDhTKjZ
bVrXFy4lATxXXeSRqzDy/pWHZ0ZykeREdYwcl+Rp01YvzQgfmajzgwDQkuzfHuu3
Q/IMjVnmDbbJX7LgaYECtmPRAvejHvMOj6ndvdCBHtjc1EZZ+ezwt7NKpLwbdSpj
ckaM8ios8+p9u+QB
=h3uq
-END PGP SIGNATURE-
diff -ur a/debian/gitlab.gitlab-workhorse.service 
b/debian/gitlab.gitlab-workhorse.service
--- a/debian/gitlab.gitlab-workhorse.service2016-07-19 11:11:39.0 
+0200
+++ b/debian/gitlab.gitlab-workhorse.service2017-01-17 10:18:52.816505949 
+0100
@@ -13,14 +13,16 @@
 WorkingDirectory=/usr/share/gitlab
 EnvironmentFile=/etc/gitlab/gitlab-debian.conf
 SyslogIdentifier=gitlab-workhorse
-ExecStart=/usr/bin/gitlab-workhorse \
+ExecStart=/bin/sh -c '/usr/bin/gitlab-workhorse \
 -listenUmask 0 \
 -listenNetwork unix \
 -listenAddr ${gitlab_pid_path}/gitlab-workhorse.socket \
 -authBackend http://127.0.0.1:8080 \
 -authSocket ${gitlab_pid_path}/gitlab.socket \
--documentRoot ${gitlab_app_root}/public
+-documentRoot ${gitlab_app_root}/public \
+>> ${gitlab_log_dir}/gitlab-workhorse.log 2>&1'
 Restart=on-abnormal
+KillMode=control-group
 
 [Install]
 WantedBy=gitlab.target
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#848872: marked as done (gitlab: please document how to operate Debian gitlab behind an ssl terminating reverse proxy)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #848872,
regarding gitlab: please document how to operate Debian gitlab behind an ssl 
terminating reverse proxy
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
848872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Severity: wishlist

Hi,

supposedly, gitlab can be operated behind an SSL terminating reverse
proxy (I'm using pound) by adding the headers:

X-Forwarded-Proto: https
X-Forwarded-Ssl: on

This also works for the most part but there is still one remaining bug.
The clone URL starts with http:// even though it should be https://.
Thus, whenever I share the clone url, I now must manually replace the
http:// with a https:// which is inconvenient.

Online instructions of how to fix this problem do not seem to apply to
the Debian package as I am unable to find the referenced configuration
values. The instructions seem to be very specific to the omnibus
package.

It would be greatly appreciated if the Debian gitlab package could be
operated behind an SSL terminating reverse proxy just as easily and
without the clone-url bug.

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#846180: marked as done (gitlab not restarted after redis-server upgrade)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #846180,
regarding gitlab not restarted after redis-server upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
846180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gitlab
Version: 8.13.6+dfsg1-2
Severity: normal

Dear Maintainer,

I just installed an upgraded version of redis-server (but not of gitlab 
itself), and after the upgrade gitlab was no longer running.  The 
following reproduces this easily for me:



$ for i in "" -mailroom -sidekiq -unicorn -workhorse; do
  s=gitlab$i; echo $s; sudo service $s status | grep Active; done

gitlab
   Active: active (exited) since Mon 2016-11-28 21:06:38 EST; 3s ago
gitlab-mailroom
   Active: active (running) since Mon 2016-11-28 21:06:26 EST; 15s ago
gitlab-sidekiq
   Active: active (running) since Mon 2016-11-28 21:06:38 EST; 3s ago
gitlab-unicorn
   Active: active (running) since Mon 2016-11-28 21:06:26 EST; 15s ago
gitlab-workhorse
   Active: active (running) since Mon 2016-11-28 21:06:26 EST; 15s ago



$ sudo apt-get install redis-server --reinstall

Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not 
upgraded.

Need to get 0 B/407 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 253802 files and directories currently installed.)
Preparing to unpack .../redis-server_3%3a3.2.5-2_amd64.deb ...
Unpacking redis-server (3:3.2.5-2) over (3:3.2.5-2) ...
Processing triggers for systemd (232-6) ...
Processing triggers for man-db (2.7.5-2) ...
Setting up redis-server (3:3.2.5-2) ...



$ for i in "" -mailroom -sidekiq -unicorn -workhorse; do
  s=gitlab$i; echo $s; sudo service $s status | grep Active; done

gitlab
   Active: inactive (dead) since Mon 2016-11-28 21:06:49 EST; 13s ago
gitlab-mailroom
   Active: inactive (dead) since Mon 2016-11-28 21:06:50 EST; 13s ago
gitlab-sidekiq
   Active: inactive (dead) since Mon 2016-11-28 21:06:52 EST; 10s ago
gitlab-unicorn
   Active: inactive (dead) since Mon 2016-11-28 21:06:50 EST; 12s ago
gitlab-workhorse
   Active: inactive (dead) since Mon 2016-11-28 21:06:49 EST; 13s ago



I have no idea whether this is something wrong in the gitlab service 
files, something wrong in redis-server, or something elsewhere (e.g. in 
debhelper's scripts for restarting on upgrade).



Jason Rhinelander
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#847421: marked as done (gitlab should precompile assets itself if relevant dependencies change)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #847421,
regarding gitlab should precompile assets itself if relevant dependencies change
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.3+dfsg1-2
Severity: important

Hi,

in #846916 you advised me to run "rake assets:precompile" after I
upgraded my version of ruby-jquery-rails. This really should not be
necessary and the gitlab package should do this itself if any relevant
package versions get upgraded/changed. I could for example imagine that
you could use dpkg triggers to run the required gitlab tasks.

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#839702: marked as done (gitlab: logrotate not working?)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #839702,
regarding gitlab: logrotate not working?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
839702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.12.3+dfsg1-1
Severity: minor

Ever since I've installed GitLab "/var/log/gitlab/production.log" keep 
growing (it is already over 700 MiB) despite the following in the
"/etc/gitlab/gitlab.rb":


logging['logrotate_frequency'] = "daily"
logging['logrotate_size'] = 200 * 1024 * 1024
logging['logrotate_rotate'] = 30
logging['logrotate_compress'] = "compress"
logging['logrotate_method'] = "copytruncate"
logging['logrotate_postrotate'] = nil
logging['logrotate_dateformat'] = nil


Package "logrotate" is installed...

-- 
Best wishes,
 Dmitry Smirnov.

---

The great enemy of the truth is very often not the lie -- deliberate,
contrived and dishonest, but the myth, persistent, persuasive, and
unrealistic. Belief in myths allows the comfort of opinion without the
discomfort of thought.
-- John F Kennedy


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#846179: marked as done (gitlab: Use notify on ready under systemd instead of hack with sleep + check commandline)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #846179,
regarding gitlab: Use notify on ready under systemd instead of hack with sleep 
+ check commandline
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
846179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gitlab
Version: 8.13.6+dfsg1-2
Severity: normal

Dear Maintainer,

The current systemd service file for gitlab-sidekiq contains a hack to 
delay the systemd service startup until sidekiq is actually ready by 
sleeping for up to 32 seconds (in increments of 4 seconds) until 
sidekiq's cmdline changes.


Besides being an unpleasant hack, and potentially ending too early (e.g. 
if sidekiq takes more than 32 seconds to start up on a slow/loaded 
machine), this also has the unfortunate consequence of showing this 
command forever in the service status output, and of making the service 
take up to 4 seconds longer than necessary to actually be registered as 
started.


We can do much better by performing a proper systemd notify, as follows 
(I've tested this locally, and it works properly):



1. Patch the installed /etc/gitlab/initializers/sidekiq.rb to add, near 
the top of the configure_server function:



  if ((socket_path = ENV["NOTIFY_SOCKET"]))
config.on(:startup) do
  notify_socket = Socket.new(Socket::AF_UNIX, Socket::SOCK_DGRAM, 0)
  notify_socket.connect(Socket.sockaddr_un(socket_path))
  notify_socket.sendmsg "READY=1", Socket::MSG_NOSIGNAL
end
  end


2. change the gitlab-sidekiq.service file to contain:

Type=notify

and delete the ExecStartPost= line.



Then we get proper notification support: notification happens 
immediately upon sidekiq being ready, the hack is gone, and the job 
starts faster.



Jason Rhinelander



smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#820065: marked as done (gitlab: please adapt the postinst output for Debian)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #820065,
regarding gitlab: please adapt the postinst output for Debian
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
820065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.5.8+dfsg-3
Severity: wishlist

Hi,

when upgrading gitlab, the user might be presented with stanzas like
this:


 [...]
 Check GitLab API access: FAILED. code: 502
 gitlab-shell self-check failed
   Try fixing it:
   Make sure GitLab is running;
   Check the gitlab-shell configuration file:
   sudo -u gitlab -H editor /usr/share/gitlab-shell/config.yml
   Please fix the error above and rerun the checks.
 [...]
 Checking Sidekiq ...
 
 Running? ... no
   Try fixing it:
   sudo -u gitlab -H RAILS_ENV=production bin/background_jobs start
   For more information see:
   doc/install/installation.md in section "Install Init Script"
   see log/sidekiq.log for possible errors
   Please fix the error above and rerun the checks.
 [...]
 All migrations up? ... no
   Try fixing it:
   sudo -u gitlab -H bundle exec rake db:migrate RAILS_ENV=production
   Please fix the error above and rerun the checks.
 [...]


As a user, I'd expect that after installing the "gitlab" package, I can
follow the above instructions without problems. Unfortunately, this is
not the case, because:

 - the gitlab package does not Depends, Recommends or Suggests sudo or
   an editor
 - executing bin/background_jobs does not seem to work on a Debian
   system
 - as described in README.Debian, the "sudo -u gitlab -H bundle exec
   rake" line will not work on Debian gitlab

I see the following ways to fix this:

 - suggest sudo and editor
 - adapt the messages such that they give advice which can be executed
   on a Debian gitlab installation
 - add more sections to README.Debian like "if gitlab tells you to run
   A, run B instead"

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#836551: marked as done (gitlab: short gpg key used in script)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #836551,
regarding gitlab: short gpg key used in script
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
836551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.10.5+dfsg-2
Severity: important

Dear Maintainer,

Your package appears to contain commands which use a short gpg-key
ID. These have recently been identified as potential security concerns,
due to a chance that the wrong key can be imported in the case of a
forced key-ID collision [1].

The affected file is:
 Scala.gitlab-ci.yml [2]


Please consider upgrading to a full key ID, for example, replace the command:

 gpg --keyserver  --recv-keys  

with

 gpg --keyserver   --recv-keys 

eg (not specific to your package):

 gpg --keyserver keyring.debian.org --recv-keys 05C3E651

becomes:

 gpg --keyserver keyring.debian.org --recv-keys 
0x0D59D2B15144766A14D241C66BAF400B05C3E651


(Note the tail bytes are the same)

This has previously been forwarded to the security team, who advised to
report individual public bugs against each package - hence this bug.

[1] http://lwn.net/Articles/697417
[2] 
https://anonscm.debian.org/cgit/pkg-ruby-extras/gitlab.git/tree/vendor/gitlab-ci-yml/Scala.gitlab-ci.yml
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#831448: marked as done (gitlab: fails to install database)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #831448,
regarding gitlab: fails to install database
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
831448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.9.0+dfsg-4
Severity: grave
Justification: renders package unusable

installing gitlab via apt with LANG=en_US.UTF-8 results in this:

Create database if not present
psql: FATAL:  database "gitlab_production" does not exist
createdb: database creation failed: ERROR:  encoding "UTF8" does not match 
locale "en_US"
DETAIL:  The chosen LC_CTYPE setting requires encoding "LATIN1".
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)
  

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#820564: marked as done (gitlab: CI tests broken)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #820564,
regarding gitlab: CI tests broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
820564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.5.8+dfsg-5
Severity: normal
User: autopkgtest-de...@lists.alioth.debian.org
Usertags: autopkgtest

https://ci.debian.net/packages/g/gitlab/

Fixing the CI tests will also help everyone to test reverse dependencies
against gitlab. For example I am now preparing a new upstream release of
rails, and I can test the new binaries against redmine, but not against
gitlab.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Antonio Terceiro 


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1031573: marked as done (RM: jthread -- ROM; abandoned upstream, unmaintained)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:04:42 +
with message-id 
and subject line Bug#1031573: Removed package(s) from unstable
has caused the Debian Bug report #1031573,
regarding RM: jthread -- ROM; abandoned upstream, unmaintained
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: ftp.debian.org
severity: normal
user: ftp.debian@packages.debian.org
usertags: remove

Please remove src:jthread from bookworm and sid.  It no longer has
reverse dependencies and is abandoned upstream.

It has release critical bug #1031253 that I plan to not fix.

Best wishes,
Mike
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   jthread |  1.3.1-3.1 | source
libjthread-dbg |  1.3.1-3.1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
libjthread-dev |  1.3.1-3.1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
libjthread-doc |  1.3.1-3.1 | all
libjthread1.3.1 |  1.3.1-3.1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
ROM; abandoned upstream, unmaintained
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1031573

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1031551: marked as done (RM: cawbird -- ROM; unusable due to changes in Twitter policies and abandoned by the upstream developer)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:04:10 +
with message-id 
and subject line Bug#1031551: Removed package(s) from unstable
has caused the Debian Bug report #1031551,
regarding RM: cawbird -- ROM; unusable due to changes in Twitter policies and 
abandoned by the upstream developer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: cawb...@packages.debian.org
Control: affects -1 + src:cawbird

Twitter changed the Developer Agreement to prohibit "creating a substitute for 
Twitter Applications" and revoked the primary API keys around 20th January.
The development of Cawbird ceased.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   cawbird |  1.5-1 | source, amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
ROM; unusable due to changes in Twitter and abandoned by the upstream developer
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1031551

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1031253: marked as done (jthread: FTBFS (dh_install: error: missing files, aborting))

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:04:45 +
with message-id 
and subject line Bug#1031573: Removed package(s) from unstable
has caused the Debian Bug report #1031253,
regarding jthread: FTBFS (dh_install: error: missing files, aborting)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:jthread
Version: 1.3.1-3.1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules build-arch
dh build-arch
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config -a
   dh_auto_configure -a
dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
(level 9 in use)
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON "-GUnix 
Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument  value or use a ... suffix to tell
  CMake that the project does not need compatibility with older versions.


-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
CMake Warning (dev) at src/CMakeLists.txt:48 (get_target_property):
  Policy CMP0026 is not set: Disallow use of the LOCATION target property.
  Run "cmake --help-policy CMP0026" for policy details.  Use the cmake_policy
  command to set the policy and suppress this warning.

  The LOCATION property should not be read from target "jthread-shared".  Use
  the target name directly with add_custom_command, or use the generator
  expression $, as appropriate.

This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_SYSCONFDIR
FETCHCONTENT_FULLY_DISCONNECTED


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
   dh_auto_build -a
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
cd obj-x86_64-linux-gnu && make -j1 VERBOSE=1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f src/CMakeFiles/jthread-static.dir/build.make 
src/CMakeFiles/jthread-static.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/src /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src 
/<>/obj-x86_64-linux-gnu/src/CMakeFiles/jthread-static.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f src/CMakeFiles/jthread-static.dir/build.make 
src/CMakeFiles/jthread-static.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 16%] Building CXX object 
src/CMakeFiles/jthread-static.dir/pthread/jmutex.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DJTHREAD_COMPILING -I/<>/src 
-I/<>/obj-x86_64-linux-gnu/src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 

Bug#1031519: marked as done (RM: gitlab -- ROM; Remove gitlab from unstable (keep the version in experimental))

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:02:30 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1031519,
regarding RM: gitlab -- ROM; Remove gitlab from unstable (keep the version in 
experimental)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal
X-DebBugs-CC: t...@security.debian.org

Since protobuf was updated in unstable only recently, reuploading all 
(build)dependencies to unstable could not be completed in time for 
freeze and security team requested it to be kept only in experimental 
to avoid confusion for users (many open security issues and a very old 
version in unstable, whereas experimental has all the latest security 
updates).


We will try to reupload to unstable after freeze is lifted.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

gitlab |   13.4.7-2 | source, all

--- Reason ---
ROM; Remove gitlab from unstable (keep the version in experimental)
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1031519

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1025001: marked as done (gitlab: Some UI elements, including buttons, are replaced with "undefined")

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1025001,
regarding gitlab: Some UI elements, including buttons, are replaced with 
"undefined"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1025001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
Severity: important
X-Debbugs-Cc: f+deb...@chezlefab.net

Dear Maintainer,

   * What led up to the situation?

I upgraded gitlab from 15.3.4+ds1-1~fto11+1 to 15.4.2+ds1-1~fto11+3

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Dancing around a bit with a large troot. Ineffective.

   * What was the outcome of this action?

Some actions requires a carefully crafted API request to be performed
since UI is not useable.

   * What outcome did you expect instead?

Useable UI, that is clickable buttons.


-- System Information:
Debian Release: 11.5
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable'), (100, 
'bullseye-fasttrack'), (100, 'bullseye-backports-staging')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.utf8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  asciidoctor 2.0.17-1~fto11+1
ii  bc  1.07.1-2+b2
ii  bundler 2.2.5-2
ii  bzip2   1.0.8-4
ii  dbconfig-pgsql  2.0.19
ii  debconf [debconf-2.0]   1.5.77
ii  exim4-daemon-light [mail-trans  4.94.2-7
ii  fonts-font-awesome [node-font-  5.0.10+really4.7.0~dfsg-4.1
ii  gitlab-common   15.4.2+dfsg-1~fto11+1
ii  gitlab-workhorse15.4.2+ds1-1~fto11+3
ii  katex [node-katex]  0.13.11+~cs6.0.0-2~bpo11+1
ii  libjs-bootstrap4 [node-bootstr  4.5.2+dfsg1-8~deb11u1
ii  libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3
ii  libjs-popper.js [node-popper.j  1.16.1+ds-3
ii  libruby2.7 [ruby-webrick]   2.7.4-1+deb11u1
ii  lsb-base11.1.0
ii  nginx   1.18.0-6.1+deb11u3
ii  nginx-core [nginx]  1.18.0-6.1+deb11u3
ii  node-autosize   4.0.2~dfsg1-7
ii  node-axios  0.21.1+dfsg-1+deb11u1
ii  node-babel-loader   8.2.2-5
ii  node-babel-plugin-lodash3.3.4+~cs2.0.1-3
ii  node-babel7 7.12.12+~cs150.141.84-6
ii  node-brace-expansion2.0.0-1
ii  node-cache-loader   4.1.0+~cs2.0.0-1
ii  node-clipboard  2.0.8+ds+~cs9.6.11-1~bpo11+1
ii  node-compression-webpack-plugi  6.1.1-1
ii  node-copy-webpack-plugin5.1.2+~cs9.0.2-4
ii  node-core-js3.8.2-2
ii  node-cron-validator 1.3.1-1~bpo11+1
ii  node-css-loader 5.0.1+~cs14.0.5-1
ii  node-d3 5.16.0-4
ii  node-d3-selection   1.4.0-6
ii  node-dateformat 5.0.3-2~bpo11+1
ii  node-dompurify  2.3.7+dfsg-1~bpo11+1
ii  node-exports-loader 1.1.1-2
ii  node-file-loader6.2.0-2
ii  node-fuzzaldrin-plus0.5.0+dfsg-3
ii  node-glob   7.1.6+~7.1.3-1
ii  node-imports-loader 0.8.0-2
ii  node-jed1.1.1-2
ii  node-jquery 3.5.1+dfsg+~3.5.5-7
ii  node-jquery-ujs 1.2.2-2
ii  node-js-cookie  3.0.1+~3.0.0-2~bpo11+1
ii  node-js-yaml3.14.1+dfsg+~3.12.6-2
ii  node-jszip  3.5.0+dfsg-2
ii  node-jszip-utils0.0.2+dfsg-2
ii  node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9~bpo11+2
ii  node-marked 0.8.0+ds+repack-2
ii  node-mermaid8.14.0+~cs11.4.14-1~bpo11+1
ii  node-minimatch  3.0.4+~3.0.3-1
ii  node-miragejs   0.1.41+~cs5.6.6-4
ii  node-mousetrap  1.6.5~ds-1
ii  node-postcss8.4.8+~cs7.3.21-2~bpo11+2
ii  node-prismjs1.23.0+dfsg-1+deb11u2
ii  node-prosemirror-markdown   1.6.0-1~bpo11+2
ii  node-prosemirror-model  1.16.1+~cs1.1.5-1~bpo11+2
ii  node-prosemirror-state  1.3.4-1~bpo11+2
ii  

Bug#1029623: marked as done (gitlab: Services are not restarted in case of a missing database server during startup)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1029623,
regarding gitlab: Services are not restarted in case of a missing database 
server during startup
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1029623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 15.2.3+ds1-2~fto11+1
Severity: normal

Dear Maintainer,

recently I noticed, that the following gitlab-related services remained
in the "failed" state after booting the VM:
* gitlab-puma
* gitlab-sidekiq
* gitlab-workhorse

The problem was caused by the absence of the database server (it was
just booting up in a separate VM).

The same applies probably to `gitlab-mailroom`, but that service was
probably just lucky or arrived late.

Currently the `Restart` directive in the service files of the above
services is set to `Restart=on-abnormal`.
Thus, non-zero exit codes do not trigger a restart.

But the missing database connection caused exactly such a non-zero
exitcode.

Thus I would suggest to use `Restart=on-failure` for these (all?)
services, instead.

Thank you for maintaining the gitlab package!

Cheers,
Lars
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1024631: marked as done (gitlab: preinst: invalid number 9.1)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1024631,
regarding gitlab: preinst: invalid number 9.1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1024631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3

On install I get:
/var/lib/dpkg/tmp.ci/preinst: 7 [: Illagal number: 9.1

I have several postgresql clusters, 9.1, 9.6, 12, 14. Not all of them
are used. 9.1 is using port 5432.


Kurt
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1024627: marked as done (gitlab: Fails to install)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1024627,
regarding gitlab: Fails to install
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1024627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
Severity: serious

Setting up gitlab (15.4.2+ds1-1~fto11+3) ...
Bundler could not find compatible versions for gem "omniauth-oauth2":
  In Gemfile:
omniauth-auth0 (~> 2.0) was resolved to 2.0.0, which depends on
  omniauth-oauth2 (~> 1.4) x86_64-linux

omniauth-authentiq (~> 0.3.3) was resolved to 0.3.3, which depends on
  omniauth-oauth2 (>= 1.5) x86_64-linux

omniauth-azure-activedirectory-v2 (~> 1.0) was resolved to 1.0.0, which 
depends on
  omniauth-oauth2 (~> 1.7) x86_64-linux

omniauth-dingtalk-oauth2 (~> 1.0) was resolved to 1.0.0, which depends on
  omniauth-oauth2 (~> 1.7.1) x86_64-linux

omniauth-facebook (~> 4.0) was resolved to 4.0.0, which depends on
  omniauth-oauth2 (~> 1.2) x86_64-linux

omniauth-oauth2-generic (~> 0.2.2) was resolved to 0.2.2, which depends on
  omniauth-oauth2 (~> 1.0) x86_64-linux

Could not find gem 'omniauth-oauth2 (~> 1.7.1)', which is required by gem 
'omniauth-auth0 (~> 2.0)', in any of the sources.


Kurt
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1024143: marked as done (gitlab: postinst fails silently within rake-tasks, if /var/lib/gitlab/.cache/yarn/v6 does not exist)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1024143,
regarding gitlab: postinst fails silently within rake-tasks, if 
/var/lib/gitlab/.cache/yarn/v6 does not exist
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1024143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 15.2.3+ds1-2~fto11+1
Severity: normal
Tags: patch

Dear Maintainer,

during gitlab's package installation, the following line in
`rake-tasks.sh` causes a failure of the postinst processing:

> -runuser -u ${gitlab_user} -- sh -c 'test -d "/var/lib/gitlab/.cache/yarn/v6" 
> && find /var/lib/gitlab/.cache/yarn/v6/ -name .yarn-metadata.json -perm -a=w 
> -exec chmod 644 {} \;'

The above fails, if the directory does not exists.
Due to the shell's exit-on-error (`set -e`), this failure is fatal.

Attached you find a patch, which ensures the proper exitcode for the
line above.

Cheers,
Lars
--- /usr/lib/gitlab/scripts/rake-tasks.sh.orig  2022-11-15 05:16:06.185030967 
+0100
+++ /usr/lib/gitlab/scripts/rake-tasks.sh   2022-11-15 05:16:32.504552974 
+0100
@@ -45,7 +45,7 @@
 runuser -u ${gitlab_user} -- sh -c 'if ! grep nodeLinker .yarnrc.yml 
>/dev/null; then echo "nodeLinker: \"node-modules\"" >>.yarnrc.yml; fi'
 runuser -u ${gitlab_user} -- sh -c 'yarnpkg install'
 # Remove write permissions of .yarn-metadata.json files
-runuser -u ${gitlab_user} -- sh -c 'test -d "/var/lib/gitlab/.cache/yarn/v6" 
&& find /var/lib/gitlab/.cache/yarn/v6/ -name .yarn-metadata.json -perm -a=w 
-exec chmod 644 {} \;'
+runuser -u ${gitlab_user} -- sh -c 'if test -d 
"/var/lib/gitlab/.cache/yarn/v6"; then find /var/lib/gitlab/.cache/yarn/v6/ 
-name .yarn-metadata.json -perm -a=w -exec chmod 644 {} \;; fi'
 
 cd /usr/share/gitlab
 
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1023291: marked as done (gitlab-sidekiq spamming logs after upgrade to gitlab 15.4.2)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1023291,
regarding gitlab-sidekiq spamming logs after upgrade to gitlab 15.4.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1023291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
Severity: normal
X-Debbugs-Cc: z...@gsystem.sk

Dear Maintainer,
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]:   
redis.brpop("resque:gitlab:queue:adjourned_project_deletion", "resque:git
lab:queue:object_pool:object_pool_create", 
"resque:gitlab:queue:integrations_execute", "resque:gitlab:queue:gcp_cluster:clu
sters_cleanup_service_account", 
"resque:gitlab:queue:pipeline_default:ci_drop_pipeline", 
"resque:gitlab:queue:status_page_p
ublish", 
"resque:gitlab:queue:github_importer:github_import_stage_import_pull_requests", 
"resque:gitlab:queue:package_clean
up:packages_mark_package_files_for_destruction", ..
 blah maybe 100 more lines

/var/log/syslog is 10GB in just 3 days. I had to delete two other 20GB logs 
because the disk was full.


-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'oldstable-updates'), (500, 'oldoldstable'), (500, 'stable'), (500, 
'oldstable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-19-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gitlab depends on:
ii  apache2 [httpd] 2.4.54-1~deb11u1
ii  asciidoctor 2.0.17-1~fto11+1
ii  bc  1.07.1-2+b2
ii  bundler 2.2.5-2
ii  bzip2   1.0.8-4
ii  dbconfig-pgsql  2.0.19
ii  debconf [debconf-2.0]   1.5.77
ii  fonts-font-awesome [node-font-  5.0.10+really4.7.0~dfsg-4.1
ii  gitlab-common   15.4.2+dfsg-1~fto11+1
ii  gitlab-workhorse15.4.2+ds1-1~fto11+3
ii  katex [node-katex]  0.13.11+~cs6.0.0-2~bpo11+1
ii  libjs-bootstrap4 [node-bootstr  4.5.2+dfsg1-8~deb11u1
ii  libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3
ii  libjs-popper.js [node-popper.j  1.16.1+ds-3
ii  libruby2.7 [ruby-webrick]   2.7.4-1+deb11u1
ii  lsb-base11.1.0
ii  node-autosize   4.0.2~dfsg1-7
ii  node-axios  0.21.1+dfsg-1+deb11u1
ii  node-babel-loader   8.2.2-5
ii  node-babel-plugin-lodash3.3.4+~cs2.0.1-3
ii  node-babel7 7.12.12+~cs150.141.84-6
ii  node-brace-expansion2.0.0-1
ii  node-cache-loader   4.1.0+~cs2.0.0-1
ii  node-clipboard  2.0.8+ds+~cs9.6.11-1~bpo11+1
ii  node-compression-webpack-plugi  6.1.1-1
ii  node-copy-webpack-plugin5.1.2+~cs9.0.2-4
ii  node-core-js3.8.2-2
ii  node-cron-validator 1.3.1-1~bpo11+1
ii  node-css-loader 5.0.1+~cs14.0.5-1
ii  node-d3 5.16.0-4
ii  node-d3-selection   1.4.0-6
ii  node-dateformat 5.0.3-2~bpo11+1
ii  node-dompurify  2.3.7+dfsg-1~bpo11+1
ii  node-exports-loader 1.1.1-2
ii  node-file-loader6.2.0-2
ii  node-fuzzaldrin-plus0.5.0+dfsg-3
ii  node-glob   7.1.6+~7.1.3-1
ii  node-imports-loader 0.8.0-2
ii  node-jed1.1.1-2
ii  node-jquery 3.5.1+dfsg+~3.5.5-7
ii  node-jquery-ujs 1.2.2-2
ii  node-js-cookie  3.0.1+~3.0.0-2~bpo11+1
ii  node-js-yaml3.14.1+dfsg+~3.12.6-2
ii  node-jszip  3.5.0+dfsg-2
ii  node-jszip-utils0.0.2+dfsg-2
ii  node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9~bpo11+2
ii  node-marked 0.8.0+ds+repack-2
ii  node-mermaid8.14.0+~cs11.4.14-1~bpo11+1
ii  node-minimatch  3.0.4+~3.0.3-1
ii  node-miragejs   

Bug#1022875: marked as done (gitlab: JavaScript not working: Uncaught TypeError renders UI mostly unusable)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1022875,
regarding gitlab: JavaScript not working: Uncaught TypeError renders UI mostly 
unusable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1022875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 15.3.4+ds1-1~fto11+1
Severity: normal


Dear maintainer,

after upgrading our gitlab instance from 14 to 15 (thorugh fasttrack) most of 
the UI has been left in a unusable state due to the following JS error:

Uncaught TypeError: n(...) is not a function
jA48 es.object.has-own.js:6
Webpack 32
es.object.has-own.js:6:2

Is there a way to verify the integrity of the JS assets?

Regards,
Michael




-- System Information:
Debian Release: 11.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'stable-security'), (100, 'bullseye-fasttrack'), (100, 
'bullseye-backports-staging')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-0.deb11.2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gitlab depends on:
ii  apache2 [httpd] 2.4.54-1~deb11u1
ii  asciidoctor 2.0.17-1~fto11+1
ii  bc  1.07.1-3+b1
ii  bundler 2.3.5-2
ii  bzip2   1.0.8-4
ii  dbconfig-pgsql  2.0.22~bpo11+1
ii  debconf [debconf-2.0]   1.5.77
ii  fonts-font-awesome [node-font-  5.0.10+really4.7.0~dfsg-4.1
ii  gitlab-common   15.3.1+dfsg-1~fto11+1
ii  gitlab-workhorse15.3.4+ds1-1~fto11+1
ii  katex [node-katex]  0.13.11+~cs6.0.0-3
ii  libjs-bootstrap4 [node-bootstr  4.5.2+dfsg1-8~deb11u1
ii  libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3
ii  libjs-popper.js [node-popper.j  1.16.1+ds-3
ii  libruby2.7 [ruby-webrick]   2.7.4-1+deb11u1
ii  libruby3.0 [ruby-rexml] 3.0.4-7
ii  lsb-base11.1.0
ii  node-autosize   4.0.4~dfsg1+~4.0.0-1
ii  node-axios  0.26.1+dfsg-1
ii  node-babel-loader   8.2.5-1
ii  node-babel-plugin-lodash3.3.4+~cs2.0.1-3
ii  node-babel7 7.17.11+~cs214.263.190-1
ii  node-brace-expansion2.0.0-1
ii  node-cache-loader   4.1.0+~cs2.0.0-3
ii  node-clipboard  2.0.8+ds+~cs9.6.11-1
ii  node-compression-webpack-plugi  6.1.1-1
ii  node-copy-webpack-plugin5.1.2+~cs9.0.2-4
ii  node-core-js3.22.3-1
ii  node-cron-validator 1.3.1-1~bpo11+1
ii  node-css-loader 5.0.1+~cs14.0.5-1
ii  node-d3 5.16.0-5
ii  node-d3-selection   1.4.0-7
ii  node-dateformat 5.0.3-2~bpo11+1
ii  node-dompurify  2.3.7+dfsg-1~bpo11+1
ii  node-exports-loader 1.1.1-3
ii  node-file-loader6.2.0-3
ii  node-fuzzaldrin-plus0.6.0+dfsg+~0.6.2-1
ii  node-glob   7.1.6+~7.1.3-1
ii  node-imports-loader 0.8.0-5
ii  node-jed1.1.1-3
ii  node-jquery 3.5.1+dfsg+~3.5.5-7
ii  node-jquery-ujs 1.2.3-1
ii  node-js-cookie  3.0.1+~3.0.0-2
ii  node-js-yaml3.14.1+dfsg+~3.12.6-2
ii  node-jszip  3.7.1+dfsg-1
ii  node-jszip-utils0.1.0+dfsg-1
ii  node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9~bpo11+1
ii  node-marked 4.0.12+ds+~4.0.1-2
ii  node-mermaid8.14.0+~cs11.4.14-1
ii  node-minimatch  3.0.4+~3.0.3-1
ii  node-miragejs   0.1.41+~cs5.6.6-4
ii  node-mousetrap  1.6.5~ds+~1.6.8-1
ii  node-postcss8.4.8+~cs7.3.21-2~bpo11+2
ii  node-prismjs1.27.0+dfsg+~1.26.0-1
ii  node-prosemirror-markdown   1.6.0-1
ii  node-prosemirror-model  1.16.1+~cs1.1.5-1
ii  node-prosemirror-state  1.3.4-1~bpo11+2
ii  node-prosemirror-view   1.23.13-1~bpo11+1
ii  node-raven-js   3.22.1+dfsg-6
ii  node-raw-loader 4.0.2-2
ii  node-style-loader   2.0.0-3
ii  node-three-orbit-controls   82.1.0-3

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

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1019731,
regarding gitlab: failed to fetch comments in merge requests (500 Internal 
Server Error)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1019731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 request with comments, this URI (relative to
project) fails:

-/merge_requests/346/discussions.json?per_page=20

In the production.log, I found:

Completed 500 Internal Server Error in 764ms (ActiveRecord: 493.9ms | 
Elasticsearch: 0.0ms | Allocations: 144723)

Psych::DisallowedClass (Tried to load unspecified class: 
Gitlab::Diff::Position):

app/models/diff_discussion.rb:13:in `position'
app/models/diff_discussion.rb:51:in `cache_key'
app/controllers/concerns/issuable_actions.rb:186:in `render_mr_discussions'


Unfortunately, I haven't found a workaround yet. Do you have any idea
how to get comments in merge requests again?

Best,
Maximilian
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1018034: marked as done (gitlab: Content editor in Wiki breaks JavaScript)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1018034,
regarding gitlab: Content editor in Wiki breaks JavaScript
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1018034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Subject: gitlab: Content editor in Wiki breaks JavaScript
Package: gitlab
X-Debbugs-Cc: f+deb...@chezlefab.net
Version: 15.2.2+ds1-4~fto11+1
Severity: normal

Dear Maintainer,

I tried to enable Rich Text Editor while editing a Wiki page from some
project's wiki.

After doing so, I got an error message stating that an error occured.
The Raw editor disappeared, but the Rich Text Editor didn't appear.

Some errors appeared on the javascript console, saying that
t.contentEditor is undefined, and that some "plugins$" was loaded twice.

I confirmed with two other sysadmins running their own gitlab instances
that the bug is present in their instances too.

-- System Information:
Debian Release: 11.4
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable'), (100, 
'bullseye-fasttrack'), (100, 'bullseye-backports-staging')

Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
LC_ALL set to fr_FR.utf8), LANGUAGE not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  asciidoctor 2.0.16-1~fto11+1
ii  bc  1.07.1-2+b2
ii  bundler 2.2.5-2
ii  bzip2   1.0.8-4
ii  dbconfig-pgsql  2.0.19
ii  debconf [debconf-2.0]   1.5.77
ii  exim4-daemon-light [mail-trans  4.94.2-7
ii  fonts-font-awesome [node-font-  5.0.10+really4.7.0~dfsg-4.1
ii  gitlab-common   15.2.2+dfsg2-2~fto11+1
ii  gitlab-workhorse15.2.2+ds1-4~fto11+1
ii  katex [node-katex]  0.13.11+~cs6.0.0-2~bpo11+1
ii  libjs-bootstrap4 [node-bootstr  4.5.2+dfsg1-7
ii  libjs-codemirror [node-codemir  5.59.2+~cs0.23.109-1
ii  libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3
ii  libjs-popper.js [node-popper.j  1.16.1+ds-3
ii  libruby2.7 [ruby-webrick]   2.7.4-1+deb11u1
ii  lsb-base11.1.0
ii  nginx   1.18.0-6.1+deb11u2
ii  nginx-core [nginx]  1.18.0-6.1+deb11u2
ii  node-autosize   4.0.2~dfsg1-7
ii  node-axios  0.21.1+dfsg-1+deb11u1
ii  node-babel-loader   8.2.2-5
ii  node-babel-plugin-lodash3.3.4+~cs2.0.1-3
ii  node-babel7 7.12.12+~cs150.141.84-6
ii  node-brace-expansion2.0.0-1
ii  node-cache-loader   4.1.0+~cs2.0.0-1
ii  node-clipboard  2.0.8+ds+~cs9.6.11-1~bpo11+1
ii  node-compression-webpack-plugi  6.1.1-1
ii  node-copy-webpack-plugin5.1.2+~cs9.0.2-4
ii  node-core-js3.8.2-2
ii  node-cron-validator 1.3.1-1~bpo11+1
ii  node-css-loader 5.0.1+~cs14.0.5-1
ii  node-d3 5.16.0-4
ii  node-d3-selection   1.4.0-6
ii  node-dateformat 5.0.3-2~bpo11+1
ii  node-dompurify  2.3.7+dfsg-1~bpo11+1
ii  node-exports-loader 1.1.1-2
ii  node-file-loader6.2.0-2
ii  node-fuzzaldrin-plus0.5.0+dfsg-3
ii  node-glob   7.1.6+~7.1.3-1
ii  node-imports-loader 0.8.0-2
ii  node-jed1.1.1-2
ii  node-jquery 3.5.1+dfsg+~3.5.5-7
ii  node-jquery-ujs 1.2.2-2
ii  node-js-cookie  3.0.1+~3.0.0-2~bpo11+1
ii  node-js-yaml3.14.1+dfsg+~3.12.6-2
ii  node-jszip  3.5.0+dfsg-2
ii  node-jszip-utils0.0.2+dfsg-2
ii  node-lodash 
4.17.21+dfsg+~cs8.31.189.20210220-2~bpo11+1

ii  node-marked 0.8.0+ds+repack-2
ii  node-mermaid8.14.0+~cs11.4.14-1~bpo11+1
ii  node-minimatch  3.0.4+~3.0.3-1
ii  node-miragejs   0.1.41+~cs5.6.6-4
ii  node-mousetrap  1.6.5~ds-1
ii  node-postcss8.4.8+~cs7.3.21-2~bpo11+2
ii  node-prismjs1.23.0+dfsg-1+deb11u2
ii  node-prosemirror-markdown   1.6.0-1~bpo11+2
ii  node-prosemirror-model

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

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1019403,
regarding gitlab: failed to fetch comments in issue (500 Internal Server Error)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1019403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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: 66512)

NoMethodError (undefined method `h' for LabelsHelper:Module):

app/helpers/labels_helper.rb:250:in `render_label_text'
app/helpers/labels_helper.rb:61:in `render_colored_label'
lib/banzai/filter/references/label_reference_filter.rb:120:in 
`object_link_text'


To me, this seemed like a typo, so I simply removed "h " in
labels_helper.rb:250. This fixed the issue for me, as far as I can
tell.

Best,
Maximilian


---

--- a/usr/share/gitlab/app/helpers/labels_helper.rb
+++ b/usr/share/gitlab/app/helpers/labels_helper.rb
@@ -247,7 +247,7 @@
 class="#{css_class}"
 data-container="body"
 data-html="true"
-#{"style=\"background-color: #{h bg_color}\"" if bg_color}
+#{"style=\"background-color: #{bg_color}\"" if bg_color}
   >#{ERB::Util.html_escape_once(name)}#{suffix}
 HTML
   end
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1016551: marked as done (cawbird: Switch to librest 1.0 and libsoup3)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:04:13 +
with message-id 
and subject line Bug#1031551: Removed package(s) from unstable
has caused the Debian Bug report #1016551,
regarding cawbird: Switch to librest 1.0 and libsoup3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1016551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cawbird
Version: 1.5-1
Severity: serious
Forwarded: https://github.com/IBBoard/cawbird/issues/464

cawbird won't work with the new version of librest that is linked
against libsoup3. See more details in the forwarded bug.

We will upload the new librest to experimental soon after
https://bugs.debian.org/1015285 is handled.


Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.5-1+rm

Dear submitter,

as the package cawbird has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031551

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1015302: marked as done (Upgrading 14.10.5 to 15.0.4 aborts on db:migrate)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1015301,
regarding Upgrading 14.10.5 to 15.0.4 aborts on db:migrate
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1015301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gitlab
Version: 15.0.4+ds1-1
Severity: serious

Hey,

on upgrading gitlab I always end up with this error:

(1055 rows) = Did not find any relations. ]
+ echo gitlab_production database is not empty, skipping gitlab setup
gitlab_production database is not empty, skipping gitlab setup
+ runuser -u gitlab -- sh -c /usr/bin/bundle exec rake db:migrate
Attention: used pure ruby version of MurmurHash3
/usr/share/gitlab/lib/gitlab.rb:47: warning: already initialized 
constant Gitlab::APP_DIRS_PATTERN
/usr/share/gitlab/lib/gitlab.rb:47: warning: previous definition of 
APP_DIRS_PATTERN was here
/usr/share/gitlab/lib/gitlab.rb:48: warning: already initialized 
constant Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:48: warning: previous definition of 
VERSION was here
/usr/share/gitlab/lib/gitlab.rb:49: warning: already initialized 
constant Gitlab::INSTALLATION_TYPE
/usr/share/gitlab/lib/gitlab.rb:49: warning: previous definition of 
INSTALLATION_TYPE was here
/usr/share/gitlab/lib/gitlab.rb:50: warning: already initialized 
constant Gitlab::HTTP_PROXY_ENV_VARS
/usr/share/gitlab/lib/gitlab.rb:50: warning: previous definition of 
HTTP_PROXY_ENV_VARS was here
== 20220213103859 RemoveIntegrationsType: migrating 
===

rake aborted!
StandardError: An error has occurred, all later migrations canceled:

Gitlab::Database::BackgroundMigration::BatchedMigrationRunner::FailedToFinalize
/usr/share/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:76:in 
`finalize'
/usr/share/gitlab/lib/gitlab/database/background_migration/batched_migration_runner.rb:10:in 
`finalize'
/usr/share/gitlab/lib/gitlab/database/migrations/batched_background_migration_helpers.rb:139:in 
`finalize_batched_background_migration'
/usr/share/gitlab/lib/gitlab/database/migration_helpers.rb:962:in 
`ensure_batched_background_migration_is_finished'
/usr/share/gitlab/db/post_migrate/20220213103859_remove_integrations_type.rb:48:in 
`up'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:870:in 
`public_send'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:870:in 
`exec_migration'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:851:in 
`block (2 levels) in migrate'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:850:in 
`block in migrate'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/connection_adapters/abstract/connection_pool.rb:462:in 
`with_connection'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:849:in 
`migrate'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:1037:in 
`migrate'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:1329:in 
`block in execute_migration_in_transaction'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:1382:in 
`ddl_transaction'
/usr/share/gitlab/lib/gitlab/database/migrations/lock_retry_mixin.rb:36:in 
`ddl_transaction'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:1328:in 
`execute_migration_in_transaction'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:1302:in 
`each'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:1302:in 
`migrate_without_lock'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:1251:in 
`block in migrate'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:1401:in 
`block in with_advisory_lock'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/migration.rb:1416:in 
`block in with_advisory_lock_connection'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.4.7/lib/active_record/connection_adapters/abstract/connection_pool.rb:462:in 
`with_connection'

Bug#1015301: marked as done (gitlab: Upgrade to 15.0.4 fails because BackgroundMigrations could not finalize)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1015301,
regarding gitlab: Upgrade to 15.0.4 fails because BackgroundMigrations could 
not finalize
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1015301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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

/etc/systemd/system/gitaly.service.d/override.conf already exist

I moved the file away and the upgrade could continue. At the end of
the upgrade, gitaly did not start anymore, so I restored the file (it
actually contains the setting of the user running gitaly).

Then, however, I stumbled upon a much more serious issue: The database
migration could not finish as there were pending background jobs that
failed to finalize:

gitlab_production database is not empty, skipping gitlab setup
Attention: used pure ruby version of MurmurHash3
/usr/share/gitlab/lib/gitlab.rb:47: warning: already initialized constant 
Gitlab::APP_DIRS_PATTERN
/usr/share/gitlab/lib/gitlab.rb:47: warning: previous definition of 
APP_DIRS_PATTERN was here
/usr/share/gitlab/lib/gitlab.rb:48: warning: already initialized constant 
Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:48: warning: previous definition of VERSION 
was here
/usr/share/gitlab/lib/gitlab.rb:49: warning: already initialized constant 
Gitlab::INSTALLATION_TYPE
/usr/share/gitlab/lib/gitlab.rb:49: warning: previous definition of 
INSTALLATION_TYPE was here
/usr/share/gitlab/lib/gitlab.rb:50: warning: already initialized constant 
Gitlab::HTTP_PROXY_ENV_VARS
/usr/share/gitlab/lib/gitlab.rb:50: warning: previous definition of 
HTTP_PROXY_ENV_VARS was here
== 20220213103859 RemoveIntegrationsType: migrating 
===
rake aborted!
StandardError: An error has occurred, all later migrations canceled:


Gitlab::Database::BackgroundMigration::BatchedMigrationRunner::FailedToFinalize
…

I did some research, and found somebody else having a similar issue
[1]. Unfortunately, manually running the background jobs [2] did not
work either as they continued to fail. In the database I identified
the following stuck background migrations [3]:


gitlab_production=# select id,status,job_class_name, table_name, 
column_name, job_arguments from batched_background_migrations where status <> 3;
 id | status |  job_class_name  |  
table_name  | column_name | job_arguments 

++--+--+-+---
 17 |  4 | BackfillNamespaceIdForNamespaceRoute | routes
   | id  | []
 19 |  4 | BackfillMemberNamespaceForGroupMembers   | members   
   | id  | []
 20 |  4 | MigratePersonalNamespaceProjectMaintainerToOwner | members   
   | id  | []
 23 |  4 | BackfillGroupFeatures| 
namespaces   | id  | [1]
 15 |  4 | BackfillIntegrationsTypeNew  | 
integrations | id  | []
 16 |  4 | BackfillUserNamespace| 
namespaces   | id  | []
 18 |  4 | BackfillIssueSearchData  | issues
   | id  | []


I then proceeded to simply change the status of the jobs to 3 in the
database as proposed in the issue mentioned above [1]. I could then
finish the upgrade normally with `apt upgrade`.

Afterwards, I simply undid the database change (i.e., reverted the
status of the failed background migrations to 4) and then restarted
the migrations in the web UI.

As far as I can tell, everything seems normal now. The seven
background migration jobs are still pending, but I can continue to use
Gitlab normally.

Do you need any more information on the matter?

Thanks for your investigation into the issue!

Best,
Maximilian


[1]: https://gitlab.com/gitlab-org/gitlab/-/issues/340193
[2]: 
https://docs.gitlab.com/ee/user/admin_area/monitoring/background_migrations.html#manually-finishing-a-batched-background-migration
[3]: https://docs.gitlab.com/ee/update/index.html#batched-background-migrations

Bug#1012504: marked as done (cawbird: doesn't migrate because of autopkgtests failure)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:04:13 +
with message-id 
and subject line Bug#1031551: Removed package(s) from unstable
has caused the Debian Bug report #1012504,
regarding cawbird: doesn't migrate because of autopkgtests failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1012504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cawbird
Version: 1.5
Severity: important
Tags: patch
X-Debbugs-Cc: arnaud.ferra...@gmail.com

Dear Maintainer,

autopkgtests for cawbird currently fail, causing the package to be stuck in
unstable. This is due to the normal exit code of the "timeout" command being
124.

Attached patch 0001 fixes this issue so we can hope for this package to
transition normally.

While working on it, I fixed a few unrelated packaging issues reported by
lintian, see attached patches 0002 to 0004.

Cheers,
Arnaud


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cawbird depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  libatk1.0-0  2.38.0-1
ii  libc62.33-7
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libgdk-pixbuf-2.0-0  2.42.8+dfsg-1
ii  libglib2.0-0 2.72.1-1
ii  libgspell-1-21.10.0-1+b1
ii  libgstreamer1.0-01.20.2-1
ii  libgtk-3-0   3.24.33-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  liboauth01.0.3-5
ii  libpango-1.0-0   1.50.7+ds-1
ii  librest-0.7-00.8.1-1.1
ii  libsoup2.4-1 2.74.2-3
ii  libsqlite3-0 3.38.5-1
ii  libx11-6 2:1.7.5-1

cawbird recommends no packages.

cawbird suggests no packages.

-- no debconf information
>From cf17ae85a23799481fcacce1507f00d9aac71a59 Mon Sep 17 00:00:00 2001
From: Arnaud Ferraris 
Date: Wed, 8 Jun 2022 15:08:21 +0200
Subject: d/tests: ensure autopkgtest won't fail when successful

`timeout` will return the command's exit code if it ends before reaching
the configured timeout. If the command runs normally then is killed by
`timeout`, the exit code will be 124. The test should therefore pass in
this case.

This commit adds a script wrapping the actual call and returning 0 if
the command's exit code is 124.
---
 debian/tests/control  |  2 +-
 debian/tests/startup-test | 11 +++
 2 files changed, 12 insertions(+), 1 deletion(-)
 create mode 100755 debian/tests/startup-test

diff --git a/debian/tests/control b/debian/tests/control
index c0a271c..7215270 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,3 +1,3 @@
-Test-Command: xvfb-run timeout -k2 5 /usr/bin/cawbird
+Tests: startup-test
 Restrictions: superficial
 Depends: cawbird, xvfb, xauth
diff --git a/debian/tests/startup-test b/debian/tests/startup-test
new file mode 100755
index 000..294b7da
--- /dev/null
+++ b/debian/tests/startup-test
@@ -0,0 +1,11 @@
+#!/bin/sh
+
+xvfb-run timeout -k2 5 /usr/bin/cawbird
+_RET="$?"
+
+# timeout will exit with code 124 if all goes well
+if [ "$_RET" = "124" ]; then
+exit 0
+fi
+
+exit $_RET
-- 
2.35.1
>From 1424b3be1ae5f014cf7d689f9e62aa564aa7e2d0 Mon Sep 17 00:00:00 2001
From: Arnaud Ferraris 
Date: Wed, 8 Jun 2022 15:22:02 +0200
Subject: debian: remove unused README.Debian

Fixes: lintian: readme-debian-contains-debmake-template
---
 debian/README.Debian | 6 --
 1 file changed, 6 deletions(-)
 delete mode 100644 debian/README.Debian

diff --git a/debian/README.Debian b/debian/README.Debian
deleted file mode 100644
index 52820e7..000
--- a/debian/README.Debian
+++ /dev/null
@@ -1,6 +0,0 @@
-cawbird for Debian
--
-
-
-
- -- Federico Ceratto   Sat, 08 Jan 2022 15:22:41 +
-- 
2.35.1
>From cc0579d8d21a0ac0d16bf95f3e7d3dae7af4746b Mon Sep 17 00:00:00 2001
From: Arnaud Ferraris 
Date: Wed, 8 Jun 2022 15:22:49 +0200
Subject: 

Bug#1009942: marked as done (gitlab: textEncoding is not defined)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1009942,
regarding gitlab: textEncoding is not defined
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1009942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gitlab
Version: 14.8.5+ds1-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I tried experimental and fasttrack versions and the error is the same 
for configure step:


WARNING: This version of GitLab depends on gitlab-shell 13.23.2, but 
you're running 13.22.2. Please update gitlab-shell.
WARNING: This installation of GitLab uses a deprecated syntax for 
'config/database.yml'. The support for this syntax will be removed in 
15.0. More information can be found here: 
https://gitlab.com/gitlab-org/gitlab/-/issues/338182

rake aborted!
ExecJS::ProgramError: ReferenceError: textEncoding is not defined
(execjs):70276:4
(execjs):70297:14
(execjs):1:40
Object. ((execjs):1:58)
Module._compile (node:internal/modules/cjs/loader:1103:14)
Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
Module.load (node:internal/modules/cjs/loader:981:32)
Function.Module._load (node:internal/modules/cjs/loader:822:12)
Function.executeUserEntryPoint [as runMain] 
(node:internal/modules/run_main:77:12)

node:internal/main/run_main_module:17:47
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-10.4.2.0/lib/autoprefixer-rails/processor.rb:133:in 
`runtime'
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-10.4.2.0/lib/autoprefixer-rails/processor.rb:35:in 
`process'
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-10.4.2.0/lib/autoprefixer-rails/sprockets.rb:22:in 
`run'
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-10.4.2.0/lib/autoprefixer-rails/sprockets.rb:16:in 
`call'
/usr/share/rubygems-integration/all/gems/sprockets-rails-3.4.1/lib/sprockets/rails/task.rb:67:in 
`block (3 levels) in define'
/usr/share/rubygems-integration/all/gems/sprockets-rails-3.4.1/lib/sprockets/rails/task.rb:66:in 
`block (2 levels) in define'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in 
`'

Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned 
error exit status 1

Errors were encountered while processing:
 gitlab

Please help me to solve this situation.

Thx!

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (700, 
'experimental'), (500, 'stable'), (500, 'oldstable')

Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to C.UTF-8), LANGUAGE not set

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gitlab depends on:
ii  asciidoctor 2.0.16-2
ii  bc  1.07.1-3+b1
ii  bundler 2.3.5-2
ii  bzip2   1.0.8-5
ii  dbconfig-pgsql  2.0.21
ii  debconf [debconf-2.0]   1.5.79
ii  fonts-font-awesome [node-font-awesome] 5.0.10+really4.7.0~dfsg-4.1
ii  gitlab-common   14.8.5+dfsg-1
ii  gitlab-workhorse    14.8.5+ds1-3
ii  katex [node-katex]  0.13.11+~cs6.0.0-3
ii  libjs-bootstrap4 [node-bootstrap]   4.6.1+dfsg1-1
ii  libjs-codemirror [node-codemirror]  5.65.0+~cs5.83.9-1
ii  libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3
ii  libjs-popper.js [node-popper.js]    1.16.1+ds-5
ii  libruby2.7 [ruby-webrick]   2.7.5-1
ii  libruby3.0 [ruby-rexml] 3.0.3-1
ii  lsb-base    11.1.0
ii  nginx   1.18.0-9
ii  nginx-extras [nginx]    1.18.0-9
ii  node-autosize   4.0.4~dfsg1+~4.0.0-1
ii  node-axios  0.26.1+dfsg-1
ii  node-babel-loader   8.2.4-1
ii  node-babel-plugin-lodash    3.3.4+~cs2.0.1-5
ii  node-babel7 7.17.9+~cs214.260.191-1
ii  node-brace-expansion    2.0.1-1
ii  node-cache-loader   

Bug#1009954: marked as done (gitlab: Cannot install experimental or unstable version due to ruby-omniauth dependency)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1009954,
regarding gitlab: Cannot install experimental or unstable version due to 
ruby-omniauth dependency
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1009954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 14.8.5+ds1-3
Severity: important

Dear Maintainer,

So there is no way to install using experimental as the version of 
ruby-omniauth is no more
even in unstable.

apt-get -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libmbedcrypto3 libmbedtls12 libmbedx509-0 linux-image-5.16.0-6-amd64 
node-array-union node-array-uniq ruby-scientist
  ruby-securecompare ruby-sshkey
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up gitlab (14.8.5+ds1-3) ...
Successfully installed graphiql-rails-1.8.0
Parsing documentation for graphiql-rails-1.8.0
Done installing documentation for graphiql-rails after 0 seconds
1 gem installed
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Could not find gem 'omniauth (~> 1.8)' in cached gems or installed locally.

The source contains the following gems matching 'omniauth':
  * omniauth-2.0.4
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)

apt-cache policy ruby-omniauth
ruby-omniauth:
  Installed: 2.0.4-1~exp1
  Candidate: 2.0.4-1~exp1
  Version table:
 *** 2.0.4-1~exp1 100
  1 http://ftp.de.debian.org/debian experimental/main amd64 Packages
100 /var/lib/dpkg/status
 1.9.1-1 500
500 http://ftp.de.debian.org/debian unstable/main amd64 Packages
 1.8.1-1 500
500 http://ftp.de.debian.org/debian buster/main amd64 Packages


So there is no way to install using experimental.

-- System Information:
Debian Release: bookworm/sid
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 
'oldstable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging'), 
(1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-trunk-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gitlab depends on:
ii  asciidoctor 2.0.16-2
ii  bc  1.07.1-3+b1
ii  bundler 2.3.5-2
ii  bzip2   1.0.8-5
ii  dbconfig-pgsql  2.0.21
ii  debconf [debconf-2.0]   1.5.79
ii  exim4-daemon-light [mail-transport-age  4.95-5
ii  fonts-font-awesome [node-font-awesome]  5.0.10+really4.7.0~dfsg-4.1
ii  gitlab-common   14.8.5+dfsg-1
ii  gitlab-workhorse14.8.5+ds1-3
ii  katex [node-katex]  0.13.11+~cs6.0.0-3
ii  libjs-bootstrap4 [node-bootstrap]   4.6.1+dfsg1-1
ii  libjs-codemirror [node-codemirror]  5.65.0+~cs5.83.9-1
ii  libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3
ii  libjs-popper.js [node-popper.js]1.16.1+ds-5
ii  libruby2.7 [ruby-webrick]   2.7.5-1
ii  libruby3.0 [ruby-rexml] 3.0.3-1
ii  lsb-base11.1.0
ii  nginx   1.18.0-9
ii  nginx-core [nginx]  1.18.0-9
ii  node-autosize   4.0.4~dfsg1+~4.0.0-1
ii  node-axios  0.26.1+dfsg-1
ii  node-babel-loader   8.2.4-1
ii  node-babel-plugin-lodash3.3.4+~cs2.0.1-5
ii  node-babel7 7.17.9+~cs214.260.191-1
ii  node-brace-expansion2.0.1-1
ii  node-cache-loader  

Bug#1005178: marked as done (gitlab/experimental: binary-any FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:03:08 +
with message-id 
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #1005178,
regarding gitlab/experimental: binary-any FTBFS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1005178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab
Version: 14.6.4+ds1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=gitlab=14.6.4%2Bds1-1

...
dh_install -XLICENSE -O--package=gitlab-workhorse
dh_install: warning: Cannot find (any matches for) "debian/tmp/usr/bin" (tried 
in ., debian/tmp)

dh_install: warning: gitlab-workhorse missing files: debian/tmp/usr/bin
dh_install: error: missing files, aborting
make[1]: *** [debian/rules:35: override_dh_install] Error 25
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm

Dear submitter,

as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031519

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#984294: marked as done (photoflow: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:59:16 +
with message-id 
and subject line Bug#1031202: Removed package(s) from unstable
has caused the Debian Bug report #984294,
regarding photoflow: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:photoflow
Version: 0.2.8+git20200114-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/photoflow_0.2.8+git20200114-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
[ 45%] Building CXX object src/CMakeFiles/pfgui.dir/gui/widgets/layerlist.cc.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DLENSFUN_HAS_OVERLOADED_FIND_LENSES=1 
-DVIPS_GET_BLOB_REQUIRES_CONST_VOID_POINTER=1 -I/usr/include/gtkmm-3.0 
-I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 
-I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 
-I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 
-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 
-I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 
-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 
-I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freet
 ype2 -I/usr/include/libpng16 -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/<>/src/external 
-I/usr/include/OpenEXR -I/usr/include/libxml2 -I/usr/include/orc-0.4 
-I/usr/include/libgsf-1 -I/usr/include/x86_64-linux-gnu/ImageMagick-6 
-I/usr/include/ImageMagick-6 -I/usr/include/poppler/glib -I/usr/include/poppler 
-I/usr/include/librsvg-2.0 -I/usr/include/openslide 
-I/usr/lib/x86_64-linux-gnu/hdf5/serial/include -I/<>/src 
-I/<>/src/external/rawspeed/src/librawspeed 
-I/<>/src/external/rawspeed/src/external 
-I/<>/obj-x86_64-linux-gnu/src/external/rawspeed/src 
-I/usr/include/lensfun -I/<>/src/external/librtprocess/src/include 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FOR
 TIFY_SOURCE=2 -DPF_HAS_LENSFUN   -O3 -ftree-vectorize -funroll-loops 
-fomit-frame-pointer -DNDEBUG  -Dgmic_build -Dcimg_use_vt100 -Dcimg_use_fftw3 
-Dcimg_use_tiff -Dcimg_use_zlib -Dcimg_display=0 -fpermissive -std=gnu++14 
-Wno-error=narrowing -Dgmic_is_parallel -fno-ipa-sra -march=nocona 
-mtune=generic -I/<>/src/dt -DLIBRAW_NODLL 
-DINSTALL_PREFIX='"/usr"'  -Wno-deprecated-register 
-Wno-deprecated-declarations -DLOCALEDIR="/usr/share/locale" -DGTKMM_3  
-Wno-unused-parameter -fPIC -o CMakeFiles/pfgui.dir/gui/widgets/layerlist.cc.o 
-c 

Bug#947523: marked as done (gconf-editor: build-depends on deprecated gnome-doc-utils)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #947523,
regarding gconf-editor: build-depends on deprecated gnome-doc-utils
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
947523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gconf-editor
Version: 3.0.1-6
Severity: important
Control: block 936625 by -1
Control: block 889019 by -1
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gnome-doc-utils

This package Build-Depends on gnome-doc-utils. gnome-doc-utils is a
deprecated package of documentation utilities. Its most recent upstream
release was in 2012, with most changes in its git repository since then
being translation updates. The GNOME team do not consider gnome-doc-utils
to be suitable for release in Debian 11 'bullseye'.

The supported replacement is yelp.m4 in yelp-tools, as used
in many GNOME 3 packages. A porting guide is available:
https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure

gnome-doc-utils relies on Python 2 code that seems unlikely to be
converted to Python 3, so bug #936625 (part of the effort to remove
Python 2 from Debian for Debian 11 'bullseye') has its severity set to
serious. This means that this bug is highly likely to be elevated to
serious severity at some point in future.

Please convert this package to use yelp-tools, or if necessary remove
the documentation processing entirely.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#997548: marked as done (golang-github-alangpierce-go-forceexport: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/alangpierce/go-forceexport returned exit code 1)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:00:38 +
with message-id 
and subject line Bug#1031263: Removed package(s) from unstable
has caused the Debian Bug report #997548,
regarding golang-github-alangpierce-go-forceexport: FTBFS: dh_auto_test: error: 
cd _build && go test -vet=off -v -p 4 github.com/alangpierce/go-forceexport 
returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
997548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-alangpierce-go-forceexport
Version: 0.0~git20160317.8f1d694-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package 
> golang-github-alangpierce-go-forceexport
> dpkg-buildpackage: info: source version 0.0~git20160317.8f1d694-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Roger Shimizu 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --builddirectory=_build --buildsystem=golang --with=golang
>dh_auto_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_clean -O--builddirectory=_build -O--buildsystem=golang
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building golang-github-alangpierce-go-forceexport using 
> existing 
> ./golang-github-alangpierce-go-forceexport_0.0~git20160317.8f1d694.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building golang-github-alangpierce-go-forceexport in 
> golang-github-alangpierce-go-forceexport_0.0~git20160317.8f1d694-2.debian.tar.xz
> dpkg-source: info: building golang-github-alangpierce-go-forceexport in 
> golang-github-alangpierce-go-forceexport_0.0~git20160317.8f1d694-2.dsc
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 4 
> github.com/alangpierce/go-forceexport
> internal/unsafeheader
> internal/abi
> internal/cpu
> internal/goexperiment
> runtime/internal/atomic
> runtime/internal/sys
> internal/itoa
> runtime/internal/math
> math/bits
> unicode/utf8
> internal/race
> internal/bytealg
> math
> sync/atomic
> unicode
> runtime
> internal/reflectlite
> sync
> internal/testlog
> errors
> sort
> strconv
> io
> internal/oserror
> syscall
> path
> reflect
> internal/syscall/execenv
> time
> internal/syscall/unix
> io/fs
> internal/poll
> os
> internal/fmtsort
> fmt
> github.com/alangpierce/go-forceexport
>dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go test -vet=off -v -p 4 
> github.com/alangpierce/go-forceexport
> === RUN   TestTimeNow
> unexpected fault address 0x122a0
> fatal error: fault
> [signal SIGSEGV: segmentation violation code=0x1 addr=0x122a0 pc=0x4e8b9e]
> 
> goroutine 6 [running]:
> runtime.throw({0x5143d6, 0x551bad})
>   /usr/lib/go-1.17/src/runtime/panic.go:1198 +0x71 fp=0xc3a630 
> sp=0xc3a600 pc=0x433ef1
> runtime.sigpanic()
>   /usr/lib/go-1.17/src/runtime/signal_unix.go:742 +0x2f6 fp=0xc3a680 
> sp=0xc3a630 pc=0x448676
> github.com/alangpierce/go-forceexport.FindFuncWithName({0x514b53, 0x4f7980})
>   
> /<>/_build/src/github.com/alangpierce/go-forceexport/forceexport.go:60
>  +0xde fp=0xc3a700 sp=0xc3a680 pc=0x4e8b9e
> github.com/alangpierce/go-forceexport.GetFunc({0x4f1a60, 0xc0e040}, 
> {0x514b53, 0x11e0c62e})
>   
> /<>/_build/src/github.com/alangpierce/go-forceexport/forceexport.go:16
>  +0x2e fp=0xc3a728 sp=0xc3a700 pc=0x4e880e
> github.com/alangpierce/go-forceexport.TestTimeNow(0xc000112340)
>   
> /<>/_build/src/github.com/alangpierce/go-forceexport/forceexport_test.go:10
>  +0x49 fp=0xc3a770 sp=0xc3a728 pc=0x4e8cc9
> testing.tRunner(0xc000112340, 0x51e7b0)
>   

Bug#894056: marked as done (gconf-editor: only useful for gconf which is being removed from Debian)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #894056,
regarding gconf-editor: only useful for gconf which is being removed from Debian
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
894056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gconf-editor
Version: 3.0.1-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

As announced, we are working to remove gconf from Debian. As part of this 
process, I am now filing this RC bug.

References
--
https://lists.debian.org/debian-devel/2018/02/msg00169.html

https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintain...@lists.alioth.debian.org;tag=gconf

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#829951: marked as done (gconf-editor: Uses deprecated gnome-common macros/variables)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #829951,
regarding gconf-editor: Uses deprecated gnome-common macros/variables
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
829951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gconf-editor
Version: 3.0.1-3
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-common

Hi,

gnome-common did a cleanup upstream and deprecated quite a few macros
and variables.

gnome-doc-utils removal
===
The gnome-doc-utils build infrastructure was removed completely along
with the following macros:

 GNOME_DOC_INIT [1]
 GNOME_COMMON_INIT [2]


deprecated variables

The following variables used in gnome-autogen.sh have been declared
deprecated [3]:

 REQUIRED_GNOME_DOC_UTILS_VERSION
 REQUIRED_DOC_COMMON_VERSION
 USE_COMMON_DOC_BUILD
 FORBIDDEN_M4MACROS
 GNOME2_DIR
 GNOME2_PATH
 USE_GNOME2_MACROS

deprecated macros
=
The following macros have also been declared deprecated:

 GNOME_COMPILE_WARNINGS [4]
 GNOME_CXX_WARNINGS [5]

Upstream has documentation at [6] with how you can fix your package and
why those particular changes were made.

According to codesearch.d.n your package gconf-editor uses one of the macros or
variables so might be affected, especially once you run autoreconf. Please
update your package accordingly and forward it to upstream if possible.

If you have further question, please don't hesitate to ask.

Regards,
Michael

[1] https://git.gnome.org/browse/gnome-common/commit/?id=6684e2fa5
[2] https://git.gnome.org/browse/gnome-common/commit/?id=1f60e9536
[3] https://git.gnome.org/browse/gnome-common/commit/?id=4c8d8ad93
[4] https://git.gnome.org/browse/gnome-common/commit/?id=b57bae0be
[5] https://git.gnome.org/browse/gnome-common/commit/?id=2bffd7e1u
[6] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#661577: marked as done (gconf-editor: Program received signal SIGSEGV, Segmentation fault.)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #661577,
regarding gconf-editor: Program received signal SIGSEGV, Segmentation fault.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
661577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gconf-editor
Version: 3.0.1-1
Severity: normal

gconf-editor has been segfaulting regularly for me after an upgrade to
wheezy.  It happens when I press Enter after editing an items value.
The gdb backtrace from when I altered
/apps/control-centre/network/SOE/proxy/host (a string field) is:

  $ gdb gconf-editor 
  GNU gdb (GDB) 7.3-debian Copyright (C) 2011 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show
  copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  ...
  Reading symbols from /usr/bin/gconf-editor...(no debugging symbols 
found)...done.
  (gdb) run
  Starting program: /usr/bin/gconf-editor 
  [Thread debugging using libthread_db enabled]
  [New Thread 0x7fffeb6dc700 (LWP 5362)]

  Program received signal SIGSEGV, Segmentation fault.
  0x7682837a in g_hash_table_iter_init () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) backtrace
  #0  0x7682837a in g_hash_table_iter_init () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x77827988 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #2  0x77827a0d in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #3  0x772e94df in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #4  0x7683a0cf in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x7683a8c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #6  0x7683ae02 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x776a3fdd in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #8  0x0040b1c9 in ?? ()
  #9  0x7626eead in __libc_start_main (main=, 
argc=, ubp_av=, 
  init=, fini=, rtld_fini=, 
stack_end=0x7fffe248)
  at libc-start.c:228
  #10 0x0040b25d in ?? ()
  #11 0x7fffe248 in ?? ()
  #12 0x001c in ?? ()
  #13 0x0001 in ?? ()
  #14 0x7fffe530 in ?? ()
  #15 0x in ?? ()
  (gdb) 

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gconf-editor depends on:
ii  gconf-defaults-service  2.32.4-1
ii  gconf2  2.32.4-1
ii  libc6   2.13-26
ii  libgconf2-4 2.32.4-1
ii  libglib2.0-02.30.2-6
ii  libgtk-3-0  3.2.3-1
ii  libpango1.0-0   1.29.4-2
ii  policykit-1-gnome   0.105-2

gconf-editor recommends no packages.

gconf-editor suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#661183: marked as done (gconf-editor: Moving via arrowkeys in tree)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #661183,
regarding gconf-editor: Moving via arrowkeys in tree
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
661183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gconf-editor
Version: 3.0.1-1
Severity: wishlist

Dear Maintainer,

It's be much easely to move in option tree using arrows.


-- System Information: Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (550, 'testing'), (500, 'testing-proposed-updates'), (500, 
'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gconf-editor depends on:
ii  gconf-defaults-service  2.32.4-1
ii  gconf2  2.32.4-1
ii  libc6   2.13-26
ii  libgconf2-4 2.32.4-1
ii  libglib2.0-02.30.2-6
ii  libgtk-3-0  3.2.3-1
ii  libpango1.0-0   1.29.4-2
ii  policykit-1-gnome   0.105-2

gconf-editor recommends no packages.

gconf-editor suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#650766: marked as done (gconf-editor: inconsistent layout of context help)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #650766,
regarding gconf-editor: inconsistent layout of context help
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
650766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gconf-editor
Version: 3.0.1-1
Severity: normal

gconf-editor have three subwindows:
  left - tree with folder
  right - keys in selected folder
  bottom - context help (key documentation) for selected key


key documentation shows 4 lines:
   a) full key name
   b) owner of key
   c) short description
   d) long description

key documentation lacks key type information, but we will ignore this
  (it can be infered from the icon of key in key list)

However, I find that items b,c,d have vertical spacing beetween them,
and this spacing equal c-b, d-c, but is essentially pseudorandom
for each key. Every time i change different key, a labals and descriptions
jumps around, without sense. It sometimes even makes last description text
to be not fitting inside key documentation window - gconf-editor
is sometimes tring to make it automatically larger, but fails
to do this, and in such case I somehow also cannot change
this subwindow size bigger (or smaller).

gconf-editor should switch to other layout model (I guess this is
VBox), and use small constant vertical spacing beetween elements,
leaving only last entry (or adding one), which can automatically
fill whole remaining space (but requests only 0, if asked).

Thanks,
Witek



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gconf-editor depends on:
ii  gconf-defaults-service  3.2.3-1 
ii  gconf2  3.2.3-1 
ii  libc6   2.13-21 
ii  libgconf2-4 3.2.3-1 
ii  libglib2.0-02.30.2-4
ii  libgtk-3-0  3.2.2-3 
ii  libpango1.0-0   1.29.4-2
ii  policykit-1-gnome   0.105-1 

gconf-editor recommends no packages.

gconf-editor suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#645304: marked as done (gconf-editor: search box should keep previous search term)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #645304,
regarding gconf-editor: search box should keep previous search term
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
645304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gconf-editor
Version: 3.0.0-2
Severity: wishlist

When doing a search in gconf-editor, it'd be useful if on the next
search, the search string and settings were kept, since I often refine a
search once or twice if I don't know exactly what I'm looking for.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are



--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#614991: marked as done (german translation: parameter wrong)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #614991,
regarding german translation: parameter wrong
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
614991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gconf-editor
Version: 2.30.0-2
Severity: important

gconf-editor: The extended german description for /apps/gnome/toolbar_style
explains possible parameters, where the parameter »icon« is misspelled an
should be »icons«



-- System Information:
Debian Release: 6.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gconf-editor depends on:
ii  gconf-defaults-service 2.28.1-6  GNOME configuration database syste
ii  gconf2 2.28.1-6  GNOME configuration database syste
ii  libc6  2.11.2-10 Embedded GNU C Library: Shared lib
ii  libdbus-glib-1-2   0.88-2.1  simple interprocess messaging syst
ii  libgconf2-42.28.1-6  GNOME configuration database syste
ii  libglib2.0-0   2.24.2-1  The GLib library of C routines
ii  libgtk2.0-02.20.1-2  The GTK+ graphical user interface 
ii  libpango1.0-0  1.28.3-1+squeeze1 Layout and rendering of internatio
ii  policykit-1-gnome  0.96-3GNOME authentication agent for Pol

gconf-editor recommends no packages.

gconf-editor suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#528987: marked as done (gconf-editor: I suggest a wording change in the description, please.)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #528987,
regarding gconf-editor: I suggest a wording change in the description, please.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
528987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gconf-editor
Version: 2.22.0-1
Severity: minor

>From "aptitude show gconf-editor":

   This is not the recommended way of setting desktop 
   preferences, ...

"That's not very helpful," is the upshot of this report.  :-)

   ... but it might be useful when the proper 
   configuration utility for some software 
   provides no way of changing some option.

I think it would be useful to change "This is not" to $BLAH where BLAH ==
"$(whatever_IS_the recommended_way) is".  Eg.:

   Your preferred Desktop Manager is the recommended way of setting
   desktop preferences, but this might be useful when the proper
   configuration utility for some software provides no way of
   changing some option.

I'm assuming here that that's what you meant?

  -

Hi.  This is a laptop.  I've a few others running here, but it's my 
primary machine.  

I'm one of those so-called corner-cases in that I don't use 
Gnome/KDE.  I install a minimal base, then augment with fluxbox 
and run startx from CLI.  Meaning, I don't have what you may 
assume to be, "the recommended way of setting desktop preferences," 
installed.  So, I go looking in the packaging system for a way to 
control Gnome apps, find gconf-editor, and your description tells 
me not to use it, and offers no simple alternative.  Hence, the above
alternative.

I hate the way modern X stuff (Gnome, KDE, ...) essentially ignore 
X resources.  However, I'm willing to learn how the new way works 
for the few apps of that ilk I use, as long as I don't need to suffer
Gnome/KDE.

Thanks for all your efforts.  Have fun.  I think Lenny's teriffic!  :-)

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#476904: marked as done (gconf-editor: please add context menu options to main menu also)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #476904,
regarding gconf-editor: please add context menu options to main menu also
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
476904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gconf-editor
Version: 2.22.0-1
Severity: normal

It is bad useability that the context menu options (like unset key) are
only available through the context menu, and not through the main menu.
Thist makes gconf-editor unusable without a mouse.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gconf-editor depends on:
ii  gconf22.22.0-1   GNOME configuration database syste
ii  libc6 2.7-10 GNU C Library: Shared libraries
ii  libgconf2-4   2.22.0-1   GNOME configuration database syste
ii  libglib2.0-0  2.16.3-2   The GLib library of C routines
ii  libgnome2-0   2.20.1.1-1 The GNOME 2 library - runtime file
ii  libgnomeui-0  2.20.1.1-1 The GNOME 2 libraries (User Interf
ii  libgtk2.0-0   2.12.9-3   The GTK+ graphical user interface 
ii  libpango1.0-0 1.20.2-2   Layout and rendering of internatio

gconf-editor recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1031263: marked as done (RM: golang-github-alangpierce-go-forceexport -- RoQA; Not working since Go1.17, upstream seems abandoned)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:00:34 +
with message-id 
and subject line Bug#1031263: Removed package(s) from unstable
has caused the Debian Bug report #1031263,
regarding RM: golang-github-alangpierce-go-forceexport -- RoQA; Not working 
since Go1.17, upstream seems abandoned
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: golang-github-alangpierce-go-forceexp...@packages.debian.org, 
z...@debian.org
Control: affects -1 + src:golang-github-alangpierce-go-forceexport


It FTBFS for a long time. Last upstream commit is at 2016.
It was introduced as Build-Depends of Syncthing, not needed anymore.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

golang-github-alangpierce-go-forceexport | 0.0~git20160317.8f1d694-2 | source
golang-github-alangpierce-go-forceexport-dev | 0.0~git20160317.8f1d694-2 | all

--- Reason ---
RoQA; Not working since Go1.17, upstream seems abandoned
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1031263

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#465687: marked as done (gconf-editor: Please support multiple user configuration sources)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #465687,
regarding gconf-editor: Please support multiple user configuration sources
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
465687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gconf-editor
Version: 2.20.0-2
Severity: wishlist

gconf-editor can help a system administrator manage mandatory and
default settings.  This implies support for editing alternate
configuration sources.  I'd like to use the same support to edit an
additional configuration source in my home directory, which I can use
for settings I synchronize across machines.  Thus, I'd like the
ability to set an alternate configuration source in gconf-editor, and
get options similar to the existing "Set as Default", "Set as
Mandatory", "New Defaults Window", and "New Mandatory Window" for my
alternate configuration source.

- Josh Triplett

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gconf-editor depends on:
ii  gconf2   2.20.1-2+b1 GNOME configuration database syste
ii  libc62.7-6   GNU C Library: Shared libraries
ii  libgconf2-4  2.20.1-2+b1 GNOME configuration database syste
ii  libglib2.0-0 2.14.6-1The GLib library of C routines
ii  libgnome2-0  2.20.1.1-1  The GNOME 2 library - runtime file
ii  libgnomeui-0 2.20.1.1-1  The GNOME 2 libraries (User Interf
ii  libgtk2.0-0  2.12.8-1The GTK+ graphical user interface 
ii  libpango1.0-01.18.4-1Layout and rendering of internatio

gconf-editor recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#179299: marked as done (gconf-editor: Forgets layout when closed)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #179299,
regarding gconf-editor: Forgets layout when closed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
179299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=179299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gconf-editor
Version: 0.4.0-1
Severity: minor

When I quit gconf-editor it forgets the window size, and relative panel
sizes and instead resets itself to a piddling 640x400 sized window.

Surely gconf-editor knows how to read and write such things into the
Gnome configuration database! :-)

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux kant.mcmillan.net.nz 2.4.17 #2 Sat Sep 7 22:16:25 NZST 2002 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages gconf-editor depends on:
ii  libatk1.0-0   1.2.2-2The ATK accessibility library
ii  libc6 2.3.1-10   GNU C Library: Shared libraries an
ii  libgconf2-4   2.2.0-1GNOME configuration database syste
ii  libglib2.0-0  2.2.0-2The GLib library of C routines
ii  libgtk2.0-0   2.2.0-3The GTK+ graphical user interface 
ii  liblinc1  1:1.0.0-1  library to simplify creating netwo
ii  liborbit2 1:2.6.0-1  Libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0 1.2.0-3Layout and rendering of internatio
ii  libpopt0  1.6.4-2lib for parsing cmdline parameters

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1031397: marked as done (RM: python-omemo-backend-signal -- ROM; obsolete, unmaintained)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:01:17 +
with message-id 
and subject line Bug#1031397: Removed package(s) from unstable
has caused the Debian Bug report #1031397,
regarding RM: python-omemo-backend-signal -- ROM; obsolete, unmaintained
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove

Please remove python-omemo-backend-signal from unstable.
It is superceded by actively maintained python-omemo.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-omemo-backend-signal | 0.3.0~beta-1 | source
python3-omemo-backend-signal | 0.3.0~beta-1 | all

--- Reason ---
ROM; obsolete, unmaintained
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1031397

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1031242: marked as done (RM: django-hvad -- ROM; abandoned upstream ; unmaintained; EOL upstream)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:59:46 +
with message-id 
and subject line Bug#1031242: Removed package(s) from unstable
has caused the Debian Bug report #1031242,
regarding RM: django-hvad -- ROM; abandoned upstream ; unmaintained; EOL 
upstream
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove

Please remove the source package django-hvad and all its binary packages from 
bookworm and sid.


There have been no new commits upstream in 6 years, and this no longer works 
with the version of Django that is in bookworm.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

django-hvad |1.8.0-2 | source
python3-django-hvad |1.8.0-2 | all

--- Reason ---
ROM; abandoned upstream ; unmaintained; EOL upstream
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1031242

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1031202: marked as done (RM: photoflow -- ROM; appears dead upstream, FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:59:12 +
with message-id 
and subject line Bug#1031202: Removed package(s) from unstable
has caused the Debian Bug report #1031202,
regarding RM: photoflow -- ROM; appears dead upstream, FTBFS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ftp.debian.org
Severity: normal

Doesn't build anymore, please remove this from the archive.

Thanks,
Gurkan
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 photoflow | 0.2.8+git20200114-3 | source, amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x

--- Reason ---
ROM; appears dead upstream, FTBFS
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1031202

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1031172: marked as done (RM: gconf-editor -- ROM; not in bullseye or bookworm, obsolete)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:21 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #1031172,
regarding RM: gconf-editor -- ROM; not in bullseye or bookworm, obsolete
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

gconf-editor is obsolete, and is already not in bullseye or bookworm.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

gconf-editor |3.0.1-6 | source, amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
ROM; not in bullseye or bookworm, obsolete
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1031172

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1026622: marked as done (python-omemo-backend-signal: FTBFS: ModuleNotFoundError: No module named 'omemo.backends')

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 01:01:21 +
with message-id 
and subject line Bug#1031397: Removed package(s) from unstable
has caused the Debian Bug report #1026622,
regarding python-omemo-backend-signal: FTBFS: ModuleNotFoundError: No module 
named 'omemo.backends'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1026622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-omemo-backend-signal
Version: 0.3.0~beta-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>/omemo_backend_signal'
> protoc --python_out=. WhisperTextProtocol.proto
> mv WhisperTextProtocol_pb2.py whispertextprotocol_pb2.py
> make[2]: Leaving directory '/<>/omemo_backend_signal'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal
> copying omemo_backend_signal/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal
> copying omemo_backend_signal/project.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal
> copying omemo_backend_signal/wireformat.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal
> copying omemo_backend_signal/backend.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal
> copying omemo_backend_signal/whispertextprotocol_pb2.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal
> copying omemo_backend_signal/version.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal
> creating 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/x3dh
> copying omemo_backend_signal/x3dh/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/x3dh
> copying omemo_backend_signal/x3dh/state.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/x3dh
> copying omemo_backend_signal/x3dh/x3dhpkencoder.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/x3dh
> creating 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/doubleratchet
> copying omemo_backend_signal/doubleratchet/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/doubleratchet
> copying omemo_backend_signal/doubleratchet/cbcaead.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/doubleratchet
> copying omemo_backend_signal/doubleratchet/sendrecvchain.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/doubleratchet
> copying omemo_backend_signal/doubleratchet/rootchain.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/doubleratchet
> copying omemo_backend_signal/doubleratchet/doubleratchet.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/doubleratchet
> copying omemo_backend_signal/doubleratchet/symmetrickeyratchet.py -> 
> /<>/.pybuild/cpython3_3.11_omemo_backend_signal/build/omemo_backend_signal/doubleratchet
> running egg_info
> creating omemo_backend_signal.egg-info
> writing omemo_backend_signal.egg-info/PKG-INFO
> writing dependency_links to omemo_backend_signal.egg-info/dependency_links.txt
> writing requirements to omemo_backend_signal.egg-info/requires.txt
> writing top-level names to omemo_backend_signal.egg-info/top_level.txt
> writing manifest file 'omemo_backend_signal.egg-info/SOURCES.txt'
> reading manifest file 'omemo_backend_signal.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'omemo_backend_signal.egg-info/SOURCES.txt'
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.10_omemo_backend_signal/build/omemo_backend_signal
> copying omemo_backend_signal/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_omemo_backend_signal/build/omemo_backend_signal
> copying omemo_backend_signal/project.py -> 
> /<>/.pybuild/cpython3_3.10_omemo_backend_signal/build/omemo_backend_signal
> copying omemo_backend_signal/wireformat.py -> 
> 

Bug#1018898: marked as done (gconf-editor: Intent to request removal from Debian)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:58:31 +
with message-id 
and subject line Bug#1031172: Removed package(s) from unstable
has caused the Debian Bug report #1018898,
regarding gconf-editor: Intent to request removal from Debian
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1018898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gconf-editor
Version: 3.0.1-6
Severity: serious
Tags: bookworm sid

gconf-editor was removed from Testing two and a half years ago.

Its only purpose is to enable editing gconf settings which are only
used by a very small number of packages and are functionally obsolete.

I remember that the last time I tried to remove this package years
ago, the current maintainer had strong feelings against it so I
figured it was best for me to file this bug first.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 3.0.1-6+rm

Dear submitter,

as the package gconf-editor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031172

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1031302: marked as done (devscripts FTBFS with black 23.1.0)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:35:20 +
with message-id 
and subject line Bug#1031302: fixed in devscripts 2.23.2
has caused the Debian Bug report #1031302,
regarding devscripts FTBFS with black 23.1.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: devscripts
Version: 2.23.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=devscripts=s390x=2.23.1=1676400700=0
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/devscripts.html

...
==
FAIL: test_black (devscripts.test.test_black.BlackTestCase.test_black)
Test: Run black code formatter on Python source code.
--
Traceback (most recent call last):
  File "/build/1st/devscripts-2.23.1/scripts/devscripts/test/test_black.py", 
line 43, in test_black
self.fail(
AssertionError: black found code that needs reformatting:
--- wrap-and-sort   2023-02-04 23:33:58 +
+++ wrap-and-sort   2024-03-19 01:21:02.603765 +
@@ -193,11 +193,10 @@
 return True
 return False
 
 
 class InstallContent:
-
 __slots__ = ("content", "comments")
 
 def __init__(self, content, comments=None):
 self.content = content
 self.comments = comments
--- sadt2023-02-04 23:33:58 +
+++ sadt2024-03-19 01:21:02.593172 +
@@ -129,11 +129,10 @@
 def close(self):
 pass
 
 
 class DefaultProgress(Progress):
-
 _hourglass = r"/-\|"
 
 def __init__(self):
 self._counter = 0
 self._output = False
--- debootsnap  2023-02-04 23:33:58 +
+++ debootsnap  2024-03-19 01:21:02.985582 +
@@ -652,11 +652,10 @@
 for source in sources:
 print(source.deb_line(), end="")
 sys.exit(0)
 
 with tempfile.TemporaryDirectory() as tmpdirname:
-
 download_packages(tmpdirname, sources, pkgs, nativearch, foreignarches)
 
 create_repo(tmpdirname, pkgs)
 
 newpkgs = run_mmdebstrap(

--
Ran 17 tests in 37.834s

FAILED (failures=1)
Test failed: 
error: Test failed: 
make[3]: *** [Makefile:103: test_py] Error 1
--- End Message ---
--- Begin Message ---
Source: devscripts
Source-Version: 2.23.2
Done: Benjamin Drung 

We believe that the bug you reported is fixed in the latest version of
devscripts, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated devscripts package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Feb 2023 00:56:21 +0100
Source: devscripts
Built-For-Profiles: noudeb
Architecture: source
Version: 2.23.2
Distribution: unstable
Urgency: medium
Maintainer: Devscripts Maintainers 
Changed-By: Benjamin Drung 
Closes: 1030141 1031302 1031549
Changes:
 devscripts (2.23.2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yadd ]
   * Update French translation
 .
   [ Paul Wise ]
   * wnpp-alert: Fix wnpp-alert --diff, which probably never worked
 .
   [ Benjamin Drung ]
   * Format code with black 23.1 (Closes: #1031302)
   * build-rdeps: Document -q in man page (Closes: #1030141)
   * Update translations for recent changes
 .
   [ Jakub Wilk ]
   * debchange.1: Fix uneven indentation in option list (Closes: #1031549)
Checksums-Sha1:
 a003e3b41cb1a1e1e908cc6fe74b90aacd74194e 3372 devscripts_2.23.2.dsc
 d41f943571b70bcd99cb52f15bd58b2e059c2ec2 993948 devscripts_2.23.2.tar.xz
 8a93dc96858b2b0c052f8ecf4e1e5e77f1faa0fd 17576 
devscripts_2.23.2_source.buildinfo
Checksums-Sha256:
 cb13a475d045533e3e0a2cf2291e14b3dbeda929ae5c1bad4573a86a0ac03b7f 3372 
devscripts_2.23.2.dsc
 d526c10e7324f695d47161847aafbb200653073d7310fc3e4015eee68e08ced1 993948 
devscripts_2.23.2.tar.xz
 f07e3ef8192839ad990e8ee070592b6fe9008f08282313b85564514fcde6f27f 17576 

Bug#1031487: marked as done (devscripts: FTBFS: AssertionError: black found code that needs reformatting:)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:35:20 +
with message-id 
and subject line Bug#1031302: fixed in devscripts 2.23.2
has caused the Debian Bug report #1031302,
regarding devscripts: FTBFS: AssertionError: black found code that needs 
reformatting:
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: devscripts
Version: 2.23.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[3]: Entering directory '/<>/scripts'
> perl -I ../lib -c bts; \
> 
> perl -I ../lib -c build-rdeps; \
> 
> perl -I ../lib -c chdist; \
> 
> perl -I ../lib -c checkbashisms; \
> 
> perl -I ../lib -c cvs-debuild; \
> 
> perl -I ../lib -c dd-list; \
> 
> perl -I ../lib -c deb-why-removed; \
> 
> perl -I ../lib -c debc; \
> 
> cvs-debuild syntax OK
> perl -I ../lib -c debchange; \
> 
> build-rdeps syntax OK
> perl -I ../lib -c debcheckout; \
> 
> debc syntax OK
> perl -I ../lib -c debcommit; \
> 
> chdist syntax OK
> perl -I ../lib -c debdiff; \
> 
> deb-why-removed syntax OK
> perl -I ../lib -c debi; \
> 
> debcommit syntax OK
> perl -I ../lib -c debpkg; \
> 
> debchange syntax OK
> perl -I ../lib -c debrebuild; \
> 
> debpkg syntax OK
> perl -I ../lib -c debsnap; \
> 
> checkbashisms syntax OK
> perl -I ../lib -c debuild; \
> 
> debcheckout syntax OK
> perl -I ../lib -c dep3changelog; \
> 
> debdiff syntax OK
> debi syntax OK
> perl -I ../lib -c desktop2menu; \
> 
> perl -I ../lib -c dget; \
> 
> bts syntax OK
> perl -I ../lib -c dpkg-depcheck; \
> 
> dd-list syntax OK
> perl -I ../lib -c dscverify; \
> 
> dep3changelog syntax OK
> perl -I ../lib -c git-deborig; \
> 
> debsnap syntax OK
> perl -I ../lib -c grep-excuses; \
> 
> debuild syntax OK
> perl -I ../lib -c hardening-check; \
> 
> desktop2menu syntax OK
> perl -I ../lib -c mass-bug; \
> 
> grep-excuses syntax OK
> perl -I ../lib -c mk-build-deps; \
> 
> dget syntax OK
> dpkg-depcheck syntax OK
> perl -I ../lib -c mk-origtargz; \
> 
> mass-bug syntax OK
> perl -I ../lib -c namecheck; \
> 
> perl -I ../lib -c origtargz; \
> 
> dscverify syntax OK
> perl -I ../lib -c plotchangelog; \
> 
> hardening-check syntax OK
> perl -I ../lib -c rc-alert; \
> 
> git-deborig syntax OK
> perl -I ../lib -c rmadison; \
> 
> debrebuild syntax OK
> namecheck syntax OK
> perl -I ../lib -c salsa; \
> 
> perl -I ../lib -c svnpath; \
> 
> plotchangelog syntax OK
> perl -I ../lib -c tagpending; \
> 
> rmadison syntax OK
> perl -I ../lib -c transition-check; \
> 
> svnpath syntax OK
> perl -I ../lib -c uscan; \
> 
> origtargz syntax OK
> perl -I ../lib -c who-permits-upload; \
> 
> mk-build-deps syntax OK
> bash -n annotate-output
> bash -n archpath
> transition-check syntax OK
> bash -n cowpoke
> bash -n cvs-debi
> bash -n cvs-debrelease
> bash -n dcmd
> bash -n deb-reversion
> bash -n debclean
> bash -n debrelease
> bash -n debrepro
> bash -n debrsign
> bash -n debsign
> bash -n diff2patches
> bash -n dpkg-genbuilddeps
> bash -n dscextract
> bash -n edit-patch
> bash -n getbuildlog
> bash -n list-unreleased
> bash -n ltnu
> rc-alert syntax OK
> bash -n manpage-alert
> bash -n mergechanges
> tagpending syntax OK
> bash -n nmudiff
> bash -n pts-subscribe
> bash -n run_bisect
> bash -n run_bisect_qemu
> bash -n uupdate
> bash -n what-patch
> bash -n who-uploads
> bash -n whodepends
> bash -n wnpp-alert
> bash -n wnpp-check
> mk-origtargz syntax OK
> who-permits-upload syntax OK
> py3versions: no X-Python3-Version in control file, using supported versions
> python3.11 setup.py test
> salsa syntax OK
> uscan syntax OK
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> creating devscripts.egg-info
> writing devscripts.egg-info/PKG-INFO
> writing dependency_links to devscripts.egg-info/dependency_links.txt
> writing top-level names to devscripts.egg-info/top_level.txt
> writing manifest file 'devscripts.egg-info/SOURCES.txt'
> reading manifest file 'devscripts.egg-info/SOURCES.txt'
> writing manifest file 'devscripts.egg-info/SOURCES.txt'
> running build_ext
> test_black (devscripts.test.test_black.BlackTestCase.test_black)
> Test: Run black code formatter on Python source code. ... Running 

Bug#1031549: marked as done (debchange man page: uneven indentation in option list)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:35:20 +
with message-id 
and subject line Bug#1031549: fixed in devscripts 2.23.2
has caused the Debian Bug report #1031549,
regarding debchange man page: uneven indentation in option list
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: devscripts
Version: 2.23.1
Severity: minor
Tags: patch

--
Jakub Wilk
diff --git a/scripts/debchange.1 b/scripts/debchange.1
index 752a4503..d1f02de3 100644
--- a/scripts/debchange.1
+++ b/scripts/debchange.1
@@ -314,7 +314,7 @@ Preserve the source tree directory name if the upstream version number
 (or the version number of a Debian native package) changes.  See also
 the configuration variables section below.
 .TP
-\fB \-\-no\-preserve\fR, \fB\-\-nopreserve\fR
+\fB\-\-no\-preserve\fR, \fB\-\-nopreserve\fR
 Do not preserve the source tree directory name (default).
 .TP
 \fB\-\-vendor \fIvendor\fR
--- End Message ---
--- Begin Message ---
Source: devscripts
Source-Version: 2.23.2
Done: Benjamin Drung 

We believe that the bug you reported is fixed in the latest version of
devscripts, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated devscripts package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Feb 2023 00:56:21 +0100
Source: devscripts
Built-For-Profiles: noudeb
Architecture: source
Version: 2.23.2
Distribution: unstable
Urgency: medium
Maintainer: Devscripts Maintainers 
Changed-By: Benjamin Drung 
Closes: 1030141 1031302 1031549
Changes:
 devscripts (2.23.2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yadd ]
   * Update French translation
 .
   [ Paul Wise ]
   * wnpp-alert: Fix wnpp-alert --diff, which probably never worked
 .
   [ Benjamin Drung ]
   * Format code with black 23.1 (Closes: #1031302)
   * build-rdeps: Document -q in man page (Closes: #1030141)
   * Update translations for recent changes
 .
   [ Jakub Wilk ]
   * debchange.1: Fix uneven indentation in option list (Closes: #1031549)
Checksums-Sha1:
 a003e3b41cb1a1e1e908cc6fe74b90aacd74194e 3372 devscripts_2.23.2.dsc
 d41f943571b70bcd99cb52f15bd58b2e059c2ec2 993948 devscripts_2.23.2.tar.xz
 8a93dc96858b2b0c052f8ecf4e1e5e77f1faa0fd 17576 
devscripts_2.23.2_source.buildinfo
Checksums-Sha256:
 cb13a475d045533e3e0a2cf2291e14b3dbeda929ae5c1bad4573a86a0ac03b7f 3372 
devscripts_2.23.2.dsc
 d526c10e7324f695d47161847aafbb200653073d7310fc3e4015eee68e08ced1 993948 
devscripts_2.23.2.tar.xz
 f07e3ef8192839ad990e8ee070592b6fe9008f08282313b85564514fcde6f27f 17576 
devscripts_2.23.2_source.buildinfo
Files:
 c579a7df3664e620f20c65f5122d7ac9 3372 devel optional devscripts_2.23.2.dsc
 d341590e9863f66dbe1954f02416eb3f 993948 devel optional devscripts_2.23.2.tar.xz
 6e9fce426f45fe43eb0d9430cf7b6bbb 17576 devel optional 
devscripts_2.23.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmPxaHAACgkQFZ61xO/I
d0yYARAAjQOBHM5h9FTD9UM0uOGLOVZGQJdBpKIx9M00qZuyitAbC0qPlxR3Fa5p
fzk2qVucQSra1JQjGt85UH48G6QSjNhRCffGLhsIkYtxCbN642sLTzOM7Eh07tEq
6fxSYdrQq40OMLVVUp5bKy0PqYC/IjbhznvX+C+MA1ItE3cm3l3sYMWJilzh3Hxu
CyRd68G/TMKbRksMQa7rnl6QVAbdkxH4YCcek/LZhRBDQ82s1jkexGkPDZqJmfMs
dhcT/2bvsDpgS/4twH3z5wxK4yW3Jwe/MKSHt7qygqRpX6N27gu3Dt130oigR/od
LSZlU+ky6SkRhxYdMRS+YUjBT8l0tEUqqnlNu6UL2AcrQUNf/GZoOcdGXkq01tqS
7BLkm2CSO015YDHlqHB1tSLqmt/j4V2S8fUd0qdh4PWvVNQ/D1iy9dkV26ON0I0N
w1j54Acez6IOJcnmFcGh41pyw5xxT/ukF5Q/S/EmB8CdjYHivVbjHrrtMwRI4yyd
Nvhx4FXBZigjeZ3ygYsU5433Ta8CPpoERVbNUkyOBU8m0SYxB/GQsXVhsUYBip4M
Y+A/HW6uHTTL4FaXeWKFe2q6symrqadueAKTNVJQieVPmtIK3jrsvjBYT5EQOasr
RO1PHPuqcol3DI4liythk59unYHQYFGzi520V1zZHYZAhlClpxo=
=JQAg
-END PGP SIGNATURE End Message ---

Bug#1030141: marked as done (build-rdeps man page: undocumented -q)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:35:20 +
with message-id 
and subject line Bug#1030141: fixed in devscripts 2.23.2
has caused the Debian Bug report #1030141,
regarding build-rdeps man page: undocumented -q
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1030141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: devscripts
Version: 2.22.2

The -q option is not documented in the build-rdeps(1) man page. (Only 
--quiet is.)


--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: devscripts
Source-Version: 2.23.2
Done: Benjamin Drung 

We believe that the bug you reported is fixed in the latest version of
devscripts, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1030...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated devscripts package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Feb 2023 00:56:21 +0100
Source: devscripts
Built-For-Profiles: noudeb
Architecture: source
Version: 2.23.2
Distribution: unstable
Urgency: medium
Maintainer: Devscripts Maintainers 
Changed-By: Benjamin Drung 
Closes: 1030141 1031302 1031549
Changes:
 devscripts (2.23.2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yadd ]
   * Update French translation
 .
   [ Paul Wise ]
   * wnpp-alert: Fix wnpp-alert --diff, which probably never worked
 .
   [ Benjamin Drung ]
   * Format code with black 23.1 (Closes: #1031302)
   * build-rdeps: Document -q in man page (Closes: #1030141)
   * Update translations for recent changes
 .
   [ Jakub Wilk ]
   * debchange.1: Fix uneven indentation in option list (Closes: #1031549)
Checksums-Sha1:
 a003e3b41cb1a1e1e908cc6fe74b90aacd74194e 3372 devscripts_2.23.2.dsc
 d41f943571b70bcd99cb52f15bd58b2e059c2ec2 993948 devscripts_2.23.2.tar.xz
 8a93dc96858b2b0c052f8ecf4e1e5e77f1faa0fd 17576 
devscripts_2.23.2_source.buildinfo
Checksums-Sha256:
 cb13a475d045533e3e0a2cf2291e14b3dbeda929ae5c1bad4573a86a0ac03b7f 3372 
devscripts_2.23.2.dsc
 d526c10e7324f695d47161847aafbb200653073d7310fc3e4015eee68e08ced1 993948 
devscripts_2.23.2.tar.xz
 f07e3ef8192839ad990e8ee070592b6fe9008f08282313b85564514fcde6f27f 17576 
devscripts_2.23.2_source.buildinfo
Files:
 c579a7df3664e620f20c65f5122d7ac9 3372 devel optional devscripts_2.23.2.dsc
 d341590e9863f66dbe1954f02416eb3f 993948 devel optional devscripts_2.23.2.tar.xz
 6e9fce426f45fe43eb0d9430cf7b6bbb 17576 devel optional 
devscripts_2.23.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmPxaHAACgkQFZ61xO/I
d0yYARAAjQOBHM5h9FTD9UM0uOGLOVZGQJdBpKIx9M00qZuyitAbC0qPlxR3Fa5p
fzk2qVucQSra1JQjGt85UH48G6QSjNhRCffGLhsIkYtxCbN642sLTzOM7Eh07tEq
6fxSYdrQq40OMLVVUp5bKy0PqYC/IjbhznvX+C+MA1ItE3cm3l3sYMWJilzh3Hxu
CyRd68G/TMKbRksMQa7rnl6QVAbdkxH4YCcek/LZhRBDQ82s1jkexGkPDZqJmfMs
dhcT/2bvsDpgS/4twH3z5wxK4yW3Jwe/MKSHt7qygqRpX6N27gu3Dt130oigR/od
LSZlU+ky6SkRhxYdMRS+YUjBT8l0tEUqqnlNu6UL2AcrQUNf/GZoOcdGXkq01tqS
7BLkm2CSO015YDHlqHB1tSLqmt/j4V2S8fUd0qdh4PWvVNQ/D1iy9dkV26ON0I0N
w1j54Acez6IOJcnmFcGh41pyw5xxT/ukF5Q/S/EmB8CdjYHivVbjHrrtMwRI4yyd
Nvhx4FXBZigjeZ3ygYsU5433Ta8CPpoERVbNUkyOBU8m0SYxB/GQsXVhsUYBip4M
Y+A/HW6uHTTL4FaXeWKFe2q6symrqadueAKTNVJQieVPmtIK3jrsvjBYT5EQOasr
RO1PHPuqcol3DI4liythk59unYHQYFGzi520V1zZHYZAhlClpxo=
=JQAg
-END PGP SIGNATURE End Message ---

Bug#1031583: marked as done (rust-sequoia-sq: FTBFS in testing: build-dependency not installable: librust-rpassword-5+default-dev)

[Debian Bug Tracking System]

Your message dated Sun, 19 Feb 2023 00:15:30 +
with message-id <814857f1-2f1d-620d-32a8-8c7bda0ae...@debian.org>
and subject line re: rust-sequoia-sq: FTBFS in testing: build-dependency not 
installable: librust-rpassword-5+default-dev
has caused the Debian Bug report #1031583,
regarding rust-sequoia-sq: FTBFS in testing: build-dependency not installable: 
librust-rpassword-5+default-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-sequoia-sq
Version: 0.27.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230217 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-anyhow-1+default-dev (>= 1.0.18-~~), 
> librust-buffered-reader-1+compression-bzip2-dev, 
> librust-buffered-reader-1+compression-deflate-dev, 
> librust-cfg-if-1+default-dev, librust-chrono-0.4+default-dev (>= 0.4.10-~~), 
> librust-clap-3+default-dev, librust-clap-3+derive-dev, 
> librust-clap-3+env-dev, librust-clap-3+wrap-help-dev, 
> librust-clap-complete-3+default-dev, librust-itertools-0.10+default-dev, 
> librust-rpassword-5+default-dev, librust-sequoia-autocrypt-0.24-dev, 
> librust-sequoia-net-0.25-dev, librust-sequoia-openpgp-1+compression-bzip2-dev 
> (>= 1.1-~~), librust-sequoia-openpgp-1+compression-deflate-dev (>= 1.1-~~), 
> librust-sequoia-openpgp-1+crypto-nettle-dev (>= 1.1-~~), 
> librust-sequoia-openpgp-1-dev, librust-serde-1+default-dev (>= 1.0.137-~~), 
> librust-serde-1+derive-dev (>= 1.0.137-~~), librust-serde-json-1+default-dev 
> (>= 1.0.80-~~), librust-tempfile-3+default-dev (>= 3.1-~~), 
> librust-term-size-0.3+default-dev, librust-tokio-1+default-dev (>= 
> 1.13.1-~~), bash-completion, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-anyhow-1+default-dev (>= 1.0.18-~~), 
> librust-buffered-reader-1+compression-bzip2-dev, 
> librust-buffered-reader-1+compression-deflate-dev, 
> librust-cfg-if-1+default-dev, librust-chrono-0.4+default-dev (>= 0.4.10-~~), 
> librust-clap-3+default-dev, librust-clap-3+derive-dev, 
> librust-clap-3+env-dev, librust-clap-3+wrap-help-dev, 
> librust-clap-complete-3+default-dev, librust-itertools-0.10+default-dev, 
> librust-rpassword-5+default-dev, librust-sequoia-autocrypt-0.24-dev, 
> librust-sequoia-net-0.25-dev, librust-sequoia-openpgp-1+compression-bzip2-dev 
> (>= 1.1-~~), librust-sequoia-openpgp-1+compression-deflate-dev (>= 1.1-~~), 
> librust-sequoia-openpgp-1+crypto-nettle-dev (>= 1.1-~~), 
> librust-sequoia-openpgp-1-dev, librust-serde-1+default-dev (>= 1.0.137-~~), 
> librust-serde-1+derive-dev (>= 1.0.137-~~), librust-serde-json-1+default-dev 
> (>= 1.0.80-~~), librust-tempfile-3+default-dev (>= 3.1-~~), 
> librust-term-size-0.3+default-dev, librust-tokio-1+default-dev (>= 
> 1.13.1-~~), bash-completion, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [654 B]
> Get:5 copy:/<>/apt_archive ./ Packages [741 B]
> Fetched 2358 B in 0s (161 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librust-rpassword-5+default-dev 
> but it