[SOLVED] Upgrading to Pacman 4.1 - various issues

felipense · 2013-04-05 14:47:19

in my old pacman.conf i have

[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

Should i add SigLevel on the new pacman.conf?

theodoreward · 2013-04-05 15:54:39

dmacblu wrote:

try sudo pacman -R yaourt
sudo pacman -R package-query
then sudo pacman -Syyu
then fix your /etc/pacman.conf file as suggested above then put yaourt back in (if you still want it).

Thank you, this was my issue. I didn't even realize I had yaourt installed, had no idea "package-query" was a package that I could simply remove without breaking something. I'm sure as I continue using Arch this stuff will become second nature, but this issue was not at all obvious to me without reading these forums and trying to skip the lambasting to find a response.

Inxsible · 2013-04-05 15:58:31

theodoreward wrote:

trying to skip the lambasting to find a response.

That's how we roll ! Welcome to Arch !!

Joel · 2013-04-05 16:05:09

thanks, the topic did work for me...

1.- Removed:

pacman -R package-query yaourt

2.- Upgraded system:

pacman -Syu

3.- Renamed /etc/pacman.conf.pacnew

mv /etc/pacman.conf.pacnew /etc/pacman.conf

4.- Ran a new update, to use new pacman's config file

pacman -Syu

5.- Installed again package-query and yaourt
6.- Happy day

tedbell · 2013-04-05 16:31:21

ok thanks all

root · 2013-04-05 17:46:28

@felipense

I don't think so. If you check the .pacnew file you will see that there are, among other changes, two lines added in the package signing part. One of them refers to 'Siglevel' and it is set to required. I presume this can be seen as a 'general option' for package signing instead of it being established for each repository individually as it happened before the 4.1 version.
That is at least how I understand it.

@Joel

I wouldn't recommend moving the .pacnew file that easily. Or at least include an * in your 'guide' that points out the importance of using other means (f.e. vimdiff) to keep user changes which will otherwise be overwritten.

Last edited by root (2013-04-05 17:48:49)

jasonwryan · 2013-04-05 19:45:54

theodoreward wrote:

I didn't even realize I had yaourt installed.

Then you are not running Arch but one of the derivatives like Archbang or Manjaro; which is the very reason they are not supported here...

Joel · 2013-04-05 22:25:08

@root:
Well, I was thinking since we are handling delicate file names, backup is always a default measure.

felipense · 2013-04-06 01:29:13

@binskipy2u

I have the same trouble solved with this:

pacman -Rsc pacman-color 
pacman -Rsc package-query
pacman -Su
mv /etc/pacman.conf  /etc/pacman.conf.backup
mv /etc/pacman.conf.pacnew /etc/pacman.conf
pacman -Su

And then you have to reinstall yaourt.

I don't see the color in the new pacman XD. How is activated?

edit:

@root
yes tnx

Last edited by felipense (2013-04-06 01:32:27)

jasonwryan · 2013-04-06 01:32:14

felipense wrote:

I don't see the color in the new pacman XD. How is activated?

Uncomment it in pacman.conf

felipense · 2013-04-06 01:47:32

@jasonwryan

thanks. Looks really good, and is more easy to read. Like yaourt.

Last edited by felipense (2013-04-06 01:48:19)

Mr.Elendig · 2013-04-06 17:53:00

All the people wrote:

mv /etc/pacman.conf.pacnew /etc/pacman.conf

Please, for the love of all things unholy, stop suggesting this. It is stupid, evil and harmful.

It will overwrite any custom settings for pacman, including repos, package/repo signing etc. It is a bad advice to give, and can possibly cause breakage and security issues.

Please link people to this wiki page instead, or explain straight out what .pacnew files are, and how to deal with them the correct way.

Mr Green · 2013-04-06 18:28:00

jasonwryan wrote:

Then you are not running Arch but one of the derivatives like Archbang or Manjaro; which is the very reason they are not supported here...

ArchBang has never shipped with yaourt and does not come with packer anymore.

MutantJohn · 2013-04-07 03:40:11

Mr.Elendig wrote:

All the people wrote:
mv /etc/pacman.conf.pacnew /etc/pacman.conf
Please, for the love of all things unholy, stop suggesting this. It is stupid, evil and harmful.
It will overwrite any custom settings for pacman, including repos, package/repo signing etc. It is a bad advice to give, and can possibly cause breakage and security issues.
Please link people to this wiki page instead, or explain straight out what .pacnew files are, and how to deal with them the correct way.

So I just used the mv command to fix some stuff I had about an option not being found. It worked out great. Rewriting things is pretty okay in this case because I don't have anything custom in my pacman.conf.

In fact, I'd assume that if someone actually did modify their pacman.conf file, they'd be well-aware of this and wouldn't even need guidance.

Idk, using mv twice was a really quick fix and I didn't have to learn anything new and I was aware that using mv doesn't keep an old copy of the file.

Mr.Elendig · 2013-04-07 12:59:24

MutantJohn wrote:

I didn't have to learn anything new

This is NOT a good thing. Knowing how to take care of .pacnew files is critically important to be able to maintain an arch system with the least amount of hassle and problems. It is one of the FIRST and MOST IMPORTANT things one should learn as a new archlinux user.

Last edited by Mr.Elendig (2013-04-07 12:59:53)

Spyhawk · 2013-04-07 14:17:57

Of course, using mv without understanding the change is pretty stupid.

Another way of handling the *.pacnew file is using pacdiff, which is now directly shipped with pacman (previously in pacman-contrib). This allow to have a quick look, do the necessary change if necessary, and that's even faster than using 'mv'

cfr · 2013-04-07 15:48:19

MutantJohn wrote:

In fact, I'd assume that if someone actually did modify their pacman.conf file, they'd be well-aware of this and wouldn't even need guidance.

If somebody did not modify the file, they would not need guidance because there would not be a pacman.conf.pacnew. If the original file was unmodified, pacman would install the new version automatically. If you had a pacman.conf.pacnew, you modified pacman.conf at some point.

georgezaf · 2013-04-07 21:19:44

[root@georgezafnet georgezaf]# pacman -Suy
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: The following packages should be upgraded first :
    pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] y

resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: package-query: requires pacman<4.1

error update..

Last edited by georgezaf (2013-04-07 21:20:53)

WorMzy · 2013-04-07 21:26:23

Search forums. Solution everywhere.

jasonwryan · 2013-04-07 21:27:56

Merging with the mega thread...

ostroffjh · 2013-04-07 21:28:10

I've got a problem I have not seen mentioned. With pacman core/pacman 4.1.0-2 (base base-devel), when I do pacman -Sc, I get

# pacman -Sc
Packages to keep:
  All locally installed packages

Cache directory: /var/cache/pacman/pkg/
:: Do you want to remove all other packages from cache? [Y/n] y
removing old packages from cache...
error: could not open file /var/cache/pacman/pkg/usr: Error reading fd 6
error: could not open file /var/cache/pacman/pkg/sbin: Error reading fd 6
error: could not open file /var/cache/pacman/pkg/lib: Error reading fd 6
error: could not open file /var/cache/pacman/pkg/etc: Error reading fd 6

Database directory: /var/lib/pacman/
:: Do you want to remove unused repositories? [Y/n] n
#

lib is a symlink to usr/lib. etc and sbin are root root 0755, and usr is 0700 root root. It looks like most stuff in those folders is from last July, with some things much older. I've searched quite a bit, and haven't found any description of what is supposed to be in those folders. I have no trouble reading any of the files in those directories.

Can I safely delete them without messing up my system? Is the error actually indicative of some more (or less) serious problem?

Thanks for any suggestions on how to proceed or at least to troubleshoot further.

debdj · 2013-04-07 21:39:42

At times I wonder why some people use arch -_-
Is it because it's cool telling people 'Hey! I use arch', just like the case for some people about bt? Weird.

hokasch · 2013-04-08 01:28:06

@ostroffjh

/var/cache/pacman/pkg is a cache for pacman to keep packages you installed. Having /usr etc folders in there is odd, looks like a package was actually unpacked/installed in there? To find out what happened look at the files in there, or check with pacman if any package owns these files (I doubt it). Probably save to delete, as it doesn't belong there and isn't in your path anyway, but try to understand how these files ended up there first.

hydn · 2013-04-08 18:29:38

Thanks, I did see notice about /etc/pacman.conf but I forgot to uncomment multilib.

fulafisken · 2013-04-09 19:55:27

This solution worked for me, no need to remove packages:

pacman -Syy
pacman -S package-query
answer no to "upgrade pacman first?"
pacman -S pacman
pacman -Syu

Arch Linux

#26 2013-04-05 14:47:19

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#27 2013-04-05 15:54:39

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#28 2013-04-05 15:58:31

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#29 2013-04-05 16:05:09

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#30 2013-04-05 16:31:21

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#31 2013-04-05 17:46:28

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#32 2013-04-05 19:45:54

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#33 2013-04-05 22:25:08

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#34 2013-04-06 01:29:13

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#35 2013-04-06 01:32:14

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#36 2013-04-06 01:47:32

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#37 2013-04-06 17:53:00

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#38 2013-04-06 18:28:00

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#39 2013-04-07 03:40:11

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#40 2013-04-07 12:59:24

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#41 2013-04-07 14:17:57

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#42 2013-04-07 15:48:19

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#43 2013-04-07 21:19:44

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#44 2013-04-07 21:26:23

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#45 2013-04-07 21:27:56

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#46 2013-04-07 21:28:10

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#47 2013-04-07 21:39:42

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#48 2013-04-08 01:28:06

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#49 2013-04-08 18:29:38

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

#50 2013-04-09 19:55:27

Re: [SOLVED] Upgrading to Pacman 4.1 - various issues

Board footer