package: gstreamer1.0-plugins-bad
version: 1.4.3-2
severity: grave
tags: patch
We received a report in raspbian, that gmediarender was segfaulting on
startup. Further investigation by the original reporter showed that it
only happened if gstreamer1.0-plugins-bad was installed.
https://bugs.la
On 04/02/15 05:05, Andreas Beckmann wrote:
Package: fpc
Version: 2.6.4+dfsg-4
Severity: serious
Please provide a justification for the severity.
Adding the Breaks to fp-units-rtl-2.6.4 is sufficient
It's also wrong. The conflict between the freepascal 2.6.0 packages in
Debian wheezy and th
Matthias Klose wrote:
there exist several workarounds for it (lowering the
optimization, using gcc-4.8, ...).
Disabling stack protector also seems to result in a succesful compile
(reducing it from strong to regular does not).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian
peter green wrote:
Matthias Klose wrote:
there exist several workarounds for it (lowering the
optimization, using gcc-4.8, ...).
Disabling stack protector also seems to result in a succesful compile
(reducing it from strong to regular does not).
And another workaround is to use -marm
Package: pnp4nagios
Version: 0.6.24+dfsg1-3
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: arm64
Your package FTBFS on arm64 due to outdated config.sub/guess. This is a
regression and arm64 is now a release architecture hence the serious
severity.
Version 0.6.19-1 w
Sebastian Ramacher wrote:
there was a request to change the handling of the Raspberry Pi in the
libav package. Could you please explain the changes applied to the
Raspbian version?
In raspbian we have a checker that runs after all our autobuilds (and I
manually run a similar check when I do man
Sebastian Ramacher wrote:
Thank you for the explanation. What about the attached patch? [1]
I've looked through the code and the only place where --enable-runtime-cpudetect
makes a difference is on powerpc (libavutil/ppc/cpu.c). Special handling for
Raspbian should not make a difference. Reinha
Reopen 782976
Thanks.
On 24/04/15 22:49, Jonathan Wiltshire wrote:
On Mon, Apr 20, 2015 at 02:17:25AM +0100, peter green wrote:
Release team: can you clarify whether you intend to actually remove kfreebsd
from the jessie suite of the official archive before/during the jessie
release
Package: arpon
Version: 2.7.2-1
Arpon failed to build in raspbian stretch with a failure on missing
"dnet.h". Investigation shows that it looks up the distribution name
using lsb-release and if it's "Ubuntu" or "Debian" or "LinuxMint" it
inludes dumbnet.h, otherwise it includes dnet.h . This c
unmerge 766795
reassign 766795 afterstep
tags 766795 -wontfix -patch -jessie-ignore
retitle 766795 afterstep not binnmu safe
thanks.
Niels Thykier wrote:
Hi Robert, Simon and Axel,
It is not possible for debhelper to provide a *policy compliant*
link-doc *between arch:all and arch:any* packages
Sebastian Ramacher wrote:
I've applied your patch, tweaked it to use --derives-from rather than --is
implemented this change, written a changelog entry (which may be more
verbose than actually needed, feel free to cut it down if you want when
bringing the change into Debian) and am now running a
Note: not wearing any partciular hat in this message, opinions are my own.
Helmut Grohne wrote:
Package: src:libsigsegv
Version: 2.10-4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
libsigsegv FTCBFS for arm64.
Can you confirm that FTCBFS stands for "fails to cross build from sou
Daniel Schepler wrote:
Version: 7u71-2.5.3-2
This isn't limited to the testing/unstable version of openjdk-7. I just
encountered it with while merging the raspbian changes into wheezy's
openjdk-6 and I strongly suspect it affects all versions of openjdk-6
and openjdk-7 in all releases of Debia
Package: db5.3
Version: 5.3.28-9
Severity: serious
Tags: jessie
x-debbugs-cc: debhel...@packages.debian.org
The version of db5.3 that just migrated to testing build-depends on
debhelper >= 9.20141221~ but jessie only has 9.20141022 . This means
that db5.3 cannot be built in jessie.
I notice t
Package: condor
Condor started failing to build on raspbian after we started identifying
as ourselves rather than as Debian. An example of such a failure can be
seen at.
http://buildd.raspbian.org/status/fetch.php?pkg=condor&arch=armhf&ver=8.2.1~dfsg.1-1&stamp=1406013132
CMake Error at exter
Package: evolution-mapi
Severity: serious
Debian policy requires that debian packages are buildable within the
same release. Your package build-depends on libmapi-dev (>= 1:2.2).
libmapi-dev is provided by source package openchange which is at version
1.2.1-1 in testing. The new version of op
I have uploaded a libbs2b NMU to delayed/5 with the attatched debdiff.
Please tell me if you have any objections.
diff -Nru libbs2b-3.1.0+dfsg/debian/changelog
libbs2b-3.1.0+dfsg/debian/changelog
--- libbs2b-3.1.0+dfsg/debian/changelog 2011-07-25 17:43:43.0 +
+++ libbs2b-3.1.0+dfsg
Package: dcfldd
Version: 1.3.4.1-4
Severity: important
Tags: patch
Your package is failing to build on arm64 due to outdated
config.sub/guess. You already have autotools-dev in your build-depends
but don't appear to be actually using it. Given that -2.1 succeeded and
reading the changelog I pr
This isn't a bug in evolution-mapi,
It's a bug in the same sense that a FTBFS due to a bug in a compiler or
other tool is a bug. The root cause isn't in your package but
nevertheless your package is unfit for release until/unless it is dealt
with.
I don't think this is a useful use of the
I've just uploaded a gle NMU to the attatched debdiff to delayed/5 to
make gle use config.sub and config.guess from autotools-dev at build
time and hence fix the build failure on arm64.
I did not implement doko's later suggestion of a full autoreconf because
it carries a greater risk of regres
Package: nodejs
Severity: serious
Version: 0.10.29~dfsg-1.1
nodejs is failing to build with failure of the test "test-crypto-stream.js"
http://buildd.raspbian.org/status/fetch.php?pkg=nodejs&arch=armhf&ver=0.10.29~dfsg-1.1&stamp=1427831511
[02:22|% 13|+ 82|- 0]: release test-crypto-stream
This version of openjdk-7-doc doesn't contain any files other than the
copyright file and the changelog. The version in testing (7u75-2.5.4-2) is ok.
The underlying bug has been known for over 2 years, basically if the
arch all packages for openjdk is built on anything other than a handful
of
On 06/04/15 16:41, Jérémy Lal wrote:
That looks less subject to changes in openssl... will fix the patch using this
version instead.
Is something holding up an upload? are you aware that the jessie release
is looming?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
w
Package: debian-installer-netboot-images
Severity: serious
The RC policy states "Packages must be buildable within the same
release.". In this context I interpret "buildable" as buildable from
actual sourcecode (not just package together) and "the same release" as
the collection of stuff that
Release team: theres a question for you at the end of the mail.
On 20/04/15 00:49, Cyril Brulebois wrote:
peter green (2015-04-20):
Package: debian-installer-netboot-images
Severity: serious
The RC policy states "Packages must be buildable within the same release.".
In this
reopen 792685
tags 792685 +jessie
thanks
You closed the bug in a nonexistant version. Furthermore the bug isn't
"fixed" per-se it's just not applicable to stretch/sid (because we don't
support direct upgrades from wheezy to stretch/sid). The correct way to
indicate that a bug is not applicabl
package: rss2irc
version: 1.0.6-3
severity: serious
tags: sid stretch
according to
https://buildd.debian.org/status/package.php?p=rss2irc&suite=unstable
rss2irc build-depends on missing:
- amd64:libghc-irc-dev (< 0.6)
packages.debian.org confirms that the version of libghc-irc-dev in sid
and
tags 803312 +patch
thanks
mathgl fails to build from source in unstable/amd64:
I just fixed this in raspbian, it was a simple case of a missing include.
Debdiff at http://plugwash.raspbian.org/mathgl_2.3.3-3+rpi1.debdiff no
intent to nmu in Debian.
On 29/09/15 21:05, peter green wrote:
On further investigation it appears that libmarble has moved
completely to qt5.
In raspbian I disabled libmarble support in calligra. A debdiff can be
found at.
http://debdiffs.raspbian.org/main/c/calligra/calligra_2.8.5%2bdfsg-1.2%2brpi2.debdiff
I just took a look at this failure, many of the errors were caused by a
couple of missing #includes
--- llvm-toolchain-3.4-3.4.2.orig/polly/lib/ScheduleOptimizer.cpp
+++ llvm-toolchain-3.4-3.4.2/polly/lib/ScheduleOptimizer.cpp
@@ -25,6 +25,8 @@
#include "isl/options.h"
#include "isl/schedule.h"
Package: libsignon-glib
Severity: serious
Your package failed to build on all architectures other than amd64. This
is blocking the build of telepathy-accounts-signon which in turn
libktpcommoninternals9 installable in debian sid on all architectures
other than amd64.
The fix is trivial, just
Package: ktp-call-ui
Version: 0.9.0-2
Severity: serious
The version of your package in sid build-depends on
libktpcommoninternalsprivate-dev which is no longer built by the
ktp-common-internals source package in sid.
It looks like you need to upload the experimental version of this
package t
Package: krfb
Version: 4:15.04.2-1
Severity: serious
krfb build-depends on libktpcommoninternalsprivate-dev which is no longer built
by ktp-common-internals
This applies to both versions 4:15.04.2-1 and 4:15.08.3-1 of krfb.
This blocks the ktp-common-internals transition.
Package: apt
Version: 1.1.3
Severity: grave
When running apt in a Debian stretch armhf chroot on my odriod u2 DNS
resoloution fails. ping is able to resolve the hostname.
root@odroidu2:/# apt-get update
Err:1 http://mirror.bytemark.co.uk/debian stretch InRelease
Could not resolve 'mirror.byt
On 08/12/15 09:42, Julian Andres Klode wrote:
You might want to try running the ping as the _apt user and check
if that works. Maybe the _apt user does not have access to
/etc/resolv.conf?
Indeed that seems to be the issue, the resolv.conf in the chroots in
question is not world readable for
On 25/09/15 21:57, Edmund Grimley Evans wrote:
Does anyone here have any experience of mixing Fortran and C?
A couple of (possibly) related bug reports:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774618
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800040
Right.
I don't use for
On 27/09/15 09:05, Edmund Grimley Evans wrote:
peter green:
From the ppc64 build log (s390x was much the same).
Thank you for taking the trouble to look at the build logs; I just saw
that it was "Installed" and naively assumed it had worked!
Perhaps then the archite
Package: htslib
Severify: important
Tags: patch
htslib is failing to build in Debian armhf and raspbian.
I reproduced the bug locally in a raspbian stretch environment and got
the following backtrace.
root@odroidu2:/htslib-1.2.1# gdb --args test/sam test/ce.fa
GNU gdb (Raspbian 7.10-1) 7.10
C
We patched this issue in raspbian stretch. Unfortunately there now seems
to be a new issue.
http://buildd.raspbian.org/status/fetch.php?pkg=calligra&arch=armhf&ver=1%3A2.8.5%2Bdfsg-1.2%2Brpi1%2Bb2&stamp=1443503934
make[1]: Entering directory '/«BUILDDIR»/calligra-2.8.5+dfsg'
dh_install --list-m
Reassign 789670 python-pies
Fixed 789670 2.6.7-0.1
Thanks
The filing of this bug against multiple packages seems to be confusing
version tracking/britney. Reassigning the bug to be filed just against
the package that fixed it.
Package: pythia8
Severity: serious
Tags: patch
x-debbugs-cc: jcri...@debian.org
pythia8 depends on liblhapdf0 which has been replaced by liblhapfd0v5.
What I find strange is that pythia8 doesn't seem to build-depend on any
liblhapdf development packages. Instead it seems to build against it's
Package: i2c-tools
x-debbugs-cc: david.bod...@met.no
x-debbugs-cc: se...@raspberrypi.org
While dealing with a bug report in raspbian (which i'm pretty sure was
user error, using the wrong version of the raspberry pi foundation's
repo) I noticed that the raspberry pi foundation had a version of
After a discussion in #debian-python, it appeared to make sense to
package this and patch it so its where() function returns the location
where Debian is already providing CA certificates. This will be easier
than having to patch every python package that depends on certifi.
If you do that please
Package: libc6
Version: 2.21-0experimental1
I had an expermimental chroot on a system that happened to be running an
old kernel. I got an error message about needing a 2.6.32 kernel which
was strange as I already had a 2.6.32 kernel.
Reading the preinst revealed
# The GNU libc requir
Severity 794724 grave
tags 794724 +stretch sid
thanks
The libtinyxml transition has now happened in stretch and sid. This bug
needs to be fixed so that crtmpserver-dev is installable again and
crtmpserver-libs does not depend on obsolete packages.
Package: sdformat
Severity: serious
x-debbugs-cc: ignition-ma...@packages.debian.org
sdformat build-depends on libignition-math2-dev. This is provided by the
source package ignition-math2 which has never built succesfully on armel
or mips (it is failing with a test failure, I wonder if it is a
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
There were problems with using psi4 built with gcc-4.9 with a gcc-5
libstdc++6. As a result a breaks was added to libstdc++6 and psi4 was
binnmu'd.
However the binnmus on arm64 and ppc64e
Package: openni
Version: 1.5.4.0-13
Severity: important
In raspbian we run checks on built debs for armv7 tagged binary
packages. Your package was detected by these checks and on further
investigation. it seems that the following flags for all arm builds
(whether Debian armel, Debian armhf or
Tags: gfs2-utils +stretch
Thanks
I ran into this package trying to get a transition to go through in
raspbian stretch. After attacking some issues with build-dependencies on
obsolete packages and with the clean target not cleaning up properly I
ran into the same error that is given in this bug
Package: mysql-workbench
Version: 6.3.4+dfsg-2
Severity: serious
When building mysql-workbench on arm*, ppc* and s390x there are errors like.
/«BUILDDIR»/mysql-workbench-6.3.4+dfsg/library/sql.parser/source/ctype-utf8.cpp:
In function 'int mysql_parser::hexlo(int)':
/«BUILDDIR»/mysql-workbench
Package: kblackbox
Version: 4:15.08.0-1
Severity: serious
Tags: patch
kblackbox build-depends on libkdegames-dev (>= 4:14.12.2) .
libkdegames-dev is no longer build by the kdegames source package.
In raspbian stretch simply changing the build-dep resulted in a
successful build, I assume it wi
Package: kbreakout
Version: 4:15.08.0-1
Severity: serious
Tags: patch
kbreakout build-depends on libkdegames-dev (>= 4:14.12.2) . libkdegames-dev is
no longer build by the kdegames source package.
In raspbian stretch simply changing the build-dep to libkf5kdegames-dev
resulted in a successful
Package: python-biopython
Severity: serious
Tags: stretch
The release policy says that "packages must be buildable within the same
release". Your package build-depends on python3-mysqldb which is not in
testing.
To make your package releasable either bug 801112 needs to be fixed so
that pyth
On 14/10/15 11:33, Andreas Tille wrote:
To make your package releasable either bug 801112 needs to be fixed so that
I guess you mean s/801112/775254/ here, right?
Yeah, must have copy/pasted the wrong bug number.
Package: libexchangemapi-1.0-dev
Version: 3.18.0-3
dep: evolution-data-server-dev (>= 3.18.0) [not alpha, kfreebsd-amd64,
kfreebsd-i386, powerpcspe, sh4, x32]
dep: evolution-dev (<< 3.17) [not alpha, powerpcspe, sh4, x32]
It's not really possible to satisfy both of those at once...
Package: psi4
Version: 1:0.3-1
Severity: serious
The last three uploads of your package (0.3-1, 0.3-2 and 0.3-3) have all
failed on mips with testsuite timeouts.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Libstdc++6 declares a breaks on python3-taglib (<= 0.3.6+dfsg-2+b2),
presumablly as part of the big c++ ABI transition. However the binnmu
versions are out of sync across architectures lea
According to Joachim's comment on the upstream bug this was fixed in
1.0.0.0 . Should this be marked as fixed in version 1.0.0.0-1 in Debian?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
There is some confusion regarding this bug report so let me clear a few
things up.
Freepascal does not by default link dynamically against pascal code.
There has been some experimental suport in the compiler for a while but
I don't think anyone has ever seriously worked through the distro-leve
On 17/06/15 19:06, Sven Joachim wrote:
Source: fpc
Version: 2.6.4+dfsg-6
The file fpcsrc/packages/ncurses/src/form.pp declares the objects
_nc_Default_Form and _nc_Default_Field:
,
| (* Default objects *)
| {$ifndef darwin}
| _nc_Default_Form : PFORM;cvar;external;
| _nc_Default_Field
tags 787378 +patch
thanks
Googling for e_book_client_connect_sync brings us to
https://developer.gnome.org/eds/stable/eds-EBookClient.html#e-book-client-connect-sync
Which says
"The /|wait_for_connected_seconds|/ argument had been added since 3.16,
to let the caller decide how long to wait fo
tags 787390 +patch
thanks
make[4]: Entering directory '/«PKGBUILDDIR»/kde/build'
[ 18%] Building CXX object src/lib/CMakeFiles/qtsflphone.dir/call.cpp.o
cc1plus: error: /usr/include/qt4/KDE: No such file or directory [-Werror]
cc1plus: all warnings being treated as errors
make[4]: *** [src/lib/C
This may need a binNMU:
haskell-trifecta (1.4.3-1 to 1.5.1.3-4)
Maintainer: Debian Haskell Group
9 days old (needed 5 days)
libghc-trifecta-dev/ppc64el unsatisfiable Depends:
libghc-charset-dev-0.3.7.1-1690c
libghc-trifecta-dev/ppc64el unsatisfiable Depends:
libghc-comonad-
Severity 754681 important
Thanks
kfreebsd is no longer a release architecture.
Package: pjproject
Version:**2.4~dfsg-1
Severity: serious
Openssl in stretch/sid has dropped the SSLv3 functions. This makes your package
fail to build (at an earlier point in the build than previously reported build
failures
gcc -o ../bin/pjlib-test-x86_64-pc-linux-gnu \
output/pjlib-t
Tags 804605 +patch
thanks
openssl.o: In function `ssl_select_method':
/heirloom-mailx-12.5/openssl.c:220: undefined reference to `SSLv3_client_method'
collect2: error: ld returned 1 exit status
Makefile:92: recipe for target 'mailx' faile
I just fixed this in raspbian, debdiff at
http://debd
Tags 804603 +patch
thanks
The package fails to build, as openssl have dropped sslv3 support:
./.libs/libcouriertls.a(libcouriertls.o): In function `tls_create':
/courier-0.73.1/libs/tcpd/libcouriertls.c:530: undefined reference to
`SSLv3_method'
collect2: error: ld returned 1 exit status
Makefi
Tags 804604 +patch
thanks
socket.o: In function `SSLOpen':
/fetchmail-6.3.26/socket.c:917: undefined reference to `SSLv3_client_method'
collect2: error: ld returned 1 exit status
Makefile:699: recipe for target 'fetchmail' failed
make[3]: *** [fetchmail] Error 1
I just fixed this in raspbian,
I think we can make it Debian specific until it gets integrated
upstream.
I took the diff submitted as a pull request upstream, applied it to the
source package from debian (which required some path tweaks and
defuzzing) and uploaded it to raspbian. Debdiff at
http://debdiffs.raspbian.org/
Tags 804611 +patch
thanks
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-D_GNU_SOURCE -Wall -Wno-parentheses -DHAVE_CONFIG_H -I. -D_FORTIFY_SOURCE=2
-Wl,-z,relro -o socat socat.o libxio.a -lwrap -lrt -lutil -lssl -lcrypto
libxio.a(sslcls.o): In function `sycSSLv3_client
Package: libapache2-mod-wsgi-py3
Version: 4.3.0-1
Severity: serious
Tags: stretch sid
x-debbugs-cc: debian-pyt...@lists.debian.org
I run a derivative called raspbian and I noticed our auto-binnmuer was
repeatedly binnmuing mod-wsgi. Further investigation reveealed that
every time it was rebuilt
Package: light-locker
Severity: serious
The latest upload of light-locker added a build-dependency on
libsystemd-login-dev .
libsystemd-login-dev is no longer built by the systemd source package
and is not available in testing.
Package: lvm2
Version: 2.02.133-1
Severity: serious
Tags: patch
Your package build-depends on libcorosync-dev which is no longer built
by the corosync source package.
I replaced the build-depends on libcorosync-dev with
libcorosync-core-dev and tried a build in a raspbian stretch-staging
env
Tags 741804 -patch
Thanks
This was blocking a transition in raspbian stretch and I decided to take
a look to see if I could fix it before resorting to removal (since
raspbian doesn't have an unstable I don't like to remove stuff from
raspbian testing that is still in Debian unstable).
I appl
Package: opendnssec
Severity: important
Tags: patch
Opendnssec was being repeatedly binnmu'd in raspbian by our
autobinnmuuer because one of it's binaries was uninstallable. Looking at
the dose output revealed the following.
package: libhsm-bin
version: 1:1.4.6-1+b16
architecture: armhf
es
tags 706111 +wheezy
Thanks
Failure to upgrade from squeeze is not rc for jessie.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: postgresql-common
Version: 160
While troubleshooting a build failure of postgis on raspbian I
discovered /usr/share/postgresql-common/supported-versions was returning
9.3. Further investigation showed that the script was failling to
identify the distribution and falling back to an app
Just to inform you we have also encountered this error in raspbian.
http://buildd.raspbian.org/status/fetch.php?pkg=amarok&arch=armhf&ver=2.8.0-2.1%2Bb1&stamp=1410479588
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
Package: openjdk-7
Version: 7u65-2.5.2-3
x-debbugs-cc: debian-...@lists.debian.org
openjdk-7 is failing to build on the official arm64 autobuilders yet
building successfully on the debian-ports arm64 autobuilders. Version
7u65-2.5.2-3 failed with.
/«PKGBUILDDIR»/build/bootstrap/jdk1.6.0/bin/
Tags 767759 -moreinfo
Thanks
peter green wrote:
The package is now uploaded and built on all release architectures
except mips. On mips it's currently sitting in needs-build.
The package is now built successfully on all release architectures
--
To UNSUBSCRIBE, email to debian-bugs-dist
Severity 768054 normal
Tags 768054 moreinfo
Thanks
Petter Reinholdtsen wrote:
Package: fp-units-multimedia
Version: 2.6.4+dfsg-4
Severity: serious
User: debian-...@lists.debian.org
Usertags: debian-edu
We discovered this when testing package upgrades of the Debian Edu
tasks. The upgrade of the
Holger Levsen wrote:
Hi Paul,
first of all, I don't think a package can just "say" that it only can be
upgraded by "apt-get dist-upgrade" and not "apt-get upgrade" but it's early
and I'm still sleepy, so I cannot give you a reason like "policy 1.2.3" :/
Can someone enlighten me please?
seco
Paul Gevers wrote:
On 07-11-14 23:48, peter green wrote:
One thing that is almost certainly a factor is that wheezy's freepascal
can't remain installed on jessie, not because of anything to do with
jessie's freepascal package but because wheezy's freepascal package
con
Found 765272 1.7.7-4
Tags 765272 +patch
Thanks
The changelog for version 765272 claims
* debian/rules:
- call xdt-autogen before running configure to regenerate
config.{guess,sub} and gain support for new architectures closes:
#765272
However the package still FTBFS on arm64 and when
Yves-Alexis Perez wrote:
Since we are now post-freeze bugs should be fixed in a minimal way
and
as such adding an autoreconf at this point would be frowned upon. As
such for jessie I propose using the autotools_dev feature in dh to
update config.sub and config.guess without autoreconfing.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
I'm seeking approval for fixing the arm64 build failure in xfce4-notes-plugin.
The package FTBFS due to outdated config.sub/guess.
The maintainer doesn't have a problem with the changes but
Package: ftp.debian.org
A libphobos-dev dependency package was introduced in gcc-defaults 1.133,
however the architecture list for it was incorrect. The architecture
list was corrected in the next upload but the old binaries are still
present and are blocking migration to testing. Please remov
Package: tightvnc
Version: 1.3.9-6.4
Severity: important
Tightvnc FTBFS on arm64, the cause is some missing logic in the build
system to deal with it. (the build system in question seems to need to
know about each architecture explicitly). Ubuntu has had a fix for some
time* and I just took th
Package: python-zmq
Version: 14.3.1-1
Severity: important
User: debian-...@lists.debian.org
Usertags: arm64
x-debbugs-cc: debian-...@lists.debian.org
Python-zmq (versions 14.3.1-1 and 14.4.0-1) FTBFS on the official
"arm-arm" arm64 autobuilders. The same versions succeeded on the
debian-ports a
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu lhapdf_5.9.1-3 . arm64 . -m "Rebuild against octave 3.8"
The lhapdf package on arm64 was actually built against octave 3.8, unfortunately
it's not installable because octave declares Bre
Package: incron
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: arm64
incron FTBFS on arm64 with the following error.
In file included from icd-main.cpp:33:0:
inotify-cxx.h:40:34: fatal error: sys/inotify-syscalls.h: No such file or
directory
#include
Looking at th
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package tightvnc
This upload of tightvnc adds arm64 support to the packages build system. The
code is all behind conditionals so it shouldn't affect other architectures.
Thi
Ola Lundqvist wrote:
Hi
Sorry for not responding until now. The package is up for adoption so
NMU is most welcome.
Thanks, uploaded.
Final debdiff attatched, the only difference to the one proposed in the
original mail is some changelog tweaks to note that it's an upload with
the maintai
Thanks for doing the changes to recognise new architectures like
arm64. However, there's another bug to fix to fix FTBFS on arm64. The
code in libacpi.c is buggy, and assumes that Linux will always have
sysctl(). sysctl is strongly deprecated according to the man page, and
it seems it is not supp
Jonathan Wiltshire wrote:
Control: tag -1 moreinfo
On Sun, Nov 02, 2014 at 01:55:30PM +, peter green wrote:
This upload of tightvnc adds arm64 support to the packages build system. The
code is all behind conditionals so it shouldn't affect other architectures.
This is needed to
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
When looking through the list of packages that are uninstallable in arm64
testing I belive the following TPU binnmus are appropriate towards the goal
of pushing the list of uninstallable arch
Package: evolution-data-server
Version: 3.12.5-2
Tags: patch
User: debian-...@lists.debian.org
Usertags: arm64
evolution-data-server recently added a build-depends on
libphonenumber6-dev [linux-any]. lihphonenumber6-dev is built from the
source package libphonenumber
Unfortunately there are a
Interesting. A similar patch was provided for Fedora and included in
upstream CLN. However, it #defines cl_word_alignment to 4, not 8, as you
do. Are you sure about 8? If you are sure, I can change this upstream.
I'm pretty sure 8 is right.
The comments in the cln source say
// cl_uint_alig
Package: kde-workspace
Version: $:4.11.11-2
Severity: important
User: debian-...@lists.debian.org
Usertags: arm64
kde-workspace seems to be failing to build on arm64 with dpkg-shlibdeps
issues related to libkwinglesutils.so.
https://buildd.debian.org/status/fetch.php?pkg=kde-workspace&arch=arm
Package: libtecla
Version: 1.6.2-1
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: arm64
libtecla FTBFS on arm64 with the following error
checking for ld... ld
Invalid configuration `aarch64-linux-gnu': machine `aarch64' not recognized
configure: error: /bin/bash ./co
801 - 900 of 2889 matches
Mail list logo
