[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

ITP: rproxy and libhsync

I am surprised that nobody has already packaged this, but I can't
seem to find it...

If nobody protests, consider this my ITP.

[503] [lyell:bmay] ~/debian >dpkg -I libhsync-dev_0.5.7-1_i386.deb
 new debian package, version 2.0.
 size 36168 bytes: control archive= 1030 bytes.
     422 bytes,    12 lines      control              
     755 bytes,    11 lines      md5sums              
     273 bytes,     8 lines   *  postinst             #!/bin/sh
     202 bytes,     6 lines   *  prerm                #!/bin/sh
 Package: libhsync-dev
 Version: 0.5.7-1
 Section: devel
 Priority: optional
 Architecture: i386
 Installed-Size: 172
 Maintainer: Brian May <bam@debian.org>
 Description: Transfer data using rsync like protocol
  libhsync is the next generation of librsync, and provides flexible
  checksum-based differencing.  The main application at the moment in
  rproxy, but the library should eventually be generally useful.
 Source: libhsync

[504] [lyell:bmay] ~/debian >dpkg -I rproxy_0.5.7-1_i386.deb
 new debian package, version 2.0.
 size 40502 bytes: control archive= 2070 bytes.
     835 bytes,    14 lines      control              
     641 bytes,    10 lines      md5sums              
    1810 bytes,    65 lines   *  postinst             #!/bin/sh
    1213 bytes,    48 lines   *  postrm               #!/bin/sh
     190 bytes,     6 lines   *  prerm                #!/bin/sh
 Package: rproxy
 Version: 0.5.7-1
 Section: net
 Priority: optional
 Architecture: i386
 Depends: libc6 (>= 2.1.2)
 Installed-Size: 160
 Maintainer: Brian May <bam@debian.org>
 Description: Extensions to HTTP to use rsync like protocol
  rproxy adds backwards-compatible extensions to HTTP that come into
  operation when two parties to a web request understand the `hsync'
  encoding. If there are no two that can handle these extensions then
  they are silently ignored, so that the software will interoperate
  smoothly with existing systems. These parties might be the user agent
  (browser), the origin server, or intermediate proxies. At this stage
  of the project special-purpose proxies are used so that neither the
  server nor user-agent need be changed, but we expect to integrate this
  extension into popular web software in the near future.

  I do not plan to make any alterations to the upstream source
(unless there is a policy violation). However, the upstream
author(s) have made some decisions which I don't like:
  - libhsync shared library support removed.
  - binaries used for development are not installed (except for

If this is not acceptable, then please talk to upstream about fixing
it and/or take over the job of maintaining the package.
Brian May <bam@debian.org>

Reply to: