ArchThis Forum is for the discussion of Arch Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi: In the Arch Linux repository (https://www.archlinux.org/packages/?q=libc.so.6), the only thing that can be searched for is the name of a package? Or can one also search by the name of a component?
Hi: In the Arch Linux repository (https://www.archlinux.org/packages/?q=libc.so.6), the only thing that can be searched for is the name of a package? Or can one also search by the name of a component?
It clearly says “keywords” - that’s not (only) the package name.
Why don't you just test it? Took me about a minute to figure it out. Takes much less bandwidth than asking here on the forums.
I asked because the engine can't find "libc.so.6", which is really inconvenient to me in view of the following notification I got:
Code:
root@darkstar~# mount -tauto /dev/sda1 /usb
/sbin/mount.ntfs: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libfuse.so.2)
root@darkstar~#
That is not the name of the package, but in your defense, it's not immediately obvious what the package name is. I "think" it's glibc based on a. google of "libc.so.6"
I find that sevendogsbsd kind of contradicts ondoho. Can the engine at https://www.archlinux.org/packages/ find the name of a package component? According to ondoho it can. But from sevendogsbsd's post it seems it cannot.
I am not saying the search can or cannot find anything, only that the file noted by OP is not the name of the package. I misunderstood the reason for the post.
Last edited by sevendogsbsd; 03-21-2020 at 07:44 PM.
It clearly says “keywords” - that’s not (only) the package name.
Why don't you just test it? Took me about a minute to figure it out. Takes much less bandwidth than asking here on the forums.
I've never searched the packages web page like that I don't think.
If you have arch installed:
Code:
pacman -Ss editor
core/ed 1.16-1
A POSIX-compliant line-oriented text editor
core/libedit 20191231_3.1-1 [installed]
Command line editor library providing generic line editing, history, and
tokenization functions
core/nano 4.8-1 [installed]
Pico editor clone with enhancements
core/sed 4.8-1 (base-devel) [installed]
GNU stream editor
core/vi 1:070224-4 [installed]
The original ex/vi text editor
extra/alacarte 3.36.0+0+g7b5fc64-1
Menu editor for gnome
extra/dconf-editor 3.36.0-1 (gnome-extra)
dconf Editor
...
root@darkstar~# pacman -Qo /usr/lib/libc.so.6
/usr/lib/libc.so.6 is owned by glibc 2.27-3
and
Code:
pacman -S glibc
Now I get
Code:
root@darkstar~# pacman -Qo /usr/lib/libc.so.6
/usr/lib/libc.so.6 is owned by glibc 2.29-1
which is greater than the version I was asked for by the OS, and can mount sda1. I learned this from you. Thanks.
Unfortunately every time I do a general upgrade of the OS with pacman I get an error and everything on the hard disk is left as before. I posted about this here but no definitive answer was provided.
bill@darkstar~$ cat /etc/pacman.conf
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives
#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
#HookDir = /etc/pacman.d/hooks/
HoldPkg = pacman glibc
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta = 0.7
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
#Color
#TotalDownload
CheckSpace
#VerbosePkgLists
# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required
# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.
#
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
#[testing]
#Include = /etc/pacman.d/mirrorlist
[core]
Include = /etc/pacman.d/mirrorlist
[extra]
Include = /etc/pacman.d/mirrorlist
#[community-testing]
#Include = /etc/pacman.d/mirrorlist
[community]
Include = /etc/pacman.d/mirrorlist
# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.
#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist
#[multilib]
#Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
bill@darkstar~$
Code:
root@darkstar~# pacman -Syu
:: Synchronizing package databases...
core 135.6 KiB 26.4K/s 00:05 [##############################################] 100%
extra 1643.3 KiB 21.9K/s 01:15 [##############################################] 100%
community 4.8 MiB 18.5K/s 04:28 [##############################################] 100%
:: Starting full system upgrade...
:: Replace ca-certificates-cacert with core/ca-certificates? [Y/n] Y
:: Replace libsystemd with core/systemd-libs? [Y/n] Y
:: Replace libx264 with extra/x264? [Y/n] Y
:: Replace qca-qt5 with extra/qca? [Y/n] Y
:: Replace xorg-mkfontdir with extra/xorg-mkfontscale? [Y/n] Y
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing xorgproto (2019.2-2) breaks dependency 'xf86dgaproto' required by libxxf86dga
root@darkstar~#
I don't understand. It's the first time I get this. At other times pacman -Syu was doing a lot of work (above 30m) and then signaled an error.
This is from your link:
Quote:
"Failed to commit transaction (conflicting files)" error
If you see the following error: [1]
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
package: /path/to/file exists in filesystem
Errors occurred, no packages were upgraded.
This is happening because pacman has detected a file conflict, and by design, will not overwrite files for you. This is by design, not a flaw.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
