Bug#961294: Allow derivatives to define parent project fields

2020-05-22 Thread Russ Allbery
Simon Quigley  writes:

> I recently had a discussion in a Lintian merge request[1] where I
> submitted code solidifying existing behavior in the Ubuntu Desktop and
> Lubuntu teams. As I stated there, it is common practice in those teams
> (and I am sure it exists in others as well) to specify a
> `XS-Debian-Vcs-Browser` and/or `XS-Debian-Vcs-Git` field to point to
> Salsa.

> The rationale for this is to allow packaging changes to flow back
> upstream to Debian when Ubuntu's packaging repository is in a different
> location (when Ubuntu has a permanent downstream delta but continues to
> rebase that delta on top of Debian's changes).

> I would like to solidify this existing practice by modifying Debian
> Policy, amending 5.6.26 to allow usage of -Vcs-Browser and
> -Vcs-.

I'm not sure I understand why you want to make this change to Debian
Policy.  Isn't this a matter for Ubuntu policy?  The new fields wouldn't
be in the package in Debian (because they wouldn't be meaningful there).

> I would also like to use this as an opportunity to deprecate
> `Original-Maintainer` in favor of `Debian-Maintainer` and allow for
> `Debian-Uploaders` as well.

Similarly this seems to be entirely a question for Ubuntu (and Lintian, of
course).

-- 
Russ Allbery (r...@debian.org)  



Bug#892308: Same problem on buster, kmail 5.9.3

2020-05-22 Thread Josep Guerrero
Hi,

I've found the same bug on two different Debian buster systems running kmail 
5.9.3, both of them upgraded from stretch, jessie, etc. In both of them a 
small square, similar to the screenshots provided by the original poster and 
showing what looks like a piece of some other window (web browser, terminal, 
etc.), appears at the bottom left of the list of messages. This square behaves 
as if it was part of the kmail window, moving with it and being repainted if 
covered by another window. The square seems to have no effect, other than the 
cosmetic.

Regards,

Josep



Bug#954290: kexec doesn't do reboots on systemd install?

2020-05-22 Thread Vasudev Kamath
Vasudev Kamath  writes:

> In our setup of Debian 9 we noticed many kernel panic which never crash
> dumped so was searching if there is something wrong in our setup and
> came across this bug. While looking at systemd I noticed there is a
> service called systemd-kexec.service which is disabled by default. Is
> this needs to be enabled for kexec to work correctly with systemd?
>
> If this service is needed may be should be enabled on installing
> kexec-tools?

May be I misunderstood relation between kdump-tools and kexec-tools. If
so please ignore above message :-). Was actually looking at [1] which
gave me a feeling that something is missing in my setup and wrote above
mail

[1] https://wiki.archlinux.org/index.php/Kdump

Cheers,
Vasudev



Bug#954290: kexec doesn't do reboots on systemd install?

2020-05-22 Thread Vasudev Kamath


In our setup of Debian 9 we noticed many kernel panic which never crash
dumped so was searching if there is something wrong in our setup and
came across this bug. While looking at systemd I noticed there is a
service called systemd-kexec.service which is disabled by default. Is
this needs to be enabled for kexec to work correctly with systemd?

If this service is needed may be should be enabled on installing
kexec-tools? 

Cheers,
Vasudev



Bug#961314: RFP: python3-s2sphere -- Python implementation of a part of the C++ S2 geometry library

2020-05-22 Thread Christoph Anton Mitterer
Package: wnpp
Severity: wishlist

* Package name: python3-s2sphere
  Version : 0.2.5
  Upstream Author : s...@sidewalklabs.com
* URL : https://github.com/sidewalklabs/s2sphere
* License : MIT
  Programming Lang: Python
  Description : Python implementation of a part of the C++ S2 geometry 
library

S2 is a library for spherical geometry that aims to have
the same robustness, flexibility, and performance as the very
best planar geometry libraries.



Bug#961313: pyspread: Fix example in package's tutorial?

2020-05-22 Thread Kingsley G. Morse Jr.
Package: pyspread
Version: 1.99.2-2
Severity: normal

Dear Andreas,

Thanks for pyspread.

I installed version 1.99.2-2.

I tried an example in its tutorial.

pyspread->Help->Tutorial says

"Select the top-left cell and type: python 1 + 5 * 2"

but when I type

python 1 + 5 * 2

in cell [0, 0, 0], pyspread complains with

"invalid syntax (, line1)"

I expected to see

11

So, I checked the documentation on line at

https://pyspread.gitlab.io/tutorial.html

It suggests typing

1 + 5 * 2

(no "python " ).

It works!

Yay!

Maybe the tutorial in debian's package should be
more like the Quick Start Tutorial online at

https://pyspread.gitlab.io/tutorial.html

Thanks,
Kingsley








*** 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: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages pyspread depends on:
ii  python3  3.7.5-1
ii  python3-numpy1:1.16.5-1
ii  python3-pyqt55.14.1+dfsg-2
ii  python3-pyqt5.qtsvg  5.14.1+dfsg-2
pn  python3:any  

Versions of packages pyspread recommends:
ii  python3-enchant 3.0.1-1
ii  python3-matplotlib  3.0.2-2

pyspread suggests no packages.

-- no debconf information



Bug#813111: Greetings and compliment of the Day.Have a happy day,

2020-05-22 Thread Mrs.Aisha
Greetings and compliment of the Day.

 May i  use this medium to open a mutual communication with you seeking
your acceptance towards investing in your country under your management as
my partner, My name is Aisha  Gaddafi and presently living in Oman, i am a
Widow and single Mother with three Children, the only biological Daughter
of late Libyan President (Late Colonel Muammar Gaddafi) and presently i am
under political asylum protection by the Oman Government.

I have funds worth "Twenty Seven Million Five Hundred Thousand United State
Dollars" -$27.500.000.00 US Dollars which i want to entrust on you for
investment project in your country.If you are willing to handle this
project on my behalf, kindly reply urgent to enable me provide you more
details to start the transfer process. is my intention to compensate you
with 30% of the total money for your services and the balance shall be my
capital in your establishment.

I shall appreciate your urgent response through my email address below:
aishamuammargaddaf...@gmail.com)Sorry for my pictures i will enclose it in
my next mail and more about me when i hear from you okay.


Best Regards
Have a happy day,
Mrs Aisha Gaddafi.


Bug#960448: openldap: Dynamically generate contact email

2020-05-22 Thread Ryan Tandy

Control: tag -1 pending

Fixed in git. Testing would be appreciated.



Bug#961312: savelog.8: minor formatting changes to the manual

2020-05-22 Thread Bjarni Ingi Gislason
Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

  Input file is savelog.8

Test nr. 2:

Enable and fix warnings from 'test-groff'.


Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z

  [ "test-groff" is a developmental version of "groff" ]

Input file is ./savelog.8

:71 (macro IR): only 1 argument, but more are expected



Test nr. 16:

Use the correct macro for the font change of a single argument.

71:.IR "file"

#

Test nr. 36:

Wrong distance between sentences or protect the indicator.

a) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) and "info groff".

 The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.


107:Save cycle versions of the logfile (default: 7). The
126:For xz no strength option is set, and xz decides on the default based on 
the total amount of physical RAM. Note that xz can use a very large amount of 
memory for the higher compression levels.
145:instead of . to roll files

#

Test nr. 37:

Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.

savelog.8: line 8   length 92
[\-J] [\-1\ .\|.\ \-9] [\-C] [\-d] [\-l] [\-r rolldir] [\-n] [\-q] [\-D 
dateformat] file ...

savelog.8: line 126 length 192
For xz no strength option is set, and xz decides on the default based on the 
total amount of physical RAM. Note that xz can use a very large amount of 
memory for the higher compression levels.


#

Test nr. 42:

Remove superfluous quotation marks (") from the argument of a
single-font macro.

54:.I "file"

#

Test nr. 59:

Protect a period (.) or a apostrophe (') with '\&' from becoming a
control character, if it could end up at the start of a line

145:instead of . to roll files

#

  Print constants in bold, not italic (e.g., "file.1")

#

  Add ".sp 1" to empty lines.

#

  Patch:

--- savelog.8   2019-12-07 02:13:44.0 +
+++ savelog.8.new   2020-05-23 02:21:53.0 +
@@ -5,7 +5,9 @@ savelog \- save a log file
 .SH SYNOPSIS
 .B savelog
 [\-m mode] [\-u user] [\-g group] [\-t] [\-p] [\-c cycle] [\-l] [\-j]
-[\-J] [\-1\ .\|.\ \-9] [\-C] [\-d] [\-l] [\-r rolldir] [\-n] [\-q] [\-D 
dateformat] file ...
+[\-J] [\-1\ .\|.\ \-9] [\-C] [\-d] [\-l] [\-r rolldir] [\-n] [\-q]
+[\-D dateformat] file ...
+.
 .SH DESCRIPTION
 The
 .B savelog
@@ -14,9 +16,9 @@ of
 .I file
 are named:
 .RS
-
-.IR "file" "." "" "" ""
-
+.sp 1
+.IR file "."  "" 
+.sp 1
 .RE
 where
 .I 
@@ -29,49 +31,49 @@ have
 opened for I/O.  Only
 .I cycle
 versions of the file are kept.
-
+.sp 1
 If the file does not exist and
 .B \-t
 was given, it will be created.
-
+.sp 1
 For files that do exist and have lengths greater than zero, the following
 actions are performed:
-
+.sp 1
 .IP 1)
 Version numbered files are cycled.  Version
-.IR "file" "." "2"
+.IB file \&.2
 is moved to version
-.IR "file" "." "3",
+.IB file \&.3 \fR,
 version
-.IR "file" "." "1"
+.IB file \&.1
 is moved to version
-.IR "file" "." "2",
+.IB file \&.2 \fR,
 and so on.  Finally version
-.IR "file" "." "0"
+.IB file \&.0
 is moved to version
-.IR "file" "." "1",
+.IB file \&.1 \fR,
 and version
-.I "file"
+.I file
 is deleted.  Both
 compressed names and uncompressed names are cycled, regardless of
 .BR \-l .
 Missing version files are ignored.
-
+.
 .IP 2)
 The new
-.IR "file" "." "1"
+.IB file \&.1
 is compressed unless the
 .B \-l
 flag was given.  It is changed subject to the
 .BR "\-m" ", " "\-u" ", and " "\-g"
 flags.
-
+.
 .IP 3)
 The main
-.IR "file"
+.I file
 is moved to
-.IR "file" "." "0".
-
+.IB file .0 \fR.
+.
 .IP 4)
 If the
 .BR "\-m" ", " "\-u" ", " "\-g" ",  " "\-t" ", or " "\-p"
@@ -81,14 +83,14 @@ is created subject to the given flags.
 .B \-p
 flag, the file is created with the same owner, group, and permissions as
 before.
-
+.
 .IP 5)
 The new
-.IR "file" "." "0"
+.IB file \&.0
 is changed subject to the
 .BR "\-m" ", " "\-u" ", and " "\-g"
 flags.
-
+.
 .SH OPTIONS
 .TP
 .B "\-m mode"
@@ -104,7 +106,8 @@ chgrp log files to group, implies
 .B \-t
 .TP
 .B "\-c cycle"
-Save cycle versions of the logfile (default: 7). The
+Save cycle versions of the logfile (default: 7).
+The
 .I cycle
 count must be at least 2.
 .TP
@@ -122,8 +125,12 @@ compress with bzip2 instead of gzip
 .TP
 .B \-J
 compress with xz instead of gzip
-
-For xz no strength option is set, and xz decides on the default based on the 
total amount of physical RAM. Note that xz can use a very large amount of 
memory for the higher compression levels.
+.sp 1
+For xz no strength option is set,
+and xz decides on the default based on the total amount of physical

Bug#960448: openldap: Dynamically generate contact email

2020-05-22 Thread Ryan Tandy

Control: tag -1 - patch

On Tue, May 12, 2020 at 02:36:39PM -0300, Andreas Hasenack wrote:

-+WHOWHERE="Debian OpenLDAP Maintainers 
"
++WHOWHERE="$(grep ^Maintainer: debian/control | sed 's,Maintainer: ,,')"


Now I remember that I actually did try this initially.

The mkversion script is called from different parts of the build tree 
(by recursive make) and doesn't have easy access to $(top_srcdir).


The patch you've suggested just leaves WHOWHERE empty.



Bug#960302: [Pkg-roundcube-maintainers] Bug#960302: imap retry must be tunable

2020-05-22 Thread Guilhem Mullion
Control: severity -1 important

Hi Sandro,

On Mon, 11 May 2020 at 18:34:06 +0200, Matus UHLAR - fantomas wrote:
> the imap retry patch added within bug 947320 locks my accounts when I enter
> invalid password.

Could you please have a look at this regression report?  You authored
the patch and my PHP-fu is failing me :-P  It should definitely not
retry the very same incorrect credentials.  Even on systems without
anti-bruteforce logic that locks the user out, Roundcube still takes 5
times longer to complain a about a failed login — which is not
negligible when an expensive PBKDF is used for credential verification.

I think it's rather unfortunate that 
debian/patches/retry_to_reach_imap_server.patch
was AFAICT never submitted upstream and landed into stable through -p-u.
I dunno whether program/lib/Roundcube/rcube_imap.php:connect() has
access to the IMAP state machine to determine whether a greeting was
seen (AFAICT your intention was to retry on missing greeting lines, not
on NO/BYE greeting conditions let alone failed authentication attempts)
or to another interface returning whether the error is transient or not.
Either way it'd be good to have upstream's blessing before adopting such
patches to Debian :-)

Thanks!
cheers
-- 
Guilhem.


signature.asc
Description: PGP signature


Bug#961311: ssh-agent.service: cannot work without x11-common installed

2020-05-22 Thread Paul Wise
Package: openssh-client
Version: 1:8.2p1-4
Severity: normal
File: /usr/lib/systemd/user/ssh-agent.service
Usertags: wayland

On pure-Wayland systems, the ssh-agent.service is not going to be able
to start because x11-common won't nessecarily be installed. I think
either the ConditionPathExists should get dropped and the script should
check if the Xsession.options file exists before using it, when it
doesn't exist people using Wayland without x11-common installed can just use 
`systemctl --user mask/enable/disable` to manage the service.

PS: shellcheck reports some issues for the agent-launch script.

$ systemctl --user cat ssh-agent.service 
# /usr/lib/systemd/user/ssh-agent.service
[Unit]
Description=OpenSSH Agent
Documentation=man:ssh-agent(1)
Before=graphical-session-pre.target
ConditionPathExists=/etc/X11/Xsession.options
Wants=dbus.socket
After=dbus.socket

[Service]
ExecStart=/usr/lib/openssh/agent-launch start
ExecStopPost=/usr/lib/openssh/agent-launch stop

$ dpkg -S /etc/X11/Xsession.options
x11-common: /etc/X11/Xsession.options

$ grep -A4 /etc/X11/Xsession.options /usr/lib/openssh/agent-launch
if [ -z "$SSH_AUTH_SOCK" ] && grep -s -q '^use-ssh-agent$' 
/etc/X11/Xsession.options; then
S="$XDG_RUNTIME_DIR/openssh_agent"
dbus-update-activation-environment --verbose --systemd SSH_AUTH_SOCK=$S 
SSH_AGENT_LAUNCHER=openssh
exec ssh-agent -D -a $S
fi

$ shellcheck /usr/lib/openssh/agent-launch 

In /usr/lib/openssh/agent-launch line 6:
echo 'This needs $XDG_RUNTIME_DIR to be set' >&2
 ^-- SC2016: Expressions don't expand in single quotes, use double 
quotes for that.


In /usr/lib/openssh/agent-launch line 13:
dbus-update-activation-environment --verbose --systemd SSH_AUTH_SOCK=$S 
SSH_AGENT_LAUNCHER=openssh
 
^-- SC2086: Double quote to prevent globbing and word splitting.

Did you mean: 
dbus-update-activation-environment --verbose --systemd 
SSH_AUTH_SOCK="$S" SSH_AGENT_LAUNCHER=openssh


In /usr/lib/openssh/agent-launch line 14:
exec ssh-agent -D -a $S
 ^-- SC2086: Double quote to prevent globbing and 
word splitting.

Did you mean: 
exec ssh-agent -D -a "$S"

For more information:
  https://www.shellcheck.net/wiki/SC2016 -- Expressions don't expand in singl...
  https://www.shellcheck.net/wiki/SC2086 -- Double quote to prevent globbing ...


-- System Information:
Debian Release: bullseye/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.6.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openssh-client depends on:
ii  adduser   3.118
ii  dpkg  1.19.7
ii  libc6 2.30-8
ii  libedit2  3.1-20191231-1
ii  libfido2-11.4.0-1
ii  libgssapi-krb5-2  1.17-7
ii  libselinux1   3.0-1+b3
ii  libssl1.1 1.1.1g-1
ii  passwd1:4.8.1-1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages openssh-client recommends:
ii  xauth  1:1.0.10-1

Versions of packages openssh-client suggests:
pn  keychain 
pn  libpam-ssh   
ii  monkeysphere 0.43-3
ii  ssh-askpass-gnome [ssh-askpass]  1:8.2p1-4

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#960390: x86_64: No serial port output

2020-05-22 Thread Punit Agrawal
On Sat, May 23, 2020 at 1:54 AM Steve McIntyre  wrote:
>
> On Sat, May 23, 2020 at 01:15:37AM +0900, Punit Agrawal wrote:

[...]

> >To avoid needing any workarounds such as those discussed in earlier
> >replies, I looked at enabling the installer images to output on the
> >serial console by default. The attached simple change to the grub
> >configuration gives output on serial as well as connected monitor.
> >
> >The next issue that needs fixing is to update the kernel command line
> >to launch the installer on the serial console.
>
> I think few people have been bothered by this in the past - all the
> server machines I've used for years have had options for redirecting a
> VGA console to the serial port. Do you have one that doesn't?

Actually, I was installing in "-nographic" VM rather than a server.
There are workarounds that allow me to continue earlier in the thread
(See #67, #68) but I was hoping to improve things so that it just
works.

I was just surprised that it isn't possible to use the installer
without a VGA monitor (or a redirect on hardware that supports it) -
especially coming from arm64. There are a few other use cases that
will benefit from the serial support as well.

Considering that it looks to be a configuration issue - do you think
it's worth enabling? Are there any downsides that I am missing?



Bug#961310: remove-shell.8: reformat the manual's source

2020-05-22 Thread Bjarni Ingi Gislason
Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

  Input file is remove-shell.8

Test nr. 21:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes the "\/" part.

  Or

add the italic corrections.
[1] man-pages(7)

10:operates on the temporary files \fI/etc/shells.tmp\fR and
11:\fI/etc/shells.tmp2\fR to remove the given shells from the list of valid
12:login shells, and copy the result back to \fI/etc/shells\fR.

#

  Reformat sentences.



  Patch:

--- remove-shell.8  2019-12-07 02:13:44.0 +
+++ remove-shell.8.new  2020-05-23 01:02:47.0 +
@@ -2,13 +2,17 @@
 .SH NAME
 remove-shell \- remove shells from the list of valid login shells
 .SH SYNOPSIS
-.B  remove-shell
-.I  shellname
+.B remove-shell
+.I shellname
 .RI [ shellname ...]
 .SH DESCRIPTION
 .B remove-shell
-operates on the temporary files \fI/etc/shells.tmp\fR and
-\fI/etc/shells.tmp2\fR to remove the given shells from the list of valid
-login shells, and copy the result back to \fI/etc/shells\fR.
-.SH "SEE ALSO"
+operates on the temporary files
+.I /etc/shells.tmp
+and
+.I /etc/shells.tmp2
+to remove the given shells from the list of valid login shells,
+and copy the result back to
+.IR /etc/shells .
+.SH SEE ALSO
 .BR shells (5)



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

Kernel: Linux 5.6.14-1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debianutils depends on:
ii  libc6  2.30-8

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason



Bug#961146: systemd-logind sometimes ignores a systemd-inhibit lock

2020-05-22 Thread Vincent Lefevre
On 2020-05-22 23:53:58 +0200, Michael Biebl wrote:
> This is strange. Something is triggering the start of systemd-logind

What do you mean by "start of systemd-logind"?

On my machine, systemd-logind is started early at boot time and
never quits.

> (via D-Bus most likely). My educated guess is, that it is actually this
> process, which triggers the suspend, not logind itself.

But if the lid is not closed when I change the VT, the system
is not suspended.

And if I'm on a VT that is different from the one where
systemd-inhibit has been run and I close the lid, the system
is suspended.

> Remember when I initially said, that logind provides the mechanism and
> the policy is supposed to be proved by something else (usually the
> desktop environment).

A part of the policy is in logind, isn't it? I mean that
/etc/systemd/logind.conf has an option "HandleLidSwitch",
which I haven't modify, so that it is the default "suspend".
The suspend is just supposed to be blocked by an inhibitor,
which is also part of logind.

Note also that when I did the test, there was no desktop environment,
no X server, just 2 VTs involved. Which part of the system is in
charge of the VTs, then?

If I understand correctly, the suspend is done via the call of
manager_handle_action() in "login/logind-action.c". It would
be interesting to know the values of m and inhibit_key. But
according to what is logged, it seems that the call can only
be done via

manager_handle_action(manager, INHIBIT_HANDLE_LID_SWITCH, 
handle_action, manager->lid_switch_ignore_inhibited, is_edge);

in button_lid_switch_handle_action(); otherwise I would have
got another message before "Suspending...". So inhibit_key
would have the expected value. But I'm wondering about
manager; if it is not constant, this seems to be wrong
(as the inhibitors are associated with it).

Then, concerning button_lid_switch_handle_action(), there are
2 calls:

1. From button_recheck(), and it seems that this is what is called
   when I change the VT while the lid is already closed.

2. From button_dispatch(). The button_lid_switch_handle_action()
   call is preceded by "Lid closed.", which is what I get when
   I close the lid. And if I'm on a "wrong" VT, the system will
   be suspended.

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



Bug#961309: installkernel.8: minor reformatting of the manual's source

2020-05-22 Thread Bjarni Ingi Gislason
Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

  Input file is installkernel.8

chk_man: Next line: execute mandoc -T lint installkernel.8

mandoc: installkernel.8:16:19: STYLE: whitespace at end of input line
mandoc: installkernel.8:7:2: WARNING: skipping paragraph macro: PP after SH

###

  Reformat sentences.

#

  Patch:

--- installkernel.8 2019-12-07 02:13:44.0 +
+++ installkernel.8.new 2020-05-23 00:40:44.0 +
@@ -4,22 +4,26 @@ installkernel \- install a new kernel im
 .SH SYNOPSIS
 .BI "installkernel " "version zImage System.map [directory]"
 .SH DESCRIPTION
-.PP
 .B installkernel
 installs a new kernel image onto the system from the Linux source
-tree.  It is called by the Linux kernel makefiles when
+tree.
+It is called by the Linux kernel makefiles when
 .B make install
 is invoked there.
 .P
 The new kernel is installed into
 .IR {directory}/vmlinuz-{version} .
-If a symbolic link 
+If a symbolic link
 .I {directory}/vmlinuz
-already exists, it is refreshed by making a link from
+already exists,
+it is refreshed by making a link from
 .I {directory}/vmlinuz
-to the new kernel, and the previously installed kernel is available as
+to the new kernel,
+and the previously installed kernel is available as
 .IR {directory}/vmlinuz.old .
 .SH BUGS
-installkernel resides in /sbin only because the Linux kernel makefiles
-call it from there.  It should really be in /usr/sbin.  It isn't
-needed to boot a system.
+.B installkernel
+resides in /sbin only because the Linux kernel makefiles call it from
+there.
+It should really be in /usr/sbin.
+It isn't needed to boot a system.



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

Kernel: Linux 5.6.14-1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debianutils depends on:
ii  libc6  2.30-8

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason



Bug#961308: add-shell.8: Minor reformatting of the manual's source

2020-05-22 Thread Bjarni Ingi Gislason
Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

  Input file is add-shell.8

Test nr. 21:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes the "\/" part.

  Or

add the italic corrections.
[1] man-pages(7)

10:copies \fI/etc/shells\fR to \fI/etc/shells.tmp\fR, adds the given shells to
12:back to \fI/etc/shells\fR.

#

  Reformat some sentences.



  Use ".sp 1" instead of an empty line.



  Patch:

--- add-shell.8 2019-12-07 02:13:44.0 +
+++ add-shell.8.new 2020-05-23 00:21:13.0 +
@@ -7,10 +7,15 @@ add-shell \- add shells to the list of v
 .RI [ shellname ...]
 .SH DESCRIPTION
 .B add-shell
-copies \fI/etc/shells\fR to \fI/etc/shells.tmp\fR, adds the given shells to
-this file if they are not already present, and copies this temporary file
-back to \fI/etc/shells\fR.
-
+copies
+.I /etc/shells
+to
+.IR /etc/shells.tmp ,
+adds the given shells to this file
+if they are not already present,
+and copies this temporary file back to
+.IR /etc/shells .
+.sp 1
 The shells must be provided by their full pathnames.
-.SH "SEE ALSO"
+.SH SEE ALSO
 .BR shells (5)


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

Kernel: Linux 5.6.14-1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debianutils depends on:
ii  libc6  2.30-8

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason



Bug#961215: blueman-manager no longer starts because blueman-applet.service not found

2020-05-22 Thread Michael Stone

On Sat, May 23, 2020 at 02:08:47AM +0200, Tomasz Nitecki wrote:

Hey,

This issue seems to be caused by changes made in #950520 [1].

I've described the problem in more detail in that bug report [1]. To cut
long story short, this bug (#961215) seems to be affecting non /usr
merged systems.


Yeah, the "fix" was obviously incorrect.



Bug#961215: blueman-manager no longer starts because blueman-applet.service not found

2020-05-22 Thread Michael Stone
More specifically, refer to systemd.unit(5) and you'll find that 
/lib/systemd/user is not defined.




Bug#961307: Screen rotation keybinding only works on internal display, not external display

2020-05-22 Thread Josh Triplett
Package: gnome-settings-daemon
Version: 3.36.1-1
Severity: normal

Steps to reproduce (on a laptop, with an external display available):

Bind a key to rotate the screen:

gsettings set org.gnome.mutter.keybindings rotate-monitor 
"['XF86RotateWindows', 'r']"

With the internal display active, hit that rotation key repeatedly.
Watch the internal display rotate each time you hit it.

Switch to the external display (disabling the internal display).

Hit the rotation key repeatedly again. The external display remains
unaffected.

- Josh Triplett

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

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

Versions of packages gnome-settings-daemon depends on:
ii  gnome-settings-daemon-common  3.36.1-1
ii  gsettings-desktop-schemas 3.36.1-1
ii  libasound21.2.2-2.1
ii  libc6 2.30-8
ii  libcairo2 1.16.0-4
ii  libcanberra-gtk3-00.30-7
ii  libcanberra0  0.30-7
ii  libcolord21.4.4-2
ii  libcups2  2.3.3-1
ii  libfontconfig12.13.1-4.2
ii  libgcr-base-3-1   3.36.0-2
ii  libgdk-pixbuf2.0-02.40.0+dfsg-4
ii  libgeoclue-2-02.5.6-1
ii  libgeocode-glib0  3.26.2-2
ii  libglib2.0-0  2.64.2-1
ii  libgnome-desktop-3-19 3.36.2-1
ii  libgtk-3-03.24.20-1
ii  libgudev-1.0-0233-1
ii  libgweather-3-16  3.36.0-1
ii  liblcms2-22.9-4+b1
ii  libmm-glib0   1.12.8-1.1
ii  libnm01.24.0-1
ii  libnotify40.7.9-1
ii  libnspr4  2:4.25-1
ii  libnss3   2:3.52-1
ii  libpam-systemd [logind]   245.5-3
ii  libpango-1.0-01.44.7-4
ii  libpangocairo-1.0-0   1.44.7-4
ii  libpolkit-gobject-1-0 0.105-26
ii  libpulse-mainloop-glib0   13.0-5
ii  libpulse0 13.0-5
ii  libupower-glib3   0.99.11-2
ii  libwacom2 1.3-2
ii  libwayland-client01.18.0-1
ii  libx11-6  2:1.6.9-2+b1
ii  libxext6  2:1.3.3-1+b2
ii  libxi62:1.7.9-1

Versions of packages gnome-settings-daemon recommends:
pn  iio-sensor-proxy   
ii  pulseaudio 13.0-5
ii  x11-xserver-utils  7.7+8

Versions of packages gnome-settings-daemon suggests:
pn  usbguard  

-- no debconf information



Bug#950520: blueman: Ship blueman-mechanism.service under /lib/systemd/system

2020-05-22 Thread Tomasz Nitecki
Control: reopen 950520
Control: block 961215 by 950520

Hey,

I'm not sure if moving '/usr/lib/systemd/user/blueman-applet.service' to
'/lib/systemd/user/blueman-applet.service' is the correct solution here.

According to the systemd.unit(5) man [1], the user unit search path
contains '/usr/lib/systemd/user/*' but it doesn't contain
'/lib/systemd/user/*'. On /usr merged systems it will work (thanks to
the symlinked /lib), however it will break non /usr merged systems, as
evidenced by #961215 [2].

It is worth noting, that according to the manual, '/lib/systemd/system'
seems to be correct location for 'shipped blueman-mechanism.service' (as
'/lib/systemd/system/*' is in system unit search path, while
'/usr/lib/systemd/system/' is not).


Regards,
T.

[1] https://manpages.debian.org/stretch/systemd/systemd.unit.5.en.html
[2] https://bugs.debian.org/961215



signature.asc
Description: OpenPGP digital signature


Bug#961215: blueman-manager no longer starts because blueman-applet.service not found

2020-05-22 Thread Tomasz Nitecki
Hey,

This issue seems to be caused by changes made in #950520 [1].

I've described the problem in more detail in that bug report [1]. To cut
long story short, this bug (#961215) seems to be affecting non /usr
merged systems.

Just a warning - if you copy 'blueman-applet.service' from
'/lib/systemd/user' to '/usr/lib/systemd/user' and then run usrmerge, it
will fail (you'll have to remove that copy you made, to fix it).


Regards,
T.

[1] https://bugs.debian.org/950520



signature.asc
Description: OpenPGP digital signature


Bug#961306: which.1: Minor reformatting of the source

2020-05-22 Thread Bjarni Ingi Gislason
Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

  Input file is which.1

Test nr. 36:

Wrong distance between sentences.

a) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) and "info groff".

 The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.


12:PATH for executable files matching the names of the arguments. It does

#

  Patch:

--- which.1 2019-12-07 02:13:44.0 +
+++ which.1.new 2020-05-23 00:04:58.0 +
@@ -7,10 +7,12 @@ which [\-a] filename ...
 .SH DESCRIPTION
 .B which
 returns the pathnames of the files (or links) which would be executed
-in the current environment, had its arguments been given as commands
-in a strictly POSIX-conformant shell.  It does this by searching the
-PATH for executable files matching the names of the arguments. It does
-not canonicalize path names.
+in the current environment,
+had its arguments been given as commands in a strictly
+POSIX-conformant shell.
+It does this by searching the PATH for executable files matching the
+names of the arguments.
+It does not canonicalize path names.
 .SH OPTIONS
 .TP
 .B \-a


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

Kernel: Linux 5.6.14-1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debianutils depends on:
ii  libc6  2.30-8

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason



Bug#961235: RFS: austin/1.0.1-1 -- Frame stack sampler for CPython

2020-05-22 Thread Gabriele
Oh dear. I didn't spot that one! Thanks for reporting this, I have
uploaded a new version with the amended manpage.

Cheers,
Gabriele

On Fri, 22 May 2020 at 23:47, Adam Borowski  wrote:
>
> On Thu, May 21, 2020 at 08:26:40PM +0100, Gabriele wrote:
> >  * Package name: austin
> >Version : 1.0.1-1
>
> > Changes since the last upload:
> >
> >* Fixed support for Python 3.8
>
> Fails to build:
>dh_installman -O--buildsystem=autoconf
> dh_installman: warning: Section for ./debian/austin.1 is computed as "16", 
> which is not a valid section
> dh_installman: error: Could not determine section for ./debian/austin.1
> dh_installman: error: Aborting due to earlier error
>
>
> Meow!
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
> ⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
> ⠈⠳⣄



-- 
"Egli è scritto in lingua matematica, e i caratteri son triangoli,
cerchi, ed altre figure
geometriche, senza i quali mezzi è impossibile a intenderne umanamente parola;
senza questi è un aggirarsi vanamente per un oscuro laberinto."

-- G. Galilei, Il saggiatore.



Bug#961305: tempfile.1: Minor fixes in the manual

2020-05-22 Thread Bjarni Ingi Gislason
Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

  Details:

Input file is tempfile.1

chk_man: Next line: execute mandoc -T lint tempfile.1

mandoc: tempfile.1:10:2: WARNING: skipping paragraph macro: PP after SH

###

Input file is tempfile.1

Test nr. 2:

Enable and fix warnings from 'test-groff'.


Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z

  [ "test-groff" is a developmental version of "groff" ]

Input file is ./tempfile.1

:40 (macro IR): only 1 argument, but more are expected
an-end-check:: Warning: Different number of .RS and .RE calls, 
an-RS-open=1 at end of file



Test nr. 25:

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

44:.BI "-d, --directory " DIR
47:.BI "-m, --mode " MODE
50:.BI "-n, --name " FILE
53:The options -d, -p, and -s are ignored if this option is given.
55:.BI "-p, --prefix " STRING
58:.BI "-s, --suffix " STRING
61:.B "--help"
64:.B "--version"
80:trap "rm -f -- '$t'" EXIT
82:rm -f -- "$t"

#

Test nr. 37:

Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.

tempfile.1: line 8  length 96
[\-\-prefix=STRING] [\-\-suffix=STRING] [\-\-mode=MODE] [\-\-name=FILE] 
[\-\-help] [\-\-version]


#

Test nr. 42:

Remove superfluous quotation marks (") from the argument of a
single-font macro.

61:.B "--help"
64:.B "--version"

#

Test nr. 48:

The name of a man page is set in bold and the section in roman (see
man-pages(7).

72:tempfile is deprecated; you should use mktemp(1) instead.

#

Test nr. 59:

Protect a period (.) or a apostrophe (') with '\&' from becoming a
control character, if it could end up at the start of a line

80:trap "rm -f -- '$t'" EXIT

#

  Patch:

--- tempfile.1  2019-12-07 02:13:44.0 +
+++ tempfile.1.new  2020-05-22 23:42:13.0 +
@@ -5,9 +5,9 @@ tempfile \- create a temporary file in a
 .SH SYNOPSIS
 .B tempfile
 [\-d DIR] [\-p STRING] [\-s STRING] [\-m MODE] [\-n FILE] [\-\-directory=DIR]
-[\-\-prefix=STRING] [\-\-suffix=STRING] [\-\-mode=MODE] [\-\-name=FILE] 
[\-\-help] [\-\-version]
+[\-\-prefix=STRING] [\-\-suffix=STRING] [\-\-mode=MODE]
+[\-\-name=FILE] [\-\-help] [\-\-version]
 .SH DESCRIPTION
-.PP
 .B tempfile
 creates a temporary file in a safe manner.  It uses
 .BR mkstemps (3)
@@ -37,31 +37,31 @@ is used when appropriate.
 .TP
 d)
 Finally an implementation-defined directory
-.IR (/tmp)
+.RI ( /tmp )
 may be used.
 .SH OPTIONS
 .TP
-.BI "-d, --directory " DIR
+.BI "\-d, \-\-directory " DIR
 Place the file in DIR.
 .TP
-.BI "-m, --mode " MODE
+.BI "\-m, \-\-mode " MODE
 Open the file with MODE instead of 0600.
 .TP
-.BI "-n, --name " FILE
+.BI "\-n, \-\-name " FILE
 Use FILE for the name instead of
 .BR tempnam (3) .
-The options -d, -p, and -s are ignored if this option is given.
+The options \-d, \-p, and \-s are ignored if this option is given.
 .TP
-.BI "-p, --prefix " STRING
+.BI "\-p, \-\-prefix " STRING
 Use up to five letters of STRING to generate the name.
 .TP
-.BI "-s, --suffix " STRING
+.BI "\-s, \-\-suffix " STRING
 Generate the file with STRING as the suffix.
 .TP
-.B "--help"
+.B \-\-help
 Print a usage message on standard output and exit successfully.
 .TP
-.B "--version"
+.B \-\-version
 Print version information on standard output and exit successfully.
 .SH RETURN VALUES
 An exit status of 0 means the temporary file was created successfully.
@@ -69,20 +69,20 @@ Any other exit status indicates an error
 .SH BUGS
 Exclusive creation is not guaranteed when creating files on NFS
 partitions.  tempfile cannot make temporary directories.
-tempfile is deprecated; you should use mktemp(1) instead.
+tempfile is deprecated; you should use
+.BR mktemp (1)
+instead.
 .SH EXAMPLE
-
-.RS
 .nf
 #!/bin/sh
 #[...]
 t=$(tempfile) || exit
-trap "rm -f -- '$t'" EXIT
+trap "rm \-f \-\- '$t'" EXIT
 #[...]
-rm -f -- "$t"
+rm \-f \-\- "$t"
 trap - EXIT
 exit
 .fi
-.SH "SEE ALSO"
+.SH SEE ALSO
 .BR tempnam (3),
 .BR mktemp (1)


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

Kernel: Linux 5.6.14-1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debianutils depends on:
ii  libc6  2.30-8

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason



Bug#961303: Please add an entry for Turris MOX

2020-05-22 Thread Domenico Andreoli
Package: flash-kernel
Version: 3.100
Severity: wishlist
Tags: patch

Dear Maintainer,

  please add the new entry for supporting Turris MOX [0]. Patch is
attached but also MR is available on Salsa:

https://salsa.debian.org/installer-team/flash-kernel/merge_requests/20

This is the entry:

+Machine: CZ.NIC Turris Mox Board
+Kernel-Flavors: arm64
+Boot-Script-Path: /boot/boot.scr
+DTB-Id: marvell/armada-3720-turris-mox.dtb
+U-Boot-Script-Name: bootscr.uboot-generic
+Required-Packages: u-boot-tools
+

I tested it as local override in /etc/flash-kernel/db on a manually
booted Turris MOX after a Bullseye Alpha 2 install, for which only
minor dts tweaks are needed.

Regards,
Domenico

[0] https://www.turris.cz/en/mox/overview/

-- 
rsa4096: 3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA  356E CC79 2832 ED38 CB05



Bug#961304: ischroot.1: Minor fixes to the manual

2020-05-22 Thread Bjarni Ingi Gislason
Package: debianutils
Version: 4.9.1
Severity: minor
Tags: patch

Dear Maintainer,

Input file is ischroot.1

  Details:

chk_man: Next line: execute mandoc -T lint ischroot.1

mandoc: ischroot.1:9:2: WARNING: skipping paragraph macro: PP after SH

###

Test nr. 2:

Enable and fix warnings from 'test-groff'.


Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z

  [ "test-groff" is a developmental version of "groff" ]

Input file is ./ischroot.1

troff: backtrace: '/home/bg/git/groff/build/s-tmac/an-old.tmac':278: macro 'B'
troff: backtrace: file '':24
troff: :24: warning: trailing space
troff: backtrace: '/home/bg/git/groff/build/s-tmac/an-old.tmac':278: macro 'B'
troff: backtrace: file '':27
troff: :27: warning: trailing space


Test nr. 25:

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

24:.B "-f, --default-false "
27:.B "-t, --default-true "
30:.B "--help"
33:.B "--version"

#

Test nr. 36:

Wrong distance between sentences or protect the indicator.

a) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) and "info groff".

 The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.


11:detects if it is currently running in a chroot. The exit status is:
36:On GNU/Linux, chroot detection is not possible when not root. This

#

Test nr. 42:

Remove superfluous quotation marks (") from the argument of a
single-font macro.

30:.B "--help"
33:.B "--version"

#

  Patch:

--- ischroot.1  2019-12-07 02:13:44.0 +
+++ ischroot.1.new  2020-05-22 23:25:54.0 +
@@ -6,9 +6,9 @@ ischroot \- detect if running in a chroo
 .B ischroot
 [\-\-default\-false] [\-\-default\-true] [\-\-help] [\-\-version]
 .SH DESCRIPTION
-.PP
 .B ischroot
-detects if it is currently running in a chroot. The exit status is:
+detects if it is currently running in a chroot.
+The exit status is:
 .TP
 0
 if currently running in a chroot
@@ -21,17 +21,18 @@ if the detection is not possible (On GNU
 script is not run as root).
 .SH OPTIONS
 .TP
-.B "-f, --default-false "
+.B \-f, \-\-default\-false
 Exit with status 1 if the detection is not possible.
 .TP
-.B "-t, --default-true "
+.B \-t, \-\-default\-true
 Exit with status 0 if the detection is not possible.
 .TP
-.B "--help"
+.B \-\-help
 Print a usage message on standard output and exit successfully.
 .TP
-.B "--version"
+.B \-\-version
 Print version information on standard output and exit successfully.
 .SH BUGS
-On GNU/Linux, chroot detection is not possible when not root. This
+On GNU/Linux, chroot detection is not possible when not root.
+This
 works correctly on GNU/Hurd and GNU/kFreeBSD.


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

Kernel: Linux 5.6.14-1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debianutils depends on:
ii  libc6  2.30-8

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason



Bug#959561: guile-ssh: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2

2020-05-22 Thread Vagrant Cascadian
On 2020-05-03, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
>> make[5]: Entering directory '/<>/tests'
...
>> FAIL: dist.scm
>> 
>>Guile-SSH 0.11.3: tests/test-suite.log
>> 
>> 
>> # TOTAL: 11
>> # PASS:  10
>> # SKIP:  0
>> # XFAIL: 0
>> # FAIL:  1
>> # XPASS: 0
>> # ERROR: 0
>> 
>> .. contents:: :depth: 2
>> 
>> FAIL: dist
>> ==
>> 
>>  Starting test dist  (Writing full log to "dist.log")
>> 
>> Some deprecated features have been used.  Set the environment
>> variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
>> program to get more information.  Set it to "no" to suppress
>> this message.
>>  Starting test dist  (Writing full log to "dist.log")
>> tests/dist.scm:216: FAIL with-ssh
>> # of expected passes  18
>> # of unexpected failures  1
...
>> Test begin:
>>   test-name: "with-ssh"
>>   source-file: "tests/dist.scm"
>>   source-line: 216
>>   source-form: (test-assert "with-ssh" (begin (set-log-userdata! "with-ssh") 
>> (run-client-test (lambda (server) (server-listen server) (server-set! server 
>> (quote log-verbosity) (quote functions)) (let ((session (server-accept 
>> server))) (server-handle-key-exchange session) (start-session-loop session 
>> (lambda (msg type) (format-log/scm (quote nolog) "server" "msg: ~a; type: 
>> ~a" msg type) (case (car type) ((request-channel-open) (let ((c 
>> (message-channel-request-open-reply-accept msg))) (format-log/scm (quote 
>> nolog) "server" "channel 0: ~a" c) (write-line "Enter `,help' for help." c) 
>> (format-log/scm (quote nolog) "server" "channel 1: ~a" c) (usleep 100) (poll 
>> c (lambda args (let ((result (read-line c))) (format-log/scm (quote nolog) 
>> "server" "sexp: ~a" result) (or (string=? result "(begin (+ 21 21))") (error 
>> "Wrong result 1" result))) (let ((result (read-line c))) (format-log/scm 
>> (quote nolog) "server" "sexp: ~a" result) (or (string=? result "(newline)") 
>> (error "Wrong result 2" result))) (write-line "scheme@(guile-user)> $1 = 
>> 42\n" c) (sleep 5) (close c) (while #t (sleep 60)) (else 
>> (message-reply-success msg))) (lambda () (call-with-connected-session 
>> (lambda (session) (authenticate-server session) (format-log/scm (quote 
>> nolog) "client" "session: ~a" session) (unless (equal? (userauth-none! 
>> session) (quote success)) (error "Could not authenticate with a server" 
>> session)) (let ((n (make-node session #:start-repl-server? #f))) (= 
>> (with-ssh n (+ 21 21)) 42
>> result) (or (string=? result "(newline)") (error "Wrong result 2" result))) 
>> (write-line "scheme@(guile-user)> $1 = 42\n" c) (sleep 5) (close c) (while 
>> #t (sleep 60)) (else (message-reply-success msg))) (lambda () 
>> (call-with-connected-session (lambda (session) (authenticate-server session) 
>> (format-log/scm (quote nolog) "client" "session: ~a" session) (unless 
>> (equal? (userauth-none! session) (quote success)) (error "Could not 
>> authenticate with a server" session)) (let ((n (make-node session 
>> #:start-repl-server? #f))) (= (with-ssh n (+ 21 21)) 42
>> Test end:
>>   result-kind: fail
>>   actual-value: #f
>>   actual-error: (guile-ssh-error "read_from_channel_port" "Error reading 
>> from the channel" # #f)
>> Group end: dist
>> # of expected passes  18
>> # of unexpected failures  1
>> FAIL dist.scm (exit status: 1)
...
> The full build log is available from:
>http://qa-logs.debian.net/2020/05/01/guile-ssh_0.11.3-2_unstable.log
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

I can't reproduce this issue on amd64 or arm64, with versions 0.11.3-2
(sid/bullseye) or 0.12.0-1 (experimental). Both versions also built fine
on the buildd's, originally...

Reading the above mentioned wiki page, I tried building without network
to ensure it wasn't somehow trying to ssh over the network, but the
tests passed. How is network disabled in your tests?

According to https://tests.reproducible-builds.org/debian/guile-ssh,
amd64 and arm64 have failures, but they appear to be different tests
entirely.


> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot.

All my tests were also on updated, clean, minimal chroots... is there
anything unusual with your test setup not mentioned on the FAQ?


> Every failed build was retried once to eliminate random failures.

Did the retried build fail in the same way vs. just testing that it
failed twice?


Thanks for all your QA work!


live well,
  vagrant


signature.asc
Description: PGP signature


Bug#961028: hplip: No scanner found: SANE cannot load the hpaio backend

2020-05-22 Thread gpe92
Package: hplip
Version: 3.20.5+dfsg0-2
Followup-For: Bug #961028

Same problem for me with an Envy 7640.

BR

-- Package-specific info:
Saving output in log file: /home/gpe/hp-check.log

HP Linux Imaging and Printing System (ver. 3.20.5)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling the
HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies
are installed to successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball   
has the proper dependencies installed to successfully run.  
3. Both compile- and run-time check mode (-b or --both) (Default): This mode
will check both of the above cases (both compile- and run-time dependencies).   

Check types:
a. EXTERNALDEP - External Dependencies  
b. GENERALDEP - General Dependencies (required both at compile and run time)
c. COMPILEDEP - Compile time Dependencies   
d. [All are run-time checks]
PYEXT SCANCONF QUEUES PERMISSION

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

warning: debian-testing version is not supported. Using debian-10.3 versions 
dependencies to verify and install...

---
| SYSTEM INFO |
---

 Kernel: 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) GNU/Linux
 Host: reveillon
 Proc: 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) GNU/Linux
 Distribution: debian testing
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.20.5
HPLIP-Home: /usr/share/hplip
warning: HPLIP-Installation: Auto installation is not supported for debian 
distro  testing version 

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.20.5

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/hplip/HP
ppdbase=/usr/share/ppd/hplip
doc=/usr/share/doc/hplip
html=/usr/share/doc/hplip-doc
icon=no
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=no
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=yes
foomatic-drv-install=yes
foomatic-ppd-install=no
foomatic-rip-hplip-install=no
hpcups-install=yes
cups-drv-install=yes
cups-ppd-install=no
internal-tag=3.20.5
restricted-build=no
ui-toolkit=qt5
qt3=no
qt4=no
qt5=yes
policy-kit=yes
lite-build=no
udev_sysfs_rules=no
hpcups-only-build=no
hpijs-only-build=no
apparmor_build=no
class-driver=no


Current contents of '/var/lib/hp/hplip.state' file:
Plugins are not installed. Could not access file: No such file or directory

Current contents of '~/.hplip/hplip.conf' file:
[commands]
scan = /usr/bin/simple-scan %SANE_URI%

[fax]
email_address = 
voice_phone = 

[installation]
date_time = 05/23/20 01:26:22
version = 3.20.5

[last_used]
device_uri = "hp:/net/ENVY_7640_series?ip=192.168.1.4"
printer_name = ENVY_7640
working_dir = .

[polling]
device_list = 
enable = false
interval = 5

[refresh]
enable = true
rate = 30
type = 2

[settings]
systray_messages = 0
systray_visible = 0

[upgrade]
last_upgraded_time = 1424993732
latest_available_version = 3.15.11
notify_upgrade = false
pending_upgrade_time = 0


 


-
| External Dependencies |
-

 error: cups  CUPS - Common Unix Printing System
   REQUIRED1.1 -   INCOMPAT   'CUPS may not be 
installed or not running'
 gs   GhostScript - PostScript and PDF language interpreter and 
previewer REQUIRED7.059.52OK -
 xsanexsane - Graphical scanner frontend for SANE   
   OPTIONAL0.9 0.999   OK -
 scanimagescanimage - Shell scanning program
   OPTIONAL1.0 1.0.27  OK -
 dbus DBus - Message bus system 
   REQUIRED  

Bug#612804: Fwd:

2020-05-22 Thread Clara Petrea
 Have you receive my first message I sent to you yesterday


Bug#955834: enchant: unnecessarily Build-Depends on deprecated dbus-glib

2020-05-22 Thread Boyuan Yang
X-Debbugs-CC: haya...@clear-code.com

On Sat, 9 May 2020 20:08:50 +0900 Kentaro Hayashi <
haya...@clear-code.com> wrote:
> I've created MR.
> https://salsa.debian.org/debian/enchant/-/merge_requests/2

Since it is decided that src:enchant will not be part of next Debian
stable release, fixing it is really optional. However, I elected to
push a new 1.6.0-11.4 fix and drop the unnecessary build-dependency.

-- 
Regards,
Boyuan Yang


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


Bug#961235: RFS: austin/1.0.1-1 -- Frame stack sampler for CPython

2020-05-22 Thread Adam Borowski
On Thu, May 21, 2020 at 08:26:40PM +0100, Gabriele wrote:
>  * Package name: austin
>Version : 1.0.1-1

> Changes since the last upload:
> 
>* Fixed support for Python 3.8

Fails to build:
   dh_installman -O--buildsystem=autoconf
dh_installman: warning: Section for ./debian/austin.1 is computed as "16", 
which is not a valid section
dh_installman: error: Could not determine section for ./debian/austin.1
dh_installman: error: Aborting due to earlier error


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄



Bug#961302: sane-backends 1.0.30 released with security fixes

2020-05-22 Thread Rogério Brito
Source: sane-backends
Version: 1.0.29-1~experimental4
Severity: grave
Tags: security upstream
Justification: user security hole

The Sane team released a new version of sane-backends a few days ago, fixing
about 5 or 6 CVEs. From [their announcement][1]:

,
| Kevin Backhouse of the [GitHub Security Lab team][1] has discovered
| several issues in the epson2, epsonds and magicolor backends that could
| be exploited by a malicious network device.  All three backends are
| enabled by default.  Moreover, all enable automatic discovery of network
| devices.  The issues can be used to crash SANE frontends at start up or
| when starting a scan as well as corrupt memory leading to a possibility
| of remote code execution.
`

[1]: https://alioth-lists.debian.net/pipermail/sane-announce/2020/41.html

Please, upload a new version of the package as soon as possible.


Thanks,

Rogério Brito.

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

Kernel: Linux 5.6.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8), 
LANGUAGE=en_US.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br



Bug#951722: autopkgtest suite flaky on arm64

2020-05-22 Thread Michael Biebl

I'm convinced that applying such hacks are a bad practice and should be
avoided.
I also have to add, that my motivation to further look into this has now
basically dropped to zero.




signature.asc
Description: OpenPGP digital signature


Bug#951722: autopkgtest suite flaky on arm64

2020-05-22 Thread Noah Meyerhans
On Fri, May 22, 2020 at 11:51:07PM +0200, Michael Biebl wrote:
> > I will upload a new upstream version to sid containing the workaround
> > for the test failures.  I will leave this bug open, but will reduce the
> > severity to 'normal'.  In a subsequent upload, I will apply a patch to
> > implement sd_notify and will resolve the bug.  Please feel free to send
> > a patch if you don't want to wait however long it'll take for me to get
> > around to putting one together.
> 
> Please don't apply this hack. If you don't want to fix this properly to
> get a (newer) version into testing, please just disable the test for the
> time being.

If we don't test it, it can't be broken, right?

> It's great that the autopkgtest suite unconvered a real issue.
> Let's not mutilate the test suite.

I think the test suite with the workaround in place has more value than
the suite with this test completely disabled.  If the service never
becomes available, the test with the workaround will still detect the
situation, which is exactly what it's there for.

noah



Bug#961301: util-linux: column from util-linux is not available at runtime

2020-05-22 Thread Jules Samuel Randolph
Package: util-linux
Version: 2.34-0.1ubuntu9
Severity: important

Dear Maintainer,

I am trying to package bootiso , which
depends on util-linux >= 2.26 and requires the "column" command and its
numerous features, specifically -d, -N and -W flags.

However, since the bsdmainutils "column" is used instead, this dependency
cannot be honored for debian. This is a huge, blocking problem to
properly ship bootiso utility. Luckuly, being upstream author I can
write some hard-coded checks to control supported flags. But the general
idea that one author cannot rely on the presence of appropriate versions
of utilities as central to GNU/Linux as those shipped in "util-linux" is
troublesome. The rule responsible for disabling column utility is
available here:
https://salsa.debian.org/debian/util-linux/-/blob/68f9a3a314831acb19ed09ae2b598a9e471d8c46/debian/rules#L38

I have read https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908975 but
the proposed resolution, to add a "-o" option in bsdmainutils, doesn't
address bootiso users issue.

Please note I am writing from Ubuntu, but that has no incidence on the
scope of the present report. See also
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1705437
which defers the issue to Debian maintainers.

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-31-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages util-linux depends on:
ii  libaudit1  1:2.8.5-2ubuntu6
ii  libblkid1  2.34-0.1ubuntu9
ii  libc6  2.31-0ubuntu9
ii  libcap-ng0 0.7.9-2.1build1
ii  libcrypt1  1:4.4.10-10ubuntu4
ii  libmount1  2.34-0.1ubuntu9
ii  libpam0g   1.3.1-5ubuntu4
ii  libselinux13.0-1build2
ii  libsmartcols1  2.34-0.1ubuntu9
ii  libsystemd0245.4-4ubuntu3
ii  libtinfo6  6.2-0ubuntu2
ii  libudev1   245.4-4ubuntu3
ii  libuuid1   2.34-0.1ubuntu9
ii  login  1:4.8.1-1ubuntu5
ii  zlib1g 1:1.2.11.dfsg-2ubuntu1

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  dosfstools  4.1-2
ii  kbd 2.0.4-4ubuntu2
pn  util-linux-locales  

-- no debconf information



Bug#961146: systemd-logind sometimes ignores a systemd-inhibit lock

2020-05-22 Thread Michael Biebl
Am 22.05.20 um 12:19 schrieb Vincent Lefevre:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/15887
>

Thanks for forwarding this issue.

> On 2020-05-22 06:08:02 +0200, Michael Biebl wrote:
>> I can't reproduce the issue with those instructions.
>> Must be something specific to your hardware / software configuration.
>>
>> To further debug this yourself, you might try running logind manually.
>> Stop the running instance, then run
>> SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-logind
> 
> The running instance cannot be stopped as it is automatically
> restarted. 

This is strange. Something is triggering the start of systemd-logind
(via D-Bus most likely). My educated guess is, that it is actually this
process, which triggers the suspend, not logind itself.

Remember when I initially said, that logind provides the mechanism and
the policy is supposed to be proved by something else (usually the
desktop environment).



signature.asc
Description: OpenPGP digital signature


Bug#951722: autopkgtest suite flaky on arm64

2020-05-22 Thread Michael Biebl
Am 22.05.20 um 07:29 schrieb Noah Meyerhans:
> On Sun, May 10, 2020 at 11:06:26PM +0200, Michael Biebl wrote:
>>> +echo "Waiting for the service to be available"
>>> +c=0
>>> +while ! nc -z -U /var/run/dovecot/auth-userdb; do
>>> +   c=$(($c+1))
>>> +   sleep 2
>>> +   if [ $c -gt 30 ]; then
>>> +   echo "Timed out waiting for the service to be available" >&2
>>> +   exit 1
>>> +   fi
>>> +done
>>
>> Looping until the service is ready appears to be a workaround/hack at
>> best imho.
> 
> I agree, however...
> 
>> The dovecot service should only signal its readiness when the
>> communication sockets are ready yet to accept connections. I.e. this
>> autopkgtest appears to point at a real issue that should be fixed properly.
> 
> I do not believe that this is an RC issue.  In order to address the
> stale upstream version and pending security updates in sid, and allow
> the package to again enter bullseye, I propose the following:

That's a policy determined by the release manager/ maintainers of debci.
The recommended that I should file such issues with RC severity.
If you don't agree with that policy, you should probably contact them
directly.

> I will upload a new upstream version to sid containing the workaround
> for the test failures.  I will leave this bug open, but will reduce the
> severity to 'normal'.  In a subsequent upload, I will apply a patch to
> implement sd_notify and will resolve the bug.  Please feel free to send
> a patch if you don't want to wait however long it'll take for me to get
> around to putting one together.

Please don't apply this hack. If you don't want to fix this properly to
get a (newer) version into testing, please just disable the test for the
time being.
It's great that the autopkgtest suite unconvered a real issue.
Let's not mutilate the test suite.


> Dovecot has been essentially unmaintained in Debian since August 2019,
> and there's quite a backlog of work to do.  I'm going to work on getting
> it back into shape, but it will be a little while before it's where it
> should be.  It won't happen all at once.> 
> noah
> 

The patch to add sd_notify is rather trivial. Problem is, that dovecot
unhelpfully clears the full environment. In src/master/main.c,
sd_notify() should be called around/after main_init().
Unfortunately, at this point master_service_env_clean() has been called,
clearing the process environment, including NOTIFY_SOCKET, which is
passed from systemd to dovecot and is needed to make sd_notify work.

I haven't found a way how to instruct dovecot not to clear the
NOTIFY_SOCKET env var.

Regards,
Michael




signature.asc
Description: OpenPGP digital signature


Bug#940732: pulseeffects: Missing plugins

2020-05-22 Thread Tobias Gerold


Any progress on this one?

The salsa repo (https://salsa.debian.org/multimedia-team/lsp-plugins)
was already mentioned, but I see no package named "lsp-plugins".

To summarize the (obvious) way to compile the lv2-plugins (for
convenience):

#install dependencies:

(only for lv2):
  * glibc >= 2.19
  * libsndfile >= 1.0.25
  * libcairo >= 1.14
  * libGL
  * Host compatible with LV2

Debian-packages:
libsndfile1-dev libcairo2-dev libgl1-mesa-dev libglu1-mesa-dev lv2-dev

#build:
git clone https://github.com/sadko4u/lsp-plugins/

make clean
make BUILD_MODULES='lv2'
make install 

The usual install path is:
/usr/local/lib/lv2/

You can also use
make install DESTDIR=/path-to-somewhere

So you can copy the files where you want to.



Bug#961300: New upstream available

2020-05-22 Thread Lee Garrett
Package: thinkfan
Version: 0.9.3-2
Severity: wishlist

Hi Evgeni,

upstream has released 1.1 of thinkfan last month, and it would be great to
package it for Debian, as it fixes the issue of changing hwmon names between
reboots.

I'm currently fixing up the package myself, so if you migrate the git repo to
salsa I could send a PR your way. Let me know if you're interested.

Greets,
Lee

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

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

Versions of packages thinkfan depends on:
ii  init-system-helpers  1.57
ii  libatasmart4 0.19-5
ii  libc62.30-8

thinkfan recommends no packages.

thinkfan suggests no packages.

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

-- no debconf information



Bug#961290: lintian: check for ${misc:Pre-Depends} in Depends

2020-05-22 Thread Christian Göttsche
Package: lintian
Version: 2.75.0
Severity: wishlist

Maybe Lintian can warn if `${misc:Pre-Depends}` is used in the `Depends` field.



Bug#961053: transition: mumps petsc slepc

2020-05-22 Thread R hertoric
No please enlighten me on my part in this please sir

On Thu, May 21, 2020, 9:45 AM Sebastian Ramacher 
wrote:

> Control: tags -1 + moreinfo
>
> Hi Drew
>
> On 2020-05-20 00:48:48 +0800, Drew Parsons wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> >
> > I think the joint mumps 5.3.1 / petsc 3.13 / slepc 3.13 transition is
> > ready to proceed.  Packages seem well behaved in experimental.
>
> Did you test if the reverse dependencies build with the new mumps, petsc
> and slepc stack?
>
> Cheers
> --
> Sebastian Ramacher
>


Bug#961299: FTBFS: debhelper compatibility level 12 breaks linux kernel build on hppa/parisc

2020-05-22 Thread Helge Deller
Package: linux
Version: 5.6.7-1
Severity: important
Tags: ftbfs

The Debian Linux kernel fails to build from source for all kernels > 5.5.17-1, 
as can be seen here:
https://buildd.debian.org/status/logs.php?pkg=linux=hppa

During build a 32-bit Linux kernel and a 64-bit Linux kernel is built.
The 32-build builds succeeds, the 64-bit build fails.

The 64bit build fails like this:

make[3]: Leaving directory '/home/deller/build/linux/linux-5.6.7'
dh_strip --no-automatic-dbgsym -Xvmlinux
strip: debian/linux-image-5.6.0-1-parisc64/boot/vmlinuz-5.6.0-1-parisc64: file 
format not recognized
dh_strip: error: strip --remove-section=.comment --remove-section=.note 
--strip-unneeded 
debian/linux-image-5.6.0-1-parisc64/boot/vmlinuz-5.6.0-1-parisc64 returned exit 
code 1
dh_strip: error: Aborting due to earlier error

Reverting this debian commit fixes the build again:

commit 59a5af36cbf1cc01ef48b91719f999a699d99fab
Author: Ben Hutchings 
Date:   Sun Apr 19 19:49:03 2020 +0100
Use debhelper compatibility level 12
debhelper started complaining about level 9, so it's time to upgrade
again.
* Build-Depend on debhelper-compat and remove debian/compat
  (also in the signed package template)
...

So, apparently something changed how debhelper starts the strip command.
Please note, that for a 64-bit vmlinux file,
hppa64-linux-gnu-strip
is needed instead of
hppa-linux-gnu-strip
although I'm not sure if this is the problem.

Any idea?

Helge



Bug#961298: jodd: CVE-2018-21234: Potential vulnerability in JSON deserialization

2020-05-22 Thread Salvatore Bonaccorso
Source: jodd
Version: 3.8.6-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/oblac/jodd/issues/628

Hi,

The following vulnerability was published for jodd. I'm filling it as
RC severity since altough one might dispute the severity for the issue
itself, it looks that in Debian there was ever only one upload of
jodd, there are no reverse (build) dependencies neither.

Is the package acutally of some use or planned use?

CVE-2018-21234[0]:
| Jodd before 5.0.4 performs Deserialization of Untrusted JSON Data when
| setClassMetadataName is set.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-21234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21234
[1] https://github.com/oblac/jodd/issues/628

Regards,
Salvatore



Bug#959545: libmateweather: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-05-22 Thread Mike Gabriel

Control: forwarded -1 https://github.com/mate-desktop/libmateweather/issues/76

Hi,

On  So 03 Mai 2020 14:55:57 CEST, Lucas Nussbaum wrote:


Source: libmateweather
Version: 1.24.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):

make[2]: Entering directory '/<>/data'
xmllint --valid --noout ../data/Locations.xml.in
./check-timezones.sh ./Locations.xml.in
Invalid timezones in ./Locations.xml.in: America/Godthab
make[2]: *** [Makefile:637: check] Error 1
make[2]: Leaving directory '/<>/data'
make[1]: *** [Makefile:490: check-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2


The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/libmateweather_1.24.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


I have forwarded the above upstream.
https://github.com/mate-desktop/libmateweather/issues/76

Mike
--

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

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



pgputhavmdr8K.pgp
Description: Digitale PGP-Signatur


Bug#936336: coz-profiler: Python2 removal in sid/bullseye

2020-05-22 Thread Lluís Vilanova
I pushed some changes to the package repository to solve the bug when
it was opened (should be rebased onto the latest upstream release
now).

Unfortunately I do not have upload privileges and couldn't find
anybody that would keep uploading them for coz.



Bug#913759: workaround solution

2020-05-22 Thread bert
This is because for using the dark style, electrum needs the package 
qdarkstyle (https://github.com/ColinDuquesnoy/QDarkStyleSheet). It 
seems the package hasn't hit the Debian archives yet 
(https://ftp-master.debian.org/new/qdarkstyle_2.8.1+ds1-1.html).
But you can use pip3 instead. The Debian electrum package depends on 
qdarksytle < 2.7, so you could just do `pip3 install --user -Iv 
qdarkstyle==2.6.8` and electrum should be as dark as expected :)




Bug#951033: Workaround found

2020-05-22 Thread Yann Vernier
I just mucked about with Cura and tracked down inaccessible buttons to a
lacking implicitWidth for the background of ActionButton in the QML.
However, when digging for more information, I found 

https://github.com/Ultimaker/Cura/issues/5488#issuecomment-588560291

This suggests setting QT_QUICK_CONTROLS_STYLE=material, and in my
testing that does indeed resolve several of the UI bugs, including the
crash when previewing and the misrendered (size, placement, missing
background) buttons. 

I shall see if I can set this in Cura itself, but the quick workaround
would seem a wrapper script that sets the environment variable. Such
tweaks are in fact the main content of the cura script itself (aka
cura_app.py), so something like:

os.environ["QT_QUICK_CONTROLS_STYLE"] = "material"

before the CuraApplication creation (next to last line) should do.



Bug#960620: openconnect: buffer overflow in certificate handling (CVE-2020-12823)

2020-05-22 Thread Salvatore Bonaccorso
Hi,

On Wed, May 20, 2020 at 09:22:11AM +0100, Luca Boccassi wrote:
> On Tue, 2020-05-19 at 19:34 +0200, Moritz Mühlenhoff wrote:
> > On Tue, May 19, 2020 at 11:59:05AM +0100, Luca Boccassi wrote:
> > > On Tue, 2020-05-19 at 12:51 +0200, Moritz Mühlenhoff wrote:
> > > > On Tue, May 19, 2020 at 10:02:46AM +0100, Luca Boccassi wrote:
> > > > > On Thu, 14 May 2020 22:57:44 +0100 Luca Boccassi <
> > > > > bl...@debian.org
> > > > > > wrote:
> > > > > > On Thu, 2020-05-14 at 18:50 +0100, Luca Boccassi wrote:
> > > > > > > Package: openconnect
> > > > > > > Version: 6.00-1
> > > > > > > Severity: important
> > > > > > > Tags: security
> > > > > > > 
> > > > > > > Openconnect is affected by a buffer overflow in certificate 
> > > > > > > handling,
> > > > > > > that goes back at least to 6.00-1 (old-old-stable).
> > > > > > > 
> > > > > > > Fixed upstream by:
> > > > > > > 
> > > > > > > 
> > > > > https://gitlab.com/openconnect/openconnect/-/merge_requests/108
> > > > > 
> > > > > > Dear security team,
> > > > > > 
> > > > > > I uploaded to old-old-stable on request from the LTS team. How would
> > > > > > you like to handle stable and old-stable?
> > > > > 
> > > > > Ping. Should I do an upload to security-master for buster-security 
> > > > > and stretch-security?
> > > > 
> > > > It's not really clear to me why this was assigned a CVE ID, this doesn't
> > > > appear to cross any reasonable trust boundary. Certificates need to come
> > > > from a trusted source, otherwise you have many other insecurities at 
> > > > hand.
> > > > 
> > > > This appears to be "just a bug" (which would seem to reach the bar for
> > > > being fixed in a point update), but I can't see why this would need a 
> > > > DSA.
> > > > 
> > > > I might totally miss something, ofc. So please correct me if I'm wrong 
> > > > :-)
> > > > 
> > > > Cheers,
> > > > Moritz
> > > 
> > > Hi,
> > > 
> > > The upstream maintainer agrees that perhaps a CVE was not warranted.
> > > The only way this check could be done on an somewhat-external
> > > certificate is if it came from a PKCS#11 token, but it's pretty far
> > > fetched.
> > > 
> > > Release notes say:
> > > 
> > > "This release is brought to you by CVE-2020-12823; a buffer overflow
> > > when obtaining a pretty name to describe local certificates, when built
> > > against GnuTLS. Note that this isn't used for remote certificates; this
> > > is all local (client cert and supporting CAs provided locally) so not
> > > easily remotely triggerable."
> > 
> > Thanks for doublechecking!
> > 
> > As such, we don't need a DSA. You could target this for a point update
> > or we can stuff it in some git branch and piggyback on a potential
> > future DSA in case there's a DSA-relevant issue at some point?
> > 
> > Cheers,
> > Moritz
> 
> Queueing for the next time around sounds like a good idea - pushed to
> the debian/buster branch.

With the fact that procedures for updates via point releases have been
improved, it would be as well just be an option to upload for the next
buster point release and have it already queued.

Just as additional comment to the above.

Regards,
Salvatore



Bug#946801: Some thoughts

2020-05-22 Thread Jelmer Vernooij
As you may have noticed, there hasn't been much movement on this bug. I
don't want to make any hasty decisions here, since this would be a
noticeable change for users - and if we move in a particular direction,
then I don't want to have to roll back and cause even more disruption.

Some thoughts:

There are essentially two identities that can be associated with a
change:

 * the git committer
 * the git author (also what "gbp dch" and lintian-brush put in
debian/changelog)

I'm pretty sure that either way, the committer should be the person
running lintian-brush. 

Who or what the "author" of a particular change is less clear to me.
When somebody edits the control file with vim, we obviously don't
ascribe that to vim; if they reformat all files with wrap-and-sort, we
don't set the author to wrap-and-sort. At what point do we cross over? 

lintian-brush is fairly autonomous - it makes changes from start to
end, and I think that's probably what sets it apart from the other
tools I've mentioned. But isn't fully in the drivers' seat - the
committer decides when to run it and with what arguments.

On a different note, what do attributed changes in debian/changelog
mean? Is it purely for credits? Are the names in the changelog people
one can talk to to understand why particular changes were made?



Bug#961297: qemu: CVE-2020-13253

2020-05-22 Thread Salvatore Bonaccorso
Source: qemu
Version: 1:5.0-5
Severity: important
Tags: security upstream
Forwarded: https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg05835.html

Hi,

The following vulnerability was published for qemu, filling it in the
Debian BTS for tracking.

CVE-2020-13253[0]:
| sd: OOB access could crash the guest resulting in DoS

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-13253
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13253
[1] https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg05835.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



Bug#961296: mirrors: apt not working on an IPv6 only host with a ipv6 only (local) resolver

2020-05-22 Thread Jens Link
Package: mirrors
Severity: important
Tags: ipv6



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

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


When trying to setup a IPv6 only Debian stable) VM with a localy installed 
resolver apt (update / install /...) fails. 

deb.debian.org is a CNAME for debian.map.fastly.net. There are no  records 
for fastly.net so
any DNS querys from an IPv6 only resolver will not work.



Bug#961230: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.

2020-05-22 Thread Adrian Bunk
Control: clone -1 -2
Control: reassign -2 src:guile-2.0
Control: retitle -2 guile-2.0 FTBFS with make-dfsg/4.3-1: ERROR: alternatives 
priority expects min version < 1000
Control: tags -2 bullseye sid

On Fri, May 22, 2020 at 02:41:05PM +0200, Helmut Grohne wrote:
> Control: clone -1 -2
> Control: reassign -2 src:guile-3.0
> 
> On Thu, May 21, 2020 at 07:13:27PM +0200, Helmut Grohne wrote:
> > While bootstrap testing unstable, I noticed that guile-2.2 fails to
> > build from source (natively). A build now ends quicky:
> > 
> > | dpkg-buildpackage: info: source package guile-2.2
> > | dpkg-buildpackage: info: source version 2.2.7+1-5
> > | dpkg-buildpackage: info: source distribution unstable
> > | dpkg-buildpackage: info: source changed by Rob Browning 
> > 
> > |  dpkg-source --before-build .
> > | dpkg-buildpackage: info: host architecture amd64
> > |  fakeroot debian/rules clean
> > | /bin/bash: ${\#x}: bad substitution
> > | debian/rules:70: *** ERROR: alternatives priority expects min version < 
> > 1000.  Stop.
> > | dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> > exit status 2
> > 
> > This only happens since make-dfsg/4.3-1, but I think the bug here
> > ultimately is with guile-2.2. The relevant code from debian/rules is:
> > 
> > | ifneq (ok,$(shell x='$(deb_src_min_ver)';  [ "$${\#x}" -lt 4 ] && echo 
> > ok;))
> > |   $(error ERROR: alternatives priority expects min version < 1000)
> > | endif
> > 
> > It is surprising that this didn't fail with earlier versions of make.
> > The shell substitution is clearly wrong. It is unclear what it is
> > supposed to achieve. In any case, deleting these lines makes the build
> > proceed.
> 
> guile-3.0 also has this exact same bug.

So does guile-2.0:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/guile-2.0.html

> Helmut

cu
Adrian



Bug#961294: Allow derivatives to define parent project fields

2020-05-22 Thread Simon Quigley
Package: debian-policy
Version: 4.5.0.2
Severity: normal

Hello,

I recently had a discussion in a Lintian merge request[1] where I
submitted code solidifying existing behavior in the Ubuntu Desktop and
Lubuntu teams. As I stated there, it is common practice in those teams
(and I am sure it exists in others as well) to specify a
`XS-Debian-Vcs-Browser` and/or `XS-Debian-Vcs-Git` field to point to Salsa.

The rationale for this is to allow packaging changes to flow back
upstream to Debian when Ubuntu's packaging repository is in a different
location (when Ubuntu has a permanent downstream delta but continues to
rebase that delta on top of Debian's changes).

I would like to solidify this existing practice by modifying Debian
Policy, amending 5.6.26 to allow usage of -Vcs-Browser and
-Vcs-. This would make it easier for derivatives to
clearly specify where packaging changes should be submitted upstream. In
dpkg, this can be enforced by recursively running `dpkg-vendor --query
Parent` and ensuring that  matches one of those, or in Lintian
by emitting an error if that is not the case.

I would also like to use this as an opportunity to deprecate
`Original-Maintainer` in favor of `Debian-Maintainer` and allow for
`Debian-Uploaders` as well.

Thoughts?

[1] https://salsa.debian.org/lintian/lintian/-/merge_requests/310

-- 
Simon Quigley
tsimo...@debian.org
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4



signature.asc
Description: OpenPGP digital signature


Bug#896978: ITP: node-http-proxy -- High performance event emitter for Node.js

2020-05-22 Thread fancycade
Hi Andrius,

> > sponsor. This is blocked by node-eventemitter3, which is in the
> > process of being packaged.
>
> Am I right to assume you are now working on packaging this?

Yes, I have a package that builds here for your review:
https://salsa.debian.org/js-team/node-eventemitter3

The only issue I found was that the tests depend on node-assume, which hasn't 
been packaged yet.
I can take a look packaging node-assume as a next step if you think it is worth 
it.

You can find the ITP here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961243

Thanks,
Harley



Bug#959625: caml-crush: FTBFS: SP line 7: Not found a value in env for: session

2020-05-22 Thread Thomas Calderon
Hello,

I've released a new version of the package that addresses the issue with
coccinelle, I've then attempted to push the new package on ftpmaster-anon
as sources only.

Let me know if this was the right process.

Thanks!

Thomas Calderon


On Sun, 3 May 2020, 14:12 Lucas Nussbaum,  wrote:

> Source: caml-crush
> Version: 1.0.8-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200501 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > make[3]: Entering directory
> '/<>/build-SERVER/src/bindings-pkcs11'
> > camlidl -header ../../../src/bindings-pkcs11/pkcs11.idl
> > cat ../../../src/bindings-pkcs11/pkcs11_stubs.c | sed -e
> 's/Begin_roots_block(\(.*\)).*/Begin_roots_block(\1);/g' | sed -e
> 's/Begin_root(\(.*\)).*/Begin_root(\1);/g' | sed -e
> 's/End_roots(\(.*\)).*/End_roots(\1);/g' > ./tmp
> > mv ./tmp ../../../src/bindings-pkcs11/pkcs11_stubs.c
> > #Sed to patch (GetSlotList/GetMechList/FindObjects/GetObjectSize)
> > sed -i "s/* int/\* nativeint/g" ../../../src/bindings-pkcs11/pkcs11.mli
> > sed -i "s/* int/\* nativeint/g" ../../../src/bindings-pkcs11/pkcs11.ml
> > spatch --no-show-diff --in-place --sp-file
> ../../../src/bindings-pkcs11/pkcs11_stubs.cocci
> ../../../src/bindings-pkcs11/pkcs11_stubs.c
> > init_defs_builtins: /usr/bin/../lib/coccinelle/standard.h
> > warning: line 96: _ctxs, previously declared as a metavariable, is used
> as an identifier
> > warning: line 97: _ctx, previously declared as a metavariable, is used
> as an identifier
> > warning: line 97: _ctxs, previously declared as a metavariable, is used
> as an identifier
> > warning: line 98: _c1, previously declared as a metavariable, is used as
> an identifier
> > warning: line 99: _c2, previously declared as a metavariable, is used as
> an identifier
> > warning: line 104: _v3, previously declared as a metavariable, is used
> as an identifier
> > warning: line 104: _c2, previously declared as a metavariable, is used
> as an identifier
> > warning: line 104: _ctx, previously declared as a metavariable, is used
> as an identifier
> > warning: line 105: _c2, previously declared as a metavariable, is used
> as an identifier
> > warning: line 105: _v3, previously declared as a metavariable, is used
> as an identifier
> > warning: line 802: _ctxs, previously declared as a metavariable, is used
> as an identifier
> > warning: line 821: _ctxs, previously declared as a metavariable, is used
> as an identifier
> > HANDLING: ../../../src/bindings-pkcs11/pkcs11_stubs.c
> > #Sed because spatch is not able to preprocess
> > sed -i 's/^_CAMLIDL_EXTERN_C/extern/g'
> ../../../src/bindings-pkcs11/pkcs11.h
> > #Sed to change the structure packing pragma in WIN32 mode: CamlIDL fixes
> it to 8 while
> > #PKCS11 header fixes it to 1 => this can create binary interoperability
> issues
> > sed -i 's/push,8/push,1\/* Replaced for PKCS11 compatibiliy *\//g'
> ../../../src/bindings-pkcs11/pkcs11.h
> > spatch --no-show-diff --in-place --sp-file
> ../../../src/bindings-pkcs11/pkcs11.cocci
> ../../../src/bindings-pkcs11/pkcs11.h
> > init_defs_builtins: /usr/bin/../lib/coccinelle/standard.h
> > HANDLING: ../../../src/bindings-pkcs11/pkcs11.h
> > SP line 7: Not found a value in env for: session
> > make[3]: *** [Makefile:37: idl] Error 255
>
> The full build log is available from:
>http://qa-logs.debian.net/2020/05/01/caml-crush_1.0.8-1_unstable.log
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
>


Bug#959814: oggvideotools: diff for NMU version 0.9.1-5.1

2020-05-22 Thread Adrian Bunk
Control: tags 959814 + patch
Control: tags 959814 + pending

Dear maintainer,

I've prepared an NMU for oggvideotools (versioned as 0.9.1-5.1) and 
uploaded it to DELAYED/10. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru oggvideotools-0.9.1/debian/changelog oggvideotools-0.9.1/debian/changelog
--- oggvideotools-0.9.1/debian/changelog	2019-04-05 10:46:07.0 +0300
+++ oggvideotools-0.9.1/debian/changelog	2020-05-22 21:49:26.0 +0300
@@ -1,3 +1,11 @@
+oggvideotools (0.9.1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't run test-oggjoin that depends on pysycache-i18n
+that will likely be removed. (Closes: #959814)
+
+ -- Adrian Bunk   Fri, 22 May 2020 21:49:26 +0300
+
 oggvideotools (0.9.1-5) unstable; urgency=medium
 
   * Team upload.
diff -Nru oggvideotools-0.9.1/debian/control oggvideotools-0.9.1/debian/control
--- oggvideotools-0.9.1/debian/control	2019-04-05 10:46:07.0 +0300
+++ oggvideotools-0.9.1/debian/control	2020-05-22 21:49:26.0 +0300
@@ -16,7 +16,6 @@
  libgd-dev,
  libboost-dev,
  debconf,
- pysycache-i18n,
  python3-mecavideo,
 Standards-Version: 4.3.0
 Vcs-Git: https://salsa.debian.org/multimedia-team/oggvideotools.git
diff -Nru oggvideotools-0.9.1/debian/rules oggvideotools-0.9.1/debian/rules
--- oggvideotools-0.9.1/debian/rules	2019-04-05 10:46:07.0 +0300
+++ oggvideotools-0.9.1/debian/rules	2020-05-22 21:49:26.0 +0300
@@ -9,7 +9,7 @@
 # Run our test suite until the upstream source get one
 override_dh_auto_test:
 	dh_auto_test
-	TESTBINDIR=`pwd`/obj-*/src/binaries/ ./debian/tests/test-oggjoin
+	#TESTBINDIR=`pwd`/obj-*/src/binaries/ ./debian/tests/test-oggjoin
 	TESTBINDIR=`pwd`/obj-*/src/binaries/ ./debian/tests/test-oggcut
 
 debian-copyright:
diff -Nru oggvideotools-0.9.1/debian/tests/control oggvideotools-0.9.1/debian/tests/control
--- oggvideotools-0.9.1/debian/tests/control	2019-04-05 10:46:07.0 +0300
+++ oggvideotools-0.9.1/debian/tests/control	2020-05-22 21:49:26.0 +0300
@@ -1,4 +1,4 @@
-Tests: test-oggjoin test-oggcut
-Depends: @, debconf, pysycache-i18n, python3-mecavideo, valgrind
+Tests: test-oggcut
+Depends: @, debconf, python3-mecavideo, valgrind
 Restrictions: allow-stderr
 


Bug#961293: XCB: Fix clipboard breaking when timer wraps after 50 days

2020-05-22 Thread Lisandro Damián Nicanor Pérez Meyer
fixed 961293 5.12.5+dfsg-10
thanks

The bug is already fixed in testing, but I'm keeping it open in order
to track it in stable where it still affects people.



Bug#959724: codespell: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode

2020-05-22 Thread Vincent Lefevre
Control: tags -1 patch

On 2020-05-04 15:43:48 +0200, Vincent Lefevre wrote:
> Since the switch to python3.8, running codespell triggers a warning:
> 
> /usr/lib/python3.8/codecs.py:905: RuntimeWarning: line buffering 
> (buffering=1) isn't supported in binary mode, the default buffer size will be 
> used
>   file = builtins.open(filename, mode, buffering)
> 
> The bug against codespell was reported upstream here:
> 
>   https://github.com/codespell-project/codespell/issues/1331
> 
> now closed, as being fixed:
> 
>   https://github.com/codespell-project/codespell/pull/1401

I've attached a patch corresponding to

  
https://github.com/codespell-project/codespell/commit/33647e28b708c5736bab4608b1d422f0433eb0a8#diff-c4984ff60bb6d58a3a2f9940d1a396f9

for codespell 1.16.0-2.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Index: codespell-1.16.0/codespell_lib/_codespell.py
===
--- codespell-1.16.0.orig/codespell_lib/_codespell.py
+++ codespell-1.16.0/codespell_lib/_codespell.py
@@ -309,13 +309,13 @@ def build_exclude_hashes(filename, exclu
 
 
 def build_ignore_words(filename, ignore_words):
-with codecs.open(filename, mode='r', buffering=1, encoding='utf-8') as f:
+with codecs.open(filename, mode='r', encoding='utf-8') as f:
 for line in f:
 ignore_words.add(line.strip())
 
 
 def build_dict(filename, misspellings, ignore_words):
-with codecs.open(filename, mode='r', buffering=1, encoding='utf-8') as f:
+with codecs.open(filename, mode='r', encoding='utf-8') as f:
 for line in f:
 [key, data] = line.split('->')
 # TODO for now, convert both to lower. Someday we can maybe add
@@ -345,11 +345,8 @@ def build_dict(filename, misspellings, i
 def is_hidden(filename, check_hidden):
 bfilename = os.path.basename(filename)
 
-if bfilename != '' and bfilename != '.' and bfilename != '..' \
-and (not check_hidden and bfilename[0] == '.'):
-return True
-
-return False
+return bfilename not in ('', '.', '..') and \
+(not check_hidden and bfilename[0] == '.')
 
 
 def is_text_file(filename):


Bug#950404: Bug#953181: src:ndpi: fails to migrate to testing for too long

2020-05-22 Thread Adrian Bunk
On Thu, Mar 05, 2020 at 04:39:44PM +0100, Paul Gevers wrote:
>...
> If a package is out of sync between unstable and testing for a longer
> period, this usually means that bugs in the package in testing cannot be
> fixed via unstable. Additionally, blocked packages can have impact on
> other packages, which makes preparing for the release more difficult.
> Finally, it often exposes issues with the package and/or
> its (reverse-)dependencies. We expect maintainers to fix issues that
> hamper the migration of their package in a timely manner.
>...

The 32bit problem has been fixed upstream.

Dimitri, what is the status of your big endian porting for s390x[1]?

cu
Adrian

[1] https://github.com/ntop/nDPI/issues/843



Bug#961153: tech-ctte: Call for votes on TC membership of Sean Whitton

2020-05-22 Thread Niko Tyni
On Wed, May 20, 2020 at 05:03:16PM -0300, David Bremner wrote:
 
> ===BEGIN
> The Technical Committee recommends that Sean Whitton  be
> appointed by the Debian Project Leader to the Technical Committee.
> 
> S: Recommend to Appoint Sean Whitton 
> F: Further Discussion
> ===END

I vote: S > F

-- 
Niko Tyni   nt...@debian.org


signature.asc
Description: PGP signature


Bug#961156: tech-ctte: Call for votes on TC membership of Elana Hashman

2020-05-22 Thread Niko Tyni
On Wed, May 20, 2020 at 05:10:26PM -0300, David Bremner wrote:
 
> ===BEGIN
> The Technical Committee recommends that Elana Hashman  be
> appointed by the Debian Project Leader to the Technical Committee.
> 
> S: Recommend to Appoint Elana Hashman 
> F: Further Discussion
> ===END

I vote: S > F

-- 
Niko Tyni   nt...@debian.org


signature.asc
Description: PGP signature


Bug#961293: XCB: Fix clipboard breaking when timer wraps after 50 days

2020-05-22 Thread Lisandro Damián Nicanor Pérez Meyer
Source: qtbase-opensource-src
Version: 5.12.5+dfsg-10
Severity: important
Tags: patch upstream
Forwarded: https://codereview.qt-project.org/c/qt/qtbase/+/254187/

Hi! A user reported us on IRC of this bug, and it happens to be solved by 
upstream already in



According to the patch:

xcb_timestamp_t is a 32-bit unsigned value in miliseconds, so it
wraps after 49.7 days. When it happens, QXcbConnection::m_time stops
updating and copy & paste in an application would not work until the
application is restarted. This patch detects the timer wrap and
allows m_time to wrap too. The fix was verified in KDE desktop with
applications running for 51 days.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64, armhf

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Bug#961292: ITP: python-commentjson -- module for json that supports comments

2020-05-22 Thread Scott Kitterman
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman 

* Package name: python-commentjson
  Version : 0.8.3
  Upstream Author : Vaidik Kapoor 
* URL : https://pypi.org/project/commentjson
* License : Expat
  Programming Lang: Python
  Description : module for json that supports comments

 Comment JSON is a Python package that helps you create JSON files with Python
 and JavaScript style inline comments. Its API is very similar to the Python
 standard library's json module.
 .
 This is the Python 3 version of the package.

I intend to maintain this in DPMT.  It is needed to run tests for the
recently packaged python3-resolvelib package.

Scott K



Bug#944965: debsums: Script accesses internal dpkg database

2020-05-22 Thread Axel Beckert
Control: clone -1 -2
Control: reassign -2 dpkg
Control: retitle -2 dpkg: Please provide a command-line option to show md5sums 
for multiple or all packages with one call
Control: submitter -2 !
Control: block -1 by -2

Hi Guillem,

while trying to check what's left to implement this, I got reminded by
this source code comment which currently IMHO very well validates
direct database usage (as you seem to have noticed, too):

# Calling dpkg-query --control-path for every package is too slow,
# so we cheat a little bit.

Guillem Jover wrote:
> The debsums program should be switched to use something like:
> 
>   «dpkg-query --control-show $pkg md5sums»
> 
> to get the md5sums file contents. [...] While this is not ideal,
> because this interface does not allow batching, at least it will
> stop accessing the internal database. I will be adding in the near
> future a new virtual field to dpkg-query to be able to fetch all
> md5sums for all packages with something like:
> 
>   «dpkg-query \
> --showformat 'Package: ${Package}\nMd5sums: ${db-fsys:Md5sums}\n' \
> --show»

So please do so. Cloning this bug as a reminder and blocker.

Will for now upload debsums with just debsums_init removed, so at
least a bit of this issue is resolved that way.

> The other question though, is whether it still makes sense to ship
> debsums, with «dpkg --audit» checking for missing md5sums files,
> «dpkg --verify» checking for hash mismatches, and «dpkg --unpack»
> generating these when the to be installed does not provide one?

>From my point of view alone the different (IMHO way more comfortable)
command-line user interface and more readable output still validates
it's existence. (I really dislike that rpm format. :-)

I also haven't found an quick and easy way to just show conffiles or
non-conffiles with dpkg --verify on a quick glance. Even to grep out
the just changed ones is not that trivial.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#947258: lintian: manpage-without-executable is too strict (false positives for subcommand man pages)

2020-05-22 Thread Felix Lechner
Hi Daniel,

On Mon, Dec 23, 2019 at 10:06 AM Daniel Kahn Gillmor
 wrote:
>
> If there is a way that notmuch, git, and other subcommand-style tools
> should be annotating their manpages to avoid triggering this lintian
> report, please update lintian's tag description to point to how to do
> this.

So far, I learned that 'man' interprets two commands by default as a
sub-command [1] but I do not know how to tell from a man page that it
is for a sub-command like 'git add' instead of a command called
git-add.

I do not believe there is an annotation for it, although there
probably should be.

Unless someone has a better idea, I think we have parse the output
generated by 'groff -man -Tascii'. Similar to man's strategy [1] a man
page would be deemed to relate to a sub-command when the first two
words in the synopsis, connected by a hyphen, are the same as the file
name.

Kind regards
Felix Lechner

[1] https://stackoverflow.com/a/32750157



Bug#961270: RM: pdns-recursor/4.0.4-1+deb9u4

2020-05-22 Thread Moritz Mühlenhoff
On Fri, May 22, 2020 at 10:36:51AM +, Holger Levsen wrote:
> FYI,
> 
>  debian-security-support (2020.05.22) unstable; urgency=medium
>  .
>* Add pdns-recursor to security-support-ended.deb9 as explained in
>  DSA-4691-1.

Thanks for this.

Cheers,
Moritz



Bug#896978: ITP: node-http-proxy -- High performance event emitter for Node.js

2020-05-22 Thread merkys
Hi Harley,

On 2020-05-22 18:26, fancycade wrote:
>> Am I right to assume you are now working on packaging this?
> Yes, I have a package that builds here for your review:
> https://salsa.debian.org/js-team/node-eventemitter3

Thanks for letting me know. Actually, I was asking about
node-http-proxy, are you on that too?

Ping me whenever you feel the packages are ready. I will review and
sponsor them. Thanks for your efforts!

Best,
Andrius



Bug#961289: RM: netqmail -- RoQA; Orphaned, abandoned upstream, plenty of alternatives exist

2020-05-22 Thread Moritz Muehlenhoff
Package: ftp.debian.org
Severity: normal

Please remove qmail from the archive. We'll keep it updated in stable until 
Buster is EOLed,
but it should not be part of the next stable release.

Cheers,
Moritz



Bug#961288: RM: nmapsi4 [armel mips64el ppc64el s390x] -- RoQA; can no longer be built on these architectures

2020-05-22 Thread Adrian Bunk
Package: ftp.debian.org
Severity: normal

The new build dependency qtwebengine5-dev is not available
on all architectures.



Bug#961028: hplip: No scanner found: SANE cannot load the hpaio backend

2020-05-22 Thread Léo Girardin
Hello,

Same bug here with a Deskjet F4500. As a workaround I can use Webscan
by entering the IP address of the printer in Firefox URL bar. 

-- 
Léo



Bug#960390: x86_64: No serial port output

2020-05-22 Thread Steve McIntyre
On Sat, May 23, 2020 at 01:15:37AM +0900, Punit Agrawal wrote:
>tags 960390 + patch
>
>On Wed, 13 May 2020 14:14:54 +0200 john doe  wrote:
>
>[...]
>
>> I also'd like to point out that instead of modifying grub at the install
>> prompt, pressing the escape key and typing at the boot prompt the below
>> works for me (pressing the 'escape' key instead of the 'tab' key):
>>
>>
>> boot: install console=ttyS0,115200n8 DEBIAN_FRONTEND=text vga=none
>>
>>
>>  From Buster onwords, /etc/default/grub does not need to be modified at
>> all after installation.
>>
>>
>> What transpired in this thread is that modifying grub at installation
>> time is not reflected at run time.
>
>Although that is also an issue, it's not the first issue the user
>encounters. As mentioned by Bjorn and Geert, for users wanting to
>install Debian on a headless machine there is no easy answer.
>
>To avoid needing any workarounds such as those discussed in earlier
>replies, I looked at enabling the installer images to output on the
>serial console by default. The attached simple change to the grub
>configuration gives output on serial as well as connected monitor.
>
>The next issue that needs fixing is to update the kernel command line
>to launch the installer on the serial console.

I think few people have been bothered by this in the past - all the
server machines I've used for years have had options for redirecting a
VGA console to the serial port. Do you have one that doesn't?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I suspect most samba developers are already technically insane... Of
 course, since many of them are Australians, you can't tell." -- Linus Torvalds



Bug#961287: ITP: bootiso -- a bash program to securely create a bootable USB device from one image file

2020-05-22 Thread Jules Samuel Randolph
Package: wnpp
Severity: wishlist
Owner: Jules Samuel Randolph 

* Package name: bootiso
  Version : 4.0.1
  Upstream Author : Jules Samuel Randolph 
* URL : https://github.com/jsamr/bootiso
* License : GPLv3
  Programming Lang: bash
  Description : A bash program to securely create a bootable USB device 
from one image file.

This program is a user-friendly CLI to create bootable USB devices
from image files. It not only adds a security layer on top of dd by
checking target device is connected through USB port and performing
a handful of other assertions, but it also supports non-hybrid ISOs,
given that they follow either UEFI standard or provide ISOLINUX boot
configuration. The utility claims support for:

- Modern GNU/Linux images;
- BSD images;
- Ultimate Boot CD (non-hybrid) and other rescue CDs;
- Windows 7 (x64) and superior;

... and any hybrid images.

The utility also offers additional features such as persistent data
partitions, hashsum checks, quickformat... etc.

Even though this is far from the only program aimed at booting USB
sticks, I have no knowledge of similar programs operating in full
command-line mode. Being the upstream author, I plan to maintain
it as long as the project thrives. I am also very concerned and
meticulous about following GNU/Linux, POSIX and other standards and
will do everything  to comply. The utility is shipped with a man,
zsh and bash completions.

I would love to have a sponsor to help me get in. I am curently
taking a look at Debian Policy Manual and other material to create
a source repository. If someone would like to review it when it's
ready, that would be amazing.

I might also be interrested in maintaining other packages in the
future, although this is not my top priority.



Bug#872809: fixed in fonts-dejavu 2.37-2

2020-05-22 Thread Boyuan Yang
X-Debbugs-CC: fab...@debian.org debian-fo...@lists.debian.org

On Fri, 22 May 2020 15:49:07 + Debian FTP Masters <
ftpmas...@ftp-master.debian.org> wrote:
>  fonts-dejavu (2.37-2) unstable; urgency=medium
>  .
>* Drop transitional packages ttf-dejavu, ttf-dejavu-core and
>  ttf-dejavu-extra. Thanks Holger Levsen, Closes: #872809.

oops...

There are lots of packages that still (build-)depend on ttf-dejavu-*.
Shall we fix them / file bugs?


% build-rdeps ttf-dejavu
Reverse Build-depends in main:
--

csound
synfigstudio
zatacka

 build-rdeps ttf-dejavu-extra
Reverse Build-depends in main:
--

cdo
csound
metview
python-cdo
synfigstudio
zatacka

% build-rdeps ttf-dejavu-core
Reverse Build-depends in main:
--

allegro5
cdo
csound
gazebo
grub2
magics++
metview
natbraille
python-cdo
synfigstudio
zatacka



% LC_ALL=C apt rdepends ttf-dejavu
ttf-dejavu
Reverse Depends:
  Breaks: fonts-dejavu (<< 2.33+svn2514-2~)
  Suggests: pepperflashplugin-nonfree
  Depends: wmforkplop
  Suggests: matchbox
  Replaces: fonts-dejavu-extra (<< 2.20-1)
  Breaks: fonts-dejavu-extra (<< 2.20-1)
  Replaces: fonts-dejavu-core (<< 2.20-1)
  Breaks: fonts-dejavu-core (<< 2.20-1)
  Replaces: fonts-dejavu (<< 2.33+svn2514-


% LC_ALL=C apt rdepends ttf-dejavu-core
ttf-dejavu-core
Reverse Depends:
  Breaks: fonts-dejavu-core (<< 2.33+svn2514-2~)
  Depends: otrs2
  Depends: frogatto-data
  Suggests: fheroes2-pkg
  Depends: astromenace
  Depends: zatacka
  Depends: xmoto-data
  Depends: wotsap
  Depends: singularity
  Depends: scilab-test
 |Depends: sarg
  Suggests: ruby-ttfunk
  Suggests: rlvm
  Depends: plymouth-theme-hamara
  Depends: plymouth-themes
  Recommends: php-imagick
  Recommends: php-gmagick
  Depends: natbraille
  Depends: miceamaze
  Depends: manaplus-data
  Depends: libmagplus3v5
  Depends: lightyears
  Suggests: libsdl-sge-dev
  Suggests: ircmarkers
 |Depends: icewm
  Recommends: gfxboot-dev
  Depends: libgazebo-dev
  Depends: ttf-dejavu
  Replaces: fonts-dejavu-core (<< 2.33+svn2514-2~)
  Depends: 0ad-data-common
  Depends: enigma-data
  Depends: castle-game-engine-doc
  Depends: blobwars-data
  Depends: blobandconquer-data
  Depends: allegro5-doc


 LC_ALL=C apt rdepends ttf-dejavu-extra
ttf-dejavu-extra
Reverse Depends:
  Breaks: fonts-dejavu-extra (<< 2.33+svn2514-2~)
  Depends: otrs2
  Depends: libmagplus3v5
  Depends: ttf-dejavu
  Replaces: fonts-dejavu-extra (<< 2.33+svn2514-2~)
  Depends: enigma-data



-- 
Regards,
Boyuan Yang



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


Bug#961086: linux: Add armada_37xx_wdt.ko to the arm64 installer

2020-05-22 Thread Domenico Andreoli
On Tue, 19 May 2020 23:51:17 +0200, I wrote:
> Package: src:linux
> Version: 5.6.7-1
> Severity: wishlist
> 
> Hi,
> 
>   in order to install Debian on Turris MOX [0] it's necessary to kick
> the watchdog, which is started by u-boot.
> 
> Please see MR #241 [1] in order to add the needed module to the D-I
> kernel package.

I rebased this on the sid branch. Is there any chance that it can be
merged before the next upload?

Or is it something I can marge myself?  I'm not familiar with the
process and would prefer to avoid waiting for myself without knowing ;)

Thanks!
Domenico

-- 
rsa4096: 3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA  356E CC79 2832 ED38 CB05



Bug#960271: Status on bug 960271 - 'BITS_PER_LONG' wrongly used

2020-05-22 Thread Alex Bennée
FWIW I would like it to be sooner rather than later because as the
latest Debian images have rolled out more and more of our CI's have
fallen over. Our attempts to work around the fix with a snapshot
failed as well so we are currently hoping Debian based builds don't
bitrot too much before stuff starts working again.

On Fri, 22 May 2020 at 15:36, Lukas Straub  wrote:
>
> Hello Everyone,
> When will this fix be released?
>
> Regards,
> Lukas Straub



-- 
Alex Bennée
KVM/QEMU Hacker for Linaro



Bug#961286: libmagplus3v5: Depends on removed ttf-dejavu-* packages

2020-05-22 Thread Boyuan Yang
Package: libmagplus3v5
Severity: grave
Version: 4.3.3-1
Tags: bullseye sid
X-Debbugs-CC: mckins...@debian.org

Dear Debian magics++ maintainer,

As in https://bugs.debian.org/872809 , The latest upload of fonts-
dejavu removed transition packages:

* ttf-dejavu
* ttf-dejavu-core
* ttf-dejavu-extra

Your library package libmagplus3v5 still depends on the latter 2
packages.

Please use the real package names (fonts-dejavu-core, fonts-dejavu-
extra) and verify that your package did not use hardcoded font paths
since the font path has changed with the transition from ttf-dejavu* to
fonts-dejavu*.

-- 
Regards,
Boyuan Yang


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


Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream

2020-05-22 Thread gregor herrmann
On Fri, 22 May 2020 09:58:12 +0200, intrigeri wrote:

> So, once aptitude >= 0.8.13-1 has migrated to testing, we'll need to
> ask (presumably the release team) for libparse-debianchangelog-perl to
> lose its "key package" status, so the autoremoval machinery can remove
> it from testing due to this very RC bug.

Unless we go directly for an RM;RoM bug, then it will be removed from
testing when it's gone from unstable.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature


Bug#960390: x86_64: No serial port output

2020-05-22 Thread Punit Agrawal
tags 960390 + patch

On Wed, 13 May 2020 14:14:54 +0200 john doe  wrote:

[...]

> I also'd like to point out that instead of modifying grub at the install
> prompt, pressing the escape key and typing at the boot prompt the below
> works for me (pressing the 'escape' key instead of the 'tab' key):
>
>
> boot: install console=ttyS0,115200n8 DEBIAN_FRONTEND=text vga=none
>
>
>  From Buster onwords, /etc/default/grub does not need to be modified at
> all after installation.
>
>
> What transpired in this thread is that modifying grub at installation
> time is not reflected at run time.

Although that is also an issue, it's not the first issue the user
encounters. As mentioned by Bjorn and Geert, for users wanting to
install Debian on a headless machine there is no easy answer.

To avoid needing any workarounds such as those discussed in earlier
replies, I looked at enabling the installer images to output on the
serial console by default. The attached simple change to the grub
configuration gives output on serial as well as connected monitor.

The next issue that needs fixing is to update the kernel command line
to launch the installer on the serial console.


0001-x86-grub-efi-Enable-serial-console.patch
Description: Binary data


Bug#960584: src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries

2020-05-22 Thread Boyuan Yang
Control: tags -1 + pending
X-Debbugs-CC: elb...@debian.org

在 2020-05-22星期五的 23:53 +0800,Boyuan Yang写道:
> Control: reopen -1
> Control: found -1 0.9.0-1
> Control: tags -1 +bullseye +sid -pending
> Control: forcemerge 960584 961285
> X-Debbugs-CC: elb...@debian.org
> 
> This bug is actually not fixed. Reopening and tagging accordingly.
> Let
> me know if you have any questions or need any help.

Well... I didn't notice an existing deferred NMU. With the NMU it seems
that the problem can be solved soon.

Currently the testing autoremoval will take place on June 12; we should
have enough time to get the fix into Testing before the removal
actually takes place. Sorry for the noise.

-- 
Regards,
Boyuan Yang



Bug#912846: grub2: stop depending on ttf-dejavu-core

2020-05-22 Thread Steve McIntyre
On Fri, May 22, 2020 at 03:59:55PM +0100, Colin Watson wrote:
>On Fri, May 22, 2020 at 04:30:16PM +0200, Fabian Greffrath wrote:
>> The ttf-dejavu-core package has been a transitional package for 7 years
>> (!) now and its removal is going to happen with the next package
>> upload, which will be anytime soon. Please adjust your package's build-
>> dependencies to fonts-dejavu-core and add the corresponding search path
>> to configure.ac. I have already prepared a patch for the latter.
>
>Hi - thanks for the patch.  I expect I can apply this, but could you
>please also send it upstream (grub-de...@gnu.org)?  I don't see a reason
>it couldn't be applied there, and it would make ongoing maintenance
>easier.

Ah, I've just taken the change and pushed to git...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Getting a SCSI chain working is perfectly simple if you remember that there
  must be exactly three terminations: one on one end of the cable, one on the
  far end, and the goat, terminated over the SCSI chain with a silver-handled
  knife whilst burning *black* candles. --- Anthony DeBoer



Bug#961239: [Python-modules-team] Bug#961239: python-django-registration: Not compatible with Django 3.x

2020-05-22 Thread Emmanuel Arias
Hi,

This bugs seems to be fixed now on python3-django-registration 2.2-4

That is already on experimental.

Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com

El jue., 21 de may. de 2020 a la(s) 18:15, Chris Lamb
(la...@debian.org) escribió:
>
> Source: python-django-registration
> Version: 2.2-3
> Severity: normal
> User: python-modules-t...@lists.alioth.debian.org
> Usertags: django-3.x
> Control: affects -1 mini-buildd
>
> Dear maintainer,
>
> The version of Django experimental is currently 3.0.6-1. I have built
> the 153 reverse-dependencies in unstable against this version and 114
> of these build & pass their testsuite successfully. For more
> information, see:
>
> http://bugs.debian.org/960890
>
> Please use the above bug report for queries or questions regarding
> Django 3.x that are not specific to this particular package in order
> to reduce duplicated work across all of the bugs.
>
> Whilst python-django-registration itself builds from source, it causes
> other packages (eg. mini-buildd) to FTBFS.
>
> Here is the FTBFS from mini-buildd:
>
>   […]
>
> File 
> "/home/lamby/temp/cdt.20200517004829.Xc0msV8pPb.ags.lamby-debian-experimental.python3-mini-buildd/mini-buildd-1.1.31/src/mini_buildd/django_settings.py",
>  line 168, in pseudo_configure
>   django.setup()
> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in 
> setup
>   apps.populate(settings.INSTALLED_APPS)
> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 114, 
> in populate
>   app_config.import_models()
> File "/usr/lib/python3/dist-packages/django/apps/config.py", line 211, in 
> import_models
>   self.models_module = import_module(models_module_name)
> File "/usr/lib/python3.8/importlib/__init__.py", line 127, in 
> import_module
>   return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1014, in _gcd_import
> File "", line 991, in _find_and_load
> File "", line 975, in _find_and_load_unlocked
> File "", line 671, in _load_unlocked
> File "", line 783, in exec_module
> File "", line 219, in 
> _call_with_frames_removed
> File "/usr/lib/python3/dist-packages/registration/models.py", line 23, in 
> 
>   from django.utils.encoding import python_2_unicode_compatible
>   ImportError: cannot import name 'python_2_unicode_compatible' from 
> 'django.utils.encoding' 
> (/usr/lib/python3/dist-packages/django/utils/encoding.py)
>
>   make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20200517004829.Xc0msV8pPb.ags.lamby-debian-experimental.python3-mini-buildd/mini-buildd-1.1.31'
>   make: *** [debian/rules:4: build] Error 2
>   dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
>
>   […]
>
> The full build log is attached.
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
> ___
> Python-modules-team mailing list
> python-modules-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team



Bug#960584: src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries

2020-05-22 Thread Boyuan Yang
Control: reopen -1
Control: found -1 0.9.0-1
Control: tags -1 +bullseye +sid -pending
Control: forcemerge 960584 961285
X-Debbugs-CC: elb...@debian.org

This bug is actually not fixed. Reopening and tagging accordingly. Let
me know if you have any questions or need any help.

-- 
Regards,
Boyuan Yang


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


Bug#961285: theme-d-gnome: Failed to migrate to testing for too long

2020-05-22 Thread Boyuan Yang
Source: theme-d-gnome
Version: 0.9.0-1
Severity: serious
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: tommi.hoynalan...@iki.fi alteh...@debian.org


Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug. Your package src:theme-d-gnome in its
current version in unstable has been trying to migrate for 68 days.
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot
be fixed via unstable. Additionally, blocked packages can have impact
on other packages, which makes preparing for the release more
difficult. Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

Currently your package only needs another source-only upload to be able
tomigrate to Testing; please refer to 
https://wiki.debian.org/SourceOnlyUpload
to see how to make a source-only upload. Let me know if you need any
help in package sponsorship.

Regards,
Boyuan Yang

[1] 
https://lists.debian.org/debian-devel-announce/2020/02/msg5.html


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


Bug#961284: nix: FTBFS on armel and mipsel

2020-05-22 Thread Boyuan Yang
Source: nix
Version: 2.3.4+dfsg3-1
Severity: normal
X-Debbugs-CC: t...@debian.org

Dear Debian nix package maintainer,

Congratulations on getting nix into Debian!

As you can see from the buildd log, the package currently FTBFS on
armel and mipsel: https://buildd.debian.org/status/package.php?p=nix

===
g++ -std=c++17 -o /<>/src/libutil/libnixutil.so -shared
-L/usr/lib/arm-linux-gnueabi -Wl,-z,relro -Wl,-z,now -L/usr/lib/arm-
linux-gnueabi -Wl,-z,relro -Wl,-z,now -Wl,--no-copy-dt-needed-entries
src/libutil/affinity.o src/libutil/archive.o src/libutil/args.o
src/libutil/compression.o src/libutil/config.o src/libutil/hash.o
src/libutil/json.o src/libutil/logging.o src/libutil/serialise.o
src/libutil/thread-pool.o src/libutil/util.o src/libutil/xml-writer.o
-llzma -lbz2 -pthread -lcrypto -lbrotlienc -lbrotlidec -L/usr/lib/arm-
linux-gnueabi -lboost_context -Wl,-z,defs -Wl,-soname=libnixutil.so   
/usr/bin/ld: src/libutil/logging.o: in function
`std::__atomic_base::fetch_add(unsigned long long,
std::memory_order)':
/usr/include/c++/9/bits/atomic_base.h:541: undefined reference to
`__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[1]: *** [mk/lib.mk:104: src/libutil/libnixutil.so] Error 1


I'm not familiar with nix and/or gcc so unfortunately I cannot provide
any suggestion.

-- 
Regards,
Boyuan Yang


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


Bug#961269: thunderbird: DENIED operation="mkdir" name=/run/user/ /dconf requested_mask="c"

2020-05-22 Thread Vincas Dargis

xiscu, could you please create `/etc/apparmor.d/local/usr.bin.thunderbird` file 
with this rule:

owner /run/user/[0-9]*/dconf/ w,

After that, restart AppArmor with `sudo systemctl restart apparmor`. Then, try starting Thunderbird 
again, and see if that error is gone?




Bug#961231: sane: No scanners identified on HP officejet Pro 8610 (all-in-one)

2020-05-22 Thread Jörg Frings-Fürst
Hello Loris,


I found that your scanner isn't supported by sane-backends.

You have update hplip. So I think your bug is located there.

Please file
a new bug again hplip.

Bug closed.

CU
Jörg

Am Freitag, den 22.05.2020, 14:46 +0200 schrieb Jörg Frings-
Fürst:
> reassign 961231 libsane
> tags 961231 + moreinfo
> thanks
> 
> Hello Loris,
> 
> 
> thank you for spending your time helping to make Debian better with
> this bug report. 
> 
> I think there is a problem in sane-backends. Therefore I move this
> bug
> report there.
> 
> Am Donnerstag, den 21.05.2020, 19:16 +0200 schrieb loris:
> > Package: sane
> > Version: 1.0.14-15
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > I have an HP Officejet Pro 8610 (all-in-one); after last upgrading
> > I
> > am not able to use my scanner: the printer works perfectly but
> > launching xsane  I get an error message: 'no device has been
> > found'.
> > As my printer is connected to router I try to connect it to my pc
> > with usb cable:
> > 
> > With command '~$ sane-find-scanner' I get the the following output:
> > 'found USB scanner (vendor=0x03f0 [HP], product=0x7112 [HP
> > Officejet
> > Pro 8610]) at libusb:005:011'
> > 
> > With command '~$ scanimage -L' I get the the following output:
> > No scanners were identified
> > 
> > Connecting a pen-drive to printer usb port and using the printer
> > touch panel I am able to scan a document and save it to pen-drive.
> > 
> > On my old Pentium4 Fujitsu Siemens I am using xfce 4.14 as desktop
> > environment,
> > [...]
> 
> Please add a file "/lib/udev/rules.d/99-libsane.rules", put the
> context
> 
> 
> ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw
> $env{DEVNAME}"
> 
> in it, reboot and check it again.
> 
> 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#961283: libhttp-tiny-perl: Don't release with bullseye

2020-05-22 Thread Dominic Hargreaves
Package: libhttp-tiny-perl
Version: 0.076-1
Severity: serious
Justification: maintainer

libhttp-tiny-perl at this version should not be released with
bullseye, since perl contains the same version.



Bug#961269: thunderbird: DENIED operation="mkdir" name=/run/user/ /dconf requested_mask="c"

2020-05-22 Thread Vincas Dargis

Control: reassign -1 thunderbird

Reassigning to thunderbird, as it ships it's AppArmor profile itself.

We have this rule there:

owner /run/user/[0-9]*/dconf/user rw,

But it it does not handle the case when parent dir is missing. It does not reproduce in my KDE 
desktop. Maybe you use some minimal desktop where Thunderbird is the first that deals with that 
dconf stuff?


Anyhow, we should update thunderbird profile.



Bug#912846: grub2: stop depending on ttf-dejavu-core

2020-05-22 Thread Colin Watson
On Fri, May 22, 2020 at 04:30:16PM +0200, Fabian Greffrath wrote:
> The ttf-dejavu-core package has been a transitional package for 7 years
> (!) now and its removal is going to happen with the next package
> upload, which will be anytime soon. Please adjust your package's build-
> dependencies to fonts-dejavu-core and add the corresponding search path
> to configure.ac. I have already prepared a patch for the latter.

Hi - thanks for the patch.  I expect I can apply this, but could you
please also send it upstream (grub-de...@gnu.org)?  I don't see a reason
it couldn't be applied there, and it would make ongoing maintenance
easier.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]



Bug#961282: Support both MariaDB and MySQL on test_mysql.sh

2020-05-22 Thread Sergio Durigan Junior
Source: libdbi-drivers
Version: 0.9.0-9
Tags: patch
Usertags: origin-ubuntu ubuntu-patch

Hi there,

I would like to propose a patch to implement support for using MySQL
when running the test_mysql.sh script.  Even though Debian uses MariaDB
as its default database, we still ship MySQL and some users might prefer
it.

The Ubuntu libdbi-drivers package carries a similar version of this
patch, but with the opposite problem: because Ubuntu's default database
is MySQL, the patch doesn't support MariaDB.  I am working towards
having a single version of the patch which can work with both databases.

This patch does not change the current behaviour of the script: it still
works normally with MariaDB.  I also tested building libdbi-drivers
using MySQL, and the package now builds fine (it was failing before).

I'm providing a debdiff attached to this message, without a changelog
entry.

Thanks a lot for considering this!

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

diff -Nru libdbi-drivers-0.9.0/debian/patches/fix-mysql-test.patch libdbi-drivers-0.9.0/debian/patches/fix-mysql-test.patch
--- libdbi-drivers-0.9.0/debian/patches/fix-mysql-test.patch	1969-12-31 19:00:00.0 -0500
+++ libdbi-drivers-0.9.0/debian/patches/fix-mysql-test.patch	2020-05-15 15:37:26.0 -0400
@@ -0,0 +1,56 @@
+Description: Fix build errors with MySQL 8.0
+ The mysql_install_db script has been removed, and replaced with
+ the --initialize options for mysqld.
+ Also add -uroot to mysqladmin calls so package can be built without
+ root.
+Author: Lars Tangvald 
+Forwarded: no
+Last-Update: 2019-07-16
+
+Index: libdbi-drivers-0.9.0/tests/test_mysql.sh
+===
+--- libdbi-drivers-0.9.0.orig/tests/test_mysql.sh	2020-05-22 00:06:19.128004409 -0400
 libdbi-drivers-0.9.0/tests/test_mysql.sh	2020-05-22 00:07:58.055128289 -0400
+@@ -36,8 +36,23 @@
+ B=`basename "$MYTMPDIR"`
+ ABSMYTMPDIR="`cd \"$D\" 2>/dev/null && pwd || echo \"$D\"`/$B"
+ 
+-# --force is needed because buildd's can't resolve their own hostnames to ips
+-mysql_install_db --no-defaults --datadir=${ABSMYTMPDIR} --force --skip-name-resolve --user=${ME}
++if $MYMYSQLD --help 2>&1 | grep -q MariaDB 2>&1 > /dev/null; then
++is_mariadb=yes
++else
++is_mariadb=no
++fi
++
++if [ $is_mariadb = "yes" ]; then
++# --force is needed because buildd's can't resolve their own hostnames to ips
++mysql_install_db --no-defaults --datadir=${ABSMYTMPDIR} --force --skip-name-resolve --user=${ME}
++$MYMYSQLD --no-defaults --skip-grant --user=${ME} --socket=${ABSMYTMPDIR}/mysql.sock --datadir=${ABSMYTMPDIR} --skip-networking &
++else
++$MYMYSQLD --no-defaults --initialize-insecure --user=${ME} --datadir=${ABSMYTMPDIR}
++$MYMYSQLD --no-defaults --skip-grant --user=${ME} --socket=${ABSMYTMPDIR}/mysql.sock --datadir=${ABSMYTMPDIR} --skip-networking &
++fi
++
++
++$MYMYSQLD --no-defaults --initialize-insecure --user=${ME} --datadir=${ABSMYTMPDIR}
+ $MYMYSQLD --no-defaults --skip-grant --user=${ME} --socket=${ABSMYTMPDIR}/mysql.sock --datadir=${ABSMYTMPDIR} --skip-networking &
+ 
+ # mysqld needs some time to come up to speed. This avoids irritating error messages from the subsequent loop
+@@ -49,7 +64,7 @@
+ 
+ echo -n pinging mysqld.
+ attempts=0
+-while ! mysqladmin --socket=${ABSMYTMPDIR}/mysql.sock ping ; do
++while ! mysqladmin -uroot --socket=${ABSMYTMPDIR}/mysql.sock ping ; do
+ 	sleep 3
+ 	attempts=$((attempts+1))
+ 	if [ ${attempts} -gt 10 ] ; then
+@@ -71,6 +86,6 @@
+ 
+ ecode=$?
+ 
+-mysqladmin --socket=${ABSMYTMPDIR}/mysql.sock shutdown
++mysqladmin -uroot --socket=${ABSMYTMPDIR}/mysql.sock shutdown
+ rm -rf ${ABSMYTMPDIR}
+ exit ${ecode}
diff -Nru libdbi-drivers-0.9.0/debian/patches/series libdbi-drivers-0.9.0/debian/patches/series
--- libdbi-drivers-0.9.0/debian/patches/series	2020-02-28 12:08:27.0 -0500
+++ libdbi-drivers-0.9.0/debian/patches/series	2020-05-15 15:37:26.0 -0400
@@ -8,3 +8,4 @@
 pgsql_precision.patch
 test_exception_failure.patch
 test_mariadb_date_tz.patch
+fix-mysql-test.patch
diff -Nru libdbi-drivers-0.9.0/debian/test_mysql.sh libdbi-drivers-0.9.0/debian/test_mysql.sh
--- libdbi-drivers-0.9.0/debian/test_mysql.sh	2020-02-08 03:47:26.0 -0500
+++ libdbi-drivers-0.9.0/debian/test_mysql.sh	2020-05-15 15:37:26.0 -0400
@@ -26,9 +26,21 @@
 MYTEMP_DIR=`mktemp -d`
 ME=`whoami`
 
-# --force is needed because buildd's can't resolve their own hostnames to ips
-mysql_install_db --no-defaults --datadir=${MYTEMP_DIR} --force --skip-name-resolve --user=${ME}
-/usr/sbin/mysqld --no-defaults --skip-grant --user=${ME} --socket=${MYTEMP_DIR}/mysql.sock --datadir=${MYTEMP_DIR} --skip-networking &
+# Check if we're running under MariaDB or MySQL.
+if /usr/bin/mysqladmin 2>&1 | grep -q MariaDB 2>&1 > /dev/null; then
+is_mariadb=yes
+else
+is_mariadb=no
+fi
+
+if [ 

Bug#930085: reportbug gtk gui crashes

2020-05-22 Thread Nis Martensen
control: merge 709862 930085
control: tags 709862 patch

> >   Traceback (most recent call last):
> > File "/usr/bin/reportbug", line 2285, in 
> >   main()
> > File "/usr/bin/reportbug", line 1115, in main
> >   return iface.user_interface()
> > File "/usr/bin/reportbug", line 1728, in user_interface
> >   latest_first=self.options.latest_first)
> > File "/usr/lib/python3/dist-packages/reportbug/ui/gtk_ui.py", line 
> > 1763, in func
> >   args, kwargs = op.sync_pre_operation(*args, **kwargs)
> >   TypeError: cannot unpack non-iterable NoneType object
> 
> 
> > -- System Information:
> > Distributor ID: Kali
> > Description:Kali GNU/Linux Rolling
> 
> The crash is very likely caused by a system administration error. Please see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892270

Anyway reportbug should not crash, not even on non-Debian systems. This
has been reported multiple times already; merging this bug with a
previous instance.

This can be fixed with a small change:
https://salsa.debian.org/reportbug-team/reportbug/-/merge_requests/60



Bug#960384: qutebrowser fails to start with critical qt message: Could not initialize GLX

2020-05-22 Thread Florian Bruhin
Hey,

Upstream here - no idea what's happening there I'm afraid. I'm guessing you'll
have similar issues with other Qt/QtWebEngine applications as well though, I
doubt this is qutebrowser-specific. Can you try with e.g. Falkon as well?

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature


Bug#912846: grub2: stop depending on ttf-dejavu-core

2020-05-22 Thread Fabian Greffrath
Control: reassign -1 grub2
Control: found -1 2.04-7
Control: retitle -1 please migrate to fonts-dejavu-core
Control: tags -1 =patch


I am reassigning this bug back again to the grub2 package.

The ttf-dejavu-core package has been a transitional package for 7 years
(!) now and its removal is going to happen with the next package
upload, which will be anytime soon. Please adjust your package's build-
dependencies to fonts-dejavu-core and add the corresponding search path
to configure.ac. I have already prepared a patch for the latter.

Thanks,

 - Fabian

From a696233f623e9c2b480aa3ad10aed537c2890af6 Mon Sep 17 00:00:00 2001
From: Fabian Greffrath 
Date: Tue, 19 May 2020 12:19:26 +0200
Subject: [PATCH] add /u/s/fonts/truetype/dejavu to the DejaVu fonts search
 paths

---
 configure.ac | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure.ac b/configure.ac
index b2576b0..41b8758 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1669,7 +1669,7 @@ fi
 
 if test x"$starfield_excuse" = x; then
for ext in pcf pcf.gz bdf bdf.gz ttf ttf.gz; do
- for dir in . /usr/src /usr/share/fonts/X11/misc /usr/share/fonts/truetype/ttf-dejavu /usr/share/fonts/dejavu /usr/share/fonts/truetype; do
+ for dir in . /usr/src /usr/share/fonts/X11/misc /usr/share/fonts/truetype/dejavu /usr/share/fonts/truetype/ttf-dejavu /usr/share/fonts/dejavu /usr/share/fonts/truetype; do
 if test -f "$dir/DejaVuSans.$ext"; then
   DJVU_FONT_SOURCE="$dir/DejaVuSans.$ext"
   break 2
-- 
2.26.2



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


Bug#960271: Status on bug 960271 - 'BITS_PER_LONG' wrongly used

2020-05-22 Thread Lukas Straub
Hello Everyone,
When will this fix be released?

Regards,
Lukas Straub


pgpiQp_Q0hiTt.pgp
Description: OpenPGP digital signature


Bug#961122: 1.5.0.87+dfsg1-1 is out of the way already

2020-05-22 Thread Julien Puydt
Hi,

I don't understand why you report a bug on 1.5.0.87+dfsg1-1 on the 20th
of may when testing has 1.5.0.87+dfsg1-4 since the 9th of march, and
unstable had it since the 4th of march.

Isn't the problem history already?

JP



Bug#961281: qgis-providers: crssync in postinst: free(): invalid pointer SIGABRT

2020-05-22 Thread Marcel Partap
Package: qgis-providers
Version: 3.10.5+dfsg-2+b1
Severity: normal

So the postinst script calls crssync which breaks:

free(): invalid pointer

Program received signal SIGABRT, Aborted.

#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x750bd55b in __GI_abort () at abort.c:79
#2  0x75116008 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x75222f3e "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x7511d3aa in malloc_printerr (str=str@entry=0x752210e0
"free(): invalid pointer") at malloc.c:5339
#4  0x7511ed9c in _int_free (av=, p=,
have_lock=0) at malloc.c:4173
#5  0x74bb757c in osgeo::proj::common::UnitOfMeasure::~UnitOfMeasure()
() at /lib/x86_64-linux-gnu/libproj.so.19
#6  0x750d6426 in __cxa_finalize (d=0x7fffed9b9000) at
cxa_finalize.c:83
#7  0x7fffed79cd93 in  () at /lib/x86_64-linux-gnu/libproj.so.15
#8  0x7fffe740 in  ()
#9  0x77fe36f3 in _dl_fini () at dl-fini.c:138



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

Kernel: Linux 5.5.0-1-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qgis-providers depends on:
ii  dpkg  1.19.7
ii  libc6 2.30-4
ii  libexpat1 2.2.9-1
ii  libgcc-s1 10.1.0-1
ii  libgdal26 3.0.4+dfsg-1+b6
ii  libhdf5-103-1 1.10.6+repack-2
ii  libnetcdf18   1:4.7.4-1
ii  libpq512.0-1+b1
ii  libqca-qt5-2  2.2.1-2
ii  libqca-qt5-2-plugins  2.2.1-2
ii  libqgis-core3.10.53.10.5+dfsg-2+b1
ii  libqgis-gui3.10.5 3.10.5+dfsg-2+b1
ii  libqscintilla2-qt5-15 2.11.2+dfsg-6+b1
ii  libqt5core5a [qtbase-abi-5-12-5]  5.12.5+dfsg-2
ii  libqt5gui55.12.5+dfsg-2
ii  libqt5network55.12.5+dfsg-2
ii  libqt5sql55.12.5+dfsg-2
ii  libqt5sql5-sqlite 5.12.5+dfsg-2
ii  libqt5webkit5 5.212.0~alpha3-5
ii  libqt5widgets55.12.5+dfsg-2
ii  libqt5xml55.12.5+dfsg-2
ii  libspatialite74.3.0a-6+b1
ii  libsqlite3-0  3.31.1-4
ii  libstdc++69.2.1-18
ii  libxml2   2.9.4+dfsg1-7+b3
ii  qgis-providers-common 3.10.5+dfsg-2

qgis-providers recommends no packages.

qgis-providers suggests no packages.

-- no debconf information



Bug#959865: New version fixes this issue

2020-05-22 Thread Martina Ferrari
Hi,

I was just trying this extension after moving from firefox-esr to
firefox/sid, and noticed it did not work.

But if I install the latest version from
https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/ it works
again, so packaging a new version should fix this.

-- 
Martina Ferrari (Tina)



Bug#926344: RFP into ITP for #926344 - libomemo packaging

2020-05-22 Thread Henry-Nicolas Tourneur

Dear,

Evangelos and myself are going to work on packaging libomemo via the 
Debian On Mobile team.
This package is a pre-requisite for purple-lurch which we would like to 
add into Debian as well, so that OMEMO would work with Chatty 
(currently in NEW).


Best regards,

Henry-Nicolas Tourneur
Matrix id: @hntourne:matrix.nilux.be



Bug#910108: RFP: git-bug -- Distributed bug tracker embedded in Git

2020-05-22 Thread Yaroslav Halchenko
I would have loved to see this one in debian as well!  May be someone
from Debian Go Team could have paved the way 

On Tue, 02 Oct 2018, Antoine Beaupre wrote:

> Package: wnpp
> Severity: wishlist

> * Package name: git-bug
>   Version : 0.3.0
>   Upstream Author : Michael Muré 
> * URL : https://github.com/MichaelMure/git-bug
> * License : GPL-3+
>   Programming Lang: Golang
>   Description : Distributed bug tracker embedded in Git

> git-bug is a distributed bug tracker embedded in git. It uses git's
> internal storage so no files are added in your project.

> As you would do with commits and branches, you can push your bugs to
> the same git remote you are already using to collaborate with other
> people.

> ==

> I've been maintaining bugs-everywhere (BE) in Debian for a while now,
> which accomplishes a similar goal, but with bugs stored in branches
> (or in files? i forgot). In any case, BE is unmaintained now and this
> looks like a promising alternative, particularly with future two-way
> integration with upstream bugtrackers (e.g. GitHub import for now).

> It probably has (too many) golang dependencies that need to be bundled
> and all that usual stuff.

> Golang team maintenance, most likely. Documented here to share it with
> the Debian community and make sure there's no work duplicated.

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik



  1   2   >