la, 2005-09-03 kello 01:34 +0200, Andreas Schuldei kirjoitti:
> The wiki markup languages of twiki and moin-moin are not
> compatible. Still it would be nice to have some content moved
> from the old .net wiki to the new .org one.
wiki.debian.net seems to be running kwiki, not twiki, in case that
> Yes, those are the titles of those bugs *now*, after I noticed the
> problem in the list. Check the original bug titles as submitted. :)
FWIW, this was due to an issue with reportbug which was recently fixed
(#323801).
b.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
On Sat, 2005-09-03 at 01:34 +0200, Andreas Schuldei wrote:
> The wiki markup languages of twiki and moin-moin are not
> compatible. Still it would be nice to have some content moved
> from the old .net wiki to the new .org one. (the debconf team for
> one is interested in using the features of moin
On Aug 23, Marco d'Itri <[EMAIL PROTECTED]> wrote:
> (#100) How coldplug works
Update: coldplug is being reimplemented in C and will become part of
udev, so there will not be further developement of the package in this
form.
If you installed coldplug, please purge it and install hotplug again.
--
Hi all,
Debian unstable & testing still carry around libc5, and some associated
packages like altgcc, libdb1, ld.so and a few others.
Is there nowadays still a use for these packages? Does the amount of
usage warrant the efforts it take to maintain these rather outdated
packages? I get a mixed re
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
>> Would it be acceptable to reject or drop more non-spam? (We could
>I am uncomfortable with dropping any mail, but I encourage a sensible
>policy to reject spam.
Sorry if I did not make it clear before, we already are dumping
100,000 mess
The wiki markup languages of twiki and moin-moin are not
compatible. Still it would be nice to have some content moved
from the old .net wiki to the new .org one. (the debconf team for
one is interested in using the features of moin-moin for easier
cooperation and to keep the existing pages.)
The
Hello Steve,
Steve Langasek <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 01, 2005 at 09:11:31PM +, Joerg Sommer wrote:
>> It seems there is a misunderstanding. bootchart is a shell script that is
>> started as init (kernel prompt init=/sbin/bootchart), which then forks
>> the real init to start th
On Fri, Sep 02, 2005 at 11:55:23PM +0200, Wouter van Heyst wrote:
> On Fri, Sep 02, 2005 at 04:05:25PM -0400, Joe Smith wrote:
>
>> I assume that by 'preching to the choir' Wouter meant: the people you are
>> trying to convince already believe in what you are saying.
>> I suspect that Yavor inte
On Fri, Sep 02, 2005 at 06:51:20PM +0200, Richard Atterer wrote:
>> On Fri, Sep 02, 2005 at 04:04:27AM -0700, Steve Langasek wrote:
> >> But no one has yet answered my question: *why* are there ABI
> >> differences between the gnutls and openssl builds?
> To the best of my knowledge (I could be w
On Fri, Sep 02, 2005 at 04:05:25PM -0400, Joe Smith wrote:
> I assume that by 'preching to the choir' Wouter meant: the people you are
> trying to convince already believe in what you are saying.
> I suspect that Yavor interpeted this as: the people you are trying to
> convince don't care.
>
>
In article <[EMAIL PROTECTED]>,
Adeodato Simó <[EMAIL PROTECTED]> wrote:
>* Steve Langasek [Thu, 01 Sep 2005 23:03:21 -0700]:
>
>> Hrm. If this information is all just being copied to the real
>> filesystem at the end of the boot process anyway, why does it need to
>> write it out to disk instead
Package: wnpp
Severity: wishlist
Owner: David Moreno Garza <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: joomla
Version : 1.0 (not released yet)
Upstream Author : Joomla Core Team
(http://www.joomla.org/content/blogcategory/13/29/)
* URL
Package: wnpp
Severity: wishlist
Owner: David Moreno Garza <[EMAIL PROTECTED]>
* Package name: joomla
Version : 1.0 (not released yet)
Upstream Author : Joomla Core Team
(http://www.joomla.org/content/blogcategory/13/29/)
* URL : http://www.joomla.org/
* License
Please fix your broken From: header.
On Fri, Sep 02, 2005 at 05:44:26PM +0300, Delian Delchev wrote:
> Jeroen van Wolffelaar wrote:
> >On Fri, Sep 02, 2005 at 03:17:30PM +0100, Toby White wrote:
> >>Since they are Makefiles, there is no convention (is there?) for specifying
> >>which shell shoul
On Fri, Sep 02, 2005 at 04:05:25PM -0400, Joe Smith wrote:
>
> >parse error.
> >
> >1. Yavor Doganov says something.
> >2. Wouter Verhelst: Yeah. _We_ know.
> >3. Yavor Doganov: Is suddenly "sad" that Wouter (seems to) agree(s).
> >
> >WTF?
>
> I assume that by 'preching to the choir' Wouter mean
parse error.
1. Yavor Doganov says something.
2. Wouter Verhelst: Yeah. _We_ know.
3. Yavor Doganov: Is suddenly "sad" that Wouter (seems to) agree(s).
WTF?
I assume that by 'preching to the choir' Wouter meant: the people you are
trying to convince already believe in what you are saying.
* David Moreno Garza <[EMAIL PROTECTED]>, [2005-09-01 11:42 -0500]:
> On Wed, 2005-08-31 at 08:52 -0400, Bryan Donlan wrote:
> > The only thing shared between xmms1 and xmms2, really, is the name.
Hey, they're both music players as well. :)
> So is this a fork of XMMS? If not, I can't see a re
On Fri, Sep 02, 2005 at 07:07:02PM +0200, Jean-Philippe Garcia Ballester wrote:
> Hi,
> I heard OpenSSL's license is incompatible with GPL. Does this apply to
> binary package only or both binary and source package?
> The thing is, the library I'm packaging can use both libcrypto (from
> Open
also sprach Anthony Towns [2005.09.02.1852 +0200]:
> Thanks particularly to Margarita Manterola and Erinn Clark for
> acting as sounding boards and offering inspiration and advice, and
> to other folks on #debian-women (Moray Allan, James Troup, David
> Nusinow, Pascal Hakim, Hanna Wallach, Helen
Hi,
I heard OpenSSL's license is incompatible with GPL. Does this apply to
binary package only or both binary and source package?
The thing is, the library I'm packaging can use both libcrypto (from
OpenSSL) and libgcrypt, using ifdef. The binary package is built with
libgcrypt support only.
Package: wnpp
Severity: wishlist
Owner: Norbert Tretkowski <[EMAIL PROTECTED]>
* Package name: pyrss
Version : 0.9.9.1-1
Upstream Author : Rafal Zawadzki
* URL : http://pyrss.jabberstudio.org/
* License : GPL
Description : fetches rss feeds and notify regi
Package: wnpp
Severity: wishlist
Owner: Norbert Tretkowski <[EMAIL PROTECTED]>
* Package name: feedparser
Version : 3.3-1
Upstream Author : Mark Pilgrim
* URL : http://www.feedparser.org/
* License : Python license
Description : universal feed parser
Pyth
> On Fri, Sep 02, 2005 at 04:04:27AM -0700, Steve Langasek wrote:
> > But no one has yet answered my question: *why* are there ABI
> > differences between the gnutls and openssl builds?
To the best of my knowledge (I could be wrong), ATM the only ABI difference
is that when OpenSSL is used,
curl_
Andrew Suffield <[EMAIL PROTECTED]> writes:
> You could have written this with equal validity:
> long int typedef long int64_t;
Not a good idea, though, because C99 says this:
6.11.5 Storage-class specifiers
1The placement of a storage-class specifier other than at the
beginning o
On Fri, Sep 02, 2005 at 07:32:57AM +, OndÅ?ej SurÃœ wrote:
> there was three request to enable *spell extensions in php4/5 packages.
> Currently nobody from PHP maintainers team wants to add more burden on
> his shoulders, hence I request help from our fellow debian developers
> to package pspe
I will be out of the office starting 08/27/2005 and will not return until
09/12/2005.
I will have access to email.
If you need immediate assistance, please contact Melody Ng.
Benita.
For NextWave Issues or questions, please contact Paul Rodriguez
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
On Sep 02, Paul TBBle Hampson <[EMAIL PROTECTED]> wrote:
> If I've understood correctly, it is because curl expects the client program
> or library to -lgnutls or -lopenssl and therefore provide the SSL symbols
> to match the symbols which that build of the .so file is expecting.
I hope not, this
On Fri, Sep 02, 2005 at 04:04:27AM -0700, Steve Langasek wrote:
> On Fri, Sep 02, 2005 at 12:24:18PM +0200, Domenico Andreoli wrote:
> > >> - libcurl3 (GnuTLS, soname: libcurl.so.3)
> But no one has yet answered my question: *why* are there ABI differences
> between the gnutls and op
Jeroen van Wolffelaar wrote:
>On Fri, Sep 02, 2005 at 03:17:30PM +0100, Toby White wrote:
>
>
>>Since they are Makefiles, there is no convention (is there?) for specifying
>>which shell should be used to execute commands.
>>
>>
>
>I use "export SHELL=/bin/bash" in the top of Makefiles where
On Fri, Sep 02, 2005 at 03:17:30PM +0100, Toby White wrote:
> I have recently come across this behaviour while rebuilding
> modxslt; in the debian/rules file, there are several instances
> of the idiom:
>
> @cp -a $(CURDIR)/debian/libmodxslt0/usr/lib/libmodxslt0{.a,.la} \
>$(CURDIR)/debian
On Fri, Sep 02, 2005 at 03:17:30PM +0100, Toby White wrote:
> Since they are Makefiles, there is no convention (is there?) for specifying
> which shell should be used to execute commands.
I use "export SHELL=/bin/bash" in the top of Makefiles where I use bashisms.
I greatly prefer that over making
I have recently come across this behaviour while rebuilding
modxslt; in the debian/rules file, there are several instances
of the idiom:
@cp -a $(CURDIR)/debian/libmodxslt0/usr/lib/libmodxslt0{.a,.la} \
$(CURDIR)/debian/libmodxslt0-dev/usr/lib
Note the use of the {.a,.la} wildcards.
While
On Fri, Sep 02, 2005 at 12:24:18PM +0200, Domenico Andreoli wrote:
> > > - libcurl3 (GnuTLS, soname: libcurl.so.3)
> > So the libcurl3 in sarge and etch will have ABI incompatibilities?
> at the release time of etch this problem will regard only
> external software. this kind of i
On Fri, Sep 02, 2005 at 11:56:13AM +0200, Adeodato Simó wrote:
> * Domenico Andreoli [Fri, 02 Sep 2005 11:16:28 +0200]:
>
> > - libcurl3-dev (OpenSSL, depends: libssl-dev)
> > - libcurl3-openssl-dev (GnuTLS, depends: libgnutls-dev)
>
> Obvious typo/whatever here, right?
On Fri, Sep
On Fri, Sep 02, 2005 at 02:58:05AM -0700, Steve Langasek wrote:
> On Fri, Sep 02, 2005 at 11:16:28AM +0200, Domenico Andreoli wrote:
>
> > ok, we are hooked into the libflac6 transition, let's start the curl one.
>
> > my wish is to upload curl 7.14.1 with the following package layout:
>
> > -
On Fri, Sep 02, 2005 at 11:56:13AM +0200, Adeodato Simó wrote:
> * Domenico Andreoli [Fri, 02 Sep 2005 11:16:28 +0200]:
> > - libcurl3 (GnuTLS, soname: libcurl.so.3)
> So the libcurl3 in sarge and etch will have ABI incompatibilities?
If done right, I see no reason this should be
On Fri, Sep 02, 2005 at 02:49:32AM -0700, Steve Langasek wrote:
> Yes, those are the titles of those bugs *now*, after I noticed the
> problem in the list. Check the original bug titles as submitted. :)
Ah, I see. Thanks for pointing this out!
--
Jon Dowland
http://jon.dowland.name/
--
To UN
Russ Allbery <[EMAIL PROTECTED]> writes:
> The software area in which you're writing code is fairly mature and even
> standardized. Pretty much everything that does SASL uses Cyrus SASL.
It is not even that good, plenty of applications implement their own
SASL code. A quick ldd $bin|grep sasl s
On Fri, Sep 02, 2005 at 11:16:28AM +0200, Domenico Andreoli wrote:
> ok, we are hooked into the libflac6 transition, let's start the curl one.
> my wish is to upload curl 7.14.1 with the following package layout:
> - curl (OpenSSL, linked to libcurl-openssl.so.3)
> - libcurl3
* Domenico Andreoli [Fri, 02 Sep 2005 11:16:28 +0200]:
> - libcurl3-dev (OpenSSL, depends: libssl-dev)
> - libcurl3-openssl-dev (GnuTLS, depends: libgnutls-dev)
Obvious typo/whatever here, right?
> - libcurl3 (GnuTLS, soname: libcurl.so.3)
So the libcurl3 in sarg
On Sep 01, Blars Blarson <[EMAIL PROTECTED]> wrote:
> Would it be acceptable to reject or drop more non-spam? (We could
I am uncomfortable with dropping any mail, but I encourage a sensible
policy to reject spam.
--
ciao,
Marco
signature.asc
Description: Digital signature
On Fri, Sep 02, 2005 at 10:25:09AM +0100, Jon Dowland wrote:
> On Fri, Sep 02, 2005 at 12:26:09AM -0600, [EMAIL PROTECTED] wrote:
> > The following packages have been orphaned:
> >Kate (#325996), orphaned yesterday
> >Konqueror (#325996), orphaned yesterday
> >XMMS (#325995), orphaned
Hi,
On Friday 02 September 2005 08:26, [EMAIL PROTECTED] wrote:
> The following is a listing of packages for which help has been requested
> through the WNPP (Work-Needing and Prospective Packages) system in the
> last week.
Something is wrong with this list:
> The following packages have been o
On Fri, Sep 02, 2005 at 12:26:09AM -0600, [EMAIL PROTECTED] wrote:
> The following packages have been orphaned:
>
>Kate (#325996), orphaned yesterday
>Konqueror (#325996), orphaned yesterday
>XMMS (#325995), orphaned yesterday
>and (#325996), orphaned yesterday
>for (#325996),
On Thu, Sep 01, 2005 at 09:40:17PM +0200, Elimar Riesebieter wrote:
>
> On Tue, 30 Aug 2005 the mental interface of Daniel Stenberg told:
> >
> > The problem you have with libcurl and OpenSSL/GnuTLS is not strictly an
> > "upstream problem".
> >
> > In the curl project there are some ideas floa
On Aug 30, Daniel Stenberg <[EMAIL PROTECTED]> wrote:
> In my view, there's only one available work-around for the short to mid
> term, and that is to use a separate .so file for libcurl built with GnuTLS.
We know that in the long term we want to use gnutls. So why should it
not be the default fo
Hi,
* Pascal Hakim <[EMAIL PROTECTED]> [2005-09-02 10:20]:
> On Thu, Sep 01, 2005 at 09:03:26PM +0200, Nico Golde wrote:
> > What about using the msgid instead of the id so it would be
> > possible to use your MUA to mark a mail as spam via a script
> > which can be executed and calls the spam-repo
Package: wnpp
Severity: normal
Hi people,
there was three request to enable *spell extensions in php4/5 packages.
Currently nobody from PHP maintainers team wants to add more burden on
his shoulders, hence I request help from our fellow debian developers
to package pspell and aspell extensions as
"Roberto C. Sanchez" <[EMAIL PROTECTED]> writes:
> The problem is that being too restrictive on spam also means getting
> more false positives.
Therefore one must find out how much more restrictive one can be
without getting too restrictive. :D
--
Stig Sandbeck Mathisen
--
To UNSUBSCRIBE, em
On Fri, Sep 02, 2005 at 08:53:19AM +0200, Adeodato Simó wrote:
> * Steve Langasek [Thu, 01 Sep 2005 23:03:21 -0700]:
> > Hrm. If this information is all just being copied to the real
> > filesystem at the end of the boot process anyway, why does it need to
> > write it out to disk instead of just
51 matches
Mail list logo
