Archlinux: Pacman 4.1.0 released

[securitybreach]

Pacman 4.1.0 has been released with lots of new features like warnings in color, status on optional deps, compression flags, etc. The News has not been updated on the Archlinux.org page as the update just came through. Here is the steps I had to use to get the latest pacman version installed:

 

First, I tried to update and got some errors:

[root@Cerberus comhack]# pacman -Syu

:: 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...
:: pacman and pacman-contrib are in conflict. Remove pacman-contrib? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: package-query: requires pacman<4.1
:: pacman-color: requires pacman<4.1

 

So I started to remove package-query as the aur page said to reinstall package-query:

[comhack@Cerberus 11:02 PM] ~-> su
Password:
[root@Cerberus comhack]# pacman -Rns package-query
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: yaourt: requires package-query>=1.0

 

So now I have to remove yaourt also:

[root@Cerberus comhack]# pacman -Rns package-query yaourt
checking dependencies...

Targets (2): package-query-1.1-2 yaourt-1.2.2-1

Total Removed Size: 0.29 MiB

Do you want to remove these packages? [Y/n]
(1/2) removing yaourt [######################] 100%
(2/2) removing package-query [######################] 100%

 

Now I am able to update pacman:

[root@Cerberus comhack]# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
repo-ck 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]

resolving dependencies...
looking for inter-conflicts...
:: pacman and pacman-contrib are in conflict. Remove pacman-contrib? [y/N] y

Targets (2): pacman-contrib-4.0.3-1 [removal] pacman-4.1.0-2

Total Download Size: 0.58 MiB
Total Installed Size: 4.24 MiB
Net Upgrade Size: 0.61 MiB

Proceed with installation? [Y/n]
:: Retrieving packages from core...
pacman-4.1.0-2-x86_64 598.0 KiB 660K/s 00:01 [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(2/2) checking available disk space [######################] 100%
(1/1) removing pacman-contrib [######################] 100%
(1/1) upgrading pacman [######################] 100%
warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew

(you may or may not of been using pacman-contrib but either way it must be removed now)

 

 

After updating pacman, you need to compare your old /etc/pacman.conf file with the new /etc/pacman.conf.pacnew as there are a few changes:

 

Warnings are in color now if you uncomment the Color option under Misc options:

# Misc options

#UseSyslog

Color

TotalDownload

CheckSpace

#VerbosePkgLists

 

Make sure to uncomment multilib if you are running a 64 bit version of Arch:

[multilib]

SigLevel = PackageRequired

Include = /etc/pacman.d/mirrorlist

 

One thing to note, until yaourt and package-query get updated (looks like it has been updated now), it is best to use packer as a pacman/aur wrapper

 

Also, packer can provide the same function as yaourt without package-query and it build fine against the new version of pacman. :

[comhack@Cerberus 11:02 PM] ~-> packer -Syu
root Password:
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
repo-ck is up to date
:: Starting full system upgrade...
there is nothing to do
:: Synchronizing aur database...
aur 53 53 [##########################################################################################################################################################]100%
:: Starting full aur upgrade...
local database is up to date

 

[abarbarian]

First class detailed instructions.

 

Do you think you could pop round and update my Arch

[abarbarian]

Yaourt installs just fine. However these are given as optionals for yaourt.

 

 

aurvote customizepkg rsync pacman-color

 

All install apart from

 

pacman-color

 

Which seems to have disappeared from the planet as a separate package. I guess they have merged it with pacman.

 

In the old pacman.conf you had this

 

# If upgrades are available for these packages they will be asked for first

SyncFirst = pacman

 

I'm guessing that they have included this function into pacman as a default.

 

Also there is this from my old pacman.conf

 

# 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.

#ySigLevel = Required DatabaseOptional TrustedOnly

 

which has changed to this in the new pacman.conf

 

 

# 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

 

 

In my old pacman.conf I had all the lines commented out due to some hicups in the past. Was wondering if I need to uncomment "#RemoteFileSigLevel = Required" or would that cause problems again ?

 

:'(

Edited April 5, 2013 by abarbarian

[securitybreach]

Yaourt installs just fine. However these are given as optionals for yaourt.

aurvote customizepkg rsync pacman-color

 

All install apart from

pacman-color

 

Which seems to have disappeared from the planet as a separate package. I guess they have merged it with pacman.

 

They must of updated package-query and yaourt this morning sometime as it installs fine now. As far as pacman-color, the functionality has been added to pacman. You just need to uncomment the Color option under Misc options in /etc/pacman.conf.

 

In the old pacman.conf you had this

# If upgrades are available for these packages they will be asked for first

SyncFirst = pacman

 

I think this line takes care of that:

HoldPkg = pacman glibc

As far as I understand, HoldPkg basically makes sure that if there is pacman or glibc update, then it gets updated before continuing with other updates.

 

Also there is this from my old pacman.conf

# 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 TrustedOnly

 

which has changed to this in the new pacman.conf

# 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

 

In my old pacman.conf I had all the lines commented out due to some hicups in the past. Was wondering if I need to uncomment "#RemoteFileSigLevel = Required" or would that cause problems again ?

 

I never had

#RemoteFileSigLevel = Required

enabled but you do need to have:

 

SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional

 

to enable package signing which is pretty much required and should be used. Here is my pacman.conf for reference: http://ix.io/52m

[securitybreach]

Highlights of Pacman 4.1.0:

 

• File properties are now checked when using -Qkk;

• Color has been added to pacman output;

• Informational messages has been added for the optdepends installation status;

• Options have been added to specify the required signature level for Upgrade operations;

• The directory ownership can now be queried;

• SyncFirst option has been removed;

• The -f short option has been removed from --force.

 

http://news.softpedia.com/news/Arch-Linux-s-Pacman-Reaches-Version-4-1-0-342169.shtml

[V.T. Eric Layton]

[abarbarian]

Thanks securitybreach I missed

 

HoldPkg = pacman glibc

 

when I read through the file. An you put me mind at rest with your details on

 

 

 

I never had

#RemoteFileSigLevel = Required

enabled but you do need to have:

 

SigLevel = Required DatabaseOptional

LocalFileSigLevel = Optional

 

to enable package signing which is pretty much required and should be used.

 

You do realise that next time around you will be able to find all the answers in version 4.2. Maybe they should start naming pacman versions and call 4.2 The Don't Panic version.

[abarbarian]

Is this new ?

 

Optional dependencies for hexchat

enchant: Spell check [installed]

perl: Perl plugin [installed]

python2: Python plugin [installed]

 

I'm almost sure that we never got " [installed] " showing before. Neat feature though.

[amenditman]

Is this new ?

 

 

 

I'm almost sure that we never got " [installed] " showing before. Neat feature though.

You are right, that is new.

 

I like it.

[securitybreach]

Is this new ?

 

 

 

I'm almost sure that we never got " [installed] " showing before. Neat feature though.

 

Yeah I mentioned that in the first post :

Pacman 4.1.0 has been released with lots of new features like warnings in color, status on optional deps, compression flags, etc.

[saturnian]

Hm, trying to go through this thread to see how the information here applies to my Bridge Linux installation...

 

I updated to pacman 4.1 today. I may have missed this line:

 

warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew

 

Now I see both /etc/pacman.conf and /etc/pacman.conf.pacnew present, but I'm not sure if I need to replace the old file with the new one. I've been using packer, and when I run it I see:

 

[root@bridgelinux steve]# packer -Syu
warning: config file /etc/pacman.conf, line 19: directive 'SyncFirst' in section 'options' not recognized.

 

That refers to the line you guys mentioned, but in my old pacman.conf, it looks like this:

 

# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman linux-headers

 

So I think I'm supposed to replace the old pacman.conf file with the new; checking to see what folks say at the Bridge forums. Thanks for starting this thread, securitybreach!

[securitybreach]

Yes, compare your pacman.conf to the new pacman.conf.pacnew. Make any changes you need, then rename the pacman.conf.panew to pacman.conf. I am not at home right now but that is the gist of it.

[ichase]

Saturnian, I would recommend using the new pacman.conf.pacnew in place of your current pacman.conf. MAKE SURE and backup your current pacman.conf prior to doing this. The new pacman.conf has some of the changes with the new version implemented. Utilzing Security Breach's example, make the necessary changes to the pacnew file and overwrite the current .conf file. ONCE AGAIN only AFTER you have saved your current config file.

[saturnian]

Yeah, I should have mentioned that I'd make a backup of the old pacman.conf before doing anything else. Thanks folks. This is all very fascinating to me; even though I didn't install "straight" Arch, what I'm seeing here in Bridge sure looks close to what you folks are talking about. I do feel kinda clueless, though -- almost feeling like logging back into Debian, back to my "comfort zone."

 

Cool stuff. In some ways, reminds me when I first started out with Linux (the feeling of not knowing what the heck I'm doing). One of these days, I might have to go ahead and install Arch, but for now I think I'm okay with trying to get a feel for things with Bridge.

[abarbarian]

If you have bridge installed and in a workable state then I guess you have it cracked. Updating every day if possible makes life a lot easier. An quite often if an update fails and you do not have time to problem solve then waiting to try again in a few days usually sorts things out as glitches get fixed swiftly in the core and popular programs. Even old hands get caught out by some updates.

I'm still setting my install to suit and I have been at it for two years or so. Mind you I do keep installing new programs and trying to tweak them a bit. Keep a fresh backup of the running system always to hand and you can fiddle as much as you like.

 

Have fun.

 

[ichase]

One of these days, I might have to go ahead and install Arch, but for now I think I'm okay with trying to get a feel for things with Bridge.

Saturnian, I have NO DOUBT what so ever that you could successfully install Arch. I truly believe once you do you will love it. The amazing thing about Arch is, it only installs a foundation. YOU BUILD the house. Want to run KDE, GNOME, E-17, Awesome, Cinnamon, Openbox etc, install what you want. (If you got the room, install them all and with a few quick changes of your .xinitrc file, and exiting X and re-entering X you are in your new environment) Prefer Dolphin over Thunar or SpaceFM, install only Dolphin. The thing is, no one person running Arch Linux has the same set up running. They are all different because it suits what the person running it wants.

 

Not to mention you have SecurityBreach, Abarbarian, myself all running Arch, you have plenty of resources to help out when needed. Look at me, I ALWAYS asking questions.

Edited April 7, 2013 by ichase

[abarbarian]

http://forums.scotsnewsletter.com/index.php?showtopic=61902

 

Clear and current install guide.