Hi,
On 8/9/19 4:41 PM, Karsten Merker wrote:
On Fri, Aug 09, 2019 at 02:31:47PM +0200, Ivo De Decker wrote:
Some random notes (these are just my preliminary thoughts, not a new release
team policy):
[...]
- We are talking about having both native 32-bit and 64-bit packages in
the same
Hi Aurelien,
On 8/8/19 10:38 PM, Aurelien Jarno wrote:
32-bit processes are able to address at maximum 4GB of memory (2^32),
and often less (2 or 3GB) due to architectural or kernel limitations.
[...]
Thanks for bringing this up.
1) Build a 64-bit compiler targeting the 32-bit correspondin
Daniel,
On Sun, Sep 08, 2013 at 10:36:42AM +0200, Daniel Pocock wrote:
> > There's no guarantee that "make" is being used for building, and
> > it's non-trivial to determine if it is or is not in use, nor how to
> > invoke it appropriately. If we want to do it centrally, it would
> > be more rel
Hi,
On Wed, May 08, 2013 at 05:28:58PM +0100, Neil Williams wrote:
> Other steps to take as preventative measures:
> * Make it a *MUST* that all transitions, no matter how small, are
> checked with the release team starting from as soon as the freeze is
> announced (not just after it starts) suc
Hi,
On Thu, Jul 19, 2012 at 02:51:14PM +0100, Ian Jackson wrote:
> We also have this:
> gscan2pdf: Recommends: 'cuneiform' [choice 1: cuneiform from non-free]
> which looks like a bug, which I have filed.
There's also these:
capi4hylafax: Recommends: 'isdnactivecards' [choice 1: isdnactivecard
5 matches
Mail list logo
