Hi
>I agree. Something known to be >buggy shouldn't be uploaded >anywhere
>other than maybe experimental. When >I talked about low priority in my
>previous e-mail, I meant to refer to >disruptive and major changes as you
>describe. Thanks!
I would say *everything* is buggy by definition. The dec
Hello,
On Tue, Aug 02, 2016 at 12:19:55AM +0200, Jack Henschel wrote:
> Thanks for the explanation. Unfortunately, neither Section 4.4 [1] nor
> 5.6.17 [2] explain when which urgency should be used (so I just used
> the lowest one). Is there documentation for this elsewhere?
> [1] https://www.de
Hello,
On Tue, Aug 02, 2016 at 12:19:55AM +0200, Jack Henschel wrote:
> On 07/27/2016 03:28 AM, Sean Whitton wrote:
> > I can't sponsor the package, but I hope that the following review is
> > useful to you.
> Thanks for your very in-depth review, it is very helpful!
No problem :)
I noticed that
On 07/27/2016 03:28 AM, Sean Whitton wrote:
> 13. Why a 'low' upload urgency? Counterintuitively, this means that you
> think the package is more likely than usual to be buggy and so it should
> take longer to migrate to testing; it doesn't actually mean "less
> important". Unless you think the u
On 07/27/2016 03:28 AM, Sean Whitton wrote:
> I can't sponsor the package, but I hope that the following review is
> useful to you.
Thanks for your very in-depth review, it is very helpful!
> 1. You should install the examples to /usr/share/doc/yabar/examples, not
> /usr/share/yabar/examples. You
control: owner -1 !
control: tag -1 +moreinfo
Hello,
I can't sponsor the package, but I hope that the following review is
useful to you.
1. You should install the examples to /usr/share/doc/yabar/examples, not
/usr/share/yabar/examples. You can use dh_installexamples to do this.
2. Since you a
Thanks for your interest!
On 07/24/2016 11:13 PM, Sean Whitton wrote:
> I want to review this package more throughly, but I'm a bit confused by
> your git repository. You have a branch `debian/sid` which is tagged
> `0.4.0-3` but your master branch contains some additional commits.
>
> If I wan
Hello Jack,
Thank you for your reply to my earlier question.
I want to review this package more throughly, but I'm a bit confused by
your git repository. You have a branch `debian/sid` which is tagged
`0.4.0-3` but your master branch contains some additional commits.
If I want to review from gi
On 07/22/2016 03:32 AM, Sean Whitton wrote:
> I just took a look at the yabar homepage. It says that "Yabar is still
> in its infancy and far from being mature. Feel free to contribute or
> report bugs!"
Initially, I was also held of by this disclaimer.
However there are two reasons why I decided
control: tag -1 +moreinfo
Dear Jack,
I just took a look at the yabar homepage. It says that "Yabar is still
in its infancy and far from being mature. Feel free to contribute or
report bugs!"
As a general rule, experimental software is not included in Debian.
However, plenty of upstreams write "
I have updated the package to version 0.4.0-3
https://mentors.debian.net/package/yabar
One may download the latest version here:
https://mentors.debian.net/debian/pool/main/y/yabar/yabar_0.4.0-3.dsc
Changelog since the last version:
* Correctly formatted debian/copyright
* Corrected seve
11 matches
Mail list logo