Debian Planet

Welcome to Debian Planet


Apt-get into it.
Main Menu

  • Home

  • Topics

  • Web Links

  • Your Account

  • Submit News

  • Stats

  • Top 10

  • Debian

    These are important Debian sites one should not be without!

  • Official Debian site

  • Package search

  • Mailing list archives

  • Bug reports

  • Debian on CD

  • Unofficial woody CD ISOs

  • Unofficial APT sources

  • Developers’ Corner

    Other great Debian news sources:

  • Debian Weekly News

  • Kernel Cousin Debian

    (Debian mailing lists digested)
  • Community Groups

    Need help? You’re not alone on this planet.

  • debianHELP

    (User support site)

  • Debian International



  • EsDebian


  • DebianWorld


  • MaximumDebian


  • DebianUsers


  • Debian-BR


  • IRC

    The place to get help on a Debian problem (after reading docs) or to just chat and chill is #debian on

    Many of the Debian Planet staff live there so pop by and say hello.

    Wanna write?

    Got that latest or greatest scoop? Perhaps you have some important news for the Debian community? Submit a news item!

    Or perhaps you’ve written a rather ground breaking insight into some aspect of Debian and you feel compelled to share it with others? Knock up a longer editorial article and send it to the editors.


    DP is sponsored by Xinit Systems and

    Domains paid for and hosted by

    Buy your Debian merchandise at

    Who’s Online

    There are currently, 75 guest(s) and 2 member(s) that are online.

    You are Anonymous user. You can register for free by clicking here.


    Packages.gz is an imperfect aproach (Score: 2)
    by Anonymous on Friday, November 30 @ 09:15:24 GMT

    I think the real problem is that there is much un-necessary information in the Packages.gz if you you just want to check for updates.

    Packages.gz is 5.9MB, (compressed its 1.6 MB), there are 3MB just in the descriptions, its only going to grow.

    lf the user is using stable or otherwise hardly ever updates then this isnt an issue, but for testing or unstable most of the downloaded data is the same. Less than 1% of packages change between most peoples updates, but 99% of duplicate information is always beeing downloaded

    I think there should be a package index file (similar format to the override file) which just has the package name, version and revision of every package in the dist, it would endup only being a couple of hundred kB.

    Complementary to this the metadata for each BINARY package could be merged into the .dsc file, which would only have to be downloaded when its changed (not every time). Probably have to rework the revision numbering scheme to acomadate a changeing .dsc file though.

    A package daemon would be cool i think, that way it could be queried and just spit out new/updated descriptions instead of the user downloading so much duplicate information every time.

    Anyway this is all too radical to be practical at the moment, its how i see it though.

    Rsync is an issue which has been discussed at length on the debian-devel mailing list. Its too CPU intensive, using xdelta to do a binary diff against “milestone’ package.gz’s would be a better way to do it in a traditional way.

    Your Name: Anonymous [ New User ]



    Allowed HTML:
    <p> <b> <i> <a> <em> <br> <strong> <blockquote> <tt> <li> <ol> <ul>