Re: Bug#922010: RFS: libmurmurhash 1.3

I don't know why this was being discussed on a RT unblock bug (it should be moved elsewhere really, so just adding the bug in Bcc) On 11/02/2019 16:53, Fabian Klötzl wrote: > Long Description: PMurHash comes with a few functions e.g. > "PMurHash32_Process" > which I use internally, but I don't wa

Re: Please allow seqsero to migrate to testing

On 27/04/18 11:51, Andreas Tille wrote: > Hello, > > We have one more case of an arch:all package held up in testing because > a dependency on bwa and other packages which is not available on i386. > Can seqsero be allowed to migrate to Testing? force-hint added. Emilio

Re: Please allow paleomix to migrate to testing

On 24/04/18 15:47, Andreas Tille wrote: > Hello, > > We have one more case of an arch:all package held up in testing because > of installability issues on i386 due to a dependency on bwa and other > packages. Can paleomix be allowed to migrate to Testing? Force-hinted. Emilio

Re: Please allow smalr to migrate to testing

On 23/04/18 00:06, Afif Elghraoui wrote: > Hello, > > We have one more case of an arch:all package held up in testing because > of installability issues on i386 due to a dependency on bwa. Can smalr > be allowed to migrate to Testing? > > https://qa.debian.org/excuses.php?package=smalr force-h

Re: Ask for rebuild of python-biopython

On 30/11/17 17:53, olivier sallou wrote: > Hi, > package build of python-biopython failed during test step on last upload on > mips64el [0] > > I tried to build the package via a chroot on eller.debian.org > and faced no error, package could build succesfully. > Could p

Re: [Help] Failed to apply new Python policy to GNUmed packages

Andreas Tille wrote: > On Sun, 29 Mar 2009, Emilio Pozuelo Monfort wrote: > >> In that case the .pyc files won't be loaded, but the .py ones, I guess >> (please >> somebody correct me if I'm wrong). Nothing to worry about as people >> will usually >>

Re: [Help] Failed to apply new Python policy to GNUmed packages

Karsten Hilbert wrote: >> You're missing a 'export' before setting the variable (or call python in >> the >> same line you set it). > > Ah, thanks. Emilio, you are clearly a better expert on > packaging Python code under Debian than me :-) That was shell ;) >>> I really wonder how this new pyth

Re: [Help] Failed to apply new Python policy to GNUmed packages

Hiya, Andreas Tille wrote: > On Sat, 28 Mar 2009, Emilio Pozuelo Monfort wrote: > >> That is, you're now shipping some modules in a private location > > This is what I understood as recommendation in #516037. Yes, that's recommended, but it's not a requir

Re: [Help] Failed to apply new Python policy to GNUmed packages

Hi Andreas, Andreas Tille wrote: > Hi, > > I tried to implement the Python policy [1] using python-support to > the new GNUmed packages but failed. If I try the basic essence > of the /usr/bin/gnumed script I get: > > $ python -m Gnumed.wxpython.gnumed > Traceback (most recent call last): > F