scratch Videos

dbdvrf #25 Debian Developer's Reference

Length: 7:12
Rating: ( ratings)
Views:
Author: h4ck3rm1k3

http://packages.debian.org/sid/developers-reference - - and/or Build-Depends-Indep. Finally, try building your package within that chrooted environment. These steps can be automated by the use of the pbuilder program which is provided by the package of the same name (see Section A.4.3, pbuilder ). If you can't set up a proper chroot, dpkg-depcheck may be of assistance (see Section A.6.7, dpkg-depcheck ) . See the Debian Policy Manual for instructions on setting build dependencies. 2. Don't set architecture to a value other than all or any unless you really mean it. In too many cases, maintainers don't follow the instructions in the Debian Policy Manual. Setting your architecture to only one architecture (such as i386 or amd64) is usually incorrect. 3. Make sure your source package is correct. Do dpkg-source -x package.dsc to make sure your source package unpacks properly. Then, in there, try building your package from scratch with dpkg-buildpackage. 4. Make sure you don't ship your source package with the debian /files or debian/ substvars files. They should be removed by the clean target of debian/rules. 5. Make sure you don't rely on locally installed or hacked configurations or programs. For instance, you should never be calling programs in /usr/local/bin or the like. Try not to rely on programs being setup in a special way. Try building your package on another machine, even if it's the same architecture. 6. Don't depend on the package you're building being installed already (a sub-case of the above issue). There are, of course, exceptions to this rule, but be aware that any case like this needs manual bootstrapping and cannot be done by automated package builders. 7. Don't rely on the compiler being a certain version, if possible. If not, then make sure your build dependencies reflect the restrictions, although you are probably asking for trouble, since different architectures sometimes standardize on different compilers. 8. Make sure your debian/ rules contains separate binary-arch and binary-indep targets, as the Debian Policy Manual requires. Make sure that both targets work independently, that is, that you can call the target without having called the other before. To test this, try to run dpkg-buildpackage -B. 5.10.2. Guidelines for porter uploads If the package builds out of the box for the architecture to be ported to, you are in luck and your job is easy. This section applies to that case; it describes how to build and upload your binary package so that it is properly installed into the archive. If you do have to patch the package in order to get it to compile for the other architecture, you are actually doing a source NMU, so consult Section 5.11.1, How to do a NMU instead. For a porter upload, no changes are being made to the source. You do not need to touch any of the files in the source package. This includes debian/changelog. The way to invoke dpkg-buildpackage is as dpkg-buildpackage -B -mporter-email. Of course, set porter-email to your email address. This will do a binary-only build of only the architecture-dependent portions of the package, using the binary-arch target in debian/rules . If you are working on a Debian machine for your porting efforts and you need to sign your upload locally for its acceptance in the archive, you can run debsign on your .changes file to have it signed conveniently, or use the remote signing mode of dpkg-sig. 5.10.2.1. Recompilation or binary-only NMU Sometimes the initial porter upload is problematic because the environment in which the package was built was not good enough (outdated or obsolete library, bad compiler, ...). Then you may just need to recompile it in an updated environment. However, you have to bump the version number in this case, so that the old bad package can be replaced in the Debian archive (dak refuses to install new packages if they don't have a version number greater than the currently available one) . You have to make sure that your binary-only NMU doesn't render the package uninstallable. This could happen when a source package generates arch-dependent and arch-independent packages that have inter-dependencies generated using dpkg's substitution variable $(Source-Version) . Despite the required modification of the changelog, these are called binary-only NMUs — there is no need in this case to trigger all other architectures to consider themselves out of date or requiring recompilation. Such recompilations require special ``magic'' version numbering, so that the archive maintenance tools recognize that, even though there is a new Debian version, there is no corresponding source update. If you get this wrong, the archive maintainers will reject your upload

RUN-DMC Megamix - Rusty Redenbacher (Mudkids)

Length: 9:42
Rating: ( ratings)
Views:
Author: theobserver317

Tags: Adidas Beats Blending Box Classic Crew DJ Groove Hell Hip-Hop Hollis House Jam Jay JMJ king Krush Leather Live Master MC's Megamixx Mixing Mudkids Of old Peter Piper Raising Redenbacher Remix Rhyme Rock Run's Run-DMC Rusty School Scratching Sucker Than Tougher Tribute Turntablism

Respect the pioneers. They always made me try harder. There will never be another group like RUN-DMCPlaylist:'Rock Box''Darryl And Joe''Jam Master jammin''Peter Piper''Sucker MC's''Run's House''Hollis Crew''Beats To The Rhyme'RIP: JMJMUDKIDS ON MYSPACE - http://myspace.com/mudkidsMUDKIDS TV - http://youtube.com/user/theobserver317PREHENSILE TALES (RUSTY'S BLOG) - http://redenbach.blogspot.com

video of tasco getting a scratch.avi

Length: 0:11
Rating: ( ratings)
Views:
Author: tascarni

Tags: animals aussie belly bulldogs dogs scratch

tasco having a belly scratch

dbdvrf #13 Debian Developer's Reference

Length: 7:50
Rating: ( ratings)
Views:
Author: h4ck3rm1k3

Tags: debian developers reference

http://packages.debian.org/sid/developers-reference - - (-) mails classified under the given keyword(s). Define the list (=) of accepted keywords. This changes the set of accepted keywords of all the currently active subscriptions of a user. keyword [sourcepackage] [[email]] {+|-|=} [list of keywords] Same as previous item but overrides the keywords list for the indicated source package. quit | thanks | -- Stops processing commands. All following lines are ignored by the bot. The pts-subscribe command-line utility (from the devscripts package) can be handy to temporarily subscribe to some packages, for example after having made an non-maintainer upload. 4.10.2. Filtering PTS mails Once you are subscribed to a package, you will get the mails sent to sourcepackage@ packages.qa.debian.org. Those mails have special headers appended to let you filter them in a special mailbox (e.g. with procmail). The added headers are X-Loop, X-PTS-Package, X-PTS-Keyword and X-Unsubscribe. Here is an example of added headers for a source upload notification on the dpkg package: X-Loop: dpkg@packages.qa.debian.org X-PTS-Package: dpkg X-PTS-Keyword: upload-source List-Unsubscribe: [mailto: pts@qa.debian.org?body= unsubscribe+dpkg] 4.10.3. Forwarding VCS commits in the PTS If you use a publicly accessible VCS repository for maintaining your Debian package, you may want to forward the commit notification to the PTS so that the subscribers (and possible co-maintainers) can closely follow the package's evolution. Once you set up the VCS repository to generate commit notifications, you just have to make sure it sends a copy of those mails to sourcepackage_ cvs@packages.qa.debian.org. Only the people who accept the cvs keyword will receive these notifications. Note that the mail need to be sent from a debian.org machine, otherwise you'll have to add the X-PTS-Approved: 1 header. For Subversion repositories, the usage of svnmailer is recommended. See http: //wiki.debian.org/Alioth/ PackagingProject for an example on how to do it. 4.10.4. The PTS web interface The PTS has a web interface at http://packages.qa.debian.org/ that puts together a lot of information about each source package. It features many useful links (BTS, QA stats, contact information, DDTP translation status, buildd logs) and gathers much more information from various places (30 latest changelog entries, testing status, ...). It's a very useful tool if you want to know what's going on with a specific source package. Furthermore there's a form that allows easy subscription to the PTS via email. You can jump directly to the web page concerning a specific source package with a URL like http://packages.qa.debian.org/ sourcepackage. This web interface has been designed like a portal for the development of packages: you can add custom content on your packages' pages. You can add static information (news items that are meant to stay available indefinitely) and news items in the latest news section. Static news items can be used to indicate: * the availability of a project hosted on Alioth for co-maintaining the package * a link to the upstream web site * a link to the upstream bug tracker * the existence of an IRC channel dedicated to the software * any other available resource that could be useful in the maintenance of the package Usual news items may be used to announce that: * beta packages are available for testing * final packages are expected for next week * the packaging is about to be redone from scratch * backports are available * the maintainer is on vacation (if they wish to publish this information) * a NMU is being worked on * something important will affect the package Both kinds of news are generated in a similar manner: you just have to send an email either to [pts-static-news@ qa.debian.org] or to [pts-news@qa.debian.org]. The mail should indicate which package is concerned by having the name of the source package in a X-PTS-Package mail header or in a Package pseudo-header (like the BTS reports). If a URL is available in the X-PTS-Url mail header or in the Url pseudo-header, then the result is a link to that URL instead of a complete news item. Here are a few examples of valid mails used to generate news items in the PTS. The first one adds a link to the cvsweb interface of debian-cd in the Static information section: From: Raphael Hertzog [hertzog@debian.org] To: pts-static-news@qa.debian.org Subject: Browse debian-cd SVN repositoryPackage: debian-cd Url: http://svn.debian.org/ viewsvn/debian-cd/trunk/ The second one is an announcement sent to a mailing list which is also sent to the PTS so that it is published on the PTS web page of the package. Note the use of the BCC field to avoid answers sent to the PTS by mistake. From: Raphael Hertzog [hertzog@debian.org] To: debian-gtk-gnome@lists.debian.org

Scratching Bruno!

Length: 0:35
Rating: ( ratings)
Views:
Author: TheRyNoH

Tags: Bruno BT Bull Dog Dogs English Funny hanging Itch Puppy Scratch sitting terrier TheRyNoH

That's it, just me scratching Bruno