Bug#931519: 931519 resolved
On 29 January 2022 at 10:38, Paul Wise wrote: | Control: fixed -1 4.0.3 | | On Fri, 2022-01-28 at 20:07 -0600, Dirk Eddelbuettel wrote: | | > Per email by Graham from 14 Nov 2020 this has been resolved. | | Resolved upstream in 2020 but not in Debian until 2021. Correct. Graham (as author) and myself (as uploader) missed this bug report which answered (but did not close) ages ago. The package is great and in good shape. Been using it for months. Just wanted to get the migration blocker for the package taken care of. | > By now we have an even newer version 4.0.3. | | Please use a versioned -done message next time: | | https://www.debian.org/Bugs/Developer#closing Noted, thanks. Still not that fluent with these... Best, Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#990345: zookeeper: various security issues
Further for the records (for a future upgrade to newer ZK versions): There will likely need to be a NEWS.Debian entry about the following: https://issues.apache.org/jira/browse/ZOOKEEPER-3056 In short: - apparently they've added a check that prevents ZK from starting, when no snapshots were found in the dataDir - the workaround is to ONCE set snapshot.trust.empty=true (the zookeeper.snapshot.trust.empty=true mentioned in most messages of the bug does not work, which is mentioned in some later answers) - start up the server - remove the setting again quoting: "It is recommended to remove the property once you have a working server, because that check is important to ensure that the system is in good shape" Cheers, Chris.
Processed: 931519 resolved
Processing commands for cont...@bugs.debian.org:
> fixed 931519 4.0.3
Bug #931519 {Done: Dirk Eddelbuettel } [wajig] wajig:
upgradesecurity references testing/updates instead of testing-security
Ignoring request to alter fixed versions of bug #931519 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
931519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: 931519 resolved
Processing control commands:
> fixed -1 4.0.3
Bug #931519 {Done: Dirk Eddelbuettel } [wajig] wajig:
upgradesecurity references testing/updates instead of testing-security
Marked as fixed in versions wajig/4.0.3.
--
931519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#931519: 931519 resolved
Control: fixed -1 4.0.3 On Fri, 2022-01-28 at 20:07 -0600, Dirk Eddelbuettel wrote: > Per email by Graham from 14 Nov 2020 this has been resolved. Resolved upstream in 2020 but not in Debian until 2021. > By now we have an even newer version 4.0.3. Please use a versioned -done message next time: https://www.debian.org/Bugs/Developer#closing -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#931519: marked as done (wajig: upgradesecurity references testing/updates instead of testing-security)
Your message dated Fri, 28 Jan 2022 20:07:06 -0600
with message-id <25076.41290.269608.599...@rob.eddelbuettel.com>
and subject line 931519 resolved
has caused the Debian Bug report #931519,
regarding wajig: upgradesecurity references testing/updates instead of
testing-security
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.)
--
931519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wajig
Severity: normal
The wajig upgradesecurity command references testing/updates but with
bullseye that suite has been renamed to testing-security. Please update
the wajig upgradesecurity command.
src/commands.py-def upgradesecurity(args):
src/commands.py-"""Do a security upgrade"""
src/commands.py-sources_list = tempfile.mkstemp(".security", "wajig.",
"/tmp")[1]
src/commands.py-sources_file = open(sources_list, "w")
src/commands.py-# check dist
src/commands.py-sources_file.write("deb http://security.debian.org/ " +\
src/commands.py: "testing/updates main contrib
non-free\n")
src/commands.py-sources_file.close()
https://codesearch.debian.net/search?q=testing%2Fupdates+package%3Awajig
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Per email by Graham from 14 Nov 2020 this has been resolved.
By now we have an even newer version 4.0.3. This long-fixed bug should not
prevent migration to testing.
Dirk
--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org--- End Message ---
Bug#965431: bfbtester: diff for NMU version 2.0.1-7.2
Control: tags 965431 + patch Control: tags 965431 + pending Dear maintainer, I've prepared an NMU for bfbtester (versioned as 2.0.1-7.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer or cancel it. Regards, Eriberto diff -u bfbtester-2.0.1/debian/rules bfbtester-2.0.1/debian/rules --- bfbtester-2.0.1/debian/rules +++ bfbtester-2.0.1/debian/rules @@ -1,13 +1,4 @@ #!/usr/bin/make -f - -DEB_INSTALL_MANPAGES_bfbtester := debian/bfbtester.1 - -common-configure-impl:: - cd $(DEB_BUILDDIR); touch aclocal.m4 && touch Makefile.in && \ - touch src/Makefile.in && touch src/config.h.in && \ - touch src/bfbt/Makefile && touch configure - -include /usr/share/cdbs/1/class/autotools.mk -include /usr/share/cdbs/1/rules/debhelper.mk -include /usr/share/cdbs/1/rules/simple-patchsys.mk +%: + dh $@ diff -u bfbtester-2.0.1/debian/changelog bfbtester-2.0.1/debian/changelog --- bfbtester-2.0.1/debian/changelog +++ bfbtester-2.0.1/debian/changelog @@ -1,3 +1,20 @@ +bfbtester (2.0.1-7.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #965431 + * Dropped CDBS in favor of the debhelper to allow the build system to use +DH level greater than 11. Consequently: + - debian/control: removed no longer needed cdbs and autotools-dev from +Build-Depends field. + - debian/manpages: created to install the manpage. + - debian/rules: changed from CDBS to DH. + + -- Joao Eriberto Mota Filho Fri, 28 Jan 2022 22:14:01 -0300 + bfbtester (2.0.1-7.1) unstable; urgency=high * Non-maintainer upload. diff -u bfbtester-2.0.1/debian/control bfbtester-2.0.1/debian/control --- bfbtester-2.0.1/debian/control +++ bfbtester-2.0.1/debian/control @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Uwe Hermann -Build-Depends: cdbs, debhelper (>= 5), autotools-dev +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.7.2 Package: bfbtester reverted: --- bfbtester-2.0.1/debian/compat +++ bfbtester-2.0.1.orig/debian/compat @@ -1 +0,0 @@ -5 only in patch2: unchanged: --- bfbtester-2.0.1.orig/debian/manpages +++ bfbtester-2.0.1/debian/manpages @@ -0,0 +1 @@ +debian/bfbtester.1
Processed: bfbtester: diff for NMU version 2.0.1-7.2
Processing control commands: > tags 965431 + patch Bug #965431 [src:bfbtester] bfbtester: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965431 + pending Bug #965431 [src:bfbtester] bfbtester: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002548: marked as done (libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules)
Your message dated Sat, 29 Jan 2022 01:19:11 + with message-id and subject line Bug#1002548: fixed in indi-fli 1.5-2 has caused the Debian Bug report #1002548, regarding libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules 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.) -- 1002548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libfli2,indi-fli Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 2.0-2 Control: found -1 1.5-1 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Preparing to unpack .../indi-fli_1.5-1_amd64.deb ... Unpacking indi-fli (1.5-1) ... dpkg: error processing archive /var/cache/apt/archives/indi-fli_1.5-1_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/99-fli.rules', which is also in package libfli2 2.0-2 Errors were encountered while processing: /var/cache/apt/archives/indi-fli_1.5-1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /lib/udev/rules.d/99-fli.rules This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html libfli2=2.0-2_indi-fli=1.5-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: indi-fli Source-Version: 1.5-2 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of indi-fli, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated indi-fli 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: Fri, 28 Jan 2022 22:51:23 +0100 Source: indi-fli Architecture: source Version: 1.5-2 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Thorsten Alteholz Closes: 1002548 Changes: indi-fli (1.5-2) unstable; urgency=medium . * upload source * debian/control: move maintainer to debian-astro * debian/control: add VCS entries * do not install 99-fli.rules here (Closes: #1002548) Checksums-Sha1: b0b60fb963f5b6b15982593385ce4de417398209 2172 indi-fli_1.5-2.dsc e3ab0b6258dfde08ee3dfa9c0a55c39be1fbbfe4 1432 indi-fli_1.5-2.debian.tar.xz 6a14f5961dacf1e4653b5d753428f8ea8fda208e 8206 indi-fli_1.5-2_amd64.buildinfo Checksums-Sha256: 80f1a28498bf9039dc353b378f9e1850541dcdbf4dacd546dc8cc59b41a4a2c5 2172 indi-fli_1.5-2.dsc 19184e92273a8ece3c13067cfdd72fd214569cf3f36cc8dbaca6647d60313cb2 1432 indi-fli_1.5-2.debian.tar.xz 3a8b1de6d2b9ae6ae5a2704e2dd33b16b4047a87c0925033cb8fb6fa8617ff43 8206 indi-fli_1.5-2_amd64.buildinfo Files: 68390f7a7124cf3ebd5855cf8455256d 2172 science optional indi-fli_1.5-2.dsc 4f11c02cac0348fafe87229e7251b41f 1432 science optional indi-fli_1.5-2.debian.tar.xz e88d6d3e20a322672367e5e85c460377 8206 science optional indi-fli_1.5-2_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#1002213: dmitry: diff for NMU version 1.3a-1.2
Control: tags 1002213 + patch Control: tags 1002213 + pending Dear maintainer, I've prepared an NMU for dmitry (versioned as 1.3a-1.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer or cancel the upload. Regards, Eriberto diff -u dmitry-1.3a/debian/changelog dmitry-1.3a/debian/changelog --- dmitry-1.3a/debian/changelog +++ dmitry-1.3a/debian/changelog @@ -1,3 +1,19 @@ +dmitry (1.3a-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Using new DH level format. Consequently: + - debian/compat: removed. + - debian/control: changed from 'debhelper' to 'debhelper-compat' in +Build-Depends field and bumped level to 13. + - Closes: #1002213 + * Dropped CDBS in favor of the debhelper to allow the build system to use +DH level greater than 11. Consequently: + - debian/control: removed no longer needed cdbs and autotools-dev from +Build-Depends field. + - debian/rules: changed from CDBS to DH. + + -- Joao Eriberto Mota Filho Fri, 28 Jan 2022 21:25:23 -0300 + dmitry (1.3a-1.1) unstable; urgency=medium * Non-maintainer upload. reverted: --- dmitry-1.3a/debian/compat +++ dmitry-1.3a.orig/debian/compat @@ -1 +0,0 @@ -5 diff -u dmitry-1.3a/debian/control dmitry-1.3a/debian/control --- dmitry-1.3a/debian/control +++ dmitry-1.3a/debian/control @@ -2,7 +2,7 @@ Section: net Priority: extra Maintainer: Runa Sandvik -Build-Depends: cdbs, debhelper (>= 7), autotools-dev +Build-Depends: debhelper-compat (= 13) Standards-Version: 3.8.0 Homepage: http://www.mor-pah.net/index.php?file=projects/dmitry diff -u dmitry-1.3a/debian/rules dmitry-1.3a/debian/rules --- dmitry-1.3a/debian/rules +++ dmitry-1.3a/debian/rules @@ -5,5 +5,5 @@ # Workaround for #957142 export DEB_CFLAGS_MAINT_APPEND = -fcommon -include /usr/share/cdbs/1/rules/debhelper.mk -include /usr/share/cdbs/1/class/autotools.mk +%: + dh $@
Processed: dmitry: diff for NMU version 1.3a-1.2
Processing control commands: > tags 1002213 + patch Bug #1002213 [src:dmitry] dmitry: FTBFS: dh_clean: error: Compatibility levels before 7 are no longer supported (level 5 requested) Added tag(s) patch. > tags 1002213 + pending Bug #1002213 [src:dmitry] dmitry: FTBFS: dh_clean: error: Compatibility levels before 7 are no longer supported (level 5 requested) Added tag(s) pending. -- 1002213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997287: marked as done (zeitgeist: FTBFS: where-clause.vala:219.35-219.63: error: The name `pdata' does not exist in the context of `GLib.PtrArray*')
Your message dated Sat, 29 Jan 2022 00:19:33 +
with message-id
and subject line Bug#997287: fixed in zeitgeist 1.0.3-7
has caused the Debian Bug report #997287,
regarding zeitgeist: FTBFS: where-clause.vala:219.35-219.63: error: The name
`pdata' does not exist in the context of `GLib.PtrArray*'
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.)
--
997287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zeitgeist
Version: 1.0.3-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/libzeitgeist'
> /usr/bin/valac \
> --target-glib=2.36 --pkg gio-2.0 --pkg gio-unix-2.0 --pkg sqlite3
> ../config.vapi -C --vapi zeitgeist-datamodel-2.0.vapi -H
> zeitgeist-datamodel.h --library zeitgeist-2.0 \
> data-source.vala errors.vala mimetype.vala enumerations.vala event.vala
> subject.vala timerange.vala timestamp.vala ontology-uris.vala ontology.vala
> result-set.vala simple-result-set.vala utils.vala
> event.vala:250.24-250.56: warning: Access to possible `null'. Perform a check
> or use an unsafe cast.
> path = (info as DesktopAppInfo).filename;
>^
> timestamp.vala:77.32-77.46: warning: `GLib.TimeVal' has been deprecated since
> 2.62
> timestamp.vala:95.27-95.33: warning: `GLib.TimeVal' has been deprecated since
> 2.62
> timestamp.vala:95.17-95.23: warning: `GLib.TimeVal' has been deprecated since
> 2.62
> timestamp.vala:122.27-122.33: warning: `GLib.TimeVal' has been deprecated
> since 2.62
> timestamp.vala:122.17-122.23: warning: `GLib.TimeVal' has been deprecated
> since 2.62
> timestamp.vala:139.17-139.23: warning: `GLib.TimeVal' has been deprecated
> since 2.62
> timestamp.vala:185.17-185.23: warning: `GLib.TimeVal' has been deprecated
> since 2.62
> timestamp.vala:186.9-186.25: warning: `GLib.Date.set_time_val' has been
> deprecated since 2.62
> errors.vala:39.5-39.43: warning: Method `Zeitgeist.vala_bug_workaround' never
> used
> private static void vala_bug_workaround ()
> ^^^
> event.vala:299.5-299.47: warning: Method
> `Zeitgeist.Event.optimize_variant_allocation' never used
> private Variant optimize_variant_allocation (Variant event_variant) {
> ^^^
> Compilation succeeded - 11 warning(s)
> touch libzeitgeist_datamodel_2_0_la_vala.stamp
> /usr/bin/valac \
> --target-glib=2.36 --pkg gio-2.0 --pkg gio-unix-2.0 --pkg sqlite3
> ../config.vapi -C ./zeitgeist-datamodel-2.0.vapi --vapi
> zeitgeist-internal.vapi -H zeitgeist-internal.h \
> db-reader.vala sql.vala sql-schema.vala table-lookup.vala
> where-clause.vala
> sql.vala:456.13-457.55: warning: unhandled error `Zeitgeist.EngineError'
> where-clause.vala:219.35-219.63: error: The name `pdata' does not exist in
> the context of `GLib.PtrArray*'
> Memory.copy(pointers, ((PtrArray *) gptrarr)->pdata,
> ^
> Compilation failed: 1 error(s), 1 warning(s)
> make[3]: *** [Makefile:1298: libzeitgeist_internal_la_vala.stamp] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/zeitgeist_1.0.3-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!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: zeitgeist
Source-Version: 1.0.3-7
Done: Sudip Mukherjee
We believe that the bug you reported is fixed in the latest version of
zeitgeist, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sudip Mukherjee (supplier of updated zeitgeist
package)
(This message was generated automatically at the
Bug#1004490: libkcapi: binary-all FTBFS
Source: libkcapi
Version: 1.3.1-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=libkcapi&arch=all&ver=1.3.1-2&stamp=1643387702&raw=0
...
dh_missing -i
dh_missing: warning: usr/lib/x86_64-linux-gnu/libkcapi.la exists in debian/tmp
but is not installed to anywhere
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with
files per package)
* dh_install: kcapi-tools (3), libkcapi-dev (4), libkcapi-doc (144),
libkcapi1 (2)
* dh_installdocs: kcapi-tools (0), libkcapi-dev (0), libkcapi-doc (0),
libkcapi1 (0)
* dh_installman: kcapi-tools (3), libkcapi-dev (106), libkcapi-doc
(0), libkcapi1 (0)
If the missing files are installed by another tool, please file a bug
against it.
When filing the report, if the tool is not part of debhelper itself,
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide
for debhelper (10.6.3+).
(in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary
when only a subset is built
If the omission is intentional or no other helper can take care of this
consider adding the
paths to debian/not-installed.
Remember to be careful with paths containing "x86_64-linux-gnu", where
you might need to
use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
debian/not-installed
to ensure it works on all architectures (see #961104).
make: *** [debian/rules:12: binary-indep] Error 25
Bug#1004409: marked as done (libslurm-dev: slurm/slurm_version.h is missing)
Your message dated Fri, 28 Jan 2022 23:34:02 + with message-id and subject line Bug#1004409: fixed in slurm-wlm 21.08.5-2 has caused the Debian Bug report #1004409, regarding libslurm-dev: slurm/slurm_version.h is missing 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.) -- 1004409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libslurm-dev Version: 21.08.5-1.1 Severity: serious Tags: ftbfs Control: affects -1 src:mpich $ cat test.c #include $ gcc -c test.c In file included from test.c:1: /usr/include/slurm/slurm.h:55:10: fatal error: slurm/slurm_version.h: No such file or directory 55 | #include | ^~~ compilation terminated. $ --- End Message --- --- Begin Message --- Source: slurm-wlm Source-Version: 21.08.5-2 Done: Gennaro Oliva We believe that the bug you reported is fixed in the latest version of slurm-wlm, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gennaro Oliva (supplier of updated slurm-wlm 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: Fri, 28 Jan 2022 23:36:39 +0100 Source: slurm-wlm Architecture: source Version: 21.08.5-2 Distribution: unstable Urgency: medium Maintainer: Debian HPC Team Changed-By: Gennaro Oliva Closes: 984928 1004409 Changes: slurm-wlm (21.08.5-2) unstable; urgency=medium . * Add slurm_version.h to libslurm-dev (Closes: #1004409) * Add retry-getaddrinfo patch (Closes: #984928) * Update service files Checksums-Sha1: 5a8da3888c50f618def6c9990b68829464d86a94 3738 slurm-wlm_21.08.5-2.dsc ced5ef2dbe2bdfdc01317908c54b5514b1e7af75 132636 slurm-wlm_21.08.5-2.debian.tar.xz a17f9cb5d1a394e47d5b40278e8b1eef1ad934e3 21635 slurm-wlm_21.08.5-2_amd64.buildinfo Checksums-Sha256: 50a2bd018ae7e9210231e721f37d5d275019b0a86fa53c587e3f6c2bf2d316e8 3738 slurm-wlm_21.08.5-2.dsc 9fcbf38dbf0cc797e772249a8cf924bebe24900fc742b70e17b5082352c1c541 132636 slurm-wlm_21.08.5-2.debian.tar.xz c37673d8331b5a4d23feba1417f85e8f95de633b4266c7f8667bce6d76c5e5a4 21635 slurm-wlm_21.08.5-2_amd64.buildinfo Files: 94b0b11242d636cd214e681a6a194284 3738 admin optional slurm-wlm_21.08.5-2.dsc fd2f63cdcef05d7e708232bfc3f2e405 132636 admin optional slurm-wlm_21.08.5-2.debian.tar.xz f71bfd0e33830287f7f237a66a2f46dd 21635 admin optional slurm-wlm_21.08.5-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJLBAEBCgA1FiEE6zNF9WRBuLgad5h2ffpBrZYZhdcFAmH0ctUXHG9saXZhLmdA bmEuaWNhci5jbnIuaXQACgkQffpBrZYZhdf3Tw/6A+wW+GOjvdpSKQ+cmmftE2wb Q6kDWVjVkhEmN27U+naZD/c5ggkQFbjc92+P5e3F1lXhsIq4Q6Eu2VRa/2PtjP8i 1mjiNIBnvhdWZz+jC3l4bcCMSwXWjtfSqS6jB3YVKdjMebcr9WnH8D/pKq1UO4FD vYyzNJJa5y2liUIy/rGHp3V1q2MTDWPh3O+DbLnUcSbaOD6igVqNsj1FzSuWry3w /ZwjDeciT+gSNdWkoK0ef2GbpITs+yeQmkP6Hpe1WwX/OlTaSaAYFe8aKXGDnUZD cru2seztmcxaXlP3LYaAm8aDyaTmWQT34EKO9IXBzGf8Hqx7MG+ODylpxsgSZhwH N2mkguFNuU0BU6e/t3/9OLJmAQ8wqY2I/jBOOkjMvx9Ei56qJdLwBQaLs//BxfYZ OOpxM0qr57odmrJrtUrRrOt8IcrFET0L5zyC+1PFMTshyOXRuTbiuAg86I66+C2j UOhxDNiys5KHFh4Pu6cMuAqsyJVi7dj4XQ01HIapbIDALL6ljakTRXY6VHtadvfl 2eh2UM3PuB9peYNtDwcB3rzSBn/N1wfNG6wAHhbhY3noEBhQvwOScAunABIGkMIq Ml9xn8c8T83PAZCvYFN//jfPg0JCU0HeJkulM8/dyZ3wvCt7DCxttnCGs3Dsg3ZC GqPdHxfv0VwOmOJBOmQ= =Lwgu -END PGP SIGNATURE End Message ---
Bug#998540: marked as done (shared-mime-info: FTBFS: Error: cannot open mo file /<>/obj-x86_64-linux-gnu/po/*.gmo)
Your message dated Sat, 29 Jan 2022 00:10:32 +0100 with message-id and subject line Re: Bug#998540: shared-mime-info: FTBFS: Error: cannot open mo file /<>/obj-x86_64-linux-gnu/po/*.gmo has caused the Debian Bug report #998540, regarding shared-mime-info: FTBFS: Error: cannot open mo file /<>/obj-x86_64-linux-gnu/po/*.gmo 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.) -- 998540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: shared-mime-info Version: 2.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --no-parallel >dh_update_autotools_config -O--no-parallel >dh_autoreconf -O--no-parallel >dh_auto_configure -O--no-parallel > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: shared-mime-info > Project version: 2.0 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Program itstool found: YES (/usr/bin/itstool) > Program xmllint found: YES (/usr/bin/xmllint) > Program xmlto found: YES (/usr/bin/xmlto) > Program ./xdgmime/src/print-mime-data found: NO > Program ./xdgmime/src/test-mime-data found: NO > Program ./xdgmime/src/test-mime found: NO > ../meson.build:43: WARNING: > *** > *** xdgmime not compiled, test suite cannot run. Check HACKING for info *** > *** > > Checking for function "fdatasync" : YES > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency libxml-2.0 found: YES 2.9.12 > Run-time dependency glib-2.0 found: YES 2.70.0 > Run-time dependency gio-2.0 found: YES 2.70.0 > Program check_translations.sh found: YES > (/<>/po/check_translations.sh) > Program freedesktop_generate.sh found: YES > (/<>/data/freedesktop_generate.sh) > Configuring config.h using configuration > Program test_generic_icons.sh found: YES > (/<>/tests/test_generic_icons.sh) > Program test_duplicate_mime_types.sh found: YES > (/<>/tests/test_duplicate_mime_types.sh) > Program test-case-sensitivity.sh found: YES > (/<>/tests/test-case-sensitivity.sh) > Build targets in project: 84 > > shared-mime-info 2.0 > > User defined options > buildtype: plain > libdir : lib/x86_64-linux-gnu > localstatedir: /var > prefix : /usr > sysconfdir : /etc > wrap_mode: nodownload > > Found ninja-1.10.1 at /usr/bin/ninja >dh_auto_build -O--no-parallel > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v > [1/83] msgfmt ../po/af.po -o po/af/LC_MESSAGES/shared-mime-info.mo > [2/83] msgfmt ../po/ar.po -o po/ar/LC_MESSAGES/shared-mime-info.mo > [3/83] msgfmt ../po/as.po -o po/as/LC_MESSAGES/shared-mime-info.mo > [4/83] msgfmt ../po/ast.po -o po/ast/LC_MESSAGES/shared-mime-info.mo > [5/83] msgfmt ../po/az.po -o po/az/LC_MESSAGES/shared-mime-info.mo > [6/83] msgfmt ../po/be.po -o po/be/LC_MESSAGES/shared-mime-info.mo > [7/83] msgfmt ../po/b...@latin.po -o > po/be@latin/LC_MESSAGES/shared-mime-info.mo > [8/83] msgfmt ../po/bg.po -o po/bg/LC_MESSAGES/shared-mime-info.mo > [9/83] msgfmt ../po/bn_IN.po -o po/bn_IN/LC_MESSAGES/shared-mime-info.mo > [10/83] msgfmt ../po/ca.po -o po/ca/LC_MESSAGES/shared-mime-info.mo > [11/83] msgfmt ../po/c...@valencia.po -o > po/ca@valencia/LC_MESSAGES/shared-mime-info.mo > [12/83] msgfmt ../po/cs.po -o po/cs/LC_MESSAGES/shared-mime-info.mo > [13/83] msgfmt ../po/cy.po -o po/cy/LC_MESSAGES/shared-mime-info.mo > [14/83] msgfmt ../po/da.po -o po/da/LC_MESSAGES/shared-mime-info.mo > [15/83] msgfmt ../po/de.po -o po/de/LC_MESSAGES/shared-mime-info.mo > [16/83] msgfmt ../po/el.po -o po/el/LC_MESSAGES/shared-mime-info.mo > [17/83] msgfmt ../po/en_GB.po -o po/en_GB/LC_MESSAGES/shared-mime-info.mo > [18/83] msgfmt ../po/eo.po -o po/eo/LC_MESSAGES/shared-mime-info.mo > [19/83] msgfmt ../po/es.po -o po/es/LC_MESSAGES/shared-mime-info.mo > [20/83] msgfmt ../po/et.po
Bug#996380: marked as done (ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)
Your message dated Fri, 28 Jan 2022 22:06:32 + with message-id and subject line Bug#996380: fixed in ruby-safe-yaml 1.0.5-2 has caused the Debian Bug report #996380, regarding ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: 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.) -- 996380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-safe-yaml Version: 1.0.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-safe-yaml was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments (given 0, expected 2) > # ./lib/safe_yaml/safe_to_ruby_visitor.rb:14:in `initialize' > # ./lib/safe_yaml/psych_resolver.rb:25:in `new' > # ./lib/safe_yaml/psych_resolver.rb:25:in `native_resolve' > # ./lib/safe_yaml/resolver.rb:12:in `resolve_node' > # ./lib/safe_yaml/resolver.rb:55:in `block in resolve_seq' > # ./lib/safe_yaml/resolver.rb:55:in `each' > # ./lib/safe_yaml/resolver.rb:55:in `inject' > # ./lib/safe_yaml/resolver.rb:55:in `resolve_seq' > # ./lib/safe_yaml/psych_resolver.rb:17:in `resolve_root' > # ./lib/safe_yaml/resolver.rb:16:in `resolve_node' > # ./lib/safe_yaml/load.rb:151:in `load' > # ./lib/safe_yaml.rb:29:in `safe_load' > # ./spec/safe_yaml_spec.rb:7:in `safe_load_round_trip' > # ./spec/safe_yaml_spec.rb:725:in `block (4 levels) in ' > > Finished in 0.12951 seconds (files took 0.22092 seconds to load) > 134 examples, 11 failures > > Failed examples: > > rspec ./spec/safe_yaml_spec.rb:318 # Psych safe_load with special whitelisted > tags defined will allow objects to be deserialized for whitelisted tags > rspec ./spec/safe_yaml_spec.rb:330 # Psych safe_load with special whitelisted > tags defined will not allow non-whitelisted objects to be embedded within > objects with whitelisted tags > rspec ./spec/safe_yaml_spec.rb:372 # Psych safe_load with special whitelisted > tags defined with the :raise_on_unknown_tag option enabled does not raise an > exception as long as all tags are whitelisted > rspec ./spec/safe_yaml_spec.rb:415 # Psych safe_load with special whitelisted > tags defined with the :raise_on_unknown_tag option enabled with whitelisted > custom class does not raise an exception on the non-specific '!' tag > rspec ./spec/safe_yaml_spec.rb:458 # Psych safe_load when options are passed > direclty to #load which differ from the defaults (or, for example, when > certain tags are whitelisted) goes with the default option when it is not > overridden > rspec ./spec/safe_yaml_spec.rb:464 # Psych safe_load when options are passed > direclty to #load which differ from the defaults (or, for example, when > certain tags are whitelisted) allows the default option to be overridden on a > per-call basis > rspec ./spec/safe_yaml_spec.rb:688 # Psych whitelist! with a Class as its > argument successfully deserializes the specified class > rspec ./spec/safe_yaml_spec.rb:699 # Psych whitelist! with a Class as its > argument works for ranges > rspec ./spec/safe_yaml_spec.rb:704 # Psych whitelist! with a Class as its > argument works for regular expressions > rspec ./spec/safe_yaml_spec.rb:709 # Psych whitelist! with a Class as its > argument works for multiple classes > rspec ./spec/safe_yaml_spec.rb:714 # Psych whitelist! with a Class as its > argument works for arbitrary Exception subclasses > > debian/ruby-tests.rb:16:in `block in ': unhandled exception > from debian/ruby-tests.rb:14:in `each' > from debian/ruby-tests.rb:14:in `' > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-safe-yaml/ruby-safe-yaml_1.0.5-1+rebuild1633394716_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-safe-yaml Source-Version: 1.0.5-2 Done: Sergio Durigan Junior We believe that the bug you reported is fixed in the latest version of ruby-safe-yaml, 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 th
Processed: severity of 1000934 is important
Processing commands for cont...@bugs.debian.org: > severity 1000934 important Bug #1000934 [src:clazy] clazy: FTBFS on i386 with llvm-toolchain-13 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: dulwich: autopkgtest regression: src/debian/tests/testsuite3: 10: -m: not found
Processing control commands: > tags -1 patch Bug #1003017 [src:dulwich] dulwich: autopkgtest regression: src/debian/tests/testsuite3: 10: -m: not found Added tag(s) patch. -- 1003017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003017: dulwich: autopkgtest regression: src/debian/tests/testsuite3: 10: -m: not found
control: tags -1 patch for py in $(py3versions -s); do echo "= Running tests with $py ==" if ! $py3 -m unittest dulwich.tests.test_suite; then rv=1 this should really be for py3 in $(py3versions -s); do echo "= Running tests with $py ==" if ! $py3 -m unittest dulwich.tests.test_suite; then rv=1 (the for loop variable is called py and then py3 inside the if statement. I presume they should both be called py3 patch here: http://launchpadlibrarian.net/582665575/dulwich_0.20.31-1_0.20.31-1ubuntu1.diff.gz G. On Sun, 2 Jan 2022 21:08:25 +0100 Paul Gevers wrote: Source: dulwich Version: 0.20.26-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of dulwich the autopkgtest of dulwich fails in testing when that autopkgtest is run with the binary packages of dulwich from unstable. It passes when run with only packages from testing. In tabular form: passfail dulwichfrom testing0.20.26-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=dulwich https://ci.debian.net/data/autopkgtest/testing/amd64/d/dulwich/17999494/log.gz = Running tests with python3.9 == /tmp/autopkgtest-lxc.n4tqfogv/downtmp/build.r97/src/debian/tests/testsuite3: 10: -m: not found autopkgtest [23:08:36]: test testsuite3
Bug#1001057: grub2: hold 2.06 in unstable for now
Hi Colin, On Fri, 3 Dec 2021 11:17:26 + Colin Watson wrote: GRUB 2.06 is a pretty big change over 2.04. I'd like to hold this in unstable for a while longer to let things shake out before we allow it to move to testing. grub2 showed up in my out-of-sync tracking script output. Do you think it's about time you could let grub2 into testing? I'm not trying to hurry you, take your time, but I was just wondering if you forgot about this bug. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1004465: libklibc-dev: headers not installed
Processing commands for cont...@bugs.debian.org: > found 1004465 2.0.10-1 Bug #1004465 [libklibc-dev] libklibc-dev: headers not installed Marked as found in versions klibc/2.0.10-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004465: libklibc-dev: headers not installed
found 1004465 2.0.10-1 thanks Dixi quod… >Quite some files are missing: […] >/usr/lib/klibc/include/alloca.h […] >/usr/lib/klibc/include/arpa/inet.h > /usr/lib/klibc/include/asm > /usr/lib/klibc/include/asm-generic >/usr/lib/klibc/include/assert.h […] From this pattern, commit 8f680c0688151ce4d50072783a5b6fad7beabc1f is suspect: Since debhelper 11, dh_install and dh_installman have automatically searched for the listed files/directories relative to debian/tmp/ as well as in the top directory. --- a/debian/libklibc-dev.install +++ b/debian/libklibc-dev.install @@ -1,1 +1,1 @@ -debian/tmp/usr/lib/klibc/include/* +usr/lib/klibc/include/* My suspiction here is that since usr/lib/klibc/include/* exist in the top-level directory, the alternative location is not attempted. I’d probably just rever that and not rely on such fragile automatism that reek of bad magic and make the packaging harder to understand… and easier to break (e.g. if upstream adds files…) bye, //mirabilos -- 22:20⎜ The crazy that persists in his craziness becomes a master 22:21⎜ And the distance between the craziness and geniality is only measured by the success 18:35⎜ "Psychotics are consistently inconsistent. The essence of sanity is to be inconsistently inconsistent
Bug#1004211: dirty.js: autopkgtest failure on armhf and ppc64el
Control: tags -1 + moreinfo Hi, I'm unable to reproduce using a porterbox
Processed: Re: dirty.js: autopkgtest failure on armhf and ppc64el
Processing control commands: > tags -1 + moreinfo Bug #1004211 [src:dirty.js] dirty.js: autopkgtest failure on armhf and ppc64el Added tag(s) moreinfo. -- 1004211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004464: marked as done (python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase))
Your message dated Fri, 28 Jan 2022 17:04:24 +
with message-id
and subject line Bug#1004464: fixed in python-django 2:3.2.11-2
has caused the Debian Bug report #1004464,
regarding python-django FTBFS: FAIL: test_custom_fields
(inspectdb.tests.InspectDBTestCase)
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.)
--
1004464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 2:3.2.7-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=python-django&arch=all&ver=2%3A3.2.11-1&stamp=1641309500&raw=0
...
==
FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase)
Introspection of columns with a custom field (#21090)
--
Traceback (most recent call last):
File "/usr/lib/python3.10/unittest/case.py", line 59, in testPartExecutor
yield
File "/usr/lib/python3.10/unittest/case.py", line 591, in run
self._callTestMethod(testMethod)
File "/usr/lib/python3.10/unittest/case.py", line 549, in _callTestMethod
method()
File "/<>/tests/inspectdb/tests.py", line 313, in
test_custom_fields
self.assertIn("text_field = myfields.TextField()", output)
File "/usr/lib/python3.10/unittest/case.py", line 1112, in assertIn
self.fail(self._formatMessage(msg, standardMsg))
File "/usr/lib/python3.10/unittest/case.py", line 675, in fail
raise self.failureException(msg)
AssertionError: 'text_field = myfields.TextField()' not found in "# This is an
auto-generated Django model module.\n# You'll have to do the following manually
to clean this up:\n# * Rearrange models' order\n# * Make sure each model
has one field with primary_key=True\n# * Make sure each ForeignKey and
OneToOneField has `on_delete` set to the desired behavior\n# * Remove
`managed = False` lines if you wish to allow Django to create, modify, and
delete the table\n# Feel free to rename the models, but don't rename db_table
values or field names.\nfrom django.db import models\n\n\nclass
InspectdbColumntypes(models.Model):\nid =
models.TextField(primary_key=True) # This field type is a guess.\n
big_int_field = models.BigIntegerField()\nbool_field = models.TextField()
# This field type is a guess.\nnull_bool_field =
models.TextField(blank=True, null=True) # This field type is a guess.\n
char_field = models.TextField() # This field type is a guess.\n
null_char_field = models.TextField(blank=True, null=True) # This field type is
a guess.\ndate_field = models.TextField() # This field type is a guess.\n
date_time_field = models.TextField() # This field type is a guess.\n
decimal_field = models.TextField() # This field type is a guess.\n
email_field = models.TextField() # This field type is a guess.\nfile_field
= models.TextField() # This field type is a guess.\nfile_path_field =
models.TextField() # This field type is a guess.\nfloat_field =
models.TextField() # This field type is a guess.\nint_field =
models.TextField() # This field type is a guess.\ngen_ip_address_field =
models.TextField() # This field type is a guess.\npos_big_int_field =
models.TextField() # This field type is a guess.\npos_int_field =
models.TextField() # This field type is a guess.\npos_small_int_field =
models.TextField() # This field type is a guess.\nslug_field =
models.TextField() # This field type is a guess.\nsmall_int_field =
models.TextField() # This field type is a guess.\ntext_field =
models.TextField() # This field type is a guess.\ntime_field =
models.TextField() # This field type is a guess.\nurl_field =
models.TextField() # This field type is a guess.\nuuid_field =
models.TextField() # This field type is a guess.\n\nclass Meta:\n
managed = False\ndb_table = 'inspectdb_columntypes'\n"
--
Ran 14650 tests in 151.514s
FAILED (failures=1, skipped=1141, expected failures=4)
Destroying test database for alias 'default'
('file:memorydb_default?mode=memory&cache=shared')...
Destroying test database for alias 'default'
('file:memorydb_default?mode=memory&cache=shared')...
Destroying test database for alias 'default'
('file:memorydb_default?mode=memory&cache=shared')...
Destroying test database for alias 'default'
('file:memorydb_default?mode=memory&cache=share
Bug#1004464: marked as done (python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase))
Your message dated Fri, 28 Jan 2022 17:04:31 +
with message-id
and subject line Bug#1004464: fixed in python-django 2:4.0.1-2
has caused the Debian Bug report #1004464,
regarding python-django FTBFS: FAIL: test_custom_fields
(inspectdb.tests.InspectDBTestCase)
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.)
--
1004464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 2:3.2.7-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=python-django&arch=all&ver=2%3A3.2.11-1&stamp=1641309500&raw=0
...
==
FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase)
Introspection of columns with a custom field (#21090)
--
Traceback (most recent call last):
File "/usr/lib/python3.10/unittest/case.py", line 59, in testPartExecutor
yield
File "/usr/lib/python3.10/unittest/case.py", line 591, in run
self._callTestMethod(testMethod)
File "/usr/lib/python3.10/unittest/case.py", line 549, in _callTestMethod
method()
File "/<>/tests/inspectdb/tests.py", line 313, in
test_custom_fields
self.assertIn("text_field = myfields.TextField()", output)
File "/usr/lib/python3.10/unittest/case.py", line 1112, in assertIn
self.fail(self._formatMessage(msg, standardMsg))
File "/usr/lib/python3.10/unittest/case.py", line 675, in fail
raise self.failureException(msg)
AssertionError: 'text_field = myfields.TextField()' not found in "# This is an
auto-generated Django model module.\n# You'll have to do the following manually
to clean this up:\n# * Rearrange models' order\n# * Make sure each model
has one field with primary_key=True\n# * Make sure each ForeignKey and
OneToOneField has `on_delete` set to the desired behavior\n# * Remove
`managed = False` lines if you wish to allow Django to create, modify, and
delete the table\n# Feel free to rename the models, but don't rename db_table
values or field names.\nfrom django.db import models\n\n\nclass
InspectdbColumntypes(models.Model):\nid =
models.TextField(primary_key=True) # This field type is a guess.\n
big_int_field = models.BigIntegerField()\nbool_field = models.TextField()
# This field type is a guess.\nnull_bool_field =
models.TextField(blank=True, null=True) # This field type is a guess.\n
char_field = models.TextField() # This field type is a guess.\n
null_char_field = models.TextField(blank=True, null=True) # This field type is
a guess.\ndate_field = models.TextField() # This field type is a guess.\n
date_time_field = models.TextField() # This field type is a guess.\n
decimal_field = models.TextField() # This field type is a guess.\n
email_field = models.TextField() # This field type is a guess.\nfile_field
= models.TextField() # This field type is a guess.\nfile_path_field =
models.TextField() # This field type is a guess.\nfloat_field =
models.TextField() # This field type is a guess.\nint_field =
models.TextField() # This field type is a guess.\ngen_ip_address_field =
models.TextField() # This field type is a guess.\npos_big_int_field =
models.TextField() # This field type is a guess.\npos_int_field =
models.TextField() # This field type is a guess.\npos_small_int_field =
models.TextField() # This field type is a guess.\nslug_field =
models.TextField() # This field type is a guess.\nsmall_int_field =
models.TextField() # This field type is a guess.\ntext_field =
models.TextField() # This field type is a guess.\ntime_field =
models.TextField() # This field type is a guess.\nurl_field =
models.TextField() # This field type is a guess.\nuuid_field =
models.TextField() # This field type is a guess.\n\nclass Meta:\n
managed = False\ndb_table = 'inspectdb_columntypes'\n"
--
Ran 14650 tests in 151.514s
FAILED (failures=1, skipped=1141, expected failures=4)
Destroying test database for alias 'default'
('file:memorydb_default?mode=memory&cache=shared')...
Destroying test database for alias 'default'
('file:memorydb_default?mode=memory&cache=shared')...
Destroying test database for alias 'default'
('file:memorydb_default?mode=memory&cache=shared')...
Destroying test database for alias 'default'
('file:memorydb_default?mode=memory&cache=shared
Bug#1004464: python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase)
Hi, >> Just to point out that you specified the 'Version' here as 2:3.2.7, >> whilst the traceback you linked to: >> >> > https://buildd.debian.org/status/fetch.php?pkg=python-django&arch=all&ver=2%3A3.2.11-1&stamp=1641309500&raw=0 >> >> ... refers to a different version: 2:3.2.11. [..] > That was intentional: > The package does FTBFS both on the buildds and in reproducible > in both unstable and experimental, and the version in testing > did also FTBFS for me in an unstable chroot. Ah, I see — thanks for checking so many versions. I've just uploaded a fix; it was a SQLite compatibility issue. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Processed: Bug#1004464 marked as pending in python-django
Processing control commands: > tag -1 pending Bug #1004464 [src:python-django] python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase) Ignoring request to alter tags of bug #1004464 to the same tags previously set -- 1004464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004464: marked as pending in python-django
Control: tag -1 pending Hello, Bug #1004464 in python-django 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/python-team/packages/python-django/-/commit/8080a59ae57921718fa53e4355ea112ba734be17 Fix compatibility with SQLite 3.37+. (Closes: #1004464) (this message was generated automatically) -- Greetings https://bugs.debian.org/1004464
Bug#1004464: marked as pending in python-django
Control: tag -1 pending Hello, Bug #1004464 in python-django 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/python-team/packages/python-django/-/commit/875f902415bc77a246eb23fc8e9e9ad6eaad2762 Fix compatibility with SQLite 3.37+. (Closes: #1004464) (this message was generated automatically) -- Greetings https://bugs.debian.org/1004464
Processed: Bug#1004464 marked as pending in python-django
Processing control commands: > tag -1 pending Bug #1004464 [src:python-django] python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase) Added tag(s) pending. -- 1004464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004477: virt-top fails to start with OCaml 4.13.1
Le 28/01/2022 à 13:10, Adrian Bunk a écrit : > Package: virt-top > Version: 1.0.9-1.1 > Severity: serious > X-Debbugs-Cc: Debian OCaml Maintainers > > $ virt-top > the file '/usr/bin/virt-top' has not the right magic number: expected > Caml1999X030, got Caml1999X028 /usr/bin/virt-top is a bytecode executable, but its package does not depend on ocaml-base-$ABI. I've scheduled a binNMU, which should fix the immediate problem. But the long-term solution is to make virt-top depend on ocaml-base-$ABI so that the package dependency is statically broken when a new version of ocaml arrives. (Hence, this bug must stay open until that.) Cheers, -- Stéphane
Bug#1004464: python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase)
On Fri, Jan 28, 2022 at 08:42:44AM -0800, Chris Lamb wrote: > found 1004464 2:3.2.11-1 > thanks > > Hi Adrian, > > > Version: 2:3.2.7-1 > > Just to point out that you specified the 'Version' here as 2:3.2.7, > whilst the traceback you linked to: > > > https://buildd.debian.org/status/fetch.php?pkg=python-django&arch=all&ver=2%3A3.2.11-1&stamp=1641309500&raw=0 > > ... refers to a different version: 2:3.2.11. > > It's not a problem at all — am only mentioning it explicitly in case you > have a bug in a script (or similar) that might need updating. That was intentional: The package does FTBFS both on the buildds and in reproducible in both unstable and experimental, and the version in testing did also FTBFS for me in an unstable chroot. 2:3.2.7-1 is the last common ancestor of all these versions. It might have been clearer to you if I'd have set 3 found versions for 2:3.2.10-2 2:3.2.11-1 2:4.0.1-1 instead of this shortcut. > Regards, cu Adrian
Bug#1004464: python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase)
found 1004464 2:3.2.11-1 thanks Hi Adrian, > Version: 2:3.2.7-1 Just to point out that you specified the 'Version' here as 2:3.2.7, whilst the traceback you linked to: > https://buildd.debian.org/status/fetch.php?pkg=python-django&arch=all&ver=2%3A3.2.11-1&stamp=1641309500&raw=0 ... refers to a different version: 2:3.2.11. It's not a problem at all — am only mentioning it explicitly in case you have a bug in a script (or similar) that might need updating. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Processed: Re: Bug#1004464: python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase)
Processing commands for cont...@bugs.debian.org: > found 1004464 2:3.2.11-1 Bug #1004464 [src:python-django] python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase) The source 'python-django' and version '2:3.2.11-1' do not appear to match any binary packages Marked as found in versions python-django/2:3.2.11-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004482: liblog4j1.2-java: CVE-2022-23307 CVE-2022-23305 CVE-2022-23302
Package: liblog4j1.2-java Version: 1.2.17-10 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: Debian Security Team Hey. A number of holes was found in the 1.2 branch of log4j. The following is apparently critical (code injection): https://www.cvedetails.com/cve/CVE-2022-23307/ https://www.cvedetails.com/cve/CVE-2022-23305/ https://www.cvedetails.com/cve/CVE-2022-23302/ AFAIU there is no support anymore form these from upstream, and seems: https://lists.apache.org/thread/rg4yyc89vs3dw6kpy3r92xop9loywyhh there are no plans to fix it. EGI recommends: "For services where chainsaw is installed but not used apply the mitigation zip -q -d /usr/share/cassandra/lib/log4j*.jar org/apache/log4j/chainsaw/*" Not sure if that could be done for the Debian package in a new version? Is Debian going to do anything about these? Thanks, Chris. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Processed: Re: Bug#1003865: GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster)
Processing control commands:
> reassign -1 apt-cacher-ng
Bug #1003865 {Done: "Adam D. Barratt" }
[debian-archive-keyring] GPG error: http://deb.debian.org/debian sid InRelease:
The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive
Automatic Signing Key (10/buster)
Bug reassigned from package 'debian-archive-keyring' to 'apt-cacher-ng'.
No longer marked as found in versions debian-archive-keyring/2021.1.1.
Ignoring request to alter fixed versions of bug #1003865 to the same values
previously set
--
1003865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#733094: 20 GB senseless logfile
I have the same problem here with Debian 11 (bullseye). The only solution seems to be apt-get purge uvcdynctrl After that my webcam still works. So this package can be seen as unusable, harmful and dispensable. This should not be installed and all dependencies snatched. Best regards karsten
Bug#974836: marked as done (openconnect FTBFS on IPV6-only buildds)
Your message dated Fri, 28 Jan 2022 14:39:37 + with message-id and subject line Bug#974836: fixed in openconnect 8.10-7 has caused the Debian Bug report #974836, regarding openconnect FTBFS on IPV6-only buildds 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.) -- 974836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openconnect Version: 8.10-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=openconnect&arch=i386&ver=8.10-1~bpo10%2B1&stamp=1589917131&raw=0 https://buildd.debian.org/status/fetch.php?pkg=openconnect&arch=amd64&ver=8.10-1~bpo10%2B1&stamp=1589912458&raw=0 https://buildd.debian.org/status/fetch.php?pkg=openconnect&arch=amd64&ver=8.10-2&stamp=1603997003&raw=0 ... FAIL: auth-username-pass Testing certificate auth... warning: skipping unknown option 'cookie-validity' Parsing plain auth method subconfig using legacy format note: vhost:default: setting 'plain' as primary authentication method note: setting 'file' as supplemental config option listening (TCP) on [::]:443... listening (UDP) on [::]:443... ocserv[19194]: main: Starting 1 instances of ocserv-sm ocserv[19194]: main: not using control unix socket ocserv[19194]: main: initialized ocserv 1.1.1 ocserv[19214]: sec-mod: reading supplemental config from files ocserv[19214]: sec-mod: sec-mod initialized (socket: ./ocserv-socket.af571984.0) Connecting to obtain cookie... Failure: Could not receive cookie from server ocserv[19194]: main: termination request received; waiting for children to die FAIL auth-username-pass (exit status: 1) FAIL: auth-certificate == Testing certificate auth... warning: skipping unknown option 'cookie-validity' Parsing plain auth method subconfig using legacy format note: vhost:default: setting 'certificate+plain' as primary authentication method note: setting 'file' as supplemental config option listening (TCP) on [::]:443... listening (UDP) on [::]:443... ocserv[19199]: main: Starting 1 instances of ocserv-sm ocserv[19199]: main: not using control unix socket ocserv[19199]: main: initialized ocserv 1.1.1 ocserv[19215]: sec-mod: reading supplemental config from files ocserv[19215]: sec-mod: sec-mod initialized (socket: ./ocserv-socket.bee4d321.0) Connecting to obtain cookie (with key user-key-pkcs1.pem)... Failed to connect to host 127.0.0.2 Failed to open HTTPS connection to 127.0.0.2 Failed to obtain WebVPN cookie Failure: Could not connect with key user-key-pkcs1.pem! ocserv[19199]: main: termination request received; waiting for children to die FAIL auth-certificate (exit status: 1) FAIL: auth-nonascii === Testing certificate auth with non-ASCII passwords... warning: skipping unknown option 'cookie-validity' Parsing plain auth method subconfig using legacy format note: vhost:default: setting 'certificate+plain' as primary authentication method note: setting 'file' as supplemental config option listening (TCP) on [::]:443... listening (UDP) on [::]:443... ocserv[19205]: main: Starting 1 instances of ocserv-sm ocserv[19205]: main: not using control unix socket ocserv[19205]: main: initialized ocserv 1.1.1 ocserv[19216]: sec-mod: reading supplemental config from files ocserv[19216]: sec-mod: sec-mod initialized (socket: ./ocserv-socket.767477a3.0) + echo -n Connecting to obtain cookie (with password charset UTF-8)... Connecting to obtain cookie (with password charset UTF-8)... + cat ./pass-UTF-8 + CERTARGS=-c ./certs/user-key-nonascii-password.p12 --key-password ĂŻ + echo test + LC_ALL=cs_CZ.UTF-8 LD_PRELOAD=libsocket_wrapper.so ../openconnect -q 127.0.0.2:443 -u test -c ./certs/user-key-nonascii-password.p12 --key-password ĂŻ --servercert=d66b507ae074d03b02eafca40d35f87dd81049d3 --cookieonly --passwd-on-stdin Failed to connect to host 127.0.0.2 Failed to open HTTPS connection to 127.0.0.2 Failed to obtain WebVPN cookie + fail 19205 Could not connect with charset UTF-8! + PID=19205 + shift + echo Failure: Could not connect with charset UTF-8! Failure: Could not connect with charset UTF-8! + kill 19205 + test -n ./sockwrap.19193.tmp + rm -rf ./sockwrap.19193.tmp + exit 1 ocserv[19205]: main: termination request received; waiting for children to die FAIL auth-nonascii (exit status: 1) FAIL: cert-fingerprint == Testing certificate auth... warning: skipping unknown option 'cookie-validity' Parsing plain auth method subconfig using legacy format note: vhost:default: setting 'plain' as primary authentication met
Processed: Bug#974836 marked as pending in openconnect
Processing control commands: > tag -1 pending Bug #974836 [src:openconnect] openconnect FTBFS on IPV6-only buildds Added tag(s) pending. -- 974836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974836: marked as pending in openconnect
Control: tag -1 pending Hello, Bug #974836 in openconnect reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/openconnect/-/commit/b0713249f475c540a11e9d9a57595bebe2097f75 Disable build-time tests Sometimes buildd's environment is broken and lacks ipv4 localhost, so we cannot run the networked tests that use ocserv Closes: #974836 (this message was generated automatically) -- Greetings https://bugs.debian.org/974836
Bug#1004478: marked as done (emscripten: attempts internet communication during build)
Your message dated Fri, 28 Jan 2022 13:33:44 +
with message-id
and subject line Bug#1004478: fixed in emscripten 3.1.2~dfsg+~1.39.6-3
has caused the Debian Bug report #1004478,
regarding emscripten: attempts internet communication during build
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.)
--
1004478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emscripten
Version: 3.1.1~dfsg+~1.39.6-5
Severity: serious
Hello, some tests are trying to reach googleapis
test_global_inits (test_other.other) ... skipped 'relies on fastcomp
EXIT_RUNTIME=0 optimization not implemented/disabled'
ports:INFO: retrieving port: giflib from
https://storage.googleapis.com/webassembly/emscripten-ports/giflib-5.2.1.tar.gz
test_headless (test_other.other) ... ok (1.28s)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 169, in
_new_conn
conn = connection.create_connection(
File "/usr/lib/python3/dist-packages/urllib3/util/connection.py", line 73, in
create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/lib/python3.10/socket.py", line 955, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in
urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382, in
_make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 353, in
connect
conn = self._new_conn()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 181, in
_new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: : Failed to establish a new connection: [Errno -2] Name or
service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, in
urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in
increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='storage.googleapis.com',
port=443): Max retries exceeded with url:
/webassembly/emscripten-ports/giflib-5.2.1.tar.gz (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service
not known'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 3912, in
sys.exit(main(sys.argv))
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 3905, in main
ret = run(args)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 1117, in run
linker_inputs = phase_compile_inputs(options, state, newargs, input_files)
File "/usr/lib/python3.10/contextlib.py", line 79, in inner
return func(*args, **kwds)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 2609, in
phase_compile_inputs
compile_source_file(i, input_file)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 2589, in
compile_source_file
cmd = get_clang_command(input_file)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 2530, in
get_clang_command
return get_compiler(src_file) + get_cflags(state.orig_args) + compile_args
+ [src_file]
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 905, in
get_cflags
ports.add_cflags(cflags, settings)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/tools/ports/__init__.py",
line 364, in add_cflags
port.get(Ports, settings, shared)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/tools/ports/giflib.py",
line 19, in get
ports.fetch_project('giflib',
f'https://storage.googleapis.com/webassembly/emscripten-ports/giflib-{VERSION}.tar.gz',
f'giflib-{VERSION}', sha512hash=HASH)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/tools/ports/__init__.py",
line 258, in fetch_project
retrieve()
File "/<>/emscripten-3.1.1~dfsg+~1.39.
Bug#1004478: marked as pending in emscripten
Control: tag -1 pending Hello, Bug #1004478 in emscripten 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/emscripten/-/commit/c8fac749ecc9faeae9898a2e0766e6668b590513 fix avoid test test_giflib requiring download of Emscripten port; closes: bug#1004478, thanks to Gianfranco Costamagna (this message was generated automatically) -- Greetings https://bugs.debian.org/1004478
Processed: Bug#1004478 marked as pending in emscripten
Processing control commands: > tag -1 pending Bug #1004478 [src:emscripten] emscripten: attempts internet communication during build Added tag(s) pending. -- 1004478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#974836: openconnect FTBFS on IPV6-only buildds
Processing control commands: > severity -1 serious Bug #974836 [src:openconnect] openconnect FTBFS on IPV6-only buildds Severity set to 'serious' from 'important' -- 974836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004478: emscripten: attempts internet communication during build
Source: emscripten
Version: 3.1.1~dfsg+~1.39.6-5
Severity: serious
Hello, some tests are trying to reach googleapis
test_global_inits (test_other.other) ... skipped 'relies on fastcomp
EXIT_RUNTIME=0 optimization not implemented/disabled'
ports:INFO: retrieving port: giflib from
https://storage.googleapis.com/webassembly/emscripten-ports/giflib-5.2.1.tar.gz
test_headless (test_other.other) ... ok (1.28s)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 169, in
_new_conn
conn = connection.create_connection(
File "/usr/lib/python3/dist-packages/urllib3/util/connection.py", line 73, in
create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/lib/python3.10/socket.py", line 955, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in
urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382, in
_make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 353, in
connect
conn = self._new_conn()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 181, in
_new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: : Failed to establish a new connection: [Errno -2] Name or
service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, in
urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in
increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='storage.googleapis.com',
port=443): Max retries exceeded with url:
/webassembly/emscripten-ports/giflib-5.2.1.tar.gz (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service
not known'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 3912, in
sys.exit(main(sys.argv))
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 3905, in main
ret = run(args)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 1117, in run
linker_inputs = phase_compile_inputs(options, state, newargs, input_files)
File "/usr/lib/python3.10/contextlib.py", line 79, in inner
return func(*args, **kwds)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 2609, in
phase_compile_inputs
compile_source_file(i, input_file)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 2589, in
compile_source_file
cmd = get_clang_command(input_file)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 2530, in
get_clang_command
return get_compiler(src_file) + get_cflags(state.orig_args) + compile_args
+ [src_file]
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/emcc.py", line 905, in
get_cflags
ports.add_cflags(cflags, settings)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/tools/ports/__init__.py",
line 364, in add_cflags
port.get(Ports, settings, shared)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/tools/ports/giflib.py",
line 19, in get
ports.fetch_project('giflib',
f'https://storage.googleapis.com/webassembly/emscripten-ports/giflib-{VERSION}.tar.gz',
f'giflib-{VERSION}', sha512hash=HASH)
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/tools/ports/__init__.py",
line 258, in fetch_project
retrieve()
File "/<>/emscripten-3.1.1~dfsg+~1.39.6/tools/ports/__init__.py",
line 213, in retrieve
response = requests.get(url)
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 516, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError:
HTTPSConnectionPool(host='storage.googleapis.com', port=443): Max retries exceed
Bug#1004477: virt-top fails to start with OCaml 4.13.1
Package: virt-top Version: 1.0.9-1.1 Severity: serious X-Debbugs-Cc: Debian OCaml Maintainers $ virt-top the file '/usr/bin/virt-top' has not the right magic number: expected Caml1999X030, got Caml1999X028 $
Processed: Bug#1004311: found in 1.22-2, not found in 1.22-4
Processing commands for cont...@bugs.debian.org:
> found 1004311 1.22-2
Bug #1004311 {Done: Domenico Andreoli } [pahole] pahole
segfaults during kernel build
Ignoring request to alter found versions of bug #1004311 to the same values
previously set
> notfound 1004311 1.22-4
Bug #1004311 {Done: Domenico Andreoli } [pahole] pahole
segfaults during kernel build
Ignoring request to alter found versions of bug #1004311 to the same values
previously set
> --
Stopping processing here.
Please contact me if you need assistance.
--
1004311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1004453: marked as done (libcmark-dev generates broken dependencies.)
Your message dated Fri, 28 Jan 2022 09:19:00 + with message-id and subject line Bug#1004453: fixed in cmark 0.30.2-5 has caused the Debian Bug report #1004453, regarding libcmark-dev generates broken dependencies. 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.) -- 1004453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcmark-dev Version: 0.9.0-1 Severity: serious Rebuilding nheko in current sid results in the following dependencies. Depends: libc6 (>= 2.33), libcmark0 (>= 0.30.2-4), libcmark0 (<< 0.30.2-4+), libcurl4 (>= 7.16.3), libevent-core-2.1-7 (>= 2.1.8-stable), libevent-pthreads-2.1-7 (>= 2.1.8-stable), libfmt8 (>= 8.1.1+ds1), libgcc-s1 (>= 3.0), libglib2.0-0 (>= 2.22.0), libgstreamer-plugins-bad1.0-0 (>= 1.18.5), libgstreamer-plugins-base1.0-0 (>= 1.18.0), libgstreamer1.0-0 (>= 1.18.0), liblmdb0 (>= 0.9.7), libolm3 (>= 3.1.3), libqt5core5a (>= 5.15.1), libqt5dbus5 (>= 5.14.1), libqt5gui5 (>= 5.14.1) | libqt5gui5-gles (>= 5.14.1), libqt5keychain1 (>= 0.7.0), libqt5multimedia5 (>= 5.6.0~beta), libqt5network5 (>= 5.10), libqt5qml5 (>= 5.14.1), libqt5quick5 (>= 5.9.0~beta) | libqt5quick5-gles (>= 5.9.0~beta), libqt5quickwidgets5 (>= 5.3.0), libqt5svg5 (>= 5.6.0~beta), libqt5widgets5 (>= 5.15.1), libspdlog1-fmt8, libssl1.1 (>= 1.1.0), libstdc++6 (>= 11), libxcb-ewmh2 (>= 0.4.1), libxcb1, qml-module-qt-labs-platform, qml-module-qt-labs-settings, qml-module-qtgraphicaleffects, qml-module-qtmultimedia, qml-module-qtquick2, qml-module-qtquick-controls2, qml-module-qtquick-layouts, qml-module-qtquick-window2, gstreamer1.0-nice, gstreamer1.0-qt5, gstreamer1.0-vaapi Which are not satisfiable as libcmark0 does not exist in bookworm/sid This appears to be a result of https://salsa.debian.org/debian/cmark/-/commit/8be8ebaab1a6d4966b87dfe1eb18710aa20db045 Which seems wrong in several ways and IMO should be reverted. 1. It adds dependencies on a package that doesn't exist. 2. It doesn't seem necessary in the first place, cmark already incorporates the upstream version number as part of the binary package name. 3. The versioning used is too strict, it would force reverse dependencies to be rebuilt every time there was a Debian revision to cmark. --- End Message --- --- Begin Message --- Source: cmark Source-Version: 0.30.2-5 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of cmark, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated cmark 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: Fri, 28 Jan 2022 10:06:31 +0100 Source: cmark Architecture: source Version: 0.30.2-5 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1004453 Changes: cmark (0.30.2-5) unstable; urgency=medium . * Revert plain wrong change to shlibs hint file; closes: bug#1004453, thanks to Peter Green Checksums-Sha1: 56f3a512d7aec5dd643352187b5dcba3198dc047 1930 cmark_0.30.2-5.dsc 14e21979b684798ebf38ba8ff692fed3f3ad953e 10820 cmark_0.30.2-5.debian.tar.xz 5f12cac4901c46f2beca27e42c860f105a6a88c1 7999 cmark_0.30.2-5_amd64.buildinfo Checksums-Sha256: 6499f123357a065d9bd0350f8321ea4458cf7c5fb69efbfdfe5e2e82cabdd86b 1930 cmark_0.30.2-5.dsc b76a1f8c50a4a819cfe4242c5994ee6d3fa9fba2f82d205e77ef92caf1c86318 10820 cmark_0.30.2-5.debian.tar.xz 8add8f37627bbb8a73b834937864b95e0d4739d8ab8964da2fb6c4754bc0fa82 7999 cmark_0.30.2-5_amd64.buildinfo Files: 79aee63b8279f83186d6c5fbca69d85a 1930 text optional cmark_0.30.2-5.dsc 44eaaee144d7ec6e0e3392d37b53815a 10820 text optional cmark_0.30.2-5.debian.tar.xz b9fea7649920bf7499296eb53ccde7d4 7999 text optional cmark_0.30.2-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHzspsACgkQLHwxRsGg ASEWpQ//TkKKjQT5XCaVRY80eXQei1xypplo/iY2QHe75y0aKll0Sdj7dSGMAxBm uPPA/drRv22yrvfy6GfkLokcYBPY4HSFgy54TB0YEOy6vCebQuKgTuf1kGDGFTEf DSL8Iq2y6hLHrUsQXcUFgPvX
