Bug#1019409: Bug#993161: pam: some remaining changes for DPKG_ROOT

[Steve Langasek]

On Thu, Sep 08, 2022 at 09:51:41PM +0200, Helmut Grohne wrote:
> Hi technical comittee members,

> On Thu, Aug 18, 2022 at 03:44:54PM +0200, Helmut Grohne wrote:
> > Within three weeks I want Steve to reply to this bug in a way that
> > addresses Sam's needs or Sam to agree with moving forward without
> > Steve's review. Failing that, I will ask the CTTE to override the pam
> > maintainers on this patch.

> I hope that it does not surprise you. I am formally asking the CTTE to
> override the pam maintainers and requiring pam to support DPKG_ROOT.

My feedback to you on IRC was that I think it's inappropriate for you to go
package-by-package in the BTS to the packages in the base set expecting
support for a feature that has to my knowledge never been surfaced for
project-wide discussion on debian-devel or similar.

So if you want to take that discussion to the Technical Committee to ratify
as something that base packages must support, well, I don't think that's the
best use of the TC vs just starting a thread on debian-devel, but it does
satisfy my expectation that there be a project-level review of the design
prior to obligating base package maintainers to support this feature.

> (e.g. quality assurance, limitation of scope, public discussion at DC22,
> etc.)

I did not attend DC22 and this is literally the first time I've heard that
there was going to be a session about this.  I'm glad that this is getting
wider socialization within the project, but without knowing who was present
for the discussion, how widely the session was disseminated ahead of time,
and what kind of feedback was given, I don't think this rises to the level
of a project-reviewed agreement.

Looking at the list of videos from DebConf 22

  

I find the session entitled "What is DPKG_ROOT?"

  


which is good, but also appears to be a rather small self-selecting
audience.

>  * pam should support DPKG_ROOT and accept reasonable changes to that
>end.
>  * In particular, the patch in bug #993161 is considered a reasonable
>change with bearable maintenance cost and thus should be included
>in pam.

> Since I am requesting a maintainer override, a super majority is
> required.

For the record I do not consider this an override requiring a
supermajority and would abide by a majority TC decision.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1019423: libreoffice-impress: starting by double click from dolphin results in 1 pixel wide window

[Dietmar]

Package: libreoffice-impress
Version: 1:7.4.1~rc1-3+b1
Severity: important

Dear Maintainer,

opening a file (text or spreadsheet) by double click results in a 1 pixel wide
program window. Hovering, the mouse action to resize is accessible and I can
resize the window. But I have to detect the small line, what the window seems
to be.
Starting Libreoffice from menu, I get a normal sized window.

Dietmar


-- Package-specific info:

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

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

Versions of packages libreoffice-impress depends on:
ii  libbox2d22.4.1-3
ii  libc62.34-7
ii  libepoxy01.5.10-1
ii  libetonyek-0.1-1 0.1.10-3
ii  libgcc-s112.2.0-1
ii  libmwaw-0.3-30.3.21-1
ii  libodfgen-0.1-1  0.1.8-2
ii  libreoffice-common   1:7.4.1~rc1-3
ii  libreoffice-core 1:7.4.1~rc1-3+b1
ii  libreoffice-draw 1:7.4.1~rc1-3+b1
ii  librevenge-0.0-0 0.0.4-6+b1
ii  libstaroffice-0.0-0  0.0.7-1
ii  libstdc++6   12.2.0-1
ii  libuno-cppu3 1:7.4.1~rc1-3+b1
ii  libuno-cppuhelpergcc3-3  1:7.4.1~rc1-3+b1
ii  libuno-sal3  1:7.4.1~rc1-3+b1
ii  libuno-salhelpergcc3-3   1:7.4.1~rc1-3+b1
ii  ucf  3.0043
ii  uno-libs-private 1:7.4.1~rc1-3+b1

libreoffice-impress recommends no packages.

Versions of packages libreoffice-impress suggests:
ii  bluez  5.65-1

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.13.1-4.4
ii  fonts-opensymbol2:102.12+LibO7.4.1~rc1-3
ii  libabsl20220623 0~20220623.0-2
ii  libboost-locale1.74.0   1.74.0-17
ii  libc6   2.34-7
ii  libcairo2   1.16.0-6
ii  libclucene-contribs1v5  2.3.3.4+dfsg-1.1
ii  libclucene-core1v5  2.3.3.4+dfsg-1.1
ii  libcups22.4.2-1+b1
ii  libcurl3-gnutls 7.85.0-1
ii  libdbus-1-3 1.14.0-2
ii  libdconf1   0.40.0-3
ii  libeot0 0.01-5+b1
ii  libepoxy0   1.5.10-1
ii  libexpat1   2.4.8-1
ii  libexttextcat-2.0-0 3.4.5-1
ii  libfontconfig1  2.13.1-4.4
ii  libfreetype62.12.1+dfsg-3
ii  libgcc-s1   12.2.0-1
ii  libglib2.0-02.73.3-3
ii  libgpgmepp6 1.17.1-4
ii  libgraphite2-3  1.3.14-1
ii  libgstreamer-plugins-base1.0-0  1.20.3-2
ii  libgstreamer1.0-0   1.20.3-1
ii  libharfbuzz-icu02.7.4-1+b1
ii  libharfbuzz0b   2.7.4-1+b1
ii  libhunspell-1.7-0   1.7.1-1
ii  libhyphen0  2.8.8-7
ii  libice6 2:1.0.10-1
ii  libicu7171.1-3
ii  libjpeg62-turbo 1:2.1.2-1
ii  liblcms2-2  2.13.1-1
ii  libldap-2.5-0   2.5.12+dfsg-2+b1
ii  libmythes-1.2-0 2:1.2.5-1
ii  libnspr42:4.34.1-1
ii  libnss3 2:3.82-1
ii  libnumbertext-1.0-0 1.0.10-1
ii  libopenjp2-72.5.0-1
ii  liborcus-0.17-0 0.17.2-2+b1
ii  liborcus-parser-0.17-0  0.17.2-2+b1
ii  libpng16-16 1.6.37-5
ii  libpoppler123   22.08.0-2.1
ii  libraptor2-02.0.15-2
ii  librdf0 1.0.17-1.2
ii  libreoffice-common  1:7.4.1~rc1-3
ii  librevenge-0.0-00.0.4-6+b1
ii  libsm6  2:1.2.3-1
ii  libstdc++6  12.2.0-1
ii  libtiff54.4.0-4
ii  libuno-cppu31:7.4.1~rc1-3+b1
ii  libuno-cppuhelpergcc3-3 1:7.4.1~rc1-3+b1
ii  libuno-sal3 1:7.4.1~rc1-3+b1
ii  libuno-salhelpergcc3-3  1:7.4.1~rc1-3+b1
ii  libwebp71.2.2-2+b1
ii  libx11-62:1.8.1-2
ii  libx11-xcb1 2:1.8.1-2
ii  libxext62:1.3.4-1
ii  libxinerama12:1.1.4-3
ii  libxml2 2.9.14+dfsg-1+b1
ii  libxmlsec1  1.2.34-2
ii  libxmlsec1-nss  1.2.34-2
ii  libxrandr2  2:1.5.2-2+b1
ii  libxrender1 1:0.9.10-1.1
ii  libxslt1.1  1.1.35-1
ii  libzxingcore1   1.2.0-1
ii  uno-libs-private1:7.4.1~rc1-3+b1
ii  ure 

Bug#1019422: wwsympa: The same logs are output twice at a time

[IKEDA Soji]

Package: sympa
Version: 6.2.68~dfsg
Severity: important

Among the syslog output by the processes of Sympa, every log about
wwsympa process is output twice at a time.

I guess this is because /etc/rsyslog.d/sympa contains lines:

:programname, contains, "sympa" /var/log/sympa.log
:programname, contains, "wwsympa"   /var/log/sympa.log

where 'contains, "sympa"' line can match against "sympa" or "sympa/xxx"
(sympa CLI), "sympa_msg", "sympa_automatic" and "wwsympa".

Bug#1005765: dgit doesn't handle upstream files with CRLF well

[Stéphane Glondu]

Hello,

Le 03/09/2022 à 18:43, Ian Jackson a écrit :

I wrote:

I think that if
  - your upstream files have CRLF in the orig
  - your upstream files have CRLF in your git tree
  - you do not expect (or enable) line ending conversions in git
then
  - dgit will not complain
  - the source package you produce will have files with CRLF
  - everything should work


If you have a repro that demonstrates the contrary, please let us
know.  Typically a repro would consist of the following elements:

   * The precise git commit that you had as HEAD in your working tree

 We need the git hash; hopefully I can obtain the data from salsa.

   * The precise contents of all relevant .origs

 If they were already previously uploaded, we can get them from the
 archive or snapshot.d.o.  Otherwise please supply their
 sha256sums, as well as instructions for download or creation (eg
 pristine-tar branch).

   * The precise dgit command line, and any configuration settings
 applied to any of the relevant tools.


I had trouble uploading opam/2.1.2-1 with dgit. Eventually, I gave up 
and did a regular upload.


The commit id is 225dd4102cfd4391fab166d7cc220d020efedafd on:

  https://salsa.debian.org/ocaml-team/opam


Ideally, a run with dgit -D would be helpful.


I will try when I update the package.


If you have a situation that doesn't match the criteria above, but you
think should be able to work, and currently doesn't, please also let
us know.


I'm not sure whether my situation matches the criteria above, but I 
guess dgit should be able to do any upload to the official Debian 
archive, shouldn't it?



Thanks for all your work on dgit!


Cheers,

--
Stéphane

Bug#1019421: Improper permission for sympa.log after logrotate-ing

[IKEDA Soji]

Package: sympa
Version: 6.2.68~dfsg
Severity: important

After run of logrotate, permission of /var/log/sympa.log is set as:

-rw-r- sympa sympa

and therefore logging is no longer possible.

I suppose this is because /etc/logrotate.d/sympa contains

create 640 sympa sympa

which should be

create 640 syslog sympa

Bug#1016543: rsync CVE-2022-29154 not being applies on -security

[Matt Corallo]

Hi!

I was pointed to rsync CVE-2022-29154 and noted that both Debian and Ubuntu didn't apply the fix on 
the security repos. From what I can tell they've been treated as mild, seemingly in part due to an 
assumption that clients rarely fetch data from untrusted servers?


At least in the context of packages like rpki-client, a security vulnerability allowing a malicious 
server to overwrite arbitrary files on the client's filesystem would allow said server to remove any 
internet network from the global routing table of most large ISPs, allowing them to effectively nuke 
any network on the internet for some time.


I hope I'm misinformed and I'm simply misreading the description provided.

Thanks,
Matt

Bug#1016936: dwz: fails while building assaultcube

[Ben Westover]

Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27375

OK, so it turns out this error is due to Clang's adoption of DWARFv5 [1]
which dwz doesn't fully support yet [2]. Until that is fixed, the issue
can be worked around by using DWARFv4 by adding `-gdwarf-4` to flags.

--
Ben Westover

[1] https://www.phoronix.com/news/LLVM-Clang-DWARFv5-Default
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=24726


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019420: xfce4-pulseaudio-plugin volume icon flickers

[as]

Package: xfce4-pulseaudio-plugin
Version: 0.4.4-1
Severity: normal
X-Debbugs-Cc: none

After upgrading to 0.4.4-1, adjusting the volume seems to make the
panel icon flicker. Other actions like seeking on a video in VLC or
Parole, or using a video conferencing in a web browser also cause
this.

I tried compiling the latest version. It still happens there but not
as reliably.

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

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

Versions of packages xfce4-pulseaudio-plugin depends on:
ii  libc62.34-7
ii  libexo-2-0   4.16.4-1
ii  libglib2.0-0 2.73.3-3
ii  libgtk-3-0   3.24.34-3
ii  libkeybinder-3.0-0   0.3.2-1.1
ii  libnotify4   0.8.1-1
ii  libpulse-mainloop-glib0  15.0+dfsg1-4+b1
ii  libpulse015.0+dfsg1-4+b1
ii  libwnck-3-0  40.1-1
ii  libxfce4panel-2.0-4  4.16.5-1
ii  libxfce4ui-2-0   4.16.1-1
ii  libxfce4util74.16.0-1
ii  libxfconf-0-34.16.0-2

Versions of packages xfce4-pulseaudio-plugin recommends:
ii  pavucontrol  5.0-2
ii  pulseaudio   15.0+dfsg1-4+b1

xfce4-pulseaudio-plugin suggests no packages.

Bug#1019387: ITP: atomes -- an atomistic tool box

[Paul Wise]

On Thu, 2022-09-08 at 13:24 +0200, Sébastien Le Roux wrote:

> If the proper way to do that is inside a packaging team then I think
> the "Debian Scientific Computing Team" is likely to be the most
> appropriate place to start.

I feel like the Debian chemistry team might be a better option:

https://wiki.debian.org/Debichem
https://blends.debian.org/debichem/tasks/

Potentially also the Debian science team, but I'm not sure, so perhaps
you should send a mail to both teams asking them about this.

https://wiki.debian.org/DebianScience
https://wiki.debian.org/DebianScience/Chemistry

Probably the chemistry/science team wiki/etc infra needs some cleanup.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1019418: apache2: Content-Location header doesn't escape colons

[Peter Chubb]

Package: apache2
Version: 2.4.54-1~deb11u1
Severity: normal

Dear Maintainer,

We have an apache2 server that serves URLs of the form:
   https://server.com/a/b/foo:phd.html

The Content-Location HTTP response header returned is then
   Content-Location: foo:phd.html

which is invalid because of the colon.  It should return
   Content-Location: ./foo:phd.html
so that the : is not treated as a protocol delimiter.



-- Package-specific info:

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

Kernel: Linux 5.10.0-13-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apache2 depends on:
ii  apache2-bin  2.4.54-1~deb11u1
ii  apache2-data 2.4.54-1~deb11u1
ii  apache2-utils2.4.54-1~deb11u1
ii  dpkg 1.20.11
ii  init-system-helpers  1.60
ii  lsb-base 11.1.0
ii  mime-support 3.66
ii  perl 5.32.1-4+deb11u2
ii  procps   2:3.3.17-5

Versions of packages apache2 recommends:
ii  ssl-cert  1.1.0+nmu1

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  www-browser  

Versions of packages apache2-bin depends on:
ii  libapr1  1.7.0-6+deb11u1
ii  libaprutil1  1.6.1-5
ii  libaprutil1-dbd-sqlite3  1.6.1-5
ii  libaprutil1-ldap 1.6.1-5
ii  libbrotli1   1.0.9-2+b2
ii  libc62.31-13+deb11u3
ii  libcrypt11:4.4.18-4
ii  libcurl4 7.74.0-1.3+deb11u1
ii  libjansson4  2.13.1-1.1
ii  libldap-2.4-22.4.57+dfsg-3+deb11u1
ii  liblua5.3-0  5.3.3-1.1+b1
ii  libnghttp2-141.43.0-1
ii  libpcre3 2:8.39-13
ii  libssl1.11.1.1n-0+deb11u3
ii  libxml2  2.9.10+dfsg-6.7+deb11u2
ii  perl 5.32.1-4+deb11u2
ii  zlib1g   1:1.2.11.dfsg-2+deb11u1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  www-browser  

Versions of packages apache2 is related to:
ii  apache2  2.4.54-1~deb11u1
ii  apache2-bin  2.4.54-1~deb11u1

-- no debconf information

Bug#1019417: out of memory: oom-killer Killed process wpa_supplicant

[John Yu]

Package: wpasupplicant
Version: 2:2.9.0-21
Severity: important
Tags: a11y
X-Debbugs-Cc: jdoe35...@gmail.com


wpa_supplicant periodically requests more memory than what's available (~12GB)
and ends up getting killed by kernel out-of-memory killer. wpa_supplicant then
is restarted and connects to WiFi. Internet connection drops briefly.

uname -a
===
Linux elitebook 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1 (2022-08-13) x86_64
GNU/Linux

lshw -C network
===
  *-network
   description: Wireless interface
   product: Wireless 8260
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:02:00.0
   logical name: wlp2s0
   version: 3a
   serial: b8:08:cf:b2:e6:cf
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical
wireless
   configuration: broadcast=yes driver=iwlwifi
driverversion=5.10.0-17-amd64 firmware=36.ad812ee0.0 8000C-36.ucode
ip=10.152.10.29 latency=0 link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:135 memory:e110-e1101fff


dmesg transcript on one of the occasions
===
28616.513770] oom-
kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/wpa_supplicant.service,task=wpa_supplicant,pid=24977,uid=0
[28616.513786] Out of memory: Killed process 24977 (wpa_supplicant) total-
vm:13184756kB, anon-rss:13170908kB, file-rss:20kB, shmem-rss:0kB, UID:0
pgtables:25856kB oom_score_adj:0
[28617.465698] wlp2s0: deauthenticating from 6c:f3:7f:ba:2a:92 by local choice
(Reason: 3=DEAUTH_LEAVING)
[28621.551249] wlp2s0: authenticate with 6c:f3:7f:ba:2a:92
[28621.558949] wlp2s0: send auth to 6c:f3:7f:ba:2a:92 (try 1/3)
[28621.579323] wlp2s0: authenticated
[28621.605563] wlp2s0: associate with 6c:f3:7f:ba:2a:92 (try 1/3)
[28621.620294] wlp2s0: RX AssocResp from 6c:f3:7f:ba:2a:92 (capab=0x1401
status=0 aid=1)
[28621.622662] wlp2s0: associated
[28621.623845] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[28621.661000] wlp2s0: Limiting TX power to 36 (36 - 0) dBm as advertised by
6c:f3:7f:ba:2a:92
[28680.941402] G1 Service invoked oom-killer:
gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
[28680.941406] CPU: 0 PID: 21329 Comm: G1 Service Not tainted 5.10.0-17-amd64
#1 Debian 5.10.136-1
[28680.941407] Hardware name: HP HP EliteBook 850 G3/8079, BIOS N75 Ver. 01.52
04/20/2021
[28680.941409] Call Trace:
[28680.941416]  dump_stack+0x6b/0x83
[28680.941419]  dump_header+0x4a/0x1f4
[28680.941422]  oom_kill_process.cold+0xb/0x10
[28680.941426]  out_of_memory+0x1bd/0x4e0
[28680.941430]  __alloc_pages_slowpath.constprop.0+0xb90/0xc60
[28680.941434]  __alloc_pages_nodemask+0x2de/0x310
[28680.941438]  pagecache_get_page+0x175/0x390
[28680.941440]  filemap_fault+0x6a2/0x900
[28680.941444]  ? xas_load+0x5/0x80
[28680.941467]  ext4_filemap_fault+0x2d/0x50 [ext4]
[28680.941471]  __do_fault+0x34/0x170
[28680.941474]  handle_mm_fault+0x1208/0x1c10
[28680.941479]  do_user_addr_fault+0x1b8/0x400
[28680.941483]  exc_page_fault+0x78/0x160
[28680.941486]  ? asm_exc_page_fault+0x8/0x30
[28680.941487]  asm_exc_page_fault+0x1e/0x30
[28680.941490] RIP: 0033:0x7f9f21757510
[28680.941496] Code: Unable to access opcode bytes at RIP 0x7f9f217574e6.
[28680.941497] RSP: 002b:7f9f05198dc8 EFLAGS: 00010206
[28680.941500] RAX:  RBX: 7f9f1c150468 RCX:
7f9f22935797
[28680.941501] RDX:  RSI: 7f9f05198d50 RDI:
7f9f227b0fa8
[28680.941502] RBP: 7f9f05198de0 R08:  R09:
7f9f1c150fa0
[28680.941503] R10: 7ffcac5c4080 R11: 0206 R12:
7f9f1c150468
[28680.941505] R13: 7f9f1c150468 R14: 0010 R15:
00103000
[28680.941508] Mem-Info:
[28680.941513] active_anon:1823 inactive_anon:3907125 isolated_anon:0
active_file:170 inactive_file:241 isolated_file:0
unevictable:43417 dirty:0 writeback:0
slab_reclaimable:10971 slab_unreclaimable:20582
mapped:11617 shmem:59464 pagetables:13209 bounce:0
free:33044 free_pcp:647 free_cma:0
[28680.941517] Node 0 active_anon:7292kB inactive_anon:15628500kB
active_file:680kB inactive_file:964kB unevictable:173668kB isolated(anon):0kB
isolated(file):0kB mapped:46468kB dirty:0kB writeback:0kB shmem:237856kB
shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 966656kB writeback_tmp:0kB
kernel_stack:13216kB all_unreclaimable? no
[28680.941518] Node 0 DMA free:15892kB min:64kB low:80kB high:96kB
reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB
inactive_file:0kB unevictable:0kB writepending:0kB present:15988kB
managed:15892kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB
local_pcp:0kB free_cma:0kB
[28680.941523] lowmem_reserve[]: 0 3086 15851 15851 15851
[28680.941528] Node 0 DMA32 free:63524kB min:13144kB low:16428kB high:19712kB
reserved_highatomic:0KB active_anon:0kB inactive_anon:3100404kB

Bug#1019401: QSGRenderThread[569483]: segfault after suspend/resume

[piorunz]

On 09/09/2022 00:24, Lisandro Damián Nicanor Pérez Meyer wrote:


To be honest that could be a gazillion things. This is clearly related
to rendering, thus it can easily be an issue on the graphics driver...
I am also figuring that it's complicated to replicate, right? Or you
can easily replicate it every time you suspend/resume your machine?

Regards, Lisandro.


Yes I think this is related to GPU driver (AMD Radeon card).
Because its glitching sometimes and sometimes I have to kill X session.

I will be happy to provide more logs and maybe move this bug to other
relevant package, but how to catch and identify this bug in more detail?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1019369: cgit: FTBFS on riscv64: t0109-git-config test failed on riscv64

[Paul Wise]

On Thu, 2022-09-08 at 22:56 +0800, Sakura286 wrote:

> Thanks for your advice. Since "access" is invalid on riscv64, just like 
> "strace -e access", "strace -e access,faccessat" will also fail. You 
> cannot pass an invalid syscall name to "strace -e".

Ah, that is unfortunate. I note that strace has syscall groupings but
none of them are for access. It also has regexes, please try these:

strace -e /access
strace -e '/^(access|faccessat)$' echo

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1019416: transition: wxwidgets3.2

[Scott Talbert]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

It would be good if we could eliminate wxwidgets3.0 from the archive for
bullseye - the last upstream release (3.0.5.1) was over 2 years ago, and
there's very little upstream interest in bugs in it now.

Manually tracking packages is somewhat error prone, and in particular 
misses people adding new dependencies on wx3.0, so I'd like to make use 
of the transition tracker to automatically track which packages still 
need attention.

This transition probably doesn't need allocating a "slot" to happen at
this point, since packages can mostly be updated to use wxwidgets3.2
independently of one another.

Ben file:

title = "wxwidgets3.2";
is_affected = .build-depends ~ 
/libwx(gtk(-media|-webview)?)3\.2-dev|wx3\.2-(headers|i18n)/ | .build-depends ~ 
/libwx(base|gtk(-media|-webview)?)3\.0(-gtk3)?-dev|wx3\.0-(headers|i18n)/;
is_good = .build-depends ~ 
/libwx(gtk(-media|-webview)?)3\.2-dev|wx3\.2-(headers|i18n)/;
is_bad = .build-depends ~ 
/libwx(base|gtk(-media|-webview)?)3\.0(-gtk3)?-dev|wx3\.0-(headers|i18n)/;

Thanks,
Scott

Bug#1019415: qt.qpa.xcb: xcb_shm_create_segment() can't be called for size 17178820624

[Celelibi]

Package: libqt5gui5
Version: 5.15.4+dfsg-5
Severity: important

Dear Maintainer,

When running some Qt-based applications, I get the following error,
followed by a segmentation fault. Which, I believe is due to a bug in
Qt.


qt.qpa.xcb: xcb_shm_create_segment() can't be called for size 17178820624, 
maximumallowed size is 4294967295


This only happen on applications that (try to) show a splash screen,
like fritzing and shortcut. And only happen on my machine that has a 4K
monitor.

Here's what I understand of what happen:

The application tries to show a window for the splash screen. The method
QXcbWindow::create() calls QXcbWindow::propagateSizeHints() which end up
calling xcb_icccm_size_hints_set_base_size with a size of (-2, -2).
We get these values because the window baseSize isn't initialized yet
and HiDPI-scaled.
These hints are then sent to the X server.

Those values are then sent back to the application as some
ConfigureNotify event (I believe) as a pair of uint16_t. This prompts Qt
to try to reallocate an unreasonably large buffer to accomodate the
"resized" window.

Here are the few lines of logs obtained with
QT_LOGGING_RULES='qt.qpa.*=true' right before the warning message that
lead to a crash.

qt.qpa.events: Event | XCB_PROPERTY_NOTIFY(28) | sequence: 402
qt.qpa.events: Event | XCB_PROPERTY_NOTIFY(28) | sequence: 402
qt.qpa.events: Event | XCB_CONFIGURE_NOTIFY(22) | sequence: 402
qt.qpa.xcb: [ QWidgetWindow(0x55751b9cc380, name="FSplashScreenClassWindow") ] 
creating shared memory 17178820624 bytes for QSize(65534, 65534) depth 24 bits 
32
qt.qpa.xcb: xcb_shm_create_segment() can't be called for size 17178820624, 
maximumallowed size is 4294967295


I don't know exactly why this only happen on some very specific
combinations of hardwares and softwares, but google tells me this bug
affects several applications and are always related to 4K monitors.
Could be also related to the window manager. I use fluxbox.

I'm not sure why the window baseSize is uninitialized, but in any case,
setting a negative base_size hint in QXcbWindow::propagateSizeHints()
sounds definitely like a bad idea. Maybe the values should be checked
before they are passed to xcb_icccm_size_hints_set_base_size, as is the
case with other hint values in the same method.

Unfortunately, I'm not well-versed enough in Qt to make an example
program. However, just to check that this is the cause of the bug, I
made a workaround using LD_PRELOAD to replace those negative hint values
with zeros. I attach the source code.

Compile with:
gcc -o preload.so -shared -fPIC preload.c -ldl -Wl,--no-as-needed -lxcb-icccm

Run with:
LD_PRELOAD=./preload.so fritzing


Best regards,
Celelibi


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), 
(500, 'stable')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
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 libqt5gui5 depends on:
ii  fontconfig2.13.1-4.4
ii  libc6 2.34-7
ii  libdrm2   2.4.112-3
ii  libegl1   1.5.0-1
ii  libfontconfig12.13.1-4.4
ii  libfreetype6  2.12.1+dfsg-3
ii  libgbm1   22.2.0~rc3-1
ii  libgcc-s1 12.2.0-1
ii  libgl11.5.0-1
ii  libglib2.0-0  2.73.3-3
ii  libharfbuzz0b 2.7.4-1+b1
ii  libice6   2:1.0.10-1
ii  libinput101.21.0-1
ii  libjpeg62-turbo   1:2.1.2-1
ii  libmd4c0  0.4.8-1
ii  libmtdev1 1.1.6-1
ii  libpng16-16   1.6.37-5
ii  libqt5core5a [qtbase-abi-5-15-4]  5.15.4+dfsg-5
ii  libqt5dbus5   5.15.4+dfsg-5
ii  libqt5network55.15.4+dfsg-5
ii  libsm62:1.2.3-1
ii  libstdc++612.2.0-1
ii  libudev1  251.4-3
ii  libx11-6  2:1.8.1-2
ii  libx11-xcb1   2:1.8.1-2
ii  libxcb-glx0   1.15-1
ii  libxcb-icccm4 0.4.1-1.1
ii  libxcb-image0 0.4.0-2
ii  libxcb-keysyms1   0.4.0-1+b2
ii  libxcb-randr0 1.15-1
ii  libxcb-render-util0   0.3.9-1+b1
ii  libxcb-render01.15-1
ii  libxcb-shape0 1.15-1
ii  libxcb-shm0   1.15-1
ii  libxcb-sync1  1.15-1
ii  libxcb-xfixes0

Bug#1019401: QSGRenderThread[569483]: segfault after suspend/resume

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 moreinfo unreproducible

Hi!

On Thu, 8 Sept 2022 at 14:18, piorunz  wrote:
>
> Package: libqt5core5a
> Version: 5.15.4+dfsg-5
> Severity: normal
> X-Debbugs-Cc: pior...@gmx.com
>
> Dear Maintainer,
>
> I Did suspend/resume cycle of my computer.
> Later I found in dmesg:
>
> [96111.865203] QSGRenderThread[569483]: segfault at 0 ip 7fe450b2bcfb sp
> 7fe411703950 error 4 in libQt5Core.so.5.15.4[7fe450ae9000+301000]
> [96111.865213] Code: 38 64 48 8b 04 25 28 00 00 00 48 89 44 24 28 31 c0 e8 c9
> a4 ff ff 48 85 c0 0f 84 4a 11 fc ff 48 89 c3 4c 8d 68 50 48 8b 40 50 <49> 63 
> 2c
> 24 3b 68 04 7d 6c 8b 10 83 fa 01 76 25 8b 70 08 81 e6 ff

To be honest that could be a gazillion things. This is clearly related
to rendering, thus it can easily be an issue on the graphics driver...
I am also figuring that it's complicated to replicate, right? Or you
can easily replicate it every time you suspend/resume your machine?

Regards, Lisandro.

Bug#1019414: prometheus-xmpp-alerts: Datetime format is not the same as what prometheus-alertmanager uses

[Craig Small]

Package: prometheus-xmpp-alerts
Version: 0.4.2-1
Severity: important

prometheus-xmpp-alerts is expecting its datetime to be in UTC, but that
is not what the prometheus alertmanager uses.

This means basically prometheus-xmpp-alerts does not work with
prometheus-alermanager which is its main use-case.

I suspect that one or both of the programming teams assumes the servers
run UTC which is a pretty bad assuption, not sure if it is xmpp-alerts
fault for hard-coding the timezone or alermanagers fault for not setting
it. In reality its both.

In my opinion, the xmpp-alerts should accept both a UTC timezone and a
different timezone.

The file in question is 
/usr/lib/python3/dist-packages/prometheus_xmpp/__init__.py
with the function parse_timestring

ts = re.sub('\\.([0-9]{6})([0-9]{0,3})Z$', r'.\1Z', ts)
return datetime.strptime(ts, '%Y-%m-%dT%H:%M:%S.%fZ')

The error message is:
Sep 08 21:26:39 constantine prometheus-xmpp-alerts[2111702]: ValueError: time 
data '2022-09-08T21:26:09.706263468+10:00' does not match format 
'%Y-%m-%dT%H:%M:%S.%fZ'

which is true, "+10:00" doesn't match "Z", but it does match "%z". Also
%z understands "Z" too. Oddly enough it doesn't understand any other
sort of timezone, e.g. K is UTC+10h but that's strptime for you.

You'll also notice that the nanoseconds have not been stripped, again
because of the assumption of the timezone for the regex.

So the answer is, do timezones properly.
1) Make the regex understand both sorts of timezones
2) Use %z because that's what its for.

The regex is we either get "Z" or +/-hh:mm so the solution on a single
line is:

>>> datetime.strptime(re.sub('\\.([0-9]{6})([0-9]{0,3})(Z|[-+][0-9]{1,2}:[0-9]{2})$',
>>>  r'.\1\3',"2022-09-08T21:26:09.706263468+10:00"), '%Y-%m-%dT%H:%M:%S.%f%z')
datetime.datetime(2022, 9, 8, 21, 26, 9, 706263, 
tzinfo=datetime.timezone(datetime.timedelta(seconds=36000)))
>>> datetime.strptime(re.sub('\\.([0-9]{6})([0-9]{0,3})(Z|[-+][0-9]{1,2}:[0-9]{2})$',
>>>  r'.\1\3',"2022-09-08T21:26:09.706263468Z"), '%Y-%m-%dT%H:%M:%S.%f%z')
datetime.datetime(2022, 9, 8, 21, 26, 9, 706263, tzinfo=datetime.timezone.utc)
>>> datetime.strptime(re.sub('\\.([0-9]{6})([0-9]{0,3})(Z|[-+][0-9]{1,2}:[0-9]{2})$',
>>>  r'.\1\3',"2022-09-08T21:26:09.706263468-10:00"), '%Y-%m-%dT%H:%M:%S.%f%z')
datetime.datetime(2022, 9, 8, 21, 26, 9, 706263, 
tzinfo=datetime.timezone(datetime.timedelta(days=-1, seconds=50400)))

I can provide a patch if required.

 - Craig

-- System Information:
Debian Release: 11.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages prometheus-xmpp-alerts depends on:
ii  python33.9.2-3
ii  python3-aiohttp3.7.4-1
ii  python3-prometheus-client  0.9.0-1
ii  python3-slixmpp1.7.0-2
ii  python3-yaml   5.3.1-5

prometheus-xmpp-alerts recommends no packages.

Versions of packages prometheus-xmpp-alerts suggests:
ii  prometheus-alertmanager  0.21.0+ds-4+b5

-- Configuration Files:
/etc/prometheus/xmpp-alerts.yml changed [not included]

-- no debconf information

Bug#1019411: RFS: ani-cli/3.4.0-1 -- A cli to browse and watch anime (alone AND with friends).

[Mathias Gibbens]

Hi,

  You should have seen pretty clearly when uploading your package to
mentors.debian.net that another individual was already working on it.
Have you coordinated your work with him? If so, why have you opened a
duplicate RFS for this package, when one already exists (#1013293)? If
not, that's a pretty rude and inconsiderate action to take.

  Either way, the package you uploaded needs a bunch of work before
anyone will consider sponsoring it:

  * d/changelog appears to be specific to the project's github issues,
and is therefore incorrect to use for Debian packaging

  * d/watch is empty

  * The orig.tar.gz seems to include an entire copy of the git repo

  * lintian reports several issues

  I don't know if this bug should be closed or merged with #1013293,
but it's not actionable as-is.

Mathias


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

Bug#1007962: sslsplit NMU: Bug #1007962: sslsplit FTBFS when only loopback interface is configured

[Hilko Bengen]

* Timo Lindfors:

> I hope it is ok to NMU this to get sslsplit back to Debian. If not,
> please let me know! I'll wait wait for 10 days in case there are
> comments from you, others in Debian or upstream. I also hope it is ok
> to push these patches to salsa after the package has been uploaded.

Please upload and push the changes. No need for delays.

Cheers,
-Hilko

Bug#998037: gargoyle-free: Mention config file path in man

[Alexandre Detiste]

Hi,

The exemple config file is already copied to /etc/garglk.ini .

Please provide a Salsa Merge Request with the wording
of your choice ... (I can't figure how to write this... :-| )

Greetings

Bug#1019413: debcrossgen: host_arch.cpu_family() reports powerpc64le on ppc64el but should report ppc64

[Helmut Grohne]

Package: meson
Version: 0.63.2-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:dpdk

host_arch.cpu_family() should be reporting ppc64 on ppc64el according to
https://mesonbuild.com/Reference-tables.html, but it actually reports
powerpc64le when debcrossgen is in use. The relevant mapping should be
fixed in debcrossgen. I'm attaching a patch for your convenience.

Helmut
diff --minimal -Nru meson-0.63.2/debian/changelog meson-0.63.2/debian/changelog
--- meson-0.63.2/debian/changelog   2022-09-03 18:33:44.0 +0200
+++ meson-0.63.2/debian/changelog   2022-09-08 22:26:00.0 +0200
@@ -1,3 +1,10 @@
+meson (0.63.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * debcrossgen: fix host_arch.cpu_family() on ppc64el. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 08 Sep 2022 22:26:00 +0200
+
 meson (0.63.2-1) unstable; urgency=medium
 
   * New upstream release. Closes: #1017087.
diff --minimal -Nru meson-0.63.2/debian/debcrossgen 
meson-0.63.2/debian/debcrossgen
--- meson-0.63.2/debian/debcrossgen 2021-02-14 13:58:40.0 +0100
+++ meson-0.63.2/debian/debcrossgen 2022-09-08 22:25:57.0 +0200
@@ -73,7 +73,8 @@
 cpu_family_map = dict(mips64el="mips64",
   i686='x86')
 cpu_map = dict(armhf="arm7hlf",
-   mips64el="mips64",)
+   mips64el="mips64",
+   powerpc64le="ppc64",)
 
 def run(options):
 if options.arch is None:

Bug#1019411: RFS: ani-cli/3.4.0-1 -- A cli to browse and watch anime (alone AND with friends).

[Nils Wiemer]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "ani-cli":

* Package name : ani-cli
Version : 3.4.0-1
Upstream Author : https://github.com/pystardust/ani-cli
* URL : https://github.com/pystardust/ani-cli
* License : GPL-3.0+
* Vcs : [fill in URL of packaging vcs]
Section : video

The source builds the following binary packages:

ani-cli - A cli to browse and watch anime (alone AND with friends).

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


https://mentors.debian.net/package/ani-cli/

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

dget -x 
https://mentors.debian.net/debian/pool/main/a/ani-cli/ani-cli_3.4.0-1.dsc


Changes for the initial release:

ani-cli (3.4.0-1) unstable; urgency=medium
.
* Closes: #888
* Closes: #883
* gogo proxy change

Regards,

--

  Nils Wiemer

Bug#1019412: initramfs-tools: Please support compressed firmware (new in Linux 5.19)

[наб]

Source: initramfs-tools
Version: 0.142
Severity: wishlist
Tags: patch

Dear Maintainer,

Resubmitting MR 61
  https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/61
to debbugs after 4 months.

The patches, in order, do the following:
  1. /sys/module/firmware_class/parameters/path, if any, is added before
 anything else in the module loading path:
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/base/firmware_loader/main.c?h=v5.17#n406
  2. When configured with FW_LOADER_COMPRESS, Linux additionally
 searches firmware with an .xz suffix and decompresses it in-kernel:
 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/base/firmware_loader/main.c?h=v5.17#n754
  3. In 5.19, when configured with FW_LOADER_COMPRESS_ZSTD, Linux will
 additionally support ZSTD-compression with a .zst suffix:
 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/commit/?h=driver-core-next=23cfbc6ec44e5e80d5522976ff45ffcdcddfb230

The end-goal of this is that I'd like the firmware for which this is a
gain to be installed compressed in Debian
(firmware-amd-graphics firmware-iwlwifi firmware-linux-free,
 a common setup, is 19M of .deb, 159M on-disk,
 but just 51M when subjected to
   find fw.xz/ -type f -exec xz {} \;
 (61M zstd default, 55M zstd -19);
 on one machine with that + 283M of xilinx firmware
 the gain is 464M -> 87M (116M, 94M)).

Best,
наб

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

Kernel: Linux 5.10.0-17-amd64 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
From 5774cc330c144f31a5aec00e016395149e810bb7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=BD=D0=B0=D0=B1?= 
Date: Tue, 26 Apr 2022 15:41:59 +0200
Subject: [PATCH 1/3] Respect fw_path_para in add_firmware()
X-Mutt-PGP: OS

/sys/module/firmware_class/parameters/path, if any, is added before
anything else in the module loading path:
  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/base/firmware_loader/main.c?h=v5.17#n406
---
 hook-functions | 13 +
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/hook-functions b/hook-functions
index 95bd584..e9f09c0 100644
--- a/hook-functions
+++ b/hook-functions
@@ -28,7 +28,7 @@ force_load()
 }
 
 # Takes a file containing a list of modules to be added as an
-# argument, figures out dependancies, and adds them.
+# argument, figures out dependencies, and adds them.
 #
 # Input file syntax:
 #
@@ -57,18 +57,23 @@ add_modules_from_file()
 # whether a warning should be printed in that case.)
 add_firmware()
 {
-	local firmware fwloc
+	local firmware fwloc fw_path_para path_firmware
 
 	firmware="${1}"
 
-	if [ -e "${DESTDIR}/lib/firmware/updates/${version?}/${firmware}" ] \
+	read -r fw_path_para < /sys/module/firmware_class/parameters/path
+
+	if { [ -n "$fw_path_para" ] && [ -e "${DESTDIR}/${fw_path_para}/${firmware}" ]; } \
+	|| [ -e "${DESTDIR}/lib/firmware/updates/${version?}/${firmware}" ] \
 	|| [ -e "${DESTDIR}/lib/firmware/updates/${firmware}" ] \
 	|| [ -e "${DESTDIR}/lib/firmware/${version}/${firmware}" ] \
 	|| [ -e "${DESTDIR}/lib/firmware/${firmware}" ]; then
 		return 0
 	fi
 
-	for fwloc in "/lib/firmware/updates/${version}/${firmware}" \
+	[ -n "$fw_path_para" ] && path_firmware="${fw_path_para}/${firmware}" || path_firmware=
+	for fwloc in "$path_firmware" \
+		"/lib/firmware/updates/${version}/${firmware}" \
 		"/lib/firmware/updates/${firmware}" \
 		"/lib/firmware/${version}/${firmware}" \
 		"/lib/firmware/${firmware}"; do
-- 
2.30.2

From c9fa06411d3116cf851b68c319669c0f3649fd46 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=BD=D0=B0=D0=B1?= 
Date: Tue, 26 Apr 2022 15:49:45 +0200
Subject: [PATCH 2/3] Handle compressed firmware in add_firmware()
X-Mutt-PGP: OS

With CONFIG_FW_LOADER_COMPRESS, Linux additionally tries the normal
search path but suffixed with .xz, and decompresses it in-kernel, cf.
  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/base/firmware_loader/main.c?h=v5.17#n754
---
 hook-functions | 38 +-
 1 file changed, 21 insertions(+), 17 deletions(-)

diff --git a/hook-functions b/hook-functions
index e9f09c0..3790343 100644
--- a/hook-functions
+++ b/hook-functions
@@ -57,32 +57,36 @@ add_modules_from_file()
 # whether a warning should be printed in that case.)
 add_firmware()
 {
-	local firmware fwloc fw_path_para path_firmware
+	local firmware suffix fwloc fw_path_para path_firmware
 
 	

Bug#1008296: Workaround for my machine

[Sebastián Lacuesta]

Hi Alban,

My nvidia driver version: 510.85.02-1

cat /sys/module/nvidia_drm/parameters/modeset
N

grep nomodeset /proc/cmdline


Cheers,

Sebastián

El sáb, 27 ago 2022 a las 3:20,  escribió:

> On Fri, 8 Apr 2022 18:19:06 -0300 =?UTF-8?Q?Sebasti=C3=A1n_Lacuesta?=
>  wrote:
> > Overwritting 61-gdm.rules with
> >
> > ln -s /dev/null /etc/udev/rules.d/61-gdm.rules
> >
> > solves the issue for me.
>
> regarding this file disables wayland if nvidia driver below 510 (which
> is not your case) or modesetting is disabled, could you confirm you
> have the nvidia_drm driver with modesetting disabled ?
>
> cat /sys/module/nvidia_drm/parameters/modeset
>
> and
>
> grep nomodeset /proc/cmdline
>
> > Let me know if I can help testing new defaults so this can be solved.
> >
> > Regards
> > Sebastián
>
> Cheers,
>
> Alban
>
>

Bug#1019410: liblief: also package python module

[michel]

Package: liblief0
Version: 0.9.0-1+b12
Severity: wishlist
File: liblief
X-Debbugs-Cc: okgomdjgbm...@gmail.com

Dear Maintainer,



It would be nice to also package the python module.
It's kind of strange that it's not fully packaged.

Bug#644270: Is your email correct?

[John Hernandez]

Dear sir/madam

Are you from Indonesia or living in Indonesia? kindly confirm Asap.

Reply to :  herj47...@gmail.com

Thank You
Mr. John H.

Bug#993161: pam: some remaining changes for DPKG_ROOT

[Helmut Grohne]

Control: clone -1 -2
Control: retitle -2 decide whether pam should support DPKG_ROOT
Control: tags -2 =
Control: reassign -2 tech-ctte

Hi technical comittee members,

On Thu, Aug 18, 2022 at 03:44:54PM +0200, Helmut Grohne wrote:
> Within three weeks I want Steve to reply to this bug in a way that
> addresses Sam's needs or Sam to agree with moving forward without
> Steve's review. Failing that, I will ask the CTTE to override the pam
> maintainers on this patch.

I hope that it does not surprise you. I am formally asking the CTTE to
override the pam maintainers and requiring pam to support DPKG_ROOT.

DPKG_ROOT is a feature that allows installing packages into a chroot
without using the chroot syscall. The major benefit of doing so is
creating foreign chroots without requiring qemu for emulating maintainer
scripts. To work in such a setting, relevant maintainer scripts need to
be modified to operate on a chroot from outside. The location of the
chroot is communicated by dpkg using the DPKG_ROOT environment variable.
This feature is relevant to early architecture bootstrap where qemu is
not reliably available. As such the package set covered initially is
essential (thus covering pam) and shall be extended to build-essential.
Patches have been sent to all relevant essential packages and have been
applied by most. pam already carries partial support for DPKG_ROOT due
to Sam Hartman applying an earlier patch. Thank you. Unfortunately, we
later noticed that it was incomplete when we extended our QA and sent a
followup patch. This second patch is being pending in pam for about a
year. During that year, Sam repeatedly expressed discomfort with how we
approached the problem. In the end, Sam requested Steve to comment on
the matter. However, Steve has not participated at all. As such, the
patch is not being applied and eternally waiting for Steve (no pun
intended). We believe that we addressed all concerns (e.g. quality
assurance, limitation of scope, public discussion at DC22, etc.) raised
by Sam. Yet progress repeatedly stalled on this matter. Please read the
bug log for details. I've come to the conclusion that I will be unable
to resolve this.  Therefore, I ask the CTTE to override the pam
maintainers:

 * pam should support DPKG_ROOT and accept reasonable changes to that
   end.
 * In particular, the patch in bug #993161 is considered a reasonable
   change with bearable maintenance cost and thus should be included
   in pam.
 * pam maintainers are in no way required to support DPKG_ROOT beyond
   accepting reasonable patches and communicating in a timely manner.
   Keeping DPKG_ROOT in a working state is the sole responsibility of
   its proponents.

Since I am requesting a maintainer override, a super majority is
required.

Helmut

Bug#1019408: convert slepc-dev and others to Architecture: any

[Helmut Grohne]

Package: slepc-dev
Version: 3.17.2+dfsg1-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:deal.ii src:dolfin src:getdp

The affected packages cannot satisfy their cross Build-Depends, because
their dependency on slepc-dev is not satisfiable. In general,
Architecture: all packages can never satisfy cross Build-Depends unless
marked Multi-Arch: foreign or annotated :native. Both approaches would
be fatal, because slepc-dev's dependencies would be installed for the
build architecture. Its dependencies are development packages for shared
libraries. Such packages are needed for the host architecture. The only
way to forward the architecture constraint is converting slepc-dev to
Architecture: any. The same reasoning holds for a few more binary
packages built from slepc. Please consider applying the attached patch.

Helmut
diff --minimal -Nru slepc-3.17.2+dfsg1/debian/changelog 
slepc-3.17.2+dfsg1/debian/changelog
--- slepc-3.17.2+dfsg1/debian/changelog 2022-09-03 09:58:19.0 +0200
+++ slepc-3.17.2+dfsg1/debian/changelog 2022-09-08 21:21:58.0 +0200
@@ -1,3 +1,10 @@
+slepc (3.17.2+dfsg1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert -dev packages to Architecture: any. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 08 Sep 2022 21:21:58 +0200
+
 slepc (3.17.2+dfsg1-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru slepc-3.17.2+dfsg1/debian/control 
slepc-3.17.2+dfsg1/debian/control
--- slepc-3.17.2+dfsg1/debian/control   2022-09-03 09:58:19.0 +0200
+++ slepc-3.17.2+dfsg1/debian/control   2022-09-08 21:21:56.0 +0200
@@ -16,7 +16,7 @@
 
 Package: slepc-dev
 Section: libdevel
-Architecture: all
+Architecture: any
 Depends: libslepc-real-dev | libslepc-complex-dev | libslepc-real3.17-dev | 
libslepc-complex3.17-dev,
  ${misc:Depends}
 Description: Scalable Library for Eigenvalue Problem Computations
@@ -30,7 +30,7 @@
 
 Package: libslepc-real-dev
 Section: libdevel
-Architecture: all
+Architecture: any
 Depends: libslepc-real3.17-dev, ${misc:Depends}
 Description: Scalable Library for Eigenvalue Problem Computations
  SLEPc is a software library for the solution of large scale sparse eigenvalue
@@ -44,7 +44,7 @@
 
 Package: libslepc-complex-dev
 Section: libdevel
-Architecture: all
+Architecture: any
 Depends: libslepc-complex3.17-dev, ${misc:Depends}
 Description: Scalable Library for Eigenvalue Problem Computations
  SLEPc is a software library for the solution of large scale sparse eigenvalue
@@ -154,7 +154,7 @@
 
 Package: slepc64-dev
 Section: libdevel
-Architecture: all
+Architecture: any
 Depends: libslepc64-real-dev | libslepc64-complex-dev | 
libslepc64-real3.17-dev | libslepc64-complex3.17-dev,
  ${misc:Depends}
 Description: Scalable Library for Eigenvalue Problem Computations (64-bit)
@@ -169,7 +169,7 @@
 
 Package: libslepc64-real-dev
 Section: libdevel
-Architecture: all
+Architecture: any
 Depends: libslepc64-real3.17-dev, ${misc:Depends}
 Description: Scalable Library for Eigenvalue Problem Computations (64-bit)
  SLEPc is a software library for the solution of large scale sparse eigenvalue
@@ -183,7 +183,7 @@
 
 Package: libslepc64-complex-dev
 Section: libdevel
-Architecture: all
+Architecture: any
 Depends: libslepc64-complex3.17-dev, ${misc:Depends}
 Description: Scalable Library for Eigenvalue Problem Computations (64-bit)
  SLEPc is a software library for the solution of large scale sparse eigenvalue

Bug#1019385: swisswatch: add command-line parameter to display arbitrary time

[Barak A. Pearlmutter]

Great idea!

Patches welcome.

Bug#1019406: monitoring-plugins-standard: check_mailq nullmailer regex patch

[andrew bezella]

attached is a patch that updates the format expected in the nullmailer
mailq output.  the regex is a little more flexible and less specific
than the previous version.

hope this helps.

andy

-- 
andrew bezella 
internet archive
--- a/plugins-scripts/check_mailq.pl.orig	2021-11-30 22:55:47.0 -0800
+++ b/plugins-scripts/check_mailq.pl	2022-09-08 11:12:20.961943936 -0700
@@ -531,9 +531,9 @@
 	}
 
 	while () {
-	#2006-06-22 16:00:00  282 bytes
+	#2022-08-25 01:30:40 502 bytes from 
 
-	if (/^[1-9][0-9]*-[01][0-9]-[0-3][0-9]\s[0-2][0-9]\:[0-2][0-9]\:[0-2][0-9]\s{2}[0-9]+\sbytes$/) {
+	if (/^\d{4}-\d{2}-\d{2}\s+\d{2}\:\d{2}\:\d{2}\s+\d+\sbytes/) {
 		$msg_q++ ;
 	}
 	}

Bug#1019397: gem2deb: fails to cross build with gem_installer.rb

[Helmut Grohne]

Control: tags -1 + patch

Hi Antonio,

On Thu, Sep 08, 2022 at 06:32:52PM +0200, Helmut Grohne wrote:
> That leads to the question of what actually is wrong. One relatively
> obvious thing to be wrong (once you know that my host architecture was
> armel) is the x86-64-linux-gnu part in there. It comes from
> lib/gem2deb/gem_installer.rb and is computed by
> rubygems_integration_target. There ist uses RbConfig::CONFIG['arch'],
> which presumably uses the build architectures rbconfig.rb rather than
> the host architecture one. Do you happen to know how to fix this aspect?
> 
> However this is not what ultimately made the build fail. Later, we are
> instructed to check mkmf.log to see the actual failure. Unfortunately,
> mkmf.log is not part of the build log. Another build with keeping the
> build tree later, one can see that it used the build architecture
> compiler, which happened to fail to find the host architecture ruby
> header. Again, this seems to be rooted in using the wrong rbconfig.rb.
> I suppose that RUBYLIB is not augmented in the right way for running gem
> install in gem_installer.rb. Does that make sense to you?
> 
> I'd appreciate a response indicating whether I'm looking in the right
> direction.

Assuming that both of these would be correct, I tried implementing it
(without knowing ruby). Before too long, I managed to cross build
ruby-oj using the attached patch. It really does quite precisely what I
sketched in the above paragraphs. Does that work for you?

Helmut
diff --minimal -Nru gem2deb-2.0.3/debian/changelog 
gem2deb-2.0.3+nmu1/debian/changelog
--- gem2deb-2.0.3/debian/changelog  2022-07-31 01:44:54.0 +0200
+++ gem2deb-2.0.3+nmu1/debian/changelog 2022-09-08 20:48:33.0 +0200
@@ -1,3 +1,10 @@
+gem2deb (2.0.3+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Make gem_installer.rb work for cross building. (Closes: #1019397)
+
+ -- Helmut Grohne   Thu, 08 Sep 2022 20:48:33 +0200
+
 gem2deb (2.0.3) unstable; urgency=medium
 
   * Gem2Deb::YAML: fix loading more metadata.yml files.
diff --minimal -Nru gem2deb-2.0.3/lib/gem2deb/gem_installer.rb 
gem2deb-2.0.3+nmu1/lib/gem2deb/gem_installer.rb
--- gem2deb-2.0.3/lib/gem2deb/gem_installer.rb  2022-07-31 01:44:54.0 
+0200
+++ gem2deb-2.0.3+nmu1/lib/gem2deb/gem_installer.rb 2022-09-08 
20:48:24.0 +0200
@@ -201,16 +201,17 @@
 
 def rubygems_integration_target(rubyver)
   if metadata.has_native_extensions?
-arch = RbConfig::CONFIG['arch']
 api_version = Gem2Deb::RUBY_API_VERSION[rubyver]
-"/usr/lib/#{arch}/rubygems-integration/#{api_version}"
+"/usr/lib/#{host_arch}/rubygems-integration/#{api_version}"
   else
 "/usr/share/rubygems-integration/all"
   end
 end
 
 def run_gem(ruby, command, *args)
-  run(ruby, '-S', 'gem', command, '--config-file', '/dev/null', 
'--verbose', *args)
+  maybe_crossbuild(ruby) do
+run(ruby, '-S', 'gem', command, '--config-file', '/dev/null', 
'--verbose', *args)
+  end
 end
 
 def load_gemspec_data!

Bug#1014980: tinyexr: CVE-2018-12688 CVE-2018-12064 CVE-2022-34300

[Timo Röhling]

Hi,

On Fri, 15 Jul 2022 17:50:37 +0200 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= 
 wrote:

CVE-2018-12688[0]:
| tinyexr 0.9.5 has a segmentation fault in the wav2Decode function.

https://github.com/syoyo/tinyexr/issues/83

I cannot reproduce this.


CVE-2018-12064[1]:
| tinyexr 0.9.5 has a heap-based buffer over-read via
| tinyexr::ReadChannelInfo in tinyexr.h.

Doesn't seem to have been reported upstream so far:
https://github.com/ChijinZ/security_advisories/tree/master/tinyexr_7953aea

I cannot reproduce this either.


CVE-2022-34300[2]:
| In tinyexr 1.0.1, there is a heap-based buffer over-read in
| tinyexr::DecodePixelData.

https://github.com/syoyo/tinyexr/issues/167

I can confirm this bug, and I submitted a patch to upstream:
https://github.com/syoyo/tinyexr/pull/175


Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Bug#1019406: monitoring-plugins-standard: check_mailq nullmailer regex does not match current output

[andrew bezella]

Package: monitoring-plugins-standard
Version: 2.3.1-1
Severity: normal

Dear Maintainer,

it seems that the output from nullmailer's mailq has changed format since
that portion was implemented.  i noticed that it was not alerting on a
host w/many messages in its queue:

% mailq | wc -l
12488
% check_mailq -M nullmailer -w 5 -c 10
OK: nullmailer mailq (0) is below threshold (5/10)|unsent=0;5;10;0

i am testing a patch to correct this.

thanks in advance,

andy

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

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

Versions of packages monitoring-plugins-standard depends on:
ii  libc6 2.31-13+deb11u3
ii  monitoring-plugins-basic  2.3.1-1
ii  ucf   3.0043

Versions of packages monitoring-plugins-standard recommends:
ii  bind9-dnsutils [dnsutils]  1:9.16.27-1~deb11u1
ii  bind9-host [host]  1:9.16.27-1~deb11u1
ii  libcurl4   7.74.0-1.3+deb11u2
ii  libdbi10.9.0-6
ii  libldap-2.4-2  2.4.57+dfsg-3+deb11u1
ii  libmariadb31:10.5.15-0+deb11u1
ii  libnet-snmp-perl   6.0.1-6
ii  libpq5 13.7-0+deb11u1
ii  libradcli4 1.2.11-1+b2
ii  libssl1.1  1.1.1n-0+deb11u3
ii  liburiparser1  0.9.4+dfsg-1+deb11u1
ii  rpcbind1.2.5-9
ii  smbclient  2:4.13.13+dfsg-1~deb11u5
ii  snmp   5.9+dfsg-4+deb11u1
ii  sudo   1.9.5p2-3

Versions of packages monitoring-plugins-standard suggests:
pn  fping 
pn  icinga2   
pn  postfix | sendmail-bin | exim4-daemon-heavy | exim4-daemon-light  
pn  qstat 

-- no debconf information

Bug#1006418: Linux stubdomains

[Gémes Géza]

Hello Everyone,

Just my 2c's: maybe instead of trying to enable the somewhat outdated 
Mini-OS based stubdomains: 
https://wiki.xenproject.org/wiki/Device_Model_Stub_Domains we should 
rather try to implement support for Linux based stubdomains: 
https://wiki.xenproject.org/wiki/Linux_stub_domains. As IMHO this could 
be done as a special flavor of the linux kernel + a custom initramfs, I 
add the debian-kernel mailing list.


Please share your thoughts.

Thank you and best regards,

Geza

Bug#1019405: rust-oxhttp: builds uninstallable packages on archs without rust-rustls

[Steve Langasek]

Package: rust-oxhttp
Version: 0.1.4-4
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Hi Jonas,

rust-oxhttp is not migrating to testing because it builds packages which
depend on rust-rustls, and rust-rustls is not available on archs.

In Ubuntu, I have uploaded the attached patch which adds a build-dependency
on librust-rustls-dev, so that it only builds on archs where this is
available.  This has the advantage that if and when rust-rustls's build
failures get fixed, rust-oxhttp will build again.  But in the meantime, it's
best to not have librust-oxhttp+rustls-dev on these archs, and let
rust-oxhttp migrate.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru rust-oxhttp-0.1.4/debian/control rust-oxhttp-0.1.4/debian/control
--- rust-oxhttp-0.1.4/debian/control2022-06-25 05:39:29.0 -0700
+++ rust-oxhttp-0.1.4/debian/control2022-09-08 11:11:27.0 -0700
@@ -6,6 +6,7 @@
  dh-cargo (>= 25),
  librust-httparse-1+default-dev ,
  librust-url-2+default-dev ,
+ librust-rustls-dev
 Maintainer: Jonas Smedegaard 
 Standards-Version: 4.6.1
 Vcs-Git: https://salsa.debian.org/debian/rust-oxhttp.git

Bug#1019404: wireplumber: doesn't start on non-systemd

[Adam Borowski]

Package: wireplumber
Version: 0.4.11-3
Severity: normal

Hi!
Unlike PulseAudio, the PipeWire stack doesn't get up by itself on systems
that use any init/rc system other than systemd.

It works fine afterwards; so far I've been using this unsightly script:
.--
#!/bin/sh

pipewire &
sleep 1
wireplumber &
sleep 1
pipewire-pulse &
`
but that's obviously a monstrosity you don't want.  I'm including it here
only as a proof that I've tested PipeWire for sound; it works for me fine
on a bunch of machines


Meow!
-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(120, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-rc4-00016-g13430c8e1a1e (SMP w/64 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages wireplumber depends on:
ii  init-system-helpers   1.64
ii  libc6 2.35-0experimental2
ii  libglib2.0-0  2.73.3-3
ii  libpipewire-0.3-0 0.3.57-1
ii  libwireplumber-0.4-0  0.4.11-3
ii  pipewire  0.3.57-1

Versions of packages wireplumber recommends:
ii  pipewire-pulse  0.3.57-1

Versions of packages wireplumber suggests:
pn  libspa-0.2-bluetooth  

-- no debconf information

Bug#1019403: gitlab: failed to fetch comments in issue (500 Internal Server Error)

[Maximilian Stein]

Package: gitlab
Version: 15.3.2+ds1-1~fto11+1
Severity: normal
Tags: patch

Dear Maintainer,

After upgrading Gitlab, issue comments failed to fetch. I got the
following log entries:

Completed 500 Internal Server Error in 234ms (ActiveRecord: 154.4ms | 
Elasticsearch: 0.0ms | Allocations: 66512)

NoMethodError (undefined method `h' for LabelsHelper:Module):

app/helpers/labels_helper.rb:250:in `render_label_text'
app/helpers/labels_helper.rb:61:in `render_colored_label'
lib/banzai/filter/references/label_reference_filter.rb:120:in 
`object_link_text'


To me, this seemed like a typo, so I simply removed "h " in
labels_helper.rb:250. This fixed the issue for me, as far as I can
tell.

Best,
Maximilian


---

--- a/usr/share/gitlab/app/helpers/labels_helper.rb
+++ b/usr/share/gitlab/app/helpers/labels_helper.rb
@@ -247,7 +247,7 @@
 class="#{css_class}"
 data-container="body"
 data-html="true"
-#{"style=\"background-color: #{h bg_color}\"" if bg_color}
+#{"style=\"background-color: #{bg_color}\"" if bg_color}
   >#{ERB::Util.html_escape_once(name)}#{suffix}
 HTML
   end

Bug#145433: help with website.

[Nishant]

Hello,

My name is Nishant, I am an India-based - expert WordPress - WooCommerce
developer with more than 14+ years of experience with PHP, HTML5, CSS3,
JavaScript, jQuery, bootstrap, Shopify, MySQL, and WordPress theme,
WordPress Plugin, and Customize themes with clean code.. My work is
100% original.

I am able to do any kind of remote job for WordPress including CMS
Development using WordPress, Template Designs, Development and
Customization, Modification, Blog Development, Portal Development & Website
Maintenance.

Daily updates, availability, and high quality of work are guaranteed.

Feel free to contact me to ask any questions, arrange a call or discuss the
project in chat.

Thank you for your time, and have a great day!

Many Thanks,

Nishant

Bug#958981: ITP: xreader -- A generic document reader

[Antoine Beaupré]

On 2020-04-27 15:27:16, Hugo Ziviani wrote:
> Package: wnpp
> Severity: wishlist
>
> Starting working on the packing for xreader.
> Available on: (https://github.com/linuxmint/xreader)

Any progress on this?

-- 
Blind respect for authority is the greatest enemy of truth.
   - Albert Einstein

Bug#1019319: etckeeper: Prints warnings due to obsolescent egrep usage

[Antoine Beaupré]

Control: tags -1 +pending

On 2022-09-07 12:12:44, Guillem Jover wrote:
> Source: etckeeper
> Source-Version: 1.18.17-1
> Severity: normal
> Tags: upstream patch
>
> Hi!
>
> With the recent grep 2.8 release, egrep usage, which has been slated
> for removal for a long time, now generates warnings, such as:
>
>   egrep: warning: egrep is obsolescent; using grep -E
>
> This causes unintended output on etckeeper usage. I'm attaching a
> patch that should fix those. I've not touched the doc/todo/ items.

Thanks for the speedy patch, but this was actually already fixed
upstream and released in 1.18.18, which I have just pushed to unstable.

Thanks!

a.

-- 
The ideal situation occurs when the things that we regard as beautiful
are also regarded by other people as useful.
- Donald Knuth

Bug#1016936: dwz: fails while building assaultcube

[Ben Westover]

Control: retitle 1016936 dwz: Unknown debugging section .debug_addr causes some 
builds to fail
Control: tags 1016936 + upstream

Hello,

This error also occurred for me when building PolyMC under Clang, but
not GCC. It seems this problem is common for many Clang builds [1].
Fedora also seems to be having issues with this; Thus, I'm retitling
this bug to be more generic, and adding an upstream tag. I will create a
bug when my Bugzilla account creation request is approved by the admin.

Thanks,
--
Ben Westover

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997080#41


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019401: QSGRenderThread[569483]: segfault after suspend/resume

[piorunz]

Package: libqt5core5a
Version: 5.15.4+dfsg-5
Severity: normal
X-Debbugs-Cc: pior...@gmx.com

Dear Maintainer,

I Did suspend/resume cycle of my computer.
Later I found in dmesg:

[96111.865203] QSGRenderThread[569483]: segfault at 0 ip 7fe450b2bcfb sp
7fe411703950 error 4 in libQt5Core.so.5.15.4[7fe450ae9000+301000]
[96111.865213] Code: 38 64 48 8b 04 25 28 00 00 00 48 89 44 24 28 31 c0 e8 c9
a4 ff ff 48 85 c0 0f 84 4a 11 fc ff 48 89 c3 4c 8d 68 50 48 8b 40 50 <49> 63 2c
24 3b 68 04 7d 6c 8b 10 83 fa 01 76 25 8b 70 08 81 e6 ff

   * What outcome did you expect instead?
No error at all


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

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

Versions of packages libqt5core5a depends on:
ii  libc6  2.34-7
ii  libdouble-conversion3  3.2.1-1
ii  libgcc-s1  12.2.0-1
ii  libglib2.0-0   2.73.3-3
ii  libicu71   71.1-3
ii  libpcre2-16-0  10.40-1
ii  libstdc++6 12.2.0-1
ii  libzstd1   1.5.2+dfsg-1
ii  shared-mime-info   2.2-1
ii  zlib1g 1:1.2.11.dfsg-4.1

Versions of packages libqt5core5a recommends:
ii  qttranslations5-l10n  5.15.4-2

Versions of packages libqt5core5a suggests:
ii  libthai0  0.1.29-1

-- no debconf information

Bug#1019400: original-awk: New upstream release 20220122

[Boyuan Yang]

Package: original-awk
Version: 2018-08-27-1
Severity: wishlist
Tags: sid

A new upstream awk release is available at
https://github.com/onetrueawk/awk/releases/tag/20220122 .

Thanks,
Boyuan Yang


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

Bug#1019398: XDG desktop files lack video/ogg in MIME-Type list

[Petter Reinholdtsen]

Package: qtav-players
Version: 1.13.0+ds-4

The .desktop files in  this package fail to list video/ogg  as one of
the supported video files:

  % grep video/ogg /usr/share/applications/Player.desktop \
/usr/share/applications/QMLPlayer.desktop
  %

As ffmpeg is used to decode video, I believe Ogg videos are supported.

A larger list of MIME types I suspect the programs support are listed on
https://wiki.debian.org/DebianMultimedia/PlayerSupport >.

--
Happy hacking
Petter Reinholdtsen

Bug#842902: closed by Patrick Matthäi (Closing already long fixed bugs)

[Petter Reinholdtsen]

[Patrick Matthäi]
> Please feel free to reopen if I am wrong, but retest it with 0.99.13

Look like the situation is a lot better, at least.  I just updated
https://wiki.debian.org/DebianMultimedia/PlayerSupport >
and see from that list that xine-ui now list 107 media types as
supported. :)

Still some MIME types only handled by the other players, but I do not
know if xine-ui also support them. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#1019388: Acknowledgement (apt-clone: Fails to run - no /usr/bin/dpkg-repack found)

[Rann Bar-On]

Fixed by installing dpkg-repack. So maybe this is just a dependency issue?


On 9/8/22 07:39, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 1019388: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019388.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   baronr...@gmail.com
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Michael Vogt 

If you wish to submit further information on this problem, please
send it to 1019...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.


--
--
Rann Bar-On
he/him/his

Bug#1019397: gem2deb: fails to cross build with gem_installer.rb

[Helmut Grohne]

Package: gem2deb
Version: 2.0.3
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:ruby-oj
X-Debbugs-Cc: debian-cr...@lists.debian.org

Hi Antonio,

thank you for the past work in making ruby and gem2deb support cross
building. I happen to have found another issue. Again, I believe it to
be of generic nature rather than specific to a particular extension
package. An example package is ruby-oj:

https://crossqa.debian.net/build/ruby-oj_3.13.21-1_ppc64el_20220830150857.log

As a first observation, I note that the build log looks much different
from the extensions that built successfully after your changes. A common
theme among the succeeding ones is this:

/usr/bin/ruby3.0 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb ...

Notably, that's not found in ruby-oj. Instead, I see this:

/usr/bin/ruby3.0 -S gem install --config-file /dev/null --verbose --local 
--verbose --no-document --ignore-dependencies --install-dir 
debian/ruby-oj/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 
/tmp/d20220907-2098396-1rsfxr/oj-3.13.21.gem

As far as I understand this, we have multiple extension build systems
for ruby. The former one has been fixed, but the one in
"gem_installer.rb" hasn't.

That leads to the question of what actually is wrong. One relatively
obvious thing to be wrong (once you know that my host architecture was
armel) is the x86-64-linux-gnu part in there. It comes from
lib/gem2deb/gem_installer.rb and is computed by
rubygems_integration_target. There ist uses RbConfig::CONFIG['arch'],
which presumably uses the build architectures rbconfig.rb rather than
the host architecture one. Do you happen to know how to fix this aspect?

However this is not what ultimately made the build fail. Later, we are
instructed to check mkmf.log to see the actual failure. Unfortunately,
mkmf.log is not part of the build log. Another build with keeping the
build tree later, one can see that it used the build architecture
compiler, which happened to fail to find the host architecture ruby
header. Again, this seems to be rooted in using the wrong rbconfig.rb.
I suppose that RUBYLIB is not augmented in the right way for running gem
install in gem_installer.rb. Does that make sense to you?

I'd appreciate a response indicating whether I'm looking in the right
direction.

Thanks in advance

Helmut

Bug#1019396: cloudflare-ddns: Systemd service uses nonexistent user

[Sean Leonard]

Package: cloudflare-ddns
Version: 2.0.0-1+b1
Severity: important
X-Debbugs-Cc: meanderingc...@aetherislands.net

Dear Maintainer,

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

   * What led up to the situation?

 Installed, updated config, and started service with systemctl
 Logs showed an error "Failed to determine user credentials".

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

 Added system user "cloudflare-ddns" to match the systemd service
 unit.

   * What was the outcome of this action?

 Subsequent executions of the service succeeded.

   * What outcome did you expect instead?

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


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (600, 'testing'), (450, 'stable-security'), (350, 
'stable-updates'), (300, 'stable'), (175, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cloudflare-ddns depends on:
ii  libc62.33-7
ii  libcloudflare-ddns2  2.0.0-1+b1
ii  libcurl4 7.83.1-1+b1
ii  libgcc-s112.1.0-2
ii  libinireader055-1
ii  libsimdjson9 1.0.2-2
ii  libstdc++6   12.1.0-2

Versions of packages cloudflare-ddns recommends:
ii  systemd  250.4-1

cloudflare-ddns suggests no packages.

-- Configuration Files:
/etc/cloudflare-ddns/config.ini changed [not included]

-- no debconf information

Bug#1018949: netkit-telnet: Drop in favour of netkit-telnet-ssl

[Bastian Germann]

Am 06.09.22 um 16:16 schrieb Bastian Germann:

I don't have a strong opinion on any solution, but I think we should be
conservative in what we do -- it may years for people to realize
civilization depends on a particular behaviour of netkit-telnet...


Yes, but they still have that behaviour with netkit-telnet-ssl.


Just to be clear on this: There is one thing that you need to do to enable 
clear-text use of in.telnetd:
It needs the command line argument -z nossl. This should be stated in the telnetd package's description on the last 
sentence: If you want to keep using the netkit implementation, then install telnetd-ssl instead and run in.telnetd with 
the argument -z nossl for the clear-text protocol.

Bug#1019335: Reconsider the egrep and fgrep deprecation

[Santiago Ruano Rincón]

El 07/09/22 a las 21:13, Paul Gevers escribió:
> Hi all,
> 
> For transparency I'm letting you know that, with my Release Team manager hat
> on, I have just added a migration block on grep.
> 
> On Wed, 7 Sep 2022 17:39:45 +0200 Santiago Ruano =?iso-8859-1?Q?Rinc=F3n?=
>  wrote:
> > For the moment, I am waiting for (a final) upstream input about those
> > warning, in this bug:
> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57604
> > 
> > But giving:
> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49996
> > I doubt they are willing to reconsider deprecating egrep and fgrep.
> 
> But we should be considering our own users.

Yes. I just wanted to have more info from upstream. Or avoid uploading
two releases if they decided to revert that change.

> I'd appreciate it if either
> Debian continues to ship egrep and fgrep. Or if you don't want to do that or
> if you don't want to decide on your own I'd appreciate it if we had a bit of
> discussion in a broader audience (I suggest debian-de...@l.do) to see what
> we as a project believe is the right course of action.

I don't think it is needed to discuss at a debian-devel level. I am
reconsidering to revert the related changes. I hope I will be able to
upload tomorrow.

> 
> To be clear, I'm not saying we can't have this change at all, but I'm saying
> we can't have this change with at least some agreement that it's acceptable
> by the project. The block is to buy us time to reach that agreement.
> 

Thanks!

> Paul





signature.asc
Description: PGP signature

Bug#1019395: bacula FTCBFS: fails finding libmysqlclient

[Helmut Grohne]

Source: bacula
Version: 9.6.7-5
Tags: upstream patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

bacula fails to cross build from source, because it fails finding
libmysqlclient. It looks for mysql libraries using mysql_config, which
is known to not work during cross compilation. Rather than mysql_config,
using pkg-config works. This patch introduces another way of detecting
mysql using pkg-config as pkg-config generally works with cross
compilation and mysql provides a working .pc files. Please consider
applying the attached patch.

Helmut
--- bacula-9.6.7.orig/autoconf/bacula-macros/db.m4
+++ bacula-9.6.7/autoconf/bacula-macros/db.m4
@@ -340,21 +340,31 @@
 AC_HELP_STRING([--with-mysql@<:@=DIR@:>@], [Include MySQL support. DIR is the MySQL base install directory, default is to search through a number of common places for the MySQL files.]),
 [
   HAVE_LIBSR="no"
-  if test "$withval" != "no"; then
- if test "$withval" = "yes"; then
-MYSQL_CONFIG=`which mysql_config 2>/dev/null`
-if test "x${MYSQL_CONFIG}" != x; then
-   MYSQL_BINDIR="${MYSQL_CONFIG%/*}"
-   ${MYSQL_CONFIG} --libs_r >/dev/null 2>&1
-   if test $? = 0; then
-  MYSQL_LIBDIR=`${MYSQL_CONFIG} --libs_r`
-  MYSQL_INCDIR=`${MYSQL_CONFIG} --include`
-  HAVE_LIBSR="yes"
-   else
-  ${MYSQL_CONFIG} --variable=pkglibdir > /dev/null 2>&1
-  if test $? = 0 ; then
- MYSQL_LIBDIR=`${MYSQL_CONFIG} --variable=pkglibdir`
- MYSQL_INCDIR=`${MYSQL_CONFIG} --variable=pkgincludedir`
+  AS_IF([test "$withval" != "no"],[
+ AS_IF([test "$withval" = "yes"],[
+AC_REQUIRE([PKG_PROG_PKG_CONFIG])
+if $PKG_CONFIG --exists mysqlclient; then
+   MYSQL_BINDIR=/usr/bin
+   MYSQL_LIBDIR=`$PKG_CONFIG mysqlclient --libs`
+   MYSQL_INCDIR=`$PKG_CONFIG mysqlclient --cflags-only-I`
+   HAVE_LIBSR=yes
+fi
+# if something wrong fall back to old method
+if test "x${MYSQL_LIBDIR}" = x -o "x${MYSQL_INCDIR}" = x ; then
+   MYSQL_CONFIG=`which mysql_config 2>/dev/null`
+   if test "x${MYSQL_CONFIG}" != x; then
+  MYSQL_BINDIR="${MYSQL_CONFIG%/*}"
+  ${MYSQL_CONFIG} --libs_r >/dev/null 2>&1
+  if test $? = 0; then
+ MYSQL_LIBDIR=`${MYSQL_CONFIG} --libs_r`
+ MYSQL_INCDIR=`${MYSQL_CONFIG} --include`
+ HAVE_LIBSR="yes"
+  else
+ ${MYSQL_CONFIG} --variable=pkglibdir > /dev/null 2>&1
+ if test $? = 0 ; then
+MYSQL_LIBDIR=`${MYSQL_CONFIG} --variable=pkglibdir`
+MYSQL_INCDIR=`${MYSQL_CONFIG} --variable=pkgincludedir`
+ fi
   fi
fi
 fi
@@ -419,7 +429,7 @@
   AC_MSG_ERROR(Unable to find mysql.h in standard locations)
fi
 fi
- else
+ ],[
 if test -f $withval/include/mysql/mysql.h; then
MYSQL_INCDIR=$withval/include/mysql
if test -f $withval/lib64/mysql/libmysqlclient_r.a \
@@ -478,7 +488,7 @@
AC_MSG_RESULT(no)
AC_MSG_ERROR(Invalid MySQL directory $withval - unable to find mysql.h under $withval)
 fi
- fi
+ ])
  if test "x${MYSQL_LIBDIR}" != x; then
 MYSQL_INCLUDE=-I$MYSQL_INCDIR
 if test "x$HAVE_LIBSR" = "xyes"; then
@@ -546,7 +556,7 @@
  else
 AC_MSG_RESULT(no)
  fi
-  fi
+  ])
 ],[
   AC_MSG_RESULT(no)
 ])

Bug#1019369: cgit: FTBFS on riscv64: t0109-git-config test failed on riscv64

[Sakura286]

2022/9/8 8:02, Paul Wise :

Reading the documentation, this should work, but please test it:
strace -e access,faccessat


Thanks for your advice. Since "access" is invalid on riscv64, just like 
"strace -e access", "strace -e access,faccessat" will also fail. You 
cannot pass an invalid syscall name to "strace -e".


I'm trying to find out why "access" is invalid and I might submit a new 
patch later.


Regards,

Sakura286.

Bug#1019374: deb-scrub-obsolete crashes with AttributeError

[Jelmer Vernooij]

On Thu, Sep 08, 2022 at 07:55:16AM +0200, Marcin Owsiany wrote:
> Package: lintian-brush
> 
> Please see
> https://janitor.debian.net/cupboard/pkg/apt-forktracer/b292a431-c8b4-421b-9c7f-b3555ead4046/
> 
> Removing run time and build time constraints unnecessary since
> busterTraceback (most recent call last):  File
> "/code/lintian-brush/scripts/deb-scrub-obsolete", line 4, in 
>   main()  File "/code/lintian-brush/lintian_brush/scrub_obsolete.py",
> line 712, in mainresult = scrub_obsolete(  File
> "/code/lintian-brush/lintian_brush/scrub_obsolete.py", line 529, in
> scrub_obsolete+ release_aliases(release))  File
> "/code/lintian-brush/lintian_brush/scrub_obsolete.py", line 471, in
> release_aliasesdebian_distro_info.unstable:
> 'unstable',AttributeError: 'DebianDistroInfo' object has no attribute
> 'unstable'. Did you mean: 'stable'?

Thanks for the bug report - this has indeed already been fixed. Feel
free to press the "Reschedule' button to get it to reprocess the package
again.

FWIW The janitor generally runs snapshots of lintian-brush, so whatever is in
the archive is usually more stable. If you come across issues on the
site, a bug report in salsa is usually best @
https://salsa.debian.org/jelmer/janitor.debian.net/-/issues/new

Jelmer


signature.asc
Description: PGP signature

Bug#1019343: Remove Date::Manip entirely? PATCH [1/1]

[Holger Levsen]

control: severity -1 important
# getting mail every 5mins is really not acceptable
thanks

On Wed, Sep 07, 2022 at 04:59:17PM -0700, Nye Liu wrote:
> munin-graph does not seem to use Date::Manip at all, unless there is a
> hidden dependency that isn't obvious.

thank you for your bug report! have you tried your patch?


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

No mas pobres en un pais rico!


signature.asc
Description: PGP signature

Bug#1018957: mmdebstrap fails in proot mode

[Christoph Groth]

Johannes Schauer Marin Rodrigues wrote:

> $ mmdebstrap --include=hello testing - | tar -C /tmp/fakechroot -x

This is perfect for my purposes, thanks!


signature.asc
Description: PGP signature

Bug#1019394: rails breaks ruby-arbre autopkgtest: different output

[Paul Gevers]

Source: rails, ruby-arbre
Control: found -1 rails/2:6.1.6.1+dfsg-4
Control: found -1 ruby-arbre/1.4.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of rails the autopkgtest of ruby-arbre fails in 
testing when that autopkgtest is run with the binary packages of rails 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
rails  from testing2:6.1.6.1+dfsg-4
ruby-arbre from testing1.4.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of rails to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=rails

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-arbre/25833919/log.gz


Failures:

  1) Building forms building a simple form for should include the 
hidden authenticity token
 Failure/Error: expect(html).to include 'name="authenticity_token" value="AUTH_TOKEN" />'


   expected "id=\"new_mock_person_\" action=\"/\" accept-charset=\"UTF-8\" 
method...e\">Nameid=\"mock_person_name\" />\n" to include "name=\"authenticity_token\" value=\"AUTH_TOKEN\" />"

   Diff:
   @@ -1,2 +1,3 @@
   -value="AUTH_TOKEN" />
   +accept-charset="UTF-8" method="post">value="" autocomplete="off" />name="authenticity_token" value="AUTH_TOKEN" autocomplete="off" />
   +Namename="mock_person[name]" id="mock_person_name" />
 # ./spec/rails/integration/forms_spec.rb:25:in `block (3 levels) 
in '


Finished in 0.23882 seconds (files took 1.79 seconds to load)
128 examples, 1 failure

Failed examples:

rspec ./spec/rails/integration/forms_spec.rb:24 # Building forms 
building a simple form for should include the hidden authenticity token


/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib 
/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
--pattern ./spec/\*\*/\*_spec.rb --format documentation failed

mv ./.gem2deb.lib lib
mv ./.gem2deb.Gemfile.lock Gemfile.lock
autopkgtest [04:15:16]: test gem2deb-test-runner



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019393: hdf5 breaks libsis-jhdf5-java autopkgtest: Could not initialize class

[Paul Gevers]

Source: hdf5, libsis-jhdf5-java
Control: found -1 hdf5/1.10.8+repack-1
Control: found -1 libsis-jhdf5-java/19.04.1+dfsg-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of hdf5 the autopkgtest of libsis-jhdf5-java fails 
in testing when that autopkgtest is run with the binary packages of hdf5 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
hdf5   from testing1.10.8+repack-1
libsis-jhdf5-java  from testing19.04.1+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of hdf5 to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=hdf5

https://ci.debian.net/data/autopkgtest/testing/amd64/libs/libsis-jhdf5-java/25831074/log.gz

Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
[TestNGContentHandler] [WARN] It is strongly recommended to add 
"http://testng.org/testng-1.0.dtd; >" at the top 
of your file, otherwise TestNG may fail or not work as expected.

[TestNG] Running:

/tmp/autopkgtest-lxc.50ajov7f/downtmp/build.MuO/src/sourceTest/java/tests.xml

sourceTest/java/ch/systemsx/cisd/hdf5/h5ar/test.h5ar
sourceTest/java/ch/systemsx/cisd/hdf5/h5ar/test_14_12_0.h5ar
[Utils] Attempting to create /tmp/tmp.FUdpvQH0CP/test-output/All/All.xml
[Utils]   Directory /tmp/tmp.FUdpvQH0CP/test-output/All exists: true
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@697a0948)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@7cf63b9a)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@4776e209)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@265a094b)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@1f536481)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@5234b61a)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@22a260ff)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@54c425b1)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@50b734c4)
PASSED: testBitSetRoundTrip({})
PASSED: testBitSetRoundTrip({0})
PASSED: testBitSetRoundTrip({31})
PASSED: testBitSetRoundTrip({64})
PASSED: testBitSetRoundTrip({128})
PASSED: testBitSetRoundTrip({63, 191})
PASSED: testBitSetRoundTrip({64, 192})
PASSED: testBitSetRoundTrip({17, 88, 155})
PASSED: testBitSetRoundTrip({0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 
13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 
31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 
49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 
67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 
85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 
102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 
116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 
130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 
144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 
158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 
172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 
186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 
200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 
214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 
228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 
242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255})

PASSED: testAttributeTypeVariantAttributeName
PASSED: testConversion
PASSED: testTypeVariant
PASSED: testFileExistsOnFS
PASSED: testOnlyFileAndDirExistsOnFS
PASSED: testConcatLink
PASSED: testGetParentPath
PASSED: testNormalizePath
PASSED: testDescribeLink
PASSED: testGetPermissions
PASSED: testIdCache
PASSED: testToInt64
PASSED: testToInt64_Overflow
PASSED: testToUint16
PASSED: testToUint32
PASSED: testToUint8
PASSED: testIncrementIdx
PASSED: testConvertUnit
PASSED: testCompressAll
PASSED: testCompressBlackList
PASSED: testCompressBlackWhiteList
PASSED: testCompressDefault
PASSED: testCompressDefaultWithCompression
PASSED: testCompressWhiteList
FAILED: testAccessClosedReaderWriter
java.lang.ExceptionInInitializerError
at hdf.hdf5lib.HDF5Constants.(HDF5Constants.java:29)
	at 
ch.systemsx.cisd.hdf5.IHDF5WriterConfigurator$FileFormatVersion.(IHDF5WriterConfigurator.java:74)
	at 

Bug#1019392: toybox: autopkgtest regression on ppc64el: exited with signal (or returned 255)

[Paul Gevers]

Source: toybox
Version: 0.8.8+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of toybox the autopkgtest of toybox fails in 
testing when that autopkgtest is run with the binary packages of toybox 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
toybox from testing0.8.8+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=toybox

https://ci.debian.net/data/autopkgtest/testing/ppc64el/t/toybox/25825642/log.gz

# README:
# The maximum sane configuration is "make defconfig": allyesconfig isn't
CFLAGS="-g -O2 
-ffile-prefix-map=/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now" make defconfig
make[1]: Entering directory 
'/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src'
cc -g -O2 
-ffile-prefix-map=/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -o kconfig/conf 
kconfig/conf.c kconfig/zconf.tab.c -DKBUILD_NO_NLS=1 \

-DPROJECT_NAME=\"ToyBox\"
kconfig/conf.c: In function ‘conf_askvalue’:
kconfig/conf.c:104:17: warning: ignoring return value of ‘fgets’ 
declared with attribute ‘warn_unused_result’ [-Wunused-result]

  104 | fgets(line, 128, stdin);
  | ^~~
kconfig/conf.c: In function ‘conf_choice’:
kconfig/conf.c:359:25: warning: ignoring return value of ‘fgets’ 
declared with attribute ‘warn_unused_result’ [-Wunused-result]

  359 | fgets(line, 128, stdin);
  | ^~~
scripts/genconfig.sh
kconfig/conf -D /dev/null Config.in > /dev/null
make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src'

# Go for insanely overpowered toys!
# allyesconfig add build-depends: libssl-dev zlib1g-dev
#CFLAGS="-g -O2 
-ffile-prefix-map=/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now" make allyesconfig

# Hardening and such FLAGS
echo -g -O2 
-ffile-prefix-map=/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src=. 
-fstack-protector-strong -Wformat -Werror=format-security > generated/cflags

echo -Wdate-time -D_FORTIFY_SOURCE=2 >> generated/cflags
scripts/test.sh
make[1]: Entering directory 
'/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src'

scripts/install.sh --symlink --force
Compile instlist...
Library probe
generated/{Config.in,newtoys.h,flags.h,globals.h,tags.h,help.h}
Install commands...
make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src'

PASS: base32 simple
PASS: base32 file
PASS: base32 simple -d
PASS: base32 file -d
PASS: base32 default wrap
PASS: base32 multiline -d PASS: base32 -w
PASS: base32 -w0
PASS: base64 simple
PASS: base64 file
PASS: base64 simple -d
PASS: base64 simple -d
PASS: base64 default wrap
PASS: base64 multiline -d PASS: base64 -w
PASS: base64 -w0
PASS: basename /-only
PASS: basename trailing /
PASS: basename combined
PASS: basename suffix
PASS: basename suffix=result
PASS: basename reappearing suffix 1
PASS: basename reappearing suffix 2
PASS: basename invalid suffix
PASS: basename zero-length suffix
PASS: basename -s
PASS: basename -s implies -a
PASS: basename -a
PASS: blkid cramfs
PASS: blkid ext2
PASS: blkid ext3
PASS: blkid ext4
PASS: blkid f2fs
PASS: blkid msdos
PASS: blkid ntfs
PASS: blkid reiserfs
PASS: blkid squashfs
PASS: blkid vfat
PASS: blkid xfs
PASS: blkid stdin
PASS: blkid -o value -s
PASS: blkid -o export
PASS: bzcat 2 known files
PASS: bzcat overflow
PASS: bzcat badcrc
PASS: cat cat
PASS: cat -
PASS: cat file1 file2
PASS: cat - file
PASS: cat file -
PASS: cat file1 notfound file2
PASS: cat binary
PASS: cat - file1
PASS: cat > /dev/full
SKIP: chattr (not root)
SKIP: chgrp (not root)
PASS: chmod 000 dir
PASS: chmod 000 file
PASS: chmod 007 dir
PASS: chmod 007 file
PASS: chmod 030 dir
PASS: chmod 030 file
PASS: chmod 037 dir
PASS: chmod 037 file
PASS: chmod 060 dir
PASS: chmod 060 file
PASS: chmod 067 dir
PASS: chmod 067 file
PASS: chmod 100 dir
PASS: chmod 100 file
PASS: chmod 107 dir
PASS: chmod 107 file
PASS: chmod 130 dir
PASS: chmod 130 file
PASS: chmod 137 dir
PASS: chmod 137 file
PASS: chmod 160 dir
PASS: chmod 160 file
PASS: chmod 167 dir
PASS: chmod 167 file
PASS: chmod 

Bug#1019391: python-typing-inspect breaks python-marshmallow-dataclass autopkgtest: TypeError: CustomTypeNoneValidator is not a dataclass

[Paul Gevers]

Source: python-typing-inspect, python-marshmallow-dataclass
Control: found -1 python-typing-inspect/0.8.0-1
Control: found -1 python-marshmallow-dataclass/8.5.8-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of python-typing-inspect the autopkgtest of 
python-marshmallow-dataclass fails in testing when that autopkgtest is 
run with the binary packages of python-typing-inspect from unstable. It 
passes when run with only packages from testing. In tabular form:


 passfail
python-typing-inspectfrom testing0.8.0-1
python-marshmallow-dataclass from testing8.5.8-2
all others   from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of 
python-typing-inspect to testing [1]. Due to the nature of this issue, I 
filed this bug report against both packages. Can you please investigate 
the situation and reassign the bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=python-typing-inspect

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-marshmallow-dataclass/25831906/log.gz

=== FAILURES 
===
___ TestClassSchema.test_validator_stacking 



class_or_instance = .new_type at 0x7f0b19be1990>

def fields(class_or_instance):
"""Return a tuple describing the fields of this dataclass.
Accepts a dataclass or an instance of one. Tuple elements 
are of

type Field.
"""
# Might it be worth caching this, per class?
try:

  fields = getattr(class_or_instance, _FIELDS)
E   AttributeError: 'function' object has no attribute 
'__dataclass_fields__'


/usr/lib/python3.10/dataclasses.py:1197: AttributeError

During handling of the above exception, another exception occurred:

clazz = .new_type at 0x7f0b19be1990>
base_schema = None
clazz_frame = '/tmp/autopkgtest-lxc.c9zyolii/downtmp/autopkgtest_tmp/tests/test_class_schema.py', 
line 319, code test_validator_stacking>


@lru_cache(maxsize=MAX_CLASS_SCHEMA_CACHE_SIZE)
def _internal_class_schema(
clazz: type,
base_schema: Optional[Type[marshmallow.Schema]] = None,
clazz_frame: types.FrameType = None,
) -> Type[marshmallow.Schema]:
_RECURSION_GUARD.seen_classes[clazz] = clazz.__name__
try:
# noinspection PyDataclass

  fields: Tuple[dataclasses.Field, ...] = dataclasses.fields(clazz)


/usr/lib/python3/dist-packages/marshmallow_dataclass/__init__.py:370: _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _

class_or_instance = .new_type at 0x7f0b19be1990>

def fields(class_or_instance):
"""Return a tuple describing the fields of this dataclass.
Accepts a dataclass or an instance of one. Tuple elements 
are of

type Field.
"""
# Might it be worth caching this, per class?
try:
fields = getattr(class_or_instance, _FIELDS)
except AttributeError:

  raise TypeError('must be called with a dataclass type or instance')

E   TypeError: must be called with a dataclass type or instance

/usr/lib/python3.10/dataclasses.py:1199: TypeError

During handling of the above exception, another exception occurred:

clazz = .new_type at 0x7f0b19be1990>
base_schema = None
clazz_frame = '/tmp/autopkgtest-lxc.c9zyolii/downtmp/autopkgtest_tmp/tests/test_class_schema.py', 
line 319, code test_validator_stacking>


@lru_cache(maxsize=MAX_CLASS_SCHEMA_CACHE_SIZE)
def _internal_class_schema(
clazz: type,
base_schema: Optional[Type[marshmallow.Schema]] = None,
clazz_frame: types.FrameType = None,
) -> Type[marshmallow.Schema]:
_RECURSION_GUARD.seen_classes[clazz] = clazz.__name__
try:
# noinspection PyDataclass
fields: Tuple[dataclasses.Field, ...] = 
dataclasses.fields(clazz)

except TypeError:  # Not a dataclass
try:
warnings.warn(
"** WARNING ** "
f"marshmallow_dataclass was called on the class 
{clazz}, which is not a dataclass. "
"It is going to try and convert the class into a 
dataclass, which may have "
"undesirable side effects. To avoid this message, 
make sure all your classes and "
"all the classes of their fields are either 
explicitly supported by "
"marshmallow_dataclass, or define the schema 
explicitly using "

Bug#1019390: o2: autopkgtest regression on i386 and s390x: Assertion `arg->v.vf[i] == 123.456F + i' failed.

[Paul Gevers]

Source: o2
Version: 1.1~ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of o2 the autopkgtest of o2 fails in testing on 
i386 and s390x when that autopkgtest is run with the binary packages of 
o2 from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
o2 from testing1.1~ds-1
all others from testingfrom testing

I copied some of the output on i386 at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=o2

https://ci.debian.net/data/autopkgtest/testing/i386/o/o2/24929151/log.gz

make: Entering directory 
'/tmp/autopkgtest-lxc.xo3rn8r3/downtmp/build.74d/src/debian/tests'

./arraytest
DONE sending [3456]
DONE sending []
DONE sending [123, 234]
DONE sending [xixdx] messages
DONE sending 456,[456,12345][1234.56,1234.567,2345.678],1234.567
arraytest: ../../test/arraytest.c:502: service_ifvxif: Assertion 
`arg->v.vf[i] == 123.456F + i' failed.

make: *** [Makefile:64: arraytest.test] Aborted
make: Leaving directory 
'/tmp/autopkgtest-lxc.xo3rn8r3/downtmp/build.74d/src/debian/tests'

autopkgtest [19:16:11]: test simple_run



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019147: systemd-container: Trying to use a bookworm chroot with a buster host fails / Failed to create /init.scope control group

[Michael Biebl]

Am 04.09.22 um 18:40 schrieb Bernhard Übelacker:


Package: systemd-container
Severity: wishlist
X-Debbugs-Cc: bernha...@mailbox.org


Dear Maintainer,
I tried to run on top of a buster system
with systemd-container 241-7~deb10u8 to start a container
with a current bookworm chroot with systemd-container 251.4-3.
This buster system was running linux-image 4.19.0-21-amd64.

This failed with following error:

     root@debian:~# systemd-nspawn 
--directory=/var/lib/machines/test-bookworm --boot --network-veth

     Spawning container test-bookworm on /var/lib/machines/test-bookworm.
     Press ^] three times within 1s to kill container.
     systemd 251.4-3 running in system mode (+PAM +AUDIT +SELINUX 
+APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID 
+CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK 
+PCRE2 -PWQUALITY -P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD 
-BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)

     Detected virtualization systemd-nspawn.
     Detected architecture x86-64.

     Welcome to Debian GNU/Linux bookworm/sid!

     Hostname set to .
     Failed to create /init.scope control group: Operation not permitted
     Failed to allocate manager object: Operation not permitted
     [!!] Failed to allocate manager object.
     Exiting PID 1...
     Container test-bookworm failed with error code 255.


So this report is mostly to ask if this expected or desired to work?


Good question. Maybe raise that on the systemd-devel mailing list?
Keep in mind, that in bullseye we switched to cgroupv2, i.e. we build 
systemd with -Ddefault-hierarchy=unified


I'm honestly not sure which combination of versions (and cgroup layouts) 
are supported.


Michael



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1015995: gpgme1.0 FTBFS with 3.10 as only supported Python3 version

[Gianfranco Costamagna]

Hello, indeed! thanks for fixing it up!

G.






Il martedì 6 settembre 2022 21:18:09 CEST, Paul Gevers  ha 
scritto: 





Hi Alexandre,

On Mon, 25 Jul 2022 10:03:04 +0200 Gianfranco Costamagna 
 wrote:
> Hello, looks like Ubuntu already has a patch for this:
> http://launchpadlibrarian.net/594282639/gpgme1.0_1.16.0-1.2ubuntu3_1.16.0-1.2ubuntu4.diff.gz


I was about to upload an NMU gpgme with your patch applied, but it looks 
wrong to me. If I understand the patch correctly (make isn't my 
strongest point), it will just run the test with the last PYTHON in 
PYTHONS. Why was the test not put inside the do-done block?

--- a/lang/python/tests/Makefile.am
+++ b/lang/python/tests/Makefile.am
@@ -70,7 +70,8 @@ check: xcheck
  .PHONY: xcheck

  xcheck:    all
-    $(TESTS_ENVIRONMENT) $(PYTHON) $(srcdir)/run-tests.py \
+    for PYTHON in $(PYTHONS); do true; done; \
+    $(TESTS_ENVIRONMENT) $$PYTHON $(srcdir)/run-tests.py \
        --interpreters="$(PYTHONS)" --srcdir=$(srcdir) $(TESTFLAGS) \
        $(XTESTS)

Paul

Bug#1019389: python-dateutil: no Homepage field

[Jakub Wilk]

Source: python-dateutil
Version: 2.8.1-6
Severity: wishlist

Please add

  Homepage: https://github.com/dateutil/dateutil

to debian/control.

--
Jakub Wilk

Bug#884075: [Bug regex/11053] Wrong results with backreferences

[Vincent Lefevre]

Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=29560

On 2022-09-05 19:37:18 -0500, Paul Eggert wrote:
> It looks like my comment
>  was incorrect,
> in that the two bugs are different bugs. glibc bug 11053 is fixed, but
> Debian bug 884075 is not fixed. Perhaps a better match for Debian bug 884075
> is glibc bug 10844.

Bug 10844 actually seems to be a different bug.
I've reported bug 29560 upstream concerning 1.

So there are 3 upstream bugs concerning bad results with backreferences
(but the regexp's are rather different is each case):

  https://sourceware.org/bugzilla/show_bug.cgi?id=10844
(ab*){1,9}\1

  https://sourceware.org/bugzilla/show_bug.cgi?id=17356
(.{0,1})(.{0,1})(.{0,1})\3\2\1

  https://sourceware.org/bugzilla/show_bug.cgi?id=29560
^(11+)\1+$|^1?$

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

Bug#1018883: NMU for clamtk for Nautilus 43 transition

[Jeremy Bicha]

To allow clamtk-gnome to continue working after the Nautilus 43
transition which will begin soon, I am uploading an NMU with a delay
of 5 days to fix this bug. Please let me know if I should speed up or
slow down this upload.

The NMU contains these 2 merge proposals:
https://salsa.debian.org/clamav-team/clamtk/-/merge_requests/1
https://salsa.debian.org/clamav-team/clamtk/-/merge_requests/2

Thank you,
Jeremy Bicha

Bug#1019388: apt-clone: Fails to run - no /usr/bin/dpkg-repack found

[Rann Bar-On]

Package: apt-clone
Version: 0.4.3+nmu1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: baronr...@gmail.com

Dear Maintainer,

Traceback (most recent call last):
  File "/usr/bin/apt-clone", line 107, in 
clone.save_state(args.source, args.destination,
  File "/usr/lib/python3/dist-packages/apt_clone.py", line 158, in save_state
self._dpkg_repack(tar)
  File "/usr/lib/python3/dist-packages/apt_clone.py", line 300, in _dpkg_repack
self.commands.repack_deb(pkgname, tdir)
  File "/usr/lib/python3/dist-packages/apt_clone.py", line 64, in repack_deb
raise IOError("no '%s' found" % self.dpkg_repack)
OSError: no '/usr/bin/dpkg-repack' found
E: Problem executing scripts DPkg::Post-Invoke 

Did dpkg-repack disappear with some recent update?

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

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

Versions of packages apt-clone depends on:
ii  lsb-release  11.2
ii  python3  3.10.6-1
ii  python3-apt  2.3.0+b2

Versions of packages apt-clone recommends:
pn  dpkg-repack  

apt-clone suggests no packages.

-- no debconf information

Bug#1019387: ITP: atomes -- an atomistic tool box

[Sébastien Le Roux]

Package: wnpp
Severity: wishlist
Owner: Sébastien Le Roux 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: atomes
  Version : 1.1.0
  Upstream Author : Sébastien Le Roux 
* URL : https://atomes.ipcms.fr/
* License : AfferoGPLv3+
  Programming Lang: C, Fortran90, GLSL
  Description : an atomistic tool box

Atomes is a cross-platform program developed around 3 main research
ideas: analyze, visualize, and edit/create 3D atomistic models.
Atomes offers a workspace that allows to have many projects opened 
simultaneously. 
The different projects in the workspace can exchange data: analysis results, 
atomic coordinates ...
By regrouping advanced analysis techniques, 3D visualization and 3D edition 
Atomes 
introduces innovative 3D rendering possibilities and intuitive utilizations of 
the calculation results.
Atomes also provides an advanced input preparation system 
for calculations using well known molecular dynamics codes:
  Classical MD : DL-POLY [1] and LAMMPS [2]
  ab-initio MD : CPMD [3] and CP2K [4]
  QM-MM MD : CPMD [3] and CP2K [4]
To prepare the input files for these calculations is likely to be the key, 
and most complicated step towards MD simulations. Atomes offers a user-friendly 
assistant 
to help and guide the user step by step to achieve this crucial step.

Among the many reasons I could think of, to help you understand why you
should consider Atomes seriously, I will pick 3: 

1) Atomes offers various physico-chemical analysis tools for 3D atomistic
models, to my knowledge there is no software packaged by Debian that
provides these kind of tools. Atomes also offers a complete graph
edition system, so that calculations results are analyzed, prepared for 
publication, within the software it-self.  
These calculations are parallelized in OpenMP. 

2) Atomes is designed to handle millions of atoms large systems, 
this is true for both the calculation and the visualization parts of the
program. I invite the reviewer of this ITP to compare Atomes
performances, to open and visualize large CIF file [5] or large PDB file [6] 
with other softwares packaged for Debian, like avogadro [7] or GChem3D [8]

3) Atomes provided several tools to build 3D atomistic models and 
design materials: advanced crystal builder, surface creation and
passivation ... these tools and are usually found only in commercial softwares,
and simply did not have counterparts in the open source community before Atomes.

For the time being I am the sole developer/maintener of Atomes, 
and I spend a significant part of my professional time to do so. 

Sources are hosted on Github:

Atomes sources:  https://github.com/Slookeur/Atomes
Atomes DEB sources:  https://github.com/Slookeur/Atomes-deb-build

Yes I am looking for a sponsor, this is my first Debian package, 
so I am actually looking for all the help I can get. 
I am willing to spend time to learn how to do things properly 
to get Atomes approved by the Debian community and ultimately packaged. 
If the proper way to do that is inside a packaging team then I think
the "Debian Scientific Computing Team" is likely to be the most
appropriate place to start.

I am looking forward to your reply and advise. 

Best regards.

Sébastien Le Roux

References:

[1]"https://www.scd.stfc.ac.uk/Pages/DL_POLY.aspx; 
[2]"https://lammps.sandia.gov; 
[3]"http://www.cpmd.org; 
[4]"http://cp2k.berlios.de;
[5]"https://www.rcsb.org/structure/3j3q;
[6]"https://www.rcsb.org/structure/2OGM;
[7]"https://avogadro.cc;
[8]"https://gchemutils.nongnu.org/gchem3d.html;

Bug#1016538: systemd-boot: Kernel postinst and initramfs post-update hooks copy initrd twice

[Fouad FAKIH]

#1014455 talks about running the scripts twice.

The initrd copied twice is caused by /etc/initramfs/post-
update.d/systemd-boot which calls kernel-install with initrd optional
parameter.

This leads to having the initrd copied twice :

$kernel/initrd
$kernel/initrd-$version

But systemd entries are correctly configured using the last initrd
copied.

Changing the kernel-install call in /etc/initramfs/post-
update.d/systemd-boot from :

kernel-install add "$1" "/boot/vmlinuz-$1" "$2"

To :

kernel-install add "$1" "/boot/vmlinuz-$1"

Solves the issue for me.

Bug#1019359: p.qa.d.o: bugs info not updated (+first analysis)

[Paul Wise]

On Wed, 07 Sep 2022 22:18:37 +0200 Thorsten Glaser wrote:

> Perhaps www/bin/other_to_xml.py throws errors?

There aren't any errors visible in cron AFAICT.

PS: as mentioned before, the PTS is essentially abandoned.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1018957: mmdebstrap fails in proot mode

[Johannes Schauer Marin Rodrigues]

Hi Christoph,

Quoting Christoph Groth (2022-09-08 10:13:04)
> Johannes Schauer Marin Rodrigues wrote:
> 
> > Thank you, your input was very valuable because proot was essentially
> > broken since 16 August 2021 and I was waiting for somebody to tell me
> > that they are a proot user and why they need it. You are a proot user
> > but it seems that creating the chroot in fakechroot mode instead of
> > proot still lets you do what you need. Now I guess I can remove it for
> > good.
> 
> With mmdebstrap 0.7.5-2.2 on my Debian stable install, so far I can
> still run for example
> 
>   mmdebstrap --mode=proot --include=hello testing /tmp/proot
> 
> This ends with the error message that prompted our previous discussion.
> 
> The created chroot is usable with proot, however the package “hello” is
> NOT available inside (perhaps due to the error during chroot creation).
> But I can install it with apt.
> 
> So far nothing new.  But when I try (as I believe you suggest), to
> execute the following command:
> 
>   mmdebstrap --mode=fakechroot --include=hello testing /tmp/fakechroot
> 
> I obtain an error that includes a segmentation fault (see below for the
> full output).  Am I doing anything wrong?  But, I guess, even if I am,
> the above command should not result in a segfault.

There are two problems. One problem is written in the log you pasted:

> I: extracting archives...
> done
> /usr/sbin/chroot.fakechroot: line 105: 18113 Segmentation fault env -u
> FAKECHROOT_BASE_ORIG FAKECHROOT_CMD_ORIG=
> LD_LIBRARY_PATH="$fakechroot_chroot_paths"
> FAKECHROOT_BASE="$fakechroot_chroot_base" "$fakechroot_chroot_chroot"
> "${@:1:$(($fakechroot_chroot_n - 1))}"
> "${fakechroot_chroot_newroot#$FAKECHROOT_BASE_ORIG}"
> "${@:$(($fakechroot_chroot_n + 1))}"
> I: the /bin/mv binary inside the chroot doesn't work under fakechroot
> I: with certain versions of coreutils and glibc, this is due to missing 
> support
> for renameat2 in fakechroot
> I: see https://github.com/dex4er/fakechroot/issues/60
> I: expect package post installation scripts not to work


This is a bug that is solved in the next Debian release. Nothing you can do
about it if you are using stable only.

The other problem is, that you are trying to create a testing chroot from
stable. The fakechroot mode has the limitation that the C-libraries of the
system on the outside and the system on the inside have to be quite similar. A
few weeks ago, a new glibc upload happened to unstable and since migrated to
testing. Since that upload, it became impossible to create a testing chroot
with fakechroot from stable. This is not the fault of mmdebstrap but a
fundamental problem with how fakechroot works and is also documented in the man
page of fakechroot in the section "LIMITATIONS".

So how do you fix that? We come back to what I said a few emails back.
Directories are a really bad way to work with chroots. Tarballs are much
better. So how about you just run this:

$ mmdebstrap --include=hello testing /tmp/fakechroot.tar

This will probably choose the "unshare" mode on your system. Since you are not
building a directory tree but a tarball, the ownership information in that
tarball will be correct. If you want to use proot with it, then you do not care
about ownership information so you can just extract it as your normal user and
are left with the chroot directory you want.

But why do I need a temporary file you say? You do not if you don't want to.
You can also run this:

$ mmdebstrap --include=hello testing - | tar -C /tmp/fakechroot -x

This will make mmdebstrap write the tarball to standard output (so no temporary
files) and tar will immediately extract that tarball to the directory you pass
with the -C option.

Does that work for you?

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1010968: C-Kermit issue

[David Goodwin]

This problem is likely caused by a lack of support for anything newer than
TLS 1.0 in C-Kermit regardless of which version of OpenSSL it's built with.

I've fixed this in C-Kermit for Windows which connects to telnetd-ssl in
sid just fine negotiating a TLS 1.3 connection. I expect this change, along
with SSL improvements from some other people, will appear in
C-Kermit 10.0 beta.05 at some point.

Bug#1017609: ruby-terser: Test fails with node-terser >= 5

[Yadd]

On 07/09/2022 19:49, Mohd Bilal wrote:

On 9/7/22 14:11, Yadd wrote:

Can I push an NMU upload to unblock node-terser migration or can a 
Ruby-Team member push that ?


Hi,

Thanks for the patch :) . I've uploaded ruby-terser 1.1.12+dfsg-1 (the 
patch works with the latest version only) to unstable now. Hopefully 
this clears way for migration of node-terser.


Thanks


Looking at tracker.d.o, all seems OK now. Thanks a lot !

Bug#1019385: swisswatch: add command-line parameter to display arbitrary time

[Axel Stammler]

Package: swisswatch
Version: 0.6-18+b1
Severity: wishlist
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

it might be a good idea to make the frontend (i.e., the clockface and hands) 
available via
the command line so that the usual backend (i.e., the system clock) can be 
replaced by an
alternative time source, e.g. a manual setting like ”--time 11.35.55”

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

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

Versions of packages swisswatch depends on:
ii  libc6 2.31-13+deb11u3
ii  libx11-6  2:1.7.2-1
ii  libxext6  2:1.3.3-1.1
ii  libxmu6   2:1.1.2-2+b3
ii  libxt61:1.2.0-1

swisswatch recommends no packages.

swisswatch suggests no packages.

-- debconf-show failed

Bug#1019384: scikit-learn: ppc64el fails tolerance in test_mlp with scipy 1.8

[Drew Parsons]

Source: scikit-learn
Version: 1.1.2+dfsg-5
Severity: normal

scikit-learn fails debci tests when running with scipy 1.8.

The failing test is test_mlp_regressor_dtypes_casting in test_mlp.py

It's not a "large" failure, just that the tolerance rtol=0.0001 is not
met by a small amount. rtol=0.0002 would pass.

The error message is

__ test_mlp_regressor_dtypes_casting ___

def test_mlp_regressor_dtypes_casting():
mlp_64 = MLPRegressor(
alpha=1e-5, hidden_layer_sizes=(5, 3), random_state=1, max_iter=50
)
mlp_64.fit(X_digits[:300], y_digits[:300])
pred_64 = mlp_64.predict(X_digits[300:])

mlp_32 = MLPRegressor(
alpha=1e-5, hidden_layer_sizes=(5, 3), random_state=1, max_iter=50
)
mlp_32.fit(X_digits[:300].astype(np.float32), y_digits[:300])
pred_32 = mlp_32.predict(X_digits[300:].astype(np.float32))

>   assert_allclose(pred_64, pred_32, rtol=1e-04)
E   AssertionError: 
E   Not equal to tolerance rtol=0.0001, atol=0
E   
E   Mismatched elements: 1 / 60 (1.67%)
E   Max absolute difference: 1.77346709e-06
E   Max relative difference: 0.0001
Ex: array([-1.624248e-02,  2.327707e+00,  6.674963e-01,  4.904700e-01,
E   6.739288e-01,  3.166697e+00,  4.548126e-01,  6.674963e-01,
E  -3.220949e-02, -6.899952e-01,  6.674963e-01, -6.329127e-01,...
Ey: array([-1.624250e-02,  2.327706e+00,  6.674960e-01,  4.904711e-01,
E   6.739284e-01,  3.166698e+00,  4.548138e-01,  6.674960e-01,
E  -3.220773e-02, -6.899955e-01,  6.674960e-01, -6.329128e-01,...

/usr/lib/python3/dist-packages/sklearn/neural_network/tests/test_mlp.py:872: 
AssertionError

Bug#1019383: ITP: node-cjs-module-lexer -- Fast lexer to extract named exports from CommonJS modules

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: node-cjs-module-lexer
  Version : 1.2.2
  Upstream Author : Guy Bedford
* URL : https://github.com/nodejs/cjs-module-lexer#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Fast lexer to extract named exports from CommonJS modules

 Very fast JavaScript CommonJS module syntax lexer used to detect
 the most likely list of named exports of a CommonJS module.
 .
 It is used by Node.js for CommonJS and ES Modules interoperability.
 .
 Node.js is an event-based server-side JavaScript engine.

For now nodejs and jest both have a bundled copy of it, and both don't
generate the wasm build, so this package is meant to fix that.

It also makes it cleaner for nodejs internal modules to be externalized.

It is stable, and I intend to maintain this package along with nodejs
in pkg-javascript team.

Bug#1019382: gnome-online-accounts: please make the build reproducible

[Chris Lamb]

Source: gnome-online-accounts
Version: 3.45.2-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpaths
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
gnome-online-accounts could not be built reproducibly.

This is because it uses @filename@ when generating .h files instead
of @basename@.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible-build.patch   2022-09-08 09:58:17.430979484 
+0100
@@ -0,0 +1,72 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2022-09-08
+
+--- gnome-online-accounts-3.45.2.orig/src/goa/goaenumtypes.c.template
 gnome-online-accounts-3.45.2/src/goa/goaenumtypes.c.template
+@@ -5,7 +5,7 @@
+ /*** END file-header ***/
+ 
+ /*** BEGIN file-production ***/
+-/* enumerations from "@filename@" */
++/* enumerations from "@basename@" */
+ /*** END file-production ***/
+ 
+ /*** BEGIN value-header ***/
+--- gnome-online-accounts-3.45.2.orig/src/goa/goaenumtypes.h.template
 gnome-online-accounts-3.45.2/src/goa/goaenumtypes.h.template
+@@ -9,7 +9,7 @@ G_BEGIN_DECLS
+ 
+ /*** BEGIN file-production ***/
+ 
+-/* enumerations from "@filename@" */
++/* enumerations from "@basename@" */
+ /*** END file-production ***/
+ 
+ /*** BEGIN value-header ***/
+--- 
gnome-online-accounts-3.45.2.orig/src/goabackend/goabackendenumtypes.c.template
 gnome-online-accounts-3.45.2/src/goabackend/goabackendenumtypes.c.template
+@@ -5,7 +5,7 @@
+ /*** END file-header ***/
+ 
+ /*** BEGIN file-production ***/
+-/* enumerations from "@filename@" */
++/* enumerations from "@basename@" */
+ /*** END file-production ***/
+ 
+ /*** BEGIN value-header ***/
+--- 
gnome-online-accounts-3.45.2.orig/src/goabackend/goabackendenumtypes.h.template
 gnome-online-accounts-3.45.2/src/goabackend/goabackendenumtypes.h.template
+@@ -9,7 +9,7 @@ G_BEGIN_DECLS
+ 
+ /*** BEGIN file-production ***/
+ 
+-/* enumerations from "@filename@" */
++/* enumerations from "@basename@" */
+ /*** END file-production ***/
+ 
+ /*** BEGIN value-header ***/
+--- gnome-online-accounts-3.45.2.orig/src/goaidentity/goaidentityenumtypes.c.in
 gnome-online-accounts-3.45.2/src/goaidentity/goaidentityenumtypes.c.in
+@@ -5,8 +5,8 @@
+ /*** END file-header ***/
+ 
+ /*** BEGIN file-production ***/
+-#include "@filename@"
+-/* enumerations from "@filename@" */
++#include "@basename@"
++/* enumerations from "@basename@" */
+ /*** END file-production ***/
+ 
+ /*** BEGIN value-header ***/
+--- gnome-online-accounts-3.45.2.orig/src/goaidentity/goaidentityenumtypes.h.in
 gnome-online-accounts-3.45.2/src/goaidentity/goaidentityenumtypes.h.in
+@@ -9,7 +9,7 @@ G_BEGIN_DECLS
+ 
+ /*** BEGIN file-production ***/
+ 
+-/* enumerations from "@filename@" */
++/* enumerations from "@basename@" */
+ /*** END file-production ***/
+ 
+ /*** BEGIN value-header ***/
--- a/debian/patches/series 2022-09-08 09:38:17.682223220 +0100
--- b/debian/patches/series 2022-09-08 09:58:15.454973116 +0100
@@ -0,0 +1 @@
+reproducible-build.patch

Bug#1019381: ITP: phosh-tour -- A short introduction to phosh on smartphones

[Guido Günther]

Package: wnpp
Severity: wishlist
Owner: Guido Günther 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: phosh-tour
  Version : 0.21.0
  Upstream Author : Sam Sam Hewitt , Guido Günther 

* URL : https://www.example.org/
* License : GPL
  Programming Lang: C
  Description : A short introduction to phosh on smartphones

Phosh tour gives a short visual introduction on how to use phosh on a
smartphone explaining the available gestures for navigation, quick
settings, etc.

Bug#1019380: UDD: import ports.d.o data to ports tables instead of derivatives tables

[Paul Wise]

Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: udd
X-Debbugs-CC: John Paul Adrian Glaubitz , Aurelien Jarno 


Currently the unofficial Debian ports archive is imported in UDD tables
named 'derivatives', but these days it is more of a Debian subproject.

The 'derivatives' table also receives (or did in the past) data from
aptosid and skolelinux, which are/were both derivatives of Debian.

Therefore, I would like ports data to be imported into 'ports' tables
instead and make the new ports table available to the UDD madison cgi
and then add the ports UDD madison cgi to the default rmadison URL map.

https://qa.debian.org/cgi-bin/madison.cgi?table=derivatives

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1018957: mmdebstrap fails in proot mode

[Christoph Groth]

Johannes Schauer Marin Rodrigues wrote:

> Thank you, your input was very valuable because proot was essentially
> broken since 16 August 2021 and I was waiting for somebody to tell me
> that they are a proot user and why they need it. You are a proot user
> but it seems that creating the chroot in fakechroot mode instead of
> proot still lets you do what you need. Now I guess I can remove it for
> good.

With mmdebstrap 0.7.5-2.2 on my Debian stable install, so far I can
still run for example

  mmdebstrap --mode=proot --include=hello testing /tmp/proot

This ends with the error message that prompted our previous discussion.

The created chroot is usable with proot, however the package “hello” is
NOT available inside (perhaps due to the error during chroot creation).
But I can install it with apt.

So far nothing new.  But when I try (as I believe you suggest), to
execute the following command:

  mmdebstrap --mode=fakechroot --include=hello testing /tmp/fakechroot

I obtain an error that includes a segmentation fault (see below for the
full output).  Am I doing anything wrong?  But, I guess, even if I am,
the above command should not result in a segfault.

Thanks
Christoph

 8< 
I: chroot architecture amd64 is equal to the host's architecture
I: automatically chosen format: directory
I: running apt-get update...
done
I: downloading packages with apt...
done
I: extracting archives...
done
/usr/sbin/chroot.fakechroot: line 105: 18113 Segmentation fault env -u
FAKECHROOT_BASE_ORIG FAKECHROOT_CMD_ORIG=
LD_LIBRARY_PATH="$fakechroot_chroot_paths"
FAKECHROOT_BASE="$fakechroot_chroot_base" "$fakechroot_chroot_chroot"
"${@:1:$(($fakechroot_chroot_n - 1))}"
"${fakechroot_chroot_newroot#$FAKECHROOT_BASE_ORIG}"
"${@:$(($fakechroot_chroot_n + 1))}"
I: the /bin/mv binary inside the chroot doesn't work under fakechroot
I: with certain versions of coreutils and glibc, this is due to missing support
for renameat2 in fakechroot
I: see https://github.com/dex4er/fakechroot/issues/60
I: expect package post installation scripts not to work
I: installing essential packages...
done
/usr/sbin/chroot.fakechroot: line 105: 18134 Segmentation fault env -u
FAKECHROOT_BASE_ORIG FAKECHROOT_CMD_ORIG=
LD_LIBRARY_PATH="$fakechroot_chroot_paths"
FAKECHROOT_BASE="$fakechroot_chroot_base" "$fakechroot_chroot_chroot"
"${@:1:$(($fakechroot_chroot_n - 1))}"
"${fakechroot_chroot_newroot#$FAKECHROOT_BASE_ORIG}"
"${@:$(($fakechroot_chroot_n + 1))}"
E: run_chroot failed: E: env --unset=APT_CONFIG --unset=TMPDIR /usr/sbin/chroot
/tmp/fakechroot dpkg --install --force-depends --status-fd=<$fd>
/var/cache/apt/archives//base-files_12.2_amd64.deb
/var/cache/apt/archives//base-passwd_3.6.0_amd64.deb
/var/cache/apt/archives//bash_5.2~rc2-2_amd64.deb
/var/cache/apt/archives//bsdutils_1%3a2.38.1-1_amd64.deb
/var/cache/apt/archives//coreutils_8.32-4.1_amd64.deb
/var/cache/apt/archives//dash_0.5.11+git20210903+057cd650a4ed-9_amd64.deb
/var/cache/apt/archives//debconf_1.5.79_all.deb
/var/cache/apt/archives//debianutils_5.7-0.3_amd64.deb
/var/cache/apt/archives//diffutils_1%3a3.8-1_amd64.deb
/var/cache/apt/archives//dpkg_1.21.9_amd64.deb
/var/cache/apt/archives//findutils_4.9.0-3_amd64.deb
/var/cache/apt/archives//gcc-12-base_12.2.0-1_amd64.deb
/var/cache/apt/archives//grep_3.7-1_amd64.deb
/var/cache/apt/archives//gzip_1.12-1_amd64.deb
/var/cache/apt/archives//hostname_3.23_amd64.deb
/var/cache/apt/archives//init-system-helpers_1.64_all.deb
/var/cache/apt/archives//libacl1_2.3.1-1_amd64.deb
/var/cache/apt/archives//libattr1_1%3a2.5.1-1_amd64.deb
/var/cache/apt/archives//libaudit-common_1%3a3.0.7-1_all.deb
/var/cache/apt/archives//libaudit1_1%3a3.0.7-1+b1_amd64.deb
/var/cache/apt/archives//libblkid1_2.38.1-1_amd64.deb
/var/cache/apt/archives//libbz2-1.0_1.0.8-5_amd64.deb
/var/cache/apt/archives//libc-bin_2.34-7_amd64.deb
/var/cache/apt/archives//libc6_2.34-7_amd64.deb
/var/cache/apt/archives//libcap-ng0_0.8.3-1+b1_amd64.deb
/var/cache/apt/archives//libcap2_1%3a2.44-1_amd64.deb
/var/cache/apt/archives//libcrypt1_1%3a4.4.28-2_amd64.deb
/var/cache/apt/archives//libdb5.3_5.3.28+dfsg1-0.10_amd64.deb
/var/cache/apt/archives//libdebconfclient0_0.264_amd64.deb
/var/cache/apt/archives//libgcc-s1_12.2.0-1_amd64.deb
/var/cache/apt/archives//libgcrypt20_1.10.1-2_amd64.deb
/var/cache/apt/archives//libgmp10_2%3a6.2.1+dfsg1-1_amd64.deb
/var/cache/apt/archives//libgpg-error0_1.45-2_amd64.deb
/var/cache/apt/archives//liblz4-1_1.9.4-1_amd64.deb
/var/cache/apt/archives//liblzma5_5.2.5-2.1_amd64.deb
/var/cache/apt/archives//libmount1_2.38.1-1_amd64.deb
/var/cache/apt/archives//libpam-modules-bin_1.5.2-2_amd64.deb
/var/cache/apt/archives//libpam-modules_1.5.2-2_amd64.deb
/var/cache/apt/archives//libpam-runtime_1.5.2-2_all.deb
/var/cache/apt/archives//libpam0g_1.5.2-2_amd64.deb
/var/cache/apt/archives//libpcre2-8-0_10.40-1_amd64.deb
/var/cache/apt/archives//libpcre3_2%3a8.39-14_amd64.deb
/var/cache/apt/archives//libselinux1_3.4-1+b1_amd64.deb

Bug#1016084: transition: petsc

[Sebastian Ramacher]

On 2022-09-04 10:02:53 +0200, Drew Parsons wrote:
> All uploads are done now.  Let the binNMUs rip.

The rebuilds have been done. The transition is now blocked on #1019287.

Cheers
-- 
Sebastian Ramacher

Bug#1004027: Acknowledgement (aunpack should support unrar command)

[VA]

Same thing about .7z archives: I have `7zip` and `p7zip` packages 
installed, which are fine for unpacking .7z archives, but aunpack 
refuses to unpack them because none of these 2 packages ship a 7z command.
They do ship 7zr and p7zip commands though, which are suitable for 
extracting .7z archives.

Bug#1019379: Align 0002-ffmpeg-5.0-1419.patch with upstream version?

[Petter Reinholdtsen]

Package: casparcg-server
Version: 2.3.3+dfsg-3
Severity: wishlist

The current edition of
0002-ffmpeg-5.0-1419.patch is slighlty different from the version that
went into the upstream git repository as
https://github.com/CasparCG/server/commit/6bb06aa7cb2c409dff4ba4978c979c29a09c8034
 >.
It might be a good idea to update it to match the upstream until a new
upstream release is made.

I believe a better approach is be to convince upstream to make a new
release, removing the need for this patch completely. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#893448: please add a chromium-source binary package

[Petter Reinholdtsen]

[Filip Hanes]
> Hi,
> I'm new maintainer of casparcg-server after pere.

And I am very happy to have a replacement who actually use the
package. :)  The package is also moved under the Debian Multimedia
umbrella, allowing more people to particiate. :)

>> 1) Chromium adds a chromium-source binary package, with the
>> understanding that whoever packages CEF will keep it out of stable
>
> Could we try this option 1) to make some progress at least in unstable
> and testing and later with more experience see if we can continue to
> other option?

I suggest you give it a go locally, and see if you can get it working,
as well as report your progress on #debian-multimedia, to see if others
can help. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#1018777: pari-nflistdata: Unhandled data compression by dh_compress

[Bill Allombert]

> Package: pari-nflistdata
> Version: 0.20220729-1
> Severity: important
> X-Debbugs-CC: ballo...@debian.org
> 
> Dear Debian pari-nflistdata package maintainer,
> 
> As seen in https://packages.debian.org/sid/all/pari-nflistdata/filelist ,
> some files are compressed into .gz file (QT --> QT.gz). I believe this is
> due to automatic compression made by dh_compress.
> 
> The unhandled compression may make these data unavailable if the
> uncompressed version were to be used. Please consider adjusting the
> compression handling in debian/rules file.

Dear Boyuan Yang,

Fundamentally I do not understand your sentence. 
What is "unhandled compression", what would the "uncompressed version" to be 
used ?
What is the actual problem you are reporting ?

I have uploaded pari 2.15.0~pre1 to experimental and it passes it test-suite, so
pari-nflistdata is read correctly.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#1019051: ffmpeg: Repackaging with pipewire: dpkg-shlibdeps: error: no dependency information found for libjack.so.0 used by libavdevice.so.59.7.100

[Sebastian Ramacher]

Control: reassign -1 pipewire-jack

On 2022-09-08 09:35:17 +0200, IOhannes m zmölnig (Debian GNU|Linux) wrote:
> On 9/7/22 21:11, Sebastian Ramacher wrote:
> > I cannot reproduce this issue when building ffmpeg in sbuild with
> > pipewire-jack installed. Are you sure that's the root cause of your
> > issue? Could you please provide a full log?
> 
> i think the issue is, that in many cases, you want pipewire to be a drop-in
> replacement for jack.
> so they follow instructions like [1], which effectively adds a new search
> path for the dynamic linker, which then confuses dpkg-shlibdeps
> 
> this (changing your ld.so.conf) is something you most likely did *not* do in
> your schroot, hence you didn't experience the problem.

In that case, let's reassign this to pipewire. In any case, it's a
non-serious issue since builds on the buildds or in sbuild/pbuilder do
the right thing.

Cheers
-- 
Sebastian Ramacher

Bug#1014567: Please ship instructions on how to use this package (and/or sysroot symlinks)

[Jérémy Lal]

Package: wasi-libc
Version: 0.0~git20220510.9886d3d-1
Followup-For: Bug #1014567

Hi, node-undici debian package compiles some code to wasm using wasi-libc.
You can look at the build log here: 
https://buildd.debian.org/status/package.php?p=node-undici

The relevant line is:
clang -nodefaultlibs --sysroot=/usr -target wasm32-unknown-wasi -Ofast 
-fno-exceptions -fvisibility=hidden -mexec-model=reactor -Wl,-lc 
-Wl,-error-limit=0 -Wl,-O3 -Wl,--lto-O3 -Wl,--strip-all -Wl,--allow-undefined 
-Wl,--export-dynamic -Wl,--export-table -Wl,--export=malloc -Wl,--export=free 
deps/llhttp/src/api.c deps/llhttp/src/http.c deps/llhttp/src/llhttp.c 
-Ideps/llhttp/include -o lib/llhttp/llhttp.wasm


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

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

-- no debconf information

Bug#881514: Take over maintainance

[Patrick Matthäi]

retitle 881516 ITA: xine-ui -- the xine video player, user interface
owner 881516 !
retitle 881514 ITA: xine-lib-1.2 -- xine video player library – documentation 
files
owner 881514 !
thanks

Hi,

I will take over the maintainance of both packages

Bug#1019204: ss command freeze and the process cannot be killed

[Stéphane Hoc]

I found the reason why this crash occurs, when IPv6 is disabled.
A fix would be appreciated.

Bug#983475: shim-signed-common: failure to install w/o SetVariable()

[Frieder Schrempf]

Hi,

Am 30.04.21 um 20:16 schrieb Heinrich Schuchardt:
> Am 30. April 2021 20:06:22 MESZ schrieb Steve McIntyre :
>> Control: reassign -1 grub2-common
>>
>> Hi Heinrich,
>>
>> [ reassigning to grub2-common, the package which includes grub-install
>> ]
>>
>> On Wed, Feb 24, 2021 at 09:08:15PM +0100, Heinrich Schuchardt wrote:
>>> Package: shim-signed-common
>>> Version: 1.33+15+1533136590.3beb971-7
>>> Severity: normal
>>>
>>> Dear Maintainer,
>>>
>>> on systems using U-Boot as firmware the UEFI runtime service
>>> SetVariable() is not available. Variable Boot has to be set
>> manually
>> >from the U-Boot console.
>>>
>>> The installation of shim-signed-common fails with:
>>>
>>> The following NEW packages will be installed:
>>>  shim-signed-common
>>> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
>>> Need to get 0 B/13.3 kB of archives.
>>> After this operation, 50.2 kB of additional disk space will be used.
>>> Preconfiguring packages ...
>>> Can't exec "/tmp/shim-signed-common.config.PoZZwF": Permission denied
>> at
>>> /usr/lib/aarch64-linux-gnu/perl-base/IPC/Open3.pm line 178.
>>> open2: exec of /tmp/shim-signed-common.config.PoZZwF configure 
>> failed:
>>> Permission denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
>>> Selecting previously unselected package shim-signed-common.
>>> (Reading database ... 149437 files and directories currently
>> installed.)
>>> Preparing to unpack
>>> .../shim-signed-common_1.33+15+1533136590.3beb971-7_all.deb ...
>>> Unpacking shim-signed-common (1.33+15+1533136590.3beb971-7) ...
>>> Setting up shim-signed-common (1.33+15+1533136590.3beb971-7) ...
>>> Installing for arm64-efi platform.
>>> grub-install: warning: Cannot set EFI variable Boot.
>>> grub-install: warning: efivarfs_set_variable: failed to create
>>> /sys/firmware/efi/efivars/Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c
>>> for writing: Read-only file system.
>>> grub-install: warning: _efi_set_variable_mode: ops->set_variable()
>>> failed: Read-only file system.
>>> grub-install: error: failed to register the EFI boot entry: Read-only
>>> file system.
>>> dpkg: error processing package shim-signed-common (--configure):
>>> installed shim-signed-common package post-installation script
>>> subprocess returned error exit status 1
>>> Errors were encountered while processing:
>>> shim-signed-common
>>>
>>> To make the package usable with U-Boot the installation should not
>> fail
>>> but complete with a warning.
>>
>> Apologies for not responding earlier...
>>
>> This is a complicated situation, and there is no single right answer
>> at the moment. On platforms where EFI variables are settable
>> (e.g. most x86 machines, arm64 server machines), we absolutely *must*
>> report failure to install boot variables - this will make the system
>> fail to boot after installation. But on other platforms (e.g. most
>> current U-Boot systems), we can't install variables and instead we'll
>> have to install to the removable media path. AFAIK the U-Boot
>> developers are trying to add support for setting EFI variables on many
>> of their platforms, so hopefully this problem will go away soon.
> 
> This will require OP-TEE and StandAloneMM. The problem will persist on most 
> boards
> 
>>
>> In the meantime, to do a better job we need a reliable way to detect
>> if the platform can't support writing of EFI variables. Suggestions
>> welcome. :-/
> 
> SetVariable() must return EFI_UNSUPPORTED in this case. With UEFI 2.8+ you 
> could also look at the EFI_RT_PROPERTIES_TABLE configuration table to 
> identify unsupported runtime services. But Linux will only provide access to 
> the table with CONFIG_EFI_TEST=y.
> 

Are there any news to this issue?

I stumbled upon this while trying to install Debian on an ARM64 device
(using U-Boot without OP-TEE) and the installer fails with the error above.

I also discovered, that installing Ubuntu on the same device works just
fine and doesn't show any issue like this.

It would be really great if we could solve this to allow Debian being
used on a whole lot of devices that seem to be affected by this.

Thanks for any help!
Frieder

Bug#1019378: ITP: rust-asn1 -- ASN.1 (DER) parser and writer for Rust

[Claudius Heine]

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

* Package name: rust-asn1
  Version : 0.12.1
  Upstream Author : Alex Gaynor 
* URL : https://github.com/alex/rust-asn1
* License : BSD-3-Clause
  Programming Lang: Rust
  Description : ASN.1 (DER) parser and writer for Rust

Rust library for parsing and generating ASN.1 data (DER only).

Dependency of python-cryptography 38.0.0.

Bug#1004832: ping qrpnxz, revival \o/

[Geert Stappers]

On Wed, Sep 07, 2022 at 04:54:26PM -0500, Russell Hernandez Ruiz wrote:
> I've got Salsa access now. I will push what I have in the next few
> days.

OK


> I'll check for newer versions, and add the bits necessary to
> allow the automatic checking of updates.

Also good.

Do known:
* That perfect is the enemy good.
* I'm fine with uploading the "what I have" version, letting that
  migrate to testing. And then uploading a newer version.
  So we can verify checking of updates.
* Not every message on this ITP needs to go to the BTS


Groeten
Geert Stappers

BTS  Bug Tracking System (for us 1004...@bugs.debian.org)
-- 
Silence is hard to parse

Bug#1019377: ERROR: cannot flip ro->rw with received_uuid set

[Boris Kolpackov]

Package: btrfs-progs
Version: 5.18.1-1

After upgrading from btrfs-progs 5.14.1-1 with Linux kernel 5.14.9 to
btrfs-progs 5.18.1-1 with Linux kernel 5.18.16 (from current testing)
I see the following new error when trying to clear the read-only
property of a freshly received snapshot:

btrfs property set -ts /btrfs/test/mysubvol ro false
ERROR: cannot flip ro->rw with received_uuid set, use force if you really want 
that

The subvolume is sent/received using the following command:

sudo btrfs send mysubvol | ssh user@host sudo btrfs receive /btrfs/test/

Adding the -f flag as suggested by the error message helps but it's not
clear what the implication of this are. I tried to search the internet
for this error but only found instances of others running into it with
no insight into what it means.

Bug#1019341: pulseaudio: Start of daemon fails

[Axel Dürrbaum]

Hello,

the problem is solved_

somehow the library libmp3lame0 was uninstalled during the update process yesterday 
(apt update && apt autoremove).

Or it was a missing depency from libsndfile1?

Now the daemon starts again!

Sincerly yours
Axel Dürrbaum

On Wed, 07 Sep 2022 16:26:54 +0200 =?utf-8?q?Axel_D=C3=BCrrbaum?= 
 wrote:

Package: pulseaudio
Version: 16.1+dfsg1-1
Severity: important

Dear Maintainer,

after the update today the pulseaudio daemon does not start anymore:

pulseaudio: symbol lookup error: /usr/lib/x86_64-linux-gnu/libsndfile.so.1:
undefined symbol: lame_encode_buffer_interleaved_int

That conserns the stable and the experimental version of pulseaudio.

Sincerely yours
Axel Dürrbaum


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


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

Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.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.129
ii  init-system-helpers 1.64
ii  libasound2  1.2.7.2-1
ii  libasound2-plugins  1.2.7.1-1
ii  libc6   2.34-7
ii  libcap2 1:2.44-1
ii  libdbus-1-3 1.14.0-2
ii  libfftw3-single33.3.8-2
ii  libgcc-s1   12.2.0-1
ii  libglib2.0-02.73.3-3
ii  libgstreamer-plugins-base1.0-0  1.20.3-2
ii  libgstreamer1.0-0   1.20.3-1
ii  libice6 2:1.0.10-1
ii  libltdl72.4.7-4
ii  liborc-0.4-01:0.4.32-2
ii  libpulse0   16.1+dfsg1-1
ii  libsm6  2:1.2.3-1
ii  libsndfile1 1.1.0-1
ii  libsoxr00.1.3-4
ii  libspeexdsp11.2.0-1
ii  libstdc++6  12.2.0-1
ii  libsystemd0 251.4-3
ii  libtdb1 1.4.6-3


--
Universität Kassel / FB 15 Maschinenbau / FG Mess- und Regelungstechnik
Mönchebergstrasse 7, 34109 Kassel
Tel: ++49 561 804 3261 / Raum 1713 Ingenieurwissenschaften IIIbegin:vcard
fn;quoted-printable:Axel D=C3=BCrrbaum
n;quoted-printable:D=C3=BCrrbaum;Axel
org;quoted-printable:Universit=C3=A4t Kassel;FB 15 Maschinenbau / FG Mess- und Regelungstechnik
adr;quoted-printable:Raum 1713;;M=C3=B6nchebergstrasse 7;Kassel;Hessen;34109;Deutschland
email;internet:axel.duerrb...@mrt.uni-kassel.de
title:Dipl-Ing.
tel;work:++49 561 804 3261
tel;fax:++49 561 804 2847
note;quoted-printable:PGP KeyID: 0x694BFDA0=0D=0A=
	PGP Fingerprint: 902B 49AA 4BEF 5DBB 0120 DC37 3A99 6EBD 694B FDA0=0D=0A=
	
x-mozilla-html:FALSE
url:http://www.uni-kassel.de/fb15/mrt/
version:2.1
end:vcard

Bug#1019376: python-tomlkit: New Upstream version

[Matthias Urlichs]

Source: python-tomlkit
Version: 0.6.0-2
Severity: minor
X-Debbugs-Cc: sm...@smurf.noris.de

Upstream has tagged 0.11.4 by now. Please update.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (720, 'testing'), (700, 'stable'), (600, 'oldstable'), (500, 
'stable-security'), (500, 'unstable'), (450, 'focal'), (350, 'oldoldstable'), 
(300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

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

Bug#1019375: Not started under wayland/plasma

[Didier 'OdyX' Raboud]

Package: unburden-home-dir
Version: 0.4.2
Severity: important

Hello Axel,

with KDE's Plasma under Wayland, unburden-home-dir isn't started at all,
although other XSession.d scripts are.

What am I doing wrong?

Best,
Didier

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

Kernel: Linux 5.19.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_CH:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages unburden-home-dir depends on:
ii  dpkg   1.21.9
ii  libconfig-file-perl1.54-1
ii  libfile-basedir-perl   0.09-1
ii  libfile-rsync-perl 0.49-2
ii  libfile-touch-perl 0.12-1
ii  libfile-which-perl 1.27-1
ii  libipc-run-perl20220807.0-1
ii  libstring-expand-perl  0.04-4
ii  libtry-tiny-perl   0.31-1
ii  perl   5.34.0-5

Versions of packages unburden-home-dir recommends:
ii  lsof4.95.0-1
ii  x11-common  1:7.7+23

Versions of packages unburden-home-dir suggests:
pn  agedu 
pn  autotrash 
pn  bleachbit 
pn  corekeeper
ii  eatmydata 130-2
pn  fslint
pn  ncdu | baobab | filelight | xdiskusage | xdu  
pn  tmpreaper 
pn  unburden-home-dir-doc 

-- Configuration Files:
/etc/default/unburden-home-dir changed:
UNBURDEN_HOME=true

/etc/unburden-home-dir.list changed:
m D .thumbnails thumbnails
m D .ccache ccache
m d .config/google-chrome/*/Thumbnails google-chrome-thumbnails-%1
m f .config/google-chrome/*/Thumbnails-journal 
google-chrome-thumbnails-journal-%1
m d .config/chromium/*/Thumbnails chromium-thumbnails-%1
m f .config/chromium/*/Thumbnails-journal chromium-thumbnails-journal-%1
m d .mozilla/default/*/Cache mozilla-default-cache-%1
m d .mozilla/default/*/startupCache mozilla-default-startup-cache-%1
m d .mozilla/firefox/*/Cache firefox-cache-%1
m d .mozilla/firefox/*/startupCache firefox-startup-cache-%1
m d .mozilla/firefox/*/Cache.Trash firefox-cache-trash-%1
m d .conkeror.mozdev.org/conkeror/*/Cache conkeror-cache-%1
m d .conkeror.mozdev.org/conkeror/*/startupCache conkeror-startup-cache-%1
m d .conkeror.mozdev.org/conkeror/*/Cache.Trash conkeror-cache-trash-%1
m d .kazehakase/mozilla/kazehakase/Cache kazehakase-cache
m d .galeon/mozilla/galeon/Cache galeon-cache
m d .gnome2/epiphany/mozilla/epiphany/Cache epiphany-cache
m d .xxxterm/cache xxxterm-cache
m d .forg/cache forg-cache
m d .opera/cache opera-cache
m d .opera/cache4 opera-cache4
m d .opera/opcache opera-opcache
m d .opera/cacheOp opera-cacheOp
m d .config/qupzilla/profiles/*/networkcache qupzilla-cache-%1
m d .thunderbird/*/Cache thunderbird-cache-%1
m d .mozilla-thunderbird/*/Cache debian-thunderbird-cache-%1
m d .icedove/*/Cache icedove-cache-%1
m d .buzzbird/*/Cache buzzbird-cache
m f .aptitude/cache aptitude-cache
m d .wesnoth*/cache wesnoth%1-cache
m d .gaia/cache gaia-cache
m d .googleearth/Cache google-earth-cache
m d .java/deployment/cache java-deployment-cache
m d .adobe/Acrobat/*/Cache adobe-acrobat-%1-cache
m d .shotwell/thumbs shotwell-thumbs
m D .sxiv sxiv-thumbs
m D .devscripts_cache devscripts_cache
r D .Trash trash
r D .local/Trash local-trash
r D Downloads downloads
r D Téléchargements downloads


-- no debconf information

Bug#1019374: Acknowledgement (deb-scrub-obsolete crashes with AttributeError)

[Marcin Owsiany]

I realized now this might be fixed already in
https://salsa.debian.org/jelmer/lintian-brush/-/commit/0812a32417e8f78278dc1f574c0e528919edc0db
but not rolled out yet?