Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
On Thursday 28 October 2004 01:57, Shaun Jackman wrote: A package in main must not depend on any software outside of main, and must be DFSG-free; A package in contrib must be DFSG-free; A package in non-free must be legally distributable by Debian. There are no further restrictions than the above. Perhaps that's true -- I must do a little reading. However, if you upload a package to contrib that build-depends on a package not in contrib or non-free, you'll get a FTBFS RC bug filed against you before you blink. To me, a package in contrib with an unfixable RC bug should not be in the archive. My package build depends are all in main. As far as I can tell, yes, my program belongs and has no problem being in contrib. Which brings me still back to my original question which no one has yet to answer. What can I do to find a sponsor?... I have almost given up hope... - ods15
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
* Erik Schanze [Wed, 27 Oct 2004 18:31:35 +0200]: If your program depends on MPlayer, it must go into non-free. If your program depends on a program in non-free, it must go into contrib. But MPlayer isn't even in non-free. not exactly. packages in contrib can depend on packages not available in Debian. see §2.2.2 of the Policy. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 The difference between literature and journalism is that journalism is unreadable and literature is not read. -- Oscar Wilde
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
However, if you upload a package to contrib that build-depends on a package not in contrib or non-free, you'll get a FTBFS RC bug filed against you before you blink. Hmm, I didn't, back in the days when regina-normal built against java2 (which wasn't in the archive at the time). Though thankfully those days are gone. b.
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
Shaun Jackman [EMAIL PROTECTED] wrote: Perhaps that's true -- I must do a little reading. However, if you upload a package to contrib that build-depends on a package not in contrib or non-free, you'll get a FTBFS RC bug filed against you before you blink. Are there any (inofficial) buildds for contrib? Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
On Thursday 28 October 2004 15:15, Thaddeus H. Black wrote: Hello Oded. snip Again, good luck. If and when you find an appropriate sponsor, let me know the good news. Wow, honestly, that was some damn great advice... And it does sound very accurate and I do understand it. I don't know if I will follow through with it or not. I recently quit my job (good thing. fast food...), so I have plenty of time on my hands, so I might, on the other hand, I start army in less than 2 months (mandatory). I understand Debian's interest in wanting people this serious and hard working, and putting these trials for them... But I must admit, it almost sounds not worth it for my project... :/ I simply developed kmenc15 myself for fun, put it up on some sites, and thought, why not have it also up on my favorite distro, and I never thought it would be something this complicated. My package requires relatively very small amount of maintaining (grand total of 100k including 90k of images :), and I have the obvious advantage of being both the author and maintainer... :) For this reason I find the trials almost pointless, as even a non-serious programmer can handle it. Even though, for the pure cause of boredom, I might follow up on your very great advice, I'd like to think of myself as someone serious enough to do these things. I have no plan of becoming a DD though. I would only be very proud to see my favorite program in my favorite GNU/Linux distro An honest Thankyou. - ods15
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
On Thu, Oct 28, 2004 at 05:10:04PM +0200, Frank Küster wrote: Shaun Jackman [EMAIL PROTECTED] wrote: Perhaps that's true -- I must do a little reading. However, if you upload a package to contrib that build-depends on a package not in contrib or non-free, you'll get a FTBFS RC bug filed against you before you blink. Are there any (inofficial) buildds for contrib? None that I am aware of, at least. -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
On Wednesday 27 October 2004 05:23, Daniel Burrows wrote: That's not surprising. Policy says (section 2.2.2, The contrib section): Examples of packages which would be included in contrib or non-US/contrib are: * free packages which require contrib, non-free packages or packages which are not in our archive at all for compilation or execution, and * wrapper packages or other sorts of free accessories for non-free programs. OK, either I am misreading, or you just prooved me right: * free packages which require [..] packages which are not in our archive at all for compilation or execution My program == free program MPlayer == package which is not in the Debian archives at all. According to that, MPlayer doesn't need to be in the Debian archives for my program to be in contrib!... Am I misunderstanding?.. - ods15
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
On Tue, Oct 26, 2004 at 10:52:58PM +0200, Oded Shimon wrote: On Tuesday 26 October 2004 22:37, Shaun Jackman wrote: For your package to go in contrib, your dependency -- mplayer -- must exist in non-free. Really? I didn't know this. That's not true. There are many packages in contrib which do not have all their dependencies in non-free. E.g., the bunch of java packages which do not work with anything but a non-free java compiler -- a java compiler which Debian itself cannot distribute (and therefor is not in non-free). A package in main must not depend on any software outside of main, and must be DFSG-free; A package in contrib must be DFSG-free; A package in non-free must be legally distributable by Debian. There are no further restrictions than the above. -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune signature.asc Description: Digital signature
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
On Wednesday 27 October 2004 11:05, Wouter Verhelst wrote: That's not true. There are many packages in contrib which do not have all their dependencies in non-free. E.g., the bunch of java packages which do not work with anything but a non-free java compiler -- a java compiler which Debian itself cannot distribute (and therefor is not in non-free). A package in main must not depend on any software outside of main, and must be DFSG-free; A package in contrib must be DFSG-free; A package in non-free must be legally distributable by Debian. There are no further restrictions than the above. Yup, thats exactly what I thought. In which case, my program does have a chance to be in contrib. which brings me to my original question, what should I do to find a sponsor?... I believe I've maxed out my available resources... - ids15
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
Yup, thats exactly what I thought. In which case, my program does have a chance to be in contrib. which brings me to my original question, what should I do to find a sponsor?... I believe I've maxed out my available resources... It might be that you need to wait until you've gone through NM and can upload on your own. Speaking only for myself, my time is limited and sponsorship chews up a fair bit of time (checking over the packaging, talking with the maintainer about what needs fixing, etc), and I'd rather spend that time on packages that can go into main. I don't know how many others feel the same, but if you're looking to go through NM you may find more offers of help if you choose something in main to train yourself on. Of course I may be wrong, just my thoughts on the matter. b.
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
Oded Shimon [EMAIL PROTECTED]: On Wednesday 27 October 2004 05:23, Daniel Burrows wrote: OK, either I am misreading, or you just prooved me right: * free packages which require [..] packages which are not in our archive at all for compilation or execution My program == free program MPlayer == package which is not in the Debian archives at all. According to that, MPlayer doesn't need to be in the Debian archives for my program to be in contrib!... If your program depends on MPlayer, it must go into non-free. If your program depends on a program in non-free, it must go into contrib. But MPlayer isn't even in non-free. Regards, Erik -- www.ErikSchanze.de * Bitte keine HTML-E-Mails! No HTML mails, please! Limit: 100 kB * * Linux-Info-Tag in Dresden, am 30. Oktober 2004 * Info: http://www.linux-info-tag.de * pgp19J0gKEjHK.pgp Description: signature
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
According to that, MPlayer doesn't need to be in the Debian archives for my program to be in contrib!... Yes, that's true. Please note that a package called `mozilla-mplayer' [0] is in the Debian archive. [0] http://packages.debian.org/unstable/misc/mozilla-mplayer */ Christoffer Sawicki [EMAIL PROTECTED]
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
That's not true. There are many packages in contrib which do not have all their dependencies in non-free. E.g., the bunch of java packages which do not work with anything but a non-free java compiler -- a java compiler which Debian itself cannot distribute (and therefor is not in non-free). I maintain one of those packages, and it build-depends on java2-compiler and depends on java2-runtime and java-virtual-machine. All these dependencies are satisfiable in main/contrib. Java packages are unique because most pacakages are architecture-all and are not rebuilt. Now that I look at it, it doesn't seem entirely kosher, but it works. A package in main must not depend on any software outside of main, and must be DFSG-free; A package in contrib must be DFSG-free; A package in non-free must be legally distributable by Debian. There are no further restrictions than the above. Perhaps that's true -- I must do a little reading. However, if you upload a package to contrib that build-depends on a package not in contrib or non-free, you'll get a FTBFS RC bug filed against you before you blink. To me, a package in contrib with an unfixable RC bug should not be in the archive. Cheers, Shaun
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
On Tuesday 26 October 2004 22:37, Shaun Jackman wrote: For your package to go in contrib, your dependency -- mplayer -- must exist in non-free. Really? I didn't know this. Due to patent issues, mplayer cannot go in non-free I've heard of that.. if possible, I'm curious what the issues are. Got a link? [1]. Thus, your package cannot go in contrib. Your package can go in experimental/contrib, which has very little requirements. Wait, when you said the thing about contrib and non-free, did you mean in stable? Can my package go in unstable/contrib? Becuase it depends on kde 3.3, which AFAIK doesn't exist in either stable or experimental. Taht was my original intention. Thankyou for your reply. - ods15
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
On Wednesday 27 October 2004 00:00, Shaun Jackman wrote: Sorry, no link. The basic issue, though, is that MPEG 1/2/4 encoding is encumbered by patents. OK, so my question is, what about xine? How come xine can be in Debian? AFAIK xine can open mpeg1 mpeg2 and mpeg4. Wait, when you said the thing about contrib and non-free, did you mean in stable? Can my package go in unstable/contrib? Becuase it depends on kde 3.3, which AFAIK doesn't exist in either stable or experimental. Taht was my original intention. No. So, what you're saying, the 'experimental' actually has even less restrictions than unstable? Heh. I understand. If so, yeah, I guess its hopeless. Is the rumor that MPlayer will be in Debian soon true?... Something about the issues being solved... - ods15
Re: RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
On Tuesday 26 October 2004 04:52 pm, Oded Shimon wrote: On Tuesday 26 October 2004 22:37, Shaun Jackman wrote: For your package to go in contrib, your dependency -- mplayer -- must exist in non-free. Really? I didn't know this. That's not surprising. Policy says (section 2.2.2, The contrib section): Examples of packages which would be included in contrib or non-US/contrib are: * free packages which require contrib, non-free packages or packages which are not in our archive at all for compilation or execution, and * wrapper packages or other sorts of free accessories for non-free programs. (disregarding any other reasons your package might not be suitable for the archive) Daniel -- /--- Daniel Burrows [EMAIL PROTECTED] --\ | Imagine if every Thursday your shoes exploded if you | | tied them the usual way. This happens to us all the | | time with computers, and nobody thinks of complaining. | \ Debian GNU/Linux http://www.debian.org -- Because. ---/ pgp2YpM0IhVbn.pgp Description: PGP signature
RFS: kmenc15 - An advanced Qt/KDE MEncoder frontend.
Hi. This is no longer an RFS, I posted this RFS here quite a while ago, this is now a plea for: What should I do? My program is an MEncoder frontend which depends on MPlayer, if I am not mistaken, that means it belongs in contrib. I have completed a Debian package, have been looking for a sponsor for quite some time, I have tried asking here, in debian-mentors, in several other relevant debian mailing lists, and in the IRC channel, and got for it one useful reply, to contact Marillat. Thanks to him, my program is now up at the unofficial archives at http://hpisi.nerim.net/ , for which I am very grateful. My question is, at this point, is there any chance my program will be in the official Debian archives (in section contrib)? Is there anything else I should try to find a sponsor?... - ods15
