Re: RFS: gpaw/0.10.0.11364 ITP -- DFT and beyond within the projector-augmented wave method
Hi Marcin.
it would be nice if you would follow the list etiquette and not CC
single authors. Thanks.
On Thu, Jul 23, 2015 at 03:41:07PM +0200, Marcin Dulak wrote:
> > Hi Marcin,
> >
> > On Thu, Jul 23, 2015 at 02:30:32PM +0200, Marcin Dulak wrote:
> > > ~/gpaw $ cme fix dpkg-control
> > > Unknown application: dpkg-control. Run 'cme list' to list available
> > > applications
> >
> > Did you installed libconfig-model-dpkg-perl ?
> >
>
> too late, now on a broken debian 8.
In how far broken?
> While still on debian 8, i did what
> http://debian-med.alioth.debian.org/docs/policy.html says:
> *apt-get* install cme libconfig-model-dpkg-perl libconfig-model-itself-perl
> and cme seems not available on jessie.
That's correct. In Jessie cme is provided by some other package.
The policy is adapted to testing / unstable. In any case you
can find out what package provided what file by
apt-file search /usr/bin/cme
Check this out on your jessie system please since I simply forgot.
> actually I got 'cme fix dpkg-control' to work on a broken
> jessie/testing/sid,
> and commited that fix.
Again: In how far broken? In principle you can install packages from
testing / unstable inside stable, specifically these Perl packages
should not cause any harm (as long as there was no Perl migration).
> ...
> I think i saw a Vagrantfile like that somewhere, but it should be Debian
> that officially maintains such.
I can't follow this arguing. You should build in a pbuilder / unstable
environment and that's what all doc should recomment (sometimes instead
of pbuilder sbuild is used - the principle is the same). If you spot an
invalid doc please point the according author to this issue but you
should be more specific about the problem of the doc.
> > > i've clarified also with GPAW upstream that the latest GPAW release,
> > > 0.11.0, is not ready for python3 yet (e.g. it does not work in parallel
> > > with python3).
> >
> > :-(
> >
> what will happen then to gpaw packaging?
In any case I consider it sensible to package the latest version.
I could imagine that we could add some text to README.source about
the current upstream work regarding Python 3.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: