Hi
When building Debian packages in scratchbox I often get problems
because the dpkg tools don't see the devkit tools as being installed.
Must I manually falsify the /var/lib/dpkg contents or am I missing
something?
Regards
Peter Pearse
__
No, the modifications to the qemu I have are not available anywhere else. If
it needs to get built with the scratchbox patches applied to it, I can
probably get that done, but I need to know if that's the case, and if so,
whether all the scratchbox patches get applied, up to and including the one
f
Diane Holt wrote:
I noticed that for 0.9.0 in your repository, there's only one patch file
(to the Makefile, to build static), so do you apply all the patches for
the previous versions as well?
Sorry to be a bother, but I really need to get this working (this qemu
supports additional features
New release:
* scratchbox-apt-https-devkit 1.0
Highlights:
* Support for https repositories for any flavor of debian devkit (at
least in theory) and, of course, a brand new version of apt
Notes:
* The apt inside this devkit is lenny's version, 0.7.6. It may not work
properly with the olde
Hi Timo & Jussi,
Thanks very much for turning that around so quickly. Unfortunately, my qemu
still isn't working for me -- but I think I may know why now. In looking
through your repository, I found a number of patch files for the qemu
sources. Are the qemu's that are used in scratchbox all built
Timo Savola wrote:
Thanks! I had actually just tracked down misc_runner, so I was starting to
look at misc_runner.c myself, but if the fix will be available soon, I guess
I can stop doing that :)
BTW, I tried passing the flag in using the var, but it didn't work.
It should.. Anyway, my change
