Your message dated Mon, 7 Jan 2008 12:16:48 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Fixed
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
Paul Wise <[EMAIL PROTECTED]> writes:
> lintian.debian.org replaces dashes in source package names with
> underscores. The PTS should do the same so that links to
> lintian.debian.org work properly. An example package:
>
> http://packages.qa.debian.org/c/chromium-data.html
> http://lintian.debian.
lintian.debian.org replaces dashes in source package names with
underscores. The PTS should do the same so that links to
lintian.debian.org work properly. An example package:
http://packages.qa.debian.org/c/chromium-data.html
http://lintian.debian.org/reports/maintainer/[EMAIL PROTECTED]
http://li
retitle 373218 naming convention for lintian URLs is not in sync with
lintian.d.o
thanks
With the new lintian.d.o naming convention [1], this bug should be way
better now, since now URLs are email based and way less characters that
need escaping are present there.
Instead of closing the bug howe
webvinz . com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I'm not wholly adverse to this approach, but there's a lot of stuff that
links to lintian maintainer pages and I'm not particularly thrilled with
the idea of changing those URLs.
I also made the changes to the other pages I could find linking to the
lintian pages.
Why not just fix the qa code
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Fri, 29 Jun 2007, Russ Allbery wrote:
>> According to RFC 2396, the list of characters reserved, banned, or
>> disrecommended for URIs are:
>>
>> ; / ? : @ & = + $ , < > # % " { } | \ ^ [ ] `
>>
>> and space. The safest thing to do would be t
On Fri, 29 Jun 2007, Russ Allbery wrote:
> According to RFC 2396, the list of characters reserved, banned, or
> disrecommended for URIs are:
>
> ; / ? : @ & = + $ , < > # % " { } | \ ^ [ ] `
>
> and space. The safest thing to do would be to map all of those characters
> to _. (Some of them
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Thu, 28 Jun 2007, Russ Allbery wrote:
>> Well, he extracts everything between <>, but I believe we still lose
>> if, for instance, there's a # in the e-mail address (which is an
>> entirely valid RFC 2822 character). I'm a little worried about +,
>
On Thu, 28 Jun 2007, Russ Allbery wrote:
> Well, he extracts everything between <>, but I believe we still lose if,
> for instance, there's a # in the e-mail address (which is an entirely
> valid RFC 2822 character). I'm a little worried about +, which is a very
> common character and sometimes ha
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Thu, 28 Jun 2007, Russ Allbery wrote:
>> You can't drop that tr///. It's what takes care of all the special
>> characters that otherwise need escaping.
> Since he extracts the email part, it's less of a problem.
Well, he extracts everything betwe
On Thu, 28 Jun 2007, Russ Allbery wrote:
> > --- orig/html_reports 2007-06-28 12:33:42.0 -0500
> > +++ new/html_reports2007-06-28 12:14:58.0 -0500
> > @@ -480,11 +480,7 @@
>
> > my $file = $maint;
> > if ($file) {
> > - $file =~ s/^(.+)\<.*$/$1/;
> > -
Raphael Geissert <[EMAIL PROTECTED]> writes:
> Package: qa.debian.org
> Tags: patch
> Followup-For: Bug #373218
> I just wrote a patch for this problem. The best solution I found it to
> drop the current naming convention of the lintian reports and use the
> maintainer
Package: qa.debian.org
Tags: patch
Followup-For: Bug #373218
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just wrote a patch for this problem.
The best solution I found it to drop the current naming convention of the
lintian reports and use the
maintainer login (the same way most of the
Hi again
as I have some time, I wanted to create patch for this issue. However
I'm don't know XSL which is being used for generating PTS page. Fixing
for some more names can be done by adding selected special chars to
replace string, but this will again sometimes end on some name with
different sp
Hi,
sorry for closing this I mixed this exactly because there is
a working link on your developer page :)
I looked into the PTS page and the site which includes
Lintian is just a .xsl file. On ddpo php is used to encode
the url and strip these %xx character from the url.
Is there any way to get
reopen 373218
thanks
Hi
this issue IMHO still exists. On PTS[1] there is link to page with all
accents[2] which does not exist, while on DDPO[3] Lintian link points
to existing page[4].
[1]:http://packages.qa.debian.org/m/mpdscribble.html
[2]:http://lintian.debian.org/reports/mMichal_%C4%8Ciha%C
Processing commands for [EMAIL PROTECTED]:
> reopen 373218
Bug#373218: PTS: wrong link to lintian page
Bug reopened, originator not changed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debia
Your message dated Tue, 24 Apr 2007 17:59:21 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing 373218
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 r
Package: qa.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
link to lintian page is broken for non-ascii names. This is simmilar to
bug #349712 which has been fixed by fixing one special char.
My lintian link leads to
http://lintian.debian.org/reports/mMichal_%C4%8C
20 matches
Mail list logo
