emerging pyro-3.3 fails: changing mode of /var/tmp/portage/pyro-3.3/image/usr/bin/rns to 755 changing mode of /var/tmp/portage/pyro-3.3/image/usr/bin/wxnsc to 755 changing mode of /var/tmp/portage/pyro-3.3/image/usr/bin/xnsc to 755 Install finished. ACCESS DENIED rename: /usr/bin/esd mv: cannot move `/usr/bin/esd' to `/usr/bin/pyroesd': Permission denied man: prepallstrip: strip: i686-pc-linux-gnu-strip --strip-unneeded strip: i686-pc-linux-gnu-strip --strip-unneeded >>> Completed installing pyro-3.3 into /var/tmp/portage/pyro-3.3/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-dev-python_-_pyro-3.3-27295.log" rename: /usr/bin/esd -------------------------------------------------------------------------------- tim@laptop ~ $ Reproducible: Always Steps to Reproduce: 1. 2. 3.
You neglected to post emerge --info output as instructed to when filing the bug.
no emerge --info, because it was not needed: --- pyro-3.3.ebuild.~1~ 2005-02-07 05:13:39.000000000 +0000 +++ pyro-3.3.ebuild 2005-09-15 11:16:37.317084040 +0000 @@ -30,5 +30,5 @@ cp -r ${S}/examples ${D}/usr/share/doc/${PF} dohtml -r docs/* - mv /usr/bin/esd /usr/bin/pyroesd + mv ${D}/usr/bin/esd ${D}/usr/bin/pyroesd } (sorry for cut&paste of the patch, but it's trivial, and i'm quite busy at the moment)
(In reply to comment #2) > - mv /usr/bin/esd /usr/bin/pyroesd > + mv ${D}/usr/bin/esd ${D}/usr/bin/pyroesd Ooops. Hmm, no idea why it's wrong in one ebuild and correct in the other two.
This bug was fixed more than year ago. Unfortunately no one cared to mark fixed ebuilds stable. Arch teams: please take a look.
the latest stable version on x86 is 3.3, which isn't keyworded at all on amd64 and ppc, so what do we have to mark stable exactly? till now, the rule was "don't mark stable before maintainer did"...
> "don't mark stable before maintainer did"... Well, I did. Just do cvs up. :-)
i see... amd64 done then
ppc stable
Thanks!
