Off list.
Thanks!
Richard
On Wed, 16 Oct 2013 19:49:54 +0200
Dominik George n...@naturalnet.de wrote:
Hi,
The only problem is that on small machines (things like the BeagleBone)
xz compression requires enough memory that you have to enable swap to
use dpkg. Now on a machine with a sensible disk this is not a
On Fri, Oct 25, 2013 at 03:33:42PM +0200, Marko Randjelovic wrote:
correct me if I'm wrong, but it appears to me that xz compression has
become the default in dpkg. With that in mind, won't this issue come up
anyway? I mean, once a maintainer fixes a bug in a pckage and uplods it,
the
On Fri, 25 Oct 2013 15:52:38 +0200
Adam Borowski kilob...@angband.pl wrote:
xz has slow compression, fast decompression. You're not really going to
build packages on any box where compression speed is a blocker, and even if
you do, actually building the package will take a wolf share of the
On Fri, Oct 25, 2013 at 05:36:08PM +0200, Marko Randjelovic wrote:
Not quite, xz is also slower than gzip in decompression, cca 3 times,
which is not neglectable on slow machines, especially when installing
large sets of packages.
This is incorrect. xz -[012] is way better in terms of
On Fri, 18 Oct 2013, Guillem Jover wrote:
For example on one of my 64-bit systems, with 220481 paths installed, I
go from 62.8 MiB to 46.1 MiB max resident memory, a saving of 16.7 MiB.
That should compensate a bit for the slight increase in memory usage
from xz.
This is great, thank you!
--
On Wed, October 16, 2013 16:20, Hideki Yamane wrote:
As dpkg introduced xz compression by default, we can make whole
packages xz-ed now. I think it's worth to try, so propose it as
a release goal (I know it should be sent before its dead line, but
please read).
Because dpkg =1.17.0
David Goodenough david.goodenough at btconnect.com writes:
xy may only use a tiny bit, but the combination of apt-get, dpkg and
xy seems to cause problems. Its not just BeagleBones, there are x86
machines with just 64MB still on sale.
SOL then. It’s actually apt/dpkg that takes that much
On Thu, Oct 17, 2013 at 11:31:23AM +, Thorsten Glaser wrote:
So, this means that, yes, you need a total of at least 128 MiB RAM+swap,
if not more, to use apt/dpkg in sid (and recent releases were not much
smaller).
Managed with ~100M with squeeze (in VMs) — I remember because I recall
yum
Le Thu, Oct 17, 2013 at 11:31:23AM +, Thorsten Glaser a écrit :
It’s actually apt/dpkg that takes that much memory because,
you know, a database listing 3 binary packages in sid *does* take
quite some RAM. We have the same problem on m68k, but you can’t do much
against that (except,
SEE 271...@bugs.debian.org
Maybe insted of reading the file in memory concatenating then mmaping the
resulting file will help in case of low memory
Bastien
Le 17 oct. 2013 13:43, Jonathan Dowland j...@debian.org a écrit :
On Thu, Oct 17, 2013 at 11:31:23AM +, Thorsten Glaser wrote:
So,
On Thu, Oct 17, 2013 at 09:39:34PM +0900, Charles Plessy wrote:
Le Thu, Oct 17, 2013 at 11:31:23AM +, Thorsten Glaser a écrit :
It’s actually apt/dpkg that takes that much memory because,
you know, a database listing 3 binary packages in sid *does* take
quite some RAM. We have
Hi!
On Wed, 2013-10-16 at 17:32:37 +0100, David Goodenough wrote:
xy may only use a tiny bit, but the combination of apt-get, dpkg and
xy seems to cause problems. Its not just BeagleBones, there are x86
machines with just 64MB still on sale.
Ok, I went through the dpkg code, and have reduced
Hi,
As dpkg introduced xz compression by default, we can make whole
packages xz-ed now. I think it's worth to try, so propose it as
a release goal (I know it should be sent before its dead line, but
please read).
On Wednesday 16 Oct 2013, Hideki Yamane wrote:
Hi,
As dpkg introduced xz compression by default, we can make whole
packages xz-ed now. I think it's worth to try, so propose it as
a release goal (I know it should be sent before its dead line, but
please read).
David Goodenough david.goodeno...@btconnect.com writes:
The only problem is that on small machines (things like the BeagleBone)
xz compression requires enough memory that you have to enable swap to
use dpkg. Now on a machine with a sensible disk this is not a problem,
but on a machine where
On Wednesday 16 Oct 2013, Marius Gavrilescu wrote:
David Goodenough david.goodeno...@btconnect.com writes:
The only problem is that on small machines (things like the BeagleBone)
xz compression requires enough memory that you have to enable swap to
use dpkg. Now on a machine with a
On Wed, Oct 16, 2013 at 05:32:37PM +0100, David Goodenough wrote:
xy may only use a tiny bit, but the combination of apt-get, dpkg and
xy seems to cause problems. Its not just BeagleBones, there are x86
machines with just 64MB still on sale.
Do we expect to build Debian packages on such
On Wednesday 16 Oct 2013, Lars Wirzenius wrote:
On Wed, Oct 16, 2013 at 05:32:37PM +0100, David Goodenough wrote:
xy may only use a tiny bit, but the combination of apt-get, dpkg and
xy seems to cause problems. Its not just BeagleBones, there are x86
machines with just 64MB still on sale.
Lars Wirzenius l...@liw.fi writes:
Do we expect to build Debian packages on such systems?
David's point was that installing such a package would require too much
memory due to xz's decompression memory requirements (9MB with default
options).
--
Marius Gavrilescu
pgpuiMWwJJsFS.pgp
On Wed, Oct 16, 2013 at 07:19:19PM +0300, Marius Gavrilescu wrote:
At the default preset (-6), the required RAM for decompressing is about
9MB. The BeagleBone seems to have 256MB of memory (that's what
Wikipedia says), so 9MB shouldn't be an issue.
Didn't we discuss this last year already?
Hi,
The only problem is that on small machines (things like the BeagleBone)
xz compression requires enough memory that you have to enable swap to
use dpkg. Now on a machine with a sensible disk this is not a problem,
but on a machine where the disk is an SD-card it is a disaster.
correct me
On 10/17/2013 12:35 AM, Lars Wirzenius wrote:
On Wed, Oct 16, 2013 at 05:32:37PM +0100, David Goodenough wrote:
xy may only use a tiny bit, but the combination of apt-get, dpkg and
xy seems to cause problems. Its not just BeagleBones, there are x86
machines with just 64MB still on sale.
Do
23 matches
Mail list logo
