Hi, Danny Edel wrote: > Debian actually has ready-made VM scripts for you. > https://wiki.debian.org/sbuild
They urgently need advertising at the entry points of mentors.debian.net and at the upload instructions. > call "debuild -S" on your host machine first: > This will create a .debian.tar.xz and a (signed) .dsc file in "..", then > you can call "sbuild --dist sid your-package_version.dsc". If that goes > through, you know your dsc is good and you can upload it to mentors with > "dupload --to mentors my.changes". I was desparately digging the Debian docs for something like this. Hm. What shall i do with my brand new sid VM now ? I copied the development workshop from the host and installed the needed packages for dpkg-buildpackage. The first round of packages is built as was done on the host machine and installed. Next i plan to test the proposed command debuild. So many branches to explore ... https://wiki.debian.org/sbuild#Setup writes: > 5 ... *logout* and *re-login* I'm logged in by my X session and want to keep it running. Line 2 seems newer than the explanation beneath. So line 5 would be covered by: "The fourth line is to update the active user group set to include sbuild." > logout-relogin or use "newgrp sbuild" in your current shell. Aha. Enlightenment. A fruitless google search of "active user group set" already brought me to the suspicion that something around newgroup(1) was meant. > so make sure to have > 10G space there. 2 TB free. My mass storage still produces an echo when i shout. Well, i need to make some progress with uploading. So i'll go on with the VM for now. I need to learn a bit more about what sbuild does. On the long run it looks cleaner. Which one to install ? dput: /usr/bin/dput dput-ng: /usr/bin/dput My Jessie obviously has "dput" installed. So many branches ... Have a nice day :) Thomas
