Construction paquet python3

--089e01176ee3b69d1f050d076556
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

​Bonjour,

Je rencontre actuellement un problème lors de la tentative de rét=
roportage
du paquet python3 sur wheezy :
https://packages.debian.org/jessie/python3

En effet, en utilisant l'outil 'pbuilder', j'ai des erreurs lors d'une
tentative de création du paquet :

<<
# pdebuild

for f in debian/*.in; do
f2=`echo $f | sed "s,PVER,python3.4,g;s/@VER@/3.4/g;s,.in$,,"`;
if [ $f2 != debian/control ] && [ $f2 != debian/source.lintian-overri=
des
]; then
rm -f $f2;
fi;
done
dh_clean
dpkg-source -b python3.4-3.4.2
dpkg-source: info: using source format `1.0'
dpkg-source: info: building python3.4 using existing
python3.4_3.4.2.orig.tar.gz
dpkg-source: info: building python3.4 in
python3.4_3.4.2-1~bpo60+netplus1.diff.gz
dpkg-source: warning: ignoring deletion of file configure, use
--include-removal to override
dpkg-source: info: building python3.4 in
python3.4_3.4.2-1~bpo60+netplus1.dsc
debian/rules build
cpp -E
-DDebian

-Darch_os_linux -Darch_amd64
-o - debian/patches/series.in
| egrep -v '^(#.*|$)' > debian/patches/series
: # build locales needed by the testsuite
echo "pybench run disabled for this build" >
/tmp/buildd/python3.4-3.4.2/build-static/pybench.log
rm -rf locales
BEGIN pystone static
cd /tmp/buildd/python3.4-3.4.2/build-static && ./python
../Lib/test/pystone.py
/bin/bash: /tmp/buildd/python3.4-3.4.2/build-static/pybench.log: No such
file or directory
debian/rules:567: recipe for target 'stamps/stamp-pybench' failed
make: *** [stamps/stamp-pybench] Error 1
make: *** Waiting for unfinished jobs.
/bin/bash: line 0: cd: /tmp/buildd/python3.4-3.4.2/build-static: No such
file or directory
mkdir locales
debian/rules:549: recipe for target 'stamps/stamp-pystone' failed
make: *** [stamps/stamp-pystone] Error 1
if which localedef >/dev/null 2>&1; then
sh debian/locale-gen;
fi

==

(
echo '#! /bin/sh';
echo 'set -x';
echo 'export LOCPATH=/tmp/buildd/python3.4-3.4.2/locales';
echo '/tmp/buildd/python3.4-3.4.2/build-static/python
/tmp/buildd/python3.4-3.4.2/debian/script.py test_results '''make test
TESTOPTS="-j 1 -w -uall -x test_ensurepip test_linuxaudiodev
test_ossaudiodev test_venv"'';
echo 'echo DONE';
) > /tmp/buildd/python3.4-3.4.2/build-debug/run_tests
/bin/bash: line 6: /tmp/buildd/python3.4-3.4.2/build-debug/run_tests: No
such file or directory
debian/rules:487: recipe for target 'stamps/stamp-check' failed
make: *** [stamps/stamp-check] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package

>>

En effet, en essayant de me 'chrooter' au niveau du répertoire de mon
environnement de pbuilder je constate que le répertoire '/tmp/buildd'
existe bien.
Je tiens à préciser qu'avec cet environnement pbuilder je suis d=
éjà parvenu
à créer des paquets (ex: mtr ou mpdecimal).

Avez déjà eu ce genre de message ? Des conseils à me donner =
?
Merci d'avance.

--089e01176ee3b69d1f050d076556
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir="ltr"><div class="gmail_default" style="font-family:arial,he=
lvetica,sans-serif">​Bonjour,<br><br></div><div class="gmail_defa=
ult" style="font-family:arial,helvetica,sans-serif">Je rencontre actuelle=
ment un problème lors de la tentative de rétroportage du paquet p=
ython3 sur wheezy :<br><a href="https://packages.debian.org/jessie/python=
3">https://packages.debian.org/jessie/python3</a><br><br></div><div class=
="gmail_default" style="font-family:arial,helvetica,sans-serif">En effe=
t, en utilisant l&#39;outil &#39;pbuilder&#39;, j&#39;ai des erreurs lors d=
&#39;une tentative de création du paquet :<br><br>&lt;&lt;<br></div><d=
iv class="gmail_default" style="font-family:arial,helvetica,sans-serif"=
># pdebuild<br><br>for f in debian/*.in; do <br>  f2=`echo $f | =
sed &quot;s,PVER,python3.4,g;s/@VER@/3.4/g;s,.in$,,&quot;`; <br>  if=
[ $f2 != debian/control ] &amp;&amp; [ $f2 != debian/source.lintian-ov=
errides ]; then <br>    rm -f $f2; <br>  fi; <br>don=
e<br>dh_clean<br> dpkg-source -b python3.4-3.4.2<br>dpkg-source: info:=
using source format `1.0&#39;<br>dpkg-source: info: building python3.4 usi=
ng existing python3.4_3.4.2.orig.tar.gz<br>dpkg-source: info: building pyth=
on3.4 in python3.4_3.4.2-1~bpo60+netplus1.diff.gz<br>dpkg-source: warning: =
ignoring deletion of file configure, use --include-removal to override<br>d=
pkg-source: info: building python3.4 in python3.4_3.4.2-1~bpo60+netplus1.ds=
c<br> debian/rules build<br>cpp -E <br>  -DDebian <br> Â=
  <br>  -Darch_os_linux -Darch_amd64 <br>  -o - debian/patche=
s/<a href="http://series.in">series.in</a> <br>  | egrep -v &#39;^(=
#.*|$)&#39; &gt; debian/patches/series<br>: # build locales needed by the t=
estsuite<br>echo &quot;pybench run disabled for this build&quot; &gt; /tmp/=
buildd/python3.4-3.4.2/build-static/pybench.log<br>rm -rf locales<br>BEGIN =
pystone static<br>cd /tmp/buildd/python3.4-3.4.2/build-static &amp;&amp; ./=
python ../Lib/test/pystone.py<br>/bin/bash: /tmp/buildd/python3.4-3.4.2/bui=
ld-static/pybench.log: No such file or directory<br>debian/rules:567: recip=
e for target &#39;stamps/stamp-pybench&#39; failed<br>make: *** [stamps/sta=
mp-pybench] Error 1<br>make: *** Waiting for unfinished jobs.<br>/bin/ba=
sh: line 0: cd: /tmp/buildd/python3.4-3.4.2/build-static: No such file or d=
irectory<br>mkdir locales<br>debian/rules:549: recipe for target &#39;stamp=
s/stamp-pystone&#39; failed<br>make: *** [stamps/stamp-pystone] Error 1<br>=
if which localedef &gt;/dev/null 2&gt;&amp;1; then <br>  sh debian/lo=
cale-gen; <br>fi<br><br>=
==
<br>( <br>  echo &#39;#! /bin/sh&#39;; <br>  echo &#39;set -x&#=
39;; <br>  echo &#39;export LOCPATH=/tmp/buildd/python3.4-3.4.2/loc=
ales&#39;; <br>  echo &#39;/tmp/buildd/python3.4-3.4.2/build-static/p=
ython /tmp/buildd/python3.4-3.4.2/debian/script.py test_results &#39;&#39;=
&#39;make test TESTOPTS=&quot;-j 1 -w -uall -x test_ensurepip test_linuxa=
udiodev test_ossaudiodev test_venv&quot;&#39;&#39;; <br>  echo &#39;=
echo DONE&#39;; <br>) &gt; /tmp/buildd/python3.4-3.4.2/build-debug/run_tes=
ts<br>/bin/bash: line 6: /tmp/buildd/python3.4-3.4.2/build-debug/run_tests:=
No such file or directory<br>debian/rules:487: recipe for target &#39;stam=
ps/stamp-check&#39; failed<br>make: *** [stamps/stamp-check] Error 1<br>dpk=
g-buildpackage: error: debian/rules build gave error exit status 2<br>E: Fa=
iled autobuilding of package<br><br></div><div class="gmail_default" s=
tyle="font-family:arial,helvetica,sans-serif">&gt;&gt;<br><br></div><div =
class="gmail_default" style="font-family:arial,helvetica,sans-serif">En=
effet, en essayant de me &#39;chrooter&#39; au niveau du répertoire d=
e mon environnement de pbuilder je constate que le répertoire &#39;/tm=
p/buildd&#39; existe bien.<br></div><div class="gmail_default" style="f=
ont-family:arial,helvetica,sans-serif">Je tiens à préciser qu&#39=
;avec cet environnement pbuilder je suis déjà parvenu à cr=
éer des paquets (ex: mtr ou mpdecimal).<br><br></div><div class="gma=
il_default" style="font-family:arial,helvetica,sans-serif">Avez déj=
à eu ce genre de message ? Des conseils à me donner ?<br></div><d=
iv class="gmail_default" style="font-family:arial,helvetica,sans-serif"=
>Merci d&#39;avance.<br><br></div><div class="gmail_default" style="fon=
t-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default"=
style="font-family:arial,helvetica,sans-serif"><br></div></div>

--089e01176ee3b69d1f050d076556--

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers debian-user-french-REQUEST@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmaster@lists.debian.org
Archive: https://lists.debian.org/BLU437-SMTP63CA3B4172E8A5A62142ABD54A0@phx.gbl

---

• Partager ce contenu :