Re: Open issue with libbpp-core
Hi,
On Wed, Jun 14, 2017 at 07:18:22PM +0200, Julien Yann Dutheil wrote:
> Not sure what the problem exactly is, but reading back our emails from one
> year ago, I realise I have skipped a few episodes: we mentioned bppsuite
> and comap, but we actually said we would proceed with the libraries first,
> I had forgotten that, I sincerely apologize for that.
I think I understood your mails rather that way that all those packages
would be new packages we need to package from scratch. I was not aware
that those packages would exist in Debian.
My hint (may be not as polite as it should have been) was also to
Andreas Beckmann who fixed some bugs in an NMU in September 2016. We
had taken over the libraries in June 2016 and I'm simply hoping that
every Debian developer would realise in cases like this: Hey, there is
a package that fits into Debian Med team - pinging them what's wrong
here might make sense.
> I have now registered
> to Alioth and will go thru all the documentation about the procedure in
> more details. I'll probably have some questions though.
I have uploaded the libs and bppsuite which all need to go through new
queue due to package name changes. I delayed the upload of bppphyview
until the libs are accepted. For sure you are more than welcome to work
on future upgrades and asking questions is perfectly fine.
Kind regards
Andreas.
> On Wed, Jun 14, 2017 at 1:47 PM, Andreas Tille <tille@debian.org> wrote:
>
> > Hi,
> >
> > On Tue, Jun 13, 2017 at 10:56:14AM +0200, Julien Yann Dutheil wrote:
> > > Ok, everything tagged then:
> > > bpp-core, seq, phyl, popgen, raa, seq-omics, phyl-omics, qt => v2.3.1
> >
> > Uploaded, needs to pass new queue.
> >
> > > bppsuite => v2.3.1
> > > bppphyview => v0.5.1
> >
> > Hmmm, I noticed that Andreas Beckmann did NMUs and Julien failed to give
> > hints to the Debian Med team. Please everybody: If you see any package
> > that belongs into Debian Med scope and is not maintained by the Debian
> > Med team please give us a hint. The whole BPP suite somehow slipped
> > through our radar and after I took over the libbpp* packages I somehow
> > failed to continue with bppsuite and bppphyview which has now left these
> > packages in a packaging state with lower packaging standards than we
> > usually are applying. The packages are also missing in our
> > metapackages. I wonder whether I did not yet made enough noise about
> > the Debian Med effort that everybody considers it normal that those
> > packages will profit from our team maintenance and that it makes sense
> > to contact the Debian Med team.
> >
> > > comap => v1.5.2
> >
> > Not yet packaged (as far as I can see).
> >
> > > physamp => v1.0.1
> > > maffilter => v1.2.1
> >
> > Will be updated as soon as the libs are available in unstable.
> >
> > > Many thanks to you for your patience!
> >
> > I'm quite patient about new upstream versions - I'm less patient with
> > packages that are not properly maintained but easily could be so if the
> > information would be properly propagated. ;-)
> >
> > Kind regards
> >
> > Andreas.
> >
> > > On Tue, Jun 13, 2017 at 9:13 AM, Andreas Tille <andreas@an3as.eu> wrote:
> > >
> > > > Hi Julien,
> > > >
> > > > On Sat, Jun 10, 2017 at 08:45:36PM +0200, Julien Yann Dutheil wrote:
> > > > > We have now committed several fixes to the cmake files and increased
> > the
> > > > > interface numbers in all libs (excepted the bpp-qt one, which did not
> > > > > change since the last version, only compatibility updates).
> > > > >
> > > > > Everything is on the master branch, but I have not tagged the new
> > > > > versions... would there be a way to check that everything is in order
> > > > > before doing so? It seems to me that making a new version number and
> > tag
> > > > > after each bug fix is rather ineffective... or maybe I should make a
> > > > > temporary tag only for testing purpose (sthg like v2.3.1-pre1?)
> > > >
> > > > I've tested to build bpp-core which looks OK and I was also able to
> > > > successfully build bpp-seq using the package resulting from the above
> > > > build process. I think it is fine to set a tag at this stage.
> > > >
> > > > Kind regards and thanks for your cooperation
> > > >
> > > > Andreas.
> > > >
> > > > --
> > > > http://fam-tille.de
> > > >
> > >
> > >
> > >
> > > --
> > > Julien Y. Dutheil, Ph-D
> > > 0 (+49) 4522 763 298
> > >
> > > § Max Planck Institute for Evolutionary Biology
> > > Molecular Systems Evolution
> > > Department of Evolutionary Genetics
> > > Plön -- GERMANY
> > >
> > > § Institute of Evolutionary Sciences - Montpellier
> > > University of Montpellier 2 -- FRANCE
> >
> > --
> > http://fam-tille.de
> >
>
>
>
> --
> Julien Y. Dutheil, Ph-D
> 0 (+49) 4522 763 298 <+49%204522%20763298>
>
> § Max Planck Institute for Evolutionary Biology
> Molecular Systems Evolution
> Department of Evolutionary Genetics
> Plön -- GERMANY
>
> § Institute of Evolutionary Sciences - Montpellier
> University of Montpellier 2 -- FRANCE
--
http://fam-tille.de
Reply to: