#607850 reportbug: enable full specification (e.g. otherpkgs) of additional origins under /etc/dpkg/origins/

Package:
reportbug
Source:
reportbug
Submitter:
Yaroslav Halchenko
Date:
2011-11-08 07:15:07 UTC
Severity:
wishlist
#607850#5
Date:
2010-12-22 23:45:27 UTC
From:
To:
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/

Another side of the coin (could be a separate bug report but since there is
bulk of them already and it is related posting here):  with a custom origin
available under /etc/dpkg/origins/, and mailto: target with a fixed email
address (without %s, but I am not saying that I am using debbugs -- just
mailto), reportbug fails due to inability to inject n or 99999 into
informative message at the end of the dialog ;):

Traceback (most recent call last):
  File "/tmp/reportbug/bin/reportbug", line 2098, in <module>
    main()
  File "/tmp/reportbug/bin/reportbug", line 1045, in main
    return iface.user_interface()
  File "/tmp/reportbug/bin/reportbug", line 2090, in user_interface
    self.options.draftpath)
  File "/tmp/reportbug/reportbug/submit.py", line 489, in send_report
    (sysinfo['email'] % 'n'), (sysinfo['email'] % '999999'))
TypeError: not all arguments converted during string formatting

so for some reason rtype is taken to be debbugs:

        if rtype == 'mailto':
            rtype = 'debbugs'
            dontquery = True

and dontquery is not participating in definition of send_report, thus shit gets
loose -- send_report considers submission as for debbugs so expects '%s' being
there.  Quick fix (attached) is to verify first that '%s' is actually in the
"email".
#607850#10
Date:
2011-01-02 13:39:34 UTC
From:
To:
Hi Yaroslav,

Do you know where we can read the full specification of
/etc/dpkg/origins/<file> contents and meaning?

Cheers,
#607850#15
Date:
2011-01-02 14:24:47 UTC
From:
To:
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?
#607850#20
Date:
2011-01-04 05:11:35 UTC
From:
To:
Yaroslav Halchenko <yoh@debian.org> writes:

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
#607850#25
Date:
2011-01-04 12:01:04 UTC
From:
To:
I've reported #608884 to ask for a proper documentation - thanks to both! :)

Cheers,
#607850#30
Date:
2011-11-08 07:11:14 UTC
From:
To:
Hi Yaroslav,

What fields do you need reportbug to extract from the files in
/etc/dpkg/origins?  The dpkg source code doesn't contain information
about any fields other than Vendor and Parent.