Hi Michael, Am 10.04.2015 um 23:05 schrieb Michael Biebl: > Am 10.04.2015 um 23:00 schrieb Micha Lenk: >> But how do we proceed with this bug to decide whether it is >> release critical for Debian Lenny or not? Michael, what do you >> suggest? > > If you can reproduce the issue reliably, you could run git bisect > between 0.9.10 and 1.0.0 to find the commit which fixed it. Then > we could evaluate, if that fix is (easily) backportable.
I am willing to do this, and I know how to use 'git bisect'. But given all the patches in the Debian package, I don't know how to put that in a consistent workflow that ensures a NetworkManager properly integrated into Debian. Either the dpkg-buildpackage fails, apparently because of missing patches, or I am struggling with applying the patches on other upstream sources than the 0.9.10.0 one. Any suggestions? Or, what pitfalls should I be aware of when building and testing upstream's source code on Debian Jessie? Best regards, Micha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
