Package: wnpp
Severity: wishlist
Owner: Xavier Oswald <[EMAIL PROTECTED]>
* Package name: libauthen-simple-http-perl
Version : 0.2
Upstream Author : Christian Hansen <[EMAIL PROTECTED]>
* URL :
http://search.cpan.org/CPAN/authors/id/C/CH/CHANSEN/Authen-Simple-HTTP-0.2
pe, 2006-12-29 kello 19:50 +0100, Vincent Bernat kirjoitti:
> OoO En cette fin de matinée radieuse du lundi 26 juin 2006, vers
> 11:19, Martin-Éric Racine <[EMAIL PROTECTED]> disait:
>
> > That is a leftover from Tollef's original code in wizard.py, where the
> > UI colors are hard-coded, ra
Package: wnpp
Severity: wishlist
Owner: Cedric Delfosse <[EMAIL PROTECTED]>
* Package name: gktools
Version : 0.10.2
Upstream Author : Nils O. Selåsdal
* URL : http://asgaard.homelinux.org/code/gktools/
* License : GPL
Programming Lang: C
Description :
Joey Hess wrote:
> No, tmpnam generates a name for a file that did not exist at some point
> in time, but that *will* exist in the worst possible state (eg, a
> symlink to something important) when an attacker is targeting your program.
Which is why I'm trying to find a way to get rid of the call
Ilija Barukcic wrote:
>
> Bell's theorem is refuted!
I submit this as the oddest spam on a Debian list this year.
--
John H. Robinson, IV [EMAIL PROTECTED]
http
WARNING: I cannot be held responsible for the above,
Colin Tuckley wrote:
> tmpnam generates a name for a file which is guaranteed *not* to exist
No, tmpnam generates a name for a file that did not exist at some point
in time, but that *will* exist in the worst possible state (eg, a
symlink to something important) when an attacker is targeting your
> I think you're confusing the buildd admin with the porters. I expect
Maybe that's because the buildd admins used to be the porters, and then,
for some reason I do not understand, this mysteriously stopped being
true.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
OoO En cette fin de matinée radieuse du lundi 26 juin 2006, vers
11:19, Martin-Éric Racine <[EMAIL PROTECTED]> disait:
> That is a leftover from Tollef's original code in wizard.py, where the
> UI colors are hard-coded, rather than inherited via the GTK theme.
> I can see the lines where th
Mike Hommey <[EMAIL PROTECTED]> writes:
> Sven Luther <[EMAIL PROTECTED]> wrote:
>> Don't you find it a bit hypocrit to have x86 uploads go directly to the
>> archive, and not allowing even a single day delay which would allow to
>> stop unclean DD-build-boxes breakage and a clean state, and on th
Jever, 29.12.2006.
Bell's theorem is refuted!
If you need more information, please download for free:
http://www.barukcic-causality.homepage.t-online.de/Causation/Causation_2006_Volume_2.pdf
.
Happy new year.
Ilija
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscri
On Fri, Dec 29, 2006 at 11:20:30AM +0100, Josselin Mouette wrote:
> An arm buildd maintainer not reading [EMAIL PROTECTED] is simply not
> doing his job as buildd maintainer. You can't pretend to be the one
> handling builds for the whole archive while not following discussions
> around problems sp
Stephane Bortzmeyer <[EMAIL PROTECTED]> wrote:
> MJ Ray <[EMAIL PROTECTED]> wrote
> > Please show where reading everything on [EMAIL PROTECTED] is
> > given as a requirement for buildd maintainership.
>
> It seems common sense!
Huh? It seems common sense that most subscribers ignore at least so
Package: wnpp
Severity: wishlist
Owner: Mattia Dongili <[EMAIL PROTECTED]>
* Package name: xserver-xorg-input-evtouch
Version : 0.8.1
Upstream Author : Kenan Esau <[EMAIL PROTECTED]>
* URL : http://stz-softwaretechnik.com/~ke/touchscreen/evtouch.html
* License :
On Thu, Dec 28, 2006 at 04:45:32PM -0800, Steve Langasek wrote:
> On Thu, Dec 21, 2006 at 11:39:13AM +0100, Aurelien Jarno wrote:
> > All started with this email:
> > http://lists.debian.org/debian-arm/2006/08/msg00151.html
>
> > ARM was *in danger*, a lot of stuff (java, xulrunner, mono, ...) wer
Stephane Bortzmeyer <[EMAIL PROTECTED]> wrote:
> It seems common sense! Debian has a serious problem if you have to
> write everything down.
>
> "A buildd maintainer must be able to type Unix commands on a
> keyboard."
"And the said keyboard must be connected one way or another to the
said buildd
On Fri, Dec 29, 2006 at 11:36:45AM +,
MJ Ray <[EMAIL PROTECTED]> wrote
a message of 43 lines which said:
> > An arm buildd maintainer not reading [EMAIL PROTECTED] is simply not
> > doing his job as buildd maintainer.
>
> Please show where reading everything on [EMAIL PROTECTED] is
> given
Steinar H. Gunderson wrote:
> Why can't you just set up a pipe, fork, connect stdout of the child to one
> end of the pipe, and exec the program?
Thanks, reading about 'pipe' led me to 'popen' which pretty much
automatically does what you suggest.
regards,
Colin
--
Colin Tuckley | [EMAI
Josselin Mouette <[EMAIL PROTECTED]> wrote:
> An arm buildd maintainer not reading [EMAIL PROTECTED] is simply not
> doing his job as buildd maintainer.
Please show where reading everything on [EMAIL PROTECTED] is
given as a requirement for buildd maintainership.
> You can't pretend to be the one
On Fri, Dec 29, 2006 at 10:17:55AM +, Colin Tuckley wrote:
> The interpreter allows the user to execute shell commands, this is
> implemented using the "system" call.
>
> [...]
>
> What is the best solution to this problem?
Why can't you just set up a pipe, fork, connect stdout of the child to
ОРГАНИЗАЦИЯ ПРАЗДНИКОВ
Организация шоу-программ с участием артистов
Подбор места праздника
Звуковое и световое обеспечение
Создание сценария
Фото и видео съемка
Стриптиз (женский и мужской)
И многое другое
ЗВОНИТЕ СЕЙЧАС!
(495)792 77 31
Le jeudi 28 décembre 2006 à 16:45 -0800, Steve Langasek a écrit :
> So first of all, neither the debian-arm list, nor the #debian-arm channel,
> nor his blog are a communication medium that's guaranteed to reach the arm
> buildd maintainer *or* the buildd local admins. For the former, you want
> [
I'm doing some work on a Basic Interpreter and will be packaging it for Debian.
The interpreter allows the user to execute shell commands, this is
implemented using the "system" call.
To capture the output from the command " > " is concatenated onto
the end of the user supplied command. The is g
On Fri, Dec 29, 2006 at 07:58:34AM +0100, Sven Luther <[EMAIL PROTECTED]> wrote:
> Don't you find it a bit hypocrit to have x86 uploads go directly to the
> archive, and not allowing even a single day delay which would allow to stop
> unclean DD-build-boxes breakage and a clean state, and on the ot
23 matches
Mail list logo
