Bug#1021906: kanboard FTBFS: Failed asserting that 3.3000000000000003 matches expected 3.3

[Adrian Bunk]

Source: kanboard
Version: 1.2.23+ds-1.1
Severity: serious
Tags: ftbfs patch fixed-upstream
Forwarded: https://github.com/kanboard/kanboard/pull/5078

https://buildd.debian.org/status/fetch.php?pkg=kanboard=all=1.2.23%2Bds-1.1=1665834979=0

...
There was 1 failure:

1) SubtaskTimeTrackingModelTest::testCalculateSubtaskTime
Total spent
Failed asserting that 3.3003 matches expected 3.3.

/<>/tests/units/Model/SubtaskTimeTrackingModelTest.php:186

FAILURES!
Tests: 1094, Assertions: 146248, Failures: 1, Warnings: 8.
make[1]: *** [debian/rules:40: override_dh_auto_test] Error 1

Bug#1021905: linux-image-6.0.0-trunk-amd64: fails to return from suspend

[Gabriel Francisco]

Package: linux-image-6.0.0-trunk-amd64
Version: 6.0-1~exp1
Severity: normal
X-Debbugs-Cc: frc.gabr...@gmail.com

Dear Maintainer,

when using linux-image-6.0.0-trunk-amd64 I noticed that my computer does
not return from suspend and checking the logs I found these lines:


Oct 15 15:30:20 computer kernel: [  209.936495] BUG: unable to handle page 
fault for address: 110e1680
Oct 15 15:30:20 computer kernel: [  209.936507] #PF: supervisor read access in 
kernel mode
Oct 15 15:30:20 computer kernel: [  209.936513] #PF: error_code(0x) - 
not-present page
Oct 15 15:30:20 computer kernel: [  209.936517] PGD 0 P4D 0
Oct 15 15:30:20 computer kernel: [  209.936521] Oops:  [#1] PREEMPT SMP 
NOPTI
Oct 15 15:30:20 computer kernel: [  209.936526] CPU: 12 PID: 1271 Comm: 
krfcommd Not tainted 6.0.0-trunk-amd64 #1  Debian 6.0-1~exp1
Oct 15 15:30:20 computer kernel: [  209.936532] Hardware name: LENOVO 
21A4GE/21A4GE, BIOS R1MET49W (1.19 ) 06/27/2022
Oct 15 15:30:20 computer kernel: [  209.936534] RIP: 
0010:hci_send_acl+0x21/0x2f0 [bluetooth]
Oct 15 15:30:20 computer kernel: [  209.936588] Code: cc cc 0f 1f 80 00 00 00 
00 0f 1f 44 00 00 41 57 49 89 ff 41 56 41 55 41 54 55 48 89 f5 53 48 83 ec 28 
4c 8b 67 18 89 54 24 0c <4d> 8b 8c 24 80 06 00 00 4c 89 4c 24 18 66 90 0f b7 da 
8b 4d 70 2b
Oct 15 15:30:20 computer kernel: [  209.936592] RSP: 0018:af6d4c31bc30 
EFLAGS: 00010286
Oct 15 15:30:20 computer kernel: [  209.936596] RAX: 8ed64afe2000 RBX: 
0004 RCX: 
Oct 15 15:30:20 computer kernel: [  209.936599] RDX: 0002 RSI: 
8ed647a69500 RDI: 8ed691757600
Oct 15 15:30:20 computer kernel: [  209.936601] RBP: 8ed647a69500 R08: 
8ed6461b3ec0 R09: 000c
Oct 15 15:30:20 computer kernel: [  209.936603] R10: 0001 R11: 
000c R12: 110e1000
Oct 15 15:30:20 computer kernel: [  209.936605] R13: af6d4c31bd78 R14: 
8ed647a69500 R15: 8ed691757600
Oct 15 15:30:20 computer kernel: [  209.936608] FS:  () 
GS:8edc5210() knlGS:
Oct 15 15:30:20 computer kernel: [  209.936611] CS:  0010 DS:  ES:  
CR0: 80050033
Oct 15 15:30:20 computer kernel: [  209.936614] CR2: 110e1680 CR3: 
00055381 CR4: 00750ee0
Oct 15 15:30:20 computer kernel: [  209.936617] PKRU: 5554
Oct 15 15:30:20 computer kernel: [  209.936619] Call Trace:
Oct 15 15:30:20 computer kernel: [  209.936623]  
Oct 15 15:30:20 computer kernel: [  209.936626]  ? mutex_lock+0xe/0x30
Oct 15 15:30:20 computer kernel: [  209.936637]  l2cap_chan_send+0x12f/0xc60 
[bluetooth]
Oct 15 15:30:20 computer kernel: [  209.936691]  ? remove_wait_queue+0x20/0x60
Oct 15 15:30:20 computer kernel: [  209.936698]  ? 
_raw_spin_unlock_irqrestore+0x23/0x40
Oct 15 15:30:20 computer kernel: [  209.936703]  ? preempt_count_add+0x6a/0xa0
Oct 15 15:30:20 computer kernel: [  209.936710]  l2cap_sock_sendmsg+0x9a/0x100 
[bluetooth]
Oct 15 15:30:20 computer kernel: [  209.936759]  sock_sendmsg+0x5f/0x70
Oct 15 15:30:20 computer kernel: [  209.936767]  rfcomm_send_frame+0x62/0xa0 
[rfcomm]
Oct 15 15:30:20 computer kernel: [  209.936778]  
rfcomm_send_disc.isra.0+0x80/0xd0 [rfcomm]
Oct 15 15:30:20 computer kernel: [  209.936787]  
__rfcomm_dlc_disconn+0x10a/0x120 [rfcomm]
Oct 15 15:30:20 computer kernel: [  209.936796]  __rfcomm_dlc_close+0x60/0x200 
[rfcomm]
Oct 15 15:30:20 computer kernel: [  209.936805]  rfcomm_run+0x6f6/0x1900 
[rfcomm]
Oct 15 15:30:20 computer kernel: [  209.936815]  ? 
_raw_spin_rq_lock_irqsave+0x20/0x20
Oct 15 15:30:20 computer kernel: [  209.936822]  ? 
rfcomm_check_accept+0xa0/0xa0 [rfcomm]
Oct 15 15:30:20 computer kernel: [  209.936830]  kthread+0xe9/0x110
Oct 15 15:30:20 computer kernel: [  209.936836]  ? 
kthread_complete_and_exit+0x20/0x20
Oct 15 15:30:20 computer kernel: [  209.936840]  ret_from_fork+0x22/0x30
Oct 15 15:30:20 computer kernel: [  209.936849]  
Oct 15 15:30:20 computer kernel: [  209.936851] Modules linked in: ehci_pci 
ipmi_devintf ehci_hcd ipmi_msghandler xt_conntrack nft_chain_nat xt_MASQUERADE 
nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink 
br_netfilter bridge stp llc nvme_fabrics ctr ccm uinput rfcomm snd_seq_dummy 
snd_hrtimer snd_seq snd_seq_device cmac algif_hash zstd zstd_compress 
algif_skcipher af_alg zram qrtr overlay bnep zsmalloc binfmt_misc nls_ascii 
nls_cp437 vfat fat intel_rapl_msr intel_rapl_common rtw89_8852ae btusb 
rtw89_8852a btrtl btbcm btintel btmtk snd_acp3x_pdm_dma snd_acp3x_rn 
snd_soc_dmic rtw89_pci edac_mce_amd bluetooth rtw89_core snd_soc_core uvcvideo 
snd_compress videobuf2_vmalloc kvm_amd videobuf2_memops videobuf2_v4l2 mac80211 
jitterentropy_rng snd_ctl_led videobuf2_common snd_hda_codec_hdmi 
snd_hda_codec_realtek kvm libarc4 drbg snd_hda_codec_generic videodev 
ansi_cprng snd_hda_intel irqbypass joydev 

Bug#1008816: ITP: kwin-bismuth -- KDE Plasma extension for tiling windows

[Blake Lee]

I hammered away basically everything but the CI. I'm not familiar enough with 
Debian's CI yet to just get it going. I'll have to research the link from the 
issue you posted when I have more time. luckily I am familiar with GitLab's CI 
in general so it shouldn't be difficult once I have a free block to try.

I believe I got everything else the way it should be.

Thanks,
Blake

On Tue, Sep 27, 2022, at 2:53 AM, Didier 'OdyX' Raboud wrote:
> Hello Blak,
> 
> Le dimanche, 25 septembre 2022, 04.45:58 h CEST Blake Lee a écrit :
> > Apologies for it taking me so long to get to it.
> 
> No problem!
> 
> > I nuked the repo and is now a clean, one commit, repo with only the unstable
> > debian files in the master branch.
> 
> Great, thanks! It was not a necessity to drop all past packaging work, but 
> doesn't hurt.
> 
> > I've also updated the files to build with the latest upstream release.
> > Tested with sbuild that it builds successfully.
> 
> For _my_ standards, the package is still missing some thinks here and there, 
> which I have filed as issues on the Salsa project, under a common milestone:
> 
> https://salsa.debian.org/qt-kde-team/extras/kwin-bismuth/-/milestones/1#tab-issues
> 
> #3 can be discussed later, but the other are quite important before upload.
> 
> Comments from others welcome of course!
> 
> Best,
> 
> OdyX
> 
> *Attachments:*
>  * signature.asc

Bug#1021499: fim: --slideshow=5 is buggy. doesn't show first picture, and 'q' doesn't quit

[d3fault]

Another small suggestion: --show-maximized to show the whole window
maximized when it's first launched. To be used in combination with -a
of course :)


d3fault

On 10/16/22, d3fault  wrote:
> Thank you for this! I haven't tested it but I'll assume it works.
> Since you're in "fim mode" maybe I can persuade you to re-add the "-1"
> flag and also re-add Ctrl-C terminating the program with error code !=
> 0. I'm trying to port the following fbi script to fim. what it does is
> recursively generates an image list from current directory, shuffles
> it, then displays those images in fbi and exits out. the whole process
> loops indefinitely (so a different shuffled order is shown every time)
> until Ctrl+C is pressed. it doesn't use a slideshow by default but I
> can pass "-t 5" to the script and then it does. side note: --slideshow
> 5 takes a bit longer to write. -t alias?
>
> thank you for your work on fim. fbi is awesome but up until now I was
> sad it didn't work with x11.
>
>
> #!/bin/bash
> while :
> do
>   fbi -noverbose -a -u "$@" -1 --list <(find . -type f \( -iname
> "*.jpg" -o -iname "*.bmp" -o -iname "*.png" -o -iname "*.gif" -o
> -iname "*.jpeg" \)) || break
> done
>
> On 10/10/22, Michele Martone  wrote:
>> ...I realize the last email patch was not covering -o fbdev and -o aa.
>>
>> Now:
>>  svn diff http://svn.savannah.nongnu.org/svn/fbi-improved -r 1676:1678
>> should cover those, too.
>> Tarballs updated.
>>
>> Feedback welcome,
>> m.
>>
>> On 20221010@12:02, Michele Martone wrote:
>>> Dear d3fault,
>>>
>>> Here is the upstream fix.
>>>
>>> In patch form:
>>>  svn diff http://svn.savannah.nongnu.org/svn/fbi-improved -r 1676:1677
>>>  (also attached)
>>>
>>> In 0.6 trunk tarball:
>>>
>>> http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz
>>>
>>> http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz.sig
>>>
>>> Would be great if you could give it a try.
>>>
>>> Cheers,
>>> Michele
>>>
>>> On 20221010@08:05, Michele Martone wrote:
>>> > Dear d3fault,
>>> >
>>> > Thanks for reporting of this defect.
>>> >
>>> > Unfortunately it's also in the latest revision.
>>> > I'll let you know here once I attack the problem.
>>> >
>>> > The good news in the last weeks I'm very active with fim, so
>>> > *maybe* we get this solved soon-ish :-)
>>> >
>>> > ciao,
>>> > Michele
>>> >
>>> > On 20221009@09:57, d3fault wrote:
>>> > > Package: fim
>>> > > Version: 0.5.3-9+b1
>>> > > Severity: normal
>>> > > X-Debbugs-Cc: d3faultdot...@gmail.com
>>> > >
>>> > > Dear Maintainer,
>>> > >
>>> > >* What led up to the situation?
>>> > >   fim --slideshow=5 ./*.jpg
>>> > >* What exactly did you do (or not do) that was effective (or
>>> > >  ineffective)?
>>> > >   I looked at the screen. I also pressed 'q'.
>>> > >* What was the outcome of this action?
>>> > >   The first image of the slideshow was just all black. The 2nd+
>>> > > images do show.
>>> > >   Also if you press 'q' while the slideshow is still running,
>>> > > the
>>> > > app doesn't quit
>>> > >   but instead it just progresses to the next image. After all
>>> > > the
>>> > > images have been
>>> > >   shown, then 'q' will quit. I would also expect slideshow mode
>>> > > to
>>> > > loop around
>>> > >   indefinitely, but that's not really a bug.
>>> > >* What outcome did you expect instead?
>>> > >   I expected to see the first image. I also expected 'q' to quit
>>> > > the app.
>>> > >
>>> > > Also confirmed the bug exists on Bullseye.
>>> > > It works fine in fbi.
>>> > >
>>> > >
>>> > > -- System Information:
>>> > > Debian Release: bookworm/sid
>>> > >   APT prefers unstable
>>> > >   APT policy: (500, 'unstable')
>>> > > Architecture: amd64 (x86_64)
>>> > >
>>> > > Kernel: Linux 5.10.0-18-amd64 (SMP w/4 CPU threads)
>>> > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
>>> > > LANGUAGE not set
>>> > > Shell: /bin/sh linked to /usr/bin/dash
>>> > > Init: systemd (via /run/systemd/system)
>>> > >
>>> > > Versions of packages fim depends on:
>>> > > ii  libaa1   1.4p5-50
>>> > > ii  libc62.35-3
>>> > > ii  libdjvulibre21   3.5.28-2
>>> > > ii  libexif120.6.24-1+b1
>>> > > ii  libgcc-s112.2.0-5
>>> > > ii  libgif7  5.2.1-2.5
>>> > > ii  libjpeg62-turbo  1:2.1.2-1+b1
>>> > > ii  libpng16-16  1.6.38-2
>>> > > ii  libreadline8 8.2-1
>>> > > ii  libsdl1.2debian  1.2.15+dfsg2-8
>>> > > ii  libstdc++6   12.2.0-5
>>> > > ii  libtiff5 4.4.0-4
>>> > >
>>> > > fim recommends no packages.
>>> > >
>>> > > fim suggests no packages.
>>> > >
>>> > > -- no debconf information
>>>
>>>
>>
>>> Index: trunk/src/CommandConsole.h
>>> ===
>>> --- trunk/src/CommandConsole.h  (revision 1676)
>>> +++ trunk/src/CommandConsole.h  (revision 1677)
>>> @@ -410,6 +410,7 @@
>>> public:
>>> void switch_if_needed(void);
>>> 

Bug#1021499: fim: --slideshow=5 is buggy. doesn't show first picture, and 'q' doesn't quit

[d3fault]

Thank you for this! I haven't tested it but I'll assume it works.
Since you're in "fim mode" maybe I can persuade you to re-add the "-1"
flag and also re-add Ctrl-C terminating the program with error code !=
0. I'm trying to port the following fbi script to fim. what it does is
recursively generates an image list from current directory, shuffles
it, then displays those images in fbi and exits out. the whole process
loops indefinitely (so a different shuffled order is shown every time)
until Ctrl+C is pressed. it doesn't use a slideshow by default but I
can pass "-t 5" to the script and then it does. side note: --slideshow
5 takes a bit longer to write. -t alias?

thank you for your work on fim. fbi is awesome but up until now I was
sad it didn't work with x11.


#!/bin/bash
while :
do
fbi -noverbose -a -u "$@" -1 --list <(find . -type f \( -iname
"*.jpg" -o -iname "*.bmp" -o -iname "*.png" -o -iname "*.gif" -o
-iname "*.jpeg" \)) || break
done

On 10/10/22, Michele Martone  wrote:
> ...I realize the last email patch was not covering -o fbdev and -o aa.
>
> Now:
>  svn diff http://svn.savannah.nongnu.org/svn/fbi-improved -r 1676:1678
> should cover those, too.
> Tarballs updated.
>
> Feedback welcome,
> m.
>
> On 20221010@12:02, Michele Martone wrote:
>> Dear d3fault,
>>
>> Here is the upstream fix.
>>
>> In patch form:
>>  svn diff http://svn.savannah.nongnu.org/svn/fbi-improved -r 1676:1677
>>  (also attached)
>>
>> In 0.6 trunk tarball:
>>
>> http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz
>>
>> http://download.savannah.nongnu.org/releases/fbi-improved/fim-0.6-trunk.tar.gz.sig
>>
>> Would be great if you could give it a try.
>>
>> Cheers,
>> Michele
>>
>> On 20221010@08:05, Michele Martone wrote:
>> > Dear d3fault,
>> >
>> > Thanks for reporting of this defect.
>> >
>> > Unfortunately it's also in the latest revision.
>> > I'll let you know here once I attack the problem.
>> >
>> > The good news in the last weeks I'm very active with fim, so
>> > *maybe* we get this solved soon-ish :-)
>> >
>> > ciao,
>> > Michele
>> >
>> > On 20221009@09:57, d3fault wrote:
>> > > Package: fim
>> > > Version: 0.5.3-9+b1
>> > > Severity: normal
>> > > X-Debbugs-Cc: d3faultdot...@gmail.com
>> > >
>> > > Dear Maintainer,
>> > >
>> > >* What led up to the situation?
>> > >   fim --slideshow=5 ./*.jpg
>> > >* What exactly did you do (or not do) that was effective (or
>> > >  ineffective)?
>> > >   I looked at the screen. I also pressed 'q'.
>> > >* What was the outcome of this action?
>> > >   The first image of the slideshow was just all black. The 2nd+
>> > > images do show.
>> > >   Also if you press 'q' while the slideshow is still running, the
>> > > app doesn't quit
>> > >   but instead it just progresses to the next image. After all the
>> > > images have been
>> > >   shown, then 'q' will quit. I would also expect slideshow mode
>> > > to
>> > > loop around
>> > >   indefinitely, but that's not really a bug.
>> > >* What outcome did you expect instead?
>> > >   I expected to see the first image. I also expected 'q' to quit
>> > > the app.
>> > >
>> > > Also confirmed the bug exists on Bullseye.
>> > > It works fine in fbi.
>> > >
>> > >
>> > > -- System Information:
>> > > Debian Release: bookworm/sid
>> > >   APT prefers unstable
>> > >   APT policy: (500, 'unstable')
>> > > Architecture: amd64 (x86_64)
>> > >
>> > > Kernel: Linux 5.10.0-18-amd64 (SMP w/4 CPU threads)
>> > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
>> > > LANGUAGE not set
>> > > Shell: /bin/sh linked to /usr/bin/dash
>> > > Init: systemd (via /run/systemd/system)
>> > >
>> > > Versions of packages fim depends on:
>> > > ii  libaa1   1.4p5-50
>> > > ii  libc62.35-3
>> > > ii  libdjvulibre21   3.5.28-2
>> > > ii  libexif120.6.24-1+b1
>> > > ii  libgcc-s112.2.0-5
>> > > ii  libgif7  5.2.1-2.5
>> > > ii  libjpeg62-turbo  1:2.1.2-1+b1
>> > > ii  libpng16-16  1.6.38-2
>> > > ii  libreadline8 8.2-1
>> > > ii  libsdl1.2debian  1.2.15+dfsg2-8
>> > > ii  libstdc++6   12.2.0-5
>> > > ii  libtiff5 4.4.0-4
>> > >
>> > > fim recommends no packages.
>> > >
>> > > fim suggests no packages.
>> > >
>> > > -- no debconf information
>>
>>
>
>> Index: trunk/src/CommandConsole.h
>> ===
>> --- trunk/src/CommandConsole.h   (revision 1676)
>> +++ trunk/src/CommandConsole.h   (revision 1677)
>> @@ -410,6 +410,7 @@
>>  public:
>>  void switch_if_needed(void);
>>  fim::string getInfoCustom(const fim_char_t * ifsp)const;
>> +fim_int show_must_go_on(void) const;
>>  };
>>  }
>>
>> Index: trunk/src/CommandConsole.cpp
>> ===
>> --- trunk/src/CommandConsole.cpp (revision 1676)
>> +++ trunk/src/CommandConsole.cpp (revision 1677)
>> @@ -645,7 +645,7 @@

Bug#1021904: krdc: Bluescreen when switching to a full screen or rescaling, the only remedy to make it usable again is restarting krdc

[manul]

Package: krdc
Version: 4:22.08.1-1
Severity: important

Dear Maintainer,

When connecting to a remote desktop using rdp, initially it connects normally 
(resolution was set to current screen resolution, initially of course it shows 
inside decorated window with scrollbars etc.).
But as soon as one attempts to enlarge to "full screen" it loses entirely the 
remote view leaving a permanent blue screen.
Even further disconnect does not solve the issue (I can't load "new connection" 
list, other hosts tab, or anything else); the rendering inside the KRDC window 
seems entirely broken frozen to a blue background.
The only remedy is entirely restarting the krdc app itself.

I tested freerdp2-x11 client alone it works normally on fullscreen etc no 
issues there.

The above renders krdc unusable unless one sticks to the default "decorated" 
view which is used immediately after connection. 
Each rescaling/fullscreen leads to a frozen bluescreen background, and the only 
way to get out of this and have krdc usable again is restarting it.

Tested on two debian sid systems, laptop and desktop.
Same behaviour on both (seems to got triggered by one of the latest versions, 
maybe released a month or so ago).

Yours,

manul


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/12 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), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages krdc depends on:
ii  libc6 2.35-3
ii  libkf5bookmarks5  5.98.0-1
ii  libkf5completion5 5.98.0-1
ii  libkf5configcore5 5.98.0-1
ii  libkf5configgui5  5.98.0-1
ii  libkf5configwidgets5  5.98.0-1
ii  libkf5coreaddons5 5.98.0-1
ii  libkf5dnssd5  5.98.0-1
ii  libkf5i18n5   5.98.0-1+b1
ii  libkf5kcmutils5   5.98.0-1
ii  libkf5notifications5  5.98.0-1
ii  libkf5notifyconfig5   5.98.0-1
ii  libkf5wallet-bin  5.98.0-1
ii  libkf5wallet5 5.98.0-1
ii  libkf5widgetsaddons5  5.98.0-1
ii  libkf5windowsystem5   5.98.0-1
ii  libkf5xmlgui5 5.98.0-1+b1
ii  libqt5core5a  5.15.6+dfsg-2
ii  libqt5gui55.15.6+dfsg-2
ii  libqt5widgets55.15.6+dfsg-2
ii  libqt5xml55.15.6+dfsg-2
ii  libssh-4  0.10.4-2
ii  libstdc++612.2.0-5
ii  libvncclient1 0.9.13+dfsg-4

Versions of packages krdc recommends:
ii  freerdp2-wayland  2.8.0+dfsg1-1
ii  freerdp2-x11  2.8.0+dfsg1-1

Versions of packages krdc suggests:
ii  khelpcenter  4:22.04.1-1
pn  krfb 

-- no debconf information

Bug#1004638: Bug#1013009: Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Emmanuel Bourg]

Le 16/10/2022 à 17:10, Philipp Kern a écrit :


While arm64/armhf remains unfixed (and could have its own t-p-u upload
based on the +0 version plus Ubuntu's patch), there's also a question if
a newer version would actually fix the issue.

I talked to Sebastian on IRC and we agreed that I'd upload the Ubuntu
patch for now. It doesn't make anything worse and will allow building
on amd64 again.


Hi Philipp,

Thank you for taking the time to look into the openjfx package. Do you 
know how difficult porting to ffmpeg 5.0 would be? The video support is 
a major feature of OpenJFX, removing it isn't ideal.


Emmanuel Bourg

Bug#1015207: transitions: ruby3.1-add

[Sebastian Ramacher]

Hi

On 2022-10-16 18:45:47 -0300, Antonio Terceiro wrote:
> Hi,
> 
> please binNMU:
> 
> puma

The 5.6.5-1 upload of puma from a few hours ago also failed. It doesn't
look like #1006022 is fixed.

> thin
> ruby-bootsnap

Scheduled

Cheers
-- 
Sebastian Ramacher

Bug#1021903: O: sleekxmpp -- XMPP (Jabber) Library Implementing Everything as a Plugin (Python 3.x)

[Martin]

Package: wnpp
Severity: normal

This package is superseded by slixmppp.
It should probably be removed before freeze.
If nobody adopts it in time, I'll ask for removal.

Bug#1021880: rust-image - multiple issues.

[Peter Green]

Hi.

It appears that rust-deflate was uploaded a bit prematurely, it depends on a new
version of rust-gzip--header which can't be packaged with the cargo/debcargo
currently in Debian.

Once cargo/debcargo are updated we can move on to updating/fixing the image
stack.

Bug#1021902: O: python-diaspy -- unofficial interface to the Diaspora social network (Python 3)

[Martin]

Package: wnpp
Severity: normal

I don't need the package anymore.
Maybe somebody in the Python team likes to be uploader?

Bug#1021603: libpmix2

[Ron Lovell]

Should have said Arch Linux Issue 75727.

On Sun, Oct 16, 2022 at 5:20 PM Ron Lovell  wrote:

> Same issue as Arch issue 279267?
>
> --
> James Ronald Lovell 
> Huntsville, AL, USA
>
>

-- 
James Ronald Lovell 
Huntsville, AL, USA

Bug#1021603: libpmix2

[Ron Lovell]

Same issue as Arch issue 279267?

-- 
James Ronald Lovell 
Huntsville, AL, USA

Bug#1001362: gnome-control-center: Please Suggest or Recommend power-profiles-daemon

[Alban Browaeys]

package gnome-control-center
fixed 1001362 1:42.0-2
thanks


power-profiles-daemon was added as a recommand in
https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/cbcba952c8a7801da2290e90b95746082721a0da
which was first shipped in Debian in 1:42.0-2.


On Thu, 09 Dec 2021 09:34:39 +0100 =?utf-8?b?SsOpcsOpbXkgTGFs?=
 wrote:
> Package: gnome-control-center
> Version: 1:41.2-1
> Severity: wishlist
> 
> Hi,
> 
> if power-profiles-daemon is installed, gnome-control-center displays
controls
> for choosing power profile.
> 
> However gnome-settings-daemon also makes use of power-profiles-
daemon,
> so maybe the dependency should be on it or on some other gnome
package.
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers stable-security
>   APT policy: (500, 'stable-security'), (500, 'unstable'), (101,
'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
> 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
> 
> Versions of packages gnome-control-center depends on:
> ii  accountsservice    0.6.55-3
> ii  apg    2.2.3.dfsg.1-5+b2
> ii  colord 1.4.5-3
> ii  desktop-base   11.0.3
> ii  desktop-file-utils 0.26-1
> ii  gnome-control-center-data  1:41.2-1
> ii  gnome-desktop3-data    41.1-1
> ii  gnome-settings-daemon  41.0-2
> ii  gsettings-desktop-schemas  41.0-2
> ii  libaccountsservice0    0.6.55-3
> ii  libatk1.0-0    2.36.0-2
> ii  libc6  2.32-5
> ii  libcairo2  1.16.0-5
> ii  libcheese-gtk25    41.1-1
> ii  libcheese8 41.1-1
> ii  libcolord-gtk1 0.1.26-2+b1
> ii  libcolord2 1.4.5-3
> ii  libcups2   2.3.3op2-7
> ii  libepoxy0  1.5.9-2
> ii  libfontconfig1 2.13.1-4.2
> ii  libgcr-base-3-1    3.40.0-3+b1
> ii  libgdk-pixbuf-2.0-0    2.42.6+dfsg-2
> ii  libglib2.0-0   2.70.2-1
> ii  libgnome-bluetooth13   3.34.5-4
> ii  libgnome-desktop-3-19  41.1-1
> ii  libgoa-1.0-0b  3.40.1-2
> ii  libgoa-backend-1.0-1   3.40.1-2
> ii  libgsound0 1.0.3-2
> ii  libgtk-3-0 3.24.30-4
> ii  libgtop-2.0-11 2.40.0-2
> ii  libgudev-1.0-0 237-2
> ii  libhandy-1-0   1.5.0-1
> ii  libibus-1.0-5  1.5.25-3
> ii  libkrb5-3  1.18.3-7

Bug#1015207: transitions: ruby3.1-add

[Antonio Terceiro]

Hi,

please binNMU:

puma
thin
ruby-bootsnap

These failed to build before, but that was probably due to something
else down the stack. All three build fine in unstable at the moment.

The only missing piece is ruby-mysql2, which I will work on next.


signature.asc
Description: PGP signature

Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem

[Steve McIntyre]

On Sun, Oct 16, 2022 at 09:57:35PM +0100, Steve McIntyre wrote:
>On Sun, Oct 16, 2022 at 07:37:53AM +0300, программист некто wrote:
>>Output already captured. See 
>>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021846  the first message 
>>- it have an attached files with grub-install output.
>
>Ah, sorry; I missed them. Looking now.

So I can see from the logs is that from 2.06-3 is just failing to
detect a f2fs filesyste. There *was* a significant set of changes
before we shipped that version: upstream security updates that fixed a
big set of bugs, including in the f2fs code. I'm thinking that one of
those changes might have caused this issue.

Are you happy to try rebuilding grub from source yourself? If so, I'd
suggest to rebuild without those f2fs changes included. If you're not
sure, let me know and I'll do a rebuild for you.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< Aardvark> I dislike C++ to start with. C++11 just seems to be
handing rope-creating factories for users to hang multiple
instances of themselves.

Bug#1021899: wrongly reports a typo for rule execute_before_mh_install

[Jelmer Vernooij]

On Sun, Oct 16, 2022 at 09:47:14PM +0200, Pierre Gruet wrote:
> In the debian/rules file of the source package jmol, I have a rule called
> execute_before_mh_install
> and lintian-brush reports a typo-in-debhelper-override-target and changes it 
> to
> execute_before_dh_install
> although mh_install is a valid sequence brought up by maven_repo_helper, which
> one uses to add Maven coordinates for Java projects.
> 
> Do you think this might get fixed?

Thanks for the report! I've committed a fix to master, should hopefully
make it into the archive in the next couple of weeks.

Cheers,

Jelmer

Bug#873197: gnome-control-center: touchpad lost functionality after debian 8 -> 9 upgrade

[Alban Browaeys]

On Fri, 25 Aug 2017 15:05:48 +0200 Rafal Pietrak 
wrote:
> Package: gnome-control-center
> Version: 1:3.22.2-3
> Severity: important
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> 
> upgrade from debian jessie to debian stretch
> 
>    * What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> gnome-control-center settings are ineffective
> 
>    * What was the outcome of this action?
> 
> none control-center does not effect the scrolling-mode
> 
>    * What outcome did you expect instead?
> 
> 1. "natural scrolling" (following the "paper", istead of
"window")
> 2. tap2click - no such option, and does not work by default
(e.g there
> is no way to switch it on)
> 

This is a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821352. That is you
have to check that xserver-xorg-input-synaptics is removed and xserver-
xorg-input-libinput is installed. GNOME does not support xserver-xorg-
input-synaptics anymore.

If you still have the issue could you confirm this fixes it?
Could you close this bug report if you are still on GNOME Xorg and do
not experience the issue anymore?


Kind regards,

Alban



> 
> -- System Information:
> Debian Release: 9.1
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8),
LANGUAGE=pl_PL.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages gnome-control-center depends on:
> ii  accountsservice    0.6.43-1
> ii  apg    2.2.3.dfsg.1-4+b1
> ii  colord 1.3.3-2
> ii  desktop-file-utils 0.23-1
> ii  gnome-control-center-data  1:3.22.2-3
> ii  gnome-desktop3-data    3.22.2-1
> ii  gnome-settings-daemon  3.22.2-2+deb9u2
> ii  gsettings-desktop-schemas  3.22.0-1
> ii  libaccountsservice0    0.6.43-1
> ii  libatk1.0-0    2.22.0-1
> ii  libc6  2.24-11+deb9u1
> ii  libcairo-gobject2  1.14.8-1
> ii  libcairo2  1.14.8-1
> ii  libcanberra-gtk3-0 0.30-3
> ii  libcanberra0   0.30-3
> ii  libcheese-gtk25    3.22.1-1+b1
> ii  libcheese8 3.22.1-1+b1
> ii  libclutter-1.0-0   1.26.0+dfsg-3
> ii  libclutter-gtk-1.0-0   1.8.2-2
> ii  libcolord-gtk1 0.1.26-1.1
> ii  libcolord2 1.3.3-2

Bug#1005264: gnome-control-center: touchpad options in gnome conrol center not work atall and not respond to chaning settings

[Alban Browaeys]

On Thu, 10 Feb 2022 08:09:44 +0330 alireza 
wrote:
> Package: gnome-control-center
> Version: 1:41.2-1
> Severity: important
> X-Debbugs-Cc: alireza...@gmail.com
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where
appropriate ***
> 
>     * What led up to the situation? upgrading
>     * What exactly did you do (or not do) that was effective (or
>   ineffective)? upwidgetgrading to gnome 41
>     * What was the outcome of this action? disabling touchpad
> settings
>     * What outcome did you expect instead? that settings on touchapd
take effect


Could it be a duplicate
of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821352, that is
xorg synaptics driver is not compatibale with GNOME anymore. Could you
tell if you are running a Gnome Xorg session or a Wayland one ?

If Xorg a session do you have xserver-xorg-input-synaptics installed?
gnome has removed support for this synaptics driver around 2016 and
only supports changing settings to the xserver-xorg-input-libinput
driver.


Kind regards,

Alban

Bug#1013171: gnome-control-center does not start on gnome Wayland

[Alban Browaeys]

On Sat, 18 Jun 2022 11:13:43 +0200 Giacomo Mulas
 wrote:
> Package: gnome-control-center
> Version: 1:42.2-1
> Severity: important
> 
> Dear Maintainer,
> 
> after some recent upgrade (I cannot pin down which one exactly, I
have an up
> to date sid system), gnome-control-center does not display any window
any
> more when running in a gnome wayland session. It still does work
properly
> in a gnome on Xorg session. It is not the only one showing this
behaviour, 
> the same happens (to me) with at least gnome-software, gnome-
extensions-app, 
> extension-manager. The problem is identical even with all gnome
extensions
> disabled, so it does not depend on this.
 
This was likely not a gnome-control-center issue if it also affect
other gnome-software. Was this fixed by an upgrade since then?


From the strace I see you have an nvidia graphic card. Could you try
wayland with nouveau? The bug is probably in the nvidia code.




> I attach at the end environment and strace for both gnome-control-
center on
> wayland (which shows no window) and on xorg (which works correctly). 
Please
> let me know if there is some test I may run to help track this
problem down.
> 
> Thanks in advance, best regards
> Giacomo Mulas
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (401, 'unstable'), (10, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.18.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 gnome-control-center depends on:
> ii  accountsservice   22.08.8-1
> ii  apg   2.2.3.dfsg.1-5+b2
> ii  colord    1.4.6-1
> ii  desktop-base  11.0.3
> ii  desktop-file-utils    0.26-1
> ii  gnome-control-center-data 1:42.2-1
> ii  gnome-desktop3-data   42.2-1
> ii  gnome-settings-daemon 42.2-1
> ii  gsettings-desktop-schemas 42.0-1
> ii  libaccountsservice0   22.08.8-1
> ii  libadwaita-1-0    1.1.2-1
> ii  libc6 2.33-7
> ii  libcairo2 1.16.0-5
> ii  libcolord-gtk4-1  0.3.0-3
> ii  libcolord2    1.4.6-1
> ii  libcups2  2.4.2-1
> ii  libepoxy0 1.5.10-1
> ii  libfontconfig1    2.13.1-4.4
> ii  libgcr-base-3-1   3.41.0-4
> ii  libgdk-pixbuf-2.0-0   2.42.8+dfsg-1
> ii  libglib2.0-0  2.72.2-2
> ii  libgnome-bg-4-1   42.2-1
> ii  libgnome-bluetooth-ui-3.0-13  42.1-1
> ii  libgnome-desktop-4-1  42.2-1

Bug#1021901: ardour: Ardour 7.0.0 out :)

[Clément Hermann]

Package: ardour
Version: 1:6.9.0+ds0-2+b1
Severity: wishlist

Dear Maintainer,

In case you didn't notice yet, Ardour 7.0.0 has been released on October
15th. Since I wanted to give it a go, I thought I'd try to upgrade to
the last upstream release.

So I created a MR on salsa for you to review:

https://salsa.debian.org/multimedia-team/ardour/-/merge_requests/4

It's still in Draft since there are a few things to fix still (check
TODO section in changelog). I intend to fix them before removing the
Draft tag.

Of course, feel free to beat me to it, add commits before merging, remove the 
draft tag and just merge and work from there; or cherry-pick what you want…

I tried my best to stay consistent with the previous work / team rules,
but I'm new to these packages, so I might have missed stuff.

HTH,

-- 
nodens


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

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

Versions of packages ardour depends on:
ii  ardour-data   1:6.9.0+ds0-2
ii  ardour-lv2-plugins1:6.9.0+ds0-2+b1
ii  libarchive13  3.6.0-1
ii  libasound21.2.7.2-1
ii  libatkmm-1.6-1v5  2.28.3-1
ii  libaubio5 0.4.9-4.2+b1
ii  libc6 2.35-2
ii  libcairo2 1.16.0-6
ii  libcairomm-1.0-1v51.14.4-1
ii  libcurl3-gnutls   7.85.0-1
ii  libcwiid1 0.6.91-4
ii  libdbus-1-3   1.14.2-1
ii  libfftw3-single3  3.3.8-2
ii  libfluidsynth32.3.0-1
ii  libfontconfig12.13.1-4.5
ii  libgcc-s1 12.2.0-5
ii  libgdk-pixbuf-2.0-0   2.42.9+dfsg-1
ii  libglib2.0-0  2.74.0-2
ii  libglibmm-2.4-1v5 2.66.5-1
ii  libgtk2.0-0   2.24.33-2
ii  libgtkmm-2.4-1v5  1:2.24.5-4+b1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-1
ii  liblilv-0-0   0.24.14-1
ii  liblo70.31-1
ii  liblrdf0  0.6.1-2
ii  libltc11  1.3.1-1
ii  libpango-1.0-01.50.10+ds-1
ii  libpangocairo-1.0-0   1.50.10+ds-1
ii  libpangoft2-1.0-0 1.50.10+ds-1
ii  libpangomm-1.4-1v52.46.3-1
ii  libpulse0 16.1+dfsg1-2
ii  libqm-dsp01.7.1-5
ii  libreadline8  8.2-1
ii  librubberband23.0.0+dfsg0-1+b1
ii  libsamplerate00.2.2-2
ii  libsigc++-2.0-0v5 2.10.8-1
ii  libsndfile1   1.1.0-2
ii  libstdc++612.2.0-5
ii  libsuil-0-0   0.10.18-1
ii  libtag1v5 1.12-1+b1
ii  libusb-1.0-0  2:1.0.26-1
ii  libvamp-hostsdk3v52.10.0-1
ii  libvamp-sdk2v52.10.0-1
ii  libwebsockets17   4.1.6-3
ii  libx11-6  2:1.8.1-2
ii  libxml2   2.9.14+dfsg-1+b1

Versions of packages ardour recommends:
ii  ardour-video-timeline  1:6.9.0+ds0-2

ardour suggests no packages.

-- no debconf information

Bug#1019347: Fixed NMU

[Sven Bartscher]

Hi,

I just wanted to give a heads up, that earlier today I uploaded an NMU 
to DELAYED+5 containing upstream version 1.7.4 which should fix this bug.


I pushed the changes to the packaging repository on salsa, so I assume a 
debdiff of the NMU is not required here.


Regards
Sven


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem

[Steve McIntyre]

On Sun, Oct 16, 2022 at 07:37:53AM +0300, программист некто wrote:
>Output already captured. See 
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021846  the first message - 
>it have an attached files with grub-install output.

Ah, sorry; I missed them. Looking now.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Mature Sporty Personal
  More Innovation More Adult
  A Man in Dandism
  Powered Midship Specialty

Bug#1007287: NMU: xfsdump 3.1.11-0.1

[Bastian Germann]

I have just uploaded a NMU. debdiff is attached.diff -Nru xfsdump-3.1.9+0+nmu2/aclocal.m4 xfsdump-3.1.11/aclocal.m4
--- xfsdump-3.1.9+0+nmu2/aclocal.m4 2020-01-31 18:30:58.0 +0100
+++ xfsdump-3.1.11/aclocal.m4   2022-08-26 18:15:01.0 +0200
@@ -1,6 +1,6 @@
-# generated automatically by aclocal 1.16.1 -*- Autoconf -*-
+# generated automatically by aclocal 1.16.3 -*- Autoconf -*-
 
-# Copyright (C) 1996-2018 Free Software Foundation, Inc.
+# Copyright (C) 1996-2020 Free Software Foundation, Inc.
 
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
diff -Nru xfsdump-3.1.9+0+nmu2/common/drive.h xfsdump-3.1.11/common/drive.h
--- xfsdump-3.1.9+0+nmu2/common/drive.h 2020-01-31 18:30:58.0 +0100
+++ xfsdump-3.1.11/common/drive.h   2022-08-08 15:48:54.0 +0200
@@ -584,7 +584,7 @@
 */
void (*do_quit)(drive_t *drivep);
/* tells the drive manager to de-allocate
-* resources, INCLUDING the slave process.
+* resources, INCLUDING the worker process.
 */
 };
 
diff -Nru xfsdump-3.1.9+0+nmu2/common/drive_minrmt.c 
xfsdump-3.1.11/common/drive_minrmt.c
--- xfsdump-3.1.9+0+nmu2/common/drive_minrmt.c  2020-01-31 18:30:58.0 
+0100
+++ xfsdump-3.1.11/common/drive_minrmt.c2022-08-08 15:48:54.0 
+0200
@@ -186,7 +186,7 @@
 * to media without error. includes media file header
 * record. this is incremented when the actual I/O is
 * done. dc_reccnt is different, indicating what has
-* been seen by client. slave may have read ahead /
+* been seen by client. worker may have read ahead /
 * written behind.
 */
int dc_fd;
@@ -211,7 +211,7 @@
 * compression
 */
bool_t dc_singlethreadedpr;
-   /* single-threaded operation (no slave)
+   /* single-threaded operation (no worker)
 */
bool_t dc_errorpr;
/* TRUE if error encountered during reading or writing.
@@ -687,7 +687,7 @@
return BOOL_TRUE;
 }
 
-/* wait here for slave to complete initialization.
+/* wait here for worker to complete initialization.
  * set drive capabilities flags. NOTE: currently don't make use of this
  * feature: drive initialization done whenever block/record sizes unknown.
  */
@@ -2514,7 +2514,7 @@
if (ringp) {
display_ring_metrics(drivep, MLOG_VERBOSE);
 
-   /* tell slave to die
+   /* tell worker to die
 */
mlog((MLOG_NITTY + 1) | MLOG_DRIVE,
  "ring op: destroy\n");
@@ -3873,10 +3873,10 @@
  bufszbuf,
  bufszsfxp,
  contextp->dc_ringpinnedpr ? _("pinned ") : "",
- ringp->r_slave_msgcnt - ringp->r_slave_blkcnt,
- ringp->r_slave_msgcnt,
- percent64(ringp->r_slave_msgcnt - ringp->r_slave_blkcnt,
-ringp->r_slave_msgcnt),
+ ringp->r_worker_msgcnt - ringp->r_worker_blkcnt,
+ ringp->r_worker_msgcnt,
+ percent64(ringp->r_worker_msgcnt - ringp->r_worker_blkcnt,
+ringp->r_worker_msgcnt),
  (double)(ringp->r_all_io_cnt)
  *
  (double)tape_recsz
diff -Nru xfsdump-3.1.9+0+nmu2/common/drive_scsitape.c 
xfsdump-3.1.11/common/drive_scsitape.c
--- xfsdump-3.1.9+0+nmu2/common/drive_scsitape.c2020-01-31 
18:30:58.0 +0100
+++ xfsdump-3.1.11/common/drive_scsitape.c  2022-08-08 15:48:54.0 
+0200
@@ -188,7 +188,7 @@
 * to media without error. includes media file header
 * record. this is incremented when the actual I/O is
 * done. dc_reccnt is different, indicating what has
-* been seen by client. slave may have read ahead /
+* been seen by client. worker may have read ahead /
 * written behind.
 */
int dc_fd;
@@ -231,7 +231,7 @@
 * compression
 */
bool_t dc_singlethreadedpr;
-   /* single-threaded operation (no slave)
+   /* single-threaded operation (no worker)
 */
bool_t dc_errorpr;
/* TRUE if error encountered during reading or writing.
@@ -800,7 +800,7 @@
return BOOL_TRUE;
 }
 
-/* wait here for slave to complete initialization.
+/* wait here for worker to complete initialization.
  * set drive capabilities 

Bug#1005264: gnome-control-center: touchpad options in gnome conrol center not work atall and not respond to chaning settings

[Alban Browaeys]

On Thu, 10 Feb 2022 08:09:44 +0330 alireza 
wrote:
> Package: gnome-control-center
> Version: 1:41.2-1
> Severity: important
> X-Debbugs-Cc: alireza...@gmail.com
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where
appropriate ***
> 
>    * What led up to the situation? upgrading
>    * What exactly did you do (or not do) that was effective (or
>  ineffective)? upwidgetgrading to gnome 41
>    * What was the outcome of this action? disabling touchpad settings
>    * What outcome did you expect instead? that settings on touchapd
take effect


Could it be a duplicate
of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821352, that is
xorg synaptics driver is not compatibale with GNOME anymore. Could you
tell if you are running a Gnome Xorg session or a Wayland one ?

If Xorg a session do you have xserver-xorg-input-synaptics installed?
gnome has removed support for this synaptics driver around 2016 and
only supports changing settings to the xserver-xorg-input-libinput
driver.


Kind regards,

Alban

Bug#1021839: info -w is slow for man pages

[Hilmar Preuße]

Am 15.10.2022 um 19:14 teilte Jakub Wilk mit:

Hi Jakub,

Apparently this is because "info -w" calls "man -a", which is a very 
inefficent way to check if a man page exists:


     $ strace -f -e trace=execve -o '| grep -w man >&2' info -w 
ffmpeg-all > /dev/null
     1142  execve("/usr/bin/man", ["/usr/bin/man", "-a", "ffmpeg-all"], 
0xfffd7dd4 /* 52 vars */) = 0




I forwarded the issue to upstream [1], the main concern there is that 
"man -w" is not supported on all OS.



No, it doesn't exist on Solaris:

https://docs.oracle.com/cd/E26502_01/html/E29030/man-1.html#scrolltoc

It may be more trouble than it's worth to try to account for different
man versions.


Hilmar

[1] https://lists.gnu.org/archive/html/bug-texinfo/2022-10/msg00116.html
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021900: ttf-tagbanwa: Consider renaming to fonts-tagbanwa

[Boyuan Yang]

Source: ttf-tagbanwa
Version: 1.011
Severity: wishlist
Tags: sid
X-Debbugs-CC: sthiba...@debian.org

Hi,

I believe Debian's Fonts Team has a recommendation that all TTF and OTF
fonts to be named after fonts-* [1]. Please consider renaming your font both
for the source package and binary package. A transitional dummy package may
be needed. Thanks!

Regards,
Boyuan Yang


[1] https://wiki.debian.org/Fonts


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

Bug#915948: dak: arch:all lag from amd64 causes old binaries to disappear?

[Christoph Berg]

> The source-only upload of perl_5.28.1-3 yesterday resulted in a mirror
> push where the new arch:any binaries (perl, perl-base etc.) were in the
> amd64 Packages list, but the arch:all ones (perl-modules-5.28, perl-doc
> etc.) were missing altogether.

This bug hit postgresql-common yesterday after the 144+nmu1 upload.
Only postgresql-server-dev-all:amd64 was present in the sid Packages
file, all arch:all packages from that source (postgresql-common and
others) were missing.

Britney was complaining pretty loudly that the binaries were missing.

One dinstall later things were in order again.

rmadison reported the packages present during that time ("source, all"),
I think, but possibly that was already after the next dinstall, before
deb.debian.org had been updated.

Christoph

Bug#1017881: ITA: unclutter-xfixes -- hide the X mouse cursor after a period of inactivity, using XFixes

[Sean Whitton]

Hello,

On Sat 15 Oct 2022 at 06:22PM GMT, Stefan Kangas wrote:

> Sean Whitton  writes:
>
>> Sweet, thanks.  I can sponsor the upload if you want.
>
> Thank you, that will be appreciated.

Okay, let me know when ready.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1021303: btllib_1.4.9+dfsg-1_amd64.changes REJECTED

[Andreas Tille]

Hi Thorsten,

Am Sun, Oct 16, 2022 at 06:00:10PM + schrieb Thorsten Alteholz:
> as the license of this software is only GPL-3, please remove the term "or (at 
> your option) any later version. " from your debian/copyright.

Fixed in new upload, thanks a lot for thorough checking
 Andreas. 

-- 
http://fam-tille.de

Bug#1021899: wrongly reports a typo for rule execute_before_mh_install

[Pierre Gruet]

Package: lintian-brush
Version: 0.132
Severity: normal

Dear Maintainer,

In the debian/rules file of the source package jmol, I have a rule called
execute_before_mh_install
and lintian-brush reports a typo-in-debhelper-override-target and changes it to
execute_before_dh_install
although mh_install is a valid sequence brought up by maven_repo_helper, which
one uses to add Maven coordinates for Java projects.

Do you think this might get fixed?

Best,

-- 
Pierre

Bug#1021074: postgresql-15: collation version mismatch warnings on upgrading to 15-rc1

[Christoph Berg]

Re: Diederik de Haas
> > > > HINT:  Rebuild all objects in this database that use the default
> > > > collation
> > > > and run ALTER DATABASE template1 REFRESH COLLATION VERSION,
> > > > or build PostgreSQL with the right library version.
> 
> The 'AND run' part of the hint was what brought confusion/doubt for me as it 
> suggested 2 different things, whereas only the latter was explained/detailed.

"Rebuild all objects" is mostly indexes that use some ordering, but
might be a plethora of corner-case-ish things like "CHECK (foo < '1-1')".

https://wiki.postgresql.org/wiki/Locale_data_changes has more details.

Arguably, the message doesn't say that, but it's hard to squeeze a
complex topic into just a few lines.

Christoph

Bug#1017035: kopano-presence: please migrate from sleekxmpp to slixmpp

[Martin]

Control: severity -1 serious

I'll ask for removal of sleekxmpp from Debian before freeze.

Bug#1021893: device-tree-compiler: reproducible builds: Embeds build time in in various binaries

[Vagrant Cascadian]

Control: tags 1021893 pending

On 2022-10-16, Vagrant Cascadian wrote:
> The build time is embedded in various binaries:
>
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/device-tree-compiler.html
>
>   /usr/bin/convert-dtsv0
>
>   /build/1st/device-tree-compiler-1.6.1/srcpos.c:101
>   vs.
>   /build/2/device-tree-compiler-1.6.1/2nd/srcpos.c:101
>
> The attached patch to debian/rules fixes this by passing the default
> CFLAGS via EXTRA_CFLAGS, which includes the -ffile-prefix-map compiler
> option.
...
> From: Vagrant Cascadian 
> Date: Sun, 16 Oct 2022 18:02:45 +
> Subject: [PATCH] debian/rules: Pass default CFLAGS via EXTRA_CFLAGS.

Pushed to git:

  
https://salsa.debian.org/crosstoolchain-team/device-tree-compiler/-/commit/95182ef710c6027f1d9796b0fb3124b43bead2e7

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1021845: s050000l.afm lost in transition from gsfonts to fonts-urw-base35

[Fabian Greffrath]

Hi Christoph,

Am Samstag, dem 15.10.2022 um 22:18 +0200 schrieb Christoph Biedl:
> and identified the problem as follows: This file s05l.afm was
> previously provided by gsfonts package, that package is now
> transitional
> and depends on fonts-urw-base35, but the file is not provided there.

as Roland already stated, the file has merely been moved to a different
location. The actual transition should be trivial.

I have filed heads-up bug reports against all packages with an install-
time relationship with the previous gsfonts and gsfonts-x11 packages,
but I may have somehow missed packages with Build-Depends on gsfonts.

I will provide a README.Debian file with the next revision, explicitly
listing the font files with their previous and new file names and paths
to make migrations easier.

Thanks!

Cheers,

 - Fabian



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

Bug#1021898: sfepy: FTBFS: distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must be an Extension instance or 2-tuple

[Sebastian Ramacher]

Source: sfepy
Version: 2021.4-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=sfepy=amd64=2021.4-1%2Bb1=1665944538=0

Traceback (most recent call last):
  File "/<>/setup.py", line 252, in 
setup_package()
  File "/<>/setup.py", line 230, in setup_package
setup(name='sfepy',
  File "/usr/lib/python3/dist-packages/numpy/distutils/core.py", line 169, in 
setup
return old_setup(**new_attr)
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
setup
return distutils.core.setup(**attrs)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
return run_commands(dist)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
973, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
992, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/numpy/distutils/command/build.py", line 
61, in run
old_build.run(self)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", 
line 132, in run
self.run_command(cmd_name)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 319, 
in run_command
self.distribution.run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1217, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
992, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/numpy/distutils/command/build_src.py", 
line 144, in run
self.build_sources()
  File "/usr/lib/python3/dist-packages/numpy/distutils/command/build_src.py", 
line 158, in build_sources
self.check_extensions_list(self.extensions)
  File "/usr/lib/python3.10/distutils/command/build_ext.py", line 362, in 
check_extensions_list
raise DistutilsSetupError(
distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must 
be an Extension instance or 2-tuple
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build 
dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned exit 
code 13


Cheers
-- 
Sebastian Ramacher

Bug#1021897: gnome-disk-utility: Crash when clicked X (cancel) on Deleting partition

[piorunz]

Package: gnome-disk-utility
Version: 43.0-1
Severity: normal
X-Debbugs-Cc: pior...@gmx.com

Crash occured when I tried to cancel Delete Partition operation which took too
long.

Steps:
Mount SATA SSD disk via SATA cable. Disk has one Ext4 partition, otherwise it's
clean and empty, zero files. MBR format.
I mounted the partition and then unmounted it, but I don't remember exactly if
partition was mounted or not.
Open Gnome Disks
Disk is in good condition, zero errors, bad sectors, or whatever, it's old
Kingston 60 GB SSD. Good performance in Disks benchmark, 300 MB/s read and
write.
Click "-" icon which will delete existing Ext4 partition.
Progress in the window shows current operation "Deleting partition" and X next
to it to cancel this.
I waited about 30 seconds, way to long just to modify MBR partition table,
which should take zero seconds.
Clicked X.
Gnome Disks immediately crashed with following errors in terminal (I run it
from terminal):
$ gnome-disks
**
GNOME-Disks:ERROR:../src/disks/gduwindow.c:4270:on_job_cancel_button_clicked:
assertion failed: (object != NULL)
Bail out! GNOME-
Disks:ERROR:../src/disks/gduwindow.c:4270:on_job_cancel_button_clicked:
assertion failed: (object != NULL)
Aborted (core dumped)

Dmesg shows no errors.

What should happen: no crash.

Maybe partition was mounted, I don't remember at this moment, and Gnome Disks
tried to delete partition anyway? Or something else failed with deleting
partition procedure, that's why it crashed when I tried to cancel this
"Deleting partition" procedure.


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

Kernel: Linux 5.19.0-2-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 gnome-disk-utility depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  libatk1.0-0  2.46.0-3
ii  libc62.35-3
ii  libcairo21.16.0-6
ii  libcanberra-gtk3-0   0.30-10
ii  libdvdread8  6.1.3-1
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.74.0-2
ii  libgtk-3-0   3.24.34-3
ii  libhandy-1-0 1.8.0-1
ii  liblzma5 5.2.5-2.1
ii  libnotify4   0.8.1-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libpwquality11.4.4-1+b1
ii  libsecret-1-00.20.5-3
ii  libsystemd0  251.5-1
ii  libudisks2-0 2.9.4-3
ii  udisks2  2.9.4-3

gnome-disk-utility recommends no packages.

gnome-disk-utility suggests no packages.

-- no debconf information

Bug#1011376: tpm2-pkcs11: Please import new upstream version

[Bastian Germann]

On Mon, 12 Sep 2022 11:49:52 +0200 Claudius Heine  wrote:
the tpm2-pytss dependency is on its way into the Repos [1] and I also 
provided a update to tpm2-pkcs11 1.8.0 [2] in my fork on salsa.


I have pushed the changes to the Vcs-Git repo.
Please upload a new version so that we can have nice things in bookworm.
Alvin, please notify me if you need a sponsor.

Bug#1021895: pylint: fails to honor "--" argument

[Nilesh Patra]

Package: pylint
Version: 2.15.3-1
Severity: serious
Tags: patch
X-Debbugs-Cc: mo...@debian.org

Hi,

It seems that the new version of pylint does not honor the
"--" arg.
In particular, if you notice the autopkgtest for ionit[1] it fails with:

/usr/bin/python3 -m pylint 
--rcfile=/tmp/autopkgtest-lxc.2tqox33y/downtmp/build.geB/src/tests/pylint.conf 
-- /usr/bin/ionit tests /usr/lib/python3/dist-packages/ionit_plugin.py setup.py
[...]
AssertionError: pylint found issues:
* Module --
--:1:0: F0001: No module named -- (fatal)

This seems to have been fixed upstream already in this commit[2]. Please - 
either
apply this or upgrade to latest upstream (which is just one patch release 
later).

[1]: 
https://ci.debian.net/data/autopkgtest/testing/amd64/i/ionit/27128934/log.gz
[2]: 
https://github.com/PyCQA/pylint/commit/43ecd7dbf34d9a4ed0e3085a9c6e047a8326e131

Thanks,
Nilesh

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

Kernel: Linux 5.18.0-3-amd64 (SMP w/8 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 pylint depends on:
ii  python3 3.10.6-1
pn  python3-astroid 
pn  python3-isort   
pn  python3-logilab-common  
pn  python3-mccabe  
ii  python3-platformdirs2.5.2-1
ii  python3-setuptools  59.6.0-1.2
ii  python3-toml0.10.2-1

Versions of packages pylint recommends:
ii  python3-tk  3.10.7-1

Versions of packages pylint suggests:
pn  pylint-doc  

Bug#1021894: openjfx: FTBFS on arm64 and armhf

[Sebastian Ramacher]

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

openjfx FTBFS on arm64 and armhf for some time now. Let's record that in
the BTS.

https://buildd.debian.org/status/fetch.php?pkg=openjfx=arm64=11.0.11%2B1-1=1651592229=0

:web:compileNativeLinux FAILED
:web:compileNativeLinux (Thread[Task worker for ':' Thread 3,5,main]) 
completed. Took 10 mins 30.851 secs.

FAILURE: Build failed with an exception.

* Where:
Build file '/<>/build.gradle' line: 3922

* What went wrong:
Execution failed for task ':web:compileNativeLinux'.
> Process 'command 'perl'' finished with non-zero exit value 2

* Try:
Run with --debug option to get more log output. Run with --scan to get full 
insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task 
':web:compileNativeLinux'.
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100)
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)
at 
org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
at 
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60)
at 
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97)
at 
org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at 
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98)
at 
org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:626)
at 
org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:581)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at 
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at 
org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Caused by: org.gradle.process.internal.ExecException: Process 'command 'perl'' 
finished with non-zero exit value 2
at 
org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:382)
at 

Bug#1021893: device-tree-compiler: reproducible builds: Embeds build time in in various binaries

[Vagrant Cascadian]

Source: device-tree-compiler
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The build time is embedded in various binaries:

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/device-tree-compiler.html

  /usr/bin/convert-dtsv0

  /build/1st/device-tree-compiler-1.6.1/srcpos.c:101
  vs.
  /build/2/device-tree-compiler-1.6.1/2nd/srcpos.c:101

The attached patch to debian/rules fixes this by passing the default
CFLAGS via EXTRA_CFLAGS, which includes the -ffile-prefix-map compiler
option.

According to my local tests, with this patch applied, device-tree-compiler 
should build
reproducibly on tests.reproducible-builds.org!

Thanks for maintaining device-tree-compiler!

live well,
  vagrant
From 77ddff89156eb55a550238a490e58023476c8efa Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Sun, 16 Oct 2022 18:02:45 +
Subject: [PATCH] debian/rules: Pass default CFLAGS via EXTRA_CFLAGS.

commit 13c4c940e65039052b5be499a848aaa9ffaffaa7 "Enable pylibfdt build
(Closes: #877125)" introduced a regression by removing the default CFLAGS.

This triggered reproducible builds issues with embedded build paths,
because -ffile-prefix-map was no longer getting passed to the
compiler.

The pylibfdt build system ignores CFLAGS, but respects EXTRA_CFLAGS,
so pass all CFLAGS via EXTRA_CFLAGS.
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index b146728..5aae1d5 100755
--- a/debian/rules
+++ b/debian/rules
@@ -15,7 +15,7 @@ export CC = $(DEB_HOST_GNU_TYPE)-gcc
 endif
 
 include /usr/share/dpkg/buildflags.mk
-EXTRA_CFLAGS = -Wno-error
+EXTRA_CFLAGS = $(CFLAGS) -Wno-error
 CPPFLAGS += -I libfdt -I .
 
 %:
-- 
2.37.2



signature.asc
Description: PGP signature

Bug#1021892: pmw: autopkgtest regression: [stavelines ] is deprecated; use [stave m/] instead

[Paul Gevers]

Source: pmw
Version: 1:5.20-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
pmwfrom testing1:5.20-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=pmw

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pmw/27178828/log.gz

doc/examples/ex44
PMW version 5.20
** Warning: [stavelines ] is deprecated; use [stave m/] instead
   Detected near line 6 of doc/examples/ex44
[stave 1 hclef 0 stavelines 1]
->


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021891: rsass: autopkgtest regression: no matching package named `arc-swap` found

[Paul Gevers]

Source: rsass
Version: 0.26.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
rsass  from testing0.26.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 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=rsass

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rsass/27178838/log.gz

debian cargo wrapper: options, profiles, parallel: ['parallel=64'] [] 
['-j64']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/tmp/tmp.3vENjMmwHj/registry/
debian cargo wrapper: options, profiles, parallel: ['parallel=64'] [] 
['-j64']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', 
'-j64', '--target', 'x86_64-unknown-linux-gnu', '--all-targets'],) {}

error: no matching package named `arc-swap` found
location searched: registry `crates-io`
required by package `rsass v0.26.0 (/usr/share/cargo/registry/rsass-0.26.0)`
autopkgtest [08:19:18]: test librust-rsass-dev:default



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021890: groff-base: tbl(?) with prevailing i/fI doesn't process fC[RB] in a cell for tty output, okay for troff?

[наб]

Package: groff-base
Version: 1.22.4-6
Severity: normal

Dear Maintainer,

This is bizarre to me so idk how to even describe it right;
please consider the following reduced example.

-- >8 --
.Dd
.Dt STTY 1
.Os
.Sh DESCRIPTION
.TS
li.
\f(CRispeed \fPnumber
.TE
.TS
li.
\f(CRispeed \fPnumber
.TE
.Pp
.TS
lfI.
\f(CRispeed \fPnumber
.TE
.TS
lfI.
\fRispeed \fPnumber
.TE
.Pp
.TS
li.
\f(CBispeed \fPnumber
.TE
.TS
lfI.
\f(CBispeed \fPnumber
.TE
-- >8 --

This /does/ yield the correct fonts in -Tps: 3xCR, R, 2xCB.
But it does /not/ yield the correct fonts nroff mode (same for man ./):
-- >8 --
$ groff -Tutf8 -P -c -mdoc -t ./repg.1
DDEESSCCRRIIPPTTIIOONN
 _i_s_p_e_e_d _n_u_m_b_e_r
 _i_s_p_e_e_d _n_u_m_b_e_r

 _i_s_p_e_e_d _n_u_m_b_e_r
 ispeed _n_u_m_b_e_r

 _i_s_p_e_e_d _n_u_m_b_e_r
 _i_s_p_e_e_d _n_u_m_b_e_r
-- >8 --

I.e. /all/ of these underlined/italic except the one that has an
explicit \fR.

Soz,
наб

-- System Information:
Debian Release: 11.5
  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

Versions of packages groff-base depends on:
ii  libc6 2.31-13+deb11u4
ii  libgcc-s1 10.2.1-6
ii  libstdc++610.2.1-6
ii  libuchardet0  0.0.7-1

groff-base recommends no packages.

Versions of packages groff-base suggests:
ii  groff  1.22.4-6

-- no debconf information


signature.asc
Description: PGP signature

Bug#994348: python-apt: diff for NMU version 2.3.0+nmu1

[Micha Lenk]

Hi all,

I just realized an alternative implementation was already contributed by 
Michael Vogt on salsa.d.o


https://salsa.debian.org/apt-team/python-apt/-/merge_requests/67

Good to see he ended up with almost the same implementation as I did.

Regards,
Micha

Bug#1006022: closed by Pirate Praveen (already fixed in 5.6.4-1)

[Paul Gevers]

Control: reopen -1

Hi Pirate,

On 16-10-2022 18:03, Debian Bug Tracking System wrote:

Subject:
already fixed in 5.6.4-1
From:
Pirate Praveen 
Date:
16-10-2022 18:00

To:
1006022-d...@bugs.debian.org


closing


I'm not convinced. To give some examples:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/puma/26957707/log.gz

autopkgtest [12:18:03]:  apt-source puma
Get:1 http://deb.debian.org/debian testing/main puma 5.6.4-1 (dsc) [2,087 B]
Get:2 http://deb.debian.org/debian testing/main puma 5.6.4-1 (tar) [311 kB]
Get:3 http://deb.debian.org/debian testing/main puma 5.6.4-1 (diff) 
[9,004 B]


[...]

  1) Error:
TestIntegrationSingle#test_hot_restart_does_not_drop_connections:
Errno::EBADF: Bad file descriptor

/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helpers/integration.rb:50:in 
`close'


/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helpers/integration.rb:50:in 
`teardown'


/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helper.rb:90:in 
`block (5 levels) in run'


/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helper.rb:90:in 
`each'


/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helper.rb:90:in 
`block (4 levels) in run'

/usr/lib/ruby/3.0.0/timeout.rb:97:in `block in timeout'
/usr/lib/ruby/3.0.0/timeout.rb:107:in `timeout'

/tmp/autopkgtest-lxc.8ydn8oqp/downtmp/build.4F8/src/test/helper.rb:89:in 
`block (3 levels) in run'


418 runs, 1135 assertions, 0 failures, 1 errors, 6 skips


https://ci.debian.net/data/autopkgtest/testing/arm64/p/puma/24007200/log.gz

autopkgtest [21:22:10]:  apt-source puma
Get:1 http://deb.debian.org/debian testing/main puma 5.6.4-1 (dsc) [2,087 B]
Get:2 http://deb.debian.org/debian testing/main puma 5.6.4-1 (tar) [311 kB]
Get:3 http://deb.debian.org/debian testing/main puma 5.6.4-1 (diff) 
[9,004 B]


[...]

  1) Failure:
TestBusyWorker#test_multiple_requests_waiting_on_less_busy_worker 
[/tmp/autopkgtest-lxc.vmusro6g/downtmp/build.DoB/src/test/test_busy_worker.rb:80]:

maximum number of concurrent requests needs to be 1.
Expected: 1
  Actual: 2

418 runs, 1125 assertions, 1 failures, 0 errors, 6 skips


https://ci.debian.net/data/autopkgtest/testing/armel/p/puma/26313576/log.gz

autopkgtest [19:18:01]:  apt-source puma
Get:1 http://deb.debian.org/debian testing/main puma 5.6.4-1 (dsc) [2,087 B]
Get:2 http://deb.debian.org/debian testing/main puma 5.6.4-1 (tar) [311 kB]
Get:3 http://deb.debian.org/debian testing/main puma 5.6.4-1 (diff) 
[9,004 B]


[...]

  1) Failure:
TestPumaServer#test_not_drain_on_shutdown 
[/tmp/autopkgtest-lxc.4nhbkp68/downtmp/build.fbR/src/test/test_puma_server.rb:1341]:

Expected 0 to not be equal to 0.

418 runs, 1141 assertions, 1 failures, 0 errors, 6 skips



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021889: pylint breaks pylint-django autopkgtest: ScopeConsumer.__new__() missing 1 required positional argument: 'scope_type'

[Paul Gevers]

Source: pylint, pylint-django
Control: found -1 pylint/2.15.3-1
Control: found -1 pylint-django/2.0.13-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
pylint from testing2.15.3-1
pylint-django  from testing2.0.13-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 pylint 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=pylint

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pylint-django/27163271/log.gz

Running “django-admin startproject testproject”
Running “django-admin startapp testapp”
Running “pylint --version”
pylint 2.15.3
astroid 2.12.10
Python 3.10.7 (main, Sep  8 2022, 14:34:29) [GCC 12.2.0]
Running “pylint -E --load-plugins=pylint_django testapp/”
Exception on node  in file 
'/tmp/autopkgtest-lxc.6ld_wzc5/downtmp/autopkgtest_tmp/testproject/testapp/__init__.py'

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pylint/utils/ast_walker.py", 
line 95, in walk

callback(astroid)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 739, in wrap_func

return with_method(orig_method, *args, **kwargs)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 317, in ignore_import_warnings_for_related_fields
consumer._atomic = ScopeConsumer(new_things, consumer.consumed, 
consumer.scope_type)  # pylint: disable=W0212
TypeError: ScopeConsumer.__new__() missing 1 required positional 
argument: 'scope_type'
Can't write the issue template for the crash in 
/home/debci/.cache/pylint/pylint-crash-2022-10-16-06-16-20.txt because 
of: '[Errno 2] No such file or directory: 
'/home/debci/.cache/pylint/pylint-crash-2022-10-16-06-16-20.txt''

Here's the content anyway:
First, please verify that the bug is not already filled:
https://github.com/PyCQA/pylint/issues/

Then create a new crash issue:
https://github.com/PyCQA/pylint/issues/new?assignees==crash%2Cneeds+triage=BUG-REPORT.yml


Issue title:
Crash  (if possible, be more specific about what made pylint crash)
Content:
When parsing the following file:



```python

```

pylint crashed with a ``AstroidError`` and with the following stacktrace:
```
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
782, in _lint_file

check_astroid_module(module)
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
1049, in check_astroid_module

retval = self._check_astroid_module(
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
1099, in _check_astroid_module

walker.walk(node)
  File "/usr/lib/python3/dist-packages/pylint/utils/ast_walker.py", 
line 95, in walk

callback(astroid)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 739, in wrap_func

return with_method(orig_method, *args, **kwargs)
  File 
"/usr/lib/python3/dist-packages/pylint_django/augmentations/__init__.py", 
line 317, in ignore_import_warnings_for_related_fields
consumer._atomic = ScopeConsumer(new_things, consumer.consumed, 
consumer.scope_type)  # pylint: disable=W0212
TypeError: ScopeConsumer.__new__() missing 1 required positional 
argument: 'scope_type'


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
747, in _lint_files

self._lint_file(fileitem, module, check_astroid_module)
  File "/usr/lib/python3/dist-packages/pylint/lint/pylinter.py", line 
784, in _lint_file

raise astroid.AstroidError from e
astroid.exceptions.AstroidError
```
.
* Module testapp
testapp/__init__.py:1:0: F0002: testapp/__init__.py: Fatal error while 
checking 'testapp/__init__.py'. Please open an issue in our bug tracker 
so we address this. There is a pre-filled template that you can use in 
'/home/debci/.cache/pylint/pylint-crash-2022-10-16-06-16-20.txt'. 
(astroid-error)
Can't write the issue template for the crash in 
/home/debci/.cache/pylint/pylint-crash-2022-10-16-06-16-20.txt because 
of: '[Errno 2] No such file or directory: 

Bug#1021821: systemd: FTBFS with stage1 profile

[Niels Thykier]

On Sat, 15 Oct 2022 14:28:12 +0200 Michael Biebl  wrote:

Am 15.10.22 um 14:01 schrieb Helmut Grohne:
> Source: systemd
> Version: 251.6-1
> Severity: important
> Justification: breaks architecture bootstrap
> Tags: ftbfs patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> Hi,
> 
> the addition of cryptsetup plugins broke the stage1 build. Do you think

> it would be possible to add a native stage1 build pass to salsa-ci such
> that you'd notice earlier? Of course you'd only get the failure then,
> not the patch. ;)
> 
> What happens to break is missing files in dh_install. Clearly, the

> intention was not to include cryptsetup plugins in stage1 and I agree
> with that. Unfortunately, dh_install itself does not allow
> conditionalizing lines in .install files. I'm attaching a patch that
> uses dh-exec to achieve this and hope you like it. If not, maybe we can
> install the plugins from debian rules manually?

Given that dh-exec is basically unmaintained, I'm a bit reluctant to 
switch to it.


The dh-exec package has a maintainer again. (I think this was mentioned 
on IRC as well - repeating here for completeness)


Could you raise this with Niels/debhelper: I do think we need better 
support for build profiles in dh_install.


Personally, I think dh-exec does a great job at providing filters (among 
other features) to debhelper configuration files and I am not currently 
not considering to absorbing them into debhelper itself.


Thanks,
~Niels

Bug#997184: ncurses-hexedit: FTBFS: init.c:390:10: error: format not a string literal and no format arguments [-Werror=format-security]

[Reiner Herrmann]

user debian-rele...@lists.debian.org
usertags 997184 + bsp-2022-10-de-karlsruhe
tags 997184 + patch
thank you

Hi,

the attached patch fixes the build errors caused by the new
GCC version.

Kind regards,
  Reiner
From 8525b3f41ef3acf2130167cc0072c38452253cc0 Mon Sep 17 00:00:00 2001
From: Reiner Herrmann 
Date: Sun, 16 Oct 2022 19:32:38 +0200
Subject: [PATCH] Fix FTBFS with GCC 12

Closes: #997184
---
 debian/patches/gcc12.patch | 246 +
 debian/patches/series  |   1 +
 2 files changed, 247 insertions(+)
 create mode 100644 debian/patches/gcc12.patch

diff --git a/debian/patches/gcc12.patch b/debian/patches/gcc12.patch
new file mode 100644
index 000..540c788
--- /dev/null
+++ b/debian/patches/gcc12.patch
@@ -0,0 +1,246 @@
+Author: Reiner Herrmann 
+Bug-Debian: https://bugs.debian.org/997184
+Description: Fix FTBFS with GCC 12
+ - make sure global variables are declared in only one place
+   to fix "multiple definition" linking errors
+ - use fixed format string to prevent format string vulnerabilities
+
+--- a/src/hexedit.h
 b/src/hexedit.h
+@@ -343,7 +343,7 @@
+ 
+ 
+/* Global structure, keep most global variables here. */
+-struct
++struct Global
+ {
+WINDOW *wmain, *wstatus, *whelp; /* three windows used throughout. */
+unsigned long filesize;  /* size of the file buffer. */
+@@ -365,7 +365,7 @@
+ /* buf end. */
+int beeping; /* Allow beeping or not. */
+int help_msg_count;  /* Number of messages in help menu. */
+-} Globals;
++};
+ 
+ 
+ struct foundit
+@@ -400,7 +400,7 @@
+int s;
+struct Change *base;
+struct Change *top;
+-} UndoStack;
++};
+ 
+ 
+ struct FileNames
+--- a/src/init.c
 b/src/init.c
+@@ -35,6 +35,9 @@
+ 
+ extern char **environ;
+ 
++struct Global Globals;
++extern struct ChangeLog UndoStack;
++
+ 
+/* This is called once at the start of the program.  Handles HEXEDIT
+ * Environment variable, command line arguments, sets up signal
+@@ -385,7 +388,7 @@
+  box (wpopup, 0, 0);
+  wmove (wpopup, 1, (FILE_ERR_WIDTH / 2)
+  - (strlen (msg) / 2));
+- wprintw (wpopup, (char *) msg);
++ wprintw (wpopup, "%s", (char *) msg);
+  wmove (wpopup, FILE_ERR_HEIGHT - 3, (FILE_ERR_WIDTH / 2) -
+ (strlen (strerror (errno)) + strlen ("Reason: ")) / 2);
+  wprintw (wpopup, "Reason: %s", 
+--- a/src/misc.c
 b/src/misc.c
+@@ -26,6 +26,8 @@
+ #endif
+ #endif
+ 
++extern struct Global Globals;
++extern struct ChangeLog UndoStack;
+ 
+ int
+ mappos (int pos)
+--- a/src/undo.c
 b/src/undo.c
+@@ -15,6 +15,8 @@
+ #include "hexedit.h"
+ #include 
+ 
++struct ChangeLog UndoStack;
++extern struct Global Globals;
+ 
+ void
+ pushUndo (int type, unsigned long offset,
+--- a/src/widgets.c
 b/src/widgets.c
+@@ -14,6 +14,8 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
++
+ #define S_BOX_COLOR  (COLOR_PAIR(4) | A_BOLD)
+ 
+ 
+@@ -366,7 +368,7 @@
+if (!rstr.str)
+{
+   wmove (win, 4, boxleft);
+-  wprintw (win, (char *) NOT_ENOUGH_MEMORY);
++  wprintw (win, "%s", (char *) NOT_ENOUGH_MEMORY);
+   getch ();
+   return NULL;
+}
+--- a/src/windows.c
 b/src/windows.c
+@@ -14,6 +14,7 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
+ 
+/* Brings up Jump to offset window, to relocate to a different part
+ * of the file.  Uses one string box and takes input in octal, decimal, 
+--- a/src/calc.c
 b/src/calc.c
+@@ -14,6 +14,8 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
++
+/* Used only for redraw function after Control-C */
+ struct calcEntryBox *bbox;
+ struct calcEntryBox *obox;
+--- a/src/print.c
 b/src/print.c
+@@ -14,6 +14,8 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
++
+ static long findNewline   (unsigned long);
+ static void drawAscii (unsigned long off);
+ static void drawAsciiDump (unsigned long, unsigned long *);
+--- a/src/calckeys.c
 b/src/calckeys.c
+@@ -14,6 +14,7 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
+ 
+ void
+ calcNumberKey (struct calcEntryBox *binbox, struct calcEntryBox *octbox,
+--- a/src/edit.c
 b/src/edit.c
+@@ -15,6 +15,8 @@
+ #include "hexedit.h"
+ #include 
+ 
++extern struct Global Globals;
++
+ /* The routines in this file are very messy and ugly and not much thought
+  * went into thinking how to minimize the amount of code, I only did it
+  * real fast, making every case I could think of a separate code block,
+--- a/src/file.c
 b/src/file.c
+@@ -30,6 +30,8 @@
+ 
+ #include "hexedit.h"
+ 
++extern struct Global Globals;
++
+ struct FileNames *fp = NULL; /* used to traverse the list of files */
+ struct FileNames **pages = NULL; /* node that starts a new page */
+ int current_page = 0;
+--- a/src/filebuf.c
 b/src/filebuf.c
+@@ -15,6 +15,7 @@
+ #include "hexedit.h"
+ 

Bug#1021877: debhelper: please disallow debian/compat in level 14+

[Niels Thykier]

Adam Borowski:

Package: debhelper
Version: 13.10
Severity: wishlist

Hi!
It would be nice if you banned old-style debian/compat in upcoming compat
levels, in favour of the debhelper-compat b-dependency.

This would remove any need to check for missing debhelper dependency, and
allow speeding up buildds by preinstalling debhelper.  99.9% of packages
(61 exceptions in bookworm) use debhelper, yet it currently needs to be
installed with apt+dpkg for every single build, which does take a while.

In theory, there's a lintian check for missing debhelper b-dep, but that's
an extra moving part.  Plus, in the far future, when we drop compat 13,
it'd be less complexity for you.


Meow!
[...]



One concern I have with this proposal is how would one use a non-stable 
compat level? The self-hosted debhelper is a primary consumer of this 
but we also see other packages opt'ing in to experimenting with the 
"latest and greatest".


If I do not add the provides, you cannot request that debhelper-compat 
and if I add the provides (before it is stable), then the dependency 
does not guarantee you get a stable compat level when it is finalized 
(defeating the purpose of a stable compat level).
  The only alternative I see is to now have two Provides per compat 
level (one for the experimental version and one for the stable version). 
 This includes me now having to track experimental compat levels as 
something to be removed (meaning more administrative work for me).


Thanks,
~Niels

Bug#1021888: librust-deflate-dev: impossible to install

[Jonas Smedegaard]

Package: librust-deflate-dev
Version: 1.0.0-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install: Depends on missing package 
librust-gzip-header-1+default-dev

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNMOEQACgkQLHwxRsGg
ASHSFw/+LViZjDgukHKs4L/lU28HGvX9w/oM5ipGKgsrEM0J4kcT6Om6yzg2CCCl
Ss7IZg9zx5kVr2O45Bxo2jl+NDh51WocsiT/tjlOmF8EoPylXlJfxpfIuIvvNArW
GNpt9FhSTzYOIohEf/QWYiC2cdwWA+lek0qyhUPIjaa+1B/j4aSxlbwAwYnr33YN
8t329wAKyhbRDJVRDKeWsspqYAIC7AiVxMOF1EJ/TPjRtA64FBUZkn0NXoCZek9c
LocZSqaSvgiRibhEb/ifDndmkncY2TCt7cvbhjcB9UvGbxiiIRFRnR+W8SrEHEqf
w9ED6rE//jhT3/GYlZ6UaK9b64CbrT7VX5Hkl35NexO2tUucCSgORCetCEdcNsly
j6UV1/3v5KYbX3gRGCvQJO/3zNcEmZlQ88Nt6CbHiQBwbGfpztja7R+v7p2MK63P
fr/GIFE5V08f6pQe0PtDcbjRtFvxx6jA7vO1yg1lz3Bh0UYnGCrwpnLMn67LrF8C
rqfQx0vZyl4dhvQDFrL/56WNETgcJcXyPEdr8UCHHGm+tABzAhogtUwZYtcIS5m7
hXKSY7o1uOY8/hU1WDi9rVV79TFBXYoZTPjZrmUo5tKKBOcUCu6LOzF/hlXJnEEO
YMSe5FpL7WtgmUZ70qrZOnHIPid7Aw48RJccBrZ7stP8g/xhjDU=
=RAGB
-END PGP SIGNATURE-

Bug#1020747: AM_PATH_PYTHON

[Jerome BENOIT]

control: reassign -1 autoconf-archive
control: tags -1 patch

I have just doublechecked: the bug does lie in autoconf-archive .

The faulty code was introduce in commit df89f6cdaade38f3c1c9987be0c5a57c96fc1730
https://github.com/autoconf-archive/autoconf-archive/commit/df89f6cdaade38f3c1c9987be0c5a57c96fc1730

The current code tuple(sys.version_info) gives the 5-tuple (3, 10, 7, 'final', 
0) while
the former code sys.version.split()[0] would give the 3-tuple (3, 10, 7).
So, at first glance, the current code tuple(sys.version_info) should be 
replaced by
tuple(sys.version_info)[:3].

A patch that applied to the current ax_python_devel serial 32 is attached.

Best wishes,
Jerome


On Fri, 30 Sep 2022 14:31:47 + Bastien =?ISO-8859-1?Q?Roucari=E8s?= 
 wrote:

control: reassign -1 automake
control: affects -1 autoconf-archive


Hi,


The macro AM_PATH_PYTHON dos not support 3 level python version...


The bug lie in automake not autoconf-archive 



Could be workarround by a little sed script in order remove micro version on graph tool 
side



Bastien


--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
--- ax_python_devel.m4-s32.original	2022-10-01 17:42:46.0 +0200
+++ ax_python_devel.m4	2022-10-16 18:40:38.873380357 +0200
@@ -125,7 +125,7 @@
 return tuple(map(int, s.strip().replace("rc", ".").split(".")))
 def __init__(self):
 import sys
-self.vpy = tuple(sys.version_info)
+self.vpy = tuple(sys.version_info)[[:3]]
 def __eq__(self, s):
 return self.vpy == self.vtup(s)
 def __ne__(self, s):


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021823: info: memory exhausted for python3.10.info

[Hilmar Preuße]

Am 15.10.2022 um 15:32 teilte Jakub Wilk mit:

Hi Jakub,


info runs out of memory when trying to dump python3.10 docs on stdout:

    $ dpkg-query -W python3.10-doc
    python3.10-doc    3.10.7-2

    $ info python3.10 > /dev/null
    info: memory exhausted

I'm failing to reproduce the issue on my system. Are you able to 
reproduce the issue using the latest git checkout? There were a few 
issues regarding this fixed since latest release.


Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021862: mupen64plus: Backport SDL_SetVideoMode fix to Salsa

[Sven Eckelmann]

On Sunday, 16 October 2022 17:56:23 CEST Brendon wrote:
> Oops. Consider me blind then. You can close this now.

Sorry if this came across that way. I just wanted to let you confirm that this 
is the fix you are talking about. But it sounds like it is.

Thanks,
Sven

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

Bug#1021887: rust-thiserror: please update to 1.0.31

[Jonas Smedegaard]

Source: rust-thiserror
Version: 1.0.30-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to upstream release v1.0.31, needed by projects I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNMM7cACgkQLHwxRsGg
ASG8YQ//V5qhjtceBooirKR/+k0eqpT25gkOgWEEvg4vND4vPwL/j4A6Ju7OgQro
yv2pyW55cc4QoyIwgD87hZonNPO2fhz0CYqYOcx27AvMeAhYaME7wXMZQbhTRkR6
5eDRRVAW9TfigRYwe/Td+Wf3vNTUbFfPZ2JNAXW5o7jTAJy2HoR8sAWRraWcjY1P
Pl7Yr1NCV26+eIvy1cEw3Ep5Nq8uu0RkC22zQM7WkeOtEkAHxI87pLqtmj8NoYL+
r16gHXhl8m/xfkaghwbBtErKGmxcQW/FrKLGWuCGOCXZnTXhxf+GUq5qzw2b0EXW
RBLG9XGovq5jLyau9Z8QqlAEVpLY2PbMh3E0Pxt3cajikqZiJ5s4C4BZa1CDq0Cp
iosarVmiXzQ1TyV9uRPmR5MdqlSFtOEdWtiYZu4AuRnhzIL+hQSFZAOmwKeIuNK5
2GPNUG2Iyufd5uKNMeDisYxVpiA1eb6DJZ+znZFCUFSxBGlJzlcdCb2hTNI2Isq1
O1WgNQtGk8qwphUk0gd4u3fOoMock+aSlKbG2+/7Szf6Z0u43BqqTn7PNrh9WXGu
ZKKl4IYTqWXJR2q3kO5W+QPtlxcnGNvS1pLEaZLM+DMbJrN5Yf4V40F+0WroJ7OG
cGGMnZAEpqso/g7JBXtS1vCJgku6U3DQ75dfR5wQJHPmgJzsKbI=
=UCQ+
-END PGP SIGNATURE-

Bug#1021827: info -o: exit status 0 on error

[Hilmar Preuße]

Control: tags -1 + fixed-upstream

Am 15.10.2022 um 15:47 teilte Jakub Wilk mit:


"info -o" exits with status 0 when it can't find the node:

     $ info -o /dev/null lolcow
     info: No menu item 'lolcow' in node '(dir)Top'

     $ echo $?
     0

In contrast, if I omit the -o option, it exits with status 1, as it should:

     $ info lolcow
     info: No menu item 'lolcow' in node '(dir)Top'

     $ echo $?
     1


Fixed in git, tagging.

commit 15408a7b46ae1c0deadaf386481cb32a91208374
Author: Gavin Smith 
Date:   Sun Oct 16 12:35:37 2022 +0100

* info/info.c (main) <--output>: Exit with status of 1, not 0,
if there was an error.  Report from Hilmar Preusse .

H.
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021714: lists.debian.org: Request for new mailing list: collab-maint (was: Evolving away from source package realms)

[Andreas Metzler]

On 2022-10-13 Santiago Ruano Rincón  wrote:
> Package: lists.debian.org
> Severity: wishlist

> Dear list masters and fellow Debian peers,

> I hereby would like to propose to create a mailing list for
> collaborative maintenance.

> Name: debian-collab-maint

> Rationale:

> El 13/10/22 a las 07:02, Tobias Frost escribió:
[...]
> Other than the salsa Debian group, I think it would be useful to have a
> mailing list to share the responsibility of packages, and at the same
> time, reduce the personal "ownership" of them. Packages with Maintainer:
[...]

Hello,

I am not sure this is the right way.

* It is already possible to avoid personal e-mail adresses as maintainer
  using team+...@tracker.debian.org

* Scalability: If this was used for many packages the mailing would just
  be too noisy. Take a look at e.g. debian-qa-packages@ldo, which is
  imho unreadable.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1017304: libmateweather: diff for NMU version 1.26.0-1.1

[Mike Gabriel]

Hi Reiner,

On  Sa 15 Okt 2022 18:16:49 CEST, Reiner Herrmann wrote:


Control: tags 1017304 + patch
Control: tags 1017304 + pending

Dear maintainer,

I've prepared an NMU for libmateweather (versioned as 1.26.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
  Reiner


thanks for doing the NMU. I have updated the packaging Git with your .debdiff.

Greets,
Mike
--

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

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



pgp9IJUEFPi9G.pgp
Description: Digitale PGP-Signatur

Bug#1019554: Stamp files are not updated

[Helge Kreutzmann]

Hello Lance,
On Fri, Oct 07, 2022 at 12:34:33PM +, Lance Lin wrote:
> I believe I've found the issue! Sorry it has taken so long to get back to you 
> but I believe I have an answer.
> 
> It seems to be related to an inadequate cleanup. I don't have a great 
> explanation but I found something that works.
> 
> The -33 version that removed the symlinks *somehow* (I am not sure) corrupted 
> the whole install. I've found that
> uninstalling anacron, removing the files associated with anacron and then 
> re-installing the package (-35) will 
> 
> yield a service that works.
> 
> Specifically, I removed:
> /var/lib/systemd/deb-systemd-helper-*/ ... anacron files [might not be 
> needed?]
> /var/lib/dpkg/info/anacron.* files [might not be needed?]
> /var/spool/anacron
> /etc/anacrontab [I think this file is the problem!!]
> 
> Since you already have cron files, perhaps you could back them up, uninstall 
> anacron, remove the files, and then
> re-install anacron (-35), and then overlay your existing cron files? Would 
> you be so kind to test this out on 
> your machine and see if this fixes it?

I did the following:
apt-get remove --purge anacron

root@twentytwo:~# ls /var/lib/systemd/deb-systemd-helper-* | grep anacron
root@twentytwo:~#
root@twentytwo:~# LC_ALL=C ls /var/lib/dpkg/info/anacron*
ls: cannot access '/var/lib/dpkg/info/anacron*': No such file or directory
root@twentytwo:~# LC_ALL=C ls /var/spool/anacron
ls: cannot access '/var/spool/anacron': No such file or directory
root@twentytwo:~# LC_ALL=C ls /etc/anacrontab
ls: cannot access '/etc/anacrontab': No such file or directory

root@twentytwo:~# mkdir ~/crontmp
root@twentytwo:~# mv -iv /etc/cron* ~/crontmp/
Datei umbenannt '/etc/cron.d' -> '/root/crontmp/cron.d'
Datei umbenannt '/etc/cron.daily' -> '/root/crontmp/cron.daily'
Datei umbenannt '/etc/cron.hourly' -> '/root/crontmp/cron.hourly'
Datei umbenannt '/etc/cron.monthly' -> '/root/crontmp/cron.monthly'
Datei umbenannt '/etc/crontab' -> '/root/crontmp/crontab'
Datei umbenannt '/etc/cron.weekly' -> '/root/crontmp/cron.weekly'

# apt-get install anacron

and then moved the cron files back.

root@twentytwo:~# LC_ALL=C ls -l /var/spool/anacron
total 0
-rw--- 1 root root 0 Oct 16 18:31 cron.daily
-rw--- 1 root root 0 Oct 16 18:31 cron.monthly
-rw--- 1 root root 0 Oct 16 18:31 cron.weekly

I report to you tomorrow if cron.daily gets updated …

> Thank you for your help in tracking this down!

Thanks for fixing it so swiftly and promptly.

Greetings

   Helge



-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1010957: closed by Debian FTP Masters (reply to Colin Watson ) (Bug#1010957: fixed in man-db 2.11.0-1)

[Johannes Schauer Marin Rodrigues]

Hi Colin,

Quoting Debian Bug Tracking System (2022-10-15 17:30:07)
> This is an automatic notification regarding your Bug report
> which was filed against the src:man-db package:
> 
> #1010957: man-db: unreproducible index.db: contents depend on directory read 
> order
> 
> It has been closed by Debian FTP Masters  
> (reply to Colin Watson ).

thank you! I just confirmed that man-db 2.11.0-1 indeed fixes this and removed
my workaround from mmdebstrap:

https://gitlab.mister-muffin.de/josch/mmdebstrap/commit/aac7157820c6e278e140e132d25bdcce979fd4bc

cheers, josch

signature.asc
Description: signature

Bug#1021862: mupen64plus: Backport SDL_SetVideoMode fix to Salsa

[Brendon]

Oops. Consider me blind then. You can close this now.

Cheers,
Brendon



sent with FairEmail

Oct 16, 2022 03:40:03 Sven Eckelmann :

> On Sunday, 16 October 2022 10:16:58 CEST you wrote:
>> Package: mupen64plus
>> Severity: important
>> X-Debbugs-Cc: ed7-aspire4...@hotmail.com
>> 
>> mupen64plus is currently unusuable with the latest SDL (at least in 
>> bookworm).
> 
> This is impossible. This package is a meta-package without dependency to SDL
> 
>> 
>> A fix has been patched into upstream:
>> https://github.com/mupen64plus/mupen64plus-core/pull/970
>> 
>> There are discussions of a new release:
>> https://github.com/mupen64plus/mupen64plus-core/issues/973
>> but it's best to backport the patch to salsa for now just in case the 
>> discussion goes nowhere.
>> 
>> I don't know whether that alone fixes the problem though, but I'm pretty 
>> sure it should still build.
> 
> Can you please tell me what the difference is there to the version 2.5-9 of
> libmupen64plus2 [1]
> 
> 
> Kind regards,
>     Sven
> 
> https://tracker.debian.org/news/1372713/accepted-mupen64plus-core-25-9-source-into-unstable/

Bug#1021886: moc: Please allow URLs to start with https

[Martin Quinson]

Package: moc
Version: 1:2.6.0~svn-r3005-2.1
Severity: wishlist
Tags: patch

Hello,

it would be nice to be able to play online streams which URL starts with
https:// instead of http://

The idea and patch comes from:
https://github.com/jonsafari/mocp/pull/32/files

I'm using this patch locally and it works for me.

Thanks in advance,
Mt

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

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

Versions of packages moc depends on:
ii  libasound2    1.2.7.2-1
ii  libc6 2.35-1
ii  libcurl3-gnutls   7.85.0-1
ii  libdb5.3  5.3.28+dfsg1-0.10
ii  libfaad2  2.10.0-2+b1
ii  libflac8  1.3.4-2
ii  libgcc-s1 12.2.0-3
ii  libid3tag0    0.15.1b-14
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-1
ii  libltdl7  2.4.7-4
ii  libmad0   0.15.1b-10.1+b1
ii  libmagic1 1:5.41-4
ii  libmodplug1   1:0.8.9.0-3
ii  libmpcdec6    2:0.1~r495-2
ii  libncursesw6  6.3+20220423-2
ii  libogg0   1.3.5-1
ii  libopusfile0  0.12-2
ii  libpopt0  1.18-3
ii  librcc0   0.2.13+ds-2
ii  libresid-builder0c2a  2.1.1-15+b1
ii  libsamplerate0    0.2.2-2
ii  libsidplay2   2.1.1-15+b1
ii  libsidutils0  2.1.1-15+b1
ii  libsndfile1   1.1.0-2
ii  libspeex1 1.2.1-1
ii  libstdc++6    12.2.0-3
ii  libtagc0  1.12-1+b1
ii  libtinfo6 6.3+20220423-2
ii  libvorbisfile3    1.3.7-1
ii  libwavpack1   5.5.0-1

moc recommends no packages.

Versions of packages moc suggests:
ii  moc-ffmpeg-plugin  1:2.6.0~svn-r3005-2

-- no debconf information

--- a/files.c
+++ b/files.c
@@ -85,6 +85,7 @@
 inline int is_url (const char *str)
 {
 	return !strncasecmp (str, "http://;, sizeof ("http://;) - 1)
+		|| !strncasecmp (str, "https://;, sizeof ("https://;) - 1)
 		|| !strncasecmp (str, "ftp://;, sizeof ("ftp://;) - 1);
 }
 


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

Bug#1021074: postgresql-15: collation version mismatch warnings on upgrading to 15-rc1

[Diederik de Haas]

On Sunday, 16 October 2022 17:15:55 CEST Christoph Berg wrote:
> > > HINT:  Rebuild all objects in this database that use the default
> > > collation
> > > and run ALTER DATABASE template1 REFRESH COLLATION VERSION,
> > > or build PostgreSQL with the right library version.
> > 
> > As I didn't know how to fix that issue ...
> 
> that's
> https://www.postgresql.org/docs/15/sql-altercollation.html#SQL-ALTERCOLLATIO
> N-NOTES in action. I'm not aware of any differences between these libc
> versions, so just running "alter databse refresh collation version"
> would have been enough.

The 'AND run' part of the hint was what brought confusion/doubt for me as it 
suggested 2 different things, whereas only the latter was explained/detailed.

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

Bug#1021885: apt: please add a command for "give configured $DEFAULTVENDOR mirror"

[Adam Borowski]

Package: apt
Version: 2.5.3+b1
Severity: wishlist

Hi!
I see that random programs parse apt's configuration to obtain the default
mirror for use with chroots/containers/etc.  And they all do it in their own
hacky and incomplete ways.  Thus eg. piuparts fails to understand 822-style
sources, and so on.

I started looking how to implement that, and went:
 * `apt-cache policy` has that needed information
 * /etc/dpkg/origins/default gives $Vendor
 * ... so the highest-priority entry with "release o=$Vendor" should do
 * but is that o= or l= ?
You see where it is going...

As you acolytes of the Cow know the right way to do so, while me and all
those piudockernetesemu authors don't -- could you please implement
`apt-cache defaultmirror` or such?


Meow!

Bug#1021884: korganizer segfaults when adding new event

[ael]

Package: korganizer
Version: 4:22.08.0-2
Severity: normal

Dear Maintainer,

Kalarm stopped working on this testing system a few days ago, so I
removed it and tried to use the inbuilt support for events and reminders
in korganizer.

It seem to be hit and miss whether new events are recorded, but now I
get a consistent segfault when adding a new event. That new event might
overlap the time slot for an existing event. But whatever, a seg fault
is always serious

I ran under gdb to try to get some diagnostics. gdb.txt session log
attached.

ael


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/8 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)

Versions of packages korganizer depends on:
ii  kdepim-runtime   4:22.08.0-2
ii  kio  5.98.0-1
ii  libc62.35-3
ii  libgcc-s112.2.0-3
ii  libkf5akonadicalendar5abi1 [libkf5akonadicalendar5-22.08]4:22.08.0-2
ii  libkf5akonadicontact5 [libkf5akonadicontact5-22.08]  4:22.08.0-2
ii  libkf5akonadicore5abi2 [libkf5akonadicore5-22.08]4:22.08.0-2
ii  libkf5akonadinotes5 [libkf5akonadinotes5-22.08]  4:22.08.0-2
ii  libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-22.08]  4:22.08.0-2
ii  libkf5calendarcore5abi2  5:5.98.0-1
ii  libkf5calendarsupport5abi1 [libkf5calendarsupport5-22.08]4:22.08.0-2
ii  libkf5calendarutils5 [libkf5calendarutils5-22.08]4:22.08.0-2
ii  libkf5completion55.98.0-1
ii  libkf5configcore55.98.0-1
ii  libkf5configgui5 5.98.0-1
ii  libkf5configwidgets5 5.98.0-1
ii  libkf5contacts5  5:5.98.0-1
ii  libkf5coreaddons55.98.0-1
ii  libkf5crash5 5.98.0-1
ii  libkf5eventviews5abi1 [libkf5eventviews5-22.08]  4:22.08.0-2
ii  libkf5holidays5  1:5.98.0-1
ii  libkf5i18n5  5.98.0-1
ii  libkf5iconthemes55.98.0-2
ii  libkf5identitymanagement5 [libkf5identitymanagement5-22.08]  22.08.0-2
ii  libkf5incidenceeditor5abi1 [libkf5incidenceeditor5-22.08]22.08.0-2
ii  libkf5itemmodels55.98.0-1
ii  libkf5itemviews5 5.98.0-1
ii  libkf5jobwidgets55.98.0-1
ii  libkf5kcmutils5  5.98.0-1
ii  libkf5kiocore5   5.98.0-1
ii  libkf5kiogui55.98.0-1
ii  libkf5kiowidgets55.98.0-1
ii  libkf5kontactinterface5 [libkf5kontactinterface5-22.08]  22.08.0-2
ii  libkf5libkdepim5 [libkf5libkdepim5-22.08]4:22.08.0-2
ii  libkf5mailtransport5 [libkf5mailtransport5-22.08]22.08.0-2
ii  libkf5mime5abi1 [libkf5mime5-22.08]  22.08.0-2
ii  libkf5newstuffcore5  5.98.0-1
ii  libkf5newstuffwidgets5   5.98.0-1
ii  libkf5notifications5 5.98.0-1
ii  libkf5parts5 5.98.0-1
ii  libkf5pimcommon5abi2 [libkf5pimcommon5-22.08]4:22.08.0-2
ii  libkf5pimcommonakonadi5abi1 [libkf5pimcommonakonadi5-22.08]  4:22.08.0-2
ii  libkf5widgetsaddons5 5.98.0-1
ii  libkf5windowsystem5  5.98.0-1
ii  libkf5xmlgui55.98.0-1
ii  libkuserfeedbackcore11.2.0-2
ii  libkuserfeedbackwidgets1 1.2.0-2
ii  libqt5core5a 5.15.4+dfsg-5
ii  libqt5dbus5  5.15.4+dfsg-5
ii  libqt5gui5   5.15.4+dfsg-5
ii  libqt5widgets5   5.15.4+dfsg-5
ii  libstdc++6   12.2.0-3

Versions of packages korganizer recommends:
pn  kalendarac  

korganizer 

Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Philipp Kern]

tag 1013009 + pending
tag 1004638 + pending
thanks

On Sun, Oct 16, 2022 at 03:53:13PM +0200, Philipp Kern wrote:
> I think it's still worthwhile to upload this build.

While arm64/armhf remains unfixed (and could have its own t-p-u upload
based on the +0 version plus Ubuntu's patch), there's also a question if
a newer version would actually fix the issue.

I talked to Sebastian on IRC and we agreed that I'd upload the Ubuntu
patch for now. It doesn't make anything worse and will allow building
on amd64 again.

nmudiff attached.

Kind regards
Philipp Kern
diff -Nru openjfx-11.0.11+1/debian/changelog openjfx-11.0.11+1/debian/changelog
--- openjfx-11.0.11+1/debian/changelog  2022-05-03 16:48:31.0 +0200
+++ openjfx-11.0.11+1/debian/changelog  2022-10-16 12:19:38.0 +0200
@@ -1,3 +1,14 @@
+openjfx (11.0.11+1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop build-dependency on ffmpeg, openjfx isn't source-compatible with
+ffmpeg 5.0. Closes: #1004638.
+  * Build-depend on g++-11, source not compatible with g++ 12.
+Closes: #1013009.
+(Both patches taken from Ubuntu, thanks to Steve Langasek)
+
+ -- Philipp Kern   Sun, 16 Oct 2022 12:19:38 +0200
+
 openjfx (11.0.11+1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru openjfx-11.0.11+1/debian/control openjfx-11.0.11+1/debian/control
--- openjfx-11.0.11+1/debian/control2022-05-03 15:33:58.0 +0200
+++ openjfx-11.0.11+1/debian/control2022-10-16 12:19:38.0 +0200
@@ -10,13 +10,12 @@
default-jdk,
default-jdk-doc,
flex,
+   g++-11,
gperf,
gradle (>= 4.4),
gradle-debian-helper (>= 2.0),
junit4,
libasound2-dev,
-   libavcodec-dev,
-   libavformat-dev,
libgl1-mesa-dev,
libgstreamer-plugins-base1.0-dev,
libgstreamer1.0-dev,
diff -Nru openjfx-11.0.11+1/debian/patches/disable-ffmpeg.patch 
openjfx-11.0.11+1/debian/patches/disable-ffmpeg.patch
--- openjfx-11.0.11+1/debian/patches/disable-ffmpeg.patch   1970-01-01 
01:00:00.0 +0100
+++ openjfx-11.0.11+1/debian/patches/disable-ffmpeg.patch   2022-10-16 
12:19:38.0 +0200
@@ -0,0 +1,24 @@
+Description: Don't build ffmpeg plugin when ffmpeg is disabled
+Author: Steve Langasek 
+Last-Update: 2022-09-21
+Bug-Debian: https://bugs.debian.org/1004638
+
+Index: openjfx-11.0.11+1/build.gradle
+===
+--- openjfx-11.0.11+1.orig/build.gradle
 openjfx-11.0.11+1/build.gradle
+@@ -3715,14 +3715,6 @@ project(":media") {
+ }
+ }
+ }
+-} else {
+-// Building fxavcodec plugin (libav plugin)
+-exec {
+-commandLine ("make", "${makeJobsFlag}", "-C", 
"${nativeSrcDir}/gstreamer/projects/linux/avplugin")
+-args("CC=${mediaProperties.compiler}", 
"LINKER=${mediaProperties.linker}",
+- "OUTPUT_DIR=${nativeOutputDir}", 
"BUILD_TYPE=${buildType}",
+- "BASE_NAME=avplugin", IS_64 ? "ARCH=x64" 
: "ARCH=x32")
+-}
+ }
+ }
+ }
diff -Nru openjfx-11.0.11+1/debian/patches/series 
openjfx-11.0.11+1/debian/patches/series
--- openjfx-11.0.11+1/debian/patches/series 2022-05-03 15:27:46.0 
+0200
+++ openjfx-11.0.11+1/debian/patches/series 2022-10-16 12:19:38.0 
+0200
@@ -18,3 +18,4 @@
 no-error_deprecated-declarations.patch
 32-gradle-compatibility.patch
 36-disable-swt-on-32bit-arch.patch
+disable-ffmpeg.patch
diff -Nru openjfx-11.0.11+1/debian/rules openjfx-11.0.11+1/debian/rules
--- openjfx-11.0.11+1/debian/rules  2022-05-03 15:27:46.0 +0200
+++ openjfx-11.0.11+1/debian/rules  2022-10-16 12:19:38.0 +0200
@@ -3,6 +3,8 @@
 DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 
+export CXX=g++-11
+
 # FIXME: looks like s390x is recognized as a 32bit arch ...
 # more heap on s390x needed
 ifneq (,$(filter $(DEB_HOST_ARCH), s390x))

Bug#1021883: rust-image: please upgrade to 0.24.2

[Jonas Smedegaard]

Source: rust-image
Version: 0.23.14-2
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to upstream release 0.24.2, needed by projects I am
preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNMHloACgkQLHwxRsGg
ASHeCRAAkwIe6uLDHZiA3HOT321LLvtXB1O+cqSLXD639WunSB6sItNC+CAKar7L
iLDT2YJQoyKUKMoVmiCcxhxTjnglumD/2FB/WfUI3AYJW05EZlQR5IPWf+WGhwuZ
SJa9hkBbQZBFpTr1G8ioBtnhjQnTVvOVtiD8n8S1ABmXQUygxiHYGJMCAbRWjgRp
yWKJClXg6+3y6TiG07YTUV4Fq7lNxai3qj7R8IKwuicgXMXAEl0c64q/ZxJi6tSu
zHXxHws3lMookgFk+7QyQ4/lSTyprZjQVl+0R9dQUBp0+SYuf+70vHbLiR7EzsXO
zbdojT5MP3yjFixcskXHNPq9uyA5DF3SsR05gmriOJrn4K2iFoZTf6PgYVnziPbz
6UHmAqOSg/kmn1O5FmUoCau+CJ0C0xM7vX0eG9gWeutUUPN8xEF4CR4eDw0IiQF3
hx7yjzl4Yn1eZNEjSPz5lWOfATc+Vcwq03gsYtLQ7SnqOrhawNT0Ip0H2GF/Crlv
mroF494iRFsucye7YLFx4xzJUY6aJR5jqmDXbTl8wAiXDovVTpE0Cj67OJ3+NtAj
HsnFZD6VFdFEx2ppPmEc1tIdS+0Yta5daAP6Vw1H6Gz17kDWAgvPBuTDKR45CG92
tBikClcL9bID+nPz2cm11A+M6WXrHi6WwhFSNDiRqmgh2tcFcMs=
=tlpU
-END PGP SIGNATURE-

Bug#1021882: ros2-rosidl: FTBFS on mipsel: test failures

[Sebastian Ramacher]

Source: ros2-rosidl
Version: 3.3.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=ros2-rosidl=mipsel=3.3.0-2=1665762594=0


94% tests passed, 1 tests failed out of 16

Label Time Summary:
cppcheck  =   3.13 sec*proc (2 tests)
cpplint   = 174.44 sec*proc (2 tests)
gtest =   4.96 sec*proc (7 tests)
linter= 198.87 sec*proc (6 tests)
uncrustify=  21.30 sec*proc (2 tests)

Total Test time (real) = 120.04 sec

The following tests FAILED:
  2 - cpplint_rosidl_generated_cpp (Timeout)
Errors while running CTest
make[1]: *** [Makefile:74: test] Error 8

Cheers
-- 
Sebastian Ramacher

Bug#998206: calendar: cronjob processes all users’ calendars as root, allowing information disclosure

[Philipp Kern]

Hi,

On Wed, Dec 08, 2021 at 12:11:28PM +, Thorsten Glaser wrote:
> Michael Meskes dixit:
> 
> >I did some more testing and it seems this simple patch fixes the issue:
> 
> I think you should still include a setgroups(0, NULL) call there.
> 
> Personally I’d prefer setres[ug]id() because that makes the intent
> more explicit even when the effect is the same, but… I’ll let you
> and the security team decide.

Gentle bump for this issue. Also shouldn't patching out setusercontext
and having no substitute get a CVE? >:)

calendar.c forks, so there is no need to regain privileges post
setuid(). I'm kinda with tg in that setres[ug]id() makes the intent
clearer instead of relying on uid==0 behavior.

Kind regards
Philipp Kern

Bug#885563: Bug#887649: Bug#885563: vte: Do not release with Buster

[Cyril Brulebois]

Philipp Kern  (2022-10-16):
> Unfortunately it doesn't look like there was progress on #887649 this
> cycle either. So I fear that we'll end up needing to tag both #887649
> and #885563 bookworm-ignore. :(

I'm keeping an open mind but given the remaining time, and the otherwise
important workload on firmware and other things, it looks to me working
on this is likely to trigger more immediate questions/problems than
we'll have time to figure out before it's time to release.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#997174: netdiag: FTBFS: statnet.c:471:32: error: format not a string literal and no format arguments [-Werror=format-security]

[Michael Meskes]

Hi Reiner,

> I've prepared an NMU for netdiag (versioned as 1.2-1.2) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

Please go ahead, I wouldn't mind it being uploaded without delay.

Thanks,
Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De
Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org

Bug#1021881: build-essential: please include debhelper

[Adam Borowski]

Package: build-essential
Version: 12.9
Severity: wishlist

Hi!
I think it's time to revisit inclusion of debhelper into build-essential.
The last times it was formally proposed were five-digit bug numbers, and
Debian has changed a lot since then -- 99.82% packages in bookworm use
debhelper in some form (61 exceptions out of 33401).

My real reason: currently, every time a buildd installs dependencies, it
needs to manually add debhelper+deps after cloning the chroot.  This does
take time:
debootstrap --variant=buildd unstable x 
http://apt-rosy.angband.pl:3142/debian
time chroot x apt-get install -y debhelper
  → 7.888s
  (on an 8-way btrfs raid0 of optane disks, w/o eatmydata)
Many years ago, a reason "why not" I heard was that we'd fail to find
missing build-depends on debhelper.  That's not a concern anymore: new
packages B-Dep on debhelper-compat instead, and old ones can be spotted
with a lintian check.  I've also filed #1021877 asking to disallow
debian/compat in levels 14+, thus making sure such missing dependencies
won't ever creep back in (b-essential would guarantee dh 13 in bullseye+).

Policy reason: in #64827 you punted the request to debian-policy, as
their definition is "packages needed to build a C/C++ hello-world".
These days, using dh is not only "best practice", I even had ftp-masters
REJECT a package of mine because of using dirty tricks intead of
debhelper.  Thus, we can say that it's required in practice.

Ie, debhelper is truly ubiquitous, unlike C/C++ in the perl-python-go-
rust-haskell-font-docs world.


Meow!

Bug#1021074: postgresql-15: collation version mismatch warnings on upgrading to 15-rc1

[Diederik de Haas]

On zaterdag 1 oktober 2022 16:19:19 CEST you wrote:
> The main part of the warnings, is this:
> WARNING:  database "template1" has a collation version mismatch
> DETAIL:  The database was created using collation version 2.34, but the
> operating system provides version 2.35. 
> HINT:  Rebuild all objects in this database that use the default collation
> and run ALTER DATABASE template1 REFRESH COLLATION VERSION, 
> or build PostgreSQL with the right library version.

As I didn't know how to fix that issue and didn't know what kind of effect it 
would have when I'd put actual data in the DBs, I purged all the postgresql 
packages and installed them anew.

Feel free to close the issue if it's not worth pursuing it.

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

Bug#844321: unison: Please update to latest upstream version

[Daniel Reichelt]

*bump*


On Mon, 20 May 2019 16:31:05 +0200 =?UTF-8?Q?St=c3=a9phane_Glondu?= 
 wrote:


> Le 20/05/2019 à 16:06, Christoph Groth a écrit :
> > Unison 2.51.2 that has been released in January 2018 has a new feature
> > that is very useful for synchronizing, for example, '.git' directories:
> >
> >> Add a new preference, 'atomic', for specifying directories that should
> >> be treated atomically.
> >
> > It would be great to see this in Debian soon!
>
> Indeed, this new feature looks interesting!
>
> I will look into this when Buster is released.
>
> Cheers,
>
> --
> Stéphane
>
>

Bug#1021880: librust-image+default-dev: impossible to install

[Jonas Smedegaard]

Package: librust-image+default-dev
Version: 0.23.14-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package librust-image+default-dev cannot be satisfied.

As a build-dependency on my pbuilder setup, it fails like this:

The following packages have unmet dependencies:
 pbuilder-satisfydepends-dummy : Depends: librust-image-0.23+default-dev which 
is a virtual package, provided by:
  - librust-image+default-dev 
(0.23.14-2), but it is not installable

At the command-line a bit more is revealed:

# LANG=C apt install librust-image+default-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 librust-png+deflate-dev : Depends: librust-deflate-0.8+default-dev (>= 
0.8.2-~~) but it is not installable
E: Unable to correct problems, you have held broken packages.


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNMEK4ACgkQLHwxRsGg
ASHvGg/7Boy3eIa2+uAX2RJRJHUomMjrrLss4j/yAcfYXSbaCrou6kulnGfQMkuy
CsFRkSG+SxQ9sdgQ6sLZfXXLr3OwQ5d36wR4uZSxSf31KK1ttalSc0H2y2oGSg7g
WrEDpglP+oVZ10RoaI1I52zSFnDpDRo3xLPWicAT5MyWRfjNyDBiAcbD7dKOYL6k
TWFToUqw+egBtCVL/FEdnHTqvJ5w5O4Ekuq1ynmCrxdo0hoJZn2Hy32jiGgFNl+P
FJlLq+lhm/TSc5riR/pBaaHuZeWwhW8d+A7l1f2Ih0pYkTq6JmTwRIK6CRRDWN/e
BfuU+Y+paD5khfSO8TtBvSPr9b0ysVSVOYwtdck70pkSdQOodbmJKxWGI1c/xLQx
Ujy03DqEupPBfrOQsC7wLf24B1m13IrEYKUwfnDesml/wwDLjAYexJWQkrEnyBDW
MJqNDGL6XCklQ7b+G+hlkQgsQB82CaQJY/q4HhFi6AwecM7dBTSM6mq6qtsfQiah
MSHyT5m1IhJI8OU5wP6b5KdDEVvALKO3MF57CThO4u/MjdCkPQRdHeUbPnC9fpAX
SNp0SnCZYpKR+4hjjOB+mTX/c/VNHSa1fLLG7QwSe6JwKg+f7ELTUnhwvziQafkQ
a9DETi+6GU9WM7OYnUjMGi9M7jnsHNdTS4F3CBfL82/7Tm6bKWM=
=r2Xm
-END PGP SIGNATURE-

Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Philipp Kern]

Hey,

On 16.10.22 14:02, Sebastian Ramacher wrote:

I was looking into applying Ubuntu's patch to Debian. It still has the
issue that the builds on arm64 and armhf fail. Reverting to 11.0.11+0
seems to fix that.


So we definitely need the g++-11 dependency as well. I guess I was 
misled by the most recent logs now failing due to ffmpeg, but the 
earlier log failed differently - that's true.


I think it's still worthwhile to upload this build. It looks like the 
getJumpIsland* code is guarded by an JUMP_ISLANDS ifdef (and newly 
introduced in +1). But it's also hard-enabled for ARM64 specifically:


| #if CPU(ARM64) && CPU(ADDRESS64)
| #define USE_JUMP_ISLANDS 1
| #endif

Did I expect to run into an embedded copy of WebKit? Not really. We are 
also already turning off the JIT for armel through a patch.


Kind regards
Philipp Kern

Bug#1004963: Bug#1014977: libde265: CVE-2022-1253 CVE-2021-36411 CVE-2021-36410 CVE-2021-36408 CVE-2021-35452

[Philipp Kern]

tags -1 + pending
thanks

Hey Moritz,

On Fri, Jul 15, 2022 at 05:48:41PM +0200, Moritz Mühlenhoff wrote:
> The following vulnerabilities were published for libde265.
[...]

Thanks for clearly linking to the upstream commits, that was very
helpful! Compared to the older bug these were quite straightforward to
apply. The CVEs referenced by #1004963 are still open in upstream's
bugtracker.

Attached is the diff of the NMU I just uploaded to DELAYED/2-days.

Kind regards and thanks
Philipp Kern
diff -Nru libde265-1.0.8/debian/changelog libde265-1.0.8/debian/changelog
--- libde265-1.0.8/debian/changelog 2020-12-16 16:32:29.0 +0100
+++ libde265-1.0.8/debian/changelog 2022-10-16 15:26:20.0 +0200
@@ -1,3 +1,17 @@
+libde265 (1.0.8-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Import upstream fixes for CVE-tracked vulnerabilities
+(Closes: #1014977)
+- CVE-2022-1253
+- CVE-2021-36411
+- CVE-2021-36410
+- CVE-2021-36409
+- CVE-2021-36408
+- CVE-2021-35452
+
+ -- Philipp Kern   Sun, 16 Oct 2022 15:26:20 +0200
+
 libde265 (1.0.8-1) unstable; urgency=medium
 
   * Update to debhelper compat level 13 and add debian/not-installed
diff -Nru libde265-1.0.8/debian/patches/0001-CVE-2022-1253.patch 
libde265-1.0.8/debian/patches/0001-CVE-2022-1253.patch
--- libde265-1.0.8/debian/patches/0001-CVE-2022-1253.patch  1970-01-01 
01:00:00.0 +0100
+++ libde265-1.0.8/debian/patches/0001-CVE-2022-1253.patch  2022-10-16 
15:19:58.0 +0200
@@ -0,0 +1,50 @@
+From 8e89fe0e175d2870c39486fdd09250b230ec10b8 Mon Sep 17 00:00:00 2001
+From: Dirk Farin 
+Date: Tue, 5 Apr 2022 09:52:57 +0200
+Subject: [PATCH] error on out-of-range cpb_cnt_minus1 (oss-fuzz issue 27590)
+
+---
+ libde265/sps.cc | 5 -
+ libde265/vui.cc | 6 ++
+ 2 files changed, 10 insertions(+), 1 deletion(-)
+
+Index: libde265-1.0.8/libde265/sps.cc
+===
+--- libde265-1.0.8.orig/libde265/sps.cc
 libde265-1.0.8/libde265/sps.cc
+@@ -425,7 +425,10 @@ de265_error seq_parameter_set::read(erro
+ 
+   vui_parameters_present_flag = get_bits(br,1);
+   if (vui_parameters_present_flag) {
+-vui.read(errqueue, br, this);
++de265_error err = vui.read(errqueue, br, this);
++if (err) {
++  return err;
++}
+   }
+ 
+ 
+Index: libde265-1.0.8/libde265/vui.cc
+===
+--- libde265-1.0.8.orig/libde265/vui.cc
 libde265-1.0.8/libde265/vui.cc
+@@ -201,6 +201,9 @@ de265_error video_usability_information:
+ if (!low_delay_hrd_flag[i])
+ {
+   READ_VLC_OFFSET(cpb_cnt_minus1[i], uvlc, 0);
++  if (cpb_cnt_minus1[i] > 31) {
++  return DE265_ERROR_CODED_PARAMETER_OUT_OF_RANGE;
++  }
+ }
+ 
+ for (nalOrVcl = 0; nalOrVcl < 2; nalOrVcl++)
+@@ -361,6 +364,9 @@ de265_error video_usability_information:
+ if (vui_hrd_parameters_present_flag) {
+   de265_error err;
+   err = hrd_parameters(errqueue, br, sps);
++  if (err) {
++  return err;
++  }
+ }
+   }
+ 
diff -Nru libde265-1.0.8/debian/patches/0001-fill-32x32-scaling-matrices.patch 
libde265-1.0.8/debian/patches/0001-fill-32x32-scaling-matrices.patch
--- libde265-1.0.8/debian/patches/0001-fill-32x32-scaling-matrices.patch
1970-01-01 01:00:00.0 +0100
+++ libde265-1.0.8/debian/patches/0001-fill-32x32-scaling-matrices.patch
2022-10-16 15:25:49.0 +0200
@@ -0,0 +1,85 @@
+From 7d5aeb5f11531de33f5b7ae0e768ffc50da4facb Mon Sep 17 00:00:00 2001
+From: Dirk Farin 
+Date: Tue, 23 Feb 2021 16:29:01 +0100
+Subject: [PATCH] fill 32x32 scaling matrices
+
+---
+ libde265/sps.cc   | 25 +++--
+ libde265/sps.h|  2 +-
+ libde265/transform.cc |  4 +---
+ 3 files changed, 25 insertions(+), 6 deletions(-)
+
+Index: libde265-1.0.8/libde265/sps.cc
+===
+--- libde265-1.0.8.orig/libde265/sps.cc
 libde265-1.0.8/libde265/sps.cc
+@@ -873,10 +873,10 @@ de265_error read_scaling_list(bitreader*
+   int dc_coeff[4][6];
+ 
+   for (int sizeId=0;sizeId<4;sizeId++) {
+-int n = ((sizeId==3) ? 2 : 6);
++//int n = ((sizeId==3) ? 2 : 6);
+ uint8_t scaling_list[6][32*32];
+ 
+-for (int matrixId=0;matrixIdScalingFactor_Size1[matrixId][y][x];
++
++  for (int dy=0;dy<4;dy++)
++for (int dx=0;dx<4;dx++) {
++  sclist->ScalingFactor_Size3[matrixId][4*y+dy][4*x+dx] = v;
++}
++  }
++
++  sclist->ScalingFactor_Size3[matrixId][0][0] = 
sclist->ScalingFactor_Size1[matrixId][0][0];
++}
++  
+   return DE265_OK;
+ }
+ 
+Index: libde265-1.0.8/libde265/sps.h
+===
+--- libde265-1.0.8.orig/libde265/sps.h
 libde265-1.0.8/libde265/sps.h
+@@ -54,7 +54,7 @@ typedef struct scaling_list_data {
+   uint8_t ScalingFactor_Size0[6][4][4];
+   uint8_t 

Bug#997174: netdiag: FTBFS: statnet.c:471:32: error: format not a string literal and no format arguments [-Werror=format-security]

[Reiner Herrmann]

Control: tags -1 + pending
Control: tags -1 + patch

Dear maintainer,

I've prepared an NMU for netdiag (versioned as 1.2-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
  Reiner
diff -u netdiag-1.2/debian/changelog netdiag-1.2/debian/changelog
--- netdiag-1.2/debian/changelog
+++ netdiag-1.2/debian/changelog
@@ -1,3 +1,10 @@
+netdiag (1.2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use fixed format strings in mvprintw calls. (Closes: #997174)
+
+ -- Reiner Herrmann   Sun, 16 Oct 2022 15:28:17 +0200
+
 netdiag (1.2-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u netdiag-1.2/debian/patches/series netdiag-1.2/debian/patches/series
--- netdiag-1.2/debian/patches/series
+++ netdiag-1.2/debian/patches/series
@@ -8,3 +8,4 @@
 clang-ftbfs.diff
 gcc-10.diff
 pcap_init.diff
+gcc12.patch
only in patch2:
unchanged:
--- netdiag-1.2.orig/debian/patches/gcc12.patch
+++ netdiag-1.2/debian/patches/gcc12.patch
@@ -0,0 +1,51 @@
+Author: Reiner Herrmann 
+Bug-Debian: https://bugs.debian.org/997174
+Description: Use fixed format string in mvprintw to prevent format string vulnerabilities
+
+--- a/statnet-3.8/statnet.c
 b/statnet-3.8/statnet.c
+@@ -467,7 +467,7 @@
+ #define min(a,b) (((a) > (b)) ? (b) : (a))
+   if( COLS < 25 + min( 25, strlen( StatMem->servername ) ) )
+   {
+-mvprintw (0, (COLS - min( 25, strlen( StatMem->servername ) )) / 2,
++mvprintw (0, (COLS - min( 25, strlen( StatMem->servername ) )) / 2, "%s",
+ 			StatMem->servername);
+   }
+   else
+@@ -475,13 +475,13 @@
+ if( ((COLS/2) + 14) > COLS - min( 25, strlen( StatMem->servername )+1 ) )
+ {
+   mvprintw (0, 0, "STATISTICS OF NETWORKS");
+-  mvprintw (0, (COLS - min( 25, strlen( StatMem->servername )+1 )),
++  mvprintw (0, (COLS - min( 25, strlen( StatMem->servername )+1 )), "%s",
+ 	  		StatMem->servername);
+ }
+ 	else
+ {
+   mvprintw (0, (COLS - 22) / 2, "STATISTICS OF NETWORKS");
+-  mvprintw (0, (COLS - min( 25, strlen( StatMem->servername )+1 )),
++  mvprintw (0, (COLS - min( 25, strlen( StatMem->servername )+1 )), "%s",
+ 	  		StatMem->servername);
+ }
+   }
+--- a/netwatch-1.3.1-2/dispdata.c
 b/netwatch-1.3.1-2/dispdata.c
+@@ -1488,7 +1488,7 @@
+ 	  fprintf (fpspeclog, "%s\n", ttt);
+ 	else
+ 	  //!!mvprintw (yact, xleft, "%s",ttt);
+-	  mvprintw (yact, xleft, ttt);
++	  mvprintw (yact, xleft, "%s", ttt);
+ 	attron (col4);
+ 	if (current->update)
+ 	{
+@@ -1736,7 +1736,7 @@
+ 	  fprintf (fpspeclog, "%s\n", ttt);
+ 	else
+ 	  //!!mvprintw (yact, xright,"%s", ttt);
+-	  mvprintw (yact, xright, ttt);
++	  mvprintw (yact, xright, "%s", ttt);
+ 	attron (col4);
+ 	if (current->update)
+ 	{

Bug#1021879: rust-kamadak-exif: please upgrade to v0.5.4

[Jonas Smedegaard]

Source: rust-kamadak-exif
Version: 0.3.1-2
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to newer major upstream release v0.5.4, needed by
packages I am preparing.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNMCqMACgkQLHwxRsGg
ASFIxg//QNYtxYjwRx73Wd6QH/BuRVScvPWAW/zdi6EA6omgCCJQHnAx2yzssi5O
YsU55m0UZGOPGsmVi5XpTT2pG6zquDdAntV1t10N7L9y4T9+z5tIY4dzSr7uzzgo
z5tsnO7Wgf/1mF9EEZH4E+Ea7wjIP8z0Nd6n7WG6+qPSQI4S16fAEt13CeXw8ABx
Ayj/8ST0d8q38TWcz+8Iz4AzVTK4Z4Lp2QWWRiTJhPn3cpBrpMF89wTRq/t2WLtK
LyAwjUlHNgsOnkkNQEGZCI9FZCw/Diwc+An10AkChnYTVYKHNozW7V4EQXuGxISW
N1e3qfsXhb7ugPyEA4GiRug/6csy/MOf+ECg7+x/qAdFOoJ6i3UWMEXRv9bq5RPj
V1T7NBT1Sb4rKrn+GPoJ1pb3w+q7tBM+GU/n6rz/IVLvPKjMfdAwhlfwEUKvGg9L
HwT3XLN3irA8Ukx8VOFH63KtF6j2huOvUi5WjXW+80oPR9D0dcWkrisY4OypRE/2
0j2HP6zzQ0tcvFd7MKggw+k2dhG63YFmOoxSWOGNN3ygkx9+gYOje5UPH9je48HH
Rn0vVv0mdSagUl5SP3s3Weq/X/cp6U+ORfEIOryCv34e9Zc4OQ8JSdB7zJGTuhHa
KzHmihrTGsPu8FPQJeKDH9exYVGxQaz/3VeEEWJo1NFP8+ej9Y8=
=fmcf
-END PGP SIGNATURE-

Bug#1021878: rust-insta: please update to 1.12 (or newer)

[Jonas Smedegaard]

Source: rust-insta
Version: 1.5.2-2
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to upstream release v1.12.0 or newer,
needed by packages I am preparing for Debian.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNMCO8ACgkQLHwxRsGg
ASED3w/+ISXVBkU6kGLP8N3ILKr/kskbNuVrFWoMOtIRVPtVY0Bx0ZPnxMXDbPkP
dx8waqMPl9BVgaAHilBc3FxQtqGc6KEGh5zcDwjVR+OTjXil8/FyTN7YM/wTNwu3
Wht88b2ahzpwNCSo5Uh/6vlzqXM2YjJPywI/Ld9wb+0r2vAj/nwVLXQZhwm6WYYD
qoZ9gSJ9XT2p3HEeC4+tPWpzn2I2/XJ3V7UEZFAlTY8eyIgn/qd8qSJg9FKdHXJY
nMdjfVSnt7IGwAcqXSbVgOASIj32uQtyrq6Bug7Y0TFQFmRaFkLQi74xf6dSWh4J
cEpTK+LdkTEM8vNzm3T/hAoeU4+GlOySvCS6gGxZj/Dce3dSTte/q0P44Memr1zU
1CYGd9SK/uoTvu+Vuod3ypz9zyS2nQ+VkzmQaolgHaXbE4JRd1C05axPx3a6FT9V
a0qoE3X7ICrJS4+X06Mm/T+3ZlWx6WHH3babrH37uKuYcXVSwkms0OF4n7OGPiUo
4oSPcKbbBPHfszVJFbMMx4g/ARYGWR5GsGfWofQSfWUBpkc3oxBWqduIjM7cfdG1
x1jxeITNrJYzRnW5zAn2WaGOVaCEQCJ0cGiU3xt0Mc0n8zh04HdtyMzSJZ0xNUpJ
dRZ2BAOoAAtP+8R+fI7QdHLujEk5V7Md30eynEf0cuwANdsioZw=
=MKPA
-END PGP SIGNATURE-

Bug#1021661: RFS: hashcash/1.22-1 [ITA] [RC] -- postage payment scheme for email based on hash calculations

[Stefan Kangas]

Bastian Germann  writes:

> Am 16.10.22 um 07:00 schrieb Stefan Kangas:
>> Also, I notice that it says "Build log checks report 1 warning" at:
>> https://tracker.debian.org/pkg/hashcash
>
> It is the line:
> fastmint_library.c:92:17: warning: implicit declaration of function 
> ‘SHA1_Transform’; did you mean ‘SHA1_Xform’?
> [-Wimplicit-function-declaration]
>
> Wasn't sha1 disabled in hashcash? Maybe there is something missing in the 
> sha1 patch.

Right, I see it now.  I believe the warning is harmless, but I have
pushed a fix to the git repository.[1]  It can probably wait until the
next release.

Thanks again for sponsoring this package.

Footnotes:
[1]  
https://salsa.debian.org/skangas/hashcash/-/commit/8cc5e83f772c254ece85999e284e7e82ae0a65e1

Bug#1012989: libsass symbols table looks updated

[Étienne Mollier]

Control: tags -1 - pending

Étienne Mollier, on 2022-10-16:
> This issue looks fixed in the experimental updload, if I trust
> the current buildd status report[1], and the bug still open
> might simply be an oversight.  I suppose the bug can be closed
> now already or when migrating the package to unstable.
> 
> [1]: 
> https://buildd.debian.org/status/package.php?p=libsass=experimental=compact

Hmn, typical me: my mail fires away and some 1.5 seconds later I
see a lintian error stating that the tracking file must get new
symbols.  That being said, strictly speaking, changes in version
-2 do not break the build with gcc-12.  I'm sorry for the noise,
I was hopeful to provide a patch updating the table, preferably
for all supported architectures, but my time at the BSP is
running out.

Any ways, have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from my alarm clock.


signature.asc
Description: PGP signature

Bug#1021877: debhelper: please disallow debian/compat in level 14+

[Adam Borowski]

Package: debhelper
Version: 13.10
Severity: wishlist

Hi!
It would be nice if you banned old-style debian/compat in upcoming compat
levels, in favour of the debhelper-compat b-dependency.

This would remove any need to check for missing debhelper dependency, and
allow speeding up buildds by preinstalling debhelper.  99.9% of packages
(61 exceptions in bookworm) use debhelper, yet it currently needs to be
installed with apt+dpkg for every single build, which does take a while.

In theory, there's a lintian check for missing debhelper b-dep, but that's
an extra moving part.  Plus, in the far future, when we drop compat 13,
it'd be less complexity for you.


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

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

Versions of packages debhelper depends on:
ii  autotools-dev20220109.1
ii  dh-autoreconf20
ii  dh-strip-nondeterminism  1.13.0-1
ii  dpkg 1.21.9
ii  dpkg-dev 1.21.9
ii  dwz  0.14+20220924-2
ii  file 1:5.41-4
ii  libdebhelper-perl13.10
ii  libdpkg-perl 1.21.9
ii  man-db   2.10.2-3
ii  perl 5.34.0-5
ii  po-debconf   1.0.21+nmu1

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn  dh-make  

-- no debconf information

Bug#979021: lirc: diff for NMU version 0.10.1-7.1

[Micha Lenk]

tags 979021 + pending
forwarded 979021 https://sourceforge.net/p/lirc/tickets/374/
user debian-rele...@lists.debian.org
usertags -1 + bsp-2022-10-de-karlsruhe
thank you


Dear maintainer,

I've prepared an NMU for lirc (versioned as 0.10.1-7.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.

Additionally I dared to forward the patch affecting the upstream
code to their bug tracker. Hopefully this will make future
maintenance of this package easier.

Regards,
Micha
diff -Nru lirc-0.10.1/debian/changelog lirc-0.10.1/debian/changelog
--- lirc-0.10.1/debian/changelog	2022-05-12 21:29:00.0 +0200
+++ lirc-0.10.1/debian/changelog	2022-10-16 13:31:28.0 +0200
@@ -1,3 +1,14 @@
+lirc (0.10.1-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Add patch to support passing MODINFO to configure.
+  * debian/rules: Pass MODINFO and SH_PATH to configure. The paths to "modinfo"
+and "sh" may vary as either located in /bin and /sbin or in /usr/bin and
+/usr/sbin if the system is configured as a usrmerge system. Use the
+non-usrmerge paths for the most compatible location (closes: #979021).
+
+ -- Micha Lenk   Sun, 16 Oct 2022 13:31:28 +0200
+
 lirc (0.10.1-7) unstable; urgency=medium
 
   * Add patch from Fedora for failing tests. Closes: #1009389
diff -Nru lirc-0.10.1/debian/patches/0010-Patch-configure.ac-to-support-passing-MODINFO.patch lirc-0.10.1/debian/patches/0010-Patch-configure.ac-to-support-passing-MODINFO.patch
--- lirc-0.10.1/debian/patches/0010-Patch-configure.ac-to-support-passing-MODINFO.patch	1970-01-01 01:00:00.0 +0100
+++ lirc-0.10.1/debian/patches/0010-Patch-configure.ac-to-support-passing-MODINFO.patch	2022-10-16 13:31:28.0 +0200
@@ -0,0 +1,28 @@
+From: Vagrant Cascadian 
+Date: Sat, 2 Jan 2021 01:03:10 +
+Subject: Patch configure.ac to support passing MODINFO.
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979021
+Bug: https://sourceforge.net/p/lirc/tickets/374/
+Reviewed-by: Simon McVittie 
+Last-Update: 2022-10-16
+
+---
+ configure.ac | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index 58347d8..1d910b0 100644
+--- a/configure.ac
 b/configure.ac
+@@ -25,8 +25,6 @@ AC_CHECK_PROGS([MODINFO], [modinfo], [no], [$PATH:/sbin:/usr/sbin])
+ if test x$MODINFO = xno; then
+   AC_MSG_WARN(["No modinfo command found - skipping kernel drivers."])
+   MODINFO="false"
+-else
+-  MODINFO=$( PATH=$PATH:/sbin:/usr/sbin which modinfo )
+ fi
+ AC_SUBST(MODINFO)
+ AC_CHECK_PROG([PKGCONFIG],[pkg-config],[yes],[no])
+-- 
+2.20.1
+
diff -Nru lirc-0.10.1/debian/patches/series lirc-0.10.1/debian/patches/series
--- lirc-0.10.1/debian/patches/series	2022-05-12 21:26:56.0 +0200
+++ lirc-0.10.1/debian/patches/series	2022-10-16 13:31:28.0 +0200
@@ -7,3 +7,4 @@
 0007-lirc-gpio-ir-0.10.patch
 0008-python3.8.diff
 0009-Replace-the-obsolete-get_event_loop-with-get_running.patch
+0010-Patch-configure.ac-to-support-passing-MODINFO.patch
diff -Nru lirc-0.10.1/debian/rules lirc-0.10.1/debian/rules
--- lirc-0.10.1/debian/rules	2021-03-18 22:21:31.0 +0100
+++ lirc-0.10.1/debian/rules	2022-10-16 13:31:28.0 +0200
@@ -22,10 +22,14 @@
 override_dh_auto_configure:
 ifeq ($(DEB_BUILD_ARCH_OS), linux)
 	dh_auto_configure -- \
+	SH_PATH=/bin/sh \
+	MODINFO=/sbin/modinfo \
 	--enable-uinput --enable-devinput \
 	--enable-silent-rules
 else
 	dh_auto_configure -- \
+	SH_PATH=/bin/sh \
+	MODINFO=/sbin/modinfo \
 	--disable-uinput --disable-devinput \
 	--enable-silent-rules
 endif

Bug#1021876: gdisk: debdiff for gdisk/1.0.9-2.1

[Hilko Bengen]

Package: gdisk
Version: 1.0.9-2
Severity: normal
X-Debbugs-Cc: none, Hilko Bengen 

Dear Maintainer,

Please find attached the debdiff corresponding to my recent
non-maintainer upload of gdisk/1.0.9-2.1 to DELAYED/5. Feel free
reschedule or cancel my upload as you see fit.

Cheers,
-Hilko

diff -Nru gdisk-1.0.9/debian/changelog gdisk-1.0.9/debian/changelog
--- gdisk-1.0.9/debian/changelog	2022-06-02 14:42:03.0 +0200
+++ gdisk-1.0.9/debian/changelog	2022-10-16 14:32:11.0 +0200
@@ -1,3 +1,11 @@
+gdisk (1.0.9-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch by Håvard F. Aasen to fix data corruption, FTBFS with
+popt 1.19 (Closes: #1020446)
+
+ -- Hilko Bengen   Sun, 16 Oct 2022 14:32:11 +0200
+
 gdisk (1.0.9-2) unstable; urgency=medium
 
   * Fix UUID generation (Closes: #1011006)
diff -Nru gdisk-1.0.9/debian/patches/handle-plugged-memory-leak-from-popt gdisk-1.0.9/debian/patches/handle-plugged-memory-leak-from-popt
--- gdisk-1.0.9/debian/patches/handle-plugged-memory-leak-from-popt	1970-01-01 01:00:00.0 +0100
+++ gdisk-1.0.9/debian/patches/handle-plugged-memory-leak-from-popt	2022-10-16 14:32:11.0 +0200
@@ -0,0 +1,42 @@
+From: =?utf-8?b?IkjDpXZhcmQgRi4gQWFzZW4i?= 
+Date: Sat, 15 Oct 2022 18:55:20 +0200
+Subject: Handle plugged memory leak from popt
+
+With popt version 1.19, a memory leak was plugged. gdisk (sdisk) assumed
+the value returned by poptGetArg() would remain usable forever because
+popt has leaked the value for quite a long time.
+
+This patch consist of one incomplete fix, that has been included in the
+official repository, and one that of this writing, is still an open PR.
+
+Origin: upstream, https://sourceforge.net/p/gptfdisk/code/ci/5d5e76d369a412bfb3d2cebb5fc0a7509cef878d/
+Origin: upstream, https://sourceforge.net/p/gptfdisk/code/merge-requests/28/
+Bug-Debian: https://bugs.debian.org/1020446
+---
+ gptcl.cc | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/gptcl.cc b/gptcl.cc
+index 34c9421..ab95239 100644
+--- a/gptcl.cc
 b/gptcl.cc
+@@ -156,9 +156,10 @@ int GPTDataCL::DoOptions(int argc, char* argv[]) {
+ 
+// Assume first non-option argument is the device filename
+device = (char*) poptGetArg(poptCon);
+-   poptResetContext(poptCon);
+ 
+if (device != NULL) {
++  device = strdup(device);
++  poptResetContext(poptCon);
+   JustLooking(); // reset as necessary
+   BeQuiet(); // Tell called functions to be less verbose & interactive
+   if (LoadPartitions((string) device)) {
+@@ -498,6 +499,7 @@ int GPTDataCL::DoOptions(int argc, char* argv[]) {
+  cerr << "Error encountered; not saving changes.\n";
+  retval = 4;
+   } // if
++  free(device);
+} // if (device != NULL)
+poptFreeContext(poptCon);
+return retval;
diff -Nru gdisk-1.0.9/debian/patches/series gdisk-1.0.9/debian/patches/series
--- gdisk-1.0.9/debian/patches/series	2022-06-02 14:39:46.0 +0200
+++ gdisk-1.0.9/debian/patches/series	2022-10-16 14:32:11.0 +0200
@@ -1 +1,2 @@
 fix-uuid-generation
+handle-plugged-memory-leak-from-popt

Bug#1021529: pcmanfm-qt: diff for NMU version 0.16.0-1.1

[Sebastian Ramacher]

Control: tags 1021529 + patch
Control: tags 1021529 + pending

Dear maintainer,

I've prepared an NMU for pcmanfm-qt (versioned as 0.16.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru pcmanfm-qt-0.16.0/debian/changelog pcmanfm-qt-0.16.0/debian/changelog
--- pcmanfm-qt-0.16.0/debian/changelog	2021-01-07 10:33:42.0 +0100
+++ pcmanfm-qt-0.16.0/debian/changelog	2022-10-16 15:02:26.0 +0200
@@ -1,3 +1,11 @@
+pcmanfm-qt (0.16.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Remove hard-coded dependency on libfm-qt8 (Closes:
+#1021529)
+
+ -- Sebastian Ramacher   Sun, 16 Oct 2022 15:02:26 +0200
+
 pcmanfm-qt (0.16.0-1) unstable; urgency=medium
 
   [ Alf Gaida ]
diff -Nru pcmanfm-qt-0.16.0/debian/control pcmanfm-qt-0.16.0/debian/control
--- pcmanfm-qt-0.16.0/debian/control	2021-01-07 10:30:30.0 +0100
+++ pcmanfm-qt-0.16.0/debian/control	2022-10-15 19:48:09.0 +0200
@@ -27,7 +27,6 @@
  ${shlibs:Depends},
  default-dbus-session-bus | dbus-session-bus | dbus-x11,
  desktop-file-utils,
- libfm-qt8 (>= 0.16.0~),
  lxqt-sudo
 Recommends: eject,
 ffmpegthumbnailer,

Bug#1021810: Should firefox-esr be dropped on 32bit architectures in bookworm?

[Arnd Bergmann]

On Sat, Oct 15, 2022, at 8:27 AM, Adrian Bunk wrote:
> Package: firefox-esr
> Version: 102.3.0esr-1
> Severity: serious
> Tags: bookworm sid
> X-Debbugs-Cc: Carsten Schoenert , 
> debian-rele...@lists.debian.org, t...@security.debian.org, 
> debian-...@lists.debian.org
>
> [ various potentially interested parties are Cc'ed ]
>
> 4 GB address space for one process is an absolute limit on 32bit
> architectures, including for native building as is done in Debian.[1]
>
> mipsel has 2 GB address space (all Debian buildds have 64bit kernels),
> the 2020 Firefox ESR (78) was the last Firefox ESR to build there.
>
> On i386 and 32bit arm:
> 4 GB address space are available with a 64bit kernel.
> 3 GB address space are typically available with a 32bit kernel.
>
> All i386 buildds are using a 64bit kernel,
> but armhf buildds are currently mixed.
>
> This uncovered that the 2022 ESR of Firefox (102) already needs
> more than 3 GB address space on armhf.[2]

I see there is already a patch in there that changes from fulllto
link mode to thinlto, which uses less memory. It might be worth
investigating if it is still possible to build firefox-esr with
LTO disabled altogether, as that should use drastically less
address space at build time, at the expense of runtime performance.

 Arnd

Bug#1021510: lxqt-qtplugin: diff for NMU version 0.16.0-1.1

[Sebastian Ramacher]

Control: tags 1021510 + patch
Control: tags 1021510 + pending

Dear maintainer,

I've prepared an NMU for lxqt-qtplugin (versioned as 0.16.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru lxqt-qtplugin-0.16.0/debian/changelog lxqt-qtplugin-0.16.0/debian/changelog
--- lxqt-qtplugin-0.16.0/debian/changelog	2021-01-07 10:53:47.0 +0100
+++ lxqt-qtplugin-0.16.0/debian/changelog	2022-10-16 15:00:28.0 +0200
@@ -1,3 +1,11 @@
+lxqt-qtplugin (0.16.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Update hard-coded dependency on libfm-qt8 to libfm-qt11
+(Closes: #1021510)
+
+ -- Sebastian Ramacher   Sun, 16 Oct 2022 15:00:28 +0200
+
 lxqt-qtplugin (0.16.0-1) unstable; urgency=medium
 
   [ Alf Gaida ]
diff -Nru lxqt-qtplugin-0.16.0/debian/control lxqt-qtplugin-0.16.0/debian/control
--- lxqt-qtplugin-0.16.0/debian/control	2021-01-07 10:53:35.0 +0100
+++ lxqt-qtplugin-0.16.0/debian/control	2022-10-16 15:00:25.0 +0200
@@ -26,7 +26,7 @@
 Multi-Arch: same
 Depends: ${misc:Depends},
  ${shlibs:Depends},
- libfm-qt8
+ libfm-qt11
 Recommends: lxqt-session,
 lxqt-config
 Suggests: lxqt | lxqt-core

Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

On 2022-10-16 14:02:12 +0200, Sebastian Ramacher wrote:
> On 2022-10-16 11:42:40 +, Philipp Kern wrote:
> > On Sun, Jan 30, 2022 at 11:23:39PM +0100, Sebastian Ramacher wrote:
> > > openjfx FTBFS with ffmpeg 5.0 (available in experimental):
> > [...]
> > 
> > It looks like even upstream openjfx (moved to [1]) is still not
> > source-compatible with ffmpeg 5.0. I could not find a bug in Oracle's
> > Java bug tracker about this either.
> > 
> > Ubuntu has disabled ffmpeg support[2], but hasn't released with that yet
> > (it's only in Kinetic due to be released soonish). This drops
> > libavplugin.so completely from libopenjfx-jni.
> > 
> > Source packages with a reverse (build-)dependency:
> > 
> > | afterburner.fx
> > | controlsfx
> > | davmail
> > | easybind
> > | fontawesomefx
> > | igv
> > | javafxsvg
> > | josm
> > | libhibernate-validator-java
> > | libjloda-java
> > | libmiglayout-java
> > | mediathekview
> > | megan-ce
> > | openchemlib
> > | pdfsam
> > | starjava-topcat
> > | triplea
> > | zeroc-ice
> > 
> > controlsfx uses javafx.scene.media.Media. pdfsam uses
> > javafx.scene.media.AudioClip. The others don't use javafx.scene.media at
> > all. mediathekview does not use controlsfx's MediaImageCell - which is
> > the one importing javafx.scene.media.Media. So I'd assume that within
> > Debian this breaks at most completion sound functionality in pdfsam-gui
> > if we were to drop the ffmpeg build-dependency.
> > 
> > I'm going to go ahead and do that.
> 
> I was looking into applying Ubuntu's patch to Debian. It still has the
> issue that the builds on arm64 and armhf fail. Reverting to 11.0.11+0
> seems to fix that.

… and I can confirm that 11.0.11+0 with the changes from Ubuntu builds
successfully on arm64.

Cheers
-- 
Sebastian Ramacher

Bug#1018584: python-stdnum: build-depends on python3-nose or uses it for autopkgtest

[Arthur de Jong]

Control: tags -1 + upstream pending

On Sun, 2022-08-28 at 21:51 +0300, Dmitry Shachn
> Your package still uses nose [1], which is an obsolete testing
> framework for Python, dead and unmaintained since 2015 [2][3].

The upstream repo switched from nose to pytest:
https://arthurdejong.org/git/python-stdnum/commit/?id=8a28e388890f0bcd0ada9df846562080bda96bf3

This will be included in the next upload.

-- 
-- arthur - adej...@debian.org - https://people.debian.org/~adejong --



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

Bug#1021875: dh-python: dh_python3 does not support --remaining-packages

[Andreas Beckmann]

Source: dh-python
Severity: normal

Hi,

I just tried giving some custom flags for some packages to dh_python3
and finish that override target with dh_python3 --remaining-packages,
but that causes a failure due to the unrecognized fag.

Andreas

Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Sebastian Ramacher]

On 2022-10-16 11:42:40 +, Philipp Kern wrote:
> On Sun, Jan 30, 2022 at 11:23:39PM +0100, Sebastian Ramacher wrote:
> > openjfx FTBFS with ffmpeg 5.0 (available in experimental):
> [...]
> 
> It looks like even upstream openjfx (moved to [1]) is still not
> source-compatible with ffmpeg 5.0. I could not find a bug in Oracle's
> Java bug tracker about this either.
> 
> Ubuntu has disabled ffmpeg support[2], but hasn't released with that yet
> (it's only in Kinetic due to be released soonish). This drops
> libavplugin.so completely from libopenjfx-jni.
> 
> Source packages with a reverse (build-)dependency:
> 
> | afterburner.fx
> | controlsfx
> | davmail
> | easybind
> | fontawesomefx
> | igv
> | javafxsvg
> | josm
> | libhibernate-validator-java
> | libjloda-java
> | libmiglayout-java
> | mediathekview
> | megan-ce
> | openchemlib
> | pdfsam
> | starjava-topcat
> | triplea
> | zeroc-ice
> 
> controlsfx uses javafx.scene.media.Media. pdfsam uses
> javafx.scene.media.AudioClip. The others don't use javafx.scene.media at
> all. mediathekview does not use controlsfx's MediaImageCell - which is
> the one importing javafx.scene.media.Media. So I'd assume that within
> Debian this breaks at most completion sound functionality in pdfsam-gui
> if we were to drop the ffmpeg build-dependency.
> 
> I'm going to go ahead and do that.

I was looking into applying Ubuntu's patch to Debian. It still has the
issue that the builds on arm64 and armhf fail. Reverting to 11.0.11+0
seems to fix that.

Cheers

> 
> Kind regards
> Philipp Kern
> 
> [1] https://github.com/openjdk/jfx
> [2] https://patches.ubuntu.com/o/openjfx/openjfx_11.0.11+1-1ubuntu1.patch

-- 
Sebastian Ramacher

Bug#1004638: openjfx: FTBFS with ffmpeg 5.0

[Philipp Kern]

On Sun, Jan 30, 2022 at 11:23:39PM +0100, Sebastian Ramacher wrote:
> openjfx FTBFS with ffmpeg 5.0 (available in experimental):
[...]

It looks like even upstream openjfx (moved to [1]) is still not
source-compatible with ffmpeg 5.0. I could not find a bug in Oracle's
Java bug tracker about this either.

Ubuntu has disabled ffmpeg support[2], but hasn't released with that yet
(it's only in Kinetic due to be released soonish). This drops
libavplugin.so completely from libopenjfx-jni.

Source packages with a reverse (build-)dependency:

| afterburner.fx
| controlsfx
| davmail
| easybind
| fontawesomefx
| igv
| javafxsvg
| josm
| libhibernate-validator-java
| libjloda-java
| libmiglayout-java
| mediathekview
| megan-ce
| openchemlib
| pdfsam
| starjava-topcat
| triplea
| zeroc-ice

controlsfx uses javafx.scene.media.Media. pdfsam uses
javafx.scene.media.AudioClip. The others don't use javafx.scene.media at
all. mediathekview does not use controlsfx's MediaImageCell - which is
the one importing javafx.scene.media.Media. So I'd assume that within
Debian this breaks at most completion sound functionality in pdfsam-gui
if we were to drop the ffmpeg build-dependency.

I'm going to go ahead and do that.

Kind regards
Philipp Kern

[1] https://github.com/openjdk/jfx
[2] https://patches.ubuntu.com/o/openjfx/openjfx_11.0.11+1-1ubuntu1.patch

Bug#1012989: libsass symbols table looks updated

[Étienne Mollier]

Control: fixed -1 3.6.5+20211226-2
Control: tags -1 pending

Greetings,

This issue looks fixed in the experimental updload, if I trust
the current buildd status report[1], and the bug still open
might simply be an oversight.  I suppose the bug can be closed
now already or when migrating the package to unstable.

[1]: 
https://buildd.debian.org/status/package.php?p=libsass=experimental=compact

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from my alarm clock.


signature.asc
Description: PGP signature

Bug#1019682: schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(error).to be_empty

[Michael Biebl]

Control: severity -1 serious

I assume the recent build failure in unstable is due to this isssue

https://buildd.debian.org/status/package.php?p=schleuder

Bumping the severity accordingly.

On Tue, 13 Sep 2022 09:10:24 -0300 Antonio Terceiro 
 wrote:

Source: schleuder
Version: 4.0.3-4
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild schleuder with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>   Failure/Error: expect(error).to be_empty
> expected 
`":85:in `require': 
cannot loa...or_ruby/rubygems/core_ext/kernel_require.rb>:85:in `require'\n\tfrom bin/schleuder:12:in 
`'\n".empty?` to be truthy, got false
>   # ./spec/schleuder/integration/filters_spec.rb:104:in `block (3 levels) in 
'
>   # ./spec/spec_helper.rb:64:in `block (3 levels) in '
>   # ./spec/spec_helper.rb:63:in `block (2 levels) in '
> 
> Finished in 3 minutes 8.5 seconds (files took 0.86967 seconds to load)

> 543 examples, 21 failures
> 
> Failed examples:
> 
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:10]' # user sends emails with different charsets works with simple_latin1

> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:1]' 
# user sends emails with different charsets works with japanese
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:5]' 
# user sends emails with different charsets works with japanese_shift_jis
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:3]' 
# user sends emails with different charsets works with 
japanese_attachment_long_name
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:11]' 
# user sends emails with different charsets works with simple_utf8
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:6]' 
# user sends emails with different charsets works with ks_c_5601-1987
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:12]' 
# user sends emails with different charsets works with thunderbird-multi-alt-html
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:9]' 
# user sends emails with different charsets works with simple_jpiso2022
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:2]' 
# user sends emails with different charsets works with japanese_attachment
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:4]' 
# user sends emails with different charsets works with japanese_iso_2022
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:8]' 
# user sends emails with different charsets works with simple_jis
> rspec './spec/schleuder/integration/receive_different_charsets_spec.rb[1:7]' 
# user sends emails with different charsets works with signed_utf8
> rspec './spec/schleuder/integration/send_encrypted_spec.rb[1:4]' # user sends 
an encrypted message from thunderbird being encrypted+signed-mime
> rspec './spec/schleuder/integration/send_encrypted_spec.rb[1:2]' # user sends 
an encrypted message from thunderbird being encrypted-mime
> rspec './spec/schleuder/integration/send_encrypted_spec.rb[1:1]' # user sends 
an encrypted message from thunderbird being encrypted-inline
> rspec './spec/schleuder/integration/send_encrypted_spec.rb[1:3]' # user sends 
an encrypted message from thunderbird being encrypted+signed-inline
> rspec ./spec/schleuder/integration/receive_bounce_spec.rb:4 # a bounce 
message is received from bounce example
> rspec ./spec/schleuder/integration/filters_spec.rb:55 # running filters 
.fix_exchange_messages! accepts a valid plain-text message
> rspec ./spec/schleuder/integration/filters_spec.rb:32 # running filters 
.fix_exchange_messages! accepts an invalid pgp/mime Exchange message
> rspec ./spec/schleuder/integration/filters_spec.rb:118 # running filters 
.strip_html_from_alternative! does NOT strip HTML-part from 
multipart/alternative-message that does NOT contain ascii-armored PGP-data
> rspec ./spec/schleuder/integration/filters_spec.rb:81 # running filters 
.strip_html_from_alternative! strips HTML-part from multipart/alternative-message 
that contains ascii-armored PGP-data
> 
> Randomized with seed 41721
> 
> /usr/bin/ruby3.1 -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 --format documentation failed
> ERROR: Test "ruby3.1" failed: 



The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/schleuder/schleuder_4.0.3-4+rebuild1663008348_amd64-2022-09-12T18:45:49Z.build

To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on
when you try this, it might mean installing ruby-all-dev from 

Bug#1021874: python-greenlet: FTBFS with Python 3.11 as a supported version

[Graham Inggs]

Source: python-greenlet
Version: 1.1.2-3
Severity: important
Tags: ftbfs fixed-upstream
User: debian-pyt...@lists.debian.org
Usertags: python3.11

Hi Maintainer

python-greenlet will FTBFS once Python 3.11 is added as a supported version.
I've copied what I hope is the relevant part of the log below.  This
appears to be fixed in the upstream 1.1.3 release.

Regards
Graham


uilding 'greenlet._greenlet' extension
creating build
creating build/temp.linux-x86_64-3.11
creating build/temp.linux-x86_64-3.11/src
creating build/temp.linux-x86_64-3.11/src/greenlet
x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
-fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv
-O2 -g -O2 -ffile-prefix-map=/<>=. -flto=auto
-ffat-lto-objects -flto=auto -ffat-lto-objects
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.11 -c
src/greenlet/greenlet.c -o
build/temp.linux-x86_64-3.11/src/greenlet/greenlet.o
In file included from src/greenlet/greenlet.c:11:
src/greenlet/greenlet.h:42:5: error: unknown type name ‘CFrame’
   42 | CFrame* cframe;
  | ^~
src/greenlet/greenlet.c: In function ‘green_clear_exc’:
src/greenlet/greenlet.c:173:17: error: ‘_PyErr_StackItem’ {aka ‘struct
_err_stackitem’} has no member named ‘exc_type’
  173 | g->exc_state.exc_type = NULL;
  | ^
src/greenlet/greenlet.c:175:17: error: ‘_PyErr_StackItem’ {aka ‘struct
_err_stackitem’} has no member named ‘exc_traceback’
  175 | g->exc_state.exc_traceback = NULL;
  | ^
src/greenlet/greenlet.c: In function ‘g_switchstack’:
src/greenlet/greenlet.c:528:44: error: ‘PyThreadState’ {aka ‘struct
_ts’} has no member named ‘recursion_depth’; did you mean
‘recursion_limit’?
  528 | current->recursion_depth = tstate->recursion_depth;
  |^~~
  |recursion_limit
src/greenlet/greenlet.c:529:38: error: ‘PyThreadState’ {aka ‘struct
_ts’} has no member named ‘frame’; did you mean ‘cframe’?
  529 | current->top_frame = tstate->frame;
  |  ^
  |  cframe
src/greenlet/greenlet.c:552:25: warning: assignment to ‘int *’ from
incompatible pointer type ‘_PyCFrame *’ [-Wincompatible-pointer-types]
  552 | current->cframe = tstate->cframe;
  | ^
src/greenlet/greenlet.c:577:17: error: ‘PyThreadState’ {aka ‘struct
_ts’} has no member named ‘recursion_depth’; did you mean
‘recursion_limit’?
  577 | tstate->recursion_depth = target->recursion_depth;
  | ^~~
  | recursion_limit
src/greenlet/greenlet.c:578:17: error: ‘PyThreadState’ {aka ‘struct
_ts’} has no member named ‘frame’; did you mean ‘cframe’?
  578 | tstate->frame = target->top_frame;
  | ^
  | cframe
src/greenlet/greenlet.c:601:24: warning: assignment to ‘_PyCFrame *’
from incompatible pointer type ‘int *’ [-Wincompatible-pointer-types]
  601 | tstate->cframe = target->cframe;
  |^
src/greenlet/greenlet.c: In function ‘g_initialstub’:
src/greenlet/greenlet.c:813:5: error: unknown type name ‘CFrame’
  813 | CFrame trace_info;
  | ^~
src/greenlet/greenlet.c:857:18: error: incompatible types when
assigning to type ‘int’ from type ‘_PyCFrame’
  857 | trace_info = *PyThreadState_GET()->cframe;
  |  ^
src/greenlet/greenlet.c:864:17: error: request for member ‘previous’
in something not a structure or union
  864 | self->cframe->previous = _GET()->root_cframe;
  | ^~
src/greenlet/greenlet.c:878:50: error: ‘PyThreadState’ {aka ‘struct
_ts’} has no member named ‘recursion_depth’; did you mean
‘recursion_limit’?
  878 | self->recursion_depth = PyThreadState_GET()->recursion_depth;
  |  ^~~
  |  recursion_limit
src/greenlet/greenlet.c: In function ‘green_new’:
src/greenlet/greenlet.c:1018:34: warning: assignment to ‘int *’ from
incompatible pointer type ‘_PyCFrame *’ [-Wincompatible-pointer-types]
 1018 | ((PyGreenlet*)o)->cframe = _GET()->root_cframe;
  |  ^
In file included from /usr/include/python3.11/Python.h:45,
 from src/greenlet/greenlet.h:8:
src/greenlet/greenlet.c: In function ‘green_traverse’:
src/greenlet/greenlet.c:1124:29: error: ‘_PyErr_StackItem’ {aka
‘struct _err_stackitem’} has no member named ‘exc_type’
 1124 | Py_VISIT(self->exc_state.exc_type);
  | ^
/usr/include/python3.11/objimpl.h:199:13: note: in definition of macro
‘Py_VISIT’
  199 | if (op) {
 \
  | ^~
In file included 

Bug#1021873: python-cffi: FTBFS with Python 3.11 as a supported version

[Graham Inggs]

Source: python-cffi
Version: 1.15.1-1
Severity: important
Tags: ftbfs fixed-upstream
User: debian-pyt...@lists.debian.org
Usertags: python3.11

Hi Maintainer

python-cffi will FTBFS once Python 3.11 is added as a supported
version.  I've copied what I hope is the relevant part of the log
below.  This appears to be fixed upstream already [1], although not
yet in a release.

Regards
Graham


[1] 
https://foss.heptapod.net/pypy/cffi/-/commit/8a3c2c816d789639b49d3ae867213393ed7abdff


=== FAILURES ===
___ test_callback_exception 

def test_callback_exception():
try:
import cStringIO
except ImportError:
import io as cStringIO# Python 3
import linecache
def matches(istr, ipattern, ipattern38, ipattern311):
if sys.version_info >= (3, 8):
ipattern = ipattern38
if sys.version_info >= (3, 11):
ipattern = ipattern311
str, pattern = istr, ipattern
while '$' in pattern:
i = pattern.index('$')
assert str[:i] == pattern[:i]
j = str.find(pattern[i+1], i)
assert i + 1 <= j <= str.find('\n', i)
str = str[j:]
pattern = pattern[i+1:]
assert str == pattern
return True
def check_value(x):
if x == 1:
raise ValueError(42)
def Zcb1(x):
check_value(x)
return x * 3
BShort = new_primitive_type("short")
BFunc = new_function_type((BShort,), BShort, False)
f = callback(BFunc, Zcb1, -42)
#
seen = []
oops_result = None
def oops(*args):
seen.append(args)
return oops_result
ff = callback(BFunc, Zcb1, -42, oops)
#
orig_stderr = sys.stderr
orig_getline = linecache.getline
try:
linecache.getline = lambda *args: 'LINE'# hack: speed
up PyPy tests
sys.stderr = cStringIO.StringIO()
if hasattr(sys, '__unraisablehook__'):  # work around pytest
sys.unraisablehook = sys.__unraisablehook__ # on recent CPythons
assert f(100) == 300
assert sys.stderr.getvalue() == ''
assert f(1) == -42
>   assert matches(sys.stderr.getvalue(), """\
From cffi callback :
Traceback (most recent call last):
  File "$", line $, in Zcb1
$
  File "$", line $, in check_value
$
ValueError: 42
""", """\
Exception ignored from cffi callback :
Traceback (most recent call last):
  File "$", line $, in Zcb1
$
  File "$", line $, in check_value
$
ValueError: 42
""", """\
Exception ignored from cffi callback :
Traceback (most recent call last):
  File "$", line $, in Zcb1
$
$
  File "$", line $, in check_value
$
$
ValueError: 42
""")

c/test_c.py:1387:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

istr = 'Exception ignored from cffi callback .Zcb1 at 0x7f1149b839c0>:\nTraceback
(...est/python-cffi/python-cffi-1.15.1/c/test_c.py", line 1362, in
check_value\nraise>
ipattern = 'Exception ignored from cffi callback :\nTraceback (most recent call last):\n  File "$", line $, in
Zcb1\n$\n$\n  File "$", line $, in check_value\n$\n
$\nValueError>
ipattern38 = 'Exception ignored from cffi callback :\nTraceback (most recent call last):\n  File "$", line $, in
Zcb1\n$\n  File "$", line $, in check_value\n$\nValueError:
42\n'
ipattern311 = 'Exception ignored from cffi callback :\nTraceback (most recent call last):\n  File "$", line $, in
Zcb1\n$\n$\n  File "$", line $, in check_value\n$\n
$\nValueEr>

def matches(istr, ipattern, ipattern38, ipattern311):
if sys.version_info >= (3, 8):
ipattern = ipattern38
if sys.version_info >= (3, 11):
ipattern = ipattern311
str, pattern = istr, ipattern
while '$' in pattern:
i = pattern.index('$')
>   assert str[:i] == pattern[:i]
E   AssertionError: assert '\n  Fi' == '\n'
E Strings contain only whitespace, escaping them using repr()
E - '\n'
E ?  ^^
E + '\n  Fi'
E ?  ^^

c/test_c.py:1353: AssertionError

Bug#1021872: debmake: Debmake does not work unless wget is installed, but stand-alone curl is able to download source package

[Marco Mattiolo]

Package: debmake
Version: 4.4.0-1
Severity: normal

Dear Maintainer,

thank you for developing and maintaining debmake!

I am encontering a strange issue: debmake is not able to download source 
package, unless wget is installed. Looking into source code, looks like 
both wget and curl should work, but I have to install wget in the docker 
image I am working in, otherwise it will not work.


Please note, downloading source package with stand-alone curl seems to work.

Please find command line relevant lines at the end of the 
reportbug-generated info.


Marco



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

Kernel: Linux 5.10.0-18-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE

Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages debmake depends on:
ii  devscripts  2.22.2
ii  dpkg-dev    1.21.9
ii  python3 3.10.6-1
ii  python3-debian  0.1.48
ii  rsync   3.2.6-4+b1

Versions of packages debmake recommends:
ii  build-essential  12.9
ii  curl 7.85.0-1
ii  strace   5.10-1
ii  wget 1.21.3-1+b1

Versions of packages debmake suggests:
ii  autotools-dev 20220109.1
pn  ccache    
pn  cmake 
pn  debmake-doc   
pn  dgit  
ii  dh-autoreconf 20
pn  dh-python 
ii  eatmydata 130-2
pn  gem2deb   
ii  git   1:2.37.2-1
pn  git-buildpackage  
pn  gitk  
pn  javahelper    
ii  lintian   2.115.3
pn  mc    
pn  quilt 
pn  rpm2cpio  
pn  sbuild    

-- no debconf information


mobian@24498a68ffb1:/home/debian/build/build_plasmamobile$ debmake -a 
https://download.kde.org/stable/plasma/5.26.0/plasma-mobile-5.26.0.tar.xz

I: set parameters
I: =
I: package_dir = /usr/lib/python3/dist-packages
I: base_path   = /usr
I: base_lib_path   = /usr/lib/debmake
I: base_share_path = /usr/share/debmake
I: =
I: sanity check of parameters
I: $ /usr/bin/curl 
https://download.kde.org/stable/plasma/5.26.0/plasma-mobile-5.26.0.tar.xz

E: Non-existing tarball name plasma-mobile-5.26.0.tar.xz
mobian@24498a68ffb1:/home/debian/build/build_plasmamobile$ sudo apt 
install wget

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  sgml-base
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
  wget
0 upgraded, 1 newly installed, 0 to remove and 142 not upgraded.
Need to get 967 kB of archives.
After this operation, 3683 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main arm64 wget arm64 
1.21.3-1+b1 [967 kB]

Fetched 967 kB in 22s (44.6 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package wget.
(Reading database ... 33514 files and directories currently installed.)
Preparing to unpack .../wget_1.21.3-1+b1_arm64.deb ...
Unpacking wget (1.21.3-1+b1) ...
Setting up wget (1.21.3-1+b1) ...
Processing triggers for man-db (2.11.0-1+b1) ...
mobian@24498a68ffb1:/home/debian/build/build_plasmamobile$ debmake -a 
https://download.kde.org/stable/plasma/5.26.0/plasma-mobile-5.26.0.tar.xz

I: set parameters
I: =
I: package_dir = /usr/lib/python3/dist-packages
I: base_path   = /usr
I: base_lib_path   = /usr/lib/debmake
I: base_share_path = /usr/share/debmake
I: =
I: sanity check of parameters
I: $ /usr/bin/wget 
https://download.kde.org/stable/plasma/5.26.0/plasma-mobile-5.26.0.tar.xz
--2022-10-16 10:39:04-- 
https://download.kde.org/stable/plasma/5.26.0/plasma-mobile-5.26.0.tar.xz
Resolving download.kde.org (download.kde.org)... 168.119.32.158, 
2a01:4f8:242:1ed5::3
Connecting to download.kde.org (download.kde.org)|168.119.32.158|:443... 
connected.

HTTP request sent, awaiting response... 302 Found
Location: 
https://kde.mirror.garr.it/kde/ftp/stable/plasma/5.26.0/plasma-mobile-5.26.0.tar.xz 
[following]
--2022-10-16 10:39:04-- 
https://kde.mirror.garr.it/kde/ftp/stable/plasma/5.26.0/plasma-mobile-5.26.0.tar.xz
Resolving kde.mirror.garr.it (kde.mirror.garr.it)... 90.147.160.72, 
90.147.160.70, 90.147.160.73, ...
Connecting to kde.mirror.garr.it 
(kde.mirror.garr.it)|90.147.160.72|:443... connected.

HTTP request sent, awaiting response... 200 OK
Length: 3356376 (3.2M) [application/octet-stream]
Saving to: ‘plasma-mobile-5.26.0.tar.xz’

plasma-mobile-5.26.0.tar 

Bug#932047: lightdm: greeter session support for elogind

[Mark Hindley]

Sam,

Thanks for this, very helpful.

I have again tested both approaches and they both work and I can find no
breakage.

On Tue, Oct 11, 2022 at 03:30:12PM -0600, Sam Hartman wrote:
> I think we want something there that allows people to get third-party
> packages into the pam config.
> If common-session isn't going to be good enough, then I guess we'd need
> to create something on the PAM side.
> But let's explore whether common-session is good enough, because it does
> look like other display managers have similar architecture and manage to
> use common-session.

Testing with @include common-session:

test@debian-sid:~$ ps -Alf|grep lightdm
4 S root   23261   1  0  80   0 - 58787 -  11:04 ?00:00:00 
/usr/sbin/lightdm
4 S root   23266   23261  2  80   0 - 80210 -  11:04 tty7 00:00:25 
/usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
4 S root   23327   23261  0  80   0 - 40649 -  11:05 ?00:00:01 
lightdm --session-child 15 26
0 S test   23435   23432  0  80   0 -  1627 -  11:18 pts/100:00:00 
grep lightdm

> Here are my thoughts on testing common-session in the greeter config:
> 
> * Take a look at how things appear in logind--does the greeter appear as
>   a session?  If so does anything break because of that?  (Withd Gnome,
>   the greeter does not appear to appear in loginctl list-sessions)

Neither for lightdm-greeter:

test@debian-sid:~$ loginctl list-sessions
SESSION  UID USER SEAT  TTY 
  1 1000 test seat0 tty1
  7 1000 test seat0 

2 sessions listed.

> * What selinux context do things appear in.  This only matters if
>   selinux is already in your testing structure

I am not sure I have quite understood this, which testing structure are you
referring to here? SElinux is not in /etc/pam.d/lightddm-greeter, only
/etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin.

> * Does the structure  of keyrings look like you expect.
> 
> * Do you end up with a systemd for the greeter user (assuming you are
> using systemd).  If so, do you want one?

No

test@debian-sid:~$ ps -Alf | grep systemd
4 S root   1   0  0  80   0 - 42151 -  09:19 ?00:01:04 
/lib/systemd/systemd --system --deserialize 37
4 S message+ 342   1  0  80   0 -  2309 -  09:19 ?00:00:09 
/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile 
--systemd-activation --syslog-only
4 S root 345   1  0  80   0 -  3598 -  09:19 ?00:00:05 
/lib/systemd/systemd-logind
4 S test 437   1  0  80   0 -  3906 -  09:30 ?00:00:08 
/lib/systemd/systemd --user
4 S root6919   1  0  80   0 - 12319 -  09:43 ?00:00:16 
/lib/systemd/systemd-journald
4 S systemd+   11560   1  0  80   0 - 22504 -  10:05 ?00:00:02 
/lib/systemd/systemd-timesyncd
4 S root   11591   1  0  80   0 -  6236 -  10:05 ?00:00:06 
/lib/systemd/systemd-udevd
0 S test   23149 437  0  80   0 -  2278 -  10:54 ?00:00:00 
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile 
--systemd-activation --syslog-only
0 S test   23439   23432  0  80   0 -  1627 -  11:18 pts/100:00:00 
grep systemd

> My suspicion is that since this appears to be working for other display
> managers, it's all fine.

It seems that way to me as well.

> But those are the areas where trouble is most likely to show up.

Thanks

Best wishes

Mark

Bug#1021862: mupen64plus: Backport SDL_SetVideoMode fix to Salsa

[Sven Eckelmann]

On Sunday, 16 October 2022 10:16:58 CEST you wrote:
> Package: mupen64plus
> Severity: important
> X-Debbugs-Cc: ed7-aspire4...@hotmail.com
> 
> mupen64plus is currently unusuable with the latest SDL (at least in bookworm).

This is impossible. This package is a meta-package without dependency to SDL

> 
> A fix has been patched into upstream:
> https://github.com/mupen64plus/mupen64plus-core/pull/970
> 
> There are discussions of a new release:
> https://github.com/mupen64plus/mupen64plus-core/issues/973
> but it's best to backport the patch to salsa for now just in case the 
> discussion goes nowhere.
> 
> I don't know whether that alone fixes the problem though, but I'm pretty sure 
> it should still build.

Can you please tell me what the difference is there to the version 2.5-9 of 
libmupen64plus2 [1]


Kind regards,
Sven

https://tracker.debian.org/news/1372713/accepted-mupen64plus-core-25-9-source-into-unstable/

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