Re: [DebianGIS] Web pages showing tasks
Andreas Tille wrote: Thanks for your input. The obviousely missing feature in the tasks page is the information about the versions in the different distributions (including backport.org). It is definitely planed for a later version to add some information about availablility in stable / testing / unstable. Including backports.org is a nice idea which I not have thought of - but it sounds interesting. that is quite simple (including backports.org), just add a link to: http://packages.debian.org/package name the name can even be sloppy, e.g. http://packages.debian.org/gdal Hamish Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [DebianGIS] Web pages showing tasks
On Fri, 22 Feb 2008, Hamish wrote: that is quite simple (including backports.org), just add a link to: http://packages.debian.org/package name the name can even be sloppy, e.g. http://packages.debian.org/gdal I dont's think so. IMHO the link should only be added if the package really exists in backports which requires scanning the Sources / Packages file from there which is not yet done. (I don't say that it is much effort but it is just not done because I do not regard this as high priority - volunteers are welcome as always...) Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [DebianGIS] Web pages showing tasks
On Fri, Feb 22, 2008 at 12:49:07AM -0800, Hamish wrote: Andreas Tille wrote: Thanks for your input. The obviousely missing feature in the tasks page is the information about the versions in the different distributions (including backport.org). It is definitely planed for a later version to add some information about availablility in stable / testing / unstable. Including backports.org is a nice idea which I not have thought of - but it sounds interesting. that is quite simple (including backports.org), just add a link to: http://packages.debian.org/package name the name can even be sloppy, e.g. http://packages.debian.org/gdal Well, linking is the easiest way, I would prefer a summary page because it is more useful that looking every project on the general packages.debian.org or packages.qa.debian.org site. About that I would think some web services which can be used to return specific information in well formed XML for the packages.* sites... Something that bugs.d.o already does, but I dunno if it is also available for other sites. Surely much better than re-inventing the wheel each time... -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [DebianGIS] Web pages showing tasks
On Fri, 22 Feb 2008, Francesco P. Lovergine wrote: Well, linking is the easiest way, I would prefer a summary page because it is more useful that looking every project on the general packages.debian.org or packages.qa.debian.org site. About that I would think some web services which can be used to return specific information in well formed XML for the packages.* sites... Something that bugs.d.o already does, but I dunno if it is also available for other sites. Surely much better than re-inventing the wheel each time... Well, I don't think that at the suggested page something is reinvented. (Feel free to prove me wrong - I would hate to reinvent anything.) IMHO there is no such think like an overview about descriptions of a certain subset of packages that exist and that _not_ _yet_ exists in Debian. While you could probably get the descriptions of the existing packages from some XML service (which would be a nice thing) I doubt that this service will be expanded to DDTP translations - which is really high on my agenda because if we could have the descriptions translated for our target users we could start claiming this is user friendly. For the other pages that are used in Debian-Med David is using some services - but I can not comment on this until I have revised the code. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [DebianGIS] Web pages showing tasks
Hi Andreas, Il giorno Fri, 22 Feb 2008 14:12:56 +0100 (CET) Andreas Tille [EMAIL PROTECTED] ha scritto: For the other pages that are used in Debian-Med David is using some services - but I can not comment on this until I have revised the code. I can comment a bit on this. I haven't followed the whole thread (nor have the time to do so at the moment, sorry), but the scripts I've made for Debian-Med (and also the one Andreas improved -- update-tasks) are not reinventing anything. The scripts I created originally used the SOAP service provided by bugs.debian.org [1] and some HTML parsing from the DDTSS interface to DDTP [2] and [3]. Beware that [3] is outdated, but we've had a harsh (that's an euphemism) discussion with DDTP guys because we were using that, so we're waiting for some interface (SOAP, CGI, XML, ...) to be implemented before updating any script (in fact, the update-ddtp script is currently not 100%-functional). Please let me know if you need further explanation of my scripts :) (or talk with Andreas ;) Ciao, David [1] http://wiki.debian.org/DebbugsSoapInterface [2] http://ddtp.debian.net/debian/dists/sid/main/i18n/Translation-$lang [3] http://kleptog.org/cgi-bin/ddtss2-cgi/$lang/fetch?package=$pkg -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Re: Bug#426581: meshlab - anyone still working on this
Paolo Cignoni writes (Re: Bug#426581: meshlab - anyone still working on this): I am a bit ignorant about debian package creation so be patient with my naiveness :) I would try to help as I can. My comments intermixed below. Thanks for your reply and sorry for the delay in getting back to you. After I built it (on lenny), I ran meshlab from an xterm. It opened an entirely blank override-redirect pale grey window covering the top left area of my display, as well as the main window. What is that blank window for ? Can it be got rid of ? This is not a the exepected behaviour. if meshlab is invoked without any mesh it should ask for a file to open with the standard filedialog. So as a test today I'm running meshlab t.stl where t.stl is a file generated by a prograam of my own. I get two windows. One is the main meshlab window which has my object in in, the various menus, and so on. That is fine. The other window is blank, 800x700, at the top left corner of the screen, and is somehow bypassing the X11 window manager. xwininfo says this: xwininfo: Window id: 0xc40009b Plugin Absolute upper-left X: 0 Absolute upper-left Y: 0 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 800 Height: 480 Depth: 24 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x20 (installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: yes Map State: IsViewable Override Redirect State: no Corners: +0+0 -800+0 -800-720 +0-720 -geometry 800x480+0+0 It's basically pale grey. Looking at it in xmag it's a uniform shade with rgb = 0xefef 0xefef 0xefef. A closer examination shows two small darker squares side by side in the top right corner, coloured rgb = 0x 0xdfdf 0xe4e4. My window manager is vtwm, in case that's relevant. I have taken a screenshot of my whole desktop and put it at http://www.chiark.greenend.org.uk/~ian/t.2008-02-22/screenshot.png (this is after I resized the main meshlab window, which usually starts to fill the whole screen). If I ask for `Edit / Measure' I can't get the rest of the edit menu back without clicking on the measuring tape in the toolbar. I assume this is unintentional and is an upstream UI bug. ahem . probably it is not a very intuitive pattern of action but eventually it was intentional http://meshlab.sourceforge.net/wiki/index.php/Interactive_editing_tools I think this should be addressed at some point. If one is not supposed to be able to drive the program from the menu then there is little point having the menu item. Perhaps it would be better if the menu items (and indeed the other tools in the toolbar) were not greyed out ? Selecting them could then go straight from the old mode to the new. If I run the program with --help or -h, it tries to open them as files. It ought at least to bomb out with a message saying please refer to the meshlab wiki (with a URL). quite a good idea. if started with -h or --help it could directly open the meshlab wiki by using the defaul os browser. I don't think this would be appropriate in Debian. Users would expect --help to print some information to stdout. So a simple message with a URL in it, or some documentation, would be ideal from our point of view. lintian says: ... I did not fully understand the above, but i hope that i can ignore them :) These are Debian-specific things which as upstream you do not need to worry about :-). I raise another issue: U3D. meshlab, to export files into u3d format, needs a binary (idtfconverter), that is compiled out of the u3d open source library. So i see that here there is another dependency here and perhaps there is the need for someone to NMU sourceforge.net/projects/*u3d* I think for Debian this isn't critical, if meshlab at least doesn't crash if the binary isn't found. Although of course importing u3d files would be good. (`NMU' isn't the right term. You can probably just say `package'.) Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#426581: meshlab - anyone still working on this
Teemu Ikonen writes (Re: Bug#426581: meshlab - anyone still working on this): Thanks for the review. I fixed the problems you found except these: After I built it (on lenny), I ran meshlab from an xterm. It opened an entirely blank override-redirect pale grey window covering the top left area of my display, as well as the main window. What is that blank window for ? Can it be got rid of ? I cannot repeat this. What is your window manager ? See my mail just sent for more information about this. Edit / Vertex painting works here. The shaders crash here as well, but AFAIK they need hardware support to work, which I do not have here. Meshlab should check if GL_ARB_vertex_shader and GL_ARB_fragment_shader extensions are available, before trying to use them. I don't have time to start fixing this, or other upstream bugs. Paolo, can you help here? Well, I don't think these are release-critical bugs. However I have discovered one thing that we in Debian ought to consider release-critical: I have discovered that the program prompted me that a new version had been released. This is presumably achieved by contacting some upstream server to check. Paulo, is that correct ? I'm afraid that it is not acceptable for a program packaged for Debian to phone home like this and that feature must be disabled before we upload it even to unstable. If I run the program with --help or -h, it tries to open them as files. It ought at least to bomb out with a message saying please refer to the meshlab wiki (with a URL). Upstream. If I provide a patch will you incorporate it in your package ? I can do it as a bzr branch or an emailed diff, whichever you prefer. I think this is quite important. The behaviour atm is rather poor if you're trying just to figure out how to run the program. I updated the package and put it to again to http://esko.osmas.info/~tmx/meshlab/ but as there are still problems (mainly with the shaders), maybe the package is not quite ready yet. I haven't looked at this yet but I think we're definitely getting there. If you can fix it so it doesn't phone home I'll upload it. (The lib3ds package whose new upstream version I NMU'd has just migrated to testing and I haven't yet heard an objection from its maintainer.) Thanks, Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
