[SOLVED] .pacnew files

I just realized something that may have some bad consequences (Atleast, I think they might be bad, usually when I forget to do something on a Linux system it results in me reinstalling the entire OS).
I forgot to merge some files that are used by pacman, but I dont know how. I need to merge /etc/pacman.d/mirrorlist and /etc/pacman.d/mirrorlist.pacnew. I also need to merge pacman.conf and pacman.conf.pacnew. I read some forum posts about this topic, but I did not fully understand then (I'm a noob). They were talking about programs like pacdiff and vimdiff. Should I use those programs? If so, how would I go about downloading and merging the 2 files?
Last edited by dsplayer14 (2012-06-27 15:04:59)

If you're sticking around arch, or linux in general, you should learn to use these tools. Vimdiff is wonderful ... but only if you already use vim. If you don't use vim it will most likely just confuse the hell out of you.
For the time being or while your still learning to use these tools well, I'd recommend whatever text editor you are comfortable with. If it's nano, use nano, or leafpad, or gedit, kate, any of them will work. Open each file in one instance of the editor side by side. The *.pacnew file will have the most up-to-date "defaults". If you have not added or changed anything in your config files, then you can actually just move pacman.conf.pacnew to pacman.conf overwritting the latter. But with the pacman.conf, you should also read it carefully as it may have some important instructions depending on when you last updated (about package signing and the like). If you have changed your pacman.conf, you'll have to "merge" those changes. All the diff/merge tools help in this process, but all it is is putting together the updates in the pacnew with the changes you have made.
The mirrorlist.pacnew is less important. Mainly it just removed the ftp mirrors which (if you have a working system) you're most likely not using anyways. If you use any mirrorlist tool like reflector, just delete the mirrorlist.pacnew. Or if your current mirrorlist is working well - just delete the mirrorlist.pacnew.
Last edited by Trilby (2012-06-27 14:30:46)

Similar Messages

[SOLVED]pacnew files? i need help...

Hi,
After upgrade with pacman -Syu, a lot of pacnew files in /etc.I read about this in archwiki but i'm still confused :S I have no idea how to use vimdiff or meld ...
Can someone explain me simple what to do with pacnew files.I'm new in arch linux and i need help.
Thanks to everyone. (sorry for my english)
Last edited by grobar87 (2011-04-15 14:26:42)

ewaller wrote:
a pacnew file is used when an update to a package requires a new configuration file, but there is already a configuration on your system which would be wrong to simply overwrite.
If there is nothing in the old, corresponding file you want to keep, it is okay for you to move the pacnew file and overwrite the old configuration. If it is not okay, you need to incorporate your customizations into the pacnew file, and then move the pacnew file and overrwrite the old file.
The tools you mentioned are just that -- tools to help figure out what changed. The easiest solution is just to run diff fileName fileName.pacnew to see the lines that changed.
Thanks for reply...I install vim and run diff:
[root@DejanArch dejan]# diff /etc/group /etc/group.pacnew
8c8
< lp:x:7:daemon,dejan
> lp:x:7:daemon
11c11
< wheel:x:10:root,dejan
> wheel:x:10:root
15a16
> utmp:x:20:
20,28c21,29
< games:x:50:dejan
< network:x:90:dejan
< video:x:91:dejan
< audio:x:92:dejan
< optical:x:93:dejan,hal
< floppy:x:94:hal
< storage:x:95:dejan,hal
< scanner:x:96:dejan
< power:x:98:dejan
> games:x:50:
> network:x:90:
> video:x:91:
> audio:x:92:
> optical:x:93:
> floppy:x:94:
> storage:x:95:
> scanner:x:96:
> power:x:98:
31,39d31
< dbus:x:81:
< hal:x:82:
< avahi:x:84:
< usbmux:x:140:
< camera:x:97:dejan
< ntp:x:1000:
< rtkit:x:133:
< deluge:x:125:
< utmp:x:20:
Now? How to merge this two files?
Thanks again.
Last edited by grobar87 (2011-04-13 18:57:50)

[Solved] A Challenge: Loop meld to update *.pacnew files

I got no secret, I love meld . Does a great job of showing differences alot of times if even scattered all over the page, allows for copy and paste... vimdiff is good but requires a much more keypresses, copy and paste isn't as elegant, and with my fixed drop-down terminal is just too narrow to be able to do it well. So what I usually end up doing is:
find /etc -type f -name "*.pacnew"
and just go through them one at a time:
kdesu meld /etc/config /etc/config.pacnew
I haven't do much work with loops, so I was hoping that someone that knew a little about them that could create a script that would go through them one by one. I suppose this is going to be a little tricker because (I imagine) it's going to have to detect when the windowed instance closes.
From the knowledge I know, I would do:
#!/bin/bash
# etc-update - merge *.pacnew files with original configurations with meld
pacnew=$(find /etc -type f -name "*.pacnew")
for i in $pacnew
do
kdesu meld $i
done
Which isn't going to work very well. Well, I guess it could, but it's going to open them all at once and leave a nice scruched-up taskbar with *.pacnew files. Like to be able to go through them one by one.
Anyone had any experiences at this that could help?
Last edited by Gen2ly (2009-10-03 01:46:55)

brisbin33 wrote:
http://pbrisbin.com:8080/bin/pacnews
just do a find/replace of vimdiff for meld (or whatever...)
Nice script, bris. If I had know about that before, I'd be using it. Do like the idea of the walk-through process and the saving of the the current one.
lol, I just read your last post and just what I thought about.
ugkbunb wrote:I just edited the pacdiff script to use meld and it worked great : ) -- I am not at home atm, but if you would like I can post up my edited pacdiff script.
Yeah, I saw that on the wiki. Said it was for CLI though so I didn't get to try.
@ lolilolicon, and Procyon
Still learning about pids, what I have seen was more complicated than this. Pretty clever.
Allan wrote:
Maybe....
#!/bin/bash
# etc-update - merge *.pacnew files with original configurations with meld
pacnew=$(find /etc -type f -name "*.pacnew")
for i in $pacnew
do
kdesu meld $(basename $i .pacmew) $i &
wait
done
Note - untested
Ah, very nice. Also fits into my knowledge of bash. Hadn't thought about just using & but it works great. Had to truncate the file extension and just used a bash filter:
#!/bin/bash
# pacnew-diff - merge *.pacnew files with original configurations with meld
pacnew=$(find /etc -type f -name "*.pacnew")
for config in $pacnew
do
kdesu meld ${config%\.*} $config &
wait
done
Like to be able to do a backup of the current config and then erase the pacnew file afterword, but havn't found out a way to do that without having to type in a password everytime, but, I guess, that can easily be done elsewhere.
Last edited by Gen2ly (2009-10-02 20:27:17)

(SOLVED) Trouble merging .pacnew files with meld

Dear Archers
Unable to merge .pacnew files, following the example on ArchWiki. Only, the difference between the two files shown
[root@KRISHNA san2ban]# #!/bin/bash
[root@KRISHNA san2ban]# # pacnew-update - merge *.pacnew files with original configurations with meld
[root@KRISHNA san2ban]#
[root@KRISHNA san2ban]# pacnew=$(find /etc -type f -name "*.pacnew")
[root@KRISHNA san2ban]#
[root@KRISHNA san2ban]# for config in $pacnew; do
> # Merge with meld
> gksu meld ${config%\.*} $config &
> wait
> done
[1] 1578
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
Also, on the Archwiki, we are advised to change 'kdesu' to 'gksudo' for GNOME, but I think it should be gksu
Last edited by San2ban (2011-08-18 14:07:53)

San2ban wrote:
Dear Karol
Thanks. yes, manual intervention is needed
Wonder how it will be without you guy's guiding us
You bet your ass, manual intervention is needed. If you try to blindly just merge *.pacnew with original files, it might lead to an unbootable system. Especially when you get pacnew files for /etc/group and /etc/inittab

(SOLVED)recent update .pacnew files what to do?

Maybe I'm having a duh! moment but today #pacman -Syu gave me /etc/makepkg.conf and /etc/makepkg.conf.pacnew that are identical.; and /etc/pacman.conf(my edited one) and /etc/pacman.conf.pacnew(like new install file). Can I just delete the .pacnew files and keep the original files?
Last edited by lestoil (2009-10-02 17:38:30)

maybe yes, maybe no!
you need to check every .pacnew, if the .pacnew is identical to the original file, you can remove it.
if it isn't identical, you need to merge this 2 files...
i would like to help you a bit more, but my poor english stop me xD
Sorry, for more info, the wiki
http://wiki.archlinux.org/index.php/Pac … save_Files

[SOLVED] Messed things up while trying to deal with a .pacnew file

I manually applied some of the changes recently made to /etc/services but, damn, forgot to save both of the modified files.
I only saved the .pacnew one (after having removed the lines that I had checked).
I know, how on earth.. Well, I don't really know.
Now the question is: Is there some way for me to download a new .pacnew file to start all over?
Last edited by av (2012-09-08 08:33:04)

If you want the stock /etc/services, they are provided by iana-etc package:
$ pacman -Qo /etc/services
/etc/services is owned by iana-etc 2.30-3
Edit: If the modifications were done wrt to an update, https://bbs.archlinux.org/viewtopic.php … 5#p1139205
Last edited by karol (2012-09-08 07:53:44)

[SOLVED] == ERROR: file not found: `/sbin/dmsetup'

[EDIT] A much simpler way to deal with this is to explicitly ignore the kernel update during a full system update:
pacman -Syu --ignore linux
Then explicitly update the kernel alone:
pacman -S linux
[EDIT] First, after a full system update I had to move the STUB kernel image from the UEFI directory back to /boot, them recreate the images a second time. The systemd service moved it back to the UEFI directory.
[EDIT] The use of 'mdadm_udev' in HOOKS= also seems to be no longer just 'preferred' to the 'mdadm' hook but instead is now mandatory.
I've read the news item...
Changes to LVM
2013-02-12 - Thomas Bächler
With lvm2 2.02.98-3, we now utilize lvmetad to activate LVM volumes automatically. This implies the following changes:
The lvm2 initramfs hook now requires the udev hook.
The use_lvmetad = 1 must be set in /etc/lvm/lvm.conf. This is the default now - if you have a lvm.conf.pacnew file, you must merge this change.
You can restrict the volumes that are activated automatically by setting the auto_activation_volume_list in /etc/lvm/lvm.conf. If in doubt, leave this option commented out.
If you need monitoring (needed for snapshots), run systemctl enable lvm-monitoring.service.
The lvmwait kernel command line option is no longer needed and has no effect.
If you run pacman -Syu and update device-mapper, linux and lvm2 at the same time, you will get an error message that /sbin/dmsetup is missing. Run mkinitcpio -p linux again after the update to avoid any problems.
...and I do get the message...
==> ERROR: file not found: `/sbin/dmsetup'
...but after a full system update with...
pacman -Syu
...when I execute...
mkinitcpio -p linux
...this is what I get...
Building image from preset: 'default'
/boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
ERROR:specified kernel image does not exist: `/boot/vmlinuz-linux'
Building image from preset: 'fallback'
/boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
ERROR:specified kernel image does not exist: `/boot/vmlinuz-linux'
So of course if I reboot I get the dreaded 'No volume groups found' message.
I should mention that I use the systemd path and service to move the kennel after it has been updated.
Last edited by KairiTech (2013-04-07 02:45:12)

With lvm2 2.02.98-3, we now utilize lvmetad to activate LVM volumes automatically. This implies the following changes:
The lvm2 initramfs hook now requires the udev hook.
The use_lvmetad = 1 must be set in /etc/lvm/lvm.conf. This is the default now - if you have a lvm.conf.pacnew file, you must merge this change.
You can restrict the volumes that are activated automatically by setting the auto_activation_volume_list in /etc/lvm/lvm.conf. If in doubt, leave this option commented out.
If you need monitoring (needed for snapshots), run systemctl enable lvm-monitoring.service.
The lvmwait kernel command line option is no longer needed and has no effect.
Just to confirm. You did all these steps, right?
EDIT: I just noticed something:
KairiTech wrote:HOOKS="base udev autodetect sata mdadm usbinput keymap encrypt lvm2 filesystems timestamp shutdown"
Replace
mdadm
with
mdadm_udev
. Maybe this is nothing, but it is recommended to use this one instead of the other.
NEW EDIT: Expecially this one
The use_lvmetad = 1 must be set in /etc/lvm/lvm.conf. This is the default now - if you have a lvm.conf.pacnew file, you must merge this change.
Last edited by s1ln7m4s7r (2013-03-24 20:42:55)

Permission of .pacnew files

After updating sudo package smth made me check the diff between /etc/sudoers and /etc/sudoers.pacnew (I did it from regular user, not root) :
$ LANG="" diff /etc/sudoers.pacnew /etc/sudoers
diff: /etc/sudoers: Permission denied
For my surprise he yelled only for /etc/sudoers, and nothing about sudoers.pacnew file.
So I checked the permissions:
$ LANG="" ls -l /etc/sudoers*
-r--r----- 1 root root 723 Jun 20 02:11 /etc/sudoers
-rw-r--r-- 1 root root 608 Jun 27 00:26 /etc/sudoers.pacnew
As You can see the .pacnew file has read permission for ALL. There's nothing wrong with this, it's a default file and there's nothing importand in there I thought. BUT after a minute... what about a situation when an administrator moves the /etc/sudoers.pacnew to /etc/sudoers, then edits it and makes important changes.. ? The file is still readable for ALL!
I think it's quite important issue or mayby I don't know about smth
EDIT:
I made a little test:
# ls -l /etc/sudoers*
-r--r----- 1 root root 723 VI 20 02:11 /etc/sudoers
-rw-r--r-- 1 root root 608 VI 27 00:26 /etc/sudoers.pacnew
# cp /etc/sudoers.pacnew /etc/sudoers
# ls -l /etc/sudoers*
-r--r----- 1 root root 608 VI 27 01:29 /etc/sudoers
-rw-r--r-- 1 root root 608 VI 27 00:26 /etc/sudoers.pacnew
So when admin only copies the new file on the old one, the permissions will stay OK, it's quite normal
# rm /etc/sudoers; cp /etc/sudoers.pacnew /etc/sudoers
# ls -l /etc/sudoers*
-rw-r--r-- 1 root root 608 VI 27 01:30 /etc/sudoers
-rw-r--r-- 1 root root 608 VI 27 00:26 /etc/sudoers.pacnew
But what about this? When we first remove the file and then change the name?
I think it's still important to set the permissions of .pacnew files like they are in the package.
EDIT 2:
I forgot to say that after editing the file with visudo, the permissions are changed to proper one.
Last edited by MAC!EK (2007-06-26 23:38:21)

Interesting, please report a bug : bugs.archlinux.org
I think only the "ls -l /etc/sudoers*" output after install is needed, which show
the incorrect permission of the pacnew file, but feel free to stay as verbose for the bug report too
I actually learned something, didn't know that cp behaved that way : when copying a file over an other, it keeps the permission of the replaced file.
But well, that's not related to pacman.

Pacnew_scripts: scripts to merge some .pacnew files after an upgrade

info page: http://xyne.archlinux.ca/info/pacnew_scripts
I was updating my old system which doesn't get turned on that often and had to deal with about 15 pacnew files. Most only required a simple "mv /path/to/file{.pacnew,}" but some required merging. I found a script that I had written a while ago to merge /etc/group.pacnew, made some changes, made a copy which can handle gshadow, then wrote scripts to handle the pacman mirrorlist and locale.gen.
Thus the pacnew_scripts package was born.
infopage wrote:
This package contains scripts which can help merge .pacnew files after a pacman upgrade. These scripts print their results to STDOUT and thus do NOT make any changes to the files. It is up to the user to inspect the output and, if satisfied, redirect it to the original file and then delete the .pacnew file.
The scripts accept "-c" and "--compare" as options and will display relevant information about differences between the files. For group and gshadow, this will display 3 columns to compare the original, .pacnew and merged files and will use colors to highlight changes. For the mirrorlist and locale.gen, it will check that all settings in the original file are available in the new file and print out a list of any that aren't (e.g. if one of your current mirrors has been dropped from the mirrorlist, it will be listed in the output).
I'll probably add scripts as I go. I might also merge the scripts to avoid some redundancy but I decided to keep them simple for now. merge_pacnew_locale_gen is actually very generic and works on the mirrorlist and probably other files as well. If you find any, let me know.
Last edited by Xyne (2010-03-21 13:03:34)

beroal wrote:
I'm really astonished that you interpreted my post as an advertisement of "diffpac".
Xyne wrote:Have you even tried these scripts and compared them to the alternatives that you've proposed? … you can at least post comments based on an informed comparison.
I expected such a comparison from you. If "pacnew_scripts" merges files automatically, what algorithm does it use?
I didn't interpret it as advertisement. It seemed that you read the basic description of what this does and concluded that something else already does the same thing. Following on the tail of the previous posts I felt that your post was somewhat rude because it implies that this is useless. Obviously that is relative, but even so I see no point of posting in this thread to express it, even indirectly.
I admit that I may have interpreted your post the wrong way and if I did then I apologize, but even then I don't understand why you felt the need to post what you did in a contribution thread.
As for algorithms, there are different scripts and they use different algorithms. The group and gshadow scripts create hash representations of the groups in the original and .pacnew files. Groups which only exist in one of the files pass through untouched. Groups which exist in both have their members combined, which usually means that the original simply passes through. Using the "--compare" option, three aligned columns are displayed which clearly shows existing groups, new groups and the results of merging, with colors used to highlight all changes.
The mirrorlist script creates a list of selected servers in the current mirrorlist and generates a new mirrorlist from the .pacnew mirrorlist with all servers in the generated list uncommented, if they exist. Passing the "--compare" option will simply check if all the currently selected mirrors still exist in the new mirrorlist (they might not if they're dropped) and prints out a list of any that aren't.
The locale_gen script does the same thing for currently enabled locales.
Also note that all of the results are printed to STDOUT so no files are actually changes. It isn't fully "automatic" and the user is expected to sanity-check the results before overwriting the target files.

Managing pacsave and pacnew files

Sometimes it is a while before I do another 'pacman -Syu' ... so when I do I might find myself with a few .pacsave and .pacnew files to manage. To help myself deal with them I have written two simple little scripts to check and compare them quickly from the command line. I named the scripts diff_pacnew.sh and diff_pacsave.sh - and offer them here thinking it might be of interest to and maybe useful for forum members.
They use 'diff' to compare the existing file with the new one and prompt to enter a comment (such as "delete pacsave" or "add xyz to the file"). The comments are saved in /tmp/diff_pacsave.txt and /tmp/diff_pacnew.txt so I don't need to remember everything. I just read the txt files and alter/replace/remove the pacsave/pacnew files according to my notes there.
They use the 'locate' tool so I run 'updatedb' before using them.
#!/bin/bash
# diff_pacsave.sh
# script used in Archlinux
# to compare configuration files with their updated versions
for i in `locate *.pacsave`
do
j=`echo $i | sed 's/.pacsave//'`
if [ -f $j ]
then
echo "...................."
echo "comparing $i with $j"
diff $i $j
echo "Enter notes"
read notes
echo "$j" >> /tmp/diff_pacsave.txt
echo "$notes" >> /tmp/diff_pacsave.txt
echo >> /tmp/diff_pacsave.txt
echo
fi
done
#!/bin/bash
# diff_pacnew.sh
# script used in Archlinux
# to compare configuration files with their updated versions
for i in `locate *.pacnew`
do
j=`echo $i | sed 's/.pacnew//'`
if [ -f $j ]
then
echo "...................."
echo "comparing $i with $j"
diff $i $j
echo "Enter notes"
read notes
echo "$j" >> /tmp/diff_pacnew.txt
echo "$notes" >> /tmp/diff_pacnew.txt
echo >> /tmp/diff_pacnew.txt
echo
fi
done

Thanks jason.
Hey Xyne, so i renamed my crond.pacnew to crond (there was no crond before). I don't really know if i need it. I've never messed with it before.
Mine looks like this:
/var/log/crond.log {
sharedscripts
copytruncate
missingok
postrotate
kill -HUP `cat /var/run/cron.pid`
endscript
and it's in the /etc/logrotate.d/ directory. Think I may need it? I have no idea what that stuff means. hehe I just started using Linux just over a month ago with Arch! wooo!!

Tool for merging pacnew files ??

Hi all,
Is there a program available that are able to merge a .pacnew file with the existing files, instead of doing this manually ??
Maybe vim can do this but I am not sure ??
It would be nice to do this quickly to save time !!
Last edited by niller (2008-03-11 12:02:08)

niller wrote:Maybe vim can do this but I am not sure ??
Yup, try this from a terminal:
$ vimdiff /etc/conf /etc/conf.pacnew
Last edited by tom5760 (2008-03-11 13:53:21)

Pacnew files appears in filesytem after upgrade. What do YOU do ?

Hi all
Having great fun with ArchLinux for the last two weeks now, and really enjoy this distro !!
Did a system upgrade yesterday and everything went fine.
But when I'm in console Emacs suddenly behaves strangely when typing danish characters :-/
I looked in /etc for consulting the locale files and discovered some new files with a .pacnew extension.
I did a
grep pacnew /var/log/pacman.log
and gets this
[2008-02-04 09:20] >>> when merging the pacnew file with your old configuration.
[2008-02-04 09:48] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew
[2008-02-04 09:48] ==> Check /etc/locale.gen.pacnew for new supported locales
[2008-02-04 09:48] warning: /etc/profile installed as /etc/profile.pacnew
[2008-02-04 09:48] warning: /etc/rc.conf installed as /etc/rc.conf.pacnew
[2008-02-04 09:48] See /etc/crypttab(.pacnew) for more information.
[2008-02-04 09:49] warning: /etc/logrotate.conf installed as /etc/logrotate.conf.pacnew
[2008-02-04 09:49] warning: /etc/nanorc installed as /etc/nanorc.pacnew
The question is now:
What should I do with this ?? I guess that the /etc/locale.gen.pacnew is to blame for emacs character problems ??
What do YOU do ??
(please have in mind that I am not a emacs expert :-)

stonecrest wrote:
shining wrote:
niller wrote:What do YOU do ??
If it's a config file I edited in the past, I use vimdiff for merging both files.
If not, I simply overwrite the old config file by the .pacnew one.
I thought you only get a pacnew if you had made changes to the file. Or am I confused?
No you are not confused, but they are exceptions. Like some times last year, because of a bug concerning files in NoUpgrade, we had to reset all md5sums of these files.
And same when a file is relocated, like recently /etc/profile which moved from bash to filesystem.
But you are right, in the general case, it does not happen, so I vimdiff all .pacnew files I get
I also find the very simple pacdiff useful when there are several of them.
Last edited by shining (2008-03-12 10:38:31)

Pacmerge -- merge .pacnew files

pacmerge is a simple (80-line) program to interactively merge .pacnew files with sdiff.
https://aur.archlinux.org/packages.php?ID=52485
Why another such program? For two main reasons:
1. Most others use the wronganother program to merge (e.g. vimdiff, kdiff (eww), &c.), which is difficult to change
2. Haskell is nicer than bash
Last edited by strake (2011-11-26 18:27:40)

karol wrote:
doublerebel wrote:I don't care for the obtuse UI of vimdiff
Use can use regular diff if you want.
Or e.g. meld.
I am aware of the other suggested options, I'm not as noob as my post count appears. Diff does not merge files. Copy and paste between files in a terminal while referencing the diff is not a simple task. Meld is GUI-only.
There is definitely a place for a simple CLI .pacnew interactive merge tool. Diffpac/pacdiffviewer is close, but without documentation and also uses vimdiff -- although at least Diffpac has almost no dependencies.
Most of the .pacnew configuration updates are trivial (thanks to Arch's clean structure and upgrade process), and therefore merging should be trivial as well. .pacnew merging is a bump in Arch's otherwise smooth rolling upgrades.

Pacman -Syu [.pacnew files:SOLVED]

Having just done a full system upgrade, I noticed the following:
warning: extracting /etc/shadow as /etc/shadow.pacnew
warning: /etc/gshadow installed as /etc/gshadow.pacnew
warning: extracting /etc/passwd as /etc/passwd.pacnew
warning: extracting /etc/ld.so.conf as /etc/ld.so.conf.pacnew
warning: extracting /etc/fstab as /etc/fstab.pacnew
warning: extracting /etc/group as /etc/group.pacnew
Does this mean I need to copy/overwrite all of the above .pacnew over to the original files?
Thanks in advance.
Last edited by Ipsofacto (2007-04-23 16:51:32)

if theres an important change u'll prolly know if u regurarly take a look at news in main page, forums & the mailing list. after the first 2 months or so on arch i delete em without even viewing them
Last edited by dolby (2007-04-23 05:21:44)

[SOLVED] Php not loading mysql extensions [Merge php.ini.pacnew file].

Hi guys.
I have bitten the bullet and upgraded to the Apache 2.4 and PHP from testing and solved a 10 tons of post-upgrade config nightmares just to figure out that MariaDB will not work with those versions until recompiled against them. Can we please have MariaDB added to testing repo after it was compiled against the Apache and PHP from testing?
Thanks in advance.
Kind regards.
Andrzej
Last edited by AndrzejL (2014-03-02 22:53:23)

Pierre wrote:I don't see how that is related to Apache though. Are the mosql-modules enabled in php.ini?
Spider.007 wrote:So after 10 tons of nightmares you didn't enable the mysql.so and mysqli.so extensions in your php.ini?
I am not an idiot guys (well maybe I am but...), I would not come here and complain about missing extensions for mysql if I didnt tripple checked they were enabled in php.ini.
[root@icsserver andrzejl]# cat /etc/php/php.ini | grep -v ';' | grep -i mysql | grep ext
extension=mysqli.so
extension=mysql.so
extension=pdo_mysql.so
[root@icsserver andrzejl]#
Pierre wrote: How are you using PHP?
FPM/FastCGI / proxying all the php requests,
PHP is working fine from what I can see.
And Wordpress spits out:
"Your PHP installation appears to be missing the MySQL extension which is required by WordPress."
Which I assumed meant that the mysqld (in this case MariaDB) should be recompiled against php to provide those extensions. Could be wrong. Wouldn't be the first time.
Cheers.
Andrzej
Last edited by AndrzejL (2014-03-02 15:01:43)

[SOLVED] .pacnew files

Similar Messages

Maybe you are looking for