Bug#1024795: python3-llvmlite: Depends from non-existing packages libllvm11 and llvm-11
Package: python3-llvmlite Severity: grave Justification: renders package unusable Hi, $ sudo apt install python3-llvmlite Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-llvmlite : Depends: llvm-11 but it is not installable Depends: libllvm11 (>= 1:9~svn298832-1~) but it is not installable E: Unable to correct problems, you have held broken packages. $ apt policy llvm-11 libllvm11 llvm-11: Installed: (none) Candidate: (none) Version table: libllvm11: Installed: (none) Candidate: (none) Version table: The lack of llvm-11 and libllvm11 makes python3-llvmlite uninstallable. Kind regards Andreas. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages python3-llvmlite depends on: ii libc6 2.36-5 pn libllvm11 ii libstdc++6 12.2.0-9 pn llvm-11 ii python3 3.10.6-3 python3-llvmlite recommends no packages. Versions of packages python3-llvmlite suggests: pn llvmlite-doc
Bug#1024677: marked as done (protobuf: autopkgtest failure (error: file not found: com/example/tutorial/AddressBookProtos.java))
Your message dated Fri, 25 Nov 2022 06:50:42 + with message-id and subject line Bug#1024677: fixed in protobuf 3.21.9-5 has caused the Debian Bug report #1024677, regarding protobuf: autopkgtest failure (error: file not found: com/example/tutorial/AddressBookProtos.java) 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.) -- 1024677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: protobuf Version: 3.21.9-3 Severity: serious Tags: upstream patch Control: block 1023535 by -1 Dear Maintainer, The autopkgtest for your package is failing: autopkgtest [02:27:53]: test simple: [--- *** Building example programs protoc $PROTO_PATH --cpp_out=. --java_out=. --python_out=. addressbook.proto pkg-config --cflags protobuf # fails if protobuf is not installed c++ -std=c++11 add_person.cc addressbook.pb.cc -o add_person_cpp `pkg-config --cflags --libs protobuf` pkg-config --cflags protobuf # fails if protobuf is not installed c++ -std=c++11 list_people.cc addressbook.pb.cc -o list_people_cpp `pkg-config --cflags --libs protobuf` javac -cp $CLASSPATH AddPerson.java ListPeople.java com/example/tutorial/AddressBookProtos.java error: file not found: com/example/tutorial/AddressBookProtos.java Usage: javac use --help for a list of possible options make: *** [Makefile:66: javac_middleman] Error 2 https://ci.debian.net/data/autopkgtest/unstable/amd64/p/protobuf/28586956/log.gz The attached patch fixes the issue by correcting the paths in the Makefile. Kind Regards, Bas --- a/examples/Makefile 2022-10-26 19:50:48.0 +0200 +++ b/examples/Makefile 2022-11-23 07:07:29.963242439 +0100 @@ -13,8 +13,8 @@ clean: rm -f add_person_cpp list_people_cpp add_person_java list_people_java add_person_python list_people_python - rm -f javac_middleman AddPerson*.class ListPeople*.class com/example/tutorial/*.class - rm -f protoc_middleman addressbook.pb.cc addressbook.pb.h addressbook_pb2.py com/example/tutorial/AddressBookProtos.java + rm -f javac_middleman AddPerson*.class ListPeople*.class com/example/tutorial/protos/*.class + rm -f protoc_middleman addressbook.pb.cc addressbook.pb.h addressbook_pb2.py com/example/tutorial/protos/*.java rm -f *.pyc rm -f go/tutorialpb/*.pb.go add_person_go list_people_go rm -f protoc_middleman_dart dart_tutorial/*.pb*.dart @@ -63,7 +63,7 @@ cd go && go test ./cmd/list_people javac_middleman: AddPerson.java ListPeople.java protoc_middleman - javac -cp $$CLASSPATH AddPerson.java ListPeople.java com/example/tutorial/AddressBookProtos.java + javac -cp $$CLASSPATH AddPerson.java ListPeople.java com/example/tutorial/protos/*.java @touch javac_middleman add_person_java: javac_middleman --- End Message --- --- Begin Message --- Source: protobuf Source-Version: 3.21.9-5 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of protobuf, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated protobuf 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, 25 Nov 2022 07:04:22 +0100 Source: protobuf Architecture: source Version: 3.21.9-5 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 1024677 Changes: protobuf (3.21.9-5) unstable; urgency=medium . * Backport upstream fix of Makefile rule for java target in examples (closes: #1024677). Checksums-Sha1: 2ff059528d2dc464f1912682965dff08e42dd3f4 3067 protobuf_3.21.9-5.dsc eef938cb2e097cb76b420f284cf9fa75bc60a783 30824 protobuf_3.21.9-5.debian.tar.xz Checksums-Sha256: b9814d62e96fbc870f4dd32243274a797fc6d22c21ea0a1d26729f86d0d13ce0 3067 protobuf_3.21.9-5.dsc 667b078b7b68fbba68bc782bfcf992d74e2619924b70a1fce3f53709a51f9f25 30824 protobuf_3.21.9-5.debian.tar.xz Files: fac62d14675e46565e0ada160aa77487 3067 devel
Bug#1021846: [programmer11...@programist.ru: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem]
Hi Steve, It seems invalid Commit id which you reported. It should be 4bd9877f62166b7e369773ab92fe24a39f6515f8 did you applied below patch and tested? Could you please confirm that. fs/f2fs: Do not read past the end of nat journal entries https://git.savannah.gnu.org/cgit/grub.git/patch/?id=4bd9877f62166b7e369773ab92fe24a39f6515f8 thanks, Sudhakar Kuppusamy On 2022-11-24 20:39, Daniel Kiper wrote: Adding Daniel Axtens... On Tue, Nov 15, 2022 at 06:31:45PM +, Steve McIntyre wrote: Hi all! программист некто (in CC) reported this bug a few weeks back in Debian. Since I applied the bundle of filesystem bounds-checking fixes a few months back, he can't run grub-install. He's done the work to determine that the patch that breaks things for him is 2d014248d540c7e087934a94b6e7a2aa7fc2c704 fs/f2fs: Do not read past the end of nat journal entries The full thread of our discussion is at https://bugs.debian.org/1021846 I don't have any knowledge of f2fs to go any further here. Help please! :-) - Forwarded message from программист некто - From: программист некто To: sub...@bugs.debian.org Date: Sat, 15 Oct 2022 23:54:36 +0300 Subject: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem Message-Id: <3168731665867...@wf4nrjvtssjecb53.iva.yp-c.yandex.net> Package: grub-pc Version: 2.06-3~deb11u1 Severity: critical Hello. Since version 2.06-3, grub-install is broken: it fails with "error: unknown filesystem". I test command /usr/sbin/grub-install -v /dev/sda in some versions. Results in mail attachments. Versions older than 2.06-3 works without error (2.06-2 and lower). Tested versions: 2.04-20, 2.06-1, 2.06-2, 2.06-3~deb10u1, 2.06-3~deb11u1, 2.06-4. Disk partitions: # fdisk --list-details Disk /dev/sda: 29,82 GiB, 32017047552 bytes, 62533296 sectors Disk model: TS32GSSD370S Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc7177f7e Device Boot Start End Sectors Id Type Start-C/H/S End-C/H/S Attrs /dev/sda1 2048 22763519 22761472 83 Linux 4/4/1 1023/254/2 /dev/sda2 * 25866240 62531583 36665344 7 HPFS/ 1023/254/2 1023/254/2 80 $ disktype /dev/sda1 --- /dev/sda1 Block device, size 10.85 GiB (11653873664 bytes) F2FS file system (version 1.14) $ disktype /dev/sda2 --- /dev/sda2 Block device, size 17.48 GiB (18772656128 bytes) NTFS file system Volume size 17.48 GiB (18772652032 bytes, 36665336 sectors) - End forwarded message - -- Steve McIntyre, Cambridge, UK. st...@einval.com Mature Sporty Personal More Innovation More Adult A Man in Dandism Powered Midship Specialty
Bug#1024790: ortools: FTBFS everywhere
Source: ortools Version: 8.2+ds-6 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=ortools=amd64=8.2%2Bds-6%2Bb2=1669159851=0 make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f ortools/sat/python/CMakeFiles/pywrapsat_swig_compilation.dir/build.make ortools/sat/python/CMakeFiles/pywrapsat_swig_compilation.dir/build [ 4%] Generate C++ protocol buffer for ortools/sat/cp_model.proto /usr/bin/protoc --proto_path=/<> --proto_path=/usr/include --cpp_out=/<>/obj-x86_64-linux-gnu ortools/sat/cp_model.proto make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 5%] Swig compile sat.i for python cd /<>/obj-x86_64-linux-gnu/ortools/sat/python && /usr/bin/cmake -E make_directory /<>/obj-x86_64-linux-gnu/ortools/sat/python/CMakeFiles/pywrapsat.dir /<>/obj-x86_64-linux-gnu/python/ortools/sat /<>/obj-x86_64-linux-gnu/python/ortools/sat cd /<>/obj-x86_64-linux-gnu/ortools/sat/python && /usr/bin/cmake -E touch /<>/obj-x86_64-linux-gnu/ortools/sat/python/CMakeFiles/pywrapsat.dir/satPYTHON.stamp /<>/ortools/linear_solver/linear_solver.h:766: Error: Syntax error in input(3). make[4]: *** [ortools/linear_solver/python/CMakeFiles/pywraplp_swig_compilation.dir/build.make:79: ortools/linear_solver/python/CMakeFiles/pywraplp.dir/linear_solverPYTHON.stamp] Error 1 make[4]: *** Deleting file 'ortools/linear_solver/python/CMakeFiles/pywraplp.dir/linear_solverPYTHON.stamp' make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[3]: *** [CMakeFiles/Makefile2:1400: ortools/linear_solver/python/CMakeFiles/pywraplp_swig_compilation.dir/all] Error 2 make[3]: *** Waiting for unfinished jobs Cheers -- Sebastian Ramacher
Bug#1022307: status on t_coffee causing biopython ftbfs
Hi Nilesh, Nilesh Patra, on 2022-11-23: > On Wed, 23 Nov 2022 15:07:32 +0200 Andrius Merkys wrote: > > On Tue, 22 Nov 2022 23:54:48 +0100 =?utf-8?Q?=C3=89tienne?= Mollier > > wrote: > > > Hi, mostly retitling the open entry against biopython for the > > > sake of clarity, and also pinging both bugs to reset auto- > > > removal counters. We don't have much news from t_coffee > > > upstream to day unfortunately. Maybe it will be necessary to > > > revert the t-coffee version bump for the upcoming Debian release > > > or do people see other options? > > > > This issue is blocking Python 3.11-add transition, but we surely do not > > want biopython to be dropped from testing. However, the problem is not > > with biopython, but with t-coffee which biopython merely uses for tests. > > Would it be acceptable to skip t-coffee tests for now thus unblocking > > Python 3.11-add transition? > > This bug report should remain open to remind > > us bring t-coffee tests back once #1022570 is solved. > > That sounds quite a reasonable thing to do, but we probably should also > decrese the severity of this bug to "important" to let biopython be in testing > once the corresponding tests are skipped. > > Étienne, what do you think? I removed the build-dependency on t-coffee for the experimental upload of biopython 1.80 in order to get tests to go through. This skips the faulty test in biopython. t-coffee merely enhances biopython, and I don't believe it would impede the overall usability of the module. It will be possible to reduce the severity of the bug once one migrates python-biopython to sid. If in the meantime t-coffee gets fixed or reverted, then we could even restore the tests and close the bug. Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. On air: Supertramp - Even in the Quietest Moments signature.asc Description: PGP signature
Bug#1012950: itk-4.y buildability status
Control: severity 1012950 important Control: tags 1012950 - pending Hi, I reduce the severity of ITK4 ftbfs with introduction of gcc-12, since the package in its current form now uses gcc-11 only, and thus builds through. I also remove the tag pending upload since the initial problem is still unresolved. If I made a mistake by reducing the severity, feel free to re-raise it. I don't expect to push much further for ITK4. In hope this helps, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. On air: Genesis - White Mountain signature.asc Description: PGP signature
Processed: Re: itk-4.y buildability status
Processing control commands: > severity 1012950 important Bug #1012950 [src:insighttoolkit4] insighttoolkit4: ftbfs with GCC-12 Severity set to 'important' from 'serious' > tags 1012950 - pending Bug #1012950 [src:insighttoolkit4] insighttoolkit4: ftbfs with GCC-12 Removed tag(s) pending. -- 1012950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024786: aionotify: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Source: aionotify Version: 0.2.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of aionotify fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 aionotify from testing0.2.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. E.g.: """ Removed the @asyncio.coroutine() decorator enabling legacy generator-based coroutines to be compatible with async / await code. The function has been deprecated since Python 3.8 and the removal was initially scheduled for Python 3.10. Use async def instead. (Contributed by Illia Volochii in bpo-43216.) """ More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/a/aionotify/28628638/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/aionotify/__init__.py", line 5, in from .base import Watcher File "/usr/lib/python3/dist-packages/aionotify/base.py", line 10, in from . import aioutils File "/usr/lib/python3/dist-packages/aionotify/aioutils.py", line 122, in @asyncio.coroutine ^ AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'? autopkgtest [12:13:03]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Processed: aionotify: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Processing control commands: > affects -1 src:python3-defaults Bug #1024786 [src:aionotify] aionotify: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Added indication that 1024786 affects src:python3-defaults -- 1024786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024785: supysonic: (autopkgtest) needs update for python3.11: DecompileError: Unsupported operation
Source: supysonic
Version: 0.7.2+ds-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
supysonic fails in testing when that autopkgtest is run with the binary
packages of python3-defaults from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
supysonic from testing0.7.2+ds-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 of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/armel/s/supysonic/28609595/log.gz
==
ERROR: test_get_album_list
(tests.api.test_album_songs.AlbumSongsTestCase.test_get_album_list)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.umijt0w4/downtmp/autopkgtest_tmp/tests/api/test_album_songs.py",
line 61, in test_get_album_list
self._make_request("getAlbumList", {"type": "kraken"}, error=0)
File
"/tmp/autopkgtest-lxc.umijt0w4/downtmp/autopkgtest_tmp/tests/api/apitestbase.py",
line 74, in _make_request
rg = self.client.get(uri, query_string=args)
^^^
File "/usr/lib/python3/dist-packages/werkzeug/test.py", line 1129, in get
return self.open(*args, **kw)
^^
File "/usr/lib/python3/dist-packages/flask/testing.py", line 235, in open
return super().open(
^
File "/usr/lib/python3/dist-packages/werkzeug/test.py", line 1074, in
open
response = self.run_wsgi_app(request.environ, buffered=buffered)
^
File "/usr/lib/python3/dist-packages/werkzeug/test.py", line 945, in
run_wsgi_app
rv = run_wsgi_app(self.application, environ, buffered=buffered)
^^
File "/usr/lib/python3/dist-packages/werkzeug/test.py", line 1231, in
run_wsgi_app
app_rv = app(environ, start_response)
File "/usr/lib/python3/dist-packages/flask/app.py", line 2091, in
__call__
return self.wsgi_app(environ, start_response)
^^
File "/usr/lib/python3/dist-packages/pony/utils/utils.py", line 35,
in pony_wrapper
return caller(func, *args, **kwargs)
^
File "/usr/lib/python3/dist-packages/pony/orm/core.py", line 519, in
new_func
result = func(*args, **kwargs)
^
File "/usr/lib/python3/dist-packages/flask/app.py", line 2076, in
wsgi_app
response = self.handle_exception(e)
File "/usr/lib/python3/dist-packages/flask/app.py", line 2073, in
wsgi_app
response = self.full_dispatch_request()
File "/usr/lib/python3/dist-packages/flask/app.py", line 1518, in
full_dispatch_request
rv = self.handle_user_exception(e)
^
File "/usr/lib/python3/dist-packages/flask/app.py", line 1516, in
full_dispatch_request
rv = self.dispatch_request()
^^^
File "/usr/lib/python3/dist-packages/flask/app.py", line 1502, in
dispatch_request
return
self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
^
File "/usr/lib/python3/dist-packages/supysonic/api/albums_songs.py",
line 77, in album_list
query = select(t.folder for t in Track)
^^^
File "/usr/lib/python3/dist-packages/pony/orm/core.py", line 5560, in
select
return make_query(args, frame_depth=cut_traceback_depth+1)
^^^
File "/usr/lib/python3/dist-packages/pony/orm/core.py", line 5546, in
make_query
tree, external_names, cells = decompile(gen)
^^
File "/usr/lib/python3/dist-packages/pony/orm/decompiling.py",
Processed: supysonic: (autopkgtest) needs update for python3.11: DecompileError: Unsupported operation
Processing control commands: > affects -1 src:python3-defaults Bug #1024785 [src:supysonic] supysonic: (autopkgtest) needs update for python3.11: DecompileError: Unsupported operation Added indication that 1024785 affects src:python3-defaults -- 1024785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024784: swift: (autopkgtest) needs update for python3.11: Segmentation fault
Source: swift Version: 2.30.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of swift fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 swift from testing2.30.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/s390x/s/swift/28606516/log.gz + py3versions -vr + python3.11 -m nose test/unit -v --exclude-test=test.unit.common.test_utils.TestUtils.test_get_logger_sysloghandler_plumbing --exclude-test=test.unit.common.middleware.test_cname_lookup.TestCNAMELookup --exclude-test=test.unit.common.test_db.TestDatabaseBroker.test_get --exclude-test=test.unit.container.test_sync.TestContainerSync.test_init --exclude-test=test.unit.common.test_utils.TestPunchHoleReally.test_punch_a_hole --exclude-test=test.unit.common.test_utils.Test_LibcWrapper.test_argument_plumbing nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] nose.plugins.xcover: INFO: Coverage report will include only packages: ['swift'] nose.plugins.cover: INFO: Coverage report will include only packages: ['swift'] Unable to read test config /etc/swift/test.conf - file not found test_db_validate_fails (test.unit.account.test_auditor.TestAuditorRealBroker.test_db_validate_fails) ... Segmentation fault autopkgtest [14:04:13]: test unittests OpenPGP_signature Description: OpenPGP digital signature
Processed: swift: (autopkgtest) needs update for python3.11: Segmentation fault
Processing control commands: > affects -1 src:python3-defaults Bug #1024784 [src:swift] swift: (autopkgtest) needs update for python3.11: Segmentation fault Added indication that 1024784 affects src:python3-defaults -- 1024784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024783: ironic: (autopkgtest) needs update for python3.11: Cannot spec a Mock object
Source: ironic
Version: 1:21.1.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
ironic fails in testing when that autopkgtest is run with the binary
packages of python3-defaults from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
ironic from testing1:21.1.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/s390x/i/ironic/28630776/log.gz
==
FAIL:
ironic.tests.unit.drivers.modules.irmc.test_inspect.IRMCInspectTestCase.test_inspect_hardware
ironic.tests.unit.drivers.modules.irmc.test_inspect.IRMCInspectTestCase.test_inspect_hardware
--
testtools.testresult.real._StringException: Traceback (most recent call
last):
File "/usr/lib/python3.11/unittest/mock.py", line 1369, in patched
return func(*newargs, **newkeywargs)
^
File
"/tmp/autopkgtest-lxc.xfyi6n2m/downtmp/build.Dl6/src/ironic/tests/unit/drivers/modules/irmc/test_inspect.py",
line 207, in test_inspect_hardware
new_port_mock1 = mock.MagicMock(spec=objects.Port)
^
File "/usr/lib/python3.11/unittest/mock.py", line 2082, in __init__
_safe_super(MagicMixin, self).__init__(*args, **kw)
File "/usr/lib/python3.11/unittest/mock.py", line 1100, in __init__
_safe_super(CallableMixin, self).__init__(
File "/usr/lib/python3.11/unittest/mock.py", line 451, in __init__
self._mock_add_spec(spec, spec_set, _spec_as_instance, _eat_self)
File "/usr/lib/python3.11/unittest/mock.py", line 502, in _mock_add_spec
raise InvalidSpecError(f'Cannot spec a Mock object. [object={spec!r}]')
unittest.mock.InvalidSpecError: Cannot spec a Mock object.
[object=]
==
FAIL:
ironic.tests.unit.drivers.modules.irmc.test_inspect.IRMCInspectTestCase.test_inspect_hardware_with_power_off
ironic.tests.unit.drivers.modules.irmc.test_inspect.IRMCInspectTestCase.test_inspect_hardware_with_power_off
--
testtools.testresult.real._StringException: Traceback (most recent call
last):
File "/usr/lib/python3.11/unittest/mock.py", line 1369, in patched
return func(*newargs, **newkeywargs)
^
File
"/tmp/autopkgtest-lxc.xfyi6n2m/downtmp/build.Dl6/src/ironic/tests/unit/drivers/modules/irmc/test_inspect.py",
line 262, in test_inspect_hardware_with_power_off
new_port_mock1 = mock.MagicMock(spec=objects.Port)
^
File "/usr/lib/python3.11/unittest/mock.py", line 2082, in __init__
_safe_super(MagicMixin, self).__init__(*args, **kw)
File "/usr/lib/python3.11/unittest/mock.py", line 1100, in __init__
_safe_super(CallableMixin, self).__init__(
File "/usr/lib/python3.11/unittest/mock.py", line 451, in __init__
self._mock_add_spec(spec, spec_set, _spec_as_instance, _eat_self)
File "/usr/lib/python3.11/unittest/mock.py", line 502, in _mock_add_spec
raise InvalidSpecError(f'Cannot spec a Mock object. [object={spec!r}]')
unittest.mock.InvalidSpecError: Cannot spec a Mock object.
[object=]
--
Ran 8768 tests in 240.038s
FAILED (failures=2, skipped=44)
OpenPGP_signature
Description: OpenPGP digital signature
Processed: ironic: (autopkgtest) needs update for python3.11: Cannot spec a Mock object
Processing control commands: > affects -1 src:python3-defaults Bug #1024783 [src:ironic] ironic: (autopkgtest) needs update for python3.11: Cannot spec a Mock object Added indication that 1024783 affects src:python3-defaults -- 1024783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024781: python-molotov: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Source: python-molotov
Version: 2.1-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
python-molotov fails in testing when that autopkgtest is run with the
binary packages of python3-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
python-molotov from testing2.1-4
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be
updated. E.g.:
"""
Removed the @asyncio.coroutine() decorator enabling legacy
generator-based coroutines to be compatible with async / await code. The
function has been deprecated since Python 3.8 and the removal was
initially scheduled for Python 3.10. Use async def instead. (Contributed
by Illia Volochii in bpo-43216.)
"""
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-molotov/28600688/log.gz
=== FAILURES
===
TestUtil.test_can_call
args = (,), kw
= {}
@functools.wraps(func)
def _async_test(*args, **kw):
cofunc = asyncio.coroutine(func)
E AttributeError: module 'asyncio' has no attribute 'coroutine'
molotov/tests/support.py:242: AttributeError
TestFmwk.test_aworker
_
args = (,), kw
= {}
@functools.wraps(func)
def _async_test(*args, **kw):
cofunc = asyncio.coroutine(func)
E AttributeError: module 'asyncio' has no attribute 'coroutine'
molotov/tests/support.py:242: AttributeError
_ TestFmwk.test_aworker_noexc
__
args = (,)
kw = {}
@functools.wraps(func)
def _async_test(*args, **kw):
cofunc = asyncio.coroutine(func)
E AttributeError: module 'asyncio' has no attribute 'coroutine'
molotov/tests/support.py:242: AttributeError
__ TestFmwk.test_failing_step
__
args = (,)
kw = {}
@functools.wraps(func)
def _async_test(*args, **kw):
cofunc = asyncio.coroutine(func)
E AttributeError: module 'asyncio' has no attribute 'coroutine'
molotov/tests/support.py:242: AttributeError
TestFmwk.test_failure
_
args = (,), kw
= {}
@functools.wraps(func)
def _async_test(*args, **kw):
cofunc = asyncio.coroutine(func)
E AttributeError: module 'asyncio' has no attribute 'coroutine'
molotov/tests/support.py:242: AttributeError
_ TestFmwk.test_picker
_
args = (,), kw = {}
@functools.wraps(func)
def _async_test(*args, **kw):
cofunc = asyncio.coroutine(func)
E AttributeError: module 'asyncio' has no attribute 'coroutine'
molotov/tests/support.py:242: AttributeError
___ TestFmwk.test_session_shutdown_exception
___
args = (testMethod=test_session_shutdown_exception>,)
kw = {}
@functools.wraps(func)
def _async_test(*args, **kw):
cofunc = asyncio.coroutine(func)
E AttributeError: module 'asyncio' has no attribute 'coroutine'
molotov/tests/support.py:242: AttributeError
TestFmwk.test_setup_session_fresh_loop
args = (testMethod=test_setup_session_fresh_loop>,)
kw = {}
@functools.wraps(func)
def _async_test(*args, **kw):
cofunc = asyncio.coroutine(func)
E AttributeError: module 'asyncio' has no attribute 'coroutine'
molotov/tests/support.py:242: AttributeError
__ TestFmwk.test_step
__
args = (,), kw = {}
@functools.wraps(func)
def _async_test(*args, **kw):
cofunc = asyncio.coroutine(func)
E AttributeError: module 'asyncio' has no attribute 'coroutine'
molotov/tests/support.py:242: AttributeError
___ TestListeners.test_add_listener
args = (testMethod=test_add_listener>,)
kw = {}
@functools.wraps(func)
def _async_test(*args, **kw):
Processed: python-molotov: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'
Processing control commands: > affects -1 src:python3-defaults Bug #1024781 [src:python-molotov] python-molotov: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Added indication that 1024781 affects src:python3-defaults -- 1024781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024780: msxpertsuite: FTBFS with new qcustomplot
Source: msxpertsuite Version: 5.8.9-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=msxpertsuite=amd64=5.8.9-1%2Bb1=1669196043=0 [ 70%] Building CXX object massxpert/CMakeFiles/massxpert.dir/qrc_application.cpp.o [ 70%] Linking CXX executable massxpert /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -Wl,-z,relro -rdynamic CMakeFiles/massxpert.dir/massxpert_autogen/mocs_compilation.cpp.o CMakeFiles/massxpert.dir/nongui/CalcOptions.cpp.o CMakeFiles/massxpert.dir/nongui/ChemEntVignette.cpp.o CMakeFiles/massxpert.dir/nongui/ChemEntVignetteRenderer.cpp.o CMakeFiles/massxpert.dir/nongui/ChemicalGroup.cpp.o CMakeFiles/massxpert.dir/nongui/ChemicalGroupRule.cpp.o CMakeFiles/massxpert.dir/nongui/CleaveMotif.cpp.o CMakeFiles/massxpert.dir/nongui/CleaveOligomer.cpp.o CMakeFiles/massxpert.dir/nongui/CleaveOptions.cpp.o CMakeFiles/massxpert.dir/nongui/CleaveRule.cpp.o CMakeFiles/massxpert.dir/nongui/CleaveSpec.cpp.o CMakeFiles/massxpert.dir/nongui/Cleaver.cpp.o CMakeFiles/massxpert.dir/nongui/ConfigSetting.cpp.o CMakeFiles/massxpert.dir/nongui/ConfigSettings.cpp.o CMakeFiles/massxpert.dir/nongui/Coordinates.cpp.o CMakeFiles/massxpert.dir/nongui/CrossLink.cpp.o CMakeFiles/massxpert.dir/nongui/CrossLinkList.cpp.o CMakeFiles/massxpert.dir/nongui/CrossLinkedRegion.cpp.o CMakeFiles/massxpert.dir/nongui/CrossLinker.cpp.o CMakeFiles/massxpert.dir/nongui/CrossLinkerSpec.cpp.o CMakeFiles/massxpert.dir/nongui/FragOptions.cpp.o CMakeFiles/massxpert.dir/nongui/FragRule.cpp.o CMakeFiles/massxpert.dir/nongui/FragSpec.cpp.o CMakeFiles/massxpert.dir/nongui/Fragmenter.cpp.o CMakeFiles/massxpert.dir/nongui/Ionizable.cpp.o CMakeFiles/massxpert.dir/nongui/Modif.cpp.o CMakeFiles/massxpert.dir/nongui/ModifSpec.cpp.o CMakeFiles/massxpert.dir/nongui/Monomer.cpp.o CMakeFiles/massxpert.dir/nongui/MonomerDictionary.cpp.o CMakeFiles/massxpert.dir/nongui/MonomerSpec.cpp.o CMakeFiles/massxpert.dir/nongui/Oligomer.cpp.o CMakeFiles/massxpert.dir/nongui/OligomerList.cpp.o CMakeFiles/massxpert.dir/nongui/OligomerPair.cpp.o CMakeFiles/massxpert.dir/nongui/PkaPhPi.cpp.o CMakeFiles/massxpert.dir/nongui/PkaPhPiDataParser.cpp.o CMakeFiles/massxpert.dir/nongui/PolChemDef.cpp.o CMakeFiles/massxpert.dir/nongui/PolChemDefCatParser.cpp.o CMakeFiles/massxpert.dir/nongui/PolChemDefEntity.cpp.o CMakeFiles/massxpert.dir/nongui/PolChemDefSpec.cpp.o CMakeFiles/massxpert.dir/nongui/Polymer.cpp.o CMakeFiles/massxpert.dir/nongui/Prop.cpp.o CMakeFiles/massxpert.dir/nongui/PropListHolder.cpp.o CMakeFiles/massxpert.dir/nongui/Sequence.cpp.o CMakeFiles/massxpert.dir/nongui/globals.cpp.o CMakeFiles/massxpert.dir/gui/AboutMassXpertDlg.cpp.o CMakeFiles/massxpert.dir/gui/AbstractMainTaskWindow.cpp.o CMakeFiles/massxpert.dir/gui/AbstractPolChemDefDependentDlg.cpp.o CMakeFiles/massxpert.dir/gui/AbstractSeqEdWndDependentDlg.cpp.o CMakeFiles/massxpert.dir/gui/Application.cpp.o CMakeFiles/massxpert.dir/gui/AtomDefDlg.cpp.o CMakeFiles/massxpert.dir/gui/CalculatorChemPadDlg.cpp.o CMakeFiles/massxpert.dir/gui/CalculatorChemPadGroupBox.cpp.o CMakeFiles/massxpert.dir/gui/CalculatorRecorderDlg.cpp.o CMakeFiles/massxpert.dir/gui/CalculatorWnd.cpp.o CMakeFiles/massxpert.dir/gui/ChemPadButton.cpp.o CMakeFiles/massxpert.dir/gui/CleavageDlg.cpp.o CMakeFiles/massxpert.dir/gui/CleaveOligomerTableView.cpp.o CMakeFiles/massxpert.dir/gui/CleaveOligomerTableViewMimeData.cpp.o CMakeFiles/massxpert.dir/gui/CleaveOligomerTableViewModel.cpp.o CMakeFiles/massxpert.dir/gui/CleaveOligomerTableViewSortProxyModel.cpp.o CMakeFiles/massxpert.dir/gui/CleaveSpecDefDlg.cpp.o CMakeFiles/massxpert.dir/gui/CompositionTreeView.cpp.o CMakeFiles/massxpert.dir/gui/CompositionTreeViewItem.cpp.o CMakeFiles/massxpert.dir/gui/CompositionTreeViewModel.cpp.o CMakeFiles/massxpert.dir/gui/CompositionTreeViewSortProxyModel.cpp.o CMakeFiles/massxpert.dir/gui/CompositionsDlg.cpp.o CMakeFiles/massxpert.dir/gui/ConfigSettingsDlg.cpp.o CMakeFiles/massxpert.dir/gui/CrossLinkerDefDlg.cpp.o CMakeFiles/massxpert.dir/gui/DecimalPlacesOptionsDlg.cpp.o CMakeFiles/massxpert.dir/gui/FragSpecDefDlg.cpp.o CMakeFiles/massxpert.dir/gui/FragmentOligomerTableView.cpp.o CMakeFiles/massxpert.dir/gui/FragmentOligomerTableViewMimeData.cpp.o CMakeFiles/massxpert.dir/gui/FragmentOligomerTableViewModel.cpp.o CMakeFiles/massxpert.dir/gui/FragmentOligomerTableViewSortProxyModel.cpp.o CMakeFiles/massxpert.dir/gui/FragmentationDlg.cpp.o CMakeFiles/massxpert.dir/gui/MainWindow.cpp.o CMakeFiles/massxpert.dir/gui/MassListSorterDlg.cpp.o CMakeFiles/massxpert.dir/gui/MassSearchDlg.cpp.o CMakeFiles/massxpert.dir/gui/MassSearchOligomerTableView.cpp.o CMakeFiles/massxpert.dir/gui/MassSearchOligomerTableViewMimeData.cpp.o
Bug#1024768: marked as done (libphonenumber: FTBFS after switch to debhelper)
Your message dated Thu, 24 Nov 2022 19:34:37 + with message-id and subject line Bug#1024768: fixed in libphonenumber 8.12.57+ds-3 has caused the Debian Bug report #1024768, regarding libphonenumber: FTBFS after switch to debhelper 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.) -- 1024768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libphonenumber Version: 8.12.57+ds-2 Severity: serious Creating this for tracking and coordination purposes. After this [1] upload, libphonenumber is FTBFS. Please refer to the buildd logs [2]. [1] https://tracker.debian.org/news/1389357/accepted-libphonenumber-81257ds-2-source-into-unstable/ [2] https://buildd.debian.org/status/package.php?p=libphonenumber --- End Message --- --- Begin Message --- Source: libphonenumber Source-Version: 8.12.57+ds-3 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of libphonenumber, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated libphonenumber 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, 24 Nov 2022 20:17:13 +0100 Source: libphonenumber Architecture: source Version: 8.12.57+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Jochen Sprickerhof Closes: 1017496 1024768 Changes: libphonenumber (8.12.57+ds-3) unstable; urgency=medium . * Team upload. * Add patch to link geocoding-shared with phonenumber-shared (Closes: #1017496) * Build java lib in arch any builds (Closes: #1024768) Checksums-Sha1: 065489aca6dce6b8b69fc97a177a07d0530168d8 2899 libphonenumber_8.12.57+ds-3.dsc 1855daa06b545e888fe50b9580cb1f327b44095a 12300 libphonenumber_8.12.57+ds-3.debian.tar.xz ea9df596790089aa556b8146236d6afcfc8be5e5 19103 libphonenumber_8.12.57+ds-3_source.buildinfo Checksums-Sha256: 8d7bc92ef866c125aa39c52ce8c2ae20b5f2243c7754012a2ec73cee98d9a0e2 2899 libphonenumber_8.12.57+ds-3.dsc 77cb18483834a5a0c22e55bb1a094eac6a698d47a382685f649503468fa09814 12300 libphonenumber_8.12.57+ds-3.debian.tar.xz c2487f189b6d29a21c42bd4c89fd007f5eeed23ed84052c89ad5e344acb7e6ec 19103 libphonenumber_8.12.57+ds-3_source.buildinfo Files: 9e21728dc2664939e0761101551a3acc 2899 libs optional libphonenumber_8.12.57+ds-3.dsc 48c9e64a3d6b167cf60e039cff53e663 12300 libs optional libphonenumber_8.12.57+ds-3.debian.tar.xz c53b6759e7675e49f22b80247c10ee80 19103 libs optional libphonenumber_8.12.57+ds-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmN/w14ACgkQW//cwljm lDPTqxAAnTk0z99iIIhQLJ+WKLb1o3RkSRCq/tWS8j7aJVjYpdY6jyQIxf3SZ2d4 nv6I7qHuERW/o+FcHjs0Ie0VCvIGl2bWU3v+dYAREE/jY+lPzPD3UObo4prLLG86 fT9R+RPqGnVfsgPPQc0YUhYUKPLtUgeoJBOd6BNKcElJ7jRWlk4Q5jXat6Gp6bz3 tOdhOoaO4swIEkLCYiBQ6argx8A363npV3xWwJ4eVZ5cM36QKhHwf1vunvbnTeMu +0AFALioSObWORCz8bzHAQVKNCjV51ViCV/E4nAKrT8zdbysQgUVJMFrxPa9Wty6 nvB2Dnev1D0byngKfJV5zACYSPMWcmJ63Wyuan2GBfQCuq5QjEBLQn+C6P2yI8a9 kmqUsNNCp7r62diWXhLrhWRyksxuquot8dXSwoGebmzTPZifboCTLTVw23ztS9e+ EqzKVaEUAWrb8kCOCmGfYStthoq7whRij35lTDTc5Ekq2OpeLOCC83+kdnxMKP/9 lfICPVoUWOi5SGXEmVGJ0J2zkESrhX7qahJlD0V15Bqw+yTn4KYvYQm0UOqsDAYz AAUlhioCKqZHVM+qzTUrW8R+OgVjY68Tj/jNa33KYhcOa8PZuhUoeD7yaMjqTat5 5jCPTztn0j/BeayDXCwjg2QJD43dNwhenpRzXlbG8aRW4/kJweI= =kMsB -END PGP SIGNATURE End Message ---
Processed: Re: [Pkg-utopia-maintainers] Bug#1024699: volume-key: Testsuite error on local rebuild
Processing control commands: > tags -1 + moreinfo unreproducible Bug #1024699 [src:volume-key] volume-key: Testsuite error on local rebuild Added tag(s) unreproducible and moreinfo. > severity -1 normal Bug #1024699 [src:volume-key] volume-key: Testsuite error on local rebuild Severity set to 'normal' from 'serious' -- 1024699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024699: [Pkg-utopia-maintainers] Bug#1024699: volume-key: Testsuite error on local rebuild
Control: tags -1 + moreinfo unreproducible Control: severity -1 normal Am 23.11.22 um 13:18 schrieb Andreas Metzler: Source: volume-key Version: 0.3.12-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, volume-key FTBFS on current sid: FAIL: packet_roundtrips.sh Please provide instructions how this issue can be reproduced Michael OpenPGP_signature Description: OpenPGP digital signature
Processed: bug 1023788 is forwarded to https://savannah.nongnu.org/bugs/index.php?63413
Processing commands for cont...@bugs.debian.org: > forwarded 1023788 https://savannah.nongnu.org/bugs/index.php?63413 Bug #1023788 [src:getfem] getfem: fails to build from source on s390x Set Bug forwarded-to-address to 'https://savannah.nongnu.org/bugs/index.php?63413'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1023788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: update bts meta ifno
Processing commands for cont...@bugs.debian.org:
> reassign 1024169 src:csound 1:6.18.0+dfsg-2
Bug #1024169 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:csound, src:csound-plugins] csound breaks csound-plugins autopkgtest: ***
stack smashing detected ***: terminated
Bug reassigned from package 'src:csound, src:csound-plugins' to 'src:csound'.
No longer marked as found in versions csound-plugins/1.0.2~dfsg1-2 and
csound/1:6.18.0+dfsg-2.
No longer marked as fixed in versions csound/1:6.18.1+dfsg-1.
Bug #1024169 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:csound] csound breaks csound-plugins autopkgtest: *** stack smashing
detected ***: terminated
Marked as found in versions csound/1:6.18.0+dfsg-2.
> affects 1024169 src:csound-plugins
Bug #1024169 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:csound] csound breaks csound-plugins autopkgtest: *** stack smashing
detected ***: terminated
Added indication that 1024169 affects src:csound-plugins
> fixed 1024169 1:6.18.1+dfsg-1
Bug #1024169 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:csound] csound breaks csound-plugins autopkgtest: *** stack smashing
detected ***: terminated
The source 'csound' and version '1:6.18.1+dfsg-1' do not appear to match any
binary packages
Marked as fixed in versions csound/1:6.18.1+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1024169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1023738: orthanc-dicomweb FTBFS with node-axios 1.1
Dear Étienne and Nilesh, On 24/11/22 17:25, Étienne Mollier wrote: Control: tags -1 - patch Hi Nilesh, Nilesh Patra, on 2022-11-24: On Fri, 18 Nov 2022 22:48:42 +0100 =?utf-8?Q?=C3=89tienne?= Mollier wrote: orthanc-dicomweb is currently affected by a failure to build from source (Bug#1023738). I took the liberty to have a look, and it seems that since axios 1.0 the dist/axios.map file is not provided anymore. [...] However axios code has changed a bit since last version and so has the sourcemap file. This needs to be tested with orthanc-dicomweb (if it is even compatible) [...] Thanks for checking in depth, I remove the "patch" tag for now. But Sebastian is the best judge. Please let us know. Many thanks for your great help with this issue! Sorry for not answering earlier, but I'm still in the process of finalizing the GNU Health / Orthanc conference, and I'm extremely busy with my academic activities. I'll have a look by Wednesday 30th November. Kind Regards, Sébastien-
Bug#1022387: marked as done (dxf2gcode: FTBFS: dh_usrlocal: error: debian/dxf2gcode/usr/local/bin/dxf2gcode is not a directory)
Your message dated Thu, 24 Nov 2022 16:34:56 + with message-id and subject line Bug#1022387: fixed in dxf2gcode 20170925-5 has caused the Debian Bug report #1022387, regarding dxf2gcode: FTBFS: dh_usrlocal: error: debian/dxf2gcode/usr/local/bin/dxf2gcode is not a directory 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.) -- 1022387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dxf2gcode Version: 20170925-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > python3 ./st-setup.py install --prefix=usr --install-lib > usr/lib/python3/dist-packages --root=debian/dxf2gcode > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > running egg_info > writing dxf2gcode.egg-info/PKG-INFO > writing dependency_links to dxf2gcode.egg-info/dependency_links.txt > writing requirements to dxf2gcode.egg-info/requires.txt > writing top-level names to dxf2gcode.egg-info/top_level.txt > reading manifest file 'dxf2gcode.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'COPYING' > writing manifest file 'dxf2gcode.egg-info/SOURCES.txt' > running build_scripts > running install_lib > creating debian/dxf2gcode > creating debian/dxf2gcode/usr > creating debian/dxf2gcode/usr/lib > creating debian/dxf2gcode/usr/lib/python3 > creating debian/dxf2gcode/usr/lib/python3/dist-packages > copying build/lib/dxf2gcode_ui5.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages > copying build/lib/dxf2gcode_images5_rc.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages > creating debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode > copying build/lib/dxf2gcode/__init__.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode > creating debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/__init__.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/canvas.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/canvas2d.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/configwindow.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/routetext.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/treeview.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/wpzero.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/aboutdialog.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/messagebox.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/popupdialog.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/arrow.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/canvas3d.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > copying build/lib/dxf2gcode/gui/treehandling.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/gui > creating debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro > copying build/lib/dxf2gcode/postpro/__init__.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro > copying build/lib/dxf2gcode/postpro/tspoptimisation.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro > copying build/lib/dxf2gcode/postpro/postprocessor.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro > copying build/lib/dxf2gcode/postpro/breaks.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro > copying build/lib/dxf2gcode/postpro/postprocessorconfig.py -> > debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/postpro > creating debian/dxf2gcode/usr/lib/python3/dist-packages/dxf2gcode/dxfimport > copying build/lib/dxf2gcode/dxfimport/__init__.py -> >
Bug#1024169: marked as done (csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated)
Your message dated Thu, 24 Nov 2022 16:34:47 + with message-id and subject line Bug#1024169: fixed in csound 1:6.18.1+dfsg-1 has caused the Debian Bug report #1024169, regarding csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated 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.) -- 1024169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: csound, csound-plugins Control: found -1 csound/1:6.18.0+dfsg-2 Control: found -1 csound-plugins/1.0.2~dfsg1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of csound the autopkgtest of csound-plugins fails in testing when that autopkgtest is run with the binary packages of csound from unstable. It passes when run with only packages from testing. In tabular form: passfail csound from testing1:6.18.0+dfsg-2 csound-plugins from testing1.0.2~dfsg1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of csound to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=csound https://ci.debian.net/data/autopkgtest/testing/arm64/c/csound-plugins/28320936/log.gz *** stack smashing detected ***: terminated csound command: Aborted csound command: Segmentation fault autopkgtest [17:15:52]: test command1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: csound Source-Version: 1:6.18.1+dfsg-1 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of csound, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated csound 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: Thu, 24 Nov 2022 17:00:05 +0100 Source: csound Architecture: source Version: 1:6.18.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1024169 Changes: csound (1:6.18.1+dfsg-1) unstable; urgency=medium . * New upstream version 6.18.1+dfsg + Fixes BigEndian issues + Fixes ABI compatibility (Closes: #1024169) + Drop patches applied (or obsoleted) upstream * Drop "Recommends:stk" (this belongs to csound-plugins) * Drop obsolete Cmake configvars * Modernize 'licensecheck' target + Regenerate d/copyright_hints Checksums-Sha1: 234ca9cc7ec4c3837b953def5899de34cc6d649b 3384 csound_6.18.1+dfsg-1.dsc e6e6134ca73d3e11bdc716871b4f295742837ece 25231484 csound_6.18.1+dfsg.orig.tar.xz ff8051bd150d4903971265f922ffc8b920ac3d80 52564 csound_6.18.1+dfsg-1.debian.tar.xz Checksums-Sha256: 931cc8ec04ad66b5b68b34cbe6fe790dd8851dbad92772bf0e6dfbedd6adb319 3384 csound_6.18.1+dfsg-1.dsc cca9e8cd5655b5b5b99f967cff7f9fa222307becf00f70f1508126377ef94d4e 25231484 csound_6.18.1+dfsg.orig.tar.xz a29c8c79b9f8a85130564861df8587d8a78238fb09049d67b647ffbdba7d247b 52564 csound_6.18.1+dfsg-1.debian.tar.xz Files: b7eaabaf53c48fd4e9797655b6d8c275 3384 sound optional csound_6.18.1+dfsg-1.dsc bebeed8b5aec52b0a96de82879034679 25231484 sound optional csound_6.18.1+dfsg.orig.tar.xz 4771a2be723c20b33a06be8401409e8c 52564 sound optional csound_6.18.1+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmN/l9EACgkQtlAZxH96 NvglzA/7Bmyi4RYuHsitTGGw7s3TRHsDoCu/ALqLdCWvfl7HwOdEkc2TYPx7qU7e 2DjfB4zITKgrCNWcsQcCz0Yr13yVqDhXcRbRrkvWEJyIbB1CnTOVxg/G/QOHp1yb
Bug#1024773: libpresage-doc: missing Breaks+Replaces: libpresage-dev (<< 0.9.1-2.4)
Package: libpresage-doc Version: 0.9.1-2.4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' 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 libpresage-dev:amd64. Preparing to unpack .../libpresage-dev_0.9.1-2.3_amd64.deb ... Unpacking libpresage-dev:amd64 (0.9.1-2.3) ... dpkg: error processing archive /var/cache/apt/archives/libpresage-dev_0.9.1-2.3_amd64.deb (--unpack): trying to overwrite '/usr/share/doc/libpresage-dev/getting_started.txt.gz', which is also in package libpresage-doc 0.9.1-2.4 Errors were encountered while processing: /var/cache/apt/archives/libpresage-dev_0.9.1-2.3_amd64.deb cheers, Andreas libpresage-doc=0.9.1-2.4_libpresage-dev=0.9.1-2.3.log.gz Description: application/gzip
Bug#1023738: orthanc-dicomweb FTBFS with node-axios 1.1
Control: tags -1 - patch Hi Nilesh, Nilesh Patra, on 2022-11-24: > On Fri, 18 Nov 2022 22:48:42 +0100 =?utf-8?Q?=C3=89tienne?= Mollier > wrote: > > orthanc-dicomweb is currently affected by a failure to build > > from source (Bug#1023738). I took the liberty to have a look, > > and it seems that since axios 1.0 the dist/axios.map file is not > > provided anymore. > > I just did an upload for node-axios that provides the sourcemap file > again with a minor change (/usr/share/nodejs/axios/dist/axios.min.js.map > instead > of min.map) > > However axios code has changed a bit since last version and so has the > sourcemap file. > This needs to be tested with orthanc-dicomweb (if it is even compatible) Thanks for your work on the node-axios front, with some luck, bringing back a map file will be helpful. > > This is causing the following cmake error: > > > > CMake Error at debian/ThirdPartyDownloads/JavaScriptLibraries.cmake:29 > > (file): > > file COPY_FILE failed to copy > > > > /usr/share/nodejs/axios/dist/axios.map > > > > to > > > > /<>/Build/javascript-libs/js/axios.min.map > > > > Scanning through the source code, I noticed that axios.min.map > > file was not used anywhere (only mention is in a cmake file > > which is patched out in Debian context). When removing the > > reference this way, I got the package to build again: > > Looking at the description of node-axios: > > Description: Promise based HTTP client for the browser and node.js > Features: > - Make XMLHttpRequests from the browser > - Make http requests from node.js > - Supports the Promise API > - Intercept request and response > - Transform request and response data > - Cancel requests > - Automatic transforms for JSON data > - Client side support for protecting against XSRF > . > Node.js is an event-based server-side JavaScript engine. > > Looks like axios might be used for an http client which the dicomweb > _probably_ > aims at doing. So removing that file via your patch _might_ not be correct. Thanks for checking in depth, I remove the "patch" tag for now. > But Sebastian is the best judge. Please let us know. Definitely Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. On air: Manticora - 1963. Creator of Failure signature.asc Description: PGP signature
Processed: Re: orthanc-dicomweb FTBFS with node-axios 1.1
Processing control commands: > tags -1 - patch Bug #1023738 [src:orthanc-dicomweb] orthanc-dicomweb FTBFS with node-axios 1.1 Removed tag(s) patch. -- 1023738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024180: marked as done (pngcheck: autopkgtest needs update for new version of zlib: warning on stderr)
Your message dated Thu, 24 Nov 2022 15:35:20 + with message-id and subject line Bug#1024180: fixed in pngcheck 3.0.2-3 has caused the Debian Bug report #1024180, regarding pngcheck: autopkgtest needs update for new version of zlib: warning on stderr 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.) -- 1024180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pngcheck Version: 3.0.2-2 Severity: serious X-Debbugs-CC: z...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:zlib Dear maintainer(s), With a recent upload of zlib the autopkgtest of pngcheck fails in testing when that autopkgtest is run with the binary packages of zlib from unstable. It passes when run with only packages from testing. In tabular form: passfail zlib from testing1:1.2.13.dfsg-1 pngcheck from testing3.0.2-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Your test *only* fails because of a warning. The default behavior of autopkgtest is to fail when there is output on stderr, unless the allow-stderr restriction is added. In this case, I'd try to avoid the warning altogether, because this is something that can happen easily in Debian. Currently this regression is blocking the migration of zlib to testing [1]. Of course, zlib shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in zlib was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from zlib should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. 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=zlib https://ci.debian.net/data/autopkgtest/testing/amd64/p/pngcheck/28323432/log.gz zlib warning: different version (expected 1.2.11, using 1.2.13) OK: debian/tests/openlogo-nd-100.png (101x124, 8-bit palette, non-interlaced, 88.5%). autopkgtest [11:15:19]: test command2 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: pngcheck Source-Version: 3.0.2-3 Done: David da Silva Polverari We believe that the bug you reported is fixed in the latest version of pngcheck, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David da Silva Polverari (supplier of updated pngcheck 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: Thu, 24 Nov 2022 15:14:37 + Source: pngcheck Architecture: source Version: 3.0.2-3 Distribution: unstable Urgency: medium Maintainer: David da Silva Polverari Changed-By: David da Silva Polverari Closes: 1024180 Changes: pngcheck (3.0.2-3) unstable; urgency=medium . * debian/control: bumped Standards-Version to 4.6.1. * debian/copyright: updated packaging copyright years. * debian/tests/control: changed test to avoid failing only because of warning. Thanks to Paul Gevers . (Closes: #1024180) Checksums-Sha1: 0e0b6180910281c4352932da3a841fa20edc4fcd 1893 pngcheck_3.0.2-3.dsc 82f87e9e1d892def459da1cfae9fc61fe6b2a09e 14956 pngcheck_3.0.2-3.debian.tar.xz f7d4ac6024c73e641e7fc1496d7922a314ce98ff 5543 pngcheck_3.0.2-3_source.buildinfo Checksums-Sha256: db5a47440797284baadae36494f5a6fed192db1fbbf0546397085a5b62a27ed1 1893 pngcheck_3.0.2-3.dsc d3b4368e6943729ba5cb73a81759620688d9d8f4dc4afb6b4041bb5693d3c18d 14956 pngcheck_3.0.2-3.debian.tar.xz 880f081fd0e15d7798e0aea0309fedb211069a48b62d06cf48a1ce8798482dec 5543
Bug#1021846: [programmer11...@programist.ru: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem]
Adding Daniel Axtens... On Tue, Nov 15, 2022 at 06:31:45PM +, Steve McIntyre wrote: > Hi all! > > программист некто (in CC) reported this bug a few weeks back in > Debian. Since I applied the bundle of filesystem bounds-checking fixes > a few months back, he can't run grub-install. He's done the work to > determine that the patch that breaks things for him is > > 2d014248d540c7e087934a94b6e7a2aa7fc2c704 fs/f2fs: Do not read past the end of > nat journal entries > > The full thread of our discussion is at https://bugs.debian.org/1021846 > > I don't have any knowledge of f2fs to go any further here. Help please! :-) > > - Forwarded message from программист некто > - > > From: программист некто > To: sub...@bugs.debian.org > Date: Sat, 15 Oct 2022 23:54:36 +0300 > Subject: Bug#1021846: grub-install is broken since 2.06-3: error: unknown > filesystem > Message-Id: <3168731665867...@wf4nrjvtssjecb53.iva.yp-c.yandex.net> > > Package: grub-pc > Version: 2.06-3~deb11u1 > Severity: critical > > Hello. Since version 2.06-3, grub-install is broken: it fails with "error: > unknown filesystem". > I test command /usr/sbin/grub-install -v /dev/sda > in some versions. Results in mail attachments. > Versions older than 2.06-3 works without error (2.06-2 and lower). > Tested versions: 2.04-20, 2.06-1, 2.06-2, 2.06-3~deb10u1, 2.06-3~deb11u1, > 2.06-4. > > Disk partitions: > > # fdisk --list-details > Disk /dev/sda: 29,82 GiB, 32017047552 bytes, 62533296 sectors > Disk model: TS32GSSD370S > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disklabel type: dos > Disk identifier: 0xc7177f7e > > Device Boot Start End Sectors Id Type Start-C/H/S End-C/H/S Attrs > /dev/sda1 2048 22763519 22761472 83 Linux 4/4/1 1023/254/2 > /dev/sda2 * 25866240 62531583 36665344 7 HPFS/ 1023/254/2 1023/254/2 80 > > $ disktype /dev/sda1 > --- /dev/sda1 > Block device, size 10.85 GiB (11653873664 bytes) > F2FS file system (version 1.14) > > $ disktype /dev/sda2 > --- /dev/sda2 > Block device, size 17.48 GiB (18772656128 bytes) > NTFS file system > Volume size 17.48 GiB (18772652032 bytes, 36665336 sectors) > > - End forwarded message - > -- > Steve McIntyre, Cambridge, UK.st...@einval.com > Mature Sporty Personal > More Innovation More Adult > A Man in Dandism > Powered Midship Specialty
Bug#1024768: libphonenumber: FTBFS after switch to debhelper
Source: libphonenumber Version: 8.12.57+ds-2 Severity: serious Creating this for tracking and coordination purposes. After this [1] upload, libphonenumber is FTBFS. Please refer to the buildd logs [2]. [1] https://tracker.debian.org/news/1389357/accepted-libphonenumber-81257ds-2-source-into-unstable/ [2] https://buildd.debian.org/status/package.php?p=libphonenumber
Processed: tagging 1024651
Processing commands for cont...@bugs.debian.org: > tags 1024651 + fixed-upstream upstream Bug #1024651 [src:ruby-gpgme] ruby-gpgme: FTBFS against libgpgme-dev >= 1.18.0-2 Added tag(s) fixed-upstream and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1024651 is forwarded to https://github.com/ueno/ruby-gpgme/pull/166
Processing commands for cont...@bugs.debian.org: > forwarded 1024651 https://github.com/ueno/ruby-gpgme/pull/166 Bug #1024651 [src:ruby-gpgme] ruby-gpgme: FTBFS against libgpgme-dev >= 1.18.0-2 Set Bug forwarded-to-address to 'https://github.com/ueno/ruby-gpgme/pull/166'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#981484: webext-exteditor: not compatible with current thunderbird
On Sun, 31 Jan 2021 20:56:35 +0100 Ivo De Decker wrote: > package: webext-exteditor > version: 2.0.4-1 > severity: serious > > Hi, > > Thunderbird 1:78.7.0-1 has 'Breaks: webext-exteditor (<= 2.0.4-1)', which > means webext-exteditor doesn't work with it. Upstream isn't active anymore. I suggest switching to: https://github.com/Frederick888/external-editor-revived -- Paride
Bug#1024493: Proposed-RM: bs1770gain -- RoQA; inappropriate content
On Mon, 21 Nov 2022 13:53:43 +0100 Leon van Kammen wrote: > my few cents: the problem with censorship is, once you start, the > rabbithole is infinite. > Whatever shitty homepage or comment it is, eventually it's just a homepage > or comment. > I think debian-devs should not be going down the rabbithole of scanning all > code for 'bad' words, bad images, suspicious logos etc, as the creativity > of humans in infinite too.. > The reactive path also plays in the hands of those activists (expect > "debian turns out to be ran by X" youtube vids). Cat't agree more. The offensive content has been patched out already there is no merit to keep digging down on it more and more. This package is actually useful as Petter already stated clearly, so removing it just on the basis of a homepage does not seem good. A sensible compromise maybe to remove the homepage field from d/control if that serves the purpose. Debian was always about technology and shall always be about that (let's not forget that at the end of the day it is an operating system). Imposing debian values over each line of code over each package makes it no longer fully focussed about technology. We can't and shouldn't expect each upstream's ideologies to be same as ours, that's literally impossible. I personally value inclusiveness, being excellent to people a lot but those things should be applied to developers/contributors engaging in debian. Not for each and every package's contributors that lands in debian. I doubt if a user is going to migrate all the way through the source code, and visit upstream homepage and get offended because _we_ vendor the software. In the end it's our and the user's loss because a useful software would be dropped out of the bag for reasons not related to technical aspect. In the end, you will do what you want (i.e. maybe removing the package and I know that) but I just wanted to speak up. (And I see this as a different case as compared to the fortunes-off thing as this does not spit that kind of virtiol onto user's terminal after the patch) -- Best, Nilesh signature.asc Description: PGP signature
Processed: closing 1024175, closing 1024174
Processing commands for cont...@bugs.debian.org: > close 1024175 4.1.0-1 Bug #1024175 [src:ruby-omniauth-gitlab] ruby-omniauth-gitlab: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1 Marked as fixed in versions ruby-omniauth-gitlab/4.1.0-1. Bug #1024175 [src:ruby-omniauth-gitlab] ruby-omniauth-gitlab: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1 Marked Bug as done > close 1024174 1.0.1-1 Bug #1024174 [src:ruby-omniauth-dingtalk-oauth2] ruby-omniauth-dingtalk-oauth2: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1) Marked as fixed in versions ruby-omniauth-dingtalk-oauth2/1.0.1-1. Bug #1024174 [src:ruby-omniauth-dingtalk-oauth2] ruby-omniauth-dingtalk-oauth2: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1024174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024174 1024175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024174: closing 1024175, closing 1024174
close 1024175 4.1.0-1 close 1024174 1.0.1-1 thanks These bugs have been closed in the last uploads of ruby-omniauth-gitlab and ruby-omniauth-dingtalk-oauth2, respectively, but I missed the bugs already reported.
Bug#1023738: orthanc-dicomweb FTBFS with node-axios 1.1
On Fri, 18 Nov 2022 22:48:42 +0100 =?utf-8?Q?=C3=89tienne?= Mollier wrote: > Control: tags -1 + patch > > Hi Sébastien, > > orthanc-dicomweb is currently affected by a failure to build > from source (Bug#1023738). I took the liberty to have a look, > and it seems that since axios 1.0 the dist/axios.map file is not > provided anymore. I just did an upload for node-axios that provides the sourcemap file again with a minor change (/usr/share/nodejs/axios/dist/axios.min.js.map instead of min.map) However axios code has changed a bit since last version and so has the sourcemap file. This needs to be tested with orthanc-dicomweb (if it is even compatible) > This is causing the following cmake error: > > CMake Error at debian/ThirdPartyDownloads/JavaScriptLibraries.cmake:29 > (file): > file COPY_FILE failed to copy > > /usr/share/nodejs/axios/dist/axios.map > > to > > /<>/Build/javascript-libs/js/axios.min.map > > Scanning through the source code, I noticed that axios.min.map > file was not used anywhere (only mention is in a cmake file > which is patched out in Debian context). When removing the > reference this way, I got the package to build again: Looking at the description of node-axios: Description: Promise based HTTP client for the browser and node.js Features: - Make XMLHttpRequests from the browser - Make http requests from node.js - Supports the Promise API - Intercept request and response - Transform request and response data - Cancel requests - Automatic transforms for JSON data - Client side support for protecting against XSRF . Node.js is an event-based server-side JavaScript engine. Looks like axios might be used for an http client which the dicomweb _probably_ aims at doing. So removing that file via your patch _might_ not be correct. But Sebastian is the best judge. Please let us know. -- Best, Nilesh signature.asc Description: PGP signature
Bug#1024674: Bug#1024726: nmu: evolution-data-server_3.46.1-1+b1
* Jeremy Bicha [2022-11-23 16:33]: Please schedule this rebuild to fix evolution-data-server compatibility with libphonenumber which was rebuilt for the ongoing protobuf transition. This rebuild wasn't on the auto tracker which suggests that there is a bigger dependency issue somewhere. I don't know if other packages are also affected. See https://bugs.debian.org/1024674 The problem is/was that libphonenumber8 exposes the protobuf ABI. I've just uploaded a -2 to declare this dependency through a libphonenumber8-protobuf32 virtual package, similar how it is done in ignition-msgs. I've just did a test build and evolution-data-server picks up the new dependency now. so I think the request should be: dw evolution-data-server_3.46.1-1+b1 . ANY . unstable . -m "libphonenumber8 (>= 8.12.57+ds-2)" Cheers Jochen signature.asc Description: PGP signature
Bug#1024522: marked as done (python-leidenalg FTBFS with igraph 0.10.2)
Your message dated Thu, 24 Nov 2022 11:23:24 + with message-id and subject line Bug#1024522: fixed in python-leidenalg 0.9.0-1 has caused the Debian Bug report #1024522, regarding python-leidenalg FTBFS with igraph 0.10.2 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.) -- 1024522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-leidenalg Version: 0.8.10-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=python-leidenalg=amd64=0.8.10-1%2Bb3=1668985384=0 ... src/leidenalg/GraphHelper.cpp: In member function ‘void Graph::cache_neighbour_edges(size_t, igraph_neimode_t)’: src/leidenalg/GraphHelper.cpp:465:33: error: cannot convert ‘igraph_vector_t*’ to ‘igraph_vector_int_t*’ 465 | igraph_incident(this->_graph, incident_edges, v, mode); | ^~ | | | igraph_vector_t* In file included from /usr/include/igraph/igraph.h:57, from include/GraphHelper.h:4, from src/leidenalg/GraphHelper.cpp:1: /usr/include/igraph/igraph_interface.h:74:90: note: initializing argument 2 of ‘igraph_error_t igraph_incident(const igraph_t*, igraph_vector_int_t*, igraph_integer_t, igraph_neimode_t)’ 74 | IGRAPH_EXPORT igraph_error_t igraph_incident(const igraph_t *graph, igraph_vector_int_t *eids, igraph_integer_t vid, | ~^~~~ ... --- End Message --- --- Begin Message --- Source: python-leidenalg Source-Version: 0.9.0-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of python-leidenalg, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-leidenalg 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, 24 Nov 2022 11:18:04 +0100 Source: python-leidenalg Architecture: source Version: 0.9.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1024522 Changes: python-leidenalg (0.9.0-1) unstable; urgency=medium . [ Étienne Mollier ] * New upstream version . [ Andreas Tille ] * Versioned Build-Depends: python-igraph (>= 0.10) Closes: #1024522 Checksums-Sha1: 1360cba15889ca4760d2be40a537765deb833513 2385 python-leidenalg_0.9.0-1.dsc e88ed385600129266e6d444db2be71b41480f78b 483479 python-leidenalg_0.9.0.orig.tar.gz ee3ffb3e164c8952ca5c0a53890fe221d0028bf2 3964 python-leidenalg_0.9.0-1.debian.tar.xz 1737eea43ad919e43fb0474371f2250e0a0c61a3 8536 python-leidenalg_0.9.0-1_amd64.buildinfo Checksums-Sha256: d958756a57b2eae91f5cd768037bcd34a9f24a99b0fd94fb37df046ab1db5f76 2385 python-leidenalg_0.9.0-1.dsc b31e446ca2fadbcb280b6ddb1008ac543a2d6b601e936040a3ec62c2a8ba8108 483479 python-leidenalg_0.9.0.orig.tar.gz e197cf54941445575022ea511b89eddc8327a57dcf3d1d67b5dec8ae4e8f1b08 3964 python-leidenalg_0.9.0-1.debian.tar.xz a2a334396c4188b2202e02b25fef478e042aeededa7a9ba9c2b887a11db12caf 8536 python-leidenalg_0.9.0-1_amd64.buildinfo Files: ff2e1a37988520e7de02dfde11fba026 2385 science optional python-leidenalg_0.9.0-1.dsc bd4231fb56c82936d80fee465a8e8d39 483479 science optional python-leidenalg_0.9.0.orig.tar.gz 88e7f2063a4c647efee2662ad9c17d28 3964 science optional python-leidenalg_0.9.0-1.debian.tar.xz 1293ea0e1d759b43b84d9f2b0162e26c 8536 science optional python-leidenalg_0.9.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmN/SnQRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHaQxAAjiUGxPnDg8luGZOjOVQURN6xPjhFEK5F kAhkE+VdUautcAZ69/7G5jf3+TV73ij++CVTpeHk7cNsTNBtltVg4EW8Drc2AqX/ J5JqeBUtfUFV/f0R/rJNftiKnnEekuE37iAklvwZJjPzPBaZQXdqQq17Gdt7OcI0 lRUARkATbUf5yNrEXU9mJ/Z6yiRGiYdGw+JF5HxKRWMNYTlw7EFGiBdOeyxLPUZX YkKKxhPaKxs9iNO6b15ZOBSd+bzB+Vm8TzG04tZBjeUMkllyqEqDPv5yh5X+jkwa
Bug#1024458: marked as done (seqan-needle: binary-all FTBFS)
Your message dated Thu, 24 Nov 2022 11:23:38 + with message-id and subject line Bug#1024458: fixed in seqan-needle 1.0.1.0.0.git.3011926+ds-4 has caused the Debian Bug report #1024458, regarding seqan-needle: binary-all FTBFS 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.) -- 1024458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: seqan-needle Version: 1.0.1.0.0.git.3011926+ds-2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=seqan-needle=all=1.0.1.0.0.git.3011926%2Bds-2=1668618292=0 ... debian/rules override_dh_auto_build-indep make[1]: Entering directory '/<>' cd obj-* && /usr/bin/make doc /bin/sh: 1: cd: can't cd to obj-* make[1]: *** [debian/rules:26: override_dh_auto_build-indep] Error 2 --- End Message --- --- Begin Message --- Source: seqan-needle Source-Version: 1.0.1.0.0.git.3011926+ds-4 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of seqan-needle, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated seqan-needle 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, 24 Nov 2022 11:38:47 +0100 Source: seqan-needle Architecture: source Version: 1.0.1.0.0.git.3011926+ds-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1024458 Changes: seqan-needle (1.0.1.0.0.git.3011926+ds-4) unstable; urgency=medium . * Team upload. * Create doc without previous binary build Closes: #1024458 Checksums-Sha1: 16fda09863bee9848bddfb3fee149e290e81420b 2281 seqan-needle_1.0.1.0.0.git.3011926+ds-4.dsc e484a3867f677c7a91ac21744337637bcdcfd25b 6052 seqan-needle_1.0.1.0.0.git.3011926+ds-4.debian.tar.xz d10b115fd8035b6c1f68ebe6dcfd7dc0e6bd2d79 8208 seqan-needle_1.0.1.0.0.git.3011926+ds-4_amd64.buildinfo Checksums-Sha256: 3560b1624aff0499dd8f47954890d2840508b78152f706bfcad796863d5a523a 2281 seqan-needle_1.0.1.0.0.git.3011926+ds-4.dsc 0f39029448ddca892db717c02cfd153eccd4b315ee6a2fb42db73d7eaed454ef 6052 seqan-needle_1.0.1.0.0.git.3011926+ds-4.debian.tar.xz c402ff0b4d539286eadd002c7ca69d4842c208a5243e575eef9480c3893af3f6 8208 seqan-needle_1.0.1.0.0.git.3011926+ds-4_amd64.buildinfo Files: e827bbaf0fd55b0480ee77ec65db47eb 2281 science optional seqan-needle_1.0.1.0.0.git.3011926+ds-4.dsc 16c8be5f321c4109a6b2980b8139efa0 6052 science optional seqan-needle_1.0.1.0.0.git.3011926+ds-4.debian.tar.xz 980d698655306687d63927b72d8cda89 8208 science optional seqan-needle_1.0.1.0.0.git.3011926+ds-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmN/StERHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHxfg//Zva/FxVpJevX1eJvovcrJcriPtBCMZk1 AjmcleKj2EEq9EtU92lsfNvEeUft4JE2fw4cPeONL2ZQ95hH9az9n0Q6h72K3Z0H yIYsqU8JRYMm3QxFiqDMClSAJSqt6v+AEuWeEoQzXOfOwo38IOLuQS9B+jL5M7w7 5rkZplXprJTqyWD3Slmm41D8No3gLDwqIgjwhopzL2c9ead32gYFP2Hs+VsIJ3Pn QEhm5pnYNFt/avRVJ2rrf9SO3HQew9LRatfQgUltgdvRRG3ZBa+to3rvL/IQKUrY fvWO712Bi9UQ23hX/N+xR8Sq/8m+mn4p/5AunbQOpDrosPq21yhl7MXRwMWpoJWr lFvD9qv7dNzx7+nQ4qlRFwtzjiYHKr3MYGTky0lyPxRRB+Mj1ovjigK65UsNcW7U oQ16Y9Kd5mj6h9udHyd2j1YdS+qgQQZ6d9vxEqa6N/ygah0IqsIgL03tGhvbXGRD PBnPBgUPp44qvP8x7H/h/k6f3swCXcrUo2tcxLGFceQP3a4oLNZOZNSzOMtHgg4r bfZiEOc2M8hJOxtEI5xwCvq9S2/jOUvdU+sfT3FIFZnIgtuZ9pO45QnDnOMhEzCW 9KBVBCGgShk6IXhdJhls26B11t2fzrp3zAB675H0p51strTMbvGv175/crG0zg4+ Qu1t4MxaYWY= =atv/ -END PGP SIGNATURE End Message ---
Bug#1024701: marked as done (libphonenumber8 update breaks evolution)
Your message dated Thu, 24 Nov 2022 11:20:22 + with message-id and subject line Bug#1024701: fixed in libphonenumber 8.12.57+ds-2 has caused the Debian Bug report #1024701, regarding libphonenumber8 update breaks evolution 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.) -- 1024701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libphonenumber8 Version: 8.12.57+ds-1+b2 Severity: serious After updating libphonenumber8 from version 8.12.57+ds-1+b1 to version 8.12.57+ds-1+b2 in Debian Sid, Gnome Evolution fails to launch. Downgrading to the previous version (still in Bookworm) fixes the issue. Regards signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: libphonenumber Source-Version: 8.12.57+ds-2 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of libphonenumber, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated libphonenumber 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, 24 Nov 2022 12:03:20 +0100 Source: libphonenumber Architecture: source Version: 8.12.57+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Jochen Sprickerhof Closes: 1024701 Changes: libphonenumber (8.12.57+ds-2) unstable; urgency=medium . * Team upload. * Convert to debhelper * Expose protobuf ABI (Closes: #1024701) * Bump policy version (no changes) * Move package description to source package * Drop old Conflicts/Replaces Checksums-Sha1: 544dd8220be2f51d3aa132a5c41d87694d432ab0 2899 libphonenumber_8.12.57+ds-2.dsc 29be7beb720f1aaac9dc6869014f5a11e4fea13d 11944 libphonenumber_8.12.57+ds-2.debian.tar.xz 723410b32318da06636fa2ec85de89ec795092d5 19351 libphonenumber_8.12.57+ds-2_source.buildinfo Checksums-Sha256: 39a6db5078070a4b42f1e915c76fb926836cff63ec0ec2913e60c9b667aa75d9 2899 libphonenumber_8.12.57+ds-2.dsc c9ee290c9a9950b28fb832f602e550dbf041db5855001ead159ab7fc93e85168 11944 libphonenumber_8.12.57+ds-2.debian.tar.xz 5320a4bc2244a8100f1d156198738e6dc2ef12d3b7d0e3dc6cf94788386d8f9c 19351 libphonenumber_8.12.57+ds-2_source.buildinfo Files: 397e3913ccf75f4d8fff85c9b64e18d0 2899 libs optional libphonenumber_8.12.57+ds-2.dsc d26f40bf89a0079fb4878cdafe9d1c8c 11944 libs optional libphonenumber_8.12.57+ds-2.debian.tar.xz 50725b4e815885ded890102fb01b9675 19351 libs optional libphonenumber_8.12.57+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmN/T7AACgkQW//cwljm lDM0tw/7B6XKWKjDVFcFYot3DkqqqYHIr8122z2eL/onFvQX87ql5nuKCZ3xhM8q 1f4JdNRJRmgSRl9ArJSP6UgKklVe9heteegbg3oMqT0MebEHl6w9T2QAl+Ol5wFp +N8KPs0bFBX2S+0y0xdF+st8PiNRC3R7UlyMie5X7oRK/G6TyeYURPyS8pM86TqW PabvpONGCqyYPSAaV7LdXWCoiOJPIyvgwaTjeiowvBhMhL6oKLTmGaFn1mcov/Gn F1ZQmkd/JSRduFVRF27j4CUjRi3gxZMK/NUhfTQ8/Dxo/sK1p/LGmmM7aF6VaFUc Bj+T4s4CUi8TO28/tL6Ujuv4OV2qyjve2HJbIgMK9HQmUUwrBUkBy9PIw7p7pQn/ 4Ztb3snWg5oeNpflX5lKpZX8BZ0cl4xTAyFq2rSHYBA4l2XSjcYZ8jzzqq4qFr6S LT37dFoAeglrZLXTpJFip/yIsaI9g1XZBmfvlUzOV723bw0d5jn2R86t0vpHhaJI OyrgDjtuMo24v1JnQu9B1uh5qw0pAsPJjPaZsxXAN4BXp2iouFumZ/zwN5I/xnyq n/JhsekKWHYnHuVdw/90yfxv5dpEYruuX0yEVfTzh8WpnDy/Y9leiECUA2LHp6a+ qQdzczGy/JU75VxiC6XTdKlOYhQqqjHcr+X8upYqLZdC/3uExlY= =19mP -END PGP SIGNATURE End Message ---
Bug#1008434: marked as done (golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/hashicorp/go-plugin github.com/hashicorp/go-p
Your message dated Thu, 24 Nov 2022 11:58:43 +0100 with message-id and subject line Re: Bug#1008434: golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/hashicorp/go-plugin github.com/hashicorp/go-plugin/internal/plugin returned exit code 1 has caused the Debian Bug report #1008434, regarding golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/hashicorp/go-plugin github.com/hashicorp/go-plugin/internal/plugin returned exit code 1 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.) -- 1008434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-hashicorp-go-plugin Version: 1.0.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > DH_GOLANG_EXCLUDES="examples test/grpc" \ > dh_auto_test > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 > github.com/hashicorp/go-plugin github.com/hashicorp/go-plugin/internal/plugin > === RUN TestClient_testInterfaceReattach > 2022-03-26T19:39:12.362Z [DEBUG] plugin: starting plugin: > path=/tmp/go-build1311877249/b001/go-plugin.test > args=[/tmp/go-build1311877249/b001/go-plugin.test, > -test.run=TestHelperProcess, --, test-interface-daemon] > 2022-03-26T19:39:12.362Z [DEBUG] plugin: plugin started: > path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239565 > 2022-03-26T19:39:12.362Z [DEBUG] plugin: waiting for RPC address: > path=/tmp/go-build1311877249/b001/go-plugin.test > 2022-03-26T19:39:12.367Z [DEBUG] plugin.go-plugin.test: plugin address: > address=/tmp/plugin1699243854 network=unix timestamp=2022-03-26T19:39:12.367Z > 2022-03-26T19:39:12.367Z [DEBUG] plugin: using plugin: version=1 > 2022-03-26T19:39:13.369Z [DEBUG] plugin.go-plugin.test: 2022/03/26 19:39:13 > [ERR] plugin: plugin server: accept unix /tmp/plugin1699243854: use of closed > network connection > 2022-03-26T19:39:13.370Z [DEBUG] plugin: plugin process exited: > path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239565 > 2022-03-26T19:39:14.367Z [DEBUG] plugin: reattached plugin process exited > 2022-03-26T19:39:14.367Z [DEBUG] plugin: plugin exited > --- PASS: TestClient_testInterfaceReattach (2.01s) > === RUN TestClient > 2022-03-26T19:39:14.367Z [DEBUG] plugin: starting plugin: > path=/tmp/go-build1311877249/b001/go-plugin.test > args=[/tmp/go-build1311877249/b001/go-plugin.test, > -test.run=TestHelperProcess, --, mock] > 2022-03-26T19:39:14.368Z [DEBUG] plugin: plugin started: > path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239573 > 2022-03-26T19:39:14.368Z [DEBUG] plugin: waiting for RPC address: > path=/tmp/go-build1311877249/b001/go-plugin.test > 2022-03-26T19:39:14.373Z [DEBUG] plugin: using plugin: version=1 > 2022-03-26T19:39:14.373Z [ERROR] plugin: client: error="dial tcp :1234: > connect: connection refused" > 2022-03-26T19:39:14.373Z [WARN] plugin: plugin failed to exit gracefully > 2022-03-26T19:39:14.373Z [DEBUG] plugin: plugin process exited: > path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239573 error="signal: > killed" > --- PASS: TestClient (0.01s) > === RUN TestClient_killStart > 2022-03-26T19:39:14.374Z [DEBUG] plugin: starting plugin: > path=/tmp/go-build1311877249/b001/go-plugin.test > args=[/tmp/go-build1311877249/b001/go-plugin.test, > -test.run=TestHelperProcess, --, bad-version, /tmp/plugin2389898487/booted] > 2022-03-26T19:39:14.374Z [DEBUG] plugin: plugin started: > path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239579 > 2022-03-26T19:39:14.374Z [DEBUG] plugin: waiting for RPC address: > path=/tmp/go-build1311877249/b001/go-plugin.test > 2022-03-26T19:39:14.379Z [WARN] plugin: plugin failed to exit gracefully > 2022-03-26T19:39:14.379Z [DEBUG] plugin: plugin process exited: > path=/tmp/go-build1311877249/b001/go-plugin.test pid=1239579 error="signal: > killed" > --- PASS: TestClient_killStart (0.01s) > === RUN TestClient_testCleanup > 2022-03-26T19:39:14.380Z [DEBUG] plugin: starting plugin: > path=/tmp/go-build1311877249/b001/go-plugin.test > args=[/tmp/go-build1311877249/b001/go-plugin.test, > -test.run=TestHelperProcess, --, cleanup, /tmp/plugin3397144587/output] > 2022-03-26T19:39:14.380Z [DEBUG] plugin: plugin started: >
Bug#1024626: blender FTBFS on 32bit
Source: blender Followup-For: Bug #1024626 I am not sure why I am always to forget something when sumbit reportbug:( The issue for upstream: https://developer.blender.org/T102742 Sorry for the noisy. -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#1024626: blender FTBFS on 32bit
Source: blender Followup-For: Bug #1024626 Hi, Just FYI, I have reported the bug to upstream and will NMU if find a workround. -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#1024344: precious - new version of rust-serial-test.
Quoting Peter Green (2022-11-17 22:13:44) > Package: precious > Version: 0.3.0-1 > Severity: serious > > I've just uploaded version 0.9 of rust-serial-test, the dependencies in > precious > need updating to match. A debdiff is attatched. > > If I get no response i'll probablly NMU this in a week or so. Thanks! I expect to update precious in a few days - preferably to newer upstream release, if bugs #1024747, #1024749 and #1024750 can be easily fixed, otherwise without that version change. I.e. no need for an NMU here - thanks for the offer. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1020018: marked as done (libxmlada: FTBFS: unsatisfiable build-dependency: unicode-data (< 15~) but 15.0.0-1 is to be installed)
Your message dated Thu, 24 Nov 2022 09:34:13 + with message-id and subject line Bug#1020018: fixed in libxmlada 23.0.0-1 has caused the Debian Bug report #1020018, regarding libxmlada: FTBFS: unsatisfiable build-dependency: unicode-data (< 15~) but 15.0.0-1 is to be installed 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.) -- 1020018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxmlada Version: 22.0.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220917 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, > gnat, gnat-11, unicode-data (>= 14~), unicode-data (<< 15~), > dh-sequence-sphinxdoc, python3-sphinx (>= 1.6.3-2), latexmk, tex-gyre, > texlive-fonts-recommended, texlive-plain-generic, texlive-latex-extra > Filtered Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, > gnat, gnat-11, unicode-data (>= 14~), unicode-data (<< 15~), > dh-sequence-sphinxdoc, python3-sphinx (>= 1.6.3-2), latexmk, tex-gyre, > texlive-fonts-recommended, texlive-plain-generic, texlive-latex-extra > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [492 B] > Get:5 copy:/<>/apt_archive ./ Packages [564 B] > Fetched 2013 B in 0s (118 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: unicode-data (< 15~) but 15.0.0-1 > is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2022/09/17/libxmlada_22.0.0-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=lu...@debian.org=1=1=1=1#results 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: libxmlada Source-Version: 23.0.0-1 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of libxmlada, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated libxmlada 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: Thu, 24 Nov 2022 08:52:59 + Source: libxmlada Architecture:
Bug#1024755: r-bioc-bluster: Autopkgtest fails since r-bioc-scater is not yet updated to latest version matching BioC 3.16
Source: r-bioc-bluster Version: 1.8.0+dfsg-1 Severity: critical Justification: breaks unrelated software X-Debbugs-Cc: 1023...@bugs.debian.org Since autopkgtest of r-bioc-bluster depends from r-bioc-scater which needs a new dependency r-cran-ggrastr (ITP #1024582) it is blocking the BioC 3.16 transition[1] due to debci failures for an undetermined time. To not create any blocker for other packages r-bioc-bluster should be removed from testing which is the purpose of this bug. [1] https://release.debian.org/transitions/html/r-api-bioc-3.16.html -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1024754: r-bioc-mofa: Should not block BioC 3.16 transition
Source: r-bioc-mofa Version: 1.6.1+dfsg-7 Severity: critical Tags: ftbfs Justification: breaks unrelated software X-Debbugs-Cc: 1023...@bugs.debian.org Since r-bioc-mofa depends r-bioc-multiassayexperiment with RC bug #1024748 and thus it is blocking the BioC 3.16 transition[1] for an undetermined time. To not create any blocker for other packages r-bioc-mofa should be removed from testing which is the purpose of this bug. Kind regards Andreas. [1] https://release.debian.org/transitions/html/r-api-bioc-3.16.html -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1024751: r-bioc-scater: Should not block BioC 3.16 transition
Source: r-bioc-scater Version: 1.24.0+ds-1 Severity: critical Tags: ftbfs Justification: breaks unrelated software X-Debbugs-Cc: 1023...@bugs.debian.org Since r-bioc-scater needs a new dependency r-cran-ggrastr (ITP #1024582) it is blocking the BioC 3.16 transition[1] for an undetermined time. To not create any blocker for other packages r-bioc-scater should be removed from testing which is the purpose of this bug. Kind regards Andreas. [1] https://release.debian.org/transitions/html/r-api-bioc-3.16.html -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1024748: r-bioc-multiassayexperiment: Should not block BioC 3.16 transition
Source: r-bioc-multiassayexperiment Version: 1.22.0+dfsg-1 Severity: critical Tags: ftbfs Justification: breaks unrelated software X-Debbugs-Cc: 1023...@bugs.debian.org Since r-bioc-multiassayexperiment needs a new dependency r-bioc-biocbaseutils (ITP #1024567) it is blocking the BioC 3.16 transition[1] for an undetermined time. To not create any blocker for other packages r-bioc-multiassayexperiment should be removed from testing which is the purpose of this bug. Kind regards Andreas. [1] https://release.debian.org/transitions/html/r-api-bioc-3.16.html -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1023149: marked as done (pandoc FTBFS on i386)
Your message dated Thu, 24 Nov 2022 08:37:07 +
with message-id
and subject line Bug#1023149: fixed in pandoc 2.17.1.1-1.1
has caused the Debian Bug report #1023149,
regarding pandoc FTBFS on i386
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.)
--
1023149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandoc
Version: 2.17.1.1-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Debian Haskell Group
https://buildd.debian.org/status/logs.php?pkg=pandoc=2.17.1.1-1%2Bb3
...
[193 of 214] Compiling Text.Pandoc.Readers.EPUB
src/Text/Pandoc/Readers/EPUB.hs:79:40: error:
• Local identifier ‘FilePath’ used as a type
• In the type signature:
parseSpineElem :: PandocMonad m =>
FilePath -> (FilePath, MimeType) -> m Pandoc
In an equation for ‘archiveToEPUB’:
archiveToEPUB os archive
= do (root, content) <- getManifest archive
(coverId, meta) <- parseMeta content
(cover, items) <- parseManifest content coverId
where
os'
= os
{readerExtensions = enableExtension
Ext_raw_html (readerExtensions os)}
parseSpineElem ::
PandocMonad m => FilePath -> (FilePath, MimeType) -> m Pandoc
parseSpineElem (normalise -> r) (normalise -> path, mime)
= do doc <- mimeToReader mime r path
mimeToReader ::
PandocMonad m => MimeType -> FilePath -> FilePath -> m Pandoc
|
79 | parseSpineElem :: PandocMonad m => FilePath -> (FilePath, MimeType) ->
m Pandoc
|
src/Text/Pandoc/Readers/EPUB.hs:84:50: error:
• Local identifier ‘FilePath’ used as a type
• In the type signature:
mimeToReader :: PandocMonad m =>
MimeType -> FilePath -> FilePath -> m Pandoc
In an equation for ‘archiveToEPUB’:
archiveToEPUB os archive
= do (root, content) <- getManifest archive
(coverId, meta) <- parseMeta content
(cover, items) <- parseManifest content coverId
where
os'
= os
{readerExtensions = enableExtension
Ext_raw_html (readerExtensions os)}
parseSpineElem ::
PandocMonad m => FilePath -> (FilePath, MimeType) -> m Pandoc
parseSpineElem (normalise -> r) (normalise -> path, mime)
= do doc <- mimeToReader mime r path
mimeToReader ::
PandocMonad m => MimeType -> FilePath -> FilePath -> m Pandoc
|
84 | mimeToReader :: PandocMonad m => MimeType -> FilePath -> FilePath -> m
Pandoc
|
-e: error: debian/hlibrary.setup build --builddir=dist-ghc returned exit code 1
...
The patch below workarounds the issue, which indicates that it might
be a bug in the compiler and not a problem in pandoc?
Short-term it might even be good enough to unblock migration of several
packages to testing.
--- debian/rules.old2022-10-30 17:52:59.643347191 +
+++ debian/rules2022-10-30 17:54:14.347251214 +
@@ -192,6 +192,10 @@
DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-optc--param
-optcggc-min-expand=10 -O0"
endif
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU), i386))
+DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-O0"
+endif
+
DEB_SETUP_GHC_CONFIGURE_ARGS += $(if $(filter
nocheck,$(DEB_BUILD_OPTIONS)),,-ftests)
DEB_INSTALL_DOCS_ALL += README.md
--- End Message ---
--- Begin Message ---
Source: pandoc
Source-Version: 2.17.1.1-1.1
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
pandoc, 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 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated pandoc package)
(This message was generated automatically at their
Bug#1023149: pandoc: diff for NMU version 2.17.1.1-1.1
Quoting Scott Talbert (2022-11-24 03:00:41) > On Sat, 19 Nov 2022, Adrian Bunk wrote: > > > Control: tags 1023149 + patch > > Control: tags 1023149 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for pandoc (versioned as 2.17.1.1-1.1) and uploaded > > it to DELAYED/15. Please feel free to tell me if I should cancel it. > > Can this NMU be accepted ASAP? > > Assuming I'm reading excuses correctly, I believe this is preventing a > massive number of haskell packages from migrating to testing. I welcome this bugfix and agree: @Adrian, please release it without further delay. Unfortunately I cannot take over and release now myself, as my GPG key has expired so I cannot do package uploads until the next batch update of the keyring data (which was estimated to happen two days ago, so will probably happen soonish). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1023149: pandoc: diff for NMU version 2.17.1.1-1.1
On Wed, Nov 23, 2022 at 09:00:41PM -0500, Scott Talbert wrote: > On Sat, 19 Nov 2022, Adrian Bunk wrote: > > > Control: tags 1023149 + patch > > Control: tags 1023149 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for pandoc (versioned as 2.17.1.1-1.1) and uploaded > > it to DELAYED/15. Please feel free to tell me if I should cancel it. > > Can this NMU be accepted ASAP? > > Assuming I'm reading excuses correctly, I believe this is preventing a > massive number of haskell packages from migrating to testing. I assume this is approval from a member of the maintainer team, and have rescheduled pandoc for immediate upload. > Thanks, > Scott cu Adrian
Bug#1024417: [pkg-gnupg-maint] Bug#1024417: kgpg FTBFS: Did not find GPGME
On Wed, 23 Nov 2022 15:42:31 -0500 Daniel Kahn Gillmor wrote: > On Wed 2022-11-23 16:27:43 +0100, Andreas Metzler wrote: > > Unless kgpg maintainers/upstream has a strong opinion against using > > pkg-config the obvious choice would be to drop cmake/FindGpgme.cmake > > and simply use FindPkgConfig. - Attached patch seems to work for me, > > i.e. build including dh_auto_test works. > > Thanks for this, Andreas. > > I've proposed this change upstream as well at > https://invent.kde.org/utilities/kgpg/-/merge_requests/18 I think that this is a great debian stop gap measure, but due to upstream also supporting windows, the Good Fix[tm] should go into FindGpgme.cmake instead, but could be derived from pkgconfig there. /Sune
