[Stable Update] 2018-06-07 - Kernels, Systemd, Pamac, Octopi, Rebuilds

update
stable

#1

Hi community,

Welcome to another stable update. So what do we have with this one?

  • Systemd got some more fixes and updates
  • Pamac v6.4 introduces an option to auto download updates (disabled by default) and using --search on pamac-manager will start Pamac directly in search-mode.
  • Fixes to Octopi
  • linux417 got finally released
  • Usual upstream rebuilds

We hope with all these changes Manjaro to be more efficient for you all.


If you are curious about the latest state of development for the upcoming Manjaro-Illyria 18.0 release, you now have the opportunity to download a beta-build of Manjaro-Xfce 18.0 including the latest xfce-gtk3 packages aswell as our most recent styling efforts:


Latest information about the intel-cpu-bug risk and our efforts can be found here.


Current supported Kernels

  • linux316 3.16.56
  • linux318 3.18.112 [EOL]
  • linux41 4.1.51
  • linux44 4.4.135
  • linux49 4.9.106
  • linux414 4.14.48
  • linux415 4.15.18 [EOL]
  • linux416 4.16.14
  • linux417 4.17.0
  • linux414-rt 4.14.40_rt30
  • linux416-rt 4.16.12_rt5

Package Updates (Mon Jun 4 06:33:51 CEST 2018)

  • stable community x86_64: 873 new and 859 removed package(s)
  • stable core x86_64: 20 new and 20 removed package(s)
  • stable extra x86_64: 142 new and 144 removed package(s)
  • stable multilib x86_64: 5 new and 6 removed package(s)

A detailed list of all package changes may be found here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:


Boot failure. PC does not start
#2

Known issues and solutions

This is a wiki post; please edit as necessary.


Kernel 4.9 issues

Seems on rare conditions you may face a faulty boot with linux49. It results in messages similar like this: <module> likely not compiled with -mcmodel=kernel. Also you will land in the emergency console.

We recommend to install at least another kernel as backup. You may follow this post to recover. v4.9.105 is known to be working.


Items from previous update sets

:: alpm-octopi-utils: installing “pacman” (5.1.0-2) breaks the dependency with «pacman <5.1»

Make sure your mirrors are up-to-date. All package management tools should be compatible with pacman 5.1


:: ffmpeg2.8: installing x265 (2.8-1) breaks dependency ‘libx265.so=151-64’

ffmpeg2.8 is no longer in the repos. Remove it, and if you need it, rebuild/reinstall it from the AUR.


gcc54 and gcc5 are in conflict

For those using CUDA, if this error comes up, run the update from terminal
sudo pacman -Syyu
and type YES to replace gcc5 with gcc54


Extension “Workspace to Dock” is bugged

Be careful like there is a bug if you use the Extension “Workspace to Dock”. You need to update/install this version in ~/.local/share/gnome-shell/extensions/ for not have desktop freeze after reboot : https://github.com/passingthru67/workspaces-to-dock/archive/master.zip

Thanks for nabd who have solved this issue : [Testing Update] 2018-05-11 - Kernels, GCC8, Gnome 3.28.2, Cinnamon, KDE Apps 18.04.1, LibreOffice


I see a lot of pacnew files

Well, there is no manual intervention needed for pacnew files coming from filesystem package. The best thing you can do is, do nothing.

Never, ever, ever, ever, ever merge the pacnew file for /etc/{passwd,shadow,gshadow,group}, unless you want to make the new comments match aesthetically with your in-use user accounts database. The only practical difference that merging can ever cause is to accidentally delete users or mangle the whole file’s syntax and render your computer maybe unbootable.

More advice in this regard you may find here.


Nvidia drivers and Fermi support

With the current Nvidia driver release v396.24, support for the old Fermi cards got dropped. Please switch either over to Nouveau driver or downgrade to v390xx driver series.

Bumblebee users follow:

sudo mhwd -r pci video-hybrid-intel-nvidia-bumblebee
sudo mhwd -i pci video-hybrid-intel-nvidia-390xx-bumblebee

Normal users follow:

sudo mhwd -r pci video-nvidia
sudo mhwd -i pci video-nvidia-390xx

To switch to opensource drivers do:

sudo mhwd -r pci video-nvidia
sudo mhwd -i pci video-linux


Changes made to Glibc

The new version of glibc removes support for NIS and NIS+. The default /etc/nsswitch.conf file provided by filesystem package already reflects this change. Please make sure to merge pacnew file if it exists prior to upgrade.

NIS functionality can still be enabled by installing libnss_nis package. There is no replacement for NIS+ in the official repositories.


Changes made to PAM

pam 1.3.0-2 no longer ships pam_unix2 module and pam_unix_*.so compatibility symlinks. Before upgrading, review PAM configuration files in the /etc/pam.d directory and replace removed modules with pam_unix.so. Users of pam_unix2 should also reset their passwords after such change. Defaults provided by pambase package do not need any modifications.

Check grep -rn 'pam_unix[2_]' /etc/pam.d, if no output, you need to do nothing.


Samba units renamed

Note: In samba 4.8.0-1, the units were renamed from smbd.service and nmbd.service to smb.service and nmb.service.

To provide basic file sharing through SMB start/enable smb.service and/or nmb.service services. See the smbd(8) and nmbd(8) man pages for details, as the nmb.service service may not always be required.


Directory permissions differ

Directory permissions differ on /var/lib/samba/private/
filesystem: 755 package: 700

sudo chmod 700 /var/lib/samba/private/


Samba - Error 255: net usershare add: cannot convert name “Everyone” to a SID.

Currently there seems to be an issue when using group = sambashare with Samba 4.8.1-1, which is used by default in thesmb.conf provided by Manjaro. Changing it to group = +sambashare or force group = +sambashare resolves this. However, we might fill out a bug report, to see why that is currently needed.

Commenting/removing group = sambashare is also a viable solution.


Long delay for starting Desktop Environment

There’s a bug which is exhausting the entropy pool. This is refilled over time through e.g. disk activity and mouse movement. You can increase the fill rate with a software solution:

sudo pacman -S haveged
sudo systemctl enable haveged
sudo systemctl start haveged

An alternative method if activating the haveged service is not something you want to do is to press the shift key 8-10 times in succession.


#3

Seems everything went smooth. Just pamac showed only around 170 MB download size, which then ended up being around 400 MB. And the progress bar in the GUI was showing wrong info (it was 100% but still a lot of downloads to do.)
EDIT: I am on Manjaro Gnome


#4

Hello,
before 01.06.2018, my system was taking about 4 second to shutdown.
After the updates is taking 30 seconds.
I have not added anything to startup.
I use KDE, stable, kernel-4.14.48-1.
Is there a way to check what proces is taking so much to close ?
I am a newbie.


#5

Post a journal of a previous boot with command

$ journalctl -b -1

Please use the forum’s summary “it’s in the toothweel dropdown in a response window”

[details="Summary"]

[/details]

You can additionaly use ``` on the first line of the pasted text and the last to have it monospaced :slight_smile:


#6

No issues noticed. Multiple XFCE systems, all kernel 4.14 :+1: Thanks guys.


#7

Had file exists conflicts on multiple python3.6 files. Renamed conflict files to *.bak, installed updates, and after successful update, removed the *.bak files.


#8

Did you install or update anything with pip? It’s recommended not to use any other package manager besides pacman as conflicts will happen like that if you do.


#9

I use pacaur. All my pip usage is contained within virtualenvironments, except global updates to pip itself. Which looking back at the logs now, was the package with the errors… d’oh!


#10

No issues observed so far . XFCE system, using kernel 4.17: Thank you.


#11

No issues observed so far. KDE system, using kernel 4.14. Thank you for all the hard work making these updates so smooth.


#12

Working well, smooth update. Thanks Manjaro Team. :smiley:


#13

No issues observed so far. XFCE + kernel 4.14.


#14

I’ve got the same issue - do you know if pacman have alternative packages then?


#15

KDE Plasma, kernel 4.16.14-1. Smooth reboot.

Thanks to all for the update!:wink:


#16

LXQT updated today with no issues.
Another perfect update.
Thanks!


#17

I’ve only just started the upgrade. I’m getting two of everything. :fearful:

Synchronizing package databases...
Starting full system upgrade...

Preparing...
Resolving dependencies...
Checking inter-conflicts...
Downloading...
Downloading manjaro-keyring-20180607-1-any.pkg.tar.xz...
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Upgrading manjaro-keyring (20171027-2 -> 20180607-1)...
==> Appending keys from manjaro.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key 75C1B95A4D9514A57EB2DAE71817DC63CD3B5DF5...
  -> Locally signing key 16DC688DF3EECC72323954237EC47C82A42D53A2...
  -> Locally signing key 76C6E477042BFE985CC220BD9C08A255442FAFF0...
  -> Locally signing key 2D14560CDCE6A75BB186DB758238651DDF5E0594...
  -> Locally signing key B4663188A692DB1E45A98EE95BD96CC4247B52CC...
  -> Locally signing key 04BB537F5BC2D399BFA72F8F17C752B61B2F2E90...
  -> Locally signing key 35B4FF23EA9477582C2A0AF12B80869C5C0102A6...
  -> Locally signing key 77DC01C9971AC3C39A0626F72C089F09AC97B894...
  -> Locally signing key 39F0EC1AE50B37E5F3196F09DAD3B211663CA268...
  -> Locally signing key E4CDFE50A2DA85D58C8A8C70CAA6A59611C7F07E...
  -> Locally signing key 7C89F4D439B2BFACF425107B62443D89B35859F8...
  -> Locally signing key 22C903DE964E6FE321656E318DB9F8C18DF53602...
  -> Locally signing key 5A97ED6B72418199F0C22B23137C934B5DCB998E...
  -> Locally signing key 2C688B52E3FC0144B7484BABE3B3F44AC45EE0AA...
  -> Locally signing key 1E7908935AAB9A00D6B47503363DFFFD59152F77...
  -> Locally signing key 74C2F2CC05A0AB7D859839938934292D604F8BA2...
==> Importing owner trust values...
==> Disabling revoked keys in keyring...
  -> Disabling key FAA6840E8C3FC7F89BEE0DC8AC7AB10BCB6CDD17...
  -> Disabling key 540DE7083B89314CF70EA6F0C1B1AD0DA80EBF3E...
==> Updating trust database...
gpg: next trustdb check due at 2018-06-25
Running post-transaction hooks...
Arming ConditionNeedsUpdate...
Starting full system upgrade...
Resolving dependencies...
Resolving dependencies...
Checking inter-conflicts...
Checking inter-conflicts...
Downloading...
Downloading...
Downloading b43-fwcutter-019-2-x86_64.pkg.tar.xz...
Downloading b43-fwcutter-019-2-x86_64.pkg.tar.xz...
Downloading libsystemd-238.133-1-x86_64.pkg.tar.xz...
Downloading libsystemd-238.133-1-x86_64.pkg.tar.xz...
Downloading jfsutils-1.1.15-5-x86_64.pkg.tar.xz...
Downloading jfsutils-1.1.15-5-x86_64.pkg.tar.xz...
Downloading p11-kit-0.23.12-1-x86_64.pkg.tar.xz...
Downloading p11-kit-0.23.12-1-x86_64.pkg.tar.xz...
Downloading systemd-238.133-1-x86_64.pkg.tar.xz...
Downloading systemd-238.133-1-x86_64.pkg.tar.xz...
Downloading linux414-4.14.48-1-x86_64.pkg.tar.xz...
Downloading linux414-4.14.48-1-x86_64.pkg.tar.xz...

Everything updated OK


#18

i3 wm system with 4.14 kernel.
No issues. Another perfect update.

Thank you!


#19

Got errors while installing python-pip packages

Transaction error

python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/init.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/init.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/basecommand.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/baseparser.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/build_env.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/cache.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/cmdoptions.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/compat.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/configuration.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/download.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/exceptions.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/index.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/locations.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/pep425tags.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/resolve.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/status_codes.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pycache/wheel.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/basecommand.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/baseparser.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/build_env.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/cache.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/cmdoptions.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/init.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/init.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/check.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/completion.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/configuration.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/download.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/freeze.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/hash.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/help.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/install.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/list.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/search.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/show.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/uninstall.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/pycache/wheel.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/check.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/completion.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/configuration.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/download.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/freeze.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/hash.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/help.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/install.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/list.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/search.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/show.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/uninstall.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/commands/wheel.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/compat.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/configuration.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/download.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/exceptions.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/index.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/locations.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/models/init.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/models/pycache/init.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/models/pycache/index.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/models/index.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/operations/init.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/operations/pycache/init.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/operations/pycache/check.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/operations/pycache/freeze.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/operations/pycache/prepare.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/operations/check.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/operations/freeze.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/operations/prepare.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/pep425tags.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/req/init.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/req/pycache/init.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/req/pycache/req_file.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/req/pycache/req_install.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/req/pycache/req_set.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/req/pycache/req_uninstall.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/req/req_file.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/req/req_install.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/req/req_set.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/req/req_uninstall.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/resolve.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/status_codes.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/init.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/init.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/appdirs.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/deprecation.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/encoding.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/filesystem.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/glibc.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/hashes.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/logging.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/misc.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/outdated.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/packaging.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/setuptools_build.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/temp_dir.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/typing.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/pycache/ui.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/appdirs.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/deprecation.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/encoding.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/filesystem.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/glibc.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/hashes.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/logging.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/misc.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/outdated.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/packaging.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/setuptools_build.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/temp_dir.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/typing.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/utils/ui.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/vcs/init.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/vcs/pycache/init.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/vcs/pycache/bazaar.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/vcs/pycache/git.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/vcs/pycache/mercurial.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/vcs/pycache/subversion.cpython-36.pyc’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/vcs/bazaar.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/vcs/git.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/vcs/mercurial.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/vcs/subversion.py’ существует в файловой системе
python-pip: ‘/usr/lib/python3.6/site-packages/pip/_internal/wheel.py’ существует в файловой системе
Обнаружены ошибки, пакеты не обновлены.
=>> Try again? [y/N]:


Unable to update - please help
#20

You have to see why the files already exist in your filesystem. Most likely you used pip and some point and also pacman. Check for example with pacman -Qo /usr/lib/python3.6/site-packages/pip/_internal/vcs/git.py. If no package is displayed owning that file you may copy the list of existing files to a text document and add sudo rm -v <path/to/the/file> and run the content in a terminal.


Failed to commit transaction due to Python conflict
Python code run - segmentation fault core dumped