On Tue, Jan 4, 2011 at 06:11, Goswin von Brederlow goswin-...@web.de wrote:
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.
I've reported #608884 to ask for a proper documentation - thanks to
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)
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
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
Package: reportbug
Version: 4.12.6
Severity: wishlist
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
5 matches
Mail list logo
