libguytools
Hi, I tried to have a look at the libguytools package about bug #565859. I cloned the git repo and it seems that there is only a master branch. No upstream, debian nor pristine-tar branches. when I try a : git checkout -b upstream origin/upstream git throws this error : fatal: git checkout: updating paths is incompatible with switching branches. Did you intend to checkout 'origin/upstream' which can not be resolved as commit? Is it a configuration problem or is it me that forgot something ? -- Christophe Monniez ___ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/forensics-devel
afflib, libewf, libguytools, guymager
Hi, I'm currently working on the four packages mentionned in the subject. The problem that I'm facing is that they are tied together like that : + afflib optionnaly needs libewf to be more complete + libguytools needs libewf + guymager needs libguytools The problem that I'm facing is that I test the packages building with pbuilder. As pbuilder looks in the build-dpends to automaticaly download the ones needed, I cannot test the build of afflib as it needs libewf which is yet to born. The same problem will occur on the Debian build system. The solution might be to upload those packages in the right order and wait that it comes out officially before sending the next one. But it will make a long time before the last package will arrive in testing. For the pbuilder problem, I did not see any option to add extra-custom packages but I might use another way to test it. Do someone have an idea to solve this kind of problem ? I suppose that a lot of 'big' packages have this kind of problem, so I'm sure that a solution exists. -- Christophe Monniez ___ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/forensics-devel
Re: afflib, libewf, libguytools, guymager
Christophe Monniez wrote: The problem that I'm facing is that I test the packages building with pbuilder. As pbuilder looks in the build-dpends to automaticaly download the ones needed, I cannot test the build of afflib as it needs libewf which is yet to born. i've no idea, i don't use pbuilder (but an own script to manage the chroot). The same problem will occur on the Debian build system. if you're refering to the buildds, they will automatically handle this (and wait with building packages until all build-depends are available). The solution might be to upload those packages in the right order and wait that it comes out officially before sending the next one. doesn't matter at all; they all go through NEW anyway, and are, as history has shown, often not released out of NEW in the right order anyway. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ ___ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/forensics-devel
