On 2014-11-12 02:14, Don Armstrong wrote:
On Wed, 12 Nov 2014, Christian Kastner wrote:
Going even further, what would you see as possible solutions for
augmenting bug reports tagged 'entry-point' with the information I
mention in first post, ie:
On 2014-11-09 20:20, Christian Kastner wrote:
On Wed, Nov 12, 2014 at 9:50 AM, Christian Kastner deb...@kvr.at wrote:
I'd argue it's good enough for the task itself, but searching for areas
to contribute to could still be improved significantly.
I agree.
For example,
given the following list of motivations a new contributor might have
On Tue, 11 Nov 2014, Don Armstrong wrote:
The existing help tag is really for bugs for which the maintainer needs
or wants help; these are basically a superset of entry-point, and bugs
which are more difficult than it would be reasonable for a new
contributor to help.
I suppose it would be
Your message dated Wed, 12 Nov 2014 16:24:42 +
with message-id e1xoaio-0004eb...@quantz.debian.org
and subject line closing RFS: python-riemann-client/5.1.1-1 [ITP#764739]
has caused the Debian Bug report #765958,
regarding RFS: python-riemann-client/5.1.1-1 [ITP#764739]
to be marked as done.
Le mardi 11 novembre 2014 à 03:54:50, Don Armstrong a écrit :
On Wed, 12 Nov 2014, Stéphane Aulery wrote:
Le mardi 11 novembre 2014 à 03:07:31, Don Armstrong a écrit :
The existing help tag is really for bugs for which the maintainer needs
or wants help; these are basically a superset
I have a package which is split into two sources (a server and gui). The
server version should match the gui version (upstream version) at all times.
Because of this when I'm creating the meta-package that will depend on
both the gui and server, should be versioned to to be the same upstream
Hi Daniel,
On 12.11.2014 22:30, Daniel Lintott wrote:
I have a package which is split into two sources (a server and gui). The
server version should match the gui version (upstream version) at all times.
Because of this when I'm creating the meta-package that will depend on
both the gui and
Hi Daniel,
Could you try ${binary:Version} instead?
Cheers,
Roger
On Wed, Nov 12, 2014 at 9:30 PM, Daniel Lintott dan...@serverb.co.uk wrote:
I have a package which is split into two sources (a server and gui). The
server version should match the gui version (upstream version) at all times.
On Wed, 12 Nov 2014, Roger Light wrote:
Could you try ${binary:Version} instead?
(= ${binary:Version}) can break binNMUs. Be careful.
--
One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows
On Wed, 12 Nov 2014, Stéphane Aulery wrote:
Le mardi 11 novembre 2014 à 03:54:50, Don Armstrong a écrit :
On Wed, 12 Nov 2014, Stéphane Aulery wrote:
Le mardi 11 novembre 2014 à 03:07:31, Don Armstrong a écrit :
The existing help tag is really for bugs for which the maintainer needs
Hi,
I try to backport bilibop_0.4.22 source package (native). If only changes
from 0.4.22 to 0.4.22~bpo70+1 are copied in to the changes file, lintian
complains with the 'backports-changes-missing' error tag [1]. If I add
-v0.4.21 dpkg-genchanges, the resulting changes file says:
Priority:
Oops,
not Priority: but Urgency:
quidame quid...@safe-mail.net wrote:
Hi,
I try to backport bilibop_0.4.22 source package (native). If only changes
from 0.4.22 to 0.4.22~bpo70+1 are copied in to the changes file, lintian
complains with the 'backports-changes-missing' error tag [1]. If I
Raphael Hertzog hert...@debian.org writes:
In fact, I believe they should be mostly disjoint. As a maintainer, I
welcome help on all bugs.
When I tag a bug help it's because I believe that I don't have the
skills to fix it by myself and that external help is really needed to
make some
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package lightmdeditor
* Package name : lightmdeditor
Version : 1.0-2
Upstream Author: Bhavyanshu Parasher a...@bhavyanshu.me
* URL :
14 matches
Mail list logo
