Bug#965943: cloud.debian.org: ec2 buster arm64 don't come online in us-east-2

[Ross Vandegrift]

Package: cloud.debian.org
Severity: normal
Usertags: aws

The buster arm64 images in us-east-2 don't seem to come online - ping and ssh
fail.  The ec2 status checks pass, but take unusually long to get there.  I
tried a1 and c6g instances.  There's nothing in the system log output, and no
screenshots on arm64.

I think it's the images since:
- amd64 in the same vpc, with the same security groups works correctly
- arm64 in us-west-2 & us-east-1 work correctly

Here's the images I tried:
  ami-0a5def50f0aa9c6a3
  ami-0a67a4b56b2021f1c
  ami-0b1808bb4e7ed5ff5

Ross

Bug#964100: iputils-arping should use alternatives to remove conflict with arping

[Salvatore Bonaccorso]

Hi Noah, Boian,

On Thu, Jul 02, 2020 at 10:32:28AM -0700, Noah Meyerhans wrote:
> On Wed, Jul 01, 2020 at 09:29:22PM +0300, Boian Bonev wrote:
> > I would like to propose a patch with alternatives support.
> > 
> > Before doing this there are some things to confirm:
> > 
> > - are you willing to accept such a patch?
> 
> It seems reasonable.  I have a vague (and possibly mistaken) memory that
> I looked in to doing this a number of years ago and found that it would
> not be appropriate to use alternatives for these two programs.  I don't
> remember the reasoning and I haven't managed to find any record of this,
> though.
> 
> I'd like to determine more definitively whether my memory is accurate or
> not before we proceed with this work, so please give me some time.

I have similar memory here, that due to both tools not having good
interchanability, that the alternatives systems would not be
appropriate here. But I have not found old records of possible
discussion for that.

If it is policy and best-practice conform doing so then I would not
object to such a plan, speaking with my src:arping maintainer hat on.
But my gut feeling here is that they cannot be drop-in replacements of
each other, that we would open problems.

Please do keep me in the loop for this discussion if possible
(subscribed to the bug, fwiw).

Regards,
Salvatore

Bug#964292: goldencheetah FTBFS: some qt incompatibility

[Satoru KURASHIKI]

hi,

On Sun, Jul 5, 2020 at 5:03 PM Helmut Grohne  wrote:
>
> Source: goldencheetah
> Version: 1:3.5~DEV1903-1
> Severity: serious
> Tags: ftbfs
>
> goldencheetah fails to build from source in unstable. The relevant
> failure is:
>
> | In file included from Metrics/PowerProfile.cpp:20:
> | Metrics/PowerProfile.h:77:37: error: field ‘values’ has incomplete type 
> ‘QMap >’
> |77 | QMap  > values;// key is 
> percentile; 99.99, 1, 95 etc
> |   | ^~
>
> It's multiple failing files. Reproduced by reproducible builds at
> https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/goldencheetah_3.5~DEV1903-1.rbuild.log.gz.
> Also seen by crossqa at
> http://crossqa.subdivi.de/build/goldencheetah_1:3.5%7EDEV1903-1_ppc64el_20200705072113.log.
> There we can also see that the issue wasn't present 17 days ago. Looks
> like QT somehow broke goldencheetah.
>
> Helmut

This was fixed in upstream, so I will fix it with newer package version 3.5.
cf. https://github.com/GoldenCheetah/GoldenCheetah/issues/3270

regards,
-- 
KURASHIKI Satoru

Bug#965942: barcode does not correctly encode XML characters in SVG output

[Timo Boettcher]

Package: barcode
Version: 0.99-3
Severity: normal
Tags: upstream

Dear Maintainer,

barcode does not correctly encode XML characters in svg output mode (-S),
leading at least to broken SVG documents. The plain text of the barcode is
embedded three times into the SVG document: Twice in a comment before and after
the actual barcode, once in a character-by-character fashion to show the
contents of the barcode.

When creating a "128" barcode of the character "<", this breaks the SVG file in
the character-by-character display:

$ barcode -S -e 128 -b "<"

http://www.w3.org/2000/svg; version="1.1" width="66pt" 
height="100pt">



[...]
<




Similarly, it is possible to break out of the comments:
$ barcode -S -e 128 -b "\"-->123"

Bug#965941: src:glibc: FTBFS with libselinux-dev (>= 3.1) due to deprecations warnings

[Aurelien Jarno]

Package: src:glibc
Version: 2.31-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)

Since the upload of libselinux 3.1 to unstable, glibc doesn't build
anymore due to deprecation warnings:

| ...
| x86_64-linux-gnu-gcc-10 makedb.c -c -std=gnu11 -fgnu89-inline  -pipe -O2 -g 
-fdebug-prefix-map=/home/aurel32/work/glibc/glibc-2.31=. -Wall -Wwrite-strings 
-Wundef -Werror -fmerge-all-constants -frounding-math -fstack-protector-strong 
-Wstrict-prototypes -Wold-style-definition -fmath-errno   -fpie   -isystem 
/home/aurel32/work/glibc/glibc-2.31/debian/include  -I../include 
-I/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss  
-I/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc  
-I../sysdeps/unix/sysv/linux/x86_64/64  -I../sysdeps/unix/sysv/linux/x86_64  
-I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86  
-I../sysdeps/x86/nptl  -I../sysdeps/unix/sysv/linux/wordsize-64  
-I../sysdeps/x86_64/nptl  -I../sysdeps/unix/sysv/linux/include 
-I../sysdeps/unix/sysv/linux  -I../sysdeps/nptl  -I../sysdeps/pthread  
-I../sysdeps/gnu  -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  
-I../sysdeps/unix/x86_64  -I../sysdeps/unix  -I../sysdeps/posix  
-I../sysdeps/x86_64/64  -I../sysdeps/x86_64/fpu/multiarch  
-I../sysdeps/x86_64/fpu  -I../sysdeps/x86/fpu/include -I../sysdeps/x86/fpu  
-I../sysdeps/x86_64/multiarch  -I../sysdeps/x86_64  -I../sysdeps/x86  
-I../sysdeps/ieee754/float128  -I../sysdeps/ieee754/ldbl-96/include 
-I../sysdeps/ieee754/ldbl-96  -I../sysdeps/ieee754/dbl-64/wordsize-64  
-I../sysdeps/ieee754/dbl-64  -I../sysdeps/ieee754/flt-32  
-I../sysdeps/wordsize-64  -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. 
-I../libio -I. -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/10/include 
-isystem /home/aurel32/work/glibc/glibc-2.31/debian/include  -D_LIBC_REENTRANT 
-include 
/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/libc-modules.h 
-DMODULE_NAME=nonlib -include ../include/libc-symbols.h  -DPIC 
-DTOP_NAMESPACE=glibc -o 
/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o -MD -MP 
-MF /home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o.dt 
-MT /home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o
| makedb.c: In function 'set_file_creation_context':
| makedb.c:849:3: error: 'security_context_t' is deprecated 
[-Werror=deprecated-declarations]
|   849 |   security_context_t ctx;
|   |   ^~
| makedb.c:863:3: error: 'matchpathcon' is deprecated: Use selabel_lookup 
instead [-Werror=deprecated-declarations]
|   863 |   if (matchpathcon (outname, S_IFREG | mode, ) == 0 && ctx != 
NULL)
|   |   ^~
| In file included from makedb.c:50:
| /usr/include/selinux/selinux.h:500:12: note: declared here
|   500 | extern int matchpathcon(const char *path,
|   |^~~~
| cc1: all warnings being treated as errors
| make[3]: *** [../o-iterator.mk:9: 
/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o] Error 1
| make[3]: *** Waiting for unfinished jobs
| make[3]: Leaving directory '/home/aurel32/work/glibc/glibc-2.31/nss'
| make[2]: *** [Makefile:487: nss/others] Error 2
| make[2]: Leaving directory '/home/aurel32/work/glibc/glibc-2.31'
| make[1]: *** [Makefile:9: all] Error 2
| make[1]: Leaving directory 
'/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc'
| make: *** [debian/rules.d/build.mk:114: 
/home/aurel32/work/glibc/glibc-2.31/stamp-dir/build_libc] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Bug#960748: node-babel: meta bug to keep out of testing

[peter green]

Last blockers for removal:

1. node-yarnpkg - #960120 - should be patched/fixed for 1.x or switch 
to 'berry'/2.x (supports babel 7) in time for bullseye
2. libjs-webrtc-adapte - #959798 - browserify-lite can be replaced by 
webpack

3. rainloop - #960021 - not in bullseye

Once the blockers are fixed, this should be changed to an RM bug.


It looks like several packages were missed that build-depend on the babeljs
virtual package which is provided by node-babel-cli

Namely (in testing, there may be others in unstable I don't know about)

node-ramda
node-globby
node-rollup-plugin-buble

Are these something you want to deal with centrally or should I file individual
bug reports?

Bug#965940: linux-image-5.7.0-1-amd64: general protection fault during apt upgrade

[Brian Paterni]

Package: src:linux
Version: 5.7.6-1
Severity: normal
X-Debbugs-Cc: bpate...@gmail.com

Dear Maintainer,

This seems to happen occasionally when software is being installed with `apt
upgrade` where the system becomes unresponsive. I can still kill currently
running processes, but I can't start new ones. After a reboot, the syslog
indicates that there was a general protection fault:

Jul 20 22:05:36 hafx kernel: [188301.288874] general protection fault, probably
for non-canonical address 0xffbf8fb327de77f8:  [#1] SMP NOPTI
Jul 20 22:05:36 hafx kernel: [188301.21] CPU: 7 PID: 695 Comm: sshd Not
tainted 5.7.0-1-amd64 #1 Debian 5.7.6-1
Jul 20 22:05:36 hafx kernel: [188301.23] Hardware name: To be filled by
O.E.M. To be filled by O.E.M./SABERTOOTH 990FX R2.0, BIOS 2501 04/08/2014
Jul 20 22:05:36 hafx kernel: [188301.288890] RIP:
0010:kmem_cache_alloc+0x73/0x220
Jul 20 22:05:36 hafx kernel: [188301.288892] Code: 99 01 00 00 4d 8b 06 65 49
8b 50 08 65 4c 03 05 4b 03 7a 5d 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 46
20 49 8b 3e 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9e 70 01 00 00 4c 89 e0 48 0f c9
48 31 cb
Jul 20 22:05:36 hafx kernel: [188301.288894] RSP: 0018:a458c06e7ce0 EFLAGS:
00010282
Jul 20 22:05:36 hafx kernel: [188301.288896] RAX: ffbf8fb327de77f8 RBX:
 RCX: 
Jul 20 22:05:36 hafx kernel: [188301.288897] RDX: 000ed0a0 RSI:
0cc0 RDI: 34a590c07660
Jul 20 22:05:36 hafx kernel: [188301.288899] RBP: 0cc0 R08:
c458bf9c7660 R09: 0010
Jul 20 22:05:36 hafx kernel: [188301.288900] R10:  R11:
 R12: ffbf8fb327de7790
Jul 20 22:05:36 hafx kernel: [188301.288901] R13: a267ff8a R14:
8fb328047b80 R15: 8fb007c22bc0
Jul 20 22:05:36 hafx kernel: [188301.288903] FS:  7f1ab4484f40()
GS:8fb32edc() knlGS:
Jul 20 22:05:36 hafx kernel: [188301.288905] CS:  0010 DS:  ES:  CR0:
80050033
Jul 20 22:05:36 hafx kernel: [188301.288906] CR2: 7feec0a0 CR3:
000425294000 CR4: 000406e0
Jul 20 22:05:36 hafx kernel: [188301.288908] Call Trace:
Jul 20 22:05:36 hafx kernel: [188301.288915]  vm_area_dup+0x1a/0x50
Jul 20 22:05:36 hafx kernel: [188301.288918]  dup_mm+0x2c5/0x590
Jul 20 22:05:36 hafx kernel: [188301.288921]  copy_process+0x17a1/0x1a10
Jul 20 22:05:36 hafx kernel: [188301.288924]  _do_fork+0x70/0x3a0
Jul 20 22:05:36 hafx kernel: [188301.288926]  __do_sys_clone+0x73/0x90
Jul 20 22:05:36 hafx kernel: [188301.288930]  do_syscall_64+0x52/0x180
Jul 20 22:05:36 hafx kernel: [188301.288934]
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jul 20 22:05:36 hafx kernel: [188301.288936] RIP: 0033:0x7f1ab3e07c50
Jul 20 22:05:36 hafx kernel: [188301.288938] Code: ed 0f 85 1b 01 00 00 64 4c
8b 0c 25 10 00 00 00 45 31 c0 4d 8d 91 d0 02 00 00 31 d2 31 f6 bf 11 00 20 01
b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 ac 00 00 00 41 89 c5 85 c0 0f 85
b9 00 00
Jul 20 22:05:36 hafx kernel: [188301.288940] RSP: 002b:7fff33460890 EFLAGS:
0246 ORIG_RAX: 0038
Jul 20 22:05:36 hafx kernel: [188301.288942] RAX: ffda RBX:
 RCX: 7f1ab3e07c50
Jul 20 22:05:36 hafx kernel: [188301.288944] RDX:  RSI:
 RDI: 01200011
Jul 20 22:05:36 hafx kernel: [188301.288945] RBP:  R08:
 R09: 7f1ab4484f40
Jul 20 22:05:36 hafx kernel: [188301.288946] R10: 7f1ab4485210 R11:
0246 R12: 
Jul 20 22:05:36 hafx kernel: [188301.288948] R13: 56129e8577a0 R14:
0001 R15: 
Jul 20 22:05:36 hafx kernel: [188301.288950] Modules linked in: xt_multiport
si2157 lgdt3306a i2c_mux nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype
br_netfilter overlay xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT
nf_reject_ipv4 xt_tcpudp nft_compat nft_counter nft_chain_nat nf_nat
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink bridge
stp llc binfmt_misc edac_mce_amd kvm_amd ccp rng_core kvm snd_hda_codec_realtek
snd_hda_codec_generic irqbypass ledtrig_audio ghash_clmulni_intel saa7164
tveeprom efi_pstore dvb_core eeepc_wmi asus_wmi battery sparse_keymap
snd_hda_codec_hdmi tun snd_hda_intel snd_usb_audio rfkill snd_intel_dspcfg
video pcspkr aesni_intel wmi_bmof efivars libaes snd_hda_codec crypto_simd
cryptd glue_helper snd_usbmidi_lib joydev videodev snd_hda_core snd_rawmidi
snd_seq_device snd_hwdep k10temp snd_pcm fam15h_power sp5100_tco watchdog sg mc
snd_timer snd soundcore evdev acpi_cpufreq loop parport_pc ppdev lp parport
sunrpc efivarfs ip_tables x_tables autofs4 ext4 crc16
Jul 20 22:05:36 hafx kernel: [188301.288994]  mbcache jbd2 crc32c_generic
dm_mod hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid sd_mod t10_pi
crc_t10dif crct10dif_generic ohci_pci amdgpu gpu_sched i2c_algo_bit ttm
crct10dif_pclmul mxm_wmi crct10dif_common crc32_pclmul drm_kms_helper
crc32c_intel r8169 ahci 

Bug#965939: O: lprng-doc -- lpr/lpd printer spooling system (documentation)

[Craig Small]

Package: wnpp
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I intend to orphan the lprng-doc package. I thought it was part of lprng
which I have also orphaned.

The package description is:
 The  LPRng  software  is an enhanced, extended, and portable  version
 of the Berkeley LPR software (the standards UNIX printer spooler)
 You can use this for local and remote printers.
 This is the documentation for LPRng

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAl8WYwYSHGNzbWFsbEBk
ZWJpYW4ub3JnAAoJEAIhZsD/PITjaiQQAI+sqyc1+9eTXCKcayGr5/yFn7xBhImZ
9WIIeYm8bQ8HwXIZzMRslWeHpCgNr3XWBrHsavchA8lWvjnzCeEP7drZmHj7Bztr
EQfRRhQ8Bb72D0Ty4ejAlsTi/mrPE0/8K4nCdq5sWrllhu2w2pbZouhPTEiTouyK
TsfHC5MHWUpmMi8RRskUNTYl/vLAtjtLXLp7hbwMycPjlQoRKQ3Uro8V+a3+cH1r
/4AbfjRD2uCS8qfR6cdfIgjcB9No+4SnOvVCPekO2JNRMkSRYdukfi7L2IwdJMc7
OxsrpFoYtGKylXbDYmwCUJnWWgX7Y/VlapEuvcV5JuSsQKkQput3Izgz4dI3W5w8
DSlgGHun5oJ/OM9wqkvmEYc44iG0uOk/GRQMCdE7QEcKugdeXmssewq5HiUTyPZ8
1AvhIDdH0m9FSyzUih+/6eO8HTDuVReRhxzBF+8N4Sj5lVVrvvup788ECA/ztGOj
OhOAw4m3KoV3BThs5afT8JomUepGAnqhYLxSRcOEiiKasXg9073VtD+t39wJzMjR
3390EMpBgu0sPuNbEiCxj/XzFHDBEPW8XJhhcTY4qe4zixzQ/pSaiaWAnCgUV6sj
jAYcTp+/FoqSRyLYXrt9T/6m9sqFsQXAT2ALofntyegDZtpIfuiM2f5WxX1bqKDe
c3RBTjZ6Tpgr
=E2yE
-END PGP SIGNATURE-

Bug#960966: unattended-upgrades pegs CPU at 100% for an extended period

[Paul Wise]

Package: unattended-upgrades
Version: 2.4
Followup-For: Bug #960966
Control: severity -1 important

I noticed this 100% CPU usage in unattended-upgrades too.

When I strace the process, it seems to be repeatedly stat()ing all the
files that it expects to be in /var/lib/apt/lists/ over and over again,
including both the files that exist and ones that do not exist because
apt doesn't write empty files to disk.

$ sudo strace -p 1359212 |& grep 
deb.debian.org_debian_dists_testing_main_source_Sources
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
stat("/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources",
 {st_mode=S_IFREG|0644, st_size=42687296, ...}) = 0
...

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#965938: dnssec-trigger-script: add new trust-ad option to /etc/resolv.conf when using local unbound resolver

[Paul Wise]

Package: dnssec-trigger
Version: 0.17+repack-3+b1
Severity: important
File: /usr/lib/dnssec-trigger/dnssec-trigger-script

It looks like the dnssec-trigger-script will need to be adapted to this
change in glibc in order to keep working:

glibc (2.31-0experimental2) experimental; urgency=medium

  Starting with glibc 2.31, the DNS stub resolver does not blindly trust the
  AD (authenticated data) flag, indicating a DNSSEC validation:

  - By default the name servers and the network path to them are treated as
untrusted. In this mode, the AD flag is not set in queries, and it is
automatically cleared in responses, indicating a lack of DNSSEC
validation.

  - A new trust-ad option, set via the options directive in /etc/resolv.conf
(or if RES_TRUSTAD is set in _res.options), indicates that the name
server is trusted. In this mode, the AD bit, as provided by the name
server, is made available to the applications.

  Therefore if you trust your name servers, for example because you use a
  locally running validating resolver (e.g. unbound, systemd-resolved or
  dnsmasq), you might want to add the following line to /etc/resolv.conf:

options trust-ad

 -- Aurelien Jarno   Sun, 17 May 2020 15:59:38 +0200

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

Versions of packages dnssec-trigger depends on:
ii  gir1.2-nm-1.0   1.26.0-1
iu  libc6   2.31-1
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-5
ii  libglib2.0-02.64.3-2
ii  libgtk2.0-0 2.24.32-4
ii  libldns31.7.1-2
ii  libssl1.1   1.1.1g-1
ii  python3 3.8.2-3
ii  python3-gi  3.36.0-3
ii  python3-lockfile1:0.12.2-2.2
ii  sensible-utils  0.0.12+nmu1
ii  unbound 1.10.1-1

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#965166: [Pkg-net-snmp-devel] Bug#965166: snmpd privilege escalation

[Bart Van Assche]

On 2020-07-19 20:25, Craig Small wrote:
> A patch has been applied to the Net-SNMP v5.8 and master branches that
> removes the EXTEND MIB from the list with default MIBs. See also commit
> c2b96ee74439 ("snmpd: Disable NET-SNMP-EXTEND-MIB support by default").
> 
> Is the single line removal in that commit all it needs? From what I can
> see the patch for v5.8 and master branches is just importing c2b96ee74439
> That will make things very easy to fix.

The above matches my understanding.

> Since Net-SNMP already
> supports other mechanisms for extending snmpd, e.g. the extend and
> extendfix directives in snmpd.conf, I propose to disable the EXTEND MIB.
> 
> I'm happy to see it go, for the reasons you point out.
> 
> Oddly enough, if you set the user in the configuration file and set it
> on the command line with the -u flag, the configuration file parameter
> wins. 
> 
> root       41574  0.0  0.0  23592 13768 ?        Ss   13:12   0:00
> /usr/sbin/snmpd -LOw -u Debian-snmp -g Debian-snmp -I -smux mteTrigger
> mteTriggerConf -f -p /run/snmpd.pid

A patch is under discussion that will change this behavior such that the
command line -u flag takes precedence if both the -u flag and the
agentuser configuration file parameter have been set. I hope that patch
will be applied a few days from now.

Bart.

Bug#965937: unp: package description now implies that lhasa is non-free

[Paul Wise]

Package: unp
Version: 2.0~pre8
Severity: minor

The package description now implies that lhasa is non-free, while it is
available in Debian main. I think it would be good to remove mention
of lhasa from the package description and add it to the Suggests.

$ pipetty apt show unp=2.0~pre8 | tail -n3
 You may also want to install some non-free packages like "unace-nonfree",
 "unrar-nonfree" and "lhasa" to extract archives of these types.

$ apt-cache show lhasa | grep Section
Section: utils

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#806947: coreutils: improve expr with huge numbers by GMP

[Jim Meyering]

On Mon, Jul 20, 2020 at 9:36 AM John Scott  wrote:
> > The reason it doesn't currently build that way is that it would
> > as a side effect raise the priority of libgmp, and I'm not sure that
> > using expr for big numbers is worth making libgmp mandatory on a minimal
> > debian install.
> It appears this is no longer the case, GMP is a required part of an install.
> The dependency chain now goes GMP → Nettle → GnuTLS → apt and systemd

This is resolved by
https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=v8.32-41-g67fc55d63
It allows to build GMP-supporting expr without libgmp.

Bug#965029: console-setup: fonts missing numerous unicode->font mappings for box-drawing characters

[Nick Black]

Anton Zinoviev left as an exercise for the reader:
> Оk.  I've attached updated versions of Arabic-Fixed16.psf, 
> Arabic-VGA16.psf and Lat15-Terminus16.psf.  Hopefully, this time the 
> fonts are ok.


Tested all three using the same methodology as outlined earlier.

Looks perfect =].

-- 
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.

Bug#965936: Update backport version qelectrotech

[Gleisson Jesuino Joaquim Cardoso]

Package: qelectrotech
Version: 0.6.1-1~bpo9+1

Dear Maintainer,
Congratulations on the great work done in packaging this excellent program.
I noticed that the qeleltrotech package, which is unstable and testing, has 
been in version 0.7.0-1 for some time.
Could you please include this version in the backport ? Because it brings 
great improvements over 0.6.1-1.
Thank you very much in advance.

.
⢀⣴⠾⠻⢶⣦⠀ Gleisson J. J. Cardoso
⣾⠁⢰⠒⠀⣿⡁ 63AA 56DD 134C A8E6 5E1E
⢿⡄⠘⠷⠚⠋⠀ 72EE 2E56 926F 5034 7551
⠈⠳⣄GPG: rsa4096/50347551

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

Bug#965934: lintian-brush: Set Rules-Requires-Root: no

[Jelmer Vernooij]

Hi Guilhem,

On Tue, Jul 21, 2020 at 01:45:28AM +0200, Guilhem Moulin wrote:
> While it's difficult to change the default value for Rules-Requires-Root:
> in dpkg-buildpackage, it's arguably less intrusive to do it in lintian-brush
> (at least in opinionated mode) as the maintainer has a chance to review
> the changes and compare binary packages before uploading.
> 
> The attached fixer can be used to unconditionally set ‘Rules-Requires-Root: 
> no’.
> I suppose it would be better to have some heuristics to try to guess
> whether d/rules requires root privileges, but for packages with simple d/rules
> and where upstream tests don't require privileged access the fixer is
> probably good enough :-)
Thanks for the patch!

I've committed this fixer to master with some minor changes. lintian-brush
works with certainty levels. By default, only changes with certainty
"certain" are included, with the idea that maintainers can just fire
and forget when running lintian-brush.

This script is now included with certainty "possible".
"lintian-brush --uncertain" will make lower certainty changes,
and warn when it does so.

Jelmer

Bug#965343: cinnamon-control-center: Upstream patch: Don't allow monitors to be dragged apart.

[Norbert Preining]

Hi

> There are many cc-display-panel.c commits upstream. Yet-I don't know which 
> ones are bug fixes but they look like speed/stability improvements.

I will upload a new package with just this one commit taken, and the
rest will come in with the next upstream release.

Best

Norbert

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

Bug#965932: libc6: breaks openssh-server/buster

[Matthew Gabeler-Lee]

Package: libc6
Version: 2.31-1
Followup-For: Bug #965932

Having the same issue, found an additional tidbit that may be of use:

When the failure happens, kernel logs a line like this:

Jul 20 20:04:38 hostname kernel: [  373.963787] audit: type=1326 
audit(1595289878.694:7): auid=4294967295 uid=100 gid=65534 ses=4294967295 
subj==unconfined pid=11667 comm="sshd" exe="/usr/sbin/sshd" sig=31 
arch=c03e syscall=230 compat=0 ip=0x7f6a9798fbea code=0x0

Also, Andreas notes:

> I haven't tried sshd/bullseye.

I did, and it works fine with the new libc6.

Sounds like libc6 needs a Breaks for openssh-server less than something
(exactly where it breaks I guess is TBD, but less than the 1:8.3p1-1 current
in bullseye seems safe).

-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-debug'), (500, 'testing'), (500, 
'oldstable'), (490, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-1-amd64 (SMP w/16 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)

Versions of packages libc6 depends on:
ii  libcrypt1  1:4.4.16-1
ii  libgcc-s1  10.1.0-6

Versions of packages libc6 recommends:
ii  libidn2-0  2.0.5-1+deb10u1

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.71
ii  glibc-doc  2.28-10
ii  libc-l10n  2.31-1
ii  locales2.31-1

-- debconf information:
  glibc/restart-failed:
* glibc/disable-screensaver:
* glibc/upgrade: true
* libraries/restart-without-asking: true
  glibc/kernel-not-supported:
* glibc/restart-services: spamassassin samba dovecot exim4 cups cron atd apache2
  glibc/kernel-too-old:

Bug#965935: MR link

[dann frazier]

https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/32

Bug#935035: u-boot: Olimex Teres-I support for builtin keyboard

[Jonas Smedegaard]

Quoting Vagrant Cascadian (2020-07-20 22:05:43)
> On 2020-07-19, Jonas Smedegaard wrote:
> > Patch is still needed, and I have now updated it upstream: 
> > https://patchwork.ozlabs.org/project/uboot/patch/20200719135632.681954-2...@jones.dk/
> 
> This link gets both patches:
> 
>   https://patchwork.ozlabs.org/project/uboot/list/?series=190758=*

Ah, that's helpful!


> It looks like they've gotten a few reviews already, and presuming no
> objections surface, I could apply them in the next u-boot 2020.07
> upload, and hopefully will be applied upstream for 2020.10.

Thanks.


> > The newest upstream patch is larger, because developers requested I 
> > do a more general change, where earlier proposed patches generalized 
> > only across sunxi devices.
> >
> > There should be no functional difference between the older more 
> > minimal patches and the newer one, and I therefore propose to apply 
> > the older one for Buster.
> 
> The wip-teres-i-keyboard branch on salsa?

Yes.


> That includes a bunch of changes for platforms (unifier) that we don't 
> support.

If you prefer a shorter patch with those plastforms being broken, then 
indeed I can reduce it.


> I think could probably be trimmed down to a more minimal patch. e.g. 
> It doesn't look like CONFIG_USE_PREBOOT is needed at all; I *think* 
> you could just use CONFIG_PREBOOT without adding Kconfig support 
> (needs testing) and then use ifdef/ifndef directly where the preboot 
> command is added.

Sorry, I don't follow how you think it could be done without per-board 
definitions.


> I'd normally be hesitant to add non-upstreamed patches, and will want 
> to wait to see how that plays out, but once the functionality lands in 
> experimental or unstable, I'd be willing to consider a more minimal 
> patch for buster.

Thanks.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#962872: ocrmypdf: new major upstream version available

[Sean Whitton]

Hello James,

On Sun 19 Jul 2020 at 08:00AM -07, James R Barlow wrote:

> I updated debian/copyright in both projects at the HEAD revision (not a
> tagged release). These files should reflect the current status.

Great.  I see you merged in my d/copyright.  Previously I'd not wanted
to bother you with that, but going forward, if I update d/copyright,
would you like PRs from me, or would you prefer to just merge in my
changes before making your own updates?

> I believe this means the updates shouldn't be too difficult, and also
> that the -dfsg version tag could be dropped from both
> packages. (pikepdf is now powerful enough that I can usually
> synthesize problematic constructs instead of adding another test
> resource.)

Thank you for the details here -- I will look into verifying whether it
can be dropped.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#965935: configure_networking() should wait for specified interface

[dann frazier]

Package: initramfs-tools-core
Version: 0.137
Severity: normal
Tags: patch

configure_networking() will do a `udevadm settle` before trying to configure
an interface. However it is possible for a NIC to appear after the event
queue has settled. This is pretty reproducible with a USB NIC I have.
There doesn't appear to be a good way to wait for all devices that
were connected at boot time to become available - `udevadm settle` is
just the closest thing we have.

However, in the case that the user has told us which interface they expect
to be used in the initramfs, we can just wait for it specifically. As a
bonus, this should shave off some time on systems where the NIC is available
before the udev event queue has emptied. I've a patch to do this, which
I'll submit as an MR in salsa.

Note: This should help out with the following issue in clevis, which
provides a mechanism for unlocking a LUKS root device from the initramfs
by communicating with a tang server:
  https://github.com/latchset/clevis/issues/145

-- 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)
Foreign Architectures: i386

Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages initramfs-tools-core depends on:
ii  coreutils8.32-3
ii  cpio 2.13+dfsg-3
ii  e2fsprogs1.45.6-1
ii  klibc-utils  2.0.7-1
ii  kmod 27+20200310-2
ii  logsave  1.45.6-1
ii  udev 245.6-3

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.30.1-5
ii  pigz 2.4-1+b1

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.10-1

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

-- no debconf information

Bug#954272: slurmd: SLURM not working with OpenMPI

[Lars Veldscholte]

On 20-07-2020 16:27, Alastair McKinstry wrote:


On 20/07/2020 14:52, Lars Veldscholte wrote:

Hi,

I believe I have found a solution.

I must confess that I still don't fully understand the difference 
between the various PMI APIs, and which ones are supported by OpenMPI, 
but I found that the recommended way is to use PMIx.


However, PMIx was not working on my system even though libpmix2 is 
installed:


# srun --mpi pmix ./a.out

srun: error: (null) [0] /mpi_pmix.c:133 [init] mpi/pmix: ERROR: 
pmi/pmix: can not load PMIx library


srun: error: Couldn't load specified plugin name for mpi/pmix: Plugin 
init() callback failed


srun: error: cannot create mpi context for mpi/pmix

srun: error: invalid MPI type 'pmix', --mpi=list for acceptable types

Running `strace srun --mpi=pmix ./a.out` revealed that SLURM is 
looking for the pmix library at 
`/usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so`, which does not exist, 
only `libpmix.so.2` exists.


Which code is trying to load libpmix.so ? The compiled code should be 
loading libpmix.so.2 directly; the libpmix.so should only be needed

at build-time.


srun is, I suppose. I've attached the entire strace output in case it's 
of any help.




Perhaps the problem is that libpmix-dev is not installed at compile 
time. I can add it as a Dependency of libopenmpi-dev.



Installing the package `libpmix-dev` installs this library (it 
symlinks it to the same file `libpmix.so.2` is symlinked to).


Now, `srun --mpi=pmix ./a.out` is working!

I'm not 100% sure, but I think that the package `libpmix2` should also 
install the file `libpmix.so`. The dev package shouldn't be required 
for that, right?


Lars


Regards

Alastair



Regards,

Lars

# strace srun --mpi=pmix_v3 ./a.out
execve("/usr/bin/srun", ["srun", "--mpi=pmix_v3", "./a.out"], 0x7ffd4f380370 /* 
17 vars */) = 0
brk(NULL)   = 0x563aea4e4000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, 
"/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64/x86_64/libz.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64/x86_64", 0x7ffe2154f320) = 
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64/libz.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64", 0x7ffe2154f320) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64/libz.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64", 0x7ffe2154f320) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/libz.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/tls", 0x7ffe2154f320) = -1 ENOENT (No 
such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64/x86_64/libz.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64/x86_64", 0x7ffe2154f320) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64/libz.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64", 0x7ffe2154f320) = -1 ENOENT 
(No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64/libz.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64", 0x7ffe2154f320) = -1 ENOENT 
(No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/libz.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm", {st_mode=S_IFDIR|0755, 
st_size=20480, ...}) = 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=34055, ...}) = 0
mmap(NULL, 34055, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2eddeec000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libz.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0203\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=113088, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f2eddeea000
mmap(NULL, 115088, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f2eddecd000
mprotect(0x7f2edded, 98304, PROT_NONE) = 0
mmap(0x7f2edded, 69632, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7f2edded
mmap(0x7f2eddee1000, 24576, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x14000) = 0x7f2eddee1000
mmap(0x7f2eddee8000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a000) = 0x7f2eddee8000
close(3)= 0

Bug#965934: lintian-brush: Set Rules-Requires-Root: no

[Guilhem Moulin]

Package: lintian-brush
Version: 0.72
Severity: wishlist
Tags: patch

Hi there,

While it's difficult to change the default value for Rules-Requires-Root:
in dpkg-buildpackage, it's arguably less intrusive to do it in lintian-brush
(at least in opinionated mode) as the maintainer has a chance to review
the changes and compare binary packages before uploading.

The attached fixer can be used to unconditionally set ‘Rules-Requires-Root: no’.
I suppose it would be better to have some heuristics to try to guess
whether d/rules requires root privileges, but for packages with simple d/rules
and where upstream tests don't require privileged access the fixer is
probably good enough :-)

Thanks for maintaining lintian-brush!
-- 
Guilhem.
#!/usr/bin/python3

from debmutate.control import ( ControlEditor )
from lintian_brush.fixer import report_result

require_root = "no"
updated = False

with ControlEditor() as updater:
if "Rules-Requires-Root" not in updater.source:
# XXX add some heuristics to set require_root = "yes" in common
# cases, like `debian/rules binary` chown(1)'ing stuff
updater.source["Rules-Requires-Root"] = require_root
updated = True

report_result(
"Set Rules-Requires-Root: %s." % require_root,
fixed_lintian_tags=["rules-requires-root-missing"])

if require_root == "no" and updated == True:
with open("/dev/tty", "w") as p:
  # ugly work around lintian-brush capturing the error output 
  p.write("NOTE: Don't forget to verify that the binaries built with this field present are identical!\n")


signature.asc
Description: PGP signature

Bug#659348: LibreJS updates

[Ben Finney]

On 20-Jul-2020, John Scott wrote:
> I've been making a little bit of progress on this.

Thank you for the update, and for continuing to make progress on this.

-- 
 \ “To punish me for my contempt of authority, Fate has made me an |
  `\   authority myself.” —Albert Einstein, 1930-09-18 |
_o__)  |
Ben Finney 

signature.asc
Description: PGP signature

Bug#965933: rlinetd: [INTL:pt] Initial Portuguese translation of manpage

[Américo Monteiro]

Package: rlinetd
Version: 0.9.1-3
3ags: l10n, patch-
Severity: wishlist

Updated Portuguese translation for  rlinetd's manpage
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' 

-- 
Melhores cumprimentos/Best regards,

Américo Monteiro




rlinetd_0.9.1-3_rlinetd-man.pt.po.gz
Description: application/gzip

Bug#937446: fixed in pygments 2.3.1+dfsg-4

[Samat K Jain]

Hello,

The:

Conflicts: python-pygments (<= 2.0~),

in python3-pygments breaks python-pygments, which is used by a lot of
software that has no migration path (mainly, MoinMoin).

Could we remove this so python3-pygments and python-pygments are
co-installable again?

Looking through
https://salsa.debian.org/python-team/modules/pygments/-/commit/a1327489535e69bd2a4417263e51aa645be749a5,
I don't see anything immediately obvious that would prevent co-installation.

Regards,
Samat



signature.asc
Description: OpenPGP digital signature

Bug#659348: LibreJS updates

[John Scott]

I've been making a little bit of progress on this. I'm kind of blocked by what 
appears to be a quirk with dh_webext, but otherwise I'm getting close to 
having a working package:
alioth-lists.debian.net/pipermail/pkg-mozext-maintainers/2020-July/008575.html

In the interim I've been getting started on the debian/copyright. Things I 
have done:
* upstream/metadata, watch file with digital signature
* cleaning bundled npm modules before build time (no repack needed)
* install Info documentation and register with doc-base

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

Bug#965932: libc6: breaks openssh-server/buster

[Andreas Beckmann]

Package: libc6
Version: 2.31-1
Severity: critical
Justification: breaks unrelated software; breaks remote access

TL;DR: sshd privsep child dies with SIGSYS in clock_nanosleep() (libc6 2.31-1)
while it succeeded using nanosleep() under libc6 2.30-8

The machine in question is running buster with some selected packages
(mainly compilers and development stuff) from bullseye (and is located
at a remote location).

The running kernel is 4.19.0-9-amd64 4.19.118-2.
openssh-server 1:7.9p1-10+deb10u2 is running.
After upgrading libc6 from 2.30-8 to 2.31-1 (which caused sshd to restart),
sshd was running, but dropped incoming connections during authentication.
Luckily I still had a terminal open and could downgrade again to 2.30-8
which restored accessibility.

Thanks to the people trying to guess usernames and passwords, I noticed this
difference in /var/log/auth.log:

with 2.31-1:
Jul 20 21:52:11 hostname sshd[25603]: Invalid user ping from 139.219.0.102 port 
39588
Jul 20 21:52:11 hostname sshd[25603]: pam_unix(sshd:auth): check pass; user 
unknown
Jul 20 21:52:11 hostname sshd[25603]: pam_unix(sshd:auth): authentication 
failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.219.0.102 
Jul 20 21:52:13 hostname sshd[25603]: Failed password for invalid user ping 
from 139.219.0.102 port 39588 ssh2

after downgrading to 2.30-8:
Jul 20 21:54:33 hostname sshd[26824]: Invalid user mickey from 51.83.131.123 
port 32822
Jul 20 21:54:33 hostname sshd[26824]: pam_unix(sshd:auth): check pass; user 
unknown
Jul 20 21:54:33 hostname sshd[26824]: pam_unix(sshd:auth): authentication 
failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.131.123 
Jul 20 21:54:35 hostname sshd[26824]: Failed password for invalid user mickey 
from 51.83.131.123 port 32822 ssh2
Jul 20 21:54:35 hostname sshd[26824]: Received disconnect from 51.83.131.123 
port 32822:11: Bye Bye [preauth]
Jul 20 21:54:35 hostname sshd[26824]: Disconnected from invalid user mickey 
51.83.131.123 port 32822 [preauth]


I can reproduce this by running sshd in a mininmal buster chroot and
upgrading libc6 (+ libgcc-s1 libcrypto1 libc-bin).
(There is even no need to restart sshd (which was started under 2.31-1) after
downgrading libc6 again to 2.30-8 to get it functional again.)
I haven't tried sshd/bullseye. I haven't tried booting with 2.31-1.

$ ssh -vvv foo@localhost -p 9922
[...]
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:/07awyZSdCd9QgaTWi1dn3kEg9rbZtYC+ejHd6ZFi2w
debug3: put_host_port: [127.0.0.1]:9922
debug3: put_host_port: [localhost]:9922
debug3: hostkeys_foreach: reading file "/home/beckmann/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file 
/home/beckmann/.ssh/known_hosts:4
debug3: load_hostkeys: loaded 1 keys from [localhost]:9922
debug1: Host '[localhost]:9922' is known and matches the ECDSA host key.
debug1: Found key in /home/beckmann/.ssh/known_hosts:4
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug1: Will attempt key: /home/beckmann/.ssh/id_dsa
debug1: Will attempt key: /home/beckmann/.ssh/id_ecdsa
debug1: Will attempt key: /home/beckmann/.ssh/id_ed25519
debug1: Will attempt key: /home/beckmann/.ssh/id_xmss
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: 
server-sig-algs=
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
Connection closed by 127.0.0.1 port 9922

# /usr/sbin/sshd -ddd
debug2: load_server_config: filename /etc/ssh/sshd_config
debug2: load_server_config: done config len = 328
debug2: parse_server_config: config /etc/ssh/sshd_config len 328
debug3: /etc/ssh/sshd_config:13 setting Port 9922
debug3: /etc/ssh/sshd_config:26 setting SyslogFacility LOCAL7
debug3: /etc/ssh/sshd_config:27 setting LogLevel DEBUG3
debug3: /etc/ssh/sshd_config:56 setting PasswordAuthentication yes
debug3: /etc/ssh/sshd_config:61 setting ChallengeResponseAuthentication no
debug3: /etc/ssh/sshd_config:84 setting UsePAM yes
debug3: /etc/ssh/sshd_config:89 setting X11Forwarding yes
debug3: /etc/ssh/sshd_config:93 setting PrintMotd no
debug3: /etc/ssh/sshd_config:111 setting AcceptEnv LANG LC_*
debug3: /etc/ssh/sshd_config:114 setting Subsystem sftp 
/usr/lib/openssh/sftp-server
debug1: sshd version OpenSSH_7.9, OpenSSL 1.1.1d  10 Sep 2019
debug1: private host key #0: ssh-rsa 
SHA256:Ny3efyKdYNkwzXduBRO9Fzl0k2K505paO5QFGGw0o1s
debug1: private host key #1: ecdsa-sha2-nistp256 
SHA256:/07awyZSdCd9QgaTWi1dn3kEg9rbZtYC+ejHd6ZFi2w
debug1: private host key #2: ssh-ed25519 
SHA256:COeHE8usWY7gfl1+F5DqGx8pptr/4duLPiaPai3J5uo
debug1: 

Bug#964805: Debian Sid HP PA-RISC init (pid 1): Unaligned data reference (code 28) at f8affb6f

[Helge Deller]

On 20.07.20 23:41, John David Anglin wrote:
> Is it possible to use a PA 2.0 kernel?
> It uses ldcw,co which only needs 4-byte alignment.

There is no support for 64bit (PA2.0) in qemu yet.

Helge

Bug#964805: Debian Sid HP PA-RISC init (pid 1): Unaligned data reference (code 28) at f8affb6f

[John David Anglin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
 
Is it possible to use a PA 2.0 kernel?  It uses ldcw,co which only needs 4-byte 
alignment.

Only very old versions of glibc use ldcw directly in userspace.

On 2020-07-20 5:33 p.m., Helge Deller wrote:
> The relevant error is:
>  Not-handled unaligned insn 0x0f8011dc
> which translates to this assembler statement:
>  ldcw 0(ret0),ret0
>
> The ldcw expects an 16-byte aligned address, but in some specific version of
> hppa's glibc implementation was a bug which could not guarantee this.  
>
>>> Let me know if you need this VM qcow2 image. CDROM image downloaded from
>>> https://cdimage.debian.org/cdimage/ports/current/debian-10.0.0-hppa-NETINST-1.iso
>
> You either need a fixed install media, or even better an updated
> qemu build which reports this misalignment instead of stopping.
>  
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964805
>


- -- 
John David Anglin  dave.ang...@bell.net
-BEGIN PGP SIGNATURE-
 
iQIzBAEBCAAdFiEEnRzl+6e9+DTrEhyEXb/Nrl8ZTfEFAl8WD34ACgkQXb/Nrl8Z
TfGZ+A/+L04rBn2KcTqANx8e0t29IUV5OrkId0Z2DuQumJDLU2wBkthv+NwVbd3Z
RoMpqB98Z+XjRqeRYZEOmcbf9w/jUbgHnvnQyeCEO+SZrZh6dWhQLQEnR7WcI2JL
CMxxx3EUqZAg/B/Ge2iGq3ebFs2UZctAtjzPY8zbDUOQmAt4679geOYn1MH8P2zj
CXPlBzUT8tnWTkW7Ey6IJyNUkqy0cRpaladOzDCbgN9ZYD8H7kt9+7nJM/0J87ae
AtLPHhrjWLNg/RQeI+AGfyOGN0IKHGz+ECBAZB4ASWvZ0KJ+FphY1LdZTA6vVYVC
TjWHCW1f/uNaPqRyVh1LWQd7GHIAK3e/49lEEG17qFuyPxWX5rtLYyU9qP6DtQQh
Uug5TunlkYa+KCm2tb+pljwEhh864nSX8vdm4IfkK/YUzysDiER8Ie+k6hccZHeu
HcsWo7VXVo5w3vbI2kA/Bf9vItd+JX0DSiz4iZuZO8ef+k/SMgmmAxQc0C6/Qv7a
e1mp1NaXXly6HURbwicQ33mi06vQuMeL13+gQw4gQXrXB6U15ORz0NKOkEBn6h27
2JxYj/IEY9hiF3Lonhdqnuu0UGkeaFGhYeYbFZfW7qzYOFo5bPvfI9t5fHuU93kl
y1AoZBUcqZ14PRlzTIev3ID/hsMzDX5Qsu9qQ++mg7OL28/PIVY=
=rCsP
-END PGP SIGNATURE-

Bug#965384: repsnapper: syntax error in desktop file; causes flwm postinst failure

[Laurent Bonnaud]

Package: repsnapper
Version: 2.5a5-2+b1
Severity: normal


Dear Maintainer,

here is the problem:

Setting up flwm (1.02+git2015.10.03+7dbb30-7) ...
Exec key for 'repsnapper' contains '%F', '%U' or '%D' at the wrong place
dpkg: error processing package flwm (--configure):


-- 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.7.0-1-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--
Laurent.

Bug#925676: faumachine: ftbfs with GCC-9

[stefan]

Hi,

current FAUmachine git builds fine with gcc-9
(https://gitlab.cs.fau.de/faumachine/faumachine.git),
and I've updated packaging (unfortunately not stored in a public VCS).

However, there is still an issue with python2->python3 migration,
see (#943061). Current status is that scripts/faum-tragesym does
not yet work with python3 (it's a script taken from gEDA project
and slightly adapted for FAUmachine). I've started porting, but
can't say for sure when it will be done.

If anyone wants to help, just give me a ping.

Cheers,
  Stefan.


signature.asc
Description: PGP signature

Bug#964805: Debian Sid HP PA-RISC init (pid 1): Unaligned data reference (code 28) at f8affb6f

[Helge Deller]

The relevant error is:
 Not-handled unaligned insn 0x0f8011dc
which translates to this assembler statement:
 ldcw 0(ret0),ret0

The ldcw expects an 16-byte aligned address, but in some specific version of
hppa's glibc implementation was a bug which could not guarantee this.  

>> Let me know if you need this VM qcow2 image. CDROM image downloaded from
>> https://cdimage.debian.org/cdimage/ports/current/debian-10.0.0-hppa-NETINST-1.iso

You either need a fixed install media, or even better an updated
qemu build which reports this misalignment instead of stopping.
 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964805



signature.asc
Description: OpenPGP digital signature

Bug#965931: Please enable Intel I225-LM/I225-V support

[Sergio Durigan Junior]

Package: linux-image-amd64
Version: 5.7.6-1
Severity: wishlist

Hi,

Please consider enabling support for the Intel I225-LM/I225-V network
cards.  I have a machine with an I225-V and I have to recompile Linux in
order to use it.

The config setting is:

  CONFIG_IGC=m

Thank you in advance!

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


signature.asc
Description: PGP signature

Bug#965930: RFS: taptempo/1.4.5-1 -- command line tap tempo

[François Mazen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: taptempo
   Version : 1.4.5-1
   Upstream Author : Francois Mazen 
 * URL : https://taptempo.tuxfamily.org
 * License : GPL-3.0+
 * Vcs : https://salsa.debian.org/mzf/taptempo
   Section : sound

It builds those binary packages:

  taptempo - command line tap tempo

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/t/taptempo/taptempo_1.4.5-1.dsc

Changes since the last upload:

   * New upstream release
   * Change Vcs-Browser and Vcs-Git to Salsa
   * Bump standard version to 4.5.0
   * Fix lintian warnings

Regards,

François


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

Bug#963081: src:camera.app: Please switch to using pkg-config for libgphoto2

[Yavor Doganov]

Sudip Mukherjee wrote:
> On Fri, Jun 19, 2020 at 09:41:22PM +0300, Yavor Doganov wrote:
> > wf...@niif.hu wrote:
> > > Yavor Doganov  writes:
> > > > Thanks; I'll fix this shortly -- the upload will depend on my sponsor
> > > > though.  Meanwhile, feel free to upload libgphoto2 whenever you like
> > > > and raise the severity of this bug to serious.
> > > 
> > > Did so, thanks.  I'm willing to sponsor your upload fixing this issue if
> > > needed.
> > 
> > It has a bunch of other changes so I'm not sure you'll be comfortable
> > reviewing them.  And I've already contacted my sponsor...  Anyway, the
> > updated package is available at mentors.d.n and also on Salsa.
> 
> Fixing the FTBFS is fairly simple and the attached patch is sufficient.
> Might be worth doing the NMU as it has been removed from testing.

I've already pushed Ferenc's fix plus some other changes so please
don't NMU it.  Pinging my sponsor again (sorry to disturb you, Peter).

Bug#965929: pytest: Please consider updating to version 5.4

[Christian Kastner]

Source: pytest
Version: 4.6.11
Severity: wishlist

This is just a friendly request to please consider updating to version
5.4 of pytest :-)

Bug#965371: resolve: enable RES_TRUSTAD towards the 127.0.0.53 stub resolver

[Michael Biebl]

Am 20.07.20 um 15:38 schrieb Johan Fleury:
> Package: systemd
> Version: 245.6-3
> Severity: wishlist
> Tags: patch
> X-Debbugs-Cc: jfle...@arcaik.net
> 
> Since glibc 2.31, the resolvers in /etc/resolve.conf are not trusted
> anymore and the AD flag is stripped from their responses.
> 
> As systemd-resolved is listening on a loopback interface, the `trust-ad`
> option was added to its stub resolve.conf file by upstream commit
> a742f98[^1].
> 
> It would be great if this commit could be backported to systemd 245 in Sid,
> waiting for version 246 to be released by upstream.
> 
> [^1]: 
> https://github.com/systemd/systemd/commit/a742f9828ea73d9c2c9bafe701c10fe60f058012
> 

Isn't this a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960023 ?




signature.asc
Description: OpenPGP digital signature

Bug#963081: src:camera.app: Please switch to using pkg-config for libgphoto2

[Sudip Mukherjee]

On Fri, Jun 19, 2020 at 09:41:22PM +0300, Yavor Doganov wrote:
> wf...@niif.hu wrote:
> > Yavor Doganov  writes:
> > 
> > > Thanks; I'll fix this shortly -- the upload will depend on my sponsor
> > > though.  Meanwhile, feel free to upload libgphoto2 whenever you like
> > > and raise the severity of this bug to serious.
> > 
> > Did so, thanks.  I'm willing to sponsor your upload fixing this issue if
> > needed.
> 
> It has a bunch of other changes so I'm not sure you'll be comfortable
> reviewing them.  And I've already contacted my sponsor...  Anyway, the
> updated package is available at mentors.d.n and also on Salsa.

Fixing the FTBFS is fairly simple and the attached patch is sufficient.
Might be worth doing the NMU as it has been removed from testing.

--
Regards
Sudip
diff -Nru camera.app-0.8.0/debian/rules camera.app-0.8.0/debian/rules
--- camera.app-0.8.0/debian/rules	2018-02-07 12:12:59.0 +
+++ camera.app-0.8.0/debian/rules	2020-07-20 21:11:00.0 +0100
@@ -17,8 +17,8 @@
 
 # override GNUmakefile.preamble
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
-export ADDITIONAL_INCLUDE_DIRS += `/usr/lib/$(DEB_HOST_MULTIARCH)/libgphoto2-dev/bin/gphoto2-config --cflags`
-export ADDITIONAL_GUI_LIBS += `/usr/lib/$(DEB_HOST_MULTIARCH)/libgphoto2-dev/bin/gphoto2-config --libs`
+export ADDITIONAL_INCLUDE_DIRS += `pkg-config libgphoto2 --cflags`
+export ADDITIONAL_GUI_LIBS += `pkg-config libgphoto2 --libs`
 
 %:
 	dh $@

Bug#965928: ITP: proftpd-mod-proxy -- ProFTPD module mod_proxy

[Hilmar Preusse]

Package: wnpp
Severity: wishlist
Owner: Hilmar Preusse 
X-Debbugs-Cc: debian-de...@lists.debian.org, 
pkg-proftpd-maintain...@alioth-lists.debian.net

* Package name: proftpd-mod-proxy
  Version : 0.5
  Upstream Author : TJ Saunders
* URL : https://github.com/Castaglia/proftpd-mod_proxy
* License : GPL2+
  Programming Lang: C
  Description : ProFTPD module mod_proxy

According to the upstream author this is one of the popular
modules in proftp. Hence I'm wondering why we don't have it in
Debian.

I plan to maintain it in the "Debian ProFTPD Team".

Bug#965927: lintian: False positive for jQuery + Underscore

[Christian Kastner]

Package: lintian
Version: 2.84.0
Severity: minor

When preparing src:numpydoc 1.1.0-1, lintian reported source-is-missing
errors for minimized jquery.js and underscore.js files even though there
are corresponding regular copies of the same version of those files
in the same directory [1]:

  jquery-3.5.1.js
  jquery.js
  underscore-1.3.1.js
  underscore.js

[1] 
https://sources.debian.org/src/numpydoc/1.1.0-1/numpydoc/tests/tinybuild/_build/html/_static/

I fixed this with an override, but the tag info asked to report a false
positive as a bug.

The only noteworthy thing about this setup is that this is a
sphinx-based documentation build used solely as a test artifact.


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

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

Versions of packages lintian depends on:
ii  binutils  2.34.90.20200706-1
ii  bzip2 1.0.8-3
ii  diffstat  1.63-1
ii  dpkg  1.20.5
ii  dpkg-dev  1.20.5
ii  file  1:5.38-5
ii  gettext   0.19.8.1-10
ii  gpg   2.2.20-1
ii  intltool-debian   0.35.0+20060710.5
ii  libapt-pkg-perl   0.1.36+b3
ii  libarchive-zip-perl   1.68-1
ii  libcapture-tiny-perl  0.48-1
ii  libclass-xsaccessor-perl  1.19-3+b5
ii  libclone-perl 0.45-1
ii  libconfig-tiny-perl   2.24-1
ii  libcpanel-json-xs-perl4.19-1
ii  libdata-validate-domain-perl  0.10-1
ii  libdevel-size-perl0.83-1+b1
ii  libdpkg-perl  1.20.5
ii  libemail-address-xs-perl  1.04-1+b2
ii  libfile-basedir-perl  0.08-1
ii  libfile-find-rule-perl0.34-1
ii  libfont-ttf-perl  1.06-1
ii  libhtml-parser-perl   3.72-5
ii  libio-async-loop-epoll-perl   0.21-1
ii  libio-async-perl  0.77-3
ii  libjson-maybexs-perl  1.004002-1
ii  liblist-compare-perl  0.53-1
ii  liblist-moreutils-perl0.416-1+b5
ii  liblist-utilsby-perl  0.11-1
ii  libmoo-perl   2.004000-1
ii  libmoox-aliases-perl  0.001006-1
ii  libnamespace-clean-perl   0.27-1
ii  libpath-tiny-perl 0.114-1
ii  libsereal-decoder-perl4.017+ds-1
ii  libsereal-encoder-perl4.017+ds-1
ii  libtext-levenshteinxs-perl0.03-4+b7
ii  libtext-xslate-perl   3.5.8-1
ii  libtime-duration-perl 1.21-1
ii  libtime-moment-perl   0.44-1+b2
ii  libtimedate-perl  2.3300-1
ii  libtry-tiny-perl  0.30-1
ii  libtype-tiny-perl 1.010002-1
ii  libunicode-utf8-perl  0.62-1+b1
ii  liburi-perl   1.76-2
ii  libxml-libxml-perl2.0134+dfsg-2
ii  libxml-writer-perl0.625-1
ii  libyaml-libyaml-perl  0.82+repack-1
ii  man-db2.9.3-2
ii  patchutils0.4.2-1
ii  perl [libdigest-sha-perl] 5.30.3-4
ii  t1utils   1.41-4
ii  xz-utils  5.2.4-1+b1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b6

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  libtext-template-perl  1.59-1

-- debconf-show failed

Bug#964805: Debian Sid HP PA-RISC init (pid 1): Unaligned data reference (code 28) at f8affb6f

[Michael Biebl]

Control: tags -1 + help
Control: user -1 debian-h...@lists.debian.org
Control: usertags -1 + hppa

Hi Anton,

hppa is no longer a supported architecture.
If you want to see this fixed, you'll need to provide a patch and get
that accepted upstream or have to work with someone who can help with that.
For that, I've CCed the hppa mailing list and usertagged the bug report
accordingly.
Last time we had an hppa issue, John David Anglin was very helpful.
Maybe he can chime in here as well

Regards,
Michael


On Sat, 11 Jul 2020 01:01:48 +0800
=?UTF-8?B?0JDQvdGC0L7QvSDQmtC+0YfQutC+0LI=?= 
wrote:
> Package: systemd-sysv
> Version: 245.6-1
> 
> I attached installation and running scripts at the bottom. I ran
> Debian 10.0.0 installation cdrom with Qemu 4.2.0, installation went
> fine but the bus error appears all the time while running.
> 
> Let me know if you need this VM qcow2 image. CDROM image downloaded from
> https://cdimage.debian.org/cdimage/ports/current/debian-10.0.0-hppa-NETINST-1.iso
> 
> QEMU emulator version 4.2.0 (qemu-4.2.0-7.fc32)
> 
> Formatting 'debian-10.0.0-hppa-hdd.qcow2', fmt=qcow2 size=4294967296
> cluster_size=65536 lazy_refcounts=off refcount_bits=16
> WARNING: Image format was not specified for 'json:{"fat-type": 0,
> "backing": {"driver": "vvfat_write_target"}, "dir": "share/",
> "driver": "vvfat", "floppy": false, "rw": true, "write-target":
> {"driver": "qcow", "file": {"driver": "file", "filename":
> "/var/tmp/vl.2AiM5z"}}}' and probing guessed raw.
>  Automatically detecting the format is dangerous for raw
> images, write operations on block 0 will be restricted.
>  Specify the 'raw' format explicitly to remove the restrictions.
> qemu-system-hppa: warning: Guest expects a stronger memory ordering
> than the host provides
> This may cause strange/hard to debug errors
> 
> Firmware Version 6.1
> 
> Duplex Console IO Dependent Code (IODC) revision 1
> 
> Memory Test/Initialization Completed
> 
> --
>   (c) Copyright 2017-2018 Helge Deller  and SeaBIOS developers.
> --
> 
>   Processor   SpeedState   Coprocessor State  Cache Size
>   -     -  -  --
>   0  250 MHzActive Functional0 KB
>   1  250 MHzIdle   Functional0 KB
>   2  250 MHzIdle   Functional0 KB
>   3  250 MHzIdle   Functional0 KB
> 
> 
>   Available memory: 512 MB
>   Good memory required: 16 MB
> 
>   Primary boot path:FWSCSI.0.0
>   Alternate boot path:  FWSCSI.1.0
>   Console path: SERIAL_1.9600.8.none
>   Keyboard path:PS2
> 
> Available boot devices:
> 1. DVD/CD [lsi 00:00.0 1:0 Drive QEMU QEMU CD-ROM 2.5+]
> 2. lsi 00:00.0 0:0 Drive QEMU QEMU HARDDISK 2.5+
> 3. lsi 00:00.0 2:0 Drive QEMU QEMU HARDDISK 2.5+
> 
> Booting from DVD/CD [lsi 00:00.0 1:0 Drive QEMU QEMU CD-ROM 2.5+]
> 
> Booting...



signature.asc
Description: OpenPGP digital signature

Bug#965235: libreoffice: “Personal Edition”, WTF‽

[Rene Engelhard]

Hi,

Am 20.07.20 um 21:46 schrieb Thorsten Glaser:
> Thanks for the update! Feel free to close this any time you want. 

Will do when that change actually is there..


Regards,


Rene

Bug#965926: botch: FTBFS in sid

[Gianfranco Costamagna]

Source: botch
Version: 0.22-4
Severity: serious

Hello, the same that happened to other ocaml packages is now happening to botch 
too.

If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
   dh_dwz
dwz: debian/botch/usr/bin/botch-annotate-strong: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-bin2src: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-build-fixpoint: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-buildcheck-more-problems: DWARF version 0 
unhandled
dwz: debian/botch/usr/bin/botch-buildgraph2srcgraph: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-calculate-fas: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-clean-repository: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-collapse-srcgraph: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-create-graph: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-distcheck-more-problems: DWARF version 0 
unhandled
dwz: debian/botch/usr/bin/botch-find-fvs: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-optuniv: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-partial-order: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-print-stats: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-src2bin: DWARF version 0 unhandled
dwz: Too few files for multifile optimization
dh_dwz: error: dwz 
-mdebian/botch/usr/lib/debug/.dwz/x86_64-linux-gnu/botch.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/botch.debug -- 
debian/botch/usr/bin/botch-annotate-strong debian/botch/usr/bin/botch-bin2src 
debian/botch/usr/bin/botch-build-fixpoint 
debian/botch/usr/bin/botch-buildcheck-more-problems 
debian/botch/usr/bin/botch-buildgraph2srcgraph 
debian/botch/usr/bin/botch-calculate-fas 
debian/botch/usr/bin/botch-clean-repository 
debian/botch/usr/bin/botch-collapse-srcgraph 
debian/botch/usr/bin/botch-create-graph 
debian/botch/usr/bin/botch-distcheck-more-problems 
debian/botch/usr/bin/botch-find-fvs debian/botch/usr/bin/botch-optuniv 
debian/botch/usr/bin/botch-partial-order debian/botch/usr/bin/botch-print-stats 
debian/botch/usr/bin/botch-src2bin returned exit code 1
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



I still don't understand if the problem is in binutils or somewhere else

G.

Bug#935035: u-boot: Olimex Teres-I support for builtin keyboard

[Vagrant Cascadian]

On 2020-07-19, Jonas Smedegaard wrote:
> Quoting Jonas Smedegaard (2020-04-27 09:00:49)
>> Quoting Vagrant Cascadian (2020-04-20 19:25:15)
>> > Control: tags 935035 moreinfo
>> > 
>> > On 2019-08-18, Jonas Smedegaard wrote:
>> > > U-Boot supports the DIY laptop Olimex Teres-I, except the builtin
>> > > keyboard is not detected.
>> > ...
>> > > A working patchset is pushed to git branch wip-teres-i-keyboard:
>> > > https://salsa.debian.org/debian/u-boot/tree/wip/teres-i-keyboard
>> > ...
>> > > This patchset is not in mainline U-Boot, but I intent to propose it.
>> > 
>> > Any status update on mainline support? Is it still an issue with newer 
>> > u-boot packages in Debian?
>> 
>> Last I checked it was still needed.
>> 

>> I noticed a recent change to the USB driver (commit 31232de) that 
>> *might* render all or half of my patch unnecessary, but that's just a 
>> guess based on the commit message - needs to be actually tested.
>> 
>> If still needed, then status of the patch is that U-boot developers 
>> wants a more general cleanup of the related options, won't accept my 
>> minimal patch as-is.  Again, I have not yet taken the time to do that.
>
> Patch is still needed, and I have now updated it upstream: 
> https://patchwork.ozlabs.org/project/uboot/patch/20200719135632.681954-2...@jones.dk/

This link gets both patches:

  https://patchwork.ozlabs.org/project/uboot/list/?series=190758=*

It looks like they've gotten a few reviews already, and presuming no
objections surface, I could apply them in the next u-boot 2020.07
upload, and hopefully will be applied upstream for 2020.10.


> The newest upstream patch is larger, because developers requested I do a 
> more general change, where earlier proposed patches generalized only 
> across sunxi devices.
>
> There should be no functional difference between the older more minimal 
> patches and the newer one, and I therefore propose to apply the older 
> one for Buster.

The wip-teres-i-keyboard branch on salsa?

That includes a bunch of changes for platforms (unifier) that we don't
support.

I think could probably be trimmed down to a more minimal patch. e.g. It
doesn't look like CONFIG_USE_PREBOOT is needed at all; I *think* you
could just use CONFIG_PREBOOT without adding Kconfig support (needs
testing) and then use ifdef/ifndef directly where the preboot command is
added.

I'd normally be hesitant to add non-upstreamed patches, and will want to
wait to see how that plays out, but once the functionality lands in
experimental or unstable, I'd be willing to consider a more minimal
patch for buster.


> Please tell me if you disagree, then I will prepare a backport of the 
> newest more general patchset.

I think the full patchsets are too invasive for buster, so would prefer
to avoid it.


> Or, obviously, please tell me if you consider it unlikely that this 
> change can be accepted in Buster, so we stop spend more time on that.

I think it can be done, but we'll have to be careful not to break other
platforms. I have several other platforms (pine64+, pinebook, others)
that might be impacted by these changes, so can check for breakage at
least.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#965721: mgp: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Thorsten Glaser]

Niels Thykier dixit:

>The package mgp uses debhelper with a compat level of 5 or 6,
>which is deprecated and scheduled for removal[1].

OK. I have a large update coming anyway, it’s missing a few
regression fixes though :/

>Please bump the debhelper compat at your earliest convenience
>/outside the freeze/!

Thanks for the ahead-of-time notice.

bye,
//mirabilos
-- 
Stéphane, I actually don’t block Googlemail, they’re just too utterly
stupid to successfully deliver to me (or anyone else using Greylisting
and not whitelisting their ranges). Same for a few other providers such
as Hotmail. Some spammers (Yahoo) I do block.

Bug#965925: Updating the telepathy-python Uploaders list

[Pierre-Elliott Bécue]

Source: telepathy-python
Version: 0.15.19-3
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Dafydd Harries  has not been working on
the telepathy-python package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965028: systemd: journalctl does not work for normal users at all

[Michael Biebl]

Control: reassign -1 user-setup
Control: retitle -1 add admin user to group systemd-journal

I'm going to reassign this bug report to user-setup which I think is the
debian-installer component responsible for setting up the initial group
memberships.

Whether such a change is suitable for a stable release is up to the
user-setup maintainers to decide.

Regards,
Michael


Am 19.07.20 um 01:02 schrieb Daniel Blaschke:
> If adm is the only group necessary for log-access in bullseye, then it's
> probably all good.
> It would however be nice to see a fix also in buster (ie busters debian
> installer at the next point release).
>  Cheers,
> Daniel
> 
> On Thu, 16 Jul 2020, Michael Biebl wrote:
> 
>> Am 15.07.20 um 12:52 schrieb Michael Biebl:
>>> Am 15.07.20 um 01:19 schrieb Daniel Blaschke:
 OK, so now it works after rebooting - logging out and back in was not
 enough after adding myself to the groups apparently; sorry for the
 noise.
 Could this bug perhaps be reassigned to the debian-installer?
 Kind of think the primary admin user (which is set up during a fresh
 install) should be added to those groups by default.
>>>
>>> I think with bullseye this issue is mostly moot as a persistent journal
>>> is now the default and the /var/log/journal directory has an ACL with
>>> read permissions for the "adm" group and the admin user is already added
>>> to this group.
>>>
>>> buster:
>>>
>>> # getfacl /run/log/journal/
>>> getfacl: Removing leading '/' from absolute path names
>>> # file: run/log/journal/
>>> # owner: root
>>> # group: systemd-journal
>>> # flags: -s-
>>> user::rwx
>>> group::r-x
>>> other::r-x
>>>
>>> bullseye:
>>>
>>> # getfacl /var/log/journal/
>>> getfacl: Removing leading '/' from absolute path names
>>> # file: var/log/journal/
>>> # owner: root
>>> # group: systemd-journal
>>> # flags: -s-
>>> user::rwx
>>> group::r-x
>>> group:adm:r-x
>>> mask::r-x
>>> other::r-x
>>> default:user::rwx
>>> default:group::r-x
>>> default:group:adm:r-x
>>> default:mask::r-x
>>> default:other::r-x
>>>
>>
>> Do you see any value in adding users to the more explicit
>> systemd-journal group? If not, I'd just close this bug report.
>>
>> Regards,
>> Michael
>>
>>




signature.asc
Description: OpenPGP digital signature

Bug#965540: gcc-3.3: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Philipp Kern]

Hi,

On 20.07.20 21:35, Niels Thykier wrote:
> Source: gcc-3.3
> Version: 1:3.3.6ds1-31
> Severity: normal
> Usertags: compat-5-6-removal
> 
> The package gcc-3.3 uses debhelper with a compat level of 5 or 6,
> which is deprecated and scheduled for removal[1].

Are you sure that 1:3.3.6ds1-31 is broken? That's the version I uploaded
with the fix.

Kind regards
Philipp Kern

Bug#965398: caml-crush: FTBFS: DWARF version 0 unhandled

[Adrian Bunk]

Control: reassign -1 binutils 2.34.90.20200706-1
Control: reassign 965372 binutils 2.34.90.20200706-1
Control: forcemerge -1 965372
Control: retitle -1 FTBFS: DWARF version 0 unhandled
Control: affects -1 dwz src:caml-crush src:ocaml-mccs src:ocamlnet src:extlib

On Mon, Jul 20, 2020 at 08:57:07PM +0200, Sebastian Ramacher wrote:
> Source: caml-crush
> Version: 1.0.9-1
> Severity: serious
> Tags: ftbfs sid bullseye
> Justification: fails to build from source (but built successfully in the past)
> 
> binNMUs of caml-crush failed with:
> | dh_dwz -a -O--no-parallel
> |   dwz -- debian/caml-crush-server/usr/bin/pkcs11proxyd
> | dwz: debian/caml-crush-server/usr/bin/pkcs11proxyd: DWARF version 0 
> unhandled
> | dh_dwz: error: dwz -- debian/caml-crush-server/usr/bin/pkcs11proxyd 
> returned exit code 1
> 
> See
> https://buildd.debian.org/status/fetch.php?pkg=caml-crush=amd64=1.0.9-1%2Bb1=1595270582=0

See #965115 #965300 #965372

I don't think the current approach of reporting one bug per ocaml 
package and then manually disabling dwz in every single package
is a good way forward.

What changed was binutils (#965115), and the fix will likely have to be 
either in binutils or in dwz.

> Cheers

cu
Adrian

Bug#965235: libreoffice: “Personal Edition”, WTF‽

[Thorsten Glaser]

Rene Engelhard dixit:

[…]
>seamless continuity from the 6.4 version to the 7.0."

Thanks for the update! Feel free to close this any time you want.

bye,
//mirabilos
-- 
I want one of these. They cost 720 € though… good they don’t have the HD hole,
which indicates 3½″ floppies with double capacity… still. A tad too much, atm.
‣ http://www.floppytable.com/floppytable-images-1.html

Bug#964738: gnome-shell-extensions : On screen keyboard has missing icons for Enter, Shift, Caps-lock, alt keys

[smcv]

Control: reopen -1
Control: reassign -1 gnome-shell
Control: found -1 3.36.3-1

> Package: gnome-shell-extensions

Sorry, I didn't notice that this wasn't already a gnome-shell
bug. Reopening so that I can close it for the right package.

smcv

Bug#891047: (no subject)

[Yuri Konotopov]

This is still issue in latest stable uscan.

Reproducible e.g. using [1] current master

Dropping "same" keyword is workaround for this issue.


[1] https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice


--
Best regards, Yuri Konotopov

Bug#965080: Resignation + Call for votes for new Chair

[smcv]

On Wed, 15 Jul 2020 at 21:05:23 +0200, Margarita Manterola wrote:
> ===BEGIN===
> 
> The chair of the Debian Technical Committee will be:
> 
>  A : Philip Hands
>  B : Margarita Manterola
>  C : David Bremner
>  D : Niko Tyni
>  E : Gunnar Wolf
>  F : Simon McVittie
>  G : Sean Whitton
>  H : Elana Hashman 
> 
> ===END===

I vote A = B = C = D = E > F > G = H.

smcv


signature.asc
Description: PGP signature

Bug#792580: INF0

[Abdurohman Mengesha Yessuf]

DO YOU RECEIVED MY LAST MAIL ?

Bug#962259: Creating Webhooks fails and returns error 500

[Pirate Praveen]

On Tue, Jul 21, 2020 at 00:42, Pirate Praveen 
 wrote:
This appear to be a bug in ruby-attr-encrypted gem with rails 6 as 
seen in 
https://people.debian.org/~praveen/rails6-meta-build/buildlogs/ruby-attr-encrypted.log, 
but unfortunately that gem seems unmaintained now 
https://github.com/attr-encrypted/attr_encrypted/issues/379



See https://gitlab.com/gitlab-org/gitlab/-/issues/26243 also

Bug#965399: Updating the telepathy-rakia Uploaders list

[Pierre-Elliott Bécue]

Source: telepathy-rakia
Version: 0.8.0-3
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Dafydd Harries  has not been working on
the telepathy-rakia package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965080: Resignation + Call for votes for new Chair

[Philip Hands]

Margarita Manterola  writes:
...
> ===BEGIN===
>
> The chair of the Debian Technical Committee will be:
>
>  A : Philip Hands
>  B : Margarita Manterola
>  C : David Bremner
>  D : Niko Tyni
>  E : Gunnar Wolf
>  F : Simon McVittie
>  G : Sean Whitton
>  H : Elana Hashman
>
> ===END===

I vote: B > C > A = D = E = F > G = H

Cheers, Phil.
--
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#700970: lintian: check for incorrectly formatted lists in DEP-5 copyright files

[Felix Lechner]

Hi Jakub,

I am not sure what Policy §5.6.13 said in 2013, but from my
perspective such formatting is not an error (unless the entire text is
indented by more than a single space).

For the examples you attached, especially, it is actually desirable
that the bullet points are rendered verbatim as described in policy:

> Those starting with two or more spaces. These will be displayed
> verbatim.

I would like to close this bug. Please object if you disagree. Thanks!

Kind regards
Felix Lechner

Bug#962259: Creating Webhooks fails and returns error 500

[Pirate Praveen]

On Fri, 5 Jun 2020 10:33:42 +0200 =?UTF-8?Q?Patrick_Matth=c3=a4i?= 
 wrote:

> Subject: gitlab: Creating Webhooks fails and returns error 500
> Package: gitlab
> Version: 13.0.4-1+fto10+1
> Severity: normal
>
> On creating a webhook at a project we just get a 500 error since a
> longer time. This is logged:
>
> ==> /var/log/gitlab/production.log <==
> Started POST "/customer/X/hooks" for  at 2020-06-05
> 10:27:31 +0200
> Processing by Projects::HooksController#create as HTML
> Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]",
> "hook"=>"[FILTERED]", "namespace_id"=>"customer", 
"project_id"=>"XX"}

> Completed 500 Internal Server Error in 137ms (ActiveRecord: 3.8ms |
> Elasticsearch: 0.0ms | Allocations: 12840)
>
> ==> /var/log/gitlab/production_json.log <==
> 
{"method":"POST","path":"/customer/XX/hooks","format":"html","controller":"Projects::HooksController","action":"create","status":500,"time":"2020-06-05T08:27:31.242Z","params":[{"key":"utf8","value":"✓"},{"key":"authenticity_token","value":"[FILTERED]"},{"key":"hook","value":"[FILTERED]"},{"key":"namespace_id","value":"customer"},{"key":"project_id","value":"XXX"}],"remote_ip":"","user_id":10,"username":"ZZZ","ua":"Mozilla/5.0

> (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101
> 
Firefox/77.0","queue_duration_s":null,"correlation_id":"mal85NkY5w1","meta.user":"AAA","meta.project":"customer/","meta.root_namespace":"customer","meta.caller_id":"Projects::HooksController#create","redis_calls":1,"redis_duration_s":0.000427,"cpu_s":0.18,"exception.class":"NoMethodError","exception.message":"undefined

> method `set_attribute_was' for
> 
#","exception.backtrace":["app/controllers/projects/hooks_controller.rb:20:in

> `create'","app/controllers/application_controller.rb:496:in
> `set_current_admin'","lib/gitlab/session.rb:11:in
> `with_session'","app/controllers/application_controller.rb:487:in
> 
`set_session_storage'","app/controllers/application_controller.rb:481:in

> `set_locale'","lib/gitlab/error_tracking.rb:48:in
> `with_context'","app/controllers/application_controller.rb:546:in
> `sentry_context'","app/controllers/application_controller.rb:474:in
> `block in 
set_current_context'","lib/gitlab/application_context.rb:52:in

> `block in use'","lib/gitlab/application_context.rb:52:in
> `use'","lib/gitlab/application_context.rb:20:in
> `with_context'","app/controllers/application_controller.rb:467:in
> 
`set_current_context'"],"db_duration_s":0.0038,"view_duration_s":0.0,"duration_s":0.1377}

>
> ==> /var/log/gitlab/production.log <==
>
> NoMethodError (undefined method `set_attribute_was' for
> #):

This appear to be a bug in ruby-attr-encrypted gem with rails 6 as seen 
in 
https://people.debian.org/~praveen/rails6-meta-build/buildlogs/ruby-attr-encrypted.log, 
but unfortunately that gem seems unmaintained now 
https://github.com/attr-encrypted/attr_encrypted/issues/379

Bug#965398: caml-crush: FTBFS: DWARF version 0 unhandled

[Sebastian Ramacher]

Source: caml-crush
Version: 1.0.9-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

binNMUs of caml-crush failed with:
| dh_dwz -a -O--no-parallel
|   dwz -- debian/caml-crush-server/usr/bin/pkcs11proxyd
| dwz: debian/caml-crush-server/usr/bin/pkcs11proxyd: DWARF version 0 unhandled
| dh_dwz: error: dwz -- debian/caml-crush-server/usr/bin/pkcs11proxyd returned 
exit code 1

See
https://buildd.debian.org/status/fetch.php?pkg=caml-crush=amd64=1.0.9-1%2Bb1=1595270582=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#965397: RFS: ripit/4.0.0~rc20161009-1 -- Textbased audio CD ripper

[Elimar Riesebieter]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: ripit
   Version : 4.0.0~rc20161009-1
   Upstream Author : Felix Suwald 
 * URL : http://www.suwald.pl/ripit/news.php
 * License : GPL-2
 * Vcs : https://salsa.debian.org/riesebie/ripit
   Section : sound

It builds those binary packages:

  ripit - Textbased audio CD ripper

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/r/ripit/ripit_4.0.0~rc20161009-1.dsc

Changes since the last upload:

 ripit (4.0.0~rc20161009-1) unstable; urgency=medium
 .
   * New upstream release candidate
   * New upstream homepage http://www.ripit.pl/ripit/news.php.
 (Closes: #965369)
   * Use gnudb instead of freedb in config. (Closes: #965232)
   * Bump debhelper compatibility level to 13.
 + Replace debian/compat with a versioned b-d on debhelper-compat.
   * Declare compliance with Debian Policy 4.5.0. (No changes needed.)
   * Refresh patches as needed
   * Remove trailing whitespace from changelog
   * Added VCS-(Browser|Git) and Rules-Requires-Root=no to debian/control
   * Replaced exim4 with default-mta in Recommends:
   * Introduced 0001-Fixed-more-typos-in-ripit.1.patch
   * Added gbp.conf

Regards,
Elimar
-- 
  355/113: Not the famous irrational number pi,
   but an incredible simulation!
-unknown

Bug#965394: Updating the telepathy-glib Uploaders list

[Pierre-Elliott Bécue]

Source: telepathy-glib
Version: 0.24.1-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Dafydd Harries  has not been working on
the telepathy-glib package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965392: Updating the rrootage Uploaders list

[Pierre-Elliott Bécue]

Source: rrootage
Version: 0.23a-12
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Dafydd Harries  has not been working on
the rrootage package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965151: /usr/bin/tx: transifex-client and afdko shipping binaries under the same name

[Adrian Bunk]

On Mon, Jul 20, 2020 at 09:35:35AM +0800, Yao Wei wrote:
>...
> I am currently considering doing it by moving all binaries of afdko from
> /usr/bin to /usr/bin/afdko, and then creating another package
> afdko-legacy, that, similar to node-legacy before node changed the name
> to ax25-node, symlinks all binaries from /usr/bin/afdko back to
> /usr/bin.

This was a one-time decision, it is not a general procedure.

> This will decrease the mess of one package having multiple
> binaries, and ensure the compatibility of font building scripts that
> invokes afdko tx.  Does it require CTTE agreement since afdko-legacy is
> also in conflict with tx?
>...

Yes.

Cases like node or git or chromium where a very popular new program 
(unintentionally) steals the name of a fringe program are rare.

This looks like the common case where two fringe packages both use
a far too generic name for a program, and the older package might
have users using it with this name in stable releases.

> Thanks,
> Yao Wei

cu
Adrian

Bug#965393: Updating the telepathy-gabble Uploaders list

[Pierre-Elliott Bécue]

Source: telepathy-gabble
Version: 0.18.4-1 0.18.4-3
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Dafydd Harries  has not been working on
the telepathy-gabble package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965389: Updating the empathy Uploaders list

[Pierre-Elliott Bécue]

Source: empathy
Version: 3.25.90+really3.12.14-1 3.25.90+really3.12.14-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Dafydd Harries  has not been working on
the empathy package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965391: Updating the python-gssapi Uploaders list

[Pierre-Elliott Bécue]

Source: python-gssapi
Version: 1.4.1-1 1.6.1-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Dafydd Harries  has not been working on
the python-gssapi package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965395: Updating the telepathy-idle Uploaders list

[Pierre-Elliott Bécue]

Source: telepathy-idle
Version: 0.2.0-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Dafydd Harries  has not been working on
the telepathy-idle package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965390: Updating the gssproxy Uploaders list

[Pierre-Elliott Bécue]

Source: gssproxy
Version: 0.8.0-1.1 0.8.2-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Dafydd Harries  has not been working on
the gssproxy package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965396: Updating the telepathy-logger Uploaders list

[Pierre-Elliott Bécue]

Source: telepathy-logger
Version: 0.8.2-3 0.8.2-4
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Dafydd Harries  has not been working on
the telepathy-logger package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965387: O: kanjipad -- handwriting recognition tool for Kanji

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of kanjipad, Dafydd Harries ,
is apparently not active anymore.  Therefore, I orphan this package now.

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

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

Some information about this package:

Package: kanjipad
Binary: kanjipad
Version: 2.0.0-8
Maintainer: Dafydd Harries 
Build-Depends: libgtk2.0-dev, debhelper (>> 9), quilt
Architecture: any
Standards-Version: 3.9.3
Format: 3.0 (quilt)
Files:
 a270b1d6b013d377c04ea0400f0c8fbb 1177 kanjipad_2.0.0-8.dsc
 bdfe75534322840b3ff566e0a91c472d 75930 kanjipad_2.0.0.orig.tar.gz
 dfa878a21385c2fe19875a128aca1048 3556 kanjipad_2.0.0-8.debian.tar.gz
Vcs-Browser: 
http://anonscm.debian.org/gitweb/?p=collab-maint/kanjipad.git;a=summary
Vcs-Git: git://anonscm.debian.org/collab-maint/kanjipad.git
Checksums-Sha256:
 8b2d07bfb186b964dd5b7a22eb415edc81e787fcf26b8dcbefe0f5f1af89e09a 1177 
kanjipad_2.0.0-8.dsc
 28272f61ec09c607a3578e3626e9e4fd43d1d9d1e21cb64328745766d00ee9e1 75930 
kanjipad_2.0.0.orig.tar.gz
 1713c6f72df93626f2586778aaac89c6fbca230e2884f2f9a59d9c5592b990d6 3556 
kanjipad_2.0.0-8.debian.tar.gz
Package-List: 
 kanjipad deb x11 extra
Directory: pool/main/k/kanjipad
Priority: source
Section: x11

Package: kanjipad
Source: kanjipad (2.0.0-8)
Version: 2.0.0-8+b1
Installed-Size: 93
Maintainer: Dafydd Harries 
Architecture: amd64
Depends: libc6 (>= 2.7), libglib2.0-0 (>= 2.16.0), libgtk2.0-0 (>= 2.8.0), 
libpango-1.0-0 (>= 1.14.0)
Recommends: fonts-ipafont-gothic | fonts-japanese-gothic
Description-en: handwriting recognition tool for Kanji
 Kanjipad translates drawings by the user into Kanji characters. Translated
 characters can be copied and pasted into other applications.
Description-md5: 1176760a183a8dc10e9d67a1578d027c
Tag: culture::japanese, implemented-in::c, interface::graphical,
 interface::x11, role::program, uitoolkit::gtk
Section: x11
Priority: optional
Filename: pool/main/k/kanjipad/kanjipad_2.0.0-8+b1_amd64.deb
Size: 33184
MD5sum: 2ae8d7e5115fa67d02723e95bf0071ca
SHA256: 1c67960dcc4d90a820a6f178bb96d12b2c33f16ce8d0e63b08537528c31553fe


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#965388: O: typespeed -- Zap words flying across the screen by typing them correctly

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of typespeed, Dafydd Harries ,
is apparently not active anymore.  Therefore, I orphan this package now.

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

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

Some information about this package:

Package: typespeed
Binary: typespeed
Version: 0.6.5-2.1
Maintainer: Dafydd Harries 
Build-Depends: debhelper (>= 5), quilt (>= 0.46-7), libncurses5-dev, 
autotools-dev
Architecture: any
Standards-Version: 3.8.4
Format: 1.0
Files:
 38251d0f98269b4ab4369ae2e07659b2 1858 typespeed_0.6.5-2.1.dsc
 578102b418c7df84903d3e90df2e7483 254170 typespeed_0.6.5.orig.tar.gz
 a3845ca52cfb105526c72221171035e4 8112 typespeed_0.6.5-2.1.diff.gz
Vcs-Browser: http://git.debian.org/?p=collab-maint/typespeed.git
Vcs-Git: git://git.debian.org/git/collab-maint/typespeed
Checksums-Sha256:
 6525c2f90bd2eb5872dc4197ebda82c7307698369e43fa9a53aec1322f45f7b1 1858 
typespeed_0.6.5-2.1.dsc
 5c860385ceed8a60f13217cc0192c4c2b4705c3e80f9866f7d72ff306eb72961 254170 
typespeed_0.6.5.orig.tar.gz
 31a2e03b39b1a17c3b1716cab9d4750966088c2ae75621be1d833371ca1ba1a9 8112 
typespeed_0.6.5-2.1.diff.gz
Homepage: http://tobias.eyedacor.org/typespeed/
Package-List: 
 typespeed deb games optional arch=any
Directory: pool/main/t/typespeed
Priority: source
Section: games

Package: typespeed
Source: typespeed (0.6.5-2.1)
Version: 0.6.5-2.1+b3
Installed-Size: 198
Maintainer: Dafydd Harries 
Architecture: amd64
Depends: fileutils (>= 4.0-5) | coreutils (>> 5), libc6 (>= 2.14), libncurses6 
(>= 6), libtinfo6 (>= 6)
Conflicts: suidmanager (<< 0.50)
Description-en: Zap words flying across the screen by typing them correctly
 Typespeed is a game in which words fly across your screen. Your task is to
 zap the words by typing them before they cross the screen. If too many words
 get by you, the game is over.
Description-md5: e96cff21f40c078569c1ce9622c18e62
Homepage: http://tobias.eyedacor.org/typespeed/
Tag: game::typing, interface::text-mode, role::program, uitoolkit::ncurses,
 use::gameplaying, use::learning
Section: games
Priority: optional
Filename: pool/main/t/typespeed/typespeed_0.6.5-2.1+b3_amd64.deb
Size: 68580
MD5sum: e4bd56702d17d78fc95aab6724609033
SHA256: 40635625875e9fa2b3bc164cb16881080bfb443d0cd4f2c9aea62182a76bfae5


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#943552: ITP: tracecompass -- trace viewer and analyzer

[Sudip Mukherjee]

Update:
It will also need few packages which are not built currently.
equinox-p2->
  * libequinox-p2-ui-java.
  * libequinox-p2-ui-sdk-java.
  * libequinox-p2-ui-sdk-scheduler-java

eclipse-platform-ui->
  * libeclipse-ui-navigator-resources-java.
  * libeclipse-ui-themes-java.

This has been discussed at
https://lists.debian.org/debian-java/2020/07/msg4.html

-- 
Regards
Sudip

Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64

[Hans van Kranenburg]

Hi,

On Wed, 15 Jul 2020 20:52:40 -0700 Sarah Newman  wrote:
> On 7/7/20 8:13 PM, Ben Hutchings wrote:
> > Control: reassign -1 src:linux
> > Control: tag -1 moreinfo
> > 
> > On Tue, 2020-07-07 at 17:30 -0700, Sarah Newman wrote:
> >> Package: linux-signed-amd64
> >> Version: 4.19.0-9-amd64
> >>
> >> We've had two separate reports now of debian buster users running
> >> 4.19.0-9-amd64 who experienced serious file system corruption.
> > 
> > Which version?  (I.e. what does "uname -v" or
> > "dpkg -s linux-image-4.19.0-9-amd64" say?)
> > 
> >> - Both were using ext3
> >> - Both are running Xen HVM, but I do not have reason to believe this to be 
> >> related
> 
> [...]

I have servers which run 4.19.118-2 as dom0 kernel and a Xen 4.11.4-1
rebuild for Buster.

One example is a smallish 6-server cluster that got a reboot cycle 48
days ago.

It contains a few heavily loaded domUs with 4.19.118 or 4.19.131 based
kernels.

No problems or disk corruption or anything is seen yet. dom0 filesystem
is ext4, domUs use a mix of ext4 and btrfs (over iscsi). So, no ext3
anywhere.

We haven't got bug reports against Debian Xen packages in the BTS about
this.

I have not yet tried to make an ext3 fs on a block device in a test domU
and then have it do things with the fs and reboot it now and then. If
wanted, I can do that and see if there's any problem after a week or
two. Just to add chaos to help correlating.

FWIW,
Hans

Bug#965143: sssd: SSSD 2.3 won't let log in or use sudo

[Sam Morris]

Source: sssd
Followup-For: Bug #965143
Control: -1 + fixed-upstream patch

Upstream things this is https://github.com/SSSD/sssd/pull/5222 which
has been fixed upstream.

https://patch-diff.githubusercontent.com/raw/SSSD/sssd/pull/5222.patch

-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (535, 'stable-updates'), (535, 'stable'), (520, 'testing'), (510, 
'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-8-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#965264: fcitx: cannot switch to Chinese pinyin input by pressing Ctrl+space

[Junyue]

在 2020/7/19 上午2:23, Aron Xu 写道:

Hi,

Would you mind to attach the output of `fcitx-diagnose` command?

Best,
Aron


Dear Aron,

Below is the output. Thanks!

# 系统信息:
1.  `uname -a`:

Linux debian 5.4.38-1.fc28.lemote.mips64el #1 SMP PREEMPT Mon 
May 4 23:36:26 CST 2020 mips64 GNU/Linux


2.  `lsb_release -a`:

No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux bullseye/sid
Release:testing
Codename:   bullseye

3.  `lsb_release -d`:

Description:Debian GNU/Linux bullseye/sid

4.  `/etc/lsb-release`:

`/etc/lsb-release` 未找到.

5.  `/etc/os-release`:

PRETTY_NAME="Debian GNU/Linux bullseye/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

6.  桌面环境:

桌面环境为 `xfce`。

7.  Bash 版本:

BASH_VERSION='5.0.16(1)-release'

# 环境:
1.  DISPLAY:

DISPLAY=':0.0'

2.  键盘布局:

1.  `setxkbmap`:

xkb_keymap {
xkb_keycodes  { include "evdev+aliases(qwerty)"   };
xkb_types { include "complete"};
xkb_compat{ include "complete"};
xkb_symbols   { include "pc+us+inet(evdev)"   };
xkb_geometry  { include "pc(pc105)"   };
};

2.  `xprop`:

_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""

3.  Locale:

1.  全部可用 locale:

C
C.UTF-8
POSIX
zh_CN.utf8

2.  当前 locale:

LANG=zh_CN.UTF-8
LANGUAGE=zh_CN:zh
LC_CTYPE="zh_CN.UTF-8"
LC_NUMERIC="zh_CN.UTF-8"
LC_TIME="zh_CN.UTF-8"
LC_COLLATE="zh_CN.UTF-8"
LC_MONETARY="zh_CN.UTF-8"
LC_MESSAGES="zh_CN.UTF-8"
LC_PAPER="zh_CN.UTF-8"
LC_NAME="zh_CN.UTF-8"
LC_ADDRESS="zh_CN.UTF-8"
LC_TELEPHONE="zh_CN.UTF-8"
LC_MEASUREMENT="zh_CN.UTF-8"
LC_IDENTIFICATION="zh_CN.UTF-8"
LC_ALL=

4.  目录：

1.  主目录：

/home/junyue

2.  `${XDG_CONFIG_HOME}`:

环境变量 `XDG_CONFIG_HOME` 没有设定。

`XDG_CONFIG_HOME` 的当前值是 `~/.config` (`/home/junyue/.config`)。

3.  Fcitx 设置目录：

当前 fcitx 设置目录是 `~/.config/fcitx` 
(`/home/junyue/.config/fcitx`)。


5.  当前用户：

脚本作为 junyue (1000) 运行。

# Fcitx 状态:
1.  可执行文件:

在 `/usr/bin/fcitx` 找到了 fcitx.

2.  版本:

Fcitx 版本: `4.2.9.7`

3.  进程:

找到了 2 个 fcitx 进程:

22052 fcitx
22069 fcitx-dbus-watc

4.  `fcitx-remote`:

`fcitx-remote` 工作正常.

5.  DBus 界面:

使用 `dbus-send` 来检查 dbus。

DBus 名称 `org.fcitx.Fcitx` 的所有者是 `:1.67`。

DBus 名称 `org.fcitx.Fcitx` 的 PID 所有者是 `22052`。

# Fcitx 配置界面:
1.  配置工具封装：

在 `/usr/bin/fcitx-configtool` 找到了 fcitx-configtool。

2.  用于 GTK+-2.0 的配置界面：

**未找到 gtk2 的配置界面.**

3.  用于 GTK+-3.0 的配置界面：

在 `/usr/bin/fcitx-config-gtk3` 找到了 `fcitx-config-gtk3`。

4.  KDE 的配置界面：

**`kcmshell4` 未找到.**

# 前端设置:
## Xim:
1.  `${XMODIFIERS}`:

环境变量 XMODIFIERS 已经正确地设为了 "@im=fcitx".
从环境变量中获取的 Xim 服务名称为 fcitx.

2.  根窗口上的 XIM_SERVERS:

Xim 服务的名称与环境变量中设置的相同.

## Qt:
1.  qt4 - `${QT4_IM_MODULE}`:

环境变量 QT4_IM_MODULE 已经正确地设为了 "fcitx".

2.  qt5 - `${QT_IM_MODULE}`:

环境变量 QT_IM_MODULE 已经正确地设为了 "fcitx".

3.  Qt 输入法模块文件:

找到了 Qt4 的输入法模块: 
`/usr/lib/mips64el-linux-gnuabi64/qt4/plugins/inputmethods/qtim-fcitx.so`.
找到了 Qt5 的输入法模块: 
`/usr/lib/mips64el-linux-gnuabi64/qt5/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so`.
找到了 fcitx 的 qt 模块: 
`/usr/lib/mips64el-linux-gnuabi64/fcitx/qt/libfcitx-quickphrase-editor5.so`.


## Gtk:
1.  gtk - `${GTK_IM_MODULE}`:

环境变量 GTK_IM_MODULE 已经正确地设为了 "fcitx".

2.  `gtk-query-immodules`:

1.  gtk 2:

**无法找到 gtk 2 的 `gtk-query-immodules`.**

**无法找到 gtk 2 的 fcitx 输入法模块.**

2.  gtk 3:

**无法找到 gtk 3 的 `gtk-query-immodules`.**

**无法找到 gtk 3 的 fcitx 输入法模块.**

3.  Gtk 输入法模块缓存:

1.  gtk 2:

**无法找到 gtk 2 的输入法模块缓存**

**无法在缓存中找到 gtk 2 的 fcitx 输入法模块.**

2.  gtk 3:

**无法找到 gtk 3 的输入法模块缓存**

**无法在缓存中找到 gtk 3 的 fcitx 输入法模块.**

4.  Gtk 输入法模块文件:

1.  gtk 2:

找到的全部 Gtk 2 输入法模块文件均存在.

2.  gtk 3:

找到的全部 Gtk 3 输入法模块文件均存在.

# 配置:
## Fcitx 插件:
1.  插件配置文件目录:

找到了 fcitx 插件配置目录: `/usr/share/fcitx/addon`.

2.  插件列表:

1.  找到了 29 个已启用的插件:

fcitx-autoeng
fcitx-chttrans
fcitx-classic-ui
fcitx-clipboard
fcitx-dbus
fcitx-freedesktop-notify
fcitx-fullwidth-char
fcitx-googlepinyin
fcitx-imselector
fcitx-ipc
fcitx-ipcportal
fcitx-keyboard
fcitx-kimpanel-ui
fcitx-lua
fcitx-notificationitem
fcitx-pinyin
   

Bug#965386: plasma-browser-integration: Please package Firefox extension

[Michael Weghorn]

Package: plasma-browser-integration
Version: 5.17.5-1
Severity: wishlist
X-Debbugs-Cc: m.wegh...@posteo.de

Dear Maintainer,

currently, the WebExtension for plasma-browser-integration is not packaged in
Debian.
For the Firefox case, it is therefore necessary to install the extension
manually from AMO: https://addons.mozilla.org/en-US/firefox/addon/plasma-
integration/

It would be great if it could be provided via Debian package (possibly a
separate binary package than the one that already exists).

Note: The file 'dev_README.txt' in the sources describes how to build the
extension, but this probably cannot be followed as is, since it involves
installing packages via "npm" in the first step (which is not in line with
Debian's packaging practices).

Best regards,
Michael



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

Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-browser-integration depends on:
ii  kio   5.70.1-1
ii  libc6 2.31-1
ii  libkf5activities5 5.70.0-1
ii  libkf5configcore5 5.70.0-1
ii  libkf5coreaddons5 5.70.0-1
ii  libkf5crash5  5.70.0-1
ii  libkf5dbusaddons5 5.70.0-1
ii  libkf5filemetadata3   5.70.0-1
ii  libkf5i18n5   5.70.0-1
ii  libkf5kiocore55.70.1-1
ii  libkf5kiowidgets5 5.70.1-1
ii  libkf5notifications5  5.70.0-1
ii  libkf5purpose-bin 5.70.0-1
ii  libkf5purpose55.70.0-1
ii  libkf5runner5 5.70.0-1
ii  libkf5service-bin 5.70.0-1
ii  libkf5service55.70.0-1
ii  libqt5core5a  5.14.2+dfsg-4
ii  libqt5dbus5   5.14.2+dfsg-4
ii  libqt5gui55.14.2+dfsg-4
ii  libqt5widgets55.14.2+dfsg-4
ii  libstdc++610.1.0-6

plasma-browser-integration recommends no packages.

plasma-browser-integration suggests no packages.

-- no debconf information

Bug#965151: /usr/bin/tx: transifex-client and afdko shipping binaries under the same name

[Adrian Bunk]

On Mon, Jul 20, 2020 at 03:05:26AM +, Paul Wise wrote:
> On Mon, Jul 20, 2020 at 1:40 AM Yao Wei wrote:
> 
> > There's a serious bug when I am uploading afdko package, that one of the
> > binaries in this package "tx" has name conflicting with
> > transifex-client.
> 
> As transifex-client is client for the proprietary Transifex service,
> personally I would just add a conflict.

Policy says this is not an option, and I agree with policy.

If we start allowing conflicts between completely unrelated packages
it might not end well in the long run.

Imagine the GNU Interactive Tools would still provide /usr/bin/git
with such a Conflicts.

> Also talk to upstream about choosing a more appropriate name for the
> tx program, that is way too short even if it weren't conflicting with
> another package.
>...

I would agree with that, my first thought was whether there is also
an rx program...

> bye,
> pabs

cu
Adrian

Bug#965374: mudlet: Packaging new version

[Matthias Urlichs]

Package: mudlet
Version: 1:3.7.1-1.1
Severity: normal

I intend to package the current mudlet Upstream release (4.9.1).

The current version is way too old, lots of scripts no longer work with it.

-- 
-- Matthias Urlichs




signature.asc
Description: OpenPGP digital signature

Bug#965385: lintian: debian-watch-file-missing-version issued for comment-only watch file

[gregor herrmann]

Package: lintian
Version: 2.84.0
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Lintian just told me about a missing version= in a debian/watch file
(aka the debian-watch-file-missing-version tag) but the watch file
consists _only_ of 2 comment lines (in order to explain why there is
no watch URL).

I think, in this case the tag doesn't make a lot of sense, nor any of
the other checks.

Looking at checks/debian/watch.pm, I guess before the
look-for-version part (l. 109) the function should return if @lines
is empty (or $contents before).


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl8V3jFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYYxxAAoaZnA2uYC9jxJcjzL7FasILl4Y94u/fDcRSf0vZtbwQRWTzHOgEx6Bgu
YZYWxNdS+R3UQB72RFVaiZCDPei0lbLHWZXPS+oh7E3D43uM6MEMagmNWQ0BGTvq
ajrsB5PMMK7I0uw6SHM1ratPSHCqtPze9bem+drccNHcJTOQJNOt8NmZy5rmYiue
Nszypt9DAePuvLay+ZRsmlkAl61f1/mz1LBGqIpmVXl1l2V2xIL7KBMcx8gWfwSb
1sIQXW6G1gdLJQfONoCG/nBX4Zs9NraZUwb++qZDJUvdirpzJqk+WlvMgQuYVfia
M2J8WmoECHdPpxZgohvsGRibVKSfcHS6+MsOuIwebntp0LtGYLBK6VFIAQL1Hq4P
AQwLV4/ZH8w63dOUKTW7Z8XQ945r/QrRzqU+ukstQGbactey/rY6aPzA4h9cqGbR
Lk9zvCz5c+NSTnWxyQPGrvMKT/jONvZ+nyAqRyFTaEXihZkLQkUW+DR4irS38lTm
QCybzUVbz04j1VFEniqLGTI/1C4uDP7Jmd9BDsMNt+gy5Yurc2VMNJ2aLCKcvRMO
HEfrPnjQlXshOBcJa4W9DoO90ibdJeZmX8qs6xvwcsl5yyGT2/yeU0ZOphTQmjzK
RIHPuuOkxHwERyd9SIxD7KWeL1oUcojueggkTTIDqmcNcIzdEcM=
=4VP4
-END PGP SIGNATURE-

Bug#954272: slurmd: SLURM not working with OpenMPI

[Lars Veldscholte]

Hi,

I believe I have found a solution.

I must confess that I still don't fully understand the difference 
between the various PMI APIs, and which ones are supported by OpenMPI, 
but I found that the recommended way is to use PMIx.


However, PMIx was not working on my system even though libpmix2 is 
installed:


# srun --mpi pmix ./a.out

srun: error: (null) [0] /mpi_pmix.c:133 [init] mpi/pmix: ERROR: 
pmi/pmix: can not load PMIx library


srun: error: Couldn't load specified plugin name for mpi/pmix: Plugin 
init() callback failed


srun: error: cannot create mpi context for mpi/pmix

srun: error: invalid MPI type 'pmix', --mpi=list for acceptable types

Running `strace srun --mpi=pmix ./a.out` revealed that SLURM is looking 
for the pmix library at `/usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so`, 
which does not exist, only `libpmix.so.2` exists.


Installing the package `libpmix-dev` installs this library (it symlinks 
it to the same file `libpmix.so.2` is symlinked to).


Now, `srun --mpi=pmix ./a.out` is working!

I'm not 100% sure, but I think that the package `libpmix2` should also 
install the file `libpmix.so`. The dev package shouldn't be required for 
that, right?


Lars



signature.asc
Description: OpenPGP digital signature

Bug#965235: libreoffice: “Personal Edition”, WTF‽

[Rene Engelhard]

Hi,

https://blog.documentfoundation.org/blog/2020/07/20/update-on-marketing-and-communication-plans-for-the-libreoffice-7-x-series/

"As such, the 7.0 release of LibreOffice will not see any of the
tagline/flavor text proposed inside the release candidate (RC) versions,
the Marketing/Communication Plan for 2020-2025 or any of the
alternatives proposed during the discussion, specifically inside the
splash-screen, the start center and the about box; to explain it with
other words, the modifications put in the RC versions with the regards
of branding will be reverted to a previous state, so there will be
seamless continuity from the 6.4 version to the 7.0."

They still might reinstate that for 7.1+, though, but 7.0.0 is the
version for bullseye anyways.[1]

Regards,

Rene

[1] 7.1.0 comes too late (compare
https://wiki.documentfoundation.org/ReleasePlan/6.4 which +1 year
resembles 7.1 with
https://release.debian.org/bullseye/freeze_policy.html#transition)

Bug#965371: resolve: enable RES_TRUSTAD towards the 127.0.0.53 stub resolver

[Johan Fleury]

Package: systemd
Version: 245.6-3
Severity: wishlist
Tags: patch
X-Debbugs-Cc: jfle...@arcaik.net

Since glibc 2.31, the resolvers in /etc/resolve.conf are not trusted
anymore and the AD flag is stripped from their responses.

As systemd-resolved is listening on a loopback interface, the `trust-ad`
option was added to its stub resolve.conf file by upstream commit
a742f98[^1].

It would be great if this commit could be backported to systemd 245 in Sid,
waiting for version 246 to be released by upstream.

[^1]: 
https://github.com/systemd/systemd/commit/a742f9828ea73d9c2c9bafe701c10fe60f058012

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-8
ii  libapparmor1 2.13.4-3
ii  libaudit11:2.8.5-3+b1
ii  libblkid12.35.2-7
ii  libc62.31-1
ii  libcap2  1:2.36-1
ii  libcrypt11:4.4.16-1
ii  libcryptsetup12  2:2.3.3-1
ii  libgcrypt20  1.8.6-2
ii  libgnutls30  3.6.14-2+b1
ii  libgpg-error01.38-2
ii  libidn2-02.3.0-1
ii  libip4tc21.8.5-2
ii  libkmod2 27+20200310-2
ii  liblz4-1 1.9.2-2
ii  liblzma5 5.2.4-1+b1
ii  libmount12.35.2-7
ii  libpam0g 1.3.1-5
ii  libpcre2-8-0 10.34-7
ii  libseccomp2  2.4.3-1+b1
ii  libselinux1  3.1-2
ii  libsystemd0  245.6-3
ii  mount2.35.2-7
ii  systemd-timesyncd [time-daemon]  245.6-3
ii  util-linux   2.35.2-7

Versions of packages systemd recommends:
ii  dbus  1.12.20-1

Versions of packages systemd suggests:
ii  policykit-10.105-28
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.137
ii  libnss-systemd   245.6-3
ii  libpam-systemd   245.6-3
ii  udev 245.6-3

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

-- no debconf information

Bug#965080: Resignation + Call for votes for new Chair

[Niko Tyni]

On Wed, Jul 15, 2020 at 09:05:23PM +0200, Margarita Manterola wrote:

> ===BEGIN===
> 
> The chair of the Debian Technical Committee will be:
> 
>  A : Philip Hands
>  B : Margarita Manterola
>  C : David Bremner
>  D : Niko Tyni
>  E : Gunnar Wolf
>  F : Simon McVittie
>  G : Sean Whitton
>  H : Elana Hashman 
> 
> ===END===

I vote: B > C > A = D = E = F > G = H

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


signature.asc
Description: PGP signature

Bug#965383: ITP: golang-github-tatsushid-go-prettytable: Builds a simple text table with a multibyte, doublewidth character support

[Nilesh Patra]

Package: wnpp
Severity: wishlist
Owner: Nilesh Patra 
X-Debbugs-CC: debian-de...@lists.debian.org


* Package name: golang-github-tatsushid-go-prettytable
  Version : 0.0~git20141013.ed2d14c-1
  Upstream Author : Tatsushi Demachi
* URL : https://github.com/tatsushid/go-prettytable

* License : Expat
  Programming Lang: Golang
  Description : Builds a simple text table with a multibyte,
doublewidth character support

go-prettytable go-prettytable is a library for
 Golang to build a simple text table with a multibyte,
 doublewidth character support.

I shall maintain this package.

Bug#965381: src:qemu: upstream changelog wildly outdated

[Jonas Smedegaard]

Package: src:qemu
Version: 1:5.0-11
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

/usr/share/doc/qemu-user/changelog.gz ends at release 0.12.0.

Please either replace it with a more up-to-date upstream-curated file,
replace it with a locally generated file from git,
or (as a last resort) simply drop the file.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl8V01MACgkQLHwxRsGg
ASGoHBAAnr39Asc2qE2+HnFeZr6wU1ytN3cxOPzIAIP+dr+Xk25THJo6bzD/NC8u
QP2z1Pk7qmC30Cq13gUYyPHyH1VwvQmgBmIHEdZ96S9ZBwc7pZ5ByzX+IZoHUNi5
czCLuPi66mIjXtE0Okf6Nf0uGKALr14S6aSIzeC3/bjy8w2SoAB7Rw2k98JdMJfO
RMA+e613PgHHX9V2ikiXYLxhQ920pZ8GDWbmjY5fI9LqYvEqnYcywFwEf4mVyCps
MuaVDmNF8U3WUHxraW8OnL6RUUGxJkp/dUzEL+XRb11A0jRZTkV5HzBb8FaPtW2A
+C6DIiIIMzQ+MR2V7q5EzS95vZU37Gohi7ybWsqF7xEnsyOknnrYUM7tfL/vRz53
rA1BioXqxzppbFWvA3YVhCHMSDMYTK0a3PeBvrt/2HmJvXz7EwEkXGIp9Rdf/8lL
VxrR0ErCPN+dZIpEKsj6pD8h2Poi2U9ltgabcbY9muXIf+nwkyf8qA6RMqREyfvp
+tF/7GPnXzmL0wP+93qlf8CsJ+zAEjBXnvipbALlE/Gfts2TKR8rYDvc642o/kfH
6FKZ/DqmYikHw9B9SPCWicXr/L8ejKbuT/916uzs+URCgw0+rszoHn2MSfdt2UNC
oH4q2++iCIZhrhaPcZ43o4+HwvXJDfOzKpLqFlCRxIB65tQyDtA=
=bLB4
-END PGP SIGNATURE-

Bug#965029: console-setup: fonts missing numerous unicode->font mappings for box-drawing characters

[Anton Zinoviev]

On Mon, Jul 20, 2020 at 09:34:36AM -0400, Nick Black wrote:
> 
> I don't make use of the following, so they're not important to
> me, but it might be worthwhile to handle these:
> 
> U+2BBD BALLOT BOX WITH LIGHT X
> U+2718 HEAVY BALLOT X
> U+2717 BALLOT X

Оk.  I've attached updated versions of Arabic-Fixed16.psf, 
Arabic-VGA16.psf and Lat15-Terminus16.psf.  Hopefully, this time the 
fonts are ok.
 
> Will this work be going upstream? I'm not clear on whether
> you're the upstream maintainer, or just Debian's.

In this case Debian = upstream.

Anton Zinoviev



Arabic-VGA16.psf
Description: Binary data


Arabic-Fixed16.psf
Description: Binary data


Lat15-Terminus16.psf
Description: Binary data

Bug#965370: RFS: wand/0.6.2-1 -- Python interface for ImageMagick library (Python 3)

[Håvard Flaget Aasen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "wand"

 * Package name: wand
   Version : 0.6.2-1
   Upstream Author : E. McConville 
 * URL : https://github.com/emcconville/wand
 * License : Expat
 * Vcs : https://salsa.debian.org/debian/wand
   Section : python

It builds those binary packages:

  python3-wand - Python interface for ImageMagick library (Python 3)
  pypy-wand - Python interface for ImageMagick library (PyPy)
  wand-doc - Python interface for ImageMagick library (documentation)

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/w/wand/wand_0.6.2-1.dsc

Changes since the last upload:

   * New upstream version 0.6.2
   * Set upstream metadata fields: Bug-Submit.
   * Update salsa CI
 - Watch all variations of reprotest.
   * Use spaces rather than tabs in d/copyright
   * Rebase patches
   * flask sphinx theme is now in the upstream repository
 - Remove patch and lintian-override


This package has a lintian warning, which is still being discussed here [1]

Regards,
Håvard

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

Bug#944989: a note about python-modernize

[Thomas Grainger]

I have just released modernize==0.8rc1 to pypi that drops use of
lib2to3 in favour of fissix

Thomas Grainger

Bug#965349: regression in dh_installchangelogs or dh_missing causes fatal error when installing upstream changelog from debian/tmp

[Nicholas D Steeves]

Hi Niels,

Thank you for the quick reply!

Niels Thykier  writes:

> Thanks for filing the bug.  I suspect that the reason that falling back
> to compat 12 works is because it downgrades the issue to a warning
> (compat 12 defaulting to --list-missing vs. compat 13 defaulting to
> --fail-missing).
>

You're right :-)

> Can you confirm that finding?  Because then it is probably just the new
> default and not a regression.
>
> Obviously, that still leaves finding a solution to the problem, but for
> starters lets confirm whether or not this is a regression.
>

Confirmed, the new default exposes what may be an old bug.

dh_missing: warning: changelog exists in debian/tmp but is not installed to 
anywhere
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_elpa: elpa-counsel (2), elpa-ivy (4), elpa-ivy-hydra (1), 
elpa-swiper (1)
 * dh_installdocs: elpa-counsel (0), elpa-ivy (1), elpa-ivy-hydra (0), 
elpa-swiper (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.

I am explicitly installing it in rules with 'dh_installchangelogs
debian/tmp/changelog' and have confirmed the file exists in each of the
binary packages for both debhelper-compat 12 and 13.

Please let me know if there's anything else I can do to help.  I'm sorry
to say I never learned Perl.

Best,
Nicholas


signature.asc
Description: PGP signature

Bug#965338: libreoffice-math creates its own menu section, "Education"

[Rene Engelhard]

Hi,

Am 19.07.20 um 21:21 schrieb Adam Borowski:
> In the applications menu (on XFCE in my case), Libreoffice-Math instead of
> living with the rest of components in "Office" where one would expect it,
> creates a menu section on its own, with only one tenant, itself.
>
> Thus, please move
> Education/LibreOffice Math
> to
> Office/LibreOffice Math

It is already in Office.

$ cat /usr/share/applications/libreoffice-math.desktop

[Desktop Entry]

Version=1.0
Terminal=false
NoDisplay=false
Icon=libreoffice-math
Type=Application
Categories=Office;Spreadsheet;Education;Science;Math;

[...]

I think we should remove it from Education, indeed.


I also think we should remove it from Science.

People doing Science and Maths are supposed to use LaTeX anyways :-)


Regards,


Rene

Bug#806947: coreutils: improve expr with huge numbers by GMP

[John Scott]

> The reason it doesn't currently build that way is that it would
> as a side effect raise the priority of libgmp, and I'm not sure that
> using expr for big numbers is worth making libgmp mandatory on a minimal
> debian install.
It appears this is no longer the case, GMP is a required part of an install. 
The dependency chain now goes GMP → Nettle → GnuTLS → apt and systemd

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

Bug#963857: gammaray: FTBFS on IPv6-only environments

[Dmitry Shachnev]

Control: severity -1 important

On Wed, Jul 01, 2020 at 12:47:48PM +0300, Dmitry Shachnev wrote:
> I cannot reproduce this bug using your instructions. Can you please check
> again if it happens with Qt 5.14 from unstable (and with gammaray 2.11.1-2
> from unstable too)?

As I am unable to reproduce this bug, I am downgrading the severity to prevent
gammaray auto-removal from testing.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#963284: pd-unauthorized: diff for NMU version 0.1-4.1

[Adrian Bunk]

Control: tags 963284 + patch
Control: tags 963284 + pending

Dear maintainer,

I've prepared an NMU for pd-unauthorized (versioned as 0.1-4.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should cancel it.

cu
Adrian
diff -Nru pd-unauthorized-0.1/debian/changelog pd-unauthorized-0.1/debian/changelog
--- pd-unauthorized-0.1/debian/changelog	2020-04-13 22:17:47.0 +0300
+++ pd-unauthorized-0.1/debian/changelog	2020-07-20 18:44:29.0 +0300
@@ -1,3 +1,10 @@
+pd-unauthorized (0.1-4.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove local sys_sockerror() prototypes. (Closes: #963284)
+
+ -- Adrian Bunk   Mon, 20 Jul 2020 18:44:29 +0300
+
 pd-unauthorized (0.1-4) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru pd-unauthorized-0.1/debian/patches/series pd-unauthorized-0.1/debian/patches/series
--- pd-unauthorized-0.1/debian/patches/series	2020-04-13 22:17:47.0 +0300
+++ pd-unauthorized-0.1/debian/patches/series	2020-07-20 18:44:29.0 +0300
@@ -1,3 +1,4 @@
 fix_hardening.patch
 fix_Wreturn.patch
 spelling.patch
+sys_sockerror.patch
diff -Nru pd-unauthorized-0.1/debian/patches/sys_sockerror.patch pd-unauthorized-0.1/debian/patches/sys_sockerror.patch
--- pd-unauthorized-0.1/debian/patches/sys_sockerror.patch	1970-01-01 02:00:00.0 +0200
+++ pd-unauthorized-0.1/debian/patches/sys_sockerror.patch	2020-07-20 18:44:29.0 +0300
@@ -0,0 +1,47 @@
+Description: Remove local sys_sockerror() prototypes
+ The parameter became const.
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/963284
+
+--- pd-unauthorized-0.1.orig/mp3fileout~.c
 pd-unauthorized-0.1/mp3fileout~.c
+@@ -84,7 +84,6 @@ static struct timeval ztout;
+ 
+ static char   *mp3fileout_version = "mp3fileout~: mp3 file streamer version 0.2, written by ydego...@free.fr";
+ 
+-extern void sys_sockerror(char *s);
+ 
+ void mp3fileout_closesocket(int fd)
+ {
+--- pd-unauthorized-0.1.orig/mp3streamin~.c
 pd-unauthorized-0.1/mp3streamin~.c
+@@ -83,7 +83,6 @@ static struct timeval ztout;
+ 
+ static char   *mp3streamin_version = "mp3streamin~: mp3 peer-to-peer streamer version 0.3, written by ydego...@free.fr";
+ 
+-extern void sys_sockerror(char *s);
+ 
+ void mp3streamin_closesocket(int fd)
+ {
+--- pd-unauthorized-0.1.orig/speexin~.c
 pd-unauthorized-0.1/speexin~.c
+@@ -30,6 +30,10 @@
+ #include 
+ #include 
+ 
++#if PD_MINOR_VERSION >= 37
++#include "s_stuff.h"
++#endif
++
+ #include 
+ #include 
+ #include 
+@@ -82,8 +86,6 @@ static struct timeval ztout;
+ 
+ static char   *speexin_version = "speexin~: speex voice quality streamer version 0.2, written by ydego...@free.fr";
+ 
+-extern void sys_sockerror(char *s);
+-
+ void speexin_closesocket(int fd)
+ {
+ #ifndef _WIN32

Bug#958720: [Pkg-phototools-devel] Bug#958720: Acknowledgement (darktable: Error at start - free(): invalid next size (fast))

[Ronny Bachmann]

The problem was my self compiled tool lensfun. With the Debian version
and an update of the database with "lensfun-update-data" the problem
seems to be solved.

Thanks Ronny

Bug#965379: Sometimes draws hyphens after each word

[Andrey Rahmatullin]

Package: fbreader
Version: 0.12.10dfsg2-4
Severity: normal

Most of the time, fbreader draws hyphens after each word in any book including
its built-in help page. IIRC this started after switching to GTK. I cannot find
any useful patterns in reproducibility, or guess why does it happen (I also
tried looking at lsof and the config dir and check and change the app
settings). I can reproduce it on two testing/sid systems, including one with an
empty config.



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

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

Versions of packages fbreader depends on:
ii  libc6  2.31-1
ii  libsqlite3-0   3.32.3-1
ii  libstdc++6 10.1.0-6
ii  libzlcore0.13  0.12.10dfsg2-4
ii  libzltext0.13  0.12.10dfsg2-4
ii  libzlui-gtk0.12.10dfsg2-4

Versions of packages fbreader recommends:
ii  sensible-utils  0.0.12+nmu1

fbreader suggests no packages.

-- no debconf information

Bug#965301: opendht FTBFS in unstable.

[Adrian Bunk]

Control: reassign -1 libmsgpack-dev 3.3.0-3
Control: close -1 3.3.0-4
Control: affects -1 src:opendht

On Sun, Jul 19, 2020 at 09:16:59PM -0400, James McCoy wrote:
> On Sun, Jul 19, 2020 at 03:30:18AM +0100, peter green wrote:
> > Secondly on architectures where the build can be attempted it is failing
> > with
> > 
> > > [  3%] Building CXX object CMakeFiles/opendht-static.dir/src/utils.cpp.o
> > > /usr/bin/c++  -DASIO_STANDALONE -DOPENDHT_LOG=true 
> > > -DOPENDHT_PEER_DISCOVERY -DPACKAGE_VERSION=\"2.1.0\" -I/<>/. 
> > > -I/<>/include -I/<>/include/opendht 
> > > -I/<>/obj-x86_64-linux-gnu/include  -g -O2 
> > > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type 
> > > -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden 
> > > -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -fPIC   
> > > -std=gnu++14 -o CMakeFiles/opendht-static.dir/src/utils.cpp.o -c 
> > > /<>/src/utils.cpp
> > > In file included from /usr/include/msgpack/adaptor/cpp11/chrono.hpp:14,
> > >  from /usr/include/msgpack/type.hpp:38,
> > >  from /usr/include/msgpack.hpp:22,
> > >  from /<>/include/opendht/utils.h:23,
> > >  from /<>/src/utils.cpp:23:
> > > /usr/include/msgpack/v1/adaptor/cpp11/chrono.hpp:20:10: fatal error: 
> > > boost/numeric/conversion/cast.hpp: No such file or directory
> > >20 | #include 
> > >   |  ^~~
> > > compilation terminated.
> > 
> > I am ccing the msgpack-c maintainers in case this is a problem in that 
> > package.
> 
> Yes, in this case it is, since that code doesn't require explicit opt-in
> to use boost.  I'll update libmsgpack-dev's Depends.

Thanks, I am moving this bug where it was fixed.

> Cheers,

cu
Adrian

Bug#965327: Lower severity of bash-completion-with-hashbang

[Vincent Bernat]

 ❦ 20 juillet 2020 15:00 +00, Chris Lamb:

>> Lintian is a very useful tool, but too many stuff is a warning while
>> this is a matter of opinion. I have given up on the "info" level
>> since a long time for similar reasons. I would like not to give up on
>> the "warning" level.
>
> (It is a shame to read you have given up on "I:" and it would be nice
> if Lintian earned back your trust. Now that it has a slightly simpler
> system of classification, could you file a wishlist bugs against what
> you feel are, or felt were, the worst offenders?)

Thanks! I'll reuse -I and will open bugs if needed.
-- 
Don't just echo the code with comments - make every comment count.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature