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

Bug#700943: marked as done (RFS: stdsyslog/0.03-1 [ITP] -- log a program's output to the system log)

Your message dated Thu, 21 Feb 2013 21:53:36 +0100
with message-id <20130221205336.GP8380@jadzia.comodo.priv.at>
and subject line Re: Bug#700943: RFS: stdsyslog/0.03-1 [ITP] -- log a program's output to the system log
has caused the Debian Bug report #700943,
regarding RFS: stdsyslog/0.03-1 [ITP] -- log a program's output to the system log
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.)


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

Dear mentors,

I am looking for a sponsor for my package "stdsyslog" - a tool that runs
a program and sends its output (on the standard output, standard error
and possibly other streams) to the system log.  This will be an initial
upload to close my ITP bug #699347.

* Package name:		: stdsyslog
  Version		: 0.03-1
  Upstream author	: Peter Pentchev <roam@ringlet.net>
* URL			: http://devel.ringlet.net/sysutils/stdsyslog/
* License		: BSD-2
  Section		: utils

It builds a single binary package, "stdsyslog", containing the utility
itself and a manual page.  It has been tested with Lintian and pbuilder.

The package is available for reviewing on mentors.d.n:

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

dget -x http://mentors.debian.net/debian/pool/main/s/stdsyslog/stdsyslog_0.03-1.dsc

As noted in the ITP bug, yes, I'm aware that the functionality of this
package might be partially replicated by a slightly convoluted command
line involving logger(1) and process substitution on shells that support
it, however once one decides to go just a little bit further, add just a
little bit more functionality, one gets to writing a simple script/tool
to do it - and that's exactly the duplication of work that I'm trying to
avoid here :)

Thanks in advance for your attention!

G'luck,
Peter

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Peter Pentchev	roam@ringlet.net roam@FreeBSD.org p.penchev@storpool.com
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
This sentence is false.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
On Thu, 21 Feb 2013 19:01:57 +0200, Peter Pentchev wrote:

> > Nice idea, and the package looks good to me.
> Thanks! :)  And thanks for the review!

You're welcome!
 
> > - Why don't you run the test suite during the build? I tried with
> >   TEST_STDSYSLOG and it worked.
> Well, I imagine - though I could be wrong here - that some people might
> not be too happy seeing syslog messages coming from a package build; 

Uh, good point.
I admit that I didn't actually look into the syslog ...

> Of course, another part of the reason is that these tests do not really
> test the *functionality* of stdsyslog - all they do is make sure that
> the stdsyslog binary *accepts* the combinations of command-line options.

I see, thanks for the explanation.

> Still, if you think that it would be a good idea to run the test suite
> during the Debian package build, I'll make it so.

No, now I understand your choice and agree with it.
 
> > - Any specific reason for "debhelper (>> 9)" instead of ">="? Not
> >   that it changes anything, I'm just curious about the
> >   not-so-often-used option.
> I guess I kind of got used to this sometime in the early days of my
> Debian packaging... 

Ok, so just habits like mine (only different ones). Fine.

> > (BTW: A pristine-tar branch in your git repo would be nice; at least
> > for git-buildpackage users, maybe not so mach otherwise :))
> Oof, right :)  I'll do that tonight or early tomorrow.  It's just that
> this is the master repository for the stdsyslog "upstream" sources, too,
> so I didn't even think about pristine-tar in this case :)

That was my guess, just that as a lazy reviewer/uploader I missed it
:)

Ok, I've uploaded the package now.
Feel free to contact me for future updates (preferably with a git
repo containing a pristine-tar branch :))


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Beatles: Glass Onion

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: