Kenton (upstream maintainer) has narrowed this down to a compiler bug that
only occurs during a build without the -DNDEBUG flag set. Typically the
NDEBUG flag is set if CXXFLAGS are left unspecified, but the Debian build
scripts obviously meddle with those a little. To work around this, I've
❦ 19 août 2013 01:34 CEST, Tom Lee deb...@tomlee.co :
I'm thinking maybe I rip out the symbols file all together for now --
it sounds like the tooling isn't there for it yet. What do you think?
Yes, just remove it.
--
Watch out for off-by-one errors.
- The Elements of Programming
Compiler issue doesn't appear to be a Debian bug. Kenton just filed
upstream, logging it here for posterity:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58192
Again, the capnproto package now builds with the -DNDEBUG flag which
enables some inlining that happens to work around this bug.
On
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package mwlib.rl
* Package name: mwlib.rl
Version : 0.14.3-1
Upstream Author : PediaPress GmbH
* URL : https://github.com/pediapress/mwlib.rl
* License : BSD-3
❦ 18 août 2013 22:35 CEST, Andrey Rahmatullin w...@wrar.name :
You are using a .install file but since you override dh_auto_install, it
is not used.
Yeah, I've forgot to delete it.
For the manual page, just declare it in a .manpages.
Oh, I didn't know dh_installman is that clever.
Okay,
❦ 19 août 2013 07:57 CEST, Tom Lee deb...@tomlee.co :
Also incorporated part of an upstream patch for another potential,
seemingly unrelated memory corruption issue that didn't quite make the
0.2.0 release.
Let me know if you still can't build from source with these two changes in
place.
On Mon, Aug 19, 2013 at 12:28 AM, Vincent Bernat ber...@debian.org wrote:
OK, it works for me too.
Great!
I've also explicitly removed the .symbols file as I found the Policy
Manual
explicitly talks about C++ libraries in the last paragraph of section
8.6 (
❦ 19 août 2013 09:56 CEST, Tom Lee deb...@tomlee.co :
- The hardening stuff does not seem to work correctly. Maybe you could
just try with debhelper 9 and debian/compat to 9 to have them apply
automatically.
Happy to try compat 9, but what can I do to verify that the hardening stuff
Le 19/08/2013 03:05, Wookey a écrit :
+++ Henrique de Moraes Holschuh [2013-08-18 21:39 -0300]:
On Sun, 18 Aug 2013, Adam Borowski wrote:
C - ship both versions on i386 and switch between them on runtime
The linker can select at runtime different sets of libraries depending on
some cpu
On 2013-08-19 11:31 +0200, Fabien Givors (Debian) wrote:
I had a look to eglibc source package. I can tell some dark magic is at
work in this package. But as I need only a small fragment of it, I'll
probably be able to extract it.
It would probably be easier to look at a simpler package such
On Mon, Aug 19, 2013 at 1:47 AM, Vincent Bernat ber...@debian.org wrote:
❦ 19 août 2013 09:56 CEST, Tom Lee deb...@tomlee.co :
- The hardening stuff does not seem to work correctly. Maybe you could
just try with debhelper 9 and debian/compat to 9 to have them apply
automatically.
❦ 19 août 2013 11:46 CEST, Tom Lee deb...@tomlee.co :
The easiest way is to use Lintian (I use it with -viI).
Odd, I don't see any warnings:
tom@desktop:~/Source$ lintian -viI capnproto_0.2.0-1.dsc
N: Using profile debian/main.
N: Setting up lab in /tmp/temp-lintian-lab-q9W0nEVK6F ...
Andreas Moog writes:
All assets (graphics, music, text) are licensed under a Creative Commons
BY-NC-SA 3.0 Unported License. See
http://creativecommons.org/licenses/by-nc-sa/3.0/deed.en_US for more info.
As far as I understand it, that means your package can not enter Debian,
but has to go
Hi Andreas,
On Sun, Aug 18, 2013 at 10:27:50AM +0200, Andreas Moog wrote:
Well, this is the Gtk library - but it does not explain why the linker
might find it when using debuild (even in a manually created unstable
chroot but fails when using pdebuild. Usually this is an issue of a
Bonjour,
je suis débutante dans la création des paquets débian:
1) j'aimerai réduire la taille de mon paquet source généré! est-ce qu'il y
a un moyen afin d'ignorer des dossier lors de la création d'un paquet
source?
je viens de tester : export DH_ALWAYS_EXCLUDE=.bzr-builddeb:logs
dans le
Your message dated Mon, 19 Aug 2013 16:23:43 +
with message-id e1vbsf5-0008ma...@quantz.debian.org
and subject line closing RFS: cpuid/20130610-1 [ITA]
has caused the Debian Bug report #720113,
regarding RFS: cpuid/20130610-1 [ITA]
to be marked as done.
This means that you claim that the
Hi Marius,
building with pbuilder gave this error message. Is this a problem?
Thorsten
imake -DUseInstalled -I/usr/lib/X11/config
make Makefiles
make[2]: Entering directory `/tmp/buildd/xfishtank-2.5'
make[2]: Nothing to be done for `Makefiles'.
make[2]: Leaving directory
Hi,
I am currently working on the ticalcs package:
URL:http://packages.qa.debian.org/libt/libticalcs.html
It contains so-called ROM-dumpers in assembler code which have been
removed for DFSG reasons on the older versions of this package, and I
followed that example and removed them from the
On Mon, Aug 19, 2013 at 11:55:12PM +0200, Andreas B. Mundt wrote:
It contains so-called ROM-dumpers in assembler code which have been
removed for DFSG reasons on the older versions of this package, and I
followed that example and removed them from the version in sid as
well.
However, as
On Tue, Aug 20, 2013 at 12:30:32AM +0200, Adam Borowski wrote:
On Mon, Aug 19, 2013 at 11:55:12PM +0200, Andreas B. Mundt wrote:
It contains so-called ROM-dumpers in assembler code which have been
removed for DFSG reasons on the older versions of this package, and I
followed that example
Dear mentors,
I would like to request a review and sponsorship of my package.
The package is available via the mentors website:
https://mentors.debian.net/package/mosquitto
Although the report states that the watch file is missing or does not
work, this is not the case. There was simply a web
Besides the obvious LT name, I've done some more digging that leads me
to suspect that the issue is the version of libtool. I was able to
install autoconf 2.59 and automake 1.9.6, but libtool 1.5.22 (8 years
old) is not available. How should we proceed at this point?
On Fri, Aug 16, 2013 at 10:28
Alright, latest build of this package is up on mentors.debian.net:
http://mentors.debian.net/package/capnproto
Noticed that my watch file has detected a new point release Kenton put out
earlier today to work around that GCC compiler bug.
Should I upgrade to the new release now? Or is it okay to
23 matches
Mail list logo
