Re: Finishing ncbi-vdb and sra-sdk
- To: "Aaron M. Ucko" <ucko@debian.org>
- Cc: debian-med@lists.debian.org
- Subject: Re: Finishing ncbi-vdb and sra-sdk
- From: Andreas Tille <tille@debian.org>
- Date: Wed, 28 Sep 2022 20:27:36 +0200
- Message-id: <[🔎] YzSSGBUb8ulbR8sP@an3as.eu>
- In-reply-to: <udlsfljmap8.fsf@mit.edu>
- References: <udl4jz2mn6w.fsf@mit.edu> <YuGgMpx1b0Djuqth@an3as.eu> <YuJXaLc5yy+7PN/M@an3as.eu> <udlh731s0rl.fsf@mit.edu> <YuO3+D+qyXCUGeCU@an3as.eu> <udl35e74dv1.fsf@mit.edu> <YvDzVEr0jgIb5GUH@an3as.eu> <udl8rnbd3g0.fsf@mit.edu> <YwhT0rwVlr2QHaLx@an3as.eu> <udlsfljmap8.fsf@mit.edu>
Hi Aaron,
ping about this NCBI suite?
Kind regards
Andreas.
Am Fri, Aug 26, 2022 at 08:49:23AM -0400 schrieb Aaron M. Ucko:
> Andreas Tille <tille@debian.org> writes:
>
> > I noticed that another upload does not keep the position of the package
> > in the new queue but pulls it down at the end again. :-( BTW, what is
>
> Oops. I've gone ahead with 3.0.0+dfsg2-2 now, then; I'm confident in
> those changes and don't want to let the position slip much more.
>
> > your rationale to push the old version 2.11.2+dfsg-5 as well? Wouldn't
> > that be overridden by 3.0.0+dfsg2-1?
>
> Not immediately, because they're going to different suites, with 3.x
> still targeting experimental for now. The idea is to allow for a
> maximally clean transition to having a separate ncbi-vdb-data binary
> package in systems running testing or unstable and updated reasonably
> often. (Stable will of course be another matter, but still smooth
> enough.)
>
> > Thanks for working on this.
>
> No problem.
>
> > Without checking the background I think
> > debhelper uses debian/tmp for multiple binary packages and
> > debian/pkgname for single binary packages.
>
> Right, though I think that may vary by compatibility level.
>
> > I fail to understand in
> > what way the name of that temporary dir might be an issue but I can't
> > check in the next two weeks.
>
> debian/rules has some explicit references to debian/tmp, and dh_install
> moreover fails in this situation with the package's .install list.
> These are formalities that would be quick to address, but there's no
> point given that the source package will need to build multiple binary
> packages soon anyway.
>
> --
> Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
> http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?amu@monk.mit.edu
>
>
--
http://fam-tille.de
Reply to: