RFC - update and move to git source for debian updates and 3.0 (git) source format
@nextime @jaromil I've pushed ahead and done the work to upgrade debootstrap to resolve the issues for our installer.
As part of this I also merged our version onto debians git source, so we can have a full history and more easily merge or cherry-pick updates from there and converted our package to 3.0 (git) format.
This is all done and successfully built in suites/jessie-proposed.
If your happy with this approach I'd like to push this into suites/jessie ASAP so we can get debian-installer fixed.
Instructions on howto setup and merge from debian's git repo are located in debian/README.DevuanSource
If you'd rather continue with the alternative method of merging upstream tar balls, then feel free to ditch it and merge in the 1.0.86 release from debian.
Regards, Daniel.
-
go ahead and push it to jessie, also, is the version you picked up from debian the same for ascii and ceres? If yes, maybe we should move your new version to master too
-
Ok this is done. There are newer versions for testing & unstable so I've now merged those in as well and set suites/experimental to track master (currently the same as ascii and unstable). I don't care for using master so I'd rather make experimental the default branch as that better matches the path of development.
I'm thinking of writing a tool to make keeping track of upstreams easier - similar to what uscan and the debian/watch is for debian, but making it support using VCS for tracking upstreams. This also makes it easier for us to go our own way and also do automated builds of upstream changes etc. Part of that utility will be a tool that reads the current git config and using that to create the watch file.
-
closed
-
Ok this is done. There are newer versions for testing & unstable so I've now merged those in as well and set suites/experimental to track master (currently the same as ascii and unstable). I don't care for using master so I'd rather make experimental the default branch as that better matches the path of development.
I'm thinking of writing a tool to make keeping track of upstreams easier - similar to what uscan and the debian/watch is for debian, but making it support using VCS for tracking upstreams. This also makes it easier for us to go our own way and also do automated builds of upstream changes etc. Part of that utility will be a tool that reads the current git config and using that to create the watch file.