Bug#679763: debsnap: bisect option/script

Osamu Aoki osamu at debian.org
Tue Mar 8 10:43:34 UTC 2016


Hi,

On Tue, Mar 08, 2016 at 10:17:58AM +0800, Paul Wise wrote:
> On Mon, 2016-03-07 at 21:44 +0900, Osamu Aoki wrote:
> 
> > For source history, "gbp inport-dscs --debsnap" gives you access to real
> > "git bisect" access.  So no point reinvention it in debsnap itself.
> 
> I wasn't aware of that, thanks for the tip.
> 
> > (Yes, I am living in high bandwidth region.)
> 
> Yeah, for me that would be a prohibitive exercise.
> 
> I can't imagine how Joey Hess would use that ;)

Then try --list approach in few weeks.

> > For binary package history checking, dependency etc. matters and most
> > likely needs your manual attention.  At least with the new --list option
> > printing out sorted list of versions, you can do bisect like action
> > manually whice checking dependencyetively recent versions. 
> 
> I don't see any --list option in the debsnap in unstable.

Oh, that is pending upload feature :-)  I just coded it.
 
> pabs at chianamo ~ $ debsnap --binary --list libc6
> Unknown option: list
> ...
> 
> I would really like to see a general bisect tool that could wrap
> debsnap and other bisect situations.
> 
> This can be hacked around using a fake git repo and git bisect though,
> so once debsnap --list is available that should be enough.
> 
> > Do you still think we should add complexities into debsnap?
> 
> No. 
> 
> Please close this bug with the upload that adds debsnap --list.

OK.



More information about the devscripts-devel mailing list