Re: Bug#637351: ITP: urfkill -- urfkill is a daemon for the management of the radio killswitches.

2011-08-11 Thread Keng-Yu Lin
2011/8/11 Karl Goetz :
> Hi,
> How does it differ from rfkill, already in the archive? Perhaps the
> description could be updated to make this clear.
> thanks,
> kk
>

"rfkill" package in the archive is just a simple utility for switch
on/off the RF device.
urfkill handles the hotkeys (KEY_WLAN, KEY_BLUETOOTH, KEY_RFKILL, etc)
and can be configurable to behave differently on the key pressed.
Say, one may like the bluetooth to be switched off too on KEY_WLAN,
whereas in fact KEY_WLAN is for Wifi only, at least literally.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMe48JjCmqp0tPXAZjU4vhurFH2V1XG_DcfyFFk7T=zc4zc...@mail.gmail.com



Bug#637422: ITP: libaacs -- free-and-libre implementation of AACS

2011-08-11 Thread Alessio Treglia
Package: wnpp
Severity: wishlist
Owner: Alessio Treglia 

* Package name: libaacs
  Version : 0~20110623.git964342f
  Upstream Author : libaacs-devel mailing list 
* URL : http://www.videolan.org/developers/libaacs.html
* License : LGPL
  Programming Lang: C
  Description : free-and-libre implementation of AACS

 libaacs is a research project to implement the Advanced Access Content
 System specification. This research project provides, through an
 open-source library, a way to understand how the AACS works.
 Features:
  * Portability: Currently supported platforms are GNU/Linux, Windows,
MacOS X. The main dependency is libgcrypt for all cryptographic
functions.
  * Freedom: libaacs is released under a Free Software license, ensuring
it will stay free.
  * Legal: libaacs does not include any key or certificate and respects
copyright.
 .
 This package doesn't provide any key or certificate that could be used
 to decode encrypted copyrighted material.
 .
 This package provides the shared library.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110811094706.15316.14929.reportbug@alessio-laptop



mentors.debian.net runs the debexpo code now

2011-08-11 Thread Asheesh Laroia

Hello lovely debian-devel folks,

Thanks to huge work by Johnny Lamb, Christoph Haas, Jan Dittberner, Kalle 
Söderman, Serafeim Zanikolas, David Paleino, and Paul Wise, we have had a 
alpha-level product called Debexpo that can replace mentors.debian.net as 
the place we do package review for new contributors in Debian.


About a year ago, we began the process to revive the project. Andrey 
Rahmatullin (wRAR), Arno Töll, Wolodja Wentland, and I have finally 
finished it. Christine Spang (along with SIPB at MIT) put together the 
virtual machine that runs it. Thanks to many others who have provided 
advice and ideas.


It's live: http://mentors.debian.net/

The big differences between this and the old code are:

* Maintainable codebase

* Ability to see package quality on the package page -- see e.g. 
http://expo.debian.net/package/trafficserver


* Ability to leave comments on the web, and subscribe to receive email 
updates about packages


* Ability to write new plugins that do new kinds of quality checks

* Beautiful new design, based on main Debian.org layout (idea thanks to 
Francesca Ciceri)


* Christoph Haas can finally stop worrying that it'll never happen.

Finishing this coding and migration has been the biggest single thing I've 
been doing in my life for the past three or four weeks, so I am now going 
to take a bit of a break from it. I will try to advise and make sure that 
the community grows.


Huge props to Arno for not only excellent hacking, but fantastic work in 
getting new contributors.


http://wiki.debian.org/Debexpo explains where to find the bug tracker and 
mailing list.


There is surely more work to be done -- changing strings, updating more 
docs, and so forth. You can find us on #debexpo and also our bug tracker.


P.S. Johnny Lamb's original code is actually of pretty high quality. Huge 
thanks to him for that; the logging and the clear file layout helped us as 
immensely.


-- Asheesh.

Re: mentors.debian.net runs the debexpo code now

2011-08-11 Thread Paul Wise
On Thu, Aug 11, 2011 at 1:03 PM, Asheesh Laroia wrote:

> Thanks to huge work by Johnny Lamb, Christoph Haas, Jan Dittberner, Kalle
> Söderman, Serafeim Zanikolas, David Paleino, and Paul Wise, we have had a
> alpha-level product called Debexpo that can replace mentors.debian.net as
> the place we do package review for new contributors in Debian.

Congrats to everyone who was involved in this project, it is a huge
achievement to get this done!

I personally am looking forward to the metrics and sponsor <-> matching feature:

http://wiki.debian.org/DebianMentorsNet#Metrics

I might actually start doing sponsorship again if this were implemented.

Any volunteers?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6FYV=VJ=2ir_t3sjdh5+tkda1a-him-qhzwyl3mjza...@mail.gmail.com



Bug#637454: RFP: bluegriffon -- Next Generation WYSIWYG HTML editor based on Gecko

2011-08-11 Thread Axel Beckert
Package: wnpp
Severity: wishlist

* Package name: bluegriffon
  Version : 1.1.1
  Upstream Author : Disruptive Innovations, 
http://www.disruptive-innovations.com/
Daniel Glazman 
Laurent Jouanneau 

* URL or Web page : http://www.bluegriffon.org/
* License : MPL 1.1, GPL 2, LGPL 2.1; some graphics also CC-SA
  Description : Modern WYSIWYG HTML editor based on Gecko

>From the website:

  BlueGriffon is a new WYSIWYG content editor for the World Wide
  Web. Powered by Gecko, the rendering engine of Firefox 4, it's a
  modern and robust solution to edit Web pages in conformance to the
  latest Web Standards.

  BlueGriffon is an intuitive application that provides Web authors
  (beginners or more advanced) with a simple User Interface allowing to
  create attractive Web sites without requiring extensive technical
  knowledge about Web Standards.

  Because Gecko lives inside BlueGriffon, the document you edit will
  look exactly the same in Firefox 4. Advanced users can always use the
  Source View to hard-code their page.

  BlueGriffon is available in English, Dutch, French, Czech, German,
  Hebrew, Italian, Japanese, Korean, Simplified Chinese, Spanish and
  Traditional Chinese

There's also a "needs-packaging" bug report for Ubuntu:

  https://bugs.launchpad.net/ubuntu/+bug/815498

The team of GetDeb.net already built packages of BlueGriffon 1.1.1:

  http://www.getdeb.net/software/BlueGriffon
  https://bugs.launchpad.net/getdeb.net/+bug/820730



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874o1of176@kiva6.ethz.ch



Re: Bug#637454: RFP: bluegriffon -- Next Generation WYSIWYG HTML editor based on Gecko

2011-08-11 Thread Mike Hommey
On Thu, Aug 11, 2011 at 04:54:37PM +0200, Axel Beckert wrote:
> Package: wnpp
> Severity: wishlist
> 
> * Package name: bluegriffon
>   Version : 1.1.1
>   Upstream Author : Disruptive Innovations, 
> http://www.disruptive-innovations.com/
> Daniel Glazman 
> Laurent Jouanneau 
> 
> * URL or Web page : http://www.bluegriffon.org/
> * License : MPL 1.1, GPL 2, LGPL 2.1; some graphics also CC-SA
>   Description : Modern WYSIWYG HTML editor based on Gecko
> 
> >From the website:
> 
>   BlueGriffon is a new WYSIWYG content editor for the World Wide
>   Web. Powered by Gecko, the rendering engine of Firefox 4, it's a
>   modern and robust solution to edit Web pages in conformance to the
>   latest Web Standards.
> 
>   BlueGriffon is an intuitive application that provides Web authors
>   (beginners or more advanced) with a simple User Interface allowing to
>   create attractive Web sites without requiring extensive technical
>   knowledge about Web Standards.
> 
>   Because Gecko lives inside BlueGriffon, the document you edit will
>   look exactly the same in Firefox 4. Advanced users can always use the
>   Source View to hard-code their page.
> 
>   BlueGriffon is available in English, Dutch, French, Czech, German,
>   Hebrew, Italian, Japanese, Korean, Simplified Chinese, Spanish and
>   Traditional Chinese
> 
> There's also a "needs-packaging" bug report for Ubuntu:
> 
>   https://bugs.launchpad.net/ubuntu/+bug/815498
> 
> The team of GetDeb.net already built packages of BlueGriffon 1.1.1:
> 
>   http://www.getdeb.net/software/BlueGriffon
>   https://bugs.launchpad.net/getdeb.net/+bug/820730

Yay, one more copy of the gecko engine :(

Mike


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110811151756.ga11...@glandium.org



Re: Bug#637454: RFP: bluegriffon -- Next Generation WYSIWYG HTML editor based on Gecko

2011-08-11 Thread Axel Beckert
Hi Mike,

Mike Hommey wrote:
> >   Description : Modern WYSIWYG HTML editor based on Gecko
> 
> Yay, one more copy of the gecko engine :(

Your fear it won't be able to run it with xulrunner directly like e.g.
Conkeror does?

On a first glance it looked like a xulrunner application, but it seems
as if it has a xulrunner application embedded. At least upstream's
code repo includes an application.ini, but the upstream tar ball also
ships a libxul.so... Haven't looked closer yet, though.

The upstream author seems to be the author of the Netscape Composer,
too, so I don't wonder about his choice of platform at all. :-)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110811154640.gq29...@sym.noone.org



Re: Bug#637454: RFP: bluegriffon -- Next Generation WYSIWYG HTML editor based on Gecko

2011-08-11 Thread Mike Hommey
On Thu, Aug 11, 2011 at 05:46:41PM +0200, Axel Beckert wrote:
> Hi Mike,
> 
> Mike Hommey wrote:
> > >   Description : Modern WYSIWYG HTML editor based on Gecko
> > 
> > Yay, one more copy of the gecko engine :(
> 
> Your fear it won't be able to run it with xulrunner directly like e.g.
> Conkeror does?
> 
> On a first glance it looked like a xulrunner application, but it seems
> as if it has a xulrunner application embedded. At least upstream's
> code repo includes an application.ini, but the upstream tar ball also
> ships a libxul.so... Haven't looked closer yet, though.
> 
> The upstream author seems to be the author of the Netscape Composer,
> too, so I don't wonder about his choice of platform at all. :-)

AFAIK, it's quite tied to the underlying engine, but I haven't heard
Daniel's plans wrt the rapid release of Firefox. I'm not sure, for
example, that the current BG works with the 5.0 engine instead of 4.0.

Mike


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110811160749.ga12...@glandium.org



Re: The archive now supports xz compression

2011-08-11 Thread Adam Borowski
On Thu, Aug 11, 2011 at 05:12:36PM +0200, Ansgar Burchardt wrote:
> Hi,
> 
> The archive software now accepts packages using xz for compression in
> addition to gzip and bzip2 for both source and binary packages.

Hurray!

> please only use xz (or bzip2 for that matter) if your
> package really profits from its usage (for example, it provides a
> significant space saving). While those methods may compress better they
> often use more CPU time to do so and a very small decrease in package
> size is hardly worth the extra effort placed on slower systems.

This is very bad advice.

Do you remember my joke package "goodbye" less than two weeks ago?  If you
compared the optimized[1] debhelper-less dpkg-less code to standard "slow"
debhelper, you lose 2.6 seconds per package[2].

In that time you can compress 8MB (and decompress that in 0.09s).

Thus, if you care about amounts of CPU time that small, you can as well go
through the whole archive replacing debhelper with "goodbye", for all
packages smaller than that 8MB.

The cost is roughly linear, too -- so compressing a 20KB package costs about
nothing.

And what do we gain in return?  A massive decrease of the archive size --
both disk space and bandwidth.  Regular packages compress twice as much with
xz as with gzip, with uncompressible data in the mix the average was 2/3 for
amd64 CD1.


Thus, I'd strongly recommend just compressing everything with xz, on all
architectures.  Preferably, as a default in dpkg-dev.


> Think of both user systems and the Debian buildds which will waste more
> time - an especially bad problem on slower architectures.

The gain is especially meaningful for slower architectures, as they tend to
have less disk space and slower network links (arm tends to be used in
phones).  No extra memory is needed -- decompression is not done in parallel
with memory-hungry stages of dpkg's work.  The decompression, merely 2.5
times slower than with gzip, is a tiny fraction of what dpkg takes.


> Please remember that packages in the base system[1] (and dependencies)
> *must* currently use gzip as otherwise debootstrap will be unable to
> install a system.
>
> 1: Meaning everything with Priority: required.

I'm not as strongly opinionated here, but I guess decreasing the size of d-i
images would be a huge win as well.



Meow!

[1]. Three calls of system() could be avoided for little effort and two more
for substantial effort -- and all of them could be turned into execve(), but
otherwise, it's pretty much as fast as you can get.  With package build time
below a single disk seek, further optimizations are pointless.  The point of
"goodbye" was abuse of policy and buzzword compliancy, not speed.

[2]. Debhelper costs are surprisingly constant, even between a "copy a
single file" package and full-blown autoconf+C ones.

-- 
1KB // Yo momma uses IPv4!


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110811183010.ga27...@angband.pl



Re: The archive now supports xz compression

2011-08-11 Thread Philipp Kern
On 2011-08-11, Adam Borowski  wrote:
>> Think of both user systems and the Debian buildds which will waste more
>> time - an especially bad problem on slower architectures.
> The gain is especially meaningful for slower architectures, as they tend to
> have less disk space and slower network links (arm tends to be used in
> phones).  No extra memory is needed -- decompression is not done in parallel
> with memory-hungry stages of dpkg's work.  The decompression, merely 2.5
> times slower than with gzip, is a tiny fraction of what dpkg takes.

It takes a lot longer to compress on slower architectures (i.e. on the
buildds), though.  You could've built a whole package in that time.  (Resorting
to your style of argument.)

>> Please remember that packages in the base system[1] (and dependencies)
>> *must* currently use gzip as otherwise debootstrap will be unable to
>> install a system.
>>
>> 1: Meaning everything with Priority: required.
>
> I'm not as strongly opinionated here, but I guess decreasing the size of d-i
> images would be a huge win as well.

You cannot debootstrap it anymore.  I can hardly call that a win.  (So we'd
need to wait a few releases for that.)

> [1]. Three calls of system() could be avoided for little effort and two more
> for substantial effort -- and all of them could be turned into execve(), but
> otherwise, it's pretty much as fast as you can get.  With package build time
> below a single disk seek, further optimizations are pointless.  The point of
> "goodbye" was abuse of policy and buzzword compliancy, not speed.

It compiles the same script multiple times during build.

Kind regards
Philipp Kern


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnj48coe.a7f.tr...@kelgar.0x539.de



Re: The archive now supports xz compression

2011-08-11 Thread Raphael Hertzog
Hi,

On Thu, 11 Aug 2011, Adam Borowski wrote:
> Thus, I'd strongly recommend just compressing everything with xz, on all
> architectures.  Preferably, as a default in dpkg-dev.

I am very much in favor of this as well but after having discussed this
at debconf with Colin Watson and Joey Hess, I'm not going to change this
immediately.

As Ansgar mentionned, it creates a new requirement: for debootstrap to work
xz must be present and it's currently not present in debian-installer.

So changing the default in dpkg-dev would either require to hardcode
gzip for all "base" packages or accept xz as a new dependency for
debootstrap.

The set of "base" package is not clearly defined, it's roughly "all
required packages and their dependencies" but this can't be really
automated and can theoretically change at the whims of ftpmasters
since the priorities are under the control of ftpmasters.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634248

Since hardcoding gzip for base packages seems to be a bit brittle,
we need to work towards allowing xz usage in debian-installer and accept
it as a dependency for deboostrap on non-Debian systems (I don't think
it's a big issue, xz is portable and is more and more widely used).

I guess that a first step is to have an xz udeb...

Would you like to drive a release goal to have all packages of DVD1
use XZ compressions ?

1/ Ensure XZ support is integrated in debian-installer (and deboostrap
   fixed to add it as a dependency).
2/ Wait until we update dpkg to use XZ by default.
3/ Ensure all packages useful in DVD1 are updated or bin-nmued
   before the freeze.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
  ▶ http://RaphaelHertzog.fr (Français)


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110811191955.gh6...@rivendell.home.ouaza.com



Re: mentors.debian.net runs the debexpo code now

2011-08-11 Thread Raphael Hertzog
Hi Asheesh,

thank you for your work on this new version! It's really a big step
forward.

On Thu, 11 Aug 2011, Asheesh Laroia wrote:
> It's live: http://mentors.debian.net/

The PTS cron mail now gives me this message:
| Downloading 
http://mentors.debian.net/debian/dists/unstable/non-free/source/Sources.gz
| failed, Sources-mentors_non-free.gz is stale now

Can you ensure it's always generated (even if empty) ?

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
  ▶ http://RaphaelHertzog.fr (Français)


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110811193157.ga7...@rivendell.home.ouaza.com



Bug#637476: ITP: libdata-section-simple-perl -- Perl module for reading data from __DATA__

2011-08-11 Thread Fabrizio Regalli
Package: wnpp
Owner: Fabrizio Regalli 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org

* Package name: libdata-section-simple-perl
  Version : 0.02
  Upstream Author : Tatsuhiko Miyagawa 
* URL : http://search.cpan.org/dist/Data-Section-Simple/
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Perl module for reading data from __DATA__

Data::Section::Simple is a simple module to extract data
from __DATA__ section of the file.
This module does not implement caching (yet) which means
in every get_data_section or get_data_section($name) this
module seeks and re-reads the data section. If you want
to avoid doing so for the better performance, you should
implement caching in your own caller code.



signature.asc
Description: This is a digitally signed message part


Re: The archive now supports xz compression

2011-08-11 Thread Colin Watson
On Thu, Aug 11, 2011 at 09:19:55PM +0200, Raphael Hertzog wrote:
> As Ansgar mentionned, it creates a new requirement: for debootstrap to work
> xz must be present and it's currently not present in debian-installer.

The main thing I consider to be difficult is that putting xz-compressed
packages in the base system requires people on foreign systems to have
an xz decompressor available.  To a large extent this is outside our
control.

> Since hardcoding gzip for base packages seems to be a bit brittle,
> we need to work towards allowing xz usage in debian-installer and accept
> it as a dependency for deboostrap on non-Debian systems (I don't think
> it's a big issue, xz is portable and is more and more widely used).

Can you quantify that?  I don't have hard numbers for the non-Debian
systems where people report running debootstrap; perhaps you do ...

> I guess that a first step is to have an xz udeb...

No.  busybox already has an unxz applet, so if we choose to do this then
we should enable that applet in busybox-udeb, not add a separate udeb.

-- 
Colin Watson   [cjwat...@debian.org]


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110811225511.ga20...@riva.dynamic.greenend.org.uk



Re: Bug#634015: Proposition to team-maintain m2crypto.

2011-08-11 Thread Charles Plessy
Le Wed, Aug 10, 2011 at 12:17:04PM +, Philipp Kern a écrit :
> On 2011-08-10, Charles Plessy  wrote:
> >   
> > 
> >   # Matt Rodriguez, LBNL
> >   #Copyright (c) 2003, The Regents of the University of California,
> >   #through Lawrence Berkeley National Laboratory
> >   #(subject to receipt of any required approvals from the U.S. Dept. of 
> > Energy).
> >   #All rights reserved.
> >   
> > 
> >
> > Of course, this file is not used at build time and is not distributed in our
> > binary packages, but if I understand well our procedures, I can not 
> > knowingly
> > upload a package that contains this file.
> >
> > Hence the question to the other developers: is it necessary to correct 
> > m2crypto
> > source package in Stable ?  Not that I am interested to do it – you know my
> > position on these files is that they should be documented but ignored 
> > otherwise
> > (see http://lists.debian.org/20100124144741.gd13...@kunpuu.plessy.org ).  So
> > if the answer is yes, can somebody volunteer to do the work ?
> 
> All I can say is "wtf".  You knowingly accept that Debian distributes
> undistributable files?  It's not that it's a non-free license that still 
> allows
> distribution, it's "All Rights Reserved".

In summary:

 - Somebody, not me, accepted the m2crypto package with this file in our 
archive.

 - I found this file and reported it.  I admit I did not realise immediately
   it was not redistributable at all.

 - You said ‘wtf’.

 - I contacted the file's author (whose new address was not easy to find), who
   confirmed it is intended to be resistributed under the same terms as the 
whole
   m2crypto package.

 - Problem solved.

I appologise for ranting about non-free files with the wrong example.  This was
inapproppriate, and I understand I lose credit for this.  But I do not think 
that
saying ‘wtf’ contributed at all to solve the real problem.

Cheers,

-- 
Charles


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110811234424.gd25...@merveille.plessy.net



Re: Bug#634015: Proposition to team-maintain m2crypto.

2011-08-11 Thread Charles Plessy
Dear all,

after clearing out possible copyright issues in some files of the m2crypto
source package, I am ready to upload an updated package.  I would like to
manage its sources in a VCS.  I originally thought about the Debian Python
Modules Team, but it only uses Subversion.  Here are the three possibilities I
see:

 - In python-modules, with Subversion, or
 - in collab-maint, with Git.

Dima or anybody else interested in participating, please let me know your
preferences.  Otherwise I think I will go for collab-maint with Git.

Have a nice day,

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110812002914.ga26...@merveille.plessy.net



sdh baca pengumumannya ?

2011-08-11 Thread Indri
PENGUMUMAN : 

Apapun Bisnis Anda Pasti Bisa Laris,
ikuti caranya di http://www.alatpromosi.co.cc





-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/02cf8459$40767$0ef93583668519@bambang-pc