Re: RFS: disco
-----BEGIN PGP SIGNED MESSAGE-----
On 2010-12-08 02:25, Janos Guljas wrote:
> Dear mentors,
> I am looking for a sponsor for my package "disco".
> Kind regards
> Janos Guljas
Sorry for not getting back to you earlier.
> Why do disco-master Pre-Depends on python-disco? I see nothing in the
> preinst script that suggests that python-disco must be present before
> disco-master is unpacked.
Python module "disco" is needed for starting python-master.
Python-setuptools on disco python module must be triggered before
running /etc/init.d/disco-master start, which is done after installing
python-disco. Trying to start disco-master before configuring
python-disco package will fail.
You only need a Pre-Depends if you are starting disco-master in the
preinst script (which does not make sense, since the package has yet to
be unpacked at that point).
If a package A depends on B, then the postinst script of B will always
be run before the postinst of A.
If you can avoid Pre-Depending then please do, since the strength of the
dependency makes some difficult and you need approval to do it.
> It fails to build from source if Build-Depends-Indep are not satisfied
> when dpkg-buildpackage is invoked with -B:
> sphinx-build -b html -d .build/doctrees . .build/html
> make: sphinx-build: Command not found
> This is how auto-builders will build your package. As I recall the
> debian-policy is disagreeing with reality here. I believe there is an
> attempt to make these two agree, but for now your package must be able
> to build without Build-Depends-Indep when dpkg-buildpackage is passed -B.
Are you suggesting to move references from:
Build-Depends-Indep: python-sphinx, libjs-jquery
With that set, cowbuilder --build disco_0.3.1-1.dsc --buildresult .
- --binary-arch is building packages fine. But I do not understand the
reason for -B option in autobuild scripts. Do you have some references
that can clarify reason for it. Until now, I tested packages without
- --binary-arch build. I see now that this is a requirement.
Moving those packages (as you now have done) to Build-Depends is one
You should be able reproduce the original issue by moving them back to
Build-Depends-Indep and running cowbuilder with --debbuildopts "-B".
> Have you contacted (or considered to contact) the python application
> team about team maintaining the package? (See  for more info).
Yes, but I am not sure is this belongs to DMPT or PAPT. There are
modules and application packages...
Have you tried contacting any of the teams? Either team should be able
to help you (at least by telling you, that you should contact the other
team). Again I am not really into Python, so I cannot do much for you here.
Once again, sorry for the late reply. Another time, feel free to ping me
privately if I do not reply to you within 4 days. :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----