| | |
|
|
| | |
|
|
| My Breast BrotherTue, 02 Dec 2008 00:56:22 -0800 by FatxKidxProductionsChocolate comprises a number of raw and processed foods that are produced from the seed of the tropical cacao tree. Native to lowland, tropical South America, cacao has been cultivated for at least three millennia in Central America and Mexico, with its earliest documented use around 1100 BC. Related: american will wiesenfeld john simple plan | |
|
|
| | |
|
|
| DON'T DRINK&RIDE!. WARNING-GRAPHIC PICTURESTue, 02 Dec 2008 00:54:43 -0800 by samuirescueA young lad (19yrs) visits his friends and has a few beers too many befor riding home on his expensively modified Honda 125... with the almost inevitable results! He wanders over the white line and clips a pick-up coming the other way. He was unconcious but alive when we reached the scene, but had serious head injuries and multiple lacerations and abrasions. He regained conciousness a litlle as we were transferring him to the spinal board, and, confused and disorientated, started struggling and fighting with us. We eventually managed to get him strapped to the spinal board and get him to the hospital in Nathon. He has a good chance of surviving, but we don't know at this stage how well he will recover from his head injuries. Again... NO HELMET! WEAR A HELMET IN THAILAND, AND DON'T DRINK AND RIDE!!! Related: accident injury blood crash hospital thailand samui rescue motorbike pickup crazy drunk | |
|
|
| | |
|
|
| | |
|
|
| | |
|
|
| dbdvrf #16 Debian Developer's ReferenceTue, 02 Dec 2008 00:52:45 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - part of the source version number is 0 or 1, indicating a new upstream version. This behavior may be modified by using -sa to always include it or -sd to always leave it out. If no original source is included in the upload, the original source tar-file used by dpkg-source when constructing the .dsc file and diff to be uploaded must be byte-for-byte identical with the one already in the archive. Please notice that, in non-native packages, permissions on files that are not present in the .orig.tar.gz will not be preserved, as diff does not store file permissions in the patch. 5.5. Picking a distribution Each upload needs to specify which distribution the package is intended for. The package build process extracts this information from the first line of the debian/ changelog file and places it in the Distribution field of the .changes file. There are several possible values for this field: stable, unstable, testing-proposed-upd ates and experimental. Normally, packages are uploaded into unstable. Actually, there are two other possible distributions: stable-security and testing-security, but read Section 5.8.5, Handling security-related bugs for more information on those. It is not possible to upload a package into several distributions at the same time. 5.5.1. Special case: uploads to the stable and oldstable distributions Uploading to stable means that the package will transfered tothe proposed-updates-new queue for review by the stable release managers, and if approved will be installed in stable-proposed-upda tes directory of the Debian archive. From there, it will be included in stable with the next point release. To ensure that your upload will be accepted, you should discuss the changes with the stable release team before you upload. For that, send a mail to the [debian-release@list s.debian.org] mailing list, including the patch you want to apply to the package version currently in stable. Always be verbose and detailed in your changelog entries for uploads to the stable distribution. Extra care should be taken when uploading to stable. Basically, a package should only be uploaded to stable if one of the following happens: * a truly critical functionality problem * the package becomes uninstallable * a released architecture lacks the package In the past, uploads to stable were used to address security problems as well. However, this practice is deprecated, as uploads used for Debian security advisories are automatically copied to the appropriate proposed-updates archive when the advisory is released. See Section 5.8.5, Handling security-related bugs for detailed information on handling security problems. If the security teams deems the problem to be too benign to be fixed through a DSA, the stable release managers are usually willing to include your fix nonetheless in a regular upload to stable.Changing anything else in the package that isn't important is discouraged, because even trivial fixes can cause bugs later on. Packages uploaded to stable need to be compiled on systems running stable, so that their dependencies are limited to the libraries (and other packages) available in stable; for example, a package uploaded to stable that depends on a library package that only exists in unstable will be rejected. Making changes to dependencies of other packages (by messing with Provides or shlibs files), possibly making those other packages uninstallable, is strongly discouraged. Uploads to the oldstable distributions are possible as long as it hasn't been archived. The same rules as for stable apply.5.5.2. Special case: uploads to testing/testing-prop osed-updates Please see the information in the testing section for details. 5.6. Uploading a package 5.6.1. Uploading to ftp-master To upload a package, you should upload the files (including the signed changes and dsc-file) with anonymous ftp to ftp-master.debian.or g in the directory /pub/ UploadQueue/. To get the files processed there, they need to be signed with a key in the Debian Developers keyring or the Debian Maintainers keyring (see http://wiki.debian.o rg/ Maintainers). Please note that you should transfer the changes file last. Otherwise, your upload may be rejected because the archive maintenance software will parse the changes file and see thatnot all files have been uploaded. You may also find the Debian packages Section A.5.1, dupload or Section A.5.2, dput useful when uploading packages. These handy programs help automate the process of uploading packages into Debian. For removing packages, please see the README file in that ftp directory, and the Debian package Section A.5.3, dcut . 5.6.2. Delayed uploads Delayed uploads are done for the moment via the delayed queue at gluck . The upload-directory is gluck:~tfheen/DELAYE D/ [012345678]-day. 0-day Related: debian developers reference | |
|
|
| dbdvrf #15 Debian Developer's ReferenceTue, 02 Dec 2008 00:50:14 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - on the list, and lets them know if anyone else is working on it already. * It lets other people thinking about working on the package know that there already is a volunteer, so efforts may be shared. * It lets the rest of the maintainers know more about the package than the one line description and the usual changelog entry ``Initial release'' that gets posted to [ debian-devel-changes @ lists.debian.org]. * It is helpful to the people who live off unstable (and form our first line of testers). We should encourage these people. * The announcements give maintainers and other interested parties a better feel of what is going on, and what is new, in the project. Please see http://ftp-master.de bian.org/REJECT-FAQ. html for common rejection reasons for a new package. 5.2. Recording changes in the package Changes that you make to the package need to be recorded in the debian/changelog. These changes should provide a concise description of what was changed, why (if it's in doubt), and note if any bugs were closed. They also record when the package was completed. This file will be installed in /usr/share/doc/ package/changelog.De bian.gz, or /usr/share/doc/packa ge/ changelog.gz for native packages. The debian/changelog file conforms to a certain structure, with a number of different fields. One field of note, the distribution, is described in Section 5.5, Picking a distribution . More information about the structure of thisfile can be found in the Debian Policy section titled debian/ changelog. Changelog entries can be used to automatically close Debian bugs when the package is installed into the archive. See Section 5.8.4, When bugs are closed by new uploads . It is conventional that the changelog entry of a package that contains a new upstream version of the software looks like this: * new upstream version There are tools to help you create entries and finalize the changelog for release ? see Section A.6.1, devscripts and Section A.6.6, dpkg-dev-el . See also Section 6.3, Best practices for debian/changelog . 5.3. Testing the package Before you upload your package, you should do basic testing on it. At a minimum, you should try the following activities (you'll need to have an older version of the same Debian package around): * Install the package and make sure the software works, or upgrade the package from an older version to your new version if a Debian package for it already exists. * Run lintian over the package. You can run lintian as follows: lintian -v package-version.chan ges. This will check the source package as well as the binary package. If you don't understand the output that lintian generates, try adding the -i switch, which will cause lintian to output a very verbose description of the problem. Normally, a package should not be uploaded if it causes lintian to emit errors (they will start with E). For more information on lintian, see Section A.2.1, lintian . * Optionally run Section A.2.2, debdiff to analyze changes from an older version, if one exists. * Downgrade the package to the previous version (if one exists) ? this tests the postrm and prerm scripts. * Remove the package, then reinstall it. * Copy the source package in a different directory and try unpacking it and rebuilding it. This tests if the package relies on existing files outside of it, or if it relies on permissions being preserved on the files shipped inside the .diff.gz file. 5.4. Layout of the source package There are two types of Debian source packages: * the so-called native packages, where there is no distinction between the original sources and the patches applied for Debian * the (more common) packages where there's an original source tarball file accompanied by another file that contains the patches applied for Debian For the native packages, the source package includes a Debian source control file (.dsc) and the source tarball (.tar.gz). A source package of a non-native package includes a Debian source control file, the original source tarball (.orig.tar.gz) and the Debian patches (.diff.gz). Whether a package is native or not is determined when it is built by dpkg-buildpackage(1) . The rest of this section relates only to non-native packages. The first time a version is uploaded which corresponds to a particular upstream version, the original source tar file should be uploaded and included in the .changes file. Subsequently, this very same tar file should be used to build the new diffsand .dsc files, and will not need to be re-uploaded. By default, dpkg-genchanges and dpkg-buildpackage will include the original source tar file if and only if the Debian revision Related: debian developers reference | |
|
|
| | |
|
|
| yo 4- cheetah sistersTue, 02 Dec 2008 00:49:45 -0800 by princess08iyathis is the very 1st vid I personally made. The pictures found in this video is from our field trip. The girls are my friends. Hope you will enjoy it! The music is made by the cheetah girls. Yes, i am their biggest fan. I miss them so much. I think they are great. What do you think?? Pls rate and comment. n_n Related: cheetah girls sisters friendship love | |
|
|
| | |
|
|
| John Cena - If It All Ended Tomorrow (WITH LYRICS)Tue, 02 Dec 2008 00:48:35 -0800 by PCRDXA Track from the 2005 album, You Cant See Me! Featuring Tha Trademarc.What Would You Do If It All Ended Tomorrow?Time Runnin Out, Ain't No More You Can BorrowSo Many Paths, which one you gonna follow?What Would You Do If It All Ended Tomorrow?What Would You Do If It All Ended Tomorrow?Time Runnin Out, Ain't No More You Can BorrowSo Many Paths, which one you gonna follow?What Would You Do, What Would You Do?Uh, this is how it go downI have the black-pound-silence so it don't make soundI pile a 150 outta town, aint nobody aroundIm in the back seat breakin it downMy love has been a past week dawg lately I foundOur press made us turn the radio downBut God bless now they talkin bout layin me downNow they on about shovels in the weight of the groundWhat now?Preachin on the way that they handle thingWaitin' patiently to do the 6-foot Same ThingNow, so I take a second look at my lifeI made too many mistakes that I just couldnt make rightShould've been more focused than I take things lightWhen I'm gone this is what ya'll will say I was likeAmerican fool, no not that baddest or coolJust a big fish caught up in the shallowish poolNot a big name playa, in fact its trueNever wanted this shit without the kats he knewHe got lucky rode the co-tails of everyones fameIn two weeks aint nobody gon' rememba his nameFuck ItI'm ready to go, I done made recordsMade monetary often that flowMore importantly though, I proved everyone wrongIts all over regardless what you say when Im goneWhat now?What Would You Do If It All Ended Tomorrow?Time Runnin Out, Ain't No More You Can BorrowSo Many Paths, which one you gonna follow?What Would You Do If It All Ended Tomorrow?What Would You Do If It All Ended Tomorrow?Time Runnin Out, Ain't No More You Can BorrowSo Many Paths, which one you gonna follow?What Would You Do, What Would You Do?I want ya'll to feel the wound, its the truth in my wordsI been quiet for too long, the truth should be heardIt was a while back, 10:20 in the morn'Kat should up on my lawn in the rug-ed uniformUnexpected, theres a knock on my doorI met this fool in the club, I don' see him beforeOpen to great him, but the second he sees meHis eyes buckle, his voice is uneasyBut it's cool, I didn't even catch it at firstI check his shoulder, homie's rockin a purseNow I know something's tricky, but I'm already sittin downHomie pipes up, you should hear what he's spittin outSays I've been sleepin wit his wifeyAnd he ain't the type of kat to take that shit lightlyI made a move and he told me homie waitReached in his purse pulled a chrome 38He asked me if I'm ready to dieSaid he was gonna pull my brains all over the skySaid he was leavin the country, and he was straight with the passportsCocked the hammer, I'm thinkin my last thoughtsI'm in a bad way, nothin could save this.I close my eyes hopin it's painlessJust waitin for the sound, ready to swallow tooBut homie havin trouble with his follow throughBy a miracle, I avoid the chalk groundHomie's confused, he just wanna be talked downHis wife is sleepin through town and he knew itPicked me outta the crowd but couldn't do itJust lost it, and as he's walkin awayI realize life is short so I'm markin the dayNow it's full speed ahead, I'll rest when I'm deadAnd I could give a Fuck what the next man saidI live how I wanna liveBuy what I wanna buyDo what I wanna doTry What I wanna tryFear nothin, take chancesNot afraid to fail, always makin advancesSo when I ride on the Grim Reaper HighwayNo regrets bitch, I did it my wayYeah (yeah, yeah, yeah)What Would You Do If It All Ended Tomorrow?Time Runnin Out, Ain't No More You Can BorrowSo Many Paths, which one you gonna follow?What Would You Do If It All Ended Tomorrow?What Would You Do If It All Ended Tomorrow?Time Runnin Out, Ain't No More You Can BorrowSo Many Paths, which one you gonna follow?What Would You Do, What Would You Do? Related: john cena tha trademarc if it all ended tomorrow with lyrics 2005 you cant see me hip-hop | |
|
|
| dbdvrf #14 Debian Developer's ReferenceTue, 02 Dec 2008 00:47:40 -0800 by h4ck3rm1k3http://packages.debi an.org/sid/developer s-reference - - Bcc: pts-news@qa.debian.o rg Subject: Galeon 2.0 backported for woody X-PTS-Package: galeon Hello gnomers! I'm glad to announce that galeon has been backported for woody. You'll find everything here: ... Think twice before adding a news item to the PTS because you won't be able to remove it later and you won't be able to edit it either. The only thing that you can do is send a second news item that will deprecate the information contained in the previous one. 4.11. Developer's packages overview A QA (quality assurance) web portal is available at http:// qa.debian.org/develo per.php which displays a table listing all the packages of a single developer (including those where theparty is listed as a co-maintainer). The table gives a good summary about the developer's packages: number of bugs by severity, list of available versions in each distribution, testing status and much more including links to any other useful information. It is a good idea to look up your own data regularly so that you don't forget any open bugs, and so that you don't forget which packages are your responsibility. 4.12. Debian's GForge installation: Alioth Alioth is a Debian service based on a slightly modified version of the GForge software (which evolved from SourceForge). This software offers developers access to easy-to-use tools such as bug trackers, patch manager, project/task managers, file hosting services, mailing lists, CVS repositories etc. All these tools are managed via a web interface. It is intended to provide facilities to free software projects backed or led by Debian, facilitate contributions from external developers to projects started by Debian, and help projects whose goals are the promotion of Debian or its derivatives. It's heavily used by many Debian teams and provides hosting for all sorts of VCS repositories. All Debian developers automatically have an account on Alioth. They can activate it by using the recover password facility. External developers can request guest accounts on Alioth. For more information please visit the following links: * http://wiki.debian.o rg/Alioth * http://wiki.debian.o rg/Alioth/FAQ * http://wiki.debian.o rg/ Alioth/PackagingProj ect * http://alioth.debian .org/ 4.13. Goodies for Developers 4.13.1. LWN Subscriptions Since October of 2002, HP has sponsored a subscription to LWN for all interested Debian developers. Details on how to get access to this benefit are in http://lists.debian. org/ debian-devel-announc e/ 2002/10/msg00018.htm l. Chapter 5. Managing Packages This chapter contains information related to creating, uploading, maintaining, and porting packages. 5.1. New packages If you want to create a new package for the Debian distribution, you should first check the Work-Needing and Prospective Packages (WNPP) list. Checking the WNPP list ensures that no one is already working on packaging that software, and that effort isnot duplicated. Read the WNPP web pages for more information. Assuming no one else is already working on your prospective package, you must then submit a bug report (Section 7.1, Bug reporting ) against the pseudo-package wnpp describing your plan to create a new package, including, but not limiting yourself to, a description of the package, the license of the prospective package, and the current URL where it can be downloaded from. You should set the subject of the bug to ITP: foo -- short description, substituting the name of the new package for foo. The severity of the bug report must be set to wishlist. Please send a copy to [debian-devel@ lists.debian.org] by using the X-Debbugs-CC header (don't use CC:, because that way the message's subject won't indicate the bug number). If you are packaging so many new packages (]10) that notifying the mailing list in seperate messages is too disruptive, do send a summary after filing the bugs to the debian-devel list instead. This will inform the other developers about upcoming packages and will allow a review of your description and package name. Please include a Closes: bug#nnnnn entry in the changelog of the new package in order for the bug report to be automatically closed once the new package is installed in the archive (see Section 5.8.4, When bugs are closed by new uploads ). When closing security bugs include CVE numbers as well as the Closes: #nnnnn. This is useful for the security team to track vulnerabilities. If an upload is made to fix the bug before the advisory ID is known, it is encouraged to modify the historical changelog entry with the next upload. Even in this case, please include all available pointers to background information in the original changelog entry. There are a number of reasons why we ask maintainers to announce their intentions: * It helps the (potentially new) maintainer to tap into the experience of people Related: debian developers reference | |
|
|
| Burn - Jessica MauboyTue, 02 Dec 2008 00:47:28 -0800 by JoolieCBlover(Verse1)Did my make-up and my hair the way you like (like) like (like)Still you seem to find something bout' me that isn't right (right) right (right)You called me sexy then we burst again, I'm sorry this is the way I am, I'm crazy just for giving you a chance chance, This will never happen again, (Chorus)Look what you did to me, give me some remedy, I need a doctor cause this is starting to burn, Try to fix it now; the grit is to the ground, This love is over so baby just let it burn, (Verse2)When we're at the club gonna shake it the way that turns you on (on)(You couldn't take your eyes off me), you know that I'm hotBut you wanna make me feel like I did something wrong, wrongYou're twisted, if you think that you could control me, Your actions are about to leave you sad and lonely, You're crazy, so let me put this to an end end, Don't ever want to see you again, (Chorus)(Verse3)I'm on fire, I'm on fire, No way to cool me down, boy you're burning me up, I'm on fire, I'm on fire, No way to cool me down, boy you're burning me up, ohh ohh ohh ohh(Chorus x2)Oh ohh ohh burn burn ohh ohh burn burn Related: burn jessica mauboy | |
|
|
| effexor migraineTue, 02 Dec 2008 00:47:14 -0800 by 275d6e65fcelexa and binging celexa versus effexor side effects effexor rx75 buy effexor effexor welbutrin side effects combination welbutrin and effexor effexor does it really work will effexor help with back pain effexor maximum dose effexor withdrawel problems alcohol and zomig and effexor Related: health | |
|
|
| | |
|
|
| | |
|
|
| | |
|
| |
