On Tue, Jan 4, 2011 at 06:11, Goswin von Brederlow 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 both! :)
Cheers,
Yaroslav Halchenko writes:
> On Sun, 02 Jan 2011, Sandro Tosi wrote:
>> Hi Yaroslav,
>> On Thu, Dec 23, 2010 at 00:45, Yaroslav Halchenko
>> wrote:
>> > I was looking into creation of custom /etc/dpkg/origins/ for our
>> > neurodebian
>> > (http://neuro.debian.net) repository. Unfortunately,
On Sun, 02 Jan 2011, Sandro Tosi wrote:
> Hi Yaroslav,
> On Thu, Dec 23, 2010 at 00:45, Yaroslav Halchenko
> 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 abo
Hi Yaroslav,
On Thu, Dec 23, 2010 at 00:45, Yaroslav Halchenko 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
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 emp
5 matches
Mail list logo
