Bug#1023585: Bug#989125: lists.debian.org: Request a mailing list named "debian-loongarch64"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, As I am interested in doing SIMD work on the Loongaarch64 ISA and I now have actual working hardware: Loongson 7a2000 3a5000 board. I think having a list for the new port is a good thing, I second the proposal. Regards Konstantinos

Bug#1021079: NMU w/o ppc64el?

On 15/1/23 03:33, Adam Borowski wrote: Hi! As you're apparently too busy to either fix ppc or suggest a different plan, I'd make a NMU dropping ppc64el for now so the package can be released with Bookworm. Please say if I shouldn't. Hi Adam, It is true that I am busy during this period,

Bug#1004238: RFA: python-gbulb

Package: wnpp Severity: normal Control: affects -1 src:python-gbulb I have stopped using this package since some time and I can no longer afford the time to maintain it. If someone is willing to adopt it, feel free otherwise I will orphan it in the coming weeks. Regards Konstantinos

Bug#1004237: RFA: dlang-openssl

Package: wnpp Severity: normal Control: affects -1 src:dlang-openssl I have stopped using this package since some time and I can no longer afford the time to maintain it. If someone is willing to adopt it, feel free otherwise I will orphan it in the coming weeks. Regards Konstantinos

Bug#1004236: RFA: dlang-libevent

Package: wnpp Severity: normal Control: affects -1 src:dlang-libevent I have stopped using this package since some time and I can no longer afford the time to maintain it. If someone is willing to adopt it, feel free otherwise I will orphan it in the coming weeks. Regards Konstantinos

Bug#1004235: RFA: autobahn-cpp

Package: wnpp Severity: normal Control: affects -1 src:autobahn-cpp I have stopped using this package since some time and I can no longer afford the time to maintain it. If someone is willing to adopt it, feel free otherwise I will orphan it in the coming weeks. Regards Konstantinos

Bug#1004079: ITP: vectorscan

Package: wnpp Severity: wishlist Owner: Konstantinos Margaritis * Package name: vectorscan   Version : 5.4.6   Upstream Author : Vectorscan Team * URL :https://github.com/VectorCamp/vectorscan * License : BSD   Programming Lang: C, C++   Description :Portable

Bug#976901: nvidia-tesla-450-kernel-dkms: Fails to build DKMS kernel module on ppc64le 450.80.02

On 19/12/20 3:24 μ.μ., Andreas Beckmann wrote: Control: severity -1 important This bug should not cause nvidia-cuda-toolkit to be removed from testing... Indeed, and seeing that Nvidia only supports the "compute" mode of the driver on ppc64le, I'm having second thoughts about using them on

Bug#976901: nvidia-tesla-450-kernel-dkms: Fails to build DKMS kernel module on ppc64le 450.80.02

On 10/12/20 5:37 μ.μ., Andreas Beckmann wrote: If it works with Linux 5.8, can you stick to an older kernel (which will not receive security updates) until there is a newer driver release available from Nvidia? I just installed 5.8 from buster-backports along with tesla-440 driver and it

Bug#976901: nvidia-tesla-450-kernel-dkms: Fails to build DKMS kernel module on ppc64le 450.80.02

On 10/12/20 1:19 π.μ., Andreas Beckmann wrote: but I'm not sure whether it is worth backporting them, since you most likely will be affected by #973729 - nvidia-uvm does not work with Linux 5.9 which is fixed in 455.45.01 Well, I did the replace you suggested below and even though the modules

Bug#913752: Why is an "all" package compiling things?

Στις 14-11-2018, ημέρα Τετ, και ώρα 18:53 +, ο/η Steve McIntyre έγραψε: > Package: autobahn-cpp > Version: 17.5.1+git7cc5d37-2 > Severity: serious > Justification: fails to build from source > > Hi, > > Running an rebuild of armhf and armel running on top of arm64 > machines, I'm seeing

Bug#859667: [Pkg-d-devel] Bug#859667: libundead: FTBFS on armhf and ppc64el: tests fail

Στις 07-04-2017, ημέρα Παρ, και ώρα 18:03 +0200, ο/η Iain Buclaw έγραψε: > On 7 April 2017 at 16:02, Andreas Tille wrote: > > On Wed, Apr 05, 2017 at 10:22:28PM +0200, Iain Buclaw wrote: > > > Which compiler? > > > > $ LANG=C apt-cache policy ldc > > ldc: > >   Installed:

Bug#836193: Improper handling of arch all only package

Στις 08-02-2017, ημέρα Τετ, και ώρα 14:14 +0100, ο/η Stephan Sürken έγραψε: > However, could it be that your are simply having incorrect build- > deps? ... > Removing these dependendies from control make the package build fine. > > It seems it's just a "correctly failing build" -- please check

Bug#836193: Improper handling of arch all only package

Στις 08-02-2017, ημέρα Τετ, και ώρα 13:32 +0100, ο/η Stephan Sürken έγραψε: > Also, it would be (easy and) helpful if you can just build the test > packages, and report whether test package 'mbd-test-archall' also > fails > on your setup. mdb-test-archall passes which is good Konstantinos

Bug#836193: Improper handling of arch all only package

Στις 08-02-2017, ημέρα Τετ, και ώρα 11:51 +0100, ο/η Stephan Sürken έγραψε: > Hi Konstantinos, > > > On Di, 2017-02-07 at 16:32 +0200, Konstantinos Margaritis wrote: > (...) > > > I fear only a complete Debian Source Package would be of any help. > > Alternativel

Bug#836193: Improper handling of arch all only package

team, test-sample-framework-doc Architecture: all Version: 3.1.106~test9+2 Maintainer: Konstantinos Margaritis <mar...@debian.org> Standards-Version: 3.9.8 Build-Depends: debhelper (>= 10), dh-python, docbook-xml, docbook-xsl, lsb-release, python-all, python3-all, xsltproc Build-Depend

Bug#836193: Improper handling of arch all only package

Hello, I just wanted to say that I was able to reproduce this bug on a stretch based system (mini-buildd 1.0.29), building 2 arches, i386/amd64, where i386 is optional and amd64 builder builds arch:all packages. I uploaded a python package in both source and binary form (ie, source.changes,

Bug#852664: ITP: python-gbulb

Package: wnpp Severity: wishlist Owner: Konstantinos Margaritis <mar...@debian.org> * Package name: python-gbulb   Version : 0.5.2   Upstream Author : Nathan Hoad * URL : https://github.com/nathan-hoad/gbulb * License : Apache 2.0   Programming Lang:

Bug#851575: ITP: autobahn-cpp -- WAMP in C++ for Boost/Asio

Package: wnpp Severity: wishlist Owner: Konstantinos Margaritis <mar...@debian.org> * Package name: autobahn-cpp   Version : 0.2.1   Upstream Author : Crossbar.io Technologies GmbH and contributors * URL : http://crossbar.io/autobahn * License : Boost So

Bug#796751: ldc: diff for NMU version 1:0.14.0.dfsg-1.1

Hi Neil, if this is urgent and cannot wait a couple of days, the past days I've been testing 0.15.2 and quite possibly I'll upload directly 0.16.0 (which was just tagged) soon. If I haven't uploaded by this weekend feel free to upload 0.14.0.dfsg-1.1 (for the record, 0.15.1-1 has been in

Bug#779029: scummvm: fails to work on armhf, ARM ASM is buggy [PATCH]

. Regards -- Konstantinos Margaritis email: mar...@freevec.org, mar...@debian.org blog: http://freevec.org gpg: 3FC3 7391 FECD D3CB 5501 7121 6606 027F 6437 124C Description: Disable arm asm as it breaks on armhf --- scummvm-1.7.0+dfsg.orig/configure +++ scummvm-1.7.0+dfsg/configure @@ -2027,10

Bug#763900: raise severity as it's totally unusable on powerpc

severity 763900 grave thanks This is the definition of a 'grave' bug, this package is totally unusable on powerpc at the moment. The patch supplied also seems trivial, please fix the package. Regards Konstantinos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a

Bug#734360: gitpkg: Please support git submodules

Hi all, I would like to say that I've tested the patch from Benjamin with my ldc git tree on alioth: http://anonscm.debian.org/cgit/pkg-ldc/pkg-ldc.git/ which includes 3 submodules from upstream, and gitpkg successfully includes those in the resulting source package. Without the patch, gitpkg

Bug#767526: RM: ldc [sparc] ROM; ANAIS

Package: ftp.debian.org Severity: normal A followup to #760871, it appears I had forgotten to include sparc in the old versions list for ldc. It would be greatly appreciated if that could be removed as well, as its presence forbids the already resolved bugs to be archived. out of date on sparc:

Bug#766630: supercollider: ftbfs on ppc64el -- error: invalid parameter combination for AltiVec intrinsic

On Fri, 24 Oct 2014 12:39:18 -0200 ferse...@br.ibm.com wrote: In any case, perhaps the solution is to disable supernova in ppc64el as well instead of adding custom flags. Simply disabling it for ppc64el did not do the work (completely), but you can test it if you want =) The problem is

Bug#766630: supercollider: ftbfs on ppc64el -- error: invalid parameter combination for AltiVec intrinsic

On Fri, 24 Oct 2014 12:13:16 -0300 Felipe Sateler fsate...@debian.org wrote: I had a few questions regarding the patch for enabling altivec on ppc32, I'll repeat them here: I'm very ignorant on altivec (or simd in general), but I try to understand the patch anyway. This patch seems to

Bug#761454: ldc: Linking issues

On Mon, 15 Sep 2014 19:18:36 +0200 Witold Baryluk witold.bary...@gmail.com wrote: I think the problem is that I run stable with only LDC from sid. Some versioned dependencies are not fully correct probably. I will take look later. Hi Witold, Do you have any news on this? Have you tried it

Bug#761454: ldc: Linking issues

tags 761454 + moreinfo unreproducible thanks On Sun, 14 Sep 2014 00:10:13 +0200 Witold Baryluk witold.bary...@gmail.com wrote: Package: ldc Version: 1:0.14.0.dfsg-1 Severity: normal Dear Maintainer, $ cat heelo.d module hello; import std.stdio; void main() { } $ ldc2 hello.d

Bug#760871: Please remove old ldc versions (0.14.0)

Package: ftp.debian.org Severity: normal As suggested in #754856, old ldc binaries need to be removed from unstable: out of date on armel: ldc (from 1:0.13.0-1) out of date on kfreebsd-amd64: ldc, libllvm-bindings-d (from 0.9.1 +hg1634-1) out of date on kfreebsd-i386: ldc, libllvm-bindings-d

Bug#754856: buildd.debian.org: please remove s390* from p-a-s for ldc

On Sat, 26 Jul 2014 17:20:08 +0200 Philipp Kern pk...@debian.org wrote: Sure, but first you need to upload a build that's arch-restricted. Then we try to drop the package from P-a-s anyway so that the architecture field is authoritative. Hi, upload of 0.14.0-1 fixed that, I am in the process

Bug#758620: linux-image-3.2.0-4-powerpc64: please enable CONFIG_VSX in the powerpc64 flavours

Package: linux Version: 3.2.0-4 Severity: minor Hi, I was trying to test some VSX code in the partch.debian.org powerpc/powerpc64 porterbox and while VSX support was enabled in the compiler, it was not enabled in the kernel. Since it's required/recommended to use official kernels in Debian

Bug#754856: buildd.debian.org: please remove s390* from p-a-s for ldc

On Sat, 26 Jul 2014 15:54:50 +0200 Philipp Kern pk...@debian.org wrote: tag 754856 + moreinfo thanks On Tue, Jul 15, 2014 at 11:26:07AM +0300, Konstantinos Margaritis wrote: Please remove s390/s390x entries from p-a-s for the ldc package. Since I took over the package, I'd like to check

Bug#754856: buildd.debian.org: please remove s390* from p-a-s for ldc

On Sat, 26 Jul 2014 17:20:08 +0200 Philipp Kern pk...@debian.org wrote: Sure, but first you need to upload a build that's arch-restricted. Then we try to drop the package from P-a-s anyway so that the architecture field is authoritative. Ok, am actually working on that these days. I'll ping

Bug#754856: buildd.debian.org: please remove s390* from p-a-s for ldc

Package: buildd.debian.org Severity: wishlist Please remove s390/s390x entries from p-a-s for the ldc package. Since I took over the package, I'd like to check what's it's current status with s390* is, if it doesn't I can take it with upstream and if it's easily fixable I can fix it, if not I'll

Bug#754689: ldc: FTBFS on kfreebsd-*: undefined references

On Sun, 13 Jul 2014 15:15:45 +0200 Cyril Brulebois k...@debian.org wrote: Source: ldc Version: 1:0.13.0-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-* due to undefined references during linking: Hi Cyril, Also talked to upstream about this

Bug#754690: ldc: FTBFS on powerpc: static assert Architecture not supported.

On Sun, 13 Jul 2014 15:16:49 +0200 Cyril Brulebois k...@debian.org wrote: Source: ldc Version: 1:0.13.0-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on powerpc: Hi Cyril, Ok, I've taken it with upstream and it seems a fix will be available soon (actually,

Bug#744132: ITP: dlang-openssl - D bindings for openssl library

in other distros like Arch which also support multiple D compilers but include compiler-agnostic sources in /usr/include/dlang/common. Konstantinos Margaritis pgp7ivv_xGB9Y.pgp Description: PGP signature

Bug#742223: ITP: dlang-libevent - D bindings for libevent library

Package: dlang-libevent Version: 2.0.16-1 Severity: Wishlist I've decided to improve the D language support in Debian, and as part of that process, I intend to package several D bindings for common libraries for Debian. First one is the libevent D bindings. URL:

Bug#742222: ITP: dlang-libevent - D bindings for libevent library

Package: wnpp Severity: Wishlist I've decided to improve the D language support in Debian, and as part of that process, I intend to package several D bindings for common libraries for Debian. First one is the libevent D bindings. Resulting package name: dlang-libevent (following golang binding

Bug#730798: ITA: ldc - LLVM D compiler

retitle 730798 ITA: ldc LLVM D compiler stop Package: wnpp Version: 0.9.1+hg1634-1 I'd like to help on this package and willing to adopt it. I intend to build an updated package and upload to the archive soon (=in the next couple of weeks hopefully), if there are no objections. Konstantinos

Bug#722104: Reproduced on GA-M68SM-S2 (AM2) with Radeon 7950 and hdmi monitor connected.

Since a couple of days, I experience exactly the same symptom here, but slighty newer kernels. 3.10 used to work fine, after the upgrade to 3.11 (3.11.8-1), onboard audio is not even detected (ALC888 chipset according to the manufacturer). I would gladly provide more info if needed. Konstantinos

Bug#727708: tech-ctte: Decide which init system to default to in Debian.

Hi TC and people, Another issue that might or might have not already been answered, that was triggered from seeing direct comparison metrics. Do we have some kind of a metric or some even personal experience with regards to which project has been the most friendly in accepting patches *from*

Bug#727708: init system question before the technical committee

Hi all, I'd just like to mentioned just a small(big? you decide) issue that I haven't seen mentioned yet from anyone. Against systemd. systemd has explicitly mentioned its Linux-only support. Sure, that affects kFreeBSD/Hurd now. But changing an init system should be done looking ahead *at

Bug#687642: gnat-4.6: libgnarl-4.6.a should be rebuilt with -fPIC, libaws FBTFS

Hi, (sorry for the delay, but for some reason I didn't receive this email) libgnarl-4.6.a is the *static* library, it should definitely not be compiled with -fPIC. The *shared* library, libgnarl-4.6.so, is already built with -fPIC. If you have time before I do, please investigate why

Bug#692557: libjogl2-java: FTBFS on armel/armhf, fixed in Ubuntu

Package: libjogl2-java_ Version: 2.0-rc8-1 Severity: serious Tags: patch The package has already been fixed in Ubuntu, please check their diff, I tested it on the Debian version and it happily built on armhf.

Bug#692499: arb: FTBFS on armhf [PATCH]

Package: src:arb Version: 5.3-4 Severity: important Hi, according to https://buildd.debian.org/status/package.php?p=arbsuite=sid arb fails to build from source on armhf (severity is not serious however as the package was never built on armhf before). The patch to fix the build failure is

Bug#691574: booth: FTBFS on some arches due to -Werror=cast-align

Package: booth Version: 0.1.0-1 Severity: important Tags: patch Booth fails on some arches when -Werror=cast-align warning is enabled, according to the status page: https://buildd.debian.org/status/package.php?p=boothsuite=sid Removing the cast-align warning from configure.ac fixes the build on

Bug#691333: qgis: FTBFS: on armel/armhf qreal maps to float not double [PATCH]

Package: qgis Version: 1.7.4+1.7.5~20120320-1.1 Severity: important Tags: patch Hi, On armel/armhf qreal is typedef'ed to float not double, that leads to a few packages failing to build. the attached patch implements (when #ifdef QT_ARCH_ARM) the missing methods and the package builds fine on

Bug#654594: util-vserver: FTBFS on armhf, undefined reference to `syscall'

On Tue, 2012-10-23 at 00:00 +0200, Hector Oron wrote: Hello, On Mon, Oct 22, 2012 at 09:43:18PM +0300, Konstantinos Margaritis wrote: Actually the bug isn't in util-vserver but in dietlibc, it's missing the syscall symbol. Reassigning to dietlibc. On armhf: /usr/lib/diet/lib

Bug#691179: trafficserver: FTBFS:

Package: src:trafficserver Version: 3.2.0-1 Severity: serious Tags: patch (tagged serious as the package used to build for armhf previously) In https://buildd.debian.org/status/package.php?p=trafficserversuite=sid In lulu.h barriers are defined only for x86 and x86_64, but not for arm. Well,

Bug#691179: trafficserver: FTBFS:

On Mon, 2012-10-22 at 19:13 +0200, Arno Töll wrote: thanks for the report, but I noticed that already. I reported the problem to upstream [1] where it is fixed already in trunk and proposed as a backport to their stable branch for 3.2.x. Note, upstream's fix [2] is slightly different to yours.

Bug#654594: util-vserver: FTBFS on armhf, undefined reference to `syscall'

reassign 654594 dietlibc thanks Actually the bug isn't in util-vserver but in dietlibc, it's missing the syscall symbol. Reassigning to dietlibc. Regards Konstantinos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#691032: libembperl-perl: FTBFS: -m32 is i386/amd64 only

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#691034: libembperl-perl: FTBFS: -m32 is i386/amd64 only

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#691035: libembperl-perl: FTBFS: -m32 is i386/amd64 only

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#691036: libembperl-perl: FTBFS: -m32 is i386/amd64 only

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#691037: libembperl-perl: FTBFS: -m32 is i386/amd64 only

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#691038: libembperl-perl: FTBFS: -m32 is i386/amd64 only

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#691039: libembperl-perl: FTBFS: -m32 is i386/amd64 only

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#691040: libembperl-perl: FTBFS, -m32 is not valid on non-x86 architectures.

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#691041: libembperl-perl: FTBFS, -m32 is not valid on non-x86 architectures.

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#691042: libembperl-perl: FTBFS, -m32 is not valid on non-x86 architectures.

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#691043: libembperl-perl: FTBFS, -m32 is not valid on non-x86 architectures.

Package: libembperl-perl Version: 2.5.0~rc2-1 Severity: serious Tags: patch According to https://buildd.debian.org/status/package.php?p=libembperl-perlsuite=sid the package fails on armel/armhf, mips/mipsel, s390 due to -m32 not being available on those platforms as a valid gcc flag. Please

Bug#690962: mess: FTBFS, please lower the number of parallel jobs from -j5

On Fri, 2012-10-19 at 21:08 +0200, Emmanuel Kasper wrote: If that OK I start ( number of CPU cores + 1 ) as the number of make jobs ? This is how we do it on the very similar mame package. I think it should work nicely. Regards Konstantinos -- To UNSUBSCRIBE, email to

Bug#690962: mess: FTBFS, please lower the number of parallel jobs from -j5

Package: mess Version: 0.146-3 Severity: important Currently in debian/rules make starts -j5. Currently the armhf autobuilders have only 1GB of RAM and starting 5 C++ jobs is a bit too heavy on the builders. Lowering it to eg. 3 or even 2 is a bit nicer, or if you would like, add some code to

Bug#690830: camitk: FTBFS on armhf, needs -fPIC

Package: camitk Version: 3.0.2-1 Severity: Important Tags: patch Hi, According to http://buildd.debian.org/status/package.php?p=camitksuite=sid camitk FTBFS on at least armhf and mipsel, and the fix is rather easy -at least it was tested to work on armhf, just add -fPIC in the CXXFLAGS. The

Bug#668121: cde: should be i386/amd64 only.

Declaring a package as arch: any is fine for the first attempts (until it's tried at least once on other arches, where it might actually build/work) but once it has been proven that there is no actual support for any other arch, and it would require substantial amount of work to port it, then it

Bug#690871: Love: FTBFS: missing build dependency glee-dev

Package: love Version: 0.8.0-2 Severity: serious Adding glee-dev to the build dependencies makes the package build again. Regards Konstantinos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#690005: simgear: FTBFS for different reasons

tags 690005 patch thanks Hi, At least with regards to the build failures by undefined references to SGMutex::SGMutex(), etc, the fix is quite easy and was tested to work on armhf, just add sgthreads and pthreads library to the CMakeFiles.txt. Regards Konstantinos diff -ruN

Bug#690753: rhmessaging: FTBFS on arm* (and other arches)

Package: rhmessaging Version: 0.16-1 Severity: Important Tags: patch For armel/armhf the following simple patch seems to work, the package builds and the tests pass. I assume similar fixes might be worth testing on mips/mipsel/sparc as well. Regards Konstantinos diff -ruN

Bug#689517: ocaml: Uses uname -m instead of DEB_BUILD_GNU_TYPE

Package: ocaml Version: 3.12.1-4 Severity: Important The configure script doesn't get the build triplet as an argument so it uses internally uname -m to get the arch, thus on a 32-bit chroot on a 64-bit system it reports x86_64. This leads to BNG_ARCH_amd64 being defined and the build fails when

Bug#687608: open-axiom: should not use -m32/-m64 flags in CXXFLAGS/LDFLAGS

Package: open-axiom Version: 1.4.1+svn~2626-2 Severity: Important Tags: patch The package fails to build on many arches, because configure erroneously tries to add -m32/-m64 in CXXFLAGS/LDFLAGS. This should be left out, IMHO, as after some quick tests, host_lisp_precision was equal to the

Bug#687612: FTBFS: openimageio: 64-bit atomics not in gcc-4.6 for some arches, builds ok with gcc-4.7

Package: openimageio Version: 1.0.5+dfsg0-1 Severity: Important The package FTBFS on many arches (arm*, mips*, powerpc and sparc) due to missing 64-bit atomics support in gcc-4.6. The package builds fine so you might consider changing that in build-depends or reassigning the bug to gcc-4.6, but I

Bug#687613: libplayer: build with -fPIC

Package: libplayer Version: 2.0.1-2.1 Severity: Important Tags: patch CFLAGS doesn't really get used in configure, trivial patch to fix this. Builds successfully on armhf after that. Regards Konstantinos diff -ruN libplayer-2.0.1/debian/rules libplayer-2.0.1.mine/debian/rules ---

Bug#641152: FTBFS: '.../libusb-java/usr/share/java/': No such file or directory

Hi, This package FTBFS on all arches other than amd64 because binary-arch target fails. The attached package fixes the binary-arch case. Regards Konstantinos diff -ruN libusb-java-0.8+ztex20090101/debian/rules libusb-java-0.8+ztex20090101.mine/debian/rules ---

Bug#687629: libjdic-java: please set JAVA_HOME correctly

Package: libjdic-java Version: 0.9.5-7 Severity: Serious Apart from the other FTBFS bugs, this also has to be fixed (fails on many arches), JAVA_HOME should be set to: JAVA_HOME=/usr/lib/jvm/java-6-openjdk-$(DEB_BUILD_ARCH) Please fix that also if you plan to fix the other bugs. Regards

Bug#687637: openvas-client-dfsg: FTBFS on all arches but i386

Package: openvas-client-dfsg Version: 20100705-4 Severity: Serious Tags: patch Hi, This package FTBFS on all arches other than i386 because binary-arch target fails. The attached package fixes those cases. Regards Konstantinos -- Konstantinos Margaritis konstantinos.margari...@freevec.org

Bug#657688: juman: FTBFS: cp: target `debian/juman-dic/usr/share/juman/dic' is not a directory

Hi, This package FTBFS on all arches other than i386 because binary-arch target fails. The attached package fixes the binary-arch case. Regards Konstantinos diff -ruN juman-7.0/debian/rules juman-7.0.mine/debian/rules --- juman-7.0/debian/rules 2012-01-20 04:18:22.0 + +++

Bug#687642: gnat-4.6: libgnarl-4.6.a should be rebuilt with -fPIC, libaws FBTFS

Package: gnat-4.6 Version: 4.6.3-6 Severity: Important According to: https://buildd.debian.org/status/package.php?p=libawssuite=sid libaws FTBFS at linking phase due to libgnarl-4.6 not built with -fPIC. I am unsure what to change in the gnat-4.6 source to test that so I don't have a patch for

Bug#687608: open-axiom: should not use -m32/-m64 flags in CXXFLAGS/LDFLAGS

On Fri, 14 Sep 2012 19:50:25 +0400 Игорь Пашев pashev.i...@gmail.com wrote: Hi, Konstantinos Could you please provide configure and build log, so I could see what's wrong. This issue is a little curious, because OpenAxiom was successfully compiled on amd64, i368 and freebsd-amd64.

Bug#671489: italc: incorrectly searches for Qt4 libs in lib64

Hi, After looking at this a bit... This is an excerpt from acinclude.m4:130 : QT_LIBS=`ls $QTDIR/lib64/libQt*.so 2 /dev/null` if test x$QT_LIBS = x; then QT_LIBS=`ls $QTDIR/lib/libQt*.so 2 /dev/null` if test x$QT_LIBS = x; then

Bug#687539: plexus-interactivity-api: missing jar from /usr/share/java

Package: plexus-interactivity-api Version: 1.0-alpha-6 Severity: important Please add --java-lib to the .poms file. Missing jar from /usr/share/java breaks build of other packages (maven2-core tested to fail because of plexus-interactivity-api, plexus-ciper and plexus-sec-dispatcher). Regards

Bug#687541: plexus-cipher: missing jar from /usr/share/java

Package: plexus-cipher Version: 1.5-2 Severity: important Please add --java-lib to the .poms file. Missing jar from /usr/share/java breaks build of other packages (maven2-core tested to fail because of plexus-interactivity-api, plexus-ciper and plexus-sec-dispatcher). Regards Konstantinos --

Bug#687542: plexus-sec-dispatcher: missing jar from /usr/share/java

Package: plexus-sec-dispatcher Version: 1.3.1-5 Severity: important Please add --java-lib to the .poms file. Missing jar from /usr/share/java breaks build of other packages (maven2-core tested to fail because of plexus-interactivity-api, plexus-ciper and plexus-sec-dispatcher). Regards

Bug#687559: diagnostics: tries to build stacktrace on armhf [PATCH]

Package: diagnostics Version: 0.3.3-1.3 Severity: Important At the moment, the package does not detect armhf triplet (arm-linux-gnueabihf) so it enables stacktrace in configure. This fails because _URC_NORMAL_STOP is not defined:

Bug#687368: libseccomp: package is i386 amd64 only

Package: libseccomp Version: 0.1.0-1 Severity: Important According to src/arch.c ~line 38: #if __i386__ .token = AUDIT_ARCH_I386, #elif __x86_64__ .token = AUDIT_ARCH_X86_64, #else #error the arch code needs to know about your machine type #endif /* machine type guess */ The

Bug#687317: getdp: package FTBFS on armhf [PATCH]

Package: getdp Version: 2.2.0-1 Severity: Important Tags: patch Ηι, Package FTBFS because it cannot find the proper paths for petsc and slepc. The reason is that armhf/armel (which this patch also covers in case the package is buildable there as well), use a different triplet than *-linux-gnu.

Bug#687098: package is arch: i386 amd64 only

Package: bcov Version: 0.2-1.2 Severity: serious Bug has already been reported in Ubuntu (LP:841468). bcov already supports only i386,amd64, please set the Architecture field accordingly. Regards Konstantinos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a

Bug#495889: ski: diff for NMU version 1.3.2-4.1

On Wednesday 29 February 2012 06:28:07 Nobuhiro Iwamatsu wrote: Hi, tags 495889 + pending thanks Dear maintainer, I've prepared an NMU for ski (versioned as 1.3.2-4.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. Do

Bug#632119: Chromium builds on arm with ld.bfd but not with gold. updated patch

Apparently this is a bug in gold for armel/armhf -will file a bug report there soon- as chromium builds and works fine if linked with the plain linker. The updated patch enables the build for armhf and most likely on armel as well. Working packages (tested) for armhf can be found here:

Bug#628253: libsfml: diff for NMU version 1.6+dfsg1-2.1

. + + -- Konstantinos Margaritis mar...@debian.org Fri, 03 Feb 2012 15:31:30 +0200 + libsfml (1.6+dfsg1-2) unstable; urgency=low * Add patch by Evgeni to build against gcc-4.6 (Closes: #625031) diff -u libsfml-1.6+dfsg1/debian/patches/series libsfml-1.6+dfsg1/debian/patches/series --- libsfml-1.6

Bug#639771: fritzing: diff for NMU version 0.6.3b+dfsg-3.1

this time by Nobuhiro. (Closes: #639771) + + -- Konstantinos Margaritis mar...@debian.org Thu, 02 Feb 2012 23:49:21 +0200 + fritzing (0.6.3b+dfsg-3) unstable; urgency=low * Removed redundant build-dependencies. diff -Nru fritzing-0.6.3b+dfsg/debian/patches/ftbfs_fix_for_armel_sh4.patch fritzing

Bug#645549: blcr: diff for NMU version 0.8.4-1.1

/debian/changelog 2011-10-12 18:42:47.0 + +++ blcr-0.8.4/debian/changelog 2012-02-03 02:12:06.0 + @@ -1,3 +1,10 @@ +blcr (0.8.4-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Actually add armhf in control file. (Closes: #645549). + + -- Konstantinos Margaritis mar

Bug#604947: midish: diff for NMU version 1.0.4-1.1

/changelog --- midish-1.0.4/debian/changelog 2010-10-31 10:25:39.0 + +++ midish-1.0.4/debian/changelog 2012-01-31 02:21:12.0 + @@ -1,3 +1,9 @@ +midish (1.0.4-1.1) unstable; urgency=low + + * Non-maintainer upload, fixes FTBFS. (Closes: #604947, #652177) + + -- Konstantinos

Bug#554280: fbxkb: diff for NMU version 0.6-1.1

(). + * Link to X11 to build with binutils-gold. (Closes: #554280) + + -- Konstantinos Margaritis mar...@debian.org Fri, 31 Jan 2012 13:46:19 +0200 + fbxkb (0.6-1) unstable; urgency=low * Initial Release. diff -u fbxkb-0.6/debian/rules fbxkb-0.6/debian/rules --- fbxkb-0.6/debian/rules +++ fbxkb

Bug#658118: squeak-vm: diff for NMU version 1:4.4.7.2357-1.1

-maintainer upload. + * Patch by Ricardo Salveti de Araujo ricardo.salv...@linaro.org, reenable +gcc optimizations on ARM again, remove -mno-fused-madd flag. Closes( #634240). + + -- Konstantinos Margaritis mar...@debian.org Tue, 31 Jan 2012 15:35:41 + + squeak-vm (1:4.4.7.2357-1

Bug#622011: openvas-client: diff for NMU version 2.0.5-1.1

. (Closes: #622011) + + -- Konstantinos Margaritis mar...@debian.org Tue, 31 Jan 2012 16:56:33 + + openvas-client (2.0.5-1) unstable; urgency=low * New upstream release diff -u openvas-client-2.0.5/debian/patches/00list openvas-client-2.0.5/debian/patches/00list --- openvas-client-2.0.5/debian

Bug#625198: drift: diff for NMU version 2.2.3-2.1

: #625198) + + -- Konstantinos Margaritis mar...@debian.org Tue, 31 Jan 2012 18:00:21 + + drift (2.2.3-2) unstable; urgency=low * Added README.Debian which explains how to rebuild DrIFT in case you diff -u drift-2.2.3/debian/rules drift-2.2.3/debian/rules --- drift-2.2.3/debian/rules

Bug#621926: gfarm: diff for NMU version 2.4.1-1.1

not support +=. (Closes: #621926). + + -- Konstantinos Margaritis mar...@debian.org Tue, 31 Jan 2012 19:01:26 + + gfarm (2.4.1-1) unstable; urgency=low * New upstream release. diff -Nru gfarm-2.4.1/debian/patches/09_change-shell.patch gfarm-2.4.1/debian/patches/09_change-shell.patch

Bug#622002: xoscope: diff for NMU version 2.0-3.2

. + + -- Konstantinos Margaritis mar...@debian.org Tue, 31 Jan 2012 18:52:33 +0200 + xoscope (2.0-3.1) unstable; urgency=medium * Non-maintainer upload. diff -u xoscope-2.0/debian/patches/series xoscope-2.0/debian/patches/series --- xoscope-2.0/debian/patches/series +++ xoscope-2.0/debian/patches/series @@ -2,0

  1   2   3   4   5   >