Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 829127 - dev-libs/libphonenumber: causes many apps to fail to compile after protobuf update
Summary: dev-libs/libphonenumber: causes many apps to fail to compile after protobuf u...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo KDE team
URL: https://issuetracker.google.com/issue...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-13 23:36 UTC by Maciej Mrozowski
Modified: 2021-12-16 13:55 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Example failed compilation after protobuf update, for kde-apps/kitinerary (build.log,272.95 KB, text/plain)
2021-12-13 23:36 UTC, Maciej Mrozowski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Mrozowski gentoo-dev 2021-12-13 23:36:18 UTC
Created attachment 758836 [details]
Example failed compilation after protobuf update, for kde-apps/kitinerary

C++ variant of libphonenumber installs generated .pb.h files instead of provide .proto file only. .pb.h are specific to protobuf version and will not work with other version.
So when protobuf is updated, all packages depending on .pb.h, due to this injected dependency, won't build until libphonenumber it-self is reinstalled.
Comment 1 Maciej Mrozowski gentoo-dev 2021-12-13 23:38:20 UTC
This is really upstream bug that we can do little about as installed .pb.h is shockingly part of public API.
Creating bug for reference.
Comment 2 Andreas Sturmlechner gentoo-dev 2021-12-14 11:29:12 UTC
dev-libs/libphonenumber should have been rebuilt on protobuf (slot change) update. If it did not before starting compilation of libphonenumber revdeps, then this would be a portage bug, no?
Comment 3 Andreas Sturmlechner gentoo-dev 2021-12-16 13:55:29 UTC
Please reopen after

1) adding emerge --info
2) showing that the issue is not caused by wrong (re-)emerge ordering