[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#914558: marked as done (petsc: hardcodes path to sh depending on build host)

Your message dated Thu, 10 Jan 2019 00:14:19 +0100
with message-id <E1ghN3D-0002dT-Eo@grendel>
and subject line Re: petsc: hardcodes path to sh depending on build host
has caused the Debian Bug report #914558,
regarding petsc: hardcodes path to sh depending on build host
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 owner@bugs.debian.org
immediately.)


-- 
914558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914558
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: petsc
Version: 3.9.4+dfsg1-2

Dear maintainer,

Recently your package was rebuild as part of the hdf5 transition. During
the rebuild, the buildds accidentally had a merged usr setup [1].
Although this setup has been reverted, it exposed the fact that your
package embeds the path to sh from the build host, as the autopkgtest of
your started failing [2] with the error copied below. There was a large
thread on debian-devel@l.d.o about merged usr setup due to the buildd
issue. I think your build should not rely on the location of sh in the
$PATH of the build host.

I have requested binNMUs of your package on #debian-release.

Paul

[1] https://wiki.debian.org/UsrMerge
[2] https://ci.debian.net/packages/p/petsc/unstable/amd64/
[3]
https://lists.debian.org/msgid-search/20181120211617.gxnuwxpx2hy445ps@angband.pl

https://ci.debian.net/data/autopkgtest/testing/amd64/p/petsc/1370827/log.gz

autopkgtest [07:28:26]: test test-petsc: [-----------------------
Running test examples to verify correct installation
Using PETSC_DIR=/usr/lib/petsc
make: /usr/bin/sh: Command not found
make: [/usr/lib/petsc/lib/petsc/conf/rules:158: clean-legacy] Error 127
(ignored)
make: /usr/bin/sh: Command not found
make: [/usr/lib/petsc/lib/petsc/conf/rules:159: clean-legacy] Error 127
(ignored)
run SNES testex19
make: /usr/bin/sh: Command not found
make: [/usr/lib/petsc/lib/petsc/conf/rules:402: ex19.PETSc] Error 127
(ignored)
make: /usr/bin/sh: Command not found
make: [/usr/lib/petsc/lib/petsc/conf/rules:403: ex19.PETSc] Error 127
(ignored)
make: /usr/bin/sh: Command not found
make: [makefile:266: testex19] Error 127 (ignored)
test HYPRE
make: /usr/bin/sh: Command not found
make: [makefile:287: runex19_hypre] Error 127 (ignored)
test MUMPS
make: /usr/bin/sh: Command not found
make: [makefile:297: runex19_fieldsplit_mumps] Error 127 (ignored)
run testex5f
make: /usr/bin/sh: Command not found
make: [/usr/lib/petsc/lib/petsc/conf/rules:453: ex5f.PETSc] Error 127
(ignored)
make: /usr/bin/sh: Command not found
make: [/usr/lib/petsc/lib/petsc/conf/rules:454: ex5f.PETSc] Error 127
(ignored)
make: /usr/bin/sh: Command not found
make: *** [makefile:250: testex5f] Error 127
make: /usr/bin/sh: Command not found
make: [/usr/lib/petsc/lib/petsc/conf/rules:158: clean-legacy] Error 127
(ignored)
make: /usr/bin/sh: Command not found
make: [/usr/lib/petsc/lib/petsc/conf/rules:159: clean-legacy] Error 127
(ignored)
Completed test examples
autopkgtest [07:28:26]: test test-petsc: -----------------------]

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
buildds are fixed, petsc is rebuilt, no point keeping this bug open.

--- End Message ---
Reply to: