Re: Subject: RFS: mantis (updated package)
Good Morning Daniel, Daniel Baumann wrote: schönfeld / in-medias-res wrote: http://just-imho.net/~schoenfeld/debian-devel/mantis-1.0.6.tar.gz the patches need to be -p1, not -p0. that's all :) well that did what it should did. Another problem: You mentioned that it does not make much sense to use a patch system and modifying checkin.php directly. Normally, i agree, but then i will have to add a lintian override to my package, because to remove the change and instead add it as a patch does lead into an lintian E on the .changes. E: mantis: wrong-path-for-interpreter #!/usr/local/bin/php != /usr/bin/php (./usr/share/mantis/www/core/checkin.php) What should i do, to do it right? Use a lintian override for now and inform the lintian developers about it? Because i think it can be considered as a lintian bug which occurs when using dpatch (or similar systems). So far i'm ready with my changes. I just saw a few things here and there and will recheck if I've incorporated all the changes you've requested. Greets Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Subject: RFS: mantis (updated package)
Patrick Schönfeld wrote: You mentioned that it does not make much sense to use a patch system and modifying checkin.php directly. Normally, i agree, but then i will have to add a lintian override to my package, because to remove the change and instead add it as a patch does lead into an lintian E on the .changes. my point is: when using a patch managment system, which is good, then use it for everything. why can't you do a dpatch for the changes needed on that file too? -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Subject: RFS: mantis (updated package)
Daniel Baumann wrote: Patrick Schönfeld wrote: You mentioned that it does not make much sense to use a patch system and modifying checkin.php directly. Normally, i agree, but then i will have to add a lintian override to my package, because to remove the change and instead add it as a patch does lead into an lintian E on the .changes. my point is: when using a patch managment system, which is good, then use it for everything. I agree :-) why can't you do a dpatch for the changes needed on that file too? Forget everything i said. It was my mistake and were caused because of a bogus patch which did apply but not correct :o) Now it is a dpatch and its working and no warnings appear. Greets Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Subject: RFS: mantis (updated package)
Hi On Tue, 28 Nov 2006 17:59:06 +0100 Daniel Baumann [EMAIL PROTECTED] wrote: ---snip--- Upstream URL: http://www.mantisbt.org ---snap--- should be this: ---snip--- Homepage: http://www.matisbt.org ---snap--- More important is that it should point to http://www.mantisbugtracker.com/ -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: Subject: RFS: mantis (updated package)
Hi, Michal Čihař wrote: More important is that it should point to http://www.mantisbugtracker.com/ why this? It seems as it would make no difference. Greets Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: AKFQuiz
Am Dienstag, dem 28. Nov 2006 schrieb George Danchev: gpc --automake --executable-file-name -Wall -Wno-identifier-case -O3 -s -D SDL -D Transitional -D scrNoEscKey scrquiz.pas scrquiz.pas: In function `askfile': scrquiz.pas:1013: error: reference expected, value given scrquiz.pas:1015: error: reference expected, value given make[1]: *** [scrquiz] Error 1 make[1]: Leaving directory `/home/danchev/download/akfquiz-4.4.0/srcbin' make: *** [all] Error 2 I believe gpc is just plain wrong, but OTOH it supports all architectures available in Debian, so if you ask me I'll go for tweaking the code after it. The problem is solved now in my code. I still consider it as a bug-workaround rather than a fix. It should IMHO be fixed in GPC. I've already written a mail to the GPC's mailing list about it. What my package is concerned: I still try to make some changes before I ask for a sponsor. -- AKFoerster -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Subject: RFS: mantis (updated package)
Hi Daniel, i have just finished my work on the package. My changes are: * the ones you mentioned - everything should be okay now * (re)added a debian/po directory and template files for translators * Changed Upstream URL to mantisbugtracking.com as Michael told me Incoming queue of m.d.o is stil stalled. Therefore i uploaded it to my private webspace again: - URL: http://just-imho.net/~schoenfeld/debian-devel/mantis - dget http://just-imho.net/~schoenfeld/debian-devel/mantis/mantis_1.0.6-1.dsc Best Regards Patrick Daniel Baumann wrote: Patrick Schönfeld wrote: http://just-imho.net/~schoenfeld/debian-devel/mantis_1.0.6-1.dsc you're using patches, nevertheless you're modifying core/checkin.php, is this intentional? * NEWS: don't use two (or more) empty lines as seperator, one is just enough. * README.LDAP: remove the ueseless empty line at the end of the file. * changelog: remove the empty lines at the end of the file. * This: ---snip--- Upstream URL: http://www.mantisbt.org ---snap--- should be this: ---snip--- Homepage: http://www.matisbt.org ---snap--- also note the two leading spaces. * This '|apache-perl' should be this '| apache-perl' * dirs is useless here. * mantis.dirs, mantis.example has a useless empty line at the end. * remove the useless commented stuff in watch * you're lacking a build-depends on dpatch * if you're including the dpatch.make in rules, you can skip the definition of patch/unpatch targets. look at 9base for an example. * this is ugly: ---snip--- #! /bin/sh -e ---snap--- this is beautiful: ---snip--- #!/bin/sh -e ---snap--- in your dpatch headers. Additionally, you may want also fix the author information: This is ugly: ---snip--- by [EMAIL PROTECTED] ---snap--- This is beautiful: ---snip--- by Patrick Schönfeld [EMAIL PROTECTED] ---snap--- * what is debian/patches/DPATCH intended to be for? if you fix above things, i'll sponsor mantis. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Subject: RFS: mantis (updated package)
On Wed, 29 Nov 2006 11:46:44 +0100 Patrick Schönfeld [EMAIL PROTECTED] wrote: Hi, Michal Čihař wrote: More important is that it should point to http://www.mantisbugtracker.com/ why this? It seems as it would make no difference. See http://www.mantisbugtracker.com/index.php?f_offset=18 -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: Subject: RFS: mantis (updated package)
Patrick Schönfeld wrote: * the ones you mentioned - everything should be okay now no, not all: * this: ---snip--- Upstream URL: http://www.mantisbugtracker.com ---snap--- should be this: ---snip--- Homepage: http://www.mantisbugtracker.com ---snap--- * debian/copyright is incomplete, you need to list all copyright holders and their licenses. e.g. adodb and phpmailer is missing (and likely also others, stopped after finding these two). additionally: * you're package produces only one binary package, hence, i suggest for consistency reason to not mix prefixed helpers and not prefixed ones. means, rename mantis.dirs to dirs, etc. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Subject: RFS: mantis (updated package)
Hi Thijs, Thijs Kinkhorst wrote: [...] Good to see that Mantis is getting a new maintainer. :-) Please note that there have been numerous security issues with Mantis in the recent past. Yes i know that mantis has a bad security history. Anyway i prefer to stay on mantis instead of the alternatives in our company and also i prefer to use packages instead of manual installations. Therefore i am heavy motivated to care for this package. So you must be willing to dilligently backport any issues that may arise to the stable release. It's not that hard, but there have been problems with this in the past. Please be prepared :) When i decided to adopt the package, i knew that it would need some work. I already had to invest a *lot of* work in this package, because i had to redo a lot of things which were done half or broken in the earlier versions. Also some things changed at upstream, which changes the way i have to handle things. Okay, but long speak, short sin: I know there may be much work with the package and i am willing to do it. IMO that totally makes sense, as i would like to apply for NM in the future. Greets Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How to unpack upstream tarball in a dpatch-using package?
Be given a source package with the following layout: foo/ foo/debian foo/debian/rules foo/debian/patches foo/debian/patches/00list foo/debian/patches/01bar foo/upstream/package.tar.bz2 So I want the package build process to unpack foo/upstream/packag.tar.bz2 before trying to apply the patches with dpatch. Is it better to do some makefile magic for this unpacking (as having an unpack-stamp which patch depends on, or would one better have a foo/debian/patches/00unpack dpatch snippet doing the unpacking? Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Subject: RFS: mantis (updated package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Daniel Baumann wrote: no, not all: * this: [...] should be this: [...] oops, you got me! :-) Corrected. * debian/copyright is incomplete, you need to list all copyright holders and their licenses. e.g. adodb and phpmailer is missing (and likely also others, stopped after finding these two). Hmm. Do i really need to do this? Because my debian/rules don't install them, as i patched the sources (with patch 01 and 02) to use the debian packages of them instead. I just did not want to change the orig tarball for this. additionally: * you're package produces only one binary package, hence, i suggest for consistency reason to not mix prefixed helpers and not prefixed ones. means, rename mantis.dirs to dirs, etc. Yeah. Good that you say that. I've forgotten to change it, hence i already decided that i should do so mainly for consistence. Corrected. Well, packages are updated, except for the copyright thing, which i asked about above. Greets Patrick -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFbXQzTKIzE6LY9r8RAkQyAKCSSvwtJqEFnQ17SOU2oQcQwHasPACaAuft 2pr2ujBq4O4YPvLuBohl7Yg= =tKD+ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Subject: RFS: mantis (updated package)
Hi, * debian/copyright is incomplete, you need to list all copyright holders and their licenses. e.g. adodb and phpmailer is missing (and likely also others, stopped after finding these two). Hmm. Do i really need to do this? Because my debian/rules don't install them, as i patched the sources (with patch 01 and 02) to use the debian packages of them instead. I just did not want to change the orig tarball for this. You need to clean up the orig tarball (written somewhere in the policy). And then the copyright question is solved as well. Well, packages are updated, except for the copyright thing, which i asked about above. Cheers, Eric -- You don't need to CC me on debian-java, debian-mentors and pkg-java-maintainers. Please CC me on other Debian lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Subject: RFS: mantis (updated package)
Patrick Schönfeld wrote: Hmm. Do i really need to do this? Because my debian/rules don't install them, as i patched the sources (with patch 01 and 02) to use the debian packages of them instead. I just did not want to change the orig tarball for this. as we are also distributing the source, not just the binaries, you have to: * either write a complete debian/copyright file covering all code shipped within the sources. * or, rebuild the upstream tarball and remove the things not needed. note that i'm strongly advocating not to do that, unless you save several megabytes on the tarball size witht hat. note, that you will also have to document the changes you made in debian/copyright, and, should add a '+debian' tag the upstream version to reflect the changed upstream tarball. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to unpack upstream tarball in a dpatch-using package?
Marc Haber -- 29.11.2006 13:36 --: Be given a source package with the following layout: foo/ foo/debian foo/debian/rules foo/debian/patches foo/debian/patches/00list foo/debian/patches/01bar foo/upstream/package.tar.bz2 So I want the package build process to unpack foo/upstream/packag.tar.bz2 before trying to apply the patches with dpatch. Is it better to do some makefile magic for this unpacking (as having an unpack-stamp which patch depends on, or would one better have a foo/debian/patches/00unpack dpatch snippet doing the unpacking? I'd do it with makefile magic. This will allow you to move to another patch system if such need arises. dam -- Damyan Ivanov Modular Software Systems [EMAIL PROTECTED] phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim signature.asc Description: OpenPGP digital signature
Re: Subject: RFS: mantis (updated package)
Hi, Daniel Baumann wrote: as we are also distributing the source, not just the binaries, you have to: * either write a complete debian/copyright file covering all code shipped within the sources. Daniel, Thijs: thanks for clarification in this point. I have now uploaded another changed package. Hope to meet the requirements now. - URL: http://just-imho.net/~schoenfeld/debian-devel/mantis - dget http://just-imho.net/~schoenfeld/debian-devel/mantis/mantis_1.0.6-1.dsc Best Regards Patrick signature.asc Description: OpenPGP digital signature
Re: Subject: RFS: mantis (updated package)
Eric Lavarde - Debian wrote: Hi, * debian/copyright is incomplete, you need to list all copyright holders and their licenses. e.g. adodb and phpmailer is missing (and likely also others, stopped after finding these two). Hmm. Do i really need to do this? Because my debian/rules don't install them, as i patched the sources (with patch 01 and 02) to use the debian packages of them instead. I just did not want to change the orig tarball for this. You need to clean up the orig tarball (written somewhere in the policy). And then the copyright question is solved as well. No, you don't! You *only* modify the source tarball to remove things that are not free. The software is free but you don't install it into the deb. That's fine, but still notice it in debian/copyright: that file covers all licences, whether stuff is installed into the deb or not, since we are distributing the source tarball. It would make sense though to make it explicit that this only applies to the source package. Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Subject: RFS: mantis (updated package)
Sorry! I made a mistake, when sending out this mail. There has been an error, while updating the packages on my server. It is *now* updated. I'm really sorry for wasting your time :-( Patrick Schönfeld wrote: Hi, Daniel Baumann wrote: as we are also distributing the source, not just the binaries, you have to: * either write a complete debian/copyright file covering all code shipped within the sources. Daniel, Thijs: thanks for clarification in this point. I have now uploaded another changed package. Hope to meet the requirements now. - URL: http://just-imho.net/~schoenfeld/debian-devel/mantis - dget http://just-imho.net/~schoenfeld/debian-devel/mantis/mantis_1.0.6-1.dsc Best Regards Patrick signature.asc Description: OpenPGP digital signature
Re: [ping] RFS: yorick-yeti -- several extensions for the Yorick interpreted language
On Wed, 29 Nov 2006 01:32:21 +0100 Daniel Baumann [EMAIL PROTECTED] wrote: Thibaut Paumard wrote: http://mentors.debian.net/debian/pool/main/y/yorick-yeti/yorick-yeti_6.1.6-1.dsc Here we go: [...] the rest is good. tell me if/when you changed something. Many thanks, I've made the five corrections you asked for. The updated package can be found at the same place as the older: dget http://mentors.debian.net/debian/pool/main/y/yorick-yeti/yorick-yeti_6.1.6-1.dsc Best regards, Thibaut. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [ping] RFS: yorick-yeti -- several extensions for the Yorick interpreted language
On Wed, 29 Nov 2006 17:33:47 +0100 Thibaut Paumard [EMAIL PROTECTED] wrote: I've made the five corrections you asked for. The updated package can be found at the same place as the older: dget http://mentors.debian.net/debian/pool/main/y/yorick-yeti/yorick-yeti_6.1.6-1.dsc Trying to prepare a backport, I just noticed that the version of libgsl0-dev in sarge is not sufficient for compiling yorick-yeti. I have therefore re-uploaded with a versioned dependency set = 1.8 (the version in etch). Sorry for this late correction (if you already checked the previous version, I let you decide whether this bug fix warrants checking/uploading anew). Best regards, Thibaut. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: recordmydesktop
Dear mentors, I am looking for a sponsor for my package recordmydesktop. * Package name: recordmydesktop Version : 0.3.0r2-1 Upstream Author : John Varouhakis [EMAIL PROTECTED] * URL : http://recordmydesktop.sourceforge.net * License : GPL Section : graphics It builds these binary packages: recordmydesktop - Captures audio-video data of a linux desktop session The package is lintian clean. The upload would fix this bug: 381154 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/r/recordmydesktop - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/r/recordmydesktop/recordmydesktop_0.3.0r2-1.dsc I would be glad if someone uploaded this package for me. Kind regards José L. Redrejo Rodríguez signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: [ping] RFS: yorick-yeti -- several extensions for the Yorick interpreted language
Thibaut Paumard wrote: dget http://mentors.debian.net/debian/pool/main/y/yorick-yeti/yorick-yeti_6.1.6-1.dsc you forgot: * yorick-dev (=1.6.02) should be yorick-dev (= 1.6.02) and additionally: * yorick-yeti.copyright has a useless empty line at the top of the file. Sorry for this late correction (if you already checked the previous version, I let you decide whether this bug fix warrants checking/uploading anew). no problem. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: recordmydesktop
José L. Redrejo Rodríguez wrote: http://mentors.debian.net/debian/pool/main/r/recordmydesktop/recordmydesktop_0.3.0r2-1.dsc * debian/changelog has a useless empty line at the end of the file. * debhelper (= 4.0.0) is over-precise, debhelper (= 4) is just enough. * installing NEWS and README through debian/docs is not clever, they do not contain any usefull information (also TODO, actually). * debian/rules: - do not use two or more empty lines as seperator, one is just enough. - remove the useless comented dh_* calls. the rest is good. if you fix above things, i'm happy to sponsor it. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: recordmydesktop
El mié, 29-11-2006 a las 21:00 +0100, Daniel Baumann escribió: José L. Redrejo Rodríguez wrote: http://mentors.debian.net/debian/pool/main/r/recordmydesktop/recordmydesktop_0.3.0r2-1.dsc * debian/changelog has a useless empty line at the end of the file. * debhelper (= 4.0.0) is over-precise, debhelper (= 4) is just enough. * installing NEWS and README through debian/docs is not clever, they do not contain any usefull information (also TODO, actually). * debian/rules: - do not use two or more empty lines as seperator, one is just enough. - remove the useless comented dh_* calls. the rest is good. if you fix above things, i'm happy to sponsor it. Fixed and upload again to mentors.debian.net. I'm happy to know you would like to sponsor it. Thanks. signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: RFS: recordmydesktop
On (29/11/06 20:38), José L. Redrejo Rodríguez wrote: Dear mentors, I am looking for a sponsor for my package recordmydesktop. * Package name: recordmydesktop Version : 0.3.0r2-1 Upstream Author : John Varouhakis [EMAIL PROTECTED] * URL : http://recordmydesktop.sourceforge.net * License : GPL Section : graphics This should really be an answer to the ITP, but I am posting here for expediancy reasons. You state in the ITP that this tool is a frontend to recordMyDesktop. Is that packaged separately or within this package? I presume it is already in the archive if it is separate, but I haven't looked, which I apologise for. My question is, if it is packaged separately why is this package named recordmydesktop, rather than recordmydesktop-gui or similar? If it is included why do you just talk about a frontend in the description, and not about the tool itself? Thanks, James -- James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/ seccure key - (3+)k7|M*edCX/.A:n*N!|7U.L#9E)Tu)T0AM - secp256r1/nistp256 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: recordmydesktop
José L. Redrejo Rodríguez wrote: Fixed and upload again to mentors.debian.net. I'm happy to know you would like to sponsor it. Thanks. uploaded. unfortunately i missed the confusing thing about the gtk-frontend and the backend in the description which james just pointed out. please prepare an update with improved description. additionally, am i right that you're packaging the gtk-frontend now too? -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: recordmydesktop
El mié, 29-11-2006 a las 20:18 +, James Westby escribió: On (29/11/06 20:38), José L. Redrejo Rodríguez wrote: Dear mentors, I am looking for a sponsor for my package recordmydesktop. * Package name: recordmydesktop Version : 0.3.0r2-1 Upstream Author : John Varouhakis [EMAIL PROTECTED] * URL : http://recordmydesktop.sourceforge.net * License : GPL Section : graphics This should really be an answer to the ITP, but I am posting here for expediancy reasons. I guess you're refering to the ITP I've just filled for gtk-recordmydesktop, as that's the frontend for recordMyDesktop You state in the ITP that this tool is a frontend to recordMyDesktop. Is that packaged separately or within this package? I presume it is already in the archive if it is separate, but I haven't looked, which I apologise for. My question is, if it is packaged separately why is this package named recordmydesktop, rather than recordmydesktop-gui or similar? It's packaged separately and I've just kept the names the upstream author is using with his work. Maybe you're right, and recordmydesktop-gui would be more accurate, but he decided the names. The author first begun to work on recordmyDesktop and, some months later, he decided to do a GUI and called it gtk-recordMyDesktop. If it is included why do you just talk about a frontend in the description, and not about the tool itself? Thanks, James -- James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/ seccure key - (3+)k7|M*edCX/.A:n*N!|7U.L#9E)Tu)T0AM - secp256r1/nistp256 signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: RFS: recordmydesktop
El mié, 29-11-2006 a las 21:29 +0100, Daniel Baumann escribió: José L. Redrejo Rodríguez wrote: Fixed and upload again to mentors.debian.net. I'm happy to know you would like to sponsor it. Thanks. uploaded. Thanks very much. unfortunately i missed the confusing thing about the gtk-frontend and the backend in the description which james just pointed out. please prepare an update with improved description. In fact, I haven't understood totally the confusion. I supposse it was due to the fact the ITP I've filled for the frontend (gtk-recordMyDesktop) was sent to debian-devel almost at the same time that my message to mentors for the backend (recordMyDesktop). additionally, am i right that you're packaging the gtk-frontend now too? -- Yes, I've just filled the ITP in Debian for it. In fact, I've done it some time ago, but I'm still testing it before uploading it to mentors. Regards José L. signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: RFS: recordmydesktop
José L. Redrejo Rodríguez wrote: Thanks very much. welcome. In fact, I haven't understood totally the confusion. I supposse it was due to the fact the ITP I've filled for the frontend (gtk-recordMyDesktop) was sent to debian-devel almost at the same time that my message to mentors for the backend (recordMyDesktop). ok. Yes, I've just filled the ITP in Debian for it. In fact, I've done it some time ago, but I'm still testing it before uploading it to mentors. contact me off-list if you want sponsoring for that, and, also for other updates when needed for the previous package. http://people.debian.org/~daniel/documents/sponsoring.html#contact -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: uebimiau
Dear mentors, I am looking for a sponsor for my package uebimiau. * Package name: uebimiau Version : 2.7.10-1 Upstream Author : Aldoir Ventura * URL : http://www.uebimiau.org/ * License : GPL Section : web It builds these binary packages: uebimiau - This is an universal webmail developed in PHP The package is lintian clean. The upload would fix these bugs: 395277 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/u/uebimiau - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/u/uebimiau/uebimiau_2.7.10-1.dsc I would be glad if someone uploaded this package for me, and also if someone checks it and make suggestions. It's my first ITP. Regards and thanks for reading, -- Muammar El Khatib. Linux user: 403107. Key fingerprint = 90B8 BFC4 4A75 B881 39A3 1440 30EB 403B 1270 29F1 http://muammarelkhatib.net | http://www.teorex.org ,''`. : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: build-essential / native-package-with-dash-version ?
On Tue, 28 Nov 2006 22:03:22 -0500, Joe Smith [EMAIL PROTECTED] said: Hubert Chan [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] On Tue, 28 Nov 2006 13:30:03 -0300, andremachado [EMAIL PROTECTED] said: The executable-not-elf-or-script I guess will continue. Jar, war, policy and stamp are generated by the compilation and are the results. I don't know about whether jar files should be executable, but if they shouldn't you should chmod -x them in your build process, after they get installed. Jar files are simply zip files with a manifest. The last I checked the exec syscall had no special handling for zip files, and as they lack a bang path, they relly are not executable as far as the system is concerned. So unless a JVM expects jars to have the executable bit set, it probably should not be. It is possible to support execution of jar files using the binfmt_misc mechanism. The only question is whether or not that's something that we do in Debian, which should probably be in the Debian Java policy somewhere. As I don't maintain any Java-related packages, though, I don't know what the Java policy says, so I don't know if jar files are allowed to be executable (although I suspect that they shouldn't be). -- Hubert Chan [EMAIL PROTECTED] -- Jabber: [EMAIL PROTECTED] PGP/GnuPG key: 1024D/124B61FA http://www.uhoreg.ca/ Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: recordmydesktop
On (29/11/06 22:05), José L. Redrejo Rodríguez wrote: El mié, 29-11-2006 a las 20:18 +, James Westby escribió: This should really be an answer to the ITP, but I am posting here for expediancy reasons. I guess you're refering to the ITP I've just filled for gtk-recordmydesktop, as that's the frontend for recordMyDesktop Ah, I have just looked again and you did file that ITP, but you had * Package name : recordmydesktop Apologies for the confusion. James -- James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/ seccure key - (3+)k7|M*edCX/.A:n*N!|7U.L#9E)Tu)T0AM - secp256r1/nistp256 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
