FTBFS on Utopic, all architectures
Bug #1378819 reported by
Robie Basak
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libecap (Ubuntu) |
Fix Released
|
Undecided
|
Robie Basak |
Bug Description
Symbols file mismatch: https:/
The attached patch fixes it, but I'm not comfortable uploading since I don't see how I can verify that these symbols aren't part of the public interface.
If we just update the symbols file to match without checking, then what's the point of having the symbols file present at all?
Related branches
Changed in libecap (Ubuntu): | |
assignee: | nobody → Robie Basak (racb) |
status: | Triaged → In Progress |
tags: | added: patch |
To post a comment you must log in.
13:53 <rbasak> doko: sorry, I'm still not comfortable with this. I don't really
follow the bigger picture of how to determine that these symbols really aren't n
eeded.
13:53 <rbasak> The package includes all the headers, which makes it awkward.
13:54 <rbasak> doko: if you're happy with my diff, then I guess I can upload tha
t.
13:54 <rbasak> Or else, I don't really see the point of having the symbols file
in the first place if we just change it to accomodate when needed.
14:20 <doko> rbasak, agreed for c++ symbols files, but c symbol files should be fine
14:20 <doko> go ahead with the upload
14:20 <doko> my libabigail upload is still stuck in NEW
14:22 <rbasak> doko: OK - you mean an upload to drop this c++ symbols file entirely, or just to mark the disappearing symbols as optional as in my diff?
14:23 <doko> well, optional shouldn't hurt from my point of view
14:23 <rbasak> OK
14:23 <rbasak> Thanks