Bug 156433 – sys-process/fcron-3.0.1-r2 file collision with sys-freebsd/freebsd-share-6.2_rc1

• Status: RESOLVED FIXED
• Product: Gentoo/Alt

[Description Tiziano Müller (RETIRED) 2006-11-27 11:24:42 UTC]

[...]
>>> Install fcron-3.0.1-r2 into /var/tmp/portage/sys-process/fcron-3.0.1-r2/image/ category sys-process
>>> Completed installing fcron-3.0.1-r2 into /var/tmp/portage/sys-process/fcron-3.0.1-r2/image/

man:
gzipping man page: bitstring.3
gzipping man page: fcron.8
gzipping man page: fcron.conf.5
gzipping man page: fcrontab.5
gzipping man page: fcrondyn.1
gzipping man page: fcrontab.1
strip: strip --strip-unneeded
   usr/sbin/fcron
   usr/bin/fcrontab
   usr/bin/fcronsighup
   usr/bin/fcrondyn
* checking 31 files for package collisions
existing file /usr/share/man/man3/bitstring.3.gz is not owned by this package
* spent 0.0783088207245 seconds checking for file collisions
* This package is blocked because it wants to overwrite
* files belonging to other packages (see messages above).
* If you have no clue what this is all about report it
* as a bug for this package on http://bugs.gentoo.org

package sys-process/fcron-3.0.1-r2 NOT merged


Searching all installed packages for file collisions...
Press Ctrl-C to Stop

 * sys-freebsd/freebsd-share-6.2_rc1:

     '/usr/share/man/man3/bitstring.3.gz'

******************************************
... and probably more.

[Comment 1 Diego Elio Pettenò (RETIRED) 2006-11-27 11:26:44 UTC]

Uhm, why is fcron installing a manpage in section 3?

[Comment 2 Tiziano Müller (RETIRED) 2006-11-27 15:29:00 UTC]

Correction, it seems that FreeBSD's sed doesn't like the "-i", "-e" exists accordingly to the manual.

[Comment 3 SpanKY 2006-11-27 15:30:52 UTC]

Gentoo/FreeBSD should be compensating such that 'sed -i' works ... one hard requirement of Gentoo is that your sed support the -i switch

[Comment 4 Diego Elio Pettenò (RETIRED) 2006-11-27 15:44:03 UTC]

Mike you probably commented on the wrong bug. But no, a requirement of portage is that sed is GNU-sed compatible (in our case it's GNU sed itself).
Nobody said anything about outside ebuilds, where scripts should find if sed is GNU sed or you need gsed or some other tweak.

[Comment 5 SpanKY 2006-11-27 16:31:55 UTC]

no, i was following up to comment #2 ... and yes, i was assuming the sed usage was inside of ebuilds/portage environment

[Comment 6 Diego Elio Pettenò (RETIRED) 2006-11-27 16:49:33 UTC]

Then I suppose it was Tiziano who replied to the wrong bug :)

See bug #156435 where it belonged.

[Comment 7 Tiziano Müller (RETIRED) 2006-11-28 05:01:28 UTC]

yes, it was me :) sorry...

[Comment 8 Pierre Guinoiseau 2007-02-09 18:24:00 UTC]

Well, why is it still not fixed ?
The fcron's bitstring manpage is older than the freebsd one, so wouldn't a plain "rm -f doc/en/man/bitstring.3" be enough to make it works ?

[Comment 9 Wolfram Schlich (RETIRED) 2007-02-13 16:36:38 UTC]

Oh, sorry -- it was fixed in =sys-process/fcron-3.0.2 on 2007-01-18 :-)