On Wed, 27 Jun 2007, Javier Fernández-Sanguino Peña wrote:
It would be nice if you uploaded also the files (TeX+figs) you used in your
presentation. That way people could still use them as a template, or as
a starting point for their own presentations just in case no "official"
template ends up
Zachary Palmer wrote:
Hey, all. I *think* I have a working submission for the contrib
section of Debian mainline; this is the [EMAIL PROTECTED]
download-and-install wrapper that I was discussing a couple days ago.
I'm rather new at this, so I don't know exactly how I should proceed.
What is
Hello,
I might start thinking about porting an x509 application from OpenSSL to
GnuTLS (Gnu Transport Layer Security) and so looking about feedbacks,
experiences ..etc.. about such porting, libraries ..etc..
Thanks for your (intellectual and spirit) contribution.
Regards,
Bruno
--
PGP key ID
Hi Zach,
On Wednesday 27 June 2007 03:44:21 Zachary Palmer wrote:
> Hey, all. I *think* I have a working submission for the contrib section
> of Debian mainline; this is the [EMAIL PROTECTED] download-and-install
> wrapper that I was discussing a couple days ago. I'm rather new at
> this, so I do
Hello,
as discussed on [EMAIL PROTECTED], we're looking for a copy of dpkg's old
arch repository used while Scott James Remnant was dpkg's maintainer.
http://lists.debian.org/debian-dpkg/2007/06/msg6.html
If anyone has a copy of it, please make it available to us.
It was named [EMAIL PROTECT
Greets,
I have some interrogations about apt :
I want to develop a centralized system holding what packages operations
happened on a remote debian system (in a database).
I'm using the DPkg::Pre-Install-Pkgs apt option to get information about
what packages are installed/removed/updated but I nee
On Tue, Jun 26, 2007, Joey Hess wrote:
> I think it would also be useful to include 'nostrip' and 'noopt' in the
> Build-Options field, as a way to indicate that the package implements
> those DEB_BUILD_OPTIONS. I also have some Evil Plans for other things
> that can go in Build-Options, but they'r
On Wednesday 27 June 2007 18:05, Bruno Costacurta <[EMAIL PROTECTED]> wrote:
> I might start thinking about porting an x509 application from OpenSSL to
> GnuTLS (Gnu Transport Layer Security) and so looking about feedbacks,
> experiences ..etc.. about such porting, libraries ..etc..
>
> Thanks for
Package: wnpp
Severity: wishlist
Owner: Julian Andres Klode <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: hubackup
Version : 0.0.7
Upstream Author : Sivan Greenberg <[EMAIL PROTECTED]>
* URL : https://launchpad.net/hubackup
* License
Loïc Minier <[EMAIL PROTECTED]> writes:
> On Tue, Jun 26, 2007, Joey Hess wrote:
>> I think it would also be useful to include 'nostrip' and 'noopt' in the
>> Build-Options field, as a way to indicate that the package implements
>> those DEB_BUILD_OPTIONS. I also have some Evil Plans for other thi
On Sun, Jun 10, 2007 at 08:40:21AM +0900, Junichi Uekawa wrote:
> > > I had an idea and still pondering on it. I wanted to do automatic
> > > two-way synchronization with README.Debian and wiki.debian.org
I like the idea in general, but I would rather focus on ...
> [web->package]
>
> 2. upstre
On 6/27/07, Frédéric PICA <[EMAIL PROTECTED]> wrote:
Greets,
I have some interrogations about apt :
I want to develop a centralized system holding what packages operations
happened on a remote debian system (in a database).
I'm using the DPkg::Pre-Install-Pkgs apt option to get information about
On 6/27/07, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
Hello,
as discussed on [EMAIL PROTECTED], we're looking for a copy of dpkg's old
arch repository used while Scott James Remnant was dpkg's maintainer.
http://lists.debian.org/debian-dpkg/2007/06/msg6.html
If anyone has a copy of it, pl
Hi,
I have some trouble building the new version of WordNet. For
reasons I do not want to discuss here I had to build a composite
source tarball from two different upstream tarballs and had
to adjust the autoconf stuff - which obviousely failed. I
putted the relevant files to
http://people.
Stefano Zacchiroli <[EMAIL PROTECTED]> wrote:
> I guess a lot of us have similar needs. What about defining a
> standardized debian/rules target which should take care of similar
> stuff?
We already have that: get-orig-source.
If the upstream-provided contents change regularly, this should als
On Wed, 27 Jun 2007, Gustavo Franco wrote:
> On 6/27/07, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> >If anyone has a copy of it, please make it available to us.
> >It was named [EMAIL PROTECTED]/dpkg--devel--1.13 AFAIK.
> >(Neither Scott nor Ian have a copy of it)
>
> Hi buxy,
>
> Manoj partici
Hi,
> > sorry, wrong mailing list.
> > re-sending the same mail to @jp.
>
> But it made me run
>
> $ apt-cache show yatex
> [...]
> Recommends: ptex-bin|ptex-jtex, tetex-bin
> [...]
> Description: Yet Another TeX mode for Emacs
>
>
> Please replace tetex-bin with texlive - this is one of the
Hi :)
Can anyone please sign my key?
here is my USER-ID:
"Amin Shali (http://www.amshali.org/) <[EMAIL PROTECTED]>"
Thanks,
--
http://www.amshali.org/
Em Qua, 2007-06-27 às 19:28 +0330, Amin Shali escreveu:
> Hi :)
> Can anyone please sign my key?
No.
Quoting http://www.debian.org/events/keysigning:
"You should never sign a key for somebody else you haven't met
personally. Signing a key based on anything other than first-hand
knowledge destro
Russ Allbery <[EMAIL PROTECTED]> writes:
> Currently, policy says that it's recommended (the weakest policy
> directive) to support noopt and nostrip. My main concern with increasing
> the strength of that directive is that, depending on how demented the
> upstream build system is, it can be diff
On Wed, Jun 27, 2007 at 05:34:42PM +0200, Frank Küster wrote:
> > I guess a lot of us have similar needs. What about defining a
> > standardized debian/rules target which should take care of similar
> > stuff?
>
> We already have that: get-orig-source.
Documented where?
Anyhow I was thinking a
Stefano Zacchiroli <[EMAIL PROTECTED]> writes:
> On Wed, Jun 27, 2007 at 05:34:42PM +0200, Frank Küster wrote:
>> > I guess a lot of us have similar needs. What about defining a
>> > standardized debian/rules target which should take care of similar
>> > stuff?
>>
>> We already have that: get-ori
Andreas Tille <[EMAIL PROTECTED]> writes:
> the relevant line in src/Makefile.am is
>
> INCLUDES = -I$(top_srcdir)/include $(TCL_INCLUDE_SPEC) -I$(TK_PREFIX)/include
>
> I have no idea why TCL_INCLUDE_SPEC which is not propagated
> correctly to Makefile.in and thus cc has not the correct path
> t
On 6/27/07, Ben Pfaff <[EMAIL PROTECTED]> wrote:
The puzzling thing to me about this situation is what is expected
to set TK_PREFIX. "grep TK_PREFIX" in the wordnet directory
shows TK_PREFIX being used, but never defined anywhere. "grep
TK_PREFIX" in /usr/share/aclocal shows no hits at all.
Di
On 6/27/07, Ben Pfaff <[EMAIL PROTECTED]> wrote:
The puzzling thing to me about this situation is what is expected
to set TK_PREFIX. "grep TK_PREFIX" in the wordnet directory
shows TK_PREFIX being used, but never defined anywhere. "grep
TK_PREFIX" in /usr/share/aclocal shows no hits at all.
Di
"Sergei Golovan" <[EMAIL PROTECTED]> writes:
> On 6/27/07, Ben Pfaff <[EMAIL PROTECTED]> wrote:
>> The puzzling thing to me about this situation is what is expected
>> to set TK_PREFIX. "grep TK_PREFIX" in the wordnet directory
>> shows TK_PREFIX being used, but never defined anywhere. "grep
>>
Stefano Zacchiroli <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 27, 2007 at 05:34:42PM +0200, Frank Küster wrote:
>> > I guess a lot of us have similar needs. What about defining a
>> > standardized debian/rules target which should take care of similar
>> > stuff?
>>
>> We already have that: get-orig
* Bruno Costacurta:
> I might start thinking about porting an x509 application from OpenSSL to
> GnuTLS (Gnu Transport Layer Security) and so looking about feedbacks,
> experiences ..etc.. about such porting, libraries ..etc..
What kind of level of X.509 support do you need? Is chasing
certifi
On Wed, 27 Jun 2007, Ben Pfaff wrote:
OK, I can see now that /usr/lib/tk8.4/tkConfig.sh sets TK_PREFIX
in the environment of "configure". But what is meant to
propagate this environment variable into the Makefile? I don't
see anything intended to do that. Autoconf does not
automatically propa
Andreas Tille <[EMAIL PROTECTED]> writes:
> Yes, you both seem to come to the same conclusion as I myself - but
> I have no idea how to fix this. There must be some trick to propagate
> these variables, but how? I've got no clue out of reading the
> texinfo docs.
That part is easy: just add
Andreas Tille wrote:
> On Wed, 27 Jun 2007, Ben Pfaff wrote:
>
> >OK, I can see now that /usr/lib/tk8.4/tkConfig.sh sets TK_PREFIX
> >in the environment of "configure". But what is meant to
> >propagate this environment variable into the Makefile? I don't
> >see anything intended to do that. Aut
On Wednesday 27 June 2007 16:45:06 pm Andreas Tille wrote:
> On Wed, 27 Jun 2007, Ben Pfaff wrote:
> > OK, I can see now that /usr/lib/tk8.4/tkConfig.sh sets TK_PREFIX
> > in the environment of "configure". But what is meant to
> > propagate this environment variable into the Makefile? I don't
>
On Wed, Jun 27, 2007 at 08:08:08PM +0200, Frank Küster wrote:
> > Anyhow I was thinking at something more generic that only getting orig
> > sources
> I don't think a Debian diff.gz should contain arbitrary updates from
> upstream.
I didn't imply that it should be some other kind of updates, but
On Mon, Jun 18, 2007 at 10:30:55AM +0200, Goswin von Brederlow wrote:
> I would like to gather up some momentum for a policy change. Namely
> that the build-arch/indep targets in debian/rules become required
> instead of being optional.
> The reason for this is that dpkg-buildpackage can't reliabl
Package: general
Severity: wishlist
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-6-generic (SMP w/1 CPU core)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh lin
On Wed, Jun 27, 2007 at 01:04:30PM -0300, Guilherme de S. Pastore wrote:
> Em Qua, 2007-06-27 às 19:28 +0330, Amin Shali escreveu:
> > Hi :)
> > Can anyone please sign my key?
>
> No.
>
> Quoting http://www.debian.org/events/keysigning:
>
> "You should never sign a key for somebody else you hav
Rafael wrote:
> Package: general
> Severity: wishlist
>
>
>
> -- System Information:
> Debian Release: lenny/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.22-6-generic (SMP w/1 CPU core)
> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.
On 6/28/07, Andrew Donnellan <[EMAIL PROTECTED]> wrote:
I interpreted it as saying 'Give a warning if someone accidentally
pulls it out before unmounting', not 'Tell me when I can pull it out
after unmounting.'
The original request in the BR I mean; not the message from gnome-mount.
--
Andrew
On 6/28/07, Michael Biebl <[EMAIL PROTECTED]> wrote:
FWIW recent GNOME desktops in unstable using gnome-mount for doing the mounting
stuff, already have this kind of functionality. Whenever you unmount a removable
device, gnome-mount will show you a message via notification-daemon, when it is
saf
Hi!
Could someone explain me (or point to a manual) what 'Uploaded' means
in http://people.debian.org/~igloo/status.php?packages=erlang ?
The package was initially uploaded for amd64 architecture. It was
built for i386 and stays in 'uploaded' state for several days. I
wonder why it can't become
On Thu, 2007-06-28 at 14:54 +1000, Andrew Donnellan wrote:
> On 6/28/07, Michael Biebl <[EMAIL PROTECTED]> wrote:
> > FWIW recent GNOME desktops in unstable using gnome-mount for doing the
> > mounting
> > stuff, already have this kind of functionality. Whenever you unmount a
> > removable
> > de
41 matches
Mail list logo
