Bug#1056088: marked as pending in bagel
Control: tag -1 pending Hello, Bug #1056088 in bagel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debichem-team/bagel/-/commit/2dc6e7c37ac418531088df93d512dfe6fc9aa501 Fix FTBFS against boost 1.83. (Closes: #1056088) (this message was generated automatically) -- Greetings https://bugs.debian.org/1056088
Bug#1050019: Reporting an issue
forwarded 1050019 https://github.com/google/cctz/issues/274 thanks Hi, I have reported the issue here [1] [1] https://github.com/google/cctz/issues/274 Best regards Anton
Bug#1040731: wslay: autopkgtest failure due to new CMake deprecation warning
Hi Timo, thanks a lot for this upload! I have just prepared a "normal" update, including your changes and some others. If you want, you can cancel NMU or it will be automatically rejected by the system. Best regards Anton Am Di., 1. Aug. 2023 um 11:21 Uhr schrieb Timo Röhling : > Hi Anton, > > On Fri, 21 Jul 2023 21:13:56 +0200 Anton Gladky wrote: > > Thanks a lot for the MR and update. > > I will prepare an update and upload it in one week. If it's ok for you. > > Otherwise, please NMU. > I have just uploaded an NMU to DELAYED/5 and pushed the corresponding > commits to the branch nmu-bug-1040731. Chris' solution is probably > cleaner (I just hot-patched the CMakeLists.txt in autopkgtest), so > if you have time this week, feel free to upload your own release, > and I will cancel my upload. > > > Cheers > Timo > > -- > ⢀⣴⠾⠻⢶⣦⠀ ╭╮ > ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ > ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ > ⠈⠳⣄ ╰╯ >
Bug#1040731: wslay: autopkgtest failure due to new CMake deprecation warning
Hi Chris, Thanks a lot for the MR and update. I will prepare an update and upload it in one week. If it's ok for you. Otherwise, please NMU. Best regards Chris Hofstaedtler schrieb am Fr., 21. Juli 2023, 20:58: > Hi Anton, > > * roehl...@debian.org : > > Source: wslay > [..] > > > > your package wslay will soon experience autopkgtest failures because > > the new CMake release 3.27 will issue a deprecation warning on stderr > > if cmake_minimum_required() asks for compatibility with CMake 3.4 or > > older. > > I've opened an MR with a trivial fix for this on salsa.d.o: > https://salsa.debian.org/debian/wslay/-/merge_requests/5 > > Depending on your preferences I could also prepare an NMU with this > and upload to delayed? > > Thanks, > Chris > > > PS: I assume wslay probably wants to go away. I hope dnsdist can > switch from h2o to nghttp2 during trixie. >
Bug#1028104: libboost-dev: Boost with C++20 uses unavailable std functions
Hi, boost-defaults_1.81.0 is in experimental. But boost1.81 is also available in the Debian Bookworm [1]. [1] https://packages.debian.org/source/testing/boost1.81 Regards Anton Am Di., 18. Apr. 2023 um 09:27 Uhr schrieb Olaf van der Spek : > ... > 1.81 is in experimental, not in bookworm, right? > It's unfortunate it's not in bookworm.
Bug#1028104: libboost-dev: Boost with C++20 uses unavailable std functions
Hi, I think there is a risk that something needs to be fixed, as there are no RC bugs against libboost-dev. It seems like boost1.81 is not affected by this problem. So, if somebody needs a newer library, they can take libboost1.81-dev, which is available for bookworm. I would not fix anything in boost shortly before release. Paul, if you have some use cases where a small fix is really necessary, we can discuss it. Otherwise, I would leave it as it is. Best regards, Anton Anton Am Di., 21. März 2023 um 22:03 Uhr schrieb Paul Gevers : > > Hi, > > On Sun, 08 Jan 2023 00:26:39 +0100 Andreas Beckmann wrote: > > This happens with g++-12 but not with g++-11. > > It is fixed in the boost version in experimental. > > Any chance for a *targeted* fix in bookworm? > > Paul
Bug#1028104: libboost-dev: Boost with C++20 uses unavailable std functions
Hi Paul, Yes i will do it. Paul Gevers schrieb am Do., 6. Apr. 2023, 14:36: > Hi, > > On Tue, 21 Mar 2023 21:58:11 +0100 Paul Gevers wrote: > > On Sun, 08 Jan 2023 00:26:39 +0100 Andreas Beckmann > wrote: > > > This happens with g++-12 but not with g++-11. > > > It is fixed in the boost version in experimental. > > > > Any chance for a *targeted* fix in bookworm? > > Ping. (No is also an answer). > > Paul >
Bug#1032554: h2o: FTBFS in testing: [h2o_mruby] in request:/:mruby raised: /tmp/UpqKGDqVnc:19: yeah! (RuntimeError)
Hi Chris, thanks for your work! Please go ahead and upload without a delay. Please push your changes to git and tag it. Thanks and regards Anton Am Di., 21. März 2023 um 19:57 Uhr schrieb Chris Hofstaedtler < z...@debian.org>: > Hi, > > I will upload a change disabling the failing test to DELAYED/7. > Please let me know if I should cancel it. Debdiff attached. > > The failing mruby test might or might not point to a real problem, > it seems like its not 100% reproducible (in my builds at least). > I want src:h2o / libh2o to stay in bookworm so it can be used by > dnsdist; after bookworm I expect dnsdist upstream to switch away > from h2o, which itself seems upstream-dead. > > Thanks, > Chris > >
Bug#1027965: Fix for the RC bug in vtk
Adding ciruclar dependencies is what we do want to avoid. It looks like gdcm has already explicit dep on vtk9-qt-dev, thus closing the ticket. Regards Anton
Bug#1027965: Fix for the RC bug in vtk
Hi Steven. thanks for the notice! vtk9 upload is in my todo list for the next few days. Regards Anton Am So., 5. Feb. 2023 um 17:30 Uhr schrieb Steven Robbins : > > Hello, > > Was looking yesterday for an RC bug to fix and noticed #1027965 against VTK -- > a build failure in gdcm caused by missing dependency. The fix proposed by > Mathieu seems reasonable to me. > > Anton: I'm writing to ask your opinion about the commits in salsa since the > last upload (June 2022); specifically, do you feel they are suitable for > inclusion now? > > Should I: > > 1. apply the patch to the lastest in salsa? > 2. apply the patch to the last upload sources ignoring salsa? > 3. leave it alone and let you deal with it? > 4. something else? > > Appreciate your insight. > -Steve
Bug#1028867: Rassign and close
reassign 1028867 php8.2 8.2.1-1 fixed 1028867 8.2.2-1 thanks The problem not in php-sabre-vobject but in php itself [1]. Upstream fix [2] and is fixed in Debian already [3]. Thus - reassign and close. [1] https://github.com/Shardj/zf1-future/issues/304 [2] https://github.com/php/php-src/commit/d12ba111e03fa4e6d76a66a029f5dbe6265b1ea9 [3] https://sources.debian.org/src/php8.2/8.2.2-1/ext/date/lib/parse_date.c/#L790 Best regards
Bug#1028950: marked as pending in php-horde-view
Control: tag -1 pending Hello, Bug #1028950 in php-horde-view reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/horde-team/php-horde-view/-/commit/ab9a91e6ff4955f526e0e573450f5bd0fba79d98 debian/patches: fix warnings du to php8.2. (Closes: #1028950) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028950
Bug#1003747: marked as pending in php-horde-ldap
Control: tag -1 pending Hello, Bug #1003747 in php-horde-ldap reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/horde-team/php-horde-ldap/-/commit/31c2507f14596e6d37d75613b663216637dcbc1d d/patches: partly fix autopkgtests. Some todos are left. (Closes: #1003747) (this message was generated automatically) -- Greetings https://bugs.debian.org/1003747
Bug#1028951: Close
Thank you for your bug report! It looks like the issue is no more here. CI and new upload did not show any regression. Thus I am closing the ticket. Thanks Anton
Bug#1028110: marked as pending in php-horde-lz4
Control: tag -1 pending Hello, Bug #1028110 in php-horde-lz4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/horde-team/php-horde-lz4/-/commit/4e5ab4940daf5cfd1dd92529ad02f634b4e3234a d/t/control: add php-dom. (Closes: #1028110) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028110
Bug#1003784: marked as pending in php-horde-wicked
Control: tag -1 pending Hello, Bug #1003784 in php-horde-wicked reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/horde-team/php-horde-wicked/-/commit/a4c38ee869b6e86c8b6ffe459732f1542cb3dfc0 d/patches: fix php8.0 failure. (Closes: #1003784) (this message was generated automatically) -- Greetings https://bugs.debian.org/1003784
Bug#1003473: marked as pending in php-horde-lz4
Control: tag -1 pending Hello, Bug #1003473 in php-horde-lz4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/horde-team/php-horde-lz4/-/commit/17094c5f099ecf0d5ccbb89da690a759b185e559 d/patches: fix compilation against php8.1. (Closes: #1003473) (this message was generated automatically) -- Greetings https://bugs.debian.org/1003473
Bug#1003648: Reassign
reassign 1003648 php-horde-prefs/2.9.0-8 thanks The warning is in Prefs.php, which is in package php-horde-prefs. Some other packages can be affected Anton
Bug#1003649: marked as pending in php-horde-argv
Control: tag -1 pending Hello, Bug #1003649 in php-horde-argv reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/horde-team/php-horde-argv/-/commit/1a6dde08c44d5a075389a66e46a90c86ee6c40e1 Fix autopkgtests. (Closes: #1003649) (this message was generated automatically) -- Greetings https://bugs.debian.org/1003649
Bug#1025658: libboost-python1.74-dev: Python 3.11 changes break loading of boost-python using extensions
Hi Niels, thanks for the note. Yes, I will take care of it. Regards Anton
Bug#1023273: Old version is not working
The newer 14 version of ocrmypdf is needed to suppor the ghostscript 10. I have checked and can confirm, that 14.0.1 is working well. Regards Anton
Bug#1013158: facet-analyser: vtk[6,7] removal
Hi Picca, I have just successfully cloned the git-repo. I have only got a warning "[attr]our-c-style whitespace=tab-in-indent format.clang-format=9 n" but I thinking it is not critical. Please try to checkout it again. Maybe it was salsa issue? Regards Anton Am Di., 1. Nov. 2022 um 10:18 Uhr schrieb PICCA Frederic-Emmanuel < frederic-emmanuel.pi...@synchrotron-soleil.fr>: > Hello Anton, I try to checkout paraview in order to add the -dev > dependencies > > but I have this message > > $ git clone https://salsa.debian.org/science-team/paraview > Clonage dans 'paraview'... > remote: Enumerating objects: 175624, done. > remote: Counting objects: 100% (78929/78929), done. > remote: Compressing objects: 100% (38687/38687), done. > remote: Total 175624 (delta 47039), reused 65625 (delta 39190), > pack-reused 96695 > Réception d'objets: 100% (175624/175624), 246.21 Mio | 12.11 Mio/s, fait. > Résolution des deltas: 100% (109096/109096), fait. > [attr]our-c-style whitespace=tab-in-indent,-blank-at-eol > format.clang-format non permis : > ThirdParty/QtTesting/vtkqttesting/.gitattributes : 8 > [attr]our-c-style whitespace=tab-in-indent,-blank-at-eol > format.clang-format=9 non permis : > ThirdParty/catalyst/vtkcatalyst/catalyst/.gitattributes : 4 > [attr]our-c-style whitespace=tab-in-indent,-blank-at-eol > format.clang-format=8 non permis : VTK/.gitattributes : 10 > [attr]our-c-style whitespace=tab-in-indent format.clang-format=9 non > permis : VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/.gitattributes : 2 > Mise à jour des fichiers: 100% (30828/30828), fait. > [attr]our-c-style whitespace=tab-in-indent,-blank-at-eol > format.clang-format=8 non permis : VTK/.gitattributes : 10 > [attr]our-c-style whitespace=tab-in-indent format.clang-format=9 non > permis : VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/.gitattributes : 2 > Downloading VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md (643 B) > Error downloading object: VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md > (b30a14a): Smudge error: Error downloading > VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md > (b30a14a308f64c6fc2969e2b959d79dacdc5affda1d1c0e24f8e176304147146): > [b30a14a308f64c6fc2969e2b959d79dacdc5affda1d1c0e24f8e176304147146] Object > does not exist on the server or you don't have permissions to access it: > [404] Object does not exist on the server or you don't have permissions to > access it > > Errors logged to > /home/experiences/instrumentation/picca/debian/science-team/paraview/.git/lfs/logs/20221101T101535.441130442.log > Use `git lfs logs last` to view the log. > error: le filtre externe 'git-lfs filter-process' a échoué > fatal: VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/data/README.md : le filtre smudge > 'lfs' a échoué > warning: Le clone a réussi, mais l'extraction a échoué. > Vous pouvez inspecter ce qui a été extrait avec 'git status' > et réessayer avec 'git restore --source=HEAD :/' >
Bug#1016248: marked as pending in content-hub
Control: tag -1 pending Hello, Bug #1016248 in content-hub reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ubports-team/content-hub/-/commit/b4fad56d8242ba8e350d9752eed192331f6844ac Update symbols due to gcc-12. (CloseS: #1016248) (this message was generated automatically) -- Greetings https://bugs.debian.org/1016248
Bug#1015103: marked as pending in lomiri-ui-extras
Control: tag -1 pending Hello, Bug #1015103 in lomiri-ui-extras reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ubports-team/lomiri-ui-extras/-/commit/282f186494d31d546336365dbb9805731e268eb8 Disable tst_printers test. (Closes: #1015103) (this message was generated automatically) -- Greetings https://bugs.debian.org/1015103
Bug#1012993: marked as pending in lomiri-thumbnailer
Control: tag -1 pending Hello, Bug #1012993 in lomiri-thumbnailer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ubports-team/lomiri-thumbnailer/-/commit/451c874dfb0cfa2f2f51f7e188b10d255ab3b259 Add missing header. (Closes: #1012993) (this message was generated automatically) -- Greetings https://bugs.debian.org/1012993
Bug#1013616: Thanks
Thanks, Jonathan, for the patch! Anton
Bug#1019061: Done
gnuplot-data is built. Thus closing. Cheers Anton
Bug#1019061: Root cause is #1019061
Hi, thanks for bug report. The main problem is #1017698. Gnuplot cannot be built due to missing build-dep on emacs-nox. Regards Anton
Bug#1009739: fixed in yade 2022.01a-8
Hi Bernhard, I think one can ask the corresponding arm-mailing list. Anyway, if you have a solution for that I could test it first on the real hardware. Thanks Anton Am Mi., 1. Juni 2022 um 00:12 Uhr schrieb Bernhard Übelacker : > > Hello Anton, > I am happy if my work helps. > And I am sorry, but I fear my test shows now a failure > for armhf and armel too. > > From 'echo | gcc -dM -E - | grep -i arm' I see gcc has > on both platforms predefined the macro __ARMEL__. > But I am not sure what is the best way to just detect those > platforms, or maybe just check for sizeof(void*)==4 or similar. > > Kind regards, > Bernhard >
Bug#1009739: fixed in yade 2022.01a-8
Hi Bernhard, Thank you very much for this information and for fixing it! I have just uploaded boost1.74_1.74.0-15 with this fix and will revert the workaround in yade! Best regards Anton
Bug#1001528: Eigen3 affected?
affects 1001528 -eigen3 thanks Well, I do not see how eigen3 can help to fix this bug. The problem exists definitely in the upstream of the purify, So the upstream of this package should be active to resolve the issue against the mathematical library used by them. Regards Anton
Bug#986590: Severity
severity 986590 important thanks I have temporarily disabled the unreliable test. Thus I am reducing the bug's severity. Yes, I know, it is wrong to disable a failing test. But I am continuing to work on it, trying to build it with threadsanitizer and check, what is going on there. Any help is appreciated/ Thanks Anton
Bug#986590: Patch
As I mentioned before the patch does not solve the problem. Increasing the "Session time" sometimes causes very long test-times. So we have here definitely the deadlock. If somebody has more experience in glib, it would be really helpful to investigate an issue. Best regards Anton
Bug#986590: Still reproducible
The bug is still reproducible. This time on armhf [1] and in CI [2]. [1] https://buildd.debian.org/status/fetch.php?pkg=dbus-test-runner=armhf=19.04.0-1%7Eexp1=1651644822=0 [2] https://salsa.debian.org/debian/dbus-test-runner/-/jobs/2731578 Regards Anton
Bug#986590: Patch #76, still fails
Unfortunately the patch in #76 still fails. Needs some more investigation: == FAIL: test-libdbustest-mock-test ** (gtester:7666): WARNING **: 21:18:27.890: Deprecated: Since GLib 2.62, gtester and gtester-report are deprecated. Port to TAP. TEST: ./test-libdbustest-mock... (pid=7667) /libdbustest/mock/basic: (/builds/debian/dbus-test-runner/debian/output/source_dir/tests/.libs/test-libdbustest-mock:7667): libdbustest-WARNING **: 21:18:27.910: Unable to start watchdog DBus daemon: unix:abstract=/tmp/dbus-QtSQwrxNGw,guid=5439845aad7f1bb8e63d4297626c5623 DBusMock: Started with PID: 7687 DBusMock: Shutting down DBus daemon: Shutdown ** ERROR:test-libdbustest-mock.c:45:wait_for_connection_close: assertion failed: (wait_count != SESSION_MAX_WAIT) FAIL GTester: last random seed: R02S0c733c834df4b87e3a0bb6bff1c44e77 (pid=7728) /libdbustest/mock/properties: (/builds/debian/dbus-test-runner/debian/output/source_dir/tests/.libs/test-libdbustest-mock:7728): libdbustest-CRITICAL **: 21:21:48.365: dbus_test_dbus_mock_object_add_property: assertion 'g_variant_is_of_type(value, type)' failed (/builds/debian/dbus-test-runner/debian/output/source_dir/tests/.libs/test-libdbustest-mock:7728): libdbustest-WARNING **: 21:21:48.367: Unable to start watchdog DBus daemon: unix:abstract=/tmp/dbus-FB8W7MsRSE,guid=4425b2c97b1ed05ae561ebd2626c56ec DBusMock: Started with PID: 7747 (/builds/debian/dbus-test-runner/debian/output/source_dir/tests/.libs/test-libdbustest-mock:7728): libdbustest-CRITICAL **: 21:21:48.462: Property 'prop1' is not of same value in dbus_test_dbus_mock_object_update_property() DBusMock: Shutting down DBus daemon: Shutdown OK /libdbustest/mock/methods: (/builds/debian/dbus-test-runner/debian/output/source_dir/tests/.libs/test-libdbustest-mock:7728): libdbustest-WARNING **: 21:21:48.472: Unable to start watchdog DBus daemon: unix:abstract=/tmp/dbus-7xF4SrW7pk,guid=9514c44ce88f66e83ee408cc626c56ec DBusMock-1: Started with PID: 7755 DBusMock-1: Shutting down DBus daemon: Shutdown OK /libdbustest/mock/signals: (/builds/debian/dbus-test-runner/debian/output/source_dir/tests/.libs/test-libdbustest-mock:7728): libdbustest-WARNING **: 21:21:48.771: Unable to start watchdog DBus daemon: unix:abstract=/tmp/dbus-4AGx7A42El,guid=46c8120e5b0e1fa2f9082734626c56ec DBusMock-2: Started with PID: 7763 DBusMock-2: 1651267308.866 emit /test foo.test.interface.testsig DBusMock-2: 1651267308.968 emit /test foo.test.interface.testsig_abc "a" "b" "c" DBusMock-2: Shutting down DBus daemon: Shutdown OK /libdbustest/mock/running: (/builds/debian/dbus-test-runner/debian/output/source_dir/tests/.libs/test-libdbustest-mock:7728): libdbustest-WARNING **: 21:21:49.076: Unable to start watchdog DBus daemon: unix:abstract=/tmp/dbus-MJiLNJREgr,guid=71b2068fe312fd7ba7dd5e06626c56ed DBusMock-3: Started with PID: 7771 DBusMock-3: Shutting down DBus daemon: Shutdown OK /libdbustest/mock/running-system: (/builds/debian/dbus-test-runner/debian/output/source_dir/tests/.libs/test-libdbustest-mock:7728): libdbustest-WARNING **: 21:21:49.371: Unable to start watchdog DBus daemon: unix:abstract=/tmp/dbus-KMNGhYfACr,guid=a04514c03ab8369dfed6f3f9626c56ed DBusMock-4: Started with PID: 7779 DBusMock-4: Shutting down DBus daemon: Shutdown OK /libdbustest/mock/interfaces: (/builds/debian/dbus-test-runner/debian/output/source_dir/tests/.libs/test-libdbustest-mock:7728): libdbustest-WARNING **: 21:21:49.668: Unable to start watchdog DBus daemon: unix:abstract=/tmp/dbus-yeC3JJFI37,guid=e1b247ec47e3e0d499b9f17c626c56ed DBusMock-5: Started with PID: 7787 DBusMock-5: Shutting down DBus daemon: Shutdown OK FAIL: ./test-libdbustest-mock FAIL test-libdbustest-mock-test (exit status: 1) == Anton
Bug#1008426: h2o: diff for NMU version 2.2.5+dfsg2-6.2
I do not have this tag as I did not repack a tarball. Anton Am Mi., 13. Apr. 2022 um 22:47 Uhr schrieb Chris Hofstaedtler : > > Hi Anton, > > * Anton Gladky [220412 19:18]: > > thanks a lot for NMU! Feel free to upload immediately, > > but please commit your changes into the git. Thanks! > > okay, can/will do. Could you push the tag tags/upstream/2.2.5+dfsg2 into > git? > > I have cancelled the NMU in the meantime. > > Thanks, > Chris >
Bug#1008426: h2o: diff for NMU version 2.2.5+dfsg2-6.2
Hi Chris,
thanks a lot for NMU! Feel free to upload immediately,
but please commit your changes into the git. Thanks!
Regards
Anton
Am Di., 12. Apr. 2022 um 17:33 Uhr schrieb Chris Hofstaedtler :
>
> Control: tags 1008426 + patch
> Control: tags 1008426 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for h2o (versioned as 2.2.5+dfsg2-6.2) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
>
> Regards.
>
> diff -Nru h2o-2.2.5+dfsg2/debian/changelog h2o-2.2.5+dfsg2/debian/changelog
> --- h2o-2.2.5+dfsg2/debian/changelog2021-10-17 11:38:52.0 +
> +++ h2o-2.2.5+dfsg2/debian/changelog2022-04-12 14:57:18.0 +
> @@ -1,3 +1,11 @@
> +h2o (2.2.5+dfsg2-6.2) unstable; urgency=medium
> +
> + * Non-maintainer upload.
> + * Remove now unsupported hash parameters to FileUtils methods,
> +fixing FTBFS. (Closes: #1008426)
> +
> + -- Chris Hofstaedtler Tue, 12 Apr 2022 14:57:18 +
> +
> h2o (2.2.5+dfsg2-6.1) unstable; urgency=medium
>
>* Non-maintainer upload.
> diff -Nru h2o-2.2.5+dfsg2/debian/patches/mruby_fileutils_no_verbose
> h2o-2.2.5+dfsg2/debian/patches/mruby_fileutils_no_verbose
> --- h2o-2.2.5+dfsg2/debian/patches/mruby_fileutils_no_verbose 1970-01-01
> 00:00:00.0 +
> +++ h2o-2.2.5+dfsg2/debian/patches/mruby_fileutils_no_verbose 2022-04-12
> 14:56:46.0 +
> @@ -0,0 +1,70 @@
> +Remove hash with verbose from calls to FileUtils. This apparently
> +has stopped being supported in ruby.
> +
> +Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008426
> +
> +Index: h2o-2.2.5+dfsg2/deps/mruby/Rakefile
> +===
> +--- h2o-2.2.5+dfsg2.orig/deps/mruby/Rakefile
> h2o-2.2.5+dfsg2/deps/mruby/Rakefile
> +@@ -37,15 +37,15 @@ load "#{MRUBY_ROOT}/tasks/gitlab.rake"
> + task :default => :all
> +
> + bin_path = ENV['INSTALL_DIR'] || "#{MRUBY_ROOT}/bin"
> +-FileUtils.mkdir_p bin_path, { :verbose => $verbose }
> ++FileUtils.mkdir_p bin_path
> +
> + depfiles = MRuby.targets['host'].bins.map do |bin|
> + install_path = MRuby.targets['host'].exefile("#{bin_path}/#{bin}")
> + source_path =
> MRuby.targets['host'].exefile("#{MRuby.targets['host'].build_dir}/bin/#{bin}")
> +
> + file install_path => source_path do |t|
> +-FileUtils.rm_f t.name, { :verbose => $verbose }
> +-FileUtils.cp t.prerequisites.first, t.name, { :verbose => $verbose }
> ++FileUtils.rm_f t.name
> ++FileUtils.cp t.prerequisites.first, t.name
> + end
> +
> + install_path
> +@@ -78,8 +78,8 @@ MRuby.each_target do |target|
> + install_path = MRuby.targets['host'].exefile("#{bin_path}/#{bin}")
> +
> + file install_path => exec do |t|
> +- FileUtils.rm_f t.name, { :verbose => $verbose }
> +- FileUtils.cp t.prerequisites.first, t.name, { :verbose =>
> $verbose }
> ++ FileUtils.rm_f t.name
> ++ FileUtils.cp t.prerequisites.first, t.name
> + end
> + depfiles += [ install_path ]
> + elsif target == MRuby.targets['host-debug']
> +@@ -87,8 +87,8 @@ MRuby.each_target do |target|
> + install_path =
> MRuby.targets['host-debug'].exefile("#{bin_path}/#{bin}")
> +
> + file install_path => exec do |t|
> +-FileUtils.rm_f t.name, { :verbose => $verbose }
> +-FileUtils.cp t.prerequisites.first, t.name, { :verbose =>
> $verbose }
> ++FileUtils.rm_f t.name
> ++FileUtils.cp t.prerequisites.first, t.name
> + end
> + depfiles += [ install_path ]
> + end
> +@@ -127,16 +127,16 @@ end
> + desc "clean all built and in-repo installed artifacts"
> + task :clean do
> + MRuby.each_target do |t|
> +-FileUtils.rm_rf t.build_dir, { :verbose => $verbose }
> ++FileUtils.rm_rf t.build_dir
> + end
> +- FileUtils.rm_f depfiles, { :verbose => $verbose }
> ++ FileUtils.rm_f depfiles
> + puts "Cleaned up target build folder"
> + end
> +
> + desc "clean everything!"
> + task :deep_clean => ["clean"] do
> + MRuby.each_target do |t|
> +-FileUtils.rm_rf t.gem_clone_dir, { :verbose => $verbose }
> ++FileUtils.rm_rf t.gem_clone_dir
> + end
> + puts "Cleaned up mrbgems build folder"
> + end
> diff -Nru h2o-2.2.5+dfsg2/debian/patches/series
> h2o-2.2.5+dfsg2/debian/patches/series
> --- h2o-2.2.5+dfsg2/debian/patches/series 2020-05-03 20:12:52.0
> +
> +++ h2o-2.2.5+dfsg2/debian/patches/series 2022-04-12 14:54:56.0
> +
> @@ -4,3 +4,4 @@
> tests-force-TLSv1.2-on-s_client-invocations.patch
> link-libh2o-with-wslay.patch
> fix_CVE-2019_1.patch
> +mruby_fileutils_no_verbose
>
Bug#1001484: sfepy: (autopkgtest) needs update for python3.10: Sequence' from 'collections' is removed
I will do it ASAP Anton Am Do., 24. März 2022 um 18:54 Uhr schrieb Stefano Rivera : > > Control: tag -1 + pending > > I see a commit fixing this in git, just waiting to be uploaded. > https://salsa.debian.org/science-team/sfepy/-/commit/f6a4f8d2435e8406a629a75ee89891a24631233a > > SR > > -- > Stefano Rivera > http://tumbleweed.org.za/ > +1 415 683 3272
Bug#984232: status
This bug is fixed. I followed the advice from Adrian and now the package builds fine. Regards Anton Am Sa., 18. Dez. 2021 um 01:39 Uhr schrieb Ryan Pavlik : > > The updated package just needs the copyright file updated and reviewed. If > you'd like a fix uploaded before I get a chance to do that (which is somewhat > intimidating, they swapped some bundled dependencies since the last packaged > version), please feel free to nmu. Alternately I'd happily accept an mr to > make the copyright file complete again. > > Ryan > > On Wed, Dec 15, 2021, 5:24 AM Adrian Bunk wrote: >> >> On Mon, Nov 15, 2021 at 02:53:40PM -0600, Ryan Pavlik wrote: >> > Upstream has fixed this, and I have a package with the latest upstream >> > sources in progress, happy to accept help to put it over the edge. >> >> Any progress on this? >> >> If necessary, I could NMU with the minimal fix of adding >> export DEB_CXXFLAGS_MAINT_APPEND += -std=gnu++14 >> to debian/rules. >> >> > Ryan >> >> cu >> Adrian >> > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1000611: libvtk9{,-qt}: soname change without library transition
Hi Adrian, thanks for the bug report. It was really an accidental upload into unstable instead of experimental. Yes, I will rename the package and upload it ASAP. Regards Anton Am Do., 25. Nov. 2021 um 22:03 Uhr schrieb Adrian Bunk : > > Package: libvtk9 > Version: 9.1.0+dfsg2-2 > Severity: serious > Control: affects -1 libvtk9-qt src:vtk9 > > https://ci.debian.net/data/autopkgtest/testing/amd64/f/freecad/16980590/log.gz > > ... > ERROR: TestFemApp (unittest.loader._FailedTest) > -- > ImportError: Failed to import test module: TestFemApp > Traceback (most recent call last): > File "/usr/lib/python3.9/unittest/loader.py", line 154, in loadTestsFromName > module = __import__(module_name) > File "/usr/share/freecad/Mod/Fem/TestFemApp.py", line 33, in > from femtest.app.test_mesh import TestMeshCommon as FemTest07 > File "/usr/share/freecad/Mod/Fem/femtest/app/test_mesh.py", line 33, in > > import Fem > ImportError: libvtkFiltersExtraction-9.0.so.1: cannot open shared object > file: No such file or directory > ... > > > The soname of the vtk9 libraries is not 9, it is 9.0 for VTK 9.0 > and 9.1 for VTK 9.1: > > $ objdump -p /usr/lib/x86_64-linux-gnu/libvtkChartsCore-9.1.so.1 | grep > SONAME > SONAME libvtkChartsCore-9.1.so.1 > $ > > In bullseye libvtk9 and libvtk9-qt should have been named > libvtk9.0 and libvtk9.0-qt, but this alone is harmless. > > Not harmless is that the libraries must transition to the new > soname in 9.1, renaming the packages to libvtk9.1 and libvtk9.1-qt. > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#998411: Bug#996204: transition: numerical library stack: hypre SONAME (Policy 8.1)
I have fixed gmsh. It will appear in NEW soon. Regards Anton
Bug#984068: marked as pending in itksnap
Control: tag -1 pending Hello, Bug #984068 in itksnap reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/itksnap/-/commit/23e6d300304fd9fff8d31984b43ed438cfc7eb17 Add upstream commit fixing the C++ version used Closes: #984068 (this message was generated automatically) -- Greetings https://bugs.debian.org/984068
Bug#996976: vtk6: Remove vtk6 from the Debian 12
Source: vtk6 Severity: serious vtk has now 3 versions in archive: vtk6, vtk7 and vtk9. Intention is to remove older unsupported versions in favour of cyrrent vtk9.
Bug#994405: libgmp10:i386: buffer overflow due to integer overflow in mpz/inp_raw.c on 32-bit machines
Control: severity -1 important Control: notfound -1 2:6.2.1+dfsg-2 Control: found -1 2:6.2.1+dfsg-1 Thanks for the bug report. We will fix it when CVE (if any) will be assigned and upstream patch will be available. Though, the integer overflows are not making the package unusable in most cases. Thus the severity is reduced. Regards Anton
Bug#990895: httraqt: Apparently installs entire program in /usr/share/doc/
Control: gravity -1 minor Control: tags -1 +moreinfo +unreproducible Thanks for the bug report, I am not able to reproduce the issue. Please provide more information about how to reproduce it. It looks like something is broken on your side. Try to install another similar package. Regards Anton
Bug#988326: libboost-python-dev: Linking against boost_python requires the python version number ex: -lboost_python39
Control: tags -1 wontfix Hi, I am closing this bug. See an explanation above. Best regards Anton
Bug#987921: [RFS] Re: Bug#987921: linbox FTBFS on 32bit with gcc 10
Your changes look good. Let's wait for approval by release team not to pollute unstable by unapproved uploads. Regards Anton Am Mo., 10. Mai 2021 um 11:40 Uhr schrieb Torrance, Douglas < dtorra...@piedmont.edu>: > On Sun 09 May 2021 05:16:38 PM EDT, Anton Gladky wrote: > > I will review/upload the package tomorrow, > > Please file a pre-approval request against release.debian.org. Thanks > > Thanks! Pre-approval request: https://bugs.debian.org/988296 > > Doug
Bug#987921: [RFS] Re: Bug#987921: linbox FTBFS on 32bit with gcc 10
Hi Doug, I will review/upload the package tomorrow, Please file a pre-approval request against release.debian.org. Thanks Regards Anton Am So., 9. Mai 2021 um 22:48 Uhr schrieb Torrance, Douglas < dtorra...@piedmont.edu>: > Control: tags -1 pending > > On Sun 02 May 2021 12:46:50 AM EDT, Adrian Bunk wrote: > > Source: linbox > > Version: 1.6.3-2 > > Severity: serious > > Tags: ftbfs > > > > > https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/i386/linbox.html > > I've fixed this RC bug in git: > https://salsa.debian.org/science-team/linbox > > Would anyone be willing to review/sponsor? I'm hoping that linbox won't > get removed before the bullseye release. > > Thanks! > Doug >
Bug#982616: Revert voro++_0.5?
Hi, maybe it makes sense to revert the upload of a newer version? There is a risk of dropping this and all dependent packages from Bullseye. Cheers Anton
Bug#982624: python3-luma.led-matrix: Depends: python3-luma.core but it is not installable
Hi Adrian, thanks for bugreport. core-package ist still in NEW queue. So, no way to fix this bug right now. Regards Anton Am Fr., 12. Feb. 2021 um 16:27 Uhr schrieb Adrian Bunk : > Package: python3-luma.led-matrix > Version: 1.5.0+dfsg1-1 > Severity: serious > > The following packages have unmet dependencies: > python3-luma.led-matrix : Depends: python3-luma.core but it is not > installable >
Bug#977921: boost1.74: context asm files not built on mipsel
It looks like the main problem is here [1]: [1] https://buildd.debian.org/status/fetch.php?pkg=boost1.74=mipsel=1.74.0-5=1608350424=0 === /<>/b2 -j4 -q -d2 --disable-long-double --layout=system --ignore-site-config --user-config=/<>/user-config.jam debug-symbols=on --without-python Performing configuration checks - default address-model: 32-bit - default architecture : mips1 Building the Boost C++ Libraries. - symlinks supported : yes error: No best alternative for libs/context/build/asm_sources === @Giovanni , @Dimitri could you please take a look, what is missing there in parameters? Thank you! Anton Am Di., 22. Dez. 2020 um 23:15 Uhr schrieb Adrian Bunk : > > Source: boost1.74 > Version: 1.74.0-3 > Severity: serious > Tags: ftbfs > Control: affects -1 src:nix libboost-coroutine1.74.0 libboost-fiber1.74.0
Bug#977243: Still not fixed
tags 977243 -pending
thanks
CC-ing on of upstream contributors.
@Casey could you please take a look? This part of the code
fails with the newer boost_1.74? Thanks!
It looks like the last version in git still fails to build.
===
ceph/src/common/async/completion.h: In instantiation of 'void
ceph::async::detail::CompletionImpl::destroy_defer(std::tuple&&) [with Executor1 =
boost::asio::io_context::basic_executor_typ
e, 0>; Handler =
boost::asio::detail::coro_handler,
boost::asio::exec
ution::detail::blocking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boos
t::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > > >, void>;
T = void; Args = {boost::system::error_code}]':
/root/mod1/ceph/src/common/async/completion.h:188:8: required from
here
/root/mod1/ceph/src/common/async/completion.h:194:29: error:
'boost::asio::executor_work_guard,
boost::asio::execution::detail::blo
cking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution
::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > >, void>::executor_type' {aka
'class
boost::asio::execution::any_executor,
boost::asio::execution::detail::blocking::never_t<0>
,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only >,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only > >'} has no member named 'defer'; did you mean 'prefer'?
194 | w.second.get_executor().defer(std::move(f), alloc2);
| ^
| prefer
ceph/src/common/async/completion.h: In instantiation of 'void
ceph::async::detail::CompletionImpl::destroy_dispatch(std::tuple&&) [with Executor1 =
boost::asio::io_context::basic_executor_
type, 0>; Handler =
boost::asio::detail::coro_handler,
boost::asio::e
xecution::detail::blocking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, b
oost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > > >,
void>; T = void; Args = {boost::system::error_code}]':
/root/mod1/ceph/src/common/async/completion.h:196:8: required from here
/root/mod1/ceph/src/common/async/completion.h:202:29: error:
'boost::asio::executor_work_guard,
boost::asio::execution::detail::blo
cking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution
::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > >, void>::executor_type' {aka
'class
boost::asio::execution::any_executor,
boost::asio::execution::detail::blocking::never_t<0>
,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only >,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only > >'} has no member named 'dispatch'
202 | w.second.get_executor().dispatch(std::move(f), alloc2);
| ^~~~
ceph/src/common/async/completion.h: In instantiation of 'void
ceph::async::detail::CompletionImpl::destroy_post(std::tuple&&) [with Executor1 =
boost::asio::io_context::basic_executor_type
, 0>; Handler =
boost::asio::detail::coro_handler,
boost::asio::execu
tion::detail::blocking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost
::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > > >, void>;
T = void; Args = {boost::system::error_code}]':
/root/mod1/ceph/src/common/async/completion.h:204:8: required from here
/root/mod1/ceph/src/common/async/completion.h:210:29: error:
'boost::asio::executor_work_guard,
boost::asio::execution::detail::blo
cking::never_t<0>,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution
::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only > >, void>::executor_type' {aka
'class
boost::asio::execution::any_executor,
boost::asio::execution::detail::blocking::never_t<0>
,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only
>, boost::asio::execution::prefer_only >,
boost::asio::execution::prefer_only
>,
>boost::asio::execution::prefer_only > >'} has no member named 'post'
210 | w.second.get_executor().post(std::move(f), alloc2);
| ^~~~
===
Best regards
Anton
Bug#975169: marked as pending in litecoin
Control: tag -1 pending Hello, Bug #975169 in litecoin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/litecoin/-/commit/aed969f19234bebec7b4c93170f20afd392b5ab5 Add missing header. (Closes: #975169) (this message was generated automatically) -- Greetings https://bugs.debian.org/975169
Bug#977265: diff NMU for dds_2.9.0-8.1
Hi Christoph, Thanks for the feedback! I just generated a new symbols-file. Can you recommend a better fix for that? Regards Anton
Bug#977229: diff NMU for kcollectd_0.11.99.0-1.1
tags 977229 +pending +patch user team+bo...@tracker.debian.org usertag 977229 +boost174 thanks Dear maintainer, I have prepared an NMU (versioned as 0.11.99.0-1.1) and uploaded to DELAYED/5. Please feel free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. MR is here [1]. [1] https://salsa.debian.org/qt-kde-team/extras/kcollectd/-/merge_requests/1 Best regards Anton nmu.debdiff Description: Binary data
Bug#977265: Diff
Forgotten diff. Anton nmu.debdiff Description: Binary data
Bug#977265: diff NMU for dds_2.9.0-8.1
tags 977265 +pending +patch user team+bo...@tracker.debian.org usertag 977265 +boost174 thanks Dear maintainer, I have prepared an NMU (versioned as dds_2.9.0-8.1) and uploaded to DELAYED/5. Please feel free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. MR is here [1]. [1] https://salsa.debian.org/debian/dds/-/merge_requests/1 Best regards Anton
Bug#977226: diff NMU for 0.46.0-1.1
tags 977226 +pending +patch user team+bo...@tracker.debian.org usertag 977226 +boost174 thanks Dear maintainer, I have prepared an NMU (versioned as 0.46.0-1.1) and uploaded to DELAYED/5. Please feel free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. MR is here [1]. [1] https://salsa.debian.org/games-team/openmw/-/merge_requests/1 Best regards Anton nmu.debdiff Description: Binary data
Bug#977185: Can be switched to default
I have checked and your package can easily be switched to the unversioned dev-package. Regards Anton
Bug#976909: h2o: FTBFS on ppc64el: ld: /usr/lib/gcc/powerpc64le-linux-gnu/10/../../../powerpc64le-linux-gnu/Scrt1.o:(.data.rel.ro.local+0x8): undefined reference to `main'
severity 976909 normal tags 976909 +moreinfo thanks Hi Lucas, thanks for filing the bug. But I cannot reproduce this failure and it looks like the last upload of the package h2o into the archive was successfully built of ppc64el [1]. Could you please check your setup and provide more information? [1] https://buildd.debian.org/status/fetch.php?pkg=h2o=ppc64el=2.2.5%2Bdfsg2-6=1608152493=0 Regards Anton Am Mi., 9. Dez. 2020 um 10:09 Uhr schrieb Lucas Nussbaum : > > Source: h2o > Version: 2.2.5+dfsg2-5 > Severity: serious > Justification: FTBFS on ppc64el > Tags: bullseye sid ftbfs > Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
Bug#977449: deff NMU for 1.3.0+dfsg1-3.2
tags 977449 +pending +patch user team+bo...@tracker.debian.org usertag 977449 +boost174 thanks Dear maintainer, I have prepared an NMU (versioned as 1.3.0+dfsg1-3.2) and uploaded to DELAYED/5. Please feel free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. MR is here [1]. [1] https://salsa.debian.org/3dprinting-team/slic3r/-/merge_requests/1 Best regards Anton nmu.debdiff Description: Binary data
Bug#977351: Fixed
reassign 977351 facter 3.14.12-1 fixed 977351 3.14.12-1+b2 thanks Hi Stefan, thanks for filing a bug. We are in the middle of transition from boost_1.71 to boost_1.74, and leatherman was built earlier than facter. Thus such a problem occurred. facter is already also rebuilt and the issue should be resolved. Regards Anton
Bug#977219: diff NMU for anytun_0.3.7-1.3
tags 977219 +pending +patch user team+bo...@tracker.debian.org usertag 977219 +boost174 thanks Dear maintainer, I have prepared an NMU (versioned as 0.3.7-1.3) and uploaded to DELAYED/5. Please feel free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. Best regards Anton nmu.debdiff Description: Binary data
Bug#975863: Merge request
Dear maintainers, MR is here [1]. Please consider to accept it. [1] https://salsa.debian.org/puppet-team/leatherman/-/merge_requests/2 Best Regards Anton
Bug#975863: Raising the bug's severity
severity 975430 serious severity 975588 serious severity 975593 serious severity 975660 serious severity 975665 serious severity 975666 serious severity 975667 serious severity 975672 serious severity 975863 serious thanks boost1.74 is already default in unstable. Thus raising the bug's severity. Cheers Anton
Bug#975863: leatherman: /usr/include/boost/nowide/ are shipped by boost_1.74
Package: leatherman Version: 1.12.1+dfsg-1 Severity: serious Tags: patch Justification: Policy 10.1 User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package ships some files, which are now shipped by libboost1.74-dev [1]: /usr/include/boost/nowide/args.hpp /usr/include/boost/nowide/cenv.hpp /usr/include/boost/nowide/config.hpp /usr/include/boost/nowide/convert.hpp /usr/include/boost/nowide/cstdio.hpp /usr/include/boost/nowide/cstdlib.hpp /usr/include/boost/nowide/filebuf.hpp /usr/include/boost/nowide/fstream.hpp /usr/include/boost/nowide/integration/filesystem.hpp /usr/include/boost/nowide/iostream.hpp /usr/include/boost/nowide/stackstring.hpp /usr/include/boost/nowide/system.hpp /usr/include/boost/nowide/utf8_codecvt.hpp /usr/include/boost/nowide/windows.hpp I have prepared an updated version of your package with the fix but it can only be uploaded after we start a transition to boost_1.74, so libleatherman-dev can have libboost-nowide-dev in build-depends. [1] https://packages.debian.org/sid/alpha/libboost1.74-dev/filelist Best regards Anton - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl++1PIRHGdsYWRrQGRl Ymlhbi5vcmcACgkQ0+Fzg8+n/waB/Q//fM6sQs9VHnXY831uV74rog1xJdXdUT/D RM15+ITwY+IcZ88n7w1g5nWwsVBlL5MEfwHtw3ChXmAgMaYpbcFJZq9yT1xjwdW5 5pteEpZrb2KdFNPnkGFN/DmD0SqdRdF4ZN2AKV44pUJ8+64pGKXOFWfSXuOoRaV1 QDdE4IWVghwafaGHklIalfWElRuooj2VHIiW+oBX8jN61i+HVAQwRvX65G1nuISY UtJ2Nu+NF4V+cB4NiMJAs/aUl6MgXwqyf+yLQVAz0A+RtBo+csfSf3KegY7QoiKY gCOZAI6Qb01ha+N4bhQBE3oCR2hvtgjWWSulbZkdAhmYq8vY9RHhveRXbhtSBp39 ItnZrKVL6CyqwrUO+CeHM3FSOFWIolgFRLCn/tuRRHbEzksju+PerBmxpomaxpLr Q1hw+/NoDs0keBa5QyuGpkaKZp1waDV0FQfJc8+YTAa98I7xi78LymASPw3EyHZZ n4Bxzwqu1pwTS5NTYSxRpqqbRIpn060OlzxxQdsoH4rmINwCF2w+yDwGgtx0oSd2 r75kv7DXU6A4J9pXhAUPnixLjpJH2u54b7RvQ5yAXVNdIl5OCB4R7vTf4l21kRx4 MN44ulvoJM2+3m+xjRmtBPdQKcWOWTe5AEjvZBA9Z3liDAL8jVOWKnZC1Kmy+E37 QWXcNN4NqGw= =u+Ew -END PGP SIGNATURE-
Bug#975012: dplfin: FTBFS: 69% tests passed, 15 tests failed out of 49
Hi Sebastian, Thanks for your bug report. I am preparing a transition to boost 1.74 and tested my minimal changes to fix #974948. It worked locally. Anyway I have reverted the fix for #974948 and it did not help. So the reason is somewhere else. Sorry for the inconvenience. Best regards Anton Am Di., 17. Nov. 2020 um 22:39 Uhr schrieb Sebastian Ramacher : > > Source: dolfin > Version: 2019.2.0~git20200629.946dbd3-6 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org
Bug#972372: sfepy: diff for NMU version 2019.4-2.1
Hi Stefano, thanks for NMU, feel free to upload it immediately. Just push your changes into the git. Best regards, Anton Am Sa., 17. Okt. 2020 um 22:15 Uhr schrieb Stefano Rivera : > > Control: tags 972372 + patch > Control: tags 972372 + pending > > Dear maintainer, > > I've prepared an NMU for sfepy (versioned as 2019.4-2.1) and > uploaded it to DELAYED/3. Please feel free to tell me if I > should delay it longer. > > Regards. > > SR > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#966871: Fixed
966871 fixed 3.3.7-3 thanks
Bug#967016: marked as pending in libopenshot
Control: tag -1 pending Hello, Bug #967016 in libopenshot reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/libopenshot/-/commit/2131f128e7d34d3e733a7809ed07ba47eb0c9712 Fix FTBFS due to gcc-10 and ffmpeg. (Closes: #967016) (this message was generated automatically) -- Greetings https://bugs.debian.org/967016
Bug#964666: marked as pending in libopenshot
Control: tag -1 pending Hello, Bug #964666 in libopenshot reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/libopenshot/-/commit/43689f7b3b058dfd0ee83dd7ff6a6bc863a02004 Add d/not-installed. (Closes: #964666) (this message was generated automatically) -- Greetings https://bugs.debian.org/964666
Bug#962253: esys-particle: diff for NMU version 2.3.5+dfsg1-4.1
Hello Adrian, thanks a lot for the patch and NMU. I am preparing a new upload of esys-particle and I will integrate your changes. Could you please then cancel yout upload to prevent the race condition? Thanks Anton Am Mi., 10. Juni 2020 um 15:09 Uhr schrieb Adrian Bunk : > > Control: tags 962253 + patch > Control: tags 962253 + pending > > Dear maintainer, > > I've prepared an NMU for esys-particle (versioned as 2.3.5+dfsg1-4.1) > and uploaded it to DELAYED/2. Please feel free to tell me if I should > cancel it. > > cu > Adrian > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#960426: Forwarded
forwarded 960426 https://github.com/svgpp/svgpp/issues/79 thanks
Bug#944197: HELP needed for uploading a new upstream version of the Rheolef package
I think I sponsored this package some time ago and I will try to have a look again. Anton Am Mo., 23. März 2020 um 18:33 Uhr schrieb Pierre Saramito : > > Hi Andreas Tille, > > > From Andreas: > > Currently I can only support Covid-19 related > > packages (which we try to assemble in Debian Med team currently) > > Let me known if I could help the Debian Med team ? > I remain "confined" at home, but I could help (test pkg, ect) ? > > > > please find some other sponsor from Debian Science project. > > Is there somebody from the Debian science project > to just help me for uploading the Rheolef-7.1-1 pkg ? > The debianization is ready and well-tested at >https://salsa.debian.org/science-team/rheolef > It closes the two FTBFS bugs: #944197 and #946116 > > > Best wishes, > > Pierre > > -- > pierre.saram...@imag.fr > Directeur de Recherche CNRS > Laboratoire Jean Kuntzmann, Grenoble, France > http://ljk.imag.fr/membres/Pierre.Saramito >
Bug#937455: pygts: Python2 removal in sid/bullseye
Hi Stuart, Yes, I think it can be removed and reintroduced if the python3-version appears. Regards Anton Am Mi., 29. Jan. 2020 um 02:18 Uhr schrieb Stuart Prescott : > > pygts is dead upstream and the C parts of the code will need a bit of work to > port them to Python 3. This package does have a reasonable popcon (281) but > it's hard to see the porting work happening. > > The package needs to go through NEW either with an added python3-gts binary > package or if removed and then re-added later after porting. > > Is it time to remove pygts from Debian? > > -- > Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net > Debian Developer http://www.debian.org/ stu...@debian.org > GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#948713: marked as pending in python-pygraphviz
Hello Sandro, thank you for your upload. I have cancelled my NMU. Best regards Anton
Bug#948713: diff NMU for python-pygraphviz_1.5-2.1
tags 948713 +pending thanks Dear maintainer, I have prepared an NMU (versioned as 1.5-2.1) and uploaded to DELAYED/5. Please fell free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. Best regards Anton nmu.debdiff Description: Binary data
Bug#948713: Patch
tags 948713 +patch Dear maintainer, please consider to apply the attached patch. Thanks Anton From d639572ac17b8006dcc0b52997027229eecddd09 Mon Sep 17 00:00:00 2001 From: Anton Gladky Date: Sun, 12 Jan 2020 15:30:27 +0100 Subject: [PATCH] Install python3-files into a proper place; Closes: #948713 --- debian/changelog | 7 +++ debian/rules | 9 + 2 files changed, 16 insertions(+) diff --git a/debian/changelog b/debian/changelog index 9ac4f59..5feba4e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +python-pygraphviz (1.5-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Install python3-files into a proper place; Closes: #948713 + + -- Anton Gladky Sun, 12 Jan 2020 15:28:52 +0100 + python-pygraphviz (1.5-2) unstable; urgency=medium [ Ondřej Nový ] diff --git a/debian/rules b/debian/rules index 98da16a..d5f531e 100755 --- a/debian/rules +++ b/debian/rules @@ -10,6 +10,15 @@ ifeq (,$(filter nostrip,$(DEB_BUILD_OPTIONS))) dh_strip -ppython3-pygraphviz --dbg-package=python3-pygraphviz-dbg endif +PYTHON3=$(shell py3versions -r) + +override_dh_install: + set -e; \ + for python in $(PYTHON3); do \ + $$python setup.py install --install-layout=deb --root=$(CURDIR)/debian/python3-pygraphviz; \ + $$python-dbg setup.py install --install-layout=deb --root=$(CURDIR)/debian/python3-pygraphviz-dbg; \ + done + override_dh_installexamples: dh_installexamples -ppython-pygraphviz-doc examples/* -- 2.24.1
Bug#948713: python3-pygraphviz is empty
Package: python3-pygraphviz Version: 1.5-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, the binary package python3-pygraphviz_1.5-2 seems to be empty [1]: /usr/share/doc/python3-pygraphviz/changelog.Debian.gz /usr/share/doc/python3-pygraphviz/copyright [1] https://packages.debian.org/sid/amd64/python3-pygraphviz/filelist Could you please have a look? Thank you Anton -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl4bKYoRHGdsYWRrQGRl Ymlhbi5vcmcACgkQ0+Fzg8+n/wYtgRAAk/DLGGYctSlaL8uB66jPF25KxxzLA1FF KujXkGJNddGKNEiObQM8zO/hih0A5Xmd4TgqIUY5RsyCYjKkNfrybpWH2NYb+F5p 1R9ncj/YyEqwCx1BdgaUL86zqEPH2dU0Fn9Ejfh1vlA5bLdXfpxNVKjfOxgu8q6C 9DXghpS+7CmIg+cFfil0mAc7gu1tTm+uEgd4fNcJOcZUpz7SdBYIK3yjKYR/HIRj TA8JK99afmOJgyC1zB84Xut8WSPjhxo2EavUBdPG9qAgLIA+IMad+4mAn2wqhYFu Y6hB1QBqxlYZYbNrL5l43SPKrrYcAEvwKTWIr64g7Ck/rmXILqp7bLB6LFNKTA3H YaJ6/QgRVfYuU54yuJn+CO7nd93gfT7jrG4nJI5nYcQLQiL8mOIICOONyHKkAR0O 0aG8lQMwGVLurF2BCfqiwrCt3jcJIvXRYTdLnn1HDVDgNz4/iNdnRRCjhFxKA3bx Enzb/J1puisdDPnG70JhZqI/x40KCbNE+QG8mnyUwKXAudeW3PZ2DbBkbCsF8IoD NX1eYsM2OdkgCFYLe/I8qTi5Oc/FCb9OwrXiNwsofVunAKYaVzOt0KA11zjaH8fg 9QPP5FGnvOgB4EWmx8+VPUf1Atwah6JAee8xf+SJduZwNx5PUqry/WhUZ3nU8k0h H/WSTYZSv3w= =TEnE -END PGP SIGNATURE-
Bug#946984: yade: Ships python3.8 scripts, without any python3 or python3.8 deps
Hi, it is already done and will be uploaded tonight. The problem is that it should go through NEW-queue. Regards Anton Am Mi., 18. Dez. 2019 um 22:51 Uhr schrieb Dimitri John Ledkov : > > Package: yade > Version: 2019.12~git~0~e74819ea-4 > Severity: grave > > Dear Maintainer, > > Autopkgtest correctly points out that `yade` cannot be executed in > testing, upon migration. > > yade appears to be switched from python2 to python3 incorrectly as follows. > > Package yade builds scripts as python3.8, yet depends on python-yade > (py2 name by policty) and python:Depends => meaning that --with > python3 (dh_python3) does nothing and doesn't generate neither python3 > nor python3.8 depends. > > Then python-yade package is missnamed too, it must be named > python3-yade for dh_python3 to process it, and for example correct any > scripts shebangs from python3.8 to just python3 (if appropriate). > > Overall this package will not migrate, and will not work in testing as > is. > > Please > 1) correct Package: yade dependency from python:Depends, to python3:Depends > 2) correct Package: yade dependency from python-yade, to python3-yade > 3) correct Package: python-yade name to python3-yade > 4) Rename relevant debian/python-yade.* to debian/python3-yade.* > > Please do this soon, as yade is due to be autoremoved from testing! > > Regards, > > Dimitri. > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#946223: [NMU] FTFBS with CGAL 5.0
Hi Joachim, thanks for the patch! Yade is building already in experimental, but not on all archs. I will try to fix it as soon as possible and upload to unstable. Regards Anton Am Do., 5. Dez. 2019 um 21:27 Uhr schrieb Joachim Reichel : > > Source: yade > Version: 2019.01a-3 > Severity: serious > Tags: ftbfs > Control: block 944417 by -1 > > Hi, > > the transition to CGAL 5.0 started (see bug #944417) and your package FTBFS. > Attached are two patches that fix the problem. In addition, one needs to add > "Build-Depends: libcgal-dev (>= 5.0~). > > Just applying these two patches is not enough due to bug #938859. What is your > planned timeline for an upload to unstable? > > Best regards, > Joachim > > -- System Information: > Debian Release: 10.2 > APT prefers stable-debug > APT policy: (800, 'stable-debug'), (800, 'stable'), (700, 'testing-debug'), > (700, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#945840: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory
Hi, I agree with Giovanni, I think we need to re-enable python2 for a while. Regards Anton
Bug#945488: Fixed already
forcemerge 944892 945488 thanks
Bug#874878: [freemat] Future Qt4 removal from Buster
Removal requested: #943958 Anton
Bug#874878: [freemat] Future Qt4 removal from Buster
Yes, I think the package should be removed. Also the package has no active uploader and nobody in science group identified such an interest [1]. I will take care about it. [1] https://lists.debian.org/debian-science/2019/09/msg00018.html Anton
Bug#942000: dune-grid build-depends on removed python-vtk6
Source: dune-grid Severity: serious Dear Maintainer, dune-grid build-depends on the python-vtk6 package, which was dropped due to the python2-removal. Please remove the package from build-depends. Thanks, Anton
Bug#929597: CVE-2019-12211 CVE-2019-12212 CVE-2019-12213 CVE-2019-12214
severity 929597 important thanks The fix from upstream is still not available. I am not feeling confident enough to provide a fix for this complex peace of code without breaking it. Also reducing the severity. If the security team decides to keep it "grave" - feel free to revert it. Regards Anton Am Mo., 3. Juni 2019 um 20:23 Uhr schrieb Anton Gladky : > > There is no upstream fix still available. > > I am planning to decrease the severity of > the ticket to normal and track it as a simple > security issue. > > Anton > > Am Mo., 27. Mai 2019 um 23:01 Uhr schrieb Anton Gladky : > > > > CVE-2019-12214 does not affect buster and stretch. > > Jessie should be double checked because an older > > version is used there. > > > > Anton > > > > Am So., 26. Mai 2019 um 22:01 Uhr schrieb Anton Gladky : > > > > > > Hi Moritz, > > > > > > thanks for the reporting. As far as I see, there is still > > > no available fix from upstream. > > > > > > Cheers > > > > > > Anton > > > > > > Am So., 26. Mai 2019 um 21:27 Uhr schrieb Moritz Muehlenhoff > > > : > > > > > > > > Source: freeimage > > > > Severity: grave > > > > Tags: security > > > > > > > > Please see > > > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12211 > > > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12212 > > > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12213 > > > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12214 > > > > > > > > Cheers, > > > > Moritz > > > > > > > > -- > > > > debian-science-maintainers mailing list > > > > debian-science-maintain...@alioth-lists.debian.net > > > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#929597: CVE-2019-12211 CVE-2019-12212 CVE-2019-12213 CVE-2019-12214
There is no upstream fix still available. I am planning to decrease the severity of the ticket to normal and track it as a simple security issue. Anton Am Mo., 27. Mai 2019 um 23:01 Uhr schrieb Anton Gladky : > > CVE-2019-12214 does not affect buster and stretch. > Jessie should be double checked because an older > version is used there. > > Anton > > Am So., 26. Mai 2019 um 22:01 Uhr schrieb Anton Gladky : > > > > Hi Moritz, > > > > thanks for the reporting. As far as I see, there is still > > no available fix from upstream. > > > > Cheers > > > > Anton > > > > Am So., 26. Mai 2019 um 21:27 Uhr schrieb Moritz Muehlenhoff > > : > > > > > > Source: freeimage > > > Severity: grave > > > Tags: security > > > > > > Please see > > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12211 > > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12212 > > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12213 > > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12214 > > > > > > Cheers, > > > Moritz > > > > > > -- > > > debian-science-maintainers mailing list > > > debian-science-maintain...@alioth-lists.debian.net > > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#929597: CVE-2019-12211 CVE-2019-12212 CVE-2019-12213 CVE-2019-12214
CVE-2019-12214 does not affect buster and stretch. Jessie should be double checked because an older version is used there. Anton Am So., 26. Mai 2019 um 22:01 Uhr schrieb Anton Gladky : > > Hi Moritz, > > thanks for the reporting. As far as I see, there is still > no available fix from upstream. > > Cheers > > Anton > > Am So., 26. Mai 2019 um 21:27 Uhr schrieb Moritz Muehlenhoff > : > > > > Source: freeimage > > Severity: grave > > Tags: security > > > > Please see > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12211 > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12212 > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12213 > > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12214 > > > > Cheers, > > Moritz > > > > -- > > debian-science-maintainers mailing list > > debian-science-maintain...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#929597: CVE-2019-12211 CVE-2019-12212 CVE-2019-12213 CVE-2019-12214
Hi Moritz, thanks for the reporting. As far as I see, there is still no available fix from upstream. Cheers Anton Am So., 26. Mai 2019 um 21:27 Uhr schrieb Moritz Muehlenhoff : > > Source: freeimage > Severity: grave > Tags: security > > Please see > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12211 > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12212 > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12213 > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12214 > > Cheers, > Moritz > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#917500: liggghts: FTBFS (style_atom.h: No such file or directory)
Hello Santiago, thanks for the reporting it. Unfortunately I am not able to reproduce the described error. It builds just fine and the recent upload into Debian did not identified the problems with the package [1]. Please give some more information, how can it be reproduced. Thanks [1] https://buildd.debian.org/status/package.php?p=liggghts Anton Am Fr., 28. Dez. 2018 um 00:57 Uhr schrieb Santiago Vila : > > Package: src:liggghts > Version: 3.8.0+repack1-1 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > > > [...] > debian/rules build-indep > dh build-indep --buildsystem=cmake > --builddirectory=/<>/liggghts-3.8.0+repack1/debian/build >dh_update_autotools_config -i -O--buildsystem=cmake > -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build >dh_autoreconf -i -O--buildsystem=cmake > -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build >dh_auto_configure -i -O--buildsystem=cmake > -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build > cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ../.. > -- The C compiler identification is GNU 8.2.0 > -- The CXX compiler identification is GNU 8.2.0 > -- Check for working C compiler: /usr/bin/cc > -- Check for working C compiler: /usr/bin/cc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Detecting C compile features > -- Detecting C compile features - done > > [... snipped ...] > > CMAKE_EXPORT_NO_PACKAGE_REGISTRY > > > -- Build files have been written to: > /<>/liggghts-3.8.0+repack1/debian/build >dh_auto_build -i -O--buildsystem=cmake > -O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build > cd debian/build && make -j1 "INSTALL=install --strip-program=true" > make[1]: Entering directory > '/<>/liggghts-3.8.0+repack1/debian/build' > /usr/bin/cmake -S/<>/liggghts-3.8.0+repack1 > -B/<>/liggghts-3.8.0+repack1/debian/build --check-build-system > CMakeFiles/Makefile.cmake 0 > /usr/bin/cmake -E cmake_progress_start > /<>/liggghts-3.8.0+repack1/debian/build/CMakeFiles > /<>/liggghts-3.8.0+repack1/debian/build/CMakeFiles/progress.marks > make -f CMakeFiles/Makefile2 all > make[2]: Entering directory > '/<>/liggghts-3.8.0+repack1/debian/build' > make -f src/CMakeFiles/libliggghts.dir/build.make > src/CMakeFiles/libliggghts.dir/depend > make[3]: Entering directory > '/<>/liggghts-3.8.0+repack1/debian/build' > cd /<>/liggghts-3.8.0+repack1/debian/build && /usr/bin/cmake -E > cmake_depends "Unix Makefiles" /<>/liggghts-3.8.0+repack1 > /<>/liggghts-3.8.0+repack1/src > /<>/liggghts-3.8.0+repack1/debian/build > /<>/liggghts-3.8.0+repack1/debian/build/src > /<>/liggghts-3.8.0+repack1/debian/build/src/CMakeFiles/libliggghts.dir/DependInfo.cmake > --color= > Scanning dependencies of target libliggghts > make[3]: Leaving directory '/<>/liggghts-3.8.0+repack1/debian/build' > make -f src/CMakeFiles/libliggghts.dir/build.make > src/CMakeFiles/libliggghts.dir/build > make[3]: Entering directory > '/<>/liggghts-3.8.0+repack1/debian/build' > [ 0%] Building CXX object src/CMakeFiles/libliggghts.dir/angle.cpp.o > cd /<>/liggghts-3.8.0+repack1/debian/build/src && /usr/bin/mpicxx > -Dlibliggghts_EXPORTS -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" > -DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" > -DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)" > -I/usr/include/vtk-6.3 -I/usr/include/freetype2 > -I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/openmpi > -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi > -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/jsoncpp > -I/usr/include/eigen3 -I/<>/liggghts-3.8.0+repack1 > -I/<>/liggghts-3.8.0+repack1/src -g -O2 > -fdebug-prefix-map=/<>/liggghts-3.8.0+repack1=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG > -fPIC -o CMakeFiles/libliggghts.dir/angle.cpp.o -c > /<>/liggghts-3.8.0+repack1/src/angle.cpp > [ 0%] Building CXX object src/CMakeFiles/libliggghts.dir/angle_hybrid.cpp.o > cd /<>/liggghts-3.8.0+repack1/debian/build/src && /usr/bin/mpicxx > -Dlibliggghts_EXPORTS -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" > -DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" > -DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)" > -I/usr/include/vtk-6.3 -I/usr/include/freetype2 > -I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/openmpi >
Bug#917869: python-escript FTBFS on armhf, mips, mipsel and mips64el
Thanks, I will take care of it. Anton Am Mi., 2. Jan. 2019 um 00:51 Uhr schrieb Adrian Bunk : > > On Mon, Dec 31, 2018 at 06:51:12AM +, peter green wrote: > >... while the mips and mipsel builds ran out of virtual memory. > > > > It may be worth playing with the settings, the first thing to try is > > probably -Wl,-no-keep-memory , if that fails it may be worth trying > > optimising for size ( -Os instead of -O2 ) > > I'd be surprised if -Os would help. > > Most of the time the mips/mipsel build can be fixed by appending -g1 to > the CXXFLAGS, overwriting the default -g (which is -g2). > > cu > Adrian > > -- > >"Is there not promise of rain?" Ling Tan asked suddenly out > of the darkness. There had been need of rain for many days. >"Only a promise," Lao Er said. >Pearl S. Buck - Dragon Seed > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#915344: openfoam: diff for NMU version 4.1+dfsg1-2.3
Could you please push your changes into the git? Thanks! Anton Am Di., 1. Jan. 2019 um 13:35 Uhr schrieb Adrian Bunk : > > On Tue, Jan 01, 2019 at 01:02:07AM +0100, Anton Gladky wrote: > > Hello Adrian, > > Hello Anton, > > > thank you for the patch! Feel free to put the NMU-upload > > into the DELAYED/0. > > thanks, done. > > > Regards > > > > Anton > > cu > Adrian > > -- > >"Is there not promise of rain?" Ling Tan asked suddenly out > of the darkness. There had been need of rain for many days. >"Only a promise," Lao Er said. >Pearl S. Buck - Dragon Seed >
Bug#915344: openfoam: diff for NMU version 4.1+dfsg1-2.3
Hello Adrian, thank you for the patch! Feel free to put the NMU-upload into the DELAYED/0. Regards Anton Am Mo., 31. Dez. 2018 um 16:39 Uhr schrieb Adrian Bunk : > > Control: tags 915344 + patch > Control: tags 915344 + pending > > Dear maintainer, > > I've prepared an NMU for openfoam (versioned as 4.1+dfsg1-2.3) and > uploaded it to DELAYED/14. Please feel free to tell me if I should > cancel it. > > cu > Adrian > > -- > >"Is there not promise of rain?" Ling Tan asked suddenly out > of the darkness. There had been need of rain for many days. >"Only a promise," Lao Er said. >Pearl S. Buck - Dragon Seed > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#916971: gmsh: diff for NMU version 3.0.6+dfsg1-4.1
Hello Gilles,
thanks for the NMU! Feel free to put it into the DELAYED/0.
Regards
Anton
Am So., 30. Dez. 2018 um 12:24 Uhr schrieb Gilles Filippini :
>
> Control: tags 916971 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for gmsh (versioned as 3.0.6+dfsg1-4.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
>
> Regards,
>
> _g.
>
>
> diff -Nru gmsh-3.0.6+dfsg1/debian/changelog gmsh-3.0.6+dfsg1/debian/changelog
> --- gmsh-3.0.6+dfsg1/debian/changelog 2018-12-03 01:47:52.0 +0100
> +++ gmsh-3.0.6+dfsg1/debian/changelog 2018-12-30 10:09:26.0 +0100
> @@ -1,3 +1,11 @@
> +gmsh (3.0.6+dfsg1-4.1) unstable; urgency=medium
> +
> + * Non-maintainer upload.
> + * New patch support-med-4.patch to fix FTBFS against med-fichier 4.0.0
> +(Closes: #916971)
> +
> + -- Gilles Filippini Sun, 30 Dec 2018 10:09:26 +0100
> +
> gmsh (3.0.6+dfsg1-4) unstable; urgency=medium
> [ Joost van Zwieten ]
> diff -Nru gmsh-3.0.6+dfsg1/debian/patches/series
> gmsh-3.0.6+dfsg1/debian/patches/series
> --- gmsh-3.0.6+dfsg1/debian/patches/series 2018-12-03 01:47:52.0
> +0100
> +++ gmsh-3.0.6+dfsg1/debian/patches/series 2018-12-24 09:28:43.0
> +0100
> @@ -3,3 +3,4 @@
> 30_delete_gl2ps_from_source.patch
> 40_gnuinstalldirs.patch
> 140_drop_css.patch
> +support-med-4.patch
> diff -Nru gmsh-3.0.6+dfsg1/debian/patches/support-med-4.patch
> gmsh-3.0.6+dfsg1/debian/patches/support-med-4.patch
> --- gmsh-3.0.6+dfsg1/debian/patches/support-med-4.patch 1970-01-01
> 01:00:00.0 +0100
> +++ gmsh-3.0.6+dfsg1/debian/patches/support-med-4.patch 2018-12-24
> 09:28:43.0 +0100
> @@ -0,0 +1,386 @@
> +Index: gmsh-3.0.6+dfsg1/Geo/GModelIO_MED.cpp
> +===
> +--- gmsh-3.0.6+dfsg1.orig/Geo/GModelIO_MED.cpp
> gmsh-3.0.6+dfsg1/Geo/GModelIO_MED.cpp
> +@@ -29,7 +29,7 @@ extern "C" {
> + #include
> + }
> + +-#if (MED_MAJOR_NUM == 3)
> ++#if (MED_MAJOR_NUM >= 3)
> + // To avoid too many ifdefs below we use defines for the bits of the
> + // API that did not change too much between MED2 and MED3. If we remove
> + // MED2 support at some point, please remove these defines and replace
> +@@ -69,7 +69,7 @@ med_geometrie_element msh2medElementType
> + case MSH_HEX_20: return MED_HEXA20;
> + case MSH_PRI_15: return MED_PENTA15;
> + case MSH_PYR_13: return MED_PYRA13;
> +-#if (MED_MAJOR_NUM == 3)
> ++#if (MED_MAJOR_NUM >= 3)
> + case MSH_QUA_9: return MED_QUAD9;
> + case MSH_HEX_27: return MED_HEXA27;
> + #endif
> +@@ -95,7 +95,7 @@ int med2mshElementType(med_geometrie_ele
> + case MED_HEXA20: return MSH_HEX_20;
> + case MED_PENTA15: return MSH_PRI_15;
> + case MED_PYRA13: return MSH_PYR_13;
> +-#if (MED_MAJOR_NUM == 3)
> ++#if (MED_MAJOR_NUM >= 3)
> + case MED_QUAD9: return MSH_QUA_9;
> + case MED_HEXA27: return MSH_HEX_27;
> + #endif
> +@@ -113,7 +113,7 @@ int med2mshNodeIndex(med_geometrie_eleme
> + case MED_TRIA6:
> + case MED_QUAD4:
> + case MED_QUAD8:
> +-#if (MED_MAJOR_NUM == 3)
> ++#if (MED_MAJOR_NUM >= 3)
> + case MED_QUAD9:
> + #endif
> + return k; // same node numbering as in Gmsh
> +@@ -133,7 +133,7 @@ int med2mshNodeIndex(med_geometrie_eleme
> + static const int map[20] =
> {0,1,3,2,4,5,6,7,8,9,10,11,16,17,18,19,12,13,14,15};
> + return map[k];
> + }
> +-#if (MED_MAJOR_NUM == 3)
> ++#if (MED_MAJOR_NUM >= 3)
> + case MED_HEXA27: {
> + static const int map[27] =
> {0,1,3,2,4,5,6,7,8,9,10,11,16,17,18,19,12,13,14,15,
> + 20, 22, 21, 23, 24, 25, 26};
> +@@ -185,7 +185,7 @@ int GModel::readMED(const std::string
> + char meshName[MED_TAILLE_NOM + 1], meshDesc[MED_TAILLE_DESC + 1];
> + med_int spaceDim;
> + med_maillage meshType;
> +-#if (MED_MAJOR_NUM == 3)
> ++#if (MED_MAJOR_NUM >= 3)
> + med_int meshDim, nStep;
> + char dtUnit[MED_SNAME_SIZE + 1];
> + char axisName[3 * MED_SNAME_SIZE + 1], axisUnit[3 * MED_SNAME_SIZE + 1];
> +@@ -241,7 +241,7 @@ int GModel::readMED(const std::string
> + char meshName[MED_TAILLE_NOM + 1], meshDesc[MED_TAILLE_DESC + 1];
> + med_int spaceDim, nStep = 1;
> + med_maillage meshType;
> +-#if (MED_MAJOR_NUM == 3)
> ++#if (MED_MAJOR_NUM >= 3)
> + med_int meshDim;
> + char dtUnit[MED_SNAME_SIZE + 1];
> + char axisName[3 * MED_SNAME_SIZE + 1], axisUnit[3 * MED_SNAME_SIZE + 1];
> +@@ -276,7 +276,7 @@ int GModel::readMED(const std::string
> + MEDversionLire(fid, [0], [1], [2]);
> + + // read nodes
> +-#if (MED_MAJOR_NUM == 3)
> ++#if (MED_MAJOR_NUM >= 3)
> + med_bool changeOfCoord, geoTransform;
> + med_int numNodes = MEDmeshnEntity(fid, meshName, MED_NO_DT, MED_NO_IT,
> MED_NODE,
> + MED_NO_GEOTYPE, MED_COORDINATE,
> MED_NO_CMODE,
> +@@ -295,7 +295,7 @@ int GModel::readMED(const std::string
> + }
> + std::vector verts(numNodes);
> + std::vector coord(spaceDim * numNodes);
>
Bug#916234: depending software build failure (arm64, armel, mips)
Hello, #915934 can be related. Please forward to GCC. Anton Am Di., 11. Dez. 2018 um 19:54 Uhr schrieb Filippo Rusconi : > > Package: libeigen3-dev > Version: 3.3.5-2 > Severity: serious > > > Greetings, > > when building libpwiz on the arm64, armel, mips architectures, the build fails > with the following error: > > In file included from /usr/include/eigen3/Eigen/SparseCore:50, > from /usr/include/eigen3/Eigen/Sparse:26, > from /usr/include/eigen3/Eigen/Eigen:2, > from pwiz/analysis/demux/DemuxTypes.hpp:24, > from pwiz/analysis/demux/DemuxDebugWriter.hpp:23, > from pwiz/analysis/demux/DemuxDebugWriter.cpp:20: > /usr/include/eigen3/Eigen/src/SparseCore/SparseBlock.h: In member function > 'Eigen::internal::sparse_matrix_block_impl BlockCols>::BlockType& > Eigen::internal::sparse_matrix_block_impl BlockCols>::operator=(const BlockType&)': > /usr/include/eigen3/Eigen/src/SparseCore/SparseBlock.h:216:33: error: > expected primary-expression before '>' token >return operator=(other); > ^ > > Please, see > > https://buildd.debian.org/status/fetch.php?pkg=libpwiz=arm64=3.0.18342-1=1544522661=log > https://buildd.debian.org/status/fetch.php?pkg=libpwiz=armel=3.0.18342-1=1544523773=log > https://buildd.debian.org/status/fetch.php?pkg=libpwiz=mips=3.0.18342-1=1544524240=log > > I am not positively sure that this package is guilty, but I cannot see another > bug reporting route at the moment. > > Sincerely, > Filippo > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages libeigen3-dev depends on: > ii pkg-config 0.29-4+b1 > > libeigen3-dev recommends no packages. > > Versions of packages libeigen3-dev suggests: > pn libeigen3-doc > pn libmpfrc++-dev > > -- no debconf information > > -- > > ⢀⣴⠾⠻⢶⣦⠀ Filippo Rusconi, PhD > ⣾⠁⢠⠒⠀⣿⡁ Scientist at CNRS > ⢿⡄⠘⠷⠚⠋⠀ Debian Developer > ⠈⠳⣄ http://msxpertsuite.org > http://www.debian.org > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#914063: diff NMU for tagpy_2013.1-6.1
tags 914063 +pending +patch thanks Dear maintainer, I have prepared an NMU (versioned as 2013.1-6.1) and uploaded to DELAYED/5. Please fell free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. Best regards Anton nmu.debdiff Description: Binary data
Bug#913980: diff NMU for anytun_0.3.7-1.1
tags 913980 +pending +patch thanks Dear maintainer, I have prepared an NMU (versioned as 0.3.7-1.1) and uploaded to DELAYED/10. Please fell free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. Best regards Anton anytun.debdiff Description: Binary data
Bug#913980: FTBFS against boost1.67
Source: anytun
Version: 0.3.7-1
Severity: serious
Dear maintainer,
there is an ongoing boost1.67 transition [1].
Your package fails to build with the following message:
resolver.cpp: In member function 'void
ResolveHandler::operator()(const boost::system::error_code&,
boost::asio::ip::basic_resolver_iterator)':
resolver.cpp:84:21: error: 'boost::system::posix_error' has not been declared
if(boost::system::posix_error::success == e) {
^~~
make[1]: *** [Makefile:227: resolver.o] Error 1
[1] https://release.debian.org/transitions/html/boost1.67.html
Best regards
Anton
Bug#897826: openfoam: diff for NMU version 4.1+dfsg1-2.2
Hello Adrian, thank you for your work on OpenFoam. Please feel free to move the upload into the DELAYED/0. Best regards Anton 2018-08-12 15:08 GMT+02:00 Adrian Bunk : > Dear maintainer, > > I've prepared an NMU for openfoam (versioned as 4.1+dfsg1-2.2) and > uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it. > > This change works around gcc 8 seemingly using more memory, > which caused FTBFS on mips/mipsel. > > cu > Adrian > > -- > >"Is there not promise of rain?" Ling Tan asked suddenly out > of the darkness. There had been need of rain for many days. >"Only a promise," Lao Er said. >Pearl S. Buck - Dragon Seed > > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
