martin f krafft wrote:
also sprach Russ Allbery r...@debian.org [2009.06.23.0158 +0200]:
Meeting in person and exchanging government ID or something that
looks good enough to fool people is a compromise position, but
I do think there's a general feeling that it's close to a sweet
spot in that
Marco Túlio Gontijo e Silva wrote:
I've reported a bug asking to change a word in the documentation of
emdebian-rootfs. It's written:
[snip]
What do you think about that?
Please keep the discussion to the bug report. IIRC there are about
80-100 bug reports reported every day. If all this
Giacomo A. Catenazzi wrote:
Very strange logic. BTW AFAIK justice doesn't identify people
because of ID documents.
It certainly does. Just imagine what will happen if you make yourself
wanted by the authorities and then show your (valid) documents to some
police officers. In case you don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
martin f krafft wrote:
The government IDs are relevant because when we're collaborating
on an OS where there's minimal code review of the work done by
maintainers and a well-chosen malicious package could cause
millions or billions of dollars in
Mathieu Malaterre wrote:
You do not need to be rude when I explicitly quote the actual doc I am
reading, which obviously should not recommend the use of chroot
FWIW, this is the wrong mailing list for that kind of question. People
tend to be more helpful, if the correct form and forum/list is
Thanks to all!
Many thanks to our release managers and all developers for spending the
past 21 months preparing and releasing Etch!
Etch is a great OS and a great distribution -- to me it's the best
software I ever had. I would switch to something better than debian, but
I know that such a move
Lars Wirzenius wrote:
However, changing the popcon debconf question to something like the
following might be an acceptable compromise:
Would you like to participate in the Debian package popularity
contest meter? Blah blah blah. You may also choose to only
report
Roberto C. Sánchez wrote:
On Fri, Apr 13, 2007 at 12:21:09AM +0200, Javier Fernández-Sanguino Peña
wrote:
The only caveat I can think of (but there might be others) is that it would
not be possible to properly count installations that are using
corporate (or ISP's) caching proxies (in
Moritz Muehlenhoff wrote:
Johannes Wiedersich wrote:
Presently the number of installations reported to popcon is about the
same as the number of subscriptions to debian-security-announce, but I
am sure there are many users of debian who don't read d-s-a and many
users, who have several -maybe
On 2008-09-18 19:19, Robert Lemmen wrote:
while the EULA topic is already being discussed:
Where is it already discussed? At least not on d-d, as far as I can
see/find...
Thanks,
Johannes
NB: Google finds only some ubuntu discussions for me...
signature.asc
Description: OpenPGP digital
On 2008-09-24 11:50, Noèl Köthe wrote:
we reached http://bugs.debian.org/50
For the occasion of the 50th Debian bug being reported today, I
couldn't resist digging some statistics from bugs.debian.org.
Out of the 50 bugs reported so far more than 44 thousand bugs
have been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josselin Mouette wrote:
Le vendredi 07 novembre 2008 à 00:27 +0100, Michelle Konzack a écrit :
The problem is, that even if it is mass production since some time, I
can not distribute the firmware as open source since it change the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josselin Mouette wrote:
Being in favor of open-sourcing firmwares (including those controlling
critical security devices in cars) does not mean being in favor of
letting anyone ship their own version. In such cases, there needs to be
some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Palfrader wrote:
On Sat, 08 Nov 2008, Theodore Tso wrote:
Fortunately for us, at the
moment I am not aware of large numbers of highly popular laptops or
servers for which non-free firmware is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gunnar Wolf wrote:
But anyway, and knowing this is not an Ubuntu list... Does anybody
know why on Earth is Acroread popular? Why isn't a PDF regularly
handled in a saner way with Evince (or kde-based lookalike) in some
distributions?
Zillions of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan McDowell wrote:
Anyway, I'm probably hugely off topic now. If anyone has experience with
Free software and PDF annotations I'd love to hear about it, otherwise
I'll try to find some time to build up the SoC work and see what
happens.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Didier Raboud wrote:
Romain Beauxis wrote:
You can't get both recent *and* stabilized software. For a solid release
to be done, one needs to hold new improvements for a while.
Yes. But there is a bunch of non-DD people that strongly want to use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josselin Mouette wrote:
Actually I don’t think we should recommend testing at all to desktop
users.
Why?
Except during freeze times, I find unstable to be much more
usable, and keep testing for (non-production) servers.
IMHO, there is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julien BLACHE wrote:
I'd argue about that official thing that people have been using to
qualify d-d-a. It's an announce list for developers, by
developers. I'm not sure what's official in there. I'd tend to say
anything official is project
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Romain Beauxis wrote:
Le Thursday 18 December 2008 16:37:38 Johannes Wiedersich, vous avez écrit :
The point is it was an 'announcement' and it
was perceived as inappropriate (not only OT) by many.
I fully disagree
Pierre Habouzit wrote:
On Thu, Dec 18, 2008 at 10:28:09PM +, Russell Coker wrote:
The creation of a fake picture of Manoj wearing leather makes it clear that
Joss was intending to make an insinuation of homosexuality in order to
offend.
I'm really speechless... I mean, even from you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Romain Beauxis wrote:
Le Friday 19 December 2008 01:04:05 Johannes Wiedersich, vous avez écrit :
Joss, it is disappointing that after all that time since your faux pas
[1], you still seem to fail to understand that what might be acceptable
within
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loïc Minier wrote:
On Fri, Dec 19, 2008, Johannes Wiedersich wrote:
What slightly upsets me about the issue is not what happened, but rather
that the French appear so arrogant as to think what happened on a world
wide announcement is fine, just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Romain Beauxis wrote:
I start a discussion trying to explain how misunderstanding can happen and it
ends up claiming that french are arogant.
I am sorry, if I misunderstood your point as defending Joss's
announcement, while you were just trying to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Josefsson wrote:
Merely the number of distinct IP addresses downloading a particular
popular update from security.debian.org at least once would be
interesting.
Did you think about thousands of computers having 'private ips' with
some nat
Adeodato Simó wrote:
The weekend of February 14th is going to be our tentative target for
release.
Please, don't release before ready, but actually about half an hour
before that date would be more fun:
At 23:31:30 UTC on February 13, 2009, a celebration is expected as the
Unix time number
David Paleino wrote:
As someone noted on debian-italian, one second later would be just as cool:
$ factor 1234567891
1234567891: 1234567891
(i.e. it's a prime number)
From my quick check, these events don't seem to be so rare:
$ for i in $(seq 1234567890 $[1234567890+3600]); \
do factor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-03 19:59, Pierre Habouzit wrote:
On Tue, Jun 03, 2008 at 04:18:46PM +, Joey Hess wrote:
Pierre Habouzit wrote:
No it's not. The principal goal of testing is to evaluate what would
be our next stable if we tried to release *RIGHT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-03 22:26, Josselin Mouette wrote:
Le mardi 03 juin 2008 à 21:06 +0200, Johannes Wiedersich a écrit :
As I've understood it so far, testing is for 'people trying to help the
developers by testing the software prior to release'. If too
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-04 14:09, Riku Voipio wrote:
...for a certain subclass of _powerusers_ who are willing to
walk through a minefield[1] using buggy software. For more typical
endusers, buggy and unreliable software is a just big source of
frustration.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-03 19:59, Pierre Habouzit wrote:
It depends of your definition of usable. I don't think it's usable on
a daily basis because:
FWIW, let the users decide what they use or want to use. I took a curde
estimate by counting what the readers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-04 16:11, Johannes Wiedersich wrote:
[1] search +testing +lenny on
The searches were performed without the '+' to have 'testing or lenny' etc.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-04 16:31, Charles Plessy wrote:
Our packages are free software, so imperfect ones removed from the
archive can be redistributed in third-party apt repository if there is a
niche for this. This way, the decisions of removal can be proven
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-04 20:34, Josselin Mouette wrote:
Le mercredi 04 juin 2008 à 17:13 +0200, Johannes Wiedersich a écrit :
update-manager
update-notifier
Update-manager *does* have an unfixed RC bug, and the GNOME team is too
busy currently to fix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-06-04 18:36, Pierre Habouzit wrote:
No it's not. A user that prefers to have broken software rather than
no software (if the option non broken software is absent) should use
unstable. I mean it.
You can easily use testing by default,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all!
One of my bug reports appears to have been closed by a s_p_a_m mail:
#325588: kile crashes on auto-save, incurring data loss
It has been closed by Theron Landers
[EMAIL PROTECTED] (reply to
[EMAIL PROTECTED]).
Their explanation is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-07-03 08:58, Lars Wirzenius wrote:
For unarchiving and un-closing, use the control bot
([EMAIL PROTECTED]).
I didn't know about the 'unarchive' command.
Thanks, everything is fine now!
Johannes
-BEGIN PGP SIGNATURE-
Version: GnuPG
On 2008-08-03 18:44, Frank Küster wrote:
I would like to solve a long-standing bug and finally make TeX aware
of libpaper and its system-wide paper size setting.
Good!
However, taking the intersection of paper sizes the different
program's configuration files accept as default, I end up with
On 2008-08-02 22:28, Steve Langasek wrote:
On Sat, Aug 02, 2008 at 04:48:14PM +, Jörg Sommer wrote:
Steve Langasek [EMAIL PROTECTED] wrote:
On Thu, Jul 31, 2008 at 09:27:10AM +, Jörg Sommer wrote:
[snip]
So, must these packages pre‐depend on awk?
No, but I think we may have a bug
On 08/09/2008 03:12 PM, Rudi Effe wrote:
[snip]
(4) missing eyecandiness: grey and simple icons, no rounded corners,
dominating dark grey, low percentage of area used for content/
information (too much frame).
Install gtk-qt-engine and configure it from control centre.
Johannes
$
On 08/18/2008 06:08 PM, thacrazze wrote:
Hallo,
in the Amarok package is a security issue
It is fixed in Amarok 1.4.10
(http://secunia.com/advisories/31418/,
http://amarok.kde.org/en/releases/1/4/10)
Please update the packages with the fix.
They already have been updated as to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frans Pop wrote:
Holger Levsen wrote:
But I also think the acknowledgement mail should contain the information
that the submitter is not being subscribed by default and how s/he can
subscribe.
IMHO this is very wrong: the user has already taken
HXC wrote:
I also wondered what the community finds about the colours and layout
used for the website Does it need to be upgraded? Do find a new layout
or other colours more appealing? If so what do you have in mind? Or do
you think the current theme is just fine?
The current theme and
43 matches
Mail list logo
