Bug 630454

Summary:	dev-vcs/gitolite-gentoo-3.6.1-r1 fails install cannot stat 'README.markdown': No such file or directory
Product:	Gentoo Linux	Reporter:	Kent Fredric (IRC: kent\n) (RETIRED) <kentnl>
Component:	Current packages	Assignee:	Christian Ruppert (idl0r) <idl0r>
Status:	RESOLVED OBSOLETE
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Kent Fredric (IRC: kent\n) (RETIRED) gentoo-dev

2017-09-09 09:46:22 UTC

I don't use this for anything, just this error turned up while testing absolutely everything for obvious problems.

>>> Install gitolite-gentoo-3.6.1-r1 into /var/tmp/portage/dev-vcs/gitolite-gentoo-3.6.1-r1/image/ category dev-vcs
/usr/bin/install: cannot stat 'README.markdown': No such file or directory
!!! dodoc: README.markdown does not exist
 * ERROR: dev-vcs/gitolite-gentoo-3.6.1-r1::gentoo failed (install phase):
 *   dodoc failed
>>> Install gitolite-gentoo-3.6.1-r1 into /var/tmp/portage/dev-vcs/gitolite-gentoo-3.6.1-r1/image/ category dev-vcs
/usr/bin/install: cannot stat 'README.markdown': No such file or directory
!!! dodoc: README.markdown does not exist
 * ERROR: dev-vcs/gitolite-gentoo-3.6.1-r1::gentoo failed (install phase):
 *   dodoc failed


the version logically before it and the version logically after it don't suffer this problem. Just this quaint version :)


find /var/tmp/portage/dev-vcs/gitolite-gentoo-3.6.1-r1/ | grep README
/var/tmp/portage/dev-vcs/gitolite-gentoo-3.6.1-r1/work/gitolite-gentoo-3.6.1/README.Developer
/var/tmp/portage/dev-vcs/gitolite-gentoo-3.6.1-r1/work/gitolite-gentoo-3.6.1/README.Gentoo
/var/tmp/portage/dev-vcs/gitolite-gentoo-3.6.1-r1/work/gitolite-gentoo-3.6.1/README.txt
/var/tmp/portage/dev-vcs/gitolite-gentoo-3.6.1-r1/work/gitolite-gentoo-3.6.1/t/README


 diff -Naur gitolite-gentoo-3.6.1{,-r1}.ebuild | grep -i READ
-       dodoc README.txt CHANGELOG
+       dodoc README.markdown CHANGELOG


*shrug*

Comment 1 Christian Ruppert (idl0r) gentoo-dev

2022-05-19 20:04:45 UTC

From what I can see that's already fixed. Closing.