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

Bug#741339: RFS: sbnc/1.3~beta8-1 [ITA]



Package: sponsorship-requests
Severity: normal 

  Dear mentors,

  I am looking for a sponsor for my package "sbnc". As always checked
  with lintian. 

 * Package name    : sbnc
   Version         : 1.3~beta8-1
   Upstream Author : Gunnar Beutner <gunnar@beutner.name>
 * URL             : http://www.shroudbnc.info/
 * License         : GPL
   Section         : net

  It builds those binary packages:

    sbnc - IRC proxy for multiple users
    sbnc-dbg - IRC proxy for multiple users (debugging symbols)
    sbnc-php-dev - IRC proxy for multiple users (PHP classes)
    sbnc-tcl - IRC proxy for multiple users (Tcl extension)

  To access further information about this package, please visit the following URL:

  http://mentors.debian.net/package/sbnc

  Alternatively, one can download the package with dget using this command:

    dget -x http://mentors.debian.net/debian/pool/main/s/sbnc/sbnc_1.3~beta8-1.dsc

  More information about *sbnc* can be obtained from http://www.shroudbnc.info/

  Changes since the last upload:

  * New upstream release
    Upstream fixed several memory & resource leaks and removed dead code 
  * New Maintainer (Closes: #622977)
  * Include new watch file - Thanks to Bart Martens
  * Updated standards version
  * Set debhelper compatibility to 9
  * Include Japanese translation (Closes: #693059) 
    Thanks to victory <victory.deb@gmail.com> 
  * fix lintian warnings
  * enabled hardening flags
  * remove old snippets from debian/rules
  * adjust init script to source init functions
  * sbnc mysql support was removed because upstream dropped it from source
    Package sbnc-mysql is dropped as consequence 
    Also dropped build depends on libmysql-client
  * moved tcl scripts from /var/lib/sbnc to /usr/share/sbnc
  * removed most of the patches as they are now included by upstream
  * Place user configs in /etc/sbnc instead of /var/lib/sbnc


  Regards,
   Stefan Bauer


Reply to: