Bug#1012435: RM: oroborus -- RoQA; Upstream Dead; Orphaned; FTBFS; Unmaintained

[Pino Toscano]

Package: ftp.debian.org
Severity: normal
Control: block -1 by 1012421 1012433 1012434

Hi,

the oroborus source:
- had no maintainer upload in the past 11+ years, with a single NMU to
  fix the build with GCC 10
- it was recently orphaned due to the maintainer retirement
- its upstream was the Debian source itself
- a very low popcon value (19 at the time of this writing)
- plenty of alternatives ("minimalist/lightweights" WMs) exist

Hence, it looks to me it would be a better idea to simply remove
oroborus from Debian.

Thanks,
-- 
Pino

Bug#1012434: RM: keylaunch -- RoQA; Upstream Dead; Orphaned; FTBFS; Unmaintained

[Pino Toscano]

Package: ftp.debian.org
Severity: normal

Hi,

the keylaunch source:
- had no upload in the past 11+ years
- it was recently orphaned due to the maintainer retirement
- its upstream was the Debian source itself (part of the oroborus project)
- a very low popcon value (21 at the time of this writing)

Hence, it looks to me it would be a better idea to simply remove
desklaunch from Debian.

Thanks,
-- 
Pino

Bug#1012433: RM: desklaunch -- RoQA; Upstream Dead; Orphaned; FTBFS; Unmaintained

[Pino Toscano]

Package: ftp.debian.org
Severity: normal

Hi,

the desklaunch source:
- had no upload in the past 11+ years
- it was recently orphaned due to the maintainer retirement
- its upstream was the Debian source itself (part of the oroborus project)
- a very low popcon value (26 at the time of this writing)

Hence, it looks to me it would be a better idea to simply remove
desklaunch from Debian.

Thanks,
-- 
Pino

Bug#1012432: lintian: improve explanation of package-name-doesnt-match-sonames to prevent SONAME bumps without changing the package name

[Johannes Schauer Marin Rodrigues]

Source: lintian
Version: 2.114.0
Severity: normal
X-Debbugs-Cc: jo...@debian.org

Hi,

currently, the explanation of package-name-doesnt-match-sonames reads:

N:   The package name of a library package should usually reflect the soname of 
the included
N:   library. The package name can determined from the library file name with 
the following code
N:   snippet:
N:
N:$ objdump -p /path/to/libfoo-bar.so.1.2.3 | sed -n 
-e's/^[[:space:]]*SONAME[[:space:]]*//p' | \
N:sed -r -e's/([0-9])\.so\./\1-/; s/\.so(\.|$)//; y/_/-/; s/(.*)/\L&/'

I think this can be improved. Firstly, the text above talks about
"should" but policy §8.1 talks about "must":

> The run-time shared library must be placed in a package whose name changes
> whenever the SONAME of the shared library changes.

The tag explanation also misses why this is important which is also
explained by policy §8.1:

> This allows several versions of the shared library to be installed at
> the same time, allowing installation of the new version of the shared
> library without immediately breaking binaries that depend on the old
> version.

Maybe amend the explanation of the tag with text from policy, turning a
"should" into a "must" or directly reference the first paragraph of
§8.1. The use of "should" in the current explanation doesn't give much
reason why one should not override this tag.

Secondly, using this tag easily leads to mistakes when upstream *does*
bump the SONAME but if the maintainer overrode this tag will do an
upload without changed package name. This happened for example recently
in #1012407 or in #1010536.

In #debian-devel, Simon McVittie two ways to prevent this from happening
in the future. Since lintian cannot detect the intent of the developer,
I think it would make sense to extend the description of the tag to
inform the developer about the possible consequences of overriding this
tag and what they can do to prevent bugs like #1012407 or #1010536 to
happen in the future. The hope is that by giving more context in the tag
description, maintainers who want to override this tag, also will take
extra action to prevent bad uploads. Simon McVittie presented two
possible solutions:

1. override the entire lintian tag, not just the tag name

Instead of writing:

> libfooXX: package-name-doesnt-match-sonames

write (for example when overriding because of bundling):

> libfooXX: package-name-doesnt-match-sonames libbarXX libbazXX

That way, should XX change, the tag will not match anymore and the
developer would get a lintian warning. This is done for example in
src:glib2.0 d/libglib2.0-0.lintian-overrides.

2. use fully qualified names in d/*.install

Instead of writing:

> usr/lib/*/libfoo*.so.*

write:

> usr/lib/*/libfoo-XX.so.Y
> usr/lib/*/libfoo-XX.so.Y.*

That way, should the SONAME change, the wildcard would no longer match
and the maintainer would receive an error and has to investigate the
situation.

I propose the following new explanation for
package-name-doesnt-match-sonames:


N:   The run-time shared library must be placed in a package whose name changes
N:   whenever the SONAME of the shared library changes.
N:   This allows several versions of the shared library to be installed at
N:   the same time, allowing installation of the new version of the shared
N:   library without immediately breaking binaries that depend on the old
N:   version. See policy §8.1 for details.
N:
N:   If you decide to override this tag, please consider adding measures to
N:   prevent you from accidentally forgetting to change the shared library
N:   package name in case an SONAME bump happens in the future. So instead of
N:   adding an override like:
N:
N:   libfoo-bar: package-name-doesnt-match-sonames
N:
N:   override the entire lintian tag with version numbers:
N:
N:   libfoo-bar: package-name-doesnt-match-sonames libbarXX libbazXX
N:
N:   Additionally, consider explicitly adding version numbers instead of
N:   wildcards into your d/lib*.install. That way, you will get an error should
N:   the SONAME change in the future. Instead of writing:
N:
N:   usr/lib/*/libfoo*.so.*
N:
N:   write:
N:
N:   usr/lib/*/libfoo-bar.so.Y
N:   usr/lib/*/libfoo-bar.so.Y.*
N:
N:   The package name can determined from the library file name with the 
following code snippet:
N:
N:$ objdump -p /path/to/libfoo-bar.so.1.2.3 | sed -n 
-e's/^[[:space:]]*SONAME[[:space:]]*//p' | \
N:sed -r -e's/([0-9])\.so\./\1-/; s/\.so(\.|$)//; y/_/-/; s/(.*)/\L&/'


Thanks!

cheers, josch

Bug#1007717: Draft resolution for "Native source package format with non-native version"

[Helmut Grohne]

Hallo,

On Tue, May 10, 2022 at 05:29:57PM -0700, Sean Whitton wrote:
> DRAFT
> 
> Using its powers under constitution 6.1.5, the Technical Committee
> issues the following advice:

I've given this some thought and feel uneasy about one item.

>   4. We believe that there are indeed circumstances in which
>  1.0-with-diff is the best choice for a particular source package,
>  including, but not limited to, git-first packaging workflows.

While I can agree with this item on a technical level, I think there is
more to it than that and I am wondering whether it sends the "right"
message.

Sometimes, things we do are technically possible and fill a niche well.
Yet, we decide that it is no longer reasonable to continue supporting
them and remove their support despite the feature being useful to some.
Quite clearly, there is a trade-off involved here. Continuing to support
1.0-with-diff comes with a cost that reduces uniformity inside the
archive. Evidently, this is what motivated Lucas to file the MBF
initially. My experience is that lack of uniformity is a significant
barrier to prospective contributors to Debian.

Exploring different technical approaches does have value as well, but I
think we've had sufficient time to consider the various advantages and
disadvantages of various source packages formats. On a whole, it seems
to me that that the number of packages benefiting from 1.0-with-diff is
relatively small.

What would you think about adding an alternative option 4?

4b. We believe that there are indeed circumstances in which
1.0-with-diff is the best choice for a particular source package.
Given that the number of packages for which this is relevant is
fairly small, we recommend discontinuing use of 1.0-with-diff to
gain more uniformity.

Helmut

Bug#1012430: Acknowledgement (firefox-esr: Permanent certificate exceptions do not work in private windows.)

[Mad Horse]

This bug has been forwarded to mozilla as 
https://bugzilla.mozilla.org/show_bug.cgi?id=1772976 , which needs 
approval to be publicly accessible.

Bug#1012431: exim4: Exim does not deliver local mail immediately through pipe transport

[Kamil Jonca]

Package: exim4
Version: exim4-daemon-light
Severity: normal
X-Debbugs-Cc: kjo...@poczta.onet.pl

I have configured exim to deliver mail via dovecot-lda with pipe transport.

Recently I found that mails between two different local user are not delivered 
immediately but, during first deliver exim got "Resource temporarily 
unavailable"
and message is put to queue and delivered during queue run.

i.e. 
when I try:

==
echo bla|sudo -u logcheck mail kjonca
=

i got in logs:

2022-06-07 06:24:13.531 [2774788] 1nyQlJ-00Bdqe-FA <= logcheck@alfa.kjonca 
U=logcheck P=local S=436 M8S=0 RT=0.004s id*=E1nyQlJ-00Bdqe-FA@alfa.kjonca from 
 for kjonca
2022-06-07 06:24:13.551 [2774789] 1nyQlJ-00Bdqe-FA == kjonca@alfa.kjonca 
R=dovecot T=dovecot_pipe defer (0) DT=0.003s: Failed to create child process 
for dovecot_pipe transport: Resource temporarily unavailable

and message is in queue

user root have no this problem:
ie 

=
echo bla|sudo mail kjonca
=

makes immediately delivery.
How can I debug this?
KJ


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

Kernel: Linux 5.17.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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 exim4 depends on:
ii  debconf [debconf-2.0]  1.5.79
ii  exim4-base 4.95-6
ii  exim4-daemon-light 4.95-6

exim4 recommends no packages.

exim4 suggests no packages.

Bug#1012430: firefox-esr: Permanent certificate exceptions do not work in private windows.

[Mad Horse]

Package: firefox-esr
Version: 91.10.0esr-1
Severity: normal

Dear Maintainer,

Although permanent certificate exceptions cannot be added from private 
windows,
existing permanent certificate exceptions once added from normal mode 
used to
be effective in private windows under the same profile in previous 
version, but

that is not the case in the current version.

Now, even if a permanent certificate exceptions had been added for an HTTPS
site from normal mode, if one opens a private window and tries to access the
very same site with the private window, the warning for untrusted 
certificate

will be generated. To suppress the warning, they should add the same
certificate in the private window as a temporary certificate exception 
(because
only temporary certificate exceptions can be added in private windows) 
over and
over, when they access the site from a private window for the first time 
after

they launch firefox-esr.

At least, there should be an option (even in about:config) to control 
whether

existing permanent certificate exceptions are effective in private windows,
rather than rejecting them unconditionally.


-- Package-specific info:


-- Addons package information

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

Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=zh_CN.utf8, LC_CTYPE=zh_CN.utf8 (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 firefox-esr depends on:
ii debianutils 5.7-0.2
ii fontconfig 2.13.1-4.4
ii libatk1.0-0 2.38.0-1
ii libc6 2.33-7
ii libcairo-gobject2 1.16.0-5
ii libcairo2 1.16.0-5
ii libdbus-1-3 1.14.0-1
ii libdbus-glib-1-2 0.112-2
ii libevent-2.1-7 2.1.12-stable-5
ii libffi8 3.4.2-4
ii libfontconfig1 2.13.1-4.4
ii libfreetype6 2.12.1+dfsg-2
ii libgcc-s1 12.1.0-2
ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1
ii libglib2.0-0 2.72.1-1
ii libgtk-3-0 3.24.34-1
ii libnspr4 2:4.34-1
ii libnss3 2:3.79-1
ii libpango-1.0-0 1.50.7+ds-1
ii libstdc++6 12.1.0-2
ii libvpx7 1.11.0-2
ii libx11-6 2:1.7.5-1
ii libx11-xcb1 2:1.7.5-1
ii libxcb-shm0 1.14-3
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.4-1
ii libxfixes3 1:6.0.0-1
ii libxrender1 1:0.9.10-1
ii procps 2:3.3.17-7+b1
ii zlib1g 1:1.2.11.dfsg-4

Versions of packages firefox-esr recommends:
ii libavcodec57 7:3.4.3-1
ii libavcodec58 7:4.4.2-1+b1

Versions of packages firefox-esr suggests:
ii fonts-lmodern 2.005-1
ii fonts-stix [otf-stix] 1.1.1-4.1
ii libcanberra0 0.30-10
ii libgssapi-krb5-2 1.19.2-2+b1
ii pulseaudio 15.0+dfsg1-4

-- no debconf information

Bug#1012422: plasma-systemmonitor: plasma system monitor doesn't start anymore

[Adrian]

Hi Aurelien,

I've upgraded all Plasma to 5.24.90. After reboot plasma-systemmonitor 
started to work again.


Thank you!

On 06/06/2022 23:38, Aurélien COUDERC wrote:

Le 06/06/2022 à 21:44, Adrian Ban a écrit :>

Dear Maintainer,


Dear Adrian,


After upgrading the plasma-systemmonitor to version 5.24.5-1 and then to
5.24.90-2, I can't start it anymore. straces shows that is exists 
with 0.


Thank you for your bug report.

Indeed I need to tighten some dependencies to try and avoid this kind 
of situations, but from your bug report :



ii ksystemstats 5.24.5-1


you’re using an older version of ksystemstats, which is not supported. 
Upgrading it (and other Plasma packages) to 5.24.90 should fix your 
issue.


Generally speaking upstream doesn’t support mixed versions of Plasma 
components. So if you’re going the experimental / 5.25 beta route then 
you should upgrade *all* Plasma packages to 5.25 beta = 5.24.90 together.
Otherwise you will experience strange bugs that will be specific to 
your partial upgrade and won’t be of any interest to upstream.



Happy hacking !
--
Aurélien


--
Adrian Ban
Tel: +40788388190
Web: www.easynet.dev 

Bug#1012417: Fails to install; conflict with libdcmtk16: trying to overwrite '/usr/share/libdcmtk16/acrnema.dic', which is also in package libdcmtk16 3.6.6-5

[Paul Wise]

Package: libdcmtk17
Version: 3.6.7-3
Followup-For: Bug #1012417
Control: severity -1 serious
Control: retitle -1 libdcmtk17: Fails to install; conflict with libdcmtk16: 
trying to overwrite '/usr/share/libdcmtk16/acrnema.dic', which is also in 
package libdcmtk16 3.6.6-5

This bug should have been filed at severity serious, since it prevents
upgrade of packages depending on libdcmtk16 and libdcmtk17.

Here is my log from when unattended-upgrades tried to upgrade:

Package installation log:
Log started: 2022-06-07  05:51:27
apt-listchanges: Reading changelogs...
apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo
apt-listchanges: Reading changelogs...
Selecting previously unselected package libdcmtk17:amd64.
Preparing to unpack .../libdcmtk17_3.6.7-3_amd64.deb ...
Unpacking libdcmtk17:amd64 (3.6.7-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/libdcmtk17_3.6.7-3_amd64.deb (--unpack):
 trying to overwrite '/usr/share/libdcmtk16/acrnema.dic', which is also in 
package libdcmtk16 3.6.6-5
Selecting previously unselected package libopenimageio2.3:amd64.
Preparing to unpack .../libopenimageio2.3_2.3.14.0+dfsg-3+b1_amd64.deb ...
Unpacking libopenimageio2.3:amd64 (2.3.14.0+dfsg-3+b1) ...
Preparing to unpack .../blender_3.1.2+dfsg-1+b1_amd64.deb ...
Unpacking blender (3.1.2+dfsg-1+b1) over (3.1.2+dfsg-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libdcmtk17_3.6.7-3_amd64.deb

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_DIE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libdcmtk17 depends on:
ii  libc62.33-7
ii  libgcc-s112.1.0-2
ii  libpng16-16  1.6.37-5
ii  libssl3  3.0.3-6
ii  libstdc++6   12.1.0-2
ii  libtiff5 4.4.0-2
ii  libwrap0 7.6.q-31
ii  libxml2  2.9.14+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4

libdcmtk17 recommends no packages.

libdcmtk17 suggests no packages.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#1012429: O: onedrive -- folder synchronization with OneDrive

[Bastian Germann]

Package: wnpp

As noted in #988630, onedrive's maintainer Norbert Preining does not want to 
maintain
the package any longer. Therefore, this package has been orphaned.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Bug#1012428: gnome-shell-common: drmModeAddFB2WithModifiers Failed

[Tim McConnell]

Package: gnome-shell-common
Version: 42.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

What led up to the situation? Do not know, my logs are getting multiple reports
of this error(?)

What exactly did you do (or not do) that was effective (or
 ineffective)? Unknown

What was the outcome of this action?
11433 lines of:
gnome-shell[4883]: Failed to scan out client buffer: drmModeAddFB2WithModifiers
failed: Invalid argument

What outcome did you expect instead?
Not getting all of those errors in one hour



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

Kernel: Linux 5.17.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 gnome-shell-common depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3

gnome-shell-common recommends no packages.

gnome-shell-common suggests no packages.

-- no debconf information

Bug#988630: NMU: onedrive: Please update to the latest version

[Norbert Preining]

Hi Bastian,

thanks, feel free to adopt it / salvage it / whatever you feel like
doing with it.

regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1012427: file: fails to detect JSON files with many levels

[Vincent Lefevre]

Package: file
Version: 1:5.41-4
Severity: normal
Tags: upstream fixed-upstream patch
Forwarded: https://bugs.astron.com/view.php?id=327

"file" fails to detect JSON files with many levels:

$ echo '{"a":{"b":{"c":{"d":[{"e":[{"f":{"g":[{"h":0}]}}]}]' | file -
/dev/stdin: ASCII text

This has been fixed upstream by increasing the number of allowed levels:
https://github.com/file/file/commit/6511e6f45a534551b0293e82a434e3cd6504066c

I've attached the corresponding patch without the changes in the
debug messages.

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

Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.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 file depends on:
ii  libc6  2.33-7
ii  libmagic1  1:5.41-4

file recommends no packages.

file suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Index: b/src/is_json.c
===
--- a/src/is_json.c
+++ b/src/is_json.c
@@ -338,7 +338,7 @@ json_parse(const unsigned char **ucp, co
 		goto out;
 
 	// Avoid recursion
-	if (lvl > 20)
+	if (lvl > 500)
 		return 0;
 #if JSON_COUNT
 	/* bail quickly if not counting */

Bug#1012403: python3-python-flask-jwt-extended,python3-flask-jwt-extended: duplicate packages

[Emmanuel Arias]

Hi,

I cc Joseph.

Joseph, flask-jwt-extended is in Debian from some time ago
https://tracker.debian.org/pkg/python-flask-jwt-extended.

On Mon, Jun 6, 2022 at 11:15 AM Andreas Beckmann  wrote:

> Package: python3-python-flask-jwt-extended,python3-flask-jwt-extended
> Version: 4.4.0-1
> Severity: serious
>
> looks like a duplicate package was just uploaded to the archive.
>
> Andreas
>
>

Bug#1012426: file: fails to detect JSON in case of empty array with spaces

[Vincent Lefevre]

Package: file
Version: 1:5.41-4
Severity: normal
Tags: upstream patch
Forwarded: https://bugs.astron.com/view.php?id=354

When a JSON file has an empty array with spaces between the brackets,
it is misdetected as a text file:

$ echo '{"a":[ ]}' | file -
/dev/stdin: ASCII text

I've attached a patch (same fix as I've submitted upstream).

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

Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.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 file depends on:
ii  libc6  2.33-7
ii  libmagic1  1:5.41-4

file recommends no packages.

file suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Description: Fails to detect JSON in case of empty array with spaces.
Author: Vincent Lefevre 
Last-Update: 2022-06-06

diff --git a/src/is_json.c b/src/is_json.c
index c276b7be..36cccbdf 100644
--- a/src/is_json.c
+++ b/src/is_json.c
@@ -183,6 +183,7 @@ json_parse_array(const unsigned char **ucp, const unsigned char *ue,
 
 	DPRINTF("Parse array: ", uc, *ucp);
 	while (uc < ue) {
+		uc = json_skip_space(uc, ue);
 		if (*uc == ']')
 			goto done;
 		if (!json_parse(, ue, st, lvl + 1))

Bug#1012425: readline-common: Please remove dep on install-info

[Hilmar Preusse]

Package: readline-common
Version: 8.1.2-1.2
Severity: minor

Dear Maintainer,

Version in experimental is affected too, further package readline-doc.

These packages declare a dep on "install-info". However this dep should only
be needed for info viewers, as they have to care about updating the info index.
Your packages do not seem to be info viewers hence the Dep on "install-info"
is not needed. Consider to remove it.

https://wiki.debian.org/Transitions/DpkgToGnuInstallInfo

Many thanks,
  Hilmar Preuße

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

Kernel: Linux 5.17.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
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)
LSM: AppArmor: enabled

Versions of packages readline-common depends on:
ii  dpkg  1.21.8
ii  install-info  6.8-4+b1

readline-common recommends no packages.

Versions of packages readline-common suggests:
pn  readline-doc  

-- no debconf information

Bug#1012424: lilypond-doc: Please remove dep on install-info

[Hilmar Preusse]

Package: lilypond-doc
Version: 2.22.2-1
Severity: minor

Dear Maintainer,

The bug hits the following packages too, I guess they come
from the same source.

 4 lilypond-doc-html LilyPond HTML Documentation
 5 lilypond-doc-html-ca  LilyPond HTML Documentation in Catalan
 6 lilypond-doc-html-cs  LilyPond HTML Documentation in Czech
 7 lilypond-doc-html-de  LilyPond HTML Documentation in German
 8 lilypond-doc-html-es  LilyPond HTML Documentation in Spanish
 9 lilypond-doc-html-fr  LilyPond HTML Documentation in French
10 lilypond-doc-html-hu  LilyPond HTML Documentation in Hungarian
11 lilypond-doc-html-it  LilyPond HTML Documentation in Italian
12 lilypond-doc-html-ja  LilyPond HTML Documentation in Japanese
13 lilypond-doc-html-nl  LilyPond HTML Documentation in Dutch
14 lilypond-doc-html-pt  LilyPond HTML Documentation in Portuguese
15 lilypond-doc-html-zh  LilyPond HTML Documentation in Chinese
16 lilypond-doc-pdf  LilyPond PDF Documentation
17 lilypond-doc-pdf-ca   LilyPond PDF Documentation in Catalan
18 lilypond-doc-pdf-de   LilyPond PDF Documentation in German
19 lilypond-doc-pdf-es   LilyPond PDF Documentation in Spanish
20 lilypond-doc-pdf-fr   LilyPond PDF Documentation in French
21 lilypond-doc-pdf-hu   LilyPond PDF Documentation in Hungarian
22 lilypond-doc-pdf-it   LilyPond PDF Documentation in Italian
23 lilypond-doc-pdf-nl   LilyPond PDF Documentation in Dutch
24 lilypond-doc-pdf-pt   LilyPond PDF Documentation in Portuguese

These packages declare a dep on "install-info". However this dep should only
be needed for info viewers, as they have to care about updating the info index.
Your packages do not seem to be info viewers hence the Dep on "install-info"
is not needed. Consider to remove it.

https://wiki.debian.org/Transitions/DpkgToGnuInstallInfo

Many thanks,
  Hilmar Preuße

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

Kernel: Linux 5.17.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
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)
LSM: AppArmor: enabled

Versions of packages lilypond-doc depends on:
ii  install-info  6.8-4+b1

Versions of packages lilypond-doc recommends:
pn  lilypond-doc-html  
pn  lilypond-doc-pdf   

Versions of packages lilypond-doc suggests:
pn  lilypond  

Bug#1012423: RFP: glpi -- GLPI is a Free Asset and IT Management Software

[Fabio Fantoni]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: fantonifa...@tiscali.it

* Package name: glpi
  Version : 10.0.1
  Upstream Author : GLPI-project Team
* URL : https://glpi-project.org
* License : GPL-3+
  Programming Lang: PHP
  Description : GLPI is a Free Asset and IT Management Software

GLPI is a Free Asset and IT Management Software package, Data center 
management, ITIL Service Desk, licenses tracking and software auditing.

Bug#1012422: plasma-systemmonitor: plasma system monitor doesn't start anymore

[Aurélien COUDERC]

Le 06/06/2022 à 21:44, Adrian Ban a écrit :>

Dear Maintainer,


Dear Adrian,


After upgrading the plasma-systemmonitor to version 5.24.5-1 and then to
5.24.90-2, I can't start it anymore. straces shows that is exists with 0.


Thank you for your bug report.

Indeed I need to tighten some dependencies to try and avoid this kind of 
situations, but from your bug report :



ii  ksystemstats 5.24.5-1


you’re using an older version of ksystemstats, which is not supported. 
Upgrading it (and other Plasma packages) to 5.24.90 should fix your issue.


Generally speaking upstream doesn’t support mixed versions of Plasma 
components. So if you’re going the experimental / 5.25 beta route then 
you should upgrade *all* Plasma packages to 5.25 beta = 5.24.90 together.
Otherwise you will experience strange bugs that will be specific to your 
partial upgrade and won’t be of any interest to upstream.



Happy hacking !
--
Aurélien

Bug#588872: patch

[Matt Barry]

tags -1 + patch
thanks

Patch available on salsa.

Bug#1012422: plasma-systemmonitor: plasma system monitor doesn't start anymore

[Adrian Ban]

Package: plasma-systemmonitor
Version: 5.24.90-2
Severity: important

Dear Maintainer,

After upgrading the plasma-systemmonitor to version 5.24.5-1 and then to
5.24.90-2, I can't start it anymore. straces shows that is exists with 0.

statx(AT_FDCWD,
"/home/adrian/.local/share/flatpak/exports/share/icons/hicolor/symbolic/apps",
AT_STATX_SYNC_AS_STAT, STATX_ALL, {stx_mask=STATX_ALL|STATX_MNT_ID,
stx_attributes=0, stx_mode=S_IFDIR|0755, stx_size=4096, ...}) = 0
statx(AT_FDCWD, "/var/lib/flatpak/exports/share/icons/hicolor/symbolic/apps",
AT_STATX_SYNC_AS_STAT, STATX_ALL, {stx_mask=STATX_ALL|STATX_MNT_ID,
stx_attributes=0, stx_mode=S_IFDIR|0755, stx_size=4096, ...}) = 0
statx(AT_FDCWD, "/usr/share/icons/hicolor/symbolic/apps",
AT_STATX_SYNC_AS_STAT, STATX_ALL, {stx_mask=STATX_ALL|STATX_MNT_ID,
stx_attributes=0, stx_mode=S_IFDIR|0755, stx_size=4096, ...}) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(7, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7ffd541a53c0, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
write(7, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x561f95668b90, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY) = 0
futex(0x561f95668b40, FUTEX_WAKE_PRIVATE, 1) = 0
write(7, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f2f55be2880, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7ffd541a53e0, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
write(7, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x561f9563ce90, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY) = 0
futex(0x561f9563ce40, FUTEX_WAKE_PRIVATE, 1) = 0
write(7, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x561f95640a20, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY) = 0
futex(0x561f956409d0, FUTEX_WAKE_PRIVATE, 1) = 0
msync(0x7f2f4988d000, 10547304, MS_ASYNC|MS_INVALIDATE) = 0
munmap(0x7f2f4988d000, 10547304)= 0
write(7, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7ffd541a5530, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
write(7, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x561f955dc6a8, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x561f955d3a70, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY) = 0
futex(0x561f955d3a20, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f2f4b14e040, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f2f4b123070, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getpid()= 456284
exit_group(0)   = ?
+++ exited with 0 +++


*** 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 testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 5.17.0-1-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:ro
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-systemmonitor depends on:
ii  ksystemstats 5.24.5-1
ii  libc62.33-7
ii  libkf5configcore55.94.0-3
ii  libkf5configgui5 5.94.0-3
ii  libkf5coreaddons55.94.0-1
ii  libkf5dbusaddons55.94.0-1
ii  libkf5globalaccel-bin5.94.0-1
ii  libkf5globalaccel5   5.94.0-1
ii  libkf5i18n5  5.94.0-1
ii  libkf5itemmodels55.94.0-1
ii  libkf5kiogui55.94.0-1
ii  libkf5newstuffcore5  5.94.0-2
ii  libkf5service-bin5.94.0-1
ii  libkf5service5   5.94.0-1
ii  libkf5windowsystem5  5.94.0-1
ii  libksysguardsensorfaces1 4:5.24.90-1
ii  libqt5core5a 5.15.2+dfsg-16+b1
ii  libqt5dbus5  5.15.2+dfsg-16+b1
ii  libqt5gui5   5.15.2+dfsg-16+b1
ii  libqt5qml5   5.15.2+dfsg-10
ii  libqt5widgets5   5.15.2+dfsg-16+b1
ii  libstdc++6   12.1.0-2
ii  qml-module-org-kde-kcm   5.94.0-1
ii  qml-module-org-kde-kcoreaddons   5.94.0-1
ii  qml-module-org-kde-kirigami2 5.94.0-1
ii  qml-module-org-kde-kitemmodels   5.94.0-1
ii  qml-module-org-kde-kquickcontrolsaddons  5.94.0-1
ii  qml-module-org-kde-ksysguard 4:5.24.5-1
ii  qml-module-org-kde-newstuff 

Bug#1012421: RM: deskmenu -- RoQA; Upstream Dead; Orphaned; FTBFS; Unmaintained

[Boyuan Yang]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove

Dear FTP Masters,

Package deskmenu ( https://tracker.debian.org/pkg/deskmenu ) saw no upload
in the past 12 years, was orphaned due to maintainer retirement, and has a
dead upstream with defunct homepage. It also has a low popcon value (41). As
a result, I believe this package is eligible for removal from Debian Sid.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#1012420: no_del_paths includes /srv?

[Matt Barry]

Package: adduser
Severity: wishlist

AIUI /srv is under the purview of the sysadmin; if they decide to set
DHOME somewhere under /srv, shouldn't this behave the same as with
/home?

Cheers,
Matt


signature.asc
Description: This is a digitally signed message part

Bug#1012419: name of shared lib package did not follow SOVERSION bump, which causes breakages

[Pierre Gruet]

Source: ceres-solver
Version: 2.1.0+dfsg1-1
Severity: important

Dear Maintainer,

Recently version 2.1.0+dfsg-1 entered unstable, with new upstream version
2.1.0. Yet, there was a SOVERSION bump in this new upstream version, as can be
seen in internal/ceres/CMakeLists.txt (SOVERSION 3, was 2 previously).

The shared lib package should have been renamed to libceres3 and should have
gone to experimental through NEW in order to make a proper transition. The
current situation causes breakages, for instance with openturns and sight which
are reverse dependencies of ceres-solver and desperately look for libceres.so.2
at runtime.

I think we should repackage upstream version 2.0.0 with the version number
2.1.0+really2.0.0+dfsg-1 so that we avoid breakages in unstable and testing,
and afterwards we could package version 2.1.0 again, bump the soname and send
the package to experimental to properly transition the library.

Sorry I did not spot this when I reviewed the package before its last upload!

Best,

-- 
Pierre

Bug#1012418: librust-zbus-dev: Broken with nix 0.24.1

[Dorota Czaplejewicz]

Filling in the gaps.

On Mon, 06 Jun 2022 18:23:39 +
dcz  wrote:

> Package: librust-zbus-dev
> Version: 1.9.2-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 

zbus is broken since a couple days: 
https://gitlab.gnome.org/World/Phosh/squeekboard/-/jobs/2047130

in particular, it tries to call into nix::sendmsg, but it seems sendmsg 
parameters have changed:

   Compiling zbus v1.9.2
error[E0308]: mismatched types
  --> /usr/share/cargo/registry/zbus-1.9.2/src/raw/socket.rs:70:13
   |
70 | ,
   |  types differ in mutability
   |
   = note: expected mutable reference ` [IoSliceMut<'_>]`
  found reference `&[IoVec< [u8]>; 1]`
error[E0308]: mismatched types
  --> /usr/share/cargo/registry/zbus-1.9.2/src/raw/socket.rs:99:41
   |
99 | match sendmsg(self.as_raw_fd(), , , MsgFlags::empty(), 
None) {
   |  expected slice, found array 
of 1 element
   |
   = note: expected reference `&[IoSlice<'_>]`
  found reference `&[IoVec<&[u8]>; 1]`
For more information about this error, try `rustc --explain E0308`.
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.17.5-200.fc35.x86_64 (SMP w/2 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_WARN
> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /bin/dash
> Init: unable to detect
> 
> Versions of packages librust-zbus-dev depends on:
> pn  librust-async-io-1+default-dev 
> pn  librust-byteorder-1+default-dev
> pn  librust-derivative-2+default-dev   
> pn  librust-enumflags2-0.6+default-dev 
> pn  librust-enumflags2-0.6+serde-dev   
> pn  librust-fastrand-1+default-dev 
> pn  librust-futures-0.3+default-dev
> pn  librust-nb-connect-1+default-dev   
> pn  librust-nix+default-dev
> pn  librust-once-cell-1+default-dev
> pn  librust-polling-2+default-dev  
> pn  librust-scoped-tls-1+default-dev   
> pn  librust-serde-1+default-dev
> pn  librust-serde-1+derive-dev 
> pn  librust-serde-repr-0.1+default-dev 
> pn  librust-serde-xml-rs-0.4+default-dev   
> pn  librust-zbus-macros-1.9.2+default-dev  
> pn  librust-zvariant-2+enumflags2-dev  
> 
> librust-zbus-dev recommends no packages.
> 
> librust-zbus-dev suggests no packages.



pgpQllookE3CQ.pgp
Description: OpenPGP digital signature

Bug#1012362: transition: luajit

[Paul Gevers]

Control: tag -1 confirmed
Control: forwarded -1 
https://release.debian.org/transitions/html/libluajit2-support.html

Hi Mo,

On 05-06-2022 19:30, M. Zhou wrote:

So, currently I have a pending commit[2] modifying the dependency template[1],
so that src:luajit reverse dependencies can be rebuilt without source
modification to allow library fallback.

Specifically, before transition, luajit reverse dependencies will have:
   Depends: libluajit-5.1-2
After transition, they should have:
   Depends: libluajit-5.1-2 | libluajit2-5.1-2
And the only thing we need to do is to upload the pending commit[2]
once approved. Then we just trigger a rebuild for all luajit reverse
dependencies.


Please go ahead.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009733: src:exempi: fails to migrate to testing for too long: FTBFS on armel and armhf

[Paul Gevers]

Hi Bernhard,

On 06-06-2022 18:47, Bernhard Übelacker wrote:

Am 06.06.22 um 18:43 schrieb Bernhard Übelacker:

I came here due to the recent message to debian-arm.
Still unsure because this bug is already closed?


Yeah, sorry about that. I file those "fails to migrate for too long 
bugs" most often against the version in testing, hence I close it 
immediately. With FTBFS bugs I'm unsure what my default should be.



Forgot to mention the merge request with the actual change:
https://salsa.debian.org/bernhardu-guest/exempi/-/merge_requests/1


It looks like that archive is private and thus can't bee seen. Also, I'd 
hope/expect the merge_request would be against the s.d.o/debian/exempi 
archive.


Thanks for taking the time to look into the issue, much appreciated.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012418: librust-zbus-dev: Broken with nix 0.24.1

[dcz]

Package: librust-zbus-dev
Version: 1.9.2-1
Severity: grave
Justification: renders package unusable

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')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.5-200.fc35.x86_64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages librust-zbus-dev depends on:
pn  librust-async-io-1+default-dev 
pn  librust-byteorder-1+default-dev
pn  librust-derivative-2+default-dev   
pn  librust-enumflags2-0.6+default-dev 
pn  librust-enumflags2-0.6+serde-dev   
pn  librust-fastrand-1+default-dev 
pn  librust-futures-0.3+default-dev
pn  librust-nb-connect-1+default-dev   
pn  librust-nix+default-dev
pn  librust-once-cell-1+default-dev
pn  librust-polling-2+default-dev  
pn  librust-scoped-tls-1+default-dev   
pn  librust-serde-1+default-dev
pn  librust-serde-1+derive-dev 
pn  librust-serde-repr-0.1+default-dev 
pn  librust-serde-xml-rs-0.4+default-dev   
pn  librust-zbus-macros-1.9.2+default-dev  
pn  librust-zvariant-2+enumflags2-dev  

librust-zbus-dev recommends no packages.

librust-zbus-dev suggests no packages.

Bug#898949: schroot: PAM config should use common-session-noninteractive

[Christoph Biedl]

Control: tags 898949 pending

Ansgar Burchardt wrote...

> The /etc/pam.d/schroot included in the package uses
> 
>   @include common-session
> 
> Please use
> 
>   @include common-session-noninteractive
> 
> instead as cron, at, ... already do.

Well, Ubuntu this this change a few months ago, and this didn't seem to
create significant damage. Let's give it a spin for 1.6.10-14

Christoph


signature.asc
Description: PGP signature

Bug#1012416: biosig: FTBFS: accovf_mex.cpp:44:26: error: pragma or attribute ‘target("avx2")’ is not valid

[Sebastian Ramacher]

Source: biosig
Version: 2.4.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=biosig=arm64=2.4.0-1=1654526631=0

accovf_mex.cpp:44:26: error: pragma or attribute ‘target("avx2")’ is not valid
   44 | #pragma GCC target("avx2")
  |  ^
g++ -I/usr/include/octave-7.1.0/octave/.. -I/usr/include/octave-7.1.0/octave  
-pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g  -o 
physicalunits.mex  /tmp/oct-HoFmCA.o   -L.. -lbiosig -shared -Wl,-Bsymbolic 
-Wl,-z,relro -Wl,-z,now -shared  -L/usr/lib/aarch64-linux-gnu -shared 
-Wl,-Bsymbolic  -Wl,-z,relro 
/usr/bin/mkoctfile  -I.. -v -g --mex "mexSOPEN.cpp" -L.. -lbiosig -o 
"mexSOPEN.mex"
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/octave-7.1.0/octave/.. -I/usr/include/octave-7.1.0/octave  
-pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g   -I.. -I.  
-DMEX_DEBUG mexSOPEN.cpp -o /tmp/oct-QNax32.o
make[3]: *** [Makefile:203: accovf_mex.mex] Error 1
make[3]: *** Waiting for unfinished jobs

Cheers
-- 
Sebastian Ramacher

Bug#1012417: Fails to install; conflict with libdcmtk16

[Jörg Sommer]

Package: libdcmtk17
Version: 3.6.7-2
Severity: normal

Hi,

```
% apt upgrade
…
Preparing to unpack .../libdcmtk17_3.6.7-2_amd64.deb ...
Unpacking libdcmtk17:amd64 (3.6.7-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/libdcmtk17_3.6.7-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libdcmdata.so.17.3.6.7', which 
is also in package libdcmtk16:amd64 3.6.7-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libdcmtk17_3.6.7-2_amd64.deb
```

Regards Jörg

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

Kernel: Linux 5.18.0-trunk-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 libdcmtk17 depends on:
ii  libc62.33-7
ii  libgcc-s112.1.0-2
ii  libpng16-16  1.6.37-5
ii  libssl1.11.1.1o-1
ii  libstdc++6   12.1.0-2
ii  libtiff5 4.4.0-2
ii  libwrap0 7.6.q-31
ii  libxml2  2.9.14+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4

libdcmtk17 recommends no packages.

libdcmtk17 suggests no packages.


signature.asc
Description: PGP signature

Bug#965348: schroot: [INTL:pt] Initial Portuguese translation of manpage

[Christoph Biedl]

Control: tags 965348 pending

Américo Monteiro wrote...

> version 1.6.10-13 of manpage updated

Obrigado, applied.

Christoph


signature.asc
Description: PGP signature

Bug#1006511: net-snmp: FTBFS with OpenSSL 3.0

[Sergio Durigan Junior]

On Sunday, May 15 2022, Craig Small wrote:

> Upstream should have a new version of net-snmp that compiles with
> OpenSSL v3.0 in May.  I've tested the RC1 release and it compiles
> fine.
>
> https://sourceforge.net/p/net-snmp/mailman/message/37642006/

FWIW, Ubuntu's net-snmp has been using the following two patches
(backported from upstream) in order to fix the FTBFS with openssl 3.0:

https://git.launchpad.net/ubuntu/+source/net-snmp/tree/debian/patches/lp1945960-Fix-the-build-against-OpenSSL-3.0.patch

https://git.launchpad.net/ubuntu/+source/net-snmp/tree/debian/patches/lp1945960-configure-static-linking-Fix-SSL-checks.patch

If you'd like I can submit an MR/debdiff with these backports for Debian
as well.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#516285: pending

[matt]

tags -1 pending
thanks

Bug#1012410: gnome-shell: warnings about needing an allocation

[Tim McConnell]

Package: gnome-shell
Version: 42.1-1
Severity: important
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

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

What led up to the situation? Don't know actually, maybe a system upgrade?

What exactly did you do (or not do) that was effective (or
 ineffective)?Unsure

What was the outcome of this action? Received these lines in my log files:
Jun  6 10:34:22 DebianTim gnome-shell[4883]: Can't update stage views actor
[:0x55ef4ff7a1b0] is on because it needs
an allocation.
Jun  6 10:34:22 DebianTim gnome-shell[4883]: Can't update stage views actor
[:0x55ef4ff7ba40] is on because it needs an allocation.
Jun  6 10:34:22 DebianTim gnome-shell[4883]: Can't update stage views actor
[:0x55ef50857990] is on because it needs an allocation.
Jun  6 10:34:22 DebianTim gnome-shell[4883]: Can't update stage views actor
[:0x55ef503cfa70] is on because it needs an allocation.
Jun  6 10:34:22 DebianTim gnome-shell[4883]: Can't update stage views actor
[:0x55ef503d0570] is on because it needs an allocation.
Jun  6 10:34:22 DebianTim gnome-shell[4883]: Can't update stage views actor
[:0x55ef5048d500] is on because it needs an allocation.
Jun  6 10:34:22 DebianTim gnome-shell[4883]: Can't update stage views actor
[:0x55ef508a5380] is on because it needs an allocation.

What outcome did you expect instead? None of these warnings

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


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

Kernel: Linux 5.17.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  gir1.2-accountsservice-1.0   22.08.8-1
ii  gir1.2-adw-1 1.1.1-1
ii  gir1.2-atk-1.0   2.38.0-1
ii  gir1.2-atspi-2.0 2.44.1-1
ii  gir1.2-freedesktop   1.72.0-1+b1
ii  gir1.2-gcr-3 3.41.0-4
ii  gir1.2-gdesktopenums-3.0 42.0-1
ii  gir1.2-gdkpixbuf-2.0 2.42.8+dfsg-1
ii  gir1.2-gdm-1.0   42.0-1
ii  gir1.2-geoclue-2.0   2.6.0-1
ii  gir1.2-glib-2.0  1.72.0-1+b1
ii  gir1.2-gnomebluetooth-3.042.0-5
ii  gir1.2-gnomedesktop-3.0  42.1-1
ii  gir1.2-graphene-1.0  1.10.8-1
ii  gir1.2-gstreamer-1.0 1.20.2-1
ii  gir1.2-gtk-3.0   3.24.34-1
ii  gir1.2-gtk-4.0   4.6.5+ds-1
ii  gir1.2-gweather-4.0  4.0.0-2
ii  gir1.2-ibus-1.0  1.5.26-4
ii  gir1.2-mutter-10 42.2-1
ii  gir1.2-nm-1.01.38.0-2
ii  gir1.2-nma-1.0   1.8.38-1
ii  gir1.2-pango-1.0 1.50.7+ds-1
ii  gir1.2-polkit-1.00.105-33
ii  gir1.2-rsvg-2.0  2.54.3+dfsg-1
ii  gir1.2-soup-2.4  2.74.2-3
ii  gir1.2-upowerglib-1.00.99.18-3
ii  gir1.2-webkit2-4.0   2.36.3-1
ii  gnome-backgrounds42.0-1
ii  gnome-settings-daemon42.2-1
ii  gnome-shell-common   42.1-1
ii  gsettings-desktop-schemas42.0-1
ii  gstreamer1.0-pipewire0.3.51-1
ii  libatk-bridge2.0-0   2.38.0-4
ii  libatk1.0-0  2.38.0-1
ii  libc62.33-7
ii  libcairo21.16.0-5
ii  libecal-2.0-13.44.2-1
ii  libedataserver-1.2-263.44.2-1
ii  libgcr-base-3-1  3.41.0-4
ii  libgdk-pixbuf-2.0-0  2.42.8+dfsg-1
ii  libgirepository-1.0-11.72.0-1+b1
ii  libgjs0g 1.72.0-2
ii  libgles2 1.4.0-1
ii  libglib2.0-0 2.72.1-1
ii  libglib2.0-bin   2.72.1-1
ii  libgnome-autoar-0-0  0.4.3-1
ii  libgnome-desktop-3-1942.1-1
ii  libgraphene-1.0-01.10.8-1
ii  libgtk-3-0   3.24.34-1
ii  libgtk-4-1   4.6.5+ds-1
ii  libical3

Bug#1012409: vlc: No sound when playing mp3 audio file from vlc. With Totem this is not the case

[riquet607]

Package: vlc
Version: 3.0.17.4-2+b1
Severity: important

Dear Maintainer,

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

   * What led up to the situation? upgrade bullseye to testing release
bookworm/sid

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


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

Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 vlc depends on:
ii  vlc-bin  3.0.17.4-2+b1
ii  vlc-plugin-base  3.0.17.4-2+b1
ii  vlc-plugin-qt3.0.17.4-2+b1
ii  vlc-plugin-video-output  3.0.17.4-2+b1

Versions of packages vlc recommends:
ii  vlc-l10n   3.0.17.4-2
ii  vlc-plugin-access-extra3.0.17.4-2+b1
ii  vlc-plugin-notify  3.0.17.4-2+b1
ii  vlc-plugin-pipewire3-1
ii  vlc-plugin-samba   3.0.17.4-2+b1
ii  vlc-plugin-skins2  3.0.17.4-2+b1
ii  vlc-plugin-video-splitter  3.0.17.4-2+b1
ii  vlc-plugin-visualization   3.0.17.4-2+b1

Versions of packages vlc suggests:
pn  vlc-plugin-fluidsynth  
pn  vlc-plugin-jack
pn  vlc-plugin-svg 

Versions of packages libvlc-bin depends on:
ii  libc62.34-0experimental4
ii  libvlc5  3.0.17.4-2+b1

Versions of packages libvlc5 depends on:
ii  libc62.34-0experimental4
ii  libvlccore9  3.0.17.4-2+b1

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.17.4-2+b1

Versions of packages vlc-bin depends on:
ii  libc6   2.34-0experimental4
ii  libvlc-bin  3.0.17.4-2+b1
ii  libvlc5 3.0.17.4-2+b1

Versions of packages vlc-plugin-access-extra depends on:
ii  libc62.34-0experimental4
ii  libsrt1.4-gnutls 1.4.4-4
ii  libvlccore9 [vlc-plugin-abi-3-0-0f]  3.0.17.4-2+b1
ii  libvncclient10.9.13+dfsg-4
ii  libxcb-composite01.14-3
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4 0.7.4-20
ii  libarchive13 3.6.0-1
ii  libaribb24-0 1.0.3-2
ii  libasound2   1.2.6.1-2+b1
ii  libass9  1:0.16.0-1
ii  libavahi-client3 0.8-5
ii  libavahi-common3 0.8-5
ii  libavc1394-0 0.5.4-5
ii  libavcodec58 7:4.4.2-1+b1
ii  libavformat587:4.4.2-1+b1
ii  libavutil56  7:4.4.2-1+b1
ii  libbluray2   1:1.3.1-2
ii  libc62.34-0experimental4
ii  libcairo21.16.0-5
ii  libcddb2 1.3.2-7
ii  libchromaprint1  1.5.1-2
ii  libdav1d61.0.0-2
ii  libdbus-1-3  1.14.0-1
ii  libdc1394-25 2.2.6-4
ii  libdca0  0.0.7-2
ii  libdvbpsi10  1.3.3-1
ii  libdvdnav4   6.1.1-1
ii  libdvdread8  6.1.2-1
ii  libebml5 1.4.2-2
ii  libfaad2 2.10.0-2
ii  libflac8 1.3.4-1
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.12.1+dfsg-2
ii  libfribidi0  1.0.8-2.1
ii  libgcc-s112.1.0-2
ii  libgcrypt20  1.10.1-2
ii  libglib2.0-0 2.72.1-1
ii  libgnutls30  3.7.4-2
ii  libgpg-error01.45-2
ii  libharfbuzz0b2.7.4-1+b1
ii  libixml101:1.8.4-2
ii  libjpeg62-turbo  1:2.1.2-1
ii  libkate1 0.4.1-11
ii  liblirc-client0  0.10.1-7
ii  liblua5.2-0  5.2.4-2
ii  libmad0  0.15.1b-10
ii  libmatroska7 1.6.3-2
ii  libmpcdec6   2:0.1~r495-2
ii  libmpeg2-4   0.5.1-9
ii  libmpg123-0  1.29.3-1
ii  libmtp9  1.1.19-1
ii  libncursesw6 6.3+20220423-2
ii  libnfs13 4.0.0-1
ii  libogg0  1.3.4-0.1
ii  libopenmpt-modplug1  0.8.9.0-openmpt1-2
ii  libopus0 1.3.1-0.1
ii  libpng16-16

Bug#983349: sane-escl: cannot open device when ipp-usb is running

[Jörg Frings-Fürst]

Hello,


no answer since more then three months.

So I close this bug.


CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



signature.asc
Description: This is a digitally signed message part

Bug#998656: sane-avision: adds a blank a4 page at the bottom of the scan

[Jörg Frings-Fürst]

fixed 998656 1.0.32-1
tags 998656 - moreinfo
thanks

Hello,


no answer since more then three months.

So I close this bug.


CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



signature.asc
Description: This is a digitally signed message part

Bug#1012166: ITP: haskell-tzdata -- Haskell package that distributes the standard time zone database

[Philipp Kern]

Hi,

On 31.05.22 10:14, Robert Greener wrote:

The goal of this package is to distribute the standard Time Zone Database in a 
cabal package, so that it can be used in Haskell programs uniformly on all 
platforms.

This package currently ships the 2022a version of the time zone database. The 
version of the time zone database shipped is always reflected in the version of 
this package: x.y.MMDD.z, then MMDD is the official release date of 
time zone database.
I'm not sure further proliferation of this data that needs updating 
frequently is helpful. Is there any way this data could instead be read 
from disk - i.e. the from the existing tzdata package?


This would add up to the load of all the various packages of various 
languages that already need updating with every tzdata release.


Kind regards
Philipp Kern

Bug#1012408: ITP: mathjax-siunitx -- Extension for libjs-mathjax to suppourt siunitx

[Georges Khaznadar]

Package: wnpp
Severity: wishlist
Owner: Georges Khaznadar 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: mathjax-siunitx
  Version : 0.1
  Upstream Author : Yves Delley  
* URL : https://github.com/burnpanck/MathJax-siunitx
* License : Apache-2
  Programming Lang: Javascript
  Description : Extension for libjs-mathjax to support siunitx

 The siunitx package allows to typeset physical quantities consistently
 using the syntax \SI{299e6}{\metre\per\second}. This extension provides
 the same syntax in MathJax. Please see the documentation for siunitx
 on CTAN for details about siunitx.
 .
 MathJax was designed with the goal of consolidating the recent advances in web
 technologies into a single, definitive, math-on-the-web platform supporting
 the major browsers and operating systems.

I need this javascript package as an engine to embed in a future web
service, allowing teachers to share free-libre documents. As some of them
require formula rendering, and some of them teach physics, MathJax is
not enough if one wants to take in account properly physical quantities.
Hence this extension.

Bug#1012405: guix: Guix command uses less but less does not exist in dependent software

[Taiju HIGASHI]

Hi,

Perhaps I should have done a little more research before submitting.

>From reading the source code, I see that it does not necessarily have to
be less.
However, some sort of pager program is required. [0]

I'm not familiar with Debian packages, but is there a mechanism for
presenting to the user in advance that a pager program is needed?

0: 
https://git.savannah.gnu.org/cgit/guix.git/tree/guix/ui.scm?id=e71f35df74f970a93e0b178fc5a294781b3a#n1677

Thanks,
-- 
Taiju

Bug#1011282: device-tree-compiler: provide pylibfdt

[Bastian Germann]

Control: tags -1 patch
Control: tags 877125 patch

On Thu, 19 May 2022 08:49:27 -0700 Vagrant Cascadian  wrote:

I've tried several times, but always get stuck with:

  https://bugs.debian.org/877125

There was a hint at a proposed path forward ~2019, but I wasn't able to
get it to work...

Would be happy to see this fixed as well!


Please find a patch attached that depends on #877125's 
0001-Enable-pylibfdt-build-Closes-877125.patch.
Both patches applied should make the build work.From cedf1902e0e845fdd273e052ad4137e0ce02f82c Mon Sep 17 00:00:00 2001
From: Bastian Germann 
Date: Mon, 6 Jun 2022 16:23:10 +0200
Subject: [PATCH] Create bin pkg python3-libfdt (Closes: #1011282)

Installing pylibfdt as python3-libfdt without pybuild needs adding some
setuptools install flags that cannot be passed to the install call without
an additional patch.
---
 debian/control| 11 +++
 debian/not-installed  |  1 +
 .../patches/04_Install_to_dist_packages.patch | 19 +++
 debian/patches/series |  1 +
 debian/python3-libfdt.install |  2 ++
 debian/rules  |  2 +-
 6 files changed, 35 insertions(+), 1 deletion(-)
 create mode 100644 debian/not-installed
 create mode 100644 debian/patches/04_Install_to_dist_packages.patch
 create mode 100644 debian/python3-libfdt.install

diff --git a/debian/control b/debian/control
index f82e53c..b366d16 100644
--- a/debian/control
+++ b/debian/control
@@ -5,6 +5,7 @@ Maintainer: Héctor Orón Martínez 
 Uploaders: Riku Voipio , Vagrant Cascadian 
 Standards-Version: 4.6.0
 Build-Depends: debhelper-compat (= 13),
+ dh-python,
  flex,
  bison,
  libyaml-dev,
@@ -50,3 +51,13 @@ Description: Flat Device Trees manipulation library - development files
  This is a library containing functions for manipulating Flat Device Trees.
  .
  This package contains the files needed for development against libfdt.
+
+Package: python3-libfdt
+Architecture: any
+Section: python
+Depends: ${python3:Depends}, ${shlibs:Depends}, ${misc:Depends}
+Provides: ${python3:Provides}
+Description: Flat Device Trees manipulation library - Python bindings
+ This is a library containing functions for manipulating Flat Device Trees.
+ .
+ This package contains the files needed for Python development with libfdt.
diff --git a/debian/not-installed b/debian/not-installed
new file mode 100644
index 000..b54b0c7
--- /dev/null
+++ b/debian/not-installed
@@ -0,0 +1 @@
+usr/lib/python3/dist-packages/__pycache__
diff --git a/debian/patches/04_Install_to_dist_packages.patch b/debian/patches/04_Install_to_dist_packages.patch
new file mode 100644
index 000..9c8abac
--- /dev/null
+++ b/debian/patches/04_Install_to_dist_packages.patch
@@ -0,0 +1,19 @@
+From: Bastian Germann 
+Date: Fri, 20 May 2022 19:00:00 +0200
+Subject: pylibfdt: Install to dist-packages
+
+Signed-off-by: Bastian Germann 
+---
+diff --git a/pylibfdt/Makefile.pylibfdt b/pylibfdt/Makefile.pylibfdt
+index b1c80af..deb3f91 100644
+--- a/pylibfdt/Makefile.pylibfdt
 b/pylibfdt/Makefile.pylibfdt
+@@ -21,7 +21,7 @@ $(PYMODULE): $(PYLIBFDT_srcs) $(LIBFDT_archive) $(SETUP) $(VERSION_FILE)
+ 
+ install_pylibfdt: $(PYMODULE)
+ 	@$(VECHO) INSTALL-PYLIB
+-	$(PYTHON) $(SETUP) $(SETUPFLAGS) install --prefix=$(PREFIX)
++	$(PYTHON) $(SETUP) $(SETUPFLAGS) install --prefix=$(PREFIX) --root=/ --install-lib=$(PREFIX)/lib/python3/dist-packages --install-layout=deb --single-version-externally-managed
+ 
+ pylibfdt_clean:
+ 	@$(VECHO) CLEAN "(pylibfdt)"
diff --git a/debian/patches/series b/debian/patches/series
index 3b4e70f..f384023 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 01_build_doc.patch
 02_Move_setup.py_to_the_top_level.patch
 03_fix_with_Python_3.10.patch
+04_Install_to_dist_packages.patch
diff --git a/debian/python3-libfdt.install b/debian/python3-libfdt.install
new file mode 100644
index 000..a2166f4
--- /dev/null
+++ b/debian/python3-libfdt.install
@@ -0,0 +1,2 @@
+usr/lib/python3/dist-packages/_libfdt*
+usr/lib/python3/dist-packages/libfdt*
diff --git a/debian/rules b/debian/rules
index 01a4155..968d0ca 100755
--- a/debian/rules
+++ b/debian/rules
@@ -18,7 +18,7 @@ EXTRA_CFLAGS = -Wno-error
 CPPFLAGS += -I libfdt -I .
 
 %:
-	dh $@
+	dh $@ --with python3
 
 override_dh_auto_build:
 	dh_auto_build -- V=1 EXTRA_CFLAGS="$(EXTRA_CFLAGS)" CPPFLAGS="$(CPPFLAGS)"

Bug#988630: onedrive: Please update to the latest version

[Bastian Germann]

Hi Norbert,

Are you saying you consider this to be orphaned?

Thanks,
Bastian

Bug#1000922: Please switch to llvm-toolchain 13

[Sylvestre Ledru]

Control: severity -1 serious

This package is one of the the last standing in the way of removing
llvm-toolchain-11. Bumping severity.

Sylvestre

Bug#1012407: libsingular4m2n1: changes SONAME without changing package name

[David Bremner]

Package: libsingular4m2n1
Version: 1:4.3.0-p1+ds-2
Severity: serious
Justification: violates policy MUST: section 8.1, first paragraph

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Version 4.3.0 of libsingular4m2n1 has an SONAME of 

libsingular-Singular-4.3.0.so

Version 4.2.1 has SONAME

libsingular-Singular-4.2.1.so

This means the package name has to change, otherwise packages built
against 4.2.1 will break on systems with 4.3.0 installed.

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

Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libsingular4m2n1 depends on:
ii  libc6   2.33-7
ii  libflint-2.8.5  2.8.5-2
ii  libgmp102:6.2.1+dfsg-3
ii  libmpfr64.1.0-3
ii  libntl4411.5.1-1+b1
ii  libreadline88.1.2-1.2
ii  libstdc++6  12.1.0-2

libsingular4m2n1 recommends no packages.

libsingular4m2n1 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmKeDmMACgkQA0U5G1Wq
FSGHzw//UV7FGyvisGdYJaHpl+OVZyvQ/lPrWZyelFM2U94o8hB+E4Mi6ZKvxX7/
jJ1G7U8yR5GSgkAmzNwrUTL2rO+F0db/qnQV7i5IgTOmtCOrSoDUKvf08daTTUMl
5/Fe1y7VrESL6aFljigYLf2HuO+uoXqQRmIP8hmr7Io4N4s01ipBojrQ1Kuj10PP
VaRi3hPX/FzkVk6exA6W8sVxh36mMu1S6tAy9kWjpF3asnmy7dks/byjBwei88rL
RKHVle59pjGghY3LscEesgHV05EiH1AFsc7h5XWpxKqaNpUtgunz0KSEsX3iAVqK
jg76WErZAgzmclXsGPqgtdtxUYs7qa28Yf51X2PUhsYNpcXhr7lsOn+VT0GxXIEm
Hp3T9QzNwXl51hXqy11ajPn2uZENUXF66UxAuxbTqbmuyxg8uCPg6s4i1UeLcYUI
HDT38SVBj44dHdO8DrzrLTuCxxHx0cUKqX7Jq/Ie/1++JRkEUFyVr6Ls60szhKKs
XPYLeRAZMtxk9Rg1Vbbsqnn7GAiq8C9OeiCgpBFGbXo9m2gMZkjrHOQjexT12vVw
5/my1wm3jpx8eGoJ+Trkz61aFqU0ohG+PWH0lwGnrkBahogdFMWkL6SKfS5r1bfO
c7mJ7FIjO0Sxtu/HQ3KUaOhLv0jxw1bENV3gfPFyid37Xo1eetg=
=IVAe
-END PGP SIGNATURE-

Bug#1012406: RM: libclc -- ROM; Merged in llvm-toolchain

[Sylvestre Ledru]

Package: ftp.debian.org
Severity: normal

See bug #1000917

Bug#1012403: python3-python-flask-jwt-extended,python3-flask-jwt-extended: duplicate packages

[Andreas Beckmann]

Package: python3-python-flask-jwt-extended,python3-flask-jwt-extended
Version: 4.4.0-1
Severity: serious

looks like a duplicate package was just uploaded to the archive.

Andreas

Bug#1012404: RM: llvm-toolchain-12 -- ROM; Limit the number of llvm versions

[Sylvestre Ledru]

Package: ftp.debian.org
Severity: normal

Just like with bug #974789 for -9, #974788 for -10, #1000941 for -11 and 
many others before, 
I am opening this to keep track of all the changes needed to be able to get
rid of llvm-toolchain-12 (afaik, one).

Sylvestre

Bug#1012405: guix: Guix command uses less but less does not exist in dependent software

[Taiju HIGASHI]

Package: guix
Version: 1.3.0-4
Severity: normal

Dear Maintainer,

* What led up to the situation?
A situation that was being verified with the help of an acquaintance.

Note: This is occurring in a container executed with the following command.

docker run --rm -it debian:sid-20220527 bash

* What exactly did you do (or not do) that was effective (or ineffective)?
$ apt update -y
$ apt install guix
$ guix package -s gcc

* What was the outcome of this action?
The following error occurred.

In execvp of less: No such file or directory

* What outcome did you expect instead?
I want to make sure that less is included in the dependent software and that it 
will work correctly when installed in an environment without less.

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

Kernel: Linux 5.17.11 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages guix depends on:
ii  guile-3.0   3.0.8-2
ii  guile-3.0-libs  3.0.8-2
ii  guile-gcrypt0.3.0-4
ii  guile-git   0.5.2-4
ii  guile-gnutls3.7.4-2
ii  guile-json  4.5.2-3
ii  guile-lzlib 0.0.2-3
ii  guile-sqlite3   0.1.3-3
ii  guile-ssh   0.13.1-6
ii  guile-zlib  0.1.0-4
ii  libbz2-1.0  1.0.8-5
ii  libc6   2.33-7
ii  libgcc-s1   12.1.0-2
ii  libgcrypt20 1.10.1-2
ii  libsqlite3-03.38.5-1
ii  libssh-dev  0.9.6-2+b1
ii  libstdc++6  12.1.0-2
ii  zlib1g  1:1.2.11.dfsg-4

Versions of packages guix recommends:
ii  nscd 2.33-7
ii  systemd  251.2-2

guix suggests no packages.

-- no debconf information

Bug#1011051: libssl3: upgrade to libssl3 broke my dovecot setup

[Steven Robbins]

On Monday, June 6, 2022 6:11:38 A.M. CDT Bernhard Übelacker wrote:

> The recent dovecot upload contains this fix:
> 
>dovecot (1:2.3.19+dfsg1-1) unstable; urgency=medium
>  * [d223bbd] d/patches: add patch to support openssl 3.0 (Closes:
> #996273)
> 
>   
> https://salsa.debian.org/debian/dovecot/-/commit/d223bbd1d0968ad2b46c4316c1
> 02c11bde8c5075

That's good news.  Does it mean one can remove the workaround (commenting out 
"providers = provider_sect") ?

Regards,
-Steve
 

Bug#1012275: closing 1012275

[Julian Wollrath]

reopen 1012275
tags 1012275 patch


Hi,

On Sun, 05 Jun 2022 23:46:25 +0200 Christoph Anton Mitterer
 wrote:
> On Sat, 2022-06-04 at 14:42 +0200, Vincent Bernat wrote:
> > Unfortunately, Firefox is not buildable due to depending on a
> > version of
> > Cargo not available in unstable.
>
> Shouldn't that be reopened then?
>
> I wouldn't be surprised if quite a number of people use the non ESR
> FF, probably also DDs/DMs.
>
> And because of rust deps, it seems to happen more often now, that
> security critical upgrades cannot enter unstable. (And yes I'm well
> aware, that unstable has no official security support, but still).

I am not sure though why the packaging requires a newer cargo version
then available from unstable and not just a newer rustc version, I
tried lowering the required version (see patch below) and it builds
just fine for me.


Cheers,
Julian


Patch:

diff -upNr a/debian/control b/debian/control
--- a/debian/control2022-05-31 23:07:37.0 +0200
+++ b/debian/control2022-06-06 13:50:48.239713566 +0200
@@ -28,7 +28,7 @@ Build-Depends: autotools-dev,
yasm,
nasm (>= 2.14) [amd64 i386],
rustc (>= 1.59),
-   cargo (>= 0.60),
+   cargo (>= 0.57),
llvm-dev,
libclang-dev,
clang,
diff -upNr a/debian/control.in b/debian/control.in
--- a/debian/control.in 2022-05-31 23:04:04.0 +0200
+++ b/debian/control.in 2022-06-06 13:51:17.093109680 +0200
@@ -51,9 +51,9 @@ Build-Depends: autotools-dev,
rustc (>= 1.59),
 %endif
 %if DIST == bullseye || DIST == buster || DIST == stretch
-   cargo-mozilla (>= 0.60),
+   cargo-mozilla (>= 0.57),
 %else
-   cargo (>= 0.60),
+   cargo (>= 0.57),
 %endif
 %if DIST == stretch
gcc-mozilla (>= 7.1),
diff -upNr a/debian/patches/debian-hacks/Lower-cargo-version.patch 
b/debian/patches/debian-hacks/Lower-cargo-version.patch
--- a/debian/patches/debian-hacks/Lower-cargo-version.patch 1970-01-01 
01:00:00.0 +0100
+++ b/debian/patches/debian-hacks/Lower-cargo-version.patch 2022-06-06 
14:13:11.030629556 +0200
@@ -0,0 +1,13 @@
+diff --git a/python/mozboot/mozboot/util.py b/python/mozboot/mozboot/util.py
+index 86720993d0..fdbf48f3ed 100644
+--- a/python/mozboot/mozboot/util.py
 b/python/mozboot/mozboot/util.py
+@@ -23,7 +23,7 @@ if sys.version_info < (3,):
+ else:
+ from urllib.request import urlopen
+
+-MINIMUM_RUST_VERSION = "1.59.0"
++MINIMUM_RUST_VERSION = "1.56.0"
+
+
+ def get_tools_dir(srcdir=False):
diff -upNr a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series 2022-05-31 22:51:42.0 +0200
+++ b/debian/patches/series 2022-06-06 14:13:27.027350785 +0200
@@ -17,3 +17,4 @@ debian-hacks/Avoid-using-vmrs-vmsr-on-ar
 debian-hacks/Use-build-id-as-langpack-version-for-reproducibility.patch
 debian-hacks/Allow-to-build-with-older-versions-of-nodejs-10.patch
 debian-hacks/Fix-math_private.h-for-i386-FTBFS.patch
+debian-hacks/Lower-cargo-version.patch



--
 ()  ascii ribbon campaign - against html e-mail
 /\- against proprietary attachments

Bug#1012402: gufw: Illegal instruction on startup with armhf

[Thomas Walther]

Package: gufw
Version: 20.04.1-1
Severity: serious
Justification: Binary package does not seem to work in stable distribution
X-Debbugs-Cc: walther...@gmx.de

when trying to start gufw remotely on armhf it crashes, output is:
/usr/bin/gufw: line 2: [: too many arguments

(polkit-gnome-authentication-agent-1:2758): polkit-gnome-1-WARNING **: 
15:26:18.963: Unable to get a pixbuf for GTK_STOCK_DIALOG_AUTHENTICATION 
(gtk-dialog-authentication) at size 48
ls: cannot access '/usr/lib/python*/site-packages/gufw/gufw.py': No such file 
or directory

(gufw.py:2975): dbind-WARNING **: 15:26:31.061: Couldn't connect to 
accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_0: No 
such file or directory
/usr/bin/gufw-pkexec: line 10:  2975 Illegal instruction python3 
${LOCATIONS[${i}]} $1


-- System Information:
Debian Release: 11.3
Architecture: armhf (armv7l)

Kernel: Linux 5.10.109 (PREEMPT)
Kernel taint flags: TAINT_RANDSTRUCT
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gufw depends on:
ii  gir1.2-gtk-3.0  3.24.24-4+deb11u2
ii  gir1.2-webkit2-4.0  2.36.3-1~deb11u1
ii  policykit-1 0.105-31+deb11u1
ii  python3 3.9.2-3
ii  python3-gi  3.38.0-2
ii  ufw 0.36-7.1

gufw recommends no packages.

gufw suggests no packages.

-- debconf-show failed

Bug#1012401: RFS: csoundqt/1.1.0-1 -- frontend for the csound sound processor

[Dennis Braun]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "csoundqt":

* Package name : csoundqt
Version : 1.1.0-1
Upstream Author : Andrés Cabrera 
* URL : https://github.com/CsoundQt/CsoundQt
* License : LGPL-2.1+, GPL-3+, BSD-3-clause, CC-BY-SA-3.0
* Vcs : https://salsa.debian.org/multimedia-team/csoundqt
Section : sound

The source builds the following binary packages:

csoundqt - frontend for the csound sound processor
csoundqt-examples - example scores for csoundqt

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/csoundqt/

Alternatively, you can download the package with 'dget' using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/c/csoundqt/csoundqt_1.1.0-1.dsc


Changes since the last upload:

csoundqt (1.1.0-1) unstable; urgency=medium
.
[ Debian Janitor ]
* Remove constraints unnecessary since buster:
+ Build-Depends: Drop versioned constraint on libcsnd-dev and
libcsound64-dev.
* debian/copyright: use spaces rather than tabs to start continuation lines.
.
[ Dennis Braun ]
* New upstream version 1.1.0
+ Remove dfsg tag, the unfree Sruti-Drone_Box.csd file has been removed
* d/control:
+ Bump Standards-Version to 4.6.1
+ Set RRR: no
* Drop all patches, applied by upstream
* Update d/csoundqt.lintian-overrides

Regards,
Dennis


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012400: fakeroot: FAKEROOTDONTTRYCHOWN isn't documented

[Dave Love]

Package: fakeroot
Version: 1.25.3-1.1
Severity: normal
X-Debbugs-Cc: none, Dave Love 

The man page doesn't document the use of environment variable
FAKEROOTDONTTRYCHOWN, which turns out to be useful at least for the next
version of charliecloud.  (It looks as if that's the only one.)

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

Kernel: Linux 5.10.0-14-amd64 (SMP w/4 CPU threads)
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)
LSM: AppArmor: enabled

Versions of packages fakeroot depends on:
ii  libc62.31-13+deb11u3
ii  libfakeroot  1.25.3-1.1

fakeroot recommends no packages.

fakeroot suggests no packages.

-- no debconf information

Bug#1012399: fonts-vlgothic: The VL Gothic xAvgCharWidth in the OS/2 table seems wrong

[Francois Gouget]

Package: fonts-vlgothic
Version: 20200720-1
Severity: normal

Dear Maintainer,

Running Wine's tests against the 20200720 VL Gothic fonts finds some
inconsistencies that seem related to the xAvgCharWidth in the OS/2
table. From Wine bug 52951 [1]:

Sagawa wrote:
> From my viewpoint, this is a bug in font.
> VL Gothic ver.20200720 has a strange xAvgCharWidth value, 958, in
> OS/2 table. Generally, xAvgCharWidth is half of the unitsPerEm for
> Japanese fixed-pitch font.
> Previous version of VL Gothic, e.g. 20141206, had 500 xAvgCharWidth.
>
> I've tested the font face on Windows. It shows unnatural horizontal
> spaces between Kanji characters. However, VL Gothic mainly designed
> for Linux. I guess it doesn't matter on Linux.

The specific Wine test failures are:
font.c:4885: Test failed: expected 36 [tmAveCharWidth*2], got 19 [gmCellIncX] 
(VL Gothic:136 [lfCharSet])

[1] https://bugs.winehq.org/show_bug.cgi?id=52951#c1

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

Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr:en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#988630: onedrive: Please update to the latest version

[Norbert Preining]

> Raising severity because of the unusable state.

I would recommend this:
https://github.com/abraunegg/onedrive/blob/master/docs/ubuntu-package-install.md#distribution-package-install-instructions

Up to date packages for Debian stable/testing/unstable, Ubuntu.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#1012398: ITP: golang-github-gomagedon-expectate --

[Victor Seva]

Package: wnpp
Severity: wishlist
Owner: Victor Seva 

* Package name: golang-github-gomagedon-expectate
  Version : 1.1.0-1
  Upstream Author : Steven C Kaufman 
* URL : https://github.com/gomagedon/expectate
* License : Expat
  Programming Lang: Go
  Description : lightweight testing utility for golang
  .
  This testing library's intended purpose is to provide 'expect'
  syntax assertions to golang without using the heavy-handed ginkgo
  toolset.

This package is needed by secsipidx 1.2.0

--
-
|   ,''`. |
|  : :' : |
|  `. `'  Victor Seva |
|`-PGP Key ID: 0x51A09B18CF5A5068 |
 -


OpenPGP_0x51A09B18CF5A5068.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012339: pampi-nonfree don't use localized Documents directory

[Georges Khaznadar]

Hello Davide,

I modified a patch for pampi-nonfree, so it should rely on Qt5's
detection library to decide the location of Documents/Documenti or
other local names for this generic place.

I have uploaded the release to debian/unstable, and closed the bug
report.

Please feel free to reopen it if the patch is inappropriate.

Best regards,   Georges.

Davide Prina a écrit :
> Package: pampi
> Version: 1.1+dfsg1-4
> Severity: normal
> X-Debbugs-Cc: davide.pr...@null.net
> 
> Hi,
> 
> if you run the pampi-nonfree binary in a non English Debian installation
> you have errors like this:
> /home/$YOURUSER/Documents/presentations/assets/tools/GeoGebra/deployggb.js: 
> file or directory do not exist
> 
> this because in a localized sistem the Documents directory has the
> localized name.
> For example in Italian is Documenti.
> 
> As workaround, for who want to execute the binary can create a symbolic
> link between the English name and the localized one, execute the binary
> and then remote the link.
> For example for Italian language:
> 
> $ ln -s ~/Documenti ~/Documents
> $ pampi-nonfree
> $ rm ~/Documents
> 
> Ciao
> Davide
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 
> 'stable-security')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.17.3-dp-20220426 (SMP w/4 CPU threads; PREEMPT)
> Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (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 pampi depends on:
> ii  fonts-katex 0.13.11+~cs6.0.0-3
> ii  fonts-opendyslexic  20160623-4
> ii  fonts-sil-andika6.101-2
> ii  hovercraft  2.7-3
> ii  jsxgraph1.4.3+dfsg1-1
> ii  libjs-bootstrap 3.4.1+dfsg-2
> ii  libjs-c30.4.11+dfsg-4
> ii  libjs-impress   1.1.0-2
> ii  libjs-katex 0.13.11+~cs6.0.0-3
> ii  libjs-marked4.0.16+ds+~4.0.3-1
> ii  macaulay2-common1.20+ds-4
> ii  pandoc  2.9.2.1-3+b2
> ii  python3 3.10.4-1+b1
> 
> pampi recommends no packages.
> 
> pampi suggests no packages.
> 
> -- no debconf information

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Bug#1012054: linux-headers-5.17.0-1-amd64: Sleep mode have stoped working with 5.17 version

[Martin Insulander]

(I noticed I put this on kernel header instead of kernel, should be moved).

But I found this report https://bugzilla.kernel.org/show_bug.cgi?id=215768

And turning off the bluetooth makes my computer sleep, turning it on and
the computer wakes up directly at sleep. So I'm looking forward to the 5.19
release or the bluez update, whichever comes first.

brgds from Martin

Den sön 29 maj 2022 kl 15:09 skrev Martin Insulander <
martin+deb...@insulander.info>:

> Package: linux-headers-5.17.0-1-amd64
> Version: 5.17.3-1
> Severity: important
> X-Debbugs-Cc: martin+deb...@insulander.info
>
> Hi, I try to put the computer to sleep, with either closing the lid or
> pressing
> sleep (in kde menu).
>
> Expect it to sleep.
>
> What happens, since 5.17, it looks like the computer starts to sleep, but
> directly when screen blacks out, it starts again.
>
> This works well in 5.16 (selecting it from Grub at start).
>
> Brgds from Martin
>
>
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (401, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
> Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.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 linux-headers-5.17.0-1-amd64 depends on:
> ii  linux-compiler-gcc-11-x86  5.17.3-1
> ii  linux-headers-5.17.0-1-common  5.17.3-1
> ii  linux-kbuild-5.17  5.17.3-1
>
> linux-headers-5.17.0-1-amd64 recommends no packages.
>
> linux-headers-5.17.0-1-amd64 suggests no packages.
>
> -- no debconf information
>

Bug#1012396: reportbug: Opening list of bugs in the browser leads to a wrong URL

[Philippe SWARTVAGHER]

Package: reportbug
Version: 11.5.0
Severity: normal
Tags: upstream

Dear Maintainer,

When launching for instance `reportbug dia`:
> ...
> Querying Debian BTS for reports on dia src:dia... # so two packages
> ...
> Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? # hit 'b'

It opens my browser with the following URL:
`https://bugs.debian.org/['dia', 'src:dia']`, which is a wrong URL: the
BTS page claims there is no maintainer for the package `['dia',
'src:dia']` (of course!).

I tried to make a fix: when this line [1] is reached, `source` is
`False` and `package` contains `['dia', 'src:dia']`. I don't know if
this situtation is normal, and thus we have to select the correct
package from a list, or if it shouldn't be a list a all and it has to be
fixed in a parent function of the call stack...

Philippe.

[1]
https://salsa.debian.org/reportbug-team/reportbug/-/blob/master/reportbug/ui/text_ui.py#L687



-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/philippe/.reportbugrc:
reportbug_version "11.0.0"
mode standard
ui text

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

Kernel: Linux 5.17.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 reportbug depends on:
ii apt 2.5.0
ii python3 3.10.4-1+b1
ii python3-reportbug 11.5.0
ii sensible-utils 0.0.17

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn claws-mail 
ii debconf 1.5.79
ii debsums 3.0.2
pn dlocate 
pn emacs-bin-common 
ii exim4-daemon-light [mail-transport-agent] 4.95-6
ii file 1:5.41-4
ii gnupg 2.2.35-2
pn python3-urwid 
pn reportbug-gtk 
ii xdg-utils 1.1.3-4.1

Versions of packages python3-reportbug depends on:
ii apt 2.5.0
ii file 1:5.41-4
ii python3 3.10.4-1+b1
ii python3-apt 2.3.0+b1
ii python3-debian 0.1.44
ii python3-debianbts 3.2.1
ii python3-requests 2.27.1+dfsg-1
ii sensible-utils 0.0.17

python3-reportbug suggests no packages.

-- no debconf information

Bug#922630: dupe of 993051?

[Vincent Lefevre]

On 2022-06-06 11:51:17 +0200, Mathieu ROY wrote:
> This bug is very likely the same as 993051 that you fixed yesterday.

I agree. With the absence of additional information (and a vague
bug title), these bugs should be regarded as being the same.

Before the upgrade to 0.8-6 (i.e. containing the 993051 bug fix),
I'm trying to reproduce the issue with 0.8-5[*], but I do not
notice it any longer. I suppose that on the network, there was a
machine that triggered the issue, but it is no longer there. So,
unfortunately, I can't say more on the issue I got at that time.

[*] Same machine, same network, same avahi-daemon version as
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922630#20
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922630#27

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1012390: Gajim 1.4.0 crashes at startup if gir1.2-gst-plugins-base-1.0 is not installed

[Grzegorz Szymaszek]

On Mon, Jun 06, 2022 at 10:11:37AM +, Martin wrote:
> On 2022-06-06 11:00, Grzegorz Szymaszek wrote:
> > Installing gir1.2-gst-plugins-base-1.0 makes it work again. gajim
> > currently recommends this package, perhaps it should depend on it?
> 
> Yes and it's already done in 1.4.3-1, now in Debian unstable.

Great, thank you!

-- 
Grzegorz


signature.asc
Description: PGP signature

Bug#1010911: RM: gajim-plugininstaller/experimental -- RoM; obsoleted by gajim 1.4.0

[Martin]

Control: reopen -1
Control: retitle -1 RM: gajim-plugininstaller/experimental -- RoM; obsoleted by 
gajim 1.4.0

gajim-plugininstaller should be removed from experimental, too.
It's not urgent, of course.

Bug#986174: marked as pending in subversion

[John Paul Adrian Glaubitz]

Hi!

On 6/6/22 12:31, James McCoy wrote:
>> Thanks! While you're at it, could you disable Ruby support on ia64 for the 
>> time being?
> 
> Already done. :)
> 
> https://salsa.debian.org/jamessan/subversion/-/commit/cc181155e36385c3af550fe1495827eb65cd6fb9

OK, great. Then we'll just have to wait for the next upload.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#771058: tag patch

[Niels Thykier]

Control: tags -1 + patch
thanks

MR at
https://salsa.debian.org/python-debian-team/python-debian/-/merge_requests/88

Bug#1012395: start-stop-daemon: matching only on non-root pidfile /run/netdata.pid is insecure

[Gian Piero Carrubba]

Package: netdata-core
Version: 1.34.1-1+b1
Severity: normal
Tags: patch

Init: OpenRC (via /run/openrc), PID 1: init

> ls -l /run/netdata.pid
ls: cannot access '/run/netdata.pid': No such file or directory
> sudo service netdata start
Starting the netdata daemon...2022-06-06 12:09:40: netdata INFO  : MAIN
: CONFIG: cannot load cloud config
'/var/lib/netdata/cloud.d/cloud.conf'. Running with internal defaults.
done.
> sudo service netdata status
netdata is running.
> sudo service netdata stop
Stopping the netdata daemon...start-stop-daemon: matching only on
non-root pidfile /run/netdata.pid is insecure
failed (/usr/sbin/netdata died: process 12267 not running; or permission
denied).
> ls -l /run/netdata.pid
-rw-r--r-- 1 netdata netdata 6 Jun  6 12:09 /run/netdata.pid
> pgrep -l netdata
12267 netdata
12269 netdata

Thanks,
Gian Piero.

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

Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled

Versions of packages netdata-core depends on:
ii  init-system-helpers  1.63
ii  libc62.33-7
ii  libcap2  1:2.44-1
ii  libcap2-bin  1:2.44-1
ii  libjson-c5   0.16-1
ii  libjudydebian1   1.0.5-5+b2
ii  liblz4-1 1.9.3-2
ii  libmnl0  1.0.4-3
ii  libnetfilter-acct1   1.0.3-3
ii  libssl3  3.0.3-6
ii  libuuid1 2.38-4
ii  libuv1   1.44.1-2
ii  lsb-base 11.2
ii  zlib1g   1:1.2.11.dfsg-4

Versions of packages netdata-core recommends:
ii  curl  7.83.1-1+b1

Versions of packages netdata-core suggests:
ii  apcupsd 3.14.14-3.1
ii  iproute25.17.0-2
ii  iw  5.16-1
ii  lm-sensors  1:3.6.0-7
pn  nc  

-- Configuration Files:
/etc/netdata/netdata.conf changed [not included]

-- no debconf information
--- a/netdata   2022-04-15 22:03:48.0 +0200
+++ b/netdata   2022-06-06 12:23:43.413715597 +0200
@@ -46,8 +46,8 @@
 
log_action_begin_msg "Starting $DESC"
 
-   if start-stop-daemon --start --quiet --pidfile $PIDFILE --startas 
$DAEMON --test; then
-   if start-stop-daemon --start --quiet --pidfile $PIDFILE 
--startas $DAEMON -- $DAEMON_ARGS; then
+   if start-stop-daemon --start --quiet --pidfile $PIDFILE --name $NAME 
--startas $DAEMON --test; then
+   if start-stop-daemon --start --quiet --pidfile $PIDFILE --name 
$NAME --startas $DAEMON -- $DAEMON_ARGS; then
log_action_end_msg 0
else
log_action_end_msg 1
@@ -65,7 +65,7 @@
exit 0
fi
 
-   if start-stop-daemon --stop --quiet --pidfile $PIDFILE 
--retry=$STOP_SCHEDULE; then
+   if start-stop-daemon --stop --quiet --pidfile $PIDFILE --name $NAME 
--retry=$STOP_SCHEDULE; then
log_action_end_msg 0
else
log_action_end_msg 1 "$DAEMON died: process $pid not running; 
or permission denied"

Bug#986174: marked as pending in subversion

[James McCoy]

On Mon, Jun 06, 2022 at 11:24:21AM +0200, John Paul Adrian Glaubitz wrote:
> Hi!
> 
> On 6/6/22 02:55, James McCoy wrote:
> > Bug #986174 in subversion reported by you has been fixed in the
> > Git repository and is awaiting an upload. You can see the commit
> > message below and you can check the diff of the fix at:
> > 
> > https://salsa.debian.org/jamessan/subversion/-/commit/d90374d3bf58fdc8a350576c73e9303668ae3b2d
> 
> Thanks! While you're at it, could you disable Ruby support on ia64 for the 
> time being?

Already done. :)

https://salsa.debian.org/jamessan/subversion/-/commit/cc181155e36385c3af550fe1495827eb65cd6fb9

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#1012394: RFS: pt2-clone/1.49+ds-1 -- Music tracker clone of ProTracker 2 for modern computers

[Dennis Braun]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for "my" package "pt2-clone":

* Package name : pt2-clone
Version : 1.49+ds-1
Upstream Author : Olav "8bitbubsy" Sørensen 
* URL : https://16-bits.org/pt.php
* License : BSD-3-clause, zlib-style
* Vcs : https://salsa.debian.org/multimedia-team/pt2-clone
Section : sound

The source builds the following binary packages:

pt2-clone - Music tracker clone of ProTracker 2 for modern computers

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/pt2-clone/

Alternatively, you can download the package with 'dget' using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/pt2-clone/pt2-clone_1.49+ds-1.dsc


Changes since the last upload:

pt2-clone (1.49+ds-1) unstable; urgency=medium
.
* New upstream version 1.49+ds
+ Refresh Files-Excluded
* d/control:
+ Add me as uploader
+ Wrap-and-sort B-Ds and Depends
+ Bump Standards Version to 4.6.1
* d/copyright: Add myself to the d/ section
* Remove obsolete d/dirs folder
* d/rules: Remove unneeded linker flags
* Add salsa ci config

Regards,
Dennis

Bug#1012393: RFS: bambootracker/0.5.0-1 -- YM2608 (OPNA, sound chip of Yamaha) music tracker

[Dennis Braun]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for "my" package "bambootracker":

* Package name : bambootracker
Version : 0.5.0-1
Upstream Author : Rerrah
* URL : https://github.com/rerrahkr/BambooTracker
* License : MIT, GPL-2+, BSD-3-clause, CC-BY-SA-3.0
* Vcs : https://salsa.debian.org/multimedia-team/bambootracker
Section : sound

The source builds the following binary packages:

bambootracker - YM2608 (OPNA, sound chip of Yamaha) music tracker

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/bambootracker/

Alternatively, you can download the package with 'dget' using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/b/bambootracker/bambootracker_0.5.0-1.dsc


Changes since the last upload:

bambootracker (0.5.0-1) unstable; urgency=medium
..
* New upstream version 0.5.0
+ Build with jack, pulsaudio and rtaudio support
* Add emu2149 sources as missing-sources, a PSG emulator Build-Dependency
* d/control:
+ Add me as uploader
+ Wrap-and-sort B-Ds and Depends
+ Update B-Ds: Add libjack-jackd2-dev | libjack-dev,
mark libasound2-dev as linux-any, add libpulse-dev and librtaudio-dev
+ Bump Standards Version to 4.6.1
* d/copyright: Bump year and add myself to the d/ section
* d/docs: Don't install old/archived specs
* Install the 256x256 icon from upstream
* Add d/lintian-overrides
* d/rules:
+ Use the root dir to build
+ Copy emu2149 files before dh_auto_configure
+ Delete the man/en dir after moving the man file
+ Avoid two /usr/share/doc folders
* Avoid double installations of examples

Regards,
Dennis

Bug#1012390: Gajim 1.4.0 crashes at startup if gir1.2-gst-plugins-base-1.0 is not installed

[Martin]

Control: fixed -1 1.4.3-1

Hi Grzegorz!

On 2022-06-06 11:00, Grzegorz Szymaszek wrote:
> Installing gir1.2-gst-plugins-base-1.0 makes it work again. gajim
> currently recommends this package, perhaps it should depend on it?

Yes and it's already done in 1.4.3-1, now in Debian unstable.

Cheers, Martin

Bug#1012392: RFS: snd/22.4-1 -- Sound file editor

[Dennis Braun]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for "my" package "snd":

* Package name : snd
Version : 22.4-1
Upstream Author : IOhannes m zmölnig 
* URL : https://ccrma.stanford.edu/software/snd/
* License : GPL-2+, Expat, LLGPL, BSD-2-clause, public-domain, 
other-Tcl/Tk, GPL-2+ or GL2PS

* Vcs : https://salsa.debian.org/multimedia-team/snd
Section : sound

The source builds the following binary packages:

snd - Sound file editor (metapackage)
snd-common - Sound file editor (core)
snd-doc - Sound file editor (documentation)
snd-gui-jack - Sound file editor (graphical user interface - JACK)
snd-gui-pulse - Sound file editor (graphical user interface - PulseAudio)
snd-nox - Sound file editor (cmdline)
snd-gtk-jack - Sound file editor (dummy transitional package)
snd-gtk-pulse - Sound file editor (dummy transitional package)

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/snd/

Alternatively, you can download the package with 'dget' using this command:

dget -x https://mentors.debian.net/debian/pool/main/s/snd/snd_22.4-1.dsc

Changes since the last upload:

snd (22.4-1) unstable; urgency=medium
.
[ Debian Janitor ]
* Fix day-of-week for changelog entries 4.10-1, 3.4-1.
* Use cross-build compatible macro for finding pkg-config.
.
[ Dennis Braun ]
* New upstream version 22.4
+ Update d/upstream-changelog
* d/control:
+ Add libjack-jackd2-dev as B-D and libjack-dev as optional
+ Bump Standards Version to 4.6.1

Regards,
Dennis

Bug#1012391: RFS: projectm/3.1.12-2 -- projectM SDL module

[Dennis Braun]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "projectm":

* Package name : projectm
Version : 3.1.12-2
Upstream Author : [fill in name and email of upstream]
* URL : https://github.com/projectM-visualizer/projectm
* License : LGPL-2.1+, GPL-2+, bitstream-vera, Expat
* Vcs : https://salsa.debian.org/multimedia-team/projectm
Section : sound

The source builds the following binary packages:

libprojectm3 - Advanced Milkdrop-compatible music visualization library
libprojectm-dev - Advanced Milkdrop-compatible music visualization 
library - dev
projectm-data - Advanced Milkdrop-compatible music visualization library 
- data

projectm-jack - projectM JackAudio module
projectm-pulseaudio - projectM PulseAudio module
projectm-sdl - projectM SDL module

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/projectm/

Alternatively, you can download the package with 'dget' using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/projectm/projectm_3.1.12-2.dsc


Changes since the last upload:

projectm (3.1.12-2) unstable; urgency=medium
..
* Bump Standards Version to 4.6.1
* Switch projectm3 dependency from ttf-bitstream-vera to fonts-dejavu-core
(Closes: #998268)
+ Update font patch: Use fonts-dejavu-core instead of ttf-bitstream-vera
* Make projectm-pulseaudio depend on projectm-data (Closes: #997665)
* Add libjack-jackd2-dev as B-D and libjack-dev as optional

Regards,
Dennis

Bug#922630: dupe of 993051?

[Mathieu ROY]

Hi,

This bug is very likely the same as 993051 that you fixed yesterday.

Thanks!

Regards,

Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- generate/convert the docstrings from code signature)

[Nilson Silva]

This is the previous version.

Before making a push, I made a pull. because you had created a debian tag.
the remote branch was a commit ahead of me.

after I made a pull,
I made the new entry in the changlog and then I made the last commit. then I 
pushed again.
as it was not passing the CI/CD test I did a force.

If I have to go back to the previous state, could you tell me how to do it?

I thought in my ignorance, that as I had made a pull before there would be no 
problem.

forgive
thanks!


From: Bastian Germann 
Sent: Monday, June 6, 2022 4:52:22 AM
To: Nilson Silva ; 1011...@bugs.debian.org 
<1011...@bugs.debian.org>
Subject: Re: Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- 
generate/convert the docstrings from code signature)

Hi Nilson,

This is not at all the idea of collaboration via git. You now do not have a 
version that matches the published archive
version. Please do not do such things! CI may pass or not. It is not the idea 
to have the Salsa CI passing all the time
but to have a working copy that 1) represents the archive and 2) makes it 
easier for people to contribute without being
the uploader.

So, please recover the old version.

Thanks,
Bastian

Am 06.06.22 um 06:23 schrieb Nilson Silva:
> I decided Deleted the branches and made a new push. Just go up foul to 
> unstable. Thanks!
>
>
> 
> *De:* Nilson Silva 
> *Enviado:* segunda-feira, 6 de junho de 2022 00:30
> *Para:* Bastian Germann ; 1011...@bugs.debian.org 
> <1011...@bugs.debian.org>
> *Assunto:* RE: Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- 
> generate/convert the docstrings from code
> signature)
>
> Hi! As the package has already been accepted. I have already updated the 
> salsa repository with the new changelog entry
> for unstable. I created the new tag and pushed it; But it is not passing the 
> CI/CD test. It is saying that this file has
> been modified. source_dir/doc/sphinx/source/pyment.rst. But don't mess with 
> anything. So much so that in my repository
> it is passing normally.
> https://salsa.debian.org/nilsonfsilva/pyment/-/commit/8e784390ef3c4d7a0cc5e3e7808419003a128799/pipelines?ref=debian%2Fmaster
> I didn't understand this one. If you can explain, thank you.
>
> .
>
> Thanks!
>
>
> 
> *De:* Debian Bug Tracking System 
> *Enviado:* quarta-feira, 25 de maio de 2022 21:24
> *Para:* Bastian Germann 
> *Assunto:* Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- 
> generate/convert the docstrings from code
> signature)
> Your message dated Thu, 26 May 2022 02:21:02 +0200
> with message-id 
> and subject line Re: ENC: RFS: pyment/1.0-1 [ITP] -- generate/convert the 
> docstrings from code signature (CONSIDER THIS)
> has caused the Debian Bug report #1011018,
> regarding RFS: pyment/0.3.4+ds-1 [ITP] -- generate/convert the docstrings 
> from code signature
> 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.)
>
>
> --
> 1011018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011018
> 
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Bug#1012348: transition: rocksdb

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2022-06-05 10:26:25, László Böszörményi wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi RMs,
> 
> Transition request to show my intentions and track what's blocking.
> Two packages, balboa and python-rocksdb are affected with the rocksdb
> 7.2.2 transition. The former builds fine while the latter uses a
> library header that was changed big and renamed. Its upstream did some
> updates [1] but not finished. Package maintainer is noted days ago
> [2].
> I don't know how long python-rocksdb upstream will take for the update. :(

Please go ahead. If python-rocksdb takes too long to get fixed, we can
temporarily remove it from testing.

Cheers

> 
> Thanks for considering,
> Laszlo/GCS
> [1] 
> https://github.com/NightTsarina/python-rocksdb/commit/be185cc96df366dc81bd46466341e7057d7775b6
> [2] https://bugs.debian.org/1012074
> 

-- 
Sebastian Ramacher

Bug#986174: marked as pending in subversion

[John Paul Adrian Glaubitz]

Hi!

On 6/6/22 02:55, James McCoy wrote:
> Bug #986174 in subversion reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
> 
> https://salsa.debian.org/jamessan/subversion/-/commit/d90374d3bf58fdc8a350576c73e9303668ae3b2d

Thanks! While you're at it, could you disable Ruby support on ia64 for the time 
being?

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1012390: Gajim 1.4.0 crashes at startup if gir1.2-gst-plugins-base-1.0 is not installed

[Grzegorz Szymaszek]

Package: gajim
Version: 1.4.0-1

Dear Maintainer,

after upgrading to Gajim 1.4.0, the program no longer starts correctly
and shows the crash reporting dialog instead. Here are the software
component versions listed in the dialog:
- OS: Debian GNU/Linux bookworm/sid testing (bookworm)
- GTK Version: 3.24.34
- PyGObject Version: 3.42.1
- GLib Version : 2.72.0
- python-nbxmpp Version: 3.0.1
- Gajim Version: 1.4.0
And here is the traceback:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gajim/gtk/application.py", line 233, 
in _startup
from gajim.gui_interface import Interface
  File "/usr/lib/python3/dist-packages/gajim/gui_interface.py", line 74, in 

from gajim.common.preview import PreviewManager
  File "/usr/lib/python3/dist-packages/gajim/common/preview.py", line 38, 
in 
from gajim.common.preview_helpers import aes_decrypt
  File "/usr/lib/python3/dist-packages/gajim/common/preview_helpers.py", 
line 34, in 
from gi.repository import GstPbutils
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 136, in 
load_module
raise ImportError('cannot import name %s, '
ImportError: cannot import name GstPbutils, introspection typelib not found

Installing gir1.2-gst-plugins-base-1.0 makes it work again. gajim
currently recommends this package, perhaps it should depend on it?


All the best

-- 
Grzegorz


signature.asc
Description: PGP signature

Bug#1012318: diffoscope 214 produced no output and was killed after running into timeout after 150m

[Chris Lamb]

Vagrant Cascadian wrote:

> Some things just take a long time to run diffoscope, and
> tests.reproducible-builds.org only lets diffoscope run for 150m and then
> kills it to avoid very large unreproducible packages from eating all the
> resources.

(I do see that Vagrant has sent a diff in a subsequent email in this
thread...)

For the benefit of Roman, there are actually two levels of timeouts
involved when running diffoscope on tests.reproducible-builds.org:

First, we pass a value to diffoscope's --timeout option:

  --timeout SECONDS Best-effort attempt at a global timeout in seconds. If
enabled, diffoscope will not recurse into any further
sub-archives after X seconds of total execution time.
(default: no timeout) [experimental]

... and then there's a longer and harsher timeout that's controlled by
the Jenkins apparatus that runs tests.r-b.org. It is this timeout you
are seeing when you see "diffoscope was killed..." on the website.

It's not strictly a *bug* that diffoscope takes a long time, but it is
curious that the best-effort "--timeout" is not kicking in early enough
and ensuring that the harsher timeout does not kill diffoscope outright.

Indeed, the --timeout option was implemented precisely to avoid having
no output whatsoever on tests.r-b.org.

Vagrant, do you have --profile output, out of interest? It would be
interesting, for instance, if the HTML generation was taking so long
that even if diffoscope stopped recursing into subarchives, it hit
Jenkins' hard timeout. This may suggest that there is a bug in the
HTML generation, and/or that the --timeout value on tests.r-b.org has
not been set low enough relative to the hard timeout.


Best wishes,

-- 
  o
⬋   ⬊  Chris Lamb
   o o reproducible-builds.org 
⬊   ⬋
  o

Bug#1012198: Source of problem is a wrong link of libsane.so.1

[Jörg Frings-Fürst]

Hello Markus,

thank you for spending your time helping to make Debian better with
this bug report.

The symlinks are already created when compiling the sources. And when
installing the package still copied to the right place.

First I checked if there is an artifact from the upgrade stretch via
Buster to Bullseye. But this is not the case and would certainly have
been reported before.

With the Brother packages present here some symlinks are created only
with the installation, but no /usr/lib64/sane/libsane.so.1. Here
however only current packages are available to me.

Since the /usr/lib64/sane/libsane.so.1 does not come from the package
sane-backends I close this bug. If there are new findings, please open
a new bugreport.


CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



Am Mittwoch, dem 01.06.2022 um 01:11 + schrieb Markus Kolb:
> Hello again,
> 
> I've built the version from Testing locally and with this I've found
> that the problem has been a more priorised link 
> /usr/lib64/sane/libsane.so.1 which becomes created to a
> /usr/lib64/sane/libsane-brother3.so.1.0.7.
> The brother3.so is from a manually installed deb-file for my Brother
> network printer.
> 
> But I've no idea why the libsane.so.1 link is created during
> installation of libsane1 package to this ...brother3.so...
> 
> After deleting the wrong link, it uses the correct /usr/lib/x86_64-
> linux-gnu/libsane.so.1 from libsane1 package and the scanimage tool
> works.
> Instead of deleting the link I've replaced it now with a new link
> targeting the correct /usr/lib/x86_64-linux-gnu/libsane.so.1. In the
> hope it stays in place for the future. 
> 
> Is it possible that the libsane-brother3.so.1.0.7 is found with a
> glob like libsane*so.* and wrongly linked during libsane-common,
> libsane1 or sane-utils package install?




signature.asc
Description: This is a digitally signed message part

Bug#1011954: CVE-2022-1586 CVE-2022-1587

[Moritz Mühlenhoff]

Am Fri, May 27, 2022 at 06:52:11PM +0100 schrieb Matthew Vernon:
> Hi,
> 
> Would you like me to prepare an upload for these, or are you working on
> this?
> 
> [sorry, it's not clear from the bug report]

Sorry, this fell through the cracks until I just started to flush in
inbox's backlog.

Whether we should fix this via a DSA needs a closer look first; for
regex engines the decisive factor is whether the OOB reads can be
triggered via malformed input fed to the regex library (then we can
fix this via a DSA) or via an untrusted regex pattern passed to
the library (which wouldn't warrant a DSA since it's inherently
unsafe and some basic form of sanitising is within the responsbility
of the application using pcre.

Cheers,
Moritz

Bug#1012389: duplicity: Can't backup anymore - AssertionError

[Christophe Lohr]

Package: duplicity
Version: 0.8.22-1
Severity: important
Tags: upstream

Dear Maintainer,

I can't use duplicity anymore.
For instance:
~$ duplicity collection-status $TARGET
Traceback (innermost last):
  File "/usr/bin/duplicity", line 92, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 75, in with_tempdir
fn()
  File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1577, in
main
do_backup(action)
  File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1599, in
do_backup
action).set_values()
  File "/usr/lib/python3/dist-packages/duplicity/dup_collections.py", line 761,
in set_values
self.set_matched_chain_pair(local_sig_chains + remote_sig_chains,
  File "/usr/lib/python3/dist-packages/duplicity/dup_collections.py", line 775,
in set_matched_chain_pair
sig_chains = sig_chains and self.get_sorted_chains(sig_chains)
  File "/usr/lib/python3/dist-packages/duplicity/dup_collections.py", line 992,
in get_sorted_chains
assert len(chain_list) == 2
 AssertionError


What's wrong? What should I do?

Best regards


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'oldstable-updates'), (500, 'oldoldstable'), (500, 'testing'), (500, 'stable'), 
(500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 duplicity depends on:
ii  gnupg  2.2.35-2
ii  libc6  2.33-7
ii  librsync2  2.3.2-1+b1
ii  python33.10.4-1+b1
ii  python3-fasteners  0.17.3-2
ii  python3-future 0.18.2-6
ii  python3-lockfile   1:0.12.2-2.2
ii  python3.10 3.10.4-1

Versions of packages duplicity recommends:
ii  python3-oauthlib  3.2.0-1
ii  python3-paramiko  2.8.1-1
ii  python3-pexpect   4.8.0-3
ii  python3-urllib3   1.26.9-1
ii  rsync 3.2.4-1

Versions of packages duplicity suggests:
ii  lftp 4.9.2-1+b1
ii  ncftp2:3.2.5-2.2
pn  par2 
pn  python3-boto 
ii  python3-pip  22.1.1+dfsg-1
pn  python3-swiftclient  
pn  tahoe-lafs   

-- no debconf information

Bug#1012388: RFP: jupytext -- a plugin for Jupyter that can convert Jupyter notebook formats

[Drew Parsons]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-pyt...@lists.debian.org

* Package name: jupytext
  Version : 1.13.8
  Upstream Author : Marc Wouts 
* URL : https://github.com/mwouts/jupytext
* License : MIT
  Programming Lang: Python
  Description : a plugin for Jupyter that can convert Jupyter notebook 
formats

Have you always wished Jupyter notebooks were plain text documents?
Wished you could edit them in your favorite IDE? And get clear and
meaningful diffs when doing version control? Then... Jupytext may well
be the tool you're looking for!

Jupytext is a plugin for Jupyter that can save Jupyter notebooks as either
- Markdown files (or MyST Markdown files, or R Markdown or Quarto text 
notebooks)
- Scripts in many languages.

The conversion goes both ways, jupytext can convert python scripts or
markdown files into .ipynb Jupyter scripts.


jupytext can help generate docs for python modules, and has started
being used in the doc workflow for some packages (e.g. dolfinx).

Best suited for team maintenance under the Python Packaging Team.

Bug#1012387: coffeescript: please make the build reproducible

[Chris Lamb]

Source: coffeescript
Version: 2.7.0-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
coffeescript could not be built reproducibly.

This is because it uses the current build date when generating years in
copyright headers. A patch is attached that seeds this date from the
value of SOURCE_DATE_EPOCH [1]

 [0] https://reproducible-builds.org/
 [1] https://reproducible-builds.org/docs/source-date-epoch/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible-build.patch   2022-06-06 09:30:12.420262570 
+0100
@@ -0,0 +1,23 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2022-06-06
+
+--- coffeescript-2.7.0.orig/Cakefile
 coffeescript-2.7.0/Cakefile
+@@ -16,12 +16,15 @@ unless process.env.NODE_DISABLE_COLORS
+   reset  = '\x1B[0m'
+ 
+ # Built file header.
++now = new Date()
++if process.env.SOURCE_DATE_EPOCH
++  now = new Date((process.env.SOURCE_DATE_EPOCH * 1000) + 
(now.getTimezoneOffset() * 6))
+ header = """
+   /**
+* CoffeeScript Compiler v#{CoffeeScript.VERSION}
+* https://coffeescript.org
+*
+-   * Copyright 2011-#{new Date().getFullYear()}, Jeremy Ashkenas
++   * Copyright 2011-#{now.getFullYear()}, Jeremy Ashkenas
+* Released under the MIT License
+*/
+ """
--- a/debian/patches/series 2022-06-06 09:06:57.161874011 +0100
--- b/debian/patches/series 2022-06-06 09:21:57.567702386 +0100
@@ -1,2 +1,3 @@
 fix-node-path.patch
 privacy.patch
+reproducible-build.patch

Bug#988630: onedrive: Please update to the latest version

[Bastian Germann]

Control: severity -1 serious

On Wed, 8 Dec 2021 19:48:56 +0100 bor...@adott.hu wrote:> At the moment, that version is also unusable because of a 
recent change

in OneDrive.


Raising severity because of the unusable state.

Bug#939619: pygatt -- Python interface to the gatttool Bluetooth command

[Petter Reinholdtsen]

[Bastian Germann]
> I do not know. If you have a reason why you need this specific library when
> there is one similar alreay existing in Debian please explain it here.

OK.  The reason was explained in the initial message.  It was needed to
get bluetooth_le_tracker from Home Assistant working in the Debian based
distribution Hassbian.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- generate/convert the docstrings from code signature)

[Bastian Germann]

Hi Nilson,

This is not at all the idea of collaboration via git. You now do not have a version that matches the published archive 
version. Please do not do such things! CI may pass or not. It is not the idea to have the Salsa CI passing all the time 
but to have a working copy that 1) represents the archive and 2) makes it easier for people to contribute without being 
the uploader.


So, please recover the old version.

Thanks,
Bastian

Am 06.06.22 um 06:23 schrieb Nilson Silva:

I decided Deleted the branches and made a new push. Just go up foul to 
unstable. Thanks!



*De:* Nilson Silva 
*Enviado:* segunda-feira, 6 de junho de 2022 00:30
*Para:* Bastian Germann ; 1011...@bugs.debian.org 
<1011...@bugs.debian.org>
*Assunto:* RE: Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- generate/convert the docstrings from code 
signature)


Hi! As the package has already been accepted. I have already updated the salsa repository with the new changelog entry 
for unstable. I created the new tag and pushed it; But it is not passing the CI/CD test. It is saying that this file has 
been modified. source_dir/doc/sphinx/source/pyment.rst. But don't mess with anything. So much so that in my repository 
it is passing normally. 
https://salsa.debian.org/nilsonfsilva/pyment/-/commit/8e784390ef3c4d7a0cc5e3e7808419003a128799/pipelines?ref=debian%2Fmaster 
I didn't understand this one. If you can explain, thank you.


.

Thanks!



*De:* Debian Bug Tracking System 
*Enviado:* quarta-feira, 25 de maio de 2022 21:24
*Para:* Bastian Germann 
*Assunto:* Bug#1011018: marked as done (RFS: pyment/0.3.4+ds-1 [ITP] -- generate/convert the docstrings from code 
signature)

Your message dated Thu, 26 May 2022 02:21:02 +0200
with message-id 
and subject line Re: ENC: RFS: pyment/1.0-1 [ITP] -- generate/convert the 
docstrings from code signature (CONSIDER THIS)
has caused the Debian Bug report #1011018,
regarding RFS: pyment/0.3.4+ds-1 [ITP] -- generate/convert the docstrings from 
code signature
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.)


--
1011018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011018 


Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#939619: pygatt -- Python interface to the gatttool Bluetooth command

[Bastian Germann]

Am 06.06.22 um 09:11 schrieb Petter Reinholdtsen:

[Bastian Germann]

Please use the pygattlib package.


[Petter Reinholdtsen]

This library is used by the bluetooth_le_tracker component of Home
Assistant, and is needed to get this component working on Hassbian.


Is the bluetooth_le_tracker component of Home Assistent now ported to
use pygattlib?


I do not know. If you have a reason why you need this specific library when
there is one similar alreay existing in Debian please explain it here.

Bug#1012279: php-horde-turba: CVE-2022-30287

[Salvatore Bonaccorso]

Hi Mike, Juri,

On Sun, Jun 05, 2022 at 07:50:20PM +, Mike Gabriel wrote:
> Hi Salvatore,
> 
> On  So 05 Jun 2022 14:35:03 CEST, Salvatore Bonaccorso wrote:
> 
> > Hi,
> > 
> > On Sun, Jun 05, 2022 at 12:02:54PM +, Mike Gabriel wrote:
> > > Hi Juri,
> > > 
> > > On  Sa 04 Jun 2022 00:13:11 CEST, debian wrote:
> > > 
> > > > Hello,
> > > >
> > > > here is draft for MR:
> > > > https://salsa.debian.org/horde-team/php-horde-turba/-/merge_requests/1
> > > > I would look after it next time on sunday evening.
> > > >
> > > > @Mike: Can you please review it?
> > 
> > it looks that the force pushed commit two days ago adjusted two
> > further create() -> createTrusted() stances in lib/Application.php,
> > can you double check?
> 
> I actually did double check already, applied 9f242132 and saw that it did
> not apply properly (and thus reverted). See Git history at [1]. It seems
> that the backup/restore API calls (where these two spots of create ->
> createTrusted had been added) were not part of the 4.2.25 upstream release
> of turba.
> 
> > https://github.com/horde/turba/commit/9f2521328aa7d0dbd905591eca138c8e7580d673
> > (which is not yet merged, but compare to the used
> > https://github.com/horde/turba/commit/784da95e0190321b08ceeb27e2cb6c7505f2057c).
> > 
> > p.s.: the upload did contain a non valid bug closer, which in case the
> > above is correct cha be simply closed in a 4.2.25-7 upload.
> 
> If you agree, we have to close the bug manually as Juri's approach already
> contained the right patch.

yes, thank you!

Salvatore

Bug#1012279: php-horde-turba: CVE-2022-30287

[Salvatore Bonaccorso]

Source: php-horde-turba
Source-Version: 4.2.25-6

On Mon, Jun 06, 2022 at 05:50:33AM +0200, Juri Grabowski wrote:
> Hello together,
> 
> On 2022-06-05 14:35 7, Salvatore Bonaccorso wrote:
> > it looks that the force pushed commit two days ago adjusted two
> > further create() -> createTrusted() stances in lib/Application.php,
> > can you double check?
> functions backup and _restoreContact are only available on turba/master
> for future release.

Thanks for checking. In this case let's close this bug with the
4.2.25-6 version.

Regards,
Salvatore

Bug#1012386: python-seqcluster: FTBFS: ModuleNotFoundError: No module named 'attr'

[Andreas Beckmann]

Source: python-seqcluster
Version: 1.2.8+ds-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

python-seqcluster recently started to FTBFS after some (transitive)
build-dependency got updated:

[...]
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bman   doc/source 
build/man # Manpage generator
Running Sphinx v4.5.0

Exception occurred:
  File "/usr/lib/python3/dist-packages/myst_parser/main.py", line 3, in 
import attr
ModuleNotFoundError: No module named 'attr'
The full traceback has been saved in /tmp/sphinx-err-3fkwfzes.log, if you want 
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 2
[...]

The sphinx error log contains:

# Sphinx version: 4.5.0
# Python version: 3.10.4 (CPython)
# Docutils version: 0.17.1 release
# Jinja2 version: 3.0.3
# Last messages:

# Loaded extensions:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 272, in 
build_main
app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 217, in 
__init__
self.setup_extension(extension)
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 374, in 
setup_extension
self.registry.load_extension(self, extname)
  File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 438, in 
load_extension
metadata = setup(app)
  File "/usr/lib/python3/dist-packages/myst_parser/__init__.py", line 12, in 
setup
from myst_parser.sphinx_parser import MystParser
  File "/usr/lib/python3/dist-packages/myst_parser/sphinx_parser.py", line 15, 
in 
from myst_parser.main import default_parser
  File "/usr/lib/python3/dist-packages/myst_parser/main.py", line 3, in 
import attr
ModuleNotFoundError: No module named 'attr'


Andreas


python-seqcluster_1.2.8+ds-2.log.gz
Description: application/gzip

Bug#1011653: blender ftbfs: no matching functional for call to openvdb*

[Gianfranco Costamagna]

On Wed, 25 May 2022 19:44:40 -0400 "M. Zhou"  wrote:

Source: blender
Version: 2.83.5+dfsg-5
Severity: serious

I found it ftbfs during onetbb reverse dependency test,
although the reason irrelevant to onetbb.
Version 3.X is still not built for amd64.






The reason for this failure is in DCMTK, bug #1010536

G.

Bug#939619: pygatt -- Python interface to the gatttool Bluetooth command

[Petter Reinholdtsen]

[Bastian Germann]
> Please use the pygattlib package.

[Petter Reinholdtsen]
> This library is used by the bluetooth_le_tracker component of Home
> Assistant, and is needed to get this component working on Hassbian.

Is the bluetooth_le_tracker component of Home Assistent now ported to
use pygattlib?

-- 
Happy hacking
Petter Reinholdtsen

Bug#969390: ddcci-dkms: ddcci detection fails with "invalid identification response"

[Marvin Gülker]

Hi,

Am Sonntag, dem 05. Juni 2022 schrieb Stephen Kitt:
> The driver works fine for me now on the current 5.10 kernel in Debian 11; do
> you still have this issue?

I do not use ddcci anymore, so I can't relate. Sorry.

  -quintus

Bug#1012318: diffoscope 214 produced no output and was killed after running into timeout after 150m

[Vagrant Cascadian]

On 2022-06-03, Vagrant Cascadian wrote:
> On 2022-06-04, Roman Lebedev wrote:
>> it would appear, diffoscope is failing when runing agains halide package:
>>
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/halide.html
>>
>> Unfortunately, i do not know what the more specific problem is.
...
> I'll see if I can find you some diffoscope output for halide by running
> it on a fairly powerful machine I have access to...

https://people.debian.org/~vagrant/reproducible/halide.diffoscope.out.zst

It's under 200MB download, expands to ~2GB uncompresed...


live well,
  vagrant


signature.asc
Description: PGP signature