Re: recent l10n changes produce huge tidy/validate output

2003-09-12 Thread Martin Quinson 
On Thu, Sep 11, 2003 at 05:52:13PM +0200, Martin Quinson wrote:
> On Thu, Sep 11, 2003 at 10:56:28AM +0200, Gerfried Fuchs wrote:
> > Hi!
> > 
> >  Something did go wrong with the recent changs to the l10n pages. They
> > produce tons of output in the tidy/validate analyses[1]. From what I can
> > see it is because unescaped translator names that are taken 1:1 into the
> > corresponding pages.
> > 
> >  Can someone with enough l10n/i18n knowledge fix that? Would be really
> > nice, thanks.
> > 
> >  So long,
> > Alfie
> > [1] http://www-master.debian.org/~barbier/tidy/ and s/tidy/validate/
> 
> Yup, we're on it.

Ok, Denis did commit the change from Tomohiro in
intl/l10n/scripts/transmonitor-check, so the issue will be solved. But,
Denis, you forgot to remove the offending parts of the DB, so that those
packages are rescaned.

It looks like there is another problem on those web pages, since they where
not built yesterday. It matches my lastest commit to ease the navigation
about errors in template files...

Where are the build log, again, so that I can check my stupidity of the day?

Sorry, Mt.

-- 
Dans un pays d'extrême droite, On se torche avec les doigts, 
Y'a plus de journaux pour ça.
   -- Frères misère

Re: recent l10n changes produce huge tidy/validate output

2003-09-12 Thread Martin Quinson 
On Fri, Sep 12, 2003 at 08:45:57AM +0200, Martin Quinson wrote:
> But, Denis, you forgot to remove the offending parts of the DB, so that
> those packages are rescaned.

Forget it. Of course you did not miss that point. I did not check well...

Sorry, Mt.

-- 
Ian Fleming was a UNIX fan! How do I know? 
Well, James Bond had the (license to kill) number 007,
i.e., he could execute anyone!

Re: recent l10n changes produce huge tidy/validate output

2003-09-12 Thread Denis Barbier 
On Fri, Sep 12, 2003 at 09:10:26AM +0200, Martin Quinson wrote:
> On Fri, Sep 12, 2003 at 08:45:57AM +0200, Martin Quinson wrote:
> > But, Denis, you forgot to remove the offending parts of the DB, so that
> > those packages are rescaned.
> 
> Forget it. Of course you did not miss that point. I did not check well...

Right ;)
Pages are not fixed yet, the DB file is copied daily on www-master.d.o
at 12:49 UTC, and next build should begin at 13:24 UTC, but validation
report pages will be updated only around 23:00 UTC.

Build logs are available at
  http://www-master.debian.org/build-logs/
and linked from
  http://www.debian.org/devel/website/desc

Denis

Re: recent l10n changes produce huge tidy/validate output

2003-09-12 Thread Gerfried Fuchs 
* Martin Quinson <[EMAIL PROTECTED]> [2003-09-12 08:45]:
> Where are the build log, again, so that I can check my stupidity of the day?

 If you haven't found them yet, they are linked from the
/devel/website/desc page (easier to remember :) and are here:
, especially
 might be
what you are looking for.

 So long,
Alfie
-- 
"I feel more alive dead then when I was alive"
  -- Clawfinger, "Catch Me"


pgp4TrGyiI5ep.pgp
Description: PGP signature

Re: recent l10n changes produce huge tidy/validate output

2003-09-12 Thread Denis Barbier 
On Fri, Sep 12, 2003 at 08:45:57AM +0200, Martin Quinson wrote:
[...]
> It looks like there is another problem on those web pages, since they where
> not built yesterday. It matches my lastest commit to ease the navigation
> about errors in template files...

Looks like they have been built now,
  http://www.debian.org/intl/l10n/templates/fr
has links to errors found in templates.

Denis

Re: recent l10n changes produce huge tidy/validate output

2003-09-12 Thread Martin Quinson 
On Fri, Sep 12, 2003 at 10:29:01AM +0200, Denis Barbier wrote:
> On Fri, Sep 12, 2003 at 08:45:57AM +0200, Martin Quinson wrote:
> [...]
> > It looks like there is another problem on those web pages, since they where
> > not built yesterday. It matches my lastest commit to ease the navigation
> > about errors in template files...
> 
> Looks like they have been built now,
>   http://www.debian.org/intl/l10n/templates/fr
> has links to errors found in templates.

Yuhu ! I make a red sign in my calendar: I managed to change those scripts
without breaking anything at least once in my life ;)

Only a small Use of uninitialized value in concatenation (.) or string at
../../../../english/international/l10n/scripts/gen-files.pl line 114.

Sorry for the noise, Mt.

-- 
Each language has its purpose, however humble.  Each language expresses the
Yin and Yang of software.  Each language has its place within the Tao.
But do not program in COBOL if you can avoid it.
  -- The Tao of programming

★お得情報メールマガジン★

2003-09-12 Thread お得情報メルマガ 
[EMAIL PROTECTED]
□━□
【重要】このメールは規定通りに登録されているメールアドレスへ送信している
メルマガです。登録されているアドレスについては、下の方をご覧ください。
※購読解除　⇒　http://banner.peeps.jp/
　このメールに返信しても解除されませんのでご注意下さい。
□━□


[EMAIL PROTECTED]

【アダルトキャンディー】
　☆風俗店超格安ホームページ製作☆　

┌──　〜特徴〜
│ 1.オリジナルドメイン取得(お好きな名前.comなど)
│ 2.完全携帯対応ホームページ製作
│ 3.更新はお客様が簡単に出来ます
│ 4.ＴＯＰページにオリジナルフラッシュ設置
│ 5.携帯対応掲示板設置　
│ 6.スペース50メガ
│ 7.プロフィール機能
│ 　(※写真・出勤状況をタイムリーに更新可能！)
│ 　　その多数のサービス
└─

以上のサービスを業界最安値にてご提供いたします。
あなたの周りにＰＣをお持ちの方が何人いらっしゃいますか？
携帯対応なら全員がＨＰにアクセスできます!!

女の子の写真やプロフィール、出勤情報等をタイムリーに更新可能です
毎日の更新業務はタイムリーでないとお客様は集まりません！

金額は絶対に他社では真似できません♪

風俗店に現在、ホームページとドメインは必須です。
プロバイダーのＵＲＬだと信憑性にかけますよね…
売り上げ・集客・信用をこの期にアップしてみませんか？


　　※販売店･代理店も募集しております

□当HPにて詳細を!!(携帯OK)
■■■今や風俗店も独自のドメインでＨＰはあたりまえですよ♪■■■
　　　http://adult.peeps.jp/



∞∞
【メール登録について】
当マガジンは、以下のメールアドレスが登録されております
①メルマガ投稿のあった方（一括投稿サイト経由も含む）
②購読登録フォームより、ご自分で登録をした方
③上記に覚えの無い方は、第三者によるイタズラが考えられます。
　（お手数ですが、下記より解除してください。）

購読登録の確認メールは送信されません。
それで「登録した覚えが無い」と勘違いされる方が時々居られます。
ご理解の程よろしくお願い致しますm(_ _)m

http://banner.peeps.jp/

Bug#195105: marked as done (packages.debian.org: search_packages: search is (temporarily) broken)

2003-09-12 Thread Debian Bug Tracking System 
Your message dated Fri, 12 Sep 2003 17:15:34 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Will close it because unreproducible
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--
Received: (at submit) by bugs.debian.org; 28 May 2003 19:01:15 +
>From [EMAIL PROTECTED] Wed May 28 14:01:14 2003
Return-path: <[EMAIL PROTECTED]>
Received: from morimoto.progeny.com [216.37.46.163] 
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19L6Ak-0004Pl-00; Wed, 28 May 2003 14:01:14 -0500
Received: from albus.progeny.com (albus.progeny.com [192.168.1.14])
by morimoto.progeny.com (Postfix) with ESMTP
id C7CC4636A6; Wed, 28 May 2003 14:01:10 -0500 (EST)
Received: by albus.progeny.com (Postfix, from userid 10018)
id 88D4D18145; Wed, 28 May 2003 14:01:10 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "John R. Daily" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: packages.d.o: Search is broken
X-Mailer: reportbug 2.10.1
Date: Wed, 28 May 2003 14:01:10 -0500
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-6.0 required=4.0
tests=BAYES_01,HAS_PACKAGE
version=2.53-bugs.debian.org_2003_05_24
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_05_24 
(1.174.2.15-2003-03-30-exp)

Package: www.debian.org
Version: unavailable; reported 2003-05-28
Severity: important

When running searches on packages names, or using the URL shortcut
http://packages.debian.org/foo, I'm currently seeing:

Malformed query! (Or something strange happened to this script.)

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux albus.progeny.com 2.4.18-686 #1 Sun Apr 14 11:32:47 EST 2002 i686
Locale: LANG=en_US, LC_CTYPE=en_US


---
Received: (at 195105-done) by bugs.debian.org; 12 Sep 2003 15:12:09 +
>From [EMAIL PROTECTED] Fri Sep 12 10:07:00 2003
Return-path: <[EMAIL PROTECTED]>
Received: from sorgfalt.net (mail.sorgfalt.net) [217.160.169.191] 
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19xpVg-00088N-00; Fri, 12 Sep 2003 10:06:56 -0500
Received: from fphfslinux.physik.uni-karlsruhe.de ([129.13.104.109] 
helo=djpigpb)
by mail.sorgfalt.net with asmtp (Exim 3.35)
id 19xpVf-0003Nt-00
for <[EMAIL PROTECTED]>; Fri, 12 Sep 2003 17:06:55 +0200
Received: from djpig by djpigpb with local (Exim 3.36 #1 (Debian))
id 19xpe2-sp-00
for <[EMAIL PROTECTED]>; Fri, 12 Sep 2003 17:15:34 +0200
Date: Fri, 12 Sep 2003 17:15:34 +0200
To: [EMAIL PROTECTED]
Subject: Will close it because unreproducible
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
From: Frank Lichtenheld <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=0.0 required=4.0
tests=none
version=2.53-bugs.debian.org_2003_8_27
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_8_27 
(1.174.2.15-2003-03-30-exp)

Hi.

I close this bug as it seems to have happend only once and is completly
unreproducible now.

If you disagree or have encountered similar problems since then, please
object. Will reopen it then.

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/

Bug#208513: Found the cause of the problem

2003-09-12 Thread Frank Lichtenheld 
tags 208513 pending
thanks

Hi.

Regarding the bug, that
http://packages.debian.org/stable/devel/gcc-2.95.html
shows a "Source not found" message despite the fact that there is of
course the source code available:

The problem seems to be that the current scripts doesn't handle a
versioned Source: well
(Source: gcc-2.95 (2.95.4.ds13-11woody1))

Will be fixed in my new version of the scripts (yes, it is coming finally)

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/

Processed: Found the cause of the problem

2003-09-12 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

> tags 208513 pending
Bug#208513: gcc 2.95.4 source has disappeared
There were no tags set.
Tags added: pending

> thanks
Stopping processing here.

Please contact me if you need assistance.

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

Some (layout) improvements for devel/wnpp/index

2003-09-12 Thread Frank Lichtenheld 
Hi.

I just read devel/wnpp/index and found it somewhat confusing.
I prepared a patch that adds a toc and makes some layout
changes.

Objections? (Yeah, I know this looks lika a pain for translators but I
can commit as much as possible for each translation so they
have only to add the toc part.)

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/
Index: index.wml
===
RCS file: /cvs/webwml/webwml/english/devel/wnpp/index.wml,v
retrieving revision 1.20
diff -u -r1.20 index.wml
--- index.wml   24 Apr 2003 10:25:46 -  1.20
+++ index.wml   12 Sep 2003 18:26:27 -
@@ -1,13 +1,16 @@
 #use wml::debian::template title="Work-Needing and Prospective Packages"
+#use wml::debian::toc
 # $Id: index.wml,v 1.20 2003/04/24 10:25:46 kraai Exp $
 
+%body
+
 Work-Needing and Prospective Packages, WNPP for short, is a list 
 of packages in need of new maintainers and prospective packages in Debian.
 In order to closely track the real status of such things, WNPP is currently
 operated as a pseudo-package in the http://bugs.debian.org/";>Debian
 Bug Tracking System (BTS).
 
-
+
 
 Packages in need of a new maintainer:
 
@@ -29,7 +32,11 @@
 please check the http://bugs.debian.org/wnpp";>wnpp pseudo package
 entry in the BTS.
 
-
+
+
+Using WNPP
+
+
 
 Since it uses the BTS, every developer is already familiar with the
 technical details, such as submission of new information, modification of
@@ -43,12 +50,15 @@
 only submit one bug per source package rather than one bug for each
 binary package built from a source package.
 
+
+Adding new entries with "reportbug"
+
 You can use http://packages.debian.org/reportbug";>reportbug
-(apt-get install reportbug):
+(apt-get install reportbug):
 
 
-  $ reportbug --email [EMAIL PROTECTED] wnpp
-  Using 'Your Name <[EMAIL PROTECTED]>' as your from address.
+  $ reportbug --email [EMAIL PROTECTED] wnpp
+  Using 'Your Name <[EMAIL PROTECTED]>' as your from 
address.
   Getting status for wnpp...
   Querying Debian bug tracking system for reports on wnpp
   (Use ? for help at prompts.)
@@ -85,8 +95,8 @@
 After your selection you will be asked for the package name:
 
 
-Choose the request type: x
-Please enter the proposed package name: PACKAGENAME
+Choose the request type: x
+Please enter the proposed package name: PACKAGENAME
 Checking status database...
 
 
@@ -97,19 +107,19 @@
 
 Please briefly describe this package; this should be an appropriate short
 description for the eventual package:
-> A DESCRIPTION
+> A DESCRIPTION
 
-Subject: ITP: PACKAGENAME -- A DESCRIPTION
+Subject: ITP: PACKAGENAME -- A DESCRIPTION
 Package: wnpp
 Version: N/A; reported 2002-01-30
 Severity: wishlist
 
-* Package name: PACKAGENAME
-  Version : x.y.z
-  Upstream Author : Name <[EMAIL PROTECTED]>
-* URL : http://www.some.org/
-* License : (GPL, LGPL, BSD, MIT/X, etc.)
-  Description : A DESCRIPTION
+* Package name: PACKAGENAME
+  Version : x.y.z
+  Upstream Author : Name <[EMAIL PROTECTED]>
+* URL : http://www.some.org/
+* License : (GPL, LGPL, BSD, MIT/X, etc.)
+  Description : A DESCRIPTION
 
 
 -- System Information
@@ -123,11 +133,11 @@
 of the package.
 
 
-Choose the request type: x
-Please enter the name of the package: PACKAGENAME
+Choose the request type: x
+Please enter the name of the package: PACKAGENAME
 Checking status database...
 
-Subject: O: PACKAGENAME -- SHORT DESCRIPTION
+Subject: O: PACKAGENAME -- SHORT DESCRIPTION
 Package: wnpp
 Version: N/A; reported 2002-01-30
 Severity: normal
@@ -150,20 +160,23 @@
 Submit this bug report (e to edit) [Y|n|i|e|?]? 
 
 
+
+Adding new entries via email
+
 It is also possible to report reports/bugs against the WNPP via email.
 The format of the submission should be like this:
 
 
   To: [EMAIL PROTECTED]
-  Subject: :  -- 
+  Subject: TAG: package name -- short package 
description
   
   Package: wnpp
-  Severity: 
+  Severity: see below
   
-  < Some information about the package.  If this is an ITP or RFP an URL
+  Some information about the package.  (If this is an ITP or RFP an 
URL
   where the package (either the .deb or the original source) can be downloaded
   from is required, as well as
-  information concerning its license. >
+  information concerning its license.)
 
 
 The tags to be used and their corresponding severities are:
@@ -205,6 +218,9 @@
 
 
 
+
+Removing entries
+
 The procedures for closing these bugs are as follows:
 
 
@@ -263,7 +279,7 @@
 If you feel that the developers' mailing list should know about your ITP,
 RFA or anything else, add the header
 X-Debbugs-CC: debian-devel@lists.debian.org
-to the message (note: that's a real header, not a pseudo-header).
+to the message (note: that's a real header, not a pseudo-header).
 
 Of course, the easiest way of closing these bugs is to include an entry
 in

wnpp and bug owners

2003-09-12 Thread Colin Watson 
So, we've now got bug ownership in the BTS, and it occurs that we could
use this productively to improve the way wnpp bugs are managed. Up to
now, when people "accept" an RFP or an RFA/O by retitling it to an ITP
or an ITA respectively, sometimes they change the submitter address and
sometimes they don't. Changing the submitter address has the
disadvantage that the original submitter never gets notified when the
new package is uploaded, and both have the disadvantage that the
prospective maintainer doesn't receive mails sent to the wnpp bug.

Bug ownership should solve this problem: people ITPing and ITAing
reports should set themselves as the owner of the bug, which is the same
as saying that they're taking responsibility for fixing it, and means
that they'll get mail about the bug. (Please do NOT set yourself as a
bug owner just to get this subscription property! We'll provide a
facility for that fairly soon.)

I'd like to commit the following patch to /devel/wnpp/. Any comments?

Index: index.wml
===
RCS file: /cvs/webwml/webwml/english/devel/wnpp/index.wml,v
retrieving revision 1.20
diff -p -u -r1.20 index.wml
--- index.wml   24 Apr 2003 10:25:46 -  1.20
+++ index.wml   12 Sep 2003 22:32:07 -
@@ -213,7 +213,8 @@ The format of the submission should be l
   If you are going to adopt a package, retitle its bug
   to replace `O' with `ITA', in order for other people to know the
   package is being adopted and to prevent its automatic removal from the
-  archive. To actually adopt the package, upload it with your name in
+  archive, and set yourself as the owner of the bug.
+  To actually adopt the package, upload it with your name in
   its Maintainer: field, and put something like
   
   * New maintainer (Closes: #bugnumber)
@@ -232,7 +233,8 @@ The format of the submission should be l
   If you are going to adopt a package, retitle its bug
   to replace `RFA' with `ITA', in order for other people to know the
   package is being adopted and to prevent its automatic removal from the
-  archive. To actually adopt the package, upload it with your name in
+  archive, and set yourself as the owner of the bug.
+  To actually adopt the package, upload it with your name in
   its Maintainer: field, and close this bug once the package has been
   installed.
 
@@ -254,8 +256,9 @@ The format of the submission should be l
   RFP
   If you are going to package this, retitle the bug report
   to replace `RFP' with `ITP', in order for other people to know the
-  program is already being packaged. Then package the software, upload
-  it and close this bug once the package has been installed.
+  program is already being packaged, and set yourself as the owner of
+  the bug. Then package the software, upload it and close this bug once
+  the package has been installed.
   
 
 
@@ -270,8 +273,9 @@ in the package changelog saying what you
 (closes: bug#n) to it. This way the bug will be closed
 automatically after the new package gets installed into the archive.
 
-Attention: You can not reassign or
-retitle bug reports by mailing the report number @bugs.debian.org,
+Attention: You can not reassign,
+retitle, or set the owner of bug reports by mailing the report number
[EMAIL PROTECTED],
 nor by filing new reports. You have to send an appropriate
 message to the BTS control bot — 
 read the instructions for it!

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]