stackwalker.cc:125: INFO: Couldn't load symbols for: /lib/i386-linux-gnu/libglib-2.0.so.0|......

[Weber]

Package:iceweasel

version : 38.3.0 esr

Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.68-1+deb7u3 i686 GNU/Linux


dear developers

after my upgrade today , i startet firefox in su terminal

i got these errors see below -->:

after second start ,the error was different.

has someone forgotten again to test firefox before send it to the world?



-->

user33@debian:/usr/bin$ firefox
*** UTM:SVC TimerManager:registerTimer - id: browser-cleanup-thumbnails
console.error:
  [CustomizableUI]
  Custom widget with id loop-button does not return a valid node
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols for: |
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols
for: /lib/i386-linux-gnu/libglib-2.0.so.0|1DACD275C7698050A777B0F35BEBF45B0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb724d800
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols
for: /usr/lib/iceweasel/libxul.so|4BB5BA704A08E45760868FC0A471326D0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72c3500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb74996e0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xbfa9bfec
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb722ae80
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72c34c0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7fff
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72c3500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72238e4
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb722ae80
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xae851680
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72df110
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols
for: /usr/lib/iceweasel/libnspr4.so|771155C5C020D5F1DCB6CFF8283322F40
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xbfa9c038
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x319
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x117a16b1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x5014
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72238e0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb722ba50
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xc1acd
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x14
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09

stackwalker.cc:125: INFO: Couldn't load symbols for: /lib/i386-linux-gnu/libglib-2.0.so.0|......

[Weber]

Package:iceweasel

version : 38.3.0 esr

Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.68-1+deb7u3 i686 GNU/Linux


dear developers

after my upgrade today , i startet firefox in su terminal

i got these errors see below -->:

after second start ,the error was different.

has someone forgotten again to test firefox before send it to the world?



-->

user33@debian:/usr/bin$ firefox
*** UTM:SVC TimerManager:registerTimer - id: browser-cleanup-thumbnails
console.error:
  [CustomizableUI]
  Custom widget with id loop-button does not return a valid node
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols for: |
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols
for: /lib/i386-linux-gnu/libglib-2.0.so.0|1DACD275C7698050A777B0F35BEBF45B0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb724d800
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols
for: /usr/lib/iceweasel/libxul.so|4BB5BA704A08E45760868FC0A471326D0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72c3500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb74996e0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xbfa9bfec
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb722ae80
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xa3993500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72c34c0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x7fff
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72c3500
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72238e4
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb722ae80
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xae851680
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72df110
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: stackwalker.cc:125: INFO: Couldn't load symbols
for: /usr/lib/iceweasel/libnspr4.so|771155C5C020D5F1DCB6CFF8283322F40
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xbfa9c038
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x319
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x117a16b1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x5014
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb72238e0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xb722ba50
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xc1acd
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0xaca87d30
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x1
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x14
2015-09-24 22:57:25: basic_code_modules.cc:88: INFO: No module at 0x0
2015-09

UTM:SVC TimerManager:registerTimer - id: browser-cleanup-thumbnails,console.error

[Weber]

 Openbox-Message: Konnte keine gültige Menü-Datei
"/usr/share/lxde/openbox/menu.xml" finden
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area

** (lxterminal:3130): WARNING **: Configuration file create failed:
Keine Berechtigung


** (lxterminal:7835): WARNING **: Configuration file create failed:
Keine Berechtigung

enigmail.js: Registered components
mimeVerify.jsm: module initialized
mimeEncrypt.js: module initialized
*** UTM:SVC TimerManager:registerTimer - id: browser-cleanup-thumbnails
console.error:
  [CustomizableUI]
  Custom widget with id loop-button does not return a valid node
*** UTM:SVC TimerManager:notify - notified
@mozilla.org/browser/search-service;1
WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate.
Use isContentWindowPrivate instead (but only for frame scripts).
pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14
nsBrowserAccess.prototype.openURI@chrome://browser/content/browser.js:15030:21
noscriptOverlay<.browserAccess.openURI@chrome://noscript/content/noscriptOverlay.js:2818:13
*** UTM:SVC TimerManager:notify - notified
@mozilla.org/browser/search-service;1
*** UTM:SVC TimerManager:notify - notified timerID:
browser-cleanup-thumbnails
WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate.
Use isContentWindowPrivate instead (but only for frame scripts).
pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14
nsBrowserAccess.prototype.openURI@chrome://browser/content/browser.js:15030:21
noscriptOverlay<.browserAccess.openURI@chrome://noscript/content/noscriptOverlay.js:2818:13

(x-www-browser:8118): Gtk-CRITICAL **: IA__gtk_clipboard_set_with_data:
assertion `targets != NULL' failed

(x-www-browser:8118): Gtk-CRITICAL **: IA__gtk_clipboard_set_with_data:
assertion `targets != NULL' failed

(x-www-browser:8118): Gtk-CRITICAL **: IA__gtk_clipboard_set_with_data:
assertion `targets != NULL' failed

(x-www-browser:8118): Gtk-CRITICAL **: IA__gtk_clipboard_set_with_data:
assertion `targets != NULL' failed

(x-www-browser:8118): Gtk-CRITICAL **: IA__gtk_clipboard_set_with_data:
assertion `targets != NULL' failed

Bug#278940: ITP: socket++ -- lightweight convenience library to handle low level BSD sockets in C++

[Dan Weber]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: wnpp
Severity: wishlist

* Package name: socket++
  Version : 1.12.12
  Upstream Author : Gnanasekaran(Sekar) Swaminathan <[EMAIL PROTECTED]>,
Herbert Straub <[EMAIL PROTECTED]>
* URL : http://www.linuxhacker.at/socketxx
* License : Pasted below with License Statement
  Description : lightweight convenience library to handle low level BSD 
sockets in C++

  Socket++ library defines a family of C++ classes that can be used more
  effectively than directly calling the underlying low-level system functions.
  One distinct advantage of the socket++ is that it has the same interface as
  that of the iostream so that the users can perform type-safe input output.
  See your local IOStream library documentation for more information on
  iostreams.
  .
  Development of the original socket++ died some years ago, and a new
  upstream has taken control.  The original socket++ ended at version 1.11.
  Lauri Nurmi  modified the source code to make Socket++ compile with recent
  GCC under linux.  This version is fork of the code from Lauri Nurmi which
  was just some enhancements to make it standard conforming at version 1.11.



- -- License

Original Copyright Notice:

Permission is granted to use at your own risk and distribute this software
in source and  binary forms provided  the above copyright notice and  this
paragraph are  preserved on all copies.  This software is provided "as is"
with no express or implied warranty.

Copyright Statement:

>
> Got your message. Please feel free to include it in
> any software and use it as you please. Let me know if
> you need any help with it.

and further:
+++
Hi Herbert,

That was not the intention. It is a free code. You can modify,
copy, and distribute and use it in anyway as you see fit.

Other people are maintaining it and ported it to different
OSes. Other than that, not much has changed as far as I know.
I haven't looked at it recently.

- -Sekar

- -- Side Note

This ITP is being cross posted to debian-legal for the purpose of verifying
that this is capable of being placed in main.

Dan Weber


- -- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (499, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.reiser4.vserver
Locale: LANG=en_US, LC_CTYPE=en_US
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBg6qkF6i3K/AxoQERAp42AKClgh7dXmH/48TeuORsCqKq6d25bwCfdAjg
CcC0AqjCdXGesDg92Q20Irs=
=TPT8
-END PGP SIGNATURE-

Re: Re: Bug#340428: octave2.9 - lists mailing list as uploader in changelog

[Thomas Weber]

Hi
> First, what is DOG, I never heard about it.
"In the debian/changelog for octave2.9 (and all other packages maintained
collectively by the Debian Octave Group, the DOG)"
Start of Thread: 
http://lists.debian.org/debian-devel/2005/11/msg01378.html


> Second, I'm a member of the debian-installer team. I never say uploads
> with such entries.

http://lists.debian.org/debian-devel-changes/2005/11/msg01337.html

Regards
Thomas


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

Re: Survey on Debian contributors

[Thomas Weber]

Hi,

Am Dienstag, den 17.01.2006, 18:20 +0200 schrieb Niklas Vainio:
> Please take a few minutes to answer the survey at 
> http://hiisi.fi/survey/debian

Some suggestions:
Surveys from a university should have a place on the university's
webserver -- they look official.

Question 11 (income):
Is this before of after taxes? If you are free to choose, I suggest
after taxes -- gross salaries are very difficult to compare.

Thomas


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

Re: Bug#348607: ITP: gtkedit -- Notepad clone based on GTK+

[Thomas Weber]

Hi,

Am Dienstag, den 17.01.2006, 18:56 -0500 schrieb Christopher Peterman:
> Package: wnpp
> Severity: wishlist
> 
> * Package name: gtkedit
>   Version : 0.1/b1
>   Upstream Author : Daniel Guerrero <[EMAIL PROTECTED]>
> * URL or Web page : http://gtkedit1.sourceforge.net
> * License : MIT
>   Description : Notepad clone based on GTK+
>   
>   GTKEdit is a lightweight Notepad clone designed for low performance
>   systems

Do you really want to introduce a GTK 1.2 application into unstable at
this point of time? 

Regards
Thomas


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

Re: svn problem: Can you help me?

[Thomas Weber]

Hi Lionel, 

Am Sonntag, den 29.01.2006, 22:11 +0100 schrieb Lionel Elie Mamane:
> What does that mean and how do I get out of this dead-end? Thanks in
> advance.

Does this one help?
http://svn.haxx.se/users/archive-2003-07/0133.shtml

Thomas


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

Re: Amendment to GR on GFDL, and the changes to the Social Contract

[Thomas Weber]

Am Donnerstag, den 09.02.2006, 12:50 +0100 schrieb Marco d'Itri:
> On Feb 09, Adam Borowski <[EMAIL PROTECTED]> wrote:
> 
> > There are two different definitions of the word software:
> > 1. something that can be represented as a finite stream of bits
> > 2. a computer program
> > 
> > Definition 1. is precise, definition 2. is not (PostScript, pseudocode, 
> Unfortunately, definition #2 is the one which almost everybody agreed to

How so? Is there any document in Debian, stating that "software" follows
definition 2? 

BTW, taking this classification, where do you put PostScript files --
software or documentation?

Regards
Thomas


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

Re: Honesty in Debian (was Re: Amendment to GR on GFDL, and the changes to the Social Contract

[Thomas Weber]

Am Montag, den 13.02.2006, 09:37 +0100 schrieb Xavier Roche:
> But I still consider documentation different than softwares, and don't see
> any major problem regarding the FDL.

Well, there are cases where the differences are totally unclear. Let's
start with PostScript files, go to interactive PDFs and -- while we are
at it -- let's think about HTML files with Javascript.

What are these? Documentation, computer programs, both? If they are both
(which is probably the best description), which guidelines should be
applied?

Regards
Thomas


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

Re: New packages.debian.org

[Thomas Weber]

Hi, 

Am Montag, den 06.03.2006, 15:11 -0400 schrieb Ben Armstrong:
> On Mon, 2006-03-06 at 19:38 +0100, Martin Schulze wrote:
> > It checks the User-Agent string.
> 
> What are the expected results for a user accessing the following URL
> from IE running on a W2K terminal server?

I guess the original "only runs this service" should be parsed as
"there's no additionally ftp server, archive or whatever" on this
machine.

Reading the whole message on debian-devel-announce seems to suggest this
interpretation.


Regards
Thomas


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

Re: Bug#355638: ITP: w3c-linkchecker -- check the validity of links in an HTML or XHTML document

[Thomas Weber]

Hi, 

Am Montag, den 06.03.2006, 22:31 +0100 schrieb Jonas Genannt:
> * Package name: w3c-linkchecker
>   Version : 4.2.1
>   Upstream Author : Hugo Haas <[EMAIL PROTECTED]>
> * URL : http://search.cpan.org/~scop/
> * License : W3C Software License
>   
> http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
>   Description : check the validity of links in an HTML or XHTML document

Eh, is this the same program that comes as "checklink" with the
w3c-markup-validator? 

Regards
Thomas



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

Re: Bug#355638: ITP: w3c-linkchecker -- check the validity of links in an HTML or XHTML document

[Thomas Weber]

Hi, 

Am Dienstag, den 07.03.2006, 11:13 +0100 schrieb Jonas Genannt:
> > Eh, is this the same program that comes as "checklink" with the
> > w3c-markup-validator? 
> 
> Please see #263716 and #324028

Thanks for that one; as I'm using the checklink command, but not the
validator, I'm looking forward to your package.

(No need to CC me, I'm subscribed).

Regards
Thomas


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

Re: tetex URGENT: can't use ygoth font

[Olaf Weber]

Yann Dirson writes:

> Compilation works fine. But dvips fails: it seems that mf produces
> output (despite many "Strange path" warnings), but no file is created
> in /var/spool/texmf/pk/ljfour/public/gothic/, which may explain why
> dvips says "Font ygoth not found".

Older versions of the MakeTeX scripts assume that the font wasn't
created if strange path errors occured.  This is fixed in the most
recent versions.  I'm not entirely certain this was already fixed in
teTeX 0.4pl8.

The relevant change looks like this, and should be made to both
MakeTeXPK and MakeTeXTFM:

-echo "$0: Running $cmd"
-$cmd &2; exit 1; }
+echo "$progname: Running $cmd"
+$cmd $$.errs 2>/dev/null
+  grep '^! Strange path' $$.errs >$$.strange 2>/dev/null
+  if cmp $$.errs $$.strange >/dev/null 2>&1 \
+&& test -s $$.strange >/dev/null 2>&1; then
+echo "$progname: warning: \`$cmd' caused strange path errors." >&2
+  else
+echo "$progname: \`$cmd' failed." >&2
+exit 1;
+  fi
+}


-- 
Olaf Weber


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Bug#381992: ITP: libming-fonts-openoffice -- Fonts for use with the Ming Library for SWF Creation

[Thomas Weber]

Hi, 

Am Dienstag, den 08.08.2006, 02:28 -0500 schrieb Alejandro Rios P.:
> .These fonts canNOT be used with X11 or for printing.

I suggest writing this as 'can NOT'. It's easier to parse and (with the
idea of descriptions' translations in mind) comes closer to what happens
in a translation -- at least for the languages I know.

Regards
Thomas



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

Re: WTF ? (Fwd: Your message to Yaird-devel awaits moderator approval)

[Thomas Weber]

Hi, 

Am Dienstag, den 15.08.2006, 11:18 +1000 schrieb Brian May:
> Besides, it is yet-another message I receive and I have to process -
> keeping the message around for another week in case the moderator wont
> accept the message is highly annoying and probably will mean that the
> bug report gets forgotten - and even then - it is very unclear what to
> do when the message isn't accepted (or rejected).

How is that different from a non-responsive maintainer (in which case
you don't even know that the message arrived on his mail system)?

Regards
Thomas


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

Re: WTF ? (Fwd: Your message to Yaird-devel awaits moderator approval)

[Thomas Weber]

Hi, 

Am Donnerstag, den 17.08.2006, 10:52 +1000 schrieb Brian May:
> * In one case you can usually assume the maintainer got the message,
> in the other case you practically got confirmation that the message
> didn't get through.
> 
> * If the maintainer doesn't respond, you can always send a ping, and
> find out if he/she replies.
> 
> * If you get a warning message from a mailing list, then sending a ping
> message won't do any good, the same thing will happen.

I would sum up all these reasons as "if the message doesn't come
through, the maintainers are MIA". Just for the record: for every
message held for approval, the moderators get an email saying so. It's
not like they have to check this manually.


> * The warning message seems rude. I took the effort to email Debian a
> bug report - why should I get spammed with this meaningless message
> in response?

I actually consider this a configuration issue. However, I have not yet
seen a possibility to waive BTS messages through (which would be really
helpful). I'm looking into the documentation right now.


> * The warning message implies that people who
> send bug reports to Debian must also subscribe to upstream mailing
> lists. This is unacceptable (IMHO). I already subscribe to far too many
> mailing lists.
I don't think that the message implies that. At least, you are the first
one to bring this up.


> * It gives the impression that the Debian maintainers aren't
> interested in receiving bug reports or improving the quality of
> their packages.
Well, I think it gives the impression that the lists' moderators care
about not filling the subscribers' inboxes with even more spam; I don't
have hard numbers (I don't count the messages), but my feeling is that
> 50% of all messages are spam. I suggest you have a look at some
not-so-much used lists at lists.debian.org (June 2006 of
debian-consultants is a pretty good example). These lists look as if
nobody cared what happens with them.

Regards
Thomas


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

Re: I want one of those!

[Thomas Weber]

Am Freitag, den 18.08.2006, 11:27 +0300 schrieb Riku Voipio:
> > http://www.movidis.com/products/rev.asp
> 
> Has anyone contacted movidis/cavium of getting this system supported
> in etch? It would make a nice bullet in etch release notes :)

According to the linked informationweek article in Adrians's original
posting, this machine actually ships with Debian.

Regards
Thomas


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

Re: Request to mailing list Pkg-qof-maintainers rejected

[Thomas Weber]

Am Sonntag, den 10.09.2006, 21:22 -0700 schrieb Steve Langasek:
> For my part, I find it pretty offensive that a mailing list that's set as
> the maintainer of a package would have mail filters configured this way in
> the first place.  For the samba packaging team, for instance, I've taken
> pains to adjust the spam filters to allow bts mail in automatically before
> ever setting the maintainer field to point to the list; I would expect other
> packaging teams to take the same care.

Can you publish/describe your setup?

Regards
Thomas



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

Re: Media players in Debian (was: new mplayer)

[Thomas Weber]

Hi, 

Am Samstag, den 23.09.2006, 13:07 +0200 schrieb Bartosz Fenski aka
fEnIo:
> Please tell me what's wrong with *current* package and what can we do to
> make it better and stop saying me it's license issue.

IIRC, one of the things that lead to the rejection of the mplayer
package last time:
http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/2006-July/044840.html

Regards
Thomas


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

Re: Politeness was: woody removed from mirrors

[Thomas Weber]

Am Montag, den 08.01.2007, 21:50 -0800 schrieb Will Lowe:
> Oh, and ... archive.debian.org doesn't seem to be rsync-enabled.  Is
> there anyplace that has woody and *does* support rsync?  

http://www.debian.org/distrib/archive.html
mentions several rsync sites.

Regards
Thomas



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

Re: Is Ryuichi Arafune MIA?

[Thomas Weber]

Hi, 

Am Donnerstag, den 11.01.2007, 23:32 -0400 schrieb Muammar Wadih El
Khatib Rodriguez:
> Ryuichi, may I take over the webmagick package?
> 
> If you agree or don't reply, I'll take over the webmagick package.

Did you put Ryuichi's mail address in BCC (same goes for Luciano's
mail)? Otherwise he might simply not read debian-devel.

Tatsuya had him in the TO: header.

Regards
Thomas



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

Re: Sun Java available from non-free

[Thomas Weber]

I don't have a particular opinion for Java in Debian or not, but there
are some points you raise:

Am Sonntag, den 21.05.2006, 12:34 -0500 schrieb Raphael Hertzog:
> In that case, ftpmasters accepted it, end of discussion. 

Don't you think that the main problem here is that there *wasn't* any
discussion, at least for the vast majority of Debian developers and
users? And yes, as a Debian user I'm surprised that such decisions are
taken behind closed doors; this is not a security related issue and it
wouldn't have done any harm to Debian to discuss this in the open.

If that had delayed the inclusion, so be it; after several years without
Sun's Java in Debian, some more weeks wouldn't have hurt neither users
nor the project itself.



> Furthermore, doing a bit of Debian PR by having a timely announce of the
> new java license, is good for us too.

I agree with you that it was a good PR stunt. At the same time, it was
an internal communication disaster.

Oh, and the impression that pushing non-free packages in after several
hours has a high priority, while (license-wise) simple packages linger
for weeks in NEW was probably a bonus[1].



> > It would be bad PR if Debian will have to remove Sun Java from the
> > archive, shortly after public announcements that it accepted it in.
> 
> No it wouldn't.

Well, there I disagree with you: it would. At the very least, it would
give the impression that Debian can't decide what it wants.


[1] Yes, I know that this was due to the fact, that three ftp-admins
have examined the license probably far longer than the package was in
the NEW queue. Why do I know it? Because AJ did *communicate* it.

Regards
Thomas


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

Re: Sun Java available from non-free

[Thomas Weber]

Am Sonntag, den 21.05.2006, 15:58 -0500 schrieb Raphael Hertzog:
> No, if we should discuss before taking any action we wouldn't get
> anything done. 
Oh, come on. Nobody expects you to ask before updating a simple package.


> If you really want to contest the decision, you have the
> GR.
ROFL, yes, that will give us a much higher productivity...; taking
decisions behind closed doors and then let people decide via a GR.


> Someone from Sun contacts you to examinate a new license for Java and ask
> you advice and all, and ask you to keep that info private. What do you
> respond to him ? "No sorry, we really don't care, go away"?
Discuss it with them; let them publish the license; announce your wish
to include it into Debian. If we assume that a discussion takes about
two weeks, that would have been the delay between the inclusion.


> There was no other choice, that's all. 
Sorry, that's not true, I've pointed out another choice above.


> And we would have lost an opportunity to do some PR stuff and show
> everyone that we're an important player in the Linux world.
How about is taking some time to include this stuff a lost opportunity?
Do you believe the announcement has a greater impact if it comes close
to Sun's announcement? Sorry, while this was really good for Sun, the
effect for Debian is probably negletable. 

By the way, did you actually check what kind of PR this generated?
Reading the german news sites (and Slashdot) [1,2], I fear that it
wasn't made clear that the packages go into non-free; I think people
will expect to find them in main.
Perhaps next time a real press release from Debian would be in order,
instead of letting Sun take the lead.


> The choice has already been made. Both sides have positive sides and
> negative ones. The choice has been made, no point in discussing it over
> again and again.
Raphael, if you keep pissing people of with this "we have decided, now
get back to working" attitude, you might find that your good PR might
backfire. Even a failed GR about this issue will generate more bad press
than the announcement created good one.


> I have to agree this sucks but if you have the schedule in mind it's easy
> to understand:
I point to my earlier posting about communication: I can't have a
schedule in mind if I didn't know there existed one in the first place.


> No, it would simply show that Sun is not committed to what they told us.
> We have been reasonable and accepted to work with them. If they change
> their mind, then it's Sun which is not reasonable.
If Debian publishes a press release saying "we remove this because of
Sun's actions", this will generate bad press for both Debian and Sun.
Even if it's worse for Sun, it's still something we should try to avoid.

[1] http://www.golem.de/0605/45369.html
[2] http://developers.slashdot.org/article.pl?sid=06/05/19/2044202


Thomas


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

Contacting the buildd admin of the current build chroot

[Thomas Weber]

Hi, 

is it possible for a 'building' package to send a mail to the buildd
admin of the current buildd machine (i.e. something like
[EMAIL PROTECTED])?

Reason: somewhere around Sep-Nov 2005, an alternative symlink was left
by the octave2.1 package in state 'manual'. This means that packages
build-depending on octave2.1 fail to build (if they are built on a
buildd which built octave2.1 in this period). A more explicit
explanation can be found at
http://lists.debian.org/debian-devel/2006/01/msg01566.html.

Sending this problem to the [EMAIL PROTECTED] list
didn't fix it for all machines, as can be seen at
http://buildd.debian.org/fetch.php?pkg=octaviz%26ver=0.4.0-26%
26arch=ia64%26stamp=1149076049%26file=log
(search for '2005').

Now, I would like to add something to debian/rules that checks for the
state (auto/manual) of this symlink and sends a mail to the buildd admin
if the state is 'manual'. Thus, only involved admins would be bothered.

Alternatively, I could add 
  update-alternatives --auto octave-config 
to debian/rules; but I don't know if this is acceptable.

Suggestions?

Thanks
Thomas


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

Re: CDBS and dh_install

[Thomas Weber]

Hi, 

first off, I'm neither a DD nor an NM, but I do some packaging work
(thanks to alioth), As most people here argue against CDBS, I think the
benefits of it are missed (if you didn't guess, I use it and I like it).

Am Freitag, den 09.06.2006, 15:10 -0700 schrieb Steve Langasek:
> On Fri, Jun 09, 2006 at 02:02:48PM -0500, Manoj Srivastava wrote:
> > > This is also my impression. CDBS might be nice to automate the task
> > > "make a .deb out of this Gnome source", but imho it completely fails
> > > when you want to deviate from the "standard" in any way.

I guess this paragraph sums it up pretty good. CDBS is not the best
choice if you need something  *not* _c_ommon. OTOH, if I see a CDBS
based rules files with three lines, this tells me one thing pretty
clearly: there's nothing unusual in this package.


> Let's compare debhelper to cdbs.
I don't quite agree with your analysis. If you say "CDBS stuff is
under /usr/share/cdbs", you must as well say "dh_* stuff is
under /usr/share/perl5/Debian/Debhelper/". 

The problem is the documentation, which leaves room for improvement. I
mean, how many people would understand dh_* without the manpages?



> /usr/share/cdbs/1/rules/debhelper.mk anyway, so they're still *using*
> debhelper behind the scenes. :)  
Yes, and that's a fact I like a lot. I mean, having debian/rules files
in different packages, which are almost exchangable, but still every
single one has > 50 lines, is unproductive. 
(Packaging-wise) simple packages should have simple and *short*
debian/rules files.

I mean, if I want default values for a program, I do "./configure" and
not "./configure --enable-default-prefix --enable-default-docpath ..."


Regards
Thomas


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

Re: CDBS and dh_install

[Thomas Weber]

Am Samstag, den 10.06.2006, 15:38 -0700 schrieb Steve Langasek:
> Oh, I disagree; I think I have a pretty good idea what the benefits are of
> CDBS, I just think that many CDBS proponents underemphasize the *downside*
> of CDBS.
> 
> So tell me, how do you know a priori whether the software you're packaging
> is going to be "common", or if it's going to need to deviate from CDBS at
> some point in the future?  

Well, how do I know if I have to deviate from the debhelper scripts at
some point in the future? In fact, if I bump up the compat level, I
might very well need to change my scripts.

The difference is that joey is extremely careful not to break things
(and debhelper scripts are already quite mature).


> If you're recommending a packaging style to a new
> packager who probably doesn't have the level of committment to learn more
> than a single helper style, how do you know whether they will at some point
> need to package something that doesn't fit in cdbs's neat little view of the
> world?
I don't know it, but that's not the problem. CDBS is for the simple
cases where its neat little view is fulfilled. I believe a large number
of packages in Debian fit in this little view. Does it really make sense
to have long rules files for these packages? I believe packagers' time
is better spent on complicated packages, where CDBS isn't enough.

NM's using only CDBS will probably fail. 



> Er... is that really meant to be a defense of CDBS?  debhelper *does* have
> manpages, and this is an important part of why I think it's better.
It wasn't meant as a defense. Now, we have (basically) two choices: dump
CDBS or improve the docs.


> > I mean, if I want default values for a program, I do "./configure" and
> > not "./configure --enable-default-prefix --enable-default-docpath ..."
> 
> Hmm, interesting comparison, given all the arguments that cdbs itself passes
> to ./configure by default:
> 
>   --build=$(DEB_BUILD_GNU_TYPE) --prefix=$(DEB_CONFIGURE_PREFIX) \
>   --includedir=$(DEB_CONFIGURE_INCLUDEDIR) \
>   --mandir=$(DEB_CONFIGURE_MANDIR) --infodir=$(DEB_CONFIGURE_INFODIR) \
>   --sysconfdir=$(DEB_CONFIGURE_SYSCONFDIR) \
>   --localstatedir=$(DEB_CONFIGURE_LOCALSTATEDIR) \
>   --libexecdir=$(DEB_CONFIGURE_LIBEXECDIR) --disable-maintainer-mode \
>   --disable-dependency-tracking
> 
> :)
Yes, but I don't need to type this stuff myself (and it's there if I
need to override it) in dozens of packages.


> What problems does this cause?  I mean, I've heard of a few bugs from time
> to time caused by maintainers putting key debhelper commands out of order;
The right order surely was documented :)
But we all know (at least those with end user experience) that people
never read docs -- so why bother writing them? :)


Regards
Thomas


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

Re: CDBS and dh_install

[Thomas Weber]

Am Sonntag, den 11.06.2006, 11:30 +0100 schrieb Mark Brown:

> That's a bit different: updating the debhelper compat level is updated
> by the maintainer explicitly changing the package rather than by
> installing a new version of debhelper.

Well, I certainly agree that it is a bug if CDBS changes its behaviour
and the number is not bumped there as well. The problem currently seems
that CDBS is used for packages but actually still somewhat unstable. 

Thomas


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

Re: make -j in Debian packages

[Thomas Weber]

Am Sonntag, den 25.06.2006, 18:11 +0300 schrieb Lars Wirzenius:
> I doubt we need a policy change for this. At some point, we need to stop
> legislating and start assuming the package maintainers have common
> sense.

Agreed. However, it might be a good idea to have *one* canonical
variable name for that; perhaps dev-ref is a better place for this than
policy.

Thomas


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

Bug#376214: ITP: octave2.1-forge -- Contributed functions for GNU Octave from http://octave.sf.net for Octave 2.1

[Thomas Weber]

Package: wnpp
Severity: wishlist
Owner: Thomas Weber <[EMAIL PROTECTED]>


* Package name: octave2.1-forge
  Version : 2006.03.17
  Upstream Author : Paul Kienzle <[EMAIL PROTECTED]>
* URL : http://octave.sourceforge.net/
* License : Various (GPL, Public Domain)
  Programming Lang: Octave, C++
  Description : Contributed functions for GNU Octave from 
http://octave.sf.net for Octave 2.1

The octave-forge project contains over 500 contributed functions for GNU Octave
which are not in the main distribution. These functions are grouped according
to the following subdirectories: audio, comm, control, general, geometry,
ident, image, io, linear-algebra, miscellaneous, optim, path, plot, set,
signal, sparse, specfun, special-matrix, splines, statistics, strings, struct,
symbolic, time. 
   
While the main Octave distribution is conservative about accepting new
functions and changes, octave-forge is very open. As a result, be prepared for
some lower quality code and more rapidly changing interfaces to the functions
in octave-forge.

This package is compiled for Octave 2.1. If you need it for Octave 2.9, use the
octave2.9-forge package.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (700, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

This package will be maintained by the Debian Octave Group on Alioth. This
package is already in the archive as 'octave-forge'. We will introduce a similar
package compiled for Octave 2.9, therefore the new package.

Regards
  Thomas


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

Bug#376215: ITP: octave2.9-forge -- Contributed functions for GNU Octave from http://octave.sf.net for Octave 2.9

[Thomas Weber]

Package: wnpp
Severity: wishlist
Owner: Thomas Weber <[EMAIL PROTECTED]>


* Package name: octave2.9-forge
  Version : 2006.03.17
  Upstream Author : Paul Kienzle <[EMAIL PROTECTED]>
* URL : http://octave.sourceforge.net/
* License : Various (GPL, Public Domain)
  Programming Lang: Octave, C++
  Description : Contributed functions for GNU Octave from 
http://octave.sf.net for Octave 2.9

The octave-forge project contains over 500 contributed functions for GNU Octave
which are not in the main distribution. These functions are grouped according
to the following subdirectories: audio, comm, control, general, geometry,
ident, image, io, linear-algebra, miscellaneous, optim, path, plot, set,
signal, sparse, specfun, special-matrix, splines, statistics, strings, struct,
symbolic, time. 
   
While the main Octave distribution is conservative about accepting new
functions and changes, octave-forge is very open. As a result, be prepared for
some lower quality code and more rapidly changing interfaces to the functions
in octave-forge.

This package is compiled for Octave 2.9. If you need it for Octave 2.1, use the
octave2.1-forge package.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (700, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

This package will be maintained by the Debian Octave Group on Alioth. 

Regards
  Thomas


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

Re: ITP lame

[Lars Weber]

Buddha Buck <[EMAIL PROTECTED]> wrote:

> >I understand fully that using the name "non-US" for patent-encumbered
> >software is wrong. However, the machine pandora.debian.org is in an
> >excellent position to also host a "non-Software-Patents" section of the
> >archive, which can again be subdivided in main, contrib and non-free.
> 
> If we do that, I suggest that "non-Software-Patents" is a bad 
> name.  Perhaps "patented" is a better name.

Does it have to be tied to patent-problems?  What about a more general
section named (for example) "encumbered"?

It could then also be used for software with other sorts of local
problems -- like "indexed" games here in germany.

Lars


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

Re: Bits from the DPL: FTP assistants, marketing team, init scripts, elections

[Thomas Weber]

Am Montag, den 25.02.2008, 12:00 +0100 schrieb Holger Levsen:
> Hi,
> 
> On Monday 25 February 2008 08:15, Aníbal Monsalve Salazar wrote:
> > On Mon, Feb 25, 2008 at 09:07:20AM +0200, Lars Wirzenius wrote:
> > >We had a chicken[¹]. We spent years actively getting rid of it.
> > >[¹] Technically speaking it was a penguin. But it was a youthful
> > >penguin, rebelling against its genetic heritage.
> 
> Oh why? I liked the chicken! When I read Sams mail I immediatly thought of 
> it. 
> Maybe it's good idea to renew the drawing (and keep the basic idea/look), but 
> IMHO thats all. 

Can anyone please give an URL for this picture? 

Thomas


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

Re: Bits from the DPL: FTP assistants, marketing team, init scripts, elections

[Thomas Weber]

Am Montag, den 25.02.2008, 13:42 +0100 schrieb David Paleino:
> On Mon, 25 Feb 2008 12:38:07 +0100, Thomas Weber wrote:
> 
> > Am Montag, den 25.02.2008, 12:00 +0100 schrieb Holger Levsen:
> > > Hi,
> > > 
> > > On Monday 25 February 2008 08:15, Aníbal Monsalve Salazar wrote:
> > > > On Mon, Feb 25, 2008 at 09:07:20AM +0200, Lars Wirzenius wrote:
> > > > >We had a chicken[¹]. We spent years actively getting rid of it.
> > > > >[¹] Technically speaking it was a penguin. But it was a youthful
> > > > >penguin, rebelling against its genetic heritage.
> > > 
> > > Oh why? I liked the chicken! When I read Sams mail I immediatly thought of
> > > it. Maybe it's good idea to renew the drawing (and keep the basic
> > > idea/look), but IMHO thats all. 
> > 
> > Can anyone please give an URL for this picture? 
> 
> I believe what they're talking about can be seen on 
> http://lintian.debian.org/.
> (see the penguins on the background of the logo)

Thanks. I finally found 
http://www.debian.org/vote/1999/debianlogo-3.jpg

An image of a chicken, picking at 2+ grains and still not sated
comes to my mind.

Thomas



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

Re: mass ITPs

[Thomas Weber]

On 01/03/08 19:48 +0100, Christian Perrier wrote:
> There seems to be some crazyness about packaging new stuff these
> days. That would be fine.if only our existing packages were well
> maintained.which, for many of them is certainly not true.

Just for the record: every single package Rafael itp'd is already in
the archive as part of octave2.1-forge. Upstream decided to split this
up, so we follow. 

Thomas


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

Re: dpkg semi-hijack - an announcement (also, triggers)

[Thomas Weber]

Am Montag, den 10.03.2008, 11:24 +0100 schrieb Josselin Mouette:
> Le lundi 10 mars 2008 à 01:45 -0800, Mike Bird a écrit :
> > Hi Marc,
> > 
> > "needed" has several similar but distinct meanings.  None of the meanings
> > is more obvious than any other.  "Need" I remind you that if you had taken
> > the time to do the "necessary" homework you could have saved the readers
> > of this thread the "necessity" of ignoring your post?
> > 
> >   needed[2]:
> > To want strongly; to feel that one must have something.
> > 
> > Example:
> >   After ten days of hiking, I needed a shower and a shave.
> 
> Hi Mike,
> 
> Another example:
> After ten days of trolling, the Debian project needs Mike Bird
> to go to hell.
> 

Could all of you now please switch this to private mail? This is
debian-devel, neither debian-english-semantics nor debian-kindergarten.

Thanks
Thomas


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

Re: Misc development news (#6)

[Thomas Weber]

Am Dienstag, den 15.04.2008, 22:58 +0200 schrieb Raphael Hertzog:
> FTFBS on packages build-depending on libqt4-dev
> ---
> 
>  If your package is build-depending on libqt4-dev and is currently failing
>  to build from sources, please wait for the next qt4-x11 package revision
>  before adding a gazillion of build-deps to your package.
> 
>   -- Sune Vuorela

This isn't helpful for several reasons:
a) Burying this information in a wiki where people may or may not read
it in time (I just reverted a change already done in SVN).
b) What is the current/next revision of qt4-x11 at the time of writing
(ie, is this still valid or already obsoleted)?

Thomas



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

Re: [OT] Need old Packages.gz and Release Files

[Thomas Weber]

Am Freitag, den 25.04.2008, 13:16 +0700 schrieb Mikhail Gusarov:
> Twas brillig at 10:56:18 25.04.2008 UTC+08 when [EMAIL PROTECTED] did gyre 
> and gimble:
> 
>  j> By the way, it would be great if the mirrors kept more than just a
>  j> week of Diffs. It seems every time I get back from a trip, I end up
>  j> uploading the whole Packages.gz file again. Two weeks worth would be
>  j> better.
> 
> ...for you.
> 
> Think about two-week trips, three-week trips, month-long vacations,
> three-months-long vacations, round-the-world trips... Won't this result
> in keeping whole year of diffs?

No, you can the take the combined size of all diffs as an upper bound.
If it becomes larger than the current Packages.gz file, it's time to
drop older diffs.

Thomas


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

Re: co-mentor for a GSoC proposal wanted: debbugs web submission

[Thomas Weber]

Am Freitag, den 16.03.2007, 20:11 +0900 schrieb Paul Wise:
> On Fri, 2007-03-16 at 11:52 +0100, Rafael Laboissiere wrote:
> 
> > Instead of a GUI or a web interface, what I would love to have is a
> > curses-capable version of reportbug.  As someone mentioned elsewhere in this
> > thread, browsing wnpp bug report titles in reportbug is a real pain.  A
> > curses scrollable window would help a lot here, in particular if we could
> > search for re patterns.
> 
> Try reportbug -u urwid. There is also -u newt, but it doesn't seem to
> work and has a big warning.

Any chance of including this information in reportbug's manpage? The
--help option doesn't tell which interface are available.

Thomas


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

Re: discussion with the FSF: GPLv3, GFDL, Nexenta

[Thomas Weber]

Hi, 

Am Montag, 4. Juni 2007 02:45:07 schrieb Wouter Verhelst:
> On Sun, Jun 03, 2007 at 05:09:57PM -0700, Don Armstrong wrote:
> > On Mon, 04 Jun 2007, Wouter Verhelst wrote:

> What I was trying to show is that the relevance of a copyright case
> brought against you in a jurisdiction outside of your immediate concern
> is zero, for all practical matters; that means you can simply ignore it,
> and nothing Bad will happen. Therefore, I don't think it makes it
> anything even remotely representing non-freeness.

You might want to read 
"Abkommen zwischen der Bundesrepublik Deutschland und dem Königreich Belgien
über die gegenseitige Anerkennung und Vollstreckung von gerichtlichen
Entscheidungen, Schiedssprüchen und öffentlichen Urkunden in Zivil- und
Handelssachen"

No idea how it is called in Belgium, but it's the German part of a treaty from 
1958 dealing precisely with that sort of thing. So, it seems extremely likely 
that if I win in Germany in a civil case, I can have this decision executed 
in Belgium. Additionally, you might want to check European law for similar 
agreements (which would mean that the jurisdiction of your immediate concern 
spans > 20 countries).

Thomas

Re: discussion with the FSF: GPLv3, GFDL, Nexenta

[Thomas Weber]

Am Montag, 4. Juni 2007 08:51:56 schrieb Arnoud Engelfriet:

Thanks for finding an english text.

> Just see EC Regulation 44/2001:
> "A judgment given in a Member State is to be recognised automatically, no
> special proceedings being necessary unless recognition is actually
> contested. A declaration that a foreign judgment is enforceable is to be
> issued after purely formal checks of the documents supplied."
> http://europa.eu/scadplus/leg/en/lvb/l33054.htm
>
> Most relevant is article 5(1) that says that "in matters relating to a
> contract, [jurisdiction is] in the courts for the place of performance of
> the obligation in question". If I'm in the Netherlands and distribute
> CDDL software to a Belgian citizen while violating the CDDL, the
> copyright holder has to come to the Netherlands, choice-of-venue
> (mostly) notwithstanding.


What about article 23(1)?
"If the parties, one or more of whom is domiciled in a Member State, have 
agreed that a court or the courts of a Member State are to have jurisdiction 
to settle any disputes which have arisen or which may arise in connection 
with a particular legal relationship, that court or those courts shall have 
jurisdiction."

But actually, that wasn't my point. I only wanted to show that "I'm living in 
X. If you sue me and win in Y, I just don't care" can be an expensive 
attitude in the EU.

> Arnoud Engelfriet, Dutch & European patent attorney - Speaking only for
> myself 

Ups, a professional. I'd better be quiet now ;)

Thomas



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

Re: License discussions in Debian

[Thomas Weber]

Am Dienstag, 5. Juni 2007 09:08:31 schrieb Frank Küster:
> Anthony Towns <[EMAIL PROTECTED]> wrote:
> > On Mon, Jun 04, 2007 at 11:08:39PM +0200, Frank K?ster wrote:
> And a mail like
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=350624;msg=142;att=0
> is not only not-helpful-at-all, it's really discouraging to see a
> discussion ending like this.  Well, in that particular case I'd
> understand if you don't answer to the bug, but the reasoning could be
> published elsewhere where Mr. $greps_for_his_name_on_debian_lists cannot
> answer easily.

I was the bug submitter. I asked Anthony in private mail and he gave a few 
reasons. I'm not really convinced by them, but in the end, it's not my 
responsability. I just make sure I don't install star on my systems and I'm 
done with it. If everyone else (maintainer, ftp-masters, mirror 
operators, ...) is happy with it, why should I bother any longer?

Thomas

Re: License discussions in Debian

[Thomas Weber]

Am Dienstag, 5. Juni 2007 14:20:40 schrieb Anthony Towns:
> On Tue, Jun 05, 2007 at 12:07:52PM +0200, Frank K?ster wrote:
> > You could ask Anthony whether you're allowed to publish his reasons on
> > -legal.  That would do the project a great favor.
>
> You could just ask me directly you know...

As my mail to you was private as well, I think Frank's approach was correct.


> ] Via Simon Phipps's talk at debconf, we've got Sun on the record
> ] as interpreting "choice of venue" as only being relevant when the
> ] two parties to a suit both have a presence in multiple jurisdictions,
> ] including the one that's "chosen", which means it's not a problem at all.
> ]
> ] For the other case, even if Sun did want to make German laws apply to
> ] an Australian or similar, I don't think that holds up as a claim anyway.
>
> I don't think that's a particularly useful addition to what's already
> been in this thread. 

Actually, it is. If you look at the sub-thread involving Arnoud Engelfriet, 
you will see that Simon's idea of ' "choice of venue" being only important 
for multinational companies' is flawed, at least for the case at hand (star, 
choice of venue: Berlin, Germany, Europe).

The same goes for the second paragraph as well (well, not for Australia and 
the United States, but EU is not that small, either).

Additionally, the cited text is Sun's interpretation. What's the 
interpretation of star's licensor?

Thomas


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

Re: Source package containing HTML-only form of texinfo doc

[Thomas Weber]

Hi, 

Am Donnerstag, 5. Juli 2007 16:02:13 schrieb [EMAIL PROTECTED]:

> > Am I misunderstanding what you're saying? octave2.9-htmldoc contains
> > this exact documentation that upstream is distributing.
>
>   Yes, but built from source, and the source of octave2.9-htmldoc contains
> the texinfo source. qtoctave doesn't, which is a breach of the GPL: you
> must be able to distribute the preferred form of modification, and not
> having it in the upstream sources - even when we know where they come from
> - makes it delicate for us to distribute it.
>
>   In other words, any users should be able to do
>
> apt-get source qtoctave
>
> and modify the documentation, which is not possible as the texinfo source
> is missing.

I'm one of Octave's Debian maintainers. 

The problematic part is that qtoctave is primarly a Windows application. I 
don't think they even have any sort of code for generating the HTML files 
from the Texinfo sources, so even including the texinfo files would still be 
a violation.

Maybe they should just update the documentation and use the HTML files from 
[1]. I think the files there have a more liberal license.

[1] http://www.gnu.org/software/octave/doc/interpreter/

Thomas


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

Re: Bug reports of DFSG violations are tagged ???lenny-ignore????

[Thomas Weber]

Am Dienstag, den 21.10.2008, 08:29 +0200 schrieb Marc Haber:
> On Mon, 20 Oct 2008 15:49:40 -0700, Thomas Bushnell BSG
> <[EMAIL PROTECTED]> wrote:
> >On Mon, 2008-10-20 at 22:26 +0100, Mark Brown wrote:
> >> No, really.  The kernel team are volunteers.  Ordering them to do things
> >> doesn't help at all; one could equally well send the same message to
> >> everyone working on Debian (or, indeed, the wider community) since they
> >> could also step up to the plate and help fix this issue.
> >
> >Of course.  These are RC bugs.  I would be happy to upload an NMU that
> >fixed the RC issue by removing support for the relevant hardware, and
> >dropping blobs from the source.  I don't think it's a very challenging
> >task, but I'm happy to do so.  Will that be ok?
> 
> You're not seriously thinking that a release without E100 support does
> make any sense and is any good for Debian, right?

How long do you want to ignore the issue, then? It's software without
source, every other package gets a REJECTED in NEW for such stuff.

Thomas


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

Re: Bug reports of DFSG violations are tagged ???lenny-ignore????

[Thomas Weber]

Am Dienstag, den 21.10.2008, 12:57 +0200 schrieb Pierre Habouzit:
> On Tue, Oct 21, 2008 at 09:04:21AM +, Thomas Weber wrote:
> > Am Dienstag, den 21.10.2008, 08:29 +0200 schrieb Marc Haber:
> > > On Mon, 20 Oct 2008 15:49:40 -0700, Thomas Bushnell BSG
> > > <[EMAIL PROTECTED]> wrote:
> > > >On Mon, 2008-10-20 at 22:26 +0100, Mark Brown wrote:
> > > >> No, really.  The kernel team are volunteers.  Ordering them to do 
> > > >> things
> > > >> doesn't help at all; one could equally well send the same message to
> > > >> everyone working on Debian (or, indeed, the wider community) since they
> > > >> could also step up to the plate and help fix this issue.
> > > >
> > > >Of course.  These are RC bugs.  I would be happy to upload an NMU that
> > > >fixed the RC issue by removing support for the relevant hardware, and
> > > >dropping blobs from the source.  I don't think it's a very challenging
> > > >task, but I'm happy to do so.  Will that be ok?
> > > 
> > > You're not seriously thinking that a release without E100 support does
> > > make any sense and is any good for Debian, right?
> > 
> > How long do you want to ignore the issue, then? It's software without
> > source, every other package gets a REJECTED in NEW for such stuff.
> 
> If we weren't doing compromises, then:

You are missing my point. We[1] got a reject for a documentation PDF
without source. So, we contacted upstream who checked the copyright with
the company in order to release the source for the documentation. And
yes, it's work, painful, whatever and I would have preferred not having
to do it.

The kind of "compromise" above makes it close to impossible to argue in
such cases: 

Upstream: "You are ignoring the issue in case X, why do you bother me
about Y? It's not even code, if you want the text, just extract it."

What do you expect me to say in such cases: "You are not the kernel."?

[1] Packages are group-maintained.

> I don't say it's nothing we should _care_ about, but at some point:
>   * you don't have the source of your BIOS;
>   * you don't have the VHDL source of your CPU and all the chipsets of
> your computer;
>   * I'm sure your laptop/computer has dozens of patented hardware bits,
> so you're supporting patents while buying it, you should do a
> pilgrimage to cleanse yourself from all that filth.

Yes, and what of the above is in Debian's archive? Frankly, if binary
firmware is okay, just say so in the DFSG. No problem with me. But then
please be consistent and stop forbidding uploads for documents without
source, too. Because I'm unable to explain the difference between
"firmware without source" and "binary documentation without source". Can
you explain it?

> Firmwares are here because it's cheaper nowadays to have a chip that is
> versatile and configured to a specific task. Older hardware had less
> firmwares because the chips were made specifically for the board it was
> in, and you had no problems with not having the source "code" of the
> chip. So really, I see there is a double standard here, and a lot of
> hypocrisy.

See above, the same tale about double standards can be told as soon as
other packages enter the picture.

Thomas


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

Re: Bug reports of DFSG violations are tagged ???lenny-ignore????

[Thomas Weber]

On Tue, Oct 21, 2008 at 05:06:29PM -0500, William Pitcock wrote:
> On Wed, 2008-10-22 at 09:03 +1100, Ben Finney wrote:
> > William Pitcock <[EMAIL PROTECTED]> writes:
> > 
> > > Unfortunately, those who contribute to Debian must be dedicated to
> > > ensuring future releases of Debian support the latest available
> > > hardware at time of release.
> > 
> > That's news to me. Where is such a dedication required? Is it some
> > special reading of the vague “our users” commitment, or do you get
> > this dedication from all Debian contributors some other way?
> > 
> > Does that dedication somehow override every DD's explicit commitment
> > to ensuring Debian is 100% DFSG-free in the Social Contract?
> 
> I worded that rather badly. You should imply "within acceptable terms of
> the DFSG" here... in this case, putting stuff in the nonfree firmware
> package in non-free is an acceptable solution.

May I suggest that people cool down a little bit and don't assume the
worst from the other participants of the discussion.

Shit happens[1], throwing mud doesn't improve the atmosphere at all.

[1] That includes, but is not limited to, bugs in packages and
suboptimal wording in e-mails.

Thomas


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

Re: Bug reports of DFSG violations are tagged 'lenny-ignore'?

[Thomas Weber]

Am Mittwoch, den 22.10.2008, 08:36 +0200 schrieb Bastian Blank:
> On Wed, Oct 22, 2008 at 08:07:52AM +0200, Michal Čihař wrote:
> > At least ipw2100 drivers changed firmware name if they required
> > different version, so I guess this is also used by others...
> 
> If they need an incompatible one. Not necessarily if they just need a
> newer one.

I'm not really into hardware, but how often does kernel firmware change
in an incompatible way? It seems to defeat its purpose (providing a
stable interface a driver can talk to).

Thanks
Thomas


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

Re: Bug reports of DFSG violations are tagged ???lenny-ignore????

[Thomas Weber]

On Sat, Oct 25, 2008 at 01:47:15AM -0700, Steve Langasek wrote:
> On Tue, Oct 21, 2008 at 01:15:44PM +0200, Thomas Weber wrote:
> > You are missing my point. We[1] got a reject for a documentation PDF
> > without source. So, we contacted upstream who checked the copyright with
> > the company in order to release the source for the documentation. And
> > yes, it's work, painful, whatever and I would have preferred not having
> > to do it.
> 
> Could you please elaborate here?  

Sure, what do you want to know?

Rejection email:
http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2008-April/003819.html

Upstream tarball:
http://downloads.sourceforge.net/octave/fixed-0.7.5.tar.gz?download

Copyright of the PDF when uploaded:

Copyright C 2004 Motorola Inc
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
Permission is granted to copy and distribute translations of this manual
into another language, under the same conditions as for modified
versions.

The "C" above was a copyright symbol.

Thomas


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

Re: RC bug for >10 packages

[Thomas Weber]

On Sat, Oct 25, 2008 at 06:25:47PM +0200, Francis Tyers wrote:
> We've come up with a better solution, which is to add dependencies to
> the apertium package, and then make the apertium package depend on a
> particular version of pcre3. It's safer this way, as I can't find out
> anything about compatibility of precompiled regular expressions in pcre
> between versions, so better to assume they aren't.

Your assumption is correct, from "man pcreprecompile":

"If you save compiled patterns to a file, you can copy them to a
different host and run them there. This works even if the new host has
the opposite endianness to the one on which the patterns were compiled.
There may be a small performance penalty, but it should be
insignificant.  However, compiling regular expressions  with  one
version of PCRE for use with a different version is not guaranteed to
work and may cause crashes."

Thomas


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

Re: Bug reports of DFSG violations are tagged ???lenny-ignore????

[Thomas Weber]

On Mon, Oct 27, 2008 at 10:30:10PM +0200, Holger Levsen wrote:
> Hi,
> 
> On Monday 27 October 2008 19:35, Frank Küster wrote:
> > If the PDF is frozen documentation, it's probably worth the effort. If
> > upstream changes the PDF with every new version, you should ask them for
> > their sources instead.
> 
> What if they use openoffice.org to edit the pdf and the pdf is the source?

Can we please come back to discussing _real_ problems and deal with
hypothetical ones when they arise?

Thomas


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

Re: [DRAFT] resolving DFSG violations

[Thomas Weber]

Am Donnerstag, den 30.10.2008, 01:48 -0500 schrieb William Pitcock:
> On Wed, 2008-10-29 at 22:52 -0700, Thomas Bushnell BSG wrote:
> > But regardless, Debian has promised that Debian is only free software.
> 
> Then why does Debian have non-free? Is that not part of Debian?

"Thus, although non-free works are not a part of Debian, ..."
Social contract, paragraph 5.


> If non-free is meant to be an opt-in part of Debian, then put the
> distributable firmware there and be done with it.

You know, quite a big part of the discussion is about whether this is 
a) feasible at all
b) feasible so short before a release

Thomas




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

Re: First call for votes for the Lenny release GR

[Thomas Weber]

Am Montag, den 15.12.2008, 00:31 + schrieb Steve McIntyre:
> On Sun, Dec 14, 2008 at 10:23:18PM +0100, Cyril Brulebois wrote:
> >Debian Project Secretary  (13/12/2008):
> >> 
> >>FIRST CALL FOR VOTES FOR THE Lenny Release General Resolution
> >>=  === = === === = === === ==
> >> 
> >> Voting period starts  00:00:01 UTC on Sunday,   December 14th, 2008
> >> Votes must be received by 23:59:59 UTC on Saturday, December 21st, 2008
> >  ^^^
> >
> >Can we please have a reference to the mail/thread about shortening the
> >voting period?
> 
> I'm fairly certain there wasn't one.

http://lists.debian.org/debian-vote/2008/11/msg00046.html

I read this message as "get over with it as fast as possible", which is
what Manoj is doing here. 

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: First call for votes for the Lenny release GR

[Thomas Weber]

Am Montag, den 15.12.2008, 10:06 + schrieb Steve McIntyre:
> I've been talking with Manoj already, in private to try and avoid
> flaming. I specifically asked him to delay this vote until the
> numerous problems with it were fixed, and it was started anyway. I'm
> *really* not happy with that, and I'm following through now.

Uh, I don't quite get this: you shortened the discussion period, but at
the same time asked the secretary to delay the vote? Why didn't you use
your position to at least delay it as far as within your power?

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Josselin Mouette and Planet Debian

[Thomas Weber]

Am Donnerstag, den 18.12.2008, 22:51 -0800 schrieb Steve Langasek:
> On Fri, Dec 19, 2008 at 01:04:05AM +0100, Johannes Wiedersich wrote:
> > I am really speechless The French seem to have a completely
> > different understanding of the English language used in all these
> > matters than almost every one else in the world. I guess it is really
> > time that Joss realizes that what might have been OK to be written in
> > French is considered an insult when written in English to thousands of
> > readers from different cultural backgrounds.
> 
> No, the problem is that certain of our French developers *think* that the
> rest of the world just doesn't understand their French humor and that
> something has been lost in translation.
> 
> When the reality is that we understand it just fine, and think they're
> assholes for it.
> 
> It's only a cultural difference if you're counting Kindergarten as a
> "culture".

I find this strange, given that not too long ago you categorized the
participants of debian-legal as "wankers".

http://lists.debian.org/debian-devel/2008/12/msg00174.html

Joss' messages can be understood as pretty bad humor. Was your message
above also meant as a joke?

Or do you need to let of some steam here, because such behaviour is
unacceptable on Ubuntu lists?

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Josselin Mouette and Planet Debian

[Thomas Weber]

On Fri, Dec 19, 2008 at 08:31:15PM -0800, Steve Langasek wrote:
> On Fri, Dec 19, 2008 at 10:11:25AM +0100, Thomas Weber wrote:
> > > No, the problem is that certain of our French developers *think* that the
> > > rest of the world just doesn't understand their French humor and that
> > > something has been lost in translation.
> 
> > > When the reality is that we understand it just fine, and think they're
> > > assholes for it.
> 
> > > It's only a cultural difference if you're counting Kindergarten as a
> > > "culture".
> 
> > I find this strange, given that not too long ago you categorized the
> > participants of debian-legal as "wankers".
> 
> > http://lists.debian.org/debian-devel/2008/12/msg00174.html
> 
> > Joss' messages can be understood as pretty bad humor. Was your message
> > above also meant as a joke?
> 
> No.  What part of that message would lead you to think I was joking?
Nothing lead me to that, but then I'm not a native English speaker, so I
may overlook subtleties.

> > Or do you need to let of some steam here, because such behaviour is
> > unacceptable on Ubuntu lists?
> 
> There's no ubuntu-legal list infested with leeches who think it's their
> business to tell Ubuntu how to interpret its own license requirements
> without ever having contributed a line of code to Ubuntu, so I don't think
> the analogy holds.

Sorry, but I don't think the idea of 'politeness' differs so much over
different mailing lists. Either you don't insult people or you do. And
my point wasn't about debian-legal, obviously. But rather about people
insulting people one day and then finger-pointing at other people
insulting other people the next day.

If you expect a certain behaviour, the best start is showing it
yourself.

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: is it a DFSG breach or not?

[Thomas Weber]

On Sat, Jan 24, 2009 at 10:23:33PM +0300, Dmitry E. Oboukhov wrote:
> I am asked to act as a sponsor of phpunit  [*]  package.   However  there's
> a situation that needs an advice.  There's  JS  in  the  package  that  was
> run through the filter which deletes comments and spaces.  In  fact  it  is
> like Java script passed through obfuscator.

According to the README in yui-2.6.0/build/yahoo-dom-events, this file
is constructed from three other files in the source code. These files
are heavily commented.

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Short report on Debian at UseR! 2007 conference at Iowa State Univ.

[Thomas Weber]

Hi, 

Am Dienstag, den 21.08.2007, 11:11 -0500 schrieb Dirk Eddelbuettel: 
> E.g. a good example of how it's nice to have the code in one place (as
> opposed to dozens of debian/rules files) is that just recently I learned about
> a neat x11 framebuffer server wrapper, 

Which package is that? I might need this wrapper for Octave. 

Thanks
Thomas



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

Re: Missing libatlas3 on arm prevents blitz++ from entering testing

[Thomas Weber]

Am Montag, den 17.09.2007, 20:33 -0700 schrieb Steve Langasek:
> Andreas,
> 
> On Mon, Sep 17, 2007 at 10:46:00PM +0200, Andreas Tille wrote:
> 
> > according to
> 
> >http://qa.debian.org/excuses.php?package=blitz%2B%2B
> 
> > there is no libatlas.so.3 available for arm which prevents blitz++
> > from entering testing.  I also did not found any useful atlas
> > implementation for arm:
> 
> >
> > http://packages.debian.org/search?searchon=contents&keywords=atlas&mode=path&suite=unstable&arch=arm
> 
> > So what would be the best idea to get blitz++ into testing?
> > Did I missed something?

Build-depend on refblas3 and lapack like the following:
refblas3-dev | atlas3-base-dev, lapack3-dev | atlas3-base-dev

ATLAS provides interfaces according to the BLAS standard, so refblas and
lapack are drop-in replacements[1] (also much slower, but that's not the
point: on more common architectures, people might have local faster
libraries that they might then use instead of the libraries in Debian).

Directly depending just on ATLAS is usually not what you want.


> I don't understand why atlas3 has such non-standard dev package handling,

Its build system is anything but standard and you normally *don't want*
it at build time.


> Once this is implemented, you can ask the maintainers of
> Packages-arch-specific to mark your package as "not for arm" as seen by the
> buildds, and ask the ftp team to remove the arm binary from unstable.

I think that's unneccessary, unless there's something in the blitz++
library that prevents it from building on ARM.

[1] Actually, it's the other way round: ATLAS should be a drop-in for
refblas and lapack.

Thomas


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

Re: Testing parallel builds

[Thomas Weber]

Am Dienstag, den 09.10.2007, 00:00 +0900 schrieb Michal Čihař:
> Hello
> 
> Dne Mon, 08 Oct 2007 16:46:46 +0200
> Pierre Habouzit <[EMAIL PROTECTED]> napsal(a):
> 
> > On Mon, Oct 08, 2007 at 02:39:59PM +, Michal Čihař wrote:
> > > BTW: When mentioning CMake, are there any known problems with parallel
> > > build with it? I just randomly tried it last week and it seemed to be
> > > broken at least in some cases.
> > 
> >   I reckon I don't know for sure. Like automake I believe you can write
> > extensions that break parallel build quite easily.
> 
> Well I'm not aware I'd use anything besides various crap that detects
> libraries and includes. I should probably do my homework and look
> deeper at that issue.

Trivial example: a package that builds a binary which in turn is used to
create some source files for later compile. 

If the source files don't have the binary as dependency, your build will
break with parallel mode.

Thomas


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

Bug#458456: ITP: libimage-metadata-jpeg-perl -- Perl extension for showing/modifying JPEG (meta)data

[Rene Weber]

Package: wnpp
Severity: wishlist
Owner: Rene Weber <[EMAIL PROTECTED]>

* Package name: libimage-metadata-jpeg-perl
  Version : 0.15
  Upstream Author : Stefano Bettelli <[EMAIL PROTECTED]>
* URL : http://search.cpan.org/~bettelli/
* License : GPL
  Programming Lang: Perl
  Description : Perl extension for showing/modifying JPEG (meta)data

This package provides an interface for reading and interpreting the
content of JPEG segments, in particular of those segments containing
metadata (like TIFF headers, thumbnails, Exif info, IPTC info, comments,
etc.). Some segments can even be modified and rewritten to disk.

This is being packaged as a dependency of Mapivi which I will be ITPing
shortly.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)



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

Bug#458460: ITP: mapivi -- Photo viewer and organizer with emphasis on IPTC fields

[Rene Weber]

Package: wnpp
Severity: wishlist
Owner: Rene Weber <[EMAIL PROTECTED]>

* Package name: mapivi
  Version : 0.9.1
  Upstream Author : Martin Herrmann <[EMAIL PROTECTED]>
* URL : http://mapivi.sourceforge.net/mapivi.shtml
* License : GPL
  Programming Lang: Perl
  Description : Photo viewer and organizer with emphasis on IPTC fields

Cross-platform (UNIX, Mac OS X and Windows) picture manager and organizer,
Mapivi is a stand alone tool, there is no need for a web server, online
access or a database.

Deals with EXIF data (like timestamp, camera model, focal length, exposure
time, aperture, etc.), and is able to rename the pictures according to their
internal date/time, to display and modify JPEG comments and to do lossless
rotation.

The idea of using Mapivi as an picture organizer is to keep user, EXIF, and
IPTC information where it belongs -- in the pictures -- as well in a
searchable Mapivi database.

Mapivi is also able to do image processing. Mapivi serves here as a
frontend (GUI) for many proven command line tools, like the Image Magick
tools.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)



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

Re: postscropt document without source

[Thomas Weber]

Am Montag, den 14.01.2008, 10:41 + schrieb Colin Tuckley:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Joerg Jaspert wrote:
> 
> > Source, as we ship the source too. For the (C)/license checks in NEW it
> > (*nearly*) doesn't matter if you ship it in the binary package or not.
> 
> Right, so a source tarball repack is needed.

Which blas package is this? The one from netlib?

Thomas


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

Re: postscropt document without source

[Thomas Weber]

Am Montag, den 14.01.2008, 17:22 +0530 schrieb Kumar Appaiah:
> On Mon, Jan 14, 2008 at 11:49:05AM +0100, Thomas Weber wrote:
> > > Right, so a source tarball repack is needed.
> > 
> > Which blas package is this? The one from netlib?
> 
> Yes. Please see the latest mails from debian-toolchain for context.

Okay, thanks for doing the grunt work. But which upstream tarball are
you using? Everything I could find at Netlib doesn't have a PDF at all.

Thanks
Thomas


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

Re: Changes in dpkg Pre-Depends

[Thomas Weber]

On Tue, Feb 23, 2010 at 04:01:51PM +0100, Marco d'Itri wrote:
> On Feb 23, Josselin Mouette  wrote:
> 
> > Le mardi 23 février 2010 à 14:43 +0100, Marco d'Itri a écrit : 
> > > Using non-PIC code for a 5% speed up looks like an acceptable trade off
> > > to me, but it really must be restricted only to architectures which
> > > need it.
> > Those who worry about a 5% speedup should use amd64. Which is an
> > architecture that doesn???t need it.
> Cool, where can I send you the invoice for the replacement hardware?

You have x86 hardware that is so old that it doesn't run amd64, but at
the same moment you care about speed?

Thomas


-- 
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/20100223175800.ga12...@atlan

Re: Changes in dpkg Pre-Depends

[Thomas Weber]

On Tue, Feb 23, 2010 at 08:32:09PM +0100, Marco d'Itri wrote:
> On Feb 23, Thomas Weber  wrote:
> 
> > You have x86 hardware that is so old that it doesn't run amd64, but at
> > the same moment you care about speed?
> Why should I not care about speed if the hardware is slow?

That you care personally about it is reasonable. That you force that
solution upon others only if the trade-off is reasonable. In other
words, only if there is a significant part of Debian users positively
affected by this trade-off.

And sorry, you don't care about speed if you still run *that* old
hardware, otherwise you would have upgraded. (I bought my current
desktop used and it is already able to run amd64).

> Anyway, there are often good reasons to use x86 on modern hardware
> (think about laptops and smaller VPSes).

I don't quite get the advantage of x86 on moder laptops. Care to
explain?

Thomas


-- 
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/20100223220335.ga25...@atlan

Re: Changes in dpkg Pre-Depends

[Thomas Weber]

On Tue, Feb 23, 2010 at 04:45:22PM -0500, Joey Hess wrote:
> Thomas Weber wrote:
> > You have x86 hardware that is so old that it doesn't run amd64, but at
> > the same moment you care about speed?
> 
> It's not particularly hard to find new hardware with 32 bit Atom chips
> in it. There's this whole "netbook" thing..

Right, and following Wikipedia, they are clocked at 2GHz at most. I have
some problem understanding someone who buys such a system and at the
same time cares about 5% speed difference.

Thomas


-- 
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/20100223222502.gb29...@atlan

Re: need help of Octave language expert

[Thomas Weber]

Hi, 

I'm cc'ing debian-devel, so people see that there is an answer. If
whoever wants to continue the discussion, please strongly consider
dropping debian-devel -- the list is noisy enough.

On Wed, Mar 10, 2010 at 12:06:06PM +0900, Atsuhito Kohda wrote:
> Hi all,
> 
> I, a maintainer of TeXmacs, try to make TeXmacs as sane
> as possible before squeeze release.
> 
> I noticed recently that if one starts Octave plugin under 
> TeXmacs, it displays an error messages as follows:
> 
> -
> parse error near line 8 of file 
> /usr/share/texmacs/TeXmacs/plugins/octave/octave/.octaverc
> 
>   syntax error
> 
> >>>gset terminal postscript eps enhanced color;

Directly accessing gnuplot (which is what 'gset' did) is deprecated in
octave3.0 and even more in the 3.2 series. Spending time on this issue
is probably wasted, unless TeXmacs' upstream is willing to adapt the
necessary changes.

Following 
http://old.nabble.com/octave-plugin-maintainership-td26618436.html
it seems Mansour Moufid wanted to take over maintenance of the plugin. I
suggest getting in contact with him.


> I attach problematic files mentioned in the above messsages.
> If someone finds any fix, I greatly appreciate.

In essence, the plot commands in the file need a rewrite. Sorry, but my
problem is just the other way round: I have zero knowledge about
TeXmacs.

Thomas


-- 
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/20100310073433.ga11...@atlan

Re: German Debian (was: Processed: ipv6 release goal)

[Thomas Weber]

On Wed, Mar 24, 2010 at 04:38:49PM +0100, Hendrik Sattler wrote:
> Zitat von Marc Haber :
>
> Directly from www.debian.org (english, then German, then translated back):
> "it comes with over 25000 packages, precompiled software bundled up in a 
> nice format for easy installation on your machine."
> -> "Es enthält mehr als 25000 Softwarepakete, vorkompilierte Software in 
> einfach zu installierenden Paketen."
> -> "It contains more than 25000 software packages, precompiled software 
> in easily installable packages."
>
> From a good translation, I'd expect that the reverse is the original  
> text in some form. 

That is an unfounded expectation. It's a well known effect that
translations tend to be more explicit than the original text.  
See
http://www.linguateca.pt/documentos/Frankenberg-Garcia2004.doc
for an analysis (especially table 6).

> Additionally, the translations often sound too formal to a native
> speaker:
> "Debian ist ein freies Betriebssystem (OS) für Ihren Rechner."
> Although "Ihren" is the formal translation of "your" (which has a formal 
> and a non-formal translation in German), capitalizing that word is very 
> formal (e.g. used in directly addressed letters). To avoid that, it is 
> way more common to not address the reader directly. 

$ lynx --dump  http://www.duden.de/firmenloesungen/index.php?nid=15 | grep Ihren

For non-german readers: the 'Duden' is usually considered to be *the*
reference for spelling in Germany.

But ignoring that, how do you avoid addressing the reader when
translating the snippet "for your computer" and at the same time keep
your expectation above that the reverse translation should come really
close to the original text? 
If you don't address the reader in the translation, there's no way to
get the 'addressing' back in the reverse translation, is there?

And these are exactly the kind of problems translators have.

Thomas


-- 
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/20100324185841.ga10...@atlan

Re: Recent changes in dpkg

[Thomas Weber]

On Wed, May 26, 2010 at 10:34:32PM +0100, Neil Williams wrote:
> On Wed, 26 May 2010 22:59:25 +0200
> Iustin Pop  wrote:
> 
> > On Wed, May 26, 2010 at 10:43:36PM +0200, Bernd Zeimetz wrote:
> > > On 05/24/2010 11:05 AM, Raphael Hertzog wrote:
> 
> I think the announcement is wrong, we cannot ever expect every single
> package to be touched for any single change. We don't even do that when
> libc changes SONAME - that only affects compiled packages, this
> theoretically affects all source packages which means huge numbers of
> rebuilds and transitions.
> 
> There is nothing wrong with a source package that glides through several
> stable releases without needing a rebuild, especially if it only
> builds an Arch:all binary package. As long as it is bug free, an ancient
> standards version alone is not sufficient reason to change anything in
> the package or make any upload just for the sake of making an upload.

So, we are talking about packages that have 
a) no (fixed) bug reports
b) no new upstream version 
in 4 years. 
How many packages are we talking about here? Is there a way to get the
number of packages that have the same version in Lenny and Squeeze?

Anyway, I don't think asking for an upload once every 4 years is so much
of a burden.

Thomas


-- 
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/20100527204747.ga12...@atlan

Re: Recent changes in dpkg

[Thomas Weber]

On Thu, May 27, 2010 at 07:45:30PM -0400, James Vega wrote:
> On Thu, May 27, 2010 at 10:47:47PM +0200, Thomas Weber wrote:
> > How many packages are we talking about here? Is there a way to get the
> > number of packages that have the same version in Lenny and Squeeze?
> 
> According to a quick query on UDD, there are 3169 source packages which
> have the same source version in Lenny and Squeeze.  746 when comparing
> Etch and Squeeze.

Following up on this (thanks James):

I would be grateful if someone could check the following queries (i.e.,
if they do what the comment says they do):


-- up-to-date packages with same version in lenny and squeeze
---
SELECT count(s1.source) FROM sources s1, sources s2, dehs dehs
WHERE s1.source  = s2.source
AND   s1.version = s2.version
AND   s1.release = 'lenny'
AND   s2.release = 'squeeze'
AND   s1.source  = dehs.source
AND   dehs.unstable_status = 'uptodate';

Result: 1059


-- Number of packages that didn't have any bugs ever, are uptodate and
-- not orphaned
---
SELECT count(*) FROM (
SELECT s1.source FROM sources s1, sources s2, dehs dehs
WHERE s1.source  = s2.source
AND   s1.version = s2.version
AND   s1.release = 'lenny'
AND   s2.release = 'squeeze'
AND   s1.source  = dehs.source
AND   dehs.unstable_status = 'uptodate'
) AS psources
WHERE psources.source NOT IN (SELECT bugs.source FROM bugs)
AND psources.source NOT IN (SELECT source FROM orphaned_packages)
;

Result: 634


-- Number of packages that have only closed bugs, are up-to-date and not
-- orphaned
---
SELECT count(*) FROM (
SELECT s1.source FROM sources s1, sources s2, dehs dehs
WHERE s1.source  = s2.source
AND   s1.version = s2.version
AND   s1.release = 'lenny'
AND   s2.release = 'squeeze'
AND   s1.source  = dehs.source
AND   dehs.unstable_status = 'uptodate'
) AS psources
WHERE psources.source IN (
SELECT bugs.source FROM bugs
WHERE bugs.status IN ('done', 'fixed')
)
AND psources.source NOT IN (SELECT source FROM orphaned_packages)
;

Result: 55
---



So, we are talking about 1000 packages which are up-to-date in
unstable currently. Bugs don't change that picture much. I consider this
manageable during a full cycle.

And frankly, arguing back and forth about this is an exercise in
futility: 
Is the new format worse than the old one? No. 
Does it offer advantages over the old one? Yes, maybe not for all
packages, but for some.
So, let's make life easier for the dpkg developers and convert our
packages. It's not that much of a burden (From my experience, it's far
less work than even the most trivial bug fix).

Thomas


-- 
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/20100529121727.ga28...@atlan

Re: Atlas proposal

[Thomas Weber]

On Wed, Aug 18, 2010 at 01:59:59PM +0200, Sylvestre Ledru wrote:
> I am more concern about advanced users of scientific computing software
> (Scilab, R, Octave...) which are familiar with such tools but not
> familiar enough with the internals. 
> They just see these software as a whole and would not guess that
> changing RefBLAS => Atlas could improve the performances to a 40
> factor...

Oh, that's not a problem in practice. They will be told so when asking
on the mailing lists of those projects about the speed. Apart from that,
putting ATLAS into Recommends: has served fine, at least for the Octave
packages in Debian.

> Here, at Scilab (and other people at the DebConf reported me the same
> experiences), it is not rare that people are complaining about the speed
> of the software because RefBLAS is used as the linear algebra library. 

That's because you are a bad, bad boy ;) and don't recommend at least the
libatlas3gf-base package. 
Personally, I would prefer to have just one compiled ATLAS package with
support for different instruction sets. Yes, this doesn't cater for
different cache sizes, but there's a limit on what we as distribution
can provide.

I don't have any preference about the -auto package for local
compilation.

Thomas


-- 
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/20100818183531.ga11...@atlan

Re: [poll] Ubuntu column on DDPO visible by default?

[Thomas Weber]

On Thu, Aug 26, 2010 at 07:42:07AM +0200, Lucas Nussbaum wrote:
> I don't see what a discussion on -devel@ would bring. We are unlikely to
> come up with a better choice of solutions than what we already have
> (keep it on by default, revert the change and make it disabled by
> default).

Maybe this is a stupid question, but what purpose does the Ubuntu column
have at all? If I'm interested in a package in Ubuntu, that's what
Launchpad is for. I mean, we don't have the information for the 120
other derivatives there, either (should we ever have that, I'm not sure
that "it's just 120 clicks and then it's stored in a cookie" would cut
it, btw.).

Thomas


-- 
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/20100826212048.ga13...@atlan

Re: plagiarism of reiserfs by Debian

[Marcel Weber]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
First I have to say, that I even did not realize, that the credits had 
been removed.

I think Hans has a good point. The inclusion of credits is something 
that should be respected. Free software does not mean that you can do 
what you want with a piece of code, but that you're allowed to use, 
modify and redistribute it freely, respecting it's license.

Even a credit that goes into the direction of a commercial has to be 
respected, if the license forbids it's removal. The same way we (the 
debian population) insist on the proper use of the most common GPL V2, 
so other licences have to be respected as well. How would we complain 
if a company like Microsoft would include GPL based software in their 
products without mentioning and crediting it. And anyone who fears that 
free software could become commercial sponsored software must exclude 
this kind of software from the distribution instead of violating 
licences.

Hans, I hope that the removal of these credits was a mistake and that 
they're going to be included in future releases of testing. ReiserFS is 
a really fine piece of software and anyone who helped with it's 
development should have the right to be credited if he or she wants so.

Perhaps someone should file a bug against this.
Regards
Marcel
Am Samstag, 19.04.03, um 18:07 Uhr (Europe/Zurich) schrieb Hans Reiser:
Please explain your reasons for removing the credits and attributions 
from the reiserfs utilities in violation of our copyright.

You'll note that ReiserFS anticipated the GNU GPL V3 by including 
clauses that forbid removal of credits in its license, and for a long 
time I have been telling Stallman that he needs to get V3 of the GPL 
out the door.

By the way, does Debian support as a matter of principle the 
decrediting of Stallman and KDE by RedHat?  I had really expected this 
from RedHat, not Debian, when I wrote those clauses.

In the academic world, this is called plagiarism.  In the academic 
world, knowledge is shared but fairly credited.  The GPL is born of 
the academic tradition.

--
Hans

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


- ---
PGP / GPG Key:  http://www.ncpro.com/GPG/mmweber-at-ncpro-com.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (Darwin)
iD8DBQE+oY821EXMUTKVE5URAqQrAKCvtbJ/cP1B6J0ZzB2b1KtFPdP4YQCeIyY/
ls+MGfkxc3Kpt+Soe/31hjs=
=zc6y
-END PGP SIGNATURE-

Re: plagiarism of reiserfs by Debian

[Marcel Weber]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 20.04.03, um 01:06 Uhr (Europe/Zurich) schrieb Chris Cheney:
First of all emacs is pure bloat so who cares what it does... Vim has
one line about Ugandan orphans at startup, until now I didn't even
notice it was there. If had been pages of crap like what is spewed from
mkfs.reiserfs it would have probably been removed as well, unless it
was against Vim's license, which happens not to be GPL. As far as I can
tell if it annoyed someone enough it is legal under Vim's license to
remove the Uganda message as well, they only require the license text
itself to remain with the application.  A GPLv3 allowing spamware would
be very annoying, I hope it doesn't happen. If anything this stupid
reiserfs spamware should be spewed before the program runs, not after,
so that the user can see what actually occured without having to scroll
back up, which depending on their console type might be difficult.
Chris

All I can say to this is: use what you like, resp. if you don't like 
bloated software or spamware do not use it. My point is, that it should 
be a right of the original authors of the software to include credits. 
If someone else does a complete rewrite of the software, okay than we 
can discuss it, but if the rewrite means only the removal of the 
credits it is questionable.

But first of all, before we continue this discussion: What exactly has 
been removed? A readme file, the outputs during boot time, the outputs 
of mkfs.reiserfs? Has this output any impact on the usability of the 
software, so that there were good reasons the remove it? Has the 
license been violated by removing the credits?

Marcel
- ---
PGP / GPG Key:  http://www.ncpro.com/GPG/mmweber-at-ncpro-com.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (Darwin)
iD8DBQE+oe6k1EXMUTKVE5URAnmyAKCTpeRYv6c45/3NpK7/jFZvxa6hIACgw8OX
VFGEUd3wnUNsuzu0JQTAXcY=
=ZQWW
-END PGP SIGNATURE-

Re: aag - wrapper for apt-get with support for recommend and suggests field

[Kai Weber]

On Tue, Apr 29, 2003 at 03:58:34PM +0200, Alexander Wirt wrote:

> > Why not just use aptitude?[1]
> Its interactive, I don't want to launch a GUI if I want so simple add a
> package. Additionally it seams that aptitude is currently broken in Sid.
> So this are two good reasons for me.

aptitude can be used interactive, too.

aptitude install foo

Kai

Re: ITP: latex209 -- macro files of LaTeX 2.09 25-mar-1992 version

[Olaf Weber]

Atsuhito Kohda writes:

> From: Agustin Martin Domingo <[EMAIL PROTECTED]>
> Subject: Re: ITP: latex209 -- macro files of LaTeX 2.09 25-mar-1992 version
> Date: Fri, 16 May 2003 13:50:39 +0200

>> I am cc'ing this message to the debian-tetex-maint list. I think they 
>> would also like to know about this and will have a much better knowledge 
>> than I have about how possible it is and the incompatibilities that 
>> might arise.

> Even in the latest teTeX 2.0.2, there are settings in texmf.cnf
> as follows;

> TEXINPUTS.latex = .;$TEXMF/tex/{latex,generic,}//
> TEXINPUTS.latex209 = .;$TEXMF/tex/{latex209,generic,latex,}//

> that is, there is basically no problem to provide latex209 
> macros under $TEXMF/tex/latex209 if the command was called 
> "latex209".

Yes.  The main requirement for this to work well is that the latex209
installation be sufficiently complete, so that latex209 styles files
will always be found in preference to (possibly incompatible) latex2e
style files.  CTAN is a good place to get the distribution files.

But also note that historically, there has been little agreement on
what should be in a LaTeX 2.09 setup beyond Lamport's core.  One of
the results was that setups ended up being incompatible with each
other, even though they contained style files with same names.
Incompatible meaning one or both of "my document cannot be typeset
here" or "my document is typeset in a completely different way here".
So some finetuning will be required.

-- 
Olaf Weber

   (This space left blank for technical reasons.)

Bug#126610: ITP: mdctl -- utility to control 'new style' RAID disks

[Michael Weber]

Package: wnpp
Version: N/A; reported 2001-12-27
Severity: wishlist

* Package name: mdctl
  Version : 0.5-1
  Upstream Author : Neil Brown <[EMAIL PROTECTED]>
* URL : http://www.cse.unsw.edu.au/~neilb/source/mdctl/
* License : GPL
  Description : utility to control 'new style' RAID disks

  mdctl is a single program that can be used to control Linux MD
  devices.  It is intended to provide all the functionality of the
  mdutils and raidtools(2) but with a very different interface.
  .
  Unlike raidtools, mdctl can perform all functions without a
  configuration file.
  
  
-- System Information
Debian Release: woody
Architecture: i386
Kernel: Linux stargate 2.4.12 #2 SMP Thu Oct 25 22:44:15 CEST 2001 i686
Locale: LANG=C, LC_CTYPE=de_DE.ISO-8859-1


pgp5naZ6N787x.pgp
Description: PGP signature

Re: at least 260 packages broken on arm, powerpc and s390 due to wrong assumption on char signedness

[Olaf Weber]

Ganesan R writes:
> On Mon, Dec 31, 2001 at 01:33:37PM -0500, Colin Walters wrote:

>> It can't be larger than 255 (precisely because it is limited to a single
>> byte).

>> The more I think about it, the more it makes sense to always explicitly
>> declare all char variables as signed or unsigned; otherwise, you're just
>> asking for latent bugs.

Do remember that people port to systems other than Linux with gcc.
IIRC 'signed char' is not available in pre-ANSI C.  Code that was
written to be compilable on those platforms will use plain char and
extra checks.  For such code, these 'comparison is always {true|false}
due to limited range of datatype' messages are just annoying.

For portability the general rule is that _if_ you can get away with
using plain 'char', you should.

> This works only as long as you own all of your code. The problem is you can
> assign signed char to unsigned char or vice versa without any ill effects;
> you won't even get a compiler warning. However, the same can't be said for
> signed char * vs unsigned char *. If you are interfacing to external code
> (even functions like strcpy etc), you are asking for a major type casting
> headache. Worse, the problem won't even show up if you are developing on the
> "right" platform. I've gone down that route once and then gave up :-(. 

C++ is interesting in that regard, as it treats 'char', 'signed char',
and 'unsigned char' as three different types.  If you want to the C
string handling functions, you'll have to use 'char*' for strings, or
implement a workaround.

> Another thing that puzzles me since this whole debate started. If you look
> at the declaration of ctype.h functions (isalpha family), they take a int as
> an argument. The man page explicitly mentions the argument should be an
> unsigned char - obvious because a signed char would sign extend to an int.
> For platforms that default to signed char, and it appears majority of them
> do, you need to cast a "default" char type before calling ctype functions.
> Still, I have not seen any code that does it.

For this reason, implementations of the isalpha family tend to work
around the problem of being given negative-valued char arguments.  So
you get code like this in libc's ctype.h:

extern __inline int
    tolower (int __c) __THROW
{
  return __c >= -128 && __c < 256 ? __ctype_tolower[__c] : __c;
}

As result, faulty code sort-of works, and therefore never gets fixed.

-- 
Olaf Weber

   (This space left blank for technical reasons.)

Re: Please don't do this (code fragment)

[Olaf Weber]

Thomas Bushnell writes:

> Actually, the C standard does essentially guarantee two's complement
> arithmetic.  It specifies integer overflow behavior and
> signed/unsigned conversion behavior exactly.

It does for unsigned integers, but for signed integers overflow is
undefined behaviour.  The clearest statement of that is 3.4.3, albeit
in an example:

   3.4.3
 1 undefined behavior behavior, upon use of a nonportable or erroneous
   program construct or of erroneous data, for which this International
   Standard imposes no requirements
 2 NOTE Possible undefined behavior ranges from ignoring the situation
   completely with unpredictable results, to behaving during translation
   or program execution in a documented manner characteristic of the
   environment (with or without the issuance of a diagnostic message),
   to terminating a translation or execution (with the issuance of a
   diagnostic message). 
 3 EXAMPLE An example of undefined behavior is the behavior on integer
   overflow.

-- 
Olaf Weber

   (This space left blank for technical reasons.)

Re: How to avoid stealth installation of systemd?

[Thomas Weber]

On Tue, Jul 01, 2014 at 04:38:16PM +0200, Thijs Kinkhorst wrote:
> The responses from the systemd maintainers are indeed on the terse side,
> but I can imagine that your style of bug reporting does not invite our
> volunteers to spend more time on it.

This is not a question of spending time. An upgrade broke functionality
and purging systemd fixed this issue. That does not mean that it is a
bug in systemd, but it surely is a bug somewhere, be it the dependencies
(if systemd-shim is needed, why was it not installed during the upgrade?)
or the code of some other package.
Now, time is limited, but "I don't have time right now" is certainly not
a reason to close a bug within three hours.

Or, taking a different perspective: now that the issue is known, what is
done to prevent another user from hitting the very same issue in the
future?

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140701152012.GA4890@t61

Re: [Pkg-xfce-devel] Reverting to GNOME for jessie's default desktop

[Thomas Weber]

On Mon, Aug 11, 2014 at 03:20:49AM +0100, Anthony F McInerney wrote:
> Would the people who are claiming that blank cdr are cheaper than dvdr,
> especially in third world countries, please cite sources (shops, price
> checkers etc) of the price of say 5 pack or 10 pack, even up to 50pack of
> CD's, vs the same amount of DVD's, from those third world countries. Is the
> price of a small pack of DVD's really worth making the decision on a DE for
> debian?

Not sure why you'd want to go for third world countries, but let's look
at Germany (Aldi is one of the two biggest discounters here):
http://www.presseportal.de/pm/112096/2653870/aldi-senkt-preise-fuer-fischprodukte-oel-und-smoothies
CD-R Rohlinge (80 Minuten, je 50er Spindel) 5,99 Euro
DVD+R Rohlinge (je 20er Spindel)3,99 Euro 
That is 0.12 EUR per CDR and 0.20 EUR per DVD. 

> DVD readers/writers are cheaper now than CD readers/writers ever were.
I don't think it makes sense to ask for the price of one media (which is
in Cents), but then assume that the extra cost for a new DVD reader is
negligible.

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140811091514.GA5055@t61

Re: [FFmpeg-devel] Reintroducing FFmpeg to Debian

[Thomas Weber]

On Wed, Aug 13, 2014 at 12:53:41AM +0100, Kieran Kunhya wrote:
> > Also ive offered my resignation in the past.
> > I do still offer to resign from the FFmpeg leader position, if it
> > resolves this split between FFmpeg and Libav and make everyone work
> > together again. I never understood why people who once where friends
> > became mutually so hostile
> 
> The big elephant in the room in any discussion about even moving an
> iota in the direction of something resembling a resolution is that you
> as FFmpeg leader are a hidden leader. Every year at VDD when there is
> any informal discussion of any reconciliation as Attila alludes to the
> line "we can't get anywhere since Michael isn't here" is uttered and
> then everyone moves on.

Guys, 
this is getting nowhere. You need to solve this in a non-public
discussion. 
Given the amount of noise this has generated on debian-devel, I am sure
some of the Debian oldtimers[1] will be happy[2] to act as mediators for
such a discussion if it is organized in a somewhat convenient
location/conference/etc and if both sides consider such a mediation
helpful.

[1] With or without previous contacts with ffmpeg/libav.
[2] Think of it like "spending some hours to fix the issue" vs "spending
some hours to read more mails on debian-devel".

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140814065750.GA30581@t61

Bug#669102: ITP: sanlock -- a shared storage lock manager - useful for accessing vm images on a NAS or SAN

[David Weber]

Package: wnpp
Severity: wishlist
Owner: David Weber 

* Package name: sanlock
  Version : 2.1
  Upstream Author : David Teigland 
* URL : https://fedorahosted.org/sanlock/
* License : (LGPLv2+, GPLv2, GPLv2+)
  Programming Lang: (C, Python)
  Description : a shared storage lock manager - useful for accessing vm 
images on a NAS or SAN

Sanlock ensures that single disk cannot be used by more than one running VM at 
a time, across any host in a network.

See 
http://git.fedorahosted.org/git/?p=sanlock.git;a=blob;f=README.license;h=9bf5cae09fc44d7050c89535f0a8b49f23fcae3d;hb=HEAD
 for license



-- 
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/20120417093906.20315.52941.report...@debian-buildhost.munzinger.de

Re: Want to become a DM and co-maintainer

[Thomas Weber]

On Sat, Nov 12, 2011 at 08:54:24PM +0100, Svante Signell wrote:
> Where/how to apply to become a co-maintainer and a maintainer? The
> packages I'm interested into start with are: gnuradio and octave.

Octave is group-maintained, the group's list is at 
http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2011-November/thread.html

If you want to join, create an account on alioth and request to join the
group.

The above is a bit terse, so feel free to ask me if you need further
information.

Thomas


-- 
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/2012204340.GA3502@t61

Re: Do symbols make sense for C++

[Thomas Weber]

On Thu, Jan 26, 2012 at 08:08:07AM +, Sune Vuorela wrote:
> >Am I missing some trick to make them useful?
> 
> You miss pkgkde-symbolshelper written by the fabulous Modestas Vainius
> which is available in pkg-kde-tools.
> 
> http://pkg-kde.alioth.debian.org/symbolfiles.html

I'm currently creating symbol files for Octave in Debian. And quite
frankly, the way symbol files for C++ libraries are handled and
(especially) documented is totally frustrating.

There's exactly zero precise documentation on how to maintain symbol
files there. When the topic is brought up on mailing list, people point
at some tools from the KDE packages, but still there's no documentation
on the problem itself. The best example is dpkg-gensymbols(1) itself:

[topic is the 'optional' tag]:
"For example, most of C++ template instantiations fall into this category".

Yeah, great. Which instantiations cannot be marked as optional and how
do I recognize them? And if it's actually impossible to maintain symbol
files for C++ libraries (as Florian Weimer has claimed in this thread),
why doesn't the manpage just say so?

Thomas


-- 
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/20120126230100.GA1677@t61

Re: Do symbols make sense for C++

[Thomas Weber]

On Thu, Jan 26, 2012 at 11:49:06PM +, Sune Vuorela wrote:
> On 2012-01-26, Thomas Weber  wrote:
> > I'm currently creating symbol files for Octave in Debian. And quite
> > frankly, the way symbol files for C++ libraries are handled and
> > (especially) documented is totally frustrating.
> >
> > There's exactly zero precise documentation on how to maintain symbol
> > files there. When the topic is brought up on mailing list, people point
> > at some tools from the KDE packages, but still there's no documentation
> > on the problem itself. The best example is dpkg-gensymbols(1) itself:
> 
> did you read the link I posted? That's currently the best docs we have
> for pkgkde-symbolshelper. Better docs is always a nice thing to have.
> Please help improve it.

I have read the link, but that's not the issue. I want to understand the
problem and after that I can think about a tool to use. As an example,
the policy tells you what a package must look like - it doesn't just
document debhelper.

In other words, I'm lacking the knowledge for writing better
documentation for pkgkde-symbolhelper.
 
> > Yeah, great. Which instantiations cannot be marked as optional and how
> > do I recognize them? And if it's actually impossible to maintain symbol
> > files for C++ libraries (as Florian Weimer has claimed in this thread),
> > why doesn't the manpage just say so?
> 
> It is not at all impossible to maintain symbol files for c++ libraries.

I surely hope so, I have already spent quite some time on getting them
in shape for Octave ;). That doesn't change the fact that I'm less than
sure about some of the things I'm doing there.

Thomas


-- 
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/20120127140552.GA14865@t61

Re: lcms -> lcms2 migration

[Thomas Weber]

On Sun, Feb 09, 2014 at 02:21:46AM +0100, Moritz Mühlenhoff wrote:
> On Sun, Dec 29, 2013 at 11:25:48AM +0100, Bastien ROUCARIES wrote:
> > On Sun, Dec 29, 2013 at 10:33 AM, Moritz Mühlenhoff  
> > wrote:
> > > Hi,
> > > lcms needs to go for jessie in favour of lcms2 (#717928). (liblcms1-dev 
> > > -> liblcms2-dev)
> > > The maintainer seems MIA, so I'm going ahead. Below is a dd-list of 
> > > affected packages.
> > > This is a headsup as recommended by policy, I'll file bugs in a few weeks.
> > 
> > Could you note that lcms2 have some ABI problem, and it seems we
> > should do a transition in newer version. See
> > http://upstream-tracker.org/versions/lcms.html
> > and #701993.
> > 
> > So maybe we should made directly the transition to the new ABI ?
> 
> Sorry for the late reply. I wouldn't hold my breath for the transition
> to the new ABI, so moving from lcms1 to lcms2 is probably more important
> for now.

I have uploaded lcms2 2.5 to delayed/7 yesterday. After consulting with
the maintainer, I have added myself as co-maintainer.

Thomas


-- 
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/20140209120047.GA12676@t61

Re: Bug#741930: reportbug: add current init system information

[Thomas Weber]

On Sat, Mar 22, 2014 at 02:16:10PM +0100, Thijs Kinkhorst wrote:
> I think it should be in every report. reportbug currently adds the kernel
> version and what /bin/sh points to, and for both of those it can just as
> well be argued that they are not relevant to the majority of bug reports.
> For those bugs where it will matter, it will save wasted developer time in
> extra back and forths, which is the most precious resource we have.

And for those packages where it does not matter, it will cost extra
developer concentration/time in ignoring the noise. Sorry, but this
feels like being good for some, bad for all others. Developers
interested in the information should add bug scripts now and if we then
have the confirmed information that indeed lots of bug reports profit
from this information, then the change should be pushed to reportbug. 

And while we are at it, do we *really* need the information about
/bin/sh in at least a significant share of today's bug reports?

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140323074148.GA28868@t61

Re: Bug#741930: reportbug: add current init system information

[Thomas Weber]

On Sun, Mar 23, 2014 at 05:03:00PM +, brian m. carlson wrote:
> On Sun, Mar 23, 2014 at 08:41:48AM +0100, Thomas Weber wrote:
> > And while we are at it, do we *really* need the information about
> > /bin/sh in at least a significant share of today's bug reports?
> 
> You probably want it, because a decent number of people use a shell
> other than bash or dash as /bin/sh.  For example, one might use
> mksh-static because it's statically linked.  Also, someone might try to
> use zsh as /bin/sh, which doesn't work (it breaks debconf).

The fact that a lot of people use a variety of shells does not mean that
it makes sense to include it in *every* bug report. How important is the
user's shell for every database-, web- or fileserver? How for every office
application? How important is it for requests to the release team?
Every single bug report for these (pseudo)packages will include this
information, so it better be important.
 
> It's much better to have this information up front than to have to guess
> about it, especially since many reporters won't think to mention it.

If you know that your package might break by using a certain shell, you
can use reportbug's scripts. 

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140325071206.GA17855@t61

Re: Bug#23576: tetex-base: no write-permissions on public font directories

[Olaf Weber]

christoph martin writes:
> [EMAIL PROTECTED] writes:

>> Package: tetex-base
>> Version: 0.9-7
>> 
>> When the user first hits an ungenerated font then "permission denied"
>> messages are plentiful... :)

> The fonts get generated correctly, but it is a security problem to let
> everybody write the ls-R file.

But how much of a security risk is it?  It would mean a normal user
could clobber the file if he wanted to, which is a kind of denial of
service attack.  But are there any other risks?

And how do those risks compare with the ability to base a denial of
service attack on /var/cache/fonts (or whatever you call it) being
world-writable?  (mode 1777)

In particular, would it be worth the trouble to use setgid (_not_
setuid) executables to allow for updating ls-R files and fonts without
having them world-writable?  Or would that be gross overkill?  (Note
that just making the executables setgid is not desirable, some scheme
of aquiring and dropping permissions at the correct times has to be
implemented for this to work.)

[...]

> TeX can find the generated fonts even without them noted in the ls-R
> file. But to speed it up they can be in the ls-R file. For this reason
> there is a cronjob every day which updates the ls-R files.

Note that it is possible to create a texmf.cnf which ensures that
generated fonts not mentioned in the ls-R file _won't_ be found.  Just
use !! in the definition of VARTEXFONTS.

[...]

> The links exists:

> # ls -l /usr/lib/texmf/web2c/texmf.cnf 
> lrwxrwxrwx   1 root root   20 Jun 15 14:20 
> /usr/lib/texmf/web2c/texmf.cnf -> /etc/texmf/texmf.cnf

Incidentally, /etc/web2c/texmf.cnf might have been more appropriate.

-- 
Olaf Weber


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

Re: Bug#23576: tetex-base: no write-permissions on public font directories

[Olaf Weber]

Christoph Martin writes:

> A normal user could replace the file with a link to some other file
> say /vmlinuz or a file in another user homedir. Then if root or this
> other user  tries to write ls-R he/she would write to /vmlinuz or
> other files.

mktexupd checks for a magic string, and won't change ls-R files where
this is lacking.  A similar check can be added to mktexlsr, just in
case.

> BTW it is Debian policy to not have word-writable files.

Noted.

-- 
Olaf Weber


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

Re: Ian's solution [was: What hack in ld.so?]

[Olaf Weber]

Gordon Matzigkeit writes:

> Hi, all!
> There's been so much traffic on this thread, that I suspect most
> people have missed the fact that Ian Lance Taylor has analyzed and
> *solved* the problems with interaction between libtool and
> libc5-compat shared libraries.

By, as far as I can tell, breaking the ABI.

I suppose that an alternative hack would be not to take the DT_RPATH
as cast is stone, but subject it to some kind of rewriting if the
binary is found to use libc5.  For example, you could try to quietly
append "/libc5-compat" to every component, on the assumption that on a
libc6-based system, all libc5 binaries will be moved to such
locations.

Another good point that was raised is that some systems, like IRIX,
have environment variables that are used by rld (the run-time loader
on IRIX) to select a whole different root (_RLD_ROOT), or just to have
some directories searched before even DT_RPATH is checked (_RLD_PATH?
I'll have to check).

(Use of _RLD_ROOT, combined with the ability to extract a package
under an alternate root is precisely what is required to get several
incompatible packages to live together on a single system.)

That having been said, I do believe that to use -rpath to specify
system directories is a bad idea, if for no other reason than that it
prevents users from using LD_LIBRARY_PATH to customize their
environment.  Instead they have to rely on non-standard extensions.  I
do realise that on Linux, thanks to the ldconfig mechanism, the set of
system directories is rather fungible.  On IRIX for example, the
system directories for o32 binaries are /lib and /usr/lib, period.
The case for using -rpath is a lot more clear-cut on some systems than
on others.

-- 
Olaf Weber

Bug#886216: ITP: xymonq -- query-cli for Xymon

[Jonas Weber]

Package: wnpp
Severity: wishlist
Owner: Jonas Weber 

* Package name: xymonq
  Version : 0.7
  Upstream Author : Thomas Eckert 
* URL : http://www.it-eckert.com/software/xymonq/
* License : Permissive
  Programming Lang: Bash
  Description : query-cli for Xymon

Xymonq makes the monitoring data and configuration gathered
by the Xymon monitoring service available for use in shell scripts
and on the command line. Multiple filtering possibilities give
access to a vast amount of data in an easily usable format.

We use this software in production daily across a diverse set
of monitored hosts and monitoring setups. This package provides
additional filtering and querying methods on top of the underlying
Xymon client.

I plan to maintain this package in cooperation with upstream. For
the upload I'm needing a sponsor.

Bug#906065: ITP: postgrest -- Serve a RESTful API from any Postgres database

[Jonas Weber]

Package: wnpp
Severity: wishlist
Owner: Jonas Weber 

* Package name: postgrest
  Version : 5.0
  Upstream Author : Joe Nelson
* URL : https://postgrest.org/
* License : MIT
  Programming Lang: Haskell
  Description : Serve a RESTful API from any Postgres database

>From the webpage:

PostgREST is a standalone web server that turns your PostgreSQL database
directly into a RESTful API. The structural constraints and permissions
in the database determine the API endpoints and operations.

Using PostgREST is an alternative to manual CRUD programming. Custom API
servers suffer problems. Writing business logic often duplicates,
ignores or hobbles database structure. Object-relational mapping is a
leaky abstraction leading to slow imperative code. The PostgREST
philosophy establishes a single declarative source of truth: the data
itself.

I'll need a sponsor to upload the resulting packages to the
repositories.

Re: Replacing apt's http method (dropping curl)

[Bob Weber]

On 6/27/17 2:00 PM, Julian Andres Klode wrote:
> Hi everyone,
>
> as we discussed before in IRC, we plan to eventually replace
> our existing curl-based https method with our http method,
> by adding TLS support to it. This will move HTTPS support
> into apt proper, removing the apt-transport-https package.
>
> I'm not sure how long this will take, I hope we get something
> useful next month.
>
> Rationale
> =
> * The https method is split out of apt because curl has a lot
>   of dependencies (29 vs 7 on my test setup, 15.9 vs 4 MB of
>   disk space)
> * We want https to be a default these days, even if it provides
>   only minor security improvements.
> * Our http method is actually tested a lot because it is the
>   default and supports advanced features, the https method just
>   does curl easy stuff sequentially.
>
> Transition plan
> ===
> I plan to do this in two stages, both of which I expect to
> happen in unstable if all features have been implemented
> quickly. There might be feature-incomplete alphas in
> experimental.
>
> In the first stage, the "https" method is renamed to
> "https+curl", and a https->http symlink is added in apt.
>
> If no significant regressions are reported (we might drop
> some options or increase some checks), and the package has
> been in testing for some time, the apt-transport-https
> package is removed.
>
> This ensures that (a) we get proper testing and (b) users
> have a workaround if something fails in that testing period.
>
> Implementation
> ==
> I so far implemented basic https support using GnuTLS, including
> SNI and certificate validation, and one (!) local CA file (as our
> tests need that). The code is incredibly hacky right now. And
> https->http redirects don't work yet.
>
> Alternatives would be to use libnss or openssl. In the latter
> case, we'd have to build a separate helper binary that does not
> link to the GPLed code, and just unwraps a TLS connection into
> a pipe (similar to stunnel) - we could also use a helper generally,
> it would allow us to run the TLS stack as nobody (!!!) [OK,
> we have to open the socket in the parent process and pass it
> down to the TLS stack, so _apt opens the connection for firewalls].
>
> The existing shitty proof of concept is available on GitHub:
>
> https://github.com/Debian/apt/compare/master...julian-klode:feature/http-https?expand=1
>
> But as I said it's ugly. It also does not yet link the http
> binary to the https binary.
>
This may not be the place or time to ask this but will https  work with 
apt-cacher-ng?  Most caches just pass the data through them and can't store the
original files like apt-cacher-ng can.  Would the local machines connect to
ap-acacher-ng over http and apt-cacher-ng connect to the debian mirrors using
https?  Or could the apt-cacher-ng install generate a local certificate that the
local machines could be set to accept as a valid debian cache/mirror and have
apt-cacher-ng use https to the debian mirrors?


...Bob

Re: Bug#812885: general: Bluetooth doesn't work

[Bob Weber]

On 01/27/2016 10:49 AM, justysia wrote:
> Package: general
> Severity: normal
>
> Dear Maintainer,
>
> Hello!
>   I was trying to make bluetooth work properly,
> but I couldn't find a way to do it.
> So I hope You will help me, plese.
> this appears when system starts up:
> [12.695075] bluetooth hci0: firmware: failed to load 
> brcm/BCM43142A0-4ca-2009.hcd (-2)
> Please help me fix it.
> Best regards,
> Justysia
>
> -- System Information:
> Debian Release: 8.3
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
The real file seems to be BCM43142A0-04ca-2009.hcd (note the 0 -zero before
4ca).  On page
http://askubuntu.com/questions/599893/bluetooth-is-not-working-on-14-04-with-bcm43142
there seems to be a solution but I dont have that  bt adapter so I cannot
confirm that it will work for you.  I have another Broadcom  (BCM20702A0)
adapter that I used a similar fix to get its firmware to load.  Basically you
download fw-04ca_2009.hcd and rename it to
/lib/firmware/brcm/BCM43142A0-04ca-2009.hcd.  You might have to create the
directory firmware and brcm if they dont exist on your system.  If you run lsusb
you should see an ID 04ca-2009 listed.  If not then this wont help you.

...bob

Bug#872380: ITP: pocket-home -- a simple menu for mobile devices

[Stephen Paul Weber]

Package: wnpp
Severity: wishlist

After discussions at Debconf17, it was suggested that I should package for 
Debian the pocket-home program that forms the lightweight home menu of the 
pocketCHIP device.  It is GPL3+ and the most maintained upstream is 
.


This package is already useful on the pocketCHIP (which runs Debian) but 
would be useful on other low-power, low-resolution, touch-friendly devices 
as well.


It is my intention not only to maintain this package, but also to work with 
upstream on improvements as they are discovered to make this program more 
useful on other target devices.


signature.asc
Description: PGP signature