dbdvrf #51 Debian Developer's Reference
- Length: 7:30
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - The debian/packages file contains instruction to build packages and there is no need to create any Makefile files. There is possibility to use macro engine similar to the one used in SPECS files from RPM source packages. For more informations see YADA site. A.3.5.**equivs equivs is another package for making packages. It is often suggested for local use if you need to make a package simply to fulfill dependencies. It is also sometimes used when making ``meta-packages'', which are packages whose only purpose is to depend on other packages. A.4.**Package builders The following packages help with the package building process, general driving dpkg-buildpackage as well as handling supportingtasks. A.4.1.**cvs-buildpackage cvs-buildpackage provides the capability to inject or import Debian source packages into a CVS repository, build a Debian package from the CVS repository, and helps in integrating upstream changes into the repository. These utilities provide an infrastructure to facilitate the use of CVS by Debian maintainers. This allows one to keep separate CVS branches of a package for stable, unstable and possibly experimental distributions, along with the other benefits of a version control system. A.4.2.**debootstrap The debootstrap package and script allows you to bootstrap a Debian base system into any part of your filesystem. By base system, we mean the bare minimum of packages required to operate and install the rest of the system. Having a system like this can be useful in many ways. For instance, you can chroot into it if you want to test your build dependencies. Or you can test how your package behaves when installed into a bare base system. Chroot builders use this package; see below. A.4.3.**pbuilder pbuilder constructs a chrooted system, and builds a package inside the chroot. It is very useful to check that a package's build-dependencies are correct, and to be sure that unnecessary and wrong build dependencies will not exist in the resulting package. A related package is pbuilder-uml, which goes even further by doing the build within a User Mode Linux environment.A.4.4.**sbuild sbuild is another automated builder. It can use chrooted environments as well. It can be used stand-alone, or as part of a networked, distributed build environment. As the latter, it is part of the system used by porters to build binary packages for all the available architectures. See Section**5.10.3.3, ***wanna-build*** for more information, and http://buildd.debian.org / to see the system in action. A.5.**Package uploaders The following packages help automate or simplify the process of uploading packages into the official archive. A.5.1.**dupload dupload is a package and a script to automatically upload Debian packages to the Debian archive, to log the upload, and to send mail about the upload of a package. You can configure it for newupload locations or methods. A.5.2.**dput The dput package and script does much the same thing as dupload, but in a different way. It has some features over dupload, such as the ability to check the GnuPG signature and checksums before uploading, and the possibility of running dinstall in dry-run mode after the upload. A.5.3.**dcut The dcut script (part of the package Section* *A.5.2, ***dput*** ) helps in removing files from the ftp upload directory. A.6.**Maintenance automation The following tools help automate different maintenance tasks, from adding changelog entries or signature lines and looking up bugs in Emacs to making use of the newest and official config.sub. A.6.1.**devscripts devscripts is a package containing wrappers and tools which are very helpful for maintaining your Debian packages. Example scripts include debchange and dch, which manipulate your debian/ changelog file from the command-line, and debuild, which is a wrapper around dpkg-buildpackage. The bts utility is also very helpful to update the state of bug reports on the command line. uscan can be used to watch for new upstream versions of your packages. debrsign can be used to remotely sign a package prior to upload, which is nice when the machine you build the package on is different from where your GPG keys are. See the devscripts(1) manual page for a complete list of available scripts. A.6.2.**autotools-dev autotools-dev contains best practices for people who maintain packages which use autoconf and/or automake. Also contains canonical config.sub and config.guess files which are known to work on all Debian ports. A.6.3.**dpkg-repack dpkg-repack creates Debian package file out of a package that has already been installed. If any changes have been made to the package while it was unpacked (e.g., files in /etc were modified), the new package will inherit the changes. This utility can make it easy to copy packages from one computer to another, or to recreate
dbdvrf #49 Debian Developer's Reference
- Length: 7:14
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - is a good idea to send the document to the corresponding l10n mailing list, asking for a review. Once it has been done, you should feel more confident in the quality of the translation, and feel safe to include it in your package. 8.2.3.**How to get a given translation updated If you have some translations of a given text lying around, each time you update the original, you should ask the previous translator to update the translation with your new changes. Keep in mind that this task takes time; at least one week to get the update reviewed and all. If the translator is unresponsive, you may ask for help on the corresponding l10n mailing list. If everything fails, don'tforget to put a warning in the translated document, stating that the translation is somehow outdated, and that the reader should refer to the original document if possible. Avoid removing a translation completely because it is outdated. Old documentation is often better than no documentation at all for non-English speakers. 8.2.4.**How to handle a bug report concerning a translation The best solution may be to mark the bug as forwarded to upstream, and forward it to both the previous translator and his /her team (using the corresponding debian-l10n-XXX mailing list). 8.3.**I18N & L10N FAQ for translators While reading this, please keep in mind that there is no general procedure within Debian concerning these points, and that in any case, you should collaborate with your team and the package maintainer. 8.3.1.**How to help the translation effort Choose what you want to translate, make sure that nobody is already working on it (using your debian-l10n-XXX mailing list), translate it, get it reviewed by other native speakers on your l10n mailing list, and provide it to the maintainer of the package (see next point). 8.3.2.**How to provide a translation for inclusion in a package Make sure your translation is correct (asking for review on your l10n mailing list) before providing it for inclusion. It will save time for everyone, and avoid the chaos resulting in having several versions of the same document in bug reports. The best solution is to file a regular bug containing thetranslation against the package. Make sure to use the 'PATCH' tag, and to not use a severity higher than 'wishlist', since the lack of translation never prevented a program from running. 8.4.**Best current practice concerning l10n * As a maintainer, never edit the translations in any way (even to reformat the layout) without asking on the corresponding l10n mailing list. You risk for example breaksing the encoding of the file by doing so. Moreover, what you consider an error can be right (or even needed) in the given language. * As a translator, if you find an error in the original text, make sure to report it. Translators are often the most attentive readers of a given text, and if they don't report the errors they find, nobody will. * In any case, remember that the major issue with l10n is that it requires several people to cooperate, and that it is very easy to start a flamewar about small problems because of misunderstandings. So if you have problems with your interlocutor, ask for help on the corresponding l10n mailing list, on debian-i18n, or even on debian-devel (but beware, l10n discussions very often become flamewars on that list :) * In any case, cooperation can only be achieved with mutual respect. Appendix**A.**Overview of Debian Maintainer Tools This section contains a rough overview of the tools available to maintainers. The following is by no means complete or definitive, but just a guide to some of the more popular tools.Debian maintainer tools are meant to aid developers and free their time for critical tasks. As Larry Wall says, there's more than one way to do it. Some people prefer to use high-level package maintenance tools and some do not. Debian is officially agnostic on this issue; any tool which gets the job done is fine. Therefore, this section is not meant to stipulate to anyone which tools they should use or how they should go about their duties of maintainership. Nor is it meant to endorse any particular tool to the exclusion of a competing tool. Most of the descriptions of these packages come from the actual package descriptions themselves. Further information can be found in the package documentation itself. You can also see more info with the command apt-cache show [package-name]. A.1.**Core tools The following tools are pretty much required for any maintainer. A.1.1.**dpkg-dev dpkg-dev contains the tools (including dpkg-source) required to unpack, build, and upload Debian source packages. These utilities contain the fundamental, low-level functionality required to create and manipulate packages; as such, they are
dbdvrf #46 Debian Developer's Reference
- Length: 7:8
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - that they decide to help finish a major upgrade (like a new perl version which requires recompilation of all the binary modules) . The rules for non-maintainer uploads differ during the parties because the announcement of the party is considered prior notice for NMU. If you have packages that may be affected by the party (because they have release critical bugs for example) , you should send an update to each of the corresponding bug to explain their current status and what you expect from the party. If you don't want an NMU, or if you're only interested in a patch, or if you will deal yourself with the bug, please explain that in the BTS. People participating in the party have special rules for NMU, they can NMU without prior notice if they upload their NMU to DELAYED/3-day at least. All other NMU rules apply as usually; they should send the patch of the NMU to the BTS (to one of the open bugs fixed by the NMU, or to a new bug, tagged fixed). They should also respect any particular wishes of the maintainer. If you don't feel confident about doing an NMU, just send a patch to the BTS. It's far better than a broken NMU. 7.3.**Contacting other maintainers During your lifetime within Debian, you will have to contact other maintainers for various reasons. You may want to discuss a new way of cooperating between a set of related packages, or you may simply remind someone that a new upstream version is available and that you need it.Looking up the email address of the maintainer for the package can be distracting. Fortunately, there is a simple email alias, [package]@packages.debian.org, which provides a way to email the maintainer, whatever their individual email address (or addresses) may be. Replace [package] with the name of a source or a binary package. You may also be interested in contacting the persons who are subscribed to a given source package via Section* *4.10, ***The Package Tracking System* ** . You can do so by using the [package] @packages.qa.debian.org email address. 7.4.**Dealing with inactive and/or unreachable maintainers If you notice that a package is lacking maintenance, you should make sure that the maintainer is active and will continue to work on their packages. It is possible that they are not active any more, but haven't registered out of the system, so to speak. On the other hand, it is also possible that they just need a reminder. There is a simple system (the MIA database) in which information about maintainers who are deemed Missing In Action is recorded. When a member of the QA group contacts an inactive maintainer or finds more information about one, this is recorded in the MIA database. This system is available in /org/ qa.debian.org/mia on the host qa.debian.org , and can be queried with the mia-query tool. Use mia-query --help to see how to query the database. If you find that no information has been recorded about an inactive maintainer yet, or that you can add more information, you should generally proceed as follows. The first step is to politely contact the maintainer, and wait a reasonable time for a response. It is quite hard to define reasonable time, but it is important to take into account that real life is sometimes very hectic. One way to handle this would be to send a reminder after two weeks. If the maintainer doesn't reply within four weeks (a month), one can assume that a response will probably not happen. If that happens, you should investigate further, and try to gather as much useful information about the maintainer in question as possible. This includes: * The echelon information available through the developers' LDAP database, which indicates when the developer last posted to a Debian mailing list. (This includes mails about uploads distributed via the [ debian-devel-changes@ lists.debian.org] list.) Also, remember to check whether the maintainer is marked as on vacation in the database. * The number of packages this maintainer is responsible for, and the condition of those packages. In particular, are there any RC bugs that have been open for ages? Furthermore, how many bugs are there in general? Another important piece of information is whether the packages have been NMUed, and if so, by whom. * Is there any activity of the maintainer outside of Debian? For example, they might have posted something recently to non-Debian mailing lists or news groups. A bit of a problem are packages which were sponsored *** the maintainer is not an official Debian developer. The echelon information is not available for sponsored people, for example, so you need to find and contact the Debian developer who has actually uploaded the package. Given that they signed the package, they're responsible for the upload anyhow, and are likely to know what happened
dbdvrf #45 Debian Developer's Reference
- Length: 7:29
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - to the original filename. Note that you don't need to depend on sharutils to get the uudecode program if you use perl's pack function. The code could look like uuencode-file: perl -ne 'print(pack "u", $$_);' $(file) ] $(file).uuencoded uudecode-file: perl -ne 'print(unpack "u", $$_);' $(file).uuencoded ] $(file) Chapter**7.**Beyond Packaging Debian is about a lot more than just packaging software and maintaining those packages. This chapter contains information about ways, often really critical ways, to contribute to Debian beyond simply creating and maintaining packages. As a volunteer organization, Debian relies on the discretion of its members in choosing what they want to work on and in choosing the most critical thing to spend their time on. 7.1.**Bug reporting We encourage you to file bugs as you find them in Debian packages. In fact, Debian developers are often the first line testers. Finding and reporting bugs in other developers' packages improves the quality of Debian. Read the instructions for reporting bugs in the Debian bug tracking system. Try to submit the bug from a normal user account at which you are likely to receive mail, so that people can reach you if they need further information about the bug. Do not submit bugs as root. You can use a tool like reportbug(1) to submit bugs. It can automate and generally ease the process. Make sure the bug is not already filed against a package. Each package has a bug list easily reachable at http:// bugs.debian.org/packagename Utilities like querybts( 1) can also provide you with this information (and reportbug will usually invoke querybts before sending, too). Try to direct your bugs to the proper location. When for example your bug is about a package which overwrites files from another package, check the bug lists for both of those packages in order to avoid filing duplicate bug reports. For extra credit, you can go through other packages, merging bugs which are reported more than once, or tagging bugs `fixed' when they have already been fixed. Note that when you are neither the bug submitter nor the package maintainer, you should not actually close the bug (unless you secure permission fromthe maintainer). From time to time you may want to check what has been going on with the bug reports that you submitted. Take this opportunity to close those that you can't reproduce anymore. To find out all the bugs you submitted, you just have to visit http:// bugs.debian.org/from:[your-email-addr]. 7.1.1.**Reporting lots of bugs at once (mass bug filing) Reporting a great number of bugs for the same problem on a great number of different packages *** i.e., more than 10 *** is a deprecated practice. Take all possible steps to avoid submitting bulk bugs at all. For instance, if checking for the problem can be automated, add a new check to lintian so that an error or warning is emitted. If you report more than 10 bugs on the same topic at once, it is recommended that you send a message to [ debian-devel@lists.debian.org] describing your intention before submitting the report, and mentioning the fact in the subject of your mail. This will allow other developers to verify that the bug is a real problem. In addition, it will help prevent a situation in which several maintainers start filing the same bug report simultaneously. Please use the programms dd-list and if appropriate whodepends (from the package devscripts) to generate a list of all affected packages, and include the output in your mail to [ debian-devel@lists.debian.org]. Note that when sending lots of bugs on the same subject, you should send the bug report to [maintonly@bugs.debian.org] so that the bug report is not forwarded to the bug distribution mailing list. 7.2.**Quality Assurance effort 7.2.1.**Daily work Even though there is a dedicated group of people for Quality Assurance, QA duties are not reserved solely for them. You can participate in this effort by keeping your packages as bug-free as possible, and as lintian-clean (see Section**A.2.1, ***lintian*** ) as possible. If you do not find that possible, then you should consider orphaning some of your packages (see Section**5.9.4, ***Orphaning a package* ** ). Alternatively, you may ask the help of other people in order to catch up with the backlog of bugs that you have (you can ask for help on [debian-qa@lists.debian.org] or [debian-devel@lists.debian.org]) . At the same time, you can look for co-maintainers (see Section**5.12, * **Collaborative maintenance*** ). 7.2.2.**Bug squashing parties From time to time the QA group organizes bug squashing parties to get rid of as many problems as possible. They are announced on [debian-devel-announce@ lists.debian.org] and the announcement explains which area will be the focus of the party: usually they focus on release critical bugs but it may happen
free runescape account
- Length: 3:22
- Rating: ( ratings)
- Views:
- Author: ghrca
Tags: maxhits moneymaking runescape
send you email in a comment and ill send username,pass and bankpin in email
Page: 1 of 34245