| | |
|
|
| | |
|
|
| | |
|
|
| House for sale in Paphos Area, Paphos, CyprusTue, 02 Dec 2008 07:26:19 -0800 by op24upload011http://www.overseasp roperty24.co.uk/en/a broad_properties/atl antik_mittelmeer_sue d_europa/138.html?al lagents_id=779&r ef_no_p2=126214%2F77 9%5Bgpg%5D&categ ory=HouseHouse (House) for sale in Paphos Area, Paphos, South Cyprus Cyprus Country: Cyprus, South CyprusLocation: Paphos, Paphos AreaType: NewStyle: Detached VillaSize: 331 sq m Bedrooms: 3Garden: Not SpecifiedTerrace: Not SpecifiedFeatures:Pr ivate Pool, Parking: Covered DrivewayPlot Size:2172 Description Viewing Info. Rental Pack Property Description Villas are situated right on the beach-front of one of the most sought areas in Cyprus, the mythological Baths of Aphrodite and the spectacular, Akamas National Park, the pride of the area. Part of the natural beauty of Akamas Peninsula, where there are virgin forests and untouched beaches. While driving towards this exclusive project one can admire the scenic coastal view. Amenities such as supermarkets, a post office, banks, restaurants and other stores are within 3 minutes drive from this unique project. Consists of detached villas, each including a private pool and large spacious verandas. It is worth noting, plots are large sized from 500m² - 2250m². The exterior and interior of each villa has been carefully designed giving priority to a more Mediterranean style of architecture, ensuring all villas the magical view of Cyprus spectacular golden sunsets.Due to its exquisite location, this project gives one the opportunity to own an exclusive Cyprus property, ideal for permanent or vacation residence a solid investment, which also ensures tranquility in this amazing setting. Thousands of properties at http://www.overseasp roperty24.co.ukovers eas property ads Related: apartment flat homes hotel housing plot property real-estate villa | |
|
|
| FFXII NLBLLG Part 27 - VyraalTue, 02 Dec 2008 06:00:17 -0800 by SailorNemesis1A bit more challenging then previous hunts in the beginning, but once blind connects the battle is basically over. After blind, I also inflict Vyraal with silence so he cannot use Immobilizega any more, then simply Windslicer Shot him down. He seems to focus on nearest enemies and does that really fast with his instant attacks, later Attack CT 0 and even haste buffed. Reviving as fast as possible is priority, afterwards berserking Reddas, who will die quite often anyway. Null EVA after 50% HP, as well as Restore to get back 30% do not make this easier either, but in the end it is a fight of reviving fast enough while Bal kills it. Related: final fantasy xii ffxii nlb llg nlbllg no license board low level game 122333 vyraal | |
|
|
| FFXII NLBLLG Part 26 - Gil SnapperTue, 02 Dec 2008 04:19:45 -0800 by SailorNemesis1Again, Reddas makes fights like this easy. The fight starts with blinding, then silencing Gil Snapper. Blind makes surviving possible, while Silence takes care of his ice based spells, which could else easily obliterate my party as Snapper has Piercing Magic. While it is true that Gil Snapper has purify, while there is someone standing near it he won't be using it, so Reddas and the Seeq stand close all the time and he will keep statuses.The most annoying move left is Flash, but nothing that some Eye Drops cannot take care of.Only problem left to take care of is Gil Snappers Damage Return passive ability. Reddas kills himself all the time for me, so I took a HP 50% - Hi Potion Gambit in. Worked quite good but when too many guys died at once, as priority would be on Phoenix Downs, which then leads to another death of Balthier or Reddas.. death spiral, really. Related: final fantasy xii ffxii nlb llg nlbllg no license board low level game 122333 gil snapper | |
|
|
| | |
|
|
| dbdvrf #38 Debian Developer's ReferenceTue, 02 Dec 2008 01:49:28 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - Maintainer scripts include the files debian/postinst, debian/ preinst, debian/prerm and debian/postrm. These scripts take care of any package installation or deinstallation setup which isn't handled merely by the creation or removal of files and directories. The following instructions supplement the Debian Policy. Maintainer scripts must be idempotent. That means that you need to make sure nothing bad will happen if the script is called twice where it would usually be called once. Standard input and output may be redirected (e.g. into pipes) for logging purposes, so don't rely on them being a tty. All prompting or interactive configuration should be kept to a minimum. When it is necessary, you should use the debconfpackage for the interface. Remember that prompting in any case can only be in the configure stage of the postinst script. Keep the maintainer scripts as simple as possible. We suggest you use pure POSIX shell scripts. Remember, if you do need any bash features, the maintainer script must have a bash shebang line. POSIX shell or Bash are preferred to Perl, since they enable debhelper to easily add bits to the scripts. If you change your maintainer scripts, be sure to test package removal, double installation, and purging. Be sure that a purged package is completely gone, that is, it must remove any files created, directly or indirectly, in any maintainer script. If you need to check for the existence of a command, you shoulduse something like if [ -x /usr/sbin/install-do cs ]; then ... If you don't wish to hard-code the path of a command in your maintainer script, the following POSIX-compliant shell function may help: pathfind() { OLDIFS="$IFS" IFS=: for p in $PATH; do if [ -x "$p/$*" ]; then IFS="$OLDIFS" return 0 fi done IFS="$OLDIFS" return 1 } You can use this function to search $PATH for a command name, passed as an argument. It returns true (zero) if the command was found, and false if not. This is really the most portable way, since command -v, type, and which are not POSIX. While which is an acceptable alternative, since it is from the required debianutils package, it's not on the root partition. That is, it's in /usr/bin rather than /bin, so one can't use it in scripts which are run before the /usr partition is mounted. Most scripts won't have this problem, though. 6.5.**Configuration management with debconf Debconf is a configuration management system which can be used by all the various packaging scripts (postinst mainly) to request feedback from the user concerning how to configure the package. Direct user interactions must now be avoided in favor of debconf interaction. This will enable non-interactive installations in the future. Debconf is a great tool but it is often poorly used. Many common mistakes are listed in the debconf-devel(7) man page. It is something that you must read if you decide to use debconf. Also, we document some best practices here. These guidelines include some writing style and typography recommendations, general considerations about debconf usage as well as more specific recommendations for some parts of the distribution (the installation system for instance). 6.5.1.**Do not abuse debconf Since debconf appeared in Debian, it has been widely abused and several criticisms received by the Debian distribution come from debconf abuse with the need of answering a wide bunch of questions before getting any little thing installed. Keep usage notes to what they belong: the NEWS.Debian, or README.Debian file. Only use notes for important notes which may directly affect the package usability. Remember that notes willalways block the install until confirmed or bother the user by email. Carefully choose the questions priorities in maintainer scripts. See debconf-devel(7) for details about priorities. Most questions should use medium and low priorities. 6.5.2.**General recommendations for authors and translators 6.5.2.1.**Write correct English Most Debian package maintainers are not native English speakers. So, writing properly phrased templates may not be easy for them. Please use (and abuse) [debian-l10n-english @ lists.debian.org] mailing list. Have your templates proofread. Badly written templates give a poor image of your package, of your work...or even of Debian itself. Avoid technical jargon as much as possible. If some terms sound common to you, they may be impossible to understand for others. If you cannot avoid them, try to explain them ( use the extended description). When doing so, try to balance between verbosity and simplicity. 6.5.2.2.**Be kind to translators Debconf templates may be translated. Debconf, along with its sister package po-debconf offers a simple framework for getting templates translated by translation teams or even individuals. Related: debian developers reference | |
|
|
| dbdvrf #36 Debian Developer's ReferenceTue, 02 Dec 2008 01:44:10 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - add-on to should be put in here. * Why should I want this package? This is related to the above, but not the same (this is a mail user agent; this is cool, fast, interfaces with PGP and LDAP and IMAP, has features X, Y, and Z). * If this package should not be installed directly, but is pulled in by another package, this should be mentioned. * If the package is experimental, or there are other reasons it should not be used, if there are other packages that should be used instead, it should be here as well. * How is this package different from the competition? Is it a better implementation? more features? different features? Why should I choose this package. 6.2.4.**Upstream home page We recommend that you add the URL for the package's home page in the Homepage field of the Source section in debian/control. Adding this information in the package description itself is considered deprecated. 6.2.5.**Version Control System location There are additional fields for the location of the Version Control System in debian/control. 6.2.5.1.**Vcs-Browse r Value of this field should be a http:// URL pointing to a web-browsable copy of the Version Control System repository used to maintain the given package, if available. The information is meant to be useful for the final user, willing to browse the latest work done on the package (e.g. when looking for the patch fixing a bug tagged as pending in the bug tracking system). 6.2.5.2.**Vcs-* Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar) , cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn ( Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. In the following example, an instance of the field for a Subversion repository of the vim package is shown. Note how the URL is in the svn:// scheme (instead of svn+ssh: //) and how it points to the trunk/ branch. The use of the Vcs-Browser and Homepage fields described above is also shown. Source: vim Section: editors Priority: optional [snip] Vcs-Svn: svn://svn.debian.org / svn/pkg-vim/trunk/pa ckages/ vim Vcs-Browser: http:/ /svn.debian.org/wsvn / pkg-vim/trunk/packag es/ vim Homepage: http://www.vim.org 6.3.**Best practices for debian/changelog The following practices supplement the Policy on changelog files . 6.3.1.**Writing useful changelog entries The changelog entry for a package revision documents changes in that revision, and only them. Concentrate on describing significant and user-visible changes that were made since the last version. Focus on what was changed *** who, how and when are usually less important. Having said that, remember to politely attribute people who have provided notable help in making the package (e.g., those who have sent in patches). There's no need to elaborate the trivial and obvious changes. You can also aggregate several changes in one entry. On the other hand, don't be overly terse if you have undertaken a major change. Be especially clear if there are changes that affect the behaviour of the program. For further explanations, use the README.Debian file. Use common English so that the majority of readers can comprehend it. Avoid abbreviations, tech-speak and jargon when explaining changes that close bugs, especially for bugs filed by users that did not strike you as particularly technically savvy. Be polite, don't swear. It is sometimes desirable to prefix changelog entries with the names of the files that were changed. However, there's no need to explicitly list each and every last one of the changed files, especially if the change was small or repetitive. You may use wildcards. When referring to bugs, don't assume anything. Say what the problem was, how it was fixed, and append the closes: #nnnnn string. See Section** 5.8.4, ***When bugs are closed by new uploads* ** for more information. 6.3.2.**Common misconceptions Related: debian developers reference | |
|
|
| SSFIIT HD Remix Music-.Chun Li StageTue, 02 Dec 2008 01:38:44 -0800 by evilaj2010Control Motion Changes:* Super input window is larger and is a fixed size, rather than random size.* Aerial spinning bird kick can be done with charge down, up+kick, so that you can do it after a pogo, like in SF2:Hyper FightingBuffs:* Removed df+medium kick move (it only ever got in the way, so removing it helps her).* Ground spinning bird kick has a new parabolic arc. It can also air-juggle and deals a fair amount of dizzy.* Aerial spinning bird kick travels more straight now, then falls in an arc at the end* Lighting legs easier to execute (now requires 3 presses of a given kick button rather than 5 presses)Nerfs:* df+roundhouse (the "neckbreaker") no longer crosses up, removing the loop of repeated knockdowns against some characters.* Lighting legs do less damage and have barely worse priority in Chun Li's stomach area.* Chun Li's super can still be stored, but deals much less damage, and follow up with upkicks can get only one extra hit on some characters and usually misses against others.http://www.si rlin.net/articles/st reet-fighter-hd-remi x-chun-li.html Related: super street fighter ii turbo hd remix music ost bgm soundtrack arrange sound game xbox 360 xbla psn ps3 playstation | |
|
|
| dbdvrf #30 Debian Developer's ReferenceTue, 02 Dec 2008 01:29:40 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - source in order to get them to compile for their target architecture; that would be considered a source NMU rather than a binary-only NMU. As you can see, we don't distinguish in terminology between porter NMUs and non-porter NMUs. Both classes of NMUs, source and binary-only, can be lumped under the term ``NMU''. However, this often leads to confusion, since most people think ``source NMU'' when they think ``NMU''. So it's best to be careful: always use ``binary NMU'' or ``binNMU'' for binary-only NMUs. 5.12. Collaborative maintenance Collaborative maintenance is a term describing the sharing of Debian package maintenance duties by several people. This collaboration is almost always a good idea, since it generally results in higher quality and faster bug fix turnaround times. It is strongly recommended that packages with a priority of Standard or which are part of the base set have co-maintainers. Generally there is a primary maintainer and one or more co-maintainers. The primary maintainer is the person whose name is listed in the Maintainer field of the debian/control file. Co-maintainers are all the other maintainers, usually listed in the Uploaders field of the debian/control file. In its most basic form, the process of adding a new co-maintainer is quite easy: * Setup the co-maintainer with access to the sources you build the package from. Generally this implies you are using a network-capable version control system, such as CVS or Subversion. Alioth (see Section 4.12, Debian's GForge installation: Alioth ) provides such tools, amongst others. * Add the co-maintainer's correct maintainer name and address to the Uploaders field in the first paragraph of the debian/ control file. Uploaders: John Buzz [jbuzz@debian.org], Adam Rex [arex@debian.org] * Using the PTS (Section 4.10, The Package Tracking System ), the co-maintainers should subscribe themselves to the appropriate source package. Another form of collaborative maintenance is team maintenance, which is recommended if you maintain several packages with the same group of developers. In that case, the Maintainer and Uploaders field of each package must be managed with care. It isrecommended to choose between one of the two following schemes: 1. Put the team member mainly responsible for the package in the Maintainer field. In the Uploaders, put the mailing list address, and the team members who care for the package. 2. Put the mailing list address in the Maintainer field. In the Uploaders field, put the team members who care for the package. In this case, you must make sure the mailing list accept bug reports without any human interaction (like moderation for non-subscribers). In any case, it is a bad idea to automatically put all team members in the Uploaders field. It clutters the Developer's Package Overview listing (see Section 4.11, Developer's packages overview ) with packages one doesn't really care for, and creates a false sense of good maintenance. 5.13. The testing distribution 5.13.1. Basics Packages are usually installed into the testing distribution after they have undergone some degree of testing in unstable. They must be in sync on all architectures and mustn't have dependencies that make them uninstallable; they also have to have generally no known release-critical bugs at the time they're installed into testing . This way, testing should always be close to being a release candidate. Please see below for details. 5.13.2. Updates from unstable The scripts that update the testing distribution are run twice each day, right after the installation of the updated packages; these scripts are called britney. They generate the Packages files for the testing distribution, but they do so in an intelligent manner; they try to avoid any inconsistency and to use only non-buggy packages. The inclusion of a package from unstable is conditional on the following: * The package must have been available in unstable for 2, 5 or 10 days, depending on the urgency (high, medium or low). Please note that the urgency is sticky, meaning that the highest urgency uploaded since the previous testing transition is taken into account. Those delays may be doubled during a freeze, or testing transitions may be switched off altogether; * It must not have new release-critical bugs (RC bugs affecting the version available in unstable, but not affecting the version in testing); * It must be available on all architectures on which it has previously been built in unstable. Section 4.9.2, The dak ls utility may be of interest to check that information; * It must not break any dependency of a package which is already available in testing; * The packages on which Related: debian developers reference | |
|
|
| dbdvrf #24 Debian Developer's ReferenceTue, 02 Dec 2008 01:13:50 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - 5.9.4. Orphaning a package If you can no longer maintain a package, you need to inform others, and see that the package is marked as orphaned. You should set the package maintainer to Debian QA Group [packages@qa.debian. org] and submit a bug report against the pseudo package wnpp. The bug report should be titled O: package -- short description indicating that the package is now orphaned. The severity of the bug should be set to normal; if the package has a priority of standard or higher, it should be set to important. If you feel it's necessary, send a copy to [ debian-devel@lists.d ebian.org] by putting the address in the X-Debbugs-CC: header of the message (no, don't use CC:, because that way the message's subject won't indicate the bug number). If you just intend to give the package away, but you can keep maintainership for the moment, then you should instead submit a bug against wnpp and title it RFA: package -- short description. RFA stands for Request For Adoption. More information is on the WNPP web pages. 5.9.5. Adopting a package A list of packages in need of a new maintainer is available in the Work-Needing and Prospective Packages list (WNPP). If you wish to take over maintenance of any of the packages listed in the WNPP, please take a look at the aforementioned page for information and procedures. It is not OK to simply take over a package that you feel is neglected ? that would be package hijacking. You can, of course,contact the current maintainer and ask them if you may take over the package. If you have reason to believe a maintainer has gone AWOL (absent without leave), see Section 7.4, Dealing with inactive and/or unreachable maintainers . Generally, you may not take over the package without the assent of the current maintainer. Even if they ignore you, that is still not grounds to take over a package. Complaints about maintainers should be brought up on the developers' mailing list. If the discussion doesn't end with a positive conclusion, and the issue is of a technical nature, consider bringing it to the attention of the technical committee ( see the technical committee web page for more information). If you take over an old package, you probably want to be listed as the package's official maintainer in the bug system. This will happen automatically once you upload a new version with an updated Maintainer: field, although it can take a few hours after the upload is done. If you do not expect to upload a new version for a while, you can use Section 4.10, The Package Tracking System to get the bug reports. However, make sure that the old maintainer has no problem with the fact that they will continue to receive the bugs during that time. 5.10. Porting and being ported Debian supports an ever-increasing number of architectures. Even if you are not a porter, and you don't use any architecture but one, it is part of your duty as a maintainer to be aware of issues of portability. Therefore, even if you are not a porter, you should read most of this chapter. Porting is the act of building Debian packages for architectures that are different from the original architecture of the package maintainer's binary package. It is a unique and essential activity. In fact, porters do most of the actual compiling of Debian packages. For instance, when a maintainer uploads a (portable) source packages with binaries for the i386 architecture, it will be built for each of the other architectures, amounting to 12 more builds. 5.10.1. Being kind to porters Porters have a difficult and unique task, since they are required to deal with a large volume of packages. Ideally, every source package should build right out of the box. Unfortunately, this is often not the case. This section contains a checklist of ``gotchas'' often committed by Debian maintainers ? common problems which often stymie porters, and make their jobs unnecessarily difficult. The first and most important thing is to respond quickly to bug or issues raised by porters. Please treat porters with courtesy, as if they were in fact co-maintainers of your package (which, in a way, they are). Please be tolerant of succinct or even unclear bug reports; do your best to hunt down whatever the problem is. By far, most of the problems encountered by porters are caused by packaging bugs in the source packages. Here is a checklist of things you should check or be aware of. 1. Make sure that your Build-Depends and Build-Depends-Indep settings in debian/ control are set properly. The best way to validate this is to use the debootstrap package to create an unstable chroot environment (see Section A.4.2, debootstrap ). Within that chrooted environment, install the build-essential package and any package dependencies mentioned in Build-Depends Related: debian developers reference | |
|
|
| 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 #17 Debian Developer's ReferenceTue, 02 Dec 2008 00:55:27 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - is uploaded multiple times per day to ftp-master.debian.or g. With a fairly recent dput, this section [tfheen_delayed] method = scp fqdn = gluck.debian.org incoming = ~tfheen in ~/.dput.cf should work fine for uploading to the DELAYED queue. Note: Since this upload queue goes to ftp-master.debian.or g, the prescription found in Section 5.6.1, Uploading to ftp-master applies here as well. 5.6.3. Security uploads 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. For details, please see section Section 5.8.5, Handling security-related bugs . 5.6.4. Other upload queues The scp queues on ftp-master.debian.or g, and security.debian.org are mostly unusable due to the login restrictions on those hosts. The anonymous queues on ftp.uni-erlangen.de and ftp.uk.debian.org are currently down. Work is underway to resurrect them. The queues on master.debian.org, samosa.debian.org, master.debian.or.jp, and ftp.chiark.greenend. org.uk are down permanently, and will not be resurrected. The queue in Japan will be replaced with a new queue on hp.debian.or.jp some day. 5.6.5. Notification that a new package has been installed The Debian archive maintainers are responsible for handling package uploads. For the most part, uploads are automatically handled on a daily basis by the archive maintenance tools, katie . Specifically, updates to existing packages to the unstable distribution are handled automatically. In other cases, notably new packages, placing the uploaded package into the distribution is handled manually. When uploads are handled manually, the change to the archive may take up to a month to occur. Please be patient. In any case, you will receive an email notification indicating that the package has been added to the archive, which also indicates which bugs will be closed by the upload. Please examine this notification carefully, checking if any bugs you meant to close didn't get triggered.The installation notification also includes information on what section the package was inserted into. If there is a disparity, you will receive a separate email notifying you of that. Read on below. Note that if you upload via queues, the queue daemon software will also send you a notification by email. 5.7. Specifying the package section, subsection and priority The debian/control file's Section and Priority fields do not actually specify where the file will be placed in the archive, nor its priority. In order to retain the overall integrity of the archive, it is the archive maintainers who have control over these fields. The values in the debian/control file are actuallyjust hints. The archive maintainers keep track of the canonical sections and priorities for packages in the override file. If there is a disparity between the override file and the package's fields as indicated in debian/control, then you will receive an email noting the divergence when the package is installed into the archive. You can either correct your debian/control file for your next upload, or else you may wish to make a change in the override file. To alter the actual section that a package is put in, you need to first make sure that the debian/control file in your package is accurate. Next, send an email [override-change@ debian.org] or submit a bug against ftp.debian.org requesting that the section or priority for your package be changed from the old section or priority to the new one. Be sure to explain your reasoning. For more information about override files, see dpkg-scanpackages (1) and http://www.debian.or g/ Bugs/Developer#maint incorrect. Note that the Section field describes both the section as well as the subsection, which are described in Section 4.6.1, Sections . If the section is main, it should be omitted. The list of allowable subsections can be found in http: // www.debian.org/doc/d ebian-policy/ ch-archive.html#s-su bsections. 5.8. Handling bugs Every developer has to be able to work with the Debian bug tracking system. This includes knowing how to file bug reports properly (see Section 7.1, Bug reporting ), how to update them and reorder them, and how to process and close them. The bug tracking system's features are described in the BTS documentation for developers. This includes closing bugs, sending followup messages, assigning severities and tags, marking bugs as forwarded, and other issues. Operations such as reassigning bugs to other packages, merging separate bug reports about the same issue, or reopening bugs when they are prematurely closed, are handled using the so-called control mail server. All of the commands available on Related: debian developers reference | |
|
|
| dbdvrf #12 Debian Developer's ReferenceTue, 02 Dec 2008 00:41:48 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - in testing and that there has been a binary-only NMU of the package for all architectures. Each version of the package has been recompiled on all architectures. 4.10. The Package Tracking System The Package Tracking System (PTS) is an email-based tool to track the activity of a source package. This really means that you can get the same emails that the package maintainer gets, simply by subscribing to the package in the PTS. Each email sent through the PTS is classified under one of the keywords listed below. This will let you select the mails that you want to receive. By default you will get: bts All the bug reports and following discussions. bts-control The email notifications from [control@bugs.debian .org] about bug report status changes. upload-source The email notification from katie when an uploaded source package is accepted. katie-other Other warning and error emails from katie (such as an override disparity for the section and/or the priority field). default Any non-automatic email sent to the PTS by people who wanted to contact the subscribers of the package. This can be done by sending mail to sourcepackage@packag es.qa.debian.org. In order to prevent spam, all messages sent to these addresses must contain the X-PTS-Approved header with a non-empty value. contact Mails sent to the maintainer through the *@packages.debian.or g email aliases. summary Regular summary emails about the package's status. Currently, only progression in testing is sent. You can also decide to receive additional information: upload-binary The email notification from katie when an uploaded binary package is accepted. In other words, whenever a build daemon or a porter uploads your package for another architecture, you can get an email to track how your package gets recompiled for all architectures. cvs VCS commit notifications, if the package has a VCS repository and the maintainer has set up forwarding of commit notifications to the PTS. The "cvs" name is historic, in most cases commit notifications will come from some other VCS like subversion or git. ddtp Translations of descriptions or debconf templates submitted to the Debian Description Translation Project. derivatives Information about changes made to the package in derivative distributions (for example Ubuntu). 4.10.1. The PTS email interface You can control your subscription(s) to the PTS by sending various commands to [pts@qa.debian.org]. subscribe [sourcepackage] [[email]] Subscribes email to communications related to the source package sourcepackage. Sender address is used if the second argument is not present. If sourcepackage is not a valid source package, you'll get a warning. However if it's a valid binary package, the PTS will subscribe you to the corresponding source package. unsubscribe [sourcepackage] [[email]] Removes a previous subscription to the source package sourcepackage using the specified email address or the sender address if the second argument is left out. unsubscribeall [[email]] Removes all subscriptions of the specified email address or the sender address if the second argument is left out. which [[email]] Lists all subscriptions for the sender or the email address optionally specified. keyword [[email]] Tells you the keywords that you are accepting. For an explanation of keywords, see above. Here's a quick summary: * bts: mails coming from the Debian Bug Tracking System * bts-control: reply to mails sent to [ control@bugs.debian. org] * summary: automatic summary mails about the state of a package * contact: mails sent to the maintainer through the *@packages.debian.or g aliases * cvs: notification of VCS commits * ddtp: translations of descriptions and debconf templates * derivatives: changes made on the package by derivative distributions * upload-source: announce of a new source upload that has been accepted * upload-binary: announce of a new binary-only upload (porting) * katie-other: other mails from ftpmasters (override disparity, etc.) * default: all the other mails (those which aren't automatic) keyword [sourcepackage] [[email]] Same as the previous item but for the given source package, since you may select a different set of keywords for each source package. keyword [[email]] {+|-|= } [list of keywords] Accept (+) or refuse (-) mails classified under the given keyword(s). Define the list (=) of accepted keywords. This changes the default set of keywords accepted by a user. keywordall [[email]] {+|-|=} [list of keywords] Accept (+) or refuse Related: debian developers reference | |
|
|
| | |
|
|
| | |
|
|
| bupropion tramadolMon, 01 Dec 2008 22:49:25 -0800 by 9313493ctramadol and anti parkinson meds buy cheap tramadol online 35009 tramadol sales online pharmacies no prescription tramadol addiction treatment with methadone buy information tramadol tramadol prescriptions priority overnight buy tramadol online now can you snort tramadol search results tramadol overnight tramadol hydrochloride synthesis Related: health | |
|
|
| keyword tramadolMon, 01 Dec 2008 22:17:22 -0800 by 13324bfbeware shipping tramadol tramadol and cash on delivery tramadol hydrochloride xl flonase myonlinemeds biz tramadol klonopin tramadol interaction tramadol ibs tramadol 180 ct 49 tramadol prescriptions priority overnight prescription tramadol drug akyma tramadol Related: health | |
|
|
| Barista - Feeding TimeMon, 01 Dec 2008 19:03:28 -0800 by JonseySquarepantsPLEASE READ BEFORE COMMENTING!!This is me feeding my guinea pig Barista. I ALWAYS make sure Barista does not starve, get thirsty, cold, or get sick. Guinea pigs are my #1 priority before anything else. His food bowl and water bottle were emptied before filming and those timothy hay sticks are very long and the bottle of yellow colored liquid was some vitamin drop thing (which is essential for a proper guinea pig diet). The Timothy hay was for Guinea pigs, Rabbits and hamsters (I think). So please enjoy Barista - Feeding time.©2008 JSGuineapiggies Productions.Special Thanks to JustGuineaPiggies. Related: barista guinea pig pig barista gp barry barry pellets fiesta timothy hay justguineapiggies funny | |
|
| |
