Re: RFS: zimpl (updated package)
Hi, > I am looking for a sponsor for the new version 2.07.ds1-1 > of my package "zimpl". Usually, Anibal Monsalve Salazar sponsors the > package, but I haven't got a reply for a few days, so I assume he is > busy right now. meanwhile Anibal replied that he'll review the package, so I withdraw my request. Regards, Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Some help needed for kernel-module and m-a
Hi, Gudjon I. Gudjonsson schrieb: The trick is in the control.modules.in file. Is it possible to see your package. Then I (or some other) might be able to find the error. http://jesusch.de/~jesusch/debian/oracleasm-2.0.4/debian/control.modules.in It's basically still the template generated by dh_make - just some minor modifications. Bjoern -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: bluetooth-alsa (updated package)
Dear mentors, I am looking for a sponsor for the new version 0.5cvs20070908-1 of my package "bluetooth-alsa". It builds these binary packages: bluetooth-alsa - Bluetooth audio for Linux The package appears to be lintian/pbuilder clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/b/bluetooth-alsa - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/b/bluetooth-alsa/bluetooth-alsa_0.5cvs20070908-1.dsc I would be glad if someone uploaded this package for me. Kind regards, -- Krzysztof Burghardt <[EMAIL PROTECTED]> http://www.burghardt.pl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: gwyddion - Scanning Probe Microscopy analysis software
> Thank you very much for reading until here! Any comments (also on different > topics) are very much welcome! Thank you for doing the packaging! I didn't know about the program before, I just tried your .deb and it looks very good (both the packaging and gwyddion). I am looking forward when you resolve the rest of technical issues and it hits unstable. I'll point it out to my colleagues in Prague who use windows and proprietary programs for processing AFM images, to try gwyddion out. Just curious - what is Czech Metrology Institute using scanning probe microscopy techniques for? I always thought metrology institutes are predicting weather. :) Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: New ccontrol package, 0.9.1+20060806-4
Ted Percival wrote: > I originally emailed my regular sponsor, Amaya, but this time didn't > get an immediate reply -- so I'm posting to mentors. This fix is > important for Ubuntu so I'd like to get it into Debian ASAP so it can > be synced. Oops, I just uploaded before realizing you had CC:ed the list. So please scream at me gently if I fsckd up :) Sorry for the late reply, been overloaded by RL (but both for fun and profit, so no complaints here). Happy hacking! -- ·''`. If I can't dance to it, it's not my revolution : :' :-- Emma Goldman `. `' Proudly running Debian GNU/Linux (unstable) `- www.amayita.com www.malapecora.com www.chicasduras.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Some help needed for kernel-module and m-a
Hi You need to call prep-deb-files in debian/rules binary-modules: prep-deb-files Now it works happily :) Your package does not work on kernel 2.6.22 and it seems like the archive is buggy since only kernel 2.6.18-5 is available but version 2.6.18-4 is listed. I tried three different servers. Do you know where to report that? Cheers Gudjon On Friday 07 September 2007 21:22:28 Bjoern Boschman wrote: > Hi, > > I'm currently debianizing oracleasm. > Till now quite some things look pretty well. > > They point where I'm lost it the module-assistant build. > > When I install the oracleasm-source_2.0.4-1_all.deb package it unpacks > /usr/src/oracleasm.tar.bz2 correctly. > > After that I want to build the module using m-a a-b oracleasm > > Everything seems to be build correctly BUT instead of building a > oracleasm-kernel-whatever it generates a > oracleasm-source_2.0.4-1+2.6.18.dfsg.1-13etch2_all.deb which is again > the same package name as the module-source. > > Also the package does not contain the .ko file although it had been > build under > /usr/src/modules/oracleasm/debian/oracleasm-kernel-2.6.18-5-vserver-amd64/l >ib/modules/2.6.18-5-vserver-amd64/misc/oracleasm.ko > > > Might anybody have a look on my try to find the hint I'm missing? > > The sources and all is available via http://jesusch.de/~jesusch/debian/ > > > thnx in advance > > Bjoern -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: tesseract (updated package)
Dear mentors, I am looking for a sponsor for the new version 2.01-1 of "tesseract", plus the eight language packages, "tesseract-eng", "tesseract-deu", "tesseract-deu-f", "tesseract-nld", "tesseract-spa", "tesseract-por", "tesseract-ita", "tesseract-fra" It builds these binary packages: tesseract - The well-known OCR engine first developed by HP and now taken over by Google The upload would close Bug#434152. The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/t/tesseract - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tesseract/tesseract_2.01-1.dsc The languages packages are: - URL: http://mentors.debian.net/debian/pool/main/t/tesseract-deu - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tesseract-deu/tesseract-deu_2.00-1.dsc The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/t/tesseract-deu-f - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tesseract-deu-f/tesseract-deu-f_2.01-1.dsc - URL: http://mentors.debian.net/debian/pool/main/t/tesseract-eng - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tesseract-eng/tesseract-eng_2.00-1.dsc - URL: http://mentors.debian.net/debian/pool/main/t/tesseract-fra - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tesseract-fra/tesseract-fra_2.00-1.dsc - URL: http://mentors.debian.net/debian/pool/main/t/tesseract-ita - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tesseract-ita/tesseract-ita_2.00-1.dsc - URL: http://mentors.debian.net/debian/pool/main/t/tesseract-nld - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tesseract-nld/tesseract-nld_2.00-1.dsc - URL: http://mentors.debian.net/debian/pool/main/t/tesseract-spa - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tesseract-spa/tesseract-spa_2.00-1.dsc The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/t/tesseract-por - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tesseract-por/tesseract-por_2.01-1.dsc I would be glad if someone uploaded this package for me. Regards Jeff Ratcliffe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Some help needed for kernel-module and m-a
Hi, Gudjon I. Gudjonsson schrieb: You need to call prep-deb-files in debian/rules binary-modules: prep-deb-files Now it works happily :) Thnx for the point! I wouldn't have found that by myself. Your package does not work on kernel 2.6.22 and it seems like the archive is buggy since only kernel 2.6.18-5 is available but version 2.6.18-4 is listed. I tried three different servers. Do you know where to report that? I think that's more related due to some unclean source directory. Should be fixed by now. You can try http://jesusch.de/~jesusch/debian/oracleasm-source_2.0.4-1_all.deb Bjoern -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: metacam (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.2-4 of my package "metacam". It builds these binary packages: metacam- extract EXIF information from digital camera files The package appears to be lintian clean. The upload would fix these bugs: 279342, 425241 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/metacam - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/metacam/metacam_1.2-4.dsc I would be glad if someone uploaded this package for me. Kind regards, -- Juan Angulo Moreno http://www.0x29.com.ve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: grub-splashimages (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.2.2 of my package "grub-splashimages". It builds these binary packages: grub-splashimages - a collection of great GRUB splashimages The package appears to be lintian/linda/pbuilder clean. The upload would fix these bugs: 440232 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/grub-splashimages - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/grub-splashimages/grub-splashimages_1.2.2.dsc I would be glad if someone uploaded this package for me. Kind regards, -- Krzysztof Burghardt <[EMAIL PROTECTED]> http://www.burghardt.pl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: Kenta Cho's games
Hi, I finally finished all of Kenta Cho's games, and it is time to find sponsorship for them. Some of them are already in the archive, but there are new debian releases, so those should be easier: http://mentors.debian.net/debian/pool/main/b/bulletml/bulletml_0.0.6-2.dsc http://mentors.debian.net/debian/pool/main/r/rrootage/rrootage_0.23a-6.dsc http://mentors.debian.net/debian/pool/main/a/a7xpg/a7xpg_0.11.dfsg1-2.dsc http://mentors.debian.net/debian/pool/main/g/gunroar/gunroar_0.15.dfsg1-2.dsc (rrootage needs a previous upload of the newer release of the libary bulletml) These other games are NEW: http://mentors.debian.net/debian/pool/main/m/mu-cade/mu-cade_0.11.dfsg1-1.dsc http://mentors.debian.net/debian/pool/main/t/torus-trooper/torus-trooper_0.22.dfsg1-1.dsc http://mentors.debian.net/debian/pool/main/t/tumiki-fighters/tumiki-fighters_0.2.dfsg1-1.dsc http://mentors.debian.net/debian/pool/main/v/val-and-rick/val-and-rick_0.1a.dfsg1-1.dsc All these games are under a BSD license, are arcade games, abstract shooters, and if you want to know more about them, I recently wrote an entry in my weblog about them: http://www.miriamruiz.es/weblog/?p=107 bulletml is a library coded in C++ rrootage is a game coded in C++ The rest are games coded in D Language. Greetings and thanks, Miry PS: Please, to organize things a bit, if you intend to sponsor some of these games, it'd be better if you told in the list, so that other possible sponsors already know. PS2: Of course, as usual, feedback is welcome. There's a hard work behind all of these games, and they're quite severely patched, as the original ones were developed on Windows with a proprietary D compiler, and we have moved them to Linux with gdc free D Language compiler, which is already in Debian. Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: gwyddion - Scanning Probe Microscopy analysis software
Justin Pryzby schrieb am 07.09.2007 17:46 Uhr: > On Fri, Sep 07, 2007 at 05:20:56PM +0200, Jan Beyer wrote: >> On 09/07/2007 01:55 PM, Justin Pryzby wrote : >>> On Fri, Sep 07, 2007 at 11:54:18AM +0200, Jan Beyer wrote: Furthermore there are lintian warnings, which I did not quieten. They are about the libgwyddion2 package which contains several libraries and thus doesn't match the SONAMES of them. What is current practice? Allow the >> >>> So I think the libraries should only be in the same package if they >>> have the same soname. (Or, you can put them into a subdirectory of >>> /usr/lib/ if they're not linked against directly and it's no problem). >> The point is, at least as upstream explained to me, that these libraries are >> not particularly well split with regard to their contents. So no one will >> link against just one or some of them. In fact, one often needs some modules >> (which are in the gwyddion package) to build something reasonable. That's >> why I/we (we=upstream+me) decided to put them together. >> Concerning putting them into subdirectories: This would mean creating a >> subdirectory for each library and putting it in there? Could I then keep >> them all in one package? > The directory would be named after the package. > /usr/lib/libgwyddion2/* and either the public libraries or final > binaries would need rpath to find them. (It still seems a grey area > whether to add a soname and install the lib to /usr/lib or to use > rpath for some things). hmmm, then simply splitting the library package sounds easier... ;-) And finally there is a duplicate depends of gwyddion on libgwyddion2, one added by the debhelper scripts and one by me - should I override this, or take away my hand-written dependency? >>> I think you should drop the manually-added one since the automatic one >>> will always be working with ELF dependency output. >> Should I force a versioned automatic dependency via dh_makeshlibs -V or >> dh_makeshlibs -V 'libgwyddion2 (>=2.8)'? > I think you have to bump the shlibs version whenever upstream adds a > symbol. Unless you can show (by reading the diff) that a new upstream > *doesn't* do this (or make incompatible changes), it's prolly safe to > increment this at every new upstream. > > Otherwise an object compiled against a recent libgwyddion2 with new > symbol would end up in a package with Depends: libgwyddion2 (>=X) > where version X doesn't actually provide the symbol, and an app will > crash whenever the symbol lookup is attempted. Then I'll use libxxxy-z (=a.b), which should be inserted by the -V option. Unfortunately my Linux-installation is screwed up at the moment :-(, but I'll work on it as soon as I get it fixed (hopefully during the coming week). Do you have any comments on this Depends: python | perl | ruby line? Is it allowed and does it work like one would expect it? Do you prefer the next package version to be 2.8-2 or should it stay 2.8-1 (there seems to be no real consensus about this)? Many thanks! Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: gwyddion - Scanning Probe Microscopy analysis software
Ondrej Certik schrieb am 08.09.2007 14:04 Uhr: >> Thank you very much for reading until here! Any comments (also on different >> topics) are very much welcome! > > Thank you for doing the packaging! I didn't know about the program > before, I just tried your .deb and it looks very good (both the > packaging and gwyddion). I am looking forward when you resolve the > rest of technical issues and it hits unstable. I'll point it out to my > colleagues in Prague who use windows and proprietary programs for > processing AFM images, to try gwyddion out. Thanks! This is very much welcome, of course! > Just curious - what is Czech Metrology Institute using scanning probe > microscopy techniques for? I always thought metrology institutes are > predicting weather. :) > > Ondrej > > Probably Petr Klapetek <[EMAIL PROTECTED]> is the right one to ask in this question. But you're right - it's an interesting question, which I did not yet ask them... ;-) Have a nice weekend, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: gwyddion - Scanning Probe Microscopy analysis software
> > "David Necas (Yeti)" <[EMAIL PROTECTED]> schrieb am 08.09.2007 20:38: > > > On Sat, Sep 08, 2007 at 08:34:31PM +0200, Jan Beyer wrote: > > Probably Petr Klapetek <[EMAIL PROTECTED]> is the right one to ask > > in this question. But you're right - it's an interesting question, which > > I did not yet ask them... ;-) > > Quoting my reply to Ondrej: > > Metrology institutes define the measurement standards so > that you can compare the lengths of metrology and > meteorology and find that the latter is 22.2% longer... shame on me, that I missed these 22.2%... I shouldn't be trying to read and write mail in the evening with a headache and fever... Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: gwyddion - Scanning Probe Microscopy analysis software
> > Metrology institutes define the measurement standards so > > that you can compare the lengths of metrology and > > meteorology and find that the latter is 22.2% longer... > shame on me, that I missed these 22.2%... > I shouldn't be trying to read and write mail in the evening with a headache > and fever... Shame on me as well. But now I think I will never mistake metrology and meteorology again, that's what debian-mentors is for, right? :) O. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
packaging sqliteman
Hi, I've created the beginnings of a package for sqliteman (upstream site is http://sqliteman.com). The problem I have is this program, currently seems to have a few fairly major bugs (for example it is impossible to run "insert ... values" statements - upstream bug #17). What's my best course of action - ITP it now and work on completing the package despite its current buggy state, or hold fire until the more serious bugs have been resolved upstream? In case anyone is interested I've put the work-in-progress source package at : http://encoresoup.com/project/pkg_sqliteman. Regards, David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: anubis
Dear mentors, I am looking for a sponsor for my package "anubis". I have fixed missing m4 build dependency and add manual pages and thus I'm requesting RFS second time. * Package name: anubis Version : 4.0-1 Upstream Author : Wojciech Polak <[EMAIL PROTECTED]> Sergey Poznyakoff <[EMAIL PROTECTED]> Krzysztof Burghardt <[EMAIL PROTECTED]> * URL : http://www.gnu.org/software/anubis/ * License : GPL Section : net It builds these binary packages: anubis - an SMTP message submission daemon The package appears to be lintian/linda/pbuilder clean. The upload would fix these bugs: 439690 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/a/anubis - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/a/anubis/anubis_4.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards, -- Krzysztof Burghardt <[EMAIL PROTECTED]> http://www.burghardt.pl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: cellwriter
I modified the source a bit to make it compile in Etch and built with cowbuilder for this upload (1.0.2-1). On Fri, 2007-09-07 at 22:43 -0300, Nelson A. de Oliveira wrote: > # Add here any variable or target overrides you need. > > As a suggestion, remove this line. Done. > It's not necessary to install README (this info is already on the > package description and on the manpage). > AUTHORS is also included on debian/copyright, so I don't see a need to > install it too. It's a GNU standard to have it, so why not? I've actually just added some information to the README which isn't mentioned anywhere else. > I strongly recommend to you create a debian/menu file. Done. > All the files inside your tarball have the execution bit set. It's not > need to have all the files executable (just a suggestion for your next > release). An unfortunate side-effect of compiling on a FAT partition (I dual boot). I've recompiled on an EXT3 and hopefully set all the permissions correctly this time. > And I have tested cellwriter and it's not working :-( > While training its input, the letters don't get darker with training. > Any ideas why it's happening? It would be unusual for there to be a bug there. The letters get darker gradually, it's not very noticeable. When you draw a letter, you must move the mouse out of the box so that the ink disappears. If you train the program this way, click Finish, write something and your input isn't recognized, it still doesn't mean that the training is broken. If you draw an input character that is very different from the training samples, CellWriter will reject it. Most often this happens when someone trains a character by drawing it twice without moving the pointer out of the box (so the program expects you to draw that character twice this way every time!) or if you put a dot where there shouldn't be one on accident. -- Michael Levin <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: packaging sqliteman
On Sat, 08 Sep 2007 23:23:13 +0100 David Claughton <[EMAIL PROTECTED]> wrote: > Hi, > > I've created the beginnings of a package for sqliteman (upstream site is > http://sqliteman.com). It's a GUI frontend for a well established and generally not that buggy backend - it doesn't make a lot of sense (to me at least) to package it in the current state. > The problem I have is this program, currently seems to have a few fairly > major bugs (for example it is impossible to run "insert ... values" > statements - upstream bug #17). That is such a major omission and such a small amount of work. SQLite is easy (comparatively) and there are numerous packages out there inserting new data all the time. A frontend that cannot support INSERT is pre-alpha IMHO. (I've written one and I maintain almost a dozen others.) After all, commands to SQLite are passed as SQL statements - plain text. The website does come across as more hype than substance. > What's my best course of action - ITP it now and work on completing the > package despite its current buggy state, or hold fire until the more > serious bugs have been resolved upstream? There's no problem keeping an ITP open for ages (I've got one v.old ITP due to upstream bugs and lack of development time but that's my own upstream project so sometimes that changes the way that people view such an old ITP.) The thing is to ensure that the ITP indicates that this isn't imminent (and why) as well as responding if anyone does check on the progress of the ITP. There are few deadlines in free software so even apparently small amounts of code can take significant amounts of time - are you sure you will still be interested in packaging it when the issues are actually fixed? Even if that is next year or longer? (Real life has a habit of destroying even the best laid plans - you and upstream.) If you are that motivated, maybe you should get involved in the development and work on some of the code yourself. :-) -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpQDqoaGHKwW.pgp Description: PGP signature
Re: RFS: cellwriter
Hi! On 9/8/07, Michael Levin <[EMAIL PROTECTED]> wrote: > > It's not necessary to install README (this info is already on the > > package description and on the manpage). > > AUTHORS is also included on debian/copyright, so I don't see a need to > > install it too. > > It's a GNU standard to have it, so why not? I've actually just added > some information to the README which isn't mentioned anywhere else. There is no problem in installing README and AUTHORS. It's just not necessary to install a README that contains instructions to compile and install the program (since the user will get a package ready to use, without needing to compile, install, etc), right? The same thing with AUTHORS. The content of this file is already included on debian/copyright. You will just get duplicated data if you install it. > > I strongly recommend to you create a debian/menu file. > > Done. Section of your menu file should be "Applications/Accessibility" And it's not necessary to have "Encoding=UTF-8" in cellwriter.desktop. > > And I have tested cellwriter and it's not working :-( > > While training its input, the letters don't get darker with training. > > Any ideas why it's happening? > > It would be unusual for there to be a bug there. The letters get darker > gradually, it's not very noticeable. When you draw a letter, you must > move the mouse out of the box so that the ink disappears. Hum... I see no ink when I draw anything on the boxes :-/ Does it need something from Gnome to work properly? (I am using Window Maker). I have tried compiling it with --disable-gnome, but nothing seems to change. Best regards, Nelson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: RFS: Kenta Cho's games
bulletml, mu-cade and torus-trooper have already been uploaded :) Greetings, Miry --- Miriam Ruiz <[EMAIL PROTECTED]> escribió: > Hi, > > I finally finished all of Kenta Cho's games, and it is time to find > sponsorship for them. Some of them are already in the archive, but there are > new debian releases, so those should be easier: > > http://mentors.debian.net/debian/pool/main/b/bulletml/bulletml_0.0.6-2.dsc > http://mentors.debian.net/debian/pool/main/r/rrootage/rrootage_0.23a-6.dsc > http://mentors.debian.net/debian/pool/main/a/a7xpg/a7xpg_0.11.dfsg1-2.dsc > http://mentors.debian.net/debian/pool/main/g/gunroar/gunroar_0.15.dfsg1-2.dsc > > (rrootage needs a previous upload of the newer release of the libary > bulletml) > > These other games are NEW: > > http://mentors.debian.net/debian/pool/main/m/mu-cade/mu-cade_0.11.dfsg1-1.dsc > http://mentors.debian.net/debian/pool/main/t/torus-trooper/torus-trooper_0.22.dfsg1-1.dsc > http://mentors.debian.net/debian/pool/main/t/tumiki-fighters/tumiki-fighters_0.2.dfsg1-1.dsc > http://mentors.debian.net/debian/pool/main/v/val-and-rick/val-and-rick_0.1a.dfsg1-1.dsc > > All these games are under a BSD license, are arcade games, abstract > shooters, > and if you want to know more about them, I recently wrote an entry in my > weblog about them: > > http://www.miriamruiz.es/weblog/?p=107 > > bulletml is a library coded in C++ > rrootage is a game coded in C++ > The rest are games coded in D Language. > > Greetings and thanks, > Miry > > PS: Please, to organize things a bit, if you intend to sponsor some of > these > games, it'd be better if you told in the list, so that other possible > sponsors > already know. > > PS2: Of course, as usual, feedback is welcome. There's a hard work behind > all > of these games, and they're quite severely patched, as the original ones > were > developed on Windows with a proprietary D compiler, and we have moved them > to > Linux with gdc free D Language compiler, which is already in Debian. Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: cellwriter
On Sat, 2007-09-08 at 20:12 -0300, Nelson A. de Oliveira wrote: > There is no problem in installing README and AUTHORS. It's just not > necessary to install a README that contains instructions to compile > and install the program (since the user will get a package ready to > use, without needing to compile, install, etc), right? I agree but this is default behavior for Automake and I haven't found a way to turn it off. > Section of your menu file should be "Applications/Accessibility" Done. I should point out that I was using what appears to be an outdated (year old?) policy manual that needs updating: http://www.debian.org/doc/packaging-manuals/menu-policy/ch2.html > And it's not necessary to have "Encoding=UTF-8" in cellwriter.desktop. Done. > Hum... I see no ink when I draw anything on the boxes :-/ > Does it need something from Gnome to work properly? (I am using Window Maker). > I have tried compiling it with --disable-gnome, but nothing seems to change. I can think of two possible issues: 1) XInput is not supported? 2) Your Window Manager won't give motion/button events to a window that refuses focus GTK allows the creation of GtkWindows that do not grab focus. For CellWriter, this is critical because it needs to generate keystrokes to send out to a different window you have in focus. Possibly your window manager doesn't give CellWriter the events it needs to function. CellWriter works on Metacity and XFWM. I will download a few different window managers and see if others have issues. I'll look for a workaround but in the meantime, I don't think this issue should prevent the upload of the package. CellWriter is positioned as a kind of GNOME utility anyway, you use a custom WM at your own risk. :| -- Michael Levin <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: cellwriter
On Sat, 2007-09-08 at 20:12 -0300, Nelson A. de Oliveira wrote: > Hum... I see no ink when I draw anything on the boxes :-/ > Does it need something from Gnome to work properly? (I am using Window Maker). > I have tried compiling it with --disable-gnome, but nothing seems to change. Hmm. I seem to have placed the blame on Window Maker too early. I just ran it and CellWriter worked fine. Can you give me any more hints to go on? -- Michael Levin <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: cellwriter
Hi Michael! Your package looks good. There are only 3 small things that you may want to do (or you can do them on a latter version of your package). On 9/8/07, Michael Levin <[EMAIL PROTECTED]> wrote: > On Sat, 2007-09-08 at 20:12 -0300, Nelson A. de Oliveira wrote: > > There is no problem in installing README and AUTHORS. It's just not > > necessary to install a README that contains instructions to compile > > and install the program (since the user will get a package ready to > > use, without needing to compile, install, etc), right? > > I agree but this is default behavior for Automake and I haven't found a > way to turn it off. You don't need to remove them from your source package. You can just not install them. With CDBS you need to use this in debian/rules, after the includes: DEB_INSTALL_DOCS_ALL := TODO Then CDBS will only install the TODO file (leaving README and AUTHORS without being installed, for example). > I should point out that I was using what appears to be an outdated (year > old?) policy manual that needs updating: > http://www.debian.org/doc/packaging-manuals/menu-policy/ch2.html The latest version of lintian will catch this old menu format. You can also read /usr/share/doc/menu/menu.txt.gz, from menu package version 2.1.35 > > And it's not necessary to have "Encoding=UTF-8" in cellwriter.desktop. > > Done. It's not wrong to modify a file directly (like you did with cellwriter.desktop), but it's good to keep all your changes inside the debian/ dir. If you need to modify a file, you can patch it (using dpatch, quilt, simple-patch-system, or something else that you like). And the last thing is change command="cellwriter" to command="/usr/bin/cellwriter" in your debian/menu file. If you want to fix debian/rules to install only the necessary docs, use a patch system (for cellwriter.desktop) and change the menu file, then perfect. Otherwise I can upload the package if you don't want to change them now (as I said before, your package isn't wrong if you don't change this). (I will reply the other email only to you as debian-mentors isn't the place to we talk about this, OK?) Best regards, Nelson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
