Yaroslav Halchenko <y...@debian.org> writes:
> On Sun, 02 Jan 2011, Sandro Tosi wrote:
>> Hi Yaroslav,
>> On Thu, Dec 23, 2010 at 00:45, Yaroslav Halchenko <deb...@onerussian.com>
>> wrote:
>> > I was looking into creation of custom /etc/dpkg/origins/ for our
>> > neurodebian
>> > (http://neuro.debian.net) repository. Unfortunately, debianbts.py code
>> > cares
>> > only about vendor and bugs fields, and sets others (e.g. otherpkgs,
>> > mirrors,
>> > etc) to empty, and there seems to be no ability to customi9ze them anyhow,
>> > besides submitting a patch against debianbts.py to add full definition to
>> > be
>> > added to the original 'SYSTEMS', which seems to demolish the point of
>> > having
>> > /etc/dpkg/origins/
>> Do you know where we can read the full specification of
>> /etc/dpkg/origins/<file> contents and meaning?
>
> not exactly and I do not think there is much more than Vendor*, Bugs*.
> dpkg-vendor seems to be another tool using it and since it was said to
> reuse existing structure
> http://lists.debian.org/debian-devel/2008/09/msg00193.html
> may be Goswin could help us out -- is there a full specification for the
> syntax of /etc/dpkg/origins?
Sorry, no idea. I guess the best source of information about what was
actually implemented out of the idea would be the dpkg-vendor source
itself.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
