Hello,
Thank you for getting this project onto alioth.[1] Here's my review of
the version I found there:
1. Have you considered reworking the long description as I suggested
previously?
2. Are you sure you aren't willing to rework the organisation of the
project to avoid the override in d/
Hi, still missing a build-dependency on libncurses5-dev
the package just FTBFS
http://debomatic-amd64.debian.net/distribution#unstable/dvtm/0.15-1/buildlog
If it is ok for you I can add it, sign and upload.
g.
Il Mercoledì 25 Maggio 2016 21:03, Dmitry Bogatov ha scritto:
> Hi Dmitry, due t
> Hi, still missing a build-dependency on libncurses5-dev
>
> the package just FTBFS
> http://debomatic-amd64.debian.net/distribution#unstable/dvtm/0.15-1/buildlog
> If it is ok for you I can add it, sign and upload.
Yes, proceed, please. My bad. Some time ago I installed ghc into blessed image,
Your message dated Thu, 26 May 2016 11:05:26 + (UTC)
with message-id <1371083583.1675898.1464260726125.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#822856: Another try for dvtm?
has caused the Debian Bug report #822856,
regarding RFS: dvtm/0.15-0.1 NMU
to be marked as done.
This mea
Hi Gianfranco,
On Sun, May 22, 2016 at 06:48:36AM +, Gianfranco Costamagna wrote:
> ...
> I would say: remove the add_subdirectory (line 21)
> and then:
> 1) create a "FindF2C.cmake" file and use it as helper
> (that would be the best and upstreamable choice
> you can find some examples in "et
Hi Andreas,
>o what I'd like to know: What's the difference between building the
>code copy of libf2c comming with clapack (which can be proved by
>deactivating use_debian_packaged_f2c.patch) and using libf2c2. (Bonus
I would look at both build logs and gcc versions.
maybe some new gcc compil
Your message dated Thu, 26 May 2016 11:35:41 + (UTC)
with message-id <360037010.1744586.1464262541390.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#811455: RFS: qhttpengine/0.1.0+dfsg1-1 [ITP]
has caused the Debian Bug report #811455,
regarding RFS: qhttpengine/0.1.0+dfsg1-1 [ITP]
to
On 23/05/16 09:18, Gianfranco Costamagna wrote:
Hi Lumin, Ghislain
I think a lot of good progress has been made on the package, bravo
lumin.
An update to this, according to
https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html
Even if I want to add some testsuite for python-c
On Sun, 15 May 2016 15:13:34 + Mattia Rizzolo wrote:
> Hi Robert!
>
> On Thu, Mar 03, 2016 at 03:52:07PM -0500, Robert James Clay wrote:
> >I'm afraid that I got rather heavily tied up in other things and so
> > haven't
> > been able to work on this as much as I'd like... Should I perh
Hello Andres,
> Once I have uploaded libf2c2 version 20130926-1 the build somehow
> stopped working again. I can not even reproduce things with a local
> rebuild.I always get something like:
>
> ...
> Start 76: xeigtstd_lse_in
> 76/76 Test #76: xeigtstd_lse_in ..***Faile
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "maldetect":
* Package name: maldetect
Version : 1.5-1
Upstream Author : Ryan MacDonald
* URL : https://www.rfxn.com/projects/linux-malware-detect/
* License
* Giulio Paci , 2016-05-25, 19:10:
https://anonscm.debian.org/git/collab-maint/openfst.git
[...]
I added some code to restrict the build to mips, mipsel and hurd-i386.
Just like the last time[1], -O0 wasn't enough to get the tests built on
mips:
| libtool: link: g++ -g -O0 -fPIE -fstack-pro
Hi everyone,
Say a package installs only headers, and in one of those, a header of
another -dev package is #included. How to depend on the package?
Cheers,
Nico
Hi,
>Say a package installs only headers, and in one of those, a header of another
>-dev package is #included. How to depend on the package?
I would call it libfoo-dev (arch:all) and depend (runtime) on libbar-dev.
Feel free to steal from websocketpp, a source-only library I maintain.
https:
Hi Nico:
On 26/05/16 19:06, Nico Schlömer wrote:
> Hi everyone,
>
> Say a package installs only headers, and in one of those, a header of
> another -dev package is #included. How to depend on the package?
Have a look to the libmpfrc++-dev package.
Best wishes,
Jerome
>
> Cheers, Nico
--
Je
Hi,
On 05/25/2016 11:23 PM, James Cowgill wrote:
> On Wed, 2016-05-25 at 21:10 +0200, Muri Nicanor wrote:
>> I am looking for a sponsor for my package "usbguard"
>
> This looks like quite an interesting package, so here's a review.
wow, thanks for the detailed review, i really appreciate it, i've
Hi Sean,
>> Now that those -dbg packages have been renamed to -dbgsym, do you
>> think it may be a good idea to generate again those debug packages?
>> I would be really thankful for any advice regarding "good practices"
>> in this sense...
>
> Based on your description, it sounds like the -g pack
On 26/05/2016 18:48, Jakub Wilk wrote:
> * Giulio Paci , 2016-05-25, 19:10:
https://anonscm.debian.org/git/collab-maint/openfst.git
> [...]
>> I added some code to restrict the build to mips, mipsel and hurd-i386.
>
> Just like the last time[1], -O0 wasn't enough to get the tests built on mip
On Fri, May 27, 2016 at 4:19 AM, Muri Nicanor wrote:
> thanks again, such thorough reviews really help to get an understanding
> for the packaging process!
Here is another review, I don't intend to sponsor this though.
These things block the upload of this package to Debian:
debian/copyright is
19 matches
Mail list logo
