Hi Corentin, please note that I assume you are subscribed to the list and do not CC you any more since this is the list policy.
On Fri, Aug 22, 2014 at 12:56:10PM +0200, Corentin Desfarges wrote: > >> cmake 2.8.12.1. > > > >Well, current cmake in unstable (and testing) is 2.8.12.2-1. You should > >be able to build the package in a pbuilder chroot which should > guarantee that > >we are using the very same tools. (If you have no idea how to set up this > >feel free to ask for more details. > > I've read the different documentations that you gave me, but I'm not > totally sure to know how to do. Here is the process that I try to > apply, can you tell me what do you think about it ? > > To build vxl without modify the package : > On a Debian system (Jessie), I my work directory, I have these files > (found on https://packages.debian.org/experimental/libvxl1-dev) : > vxl_1.17.0-8.1.dsc > vxl_1.17.0.orig.tar.gz > vxl_1.17.0-8.1.debian.tar.xz > > I run these commands : > pbuilder --create > pbuilder --build vxl_1.17.0-8.1.dsc Ahhh, the last command is new to me - may be I learned something that might help me in the future. I think the simplest workflow would be: apt-get source vxl (well, you just have the sources downloaded so you can safe bandwidth if you dont and just do dpkg-source -x *.dsc to unpack the source). This gives you the files above and an unpackaged source tree. Usually you cd <unpackaged_sourc_dir> pdebuild > My other question is what's the correct way to modify a package and > repack it ? Quite at the top of our team policy are links to packaging beginners documentation (new maintainers guide). In principle the modifications on the packaging are done in the debian/ dir. If you need to change something in the upstream code you are using `quilt` like: quilt <new_changes>.patch quilt edit source/file/to/change quilt refresh > Where a the sources to download ? You currently have the latest upstream source since 1.17.0 ist the last version. > On sourgeforge ? It depends - in the vxl case yes. In debian/watch file you can see where the sources are obtained from and the command `uscan` is actually reading debian/watch and performs the download. However, currently there are changes in SVN available which I wanted you to check: svn checkout svn+ssh://svn.debian.org/svn/debian-med/trunk/packages/vxl I have commited some changes to trunk to fix the issue with minified JavaScript code without the original source which is considered as non-free by Debian. Since this throws a lintian error since some time we can not upload the package source as is any more. So my solution was to strip the files from the upstream source and by doing so change the source tarball. This change will be reflected by appending a '+dfsg' suffix to the version which you can see in the debian/changelog file in trunk/. The way how I changed the upstream tarball is also quite new (since some monthes) and not yet known even to all Debian developers - so you are starting with some "hot stuff". ;-) I simply added Files-Excluded: contrib/brl/bseg/boxm2/ocl/exe/auxiliary to debian/copyright which deletes the directory with the files in questions which should be no problem since it is not used anyway. (Attention: Due to my weak skills with cmake it might be that exactly this deletion might have caused the trouble I was running into. I have no idea whether this can be - the error message gives no clue about this.) Now since we have organised the removal of the files we would need to fetch the source from scratch (please do not before you kept on reading the next two paragraphs!). Usually you are using uscan to fetch an upstream source which would work like this: uscan --verbose --force-download However, since we are changing the upstream tarball anyway and will loose the chance to compare the MD5sum of the download we could do better by using a better compression which is quite some deal with vxl due to its size. Since we now have a non-default download method it is good practice to provide a get-orig-source target in debian/rules (please have a look there at the bottom. This would enable you to debian/rules get-orig-source # please read below! This would be the generic way to fetch the "new" upstream source. However, to safe you a 40MB download which you in principle have on your disk you can also call the tool which is called by uscan in turn manually to get the result straight. Make sure you are just in the unpackaged source dir featuring a copy of the debian/ dir you found in trunk/ and than you can simply do mk-origtargz --repack --compress xz vxl_1.17.0.orig.tar.gz This should result in a file vxl_1.17.0+dfsg.orig.tar.xz in the directory below which will be your new upstream source tarball. Mk-origtargz should tell you about the number of deleted files and the dir contrib/brl/bseg/boxm2/ocl/exe/auxiliary should have vanished. Now you can delete your current working directory and unpack tar xaf vxl_1.17.0+dfsg.orig.tar.xz and copy trunk/debian into the unpackaged dir. Cd to this dir and say pdebuild This should have the same result as I posted here on the list. If so this build error needs to be tracked down. Just report here what might happen on your side. I hope these hints might get you start working. > Thank you for your attention You are welcome Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140822114834.ga24...@an3as.eu
