Error upgrading the dialog port
During an 'upgrade outdated' the dialog port failed. I had forgotten about dialog, no longer use it and have now uninstalled it. However, someone may want to know about how it failed so I enclose the log mentioned with in the error message. Barrie. main.log Description: Binary data ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
For obvious reasons, Palm has not been keeping its drivers up-to-date; http://kb.hpwebos.com/wps/portal/kb/common/article/33529_en.html#mac is still downloadable but I would be very very surprised if it worked on 10.9. I did find this: http://pccallup.sourceforge.net which may be a working replacement. (I don’t have one to test with, sorry.) The Palm software hasn’t worked since 10.7. That’s why I switched to Missing Sync. However it (and other companies) used iSync which Apple has removed from 10.9. I tried the pccallup and the site still exists but there are no files available. Can I copy a /dev/pilot air /dev/ttyUSB1 from a backup under an old operating system or are there going to be other pieces that go along with that that I’ll also be missing? Thanks, Lenore ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Thu, 16 Jan 2014, Lenore Horner wrote: For obvious reasons, Palm has not been keeping its drivers up-to-date; http://kb.hpwebos.com/wps/portal/kb/common/article/33529_en.html#mac is still downloadable but I would be very very surprised if it worked on 10.9. I did find this: http://pccallup.sourceforge.net which may be a working replacement. (I don’t have one to test with, sorry.) The Palm software hasn’t worked since 10.7. That’s why I switched to Missing Sync. However it (and other companies) used iSync which Apple has removed from 10.9. I tried the pccallup and the site still exists but there are no files available. Can I copy a /dev/pilot air /dev/ttyUSB1 from a backup under an old operating system or are there going to be other pieces that go along with that that I’ll also be missing? No, that definitely won’t work. Your best bet might be to run an old OS version in emulation... but even that could be tricky. Alternatively, there are other hacky things you could do with the device if you’re loath to retire it, but that’s getting way off-topic for this list. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Jan 16, 2014, at 9:52 AM, Lenore Horner lenorehor...@sbcglobal.net wrote: For obvious reasons, Palm has not been keeping its drivers up-to-date; http://kb.hpwebos.com/wps/portal/kb/common/article/33529_en.html#mac is still downloadable but I would be very very surprised if it worked on 10.9. I did find this: http://pccallup.sourceforge.net which may be a working replacement. (I don’t have one to test with, sorry.) The Palm software hasn’t worked since 10.7. That’s why I switched to Missing Sync. However it (and other companies) used iSync which Apple has removed from 10.9. I tried the pccallup and the site still exists but there are no files available. Can I copy a /dev/pilot air /dev/ttyUSB1 from a backup under an old operating system or are there going to be other pieces that go along with that that I’ll also be missing? Thanks, Lenore As was stated earlier, these aren’t files, so they can’t just be copied. These are essentially the inputs and output of device drivers. So, when the right drivers are installed, copying /dev/pilot will cause the driver to read data from the Palm, and output the results to another file. The device driver is code that reads (or writes) data from a piece of hardware and then outputs that data to /dev/pilot (or whatever). So, that another program can read from that as though it is a file. So /dev/pilot is really a virtual file, not a real file, and trying to copy it would not cause the driver to be copied, but instead would cause the device driver to try to read some data. —Adam ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Registry database disk image is malformed
I was installing a large port when my system KP'd. Upon restart, I tried to continue installing the port, but get an error the the sqlite database registry.db is malformed. The conventional wisdom in such cases seems to be to dump and restore the database. I can dump the database fine, but when I try to restore to a new db file, I get an error creating the PORTS table regarding an invalid text collation value of VERSION. Am I correct in assuming that this is a MacPorts extension to sqlite3? If so, is there a command line tool which understands that extension? Thanks... John ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Registry database disk image is malformed
In the base/src/cregistry/sql.c of MacPorts, I see this command inside init_db(): sqlite3_create_collation(db, VERSION, SQLITE_UTF8, NULL, sql_version); Can you make the collation from that? There is a db function defined by init_db() as well. On Jan 16, 2014, at 13:43, John Ruschmeyer jrusc...@gmail.com wrote: I was installing a large port when my system KP'd. Upon restart, I tried to continue installing the port, but get an error the the sqlite database registry.db is malformed. The conventional wisdom in such cases seems to be to dump and restore the database. I can dump the database fine, but when I try to restore to a new db file, I get an error creating the PORTS table regarding an invalid text collation value of VERSION. Am I correct in assuming that this is a MacPorts extension to sqlite3? If so, is there a command line tool which understands that extension? Thanks... John ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Registry database disk image is malformed
On Thu, Jan 16, 2014 at 02:53:16PM -0500, Jeremy Lavergne wrote: In the base/src/cregistry/sql.c of MacPorts, I see this command inside init_db(): In the very same directory, you should see a binary sqlite extension you can load into the standard sqlite3 command line client using .load path The same directory should also contain a readme file explaining this procedure. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error upgrading the dialog port
On Jan 16, 2014, at 04:22, Barrie Stott wrote: During an 'upgrade outdated' the dialog port failed. I had forgotten about dialog, no longer use it and have now uninstalled it. However, someone may want to know about how it failed so I enclose the log mentioned with in the error message. Please file a bug report in the issue tracker. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Registry database disk image is malformed
On Jan 16, 2014, at 12:43, John Ruschmeyer wrote: I was installing a large port when my system KP'd. Upon restart, I tried to continue installing the port, but get an error the the sqlite database registry.db is malformed. The conventional wisdom in such cases seems to be to dump and restore the database. I can dump the database fine, but when I try to restore to a new db file, I get an error creating the PORTS table regarding an invalid text collation value of VERSION. Am I correct in assuming that this is a MacPorts extension to sqlite3? If so, is there a command line tool which understands that extension? Yes, that is a MacPorts SQLite extension. You can load it this way: http://trac.macports.org/ticket/35281#comment:6 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Check dependencts for camlimages
see https://trac.macports.org/ticket/41976 I haven't seen any further movement on this lately. doing update all gets clobbered by the presence of camlimages. When I do this : [console] linus:~ tim$ port dependents camlimages camlimages has no dependents. [/console] Do I presume that it is safe to uninstall camlimages? If so, what is the correct syntax? I don't recall installing camlimages and since it has no dependents, how might it have gotten on my machine? :) Other than me coding in my sleep. Thanks -- Tim tim at tee jay forty nine dot com or akwebsoft dot com http://www.akwebsoft.com, http://www.tj49.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Check dependencts for camlimages
On Jan 16, 2014, at 19:05, Tim Johnson t...@akwebsoft.com wrote: see https://trac.macports.org/ticket/41976 I haven't seen any further movement on this lately. doing update all gets clobbered by the presence of camlimages. When I do this : [console] linus:~ tim$ port dependents camlimages camlimages has no dependents. [/console] Do I presume that it is safe to uninstall camlimages? Sure. If anything depends on it, MacPorts will tell you and will not uninstall it. If so, what is the correct syntax? sudo port uninstall camlimages I don't recall installing camlimages and since it has no dependents, how might it have gotten on my machine? You either installed it, or another port you installed installed it as a dependency. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Any objections to removal of the carbon variant in py-wxpython-2.8?
On Jan 15, 2014, at 19:57, Eric Gallager wrote: On Wed, Jan 15, 2014 at 6:13 PM, Ryan Schmidt wrote: On Jan 15, 2014, at 10:27, Eric Gallager wrote: I am still on 10.6 and still use the `+carbon` variant for py-wxpython-2.8… Yes but would it be a problem for you to use the +gtk variant instead? If so please explain. No, just that I prefer it and currently use it... I could probably do without it though. Why do you prefer it? In what way is the carbon variant different from the gtk variant? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Jan 16, 2014, at 10:20, John Ruschmeyer jrusc...@gmail.com wrote: I think you want /dev/pilot to be a symbolic link to the device for your serial port. Something like: # ln -s /dev/ttyUSB1 /dev/pilot Doesn’t that mean I should have /dev/ttyUSB1 already? I don’t. Oddly, Missing Sync will actually sync with the palm still under Mavericks — sort of: calendar and contacts will not sync but supposedly media will. So something lets my laptop talk to the palm when it’s plugged in but I don’t know where to find it and how to tell jpilot what to look for. Lenore ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Jan 16, 2014, at 21:09, Lenore Horner lenorehor...@sbcglobal.net wrote: On Jan 16, 2014, at 10:20, John Ruschmeyer jrusc...@gmail.com wrote: I think you want /dev/pilot to be a symbolic link to the device for your serial port. Something like: # ln -s /dev/ttyUSB1 /dev/pilot Doesn’t that mean I should have /dev/ttyUSB1 already? I don’t. I don’t either. Oddly, Missing Sync will actually sync with the palm still under Mavericks — sort of: calendar and contacts will not sync but supposedly media will. So something lets my laptop talk to the palm when it’s plugged in but I don’t know where to find it and how to tell jpilot what to look for. We’re talking about the jpilot port? It hasn’t been updated since 2006. Meanwhile new versions of jpilot have been released as recently as 2011. We should probably update the port to that version and then see where that gets us. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpilot
On Jan 16, 2014, at 21:24, Ryan Schmidt ryandes...@macports.org wrote: On Jan 16, 2014, at 21:09, Lenore Horner lenorehor...@sbcglobal.net wrote: On Jan 16, 2014, at 10:20, John Ruschmeyer jrusc...@gmail.com wrote: I think you want /dev/pilot to be a symbolic link to the device for your serial port. Something like: # ln -s /dev/ttyUSB1 /dev/pilot Doesn’t that mean I should have /dev/ttyUSB1 already? I don’t. I don’t either. From the jpilot documentation: http://www.jpilot.org/docs/manual.html Serial Port Setup When syncing, J-Pilot uses the port and speed settings out of the J-Pilot preferences screen. If the port is blank then J-Pilot will use the PILOTPORT environment variables, as does pilot-link. If these are blank also then J-Pilot will default to /dev/pilot. It is recommended, but not necessary to make a link from /dev/pilot to the correct serial port. So, if your cradle is on COM1, this is /dev/ttyS0 under Linux. You could execute the command ln -s /dev/ttyS0 /dev/pilot. COM2 is /dev/ttyS1, and so on. The Linux serial ports cua[n] are going away. You should use the ttyS[n] ports instead. USB ports are usually /dev/ttyUSB1, or /dev/usb/tts/1 (for devfs), but some devices use /dev/ttyUSB0, or /dev/usb/tts/0. You must also give non-root users permissions to access the serial port. The command to do this is (as root) chmod 666 /dev/ttyS0 for the first serial port, ttyS1, for the second, and so on. The mention of “/dev/ttyUSB1” could very well be a Linuxism not applicable to OS X. OS X might not expose the USB ports as a device; I don’t know. This post says it does not: http://stackoverflow.com/questions/11784248/mac-os-analog-to-dev-ttyusbxx ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
