Re: Trying to understand patch management - in combination with version control
On 2008-09-02, Andreas Schildbach [EMAIL PROTECTED] wrote: Now, when I (or a co-maintainer) check out the project from SVN, I get (as expected) a nearly empty project directory, containing just the debian directory. But, how am I supposed to actually create the patches that go into debian/patches? My current understanding is: I modify/delete/create a set of files and use something like interdiff/debdiff to extract the changeset. But in the case of mergeWithUpstream-mode there is no file to modify... Don't tell me I have to write patches by hand (-: Also, can you point me to a document that explains workflow with a patch management system in general, preferably in combination with a version control system. I'm using svn - and part of the kde/qt team. Only debian-dir is kept in svn. Packages uses quilt Upstream releases tar.bz2 files. Goal: refresh patches and add a note to the upstream README file My basic workflow is as follows: bunzip2 kdeutils-4.1.1.tar.bz2 gzip --best kdeutils-4.1.1.tar mv kdeutils-4.1.1.tar.gz kdeutils_4.1.1.orig.tar.gz tar xzf kdeutils_4.1.1.orig.tar.gz cd kdeutils-4.1.1 cp -a ~/svn/pkg-kde/branches/kde4/packages/kdeutils/debian . #do changelog #refresh patches while quilt push ; do quilt refresh ; done quilt new 05_README_changes.diff quilt edit README quilt refresh dpkg-buildpackage #profit and that's (if existing patches works as is) the full list of steps to update to new upstream and do a debian specific change. /Sune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help writing watch file for unusual, troublesome case.
* Brandon [EMAIL PROTECTED] [080902 22:31]: Also, xevil is a dead project. The latest release was years ago, and Satan doesn't respond to email. Would you guys recommend not having a watch file? I think especially with dead upstream a watch file is usefull. If upstream is active and knows you exists or you are on the webpage from time to time, then you will notice yourself. If upstream just wakes up, puts a new version and vanishes again then a watch file is almost the only chance you have to detect it... Also email addresses often change, sometimes it helps to look for other projects of the same person to see if there are other addresses now (sometimes there is even a mailinglist there also dedicated to the old project but not listed on the old project page directly). Hochachtungsvoll, Bernhard R. Link -- Never contain programs so few bugs, as when no debugging tools are available! Niklaus Wirth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: sqlmap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my package sqlmap. * Package name: sqlmap Version : 0.6-1 Upstream Author : Bernardo Damele A. G. and Daniele Bellucci * URL : http://sqlmap.sourceforge.net * License : GPLv2 Section : net It builds these binary packages: sqlmap - an automatic SQL injection tool entirely developed in Python The package appears to be lintian clean. The package can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/s/sqlmap - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/s/sqlmap/sqlmap_0.6-1.dsc I would be glad if someone uploaded this package for me. Kind regards, - -- Bernardo Damele A. G. E-mail / Jabber: bernardo.damele (at) gmail.com Mobile number: +39-3493821385 PGP Key ID: 0x05F5A30F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIvoGzdntYwQX1ow8RAigmAKCuqq6OG9o4jzoO5bTWofSclpB1fACgpDcV qcYuLEInSjPz6eV/H7+oK2c= =4DWO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: sqlmap
Hello Bernardo, Version : 0.6-1 is it a new package (not already in Debian)? If so, is there an ITP for this package? If no, please file one (or rename an RFP if there exists one); if yes, close it with this upload. sqlmap - an automatic SQL injection tool entirely developed in Python Don't you think an and entirely developed in Python don't add anything to the short description of the package? maybe rephrase a little. - - Source repository: deb-src http://mentors.debian.net/debian unstable diff.gz is empty: sqlmap_0.6-1.diff.gz03-Sep-2008 14:15 20 what went wrong? Kidnly, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: sqlmap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Sandro, Sandro Tosi wrote: ... is it a new package (not already in Debian)? If so, is there an ITP for this package? If no, please file one (or rename an RFP if there exists one); if yes, close it with this upload. There was no ITP for sqlmap package. I filled in one on bugs.debian.org[1]. Is it right? Thanks for notifying. sqlmap - an automatic SQL injection tool entirely developed in Python Don't you think an and entirely developed in Python don't add anything to the short description of the package? maybe rephrase a little. Fixed and reuploaded on mentors.debian.net[2]. diff.gz is empty: sqlmap_0.6-1.diff.gz03-Sep-2008 14:15 20 what went wrong? Because it's a new package. Should diff.gz have something into it? [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497667 [2] http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=sqlmap Regards, - -- Bernardo Damele A. G. E-mail / Jabber: bernardo.damele (at) gmail.com Mobile number: +39-3493821385 PGP Key ID: 0x05F5A30F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIvp+XdntYwQX1ow8RAmixAJoDOxlzcLoRAk/Ep6NkjhqkvQhURwCgrHWZ btWmn9raKAP1z7/Tr6OLoec= =dIeX -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: sqlmap
There was no ITP for sqlmap package. I filled in one on bugs.debian.org[1]. Is it right? Thanks for notifying. Next time, please file it before start packaging it (so we can avoid duplicate work on the same tool, etc etc). diff.gz is empty: sqlmap_0.6-1.diff.gz03-Sep-2008 14:15 20 what went wrong? Because it's a new package. Should diff.gz have something into it? Yes, it has to, but I can see your problem: you are both packager and upstream author. My suggestion is: keep upstream work separate from debian packaging work. diff.gz is the difference applied to upstream source code by the packager (so it usually contains debian/ directory only). You have merged both in orig tarball. Please split that and only release upstream tarball without debian/ dir, and apply it only in a second moment. I just give a fast look, and I noticed: * debian/changelog has to contain changes related to debian package *only*, so jsut one entry with Initial package; Closes #ITP bugnumber is what we expect there * debian/copyright has Daniele's email wrongly typed; if the source is GPLv2, than link to /usr/share/common-licenses/GPL-2 (GPL is a link to the lastest GPL version available, so now is GPL-3) * it would have been better if you leave debian/rules as dh_make template proposed to you * moreover, dpatch integration is done wrong: check http://wiki.debian.org/DebianPackagingHandbook/PatchSystems * if you're upstream, why you need a patch system? can't you simply release a new version? :) * don't ship pdf (in docs) if they are not generated a build time * check if some Build-Depends can go to Build-Depends-Indep * adding a watch file might be intersting * I still see Description: an automatic SQL injection tool entirely developed in Python and I know why: you uploaded -2 revsion, that DON'T upload the orig.tar.gz file (see why debianization has to be separated?) That's enough for a 5 minutes check :) Cheers, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: bzr-diffstat
Dear mentors, I am looking for a sponsor for my package bzr-diffstat. * Package name: bzr-diffstat Version : 0.2.0+bzr17-1 Upstream Author : Michael Ellerman, Russ Brown * URL : https://www.launchpad.net/bzr-diffstat * License : GPL-2 + Section : devel It builds these binary packages: bzr-diffstat - Plugin to generate diffstats for bzr revisions The package appears to be lintian clean. The upload would fix these bugs: 497150 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/b/bzr-diffstat - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/b/bzr-diffstat/bzr-diffstat_0.2.0+bzr17-1.dsc I would be glad if someone uploaded this package for me. Kind regards David Futcher -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Need a DD with some experiencie with 3.0 (quilt) package format
Hello all: I need somebody with experience in the packaging format 3.0 (quilt), the one that allows the package to have more than one orig.tar.gz tarball at the same time. Many thanks er Envite signature.asc Description: This is a digitally signed message part.
Re: Trying to understand patch management - in combination with version control
On Wednesday 03 September 2008 05:04:12 Ben Finney wrote: --cut-- I'm experimenting with Bazaar's loom feature, which allows a single branch to contain multiple threads of development. A loom allows any of the threads to be advanced, turned into separate patches as needed, while still having a coherent end result representing the aggregate of all of them URL:http://bazaar-vcs.org/Documentation/LoomAsSmarterQuilt. Others might discuss the rebase feature of Git, but that method loses too much intermediate state and prevents sharing the branch with others. I prefer the loom approach in Bazaar. Yeah, rebase being very cool is sometimes abnormally used, so I'm not sure you have choosen the right git counterpart to the bzr's loom feature. It should be compared with topgit instead, which self-maintained source package is a real demonstration (see README.source, README.gz is also very helpful ;-) of how topgit can be used for maintaining your patch queue. -- pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Trying to understand patch management - in combination with version control
also sprach George Danchev [EMAIL PROTECTED] [2008.09.03.1926 +0100]: Yeah, rebase being very cool is sometimes abnormally used, so I'm not sure you have choosen the right git counterpart to the bzr's loom feature. It should be compared with topgit instead, which self-maintained source package is a real demonstration (see README.source, README.gz is also very helpful ;-) of how topgit can be used for maintaining your patch queue. The vcs-pkg-discuss mailing list (http://vcs-pkg.org) is the place for further technical discussions on this, if you are interested. Note that topgit's self-maintained source package is work-in-progress and just an idea right now. The whole workflow needs polishing (and people trying and improving it). You might like to watch http://meetings-archive.debian.net/pub/debian-meetings/2008/debconf8/high/547_Packaging_with_version_control_systems.ogg slides: http://people.debian.org/~madduck/talks/vcs-pkg_debconf8_2008.08.11/slides.s5.html for more information. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems all software projects are done by iterative prototyping. some companies call their prototypes releases, that's all. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
RFS: pidgin-facebookchat
Dear mentors, I am looking for a sponsor for my package pidgin-facebookchat. * Package name: pidgin-facebookchat Version : 1.35-1 Upstream Author : Eion Robb [EMAIL PROTECTED] * URL : http://code.google.com/p/pidgin-facebookchat/ * License : GPL version 3 or later. Section : net It builds these binary packages: pidgin-facebookchat - Facebook Chat plugin for Pidgin The package appears to be lintian clean in both source and binary. The upload would fix these bugs: 497698 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/pidgin-facebookchat - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/pidgin-facebookchat/pidgin-facebookchat_1.35-1.dsc I would be glad if someone uploaded this package for me. Kind regards Jonathan signature.asc Description: Digital signature
Re: Need a DD with some experiencie with 3.0 (quilt) package format
Noel David Torres Taño [EMAIL PROTECTED] writes: I need somebody with experience in the packaging format 3.0 (quilt), the one that allows the package to have more than one orig.tar.gz tarball at the same time. You shouldn't expect to get private attention from a single person. Instead, this forum operates on the principle of discussion questions in public so that many can help, and many can benefit from the discussion. Go ahead and ask your Debian packaging related questions here on the mailing list. -- \ “Pinky, are you pondering what I'm pondering?” “Uh, I think so, | `\ Brain, but we'll never get a monkey to use dental floss.” | _o__) —_Pinky and The Brain_ | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
