Hi, Just a "hello I'm still alive" mail Firstly, thanks for the uploading. packages built fine but there is a problem with kfreebsd during the install process? I'll try to check this. Can I create a pbuilder chroot using kfreebsd on a debian testing amd64? Next is inline. >> Yes, but pbuilder is toooooo slow on my VBox (> 6 hours for *one* build). > > Ups, that's *really* slow. You might gain some spead with cowbuilder > (that uses copy on write to create the chroot system). >> I only succeeded to have a debian testing with xfce running without crashing. > > I can not comment on this because it is to rare information. I can now work with gnome 3.4.3 and/or 3.8 on my laptop without crash using the gnome classic mode. >> But I did not succeed with the SVN+SSH configuration. Why??? I miss time to explore. > > As I wasked in my previous mail, please try to ssh into svn.d.o. It is > really hard to tall why it fails on your side without doing these simple > tests. Ok I'll send you the result (now it's problem of public key) >>> I currently can't update my pbuilder environment (from Sao Paolo airport) >> >> Yes, your Qt4 packages was the latests. May be we need to add >> >> qt4-default >> >> to build-dep to get around this issue? Not sure. > > Well, your latest change was to add libopencv-objdetect-dev as > Build-Depends which solved the problem I was observing on my side in the > first place. So it somehow seems settled. That's strange because opencv does not affect Qt build process and your problem was clearly linked to the Qt build. Whatever, if all works fine we win some time on this side. >> Ok you can test my very latest commit, it should work. > > I checked your last commit and also noticed the enhanced d/watch file. > However, the current download page does not contain the version you > injected in d/changelog. Please note that I reverted the upstream > version to what is downloadable for public. I also have set the target > distribution to UNRELEASED - please also do it this way until the > package is actually uploaded. Ooops, yes... Sorry. I'm tired and just wanted to write 0.9.0~beta1-2 > I did another change that uses xz compression in the resulting binaries > - seems to be a good idea considering their size. Ah? Interesting! > What is confusing me a bit is the fact that the build keeps on working > under my 'testing' system but fails again in pbuilder with the problem > I reported initially. I will try to track down this on my side first > because Thorsten was obviously able to build the package. May be you need to update the pbuilder root? >> Yes I commit a draft code that I've reverted later. > > So this explains why it failed on my side. No this had nothing to do with your previous build crash. >>> Ahh, it is about the LSM presentation, right? How many time is left? >>> As I said I can not do anything the next 24 hours but I might have a >>> look into what has changed on Tuesday once I might be back to normal >>> operation. >> >> I'm presenting FreeMedForms on the 11th july conference + workshop. > > OK. You should be fine with the package that was uploaded to > experimental by Thorsten. T.H.A.N.K.S. A L.O.T.! the correct command to install the packages is sudo apt-get -t experimental freemedforms-project is that it? > Any other polishing should be done without > time pressure to finally polish everything that deserves beeing solved. Yes I'm already investigation some issue on the package and already corrected two of them. I don't know what to do for the documentation packages. I'm trying to fine some information about the rpath issue. Eric
Attachment:
PGP.sig
Description: =?iso-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=