Your message dated Mon, 13 Nov 2006 14:17:32 +0100
with message-id <[EMAIL PROTECTED]>
and subject line alexandria: Pulling information from internet sources does not
work at all
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)
--- Begin Message ---
Package: alexandria
Version: 0.5.1-3
Severity: serious
alexandria in sarge seems to be non-usable. - I have done the usual
steps a beginner would do:
1. start the program
2. klick [Add Book]
3. Type in ISIN 3-446-15497-3
4. klick on [+Add]
5. Get error message: "No results were found. Make sure your search
criterion is spelled correctly. and try again.
I already *have* followed the advice in bug #328496 and have added the
new developer token. And amazon seems to accept it - from strace
output:
5548 write(21, "GET
/onca/xml3?t=calibanorg-20&AsinSearch=3446154973&f=xml&type=heavy&dev-t=142TF8CHT48WYPPS6J82&locale=de
HTTP/1.1\r\nAccept: */*\r\nUser-Agent: Ruby/Amazon 0.9.0\r\nHost:
xml.amazon.com\r\n\r\n", 185) = 185
[...]
5548 write(21, "GET
/onca/xml3?t=calibanorg-20&AsinSearch=3446154973&f=xml&type=heavy&dev-t=142TF8CHT48WYPPS6J82&locale=de
HTTP/1.1\r\nAccept: */*\r\nUser-Agent: Ruby/Amazon 0.9.0\r\nHost:
xml.amazon.com\r\n\r\n", 185) = 185
And indeed checking
http.//xml.amazon.com/onca/xml3?t=calibanorg-20&AsinSearch=3446154973&f=xml&type
=heavy&dev-t=142TF8CHT48WYPPS6J82&locale=de
in e.g. mozilla shows that amazon would provide the correct data:
| <pRODUCTinfo
xsi:noNamespaceSchemaLocation="http://xml.amazon.com/schemas3/dev-heavy.xsd";>
| -
| <Request>
| -
| <Args>
| <Arg value="de" name="locale"/>
| <Arg value="Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20060926
Debian/1.7.8-1sarge7.3.1" name="UserAgent"/>
| <Arg value="0W9BYZ03S8XCJNCHJEY1" name="RequestID"/>
| <Arg value="142TF8CHT48WYPPS6J82" name="dev-t"/>
| <Arg value="3446154973" name="AsinSearch"/>
| <Arg value="heavy" name="type"/>
| <Arg value="xml" name="f"/>
| <Arg value="calibanorg-20" name="t"/>
| </Args>
| </Request>
| -
| <Details
url="http://www.amazon.de/gp/product/3446154973%3ftag=calibanorg-20%26link_code=xm2%26camp=2025%26dev-t=142TF8CHT48WYPPS6J82";>
| <Asin>3446154973</Asin>
| -
| <ProductName>
| Programmieren in C. ANSI C (2. A.). Mit dem C-Reference Manual.
| </ProductName>
I assume the alexandria 0.6.1-1 in upcoming etch is functional
currently, please doublecheck and make a versioned close if this is
the case.
cu and- tellico doesn't work, too. ;-) -reas
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-k7
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Versions of packages alexandria depends on:
ii gconf2 2.8.1-6 GNOME configuration database syste
ii libamazon-ruby 0.9.0-1 a Ruby library for programmatic ac
ii libgconf2-ruby 0.12.0-2 GConf 2 bindings for the Ruby lang
ii libgettext-ruby1.8 0.8.0-1 Gettext for ruby1.8
ii libglade2-ruby 0.12.0-2 Libglade 2 bindings for the Ruby l
ii libgnome2-ruby 0.12.0-2 GNOME 2 bindings for the Ruby lang
ii libruby1.8 [libyaml-ruby1. 1.8.2-7sarge4 Libraries necessary to run Ruby 1.
ii ruby1.8 1.8.2-7sarge4 Interpreter of object-oriented scr
-- no debconf information
--
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken. (c) Jasper Ffforde
--- End Message ---
--- Begin Message ---
Version: 0.6.1-1
Hi,
> alexandria in sarge seems to be non-usable. - I have done the usual
> steps a beginner would do:
[...]
> I assume the alexandria 0.6.1-1 in upcoming etch is functional
> currently, please doublecheck and make a versioned close if this is
> the case.
I double checked, works fine, and "djpig" also confirms it ("Probably
sarge only, seems to work fine in etch"). I think it's safe to close
with the etch version.
I'm not sure if sarge is fixable, that's up to the maintainer and the
stable release team to find out. Thanks for reporting.
Thijs
signature.asc
Description: This is a digitally signed message part
--- End Message ---
