[Debichem-devel] libodsstream packaging (Was: Bug#879556: ITP: beads -- 2-DE electrophoresis gel image spot detection)

[Andreas Tille]

Hi Olivier,

On Fri, Nov 24, 2017 at 03:31:00PM +0100, Olivier Langella wrote:
> > OK, I've added a watch file but I'm a bit astonished that you added
> > version 0.4.11 in pristine-tar but the link above points to version
> > 0.4.10-1.  You should probably update the download area.
> 
> Yes you're right, I've made some changes and made the git repository with
> the very latest version 0.4.11 but didn't published it yet on :
> https://sourcesup.renater.fr/frs/download.php/latestfile/963/libodsstream-0.4.11.tar.gz
> 
> This is updated now, you may will notice that the package file name is
> slightly different:
> this is because for the 0.4.10 (libodsstream_0.4.10-1.tar.gz) , I've
> uploaded the tar gz file generated by my own dpkg-build... I think it is
> better to make a proper targz and separate it from dpkg, so I will now
> upload "real" targz files.

Yes, please.  The '-1' revision is simply wrong for an upstream tarball.
It does not conflict with the Debian version - so if upstream would
choose a versioning system containing '-' signs it is fine but upstream
should not try to mimik the Debian revision.  The watch file keeps on
reporting 0.4.10-1 - it seems not really be fixed at the download
location.
 
> > dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2
> > debian/rules:9: recipe for target 'build' failed
> > make: *** [build] Error 2
> > dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
> > 
> > Hope this helps for a first shot.
> 
> I see that there is already a lot of work.
> Thanks a lot, I'm still struggling to get a correct pbuilder environment to
> be able to compile it with sid (I'm working in stretch).

I'd recommend cowbuilder (which is a bit faster than pbuilder since it
is using copy-on-write).  You can easily do it on stretch.  May be the
Debian wiki helps:
   https://wiki.debian.org/cowbuilder

> If I can solve it, I will push some fix.

Just let us know here if you keep on having trouble.

> > BTW, you might like to drop the Qt4 package since Qt4 will be droped
> > from Debian in this release cycle (if I'm not missleaded).
> 
> Yes, this is planned. I've just finished the Qt5 port of my softwares, and I
> have also a working version of beads in Qt5, so it is possible to drop it...
> I had the hope that perhaps some people could be interested in libodsstream
> : it can read and write ODS files using a kind of "SAX" approach. As many
> people still use Qt4, I thought it might be usefull.

Feel free to keep Qt4 in your upstream source - but I think we should
leave it out in the Debian packaging.

Kind regards

      Andreas.

-- 
http://fam-tille.de