On May 30, Joey Hess ([EMAIL PROTECTED]) wrote:
> Neil Roeth wrote:
> > Thanks for the hints. I should have been more clear - I have no problem
> > getting the main page, i.e., [EMAIL PROTECTED] There are
> > links in that page to bugs.debian.org/cgi-bin/bugreport.cgi?bug= for
> > each
> >
Neil Roeth wrote:
> Thanks for the hints. I should have been more clear - I have no problem
> getting the main page, i.e., [EMAIL PROTECTED] There are
> links in that page to bugs.debian.org/cgi-bin/bugreport.cgi?bug= for each
> bug, and I want to get each of those as a local web page, too. That
I really think this should go to the debian-perl list so I'm sending it
there. The libc-include-perl example below is one of the best arguments
I've seen for changing the perl module naming scheme. It's a pity that
we didn't think it through more before deciding on it. IIRC we just took
the example
I recently had a bug (193950) filed against one of my packages because the
shared libraries had "undefined non-weak symbols" - libstdc++ was not being
linked in. I resolved it with what I consider a gruesome hack. I discovered
that forcing libtool to use g++ while linking would automatically link
Neil Roeth <[EMAIL PROTECTED]> writes:
> I recently adopted several packages (jade, openjade, opensp) and several of
> the open bugs were fixed by NMUs, so they have "fixed" tags. I think all I
> need to do is send an email to [EMAIL PROTECTED] that says, "This bug
> was fixed in the NMU of versi
On Thu, May 29, 2003 at 07:14:39PM -0400, Neil Roeth wrote:
> I recently adopted several packages (jade, openjade, opensp) and
> several of the open bugs were fixed by NMUs, so they have "fixed"
> tags. I think all I need to do is send an email to
> [EMAIL PROTECTED] that says, "This bug was fixed
I recently adopted several packages (jade, openjade, opensp) and several of
the open bugs were fixed by NMUs, so they have "fixed" tags. I think all I
need to do is send an email to [EMAIL PROTECTED] that says, "This bug
was fixed in the NMU of version 1.2.1-29.3. The fix has been propagated to
t
My sponsor is unavailable to upload for me right now, so I am seeking a
Developer who would like to help me get the following uploaded:
1. A bugfix to the smlnj-runtime package. Fixes a compile problem with
the gcc-3.3 compiler.
2. Optionally a set of new smlnj related packages:
libckit-s
Hi,
I am a new DD, so there are a lot of subtleties out there still waiting
for me to learn :)
One of them is: A coworker of mine is a co-developer of a Java-based
LMS, OpenUSS (http://www.openuss.org). We were talking that it would be
interesting to package OpenUSS for Debian - Initially I off
Kalle Kivimaa wrote:
> José Luis Tallón <[EMAIL PROTECTED]> writes:
>
>>It would probably be easier for th users if the name-mangling yielded
>>"libperl-curl-easy" or "libperl-www-curl" instead of the current one...
>>
>>...any reasons for doing it otherwise i have overlooked ?
>
> Debian Perl Po
José Luis Tallón <[EMAIL PROTECTED]> writes:
> It would probably be easier for th users if the name-mangling yielded
> "libperl-curl-easy" or "libperl-www-curl" instead of the current one...
>
> ...any reasons for doing it otherwise i have overlooked ?
Debian Perl Policy is quite specific: Foo::B
At 09:27 29/05/2003 +0200, you wrote:
On Thu, May 29, 2003 at 12:44:22AM -0400, Deedra Waters wrote:
[...]
> | > If you look at the packages description, you will see thatit says "This
> | > module provides the Perl bindings to libcurl." In the description it
> | > tells what the package is.
> | C
12 matches
Mail list logo
