Re: MIA - Software for medical image alaysis
Hello Andreas, On 11/22/12 15:15, Andreas Tille wrote: Hi Gert, On Thu, Nov 22, 2012 at 02:47:54PM +0100, Gert Wollny wrote: thanks for the pointers. I made myself an Alioth account (gert-guest) and will star to move the packages from ubuntus bazaar to the git structure. I'm at the point of uploading the first package (vistaio), to git.debian.org/git/debian-med/vistaio.git I've seen that I should add the packages to the tasks file, Since this library is only IO, should it still go into imaging? Where would the doc package go? BTW: There are packages libvista2/libvsta2-dev package listed. Maybe it should be removed. Best Gert -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50b6102b.1010...@gmail.com
Re: MIA - Software for medical image alaysis
Hi Gert, On Wed, Nov 28, 2012 at 02:22:51PM +0100, Gert Wollny wrote: > I'm at the point of uploading the first package (vistaio), to > > git.debian.org/git/debian-med/vistaio.git That's great - but please use git.debian.org/git/debian-med/libvistaio.git We will have another package vista (Hospital information system totally unrelated to libvista (and this other non-free system with the same name.) I do not think that we should make the name space that similar and prefixing a library package with 'lib' is a good idea in general. > I've seen that I should add the packages to the tasks file, I'd volunteer to do this. > Since this library is only IO, should it still go into imaging? H, I admit that I do not know much about it - so if you think that it is just a precondition for those really imaging related libraries it might not be worth mentioning it here. I'll have a look at the package description - just make sure it is verbose enough to let even people like me understand the use of the package. > Where would the doc package go? Currently we do not maintain doc packages via metapackages (once we had med-doc but it was totally unmaintained - so we decided to drop it.) > BTW: > There are packages libvista2/libvsta2-dev package listed. Maybe it > should be removed. I just removed libvista2 because the imaging task should list applications rather than libraries. If you would confirm that libvista2-dev is dead / unmaintained / not worth packaging I'll remove it as well. At the time when I included this entry it made some sense and I did not followed the development any more. Kind regards Andreas. PS: You could do me a favour if you would not CC me in your mails because it is the list policy to just post to the list. Hope this does not cause much trouble with your mail user agent. -- 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: http://lists.debian.org/20121128150947.ga8...@an3as.eu
Re: MIA - Software for medical image alaysis
On 11/28/12 16:09, Andreas Tille wrote: On Wed, Nov 28, 2012 at 02:22:51PM +0100, Gert Wollny wrote: I'm at the point of uploading the first package (vistaio), to git.debian.org/git/debian-med/vistaio.git That's great - but please use git.debian.org/git/debian-med/libvistaio.git Directory name changed, Should I also change the source package name from vistaio to libvistaio? The other proposed directory names (+.git) would be libmialm, mia, mialmpick, miaviewitgui, pymia I've seen that I should add the packages to the tasks file, I'd volunteer to do this. Thanks, Since this library is only IO, should it still go into imaging? H, I admit that I do not know much about it - so if you think that it is just a precondition for those really imaging related libraries it might not be worth mentioning it here. I'll have a look at the package description - just make sure it is verbose enough to let even people like me understand the use of the package. It is really only IO, Tell me if the description needs clarification, and of course anything else that is needed to make the package Debian worthy. BTW: There are packages libvista2/libvsta2-dev package listed. Maybe it should be removed. I just removed libvista2 because the imaging task should list applications rather than libraries. If you would confirm that libvista2-dev is dead / unmaintained / not worth packaging I'll remove it as well. At the time when I included this entry it made some sense and I did not followed the development any more. I think it's dead. I do not maintain it anymore, and most if not all image processing facilities are included in libvia (AFAIK). Vistaio is effectively libvista stripped down to the IO functions (plus some new IO data types). PS: You could do me a favour if you would not CC me in your mails because it is the list policy to just post to the list. Hope this does not cause much trouble with your mail user agent. That's fine, I just did it this way because the first responses also were to me with the list in CC. Next week I will be out of office, but after that will start to add the other packages. Many thanks, Gert -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50b631cf.4020...@gmail.com
Re: MIA - Software for medical image alaysis
Hi Gert, On Wed, Nov 28, 2012 at 04:46:23PM +0100, Gert Wollny wrote: > > git.debian.org/git/debian-med/libvistaio.git > > > Directory name changed, Should I also change the source package name > from vistaio to libvistaio? Yes - we have some kind of undocumented good practice to do so (probably it would be sane to push this into team policy). > The other proposed directory names (+.git) would be > > libmialm, mia, mialmpick, miaviewitgui, pymia Sounds reasonable to me. > It is really only IO, Tell me if the description needs > clarification, and of course anything else that is needed to make > the package Debian worthy. I'll have a look later today or tomorrow. I (or some other team member) need to have a close look when sponsering the package anyway. > I think it's dead. I do not maintain it anymore, and most if not all > image processing facilities are included in libvia (AFAIK). Vistaio > is effectively libvista stripped down to the IO functions (plus some > new IO data types). OK, thanks for the clarification. > >PS: You could do me a favour if you would not CC me in your mails > > because it is the list policy to just post to the list. Hope > > this does not cause much trouble with your mail user agent. > That's fine, I just did it this way because the first responses also > were to me with the list in CC. Yep, that's what we are sometimes doing for newcomers when we are not 100% sure whether he is subscribed. > Next week I will be out of office, but after that will start to add > the other packages. Thanks for your effort 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: http://lists.debian.org/20121128181509.ga13...@an3as.eu
Re: MIA - Software for medical image alaysis
Hello Andreas, On 11/28/12 19:15, Andreas Tille wrote: Directory name changed, Should I also change the source package name from vistaio to libvistaio? Yes - we have some kind of undocumented good practice to do so (probably it would be sane to push this into team policy). Done and changes pushed; builds on sid lintian error free, and in the pbuilder chroot. Best, Gert -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50b65b93.3020...@gmail.com
Re: MIA - Software for medical image alaysis
Hi Gert, On Wed, Nov 28, 2012 at 07:44:35PM +0100, Gert Wollny wrote: > >Yes - we have some kind of undocumented good practice to do so (probably > >it would be sane to push this into team policy). > > Done and changes pushed; builds on sid lintian error free, and in > the pbuilder chroot. Cool. Unfortunately it does not (yet) build for me: ~/tmp $ debcheckout --user tille git://git.debian.org/debian-med/libvistaio.git --git-track '*' declared git repository at git+ssh://ti...@git.debian.org/git/debian-med/libvistaio.git git clone git+ssh://ti...@git.debian.org/git/debian-med/libvistaio.git libvistaio ... Cloning into 'libvistaio'... remote: Counting objects: 192, done. remote: Compressing objects: 100% (145/145), done. remote: Total 192 (delta 58), reused 143 (delta 35) Receiving objects: 100% (192/192), 184.98 KiB | 191 KiB/s, done. Resolving deltas: 100% (58/58), done. Branch pristine-tar set up to track remote branch pristine-tar from origin. Branch upstream set up to track remote branch upstream from origin. Use of uninitialized value $srcpkg in substitution (s///) at /usr/bin/debcheckout line 822. ~/tmp $ cd libvistaio ~/tmp/libvistaio(master) $ git-buildpackage dh clean dh_testdir dh_auto_clean dh_clean gbp:info: Orig tarball 'libvistaio_1.2.14.orig.tar.xz' not found at '../tarballs/' fatal: Path 'libvistaio_1.2.14.orig.tar.xz.delta' does not exist in 'refs/heads/pristine-tar' pristine-tar: git show refs/heads/pristine-tar:libvistaio_1.2.14.orig.tar.xz.delta failed gbp:error: Couldn't checkout "libvistaio_1.2.14.orig.tar.xz": /usr/bin/pristine-tar returned 128 Either the pristine-tar branch seems to be incorrect or it is me fighting hard with Git (I "feel" only 50% success when doing such things - so it seems to be a probably assumption that again something is wrong on my side :-(). Kind regards 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: http://lists.debian.org/20121128223028.gd13...@an3as.eu
Re: MIA - Software for medical image alaysis
Hello Andreas, > Cool. Unfortunately it does not (yet) build for me: > > ~/tmp $ debcheckout --user tille > git://git.debian.org/debian-med/libvistaio.git --git-track '*' > declared git repository at > git+ssh://ti...@git.debian.org/git/debian-med/libvistaio.git > git clone git+ssh://ti...@git.debian.org/git/debian-med/libvistaio.git > libvistaio ... > Cloning into 'libvistaio'... > remote: Counting objects: 192, done. > remote: Compressing objects: 100% (145/145), done. > remote: Total 192 (delta 58), reused 143 (delta 35) > Receiving objects: 100% (192/192), 184.98 KiB | 191 KiB/s, done. > Resolving deltas: 100% (58/58), done. > Branch pristine-tar set up to track remote branch pristine-tar from origin. > Branch upstream set up to track remote branch upstream from origin. > Use of uninitialized value $srcpkg in substitution (s///) at > /usr/bin/debcheckout line 822. > > ~/tmp $ cd libvistaio > ~/tmp/libvistaio(master) $ git-buildpackage > dh clean >dh_testdir >dh_auto_clean >dh_clean > gbp:info: Orig tarball 'libvistaio_1.2.14.orig.tar.xz' not found at > '../tarballs/' > fatal: Path 'libvistaio_1.2.14.orig.tar.xz.delta' does not exist in > 'refs/heads/pristine-tar' > pristine-tar: git show > refs/heads/pristine-tar:libvistaio_1.2.14.orig.tar.xz.delta failed > gbp:error: Couldn't checkout "libvistaio_1.2.14.orig.tar.xz": > /usr/bin/pristine-tar returned 128 I think if you don't have the tarball, you need to run git-buildpackage --git-pristine-tar at least I did it once, when it complained about the missing tarball. (Although I use git for quite some time now, the Debian packaging additions are also new to me). There is another problem though, I forgot to tag the last upload. You can work around this by doing git tag -d upstream/1.2.14-1 git tag upstream/1.2.14-1 this will delete the tag that I set earlier (*) and then set the tag to the current git head. *) Actually, the tagged version should also work, just not with multiarch. Which reminds me that this requires to set a minimum cmake version in the dependencies. I'll fix this and the tag first thing in the morning tomorrow. Best Gert -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1354144777.10630.19.camel@middleearth
Re: MIA - Software for medical image alaysis
Hi, there seems to be some problem with creating the source tarball from libvistaio. Any hint? On Thu, Nov 29, 2012 at 12:19:37AM +0100, Gert Wollny wrote: > Hello Andreas, > > > > Cool. Unfortunately it does not (yet) build for me: > > > > ~/tmp $ debcheckout --user tille > > git://git.debian.org/debian-med/libvistaio.git --git-track '*' > > declared git repository at > > git+ssh://ti...@git.debian.org/git/debian-med/libvistaio.git > > git clone git+ssh://ti...@git.debian.org/git/debian-med/libvistaio.git > > libvistaio ... > > Cloning into 'libvistaio'... > > remote: Counting objects: 192, done. > > remote: Compressing objects: 100% (145/145), done. > > remote: Total 192 (delta 58), reused 143 (delta 35) > > Receiving objects: 100% (192/192), 184.98 KiB | 191 KiB/s, done. > > Resolving deltas: 100% (58/58), done. > > Branch pristine-tar set up to track remote branch pristine-tar from origin. > > Branch upstream set up to track remote branch upstream from origin. > > Use of uninitialized value $srcpkg in substitution (s///) at > > /usr/bin/debcheckout line 822. > > > > ~/tmp $ cd libvistaio > > ~/tmp/libvistaio(master) $ git-buildpackage > > dh clean > >dh_testdir > >dh_auto_clean > >dh_clean > > gbp:info: Orig tarball 'libvistaio_1.2.14.orig.tar.xz' not found at > > '../tarballs/' > > fatal: Path 'libvistaio_1.2.14.orig.tar.xz.delta' does not exist in > > 'refs/heads/pristine-tar' > > pristine-tar: git show > > refs/heads/pristine-tar:libvistaio_1.2.14.orig.tar.xz.delta failed > > gbp:error: Couldn't checkout "libvistaio_1.2.14.orig.tar.xz": > > /usr/bin/pristine-tar returned 128 > > I think if you don't have the tarball, you need to run > > git-buildpackage --git-pristine-tar > > at least I did it once, when it complained about the missing tarball. As far as I know (and see from the prefectly identical output) git-buildpackage is doing this automatically in case it can not find the source tarball at the expected location - at least when adding this option the output remains identically. > There is another problem though, I forgot to tag the last upload. You > can work around this by doing > > git tag -d upstream/1.2.14-1 > git tag upstream/1.2.14-1 > > this will delete the tag that I set earlier (*) and then set the tag to > the current git head. > > *) Actually, the tagged version should also work, just not with > multiarch. Which reminds me that this requires to set a minimum cmake > version in the dependencies. I'll fix this and the tag first thing in > the morning tomorrow. I do not think that there is a need to tag upstream/- If you are properly using pristine-tar as written in our team policy[1] git import-orig --pristine-tar /path/to/package_version.orig.tar.gz the tagging of upstream versions is done automatically (and is lacking the '-' part). Once you are done with the Debian packaging the tag is rather debian/- However, there is no point in doing this tagging before we upload the read package to the Debian mirror (in case of an initial package upload I do even delay the tagging until the package was acceted by ftpmaster.) Kind regards Andreas. [1] http://debian-med.alioth.debian.org/docs/policy.html#git-tips -- 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: http://lists.debian.org/20121129073939.ga4...@an3as.eu
