SHARE
TWEET

Untitled

a guest Jul 20th, 2019 75 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. klark ~ # eselect news read 28
  2. 2019-06-05-amd64-17-1-profiles-are-now-stable
  3.   Title                     amd64 17.1 profiles are now stable
  4.   Author                    Michał Górny <mgorny@gentoo.org>
  5.   Posted                    2019-06-05
  6.   Revision                  3
  7.  
  8. A new set of 17.1 amd64 profiles has been added to the Gentoo
  9. repository in Dec 2017.  These profiles switch to a more standard
  10. 'no SYMLINK_LIB' multilib layout, and require explicit migration as
  11. described below.  They are considered stable at the moment, and we would
  12. like to request all users to upgrade their systems.  The old profiles
  13. will be deprecated in the near future.
  14.  
  15. In the new profiles, the lib->lib64 compatibility symlink is removed.
  16. 64-bit libraries need to be installed directly to lib64.  /lib
  17. and /usr/lib become real directories, that are used for cross-arch
  18. and native non-library packages (gcc, clang) and 32-bit libraries
  19. on the multilib profile (which improves compatibility with prebuilt x86
  20. packages).
  21.  
  22. Migration from both 13.0 and 17.0 profiles is supported.  In case
  23. of the former, reading the news item for 17.0 upgrade [1]
  24. is recommended.
  25.  
  26. The migration is performed using app-portage/unsymlink-lib tool.
  27. The following steps can be used to upgrade your system:
  28.  
  29. 1. Sync and upgrade your system to the newest package versions
  30.    to reduce the risk of issues.
  31.  
  32. 2. If you are still running a 13.0 profile, select gcc 6.4.0 or later
  33.    as the system compiler, source /etc/profile and reinstall libtool:
  34.  
  35.      # gcc-config -l
  36.      [1] x86_64-pc-linux-gnu-5.5.0 *
  37.      [2] x86_64-pc-linux-gnu-8.3.0
  38.      # gcc-config 2
  39.      # . /etc/profile
  40.      # emerge -1v libtool
  41.  
  42. 3. Install the tool:
  43.  
  44.      # emerge -1v app-portage/unsymlink-lib
  45.  
  46. 4. Run 'unsymlink-lib --analyze' and check the output for obvious
  47.    mistakes.  If you need to perform any changes to the system, remember
  48.    to run 'unsymlink-lib --analyze' again afterwards.
  49.  
  50. [past this point do not call emerge or modify /usr manually]
  51.  
  52. 5. This is a very good time to make a backup.
  53.  
  54. 6. Run 'unsymlink-lib --migrate'.  You can add '--pretend' first to see
  55.    what is going to happen.
  56.  
  57. 7. Reboot your system.  Check if important programs work.
  58.    In particular, verify that e.g. 'emerge --info' works (but do not
  59.    install anything).  If you hit any serious problems, you can use
  60.    'unsymlink-lib --rollback' to revert the changes and return to
  61.    step 4.
  62.  
  63. 8. Run 'unsymlink-lib --finish'.  You can add '--pretend' first to see
  64.    what is going to happen but note that you're going to see a very long
  65.    list of files to remove.
  66.  
  67. 9. Switch the profile, e.g.:
  68.  
  69.      # eselect profile set default/linux/amd64/17.1/desktop
  70.  
  71. [at this point you can start using emerge again]
  72.  
  73. 10. Rebuild the toolchain:
  74.  
  75.       # emerge -1v sys-devel/gcc:8.3.0
  76.       [ repeat for other slots you will be using ]
  77.       [ if you are upgrading from 13.0 profile, also: ]
  78.       # emerge -1v sys-devel/binutils
  79.       # emerge -1v sys-libs/glibc
  80.  
  81. 11. If you are using a multilib profile, rebuild all 32-bit packages.
  82.     This can be done using:
  83.  
  84.       # emerge -1v --deep /lib32 /usr/lib32 /usr/lib/llvm/*/lib32
  85.  
  86.     Alternatively, if you are switching from one of the 13.0 profiles
  87.     you can rebuild all packages as detailed in the 17.0 news item:
  88.  
  89.       # emerge -ev @world
  90.  
  91. 12. Once the last 32-bit package is rebuilt, your package manager
  92.     should remove the orphaned /lib32 and /usr/lib32 symlinks.  If that
  93.     does not happen, remove them manually:
  94.  
  95.       # rm /lib32 /usr/lib32
  96.  
  97. For known issues, please see bug #506276 [2].  If you have any problems
  98. with the new profiles or the migration procedure, please report a bug
  99. and make it block the tracker.
  100.  
  101. For more information on the layout, please see the wiki article
  102. on AMD64 multilib layouts [3].
  103.  
  104. [1] https://gentoo.org/support/news-items/2017-11-30-new-17-profiles.html
  105. [2] https://bugs.gentoo.org/506276
  106. [3] https://wiki.gentoo.org/wiki/Project:AMD64/Multilib_layout
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top