Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "qtractor":
* Package name: qtractor
Version : 0.9.20-1
Upstream Author : Rui Nuno Capela
* URL : https://qtractor.sourceforge.io/
* License : GPL-2+,
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 Thomas,
i've successfully built paperwork 2.0.2 in a clean sid chroot,
using gbp buildpackage (and sbuild).
The package is lintian clean.
However, i don't quite understand the usefulness of these packages:
- openpaperwork-core
- openpaperwork-core-doc
- openpaperwork-gtk
- openpaperwork-gtk-do
Hi,
Sorry I only checked (and answered) to your comment on mentors.d.n. I
just saw now you left the same message here.
First, thanks for reviewing my package.
The sphinxdoc debhelper extension[1] helps to install documentation
build with sphinx (python3-sphinx package).
Can you check you ins
Hi,
On Thu, 11 Feb 2021 12:54:11 +0100 =?UTF-8?Q?G=C3=BCrkan_Myczko?=
wrote:
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "flowblade":
>
> * Package name : flowblade
> Version : 2.8-1
> Upstream Author :
Thanks for the tips everyone - it wasn't the silver bullet I was after,
but that has given me some clues to investigate.
It turned out to be faster to fix my laptop and upload from there :-)
I will hopefully get some time to fully investigate what is wrong with
the desktop machine soon.
On 10/02/
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
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/
13 matches
Mail list logo
