RFS: perlbal, libperlbal-perl -- An http load balancer written in perl
Hello folks, As the subject says I'm looking for a sponsor for my first Debian package submission. Files location: http://hachi.kuiki.net/stuff/debian/perlbal/ ITP Bug: 456534 Source package: perlbal Packages: perlbal, libperlbal-perl License: same as perl5 (GPL1+ or Artistic) Description: Perl-based reverse proxy load balancer and web server Perlbal is a single-threaded event-based server supporting HTTP load balancing, web serving, and a mix of the two. Perlbal can act as either a web server or a reverse proxy. . One of the defining things about Perlbal is that almost everything can be configured or reconfigured on the fly without needing to restart the software. A basic configuration file containing a management port enables you to easily perform operations on a running instance of Perlbal. . Perlbal can also be extended by means of per-service (and global) plugins that can override many parts of request handling and behavior. Lintian is clean on my dev machine. Init script behaves in all tests I run it through. Daemon doesn't start by default Default user is www-data for serving Thanks for reading, Jonathan Steinert (hachi) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f66e010.1030...@hachi.kuiki.net
Bug#664634: RFS: engauge-digitizer/5.0-2 [RC]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package engauge-digitizer * Package name: engauge-digitizer Version : 5.0-2 Upstream Author : Mark Mitchell mmdigiti...@earthlink.net * URL : http://digitizer.sourceforge.net/ * License : GPL-2+ Section : science It builds those binary packages: engauge-digitizer - interactively extracts numbers from bitmap graphs or maps engauge-digitizer-doc - engauge-digitizer user manual and tutorial To access further information about this package, please visit the following URL: http://mentors.debian.net/package/engauge-digitizer Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/e/engauge- digitizer/engauge-digitizer_5.0-2.dsc More information about engauge-digitizer can be obtained from http://digitizer.sourceforge.net/ Changes since the last upload: * Added patch fixing passing double as qreal. Closes: #656943 (FTBFS on armel and armhf) * Remove deprecated encoding key in desktop file * Updated to standards version 3.9.3 Best Regards, Tobias Winchen signature.asc Description: This is a digitally signed message part.
Best use of bug tracker for a complicated situation
I maintain roxterm. The source package of that name generates a number of binary packages: roxterm-common, roxterm-gtk2, roxterm-gtk3 and roxterm (a virtual package depending on roxterm-gtk3). A user has reported 2 bugs with slightly different symptoms, one for roxterm-gtk2 and one for roxterm-gtk3. They're actually the same bug, applying to both, and I think also to old versions when there was only one binary package, roxterm. What's the best way to show the bugs affect all three? I used: affects n roxterm roxterm-gtk2 roxterm-gtk3 Would it be better to reassign them to the source package? In my control message how would I distinguish that from the binary packages of the same name? By appending :src? I reassigned them both to roxterm-gtk3 and then tried to merge them, but the merge is failing with what looks like an internal error involving an array where it expected a hash (reported verbatim to owner@bdo). So far I've been copying my comments to both bugs. Meanwhile the user has added a comment to both which looks like there might be a new, separate bug. So I reckon I should forget the merge, continue to discuss the first problem in one of the reports and retitle the other report to reflect the possible new problem. Agreed? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120319173745.5a8ec8ea@junior
Bug#664669: RFS: moserial/3.0.6-1 [ITP] -- gtk3-based serial terminal
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package moserial * Package name: moserial Version : 3.0.6-1 Upstream Author : Michael J. Chudobiak. m...@avtechpulse.com * URL : http://live.gnome.org/moserial * License : GPL3 Section : comm It builds those binary packages: moserial - gtk-based serial terminal for the gnome desktop To access further information about this package, please visit the following URL: http://mentors.debian.net/package/moserial Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/moserial/moserial_3.0.6-1.dsc Regards, Rodolphe Pelloux-Prayer -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120319183416.446.65370.reportbug@localhost.localdomain
Re: Best use of bug tracker for a complicated situation
On Mon, 19 Mar 2012 17:37:45 +, Tony Houghton h...@realh.co.uk wrote: Hi, I maintain roxterm. The source package of that name generates a number of binary packages: roxterm-common, roxterm-gtk2, roxterm-gtk3 and roxterm (a virtual package depending on roxterm-gtk3). A user has reported 2 bugs with slightly different symptoms, one for roxterm-gtk2 and one for roxterm-gtk3. They're actually the same bug, applying to both, and I think also to old versions when there was only one binary package, roxterm. What's the best way to show the bugs affect all three? I used: affects n roxterm roxterm-gtk2 roxterm-gtk3 Would it be better to reassign them to the source package? In my control message how would I distinguish that from the binary packages of the same name? By appending :src? In this case use the 'found' command for these two (still meant to be separate) bugs: found NNN sourcepackagename/version found MMM sourcepackagename/version I reassigned them both to roxterm-gtk3 and then tried to merge them, but the merge is failing with what looks like an internal error involving an array where it expected a hash (reported verbatim to owner@bdo). So far I've been copying my comments to both bugs. This internal mishap needs to be investigated. Perhaps owner@bdo will provide more information. Meanwhile the user has added a comment to both which looks like there might be a new, separate bug. So I reckon I should forget the merge, continue to discuss the first problem in one of the reports and retitle the other report to reflect the possible new problem. Agreed? Yes, if you feel that these two bug reports appear to be caused by two distinct issues, then you should not merge them anyway and continue to gather more feedback about them as them being diverged. If at some point you can see that they appear to be caused by one and the same issue, you should be able to 'merge' or 'forcemerge' them provided certain 'merge' preconditions are being met: http://www.debian.org/Bugs/server-control#merge Alternatively you can also use 'New upstream release - fixes issue FOO (Closes: #NNN, #MMM)' from the changelog instead or merging them. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/38b07cf6b70e39f804cf8371a751a...@spnet.net
Processed: block 663877 with 664584
Processing commands for cont...@bugs.debian.org: block 663877 with 664584 Bug #663877 [wnpp] ITP: utouch-evemu -- Tools and bindings for kernel input event device emulation, data capture, and replay. 663877 was not blocked by any bugs. 663877 was not blocking any bugs. Added blocking bug(s) of 663877: 664584 thanks Stopping processing here. Please contact me if you need assistance. -- 663877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.133219880719859.transcr...@bugs.debian.org
