1. It's failing in the doc/genlua stuff, which is an internal tool meant
to generate documentation that is currently unfinished. Arguably it
should be removed from source releases anyway. So a simple fix is for
debian to just remove this directory from SUBDIRS in TuvokSubdirs.pro.
I don't see
On 12/09/16 20:51, Gianfranco Costamagna wrote:
Gianfranco, as per Policy §4.4, please put your own name in the
changelog trailer when making an upload.
well, it seems unfair wrt Peter,
IMO what the changelog should look like in a case like this is
imapcopy (1.04-2.1) unstable;
Package: gazebo
Version: 7.3.0+dfsg-3
Severity: serious
Tags: patch
The most recent version of gazebo added a build-dependency on
libkido-dev to the source package and added a binary on libkido-dev to
libgazebo7-dev
No mention of this was made in the changelog and no other changes in the
On 03/09/16 06:05, Graham Inggs wrote:
This comes from protobuf 3. I found it has already been fixed in git
[1], although the patch description is incorrect.
Regards
Graham
[1]
tags 818448 +patch
thanks
The fix for this build failure is trivial. Patch attatched.
Note: I have tested that this builds, I have not tested it beyond that.
diff -Nru imapcopy-1.04/debian/changelog imapcopy-1.04/debian/changelog
--- imapcopy-1.04/debian/changelog 2014-03-29
On 03/09/16 14:15, Graham Inggs wrote:
A wild stab in the dark: don't we need to binNMU lazarus before we can
build packages with it?
I'd say yes, in that build log it looks like it's lazbuild which is
crashing. So yes a binnmu of lazarus seems the next step.
Then, don't we need to binNMU
On 03/09/16 03:36, peter green wrote:
On 02/09/16 23:05, Abou Al Montacir wrote:
Upstream suggests the following patch which may be temporary:
diff --git a/rtl/linux/powerpc/cprt0.as b/rtl/linux/powerpc/cprt0.as
index e237d8d..a5672e3 100644
--- a/rtl/linux/powerpc/cprt0.as
+++ b/rtl/linux
On 02/09/16 23:05, Abou Al Montacir wrote:
Upstream suggests the following patch which may be temporary:
diff --git a/rtl/linux/powerpc/cprt0.as b/rtl/linux/powerpc/cprt0.as
index e237d8d..a5672e3 100644
--- a/rtl/linux/powerpc/cprt0.as
+++ b/rtl/linux/powerpc/cprt0.as
@@ -88,12 +88,8 @@
On 29/08/16 15:45, Peter Michael Green wrote:
tags 835427 +patch
thanks
Older versions of tinyxml defined both XML_NO_ERROR and XML_SUCCESS
to 0. Never
versions define only XML_SUCCESS.
Attatched is a patch that replaces XML_NO_ERROR with XML_SUCCESS
Unfortunately while that patch fixed the
Apparently ginac requires C++11 now, which you need to manually enable with GCC
5.
gcc-6 is now the default and has C++11 enabled by default, so this is no
longer an issue.
Unfortunately the packege now fails to build for a different reason.
On 23/08/16 19:28, Paul Gevers wrote:
Hi Peter,
On 23-08-16 04:52, peter green wrote:
I tried building the new package in a jessie chroot (which worked with a
few minor packaging tweaks), then running the results in a sid chroot
(unfortunatley I was doing this on a porterbox so I couldn't
On 22/08/16 21:01, Paul Gevers wrote:
I am including the patch right now in our packaging. I'll upload it to
the archive and I'll then continue bootstrapping on powerpc. Give me a
couple of days. Feel free to bootstrap powerpc before I do.
I tried building the new package in a jessie chroot
It looks like this has been fixed upstream
https://github.com/johang/btfs/issues/28
However my attempts to backport the fixes failed to result in a
succesful build. Maybe it's time for the maintainer to update the
package to a newer upstream.
Package: frog
Version: 0.12.20-1
Severity: serious
x-debbugs-cc: libfo...@packages.debian.org
Frog currently FTBFS in sid as can be seen from the recent binnmus for
the ICU transition
I have been trying to get the ICU transition to go through in raspbian
stretch. I first patched libfolia to
tags 832870 +patch
thanks
This is caused by a missing build-dependency on python. This was
previously masked by python being pulled in indirectly.
While working on this issue I also found the clean target was broken. So
I fixed that too.
I have uploaded this fix to raspbian, debdiff at
About a week ago you tagged this bug pending, any ETA on an upload?
tags 811635 +patch
thanks
> document.cxx:250:12: error: cannot convert 'std::ostream {aka
std::basic_ostream}' to 'bool' in return
> return os;
> ^~
Adding an explicit cast to bool fixes this.
I have uploaded a fix for this to raspbian. The dsc is at
package: muon-updater
version: 4:5.7.1-1
severity: serious
muon-notfier and muon-updater depend on plasma-discover-updater which is
no longer built by the plasma-discover source package.
package: etcd
version: 2.3.7+dfsg-3
severity: serious
From the build log:
https://buildd.debian.org/status/fetch.php?pkg=etcd=arm64=2.3.7%2Bdfsg-3=1468514503
=== RUN TestTransportErrorc
--- FAIL: TestTransportErrorc (0.15s)
transport_test.go:153: cannot receive error from errorc
On 03/07/16 16:55, Peter Green wrote:
On 14/06/16 07:10, Scott Kitterman wrote:
On Tuesday, June 14, 2016 01:21:26 AM peter green wrote:
I am reluctant to NMU this In Debian myself because I don't use
calligra
personally and I have not had any feedback from anyone on the patched
package
On 14/06/16 07:10, Scott Kitterman wrote:
On Tuesday, June 14, 2016 01:21:26 AM peter green wrote:
I am reluctant to NMU this In Debian myself because I don't use calligra
personally and I have not had any feedback from anyone on the patched
package.
Considering it doesn't build
Package: viva
Version: 1.1+git20150820.1a3d1f680f-1
Severity: serious
Viva build-depends on libpajeutils-dev which is no longer built by
source package pajeng.
On 14/06/16 01:21, peter green wrote:
I've just done a new upload of calligra in Raspbian that on top of
previous fixes removes the dependency on which no longer exists.
Debdiff at
Apologies for not actually linking the debdiff, it's at
http://debdiffs.raspbian.org/main/c/calligra
Martin Michlmayr wrote (as bug 818395)
calligra fails to build. I don't see any obvious errors (but I didn't look
through the 22 MB of logs) but it ends with:
I already mentioned this in my posts to 797389. It seems that marble no
longer supports qt4. The fix I applied for raspbian was to
package: kdepim-runtime
severity: serious
version: 2.2.0-2
kdepim-runtime depends on libkgapi2-2 and build-depends on libkgapi-dev
. These packages were previously built by the source package libkgapi
but are no longer built.
This appears to be fixed in the version in experimental, maybe
valadoc is the last remaining reverse dependency of the cruft package
libvala-0.30-0 . A rc bug has been filed over a month ago but there was
no maintainer response. valadoc is on the "key packages" list so it's
not being autoremoved from testing.
I tried changing the build-deps but a test
My guess would be that the testsuite is just extremely slow on armel
(which uses software floating point).
Would it be possible to disable longer-running tests or is the testsuite
an all-or-nothing thing?
Package: php5-json
Severity: serious
Version: 1.3.7-1
php5-json depends on the cruft package libjson-c2 which is no longer
built from the json-c source package.
The release team attempted to schedule a binnmu but it was blocked due
to the removal of dh-php5.
Furthermore even in an
service.cpp: In static member function 'static void
sipwitch::service::publish(const char*)':
service.cpp:256:28: error: invalid conversion from 'const sockaddr*' to
'sockaddr*' [-fpermissive]
host = resolver.getAddr();
This was easy enough to fix, just add a const to the type of
* ships a gdk-pixbuf2.0.pc that requires libpng12.pc;
* depends on libpng-dev which:
- on experimental, is a real package that does not ship libpng12.pc
but only libpng16.pc and libpng.pc;
- on unstable, is provided by libpng12-dev which does provide
libpng12.pc, but that
On 08/04/16 20:55, Graham Inggs wrote:
Secondly, it should be possible to reproduce the fault by building in
an armhf schroot on abel.d.o, which has the same hardware as the
buildds. A temporary solution would be to upload armhf binaries built
on asachi.d.o.
It would be useful if someone
Found 819538 3.18.1-1
Thanks
> Your package needs to be updated to build against the new vala
0.32.
Testing is also affected by this issue.
On 19/03/16 12:26, peter green wrote:
This seems to be a result of the recent pic related backports. I'm
working on a fix now.
ok, the first thing I did was move globtype (which provides TSymStr)
from the implementation uses to the interface uses so it would be
available at that line
Package: fpc
Version: 3.0.0+dfsg-3
Severity: serious
The most recent i386 build of freepascal failed.
/usr/bin/ppc386 -Ur -Xs -O2 -n -Fui386 -Fusystems
-Fu/«BUILDDIR»/fpc-3.0.0+dfsg/fpcsrc/rtl/units/i386-linux -Fii386 -FE.
-FUi386/units/i386-linux -dRELEASE
1500 303.554/322.880 Kb Used
(10001) PPU Loading /usr/lib/fpc/3.0.0/units/x86_64-linux/fcl-net/sslsockets.ppu
(10011) PPU Source: sslsockets.pp not available
(10028) Recompiling sslsockets, checksum changed for OpenSSL
Fatal: (10022) Can't find unit sslsockets used by fphttpclient
I'm
The old default-java-plugin packages for mips* still seem to be in
unstable and for some reason don't seem to be showing up on "the cruft
report". You might want to file a removal request.
tags 813461 +patch
thanks
cqrlog fails to build from source in unstable/amd64:
Colin asked me to take a look at this.
Fixing the build failure is trivial enough, just a matter of avoiding
some field aliases that iirc were considered deprecated for some time
and have been removed in 3.0.0
A
Package: php-horde-memcache
Version: 2.0.7-3
Severity: serious
php-horde-memcache depends on php5-memcache which is no longer built by
the php-memcache source package.
Ubuntu seems to indicate that a no-change rebuild is enough to fix this.
Package: ldap-account-manager
Severity: serious
Version: 5.2-1
ldap-account-manager depends on php5-imagick which is no longer built by
the source package php-imagick.
I'm not sure if you can just change the dependency to php-imagick or if
more work is needed.
Package: fusiondirectory
Severity: serious
Version: 1.0.8.8-3
fusiondirectory depends on php5-imagick which is no longer built by the
source package php-imagick.
I'm not sure if you can just change the dependency to php-imagick or if
more work is needed.
On 15/02/16 13:36, Yaroslav Halchenko wrote:
Sorry about delay... quite often those Bus errors just go away on their
own since aren't anything to be fixed in pandas, but this time it still
persists with 0.17.1:
https://buildd.debian.org/status/fetch.php?pkg=pandas=armhf=0.17.1-3=1450078009
Package: yubioauth-desktop
Severity: serious
x-debbugs-cc: pysc...@packages.debian.org
yubioauth-desktop depends on python-pyscard which is no longer built by
pyscard.
pyscard dropped the binary package in it's most recent upload with no
explanation given in the changelog.
On 29/11/15 14:42, peter green wrote:
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
If you use and care about calligra can you please try building with the
patch I posted at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797389#17
And tell me
1. Is that patch still sufficient to make the package build in current sid?
2. Are the resulting packages installable?
3. Do the
even after a binNMU python-gnutls still depends on libgnutls-deb0-28
as it does not make use of the shlibs system. Please upgrade to use
GnuTLS 3.4
It's easy enough to change the gnutls version to 30 and update the
package dependencies.
Unfortunately after doing so the code doesn't work. I
On 02/02/16 05:37, peter green wrote:
found 813078 5.20150731-1
thanks
Sorry I missed the first sentance of my explanation of the found
command, the paragraph was meant to say.
In raspbian stretch we have seen this same issue with a binnmu of
5.20150731-1. Debian reproducability tests
found 813078 5.20150731-1
thanks
Debian reproducability tests in testing are not showing it right now,
but I strongly suspect that is because some other package hasn't been
rebuilt yet, not because the underlying issue is not there.
Having said that I think the real issue is actually in the
net_tls_TLSSession.cpp:120:38: error: 'gnutls_certificate_type_set_priority'
was not declared in this scope
(*m_gnutlsSession, certTypePriority);
^
net_tls_TLSSession.cpp:131:68: error: 'gnutls_protocol_set_priority' was not
declared in this
tags 782469 +patch
thanks
I took a look at the code in conjunction with the migration instructions
that were linked in the bug report (thanks for linking to those).
The results of the call to gnutls_pubkey_get_verify_algorithm are
discarded, the code only checks if it succeeds or not. I
tags 812848 +patch
thanks
The code in question is
static int protocol_priority[] = {GNUTLS_TLS1, GNUTLS_SSL3, 0};
static int kx_priority[] = {GNUTLS_KX_RSA, 0};
static int cipher_priority[] = {GNUTLS_CIPHER_3DES_CBC,
GNUTLS_CIPHER_ARCFOUR_128,
0};
tags 782801 +patch
thanks
This now fixed in upstream GIT, see
958f5f9e4ba752ca3e4045c09618579eae74f219 GNUTLS 3.4 compartibility.
7857ccafe14848d8378272421d2e49c3b351334b GNUTLS version 3.4.4 and newer
compartibility
After some googling I managed to find said upstream git repo
tags 805799 +patch
thanks
Ubuntu have a fix for this.
https://patches.ubuntu.com/k/kst/kst_2.0.3-4ubuntu3.patch
I cleaned up the changelog and removed ubuntus maintainer changes and
uploaded to raspbian. Debdiff of that at.
http://debdiffs.raspbian.org/main/k/kst/kst_2.0.3-4%2brpi1.debdiff
tags 809054 +patch
thanks
The attatched debdiff fixes the build by stripping any -W
tokens out of CPPFLAGS . It applies it at the debian/rules level so it
unfortunately affects everything. If someone wants to dig through the
upstream build system and apply the stripping only when the CFLAGs
tags 810520 +patch
thanks
The attatched patch makes this package build by removing -Werror from
the compiler flags.
diff -Nru ideviceinstaller-1.0.1/debian/changelog
ideviceinstaller-1.0.1/debian/changelog
--- ideviceinstaller-1.0.1/debian/changelog 2013-11-19 22:24:56.0
+
+++
Package: monodevelop
Version: 5.10.0.871-1
Severity: serious
Monodevelop (which recently changed one of it's binary packages from
arch all to arch any) failed to build on the buildds with.
dh clean --with cli,autoreconf
dh: unable to load addon cli: Can't locate
Tags 807087 +patch
thanks
xpdf fails to build with Poppler 0.38.0, which is currently in
experimental and targeted for unstable; extract of build log is:
Looks like ubuntu have a patch for this.
https://patches.ubuntu.com/x/xpdf/xpdf_3.03-17ubuntu5.patch
For the latter two options, please see a patch at
http://launchpadlibrarian.net/222938828/boats_201307-1build2_201307-1ubuntu1.diff.gz
I went to apply your patch in raspbian but I found further work was
needed to get a sucessful build. Launchpad shows it also failing in ubuntu.
The first
the new upstream version fixes the build failures with GCC 5. Had to work around
the build failure on armhf, and enabled the builds for powerpc and ppc64el.
Note that I forgot to prepare the dfsg tarball.
https://launchpad.net/ubuntu/+source/root-system/5.34.30-0ubuntu3
Note that there is now a
On 12/12/15 17:32, peter green wrote:
I was able to get aster to build for raspbian stretch (in which I have
imported the updated petsc from debian sid) with the changes in the
attatched debdiff.
Sorry I must learn to read the screen more carefully and actually check
that something has
Tags 805193 +patch
Thanks
I was able to get aster to build for raspbian stretch (in which I have
imported the updated petsc from debian sid) with the changes in the
attatched debdiff. I have not tried it on any other system. I have not
tested if the resulting packages actually work. I will be
On 12/12/15 17:47, peter green wrote:
On 12/12/15 17:32, peter green wrote:
I was able to get aster to build for raspbian stretch (in which I
have imported the updated petsc from debian sid) with the changes in
the attatched debdiff.
Sorry I must learn to read the screen more carefully
tags 807277 +patch
thanks
In a raspbian stretch-staging environment (which has sid's
ktp-common-internals) I was able to build this package after changing
the build-dependency from libktpcommoninternalsprivate-dev to libktp-dev
On 12/12/15 19:01, peter green wrote:
New debdiff attatched, still no intent to NMU.
Sorry, debdiff at
http://debdiffs.raspbian.org/main/a/aster/aster_11.5.0%2bdfsg2-3%2brpi1.debdiff
/usr/include/mpich/mpicxx.h has a hardwired dependency on the gcc used
to build mpich (gcc 5.2):
#ifdef __GNUC__
# if __GNUC__>= 5
# if __GNUC_MINOR__> 2&& 2 == 2
# error 'Please use the same version of GCC and g++ for compiling MPICH and
user MPI programs'
# endif
# endif
#endif
But the
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
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: 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
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,
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
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
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.
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: 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
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
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
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,
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
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
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 \
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
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)':
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
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.
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: 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
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
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: 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
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=armhf=1%3A2.8.5%2Bdfsg-1.2%2Brpi1%2Bb2=1443503934
make[1]: Entering directory '/«BUILDDIR»/calligra-2.8.5+dfsg'
dh_install --list-missing
cp:
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.
Indeed. This is due to libgit2 0.23 breaking some API geany-plugins
uses. Upstream added support for it in
http://git.geany.org/geany-plugins/commit/?id=37aa25a1a4508c3d7559c0a2d00663b9c8d322c6,
and it should be trivial and safe to cherry-pick.
I applied this patch in raspbian stretch-staging*
It appears the library rename introduced in uhd 3.8.5-2.1 was reverted
in uhd 3.9.0-1. There was no mention of this revert in the changelog.
Was the revert intentional and if so what was the reasoning behind it?
package: fuse-emulator-utils
version: 1.1.1-3fuse-emulator-utils
tags: stretch sid
Severity: serious
Attempting to build fuse-emulator-utils on a raspbian stretch autobuilder
failed with.
/bin/bash ./libtool --tag=CXX --mode=link g++ -g -O2
-fstack-protector-strong -Wformat
timblserver (1.8-1) experimental; urgency=low
.
* New upstream release.
- Fixes "timblserver: FTBFS in unstable: error: 'class Timbl::GetOptClass'
How come this was uploaded to experimental and not unstable?
tags 713663 -patch
thanks
Unfortunately the patch I previously sent to this bug is no longer
sufficient to make the package build. I now get lots of errors like
"usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse
error at "BOOST_JOIN""
log at
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: rss2irc
version: 1.0.6-3
severity: serious
tags: sid stretch
according to
https://buildd.debian.org/status/package.php?p=rss2ircsuite=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
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 applicable
Oh, and by the way, it seems that the potential removal of lazarus and
its reverse dependencies is not due to this bug, but because of the
fixed bug 777970, see the tracker:https://tracker.debian.org/pkg/lazarus
Which is now fixed in testing, so no longer an issue.
And if I am correct, as
801 - 900 of 1811 matches
Mail list logo
