Hi,
> g++ -ggdb -O6 -DNDEBUG -I./protoobj -g -O2 -fstack-protector-strong -Wformat
> -Werror=format-security -o obj-opt-x86_64/test_spectrum_preprocess.o -c
> src/test_spectrum_preprocess.cc
> In file included from src/test_spectrum_preprocess.cc:8:0:
> src/records.h: In destructor
Hi,
I have started packaging Tide (a tandard tool for ass-spectroscopy) at
git://anonscm.debian.org/debian-med/tide.git
Unfortunately these days gcc is more picky about C++ syntax and I was
running into
g++ -ggdb -O6 -DNDEBUG -I./protoobj -g -O2 -fstack-protector-strong -Wformat
> We try to minimize external dependencies (even a package maintainer is
> a dependency in the process). So we were hoping/looking for something
> like (its a C++ library):
>
> #if defined(PACKAGE_BUILD) && !defined(CRYPTOPP_INIT_PRIORITY)
> # pragma message "It is recommended you define
Hi Frank,
In my opinion if you need the tool, write it - don't worry about what
anybody else thinks. If other people want it as well then that's the
point to worry about distro support.
Cheers,
Roger
Hej Gianfranco!
On Fri, 25 Sep 2015 at 20:25:08 +0200, Guilhem Moulin wrote:
> You'll find the new upload at
>
> dget -x
> http://mentors.debian.net/debian/pool/main/d/dropbear/dropbear_2015.68-1.dsc
Did you have time to look at the new upload yet? (Since you didn't take
ownership of the RFS
Jeffrey Walton writes:
> On Wed, Sep 30, 2015 at 3:55 AM, Russ Allbery wrote:
>> Yeah, this is why I'd put a check into the Debian packaging to be sure
>> that the software was built this way and abort the build during the
>> check phase if it wasn't, with a
On Wed, Sep 30, 2015 at 08:28:17PM +0200, Andreas Tille wrote:
> Hi,
>
> I have started packaging Tide (a tandard tool for ass-spectroscopy) at
>
>git://anonscm.debian.org/debian-med/tide.git
>
> Unfortunately these days gcc is more picky about C++ syntax and I was
> running into
>
> g++
> We would really, really prefer that you not do this, and instead work with
> whoever is packaging the library for Debian to add a test to the packaging
> rules themselves to be sure that they're built correctly.
>
> The reason for this is that Debian's packaging tools, by design, work
> exactly
Hi,
Quoting Christoph Biedl (2015-09-30 08:25:50)
> Personally, I'm not happy about adding extra magic to version numbers
> to identify binNMUs and would rather introduce a way to define a range
> of version numbers a package satifies, like in
>
> | Version: 5.25-3+b1# upper bound
>
Jens Reyer wrote...
> On 09/29/2015 10:13 PM, Christoph Biedl wrote:
> > I don't follow. Assuming the following installation:
> >
> > Name VersionArchitecture
> > +++--==-
> > ii ma_same:amd645.25-3 amd64
> > ii ma_foreign
Jeffrey Walton writes:
> OK, thanks. We are working with László Böszörményi. He's been very
> helpful.
> But if László ever leaves Debian or stops Crypto++, then I loose my
> contact and the path to ensure things are handled correctly.
Yeah, this is why I'd put a check into
On Wed, Sep 30, 2015 at 3:55 AM, Russ Allbery wrote:
> Jeffrey Walton writes:
>
>> OK, thanks. We are working with László Böszörményi. He's been very
>> helpful.
>
>> But if László ever leaves Debian or stops Crypto++, then I loose my
>> contact and the path
Hi,
Quoting gregor herrmann (2015-09-30 18:24:22)
> The last thing I heard about versioned Provides is that not all pieces of the
> infrastructure support it yet. (wanna-build or something was missing).
>
> I'd be more than happy to hear if this is all fixed by now.
dose3 (which is used to
* Jens Reyer , 2015-09-30, 03:20:
Depends:
ma_foreign (>= ${source:Version})
ma_foreign (<< ${source:Version}.1~)
This is what Lintian recommends when you can't use the "=" dependency,
but it might be too loose.
The intention was to include all binNMUs, but
On Tue, Sep 29, 2015 at 11:20 PM, Andrey Rahmatullin wrote:
> On Tue, Sep 29, 2015 at 03:12:18PM -0500, Matt Zagrabelny wrote:
>> A quick look at the source for dh_installinit doesn't show much about
>> the '-p', nor '--remaining' options. Can you elaborate or point to
>> further
Hi Everyone,
I have one last question related to packaging and installation. (I
hope it is the last question).
Crypto++ has test files. When they are run from $PWD, them they work
fine. After installation into, say, /usr/share/, they break because
the location is an implicit dependency. So the
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "classified-ads":
* Package name: classified-ads
Version : 0.08-1
Upstream Author : Antti Järvinen
* URL :
Control: owner -1 !
Thanks
Hi Antti,
I'll take a look in th next few days.
On 09/30/2015 12:13 PM, Jakub Wilk wrote:
> * Jens Reyer , 2015-09-30, 03:20:
>> Depends:
>>ma_foreign (>= ${source:Version})
>>ma_foreign (<< ${source:Version}.1~)
>
> This is what Lintian recommends when you can't use the "=" dependency,
> but it might be too
On Wed, 30 Sep 2015 17:39:44 +0200, Christoph Biedl wrote:
> Johannes Schauer wrote...
> > in fact, this can already be done:
> >
> > Package: foo
> > Architecture: any
> > Version: 5.25-3+b1
> > Provides: foo (= 5.25-3)
>
> Oy! So what's the reason those who trigger binNMUs do not utlize this
On 09/30/2015 05:39 PM, Christoph Biedl wrote:
> Johannes Schauer wrote...
>
>> Quoting Christoph Biedl (2015-09-30 08:25:50)
>>> Personally, I'm not happy about adding extra magic to version numbers
>>> to identify binNMUs and would rather introduce a way to define a range
>>> of version numbers
Am 26.09.2015 um 16:49 schrieb Gianfranco Costamagna:
Thanks for this hint, and Gianfranco, also thanks for your answer,
especially the link. I should have stated more precisely that setop
shall be a command line tool. Python sets and combine are interesting
but not as much universal as I plan
Johannes Schauer wrote...
> Quoting Christoph Biedl (2015-09-30 08:25:50)
> > Personally, I'm not happy about adding extra magic to version numbers
> > to identify binNMUs and would rather introduce a way to define a range
> > of version numbers a package satifies, like in
> >
> > | Version:
23 matches
Mail list logo