Arch Linux

purple12

Member

Registered: 2008-08-16

Posts: 73

[SOLVED] syslog-ng file conflict blocking u/g...

OK, please don't flame me.  I already tried the WIKI search function and got some pretty good info, but I still have one or two questions.  I'm just wondering how best to proceed here.  It looks like Arch found a file conflict during an attempted system u/g.  I used # pacman -Syu, and after fetching a large number of packages, the conflict check returned the following:

stunnel-4.34-1-x86_64                                116.9K  224.5K/s 00:00:01 [##############################################] 100%
checking package integrity...
(679/679) checking for file conflicts                                           [##############################################] 100%
error: failed to commit transaction (conflicting files)
syslog-ng: /etc/modules.conf exists in filesystem
Errors occurred, no packages were upgraded.

As I said, I've read through a few forum posts relating in a general way to this sort of problem, but I'm still have the following questions:

1. This output seem to indicate that this might be the only file conflict blocking the u/g...
2. If not, could other conflicts be discovered if I repeat the pacman -Syu after resolving the conflict with this particular file?
3. finally, assuming this single conflict is the culprit, what's the best way to get past it?

Thanks very much.

btw: there's a strong chance that I'll die of embarrassment if asked how long it's been since my last u/g.

Last edited by purple12 (2011-01-23 00:21:04)

Snowman

Developer/Forum Fellow

From: Montreal, Canada

Registered: 2004-08-20

Posts: 5,212

Re: [SOLVED] syslog-ng file conflict blocking u/g...

run
pacman -Qo /etc/modules.conf
to see  which package this file belong to.

purple12

Member

Registered: 2008-08-16

Posts: 73

Re: [SOLVED] syslog-ng file conflict blocking u/g...

SOLVED. 
Thanks for the input Snowman.  Last night I found I couldn't face the prospect of an evening without my Arch box (sad, I know...), so I went online with my friend Alex M., the arch-Archer who's currently living and working in Japan.  He gave me permission to force the syslog-ng upgrade.  Turns out that this conflict was the only one identified out of over 680 packages that needed updating (it had been over a year since I'd done a full sys u/g...heh.) 
I was convinced that my ancient, heavily-whiskered Arch install would get irretrievably horked by a full upgrade, but to my utter astonishment, the damn thing updated just fine, and, with a bit of kernel module manipulation by Uber-Alex, my system was back up, fully upgraded, and shiny-new in under an hour!
Thanks Arch Devs! 
I hereby promise to be much more aggressive about system maintenance in the future...