Re: [DNG] ancient data recovery: GPE calendar
On Wed, Jun 06, 2018 at 02:42:44PM +0200, k...@aspodata.se wrote: > Hendrik: > ... > > You found a little more than I did. Running this package on a wheezy > > system is probably the easiest way to read the calendar. But exporting > > it to a modern file format is likely another matter. > > > > I managed to find the wheezy source package. But the way the word has > > changed, it may be easiest to use the binary package on a real wheezy > > system thatn to try to build the package in a modern system. > > I have in my archives: > gpe-calendar_0.91.orig.tar.gz > gpe-calendar_0.92.orig.tar.bz2 I have the second one, too. But I'm likey to have to find more before I can do anything with it. > in case you want them. > > The first one gives on configure: > No package 'libgpewidget' found > No package 'libgpepimc' found > No package 'libgpevtype' found > No package 'libeventdb' found > No package 'esound' found > No package 'libxsettings-client' found > No package 'libhandoff' found > No package 'libsoup-2.2' found > No package 'libsoundgen' found > No package 'dbus-glib-1' found > No package 'libschedule' found Yes, that's the kind of 'more' I'll need, > > > I'm still exploring alternatives before taking action. > > The best bet is to set up a wheezy system and go from there. Very likely. -- hendrik > > > For past events, I'd be happy with a complete, readable text file. I > > might be able to write a program to produce that if I find a compatible > > version of sqlite, or if current sqlite will upgrade the db to whatever > > it uses now. > ... > > There is no dependancy on sqlite: > $ find . -type f | xargs grep sql > ./ChangeLog:* configure.ac: Remove dependencies on sqlite and mimedir-1.0. Interesting. > ./ChangeLog:(do_import_vevent): Don't open an sqlite session, insert > directly > ./ChangeLog:* Makefile: Don't link with -lsqlite. Use STANDARD_CFLAGS, > ./ChangeLog:* familiar/control1 (Depends): Remove libsqlite0. Add -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ancient data recovery: GPE calendar
Hendrik: ... > You found a little more than I did. Running this package on a wheezy > system is probably the easiest way to read the calendar. But exporting > it to a modern file format is likely another matter. > > I managed to find the wheezy source package. But the way the word has > changed, it may be easiest to use the binary package on a real wheezy > system thatn to try to build the package in a modern system. I have in my archives: gpe-calendar_0.91.orig.tar.gz gpe-calendar_0.92.orig.tar.bz2 in case you want them. The first one gives on configure: No package 'libgpewidget' found No package 'libgpepimc' found No package 'libgpevtype' found No package 'libeventdb' found No package 'esound' found No package 'libxsettings-client' found No package 'libhandoff' found No package 'libsoup-2.2' found No package 'libsoundgen' found No package 'dbus-glib-1' found No package 'libschedule' found > I'm still exploring alternatives before taking action. The best bet is to set up a wheezy system and go from there. > For past events, I'd be happy with a complete, readable text file. I > might be able to write a program to produce that if I find a compatible > version of sqlite, or if current sqlite will upgrade the db to whatever > it uses now. ... There is no dependancy on sqlite: $ find . -type f | xargs grep sql ./ChangeLog:* configure.ac: Remove dependencies on sqlite and mimedir-1.0. ./ChangeLog:(do_import_vevent): Don't open an sqlite session, insert directly ./ChangeLog:* Makefile: Don't link with -lsqlite. Use STANDARD_CFLAGS, ./ChangeLog:* familiar/control1 (Depends): Remove libsqlite0. Add Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ancient data recovery: GPE calendar
On Tue, 5 Jun 2018 23:43:12 -0400, Hendrik wrote in message <20180606034312.ga24...@topoi.pooq.com>: > On Wed, Jun 06, 2018 at 04:38:59AM +0200, Arnt Karlsen wrote: > > On Tue, 5 Jun 2018 18:50:10 -0400, Hendrik wrote in message > > <20180605225010.gc12...@topoi.pooq.com>: > > > > > On Tue, Jun 05, 2018 at 11:51:11PM +0200, Arnt Karlsen wrote: > > > > On Tue, 5 Jun 2018 16:06:39 +0200, Alexander wrote in message > > > > <20180605140639.ga7...@gxis.de>: > > > > > > > > > ...on Mon, Jun 04, 2018 at 05:55:33PM -0400, Hendrik Boom > > > > > wrote: > > > > > > GPE was last seen packaged in Debian wheezy. I *might* be > > > > > > able to find an old wheezy installation, but I'm not sure > > > > > > it will still run. > > > > > > > > ..what package name? > > > > > > gpe-calendar, for the one I'm most concerned with. > > > > ..you found it?: > > https://packages.debian.org/wheezy/gpe-calendar or > > http://archive.debian.org/debian-archive/debian/pool/main/g/gpe-calendar/ > > > > ..or did I only find some old rotten bits of junk? > > https://tracker.debian.org/pkg/gpe-calendar > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;dist=oldstable;package=gpe-calendar > > > > You found a little more than I did. Running this package on a wheezy > system is probably the easiest way to read the calendar. But > exporting it to a modern file format is likely another matter. ..pipe it's output thru cat, tac, cut, netcat etc to chop up your calendar database into nice wee text bits that can be "hand fed" into your next calendar etc database. Ideally automagically, if you can, there is a nice big market for such expensive services, commonly caused by "vendor lock-in." ;o) ..beware of empty data fields, they may be valid _because_ they are empty. Like my "expertise" on databases ;oD, I ask dumb enough questions to trigger smart enough ideas to get things back up working again. ;o) > I managed to find the wheezy source package. But the way the word ..er, "word" or "world"? > has changed, it may be easiest to use the binary package on a real > wheezy system thatn to try to build the package in a modern system. > > I'm still exploring alternatives before taking action. > > For past events, I'd be happy with a complete, readable text file. I > might be able to write a program to produce that if I find a > compatible version of sqlite, or if current sqlite will upgrade the > db to whatever it uses now. > > For future events, I could hand-enter them into a new calendar system > -- preferably one that lets me export everything into a readable > form, and which I can sync across devices with something relemblig > revision control. ..netcat "hand feeding" git "hand feeding" postgresql? -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ancient data recovery: GPE calendar
On Wed, Jun 06, 2018 at 04:38:59AM +0200, Arnt Karlsen wrote: > On Tue, 5 Jun 2018 18:50:10 -0400, Hendrik wrote in message > <20180605225010.gc12...@topoi.pooq.com>: > > > On Tue, Jun 05, 2018 at 11:51:11PM +0200, Arnt Karlsen wrote: > > > On Tue, 5 Jun 2018 16:06:39 +0200, Alexander wrote in message > > > <20180605140639.ga7...@gxis.de>: > > > > > > > ...on Mon, Jun 04, 2018 at 05:55:33PM -0400, Hendrik Boom wrote: > > > > > > > > > GPE was last seen packaged in Debian wheezy. I *might* be > > > > > able to find an old wheezy installation, but I'm not sure it > > > > > will still run. > > > > > > ..what package name? > > > > gpe-calendar, for the one I'm most concerned with. > > ..you found it?: > https://packages.debian.org/wheezy/gpe-calendar or > http://archive.debian.org/debian-archive/debian/pool/main/g/gpe-calendar/ > > ..or did I only find some old rotten bits of junk? > https://tracker.debian.org/pkg/gpe-calendar > https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;dist=oldstable;package=gpe-calendar You found a little more than I did. Running this package on a wheezy system is probably the easiest way to read the calendar. But exporting it to a modern file format is likely another matter. I managed to find the wheezy source package. But the way the word has changed, it may be easiest to use the binary package on a real wheezy system thatn to try to build the package in a modern system. I'm still exploring alternatives before taking action. For past events, I'd be happy with a complete, readable text file. I might be able to write a program to produce that if I find a compatible version of sqlite, or if current sqlite will upgrade the db to whatever it uses now. For future events, I could hand-enter them into a new calendar system -- preferably one that lets me export everything into a readable form, and which I can sync across devices with something relemblig revision control. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ancient data recovery: GPE calendar
On Tue, 5 Jun 2018 18:50:10 -0400, Hendrik wrote in message <20180605225010.gc12...@topoi.pooq.com>: > On Tue, Jun 05, 2018 at 11:51:11PM +0200, Arnt Karlsen wrote: > > On Tue, 5 Jun 2018 16:06:39 +0200, Alexander wrote in message > > <20180605140639.ga7...@gxis.de>: > > > > > ...on Mon, Jun 04, 2018 at 05:55:33PM -0400, Hendrik Boom wrote: > > > > > > > GPE was last seen packaged in Debian wheezy. I *might* be > > > > able to find an old wheezy installation, but I'm not sure it > > > > will still run. > > > > ..what package name? > > gpe-calendar, for the one I'm most concerned with. ..you found it?: https://packages.debian.org/wheezy/gpe-calendar or http://archive.debian.org/debian-archive/debian/pool/main/g/gpe-calendar/ ..or did I only find some old rotten bits of junk? https://tracker.debian.org/pkg/gpe-calendar https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;dist=oldstable;package=gpe-calendar -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ancient data recovery: GPE calendar
On Tue, Jun 05, 2018 at 11:51:11PM +0200, Arnt Karlsen wrote: > On Tue, 5 Jun 2018 16:06:39 +0200, Alexander wrote in message > <20180605140639.ga7...@gxis.de>: > > > ...on Mon, Jun 04, 2018 at 05:55:33PM -0400, Hendrik Boom wrote: > > > > > GPE was last seen packaged in Debian wheezy. I *might* be able to > > > find an old wheezy installation, but I'm not sure it will still > > > run. > > ..what package name? gpe-calendar, for the one I'm most concerned with. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ancient data recovery: GPE calendar
On Tue, 5 Jun 2018 16:06:39 +0200, Alexander wrote in message <20180605140639.ga7...@gxis.de>: > ...on Mon, Jun 04, 2018 at 05:55:33PM -0400, Hendrik Boom wrote: > > > GPE was last seen packaged in Debian wheezy. I *might* be able to > > find an old wheezy installation, but I'm not sure it will still > > run. ..what package name? > Whoah, heavy bitrot around that one... > > I still have a working wheezy system, but it shouldn't be too > hard to set up a fresh wheezy VM. I mean, someone somewhere still > does security updates for that release... > It ships libsqlite 2.8, which may or may not be able to load your > database. > > One way out might be by starting a small retrocomputing adventure: > Install gpesyncd (included in wheezy) and then try to build > opensync from source to convert your data to a format that might > still be portable. (SyncML?) > > Last version of opensync that included the gpe plugin seems to > have been 0.36, of which archive.org has a copy: > > https://web.archive.org/web/20140407043108/http://opensync.org:80/download/releases/0.36/ ..according to: https://www.debian.org/distrib/archive you may find it diving down http://archive.debian.org/debian-archive/ ..e.g. for packages named flightgear: http://archive.debian.org/debian/pool/main/f/flightgear/ ..https://archive.debian.net/ is down, was AFAIR searchable. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ancient data recovery: GPE calendar
On Mon, 4 Jun 2018 17:55:33 -0400 Hendrik Boom wrote: > I have a GPE calendar, which I still use daily, and some GPE > contacts. > > The machine these run on is starting to fail -- spontaneous reboot, > random battery life, and the like. > > It still runs well enough that I can *copy* the GPE data bases. > > Any ideas how to move the data to a modern format? And what modern > calendar format to use? > > GPE was last seen packaged in Debian wheezy. I *might* be able to > find an old wheezy installation, but I'm not sure it will still run. > > Development on GPE seems to have ceased more than 10 years ago. > > The caledar data base is in sqlite 2.1 format. Even ten years ago, > people still using it and asking for help were being told to get on > with sqlite 3.0. Depending on how they structured the sqlite, you might be able to reverse engineer the thing just from looking at what's in the tables and columns. SteveT Steve Litt June 2018 featured book: Twenty Eight Tales of Troubleshooting http://www.troubleshooters.com/28 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ancient data recovery: GPE calendar
...on Mon, Jun 04, 2018 at 05:55:33PM -0400, Hendrik Boom wrote: > GPE was last seen packaged in Debian wheezy. I *might* be able to find > an old wheezy installation, but I'm not sure it will still run. Whoah, heavy bitrot around that one... I still have a working wheezy system, but it shouldn't be too hard to set up a fresh wheezy VM. I mean, someone somewhere still does security updates for that release... It ships libsqlite 2.8, which may or may not be able to load your database. One way out might be by starting a small retrocomputing adventure: Install gpesyncd (included in wheezy) and then try to build opensync from source to convert your data to a format that might still be portable. (SyncML?) Last version of opensync that included the gpe plugin seems to have been 0.36, of which archive.org has a copy: https://web.archive.org/web/20140407043108/http://opensync.org:80/download/releases/0.36/ Alex. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ancient data recovery: GPE calendar
I have a GPE calendar, which I still use daily, and some GPE contacts. The machine these run on is starting to fail -- spontaneous reboot, random battery life, and the like. It still runs well enough that I can *copy* the GPE data bases. Any ideas how to move the data to a modern format? And what modern calendar format to use? GPE was last seen packaged in Debian wheezy. I *might* be able to find an old wheezy installation, but I'm not sure it will still run. Development on GPE seems to have ceased more than 10 years ago. The caledar data base is in sqlite 2.1 format. Even ten years ago, people still using it and asking for help were being told to get on with sqlite 3.0. --- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
