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

Bug#872629: marked as done (RFS: dmalloc/5.5.2-9)



Your message dated Wed, 30 Aug 2017 02:21:12 +0200
with message-id <20170830002112.gvg7iqo2rrnjpasa@angband.pl>
and subject line Re: Bug#872629: RFS: dmalloc/5.5.2-9
has caused the Debian Bug report #872629,
regarding RFS: dmalloc/5.5.2-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
872629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872629
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package "dmalloc"

 * Package name    : dmalloc
   Version         : 5.5.2-9
   Upstream Author : Gray Watson <http://256stuff.com/gray/email/>
 * URL             : http://dmalloc.com/
 * License         : CC-BY-SA-3.0 or Dmalloc
   Section         : devel

  It builds these binary packages:

    libdmalloc-dev - debug memory allocation library (development files and doc)
    libdmalloc5 - debug memory allocation library

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

  https://mentors.debian.net/package/dmalloc


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

    dget -x https://mentors.debian.net/debian/pool/main/d/dmalloc/dmalloc_5.5.2-9.dsc

  More information about my recent changes can be obtained at https://github.com/e7appew/pkg-dmalloc.

  Changes since the last upload:

  * Avoid direct calls to dpkg-parsechangelog from debian/rules.
  * Regenerate patches with git version 2.14.1.
  * Update compliance to Standards Version 4.0.1.
    + Priority is now optional, since extra is deprecated.
    + Update configure.ac to work with autoreconf 2.69 since autoreconf
      is now automatically performed by debhelper by default.
  * Mark libdmalloc5 package as Multi-Arch: same.
  * Enable LFS support for 32-bit architectures.
  * Remove incorrect use of 'Origin: vendor' from DEP-3 patch headers.
  * Perform wrap-and-sort on all Debian control files.
  * Fix typos in documentation.
  * Package HTML and PDF docs built from texi source file, rather than
    just packaging the ones built upstream.
  * Fix erroneous failure in dmalloc_t.c test when free(NULL) is called.
  * Fix typo in debian/libdmalloc-dev.doc-base.
  * Update debian/copyright.


  Regards,
   Carlos Maddela

--- End Message ---
--- Begin Message ---
On Sun, Aug 20, 2017 at 12:25:22AM +1000, Carlos Maddela wrote:
>  * Package name    : dmalloc
>    Version         : 5.5.2-9

>   Changes since the last upload:
> 
>   * Avoid direct calls to dpkg-parsechangelog from debian/rules.
>   * Regenerate patches with git version 2.14.1.
>   * Update compliance to Standards Version 4.0.1.
>     + Priority is now optional, since extra is deprecated.
>     + Update configure.ac to work with autoreconf 2.69 since autoreconf
>       is now automatically performed by debhelper by default.
>   * Mark libdmalloc5 package as Multi-Arch: same.
>   * Enable LFS support for 32-bit architectures.
>   * Remove incorrect use of 'Origin: vendor' from DEP-3 patch headers.
>   * Perform wrap-and-sort on all Debian control files.
>   * Fix typos in documentation.
>   * Package HTML and PDF docs built from texi source file, rather than
>     just packaging the ones built upstream.
>   * Fix erroneous failure in dmalloc_t.c test when free(NULL) is called.
>   * Fix typo in debian/libdmalloc-dev.doc-base.
>   * Update debian/copyright.

✓

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀                                 -- Genghis Ht'rok'din
⠈⠳⣄⠀⠀⠀⠀ 

--- End Message ---

Reply to: