Re: Writing manpages (was: Re: Man and UTF-8.)
Hi Rogério, Em Wed, Nov 18, 2009 at 07:33:22AM -0200, Rogério Brito escreveu: | Date: Wed, 18 Nov 2009 07:33:22 -0200 | From: Rogério Brito rbr...@ime.usp.br | To: debian-mentors@lists.debian.org | Subject: Re: Writing manpages (was: Re: Man and UTF-8.) | | I guess that I only have two options left, as it seems: Perl's pod | format or docbook. The only problem with docbook is that I don't know | how to avoid the torrent of markups and typing some of them is long. | | Now, if there were some LaTeX - man, that would be amazing. Have you ever tried txt2tags ? http://txt2tags.sourceforge.net/ You can write almost anything using its wiki format and convert to man, latex, wikiwiki, and so on ;-) It's really simple to use it :D Cheers, LEslie -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Fwd: Urgent: Query on dhclient in handling IP conflict
Hi, Could you please help me out by directing this query to the appropriate forum. Thanks and regards, Sathya -- Forwarded message -- From: sathya sai sathyasai.esh...@gmail.com Date: Mon, Dec 21, 2009 at 5:51 PM Subject: Urgent: Query on dhclient in handling IP conflict To: pe...@debian.org, m...@debian.org, apoll...@debian.org Cc: sathya sai sathyasai.esh...@gmail.com Hi All, This is Sathya, a debian etch user who uses dhclient package to configure the IP address. Firstly, I would like to give my heartily thanks to you all for your great dedicated contribution towards this package. As I am newbie to this mailing list, I am not aware on where to post this query. So, thought of this mail directly sending it to you all. My system has following dhclient packages, ii dhcp3-client 3.0.4-13+etch2DHCP Client ii dhcp3-common 3.0.4-13+etch2 Common files used by all the dhcp3* packages ii dhcp3-server 3.0.4-13+etch2 DHCP server for automatic IP address assignm Following is the problem which I am facing now, I have a subnet whose IP addressing is managed by DHCP server. But, one system in that is intentionally assigned a static IP address. In multiple occasions, I am now getting IP conflicts in my subnet. On further analysing this problem, I could undertand that this probelm is happening because, 1. As DHCP server is un-aware of this statically configured system; upon receiving the DHCPREQUEST from a system (which is running dhclient) from this subnet, the DHCP server gets an unused IP from its IP pools offers it to that client. *In somecases, dhcp server is giving the same IP address as that of statically configured system. * 2. As on receiving the IP address, *our dhclient is not performing a final check on the existence of IP conflict for prior received IP address using ARP broadcast,* it goes ahead in configuring the system with this IP address. This results in an IP conflict to exist between these two systems (with this system and a system with statically configured IP). *I could also see that, our debian dhclient presently DOES NOT HAVE AN OPTION TO IMPLICITLY SUPPORT THIS.* But as per RFC 2131, the client should perform a final check to detect the IP conflict and send DHCPDECLINE message. Please find the RFC snippet as in below, 5. The client receives the DHCPACK message with configuration parameters. *The client SHOULD perform a final check on the parameters *(e.g., ARP for allocated network address), and notes the duration of the lease specified in the DHCPACK message. At this point, the client is configured. *If the client detects that the address is already in use (e.g., through the use of ARP), the client MUST send a DHCPDECLINE message* to the server and restarts the configuration process. And also I could find the following information on dhclient manpage regarding this, Before actually configuring the address, dhclient-script should somehow ARP for it and exit with a nonzero status if it receives a reply. In this case, the client will send a DHCPDECLINE message to the server and acquire a different address. This may also be done in the RENEW, REBIND, or REBOOT states, but is not required, and indeed may not be desirable. As changes to DHCP server is out of our control we are not sure on what IP would be statically configured to the system, could you please let me know your thoughts on how do this we can fix this in dhclient code to automatically detect duplicate address using ARP broadcast ? If this support this not there in present dhclient, could you please let me know by when this the community planning to give a patch for this. As I am in need of urgent need for fix on this issue, it would be really helpful if I can get your thoughts on this by earliest. Thanks a lot in advance for understanding. Regards, Sathya
Re: Urgent: Query on dhclient in handling IP conflict
On Mon, Dec 21, 2009 at 9:03 PM, sathya sai sathyasai.esh...@gmail.com wrote: Could you please help me out by directing this query to the appropriate forum. debian-user would be the appropriate forum. Please note that Debian etch is very old and will soon lose security support. You should really upgrade to Debian lenny at your earliest convenience. I'd suggest testing for the bug on both lenny and the in-development release, squeeze. -- 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
Re: Urgent: Query on dhclient in handling IP conflict
Hi Paul, I hope, this is a common problem with the dhclient which would occur even on debian lenny. Thanks and regards, Sathya On Mon, Dec 21, 2009 at 6:47 PM, Paul Wise p...@debian.org wrote: On Mon, Dec 21, 2009 at 9:03 PM, sathya sai sathyasai.esh...@gmail.com wrote: Could you please help me out by directing this query to the appropriate forum. debian-user would be the appropriate forum. Please note that Debian etch is very old and will soon lose security support. You should really upgrade to Debian lenny at your earliest convenience. I'd suggest testing for the bug on both lenny and the in-development release, squeeze. -- bye, pabs http://wiki.debian.org/PaulWise
RFS: hexalate
Dear mentors, I am looking for a sponsor for my package hexalate. * Package name: hexalate Version : 1.0.0-1 Upstream Author : Graeme Gottgra...@gottcode.org * URL : http://gottcode.org/hexalate * License : GPLV3 Section : games It builds these binary packages: hexalate - a color matching game The package appears to be lintian clean. The upload would fix these bugs: 561801 My motivation for maintaining this package is: The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/h/hexalate - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/h/hexalate/hexalate_1.0.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards Tang Ke -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: hexalate
Il giorno lun, 21/12/2009 alle 21.13 +0800, Tang Ke ha scritto: Dear mentors, I am looking for a sponsor for my package hexalate. * Package name: hexalate Version : 1.0.0-1 [...] The upload would fix these bugs: 561801 As it was pointed out in this bug, hexalate is already in Debian (and that same version is in Ubuntu too). Moreover, just as a reference, there are some things that would need to be tuned in your package. Luckily, you can just discover them by comparing it with the already existing one: mkdir 1 mkdir 2 cd 1 apt-get source hexalate cd ../2 dget \ http://mentors.debian.net/debian/pool/main/h/hexalate/hexalate_1.0.0-1.dsc dpkg -x dpkg-source -x hexalate_1.0.0-1.dsc diff -r hexalate-1.0.0 ../1/hexalate-1.0.0 | less You'll see some changes due to CDBS, but also some things that you would have had to clean; for instance, the long description, the qt4-qmake build-dependency, the On Ubuntu systems in debian/copyright. Pietro -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: gtkhash (2nd try)
Alessio Treglia wrote: Dear mentors, I am looking for a sponsor for my package gtkhash. Uploaded :) David -- . ''`. Debian developer | 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 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Urgent: Query on dhclient in handling IP conflict
Hi Matt, Thanks for your mail. I had already thought on these possiblities. But the problem here is, we dont have control over neither our DHCP server (it can be either Windows or Linux based servers) nor the client PC which configures static IP (anybody in the subnet can configure the IPs on their wish). I hope, this is true with the real time deployment scenario. Considering all these scenario, I felt that it would be better for our dhclient to do a ARP broadcast as per RFC 2131 to detect the IP conflict and send DHCPDECLINE in case of it. So that the DHCP server can understand the existance of duplicate address and respond with the newer address accordingly. Could please let me know your thoughts on this, so that we can make your dhclient much more better on this. Thanks and regards, Sathya On Mon, Dec 21, 2009 at 7:22 PM, Mathieu Trudel-Lapierre mathieu.tl@ gmail.com wrote: On Mon, Dec 21, 2009 at 8:22 AM, sathya sai sathyasai.esh...@gmail.com wrote: Hi Paul, I hope, this is a common problem with the dhclient which would occur even on debian lenny. Thanks and regards, Sathya On Mon, Dec 21, 2009 at 6:47 PM, Paul Wise p...@debian.org wrote: On Mon, Dec 21, 2009 at 9:03 PM, sathya sai sathyasai.esh...@gmail.com wrote: Could you please help me out by directing this query to the appropriate forum. debian-user would be the appropriate forum. Please note that Debian etch is very old and will soon lose security support. You should really upgrade to Debian lenny at your earliest convenience. I'd suggest testing for the bug on both lenny and the in-development release, squeeze. Without wanting to diminish what you've done (which certainly aims at resolving a particular issue you might have been seeing), I think there would be more elegant solutions to your problem than IP conflict detection (although it could be nice to have, it would probably be more effectively reported upstream). TL;DR: There is another way to avoid conflicts without requiring *any* development on dhcp3-server or dhcp3-client. You can use reservations or change the IP pool range to resolve this issue. Longer version: What I'd do in this case is either of two solutions: 1- Rather simply, and to retain most of what has been done already; change the DHCP range of IP addresses given out to dynamic clients to something that doesn't contain the IP of the machines that are statically assigned. For example, set aside 2-31 for statically assigned systems, then 32-254 for dynamic assignment. 2- Slightly change the setup: have all the systems get an IP from DHCP, but make sure that the IPs given out to the machines that should be statically assigned are always the same. You can do this easily using reservations, which is a matter of matching an IP to a particular MAC address. In dnsmasq, that's done with /etc/ethers. In dhcpd, it's done in dhcpd.conf in a special stanza. Both these options address the same issue: systems will no longer be assigned conflicting IP addresses. Additionally, there are some pretty nifty things you could do with option 2 from then on, such as dynamically building DNS information from the DHCP leases. Your servers which as assigned the same IP all the time are always there, and names of the clients (which could be new systems added from visitors or whatever), could publish their desired name through DHCP and have this information visible in DNS requests (just as you could also do reverse DNS). Sorry if this is rather verbose, just expressing a different way of solving the situation. With kind regards, / Matt
RFS: calculix
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my packages for calculix. * Package names : calculix-ccx, calculix-cgx Version : 2.0.0-1 Upstream Author : pierrot idf.dres...@gmx.net * URL : http://www.calculix.de * License : gpl Section : science It builds these binary packages: ccx - calculix crunchix - finite element program (solver) cgx - calculix graphix - finite element program (pre/postprocessor) The upload would fix these bugs: #506518 My motivation for maintaining this package is: calculix is a small but very powerful and well documented 3d fea program, which is maintained by a crowd of enthusiasts, it runs platform-independent, connects to many other fea tools (e.g. gmsh) and would fit nicely into debian The packages can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/c/calculix-ccx - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/c/calculix-ccx/calculix-ccx_2.0.0-1.dsc - - URL: http://mentors.debian.net/debian/pool/main/c/calculix-cgx - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/c/calculix-cgx/calculix-cgx_2.0.0-1.dsc I would be glad if someone uploaded these packages for me. Kind regards pierrot -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksvh50ACgkQNDe+3b60z64XkwCfalLGy9uyhz39eX6QipUIVsmx 5r8AoIS3kkv6olunu5+uttfSrg4AqUQF =7qGr -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: piwigo
Dear mentors, I am looking for a sponsor for my package piwigo. * Package namenbsp;nbsp;nbsp; : piwigo nbsp; Versionnbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; : 2.0.7-1 nbsp; Upstream Author : Pierrick LE-GALLnbsp;nbsp;nbsp; p...@piwigo.org * URLnbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; : http://piwigo.org/ * Licensenbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; : GPL nbsp; Sectionnbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; : web Piwigo is photo gallery software for the web. nbsp;Piwigo is a photo gallery software for the web, built by an active community nbsp;of users and developers. Extensions make Piwigo easily customizable. Some greats features : nbsp; - localization in English, French, German, Spanish, Italian, Portuguese, ... nbsp; - tags nbsp; - permissions on photos and categories nbsp; - virtual category allowing picture to be in multiple categories nbsp; - meaningful URLs nbsp; - user comments and rating nbsp; - use of iptc and exif metadatas nbsp; - notification of news by email or RSS feed nbsp; - best rated, most view pictures nbsp; - web API allowing requests or administration from other applications. The package appears to be lintian clean. The upload would fix these bugs: 561868 My motivation for maintaining this package is: I like this software and I'm involved in his development. I can follow easier features. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/piwigo - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/piwigo/piwigo_2.0.7-1.dsc I would be glad if someone uploaded this package for me. Regards, Nicolas Roudaire signature.asc Description: OpenPGP digital signature
Re: RFS: piwigo
Hello, I'll help you upload it... Regards, Sylvain Le Gall -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: piwigo
Hi, thanks Sylvain, I'll apprciate. Regards, Nicolas 2009/12/21 Sylvain Le Gall lt;gil...@debian.orggt; Hello, I'll help you upload it... Regards, Sylvain Le Gall -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org signature.asc Description: OpenPGP digital signature
Re: Urgent: Query on dhclient in handling IP conflict
Hi, Can someone please help me out on this. Thanks and regards, Sathya On Mon, Dec 21, 2009 at 8:09 PM, sathya sai sathyasai.esh...@gmail.comwrote: Hi Matt, Thanks for your mail. I had already thought on these possiblities. But the problem here is, we dont have control over neither our DHCP server (it can be either Windows or Linux based servers) nor the client PC which configures static IP (anybody in the subnet can configure the IPs on their wish). I hope, this is true with the real time deployment scenario. Considering all these scenario, I felt that it would be better for our dhclient to do a ARP broadcast as per RFC 2131 to detect the IP conflict and send DHCPDECLINE in case of it. So that the DHCP server can understand the existance of duplicate address and respond with the newer address accordingly. Could please let me know your thoughts on this, so that we can make your dhclient much more better on this. Thanks and regards, Sathya On Mon, Dec 21, 2009 at 7:22 PM, Mathieu Trudel-Lapierre mathieu.tl@ gmail.com wrote: On Mon, Dec 21, 2009 at 8:22 AM, sathya sai sathyasai.esh...@gmail.com wrote: Hi Paul, I hope, this is a common problem with the dhclient which would occur even on debian lenny. Thanks and regards, Sathya On Mon, Dec 21, 2009 at 6:47 PM, Paul Wise p...@debian.org wrote: On Mon, Dec 21, 2009 at 9:03 PM, sathya sai sathyasai.esh...@gmail.com wrote: Could you please help me out by directing this query to the appropriate forum. debian-user would be the appropriate forum. Please note that Debian etch is very old and will soon lose security support. You should really upgrade to Debian lenny at your earliest convenience. I'd suggest testing for the bug on both lenny and the in-development release, squeeze. Without wanting to diminish what you've done (which certainly aims at resolving a particular issue you might have been seeing), I think there would be more elegant solutions to your problem than IP conflict detection (although it could be nice to have, it would probably be more effectively reported upstream). TL;DR: There is another way to avoid conflicts without requiring *any* development on dhcp3-server or dhcp3-client. You can use reservations or change the IP pool range to resolve this issue. Longer version: What I'd do in this case is either of two solutions: 1- Rather simply, and to retain most of what has been done already; change the DHCP range of IP addresses given out to dynamic clients to something that doesn't contain the IP of the machines that are statically assigned. For example, set aside 2-31 for statically assigned systems, then 32-254 for dynamic assignment. 2- Slightly change the setup: have all the systems get an IP from DHCP, but make sure that the IPs given out to the machines that should be statically assigned are always the same. You can do this easily using reservations, which is a matter of matching an IP to a particular MAC address. In dnsmasq, that's done with /etc/ethers. In dhcpd, it's done in dhcpd.conf in a special stanza. Both these options address the same issue: systems will no longer be assigned conflicting IP addresses. Additionally, there are some pretty nifty things you could do with option 2 from then on, such as dynamically building DNS information from the DHCP leases. Your servers which as assigned the same IP all the time are always there, and names of the clients (which could be new systems added from visitors or whatever), could publish their desired name through DHCP and have this information visible in DNS requests (just as you could also do reverse DNS). Sorry if this is rather verbose, just expressing a different way of solving the situation. With kind regards, / Matt
Re: Urgent: Query on dhclient in handling IP conflict
Please take it to the debian-user list, and don't post the question repeatedly. sathya sai wrote: Hi, Can someone please help me out on this. Thanks and regards, Sathya On Mon, Dec 21, 2009 at 8:09 PM, sathya sai sathyasai.esh...@gmail.comwrote: Hi Matt, Thanks for your mail. I had already thought on these possiblities. But the problem here is, we dont have control over neither our DHCP server (it can be either Windows or Linux based servers) nor the client PC which configures static IP (anybody in the subnet can configure the IPs on their wish). I hope, this is true with the real time deployment scenario. Considering all these scenario, I felt that it would be better for our dhclient to do a ARP broadcast as per RFC 2131 to detect the IP conflict and send DHCPDECLINE in case of it. So that the DHCP server can understand the existance of duplicate address and respond with the newer address accordingly. Could please let me know your thoughts on this, so that we can make your dhclient much more better on this. Thanks and regards, Sathya On Mon, Dec 21, 2009 at 7:22 PM, Mathieu Trudel-Lapierre mathieu.tl@ gmail.com wrote: On Mon, Dec 21, 2009 at 8:22 AM, sathya sai sathyasai.esh...@gmail.com wrote: Hi Paul, I hope, this is a common problem with the dhclient which would occur even on debian lenny. Thanks and regards, Sathya On Mon, Dec 21, 2009 at 6:47 PM, Paul Wise p...@debian.org wrote: On Mon, Dec 21, 2009 at 9:03 PM, sathya sai sathyasai.esh...@gmail.com wrote: Could you please help me out by directing this query to the appropriate forum. debian-user would be the appropriate forum. Please note that Debian etch is very old and will soon lose security support. You should really upgrade to Debian lenny at your earliest convenience. I'd suggest testing for the bug on both lenny and the in-development release, squeeze. Without wanting to diminish what you've done (which certainly aims at resolving a particular issue you might have been seeing), I think there would be more elegant solutions to your problem than IP conflict detection (although it could be nice to have, it would probably be more effectively reported upstream). TL;DR: There is another way to avoid conflicts without requiring *any* development on dhcp3-server or dhcp3-client. You can use reservations or change the IP pool range to resolve this issue. Longer version: What I'd do in this case is either of two solutions: 1- Rather simply, and to retain most of what has been done already; change the DHCP range of IP addresses given out to dynamic clients to something that doesn't contain the IP of the machines that are statically assigned. For example, set aside 2-31 for statically assigned systems, then 32-254 for dynamic assignment. 2- Slightly change the setup: have all the systems get an IP from DHCP, but make sure that the IPs given out to the machines that should be statically assigned are always the same. You can do this easily using reservations, which is a matter of matching an IP to a particular MAC address. In dnsmasq, that's done with /etc/ethers. In dhcpd, it's done in dhcpd.conf in a special stanza. Both these options address the same issue: systems will no longer be assigned conflicting IP addresses. Additionally, there are some pretty nifty things you could do with option 2 from then on, such as dynamically building DNS information from the DHCP leases. Your servers which as assigned the same IP all the time are always there, and names of the clients (which could be new systems added from visitors or whatever), could publish their desired name through DHCP and have this information visible in DNS requests (just as you could also do reverse DNS). Sorry if this is rather verbose, just expressing a different way of solving the situation. With kind regards, / Matt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
