Dear Neil,

> > Could you provide this lava-dev .deb somewhere publically?

Thanks for this. So:

$ wget

   $ lintian lava-dev_2018.2+7234.16764207-1+_all.deb
  E: lava-dev: python-script-but-no-python-dep usr/share/lava-
 server/ #!/usr/bin/python


$ dpkg -I lava-dev_2018.2+7234.16764207-1+_all.deb
 Depends: build-essential, ca-certificates, devscripts, dpkg-dev,
 debootstrap (>= 1.0.86), debhelper (>= 9.20160709), fakeroot, git,
 libdistro-info-perl, node-uglify, libjs-excanvas, libjs-jquery-
 cookie, libjs-jquery, libjs-jquery-watermark, libjs-jquery-flot
 (>= 0.8.2), libjs-jquery-ui, pep8 | python-pep8, python-guestfs,
 python-nose, python-netifaces, python3-sphinx (>= 1.4), python-
 setuptools, python-pexpect (>= 4.2), python3-sphinx-bootstrap-
 theme, python-requests, python-zmq, python-yaml, python-voluptuous
 (>= 0.8.8), docbook-xsl, xsltproc, python-mock

> > As an aside: I understand that git-buildpackage is not for everyone,
> > but here is a great example of where common, shared tools would really
> > have a benefit and would save this round trip to fixing this issue.
> This isn't about git-ignore anything, this is about building upstream
> packages with (sometimes) untested and uncommitted upstream changes to
> be able to do the testing prior to and during code review. Making
> debian/patches for that is a complete nonsense. 

Alas, I think at least one of us is confused or misinterpreting the
other here..  Or, perhaps, you are not aware that git- buildpackage
is perfectly capable of doing such snapshots, indeed without
debian/patches. Perhaps you last used an old version? This is
almost certainly a conversation to be had elsewhere, mind you!


Best wishes,

     : :'  :     Chris Lamb
     `. `'` /

Reply via email to