Bug#980716: ITP: luma.core -- component library providing a Pillow-compatible drawing canvas

Package: wnpp Severity: wishlist Owner: Anton Gladky X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: luma.core Version : 2.2.0 Upstream Author : Richard Hull and contributors * URL : https://github.com/rm-hull/luma.core/ * License : MIT

Bug#980716: ITP: luma.core -- component library providing a Pillow-compatible drawing canvas

Package: wnpp Severity: wishlist Owner: Anton Gladky X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: luma.core Version : 2.2.0 Upstream Author : Richard Hull and contributors * URL : https://github.com/rm-hull/luma.core/ * License : MIT

Re: [Yade-users] [Question #695082]: Yadedaily installation and mpmath error (focal)

Question #695082 on Yade changed: https://answers.launchpad.net/yade/+question/695082 Anton Gladky posted a new comment: I have added the dependency into yadedaily https://gitlab.com/yade- dev/trunk/-/commit/fcd4d709a16ffaac3422d79dfc9926f67ee349c2 -- You received this question notification

Re: Sponsoring before freeze

Hi Thomas, uploaded! Thanks for your contribution. Please consider adding autopkgtest for the next upload. If you prepare them before freeze, please let me know and I will upload it. Regards Anton Am Do., 14. Jan. 2021 um 00:39 Uhr schrieb Thomas Schiex : > > Dear Anton, > > I have tried to

Re: Sponsoring before freeze

Hi Thomas, uploaded! Thanks for your contribution. Please consider adding autopkgtest for the next upload. If you prepare them before freeze, please let me know and I will upload it. Regards Anton Am Do., 14. Jan. 2021 um 00:39 Uhr schrieb Thomas Schiex : > > Dear Anton, > > I have tried to

Re: python-rioxarray

Hi Magnus, there are only recommendation, how do I usually deal with such kind of problems: > * the upstream tar ball comes with the egg-info directory. Presumably > I should remove that since it gets generated? Yes, remove. Put the wildcard in d/copyright under Files-Excluded section and do

Re: RFS: macaulay 1.17.1

Hi, I will take care of it. Anton Am So., 17. Jan. 2021 um 13:13 Uhr schrieb Torrance, Douglas : > > On 1/11/21 7:54 PM, Doug Torrance wrote: > > A new release of Macaulay2 was just announced. I've packaged it for > > Debian, and I think it's ready for upload to unstable: > > > >

Re: Sponsoring of packages for the next stable release

let me know. Best regards Anton Anton Am Do., 14. Jan. 2021 um 00:33 Uhr schrieb Ryan Pavlik : > > > On 1/9/2021 2:27 PM, Anton Gladky wrote: > > Dear members of Debian Science Team, > > > > we are approaching to a new stable release freeze. If youhave some > >

Re: Sponsoring of packages for the next stable release

let me know. Best regards Anton Anton Am Do., 14. Jan. 2021 um 00:33 Uhr schrieb Ryan Pavlik : > > > On 1/9/2021 2:27 PM, Anton Gladky wrote: > > Dear members of Debian Science Team, > > > > we are approaching to a new stable release freeze. If youhave some > >

Re: RFS: robot-testing-framework/2.0.1-1 [ITP] -- Robot Testing Framework

OK, uploaded! Please add manual page for the binary for the next upload. Regards Anton Am Di., 12. Jan. 2021 um 22:46 Uhr schrieb Daniele E. Domenichelli < ddomeniche...@drdanz.it>: > On 12/01/2021 19:19, Daniele E. Domenichelli wrote: > > Should I remove it from the source tarball as well?

Bug#980169: RM: solvespace [armel] -- ROM; FTBFS on armel

Package: ftp.debian.org Severity: normal Dear FTP team, please remove solvespace on armel, where the newer version fails to copmile. Thanks Anton

Sponsoring of packages for the next stable release

Dear members of Debian Science Team, we are approaching to a new stable release freeze. If youhave some packages to be sponsored, please let us know. I have a very limited time, but I will try to review/sponsor someof packages. Best regards Anton OpenPGP_signature Description: OpenPGP

Sponsoring of packages for the next stable release

Dear members of Debian Science Team, we are approaching to a new stable release freeze. If youhave some packages to be sponsored, please let us know. I have a very limited time, but I will try to review/sponsor someof packages. Best regards Anton OpenPGP_signature Description: OpenPGP

Re: RFS: robot-testing-framework/2.0.1-1 [ITP] -- Robot Testing Framework

Hi Daniele, thanks for your contribution! Your package looks fine to me. I have just a couple of minor notes. Please fix them and I will upload the package. - please go through ALL files and put license information, if the copyright is different from default one (check files in cmake-folder

Bug#979306: QVTKOpenGLWidget.h: No such file or directory

Hi Drew, this header is according to documentation deprecated. I tried to use the proposed header, but some more changes in the code are needed. Please verify it and close the bug, if nothing more can be done on vtk9 side. Regards Anton Am Di., 5. Jan. 2021 um 23:49 Uhr schrieb Drew Parsons :

Bug#979306: QVTKOpenGLWidget.h: No such file or directory

Hi Drew, this header is according to documentation deprecated. I tried to use the proposed header, but some more changes in the code are needed. Please verify it and close the bug, if nothing more can be done on vtk9 side. Regards Anton Am Di., 5. Jan. 2021 um 23:49 Uhr schrieb Drew Parsons :

Endorsing Stephan Lachnit's key BB45B0B3FF561BDBD45EE8A9B35B49EA5D563EFE

/sLxhn8g1VkgwlTBin7c vUOdBQznpe9BtCx5zWk8LErXbtYyeRRBHuWoygmnmt2fymBAZ2ekUFqFfARgCX1U fOJIMPW9tfx0+ywrM8mbo4ci1P3Su9VDI1YT+d75FRZbIhsvp71d8e23iQ2rculD UwULequw3BsbOjm8TPasl+0cUOVeaKB5VfYCdx+K31MwhLWZTgw= =3OU3 -END PGP SIGNATURE- Anton Gladky (via nm.debian.org) For details and to comment, visit https

Bug#979306: QVTKOpenGLWidget.h: No such file or directory

Hi Drew, could you please push the version of avogadrolibs which your working on into the git? So I could probably test it against newer vtk9. Thanks. Regards Anton Am Di., 5. Jan. 2021 um 05:09 Uhr schrieb Drew Parsons : > > Package: libvtk9-qt-dev > Version: 9.0.1+dfsg1-6 > Severity: normal

Bug#979306: QVTKOpenGLWidget.h: No such file or directory

Hi Drew, could you please push the version of avogadrolibs which your working on into the git? So I could probably test it against newer vtk9. Thanks. Regards Anton Am Di., 5. Jan. 2021 um 05:09 Uhr schrieb Drew Parsons : > > Package: libvtk9-qt-dev > Version: 9.0.1+dfsg1-6 > Severity: normal

Sebastian Geiger: Befürworter

HOF8fSv6LoYtiGvicjm17FykZr36EMo0876vOxWChGRDaMbaXashDszw8O2gOoWm IW15K7b5zG/jopJDlLSLbI469bFPSEJpEHl2iFkn18TcjXEeV+S4Puy5O+agm275 68fZTFzUYx24Arjk0NO4WSDjmtpNFzTN8l9tI8HbRpLiaOyK3Bc= =Rk/u -END PGP SIGNATURE- Anton Gladky (via nm.debian.org) For details and to comment, visit https://nm.debian.org/process

Bug#978088: HELP needed for uploading a new debianisation 7.1-3 of the Rheolef package

Hi Pierre, sure, I will! Please push your changes in master-branch. It looks only the tags were pushed. Regards Anton Am Sa., 2. Jan. 2021 um 19:41 Uhr schrieb Pierre Saramito : > > Hi Anton, hi all, > > I just commit with git a new release 7.1-3 of the debianisation > of the rheolef package:

Bug#978088: HELP needed for uploading a new debianisation 7.1-3 of the Rheolef package

Hi Pierre, sure, I will! Please push your changes in master-branch. It looks only the tags were pushed. Regards Anton Am Sa., 2. Jan. 2021 um 19:41 Uhr schrieb Pierre Saramito : > > Hi Anton, hi all, > > I just commit with git a new release 7.1-3 of the debianisation > of the rheolef package:

Re: HELP needed for uploading a new debianisation 7.1-3 of the Rheolef package

Hi Pierre, sure, I will! Please push your changes in master-branch. It looks only the tags were pushed. Regards Anton Am Sa., 2. Jan. 2021 um 19:41 Uhr schrieb Pierre Saramito : > > Hi Anton, hi all, > > I just commit with git a new release 7.1-3 of the debianisation > of the rheolef package:

Re: [Yade-dev] New Yade version, beginning of January 2021 - Release notes.

t; GUI (3 MRs): > Draw grid label coordinates, allow custom change of grid density. > remove unaligned margins in GUI inspect. > Add enum support for GUI dropdown menus. > > === > Are the extra debian packages yade-long-double or yade-float128, maybe even > yade-mpfr1

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

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

Re: RFS: macaulay2 1.16.99 (experimental)

Hi Doug, I have uploaded the package into experimental. However CI-pipelines are failing for the package [1]. Could you please have a look, whether the package really fails to build or it is a CI-issue? [1] https://salsa.debian.org/science-team/macaulay2/-/pipelines/211610 Regards Anton Am

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

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

Re: Veusz updated to 3.3.1: please review and upload

Uploaded! Thanks for contribution! Regards Anton Am Mi., 16. Dez. 2020 um 17:37 Uhr schrieb Jeremy Sanders : > > Dear all > > Would it be possible to review and upload the update to veusz (3.3.1) > from the repository? Not much has changed since the last update except > for the upstream

Re: Veusz updated to 3.3.1: please review and upload

Hi, please push pristine-tar branch for .3.3.1. Thanks Anton Am Mi., 16. Dez. 2020 um 17:37 Uhr schrieb Jeremy Sanders : > > Dear all > > Would it be possible to review and upload the update to veusz (3.3.1) > from the repository? Not much has changed since the last update except > for the

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:

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#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

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

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

Bug#977265: Diff

Forgotten diff. 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

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

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

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

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#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

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

Re: HELP needed for uploading a new debianisation of the Rheolef package

Hi, I will take care of it. Regards Anton Am Mi., 16. Dez. 2020 um 21:57 Uhr schrieb Pierre Saramito : > > Hi all, > > This is a kind reminder. > I just commit with git a new release 7.1-2 of the debianisation of the > rheolef package. > > It fixes a FTBFS bug #971933 (see d/changelog): >

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

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

Re: thank you for VTK9 and paraview

Hi, Ben, Matthieu thanks for your advices! It seems we have managed to compile vtk9 builds for most of platforms [1] (thanks to Adrian for that!). For GLES-compilation 4 patches were backported [2]-[5]. And for armel, armhf and mips issues this commit [6] did a trick. If you plan to release the

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

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

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

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

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: 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#975667: 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.

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.

Bug#975660: 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.

Bug#975593: 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.

Bug#975430: 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.

Bug#977146: MR

Merge request ist here [1]. [1] https://salsa.debian.org/debian/s3cmd/-/merge_requests/2 Regards Anton

Bug#977146: s3cmd fails to work due to python3.9

Package: s3cmd Version: 2.1.0-1 Severity: normal Tags: upstream patch Dear Maintainer, package s3cmd fails to work due to python3.9: Traceback (most recent call last): === File

Re: zarr and numcodecs sponsorship

Am Sa., 5. Dez. 2020 um 21:46 Uhr schrieb Antonio Valentino : > > Shall I remove the sponsor request form SoB until [1] is fixed? > Just let me know, when the package is in buildable state. Regards Anton -- debian-science-maintainers mailing list

zarr and numcodecs sponsorship

Hi Antonio, I have uploaded the new version of zarr package into the unstable. For the package numcodecs I have enabled ci-pipeline on the salsa and it looks like some tests are failing [1]. Could you please check, whether those failures are reproducible? [1]

Re: MeshLab update ready to review/sponsor

gt; This will fix https://bugs.debian.org/975157 - the lone bug, a FTBFS and > thus serious. > > I'd also like to acknowledge the help of Anton Gladky in getting the > previous 2020.06 release out. > > Thanks for your reviews and sponsorship! > > Ryan Pavlik > >

Re: thank you for VTK9 and paraview

I also have problems with vtk9 on armel, armhf and mipsel [1]. On armel and mipsel it fails with: == /usr/bin/ld: ../../lib/arm-linux-gnueabi/libvtkCommonDataModel-9.0.so.9.0.1: undefined reference to `__atomic_fetch_add_8' collect2: error: ld returned 1 exit status == and on armhf: ==

Re: RFS: gfan

No problem, please fix it and let me know. Regards Anton On 12/3/20 10:24 PM, Torrance, Douglas wrote: > Thanks, Anton! > > Some of the builds are failing after one of my changes, so I'll likely > be making another sponsorship request again soon.  :) > > Doug > OpenPGP_signature

Re: RFS: gfan

OK, uploaded! Thanks for contribution! Best regards Anton On 11/22/20 4:57 AM, Torrance, Douglas wrote: > Hello! > > Would anyone be able to review and sponsor a new upload of gfan?  Among > other things, it fixes a failing autopkgtest on 32-bit architectures [1]. >

Re: Endorsing Stephan Lachnit's key BB45B0B3FF561BDBD45EE8A9B35B49EA5D563EFE

; > El 28/11/20 a las 22:25, Anton Gladky (via nm.debian.org) escribió: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA512 > > > > > > For nm.debian.org, at 2020-11-28: > > > > > > I have sponsored the package setzer (versions 0.2.

Bug#976115: transition: boost-defaults

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear release team, this is a transition request to upgrade boost-defaults from 1.71 to 1.74. Most of issues in packages are tracked

Bug#976115: transition: boost-defaults

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear release team, this is a transition request to upgrade boost-defaults from 1.71 to 1.74. Most of issues in packages are tracked

Endorsing Stephan Lachnit's key BB45B0B3FF561BDBD45EE8A9B35B49EA5D563EFE

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 For nm.debian.org, at 2020-11-28: I have sponsored the package setzer (versions 0.2.5-1, 0.3.1-1 and 0.3.4-1), which were prepared by Stephan Lachnit and was was highly satisfied with his work. Best regards Anton Gladky -BEGIN PGP SIGNATURE

Bug#975446: libzeep: FTBFS against boost_1.74

reassign 975446 boost1.74[ retitle 975446 b2 is not installed bz boost thanks The problem is in boost, thus I am reassigning it to it. Thanks Anton Am Mi., 25. Nov. 2020 um 20:16 Uhr schrieb Giovanni Mascellani : > > Hi, > > On Mon, 23 Nov 2020 08:19:29 +0100 "Maarten L. Hekkelman" > wrote:

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

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

Bug#975661: rquantlib: FTBFS against boost_1.74

notfound 975661 0.4.12-1 thanks Hi Dirk, I have tested with the rebuilt libquantlib0 it rquantlib builds fine then. Thus I am closing the bug. Thanks! Anton Am Di., 24. Nov. 2020 um 21:57 Uhr schrieb Dirk Eddelbuettel : > Thanks, that is pertinent. The error is actually from the final step

Bug#975672: xylib: FTBFS against boost_1.74

Package: xylib Version: 1.3-1.1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975670: uhd: FTBFS against boost_1.74

Package: uhd Version: 3.15.0.0-3 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975667: supercollider: FTBFS against boost_1.74

Package: supercollider Version: 3.10.4+repack-1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here

Bug#975665: Corrected message

Excuse me for the wrong template in the initial message. Here is the fixed version: Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most relevant part is probably this: [ 16%] Building C object

Bug#975667: supercollider: FTBFS against boost_1.74

Package: supercollider Version: 3.10.4+repack-1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here

Bug#975666: sslsniff: FTBFS against boost_1.74

Package: sslsniff Version: 0.8-8.1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975665: slic3r-prusa: FTBFS against boost_1.74

Package: slic3r-prusa Version: 2.2.0+dfsg1-3 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here

Bug#975661: rquantlib: FTBFS against boost_1.74

Package: rquantlib Version: 0.4.12-1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975660: scram: FTBFS against boost_1.74

Package: scram Version: 0.16.2-1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975660: scram: FTBFS against boost_1.74

Package: scram Version: 0.16.2-1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975593: python-mapnik: FTBFS against boost_1.74

Package: python-mapnik Version: 1:0.0~20200224-7da019cf9-2 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be

Bug#975593: python-mapnik: FTBFS against boost_1.74

Package: python-mapnik Version: 1:0.0~20200224-7da019cf9-2 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be

Bug#975592: pdns-recursor: FTBFS against boost_1.74

Package: pdns-recursor Version: 4.3.5-1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1].

Bug#975590: pdns: FTBFS against boost_1.74

Package: pdns Version: 4.3.1-1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975588: openms: FTBFS against boost_1.74

Package: openms Version: 2.5.0+cleaned1-5 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1].

Bug#975587: odil: FTBFS against boost_1.74

Package: odil Version: 0.12.0-2 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975446: libzeep: FTBFS against boost_1.74

eeks now. > > regards, -maarten > > Op 22-11-2020 om 13:28 schreef Anton Gladky: > > Package: libzeep > Version: 5.0.2-3 > Severity: important > Tags: ftbfs > User: team+bo...@tracker.debian.org > Usertags: boost174 > > -BEGIN PGP SIGNED MESSAGE- > Ha

Bug#975446: libzeep: FTBFS against boost_1.74

Package: libzeep Version: 5.0.2-3 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

[Pkg-kde-extras] Bug#975445: libktorrent: FTBFS against boost_1.74

Package: libktorrent Version: 2.2.0-2 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975445: libktorrent: FTBFS against boost_1.74

Package: libktorrent Version: 2.2.0-2 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975444: libkolabxml: FTBFS against boost_1.74

Package: libkolabxml Version: 1.1.6-8_ Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

Bug#975443: libgdf: FTBFS against boost_1.74

Package: libgdf Version: 0.1.3-4 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most

<    5   6   7   8   9   10   11   12   13   14   >