apertium-afr-nld_0.3.0-1_amd64.changes is NEW
binary:apertium-afr-nld is NEW. binary:apertium-afr-nld is NEW. source:apertium-afr-nld is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of apertium-afr-nld_0.3.0-1_amd64.changes
apertium-afr-nld_0.3.0-1_amd64.changes uploaded successfully to localhost along with the files: apertium-afr-nld_0.3.0-1.dsc apertium-afr-nld_0.3.0.orig.tar.bz2 apertium-afr-nld_0.3.0-1.debian.tar.xz apertium-af-nl_0.3.0-1_all.deb apertium-afr-nld_0.3.0-1_all.deb apertium-afr-nld_0.3.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#865179: marked as done (lhapdf: please build-depend on automake, not obsolete automake1.11)
Your message dated Mon, 16 Dec 2019 06:15:46 + with message-id and subject line Bug#932052: Removed package(s) from unstable has caused the Debian Bug report #865179, regarding lhapdf: please build-depend on automake, not obsolete automake1.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 865179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lhapdf Version: 5.9.1-5 Severity: normal User: debian...@lists.debian.org Usertags: automake1.11 automake1.11-only This package Build-Depends on the obsolete automake1.11 package. Please check whether this package can be built correctly with the recommended automake version, as provided by the automake package (currently version 1.15). If it can, please build-depend on automake instead, with no automake1.11 alternative. automake (>= 1:1.11) has been available since at least Debian 7 'wheezy' (oldoldstable). If this package has an old build system, it is possible that it will need build system changes for it to be able to autoreconf with a current version of automake. If so, those changes should be forwarded upstream. See `info automake Upgrading` or https://www.gnu.org/software/automake/manual/html_node/Upgrading.html for details. automake 1.15 was released in 2014 and is now widespread, so most upstreams will probably not object to a dependency on versions >= 1.15 at this point. If automake1.11 is removed from Debian, this bug will become serious (release-critical), since the Debian buildd infrastructure would be unable to satisfy this package's build-dependencies. As far as I am aware, there are no immediate plans to remove automake1.11. Thanks, S --- End Message --- --- Begin Message --- Version: 5.9.1-6+rm Dear submitter, as the package lhapdf has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/932052 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message --- -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#925038: marked as done (Updating the lhapdf Uploaders list)
Your message dated Mon, 16 Dec 2019 06:15:46 + with message-id and subject line Bug#932052: Removed package(s) from unstable has caused the Debian Bug report #925038, regarding Updating the lhapdf Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 925038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lhapdf Version: 5.9.1-5 5.9.1-6 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint lifong...@gmail.com has not been working on the lhapdf package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them. signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 5.9.1-6+rm Dear submitter, as the package lhapdf has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/932052 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message --- -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#936840: marked as done (lhapdf: Python2 removal in sid/bullseye)
Your message dated Mon, 16 Dec 2019 06:15:46 + with message-id and subject line Bug#932052: Removed package(s) from unstable has caused the Debian Bug report #936840, regarding lhapdf: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lhapdf Version: 5.9.1-6 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:lhapdf If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 5.9.1-6+rm Dear submitter, as the package lhapdf has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/932052 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message --- -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#897779: marked as done (lhapdf: ftbfs with GCC-8)
Your message dated Mon, 16 Dec 2019 06:15:46 + with message-id and subject line Bug#932052: Removed package(s) from unstable has caused the Debian Bug report #897779, regarding lhapdf: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lhapdf Version: 5.9.1-6 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/lhapdf_5.9.1-6_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-8/porting_to.html [...] CALL AFPOLIN(AS,AF,N,S,AANS,DY) 1 Error: Actual argument contains too few elements for dummy argument 'xa' (3/10) at (1) wrapacfgpg.f:628:19: CALL AFPOLIN(AS,AF,N,S,AANS,DY) 1 Error: Actual argument contains too few elements for dummy argument 'xa' (3/10) at (1) make[2]: *** [Makefile:701: wrapacfgpg.lo] Error 1 make[2]: Leaving directory '/<>/src' make[2]: *** Waiting for unfinished jobs make[2]: Entering directory '/<>/src' /bin/bash ../libtool--mode=compile gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c -o wraplacg.lo wraplacg.f libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wraplacg.f -fPIC -o .libs/wraplacg.o libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wraplacg.f -o wraplacg.o >/dev/null 2>&1 make[2]: Leaving directory '/<>/src' make[2]: Entering directory '/<>/src' /bin/bash ../libtool--mode=compile gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c -o wrapgrvg.lo wrapgrvg.f libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wrapgrvg.f -fPIC -o .libs/wrapgrvg.o libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wrapgrvg.f -o wrapgrvg.o >/dev/null 2>&1 make[2]: Leaving directory '/<>/src' make[2]: Entering directory '/<>/src' /bin/bash ../libtool--mode=compile gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c -o wrapgsg96.lo wrapgsg96.f libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wrapgsg96.f -fPIC -o .libs/wrapgsg96.o libtool: compile: gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form -c wrapgsg96.f -o wrapgsg96.o >/dev/null 2>&1 make[2]: Leaving directory '/<>/src' make[2]: Entering directory '/<>/src' /bin/bash ../libtool--mode=compile gfortran -ffree-form -I. -I. -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -ffree-form
Bug#932052: Removed package(s) from unstable
Version: 5.9.1-6+rm Dear submitter, as the package lhapdf has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/932052 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain) -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#932052: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: lhapdf |5.9.1-6 | source lhapdf-ccwrap-doc |5.9.1-6 | all lhapdf-pdfsets-minimal |5.9.1-6 | all liblhapdf-dev | 5.9.1-6+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x liblhapdf0v5 | 5.9.1-6+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x octave-lhapdf | 5.9.1-6+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x python-lhapdf | 5.9.1-6+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; FTBFS, no progress since May 2018 -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 932...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/932052 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain) -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
ufo-core 0.15.1-2 MIGRATED to testing
FYI: The status of the ufo-core source package in Debian's testing distribution has changed. Previous version: 0.15.1-1 Current version: 0.15.1-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
silx 0.11.0+dfsg-3 MIGRATED to testing
FYI: The status of the silx source package in Debian's testing distribution has changed. Previous version: 0.11.0+dfsg-2 Current version: 0.11.0+dfsg-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
openfoam is marked for autoremoval from testing
openfoam 1906.19+dfsg1-1 is marked for autoremoval from testing on 2019-12-17 It is affected by these RC bugs: 945041: openfoam: severe build time regression -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
sasmodels is marked for autoremoval from testing
sasmodels 1.0.1-1 is marked for autoremoval from testing on 2020-01-21 It (build-)depends on packages with these RC bugs: 946582: pocl: silx: autopkgtest regression: pocl error 946583: pocl: silx: autopkgtest regression: pocl error -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#946802: python3-minieigen: missing Breaks+Replaces: python-minieigen
Package: python3-minieigen Version: 0.50.3+dfsg1-10 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-minieigen_0.50.3+dfsg1-10_amd64.deb ... Unpacking python3-minieigen (0.50.3+dfsg1-10) ... dpkg: error processing archive /var/cache/apt/archives/python3-minieigen_0.50.3+dfsg1-10_amd64.deb (--unpack): trying to overwrite '/usr/share/doc-base/python-minieigen', which is also in package python-minieigen 0.50.3+dfsg1-9 Errors were encountered while processing: /var/cache/apt/archives/python3-minieigen_0.50.3+dfsg1-10_amd64.deb cheers, Andreas python-minieigen=0.50.3+dfsg1-9_python3-minieigen=0.50.3+dfsg1-10.log.gz Description: application/gzip -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
mumps_5.2.1-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 16 Dec 2019 09:23:05 +1100 Source: mumps Architecture: source Version: 5.2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Changes: mumps (5.2.1-2) unstable; urgency=medium . * Team upload. * Standards-Version: 4.4.1 Checksums-Sha1: 95fea6adcf334f33fe0e585b9ab0afde95e7a456 2702 mumps_5.2.1-2.dsc 77f7bfcfeec3d3f53038885db1aeb0c2b07cb5cf 17732 mumps_5.2.1-2.debian.tar.xz Checksums-Sha256: ca544de5fe3e38babb4ea0715c52d93695f415348b758f53be2b2b1713e09a59 2702 mumps_5.2.1-2.dsc 56f79c064b188240823e9dc825ebebaf2a9d11b2b6558fc6e1a53e209deedbd1 17732 mumps_5.2.1-2.debian.tar.xz Files: 243466ccb1d836ca9cd50b33edd217f2 2702 devel optional mumps_5.2.1-2.dsc 1918ac6e92a292fdb72b13bb1f1ab9cb 17732 devel optional mumps_5.2.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl32vzsACgkQVz7x5L1a AforBA/9Gc0tzj+NQA3Xw3M08xNdcqEoBV6jjLbMxF/vcuw5xS3HeorB08IpYvqZ EKf/QVHgcOk0kqa8yEd7bWJKgKGNfs1lkiCQ1h3ow3m1QgQOQyf0ShveAeY8qGeF xiDEIRlLcBLkK9wK1lI1Ymm/AzJRfdyxuE0AlkYhHk+PE+8gTmM7b8hHQSTa4Q// HK/cL1YFQRN+RPve1nVu0ZbiHP+APVhXaAswO12u2XsMRclroKeLd80f7s4UKDWg qVTEJ+hAkOFinsIl7ydAYXvDFeeO5S38iamCJrEX2rq811P2/TCwMMqxjg1Nt6xw ceItXrTu4nsTUVBKf9ztmfJenNOI/rce09TwUB2AVkORKjhftGcUkCzVQV0awM4X ERjtFkO+JUMvfJyPrgpJUT1rVMdsS0Nj8DxSXccQY6ez84vFxDWKpnWYofPjTRqk RwKiCUISZTdo6di81BsxfBeV5BqQIiCNvwv+Hx/oe/iIKZtK/fbA4RejHXtdcZbA /LpyXPjiU/oX7l/zd9jcAFtQ9hT7keZcoRL8/dpddaGOOIB/hyn08uviEXQ8EII6 Qxo+n2bHCUZGMOC0VxbC9CDj4T/RBsscc0yIg1qP7vwayPF4skX+Fc0UsGw2woVz EK4OcHZWJYDZi6BiwQ7kFll8id6Sj+ERS96OA97L1OHR4zgSzrU= =kudx -END PGP SIGNATURE- Thank you for your contribution to Debian. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of mumps_5.2.1-2_source.changes
mumps_5.2.1-2_source.changes uploaded successfully to localhost along with the files: mumps_5.2.1-2.dsc mumps_5.2.1-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Legitim
2.3m ATM card has been awarded to you Email Back For more information Alcaldia La Magdalena Contreras Coordinacion -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#946698: marked as done (libopenblas-dev: openblas.pc is not detected by plkg-config (nor by locate, BTW).)
Your message dated Sun, 15 Dec 2019 21:59:14 +
with message-id
and subject line Bug#946698: fixed in openblas 0.3.7+ds-6
has caused the Debian Bug report #946698,
regarding libopenblas-dev: openblas.pc is not detected by plkg-config (nor by
locate, BTW).
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
946698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenblas-dev
Version: 0.3.7+ds-5
Severity: normal
The installation of libopenblas and libopenblas-dev does not seem to allow the
normal use of openblasin a sn autotools-based source program.
A detailed example is documented in https://trac.sagemath.org/ticket/27870
starting at comment 28 ; a configure script running on a machine having pkg-
config, libopenblas and libopenblas-dev is unable to fing the openblas.pc file
installed in the "normal" locationgiven at installation. See the above ticked
for details.
I also note that the locate command is unable to find this file.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (650, 'testing'), (60, 'unstable'), (50, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libopenblas-dev depends on:
ii libopenblas-pthread-dev 0.3.7+ds-5
ii libopenblas0 0.3.7+ds-5
libopenblas-dev recommends no packages.
libopenblas-dev suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openblas
Source-Version: 0.3.7+ds-6
We believe that the bug you reported is fixed in the latest version of
openblas, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 946...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sébastien Villemot (supplier of updated openblas package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 15 Dec 2019 22:02:19 +0100
Source: openblas
Architecture: source
Version: 0.3.7+ds-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Sébastien Villemot
Closes: 946698
Changes:
openblas (0.3.7+ds-6) unstable; urgency=medium
.
* Restore pkgconfig’s openblas.pc (for 32-bit indexing)
This file is now managed by the alternatives system, since there are
several
variants of it. (Closes: #946698)
By the way, add openblas64.pc (for 64-bit indexing).
* Fix alternatives symlink for openblas64_config.h (64-bit indexing variants)
* Drop empty postrm script for libopenblas-dev
* Make long description of libopenblas0 different from that of
libopenblas64-0.
Similar change for libopenblas-dev vs. libopenblas64-dev.
* Fix the blas{,64}.pc and lapack{,64}.pc alternatives.
For 32-bit indexing, the files pointed to an inexistent $libdir.
The 64-bit indexing variants were pointing to 32-bit libraries.
Checksums-Sha1:
7d31687db947b7de9830e1c46203e0a149524bc9 4821 openblas_0.3.7+ds-6.dsc
3d192119ce4f9bab1089971caaec3d4c8f307bc5 21152
openblas_0.3.7+ds-6.debian.tar.xz
9fef76a8f90502046886078dcfe85a9f9129ca1b 6680
openblas_0.3.7+ds-6_source.buildinfo
Checksums-Sha256:
29d79dbfbc8d619d23e5d7757f9a0bcc581a42defb94ad551df16bad7bd156b9 4821
openblas_0.3.7+ds-6.dsc
91ac5c03e60e42d3009e67436697b3c2fd51c5e56f717ea1579918eb356fa1db 21152
openblas_0.3.7+ds-6.debian.tar.xz
15d26cb4db6c3c7707aeb62b4fb9a7cdd633a4a1a5aab07b027e709b5a5d9a5e 6680
openblas_0.3.7+ds-6_source.buildinfo
Files:
61120fb9610486084251bceaafde0490 4821 devel optional openblas_0.3.7+ds-6.dsc
0b0854b332379eb49937852c9ffa7d6c 21152 devel optional
openblas_0.3.7+ds-6.debian.tar.xz
906dfca951a767505da46468281d3b4d 6680 devel optional
openblas_0.3.7+ds-6_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl32n9MACgkQLOzpNQ7O
openblas_0.3.7+ds-6_source.changes ACCEPTED into unstable
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 15 Dec 2019 22:02:19 +0100
Source: openblas
Architecture: source
Version: 0.3.7+ds-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Sébastien Villemot
Closes: 946698
Changes:
openblas (0.3.7+ds-6) unstable; urgency=medium
.
* Restore pkgconfig’s openblas.pc (for 32-bit indexing)
This file is now managed by the alternatives system, since there are
several
variants of it. (Closes: #946698)
By the way, add openblas64.pc (for 64-bit indexing).
* Fix alternatives symlink for openblas64_config.h (64-bit indexing variants)
* Drop empty postrm script for libopenblas-dev
* Make long description of libopenblas0 different from that of
libopenblas64-0.
Similar change for libopenblas-dev vs. libopenblas64-dev.
* Fix the blas{,64}.pc and lapack{,64}.pc alternatives.
For 32-bit indexing, the files pointed to an inexistent $libdir.
The 64-bit indexing variants were pointing to 32-bit libraries.
Checksums-Sha1:
7d31687db947b7de9830e1c46203e0a149524bc9 4821 openblas_0.3.7+ds-6.dsc
3d192119ce4f9bab1089971caaec3d4c8f307bc5 21152
openblas_0.3.7+ds-6.debian.tar.xz
9fef76a8f90502046886078dcfe85a9f9129ca1b 6680
openblas_0.3.7+ds-6_source.buildinfo
Checksums-Sha256:
29d79dbfbc8d619d23e5d7757f9a0bcc581a42defb94ad551df16bad7bd156b9 4821
openblas_0.3.7+ds-6.dsc
91ac5c03e60e42d3009e67436697b3c2fd51c5e56f717ea1579918eb356fa1db 21152
openblas_0.3.7+ds-6.debian.tar.xz
15d26cb4db6c3c7707aeb62b4fb9a7cdd633a4a1a5aab07b027e709b5a5d9a5e 6680
openblas_0.3.7+ds-6_source.buildinfo
Files:
61120fb9610486084251bceaafde0490 4821 devel optional openblas_0.3.7+ds-6.dsc
0b0854b332379eb49937852c9ffa7d6c 21152 devel optional
openblas_0.3.7+ds-6.debian.tar.xz
906dfca951a767505da46468281d3b4d 6680 devel optional
openblas_0.3.7+ds-6_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl32n9MACgkQLOzpNQ7O
vkrFmA/9Hh9CYmqN63QVTjEN4ojtiQIxR937bWdUCuXH9gDCX99APrbEiRpRSHma
4Qemp89m0f+C1I+32L7m71jmILYhnAgz3Hu2/1tDy9XF/QxFfaN4H/dqs/5kporX
xtBbsgr/o/SBv684ddR+2j3QM7pbTHGCvAUPFQgqlGFvRIEREDK+HDxwkNc/Y9tA
922IB+AyXe7r4/Qj+kK71OcKkSpRxAJbFQxJ5OqSr09xZL/Yvy70mS8IHnMQmQD7
g6Mm84Ldo1ZNqdNLNlmwI16fjyzrNiXsYIjXcnIKUSIyLLcaaLRpX4qL4zKsgmi2
ajXWoRLsR8qMtWW+vvS8gbsmh1dH0qNusHV/5bEZeHOzC1GfVO6Ww+2MhQmLCrPu
ZlfrmsQgJTZ617rr63u6HJLDs26EulXy+MJ93MxDDo9JGjaBVAN4du//0ZqsdAjx
UKmx6jLIfChWpww3NLf0dzRK7NEc1w4UGxJV8q5D4ZQTC1fuCy4eR4kx2Yu22guE
rx4fnZWToZOS/TmWIlAye5mgU9rDafwoIeIt5RA9O/P7b6MjP/cbidenzRlAPu5j
ZhWRKKgROU4v0jbqBzFkaKIwFeQ3W7OPpXQSb+L8/87THxkiYRqnqm5Sp+FJcv30
pFz5guMeU0vmee7+1wZJYQkUCqEgL8Yf4cf0H84bf0eGdzGMa0g=
=VFVU
-END PGP SIGNATURE-
Thank you for your contribution to Debian.
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of openblas_0.3.7+ds-6_source.changes
openblas_0.3.7+ds-6_source.changes uploaded successfully to localhost along with the files: openblas_0.3.7+ds-6.dsc openblas_0.3.7+ds-6.debian.tar.xz openblas_0.3.7+ds-6_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
scalapack_2.1.0-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Dec 2019 17:48:16 +1100 Source: scalapack Architecture: source Version: 2.1.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Changes: scalapack (2.1.0-2) unstable; urgency=medium . * Team upload. * upload new upstream release to unstable Checksums-Sha1: a22c620474baae0b969ab6f3def3223f9f3c3be2 2668 scalapack_2.1.0-2.dsc 3eba883c1d0a412ba114b18b5edeb82e58a6d7c2 13456 scalapack_2.1.0-2.debian.tar.xz Checksums-Sha256: 37f9a7f2ebd0d9c759dea37e790587752c78f482b14d058141276d8482755a51 2668 scalapack_2.1.0-2.dsc 64aef2e7ee87b1b3edfc941eebf6fa782c14fd3e6147c318e011480197fcf1e7 13456 scalapack_2.1.0-2.debian.tar.xz Files: 0d6a4a8221e6a3192f3f45e45b64b7f3 2668 devel optional scalapack_2.1.0-2.dsc 95abb19d74fa8ac6aacb342ef7af9e9f 13456 devel optional scalapack_2.1.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl313KcACgkQVz7x5L1a AfoU4A//fvOICbySptk0gEVhEsJg7uZyHDr+iS7bNRtqIBXO0OJzSvoKiVHme5Fc lGLdQe6U4frBBshdcpryKJK/OzfH8s69suGzVwobFcdu6zBbs9xuXlggjnL8+SBK lUTgvYIDbO4AbZCVBfs8DUg28rAkg13JHmsER4UClPCWxLDanLSBZjqNinl7H7Pk wI4y64Esy7hJOP9pRE5pgbkaAIwSlxYCUd23glzVFgKluGatemCTFjThndJo7xhg dJkviUEtcxhKFjeIzb+9e/himF7Bdrwq3Ba3AT+2JIgliLfFXqtOzh/oD9Vuz+3X 6q+kE0p3/suXcwgE7ENKZwZsTVIlhE/Oz/3KhsijTS7wlXENnntvYShrQPnmLsiG 0bUcCmSx19J0iMPfjRSSlBk/TOnDZao3A4Ij+UQod8eU36CyUnhTV7ndgx+rWmyt H0HaFb3UhfciuEqqEMIZeY6i7F9VppuwxIn5vz+9do6h3AfM8OVg/s/gYLXSJPD+ IrjMFhguAu5pRSkceNE2Tg2AowEx7BVdawp/raRW/cDh1cwhZxsHwnQkqc1MxTeE 6ttL/OWfjMxad/NCKfH2Ds5WYweqC5PEFMpetDeYUOEP9kZE5b2ktbw8eaeLl0zQ 097vZRhDKWg44DNdVeMwE/G6mmkIn3Ra+fi04vkozSbbYrKusV0= =JK+m -END PGP SIGNATURE- Thank you for your contribution to Debian. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of scalapack_2.1.0-2_source.changes
scalapack_2.1.0-2_source.changes uploaded successfully to localhost along with the files: scalapack_2.1.0-2.dsc scalapack_2.1.0-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#946758: python3-paraview: should be built against all supported Python3 versions
Package: python3-paraview
Version: 5.7.0-3
Severity: important
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
The recent upload of paraview release 5.7.0-3 was to fix a Python3 version
related FTBFS:
> paraview (5.7.0-3) unstable; urgency=medium
>
> * Hard-code Build-Dep on python3.8-dev. This wasn't being pulled in
> correctly
> leading to FTBFS.
Instead of depending on a hardcoded Python3 version, the correct fix should be
to build against every supported Python3 version. This way it won't FTBFS on
the next change in the supported Python3 version list.
Please find attached a patch proposal.
Thanks,
_g.
- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAl32GE0ACgkQ7+hsbH/+
z4NNMAgArSZaoxbnMR1SfK12zy/VI84L46qYaUCGFKnGqmz/q4Zdoc+pHvmbzDGX
Ac9G+AVPvfT02+aTHP7F+xOC/nZ1ltN7sgkgGaz8hNVgGbi/8U4ZvvB6JJ5tZxh0
jqfAMAOgkzrnH/xv5twB9I2K7GvHnwbDYYp2mQ2tZWpfsJQctHcK6HZjjbdQWBhN
RF9FoVV2uO5K8M7TFyzZdfgyOknrTtxkS5FdG5RUrGdlErfpTe6SH5GKP5+62GSo
SL4J6H8ApYDCxHyg/OqjvCXwdxyhM9L/cJghp4bmGxvbNNSxkB1Qqzl9RBQKKiYV
xaOiI7/F+BDcYDZfX0+fP6wFPNMOeg==
=UzEf
-END PGP SIGNATURE-
diff -Nru paraview-5.7.0/debian/changelog paraview-5.7.0/debian/changelog
--- paraview-5.7.0/debian/changelog 2019-12-11 10:16:00.0 +0100
+++ paraview-5.7.0/debian/changelog 2019-12-13 19:25:32.0 +0100
@@ -1,3 +1,10 @@
+paraview (5.7.0-4) UNRELEASED; urgency=medium
+
+ * Build for all supported Python3 versions
+ * New patches: python3-exact.patch, python3-exec-versions.patch
+
+ -- Gilles Filippini Fri, 13 Dec 2019 19:25:32 +0100
+
paraview (5.7.0-3) unstable; urgency=medium
* Hard-code Build-Dep on python3.8-dev. This wasn't being pulled in correctly
diff -Nru paraview-5.7.0/debian/control paraview-5.7.0/debian/control
--- paraview-5.7.0/debian/control 2019-12-11 10:16:00.0 +0100
+++ paraview-5.7.0/debian/control 2019-12-13 19:25:32.0 +0100
@@ -27,7 +27,7 @@
libavcodec-dev,
libswscale-dev,
libqt5sql5-sqlite,
- python3.8-dev,
+ python3-all-dev,
dh-python,
libglu1-mesa-dev,
libxt-dev,
diff -Nru paraview-5.7.0/debian/patches/python3-exact.patch
paraview-5.7.0/debian/patches/python3-exact.patch
--- paraview-5.7.0/debian/patches/python3-exact.patch 1970-01-01
01:00:00.0 +0100
+++ paraview-5.7.0/debian/patches/python3-exact.patch 2019-12-13
19:25:32.0 +0100
@@ -0,0 +1,42 @@
+Description: Makes cmake request the exact python3 version referenced
+ by variable DEBIAN_PYTHON_PYTHON. This allows building for several
+ python3 versions.
+Index: paraview-5.7.0/VTK/CMake/vtkModule.cmake
+===
+--- paraview-5.7.0.orig/VTK/CMake/vtkModule.cmake
paraview-5.7.0/VTK/CMake/vtkModule.cmake
+@@ -3643,6 +3643,9 @@ macro (vtk_module_find_package)
+ "The `FORWARD_VERSION_REQ` argument must be one of `MAJOR`, `MINOR`, "
+ "`PATCH`, or `EXACT`.")
+ endif ()
++if (_vtk_find_package_FORWARD_VERSION_REQ STREQUAL "EXACT")
++ set(_vtk_find_module_exact_option EXACT)
++endif ()
+ endif ()
+
+ if (NOT DEFINED _vtk_find_package_VERSION_VAR)
+@@ -3656,7 +3659,7 @@ macro (vtk_module_find_package)
+ endif ()
+
+ find_package("${_vtk_find_package_PACKAGE}"
+-${_vtk_find_package_VERSION}
++${_vtk_find_package_VERSION} ${_vtk_find_module_exact_option}
+ ${_vtk_find_package_config}
+ COMPONENTS ${_vtk_find_package_COMPONENTS}
+ OPTIONAL_COMPONENTS ${_vtk_find_package_OPTIONAL_COMPONENTS})
+Index: paraview-5.7.0/VTK/Utilities/Python/CMakeLists.txt
+===
+--- paraview-5.7.0.orig/VTK/Utilities/Python/CMakeLists.txt
paraview-5.7.0/VTK/Utilities/Python/CMakeLists.txt
+@@ -43,9 +43,9 @@ elseif (VTK_PYTHON_VERSION STREQUAL "3")
+ endif ()
+ vtk_module_find_package(
+ PACKAGE Python3
+-VERSION "${vtk_python_min_version}"
++VERSION "${DEBIAN_PYTHON_VERSION}"
+ COMPONENTS Development
+-FORWARD_VERSION_REQ MINOR)
++FORWARD_VERSION_REQ EXACT)
+ else ()
+ message(FATAL_ERROR
+ "`VTK_PYTHON_VERSION` must either be 2 or 3.")
diff -Nru paraview-5.7.0/debian/patches/python3-exec-versions.patch
paraview-5.7.0/debian/patches/python3-exec-versions.patch
--- paraview-5.7.0/debian/patches/python3-exec-versions.patch 1970-01-01
01:00:00.0 +0100
+++ paraview-5.7.0/debian/patches/python3-exec-versions.patch 2019-12-13
19:25:32.0 +0100
@@
