Bug 20715

Summary: Error in file name for lib64boost-* and libboost-*
Product: Mageia Reporter: Stig-Ørjan Smelror <smelror>
Component: RPM PackagesAssignee: Shlomi Fish <shlomif>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: MGA5TOO
Source RPM: boost-1.60.0-6.mga6 CVE:
Status comment:

Description Stig-Ørjan Smelror 2017-04-21 17:46:22 CEST 
I tried to install lib64boost-atomic and it couldn't find the package.

urpmi lib64boost-atomic
No package named lib64boost-atomic

When searching for lib64boost, I get the following list.
I thought that the addition of 1.60.0 was cumbersome and not very portable.
It is also the case in Mageia 5 x86_64.

Looks like when there is an update, it'll be named lib64boost-atomic1.60.1 (for example).

Is there a special reason why these packages are named as such?

urpmq -y lib64boost                                                 1 ↵
lib64boost-graph-mpi1.60.0
lib64boost-graph-mpich1.60.0
lib64boost-mpi-python1.60.0
lib64boost-mpich-devel
lib64boost-mpich-python1.60.0
lib64boost-mpich1.60.0
lib64boost-openmpi-devel
lib64boost-openmpi1.60.0
lib64boost-python3_1.60.0
lib64boost-static-devel
lib64boost_atomic1.60.0
lib64boost_chrono1.60.0
lib64boost_container1.60.0
lib64boost_context1.60.0
lib64boost_coroutine1.60.0
lib64boost_date_time1.60.0
lib64boost_filesystem1.60.0
lib64boost_graph1.60.0
lib64boost_iostreams1.60.0
lib64boost_locale1.60.0
lib64boost_log1.60.0
lib64boost_math1.60.0
lib64boost_prg_exec_monitor1.60.0
lib64boost_program_options1.60.0
lib64boost_python1.60.0
lib64boost_random1.60.0
lib64boost_regex1.60.0
lib64boost_serialization1.60.0
lib64boost_signals1.60.0
lib64boost_system1.60.0
lib64boost_thread1.60.0
lib64boost_timer1.60.0
lib64boost_type_erasure1.60.0
lib64boost_unit_test_framework1.60.0
lib64boost_wave1.60.0
lib64boost_wserialization1.60.0

urpmq -y libboost
libboost-graph-mpi1.60.0
libboost-graph-mpich1.60.0
libboost-mpi-python1.60.0
libboost-mpich-devel
libboost-mpich-python1.60.0
libboost-mpich1.60.0
libboost-openmpi-devel
libboost-openmpi1.60.0
libboost-python3_1.60.0
libboost-static-devel
libboost_atomic1.60.0
libboost_chrono1.60.0
libboost_container1.60.0
libboost_context1.60.0
libboost_coroutine1.60.0
libboost_date_time1.60.0
libboost_filesystem1.60.0
libboost_graph1.60.0
libboost_iostreams1.60.0
libboost_locale1.60.0
libboost_log1.60.0
libboost_math1.60.0
libboost_prg_exec_monitor1.60.0
libboost_program_options1.60.0
libboost_python1.60.0
libboost_random1.60.0
libboost_regex1.60.0
libboost_serialization1.60.0
libboost_signals1.60.0
libboost_system1.60.0
libboost_thread1.60.0
libboost_timer1.60.0
libboost_type_erasure1.60.0
libboost_unit_test_framework1.60.0
libboost_wave1.60.0
libboost_wserialization1.60.0
Marja Van Waes 2017-04-21 19:04:08 CEST

Source RPM: (none) => boost-1.60.0-6.mga6
Whiteboard: (none) => MGA5TOO
Assignee: bugsquad => shlomif
CC: (none) => marja11

Comment 1 Marja Van Waes 2017-04-21 19:06:38 CEST 
Assigning to the registered boost maintainer.
Comment 2 Marja Van Waes 2017-04-21 19:15:16 CEST 
On IRC, in #mageia-dev, I was told that this is as it should be, you can find more information here
https://wiki.mageia.org/en/Libraries_policy

Resolution: (none) => INVALID
Status: NEW => RESOLVED