[Debian-med-packaging] New CamiTK 4.1.2 release

[Andreas Tille]

On Wed, Jul 25, 2018 at 04:44:07PM +0200, Emmanuel Promayon wrote:
> > 
> > to make sure the policy package on your system is always taken from
> > unstable (and thus per definition up to date).
> 
> Thanks for the trick. I suppose also that lintian would have warned about
> using an old version as well (and maybe "cme check dpkg-control" would have
> says something as well).

Yes, if you are using lintian and cme (with its dependencies) from unstable.
 
> > Very sensible.  I'd applause this. ;-)
> If I manage to do that, I will let you know! FYI, we are using gitlab ci on
> the upstream gitlab server.
> 
> That leads to my new question about the good usage of the salsa git. Imagine
> that we need to update some file in order to build a package from the
> current upstream (unreleased) version (e.g., debian/control).
> 
> In this case do you think it is ok to "pollute" salsa with an extra
> "upstream-ci/master" branch?

I personally have no problem with this if it helps your workflow.
 
> When a new version would be released, "upstream-ci/master" should contain
> everything required, and it can be merged directly to "master" (and then
> started afresh).

Since I can not see any harm done by this approach just go for this.

Kind regards

    Andreas.
 

-- 
http://fam-tille.de