On Thu, 19 Dec 2013 14:45:37 +0000 Simon McVittie <simon.mcvit...@collabora.co.uk> wrote: > On 01/12/13 02:34, Bernhard R. Link wrote: > > * Simon McVittie <simon.mcvit...@collabora.co.uk> [131126 18:03]: > >> The attached patch is a proof-of-concept implementation > > [...] > > Thanks! I've rebased onto that, and added a regression test (once I > found where testtool lives - please consider including that in reprepro > tarballs, if it isn't likely to be packaged separately). > > > I think if those packages will finally come without a Priority or > > Section in the package, there will be a more complex solution needed, > > as without no Section at all, reprepro will not accept the package > > yet (unless there is one in the override file). > > Fixed, I think: I've forced them to Section: debug, Priority: extra. > > [...]
Hi,
Thanks for working on dbgsym support for reprepro.
In the actual implementation we got live now, there are a couple of
changes though.
* The dbgsym packages use the .deb extension
* The primary indicator of a dbgsym file is the header
"Auto-Built-Package", which is set to (exactly) "debug-symbols"
* Further validation that can/should be done:
- The package name should end with "-dbgsym"
- The package should be in section "debug" (possibly in a *non*
main component)
* If it sees a package "foo-dbgsym" with the header, then it should
also assert that a package called "foo" is uploaded. The latter
should be listed in the control file.
In DAK / the Debian infrastructure, the dbgsym packages are placed in a
separate component called "<suite>-debug". The current mirror is
available at [1].
Thanks,
~Niels
[1] http://debug.mirrors.debian.org/
signature.asc
Description: OpenPGP digital signature
