[Debichem-devel] Bug#910686: Pymol 2.2.0 sources available from github

[Stuart Prescott]

Hi Michael,

> I've updated the debian packaging in git now and pymol-2.2.0 builds, but
> (i) the upstream git files need updating (Andreas did that in the
> past?) 

Having downloaded the upstream source (with uscan) and ensuring that you have 
no uncommitted changes:

$ gbp import-orig ../pymol_2.2.0.orig.tar.gz

(I've done this locally, do you want me to push that change?)

> and (ii) the autopkgtests fail in a somewhat weird way for me:
> |autopkgtest [10:38:14]: testing package pymol version 2.2.0-1
> |autopkgtest [10:38:14]: build not needed
> |autopkgtest [10:38:15]: test command1: preparing testbed
> |Get:1 file:/tmp/autopkgtest.yS77Sj/binaries  InRelease
> |Ign:1 file:/tmp/autopkgtest.yS77Sj/binaries  InRelease
> |Get:2 file:/tmp/autopkgtest.yS77Sj/binaries  Release [816 B]
> |Get:2 file:/tmp/autopkgtest.yS77Sj/binaries  Release [816 B]
> |Get:3 file:/tmp/autopkgtest.yS77Sj/binaries  Release.gpg
> |Ign:3 file:/tmp/autopkgtest.yS77Sj/binaries  Release.gpg
> |Get:4 file:/tmp/autopkgtest.yS77Sj/binaries  Packages [2258 B]
> |Reading package lists...
> |Reading package lists...
> |Building dependency tree...
> |Reading state information...
> |Correcting dependencies...Starting pkgProblemResolver with broken count: 1
> |Starting 2 pkgProblemResolver with broken count: 1
> |Investigating (0) autopkgtest-satdep:amd64 < 0 @iU mK Nb Ib >
> |Broken autopkgtest-satdep:amd64 Depends on pymol:amd64 < none | 2.2.0-1 @un

How are you running the tests? It looks like you've not given autopkgtest the 
precompiled debs and haven't let it redo the compilation. The following works 
fine:

$ autopkgtest -B pymol_2.2.0-1_amd64.changes \
	--- adt-virt-schroot unstable-amd64-sbuild


The test scripts succeed although there are actually some errors in the test 
output:

	Error: unknown Setting: 'cull_spheres'.                                                                            

(I can't see any documentation about that no longer being a command -- the 
test does otherwise run just fine though)


There was also speculation a while back about this being the right time to 
switch from Python 2 to Python 3 and from tk to Qt.

Any thoughts?

Cheers
Stuart


-- 
Stuart Prescott    http://www.nanonanonano.net/   stuart at nanonanonano.net
Debian Developer   http://www.debian.org/         stuart at debian.org
GPG fingerprint    90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7