Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 736090 - media-sound/lilypond-9999 - README.txt is no longer present upstream causing the "dodoc" phase of the install to fail
Summary: media-sound/lilypond-9999 - README.txt is no longer present upstream causing ...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Scheme Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-06 01:08 UTC by Allan Bjorklund
Modified: 2020-08-06 04:50 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Allan Bjorklund 2020-08-06 01:08:22 UTC
The ebuild file specifically lists README.txt as a required documentation item, but it is no longer present in the source.  (Upstream github no longer has it.)

This causes an installation failure.

I was able to resolve it by removing README.txt from the DOCS variable in the ebuild file in my personal local portage repo.

Reproducible: Always

Steps to Reproduce:
1.emerge lilypond
2.
3.
Actual Results:  
Lilypond was not installed.

Expected Results:  
Successful install of lilypond.

The error:

>> Install media-sound/lilypond-9999 into /var/tmp/portage/media-sound/lilypond-9999/image
make -j5 -l4 DESTDIR=/var/tmp/portage/media-sound/lilypond-9999/image vimdir=/usr/share/vim/vimfiles install 
 * Fixing shebang in /usr/bin/convert-ly.
 * Fixing shebang in /usr/bin/lilypond-book.
 * Fixing shebang in /usr/bin/abc2ly.
 * Fixing shebang in /usr/bin/etf2ly.
 * Fixing shebang in /usr/bin/midi2ly.
 * Fixing shebang in /usr/bin/musicxml2ly.
 * Fixing shebang in /usr/bin/lilysong.
 * Fixing shebang in /usr/bin/lilymidi.
Traceback (most recent call last):
  File "/usr/lib/portage/python3.7/doins.py", line 611, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/usr/lib/portage/python3.7/doins.py", line 602, in main
    os.path.dirname(source)):
  File "/usr/lib/portage/python3.7/doins.py", line 450, in _doins
    return install_runner.install_file(source, os.path.dirname(dest))
  File "/usr/lib/portage/python3.7/doins.py", line 386, in install_file
    return self._ins_runner.run(source, dest_dir)
  File "/usr/lib/portage/python3.7/doins.py", line 195, in run
    sstat = os.stat(source)
FileNotFoundError: [Errno 2] No such file or directory: b'README.txt'
 * ERROR: media-sound/lilypond-9999::gentoo failed (install phase):
 *   dodoc failed
 * 
 * If you need support, post the output of `emerge --info '=media-sound/lilypond-9999::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=media-sound/lilypond-9999::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/media-sound/lilypond-9999/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-sound/lilypond-9999/temp/environment'.
 * Working directory: '/var/tmp/portage/media-sound/lilypond-9999/work/lilypond-9999'
 * S: '/var/tmp/portage/media-sound/lilypond-9999/work/lilypond-9999'

 * Messages for package media-sound/lilypond-9999:

 * ERROR: media-sound/lilypond-9999::gentoo failed (install phase):
 *   dodoc failed
 * 
 * If you need support, post the output of `emerge --info '=media-sound/lilypond-9999::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=media-sound/lilypond-9999::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/media-sound/lilypond-9999/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-sound/lilypond-9999/temp/environment'.
 * Working directory: '/var/tmp/portage/media-sound/lilypond-9999/work/lilypond-9999'
 * S: '/var/tmp/portage/media-sound/lilypond-9999/work/lilypond-9999'
Comment 1 Mike Gilbert gentoo-dev 2020-08-06 01:20:22 UTC
In the future, please mention the category/package name in the bug summary.
Comment 2 Miroslav Šulc gentoo-dev 2020-08-06 04:50:00 UTC
this has already been fixed in https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=abd576f7129eb1e005a83f71c1c9bd59b31ceb70