#8760 closed task (fixed)
Fix pysqlite link
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11.6 |
| Component: | general | Version: | none |
| Severity: | normal | Keywords: | documentation |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
pysqlite is now hosted at Google Code. The link in TracInstall needs to be updated:
OLD: pysqlite.org NEW: pysqlite.googlecode.com
Attachments (0)
Change History (9)
comment:1 by , 15 years ago
| Milestone: | → 0.11.6 |
|---|---|
| Owner: | set to |
| Status: | new → assigned |
comment:2 by , 15 years ago
I just sent you a mail. In case it doesn't reach you, please give me a current email address of you.
follow-up: 4 comment:3 by , 15 years ago
There's probably no way to just export all the tickets as static HTML, right? That would be easier than hosting a new Trac instance …
follow-up: 5 comment:4 by , 15 years ago
Replying to gh@…:
There's probably no way to just export all the tickets as static HTML, right? That would be easier than hosting a new Trac instance …
Yep, that's an alternative.
I'd like to get the feedback from Remy and Jonas on this, what they'd prefer (or simply do nothing if they find it's a weird idea of mine…).
Hint: with such a read-only "hidden" Trac instance, we could play a bit with recent versions of Trac on t.e.o and the old pysqlite Trac is for me an ideal candidate for multirepos as we could put the old svn repository together with the newer Mercurial one and have all the changeset links working again!
(btw Gerhard… I wonder if you still have a copy of the old Subversion repository, if it's not too much asking :-) )
follow-up: 6 comment:5 by , 15 years ago
Replying to cboos:
I'd like to get the feedback from Remy and Jonas on this, what they'd prefer (or simply do nothing if they find it's a weird idea of mine…).
Ah, link rot, the web's biggest curse! :-)
Do we have many references to PySQLite tickets and changesets on t.e.o? I'm too new to the project to know, and I haven't been able to find a good search keyword to find out.
Anyway, my guess is that it's easier to just import the data and host a read-only Trac instance rather than trying to create an HTML mirror.
I wouldn't use it for testing, though. Install multirepos to be able to view both repositories, but use another, dedicated instance (possibly with a copy of t.e.o) for actual testing. That will also allow training the migration to 0.12.
comment:6 by , 15 years ago
Replying to rblank:
Do we have many references to PySQLite tickets and changesets on t.e.o? I'm too new to the project to know, and I haven't been able to find a good search keyword to find out.
A lot of the tickets with the pysqlite keyword are related in one way or the other to some issue in the Pysqlite tracker. One could also search for the Pysqlite: intertrac prefix, but this also gives all the false positive due to the "pysqlite: <some versions>" matches.
While we're doing quite fine nowadays with SQLite / PySqlite w.r.t. concurrency issues, database locking and other weird stuff, this has not always been the case and being able to dig through the past tickets could be useful in the future, should some of these issues reappear, if only to not repeat past mistakes :-)
comment:7 by , 14 years ago
| Keywords: | documentation added |
|---|
follow-up: 9 comment:8 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Done (TracInstall@284 and PySqlite@46).
Looks like the pyqlite Trac at oss.itsystementwicklung.de is now offline? Too bad, it would have been useful for reference, at least.
Wild idea: maybe you can provide us with a copy that we could host here read-only (and not advertise with a "Tab" of course, simply have it reachable in order to see the old tickets).