| | |
|
|
| realXtend 0.4 Beneath the WavesTue, 02 Dec 2008 02:40:27 -0800 by realxtendvideorealXtend offers a free open source virtual world platform with which you can create your own applications using it as a base.The realXtend viewer is an open source browser (GPL license) that you can use to experience rich multiuser virtual worlds.The realXtend server is an open source server (BSD license) with which you can make your own virtual worlds available to a larger audience. The server has a sample virtual world that you can utilise as it is or you can modify it to suit your needs. realXtend also offers free, high-quality content for your own worlds.realXtend mission is to speed up the development of the global standardized 3D-web of virtual worlds by making the best technology available to everyone, and entirely free of charge.http://www.re alxtend.org/ Related: realxtend 3d technology avatar animation virtual world open source | |
|
|
| | |
|
|
| dbdvrf #22 Debian Developer's ReferenceTue, 02 Dec 2008 01:08:55 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - those. This point applies to normal package uploads as well. * Unless the upstream source has been uploaded to security.debian.org before (by a previous security update), build the upload with full upstream source (dpkg-buildpackage -sa). If there has been a previous upload to security.debian.org with the same upstream version, you may upload without upstream source ( dpkg-buildpackage -sd). * Be sure to use the exact same *.orig.tar.gz as used in the normal archive, otherwise it is not possible to move the security fix into the main archives later. * Build the package on a clean system which only has packages installed from the distribution you are building for. If you do not have such a system yourself, you can use a debian.org machine (see Section 4.4, Debian machines ) or setup a chroot (see Section A.4.3, pbuilder and Section A.4.2, debootstrap ). 5.8.5.4. Uploading the fixed package Do NOT upload a package to the security upload queue (oldstable-security, stable-security , etc.) without prior authorization from the security team. If the package does not exactly meet the team's requirements, it will cause many problems and delays in dealing with the unwanted upload. Do NOT upload your fix to proposed-updates without coordinating with the security team. Packages from security.debian.org will be copied into the proposed-updates directory automatically. If a package with the same or a higher version number is already installed into the archive, the security update will be rejected by the archive system. That way, the stable distribution will end up without a security update for this package instead. Once you have created and tested the new package and it has been approved by the security team, it needs to be uploaded so that it can be installed in the archives. For security uploads, the place to upload to is ftp://security-maste r.debian.org/ pub/ SecurityUploadQueue/ . Once an upload to the security queue has been accepted, the package will automatically be rebuilt for all architectures and stored for verification by the security team. Uploads which are waiting for acceptance or verification areonly accessible by the security team. This is necessary since there might be fixes for security problems that cannot be disclosed yet. If a member of the security team accepts a package, it will be installed on security.debian.org as well as proposed for the proper distribution-propose d-updates on ftp-master.debian.or g. 5.9. Moving, removing, renaming, adopting, and orphaning packages Some archive manipulation operations are not automated in the Debian upload process. These procedures should be manually followed by maintainers. This chapter gives guidelines on what to do in these cases. 5.9.1. Moving packages Sometimes a package will change its section. For instance, a package from the `non-free' section might be GPL'd in a later version, in which case the package should be moved to `main' or `contrib'.^[3] If you need to change the section for one of your packages, change the package control information to place the package in the desired section, and re-upload the package (see the Debian Policy Manual for details) . You must ensure that you include the .orig.tar.gz in your upload (even if you are not uploading a new upstream version), or it will not appear in the new section together with the rest of the package. If your new section is valid, it will be moved automatically. If it does not, then contact the ftpmasters in order to understand what happened. If, on the other hand, you need to change the subsection of one of your packages (e.g., ``devel'', ``admin'') , the procedure is slightly different. Correct the subsection as found in the control file of the package, and re-upload that. Also, you'll need to get the override file updated, as described in Section 5.7, Specifying the package section, subsection and priority . 5.9.2. Removing packages If for some reason you want to completely remove a package (say, if it is an old compatibility library which is no longer required), you need to file a bug against ftp.debian.org asking that the package be removed; as all bugs, this bug should normally have normal severity. The bug title should be in the form RM: package [architecture list] -- reason, where package is the package to be removed and reason is a short summary of the reason for the removal request. [architecture list] is optional and only needed if the removal request only applies to some architectures, not all. Note that the reportbug will create a title conforming to these rules when you use it to report a bug against the ftp.debian.org pseudo-package. If you want to remove a package you maintain, you should note this in the bug title by prepending ROM (Request Related: debian developers reference | |
|
|
| dbdvrf #1 Debian Developer's ReferenceMon, 01 Dec 2008 23:52:35 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - Debian Developer's Reference Developer's Reference Team [developers-referenc e@ packages.debian.org] Andreas Barth Adam Di Carlo Raphaël Hertzog Christian Schwarz Ian Jackson ver. from 1 dec 2008 off the web. Copyright © 2004, 2005, 2006, 2007 Andreas Barth Copyright © 1998, 1999, 2000, 2001, 2002, 2003 Adam Di Carlo Copyright © 2002, 2003 Raphaël Hertzog Copyright © 1997, 1998 Christian Schwarz This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details. A copy of the GNU General Public License is available as /usr/ share/common-license s/ GPL in the Debian GNU/ Linux distribution or on the World Wide Web at the GNU web site. You can also obtain it by writing to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. If you want to print this reference, you should use the pdf version. This page is also available in French. Chapter 1. Scope of This Document The purpose of this document is to provide an overview of the recommended procedures and the available resources for Debian developers. The procedures discussed within include how to become a maintainer (Chapter 2, Applying to Become a Maintainer ); how to create new packages (Section 5.1, New packages ) and how to upload packages (Section 5.6, Uploading a package ); how to handle bug reports (Section 5.8, Handling bugs ); how to move, remove, or orphan packages (Section 5.9, Moving, removing, renaming, adopting, and orphaning packages ); how to port packages (Section 5.10, Porting and being ported ); and how and when to do interim releases of other maintainers' packages ( Section 5.11, Non-Maintainer Uploads (NMUs) ). The resources discussed in this reference include the mailing lists (Section 4.1, Mailing lists ) and servers (Section 4.4, Debian machines ); a discussion of the structure of the Debian archive (Section 4.6, The Debian archive ); explanation of the different servers which accept package uploads (Section 5.6.1, Uploading to ftp-master ); and a discussion of resources which can help maintainers with the quality of their packages ( Appendix A, Overview of Debian Maintainer Tools ). It should be clear that this reference does not discuss the technical details of Debian packages nor how to generate them. Nor does this reference detail the standards to which Debian software must comply. All of such information can be found in the Debian Policy Manual. Furthermore, this document is not an expression of formal policy . It contains documentation for the Debian system and generallyagreed-upon best practices. Thus, it is not what is called a ``normative'' document. Chapter 2. Applying to Become a Maintainer 2.1. Getting started So, you've read all the documentation, you've gone through the Debian New Maintainers' Guide, understand what everything in the hello example package is for, and you're about to Debianize your favorite piece of software. How do you actually become a Debian developer so that your work can be incorporated into the Project? Firstly, subscribe to [debian-devel@lists. debian.org] if you haven't already. Send the word subscribe in the Subject of an email to [debian-devel-REQUES T@ lists.debian.org]. In case of problems, contact the list administrator at [ listmaster@lists.deb ian.org]. More information on availablemailing lists can be found in Section 4.1, Mailing lists . [ debian-devel-announc e@ lists.debian.org] is another list which is mandatory for anyone who wishes to follow Debian's development. You should subscribe and lurk (that is, read without posting) for a bit before doing any coding, and you should post about your intentions to work on something to avoid duplicated effort. Another good list to subscribe to is [ debian-mentors@lists .debian.org]. See Section 2.2, Debian mentors and sponsors for details. The IRC channel #debian can also be helpful; see Section 4.2, IRC channels . When you know how you want to contribute to Debian GNU/Linux, you should get in contact with existing Debian maintainers whoare working on similar tasks. That way, you can learn from experienced developers. For example, if you are interested in packaging existing software for Debian, you should try to get a sponsor. A sponsor will work together with you on your package and upload it to the Debian archive once they are happy with the packaging work you have done. You can find a Related: debian developers reference | |
|
|
| | |
|
|
| DETECTOR AUTOMÁTICO DE SEÑALES - Signal Test - UGOMon, 01 Dec 2008 13:07:42 -0800 by commonrailtoolsEl Detector MM100 (Ugo) permite verificar o testear la correcta alimentación de una gran variedad de componentes electromecánicos y electrónicos como ser:- Electroinyectores common rail- Electroválvulas EGR- Electroinyectores de gasolina / gpl - Electroválvulas de geometría variable- Inyectores piezoeléctricos- Bobinas de alta tensión- Electroválvulas reguladoras de flujo- BujíasLa prueba de los componentes electromecánicos/ele ctrónicos de un motor comandado por una centralita,realizado mediante el Detector MM100, permite identificar los siguientes tipos de defectos:- Centralita no alimentada o que no funciona correctamente (señal no detectada en todos o la mayor parte de los componentes)- Falsos contactos en el cableado entre centralita y componente.- Circuito eléctrico interno del componente interrumpido.- Cortocircuito hacia masa o hacia +12V en el componente Related: common rail tools mm100 signal test argentina | |
|
|
| | |
|
|
| | |
|
|
| | |
|
|
| GPL Event 6 MixSat, 29 Nov 2008 20:08:29 -0800 by MONTGOMERYSaApBtMSG entourage's journey to chesapeake city maryland for GPL event 6. The team played in division 2/3 against 18-20 year old men, and are only 14-16 year old kids. We beat out one of the teams that has been going to GPL for 3 years and our record was 3-5. The song is Harlem streets by Immortal technique. Enjoy!! Related: gpl event msg entourage paintball xball | |
|
|
| | |
|
|
| | |
|
|
| | |
|
|
| | |
|
|
| | |
|
|
| | |
|
|
| ZX GPL onboard BragaFri, 28 Nov 2008 06:00:33 -0800 by HZeroptTrack day ALFANORD 23/11/2008 uma volta ao autódromo de Braga num ZX 1.4 a GPL, não interessa a máquina mas sim o uzo que se lhe dá... mai nada !!! Related: zx gpl track day alfanord | |
|
|
| | |
|
|
| | |
|
| |
