[SOLVED] pacman & test repository

Hi,
I have two questions:
1) Where should the testing repository be added in the pacman config? Right now the order of my repositories is default:
61 [core]
62 # Add your preferred servers here, they will be used first
63 Include = /etc/pacman.d/mirrorlist
64
65 [extra]
66 # Add your preferred servers here, they will be used first
67 Include = /etc/pacman.d/mirrorlist
68
69 [community]
70 # Add your preferred servers here, they will be used first
71 Include = /etc/pacman.d/mirrorlist
Where in this order would [testing] go? I'm not sure where it should be placed.
2) Is there a way to specifically tell pacman which packages I want to be updated in the testing repository? For example, I do not want Apache to be updated from [testing] but I may want Subversion to be updated from that repository.
Thanks.
Last edited by void.pointer (2008-09-23 18:14:36)

skottish wrote:Testing is listed first in makepkg.conf. On the rare occasions that I've used testing this has worked fine. As far as the second request, I would enable testing, update the database, install the package I was looking for (with its dependencies), then disable testing. You could go through all of the work of IgnorePkg =, but I wouldn't bother.
How about an EnablePkg= ? That would pretty much solve my problem I believe. Why do you mention makepkg.conf? Doesn't it need to be in pacman.conf? I'm confused...
Adding/Removing stuff from a config file everytime I want to update isn't really something I want to do. I'd rather not use [testing] at all in that case. Gentoo can do this, I was hoping Archlinux could as well.
Last edited by void.pointer (2008-09-23 15:49:24)

Similar Messages

//solved // pacman local repository problem / testing vs testing

i have a serious problem with pacman, i hope someone can help me out.
i've tried to create a local repo and made a really stupid mistake by calling it 'testing' (i used repo-add)
now if i try to update the system with -Syu I get a flood of warnings for all my packages being newer than platform core etc
there is obviously a conflict with the usual 'testing' and I couldn't find a way to revert this. repo-remove didn't help either.
is there a way to fix it?
tia
Last edited by JYQ (2013-04-04 10:02:58)

parazyd wrote:Try editing your pacman.conf and remove it.
I tried it already. Didn't help.
jasonwryan, thanks but i have a little experience with pacman. the problem is a confict in the database.
manpages do not cover this.
"Creating & Modifying Packages( Discussion and support regarding building packages with makepkg and ABS)
was a natural choice for the thread because there are people who do the same thing.
Last edited by JYQ (2013-04-04 10:23:30)

[Solved] Pacman "filesystem: /etc/mtab exists in filesystem"

First of all I want to say hello, it's my first post here.
Well, I tried to update my system with pacman -Syu and I got this error.
[diego@snow ~]$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Targets (6): bluez-4.96-3 filesystem-2011.12-2 glibc-2.14.1-4
libldap-2.4.28-1 liboauth-0.9.6-1 xorg-xinit-1.3.1-2
Total Download Size: 0.00 MB
Total Installed Size: 36.11 MB
Proceed with installation? [Y/n]
(6/6) checking package integrity [######################] 100%
(6/6) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
filesystem: /etc/mtab exists in filesystem
Errors occurred, no packages were upgraded.
I already searched for this and I found out that this is common when using the testing repository, but I'm not using it.
Should i delete /etc/mtab? I also tried to reboot a couple of times and nothing changed.
I can still install new packages.
Last edited by tokoro (2011-12-21 03:47:53)

jasonwryan wrote:Read the news on the front page...
Well, that was easy
When upgrading to filesystem-2011.12 there will be a conflict with /etc/mtab.
Install the package as follows:
pacman -S filesystem --force
It is strongly advised to avoid the --force or -f switch as it is not safe. However, in this particular case it is needed as deleting /etc/mtab manually would break pacman.
The reason for the conflict is that the file used to be generated at boot and hence not owned by any package. Now it is a symlink to /proc/self/mounts owned by filesystem. This change means that initscripts no longer requires write access to the rootfs (though other packages might).
Last edited by tokoro (2011-12-21 03:50:21)

[gambas2] Splitted package and testing repository available!

Just following the bug report (http://bugs.archlinux.org/task/19318), now a repository is available to test gambas2 as a splitted package.
The purpose of these packages is that it will allow the possibility to add an archlinux package generator to the gambas2 ide, avoiding to add the full list of gambas2 packages, for only installing a graphical application.
The packages are built from a default archlinux installation, so no need to get testing repository enabled, i686 and x86_64 packages are available. Just add the following lines to your pacman.conf file:
i686
[gambarch]
Server = http://gambarch.toile-libre.org/os/i686
x86_64
[gambarch]
Server = http://gambarch.toile-libre.org/os/x86_64
I hope you will find these useful. I will take a look to add gambas3 splitted svn packages.
++

zodmaner wrote:
neotuli wrote:I'm not so sure what you're talking about. It's up and running smooth
Wow! The migration is finish? Great job guys! The migration from CVS to SVN is a very large undertaking and it's great to see that you guys have finally made it. Congrats guys.
This is great news indeed! Thanks for informing us about this, neotuli.
neotuli wrote:And yeah... we see the out of date flags, we even get a little spam every time you click one of them... but we're only human.
Don't worry, we understand you.
not quite..its seems community is going to take a bit longer got left behiend

Do you use test repository?

I am wondering how many users are really using test repository when upgrading. It's not the first repo by default (current will be the first).

I wanted to test evolution 2.0 but the trouble caused when trying to install, I am concluding testing is for those who plan to do it, not for "I use it when there's a specific package i want".
For one or two individual packages its fine, but not when required many dependency packages. Option -S requires to tag both current and extra thereby not accessible to install any dependency packages if required by the test package. Also option -Su doesn't work... confused by testing's own dep. packages.
I don't know if there is a way how to go around having both current and testing without having more trouble configuring pacman than doing the actual testing. :?: The testing configure in pacman has to be changed if we want to engourage users to test. Would it be possible to have in pacman script some kind of "IF and ELSE" detecting if a package is in both current/extra and testing?

Testing repository

Hey guys. I just started messing with Arch (came from Gentoo) and so far I'm impressed. I'm curious about the testing repository, though. I don't want this to be a testing system, but there are a couple of updates in testing I would like. Is it possible to selectively pull packages out of testing with pacman or is it an all or nothing? Would I just be better off building from source until it moves into one of the other repos?
Thanks
-mS

Yes, you can, but it's not recommended. The packages in testing are built against other packages that may be in testing so installing single packages from testing has the potential to break things. To do this, however, you can enable the testing repo at the BOTTOM of your /etc/pacman.conf, then install testing packages via pacman -S testing/packagename.

Problem creating unit testing repository (and workaround)

I tried to create the unit testing repository with a user that had all the required system privileges granted through a different role other than RESOURCE and CONNECT roles, and who wasn't explicitely granted CREATE VIEW, but inherited it through the custom role. However the check in SQL Developer is explicitely for the RESOURCE and CONNECT roles (regardless of what privileges they have granted to them in whichever database version past, present or future) and for CREATE VIEW privilege granted direct to the user:
SELECT DECODE (roles.required_role_count + privs.required_priv_count,
               3, 1,
               0)
          AS basic_privs_granted
FROM (SELECT COUNT (*) AS required_role_count
          FROM user_role_privs
         WHERE granted_role IN ('CONNECT', 'RESOURCE')) roles,
       (SELECT COUNT (*) AS required_priv_count
          FROM USER_SYS_PRIVS
         WHERE privilege IN ('CREATE VIEW')) privsI found this SQL contained within the sqldeveloper/extensions/oracle.sqldeveloper.unit_test.jar in an XML file: oracle/dbtools/unit_test/manage_user/UserSql.xml and replaced the SQL with one that actually checks for the specific system privileges:
SELECT DECODE (required_sys_priv_count,
               10, 1,
               0)
          AS basic_privs_granted
FROM
       (SELECT COUNT(*) AS required_sys_priv_count FROM
         (SELECT privilege
            FROM role_sys_privs
           WHERE privilege IN ('CREATE CLUSTER','CREATE INDEXTYPE','CREATE OPERATOR','CREATE PROCEDURE','CREATE SEQUENCE','CREATE SESSION','CREATE TABLE','CREATE TRIGGER','CREATE TYPE','CREATE VIEW')
          UNION
          SELECT privilege
            FROM user_sys_privs
           WHERE privilege IN ('CREATE CLUSTER','CREATE INDEXTYPE','CREATE OPERATOR','CREATE PROCEDURE','CREATE SEQUENCE','CREATE SESSION','CREATE TABLE','CREATE TRIGGER','CREATE TYPE','CREATE VIEW')))This enabled me to bypass that check when creating the respository. I don't know if all these privileges are actually required by the unit testing repository or not, so maybe the above list can be reduced...
Edited by: RDB on Mar 1, 2013 2:24 PM

Hi Sai Vineeth,
First of all, I appreciate your elaborate way of framing the question. That itself helps others to comment.
On the first two questions, I am sure you'll be able to follow the answers provided and take care of your concerns.
On your question 3), an additional piece of information that should bring smile to you
Whether the Test is to happen in DEV or QAS or whatever 'System Role' is dependent on the Test Plan.
So, if you have two distinct Test Plans, one for Unit Tests and the other for Integration Tests, which should be the case, as usual, you can certainly point the System Role to DEV or QAS as required.
Feel free to pose any other query as well.
Best regards,
Srini

Test Repository - Use of our own business process model as structure

We want to use our own business process model as structuring element in the test repository.
I entered my hierarchy by the transaction STWBM using environment/application hierarchy / Customer.
But my hierarchy is not visible in the test repository. Instead, there is always the SAP hierarchy.
How can I use my hierarchy in the test repository?

I have the same problem.
We are new on using the solution manager to do the test.
Now we want to put all the test cases (manual) in the test repository, and in other time link they to the other projects.
But the question is: How can i storage the test case in the repository to garantee when I do a new project I dont forget any test case needed from the repository?

ODI, restoring version in Test Repository - Missing Reference

Hi all,
In my Development repository I removed a column from a table, to do that I was forced to remove any mapping to that column in my interfaces. After that I created a new version of my Models and Project folder. I restore the newest version (Model and Project) into my Test Repository and I saw that the Interfaces that use the table I have changed had the exclamation mark, this means that I have missing references. The problem is that I don't have the column on the source/target tables in any of them and in the table neither.
It's weird, I went to see the ODI Work Rep metadata and saw that in the SNP_OBJ_TRACE my table is listed with the tag "Excluded Table" in ERR_MESS column. I saw the SNP_MISSING_REF and the field that I removed from the table are listed there.
But after that, I ran the Interface's Scenario and it's all ok!
Anyone knows why this happens?
Thank you,

That is about architecture....
why to have 2 codes? You will take the risk of distincts versions of code to the same process.
Unfortunately I never saw ODI working with 2 dev repository with the same code... only with distinct process.
In thery, the code at test couldn't be changed. Only at development instance.

Enabled the testing repository, is it safe to disable it now?

So, i have noticed that the new KDE packages are available in the Testing repo.
I enabled testing, updated my KDE.
I don't need the testing repository anymore.
Can i disable it?
Or i should have waited until the packages were moved to Extra?
Thanks in advance.

Disabling it shouldn't be a problem.

[Solved] pacman -Syyu sync's repository and then repoistory.db

For instance I run 'pacman -Syyu' and it will then sync core, core.db, extra, etra.db and so on a so forth for all the repo's in my pacman.conf. It did not sync the .db on my last install which was up to date unitl I just did a fresh install using the archboot iso. I looked through the pacman.conf a few times and did not see anything obvious wrong to me. <-- not saying much
I searched this section of the forum going back about 2 months figuring it has to do with signatures and found nothing. So i believe it means that either a) my last setup was incorrect. b) My searching skills are lacking.
If this is normal that is fine, it doesn't bother me, was just curous about it.
Cheers.
Last edited by doug piston (2012-07-27 04:52:08)

Sure and I apologize for the delay and not includung this information to begin with.
┌─[jarvis][watson][~]
└──╼ sudo pacman -Syyu
Password:
:: Synchronizing package databases...
core 107.7 KiB 146K/s 00:01 [-----------------------------------------------------------------------------------] 100%
core.sig 4.2 KiB 44.9K/s 00:00 [-----------------------------------------------------------------------------------] 100%
extra 1408.6 KiB 547K/s 00:03 [-----------------------------------------------------------------------------------] 100%
extra.sig 4.2 KiB 44.6K/s 00:00 [-----------------------------------------------------------------------------------] 100%
community 1765.5 KiB 762K/s 00:02 [-----------------------------------------------------------------------------------] 100%
community.sig 4.2 KiB 42.5K/s 00:00 [-----------------------------------------------------------------------------------] 100%
multilib 90.6 KiB 148K/s 00:01 [-----------------------------------------------------------------------------------] 100%
multilib.sig 4.2 KiB 45.6K/s 00:00 [-----------------------------------------------------------------------------------] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
┌─[jarvis][watson][~]
└──╼ 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/
HoldPkg = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
#UseDelta
#TotalDownload
CheckSpace
#VerbosePkgLists
ILoveCandy
# 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 = Optional TrustedOnly
# 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]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
[core]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
[extra]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
#[community-testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
[community]
SigLevel = PackageRequired
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]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
[multilib]
SigLevel = PackageRequired
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
Also I was wrong it isn't repository.db but actually repository.sig

[SOLVED] Pacman and a WebDAV(s) repository

Hi together,
i tried to set up a private repository using WebDAV (instead of http/ftp) but it did'nt work.
I cannot find anything about using pacman together with WebDAV.
The only solution I see, is using davfs2 and mount the repository locally.
Am I doing something wrong or is WebDAV simply not supported by pacman?
Thanks!
Edit: Not possible - closed
Last edited by float (2013-02-25 07:53:03)

I'm kind of in the same case:
I did my usual
pacman -Syu
some days ago, and got the following error:
error: failed to commit transaction (invalid or corrupted package)
qt-4.5.3-2-i686.pkg.tar.gz is invalid or corrupted
Errors occurred, no packages were upgraded.
I did a
pacman -Scc
which cleared the cache, and proceeded to do another pacman -Syu, which ended in the same issue and same error message.
I'm suspecting the repo (chile arch repo) is/was for some time somehow out of sync (?), and would keep on doing the same thing but I wanted to first check here for any suggestion. It's also bothersome because I had a large number of package to upgrade after the pacman -Syu and clearing the cache means having to download everything over again...
On top of it, it's preventing me to upgrade at all (as it exits in error).
Thanks!

[SOLVED] Pacman "config file could not be read" error during Arch ins

I've been attempting to get Arch setup for a while now, and after having some trouble with partitions, my wireless connecting, and setting up repos and mirrors, which the Wiki helped me solve, I've hit a bigger bump. While updating the system using pacman as the Beginners Guide says to do, I get errors when I try to continue the update process as follows :
btw: I'm typing this on a laptop next to my computer
[root@McArch~]# pacman -Syu
error: config file /etc/pacman.d/core could not be read
error: config file /etc/pacman.d/extra could not be read
error: config file /etc/pacman.d/community could not be read
:: Synchronizing package databases . . .
error: failed to updated core (unexpected error)
error: failed to updated extra (unexpected error)
error: failed to updated community (unexpected error)
error: failed to synchronize any databases
Any tips as to whats going on? I've tried to created said files, and even insert mirrors into the file, like in the /etc/pacman.d/mirrorlist file but this doesn't seem to help
Last edited by Windfinder (2008-09-29 20:43:29)

Glad you got it working.
I'm not sure what happened in your install but I just finished using an old 2007.08 iso and pacman first starts out with /etc/pacman.d/core, etc/pacman.d/extra, /etc/pacman.d/community ... etc., but I never had your problem when I did the #pacman -Syu after initial install reboot. The pacman update removes the above mentioned repos and replaces them with a single /etc/pacman.d/mirrorlist. You must have messed up an initial config file somehow as I couldn't get the same errors you got. It looks like you had your /etc/pacman.conf file messed up somehow and when you pointed it to the mirrorlist it could finally work properly. I'll just include my /etc/pacman.conf file and /etc/pacman.d/mirrorlist so you can compare. NB* these are from my x86_64 so for 32 bit machines i686 would replace x86_64 in the files.
# /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
HoldPkg = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#XferCommand = /usr/bin/curl %u > %o
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options (all disabled by default)
#NoPassiveFtp
#UseSyslog
#ShowSize
#UseDelta
#TotalDownload
# 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
# 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.
# Testing is disabled by default. To enable, uncomment the following
# two 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]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
[extra]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
[community]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs
/etc/pacman.d/mirrorlist
# Arch Linux repository mirrorlist
# North America
# - United States
Server = http://mirror.neotuli.net/arch/$repo/os/x86_64
Server = http://holmes.umflint.edu/archlinux/$repo/os/x86_64
Server = http://archlinux.unixheads.org/$repo/os/x86_64
Server = ftp://ftp.archlinux.org/$repo/os/x86_64
Server = ftp://locke.suu.edu/linux/dist/archlinux/$repo/os/x86_64
Server = ftp://ftp.gtlib.gatech.edu/pub/linux/distributions/archlinux/$repo/os/x86_64
Server = ftp://mirror.cs.vt.edu/pub/ArchLinux/$repo/os/x86_64
Server = http://mirrors.easynews.com/linux/archlinux/$repo/os/x86_64
Server = ftp://ftp.ibiblio.org/pub/linux/distributions/archlinux/$repo/os/x86_64
Server = http://mirror.rit.edu/archlinux/$repo/os/x86_64
Server = http://mirror.umoss.org/archlinux/$repo/os/x86_64
# - Canada
Server = ftp://mirror.csclub.uwaterloo.ca/archlinux/$repo/os/@carch
Well it was an interesting way to kill 30+ minutes.

[solved] pacman broken after "pacman -Syyu" excluding pacman

Hi forums,
I use arch x86_64, yaourt and the testing and multilib repositories.
A full system upgrade doing "yaourt -Syyu" didn't work, because pacman had an unfulfilled dependancy which I don't recall, but it was about a normal and a multilib version: I probably have the multilib version of a library installed, which has not been updated to the version required by pacman yet.
So I thought it would be perfectly fine to exclude pacman from this system upgrade by choosing "manually" from the options given by "yaourt -Syyu" and commented pacman.
The upgrade then went fine except for the two final lines:
package-query: error while loading shared libraries: libarchive.so.2: cannot open shared object file: No such file or directory
testdb: error while loading shared libraries: libarchive.so.2: cannot open shared object file: No such file or directory
Now everytime I try to use pacman, I get this error:
pacman: error while loading shared libraries: libarchive.so.2: cannot open shared object file: No such file or directory
Do you know how to solve this?
Thanks in advance
xiliyi
Last edited by xiliyi (2012-01-05 09:49:23)

ngoonee wrote:Actually (even without cower), makepkg will tell you what dependencies are missing when you try and compile an AUR package. In fact, -s will install them for you (unless they're from the AUR, in which case you have to download/makepkg that package first).
Actually, I was more concerned about updates for packages from AUR. yaourt would handle AUR packages as if they were in a repository, and update them, solving dependency problems.
Now what I fear is, that if some regular library gets an update, it may not updated on my system in the first place, because pacman only sees that the older version is needed for the AUR software, but is not capable of updating the AUR package (which works with the new library version) automatically. So updates will break some software unless I remove it first and install the latest version manually.

(SOLVED) Pacman error: GPGME does not exist

Hi, I have also just been struck with the same issue - a broken pacman (and for no reason that I can fathom). Was working perfectly yesterday and all I did that wan't usual was to uninstall clamav.
Anyway, I have read this post and done a pacman -Syy, which upgraded core and archlinuxfr only. I then ran pacman -Syu and received this:
[grant@ARCH ~]$ sudo pacman -Syy
[sudo] password for grant:
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
:: Synchronizing package databases...
error: failed retrieving file 'core.db' from mirror.aarnet.edu.au : Connection time-out
core 106.2 KiB 353K/s 00:00 [######################] 100%
error: GPGME error: No data
error: failed to update extra (invalid or corrupted database (PGP signature))
error: GPGME error: No data
error: failed to update community (invalid or corrupted database (PGP signature))
error: GPGME error: No data
error: failed to update multilib (invalid or corrupted database (PGP signature))
archlinuxfr 30.3 KiB 81.9K/s 00:00 [######################] 100%
error: database 'extra' is not valid (invalid or corrupted database (PGP signature))
error: database 'community' is not valid (invalid or corrupted database (PGP signature))
error: database 'multilib' is not valid (invalid or corrupted database (PGP signature))
[grant@ARCH ~]$
Should I do a reinstall of pacman using the CD? I know this is clumsy, but anything I have missed?
Last edited by mcduling (2012-12-03 06:43:56)

Here is my pacman.conf in separate screens:
GNU nano 2.2.6 File: /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/
HoldPkg = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
GNU nano 2.2.6 File: /etc/pacman.conf
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
#UseDelta
#TotalDownload
CheckSpace
GNU nano 2.2.6 File: /etc/pacman.conf
#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 = Optional TrustedOnly
# 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
GNU nano 2.2.6 File: /etc/pacman.conf
# - 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]
GNU nano 2.2.6 File: /etc/pacman.conf
#[testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
[core]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
[extra]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
#[community-testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
[community]
SigLevel = PackageRequired
GNU nano 2.2.6 File: /etc/pacman.conf
[community]
SigLevel = PackageRequired
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]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
[multilib]
#SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
[archlinuxfr]
Server = http://repo.archlinux.fr/$arch
# An example of a custom package repository. See the pacman manpage for
GNU nano 2.2.6 File: /etc/pacman.conf
# 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

[SOLVED] pacman & test repository

Similar Messages

Maybe you are looking for