Package: debdelta
Version: 0.36
Severity: wishlist

Hi,

i have a big mirror of debian, which includes
amd64, i386, hurd, and kfreebsd-*

I wish to run debdeltas easly on this mirror
pool, but only for i386 architecture.
Because most of users uses it, and debdeltas
will be most usefull for them, additionally
my server lacks CPU and disk resources for running,
full debdeltas on all architectures.

Currently i don't know how easly to do this,
I added if arch != "i386": continue just before yield
in iterate_Packages, in debdeltas, but it doesn't helped.

It is probably very simple change, and it could be usefull.

Thanks.



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-1-686-bigmem (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to pl_PL.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debdelta depends on:
ii  binutils               2.20-4            The GNU assembler, linker and bina
ii  bzip2                  1.0.5-3           high-quality block-sorting file co
ii  libbz2-1.0             1.0.5-3           high-quality block-sorting file co
ii  libc6                  2.10.2-2          GNU C Library: Shared libraries
ii  python                 2.5.4-2           An interactive high-level object-o
ii  zlib1g                 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages debdelta recommends:
ii  bsdiff                      4.3-9        generate/apply a patch between two
ii  lzma                        4.43-14      Compression method of 7z format in
ii  python-apt                  0.7.13.4     Python interface to libapt-pkg
ii  xdelta                      1.1.3-9      A diff utility which works with bi
ii  xdelta3                     0v2.dfsg-1.1 A diff utility which works with bi

debdelta suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to