Bug#984493: twisted fails autopkg tests
Package: src:twisted
Version: 20.3.0-4
Severity: serious
Tags: sid bullseye
seen on all architectures, triggered with the python3-defaults upload.
https://ci.debian.net/data/autopkgtest/testing/amd64/t/twisted/10825319/log.gz
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/twisted/web/test/test_http.py", line
2344, in testParseqs
self.assertEqual(
File "/usr/lib/python3/dist-packages/twisted/trial/_synctest.py", line 434, in
assertEqual
super(_Assertions, self).assertEqual(first, second, msg)
File "/usr/lib/python3.9/unittest/case.py", line 831, in assertEqual
assertion_func(first, second, msg=msg)
File "/usr/lib/python3.9/unittest/case.py", line 1130, in assertDictEqual
self.fail(self._formatMessage(msg, standardMsg))
twisted.trial.unittest.FailTest: {b'a': [b'b'], b'd': [b'c; =f']} != {b'a':
[b'b'], b'd': [b'c'], b' ': [b'f']}
- {b'a': [b'b'], b'd': [b'c; =f']}
?
+ {b' ': [b'f'], b'a': [b'b'], b'd': [b'c']}
? ++
/usr/lib/python3/dist-packages/twisted/web/http.py:3153: RuntimeWarning: line
buffering (buffering=1) isn't supported in binary mode, the default buffer size
will be used
/usr/lib/python3/dist-packages/twisted/web/http.py:3153: RuntimeWarning: line
buffering (buffering=1) isn't supported in binary mode, the default buffer size
will be used
/usr/lib/python3/dist-packages/twisted/web/http.py:3153: RuntimeWarning: line
buffering (buffering=1) isn't supported in binary mode, the default buffer size
will be used
/usr/lib/python3/dist-packages/twisted/web/http.py:3153: RuntimeWarning: line
buffering (buffering=1) isn't supported in binary mode, the default buffer size
will be used
/usr/lib/python3/dist-packages/twisted/web/http.py:3153: RuntimeWarning: line
buffering (buffering=1) isn't supported in binary mode, the default buffer size
will be used
/usr/lib/python3/dist-packages/twisted/web/http.py:3153: RuntimeWarning: line
buffering (buffering=1) isn't supported in binary mode, the default buffer size
will be used
/usr/lib/python3/dist-packages/twisted/web/http.py:3153: RuntimeWarning: line
buffering (buffering=1) isn't supported in binary mode, the default buffer size
will be used
/usr/lib/python3/dist-packages/twisted/web/http.py:3153: RuntimeWarning: line
buffering (buffering=1) isn't supported in binary mode, the default buffer size
will be used
---
Ran 12628 tests in 183.788s
183.78762769699097 12628 12628 0 1 2436
Bug#983379: linux uml segfault
On Thu, 2021-03-04 at 14:38 +0900, Hajime Tazaki wrote: > > Now, I don't know how to fix it (short of changing your nsswitch > > configuration) - maybe we could somehow rename sem_init()? Or maybe we > > can somehow give the kernel binary a lower symbol resolution than the > > libc/libpthread. > > objcopy (from binutils) can localize symbols (i.e., objcopy -L > sem_init $orig_file $new_file). It also does renaming symbols. But > not sure this is the ideal solution. Yes, we started thinking about it but it was too late at night when I replied ... I think there's basically a way to have an external list of symbols to export, for symbol versioning, that we could/should use to basically not export any of the kernel symbols out to libs. > How does UML handle symbol conflicts between userspace code and Linux > kernel (like this case sem_init) ? AFAIK, libnl has a same symbol as > Linux kernel (genlmsg_put) and others can possibly do as well. I fear it doesn't? johannes
Bug#983379: linux uml segfault
On 04/03/2021 05:38, Hajime Tazaki wrote: On Thu, 04 Mar 2021 07:40:00 +0900, Johannes Berg wrote: I think the problem is here: #24 0x6080f234 in ipc_init_ids (ids=0x60c60de8 ) at ipc/util.c:119 #25 0x60813c6d in sem_init_ns (ns=0x60d895bb ) at ipc/sem.c:254 #26 0x60015b5d in sem_init () at ipc/sem.c:268 #27 0x7f89906d92f7 in ?? () from /lib/x86_64-linux- gnu/libcom_err.so.2 You're in the init of libcom_err.so.2, which is loaded by "libnss_nis.so.2" which is loaded by normal NSS code (getgrnam): #40 0x7f89909bf3a6 in nss_load_library (ni=ni@entry=0x61497db0) at nsswitch.c:359 #41 0x7f89909bfc39 in __GI___nss_lookup_function (ni=0x61497db0, fct_name=, fct_name@entry=0x7f899089b020 "setgrent") at nsswitch.c:467 #42 0x7f899089554b in init_nss_interface () at nss_compat/compat- grp.c:83 #43 init_nss_interface () at nss_compat/compat-grp.c:79 #44 0x7f8990895e35 in _nss_compat_getgrnam_r (name=0x7f8990a2a1e0 "tty", grp=0x7ffe3e7a2910, buffer=0x7ffe3e7a24e0 "", buflen=1024, errnop=0x7f899089eb00) at nss_compat/compat-grp.c:486 #45 0x7f8990968b85 in __getgrnam_r (name=name@entry=0x7f8990a2a1e0 "tty", resbuf=resbuf@entry=0x7ffe3e7a2910, buffer=buffer@entry=0x7ffe3e7a24e0 "", buflen=1024, result=result@entry=0x7ffe3e7a2908) at ../nss/getXXbyYY_r.c:315 You have a strange nsswitch configuration that causes all of this (libnss_nis.so.2 -> libcom_err.so.2) to get loaded. Now libcom_err.so.2 is trying to call sem_init(), and that gets ... tada ... Linux's sem_init() instead of libpthread's. And then the crash. Now, I don't know how to fix it (short of changing your nsswitch configuration) - maybe we could somehow rename sem_init()? Or maybe we can somehow give the kernel binary a lower symbol resolution than the libc/libpthread. objcopy (from binutils) can localize symbols (i.e., objcopy -L sem_init $orig_file $new_file). It also does renaming symbols. But not sure this is the ideal solution. How does UML handle symbol conflicts between userspace code and Linux kernel (like this case sem_init) ? AFAIK, libnl has a same symbol as Linux kernel (genlmsg_put) and others can possibly do as well. It used to handle them. I do not think it does now - something broke and it's fairly recent. I actually have something which confirms this. I worked on a patch around 5.8-5.9 which would give the option to pick up libc equivalents for the functions from string.h and there was a clear performance difference of ~ 20%+ This is because UML has no means of optimizing them and picks up the worst case scenario x86 version. I parked that for a while, because had to look at other stuff at work. I restarted working on it after 5.10. My first observation was that despite not changing anything in the patches, the gain was no longer there. The performance was the same as if it picked up libc equivalents. I can either try to reproduce the nss config which causes the sem_init issue or use my own libc patchset to try to dissect. The problem commit will be roughly around the time the performance difference from applying the "switch to libc" goes away. Brgds, A. -- Hajime ___ linux-um mailing list linux...@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um -- Anton R. Ivanov https://www.kot-begemot.co.uk/
Bug#983263: marked as done (3.21.2 should not migrate automatically (yet))
Your message dated Thu, 04 Mar 2021 08:43:11 +0100 with message-id <1794198.c2dewoh...@odyx.org> and subject line Re: Bug#983263: 3.21.2 should not migrate automatically (yet) has caused the Debian Bug report #983263, regarding 3.21.2 should not migrate automatically (yet) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hplip Version: 3.21.2+dfsg0-1 Severity: serious As hplip maintainer, I'm hereby making sure that hplip 3.21.2 doesn't migrate automatically to bullseye. It was uploaded by mistake to unstable, but two alternatives exist: - A) Revert to 3.20.11, because the changes are too disruptive; - B) Allow 3.21.2 in bullseye, because the increased hardware support is worth it. Let's give the autobuilders, autopkgtest runners and Debian sid users some time in this soft freeze, to see whether there are important regressions tilting this balance towards A). OdyX --- End Message --- --- Begin Message --- Version: 3.21.2+dfsg1-1 Le dimanche, 21 février 2021, 19.31:14 h CET Didier 'OdyX' Raboud a écrit : > As hplip maintainer, I'm hereby making sure that hplip 3.21.2 doesn't > migrate automatically to bullseye. It was uploaded by mistake to unstable, > but two alternatives exist: > - A) Revert to 3.20.11, because the changes are too disruptive; > - B) Allow 3.21.2 in bullseye, because the increased hardware support is > worth it. > > Let's give the autobuilders, autopkgtest runners and Debian sid users some > time in this soft freeze, to see whether there are important regressions > tilting this balance towards A). As there were no regressions brought to my attention, let's get 3.21.2 in Bullseye; I'll address the proposed patches once it migrated. OdyX signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#983379: linux uml segfault
On Thu, 2021-03-04 at 07:28 +, Anton Ivanov wrote: > > > Now, I don't know how to fix it (short of changing your nsswitch > > configuration) - maybe we could somehow rename sem_init()? Or maybe we > > can somehow give the kernel binary a lower symbol resolution than the > > libc/libpthread. > > I have not looked in depth in how the linking process works, but it > should have picked up the sem_init from the kernel library, not libc. Well, no, other way around? libnss/libcom_err should have gotten (should get) the one from libpthread, not the one from the kernel. > We are already supposed to do that regarding kernel vs libc string.h > functions - memcpy, etc. > > Though for all of them the libc does the same so invoking the wrong one > does not kill you so this may have been broken for a while and we were > simply not noticing it. Indeed. johannes
Processed: affects 983365
Processing commands for cont...@bugs.debian.org: > affects 983365 linphone-desktop Bug #983365 [src:linphone] linphone-desktop: chat messages Ignoring request to set affects of bug 983365 to the same value previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 983365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984492: autopkg test failures
Package: src:python-w3lib
Version: 1.22.0-2
Severity: serious
Tags: sid bullseye
seen on all architectures, triggered by the python3-defaults upload.
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-w3lib/10824843/log.gz
=== python3.9 ===
= test session starts ==
platform linux -- Python 3.9.2, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.or2rkj_p/downtmp/autopkgtest_tmp
collected 146 items
tests/test_encoding.py ... [ 13%]
tests/test_form.py ... [ 15%]
tests/test_html.py . [ 51%]
[ 51%]
tests/test_http.py ... [ 56%]
tests/test_url.py F. [ 93%]
.. [100%]
=== FAILURES ===
UrlTests.test_add_or_replace_parameter
self =
def test_add_or_replace_parameter(self):
url = 'http://domain/test'
self.assertEqual(add_or_replace_parameter(url, 'arg', 'v'),
'http://domain/test?arg=v')
url = 'http://domain/test?arg1=v1=v2=v3'
self.assertEqual(add_or_replace_parameter(url, 'arg4', 'v4'),
'http://domain/test?arg1=v1=v2=v3=v4')
self.assertEqual(add_or_replace_parameter(url, 'arg3', 'nv3'),
'http://domain/test?arg1=v1=v2=nv3')
url = 'http://domain/test?arg1=v1;arg2=v2'
> self.assertEqual(add_or_replace_parameter(url, 'arg1', 'v3'),
'http://domain/test?arg1=v3=v2')
E AssertionError: 'http://domain/test?arg1=v3' !=
'http://domain/test?arg1=v3=v2'
E - http://domain/test?arg1=v3
E + http://domain/test?arg1=v3=v2
E ?
tests/test_url.py:303: AssertionError
=== warnings summary ===
tests/test_url.py::UrlTests::test_urljoin_rfc_deprecated
/usr/lib/python3/dist-packages/w3lib/url.py:618: DeprecationWarning:
w3lib.url.urljoin_rfc is deprecated, use urlparse.urljoin instead
warnings.warn("w3lib.url.urljoin_rfc is deprecated, use urlparse.urljoin
instead",
-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info
FAILED tests/test_url.py::UrlTests::test_add_or_replace_parameter - Assertion...
=== 1 failed, 145 passed, 1 warning in 0.61s ===
Bug#984491: autopkg tests fail
Package: src:python-furl Version: 2.1.0-2 Severity: serious Tags: sid bullseye triggered by the recent python3-defaults upload, tests failing on all architectures: https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-furl/10824361/log.gz autopkgtest [08:08:01]: test unittest: [--- ..F.FFF...F. == FAIL: test_add (tests.test_furl.TestQuery) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.0gvxgc25/downtmp/build.Mkz/src/tests/test_furl.py", line 660, in test_add assert q.params.allitems() == runningsum AssertionError == FAIL: test_params (tests.test_furl.TestQuery) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.0gvxgc25/downtmp/build.Mkz/src/tests/test_furl.py", line 788, in test_params assert item1 == item2 AssertionError == FAIL: test_remove (tests.test_furl.TestQuery) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.0gvxgc25/downtmp/build.Mkz/src/tests/test_furl.py", line 702, in test_remove assert len(q.params) == 0 AssertionError == FAIL: test_set (tests.test_furl.TestQuery) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.0gvxgc25/downtmp/build.Mkz/src/tests/test_furl.py", line 669, in test_set assert q.params.allitems() == items_omd.allitems() AssertionError == FAIL: test_various (tests.test_furl.TestQuery) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.0gvxgc25/downtmp/build.Mkz/src/tests/test_furl.py", line 632, in test_various assert q.params.allitems() == items.allitems() AssertionError -- Ran 76 tests in 1.357s FAILED (failures=5)
Bug#983379: linux uml segfault
On 03/03/2021 22:40, Johannes Berg wrote: I think the problem is here: #24 0x6080f234 in ipc_init_ids (ids=0x60c60de8 ) at ipc/util.c:119 #25 0x60813c6d in sem_init_ns (ns=0x60d895bb ) at ipc/sem.c:254 #26 0x60015b5d in sem_init () at ipc/sem.c:268 #27 0x7f89906d92f7 in ?? () from /lib/x86_64-linux- gnu/libcom_err.so.2 You're in the init of libcom_err.so.2, which is loaded by "libnss_nis.so.2" which is loaded by normal NSS code (getgrnam): #40 0x7f89909bf3a6 in nss_load_library (ni=ni@entry=0x61497db0) at nsswitch.c:359 #41 0x7f89909bfc39 in __GI___nss_lookup_function (ni=0x61497db0, fct_name=, fct_name@entry=0x7f899089b020 "setgrent") at nsswitch.c:467 #42 0x7f899089554b in init_nss_interface () at nss_compat/compat- grp.c:83 #43 init_nss_interface () at nss_compat/compat-grp.c:79 #44 0x7f8990895e35 in _nss_compat_getgrnam_r (name=0x7f8990a2a1e0 "tty", grp=0x7ffe3e7a2910, buffer=0x7ffe3e7a24e0 "", buflen=1024, errnop=0x7f899089eb00) at nss_compat/compat-grp.c:486 #45 0x7f8990968b85 in __getgrnam_r (name=name@entry=0x7f8990a2a1e0 "tty", resbuf=resbuf@entry=0x7ffe3e7a2910, buffer=buffer@entry=0x7ffe3e7a24e0 "", buflen=1024, result=result@entry=0x7ffe3e7a2908) at ../nss/getXXbyYY_r.c:315 You have a strange nsswitch configuration that causes all of this (libnss_nis.so.2 -> libcom_err.so.2) to get loaded. Now libcom_err.so.2 is trying to call sem_init(), and that gets ... tada ... Linux's sem_init() instead of libpthread's. And then the crash. Now, I don't know how to fix it (short of changing your nsswitch configuration) - maybe we could somehow rename sem_init()? Or maybe we can somehow give the kernel binary a lower symbol resolution than the libc/libpthread. I have not looked in depth in how the linking process works, but it should have picked up the sem_init from the kernel library, not libc. We are already supposed to do that regarding kernel vs libc string.h functions - memcpy, etc. Though for all of them the libc does the same so invoking the wrong one does not kill you so this may have been broken for a while and we were simply not noticing it. johannes -- Anton R. Ivanov https://www.kot-begemot.co.uk/
Bug#984490: test-archive.t fails in the autopkg tests
Package: src:mercurial Version: 5.6.1-2 Severity: serious Tags: sid bullseye test-archive.t fails in the autopkg tests (all architectures), triggered by the python3-defaults upload: https://ci.debian.net/data/autopkgtest/testing/amd64/m/mercurial/10823665/log.gz --- /tmp/autopkgtest-lxc.75_lnl28/downtmp/build.6MQ/src/tests/test-archive.t +++ /tmp/autopkgtest-lxc.75_lnl28/downtmp/build.6MQ/src/tests/test-archive.t.err @@ -350,49 +350,59 @@ > sys.stderr.write(str(e) + '\n') > EOF $ "$PYTHON" getarchive.py "$TIP" gz | gunzip | tar tf - 2>/dev/null - test-archive-1701ef1f1510/.hg_archival.txt - test-archive-1701ef1f1510/.hgsub - test-archive-1701ef1f1510/.hgsubstate - test-archive-1701ef1f1510/bar - test-archive-1701ef1f1510/baz/bletch - test-archive-1701ef1f1510/foo - test-archive-1701ef1f1510/subrepo/sub + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz + + gzip: stdin: unexpected end of file + [2] $ "$PYTHON" getarchive.py "$TIP" bz2 | bunzip2 | tar tf - 2>/dev/null - test-archive-1701ef1f1510/.hg_archival.txt - test-archive-1701ef1f1510/.hgsub - test-archive-1701ef1f1510/.hgsubstate - test-archive-1701ef1f1510/bar - test-archive-1701ef1f1510/baz/bletch - test-archive-1701ef1f1510/foo - test-archive-1701ef1f1510/subrepo/sub + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=bz2 + + bunzip2: Compressed file ends unexpectedly; + perhaps it is corrupted? *Possible* reason follows. + bunzip2: Inappropriate ioctl for device + Input file = (stdin), output file = (stdout) + + It is possible that the compressed file(s) have become corrupted. + You can use the -tvv option to test integrity of such files. + + You can use the `bzip2recover' program to attempt to recover + data from undamaged sections of corrupted files. + + [2] $ "$PYTHON" getarchive.py "$TIP" zip > archive.zip + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=zip $ unzip -t archive.zip Archive: archive.zip - testing: test-archive-1701ef1f1510/.hg_archival.txt*OK (glob) - testing: test-archive-1701ef1f1510/.hgsub*OK (glob) - testing: test-archive-1701ef1f1510/.hgsubstate*OK (glob) - testing: test-archive-1701ef1f1510/bar*OK (glob) - testing: test-archive-1701ef1f1510/baz/bletch*OK (glob) - testing: test-archive-1701ef1f1510/foo*OK (glob) - testing: test-archive-1701ef1f1510/subrepo/sub*OK (glob) - No errors detected in compressed data of archive.zip. +End-of-central-directory signature not found. Either this file is not +a zipfile, or it constitutes one disk of a multi-part archive. In the +latter case the central directory and zipfile comment will be found on +the last disk(s) of this archive. + unzip: cannot find zipfile directory in one of archive.zip or + archive.zip.zip, and cannot find archive.zip.ZIP, period. + [9] test that we can download single directories and files $ "$PYTHON" getarchive.py "$TIP" gz baz | gunzip | tar tf - 2>/dev/null - test-archive-1701ef1f1510/baz/bletch + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=baz + + gzip: stdin: unexpected end of file + [2] $ "$PYTHON" getarchive.py "$TIP" gz foo | gunzip | tar tf - 2>/dev/null - test-archive-1701ef1f1510/foo + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=foo + + gzip: stdin: unexpected end of file + [2] test that we detect file patterns that match no files $ "$PYTHON" getarchive.py "$TIP" gz foobar - HTTP Error 404: file(s) not found: foobar + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=foobar test that we reject unsafe patterns $ "$PYTHON" getarchive.py "$TIP" gz relre:baz - HTTP Error 404: file(s) not found: relre:baz + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=relre:baz $ killdaemons.py ERROR: test-archive.t output changed !# Ret was: 0 (test-archive.t)
Bug#982862: marked as done (nagios-plugins-contrib autopkgtest regression on several architectures: check_ssl_cert: unable to write certificate)
Your message dated Thu, 4 Mar 2021 07:49:04 +0100 with message-id <23fe1c01-9b16-5b5e-efe0-41759fffa...@cyconet.org> and subject line Re: [Pkg-nagios-devel] Bug#982862: nagios-plugins-contrib autopkgtest regression on several architectures: check_ssl_cert: unable to write certificate has caused the Debian Bug report #982862, regarding nagios-plugins-contrib autopkgtest regression on several architectures: check_ssl_cert: unable to write certificate to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nagios-plugins-contrib Version: 29.20210204 Severity: serious https://tracker.debian.org/pkg/nagios-plugins-contrib Migration status for nagios-plugins-contrib (28.20201207 to 29.20210204): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: autopkgtest for nagios-plugins-contrib/29.20210204: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass https://ci.debian.net/data/autopkgtest/testing/amd64/n/nagios-plugins-contrib/10465947/log.gz ... autopkgtest [16:53:05]: test command7: /usr/lib/nagios/plugins/check_ssl_cert -H www.debian.org autopkgtest [16:53:05]: test command7: [--- unable to write certificate 139631578813760:error:09072007:PEM routines:PEM_write_bio:BUF lib:../crypto/pem/pem_lib.c:658: SSL_CERT OK - x509 certificate 'www.debian.org' from 'R3' valid until Mar 30 00:17:56 2021 GMT (expires in 43 days)|days_chain_elem1=43;20;15;; days_chain_elem2=227;20;15;; autopkgtest [16:53:07]: test command7: ---] autopkgtest [16:53:07]: test command7: - - - - - - - - - - results - - - - - - - - - - command7 FAIL stderr: unable to write certificate --- End Message --- --- Begin Message --- Package: nagios-plugins-contrib Version: 31.20210225 Hi Adrian, Am 15.02.21 um 16:27 schrieb Adrian Bunk: > Migration status for nagios-plugins-contrib (28.20201207 to 29.20210204): > BLOCKED: Rejected/violates migration policy/introduces a regression > Issues preventing migration: > autopkgtest for nagios-plugins-contrib/29.20210204: amd64: Regression ♻ > (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Pass, i386: > Regression ♻ (reference ♻), ppc64el: Pass > > > https://ci.debian.net/data/autopkgtest/testing/amd64/n/nagios-plugins-contrib/10465947/log.gz > > ... > autopkgtest [16:53:05]: test command7: /usr/lib/nagios/plugins/check_ssl_cert > -H www.debian.org > autopkgtest [16:53:05]: test command7: [--- > unable to write certificate > 139631578813760:error:09072007:PEM routines:PEM_write_bio:BUF > lib:../crypto/pem/pem_lib.c:658: > SSL_CERT OK - x509 certificate 'www.debian.org' from 'R3' valid until Mar 30 > 00:17:56 2021 GMT (expires in 43 days)|days_chain_elem1=43;20;15;; > days_chain_elem2=227;20;15;; > autopkgtest [16:53:07]: test command7: ---] > autopkgtest [16:53:07]: test command7: - - - - - - - - - - results - - - - - > - - - - - > command7 FAIL stderr: unable to write certificate this should be fixed since 31.20210225, see https://ci.debian.net/data/autopkgtest/testing/amd64/n/nagios-plugins-contrib/10706940/log.gz: autopkgtest [03:16:29]: test command7: /usr/lib/nagios/plugins/check_ssl_cert -H www.debian.org autopkgtest [03:16:29]: test command7: [--- SSL_CERT OK - x509 certificate 'www.debian.org' from 'R3' valid until Mar 30 00:17:56 2021 GMT (expires in 31 days)|days_chain_elem1=31;20;15;; days_chain_elem2=215;20;15;; autopkgtest [03:16:30]: test command7: ---] autopkgtest [03:16:31]: test command7: - - - - - - - - - - results - - - - - - - - - - command7 PASS Cheers, Jan. -- Never write mail to , you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-@ s+:()>- a+ C$ UL$ P+ L$ !E--- W+++$ N+++ o++ K++ !w---? O M+ !V- PS+ PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y+ --END GEEK CODE BLOCK-- signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#983379: linux uml segfault
On Thu, 04 Mar 2021 07:40:00 +0900, Johannes Berg wrote: > > I think the problem is here: > > > #24 0x6080f234 in ipc_init_ids (ids=0x60c60de8 ) > > at ipc/util.c:119 > > #25 0x60813c6d in sem_init_ns (ns=0x60d895bb ) at > > ipc/sem.c:254 > > #26 0x60015b5d in sem_init () at ipc/sem.c:268 > > #27 0x7f89906d92f7 in ?? () from /lib/x86_64-linux- > > gnu/libcom_err.so.2 > > You're in the init of libcom_err.so.2, which is loaded by > > > "libnss_nis.so.2" > > which is loaded by normal NSS code (getgrnam): > > > #40 0x7f89909bf3a6 in nss_load_library (ni=ni@entry=0x61497db0) at > > nsswitch.c:359 > > #41 0x7f89909bfc39 in __GI___nss_lookup_function (ni=0x61497db0, > > fct_name=, fct_name@entry=0x7f899089b020 "setgrent") at > > nsswitch.c:467 > > #42 0x7f899089554b in init_nss_interface () at nss_compat/compat- > > grp.c:83 > > #43 init_nss_interface () at nss_compat/compat-grp.c:79 > > #44 0x7f8990895e35 in _nss_compat_getgrnam_r (name=0x7f8990a2a1e0 > > "tty", grp=0x7ffe3e7a2910, buffer=0x7ffe3e7a24e0 "", buflen=1024, > > errnop=0x7f899089eb00) at nss_compat/compat-grp.c:486 > > #45 0x7f8990968b85 in __getgrnam_r (name=name@entry=0x7f8990a2a1e0 > > "tty", resbuf=resbuf@entry=0x7ffe3e7a2910, > > buffer=buffer@entry=0x7ffe3e7a24e0 "", buflen=1024, > > result=result@entry=0x7ffe3e7a2908) > > at ../nss/getXXbyYY_r.c:315 > > > You have a strange nsswitch configuration that causes all of this > (libnss_nis.so.2 -> libcom_err.so.2) to get loaded. > > Now libcom_err.so.2 is trying to call sem_init(), and that gets ... tada > ... Linux's sem_init() instead of libpthread's. > > And then the crash. > > Now, I don't know how to fix it (short of changing your nsswitch > configuration) - maybe we could somehow rename sem_init()? Or maybe we > can somehow give the kernel binary a lower symbol resolution than the > libc/libpthread. objcopy (from binutils) can localize symbols (i.e., objcopy -L sem_init $orig_file $new_file). It also does renaming symbols. But not sure this is the ideal solution. How does UML handle symbol conflicts between userspace code and Linux kernel (like this case sem_init) ? AFAIK, libnl has a same symbol as Linux kernel (genlmsg_put) and others can possibly do as well. -- Hajime
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 982866 serious Bug #982866 [ruby-asciidoctor-kroki] FTBFS: tests require network access Severity set to 'serious' from 'important' > tags 982866 ftbfs Bug #982866 [ruby-asciidoctor-kroki] FTBFS: tests require network access Added tag(s) ftbfs. > reassign 982866 src:ruby-asciidoctor-kroki 0.2.2-2 Bug #982866 [ruby-asciidoctor-kroki] FTBFS: tests require network access Bug reassigned from package 'ruby-asciidoctor-kroki' to 'src:ruby-asciidoctor-kroki'. No longer marked as found in versions ruby-asciidoctor-kroki/0.2.2-2. Ignoring request to alter fixed versions of bug #982866 to the same values previously set Bug #982866 [src:ruby-asciidoctor-kroki] FTBFS: tests require network access Marked as found in versions ruby-asciidoctor-kroki/0.2.2-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 982866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: user debian...@lists.debian.org, usertagging 976499, affects 976499, affects 983887
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 976499 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 976499 + libdune-pdelab-dev
Bug #976499 [src:dune-pdelab] dune-pdelab: FTBFS: segfaults during tests
Added indication that 976499 affects libdune-pdelab-dev
> affects 983887 + cyrus-replication
Bug #983887 {Done: Yadd } [cyrus-imapd] cyrus-imapd: missing
Breaks+Replaces: cyrus-common (<< 3.2.3)
Added indication that 983887 affects cyrus-replication
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976499
983887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#984480: python3-yubikey-manager: copyright file missing after upgrade (policy 12.5)
Package: python3-yubikey-manager Version: 4.0.0~a1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. This was observed on the following upgrade paths: buster -> bullseye >From the attached log (scroll to the bottom...): 0m36.3s ERROR: WARN: Inadequate results from running adequate! python3-yubikey-manager: missing-copyright-file /usr/share/doc/python3-yubikey-manager/copyright MISSING COPYRIGHT FILE: /usr/share/doc/python3-yubikey-manager/copyright # ls -lad /usr/share/doc/python3-yubikey-manager drwxr-xr-x 2 root root 40 Mar 3 01:47 /usr/share/doc/python3-yubikey-manager # ls -la /usr/share/doc/python3-yubikey-manager/ total 0 drwxr-xr-x 2 root root 40 Mar 3 01:47 . drwxr-xr-x 142 root root 2980 Mar 3 01:47 .. Additional info may be available here: https://wiki.debian.org/MissingCopyrightFile Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. cheers, Andreas python3-yubikey-manager_4.0.0~a1-2.log.gz Description: application/gzip
Bug#984479: fai-nfsroot: fails to upgrade from 'buster': diversion clash
Package: fai-nfsroot Version: 5.9.4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. >From the attached log (scroll to the bottom...): Preparing to unpack .../28-fai-nfsroot_5.9.4_all.deb ... dpkg-divert: error: 'diversion of /etc/init.d/rcS to /etc/init.d/rcS.orig by fai-nfsroot' clashes with 'diversion of /etc/init.d/rcS to /etc/init.d/rcS.distrib by fai-nfsroot' dpkg: error processing archive /tmp/apt-dpkg-install-1rWE0W/28-fai-nfsroot_5.9.4_all.deb (--unpack): new fai-nfsroot package pre-installation script subprocess returned error exit status 2 Preparing to unpack .../29-libss2_1.46.1-1_amd64.deb ... Unpacking libss2:amd64 (1.46.1-1) over (1.44.5-1+deb10u3) ... Errors were encountered while processing: /tmp/apt-dpkg-install-1rWE0W/28-fai-nfsroot_5.9.4_all.deb You need to manually migrate the existing diversion to the new name. cheers, Andreas fai-nfsroot_5.9.4.log.gz Description: application/gzip
Bug#984477: libbio-variation-perl: missing Breaks+Replaces: bioperl (<< 1.7.3)
Package: libbio-variation-perl Version: 1.7.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libbio-variation-perl. Preparing to unpack .../048-libbio-variation-perl_1.7.5-1_all.deb ... Unpacking libbio-variation-perl (1.7.5-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-eyjeT8/048-libbio-variation-perl_1.7.5-1_all.deb (--unpack): trying to overwrite '/usr/bin/bp_flanks', which is also in package bioperl 1.7.2-3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) IIRC bioperl 1.7.3 is the version that got split up into several packages, therefore the existing Breaks+Replaces: libbio-perl-perl (<= 1.7.2) are also insufficiently versioned (should be (<< 1.7.3) as well). cheers, Andreas bioperl-run_1.7.3-6.log.gz Description: application/gzip
Processed: libbio-db-ncbihelper-perl: missing Breaks+Replaces: bioperl (<< 1.7.3)
Processing control commands: > affects -1 + bioperl-run Bug #984475 [libbio-db-ncbihelper-perl] libbio-db-ncbihelper-perl: missing Breaks+Replaces: bioperl (<< 1.7.3) Added indication that 984475 affects bioperl-run -- 984475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984475: libbio-db-ncbihelper-perl: missing Breaks+Replaces: bioperl (<< 1.7.3)
Package: libbio-db-ncbihelper-perl Version: 1.7.6-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + bioperl-run Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libbio-db-ncbihelper-perl. Preparing to unpack .../045-libbio-db-ncbihelper-perl_1.7.6-2_all.deb ... Unpacking libbio-db-ncbihelper-perl (1.7.6-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-eyjeT8/045-libbio-db-ncbihelper-perl_1.7.6-2_all.deb (--unpack): trying to overwrite '/usr/bin/bp_biofetch_genbank_proxy', which is also in package bioperl 1.7.2-3 IIRC bioperl 1.7.3 is the version that got split up into several packages. cheers, Andreas bioperl-run_1.7.3-6.log.gz Description: application/gzip
Bug#984474: libbio-asn1-entrezgene-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)
Package: libbio-asn1-entrezgene-perl Version: 1.730-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libbio-asn1-entrezgene-perl. Preparing to unpack .../039-libbio-asn1-entrezgene-perl_1.730-1_all.deb ... Unpacking libbio-asn1-entrezgene-perl (1.730-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-eyjeT8/039-libbio-asn1-entrezgene-perl_1.730-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/Bio::SeqIO::entrezgene.3pm.gz', which is also in package libbio-perl-perl 1.7.2-3 IIRC bioperl 1.7.3 is the version that got split up into several packages, thus the existing B+R: libbio-perl-perl (<= 1.7.2) is insufficient. cheers, Andreas bioperl-run_1.7.3-6.log.gz Description: application/gzip
Processed: closing 983167
Processing commands for cont...@bugs.debian.org: > close 983167 7.1.1+dfsg2-10 Bug #983167 [src:vtk7] vtk7: binary-all FTBFS Marked as fixed in versions vtk7/7.1.1+dfsg2-10. Bug #983167 [src:vtk7] vtk7: binary-all FTBFS Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 983167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982578: marked as done (stunnel4: CVE-2021-20230: client certificate not correctly verified when redirect and verifyChain options are used)
Your message dated Thu, 04 Mar 2021 00:48:29 + with message-id and subject line Bug#982578: fixed in stunnel4 3:5.56+dfsg-8 has caused the Debian Bug report #982578, regarding stunnel4: CVE-2021-20230: client certificate not correctly verified when redirect and verifyChain options are used to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stunnel4 Version: 3:5.56+dfsg-6 Severity: grave Tags: patch security upstream fixed-upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for stunnel4. CVE-2021-20230[0]: | client certificate not correctly verified when redirect and | verifyChain options are used If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-20230 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20230 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1925226 [2] https://bugzilla.suse.com/show_bug.cgi?id=1177580 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: stunnel4 Source-Version: 3:5.56+dfsg-8 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest version of stunnel4, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated stunnel4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 04 Mar 2021 00:59:13 +0200 Source: stunnel4 Architecture: source Version: 3:5.56+dfsg-8 Distribution: unstable Urgency: medium Maintainer: Peter Pentchev Changed-By: Peter Pentchev Closes: 982578 Changes: stunnel4 (3:5.56+dfsg-8) unstable; urgency=medium . * Add some patches cherry-picked from stunnel-5.57 and 5.58: - 09-verify-redirect and 10-verify-noredirect: CVE-2021-20230 - 11-test-netcat-source: ensure netcat is invoked properly by the test suite - 12-bio-free: fix a memory allocation/deallocation inconsistency - 13-tls13: TLS 1.3 compatibility fixes needed to let the internal tests pass with the verification/redirect fixes . All of this together Closes: #982578 Checksums-Sha1: 2015ed8fca44cf19de65332c55c188211be72406 2847 stunnel4_5.56+dfsg-8.dsc 0a6373ea19c3f76279a5c399bf9e8f6de3701521 51308 stunnel4_5.56+dfsg-8.debian.tar.xz Checksums-Sha256: 1f13970587fcc49b97acabf35d75ed4b5451922a36fa618c4df4cd85643db669 2847 stunnel4_5.56+dfsg-8.dsc 6e8fc108c5b384d96a6126072e185fa9d2b29f889866b0a99f154ab59a102aaf 51308 stunnel4_5.56+dfsg-8.debian.tar.xz Files: 4a93a80f75e0150f1975313b41283e7c 2847 net optional stunnel4_5.56+dfsg-8.dsc ebc782535dfd538fc7eab676b082b8f5 51308 net optional stunnel4_5.56+dfsg-8.debian.tar.xz -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmBAKVcQHHJvYW1AZGVi aWFuLm9yZwAKCRBlHu+wJSffE0+tEADD7ENkuX5Zj4DQjXTzDhed0sbPWphbCMpc fE90BTtQUi4/Gn0zkWgWDA29LNP2lrVEks52w7ETU0bQEolx9Lvbjr483uTTosM8 brb0QkF74r0EFCvyp/hRpWSSCZATLMBP1tMvVCP6CIv2ycUtY8jIOisLr+PLhFBq rA23UMYfjaZQnAtaN585K10wqU6MYjtaiH+C1zaKLgJmM/j5sJGtsuMXOY3xxlkI Yx88wMz3wnu6v6bzLoVcxELIOcOUPfbH2m4jC9wz7JXn5kGXLTy1Urq0aJS1gFmB CuruTmQ5LNAWPUtlY/Z9jikoJgXoGl9vQMwBiMj5Kc2LDVMQUDd0hfeeUHsuiC0r DwnVX3fkDCwIi2pOaAWGnVzBsW/yt9ZzQHJcBCccXGQNFR9WGFyBCgvZ/bkOBYYu YS44rbqdbGCtEWIhGwk84KtKhTIzoAtK2E9UIh0cM5AscpT7r+ly5Vds2AJ0Ix8E i8EEBMLmFeuaUCoEfejZ4hIPuhiSFV6iV5eer0jkIkZDbvOZqgN6Tqbjvgxp7cgx MlMbtM9WzhNsq2CTGmE2wWZip675Bw8w5LVMm2fQ9MoGr/K5Hxr0QokRxvLxX/+E btG3t1G1+4tJdJRcFc3W2S4ZcOOkBwbWkegmYAp/y8409R7jh2hppnDYTnBTijXC MWmf+yayTQ== =MXSu -END PGP SIGNATURE End Message ---
Bug#979698: marked as done (src:nodejs: should provide virtual package node-types-node)
Your message dated Wed, 03 Mar 2021 23:48:32 + with message-id and subject line Bug#979698: fixed in nodejs 14.16.0~dfsg-1 has caused the Debian Bug report #979698, regarding src:nodejs: should provide virtual package node-types-node to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nodejs Version: 12.20.1~dfsg-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bug#979693 indicates that nodejs now embeds Node.js module @node/types. Please provide virtual packages for any and all modules installed, so that consuming packages can declare explicit package relations, which helps in e.g. assess when to deprecate embedded modules or maybe move them out to independent packages. Even if the module is inherently tied to the src:nodejs codebase, it is still helpful to consistently declare virtual packages for all modules: I hope that we can at some point make it into Debian Policy that Node.js modules *must* be declared as (virtual or real) package name, which can then simplify tooling. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/60G4ACgkQLHwxRsGg ASFL5BAAhc2+rVdE2JNYjw3X42mDoKOQz34+hiX++oGEmITW0XJB8uTCsdJ5s0oj kH6zkzqdw6m4flK/pHcPFN/vqQksSprI7ZR8MRfWogjBSTCTmiH2J5/jlmEgBKta 1CLvB7HdSnbRBU2r427oxrqvPMjL7BV6Rb1TLKN98mP9BHaBdBiU63AVnLoKi5Qn EdFX86/9/vvng6X4z7T2Gr1XN2p2UXFom094fbtJ+YyiZhSbFwcQdFXQez0glrkS 90E7FmW/fdvikBF614IBy3q21PtB6w9Fp05UmZu9BtoqePGzkqkXG3BU42t3axIK hoZFDAKPAyY02vacPJ+N/QLJTpJ7xQiJmYmExUbMVAfyPzVQmSBBDtmSgSbAfsYf N9qEJgT4oTtzJWDzY4Ytp9Ed+eiqjDiUOuekwViYpFzP2vgsYfCh5aoi7mfcr+IK wIrcvGXGkmOBkfWbjtCv2jHivj67sQwIl/77UrUVmvjdhcqAoHJEpxE74mWETu1Q QiGIG/LL/j5zbqA5Vgf+eb4fsHZ5npswkbHZbIPHCpQE2i799ewP/7ZAKuxuGQWZ QAgx9ESMj9BVOgrUtRJ8ML7lxxQ+uDOgiHQMweh6cGrUqRtpsnxkoGijTxmJNJJa g/rjkrv2+cr/QAVLzIXxygdFiVE4+4z86HOUR3XZY7lS1koQVOA= =49m6 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 14.16.0~dfsg-1 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 04 Mar 2021 00:29:51 +0100 Source: nodejs Architecture: source Version: 14.16.0~dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Closes: 979698 Changes: nodejs (14.16.0~dfsg-1) experimental; urgency=medium . [ Jérémy Lal ] * New upstream version 14.16.0~dfsg Fixed vulnerabilities: + CVE-2021-22883: HTTP2 'unknownProtocol' cause DoS by resource exhaustion + CVE-2021-22884: localhost6 DNS rebinding in --inspect * Refresh make-doc patch * Patch to always use pure javascript cjs lexer * copyright: cjs-module-lexer is expat * copyright: exclude cjs-module-lexer unbuildable files * copyright: fix some copyright years * copyright: shjs is no longer used * lintian-overrides: false positive for a unicode regexp . [ Xavier Guimard ] * Embed @types/node 14 * Provides node-types-node (Closes: #979698) * Use secure copyright file specification URI. * Set upstream metadata fields: Security-Contact. * Bump debhelper compatibility level to 13 * Declare compliance with policy 4.5.1 * Use secure URI in Homepage field. * Add "Rules-Requires-Root: no" * Modernize debian/watch * Add ctype=nodejs to component(s) * Update d/copyright urls Checksums-Sha1: 33cc08048de15b5c04847843d32342209a9ff9db 3464 nodejs_14.16.0~dfsg-1.dsc 8c254868fb7fdd6e011c7d97939d53626cecdcf5 89040 nodejs_14.16.0~dfsg.orig-types-node.tar.xz 8d2921d305989633453c90bbe9aa32ce10af4011 18876272 nodejs_14.16.0~dfsg.orig.tar.xz fcfdb817227aaa76dfe99656fa7c88c1548aa4d7 134392 nodejs_14.16.0~dfsg-1.debian.tar.xz 92ded56bb5a0aa948b72897842ff6c97720ad36b 8296
Bug#983365: [PATCH] Re: Bug#983365: linphone-desktop: chat messages
Am 03.03.21 um 18:55 schrieb Dennis Filder: Hi Dennis, > On Sun, Feb 28, 2021 at 11:07:31PM +0100, Bernhard Schmidt wrote: >> an updated liblinphone has been uploaded to sid yesterday. Could you >> please try liblinphone10 and liblinphone++10 from sid (4.4.21-2) and >> report back? If it does not work you might need libsoci-core4.0 and >> libsoci-sqlite3-4.0 from unstable as well (4.0.1-4). > > I finally found the bug: libsoci_sqlite3 sometimes returns string > where liblinphone unconditionally expects int, long, double etc. which > led to silent std::bad_cast exceptions. I can't say who is actually > to blame (I feel soci should do that conversion already as it knows > what type the user requested, or at least not throw silently), but the > attached patches remedy the issue through some conditional string > conversion and make chat history actually work again in the GUI. They > should really have separated the sqlite3 database code better from the > MySQL code. > > I put this in two separate patches to make it easier to remove the > changes to the code for the legacy DB migration in case it causes > problems. Cool, thanks. Would you mind discussing your findings with upstream at https://gitlab.linphone.org/BC/public/liblinphone ? We will need a freeze exception for this, having this bug confirmed by upstream would help a lot, cherry-picking a commit from upstream would be even better. Right now I don't plan to upload src:linphone before 4.4.21-2 has migrated to testing, in order to have a minimum amount of changes to be discussed for the freeze exception. Bernhard
Processed: reassign 983365 to src:linphone
Processing commands for cont...@bugs.debian.org: > reassign 983365 src:linphone 4.4.21-1 Bug #983365 [linphone] linphone-desktop: chat messages Bug reassigned from package 'linphone' to 'src:linphone'. No longer marked as found in versions 4.4.21-2 and 4.4.21-1. Ignoring request to alter fixed versions of bug #983365 to the same values previously set Bug #983365 [src:linphone] linphone-desktop: chat messages Marked as found in versions linphone/4.4.21-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 983365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984469: guitarix: debian/copyright is inaccurate
Package: guitarix
Version: 0.42.1+dfsg1-1
Severity: serious
Tags: patch
Justification: Policy 12.5
Dear Debian Multimedia Maintainers,
I noticed that the [debian/copyright] file for guitarix states that
two images ('data/Layout.svg' and 'data/stereo.svg') are under
CC-BY-1.0, which does not meet the DFSG.
[debian/copyright]:
I got in touch with the upstream developers, with the intention to
persuade them to re-license the two files under DFSG-free terms.
And I found out that those two files are already under GPL-2+,
as the majority of the guitarix package files.
See the [confirmation] from the Guitarix devs.
[confirmation]:
Bug#983379: linux uml segfault
I think the problem is here: > #24 0x6080f234 in ipc_init_ids (ids=0x60c60de8 ) > at ipc/util.c:119 > #25 0x60813c6d in sem_init_ns (ns=0x60d895bb ) at > ipc/sem.c:254 > #26 0x60015b5d in sem_init () at ipc/sem.c:268 > #27 0x7f89906d92f7 in ?? () from /lib/x86_64-linux- > gnu/libcom_err.so.2 You're in the init of libcom_err.so.2, which is loaded by > "libnss_nis.so.2" which is loaded by normal NSS code (getgrnam): > #40 0x7f89909bf3a6 in nss_load_library (ni=ni@entry=0x61497db0) at > nsswitch.c:359 > #41 0x7f89909bfc39 in __GI___nss_lookup_function (ni=0x61497db0, > fct_name=, fct_name@entry=0x7f899089b020 "setgrent") at > nsswitch.c:467 > #42 0x7f899089554b in init_nss_interface () at nss_compat/compat- > grp.c:83 > #43 init_nss_interface () at nss_compat/compat-grp.c:79 > #44 0x7f8990895e35 in _nss_compat_getgrnam_r (name=0x7f8990a2a1e0 > "tty", grp=0x7ffe3e7a2910, buffer=0x7ffe3e7a24e0 "", buflen=1024, > errnop=0x7f899089eb00) at nss_compat/compat-grp.c:486 > #45 0x7f8990968b85 in __getgrnam_r (name=name@entry=0x7f8990a2a1e0 > "tty", resbuf=resbuf@entry=0x7ffe3e7a2910, > buffer=buffer@entry=0x7ffe3e7a24e0 "", buflen=1024, > result=result@entry=0x7ffe3e7a2908) > at ../nss/getXXbyYY_r.c:315 You have a strange nsswitch configuration that causes all of this (libnss_nis.so.2 -> libcom_err.so.2) to get loaded. Now libcom_err.so.2 is trying to call sem_init(), and that gets ... tada ... Linux's sem_init() instead of libpthread's. And then the crash. Now, I don't know how to fix it (short of changing your nsswitch configuration) - maybe we could somehow rename sem_init()? Or maybe we can somehow give the kernel binary a lower symbol resolution than the libc/libpthread. johannes
Bug#979698: marked as pending in nodejs
Control: tag -1 pending Hello, Bug #979698 in nodejs 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/js-team/nodejs/-/commit/7dc73f6f3217c59a10cf558ce479e15c8d21bfa8 Provides node-types-node Closes: #979698 (this message was generated automatically) -- Greetings https://bugs.debian.org/979698
Processed: Bug#979698 marked as pending in nodejs
Processing control commands: > tag -1 pending Bug #979698 [src:nodejs] src:nodejs: should provide virtual package node-types-node Added tag(s) pending. -- 979698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966784: marked as done (python-pymetar: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 03 Mar 2021 22:00:10 + with message-id and subject line Bug#938076: fixed in python-pymetar 1.2-0.1 has caused the Debian Bug report #938076, regarding python-pymetar: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pymetar Version: 0.19-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-pymetar Source-Version: 1.2-0.1 Done: Mattia Rizzolo We believe that the bug you reported is fixed in the latest version of python-pymetar, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated python-pymetar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 16 Feb 2021 19:13:34 +0100 Source: python-pymetar Binary: python3-pymetar Architecture: source all Version: 1.2-0.1 Distribution: unstable Urgency: low Maintainer: Uli Martens Changed-By: Mattia Rizzolo Description: python3-pymetar - Python interface to METAR reports Closes: 835340 938076 Changes: python-pymetar (1.2-0.1) unstable; urgency=low . * Non-maintainer upload. . [ gregor herrmann ] * New upstream release. - Fixes "http://weather.noaa.gov/ no longer available" (Closes: #835340) - Update .docs file to renamed/removed documents. * The new upstream release is (only) python3 compatible: - Change package name and related helper files to python3-pymetar. - Breaks/Replaces old python-pymetar. - Update build system to use --buildsystem=pybuild --with=python3. - Update build dependencies. - Depend on ca-certificates for the new default METAR URL. - Fixes "Python2 removal in sid/bullseye". (Closes: #938076) * Move Homepage field from binary to source package. . [ Mattia Rizzolo ] * Use source format 3.0 (quilt). * Convert the hack used to ignore upstream's data_files into a real patch. * Use debhelper-compat(=13) instead of d/compat (and with this, also bump the compat level). * Rewrite d/copyright using copyright-format 1.0. * Bump Standards-Version to 4.5.1: + Set Rules-Requires-Root: no * Bump watch file format to 4 and adapt to the new format version. Checksums-Sha1: 8b5c7490d1c21aaccec412f496a3ba3b6ed65da2 1842 python-pymetar_1.2-0.1.dsc f308e3a13e068cf77833d23f61d0f9ae621fe84a 3163447 python-pymetar_1.2.orig.tar.gz a51ee2c65f53a05f759957cc14815c34d1bc28fb 4288 python-pymetar_1.2-0.1.debian.tar.xz cccf2668b66c334aa1ad8a29093cab89e18584aa 6335 python-pymetar_1.2-0.1_amd64.buildinfo 0c0ab92c03acc4d87e3985a437ca0cb8003fe611 17704 python3-pymetar_1.2-0.1_all.deb Checksums-Sha256: 7cc7507a9de167c44d1c5f0ad6cf56a2d8e7d7042e73eb1c00413d8490046215 1842 python-pymetar_1.2-0.1.dsc f9a8caa21eff5367427da55a469ef396293ae4cc93797ab2f1a66a2924fbdc68 3163447 python-pymetar_1.2.orig.tar.gz
Bug#938076: marked as done (python-pymetar: Python2 removal in sid/bullseye)
Your message dated Wed, 03 Mar 2021 22:00:10 + with message-id and subject line Bug#938076: fixed in python-pymetar 1.2-0.1 has caused the Debian Bug report #938076, regarding python-pymetar: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pymetar Version: 0.19-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-pymetar If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-pymetar Source-Version: 1.2-0.1 Done: Mattia Rizzolo We believe that the bug you reported is fixed in the latest version of python-pymetar, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated python-pymetar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 16 Feb 2021 19:13:34 +0100 Source: python-pymetar Binary: python3-pymetar Architecture: source all Version: 1.2-0.1 Distribution: unstable Urgency: low Maintainer: Uli Martens Changed-By: Mattia Rizzolo Description: python3-pymetar - Python interface to METAR reports Closes: 835340 938076 Changes: python-pymetar (1.2-0.1) unstable; urgency=low . * Non-maintainer upload. . [ gregor herrmann ] * New upstream release. - Fixes "http://weather.noaa.gov/ no longer available" (Closes: #835340) - Update .docs file to renamed/removed documents. * The new upstream release is (only) python3 compatible: - Change package name and related helper files to python3-pymetar. - Breaks/Replaces old python-pymetar. - Update build system to use --buildsystem=pybuild --with=python3. - Update build dependencies. - Depend on ca-certificates for the new default
Bug#835340: marked as done (python-pymetar: http://weather.noaa.gov/ no longer available)
Your message dated Wed, 03 Mar 2021 22:00:10 + with message-id and subject line Bug#835340: fixed in python-pymetar 1.2-0.1 has caused the Debian Bug report #835340, regarding python-pymetar: http://weather.noaa.gov/ no longer available to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 835340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-pymetar Version: 0.19-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 pymetar uses http://weather.noaa.gov/pub/data/observations/metar/decoded/ as its baseurl. Since yesterday this URL, and also http://weather.noaa.gov/, just say "This Service is no longer available" which makes pymetar non-functional without manually passing a different baseurl. I looked around a bit on noaa.gov and found http://www.nws.noaa.gov/tg/datahelp.php -> "Decoded METAR Reports" which leads to http://tgftp.nws.noaa.gov/data/observations/metar/decoded/ which seems to work as a replacement. Cheers, gregor - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages python-pymetar depends on: ii python 2.7.11-2 ii python2.7 2.7.12-2 python-pymetar recommends no packages. python-pymetar suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJXvbReXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGwkwQAJAXcfKRFNEUwIozv7pXz6Am x7rK9pJgI8eA4kk5WYBVtmYTmO3FQvHCB2IdLYfo6U0AoeEuojB3TPOzBEm0zrj2 pa094w5VeRB9/0Xz0DxbJVnBISn7cdp5dejasMPRDOaVtRr1ZZsUmS1R+6zn8v9V WKHtF31Pgt7qX5Atm0OkIQHm5Fn8Eg8ZTqXrw7uEhZaJQgIta+KJe85tLXmGnbOQ hdl4ibTRw/M83o0djR01H0DCVkgtL8y6nN8BrzdLKtr5XiprF7mCSuya4A4Gspzd 4HSnE3g7KgyVZx4N++SjkXYgaqeFsOWpHOdZe+BcJc31w9qDWHOgmqGok30lhStx AUviT0dGB2qp7anLkYMivsxKHip8lC/IhtZs95IGpBzFcop/00X0Na4Rr3oEDT+G 9LshQdrE2V5obwUD/wAv2ztpH5AA4eO4HC5iKWnQGLqXrn+7grdYCqN8HPz2kOpb ddh7ebj3Q9BKN5mUv7XZCIc6SqAujGE36SYplFo6xSmXADAH99B5yM4o+1OB2AKY 0xFmlqH9m1FXyk+m7GTvpNSSzh/98vmrCioLIS1ndQKHW/Ha7rmBrKgo3smz/F+W YJPKNO1520pmYGubGMN3CKQrQt+PF8k7W47qkdvDoz+7VUptQZlcdRhCh+FiVXth 4fTKa2WYhkucJjra5hDy =G8fp -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: python-pymetar Source-Version: 1.2-0.1 Done: Mattia Rizzolo We believe that the bug you reported is fixed in the latest version of python-pymetar, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 835...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated python-pymetar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 16 Feb 2021 19:13:34 +0100 Source: python-pymetar Binary: python3-pymetar Architecture: source all Version: 1.2-0.1 Distribution: unstable Urgency: low Maintainer: Uli Martens Changed-By: Mattia Rizzolo Description: python3-pymetar - Python interface to METAR reports Closes: 835340 938076 Changes: python-pymetar (1.2-0.1) unstable; urgency=low . * Non-maintainer upload. . [ gregor herrmann ] * New upstream release. - Fixes "http://weather.noaa.gov/ no longer available" (Closes: #835340) - Update .docs file to renamed/removed documents. * The new upstream release is (only) python3 compatible: - Change package name and related helper files to python3-pymetar. - Breaks/Replaces old python-pymetar. - Update build system to use --buildsystem=pybuild --with=python3. - Update build dependencies. - Depend on ca-certificates for the new default METAR URL. - Fixes "Python2 removal in sid/bullseye". (Closes: #938076) * Move Homepage field
Bug#982984: marked as done (Mirror blocked due to repeated errors)
Your message dated Wed, 03 Mar 2021 21:48:37 + with message-id and subject line Bug#982984: fixed in apt-cacher-ng 3.6.2-1 has caused the Debian Bug report #982984, regarding Mirror blocked due to repeated errors to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt-cacher-ng Version: 3.6-1 Severity: normal I have a fairly generic apt-cacher-ng configuration that I use for sbuild. (The only configuration I've changed is to add BindAddress: localhost and change the Debian backend to https://deb.debian.org/debian/) Relatively recently I've noticed sbuild update failing with some regularity with the following error: source:buster-i386-sbuild: Performing update. Err:1 http://localhost:3142/debian buster InRelease 502 Mirror blocked due to repeated errors [IP: ::1 3142] Restarting apt-cacher-ng clears up this problem and then sbuild update works as normal. This might (or might not; it happens a few minutes earlier than this error) be correlated with the following error message: Feb 17 09:17:16 gwaihir apt-cacher-ng[833]: [warn] Call to getaddrinfo_async with no evdns_base configured. Feb 17 09:17:19 gwaihir apt-cacher-ng[833]: [warn] Call to getaddrinfo_async with no evdns_base configured. Feb 17 09:17:21 gwaihir apt-cacher-ng[833]: [warn] Call to getaddrinfo_async with no evdns_base configured. It's more strongly correlated with this error that's logged in /var/log/apt-cacher-ng/apt-cacher.err: Mon Feb 15 09:19:50 2021|Failure to create replacement of debrep/dists/stretch/InRelease - CHECK FOLDER PERMISSIONS! Mon Feb 15 09:19:50 2021|Failure to create replacement of debrep/dists/stretch/Release - CHECK FOLDER PERMISSIONS! There doesn't seem to be anything odd about the permissions of those directories under /var/cache/apt-cacher-ng. They're all owned by apt-cacher-ng:apt-cacher-ng and are mode 2755. Probably related, temporary working files seem to be left behind in /var/cache/apt-cacher-ng/debrep/dists sometimes (but not for every occurence of this error): buster: InRelease InRelease.head InRelease1613585303 contrib/ main/ non-free/ sid: InRelease InRelease.head contrib/ main/ non-free/ These files, when they appear, are zero-length. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/12 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 apt-cacher-ng depends on: ii adduser 3.118 ii debconf [debconf-2.0]1.5.74 ii dpkg 1.20.7.1 ii libbz2-1.0 1.0.8-4 ii libc62.31-9 ii libevent-2.1-7 2.1.12-stable-1 ii libevent-pthreads-2.1-7 2.1.12-stable-1 ii libgcc-s110.2.1-6 ii liblzma5 5.2.5-1.0 ii libssl1.11.1.1i-3 ii libstdc++6 10.2.1-6 ii libsystemd0 247.3-1 ii libwrap0 7.6.q-31 ii lsb-base 11.1.0 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages apt-cacher-ng recommends: ii ca-certificates 20210119 Versions of packages apt-cacher-ng suggests: pn avahi-daemon pn doc-base ii libfuse2 2.9.9-3 -- Configuration Files: /etc/apt-cacher-ng/security.conf [Errno 13] Permission denied: '/etc/apt-cacher-ng/security.conf' -- debconf information: apt-cacher-ng/cachedir: keep apt-cacher-ng/proxy: keep apt-cacher-ng/port: keep apt-cacher-ng/bindaddress: keep * apt-cacher-ng/tunnelenable: false apt-cacher-ng/gentargetmode: No automated setup --- End Message --- --- Begin Message --- Source: apt-cacher-ng Source-Version: 3.6.2-1 Done: Eduard Bloch We believe that the bug you reported is fixed in the latest version of apt-cacher-ng, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eduard Bloch (supplier of updated apt-cacher-ng
Bug#975155: marked as done (structure-synth: FTBFS: SyntopiaCore/GLEngine/Raytracer/AtomicCounter.h:28:35: error: ‘ULONG_MAX’ was not declared in this scope)
Your message dated Wed, 03 Mar 2021 21:21:03 +
with message-id
and subject line Bug#975155: fixed in structure-synth 1.5.0-7
has caused the Debian Bug report #975155,
regarding structure-synth: FTBFS:
SyntopiaCore/GLEngine/Raytracer/AtomicCounter.h:28:35: error: ‘ULONG_MAX’ was
not declared in this scope
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
975155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: structure-synth
Version: 1.5.0-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -DDATADIR=\"/usr/share/structure-synth\" -I. -I.
> -I/usr/include/x86_64-linux-gnu/qt5
> -I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui
> -I/usr/include/x86_64-linux-gnu/qt5/QtXml
> -I/usr/include/x86_64-linux-gnu/qt5/QtScript
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I.
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o AtomicCounter.o
> SyntopiaCore/GLEngine/Raytracer/AtomicCounter.cpp
> In file included from SyntopiaCore/GLEngine/Raytracer/AtomicCounter.cpp:1:
> SyntopiaCore/GLEngine/Raytracer/AtomicCounter.h:28:35: error: ‘ULONG_MAX’ was
> not declared in this scope
>28 |bool wait(unsigned long time = ULONG_MAX) { wcm.lock(); bool w =
> wc.wait(,time); wcm.unlock(); return w; }
> | ^
> SyntopiaCore/GLEngine/Raytracer/AtomicCounter.h:5:1: note: ‘ULONG_MAX’ is
> defined in header ‘’; did you forget to ‘#include ’?
> 4 | #include
> +++ |+#include
> 5 |
> make[1]: *** [Makefile:1317: AtomicCounter.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/11/19/structure-synth_1.5.0-6_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: structure-synth
Source-Version: 1.5.0-7
Done: Miriam Ruiz
We believe that the bug you reported is fixed in the latest version of
structure-synth, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 975...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Miriam Ruiz (supplier of updated structure-synth package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 03 Mar 2021 21:35:47 +0100
Source: structure-synth
Architecture: source
Version: 1.5.0-7
Distribution: unstable
Urgency: medium
Maintainer: Miriam Ruiz
Changed-By: Miriam Ruiz
Closes: 975155
Changes:
structure-synth (1.5.0-7) unstable; urgency=medium
.
* Added patch include_climits.patch to fix FTCBFS. Closes: #975155
* Upgraded Standards-Version from 4.4.0.1 to 4.5.1.0
Checksums-Sha1:
f9854a5bf216def4ab9791007b3e194b506606ae 2069 structure-synth_1.5.0-7.dsc
8e31273cb2d03f64e7a4e1b75de4f643dc84c892 23652
structure-synth_1.5.0-7.debian.tar.bz2
f8a9f28844040ae80f2aa9b11a46537c37d55971 10287
structure-synth_1.5.0-7_amd64.buildinfo
Checksums-Sha256:
4ac3b0053418c740d07a77c84a4d7bda8155e2a139d1190b9249f21ee83217af 2069
structure-synth_1.5.0-7.dsc
b2a694da34b07006d2251b4d79f0131ecaa1508af942fd29ffe76912fb1e466a 23652
structure-synth_1.5.0-7.debian.tar.bz2
05744a5467f9fb0cebaf9f1b26a1ae24323456bc8fc5736303586cc694d90b1c 10287
structure-synth_1.5.0-7_amd64.buildinfo
Files:
9d9c64ca3ccbf6a75f7ef7ecfb593427 2069 graphics optional
structure-synth_1.5.0-7.dsc
0066ce98b0da449004279a2901ba769f 23652 graphics optional
structure-synth_1.5.0-7.debian.tar.bz2
Bug#984463: recollgui: missing Breaks+Replaces: recollcmd (<< 1.28)
Package: recollgui Version: 1.28.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../5-recollgui_1.28.5-1_amd64.deb ... Unpacking recollgui (1.28.5-1) over (1.24.3-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-EVss6r/5-recollgui_1.28.5-1_amd64.deb (--unpack): trying to overwrite '/usr/share/recoll/doc/docbook-xsl.css', which is also in package recollcmd 1.24.3-3 Preparing to unpack .../6-recollcmd_1.28.5-1_amd64.deb ... Unpacking recollcmd (1.28.5-1) over (1.24.3-3) ... Errors were encountered while processing: /tmp/apt-dpkg-install-EVss6r/5-recollgui_1.28.5-1_amd64.deb cheers, Andreas recollgui_1.28.5-1.log.gz Description: application/gzip
Bug#983913: [Pkg-puppet-devel] Bug#983913: puppet-master, puppet-master-passenger: depends on unavailable puppet-server
On 3/3/21 11:06 AM, Andreas Beckmann wrote: > Package: puppet-master,puppet-master-passenger > Version: 6.16.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed puppet-master*/experimental is not > installable due to an unsatisfiable dependency on puppet-server > > > Cheers, > > Andreas Hi Andreas, This is a well known issue, done on purpose. We have the intention to package puppet-server, unfortunately, we're currently stuck on packaging jruby (it has problems). This is also the reason why the package lives in Experimental. Cheers, Thomas Goirand (zigo)
Bug#982730: marked as done (freedict: FTBFS: xsltCopyText: text allocation failed)
Your message dated Wed, 03 Mar 2021 20:33:38 + with message-id and subject line Bug#982730: fixed in freedict 2021.01.05-3 has caused the Debian Bug report #982730, regarding freedict: FTBFS: xsltCopyText: text allocation failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freedict Version: 2021.01.05-1.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210213 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/jpn-deu' > mkdir -p build/tei/ > /usr/share/freedict/teiaddphonetics -o build/tei/jpn-deu-phonetics.tei > jpn-deu.tei > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > hun-eng: Processed 4 of 139935 entries (29%). > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > hun-eng: Processed 45000 of 139935 entries (32%). > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > hun-eng: Processed 5 of 139935 entries (36%). > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > hun-eng: Processed 55000 of 139935 entries (39%). > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > deu-eng: Processed 135000 of 463244 entries (29%). > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > eng-deu: Processed 13 of 408553 entries (32%). > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > hun-eng: Processed 6 of 139935 entries (43%). > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > hun-eng: Processed 65000 of 139935 entries (46%). > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > hun-eng: Processed 7 of 139935 entries (50%). > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > deu-eng: Processed 14 of 463244 entries (30%). > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > Platform dictd supports this dictionary module. > xsltproc --novalid --xinclude --stringparam dictname jpn-deu --path > /<>/jpn-deu/ /usr/share/freedict/xsl/tei2c5.xsl > build/tei/jpn-deu-phonetics.tei >build/dictd/jpn-deu.c5 > eng-deu: Processed 135000 of 408553 entries (33%). > jpn-deu: Processed 5000 of 109546 entries (5%). > hun-eng: Processed 75000 of 139935 entries (54%). > jpn-deu: Processed 1 of 109546 entries (9%). > jpn-deu: Processed 15000 of 109546 entries (14%). > hun-eng: Processed 8 of 139935 entries (57%). > jpn-deu: Processed 2 of 109546 entries (18%). > hun-eng: Processed 85000 of 139935 entries (61%). > deu-eng: Processed 145000 of
Bug#975124: marked as done (dogecoin: FTBFS: qt/trafficgraphwidget.cpp:53:9: error: invalid use of incomplete type ‘class QPainterPath’)
Your message dated Wed, 03 Mar 2021 20:33:25 + with message-id and subject line Bug#975124: fixed in dogecoin 1.14.3-1 has caused the Debian Bug report #975124, regarding dogecoin: FTBFS: qt/trafficgraphwidget.cpp:53:9: error: invalid use of incomplete type ‘class QPainterPath’ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 975124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dogecoin Version: 1.14.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201119 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -std=c++11 -DHAVE_CONFIG_H -I. -I../src/config -U_FORTIFY_SOURCE > -D_FORTIFY_SOURCE=2 -I. -I./obj -pthread -I/usr/include -I./leveldb/include > -I./leveldb/helpers/memenv -I./secp256k1/include -I./univalue/include > -I./qt -I./qt -I./qt/forms -I./qt/forms -DQT_NO_KEYWORDS -DQT_NETWORK_LIB > -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB > -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork > -I/usr/include/x86_64-linux-gnu/qt5 > -I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport > -I/usr/include/x86_64-linux-gnu/qt5 > -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets > -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtGui > -I/usr/include/x86_64-linux-gnu/qt5 > -I/usr/include/x86_64-linux-gnu/qt5/QtCore > -I/usr/include/x86_64-linux-gnu/qt5 -DQT_DBUS_LIB -DQT_CORE_LIB > -I/usr/include/x86_64-linux-gnu/qt5/QtDBus > -I/usr/include/x86_64-linux-gnu/qt5 > -I/usr/include/x86_64-linux-gnu/qt5/QtCore > -I/usr/include/x86_64-linux-gnu/qt5 -pthread -Wdate-time -D_FORTIFY_SOURCE=2 > -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS -Wstack-protector > -fstack-protector-all -fPIC -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o > qt/libdogecoinqt_a-trafficgraphwidget.o `test -f 'qt/trafficgraphwidget.cpp' > || echo './'`qt/trafficgraphwidget.cpp > qt/trafficgraphwidget.cpp: In member function ‘void > TrafficGraphWidget::paintPath(QPainterPath&, QQueue&)’: > qt/trafficgraphwidget.cpp:53:9: error: invalid use of incomplete type ‘class > QPainterPath’ >53 | path.moveTo(x, YMARGIN + h); > | ^~~~ > In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qbrush.h:49, > from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpalette.h:46, > from > /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:48, > from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1, > from qt/trafficgraphwidget.h:8, > from qt/trafficgraphwidget.cpp:5: > /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix.h:54:7: note: forward > declaration of ‘class QPainterPath’ >54 | class QPainterPath; > | ^~~~ > qt/trafficgraphwidget.cpp:57:13: error: invalid use of incomplete type ‘class > QPainterPath’ >57 | path.lineTo(x, y); > | ^~~~ > In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qbrush.h:49, > from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpalette.h:46, > from > /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:48, > from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1, > from qt/trafficgraphwidget.h:8, > from qt/trafficgraphwidget.cpp:5: > /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix.h:54:7: note: forward > declaration of ‘class QPainterPath’ >54 | class QPainterPath; > | ^~~~ > qt/trafficgraphwidget.cpp:59:9: error: invalid use of incomplete type ‘class > QPainterPath’ >59 | path.lineTo(x, YMARGIN + h); > | ^~~~ > In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qbrush.h:49, > from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpalette.h:46, > from > /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:48, > from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1, > from qt/trafficgraphwidget.h:8, > from qt/trafficgraphwidget.cpp:5: > /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix.h:54:7: note: forward > declaration of ‘class QPainterPath’ >54 | class QPainterPath; > | ^~~~ > qt/trafficgraphwidget.cpp: In member function ‘virtual void >
Bug#984438: marked as done (questionable dependency on python3-pip)
Your message dated Wed, 03 Mar 2021 20:20:27 + with message-id and subject line Bug#984438: fixed in gnumed-client 1.8.5+dfsg-2 has caused the Debian Bug report #984438, regarding questionable dependency on python3-pip to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gnumed-client Version: 1.8.5+dfsg-1 Severity: serious Tags: sid bullseye gnumed-client depends on python3-pip. Why? The only use is in external-tools/check-prerequisites.py trying to download the pysvg module last updated in 2012, and not ported to Python3 ... Just drop that dependency, port the library, and package it. Please don't encourage downloading third party code for a package in main. --- End Message --- --- Begin Message --- Source: gnumed-client Source-Version: 1.8.5+dfsg-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of gnumed-client, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated gnumed-client package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Mar 2021 21:47:19 +0100 Source: gnumed-client Architecture: source Version: 1.8.5+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 984438 Changes: gnumed-client (1.8.5+dfsg-2) unstable; urgency=medium . * Drop python3-pip from Depends Closes: #984438 Checksums-Sha1: 5fc969bebd65bc83a422df171027cf050ba8efae 2372 gnumed-client_1.8.5+dfsg-2.dsc 138b14c3f857ae509f16949ce5b0b25fd980a653 78516 gnumed-client_1.8.5+dfsg-2.debian.tar.xz 80ad3e812f519a852b0cadb2911eafa0a175c46e 8249 gnumed-client_1.8.5+dfsg-2_amd64.buildinfo Checksums-Sha256: 42ec6d6c671c186ed01f3ce0e051dca8ea1b1538921ff10482635337490d4f3e 2372 gnumed-client_1.8.5+dfsg-2.dsc f31be41a8335f1f53282518723e2c5870a4494640116850308a0588e9f4b32b9 78516 gnumed-client_1.8.5+dfsg-2.debian.tar.xz b0311b82eab3b4c6c66d8e3be12e61c8e1437b126682fc8bedbfb9b76dd9aac4 8249 gnumed-client_1.8.5+dfsg-2_amd64.buildinfo Files: 428f421644e2a03d046fe4673dd942ec 2372 misc optional gnumed-client_1.8.5+dfsg-2.dsc 614964d3cdecb079e98a11cfc7f0467e 78516 misc optional gnumed-client_1.8.5+dfsg-2.debian.tar.xz 47ed2c22df34bfbb727cccb7739b436e 8249 misc optional gnumed-client_1.8.5+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmA/+LMRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGw6w/9G9HyYZVbIsy1qoEmFO9Nv+oDswOnTsbw UQUfwd7D/SZlVvVx6jL7320RKFM8JY3tTv1sflUISN3HmWhmVXn8PCF3urgWmsdD mnJ3/O3EQ97vwU+ciRxn58HffFD9PCh+wVBReiPP4rC56a1lrp+8Kgp6BdYanOLz LqTVu+UedS2FIILoAnosS4GyqwFTc029iKk+HsYXMoXYJHPrsP3iVm4eC0Xzd5on pm0fRCHKM54h4/oCl402VUIcLpHrFGCbXmmZJtPhjhFwdkmxTScmgd1nk0r6jhLK Vgru035UDj8elHuwcRAB/ZCUxE69/2Q/tviISmXUNSqp40YSVmV5XUmx0EM78HY5 S2z65XEscHZSpKEiokvFfED4rPAWQtc8vZSSmMu1ROhcLBHydp3FtdJMX7/BRkSD xjzVUUT/pMxCwC2cj1Xh4Xvpf4u6oFO5BjTsFJ08RufiDM4XKWR9ZWN3DdIWg+XB k1oNWOmlt1/Dho1oRVsKqrygEf/DFn3XRIFyafr1OT++1y9zFuS7Qba6aZerlo1i 3saAy8PHzllFBnqU2ix39GYjoDfu8BW14BtekwMcSadB67qnmu0p1RYpHMecTkeU RtXyy2BoJboWc7k8MCMY4kdV0S7JYjj6/0ZmgXfsLENynfgf++NfqlSXJqYQcmRb 8Th9gxRmyng= =w9zq -END PGP SIGNATURE End Message ---
Bug#982704: ofxstatement-plugins: FTBFS: TypeError: expected str, bytes or os.PathLike object, not NoneType
On Thu, 4 Mar 2021 00:27:17 +0500 Andrey Rahmatullin wrote: > On Sat, Feb 13, 2021 at 06:06:54PM +0100, Lucas Nussbaum wrote: > > > cd ofxstatement-be-argenta && python3 setup.py test > > > running test > > > [...] > > > File > > > "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line > > > 1379, in __init__ self.module_path = > > > os.path.dirname(getattr(module, '__file__', '')) File > > > "/usr/lib/python3.9/posixpath.py", line 152, in dirname p = > > > os.fspath(p) TypeError: expected str, bytes or os.PathLike > > > object, not NoneType make[1]: *** [debian/rules:32: > > > plugin_test_ofxstatement-be-argenta] Error 1 > So Python tries to find tests here and fails. I tried to debug why it > failes here but in ofxstatement-airbankcz and the difference seems to > be caused by unittest.loader.TestLoader._find_test_path() finding > ofxstatement/__init__.py here but not in ofxstatement-airbankcz. I'll > leave this at this point to someone more familiar with test discovery, > namespaces and packages. Yep, failed to quickly solve this issue too. I think I just had to turn off test discovery for ofxstatement-be-argenta. Will fix it later this week. -- Best regards, Alexander Gerasiov Contacts: e-mail: a...@gerasiov.net WWW: https://gerasiov.net TG/Skype: gerasiov PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1
Bug#984438: questionable dependency on python3-pip
Am Wed, Mar 03, 2021 at 08:33:57PM +0100 schrieb Matthias Klose: > >> gnumed-client depends on python3-pip. Why? > >> > >> The only use is in external-tools/check-prerequisites.py trying to > >> download the > >> pysvg module last updated in 2012, and not ported to Python3 ... > > > > The helper script external-tools/check-prerequisites.py > > certainly does not do anything obnoxious like "trying to > > download the pysvg module". It merely tells the user how to > > retrieve the proper version thereof. > > well, then it can tell to install python3-pip as well. It now does, thanks for the suggestiong. > > Quite apart from that the dependency can safely be demoted to > > Recommends:, or even Suggests:, if the former is still > > coupling too tightly. > > just remove it, or package the dependency properly. Is there anything fundamentally, conceptually *wrong* (not just not recommendable) with Suggests: python3-pip ? Best, Karsten -- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
Bug#984438: questionable dependency on python3-pip
On 3/3/21 8:29 PM, Karsten Hilbert wrote: > Am Wed, Mar 03, 2021 at 07:49:29PM +0100 schrieb Matthias Klose: > >> gnumed-client depends on python3-pip. Why? >> >> The only use is in external-tools/check-prerequisites.py trying to download >> the >> pysvg module last updated in 2012, and not ported to Python3 ... > > The helper script external-tools/check-prerequisites.py > certainly does not do anything obnoxious like "trying to > download the pysvg module". It merely tells the user how to > retrieve the proper version thereof. well, then it can tell to install python3-pip as well. No need to have a hard dependency on that. > Quite apart from that the dependency can safely be demoted to > Recommends:, or even Suggests:, if the former is still > coupling too tightly. just remove it, or package the dependency properly. Matthias
Processed: Re: Bug#983702: voltron: Update package with new upstream release
Processing control commands: > retitle -1 Doesn't work with current werkzeug Bug #983702 [voltron] voltron: Update package with new upstream release Changed Bug title to 'Doesn't work with current werkzeug' from 'voltron: Update package with new upstream release'. > tags -1 + upstream fixed-upstream patch Bug #983702 [voltron] Doesn't work with current werkzeug Added tag(s) upstream, patch, and fixed-upstream. -- 983702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983702: voltron: Update package with new upstream release
Control: retitle -1 Doesn't work with current werkzeug COntrol: tags -1 + upstream fixed-upstream patch On Sun, Feb 28, 2021 at 05:52:23PM +0100, Thomas Nyberg wrote: > The reason seems to be that the debian testing packaged version of werkzeug is > 1.0.1 while the packaged version of voltran does not support it. There is a > commit in the upstream repo that solves this problem: > > > https://github.com/snare/voltron/commit/ba413dcbc1914c511d03e1d95f3663a91daf349a > > Unfortunately that commit is not included in an official release. I'm unsure > if > that is required for it to be packaged with debian. Regardless, the older > version does not work as packaged (though the required changes are admittedly > quite minor). Assuming this patch fixes the problem, the correct way will be to apply it to the current version and upload it. -- WBR, wRAR signature.asc Description: PGP signature
Processed: tagging 982712
Processing commands for cont...@bugs.debian.org: > tags 982712 + fixed-upstream Bug #982712 [src:tiledarray] tiledarray: FTBFS: gemm_helper.h:168:30: error: expected initializer before ‘const’ Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 982712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982704: ofxstatement-plugins: FTBFS: TypeError: expected str, bytes or os.PathLike object, not NoneType
On Sat, Feb 13, 2021 at 06:06:54PM +0100, Lucas Nussbaum wrote: > > cd ofxstatement-be-argenta && python3 setup.py test > > running test > > [...] > > File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line > > 1379, in __init__ > > self.module_path = os.path.dirname(getattr(module, '__file__', '')) > > File "/usr/lib/python3.9/posixpath.py", line 152, in dirname > > p = os.fspath(p) > > TypeError: expected str, bytes or os.PathLike object, not NoneType > > make[1]: *** [debian/rules:32: plugin_test_ofxstatement-be-argenta] Error 1 So Python tries to find tests here and fails. I tried to debug why it failes here but in ofxstatement-airbankcz and the difference seems to be caused by unittest.loader.TestLoader._find_test_path() finding ofxstatement/__init__.py here but not in ofxstatement-airbankcz. I'll leave this at this point to someone more familiar with test discovery, namespaces and packages. -- WBR, wRAR signature.asc Description: PGP signature
Bug#984438: questionable dependency on python3-pip
Am Wed, Mar 03, 2021 at 07:49:29PM +0100 schrieb Matthias Klose: > gnumed-client depends on python3-pip. Why? > > The only use is in external-tools/check-prerequisites.py trying to download > the > pysvg module last updated in 2012, and not ported to Python3 ... The helper script external-tools/check-prerequisites.py certainly does not do anything obnoxious like "trying to download the pysvg module". It merely tells the user how to retrieve the proper version thereof. Quite apart from that the dependency can safely be demoted to Recommends:, or even Suggests:, if the former is still coupling too tightly. Thanks, Karsten (upstream) -- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
Bug#982712: tiledarray: FTBFS: gemm_helper.h:168:30: error: expected initializer before ‘const’
Control: -1 fixed-upstream Looks like this was caused by an update of libmadness-dev. Feel free to reassign this RC bug there, as it broke API compatibility when updated from 0.10.1~gite4aa500e-10.1 to 0.10.1+git20200818.eee5fd9f-1: now #defines "MADNESS_RESTRICT" instead of "restrict". This seems to be fixed upstream at https://github.com/ValeevGroup/tiledarray/commit/dbb665cb5e400aeebc39be12d015981078eff72b -- WBR, wRAR signature.asc Description: PGP signature
Bug#984439: netgen: FTBFS on armhf (unaligned access on arm64 kernel)
Source: netgen Version: 6.2.2006+really6.2.1905+dfsg-2 Severity: serious Hello, looks like the package FTBFS on armhf with an arm64 kernel. See e.g. builds from reproducible-builds.org https://tests.reproducible-builds.org/debian/logs/unstable/armhf/netgen_6.2.2006+really6.2.1905+dfsg-2.build2.log.gz Can you please have a look? thanks Gianfranco
Bug#983924: GitLab 13.7.7: ERROR in 1:0 Module parse failed: Unexpected character '' (1:0)
Hi Praveen, On Mi 03 Mär 2021 15:38:46 CET, Pirate Praveen wrote: On 2021, മാർച്ച് 3 7:54:13 PM IST, Mike Gabriel wrote: Package: gitlab Version: 13.7.7-2~fto10+1 Severity: serious Hi Praveen, I can't upgrade gitlab from 13.4.7-2~fto10+1, I get the below error messages (webpack and ttf fonts). Don't wonder about the /srv/gitlab paths, I have symlinked /var/lib/gitlab to /srv/gitlab (which always worked in the past) for better storage management. Can you share output of /usr/share/gitlab/node_modules ? It should be pointing to /var/lib/gitlab/node_modules. It does. There was some changes in node_modules path to adapt to yarn 2.0 and node-modules plugin instead of yarn 1.0. Hmmm... How can I check this. If the symlink points to /var/lib/gitlab/node_modules, then everything is fine? Or are more checks required? So it may be due to wrong paths. Another thing you can check is versions of node-katex node-babel7 etc see if new versions of any node modules are available. apt list --upgradable | grep node This shows nothing to be upgradeable. Also make sure you have gitlab-apt-pin-preferences installed, which gives higher priority to required gitlab dependencies. gitlab-apt-pin-preferences is installed indeed. However, I see this when trying to update/dist-upgrade: root@snotra:~# LANG=C apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libgo13 libgumbo1 libjs-uglify linux-image-5.6.0-0.bpo.2-amd64 linux-image-5.8.0-0.bpo.2-amd64 node-arr-diff node-arr-flatten node-arr-union node-array-unique node-base node-bluebird node-cache-base node-class-utils node-collection-visit node-component-emitter node-concat-stream node-copy-descriptor node-css node-cyclist node-define-property node-expand-brackets node-extend-shallow node-extglob node-filename-regex node-flush-write-stream node-for-in node-for-own node-fragment-cache node-from2 node-get-value node-glob-base node-has-value node-has-values node-icss-replace-symbols node-is-dotfile node-is-equal-shallow node-is-extendable node-is-plain-object node-is-primitive node-lazy-cache node-map-cache node-map-visit node-mississippi node-mixin-deep node-node-uuid node-object-copy node-object-visit node-object.omit node-output-file-sync node-parallel-transform node-parse-glob node-pascalcase node-posix-character-classes node-regex-cache node-regex-not node-repeat-element node-set-getter node-set-value node-snapdragon node-static-extend node-stream-each node-to-object-path node-to-regex node-typedarray node-union-value node-unset-value node-use ruby-daemons ruby-delayed-job ruby-font-awesome-rails ruby-uglifier Use 'apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpHIWJcS2QjV.pgp Description: Digitale PGP-Signatur
Processed: Re: bug 913978: gnome-control-center is not accessible with Orca screenreader
Processing control commands: > tags -1 bullseye-ignore Bug #913978 [gnome-control-center] is not accessible with Orca screenreader Added tag(s) bullseye-ignore. -- 913978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913978: bug 913978: gnome-control-center is not accessible with Orca screenreader
Control: tags -1 bullseye-ignore Hi On 21-02-2021 22:15, Samuel Thibault wrote: > Paul Gevers, le sam. 06 févr. 2021 10:10:33 +0100, a ecrit: >> One release further. Can somebody, e.g. from the Debian Accessibility >> Team, please at least check if this is still an issue? If not, we can >> close the bug, if so, we can document it *again* [1] as I'm not >> expecting it to get fixed in these last months if it's not fixed already. > > I had a look, it looks like it is exactly in the same state as before: > having to press right arrow twice, having to use control-f then esc to > get back to the panel list (not able to select a result element with the > keyboard). So the same text would be needed. There's the same text as for the buster release. I'm marking this bug as bullseye-ignore. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#984438: questionable dependency on python3-pip
Package: src:gnumed-client Version: 1.8.5+dfsg-1 Severity: serious Tags: sid bullseye gnumed-client depends on python3-pip. Why? The only use is in external-tools/check-prerequisites.py trying to download the pysvg module last updated in 2012, and not ported to Python3 ... Just drop that dependency, port the library, and package it. Please don't encourage downloading third party code for a package in main.
Processed: commands
Processing commands for cont...@bugs.debian.org: > found 983365 4.4.21-1 Bug #983365 [linphone] linphone-desktop: chat messages There is no source info for the package 'linphone' at version '4.4.21-1' with architecture '' Unable to make a source version for version '4.4.21-1' Marked as found in versions 4.4.21-1. > found 983365 4.4.21-2 Bug #983365 [linphone] linphone-desktop: chat messages There is no source info for the package 'linphone' at version '4.4.21-2' with architecture '' Unable to make a source version for version '4.4.21-2' Marked as found in versions 4.4.21-2. > affects 983365 linphone-desktop Bug #983365 [linphone] linphone-desktop: chat messages Added indication that 983365 affects linphone-desktop > thanks Stopping processing here. Please contact me if you need assistance. -- 983365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983265: vorta: autopkgtest regression on armhf: test times out
Hi Nicholas On 03-03-2021 05:30, Nicholas D Steeves wrote: > The delta between 0.7.1-4 and 0.7.4+5 (cherry picked commits, future > 0.7.5) might reasonably be considered "medium"; although it solves a > *number* of RC bugs, and a lot of "million papercuts" user issues. > Consequently I believe that Debian bullseye should have 0.7.4+5. Ack > Would you please advise me how to proceed with something like a > checklist before contacting the release-team? As your package isn't a key package and has a functional non-trivial autopkgtest, you don't need to contact the release team until the full freeze as the soft freeze rules count for you until then [1]. Please *do* follow all other rules. Paul [1] https://release.debian.org/bullseye/freeze_policy.html#hard OpenPGP_signature Description: OpenPGP digital signature
Bug#983924: GitLab 13.7.7: ERROR in 1:0 Module parse failed: Unexpected character '' (1:0)
Package: gitlab Version: 13.7.7-2~fto10+1 Severity: serious Hi Praveen, I can't upgrade gitlab from 13.4.7-2~fto10+1, I get the below error messages (webpack and ttf fonts). Don't wonder about the /srv/gitlab paths, I have symlinked /var/lib/gitlab to /srv/gitlab (which always worked in the past) for better storage management. Greets, Mike ``` [...] WARNING in ./editor/editor_lite.js 62:13-29 Critical dependency: the request of a dependency is an expression @ ./vue_shared/components/editor_lite.vue?vue=script=js& (/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./vue_shared/components/editor_lite.vue?vue=script=js&) @ ./vue_shared/components/editor_lite.vue?vue=script=js& @ ./vue_shared/components/editor_lite.vue @ /srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./snippets/components/snippet_blob_edit.vue?vue=script=js& @ ./snippets/components/snippet_blob_edit.vue?vue=script=js& @ ./snippets/components/snippet_blob_edit.vue @ /srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./snippets/components/snippet_blob_actions_edit.vue?vue=script=js& @ ./snippets/components/snippet_blob_actions_edit.vue?vue=script=js& @ ./snippets/components/snippet_blob_actions_edit.vue @ /srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./snippets/components/edit.vue?vue=script=js& @ ./snippets/components/edit.vue?vue=script=js& @ ./snippets/components/edit.vue @ ./snippet/snippet_edit.js @ ./pages/snippets/new/index.js @ multi ./main ./pages/snippets/new/index.js ERROR in /usr/share/gitlab/node_modules/katex/dist/fonts/KaTeX_Math-Italic.ttf 1:0 Module parse failed: Unexpected character '' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css (/srv/gitlab/node_modules/css-loader/dist/cjs.js??ref--9-1!/usr/share/gitlab/node_modules/katex/dist/katex.min.css) 36:42-82 @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css @ ./behaviors/markdown/render_math.js @ ./behaviors/markdown/render_gfm.js @ /srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./vue_shared/components/markdown/field.vue?vue=script=js& @ ./vue_shared/components/markdown/field.vue?vue=script=js& @ ./vue_shared/components/markdown/field.vue @ /srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./releases/components/app_edit_new.vue?vue=script=js& @ ./releases/components/app_edit_new.vue?vue=script=js& @ ./releases/components/app_edit_new.vue @ ./releases/mount_new.js @ ./pages/projects/releases/new/index.js @ multi ./main ./pages/projects/index.js ./pages/projects/releases/new/index.js ERROR in /usr/share/gitlab/node_modules/katex/dist/fonts/KaTeX_AMS-Regular.ttf 1:0 Module parse failed: Unexpected character '' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css (/srv/gitlab/node_modules/css-loader/dist/cjs.js??ref--9-1!/usr/share/gitlab/node_modules/katex/dist/katex.min.css) 6:41-81 @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css @ ./behaviors/markdown/render_math.js @ ./behaviors/markdown/render_gfm.js @ /srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./vue_shared/components/markdown/field.vue?vue=script=js& @ ./vue_shared/components/markdown/field.vue?vue=script=js& @ ./vue_shared/components/markdown/field.vue @ /srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./releases/components/app_edit_new.vue?vue=script=js& @ ./releases/components/app_edit_new.vue?vue=script=js& @ ./releases/components/app_edit_new.vue @ ./releases/mount_new.js @ ./pages/projects/releases/new/index.js @ multi ./main ./pages/projects/index.js ./pages/projects/releases/new/index.js ERROR in /usr/share/gitlab/node_modules/katex/dist/fonts/KaTeX_Size4-Regular.ttf 1:0 Module parse failed: Unexpected character '' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css
Processed: python3-carquinyol: missing Breaks+Replaces: python-carquinyol
Processing control commands: > affects -1 + sucrose Bug #984430 [python3-carquinyol] python3-carquinyol: missing Breaks+Replaces: python-carquinyol Added indication that 984430 affects sucrose -- 984430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984430: python3-carquinyol: missing Breaks+Replaces: python-carquinyol
Package: python3-carquinyol Version: 0.118-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + sucrose Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-carquinyol_0.118-1_amd64.deb ... Unpacking python3-carquinyol (0.118-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-carquinyol_0.118-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/copy-from-journal', which is also in package python-carquinyol 0.112-1 Preparing to unpack .../sucrose_0.118-2_all.deb ... Unpacking sucrose (0.118-2) over (0.112-6) ... Errors were encountered while processing: /var/cache/apt/archives/python3-carquinyol_0.118-1_amd64.deb Since python-carquinyol does no longer exist, the Breaks+Replaces can be unversioned. cheers, Andreas sucrose_0.118-2.log.gz Description: application/gzip
Processed: [PATCH] Re: Bug#983365: linphone-desktop: chat messages
Processing control commands: > tag -1 + patch upstream - help Bug #983365 [linphone-desktop] linphone-desktop: chat messages Added tag(s) upstream and patch. Bug #983365 [linphone-desktop] linphone-desktop: chat messages Removed tag(s) help. > reassign -1 linphone Bug #983365 [linphone-desktop] linphone-desktop: chat messages Bug reassigned from package 'linphone-desktop' to 'linphone'. No longer marked as found in versions linphone-desktop/4.2.5-3. Ignoring request to alter fixed versions of bug #983365 to the same values previously set -- 983365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983365: [PATCH] Re: Bug#983365: linphone-desktop: chat messages
Control: tag -1 + patch upstream - help Control: reassign -1 linphone On Sun, Feb 28, 2021 at 11:07:31PM +0100, Bernhard Schmidt wrote: > an updated liblinphone has been uploaded to sid yesterday. Could you > please try liblinphone10 and liblinphone++10 from sid (4.4.21-2) and > report back? If it does not work you might need libsoci-core4.0 and > libsoci-sqlite3-4.0 from unstable as well (4.0.1-4). I finally found the bug: libsoci_sqlite3 sometimes returns string where liblinphone unconditionally expects int, long, double etc. which led to silent std::bad_cast exceptions. I can't say who is actually to blame (I feel soci should do that conversion already as it knows what type the user requested, or at least not throw silently), but the attached patches remedy the issue through some conditional string conversion and make chat history actually work again in the GUI. They should really have separated the sqlite3 database code better from the MySQL code. I put this in two separate patches to make it easier to remove the changes to the code for the legacy DB migration in case it causes problems. Regards, Dennis 0001-string-conversions.patch.gz Description: application/gzip 0002-string-conversions-legacydb.patch.gz Description: application/gzip
Processed: Re: dune-pdelab: FTBFS on arm64,ppc64el: segfaults during tests
Processing control commands: > retitle -1 dune-pdelab: FTBFS: segfaults during tests Bug #976499 [src:dune-pdelab] dune-pdelab: FTBFS on arm64,ppc64el: segfaults during tests Changed Bug title to 'dune-pdelab: FTBFS: segfaults during tests' from 'dune-pdelab: FTBFS on arm64,ppc64el: segfaults during tests'. -- 976499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976499: dune-pdelab: FTBFS on arm64,ppc64el: segfaults during tests
Followup-For: Bug #976499 Control: retitle -1 dune-pdelab: FTBFS: segfaults during tests I also observed a segfault trying to build the package on amd64: The following tests FAILED: 39 - testpk (SEGFAULT) Andreas
Bug#984115: wims-lti: modifies conffiles (policy 10.7.3): /etc/apache2/sites-available/wims-lti-django.conf-dist
Package: wims-lti Version: 0.4.4-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also https://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): 0m37.1s ERROR: FAIL: debsums reports modifications inside the chroot: /etc/apache2/sites-available/wims-lti-django.conf-dist The diff from the shipped to the installed version is = @@ -5,7 +5,7 @@ DocumentRoot "/var/lib/wims-lti" -ServerName SERVERNAME +ServerName Alias /static/ /var/lib/wims-lti/collected_static/ = What is happening in postinst? = ## create the distribution's configuration for Apache sed -i "s/SERVERNAME/$virtualHost/" $apacheConfDist ## copy it to Apache configuration if the file does not exist [ -f $apacheConf ] || cp $apacheConfDist $apacheConf = You probably want to use ucf here ... the following is completely untested: * ship the template as /usr/share/wims-lti/wims-lti-django.conf-dist * depend on ucf * update the maintainer scripts: = postinst configure = apacheConfDist=/usr/share/wims-lti/wims-lti-django.conf-dist sed "s/SERVERNAME/$virtualHost/" $apacheConfDist > $apacheConf.new ucf --debconf-ok $apacheConf.new $apacheConf rm -f $apacheConf.new ucfr $DPKG_MAINTSCRIPT_PACKAGE $apacheConf = = = postrm purge = apacheConf=/etc/apache2/sites-available/wims-lti-django.conf rm -f $apacheConf if which ucf >/dev/null; then ucf --purge $apacheConf fi if which ucfr >/dev/null; then ucfr --purge $DPKG_MAINTSCRIPT_PACKAGE $apacheConf fi = = * get rid of /etc/apache2/sites-available/wims-lti-django.conf-dist = preinst, before #DEBHELPER# = if [ "$1" = "upgrade" ] && dpkg --compare-versions "$2" lt-nl "0.4.4-4~" ; then if [ -f /etc/apache2/sites-available/wims-lti-django.conf-dist ]; then # undo modifications s.t. it can be removed by dpkg-maintscript-helper sed -i 's/ServerName .*/ServerName SERVERNAME/' /etc/apache2/sites-available/wims-lti-django.conf-dist fi fi = = = debian/wims-lti.maintscript = rm_conffile /etc/apache2/sites-available/wims-lti-django.conf-dist 0.4.4-4~ = = cheers, Andreas wims-lti_0.4.4-3.log.gz Description: application/gzip
Bug#983828: marked as done (libseqan3-dev: copyright file missing (policy 12.5))
Your message dated Wed, 03 Mar 2021 15:49:00 + with message-id and subject line Bug#983828: fixed in seqan3 3.0.2+ds-9 has caused the Debian Bug report #983828, regarding libseqan3-dev: copyright file missing (policy 12.5) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libseqan3-dev Version: 3.0.2+ds-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information >From the attached log (scroll to the bottom...): 0m18.1s ERROR: WARN: Inadequate results from running adequate! libseqan3-dev: missing-copyright-file /usr/share/doc/libseqan3-dev/copyright MISSING COPYRIGHT FILE: /usr/share/doc/libseqan3-dev/copyright # ls -lad /usr/share/doc/libseqan3-dev drwxr-xr-x 2 root root 80 Mar 1 18:03 /usr/share/doc/libseqan3-dev # ls -la /usr/share/doc/libseqan3-dev/ total 12 drwxr-xr-x 2 root root 80 Mar 1 18:03 . drwxr-xr-x 106 root root 2200 Mar 1 18:03 .. -rw-r--r-- 1 root root 2088 Jan 1 12:35 changelog.Debian.gz -rw-r--r-- 1 root root 7784 Oct 13 10:33 changelog.gz Cheers, Andreas libseqan3-dev_3.0.2+ds-8.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: seqan3 Source-Version: 3.0.2+ds-9 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of seqan3, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated seqan3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 02 Mar 2021 12:45:35 +0100 Source: seqan3 Architecture: source Version: 3.0.2+ds-9 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 983828 Changes: seqan3 (3.0.2+ds-9) unstable; urgency=medium . * Team upload. * Make sure copyright file will be shipped in binary package Closes: #983828 * Disable salsa-ci build for i386 Checksums-Sha1: 72429abe037e570c4af54c4c5d1266688ab98668 2512 seqan3_3.0.2+ds-9.dsc 6abb785157d16d044ec517863c1fa2df205183e8 10804 seqan3_3.0.2+ds-9.debian.tar.xz 6fa7e208214338dbb11a0fe20a5f02fd6b434a95 10420 seqan3_3.0.2+ds-9_amd64.buildinfo Checksums-Sha256: 40ac149a9795154af1468d3e3de73025fd1569471fe0fa45145744883e9737c6 2512 seqan3_3.0.2+ds-9.dsc aea61e50ecedbbd6edfed25a67e5b4dd1f0c6603c8b6eed6d140154e6c0b5f1b 10804 seqan3_3.0.2+ds-9.debian.tar.xz e665ad0e526f6efeb453328a452ff23a5e48a2455daa59a483d0906bf23dc231 10420 seqan3_3.0.2+ds-9_amd64.buildinfo Files: e6e6386db241630eacbaa2db98d30cfe 2512 science optional seqan3_3.0.2+ds-9.dsc 2673c37928317680ea213492cbb0be49 10804 science optional seqan3_3.0.2+ds-9.debian.tar.xz f0c044591e5c06a8820d25d9bd58284b 10420 science optional seqan3_3.0.2+ds-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmA/q/URHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEGzA//awymt8jQkgSsU/ApTc347vziCxdyCxbt ERvunOStAQoMo2P2tnitL24SOcHJ9H97BERyjkpIfLrJz6QoGUmsPyT//DjEuD8r 6C/yIuFX5XY9D/1JksfNzVx4JQAAdVOQ69i3qVbkSeUExRC3T+YJCKQ8UfruxY/G cLmQ4Wi/9bEwI2213OdMr8MsQ/Ye8n3bKtNxabf6A+s9fWxB9P+FY6WbOANzVW1q rUHjZ1fJwyCCUgVo/id+HyMKCOXavHAisFHhX391KM3rRaIVmR2dGBqj+FsL0hJA BVMm2NILwuMDwJ0jSes1cHLCxN0o1X1YwL1520uGpreA8e4oHGKF/xl6SZEz/7BX gyVYJ7v71xASDrazihcnFjbPpRc5/UlAaToCgUOmzTVGFZJfkc6J0ijFVgjFTsrw jYZskXq6bnM2uZz1v9zFJdjNWp96QGxHcGKj4AkETwJJCAhswzRJoQXvrO7eUn9g XneaYuZxqgNfk2KjLIrO+Z8D1iuidPe5UDrp8dMyEkBycZ2rrOWpP37E0hvYx3SK 9kaqqgZ7LWB3bswjtGtgokJvopneqqbiVJoErOK6AGBW3UowpIM0DUxP7CSV25kn +EayZ/bOKdYsGCiwGk+yMrb2sSrZjRWzPN8qzoaNjeRPzwPs6l5OG/f7rkPf6XnB cwLaFeTis6c= =e5hr -END PGP SIGNATURE End Message ---
Bug#983924: GitLab 13.7.7: ERROR in 1:0 Module parse failed: Unexpected character '' (1:0)
On 2021, മാർച്ച് 3 8:17:44 PM IST, Mike Gabriel wrote: >Hi Praveen, > >On Mi 03 Mär 2021 15:38:46 CET, Pirate Praveen wrote: > >> On 2021, മാർച്ച് 3 7:54:13 PM IST, Mike Gabriel >> wrote: >>> Package: gitlab >>> Version: 13.7.7-2~fto10+1 >>> Severity: serious >>> >>> Hi Praveen, >>> >>> I can't upgrade gitlab from 13.4.7-2~fto10+1, I get the below error >>> messages (webpack and ttf fonts). Don't wonder about the /srv/gitlab >>> paths, I have symlinked /var/lib/gitlab to /srv/gitlab (which always >>> worked in the past) for better storage management. >> >> Can you share output of /usr/share/gitlab/node_modules ? >> >> It should be pointing to /var/lib/gitlab/node_modules. > >It does. > >> There was some changes in node_modules path to adapt to yarn 2.0 and >> node-modules plugin instead of yarn 1.0. > >Hmmm... How can I check this. If the symlink points to >/var/lib/gitlab/node_modules, then everything is fine? Or are more >checks required? See if old directory /var/lib/gitlab/.node_modules is still present, if yes, that should be removed. If that does not fix, backup yarn.lock and truncate -s0 yarn.lock to regenerate it. Try manually running yarnpkg install (see /usr/lib/gitlab/scripts/rake-tasks.sh ) and webpack. Another think you can do is to remove node_modules and let yarnpkg recreate it. >> So it may be due to wrong paths. Another thing you can check is >> versions of node-katex node-babel7 etc see if new versions of any >> node modules are available. >> >> apt list --upgradable | grep node > >This shows nothing to be upgradeable. > >> Also make sure you have gitlab-apt-pin-preferences installed, which >> gives higher priority to required gitlab dependencies. > >gitlab-apt-pin-preferences is installed indeed. > > >However, I see this when trying to update/dist-upgrade: > >root@snotra:~# LANG=C apt-get dist-upgrade >Reading package lists... Done >Building dependency tree >Reading state information... Done >Calculating upgrade... Done >The following packages were automatically installed and are no longer >required: > libgo13 libgumbo1 libjs-uglify linux-image-5.6.0-0.bpo.2-amd64 > linux-image-5.8.0-0.bpo.2-amd64 node-arr-diff node-arr-flatten >node-arr-union > node-array-unique node-base node-bluebird node-cache-base node-class-utils > node-collection-visit node-component-emitter node-concat-stream >node-copy-descriptor > node-css node-cyclist node-define-property node-expand-brackets >node-extend-shallow > node-extglob node-filename-regex node-flush-write-stream >node-for-in node-for-own > node-fragment-cache node-from2 node-get-value node-glob-base >node-has-value node-has-values > node-icss-replace-symbols node-is-dotfile node-is-equal-shallow >node-is-extendable > node-is-plain-object node-is-primitive node-lazy-cache >node-map-cache node-map-visit > node-mississippi node-mixin-deep node-node-uuid node-object-copy >node-object-visit > node-object.omit node-output-file-sync node-parallel-transform >node-parse-glob > node-pascalcase node-posix-character-classes node-regex-cache node-regex-not > node-repeat-element node-set-getter node-set-value node-snapdragon >node-static-extend > node-stream-each node-to-object-path node-to-regex node-typedarray >node-union-value > node-unset-value node-use ruby-daemons ruby-delayed-job >ruby-font-awesome-rails > ruby-uglifier >Use 'apt autoremove' to remove them. These can be removed if you like.p >0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. >1 not fully installed or removed. >After this operation, 0 B of additional disk space will be used. >Do you want to continue? [Y/n] > > >Mike -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#983029: marked as done (lava: flaky autopkgtest: lava-server-gunicorn service is not active)
Your message dated Wed, 03 Mar 2021 15:03:41 + with message-id and subject line Bug#983029: fixed in lava 2020.12-2 has caused the Debian Bug report #983029, regarding lava: flaky autopkgtest: lava-server-gunicorn service is not active to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lava Version: 2020.12-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), Your package has an autopkgtest, great. However, it fails often (since around January on amd64 and arm64) [1]. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. I copied the output at the bottom of this report. Paul [1] https://ci.debian.net/packages/l/lava/testing/amd64/ https://ci.debian.net/data/autopkgtest/testing/amd64/l/lava/10400827/log.gz + cd /root + lava-server manage check System check identified no issues (0 silenced). + lava-server manage check --deploy SystemCheckError: System check identified some issues: ERRORS: lava services: lava-server-gunicorn service is not active. INFOS: debian pkg: 'lava-coordinator' not installed from a Debian package System check identified 2 issues (2 silenced). autopkgtest [12:35:59]: test management: ---] autopkgtest [12:35:59]: test management: - - - - - - - - - - results - - - - - - - - - - management FAIL non-zero exit status 1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: lava Source-Version: 2020.12-2 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of lava, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated lava package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Mar 2021 11:54:11 -0300 Source: lava Architecture: source Version: 2020.12-2 Distribution: unstable Urgency: medium Maintainer: Debian LAVA team Changed-By: Antonio Terceiro Closes: 983029 Changes: lava (2020.12-2) unstable; urgency=medium . * debian/rules: drop jquery.flot.canvas.js. This fixes gunicorn not starting due to the jquery.flot.canvas.js pointing to a missing file. The entire charts feature will not work, since lava upstream hasn't upgraded to flot 4. (Closes: #983029) Checksums-Sha1: ddfc8ca5b95bdd5282361c3776f30919038035b8 2950 lava_2020.12-2.dsc 038e61cb669b509e9f58613b195c86e890074226 91028 lava_2020.12-2.debian.tar.xz e4490a3552439e485356dee10cace71356637b61 10052 lava_2020.12-2_source.buildinfo Checksums-Sha256: fa6d27f7abd43a47ca7ea1ae5edd6449e67cf2d74e38a4b56c219c9d27c1c8f2 2950 lava_2020.12-2.dsc a5e7a16194803e9785c0614a8efe66003a4bd96dc219749565ada4f69259fb74 91028 lava_2020.12-2.debian.tar.xz 43582775378418501f5568e5914ac82506669f64f5bdba54a05bd4b8cbf86320 10052 lava_2020.12-2_source.buildinfo Files: b566507404ae570227f85643b1e168af 2950 net optional lava_2020.12-2.dsc 4eb02f8ddbe349605563a3352213e2ea 91028 net optional lava_2020.12-2.debian.tar.xz 6fae9f15d2920e44cb6d0b415a9f1539 10052 net optional lava_2020.12-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmA/o2UACgkQ/A2xu81G C963Ug/+I1qHv7r/AlxOGgeIyCE88ci2oe+RoH7hasAjepJbr1MJHJ7otHi5v6Te sjsfo2Mi3giIEj6o72uPeQSEAtAuzxTocZ0JV1cU6rOK27GGqdfDJUH+lMLXvoQx 8BBRO6uQqc4rO82CIghe06mtI9t54unDhLul3Kl2trTcAijka+GPZ0+Q7U4H8nQs FYZRQGEm3/ahtYJ/TGZY7DxSmpicoeQxrPcvuVYbnLgucB1x96a+qMy8FDETmrL3 nnvyE1Jlb5Wfm44wGaO5+8Fg2QOGIJezTqOa4Cubph4+6i7PqErjcBaFdaz08mH4 xEFYsDGESn9BisSs2kwwzE3AV8+S8eswx/VKav/EcZ0l4KjhfvrHnI5tIfCWhq+3 yYfjGKdAlNEuMf8l79x8o452WilMDxILaJXt/HtqbJlzJAJ3hkcMh6HuMspNtuSO
Bug#983924: GitLab 13.7.7: ERROR in 1:0 Module parse failed: Unexpected character '' (1:0)
On 2021, മാർച്ച് 3 7:54:13 PM IST, Mike Gabriel wrote: >Package: gitlab >Version: 13.7.7-2~fto10+1 >Severity: serious > >Hi Praveen, > >I can't upgrade gitlab from 13.4.7-2~fto10+1, I get the below error >messages (webpack and ttf fonts). Don't wonder about the /srv/gitlab >paths, I have symlinked /var/lib/gitlab to /srv/gitlab (which always >worked in the past) for better storage management. Can you share output of /usr/share/gitlab/node_modules ? It should be pointing to /var/lib/gitlab/node_modules. There was some changes in node_modules path to adapt to yarn 2.0 and node-modules plugin instead of yarn 1.0. So it may be due to wrong paths. Another thing you can check is versions of node-katex node-babel7 etc see if new versions of any node modules are available. apt list --upgradable | grep node Also make sure you have gitlab-apt-pin-preferences installed, which gives higher priority to required gitlab dependencies. >Greets, >Mike > >``` >[...] >WARNING in ./editor/editor_lite.js 62:13-29 >Critical dependency: the request of a dependency is an expression > @ ./vue_shared/components/editor_lite.vue?vue=script=js& >(/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./vue_shared/components/editor_lite.vue?vue=script=js&) > @ ./vue_shared/components/editor_lite.vue?vue=script=js& > @ ./vue_shared/components/editor_lite.vue > @ >/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./snippets/components/snippet_blob_edit.vue?vue=script=js& > @ ./snippets/components/snippet_blob_edit.vue?vue=script=js& > @ ./snippets/components/snippet_blob_edit.vue > @ >/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./snippets/components/snippet_blob_actions_edit.vue?vue=script=js& > @ >./snippets/components/snippet_blob_actions_edit.vue?vue=script=js& > @ ./snippets/components/snippet_blob_actions_edit.vue > @ >/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./snippets/components/edit.vue?vue=script=js& > @ ./snippets/components/edit.vue?vue=script=js& > @ ./snippets/components/edit.vue > @ ./snippet/snippet_edit.js > @ ./pages/snippets/new/index.js > @ multi ./main ./pages/snippets/new/index.js > >ERROR in >/usr/share/gitlab/node_modules/katex/dist/fonts/KaTeX_Math-Italic.ttf >1:0 >Module parse failed: Unexpected character '' (1:0) >You may need an appropriate loader to handle this file type, currently >no loaders are configured to process this file. See >https://webpack.js.org/concepts#loaders >(Source code omitted for this binary file) > @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css >(/srv/gitlab/node_modules/css-loader/dist/cjs.js??ref--9-1!/usr/share/gitlab/node_modules/katex/dist/katex.min.css) > >36:42-82 > @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css > @ ./behaviors/markdown/render_math.js > @ ./behaviors/markdown/render_gfm.js > @ >/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./vue_shared/components/markdown/field.vue?vue=script=js& > @ ./vue_shared/components/markdown/field.vue?vue=script=js& > @ ./vue_shared/components/markdown/field.vue > @ >/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./releases/components/app_edit_new.vue?vue=script=js& > @ ./releases/components/app_edit_new.vue?vue=script=js& > @ ./releases/components/app_edit_new.vue > @ ./releases/mount_new.js > @ ./pages/projects/releases/new/index.js > @ multi ./main ./pages/projects/index.js >./pages/projects/releases/new/index.js > >ERROR in >/usr/share/gitlab/node_modules/katex/dist/fonts/KaTeX_AMS-Regular.ttf >1:0 >Module parse failed: Unexpected character '' (1:0) >You may need an appropriate loader to handle this file type, currently >no loaders are configured to process this file. See >https://webpack.js.org/concepts#loaders >(Source code omitted for this binary file) > @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css >(/srv/gitlab/node_modules/css-loader/dist/cjs.js??ref--9-1!/usr/share/gitlab/node_modules/katex/dist/katex.min.css) > >6:41-81 > @ /usr/share/gitlab/node_modules/katex/dist/katex.min.css > @ ./behaviors/markdown/render_math.js > @ ./behaviors/markdown/render_gfm.js > @ >/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./vue_shared/components/markdown/field.vue?vue=script=js& > @ ./vue_shared/components/markdown/field.vue?vue=script=js& > @ ./vue_shared/components/markdown/field.vue > @ >/srv/gitlab/node_modules/babel-loader/lib??ref--1!/srv/gitlab/node_modules/vue-loader/lib??vue-loader-options!./releases/components/app_edit_new.vue?vue=script=js& > @
Bug#983183: marked as done (libpam-script: Wrong path for pam_script.so)
Your message dated Wed, 03 Mar 2021 13:18:32 + with message-id and subject line Bug#983183: fixed in libpam-script 1.1.9-5 has caused the Debian Bug report #983183, regarding libpam-script: Wrong path for pam_script.so to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-script Version: 1.1.9-4+b1 Severity: grave Tags: patch Justification: renders package unusable X-Debbugs-Cc: c2h...@web.de Dear Maintainer, after reinstalling my (FAI-driven) installation with bullseye (using stretch before and ignoring buster), I found that pam-script doesn't work anymore. /var/log/auth.log claims that: PAM unable to dlopen(pam_script.so): /lib/x86_64-linux-gnu/security/pam_script.so: Couldn't open Shared-Object-file: File or directory not found PAM adding faulty module: pam_script.so Your package contains the file, but it lives in a wrong directory (and for me there is no other file in there): /lib/security/pam_script.so all other pam_*.so files live in /lib/x86_64-linux-gnu/security/ and a simple ln -s /lib/security/pam_script.so /lib/x86_64-linux-gnu/security/pam_script.so made pam_script work again. I'm not knowing the details of PAM and pam_script, but I think simply moving the directory should be the right solution. Please fix it in the remaining bullseye-freeze. Thank you Christian Meyer -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/4 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpam-script depends on: ii libc6 2.31-9 ii libpam0g 1.4.0-4 libpam-script recommends no packages. libpam-script suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libpam-script Source-Version: 1.1.9-5 Done: Martijn van Brummelen We believe that the bug you reported is fixed in the latest version of libpam-script, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martijn van Brummelen (supplier of updated libpam-script package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Mar 2021 13:11:04 +0100 Source: libpam-script Binary: libpam-script libpam-script-dbgsym Architecture: source amd64 Version: 1.1.9-5 Distribution: unstable Urgency: medium Maintainer: Martijn van Brummelen Changed-By: Martijn van Brummelen Description: libpam-script - PAM module which allows executing a script Closes: 983183 Changes: libpam-script (1.1.9-5) unstable; urgency=medium . * change lib dir (closes: #983183) * Change compat level from 9 to 11. * Remove autotools-dev from dependency's. * Standards-Version to 4.5.1. * Change Vcs address. Checksums-Sha1: 1f4b7cfe06956be6bc676fa7e622e70d86006ffc 1960 libpam-script_1.1.9-5.dsc 82bf2400bad8673fdce88cfc5c220b3a3bc8d595 34890 libpam-script_1.1.9.orig.tar.gz a92ca4961081b007278581ff3b29d494568220e0 3572 libpam-script_1.1.9-5.debian.tar.xz 2a768e75a72cc0a38800b736eb28c79fabe5556b 11404 libpam-script-dbgsym_1.1.9-5_amd64.deb 909a0360e75b110ca77f00e1ff52289ee060ce97 6294 libpam-script_1.1.9-5_amd64.buildinfo 4c013d062db78be277a3e47fb2245afb1b921850 21068 libpam-script_1.1.9-5_amd64.deb Checksums-Sha256: 34961085414f561674750096ceadea52ea4b0362e4e11fb921df225882a579b3 1960 libpam-script_1.1.9-5.dsc 0aab103d318e3048ccc6f8285950f99284c814f996d2dcbcae8f10d3b8bd8cfe 34890 libpam-script_1.1.9.orig.tar.gz 774ee73afdea35f2e783098b137f84ed98ae1ec09e5db0c68231633ee395e684 3572 libpam-script_1.1.9-5.debian.tar.xz 4cb2ff17f1abc515a06639a591affe86292f3f19aaecbdf54d2278ddedb0cc09 11404 libpam-script-dbgsym_1.1.9-5_amd64.deb b25551903a72cf3f2b51ba96b94e33706939cd8559a52e2ee10827cdafc6f633 6294
Bug#983915: gitlab: fails to install: Could not find gem 'rugged (~> 0.28)'
On 2021, മാർച്ച് 3 4:20:32 PM IST, Andreas Beckmann wrote: >Package: gitlab >Version: 13.4.7-2 >Severity: serious >User: debian...@lists.debian.org >Usertags: piuparts > >Hi, > >during a test with piuparts I noticed your package failed to install. As >per definition of the release team this makes the package too buggy for >a release, thus the severity. > >From the attached log (scroll to the bottom...): > > Setting up gitlab (13.4.7-2) ... > fatal: not a git repository (or any of the parent directories): .git > fatal: not a git repository (or any of the parent directories): .git > [ESC][31mCould not find gem 'rugged (~> 0.28)' in any of the gem sources > listed in your > Gemfile.[ESC][0m This is a known issue. We are not yet able to make gitlab work with rugged 1.1 in the archive. A license compatibility issue delayed the upstream update (reverse-markdown in the dependency chain is licensed under wtfpl which was not OK for gitlab initially, and this issue is now resolved). This is tracked in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979563 Hopefully we will see a fix soon. For now, work around is to use rugged 0.28 from snapshot.debian.org See https://wiki.debian.org/gitlab#Experimental_-_During_freeze_and_transitions > dpkg: error processing package gitlab (--configure): > installed gitlab package post-installation script subprocess returned error > exit status 1 > Processing triggers for ca-certificates (20210119) ... > Updating certificates in /etc/ssl/certs... > 0 added, 0 removed; done. > Running hooks in /etc/ca-certificates/update.d... > done. > Errors were encountered while processing: > gitlab > > >cheers, > >Andreas -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#983920: dgit-test-dummy: intentionally uninstallable package
Andreas Beckmann writes ("Bug#983920: dgit-test-dummy: intentionally
uninstallable package"):
> This bug is just for letting piuparts know that we know that the package is
> uninstallable ;-)
Haha :-). Thanks for your QA work.
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Bug#975215: marked as done (cif2cell: FTBFS: test failed)
Your message dated Wed, 03 Mar 2021 12:03:24 +
with message-id
and subject line Bug#975215: fixed in cif2cell 2.0.0a1+dfsg-4
has caused the Debian Bug report #975215,
regarding cif2cell: FTBFS: test failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
975215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cif2cell
Version: 2.0.0a1+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. pytest-3
> = test session starts
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>
> collected 7 items
>
> tests/test_cif2cell.py FFF
> [100%]
>
> === FAILURES
> ===
> _ test_parse[/<>/tests/../cifs/gamma-Pu.cif] _
>
> cif_file = '/<>/tests/../cifs/gamma-Pu.cif'
>
> @pytest.mark.skipif(sys.version_info < (3, 6), reason="requires python3.6
> or higher")
> @pytest.mark.parametrize("cif_file", CIF_FILES)
> def test_parse(cif_file):
> """Test running cif2cell on each CIF file in /cifs."""
> if sys.version_info < (3,0) and 'SiC.cif' in cif_file:
> pytest.skip(reason='skip test for files with unicode content
> under python 2.7.' +
>'see https://github.com/torbjornbjorkman/cif2cell/issues/7')
>
> > result = run_cif2cell([cif_file])
>
> tests/test_cif2cell.py:23:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> tests/test_cif2cell.py:13: in run_cif2cell
> return subprocess.check_output(['./binaries/cif2cell'] + args,
> stderr=subprocess.STDOUT).decode('utf8')
> /usr/lib/python3.9/subprocess.py:420: in check_output
> return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> input = None, capture_output = False, timeout = None, check = True
> popenargs = (['./binaries/cif2cell',
> '/<>/tests/../cifs/gamma-Pu.cif'],)
> kwargs = {'stderr': -2, 'stdout': -1}
> process = '/<>/...>
> stdout = b'Traceback (most recent call last):\n File
> "/<>/./binaries/cif2cell", line ...m fractions import
> gcd\nImportError: cannot import name \'gcd\' from \'fractions\'
> (/usr/lib/python3.9/fractions.py)\n'
> stderr = None, retcode = 1
>
> def run(*popenargs,
> input=None, capture_output=False, timeout=None, check=False,
> **kwargs):
> """Run command with arguments and return a CompletedProcess instance.
>
> The returned instance will have attributes args, returncode, stdout
> and
> stderr. By default, stdout and stderr are not captured, and those
> attributes
> will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture
> them.
>
> If check is True and the exit code was non-zero, it raises a
> CalledProcessError. The CalledProcessError object will have the
> return code
> in the returncode attribute, and output & stderr attributes if those
> streams
> were captured.
>
> If timeout is given, and the process takes too long, a TimeoutExpired
> exception will be raised.
>
> There is an optional argument "input", allowing you to
> pass bytes or a string to the subprocess's stdin. If you use this
> argument
> you may not also use the Popen constructor's "stdin" argument, as
> it will be used internally.
>
> By default, all communication is in bytes, and therefore any "input"
> should
> be bytes, and the stdout and stderr will be bytes. If in text mode,
> any
> "input" should be a string, and stdout and stderr will be strings
> decoded
> according to locale encoding, or by "encoding" if set. Text mode is
> triggered by setting any of text, encoding, errors or
> universal_newlines.
>
> The other arguments are the same as for the Popen constructor.
> """
> if input is not None:
> if kwargs.get('stdin') is not None:
> raise ValueError('stdin and input arguments may not both be
> used.')
> kwargs['stdin'] = PIPE
>
> if
Processed: reopening 846653, reassign 846653 to src:mysql-8.0, reopening 845649 ..., reopening 793504 ...
Processing commands for cont...@bugs.debian.org:
> # these bugs could be relevant for mysql-8.0, too
> reopen 846653
Bug #846653 {Done: Debian FTP Masters }
[mysql-client-core-5.7] mention how to read the history file, .mysql_history
Warning: Unknown package 'mysql-client-core-5.7'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
Warning: Unknown package 'mysql-client-core-5.7'
Warning: Unknown package 'mysql-client-core-5.7'
No longer marked as fixed in versions 5.7.26-1+rm.
Warning: Unknown package 'mysql-client-core-5.7'
> reassign 846653 src:mysql-8.0
Bug #846653 [mysql-client-core-5.7] mention how to read the history file,
.mysql_history
Warning: Unknown package 'mysql-client-core-5.7'
Bug reassigned from package 'mysql-client-core-5.7' to 'src:mysql-8.0'.
No longer marked as found in versions mysql-5.7/5.7.16-1.
Ignoring request to alter fixed versions of bug #846653 to the same values
previously set
> reopen 845649
Bug #845649 {Done: Debian FTP Masters }
[mysql-client-core-5.7] man page: mysql [options] db_name, FILES
Warning: Unknown package 'mysql-client-core-5.7'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
Warning: Unknown package 'mysql-client-core-5.7'
Warning: Unknown package 'mysql-client-core-5.7'
No longer marked as fixed in versions 5.7.26-1+rm.
Warning: Unknown package 'mysql-client-core-5.7'
> reassign 845649 src:mysql-8.0
Bug #845649 [mysql-client-core-5.7] man page: mysql [options] db_name, FILES
Warning: Unknown package 'mysql-client-core-5.7'
Bug reassigned from package 'mysql-client-core-5.7' to 'src:mysql-8.0'.
No longer marked as found in versions mysql-5.7/5.7.16-2.
Ignoring request to alter fixed versions of bug #845649 to the same values
previously set
> reopen 793504
Bug #793504 {Done: Debian FTP Masters }
[src:mysql-5.7] sysbench dep8 test
Warning: Unknown package 'src:mysql-5.7'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
Warning: Unknown package 'src:mysql-5.7'
Warning: Unknown package 'src:mysql-5.7'
No longer marked as fixed in versions 5.7.26-1+rm.
Warning: Unknown package 'src:mysql-5.7'
> reassign 793504 src:mysql-8.0
Bug #793504 [src:mysql-5.7] sysbench dep8 test
Warning: Unknown package 'src:mysql-5.7'
Bug reassigned from package 'src:mysql-5.7' to 'src:mysql-8.0'.
Ignoring request to alter found versions of bug #793504 to the same values
previously set
Ignoring request to alter fixed versions of bug #793504 to the same values
previously set
> reopen 914272
Bug #914272 {Done: Debian FTP Masters }
[mysql-5.7] mysql-5.7: [INTL:tr] turkish translation update
Warning: Unknown package 'mysql-5.7'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
Warning: Unknown package 'mysql-5.7'
Warning: Unknown package 'mysql-5.7'
No longer marked as fixed in versions 5.7.26-1+rm.
Warning: Unknown package 'mysql-5.7'
> reassign 914272 src:mysql-8.0
Bug #914272 [mysql-5.7] mysql-5.7: [INTL:tr] turkish translation update
Warning: Unknown package 'mysql-5.7'
Bug reassigned from package 'mysql-5.7' to 'src:mysql-8.0'.
Ignoring request to alter found versions of bug #914272 to the same values
previously set
Ignoring request to alter fixed versions of bug #914272 to the same values
previously set
> reopen 923065
Bug #923065 {Done: Debian FTP Masters }
[mysql-5.7] [INTL:da] Danish translation of the debconf templates mysql-5.7
Warning: Unknown package 'mysql-5.7'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
Warning: Unknown package 'mysql-5.7'
Warning: Unknown package 'mysql-5.7'
No longer marked as fixed in versions 5.7.26-1+rm.
Warning: Unknown package 'mysql-5.7'
> reassign 923065 src:mysql-8.0
Bug #923065 [mysql-5.7] [INTL:da] Danish translation of the debconf templates
mysql-5.7
Warning: Unknown package 'mysql-5.7'
Bug reassigned from package 'mysql-5.7' to 'src:mysql-8.0'.
Ignoring request to alter found versions of bug #923065 to the same values
previously set
Ignoring request to alter fixed versions of bug #923065 to the same values
previously set
> reopen 918576
Bug #918576 {Done: Debian FTP Masters }
[mysql-client-core-5.7] MySQL Reference Manual may be installed locally
Warning: Unknown package 'mysql-client-core-5.7'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
Warning: Unknown package 'mysql-client-core-5.7'
Warning: Unknown package 'mysql-client-core-5.7'
No longer marked as fixed in versions 5.7.26-1+rm.
Warning:
Bug#983748: marked as done (dh-r: pkg-r-autopkgtest breaks autopkgtests)
Your message dated Wed, 03 Mar 2021 11:33:25 + with message-id and subject line Bug#983748: fixed in dh-r 20210303 has caused the Debian Bug report #983748, regarding dh-r: pkg-r-autopkgtest breaks autopkgtests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dh-r Version: 20210218 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: issue Hi Maintainer The recent upload of dh-r causes autopkgtests using pkg-r-autopkgtest to fail. See for example the output of r-bioc-affy [1] below. Presumably caused by this commit [2]. grep: debian/*.substvars: No such file or directory E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? autopkgtest [06:13:16]: test pkg-r-autopkgtest: ---] autopkgtest [06:13:16]: test pkg-r-autopkgtest: - - - - - - - - - - results - - - - - - - - - - pkg-r-autopkgtestFAIL non-zero exit status 100 Regards Graham [1] https://ci.debian.net/packages/r/r-bioc-affy/testing/amd64/ [2] https://salsa.debian.org/r-pkg-team/dh-r/-/commit/62a4128c07a17de845e9d7260504fae187c3d193 --- End Message --- --- Begin Message --- Source: dh-r Source-Version: 20210303 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of dh-r, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated dh-r package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Mar 2021 12:16:32 +0100 Source: dh-r Architecture: source Version: 20210303 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 983748 Changes: dh-r (20210303) unstable; urgency=medium . * Do not try to run apt in autopkgtest-pkg-r Closes: #983748 Checksums-Sha1: 481b1a9fa3c14a82a40a46adff9ef538ce7983e7 1738 dh-r_20210303.dsc 0482bc39f92fcd7ac74fbc7ca7400c3322516ca0 40268 dh-r_20210303.tar.xz 18ba1612744056ea6174fb91c4d56fbd824b5b23 5829 dh-r_20210303_amd64.buildinfo Checksums-Sha256: 12c33d4e36e30ef6bfd5aea3a45a006f2c11c0594914104d6ff34a3d91ffe56c 1738 dh-r_20210303.dsc 70df8c4f5830f29420877ffe7375720ee94cda5d6cf2e86c56aa846d3a1dd434 40268 dh-r_20210303.tar.xz 07b89de46fb835543f84f24753f53bf3b7583afa5bcaf4914ad8f5971540adbd 5829 dh-r_20210303_amd64.buildinfo Files: 19ff71c0a1897604bfa060d4be4aa9ac 1738 science optional dh-r_20210303.dsc f54c296cc70758afc8f2c579c6c78780 40268 science optional dh-r_20210303.tar.xz d7e8bf188f03dc73c09e095b61b820ee 5829 science optional dh-r_20210303_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmA/cEkRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGZ9w//d6kMxjehX5NA+dwK6KHnJmqY/6u2zxat 8pSRgmVF3Q/mDMoZ5Fr5xs/S1Rvalkj8t0M/6h/GnHbccLuNfrukQCVJgMXe+VxW GmzDABssosCqrRs3J0C83Ubwr9Ek43/AlnDM6fFQuFE4xZSCj6aJqwK8YKuKXW3d hhb1s9CP4iciEmE4y1IfWxZcjXMw3tHJHF0NQ6itw/1+wSAQA/0dD0NV8wg3ermM 9lMSkN/g7O+VLnNs6fyt+cyWZUiyf77Q+2iSzRA0XQNNm7g3WyB5Ylhh/olnjXBb 1AOi8eBOsfkNyYZuAVhDWElbHOI4QUg+OeSXY6Rl35saK64DRnKehye47MdKux4s HuyX+AQmZVbceKoZkQgj62fpA83txX05DD0gBsXzehT6QLXfRrLPUeCsZB/Sn5BY pauoTz3lBxPSwufIzix6t3t+8rbZoGh36LNjMiXzqBSiK3HexGOZYBzmgU3Z23xj ot2Cd/hZPHHqwfWE5y/GO7k2vDBBnS2JWT/SuxW9htK8IgQxt8P8/DhhsPcAI8+6 FW/YhxsdJSL02ApPVKA21+rh+LetOnZZ/I5ajiNqBk8qG0JG4AIwMS3eIIxixZgB klsE27uO82pip2phXz+U91v4rGlxDtVQcgkzBYaqChHmzjbglFmcrmSI1xddJiSY 2K1a3Y6FFkU= =OFqX -END PGP SIGNATURE End Message ---
Processed: user debian...@lists.debian.org, usertagging 979388 ..., usertagging 925340
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 979388 piuparts There were no usertags set. Usertags are now: piuparts. > reassign 925340 nvidia-legacy-304xx-kernel-dkms 304.137-8 Bug #925340 [src:nvidia-graphics-drivers-legacy-304xx] nvidia-graphics-drivers-legacy-304xx: does not support Linux 5.0 or newer Bug reassigned from package 'src:nvidia-graphics-drivers-legacy-304xx' to 'nvidia-legacy-304xx-kernel-dkms'. No longer marked as found in versions nvidia-graphics-drivers-legacy-304xx/304.137-7. Ignoring request to alter fixed versions of bug #925340 to the same values previously set Bug #925340 [nvidia-legacy-304xx-kernel-dkms] nvidia-graphics-drivers-legacy-304xx: does not support Linux 5.0 or newer Marked as found in versions nvidia-graphics-drivers-legacy-304xx/304.137-8. > usertags 925340 piuparts There were no usertags set. Usertags are now: piuparts. > thanks Stopping processing here. Please contact me if you need assistance. -- 925340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests
Hi Graham, On Wed, Mar 03, 2021 at 12:44:34PM +0200, Graham Inggs wrote: > Hi Andreas > > On Wed, 3 Mar 2021 at 12:12, Andreas Tille wrote: > > My motivation for the change was that for > > example in r-bioc-mutationalpatterns (see bug #983027) the > > autopkgtest-pkg-r script failed to install all needed packages > > to run its test. This was not the only package that was affected. > > This sounds like #961138. Yes. I admit I failed noticing this totally since I'm relying on my autopkgtest pbuilder hook ... which is run as root. :-( > > I'd like to discuss this quickly whether I'm again on the wrong track. > > In my opinion, dh-r 20210301 with the commit [1] reverted should be OK > for bullseye. We should be able to see the effect in unstable soon > after your upload. Done. > > The effect would be that *a few* tests in r-bioc- packages will become > > superfluid but that should be bearable for the moment. > > What about skipping pkg-r-autopkgtest on the few affected packages? That's a maintenance burden since our clever tools keep on re-injecting it if its missing. > We would lose a lot of test coverage if you disabled it everywhere. > Let's hear opinions from the rest of the team. I think by just droping[1] it should work without my drastical suggestion. So I uploaded according to your suggestion and added a hint to TODO for the remaining packages to install. I tested r-bioc-mutationalpatterns which motivated me to the change and it passes the tests. I repeat that it was not a clever move to do [1] in that stage of the release. :-( :-( Kind regards Andreas. > [1] > https://salsa.debian.org/r-pkg-team/dh-r/-/commit/62a4128c07a17de845e9d7260504fae187c3d193 > > ___ > R-pkg-team mailing list > r-pkg-t...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team > -- http://fam-tille.de
Bug#983920: dgit-test-dummy: intentionally uninstallable package
Package: dgit-test-dummy Version: 1.31 Severity: serious Tags: wontfix User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. [...] This bug is just for letting piuparts know that we know that the package is uninstallable ;-) cheers, Andreas
Bug#983917: gnome-weather: Fails to get forecast data
Package: gnome-weather Version: 3.36.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, Gnome Weather fails to get forecast data. After entering a location the app shows the message: "Forecast data not available" This happens with every location tried: New York, New York, United States of America; London, Greater London, United Kingdom; and others. This is the terminal output: ``` $ gnome-weather GWeather-Message: 11:51:16.849: Failed to get Yr.no forecast data: 404 Not Found GWeather-Message: 11:51:16.862: Failed to get Yr.no forecast data: 404 Not Found ``` -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-weather depends on: ii dconf-gsettings-backend [gsettings-backend] 0.38.0-2 ii geoclue-2.0 2.5.7-2 ii gir1.2-gdkpixbuf-2.0 2.42.2+dfsg-1 ii gir1.2-geoclue-2.0 2.5.7-2 ii gir1.2-geocodeglib-1.0 3.26.2-2 ii gir1.2-glib-2.0 1.66.1-1+b1 ii gir1.2-gnomedesktop-3.0 3.38.4-1 ii gir1.2-gtk-3.0 3.24.24-3 ii gir1.2-gweather-3.0 3.36.1-1 ii gjs 1.66.2-1 ii libglib2.0-bin 2.66.7-1 gnome-weather recommends no packages. gnome-weather suggests no packages.
Bug#983379: linux uml segfault
On 03/03/2021 10:45, Ritesh Raj Sarraf wrote:
HI Anton,
On Wed, 2021-03-03 at 09:30 +, Anton Ivanov wrote:
OTOH, I have one more user (other than you) who's not been able to
reproduce the issue.
I will do a dissect the moment I figure out how to reproduce it.
I
will try to do some more experiments on that tomorrow.
I tried to alter the userspace a bit, but it makes no difference.
Out of curiosity, what are you running it on?
Bare-metal machines. 3 different machines, all Intel processors.
And it fails on all 3 of them.
Hmmm...
All mine are AMD. I can try to boot up an Intel later today with Bullseye to
see if it makes a difference.
On the distribution side, all 3 of them run Debian Unstable, with Linux
5.10.13
The code here is:
static inline u32 printk_caller_id(void)
{
return in_task() ? task_pid_nr(current) :
0x8000 + raw_smp_processor_id();
}
That is something which should not bomb out unless we have memory
corruption or something along those lines - current being invalid.
Must be something different. Not all machines could have bad memory at
the same time.
I did not mean bad memory. I meant memory corruption as a result of race,
buffer overrun or anything else like that.
--
Anton R. Ivanov
https://www.kot-begemot.co.uk/
Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests
Hi Andreas On Wed, 3 Mar 2021 at 12:12, Andreas Tille wrote: > My motivation for the change was that for > example in r-bioc-mutationalpatterns (see bug #983027) the > autopkgtest-pkg-r script failed to install all needed packages > to run its test. This was not the only package that was affected. This sounds like #961138. > I'd like to discuss this quickly whether I'm again on the wrong track. In my opinion, dh-r 20210301 with the commit [1] reverted should be OK for bullseye. We should be able to see the effect in unstable soon after your upload. > The effect would be that *a few* tests in r-bioc- packages will become > superfluid but that should be bearable for the moment. What about skipping pkg-r-autopkgtest on the few affected packages? We would lose a lot of test coverage if you disabled it everywhere. Let's hear opinions from the rest of the team. Regards Graham [1] https://salsa.debian.org/r-pkg-team/dh-r/-/commit/62a4128c07a17de845e9d7260504fae187c3d193
Bug#983379: linux uml segfault
HI Anton,
On Wed, 2021-03-03 at 09:30 +, Anton Ivanov wrote:
>
> >
> > OTOH, I have one more user (other than you) who's not been able to
> > reproduce the issue.
> >
> > > I will do a dissect the moment I figure out how to reproduce it.
> > > I
> > > will try to do some more experiments on that tomorrow.
>
> I tried to alter the userspace a bit, but it makes no difference.
>
> Out of curiosity, what are you running it on?
>
Bare-metal machines. 3 different machines, all Intel processors.
And it fails on all 3 of them.
On the distribution side, all 3 of them run Debian Unstable, with Linux
5.10.13
> >
>
> The code here is:
>
> static inline u32 printk_caller_id(void)
> {
> return in_task() ? task_pid_nr(current) :
> 0x8000 + raw_smp_processor_id();
> }
>
>
> That is something which should not bomb out unless we have memory
> corruption or something along those lines - current being invalid.
>
Must be something different. Not all machines could have bad memory at
the same time.
--
Given the large number of mailing lists I follow, I request you to CC
me in replies for quicker response
signature.asc
Description: This is a digitally signed message part
Bug#972936: libgcc-s1 needs Breaks: libgcc1 (<< 1:10)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964477#69 now claims this is gone with the removal of gcc-8
Bug#983478: Bug#981513: courier: please replace fam with gamin
On 03.03.21 09:21, Glenn Strauss wrote: If there is any remaining concern about upgrade compatibility, ..none from my side. Courier would simply depend on gamin only. I don't see why that would cause issues during upgrades. In Bullseye, change the fam package to import the gamin source, and then bump the fam package version number. The fam package would actually be the same as gamin, and upgrades would avoid any packaging system deficiencies in choosing between gamin and fam for upgrade. That sounds very confusing and outright wrong, IMO. What's wrong with just dropping fam? (Whether right now for Bullseye or at any later point in time...) Regards Markus
Bug#983393: marked as done (gcc-10: Segmentation fault when building mkvtoolnix)
Your message dated Wed, 3 Mar 2021 11:20:41 +0100 with message-id and subject line fixed in 10.2.1-20 has caused the Debian Bug report #983393, regarding gcc-10: Segmentation fault when building mkvtoolnix to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcc-10 Version: 10.2.1-6 Severity: serious Dear Maintainer, Since the beginning of february gcc is unable to build mkvtoolnix. https://buildd.debian.org/status/fetch.php?pkg=mkvtoolnix=amd64=53.0.0-2=1612639953=0 Christian -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.17 (SMP w/24 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gcc-10 depends on: ii binutils 2.35.2-2 ii cpp-10 10.2.1-6 ii gcc-10-base10.2.1-6 ii libc6 2.31-9 ii libcc1-0 10.2.1-6 ii libgcc-10-dev 10.2.1-6 ii libgcc-s1 10.2.1-6 ii libgmp10 2:6.2.1+dfsg-1 ii libisl23 0.23-1 ii libmpc31.2.0-1 ii libmpfr6 4.1.0-3 ii libstdc++6 10.2.1-6 ii libzstd1 1.4.8+dfsg-2 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages gcc-10 recommends: ii libc6-dev 2.31-9 Versions of packages gcc-10 suggests: pn gcc-10-doc pn gcc-10-locales pn gcc-10-multilib -- no debconf information --- End Message --- --- Begin Message --- Version: 10.2.1-20--- End Message ---
Bug#983910: rpcsvc-proto: uninstallable due to Conflicts: libc6
On 03/03/2021 10.33, Aurelien Jarno wrote: See the changelog. This is done on purpose until we can actually schedule the transition. I just needed a bug number to automatically flag the uninstallable package in piuparts ;-) Andreas
Bug#983478: Bug#981513: courier: please replace fam with gamin
On 03.03.21 09:01, Glenn Strauss wrote: I did the research in #510368 and #966273, reviewing the actual code and confidentally concluded that FAM can be removed from Bullseye. Thanks for this research. I read through both issues and don't question the general reasoning. However, I clearly do not want to needlessly change this forth and back, as I already did once. If fam stays in Bullseye, I think it's better to have courier build against libfam-dev. Whether or not fam stays in Bullseye is up to the release team. The safest choice is to have a single library (gamin) used in the distro, rather than having both FAM and gamin. I'm actively using courier built against libfam-dev in combination with gamin. So that's known working as well. Fixing them requires trivial substitutions in debian/control I know, because I already did "fix" this once. Only to be asked to revert the change few days later. I'm not going to repeat that process. Let's have a clear decision, please. And then take action. So far I've read the release team had "decided that fam will stay in bullseye". If that's not true or revisited, I'm happy to adjust courier. Regards Markus
Bug#983748: dh-r: pkg-r-autopkgtest breaks autopkgtests
Hi Graham,
sorry for all the mess. My motivation for the change was that for
example in r-bioc-mutationalpatterns (see bug #983027) the
autopkgtest-pkg-r script failed to install all needed packages
to run its test. This was not the only package that was affected.
I perfectly agree that this was one of my worst ideas regarding
its timing.
My only instant solution right now is to make
https://salsa.debian.org/r-pkg-team/dh-r/-/blob/master/scripts/pkg-r-autopkgtest#L16
unconditional or just do
--- a/scripts/pkg-r-autopkgtest
+++ b/scripts/pkg-r-autopkgtest
@@ -11,6 +11,9 @@ bioc=$(grep-dctrl -s biocViews -n '' DESCRIPTION)
echo "Test: Try to load the R library ${pkgname}"
R --no-save -e "library('${pkgname}')"
+# Do not run any more detailed tests for the moment
+exit 0
+
##
# Test pkg-r-autopkgtest on Bioconductor packages only for now
if [ "$bioc" = "" ] ; then
I'd like to discuss this quickly whether I'm again on the wrong track.
The effect would be that *a few* tests in r-bioc- packages will become
superfluid but that should be bearable for the moment.
What do you think?
Kind regards
Andreas.
On Mon, Mar 01, 2021 at 04:50:10PM +0200, Graham Inggs wrote:
> Control: reopen -1
>
> Hi Andreas
>
> This didn't work [1]. You need root in order to run 'apt-get install':
>
> E: No packages found
> E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13:
> Permission denied)
> E: Unable to acquire the dpkg frontend lock
> (/var/lib/dpkg/lock-frontend), are you root?
> autopkgtest [14:31:55]: test pkg-r-autopkgtest: ---]
> autopkgtest [14:31:55]: test pkg-r-autopkgtest: - - - - - - - - - -
> results - - - - - - - - - -
> pkg-r-autopkgtestFAIL non-zero exit status 100
>
> Please revert the entire commit [2] and upload so we can fast track
> dh-r back into testing to fix pkg-r-autopkgtests there. Maybe speak
> to debci team about whatever problem it is you are trying to solve,
> and whether it is needed at this stage of the freeze.
>
> Regards
> Graham
>
>
> [1] https://ci.debian.net/packages/r/r-bioc-affy/unstable/amd64/
> [2]
> https://salsa.debian.org/r-pkg-team/dh-r/-/commit/62a4128c07a17de845e9d7260504fae187c3d193
>
> ___
> R-pkg-team mailing list
> r-pkg-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team
>
--
http://fam-tille.de
Bug#983913: puppet-master,puppet-master-passenger: depends on unavailable puppet-server
Package: puppet-master,puppet-master-passenger Version: 6.16.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed puppet-master*/experimental is not installable due to an unsatisfiable dependency on puppet-server Cheers, Andreas
Bug#983910: rpcsvc-proto: uninstallable due to Conflicts: libc6
On 2021-03-03 10:21, Andreas Beckmann wrote: > Package: rpcsvc-proto > Version: 1.4.2-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Package: rpcsvc-proto > Version: 1.4.2-1 > Architecture: amd64 > Depends: libc6 (>= 2.14) > Conflicts: libc6 > > That does not work. See the changelog. This is done on purpose until we can actually schedule the transition. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#983379: linux uml segfault
On 02/03/2021 17:27, Ritesh Raj Sarraf wrote:
On Tue, 2021-03-02 at 17:05 +, Anton Ivanov wrote:
So the best I can extract for you is to compile the kernel with as
much
information as possible.
Can you try using one of the older kernels so we can verify if this
is indeed a 5.10 thing.
That was the first thing I tried. I tested it with 5.10, 5.9 and 5.4.
All 3 crashed. That's when I knew this one was going to be painful one
to conclude.
The only other input I have is that I have one more user who's reported
to be able to reproduce the issue.
OTOH, I have one more user (other than you) who's not been able to
reproduce the issue.
I will do a dissect the moment I figure out how to reproduce it. I
will try to do some more experiments on that tomorrow.
I tried to alter the userspace a bit, but it makes no difference.
Out of curiosity, what are you running it on?
Meanwhile, I enabled some debug info in the kernel. Here's what I have
got so far:
```
(gdb) bt
#0 0x7f89908dc087 in kill () at ../sysdeps/unix/syscall-
template.S:120
#1 0x604a3514 in uml_abort () at arch/um/os-Linux/util.c:94
#2 0x604a3791 in os_dump_core () at arch/um/os-
Linux/util.c:149
#3 0x6048d126 in panic_exit (self=0x2e66d5, unused1=6,
unused2=0x0) at arch/um/kernel/um_arch.c:217
#4 0x604c725a in notifier_call_chain (nl=0x2e66d5, val=0,
v=0x60d82f40 , nr_to_call=-1, nr_calls=0x0) at
kernel/notifier.c:83
#5 0x604c72f6 in atomic_notifier_call_chain (nh=0x2e66d5,
val=6, v=0x0) at kernel/notifier.c:217
#6 0x60a54607 in panic (fmt=0x60a55225
"UH\211\345H\201\354", ) at
kernel/panic.c:272
#7 0x6048cca3 in segv (fi=, ip=1615717312,
is_user=0, regs=0x60c2ee58 ) at
arch/um/kernel/trap.c:246
#8 0x6048ce64 in segv_handler (sig=3040981, unused_si=0x6,
regs=0x60c2ee58 ) at arch/um/kernel/trap.c:190
#9 0x604a2556 in sig_handler_common (sig=11, si=0x60c2fbf0
, mc=0x60c2fae8 ) at
arch/um/os-Linux/signal.c:48
#10 0x604a2aa2 in sig_handler (sig=3040981, si=0x6, mc=0x0) at
arch/um/os-Linux/signal.c:81
#11 0x604a265f in hard_handler (sig=3040981, si=0x60c2fbf0
, p=0x0) at arch/um/os-Linux/signal.c:180
#12
The code here is:
static inline u32 printk_caller_id(void)
{
return in_task() ? task_pid_nr(current) :
0x8000 + raw_smp_processor_id();
}
That is something which should not bomb out unless we have memory corruption or
something along those lines - current being invalid.
A.
#13 0x604de3c0 in printk_caller_id () at
kernel/printk/printk.c:1924
#14 log_output (text_len=, text=,
dev_info=, lflags=, level=, facility=) at kernel/printk/printk.c:1932
#15 vprintk_store (facility=1624806843, level=5, dev_info=0x0, fmt=0x35
, args=0x1) at
kernel/printk/printk.c:2004
#16 0x604de8b7 in vprintk_emit (facility=1624806843,
level=1622768673, dev_info=0x35, fmt=0x1 , args=0x60b97c22) at kernel/printk/printk.c:2029
#17 0x604debad in vprintk_deferred (fmt=0x1 , args=0x60b97c21) at
kernel/printk/printk.c:3079
#18 0x60a554de in printk_deferred (fmt=0x60d895bb
"\n") at kernel/printk/printk.c:3091
#19 0x6092680f in _warn_unseeded_randomness
(previous=, caller=, func_name=) at drivers/char/random.c:1534
#20 _warn_unseeded_randomness (func_name=0x60abf380 <__func__.38>
"get_random_u32", caller=0x608b5f25 ,
previous=0x35) at drivers/char/random.c:1516
#21 0x60927d47 in get_random_u32 () at
drivers/char/random.c:2221
#22 0x608b5f25 in bucket_table_alloc (nbuckets=64, gfp=3264,
ht=) at lib/rhashtable.c:203
#23 0x608b6733 in rhashtable_init (ht=0x60c60e30
, params=0x608b5e06 ) at
lib/rhashtable.c:1061
#24 0x6080f234 in ipc_init_ids (ids=0x60c60de8 )
at ipc/util.c:119
#25 0x60813c6d in sem_init_ns (ns=0x60d895bb ) at
ipc/sem.c:254
#26 0x60015b5d in sem_init () at ipc/sem.c:268
#27 0x7f89906d92f7 in ?? () from /lib/x86_64-linux-
gnu/libcom_err.so.2
#28 0x7f8990ab8fb2 in call_init (l=,
argc=argc@entry=5, argv=argv@entry=0x7ffe3e7a4c98,
env=env@entry=0x7ffe3e7a4cc8) at dl-init.c:72
#29 0x7f8990ab90b9 in call_init (env=0x7ffe3e7a4cc8,
argv=0x7ffe3e7a4c98, argc=5, l=) at dl-init.c:30
#30 _dl_init (main_map=0x61497ea0, argc=5, argv=0x7ffe3e7a4c98,
env=0x7ffe3e7a4cc8) at dl-init.c:119
#31 0x7f89909d82bd in __GI__dl_catch_exception
(exception=exception@entry=0x0, operate=operate@entry=0x7f8990abc5a0
, args=args@entry=0x7ffe3e7a1e80) at dl-error-
skeleton.c:182
#32 0x7f8990abd028 in dl_open_worker (a=a@entry=0x7ffe3e7a2020) at
dl-open.c:758
#33 0x7f89909d8260 in __GI__dl_catch_exception
(exception=exception@entry=0x7ffe3e7a2000,
operate=operate@entry=0x7f8990abcc70 ,
args=args@entry=0x7ffe3e7a2020) at dl-error-skeleton.c:208
#34 0x7f8990abc8ca in _dl_open (file=0x7ffe3e7a22a0
"libnss_nis.so.2", mode=-2147483646, caller_dlopen=0x7f89909bf3a6
, nsid=-2, argc=5, argv=0x7ffe3e7a2000,
env=0x7ffe3e7a4cc8)
at dl-open.c:837
Processed: user debian...@lists.debian.org, usertagging 941101, usertagging 947111, affects 947111 ...
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 941101 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 947111 piuparts There were no usertags set. Usertags are now: piuparts. > affects 947111 + python3-thinc Bug #947111 [src:python-thinc] python-thinc: FTBFS with Python 3.8 Added indication that 947111 affects python3-thinc > usertags 972023 piuparts Usertags were: piuparts. Usertags are now: piuparts. > affects 972023 + python3-enable Bug #972023 [src:python-enable] python-enable ftbfs with python3.9 as supported python3 version Bug #951888 [src:python-enable] python-enable FTBFS with swig 4.0.1 Added indication that 972023 affects python3-enable Added indication that 951888 affects python3-enable > usertags 964607 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 938432 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 938509 piuparts There were no usertags set. Usertags are now: piuparts. > affects 875184 + sofa-apps Bug #875184 [src:sofa-framework] [sofa-framework] Future Qt4 removal from Buster Added indication that 875184 affects sofa-apps > usertags 938516 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 943266 piuparts There were no usertags set. Usertags are now: piuparts. > severity 943266 serious Bug #943266 [src:xdeb] xdeb: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > usertags 978237 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 828550 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 640605 piuparts Usertags were: instest-20110825 instest. Usertags are now: piuparts instest-20110825 instest. > thanks Stopping processing here. Please contact me if you need assistance. -- 640605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640605 875184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875184 943266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943266 947111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947111 951888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951888 972023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983910: rpcsvc-proto: uninstallable due to Conflicts: libc6
Package: rpcsvc-proto Version: 1.4.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Package: rpcsvc-proto Version: 1.4.2-1 Architecture: amd64 Depends: libc6 (>= 2.14) Conflicts: libc6 That does not work. Andreas
Bug#983855: golang-github-coreos-bbolt-dev: fails to upgrade from 'buster': unable to install new version of '/usr/share/gocode/src/go.etcd.io/bbolt/allocate_test.go': No such file or directory
On 03/03/2021 00.48, Guillem Jover wrote: Ah! Ok good thing I had not done the unblock request. :) Attached a patch that I think fixes this issue, and also fixes a problem with the symlink loop detection. That fixes the upgrade failure I observed ;-) Andreas
Bug#983887: cyrus-imapd: missing Breaks+Replaces: cyrus-common (<< 3.2.3)
Le 03/03/2021 à 09:31, Andreas Beckmann a écrit : > On 03/03/2021 07.37, Yadd wrote: >> OK for Breaks, but why "Replaces" ? cyrus-common still exists, or is >> there something I didn't understand? > > Look at it the other way around: > > You are taking over a file owned by cyrus-common. That needs a Replaces, > otherwise you get the file owerwrite issue I observed. > If you have taken away the file, the old version of cyrus-common is > incomplete and thus you need the Breaks to ensure it does not serve as a > correctly installed package satisfying other packages dependencies. **) > > A Breaks alone would still allow apt/dpkg to > - deconfigure old cyrus-common > - unpack new cyrus-imapd => clash > - unpack new cyrus-common > > Andreas > > (The versioned dependency on cyrus-common you mentioned solves some > issues by requiring that cyrus-common gets upgraded as well, so you > can't end up with a broken cyrus-common where dpkg thinks it's correctly > installed.) > > **) Think of two theoretical packages foo and bar both shipping > /bin/foobar, where bar has Replaces: foo (but no Breaks/Conflicts or > other relationships). Then install foo, install bar, remove bar. foo is > still installed. Where is /bin/foobar? OK, thanks!
Bug#983887: cyrus-imapd: missing Breaks+Replaces: cyrus-common (<< 3.2.3)
On 03/03/2021 07.37, Yadd wrote: OK for Breaks, but why "Replaces" ? cyrus-common still exists, or is there something I didn't understand? Look at it the other way around: You are taking over a file owned by cyrus-common. That needs a Replaces, otherwise you get the file owerwrite issue I observed. If you have taken away the file, the old version of cyrus-common is incomplete and thus you need the Breaks to ensure it does not serve as a correctly installed package satisfying other packages dependencies. **) A Breaks alone would still allow apt/dpkg to - deconfigure old cyrus-common - unpack new cyrus-imapd => clash - unpack new cyrus-common Andreas (The versioned dependency on cyrus-common you mentioned solves some issues by requiring that cyrus-common gets upgraded as well, so you can't end up with a broken cyrus-common where dpkg thinks it's correctly installed.) **) Think of two theoretical packages foo and bar both shipping /bin/foobar, where bar has Replaces: foo (but no Breaks/Conflicts or other relationships). Then install foo, install bar, remove bar. foo is still installed. Where is /bin/foobar?
Bug#983478: Bug#981513: courier: please replace fam with gamin
If there is any remaining concern about upgrade compatibility, how about this: In Bullseye, change the fam package to import the gamin source, and then bump the fam package version number. The fam package would actually be the same as gamin, and upgrades would avoid any packaging system deficiencies in choosing between gamin and fam for upgrade.
Bug#983478: Bug#981513: courier: please replace fam with gamin
On Wed, Mar 03, 2021 at 08:06:57AM +0100, Markus Wanner wrote: > On 03.03.21 07:02, Glenn Strauss wrote: > > Please replace "libfam-dev" with "libgamin-dev" in debian/control > > > > Also, please replace "gamin | fam" with simply "gamin" for Bullseye. > > I just changed it forth and back. To change it again, we need some deeper > reasoning than just "please do". Are you claiming the initial information > given by Adrian Bunk in #983478 (which you're responding to) is wrong? I did the research in #510368 and #966273, reviewing the actual code and confidentally concluded that FAM can be removed from Bullseye. I am one of the developers of lighttpd and am intimately aware of the issues caused to end-users due to #510368 and symbol conflicts that it caused in lighttpd. The safest choice is to have a single library (gamin) used in the distro, rather than having both FAM and gamin. Two packages remaining in Bullseye with unnecessary dependencies on FAM: kcoreaddons and courier. Fixing them requires trivial substitutions in debian/control For kcoreaddons, I submitted: https://salsa.debian.org/qt-kde-team/kde/kcoreaddons/-/merge_requests/3 To Adrian: if courier and kcoreaddons s/libfam-dev/libgamin-dev/ and depend on gamin instead of on fam, then fam can be removed from Bullseye. For upgrades, fam should be removed, replaced by gamin since packages no longer declare dependencies on fam. Cheers, Glenn
