Re: RFS: kernelcheck
[moving to debian-devel as this is a topic broader than debian-mentors] Master Kernel master.kernel.cont...@gmail.com writes: Ben Finney ben+deb...@benfinney.id.au writes: [To be likely to have your package sponsored,] You will need to identify yourself; “Master Kernel” is hardly likely to be your real name. Is there *any way* that I don't have to disclose this information? I was contacted by a packager a while ago when this issue came up. He said it would be possible to work around it. Well, if that person says it can be done, you'd be best to ask them for the details. I am all in favour of allowing people their anonymity, but the flip side of that is anonymity is directly at odds with reputation: reputation requires consistent use of an identity. If you want to operate with Debian you are operating in a society built primarily on trust and reputation. For that, we require identity to which that reputation and trust can be associated. Also, your expressive work is (whether you choose it or not) subject to copyright, and you as a legal entity are the copyright holder; for Debian to make use of your work under copyright law, we take on the burden of assuring we have license to do so. I'm not an ftpmaster, but I would be surprised if they want to take the risk of distributing works for which the copyright provenance is essentially unknown. I would imagine many prospective sponsors feel the same way. I don't know, though, so I'm inviting further input. -- \ “Even if the voices in my head are not real, they have pretty | `\ good ideas.” —anonymous | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: kernelcheck
Le Fri, Jun 19, 2009 at 11:57:04PM -0400, Master Kernel a écrit : Is there *any way* that I don't have to disclose this information? I was contacted by a packager a while ago when this issue came up. He said it would be possible to work around it. Hi, the way Debian organises its GPG web of trust is dependant on checking the ID of the key owner. Therefore, you can not join Debian and stay anonymous. Furthermore, many Debian developers will not sponsor packages that do not originate from somebody connected to our web of trust. This said, there are other ways to contribute to Debian that do not require identification. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Packaging data for a CGI
On Sat, Jun 20, 2009 at 01:36:25PM +1000, Erik de Castro Lopo wrote: Hi all, I'm packaging a command line app called hoogle that can also run as a CGI (depending on whether QUERY_STRING or REQUEST_URI is defined). The source package generates three binary packages: hoogle - the binary hoogle-data - architecture independant data hoogle-cgi - creates a symlink from /usr/lib/cgi-bin to the binary in /usr/bin/ The issue I'm having is that the CGI also has some resources (an XML file, a javascript file and some PNGs) that need to be put somewhere appropriate so the web server can serve them in response to a standard HTTP GET. I would put this somewhere under /var/www but the policy manual says thats a bad idea: http://webapps-common.alioth.debian.org/draft/html/ch-issues.html Where should I put these resources? Look at some other packages; I believe the convention is to use /usr/share/appname. In your case, if there is already stuff in /usr/share/hoogle/ for the hoogle-data package, you might pick /usr/share/hoogle/www/ or www-data/ or something like that for the CGI script's resources. G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 yields falsehood, when appended to its quotation. yields falsehood, when appended to its quotation. pgpVuJWZnG8kG.pgp Description: PGP signature
Re: Packaging data for a CGI
Peter Pentchev wrote: Look at some other packages; I believe the convention is to use /usr/share/appname. In your case, if there is already stuff in /usr/share/hoogle/ for the hoogle-data package, you might pick /usr/share/hoogle/www/ or www-data/ or something like that for the CGI script's resources. Sorry, I don't think I explained my self clearly enough. The problem is that the CGI generates HTML which has links which look like: /hoogle/hoogle.css /hoogle/hoogle.png /hoogle/hoogle.js which the web client would interpret as: http://host-cgi-was-served-from/hoogle/hoogle.css and so on. The obvious solution is to put them in /var/www/hoogle/ but this location seems to be discouraged by the policy manual. I was wondering if there was another solution. Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Packaging data for a CGI
Erik de Castro Lopo a écrit : Where should I put these resources? Try to look at darcsweb which faces the exact same problem. Cheers, -- Mehdi Dogguy مهدي الدڤي http://www.pps.jussieu.fr/~dogguy Tel.: (+33).1.44.27.28.38 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Packaging data for a CGI
On Sat, Jun 20, 2009 at 08:08:49PM +1000, Erik de Castro Lopo wrote: Peter Pentchev wrote: Look at some other packages; I believe the convention is to use /usr/share/appname. In your case, if there is already stuff in /usr/share/hoogle/ for the hoogle-data package, you might pick /usr/share/hoogle/www/ or www-data/ or something like that for the CGI script's resources. Sorry, I don't think I explained my self clearly enough. The problem is that the CGI generates HTML which has links which look like: /hoogle/hoogle.css /hoogle/hoogle.png /hoogle/hoogle.js which the web client would interpret as: http://host-cgi-was-served-from/hoogle/hoogle.css and so on. The obvious solution is to put them in /var/www/hoogle/ but this location seems to be discouraged by the policy manual. I was wondering if there was another solution. Yes, there is, and that's exactly what I meant :) Sorry for not explaining this more clearly, or pointing at a specific package; take a look at e.g. the phpmyadmin or phppgadmin packages. (of course, I am not a Debian Developer, so the following might not necessarily be the right way of doing things; it's just that I've seen it done in more than one package) Your package should place the files into /usr/share/hoogle/www/. After that, it should either create a file in /etc/apache2/conf.d/ containing something like this (that's what phppgadmin does): Alias /hoogle /usr/share/hoogle/www/ Directory /usr/share/hoogle/www Order allow,deny Allow from all # Any other options your data files might need /Directory ...or it should instruct the user to do that for the virtual hosts she wants it active on. It may also install a symlink in /var/www/hooogle/ pointing to /usr/share/hoogle/www/. The latter two options are what the phpmyadmin package does; also see its README.Debian file. G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 You have, of course, just begun reading the sentence that you have just finished reading. pgpVx56hZnWbk.pgp Description: PGP signature
Re: Packaging data for a CGI
Mehdi Dogguy wrote: Erik de Castro Lopo a écrit : Where should I put these resources? Try to look at darcsweb which faces the exact same problem. Thanks Mehdi. That looks like what I'm after. Cheers, Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: python-pytemplate (2nd try)
Dear mentors, I am looking for a sponsor for my package python-pytemplate. * Package name: python-pytemplate Version : 1.5.1-1 Upstream Author : Stéphane Bulot steph...@bulot.org * URL : http://www.bulot.org/wiki/doku.php?id=projects:python:pytemplate * License : GPL-3 Section : python It builds these binary packages: python-pytemplate - framework for writing Python applications python-pytemplate is a small project intending to give Python developers a starting framework. It allows them to properly create scripts without struggling with configuration files and logging properties development. python-pytemplate offers different Python classes that one can use to inherit all of their properties. For instance, the ThreadTemplate class includes the methods needed to work with threads. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/python-pytemplate - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/python-pytemplate/python-pytemplate_1.5.1-1.dsc The package appears to be lintian clean. The upload would fix these bugs: 529609 I would be glad if someone reviewed/uploaded this package for me. Thank you for your time. Kind regards, Ignace Mouzannar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Packaging data for a CGI
On Sat, Jun 20, 2009 at 6:52 PM, Peter Pentchevr...@ringlet.net wrote: Your package should place the files into /usr/share/hoogle/www/. After that, it should either create a file in /etc/apache2/conf.d/ containing something like this (that's what phppgadmin does): Alias /hoogle /usr/share/hoogle/www/ Uhh, doesn't that mean the package will clobber /hoogle for every vhost on the server? -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: ampache-themes (updated package)
Dear mentors, I am looking for a sponsor for the new version 3.4.3-1 of my package ampache-themes. I have contacted my usual sponsor but he is unable to sponsor ampache-themes at this time due to other commitments. It builds these binary packages: ampache-themes - Themes for Ampache I have added the 2col theme and have removed loney-tunes. I bumped debhelper version to 7. The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/a/ampache-themes - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/a/ampache-themes/ampache-themes_3.4.3-1.dsc I would be glad if someone uploaded this package for me. Kind regards Charlie Smotherman signature.asc Description: This is a digitally signed message part
Re: Packaging data for a CGI
On Sat, Jun 20, 2009 at 08:39:46PM +0800, Paul Wise wrote: On Sat, Jun 20, 2009 at 6:52 PM, Peter Pentchevr...@ringlet.net wrote: Your package should place the files into /usr/share/hoogle/www/. After that, it should either create a file in /etc/apache2/conf.d/ containing something like this (that's what phppgadmin does): Alias /hoogle /usr/share/hoogle/www/ Uhh, doesn't that mean the package will clobber /hoogle for every vhost on the server? Actually, it does - that's why I mentioned phpmyadmin's advising the user to do that only for the virtual hosts that need it. G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If I were you, who would be reading this sentence? pgpnV3r7czIoH.pgp Description: PGP signature
Re: RFS: kernelcheck
Theoretically speaking, what if I found someone within the Debian community with a trusted identity who could package the program from source for me, and then upload it. Could I then remain anonymous as the upstream author? And is there a website for that? :) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: kernelcheck
On Sat, 20 Jun 2009 10:22:24 -0400, Master Kernel wrote: Theoretically speaking, [..] As already replied in private mail, please read the thread on debian-devel: http://lists.debian.org/debian-devel/2009/06/msg00601.html Kindly, David -- . ''`. 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
OT:Need to locate Debianistas that are TIVO hackers
Any of you who are TIVO hackers Debianistas; please contact me via e-mail off the lists. If you reply on the list I will not see it as freakin GMail scrubs the replies with my name in the header. That's a whole other issue. I am starting a personal project to design a process for using Debian to set up a TIVO series 2 box as a smart web TV system. This may even have already been done but I can not find anything online directly related to it. Thanks! -- John Foster -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Creating a transition package for source and binary switching
In 200906200345.35499.peter.fritzs...@gmx.de, Peter Fritzsche wrote: The idea behind it is that the 3: can go away No, it can't. The part before the first colon is the epoch and it is assumed to be 0 for any package that doesn't have one. Therefore any version without an epoch will be considered to be a lower version (that 3:1.1-2) by dpkg and any higher-level tools, including apt. Once an epoch is in place, it is required to stay. That's one reason the should be avoided if possible. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Packaging data for a CGI
In 20090620133708.gc1...@straylight.m.ringlet.net, Peter Pentchev wrote: On Sat, Jun 20, 2009 at 08:39:46PM +0800, Paul Wise wrote: On Sat, Jun 20, 2009 at 6:52 PM, Peter Pentchevr...@ringlet.net wrote: Your package should place the files into /usr/share/hoogle/www/. After that, it should either create a file in /etc/apache2/conf.d/ containing something like this (that's what phppgadmin does): Alias /hoogle /usr/share/hoogle/www/ Uhh, doesn't that mean the package will clobber /hoogle for every vhost on the server? Actually, it does Alternatively, you could put it as a file in /etc/apache2/sites-available. Then it can easily be enabled if the administrator desires, but it is disabled by default. Debian.README should document that fact, but experienced Apache 2.x on Debian administrators will find it right away. If it isn't appropriate to activate in any non-trivial environment, it might be better as /usr/share/doc/hoogle/apache.conf.example -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Creating a transition package for source and binary switching
+ Peter Fritzsche (Sat, 20 Jun 2009 03:45:35 +0200): Hi, I wanted to ask how to do a transition package the right way. Current situation is that there is a package with 3:1.1-2 in debian which changed the name and version numbering slightly. Now I wanted to create a package with the new package. Should I now add a new source package with the new binary package to the debian archives and changing the old source to a transition only package without any real source or what would be the right way? The idea behind it is that the 3: can go away since they promised to only change the numbering scheme if it doesn't violates the the ordering anymore. If the upstream name for the software has indeed changed, the reasonable thing to do is to create a new source package with the new name, and to provide the newly-named binary package from there. In that case, and only in that case (i.e., the binary package name has changed), the epoch (3:) can go away. Do you understand why? In this situation, and regarding the transitional package, you have two options: creating it from the old source as you suggest, or creating it from the new source. Normally, this latter approach is preferred, as to not have dummy source packages lying around. However, note that the transitional binary package has to have the epoch, whereas you wish for the new source and binary packages not to have it. It is possible to do that, but it takes a bit of effort. I suggest you take that approach, and investigate how to produce binaries with different versions from a same source package. (The answer is in the dpkg-gencontrol(1) man page; if you use debhelper, you'll need dh_gencontrol(1) too.) What Boyd said is correct only if there's not a package rename involved, which doesn't seem to be the case. But his explanations on the mechanics of an epoch are correct and may help you answer my question above. HTH, -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: visualboyadvance (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.8.0-5 of my package visualboyadvance. It builds these binary packages: visualboyadvance - a full featured Game Boy Advance emulator visualboyadvance-gtk - a GTK+ front-end to VisualBoyAdvance emulator The upload would fix these bugs: 498553, 515400, 529682 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/v/visualboyadvance - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/v/visualboyadvance/visualboyadvance_1.8.0-5.dsc I would be glad if someone uploaded this package for me. Kind regards Nick Ellery signature.asc Description: OpenPGP digital signature
RFS: sipwitch and ucommon
I am looking for a sponsor for GNU SIP Witch and GNU uCommon. Yes, I (now) know the rev should not be 0 ;). * Package name: sipwitch Version : 0.5.6-0 Upstream Author : me * URL : http://www.gnutelephony.org * License : GPL-3 Section : net It builds these binary packages: libsipwitch-dev - Headers and static link library for libswitch libsipwitch0 - Runtime library for sipwitch server perl-sipwitch - perl package to control local sipwitch server php5-sipwitch - php5 extension to control local sipwitch server python-sipwitch - Python package to control local sipwitch server sipwitch - sip peer media telephony server sipwitch-plugin-forward - Forward registration and redirection module for sipwitch sipwitch-plugin-scripting - Scripting plugin for sipwitch sipwitch-plugin-subscriber - Subscriber gateway plugin for sipwitch sipwitch-plugin-zeroconf - Zeroconf plugin for sipwitch * Package name: ucommon Version : 2.0.5-0 Upstream Author : me * URL : http://www.gnutelephony.org * License : LGPL-3 Section : libs It builds these binary packages: libucommon-dev - Headers and static link library for ucommon libucommon-doc - Class documentation for ucommon runtime libucommon2 - Portable C++ runtime for threads and sockets libucommon2-dbg - debugging symbols for libucommon2 These packages can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/sipwitch - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/sipwitch/sipwitch_0.5.6-0.dsc and - URL: http://mentors.debian.net/debian/pool/main/u/ucommon - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/u/ucommon/ucommon_2.0.5-0.dsc begin:vcard fn:David Sugar n:Sugar;David org:GNU Telephony email;internet:dy...@gnutelephony.org tel;work:+1 609 465 5336 url:http://www.gnutelephony.org version:2.1 end:vcard
