Bug#996425: hitch: diff for NMU version 1.7.1-2.1

[Stig Sandbeck Mathisen]

Adrian Bunk  writes:

> Dear maintainer,
>
> I've prepared an NMU for hitch (versioned as 1.7.1-2.1) and uploaded
> it to DELAYED/2. Please feel free to tell me if I should cancel it.
>
> cu
> Adrian
>
>

Hello Adrian,

Thank you for the bugfix, I'll pull it into the packaging repo as well.

-- 
Stig Sandbeck Mathisen
Debian Developer

Bug#1010937: transition: gdal

[Sebastiaan Couwenberg]

On 5/13/22 16:45, Bas Couwenberg wrote:

mysql-workbench (8.0.26+dfsg-1) FTBFS due to gcc-11 (#998833).

vtk6 (6.3.0+dfsg2-8.1) FTBFS due to gcc-11 (#984398).


Neither of these are in testing, and they still depends


qgis (3.22.5+dfsg-1) FTBFS due to sip6 (#1009939) and not supporting
Multi-Arch paths for gdal which is fixed in git.


sip6 (6.6.1+dfsg-2) fixed the issue causing qgis to FTBFS, and the gdal 
issue was subsequently fixed in qgis (3.22.6+dfsg-1).


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1006388: [debian-mysql] Bug#1006388: Bug#1006388: libmariadb-dev-compat: multi-arch is not present or not working. I am unable to install multiple architectures into Docker "debian:stable" as an e

[Dick Hollenbeck]

On 5/22/22 18:34, Otto Kekäläinen wrote:
> Hello Dick!
> 
> On Thu, Feb 24, 2022 at 2:54 PM Otto Kekäläinen  wrote:
>>
>> Thanks Dick for reporting #1006388!
>>
>> We need to fix multi-arch support on MariaDB 10.6 in unstable before
>> we can consider backporting anything to Bullseye/10.5. Right now we
>> don't have anybody on the maintainer team who fully understands the
>> Debian multi-arch stuff.
>>
>> If you have suggestions on how to update the debian/control file to
>> have correct Multi-Arch stanzas, please submit a Merge Request.
>>
>> https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
> 
> Do you want to take a shot at fixing this in the MariaDB packaging in Debian?

My docker image is building without error, and this is a new behaviour.
Something got fixed, and I have no reason to think anything I am using is still 
broken.
My docker image is softplc/toolkit
at docker hub.
So thank you.

Bug#1010739: haskell-distributive: FTBFS: doctests: : cannot satisfy -package distributive-0.6.2

[Scott Talbert]

Control: reassign -1 haskell-devscripts
Control: affects -1 haskell-distributive

On Sun, 8 May 2022, Daniel Schepler wrote:


doctests: : cannot satisfy -package distributive-0.6.2
  (use -v for more information)


This is due to another regression in haskell-devscripts (the problem does 
not exist with haskell-devscripts 0.16.2).  I'm not entirely sure of the 
cause yet.


Scott

Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?

[Zhang Boyang]

Hi,

On 2022/5/23 01:18, Thomas Schmitt wrote:

How can i verify that the resulting ISO properly announces all its
packages ?
(If i install it to a VM, what must i do to challenge its completeness ?)


I came up with a idea. Maybe you can use 'debian-cd' to create a DLBD 
set, say disc A1 and A2, then create another ALL-IN-ONE set, say disc B. 
Then compare if A1+A2==B. There might be small differences, like the 
package order in Packages.gz, but I think if the overall format is OK, 
then it will be OK.



Best Regards,
Zhang Boyang

Bug#988540: im-config: breaks the keyboard configuration

[Osamu Aoki]

Hi,

After reading your message, I have revised text around
  https://wiki.debian.org/Keyboard#Input_method_and_XIM

> -Original Message-
> From: Vincent Lefevre 
> To: Osamu Aoki 
> Cc: Gunnar Hjalmarsson , 988...@bugs.debian.org, brian m.
> carlson 
> Subject: Re: Bug#988540: im-config: breaks the keyboard configuration
> Date: Mon, 23 May 2022 00:54:45 +0200
> 
> On 2022-05-23 06:23:58 +0900, Osamu Aoki wrote:
> > Anyway, XIM is dead end for some foreseeable future.  My conclusion is 
> > "don't use
> > XIM" as backend of ibus. 
> > https://wiki.debian.org/Keyboard#Input_method_and_XIM
> 
> So, if I understand correctly, users may no longer be able to use xterm
> when ibus is installed.

Users may no longer be able to use xterm **reliably for some non-ASCII inputs** 
when
ibus is **activated**.

> After some search, I've found
> 
>   https://vas.neocities.org/custom_keyboard_layout_xkb_ibus.html
> 
> "This guide will help you create a custom keyboard layout in xkb and
> configure ibus to play along nicely."
> 
> But this is very unclear (and perhaps wrong for other users).
> 

That's an extreme customization.  There are many ways to get to the goal.

For most people, ibus supports XKB functionality defined by xkb-options with 
ibus's
internal mechanism.  As long as you use gnome-terminal etc.  (not for xterm nor 
rxvt)
to get keyboard input, ibus supports xkb-options based substitution smoothly.

I hope my updates
around 
https://wiki.debian.org/Keyboard#Multi-language_keyboard_configuration_strategy
make it clear.

Regards,

Osamu

Bug#1011445: ruby-gitlab-license-finder,ruby-license-finder: error when trying to install together

[Andreas Beckmann]

Package: ruby-gitlab-license-finder,ruby-license-finder
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 6.14.2.1-2
Control: found -1 7.0.1-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-license-finder.
  Preparing to unpack .../ruby-license-finder_7.0.1-1_all.deb ...
  Unpacking ruby-license-finder (7.0.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-license-finder_7.0.1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/license_finder', which is also in package 
ruby-gitlab-license-finder 6.14.2.1-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-license-finder_7.0.1-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/license_finder

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


ruby-gitlab-license-finder=6.14.2.1-2_ruby-license-finder=7.0.1-1.log.gz
Description: application/gzip

Bug#1011444: ruby-gitlab-markup: missing Breaks+Replaces: ruby-github-markup (<< 1.7.0+dfsg-4~)

[Andreas Beckmann]

Package: ruby-gitlab-markup
Version: 1.8.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../ruby-gitlab-markup_1.8.0-1_all.deb ...
  Unpacking ruby-gitlab-markup (1.8.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-gitlab-markup_1.8.0-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/github/commands/rest2html', 
which is also in package ruby-github-markup 1.7.0+dfsg-3
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-gitlab-markup_1.8.0-1_all.deb

(There is no file conflict with ruby-github-markup (1.7.0+dfsg-4) in sid.)


cheers,

Andreas


ruby-github-markup=1.7.0+dfsg-3_ruby-gitlab-markup=1.8.0-1.log.gz
Description: application/gzip

Bug#1011443: faker,ruby-faker: error when trying to install together

[Andreas Beckmann]

Package: faker,ruby-faker
Severity: serious
Tags: sid bookworm
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.9.3-0.1
Control: found -1 2.20.0-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-faker.
  Preparing to unpack .../19-ruby-faker_2.20.0-1_all.deb ...
  Unpacking ruby-faker (2.20.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-9mjGF0/19-ruby-faker_2.20.0-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/faker', which is also in package faker 
0.9.3-0.1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-9mjGF0/19-ruby-faker_2.20.0-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/bin/faker

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


faker=0.9.3-0.1_ruby-faker=2.20.0-1.log.gz
Description: application/gzip

Bug#1011442: libopendsp-dev,libopenvlbi-dev: missing Breaks+Replaces: libopenvlbi1-dev (<< 1.23)

[Andreas Beckmann]

Package: libopendsp-dev,libopenvlbi-dev
Version: 1.23.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libopendsp-dev_1.23.0-1_amd64.deb ...
  Unpacking libopendsp-dev (1.23.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libopendsp-dev_1.23.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/OpenVLBI/dsp.h', which is also in package 
libopenvlbi1-dev:amd64 1.22.8-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libopendsp-dev_1.23.0-1_amd64.deb

  Preparing to unpack .../libopenvlbi-dev_1.23.0-1_amd64.deb ...
  Unpacking libopenvlbi-dev:amd64 (1.23.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libopenvlbi-dev_1.23.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/OpenVLBI/vlbi.h', which is also in package 
libopenvlbi1-dev:amd64 1.22.8-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libopenvlbi-dev_1.23.0-1_amd64.deb


cheers,

Andreas


libopenvlbi1-dev=1.22.8-1_libopendsp-dev=1.23.0-1.log.gz
Description: application/gzip

Bug#986050: linux-image-5.10.0-13-amd64: happened on Debian 11

[js1]

Package: src:linux
Followup-For: Bug #986050
X-Debbugs-Cc: sujiannm...@gmail.com

Dear Maintainer,

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

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

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


-- Package-specific info:
** Version:
Linux version 5.10.0-13-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.106-1 (2022-03-17)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-13-amd64 
root=UUID=27876db4-6b63-4db1-b0bd-b8c9522ced14 ro

** Tainted: W (512)
 * kernel issued warning

** Kernel log:
[   24.244554] amdgpu: Topology: Add CPU node
[   24.397058] Adding 1000444k swap on /dev/sda3.  Priority:-2 extents:1 
across:1000444k FS
[   27.196659] r8169 :01:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8106e-1.fw
[   27.201666] RTL8208 Fast Ethernet r8169-0-100:00: attached PHY driver 
[RTL8208 Fast Ethernet] (mii_bus:phy_addr=r8169-0-100:00, irq=IGNORE)
[   27.486836] r8169 :01:00.0 enp1s0: Link is Down
[   29.065112] r8169 :01:00.0 enp1s0: Link is Up - 100Mbps/Full - flow 
control rx/tx
[   34.870322] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   34.873034] Bluetooth: BNEP filters: protocol multicast
[   34.875676] Bluetooth: BNEP socket layer initialized
[   35.035370] NET: Registered protocol family 38
[   35.215856] tun: Universal TUN/TAP device driver, 1.6
[ 9691.802850] FS-Cache: Loaded
[ 9691.853689] Key type dns_resolver registered
[ 9692.009745] FS-Cache: Netfs 'cifs' registered for caching
[ 9692.037235] Key type cifs.spnego registered
[ 9692.037343] Key type cifs.idmap registered
[ 9692.038014] CIFS: Attempting to mount //10.23.21.101/D
[ 9692.038136] CIFS: No dialect specified on mount. Default has changed to a 
more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use 
the less secure SMB1 dialect to access old servers which do not support 
SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[438563.405272] perf: interrupt took too long (2513 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79500
[614490.868916] CIFS: Attempting to mount //10.23.21.101/D
[711290.31] perf: interrupt took too long (3148 > 3141), lowering 
kernel.perf_event_max_sample_rate to 63500
[1006084.072858] r8169 :01:00.0 enp1s0: Link is Down
[1006085.740273] r8169 :01:00.0 enp1s0: Link is Up - 100Mbps/Full - flow 
control rx/tx
[1006156.165124] [ cut here ]
[1006156.165283] NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out
[1006156.165437] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:467 
dev_watchdog+0x24d/0x260
[1006156.165581] Modules linked in: tcp_diag udp_diag inet_diag md4 
sha512_ssse3 sha512_generic nls_utf8 cifs libarc4 dns_resolver fscache libdes 
cmac algif_hash tun algif_skcipher af_alg bnep nft_chain_nat xt_MASQUERADE 
nf_nat nft_counter xt_tcpudp xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 
amdgpu nf_defrag_ipv4 nft_compat nf_tables libcrc32c crc32c_generic gpu_sched 
nfnetlink uvcvideo nls_ascii nls_cp437 videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 vfat fat videobuf2_common videodev mc rtsx_usb_ms memstick 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi 
snd_hda_intel snd_intel_dspcfg btusb soundwire_intel 
soundwire_generic_allocation snd_soc_core btrtl btbcm snd_compress btintel 
soundwire_cadence bluetooth snd_hda_codec snd_hda_core edac_mce_amd snd_hwdep 
jitterentropy_rng soundwire_bus drbg kvm ansi_cprng snd_pcm irqbypass 
ecdh_generic ecc snd_timer snd ghash_clmulni_intel crc16 soundcore 
ideapad_laptop aesni_intel radeon sparse_keymap rfkill libaes
[1006156.166056]  crypto_simd cryptd sg wmi sp5100_tco glue_helper watchdog 
joydev ttm pcspkr serio_raw evdev drm_kms_helper ccp cec efi_pstore 
i2c_algo_bit rng_core fam15h_power k10temp acpi_cpufreq button ac drm fuse 
configfs efivarfs ip_tables x_tables autofs4 jfs rtsx_usb_sdmmc mmc_core 
rtsx_usb sd_mod sr_mod cdrom t10_pi crc_t10dif crct10dif_generic ahci xhci_pci 
libahci xhci_hcd libata r8169 ehci_pci ehci_hcd realtek crct10dif_pclmul 
mdio_devres crct10dif_common crc32_pclmul psmouse usbcore crc32c_intel scsi_mod 
i2c_piix4 libphy usb_common battery video
[1006156.168484] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.10.0-13-amd64 #1 
Debian 5.10.106-1
[1006156.168626] Hardware name: LENOVO INVALID/VIUU4, BIOS 1QCN32WW 08/18/2016
[1006156.168752] RIP: 0010:dev_watchdog+0x24d/0x260
[1006156.168843] Code: c9 c9 fd ff eb a9 4c 89 f7 c6 05 d8 61 10 01 01 e8 48 9a 
fa ff 44 89 e9 4c 89 f6 48 c7 c7 18 b9 56 b8 48 89 c2 e8 32 3b 14 00 <0f> 0b eb 
8a 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 1f 44
[1006156.169103] RSP: 0018:bac0800fceb8 EFLAGS: 00010286
[100615

Bug#1011441: openvlbi-data: missing Breaks+Replaces: libopenvlbi1 (<< 1.23)

[Andreas Beckmann]

Package: openvlbi-data
Version: 1.23.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../openvlbi-data_1.23.0-1_all.deb ...
  Unpacking openvlbi-data (1.23.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/openvlbi-data_1.23.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/OpenVLBI/cat/iau/13CO.txt', which is also in 
package libopenvlbi1:amd64 1.22.8-1
  Errors were encountered while processing:
   /var/cache/apt/archives/openvlbi-data_1.23.0-1_all.deb


cheers,

Andreas


libopenvlbi1=1.22.8-1_openvlbi-data=1.23.0-1.log.gz
Description: application/gzip

Bug#1006388: [debian-mysql] Bug#1006388: Bug#1006388: libmariadb-dev-compat: multi-arch is not present or not working. I am unable to install multiple architectures into Docker "debian:stable" as an e

[Otto Kekäläinen]

Hello Dick!

On Thu, Feb 24, 2022 at 2:54 PM Otto Kekäläinen  wrote:
>
> Thanks Dick for reporting #1006388!
>
> We need to fix multi-arch support on MariaDB 10.6 in unstable before
> we can consider backporting anything to Bullseye/10.5. Right now we
> don't have anybody on the maintainer team who fully understands the
> Debian multi-arch stuff.
>
> If you have suggestions on how to update the debian/control file to
> have correct Multi-Arch stanzas, please submit a Merge Request.
>
> https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian

Do you want to take a shot at fixing this in the MariaDB packaging in Debian?

Bug#1006111: [debian-mysql] Bug#1006111: mariadb-server: wrong groupby result in newly filled myISAM table

[Otto Kekäläinen]

On Fri, May 20, 2022 at 10:19 PM Cameron Davidson  wrote:
>
> On 20-Feb-22 10:42, Otto Kekäläinen wrote:
> > Hello!
> >
> > Thanks for using MariaDB. In the scope of Debian packaging we do not
> > fix upstream bugs. If you have a reproducible test case you could file
> > bug report upstream.
> >
> > We are in the process of uploading 10.3.34, 10.5.15 and 10.6.7 to
> > Debian. If these versions fix the issue then we can mark the issue
> > resolved for Debian.
>
> Hello,
>
> the issue I reported has been fixed for me  in the recent update.

Ok, nice

Bug#1001843: [debian-mysql] Bug#1001843: Bug#1001843: libmariadb-dev: mariadb_config reports incorrect plugin directory

[Otto Kekäläinen]

Control: tags -1 moreinfo

Hello Akira!

Was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001843 already
solved for you?

Bug#1011440: libsnmp-perl: behaviour fixed in do_not_callback_for_failed_reports.diff reintroduced in bullseye

[Ole Peder Brandtzæg]

Package: libsnmp-perl
Version: 5.9+dfsg-3+b1
Severity: normal
Tags: upstream

Dear Maintainer,

Upon upgrading from buster to bullseye this weekend, which included
libsnmp-perl going from 5.7.3 to 5.9, we noticed that one of our Perl
scripts utilising SNMP started segfaulting. Stacktraces[0] indicate
similar behaviour to what Steinar H. Gunderson described in his
do_not_callback_for_failed_reports patch.[1] Looking at the source tree,
it appears this patch was commented out just after 5.8 was released,[2]
presumably due to this upstream refactor of the receive API.[3] My
knowledge of both C and SNMP is unfortunately too lacking for it to be
apparent to me what would need to change to make it possible to reapply
the patch to the refactored functions. Any ideas on how to proceed?

All the best,
Ole Peder Brandtzæg

P.S. This is my time reporting a bug with a Debian package – do let me
know if I've done something wrong or you require additional information!

[0]: https://pastebin.com/366kWZNS
[1]: https://marc.info/?l=net-snmp-coders&m=141374910528458&w=3
[2]:
https://salsa.debian.org/debian/net-snmp/-/commit/20442f3b7a0410f5da27399017436c623c705415?page=2
[3]:
https://github.com/net-snmp/net-snmp/commit/a9ce31c4b8187aea07a648cf115e956159ac072e

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

Kernel: Linux 5.17.5 (SMP w/40 CPU threads; PREEMPT)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NO:en_DK:en_US:en_GB:en
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: default

Versions of packages libsnmp-perl depends on:
ii  libc6   2.31-13+deb11u3
ii  libnetsnmptrapd40   5.9+dfsg-3+b1
ii  libsnmp40   5.9+dfsg-3+b1
ii  perl5.32.1-4+deb11u2
ii  perl-base [perlapi-5.32.0]  5.32.1-4+deb11u2

libsnmp-perl recommends no packages.

libsnmp-perl suggests no packages.

-- no debconf information

Bug#988540: im-config: breaks the keyboard configuration

[Vincent Lefevre]

On 2022-05-23 06:23:58 +0900, Osamu Aoki wrote:
> Anyway, XIM is dead end for some foreseeable future.  My conclusion is "don't 
> use
> XIM" as backend of ibus. https://wiki.debian.org/Keyboard#Input_method_and_XIM

So, if I understand correctly, users may no longer be able to use xterm
when ibus is installed.

After some search, I've found

  https://vas.neocities.org/custom_keyboard_layout_xkb_ibus.html

"This guide will help you create a custom keyboard layout in xkb and
configure ibus to play along nicely."

But this is very unclear (and perhaps wrong for other users).

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

Bug#1011439: easy-rsa: autopkgtest regression with OpenSSL 3.0

[Adrian Bunk]

Control: retitle -1 easy-rsa does not support OpenSSL 3.0
Control: forwarded -1 https://github.com/OpenVPN/easy-rsa/pull/492

Looking closer, it seems the autopkgtest failure is just the tip of the 
iceberg and >= 3.0.9 contains more fixes for OpenSSL 3.0 support.

cu
Adrian

Bug#1011439: easy-rsa: autopkgtest regression with OpenSSL 3.0

[Adrian Bunk]

Source: easy-rsa
Version: 3.0.8-1
Severity: serious
Tags: patch
Forwarded: https://github.com/OpenVPN/easy-rsa/pull/468

https://ci.debian.net/packages/e/easy-rsa/unstable/amd64/

...
Using SSL: openssl OpenSSL 3.0.3 3 May 2022 (Library: OpenSSL 3.0.3 3 May 2022)
Enter PEM pass phrase:
40B4F1F3547F:error:1465:UI routines:UI_set_result_ex:result too 
small:../crypto/ui/ui_lib.c:884:You must type in 4 to 1024 characters
40B4F1F3547F:error:146B:UI routines:UI_process:processing 
error:../crypto/ui/ui_lib.c:544:while reading strings
40B4F1F3547F:error:0480006D:PEM routines:PEM_def_callback:problems getting 
password:../crypto/pem/pem_lib.c:62:
40B4F1F3547F:error:07880109:common libcrypto 
routines:do_ui_passphrase:interrupted or cancelled:../crypto/passphrase.c:184:
40B4F1F3547F:error:1C80009F:Provider routines:p8info_to_encp8:unable to get 
passphrase:../providers/implementations/encode_decode/encode_key2any.c:116:

Easy-RSA error:

Failed to build the CA

autopkgtest [22:28:15]: test basic-usage: ---]
autopkgtest [22:28:16]: test basic-usage:  - - - - - - - - - - results - - - - 
- - - - - -
basic-usage  FAIL non-zero exit status 1

Bug#860342: python3-taglib: Newer upstream releases available since Jan 21, 2014

[Boyuan Yang]

Control: tags 860342 -moreinfo
Control: fixed 860342 1.5.0-1
Control: close 860342
X-Debbugs-CC: rharw...@club.cc.cmu.edu

Hi,

On Fri, 14 Apr 2017 15:38:03 -0400 Robbie Harwood 
wrote:
> Package: python3-taglib
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> Please update to a newer version of the package.  This looks unmaintained
and
> I would have filed an RM request save that there are packages that depend on
> this in the archive.

I believe the latest upstream release has been packaged in Debian Sid/Testing.
I will upload the new version onto bullseye-backports later. This bug should
be considered as done.

Thanks,
Boyuan Yang


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

Bug#756400: pytaglib: Please include a python2 package

[Boyuan Yang]

X-Debbugs-CC: ja...@jpleau.ca
Control: tags 756400 +wontfix
Control: close 756400

Hi,

On Tue, 29 Jul 2014 10:30:58 -0400 Jason Pleau  wrote:
> Source: pytaglib
> Severity: wishlist
> 
> Hello!
> 
> Would it be possible to include a python-pytaglib package from this source
> package, in order to have a python2 version?
> 
> The reason I do need it is because python-nautilus from the archives runs
> extensions as python2, and the extension I am writing for Nautilus uses
> pytaglib.
> 
> I realize that we want to go forward with Python and prefer 3 over 2, but I
> don't think there is any harm in supporting both in two different packages.
> 
> This could be a bug for nautilus-python instead, but I'm not sure if it's
> possible to have it run extensions in both python2 and python3, or if it
could
> break peoples python extension. I filed it here, since this is (imho) the
> easier way.
> 
> (Also, upstream seem to have fixed his non-free file, so if we do a version
> bump (to 0.4.1) I *think* we could remove the dfsg level from the version.)

Given current condition of python2 sunset, I believe this issue is no longer
valid. Closing accordingly. If you have any other concerns, please feel free
to open a new bug report.

Thanks,
Boyuan Yang


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

Bug#1010992: sstp-client FTBFS on IPV6-only buildds

[Jonathan Rubenstein]

Control: severity -1 normal

A build from the 17th for 1.0.17+b1 completed with no errors. I think 
this bug can be closed. At the very least, it is not RC.


Is it possible the builder was faulty?

Failing build from 2022-05-14:
https://buildd.debian.org/status/fetch.php?pkg=sstp-client&arch=amd64&ver=1.0.17-1%2Bb1&stamp=1652557579&raw=0

Successful build from 2022-05-17:
https://buildd.debian.org/status/fetch.php?pkg=sstp-client&arch=amd64&ver=1.0.17-1%2Bb1&stamp=1652827337&raw=0


Best,
Jonathan Rubenstein

Bug#1006581: xmltooling: FTBFS with OpenSSL 3.0

[Adrian Bunk]

On Sun, Mar 06, 2022 at 11:38:15AM +0100, Ferenc Wágner wrote:
> Sebastian Andrzej Siewior  writes:
> 
> > Your package is failing to build using OpenSSL 3.0 with the
> > following error:
> >
> > | make[5]: Entering directory '/<>/xmltoolingtest'
> > | ../build-aux/test-driver: line 112: 1662259 Segmentation fault  "$@" 
> > >> "$log_file" 2>&1
> > | FAIL: xmltoolingtest
> 
> Hi,
> 
> I suspect that this stems from an OpenSSL version mismatch among the
> dependencies (xml-security-c or cURL, which both use OpenSSL themselves)
> and XMLTooling itself.
>...

The segmentation fault looks fixed with the dependencies rebuilt with
OpenSSL 3.0, but the test still fails:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xmltooling.html

> Thanks,
> Feri

cu
Adrian

Bug#988540: im-config: breaks the keyboard configuration

[Osamu Aoki]

Hi,

> -Original Message-
> From: Vincent Lefevre 
...
> On 2022-05-22 21:59:35 +0900, Osamu Aoki wrote:
> > I also have updated around XIM bugs with more subdued tone. As long
> > as you type ASCII characters only, you may not hit bugs (I hope.)
> 
> I use XKB specifically to enter non-ASCII characters: accented
> characters (either with a direct mapping to the Unicode character
> or via a dead key), Greek letters (via a dead key) and math symbols
> (either with a direct mapping to the Unicode character or via the
> compose key). But at the end, I always get a single Unicode character
> (I do not need to handle combinations of Unicode characters).
> 
> These where things that one could mostly do for years, even before XKB
> (e.g. with xmodmap), though xmodmap had additional limitations with
> some keys.
> 
> It seems that the issues mentioned in
> 
>   https://bugzilla.redhat.com/show_bug.cgi?id=2013610
> 
> concern input methods that are not possible with XKB (at least I'm
> not aware of).

This bug affects xterm, and rxvt which use XIM.  In this, the upstream Takao 
Fujiwara
mention on 2021-10-26 03:24:40 UTC that there are 2 possible solutions both of 
which
seems to cause difficult transition.  His tone for XIM has been very negative.  
He
mentions old bug from 2015 such as:

https://github.com/ibus/ibus/issues/1713 

In this, he is filing bug to X and it seems still open (or moved to other site?)
https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/34

Anyway, XIM is dead end for some foreseeable future.  My conclusion is "don't 
use
XIM" as backend of ibus. https://wiki.debian.org/Keyboard#Input_method_and_XIM

FYI: im-config currently sets up to run "ibus-daemon --xim" with
IBUS_ENABLE_SYNC_MODE=0 

Anyway, seeing discussion like https://github.com/ibus/ibus/issues/1713 make me
wonder to add functionality to stop running "ibus-daemon --xim" or change
IBUS_ENABLE_SYNC_MODE value to accommodate conflicting user needs.  For now, I 
am
avoiding to create complicated mess by not adding extra functionalities.

> > > -Original Message-
> > > From: Vincent Lefevre 
> > 
> > 
> > 
> > > I can read that xterm uses XIM mechanism and XIM mechanism is buggy. :(
> > > I use mostly xterm (actually a patched version). The other terminals
> > > have font and mouse-wheel handling issues.
> > 
> > Hmmm... gnome-terminal may be bloated but we can use other lighter
> > terminal programs.
> 
> I've tried xfce4-terminal and lxterminal and they have the same issues
> as gnome-terminal.
> 
> > I don't have any issue displaying English/French/Chinese/Japanese/...
> > So I am curious why you are struggling with font and terminal.
> 
> For xterm, this is due to a change in libfreetype6
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866960

I recall seeing such problem before.

> (I've patched xterm, but this is rather ugly because this depends
> very much on the font and its size, and I finally think that this
> should become a preference). I'm not sure whether this is the same
> cause for the other terminals, because the libfreetype6 developers
> recommend to use the unrounded metrics, which xterm doesn't do. In
> xfce4-terminal, allowing the vertical cell spacing in the terminal
> preferences to be slightly less than 1 might solve the issue if
> this is supported internally.

I am not annoyed by this problem now under gnome-terminal nor the problem of 
mouse.  

Let's keep these issues out of this discussion.

Osamu
> 

Bug#1011438: open-ath9k-htc-firmware: Drop BSD-4 advertisement clause

[Bastian Germann]

Source: open-ath9k-htc-firmware
Severity: minor
Version: 1.4.0-106-gc583009+dfsg1-1

The BSD-4-clause-from-Regents advertising clause is not needed anymore:
https://github.com/qca/open-ath9k-htc-firmware/commit/f6e017c06e129c289d2ebe24613c4f933a9772ad

Please drop it in d/copyright and drop the comment that you want to introduce 
with
https://salsa.debian.org/jscott/open-ath9k-htc-firmware/-/commit/957614de9235f2416a3054fa05d980adf7af4c35 ("The GPL is 
generally regarded as incompatible with the four-clause BSD license due to the latter's advertising clause.")

Bug#1006509: moonshot-trust-router: diff for NMU version 3.5.4+1+nmu1

[Adrian Bunk]

On Sun, May 22, 2022 at 02:13:57PM -0600, Sam Hartman wrote:
> > "Adrian" == Adrian Bunk  writes:
> 
> Adrian> Dear maintainer,
> 
> Adrian> I've prepared an NMU for moonshot-trust-router (versioned as
> Adrian> 3.5.4+1+nmu1) and uploaded it to DELAYED/2. Please feel free
> Adrian> to tell me if I should cancel it.
> 
> This NMU looks good to me.  Feel free to accelerate it if you like, or
> feel free to leave in delayed/2.

Thanks, rescheduled for immediate upload.

cu
Adrian

Bug#1006582: xir: diff for NMU version 1.4.1-5.1

[Adrian Bunk]

On Sun, May 22, 2022 at 09:43:51PM +0100, Punit Agrawal wrote:
> Hi Adrian,

Hi Punit,

> Thank you for the patch and the NMU.
> I've had a quick look and don't see an issue with the changes. No need to
> cancel the NMU.
>...

thanks, rescheduled for immediate upload.

> Thanks,
> Punit

cu
Adrian

Bug#1011437: Should bind9-libs be shipped in bookworm?

[Adrian Bunk]

Source: bind9-libs
Version: 1:9.11.19+dfsg-2.1
Severity: serious
Tags: bookwoem sid
Control: block -1 by 942502 942501

Looking at #942501 and #942502, the intention seems to be to not
ship bind9-libs in bookworm.

Bug#1006582: xir: diff for NMU version 1.4.1-5.1

[Punit Agrawal]

Hi Adrian,

Thank you for the patch and the NMU.
I've had a quick look and don't see an issue with the changes. No need to
cancel the NMU.

I'll also probably port the patch to the new upstream release if it's still
not working with OpenSSL 3.0.

Thanks,
Punit

On Sun, May 22, 2022 at 8:39 PM Adrian Bunk  wrote:

> Control: tags 1006582 + patch
> Control: tags 1006582 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for xir (versioned as 1.4.1-5.1) and uploaded
> it to DELAYED/2. Please feel free to tell me if I should cancel it.
>
> cu
> Adrian
>

Bug#824520: RFP: subsurface -- scuba diving logbook

[Salvo Tomaselli]

My advice is to forget this. Upstream is really uncooperative and
Torvalds went to conferences to talk about this (conveniently
forgetting to mention he was depending an unstable library whose
author said "Don't use this yet")

The video of that conference that happened ages ago is still shared
today to "prove" how the distribution model is bad, distro maintainers
are mean, and so on.

Just my advice.


Il giorno dom 22 mag 2022 alle ore 13:58 David Bremner
 ha scritto:
>
> Philippe Cerfon  writes:
>
> > btw... I've just seen there's:
> > http://ppa.launchpad.net/subsurface/subsurface/ubuntu
> > (including packaging for all the deps)
> >
> > So maybe, it could be much simpler to get this back into Debian, by
> > simply basing the Debian packaging on Ubuntu's.
>
> To be honest, I doubt that helps, since the hard part is not just making
> packages (my repo on salsa already does that), but making them in a way
> acceptable to debian policy, which is unlikely to be a priority for a
> PPA.
>
> d



-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

http://ltworf.github.io/ltworf/

Bug#995573: Any hope to see a fix coming ?

[Gacquer William]

Hello

A few months later, the bug persists.
Sadly I can't contribute but I pray every minute for the bug to be fixed :)

Best regards
William Gacquer

Bug#963777: condor: CVE-2019-18823

[Markus Koschany]

Control: tags -1 patch

Please find attached the patch to address CVE-2019-18823 for version
8.6.8~dfsg.1-2, also applied in Debian 10 "Buster".

Markus
From: Markus Koschany 
Date: Fri, 20 May 2022 14:08:49 +0200
Subject: CVE-2019-18823

Bug-Debian: https://bugs.debian.org/963777
Origin: https://github.com/htcondor/htcondor/commit/95eaee86e7ad3852c17df46a1b8b193dabd1fd14
Origin: https://github.com/htcondor/htcondor/commit/07e33c8b14aa00e04d045d4d79c963db082a3129
Origin: https://github.com/htcondor/htcondor/commit/cbcb93695a932d511c1c7bd40aed1eabeff01d8d
Origin: https://github.com/htcondor/htcondor/commit/3916209123a8ef762b7a9cd84ca0cf8b2cd99716
Origin: https://github.com/htcondor/htcondor/commit/5c84c6f0b3db4eda1eec42c2c708069bb9393f0b
---
 src/condor_daemon_client/dc_schedd.cpp   |  2 +-
 src/condor_daemon_client/dc_startd.cpp   | 40 +++---
 src/condor_includes/condor_commands.h|  2 ++
 src/condor_schedd.V6/qmgmt.cpp   | 26 +---
 src/condor_schedd.V6/qmgmt.h |  3 +++
 src/condor_schedd.V6/qmgmt_receivers.cpp | 14 +++
 src/condor_schedd.V6/schedd.cpp  |  6 ++---
 src/condor_shadow.V6.1/shadow.cpp|  4 ++-
 src/condor_startd.V6/Resource.cpp|  4 +--
 src/condor_startd.V6/command.cpp | 28 ++---
 src/condor_startd.V6/command.h   |  2 +-
 src/condor_starter.V6.1/baseStarter.cpp  |  4 +--
 src/condor_status.V6/prettyPrint.cpp |  2 +-
 src/condor_tools/history.cpp |  4 +--
 src/condor_tools/transform_ads.cpp   |  4 +--
 src/condor_utils/compat_classad.cpp  | 42 +++-
 src/condor_utils/compat_classad.h|  8 +++---
 src/condor_utils/file_transfer.cpp   |  8 +-
 src/condor_who/who.cpp   |  4 +--
 19 files changed, 153 insertions(+), 54 deletions(-)

diff --git a/src/condor_daemon_client/dc_schedd.cpp b/src/condor_daemon_client/dc_schedd.cpp
index fe935b0..bf291fa 100644
--- a/src/condor_daemon_client/dc_schedd.cpp
+++ b/src/condor_daemon_client/dc_schedd.cpp
@@ -1878,7 +1878,7 @@ bool DCSchedd::getJobConnectInfo(
 
 	if( IsFulldebug(D_FULLDEBUG) ) {
 		std::string adstr;
-		sPrintAd(adstr, output, true);
+		sPrintAd(adstr, output);
 		dprintf(D_FULLDEBUG,"Response for GET_JOB_CONNECT_INFO:\n%s\n",
 adstr.c_str());
 	}
diff --git a/src/condor_daemon_client/dc_startd.cpp b/src/condor_daemon_client/dc_startd.cpp
index be0101f..9e5693c 100644
--- a/src/condor_daemon_client/dc_startd.cpp
+++ b/src/condor_daemon_client/dc_startd.cpp
@@ -135,6 +135,12 @@ ClaimStartdMsg::writeMsg( DCMessenger * /*messenger*/, Sock *sock ) {
 	m_job_ad.Assign("_condor_SEND_PAIRED_SLOT",
 		param_boolean("CLAIM_PAIRED_SLOT",true));
 
+		// Insert an attribute in the request ad to inform the
+		// startd that this schedd is capable of understanding
+		// the newer protocol where any claim id in the response
+		// is encrypted.
+	m_job_ad.Assign("_condor_SECURE_CLAIM_ID", true);
+
 	if( !sock->put_secret( m_claim_id.c_str() ) ||
 	!putClassAd( sock, m_job_ad ) ||
 	!sock->put( scheduler_addr_to_send.c_str() ) ||
@@ -234,14 +240,29 @@ ClaimStartdMsg::readMsg( DCMessenger * /*messenger*/, Sock *sock ) {
 		Reply of 4 (REQUEST_CLAIM_PAIR) means claim accepted by a slot
 		  that is paired, and the partner slot ad and claim id will be
 		  sent next.
+		Reply of 5 (REQUEST_CLAIM_LEFTOVERS_2) is the same as 3, but
+		  the claim id is encrypted.
+		Reply of 6 (REQUEST_CLAIM_PAIR_2) is the same as 4, but
+		  the claim id is encrypted.
 	*/
 
 	if( m_reply == OK ) {
 			// no need to log success, because DCMsg::reportSuccess() will
 	} else if( m_reply == NOT_OK ) {
 		dprintf( failureDebugLevel(), "Request was NOT accepted for claim %s\n", description() );
-	} else if( m_reply == REQUEST_CLAIM_LEFTOVERS ) {
-	 	if( !sock->get(m_leftover_claim_id) ||
+	} else if( m_reply == REQUEST_CLAIM_LEFTOVERS || m_reply == REQUEST_CLAIM_LEFTOVERS_2 ) {
+		bool recv_ok = false;
+		if ( m_reply == REQUEST_CLAIM_LEFTOVERS_2 ) {
+			char *val = NULL;
+			recv_ok = sock->get_secret(val);
+			if ( recv_ok ) {
+m_leftover_claim_id = val;
+free(val);
+			}
+		} else {
+			recv_ok = sock->get(m_leftover_claim_id);
+		}
+		if( !recv_ok ||
 			!getClassAd( sock, m_leftover_startd_ad )  ) 
 		{
 			// failed to read leftover partitionable slot info
@@ -256,8 +277,19 @@ ClaimStartdMsg::readMsg( DCMessenger * /*messenger*/, Sock *sock ) {
 			// change reply to OK cuz claim was a success
 			m_reply = OK;
 		}
-	} else if( m_reply == REQUEST_CLAIM_PAIR ) {
-		if( !sock->get(m_paired_claim_id) ||
+	} else if( m_reply == REQUEST_CLAIM_PAIR || m_reply == REQUEST_CLAIM_PAIR_2 ) {
+		bool recv_ok = false;
+		if ( m_reply == REQUEST_CLAIM_PAIR_2 ) {
+			char *val = NULL;
+			recv_ok = sock->get_secret(val);
+			if ( recv_ok ) {
+m_paired_claim_id = val;
+free(val);
+			}
+		} else {
+			recv_ok = sock->get(m_paired_claim_id);
+		}
+		if( !recv_ok |

Bug#1010422: Bug#1011265: Britney fails to pin complete set in "Provides" api transitions [Was: Bug#1010422: transition: r-api-bioc-3.15]

[Andreas Tille]

Am Sun, May 22, 2022 at 07:43:35PM +0530 schrieb Nilesh Patra:
> >I've just commited a patch thet ignores the not yet packaged test
> >dependency which causes the test failure.  In any case r-bioc-scater
> 
> Then please make an upload.

https://salsa.debian.org/r-pkg-team/r-bioc-scater/-/jobs/2796964

   ->>   builddeps:. : Depends: r-cran-rcppml but it is not installable
 E: Unable to correct problems, you have held broken packages.

There was no other patch than the one I created ... and I think it
makes sense to wait for Build-Depends clearing new.  Thus I've set
a "block by".

> >needs to wait for r-cran-rcppml in new - may be some removal from
> >testing is needed in any case.
> 
> No, not really. I had already edited the description file in the last upload 
> to unbreak the transition, although I didn't observe the failing test locally.

Are you sure you pushed?

Kind regards

Andreas.

> >> [1] https://tracker.debian.org/pkg/r-bioc-scater
> >> [2] https://ci.debian.net/packages/r/r-bioc-scater/testing/amd64/
 

-- 
http://fam-tille.de

Bug#1008634: condor: CVE-2022-26110 / HTCONDOR-2022-0003

[Markus Koschany]

Control: tags -1 patch

Please find attached the patches to address CVE-2022-26110 for version
8.6.8~dfsg.1-2, also applied in Debian 10 "Buster".

Markus
From: Markus Koschany 
Date: Fri, 20 May 2022 14:09:15 +0200
Subject: CVE-2022-26110_1

Origin: https://github.com/htcondor/htcondor/commit/1cae7601d796725e7f5dd73fedf37f6fbbe379ca
---
 src/condor_daemon_core.V6/daemon_command.cpp | 40 
 src/condor_includes/condor_attributes.h  |  1 +
 2 files changed, 36 insertions(+), 5 deletions(-)

diff --git a/src/condor_daemon_core.V6/daemon_command.cpp b/src/condor_daemon_core.V6/daemon_command.cpp
index daa86ec..83d4082 100644
--- a/src/condor_daemon_core.V6/daemon_command.cpp
+++ b/src/condor_daemon_core.V6/daemon_command.cpp
@@ -1408,11 +1408,41 @@ DaemonCommandProtocol::CommandProtocolResult DaemonCommandProtocol::VerifyComman
 			m_perm = USER_AUTH_FAILURE;
 		}
 		else {
-			m_perm = daemonCore->Verify(
-		  command_desc.Value(),
-		  m_comTable[m_cmd_index].perm,
-		  m_sock->peer_addr(),
-		  m_user.Value() );
+// Authentication methods can limit the authorizations associated with
+// a given identity (at time of coding, only TOKEN does this); apply
+// these limits if present.
+			std::string authz_policy;
+			bool can_attempt = true;
+			if (m_policy && m_policy->EvaluateAttrString(ATTR_SEC_LIMIT_AUTHORIZATION, authz_policy)) {
+StringList authz_limits(authz_policy.c_str());
+authz_limits.rewind();
+const char *perm_cstr = PermString(m_comTable[m_cmd_index].perm);
+const char *authz_name;
+bool found_limit = false;
+while ( (authz_name = authz_limits.next()) ) {
+	if (!strcmp(perm_cstr, authz_name)) {
+		found_limit = true;
+		break;
+	}
+}
+bool has_allow_perm = !strcmp(perm_cstr, "ALLOW");
+if (!found_limit && !has_allow_perm) {
+	can_attempt = false;
+}
+			}
+			if (can_attempt) {
+m_perm = daemonCore->Verify(
+	command_desc.Value(),
+	m_comTable[m_cmd_index].perm,
+	m_sock->peer_addr(),
+	m_user.Value() );
+			} else {
+dprintf(D_ALWAYS, "DC_AUTHENTICATE: authentication of %s was successful but resulted in a limited authorization which did not include this command (%d %s), so aborting.\n",
+	m_sock->peer_description(),
+	m_req,
+	m_comTable[m_cmd_index].command_descrip);
+m_perm = USER_AUTH_FAILURE;
+			}
 		}
 
 	} else {
diff --git a/src/condor_includes/condor_attributes.h b/src/condor_includes/condor_attributes.h
index 7de9120..d230fb3 100644
--- a/src/condor_includes/condor_attributes.h
+++ b/src/condor_includes/condor_attributes.h
@@ -839,6 +839,7 @@ extern const char ATTR_SEC_AUTHENTICATED_USER [];
 #define ATTR_SEC_TRIED_AUTHENTICATION  "TriedAuthentication"
 #define ATTR_SEC_AUTHORIZATION_SUCCEEDED  "AuthorizationSucceeded"
 #define ATTR_SEC_RETURN_CODE  "ReturnCode"
+#define ATTR_SEC_LIMIT_AUTHORIZATION "LimitAuthorization"
 
 #define ATTR_MULTIPLE_TASKS_PER_PVMD  "MultipleTasksPerPvmd"
 
From: Markus Koschany 
Date: Fri, 20 May 2022 14:09:31 +0200
Subject: CVE-2022-26110_2

Origin: https://github.com/htcondor/htcondor/commit/8568e8ba65c9490f30a1089b6d4f8910e4bfbd6b
---
 src/condor_daemon_core.V6/daemon_command.cpp | 17 +
 1 file changed, 17 insertions(+)

diff --git a/src/condor_daemon_core.V6/daemon_command.cpp b/src/condor_daemon_core.V6/daemon_command.cpp
index 83d4082..4f2ddac 100644
--- a/src/condor_daemon_core.V6/daemon_command.cpp
+++ b/src/condor_daemon_core.V6/daemon_command.cpp
@@ -1141,6 +1141,23 @@ DaemonCommandProtocol::CommandProtocolResult DaemonCommandProtocol::Authenticate
 
 	if ( method_used ) {
 		m_policy->Assign(ATTR_SEC_AUTHENTICATION_METHODS, method_used);
+
+		// For CLAIMTOBE, explicitly limit the authorized permission
+		// levels to that of the current command and any implied ones.
+		if ( !strcasecmp(method_used, "CLAIMTOBE") ) {
+			std::string perm_list;
+			DCpermissionHierarchy hierarchy( m_comTable[m_cmd_index].perm );
+			DCpermission const *perms = hierarchy.getImpliedPerms();
+
+			// iterate through a list of this perm and all perms implied by it
+			for (DCpermission perm = *(perms++); perm != LAST_PERM; perm = *(perms++)) {
+if (!perm_list.empty()) {
+	perm_list += ',';
+}
+perm_list += PermString(perm);
+			}
+			m_policy->Assign(ATTR_SEC_LIMIT_AUTHORIZATION, perm_list);
+		}
 	}
 	if ( m_sock->getAuthenticatedName() ) {
 		m_policy->Assign(ATTR_SEC_AUTHENTICATED_NAME, m_sock->getAuthenticatedName() );


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

Bug#1006509: moonshot-trust-router: diff for NMU version 3.5.4+1+nmu1

[Sam Hartman]

> "Adrian" == Adrian Bunk  writes:

Adrian> Dear maintainer,

Adrian> I've prepared an NMU for moonshot-trust-router (versioned as
Adrian> 3.5.4+1+nmu1) and uploaded it to DELAYED/2. Please feel free
Adrian> to tell me if I should cancel it.

This NMU looks good to me.  Feel free to accelerate it if you like, or
feel free to leave in delayed/2.



signature.asc
Description: PGP signature

Bug#1006509: moonshot-trust-router: diff for NMU version 3.5.4+1+nmu1

[Adrian Bunk]

Control: tags 1006509 + patch
Control: tags 1006509 + pending

Dear maintainer,

I've prepared an NMU for moonshot-trust-router (versioned as 3.5.4+1+nmu1)
and uploaded it to DELAYED/2. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru moonshot-trust-router-3.5.4+1/debian/changelog 
moonshot-trust-router-3.5.4+1+nmu1/debian/changelog
--- moonshot-trust-router-3.5.4+1/debian/changelog  2020-12-24 
00:33:14.0 +0200
+++ moonshot-trust-router-3.5.4+1+nmu1/debian/changelog 2022-05-22 
22:44:42.0 +0300
@@ -1,3 +1,10 @@
+moonshot-trust-router (3.5.4+1+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't build with -Werror. (Closes: #1006509)
+
+ -- Adrian Bunk   Sun, 22 May 2022 22:44:42 +0300
+
 moonshot-trust-router (3.5.4+1) unstable; urgency=medium
 
   * New upstream version
diff -Nru moonshot-trust-router-3.5.4+1/debian/rules 
moonshot-trust-router-3.5.4+1+nmu1/debian/rules
--- moonshot-trust-router-3.5.4+1/debian/rules  2020-12-24 00:33:14.0 
+0200
+++ moonshot-trust-router-3.5.4+1+nmu1/debian/rules 2022-05-22 
22:44:38.0 +0300
@@ -9,6 +9,8 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+export DEB_CFLAGS_MAINT_APPEND = -Wno-error
+
 %:
dh $@ --with autoreconf 
 

Bug#996425: hitch: diff for NMU version 1.7.1-2.1

[Adrian Bunk]

Control: tags 996425 + patch
Control: tags 996425 + pending

Dear maintainer,

I've prepared an NMU for hitch (versioned as 1.7.1-2.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru hitch-1.7.1/debian/changelog hitch-1.7.1/debian/changelog
--- hitch-1.7.1/debian/changelog	2021-09-19 17:01:45.0 +0300
+++ hitch-1.7.1/debian/changelog	2022-05-22 22:24:47.0 +0300
@@ -1,3 +1,10 @@
+hitch (1.7.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't enable -Werror. (Closes: #996425)
+
+ -- Adrian Bunk   Sun, 22 May 2022 22:24:47 +0300
+
 hitch (1.7.1-2) unstable; urgency=medium
 
   * Reproducible build: Ensure documentation do not vary based on locale
diff -Nru hitch-1.7.1/debian/rules hitch-1.7.1/debian/rules
--- hitch-1.7.1/debian/rules	2021-09-19 17:01:45.0 +0300
+++ hitch-1.7.1/debian/rules	2022-05-22 22:24:14.0 +0300
@@ -31,6 +31,6 @@
 	rm -v debian/hitch/usr/share/doc/hitch/hitch.conf.example
 
 override_dh_auto_configure:
-	dh_auto_configure -- --enable-documentation --enable-warnings --with-lex --with-yacc
+	dh_auto_configure -- --enable-documentation --with-lex --with-yacc
 
 override_dh_auto_test:

Bug#1006582: xir: diff for NMU version 1.4.1-5.1

[Adrian Bunk]

Control: tags 1006582 + patch
Control: tags 1006582 + pending

Dear maintainer,

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

cu
Adrian
diff -Nru xir-1.4.1/debian/changelog xir-1.4.1/debian/changelog
--- xir-1.4.1/debian/changelog	2022-02-13 09:36:14.0 +0200
+++ xir-1.4.1/debian/changelog	2022-05-22 22:34:37.0 +0300
@@ -1,3 +1,10 @@
+xir (1.4.1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't build with -Werror. (Closes: #1006582)
+
+ -- Adrian Bunk   Sun, 22 May 2022 22:34:37 +0300
+
 xir (1.4.1-5) unstable; urgency=medium
 
   [ Vagrant Cascadian ]
diff -Nru xir-1.4.1/debian/patches/0006-No-Werror.patch xir-1.4.1/debian/patches/0006-No-Werror.patch
--- xir-1.4.1/debian/patches/0006-No-Werror.patch	1970-01-01 02:00:00.0 +0200
+++ xir-1.4.1/debian/patches/0006-No-Werror.patch	2022-05-22 22:34:37.0 +0300
@@ -0,0 +1,24 @@
+Description: Don't build with -Werror
+ Thie frequently breaks when new gcc or OpenSSL versions bring new warnings.
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1006582
+
+--- xir-1.4.1.orig/cmake/VitisCommon.cmake
 xir-1.4.1/cmake/VitisCommon.cmake
+@@ -16,11 +16,11 @@
+ 
+ set (CMAKE_CXX_STANDARD 14)
+ set (CMAKE_C_STANDARD 99)
+-set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -Wall -Werror -ggdb -O0 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 -fno-inline")
+-set(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_CXX_FLAGS_RELEASE} -O3 -Wall -Werror")
+-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=gnu++14 -Wall -Werror")
+-set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall -Werror")
+-set(CMAKE_EXE "${CMAKE_C_FLAGS} -Wall -Werror")
++set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -Wall -ggdb -O0 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 -fno-inline")
++set(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_CXX_FLAGS_RELEASE} -O3 -Wall")
++set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=gnu++14 -Wall")
++set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall")
++set(CMAKE_EXE "${CMAKE_C_FLAGS} -Wall")
+ set(CMAKE_SHARED_LINKER_FLAGS  "${CMAKE_SHARED_LINKER_FLAGS} -Wl,--no-undefined")
+ 
+ set(CMAKE_MACOSX_RPATH 1)
diff -Nru xir-1.4.1/debian/patches/series xir-1.4.1/debian/patches/series
--- xir-1.4.1/debian/patches/series	2022-02-13 09:35:45.0 +0200
+++ xir-1.4.1/debian/patches/series	2022-05-22 22:34:37.0 +0300
@@ -3,3 +3,4 @@
 0003-Install-cmake-files-in-multiarch-aware-locations.patch
 Fix-FTBFS-with-Werror-range-loop-construct-Closes-99.patch
 0005-cmake-vitis_version.c.in-Remove-the-build-date-from-.patch
+0006-No-Werror.patch

Bug#1011372: openvpn 2.6 fails to communicate due to auth errors

[Bernhard Schmidt]

Hi Antti,

> Upgrading to openvpn 2.6 breaks communication in a tunnel I'm using.
> Downgrading back to openvpn 2.5 fixes the problem.
>
> Openvpn brings up the tunnel interface but cannot receive data. Syslog
> reports auth algo inconsistency when initializing and auth errors when
> receiving traffic.

could you please check the changelog at 
https://github.com/OpenVPN/openvpn/blob/dco/Changes.rst whether some of 
the options described there make any sense to you?


I'm especially thinking of

Compatibility mode (--compat-mode)
The modernisation of defaults can impact the compatibility of 
OpenVPN 2.6.0 with older peers. The options --compat-mode allows UIs to 
provide users with an easy way to still connect to older servers.

Could you set

verb 2

I'm hoping to find some clue in the data pushed by the remote side.

Best Regards,
Bernhard

Bug#1011435: certbot does not use http_proxy from /etc/environment

[Florian La Roche]

Package: certbot
Version: 1.25.0-1
Severity: normal
X-Debbugs-Cc: florian.laro...@gmail.com

Dear Maintainer,

If you have "http_proxy" set in /etc/environment for a http proxy
server, this is not used with certbot.

best regards,

Florian La Roche


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

Kernel: Linux 5.17.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages certbot depends on:
ii  debconf [debconf-2.0]  1.5.79
ii  python33.10.4-1+b1
ii  python3-certbot1.25.0-1

certbot recommends no packages.

Versions of packages certbot suggests:
pn  python-certbot-doc  
pn  python3-certbot-apache  
ii  python3-certbot-nginx   1.25.0-1

-- debconf information:
  certbot/remove_live_certs: true

Bug#1011434: bluetoothctl no longer connects to HC-05

[Graham Knap]

Package: bluez
Version: 5.64-2

In mid-March, I was able to use the following sequence of commands to
connect an HC-05 Bluetooth serial module; probably with bluez 5.62-2.

$ sudo rfcomm bind rfcomm0 98:da:50:00:d6:02
$ bluetoothctl connect 98:da:50:00:d6:02

However, today the "bluetoothctl connect" command is failing. Here is the
output:

[CHG] Device 98:DA:50:00:D6:02 Connected: yes
[CHG] Device 98:DA:50:00:D6:02 ServicesResolved: yes
Failed to connect: org.bluez.Error.NotAvailable
br-connection-profile-unavailable

Another change in behaviour that I've noticed is that KDE's bluetooth UI
now displays a generic error message when pairing the HC05.

I have not made any configuration changes to my system in the last two
months, but I've been generally keeping it updated with Debian testing. Any
advice would be appreciated.

-- graham

Bug#1011433: votca-data: missing Breaks+Replaces: votca-xtp (<< 2022~)

[Andreas Beckmann]

Package: votca-data
Version: 2022-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../votca-data_2022-2_all.deb ...
  Unpacking votca-data (2022-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/votca-data_2022-2_all.deb (--unpack):
   trying to overwrite '/usr/share/votca/xtp/basis_sets/3-21G.xml', which is 
also in package votca-xtp 2021.2-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/votca-data_2022-2_all.deb


cheers,

Andreas


votca-xtp=2021.2-2_votca-data=2022-2.log.gz
Description: application/gzip

Bug#1011431: ocamlgraph: [INTL:pt] Update on Portuguese translation of MANPAGE

[Américo Monteiro]

Package: ocamlgraph
Version: 2.0.0-3
Tags: l10n, patch-
Severity: wishlist

Updated Portuguese translation for ocamlgraph'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



ocamlgraph_2.0.0-3_man.pt.po.gz
Description: application/gzip

Bug#1011430: RM: vkd3d [s390x] -- ROM; tests fail on s390x, not yet intended to be supported in a stable release

[Michael Gilbert]

package: ftp.debian.org
severity: normal

Please remove vkd3d binaries from s390x (testing only).  s390x is not
yet a supported architecture upstream and autopkg tests currently fail
for that architecture.  See #1010331.

Best wishes,
Mike

Bug#1011429: dds2tar: reproducible-builds: embedded build paths in /usr/bin/dds-dd

[Vagrant Cascadian]

Source: dds2tar
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The build path is embedded in /usr/bin/dds-dd:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/dds2tar.html

  /build/1st/dds2tar-2.5.2/dds2tar.c:382
  vs.
  /build/2/dds2tar-2.5.2/2nd/dds2tar.c:382

The attached patch fixes this by adjusting the Makefile to add CFLAGS to
the CCFLAGS variable, which includes the -ffile-prefix-map argument to
avoid embedding the absolute path in compiled files.


With this patch applied, dds2tar should build reproducibly on
tests.reproducible-builds.org!


live well,
  vagrant
From 0e9712a9542c383a7445599ebe1d14abe212349b Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 22 May 2022 17:58:40 +
Subject: [PATCH] Makefile: Add CFLAGS to CCFLAGS.

---
 Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index 3ecfad4..2f662c7 100644
--- a/Makefile
+++ b/Makefile
@@ -70,7 +70,7 @@ CCOPT=$(HPDAT) $(HPDAT4) $(EXP_STUFF) $(MATCH) $(BUFFER) \
 
 D=dds2tar-${V}
 
-CCFLAGS=-DVERSION=\"$V\"
+CCFLAGS=$(CFLAGS) -DVERSION=\"$V\"
 
 TAR=tar
 ARCHIVE=\
-- 
2.36.1



signature.asc
Description: PGP signature

Bug#1011428: cdbackup: reproducible-builds: embedded build paths in various binaries

[Vagrant Cascadian]

Source: cdbackup
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The build path is embedded in /usr/bin/cdbackup and /usr/bin/cdrestore:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/cdbackup.html

  /build/1st/cdbackup-0.7.1/cdbackup.c:421
  vs.
  /build/2/cdbackup-0.7.1/2nd/cdbackup.c:421

The attached patch fixes this by explicitly passing CFLAGS to
dh_auto_build in debian/rules, which includes the -ffile-prefix-map
argument to avoid embedding the absolute path in compiled files.


With this patch applied, cdbackup should build reproducibly on
tests.reproducible-builds.org!


live well,
  vagrant
From 5cc4d882ffe7bd447c315e43ced64bbee1b9a4ac Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 22 May 2022 17:40:35 +
Subject: [PATCH] debian/rules: Explicitly pass CFLAGS to dh_auto_build.

---
 debian/rules | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/rules b/debian/rules
index 123ed55..4618c51 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,6 +6,9 @@
 %:
 	dh  $@
 
+override_dh_auto_build:
+	dh_auto_build -- CFLAGS="$(CFLAGS)"
+
 # Use override_dh_* targets to customize this.
 # ---
 # Followings are the old debian/rules
-- 
2.36.1



signature.asc
Description: PGP signature

Bug#988540: im-config: breaks the keyboard configuration

[Vincent Lefevre]

On 2022-05-22 21:59:35 +0900, Osamu Aoki wrote:
> I also have updated around XIM bugs with more subdued tone. As long
> as you type ASCII characters only, you may not hit bugs (I hope.)

I use XKB specifically to enter non-ASCII characters: accented
characters (either with a direct mapping to the Unicode character
or via a dead key), Greek letters (via a dead key) and math symbols
(either with a direct mapping to the Unicode character or via the
compose key). But at the end, I always get a single Unicode character
(I do not need to handle combinations of Unicode characters).

These where things that one could mostly do for years, even before XKB
(e.g. with xmodmap), though xmodmap had additional limitations with
some keys.

It seems that the issues mentioned in

  https://bugzilla.redhat.com/show_bug.cgi?id=2013610

concern input methods that are not possible with XKB (at least I'm
not aware of).

> > -Original Message-
> > From: Vincent Lefevre 
> 
> 
> 
> > I can read that xterm uses XIM mechanism and XIM mechanism is buggy. :(
> > I use mostly xterm (actually a patched version). The other terminals
> > have font and mouse-wheel handling issues.
> 
> Hmmm... gnome-terminal may be bloated but we can use other lighter
> terminal programs.

I've tried xfce4-terminal and lxterminal and they have the same issues
as gnome-terminal.

> I don't have any issue displaying English/French/Chinese/Japanese/...
> So I am curious why you are struggling with font and terminal.

For xterm, this is due to a change in libfreetype6

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

(I've patched xterm, but this is rather ugly because this depends
very much on the font and its size, and I finally think that this
should become a preference). I'm not sure whether this is the same
cause for the other terminals, because the libfreetype6 developers
recommend to use the unrounded metrics, which xterm doesn't do. In
xfce4-terminal, allowing the vertical cell spacing in the terminal
preferences to be slightly less than 1 might solve the issue if
this is supported internally.

Concerning the mouse wheel (bug reported for gnome-terminal):

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

and this cannot be disabled (ditto with xfce4-terminal at least):

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921537#60

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

Bug#1011427: Backport 15.0 to bullseye

[Ari Pollak]

Package: pulseaudio
Version: 14.2-2
Severity: wishlist

Would it be possible to build the latest pulseaudio version for
bullseye-backports? I think it would be very useful for the improved
Bluetooth codec support, especially for headsets. I can try to help, but
I'm not currently familiar with the pulseaudio source.


-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

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

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libasound2   1.2.4-1.1
ii  libasound2-plugins   1.2.2-2
ii  libc62.31-13+deb11u3
ii  libcap2  1:2.44-1
ii  libdbus-1-3  1.12.20-2
ii  libgcc-s110.2.1-6
ii  libice6  2:1.0.10-1
ii  libltdl7 2.4.6-15
ii  liborc-0.4-0 1:0.4.32-1
ii  libpulse014.2-2
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.31-2
ii  libsoxr0 0.1.3-4
ii  libspeexdsp1 1.2~rc1.2-1.1
ii  libstdc++6   10.2.1-6
ii  libsystemd0  247.3-7
ii  libtdb1  1.4.3-1+b1
ii  libudev1 247.3-7
ii  libwebrtc-audio-processing1  0.3-1+b1
ii  libx11-6 2:1.7.2-1
ii  libx11-xcb1  2:1.7.2-1
ii  libxcb1  1.14-3
ii  libxtst6 2:1.2.3-1
ii  lsb-base 11.1.0
ii  pulseaudio-utils 14.2-2

Versions of packages pulseaudio recommends:
ii  dbus-user-session1.12.20-2
ii  libpam-systemd [logind]  247.3-7
ii  rtkit0.13-4

Versions of packages pulseaudio suggests:
ii  paprefs  1.1-2
ii  pavucontrol  4.0-2
ii  pavumeter0.9.3-4+b3
ii  udev 247.3-7

-- no debconf information

Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?

[Thomas Schmitt]

Hi,

i wrote:
> > I began to ponder about a shortcut in libisofs which would trust the
> > checksum file (-checksum-list , -md5-list) enough to omit the reading of
> > all the package files' content.

Steve McIntyre wrote:
> Cute idea (grin!), but it's a non-started - we wouldn't be able to
> generate the various checksums for the whole image.

Yeah. Ain't it sad ?


> > Would more than one empty line between paragraphs damage the readability ?

> Not sure, to be honest.

So i will have to let my script think more. (It's at 287 lines, meanwhile.)


> Might just work, yeah!

My script does meanwhile:
- Take as arguments the paths of
  boot_iso  boot_mount_directory  add_iso  add_mount_directory  result_iso
- Mount the bootable ISO (e.g. debian-11.3.0-amd64-DLBD-1.iso) and the
  add-on ISO (e.g. debian-11.3.0-amd64-DLBD-2.iso).
- Determine the release name $dist of the bootable ISO (e.g. "bullseye").
- Copy /dists and /md5sum.txt from bootable ISO to local working directory.
- Merge the /md5sum.txt of both ISOs.
- Read the paths from first checksummed file lists of both
  /dists/$dist/Release files, sort and uniq them. (I don't bet that both
  have the same list, although DVD-1 and DVD-2 have the same.)
- Merge the namesake .gz files from that list (if both exist) or copy .gz
  file from the add-on ISO (if not yet in bootable ISO).
- Create a new file /dists/$dist/Release with the header lines from the
  file in the bootable ISO and freshly computed checksums of the merged
  files.
- Produce the bootable result_iso, overwriting /dists and /md5sum.txt
  by the altered copies from the local directory.

This can be repeated by using result_iso as new boot_iso and another add_iso
and a new result_iso name.



How can i verify that the resulting ISO properly announces all its
packages ?
(If i install it to a VM, what must i do to challenge its completeness ?)


Have a nice day :)

Thomas

Bug#1011234: fakeroot doesn't correctly detect copied device nodes on ia64

[Clint Adams]

On Thu, May 19, 2022 at 10:48:13AM +0200, Mattias Ellert wrote:
> According to
> 
> https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/ia64/xstatver.h;h=f24ab4a9ee158d7f0890cd228b20bf1e278d332b;hb=HEAD
> 
> _STAT_VER should be 1 for ia64.
> 
> The libfakeroot.c has no check for ia64, and uses the default linux
> value of 3.

How long has this been broken?

Bug#1011426: bullseye-pu: package tcpdump/4.99.0-2+deb11u1

[Romain Francoise]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I would like to update the AppArmor profile for tcpdump in bullseye to
match the one in bookworm; the changes don't really qualify for a stable
update per se, but they are trivial and would be important
quality-of-life improvements for users who are not knowledgeable about
AppArmor and don't understand why they get -EPERM in some cases.

The update would fix the following bugs (both "normal"):
* "AppArmor grants access to *.pcap but not *.cap"
  https://bugs.debian.org/989433
* "apparmor profile prevents -C -W"
  https://bugs.debian.org/1010688

Full debdiff is attached.

Thanks.
diffstat for tcpdump-4.99.0 tcpdump-4.99.0

 changelog   |8 
 usr.bin.tcpdump |4 
 2 files changed, 12 insertions(+)

diff -Nru tcpdump-4.99.0/debian/changelog tcpdump-4.99.0/debian/changelog
--- tcpdump-4.99.0/debian/changelog 2021-01-15 23:41:47.0 +0100
+++ tcpdump-4.99.0/debian/changelog 2022-05-22 18:22:50.0 +0200
@@ -1,3 +1,11 @@
+tcpdump (4.99.0-2+deb11u1) bullseye; urgency=medium
+
+  * Minor AppArmor profile updates (debian/usr.bin.tcpdump):
++ Grant access to *.cap (closes: #989433).
++ Account for numerical suffix in filenames added by -W (closes: #1010688).
+
+ -- Romain Francoise   Sun, 22 May 2022 18:22:50 +0200
+
 tcpdump (4.99.0-2) unstable; urgency=medium
 
   * Add autopkgtest support, running the upstream test suite.
diff -Nru tcpdump-4.99.0/debian/usr.bin.tcpdump 
tcpdump-4.99.0/debian/usr.bin.tcpdump
--- tcpdump-4.99.0/debian/usr.bin.tcpdump   2021-01-03 21:25:50.0 
+0100
+++ tcpdump-4.99.0/debian/usr.bin.tcpdump   2022-05-22 18:19:03.0 
+0200
@@ -54,6 +54,10 @@
 
   # for -r, -F and -w
   /**.[pP][cC][aA][pP] rw,
+  /**.[cC][aA][pP] rw,
+  # -W adds a numerical suffix
+  /**.[pP][cC][aA][pP][0-9]* rw,
+  /**.[cC][aA][pP][0-9]* rw,
 
   # for convenience with -r (ie, read pcap files from other sources)
   /var/log/snort/*log* r,

Bug#1011420: opencu: missing Breaks+Replaces: cu

[Tobias Heider]

On Sun, May 22, 2022 at 02:43:17PM +0200, Andreas Beckmann wrote:
> Package: opencu
> Version: 3-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

Hey Andreas,

> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
> 
> From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package opencu.
>   Preparing to unpack .../archives/opencu_3-2_amd64.deb ...
>   Unpacking opencu (3-2) ...
>   dpkg: error processing archive /var/cache/apt/archives/opencu_3-2_amd64.deb 
> (--unpack):
>trying to overwrite '/usr/bin/cu', which is also in package cu 1.07-27+b1
>   Errors were encountered while processing:
>/var/cache/apt/archives/opencu_3-2_amd64.deb
> 
> 
> How are cu and opencu supposed to co-exist?
> Is cu supposed to be removed from the archive?

opencu is a replacement for uudp-cu in the sense that they provide a binary
with the same name and users installing opencu are unlikely to also uudp-cu.
The binaries are however not 100% cli compatible, so scripts written for
uudp-cu won't always work with opencu without adjustments.

It looks like we have a similar situation with netcat and netcat-openbsd where
the latter declares Breaks+Replaces netcat, so this seems like the correct
solution.

Regards,

Tobias

> 
> 
> cheers,
> 
> Andreas

Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?

[Steve McIntyre]

Hey Thomas!

On Sun, May 22, 2022 at 12:03:23PM +0200, Thomas Schmitt wrote:
>Steve McIntyre wrote:
>> youre initial guess is correct. We don't generate the .iso files
>> at all for the larger images [1]. This means we also don't have
>> torrent files for them [2].
>
>I began to ponder about a shortcut in libisofs which would trust the
>checksum file (-checksum-list , -md5-list) enough to omit the reading of
>all the package files' content.
>Size, ownership, permissions, et.al would still be taken from the package
>files on disk. No ISO image would emerge (because of no valid file content)
>but .jigdo and .template would be created.
>Probably libjte would need an API extension so that it knows that only
>the count parameter of a libjte_show_data_chunk() call is valid.
>Vice versa libisofs would have to ask libjte whether a particular file
>is covered by the checksum list.
>
>All tricky and probably not worth the risk of embarassing failure.

Cute idea (grin!), but it's a non-started - we wouldn't be able to
generate the various checksums for the whole image.

>So back to my idea of merging ISOs:
>
>> The debian-cd code in tools/make_disc_trees.pl is not documentation
>> **as such**, but it's exactly how we create disc trees:
>
>I am using it now for checking detail questions.
>
>
>> It's baiscally just making a self-contained apt repository on each medium.
>
>So
>  https://wiki.debian.org/DebianRepository/Format
>looks like the specs to follow.
>
>Question (to everybody):
>
>The description of Packages[.gz] files talks of "paragraphs" but does not
>exactly define a paragraph's end delimiter. From Packages.gz in the ISO
>i'd guess it is an empty line or the "Package" field of the next paragraph.
>
>Is an empty line needed between paragraphs ?

Yup, it's an empty line.

>Would more than one empty line between paragraphs damage the readability ?

Not sure, to be honest.

>Reason: I want to merge the Packages.gz files like
>
>  (gunzip   | gzip >temp_file
>
>but am not sure that the found Packages.gz will always end by an empty
>line.  So i could simply insert an echo between the gunzips, or simply
>trust that the empty line is not needed as separator, or begin to think ...

Might just work, yeah!

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< liw> everything I know about UK hotels I learned from "Fawlty Towers"

Bug#1011335: libssl3: using SSL is not possible in Kmail with the update to OpenSSL3

[Dominique Dumont]

On Fri, 20 May 2022 11:31:47 +0200 merlin  
wrote:
> On my computer the system installed is a Debian Sid AMD64 and I use Kmail to
> receive or send messages, for 4 days I could not receive or send messages 
using
> Kmail.
> When sending a message I had and I have the following error: transport
> interrupted TLS initialization failed.
> When receiving messages from Yahoo or Free mailboxes I have the error:
> unable to connect to server pop. the server immediately terminated the
> connection.
> After research the problem seems to come from SSL and precisely SSL in 
Debian
> SID is migrating to SSL3.

I use Kontact (similar to kmail) on Debian/sid, updated today and I don't have 
any issue with smtp.free.fr or imap.free.fr

Free recommends to use STARTTLS on smtp connection [1]. Could check your 
configuration ?

All the best

PS: this reply is posted via smtp.free.fr

[1] 
https://assistance.free.fr/articles/configurer-de-maniere-avancee-votre-logiciel-de-messagerie-609

Bug#1010090: closed by Adrian Bunk (Re: Bug#1010090: php-dompdf: CVE-2022-28368)

[Salvatore Bonaccorso]

Hi Adrian,

On Sun, May 22, 2022 at 01:09:03PM +, Debian Bug Tracking System wrote:
> > Hi,
> > 
> > The following vulnerability was published for php-dompdf.
> > 
> > I raise this as grave to ask the following question as well from
> > future inclusion in bookworm: Is php-dompdf still maintained? I notice
> > that it's at version 0.6.2 since stretch with one single NMU from the
> > reproducible builds team. Or should it be removed from Debian?
> 
> It is orphaned, and the maintainer of the reverse dependency has some
> interest in keeping it (see #978994).

Oh, in this case it is best if the reverse dependency maintainer picks
it acutually up. I agree there is noone to be forced, but I'm worried
that it's the same version back some releases, while there would be
several new upstream versions released in meanwhile which seem they
should be updated and enter bookworm accordingly.

> > CVE-2022-28368[0]:
> > | Dompdf 1.2.1 allows remote code execution via a .php file in the
> > | src:url field of an @font-face Cascading Style Sheets (CSS) statement
> > | (within an HTML input file).
> > 
> > 
> > If you fix the vulnerability please also make sure to include the
> > CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> >...
> 
> The vulnerability was introduced in 0.8.0, which is more recent than any 
> version currently in Debian:
> https://github.com/dompdf/dompdf/commit/0e0261b7bce372b3a05b712a023f6f742a22d57e

Thanks for triaging further the issue and updating the
security-tracker data!

Regards,
Salvatore

Bug#1011391: openssl: please support quictls patchset

[Sakirnth Nagarasa]

Hi

This patchset of OpenSSL is necessary to build the crypto helper
libraries for ngtcp2 with OpenSSL as well.

There was a pull request to support QUIC directly in OpenSSL, but it was
closed because OpenSSL wanted to implement a different QUIC
implementation. But according to the comments in the PR the community
seems not to be satisfied with this approach and it takes a while until
they implement it according to the OMC Release Requirements. So I assume
a lot of them will use this patchset like ngtcp2 already does.

URLs:
https://github.com/openssl/openssl/pull/8797 (Pull request)
https://www.mail-archive.com/openssl-project@openssl.org/msg02585.html
(OMC Release Requirements)

So it would be really nice if one of the options Jérémy Lal described
could be implemented.

Thanks
Sakirnth

Bug#1010422: Bug#1011265: Britney fails to pin complete set in "Provides" api transitions [Was: Bug#1010422: transition: r-api-bioc-3.15]

[Nilesh Patra]

On 22 May 2022 7:05:18 pm IST, Andreas Tille  wrote:
>Hi Graham,
>
>Am Sun, May 22, 2022 at 09:09:01AM +0200 schrieb Graham Inggs:
>> It looks like the only blocker now is waiting for r-bioc-scater [1] to age:
>> 
>> Too young, only 2 of 5 days old
>> 
>> It doesn't get 2-day migration because its autopkgtest regressed in
>> testing, sometime around 2021-09-23 [2].
>
>I've just commited a patch thet ignores the not yet packaged test
>dependency which causes the test failure.  In any case r-bioc-scater

Then please make an upload.

>needs to wait for r-cran-rcppml in new - may be some removal from
>testing is needed in any case.

No, not really. I had already edited the description file in the last upload to 
unbreak the transition, although I didn't observe the failing test locally.

>> [1] https://tracker.debian.org/pkg/r-bioc-scater
>> [2] https://ci.debian.net/packages/r/r-bioc-scater/testing/amd64/
>

-- 
Regards,
Nilesh

Bug#1011412: r-bioc-scater: autopkgtest regression in testing

[Andreas Tille]

Control: tags -1 pending
Control: block -1 by 1011064

The issue is fixed in Git but the new version can not be uploaded
since it needs r-cran-rcppml from new.

Kind regards

 Andreas.

Bug#1010422: Bug#1011265: Britney fails to pin complete set in "Provides" api transitions [Was: Bug#1010422: transition: r-api-bioc-3.15]

[Andreas Tille]

Hi Graham,

Am Sun, May 22, 2022 at 09:09:01AM +0200 schrieb Graham Inggs:
> It looks like the only blocker now is waiting for r-bioc-scater [1] to age:
> 
> Too young, only 2 of 5 days old
> 
> It doesn't get 2-day migration because its autopkgtest regressed in
> testing, sometime around 2021-09-23 [2].

I've just commited a patch thet ignores the not yet packaged test
dependency which causes the test failure.  In any case r-bioc-scater
needs to wait for r-cran-rcppml in new - may be some removal from
testing is needed in any case.
 
> I'll file a separate bug for that.

Feel free to do so but for the moment the issue is fixed in Git and
will be uploaded once the new Build-Depends is available.

Kind regards

  Andreas.
 
> [1] https://tracker.debian.org/pkg/r-bioc-scater
> [2] https://ci.debian.net/packages/r/r-bioc-scater/testing/amd64/

-- 
http://fam-tille.de

Bug#1011424: libg2c-dev: overly generic manpage name: real(3)

[Andreas Beckmann]

Package: libg2c-dev
Version: 1.6.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
manpage file name that now clashes with other packages:

  /usr/share/man/man3/real.3.gz


Andreas

Bug#1011423: ITP: qrtr -- Userspace reference implementation for the QRTR protocol

[Arnaud Ferraris]

Package: wnpp
Severity: wishlist
Owner: Arnaud Ferraris 
X-Debbugs-Cc: debian-de...@lists.debian.org, arnaud.ferra...@gmail.com

* Package name: qrtr
  Version : 0.3
  Upstream Author : Bjorn Andersson 
* URL : https://github.com/andersson/qrtr/
* License : BSD-3-clause
  Programming Lang: C
  Description : Userspace reference implementation for the QRTR protocol

QRTR is Qualcomm's IPC Router protocol, used for communicating with
services provided by remote processors. It is mandatory for taking
advantage of most features of recent Qualcomm SoCs, such as Wi-Fi,
cellular modem, sensors...

I plan to maintain this package as part of the DebianOnMobile team.

Bug#1011422: liblapack-doc: overly generic manpage name: real(3)

[Andreas Beckmann]

Package: liblapack-doc
Version: 3.10.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
manpage file name that now clashes with other packages:

  /usr/share/man/man3/real.3.gz


Andreas

Bug#1001593: php-easyrdf: flaky autopkgtest: Unable to connect to localhost:10101

[Adrian Bunk]

On Sun, Jan 16, 2022 at 07:38:22PM -0500, Marco Villegas wrote:
> El Sun, 16 Jan 2022 22:14:37 +0200
> Adrian Bunk  escribió:
> > ...
> > 
> > I've cancelled it.
> > 
> > ...
> 
> Adrian, thank you for canceling the upload.
> 
> I have now published a related change over the git repository on the
> debian/bullseye branch targeting unstable.

bullseye is stable, the next release will be bookworm.

> When I first looked at the problem I thought I have seen it before, and
> indeed, I have added a work-around for it for the first smoke test a
> while ago, but with curl and a fixed time to wait.
> 
> Just to keep the same approach, I added similar lines to the second
> smoke test. Please find more details on the related[1] commit now on
> salsa.
> 
> 1: 
> https://salsa.debian.org/php-team/pear/php-easyrdf/-/commit/eb3ecb4dbd17ace43150b9fabd2a7bc2230724f6
>  

If you are expecting someone (David?) to upload this, it was not stated 
clearly.

> Best,
> 
> -Marco

cu
Adrian

Bug#1011421: python3-clevercsv,python3-clevercsv-doc: both ship /usr/share/man/man1/clevercsv*.1.gz

[Andreas Beckmann]

Package: python3-clevercsv,python3-clevercsv-doc
Version: 0.7.4+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package python3-clevercsv-doc.
  Preparing to unpack .../6-python3-clevercsv-doc_0.7.4+ds-1_all.deb ...
  Unpacking python3-clevercsv-doc (0.7.4+ds-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-8i4axm/6-python3-clevercsv-doc_0.7.4+ds-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man1/clevercsv-code.1.gz', which is also 
in package python3-clevercsv 0.7.4+ds-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-8i4axm/6-python3-clevercsv-doc_0.7.4+ds-1_all.deb

These manpages are shipped in both packages:

usr/share/man/man1/clevercsv-code.1.gz
usr/share/man/man1/clevercsv-detect.1.gz
usr/share/man/man1/clevercsv-explore.1.gz
usr/share/man/man1/clevercsv-help.1.gz
usr/share/man/man1/clevercsv-standardize.1.gz
usr/share/man/man1/clevercsv-view.1.gz
usr/share/man/man1/clevercsv.1.gz


cheers,

Andreas


python3-clevercsv=0.7.4+ds-1_python3-clevercsv-doc=0.7.4+ds-1.log.gz
Description: application/gzip

Bug#988540: im-config: breaks the keyboard configuration

[Osamu Aoki]

Hi,

I also have updated around XIM bugs with more subdued tone.  As long as you type
ASCII characters only, you may not hit bugs (I hope.)


> -Original Message-
> From: Vincent Lefevre 



> I can read that xterm uses XIM mechanism and XIM mechanism is buggy. :(
> I use mostly xterm (actually a patched version). The other terminals
> have font and mouse-wheel handling issues.

Hmmm... gnome-terminal may be bloated but we can use other lighter terminal 
programs.

I don't have any issue displaying English/French/Chinese/Japanese/...  So I am
curious why you are struggling with font and terminal.

Are you using UTF-8 locale?  Even if you want to use text file encoded in 
Latin-1
mostly, it will be better to set up system as UTF-8 and use editor 
functionality to
access Latin-1 encoded files.

My terminal uses:

Backspace key generates ASCII DEL
Delete key generates ESCAPE sequence
Encoding Unicode -- UTF-8
Ambiguous width characters: narrow
Custom font: Hack Nerd Font

Regards,

Osamu

Bug#1011420: opencu: missing Breaks+Replaces: cu

[Andreas Beckmann]

Package: opencu
Version: 3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package opencu.
  Preparing to unpack .../archives/opencu_3-2_amd64.deb ...
  Unpacking opencu (3-2) ...
  dpkg: error processing archive /var/cache/apt/archives/opencu_3-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/cu', which is also in package cu 1.07-27+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/opencu_3-2_amd64.deb


How are cu and opencu supposed to co-exist?
Is cu supposed to be removed from the archive?


cheers,

Andreas


cu=1.07-27+b1_opencu=3-2.log.gz
Description: application/gzip

Bug#1011417: Bug#857540: scite: Scroll bar not moving when scrolling

[Andreas Ronnquist]

On Thu, 26 Oct 2017 17:09:36 +0200 Andreas Ronnquist  wrote:
 8< 
> 
> The problem is still there - but I am now under the impression that it
> is a libgtk3 problem, and not a SciTE problem.
> 
> See 
> https://bugzilla.gnome.org/show_bug.cgi?id=765410
> 

The SciTE part of this bug has been fixed in scite 5.2.3-1 (or
worked-around, to be honest) - So I clone it and reassign one of the
clones to scite and close it there. I believe there's other programs
that are affected (like Geany, as mentioned in the upstream bug), so I
keep this clone open here.

-- Andreas Rönnquist
gus...@debian.org

Bug#1011419: RM: tcpreplay [armhf mips64el mipsel] -- NBS; no longer built on these architectures

[Adrian Bunk]

Package: ftp.debian.org
Severity: normal
Control: block 1009199 by -1

tcpreplay (4.4.1-1) unstable; urgency=medium
...
  * Restrict architectures to those that do not require strict alignment

 -- Christoph Biedl   Thu, 21 Apr 2022 20:56:56 
+0200

Bug#1011393: openpace: FTBFS on arm64, armel and mips64el

[Adrian Bunk]

Control: retitle -1 openpace: frequent parallel FTBFS
Control: forwarded -1 https://github.com/frankmorgner/openpace/pull/56
Control: tags -1 patch

On Sat, May 21, 2022 at 07:22:29PM +0200, Sebastian Ramacher wrote:
> Source: openpace
> Version: 1.1.2+ds+git20220117+453c3d6b03a0-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> https://buildd.debian.org/status/fetch.php?pkg=openpace&arch=arm64&ver=1.1.2%2Bds%2Bgit20220117%2B453c3d6b03a0-1&stamp=1652780709&raw=0
> 
> 
> libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
> -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/cvc-print 
> cvc_print-cvc-print.o cvc_print-read_file.o cvc_print-cvc-print-cmdline.o  
> ./.libs/libeac.so ./.libs/libvc.a -lcrypto
> make[6]: Leaving directory '/<>/src'
> /usr/bin/help2man \
>   --output=cvc-print.1 \
>   --no-info \
>   --source='OpenPACE 1.1.2' \
>   ./cvc-print
> /bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic  -Wl,-z,relro -Wl,-z,now 
> -Wl,--as-needed -o cvc-print cvc_print-cvc-print.o cvc_print-read_file.o 
> cvc_print-cvc-print-cmdline.o libeac.la libvc.la -lcrypto  
> help2man: can't get `--help' info from ./cvc-print
> Try `--no-discard-stderr' if option outputs to stderr
> make[5]: *** [Makefile:1532: cvc-print.1] Error 127
> make[5]: *** Waiting for unfinished jobs
>...

This is not architecture specific, it is a parallel build failure.
Fix linked above.

> Cheers

cu
Adrian

Bug#951490: haskell-yaml: please split yaml2json out into a separate package

[Andreas Beckmann]

Control: severity -1 serious
Control: tag -1 sid bookworm

On Mon, 17 Feb 2020 11:37:42 + Jonathan Dowland  wrote:

/usr/bin/yaml2json is a potentially useful tool for many different people,
not just haskell hackers. The dep chain for libghc-yaml-dev is quite large.
On my system, it ruled out installing over a 3G network connection, even
though I already have lots of Haskell dev packages installed.

Please consider splitting it out into a separate binary package.


There is now a new package "reserialize" in the archive which also 
provides /usr/bin/json2yaml and /usr/bin/yaml2json (and thus causes file 
conflicts when attempting to install both packages) - maybe 
libghc-yaml-dev can just drop them now?



Andreas

Bug#1009750: reserialize: Fail to install because /usr/bin/json2yaml also contained in libghc-yaml-dev.

[Andreas Beckmann]

Control: severity -1 serious
Control: block -1 with 951490

On Sat, 16 Apr 2022 10:47:29 +0200 "Andrej Shadura"  
wrote:

Hi,

On Sat, 16 Apr 2022, at 10:05, Andreas Karnetzki wrote:
>dpkg: error processing archive
> /var/cache/apt/archives/reserialize_20210909-2_all.deb (--unpack):
> trying to overwrite '/usr/bin/json2yaml', which is also in package libghc-
> yaml-dev 0.11.4.0-1-b4



Wouldn’t Conflicts: libghc-yaml-dev be enough?


That's not what Conflicts is for. Why shouldn't one be able to use both 
packages in a project?


There was already #951490 against libghc-yaml-dev "haskell-yaml: please 
split yaml2json out into a separate package". Maybe libghc-yaml-dev can 
just drop the conflicting binaries now and reserialize adds

  Breaks+Replaces: libghc-yaml-dev (<< 0.11.4.0-2~)
(assuming that is the version no longer shipping them elsewhere).

Andreas

Bug#1011418: solaar: Display two icons in the systray

[Christian Marillat]

Package: solaar
Version: 1.1.3+dfsg-1
Severity: normal

Dear Maintainer,

When the PC is started an icon in displayed as seen in Solaar-1.png

Then a second icon is displayed above the first icon, as seen in Solaar-2.png

Also the mouse status is wrong.  Solaar tell me that the batterry is 15 %
when upower display 95.

Solaar need to be restarted to display the right status.

$ upower -d   
Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0
  native-path:  hidpp_battery_0
  model:MX Anywhere 3
  serial:   4090-59-a9-ba-47
  power supply: no
  updated:  dim. 22 mai 2022 14:25:07 (1 seconds ago)
  has history:  yes
  has statistics:   yes
  mouse
present: yes
rechargeable:yes
state:   discharging
warning-level:   none
percentage:  95%
icon-name:  'battery-full-symbolic'

Christian

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

Kernel: Linux 5.17.9-6 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages solaar depends on:
ii  adduser  3.121
ii  debconf [debconf-2.0]1.5.79
ii  gir1.2-ayatanaappindicator3-0.1  0.5.91-1
ii  gir1.2-gtk-3.0   3.24.33-2
ii  gir1.2-notify-0.70.7.12-1
ii  passwd   1:4.11.1+dfsg1-2
ii  python3  3.10.4-1+b1
ii  python3-evdev1.4.0+dfsg-1+b3
ii  python3-gi   3.42.1-1
ii  python3-psutil   5.9.0-1
ii  python3-pyudev   0.22.0-2
ii  python3-xlib 0.29-1
ii  python3-yaml 5.4.1-1+b1
ii  udev 250.4-1

Versions of packages solaar recommends:
ii  python3-dbus  1.2.18-3+b1
ii  upower0.99.18-2

solaar suggests no packages.

-- debconf information:
  solaar/use_plugdev_group: false

Bug#1011318: [Pkg-pascal-devel] Bug#1011318: Bug#1011318: fp terminal ide does not compile hello world

[Abou Al Montacir]

We got answer from upstream that explains the issue. The IDE does not use
/etc/fpc.cfg but /etc/fp.cfg which is not created by Debian package.

> > Can anyone using fp IDE check the following issue or at least let us 
> > know if it happens on stock FPC distributed binaries.
> 
> The IDE does not use fpc.cfg, but fp.cfg. The default installer script 
> creates such a file in lib/fpc/$fpcversion/ide/text with appropriate 
> search paths for the default units. The ide can find it there.
> 
> Note: if there is an existing existing fp.cfg in the current directory, 
> that will override the default one. This will probably be the case if 
> the IDE has been started before without it being able to find an 
> existing fp.cfg, because then it will ask to create one in the current 
> directory. So even if the package gets fixed, people may still have 
> problems afterwards if they don't delete local fp.cfg files (the same 
> goes for fp.dsk and fp.ini, but those are less likely to cause issues if 
> they're not based on the default ones).
-- 
Cheers,
Abou Al Montacir


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

Bug#824520: RFP: subsurface -- scuba diving logbook

[David Bremner]

Philippe Cerfon  writes:

> btw... I've just seen there's:
> http://ppa.launchpad.net/subsurface/subsurface/ubuntu
> (including packaging for all the deps)
>
> So maybe, it could be much simpler to get this back into Debian, by
> simply basing the Debian packaging on Ubuntu's.

To be honest, I doubt that helps, since the hard part is not just making
packages (my repo on salsa already does that), but making them in a way
acceptable to debian policy, which is unlikely to be a priority for a
PPA.

d

Bug#824520: RFP: subsurface -- scuba diving logbook

[David Bremner]

David Bremner  writes:

> Philippe Cerfon  writes:
>
>> btw... I've just seen there's:
>> http://ppa.launchpad.net/subsurface/subsurface/ubuntu
>> (including packaging for all the deps)
>>
>> So maybe, it could be much simpler to get this back into Debian, by
>> simply basing the Debian packaging on Ubuntu's.
>
> To be honest, I doubt that helps, since the hard part is not just making
> packages (my repo on salsa already does that), but making them in a way
> acceptable to debian policy, which is unlikely to be a priority for a
> PPA.

To be fair, the PPA is kept fairly up to date, while I have not updated
my repo on salsa for years. So for personal use on debian, building
from that PPA makes sense. Alternatively, there is also

 https://dfx.at/subsurface-debian/

which is explicitely targetted at debian.

Same issue there, I don't think the author is concerned with making the
package suitable for Debian.

Bug#1011407: src:v4l-utils: fails to migrate to testing for too long: ftbfs on armel and armhf + uploader built arch:all binaries

[Paul Gevers]

Hi Gregor,

On 22-05-2022 13:48, Gregor Jasny wrote:
I did not notice the build error on armel and armhf. Is there a way to 
subscribe to build failures of a package?


Yes, https://tracker.debian.org/accounts/subscriptions/

Do you have an idea how I could elegantly narrow-down the Architecture 
field of the qvidcap package from "linux-any" to not include armel and 
armhf?




That's how it looks right now:

Package: qvidcap
Section: utils
Architecture: linux-any

I'd like to add something like [!armel !armhf] to the field.


I think you can just do that, but I'm not 100% sure.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1011416: freeimage: FTBFS with tiff 4.4.0+

[GCS]

Source: freeimage
Version: 3.18.0+ds2-6
Severity: serious
Justification: FTBFS
Tags: ftbfs upstream bookworm sid

Hi,

With the upcoming release (4.4.0) of tiff your package FTBFS due to
using tiff internal API:
Source/Metadata/XTIFF.cpp:745:38: error: '_TIFFDataSize' was not
declared in this scope; did you mean 'TIFFDataType'?
  745 |
if((unsigned)_TIFFDataSize(tif_tag_type) !=
FreeImage_TagDataWidth(tag_type)) {
  |  ^
  |  TIFFDataType

Reason is that tiff internal is changed [1] and _TIFFDataSize() became
a public API but with a different function signature. It's now
TIFFFieldSetGetSize(const TIFFField* fip).
It seems your upstream is dead, but try to get it fixed.

Regards,
Laszlo/GCS
[1] 
https://gitlab.com/libtiff/libtiff/-/commit/11f3f279608ae9e68f014717393197f430f9be58

Bug#1011414: ruby-task-list,ruby-deckar01-task-list: duplicate packages

[Andreas Beckmann]

Package: ruby-task-list,ruby-deckar01-task-list
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 2.3.2-1

Hi,

both ruby-task-list and ruby-deckar01-task-list seem to be the same
package, please coordinate which one to keep (and maybe add a
transitional package if you decide for the "newer" one).

  Selecting previously unselected package ruby-deckar01-task-list.
  (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database 
... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading 
database ... 40%^M(Reading database ... 45%^M(Reading database ... 
50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database 
... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading 
database ... 80%^M(Reading database ... 85%^M(Reading database ... 
90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database 
... 9226 files and directories currently installed.)
  Preparing to unpack .../ruby-deckar01-task-list_2.3.2-2_all.deb ...
  Unpacking ruby-deckar01-task-list (2.3.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-deckar01-task-list_2.3.2-2_all.deb (--unpack):
   trying to overwrite 
'/usr/share/rubygems-integration/all/specifications/deckar01-task_list-2.3.2.gemspec',
 which is also in package ruby-task-list 2.3.2-1
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-deckar01-task-list_2.3.2-2_all.deb

Andreas

Bug#988540: im-config: breaks the keyboard configuration

[Vincent Lefevre]

On 2022-05-22 16:06:28 +0900, Osamu Aoki wrote:
> I have updated https://wiki.debian.org/Keyboard.
> 
> (debian-reference was updated in 2020-2021, I think.)
> 
> These should give clearer view on XKB/input method situation.
> 
> If you find errors, please feel free to correct them.

I can read that xterm uses XIM mechanism and XIM mechanism is buggy. :(
I use mostly xterm (actually a patched version). The other terminals
have font and mouse-wheel handling issues.

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

Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?

[Thomas Schmitt]

Hi,

Steve McIntyre wrote:
> youre initial guess is correct. We don't generate the .iso files
> at all for the larger images [1]. This means we also don't have
> torrent files for them [2].

I began to ponder about a shortcut in libisofs which would trust the
checksum file (-checksum-list , -md5-list) enough to omit the reading of
all the package files' content.
Size, ownership, permissions, et.al would still be taken from the package
files on disk. No ISO image would emerge (because of no valid file content)
but .jigdo and .template would be created.
Probably libjte would need an API extension so that it knows that only
the count parameter of a libjte_show_data_chunk() call is valid.
Vice versa libisofs would have to ask libjte whether a particular file
is covered by the checksum list.

All tricky and probably not worth the risk of embarassing failure.


So back to my idea of merging ISOs:

> The debian-cd code in tools/make_disc_trees.pl is not documentation
> **as such**, but it's exactly how we create disc trees:

I am using it now for checking detail questions.


> It's baiscally just making a self-contained apt repository on each medium.

So
  https://wiki.debian.org/DebianRepository/Format
looks like the specs to follow.

Question (to everybody):

The description of Packages[.gz] files talks of "paragraphs" but does not
exactly define a paragraph's end delimiter. From Packages.gz in the ISO
i'd guess it is an empty line or the "Package" field of the next paragraph.

Is an empty line needed between paragraphs ?
Would more than one empty line between paragraphs damage the readability ?

Reason: I want to merge the Packages.gz files like

  (gunzip temp_file

but am not sure that the found Packages.gz will always end by an empty
line.  So i could simply insert an echo between the gunzips, or simply
trust that the empty line is not needed as separator, or begin to think ...


Have a nice day :)

Thomas

Bug#1011254: The UDEB package "localechooser" contains probably some buggy source code in "05localechooser" file

[Philip Hands]

Jmkr  writes:

> I tested Phil's "sed" command in terminal like this (all one line - 
> email splits it):
>
> L=cs_CZ.UTF-8; sed -n 
> "/^${L%%_*}/"'{s/^[[:alpha:]]*;\([[:digit:]]\);.*/\1/p;q}' languagelist
>
> and it seemed to work - with "cs_CZ.UTF-8" locale it returned 2. But 
> some locales still returned wrong level. After using a modified "sed" 
> command I think I got it working even for locales like "zh_TW.UTF-8" or 
> "nn_NO.UTF-8" etc.:
>
> L=zh_TW.UTF-8; sed -n "/^${L%%_*}/"'{s/^[A-Za-z_]*;\([0-9]\);.*/\1/p;q}' 
> languagelist
>
> returns 3 and with "nn_NO.UTF-8" it returns 1. I guess "[[:alpha:]]" 
> does not include "_".

Oh, I thought I'd tested that (and remember being surprised that
[:alpha:] had seemed to include '_', so I must have deceived myself
there somehow).

Anyway, well spotted :-)

Actually, given that we don't care what's in the first field at that
point, and it's already matched the start of the country code, I think
this ought to work as well:

  "/^${L%%_*}/"'{s/^[^;]*;\([0-9]\);.*/\1/p;q}'

> Anyway it is a nice improvement doing all the work with one "sed" 
> process compared to that "wild pipelined bunch of cutting greps and 
> heads". So, thanks to what Phil "sed", I am now upgrading my version of 
> the script to the "sed" approach:).

:-)

I just pushed that change here:

  
https://salsa.debian.org/philh/localechooser/-/commit/f4845f6c8bad1ca11886ea2cff94653aa25045bc

which (once the pipeline runs) should generate a new mini-iso for testing.

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#1011318: [Pkg-pascal-devel] Bug#1011318: fp terminal ide does not compile hello world

[Abou Al Montacir]

Hi Steve,

Thank you reporting this issue.

On Fri, 2022-05-20 at 01:02 +, Steve Greenburg wrote:
> ...
> (1,1) Fatal: Can't find unit system used by
> Program  ▲
> (0) Fatal: Compilation aborted 
Yes I can reproduce.
> ...
> The config file is /etc/fpc.cfg and it mentions the above path but with
> symbols. For example it has '$fpcversion' instead of '3.2.2'. Strangely the
> 'fpc' compiler itself uses this file but has no problems. I have tested this
> on latest debian testing. I'm not sure how to fix the problem in fp itself
> however other than through the GUI or why it's not using the fpc.cfg file
> properly.
Using the following path in the GUI works also:
/usr/lib/x86_64-linux-gnu/fpc/$fpcversion/units/x86_64-linux/*
So the issue seems more that the IDE does not parse /etc/fpc.cfg rather than not
expanding the configuration variables.
Not sure if this is Debian specific or is also the case of upstream binaries.
I'll check with upstream.
-- 
Cheers,
Abou Al Montacir



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

Bug#1011413: inn2: nnrpd as distributed does not support $modify_headers, recompiled does

[Marc SCHAEFER]

Package: inn2
Version: 2.6.3-1+deb10u2
Severity: normal

Dear Maintainer,

I do this in my /etc/news/filter/filter_nnrpd.pl's filter_post:

   $modify_headers = 1;
   $hdr{'X-test'} = "42";

   return "";

However,

   - with stock INN2 package, the X-test header does not get added
   - doing apt-get source inn2 then dpkg-buildpackage -us -uc, then
 starting under news the generated /debian/inn2/usr/lib/news/bin/nnrpd -p 
42119 -D
 I can POST an article which will get the X-test header added

So, maybe there is some bizarre compatibility problem with my Perl installation 
and INN2?
I however just have normal i386 debian buster, except this change:

$ diff ./inn2-2.6.3/debian/inn2/usr/share/perl5/INN/Config.pm 
/usr/share/perl5/INN/Config.pm
123c123
< our $gpg = '/usr/bin/gpg1';
---
> our $gpg = '/usr/bin/gpg';
125c125
< our $pgp = '/usr/bin/pgp';
---
> our $pgp = '';

Thank you for any idea.

Have a nice sunday.

-- System Information:
Debian Release: 10.12
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (x86_64)

Kernel: Linux 4.19.0-20-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_CH.ISO-8859-1 (charmap=ISO-8859-1), LANGUAGE=C 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages inn2 depends on:
ii  cron [cron-daemon]  3.0pl1-134+deb10u1
ii  inn2-inews  2.6.3-1+deb10u2
ii  libc6   2.28-10+deb10u1
ii  libdb5.35.3.28+dfsg1-0.5
ii  libmime-tools-perl  5.509-1
ii  libpam0g1.3.1-5
ii  libperl5.28 5.28.1-6+deb10u1
ii  libsasl2-2  2.1.27+dfsg-1+deb10u2
ii  libssl1.1   1.1.1n-0+deb10u2
ii  lsb-base10.2019051400
ii  perl5.28.1-6+deb10u1
ii  perl-base [perlapi-5.28.1]  5.28.1-6+deb10u1
ii  postfix [mail-transport-agent]  3.4.14-0+deb10u1
ii  procps  2:3.3.15-2
ii  time1.7-25.1+b1
ii  zlib1g  1:1.2.11.dfsg-1+deb10u1

inn2 recommends no packages.

Versions of packages inn2 suggests:
ii  gnupg1  1.4.23-1
ii  libgd-perl  2.71-2
ii  libkrb5-3   1.17-3+deb10u3
ii  wget1.20.1-1.1

-- Configuration Files:
/etc/init.d/inn2 changed [not included]
/etc/logcheck/ignore.d.server/inn2 [Errno 13] Permission denied: 
'/etc/logcheck/ignore.d.server/inn2'
/etc/logcheck/violations.ignore.d/inn2 [Errno 13] Permission denied: 
'/etc/logcheck/violations.ignore.d/inn2'
/etc/news/control.ctl changed [not included]
/etc/news/expire.ctl changed [not included]
/etc/news/filter/filter_innd.pl changed [not included]
/etc/news/filter/filter_nnrpd.pl changed [not included]
/etc/news/incoming.conf changed [not included]
/etc/news/innfeed.conf changed [not included]
/etc/news/newsfeeds changed [not included]
/etc/news/nocem.ctl changed [not included]
/etc/news/readers.conf changed [not included]
/etc/news/subscriptions changed [not included]

-- debconf information:
  inn2/preinst-upgrade1: false
  inn2/preinst-upgrade-largefiles: false
  inn2/postinst-cannot-start:

-- debsums errors found:
debsums: changed file /usr/share/perl5/INN/Config.pm (from inn2 package)

Bug#1011323: Acknowledgement (lablgtk2: Please remove the obsolete gtkgl/glarea component)

[Nicolas Boulenguez]

Here is the patch.
>From cd9a07159f574cab3c21497fd47528adc7526235 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Thu, 19 May 2022 12:24:00 +0200
Subject: Remove the gtkgl/glarea component

No package depends on liblablgtk2-gl-ocaml, and it is the last package
depending on libgtkgl2, which should be removed from Debian (#967808).

diff --git a/debian/META.lablgtk2-gl b/debian/META.lablgtk2-gl
deleted file mode 100644
index 0fab3c5..000
--- a/debian/META.lablgtk2-gl
+++ /dev/null
@@ -1,9 +0,0 @@
-version="2.18.5"
-directory="+lablgtk2"
-requires = "lablgtk2"
-
-package "gtkgl" (
-  requires = "lablgtk2 lablgl"
-  archive(byte) = "lablgtkgl.cma"
-  archive(native) = "lablgtkgl.cmxa"
-)
diff --git a/debian/control b/debian/control
index fd8f51b..e7fd344 100644
--- a/debian/control
+++ b/debian/control
@@ -9,10 +9,8 @@ Build-Depends:
  debhelper-compat (= 13),
  dh-ocaml,
  ocaml,
- liblablgl-ocaml-dev,
  libncurses5-dev,
  libgtk2.0-dev,
- libgtkgl2.0-dev,
  librsvg2-dev,
  libgtkspell-dev,
  ocaml-findlib
@@ -35,19 +33,6 @@ Description: runtime libraries for OCaml bindings for GTK+ version 2
  This package include only the dynamic libraries needed for running dynamic
  bytecode executables.
 
-Package: liblablgtk2-gl-ocaml
-Architecture: any
-Depends:
- ${ocaml:Depends},
- ${shlibs:Depends},
- ${misc:Depends}
-Provides: ${ocaml:Provides}
-Description: runtime libraries for OCaml bindings to GtkGL
- lablgtk2 contains bindings for GTK+ 2.x and Objective Caml.
- .
- This package include only the dynamic libraries needed for running dynamic
- bytecode executables using GtkGL functionalities.
-
 Package: liblablgtk2-gnome-ocaml
 Architecture: any
 Depends:
@@ -63,7 +48,7 @@ Description: runtime libraries for OCaml bindings to GNOME
 
 Package: liblablgtk2-ocaml-dev
 Architecture: any
-Suggests: liblablgtk2-gl-ocaml-dev, liblablgtk2-gnome-ocaml-dev
+Suggests: liblablgtk2-gnome-ocaml-dev
 Depends:
  libgtk2.0-dev,
  libgtkspell-dev,
@@ -77,22 +62,6 @@ Description: OCaml bindings to Gtk+ version 2
  .
  This package contains the development files of lablgtk.
 
-Package: liblablgtk2-gl-ocaml-dev
-Architecture: any
-Suggests: liblablgtk2-gnome-ocaml-dev
-Depends:
- libgtkgl2.0-dev,
- ${ocaml:Depends},
- ${shlibs:Depends},
- ${misc:Depends}
-Provides: ${ocaml:Provides}
-Recommends: liblablgtk2-ocaml-doc
-Description: OCaml bindings to GtkGL
- lablgtk2 contains bindings for GTK+ 2.x and OCaml.
- .
- This package contains the development files of lablgtk for libraries using
- GtkGL.
-
 Package: liblablgtk2-gnome-ocaml-dev
 Architecture: any
 Depends:
@@ -114,7 +83,6 @@ Architecture: all
 Depends: ${misc:Depends}
 Enhances:
  liblablgtk2-ocaml-dev,
- liblablgtk2-gl-ocaml-dev,
  liblablgtk2-gnome-ocaml-dev,
 Description: OCaml bindings to Gtk+ version 2 (documentation)
  LablGTK2 contains bindings for GTK+ 2.x and OCaml.
diff --git a/debian/liblablgtk2-gl-ocaml-dev.docs b/debian/liblablgtk2-gl-ocaml-dev.docs
deleted file mode 100644
index e845566..000
--- a/debian/liblablgtk2-gl-ocaml-dev.docs
+++ /dev/null
@@ -1 +0,0 @@
-README
diff --git a/debian/liblablgtk2-gl-ocaml-dev.install.in b/debian/liblablgtk2-gl-ocaml-dev.install.in
deleted file mode 100644
index 030aa50..000
--- a/debian/liblablgtk2-gl-ocaml-dev.install.in
+++ /dev/null
@@ -1,4 +0,0 @@
-@OCamlStdlibDir@/lablgtk2/glGtk.*
-@OCamlStdlibDir@/lablgtk2/liblablgtkgl2*
-OPT: @OCamlStdlibDir@/lablgtk2/lablgtkgl.a
-OPT: @OCamlStdlibDir@/lablgtk2/lablgtkgl.cmxa
diff --git a/debian/liblablgtk2-gl-ocaml.docs b/debian/liblablgtk2-gl-ocaml.docs
deleted file mode 100644
index e845566..000
--- a/debian/liblablgtk2-gl-ocaml.docs
+++ /dev/null
@@ -1 +0,0 @@
-README
diff --git a/debian/liblablgtk2-gl-ocaml.install.in b/debian/liblablgtk2-gl-ocaml.install.in
deleted file mode 100644
index 0ae766f..000
--- a/debian/liblablgtk2-gl-ocaml.install.in
+++ /dev/null
@@ -1,4 +0,0 @@
-debian/META.lablgtk2-gl@OCamlStdlibDir@/METAS
-@OCamlStdlibDir@/lablgtk2/dlllablgtkgl2.so @OCamlDllDir@
-@OCamlStdlibDir@/lablgtk2/lablgtkgl.cma
-DYN: @OCamlStdlibDir@/lablgtk2/lablgtkgl.cmxs
diff --git a/debian/liblablgtk2-ocaml-dev.install.in b/debian/liblablgtk2-ocaml-dev.install.in
index e000ad6..8de1759 100644
--- a/debian/liblablgtk2-ocaml-dev.install.in
+++ b/debian/liblablgtk2-ocaml-dev.install.in
@@ -43,7 +43,6 @@ usr/bin/lablgtk2
 @OCamlStdlibDir@/lablgtk2/gtkEdit.*
 @OCamlStdlibDir@/lablgtk2/gtkEnums.*
 @OCamlStdlibDir@/lablgtk2/gtkFile.*
-@OCamlStdlibDir@/lablgtk2/gtkgl_tags.h
 @OCamlStdlibDir@/lablgtk2/gtkInit.*
 @OCamlStdlibDir@/lablgtk2/gtkList.*
 @OCamlStdlibDir@/lablgtk2/gtkMain.*
diff --git a/debian/liblablgtk2-ocaml-doc.ocamldoc.in b/debian/liblablgtk2-ocaml-doc.ocamldoc.in
index 2b9e078..587ddae 100644
--- a/debian/liblablgtk2-ocaml-doc.ocamldoc.in
+++ b/debian/liblablgtk2-ocaml-doc.ocamldoc.in
@@ -1,4 +1,3 @@
 -I src
--I @OCamlStdlibDir@/lablgl
 -I @OCamlStdlibDir@/threads
 --include debian/tmp@OCamlStdlibDir@/lablgtk2
diff --git a/debian/r

Bug#1011166: Chatty can no longer start since the last update

[Evangelos Ribeiro Tzaras]

Hi,

On Sun, 22 May 2022 02:06:31 +0200 (CEST) Julien 
wrote:
> Sorry for my silly question but why does Chatty still fail to start?
My pinephone is my daily driver, can you tell me what still needs to be
fixed? Do I have to use "ln -s" in the meantime?
> 

it should migrate to testing in ~4 days, in the meantime you could grab
it from unstable or add a suitable LD_LIBRARY_PATH, f.e. on amd64

$ LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/purple-2 chatty

Cheers


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

Bug#1011412: r-bioc-scater: autopkgtest regression in testing

[Graham Inggs]

Source: r-bioc-scater
Version: 1.18.3+ds-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime around 2021-09-23, r-bioc-scater's autopkgtests regressed in
testing [1].
I've copied, from a current log of 1.22.0+ds-2 in unstable, what I
hope is the relevant part below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-bioc-scater/testing/amd64/


══ Failed tests 
── Error (test-red-dim.R:224:9): runTSNE works as expected ─

Error in `loadNamespace(x)`: there is no package called ‘snifter’
Backtrace:
 ▆
  1. ├─scater::runTSNE(normed, use_fitsne = TRUE, random_state = 100L)
at test-red-dim.R:224:8
  2. │ ├─scater::calculateTSNE(y, ...)
  3. │ └─scater::calculateTSNE(y, ...)
  4. │   └─scater .local(x, ...)
  5. │ └─scater:::.calculate_tsne(...)
  6. │   └─base::do.call(snifter::fitsne, c(list(x), args,
simplified = TRUE))
  7. └─base::loadNamespace(x)
  8.   └─base::withRestarts(stop(cond), retry_loadNamespace = function() NULL)
  9. └─base withOneRestart(expr, restarts[[1L]])
 10.   └─base doWithOneRestart(return(expr), restart)

[ FAIL 1 | WARN 2 | SKIP 0 | PASS 509 ]
Error: Test failures
Execution halted

Bug#1011411: clamav-freshclam: obsolete StandardOutput= setting in /lib/systemd/system/clamav-freshclam.service

[Peter Marschall]

Package: clamav-freshclam
Version: 0.103.6+dfsg-1+b1
Severity: minor

Dear maintainer,

on startup systemd logs the error/warning:
 /lib/systemd/system/clamav-freshclam.service:11: Standard output type syslog 
is obsolete, automatically updating to journal. Please update your unit file, 
and consider removing the setting altogether.

Although it does not impact clamav-freshclam's function, fixing the cause of 
this log message removes an - admittedly - minor annoyance.

Thanks for maintaining clamav in Debian
Peter


-- Package-specific info:
--- configuration ---
#Automatically Generated by clamav-base postinst
#To reconfigure clamd run #dpkg-reconfigure clamav-base
#Please read /usr/share/doc/clamav-base/README.Debian.gz for details
LocalSocket /var/run/clamav/clamd.ctl
FixStaleSocket true
LocalSocketGroup clamav
LocalSocketMode 666
TemporaryDirectory /tmp
User clamav
AllowSupplementaryGroups true
ScanMail true
ScanArchive true
ArchiveBlockEncrypted false
MaxDirectoryRecursion 15
FollowDirectorySymlinks false
FollowFileSymlinks false
ReadTimeout 180
MaxThreads 12
MaxConnectionQueueLength 15
LogSyslog false
LogRotate true
LogFacility LOG_LOCAL6
LogClean false
LogVerbose false
PidFile /var/run/clamav/clamd.pid
DatabaseDirectory /var/lib/clamav
SelfCheck 3600
Foreground false
Debug false
ScanPE true
MaxEmbeddedPE 10M
ScanOLE2 true
ScanHTML true
MaxHTMLNormalize 10M
MaxHTMLNoTags 2M
MaxScriptNormalize 5M
MaxZipTypeRcg 1M
ScanSWF true
DetectBrokenExecutables false
ExitOnOOM false
LeaveTemporaryFiles false
AlgorithmicDetection true
ScanELF true
IdleTimeout 30
PhishingSignatures true
PhishingScanURLs true
PhishingAlwaysBlockSSLMismatch false
PhishingAlwaysBlockCloak false
DetectPUA false
ScanPartialMessages false
HeuristicScanPrecedence false
StructuredDataDetection false
CommandReadTimeout 5
SendBufTimeout 200
MaxQueue 100
ExtendedDetectionInfo true
OLE2BlockMacros false
ScanOnAccess false
AllowAllMatchScan true
ForceToDisk false
DisableCertCheck false
StreamMaxLength 10M
LogFile /var/log/clamav/clamav.log
LogTime true
LogFileUnlock false
LogFileMaxSize 0
Bytecode true
BytecodeSecurity TrustSigned
BytecodeTimeout 6
OfficialDatabaseOnly false
CrossFilesystems true
# Automatically created by the clamav-freshclam postinst
# Comments will get lost when you reconfigure the clamav-freshclam package

DatabaseOwner clamav
UpdateLogFile /var/log/clamav/freshclam.log
LogVerbose false
LogSyslog false
LogFacility LOG_LOCAL6
LogFileMaxSize 0
LogRotate true
LogTime no
Foreground false
Debug false
MaxAttempts 5
DatabaseDirectory /var/lib/clamav/
DNSDatabaseInfo current.cvd.clamav.net
ConnectTimeout 30
ReceiveTimeout 30
TestDatabases yes
ScriptedUpdates yes
CompressLocalDatabase no
Bytecode true
DatabaseMirror db.local.clamav.net
DatabaseMirror database.clamav.net
DatabaseMirror db.de.clamav.net

--- data dir ---
total 634968
-rw-r--r-- 1 clamav clamav   1438720 Mar 11  2021 bytecode.cld
drwxr-xr-x 2 clamav clamav  4096 Feb 11  2012 
clamav-ee1ff8da21693b6f95b66880ee7d6ea0
-rw-r--r-- 1 clamav clamav 184677888 May 22 08:47 daily.cld
drwxr-xr-x 2 clamav clamav  4096 May 18  2008 daily.inc
-rw-r--r-- 1 clamav clamav69 Jul 24  2021 freshclam.dat
-rw-r--r-- 1 clamav clamav 464053248 Sep 17  2021 main.cld
drwxr-xr-x 2 clamav clamav  4096 Apr 10  2008 main.inc
-rw--- 1 clamav clamav69 Apr 16  2021 mirrors.dat

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

Kernel: Linux 5.17.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 clamav-freshclam depends on:
ii  clamav-base0.103.6+dfsg-1
ii  debconf [debconf-2.0]  1.5.79
ii  dpkg   1.21.7
ii  libc6  2.33-7
ii  libclamav9 0.103.6+dfsg-1+b1
ii  logrotate  3.19.0-2
ii  lsb-base   11.1.0
ii  procps 2:3.3.17-7+b1
ii  ucf3.0043

Versions of packages clamav-freshclam recommends:
ii  ca-certificates  20211016

Versions of packages clamav-freshclam suggests:
ii  apparmor 3.0.4-2
ii  clamav-docs  0.103.6+dfsg-1

-- debconf information excluded

Bug#1010422: Bug#1011265: Britney fails to pin complete set in "Provides" api transitions [Was: Bug#1010422: transition: r-api-bioc-3.15]

[Graham Inggs]

Hi Nilesh

It looks like the only blocker now is waiting for r-bioc-scater [1] to age:

Too young, only 2 of 5 days old

It doesn't get 2-day migration because its autopkgtest regressed in
testing, sometime around 2021-09-23 [2].

I'll file a separate bug for that.

Regards
Graham


[1] https://tracker.debian.org/pkg/r-bioc-scater
[2] https://ci.debian.net/packages/r/r-bioc-scater/testing/amd64/

Bug#988540: im-config: breaks the keyboard configuration

[Osamu Aoki]

Hi,


I have updated https://wiki.debian.org/Keyboard.

(debian-reference was updated in 2020-2021, I think.)

These should give clearer view on XKB/input method situation.

If you find errors, please feel free to correct them.

Regards,

Osamu