Hi Étienne
On Sat, 13 Feb 2021 at 01:24, Étienne Mollier
wrote:
> > 2. port vsearch on arm64.
>
> Good news, this option turns out to work out of the box! :)
Thanks for testing this!
> Assuming this kind of change is welcome in Soft Freeze, would it
> be possible to do a sponsored upload to e
Hi Aaron,
On Fri, Feb 12, 2021 at 04:56:20PM -0500, Aaron M. Ucko wrote:
> Andreas Tille writes:
>
> > But other 32bit architectures like armel and armhf are passing[2]. So I
> > fail to see why exactly i386 is failing. Is this possibly an effect of
> > bug #917851?
>
> Probably not; dropping
Hi again,
Étienne Mollier, on 2021-02-12 22:47:56 +0100:
> 2. port vsearch on arm64.
Good news, this option turns out to work out of the box! :)
Assuming this kind of change is welcome in Soft Freeze, would it
be possible to do a sponsored upload to enable vsearch on arm64?
https://sa
On Fri, Feb 12, 2021 at 10:57:01PM +0100, Pierre Gruet wrote:
> dcut dm --uid "Pierre Gruet" --allow drop-seq
Hi Pierre,
dcut command applied.
Cheers,
tony
signature.asc
Description: PGP signature
Hi,
I worked on drop-seq to correct its RC bug and add some minor improvements.
Would you mind reviewing or giving me DM rights?
dcut dm --uid "Pierre Gruet" --allow drop-seq
Many thanks,
Pierre
Andreas Tille writes:
> But other 32bit architectures like armel and armhf are passing[2]. So I
> fail to see why exactly i386 is failing. Is this possibly an effect of
> bug #917851?
Probably not; dropping the bug to a Bcc. Experimentation in an i386
chroot reveals the problem to be specific
Hi Nilesh,
Nilesh Patra, on 2021-02-13 02:05:47 +0530:
> Looks like majority of the q2-* migrated to bullseye. However,
> q2-quality-control and q2-feature-classifier haven't.
> The reason is at the tracker.
>
> Please consider uploading the fix and maybe we could request testing
> migration.
Ar
Hi Étienne
Looks like majority of the q2-* migrated to bullseye. However,
q2-quality-control and q2-feature-classifier haven't.
The reason is at the tracker.
Please consider uploading the fix and maybe we could request testing
migration.
PS: I'd have tried tracking and uploading a fix myself but
Hi Juhani,
On Fri, Feb 12, 2021 at 09:11:13PM +0200, Juhani Numminen wrote:
>
> As the soft freeze has begun, drmaa will not be allowed to
> re-enter testing.
As far as I know manual progression to testing can be approached
by filing a bug report to release.debian.org, but ...
> We could remov
Andreas Tille kirjoitti 12.2.2021 klo 11.09:
> I'd like to draw your attention to bug #951704 which finally
> prevents the migration of biomaj3[1].
As the soft freeze has begun, drmaa will not be allowed to
re-enter testing.
We could remove the python3-drmaa dependency relationship from
python3-b
On Fri, Feb 12, 2021 at 04:30:48PM +0500, Andrey Rahmatullin wrote:
> On Fri, Feb 12, 2021 at 11:21:38AM +0100, Hilmar Preuße wrote:
> > > But other 32bit architectures like armel and armhf are passing[2]. So I
> > > fail to see why exactly i386 is failing. Is this possibly an effect of
> > > bug
Hi Étienne,
On 2021-02-11 20:04, Étienne Mollier wrote:
> Thanks from me as well! I landed in the industrial world before
> having a chance to start a PhD thesis; publication nomenclatures
> are kind of foreign to me. I really welcome automated tools to
> point me to my mistakes in that matter.
On Fri, Feb 12, 2021 at 11:21:38AM +0100, Hilmar Preuße wrote:
> > > You can't adjust anything to get more than 4GB virtual memory on 32-bit
> > > architectures.
> > > You can try adjusting compilation/linking parameters to make the
> > > compiler/linker use less memory though (not sure if the sugg
Hi Hilmar,
On Fri, Feb 12, 2021 at 11:21:38AM +0100, Hilmar Preuße wrote:
> > But other 32bit architectures like armel and armhf are passing[2]. So I
> > fail to see why exactly i386 is failing. Is this possibly an effect of
> > bug #917851?
> >
> Maybe the memory of the whole builder is exhaus
Am 12.02.2021 um 11:01 teilte Andreas Tille mit:
On Fri, Feb 12, 2021 at 02:39:25PM +0500, Andrey Rahmatullin wrote:
Hi,
You can't adjust anything to get more than 4GB virtual memory on 32-bit
architectures.
You can try adjusting compilation/linking parameters to make the
compiler/linker use
Hi,
On Fri, Feb 12, 2021 at 02:39:25PM +0500, Andrey Rahmatullin wrote:
> > I wonder whether this could be simply solved by adjusting the hardware /
> > emulation parameters of the according autobuilder.
> >
> > Am I missing something?
> You can't adjust anything to get more than 4GB virtual memo
On Fri, Feb 12, 2021 at 10:17:06AM +0100, Andreas Tille wrote:
> in the build log[1] I found
>
>virtual memory exhausted: Operation not permitted
>
> I wonder whether this could be simply solved by adjusting the hardware /
> emulation parameters of the according autobuilder.
>
> Am I missing
Hi,
in the build log[1] I found
virtual memory exhausted: Operation not permitted
I wonder whether this could be simply solved by adjusting the hardware /
emulation parameters of the according autobuilder.
Am I missing something?
Kind regards
Andreas.
[1]
https://buildd.debian.org/
Hi Olivier,
I'd like to draw your attention to bug #951704 which finally
prevents the migration of biomaj3[1].
Kind regards
Andreas.
[1] https://qa.debian.org/excuses.php?package=biomaj3
--
http://fam-tille.de
19 matches
Mail list logo
