Spezialveranstalter.

[Spezialveranstalter.]

Mana Tour ist in Istanbul-Izmir-Antalya ein Spezialveranstalter 
für Spezialreisen-Hotels-Gruppenreisen von Kultur und Bildungsreisen.Fuer 
Vereinen-Sportgruppen-Kirchen.
Wir sind spezialisiert auch auf Individualreisen für Familien und 
Familiefreizeiten.
*Kultur Reisen für alle Gebiete Tuerkei.
*Badeurlaub Hotel,s fuer Familien,Nur 5 Sterne All Inclusiv Hotels.
*Istanbul Reisen für die Gruppen.
*Nur Flug fuer alle Destination der Tuerkei.
*Sport Reisen als Trainingslagern.
Wir würden gern fuer sie/fuer ihre Kunden auch bedienen.
Mit Herzlichen Grüssen.
Ihr Mana Tour Team

Common handling of browser plugins?

[Fabian Greffrath]

Dear Debian developers!

At the time of this writing I have 3 packages installed that provide a
plugin for Mozilla-compatible browsers. 

These are:
- flashplugin-nonfree
- totem-mozilla
- java-gjc-compat-plugin

(1) As you can see, each of these packages follows a different naming
pattern which makes it difficult for the user to find the browser plugin
of his needs. I suggest to introduce a suffix which will be added to the
package name and makes clear that it contains a plugin. My suggestions
are 'foo-mozilla' or even better 'foo-browserplugin'.

(2) Another fact that disturbes my is that all of these packages contain
different plugin directories for the different browsers in Debian. 

These are:
flashplugin-nonfree:/usr/lib/mozilla/plugins
/usr/lib/mozilla-firefox/plugins
/usr/lib/firefox/plugins

totem-mozilla:  /usr/lib/xulrunner/plugins
/usr/lib/mozilla/plugins
/usr/lib/firefox/plugins

java-gjc-compat-plugin: /usr/lib/mozilla/plugins
/usr/lib/mozilla-firefox/plugins
/usr/lib/mozilla-snapshot/plugins

Please note the fact, that these directories are empty in the
flashplugin-nonfree and java-gjc-compat-plugin packages. The plugins are
linked in the postinst script via the alternatives system in the
java-gjc-compat-plugin package. In the flashplugin-nonfree package, the
plugin is downloaded in postinst via update-flashplugin and then linked
into the directories. 
In the totem-mozilla package, all linking is done before packaging, so
all the directories already contain the plugin.
I think a consensus should be found which plugin directories are to be
included in the package and how/when the plugin should be linked into
these directories.

(3) Another thing in which all those packages differ is the
recommendation and suggestion of compatible browsers:

flashplugin-nonfree suggests: mozilla-browser (>= 2:1.1) |
mozilla-firefox | firefox

totem-mozilla   recommends: epiphany-browser | www-browser

java-gjc-compat-plugin  does not recommend or suggest any browser

In my opinion this should be matched, too.

Thank you!

Nice greetings,
Fabian Greffrath
-- 
Fabian Greffrath
Institut für Experimentalphysik I
Ruhr-Universität Bochum
D-44780 Bochum

Raum:  NB 2/28
Tel.:  +49(234)32-27691
Fax:   +49(234)32-14170
Email: [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Moving /var/run to a tmpfs?

[Martin Wuertele]

* Marco d'Itri <[EMAIL PROTECTED]> [2006-09-16 20:20]:

> etch requires a 2.6 kernel too.
 
No. Debian won't provide a 2.4 kernel for etch but it works fine with
self built ones.

yours Martin
-- 
<[EMAIL PROTECTED]>  Debian GNU/Linux - The Universal Operating System
 guess "lp0 on fire" finally got taken literally..
[on 20.11.2002 satie.debian.org burnt down due to a fire in the Twente 
university in Enschede, NL]

Re: Common handling of browser plugins?

[Hendrik Sattler]

Am Montag 18 September 2006 11:00 schrieb Fabian Greffrath:
> (3) Another thing in which all those packages differ is the
> recommendation and suggestion of compatible browsers:
>
> flashplugin-nonfree suggests: mozilla-browser (>= 2:1.1) |
> mozilla-firefox | firefox
>
> totem-mozilla   recommends: epiphany-browser | www-browser
>
> java-gjc-compat-plugin  does not recommend or suggest any browser
>
> In my opinion this should be matched, too.

Not practical: for Konqueror, flashplugin-nonfree is somewhat usable (I hope 
that 0.9 gets better) but the other ones have better replacements in KDE 
(e.g. kaffeine) or can be directly used without plugin (java runtime 
environment).
They should only suggest with what they are known to work and be useful with.

I agree for the directories issues, though (although konqueror does not care).

HS

Re: Moving /var/run to a tmpfs?

[Martin Wuertele]

* Andreas Metzler <[EMAIL PROTECTED]> [2006-09-16 19:42]:

> It has been pointed out to me in  http://bugs.debian.org/387699
> that syvinit is going to move /var/run to a tmpfs to solve a long-standing
> issue, having some place to store state information before partitions
> are checked and mounted. (I do not know how they are going to handle
> the fact that /var/run is needed before /var is mounted, mount --move
> requires kernel 2.6 afaict.)
 
I prefere to have this optional, propably defaulting to yes as I don't
want to waste a single byte for /var/run or /var/lock on low memory
systems (which run 2.4 for the smaller memory footprint) so I can still
change it without manual intervention.

yours Martin
-- 
<[EMAIL PROTECTED]>  Debian GNU/Linux - The Universal Operating System
 oh oh, can i get we.are.the.knights.who.say.ni ?
 .no


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#388052: mplayer-nogui: mplayer segfaults (ld at fault)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 388052 general
Bug#388052: mplayer-nogui: mplayer segfaults (ld at fault)
Warning: Unknown package 'mplayer-nogui'
Bug reassigned from package `mplayer-nogui' to `general'.

> --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

List 'tompaine' closed to public posts

[NIU Sociology Listserver]

Sorry, but your posting is being returned to you.

The list is temporarily restricted.

If your post is substantive, dealing with NIU Faculty/Staff  issues, it will 
be forwarded to the list. If it is intended as private email, it will be 
forwarded accordingly.
P

If you wish to subscribe to TOMPAINE, send a message that says:
subscribe tompaine 

Send this to:  [EMAIL PROTECTED]

If you have questions, contact:
  
Herb Rubin at: [EMAIL PROTECTED]


---
Listar v1.0.0 - job execution complete.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Creating packages with debconf

[Rodrigo Tavares]

Hello,

I just configured the tree with debconf, by create a
package, but when i try to build a package the
makefile  is required. I choose single package.

Skipping copying to script-gera-banco-1.4.orig since
script-gera-dbar-1.4.orig exists.
Currently there is no top level Makefile. This may
require additional tuning.
You already have a debian/ subdirectory in the source
tree. dh_make will not try to overwrite anything.

The intetion is, my package execute the script (create
bd in postgresql) and remove this script, and make
some a questions.
How I can to create Makefile in this case ?

best regards,

Faria








___ 
Você quer respostas para suas perguntas? Ou você sabe muito e quer compartilhar 
seu conhecimento? Experimente o Yahoo! Respostas !
http://br.answers.yahoo.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Creating packages with debconf

[Tim Dijkstra]

On Mon, 18 Sep 2006 11:47:34 + (GMT)
Rodrigo Tavares <[EMAIL PROTECTED]> wrote:

> Hello,
> 
> I just configured the tree with debconf, by create a
> package, but when i try to build a package the
> makefile  is required. I choose single package.
> 
> Skipping copying to script-gera-banco-1.4.orig since
> script-gera-dbar-1.4.orig exists.
> Currently there is no top level Makefile. This may
> require additional tuning.
> You already have a debian/ subdirectory in the source
> tree. dh_make will not try to overwrite anything.
> 
> The intetion is, my package execute the script (create
> bd in postgresql) and remove this script, and make
> some a questions.
> How I can to create Makefile in this case ?

I think you're confused, you're mixing up debconf, dh_make and
dpkg-buildpackage.

You can use dh_make only to setup some defaults for your package-to-be,
it does _not_ build a package.

Have you read http://www.debian.org/doc/maint-guide/ ?

I suggest you start there.


grts Tim


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ITP: btsco -- ALSA drivers and daemons for using bluetooth audio devices

[Filippo Giunchedi]

On Sun, Sep 17, 2006 at 12:59:27PM +0900, Nobuhiro Iwamatsu wrote:
> Package: wnpp
> Owner: Nobuhiro Iwamatsu <[EMAIL PROTECTED]>
> Severity: wishlist
> 
> * Package name: btsco

you might want to have a look at pkg-bluetooth ( 
http://wiki.debian.org/Bluetooth ) as well. Eventually it might be the case to 
include btsco under the pkg-bluetooth umbrella.

thanks,
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:

If there is any better use for being famous and respected than using
that status to question orthodoxy, I haven't found it yet.
-- Eric S. Raymond


signature.asc
Description: Digital signature

Re: Common handling of browser plugins?

[Loïc Minier]

On Mon, Sep 18, 2006, Fabian Greffrath wrote:
> - flashplugin-nonfree
> - totem-mozilla
> - java-gjc-compat-plugin

> (1) As you can see, each of these packages follows a different naming
> pattern which makes it difficult for the user to find the browser plugin
> of his needs. I suggest to introduce a suffix which will be added to the
> package name and makes clear that it contains a plugin. My suggestions
> are 'foo-mozilla' or even better 'foo-browserplugin'.

 Sure, that's an interesting point.  We discussed this in #gnome-debian
 when the totem-mozilla plugin was introduced.  It was hard to find a
 good name because the plugin works in firefox, mozilla, xulrunner, and
 seamonkey based browsers.  Mozilla seemed a good name as being the
 distributor of all these sources.  Xulrunner also sounded good, since
 it's used to build totem, but it would sound strange for people using
 firefox or even for ubuntu which probably continues buidling against
 firefox-dev.

 You might also encounter conflicting policies: e.g. what if the plugin
 is written in Java?  Does it need to follow the mozilla plugin naming
 policy of the java one?

> (2) Another fact that disturbes my is that all of these packages contain
> different plugin directories for the different browsers in Debian. 
> These are:
> flashplugin-nonfree:  /usr/lib/mozilla/plugins
>   /usr/lib/mozilla-firefox/plugins
>   /usr/lib/firefox/plugins

 mozilla-firefox sounds obsolete and duplicated.

> totem-mozilla:/usr/lib/xulrunner/plugins
>   /usr/lib/mozilla/plugins
>   /usr/lib/firefox/plugins

 Upstream told me once that installing in /usr/lib/mozilla/plugins would
 be enough, but it's not: I think firefox only loads plugins from it's
 plugins dir.  Xulrunner based browsers will obviously only load plugins
 searched by the libxul library, so /usr/lib/xulrunner/plugins I
 suppose.  Mozilla is for the aging mozilla-browser, soon to be removed.

 It seems correct to me.

> java-gjc-compat-plugin:   /usr/lib/mozilla/plugins
>   /usr/lib/mozilla-firefox/plugins
>   /usr/lib/mozilla-snapshot/plugins

 mozilla-firefox should be firefox, mozilla-snapshot is probably
 obsolete as the package was removed.

> In the totem-mozilla package, all linking is done before packaging, so
> all the directories already contain the plugin.

 Yes, the plugin is below /usr/lib/totem, and regular symlinks are
 shipped in the .deb.

> (3) Another thing in which all those packages differ is the
> recommendation and suggestion of compatible browsers:
> flashplugin-nonfree   suggests: mozilla-browser (>= 2:1.1) |
> mozilla-firefox | firefox

 mozilla-firefox is probably obsolete, and this doesn't permit e.g.
 xulrunner based browsers (such as epiphany, galeon...).

> totem-mozilla recommends: epiphany-browser | www-browser

 Sadly, there's no "mozilla-browser" provides.  There's www-browser, and
 gnome-www-browser.  I suppose we should aim at x-www-browser as well.
 Perhaps a provide expressing "mozilla-pluginaware-browser" would be
 nice?


 Thanks for looking into this, it would be nice if this could result in
 some lintian warnings and / or bug reports if there's consensus on
 these.

   Bye,

-- 
Loïc Minier <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Creating packages with debconf

[Rodrigo Tavares]

Hello Tim, 

Yes I read this link, and i take a example of
changelog. After, the error messange was the same.
Then  i try the below command.

sky:~/script-gera-db-1.4# dh_gencontrol
dh_gencontrol: Compatibility levels before 4 are
deprecated.
found eof where expected more change data or trailer
at /usr/lib/dpkg/parsechangelog/debian line 156,
 line 5.
dpkg-gencontrol: error: syntax error in parsed version
of changelog at line 0: empty file
dh_gencontrol: command returned error code 6528

How I can to resolve it ?

Best regards.

Faria

--- Tim Dijkstra <[EMAIL PROTECTED]> escreveu:

> On Mon, 18 Sep 2006 11:47:34 + (GMT)
> Rodrigo Tavares <[EMAIL PROTECTED]> wrote:
> 
> > Hello,
> > 
> > I just configured the tree with debconf, by create
> a
> > package, but when i try to build a package the
> > makefile  is required. I choose single package.
> > 
> > Skipping copying to script-gera-banco-1.4.orig
> since
> > script-gera-dbar-1.4.orig exists.
> > Currently there is no top level Makefile. This may
> > require additional tuning.
> > You already have a debian/ subdirectory in the
> source
> > tree. dh_make will not try to overwrite anything.
> > 
> > The intetion is, my package execute the script
> (create
> > bd in postgresql) and remove this script, and make
> > some a questions.
> > How I can to create Makefile in this case ?
> 
> I think you're confused, you're mixing up debconf,
> dh_make and
> dpkg-buildpackage.
> 
> You can use dh_make only to setup some defaults for
> your package-to-be,
> it does _not_ build a package.
> 
> Have you read http://www.debian.org/doc/maint-guide/
> ?
> 
> I suggest you start there.
> 
> 
> grts Tim
> 
> 
> -- 
> To UNSUBSCRIBE, email to
> [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> 
> 




___ 
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale 
o discador agora! 
http://br.acesso.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: (proposed) Mass bug filing for debconf "abuse" by using low|medium priority debconf notes?

[Nathanael Nerode]

Joey Hess wrote:

> Christian Perrier wrote:
>> In short, a note should only be used for IMPORTANT stuff, so actually
>> all debconf notes should be priority highor should not exist!
> 
> It's better to simply remove them all: If it's an error, use the new
> error data type, which will always be displayed no matter the priority.
> If it's not an error, put it in NEWS.Debian, README.Debian, etc.
> 
> The only thing stopping me from making debconf notes a no-op is the note
> in d-i's nobootloader, which is a fairly legitimate note (not error), that
> can't really be put anywhere else, and possibly the partman help note
> (though noone reads that note).

Hmm.  Any time a package has to tell the user "You need to do something
manually.  It's not being done automatically because we haven't figured out
how to do that, but it's really really important to do it manually"
-- then a high-priority debconf note is appropriate.

Frankly, the kernel's "You NEED to restart your computer SOON" message is
a good example, if it's telling the truth.  But that cheats by not using 
debconf.

Upgrades which require programs to be restarted should do it automatically.
But if for some obscure reason they can't, then a high-priority note is
reasonable.

Upgrades from really-messed-up versions may also require people to do
something manually to clean up from the messed-up version.

-- 
Nathanael Nerode  <[EMAIL PROTECTED]>

Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...

Re: Creating packages with debconf

[Tim Dijkstra]

On Mon, 18 Sep 2006 13:54:40 + (GMT)
Rodrigo Tavares <[EMAIL PROTECTED]> wrote:

> Hello Tim, 
> 
> Yes I read this link, and i take a example of
> changelog. After, the error messange was the same.
> Then  i try the below command.
> 
> sky:~/script-gera-db-1.4# dh_gencontrol
> dh_gencontrol: Compatibility levels before 4 are
> deprecated.
> found eof where expected more change data or trailer
> at /usr/lib/dpkg/parsechangelog/debian line 156,
>  line 5.
> dpkg-gencontrol: error: syntax error in parsed version
> of changelog at line 0: empty file
> dh_gencontrol: command returned error code 6528
> 
> How I can to resolve it ?

Use dch to generate your changelog.

It's better to ask these questions at [EMAIL PROTECTED], btw.

And really, please read the new maintainers guide!

grts Tim


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Creating packages with debconf

[Tim Dijkstra]

On Mon, 18 Sep 2006 13:54:40 + (GMT)
Rodrigo Tavares <[EMAIL PROTECTED]> wrote:

> Hello Tim, 
> 
> Yes I read this link, and i take a example of
> changelog. After, the error messange was the same.
> Then  i try the below command.
> 
> sky:~/script-gera-db-1.4# dh_gencontrol
> dh_gencontrol: Compatibility levels before 4 are
> deprecated.
> found eof where expected more change data or trailer
> at /usr/lib/dpkg/parsechangelog/debian line 156,
>  line 5.
> dpkg-gencontrol: error: syntax error in parsed version
> of changelog at line 0: empty file
> dh_gencontrol: command returned error code 6528
> 
> How I can to resolve it ?

Use dch to generate your changelog.

It's better to ask these questions at [EMAIL PROTECTED], btw.

And really, please read the new maintainers guide!

grts Tim


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: (proposed) Mass bug filing for debconf "abuse" by using low|medium priority debconf notes?

[Frans Pop]

On Monday 18 September 2006 16:36, Nathanael Nerode wrote:
> Frankly, the kernel's "You NEED to restart your computer SOON" message
> is a good example, if it's telling the truth.  But that cheats by not
> using debconf.

Oh yes it does!
When have you last done a kernel upgrade in testing/unstable? ;-)


pgp89qPM3iRQy.pgp
Description: PGP signature

Re: Orphaning my packages

[Nathanael Nerode]

David Moreno Garza wrote:

> Hello,
> 
> I'll be taking a long vacation of Debian and free software activity
> for the next couple of months for personal reasons. Because of that,
> I'm orphaning my non-comaintained packages. I really think those
> packages shouldn't make it to Etch with a non attending maintainer,
> just like I'm beginning to become (I already orphaned some of them in
> the last couple of months). Once I get more free time or motivation
> to work on my packages, I'll be coming back, but since that's not the
> case now, I'm stepping back for a while so I don't interfere with the
> project.
> 
> If you think you could adopt some of the packages, feel free to do it
> (filling an ITA would be nice). Just talk to the Debian Perl Group
> first, if thinking on adopting some of the Perl modules; talk first
> to the pkg-ruby-extras groups if thinking on adopting some of the
> ruby modules, also.

This is such a cool thread!

Not only have you responsibly orphaned packages when you don't have time to
maintain them, but most of them were picked up very quickly!  And some have
picked up comaintainers almost immediately, which is even better!

(Sorry, I'm not picking any of them up.)

The ones which haven't been picked up either with ITAs or in this thread,
and which aren't lib*-perl or lib*-ruby, are:

* dlume
* fpm
* gxmms
* kipina
* revolution
* rxvt
* sendemail
* 
* wallpaper-tray

(There are quite a few more -perl and -ruby packages, but I'm not quite sure
which ones have been picked up.)

I will note that rxvt has 1234 popcon installs, so if anyone's going for
brownie points

-- 
Nathanael Nerode  <[EMAIL PROTECTED]>

Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: gnome 1 packages up for adoption

[Nathanael Nerode]

Steve Langasek wrote:
 
> Hmm, I've looked over the packages mentioned above, and none of the others
> seem to be removable.  I think someone's been sneaking new GNOME1 packages
> into the archive when I wasn't looking. :)
> 
> libcapplet is closest, only python-gnome-1.2 as a reverse-dep after the
> other libs we can remove are removed.  python-gnome-1.2 is QA-maintained
> as well.

gal0.x and bonobo should also be removable.

I think I covered the GNOME 1 status pretty well at
http://lists.debian.org/debian-qa/2006/09/msg00038.html.

gnome-print, python-gnome, and oaf are pretty close to removable,
but not quite.  libglade, gnome-libs, and imlib are definitely hanging
around.

Adopters welcome for any of the six.  :-)

-- 
Nathanael Nerode  <[EMAIL PROTECTED]>

Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Orphaning my packages

[gregor herrmann]

On Mon, 18 Sep 2006 10:58:31 -0400, Nathanael Nerode wrote:

> (There are quite a few more -perl and -ruby packages, but I'm not quite sure
> which ones have been picked up.)

The lib*-perl packages are all already in the Debian Perl Group's svn
repository and will be uploaded soon.

gregor
 
-- 
 .''`.   http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4
 : :' :  debian: the universal operating system - http://www.debian.org/
 `. `'   member of https://www.vibe.at/ | how to reply: http://got.to/quote/
   `-NP: Django Reinhardt: I'll see you in my dreams


signature.asc
Description: Digital signature

Re: Orphaning my packages

[Steve Kemp]

On Mon, Sep 18, 2006 at 10:58:31AM -0400, Nathanael Nerode wrote:

> The ones which haven't been picked up either with ITAs or in this thread,
> and which aren't lib*-perl or lib*-ruby, are:
> 
> * 

  I'll take  since it hasn't been claimed.

Steve
-- 
Debian GNU/Linux System Administration
http://www.debian-administration.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Why not only support Sid and Testing?

[Michelle Konzack]

Am 2006-09-15 17:47:52, schrieb Hendrik Sattler:

> Thus, you can install xorg without installing discover.
> Do you always install with all recommends? That will pull in lots of useless 
> stuff...

No, I use only apt-get because I prefer Lite-Systems.
If I use recommends my system would not be

Dateisystem  1M-Blöcke   Benutzt Verfügbar Ben% Eingehängt auf
/dev/hda1  44957   368  14% /
/dev/hda3 1428   833   524  62% /tmp
/dev/hda5 2819  1073  1603  41% /usr
/dev/hda6  714   135   541  20% /var
/dev/hda7  17720   148  12% /var/log
samba3.private:/home
 67858 64611  3247  96% /home

Once I have tried to install the same Workststion on a Test-Machine
but including Recommends...  This would automaticale install KDE and
GNOME libs and much more using additional 800 MByte.

Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
Tamay Dogan Network
Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/6/6192519367100 Strasbourg/France   IRC #Debian (irc.icq.com)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Policy process (was: [Pkg-sysvinit-devel] Re: Moving /var/run to a tmpfs?)

[Kurt Roeckx]

On Sun, Sep 17, 2006 at 11:43:18AM -0700, Russ Allbery wrote:
> Copying the debian-policy list, since this conversation is basically about
> that.
> 
> Kurt Roeckx <[EMAIL PROTECTED]> writes:
> 
> > I don't think policy changes need to be seconded.  We have a policy team
> > that should decide on what comes in policy and what not.  Although, it
> > more looks like it's just 1 person doing all the work.
> 
> > I sometimes feel that they go to slow which changing things, and I'm not
> > really sure it's a good or bad thing.
> 
> > Some of those currently open bugs against the policy package, like your
> > ~ in version numbers, really shouldn't be a problem to get into the
> > policy.  I don't think anybody has a problem with it.  I think it's just
> > that no new version of the policy has been made yet.
> 
> Well, policy-process is still shipped with the debian-policy package, and
> my experience in the past is that when I follow that process, the changes
> go into Policy fairly quickly.  Certainly seconding would show that
> someone reviewed the wording of my proposed ~ patch and has confirmed that
> it sounds like an accurate and implementable description of their
> behavior.
> 
> Maybe Manoj could weigh in on how he sees the current process?

That document says things like:
 The group that decides on policy should be the group of
 developers on the debian-policy mailing list, which is how it
 was always done; so the group of policy maintainers have no
 real power over policy.

And that is not the impression I get from it.

Also, I believe this has changed since they are now delegates of the
DPL:
http://lists.debian.org/debian-devel-announce/2005/07/msg2.html

But it's unclear to me what this exactly means.


Kurt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Orphaning my packages

[James Westby]

On (18/09/06 16:35), Steve Kemp wrote:
> On Mon, Sep 18, 2006 at 10:58:31AM -0400, Nathanael Nerode wrote:
> 
> > The ones which haven't been picked up either with ITAs or in this thread,
> > and which aren't lib*-perl or lib*-ruby, are:
> > 
> > * 
> 
>   I'll take  since it hasn't been claimed.
> 

I claimes it via ITA straight away, perhaps I should have emailed the
list as well sorry. 

I'm always happy for co-maintenance, or you can take it yourself.

I imagine it will be easy to maintain. I also maintain another package
by the same author, and he is great to work with.

I was wondering what the upload ettiquete should be. There is no now,
version, no bugs, and the packaging is fine. Do I try and find a sponsor
just for a change of maintainer, or do I wait until there is something
to do?

Let me know what you would like to do,

James

-- 
  James Westby   --GPG Key ID: B577FE13-- http://jameswestby.net/
  seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Orphaning my packages

[Steve Kemp]

On Mon, Sep 18, 2006 at 06:13:23PM +0100, James Westby wrote:

> >   I'll take  since it hasn't been claimed.

> I claimes it via ITA straight away, perhaps I should have emailed the
> list as well sorry. 

  No problem, it was my fault for trusting the mail and not checking.

> I'm always happy for co-maintenance, or you can take it yourself.
> I imagine it will be easy to maintain. I also maintain another package
> by the same author, and he is great to work with.

  Great.  It sounds like you'd be the best choice for it then.

  I would offer to comaintain, since I think that is generally a good
 thing, but for a slow-moving package like this I'm not sure that it
 is required.

> I was wondering what the upload ettiquete should be. There is no now,
> version, no bugs, and the packaging is fine. Do I try and find a sponsor
> just for a change of maintainer, or do I wait until there is something
> to do?

  You could upload now to fix the standards version and to set the
 new maintainer - thats what I'd do, even though there are no bugs
 or newer upstream available.

Steve
-- 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Orphaning my packages

[Nathanael Nerode]

gregor herrmann wrote:

> On Mon, 18 Sep 2006 10:58:31 -0400, Nathanael Nerode wrote:
> 
>> (There are quite a few more -perl and -ruby packages, but I'm not quite
>> sure which ones have been picked up.)
> 
> The lib*-perl packages are all already in the Debian Perl Group's svn
> repository and will be uploaded soon.

Cool!

I note also that the -ruby packages have all been picked up by the
Debian/Ruby Extras team or others, and so have , revolution.

That reduces the complete list of unadopted packages from David to:

* dlume -- address book program
* fpm -- GNOME 1 password manager program
* gxmms -- GNOME panel controls for xmms/beep media player
* kipina -- athlete's training log program
* rxvt -- very popular x terminal emulator
-- the adopter might also want to grab the orphaned rxvt-beta package
* sendemail -- does what it says.
-- Small and written in perl -- maybe the Debian Perl Group would like it?
* wallpaper-tray -- GNOME wallpaper changer program, some nasty bugs



Meanwhile, I don't suppose I could convince the Debian Perl Group to pick up
some of the *other* orphaned perl libraries?.  ;-)

The ones I've noticed on a quick run through the orphaned package list are:

libapache-authznetldap-perl
libbusiness-ups-perl
libcdk-perl
libcgi-xml-perl
libcgi-xmlapplication-perl
libcgi-xmlform-perl
libclass-prototyped-perl
libconfhelper-perl
libconvert-ber-perl
libcorba-orbit-perl
libdb-file-lock-perl
libdbix-xml-rdb-perl
libdbix-xmlmessage-perl
libextutils-f77-perl
libfile-counterfile-perl
liblingua-en-numbers-ordinate-perl
liblingua-ispell-perl
libmail-listdetector-perl
libmldbm-sync-perl
libnet-ftpserver-perl
libnewt-perl
libpalm-perl
libperlmenu-perl
libpod-pom-perl
libproc-process-perl
libqt-perl
libtangram-perl
libtest-cmd-perl
libtie-array-sorted-perl
libtie-cache-perl
libvcs-perl
libxml-sablot-perl
perlftlib


These perl modules constitute more than 10% of the orphaned packages.
(I suspect some of them may be obsolete or folded into the main Perl
distribution or other perl modules.  Perhaps at least these could be
identified and removal bugs filed.)

> 
> gregor
>  


-- 
Nathanael Nerode  <[EMAIL PROTECTED]>

Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: (proposed) Mass bug filing for debconf "abuse" by using low|medium priority debconf notes?

[Nathanael Nerode]

Frans Pop wrote:

> On Monday 18 September 2006 16:36, Nathanael Nerode wrote:
>> Frankly, the kernel's "You NEED to restart your computer SOON" message
>> is a good example, if it's telling the truth.  But that cheats by not
>> using debconf.
> 
> Oh yes it does!
> When have you last done a kernel upgrade in testing/unstable? ;-)

Not recently enough, I guess!  I thought I did it a few weeks ago (in
testing).  Well, that's cool! :-)

-- 
Nathanael Nerode  <[EMAIL PROTECTED]>

Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...

Re: (proposed) Mass bug fi ling for debcon f "abuse" by using low|medium priority debconf notes?

[Christian Perrier]

Quoting Frans Pop ([EMAIL PROTECTED]):
> On Monday 18 September 2006 16:36, Nathanael Nerode wrote:
> > Frankly, the kernel's "You NEED to restart your computer SOON" message
> > is a good example, if it's telling the truth.  But that cheats by not
> > using debconf.
> 
> Oh yes it does!
> When have you last done a kernel upgrade in testing/unstable? ;-)

But, this is currently not (yet) translatable... Manoj tried to work
on this but the i18n was breaking something, IIRC, and he had to
revert the change. At least, this is where I left in that story.

(not speaking about theahem...wording of these templates)



signature.asc
Description: Digital signature

Re: (proposed) Mass bug fil ing for debcon f "abuse" by using low|medium priority debconf notes?

[Steve Langasek]

On Mon, Sep 18, 2006 at 10:36:11AM -0400, Nathanael Nerode wrote:

> > Christian Perrier wrote:
> >> In short, a note should only be used for IMPORTANT stuff, so actually
> >> all debconf notes should be priority highor should not exist!

> > It's better to simply remove them all: If it's an error, use the new
> > error data type, which will always be displayed no matter the priority.
> > If it's not an error, put it in NEWS.Debian, README.Debian, etc.

> > The only thing stopping me from making debconf notes a no-op is the note
> > in d-i's nobootloader, which is a fairly legitimate note (not error), that
> > can't really be put anywhere else, and possibly the partman help note
> > (though noone reads that note).

> Hmm.  Any time a package has to tell the user "You need to do something
> manually.  It's not being done automatically because we haven't figured out
> how to do that, but it's really really important to do it manually"
> -- then a high-priority debconf note is appropriate.

Not according to the designer of debconf.  There are other mechanisms that
are more appropriate than interrupting the install with this information,
such as using NEWS.Debian.  The current limitation is that NEWS.Debian
doesn't have i18n support; I had hoped to work on this for etch, but time
got away from me.

But certainly, apt-listchanges should at this point be getting installed by
default on new systems.

> Upgrades which require programs to be restarted should do it automatically.
> But if for some obscure reason they can't, then a high-priority note is
> reasonable.

If this obscure reason always applies, then that's better put in
NEWS.Debian.  If the obscure reason is that the maintainer script tried to
do the automatic restart but failed, a debconf error message would certainly
be reasonable.

> Upgrades from really-messed-up versions may also require people to do
> something manually to clean up from the messed-up version.

In that case you only want to bother the folks who had the really messed-up
version installed, so a conditional note also seems appropriate, yes.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Orphaning my packages

[gregor herrmann]

On Mon, 18 Sep 2006 13:59:11 -0400, Nathanael Nerode wrote:

> * sendemail -- does what it says.
> -- Small and written in perl -- maybe the Debian Perl Group would like it?

AFAIK at the moment the DPG only maintains Perl modules.

> Meanwhile, I don't suppose I could convince the Debian Perl Group to pick up
> some of the *other* orphaned perl libraries?.  ;-)

I know I know :-)
 
> The ones I've noticed on a quick run through the orphaned package list are:
[long list]
> These perl modules constitute more than 10% of the orphaned packages.
> (I suspect some of them may be obsolete or folded into the main Perl
> distribution or other perl modules.  Perhaps at least these could be
> identified and removal bugs filed.)

I, too, guess that some old packages are not really needed (otherwise
someone would have adopted them ;-)) but I guess the list is worth a
second look.

Other opinions?

gregor
 
-- 
 .''`.   http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4
 : :' :  debian: the universal operating system - http://www.debian.org/
 `. `'   member of https://www.vibe.at/ | how to reply: http://got.to/quote/
   `-NP: Peter Jones: Let's Drink To The King


signature.asc
Description: Digital signature

Re: (proposed) Mass bug filing for debconf "abuse" by using low|medium priority debconf notes?

[Manoj Srivastava]

On Mon, 18 Sep 2006 18:23:31 +0200, Christian Perrier <[EMAIL PROTECTED]> said: 

> Quoting Frans Pop ([EMAIL PROTECTED]):
>> On Monday 18 September 2006 16:36, Nathanael Nerode wrote:
>> > Frankly, the kernel's "You NEED to restart your computer SOON"
>> > message is a good example, if it's telling the truth.  But that
>> > cheats by not using debconf.
>> 
>> Oh yes it does!  When have you last done a kernel upgrade in
>> testing/unstable? ;-)

> But, this is currently not (yet) translatable... Manoj tried to work
> on this but the i18n was breaking something, IIRC, and he had to
> revert the change. At least, this is where I left in that story.

Well, Steve had mentioned something about being able to have
 templated templates, or something, so that one would not have had to
 preprocess the templates.master.in to create templates.master, but I
 don't recall how that went.

> (not speaking about theahem...wording of these templates)

Bright, chatty , personal, freindly as opposed to dull,
 distant, cold, robotic? 

manoj
-- 
Inflowing thoughts come to an end in those who are ever alert of mind,
training themselves night and day, and ever intent on nirvana. 226
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: The bigger issue is badly licensed blobs (was Re: Firmware poll

[Nathanael Nerode]

Goswin von Brederlow wrote:

> [EMAIL PROTECTED] (Marco d'Itri) writes:
> 
>> On Aug 31, Nathanael Nerode <[EMAIL PROTECTED]> wrote:
>>
>>> Marco trolled again.  FYI, no serious person disagrees with this
>>> interpretation.
>> Except every other distribution, which usually retain real lawyers
>> to advise them about potential problems like this instead of relying
>> on mailing lists posts.
>> It's pathetic that you dismiss dissenting opinions as "trolling".
>>
>> --
>> ciao,
>> Marco
> 
> Every other distribution does not concern itself with the question
> wether it is legal to distribute this. They are only concerned with
> "Will anybody sue us?" and "Do we loose more profit by risking a
> lawsuite or by dropping support?".
> 
> MfG
> Goswin

And we all agree that it is very unlikely that anyone will sue us if we
distribute these firmware blobs.  I did specify that, didn't I?

Now, "Is anyone likely to sue us?" *is* the standard Debian generally uses
for patents.  I presume this is because most software patents are in fact 
issued illegally at this point (in the US see the statutes and pre-Federal 
Circuit caselaw, in the EU see the European Copyright Convention and non-EPO 
caselaw), and DDs generally consider these illegitimate and unworthy of 
respect.

If we use the "Is anyone likely to sue us?" standard, then definitely these 
mislicensed lumps should be distributed.

However, traditionally Debian has used a higher standard for copyright. 
(Perhaps because Debian developers generally respect copyright law and think 
it deserves better treatment than "can we get away with this"?  Perhaps for 
some other reason?)  The higher standard has been more like "If the 
copyright was bought up by EvilCorp and they sued us, would we probably win
anyway because we behaved impeccably?"  In the case of the
mislicensed lumps, we would probably *not* win; we would probably be 
enjoined from any further distribution at least.

Perhaps this is a mistake and Debian should use the "Is anyone likely to sue 
us?" standard for copyrights as well.  Discussion is welcome.  Perhaps 
discussion will clarify why the different standards are used.

Discussion on debian-legal please.

-- 
Nathanael Nerode  <[EMAIL PROTECTED]>

Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Policy process

[Manoj Srivastava]

On Sun, 17 Sep 2006 11:43:18 -0700, Russ Allbery <[EMAIL PROTECTED]> said: 

> Well, policy-process is still shipped with the debian-policy
> package, and my experience in the past is that when I follow that
> process, the changes go into Policy fairly quickly.  Certainly
> seconding would show that someone reviewed the wording of my
> proposed ~ patch and has confirmed that it sounds like an accurate
> and implementable description of their behavior.

> Maybe Manoj could weigh in on how he sees the current process?

Given time constraints, and the desire tobe conservative wrt
 policy canges, it does help that there is a process  by which domain
 experts can weigh in with their opinion, or by which people can say
 that there have been other eye balls on the proposal, and things look
 good.

manoj
-- 
You will be the victim of a bizarre joke.
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Bug#388176: ITP: graphthing -- a tool to create, manipulate, and study graphs

[Cyril Brulebois]

Package: wnpp
Severity: wishlist
Owner: Cyril Brulebois <[EMAIL PROTECTED]>

* Package name: graphthing
  Version : 1.3.1
  Upstream Author : David Symonds <[EMAIL PROTECTED]>
* URL : http://graph.seul.org/
* License : GPL
  Programming Lang: C++
  Description : a tool to create, manipulate, and study graphs

 The supported graphs are simple graphs and digraphs, which means no
 multiple edges or loops.
 .
 Main features:
  * Adding, deleting and moving of vertices and edges.
  * Loading and saving of graphs.
  * Graph complements, induced subgraphs and line graphs.
  * Quick creation of many common graphs:
  complete, cycle, null, star, etc. 
  * Determination of shortest path, connectivity and Eulericity.
  * BFS, DFS and Minimum Spanning Tree.
  * Adjacency matrix (including exponents) and degree sequence.
  * Chromatic polynomial and chromatic number.
  * Network algorithms: Maximum network flow.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Intend to intend to hijack SeaView.

[Charles Plessy]

Dear all,

I did not find a match for "mia" or "hijack" in the tables of content
of the policy or of the developper's reference.

If Brian R Furry ([EMAIL PROTECTED]) were MIA, I would like to hijak his
"seaview" package, for which the upstream author has made improvements
that allow to move the package from contrib to main.

The maintainer did not answer to the bugs I posted half a year ago, one
of them being potentially release critical (wrong licence in
debian/copyright). He also did not upload anything at all for one year.

Seaview it an editor for multiple alignments of biological sequences,
and I have been working recently on bringing more sequence aligners to
Debian. Having an editor for the output of these programs in "main"
rather than "contrib" would help to assemble a coherent framework for
biological sequence analysis in Etch, but it necessitates to upgrade to
the latest upstream version. In my understanding, this is too much for a
NMU.

Therefore, unless I am told not to do so, and of course unless I am
wrong to thing that Brian Furry is MIA, I would like to put the package
under the responsability of the "Debian-Med packaging team" (see
http://alioth.debian.org/projects/debian-med/
and http://alioth.debian.org/projects/debian-med/), and to submit an
upgrade to my sponsor before the 8th of October. (By the way, is freeze
time minus 10 days the deadline for uploads ?).

Have a nice day,

-- 
Charles Plessy
http://charles.plessy.org
Wako, Saitama, Japan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Internationalising kernel-package generated debconf templates

[Christian Perrier]

(attempt to move this to -i18n)

> > But, this is currently not (yet) translatable... Manoj tried to work
> > on this but the i18n was breaking something, IIRC, and he had to
> > revert the change. At least, this is where I left in that story.
> 
> Well, Steve had mentioned something about being able to have
>  templated templates, or something, so that one would not have had to
>  preprocess the templates.master.in to create templates.master, but I
>  don't recall how that went.

Yes, that's probably it. It would be nice if someone with the needed
skills (read "not bubulle") would look into this and bring some input
so that these templates are i18n'ed finallyand, as a result, all
kernel-image templates as well, of course.

Does someone in the -i18n crowd feel like looking at this and work
with Manoj on a possible solution? Before etch would be good

> 
> > (not speaking about theahem...wording of these templates)
> 
> Bright, chatty , personal, freindly as opposed to dull,
>  distant, cold, robotic? 


Well, I know we do not agree on the topic...:-). This is indeed why
I'd like to have the possibility to bring style consistency at least
for the users of the French language (who, as everybody knows, are
very unfriendly people with distant ways to address others)and
probably other languages.

And anyway, besides our disagreement about style, Manoj, we should
probably work on the *length* of the k-p templates. They're indeed a
little bit too long to fit on a 80x25 screen, which is recommended
when possible for debconf notes.




signature.asc
Description: Digital signature

Re: Intend to intend to hijack SeaView.

[Andreas Tille]

On Tue, 19 Sep 2006, Charles Plessy wrote:


Therefore, unless I am told not to do so, and of course unless I am
wrong to thing that Brian Furry is MIA, I would like to put the package
under the responsability of the "Debian-Med packaging team" (see
http://alioth.debian.org/projects/debian-med/
and http://alioth.debian.org/projects/debian-med/), and to submit an
upgrade to my sponsor before the 8th of October. (By the way, is freeze
time minus 10 days the deadline for uploads ?).


The situation you described qualifies for a group maintained upload.
You might keep the original maintainer in the Uploaders field for the
sake of politeness because a complete hijack is regarded rude (even
if the facts you describe would justify it IMHO).

Kind regards and thanks for your efforts

   Andreas.

--
http://fam-tille.de

Re: Moving /var/run to a tmpfs?

[Miles Bader]

Steve Langasek <[EMAIL PROTECTED]> writes:
> It is also clear that this is how many maintainers have understood it,
> because as you yourself have noticed, there are many packages that
> assume they can ship directories in /var/run and have them remain
> available after reboot. :)

I think it's more likely that the average maintainer just never thought
about the issue, and did what they did because "it works".

I.e. the same reason many people used to assume int was 32 bits.  When
64-bit processors became common, lots of programs broke.  The solution
to that was to educate programmers to be more careful and assume less,
not to retroactively add silly restrictions to the definition of int.

-miles
-- 
Any man who is a triangle, has thee right, when in Cartesian Space, to
have angles, which when summed, come to know more, nor no less, than
nine score degrees, should he so wish.  [TEMPLE OV THEE LEMUR]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Tracking differences between Ubuntu and Debian for a set of packages

[Fabio Tranchitella]

Hello,

  I've written a small-and-easy script to track the differences for a
given set of packages between Debian and Ubuntu. We (as Debian/Ubuntu
Zope Team) use it to coordinate syncs, but it could be useful to other
developers too.

  http://people.debian.org/~kobold/ubuntu-diff/

  If you'd like to have new sets of packages included, eventually
tracking different distributions (eg. testing / ubuntu) drop me an
email.

Have a nice day,

-- 
Fabio Tranchitella <[EMAIL PROTECTED]>.''`.
Proud Debian GNU/Linux developer, admin and user.: :'  :
 `. `'`
   http://people.debian.org/~kobold/   `-
_
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564


signature.asc
Description: Questa è una parte del messaggio	firmata digitalmente