From: Gisle Vanem <gisle.vanem@gmail.com>
To: location@lists.ipfire.org
Subject: Re: Problem in urllib?
Date: Tue, 30 Mar 2021 13:14:12 +0200 [thread overview]
Message-ID: <b165b5f5-e033-b2ea-e589-2347598f9682@gmail.com> (raw)
In-Reply-To: <D8E53F36-B32A-4990-9FB7-3358D9730562@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]
Michael Tremer wrote:
> Please just update to the 0.9.5 release and this problem will be fixed.
I seems to have that; git describe --tags
0.9.5-9-g1814283
It was only that the '0.9.4' was a left-over in my
build. What specific change after 0.9.4 did fix this?
But rebuilding such that 'User-agent: location/0.9.5',
and a little path to 'python/database.c', it seems to
work better:
...
HTTP Response: 200
Headers:
date: Tue, 30 Mar 2021 10:52:03 GMT
last-modified: Tue, 30 Mar 2021 05:06:07 GMT
etag: "425158-5beb9f4bc1867"
accept-ranges: bytes
content-length: 4346200
x-content-type-options: nosniff
x-frame-options: deny
referrer-policy: strict-origin
x-xss-protection: 1; mode=block
content-type: application/x-xz
strict-transport-security: max-age=31536000; includeSubDomains; preload
connection: close
Downloaded new database from Tue, 30 Mar 2021 05:04:14 GMT
Traceback (most recent call last):
File "f:\ProgramFiler\Python36\lib\shutil.py", line 544, in move
os.rename(src, real_dst)
FileExistsError: [WinError 183] Kan ikke opprette en fil når
filen allerede finnes: 'f:\\gv\\VC_project\\ws_trace\\tmp82
8kmqif' -> 'f:\\gv\\VC_project\\ws_trace\\IPFire-database.db'
-----------
Some issue with shutil when overwriting/renaming an existing
.db-file. But updating w/o a .db-file works fine.
PS. it would be nice that 'location.py --debug' would honour
the setting of 'LOC_LOG'. w/o this it's very hard to see
what goes on in the Python module.
next prev parent reply other threads:[~2021-03-30 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 9:08 Gisle Vanem
2021-03-30 9:27 ` Michael Tremer
2021-03-30 11:14 ` Gisle Vanem [this message]
2021-04-01 10:09 ` Michael Tremer
2021-04-01 11:06 ` Gisle Vanem
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b165b5f5-e033-b2ea-e589-2347598f9682@gmail.com \
--to=gisle.vanem@gmail.com \
--cc=location@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox