Bug#886718:

[Yangfl]

Control: retitle -1 RFP: retdec -- retargetable machine-code decompiler
Control: noowner -1

While I have done most of packaging and some of its dependencies, it
seems retdec depends heavily on modified llvm runtime, which is
unlikely to be upstreamed in a short time.

Bug#1058563:

[Yangfl]

Hi,

1.6.0-2 comes with fix for debconf conflict with user's modification
on /etc/default/minissdpd. Please recheck if /etc/default/minissdpd
was accidentally edit by debconf and whether the issue is gone with
1.6.0-2.

Bug#1063445: tryton-server: [INTL:zh] Chinese debconf templates translation

[Yangfl]

Package: tryton-server
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Chinese translation of the tryton-server file.
# Translation of tryton-server debconf templates to Chinese
# This file is distributed under the same license as the tryton-server package.
# Yangfl , 2024.
#
msgid ""
msgstr ""
"Project-Id-Version: tryton-server\n"
"Report-Msgid-Bugs-To: tryton-ser...@packages.debian.org\n"
"POT-Creation-Date: 2022-09-27 21:21+0200\n"
"PO-Revision-Date: 2024-02-08 18:19+0800\n"
"Last-Translator: Yangfl \n"
"Language-Team: 汉语 \n"
"Language: zh_CN\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Poedit 3.4.2\n"

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:1001
msgid "Initial admin password for Tryton:"
msgstr "Tryton 的初始管理员密码："

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:1001
msgid ""
"A superuser account named \"admin\" will be created for the Tryton database. "
"Please specify the password that this account should require for the initial "
"login."
msgstr ""
"将为 Tryton 数据库创建一个名为“admin”的超级用户帐户。请指定该帐户首次登录时所"
"需的密码。"

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:1001
msgid ""
"If it is left empty a random password will be used. You can reset this "
"password from the command line with"
msgstr "如果留空，将使用随机密码。您可以从命令行重置此密码"

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:1001
msgid ""
"$ sudo -u tryton trytond-admin -c /etc/tryton/trytond.conf --password -d "
""
msgstr ""
"$ sudo -u tryton trytond-admin -c /etc/tryton/trytond.conf --password -d <数"
"据库名>"

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:1001
msgid ""
"Note: The initialization of the database may take some time; please be "
"patient."
msgstr "注意：数据库的初始化可能需要一些时间；请耐心等待。"

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:2001
msgid "Email address for the admin user:"
msgstr "管理员用户的电子邮件地址："

#. Type: string
#. Description
#: ../tryton-server-postgresql.templates:2001
msgid ""
"Please specify a valid email address that should receive administrative "
"messages from the Tryton server."
msgstr "请指定一个有效的电子邮件地址，用于接收 Tryton 服务器的管理消息。"

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:1001
msgid "Set up Tryton server workers?"
msgstr "设置 Tryton 服务器 worker？"

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:1001
msgid ""
"Some Tryton server tasks can be performed asynchronously in the background "
"by workers in a task queue."
msgstr "某些 Tryton 服务器任务可以由任务队列中的 worker 在后台异步执行。"

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:1001
msgid ""
"If enabled, the workers can automatically perform tasks such as the "
"processing of sales, invoices, or purchases removing the need to execute "
"particular workflow steps manually in the clients and wait for them to "
"finish."
msgstr ""
"如果启用，worker 可以自动执行诸如销售、发票或采购等的处理任务，而无需在客户端"
"中手动执行特定工作流程步骤后等待它们完成。"

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:2001
msgid "Set up a Tryton scheduler?"
msgstr "设置 Tryton 调度程序？"

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:2001
msgid ""
"Tryton server has its own internal \"cron\" scheduler which can run periodic "
"database-maintenance tasks (configured using the Tryton clients). Please "
"specify whether it should be enabled."
msgstr ""
"Tryton 服务器有自己的内部“cron”调度程序，可以运行定期数据库维护任务（通过 "
"Tryton 客户端配置）。请指定是否启用。"

#. Type: boolean
#. Description
#: ../tryton-server-uwsgi.templates:2001
msgid "Note: Only one cron server should be enabled per database."
msgstr "注意：每个数据库只能启用一个 cron 服务器。"

#. Type: string
#. Description
#: ../tryton-server-nginx.templates:1001
msgid "Domain for the Tryton website:"
msgstr "Tryton 网站的域名："

#. Type: string
#. Description
#: ../tryton-server-nginx.templates:1001
msgid ""
"This will be the domain under which the Tryton server will be exposed via "
"http (and/or https with Letsencrypt certificates when using the python3-"
"certbot-nginx package)."
msgstr ""
"Tryton 服务器提供 http（和/或使用 Letsencrypt 证书的 

Bug#1063439: phpsysinfo: [INTL:zh] Chinese debconf templates translation

[Yangfl]

Package: phpsysinfo
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Chinese translation of the phpsysinfo file.
# Translation of phpSysInfo debconf templates to Chinese
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the phpSysInfo package.
#
# Yangfl , 2024.
#
msgid ""
msgstr ""
"Project-Id-Version: phpsysinfo\n"
"Report-Msgid-Bugs-To: phpsysi...@packages.debian.org\n"
"POT-Creation-Date: 2023-01-14 13:26+0400\n"
"PO-Revision-Date: 2024-02-08 16:24+0800\n"
"Last-Translator: Yangfl \n"
"Language-Team: 汉语 \n"
"Language: zh_CN\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Poedit 3.4.2\n"

#. Type: multiselect
#. Description
#: ../templates:2001
msgid "Web server to reconfigure automatically:"
msgstr "自动重新配置 Web 服务器："

#. Type: multiselect
#. Description
#: ../templates:2001
msgid ""
"Please choose the web server that should be automatically configured to run "
"phpSysInfo."
msgstr "请选择要自动配置运行 phpSysInfo 的 Web 服务器。"

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Do you want to restart the webservers now if needed?"
msgstr "立即重启 Web 服务器？"

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"Remember that in order to activate the new configuration the webservers have "
"to be restarted."
msgstr "请注意，要激活新配置，必须重新启动 Web 服务器。"

#. Type: note
#. Description
#: ../templates:4001
msgid "Configuring phpSysInfo with Nginx"
msgstr "配置 Nginx 使用 phpSysInfo"

#. Type: note
#. Description
#: ../templates:4001
msgid ""
"The phpSysInfo Nginx configuration file is a location block configuration. "
"Please add the line \"include /etc/phpsysinfo/nginx.conf;\" **inside** a "
"Nginx \"server {...}\" block. For example in '/etc/nginx/sites-enabled/"
"default'. You may need to adjust the socket path in '/etc/phpsysinfo/nginx."
"conf' to another path like '/run/php/php8.2-fpm.sock'. Be sure to restart "
"the webserver afterwards."
msgstr ""
"phpSysInfo Nginx 配置文件是一个 location 块配置。请在 Nginx“server {...}”块"
"【内】添加行“include /etc/phpsysinfo/nginx.conf;”，例如在“/etc/nginx/sites-"
"enabled/default”中。您可能需要调整“/etc/phpsysinfo/nginx.conf”中的套接字路"
"径，如为“/run/php/php8.2-fpm.sock”。之后请务必重启 Web 服务器。"
# Translation of phpSysInfo debconf templates to Chinese
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the phpSysInfo package.
#
# Yangfl , 2024.
#
msgid ""
msgstr ""
"Project-Id-Version: phpsysinfo\n"
"Report-Msgid-Bugs-To: phpsysi...@packages.debian.org\n"
"POT-Creation-Date: 2023-01-14 13:26+0400\n"
"PO-Revision-Date: 2024-02-08 16:24+0800\n"
"Last-Translator: Yangfl \n"
"Language-Team: 漢語 \n"
"Language: zh_TW\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Poedit 3.4.2\n"

#. Type: multiselect
#. Description
#: ../templates:2001
msgid "Web server to reconfigure automatically:"
msgstr "自動重設 Web 伺服器："

#. Type: multiselect
#. Description
#: ../templates:2001
msgid ""
"Please choose the web server that should be automatically configured to run "
"phpSysInfo."
msgstr "請選擇要自動設定執行 phpSysInfo 的 Web 伺服器。"

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Do you want to restart the webservers now if needed?"
msgstr ""
"立即重啟 Web 伺服器？\n"
"如果需要，您想立即重新啟動網頁伺服器嗎？"

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"Remember that in order to activate the new configuration the webservers have "
"to be restarted."
msgstr "請注意，要啟用新設定，必須重新啟動 Web 伺服器。"

#. Type: note
#. Description
#: ../templates:4001
msgid "Configuring phpSysInfo with Nginx"
msgstr "設定 Nginx 使用 phpSysInfo"

#. Type: note
#. Description
#: ../templates:4001
msgid ""
"The phpSysInfo Nginx configuration file is a location block configuration. "
"Please add the line \"include /etc/phpsysinfo/nginx.conf;\" **inside** a "
"Nginx \"server {...}\" block. For example in '/etc/nginx/sites-enabled/"
"default'. You may need to adjust the socket path in '/etc/phpsysinfo/nginx."
"conf' to another path like '/run/php/php8.2-fpm.sock'. Be sure to restart "
"the webserver afterwards."
msgstr ""
"phpSysInfo Nginx 設定檔是一個 location 塊配置。請在 Nginx“server {...}”塊"
"【內】新增行“include /etc/phpsysinfo/nginx.conf;”，例如在“/etc/nginx/sites-"
"enabled/default”中。您可能需要調整“/etc/phpsysinfo/nginx.conf”中的套接字路"
"徑，如為“/run/php/php8.2-fpm.sock”。之後請務必重啟 Web 伺服器。"

Bug#1063437: puppet-agent: [INTL:zh] Chinese debconf templates translation

[Yangfl]

Package: puppet-agent
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Chinese translation of the puppet-agent file.
# Translation of puppet-agent debconf template to Chinese
# This file is distributed under the same license as the puppet-agent package.
# Yangfl , 2024.
#
msgid ""
msgstr ""
"Project-Id-Version: puppet-agent\n"
"Report-Msgid-Bugs-To: puppet-ag...@packages.debian.org\n"
"POT-Creation-Date: 2023-01-28 13:26-0500\n"
"PO-Revision-Date: 2024-02-08 16:08+0800\n"
"Last-Translator: Yangfl \n"
"Language-Team: 汉语 \n"
"Language: zh_CN\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 3.4.2\n"

#. Type: boolean
#. Description
#: ../puppet-agent.templates:1001
msgid "Remove Puppet configuration and data when package is purged?"
msgstr "清除包时删除 Puppet 配置和数据吗？"

#. Type: boolean
#. Description
#: ../puppet-agent.templates:1001
msgid ""
"The directories containing Puppet code, environments, configuration, ssl "
"certificates, logs and other data are about to be removed."
msgstr ""
"包含 Puppet 代码、环境、配置、ssl 证书、日志和其他数据的目录即将被删除。"

#. Type: boolean
#. Description
#: ../puppet-agent.templates:1001
msgid ""
"If you're purging the puppet-agent package in order to replace it with a "
"more recent or custom version or if you want to keep the data for further "
"analysis, the data should be kept."
msgstr ""
"如果要将 puppet-agent 包替换为新版或自定义版本，或者想保留数据以供进一步分"
"析，则应保留数据。"

#. Type: boolean
#. Description
#: ../puppet-agent.templates:1001
msgid ""
"If puppet.conf was modified from its default configuration, some data may "
"still remain."
msgstr "如果修改了 puppet.conf 的默认配置，可能仍将残留一些数据。"
# Translation of puppet-agent debconf template to Chinese
# This file is distributed under the same license as the puppet-agent package.
# Yangfl , 2024.
#
msgid ""
msgstr ""
"Project-Id-Version: puppet-agent\n"
"Report-Msgid-Bugs-To: puppet-ag...@packages.debian.org\n"
"POT-Creation-Date: 2023-01-28 13:26-0500\n"
"PO-Revision-Date: 2024-02-08 16:10+0800\n"
"Last-Translator: Yangfl \n"
"Language-Team: 漢語 \n"
"Language: zh_TW\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 3.4.2\n"

#. Type: boolean
#. Description
#: ../puppet-agent.templates:1001
msgid "Remove Puppet configuration and data when package is purged?"
msgstr "清除套件時刪除 Puppet 設定和資料嗎？"

#. Type: boolean
#. Description
#: ../puppet-agent.templates:1001
msgid ""
"The directories containing Puppet code, environments, configuration, ssl "
"certificates, logs and other data are about to be removed."
msgstr ""
"包含 Puppet 程式碼、環境、設定、ssl 憑證、日誌和其他資料的目錄即將被刪除。"

#. Type: boolean
#. Description
#: ../puppet-agent.templates:1001
msgid ""
"If you're purging the puppet-agent package in order to replace it with a "
"more recent or custom version or if you want to keep the data for further "
"analysis, the data should be kept."
msgstr ""
"如果要將 puppet-agent 套件替換為新版或自訂版本，或者想保留資料以進行進一步"
"分析，則應保留資料。"

#. Type: boolean
#. Description
#: ../puppet-agent.templates:1001
msgid ""
"If puppet.conf was modified from its default configuration, some data may "
"still remain."
msgstr "如果修改了 puppet.conf 的預設，可能仍將殘留一些資料。"

Bug#1063436: [INTL:zh] Chinese debconf templates translation of mrtg

[Yangfl]

Package: mrtg
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Chinese translation of the mrtg file.
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the mrtg package.
# Yangfl , 2024.
#
msgid ""
msgstr ""
"Project-Id-Version: mrtg\n"
"Report-Msgid-Bugs-To: m...@packages.debian.org\n"
"POT-Creation-Date: 2023-09-07 20:43-0300\n"
"PO-Revision-Date: 2024-02-08 15:40+0800\n"
"Last-Translator: Yangfl \n"
"Language-Team: 汉语 \n"
"Language: zh_CN\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Poedit 3.4.2\n"

#. Type: note
#. Description
#: ../mrtg.templates:1001
msgid "/etc/mrtg.cfg should be moved to /etc/mrtg/mrtg.cfg"
msgstr "/etc/mrtg.cfg 应移动至 /etc/mrtg/mrtg.cfg"

#. Type: note
#. Description
#: ../mrtg.templates:1001
msgid ""
"Older versions of MRTG on Debian had the configuration file /etc/mrtg.cfg. "
"The new version reads from /etc/mrtg/mrtg.cfg instead, so MRTG will not work "
"correctly until you move your configuration across manually."
msgstr ""
"Debian 上 MRTG 旧版本的配置文件 /etc/mrtg.cfg，在新版本改为从 /etc/mrtg/mrtg."
"cfg 读取，因此在您手动移动配置之前，MRTG 将无法正常工作。"

#. Type: boolean
#. Description
#: ../mrtg.templates:2001
msgid "Fix owner, group and permissions for /var/www/html/mrtg?"
msgstr "修复 /var/www/html/mrtg 的所有者、用户组和权限？"

#. Type: boolean
#. Description
#: ../mrtg.templates:2001
msgid ""
"By default MRTG writes all graphs in the directory /var/www/html/mrtg/. This "
"directory currently exists, but it is insecure. The directory should be "
"owned by the user 'mrtg' and group 'www-data', with recommended permissions "
"of 0750."
msgstr ""
"MRTG 默认将所有图像写入 /var/www/html/mrtg/ 目录。该目录当前存在，但不安全。"
"该目录应由用户“mrtg”和组“www-data”拥有，建议权限为 0750。"

#. Type: boolean
#. Description
#: ../mrtg.templates:3001
msgid "Create /var/www/html/mrtg?"
msgstr "创建 /var/www/html/mrtg？"

#. Type: boolean
#. Description
#: ../mrtg.templates:3001
msgid ""
"By default MRTG writes all graphs in the directory /var/www/html/mrtg/. "
"However, this directory doesn't currently exist. The directory should be "
"owned by the user 'mrtg' and group 'www-data', with recommended permissions "
"of 0750."
msgstr ""
"MRTG 默认将所有图像写入 /var/www/html/mrtg/ 目录，然该目录当前并不存在。该目"
"录应由用户“mrtg”和组“www-data”拥有，建议权限为 0750。"

#. Type: boolean
#. Description
#: ../mrtg.templates:3001
msgid ""
"Alternatively, you can use another path for generated graphs. Note that "
"keeping this directory empty when using another path is not a problem."
msgstr ""
"亦可使用其他路径来生成图像。请注意，使用其他路径时保持此目录为空不是问题。"

#. Type: boolean
#. Description
#: ../mrtg.templates:4001
msgid "Remove old and conflicting file /etc/cron.d/mrtg?"
msgstr "删除遗留冲突文件 /etc/cron.d/mrtg？"

#. Type: boolean
#. Description
#: ../mrtg.templates:4001
msgid ""
"MRTG no longer needs to use cron because it is started via systemd (or init."
"d scripts)."
msgstr "MRTG 不再需要 cron，现在它通过 systemd（或 init.d 脚本）启动。"

#. Type: boolean
#. Description
#: ../mrtg.templates:4001
msgid ""
"A file /etc/cron.d/mrtg exists, left behind by an old version of MRTG. If "
"kept, this file will cause duplicate work because MRTG now runs as a daemon. "
"It is therefore strongly recommended to remove the cron file."
msgstr ""
"存在文件 /etc/cron.d/mrtg，该文件是旧版本 MRTG 留下的。如果保留，此文件将导致"
"重复工作，因为 MRTG 现在作为守护程序运行。故强烈建议删除 cron 文件。"

#. Type: boolean
#. Description
#: ../mrtg.templates:4001
msgid ""
"If this cron job is needed, consider renaming the file (e.g. from /etc/cron."
"d/mrtg to /etc/cron.d/mrtg-custom) to avoid future warnings."
msgstr ""
"如果需要此 cron 任务，请考虑重命名该文件（例如将 /etc/cron.d/mrtg 移动到 /"
"etc/cron.d/mrtg-custom）以避免将来出现警告。"
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the mrtg package.
# Yangfl , 2024.
#
msgid ""
msgstr ""
"Project-Id-Version: mrtg\n"
"Report-Msgid-Bugs-To: m...@packages.debian.org\n"
"POT-Creation-Date: 2023-09-07 20:43-0300\n"
"PO-Revision-Date: 2024-02-08 15:55+0800\n"
"Last-Translator: Yangfl \n"
"Language-Team: 漢語 \n"
"Language: zh_TW\n"
"MIME-Version: 1.0\n"
"Content-Type:

Bug#1033012:

[Yangfl]

Please kindly check 2.3.4-1 to see if that fixed your problem.

If yes I will close this bug in the next update.

Bug#1042468:

[Yangfl]

Unfortunately scrcpy is relying more and more on new API and it's no
longer trivial to fit scrcpy-server into debian's android SDK of 23.

Even worse openjdk-17 and SDK 23 is a fatal combination to
scrcpy-server; see
https://github.com/Genymobile/scrcpy/issues/3481#issuecomment-1235538418

The only way to keep scrcpy usable might only be providing a prebuilt
scrcpy-server somewhere else.

Bug#1057784: ifplugd: RM in forky?

[Yangfl]

Chris Hofstaedtler  于2023年12月8日周五 22:08写道：
>
> Control: affects -1 src:netctl
>
> Hi,
>
> I just filed the following bug against ifplugd. It was pointed out
> to me that netctl Depends on ifplugd.
>
> * Chris Hofstaedtler  [231208 14:06]:
> > Hello,
> >
> > ifplugd is effectively NMU-maintained in Debian, and dead upstream.
> >
> > I propose keeping ifplugd for trixie, but then remove it from forky.
> >
> > If someone wants to keep it, please actively maintain this package
> > for a while and then close this bug.
>
> Are there alternatives to ifplugd in netctl?
> What is the plan for netctl to use maintained software?
>
> Best,
> Chris
>

ifplugd is not a hard dependency of netctl. It is completely safe to
run netctl without ifplugd.

Bug#1032567:

[Yangfl]

I'm aware that autopkgtests do not test the final package, but clearly
they do not provide test cases other than unit tests. If this is not a
feasible way, better to remove autopkgtests completely.

Bug#1008088:

[Yangfl]

Can you kindly post it to upstream? Since it's hard to illustrate your
idea without a screenshot.

Bug#1033012:

[Yangfl]

Looks like you just somehow deleted your /etc/default/miniupnpd .

Bug#1037559: systemd-networkd-wait-online waits undefinitely if no networkd managed interfaces

[Yangfl]

On Wed, 14 Jun 2023 09:42:06 +0100 Luca Boccassi  wrote:
> Control: tags -1 moreinfo
>
> On Wed, 14 Jun 2023 01:10:16 -0700 Mo  wrote:
> > Package: systemd
> > Version: 252.6-1
> > Severity: normal
> > Tags: newcomer
> > X-Debbugs-Cc: ali...@outlook.com
> >
> > Dear Maintainer,
> >
> > after upgrade to debian 12 from debian 11, the system boots using
> almost ~2min
> > to prompt login.
> >
> > after check for systemd-analyze, get info:
> >
> > root@vm:~# systemd-analyze time
> > Startup finished in 2.246s (kernel) + 2min 3.788s (userspace) = 2min
> 6.035s
> > graphical.target reached after 2min 3.610s in userspace.
> >
> > root@vm:~# systemd-analyze blame
> > 2min 189ms systemd-networkd-wait-online.service
> > 4.253s kdump-tools.service
> > 1.910s apparmor.service
> > 1.267s ifupdown-pre.service
> > ...
> >
> > in my machine there is not using systemd-networked, and no interfaces
> managed by
> > networkd.
>
> Then why is systemd-networkd-wait-online being pulled in? Did you
> enable it or one of the targets that pull it in? If it's not in use as
> you say, it should not run in the first place.
>
> --
> Kind regards,
> Luca Boccassi

(On behalf of ali...@outlook.com as he is facing some network problem)

Thanks for your hint, this problem original happened in my cloud
machine, so I checked again.

In my local fresh install of Debian 11, the networkd and
system-networkd-wait-online
services are disabled by default.

So I create a new cloud machine, I found the vm image the vps provider
provided has these system unit file settings default although the
system didn’t using networkd：

systemd-network-generator.service disableddisabled
systemd-networkd-wait-online.serviceenabled disabled
systemd-networkd.serviceenabled enabled

so it’s maybe will not happen in users who install Debian in local
machine, but will happen
in users who using the system image from vps provider. There maybe
enabled multiple network manager.

Of course there can be a solution that require cloud service provider
provide system image with “correct config”. But this problem could
also happened in users who try to switch network manager or switch
back then forget to disable network manager that is unused.

Since upstream(systemd) take it as a bug, I think it also can be patch
into current stable package.

Thanks.

Bug#1033745: sequeler: Unlisted dependency on libgda-5.0-mysql

[Yangfl]

Adrien Dorsaz  于2023年4月13日周四 00:57写道：
>
> Indeed, they aren't hard dependencies to launch the sequeler application
> and use it for sqlite databases.
>
> Is it possible to add them as suggested dependencies ?
>
> This will help the user to find the link between these two libdga
> drivers and the application without needing to find the information here
> or on Github.

Yes, they could be `Recommends` dependencies, so I have not closed this bug,

Bug#1033745: sequeler: Unlisted dependency on libgda-5.0-mysql

[Yangfl]

Brian Vaughan  于2023年4月1日周六 01:33写道：
>
> Package: sequeler
> Version: 0.8.0-1+b2
> Severity: normal
> X-Debbugs-Cc: bgvaug...@gmail.com
>
> Without libgda-5.0-mysql installed, Sequeler will fail to connect to a MariaDB
> database, with the error message, "No provider 'MySQL' installed".
>
> sequeler 0.8.0-1+b2 lists libgda-5.0-4 as a dependency. libgda-5.0-4 suggests
> libgda-5.0-bin, libgda-5.0-mysql, and libgda-5.0-postgres.
>
> According to this upstream bug, sequeler should list as dependencies
> libgda-5.0-mysql and libgda-5.0-postgres.
> https://github.com/Alecaddd/sequeler/issues/26
>
>
> -- System Information:
> Debian Release: 12.0
>   APT prefers unstable
>   APT policy: (990, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages sequeler depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
> ii  libc62.36-8
> ii  libcairo21.16.0-7
> ii  libgda-5.0-4 5.2.10-3
> ii  libgee-0.8-2 0.20.6-1
> ii  libglib2.0-0 2.74.6-1
> ii  libgranite6  6.2.0-3
> ii  libgtk-3-0   3.24.37-2
> ii  libgtksourceview-3.0-1   3.24.11-2+b1
> ii  libsecret-1-00.20.5-3
> ii  libssh2-11.10.0-3+b1
>
> sequeler recommends no packages.
>
> sequeler suggests no packages.
>
> -- no debconf information

This does not stop user using sqlite connection, so they are not
qualified as hard dependencies.

Bug#1029075: fatresize: IOT instruction if resize twice

[Yangfl]

Package: fatresize
Version: 1.1.0-2

# mkfs.vfat /dev/sdb1
mkfs.fat 4.2 (2021-01-31)
# fatresize -q -s 1G /dev/sdb1
part(start=2048, end=16386047, length=16384000)
# fatresize -q -s 1G /dev/sdb1
part(start=2048, end=1955078, length=1953031)
Backtrace has 6 calls on stack:
  6: /lib/x86_64-linux-gnu/libparted.so.2(ped_assert+0x4e) [0x7f7e8b000c6e]
  5: fatresize(+0x337f) [0x55d3ad14437f]
  4: fatresize(+0x2ce9) [0x55d3ad143ce9]
  3: /lib/x86_64-linux-gnu/libc.so.6(+0x2718a) [0x7f7e8ae3818a]
  2: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f7e8ae38245]
  1: fatresize(+0x3191) [0x55d3ad144191]
Bug: Assertion (ped_geometry_test_sector_inside(range, *sector)) at
fatresize.c:347 in function snap() failed.
[1]9971 IOT instruction  fatresize -q -s 1G /dev/sdb1

Bug#1029074: fatresize: misleading functionality / messed up with GPT table

[Yangfl]

Package: fatresize
Version: 1.1.0-2
Severity: important

This program, unlikely other fs resizing utils like `resize2fs` or
`btrfs filesystem resize`, does not only resize fs, but also alter the
partition table, which is not mentioned in the help text or man page
at all. As the result of messing up with partition tables, this
program may lead to one of the following consequences:

* `-s max` will fail if there is any partitions after the current
partition, showing

  Error: Can't have overlapping partitions.

instead of taking the free space after the current partition.

*  `-s max` will silently failed on GPT disk, resulting an unusable
and un-fsck-able fs. `dosfsck` will give the following error message:

  Seek to :Invalid argument

The only way to recover it is to reconstruct the disk with MBR
partition table and create a partition up to the end of disk, to pick
up sectors which is unusable in GPT scheme.

* Once `-i` is specified as one of the options, resizing operation
`-s` will be ignored without any warning, nor is it mentioned in any
help text.

Bug#1025073: network-manager: accept_ra reset to 0

[Yangfl]

Package: network-manager
Version: 1.40.4-1
Tags: ipv6

Dear Maintainer,

Whenever I reconnect to the network, accept_ra is reset to 0 by
network-manager, which makes ipv6 inaccessible. The only way to
workaround it is to set a hard-coded address.

$ nmcli con d con
$ sudo sysctl net.ipv6.conf.enp2s0.accept_ra=1
net.ipv6.conf.enp2s0.accept_ra = 1
$ nmcli con u con
$ sysctl net.ipv6.conf.enp2s0.accept_ra
net.ipv6.conf.enp2s0.accept_ra = 0
$ sysctl net.ipv6.conf.all
net.ipv6.conf.all.accept_dad = 0
net.ipv6.conf.all.accept_ra = 1
net.ipv6.conf.all.accept_ra_defrtr = 1
net.ipv6.conf.all.accept_ra_from_local = 0
net.ipv6.conf.all.accept_ra_min_hop_limit = 1
net.ipv6.conf.all.accept_ra_mtu = 1
net.ipv6.conf.all.accept_ra_pinfo = 1
net.ipv6.conf.all.accept_ra_rt_info_max_plen = 0
net.ipv6.conf.all.accept_ra_rt_info_min_plen = 0
net.ipv6.conf.all.accept_ra_rtr_pref = 1
net.ipv6.conf.all.accept_redirects = 1
net.ipv6.conf.all.accept_source_route = 0
net.ipv6.conf.all.accept_untracked_na = 0
net.ipv6.conf.all.addr_gen_mode = 0
net.ipv6.conf.all.autoconf = 1
net.ipv6.conf.all.dad_transmits = 1
net.ipv6.conf.all.disable_ipv6 = 0
net.ipv6.conf.all.disable_policy = 0
net.ipv6.conf.all.drop_unicast_in_l2_multicast = 0
net.ipv6.conf.all.drop_unsolicited_na = 0
net.ipv6.conf.all.enhanced_dad = 1
net.ipv6.conf.all.force_mld_version = 0
net.ipv6.conf.all.force_tllao = 0
net.ipv6.conf.all.forwarding = 0
net.ipv6.conf.all.hop_limit = 64
net.ipv6.conf.all.ignore_routes_with_linkdown = 0
net.ipv6.conf.all.ioam6_enabled = 0
net.ipv6.conf.all.ioam6_id = 65535
net.ipv6.conf.all.ioam6_id_wide = 4294967295
net.ipv6.conf.all.keep_addr_on_down = 0
net.ipv6.conf.all.max_addresses = 16
net.ipv6.conf.all.max_desync_factor = 600
net.ipv6.conf.all.mc_forwarding = 0
net.ipv6.conf.all.mldv1_unsolicited_report_interval = 1
net.ipv6.conf.all.mldv2_unsolicited_report_interval = 1000
net.ipv6.conf.all.mtu = 1280
net.ipv6.conf.all.ndisc_evict_nocarrier = 1
net.ipv6.conf.all.ndisc_notify = 0
net.ipv6.conf.all.ndisc_tclass = 0
net.ipv6.conf.all.optimistic_dad = 0
net.ipv6.conf.all.proxy_ndp = 0
net.ipv6.conf.all.ra_defrtr_metric = 1024
net.ipv6.conf.all.regen_max_retry = 3
net.ipv6.conf.all.router_probe_interval = 60
net.ipv6.conf.all.router_solicitation_delay = 1
net.ipv6.conf.all.router_solicitation_interval = 4
net.ipv6.conf.all.router_solicitation_max_interval = 3600
net.ipv6.conf.all.router_solicitations = -1
net.ipv6.conf.all.rpl_seg_enabled = 0
net.ipv6.conf.all.seg6_enabled = 0
net.ipv6.conf.all.seg6_require_hmac = 0
sysctl: permission denied on key 'net.ipv6.conf.all.stable_secret'
net.ipv6.conf.all.suppress_frag_ndisc = 1
net.ipv6.conf.all.temp_prefered_lft = 86400
net.ipv6.conf.all.temp_valid_lft = 604800
net.ipv6.conf.all.use_oif_addrs_only = 0
net.ipv6.conf.all.use_optimistic = 0
net.ipv6.conf.all.use_tempaddr = 0
$ sysctl net.ipv6.conf.enp2s0
net.ipv6.conf.enp2s0.accept_dad = 1
net.ipv6.conf.enp2s0.accept_ra = 0
net.ipv6.conf.enp2s0.accept_ra_defrtr = 1
net.ipv6.conf.enp2s0.accept_ra_from_local = 0
net.ipv6.conf.enp2s0.accept_ra_min_hop_limit = 1
net.ipv6.conf.enp2s0.accept_ra_mtu = 1
net.ipv6.conf.enp2s0.accept_ra_pinfo = 1
net.ipv6.conf.enp2s0.accept_ra_rt_info_max_plen = 0
net.ipv6.conf.enp2s0.accept_ra_rt_info_min_plen = 0
net.ipv6.conf.enp2s0.accept_ra_rtr_pref = 1
net.ipv6.conf.enp2s0.accept_redirects = 1
net.ipv6.conf.enp2s0.accept_source_route = 0
net.ipv6.conf.enp2s0.accept_untracked_na = 0
net.ipv6.conf.enp2s0.addr_gen_mode = 1
net.ipv6.conf.enp2s0.autoconf = 1
net.ipv6.conf.enp2s0.dad_transmits = 1
net.ipv6.conf.enp2s0.disable_ipv6 = 0
net.ipv6.conf.enp2s0.disable_policy = 0
net.ipv6.conf.enp2s0.drop_unicast_in_l2_multicast = 0
net.ipv6.conf.enp2s0.drop_unsolicited_na = 0
net.ipv6.conf.enp2s0.enhanced_dad = 1
net.ipv6.conf.enp2s0.force_mld_version = 0
net.ipv6.conf.enp2s0.force_tllao = 0
net.ipv6.conf.enp2s0.forwarding = 0
net.ipv6.conf.enp2s0.hop_limit = 64
net.ipv6.conf.enp2s0.ignore_routes_with_linkdown = 0
net.ipv6.conf.enp2s0.ioam6_enabled = 0
net.ipv6.conf.enp2s0.ioam6_id = 65535
net.ipv6.conf.enp2s0.ioam6_id_wide = 4294967295
net.ipv6.conf.enp2s0.keep_addr_on_down = 0
net.ipv6.conf.enp2s0.max_addresses = 16
net.ipv6.conf.enp2s0.max_desync_factor = 600
net.ipv6.conf.enp2s0.mc_forwarding = 0
net.ipv6.conf.enp2s0.mldv1_unsolicited_report_interval = 1
net.ipv6.conf.enp2s0.mldv2_unsolicited_report_interval = 1000
net.ipv6.conf.enp2s0.mtu = 1500
net.ipv6.conf.enp2s0.ndisc_evict_nocarrier = 1
net.ipv6.conf.enp2s0.ndisc_notify = 0
net.ipv6.conf.enp2s0.ndisc_tclass = 0
net.ipv6.conf.enp2s0.optimistic_dad = 0
net.ipv6.conf.enp2s0.proxy_ndp = 0
net.ipv6.conf.enp2s0.ra_defrtr_metric = 1024
net.ipv6.conf.enp2s0.regen_max_retry = 3
net.ipv6.conf.enp2s0.router_probe_interval = 60
net.ipv6.conf.enp2s0.router_solicitation_delay = 1
net.ipv6.conf.enp2s0.router_solicitation_interval = 4
net.ipv6.conf.enp2s0.router_solicitation_max_interval = 3600
net.ipv6.conf.enp2s0.router_solicitations = -1

Bug#1022250: qtox: AppArmor profile breaks qTox under NVIDIA propiertary drivers

[Yangfl]

Control: severity -1 normal

Remark as normal, since it's related to non-free software.

Bug#1022098: mirrors: removal of some China mirrors

[Yangfl]

Package: mirrors
User: mirr...@packages.debian.org
Usertags: mirror-list

Dear Maintainer,

Due to force majeure some mirrors in China are shut down for about one month.

Since they can't provide reliable service and such 'force majeure' is
likely to happen again for the foreseeable future, I request removal
of such mirrors.

Mirrors listed in masterlist which cannot be accessed now:

mirror.nju.edu.cn
mirror.sjtu.edu.cn
mirrors.hit.edu.cn

Bug#1020517: scrcpy: Does not display the Android window.

[Yangfl]

Control: forwarded -1 https://github.com/Genymobile/scrcpy/issues/3510

See original author comment; are you using wayland?

Bug#1020517: scrcpy: Does not display the Android window.

[Yangfl]

Xerxes  于2022年9月22日周四 23:15写道：
>
> Package: scrcpy
> Version: 1.24-1
> Severity: important
> X-Debbugs-Cc: xerxesl...@gmail.com
>
> Dear Maintainer,
>
> After using the "scrcpy" command, everything seems to be normal, but the 
> window with the Android system image does not open. Just for comparison, 
> using the flatpak version of the "guiscrcpy" program, it's working.
>
> After executing the command, the message that appears is:
>
> scrcpy 1.24 
> /usr/share/scrcpy/scrcpy-server: 1 file pushed, 0 skipped. 1.6 MB/s (40683 
> bytes in 0.024s)
> [server] INFO: Device: samsung SM-A730F (Android 9)
> INFO: Renderer: opengl
> INFO: OpenGL version: 4.6 (Compatibility Profile) Mesa 22.2.0-rc3
> INFO: Trilinear filtering enabled
> INFO: Initial texture: 1080x2216
>
> And nothing happens after that.
>
> The window with the Android system should appear. I already checked the 
> "debug mode" and permissions on the device.

Strange. Android 9 too, works fine to me. Does `scrcpy -V debug` help?

Bug#1014371: bind9-libs: SIGIOT when nslookup

[Yangfl]

Package: bind9-libs
Version: 1:9.18.1-1

When nslookup, libisc aborts due to SIGIOT. This happens from time to
time. Two examples:

$ nslookup xx
netmgr/netmgr.c:1703: REQUIREhandle) != ((void *)0) && ((const
isc__magic_t *)(handle))->magic == ((('N') << 24 | ('M') << 16 | ('H')
<< 8 | ('D' && extension ({ auto_type __atomic_load_ptr =
(&(handle)->references); __typeof ((void)0, *__atomic_load_ptr)
__atomic_load_tmp; __atomic_load (__atomic_load_ptr,
&__atomic_load_tmp, (5)); __atomic_load_tmp; }) > 0)) failed, back
trace
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(+0x369ef)[0x7f87f58369ef]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc_assertion_failed+0xa)[0x7f87f583694a]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc__nmhandle_attach+0x63)[0x7f87f581fb03]
nslookup(+0xeb8a)[0x5565de836b8a]
nslookup(+0xfa85)[0x5565de837a85]
nslookup(+0x11f2b)[0x5565de839f2b]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc__nm_async_readcb+0xad)[0x7f87f58230fd]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc__nm_readcb+0x97)[0x7f87f5823227]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(+0x31f88)[0x7f87f5831f88]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc__nm_udp_read_cb+0x46)[0x7f87f5833896]
/lib/x86_64-linux-gnu/libuv.so.1(+0x1f24b)[0x7f87f57b524b]
/lib/x86_64-linux-gnu/libuv.so.1(+0x22f75)[0x7f87f57b8f75]
/lib/x86_64-linux-gnu/libuv.so.1(uv_run+0x114)[0x7f87f57a58c4]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(+0x24a6a)[0x7f87f5824a6a]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc__trampoline_run+0x16)[0x7f87f585eb56]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7d80)[0x7f87f5da5d80]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f87f532176f]
[1]6808 IOT instruction  xx

...some successful runs

$ nslookup -timeout=2 xx
;; Got SERVFAIL reply from 50.50.1.46, trying next server
netmgr/netmgr.c:1703: REQUIREhandle) != ((void *)0) && ((const
isc__magic_t *)(handle))->magic == ((('N') << 24 | ('M') << 16 | ('H')
<< 8 | ('D' && __extension__ ({ __auto_type __atomic_load_ptr =
(&(handle)->references); __typeof__ ((void)0, *__atomic_load_ptr)
__atomic_load_tmp; __atomic_load (__atomic_load_ptr,
&__atomic_load_tmp, (5)); __atomic_load_tmp; }) > 0)) failed, back
trace
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(+0x369ef)[0x7f488a4369ef]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc_assertion_failed+0xa)[0x7f488a43694a]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc__nmhandle_attach+0x63)[0x7f488a41fb03]
nslookup(+0xeb8a)[0x562945d16b8a]
nslookup(+0xfa85)[0x562945d17a85]
nslookup(+0x11f2b)[0x562945d19f2b]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc__nm_async_readcb+0xad)[0x7f488a4230fd]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc__nm_readcb+0x97)[0x7f488a423227]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(+0x31f88)[0x7f488a431f88]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc__nm_udp_read_cb+0x46)[0x7f488a433896]
/lib/x86_64-linux-gnu/libuv.so.1(+0x1f24b)[0x7f488a37124b]
/lib/x86_64-linux-gnu/libuv.so.1(+0x22f75)[0x7f488a374f75]
/lib/x86_64-linux-gnu/libuv.so.1(uv_run+0x114)[0x7f488a3618c4]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(+0x24a6a)[0x7f488a424a6a]
/lib/x86_64-linux-gnu/libisc-9.18.1-1-Debian.so(isc__trampoline_run+0x16)[0x7f488a45eb56]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7d80)[0x7f488a38ad80]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f4889f2176f]
[1]8320 IOT instruction  nslookup -timeout=2 xx

Bug#1008796: miniupnpd: compile miniupnpd also with IGD v1 only

[Yangfl]

This does not help a lot. Please, consider filling at least the
following information:
* The hardware type and software version of the clients;
* Network captures of IGD1 and IGD2 miniupnpds;
* miniupnpd log, if any.

Bug#1008796: miniupnpd: compile miniupnpd also with IGD v1 only

[Yangfl]

Control: tags -1 moreinfo

On Fri, 01 Apr 2022 20:41:29 +0200 Matteo Croce 
wrote:
> Package: miniupnpd
> Version: 2.2.1-1
> Severity: normal
>
> Dear Maintainer,
>
> miniupnpd has the force_igd_desc_v1 config option to use the v1 IGD
descriptor.
> Unfortunately, the runtime behaviour differs between the daemon compiled
with
> and without --igd2, even when force_igd_desc_v1 set.
> This makes the daemon non interoperable with some devices.
> Please consider adding another package like miniupnpd-igd1, where the
daemon
> is compiled without --igd2.
>
How differs? This should be considered as an upstream bug.

Bug#1008087: i2pd: I2Pd crashes after running for about 2-5 minutes. It is running on a VPS server with 2 gigs RAM.

[Yangfl]

Control: tags -1 moreinfo

Jiangsu Kumquat  于2022年3月22日周二 16:45写道：
>
> Package: i2pd
> Version: 2.36.0-1
> Severity: important
>
> Dear Maintainer,
>
> The i2pd package is installed and set to run at system startup. I
> noticed that it was not running and did:
>
> systemctl restart i2pd
>
> It ran for about 2 minutes then crashed. I started it again, and it
> crashed after 5 minutes.
>
> I have not been able to make it run without crashing.
>
> I was expecting the service to run without crashing.
>
> I'm trying to run i2pd on a remote VPS server that has 200 Mbps up/down
>
> -- System Information:
> Debian Release: 11.2
>   APT prefers stable-security
>   APT policy: (500, 'stable-security'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.10.0-12-amd64 (SMP w/2 CPU threads)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages i2pd depends on:
> ii  adduser 3.118
> ii  init-system-helpers 1.60
> ii  libboost-filesystem1.74.0   1.74.0-9
> ii  libboost-program-options1.74.0  1.74.0-9
> ii  libc6   2.31-13+deb11u2
> ii  libgcc-s1   10.2.1-6
> ii  libminiupnpc17  2.2.1-1
> ii  libssl1.1   1.1.1k-1+deb11u2
> ii  libstdc++6  10.2.1-6
> ii  lsb-base11.1.0
> ii  zlib1g  1:1.2.11.dfsg-2
>
> i2pd recommends no packages.
>
> i2pd suggests no packages.
>
> -- Configuration Files:
> /etc/i2pd/i2pd.conf changed:
> ipv4 = true
> ipv6 = true
> nat = false
> bandwidth = 15000
> floodfill = true
> [http]
> address = 127.0.0.1
> port = 7070
> [httpproxy]
> address = 127.0.0.1
> port = 
> [socksproxy]
> address = 127.0.0.1
> port = 4447
> [sam]
> enabled = true
> [bob]
> [i2cp]
> [i2pcontrol]
> [precomputation]
> [upnp]
> [reseed]
> verify = true
> [addressbook]
> [limits]
> [trust]
> [exploratory]
> [persist]
> [cpuext]
>
>
> -- no debconf information

syslog does not provide much useful information. Does
/var/log/i2pd/i2pd.log help?

Bug#1007269: tbox FTBFS on hppa

[Yangfl]

Helge Deller  于2022年3月15日周二 15:39写道：
>
> Package: tbox
> Version: 1.6.7-2
> Severity: important
> Tags: hppa, patch
>
> tbox fails currently on hppa:
> https://buildd.debian.org/status/logs.php?pkg=tbox=hppa
>
> The attached patch fixes this.

Nope, there're platform-specified asm codes; see
https://salsa.debian.org/yangfl-guest/tbox/-/blob/master/src/tbox/platform/arch/context.S

Bug#1006679: libosip2: please consider updating

[Yangfl]

Source: libosip2
Severity: wishlist

It has been 5 years since last update. Please consider updating
package to the latest release.

Bug#956183: transition: libwmf

[Yangfl]

Paul Gevers  于2022年1月19日周三 03:48写道：
>
> Control: tags -1 moreinfo
>
> Hi Yangfl,
>
> On Thu, 27 Aug 2020 01:35:40 +0100 Simon McVittie  wrote:
> > On Thu, 27 Aug 2020 at 01:01:39 +0100, Simon McVittie wrote:
> > > If the new library is genuinely
> > > compatible with the old library, then I think a better way to do this
> > > would be to introduce an empty, transitional package with the old name
> > > libwmf0.2-7.
> >
> > This, for example:
> > https://salsa.debian.org/yangfl-guest/libwmf/-/merge_requests/1
>
> This got merged long time ago, is this transition still needed? I see
> that there is still an autotracker, but I'm not sure if it's for the
> things related in this bug.
>
> Paul

After checking I found libwmf0.2-7-gtk left without transitional,
maybe I should add it back then someone can close this bug without
performing transition.

Bug#1000975:

[Yangfl]

Control: tags -1 unreproducible

Cannot reproduce with 1.17.4, maybe already fixed?

Bug#997062: angelscript: please provide backport

[Yangfl]

Control: tags -1 help

I have no intend to provide backport by myself, but probably by anyone else.

Reiner Herrmann  于2021年10月23日周六 下午9:27写道：
>
> Source: angelscript
> Severity: wishlist
>
> Dear maintainer,
>
> now that angelscript is also building successfully on arm64, it would be
> nice to have it also available in backports.
> Currently supertuxkart is using an embedded copy of angelscript, but
> when it is available in backports we can switch to the version from the
> archive.
>
> Kind regards,
>   Reiner

Bug#996662: Additional information

[Yangfl]

Have no idea about apparmor, but any help is appreciated.

debian-testing  于2021年10月21日周四 下午11:22写道：
>
> Understood, but I am testing on vanilla debian installs which always includes 
> apparmor.  I haven't had this issue with any other vanilla debian packages 
> with apparmor.   A specific example is evolution email client.
>
> I am not sure if it is the way tox is reading the config or if it is specific 
> to the qtox apparmor profile.  I will have to dig further.
>
>
>
> ‐‐‐ Original Message ‐‐‐
> On Thursday, October 21, 2021 3:08 PM, Yangfl  wrote:
>
> > debian-testing debian-test...@protonmail.com 于2021年10月21日周四 下午9:48写道：
> >
> > > Yangfl: Symlink outside of home, for example, if on a symlinked network 
> > > drive or usb, etc.
> > > Directory has appropriate permissions. Seems to be apparmor (see my more 
> > > recent post), since works when apparmor is deactivate.
> > > Sent with ProtonMail Secure Email.
> >
> > Then I'd rather mark this issue as wontfix since apparmor really did
> > thr right thing to stop program from accessing files outside of /home.
>
>

Bug#996708: open-iscsi: unusable with default installation

[Yangfl]

Ritesh Raj Sarraf  于2021年10月21日周四 下午10:48写道：
>
> Hello,
>
> On Sun, 2021-10-17 at 23:34 +0800, Yangfl wrote:
> > Package: open-iscsi
> > Version: 2.1.4-2
> >
> > Hi,
> >
> > After installing open-iscsi without modifying any configuration,
> > iscsiadm can't do any discovery using `iscsiadm -m discovery -t
> > sendtargets -p `, which seemly caused by failure to start
> > iscsid. Some log:
> >
> >
>
> Was the daemon running at the time when you attempted the discovery  of
> the targets ?

See the status of iscsid.service is 'active (exited)', and no iscsid
is found using `ps`.

> > After stopping those services `systemctl stop iscsid.service;
> > systemctl stop iscsid.socket` and start iscsid manually, `iscsiadm -m
> > discovery` successes as expected.
> >
>
> What do you mean by 'manually' ? Invoking the iscsid binary by hand ?

Yes, `sudo iscsid`.

And I guess the issue is probably caused by missing
/usr/lib/systemd/system/iscsid.service in
https://packages.debian.org/sid/amd64/open-iscsi/filelist . After I
manually download the service file from git repo, everything goes
fine.

Bug#996662: Additional information

[Yangfl]

debian-testing  于2021年10月21日周四 下午9:48写道：
>
> Yangfl: Symlink outside of home, for example, if on a symlinked network drive 
> or usb, etc.
>
> Directory has appropriate permissions.  Seems to be apparmor (see my more 
> recent post), since works when apparmor is deactivate.
>
>
> Sent with ProtonMail Secure Email.
>

Then I'd rather mark this issue as wontfix since apparmor really did
thr right thing to stop program from accessing files outside of /home.

Bug#996662:

[Yangfl]

Control: tags -1 unreproducible

Cannot reproduce using

cd ~/.config
mv tox tox_
ln -s tox_ tox
cd
qtox

Bug#996708: open-iscsi: unusable with default installation

[Yangfl]

Package: open-iscsi
Version: 2.1.4-2

Hi,

After installing open-iscsi without modifying any configuration,
iscsiadm can't do any discovery using `iscsiadm -m discovery -t
sendtargets -p `, which seemly caused by failure to start
iscsid. Some log:

➜  ~  _ systemctl status iscsid.service
● iscsid.service - LSB: iSCSI initiator daemon (iscsid)
 Loaded: loaded (/etc/init.d/iscsid; generated)
 Active: active (exited) since Sun 2021-10-17 23:27:38 CST; 32s ago
TriggeredBy: ● iscsid.socket
   Docs: man:systemd-sysv-generator(8)
Process: 1586 ExecStart=/etc/init.d/iscsid start (code=exited, status=0/SUC>
CPU: 27ms

10月 17 23:27:38 desktop systemd[1]: Starting LSB: iSCSI initiator daemon (iscs>
10月 17 23:27:38 desktop iscsid[1593]: iSCSI logger with pid=1594 started!
10月 17 23:27:38 desktop iscsid[1586]: Starting iSCSI initiator daemon: iscsid
10月 17 23:27:38 desktop systemd[1]: Started LSB: iSCSI initiator daemon (iscsi>
➜  ~  _ systemctl status iscsid.socket
● iscsid.socket - Open-iSCSI iscsid Socket
 Loaded: loaded (/lib/systemd/system/iscsid.socket; enabled; vendor preset:>
 Active: active (running) since Sun 2021-10-17 23:26:35 CST; 1min 44s ago
   Triggers: ● iscsid.service
   Docs: man:iscsid(8)
 man:iscsiadm(8)
 Listen: @ISCSIADM_ABSTRACT_NAMESPACE (Stream)
 CGroup: /system.slice/iscsid.socket

10月 17 23:26:35 desktop systemd[1]: Listening on Open-iSCSI iscsid Socket.
➜  ~  _ systemctl status open-iscsi.service
● open-iscsi.service - Login to default iSCSI targets
 Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor pr>
 Active: active (exited) since Sun 2021-10-17 23:26:43 CST; 1min 43s ago
   Docs: man:iscsiadm(8)
 man:iscsid(8)
Process: 745 ExecStart=/sbin/iscsiadm -m node --loginall=automatic (code=ex>
Process: 746 ExecStart=/lib/open-iscsi/activate-storage.sh (code=exited, st>
   Main PID: 746 (code=exited, status=0/SUCCESS)
CPU: 13ms

10月 17 23:26:43 desktop systemd[1]: Starting Login to default iSCSI targets...
10月 17 23:26:43 desktop iscsiadm[745]: iscsiadm: No records found
10月 17 23:26:43 desktop systemd[1]: Finished Login to default iSCSI targets.
➜  ~  ps aux|grep iscsid
user2451  0.0  0.0   6412  2204 pts/0S+   23:33   0:00
grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS
--exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn
--exclude-dir=.idea --exclude-dir=.tox iscsid

After stopping those services `systemctl stop iscsid.service;
systemctl stop iscsid.socket` and start iscsid manually, `iscsiadm -m
discovery` successes as expected.

Bug#994726:

[Yangfl]

Hi,

Thanks for your patch. I see
https://github.com/miniupnp/miniupnp/pull/562 which almost covers this
patch, thus I will not include this patch and wait for the PR get
merged in the next upstream version. Please check that PR to see if
that fixes your issue.

Bug#991875: munge: failed to upgrade from buster to bullseye

[Yangfl]

Package: munge
Severity: important
Version: 0.5.14-4

$ sudo apt update
...
N: Repository 'http://mirrors/debian buster InRelease' changed its
'Version' value from '10.1' to '10.10'

$ sudo apt install munge
# installation ok

$ sudo nano /etc/apt/sources.list
# change 'buster' to 'bullseye'

$ sudo apt update
$ sudo apt install munge
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libmunge2
The following packages will be upgraded:
  libmunge2 munge
2 upgraded, 0 newly installed, 0 to remove and 307 not upgraded.
Need to get 128 kB of archives.
After this operation, 56.3 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://mirrors/debian bullseye/main amd64 munge amd64 0.5.14-4 [106 kB]
Get:2 http://mirrors/debian bullseye/main amd64 libmunge2 amd64
0.5.14-4 [22.3 kB]
Fetched 128 kB in 0s (2,544 kB/s)
Reading changelogs... Done
(Reading database ... 29579 files and directories currently installed.)
Preparing to unpack .../munge_0.5.14-4_amd64.deb ...
Unpacking munge (0.5.14-4) over (0.5.13-2) ...
Preparing to unpack .../libmunge2_0.5.14-4_amd64.deb ...
Unpacking libmunge2 (0.5.14-4) over (0.5.13-2) ...
Setting up libmunge2 (0.5.14-4) ...
Setting up munge (0.5.14-4) ...
Installing new version of config file /etc/init.d/munge ...
Installing new version of config file /etc/logrotate.d/munge ...
Job for munge.service failed because the control process exited with error code.
See "systemctl status munge.service" and "journalctl -xe" for details.
invoke-rc.d: initscript munge, action "restart" failed.
● munge.service - MUNGE authentication service
   Loaded: loaded (/lib/systemd/system/munge.service; enabled; vendor
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2021-08-04 04:02:46 EDT; 9ms ago
 Docs: man:munged(8)
  Process: 11931 ExecStart=/usr/sbin/munged $OPTIONS (code=exited,
status=1/FAILURE)

Aug 04 04:02:46 localhost systemd[1]: Starting MUNGE authentication service...
Aug 04 04:02:46 localhost munged[11931]: munged: Error: Failed to
initialize Libgcrypt: version mismatch: expected 1.8.8
Aug 04 04:02:46 localhost systemd[1]: munge.service: Control process
exited, code=exited, status=1/FAILURE
Aug 04 04:02:46 localhost systemd[1]: munge.service: Failed with
result 'exit-code'.
Aug 04 04:02:46 localhost systemd[1]: Failed to start MUNGE
authentication service.
dpkg: error processing package munge (--configure):
 installed munge package post-installation script subprocess returned
error exit status 1
Processing triggers for systemd (241-7~deb10u1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10) ...
Errors were encountered while processing:
 munge
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ apt show libgcrypt20
...
Version: 1.8.7-6

$ sudo apt install libgcrypt20
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  rng-tools
The following packages will be upgraded:
  libgcrypt20
1 upgraded, 0 newly installed, 0 to remove and 306 not upgraded.
1 not fully installed or removed.
Need to get 563 kB of archives.
After this operation, 12.3 kB of additional disk space will be used.
Get:1 http://mirrors.bfsu.edu.cn/debian bullseye/main amd64
libgcrypt20 amd64 1.8.7-6 [563 kB]
Fetched 563 kB in 0s (7,274 kB/s)
Reading changelogs... Done
(Reading database ... 29577 files and directories currently installed.)
Preparing to unpack .../libgcrypt20_1.8.7-6_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.8.7-6) over (1.8.4-5) ...
Setting up libgcrypt20:amd64 (1.8.7-6) ...
Setting up munge (0.5.14-4) ...
Processing triggers for libc-bin (2.28-10) ...

Bug#987879: libwaffle-dev: Missing dependency on libwayland-dev

[Yangfl]

Package: libwaffle-dev
Severity: serious
Control: affects -1 src:piglit

...
-- Checking for module 'waffle-1'
--   Package 'wayland-client', required by 'waffle-1', not found
...

Bug#987833: r-cran-openmx: FTBFS on mips due to a variable called 'mips'

[Yangfl]

Source: r-cran-openmx
Tags: patch
Severity: minor

Hi,

r-cran-openmx FTBFS on mips (after fixing #987755), since a variable
is called 'mips' and on mips 'mips' is expanded to '1'. Please
consider applying this patch, adding a suffix to the variable 'mips'.
diff --git a/src/ba81quad.cpp b/src/ba81quad.cpp
index 3df6ee0..6ebca7d 100644
--- a/src/ba81quad.cpp
+++ b/src/ba81quad.cpp
@@ -212,7 +212,7 @@ void ifaGroup::import(const List )
 
 	paramRows = -1;
 	int pmatCols=-1;
-	int mips = 1;
+	int mips_ = 1;
 	int dataRows = 0;
 	NumericVector Rmean;
 	NumericMatrix Rcov;
@@ -272,7 +272,7 @@ void ifaGroup::import(const List )
 		} else if (strEQ(key, "qpoints")) {
 			qpoints = as(slotValue);
 		} else if (strEQ(key, "minItemsPerScore")) {
-			mips = as(slotValue);
+			mips_ = as(slotValue);
 		} else {
 			// ignore
 		}
@@ -313,7 +313,7 @@ void ifaGroup::import(const List )
 
 	setLatentDistribution(mean, cov);
 
-	setMinItemsPerScore(mips);
+	setMinItemsPerScore(mips_);
 
 	if (numItems() != pmatCols) {
 		mxThrow("item matrix implies %d items but spec is length %d",
@@ -422,13 +422,13 @@ void ba81NormalQuad::layer::setupOutcomes(ifaGroup )
 void ba81NormalQuad::setupOutcomes(class ifaGroup )
 { layers[0].setupOutcomes(ig); }
 
-void ifaGroup::setMinItemsPerScore(int mips)
+void ifaGroup::setMinItemsPerScore(int mips_)
 {
 	if (numItems() && mips > numItems()) {
 		mxThrow("minItemsPerScore (=%d) cannot be larger than the number of items (=%d)",
-			 mips, numItems());
+			 mips_, numItems());
 	}
-	minItemsPerScore = mips;
+	minItemsPerScore = mips_;
 }
 
 void ifaGroup::buildRowMult()
diff --git a/src/ba81quad.h b/src/ba81quad.h
index 45cbe42..d99b58c 100644
--- a/src/ba81quad.h
+++ b/src/ba81quad.h
@@ -742,7 +742,7 @@ private:
 	int minItemsPerScore;
 	double weightSum;
 public:
-	void setMinItemsPerScore(int mips);
+	void setMinItemsPerScore(int mips_);
 	std::vector rowSkip; // whether to treat the row as NA
 
 	// workspace

Bug#987829: crazydiskinfo: FTBFS on mips due to mismatched struct member

[Yangfl]

Source: crazydiskinfo
Tags: patch
Severity: minor

Hi,

crazydiskinfo FTBFS on mips, because a struct `sigaction' is
initialized tag-less, while on mips the first member happens to be
different from that on other architectures.

Please consider applying this patch to fix this problem.
diff --git a/main.cpp b/main.cpp
index 7dcdf05..9172521 100644
--- a/main.cpp
+++ b/main.cpp
@@ -507,7 +507,8 @@ int main()
 	update();
 
 	{
-		struct sigaction s = {{actionWINCH}};
+		struct sigaction s = {0};
+		s.sa_handler = actionWINCH;
 		sigaction(SIGWINCH, , nullptr);
 	}
 

Bug#987786: postgresql-13: should Build-Conflicts: gawk

[Yangfl]

Source: postgresql-13
Severity: minor

It seems postgresql configure scripts detects awk in the order of
gawk, mawk, nawk, awk, which then writes the resulting *awk into
/usr/lib/postgresql/13/lib/pgxs/src/Makefile.global . Thus if
postgresql detects gawk during building process and a downstream
plugin package declares the build dependency of mawk as usual, it will
FTBFS. Please add Build-Conflicts to gawk to postgresql-13.

Bug#987785: pg-repack: FTCBFS: read build's cpuinfo

[Yangfl]

Source: pg-repack
Tags: patch
Usertags: ftcbfs

In configure.in, line 69:
  SSE=$(cat /proc/cpuinfo | grep sse)

Since amd64 always comes with SSE, these lines can be safely removed.
diff --git a/configure.in b/configure.in
index b27ea33..e01fd0f 100644
--- a/configure.in
+++ b/configure.in
@@ -66,16 +66,8 @@ AC_DEFINE_UNQUOTED(DATADIR,"$DATADIR",[DATADIR])
 AC_DEFINE([WEBSITE],["horgand.berlios.de"],[WEBSITE])
 
 
-SSE=$(cat /proc/cpuinfo | grep sse) 
-
-if test -z "$SSE"; then 
-SSE=""
-else
-SSE="-msse"
-fi
-
 LIBS="`$FLTKCONFIG --ldflags` -lasound `pkg-config --libs jack` `pkg-config --libs sndfile` -lXpm"
-CXXFLAGS="-O3 -fno-rtti -pipe -ffast-math -ffunction-sections -fomit-frame-pointer $SSE -Wall `$FLTKCONFIG --cxxflags` `pkg-config --cflags jack` `pkg-config --cflags sndfile`"
+CXXFLAGS="-O3 -fno-rtti -pipe -ffast-math -ffunction-sections -fomit-frame-pointer -Wall `$FLTKCONFIG --cxxflags` `pkg-config --cflags jack` `pkg-config --cflags sndfile`"
 AC_CONFIG_FILES([Makefile src/Makefile data/Makefile man/Makefile])
 AC_OUTPUT
 

Bug#987761: libcm256cc: should Architecture: any-amd64 arm64 armhf any-i386 x32

[Yangfl]

Source: libcm256cc
Severity: minor

Hi,

libcm256cc depends on architecture-specified SIMD instructions, thus
should be restricted to only supported architectures.

Bug#987760: libcds: FTBFS on some 64-bit archs due to hard-coded CDS_BUILD_BITS

[Yangfl]

Source: libcds
Tags: patch ftbfs

Hi,

libcds FTBFS on some 64-bit archs, because they hard-code
CDS_BUILD_BITS to be 32 for unknown archs. Please consider applying
this patch to fix this problem.
diff --git a/cds/compiler/gcc/compiler_macro.h b/cds/compiler/gcc/compiler_macro.h
index f954d6c..841eca6 100644
--- a/cds/compiler/gcc/compiler_macro.h
+++ b/cds/compiler/gcc/compiler_macro.h
@@ -127,7 +127,11 @@
 #   error "Libcds does not support atomic implementation for the processor architecture. Try to use C++11-compatible compiler and remove CDS_USE_LIBCDS_ATOMIC flag from compiler command line"
 #   else
 #   define CDS_PROCESSOR_ARCHCDS_PROCESSOR_UNKNOWN
-#   define CDS_BUILD_BITS32
+#   if __SIZEOF_POINTER__ == 8
+#   define CDS_BUILD_BITS64
+#   else
+#   define CDS_BUILD_BITS32
+#   endif
 #   define CDS_PROCESSOR__NAME   "unknown"
 #   define CDS_PROCESSOR__NICK   "unknown"
 #   endif

Bug#987755: r-cran-rpf: FTBFS on mips due to a variable called 'mips'

[Yangfl]

Source: r-cran-rpf
Tags: patch
Severity: minor

Hi,

r-cran-rpf FTBFS on mips, since a variable is called 'mips' and on
mips 'mips' is expanded to '1'. Lines in question:

ba81quad.h:743:31: error: expected ‘,’ or ‘...’ before numeric constant
  743 |  void setMinItemsPerScore(int mips);
  |   ^~~~
ba81quad.cpp: In member function ‘void ifaGroup::import(const List&)’:
ba81quad.cpp:214:6: error: expected unqualified-id before numeric constant
  214 |  int mips = 1;
  |  ^~~~
ba81quad.cpp:274:4: error: lvalue required as left operand of assignment
  274 |mips = as(slotValue);
  |^~~~
ba81quad.cpp: At global scope:
ba81quad.cpp:426:40: error: expected ‘,’ or ‘...’ before numeric constant
  426 | void ifaGroup::setMinItemsPerScore(int mips)
  |^~~~

Please consider applying this patch, adding a suffix to the variable 'mips'.
diff --git a/src/ba81quad.cpp b/src/ba81quad.cpp
index 60d276c..d6419ce 100644
--- a/src/ba81quad.cpp
+++ b/src/ba81quad.cpp
@@ -211,7 +211,7 @@ void ifaGroup::import(const List )
 
 	paramRows = -1;
 	int pmatCols=-1;
-	int mips = 1;
+	int mips_ = 1;
 	int dataRows = 0;
 	NumericVector Rmean;
 	NumericMatrix Rcov;
@@ -271,7 +271,7 @@ void ifaGroup::import(const List )
 		} else if (strEQ(key, "qpoints")) {
 			qpoints = as(slotValue);
 		} else if (strEQ(key, "minItemsPerScore")) {
-			mips = as(slotValue);
+			mips_ = as(slotValue);
 		} else {
 			// ignore
 		}
@@ -312,7 +312,7 @@ void ifaGroup::import(const List )
 
 	setLatentDistribution(mean, cov);
 
-	setMinItemsPerScore(mips);
+	setMinItemsPerScore(mips_);
 
 	if (numItems() != pmatCols) {
 		stop("item matrix implies %d items but spec is length %d",
@@ -423,13 +423,13 @@ void ba81NormalQuad::layer::setupOutcomes(ifaGroup )
 void ba81NormalQuad::setupOutcomes(class ifaGroup )
 { layers[0].setupOutcomes(ig); }
 
-void ifaGroup::setMinItemsPerScore(int mips)
+void ifaGroup::setMinItemsPerScore(int mips_)
 {
-	if (numItems() && mips > numItems()) {
+	if (numItems() && mips_ > numItems()) {
 		stop("minItemsPerScore (=%d) cannot be larger than the number of items (=%d)",
-			 mips, numItems());
+			 mips_, numItems());
 	}
-	minItemsPerScore = mips;
+	minItemsPerScore = mips_;
 }
 
 void ifaGroup::buildRowMult()
diff --git a/src/ba81quad.h b/src/ba81quad.h
index 3e60a86..39c5eb1 100644
--- a/src/ba81quad.h
+++ b/src/ba81quad.h
@@ -740,7 +740,7 @@ private:
 	int minItemsPerScore;
 	double weightSum;
 public:
-	void setMinItemsPerScore(int mips);
+	void setMinItemsPerScore(int mips_);
 	std::vector rowSkip; // whether to treat the row as NA
 
 	// workspace

Bug#942412:

[Yangfl]

Control: tags -1 + patch

Hi, please consider applying this patch, fixing FTBFS by replacing
problematic library detector by pkg-config.
diff --git a/cmake/FindDM.cmake b/cmake/FindDM.cmake
index a7a3f9b..68c5ae7 100755
--- a/cmake/FindDM.cmake
+++ b/cmake/FindDM.cmake
@@ -59,68 +59,21 @@ ELSE()
 ENDIF()
   ELSE()
 MESSAGE(STATUS "${ODBC_CONFIG_EXEC} is not found ")
-# Try to find the include directory, giving precedence to special variables
-SET(LIB_PATHS /usr/local /usr /usr/local/Cellar/libiodbc/3.52.12)
+FIND_PACKAGE(PkgConfig REQUIRED)
+PKG_SEARCH_MODULE(ODBC REQUIRED ${ODBC_LIBS})
+PKG_SEARCH_MODULE(ODBCINST REQUIRED ${ODBC_INSTLIBS})
 
-IF("${CMAKE_SIZEOF_VOID_P}" EQUAL "8")
-  SET(LIB_PATHS "${LIB_PATHS}" "/usr/lib/x86_64-linux-gnu")
-
-  IF(EXISTS "/usr/lib64/")
-SET(LIB_SUFFIX "lib64" "x86_64-linux-gnu")
-  ELSE()
-SET(LIB_SUFFIX "lib" "x86_64-linux-gnu")
-  ENDIF()
-   
-ELSE()
-  SET(LIB_PATHS "${LIB_PATHS}" "/usr/local/lib/i386-linux-gnu" "/usr/lib/i386-linux-gnu" "/usr/local/lib/i686-linux-gnu" "/usr/lib/i686-linux-gnu")
-  SET(LIB_SUFFIX "lib" "i386-linux-gnu" "i686-linux-gnu")
-ENDIF()
-
-FIND_PATH(ODBC_INCLUDE_DIR sql.h
-HINTS ${DM_INCLUDE_DIR}
-  ${DM_DIR}
-  ENV DM_INCLUDE_DIR
-  ENV DM_DIR
-PATHS /usr/local
-  /usr
-  /usr/local/Cellar/libiodbc/3.52.12
-PATH_SUFFIXES include include/iodbc
-NO_DEFAULT_PATH
-DOC "Driver Manager Includes")
-# Giving chance to cmake_(environment)path
-FIND_PATH(ODBC_INCLUDE_DIR sql.h
-DOC "Driver Manager Includes")
-
-IF(ODBC_INCLUDE_DIR)
+IF(ODBC_FOUND)
+  SET(ODBC_INCLUDE_DIR "${ODBC_INCLUDE_DIRS}")
   MESSAGE(STATUS "Found ODBC Driver Manager includes: ${ODBC_INCLUDE_DIR}")
 ENDIF()
 # Try to find DM libraries, giving precedence to special variables
-FIND_PATH(ODBC_LIB_DIR "lib${ODBC_LIBS}.so"
-HINTS ${DM_LIB_DIR}
-  ${DM_DIR}
-  ENV DM_LIB_DIR
-  ENV DM_DIR
-PATHS ${LIB_PATHS}
-PATH_SUFFIXES ${LIB_SUFFIX} 
-NO_DEFAULT_PATH
-DOC "Driver Manager Libraries")
-FIND_PATH(ODBC_LIB_DIR "lib${ODBC_LIBS}.so"
-DOC "Driver Manager Libraries")
-FIND_PATH(ODBCINST_LIB_DIR "lib${ODBC_INSTLIBS}.so"
-HINTS ${DM_LIB_DIR}
-  ${DM_DIR}
-  ENV DM_LIB_DIR
-  ENV DM_DIR
-PATHS ${LIB_PATHS}
-PATH_SUFFIXES ${LIB_SUFFIX} 
-NO_DEFAULT_PATH
-DOC "Driver Manager Libraries")
-FIND_PATH(ODBCINST_LIB_DIR "lib${ODBC_INSTLIBS}.so"
-DOC "Driver Manager Libraries")
+SET(ODBC_LIB_DIR "${ODBC_LIBRARY_DIRS}")
+SET(ODBCINST_LIB_DIR "${ODBCINST_LIBRARY_DIRS}")
   ENDIF()
 ENDIF()
 
-IF(ODBC_LIB_DIR AND ODBC_INCLUDE_DIR)
+IF(ODBC_FOUND AND ODBCINST_FOUND)
   MESSAGE(STATUS "Found ODBC Driver Manager libraries: ${ODBC_LIB_DIR} ${ODBCINST_LIB_DIR}")
   SET(DM_FOUND TRUE)
 ENDIF()

Bug#987700: bornagain: buggy cmake file

[Yangfl]

Source: bornagain
Tags: patch

Hi,

cmake/BornAgain/Linux.cmake currently has the following lines:
  execute_process(COMMAND uname -m OUTPUT_VARIABLE SYSCTL_OUTPUT)
  if(${SYSCTL_OUTPUT} MATCHES x86_64)
  message(STATUS "Found a 64bit system")
  set(BIT_ENVIRONMENT "-m64")
  set(BORNAGAIN_ARCHITECTURE linuxx8664)
  else()
  message(STATUS "Found a 32bit system")
  set(BIT_ENVIRONMENT "-m32")
  add_definitions(-DEIGEN_DONT_ALIGN_STATICALLY=1)
  endif()

This has the following affects:
  * It stops cross building since it reads build's `uname`.
  * It stops building for most non-amd64 64-bit archs since it doesn't
recognize them as 64-bit archs.
  * It stops building for most non-i386 archs since they don't accept `-m32`.

Please consider applying this patch.
diff --git a/cmake/BornAgain/Linux.cmake b/cmake/BornAgain/Linux.cmake
index 2f482ee..98f67a5 100644
--- a/cmake/BornAgain/Linux.cmake
+++ b/cmake/BornAgain/Linux.cmake
@@ -1,14 +1,13 @@
 set(BORNAGAIN_ARCHITECTURE linux)
 set(BORNAGAIN_PLATFORM linux)
 
-execute_process(COMMAND uname -m OUTPUT_VARIABLE SYSCTL_OUTPUT)
-if(${SYSCTL_OUTPUT} MATCHES x86_64)
+if(CMAKE_SIZEOF_VOID_P GREATER 4)
 message(STATUS "Found a 64bit system")
-set(BIT_ENVIRONMENT "-m64")
-set(BORNAGAIN_ARCHITECTURE linuxx8664)
+if(${CMAKE_SYSTEM_PROCESSOR} STREQUAL x86_64)
+set(BORNAGAIN_ARCHITECTURE linuxx8664)
+endif()
 else()
 message(STATUS "Found a 32bit system")
-set(BIT_ENVIRONMENT "-m32")
 add_definitions(-DEIGEN_DONT_ALIGN_STATICALLY=1)
 endif()
 

Bug#987677: bornagain: contains ccache prebuilt objects

[Yangfl]

Source: bornagain
Severity: important

Hi, the source tarball contains lots of ccache prebuilt objects under
.ccache. Please consider removing them.

Bug#987555: sbuild: should support -J as well

[Yangfl]

Package: sbuild
Severity: wishlist

According to the man page of dpkg-buildpackage:
  -j, --jobs[=jobs|auto]
... Will add itself to the MAKEFLAGS environment variable, which
should cause all subsequent make invocations to inherit the option,
thus forcing the parallel setting on the packaging (and possibly the
upstream build system if that uses make) regardless of their support
for parallel builds, which might cause build failures...

and `-J` seems to be the right option. However, sbuild does not
support `-J`, neither does it mention it will lead to an unsafe option
of `dpkg-buildpackage`. Please add support to the `-J` option, or at
least refer to the `dpkg-buildpackage` man page in sbuild man page.

Bug#987080: ITP: portage -- package management system based on ports collections

[Yangfl]

Ludovic Bellier  于2021年4月17日周六 下午7:18写道：
>
> Le 17/04/2021 à 11:57, Yangfl a écrit :
> > Package: wnpp
> > Severity: wishlist
> > Owner: Yangfl 
> >
> > * Package name: portage
> >Version : 3.0.17
> >Upstream Author : Gentoo Foundation
> > * URL : https://gitweb.gentoo.org/proj/portage.git/
> > * License : GPL-2
> >Programming Lang: Python
> >Description : package management system based on ports collections
> >
> > Portage is a package management system based on ports collections. The
> > Package Manager Specification Project (PMS) standardises and documents
> > the behaviour of Portage so that ebuild repositories can be used by
> > other package managers.
>
> Hi Yangfl,
>
> *I'm just curious*, what is the use case for portage in Debian?
>
> As it's the Gentoo package manager, do you use it to install ebuild
> packages in Debian? To test ebuild packages? A Gentoo ebuild farm from
> Debian? ...
>
> Regards
>
> Ludovic
>

Mainly for testing and cross building, of course.

Bug#987080: ITP: portage -- package management system based on ports collections

[Yangfl]

Package: wnpp
Severity: wishlist
Owner: Yangfl 

* Package name: portage
  Version : 3.0.17
  Upstream Author : Gentoo Foundation
* URL : https://gitweb.gentoo.org/proj/portage.git/
* License : GPL-2
  Programming Lang: Python
  Description : package management system based on ports collections

Portage is a package management system based on ports collections. The
Package Manager Specification Project (PMS) standardises and documents
the behaviour of Portage so that ebuild repositories can be used by
other package managers.

Bug#986273: highwayhash: FTBFS on most archs due to bad Makefile

[Yangfl]

Source: highwayhash
Tags: patch ftbfs

Hi,

highwayhash currently FTBFS on most archs, because at Line 1 of Makefile:

  # We assume X64 unless HH_POWER, HH_ARM, or HH_AARCH64 are defined.

This, however, is unnecessary since highwayhash already comes with a
portable version of backend. Please consider apply this patch to fix
this problem (symbols not updated).
diff --git a/Makefile b/Makefile
index 67a2a5b..8a63f4b 100644
--- a/Makefile
+++ b/Makefile
@@ -32,22 +32,21 @@ HH_AARCH64 = 1
 endif
 
 ifdef HH_AARCH64
-HH_X64 =
 HIGHWAYHASH_OBJS += obj/hh_neon.o
 HIGHWAYHASH_TEST_OBJS += obj/highwayhash_test_neon.o
 VECTOR_TEST_OBJS += obj/vector_test_neon.o
 else
 ifdef HH_POWER
-HH_X64 =
 HIGHWAYHASH_OBJS += obj/hh_vsx.o
 HIGHWAYHASH_TEST_OBJS += obj/highwayhash_test_vsx.o
 else
-HH_X64 = 1
+ifdef HH_X64
 HIGHWAYHASH_OBJS += obj/hh_avx2.o obj/hh_sse41.o
 HIGHWAYHASH_TEST_OBJS += obj/highwayhash_test_avx2.o obj/highwayhash_test_sse41.o
 VECTOR_TEST_OBJS += obj/vector_test_avx2.o obj/vector_test_sse41.o
 endif
 endif
+endif
 
 # In case highwayhash_test defines PRINT_RESULTS.
 HIGHWAYHASH_TEST_OBJS += $(HIGHWAYHASH_OBJS)
diff --git a/debian/rules b/debian/rules
index d42949a..00fbbc9 100755
--- a/debian/rules
+++ b/debian/rules
@@ -5,6 +5,12 @@ export LIBDIR=$(DESTDIR)/lib/$(DEB_HOST_MULTIARCH)/
 export INCDIR=$(DESTDIR)/include/
 TESTBINS = highwayhash_test nanobenchmark_example profiler_example sip_hash_test vector_test
 
+ifneq (,$(filter $(DEB_BUILD_ARCH),amd64))
+export HH_X64=1
+endif
+ifneq (,$(filter $(DEB_BUILD_ARCH),x32))
+export HH_X64=1
+endif
 ifneq (,$(filter $(DEB_BUILD_ARCH),arm64))
 export HH_AARCH64=1
 endif

Bug#986250: libtraildb-dev: should Architecture: amd64 x32

[Yangfl]

Source: libtraildb-dev

In file included from src/tdb_encode_model.c:22:
src/dsfmt/dSFMT.h:148:12: fatal error: emmintrin.h: No such file or directory
  148 | #  include 
  |^
compilation terminated.

Bug#986249: python-procrunner: should Build-Conflicts: wget

[Yangfl]

Package: python-procrunner
Severity: important

==
test session starts
==
platform linux -- Python 3.9.2, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
rootdir: /home/ding/mips/python-procrunner-1.1.0, configfile: setup.cfg
collected 33 items

tests/test_procrunner.py 

[ 36%]
tests/test_procrunner_resolution.py ..sss

[ 87%]
tests/test_procrunner_system.py ..F.

[100%]

===
FAILURES 

___
test_running_wget
___

tmpdir = local('/tmp/pytest-of-ding/pytest-0/test_running_wget0')

def test_running_wget(tmpdir):
tmpdir.chdir()
command = ["wget", "https://www.google.com;, "-O", "-"]
try:
result = procrunner.run(command)
except OSError as e:
if e.errno == 2:
pytest.skip("wget not available")
raise
>   assert result.returncode == 0
E   AssertionError: assert 4 == 0
E+  where 4 = {'exitcode': 4, 'command': ('wget',
'https://www.google.com', '-O', '-'), 'stdout': b'', 'stderr':
b'--2021-04-01 21:4... False, 'runtime': 0.16795628699765075,
'time_start': '2021-04-01 13:48:11 GMT', 'time_end': '2021-04-01
13:48:11 GMT'}.returncode

/home/ding/mips/python-procrunner-1.1.0/.pybuild/cpython3_3.9_python-procrunner/build/tests/test_procrunner_system.py:52:
AssertionError

Bug#986248: pdfsandwich: detect native-archs for ocaml

[Yangfl]

Source: pdfsandwich

Hi,

pdfsandwich ftbfs on many archs (
https://buildd.debian.org/status/package.php?p=pdfsandwich ) because
of missing ocamlopt. Please consider adjusting makefile according to
https://bugs.debian.org/883018 , thanks.

Bug#986234: calcurse: ftbfs at the second run of dpkg-buildpackage

[Yangfl]

Source: calcurse
Version: 4.6.0-2
Severity: wishlist

$ dpkg-buildpackage -j6 -B -us -uc
[... build succeed]
$ dpkg-buildpackage -j6 -B -us -uc
[...]
checking pthread.h presence... yes
checking for pthread.h... yes
checking for pthread_create in -lpthread... yes
checking for math.h... (cached) yes
checking for exp in -lm... yes
checking whether to include documentation... yes
checking for asciidoc... no
configure: WARNING: AsciiDoc not found - cannot rebuild documentation!
configure: error: Asciidoc is required to build documentation.
tail -v -n \+0 config.log
==> config.log <==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by calcurse configure 4.6.0, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure --build=mipsisa64r6el-linux-gnuabi64 --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=${prefix}/lib/mipsisa64r6el-linux-gnuabi64
--libexecdir=${prefix}/lib/mipsisa64r6el-linux-gnuabi64
--disable-maintainer-mode --disable-dependency-tracking
[...]

Bug#906330:

[Yangfl]

Andrej Shadura  于2021年4月1日周四 下午5:55写道：
>
> Control: tag -1 moreinfo
>
> Hi,
>
> On Thu, 1 Apr 2021, at 11:51, Yangfl wrote:
> > `sbuild --no-arch-all --no-run-lintian -j1 -d unstable csh` will fail
> > (which use bmake) and `sbuild --no-arch-all --no-run-lintian -d
> > unstable csh` does not, since in the former case bmake will get
> > `MAKEFLAGS='w -j1'`.
>
> Please provide more info (logs etc).
>
> Thanks!
>
> --
> Cheers,
>   Andrej

1. sbuild --no-arch-all --no-run-lintian -j1 -d unstable csh
2. sbuild --no-arch-all --no-run-lintian -d unstable csh


csh2.build
Description: Binary data


csh1.build
Description: Binary data

Bug#985492: python-debian: should include Build-Depends-Arch and Build-Conflicts-Arch

[Yangfl]

Package: python-debian
Severity: important

https://salsa.debian.org/python-debian-team/python-debian/-/blob/master/lib/debian/deb822.py#L2274

which ignores Build-Depends-Arch and Build-Conflicts-Arch as mentioned in

https://www.debian.org/doc/debian-policy/ch-relationships.html#relationships-between-source-and-binary-packages-build-depends-build-depends-indep-build-depends-arch-build-conflicts-build-conflicts-indep-build-conflicts-arch

Bug#982865: meson: meson ignores CPPFLAGS

[Yangfl]

Package: meson
Version: 0.57.0-1

When packaging https://salsa.debian.org/yangfl-guest/sequeler , I got
blhc warning about CPPFLAGS missing (-D_FORTIFY_SOURCE=2) after
upgrading meson from 0.56.2-1 to 0.57.0-1.

Log attached.


meson-old
Description: Binary data


meson-new
Description: Binary data

Bug#982029: imgui: crash with floating point exception

[Yangfl]

Control: reassign -1 libstb
Control: severity -1 important

https://github.com/nothings/stb/issues/189

Bug#981864: libinih: Please provide libinih1-udeb

[Yangfl]

在 2021年2月9日星期二，Bastian Germann  写道：

> On Mon, 8 Feb 2021 15:36:31 +0100 Cyril Brulebois  wrote:
>
>> We would be happy to have this merged soon, since xfs support in the
>> installer is currently broken:
>>
>>   https://bugs.debian.org/981662
>>
>> I'm happy to upload the package and talk to the ftp team (a little
>> trip to NEW will happen) myself if that helps.
>>
>
> Yes, please upload. I think, the timeline justifies a NMU.
>

Hi, please upload the latest version from git repo, I have some troubles
finding sponsor, thanks.

Bug#980029:

[Yangfl]

There is no UEFIExtract in its master branch.

Bug#975381: Subject: libinih: drop Debian's custom vendorisation

[Yangfl]

Stephan Lachnit  于2020年11月21日周六 下午8:20写道：
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Package: tech-ctte
> Severity: wishlist
>
> Currently the package libinih uses some heavy patches, which aren't upstream
> and aren't used by any other distro. I'm in favor of dropping this, but the
> current maintainer disagrees and we weren't able to make any progess in the
> discussion, so I want to put this here. Parts of the discussion can be found 
> on
> this MR: https://salsa.debian.org/yangfl-guest/inih/-/merge_requests/2
>
> To understand this, one has to look a bit at the history behind inih. Upstream
> was designed as a static library for embedded devices, and therefore has a lot
> of compile time options. At this point, the current maintainer created a patch
> to make all compile time option available on runtime.
>
> When gamemode started using inih, I wanted to get rid of shipped inih code and
> upstreamed a build system to inih for a shared library, that any distro can
> use. This was done in version 48. Due to the popularity of gamemode, inih is
> now found in most major distros (all without Debian's patches):
> https://repology.org/project/inih/versions
>
> There is a notable "exception": inih is not in Ubuntu's main repository. This
> is a bit weird because gamemode is in main, but with the shipped inih source
> which got dropped from 1.6, meaning gamemode is stuck on 1.5.1 on Ubuntu. I'm
> not sure why, but I suspect the heavy patches make it harder to be included in
> main.
>
> Because the library was designed for embedded use cases where every little bit
> of performance matters, the runtime patch was refused upstream. Dropping the
> runtime patch from Debian actually isn't problem, no reverse dependency of
> libinih uses compile time options anyway. However, due to the history of inih
> in Debian is has the soversion 1, while upstream is soversion 0.
>
> I want to drop the vendorisation of Debian and start a transition to soversion
> 0 (which is also a reason I contact the Technical Committee, as it's not clear
> how this would be done). A transition is needed anyway since dropping the 
> patch
> is a breaking change anyway. If the Technical Committee agrees to this, I 
> would
> also gladly help to maintain this package since it is 2 version behind 
> upstream
> since almost half a year and I maintain gamemode, which is directly affected 
> by
> this.
>
> This isn't urgent, but it would be nice to get this done till bulleseye.
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEu0Wws/9WG9vUXuips1tJ6l1WPv4FAl+5BWIACgkQs1tJ6l1W
> Pv7dyA//QMHV+BGlUzXIMCcBlkVnYe85/TT8xH2peZTZ7j5ULBwvGGVhYG1Dt8/A
> PcziDIcVLhmEN6N5r9vTispp0McTy5nNpotVgZ/5KJ1+WzRS+7D1YGXyS6YOTF7H
> p4rK7PMMok8Yvjrxe/k8TRqRL6tw9+1cXRYhSBQg0TQGPTCEPh5nlWSgSOTKyHAe
> ZAcpeUmLXvI0fLHiKAyxtI2nVPadWy+MFlJP4oJU1ml5+4ZUqDZ/DcC+qeHE8tSh
> 8oFdtG4/3REtb1e2x0LfeV45oj/MBv7X6IyWaw5vvjzLEiZHxuY8SRgMpgBzkNaC
> y675orpcwNKFFkA5PdlxtGstDfzoUi70Gl8sNMNFt26w3+eX9+w/CxpgSIftHp6/
> 2cJRlgjfN6a2Eog9skq6XhGGoVZ1HHjq1mAtinKw9Wv0L88hd62PCzRu+ZVScGr8
> MNK43VxbP2PCBMWY5z9uFlANBbgY4R4wPbKjZmH9NJW3yJDXHeKjCGfDrw3KX/5l
> eIC+CbfEMuPHl02HY6TJwn0cDeEsRiyrLA+4aHrG1Vxy92L+4PPsQuJts6DzmGej
> HNiyXvaSC88ovkOk2mgxtPx+dgI3qpmpMzJYqkpHg2Eo5zn12DpiubsZRHmR/1Fz
> hrE4lwvV3W1DN4ztQs/Faa9zsRgPrhgEVKJMuqCwLSDeMovXCsY=
> =kj7T
> -END PGP SIGNATURE-

I think I've stated it clearly: you have not placed any valid
objection against the patch. Performance is not an issue on Debian,
and as a Debian maintainer, I have zero responsibility for any Ubuntu
stuff. IIRC, a package is not in Ubuntu main repo simply because no
one in Ubuntu side maintain it.

If you can't come up with an objection, I can give you one now: the
option affect globally, meaning that if a library modifies one option,
other part of that program will be affected. But my opinion is, as
long as the library is only linked against the main program, nothing
bad will happen. See #958243, in that case, they DO use modified inih.

The reason I have not catched up with the upstream release is they tag
every single git commit as a release, and no breaking changes happened
in that 2 releases (except for a new compile option). However if I'm
wrong or you'd like a new release, you could file a new bug for
updating.

Bug#973974: RFP: grab -- simple but very fast grep

[Yangfl]

Any adantages over existing grep alternatives (ack, silversearcher-ag, ripgrep)?

Bug#975045: [Debian-zh-dev] Bug#975045: galternatives fails to build for binnmu

[Yangfl]

Sven Mueller  于2020年11月18日周三 下午6:39写道：
>
> Package: galternatives
> Version: 1.0.7
> Tags: patch
>
> debian/rules compares the version from debian/changelog with the version 
> reported by the INFO dict. However, this fails if a binnmu is at play:
>
> A binnmu adds a changelog entry with +bX (X being an integer), but generally 
> speaking, rebuilds might add almost any + suffixes.
>
> I suggest to change debian/rules as follows to allow for binnmus:
>
> Add:
>
> BASE_VERSION=$(shell dpkg-parsechangelog \
>   sed -rne 's/^Version: ([0-9.]+)(\+.*)?/\1/p')
>
> And compare to that instead of DEB_VERSION_UPSTREAM
>
> This is similar to what is done for DEB_VERSION_UPSTREAM in pkg-info.mk, but 
> acknowledges the fact that galternatives is a native Debian package and thus 
> the whole version from the changelog is recognized as the upstream version.
>
> For 1.2-1+b1, DEB_VERSION_UPSTREAM would have 1.2, as it strips the last - 
> and everything after it.
>
> Patch attached, this time I'll refrain from submitting anything to salsa... I 
> caused too much chaos with the previous commits already (I hope I cleaned it 
> up though).

Wait, does arch: all package ever has a chance to do binnmu?

Bug#973329: Use system libimgui-dev

[Yangfl]

Source: dart
Severity: wishlist

Hi,

As libimgui-dev is now available, please consider using system library.

Also, it may be desirable to remove libdart6-external-imgui since
providing duplicate packages may cause confusion.

Bug#967591: libwmf: depends on deprecated GTK 2

[Yangfl]

On Tue, 04 Aug 2020 11:52:42 +0100 s...@debian.org wrote:
> Source: libwmf
> Severity: normal
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: gtk2 oldlibs
> Control: block 947713 by -1
>
> This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
> binary packages with a Depends on GTK 2.
>
> GTK 2 was superseded by GTK 3 in 2011 (see
> ). It no longer receives any significant
> upstream maintenance, and in particular does not get feature development
> for new features like UI scaling on high-pixel-density displays (HiDPI)
> and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
> approaching release, so it seems like a good time to be thinking about
> minimizing the amount of GTK 2 in the archive.
>
> GTK 2 is used by some important productivity applications like GIMP, and
> has also historically been a popular UI toolkit for proprietary software
> that we can't change, so perhaps removing GTK 2 from Debian will never be
> feasible. However, it has reached the point where a dependency on it is
> a bug - not a release-critical bug, and not a bug that can necessarily
> be fixed quickly, but a piece of technical debt that maintainers should
> be aware of.
>
> A porting guide is provided in the GTK 3 documentation:
> https://developer.gnome.org/gtk3/stable/migrating.html
>
> Some libraries (for example libgtkspell0) expose GTK as part of their
> API/ABI, in which case removing the deprecated dependency requires
> breaking API/ABI. For these libraries, in many cases there will already
> be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
> case the GTK 2-based library should probably be deprecated or removed
> itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
> maintainers should talk to the dependent library's upstream developers
> about whether the dependent library should break API/ABI and switch
> to GTK 3, or whether the dependent library should itself be deprecated
> or removed.
>
> A few packages extend GTK 2 by providing plugins (theme engines, input
> methods, etc.) or themes, for example ibus and mate-themes. If these
> packages deliberately support GTK 2 even though it is deprecated, and
> they also support GTK 3, then it is appropriate to mark this mass-filed
> bug as wontfix for now. I have tried to exclude these packages from
> the mass-bug-filing, but I probably missed some of them.
>
> Regards,
> smcv

This package provides GTK 2 pixbuf plugin and only one package (qiv,
which already depends on GTK 2) depends on it. Since the upstream of
libwmf is dead and exists only for historical reason, I think it's
fine to remove GTK plugin if GTK 2 is to be removed from the repo.

Bug#971924: RFP: ironseed -- science-fiction exploration/strategy adventure game in space

[Yangfl]

On Fri, 09 Oct 2020 22:46:34 +0200 Matija Nalis
 wrote:
> Package: wnpp
> Severity: wishlist
>
> * Package name: ironseed
>   Version : 0.2.4
>   Upstream Author : Matija Nalis 
> * URL : https://github.com/mnalis/ironseed_fpc
> * License : GPLv3
>   Programming Lang: Pascal
>   Description : science-fiction exploration/strategy adventure game in 
> space
>
>  It was originally both developed and published by Channel 7 for DOS in 1994.
>  Gameplay is real-time, featuring trading, diplomacy, and strategy, and
>  somewhat resembles Star Control 2 / Ur-Quan masters.
>  DOS sources have been changed to make it possible to compile it with the
>  freepascal compiler under Linux and SDL, and many bugs were fixed.
>
> Wikipedia entry: https://en.wikipedia.org/wiki/Iron_Seed
>
> The DOS version of the game was originally released under GPLv3 on
> http://ironseed.net by original developers,
> ported to SDL by https://github.com/y-salnikov/ironseed_fpc
> and further improved by
> https://github.com/nukebloodaxe/ironseed_fpc
> and finally many bugs fixed by:
> https://github.com/mnalis/ironseed_fpc (disclaimer: myself)
>
> It is a nice game (or I wouldn't invest time in fixing bugs in it!)
> I've done basic Debian packaging in github repo, and resulting Debian
> package builds and runs fine with me. I'm hoping to find someone willing to
> help me push it to Debian GNU/Linux, so more people can easily get it and
> have fun playing it.
>
> If more work is required on it, I'm willing to do it, if someone will
> point me in right direction. But I am not DD and thus cannot do it all
> the way through myself.
>
> If I get Debian lingo right, I'm looking for a sponsor.
>
>
Hi,

Since you'd like to do the packaging stuff yourself, you'd better take
a look at ITP/RFS process and refine your package to fit the policy.
The RFP process is to ask someone else to do the packaging.

Bug#969184: Re: Bug#969184: Upgrade fails when interface name has changed

[Yangfl]

On Sat, 29 Aug 2020 18:27:43 +0200 martin.st...@elektro-potkan.cz wrote:
> Hello all,
>
> I came across a similar issue today during 'apt-get upgrade' on my
> Debian unstable amd64 machine. The system was installed back in 2014 as
> Debian Wheezy and through the years (dist-)upgraded until the current
> unstable. The minissdpd package was probably installed as part of the
> system installation at the beginning as it was completely unknown to me
> (and I have never dealt with its configuration). DPKG failed with the
> following message:
> --
> Nastavuje se balík minissdpd (1.5.20190824-1) …
> Job for minissdpd.service failed because the control process exited with
> error code.
> See "systemctl status minissdpd.service" and "journalctl -xe" for
> details.
> invoke-rc.d: initscript minissdpd, action "restart" failed.
> ● minissdpd.service - keep memory of all UPnP devices that announced
> themselves
>   Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled;
> vendor preset: enabled)
>   Active: failed (Result: exit-code) since Sat 2020-08-29 16:08:28
> CEST; 23ms ago
> Docs: man:minissdpd(1)
>  Process: 16207
> ExecCondition=/usr/lib/minissdpd/minissdpd-systemd-wrapper -t
> ${MiniSSDPd_INTERFACE_ADDRESS} (code=exited, status=0/SUCCESS)
>  Process: 16208
> ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper
> ${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited,
> status=1/FAILURE)
>
> srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]: Error
> parsing address/mask (or interface name) : eth0
> srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]: can't parse
> "eth0" as a valid address or interface name
> srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]: Usage:
> /usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f
> device] -i  [-i ] ...
> srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]:
>  is either an IPv4 address with mask such as
> srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]:
> 192.168.1.42/255.255.255.0, or an interface name such as eth0.
> srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]:   By
> default, socket will be open as /var/run/minissdpd.sock
> srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]:   and pid
> written to file /var/run/minissdpd.pid
> srp 29 16:08:28 P01-MARTIN systemd[1]: minissdpd.service: Control
> process exited, code=exited, status=1/FAILURE
> srp 29 16:08:28 P01-MARTIN systemd[1]: minissdpd.service: Failed with
> result 'exit-code'.
> srp 29 16:08:28 P01-MARTIN systemd[1]: Failed to start keep memory of
> all UPnP devices that announced themselves.
> dpkg: chyba při zpracovávání balíku minissdpd (--configure):
>   installed minissdpd package post-installation script subprocess
> returned error exit status 1
> --
>
> After that, I tried changing the '/etc/default/minissdpd' config file to
> reflect my current interface name ('enp0s25'), but after running
> 'apt-get upgrade' again, it was rewritten back to 'eth0' (like Dann

This works as intended, by sololy trusting the debconf config but not
the text file, so you are supposed to always update that file via
debconf. But if everyone here hates debconf, we can make the config
file as the default.

Bug#940329:

[Yangfl]

Any progress? If not, I'm willing to package this.

Bug#968177:

[Yangfl]

not under active development?

Bug#961723: miniupnpd: does not work with the default iptables by update-alternatives

[Yangfl]

On Thu, 28 May 2020 21:05:43 +0900 Ryutaroh Matsumoto
 wrote:
> Package: miniupnpd
> Version: 2.1-6.1
> Severity: important
>
> Dear Maintainer,
>
> When iptables Debian package is installed,
> we have two versions, iptables-nft and iptables-legacy.
> The default in Buster and Bullseye is iptables-nft, as
> https://wiki.debian.org/iptables
>
> /etc/miniupnpd/iptables_init.sh registers chain MINIUPNPD
> by iptables_nft.
> But
> https://github.com/miniupnp/miniupnp/blob/master/miniupnpd/netfilter/iptcrdr.c
> tries to find chain MINIUPNPD by the legacy interface, and
> miniupnpd fails with
> chain MINIUPNPD not found
> when a new redirection is added.
>
> It MIGHT be good idea to build the package with
> ./configure --firewall=nftables ...
> Or, call update-alternatives --set iptables /usr/sbin/iptables-legacy
> by the installation script...
>
> Best regards, Ryutaroh Matsumoto

I agree nftables is better, however switching to nftables will
definitely disappoint legacy iptables, and it seems there is no way to
enable iptables and nftables in a single binary.

Bug#964069: transition: adplug

[Yangfl]

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

adplug uses a versioned soname. Packages which should only require binNMU:

  adplay
  mpd
  ocp

https://release.debian.org/transitions/html/auto-adplug.html

Bug#963725: fcitx5: Lack of proper metapackages/instructions / not work out-of-the-box

[Yangfl]

Source: fcitx5

Dear Maintainer,

In the current packaging scheme, most people won't know that only
installing `fcitx5` or `fcitx5-chinese-addons` will not make fcitx5
work. Instead,

* They should install corresponding IM module `fcitx5-frontend-gtk2`
`fcitx5-frontend-gtk3` `fcitx5-frontend-qt5` before they can virtually
input anything.
* The fcitx5 configure tool will complain about the
missing`fcitx5-config-qt` but the package name is actually
`kde-config-fcitx5`.
* They should install `fcitx5-module-dbus` to make config work.

Besides a disclaimer in /usr/share/doc/fcitx5/README.Debian , there
are no other instructions to deal with the above (of many possible)
packaging-related problems.

Bug#963723: fcitx5: panel icon is only 1 pixel wide

[Yangfl]

Package: fcitx5
Version: 0.0~git20200409.6409547-1
Severity: minor

Dear Maintainer,

See the attachment.

Desktop: mate

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

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

Versions of packages fcitx5 depends on:
ii  fcitx5-data   0.0~git20200409.6409547-1
ii  fcitx5-modules0.0~git20200409.6409547-1
ii  libc6 2.30-8
ii  libexpat1 2.2.9-1
ii  libfcitx5config5  0.0~git20200409.6409547-1
ii  libfcitx5core50.0~git20200409.6409547-1
ii  libfcitx5utils1   0.0~git20200409.6409547-1
ii  libgcc-s1 10.1.0-3
ii  libjson-c40.13.1+dfsg-9
ii  libstdc++610.1.0-3

fcitx5 recommends no packages.

Versions of packages fcitx5 suggests:
ii  fcitx5-chinese-addons  0.0~git20200409.5a087da-2
pn  fcitx5-frontend-gtk2   
ii  fcitx5-frontend-gtk3   0.0~git20200402.3e6795d-1
ii  fcitx5-frontend-qt50.0~git20200404.366aed5-1
ii  im-config  0.44.1-1

-- no debconf information

Bug#962787: gocr: dangling gocr-dev

[Yangfl]

Source: gocr

Hi,

The purpose of gocr-dev is uncleared. gocr is not a library, there is
no readme to state how to use this package, and the mentioned libgocr
package has long been removed from archive.

As k2pdfopt requires libgocr, it would be great if you could consider
providing libgocr.

Bug#933214: fdisk: program loops with "Do you really want to quit?"

[Yangfl]

Chris Hofstaedtler  于2020年5月4日周一 上午3:37写道：
>
> Control: tags -1 + moreinfo upstream unreproducible
>
> Hi Yangfl,
>
> * Yangfl  [200503 19:35]:
> > The program can be tricked inot a situation where
> >
> >   Do you really want to quit?
> >   Command (m for help):
> >
> > is printed over and over by issuing the following command sequence:
> >
> >   g
> >   n
> >   
> >   
> >   
>
> I've tried this on 2.35.1 and could not reproduce it. If you still
> see this problem, please contact upstream, as this can't be a
> Debian-only problem, and let us know the upstream bug URL.
>
> Thanks,
> Chris
>

Seen on 2.34-0.1 but not 2.35.1-1. Not sure if that is
(unintentionally) fixed by upstream.

Bug#956183: transition: libwmf

[Yangfl]

Emilio Pozuelo Monfort  于2020年4月25日周六 下午8:27写道：
>
> On 08/04/2020 07:02, Yangfl wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> >
> > libwmf is released with package split, and old-style config script
> > dropped with pkg-config file introduced. There are three packages
> > needing patches against `libwmf-config':
> >
> >   wv
> >   gimp
> >   abiword
> >
> > and two packages which should only require binNMU:
> >
> >   graphicsmagick
> >   imagemagick
> >
> > I didn't do a test rebuild of these packages, because full rebuild
> > would take too long time. The new version of libwmf should not have
> > any API/ABI breakage, so I don't expect any ftbfs.
>
> It would be good to disentangle the package split (which due to the Breaks 
> will
> mean we need a lockstep transition with all or most packages migrating at the
> same time) from the libwmf-config removal. If you reintroduce the script and 
> the
> rdeps build against the new libwmf version, then we can go ahead with this, 
> and
> libwmf-config could be removed after the transition. Otherwise we'll need to
> wait until those packages are fixed.
>
> Cheers,
> Emilio

https://salsa.debian.org/yangfl-guest/libwmf/-/commit/a542eed89c98bde74d410f6ea07ab7a3be77ebab

Readded libwmf-config into /usr/bin. If that's ok we can upload it to
unstable, and the transition should only require binNMU.

Bug#958250: Use system libjsonparser-dev

[Yangfl]

Jonas Smedegaard  于2020年4月20日周一 下午7:29写道：
>
> Quoting Sebastian Ramacher (2020-04-20 13:20:59)
> > On 2020-04-20 13:07:40 +0200, Jonas Smedegaard wrote:
> > > Quoting Sebastian Ramacher (2020-04-20 12:51:09)
> > > > On 2020-04-20 09:06:51, Yangfl wrote:
> > > > > As libjsonparser-dev is now available, please consider linking
> > > > > against system library instead of bundled json.c.
> > > >
> > > > The last release of libjsonparser was in 2014. In the meantime, vlc's
> > > > copy has seen some fixes (more so in the master branch than the
> > > > current version in Debian). Are there any plans upstream to release a
> > > > new version of libjsonparser? I don't think switching vlc to an older
> > > > libjsonparser makes sense.
> > >
> > > Seems you are asking the wrong place: Upstream developers of
> > > libjsonparser propably don't follow this bugreport.
> > >
> > > Probably helpful to go the other way: Inform libjsonparser upstream (or
> > > at least Debian maintainers ot its package) about fixes existing
> > > downstream in VLC.
> >
> > Yangfl is the package maintainer of libjsonparser in Debian …
>
> Good point.
>
> Still, better to share issues with libjsonparser as a bugreport against
> libjsonparser rather than here.
>
>  - Jonas
>
I reviewed json.c in vlc and it seems an outdated version (1.0.0)
rather than 1.1.0. Some problems (like 'Fix check for
json_relaxed_commas') already fixed in 1.1.0 in another way. Other
fixes 
https://github.com/videolan/vlc/commits/master/modules/misc/webservices/json.c
are all minor but I will pick them into Debian package.

Bug#958270: nmu: nohang_0.1-1

[Yangfl]

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

nmu nohang_0.1-1 . all . unstable . -m "Rebuild on buildd"

Bug#958269: nmu: libinih_48-1

[Yangfl]

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

nmu libinih_48-1 . amd64 . unstable . -m "Rebuild on buildd"

Bug#958265: Use system libqrcodegen-dev

[Yangfl]

Source: network-manager
Severity: wishlist

Hi,

As libqrcodegen-dev package is now available, please consider linking
against system library instead of bundled qrcodegen.c.

Bug#958266: Use system libqrcodegen-dev

[Yangfl]

Source: network-manager-applet
Severity: wishlist

Hi,

As libqrcodegen-dev package is now available, please consider linking
against system library instead of bundled qrcodegen.c.

Bug#958267: Use system libqrcodegen-dev

[Yangfl]

Source: faust
Severity: wishlist

Hi,

As libqrcodegen-dev package is now available, please consider linking
against system library instead of bundled qrcodegen.c.

Bug#958268: Use system libqrcodegen-dev

[Yangfl]

Source: radare2
Severity: wishlist

Hi,

As libqrcodegen-dev package is now available, please consider linking
against system library instead of bundled qrcodegen.c.

Bug#958264: Use system libqrcodegen-dev

[Yangfl]

Source: smplayer
Severity: wishlist

Hi,

As libqrcodegen-dev package is now available, please consider linking
against system library instead of bundled qrcodegen.c.

Bug#958262: Use system axTLS

[Yangfl]

Source: argyll
Severity: wishlist

Hi,

As axTLS package is now available, please consider linking against
system library instead of bundled one.

Bug#958263: Use system axTLS

[Yangfl]

Source: gauche
Severity: wishlist

Hi,

As axTLS package is now available, please consider linking against
system library instead of bundled one.

Bug#958261: Use system libsimpleini-dev

[Yangfl]

Source: funguloids
Severity: wishlist

Hi,

As libsimpleini-dev is now available, please consider linking against
system library instead of bundled SimpleIni.h.

Bug#958260: Use system libsimpleini-dev

[Yangfl]

Source: mrpt
Severity: wishlist

Hi,

As libsimpleini-dev is now available, please consider linking against
system library instead of bundled SimpleIni.h.

Bug#958258: Use system libminini-dev

[Yangfl]

Source: drc
Severity: wishlist

Hi,

As libminini-dev is now available, please consider linking against
system library instead of bundled minIni.c.

Bug#958259: Use system libminini-dev

[Yangfl]

Source: libnss-securepass
Severity: wishlist

Hi,

As libminini-dev is now available, please consider linking against
system library instead of bundled minIni.c.

Bug#958255: Use system libjsonparser-dev

[Yangfl]

Source: shadowsocks-libev
Severity: wishlist

Hi,

As libjsonparser-dev is now available, please consider linking against
system library instead of bundled json.c.

Bug#958256: Use system libjsonparser-dev

[Yangfl]

Source: remind
Severity: wishlist

Hi,

As libjsonparser-dev is now available, please consider linking against
system library instead of bundled json.c.

Bug#958252: Use system libjsonparser-dev

[Yangfl]

Source: simple-obfs
Severity: wishlist

Hi,

As libjsonparser-dev is now available, please consider linking against
system library instead of bundled json.c.

Bug#958251: Use system libjsonparser-dev

[Yangfl]

Source: bitlbee
Severity: wishlist

Hi,

As libjsonparser-dev is now available, please consider linking against
system library instead of bundled json.c.

Bug#958254: Use system libjsonparser-dev

[Yangfl]

Source: cctools
Severity: wishlist

Hi,

As libjsonparser-dev is now available, please consider linking against
system library instead of bundled json.c.

Bug#958250: Use system libjsonparser-dev

[Yangfl]

Source: vlc
Severity: wishlist

Hi,

As libjsonparser-dev is now available, please consider linking against
system library instead of bundled json.c.

Bug#958253: Use system libjsonparser-dev

[Yangfl]

Source: pgpool2
Severity: wishlist

Hi,

As libjsonparser-dev is now available, please consider linking against
system library instead of bundled json.c.