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

Re: Fwd: New bali-phy version

Hi Andreas,

On 05/04/2018 09:14 AM, Andreas Tille wrote:

Hi Benjamin,

I've done

     uscan --verbose --force-download
     gbp import-orig --pristine-tar bali-phy_3.1+dfsg.orig.tar.xz

since the pristine-tar branch was not populated.  Either you forgot the
import-orig step or you did not pushed.
1. Hmm... yes I think I only pushed master.  My workflow notes now look like this: 

% uscan --verbose --force-download
% gbp import-orig --pristine-tar ../bali-phy_<version>+dfsg.orig.tar.xz
% gbp dch
<edit debian/changelog to get correct version>
% git push origin --all
% debuild -S
% cd ..
% sudo pdebuild --update
% sudo pdebuild --build bali-phy_version.dsc

Does this look right?


   So there might be some
difference to your local Git repository and there is a slight chance
that this is causing the following build error (even if I doubt this
reason for the issue):

...
25/28 trees-distances --help                  OK       0.01 s
26/28 alignment-thin --help                   OK       0.01 s
27/28 alignments-diff --help                  OK       0.01 s
Traceback (most recent call last):
   File "/usr/bin/meson", line 26, in <module>
     sys.exit(main())
   File "/usr/bin/meson", line 23, in main
     return mesonmain.run(sys.argv[1:], launcher)
   File "/usr/share/meson/mesonbuild/mesonmain.py", line 278, in run
     return mtest.run(remaining_args)
   File "/usr/share/meson/mesonbuild/mtest.py", line 712, in run
     return th.doit()
   File "/usr/share/meson/mesonbuild/mtest.py", line 463, in doit
     self.run_tests(tests)
   File "/usr/share/meson/mesonbuild/mtest.py", line 621, in run_tests
     self.drain_futures(futures)
   File "/usr/share/meson/mesonbuild/mtest.py", line 637, in drain_futures
     self.process_test_result(result.result())
   File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result
     return self.__get_result()
   File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result
     raise self._exception
   File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
     result = self.fn(*self.args, **self.kwargs)
   File "/usr/share/meson/mesonbuild/mtest.py", line 232, in run
     return self._run_cmd(wrap + cmd + self.test.cmd_args + self.options.test_args)
   File "/usr/share/meson/mesonbuild/mtest.py", line 276, in _run_cmd
     preexec_fn=preexec_fn if not is_windows() else None)
   File "/usr/lib/python3.6/subprocess.py", line 709, in __init__
     restore_signals, start_new_session)
   File "/usr/lib/python3.6/subprocess.py", line 1344, in _execute_child
     raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/build/bali-phy-3.1+dfsg/tests/run-tests.py': '/build/bali-phy-3.1+dfsg/tests/run-tests.py'
FAILED: meson-test
/usr/bin/python3 -u /usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1
make: *** [debian/rules:12: build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
...

Can you please get a fresh clone and check the potential diff?
2. This is strange.  I can reproduce the error, but I don't understand it.  The file really should be there.  Also, this does not happen if I just use debuild instead of using pbuilder.
Um, pbuilder seems quite good at cleaning up after itself.  Is it possible to log in with the build directory untouch and figure out where the errors are coming from?  I haven't managed to figure this out yet... 


PS: The next days I'm not as active as usual - please excuse any delays
     from my side.

No worries, thanks for any help!  It still seems pretty quick.

-BenRI
Reply to: