Bug#659916: scribus FTBFS on armel and armhf, qreal VS double issues (again)

Package: Scribus Severity: Serious Tags: Patch Your package FTBFS on armel and armhf with the following error. [ 60%] Building CXX object scribus/CMakeFiles/scribus.dir/pageitem_textframe.cpp.o /build/buildd-scribus_1.4.0.dfsg+r17287-1-armel-qlKYbT/scribus-1.4.0.dfsg+r17287/scribus/pageitem_tex

Bug#643470: Status of isc-dhcp-client

Currently, the version of isc-dhcp-client in unstable suffers two rc bugs, a FTBFS bug ( 643569 ) and a non-free IETF documents bug ( 645760 ) both related to embedded bind source. Furthermore isc-dhcp-client FTBFS in testing due to bug 643470 (which is fixed in unstable). It has been a mont

Bug#660309: tophat: broken code in configure script for determining CFLAGS

Package: tophat Version: 1.4.1-1 Severity: serious tags: patch The configure.ac file in your package contains code to determine c compiler flags based on architecture. Unfortunately this code is horriblly broken. On i386 the configure script uses -march=i686. This is not acceptable in debian

Bug#657446: [kbibtex] FTBS on armel

Bastien ROUCARIES wrote: Any news of this bug I've just tried an arch+indep build as root, an arch only build as root and an arch+indep build as nobody on my freshly updated armel sid system. All built successfully. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with

Bug#660309: tophat: broken code in configure script for determining CFLAGS

* I have not determined exactly how it is broken but it seems to be passing on all architectures. My suspsicion is the CFLAGS set before the test aren't actually being used. Furthermore even if the -m64 test were to be fixed it should not be used in debian as on some systems it may be accepted

Bug#660322: cdcat FTBFS on buildds dbase.cpp:48:19: fatal error: bzlib.h: No such file or directory,compilation terminated.

package: cdcat version: 1.7-1 severity: serious severity: serious cdcat failed to build on all buildds with the following error g++ -c -pipe -std=c++0x -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -O2 -D_REENTRANT -Wall -W -DMEDIAINFO_S

Bug#660324: picolisp FTBFS on armhf

Package: picolisp Version: 3.0.9.3-1 severity: important tags: patch Picolisp FTBFS on armhf with a PIE related error. The attatched patch disables use of PIE on armhf to make the package build (it is already disabled on amd64) --- picolisp-3.0.9.3/debian/rules 2012-02-17 15:19:30.0 +0

Bug#660415: openmsx FTBFS in unstable. /usr/include/zlib.h:1204:26: error: conflicting declaration 'typedef struct gzFile_s* gzFile'

Package: openmsx Severity: serious Tags: patch x-debbugs-cc: wij...@debian.org openmsx FTBFS in unstable with the following error. Compiling serialize.cc... g++ \ -MP -MMD -MF derived/x86_64-linux-debian/dep/serialize.d \ -o derived/x86_64-linux-debian/obj/serial

Bug#643470: [pkg-dhcp-devel] Bug#643470: Status of isc-dhcp-client

Hello, I have been working with upstream on addressing both of these issues, and I am hopeful that the 4.2.4 release, which is due in the next couple of months, to address these issues. I'm waiting to see how much better that release looks. Speaking both as someone trying to get the armhf po

Bug#679561: pegasus-wms FTBFS with new subversion

Package: pegasus-wms Version: 4.0.1+dfsg-6 Severity: serious Tags: patch pegasus-wms FTBFS with the new subversion [exec] g++ -ffor-scope -Wall -O2 -m64 -ggdb -DMACHINE_SPECIFIC=linux -DLINUX -DMAJOR=2 -DHAS_SVNVERSION=\"Unversioned directory\" pegasus-keg.cc -c -o pegasus-keg.o [e

Bug#679588: fritzing FTBFS on armel and armhf

Package: fritzing Version: 0.7.4b+dfsg-3 Severity: serious Tags: patch Your package failed to build on the armel and armhf autobuilders. src/sketch/sketchwidget.cpp:7075:28: error: no matching function for call to 'QPen::setDashPattern(QVector&)' src/sketch/sketchwidget.cpp:7075:28: note: cand

Bug#658422: tupi FTBFS on armel and armhf. no known conversion for argument 1 from 'QPair' to 'const QPair

Package: tupi Severity: important Tags: patch Tupi FTBFS on armel and armhf with the following error. ktpaletteparser.cpp: In member function 'virtual bool KTPaletteParser::startTag(const QString&, const QXmlAttributes&)': ktpaletteparser.cpp:133:83: error: no match for 'operator<<' in '((KTPa

Bug#570805: [kfreebsd-*] please rebuild elfutils/sid, ignoring the 2 known, testsuite failures (Re: transition: liblzma 5)

Kurt Roeckx wrote: Can I instead suggest someone looks at the kernel and fixes it? It used to work, it works on the porter machines, it just fails on the buidds. Aurelien Jarno wrote: The kernel part is not trivial to solve. It now fails because of the multiple bind mounts needed by schroot

Bug#642733: poco: FTBFS: Makefile:43: *** No ODBC library found. Please install, unixODBC or iODBC and try again. Stop.

/usr/bin/make -C /build/poco-VaXUUU/poco-1.3.6p1/Data/ODBC Makefile:43: *** No ODBC library found. Please install unixODBC or iODBC and try again. Stop. make[2]: Entering directory `/build/poco-VaXUUU/poco-1.3.6p1/Data/ODBC' make[2]: Leaving directory `/build/poco-VaXUUU/poco-1.3.6p1/Data/ODBC'

Bug#658526: please build gcc-mingw-w64 without ada support on armhf

package: gcc-mingw-w64 version: 4.6.1-16+2 tags: patch gnat is not yet available on armhf but there is no reason that should block the rest of gcc-mingw-w64 being built on armhf. So please disable ada support in the armhf version of the package for now. A patch is attatched to do that. diff -

Bug#640459: libindicator: FTBFS: indicator-image-helper.c:79: undefined, reference to `roundf'

Several months ago you uploaded a fix for this rc bug to experimental but the bug is still present in unstable. Please can you fix it in unstable too? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia

Bug#651472: getting python-apt into armhf testing

python-apt is not present in armhf testing and this is making a considerable number of packages uninstallable there. Getting armhf testing into an acceptable shape is a key step towards releasing armhf with wheezy. The version of python-apt in unstable (which includes armhf binaries) is not m

Bug#658770: libax25 FTBFS make: execvp: ./configure: Permission denied

Package: libax25 Version: 0.0.12-rc2+cvs20120204-1 Tags: patch Your package FTBFS with >./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man >make: execvp: ./configure: Permission denied The problem is that diff/patch don't preserve permissions, so when your

Bug#658770: Acknowledgement (libax25 FTBFS make: execvp: ./configure: Permission denied)

Debian Bug Tracking System wrote: If you wish to submit further information on this problem, please send it to 658...@bugs.debian.org. Looks like ax25-tools and ax25-apps have the same issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscri

Bug#648068: Source package (bind9) contains non-free IETF RFC/I-D

This source package contains the following files from the IETF under non-free license terms: This seems to have been fixed in the version in unstable. If that is indeed the case can someone please close the bug so it can migrate to testing -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...

Bug#657814: closed by Alessio Treglia (Bug#657814: fixed in toonloop 2.1.18-2)

Reopen 657814 found 657814 2.1.18-2 thanks * Use autoreconf at build time to fix FTBFS. (Closes: #657814) Umm, it seems you regenerated the autotools stuff but didn't apply/include the rest of the patch. Predictablly the package still FTBFS on armel and armhf. -- To UNSUBSCRIBE, email

Bug#685036: unblock: scim-anthy/1.2.7-5

Please unblock package scim-anthy version 1.2.7-5 It has been reported to us that the configuration setup for scim-anthy crashes for some users (bug 682601 and 680988). This is due to the recent transition in the package from gtk2 to gtk3. We've also included build-flag hardening in this upload

Bug#660488: miredo: FTBFS `pkglibdir' is not a legitimate directory for `PROGRAMS'

Le dimanche 29 juillet 2012 23:31:39 Bart Martens, vous avez écrit : > Hi Rémi, > > The patch fixes the bug. Why not simply use it ? Shall I upload an NMU ? It does not address the real issue. It must be pure luck that automake accepts it. I don't know enough about automake internals to co

Bug#668021: directvnc: Couldn't parse the keyboard mapping file

>Ok, that's actually a bug (!) that should be fixed in directvnc 0.7.8. >I will prepare a new package with that version. Otherwise, the >keyboard mapping file is optional (and documented in directvnc (1), >directvnc-kbmapping (7) and directvnc-xmapconv (1)). I'm running a debian derivative called r

Bug#682361: supercollider FTFBS on amel and armhf qreal VS double issues

ble Usually qreal is double (which is why it works), but on ARM systems qreal is float instead. This causes sc to fail to build on ARM systems. --- There is a similar problem with some reference parameters in QcMultislider .cpp which I have added the fix for to this patch -- Peter Green --- QtCollide

Bug#682595: gnuradio FTBFS on armel and armhf, tries to use unsuitable assembler.

Package: gnuradio Version: 3.5.1-1 Severity: important Tags: patch gnuradio FTBFS on armel and armhf with assembler errors On armel the build failed with the following error: cd /build/buildd-gnuradio_3.6.1-1-armel-iHSnxc/gnuradio-3.6.1/build/gnuradio-core/src/lib && /usr/bin/gcc -Dgnuradio_

Bug#682738: pulseaudio: please use linux-any as architecture specifier for bluetooth related packages and dependencies.

Package: pulseaudio Version: 2.0-3 Severity: important Tags: patch The build-depends on libbluetooth-dev uses the architecture specifier [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] this means that it will not be possible to satisfy the build-depends on any new non-linux architectures. Meanwhi

Bug#664547: spatialite: FTBFS on some archs (test failures)

01234567890123456789012345678901234567890123456789012345678901234567890123456789 Current version 3.1.0~rc2-1 seems ok on all archs, but for ppc where it fails to build with something that looks like a compiler issue. Based on https://bugs.launchpad.net/ubuntu/+source/spatialite/+bug/1012976 and

Bug#683075: spatialite in wheezy FTBFS

Package: spatialite Version: 3.0.0~beta20110817-3 While working on a derivative distribution I discovered that spatialite from testing FTBFS with the following error checking for geos_c.h... yes configure: error: 'libgeos_c' is required but it doesn't seems to be installed on this system. ch

Bug#683105: libavg: please consider supporting other architectures

package: libavg version: 1.7.1-1 severity: important tags: patch Afaict prior to it's removal and reintroduction libavg was available on most architectures. The changelog entries gave no inidication of this support being dropped yet the package was marked as only being suitable for i386 and amd6

Bug#666589: xastir: FTBFS: build-dependency not installable:, libgraphicsmagick1-dev

tags 666589 +patch thanks I'm running a derivative distribution called raspbian to provide a hardfloat distribution for the Pi and one of our users asked for this package so I went looking for a soloution to make it build. And I've found one but it's kinda ugly, it would require a trip throug

Bug#671962: freerdp: FTBFS: dh_install: libfreerdp1 missing files (usr/lib/*.so.*),, aborting

I've re-install Debian/kfreebsd inside virtualbox. And does get the FTBFS. But strangely, linux arches does get a correct multiarch path but the kfreebsd-i386 didn't. Any suggestions? As a quick and dirty solution you could put code in debian/rules that checks where the files are and if needed

Bug#676914: libsasl2-2: binNMU broke multi-arch installability

I have uploaded a no-change sourceful NMU to delayed/2 to fix the multi-arch coinstallability. Please tell me if you object to this and I will remove or reschedule it. I've used a fairly short timing as apparently this is preventing testing of the new ia32-libs package. Trivial debdiff is at

Bug#676914: libsasl2-2: binNMU broke multi-arch installability

Ondřej Surý wrote: Yeah, and next binNMU will break it again. Totally useless upload, hence I do object! As russ says wheezy is now in freeze so there should not be any more transitions and hence there should not be any more binnmus for transitions (which represent the vast majority of binnmus).

Bug#684070: libxml-libxml-perl: lack of error handling in build process means that if there is a problem broken packages are built (rather than a build failure)

Package: libxml-libxml-perl Version: 2.0001+dfsg-1 I am running a debian derivative called raspbian and one of our users reported that our libxml-libxml-perl package was broken. I looked at our package and discovered that the package only contained documentation files. I then looked at our bu

Bug#683011: FTBFS on arm* and kfreebsd*: libnss-ldap missing files (debian/tmp/usr/lib/*/*), aborting

retitle 683011 FTBFS on arm* and kfreebsd*: libnss-ldap missing files (debian/tmp/usr/lib/*/*), aborting tags 683011 +patch thanks It appeared the arm* and kfreebsd* failures are the same or at least related. At the very least other behaviours seem the same on those architectures. Specifically

Bug#683011: FTBFS on arm* and kfreebsd*: libnss-ldap missing files (debian/tmp/usr/lib/*/*), aborting

Emmanuel Kasper: can you tell us if the patch in http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=14;bug=683011 fixes libnss-ldap on kfreebsd for you? Steve Langasek wrote: My opinion is that the upstream rules on naming the libnss_ldap file are a horror show. ;) Your proposed fix looks rea

Bug#684324: please consider merging patch tweaks needed for raspbian.

package: dietlibc version: 0.33~cvs20120325-3 severity: wishlist tags: patch I'm currently working on an armv6 hardfloat derivitive of debian called raspbian. When trying to build the latest version of dietlibc I ran into the following error. gcc -D__dietlibc__ -I. -isystem include -pipe -nos

Bug#528863: fp-ide: indexing help file gives "Error storing index data (-2)"

Severity 528863 important Thanks When I load the help files in fp-ide from the fp-docs package and reply yes when it asks if it needs to build the index I get an "Error storing index data (-2)". It also happens when I use only a subfolder of the docs. Path to help files: /usr/share/doc/fp-docs/f

Bug#684437: unblock: fpc/2.6.0-6

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package fpc I have just sponsored a fpc upload by Abou Al Montacir to unstable, fixing two important bugs (note: one of the bugs was initially filed as normal but speaking a

Bug#684437: unblock: fpc/2.6.0-6

Philipp Kern wrote: Uhm, is it really required by policy to delete backup files that weren't created by the package in the first place? diff -Nru fpc-2.6.0/debian/fp-compiler.postrm.in fpc-2.6.0/debian/fp-compiler.postrm.in --- fpc-2.6.0/debian/fp-compiler.postrm.in 2012-05-06 21:43:32.000

Bug#674386: supercollider: FTBFS: scons: *** No SConstruct file found.

I'd like to mark this as "won't fix" because we're dropping the scons build system. The latest version of supercollider 3.5.x (which I'm currently asking debian-multimedia maintainers to upload) uses cmake instead which is much less mess. Supercollider 1:3.5.2-1 was uploaded just before the fr

Bug#684631: clisp doesn't build on armv7 hardware

package: clisp severity: important x-debbugs-cc: debian-...@lists.debian.org clisp fails to build with a segfault in an armel sid chroot on my beagleboard XM (armv7). It fails with an illegal instruction error if I add armhf to the architecture lists, add -marm to the start (if I add it after

Bug#686038: [BTS#686038] templates://fpc/{control,fp-compiler.templates}.in

David Prévot wrote: Control: tags -1 patch Control: severity -1 serious Justification: Policy 3.9.1 Dear Debian maintainer, On Monday, August 27, 2012, I notified you of the beginning of a review process concerning debconf templates for fpc. The debian-l10n-english contributors have now review

Bug#704159: unblock (pre-approval) : clang/1:3.0-6.2

Jonathan Wiltshire wrote: I'd rather not have the DEP-3 boilerplate in your first patch; with that removed, please go ahead with an upload to unstable and ping this bug when it is ready. Done. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscri

Bug#704111: [cfe-dev] Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.

Sylvestre Ledru wrote: FYI, as soon as Wheezy is released, I will upload version 3.2 or 3.3 of clang and the llvm toolchain. Now that the issue of finding a minimal fix for testing/unstable is out of the way. I just took a look at the package in experimental. I noticed the following. You s

Bug#704080: unblock: libarchive/3.0.4-3

It seems that Adam D. Barratt unblocked libarchive to fix the security bug. Unfortunately that wasn't enough to get the package into testing. Specifically it seems that s390x has not successfully built this package for some time (since before s390x stopped being considered a "broken and fucked

Bug#704769: Libarchive FTBFS on s390x sid buildds.

Package: libarchive Version: 3.0.1b-1 Severity: serious Note: this bug report is a continuation of discussions in the unblock bug for libarchive ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704080 ). my personal guess is that there's probably nothing s390x-specific to it, it's probably

Bug#705232: RFS: logic-analyzer-rpi/0.1.1-1 [ITP]

Paul Wise wrote: On Fri, Apr 12, 2013 at 3:38 AM, Anton Gladky wrote: The only doubts I have, whether the package will be useful for Debian at all, if it is targeted only on Raspberry PI (CC-ing debian-arm to get more opinions). Debian armel can run on the Raspberry Pi, so it will be

Bug#704252: preparing the fix

Paul Gevers wrote: I just uploaded with the patch for bug 704252. I didn't feel the other two items appropriate at this moment. It took me some more time than expected, because I had to fix two bugs in your script: So you are saying that rather rather than sponsoring abou's upload you made y

Bug#705232: RFS: logic-analyzer-rpi/0.1.1-1 [ITP]

Anton Gladky wrote: I would agree with that. But there is a problem of package building. It means, we can upload only the binary-version (source-based uploads are still not implemented in Debian unfortunately), which was built on armel, what is not always simple or difficult. Also if the package

Bug#704252: preparing the fix

Paul Gevers wrote: Peter, Please calm down. Sorry I could have been clearer in my last mail. I didn't intend to blame you for most of the issues with the patch (you just took a broken patch and made it differently broken) but I could see how it could have come across that way. Still I firmly

Bug#704252: preparing the fix

Paul Gevers wrote: Please go ahead. Lets get rid of this RC bug in Wheezy ASAP, so we can release. If I can help by filing and tracking the unblock after successful build (or I can even do the (unchanged :) ) upload for you), please let me know (here or in private) I just uploaded, feel free to

Bug#705506: lxtask: Reading /proc/cpuinfo is a bad way to determine CPU count

Package: lxtask Version: 0.1.4-3 lxtask determines the number of CPUs in the system by reading /proc/cpuinfo and searching for lines starting with (case sensitive) "processor". Unfortunately this doesn't work on all kernels leading to lxtask to think there are zero processors which in turn bre

Bug#642750: [PATCH] epiphany-browser: *HIGHLY* unstable on ia64, (IA-64/IPF/Itanium) platform

The proposed patch defines a third option USE(JSVALUE64W) which we use *only* on ia64. It uses an encapsulated union without any trick for the variant data type. This is portable but - the data type is 128-bits wide, - Enabling JIT compiler isn't possible - that's not that bad; ia64 doesn't

Bug#695080: please allow users to configure distribution name used in image descriptions

Package: debian-cd Severity: wishlist when I look at the jigdo files i've generated I see "ShortInfo='Debian GNU/Linux 7.0 "Wheezy" - Official Snapshot armhf CD Binary-1 20121203-21:36 (20121203)'" any idea how to change that to say raspbian? ok I found the answer, it's hardcoded, not in an

Bug#695244: which_deb fails when trying to build source cds from an archive that doesn't have i386 or amd64 binaries

Package: debian-cd I've been working on trying to build cd images for raspbian using debian-cd. While doing this I found that when building source cds which_deb only looks for i386 and amd64 packages files. If it finds neither it fails horriblly. This prevents building source CDs for derivati

Bug#695547: fpc does not set EABI tags to distinguish armel and armhf object files.

Package: fpc Severity: important Note: this bug report is mostly a reminder to myself, i'm not expecting anyone else to take any action. In particular this makes it impossible to distinguish for fpc built objects whether they use the soft or hard float ABI and that in turn has been causing s

Bug#706144: m-tx has very limited architecture list, making texlive-full uninstallable on many architectures

Package: m-tx Severity: important A bug was reported by a raspbian user about texlive-full being uninstable due to m-tx not being available. Taking a closer look revealed that the reason for this was that m-tx declares an explicit architecture list with only a handful of architectures. So texl

Bug#706144: m-tx has very limited architecture list, making texlive-full uninstallable on many architectures

I'm not the m-tx maintainer. I've just noticed that the m-tx source code is Pascal and the Pascal compiler is only avalable on a limited set of arches. This is probably the reason. Indeed you are right, I misread the build-log and didn't notice this. It seems likely that the maintainer look

Bug#706144: m-tx_0.60d-5.1_amd64.changes ACCEPTED into unstable

Roland Stigge wrote: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Hi you two, On 05/05/13 04:48, Debian FTP Masters wrote: Accepted: Format: 1.8 Date: Sun, 05 May 2013 01:54:02 + Source: m-tx Binary: m-tx Architecture: source amd64 Version: 0.60d-5.1 Distribution: unstable Urge

Bug#684631: clisp doesn't build on armv7 hardware

I've prepared a NMU with the patch from sourceforge to prevent crashing on more modern arm hardware and with debian/* tweaks for armhf. I've uploaded to delayed/5 with the attatched debdiff. Please tell me if you have any objections to this NMU so I can change or cancel it. diff -Nru clisp-2.49

Bug#706866: transition: libarchive

I am requesting a transition from libarchive12 to libarchive13. libarchive13 is from the latest release of libarchive (3.1.2). A soname bump was done upstream due to some ABI changes, specifically with HFS support. I notice the most recent experimental upload FTBFS on many architectures with

Bug#706866: [Fwd: re: Bug#706866: transition: libarchive]

Forwarding reply to my query to the bug report. Original Message Subject:re: Bug#706866: transition: libarchive Date: Mon, 6 May 2013 20:17:37 -0400 From: Andres Mejia To: peter green References: <518842df.1000...@p10link.net> Yes, I plan on dis

Bug#710625: performous: FTBFS: xtime.hh:27:34: error: expected unqualified-id before numeric constant

It's a problem in boost which is fixed in 1.50. TIME_UTC is a C11 macro that colides with boost::TIME_UTC. In Boost 1.50, this constant was renamed to TIME_UTC_. You should update your Build-Depends (upstream has already fixed this). Unfortunately changing the build-depends to point at boos

Bug#710643: ibus: FTBFS: ibusfactory.c:294:52: error: format not a string literal and no format arguments [-Werror=format-security]

The fix was pretty simple, just let g_dbus_method_invocation_return_error do the formatting rather than trying to do it ourselves. Format security error fixed, code simplified and unnessacery copy avoided win-win-win. Patch is attached. The patch contains a NMU changelog entry but I have no i

Bug#711457: python-qt4: insufficient build-depends

Package: python-qt4 Version: 4.10.1-1 Severity: minor While working on a deriviative (specifically raspbian) I noticed that your package uses python3.2-config --configdir ). This is provided by python3.2-dev. However your build-depends do not ensure that a sufficiently recent version is instal

Bug#711544: claws-mail FTBFS, fails to find python shared library.

Package: claws-mail Version: 3.9.1-1 Severity: serious Claws-mail seems to be having trouble finding the python shared library. This seems to lead to the python plugin not being built which in turn leads to a missing file when trying to pack the debs. I presume this is related to the multiarch

Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.

Package: clang Version: 1:3.0-6.1 Severity: grave x-debbugs-cc: debian-...@lists.debian.org; cfe-...@cs.uiuc.edu (note for non-debian people reading this, the version of clang in debian wheezy is a 3.0 based version which already has patches to make it invoke the linker with appropriate argumen

Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.

Ok I just had a discussion with adam conrad about this on IRC. According to him clang currently does assume that armv7 means coretex a8 and that coretex a8 mean full vfpv3 and neon. There is a patch in ubuntu precise/quantal to fix this (26-armv7-not-neon.patch) but it's a pretty big patch an

Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.

Sylvestre Ledru wrote: No need to do a NMU here. Ok I've attached a diff. Note: i'm currently running a test build of this version i'll follow up later with results from that test to confirm things are ok (I don't see why they wouldn't be) diff -urN clang-3.0/debian/changelog clang-3.0.new/d

Bug#704159: unblock (pre-approval) : clang/1:3.0-6.2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please approve my upload for package clang, this fixes two issues one of which is filed as a grave bug. The other I also judge to be grave but is not currently filed as a bug in debian (if y

Bug#704159: unblock (pre-approval) : clang/1:3.0-6.2

peter green wrote: Debdiff is attatched Sorry forgot to attatch it, here it is. diff -Nru clang-3.0/debian/changelog clang-3.0/debian/changelog --- clang-3.0/debian/changelog 2013-02-10 14:47:29.0 + +++ clang-3.0/debian/changelog 2013-03-28 18:03:16.0 + @@ -1,3 +1,16

Bug#699589: lsb ftbfs in wheezy, testsuite problems.

Package: lsb Severity: important Attempting to build lsb in a wheezy amd64 chroot I get PYTHONPATH=. python3.2 test/test_initdutils.py -vv Traceback (most recent call last): File "test/test_initdutils.py", line 4, in import initdutils as iu File "/lsb-4.1+Debian8/initdutils.py", line 18

Bug#699589: lsb ftbfs in wheezy, testsuite problems.

severity 699589 serious thanks frbfs on a release architecture is serious (sorry for screwing this up in the inital report) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#679449: shared memory problem on armel

Ben Hutchings wrote: The wilful incompatibility of Debian derivatives Raspbian IS compatible with debian armhf in the sense that if your hardware supports it you can mix debian armhf packages and raspbian packages. In fact that is how raspbian was built in the first place. Precedent both with

Bug#679449: shared memory problem on armel

gregor herrmann wrote: As armhf really describes the ABI rather than the underlying CPU architecture, it would make our jobs with Raspbian much easier if CPU architecture dependent packages could test that the architecture is indeed Armv7+ and not blindly assume armhf implicitly means the system

Bug#679449: shared memory problem on armel

gregor herrmann wrote: On Thu, 07 Feb 2013 21:48:24 +, peter green wrote: Can this test be expressed in some easy terms to be used in debian/rules? DEB_HOST_GNU_TYPE ?=$(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) ARM_VERSION_NUMBER :=$(shell $(DEB_HOST_GNU_TYPE)-cpp -dM /dev

Bug#700470: libmouse-perl: lack of error handling in the build can lead to broken packages.

Package: libmouse-perl Version: 0.99-1 Severity: normal http://snapshot.raspbian.org/201302121719/raspbian/logs/main/libm/libmouse-perl.log dh_auto_configure -a Mouse configured with XS. This distribution requires a C compiler, but it's not available, stopped. dh_auto_build -a <--snip--> d

Bug#696909: chromium segfaults on startup on armhf

peter green wrote: I can confim that using bfd instead of gold fixes the issue on armhf. Since this mail a new version of chromium has hit sid and i've been doing some tests with it. I have good news and bad news. The good news: by using --no-keep-memory I was able to get the address

Bug#698153: lvm2: LVM - kernel 3.6.11 - leaked on lvcreate invocation

tags 698153 +patch thanks After discussions in https://bugs.launchpad.net/raspbian/+bug/1096224 I just applied a fix for this in raspbian. A filtered debdiff* is attatched. * I accidently refreshed an unrelated patch while working on the fix which created some noise in the debdiff. --- lvm2-2

Bug#684631: clisp NMU updated

Since the new eglibc was uploaded to unstable I have updated my NMU of clisp to fix the build failure with it. The old version of the nmu has been cancelled and the newversion uploaded to delayed/3, i've attatched the debdiff for the new version of the NMU to this mail. Again please tell me if

Bug#704350: lxtask NMU uploaded to delayed/10

I have uploaded a NMU of lxtask to fix the reporting of -1% CPU on some kernels to delayed/10. I also removed Daniel Baumann from uploaders per his request. Please tell me if you have any problems with this upload so that I can change or cancel it. diff -Nru lxtask-0.1.4/debian/changelog lxtas

Bug#707882: scribus FTBFS on armel and armhf, qreal vs double problems

package: scribus version: 1.4.2.dfsg+r18267-1 severity: serious Looks like you got yet another qreal vs double issue. [ 67%] Building CXX object scribus/CMakeFiles/scribus.dir/scribus.cpp.o /build/buildd-scribus_1.4.2.dfsg+r18267-1-armel-jtGbQP/scribus-1.4.2.dfsg+r18267/scribus/scribus.cpp: In

Bug#707280: mysql-5.5: gcc-4.4 is targeted for removal in unstable

Found 707280 5.5.30+dfsg-1.1 Thanks Marking this as affecting the version in testing so it doesn't block migration of the security fix. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#702499: python-zbar segfaults on import on arm

Package: python-zbar Severity: grave Version: 0.10+doc-7 root@plugwash:/# gdb python GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistr

Bug#709007: acl2 not autobuildable in jessie.

Package: acl2 Version: 6.0-2 Tags: jessie Severity: serious Emacs 24 is not currently available in jessie and is blocked from migration by three rc bugs. This means that the first choice build-deps for acl2 are not satisfiable in jessie meaning that acl2 cannot be autobuilt using the build-dep

Bug#707891: llvm-toolchain-3.2 FTBFS on most architectures.

Recent uploads have changed things round a bit. The package still FTBFS on most architectures but it does so in a different way. make[1]: Leaving directory `/build/buildd-llvm-toolchain-3.2_3.2repack-6-s390x-gQ5TrE/llvm-toolchain-3.2-3.2repack' dh_install -a cp: cannot stat 'debian/tmp/usr/bi

Bug#700389: libtimbl3-dev: Broken dependencies make other packages FTBFS (needs ticcutils/StringOps.h from libticcutils1-dev)

This bug was filed against libtimbl3-dev and the discussion in this bug claims it's an issue in that package but the bug was closed with an upload of frog. Closing a bug in one package with an upload of another leaves the bug in a somewhat confusing state. The bug is "closed" but it's still c

Bug#710102: texworks FTBFS Project ERROR: Package zlib not found

Package: textworks Version: 0.5~svn1035-1 Severity: serious configuring default paths for TeX binaries as: /usr/local/texlive/2012/bin/x86_64-linux:/usr/local/texlive/2011/bin/x86_64-linux:/usr/local/texlive/2010/bin/x86_64-linux:/usr/local/texlive/2009/bin/x86_64-linux:/usr/local/texlive/2008/bi

Bug#572420: Please change this bug to libsdl1.2debian

peter green wrote: >The bug is actually in libsdl1.2debian. It has improper compile flags >for powerpc g3. What these are I do not know. looking at the build log -maltivec seems to be the smoking gun. It appears the upstream configure script is looking for altivec support at build ti

Bug#572420: Please change this bug to libsdl1.2debian

Rick Thomas wrote: I own both G3's and G4's running Debian Stable. I can take them down for limited periods (a day or so) to run other versions of Debian. If someone who knows what he/she's doing can walk me through the steps (I'm an experienced system admin. But I'm not a developer.) I'm

Bug#625311: bomberclone: ftbfs with gcc-4.6 -Werror

tags 625311 +patch thanks patch is attatched just add it to debian/patches I have built the game with the patch and checked it seems to basically run with this patch. I have not extensively tested it. I am just doing flyby bugfixes I do not have previous experiance with this game or package. d

Bug#625319: chiark-tcl: ftbfs with gcc-4.6 -Werror

tags 625319 +patch thanks Patch is attatched that eliminates the unused but set variables. Note: i'm just doing flyby rc bugsquashing, I have tested that the resulting packages build and install but I have not tested beyong that. diff -ur chiark-tcl-1.1.0+nmu2/base/hook.c chiark-tcl-1.1.0+nmu2.

Bug#625323: collectd: ftbfs with gcc-4.6 -Werror

tags 625323 +patch thanks As well as the issue mentioned in this bug report I found two other issues that were preventing successfull build. Patches for all three issues and a new 00list file to apply them in the right order (the package uses dpatch) are attatched. Note that since I don't u

Bug#625308: audtty: ftbfs with gcc-4.6 -Werror

tags 625308 +patch thanks It appears this bug was misreported and a linker error was the cause not a compiler warning. A modified debian/rules file is attatched that makes the package build again. #!/usr/bin/make -f export LDFLAGS += -lglib-2.0 -lgobject-2.0 %: dh $@ override_dh_au

Bug#636802: fpc fails to link against libc on some architectures due to multiarch

reassign 636802 fpc thanks From my testing on armel I now belive that the issue causing the lazarus build failures is a problem with freepascal and multiarch. I haven't tried to troubleshoot the issue on powerpc or sparc as I don't have access to them but I presume it is the same issue. On a

Bug#636802: [fpc-devel] fpc fails to link against libc on some architectures due to multiarch

tags 636802 +patch thanks Note: jonas's reply was only posted to fpc-devel, not to the debian bug report , a copy can be found at http://lists.freepascal.org/lists/fpc-devel/2011-August/025444.html Jonas Maebe wrote: Is there a standard for multiarch library path locations and names? Multi

Bug#643866: electric-fence: FTBFS on GNU/kFreeBSD

Matthew Vernon wrote: Hi, I have just tested and the version in testing also FTBFS on kfreebsd OOI, what's the failure mode? Program terminated with a Segfault during the self test. Thanks, Matthew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject

Bug#622134: transition: openssl 1.0.0

openssl098 is still kept in testing by: - ace (ICE on armel) Taking a look at this one - beid (RC-buggy, candidate for removal) - ipsec-tools (#619687 #643570, has reverse dependencies) - isakmpd (#622051, candidate for removal) This bug has had a patch for several months, but the maintainer has

<    1   2   3   4   5   6   7   8   9   10   >