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

Bug#795086: marked as done (RFS: par2cmdline/0.6.14-1)

Your message dated Mon, 10 Aug 2015 20:15:51 +0000 (UTC)
with message-id <571617600.2441855.1439237751841.JavaMail.yahoo@mail.yahoo.com>
and subject line Re: Bug#795086: RFS: par2cmdline/0.6.14-1
has caused the Debian Bug report #795086,
regarding RFS: par2cmdline/0.6.14-1
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.)


-- 
795086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795086
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 "par2cmdline":
  Package name    : par2cmdline
  Version         : 0.6.14-1
  Upstream Author : Ike Devolder et al.
  URL             : https://github.com/Parchive/par2cmdline
  License         : GPL-2+
  Section         : utils

It builds a single binary package:
  par2  - PAR 2.0 compatible file verification and repair tool

Mentors URL:
  http://mentors.debian.net/package/par2cmdline

Download:
dget -x http://mentors.debian.net/debian/pool/main/p/par2cmdline/par2cmdline_0.6.14-1.dsc

Changes since the last upload:
  * New upstream release.
  * Add patch 01: use /dev/urandom instead of /dev/random in test 20
    to prevent lengthy delays during build.


Thanks.

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Hi again,

>Hi, I'm doing a test build right now, I'll see how it goes and report back :)
>
>The packaging looks good, I would appreciate a patch with an header (the one created by dpkg-source --commit), describing maybe that the patch >is already part of upstream
>
>(maybe just add a Description saying the patch can be dropped on next release, or even more on changelog mention that the patch is a cherry-pick >from upstream/master, even if the athor is you :)
>
>cheers,


built&signed&uploaded, thanks for your contribution to Debian!

another issue: next time please try to fix the hurd build failure, it might be easier than what you think,
just define PATH_MAX and a few other bits and you might be ready!

cheers,

Gianfranco

--- End Message ---
Reply to: