How do I find out which package is causing a conflict?

Benedict_White · 2005-01-13 18:08:17

I was making INN which creates a paths.h file which conflicts with the one in /usr/include.

How do I find out where that one comes from?

iBertus · 2005-01-13 18:20:03

You can do the below to learn which package owns the installed file.

 pacman -Qo /usr/include/paths.h

Of course, you can just change the filename to check any file. Btw, my paths.h file seems to be owned by glibc.

Benedict_White · 2005-01-13 20:22:54

Many thanks for that.

Perhaps next time I am reading the how to on abs and makepkg more of it will stay in. I should have remembered that one.

Any one fancy testing Inn?

(As in InterNetNews server)

See:
http://www.isc.org/index.pl?/sw/inn

I have a PKBUILD that seems to work.

phrakture · 2005-01-13 20:32:24

hmmm post your PKGBUILD here.... if it's a stand-alone application, it shouldn't distribute header files (especially paths.h) with the package...

Benedict_White · 2005-01-14 00:08:38

Well the PKGBUILD is:
pkgname=inn
pkgver=2.4.1
pkgrel=1
pkgdesc="inn, The Internet News Server, a highly scaleable news server which usenet relies on"
url="http://www.isc.org/index.pl?/sw/inn"
license=""
depends=('perl' 'python')
makedepends=()
conflicts=()
replaces=()
backup=(/etc/news/actsync.cfg /etc/news/actsync.ign /etc/news/buffindexed.conf
/etc/news/control.ctl /etc/news/cycbuff.conf /etc/news/distrib.pats
/etc/news/expire.ctl /etc/news/incoming.conf /etc/news/inn.conf
/etc/news/innfeed.conf /etc/news/innreport.conf /etc/news/innwatch.ctl
/etc/news/moderators /etc/news/motd.news /etc/news/news2mail.cf
/etc/news/newsfeeds /etc/news/nnrpd.track /etc/news/nntpsend.ctl
/etc/news/ovdb.conf /etc/news/overview.fmt /etc/news/passwd.nntp
/etc/news/radius.conf /etc/news/readers.conf /etc/news/sasl.conf
/etc/news/storage.conf /etc/news/subscriptions /etc/news/filter/INN.py
/etc/news/filter/filter.tcl /etc/news/filter/filter_innd.pl
/etc/news/filter/filter_innd.py /etc/news/filter/filter_nnrpd.pl
/etc/news/filter/nnrpd_auth.pl /etc/news/filter/nnrpd_auth.py
/etc/news/filter/startup.tcl /etc/news/filter/startup_innd.pl )
install="$pkgname.install"
source=(ftp://ftp.isc.org/isc/inn/$pkgname-$pkgver.tar.gz inn.install )
md5sums=('bec635b6e70188071fdb539cd374f2ba' '4c2436cf3d17263d4c76f34505bfe7d9')

build() {
cd $startdir/src/$pkgname-$pkgver
./configure --with-perl --with-python --prefix=/usr --sysconfdir=/etc/news
--localstatedir=/var/spool/news --with-db-dir=/var/spool/news/db
--with-etc-dir=/etc/news --with-run-dir=/var/spool/news/run
--with-spool-dir=/var/spool/news/newsspool --with-tmp-dir=/var/spool/news/tmp
--with-sendmail=/usr/sbin --with-log-dir=/var/log/news
--with-filter-dir=/etc/news/filter --includedir=/usr/inn/include

make || return 1
make DESTDIR=$startdir/pkg install
}
# End of File

But you will also need to include the following in inn.install :
post_install() {
if [ -z "`getent group news`" ]; then
groupadd -g 9 news
fi
if [ -z "`getent passwd clamav`" ]; then
useradd -u 9 -g news -c "INN News Server" -d /dev/null -s /bin/false news
fi
}

#post_upgrade() {
# post_install $1
# echo "Warning: /etc/clamav/clamav.conf is now /etc/clamav/clamd.conf"
#}

pre_remove() {
userdel news &> /dev/null
groupdel news &> /dev/null
}

op=$1
shift

$op $*
#end of file and do not include this line.
Also, the inn.install file was ripped from the clamav abs tree and I will edit it to make it make sense.

I think the include files are there fore system info as most inn news servers do little else and everything is built around them.

I will ask the inn boys though, to see what they say.

I would suggest running makapkg -g to check the MD5 checksums.

However, perhaps I ought to write a howto on use inn.

Very very bad for the noob to inn, but in reality very easy for certain configs.

I would say though that any administration of inn should be done as su- news

Perhaps though, that was not clear enough.

DO NOT ADMINISTER INN AS ANYTHING OTHER THAN NEWS.

DO NOT EVEN THINK ABOUT THINKING ABOUT IT!

That said I think you can edit /etc/news/* as root, but you should run all programs as news, mod alll other files as news.

There is a bit of a gotcha in the install as is, which is the bit about touching history (In this pkg, /var/spool/news/db/ )

Here is what INSTALL say which is usefull:

Next, you need to create an empty history database. To do this, type:

cd ~news/db
touch history
makedbz -i

The INSTALL file is generally usefull.

In particular if you want to connect to the news server with a client you need to look at /etc/news/readers.conf

I have run a few private inn servers, and frankley they whoop BBS or BBS atyle websites.

In fact, I also have a news to web gateway so that you can have a web forum and a news server at the same time. The only issue is NNTP servers do not support virtual hosts, and it is unlikely they ever will.

Benedict_White · 2005-01-14 09:32:54

Something else that needs to be done is to set the home of news which is /var/spool/news for this package.

I would be interested in any feed back.

Arch Linux

#1 2005-01-13 18:08:17

How do I find out which package is causing a conflict?

#2 2005-01-13 18:20:03

Re: How do I find out which package is causing a conflict?

#3 2005-01-13 20:22:54

Re: How do I find out which package is causing a conflict?

#4 2005-01-13 20:32:24

Re: How do I find out which package is causing a conflict?

#5 2005-01-14 00:08:38

Re: How do I find out which package is causing a conflict?

#6 2005-01-14 09:32:54

Re: How do I find out which package is causing a conflict?

Board footer