iv3d-users

Text archives Help


[IV3D-USERS] Re: Re: Re: Packaging imagevis3d in debian


Chronological Thread 
  • From: tom fogal <tfogal@sci.utah.edu>
  • To: iv3d-users@sci.utah.edu
  • Subject: [IV3D-USERS] Re: Re: Re: Packaging imagevis3d in debian
  • Date: Fri, 09 Dec 2011 13:27:51 -0700
On 12/09/2011 01:18 AM, Mathieu Malaterre wrote:
On Fri, Dec 9, 2011 at 12:46 AM, tom fogal<tfogal@sci.utah.edu>  wrote:
Mathieu Malaterre<mathieu.malaterre@gmail.com>  writes:
   I have started packaging imagevis3d for debian, see
http://bugs.debian.org/651470.

Maybe you'd like to take
ownership of the bug (or at least close it as a duplicate?)?

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530666

Sorry I did not realize that. debian bug tracker system did show me
this issue this morning. Both issue have been merged.

great, thanks!

Also note there is a 'notdebian' directory in the root 'imagevis3d'
repository (the debian policy guides specifically discourage putting a
'debian' directory in the package's repository, but when the maintainer
== the developer that adds logistical pains for no gain... so I just
called it 'notdebian' ;).

I saw that, I remove this dir as well as the 3rdParty ones in the
get-orig-source script:
http://anonscm.debian.org/viewvc/debian-med/trunk/packages/imagevis3d/trunk/debian/get-orig-source?view=markup

You can just remove 'StandaloneTuvok' entirely, it's just a demo program, BTW. Ditto with Tuvok/test, fwiw.

As a side note, I also thought at first this adds logistical pains.
Until I realize upstream source and debian package live at different
pace. The debian package lives as compiler, linker, and 3rd party libs
evolve. Therefore the debian team needs quick access to the debian/*
files to change them, and upload a new package. Some are really low
level and do not require upstream developer for doing this.

Sure, of course. It just didn't/doesn't matter to us if a packaging change affected the main repository.

I certainly see the logic when packager != maintainer.

where can I find
the source stable release ?

Yes, sorry, we haven't been making these unfortunately.  I can start
doing so with the next release, which will be 2.1.0.

that would be terrific

okay I'll start them soon, then.

We do build nightly tarballs.  I don't want the URI they are at to get
crawled/archived via the web, but I will happily point you or anyone
that asks at them via a private mail.

Hum...that defeat the part of the purpose of my question. Here is
typically the webpage I open every time I need to check the status of
my packages:

http://qa.debian.org/developer.php?login=Mathieu%20Malaterre

See the column on the far right, it indicates with a red color if a
package has had a new release from upstream. Anyway the debian/* file
are hosted on debian server so they might be 'crawled' via the web.

Ahh. This wouldn't be a good source, then; it's just a nightly build that overwrites the previous tarball and calls itself 'ImageVis3D-${next_version}.tar.gz', so it would be hard to tell when something changes anyway. I'd guess you want to point the debian/watch uri at our download page:

   http://www.sci.utah.edu/download/imagevis3d.html

I'll probably want to steal your
versions of the debian files for notdebian/ at that point.

You are free to do that. However keep in mind debian package and
upstream source do not evolve at the same pace.

Sure, not a problem.

Please let us know if there's anything else we can do to help out!

And for anyone else listening: we'd welcome contributed RPM spec or other packaging files, as well...

-tom

Archive powered by MHonArc 2.6.16.

Top of page