Package: xsever-xorg-video-vmware
Severity: serious
Version: 1:13.0.2-1
xsever-xorg-video-vmware is now failing to build on kfreebsd
checking for XATRACKER... no
configure: error: Package requirements (xatracker = 0.4.0) were not met:
No package 'xatracker' found
Consider adjusting the
Package: xserver-xorg-video-vmware
Version: 1:13.0.1-3
Severity: grave
xserver-xorg-video-vmware can no longer be installed in sid because of a
missing dependency.
root@debian:/xserver-xorg-video-vmware-13.0.1# apt-get install
xserver-xorg-video-vmware
Reading package lists... Done
Building
Tags 738382 +patch
Thanks
The debdiff at
http://debdiffs.raspbian.org/main/m/memcachedb/memcachedb_1.2.0-10%2brpi1.debdiff
was applied to make the package build in raspbian. It will probablly
make it build in debian too but this has not been tested. Whether or not
the package actually works
Tags 713671 +patch
Thanks
The fix for this issue that I just uploaded to raspbian can be found at
http://debdiffs.raspbian.org/main/h/hotkeys/hotkeys_0.5.7.4-0.3%2brpi1.debdiff
It seems that the file Changelog in the source tree is hardlinked to
debian/changelog, this may require some care
Tags 735764 +patch
thanks
I mnaged to modifidy the package so it would build, it would probablly
be better to use pkg-config but I dunno enough about cmake to do that.
I also fixed the clean target in debian/rules along the way.
Debdiff attached, no intent to NMU.
diff -Nru
Based on the patches for razorqt and various examples found by googling
I made player build. I have not tested it beyond that and I didn't find
any proper documention for the new parameters so i'm not positive it is
correct.
Debdiff atached and uploaded to raspbian. No intent to NMU in
Tags 733383 +patch
Thanks
After reproducing this failure locally and doing some digging in the
configure script I found that this FTBFS was caused by a change in
behaviour in GraphicsMagick-config.
On wheezy:
root@debian:/# /usr/bin/GraphicsMagick-config --ldflags
-L${exec_prefix}/lib
Package: gitg
Version: 0.2.7-1
Severity: serious
gitg-commit-view.c:1663:2: error: implicit declaration of function
‘gtk_source_style_scheme_get_style’ [-Werror=implicit-function-declaration]
style = gtk_source_style_scheme_get_style (scheme, current-line);
^
I initially ran into this error
Package: gtk+3.0
Version: 3.10.7-1
Severity: serious
Tags: patch
On one of the raspbian jessie autobuilders I ran into the following
error with gtk+ 3.0.
warning: failed to load external entity ../../../../examples/search-bar.c
../xml/gtkactiongroup.xml:160: parser error : Opening and ending
peter green wrote:
I've been doing some tests on this interestingly it failed for me much
earlier than on the buildd, maybe different systems give slightly
different ammounts of usable address space or something. Anyway
reducing optimisation levels etc doesn't seem to help, switching to
4.7
Package: icedtea-web
Version: 1.4.2-1
Severity: serious
x-debbugs-cc: debian-...@lists.debian.org
checking if sun.security.util.SecurityConstants is available... no
configure: error: sun.security.util.SecurityConstants not found.
make: *** [configure-stamp] Error 1
--
To UNSUBSCRIBE, email to
I've resolved this by including pre-built documentation and not
regenerating that at package build time. This fix requires a new
.orig.tar.gz file, and that needs help from ftp-masters to replace the
existing file.
I've just confirmed with the FTP team that replacing the existing file
is not
I've been doing some tests on this interestingly it failed for me much
earlier than on the buildd, maybe different systems give slightly
different ammounts of usable address space or something. Anyway reducing
optimisation levels etc doesn't seem to help, switching to 4.7 is
looking more
The package is also uploaded to mentors, but I won't request sponsorship
until the python-liblas source package is removed from unstable. (#738141)
I've just spoken to a memeber of the ftp team on irc and you have this
backwards, the normal thing to do is to upload the package doing the
Package: libreadline-ruby
Severity: serious
Tags: sid patch
Your package depends on libreadline-ruby. A recent version of the
libruby package (currently in sid but not yet in jessie) dropped the
provides of libreadline-ruby. I brought this up on #debian-ruby
(conversation pasted below) and it
Josue Abarca wrote:
I backported the patches from Paul to apply them to 1.1.0-1
and uploaded that new version.
It seems you only uploaded it to experimental, was that intentional?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Tags 713663 +patch
Thanks
I read the error message and noticed that the debian fatrat package
appears to be dynamically linked. So per the error message I defined
BOOST_ASIO_DYN_LINK. I also had to fix a load of other errors. The
attatched patch makes the package build, I have not tested it
Hideki Yamane wrote:
Attached patch would fix this FTBFS, could you check and consider to
apply it, please?
I notice your patch is based on the experimental version of the package.
Afaict (note: i'm not the maintainer of this package) uploading a
package based on the experimental version
Severity 650761 important
Thanks
ia64 is no longer a release architecture, so downgrading.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
The error mentioned in the bug report is trivial to fix, just specify
the python libdir manually in debian/rules
DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
export MOZ_PYTHON_LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH)
And bump the build-dependency on python-dev to = 2.7.5
Tags 713122 + patch
Tags 705157 + patch jessie sid
Severity 705157 serious
Thanks
The fix for 713122 is trivial, just change the build-dependency from
ghc6 | ghc to ghc (or if you really insist ghc | ghc6).
705157 (which already has a patch) now needs fixing in testing/unstable,
increasing the
Unless I missed something, only two packages remain. And the maintainers haven't
responded so far.
What would be a suitable delay for delayed-queue NMUs?
I see one of the two has now been MU'd, possiblly as a result of your mail.
By my reading of the guidelines you would be quite within
Package: qttools-opensource-source
Version: 5.2.0-8
Severity: serious
Version 5.2.0-8 of qttools-opensource-source failed
to build on the powerpc autobuilders with the following symbols
file mismatch.
- (arch=powerpc sparc)_ZN18qdesigner_internal22PropertySheetFlagValueD1Ev@Base
5.2.0
-
Package: transmission
Version: 2.82-1
Severity: serious
Tags: patch
transmission unconditionally build-depends on libsystemd-daemon-dev
which is only available on linux.
The attatched patch adjusts debian/control and debian/rules to make the
systemd stuff linux only. I have tested it builds
Package: iausofa-c
Version: 2013.12.02-1
Severity: serious
Your changelog states you have moved the package to non-free but it
seems you have only moved the binary packages to non-free and left the
source package in main. Presumablly this is a mistake.
--
To UNSUBSCRIBE, email to
Tags 713094 +patch
Thanks
I found a patch for this at https://bugs.launchpad.net/do/+bug/1097712
and used it to prepare an upload for raspbian. A debdiff can be found at
http://debdiffs.raspbian.org/main/g/gnome-do/gnome-do_0.9-1%2brpi1.debdiff
. No intent to NMU in debian.
--
To
Package: fenics
Severity: serious
Tags: jessie, sid
Fenics depends on ufc-doc. The version of the ufc source package in
jessie and sid no longer builds this binary package.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: libosl
Severity: serious
libosl builds on i386 seem to use a mixture of -march=native and
-march=pentium4, neither is appropriate for debian since i386 is
supposed to support much lower processors (not sure offhand what exactly
the minimum is supposed to be but I knot it's well below
Package: meep
Severity: serious
From the i386 build log for meep:
checking whether C++ compiler accepts -march=native... yes
checking for gcc architecture flag... -march=native
checking whether C++ compiler accepts -O3 -malign-double -fstrict-aliasing
-march=native... yes
Unfortunately the
Package: meep-openmpi
Severity: serious
From the kfreebsd-i386 build log for meep-openmpi:
checking whether C++ compiler accepts -march=native... yes
checking for gcc architecture flag... -march=native
checking whether C++ compiler accepts -O3 -malign-double -fstrict-aliasing
-march=native...
I just retested this and why still FTBFS but the error has changed
Ocamlopt src/vcg.ml
File src/vcg.ml, line 619, characters 10-22:
Warning 26: unused variable filter_up_to.
File src/vcg.ml, line 1:
Error: Some fatal warnings were triggered (1 occurrences)
make[1]: *** [src/vcg.cmx] Error 2
Package: mygui
Severity: serious
Tags: patch
http://buildd.raspbian.org/status/fetch.php?pkg=myguiarch=armhfver=3.2.0-3%2Bb1stamp=1387738789
-- Looking for FREETYPE...
-- Found PkgConfig: /usr/bin/pkg-config (found version 0.26)
-- checking for module 'freetype2'
-- found freetype2, version
Severity 729649 important
Thanks
cegui-m2k b-d's on non-available liblua5.1-expat-dev
which isn't built anymoreby lua-expat.
It's no longer built as a binary package in it's own right
but it does still seem to exist as a virtual package.
Afacit build-depening on virtual packages with only one
Tags 713126 +patch
Thanks
The attatched debdiff makes this package build in current sid. I have
not tested it beyond that. No intent to NMU.
diff -u gcj-4.6-4.6.4/debian/control.m4 gcj-4.6-4.6.4/debian/control.m4
--- gcj-4.6-4.6.4/debian/control.m4
+++ gcj-4.6-4.6.4/debian/control.m4
@@
tags 732405 +fixed-upstream
thanks
From a quick google this appears to be fixed upstream, unfortunately
the bug report does not appear to have a link to the fix.
https://rt.cpan.org/Public/Bug/Display.html?ShowHeaders=1;id=77087
--
To UNSUBSCRIBE, email to
Boris Pek wrote:
Hi,
I took the hint in the error message and added --add-missing. I also
made a small fix to the clean target. With these changes the package
built successfully. The debdiff of what I uploaded to raspbian is
attatched, I have no immediate intent to NMU in debian (though I
tags 731891 +patch
thanks
The build on the porterbox was successful, debdiff attatched, no
immediate intent to NMU.
diff -u gcc-4.4-4.4.7/debian/changelog gcc-4.4-4.4.7/debian/changelog
--- gcc-4.4-4.4.7/debian/changelog
+++ gcc-4.4-4.4.7/debian/changelog
@@ -1,3 +1,10 @@
+gcc-4.4 (4.4.7-5.1)
Package: gcc-4.4
Severity: serious
Tags: jessie, sid
In file included from ../../../../src/libgcc/../gcc/unwind-dw2.c:333:
../../../../src/libgcc/../gcc/config/mips/linux-unwind.h: In function
'mips_fallback_frame_state':
../../../../src/libgcc/../gcc/config/mips/linux-unwind.h:78: error: field
Package: cups-filters
Version: 1.0.42-1
Severity: serious
The latest upload of cups-filters failed to build on kfreebsd-*
filter/foomatic-rip/foomaticrip.c:159:6: error: conflicting types for 'gspath'
char gspath[PATH_MAX] = gs;
^
In file included from
I took the hint in the error message and added --add-missing. I also
made a small fix to the clean target. With these changes the package
built successfully. The debdiff of what I uploaded to raspbian is
attatched, I have no immediate intent to NMU in debian (though I may
change my mind later)
* debian/rules: Do not specify python include dirs in the call to CMAKE,
it causes a FTBFS because CMAKE can't find the correct includes. Since
CMAKE 2.8.11-1, CMAKE knows how to find multi-arched python by itself.
If you are going to be relying on functionlity introduced in a
Package: aghermann
Version: 1.0-2
Severity: serious
Your package build-depends on gcc = 4.7. This dependency is not
satisfiable on powerpc, s390x, sparc and ia64.
If you want to use a gcc version other than the default for an
architecture then you must depend on it directly (not via the gcc
peter green wrote:
I just uploaded a NMU for bespin to delayed/5.
There were no changes to the source itself, the only changes were to
use a version number ( 0.r1552+nmu1 ) which is compatible with 3.0
(native) and to rebuild against current sid (in particular against the
new kde-workspace
I just uploaded a NMU for bespin to delayed/5.
There were no changes to the source itself, the only changes were to use
a version number ( 0.r1552+nmu1 ) which is compatible with 3.0 (native)
and to rebuild against current sid (in particular against the new
kde-workspace).
Please tell me if
The full Globus Toolkit 5.2.5 should migrate to testing together.
However many of the updated packages got diverted to the new queue due
to package splits/renames done in order to support Multi-Arch.
This bug is filed to prevent the migration of globus-core before the
packages diverted to the
Package: tsdecrypt
Severity: serious
Tags: patch
Version: 8.0-1
tsdecrypt's build system appears to assume that the package is being
built with the intention of running it on the same machine it is being
built on. As such it uses -march=native and depending on detection code
sets several
Stephan Schreiber wrote:
block 730157 by 718047
thanks
This is likely bug#718047. Removing the --as-needed switch from the ld
invoke is the tentative workaround for that.
I just tried to reproduce the issue on merulo and the package failed
with a ld segfault but on a different file, I guess
Package: kdepimlibs
Severity: serious
Version: 4:4.11.3-1
X-debbugs-cc: debian-i...@lists.debian.org
/usr/bin/c++ -fPIC -g -O2 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W
This rc bug has been tagged pending for over 3 months now. Is there some
other problem that is blocking an upload?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reopen 697805
retitle 697805 gcc-4.(7|8) FTBFS on non-ubuntu based derivatives that
change output of lsb_release -is
severity 697805 normal
thanks
I just ran into this issue while updating gcc in raspbian. It is a real
bug IMO but it is more subtule than the original submitter realised. I
peter green wrote:
ia64/powerpc/s390x/sparc: unrecognized command line option
'-ftrack-macro-expansion=0'
This appears to be caused by the fact those architectures still have
gcc-4.6 as their default compiler. I see two possible fixes for this,
one is to check the gcc version and only pass
Package: dynare
Version: 4.3.3-4
Severity: serious
Tags: patch
While working on raspbian I discovered that dynare failed to build
because it was treating warnings as errors.
http://buildd.raspbian.org/status/fetch.php?pkg=dynarearch=armhfver=4.3.3-4stamp=1382380126
I was able to reproduce
Found 726009 1.00.0-3
Thanks
The good news is your most recent upload made yade build on i386.
The bad news is your package is still failing to build on most archictures
including several where it has built in the past.
Release architectures where your package is out of date:
Package: mumble
Severity: serious
Version: 1.2.3-349-g315b5f5-2.2
Tags: jessie, sid
zeroc-ice has recently moved from version 34 to 35. Muble still depends
on the old versions which is preventing those old versions being
decrufted and hence preventing zeroc-ice reentering testing (though
tags 723875 +patch
thanks
At
http://debdiffs.raspbian.org/main/g/gimp-plugin-registry/gimp-plugin-registry_5.20120621+rpi1.debdiff
you can find a debdiff for the upload I made to raspbian to fix several
libm link issues in gimp-plugin-registry including the one mentioned in
this bug.
Tags 713688 +patch
thanks
This was trivial to fix, just a matter of adding -lgobject-2.0 to the
list of libraries in an existing debian patch.
Debdiff attatched, no intent to NMU.
diff -Nru audtty-0.1.12/debian/changelog audtty-0.1.12/debian/changelog
--- audtty-0.1.12/debian/changelog
Moritz Muehlenhoff wrote:
Package: fpc
Severity: important
fp-units-gfx-2.6.2 uses svgalib, which is scheduled for removal
from the archive. Please disable it and drop the build-dep on
libsvga1-dev.
Sorry for not responding to this bug earlier
The practice adopted by the fpc package so-far
The code that fails is
LIBOSG_SHARE=`dpkg --get-selections|awk '{print $1}'|grep
libopenscenegraph[0-9]`
LIBOSG_VERSION=`dpkg -l $LIBOSG_SHARE |grep $LIBOSG_SHARE |sed 's/-/ /'
|awk '{print $3}'`
TMP1=`echo $LIBOSG_VERSION|awk -F '.' '{print $1}'`
TMP2=`echo $LIBOSG_VERSION|awk -F '.' '{print
Tags 723954 +patch
Thanks
I needed this built for raspbian so based on russ's hints I made a patch
which alters the pod files to make the package build successfully. In
total 20 pod files were modified (though in one directory I used sed to
fix the whole directory at once, so it's possible
Package: libfolia
Severity: grave
Tags: jessie.sid
It looks like ticcutils did yet another package rename from
libticcutils-dev to libticcutils2-dev. So this package needs another update.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
Package: ncbi-tools6
Severity: serious
Tags: patch
When trying to build ncbi-tools6 for raspbian it failed to build.
Further investigation by myself and JuN1x showed that it also failed to
build in both debian jessie amd64 and debian sid (I don't know which
architecture the sid test was done
Package: toonloop
Severity: serious
Version: 2.2.0-1
Tags: patch
Toonloop fails to build with boost 1.54
checking for boostlib = 1.35... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options... yes
checking whether the
Found 709749 1.7.28-1
Thanks
This also affects the version in testing, marking as such.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
This package was blocking a cruft removal in raspbian so I took a look.
First I fixed the error given in the bug report. This was caused by
unmatched bracket types in the Makefile. I guess make must have got
stricter.
Then I uploaded it to raspbian and discovered that it still had a
The ftbfs bugs caused by vala and a new gobject-introspection can easily be
fixed (at least in most cases) by switching to valac-0.20 which just got its way
into unstable. I just fixed bug #707378 this way by switching the build
dependency accordingly.
Unfortunately in the case of
The ftbfs bugs caused by vala and a new gobject-introspection can easily be
fixed (at least in most cases) by switching to valac-0.20 which just got its way
into unstable. I just fixed bug #707378 this way by switching the build
dependency accordingly.
Unfortunately in the case of valatoys
peter green wrote:
The ftbfs bugs caused by vala and a new gobject-introspection can
easily be fixed (at least in most cases) by switching to valac-0.20
which just got its way into unstable. I just fixed bug #707378 this
way by switching the build dependency accordingly.
Unfortunately
When I start sflphone-client-kde in the terminal even after a fresh
install I get this:
Can you clarify what exactly you mean by after a fresh install? Did
you reinstall all of debian or just the package? if the latter did you
purge the package before reinstalling and did you test with a clean
Anton Gladky wrote:
Hi Peter!
Thanks a lot for that! I have tried yesterday to fix the problem,
but could not manage that.
You, probably, forgot to attach the patch. Could you, please, do it?
Done.
Thank you,
Anton
2013/8/6 peter green plugw...@p10link.net:
Tags 717034 +patch
Tags
Tags 717034 +patch
Tags 718545 +patch
Thanks
Attatched is a patch that fixes the build failure by forcing the occ
include directory from debian/rules. The patch also contains a fix to
the clean target.
I have tested that the package builds succesfully with this patch, that
the resulting
I just ran across this bug (because of perlipq having unsatisfiable
build-depenencies in testing) and it seems it has been closed in the
version currently in wheezy and jessie but not in the version currently
in sid. It seems that the package in testing added breaks for
squeeze-wheezy updates
Guillem Jover wrote:
Package: fp-compiler-2.6.2
Version: 2.6.2-2
Severity: serious
Hi!
This package is no longer installable with the recent binutils upload
which has started providing binutils-gold, with fp-compiler-2.6.2 both
Depending on binutils and Conflicting on binutils-gold.
Here's
Ok I did some further tests. I built the two reverse build dependencies
of liblas-dev with my new version, checked that the resulting packages
installed successfully and checked that I could successfully import the
python modules.
As a result of these tests I have uploaded the NMU, final
peter green wrote:
Ok I did some further tests. I built the two reverse build
dependencies of liblas-dev with my new version, checked that the
resulting packages installed successfully and checked that I could
successfully import the python modules.
As a result of these tests I have uploaded
Package: liblas-dev
Severity: serious
Tags: patch
geotiff has recently switched from libtiff5-dev to libtiff5-alt-dev to solve a
build-dependency conflict that cropped up in grads during the gd transition.
Unfortunately this has made the dependencies for liblas-dev unsatisfiable and
the
I took a look at this one because I thought (incorrectly) that we needed to
rebuild the package for a transition in raspbian.
Fixing the failure in this bug report was easy enough and i've attached a patch.
Unfortunately at least in raspbian jessie the package then goes on to fail with.
Specifically the cause seems to be a breaks in openjdk-7-jre-headless.
root@plugwash:/php5-5.4.4# apt-get install icedtea-7-plugin
icedtea-netx openjdk-7-jre
Reading package lists... Done
Building dependency tree
Reading state information... Done
openjdk-7-jre is already the newest
I needed to rebuild this in raspbian for a transisition so I hacked up a
patch to force the package to use automake 1.11
http://debdiffs.raspbian.org/main/g/gearman-interface/gearman-interface_0.13.2-2.1+rpi1.debdiff
I suspect there is a better way to fix this but this patch provides an
Version: 1.1.0
The new ersion was built successfully on all release architectures
except ia64 (which does not have ghc available).
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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
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
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
Package: textworks
Version: 0.5~svn1035-1
Severity: serious
configuring default paths for TeX binaries as:
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
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
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
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-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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
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
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
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
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
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
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
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
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
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 http://gnu.org/licenses/gpl.html
This is free software: you are free to change and
Note: adding debian-arm to cc for feedback from other porters.
Jonathan Nieder wrote:
Hi Peter,
peter green wrote:
Patch to make the package use bfd rather than gold on armel and armhf is
attached. I may or may not upload this as a NMU.
If you'll have time to continue working
shawnland...@gmail.com wrote:
It works when built with gold 2.23
Is anyone working on either getting that into wheezy (if it's a bugfix
release that is likely to pass the release teams requirements) or to
backport the required fixes?
--
To UNSUBSCRIBE, email to
I can confim that using bfd instead of gold fixes the issue on armhf.
armel seems to be sufering from the same issue but I have not yet tried
a build with bfd on armel.
I will do an armel (but on armv7 hardware, I don't have any armv4t or
armv5 hardware to test on and all my armv6 stuff is
1001 - 1100 of 1819 matches
Mail list logo
