[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#133334: marked as done (Useful HTML Links From update_excuses.html)

Your message dated Sat, 14 May 2011 01:36:12 +0200
with message-id <20110513233612.GA32222@radis.liafa.jussieu.fr>
and subject line Re: Bug#133334: Useful HTML Links From update_excuses.html
has caused the Debian Bug report #133334,
regarding Useful HTML Links From update_excuses.html
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
133334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=133334
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ftp.debian.org
Version: N/A
Severity: wishlist

Apologies if this isn't the correct package to file this request
against.

Since update_excuses.html is in HTML format already, adding some links
from it to the outside world would be helpful...

1. Add a link from the package name to the package page on
packages.debian.org.  For example, for aptitude, have it link to:
	http://packages.debian.org/aptitude
or whatever it redirects to from there.

2. Whenever it says a package "is buggy!", link to the bugs.debian.org
Web page, either:
	http://bugs.debian.org/aptitude
or, even better, something like:
	http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=pkg&data=aptitude&archive=no&sev-inc=critical&sev-inc=grave&sev-inc=serious
which would take you to the exact N bugs (in aptitude's case, one)
that's keeping it out of testing.

3. Whenever there are "unsatisfiable Depends:", link to the anchor tag
for the package that's causing the problem.  For example, looking at
bibletime, it has one:
	* bibletime/i386 unsatisfiable Depends: libsword1 (>= 1.5.2-9) ['sword']
Part of that line should be a link down to the excuses for sword to see
why it, in turn, isn't ready for inclusion (in this case, because it's
too new and out of date on arm and m68k).

We're left to surmise for ourselves that the version of libsword1
currently in testing (in this case, 1.5.2-7) doesn't match the version
requirement of bibletime (>= 1.5.2-9).  Perhaps a link to an appropriate
page on packages.debian.org is in order.

Item #3 is more a brainstorm than a real request.  I've wished for #1
and #2 at various times, though, so I'd love to see them included in the
near future.  I hope I've whetted your collective appetite for doing
something useful with HTML links, so maybe there are other, even better
things to include as well.

Jason B.

-- 
Kindness has converted more sinners than zeal, eloquence, or learning.
	-- Frederick W. Faber, British theologian

--- End Message ---
--- Begin Message --- 
On Mon, Feb 11, 2002 at 00:42:07 -0600, Jason Bucata wrote:

> Apologies if this isn't the correct package to file this request
> against.
> 
> Since update_excuses.html is in HTML format already, adding some links
> from it to the outside world would be helpful...
> 
> 1. Add a link from the package name to the package page on
> packages.debian.org.  For example, for aptitude, have it link to:
> 	http://packages.debian.org/aptitude
> or whatever it redirects to from there.
> 
packages.qa.d.o/$pkg might make more sense.

> 2. Whenever it says a package "is buggy!", link to the bugs.debian.org
> Web page, either:
> 	http://bugs.debian.org/aptitude
> or, even better, something like:
> 	http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=pkg&data=aptitude&archive=no&sev-inc=critical&sev-inc=grave&sev-inc=serious
> which would take you to the exact N bugs (in aptitude's case, one)
> that's keeping it out of testing.
> 
That's done, afaik.

> 3. Whenever there are "unsatisfiable Depends:", link to the anchor tag
> for the package that's causing the problem.  For example, looking at
> bibletime, it has one:
> 	* bibletime/i386 unsatisfiable Depends: libsword1 (>= 1.5.2-9) ['sword']
> Part of that line should be a link down to the excuses for sword to see
> why it, in turn, isn't ready for inclusion (in this case, because it's
> too new and out of date on arm and m68k).
> 
> We're left to surmise for ourselves that the version of libsword1
> currently in testing (in this case, 1.5.2-7) doesn't match the version
> requirement of bibletime (>= 1.5.2-9).  Perhaps a link to an appropriate
> page on packages.debian.org is in order.
> 
This message usually means that the package isn't in unstable either, so
that's not even possible.

Anyway, since nobody has been bothered to reply to this bug in 9 years
it doesn't seem to do much good to keep it open.  Closing.

Cheers,
Julien

--- End Message ---
Reply to: