libraries: exclude the full set of libc6 #1632

Merged
merged 2 commits into from Oct 23, 2017

Conversation

3 participants
Collaborator

sergiusens commented Oct 18, 2017

Signed-off-by: Sergio Schvezov sergio.schvezov@canonical.com

  • Have you followed the guidelines for contributing?
  • Have you signed the CLA?
  • If this is a bugfix. Have you checked that there is a bug report open for the issue you are trying to fix on bug reports?
  • If this is a new feature. Have you discussed the design on the forum?
  • Have you successfully run ./runtests.sh static?
  • Have you successfully run ./runtests.sh unit?

libraries: exclude the full set of libc6
Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com>

@sergiusens sergiusens added this to the 2.35 milestone Oct 18, 2017

@sergiusens sergiusens added the bug label Oct 18, 2017

@sergiusens sergiusens self-assigned this Oct 18, 2017

Member

kyrofa commented Oct 18, 2017

I like this, but it seems like a bit of a half measure. In an ideal scenario, wouldn't we want to do this for every package included in the core snap? A list that, of course, we do not have.

- return frozenset(['libc.so.6'])
+ logger.debug('Only excluding libc libraries from the release')
+ libc6_libs = [os.path.basename(l)
+ for l in repo.Repo.get_package_libraries('libc6')]
@kyrofa

kyrofa Oct 18, 2017

Member

get_package_libraries definitely includes more than just libs. Will that cause issues, here?

Collaborator

sergiusens commented Oct 19, 2017

Collaborator

sergiusens commented Oct 19, 2017

Collaborator

kalikiana commented Oct 19, 2017

For the record, hitting the timeout again here test_rust_plugin.RustPluginTestCase.test_cross_compiling ... The job exceeded the maximum time limit for jobs, and has been terminated.

Member

kyrofa commented Oct 20, 2017

Ah ha, once I removed the LD_LIBRARY_PATH from bin/snapcraft-classic I was actually able to hit this error on Trusty, and this PR fixes it.

Collaborator

kalikiana commented Oct 23, 2017

@kyrofa What do you mean when you say "this error" here? Would it be worth linking a bug in a comment here? Or just a comment pointing out the problem?

Nice. So simple I got a bit suspicious at first :-D

Collaborator

sergiusens commented Oct 23, 2017

#1635 was the other problem which caused initial suspicions on this PR.

kyrofa approved these changes Oct 23, 2017

This is A) necessary and B) works, so +1 from me! The get_package_libraries method probably needs a refactor, but it causes no harm here.

@sergiusens sergiusens merged commit 1b8ea95 into snapcore:master Oct 23, 2017

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@sergiusens sergiusens deleted the sergiusens:libc6-and-friends branch Oct 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment