Bug#1001320: needrestart misdetects socket activated ssh and restarts service instead of socket
On Fri, Dec 24, 2021 at 11:04:20PM +, Colin Watson wrote: > diff --git a/debian/README.Debian b/debian/README.Debian > index dbe6c2958..0851e38e3 100644 > --- a/debian/README.Debian > +++ b/debian/README.Debian > @@ -193,9 +193,12 @@ you can run: > > To make this permanent: > > - systemctl disable ssh.service > + systemctl mask ssh.service >systemctl enable ssh.socket I think the service needs to be stopped (and disable?) before masking it. I would also mention that there might be cases of logins no longer possible regarding library updates and needrestart. This is a serious situation. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#965723: mhonarc: diff for NMU version 2.6.19-2.2
Control: tags 965723 + patch Control: tags 965723 + pending Dear maintainer, I've prepared an NMU for mhonarc (versioned as 2.6.19-2.2) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards. diff -u mhonarc-2.6.19/debian/changelog mhonarc-2.6.19/debian/changelog --- mhonarc-2.6.19/debian/changelog +++ mhonarc-2.6.19/debian/changelog @@ -1,3 +1,10 @@ +mhonarc (2.6.19-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Increased debhelper compat level to 11 (closes: #965723) + + -- Stefan Hornburg (Racke) Sat, 25 Dec 2021 07:39:51 +0100 + mhonarc (2.6.19-2.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -u mhonarc-2.6.19/debian/compat mhonarc-2.6.19/debian/compat --- mhonarc-2.6.19/debian/compat +++ mhonarc-2.6.19/debian/compat @@ -1 +1 @@ -5 \ No newline at end of file +11 \ No newline at end of file diff -u mhonarc-2.6.19/debian/control mhonarc-2.6.19/debian/control --- mhonarc-2.6.19/debian/control +++ mhonarc-2.6.19/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Jeff Breidenbach Standards-Version: 3.9.6 -Build-Depends: debhelper (>=5) +Build-Depends: debhelper (>=11) Package: mhonarc Architecture: all
Bug#1002597: curl: temporarily revert adding libssh-dev to Build-Depends
Source: curl Version: 7.80.0-1 Severity: important Dear curl maintainers, curl has added libssh-dev to Build-Depends. While libssh is cross buildable, it has a lot of unconditional dependencies and cannot be added to the bootstrap set as is. As such, curl has broken architecture bootstrap for all architectures now. I propose that curl temporarily reverts this change. Given a month time, I'll very likely figure out a way to add libssh to the bootstrap set. Is that a workable path forward? libssh build dependencies are: * cmake -> Multi-Arch: foreign * debhelper-compat -> Multi-Arch: foreign * libcmocka-dev -> I guess this could be * libgcrypt-dev -> already part of bootstrap * libkrb5-dev | heimdal-dev -> already part of bootstrap * libssl-dev -> already part of bootstrap * libz-dev -> already part of bootstrap, but needs to become non-virtual * openssh-client -> I guess this could be * openssh-server -> I guess this could be * pkg-config -> Multi-Arch: foreign * python3:any -> annotated :any So this looks mostly harmless, but involves non-trivial work and I didn't check build order yet. Given that curl comes relatively late, I don't expect much problems there. So can you give me a month? Helmut
Bug#1002596: zoem: new upstream
Package: zoem Severity: normal https://github.com/micans/zoem/releases/tag/21-341 released dec 10, 2021. See also #993009 ITP: cimfomfa -- tingea library for mcl and zoem
Bug#1002595: debbugs: get_bug_log can incorrectly return an e-mail body with xsi:type="xsd:long"
On Sat, 25 Dec 2021 01:26:00 -0500, Mike Frysinger wrote: > I get that that bug report has a lot of spam, but debbugs prob shouldn't > ever return a with xsi:type other than xsd:long. err, obviously I meant should always have xsi:type of *xsd:string*
Bug#1002542: python-requests-cache breaks howdoi autopkgtest: 'requests_cache' has no attribute 'install_cache'
`control: reassign 1002542 src:python-requests-control control: reassign 1002585 src:python-requests-control control: forcemerge 1002542 1002585 On Sat, Dec 25, 2021 at 12:19 AM Sandro Tosi wrote: > > control: reassign -1 howdoi > > > > With a recent upload of python-requests-cache the autopkgtest of howdoi > > fails in testing when that autopkgtest is run with the binary packages > > of python-requests-cache from unstable. It passes when run with only > > packages from testing. In tabular form: > > there's a new upstream release, which dropped requests_cache, so > updating howdoi is the right way. OTOH, this package has not seen an > upload in 5 and a half years, so i wont hold my breath for that. nevermind the last message: this is totally a requests_cache issue. The issue originates in url_normalize not being in Debian yet[1]; url_normalize is used in cache_keys.py [2], while install_cache() is defined in patcher.py[3] the way requests_cache setup it's first-level objects is via [4], but that try..except means that if any of those imports fails, the others wont be executed, and that's exactly what happens here: $ python3 -c "import requests_cache" ; echo $? No module named 'url_normalize' 0 so `from .cache_keys import create_key` fails and `from .patcher import *` is never executed and so install_cache() is not available. The solution here is to wait for url_normalize to leave NEW. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001442 [2] https://salsa.debian.org/python-team/packages/python-requests-cache/-/blob/master/requests_cache/cache_keys.py#L18 [3] https://salsa.debian.org/python-team/packages/python-requests-cache/-/blob/master/requests_cache/patcher.py#L23 [4] https://salsa.debian.org/python-team/packages/python-requests-cache/-/blob/master/requests_cache/__init__.py#L42-52 -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#1002595: debbugs: get_bug_log can incorrectly return an e-mail body with xsi:type="xsd:long"
Package: debbugs Severity: normal X-Debbugs-Cc: vap...@gentoo.org Running get_bug_log against this report returns bad response: https://bugs.debian.org/557671 message #45 will yield: 4327390041297022 I get that that bug report has a lot of spam, but debbugs prob shouldn't ever return a with xsi:type other than xsd:long.
Bug#1002542: python-requests-cache breaks howdoi autopkgtest: 'requests_cache' has no attribute 'install_cache'
control: reassign -1 howdoi > With a recent upload of python-requests-cache the autopkgtest of howdoi > fails in testing when that autopkgtest is run with the binary packages > of python-requests-cache from unstable. It passes when run with only > packages from testing. In tabular form: there's a new upstream release, which dropped requests_cache, so updating howdoi is the right way. OTOH, this package has not seen an upload in 5 and a half years, so i wont hold my breath for that. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#1002594: doclifter does not run tests
Package: doclifter Version: 2.20-1 Severity: normal Tags: upstream The package doclifter does not run tests with Python 3 and tests builds with 3.9.9. I fixed it in 2.20-1 with # Commands not to run: override_dh_auto_test: In debian/rules It would be interesting to make these tests executable in the future. I plan on reporting this to upstream if no one else has. python -> /usr/bin/python3 make[3]: Entering directory '/<>/tests' capabilities console_ioctl corosync.conf docliftertest1 stdin:110: warning - pic(1) markup not translated. --- docliftertest1.chk2021-09-20 17:47:39.0 + +++ /tmp/regress$2021-12-23 23:20:51.219509872 + @@ -492,21 +492,14 @@ -Now we'll test PIC translation to SVG. +Now we'll test PIC translation to SVG. - - -http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd'>http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> -http://www.w3.org/2000/svg'>http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ev="http://www.w3.org/2001/xml-events"> -SVG drawing -This was produced by version 4.4 of GNU libplot, a free library for exporting 2-D vector graphics. - - - -box - - - + +.PS +box "box" +.PE + + This line tests recognition of superscripting) ,br *** Output differs make[3]: *** [Makefile:17: regress] Error 1 make[3]: Leaving directory '/<>/tests' make[2]: *** [Makefile:9: default] Error 2 make[2]: Leaving directory '/<>/tests' make[1]: *** [Makefile:43: check] Error 2 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j4 check returned exit code 2 make: *** [debian/rules:4: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP PUBLIC KEY BLOCK- mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh 0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7 ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3 k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx /m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C +DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4 hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08 iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X 7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00 4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9 WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e
Bug#1002530: marked as pending in openrazer
I believe there is excessive closing bracket: #if defined(CONFIG_HIDRAW) && (defined(CONFIG_USB) || defined(CONFIG_USB_MODULE) /* here -> */) On Fri, 24 Dec 2021 09:45:07 + =?UTF-8?B?RHlsYW4gQcOvc3Np?= wrote: > Control: tag -1 pending > > Hello, > > Bug #1002530 in openrazer reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below and you can check the diff of the fix at: > > https://salsa.debian.org/debian/openrazer/-/commit/fb2f8d2db1e139f488bafa1b0264cb34e8e70bdb > > > Also check for CONFIG_USB_MODULE before to build dummy drivers (Closes: #1002530) > > > (this message was generated automatically) > -- > Greetings > > https://bugs.debian.org/1002530 > >
Bug#1001809: libsdl2/2.0.18 breaks osk-sdl autopkgtest: Testing osk toggle button and 'mouse' key input
On Sat, 25 Dec 2021 at 09:40:33 +1100, undef wrote: > I'll take a look at those commits early in the new year and > see whether upstream is interested in them. They certainly look helpful for > tracking this one down. Also see https://salsa.debian.org/smcv/osk-sdl/-/commits/debug-for-1001809 for an example of how those changes can be integrated with autopkgtest. smcv
Bug#1001320: needrestart misdetects socket activated ssh and restarts service instead of socket
On Fri, Dec 24, 2021 at 02:21:16PM +0100, Timo Weingärtner wrote:
> 24.12.21 12:22 Marc Haber:
> > So we agree here that it's mainly a documentation issue for ssh, so that
> > it should be recommended to actually mask ssh.service if socket
> > activation is used, right?
>
> For the bug on openssh: yes.
>
> Documentation could look like:
> If you decide to use socket activation consider masking ssh.service to avoid
> accidentally doing the wrong thing with "service ssh restart" or equivalent.
How does this patch look?
diff --git a/debian/README.Debian b/debian/README.Debian
index dbe6c2958..0851e38e3 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -193,9 +193,12 @@ you can run:
To make this permanent:
- systemctl disable ssh.service
+ systemctl mask ssh.service
systemctl enable ssh.socket
+("systemctl disable ssh.service" would also work, but masking avoids
+accidentally starting the service manually.)
+
This may be appropriate in environments where minimal footprint is critical
(e.g. cloud guests). Be aware that this bypasses MaxStartups, and systemd's
MaxConnections cannot quite replace this as it cannot distinguish between
--
Colin Watson (he/him) [cjwat...@debian.org]
Bug#1002593: imdbpy: please package new upstream release
Source: imdbpy Severity: normal X-Debbugs-Cc: mo...@debian.org Hello, upstream released a new version several months ago: 2021.04.18 Please update the debian package. Thanks, Sandro -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/8 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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1001809: [Debian-on-mobile-maintainers] Bug#1001809: libsdl2/2.0.18 breaks osk-sdl autopkgtest: Testing osk toggle button and 'mouse' key input
Hi Simon, See https://github.com/libsdl-org/SDL/issues/5136 for further analysis. osk-sdl maintainers: you might want to consider applying and/or upstreaming some of the "test: ..." commits from https://gitlab.com/smcv/osk-sdl/-/commits/reproduce-sdl-regression to improve the ability to debug this unit test. I do not intend to upstream these myself; feel free to redo them if a modified version makes more sense to you (but please move my name to a Co-authored-by if you do that). Thanks for doing the analysis on this one, I've been meaning to get to it for a while now. I'll take a look at those commits early in the new year and see whether upstream is interested in them. They certainly look helpful for tracking this one down.
Bug#1001809: libsdl2/2.0.18 breaks osk-sdl autopkgtest: Testing osk toggle button and 'mouse' key input
Control: forwarded -1 https://github.com/libsdl-org/SDL/issues/5136 On Thu, 16 Dec 2021 at 18:23:35 +, Simon McVittie wrote: > The osk-sdl autopkgtest on ci.debian.net seems to show a regression when > run with libsdl2 (>= 2.0.18) ... > This could be either a regression in libsdl2, or a pre-existing bug > in osk-sdl. See https://github.com/libsdl-org/SDL/issues/5136 for further analysis. osk-sdl maintainers: you might want to consider applying and/or upstreaming some of the "test: ..." commits from https://gitlab.com/smcv/osk-sdl/-/commits/reproduce-sdl-regression to improve the ability to debug this unit test. I do not intend to upstream these myself; feel free to redo them if a modified version makes more sense to you (but please move my name to a Co-authored-by if you do that). smcv
Bug#1002592: firefox: add-ons not yet active/loaded when FF starts and already loads websites
Package: firefox Version: 95.0.1-1 Severity: important Hey. I think this started around ore some versions before FF87: When I start FF and the previously saved sessions is loaded (i.e. websites), then (at least some) add-ons seem not to be active yet, while those sites load. The best example is, that webext-ublock-origin-firefox doesn't filter ads for YouTube vides, when that video is loaded with FF being started. OTOH, no-script seems to work from the beginning - at least there are sites loaded at FF startup where I can see that scripts are deisabled. I have hoever not made any bigger checks onto whether this is really always working. I'm also rather sure, that this has worked in the past. I only use add-ons from Debian packages, so I cannot say wheter it would work for those loaded from the web. Does anyone else see this, too? Or has some feeling whether this is Debian specific or rather some upstream issue? If so I could forward it there. Thanks, Chris.
Bug#1000739: Missing parts of upstream
Hi, Le vendredi 24 décembre 2021 à 19:00 +0100, Yadd a écrit : > > you were wrong in your fix: you wanted > mdn-browser-compat-data/html/global_attributes.json which is provided > by mdn-browser-compat-data module (not packaged). > > The new @mdn/browser-compat-data provides just one data.json. I think > we should revert your change and you should patch your package to use > @mdn/browser-compat-data/data.json#global_attribute instead of > mdn-browser-compat-data/html/global_attributes.json Why are you claiming this module isn't packaged... in a bug report about its packaging? Its debian/install file didn't list much, so I completed it, and it gave the other package I worked on what it wanted, just like it wanted, no patch necessary -- so I fail to see what's wrong here. I just had a look, and uscan says there's a new 4.1.2 version out, where I see html/global_attributes.json is still there. Are we looking at the same thing? I have: $ git remote -v origin https://salsa.debian.org/js-team/node-mdn-browser-compat-data (fetch) origin https://salsa.debian.org/js-team/node-mdn-browser-compat-data (push) Cheers, J.Puydt
Bug#1002587: python3-sage: Depends on unavailable package
Hi, Tobias. Thanks for the prompt elucidation. Best, Alexandre On December 24, 2021 6:17:16 PM GMT-03:00, Tobias Hansen wrote: >Hi, > >memory-allocator is in NEW (https://ftp-master.debian.org/new.html) since two >weeks and waiting to be approved for inclusion in Debian. I uploaded sagemath >9.4 after memory-allocator but it passed NEW faster. > >Best, >Tobias > >On 12/24/21 9:45 PM, Alexandre Lymberopoulos wrote: >> Package: python3-sage >> Version: 9.4-1 >> Severity: grave >> Justification: renders package unusable >> >> Dear Maintainer, >> >> I was trying for a few weeks to upgrade some packages and it couldn't >> do that due to sage dependencies. Now it has a new version available >> (9.4-1), which depends on python3-sage (9.4-1) that depends itself on >> python3-memory-allocator that shows up as unavailable here. >> >> Any advice? >> >> Thanks in advance and best regards, >> Alexandre >> >> -- System Information: >> Debian Release: bookworm/sid >> APT prefers testing >> APT policy: (900, 'testing'), (800, 'unstable') >> Architecture: amd64 (x86_64) >> >> Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) >> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), >> LANGUAGE=en_US:en >> Shell: /bin/sh linked to /bin/dash >> Init: systemd (via /run/systemd/system) >> >> Versions of packages python3-sage depends on: >> ii bc1.07.1-3+b1 >> ii binutils 2.37-7 >> ii bzip2 1.0.8-5 >> ii ca-certificates 20210119 >> pn cliquer >> ii cmake 3.22.1-1+b1 >> ii curl 7.79.1-2 >> ii cython3 0.29.24-1+b1 >> ii ecl 21.2.1+ds-1 >> ii eclib-tools 20210625-1+b2 >> ii fflas-ffpack 2.5.0-1 >> ii flintqs 1:1.0-3+b1 >> ii gap-atlasrep 2.1.0-3 >> ii gap-dev 4.11.1-1 >> ii gap-online-help 4.11.1-1 >> ii gap-primgrp 3.4.0-1 >> ii gap-smallgrp 1.4.1-2 >> ii gap-table-of-marks1.2.9-1 >> ii gap-transgrp 2.0.6-2 >> ii gfan 0.6.2-6 >> pn gfortran >> ii glpk-utils5.0-1 >> ii gmp-ecm 7.0.4+ds-6 >> ii jmol 14.32.3+dfsg1-1 >> ii lcalc 2.0.4-2 >> ii libatlas3-base [libblas.so.3] 3.10.3-11 >> ii libatomic-ops-dev 7.6.12-1 >> ii libblas3 [libblas.so.3] 3.10.0-2 >> pn libboost-dev >> pn libbraiding-dev >> ii libbraiding0 1.0-1+b1 >> pn libbrial-dev >> pn libbrial-groebner-dev >> ii libbrial-groebner31.2.10-1+b2 >> ii libbrial3 1.2.10-1+b2 >> pn libbz2-dev >> ii libc6 2.33-1 >> pn libcdd-dev >> ii libcdd-tools 094l-2 >> pn libcliquer-dev >> ii libcliquer1 1.21-3 >> pn libcurl4-openssl-dev >> pn libec-dev >> ii libec820210625-1+b2 >> pn libecm-dev >> ii libecm1 7.0.4+ds-6 >> ii libffi-dev3.4.2-3 >> ii libflint-2.8.42.8.4-2 >> pn libflint-arb-dev >> ii libflint-arb2 1:2.21.1-2 >> pn libflint-dev >> pn libfplll-dev >> ii libfreetype6-dev 2.11.0+dfsg-1 >> ii libgap-dev4.11.1-1 >> ii libgap7 4.11.1-1 >> ii libgc-dev 1:8.0.6-1.1 >> ii libgcc-s1
Bug#1002579: libfltk1.3-dev: libfltk1.3-dev is not Multi-Arch:same
Dima Kogan writes: > It would be nice if it was Multi-Arch:same. It would make cross-building > easier. Is there any reason it isn't? I see that it ships > /usr/bin/fltk-config, which would need to be moved to a different > package, maybe. Do you want a patch? Thanks for the suggestion. There is a second file that would be a problem as is: /usr/lib/fltk/FLTK-Targets-none.cmake. I don't think the FTP team would take well to introducing a new binary package for a handful of small files. However, it should in principle be possible to make the package multi-arch-friendly by moving the files to architecture-specific paths and arranging to select appropriate instances dynamically. If you're up for putting together such a patch, I'll be happy to consider it; otherwise, I'll try to find time myself. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#1001320: needrestart misdetects socket activated ssh and restarts service instead of socket
On Fri, Dec 24, 2021 at 02:21:16PM +0100, Timo Weingärtner wrote: > For needrestart we have the problem of the heuristics, that were designed for > non-systemd-systems, also being used on a systemd-system. I have filed Bug#1002591 for needrestart. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1002587: python3-sage: Depends on unavailable package
Hi, memory-allocator is in NEW (https://ftp-master.debian.org/new.html) since two weeks and waiting to be approved for inclusion in Debian. I uploaded sagemath 9.4 after memory-allocator but it passed NEW faster. Best, Tobias On 12/24/21 9:45 PM, Alexandre Lymberopoulos wrote: > Package: python3-sage > Version: 9.4-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I was trying for a few weeks to upgrade some packages and it couldn't > do that due to sage dependencies. Now it has a new version available > (9.4-1), which depends on python3-sage (9.4-1) that depends itself on > python3-memory-allocator that shows up as unavailable here. > > Any advice? > > Thanks in advance and best regards, > Alexandre > > -- System Information: > Debian Release: bookworm/sid > APT prefers testing > APT policy: (900, 'testing'), (800, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages python3-sage depends on: > ii bc1.07.1-3+b1 > ii binutils 2.37-7 > ii bzip2 1.0.8-5 > ii ca-certificates 20210119 > pn cliquer > ii cmake 3.22.1-1+b1 > ii curl 7.79.1-2 > ii cython3 0.29.24-1+b1 > ii ecl 21.2.1+ds-1 > ii eclib-tools 20210625-1+b2 > ii fflas-ffpack 2.5.0-1 > ii flintqs 1:1.0-3+b1 > ii gap-atlasrep 2.1.0-3 > ii gap-dev 4.11.1-1 > ii gap-online-help 4.11.1-1 > ii gap-primgrp 3.4.0-1 > ii gap-smallgrp 1.4.1-2 > ii gap-table-of-marks1.2.9-1 > ii gap-transgrp 2.0.6-2 > ii gfan 0.6.2-6 > pn gfortran > ii glpk-utils5.0-1 > ii gmp-ecm 7.0.4+ds-6 > ii jmol 14.32.3+dfsg1-1 > ii lcalc 2.0.4-2 > ii libatlas3-base [libblas.so.3] 3.10.3-11 > ii libatomic-ops-dev 7.6.12-1 > ii libblas3 [libblas.so.3] 3.10.0-2 > pn libboost-dev > pn libbraiding-dev > ii libbraiding0 1.0-1+b1 > pn libbrial-dev > pn libbrial-groebner-dev > ii libbrial-groebner31.2.10-1+b2 > ii libbrial3 1.2.10-1+b2 > pn libbz2-dev > ii libc6 2.33-1 > pn libcdd-dev > ii libcdd-tools 094l-2 > pn libcliquer-dev > ii libcliquer1 1.21-3 > pn libcurl4-openssl-dev > pn libec-dev > ii libec820210625-1+b2 > pn libecm-dev > ii libecm1 7.0.4+ds-6 > ii libffi-dev3.4.2-3 > ii libflint-2.8.42.8.4-2 > pn libflint-arb-dev > ii libflint-arb2 1:2.21.1-2 > pn libflint-dev > pn libfplll-dev > ii libfreetype6-dev 2.11.0+dfsg-1 > ii libgap-dev4.11.1-1 > ii libgap7 4.11.1-1 > ii libgc-dev 1:8.0.6-1.1 > ii libgcc-s1 11.2.0-13 > pn libgd-dev > ii libgd32.3.0-2 > pn libgf2x-dev > pn
Bug#1002591: misdetects socket activated ssh
Package: needrestart Version: 3.5-5 Severity: normal Hi, when using ssh as a socket activated service (systemctl stop/disable ssh.service, systemctl enable/start ssh.socket), after a library update needrestart will offer to restart ssh.service. This fails since port 22 is occupied by the instance services and causes the machine to be without listening process after logging out. A possible workaround is masking ssh.service, see #1001320. Restarting services... systemctl restart console-log.service cron.service exim4.service haveged.service ippl.service ntp.service rsyslog.service serial-getty@ttyS0.service ssh.service systemd-journald.service systemd-networkd.service systemd-resolved.service systemd-udevd.service Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xeu ssh.service" for details. Service restarts being deferred: /etc/needrestart/restart.d/dbus.service systemctl restart getty@tty1.service systemctl restart systemd-logind.service systemctl restart user@1001.service and the following log entries: Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping LSB: Puts a logfile pager on virtual consoles... Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping Regular background program processing daemon... Dec 8 12:58:26 emptybookworm82 systemd[1]: cron.service: Deactivated successfully. Dec 8 12:58:26 emptybookworm82 cron[429258]: (CRON) INFO (pidfile fd = 3) Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopped Regular background program processing daemon. Dec 8 12:58:26 emptybookworm82 systemd[1]: cron.service: Consumed 15min 4.856s CPU time. Dec 8 12:58:26 emptybookworm82 systemd[1]: Started Regular background program processing daemon. Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping LSB: exim Mail Transport Agent... Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping Entropy Daemon based on the HAVEGE algorithm... Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping LSB: IP protocols logger... Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping Network Time Service... Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping System Logging Service... Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping Serial Getty on ttyS0... Dec 8 12:58:26 emptybookworm82 systemd[1]: serial-getty@ttyS0.service: Deactivated successfully. Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopped Serial Getty on ttyS0. Dec 8 12:58:26 emptybookworm82 systemd[1]: Started Serial Getty on ttyS0. Dec 8 12:58:26 emptybookworm82 systemd[1]: ssh.socket: Deactivated successfully. Dec 8 12:58:26 emptybookworm82 systemd[1]: Closed OpenBSD Secure Shell server socket. Dec 8 12:58:26 emptybookworm82 systemd[1]: ssh.socket: Consumed 10.571s CPU time. Dec 8 12:58:26 emptybookworm82 systemd[1]: Starting OpenBSD Secure Shell server... Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping Flush Journal to Persistent Storage... Dec 8 12:58:26 emptybookworm82 systemd[1]: systemd-networkd-wait-online.service: Deactivated successfully. Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopped Wait for Network to be Configured. Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping Wait for Network to be Configured... Dec 8 12:58:26 emptybookworm82 systemd[1]: Stopping Network Name Resolution... Dec 8 12:58:26 emptybookworm82 systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Dec 8 12:58:26 emptybookworm82 systemd[1]: ssh.service: Failed with result 'exit-code'. Dec 8 12:58:26 emptybookworm82 systemd[1]: Failed to start OpenBSD Secure Shell server. Dec 8 12:58:26 emptybookworm82 ntpd[298]: ntpd exiting on signal 15 (Terminated) Dec 8 12:58:26 emptybookworm82 ntpd[298]: 2a01:4f8:140:246a::2 local addr 2a01:4f8:140:246a::52:100 -> Dec 8 12:58:26 emptybookworm82 haveged[220]: haveged: Stopping due to signal 15 Dec 8 12:58:27 emptybookworm82 cron[429258]: (CRON) INFO (Skipping @reboot jobs -- not system startup) Dec 8 12:58:27 emptybookworm82 systemd[1]: systemd-journal-flush.service: Deactivated successfully. Dec 8 12:58:27 emptybookworm82 systemd[1]: Stopped Flush Journal to Persistent Storage. Dec 8 12:58:27 emptybookworm82 exim4[429259]: exim4_listener. Here is what Timo Weingärtner found out in relation to my bug report against sshd: | To me it looks like a problem in needrestart. The (forked off) sshd process | handling your client connection belongs to cgroup session-NN.scope, no matter | if it was started by systemd socket activation or regular sshd. | | needrestart (invoked with "-vlp" here) detects a process with outdated libs: | | [main] #2111961 uses deleted /lib/x86_64-linux-gnu/libnss_files-2.32.so | [main] #2111961 is a child of #2111904 | | Then it figures out the binary and the cgroup: | | [main] #2111961 exe => /usr/sbin/sshd | [main] trying systemctl status | | cgroup detection didn't work, so: | | [main] #2111961 running /etc/needrestart/hook.d/10-dpkg | [main]
Bug#923191: munin-plugins-c: open_files can't cope with very large max files
Hi, I reported the bug a while ago and it has been fixed. See: https://github.com/munin-monitoring/munin-c/issues/63 It would be nice if the maintainer would have time to upload the new version (0.0.16). Kind regards Alexander
Bug#1002590: ITP: wayvnc -- VNC server for wlroots-based Wayland compositors
Package: wnpp Severity: wishlist Owner: Johannes Schauer Marin Rodrigues X-Debbugs-Cc: debian-de...@lists.debian.org, jo...@debian.org * Package name: wayvnc Version : 0.4.1 Upstream Author : Andri Yngvason * URL : https://github.com/any1/wayvnc * License : ISC Programming Lang: C Description : VNC server for wlroots-based Wayland compositors This is a VNC server for wlroots-based Wayland compositors. It attaches to a running Wayland session, creates virtual input devices, and exposes a single display via the RFB protocol. The Wayland session may be a headless one, so it is also possible to run wayvnc without a physical display attached.
Bug#1002589: pyresample: (autopkgtest) needs update for python3.10: cannot import name 'ft2font' from partially
Source: pyresample Version: 1.22.3-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.10 to the supported Python versions [0]. With a recent upload of python3-defaults the autopkgtest of pyresample fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.9.8-1 pyresample from testing1.22.3-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists what's new in Python3.10, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/996584 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyresample/17837771/log.gz === FAILURES === ___ Test.test_add_gridlines /usr/lib/python3.10/unittest/mock.py:1366: in patched with self.decoration_helper(patched, /usr/lib/python3.10/contextlib.py:135: in __enter__ return next(self.gen) /usr/lib/python3.10/unittest/mock.py:1348: in decoration_helper arg = exit_stack.enter_context(patching) /usr/lib/python3.10/contextlib.py:492: in enter_context result = _cm_type.__enter__(cm) /usr/lib/python3.10/unittest/mock.py:1421: in __enter__ self.target = self.getter() /usr/lib/python3.10/unittest/mock.py:1608: in getter = lambda: _importer(target) /usr/lib/python3.10/unittest/mock.py:1247: in _importer thing = __import__(import_path) /usr/lib/python3/dist-packages/matplotlib/__init__.py:174: in _check_versions() _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ def _check_versions(): # Quickfix to ensure Microsoft Visual C++ redistributable # DLLs are loaded before importing kiwisolver from . import ft2font E ImportError: cannot import name 'ft2font' from partially initialized module 'matplotlib' (most likely due to a circular import) (/usr/lib/python3/dist-packages/matplotlib/__init__.py) /usr/lib/python3/dist-packages/matplotlib/__init__.py:159: ImportError OpenPGP_signature Description: OpenPGP digital signature
Bug#1002588: wurlitzer: autopkgtest regression on ppc64el: AssertionError: assert 65536 == 32768
Source: wurlitzer Version: 3.0.2-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of wurlitzer the autopkgtest of wurlitzer fails in testing when that autopkgtest is run with the binary packages of wurlitzer from unstable on ppc64el. It passes when run with only packages from testing. In tabular form: passfail wurlitzer from testing3.0.2-3 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=wurlitzer https://ci.debian.net/data/autopkgtest/testing/ppc64el/w/wurlitzer/17814179/log.gz Testing with python3.9: = test session starts == platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 rootdir: /tmp/autopkgtest-lxc.yxsc4awn/downtmp/autopkgtest_tmp collected 12 items test.py ...F [100%] === FAILURES === _ test_bufsize _ @pytest.mark.skipif( wurlitzer._get_max_pipe_size() is None, reason="requires _get_max_pipe_size" ) def test_bufsize(): default_bufsize = wurlitzer._get_max_pipe_size() with wurlitzer.pipes() as (stdout, stderr): assert fcntl(sys.__stdout__, wurlitzer.F_GETPIPE_SZ) == default_bufsize assert fcntl(sys.__stderr__, wurlitzer.F_GETPIPE_SZ) == default_bufsize bufsize = 32768 # seems to only accept powers of two? with wurlitzer.pipes(bufsize=bufsize) as (stdout, stderr): assert fcntl(sys.__stdout__, wurlitzer.F_GETPIPE_SZ) == bufsize E AssertionError: assert 65536 == 32768 E+ where 65536 = fcntl(<_io.TextIOWrapper name='' mode='w' encoding='utf-8'>, 1032) E+where <_io.TextIOWrapper name='' mode='w' encoding='utf-8'> = sys.__stdout__ E+and 1032 = wurlitzer.F_GETPIPE_SZ test.py:178: AssertionError === short test summary info FAILED test.py::test_bufsize - AssertionError: assert 65536 == 32768 = 1 failed, 11 passed in 0.72s = autopkgtest [17:10:38]: test pytest OpenPGP_signature Description: OpenPGP digital signature
Bug#1002587: python3-sage: Depends on unavailable package
Package: python3-sage Version: 9.4-1 Severity: grave Justification: renders package unusable Dear Maintainer, I was trying for a few weeks to upgrade some packages and it couldn't do that due to sage dependencies. Now it has a new version available (9.4-1), which depends on python3-sage (9.4-1) that depends itself on python3-memory-allocator that shows up as unavailable here. Any advice? Thanks in advance and best regards, Alexandre -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-sage depends on: ii bc1.07.1-3+b1 ii binutils 2.37-7 ii bzip2 1.0.8-5 ii ca-certificates 20210119 pn cliquer ii cmake 3.22.1-1+b1 ii curl 7.79.1-2 ii cython3 0.29.24-1+b1 ii ecl 21.2.1+ds-1 ii eclib-tools 20210625-1+b2 ii fflas-ffpack 2.5.0-1 ii flintqs 1:1.0-3+b1 ii gap-atlasrep 2.1.0-3 ii gap-dev 4.11.1-1 ii gap-online-help 4.11.1-1 ii gap-primgrp 3.4.0-1 ii gap-smallgrp 1.4.1-2 ii gap-table-of-marks1.2.9-1 ii gap-transgrp 2.0.6-2 ii gfan 0.6.2-6 pn gfortran ii glpk-utils5.0-1 ii gmp-ecm 7.0.4+ds-6 ii jmol 14.32.3+dfsg1-1 ii lcalc 2.0.4-2 ii libatlas3-base [libblas.so.3] 3.10.3-11 ii libatomic-ops-dev 7.6.12-1 ii libblas3 [libblas.so.3] 3.10.0-2 pn libboost-dev pn libbraiding-dev ii libbraiding0 1.0-1+b1 pn libbrial-dev pn libbrial-groebner-dev ii libbrial-groebner31.2.10-1+b2 ii libbrial3 1.2.10-1+b2 pn libbz2-dev ii libc6 2.33-1 pn libcdd-dev ii libcdd-tools 094l-2 pn libcliquer-dev ii libcliquer1 1.21-3 pn libcurl4-openssl-dev pn libec-dev ii libec820210625-1+b2 pn libecm-dev ii libecm1 7.0.4+ds-6 ii libffi-dev3.4.2-3 ii libflint-2.8.42.8.4-2 pn libflint-arb-dev ii libflint-arb2 1:2.21.1-2 pn libflint-dev pn libfplll-dev ii libfreetype6-dev 2.11.0+dfsg-1 ii libgap-dev4.11.1-1 ii libgap7 4.11.1-1 ii libgc-dev 1:8.0.6-1.1 ii libgcc-s1 11.2.0-13 pn libgd-dev ii libgd32.3.0-2 pn libgf2x-dev pn libgiac-dev hi libgiac0 1.7.0.39+dfsg2-1 ii libgivaro-dev 4.2.0-1 ii libgivaro94.2.0-1 pn libglpk-dev ii libglpk40 5.0-1 ii libgmp-dev2:6.2.1+dfsg-3 ii libgmp10
Bug#1002586: pypandoc: autopkgtest regression: Pandoc died with exitcode "47" during conversion: pdflatex not found.
Source: pypandoc
Version: 1.7.1+ds0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of pypandoc the autopkgtest of pypandoc fails in
testing when that autopkgtest is run with the binary packages of
pypandoc from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
pypandoc from testing1.7.1+ds0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pypandoc
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pypandoc/17827529/log.gz
...s...E.
==
ERROR: test_pdf_conversion (tests.TestPypandoc)
--
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.cf_bnnrh/downtmp/build.Fta/src/tests.py",
line 330, in test_pdf_conversion
ret = pypandoc.convert_text('# some title\n', to='pdf',
format='md', outputfile=file_name)
File
"/tmp/autopkgtest-lxc.cf_bnnrh/downtmp/build.Fta/src/pypandoc/__init__.py",
line 106, in convert_text
return _convert_input(source, format, 'string', to,
extra_args=extra_args,
File
"/tmp/autopkgtest-lxc.cf_bnnrh/downtmp/build.Fta/src/pypandoc/__init__.py",
line 351, in _convert_input
raise RuntimeError(
RuntimeError: Pandoc died with exitcode "47" during conversion: pdflatex
not found. Please select a different --pdf-engine or install pdflatex --
see also /usr/share/doc/pandoc/README.Debian
--
Ran 25 tests in 1.564s
FAILED (errors=1, skipped=1)
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
/home/debci
autopkgtest [05:11:41]: test unittests
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1002585: python-requests-cache breaks rows autopkgtest: 'requests_cache' has no attribute 'install_cache'
Source: python-requests-cache, rows
Control: found -1 python-requests-cache/0.8.1-2
Control: found -1 rows/0.4.1-4
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of python-requests-cache the autopkgtest of rows
fails in testing when that autopkgtest is run with the binary packages
of python-requests-cache from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
python-requests-cache from testing0.8.1-2
rows from testing0.4.1-4
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of
python-requests-cache to testing [1]. Due to the nature of this issue, I
filed this bug report against both packages. Can you please investigate
the situation and reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python-requests-cache
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rows/17837757/log.gz
#1 rows print debian/tests/table.csv
--
[FAILED #1, line 1] rows print debian/tests/table.csv
@@ -1,7 +1,17 @@
-+---+---+---+
-| a | b | c |
-+---+---+---+
-| 1 | 2 | 3 |
-| 4 | 5 | 6 |
-+---+---+---+
-
+No module named 'url_normalize'
+Traceback (most recent call last):
+ File "/usr/bin/rows", line 33, in
+sys.exit(load_entry_point('rows==0.4.1', 'console_scripts', 'rows')())
+ File "/usr/lib/python3/dist-packages/click/core.py", line 1126, in
__call__
+return self.main(*args, **kwargs)
+ File "/usr/lib/python3/dist-packages/click/core.py", line 1051, in main
+rv = self.invoke(ctx)
+ File "/usr/lib/python3/dist-packages/click/core.py", line 1654, in invoke
+super().invoke(ctx)
+ File "/usr/lib/python3/dist-packages/click/core.py", line 1393, in invoke
+return ctx.invoke(self.callback, **ctx.params)
+ File "/usr/lib/python3/dist-packages/click/core.py", line 752, in invoke
+return __callback(*args, **kwargs)
+ File "/usr/lib/python3/dist-packages/rows/cli.py", line 160, in cli
+requests_cache.install_cache(str(http_cache_path))
+AttributeError: module 'requests_cache' has no attribute 'install_cache'
--
#2 echo $?
#3 rows query "SELECT * FROM table1 WHERE a = 1" debian/tests/table.csv
--
[FAILED #3, line 11] rows query "SELECT * FROM table1 WHERE a = 1"
debian/tests/table.csv
@@ -1,6 +1,17 @@
-+---+---+---+
-| a | b | c |
-+---+---+---+
-| 1 | 2 | 3 |
-+---+---+---+
-
+No module named 'url_normalize'
+Traceback (most recent call last):
+ File "/usr/bin/rows", line 33, in
+sys.exit(load_entry_point('rows==0.4.1', 'console_scripts', 'rows')())
+ File "/usr/lib/python3/dist-packages/click/core.py", line 1126, in
__call__
+return self.main(*args, **kwargs)
+ File "/usr/lib/python3/dist-packages/click/core.py", line 1051, in main
+rv = self.invoke(ctx)
+ File "/usr/lib/python3/dist-packages/click/core.py", line 1654, in invoke
+super().invoke(ctx)
+ File "/usr/lib/python3/dist-packages/click/core.py", line 1393, in invoke
+return ctx.invoke(self.callback, **ctx.params)
+ File "/usr/lib/python3/dist-packages/click/core.py", line 752, in invoke
+return __callback(*args, **kwargs)
+ File "/usr/lib/python3/dist-packages/rows/cli.py", line 160, in cli
+requests_cache.install_cache(str(http_cache_path))
+AttributeError: module 'requests_cache' has no attribute 'install_cache'
--
#4 echo $?
FAIL: 2 of 4 tests failed
autopkgtest [19:08:28]: test smoke-test
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1002584: gnudatalanguage: small test_tic_toc tolerance
Source: gnudatalanguage Version: 1.0.1-3 Severity: normal Tags: patch Self-testing of this package, particularly TEST_TIC_TOC seems to run a bit slower on arm64. Making graphicsmagick unable to migrate to testing. The reason is simple, testsuite/test_tic_toc.pro defines tolerance on line 49 to be 0.01 (1%) while the result is ~0.015 . I think it would be better to increase it to 0.02 (2%) to let the test complete successfully. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) 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 /bin/dash
Bug#1001168: Info received (Bug#1001168: Info received ())
If I run in the sid chroot, but with the binaryed built from bullseye, it works. (sid_mips64el-dchroot)picca@eller:~/matplotlib-3.5.0/build/lib.linux-mips64-3.9$ rm toto.png (sid_mips64el-dchroot)picca@eller:~/matplotlib-3.5.0/build/lib.linux-mips64-3.9$ python3 test.py (sid_mips64el-dchroot)picca@eller:~/matplotlib-3.5.0/build/lib.linux-mips64-3.9$ ls matplotlib mpl_toolkits pylab.py test.py toto.png
Bug#1001168: Info received ()
Here no error during the build of numpy 1.19.5 = 10892 passed, 83 skipped, 108 deselected, 19 xfailed, 2 xpassed, 2 warnings in 1658.41s (0:27:38) = but 109 for numpy 1.21... = 14045 passed, 397 skipped, 1253 deselected, 20 xfailed, 2 xpassed, 2 warnings, 109 errors in 869.47s (0:14:29) =
Bug#1002560: [pkg-apparmor] Bug#1002560: /usr/sbin/aa-logprof: aa-logprof doesn't understand include if exists
On Fri, 24 Dec 2021, 23:02 Christian Boltz, wrote: > Support for "include if exists" was added to aa-logprof in version 3.0. > Unfortunately the patch is quite big, which makes backporting to the > 2.13 branch nearly impossible. > > I'm afraid you'll either need to upgrade to 3.x - or avoid using > "include if exists" as long as you use 2.13.x. > Cheers, thanks for the answer. Not 100% what I want but understand why it's like that. - Craig
Bug#1001168: Info received ()
I investigated a bit more, it seems that cover is wrong. In a bullseye chroot it works $ python3 ./test.py (bullseye_mips64el-dchroot)picca@eller:~/matplotlib-3.5.0/build/lib.linux-mips64-3.9$ ls matplotlib mpl_toolkits pylab.py test.py toto.png I found that the test failed between the 3.3.4-2 and 3.3.4-2+b1 rebuild This binNMU was about python3.10 support, but in the same time numpy has changed from python3-numpy (= 1:1.19.5-1), to python3-numpy (= 1:1.21.4-2), I think that there is a non negligeable possibility for this bug to be triggered by the new numpy.
Bug#1001849: Acknowledgement (bullseye-pu: package glewlwyd/2.5.2-2+deb11u1)
Hello Salvatore, Le 2021-12-24 à 14 h 36, Salvatore Bonaccorso a écrit : Any news on the CVE assignment? Did MITRE respond? Not yet, still waiting for the submission to be reviewed according to the mitre... /Nicolas
Bug#1001849: Acknowledgement (bullseye-pu: package glewlwyd/2.5.2-2+deb11u1)
Hi Nicolas, On Sat, Dec 18, 2021 at 10:05:20AM +0100, Salvatore Bonaccorso wrote: > Hi, > > On Sat, Dec 18, 2021 at 10:03:51AM +0100, Salvatore Bonaccorso wrote: > > Hi Nicolas, > > > > On Fri, Dec 17, 2021 at 08:25:38PM -0500, Nicolas Mora wrote: > > > See attached debdiff > > > > > diff -Nru glewlwyd-2.5.2/debian/changelog glewlwyd-2.5.2/debian/changelog > > > --- glewlwyd-2.5.2/debian/changelog 2021-09-22 08:42:59.0 > > > -0400 > > > +++ glewlwyd-2.5.2/debian/changelog 2021-12-17 07:51:46.0 > > > -0500 > > > @@ -1,3 +1,9 @@ > > > +glewlwyd (2.5.2-2+deb11u2) bullseye; urgency=medium > > > + > > > + * d/patches: Fix possible privilege escalation (Closes: #1001849) > > > > This should ot close the release.d.o filled bug, but the bug in the > > BTS associates with glewlwyd if one exists. Related question: is there > > a CVE and details on the issue? > > Answering the last question to myself: As you stated the CVE was > requested :) Any news on the CVE assignment? Did MITRE respond? Regards, Salvatore
Bug#1002583: O: pymongo
Package: wnpp Severity: normal Control: affects -1 src:pymongo Orphaning package.
Bug#983441: libxapp1: generates an obsolete conffile
Control: block -1 by 886389
Il 24/02/2021 09:20, Laurent Bonnaud ha scritto:
Package: libxapp1
Version: 2.0.6-2
Severity: normal
Dear Maintainer,
here is the problem:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
[...]
/etc/xdg/autostart/xapp-sn-watcher.desktop
a9fa3be7aaf46761adcdb856c63c125f obsolete
Simply installing libxapp1 on a system is sufficient to create this
problem (no upgrade scenario is necessary).
Hi, thanks for report, I saw this issue in 3 different cases where move
conffile from a package to another cause it to be marked as absolete as
reported also by other in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886389
2 time in xapp when happened in 2.0.6-2 for xapp-sn-watcher.desktop and
rehappened in 2.2.6-1 for another move (tested on clean Sid upgrade to
experimental)
I not found a solution or workaround for now
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1002582: RFS: gcc-sh-elf/2 [RC] -- GNU C compiler for embedded SuperH devices
Package: sponsorship-requests Severity: normal X-Debbugs-CC: pkg-electronics-de...@alioth-lists.debian.net Dear mentors and Electronics Team, I'm looking for a sponsor for my package "gcc-sh-elf": * Package name : gcc-sh-elf Version : 2 (this is a native package) * License : GPL-3+ * Vcs : https://salsa.debian.org/electronics-team/toolchains/gcc-sh-elf Section : devel It builds those binary packages: gcc-sh-elf - GNU C compiler for embedded SuperH devices libnewlib-sh-elf-dev - small ISO C standard library for embedded SuperH devices To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gcc-sh-elf/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gcc-sh-elf/gcc-sh-elf_2.dsc Changes since the last upload: gcc-sh-elf (2) unstable; urgency=medium . * Disable building libcc1, which is superfluous. (Closes: #1001273) * Make new source-only upload to enable testing migration. In addition, I marked gcc-sh-elf Multi-Arch: foreign and set the homepages for the respective binary packages instead of the source package since we build Newlib as well. There are no regressions in the GCC test suite; there seem to be 42 unique failures (on amd64 and arm64 at least) as determined by grep -E "^FAIL" ../buildlog.txt | cut -d ' ' -f 2 | uniq | wc - l and these are the same ones as for the first upload with GCC 11.2.0-12. The autopkgtests are numerous and still passing and I don't anticipate any issues with this building on all architectures as it has before. Thanks, John signature.asc Description: This is a digitally signed message part
Bug#1002581: software-properties-gtk: The "Cache Refresh" dialog hangs when the PackageKit refresh task finishes with failed status
Package: software-properties-gtk
Version: 0.96.20.2-2.1
Severity: important
Tags: patch
Dear Maintainer,
The current version of software-properties-gtk (0.96.20.2-2.1) hangs
when refreshing the package list cache if the PackageKit refresh task
finishes with failed status. For intance, if a cdrom source repository
is configured but not mounted, refreshing the cache will fail with the
following error output in the terminal:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.Error: pk-client-error-quark: E: The repository
'cdrom://[Debian GNU/Linux 11.2.0 _Bullseye_ - Official amd64 DVD Binary-1
20211218-11:13] bullseye Release' does not have a Release file.
W: Updating from such a repository can't be done securely, and is therefore
disabled by default.
W: See apt-secure(8) manpage for repository creation and user configuration
details.
E: cdrom://[Debian GNU/Linux 11.2.0 _Bullseye_ - Official amd64 DVD Binary-1
20211218-11:13] bullseye Release is not (yet) available (Please use apt-cdrom
to make this CD-ROM recognized by APT. apt-get update cannot be used to add new
CD-ROMs)
(319)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 88, in on_pktask_finish
dialog = Gtk.MessageDialog(self, 0, Gtk.MessageType.ERROR,
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in
new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 572, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in
new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 518, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in
new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
This is due to a bug in the exception-handling part of
DialogCacheOutdated.on_pktask_finish(): the call to
Gtk.MessageDialog() should specify self.parent as its first
argument instead of self.
As a result of this bug, the "Cache Refresh" dialog hangs and
cannot be closed properly. (Furthermore, forcefully closing
the hung window by using right-click then "Close" fails to kill
the software-properties-gtk process: it then becomes impossible
to start software-properties-gtk again until the session is restarted
or the process is manually killed...)
This issue was already reported and fixed upstream:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829401
https://git.launchpad.net/software-properties/commit/softwareproperties/gtk/DialogCacheOutdated.py?id=354bbd08bd3a0a99d357b5b54b27a2df68db46ed
Would it please be possible to backport this fix to the currently
shipped version of software-properties-gtk? I'm attaching a trivial
patch which should apply smoothly to 0.96.20.2-2.1 and fix this issue.
Thank you very much in advance!
Cheers,
SnipFoo.
-- System Information:
Debian Release: 11.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages software-properties-gtk depends on:
ii gir1.2-gtk-3.0 3.24.24-4
ii python3 3.9.2-3
ii python3-gi 3.38.0-2
ii python3-software-properties 0.96.20.2-2.1
ii software-properties-common 0.96.20.2-2.1
software-properties-gtk recommends no packages.
Versions of packages software-properties-gtk suggests:
ii gnome-software 3.38.1-1
-- no debconf information
diff -Naur a/softwareproperties/gtk/DialogCacheOutdated.py
b/softwareproperties/gtk/DialogCacheOutdated.py
--- a/softwareproperties/gtk/DialogCacheOutdated.py
+++ b/softwareproperties/gtk/DialogCacheOutdated.py
@@ -85,7 +85,7 @@
try:
results = self._pktask.generic_finish(result)
except Exception as e:
-dialog = Gtk.MessageDialog(self, 0, Gtk.MessageType.ERROR,
+dialog = Gtk.MessageDialog(self.parent, 0, Gtk.MessageType.ERROR,
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
dialog.format_secondary_text(str(e))
dialog.run()
Bug#1002580: ITP: rime-array -- Rime Input Method Engine schema data - array30
Package: wnpp Severity: wishlist * Package name: rime-array Version : 0.0~git20210824.d10f2f8-1 Upstream Author : Gong Chen * URL : https://github.com/rime/rime-array * License : GPL-3.0 and Array-Input-Method-Public-License Programming Lang: N/A Description : Rime Input Method Engine schema data - array30 RIME is the acronym of Rime Input Method Engine. . RIME is a lightweight, extensible input method engine supporting various input schemas including glyph-based input methods, romanization-based input methods as well as those for Chinese dialects. It has the ability to compose phrases and sentences intelligently and provide very accurate traditional Chinese output. RIME's cross-platform core library is written in C++, and can work consistently on different platforms with OS-specific wrappers. . This package provides the array30 schema data of RIME. This package will be part of the effort to migrate from https://tracker.debian.org/pkg/brise to https://github.com/rime/plum by splitting individual data packages and maintaining them individually. The new binary package rime-data-array30 will replace old librime-data-array30 provided by src:brise. I plan to maintain this package under Debian Input Method Team: https://salsa.debian.org/input-method-team/rime-array . Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1001081: sbcl: `sbcl --load quicklisp.lisp` fails with `internal error 222` since 2.1.11-1
A similar “internal error 222” occurs randomly on the Debian CI platform. See this log: https://ci.debian.net/data/autopkgtest/testing/amd64/c/cl-uax-15/17757334/log.gz The problem is also mentioned in this Reddit thread, and upstream has committed a possible fix (commit f66c6e355b23), but that needs to be confirmed: https://www.reddit.com/r/lisp/comments/rmbq0f/sbcl_2111_gives_internal_error_222_nil_argsnil/ -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#959022: cgroup-tools v2 already packaged for bookworm
I don't understand why tagging "bullseye-ignore" when there was already a version of cgroup-tools supporting cgroup2. This made package to remain stuck at v0.41 for next (now current) Debian Stable. Please, cgroup-tools needs to be backported to bullseye (or at least to bullseye-backports). By backporting a working version of cgroup-tools , this will make bullseye consistent with (defaulted) Control Group v2 for userspace tools. -- Narcis Garcia __ I'm using this dedicated address because personal addresses aren't masked enough at this tracker archive. Public archive administrator should fix this against automated addresses collectors.
Bug#1000739: Missing parts of upstream
Hi Julien, you were wrong in your fix: you wanted mdn-browser-compat-data/html/global_attributes.json which is provided by mdn-browser-compat-data module (not packaged). The new @mdn/browser-compat-data provides just one data.json. I think we should revert your change and you should patch your package to use @mdn/browser-compat-data/data.json#global_attribute instead of mdn-browser-compat-data/html/global_attributes.json Cheers, Yadd
Bug#1002579: libfltk1.3-dev: libfltk1.3-dev is not Multi-Arch:same
Package: libfltk1.3-dev Version: 1.3.5-3 Severity: normal X-Debbugs-Cc: none, Dima Kogan It would be nice if it was Multi-Arch:same. It would make cross-building easier. Is there any reason it isn't? I see that it ships /usr/bin/fltk-config, which would need to be moved to a different package, maybe. Do you want a patch? Thanks -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'testing'), (500, 'unstable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf-8, LC_CTYPE=en_US.utf-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf-8), LANGUAGE=en_US.utf-8 Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libfltk1.3-dev depends on: ii libfltk-cairo1.3 1.3.5-3 ii libfltk-forms1.3 1.3.5-3 ii libfltk-gl1.3 1.3.5-3 ii libfltk-images1.3 1.3.5-3 ii libfltk1.3 1.3.5-3 ii libx11-dev 2:1.7.2-2+b1 Versions of packages libfltk1.3-dev recommends: ii fluid 1.3.5-3 ii libgl-dev 1.3.4-2+b1 ii libglu1-mesa-dev [libglu-dev] 9.0.1-1 Versions of packages libfltk1.3-dev suggests: pn fltk1.3-doc ii libcairo2-dev 1.16.0-5 ii libjpeg-dev1:2.0.6-2 ii libjpeg62-turbo-dev [libjpeg-dev] 1:2.1.2-1 ii libpng-dev 1.6.37-3 ii libxext-dev2:1.3.4-1 ii libxft-dev 2.3.2-2 ii libxinerama-dev2:1.1.4-2 ii zlib1g-dev [libz-dev] 1:1.2.11.dfsg-2 -- no debconf information
Bug#1002308: lld-13: LLD is not found by a find_package cmake call
The call is right after a clang call which works: find_package(AMDDeviceLibs REQUIRED CONFIG) find_package(Clang REQUIRED CONFIG) find_package(LLD REQUIRED CONFIG) I have installed : liblld-13 liblld-13-dev lld-13 llvm-13 llvm-13-dev llvm-13-runtime llvm-13-tools llvm-13-linker-tools libclang-13-dev clang-13 If I pass to cmake the flag -DLLD_DIR=/usr/lib/llvm-13/lib/cmake/lld I can build the project, but shouldn't it work right off the bat?
Bug#1002578: nmu: 3depict_0.0.23-1+b1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hello, Version 2.5-2 of the mathgl package is now in unstable. This version bumped the SOVERSION of all shipped libraries, and that caused a changing in the names of the corresponding packages. The 3depict binary package depends on libmgl7.5.0, which does not exist anymore in unstable. The 3depict package must be rebuilt against the new version of libmgl-dev, such that it will depend on libmgl7.6.0. Compilation of 3depict against mathgl 2.5 works smoothly, without needing to change the source files. nmu 3depict_0.0.23-1+b1 . ANY . unstable . -m "Rebuild against mathgl to correct dependency" Thanks, Rafael Laboissière
Bug#1001849: marked as done (bullseye-pu: package glewlwyd/2.5.2-2+deb11u1)
Control: reopen -1 Control: tags -1 + pending On Fri, 2021-12-24 at 16:21 +, Debian Bug Tracking System wrote: > Your message dated Fri, 24 Dec 2021 16:17:08 + > with message-id > and subject line Bug#1001849: fixed in glewlwyd 2.5.2-2+deb11u2 > has caused the Debian Bug report #1001849, > regarding bullseye-pu: package glewlwyd/2.5.2-2+deb11u1 > to be marked as done. > As Salvatore said, please don't do that. Regards, Adam
Bug#1002577: ITP: guestfs-tools -- libguestfs-based tools that have been split out of the main repository
Package: wnpp Owner: Hilko Bengen Severity: wishlist * Package name: guestfs-tools Version : 1.46.1 Upstream Author : Richard WM Jones * URL or Web page : https://libguestfs.org/ * License : GPLv2+ Description : libguestfs-based tools that have been split out of the main repository
Bug#995598: Enable rtw89 -- Driver for Realtek 8852AE, an 802.11ax device
While the code is in the 5.16 and later kernels, it is not enabled by default. Take a look at the 5.16 package in experimental -- the driver isn't present. (I know, I was giddy to see the signed kernel and then disappointed when my WiFi still didn't work.)
Bug#1001849: glewlwyd 2.5.2-2+deb11u2 flagged for acceptance
package release.debian.org tags 1001849 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: glewlwyd Version: 2.5.2-2+deb11u2 Explanation: fix possible privilege escalation
Bug#1000645: symfony 4.4.19+dfsg-2+deb11u1 flagged for acceptance
package release.debian.org tags 1000645 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: symfony Version: 4.4.19+dfsg-2+deb11u1 Explanation: fix CVE injection issue [CVE-2021-41270]
Bug#1001411: dask.distributed 2021.01.0+ds.1-2.1+deb11u1 flagged for acceptance
package release.debian.org tags 1001411 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: dask.distributed Version: 2021.01.0+ds.1-2.1+deb11u1 Explanation: fix undesired listening of workers on public interfaces [CVE-2021-42343]; fix compatibility with Python 3.9
Bug#1000408: libmodbus 3.1.4-2+deb10u1 flagged for acceptance
package release.debian.org tags 1000408 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: libmodbus Version: 3.1.4-2+deb10u1 Explanation: fix out of bound read issues [CVE-2019-14462 CVE-2019-14463]
Bug#1002575: iwd: Doesn't create global config file or its directory (/etc/iwd/)
Hi Diederik, Quoting Diederik de Haas (2021-12-24 15:54:05) > I needed the "EnableNetworkConfiguration=true" setting, which IIUC > should be done in /etc/iwd/main.conf, but I noticed that that file and > directory didn't exist. I resolved it by using mkdir and creating the > file with vim (as root) and I'm assuming/hoping things like > permissions are set correctly. But I did wonder whether I was doing it > incorrectly (and I may have, but it's working). > > So unless there are (strong) downsides to it, it would be great if the > package installation would create the directory and optionally the > file (empty with comments f.e.). I agree that it would be helpful if the iwd package included a system-wide default config file, even if containing only commented out sample entries. I have looked through the source code, and I cannot locate any such config file that would be sensible to include with the Dbian package. I will create such file myself, as I worry about the potential burden of maintaining it (or worse: that the information getting out of sync): Better if upstream would create and maintain such default config file. Do you want to suggest it to upstream? Their preferred contact is this mailinglist: https://lists.01.org/postorius/lists/iwd.lists.01.org/ Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#998042: jbig2dec 0.16-1+deb10u1 flagged for acceptance
package release.debian.org tags 998042 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: jbig2dec Version: 0.16-1+deb10u1 Explanation: fix buffer overflow issue [CVE-2020-12268]
Bug#992546: detox 1.3.0-4+deb10u1 flagged for acceptance
package release.debian.org tags 992546 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: detox Version: 1.3.0-4+deb10u1 Explanation: fix processing of large files on ARM architectures
Bug#992613: icu 63.1-6+deb10u3 flagged for acceptance
package release.debian.org tags 992613 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: icu Version: 63.1-6+deb10u3 Explanation: fix "pkgdata" utility
Bug#987376: leptonlib 1.76.0-1+deb10u1 flagged for acceptance
package release.debian.org tags 987376 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: leptonlib Version: 1.76.0-1+deb10u1 Explanation: fix denial of service issue [CVE-2020-36277], buffer over-read issues [CVE-2020-36278 CVE-2020-36279 CVE-2020-36280 CVE-2020-36281]
Bug#1001149: gerbv 2.7.0-1+deb10u1 flagged for acceptance
package release.debian.org tags 1001149 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: gerbv Version: 2.7.0-1+deb10u1 Explanation: fix code execution issue [CVE-2021-40391]
Bug#1000486: btrbk 0.27.1-1+deb10u2 flagged for acceptance
package release.debian.org tags 1000486 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: btrbk Version: 0.27.1-1+deb10u2 Explanation: fix regression in the update for CVE-2021-38173
Bug#996024: ruby-httpclient 2.8.3-3+deb10u1 flagged for acceptance
package release.debian.org tags 996024 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: ruby-httpclient Version: 2.8.3-3+deb10u1 Explanation: use system certificate store
Bug#996023: openscad 2019.01~RC2-2+deb10u1 flagged for acceptance
package release.debian.org tags 996023 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: openscad Version: 2019.01~RC2-2+deb10u1 Explanation: fix buffer overflows in STL parser [CVE-2020-28599 CVE-2020-28600]
Bug#995748: vim 8.1.0875-5+deb10u1 flagged for acceptance
package release.debian.org tags 995748 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: vim Version: 8.1.0875-5+deb10u1 Explanation: fix ability to execute code while in restricted mode [CVE-2019-20807], buffer overflow issues [CVE-2021-3770 CVE-2021-3778 CVE-2021-3875], use after free issue [CVE-2021-3796]
Bug#985063: lxcfs 3.0.3-2+deb10u1 flagged for acceptance
package release.debian.org tags 985063 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: lxcfs Version: 3.0.3-2+deb10u1 Explanation: fix misreporting of swap usage
Bug#1001556: mailman 2.1.29-1+deb10u4 flagged for acceptance
package release.debian.org tags 1001556 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: mailman Version: 2.1.29-1+deb10u4 Explanation: fix potential CSRF attack against a list admin from a list member or moderator [CVE-2021-44227]
Bug#1001280: publicsuffix 20211109.1735-0+deb10u1 flagged for acceptance
package release.debian.org tags 1001280 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: publicsuffix Version: 20211109.1735-0+deb10u1 Explanation: update included data
Bug#1000608: ros-ros-comm 1.14.3+ds1-5+deb10u3 flagged for acceptance
package release.debian.org tags 1000608 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: ros-ros-comm Version: 1.14.3+ds1-5+deb10u3 Explanation: fix denial of service issue [CVE-2021-37146]
Bug#1002576: dch doesn't read email settings from config file
Package: devscripts Version: 2.21.7 Running dch will give me: dch warning: neither DEBEMAIL nor EMAIL environment variable is set dch warning: building email address from username and mailname dch: Did you see those 2 warnings? Press RETURN to continue... The manual says I can put it in the ~/.devscripts file, but that doesn't have any effect. strace says it's being read. Putting it in an environment variable does make the warning go away. Kurt
Bug#976505: gkl: FTBFS on arm64: deflate.c:995:36: error: ‘x86_cpu_has_sse42’ undeclared (first use in this function)
Control: tags -1 wontfix Well, I guess it is fair to tag the bug with wontfix. The architecture of libgkl-jni is correctly indicated in the debian/control file, I think it is enough. Also, with current version (0.8.9+dfsg), the original error message that triggered this bug report is not showing up anymore on arm64, but another one occurs later on during the build, also linked to some missing header... Best, -- Pierre
Bug#1002575: iwd: Doesn't create global config file or its directory (/etc/iwd/)
Package: iwd Version: 1.20-3 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I needed the "EnableNetworkConfiguration=true" setting, which IIUC should be done in /etc/iwd/main.conf, but I noticed that that file and directory didn't exist. I resolved it by using mkdir and creating the file with vim (as root) and I'm assuming/hoping things like permissions are set correctly. But I did wonder whether I was doing it incorrectly (and I may have, but it's working). So unless there are (strong) downsides to it, it would be great if the package installation would create the directory and optionally the file (empty with comments f.e.). Cheers, Diederik - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 5.15.0-2-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages iwd depends on: ii init-system-helpers 1.61 ii libc62.33-1 ii libell0 0.46-1 ii libreadline8 8.1-2 Versions of packages iwd recommends: ii dbus [dbus-system-bus] 1.12.20-3 ii wireless-regdb 2021.08.28-1 iwd suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCYcXfBAAKCRDXblvOeH7b bi8dAP0c4VnVvcuTelV5oyfKFLCzm60t3ZGCPL82RMqv1yMjnAD+O+X7Fma4VNtn iOPjV9KMvPnKrA7AezComjfGrJ3kgQ4= =gAgn -END PGP SIGNATURE-
Bug#1000200: reportbug-gtk: cannot close reportbug (on fluxbox)
CC'ing the python3.9 maintainer. On 22.12.2021 00.39, Nis Martensen wrote: > Hello GTK/Gnome experts, > > Would you be able to help with #1000200? Reportbug's GTK UI does not > close properly any more. It works fine in bullseye, and there was no > change in reportbug that could have caused this change in behaviour. > >> Michael Hatzold hat am 19.11.2021 geschrieben: >>> When using reportbug-gtk I now cannot close it (the window) anymore, not >>> even >>> after sending the email. I can minimize it, but not close. I have to open >>> a VT >>> and pkill or ctrl-C it (when opened in a VT) >>> >>> It used to work, and klicking the "x" in the title bar should close it. Update: The bug was introduced with the upload of python3.9 3.9.8-1 to unstable on 7 November. Downgrading python3.9 to version 3.9.7-4 fixes the problem. Next tasks: Identify which change between python 3.9.7 and 3.9.8 is responsible, and find out which package needs to change to fix the problem.
Bug#998767: the debhelper works
The debhelper works, I'm getting ready to use it in my typedload package, to install a -doc package as well. Some lintian warnings are generated about the over abundance of sitemap files. Anyway my bug was more because I'd like the generated (and then uploaded) website to not link externally to begin with, but be self contained. That's an upstream issue. But I guess as a workaround I can upload the content of the -doc package instead, to make sure that nothing is loaded from other domains. -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno." -- Galileo Galilei http://ltworf.github.io/ltworf/
Bug#1002496: perl6-readline: Strange files under /usr/lib/perl6/vendor/dist?
Hi On Thursday, 23 December 2021 10:19:50 CET Chris Lamb wrote: > The latest version of perl6-readline seems to ship a number of > interesting-looking files under /usr/lib/perl6/vendor, such as: > > /usr/lib/perl6/vendor/dist/A8475E6287F45455F9F68569C07ADC25AA5BEFDF > > Is this some kind of .pyc equivalent for Perl 6? Either way, I'd love > to know more as these files appear to be unreproducible. Yes, theses are Raku modules pre-compiled at build time. A more detailed explanation is provided on Debian wiki: https://wiki.debian.org/Perl6PreCompProposal I don't really know why the pre-compilation is not reproducible. As a matter of fact, neither rakudo, nqp or moarvm are reproducible. I've never found the time or energy to find why. All the best Dod
Bug#785356: Wählen Sie den gewünschten Betrag für Ihr Guthaben: 2.000 € - 1.000.000 €
Wählen Sie den gewünschten Betrag für Ihr Guthaben: 2.000 € - 1.000.000 € Wir bieten kurz-, mittel- und langfristige Kredite an. Unsere Überweisungen werden von einer Bank zur Absicherung der Transaktion mit einem Zinssatz von 2% pro Jahr bereitgestellt. Bitte kontaktieren Sie mich direkt per E-Mail: Meine E-Mail-Adresse: smajslova.jarm...@hotmail.com
Bug#892058: Your Debian key is expiring
On Thursday, 16 December 2021 04:59:12 CET you wrote: > If you like this service, please leave a favorable comment here [2]. Thanks for the heads-up. I would probably have forgotten to renew my key without this reminder. All the best
Bug#1002574: System not supported with v. 3.2
Package: openrazer-driver-dkms Version: 3.2.0+dfsg-1 Driver stop working after upgrade from 3.1 to 3.2 with Razer Basilisk v2. ** Error: kernel: razermouse: system not supported, no HID or USB support Tested with kernel 5.10 and 5.15.5. Dkms tree ok: ** dkms status: openrazer-driver/3.2.0, 5.10.0-8-amd64, x86_64: installed openrazer-driver/3.2.0, 5.15.0-2-amd64, x86_64: installed Regards Edi
Bug#994575: dipy: autopkgtest idea
On Fri, 17 Dec 2021 16:34:02 +0100 Andreas Tille wrote: > Am Thu, Dec 16, 2021 at 09:10:45PM +0100 schrieb Andreas Tille: > > Hi Étienne, > > > > Am Fri, Sep 17, 2021 at 11:11:03PM +0200 schrieb Étienne Mollier: > > > While working on #983840, I needed to do some testing of the > > > package, and notice examples in doc/examples/. Maybe they could > > > be a source of inspiration for building an autopkgtest test > > > suite? > > > > I think the idea itself is good but the realisation has some flaws. > > I've commited some code implementing the idea to Git but it seems we > > need to exclude lots of those examples as you can see for instance here > > in the Salsa CI > > > >https://salsa.debian.org/med-team/dipy/-/jobs/2285615 > > > > May be running the build-time nosetest is the easier approach to an > > autopkgtest. > > Thanks for porting to pytest. I've added the pytest test to autopkgtest > but all tests are failing: > > https://salsa.debian.org/med-team/dipy/-/pipelines/328590 > > Any idea what might be wrong here? I ran it locally, for me it chokes with: | autopkgtest [18:58:22]: test command1: xvfb-run --auto-servernum --server-num=20 -s "-screen 0 1024x768x24 -ac +extension GLX +render -noreset" sh debian/tests/run-unit-test | autopkgtest [18:58:22]: test command1: [--- | Skip quick_start.py | Run brain_extraction_dwi.py | 100%|██| 589/589 [00:52<00:00, 11.30 MB/s] | Skip reconst_csa_parallel.py | Skip reconst_csa.py | Skip reconst_csd_parallel.py | Skip reconst_csd.py | Run reconst_forecast.py | /usr/lib/python3/dist-packages/dipy/viz/__init__.py:31: UserWarning: You do not have FURY installed. Some visualization functions might not work for you. For installation instructions, please visit: https://fury.gl/ | warnings.warn( | Traceback (most recent call last): | File "/tmp/autopkgtest.QurZey/autopkgtest_tmp/examples/reconst_forecast.py", line 16, in | from dipy.viz import actor, window | ImportError: cannot import name 'actor' from 'dipy.viz' (/usr/lib/python3/dist-packages/dipy/viz/__init__.py) On checking, it stems from the fact that fury (python module) that dipy needs is not in (test-)depends, and neither is it in the archive. Probably other tests also are missing some or the other module. I also see a couple of circular imports that we need to fix. This is my understanding ^^ so maybe packaging fury will help. Regards, Nilesh signature.asc Description: PGP signature
Bug#1002573: general: fstrim, 2 errors
Package: general Severity: grave Justification: renders package unusable 1st error: fstrim --verbose --all reports nothing 2nd error: fstrim --verbose / gives a wrong error message For both cases, see attachment 1.png, system l5 This happens on Debian 11.2 Bullseye on an Intel hardware The root file system is a RAID1 software array, but on a second Intel hardware with only one SSD, same Debian version, the behavior of fstrim is the same On a Raspberry Pi with Debian 10 Buster, everything works fine (see attachment 2.png, system b4) Notice on both screenshots: the fstrim versions are the same
Bug#988593: foot: A new version of foot is available (1.10.3)
On Sun, 16 May 2021 15:46:55 +0200 Nicolas Évrard wrote: > Package: foot > Version: 1.6.4-1 > Severity: wishlist The current latest version is 1.10.3 and it would be great if made available: https://codeberg.org/dnkl/foot/releases/tag/1.10.3 Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1002546: RFS: prometheus-cpp/1.0.0-4 [ITP] -- Prometheus Client Library for Modern C++
Done. Reuploaded 1.0.0-1 version with all changes incorporated. пт, 24 дек. 2021 г. в 13:59, Bastian Germann : > > On Fri, 24 Dec 2021 01:23:15 +0300 Max Dmitrichenko wrote: > > Changes for the initial release: > > > > prometheus-cpp (1.0.0-4) unstable; urgency=medium > > . > >* Provide static libraries with -dev package. > > > > prometheus-cpp (1.0.0-1) unstable; urgency=medium > > . > >* Initial release. Closes: #917817 > > Please keep only the 1.0.0-1 entry as long as this is not sponsored. > Report your changes on this issue on new uploads instead. -- With best regards Maksim Dmitrichenko
Bug#1002522: chkrootkit: autopkgtest failure everywhere except amd64
control: fixed -1 0.55-4 thanks On Thu, 23 Dec 2021 21:36:11 +0100 Paul Gevers wrote: > So let's assume the results will be OK, then you can just close this bug > with fixed version 0.55-4 and ignore it further. Thanks, it seems 0.55-4 is indeed testing fine everywhere, according to the latest https://tracker.debian.org/pkg/chkrootkit R
Bug#1001320: needrestart misdetects socket activated ssh and restarts service instead of socket
Hallo Marc Haber, 24.12.21 12:22 Marc Haber: > So we agree here that it's mainly a documentation issue for ssh, so that > it should be recommended to actually mask ssh.service if socket > activation is used, right? For the bug on openssh: yes. Documentation could look like: If you decide to use socket activation consider masking ssh.service to avoid accidentally doing the wrong thing with "service ssh restart" or equivalent. For needrestart we have the problem of the heuristics, that were designed for non-systemd-systems, also being used on a systemd-system. Grüße Timo signature.asc Description: This is a digitally signed message part.
Bug#998165: debian-policy: document and allow Description in the source paragraph
On Tue, 2021-12-21 at 17:53:31 -0700, Sean Whitton wrote: > On Sun 12 Dec 2021 at 06:47PM +01, Mattia Rizzolo wrote: > > > |--- a/policy/ch-controlfields.rst > > |+++ b/policy/ch-controlfields.rst > > |@@ -652,9 +654,14 @@ orderings. [#]_ > > | ~~~ > > | > > | In a source or binary control file, the ``Description`` field contains a > > |-description of the binary package, consisting of two parts, the synopsis > > |-or the short description, and the long description. It is a multiline > > |-field with the following format: > > |+description of the package, consisting of two parts, the synopsis or the > > short > > |+description, and the long description. > > |+ > > |+When used in a source control file in the general paragraph (i.e., the > > first > > |+one, for the source package), the text in this field is relevant for all > > binary > > |+packages built by the given source package. > > Is there really no name for the first paragraph other than "general > paragraph"? That's how the dpkg documentation (man and perl modules POD) refers to it (or first block of information, which is even worse), but I agree it's rather suboptimal, and I'd like to get a better name for it. See below. > Maybe "the source package's stanza"? Something like this might work, which is probably what we have been calling it for some time now, but that ties up with something that has been bothering me for some time now, and that is that I've found our naming of the various stanzas and the various control filenames rather confusingly similar, which for dpkg I'd really like to clear up (and have few tentative commits already), as that's even affecting its perl API currently. :/ For example we have «Debian source control file» or «Debian source packages' control file» for .dsc, then we have «Source package control file» or in dpkg «Debian source packages' master control file» for debian/control. Which are almost the same. I've been considering naming debian/control something like «Debian template source control file», as that is used to generate both the source and binary control files. But I think I'll open a new bug to cover and discuss that. > Also, how about "the text in this field describes all binary packages > which do not have their own Description: fields" ? I'm not sure whether you are (or the text would then) imply this; but the Description in the source stanza does not get inherited by the binary stanzas when generating the binary package control file, one needs to add references to it via substvars. Thanks, Guillem
Bug#1002572: git-send-email: Adds spurious space to address name containing a dot
Package: git-email Version: 1:2.34.1-1 Severity: minor Tags: upstream X-Debbugs-Cc: alx.manpa...@gmail.com $ git format-patch -o patches/send/ -1 HEAD --to='Foo V. Bar ' $ git send-email patches/send/0013-Static-optimize-index-iteration.patch patches/send/0001-foo.patch To whom should the emails be sent (if anyone)? Message-ID to be used as In-Reply-To for the first email (if any)? (mbox) Adding cc: Alejandro Colomar from line 'From: Alejandro Colomar ' (mbox) Adding to: "Foo V . Bar" from line 'To: Foo V. Bar ' I know I should theoretically use --to='"Foo V. Bar" ', but it is a bit inconvenient, since I just copy the address from Thunderbird, which doesn't add the double quotes. Why is git adding that spurious space before the dot? Can it be fixed without breaking other stuff? Thanks, Alex -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages git-email depends on: ii git 1:2.34.1-1 Versions of packages git-email recommends: ii libauthen-sasl-perl2.1600-1.1 ii libemail-valid-perl1.202-1 ii libio-socket-ssl-perl 2.072-1 ii libmailtools-perl 2.21-1 ii libnet-smtp-ssl-perl 1.04-1 ii perl 5.32.1-6 Versions of packages git-email suggests: pn git-doc -- no debconf information
Bug#983869: #983869: lsblk does not report mount point for all members of btrfs filesystems
Control: tags -1 + moreinfo Hi, thanks for the report. Given lsblk mostly just prints out information provided by the kernel, I would imagine that information is incomplete. Please strace and/or gdb your way through lsblk and see what you can find. (Or provide exact info on how to setup a reproduction system.) If you agree this is a kernel problem, please reassign to the kernel. BR, Chris
Bug#998428: dbus-session-bus-common: Deprecated option in /usr/share/dbus-1/session.conf
On Thu, 4 Nov 2021 09:42:57 + Simon McVittie wrote: > Control: reassign -1 dbus-session-bus-common,dbus-broker > > On Wed, 03 Nov 2021 at 23:56:07 -0300, Nelson A. de Oliveira wrote: > > While starting the D-Bus User Message Bus it's possible to see: > > > > = > > dbus-broker-launch[5405]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored > > dbus-broker-launch[5405]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored > > = > > dbus-session-bus-common is the configuration of the well-known session > bus as provided by dbus, the reference implementation of D-Bus. > > You appear to be using dbus-broker, a reimplementation of D-Bus, which > borrows the configuration of the well-known buses from dbus. > > If dbus-broker considers something to be deprecated, of course that's up > to the maintainers of dbus-broker; but dbus takes backwards compatibility > seriously, and so does not configure the session bus to forbid legacy > eavesdropping (even though legacy eavesdropping was a bad design and > has been superseded by Monitoring). > > smcv > > While warnings like this are a bit annoying to have in the default installation, on balance I think having a common config between the implementations will keep us "honest" (on the dbus-broker side) w.r.t. interoperability, so I'm inclined to leave it as-is. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#1002571: fcitx5: Fcitx5 Was unable to apply the kde plasma theme
Package: fcitx5
Version: 5.0.11-1
Severity: minor
Dear Maintainer,
After an upgrade of testing, the fcitx5 cannot apply the kde plasma theme
automatically. However, after closing the app and open it again, the theme will
be applied.
-- Package-specific info:
--- Fcitx5 Diagnose output ---
# System Info:
1. `uname -a`:
Linux familythree 5.15.0-2-amd64 #1 SMP Debian 5.15.5-1 (2021-11-26)
x86_64 GNU/Linux
2. `lsb_release -a`:
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux bookworm/sid
Release:testing
Codename: bookworm
3. `lsb_release -d`:
Description:Debian GNU/Linux bookworm/sid
4. `/etc/lsb-release`:
`/etc/lsb-release` not found.
5. `/etc/os-release`:
PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;
6. Desktop Environment:
Desktop environment is `kde`.
7. Bash Version:
BASH_VERSION='5.1.12(1)-release'
# Environment:
1. DISPLAY:
DISPLAY=':0'
WAYLAND_DISPLAY=''
2. Keyboard Layout:
1. `setxkbmap`:
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat{ include "complete" };
xkb_symbols { include
"pc+us+inet(evdev)+compose(ralt)+terminate(ctrl_alt_bksp)" };
xkb_geometry { include "pc(pc86)" };
};
2. `xprop`:
_XKB_RULES_NAMES(STRING) = "evdev", "pc86", "us", "",
"compose:ralt,terminate:ctrl_alt_bksp"
3. Locale:
1. All locale:
C
C.UTF-8
POSIX
zh_CN.utf8
2. Current locale:
LANG=zh_CN.UTF-8
LANGUAGE=zh_CN:zh
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=C
4. Directories:
1. Home:
/home/ybx333
2. `${XDG_CONFIG_HOME}`:
Environment variable `XDG_CONFIG_HOME` is not set.
Current value of `XDG_CONFIG_HOME` is `~/.config`
(`/home/ybx333/.config`).
3. Fcitx5 Settings Directory:
Current fcitx5 settings directory is `~/.config/fcitx5`
(`/home/ybx333/.config/fcitx5`).
5. Current user:
The script is run as ybx333 (1000).
# Fcitx State:
1. executable:
Found fcitx5 at `/usr/bin/fcitx5`.
2. version:
Fcitx version: `5.0.11`
3. process:
Found 2 fcitx5 processes:
4667 fcitx5
11889 fcitx5
4. `fcitx5-remote`:
`fcitx5-remote` works properly.
5. DBus interface:
Using `dbus-send` to check dbus.
Owner of DBus name `org.fcitx.Fcitx5` is `:1.8`.
PID of DBus name `org.fcitx.Fcitx5` owner is `4667`.
Debug information from dbus:
Group [x11::0] has 6 InputContext(s)
IC [f32d8b5dd0194fab956f82b6ecb870b1] program:reportbug frontend:dbus
cap:600012 focus:1
IC [86e9c1af1dd844009309d49e50305593] program:reportbug frontend:dbus
cap:600052 focus:0
IC [963001e1f8ab4c30a68ee82426c83e7c] program:reportbug frontend:dbus
cap:600052 focus:0
IC [853b40c222dc40b0b7a2a7748845bc0d] program:reportbug frontend:dbus
cap:600052 focus:0
IC [be1260dde5f349209631f90503861108] program:plasmashell
frontend:dbus cap:6000800072 focus:0
IC [b09d3909833b40cea08e330942c01e86] program:plasmashell
frontend:dbus cap:6000800072 focus:0
Input Context without group
# Fcitx Configure UI:
1. Config Tool Wrapper:
Found fcitx5-configtool at `/usr/bin/fcitx5-configtool`.
2. Config GUI for qt:
Found `fcitx5-config-qt` at `/usr/bin/fcitx5-config-qt`.
3. Config GUI for kde:
Found fcitx5 kcm module.
kcm_fcitx5 - Configure Input Method
# Frontends setup:
## Xim:
1. `${XMODIFIERS}`:
Environment variable XMODIFIERS is set to "@im=fcitx" correctly.
Xim Server Name from Environment variable is fcitx.
2. XIM_SERVERS on root window:
Xim server name is the same with that set in the environment variable.
3. XIM encoding:
**Your LC_CTYPE is set to C whose encoding is not UTF-8. You may have
trouble committing strings using XIM.**
## Qt:
1. qt4 - `${QT4_IM_MODULE}`:
Environment variable QT_IM_MODULE is set to "fcitx" correctly.
2. qt5 - `${QT_IM_MODULE}`:
Environment variable QT_IM_MODULE is set to "fcitx" correctly.
3. Qt IM module files:
Found fcitx5 qt5 module:
Bug#998063: Bug #998063: debian-policy: New virtual package: {default-,}dbus-system-bus
On Fri, 2021-12-24 at 10:05 +, Simon McVittie wrote:
> Sending this to -devel since Sean pointed out that new general-
> purpose
> virtual package names are meant to go there, not just to a Policy
> bug.
>
> On Fri, 29 Oct 2021 at 11:12:07 +0100, Simon McVittie wrote:
> > We now have two implementations of the D-Bus well-known system bus
> > available in Debian:
> >
> > * dbus, the portable reference implementation
> > * dbus-broker, a Linux-specific reimplementation
> >
> > so it seems like a good time to introduce {default-,}dbus-system-
> > bus
> > virtual packages, mirroring {default-,}dbus-session-bus.
> >
> > At the moment, dbus is the default for all architectures. It is
> > possible
> > that dbus-broker might take over as the default on Linux
> > architectures
> > in some future release (but it is explicitly not portable, so dbus
> > will
> > probably always be the default on kFreeBSD and Hurd, similar to how
> > we
> > choose dbus-user-session vs. dbus-launch).
> >
> > Packages depending on "dbus" can currently count on having most
> > aspects of
> > the reference implementation available (except for the session bus,
> > which
> > requires either dbus-user-session or dbus-launch), but I would
> > prefer to
> > move towards packages explicitly declaring a dependency on one or
> > more of:
> >
> > * default-dbus-system-bus | dbus-system-bus:
> > the well-known system bus, as required by e.g. Avahi, polkit,
> > udisks2
> >
> > * dbus-daemon: ability to run the dbus-daemon(1) and dbus-run-
> > session(1)
> > executables, or rely on having the D-Bus machine ID
> > /var/lib/dbus/machine-id
> > (dbus-session-bus and dbus-system-bus both imply some sort of
> > machine
> > ID, but it might be systemd's /etc/machine-id)
> >
> > * dbus-bin: ability to run assorted CLI tools such as dbus-send(1)
> > and
> > dbus-monitor(1)
>
> A patch against Policy can be found on
> https://bugs.debian.org/998063,
> but the important content is:
>
> - name: dbus-system-bus
> description: provides the D-Bus well-known system bus as a system
> service, including service activation
> - name: default-dbus-system-bus
> description: Debian's preferred implementation of dbus-system-bus,
> possibly architecture-specific
>
> This split is already implemented in bookworm, and a few packages
> already
> depend on the new virtual package names.
>
> dbus in bullseye had a Provides: for default-dbus-system-bus,
> dbus-system-bus, dbus-daemon and dbus-bin in preparation for the
> split,
> so this dependency change can safely be backported from bookworm to
> bullseye-backports without changes (but will need to be reverted in
> the
> rare case of a backport from bookworm to buster-backports-sloppy).
>
> On the Policy bug, Adam Borowski queried whether it would be better
> to
> repurpose the dbus package name as the virtual package and use a new
> package name for the reference implementation, similar to the way the
> sysvinit package name was repurposed to mean "an init system" during
> the
> transition to systemd, with the real SysV init renamed to sysvinit-
> core. I
> think this would not have been correct, because packages that depend
> on
> dbus have historically been able to rely on the combined
> functionality
> of what we're now calling dbus-system-bus, dbus-daemon and dbus-bin,
> and should continue to be able to do so.
>
> smcv
>
With my dbus-broker maintainer hat on, I fully agree with your proposal
and reasoning w.r.t. package names. Thank you very much for your work!
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
Bug#1002570: replace which by command -v in wrapper script
Package: thunderbird
Version: 1:91.4.1-1
Severity: minor
Tags: patch
X-Debbugs-Cc: jspri...@debian.org
Hi Carsten,
$ thunderbird
/usr/bin/which: this version of `which' is deprecated; use `command -v' in
scripts instead.
Can you please apply the attached patch to fix this?
Thanks!
Jochen
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages thunderbird depends on:
ii debianutils 5.5-1
ii fontconfig 2.13.1-4.2
ii libatk1.0-0 2.36.0-3
ii libbotan-2-182.18.2+dfsg-1
ii libbz2-1.0 1.0.8-5
ii libc62.33-1
ii libcairo-gobject21.16.0-5
ii libcairo21.16.0-5
ii libdbus-1-3 1.12.20-3
ii libdbus-glib-1-2 0.112-2
ii libevent-2.1-7 2.1.12-stable-1
ii libffi8 3.4.2-3
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.11.0+dfsg-1
ii libgcc-s111.2.0-13
ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2
ii libglib2.0-0 2.70.2-1
ii libgtk-3-0 3.24.30-4
ii libjson-c5 0.15-2
ii libnspr4 2:4.32-3
ii libnss3 2:3.73.1-1
ii libpango-1.0-0 1.48.10+ds1-1
ii libstdc++6 11.2.0-13
ii libvpx7 1.11.0-2
ii libx11-6 2:1.7.2-2+b1
ii libx11-xcb1 2:1.7.2-2+b1
ii libxcb-shm0 1.14-3
ii libxcb1 1.14-3
ii libxext6 2:1.3.4-1
ii libxrender1 1:0.9.10-1
ii psmisc 23.4-2
ii x11-utils7.7+5
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages thunderbird recommends:
ii hunspell-en-us [hunspell-dictionary] 1:2020.12.07-1
Versions of packages thunderbird suggests:
ii apparmor 3.0.3-6
ii fonts-lyx 2.3.6-1
ii libgssapi-krb5-2 1.18.3-7
-- no debconf information
>From 8e004cce32987ea275677b22cfe529623fde1a39 Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof
Date: Fri, 24 Dec 2021 13:11:51 +0100
Subject: [PATCH] Use POSIX command -v in wrapper
which is deprecated.
---
debian/thunderbird-wrapper.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/thunderbird-wrapper.sh b/debian/thunderbird-wrapper.sh
index 13eeec1f9dc..b3f7c2e7b73 100755
--- a/debian/thunderbird-wrapper.sh
+++ b/debian/thunderbird-wrapper.sh
@@ -32,7 +32,7 @@ fi
# some global variables
MOZ_APP_NAME=thunderbird
-MOZ_APP_LAUNCHER=$(which "$0")
+MOZ_APP_LAUNCHER=$(command -v "$0")
MOZ_LIBDIR=/usr/lib/${MOZ_APP_NAME}
ID_PROFILE_FOLDER=${HOME}/.icedove
TB_PROFILE_FOLDER=${HOME}/.thunderbird
--
2.34.1
Bug#1002568: ogre-1.12: FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory
Control: severity -1 important Control: retitle -1 ogre-1.12: FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory Control: found -1 1.12.10+dfsg2-2~exp3 On Fri, 24 Dec 2021 at 11:40:57 +0100, Bastian Germann wrote: > ogre-1.12 does not build on sid/mipsel: > https://buildd.debian.org/status/fetch.php?pkg=ogre-1.12=mipsel=1.12.10%2Bdfsg2-1.2=1640306818=0 ogre-1.12 has never built successfully on mipsel, so I don't think this is RC unless a maintainer or the Release Team says it is. FTBFS on a single architecture is generally only RC if it's a regression, and not if that architecture has never been built successfully. This looks like the root cause, which wil not be easy to fix: > virtual memory exhausted: Cannot allocate memory It might be possible to apply some tricks to make the build take less memory. I see Olek Wojnar has made a couple of attempts at this in experimental, but unfortunately without success so far. webkit2gtk is an example of another package that hits memory limits during build. It currently uses LDFLAGS += -Wl,--no-keep-memory on 32-bit architectures (a time/space trade-off), and $(CFLAGS:-g=-g1) to reduce the size and coverage of its detached debug symbols. smcv
Bug#1002560: [pkg-apparmor] Bug#1002560: /usr/sbin/aa-logprof: aa-logprof doesn't understand include if exists
Hello, Am Freitag, 24. Dezember 2021, 03:41:57 CET schrieb Craig Small: > Package: apparmor-utils > Version: 2.13.6-10 > aa-logprof doesn't understand any lines that have include if exists. Support for "include if exists" was added to aa-logprof in version 3.0. Unfortunately the patch is quite big, which makes backporting to the 2.13 branch nearly impossible. I'm afraid you'll either need to upgrade to 3.x - or avoid using "include if exists" as long as you use 2.13.x. Regards, Christian Boltz -- > We could call it openSUSE 11.11.11 ;-) I'd prefer we use the US date format: 11.11.11 ;-) [> Freek de Kruijf and Greg Freemyer in opensuse-project] signature.asc Description: This is a digitally signed message part.
Bug#1002551: sqlite3-tools: missing Breaks+Replaces: sqlite3 (<< 3.37.0)
Control: tags -1 +confirmed +pending On Fri, Dec 24, 2021 at 1:09 AM Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'sid' to 'experimental'. [...] > The existing B+R: 'sqlite3 (<< 3.17.0)' have the wrong version number. Indeed, a bad typo went in finally. Thanks for catching that. Cheers, Laszlo/GCS
Bug#1001320: needrestart misdetects socket activated ssh and restarts service instead of socket
So we agree here that it's mainly a documentation issue for ssh, so that it should be recommended to actually mask ssh.service if socket activation is used, right? Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1002569: rsplib: FTBFS on mipsel
Source: rsplib Severity: serious Version: 3.3.3-1 rsplib fails to build on sid/mipsel: https://buildd.debian.org/status/fetch.php?pkg=rsplib=mipsel=3.3.3-1=1640318034=0 ... [ 55%] Linking CXX executable cspmonitor cd /<>/obj-mipsel-linux-gnu/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/cspmonitor.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/cspmonitor.dir/cspmonitor_autogen/mocs_compilation.cpp.o CMakeFiles/cspmonitor.dir/cspmonitor.c.o -o cspmonitor -Wl,-rpath,/<>/obj-mipsel-linux-gnu/src: librspcsp.so.3.3.3 libtdbreakdetector.so.3.3.3 -lsctp -lpthread librspdispatcher.so.3.3.3 libtdnetutilities.so.3.3.3 libtdstringutilities.so.3.3.3 libtdrandomizer.so.3.3.3 libtdstorage.so.3.3.3 libtdloglevel.so.3.3.3 libtdthreadsafety.so.3.3.3 libtdtimeutilities.so.3.3.3 -lm -lsctp -lpthread /usr/bin/ld: libtdbreakdetector.so.3.3.3: undefined reference to `__atomic_store_8' /usr/bin/ld: libtdbreakdetector.so.3.3.3: undefined reference to `__atomic_load_8' collect2: error: ld returned 1 exit status make[3]: *** [src/CMakeFiles/cspmonitor.dir/build.make:128: src/cspmonitor] Error 1 make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:1525: src/CMakeFiles/cspmonitor.dir/all] Error 2 ...
Bug#1001168: full python backtrace and print locals
the full python backtrace
#8
#14 Frame 0x120debd80, for file
/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/lines.py,
line 2888, in draw (self=,
figure=<...>, _transform=None, _transformSet=False, _visible=True,
_animated=False, _alpha=None, clipbox=None, _clippath=None, _clipon=True,
_label='', _picker=None, _rasterized=False, _agg_filter=None, _mouseover=False,
_callbacks=, callbacks={}, _cid_gen=,
_func_cid_map={}, _pickled_cids=set()) at remote 0xfff7a3be20>,
_remove_method=None, _url=None, _gid=None, _snap=None, _sketch=None,
_path_effects=[], _sticky_edges=<_XYPair at remote 0xfff51bacc0>,
_in_layout=True, _suptitle=None, _supxlabel=None, _supylabel=None,
_align_label_groups={'x': , 'y':
}, _g...(truncated)
#20 Frame 0xfff448f230, for file
/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/artist.py,
line 50, in draw_wrapper (artist=, figure=<...>, _transform=None, _transformSet=False,
_visible=True, _animated=False, _alpha=None, clipbox=None, _clippath=None,
_clipon=True, _label='', _picker=None, _rasterized=False, _agg_filter=None,
_mouseover=False, _callbacks=, callbacks={}, _cid_gen=, _func_cid_map={}, _pickled_cids=set()) at remote 0xfff7a3be20>,
_remove_method=None, _url=None, _gid=None, _snap=None, _sketch=None,
_path_effects=[], _sticky_edges=<_XYPair at remote 0xfff51bacc0>,
_in_layout=True, _suptitle=None, _supxlabel=None, _supylabel=None,
_align_label_groups={'x': , 'y':
, _axes=, _axes=<...>, figure=, figure=<...>,
_transform=None, _transformSet=False, _visible=True, _animated=False,
_alpha=None, clipbox=None, _clippath=None, _clipon=True, _label='',
_picker=None, _rasterized=False, _agg_filter=None, _mouseover=False,
_callbacks=, callbacks={}, _cid_gen=,
_func_cid_map={}, _pickled_cids=set()) at remote 0xfff7a3be20>,
_remove_method=None, _url=None, _gid=None, _snap=None, _sketch=None,
_path_effects=[], _sticky_edges=<_XYPair at remote 0xfff51bacc0>,
_in_layout=True, _suptitle=None, _supxlabel=None, _supylabel=None,
_align_label_group...(truncated)
'matplotlib.ticker.Locator')
#33 Frame 0xfff448f040, for file
/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/artist.py,
line 50, in draw_wrapper (artist=, _axes=, _axes=<...>,
figure=,
figure=<...>, _transform=None, _transformSet=False, _visible=True,
_animated=False, _alpha=None, clipbox=None, _clippath=None, _clipon=True,
_label='', _picker=None, _rasterized=False, _agg_filter=None, _mouseover=False,
_callbacks=, callbacks={}, _cid_gen=,
_func_cid_map={}, _pickled_cids=set()) at remote 0xfff7a3be20>,
_remove_method=None, _url=None, _gid=None, _snap=None, _sketch=None,
_path_effects=[], _sticky_edges=<_XYPair at remote 0xfff51bacc0>,
_in_layout=True, _suptitle=None, _supxlabel=None, _supylabel=None,
_align_...(truncated)
return draw(artist, renderer)
#40 Frame 0xfff46217c0, for file
/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/axis.py,
line 1419, in draw (self=, _axes=, _axes=<...>, figure=, figure=<...>,
_transform=None, _transformSet=False, _visible=True, _animated=False,
_alpha=None, clipbox=None, _clippath=None, _clipon=True, _label='',
_picker=None, _rasterized=False, _agg_filter=None, _mouseover=False,
_callbacks=, callbacks={}, _cid_gen=,
_func_cid_map={}, _pickled_cids=set()) at remote 0xfff7a3be20>,
_remove_method=None, _url=None, _gid=None, _snap=None, _sketch=None,
_path_effects=[], _sticky_edges=<_XYPair at remote 0xfff51bacc0>,
_in_layout=True, _suptitle=None, _supxlabel=None, _supylabel=None,
_align_label_grou...(truncated)
elif not visible: # something false-like but not None
#47 Frame 0xfff461a230, for file
/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/artist.py,
line 50, in draw_wrapper (artist=, _axes=, _axes=<...>,
figure=,
figure=<...>, _transform=None, _transformSet=False, _visible=True,
_animated=False, _alpha=None, clipbox=None, _clippath=None, _clipon=True,
_label='', _picker=None, _rasterized=False, _agg_filter=None, _mouseover=False,
_callbacks=, callbacks={}, _cid_gen=,
_func_cid_map={}, _pickled_cids=set()) at remote 0xfff7a3be20>,
_remove_method=None, _url=None, _gid=None, _snap=None, _sketch=None,
_path_effects=[], _sticky_edges=<_XYPair at remote 0xfff51bacc0>,
_in_layout=True, _suptitle=None, _supxlabel=None, _supylabel=None,
_align_...(truncated)
return draw(artist, renderer)
#54 Frame 0xfff447a040, for file
/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/image.py,
line 388, in _draw_list_compositing_images (artists=[,
_axes=, _axes=<...>, figure=, figure=<...>,
_transform=None, _transformSet=False, _visible=True, _animated=False,
_alpha=None, clipbox=None, _clippath=None, _clipon=True, _label='',
_picker=None, _rasterized=False, _agg_filter=None, _mouseover=False,
_callbacks=, callbacks={}, _cid_gen=,
_func_cid_map={}, _pickled_cids=set()) at remote 0xfff7a3be20>,
_remove_method=None, _url=None,
Bug#999448: [External] Re: Bug#999448: atop: Two fixes for debian/rules: activate atopacctd before activating atop, load atop.default into pkg
On Fri, Dec 24, 2021 at 05:17:07PM +0800, 李菲 wrote: > On Fri, Dec 24, 2021 at 3:02 AM Marc Haber > wrote: > > > On Thu, Dec 23, 2021 at 07:48:19PM +0100, Marc Haber wrote: > > > The interesting line of code is > > > > > > deb-systemd-invoke $_dh_action 'atop-rotate.service' 'atop-rotate.timer' > > 'atop.service' 'atopacct.service > > > > > > which will instruct systemd to start all those four services. I am not > > > sure whether it makes sense for atop to explicitly start the two > > > atop-rotate units, and I think that systemd decides by itself in which > > > order the units are started. > > > > The atopacct unit (systemctl cat atopacct) has an explicit "Before: > > atop.service" listed. So, systemd SHOULD take care of starting atopacctd > > first before atop is started. > > > Actually I am not sure whether "before: " only guarantees this > when the host machine restarts, but not installing packages. I surely do hope that this also applies to systemctl transactions. atop's maintainer scripts group all unit starts into a single transaction, leaving the order of execution to systemd. That's done by debhelper, and as a package maintainer I am not going to interfere with that. The best I can do is to help upstream to properly design their systemd units and probably make code changes to make startup more robust. > > Can you please verify (maybe from syslog?) that the start order is > > actually wrong when you encounter the situation of misbehavior? > > > > Run `dpkg --purge atop && dpkg -i ../atop_2.6.0+byted3_amd64.deb`, > and see the log, just as follows: > # journalctl | grep atop > > Dec 24 17:08:22 n198-252-111 atopacctd[27883]: Terminated by signal 15 > > Dec 24 17:08:22 n198-252-111 systemd[1]: atopacct.service: Succeeded. > > Dec 24 17:08:22 n198-252-111 systemd[1]: atop.service: Succeeded. > > Dec 24 17:08:22 n198-252-111 systemd[1]: atop-rotate.timer: Succeeded. > > Dec 24 17:08:22 n198-252-111 systemd[1]: Stopped Daily atop restart. > > Dec 24 17:08:31 n198-252-111 systemd[1]: Started Daily atop restart. > > Dec 24 17:08:32 n198-252-111 atopacctd[29508]: Version: 2.6.0+byted3 - > 2021/12/23 17:02:33 > > Dec 24 17:08:32 n198-252-111 atopacctd[29508]: accounting to > /run/pacct_source Is that reproducible? > > (2) psacct is installed or not? > > > Yes, > > # dpkg -L atop |grep pacct > > /etc/init.d/atopacct > > /lib/systemd/system/atopacct.service > > /usr/sbin/atopacctd > /usr/share/man/man8/atopacctd.8.gz pSacct is a different package, dpkg --list psacct please. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1001168:
Here the py-bt (gdb) py-bt Traceback (most recent call first): File "/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/lines.py", line 2888, in draw File "/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/artist.py", line 50, in draw_wrapper return draw(artist, renderer) File "/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/axis.py", line 555, in draw 'matplotlib.ticker.Locator') File "/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/artist.py", line 50, in draw_wrapper return draw(artist, renderer) File "/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/axis.py", line 1419, in draw elif not visible: # something false-like but not None File "/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/artist.py", line 50, in draw_wrapper return draw(artist, renderer) File "/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/image.py", line 388, in _draw_list_compositing_images extra_height = (out_height - out_height_base) / out_height_base File "/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/axes/_base.py", line 4106, in draw Python Exception 'ascii' codec can't decode byte 0xc2 in position 2280: ordinal not in range(128): Error occurred in Python: 'ascii' codec can't decode byte 0xc2 in position 2280: ordinal not in range(128)
Bug#1002546: RFS: prometheus-cpp/1.0.0-4 [ITP] -- Prometheus Client Library for Modern C++
On Fri, 24 Dec 2021 01:23:15 +0300 Max Dmitrichenko wrote: Changes for the initial release: prometheus-cpp (1.0.0-4) unstable; urgency=medium . * Provide static libraries with -dev package. prometheus-cpp (1.0.0-1) unstable; urgency=medium . * Initial release. Closes: #917817 Please keep only the 1.0.0-1 entry as long as this is not sponsored. Report your changes on this issue on new uploads instead.
Bug#984276: opencolorio: diff for NMU version 1.1.1~dfsg0-7.1
Control: tags 984276 + pending Dear maintainer, I've prepared an NMU for opencolorio (versioned as 1.1.1~dfsg0-7.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru opencolorio-1.1.1~dfsg0/debian/changelog opencolorio-1.1.1~dfsg0/debian/changelog --- opencolorio-1.1.1~dfsg0/debian/changelog2020-12-17 23:58:56.0 +0100 +++ opencolorio-1.1.1~dfsg0/debian/changelog2021-12-24 11:33:28.0 +0100 @@ -1,3 +1,19 @@ +opencolorio (1.1.1~dfsg0-7.1) unstable; urgency=medium + + * Non-maintainer upload. + * Backport parts of upstream commit 2f87cca2e129471f57df0c3a8a3adc0c73a4811c +to use the proper variables in a debug function (fixing the build with +GCC 11); patch 0001-Adsk-Contrib-Fix-macos-issues-973.patch. +(Closes: #984276) + * Backport parts of upstream commit 7575d9cb0f514a43a4a8b107793914589ae5ac9a +to support yaml-cpp >= 0.7.0; patch +0001-Adsk-Contrib-Fix-the-display-order-issue-883.patch +- bump the libyaml-cpp-dev build dependency to >= 0.6.3 accordingly + * Add the tex-gyre indep build dependency, as it provides tgtermes.sty +(needed to build the documentation). + + -- Pino Toscano Fri, 24 Dec 2021 11:33:28 +0100 + opencolorio (1.1.1~dfsg0-7) unstable; urgency=medium * debian/control: diff -Nru opencolorio-1.1.1~dfsg0/debian/control opencolorio-1.1.1~dfsg0/debian/control --- opencolorio-1.1.1~dfsg0/debian/control 2020-12-17 23:05:42.0 +0100 +++ opencolorio-1.1.1~dfsg0/debian/control 2021-12-24 11:21:58.0 +0100 @@ -15,7 +15,7 @@ libopenimageio-dev (>= 2.0.0) , libqt5opengl5-dev, libtinyxml-dev, - libyaml-cpp-dev, + libyaml-cpp-dev (>= 0.6.3~), pkg-config, python3-dev, python3-docutils, @@ -28,7 +28,8 @@ texlive-latex-base, texlive-latex-extra, texlive-latex-recommended, - texlive-plain-generic + texlive-plain-generic, + tex-gyre Standards-Version: 4.5.1 Rules-Requires-Root: no Homepage: http://opencolorio.org diff -Nru opencolorio-1.1.1~dfsg0/debian/patches/0001-Adsk-Contrib-Fix-macos-issues-973.patch opencolorio-1.1.1~dfsg0/debian/patches/0001-Adsk-Contrib-Fix-macos-issues-973.patch --- opencolorio-1.1.1~dfsg0/debian/patches/0001-Adsk-Contrib-Fix-macos-issues-973.patch 1970-01-01 01:00:00.0 +0100 +++ opencolorio-1.1.1~dfsg0/debian/patches/0001-Adsk-Contrib-Fix-macos-issues-973.patch 2021-12-24 11:04:38.0 +0100 @@ -0,0 +1,23 @@ +From 2f87cca2e129471f57df0c3a8a3adc0c73a4811c Mon Sep 17 00:00:00 2001 +From: Patrick Hodoul +Date: Tue, 24 Mar 2020 15:26:17 -0400 +Subject: [PATCH] Adsk Contrib - Fix macos issues (#973) + +Signed-off-by: Patrick Hodoul +--- + src/core/ImageDesc.cpp| 4 ++-- + 2 files changed, 3 insertions(+), 3 deletions(-) + +--- a/src/core/ImageDesc.cpp b/src/core/ImageDesc.cpp +@@ -57,8 +57,8 @@ OCIO_NAMESPACE_ENTER + os << "gData=" << planarImg->getGData() << ", "; + os << "bData=" << planarImg->getBData() << ", "; + os << "aData=" << planarImg->getAData() << ", "; +-os << "width=" << packedImg->getWidth() << ", "; +-os << "height=" << packedImg->getHeight() << ", "; ++os << "width=" << planarImg->getWidth() << ", "; ++os << "height=" << planarImg->getHeight() << ", "; + os << "yStrideBytes=" << planarImg->getYStrideBytes() << ""; + os << ">"; + } diff -Nru opencolorio-1.1.1~dfsg0/debian/patches/0001-Adsk-Contrib-Fix-the-display-order-issue-883.patch opencolorio-1.1.1~dfsg0/debian/patches/0001-Adsk-Contrib-Fix-the-display-order-issue-883.patch --- opencolorio-1.1.1~dfsg0/debian/patches/0001-Adsk-Contrib-Fix-the-display-order-issue-883.patch 1970-01-01 01:00:00.0 +0100 +++ opencolorio-1.1.1~dfsg0/debian/patches/0001-Adsk-Contrib-Fix-the-display-order-issue-883.patch 2021-12-24 11:14:57.0 +0100 @@ -0,0 +1,659 @@ +From 7575d9cb0f514a43a4a8b107793914589ae5ac9a Mon Sep 17 00:00:00 2001 +From: Patrick Hodoul +Date: Fri, 15 Nov 2019 14:37:27 -0500 +Subject: [PATCH] Adsk Contrib - Fix the display order issue (#883) + +* Adsk Contrib - Fix the display order issue & Improve the serialization precision for double values. + +Signed-off-by: Patrick Hodoul + +* Remove useless code + +Signed-off-by: Patrick Hodoul + +* More cleanup for Yaml build + +Signed-off-by: Patrick Hodoul + +* Improve Clang7 Release support + +Signed-off-by: Patrick Hodoul + +* Improve Yaml error handling + +Signed-off-by: Patrick Hodoul + +* Disable Clang optimizations for OCIOYaml.cpp only + +Signed-off-by: Patrick Hodoul + +* Remove an hard-coded number + +Signed-off-by: Patrick Hodoul + +* Fix last remaining clang7 vs Yaml issues + +Signed-off-by: Patrick Hodoul + +* Fix last remaining clang7 vs Yaml issues, take II + +Signed-off-by: Patrick Hodoul +--- + ext/CMakeLists.txt| 2 +- + share/cmake/modules/FindYamlCpp.cmake | 23 +- +
