Hello Phillip Susi! Thank you very much for your feedback!
On Thu, Jun 12, 2014 at 03:41:21PM -0400, Phillip Susi wrote: > I had prepared a package that essentially just threw out the existing > git repo with all local deviations in it ( since it effectively had > become an unmanageable fork of upstream ), and dropped the debian/ > directory into the new upstream sources. This likely would have > caused a few regressions from any unmerged patches debian is still > carrying, but I was not about to spend the time needed to pick through > all of the ~1000 commits in the git repo figuring out which ones are > still relevant and converting them to quilt patches. Yes the existing package is quite far from smooth to update. I spent quite some time myself investigating the git repo and how to deal with the 848 commit delta between upstream and the debian branches. Finally I settled for diffing the (debian) stable branch against the newer patches/v2.20.1 branch and then settled for just rebasing the patches branch on top of (upstream) tag v2.24.2. After some investigation many patches turned out to be obsoleted by upstream changes and most other patches could be easily tweaked into applying again. There is one final patch which still needs some work to apply though and that one is (as previously mentioned): http://anonscm.debian.org/gitweb/?p=users/lamont/util-linux.git;a=commit;h=23c9f34b9098ac22c1358001c40c17209bdb46ab I have just disabled that one for now. You'll find more information documented in the changelog of my package, which you can find here for now: http://people.debian.org/~ah/util-linux-2.24/ Hopefully you'll also find other changes that I've made to be useful. My goal was not only to update the package, but to make it easier to update it again in the future. I've investigated installed file diffs between my packages and the current util-linux package (on amd64) to be similar (except the changes documented in debian/util-linux.NEWS). Further work on my side involves (among other things) to install new utilities in the package. > Adam Conrad said he would block out some paid time to do that so I have > been waiting for that for several weeks now. Ok, I guess this was a private conversation? If you have any pointers to public conversations I'd be happy to read up on what's going on. If you need any help with anything don't hesitate to ask. I'm happy to help out. I assume updating the final patch is considered the main blocker right now? Are there any other (known) blockers? Do you have any review comments on my previous work linked above? Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
