On Tue, Oct 26, 2010 at 3:10 PM, Bernd Zeimetz <bzed@debian.org> wrote: >> Even though the policy doesn't explain what Build-Depends-Indep is, it >> says that Build-Depends-Indep should be present for these Makefile >> targets: >> build, build-indep, binary, and binary-indep >> >> But there are no such targets in trac-bitten debian/rules file, so I >> assume that some kind of autotools is used to execute/supply these >> targets when debian/rules is executed. As a Windows Python user, who >> just want to see new Bitten package in Debian to upload the package to >> production server, I can't really go into the gory details of Debian >> toolchains. It already takes more time than I could allow. > > I don't mind that beginners in packaging have write access to our repositories, > assuming that they're willing to learn the necessary details during their work > within the team. But as you're neither willing to learn how packaging software > for Debian works, nor you seem to know the necessary basics like makefiles, I've > removed your write access to the Python teams' repositories. You assumption is wrong, and I'd like to think that the right signal for this outcome here is "Windows" keyword. =) Because: 1. I am willing to learn how packaging work, but nobody is able to explain the details. If you feel you're better than everybody else in packaging - then explain what is Build-Depends-Indep, how it works, what it was designed for and what is the real usage, and in which parts its usage conflicts with the policy? 2. I know basics about makefiles, but maybe not the details of your patching systems and autotools. There is a big difference in a level of incompetence. 3. I don't think that http://wiki.debian.org/Teams/PythonAppsPackagingTeam/HowToPBuilder could be written by someone who doesn't know anything about packaging. > Of course you are still welcome to update packages, please send the according > patches to me and I'll apply them. Please apply this. -- anatoly t.
Attachment:
bitten.diff
Description: Binary data