Bug 680108 – media-sound/pavucontrol-qt-0.14.1 - lafilefixer: command not found, and with lxqt-base/lxqt-l10n-0.13.0: file collisions in /usr/share/pavucontrol-qt/translations/pavucontrol-qt

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Guy 2019-03-12 10:08:39 UTC]

...

>>> Completed installing pavucontrol-qt-0.14.1 into /var/tmp/portage/media-sound/pavucontrol-qt-0.14.1/image

/etc/portage/bashrc: line 2: lafilefixer: command not found
 * Final size of build directory: 3640 KiB (3.5 MiB)
 * Final size of installed tree:   992 KiB

 * QA Notice: command not found:
 * 
 *      /etc/portage/bashrc: line 2: lafilefixer: command not found
strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment -R .GCC.command.line -R .note.gnu.gold-version
   /usr/bin/pavucontrol-qt
>>> Done.

...

* Detected file collision(s):
 * 
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_as.qm
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_bn_IN.qm
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_ca.qm
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_cs.qm

...

 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_uk.qm
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_zh_CN.qm
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * lxqt-base/lxqt-l10n-0.13.0:0::gentoo
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_as.qm
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_bn_IN.qm
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_ca.qm
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_cs.qm
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_da.qm

...

 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_ml.qm
 *      /usr/share/pavucontrol-qt/translations/pavucontrol-qt_mr.qm
 * 
 * Package 'media-sound/pavucontrol-qt-0.14.1' NOT merged due to file
 * collisions.

[Comment 1 Guy 2019-03-12 10:12:07 UTC]

Created attachment 568756 [details]
build.log

[Comment 2 Guy 2019-03-12 10:15:37 UTC]

# equery b lafilefixer
 * Searching for lafilefixer ... 
sys-apps/portage-2.3.62 (/usr/lib/python3.7/site-packages/portage/tests/lafilefixer)
sys-apps/portage-2.3.62 (/usr/lib64/python3.6/site-packages/portage/tests/lafilefixer)
sys-apps/portage-2.3.62 (/usr/lib64/python2.7/site-packages/portage/tests/lafilefixer)

[Comment 3 Chiitoo 2019-03-12 13:33:42 UTC]

Yeah, I somehow missed adding the blocker for this one...

I'm not sure about the 'lafixer' thing.  Would that not be something you, or some tool added in '/etc/portage/bashrc'?

Thanks for the report!

[Comment 4 Guy 2019-03-12 19:36:27 UTC]

In comment #2, the 'equery b(elongs)' command tells me that 'lafilefixer' is part of the 'portage' package. In my case, there are 3 version - one for each version of python I have enabled. I'm not a dev, but my understanding is that's how it works.

# locate -i 'lafilefixer'
/usr/lib64/python2.7/site-packages/portage/tests/lafilefixer
/usr/lib64/python3.6/site-packages/portage/tests/lafilefixer
/usr/lib64/python3.7/site-packages/portage/tests/lafilefixer

In theory, 'lafilefixer' should always be found.

My guess (and it's only a guess given my strictly end user knowledge) is ether the path to the command is not built correctly or it's being called for a version of python not enabled on my system.

Strictly speaking, lafilefixer is probably not required to begin with but I don't actually know that.

The package did seem to build correctly after all. It just failed on the file collisions with another already installed package.

[Comment 5 Larry the Git Cow 2019-03-12 19:37:38 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cde91197e6293e2e36409e4c1fb1f106ea4c3f3d

commit cde91197e6293e2e36409e4c1fb1f106ea4c3f3d
Author:     Jimi Huotari <[e-mail]>
AuthorDate: 2019-03-12 12:49:44 +0000
Commit:     Andreas Sturmlechner <[e-mail]>
CommitDate: 2019-03-12 19:37:22 +0000

    media-sound/pavucontrol-qt: block 'lxqt-base/lxqt-l10n'
    
    Closes: https://bugs.gentoo.org/680108
    Package-Manager: Portage-2.3.62, Repoman-2.3.12
    Signed-off-by: Jimi Huotari <[e-mail]>
    Closes: https://github.com/gentoo/gentoo/pull/11345
    Signed-off-by: Andreas Sturmlechner <[e-mail]>

 media-sound/pavucontrol-qt/pavucontrol-qt-0.14.1.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

[Comment 6 Chiitoo 2019-03-12 19:52:56 UTC]

(In reply to Guy from comment #4)
> In comment #2, the 'equery b(elongs)' command tells me that 'lafilefixer' is
> part of the 'portage' package. In my case, there are 3 version - one for
> each version of python I have enabled. I'm not a dev, but my understanding
> is that's how it works.
> 
> # locate -i 'lafilefixer'
> /usr/lib64/python2.7/site-packages/portage/tests/lafilefixer
> /usr/lib64/python3.6/site-packages/portage/tests/lafilefixer
> /usr/lib64/python3.7/site-packages/portage/tests/lafilefixer
> 
> In theory, 'lafilefixer' should always be found.
> 
> My guess (and it's only a guess given my strictly end user knowledge) is
> ether the path to the command is not built correctly or it's being called
> for a version of python not enabled on my system.
> 
> Strictly speaking, lafilefixer is probably not required to begin with but I
> don't actually know that.
> 
> The package did seem to build correctly after all. It just failed on the
> file collisions with another already installed package.

Yeah, I'm pretty sure this is something not related to 'media-sound/pavucontrol-qt'.

I wonder if the entries referring to it in your '/etc/portage/bashrc' are remnants of the 'dev-util/lafilefixer' package, that was removed some time ago (see bug 289899 for example).

What are the contents of the file anyway?  I have only things I added myself for per-package 'ccache'.

[Comment 7 Guy 2019-03-12 23:11:03 UTC]

(In reply to Chiitoo from comment #6)
> 
> I wonder if the entries referring to it in your '/etc/portage/bashrc' are
> remnants of the 'dev-util/lafilefixer' package, that was removed some time
> ago (see bug 289899 for example).
> 
> What are the contents of the file anyway?  I have only things I added myself
> for per-package 'ccache'.

I had pavcontrol-qt-0.14.1 also fail on my server during 'emerge -uND @world'. It's '/var/tmp/portage/media-sound/pavucontrol-qt-0.14.1/temp/build.log' had no references to 'lafilefixer'. It failed only for the file collisions.

My workstation was built pre 2014 while my server was built in 2017. 

In fact, I'm not certain where to check the original build date for my workstation since I carried it over as a combination stage4 install/moved hard drive from a previous PC. So yes, 'lafilefixer' probably represents an artifact from a previous era.

At this point, it is reasonable to assume 'lafilefixer' is coincidentally spurious.