On Mon, 2008-02-18 at 23:08 +0000, Philip Aston wrote: > Thanks Mark, I suspect I'll wait until a clean install rather than manually > delete files and risk making more spectacular errors (and there have been > many during my Linux adventures!). I have actually started by removing all > the apt packages, commenting out the ""sid" lines in sources.list, apt-get > update then reinstalling from my usual sources.list (started out as Debian > etch but since updated to lenny)- that's why I say I have Debian Lenny with > several "unstable" packages where these are required eg for Sony Ericsson > phones. >
Cool, sometimes it's easier to start from scratch when you have a lot of source builds hanging around. It's for this reason I originally learnt how to build debs, so the package manager always new what was what, but that's another story... > I was then able to start Raki and connect with synce-serial-start. Configure > option within raki returned "no synchronizer installed". > Only "unstable" has syncekonnector- so I uncommented sid again to get it. > After installation, I came back to "wrong library type"- so, unless > syncekonnector is itself confused by conflicting library files, it may be > that the problem is not caused by svn or other source-built packages, but by > a dependency within syncekonnector. At this point most of the apps are from > testing but that is, as you say, easily overcome. > I dont know anything about syncekonnector, so cant really comment, but I don't think its been maintained for some time. > This may be an oversimplification but I would guess that library sharing > within apt is unlikely to produce conflicts, and that, if a source-built > package has replaced a library file or changed a path, reinstallation from > apt (which is operated as root) should change it back again. > Not sure what you mean by library sharing exactly, but yes, reinstalling a package with apt will replace anything that has been overwritten. > As it happens I am also working on a self-build with a "pure" Debian Lenny > system from the testing iso rather than etch + update. I'll see what happens > to my ipaq, and report back- then I could temporarily add "unstable" to > sources.list to get the raki, rapi, and synce packages if necessary. What do > you think?-Phil > Debian tends to be very good with upgrades, so straight lenny will probably not differ much from etch + lenny update. If you want to pick certain packages from unstable or experimental, the best way is to keep those extries in sources.list, and add the following to /etc/apt/preferences Package: * Pin: release o=Debian,a=stable Pin-Priority: 400 Package: * Pin: release o=Debian,a=testing Pin-Priority: 900 Package: * Pin: release o=Debian,a=unstable Pin-Priority: 300 Package: * Pin: release o=Debian,a=experimental Pin-Priority: 100 Package: * Pin: release o=Debian Pin-Priority: -1 In short, testing is given the highest importance (Pin-Priority), followed by stable, unstable and experimental, and apt will always try to use packages from preferred suites. Since it knows about unstable packages though, it's easy to force it to install a higher version for a particular package. This is particularly useful now Jonny has got 0.11 libsynce*, librapi* and librra* into unstable. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
