Porthole-0.5.0 released

unz · l33t Joined: 28 Jul 2004 Posts: 819 Location: Roma, Italia

Big Up!

_________________
Ma che c'hai là? Sulla spalla!!!! http://lascimmia.it/

RMX · n00b Joined: 22 Aug 2004 Posts: 66

dol-sen · Posted: Wed Nov 01, 2006 3:13 am Post subject:

No, python is not bad. It seems we were trying to add two different types of data together. Our bad

I'll check it out. What version of porthole was that?

Are you using /etc/portage/package.use as a directory? That may have caused the error. If so porthole has not been updated to handle package.* directories properly yet.
I should have that implemented soon. I have finally been able to do some coding again.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

RMX · n00b Joined: 22 Aug 2004 Posts: 66

I'm using porthole-0.5 and no, /etc/portage/package.use isn't directory, it's simple text file.

dol-sen · Posted: Wed Nov 01, 2006 2:51 pm Post subject:

I've found your problem. It is a permissions problem. Porthole-0.5.0 runs as a user and so.

It seems that our get_user_config() default returns an empty tuple for read access denials. If you set your /etc/portage directory permissions for read access by everyone as well as any existing files, that will correct the problem. Any future files added will automatically get the new permissions provided you set the directory permissions correctly.

I will look into changing that code to determine which type needs to be returned for this error.

Kobboi · l33t Joined: 29 Jul 2005 Posts: 672 Location: Belgium

I'm having troubles using the bottom half of the GUI. When I select a package, I get all relevant information in tabs. But selecting another package after that doesn't change anything: all tabs are blank exept for the Dependencies tab, which just lists the name... of the package I had first selected!

Kobboi · l33t Joined: 29 Jul 2005 Posts: 672 Location: Belgium

Problem had something to do with my package.keywords being a directory. I put all of those entries in one package.keywords file and the problem now seems solved

cgmd · Posted: Fri Dec 22, 2006 1:35 am Post subject:

Hi, all...

Ive been using porthole for the past 2 years, and today, with version 0.5.0, I started having a problem.

When I enter a keyword and click "Find", it begins loading package descriptions, as always, but it now fails to progress beyond "19%".

I have no idea what is blocking this process from running to completion...

But, if I run porthole from a terminal as root, it resolves the problem.

Does anyone have any thoughts??

Thanks!
_________________
"Primum non nocere" ---Galen

dol-sen · Posted: Fri Dec 22, 2006 7:00 am Post subject:

Yeah, sorry, porthole-0.5.0 does not have directory support for /etc/portage/package.* files.

I have to finish that support in the cvs version I am trying to get ready to release. It has a number of updates and feature enhancements. It is unfortunate that -0.5.0 is finally unmasked now that it is on the brink of being outdated by portage changes. But it had stayed masked all this time due to a gtk+ bug that caused a segfault under the right conditions. That bug has now been fixed and reached stable gtk+ releases.

Since my wife and I have a small retail business that gets very busy this time of the year I have not been able to do any coding this past week or two. I hope to get a few more things finished, then hide/disable some other unfinished code/feature enhancements and call to start some pre release testing hopefully in the first two weeks of january. I had hoped to have it ready by Christmas

cgmd

Try running porthole as your user from a terminal with the -d flag to turn on debug printing.

cgmd · Posted: Fri Dec 22, 2006 10:36 pm Post subject:

dol-sen wrote:

Naib · Posted: Fri Dec 22, 2006 11:34 pm Post subject:

dol-sen · Posted: Sat Dec 23, 2006 7:24 am Post subject:

cgmd

cgmd · Posted: Sat Dec 23, 2006 7:53 pm Post subject:

dol-sen wrote:

dol-sen · Posted: Sun Dec 24, 2006 7:28 am Post subject:

I was just checking that package on my machine and it is having problems with that one as well as 'dev-util/eclipse-cdt'. That is happening on both the cvs and -0.5.0 versions. I had not set it to load the descriptions in -0.5.0, but it is not finding the ebuilds and other data for those.

I will check out porthole's code and see if maybe it is a portage bug.

Stay tuned for updates on this problem.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Sun Dec 24, 2006 8:21 am Post subject:

I don't know why, but so far portage seems like it may have an intermittent bug. What versions of portage do you have on your laptop and desktop?
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Sun Dec 24, 2006 10:07 am Post subject:

I found a fix

If you want to fix your copy of porthole-0.5.0 edit '/usr/lib/python2.4/site-packages/porthole/portagelib.py' line 768

cgmd · Posted: Sun Dec 24, 2006 9:37 pm Post subject:

dol-sen wrote:

1ino1eum_4the_win · Tux's lil' helper Joined: 07 May 2006 Posts: 92

hello.
I was looking for a remplacement for emerge (emerge -av ebuild, emerge -auvDN world, really basics command).
And I'm really suprised of this Porthole, as I even manage use flags with it !! I love it !

So now I think I can use it instead of emerge ! Great !

Now there is just one thing : config files, that need me to run dispatch-conf as root in a term.
Wouldn't be a solution for porthole , to handle config files, so we could use it alone, without anything else, to manage our ebuilds?

Another question :
right now for exemple, if I do eix-sync && emerge -auvDN world , I'm uptodate, and have no ebuild to upgrade.
but if I sync with porthole, then do upgrade, it will show me that I have some dependancies not uptodate (but not to upgrade by default).

Do I forget something?
tkx

dol-sen · Posted: Mon Dec 25, 2006 3:26 pm Post subject:

1ino1eum_4the_win

Thank you, from all those that have worked on/contributed to porthole

A config file update tool has been talked about before. I would love to add one to porthole, I have even thought about how to do it many times. Unfortuneately I have only so much time and this past year I have not had much time to work on porthole. Porthole has a plug-in system that will allow something like a config editor to be added to porthole without the need to be fully integrated into porthole's code base. This would be the best way to add that functionality. A config editor would need to be independantly changed as bugs are fixed, or portage changes require. If designed properly it could be run independanly from porthole as well.

Dependencies: If you wish to upgrade dependencies that is your choice, just like the -D switch in your emerge example. Porthole merely shows that there are upgrades available. One thing you should do when upgrading frequently is run rev-dep-rebuild to check for and repair broken packages.

cgmd

I'll check it out. It looks like a similar error. Also the bug has now been fixed in portage svn

In my system there is no package called app-admin/tmp. Is it in an overlay on your system? There are 2 packages with tmp in their name: app-admin/tmpreaper, app-admin/tmpwatch.

If you wish for it to not stall when it gets an error like that then edit the file again and put a '#' in front of the line File

cgmd · Posted: Mon Dec 25, 2006 6:26 pm Post subject:

dol-sen wrote:

1ino1eum_4the_win · Tux's lil' helper Joined: 07 May 2006 Posts: 92

Hi !
i really like porthole and I use it everytime I want to install/remove an application, set my package.keyword/use ,etc ... I even use it to set my USEflags in my make.conf, as I've tested it and it works great !
However, I still use the command line to do an emerge -auvDN world, because I'll need to do a dispatch-conf after (but maybe with the etc-proposals plugin, porthole will be usable to do en emerge -auvDN then update the conf file :p)

Anyway, I was just wonderring :
for the moment , as porthole need to be launche as a root to set up USEflags, keywowrds, and emerge/unemerge, I usualy launch an xterm, then log in root, then launch porthole.

So I would like to know if there is a way to, you know, when you launch an application that need to be root, have this little window popping up, asking for the root password (the one you have when you launch something from the system/administration menu from gnome). That would be awesome.
Thank

i92guboj · Posted: Mon Mar 12, 2007 3:28 pm Post subject:

You just need to run that little application with porthole as an argument.

For the kde dialog you'd do:

1ino1eum_4the_win · Tux's lil' helper Joined: 07 May 2006 Posts: 92

wonderfull, I've set a link in my toolbar :

dol-sen · Posted: Mon Mar 12, 2007 10:06 pm Post subject:

Porthole can also use gksu/gksudo internally for saving changes to config files if it is run as a user. Edit the preferences for the graphical su/sudo program you wish it to use when it needs to save config changes.

Remember that -0.5.0 does not yet support using the package.* files as directories. I am almost finished those changes and a few others for the next release.

If you do wish to run porthole as root then edit the menu launcher command to "gksu porthole"
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

1ino1eum_4the_win · Tux's lil' helper Joined: 07 May 2006 Posts: 92

hum, actually, there is a problem :

I can launch porthole as root (in command line or gksu that doens't matter), then do everything EXECPT clicking on web link of programms, because obviously the rest of my
session is with my own user and not root.

So the better solution would be using sudo.
However, while using sudo, you can only emerge/unemege.
You can't update package.keyword, package.use, or make.conf. Porthole ask for the password (because of sudo) but it seems that my package.* are not updated.