Problem with Portato on latest update (solved)

[rhomp2002]

When I tried to emerge an updated portato I got this:

emerge -u portato
Note: The repository at /usr/portage/local/layman/portato does not have a profiles/repo_name entry.
This can reduce the functionality of the repository in some cases.
Calculating dependencies... done!
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.



When I tried to emerge portato I got this error:

emerge portato
Note: The repository at /usr/portage/local/layman/portato does not have a profiles/repo_name entry.
This can reduce the functionality of the repository in some cases.
Calculating dependencies... done!
>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) app-portage/portato-9999 to /
* checking ebuild checksums ... [ ok ]
* checking auxfile checksums ... [ ok ]
* checking miscfile checksums ... [ ok ]
>>> cfg-update-1.8.2-r1: Creating checksum index...
>>> Unpacking source...
Note: The repository at /usr/portage/local/layman/portato does not have a profiles/repo_name entry.
This can reduce the functionality of the repository in some cases.
*
* ERROR: app-portage/portato-9999 failed.
* Call stack:
* ebuild.sh, line 1647: Called dyn_unpack
* ebuild.sh, line 768: Called qa_call 'src_unpack'
* ebuild.sh, line 44: Called src_unpack
* ebuild.sh, line 1327: Called subversion_src_unpack
* subversion.eclass, line 254: Called subversion_fetch
* subversion.eclass, line 179: Called die
*
* subversion.eclass: ESVN_REPO_URI (or specified URI) and working copy's URL are not matched.
* If you need support, post the topmost build error, and the call stack if relevant.

[wolfden]

You need to delete the folder

/usr/portage/distfiles/svn-src


than try it again



do note u need root to delete that folder

[rhomp2002]

Should there be a profiles file at /usr/portage/local/layman/portato?

That is what it seems is missing but I am not sure how to get one there. It seems to be looking for a profiles file or a repo_name file and neither is present. No idea what knocked it out because portato was working fine until I did the last update.

[Necoro]

rhomp2002:
try the following:

Code: Select all

rm -rf /usr/portage/distfiles/svn-src
layman -d portato
layman -o http://portato.sf.net/layman.xml -a portato
emerge -uav portato

And no - there should not be a profile file

[rhomp2002]

I did that and am still getting the same message about the profiles/repo_name in the repository at

/usr/portage/local/layman/portato

It does say it merged

The repository at /usr/portage/local/layman/portato does not have a profiles/repo_name entry.
This can reduce the functionality of the repository in some cases.
* Byte compiling python modules for python-2.4 .. ... [ ok ]
>>> app-portage/portato-9999 merged.
>>> Recording app-portage/portato in "world" favorites file...

>>> No packages selected for removal by clean
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.


Now I will see if I can run it.

[Necoro]

Some googling said this: http://www.nabble.com/Overlays-does-not ... 48438.html

Thus - this message is not really important ... but for convenience I added a repo_name file to the overlay (as I knew now what to do ) ...

[rhomp2002]

It seems to be working OK. When it is done I might re-emerge it to pick up the repo_name you put there so it will get rid of that error. Will let you know how it works out.

[Necoro]

It seems to be working OK. When it is done I might re-emerge it to pick up the repo_name you put there so it will get rid of that error. Will let you know how it works out.

Not re-emerge, but re-sync of the overlay

[wolfden]

rhomp2002:
try the following:

Code: Select all

rm -rf /usr/portage/distfiles/svn-src
layman -d portato
layman -o http://portato.sf.net/layman.xml -a portato
emerge -uav portato

And no - there should not be a profile file

doh! I put the wrong folder in my post, but I edited my post, was too sleepy eyed when I posted

Glad you got it sorted rhomp2002

[rhomp2002]

It worked and the message is now disappeared. Thanks to you both for ll your help.