Bug 628026

Summary:	www-client/seamonkey-2.48-r1 - sed: can't read /usr/share/enigmail/install.rdf: No such file or directory
Product:	Gentoo Linux	Reporter:	Martin Mokrejš <mmokrejs>
Component:	Current packages	Assignee:	Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c>
Status:	RESOLVED OBSOLETE
Severity:	normal	CC:	mozilla
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Martin Mokrejš 2017-08-16 15:11:48 UTC

This version fails during src_install:

make[1]: Leaving directory '/scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/work/seamonkey-2.48/seamonk/suite/installer'
 * PT_PAX marking -m /scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/image//usr/lib64/seamonkey/seamonkey with paxctl
 * PT_PAX marking -m /scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/image//usr/lib64/seamonkey/seamonkey with scanelf
 * PT_PAX marking -m /scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/image//usr/lib64/seamonkey/seamonkey-bin with paxctl
 * PT_PAX marking -m /scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/image//usr/lib64/seamonkey/seamonkey-bin with scanelf
 * PT_PAX marking -m /scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/image//usr/lib64/seamonkey/plugin-container with paxctl
 * PT_PAX marking -m /scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/image//usr/lib64/seamonkey/plugin-container with scanelf
 * XATTR_PAX marking -me /scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/image//usr/lib64/seamonkey/seamonkey with setfattr
 * XATTR_PAX marking -me /scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/image//usr/lib64/seamonkey/seamonkey-bin with setfattr
 * XATTR_PAX marking -me /scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/image//usr/lib64/seamonkey/plugin-container with setfattr
sed: can't read /usr/share/enigmail/install.rdf: No such file or directory
 * /usr/share/enigmail/install.rdf: No such file or directory
 * ERROR: www-client/seamonkey-2.48-r1::gentoo failed (install phase):
 *   <EM:ID> tag for x11-plugins/enigmail could not be found!
 * 
 * Call stack:
 *     ebuild.sh, line 115:  Called src_install
 *   environment, line 4887:  Called die
 * The specific snippet of code:
 *               die "<EM:ID> tag for x11-plugins/enigmail could not be found!";
 * 
 * If you need support, post the output of `emerge --info '=www-client/seamonkey-2.48-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=www-client/seamonkey-2.48-r1::gentoo'`.
 * The complete build log is located at '/scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/temp/build.log'.
 * The ebuild environment file is located at '/scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/temp/environment'.
 * Working directory: '/scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/work/seamonkey-2.48-en-GB'
 * S: '/scratch/var/tmp/portage/www-client/seamonkey-2.48-r1/work/seamonkey-2.48'


# emerge -pv enigmail

Calculating dependencies... done!
[ebuild   R    ] x11-plugins/enigmail-1.9.8.1::gentoo  0 KiB

...

# equery files x11-plugins/enigmail | grep rdf
/usr/share/enigmail/install.rdf
# ls -latr /usr/share/enigmail/install.rdf
ls: cannot access '/usr/share/enigmail/install.rdf': No such file or directory
# ls -latr /usr/share/enigmail/           
total 32
drwxr-xr-x 773 root root 24576 Jul 30 14:17 ..
drwxr-xr-x   2 root root  4096 Aug  7 13:23 modules
drwxr-xr-x   3 root root  4096 Aug  7 13:23 .
#

So I re-emerge enigmail and indeed, now I have:

# ls -latr /usr/share/enigmail/
total 64
drwxr-xr-x 773 root root 24576 Jul 30 14:17 ..
-rw-r--r--   1 root root  1932 Aug 16 17:00 install.rdf
-rw-r--r--   1 root root  9044 Aug 16 17:00 chrome.manifest
drwxr-xr-x   2 root root  4096 Aug 16 17:00 wrappers
drwxr-xr-x   3 root root  4096 Aug 16 17:00 defaults
drwxr-xr-x   2 root root  4096 Aug 16 17:00 chrome
drwxr-xr-x   2 root root  4096 Aug 16 17:00 modules
drwxr-xr-x   2 root root  4096 Aug 16 17:00 components
drwxr-xr-x   7 root root  4096 Aug 16 17:00 .
#


The only conclusion I have that during unmerging of seamonkey the enigmail related plugins were accidentally dropped by portage:

1502092951: Started emerge on: Aug 07, 2017 10:02:30
1502092951:  *** emerge  --sync
1502092951:  === sync
1502092951: >>> Syncing repository 'gentoo' into '/scratch/usr/portage'...
1502092951: >>> Starting rsync with rsync://176.28.50.119/gentoo-portage
1502093002: === Sync completed for gentoo
1502093030:  *** terminating.
1502093115: Started emerge on: Aug 07, 2017 10:05:15
1502093115:  *** emerge  seamonkey
1502093162:  *** exiting unsuccessfully with status '1'.
1502093162:  *** terminating.
1502093233: Started emerge on: Aug 07, 2017 10:07:12
1502093233:  *** emerge  seamonkey
1502093679:  *** exiting unsuccessfully with status '1'.
1502093679:  *** terminating.
1502100634: Started emerge on: Aug 07, 2017 12:10:34
1502100634:  *** emerge  --unmerge firefox
1502100640: === Unmerging... (www-client/firefox-54.0.1)
1502100714:  >>> unmerge success: www-client/firefox-54.0.1
1502100714:  *** exiting successfully.
1502100716:  *** terminating.
1502100717: Started emerge on: Aug 07, 2017 12:11:56
1502100717:  *** emerge  seamonkey
1502100764:  >>> emerge (1 of 2) dev-db/sqlite-3.20.0 to /
1502100770:  === (1 of 2) Cleaning (dev-db/sqlite-3.20.0::/scratch/usr/portage/dev-db/sqlite/sqlite-3.20.0.ebuild)
1502100770:  === (1 of 2) Compiling/Merging (dev-db/sqlite-3.20.0::/scratch/usr/portage/dev-db/sqlite/sqlite-3.20.0.ebuild)
1502100829:  === (1 of 2) Merging (dev-db/sqlite-3.20.0::/scratch/usr/portage/dev-db/sqlite/sqlite-3.20.0.ebuild)
1502100834:  >>> AUTOCLEAN: dev-db/sqlite:3
1502100834:  === Unmerging... (dev-db/sqlite-3.19.3)
1502100838:  >>> unmerge success: dev-db/sqlite-3.19.3
1502100843:  === (1 of 2) Post-Build Cleaning (dev-db/sqlite-3.20.0::/scratch/usr/portage/dev-db/sqlite/sqlite-3.20.0.ebuild)
1502100843:  ::: completed emerge (1 of 2) dev-db/sqlite-3.20.0 to /
1502100843:  >>> emerge (2 of 2) www-client/seamonkey-2.49.2.0_p0 to /
1502100843:  === (2 of 2) Cleaning (www-client/seamonkey-2.49.2.0_p0::/scratch/usr/portage/www-client/seamonkey/seamonkey-2.49.2.0_p0.ebuild)
1502100850:  === (2 of 2) Compiling/Merging (www-client/seamonkey-2.49.2.0_p0::/scratch/usr/portage/www-client/seamonkey/seamonkey-2.49.2.0_p0.ebuild)
1502104947:  === (2 of 2) Merging (www-client/seamonkey-2.49.2.0_p0::/scratch/usr/portage/www-client/seamonkey/seamonkey-2.49.2.0_p0.ebuild)
1502104994:  >>> AUTOCLEAN: www-client/seamonkey:0
1502104994:  === Unmerging... (www-client/seamonkey-2.48_beta1)
1502104998:  >>> unmerge success: www-client/seamonkey-2.48_beta1
1502105014:  === (2 of 2) Post-Build Cleaning (www-client/seamonkey-2.49.2.0_p0::/scratch/usr/portage/www-client/seamonkey/seamonkey-2.49.2.0_p0.ebuild)
1502105014:  ::: completed emerge (2 of 2) www-client/seamonkey-2.49.2.0_p0 to /
1502105014:  *** Finished. Cleaning up...
1502105023:  *** exiting successfully.
1502105026:  *** terminating.
1502108675: Started emerge on: Aug 07, 2017 14:24:35
1502108675:  *** emerge  @preserved-rebuild
1502108725:  *** exiting unsuccessfully with status '1'.
1502108725:  *** terminating.

Comment 1 Ian Stakenvicius (RETIRED) gentoo-dev

2017-08-16 20:05:03 UTC

If you check, you will find that although the x11-plugins/emigmail package might be "installed," there are no actual files on disk.  If you re-emerge x11-plugins/enigmail then the seamonkey install will work.

Thunderburd had a similar issue a few versions ago; although the same fix exists within seamonkey it still on occasion occurs, depending on whether or not a previous seamonkey or thunderbird version decided that it 'owns' the files installed by x11-plugins/enigmail.