Porthole-0.3 Released!

Message

tuxlearner · Post by **tuxlearner** » Sun Apr 04, 2004 10:53 am

great effort mate

IWBCMAN · Post by **IWBCMAN** » Sun Apr 04, 2004 2:21 pm

perhaps you guys could put in a right-click menu option when one selects a package-from this menu one could a) display/set current USE flags and b) display/set current use flags for the selected package. Here is a totally primitive glade-inspire snapshot of this idea...

http://iwbcman.homelinux.org/Screenshot-2.jpg

bicolao · Post by **bicolao** » Sun Apr 04, 2004 5:19 pm

IWBCMAN wrote: http://iwbcman.homelinux.org/Screenshot-2.jpg

A listview of USE flags is simplier, IMHO.

dol-sen · Post by **dol-sen** » Sun Apr 04, 2004 11:26 pm

We are planning on adding use flag editing and package version selection which would imply ACCEPT_KEYWORDS= & /etc/portage/package.unmask additions.

As for right click menus, Daniel & I discussed having right click menus early on in the new terminal window development. But it was not very clear how to implement them in pygtk. We decided to wait untill we had the terminal quite functional before figuring it out. Once we know how to implement them we can make view dependant popup menus. I like & often use right click menus when available. For the time being you will have to use the "Run Custom Command" menu option to do command line overrides of ACCEPT_KEYWORDS= & USE= for emerging packages.

The terminal window tabs have a default right click menu inherited from the gtk.Textview, they have select all, copy available. The gtk clipboard docs are sparse and the brief module descriptions not clear as to how to implement so we had to remove theose from our edit menu for now. If anyone out there knows how to use the clipboard functions, DON'T BE SHY Help will be glady accepted.

Hypnos · Post by **Hypnos** » Sun Apr 04, 2004 11:53 pm

dol-sen wrote:[...] If anyone out there knows how to use the clipboard functions, DON'T BE SHY Help will be glady accepted.

I've just used the reference manual in the past:

http://developer.gnome.org/doc/API/2.0/ ... oards.html

You get the clipboard with gtk_clipboard_get (or widget-specific convenience functions gtk_widget_get_clipboard, esp. useful if you create special-purpose clipboards).

You then write to the clipboard with gtk_clipboard_set_text

(This is all by reference, of course)

dgt84 · Post by **dgt84** » Wed Apr 14, 2004 3:43 pm

I've just updated the ebuilds for Porthole. Version 0.3-r1 is now available, with [hopefully] the correct dependencies and an update patch to bring everyone to the current cvs. Try it out, and be sure to report bugs to us! I've also submitted the ebuild to bugs.gentoo.org, so if it's ok it will be in the official Portage tree soon.

dol-sen · Post by **dol-sen** » Thu Apr 15, 2004 6:07 am

One of the changes in this revision is sticky (vertical) scrollbars, that will allow you to follow progress in any of the tabs (exept the queue tab) or disconnect it and position it manually. So far the only problem I've found is sometimes it won't reconnect to autoscroll properly when the buffer gets quite large. I am trying to figure out whether I need to change the code slightly or it is a bug in gtk.

(just a side note, I upgraded openoffice and a couple other small packages using porthole the other day. Total memory used climbed to 87.1Mb, 145,184 lines of text in the process buffer. Looks like we'll need to save the buffer to a file to limit how much main memory it uses. Other than the small autoscroll problem porthole did it without a hitch.)

The second change I made was to add -p flag checking to custom run commands in order to generate the time estimates for emerges. Rather than the --pretend flag only. Now you can take your pick.

As always try it out and report any strange or unexpected behavior. If you find any messages that should be copied to the info tab or wherever or some that should not, report them and attach the saved log file so we can refine the regular expressions used to filter out the messages/errors/warnings/etc..

dgt84 · Post by **dgt84** » Sat May 01, 2004 9:05 pm

Just thought I'd mention that Porthole-0.3-r1 just made it into Portage and is unmasked now! Congratulations, everyone

Komunjara · Post by **Komunjara** » Sat May 01, 2004 9:06 pm

i seem to get a lot of segmentation faults. They occur when after unmerge has completed. I am not sure what kind of info you guys need to make this useful, so just tell me what to do to get a better explenation.

sickboy2583 · Post by **sickboy2583** » Sun May 02, 2004 3:07 pm

I get Segmentation faults too - after emerge sync it just crashes.

Portage 2.0.50-r6 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040420-r0, 2.6.5-gentoo)
=================================================================
System uname: 2.6.5-gentoo i686 AMD Athlon(tm) XP 3200+
Gentoo Base System version 1.4.10
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -pipe -O3 -fomit-frame-pointer "
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -pipe -O3 -fomit-frame-pointer "
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa apm arts avi berkdb bluetooth cdr crypt cups dvd encode esd foomaticdb gdbm gif gnome gphoto2 gpm gtk gtk2 guile imlib java jpeg libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl slang spell ssl svga tcpd truetype x86 xml2 xmms xv zlib"

Skrot · Post by **Skrot** » Mon May 03, 2004 6:45 am

Hey, this program is great! Nice one!

But I have a problem when I press on upgrade, say no, and then cancel it. I know it says "Please Wait!" or similar, but still... What happens is that I get this error whenever I go to select another package to get information from it:

Code: Select all

Traceback (most recent call last):
  File "/usr/lib/porthole/views.py", line 196, in _clicked
    self._category_changed(category)
  File "/usr/lib/porthole/mainwindow.py", line 384, in category_changed
    raise Exception("The programmer is stupid.");
Exception: The programmer is stupid.

Nothing else happens except for that error. ie. I have to restart the program to be able to use it again.

Oh I'm using the latest 0.3-r1 version.

Cheers

dol-sen · Post by **dol-sen** » Tue May 04, 2004 6:30 am

Sorry, we haven't been around so much lately. We all seem to have been busy with life and things lately. As for the segmentation faults. It is something that I thought was fixed long ago, untill I got one a couple of days ago. I don't know what caused it.

The best way to run porthole for debugging info is to run it from a terminal

Code: Select all

 
# porthole -d

or if not installed & running a local cvs copy

# cd porthole
# ./porthole -l -d

The latter one is for running a local cvs copy (-l) .

it will print a number of debug statements in the terminal window which help us track what it was doing. We add the debug prints where and how many we need to help trace problems.

For those of you following the cvs at sourceforge. I just committed a number of fixes.

++++ Fixed it to get the entire environment including any proxy settings, buildpackage features, etc.. Porthole then adds any additional features it needs and passes that along to any process it runs in the terminal.

++++ fixed the version number sorting for the display of all the ebuilds available in the portage tree. Completely new functions that breakdown the ebuild version numbers and pad them out to the same length for proper sorting.

++++ killing a process now sends a <ctrl>C to the running process so that emerge can abort gracefully, saving any info it needs to for resume to work.

++++ Several resume bugs fixed, It all works fine now.

++++ New resume menu item ==> Skip Queue Entry to skip past a killed process to continue with the remaning queue entries.

The anaonymous cvs should show the changes in aprox. 12 hours.

Download and check it out for more bugs I may have missed. Submit the bugs to porthole bugs at the sourceforge site.

I'll look into what might be causing the segfaults. We also have several patches for bugfixes and features to intergrate submitted by some porthole users. Look for them coming soon.

chutz · Post by **chutz** » Sat May 08, 2004 2:12 am

metnik wrote:I tried to emerge gnome-vfs-sftp-0.1.2 with Porthole, but It writes some errors..

000005 /usr/sbin/ebuild.sh: line 13: rm: command not found
...
000151 ./usr/share/doc/gnome-vfs-sftp-0.1.2/AUTHORS.gz

I have a similar problem. However, I mistakenly posted it in the porthole-0.2 thread. I repost it here:

chutz wrote:I tried porthole-0.3-r1, but every time I try to emerge a package I get:

Code: Select all

/usr/sbin/ebuild.sh: line 13: rm: command not found
/usr/sbin/ebuild.sh: line 28: tee: command not found
/usr/sbin/ebuild.sh: line 30: rm: command not found

and again, and again.... After sticking a ">>> echo PATH=$PATH" in the beginning of /usr/sbin/ebuild.sh, this is what I get in the Porthole-Terminal:

Code: Select all

000001 *** emerge --nospinner gnome-extra/gxmms ***
000002 Calculating dependencies  ...done!
000003 >>> emerge (1 of 1) gnome-extra/gxmms-0.1.0 to /
000004 >>> PATH=/usr/lib/portage/bin:
000005 >>> md5 src_uri ;-) gxmms-0.1.0.tar.gz
000006 >>> PATH=/usr/lib/portage/bin:
000007 /usr/sbin/ebuild.sh: line 13: rm: command not found
000008 /usr/sbin/ebuild.sh: line 28: tee: command not found
000009 /usr/sbin/ebuild.sh: line 30: rm: command not found
000010 >>> PATH=/usr/lib/portage/bin:
000011 /usr/sbin/ebuild.sh: line 13: rm: command not found
000012 /usr/sbin/ebuild.sh: line 28: tee: command not found
000013 /usr/sbin/ebuild.sh: line 30: rm: command not found
000014 >>> PATH=/usr/lib/portage/bin:
000015 /usr/sbin/ebuild.sh: line 13: rm: command not found
000016 *** process killed ***

/var/tmp/portage/gxmms-0.1.0/temp/environment does contain a proper PATH. Portage is 2.0.50-r6

I started porthole from the command-line as root.

darkarchon · Post by **darkarchon** » Sat May 08, 2004 5:25 am

one request...

when porthole starts up... can u show a progress bar ? right now there is an incrementing list of packages wat at the bottom of the list.... a progress bar offers more eye candy...

perhaps right underneath the top buttons...

or if not a progress bar perhaps a dialog box with a little "watch" telling the user to "please wait" while the packages are being counted in.........

good thing so far... looking for it to get even better... keep up all the hard work!

darkarchon · Post by **darkarchon** » Sat May 08, 2004 5:31 am

i was trying to emerge -C kdearts thru porthole. i got:

Code: Select all

tux etc # porthole

(porthole:12791): Gtk-CRITICAL **: file gtklabel.c: line 946 (gtk_label_set_text): assertion `GTK_IS_LABEL (label)' failed

(porthole:12791): Gtk-CRITICAL **: file gtklabel.c: line 946 (gtk_label_set_text): assertion `GTK_IS_LABEL (label)' failed
Segmentation fault

dol-sen · Post by **dol-sen** » Sat May 08, 2004 7:18 am

chutz

I have had those rm not found errors before, but did not know what caused them. I believe it was because we were not passing the path variable in the environment we were giving emerge. That has now been changed to pass all of the environment plus whatever else we needed to emerge.

I will re-check to see if that error no longer appears.

look forward to a big bugfix release next week. just a few more bugs I want to squash first.

darkarchon

I am going to leave new features such as that to the next version release, not include that in this next bugfix release. We already have a popup with a progress bar we should be able to use for that.

As for your error, it looks like a gtk bug, poked at by porthole. I have not seen that one before. Nor have I tried an emerge -C in porthole before. You must have enetered that from the run custom command. "emerge -c" hmm... something I may have to try

I just did a few more bugfixes, mostly ui releated, but unfortunately the anon-cvs is about 12 hours or so behind the dev-cvs access.
So you won't be able to get them yet.

Thank you.

And as I said look forward to a bug fix release next week.

sickboy2583 · Post by **sickboy2583** » Sat May 08, 2004 10:54 am

Tried Porthole 0.3-r1 agian today to see what the segmentation faults I was getting were, so I could post the results here - Guess what it runs perfect now !

So I do not know what was causimg the segmenation faults - maybe a library has since been upgraded and fixed the problem (who knows !).

Anyway this is an excellent program, it is really usefull for browsing/searching the portage tree as well as updating your system.

Keep up the good work

chutz · Post by **chutz** » Sat May 08, 2004 11:34 am

dol-sen wrote:chutz

I have had those rm not found errors before, but did not know what caused them. I believe it was because we were not passing the path variable in the environment we were giving emerge. That has now been changed to pass all of the environment plus whatever else we needed to emerge.

I will re-check to see if that error no longer appears.

look forward to a big bugfix release next week. just a few more bugs I want to squash first.

Tried the cvs today. Works fine indeed.

darkarchon · Post by **darkarchon** » Sat May 08, 2004 3:19 pm

dol-sen wrote:As for your error, it looks like a gtk bug, poked at by porthole. I have not seen that one before. Nor have I tried an emerge -C in porthole before. You must have enetered that from the run custom command. "emerge -c" hmm... something I may have to try

actually i just searched for an installed packaged. then i hit the "-" (minus sign) to unemerge it. and it popped up the error. but it did manage to remove the package. i went back into porthole and the package was removed.

also, another quickie bug. sometimes it says "(undefined)" at the bottom where it counts all the packages. this is in a working state. perhaps you can look into it.

thanks again!

dol-sen · Post by **dol-sen** » Sat May 08, 2004 6:34 pm

I have just tried your pkg search/unmerge without incident:

Code: Select all

           ===> new search_term = :edb
MAINWINDOW: view_filter_changed()
MAIN: Showing search results
MAINWINDOW: clear_notebook()
MAINWINDOW: set_package_actions_sensitive(0)
MAINWINDOW: package_changed()
MAINWINDOW: set_package_actions_sensitive(1)
SUMMARY: update_package_info(); versions
TERMINAL: terminal_notebook() new self.visible_tablist:
[0]
TERMINAL: get & connect to vadjustments
TERMINAL: start_queue()
TERMINAL: There are pending processes, running now... [edb]
TERMINAL: terminal_notebook() new self.visible_tablist:
[0, 3]
TERMINAL: self.term.visible_tablist
[0, 3]
TERMINAL: cntrl-C sent to process
TERMINAL: leaving kill()
TERMINAL: leaving kill_process

I have done quite a few bug fixes this past week. Perhaps it was fixed as well.

I have never noticed the undefined error in the status bar, but I will look into it.

darkarchon · Post by **darkarchon** » Sat May 08, 2004 8:33 pm

I have never noticed the undefined error in the status bar, but I will look into it.

start up porthole.
after it has finished reading packages select "upgradable packages" from the "view".
note that the status bar says "(undefined)".
even after the upgradeable packages have finished downloading the bar still says "(undefined)"

thanks for the hard work my man!

dol-sen · Post by **dol-sen** » Sun May 09, 2004 6:25 am

Thanks for the howto. Well I checked it out, followed the code thru and I found the source. It actually is not an error message. It was coded into the statusbar update. The text is initialized to "(undefined)" then changed according to the view that is active. There is no code in place to change it to something apropriate for the view.

I was not involved with the coding of the main window for the most part and never had much reason to snoop very close before. I have changed the message to something a little more meaningfull for now. We will wait to the -0.4 release to implement a statusbar for the upgradeable view. That way there should be very few bugs in the porthole code we plan to release this week. There is probably a few gtk bugs though.

Schnacki · Post by **Schnacki** » Tue May 11, 2004 7:05 am

Didn't someone write, that porthole was unmasked in portage by now? I have it in my tree, but all 3 versions are masked by the ~x86-Keyword.

dgt84 · Post by **dgt84** » Tue May 11, 2004 8:54 am

Schnacki wrote:Didn't someone write, that porthole was unmasked in portage by now? I have it in my tree, but all 3 versions are masked by the ~x86-Keyword.

It's no longer hard-masked by packages.mask is what I meant

jean-michel · Post by **jean-michel** » Tue May 11, 2004 1:42 pm

Regarding the question of a good interface, one possibility would be a selectable list of radio buttons that can be toggled on and off for each use flag in the IUSE="" variable (this is a small subset of all USE flags, naturally). Will this scale to the ebuild with the longest IUSE="" list? (not sure what this would be ... transcode maybe?).

Perhaps each entry has three buttons, only one of which can be selected.
"default" (don't override default setting, whatever that is), "on" (+), and "off" (-). Current status could be read from the output of emerge -pv package, masked with the system defaults.

Porthole-0.3 Released!

Interface idea