Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.

[Asheesh Laroia]

On Mon, 24 Dec 2007, Charles Plessy wrote:


Le Sun, Dec 23, 2007 at 09:10:41PM +, Julien Cristau a écrit :



The problem is not bts, or tagpending, or the BTS.  The problem is that
your MTA is not configured correctly.  With exim, which you appear to be
using, see /etc/email-addresses.


Le Sun, Dec 23, 2007 at 10:18:01PM +0100, Mohammed Adnène Trojette a écrit :


And this causes bugs.debian.org to fail sender verification.
So either use an SMTP with *routeable* address or make your mailname a
routeable address.


Well, I do understand that I have a poorly configured mail server on my
machine. Indeed it is a laptop, not a mail server. Other sites accept
the test mails I send from this laptop, and since I am not a system
administrator, I strictly have no clue on what to do to get with `bts'
the same level of functionality than with `reportbug', that is:
installing it on a machine and using it "out of the box" to communicate
with the BTS.

Apparently I am wrong that the DEBEMAIL environment variable can contain
useful information which would make `bts' able to send mails that would
not be rejected by the BTS when using a default Debian instalation. I
will not bother you further and stop using tools that I can not master
because of my lack of interest and skills in the art of mailserver
configuration.


If your ISP has an SMTP server you can use as a relay, which is almost 
always the case, configuring your Exim to go through that should be fairly 
easy.  That should eliminate these purplexing issues (by offloading them 
to your ISPs' system administrators, who have alreaddy solved them!).


I hope this helps - feel free to email me privately to ask for more help.

-- Asheesh.

--
All possibility of understanding is rooted in the ability to say no.
-- Susan Sontag

Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.

[Asheesh Laroia]

On Mon, 24 Dec 2007, Charles Plessy wrote:


Le Sun, Dec 23, 2007 at 04:57:12PM -0500, Asheesh Laroia a écrit :


If your ISP has an SMTP server you can use as a relay, which is almost
always the case, configuring your Exim to go through that should be fairly
easy.  That should eliminate these purplexing issues (by offloading them
to your ISPs' system administrators, who have alreaddy solved them!).

I hope this helps - feel free to email me privately to ask for more help.


Thanks a lot for the help. The machine I use is a laptop, that goes from
network to network. Is there a way to get the right relay automatically
selected when I plug the ethernet cable ?


What I do is something you'll probably consider a lame hack, but I don't 
know a better solution:


My laptop runs an SMTP server on localhost port 25 that, when it receives 
mail, opens an SSH tunnel to a machine that *does* know it's ISP's SMTP 
server, and talks to that ISP SMTP server over the SSH tunnel.


If you do have a machine like that (a desktop, or a server shell account) 
somewhere, then I'm happy to provide more details.


Alternately, your home ISP might support sending mail through it using a 
username and password - that would be easiest; then you could configure 
your laptop's Exim to talk to your home ISP's SMTP server (or your Mail 
User Agents could talk to it).


-- Asheesh.

--
All of a sudden, I want to THROW OVER my promising ACTING CAREER, grow
a LONG BLACK BEARD and wear a BASEBALL HAT!! ...  Although I don't know WHY!!

Re: Bug#457477: devscripts: [tagpending] Did not tag the bug.

[Asheesh Laroia]

On Mon, 24 Dec 2007, Charles Plessy wrote:


Le Sun, Dec 23, 2007 at 05:11:56PM -0500, Asheesh Laroia a écrit :


My laptop runs an SMTP server on localhost port 25 that, when it receives
mail, opens an SSH tunnel to a machine that *does* know it's ISP's SMTP
server, and talks to that ISP SMTP server over the SSH tunnel.

If you do have a machine like that (a desktop, or a server shell account)
somewhere, then I'm happy to provide more details.


Indeed, I have a Debian box with a properly configured posfix server at
home :) I would be happy to here about the details.


Okay, here goes (CC:ing mentors in case this helps others).

http://www.asheesh.org/note/sysop/mail-tunnel.html

It's long, but it's fairly straightforward and I find it Extremely Worth 
It.  Here's the summary section:


Summary

* inetd listens on port 125
* Connections to it go through an SSH tunnel that executes "nc 
localhost 25" on some mail server
* (Optional) A real MTA runs on the laptop, so that I can send mail 
when offline; when mail delivery fails temporarily, Postfix queues the 
message until I get back online.


Justification

* Easy. Apps can be configured to use localhost port 25 (or port 125) 
with no password.
* Correct: Postfix (when using 25) handles sending mail when offline, 
and reattempts delivery for me.
* Secure: Encryption all the way through the network, with the icing 
on the cake that this all looks like SSH, so nosy networkers near your 
laptop can't even see that's what you're doing.


-- Asheesh.

--
It's sweet to be remembered, but it's often cheaper to be forgotten.

Re: alpine_1.0+dfsg-2_source.changes REJECTED

[Asheesh Laroia]

Dear Mentors,

I'm a Debian Maintainer now and am uploading a new release of my package 
alpine, for which I successfully uploaded 1.0+dfsg-1 to the archive.


I noticed that according to 
http://buildd.debian.org/build.php?pkg=alpine , the Debian archive 
never builds i386 packages.  To my surprise, it accepts the binary 
.debs I upload with the source package.


That sort of creeps me out - I'd much rather exercise a buildd and make 
sure that a pristine package gets into the archive.  So I thought I 
would upload a dsc containing only source.  (That dsc is available at 
http://mentors.debian.net/debian/pool/main/a/alpine/alpine_1.0+dfsg-2.dsc 
.)


However, I got this message back:

On Sat, 12 Jan 2008, Debian Installer wrote:


Rejected: source only uploads are not supported.


Dear Debian-Mentors,

Is it possible to ask the buildds to rebuild my package on all 
architectures as part of an upload?


Thanks!

-- Asheesh.

--
The herd instinct among economists makes sheep look like independent thinkers.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: alpine_1.0+dfsg-2_source.changes REJECTED

[Asheesh Laroia]

On Sat, 12 Jan 2008, Cyril Brulebois wrote:


Rejected: source only uploads are not supported.


That's exactly the point: at the moment, source-only uploads are
REJECTED. You have to provide at least the binaries for one
architecture.


Interesting.  Is there a reason for this policy, or is it just 
historical?


Is it possible to ask the buildds to rebuild my package on all 
architectures as part of an upload?


No. If you want to *rebuild* a package using the very same source 
already in the archive, you can read about binNMUs. But that only 
happens for good reasons (e.g. transitions). That's not a workaround so 
that source-only uploads can happen.


Got it, now I understand the way things work.  I still have the above 
question about why they work that way.


Thanks for the quick reply!

-- Asheesh.

--
Don't abandon hope: your Tom Mix decoder ring arrives tomorrow.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: alpine_1.0+dfsg-2_source.changes REJECTED

[Asheesh Laroia]

On Sat, 12 Jan 2008, Stefano Zacchiroli wrote:


On Sat, Jan 12, 2008 at 11:51:14AM +0100, Cyril Brulebois wrote:

ISTR it was intended to ensure the package at least builds fine in the
developer's environment, to reduce FTBFSes. I wasn't there at that time
though, but I've been told several times that I'll be an old DD before
it gets a chance to be changed. I guess you can call it historical.


The most precise reference to this issue it comes to my mind is:
http://lists.debian.org/debian-devel/2007/01/msg00760.html

In that mail it is well explained (or at least, it is explained in a way
I agree with) why we should require *also* binary packages to be
uploaded. However, it is not well motivated IMO why we shouldn't, for
example, upload them and throw them away afterwards (see footnote [4],
with which I personally disagree). The point of not having resources I'm
quite sure can be mitigated.


Stefano,

Thanks - I have read the whole 
http://lists.debian.org/debian-devel/2007/01/msg00760.html thread now, as 
well as have skimmed the debian-mentors thread another posted here.


I agree whole-heartedly with your position, which has been described by 
others here on debian-mentors and on debian-devel.  I think "Require 
binaries and throw them away" is a very good strategy.  It seems there is 
fairly wide consensus that having the buildds build every package is a 
good thing.


Have you considered making a General Resolution on the topic to create a 
policy that allows the buildds to build every package?


I realize that the "arch: all" packages would need technical attention 
before the policy can be realized in practice, and there may be other 
small technical issues to work out, but I imagine there are solutions to 
those issues.


-- Asheesh.

--
It is not a good omen when goldfish commit suicide.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: alpine_1.0+dfsg-2_source.changes REJECTED

[Asheesh Laroia]

On Sat, 12 Jan 2008, Cyril Brulebois wrote:


On 12/01/2008, Asheesh Laroia wrote:

I realize that the "arch: all" packages would need technical attention
before the policy can be realized in practice, and there may be other
small technical issues to work out, but I imagine there are solutions
to those issues.


I guess some packages might be exceptions to such a rule, like compilers
or other packages needing bootstrap at some point.


That's a good point - the simplest fair rule I can think of would be to 
make it "opt-in" by developers who *want* the buildds to rebuild their 
packages, and mark the package in a way that says "Please throw away my 
binary packages".


-- Asheesh.

--
Pause for storage relocation.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: alpine_1.0+dfsg-2_source.changes REJECTED

[Asheesh Laroia]

On Sat, 12 Jan 2008, Bernhard R. Link wrote:


* Asheesh Laroia <[EMAIL PROTECTED]> [080112 11:41]:

That's exactly the point: at the moment, source-only uploads are
REJECTED. You have to provide at least the binaries for one
architecture.


Interesting.  Is there a reason for this policy, or is it just
historical?


Sorry if this sounds rude: But how have you tested this package when
you did not have a binary package built in a suiteable environment
available?


Just to be clear, I did have the binary package built, and I did test it.


And if you have this package, why did you not include it?


I didn't want to include it because I don't want to treat the i386 
architecture specially, especially not in what I see as worse.  Users of 
the other architectures get packages built by a clean build environment 
maintained by a debian.org sysadmin, and they can read buildd logs.


So I rebuilt the package as a source-only upload after testing the binary 
package and uploaded just that in the hopes of getting the i386 package 
built by a buildd also.  (The thread at 
http://lists.debian.org/debian-devel/2007/01/msg00760.html was good 
reading for me to understand others' arguments in this.)


-- Asheesh.

--
If a man had a child who'd gone anti-social, killed perhaps, he'd still
tend to protect that child.
-- McCoy, "The Ultimate Computer", stardate 4731.3


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Sponsor for existing libapache-mod-* packages.

[Asheesh Laroia]

On Fri, 25 Jan 2008, Andreas Wenning wrote:


Hi

I have 3 packages which is unusable in lenny+sid as apache has been 
removed; I've repackaged those with support for apache2. I'm looking for 
a sponsor(s) for all three of them: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429126 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429085 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429095


Yay.  (I am not a DD so I can't sponsor.)

As the maintainers doesn't seem to be active regarding the packages, I 
am willing to take maintainership for them. But then someone should 
point me to, how this is done.


I think you should talk to the Debian QA team and see if the maintainer 
can be classified as "missing in action" (MIA).


-- Asheesh.

--
Household hint:
If you are out of cream for your coffee, mayonnaise makes a
dandy substitute.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: NMU package: bitcollider

[Asheesh Laroia]

On Tue, 4 Mar 2008, Salvatore Ansani wrote:

Hi guys, I made a new version of bitcollider package (revision: 
0.6.0-1.1).


Can I safely upload it on mentors ?? I need to respect any policy before 
upload ??

I sent an email to old mantainer but I didn't receive any response.


As I understand things, it's safe to upload it to mentors so that you can 
request comments; the harder question is how to get it from there to the 
Debian archive.


-- Asheesh.

--
A horse!  A horse!  My kingdom for a horse!
-- Wm. Shakespeare, "Henry VI"


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RFH: liblicense: dpkg-shlibdeps: failure: couldn't find library

[Asheesh Laroia]

I'm working on a package of the last release of liblicense.  The 
liblicense source package generates liblicense.so.1 in a 
liblicense1 package and a program /usr/bin/license that links to

liblicense.so.1 to do its job.

liblicense, by means of background, is a C library.  Its mission in life 
is to make it easier for developers to read and write license metadata in 
and out of media files; I'm also the upstream on it in my work at Creative 
Commons.  Every file format has a different standard for storing this 
metadata, so liblicense abstracts all that away.


(It does this by linking to other libraries like libflac and libvorbis and 
libexempi to provide a unified API for license and related metadata.  Not 
all file types or external libraries support all the metadata we want to 
support, but that's okay.)


When building this dsc 
, 
I get at the end of the build:


dpkg-shlibdeps: failure: couldn't find library liblicense.so.1 needed by 
debian/liblicense-cli/usr/bin/license (its RPATH is '').
Note: libraries are not searched in other binary packages that do not have 
any shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to set 
LD_LIBRARY_PATH.

dh_shlibdeps: command returned error code 512
make: *** [binary-arch] Error 1
dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit 
status 2


Naturally, I'm probably doing something wrong - but I have no idea what it 
is.  I think that the soname and library package name are correct, for one 
thing.  Can someone perhaps help?


(I also did the same build in a sid pbuilder, which gave me the same 
results.)


Thanks!

-- Asheesh.

--
Life is like a diaper -- short and loaded.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFH: liblicense: dpkg-shlibdeps: failure: couldn't find library

[Asheesh Laroia]

On Fri, 14 Mar 2008, Russ Allbery wrote:


Asheesh Laroia <[EMAIL PROTECTED]> writes:


When building this dsc
<http://asheesh.org/debian/pool/main/libl/liblicense/liblicense_0.5.1-1.dsc>,
I get at the end of the build:

dpkg-shlibdeps: failure: couldn't find library liblicense.so.1 needed by
debian/liblicense-cli/usr/bin/license (its RPATH is '').
Note: libraries are not searched in other binary packages that do not have
any shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to set
LD_LIBRARY_PATH.
dh_shlibdeps: command returned error code 512
make: *** [binary-arch] Error 1
dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit
status 2

Naturally, I'm probably doing something wrong - but I have no idea what
it is.  I think that the soname and library package name are correct,
for one thing.  Can someone perhaps help?


You have dh_makeshlibs commented out in your debian/rules file.  You have
to run dh_makeshlibs when building shared libraries.  Otherwise, you don't
get a shlibs file, which means that the shared library package won't work
right and dh_shlibdeps can't find it when setting shared library
dependencies.


Thanks - that fixed that problem!

Would it make sense for me to report a bug (and maybe a patch) to the 
message printed by dpkg-shlibdeps to point out this possible mistake 
(since it already points out the need for LD_LIBRARY_PATH)?


-- Asheesh.

--
May cause drowsiness.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFH: liblicense: dpkg-shlibdeps: failure: couldn't find library

[Asheesh Laroia]

On Sat, 15 Mar 2008, Charles Plessy wrote:


Le Fri, Mar 14, 2008 at 01:46:42PM -0700, Asheesh Laroia a écrit :
I'm working on a package of the last release of liblicense.  The 
liblicense source package generates liblicense.so.1 in a liblicense1 
package and a program /usr/bin/license that links to liblicense.so.1 to 
do its job.


Dear Asheesh,

I am just wondering if `license' isn't too much a dictionary word to get 
in /usr/bin. Have you considered if it is used by other programs that 
are yet not packaged ?


I actually don't know about another program that provides a 
/usr/bin/license, even not in Debian.  I honestly don't think this is a 
conflict.


I'd be happy to change my mind if someone else shows me something to 
change my mind


-- Asheesh.

--
Yes I have a Machintosh, please don't scream at me.
-- Larry Blumette on linux-kernel

More RFH: liblicense: Module symbols "found in none of the libraries"

[Asheesh Laroia]

I'm (still) working on packaging liblicense. 
http://www.mail-archive.com/debian-mentors@lists.debian.org/msg54877.html 
has the previous discussion.  Thanks to everyone who helped.  To give a 
quick summary, liblicense is a library that reads and writes license 
metadata out of e.g. MP3, Ogg Vorbis, and PDF files.  The reason for its 
existence is to let other programmers build on top of it and pretend that 
there is a unified API to the various metadata standards and formats, at 
least as far as license information.


A more current DSC is available at 
http://mentors.workaround.org/debian/pool/main/l/liblicense/liblicense_0.6-1.dsc 
.


I want to ask a particular question here:  My package (for which I am 
upstream) makes some interesting complaints from dpkg-shlibdeps after it 
builds:


dpkg-shlibdeps: warning: symbol LL_E_MODULE_WRITE_FAIL used by
debian/liblicense2/usr/lib/liblicense/0.6/io/sidecar_xmp.so found in 
none
of the libraries.
dpkg-shlibdeps: warning: symbol LL_WEBSTATEMENT used by
debian/liblicense2/usr/lib/liblicense/0.6/io/sidecar_xmp.so found in 
none
of the libraries.
dpkg-shlibdeps: warning: symbol LL_MORE_PERMISSIONS used by
debian/liblicense2/usr/lib/liblicense/0.6/io/sidecar_xmp.so found in 
none
of the libraries.

and so on.

Now, to give some background - these modules do work!  liblicense.so is 
responsible for determining e.g. what license a file claims it is under. 
As a user of liblicense, you might call ll_read() on a filename you pass 
in - liblicense detects the file type and dlopen()s a .so that handles 
files of that type.


So this /usr/lib/liblicense/0.6/io/sidecar_xmp.so file is a "module" that 
refers to symbols that are not contained in it.  That's expected by me - 
because the symbols it needs are guaranteed to be available when it is 
dlopen()'d by liblicense.so.


So what should I do?

(I'm still working on Paul Wise's advice to use Symbols Files as per 
http://wiki.debian.org/UsingSymbolsFiles 
.)


Thanks!

-- Asheesh.

P.S. It occurred to me that maybe I should link sidecar_xmp.so with 
-llicense, but that seemed curiously incestuous if liblicense.so would 
dlopen() it


--
Zippy's brain cells are straining to bridge synapses ...


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: ext3grep

[Asheesh Laroia]

On Sat, 12 Apr 2008, [EMAIL PROTECTED] wrote:


Hi world,
I am about to upload a fixed package for review, but I have a question - I 
spoke to the author of ext3grep about backtrace.cc and the other GPLv3 files, 
and he informed me that that was an oversight when he switched the license 
from GPLv3 to GPLv2, and has been corrected in Subversion.


Great!  To be clear about my remarks, I'm not a Debian Developer, but I am 
a DM and I maintain a couple of things (sometimes with man pages written 
by you!).


Is the Right Thing to do here to modify the orig.tar.gz to contain the GPLv2 
files, to have a patch modify the license headers appropriately (eww) at 
compile-time, or something else?


The most reasonable thing to do is to both:

1. Modify the files after you unpack the tarball, but before you build the 
package, and


2. Explain the reasoning for the patch in the debian/copyright 
file.


As for the kernel-jbd.h, a similar question stands. As far as I can see, the 
clearest thing to do is to have it use the kernel's jbd.h and make 
kernel-headers a Build-Depends, but that still raises the question of what to 
do about the orig.tar.gz.


Just build-depends on the kernel headers - why would you need to modify 
the orig.tar.gz for this?



I have added a correct watch file and Homepage tag to my package.


Great!


I believe including debug symbols is important here, as there are known
bugs in the software, and the upstream author's first command to anyone who 
reports a bug is to rebuild with the options included in my package, 
including debug symbols. This will save Debian users time, and help improve 
the software. :)


I agree with this sentiment for a program like this.

-- Asheesh.

--
She's the kind of girl who climbed the ladder of success wrong by wrong.
-- Mae West


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: ext3grep

[Asheesh Laroia]

On Sun, 13 Apr 2008, Carlo Wood wrote:


On Sat, Apr 12, 2008 at 08:48:33PM -0700, Asheesh Laroia wrote:

Is the Right Thing to do here to modify the orig.tar.gz to contain the
GPLv2 files, to have a patch modify the license headers appropriately
(eww) at compile-time, or something else?


The most reasonable thing to do is to both:

1. Modify the files after you unpack the tarball, but before you build
the package, and

2. Explain the reasoning for the patch in the debian/copyright file.


Imho, the right thing to do is to use ext3grep-0.6.0, which already
has GPLv2 for backtrace.*


Boy, that sounds great.  I didn't realize there wasn an updated release!

-- Asheesh.

--
There's so much plastic in this culture that vinyl leopard skin is
becoming an endangered synthetic.
-- Lily Tomlin


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: atmailopen

[Asheesh Laroia]

On Mon, 23 Jun 2008, Giuseppe Iuculano wrote:

First I tried tu use debian pear linking /usr/share/php to 
/usr/share/atmailopen/libs/PEAR, but unfortunately atmail doesn't work, 
just a white page...


Usually the PHP error log can show the problems here; perhaps you can turn 
up the debug level to get more output.


I also like to turn on PHP's display_errors in php.ini.

-- Asheesh.

--
"Protozoa are small, and bacteria are small, but viruses are smaller
than the both put together."


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Use of hfsprogs in Ubuntu

[Asheesh Laroia]

Keeping these lists in the loop by Rogerio's request.  I like keeping 
people in the loop, but I don't want to send messages where they're 
unwanted; send me a private mail if you think we should trim the CC: list.


On Fri, 27 Jun 2008, Rogério Brito wrote:


Hi, Asheesh.

First of all, thank you very much for your reply. I'm sorry that I could 
not reply earlier.


No trouble!  Long-awaited replies are the Debian Way! (-;


On Jun 21 2008, Asheesh Laroia wrote:

I got this mail because I'm on debian-powerpc.


Nice. I still have a PPC notebook (a G3 notebook) and I am keeping it until
it dies and I obviously want it to be as useful as possible.


(-:

I no longer have PPC machines, but I used to and obviously still know 
people who do (and can emulate the Free Darwin system in qemu-powerpc 
if necessary) - I would like to help maintain hfsprogs.


That is great. I would think that this would make hfsprogs be much 
better maintained if I can have some help and discussion.


Awesome.

I generally focus on Debian, but I believe Ubuntu is pretty great too 
and am using it right now.  If you'll help with the Ubuntu side I'd be 
happy to more directly contribute to that too.


I don't have problems with Ubuntu (and, in fact, I'm using a Ubuntu 
install at this exact moment to write you this e-mail, because I don't 
have access to my Debian machine right now).


I hope that we can cooperate well between Ubuntu and Debian.


I think the best thing to do is

(a) realize that the Gentoo guys are not going to break up their patch
into smaller pieces,
(b) separate it out ourselves, and
(c) hopefully get upstream to accept it.


Yes, that's exactly the thing that I had in mind. In fact, breaking up the
patch is a minor problem. It is getting newer upstream versions to compile
and work (and seeing which patches are needed under Debian) that is the
problem.


Wow, that's... interesting.

Does upstream use CVS?  If so, I honestly think we should use 
git-cvsimport and create a git repository for upstream, and then figure 
out exactly which upstream patches break the Debian/Gentoo patches.



I would like to clean up many things, like:

* the variable types that Apple uses in their code to standard types (this
 can be accomplished just by a sed/perl/awk substitution).


I think if we can hurry that patch along into upstream, that'd be great.

Might they accept it?


* the potentially non-cleanliness of 64-bit.


That'd be surprising, since Apple OS X targets 64-bit as I recall.


* the potential problems with little/big-endian machines.


Again - they have little and big endian machines now  So I'm 
surprised.



* the use of magic constants in their code.


Blah.  Would they accept patches fixing this?  (Do we want to practically 
reverse-engineer these constants?)



* the use of some ioctl's to see if they differ in Darwin and Linux (and
 other BSD systems that Debian might support).


Same question.


That's just for start.

I have, BTW, just talked with some Apple guys and it seems that they are
open to receiving patches. They are not completely open in the sense that
they allow access to their CVS/SVN/whatever repository, even of those parts
that are Free. :-(


Okay, so upstream is just releasing tarballs, and not even read access to 
their CVS/SVN/whatever tree?  So be it.



I think that the nicest way to do this would be to use a revision
control tool like git-buildpackage.  I'm very familiar with git as-is.


While I am a tiny bit familiar with git, I'm not familiar with the
*-buildpackage's that are available in Debian. So, I think that I will end
up learning things along the way.


I'm admittedly not familiar with git-buildpackage, just svn-buildpackage. 
But what we're going to do be doing basically amounts to maintaining a 
fork with the *hopes* of upstream taking some of our patches, and I think 
git is a great tool for that.  So hopefully it will make sense for the 
debian/ directory too. (-:


My sponsor for hfsprogs just had a problem with hfsprogs running under 
powerpc and she needs some help soon. BTW, it would be kind of you if 
you included her in your reply ([EMAIL PROTECTED]).


Hi!


Thoughts?


Let's work together and see a good exchanging filesystem being better 
supported under Linux!


Yes!

-- Asheesh.

--
Never insult an alligator until you've crossed the river.

Re: RFS: genwebgallery

[Asheesh Laroia]

On Fri, 4 Jul 2008, Patrick Schoenfeld wrote:


Hi,

On Wed, Jun 18, 2008 at 07:29:49PM +0200, markus schnalke wrote:

But back to `genwebgallery':

I think packages should be like programs according to the Unix
philosophy:
- small and simple
- do one thing well


I would usually agree with you, but only to some extent.
After all each package has a given overhead, needs mirror space and
bandwith. If you package is only a 200 lines shell script its just
questionable if the ratio program ./ additional needed space for the
packaging is okay. Also consider that my argumentation is not that your
utility isn't worth to be included into Debian. My argumentation is,
that it would be good to add it to another package, which includes
similar tools. This way the general overhead is reduced, mirror space
isn't excessive used and the user who would otherwise install both tools
(which is very likeley if tools are similar) would save some wasted
space, too.


Honestly, disks are cheap, and buildds don't spend a lot of time on shell 
script packages since they don't need to be built.  5 kilobytes for a .deb 
file and its source packaging is not a great burden to ask of the mirror 
operators.  (And five kilobytes is a generous estimate.)


Is this a real issue?

I don't mean to flame, but to understand and create a coherent 
perspective. (-:


-- Asheesh.

--
I am having FUN...  I wonder if it's NET FUN or GROSS FUN?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Updating Debian Package

[Asheesh Laroia]

On Mon, 25 Aug 2008, Kruti wrote:



Hi!!
Can someone suggest me some good links which will help me out to know how to
update a debian package and also how to make sure that through apt-get the
updated package only will be installed..


You should check out 
http://people.debian.org/~mpalmer/debian-mentors_FAQ.html and the New 
Maintainers Guide at http://www.debian.org/doc/maint-guide/ .


Once you have a package we can talk about how to install updates via 
apt-get.


-- Asheesh.

--
The opposite of a correct statement is a false statement. But the opposite
of a profound truth may well be another profound truth.
-- Niels Bohr


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Proposal for collaborative maintenance of packages

[Asheesh Laroia]

On Mon, 19 Dec 2005, Stephan Hermann wrote:

What you are suggesting is already there. It's called "hct" and it's 
keybuks child. So, seeing this in an environment of Ubuntu: I think (or 
I hope) hct will be included in launchpad, and then we will include some 
parts of REVU3 (I hope :)) into launchpad as well. You can read 
everything on http://wiki.launchpad.canonical.com, especially the part 
about Soyuz. For the REVU2 part, you can read the spec on 
https://launchpad.net/distros/ubuntu/+spec/revu .


hct looks very cool and does seem to solve some of the problems that are 
considered here.  When I read https://wiki.launchpad.canonical.com/HCT , I 
get the sense that it's not actually released yet.  Is that the case?  If 
not, how can one start using it?


Thanks.  I agree with the Ubuntu side of this discussion that dealing with 
non-distributed svn would be a pain; I don't have any experience with 
svnk, however.


-- Asheesh.

--
If people concentrated on the really important things in life,
there'd be a shortage of fishing poles.
-- Doug Larson


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

mdf2iso already packaged in Ubuntu Universe

[Asheesh Laroia]

A few months back, I filed the ITP Bug#310876 
.  Just as I'm finally uploading this to 
mentors.debian.net and about to look for a sponsor, I discovered that 
Lukas Fittl had packaged this in Ubuntu Universe.


Lukas, do you plan to upload it to Debian, too?  If not, um, what should 
we do for Debian users?


Thanks, all.

-- Asheesh.

--
Disobedience:  The silver lining to the cloud of servitude.
-- Ambrose Bierce


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RFS: cue2toc

[Asheesh Laroia]

I believe that file format compatibility is something Free Software should 
strive toward, and I would love to see cue2toc be sponsored!  CUE is a 
common format for describing CDs' table-of-contents.  cue2toc is a program 
to convert the common CUE file format into the TOC format that cdrdao can 
read and burn.


The package is lintian clean.  If you want to contact me on 
#debian-mentors, I'm paulproteus|lapt there.


Thanks!

-- Asheesh.

The source package is available at:

http://mentors.debian.net/debian/pool/main/c/cue2toc/cue2toc_0.4-1.diff.gz
http://mentors.debian.net/debian/pool/main/c/cue2toc/cue2toc_0.4.orig.tar.gz
http://mentors.debian.net/debian/pool/main/c/cue2toc/cue2toc_0.4-1.dsc

Binary for i386 Sarge at:

http://paulproteus.acm.jhu.edu/debian/cue2toc_0.4-1_i386.deb

Here's the info from the ITP (Bug #346443):

* Package name: cue2toc
  Version : 0.4
  Upstream Author : Matthias Czapla <[EMAIL PROTECTED]>
* URL : http://cue2toc.sourceforge.net/
* License : GPL
  Description : converts CUE files to cdrdao's TOC format

 cue2toc from http://cue2toc.sourceforge.net/ has features that include support
 for complete set of CUE commands (e.g. catalog number, data and audio tracks,
 ISRC codes, CD-Text,  Pre-/Postgaps (with zero data or data from file),
 subindexes etc.), automatic determination of session type and conversion of
 data files by user configurable commands based on file name extension
 matching.

--
Body by Nautilus, Brain by Mattel.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: cue2toc

[Asheesh Laroia]

On Mon, 9 Jan 2006, Kapil Hari Paranjape wrote:


Dear Sheesh,

There is a cue2toc that is included with cdrdao (in the etch version of 
cdrdao) is this the same/better?


I've spoken with asuffield, the cdrdao maintainer.  It appears the cdrdao 
upstream distributes an old version of cue2toc, and asuffield is perfectly 
happy to move the program to its own package.


We agreed that I should file this bug 
 so he would 
remove cue2toc from the cdrdao package.


-- Asheesh.

--
No one becomes depraved in a moment.
-- Decimus Junius Juvenalis


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Extra debian repository

[Asheesh Laroia]

On Sat, 14 Jan 2006, Bas Wijnen wrote:

You should somehow sign your own archive and add your public key to 
apt's keyring (I'm guessing it's in /usr/share/keyrings or 
/usr/share/apt).  I haven't done anything like that though, but I 
suppose the internet can tell you a bit more. :-)


http://wiki.debian.org/SecureApt is the canonical current documentation on 
apt authentication.


-- Asheesh.

--
Chance is perhaps the work of God when He did not want to sign.
-- Anatole France


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RFC: Packaging converters from ${format} to ISO

[Asheesh Laroia]

I want to package mdf2iso and b5i2iso, two small utilities that convert 
proprietary programs' CD image formats into the normal ISO format that 
cdrecord and Linux's iso9660 filesystem accept.  There are at least half a 
dozen such utilities that would be useful.


I could:

* create ITPs for all of these and create separate source packages 
for each of them, or


* create a single source package e.g. "all2iso" that creates separate
  binary packages for each of the utilities, or

* create a single source package that creates a single binary package for
  all of these.

Note that, after compiling for i386, each of the programs is under 20 
kilobytes.  I'd appreciate advice on which of these is the best way to go.


Thanks!

-- Asheesh.

--
Predestination was doomed from the start.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Problem compiling new upstream version, what to do?

[Asheesh Laroia]

On Tue, 17 Jan 2006, Stan Vasilyev wrote:

I'm trying to package the new version of xdialog: Xdialog-2.1.2. The 
upstream tarball doesn't compile on my system. When I run configure and 
make I get:


RANLIB@: Command not found

I found a way to fix that error by running autogen.sh in the source tree.
Should I repackage the upstream tarball or email the upstream author about
this problem?


I'm no DD, but can't you just run autogen.sh and put the difference in 
your .diff.gz like any other patch?  I get this failure, too, so you 
probably should contact upstream about it.


-- Asheesh.

--
Tomorrow, this will be part of the unchangeable past but fortunately,
it can still be changed today.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to 'su' to root from a script using Xdialog?

[Asheesh Laroia]

On Tue, 21 Mar 2006, Michelle Konzack wrote:

I like to have a Dialog which tell the $USER: "This programm requires 
root permission. Please enter the password:"


GNOME programs tend to use "gksu" for this.  You might find it would be 
appropriate for you to use in your program, too.  KDE provides "kdesu" for 
the same purpose.  Note that gksu, at least, does support using sudo to 
get root if the user has the ability to sudo.


Alternately, you could just prompt the user via a dialog you write, but 
then you'll have to be sure that it doesn't leak the root password by 
having it show up in command-line arguments or other generally visible 
areas.


-- Asheesh.

--
Maryann's Law:
You can always find what you're not looking for.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kqemu package

[Asheesh Laroia]

On Mon, 10 Apr 2006, Colin Tuckley wrote:


Adam Borowski wrote:

The problem is, you are not allowed to distribute kqemu.  So, the only 
thing you will be legally permitted to do with your package will be 
installing it on any number of machines under your control.


Why not? According to the sourceforge web sites both kqemu and kommander 
are GPL'd


I think there is confusion between http://kqemu.sourceforge.net/ and 
http://fabrice.bellard.free.fr/qemu/qemu-accel.html .


-- Asheesh.

--
If you permit yourself to read meanings into (rather than drawing meanings out
of) the evidence, you can draw any conclusion you like.
-- Michael Keith, "The Bar-Code Beast", The Skeptical Enquirer Vol 12 No 4 p 416


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: proper way to package mozilla extensions

[Asheesh Laroia]

On Mon, 24 Apr 2006, Yaroslav Halchenko wrote:


1. There are two possible packaging schemes
 a. Keep only original .xpi in the .orig.tar.gz, and extract/dpatch it
at build time.

 b. Keep unzipped .xpi in .orig.tar.gz.

 I was going the b. way but now I think that keeping original .xpi
 would be better


I'm no DD, but I would say (a) is nicer because then a checksum can be 
verified more easily.


-- Asheesh.

--
Never drink coke in a moving elevator.  The elevator's motion coupled with
the chemicals in coke produce hallucinations.  People tend to change into
lizards and attack without warning, and large bats usually fly in the
window.  Additionally, you begin to believe that elevators have windows.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: optional building of a package

[Asheesh Laroia]

On Sat, 3 Jun 2006, Charles Plessy wrote:

However, I was wondering wether it would make sense to provide to the 
Debian user a mean to install the extra programs from the Debian 
sources. Is there a way to make the source package able to produce a 
probcons-extra package, but only optionaly?


On the other hand, it could simply build a probcons-extra package by 
default, with a clear description saying that it is likely that 
probcons-extra will not be useful to the persons tempted to install it.


I think the second approach makes more sense to me as an end-user.  As I 
see it, the Debian Way isn't to have all sorts of USE flags and 
compile-time options, but instead to provide those options to users of 
binary packages.


-- Asheesh.

--
When God created two sexes, he may have been overdoing it.
-- Charles Merrill Smith


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RFS: ccd2iso (ITP #373150)

[Asheesh Laroia]

ccd2iso is a program to convert CloneCD images to normal .iso CD image 
files.  It's helpful for users who have made CloneCD images of discs that 
they want to use in a Free OS.


I've packaged it and would like comments or (preferably!) someone to 
sponsor this upload.  It's lintian and Linda clean.


I want to add that there are a lot of these little *2iso programs, and 
most of them are dead upstream because they are simple, well-tested 
programs that are complete.  Someone on #debian-mentors suggested 
rewriting them in Perl in one package, but I'd rather avoid that because 
these tools are well-tested by upstream authors invested in their 
correctness, plus programs like k3b expect the binaries to take certain 
arguments.  I worked with a friend to create a man page for this program.


Here's the info from the ITP:

* Package name: ccd2iso
  Version : 0.2
  Upstream Author : Danny Kurniawan <[EMAIL PROTECTED]>
* URL : http://sourceforge.net/projects/ccd2iso/
* License : GPL
  Description : Converter from CloneCD disc image format to standard ISO

This converts CD backup files created using the non-free CloneCD program 
to a format understood by most Free Software CD writing programs.


Homepage: http://sourceforge.net/projects/ccd2iso/

-- Asheesh.

Source package elements at:

http://paulproteus.acm.jhu.edu/debian/ccd2iso_0.2-1.diff.gz
http://paulproteus.acm.jhu.edu/debian/ccd2iso_0.2-1.dsc
http://paulproteus.acm.jhu.edu/debian/ccd2iso_0.2.orig.tar.gz

--
The trouble with being punctual is that people think you have nothing more
important to do.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: ccd2iso (ITP #373150)

[Asheesh Laroia]

On Sat, 17 Jun 2006, Alec Berryman wrote:


Asheesh Laroia on 2006-06-17 15:03:22 -0400:

I want to add that there are a lot of these little *2iso programs, and 
most of them are dead upstream because they are simple, well-tested 
programs that are complete.  Someone on #debian-mentors suggested 
rewriting them in Perl in one package, but I'd rather avoid that 
because these tools are well-tested by upstream authors invested in 
their correctness, plus programs like k3b expect the binaries to take 
certain arguments.


Forget rewriting them, how about just aggregating them into one package?


Well, I considered that, but I didn't think there was an approach that was 
beneficial.


Here's one way to do it: Talk to the upstream maintainers and get them to 
collaborate and distribute a huge meta-tarball.  But as I've said, 
upstreams for these consider them "finished", so they'd just as much 
rather not spend more time.  And when one such project updates to fix a 
bug, someone would


Here's another: I could aggregate them myself.  If so, I would end up 
making that big meta-tarball myself.  That would complicate the "watch" 
file, but more importantly if other distributions want to re-use the 
packaging work, it's now much harder to see which changes affect which 
programs.  If I choose to actually copy the *.c and *.h files out into a 
fake upstream tarball I maintain, it makes any patches or changes even 
more opaque.  Also, if one has a bugfix upstream, I'd have to regenerate 
the meta-tarball that's my fake "orig.tar.gz".


And would this mean generating multiple binary packages or just one?  If 
multiple binaries, I don't see the advantage of aggregating them all into 
a single source package; if there is a single binary package, then I worry 
it makes it harder for users to find the specific (and perhaps single) 
program that they need.


It seems that with all these questions, the easier and more comprehensible 
approach to me is to simply package each one individually.  I welcome 
others' thoughts on the topic, of course.


-- Asheesh.

--
When Marriage is Outlawed, Only Outlaws will have Inlaws.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: ccd2iso (ITP #373150)

[Asheesh Laroia]

On Sat, 17 Jun 2006, Laszlo Boszormenyi wrote:


Hi Asheesh,
Sounds good to have this.


Hi!  Thanks for the quick reply!


Anyway, the package may use debhelper compatibility level 5, but that
would make Sarge backports a very bit 'harder'.


Right, I think it's better to use debhelper compatibility level 4 for that 
reason.


The latest Policy-Version is 3.7.2, please recheck your package against 
it.


I debian/control to say "Standards-Version: 3.7.2".  Lintian and Linda 
still have nothing to say (-:.


Also I don't know if it matters, but if its GPL-2 licensed, then the 
license path has the '-2' postfix.


It does appear to be "or any later version", so I've made that clearer in 
debian/copyright.


Also, I dislike to use DEB_HOST_GNU_TYPE and DEB_BUILD_GNU_TYPE, but 
others may override my opinion.


I've kept that from debhelper's dh_make, and it seems fine to me.  If 
there are substantive reasons why this should be changed, do please tell 
me.


For the watch file you may better use: 
http://qa.debian.org/watch/sf.php?project=foobar foobar-([\d.]*).tar.gz


I've fixed that, too.


It looks OK otherwise.


Thanks!

-- Asheesh.

--
I call them as I see them.  If I can't see them, I make them up.
-- Biff Barf


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: ccd2iso (ITP #373150)

[Asheesh Laroia]

On Sat, 17 Jun 2006, Laszlo Boszormenyi wrote:


On Sat, 2006-06-17 at 15:57 -0400, Alec Berryman wrote:

Forget rewriting them, how about just aggregating them into one
package?


Sounds better. I mean to one binary with switches like 
--from= and --to= .


My main objection is that this makes the Debian experience different than 
in other distributions.  Programs like k3b that rely on these small 
utilities are easier when they act the same on every platform (bugfixes 
aside), and I would feel bad making their jobs harder.


It also means that the manual page for the super-meta-package would be 
long and complicated, full of program-specific caveats like the "mount" 
man page.


It doesn't seem worth it to make both developers' and end-users' lives 
harder.  (It also makes my life harder, since I'd have actually wrap them 
all up, but I'll mention that last and least.)


-- Asheesh.

--
Envy, n.:
Wishing you'd been born with an unfair advantage,
instead of having to try and acquire one.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: use of xvfb-run in pbuilder builds

[Asheesh Laroia]

On Tue, 4 Jul 2006, Carlo Segre wrote:

I suppose that I will have to figure out how to install all the 
requirements at run time or just give in and permanently install X on my 
chroots.


Isn't this what build dependencies are for?

-- Asheesh.

--
Counting in octal is just like counting in decimal--if you don't use your 
thumbs.
-- Tom Lehrer


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#377420: mod-bt - FTBFS: Not resolvable build dependencies

[Asheesh Laroia]

On Sun, 9 Jul 2006, Tyler MacDonald wrote:


But if I have to remove the "apr1 | apr0" sutff, then a new version of
mod-bt (and every other apache2 module) will be neccessary when the switch
to 2.2 happens.


In theory you could just switch the order of apr1 | apr0.  But I agree 
that this is less than desired.


-- Asheesh.

--
Be sure each item is properly endorsed.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[RFC] alpine - Friendly text-based email client (Bug #401001)

[Asheesh Laroia]

I'm working on packaging the Alpine mail client, an Apache License 2.0 
release of the popular PINE mail and news reader.  I'm very happy to see 
this great (both powerful and friendly) MUA be Free.


Upstream bundles an editor called PICO, originally the PIne COmposer.  I 
wanted to ask for comments on the way I handled making two binary 
packages: basically I do "make install" with CURDIR set to alpine, and I 
just "mv" the pico binary and man page out into the CURDIR for 
alpine-pico.  The "pico" binary and man page are separated because "nano" 
also has a pico man page and binary; that way, only alpine-pico conflicts 
with nano.


There's only one other significant change: The build system prompts the 
user interactively if to enable IPv6 support, so I commented out the 
question and enabled it.


Otherwise, this is a straightforward package.  I'd love to hear comments 
on this "revision 0" package.


The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/a/alpine
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/a/alpine/alpine_0.8-0.dsc

Thanks!

-- Asheesh.

--
Carelessly planned projects take three times longer to complete than expected.
Carefully planned projects take four times longer to complete than expected,
mostly because the planners expect their planning to reduce the time it takes.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [RFC] alpine - Friendly text-based email client (Bug #401001)

[Asheesh Laroia]

Quick side question resulting from off-list discussions:

This package conflicts with (custom-built) pine packages many people have 
been using.  Okay if I make alpine "Conflicts: pine" and "Replaces: pine"?


Also, I think it would be useful if /usr/bin/pine were a symlink to 
/usr/bin/alpine?  Old-time users might expect just "pine" to work.  Okay 
to do that?


-- Asheesh.

--
She was good at playing abstract confusion in the same way a midget is
good at being short.
-- Clive James, on Marilyn Monroe


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [RFC] alpine - Friendly text-based email client (Bug #401001)

[Asheesh Laroia]

On Tue, 5 Dec 2006, Daniel Baumann wrote:


http://mentors.debian.net/debian/pool/main/a/alpine/alpine_0.8-0.dsc


 * you're modifying imap/Makefile without notice in the changelog


Fixed.


 * it's normal to write debhelper with a version, such as
   debhelper (>= 4), and list it as the first build-depends.


Done.


 * outdated standards-version.


Fixed; bumped to 3.7.2.


 * Homepage: http://www.washington.edu/alpine/ should have two leading
   spaces.


Done.


 * your upstream url is not valid.


I fixed that in debian/copyright.


 * s/Copyright/License/ in copyright, and add the
   'Copyright (C) $year $copyright_holder' line.


Done.


 * remove the useless commented stuff in rules and watch


Cleaned.


 * remove the binary-indep stuff, you don't build arch: all packages


Cleaned, too.  I had to keep the rule in there or otherwise lintian would 
complain, but the rule does nothing now.



 * remove the useless dh_* calls


They're gone.


 * do not use two or more empty lines as seperator in rules, one is
   just enough.


Fixed.


 * remove the empty lines at the end of watch


Fixed.


the rest looks good. if you change above things, i'll sponsor it.


I also tested it in a pbuilder, where it installed fine.  I had to add 
some build-depends to get that to happen.  I also added "${misc:Depends}" 
to the Depends line of the packages as per discussion on this list.


Let me know what you think now.  I've bumped the revision number to 1. 
I've held off from the other proposed changes (i.e., no symlink to "pine", 
and no "conflicts: pine" nor "replaces: pine") pending further discussion. 
I think this makes a fine 0.8-1 package.


The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/a/alpine
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/a/alpine/alpine_0.8-1.dsc

Thanks!

-- Asheesh.

--
There is no such thing as inner peace.  There is only nervousness or death.
Any attempt to prove otherwise constitutes unacceptable behaviour.
-- Fran Lebowitz, "Metropolitan Life"


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [RFC] alpine - Friendly text-based email client (Bug #401001)

[Asheesh Laroia]

On Wed, 6 Dec 2006, Daniel Baumann wrote:


 * versioned depends are commonly written as: foo (>= 1.2.3), not
   foo (>=1.2.3).


Changed.


 * rules contains still a useless dh_* call (dh_installexamples to be
   precise).


Fixed.

Tell me what you think now of the package as it is hosted on 
mentors.debian.net:


- URL: http://mentors.debian.net/debian/pool/main/a/alpine
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/a/alpine/alpine_0.8-1.dsc

-- Asheesh.

--
Try to have as good a life as you can under the circumstances.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Packages (using C++) for two different distributions

[Asheesh Laroia]

On Wed, 20 Dec 2006, Kasper Peeters wrote:


So the question is: what is the easiest way for me to generate
packages for two distributions with incompatible C++ ABIs, given that
I have only one machine?


I'm not a Debian developer, but I would think the easiest thing to do is 
to install pbuilder and create a chroot for Debian.  Since the source 
package will be the same (libgmp-dev, I'd guess) for both, you can use 
pbuilder to generate the Debian package in a chroot.


pbuilder is fairly straightforward; its man page should be documentation 
enough.


-- Asheesh.

--
"Go on, girl!  You'll never get a better chance to buy Jif at this
price.  *Carpe diem*, babe!"
-- "The Naked Consumer", Erik Larson


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: What to do if my package doesn't build on some architecture

[Asheesh Laroia]

On Fri, 19 Jan 2007, Kumar Appaiah wrote:


I have come across an unexpected (serious), bug in my package libitpp,
that it doesn't build on s390. Check http://bugs.debian.org/407555


[snip]


Besides, I don't have access to such a machine!


You can emulate an s390 using the package Hercules.  See 
http://www.debian-administration.org/articles/484 for some discussion of 
that.  Unfortunately the debian-administration article here tells you how 
to install Woody, but the comments describe how to boot the Debian 
installer and install a more recent system.


-- Asheesh.

--
Stanford women are responsible for the success of many Stanford men:
they give them "just one more reason" to stay in and study every night.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: cwiid -- Linux interface to the Wiimote

[Asheesh Laroia]

On Thu, 8 Feb 2007, Romain Beauxis wrote:


Le vendredi 19 janvier 2007 15:30, Romain Beauxis a écrit :

Hi mentors !


Hi again !

Just another request for sponsoring.. If any one could have time to
review/uplaod this package it would be great !


I'm looking for a sponsor for this package:

* Package name    : cwiid
  Version         : 0.3.51
  Upstream Author : L. Donnie Smith <[EMAIL PROTECTED]>
* URL             : http://www.wiili.org/index.php/CWiid
* License         : GPL
  Programming Lang: C
  Description     : Linux interface to the Wiimote

 CWiid is a working userspace driver along with various
 applications implementing event drivers, multiple wiimote
 connectivity, gesture recognition, and other Wiimote-based
 functionality.

The binary packages are a library, its development files, and two binaries.
ITP number is #407468

You can find the package at this place:
http://www.rastageeks.org/~toots/cwiid/


The .dsc is at http://www.rastageeks.org/~toots/cwiid/cwiid_0.5.00-1.dsc . 
I'm not the packager but I'm just an interested prospective user. (-:


-- Asheesh.

--
There is no such thing as fortune.  Try again.

Re: From local source tree to Debian package

[Asheesh Laroia]

On Tue, 20 Mar 2007, Ben Finney wrote:

Writing a bunch of 'cp' or 'install' commands in the 'debian/rules' file 
seems like drudgery and is certainly prone to error. What tools are 
there to assist Debian packagers in making this task more automated?


Well, "make install" typically puts them somewhere - see the use of CURDIR 
in the new maintainers guide, like at 
http://www.debian.org/doc/maint-guide/ch-dreq.en.html .


Does that help some?  You should check out 
http://www.debian.org/doc/maint-guide/ if you haven't yet.


-- Asheesh.

--
You have an ability to sense and know higher truth.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: List of (un)sponsored packages on Mentors (approximate)

[Asheesh Laroia]

On Sun, 22 Jul 2007, Ondrej Certik wrote:

The actual discussion came up when we talked about whether the current 
GR on non-DDs with upload permissions is good or bad for Debian. And we 
agreed that Debian lacks a lot of packages just because the poor 
package maintainer (tm) didn't find a sponsor in time.


Yes, that is the most difficult part. I think it would also help, if 
there was some official repository for unnoficial packages, so that I 
(as non-DD) could just upload my package to mentors (which I can now) 
and then just add the "deb" line (not just "deb-src") into sources.list 
and could easily use all packages from mentors (at least on i386). 
Because now everyone has it's own private repository, which I find very 
unfortunate.


I find it easy enough to do:

$ sudo apt-get update
$ apt-src -bi install $package

apt-src will then "install" the source of the package into the current 
working directory, then "b"uild it, and then "i"nstall the resulting 
binaries.


This works just fine for me with the deb-src mentors line.

-- Asheesh.

--
If you steal from one author it's plagiarism; if you steal from
many it's research.
-- Wilson Mizner


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: using boost headers

[Asheesh Laroia]

On Sat, 18 Aug 2007, Carlo Segre wrote:

One of my packages uses the boost headers and distributes them in the 
original tarball.  I have been modifying the configuration scripts to ignore 
the local copy and use the libboost-dev dependency instead.  Since these are 
headers and not real libraries, would it violate policy for me to revert to 
the version included in the tarball?  Upstream prefers to continue 
distribution in the tarball and it would avoid having to continually patch 
the configuration scripts.


I haven't checked Policy, but if there's a chance that the headers will be 
for version X whereas the system libboost is version Y, and they're not 
API-compatible, then that would be Bad.


-- Asheesh.

--
Q:  How many Harvard MBA's does it take to screw in a light bulb?
A:  Just one.  He grasps it firmly and the universe revolves around him.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: piwva

[Asheesh Laroia]

On Tue, 21 Aug 2007, Paul Wise wrote:


On 8/21/07, Henrik Andreasson <[EMAIL PROTECTED]> wrote:


   Section : mail

...

piwva  - addon to pine to allow easy download/display of attachments


pine is not in main, so you should change the section to contrib/mail.


This program presumably works with alpine, which is a Free Software update 
of pine and is in main, however.  (I happen to maintain alpine.)


-- Asheesh.

--
[FORTRAN] will persist for some time -- probably for at least the next decade.
-- T. Cheatham


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: piwva

[Asheesh Laroia]

On Tue, 21 Aug 2007, Paul Wise wrote:


On 8/21/07, Asheesh Laroia <[EMAIL PROTECTED]> wrote:


This program presumably works with alpine, which is a Free Software update
of pine and is in main, however.  (I happen to maintain alpine.)


Hmm, perhaps pine-tracker should be removed from non-free then and
alpine should grow some transition packages for lenny? Have you
discussed this with the pine/pine-tracker maintainer?


The idea so far has been that until alpine reaches the stability of pine 
and the features of the Debian pine packages (which include some patches 
that I'm talking to the maintainers of for alpine support and licensing 
permission), we would keep both alpine and pine.  I haven't talked about 
transition packages because this step hasn't come yet, but I hope we will 
talk about that soon.


I'm definitely working on the above-mentioned issues with alpine, and many 
Debianites have helpfully filed Debian bugs against my package that have 
gone to help upstream improve the program.


-- Asheesh.

P.S. I got your note about 
http://www.debian.org/MailingLists/#codeofconduct , specifically if to 
"reply to all" or just the list.  Thanks for the clear link!


--
"The hands that help are better far than the lips that pray."
-- Robert G. Ingersoll


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: xvattr

[Asheesh Laroia]

On Wed, 29 Aug 2007, Venkatesh Srinivas wrote:


Dear mentors,

I am looking for a sponsor for my package "xvattr".

* Package name: xvattr
 Version : 1.3-1
 Upstream Author : Björn Englund <[EMAIL PROTECTED]>
* URL : http://freshmeat.net/projects/xvattr/
* License : GNU GPL
 Section : x11

It builds these binary packages:
xvattr - Get/set XVideo Attributes


Venkatesh,

I see at 
http://packages.ubuntu.com/cgi-bin/search_packages.pl?searchon=names&version=all&exact=1&keywords=xvattr 
that this package is already in Ubuntu.  Have you talked with the Ubuntu 
maintainer about putting it Debian?


-- Asheesh.

--
Envy is a pain of mind that successful men cause their neighbors.
-- Onasander

Re: speed of COW directory copying: XFS 20x slower than ext3

[Asheesh Laroia]

On Sun, 16 Sep 2007, Ondrej Certik wrote:


I am using cowbuilder for building my packages, because the
initialization takes like 10s, compared to several minutes with
pbuilder on my system. A few days ago, I realized that on one of my
systems, it takes 0.5s only to copy the COW directory. I became
curious and wanted to know why, so I did a benchmarking [1] and to my
utter surprise, it turned out the problem is in the XFS filesystem,
that is 20x slower, than the ext3 filesystem. I know that XFS is bad
at handling small files, but 20x times?

Basically, what cowbuilder is doing is just those 2 commands:

cp -al /var/cache/pbuilder/base.cow /tmp/new
rm -rf /tmp/new


Does this possibly have to do with buffer flushing choices by the 
filesystem?  Maybe xfs syncs after some operations (like rm -rf) that ext3 
does not.


Try adding 'sync' after both steps and see if that changes performance.

-- Asheesh.

--
  An Irishman is never at peace except when he's fighting.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Building a package for a web application

[Asheesh Laroia]

On Mon, 17 Sep 2007, liran tal wrote:


While attempting to run dpkg-buildpackage to create a .deb package of the
current directory
where I'm at I'm receiving the error message:

dpkg-genchanges: failure: cannot read files list file: No such file or
directory

my debian/ directory reads the following files:

-rw-r--r-- 1 liran liran  126 2007-09-16 10:52 changelog
-rw-r--r-- 1 liran liran  526 2007-09-17 01:57 control
-rw-r--r-- 1 liran liran  461 2007-08-22 02:39 copyright
-rw-r--r-- 1 liran liran   17 2007-09-16 10:58 dirs
-rwxr-xr-x 1 liran liran 1432 2007-09-16 09:49 postinst
-rwxr-xr-x 1 liran liran  535 2007-09-16 03:41 postrm
-rwxr-xr-x 1 liran liran  438 2007-09-16 05:11 preinst
-rw-r--r-- 1 liran liran 2410 2007-09-16 09:50 README
-rwxr-xr-x 1 liran liran   23 2007-09-16 20:56 rules
-rw-r--r-- 1 liran liran  336 2007-09-16 09:52 watch


where as the rules file is actually empty (filled with #)


An empty rules file won't get you where you want to go.

Take a look at the debian/rules file for some existing web application; 
there are many in Debian these days.  See if you can find one very similar 
to the one you want to package.


If you're more generally confused, you should check out the New 
Maintainers Guide .


-- Asheesh.

--
You know, Callahan's is a peaceable bar, but if you ask that dog what his
favorite formatter is, and he says "roff! roff!", well, I'll just have to...


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mentors.debian.net reloading

[Asheesh Laroia]

On Fri, 26 Oct 2007, Christoph Haas wrote:


Regarding CPU-intensive QA tests (builds and piuparts runs): I think
that it's very important to do them on mentors.


Might be helping the sponsor to determine if the package builds. But I'm
not sure if it's worth it. Just my personal opinion.


I don't think that resources are a problem: nobody said that you _had_
to host mentors yourself.


It is a rented virtual root server with enough power and 1 TB of free
traffic that I pay for from my spare money. I think it would be able to
do that if needed.

I might get you wrong but to me you sound more like "If you are
incapable of running the service properly then let someone else step up"
instead of "I think that test builds are important. If you agree but
don't have the proper resources I can perhaps offer some computing
power.". Sorry if my emotion chip got you wrong.


I would like to briefly comment that if you want some compute time for 
something lke this, let me know.  I see above that you think you should be 
okay, but should that ever change let me know; I'd be very happy to donate 
my spare cycles to making package sponsoring work better.


I'm personally very much a fan of automatic testing/building of packages.

-- Asheesh.

--
I am not now, nor have I ever been, a member of the demigodic party.
-- Dennis Ritchie


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mentors.debian.net reloading

[Asheesh Laroia]

On Fri, 26 Oct 2007, Christoph Haas wrote:


On Fri, Oct 26, 2007 at 03:47:09PM +0200, Ondrej Certik wrote:

The sources:
http://svn.debian.org/wsvn/collab-qa/svnbuildstat/?rev=0&sc=0
The wiki page:
http://wiki.debian.org/svnbuildstat


I believe Debian needs the same as Ubuntu has: Personal Package
Archives, where new maintainers could upload their source packages and


Agreed.


the service will automatically build and check the package.


Everybody suddenly seems to think that yet another buildd is a great
idea. Why is it?


Every once in a while, people post to debian-mentors about their package 
failing to build on the buildd for some architecture they don't have 
access to.  It'd be nice to get automated complaints about that before 
buildd time.


This does not need to be part of the "core" Debian Mentors architecture; 
someone could just automatically grab all the .dsc files and spend CPU 
cycles emulating every architecture we have and building some packages and 
posting the log.  (I'm willing to use my cycles for that, for example.)


-- Asheesh.

--
Nothing is as simple as it seems at first
Or as hopeless as it seems in the middle
Or as finished as it seems in the end.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Need help with a watch file

[Asheesh Laroia]

On Tue, 6 Nov 2007, Michael Biebl wrote:


Hi everyone,

I've got some troubles creating a working watch file for kdesvn.
Upstream uses version numbered subdirectories.

http://www.alwins-world.de/programs/download/kdesvn/

Currently the latest version is
http://www.alwins-world.de/programs/download/kdesvn/0.14.x/kdesvn-0.14.0.tar.bz2

I tried to use a match for the sub directory, as the uscan man page
claims that this is supported:
http://www.alwins-world.de/programs/download/kdesvn/(.)/kdesvn-(.*).tar.bz2


Don't you mean 
http://www.alwins-world.de/programs/download/kdesvn/(.*)/kdesvn-(.*).tar.bz2 
instead?



Unfortunately this fails.


Note the extra '*' in my version.  Does that fix things?


Has anyone an idea how I can construct a valid watch file?
An alternative html page would be
http://kdesvn.alwins-world.de/wiki/DownLoads
linking to the latest release. Unfortunately the CMS creates dumb links
like http://kdesvn.alwins-world.de/downloads/16.


What a drag.

-- Asheesh.

--
"I'm not a god, I was misquoted."
-- Lister, Red Dwarf


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Using Linda

[Asheesh Laroia]

On Sat, 15 Dec 2007, David Schulberg wrote:


Hi All,



Posted originally to debian-user and it was suggested I post here in
particular:







Have just set up Linda or I thought I had.

When I run 'linda package.deb' I get errors as follows:



debian:/home/david/Desktop/Downloads# linda checkinstall_1.6.1-1_i386.deb

Linda: Running as root, dropping to nobody.


The problem is caused by you running linda as root.

Run linda as user 'david' instead and you'll probably be fine.

-- Asheesh.

--
I have no doubt that it is a part of the destiny of the human race,
in its gradual improvement, to leave off eating animals.
-- Thoreau


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: alpine_0.999999+dfsg-2_i386.changes REJECTED

[Asheesh Laroia]

Dear Mentors:

I'm a Debian Maintainer now (not a DD, just the new separate status) and 
I'm trying to figure out why my upload was rejected.  Here's the message I 
sent to an @ftpmaster.debian.org address, but maybe some of you can help?


Thanks!

-- Asheesh.

On Sat, 15 Dec 2007, Asheesh Laroia wrote:


On Sat, 15 Dec 2007, Debian Installer wrote:


Rejected: dm:[EMAIL PROTECTED] may not upload/NMU source
package alpine


I believe that the latest alpine in unstable (namely 0.99+dfsg-1)
has me as the maintainer, me listed as the Maintainer:, and
DM-Upload-Allowed: yes in the source section of the control file.

Everything in the upload was done with the [EMAIL PROTECTED] ID of my
key 0x70096AD1; nothing mentions the new [EMAIL PROTECTED] ID.
I don't understand why this was rejected.  Can you help me understand
this so my future uploads as a Debian Maintainer are not rejected?

I'm emailing because I believe I'm doing everything correctly per
http://www.debian.org/vote/2007/vote_003 .  Thanks!

-- Asheesh.

--
Everything that you know is wrong, but you can be straightened out.





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: alpine_0.999999+dfsg-2_i386.changes REJECTED

[Asheesh Laroia]

On Sat, 15 Dec 2007, Neil Williams wrote:


Asheesh Laroia wrote:

Dear Mentors:

I'm a Debian Maintainer now (not a DD, just the new separate status) and
I'm trying to figure out why my upload was rejected.  Here's the message
I sent to an @ftpmaster.debian.org address, but maybe some of you can help?



$ gpg --list-key 70096AD1
pub   1024D/70096AD1 2005-12-28
uid          Asheesh Laroia <[EMAIL PROTECTED]>
uid      Asheesh Laroia <[EMAIL PROTECTED]>
uid  Asheesh Laroia <[EMAIL PROTECTED]>
sub   2048g/3214EBED 2005-12-28

You need to edit your key so that the UID that you use is the primary
UID. GnuPG may simply be using whichever UID was created first.

Use:

$ gpg --edit-key 70096AD1

uid 3
primary
save

$ gpg --send-key 70096AD1


I see, okay!  Thanks. (-:


To see the effect, do:
$ gpg --recv-key 28bcb3e3
$ gpg --list-key 28bcb3e3


Got it.


My debian.org UID is at the top of the list when it was actually created
after all the others because the key is (naturally) older than my DD status.

Listing your key shows the rejected UID at the top of the list.


Rejected: dm:[EMAIL PROTECTED] may not upload/NMU source
package alpine


Everything in the upload was done with the [EMAIL PROTECTED] ID of my
key 0x70096AD1;


Not really. The primary UID determines that and gpg currently has that
set to the creativecommons UID.


Great, this is a real help!  I've --send-key'd with the updated key.

The only question is, what do I do now so that the ftpmaster.debian.org 
machines will accept my uploads?


-- Asheesh.

--
It would be nice to be sure of anything the way some people are of everything.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: alpine_0.999999+dfsg-2_i386.changes REJECTED

[Asheesh Laroia]

On Sat, 15 Dec 2007, Adeodato Simó wrote:


* Asheesh Laroia [Sat, 15 Dec 2007 12:31:49 -0800]:


I believe that the latest alpine in unstable (namely 0.99+dfsg-1)
has me as the maintainer, me listed as the Maintainer:, and
DM-Upload-Allowed: yes in the source section of the control file.


The DM-Upload-Allowed field must be first introduced by a version
uploaded by a DD. That is, you'll need 0.99+dfsg-1 sponsored, and
then you'll be able to upload regularly. Make sure you use
XS-DM-Upload-Allowed in debian/control, and not just DM-Upload-Allowed.


Where is XS-DM-Upload-Allowed documented?  I only see DM-Upload-Allowed 
documented at http://www.debian.org/vote/2007/vote_003 .


If there's more canonical documentation on this to read somewhere, I'm 
happy to follow a link. (-:


-- Asheesh.

--
Take your Senator to lunch this week.

Re: alpine_0.999999+dfsg-2_i386.changes REJECTED

[Asheesh Laroia]

On Sat, 15 Dec 2007, Adeodato Simó wrote:


* Neil Williams [Sat, 15 Dec 2007 20:58:50 +]:


$ gpg --list-key 70096AD1
pub   1024D/70096AD1 2005-12-28
uid  Asheesh Laroia <[EMAIL PROTECTED]>
uid  Asheesh Laroia <[EMAIL PROTECTED]>
uid      Asheesh Laroia <[EMAIL PROTECTED]>
sub   2048g/3214EBED 2005-12-28



You need to edit your key so that the UID that you use is the primary
UID. GnuPG may simply be using whichever UID was created first.


Please, pretty please, consider refraining from giving advice when
you're not positive you're correct. (Hint: you don't sign with UIDs, so
dak could not care less about what the primary UID is.)


Oh, well, at least I've made a cosmetic change to my key that I like. (-:

-- Asheesh.

--
The world is coming to an end ... SAVE YOUR BUFFERS!!!

Bug#680141: RFS: liblastfm/0.4.0~git20090710-2 [RC]

[Asheesh Laroia]

I'm concerned by the following lintian warnings on mentors,
which I can reproduce locally:

W: liblastfm-fingerprint0: hardening-no-fortify-functions 
usr/lib/x86_64-linux-gnu/liblastfm_fingerprint.so.0.4.0
W: liblastfm0: hardening-no-fortify-functions 
usr/lib/x86_64-linux-gnu/liblastfm.so.0.4.0

Other than that, this seems reasonable so far!



--
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/1341424965-sup-4...@rose.makesad.us

Bug#680141: This seems fine to upload

[Asheesh Laroia]

John Stamp, can you clear the debdiff with the release team in an email to 
debian-release? Just email them the debdiff and ask if that would be okay, 
and if they say yes, I will upload this.


(If you already have a sponsor lined up, then that's fine, too.)

Thanks!



--
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/alpine.deb.2.00.1207051709350.32...@rose.makesad.us

Re: automatic removal of packages from mentors

[Asheesh Laroia]

On Thu, 19 Jul 2012, Bart Martens wrote:


Hi supp...@mentors.debian.net,

I understand that packages must be removed from mentors, because disk 
space is not infinite.  I have heard from multiple people requesting 
sponsorship that one of the reasons to remove packages is that no 
sponsor was found within 20 weeks.  However, some of the removed 
packages have an open RFS with recent comments.  Can you send a copy of 
the automatic notification to the RFS ?  Can you also check the age of 
the most recent comment on the RFS before removing the package ? Also, 
it would be nice that packages for which the packager does not respond 
to review comments within a reasonable time are removed first, so that 
packages waiting for a first review can remain at mentors for a bit 
longer than 20 weeks.  Of course, I understand that at some point you 
must also remove packages waiting for a first review due to lack of disk 
space.


Personally, I believe we shouldn't delete these packages from mentors 20 
weeks later.


To archive them out of the UI is something that would make sense to me.

Curious to hear the thoughts of the current mentors.debian.net 
maintainers, especially on the reasoning behind the deletion, so I can 
better understand and see if I can come up with an alternative I like 
more.


I'm typing this quickly, so if it comes out curt, pardon me! I mean to 
also send warm regards to the hard-working people who make 
mentors.debian.net go forward.


-- Asheesh.


--
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/alpine.deb.2.00.1207191944560.13...@rose.makesad.us

Bug#682519: Still looking for sponsor?

[Asheesh Laroia]

Hi there,

I'm a Debian Developer and possibly interested in reviewing and sponsoring 
this! Are you still looking?


Cheers,

-- Asheesh.


--
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/alpine.deb.2.02.1209271430140.19...@rose.makesad.us

Bug#682519: Quick notes

[Asheesh Laroia]

First of all, let me say thank you for beginning the work to package 
this in Debian!


Wow... this is a solid package:

* You have a man page.

* It's lintian clean.

* /usr/bin/fbcmd doesn't have a .php extension.

How did you even manage to make such an excellent package!?

I can't find anything terribly wrong with it.

A few questions:

* You embed a copy of a jsonwrapper PHP module in 
/usr/share/fbcmd/facebook/jsonwrapper. Should that be in PEAR? and/or does 
fbcmd work with PHP's built-in JSON stuff? Just trying to minimize 
dependencies, especially embedded copies of them.


* A few scripts seem not useful for Debian users, namely: 
/usr/share/fbcmd/fbcmd_update.php /usr/share/fbcmd/support/test_php.php -- 
should those simply not be installed?


* Why does 'man fbcmd' not mention LOADINFO but 
/usr/share/fbcmd/support/sample-loadinfo-text.php does?


* Is /usr/share/doc/fbcmd/filelist.txt relevant to Debian users?

This is looking great. Great work on the copyright file, too. Hope you can 
answer those questions, and again amazing work.


-- Asheesh.


--
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/alpine.deb.2.02.1210010337200.19...@rose.makesad.us

Re: orig tarball in conflict with debian policy

[Asheesh Laroia]

On Sat, 21 Feb 2009, Michael Rasmussen wrote:


Hi all,

What is the proper way of dealing with a orig tarball where both naming
and internal structure is in conflict with debian policy?

Especially the internal structure is a problem since it prevents using
the dh-tools in debian.

example:
orig tarball: foo-y.y.z.tgz
internal structure: foo\...


Really a backslash?

If you mean it's a forward slash, the Debian tools handle this case more 
gracefully than you might expect, I think. Go forward and act as if 
nothing's wrong, and when you have a problem, be specific about what 
it is.


-- Asheesh.

--
Q:  Why does Washington have the most lawyers per capita and
New Jersey the most toxic waste dumps?
A:  God gave New Jersey first choice.


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFS: python-clips

[Asheesh Laroia]

On Mon, 1 Feb 2010, Pablo Recio Quijano wrote:


--Dear mentors,

I am looking for a sponsor for my package "python-clips".

* Package name: python-clips
 Version : 1.0.7.348-1
 Upstream Author : Francesco Garosi, fran...@infinito.it
* URL : http://sourceforge.net/projects/pyclips/
* License : LGPL
 Section : python

It builds these binary packages:
python-clips - Python module for using CLIPS,

The package appears to be lintian clean.

The upload would fix these bugs: 544706

My motivation for maintaining this package is: I want to contribute with the
free software community the best way I can, and maintain this package is a
good
way to do it.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/p/python-clips
- Source repository: deb-src http://mentors.debian.net/debian unstable main
contrib non-free
- dget
http://mentors.debian.net/debian/pool/main/p/python-clips/python-clips_1.0.7.348-1.dsc

I would be glad if someone uploaded this package for me.


Hi! This is great that you're interested in working on it. I'm personally 
too busy to mentor you or provide an upload, but have you thought about 
joining the Debian Python packaging team?


-- Asheesh.

--
The herd instinct among economists makes sheep look like independent thinkers.


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Just sponsored my first package

[Asheesh Laroia]

I just wanted to announce gleefully to this list: I just sponsored my 
first package, miredo.


A few years ago, this list helped me find sponsors for the packages I 
wanted to contribute to Debian. People on the list taught me about being a 
friendly mentor and a detailed critic of packages. Now I'm a Debian 
developer and I can return the favor.


Debian is fun. Thanks, all, for helping build the Free World.

-- Asheesh.

--
All of life is a blur of Republicans and meat!


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Experimental release for IPv6 patched package?

[Asheesh Laroia]

On Fri, 5 Feb 2010, Mats Erik Andersson wrote:


Dear mentors,

I have taken to addressing the lack of IPv6-support for tftpd from 
netkit-tftp-0.17 (see #536509). As far as I can tell it seems to work on 
my machine, including format 3.0-quilt.


Would I be correct in guessing that the experimental release should be 
the first entry point for alterations like the Debian IPv6 goal?


I am asking out of principle, since I will try to find the official 
maintainer before I take any actions.


I don't see why you'd use experimental rather than unstable. I'd suggest 
setting the release to unstable rather than experimental. Doubly true 
since IPv6 is a release goal.


Others, feel free to say why I'm wrong.

Naturally, if this isn't your package, talk to the maintainer. But you 
already said you would do that. (-:


-- Asheesh.

--
Anyone who imagines that all fruits ripen at the same time
as the strawberries, knows nothing about grapes.
-- Philippus Paracelsus


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFS: ceph

[Asheesh Laroia]

On Fri, 5 Feb 2010, Sage Weil wrote:


Hello,

I am looking for a sponsor for ceph.  Ceph is a distributed object store 
and file system designed for scalability, reliability, and performance. 
The kernel module for mounting the file system is planned for inclusion 
in 2.6.34.


Hi! That's one awesome package. I'm very busy of late, but I hope you're 
looking into DebianMaintainer status -- have you read 
http://wiki.debian.org/DebianMaintainer ?


It'd be perfect for your situation as you're the upstream as well.

It's most helpful for this list if you post a link to a .dsc file you want 
us to review.


-- Asheesh.

--
Any circuit design must contain at least one part which is obsolete, two parts
which are unobtainable, and three parts which are still under development.


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFS: ceph

[Asheesh Laroia]

On Sat, 6 Feb 2010, Sage Weil wrote:


On Sat, 6 Feb 2010, Asheesh Laroia wrote:

On Fri, 5 Feb 2010, Sage Weil wrote:

Hello,

I am looking for a sponsor for ceph.  Ceph is a distributed object store and
file system designed for scalability, reliability, and performance. The
kernel module for mounting the file system is planned for inclusion in
2.6.34.


Hi! That's one awesome package. I'm very busy of late, but I hope you're
looking into DebianMaintainer status -- have you read
http://wiki.debian.org/DebianMaintainer ?

It'd be perfect for your situation as you're the upstream as well.


I was actually looking at the New Maintainer/Debian Developer process, but
becoming a Debian Maintainer would also serve my immediate purposes for
this package.  Ultimately I hope to be able to build and upload new
versions of the package when they are released, but finding a sponsor is
the first step.  I've spent a fair amount of time putting the package
together, but I'm sure there are issues or improvements that can be made.


For your package, I'll take a look right now. Some feedback:

First of all, you've made it a native package. 
http://people.debian.org/~mpalmer/debian-mentors_FAQ.html covers that. 
Debian etiquette prefers that you separate your packaging metadata 
(debian/*) from the rest of the source.


An explanation: "The problem is that at some point, upstream's debian 
directory will deviate from the one in the Debian package -- because the 
maintainer changes, the directory was already outdated, or someone does an 
NMU or a security upload. The .diff.gz will now be a diff between the two 
debian dirs, which is very confusing." 
<http://people.debian.org/~mpalmer/debian-mentors_FAQ.html>


(Honestly I think Debian should work on improving the situation for 
upstream maintainers who want to put debian/* in their version control 
systems, but right now I suggest separating them out. Since you're using 
git, one thing you can do is keep a separate git branch with your debian/ 
directory, and ship your standard release tarballs without it.)


The package begins to build fine in a clean sid i386 pbuilder, but the 
build ends in errors. See my attached text file for the end of the log. 
Feel free to ask me for help setting up a pbuilder if you run into trouble 
with it.


You're also missing a Debian version number, like 
ceph-0.18git20100204164957-1.


I'm also interested in becoming a Debian Developer.  My company, 
DreamHost web hosting, is a long time debian user, and we maintain a 
large number of packages internally that could be contributed upstream 
(perl modules and such).  One way or another, I'd like to see the 
packaging work we do internally get contributed back to the community.


Awesome!

My personal process for becoming a Debian developer was that I maintained 
some packages and got sponsors via this list, and while I was doing that I 
applied for DebianMaintainer status and Debian Developer status at the 
same time. DM status came much more quickly, which helped me get my 
packages uploaded faster while I was waiting for DD status.


So that's what I suggest for everyone these days.

Both DM and DD require a recommendation (advocacy) from someone who has 
worked with you. If I sponsor your packages, I'm happy to write a note for 
either or both.


-- Asheesh.mkdir -p /tmp/buildd/ceph-0.18git20100204164957/usr/include/rados
/bin/bash /tmp/buildd/ceph-0.18git20100204164957/install-sh -c -m 0644 
osdc/librados.h /tmp/buildd/ceph-0.18git2010
0204164957/usr/include/rados/librados.h
mkdir -p /tmp/buildd/ceph-0.18git20100204164957/usr/include/crush
/bin/bash /tmp/buildd/ceph-0.18git20100204164957/install-sh -c -m 0644 
crush/hash.h /tmp/buildd/ceph-0.18git2010020
4164957/usr/include/crush/hash.h
/bin/bash /tmp/buildd/ceph-0.18git20100204164957/install-sh -c -m 0644 
crush/crush.h /tmp/buildd/ceph-0.18git201002
04164957/usr/include/crush/crush.h
/bin/bash /tmp/buildd/ceph-0.18git20100204164957/install-sh -c -m 0644 
crush/types.h /tmp/buildd/ceph-0.18git201002
04164957/usr/include/crush/types.h
/bin/bash /tmp/buildd/ceph-0.18git20100204164957/install-sh -c -m 0644 
crush/mapper.h /tmp/buildd/ceph-0.18git20100
204164957/usr/include/crush/mapper.h
make[4]: Leaving directory `/tmp/buildd/ceph-0.18git20100204164957/src'
make[3]: Leaving directory `/tmp/buildd/ceph-0.18git20100204164957/src'
make[2]: Leaving directory `/tmp/buildd/ceph-0.18git20100204164957/src'
Making install in man
make[2]: Entering directory `/tmp/buildd/ceph-0.18git20100204164957/man'
make[3]: Entering directory `/tmp/buildd/ceph-0.18git20100204164957/man'
make[3]: Nothing to be done for `install-exec-am'.
test -z "/usr/share/man/man8" || /bin/mkdir -p 
"/tmp/buildd/ceph-0.18git20100204164957/usr/share/man/man8"
 /usr/bin/install -c -m 644 cosd.8 cmds.8 cmon.8 mkcephfs.8 mkmonfs.8 cf

Re: RFS: ooo-thumbnailer

[Asheesh Laroia]

On Sat, 6 Feb 2010, David D Lowe wrote:


Dear mentors,

I am looking for a sponsor for the new version 0.2-3 of my package
"ooo-thumbnailer".

It builds these binary packages:
ooo-thumbnailer - thumbnailer for OpenOffice.org documents

I'm the upstream author. The work is licensed under the GPL v2 or
higher. My motivation in maintaining this package is to see
OpenOffice.org documents, spreadsheets and presentations thumbnailed
alongside PDFs. Windows has this feature, why shouldn't Debian? All it
takes is a simple bash script.

I followed Jakub Wilk's advice and improved the package since 0.2-1.
I've removed build dependencies on Python, removed unofficial fields
from debian/control, and removed a redundant dependency on
graphics-imagemagick-compat. The package appears to be lintian clean.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/o/ooo-thumbnailer
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget
http://mentors.debian.net/debian/pool/main/o/ooo-thumbnailer/ooo-thumbnailer_0.2-1.dsc


404 Not Found

Presuming you meant 
http://mentors.debian.net/debian/pool/main/o/ooo-thumbnailer/ooo-thumbnailer_0.2-3.dsc 
and continuing with review...


Well, it builds clean in a pbuilder! Pretty simple package. Let me try 
it


I installed it, and it doesn't seem to thumbnail my spreadsheet in 
Nautilus. Maybe I need to restart Nautilus? /me tries that


Oh SWEET! There we go. (-:

Can you make a note explaining that in README.Debian?

Also, I'm just wondering: why did you remove the dependency on "bash"? 
Maybe I'm being silly, but I figure it does really depend on it.


(Other Debian mentors -- is it okay to upload a package whose version is 
0.2-3 or 0.2-4 as the first Debian upload? Or should we instead rewrite 
history and pretend this is 0.2-1 when it's ready to go?)


So far, so good -- keep me posted about those two questions, and once I'm 
satisfied, I'll foist this upon the NEW queue.


-- Asheesh.

--
I'm having a BIG BANG THEORY!!


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFS: ooo-thumbnailer

[Asheesh Laroia]

On Sat, 6 Feb 2010, Christoph Egger wrote:


On Sat, Feb 06, 2010 at 03:48:08PM -0500, Asheesh Laroia wrote:


Also, I'm just wondering: why did you remove the dependency on
"bash"? Maybe I'm being silly, but I figure it does really depend on
it.


bash is Essential and you don't explicitely depend on essential
packages but assume it's there anyway.


bash is still Essential? Man, that's lame. (-;

(Other Debian mentors -- is it okay to upload a package whose version 
is 0.2-3 or 0.2-4 as the first Debian upload? Or should we instead 
rewrite history and pretend this is 0.2-1 when it's ready to go?)


	There are some of the sponsors around demanding to increase the 
debian version for every change of a package that hit mentors and others 
that want a version just after the one in the archive.


So either way is okay, then.

-- Asheesh.

--
Parents often talk about the younger generation as if they didn't have
much of anything to do with it.


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFS: ooo-thumbnailer

[Asheesh Laroia]

On Sat, 6 Feb 2010, David D Lowe wrote:


On Sat, 2010-02-06 at 15:48 -0500, Asheesh Laroia wrote:

Presuming you meant
http://mentors.debian.net/debian/pool/main/o/ooo-thumbnailer/ooo-thumbnailer_0.2-3.dsc
and continuing with review...


Yes, indeed, my mistake.


Well, it builds clean in a pbuilder! Pretty simple package. Let me try
it

I installed it, and it doesn't seem to thumbnail my spreadsheet in
Nautilus. Maybe I need to restart Nautilus? /me tries that

Oh SWEET! There we go. (-:

Can you make a note explaining that in README.Debian?


Will do.


Also, I'm just wondering: why did you remove the dependency on "bash"?
Maybe I'm being silly, but I figure it does really depend on it.


Jakub Wilk (not a DD) recommended I do so. I quote: "Dependency on 'bash
(>=3)' could be dropped, as even oldstable has the requested version of
bash, and bash is essential."


Agreed -- leave out that dependency.

Ping debian-mentors when you've updated README.Debian!

And keep 
http://wiki.debian.org/DebianMaintainer#AdvocatingaDebianMaintainer in 
mind; I'd love to advocate you for DM status once we get to know each 
other well enough.


-- Asheesh.

--
We can defeat gravity.  The problem is the paperwork involved.


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: README.Debian updated

[Asheesh Laroia]

On Sun, 7 Feb 2010, David D Lowe wrote:


On Sat, 2010-02-06 at 21:51 -0500, Asheesh Laroia wrote:

Ping debian-mentors when you've updated README.Debian!


I've updated README.Debian, you can get the new version at:
- URL: http://mentors.debian.net/debian/pool/main/o/ooo-thumbnailer
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/o/ooo-thumbnailer/ooo-thumbnailer_0.2-4.dsc

I'm excited about finally getting this into Debian!


*Almost*

A few lintian warnings:

paulprot...@renaissance:~/pbuilder/result/sid-i386 $ lintian ooo*deb
W: ooo-thumbnailer: extra-license-file usr/share/doc/ooo-thumbnailer/COPYING.gz
W: ooo-thumbnailer: debian-changelog-line-too-long line 2
W: ooo-thumbnailer: debian-changelog-line-too-long line 5
W: ooo-thumbnailer: extra-license-file usr/share/doc/ooo-thumbnailer/COPYING.gz

Sorry to not mention these before -- can you give them a look?

Don't forget to look into DebianMaintainer status so you can keep shipping 
this (although, from the length of the script, it's almost hard to imagine 
you'll have any bugs).


-- Asheesh.

--
Now that I have my "APPLE", I comprehend COST ACCOUNTING!!


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFS: ceph

[Asheesh Laroia]

On Mon, 8 Feb 2010, Sage Weil wrote:


On Sat, 6 Feb 2010, Asheesh Laroia wrote:

For your package, I'll take a look right now. Some feedback:

First of all, you've made it a native package.


Fixed this up (after finally sorting out the difference between - and _ 
in the filename).  Also fixed up the debian version (missing in 
changelog).


Great.




The package begins to build fine in a clean sid i386 pbuilder, but the build
ends in errors. See my attached text file for the end of the log. Feel free to
ask me for help setting up a pbuilder if you run into trouble with it.


I'm having trouble getting pbuilder working; trying on another machine
now.  And it's not clear to me from the output you sent where those
warnings are coming from.  I'll continue to play with in.


rebuilding! I'll go to sleep now, though, I think. Hopefully I'll say 
something about this in the morning.


As for your pbuilder stuff, feel free to paste me errors, or find me on 
IRC; I'm paulproteus on OFTC and FreeNode.


pbuilder can be a pain to set up. Don't be too easily discouraged. And 
you'll need sudo, in my experience; I haven't had much luck with setting 
up pbuilders with fakechroot and other tricks.


-- Asheesh.

--
Happiness isn't having what you want, it's wanting what you have.


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFS: ttf-aoyagi-soseki (Japanese brush font package)

[Asheesh Laroia]

On Wed, 10 Feb 2010, Hideki Yamane wrote:


Dear mentors,

I am looking for a sponsor for my package "ttf-aoyagi-soseki".

* Package name: ttf-aoyagi-soseki
 Version : 20070207-1
 Upstream Author : 青柳衡山 (Kouzan Aoyagi) 
   and 青柳疎石 (Soseki Aoyagi)
* URL : http://musashi.or.tv/aoyagisosekifont.htm
* License : Free (public domain)
 Section : fonts

It builds these binary packages:
ttf-aoyagi-soseki - Brush-style Japanese font


I hope someone from the Debian Fonts Task Force picks this up! I'm swamped 
currently.


-- Asheesh.

--
"There... I've run rings 'round you logically"
-- Monty Python's Flying Circus

Re: README.Debian updated

[Asheesh Laroia]

On Wed, 10 Feb 2010, David D Lowe wrote:


On Tue, Feb 9, 2010 at 4:37 AM, Asheesh Laroia  wrote:

*Almost*

A few lintian warnings:

paulprot...@renaissance:~/pbuilder/result/sid-i386 $ lintian ooo*deb
W: ooo-thumbnailer: extra-license-file
usr/share/doc/ooo-thumbnailer/COPYING.gz
W: ooo-thumbnailer: debian-changelog-line-too-long line 2
W: ooo-thumbnailer: debian-changelog-line-too-long line 5
W: ooo-thumbnailer: extra-license-file
usr/share/doc/ooo-thumbnailer/COPYING.gz

Sorry to not mention these before -- can you give them a look?


A few of those are warnings for older versions of ooo-thumbnailer, I
think, as I don't get them any more. Careful with the wildcards!


Oops!


I've uploaded a new version of ooo-thumbnailer to mentors.debian.net,
with these changes:
- I removed COPYING from debian/docs, eliminating the
extra-license-file warning.
- I updated Standards-Version to 3.8.4.0

This package can be found at:
- URL: http://mentors.debian.net/debian/pool/main/o/ooo-thumbnailer
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/o/ooo-thumbnailer/ooo-thumbnailer_0.2-5.dsc



Don't forget to look into DebianMaintainer status so you can keep shipping
this (although, from the length of the script, it's almost hard to imagine
you'll have any bugs).


I'll look into it as soon as this package gets approved. Thanks for
encouraging me to do this, I wouldn't have considered it otherwise.


I just uploaded it to ftp-master!

-- Asheesh.

--
Maslow's Maxim:
If the only tool you have is a hammer, you treat everything like
a nail.


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: init script versosity

[Asheesh Laroia]

On Wed, 10 Feb 2010, PICCA Frédéric-Emmanuel wrote:


Hello

I am using the /etc/init.d/skeleton (from unstable) file to write my 
package init scripts.


but it seems that the lsb-base default behaviour is to have VERBOSE=no

so there is no output. Is it ok with the debian-policy

9.4 Console messages from init.d scripts

they say :

"This section describes the formats to be used for messages written to 
standard output by the /etc/init.d scripts."


but the next lines says "should" and not "must" when describing the init 
script output message.


so what must I do for my init scripts. VERBOSITY / no VERBOSITY ?


I'm not deeply familiar with this section of policy -- but is this 
supposed to be about separating stdout vs stderr?


If you don't get a conclusive answer here, asking your question on 
debian-devel might make sense.


-- Asheesh.

--
And on the seventh day, He exited from append mode.

Re: RFS: libzeep

[Asheesh Laroia]

On Wed, 10 Feb 2010, Maarten L. Hekkelman wrote:


Dear mentors,

I am looking for a sponsor for my package "libzeep".

* Package name: libzeep
 Version : 1.0-1
 Upstream Author : me (Maarten L. Hekkelman)
* URL : http://www.cmbi.ru.nl/
* License : boost
 Section : libs

It builds these binary packages:
libzeep-dev - Library to create SOAP server software in c++
libzeep1   - Library to create SOAP server software in c++

My motivation for maintaining this package is: I'm the original author.
And this package is used by several of my other projects which I hope
to submit to Debian soon.


I can't review this during this week, but it'd be great if you'd link to 
them, too, in the thread.


In a fortnight I'll be freer, so if you still lack a sponsor please 
re-ping the list!


-- Asheesh.

--
Scientists are people who build the Brooklyn Bridge and then buy it.
-- William Buckley


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFS: zynjacku

[Asheesh Laroia]

On Thu, 11 Feb 2010, Jaromír Mikeš wrote:


Dear mentors,

I am looking for a sponsor for my package "zynjacku".

* Package name: zynjacku
 Version : 5.2-1
 Upstream Author : Nedko Arnaudov 
* URL : http://download.gna.org/zynjacku/


http://home.gna.org/zynjacku/ is a more appropriate link for this section. 
It looks like a cool package -- I hope you get a sponsor! If not, I'll be 
freer in a fortnight. Re-ping the list then.


-- Asheesh.

--
Q:  Why did the programmer call his mother long distance?
A:  Because that was her name.

Re: RFS: wpasupplicant (updated package)

[Asheesh Laroia]

On Thu, 11 Feb 2010, Kel Modderman wrote:


Hi mentors,

I am looking for a sponsor for the new version 0.6.10-1 of the package 
"wpasupplicant". It has been a long time since its last update due to 
myself travelling and the rest of pkg-wpa-devel maintenance group being 
inactive. The inactive members have since removed themselves from the 
group which leaves us/me in need of a good mentor/sponsor.


Well, golly. Since you've worked with them for a while, can you ask them 
to sponsor you for DebianMaintainer status? See 
http://wiki.debian.org/DebianMaintainer - it's a quick way to make sure 
you have permission to upload these packages so that you don't have to go 
through the hurdles of sponsorship.


For now, I've taken a look at your package. It seems to not build properly 
in a sid pbuilder; can you try that? I'm happy to help you set up a 
pbuilder of your own so you can find these issues quickly.


Here's the error messages I get toward the end of the build.

make[4]: Entering directory `/tmp/buildd/wpasupplicant-0.6.10/src/wps'
for d in ; do make -C $d clean; done
rm -f *~ *.o *.d
make[4]: Leaving directory `/tmp/buildd/wpasupplicant-0.6.10/src/wps'
rm -f *~
make[3]: Leaving directory `/tmp/buildd/wpasupplicant-0.6.10/src'
rm -f core *~ *.o *.d eap_*.so wpa_supplicant wpa_passphrase wpa_cli 
wpa_supplicant.exe wpa_cli.exe wpa_passphrase.exe win_if_list.exe 
eapol_test preauth_test

rm -f wpa_priv
make[2]: Leaving directory 
`/tmp/buildd/wpasupplicant-0.6.10/wpa_supplicant'

dh_auto_clean --sourcedirectory=wpa_supplicant/wpa_gui-qt4 \
  --buildsystem=qmake
dh_auto_clean: unable to load build system class 'qmake': Can't locate 
Debian/Debhelper/Buildsystem/qmake.pm in @INC (@INC contains: /etc/perl 
/usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 
/usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 
/usr/local/lib/site_perl .) at (eval 10) line 2.

BEGIN failed--compilation aborted at (eval 10) line 2.

make[1]: *** [override_dh_auto_clean] Error 2
make[1]: Leaving directory `/tmp/buildd/wpasupplicant-0.6.10'
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit 
status 2


-- Asheesh.

--
I'm always looking for a new idea that will be more productive than its cost.
-- David Rockefeller


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFS: ceph

[Asheesh Laroia]

On Tue, 9 Feb 2010, Sage Weil wrote:


On Tue, 9 Feb 2010, Asheesh Laroia wrote:

On Mon, 8 Feb 2010, Sage Weil wrote:

I'm having trouble getting pbuilder working; trying on another machine
now.  And it's not clear to me from the output you sent where those
warnings are coming from.  I'll continue to play with in.


rebuilding! I'll go to sleep now, though, I think. Hopefully I'll say
something about this in the morning.


Ok, the build is fixed (man_MANS vs dist_man_MANS in the man/Makefile.am),
and pbuilder is behaving fine on my other box.  The updated .dsc is at

http://ceph.newdream.net/debian/dists/unstable/main/source/ceph_0.18git20100209082702-1.dsc


eek, have no spare time while prepping for a PyCon talk and 
conference.freeculture.org this weekend. Ping me in 10 days?


Sorry to disappear.

-- Asheesh.

--
Poverty must have its satisfactions, else there would not be so many poor
people.
-- Don Herold


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFS: zynjacku

[Asheesh Laroia]

On Thu, 11 Feb 2010, Jaromír Mikeš wrote:


Od: Asheesh Laroia 



> * Package name: zynjacku


It looks like a cool package -- I hope you get a sponsor! If not, I'll be 
freer in a fortnight. Re-ping the list then.


Hello,

It would be great if you can upload zynjacku for me ...

best regards

mira


Sorry -- not yet. Super busy. Ask again in another 10 days or so.

-- Asheesh.

--
Sic transit gloria mundi.
[So passes away the glory of this world.]
-- Thomas `a Kempis

Re: RFS: slgtk -- FTBFS fix, new uploader

[Asheesh Laroia]

On Tue, 23 Feb 2010, Jörg Sommer wrote:


Dear mentors,


I was just reviewing this, but it seems uploaded. Hooray!

In the future, try to email the list so we know that. (-:

Congratulations, and welcome to DM-Upload-Allowed!

-- Asheesh.

--
"I don't like spinach, and I'm glad I don't, because if I liked it I'd
eat it, and I just hate it."
-- Clarence Darrow

Re: RFS: zynjacku

[Asheesh Laroia]

On Sun, 21 Feb 2010, Jaromír Mikeš wrote:


Od: Asheesh Laroia 



> * Package name: zynjacku


Sorry -- not yet. Super busy. Ask again in another 10 days or so.

-- Asheesh.

Hello there,

Nobody was uploaded zynjacku package yet.
So it would be nice if you can do it for me.


Some feedback for you:

During the build process, I get this message:

dpkg-gencontrol: warning: unused substitution variable ${python:Versions}

It'd be great if you'd ask about that on #debian-python -- I have to run 
for now, but they say it might be important since you're using 
python-central.


Why Python 2.5 and earlier? I'm looking at debian/pyversions -- I'm not 
much of a Debian Python person, but I understand we're moving up to Python 
2.6.


Maybe Python 2.5 is okay for modules with C extensions, like yours? I 
haven't been keeping up to date -- I hope you can reply answering this 
question to save me the time. (-;


The manual page description says:

   This manual page documents briefly the zynjacku

and the paragraph abruptly ends there. Maybe you can just delete that 
first half-written paragraph?


That's what I have for now!

-- Asheesh.

--
Debian Hint #39: Want to download a package without installing it? Use
'aptitude download '.

Re: RFS: ceph

[Asheesh Laroia]

On Tue, 2 Mar 2010, Sage Weil wrote:


On Thu, 11 Feb 2010, Asheesh Laroia wrote:

On Tue, 9 Feb 2010, Sage Weil wrote:

Ok, the build is fixed (man_MANS vs dist_man_MANS in the man/Makefile.am),
and pbuilder is behaving fine on my other box.  The updated .dsc is at

http://ceph.newdream.net/debian/dists/unstable/main/source/ceph_0.18git20100209082702-1.dsc


eek, have no spare time while prepping for a PyCon talk and
conference.freeculture.org this weekend. Ping me in 10 days?


Hi Asheesh,

I've rebuilt packages for the latest release (0.19.1).  The .dsc is at

http://ceph.newdream.net/debian/pool/ceph-stable/c/ceph/ceph_0.19.1-1.dsc

I've also futzed around with my scripts for building .debs for the
ceph.newdream.net repository (now using pbuilder, reprepro).  I suspect
I'm not quite doing the right thing wrt package versions for the different
distributions (I'm appending something like ~bpo50+1 for lenny .deb,
etc.), but for now at least it works well enough for the separate
repository.  And I'm not sure it's that important from the perspective of
getting the packages in sid anyway.

There is also a ceph-kclient package with the source code for the kernel
module:

http://ceph.newdream.net/debian/pool/ceph-stable/c/ceph-kclient/ceph-kclient_0.19.1-1.dsc

As I understand it there is some make-kpkg magic that is supposed to build
it automagically (if it's properly packaged) but I haven't found any good
documentation on how that should be done for standalone modules.


I'm behind on this, but I hope to look again deeper by Monday evening.

-- Asheesh.

--
Democracy is a form of government in which it is permitted to wonder
aloud what the country could do under first-class management.
-- Senator Soaper


--
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/alpine.deb.2.00.1003062000521.28...@localhost

Re: RFS: recoverjpeg (updated package)

[Asheesh Laroia]

On Tue, 2 Mar 2010, William Vera wrote:


Dear mentors,

I am looking for a sponsor for the new version 2.0-1
of my package "recoverjpeg".

It builds these binary packages:
recoverjpeg - tool to recover JPEG images from a filesystem image


I suggest trying to find a sponsor in the debian-forensics mailing 
list / group.


If not, ping this debian-mentors list again in 10-15 days or so

-- Asheesh.

--
He who hesitates is sometimes saved.


--
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/alpine.deb.2.00.1003062003410.28...@localhost

Re: Regarding GSoC

[Asheesh Laroia]

On Mon, 8 Mar 2010, Sukhbir Singh wrote:


Hello everyone.

I am interested in participating in Google Summer of Code this year and 
have a project that pertains to the distribution of Debian over 
BitTorrent.This is somewhat a solution to the problem posted on the Idea 
List page ( 
http://wiki.debian.org/SummerOfCode2010/RobustBitTorrentInfrastructure)


I had written a technical paper about it, which explains in detail as to 
how content distribution can be maximized in a BitTorrent download.


I won't say that it would be the solution to all your distribution 
problems, but yes - if implemented, Debian would be able to reduce some 
of the downtime/ congestion it suffers when using BitTorrent CDN.


If any mentor is interested, I can send over the paper; it has the idea 
explained in detail. After that, we can proceed accordingly.


That sounds cool. Can you email a link to the paper to this list? You 
might also check with the debian-mirrors list to see if people there find 
it interesting.


-- Asheesh.

--
Lisp is a programmable programming language.
-- John Foderaro, [3]CACM, September 1991


--
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/alpine.deb.2.00.1003081615580.22...@localhost

Re: RFS: ceph

[Asheesh Laroia]

On Sat, 6 Mar 2010, Asheesh Laroia wrote:


On Tue, 2 Mar 2010, Sage Weil wrote:


On Thu, 11 Feb 2010, Asheesh Laroia wrote:

On Tue, 9 Feb 2010, Sage Weil wrote:
Ok, the build is fixed (man_MANS vs dist_man_MANS in the 
man/Makefile.am),

and pbuilder is behaving fine on my other box.  The updated .dsc is at

http://ceph.newdream.net/debian/dists/unstable/main/source/ceph_0.18git20100209082702-1.dsc


eek, have no spare time while prepping for a PyCon talk and
conference.freeculture.org this weekend. Ping me in 10 days?


Hi Asheesh,

I've rebuilt packages for the latest release (0.19.1).  The .dsc is at

http://ceph.newdream.net/debian/pool/ceph-stable/c/ceph/ceph_0.19.1-1.dsc

I've also futzed around with my scripts for building .debs for the
ceph.newdream.net repository (now using pbuilder, reprepro).  I suspect
I'm not quite doing the right thing wrt package versions for the different
distributions (I'm appending something like ~bpo50+1 for lenny .deb,
etc.), but for now at least it works well enough for the separate
repository.  And I'm not sure it's that important from the perspective of
getting the packages in sid anyway.

There is also a ceph-kclient package with the source code for the kernel
module:

http://ceph.newdream.net/debian/pool/ceph-stable/c/ceph-kclient/ceph-kclient_0.19.1-1.dsc

As I understand it there is some make-kpkg magic that is supposed to build
it automagically (if it's properly packaged) but I haven't found any good
documentation on how that should be done for standalone modules.


I'm behind on this, but I hope to look again deeper by Monday evening.


Reviewing now. Initial thoughts:

* Your diff.gz is empty. I guess that's better than making this a native 
package, but other maintainers will prefer that the debian directory be 
added during in the diff.gz. I think the ftpmasters might find your way a 
little shocking.


* You should remove the commented-out dh_* lines in debian/rules.

Your move_dbg_files script -- could be replaced by more careful use of 
dh_strip? Check out the --dbg-packages=package option described in "man 
dh_strip". (Also, if you feel like it, you could try debhelper 7, but 
that's no big deal.)


I'm still waiting for my build to finish. I hope that when it does and I 
have it installed, it will be clear how to use it so that I can easily 
test if it works as advertised. (-:


There are a lot of shared libraries here -- I hope you'll maintain their 
ABI stably and not cause too much churn.


Sorry to take so long on this. Let me know regarding the above comments!

-- Asheesh.

--
Politicians are the same all over.  They promise to build a bridge even
where there is no river.
-- Nikita Khrushchev


--
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/alpine.deb.2.00.1003090913560.4...@localhost

Re: RFS: ceph

[Asheesh Laroia]

On Tue, 9 Mar 2010, Asheesh Laroia wrote:


On Sat, 6 Mar 2010, Asheesh Laroia wrote:


On Tue, 2 Mar 2010, Sage Weil wrote:


On Thu, 11 Feb 2010, Asheesh Laroia wrote:

On Tue, 9 Feb 2010, Sage Weil wrote:
Ok, the build is fixed (man_MANS vs dist_man_MANS in the 
man/Makefile.am),

and pbuilder is behaving fine on my other box.  The updated .dsc is at

http://ceph.newdream.net/debian/dists/unstable/main/source/ceph_0.18git20100209082702-1.dsc


eek, have no spare time while prepping for a PyCon talk and
conference.freeculture.org this weekend. Ping me in 10 days?


Hi Asheesh,

I've rebuilt packages for the latest release (0.19.1).  The .dsc is at

http://ceph.newdream.net/debian/pool/ceph-stable/c/ceph/ceph_0.19.1-1.dsc

I've also futzed around with my scripts for building .debs for the
ceph.newdream.net repository (now using pbuilder, reprepro).  I suspect
I'm not quite doing the right thing wrt package versions for the different
distributions (I'm appending something like ~bpo50+1 for lenny .deb,
etc.), but for now at least it works well enough for the separate
repository.  And I'm not sure it's that important from the perspective of
getting the packages in sid anyway.

There is also a ceph-kclient package with the source code for the kernel
module:

http://ceph.newdream.net/debian/pool/ceph-stable/c/ceph-kclient/ceph-kclient_0.19.1-1.dsc

As I understand it there is some make-kpkg magic that is supposed to build
it automagically (if it's properly packaged) but I haven't found any good
documentation on how that should be done for standalone modules.


I'm behind on this, but I hope to look again deeper by Monday evening.


Reviewing now. Initial thoughts:

* Your diff.gz is empty. I guess that's better than making this a native 
package, but other maintainers will prefer that the debian directory be added 
during in the diff.gz. I think the ftpmasters might find your way a little 
shocking.


* You should remove the commented-out dh_* lines in debian/rules.


Generally a great package. Hey other mentors -- is an empty .diff.gz 
something that will make the ftpmasters upset?


If not, I will upload it immediately. Sage, I hope we work together to 
improve the other issues, but they're minor bugs compared to the great 
work you've done so far.


-- Asheesh.

--
Do more than anyone expects, and pretty soon everyone will expect more.


--
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/alpine.deb.2.00.1003092111030.8...@localhost

Re: RSF: logkeys

[Asheesh Laroia]

On Mon, 5 Apr 2010, Vedran Furač wrote:


Dear mentors,

I am looking for a sponsor for my package "logkeys". I would also note 
that I'm familiar with this process as, for some years now, I already 
maintain a couple of packages in debian and hopefully I haven't made any 
errors when packaging this one.


I suggest the debian-forensics team might provide a sponsor, and if not, 
I'd be happy to. Currently swamped, but talk to me in 14 days.


-- Asheesh.

--
"... an experienced, industrious, ambitious, and often quite often
picturesque liar."
-- Mark Twain

Re: RFS: evilvte (updated package)

[Asheesh Laroia]

On Sat, 10 Apr 2010, Wen-Yen Chuang wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Wen-Yen Chuang wrote:

Note: bug #576624 is vte's bug, not evilvte's.

evilvte (0.4.6-1) unstable; urgency=low
.
  * New upstream release
- avoid an severe VTE bug in version 0.24.0, please see #576624

PS: When you test the binary, if your X11 background has no pixbuf
data, "Toggle background" via right-click menu may cause evilvte
crash.
It is vte's bug in version 0.24.0. Please see #576624.


The bug of vte has been fixed in vte=1:0.24.0-2.

I would be glad if someone uploaded this package for me. :-)

The package can be found on mentors.debian.net:
- - dget
http://mentors.debian.net/debian/pool/main/e/evilvte/evilvte_0.4.6-1.dsc

Kind regards
Wen-Yen Chuang


Updated packages are something I can do, though I'm pretty busy right now. 
If you don't have a sponsor within a week, ping the list again and I'll 
make sure to review it then.


-- Asheesh.

--
Your boss is a few sandwiches short of a picnic.


--
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/alpine.deb.2.00.1004101608480.8...@rose.makesad.us

Re: RFS: scidavis (updated package, 2nd try)

[Asheesh Laroia]

On Fri, 9 Apr 2010, Ruben Molina wrote:


Dear mentors,

I am looking for a sponsor for the new version 0.2.4-1
of my package "scidavis".

It builds these binary packages:
scidavis   - application for scientific data analysis and visualization


Updated packages are a great thing. I'm busy right now, but if you don't 
get a sponsor for this and your other package after seven days, ping 
the list again and I'll see it as high priority. (-:


-- Asheesh.

--
For a light heart lives long.
-- Shakespeare, "Love's Labour's Lost"


--
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/alpine.deb.2.00.1004101609460.8...@rose.makesad.us

Re: RFS: mailscanner (updated package)

[Asheesh Laroia]

On Sun, 11 Apr 2010, Simon Walter wrote:


Dear mentors,

I am looking for a sponsor for the new version 4.79.11-2
of my package "mailscanner".

It builds these binary packages:
mailscanner - email gateway for virus scanning, spam and phishing detection

The package appears to be lintian clean.

The upload would fix these bugs: 572551, 572552, 575952


This looked good to me, so I uploaded it.

Don't keep sending "(updated package)" mails to debian-mentors. Now your 
goal should be one or two more good uploads, and then apply for 
DebianMaintainer status!


-- Asheesh.

--
You have an unusual magnetic personality.  Don't walk too close to
metal objects which are not fastened down.


--
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/alpine.deb.2.00.1004132325040.5...@rose.makesad.us

Re: RFS: drbdlinks (updated package, 2nd try)

[Asheesh Laroia]

On Sat, 10 Apr 2010, Thierry Randrianiriana wrote:


Dear mentors,

I am looking for a sponsor for my package "drbdlinks".

* Package name: drbdlinks
Version : 1.18-1
Upstream Author : Sean Reifschneider 
* URL : http://www.tummy.com/Community/software/drbdlinks/
* License : GPL2
Section : admin

It builds these binary packages:
drbdlinks  - Manages symlinks into a shared DRBD partition


Hi Thierry,

This package is in pretty good shape. I'm uploading it right now.

There are a few commented-out lines remaining in debian/rules. Could you 
clean that up and prepare a -2?


I'd love it if you'd move it to the new "dh 7" format. That'd be optional 
but really cool. (-:


-- Asheesh.

--
Q:  Why do ducks have big flat feet?
A:  To stamp out forest fires.

Q:  Why do elephants have big flat feet?
A:  To stamp out flaming ducks.


--
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/alpine.deb.2.00.1004132351180.5...@rose.makesad.us

Re: RFS: monkey (updated package)

[Asheesh Laroia]

On Tue, 13 Apr 2010, Thorsten Schmale wrote:


Dear mentors,

I am looking for a sponsor for the new version 0.10.1-1
of my package "monkey".

It builds these binary packages:
monkey - very small and fast open source web server for Linux


Did you get this uploaded? If not, where is your original sponsor? (-:

If you're willing to work with me to get DebianMaintainer status, then I 
can review this (but I'm busy until 10 days from today).


-- Asheesh.

--
You will forget that you ever knew me.


--
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/alpine.deb.2.00.1004230554240.16...@rose.makesad.us

Re: Only in pbuilder: CMake can't find FLTK

[Asheesh Laroia]

On Wed, 5 May 2010, Gary Briggs wrote:

I've been spending the last few days packaging up my pet project. I 
finally submitted it to the mentors website last night, but I'm aware of 
one problem building it, that I'm hoping someone knows how to solve. In 
one sentence, like the subject says:


When building in pbuilder, CMake can't find FLTK.


Silly question (?), but have you tried "pbuilder login" to poke around?

-- Asheesh.

--
Today is what happened to yesterday.


--
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/alpine.deb.2.00.1005062228060.11...@rose.makesad.us

Re: Only in pbuilder: CMake can't find FLTK

[Asheesh Laroia]

On Thu, 6 May 2010, Gary Briggs wrote:


On Thu, May 06, 2010 at 10:28:35PM -0400, Asheesh Laroia wrote:

On Wed, 5 May 2010, Gary Briggs wrote:


I've been spending the last few days packaging up my pet project. I
finally submitted it to the mentors website last night, but I'm aware of
one problem building it, that I'm hoping someone knows how to solve. In
one sentence, like the subject says:

When building in pbuilder, CMake can't find FLTK.


Silly question (?), but have you tried "pbuilder login" to poke around?


I have, I couldn't see anything obvious.

I'm really curious as to what's the officially correct way to get files
into a pbuilder --login chroot.  I could apt-get install subversion and
check my code out, but that feels hacky. The instructions say explicitly
not to mount anything into the pbuilder chroot, so my obvious choice is
right out.

I installed libfltk1.1-dev, and all the things that cmake does to look
for it are set up right [at least, I *think* they are...]


I think the instructions are for what to do at build time. I don't know of 
a reason that bind mounting would be bad while you're playing with 
pbuilder --login.


As for your problem, hmm... I mean, there must be some difference. Can you 
try carefully reading the source code to the fltk check code in CMake? 
Executing it step by step, and seeing where things go awry?


-- Asheesh.

--
There's small choice in rotten apples.
-- William Shakespeare, "The Taming of the Shrew"


--
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/alpine.deb.2.00.1005071022430.11...@rose.makesad.us

Re: RFS: kapow

[Asheesh Laroia]

On Sat, 8 May 2010, Tang Ke wrote:


Dear mentors,

I am looking for a sponsor for my package "kapow".

* Package name: kapow
 Version : 1.3.2-1
 Upstream Author : Graeme Gott 
* URL : http://gottcode.org/kapow/
* License : GPLV3
 Section : x11

It builds these binary packages:
kapow  - A punch clock program

The package appears to be lintian clean.

The upload would fix these bugs: 580613

My motivation for maintaining this package is: [fill in].


fill in your motivation! (-:


--
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/alpine.deb.2.00.1005090322370.1...@rose.makesad.us