On Mon, 25 Jul 2011 20:33:18 +0300
"Eugene V. Lyubimkin" wrote:
> Yes. Different sponsors prefer different ways to deal with pre-release
> changes, I believe there's no single "best way". I want bumped after
> each review (and with a usual changelog between) versions for
> packages I intend to sp
Hi,
On 2011-07-25 12:46, Andrew Gainer wrote:
> "Eugene V. Lyubimkin" wrote:
>
> > [ I prefer to have a bumped package version after an each review ]
> Other mentors have preferred that I use the VCS for keeping track of
> pre-release changes and leave the changelog clean, with only the
> "Init
Thanks for your review!
On Mon, 25 Jul 2011 12:44:49 +0300
"Eugene V. Lyubimkin" wrote:
> [ I prefer to have a bumped package version after an each review ]
Other mentors have preferred that I use the VCS for keeping track of
pre-release changes and leave the changelog clean, with only the "Ini
Hi Andrew,
[ I prefer to have a bumped package version after an each review ]
My review:
---
libbs2b
---
1) there is definitely something wrong with
remove_win32_build_instruction patch, its size is more than 2 MiB and it
includes some autotools stuff;
2) Vcs-* fields point to LAD
Thanks for the review!
On Thu, 21 Jul 2011 20:44:16 +0200
Paul Wise wrote:
> On Thu, Jul 21, 2011 at 8:04 PM, Andrew Gainer wrote:
>
> > The package appears to be *sort of* lintian clean.
>
> When in doubt, run lintian with --info, which gives detailed
> information about the warnings.
Seems
On Thu, Jul 21, 2011 at 8:04 PM, Andrew Gainer wrote:
> The package appears to be *sort of* lintian clean.
When in doubt, run lintian with --info, which gives detailed
information about the warnings.
> * There are several old-fsf-address-in-copyright-file warnings. Is the
> correct procedure on
Dear mentors,
I am looking for a sponsor for my packages "libbs2b" and "bs2b-ladspa".
* Package name: libbs2b
Version : 3.1.0-1
Upstream Author : Boris Mikhaylov
* URL : http://bs2b.sourceforge.net
* License : GPL-2 and others
Section : libs
It buil
7 matches
Mail list logo
