New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Btrfs has eliminated the BTRFS_BUILD_VERSION in latest version #11417
Conversation
Does that mean http://repo.or.cz/w/btrfs-progs-unstable/devel.git/commit/514c5689bd672b21fa8033a7a48eae56a6e36b7f was reverted? |
The comments in the bugzilla seemed to indicate that upstream would not take a patch to put the BTRFS_BUILD_VERSION back since it was being manually created while BTRFS_LIB_VERSION can be automatically created. |
|
@tianon @rhatdan for now, sandeen and kdave sound ok with it: https://bugzilla.redhat.com/show_bug.cgi?id=1202373#c4 and given that the patch grabs whatever value exists for PACKAGE_VERSION from its config.h, it shouldn't be a hassle I think. correct me if i'm wrong. |
can you fix the unit test @rhatdan, otherwise this seems like a sane fix to me :) |
Fixed. |
/cc @prologic |
They say we should only use the BTRFS_LIB_VERSION They will no longer support this since it had to be managed manually Docker-DCO-1.1-Signed-off-by: Dan Walsh <dwalsh@redhat.com> (github: rhatdan)
still failing the unit tests, would be nice to get this into 1.6.0-rc2, do you want us to carry |
@jfrazelle strange. and the build box has the have /usr/include/btrfs/version.h?
would only happen if docker was built with btrfs_noversion |
OH! ubuntu ... :-( |
oh so wait should i just upgrade btrfs-tools is that the problem On Tue, Mar 24, 2015 at 10:25 AM, Vincent Batts notifications@github.com
|
well, ideally the test would be on a newer btrfs... but would mean the test will fail when there is no version.h. @rhatdan perhaps move you Lib Version test to a _test.go file that has the build tags of |
Docker-DCO-1.1-Signed-off-by: Dan Walsh <dwalsh@redhat.com> (github: rhatdan)
Sadly I did that locally but never pushed. |
https://www.youtube.com/watch?v=vCadcBR95oU On Tue, Mar 24, 2015 at 2:15 PM, Daniel J Walsh notifications@github.com
|
\o/ |
LGTM |
Aw, that's a shame. The library version is completely 1000% meaningless to me (where the "build version" actually matches the version number of the package I've got installed), but OK. LGTM |
Btrfs has eliminated the BTRFS_BUILD_VERSION in latest version
Couldn't we instead find a way to conditionally include this based on that one release of btrfs-progs that doesn't have the build version info (since they added it back thanks to @lsm5)? |
It's especially worrying since they never responded to https://bugzilla.redhat.com/show_bug.cgi?id=1202373#c5 to tell us whether they approve of our use of this header bit or not. 😢 |
@tianon an |
/me is not pleased there is a merge commit tsk tsk |
@vbatts 👍 😍
|
Meaningless, but more than nothing. I also understand the difficulty in
|
They did, though! @lsm5 sent the patch and they applied it, and it
shouldn't be a problem going forward because it's autogenerated now instead
of manually curated.
|
…diff-479b910834cf0e4daea2e02767fd5dc9R1 pr moby#11417 Docker-DCO-1.1-Signed-off-by: Jessica Frazelle <jess@docker.com> (github: jfrazelle)
…diff-479b910834cf0e4daea2e02767fd5dc9R1 pr moby#11417 Docker-DCO-1.1-Signed-off-by: Jessica Frazelle <jess@docker.com> (github: jfrazelle)
Ah yeah. I had to dig for that commit. it's not in their master |
/me is late to the party... the BUILD_VERSION patch has now landed in btrfs-progs master branch |
yayyyyy! On Wed, Mar 25, 2015 at 5:00 PM, Lokesh Mandvekar notifications@github.com
|
They say we should only use the BTRFS_LIB_VERSION
They will no longer support this since it had to be managed manually
Docker-DCO-1.1-Signed-off-by: Dan Walsh dwalsh@redhat.com (github: rhatdan)