Hi Laurent, I'm pinging you because I think you missed my review on #786795
Let me know if you intend to address the issue I raised here :)
cheers,
G.
>You are correct, there is no need in "linux-headers-amd64", however there
>is second option just "linux-headers", and I don't understand why it
>doesn't work for you.
it does work for *me*, it doesn't for buildd system.
IIRC they are configured to pick only the first version...
>Anyway I dropp
Another issue you should address:
I duplicate-long-description
libcunit1-dev libcunit1 libcunit1-ncurses-dev libcunit1-ncurses libcunit1-doc
(you might append something like "this is the development package" "this is the
common
documentation" or so)
feel free to steal from python-pyqtgraph or
(please also address issues from other emails)
http://mentors.debian.net/debian/pool/main/c/cunit/cunit_2.1-3-dfsg1.dsc
quoting changelog:
+ * Bump to 2.1-3
+ * Fix versions
I see two patches dropped
and the watch file updated (diff between this version and your previous one,
not complete
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "alien"
* Package name: alien
Version : 8.95
Upstream Author : Joey Hess
* URL : http://joeyh.name/code/alien/
* License : GPL-2+
Section :
On Tue, Sep 08, 2015 at 10:36:00PM -0400, Yaroslav Halchenko wrote:
> 2. or provide two source packages, of which main would build only
> CPU implementation while in non-free would build both/only GPU
> (depending how organized).
Yeah, that's not super great. I might consider a -src
package and
On Wed, 02 Sep 2015, lumin wrote:
> Hi all,
> (CC'ing people interested in package Caffe)
> It takes so long time for Caffe to be packaged for Debian,
> now the package is nearly prepared to be uploaded, and
> there are still some small issues to be addressed.
> http://anonscm.debian.org/cgit/d
On Tue, Sep 08, 2015 at 08:24:19PM +, Gianfranco Costamagna wrote:
> Control: owner -1 !
>
>
> Hi,
>
> quick review:
>
>
> 1) watch file does not work, please use something like this url
>
> https://github.com/ktap/ktap/releases
Fixed.
> 2) control:
> linux-headers-amd64 | linux-header
On Tue, Sep 08, 2015 at 08:48:45PM +, Gianfranco Costamagna wrote:
> Hi,
>
> well something has been buried by my MUA.
>
> There is a new upstream release, can you please update it?
Okay, done.
> BTW there is a problem in versioning:
>
> -2.dfsg is bad, because it seems only Debian revisio
Hi,
well something has been buried by my MUA.
There is a new upstream release, can you please update it?
BTW there is a problem in versioning:
-2.dfsg is bad, because it seems only Debian revision, while
-2 is upstream and dfsg is Debian.
please use two "-" but I'm not sure if it works or not.
Hi again,
>Hm, so if I will replace all targets with dh_*_auto, and will add
>override_* for them when required, this will not work for rules.d since
>it will call the same again and again, no? Or do you suggesting get rid
>off that rules.d stuff?
yes, or merge them in the main rules file :)
Hi,
>Yes, you are right, dh-autoreconf is enough.
so please drop the other one :)
>Hm, according to lintian(1):
> "For binary packages, Lintian looks for overrides in a file named
> usr/share/lintian/overrides/ inside the binary package, where
> is the name of the binary package."
>
Control: owner -1 !
Hi,
quick review:
1) watch file does not work, please use something like this url
https://github.com/ktap/ktap/releases
2) control:
linux-headers-amd64 | linux-headers,
why?
e.g. on i386
The following packages have unmet dependencies:
sbuild-build-depends-ktap-dummy
On Tue, 08 Sep 2015 20:23:55 +0200 Paul Gevers
wrote:
> Hi
Hi,
> On 07-09-15 01:16, Vincent Blut wrote:
> > Sorry for the delay!
>
> np.
>
> > Pushed on alioth, hopefully everything is ok now. Subsequent
changes
> > start at
> > commit 7355723cab155607765d9a631353063c8f6f6ae7.
>
> Build, sig
Your message dated Tue, 8 Sep 2015 18:55:49 + (UTC)
with message-id <911227422.4928125.1441738549348.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#798215: RFS: node-typedarray/0.0.6-1 [ITP]
has caused the Debian Bug report #798215,
regarding RFS: node-typedarray/0.0.6-1 [ITP]
to be ma
Your message dated Tue, 8 Sep 2015 20:29:49 +0200
with message-id
and subject line Re: Bug#786558: RFS: sequitur-g2p/0.0.r1668-2 -- Grapheme to
Phoneme conversion tool
has caused the Debian Bug report #786558,
regarding RFS: sequitur-g2p/0.0.r1668-2 -- Grapheme to Phoneme conversion tool
to be m
Your message dated Tue, 08 Sep 2015 20:23:55 +0200
with message-id <55ef27bb.2030...@debian.org>
and subject line Re: Bug#793876: RFS: chrony/1.31.1-1
has caused the Debian Bug report #793876,
regarding RFS: chrony/1.31.1-1
to be marked as done.
This means that you claim that the problem has been
Hi,
Henrique de Moraes Holschuh wrote:
> Any name we return can colide, unless we return something that is impossible
> for isofs + extensions to return in the first place.
Rock Ridge permits any name of any length. Theoretically a NM
could contain NUL or '/' characters. (One should catch them.)
18 matches
Mail list logo
