I've uploaded a new version of UHD. Looks like upstream patches
from upstream SoapySDR have the changes needed to build again.
I'll prepare a soapyuhd 0.4.1-5 to address this soon.
-Maitland
>> affects -1 src:gr-limesdr src:gr-funcube src:gr-rds src:gr-hpsdr
>> src:gr-fosphor src:gr-satellites src:gr-radar src:gr-iqbal
> Bug #1008854 [gnuradio-dev] Packages using gnuradio-dev FTBFS
> Added indication that 1008854 affects src:gr-limesdr, src:gr-funcube,
> src:gr-rds, src:gr-hpsdr, src
On Sun, 07 Jun 2020 10:36:54 +0200
Antonio Radici wrote:
> gqrx does not start in testing, this renders the package unusable.
I'm sorry to hear this.
I noticed the -b3 version get upgraded today too, but it works for me
when I start it
(I have a box tracking testing, so no chroot here.)
>
Moritz Mühlenhoff writes:
> Hi Maitland,
> per upstream issue 98 it doesn't sound as if it's going to be fixed,
> should be remove it or are you planning to port it yourself?
I was just talking to the upstream author at the gnuradio conference.
Our plan going forward is to just remove the GUI el
On Sat, 7 Sep 2019 22:44:00 +0200
Moritz Mühlenhoff wrote:
> Hi Maitland,
> we're moving forward with the Qt4 removal.
>
> qthid-fcd-controller seems dead upstream, are you planning to port it
> yourself or shall we remove it from the archive?
>
> Cheers,
> Moritz
Yeah, I have tried to
I got surprised by the result that adding a file to
debian/libbladerf-doc.docs resulted in a file being unpacked to
/usr/share/doc/libbladerf-dev/
Upload with Breaks:/Replaces: coming soon.
-Maitland
On Sat, 12 Jan 2019 16:02:02 +0100
Christoph Berg wrote:
> Maitland, can we remove predict?
>
> Christoph
Yes...
Certainly predict-gsat is obsolete and unmaintained - and gpredict is
the logical successor.
But...
There might be curses interface fans who would mourn its removal, but
the codebase
Before getting this bug report, I uploaded
uhd 3.13.0.2-3 which fixes this bug.
-Maitland
Reiner Herrmann writes:
> the attached patch fixes the FTBFS by including the missing header.
...
> ++#include
Hi,
Thanks so much, but I see the upstream author Moe Wheatley has
now also included this fix, so I have pulled a few more commits
from upstreams work towards a version 1.21 onto a rev
If the problem can be traced to the .pc file and pkg-config I will take blame
for a bug. I am away from an appropriate computer right now, but will
investigate further soon.
-Maitland
On May 18, 2018 7:20:55 AM EDT, Andrey Rahmatullin wrote:
>On Fri, May 18, 2018 at 01:06:18PM +0200, Andreas
So yeah, we cannot expect NEON on Debian armhf.
But I did not expect these compile time errors... I would hope that
one could at least compile some NEON code on Debian armhf, and then
maybe do some runtime conditional test to only execute NEON if it
is available.
This code has not compiled on Deb
Anton Gladky writes:
> So, I think vtkdata can safely be removed as requested by Mathieu.
I support removal of vtkdata from sid and testing, and agree it should
not be released with stretch.
Back when I created the vtkdata package, I was motivated by the need for
it in build-time test targets, a
Andy Berkvam writes:
> Package: gnuradio-dev
> Version: 3.7.10.1-1~bpo8+1
> Severity: grave
> Justification: renders package unusable
Unable to reproduce in Debian, on adm64 and i386 at least.
> Running jessie and gnuradio 3.7.5. Configured jessie-backports and installed
> gnuradio 3.7.10.1.
It seemed to me that a bit of modernization in log4cpp packaging would
help fix this. I noticed upstream states that the 1.1.1 is the newest
stable release, and refactored the packaging around dh and
dh-autoreconf.
(I have not had time yet to build and test my packages with this
newer log4cpp, and
I am preparing a gr-air-modes 0.0.2.c29eb60-1 which has uptream
swig fixes that I expect will address this.
(current gr-air-modes git HEAD)
Thanks for your interest in this package. Yes, it has caused
me to learn more about swig, and this bug showed up trying
to merge multiple github features alon
Raphaël Hertzog writes:
> Package: libuhd003
> Version: 3.9.0-1
> Severity: serious
> User: de...@kali.org
> Usertags: origin-kali
>
> I just noticed that with uhd 3.9.0 libuhd003 lost the v5 suffix that had
> been introduced with 3.8.5-2.1.
>
> And the changelog has no explanation for
peter green writes:
> 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?
Yes it was intentional.
The reasoning is that uhd ro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
See Bug#770270: unblock: dime/0.20111205-2
for my unblock request.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJUbW+PAAoJEFBB8YkfROCQ3jAP/jyCZifTQUSvmbBb21ngz5hI
7aqm12HFdDpAZsGWxr5z7H/xzv6FywpRHFfWVCPVqXKoFS0kyZmW
There's more wrong with dime 0.20111205-1
Some libtool wrappers were installed into /usr/bin/dxf2vrml
and /usr/bin/dxf2sphere in the dime binary package - rather
then the correct compiled ELF binary executables. Therefore,
the dime package did not depend upon the libdime1 library
package either.
It should be fine again soon.
bladerf 0.2014.09~rc2-4 just built fine on the kfreebsds.
-Maitland
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> "Steven" == Steven writes:
Steven> I am unable to build a working gqrx-sdr from source due to this bug.
Yes. It is annoying that unstable is being unstable.
As maintainer, I am just goting to sit on my hands a bit longer - to
give a chance to the Boost Transition Team to complete the task
Indeed.
This problem has arisen since libuhd003 got rebuilt with
boost 1.55.
I only hope that there will be soon a
Binary-only non-maintainer upload of gqrx-sdr
and gnuradio to remedy this inconsistency.
Otherwise, I'm sure this particular bug will go away
upon my next upload of gqrx-sdr.
I'm C
19:11:16.0 -0400
@@ -1,3 +1,26 @@
+comedilib (0.10.1-2) unstable; urgency=low
+
+ * Bring in Ubuntu fixes (patch from A. Maitland Bottoms)
+ (Closes: #727345, #733322, #711203)
+
+ -- Gudjon I. Gudjonsson Mon, 31 Mar 2014 22:40:31 +0200
+
+comedilib (0.10.1-1ubuntu2) trusty; urgency
> "Aaron" == Aaron M Ucko writes:
Aaron> Thanks for the prompt fix to #728212! Linux and Hurd builds now
Aaron> succeed, but kFreeBSD builds are still failing, as libtool (presumably
Aaron> an old version) doesn't know how to build shared libraries there:
Prompt after letting the package bit
Source: zeroc-ice
Version: 3.5.0-1
Severity: serious
Tags: patch
The Debian package auto-build systems are failing
on creating the python3-zeroc-ice package.
# moving files (python3 policy)
mv debian/python3-zeroc-ice/usr/lib/python3.*/dist-packages/*.so*
debian/python3-zeroc-ice/usr/lib/python3
I think I was just bit by this bug.
Getting from wheezy-backports today,
initramfs-tools 0.112~bpo70+1
linux-image-3.9-0.bpo.1-amd64 3.9.6-1~bpo70+1
I found that adding rootdelay=1 to the grub boot kernel argument list
was enough to get linux-image-3.9-0.bpo.1-amd64
> Christoph Egger writes:
> /build/buildd-uhd_3.4.0-2-kfreebsd-amd64-jnOr7B/uhd-3.4.0/host/examples/network_relay.cpp:210:111:
> error: 'rx_dsp_buff_size' was not declared in this scope
Leading up to that is uhd-3.4.0/host/include/uhd/config.hpp
// Platform defines for conditional parts of h
Upload will be soon, vtk 5.4.2-7 is building now.
I had to spend some time reorganizing my local git tree,
which kept me from uploading yesterday.
Once git-buildpackage finishes I'll git-push and
upload.
-Maitland
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subj
Yes, there were a few hardcoded python2.5 paths.
Thanks for checking.
The package control file specifies
XS-Python-Version: current
And now that
http://git.debian.org/?p=collab-maint/vtk.git;a=commit;h=d809bf34bb587c7be44087d430f512adbaf0a553
has been applied, vtk 5.4.2-6 and onwards should build
The Debian packages build with the following configuration:
VTK_USE_SYSTEM_EXPAT:BOOL=ON
so the VTK components will use the systemwide
/usr/lib/libexpat.so.1 from the fixed Debian
libexpat1 package.
So while the upstream source includes source for
libexpat, it is not used to create te Debian bina
It appears that fixing 544674 will fix the powerpc/ppc problem
in bug 545335. It might be worth making a cmake 2.6.4-3 upload
for this including the findjni2.cmake.patch.
-Maitland
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Con
Varun Hiremath writes:
...
> A new version of python-vkt 5.2.1-6 was uploaded today which seems to
> fix #529961. But, for me there is no change in the behavior. I am
> still able to import vtk but not libvtkCommonPython. Does the new
> version work for you?
>
> Regards,
> Varun
>
>
Drew Parsons writes:
> Hope it's not too hard to find out what's wrong, sorry I'm not sure how
> to help!
I am building vtk 5.2.1-6 right now and I am hopeful that it will
improve the python-vtk package situation.
-Maitland
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: openoffice.org
Version: 2.0.4.dfsg.2-2
Severity: grave
Justification: renders package unusable
$ oowriter
no suitable windowing system found, exiting.
** (process:26780): WARNING **: Unknown error forking main binary / abnormal
early exit .
OK,
I have just successfully built vtk 5.0.1
in a pbuilder environment.
Perhaps you were trying vtk 4.4.2 and filed
a duplicate of bug #379240? Your bug report
doesn't say, but since 5.0.1 is still new,
I am guessing that you saw the bug on version
4.4.2-10.
-Maitland
--
To UNSUBSCRIBE, email
vtk 5.0.1-1 is making use of dh_python, and
it and mayavi_1.5-2 have been seen running
correctly with python2.4 as the default python.
There may be additional refinements to improve
python policy compliance, but I have uploaded
vtk_5.0.1-1 and mayavi_1.5-2 to support the
transition to python2.4 as
What version of cmake was pbuilder using?
(Maybe I need to bump up the versioned depends upon cmake.)
I'll try to duplicate this result...
-Maitland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
OK,
I am uploading vtk 5, maybe that will fare better.
Patches/NMU welcome this week, I'll get back to work on it myself
around 1 August.
-Maitland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Stephen Gran <[EMAIL PROTECTED]> writes:
> Attached is a patch for the 4 RC bugs against you package. I am
> uploading now to a delayed queue. If you want to override this NMU,
> please upload a fixed version yourself.
Thanks! But...
There is a -9 version in NEW that addresses these bugs,
htt
Version: 1.1.3-7
Sarge system
Yes, I encountered this on a system that still had some fonts in a
/usr/X11R6/lib/X11/fonts/WordPerfect/
directory. (Not Debian's fault...)
Got rid of those and OpenOffice.org is happy to run again.
-Maitland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
OK,
It is nice to have a system booting again.
the mdadm-1.9.0-2.1 version with the upgrade
stanza added would be a welcome improvement.
I'll give it an 'It works for me.' endorsement.
-Maitland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [E
On Date: Tue, 29 Mar 2005 03:57:27 -0800 Steve Langasek <[EMAIL PROTECTED]>
posted:
mdadm-294404.diff
Almost there, I think. However, it didn't fix my broken md+udev+2.6.8-2-686-smp
system. After installing mdadm_1.9.0-2.1_i386.deb built using the patch, the
system startup link still had
S25mdad
Package: aolserver4
Version: 4.0.10-1
Severity: serious
(Severity: grave on Alpha)
Seems not to like the size of int and long:
~# aolserver4-nsd -u www-data -t /etc/aolserver4/aolserver4.tcl
NsTclInitObjs: sizeof(int) < sizeof(long)
-Maitland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
43 matches
Mail list logo
