[issue1054967] bdist_deb - Debian packager
Changes by Éric Araujo mer...@netwok.org: -- resolution: - rejected stage: - committed/rejected versions: +3rd party -Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Éric Araujo mer...@netwok.org added the comment: We forgot to reopen the bug. -- status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Tarek Ziadé ziade.ta...@gmail.com added the comment: Please don't. I've closed this bug because the bdist_deb command is currently managed by the stdeb project and it's fine like htis. Distutils2 will not have specialized linux bdist_* command like this one, because it is best to keep it in a separate project that can evolve as its own pace, in accordance with debian/ubuntu cycles. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Andrew Straw ast...@users.sourceforge.net added the comment: I have moved the recent discussion on stdeb to a thread on the distutils-sig. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Changes by Piotr Ożarowski pi...@debian.org: -- nosy: +piotr ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Andrew Straw ast...@users.sourceforge.net added the comment: Barry, stdeb does much of what you're describing. (Try the python setup.py sdist_dsc command.) I'm not particularly pleased with the stdeb codebase as it stands, but it does work reasonably well, and I'd like to see progress in this domain, but I'm afraid I don't understand the difference between what it offers and what you're proposing. I guess maybe you're not aware of the sdist_dsc distutils command it offers? -Andrew -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: Hi Andrew, Yes, I've played with sdist_dsc, and it's nice in that it takes a non-Debianized source tree and turns it into a source package that can be uploaded. What I'm looking for is something that can take a non-Debianized source tree and turn it into a native package, essentially by pre-filling a debian/ directory like dh_make does, but including additional metadata available in the setup.py. I've started taking a crack at this: https://launchpad.net/setupdebian -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Andrew Straw ast...@users.sourceforge.net added the comment: Barry, I'm sorry I still don't understand what you think is the essential distinction. A debian source package (.dsc, .orig.tar.gz, and .diff.gz files) is simply made from a (patched) source directory, including the debian/ directory, and an upstream tarball. To build this sdist_dsc must of course make the debian/ directory. Thus, it takes a non-Debianized source tree and turn it into a native [Debian source] package, essentially by pre-filling a debian/ directory like dh_make does, but including additional metadata available in the setup.py. Then, once it done this, it calls dpkg-buildpackage -S to turn this filesystem structure into the actual source package. If your final goal is simply the filesystem structure rather than the Debian source package (.dsc, .orig.tar.gz and .diff.gz), then it seems like it would be easier to refactor stdeb to stop before calling dpkg-buildpackage rather than writing a whole new alternate way of generating the debian/ directory based on t he contents of setup.py. So I'm afraid I still don't understand what you want setupdebian to do that stdeb does not. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: Hi Andrew, I want debian/ to be created in . (aka, cwd, the directory containing setup.py), not in ./deb_dist/package-version -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Andrew Straw ast...@users.sourceforge.net added the comment: I see. So is copying the debian/ directory into its desired location a possibility for you, either manually or via a new distutils commands that shares 99% of its code with sdist_dsc? It doesn't seem like enough of a difference to start a new project. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: Manual moving/copying is what I want to avoid. I'd be totally happy with not reinventing the wheel if you think this would be easy to add to stdeb! Specifically: just create debian/ in place and do not build package. I have a few other minor suggestions, though if you think this isn't the best place to track them, please let me know where to submit them. * Add setup.py entry_points so you don't have to use --command-packages * Package: shouldn't change dots to dashes. E.g. flufl.enum should be called python-flufl.enum * Update to Standards-Version: 3.8.3 I'm happy to test whatever you come up with. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Éric Araujo mer...@netwok.org added the comment: tree and turns it into a source package that can be uploaded. What I'm looking for is something that can take a non-Debianized source tree and turn it into a native package, essentially by pre-filling a debian/ directory like dh_make does, but including additional metadata available in the setup.py. I've started taking a crack at this: Barry, what do you mean with “native package”? In Debian parlance, a native package is a piece of software that isn’t released outside of Debian and thus has no hyphen in the version number (a hyphen is normally used to separate the upstream version number from a debian-packaging-specific number, e.g. “0.2-1”). I don’t know stdeb (I avoid Setuptools), so I don’t understand the difference you make. On a related note, I’ve seen in your setupdebian code that you unconditionally remove some files under the debian directory, but some of them may be useful, especially for building multiple binary packages (i.e. separate installable .deb packages) out of one source package, e.g. to split architecture-independent modules from arch-dependent C extensions (like mercurial and mercurial-common). More info: - how to build multiple binary packages: http://wiki.debian.org/PkgSplit http://lists.debian.org/debian-python/2009/09/msg00091.html - questioning usefulness of PEP 345 for automation of deb packaging: http://lists.debian.org/debian-python/2009/11/msg00076.html - extensions to Distutils that may meet some debian packaging needs: http://bazaar.launchpad.net/~python-distutils-extra-hackers/python-distutils-extra/debian/files - rough proposal by myself for support in Distutils2: http://wiki.python.org/moin/Distutils/Proposals/SplitAndCompoundDistributions HTH -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: Eric, you're right, native isn't exactly what I was getting at. I want the debian/ directory created right next to the setup.py, as I've described in some follow ups. As far as what you see in setupdebian, this is just preliminary experiments using test-driven development. I had intended to support switches for other types of packaging options, but first things first. Since Andrew is willing, I'd rather work with him to get some of the features I'd like to see rather than continue with a separate package, so if that proves fruitful, I'll abandon setupdebian. BTW, have you seen the python-debian package? It seems to have a lot of useful stuff for manipulating changelogs, control files and such. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Éric Araujo mer...@netwok.org added the comment: Barry, IIUC you want the “debian” command to create a debian source package, which can be converted to debian binary package(s), checked and uploaded with standard tools. Perfect. Andrew, I am uncomfortable with stdeb. (Trying to express respectful constructive critique, not just picking on your project.) The version in Debian testing, 0.5.1-1, still requires setuptools (actually only pkg_resources, which is split into another package in Debian, for space or politic reasons). The py2dsc script seems to be obsoleted by the to-be “debian” command. The pypi-install script seems dangerous to me, because downloading unverified software and putting it into the system seems a rather bad idead (a.k.a. “sudo ./setup.py install considered harmful”). python-debian provides useful support code for generating and reading debian formats. A quick read show the code would benefit from some 2.6 modernizing (i.e. gain in simplicity and readability by using modern idioms and stdlib functions). Would using this package in stdeb / distutils2.command.debian instead of shelling out bring anything? (Sorry about the badly wrapped paragraph I forgot to remove in my previous message. And sorry to write so much words instead of code ;) acute-accent-ly yours -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: Éric, sorry about missing that accent. /me needs a bigger font. :) RE: python-debian modernization. We'd have to check with the authors to see what version of Python they need to remain compatible with. If it's 2.6, then I'm all for modernizing. I'm not a huge fan of shelling out to get the debian directory, but dh_make seems to be what people want to emulate. I was planning on using python-debian to fill out e.g. debian/control with information that dh_make couldn't easily be convinced to create. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: I'm not so sure about sdist_debian for the command I'm thinking about because it doesn't actually build a distribution. It just creates a 'debian' directory so I think I like just 'debian' as the name of the command. But thanks for the feedback; time to write some code! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: astraw: I've been playing with stdeb. I think it's a nice implementation of bdist_deb, but it doesn't seem to include the dh_make/debianize functionality of this patch. Is that the case or have I missed something? -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Éric Araujo mer...@netwok.org added the comment: Hello There has been a number of discussions about bdist_deb, and some code too. I don’t have links handy, unfortunately, but I remember a conclusion that was: Don’t. Debian packages are best made by Debian tools, which go to great lengths to comply with Debian Policy, work together, and are frequently updated. On the Distutils(2) site, the most we can do would be a bdist_dsc command that produces a special file which is used by debianizing tools. A key thing to remember is that .deb is not just a file format, it’s the embodiment of a Policy (the real value of Debian is its policy, not its package manager—a nice technical side effect), and as such, best handled by Debian tools. Disclaimers: I’ve not been following packaging discussions for long, these lines are a summary of other people’s thoughts, I’m not a Debian developer or maintainer. Cheers -- components: +Distutils2 -Distutils nosy: +merwok versions: +Python 2.5, Python 2.6, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: There are really two aspects of this patch. At the moment, I'm less interested in bdist_deb than I am in the 'debianize' (i.e. dh_make) functionality. I think 'python setup.py debianize' (or whatever) would be a nice way to jump start a debian/ directory from the available metadata. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Éric Araujo mer...@netwok.org added the comment: Why not use Debian’s dh_make? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: That's essentially what I want, except I want to feed dh_make some better defaults based on metadata that already lives in setup.py. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Éric Araujo mer...@netwok.org added the comment: Hello Thanks for clarifying your point. Note that I had quickly tested dh_make in a near-empty directory before posting, and the only question I got asked was the type of the package (library, many libraries, program, etc). But I’ve just realized that I have two dh_make-related variables set in my environment, plus maybe config files, so a typical user may have more questions to answer, which is annoying if the setup.cfg¹ already has them. And to be honest, the question about the type of the package is not simple if you’re not fluent with the Policy, so if Distutils2 can answer that thanks to its knowledge, all the better. I therefore agree with you :) One thing I’m attached to: The name of the command should respect existing conventions. Entirely new concepts get dedicated names (e.g. “check” and “test”), but commands fitting in the areas of sdist or bdist should say so in their name. How about sdist_debian? It may be useful to precise something at this point: You may read about both “debian” and “Debian” packages. “debian” or “.deb” or “debs” are binary distributions that use the file formats defined by Debian, whereas “Debian” packages are binary distributions that use these formats, conform to the Debian policy, are tested on lintian.debian.org and piuparts.debian.org, and most importantly, are scrutinized for Debian Free Software Guidelines compliance. That’s why I, for one, never uses third-party deb packages or apt repos: If it’s going to be installed system-wide, I want a verified Debian package. HTH ¹ Not a typo, just an anticipation of PEP 390 ;) Kind regards -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Andrew Straw ast...@users.sourceforge.net added the comment: As of stdeb 0.5.0, the setuptools dependency has been removed. Now stdeb requires only plain distutils. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Tarek Ziadé ziade.ta...@gmail.com added the comment: I am closing this issue, since stdeb implements this command now. Also, I'd love to add it in the distutils documentation, but there's one issue. Andrew, do you think you could have a plain distutils version of this command ? Setuptools changes the Command and the Distribution classes, and affects Distutils global behavior, so we can't document its usage in the Distutils documentation as it is. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Andrew Straw ast...@users.sourceforge.net added the comment: stdeb ( http://github.com/astraw/stdeb ) now includes a bdist_deb distutils command. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Lukas Lueg knabberknusperh...@yahoo.de added the comment: Thanks for your efforts. I don't think you are stepping on anyone's toes when picking up an issue that was unsolved for almost 5 years :-) Please post patches to this bug for review/comments/help/whatever -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Paul Hummer p...@eventuallyanyway.com added the comment: I've been doing a review of this patch for the last few hours. There are a few issues that need to be taken care of in order for it to move forward, and I'm currently working on them, in this order: 1. Update the patch to the most recent svn. The most current patch is almost 5 years old. I've ported it forward. 2. Fix the unittests. The patch is failing its unittests currently, and so I'm fixing the unittests, and will be adding tests where there may not be any coverage. 3. Implement the suggestions made by alberanid and kbk, adding tests where necessary. I've been chatting with jafo, and am willing to commit to maintaining this code for the next few years, and am willing to sign the contributor agreement in order to do so. I don't particularly want to step on anyone's toes, so if someone else is also working on this, I'm happy to hand off what I've already been working on. -- nosy: +rockstar ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Changes by Tony Meyer anadelonb...@users.sourceforge.net: -- nosy: +anadelonbrin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Lukas Lueg knabberknusperh...@yahoo.de added the comment: Count me in -- nosy: +ebfe ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Changes by Akira Kitada akit...@gmail.com: ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
