Uploading directly since this is over a week with no response from the
maintainer. NMU diff is identical to the last patch attached except for
unstable/UNRELEASED.
signature.asc
Description: This is a digitally signed message part.
That was meant to go to a different bug.
signature.asc
Description: This is a digitally signed message part.
Uploading directly since this is over a week with no response from the
maintainer. NMU diff is identical to the last patch attached except for
unstable/UNRELEASED.
signature.asc
Description: This is a digitally signed message part.
Package: liblua5.1-0-dev
Version: 5.1.5-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What exactly did you do (or not do) that was effective (or
ineffective)?
Rebuilt opendkim 2.6.2-1 (current version in Wheezy/Sid) against the update
liblua5.1-0-dev.
From #682183:
Looking around, it looks it could be fixed by:
* moving lua-deb-multiarch.h to /usr/include/$arch/
...
That's sufficient to fix opendkim, so merging.
signature.asc
Description: This is a digitally signed message part.
On Thursday, July 19, 2012 08:41:36 AM Andreas Beckmann wrote:
On 2012-07-19 05:36, Debian Bug Tracking System wrote:
* Add /var/run/clamav to directories shipped by clamav-base so dpkg
cleanup
will work for it too.
That won't work. /var/run is a volatile file system.
On Thursday, July 19, 2012 09:14:12 AM Andreas Beckmann wrote:
On 2012-07-19 08:56, Scott Kitterman wrote:
I left in the part where the init script will create it if it doesn't
exist
already. I checked and it gets correctly removed both after initial
install and if I remove the directory
On Wednesday, July 18, 2012 10:30:57 AM Andreas Beckmann wrote:
Package: clamav-freshclam
Version: 0.97.5+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package removes files that
were installed by another
On Wednesday, July 11, 2012 03:56:51 PM mourad wrote:
Package: kcheckgmail
Version: 0.6.0-2
Severity: important
Dear Maintainer,
* What led up to the situation?
kcheckgmail could not authenticate to gmail !
Unfortunately kcheckgmail has neither a maintainer in Debian nor any upstream
+FTBFS (Closes: #680859)
+- The package only builds and installs html documentation for the python
+ version anyway, so python3-sphinx as a build-dep is clearly wrong
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 13:29:41 -0400
+
python-pyxattr (0.5.1-1) unstable; urgency=low
: #680858)
+- The package only builds and installs html documentation for the python
+ version anyway, so python3-sphinx as a build-dep is clearly wrong
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 14:34:07 -0400
+
python-pylibacl (0.5.1-1) unstable; urgency=low
* New
Based on your comment on python-pyxattr ,I'll reschedule this one to 0 days as
well.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
require 'rubygems/gem_runner'
There is a gem_runner.rb installed for both ruby1.8 and ruby1.9.1, so I assume
this is some kind of path issue to do with the way the test is run. I didn't
figure out more, so I'm leaving this for the next person to have a look at it.
Scott K
signature.asc
to match
+(Closes: #680684)
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 20:59:26 -0400
+
libaugeas-ruby (0.4.1-1) unstable; urgency=low
* New upstream release. Closes: #665927.
diff -Nru libaugeas-ruby-0.4.1/debian/control libaugeas-ruby-0.4.1/debian/control
Package: python3-defaults
Version: 3.2.3-1
Severity: grave
Justification: renders package unusable
There's a mistake in SHEBANG_RE in debpython/tools.py that causes it to lose
the 3 in python3 in shebangs. I'll upload the fix as soon as I have a bug
number.
--
To UNSUBSCRIBE, email to
Considering upstream is dead (web site vanished in 2007) and it's even been
removed from FreeBSD ports, I think it might be time to consider this one
dead.
Adding the DEB_HOST_MULTIARCH would seem to help, but then it doesn't appear
the entire build system pays attention to SYS_INCLUDES. Then
NMU for GCC 4.7 compatiblity that was inadvertently
+reverted in the last maintainer upload (Closes: #672084) (again)
+
+ -- Scott Kitterman sc...@kitterman.com Thu, 12 Jul 2012 01:04:20 -0400
+
imageshack-uploader (2.2+hg20100408.d802dea89428-5) unstable; urgency=low
* Re-enable uploading
-depends since build system is hard coded to gcc 4.6
+and needs g++ too
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 10 Jul 2012 00:15:48 -0400
+
rubyluabridge (0.7.0-1) unstable; urgency=low
* New upstream release
diff -Nru rubyluabridge-0.7.0/debian/control rubyluabridge-0.7.0/debian
-maintainer upload.
+ * Specify use of ruby1.8 in debian/rules and add --with-ruby=ruby1.8 since
+ruby is now 1.9 (Closes: #676120)
+ * Make treil specifically depend on ruby1.8
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 10 Jul 2012 16:35:52 -0400
+
treil (1.8-1) unstable; urgency=low
-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Build-depend on ruby1.8 instead of ruby and use ruby1.8 in debian/rules
+since 1.9 is now the default (Closes: #676099)
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 10 Jul 2012 19:19:44 -0400
+
libfam-ruby (0.2.0-2) unstable
(0.5.2-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Build-depend on ruby1.8 instead of ruby and use ruby1.8 in debian/rules
+because ruby1.9 is now default (Closes: #676079)
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 10 Jul 2012 19:36:52 -0400
+
libimlib2-ruby (0.5.2-2
@@
+libnet-irc-ruby (0.14-5.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * In debian/rules and control ruby/ruby1.8 since ruby 1.9 is now default
+(Closes: #676086)
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 10 Jul 2012 20:02:06 -0400
+
libnet-irc-ruby (0.14-5) unstable
the build now that ruby1.8 is no longer default (Closes: #676078)
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 10 Jul 2012 23:15:04 -0400
+
merb (1.0.12+dfsg-4) unstable; urgency=low
* Add merb-param-protection package.
diff -u merb-1.0.12+dfsg/debian/rules merb-1.0.12+dfsg/debian/rules
+
+ * Non-maintainer upload.
+ * Build-depend on ruby/ruby-dev1.8 and build-conflict on ruby/ruby-dev1.9 to
+ensure the package continues to be built using ruby1.8 (Closes: #676094)
+- Thanks to Peter Green and Raspbian for the patch
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 10 Jul 2012 23
)
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 09 Jul 2012 23:20:01 -0400
+
libwebapp-ruby (0.4-2) unstable; urgency=low
* debian/control (Build-Depends): Added ruby (Closes: #462507).
to
+fix FTBFS now that ruby1.9.1 is default (Closes: #676087)
+ * Manually create debian/ruby-prof/usr/lib/ruby/1.8 in install rule so files
+are copied to the correct destination
+ * Directly build-depend and depend on ruby1.8 since it's no longer default
+
+ -- Scott Kitterman sc
)
+ * Manually create debian/ruby-prof/usr/lib/ruby/1.8 in install rule so files
+are copied to the correct destination
+ * Directly build-depend and depend on ruby1.8 since it's no longer default
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 09 Jul 2012 23:39:26 -0400
+
ruby-prof (0.7.3-1) unstable
no impact on the
+ functionality of the package
+
+ -- Scott Kitterman sc...@kitterman.com Fri, 06 Jul 2012 09:00:45 -0400
+
python-dateutil (1.5-1) unstable; urgency=low
[ Guido Günther ]
diff -Nru python-dateutil-1.5/debian/patches/Remove_Zoneinfo_Tarball_665894 python-dateutil-1.5+dfsg
On Friday, July 06, 2012 06:50:37 PM Gergely Nagy wrote:
Granted, python-kzorp is kind-of useless without zorp, but accidentally
satisfying dependencies is, well, accidental, and as such, not quite
appropriate.
Fair point. I think it's a bug, but not RC. I'll reopen and lower the
severity.
I can. Thanks for the second opinion.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
sip4 will cause you the same problem. I'll take care of that too.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Thursday, July 05, 2012 07:59:19 AM Scott Kitterman wrote:
sip4 will cause you the same problem. I'll take care of that too.
Actually that's wrong. Sip4 is fine.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove local CDBS rule, debian/cdbs/1/rules/copyright-check.mk, that was
+incorrectly checking for copyright checks in the Debian directory (and
+associated call in debian/rules) to fix FTBFS (Closes: #674400)
+
+ -- Scott Kitterman sc
/debian/changelog
@@ -1,3 +1,11 @@
+scanlogd (2.2.5-3.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Set adduser in postinst not to create /home/scanlogd and remove it if it
+exists. Ssolves unowned files left on system after purge (Closes: #668722)
+
+ -- Scott Kitterman sc
This bug is just the tip of the iceberg. The packaging needs to be almost
totally reworked to build in the current Debian Ruby environment.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Wednesday, July 04, 2012 10:19:34 PM Daniel Leidert wrote:
...
If the policy is not correct, it should be fixed after Wheezy release.
I'd appreciate a pointer from your site, when you start the discussion.
...
After the Wheezy release having the provides will be entirely superfluous since
Package: cdbs
Version: 0.4.115
Severity: serious
Justification: Causes FTBFS
Dear Maintainer,
* What led up to the situation?
pop-before-smtp FTBFS during a rebuild test. See #674400.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Based on the build
:59.0 -0400
@@ -1,3 +1,11 @@
+mailfilter (0.8.2-3.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Cherry pick from upstream svn rev 20 to add option to ignore timestamps
+(Closes: #661261)
+
+ -- Scott Kitterman sc...@kitterman.com Thu, 05 Jul 2012 00:22:58 -0400
I worked through this with upstream and here's the findings:
PeerList 199.192.231.53,2605:eb00:100:1::2085:29b0
is a real bug. The DB parsing code is treating everything before :: as a DB
type. This is filed upstream on Sourceforge as bug #3539493. They will
release an update
Comma separated list is a known DB type since opendkm 1.2, so you can work
around this issue by forcing it. Try:
PeerListcsl:199.192.231.53,2605:eb00:100:1::2085:29b0
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
I did test it. It defaults to 8080 if you don't specify.
Stephen Gran sg...@debian.org wrote:
This one time, at band camp, Scott Kitterman said:
Attached.
Hi,
Have you tested that that is a valid config file? I have some vague
memory of freshclam not being happy with a proxyhost
The Avogadro dependency is incorrect and should be fixed. Depends: python2.7,
python-qt4 will do what you want. Since, if Avogadro needs 2.7, you need to
depend on it directly, also depending on python2.7-qt4 is redundant.
Scott K
P.S. Due to a multi-day power outage all I've got to work from
That's a bug in the policy I failed to notice. It should be restricted to
packages that build modules only for the non-default version of Python which
Avogadro doesn't. One or the other package needs to be changed. I agree with
that.
python-avogadro is the only package in the archive that
I've looked into this a bit and the bogus proxy host is a function of whatever
debconf feeds to the postinst. I can't tell if it's inadvertent data entry or
some other issue, but it's not a clamav bug. The part of this that is a
clamav bug is that if the proxy port is not specified, the
-freshclam.postinst so that
+failure to specify port does not result in an invalid configuration
+(Closes: #678247), (LP: #784797)
+
+ -- Scott Kitterman sc...@kitterman.com Sat, 30 Jun 2012 21:35:33 -0400
+
clamav (0.97.5+dfsg-2) unstable; urgency=medium
* Medium urgency due to security fixes
I've built test packages of the current version for Squeeze
http://kitterman.com/dkim/opendkim/. Please test and see if they resolve your
issue.
Scott K
signature.asc
Description: This is a digitally signed message part.
Could you provide the information requested in
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/784797/comments/8 - I
agree it looks similar.
Thanks. I've reviewed the freshclam postinst and don't see how it can cause a
problem like this. Can you sudo dpkg-reconfigure clamav-freshclam and when you
get to the related questions, carefully check and see if there's any
whitespace in the debconf window. If so, please remove it and see
Confirmed. WIll upload a new package shortly.
signature.asc
Description: This is a digitally signed message part.
Please check again and see if this bug still exists. It should be resolved.
Thanks,
Scott K
signature.asc
Description: This is a digitally signed message part.
Please test again 4.13.2-1+b1 after it is built.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
)
+- Thanks to Felix Geyer for the fix
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 15 May 2012 01:28:54 -0400
+
uim (1:1.7.3-2) unstable; urgency=low
[ HIGUCHI Daisuke (VDR dai) ]
diff -Nru uim-1.7.3/debian/control uim-1.7.3/debian/control
--- uim-1.7.3/debian/control 2012-03-10 02:30
+
+ * Non-maintainer upload.
+ * Fix FTBFS with Qt 4.8 (multiarch) by updating ibus-qt4.install to use
+multiarch paths (Closes: #662775)
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 15 May 2012 02:44:44 -0400
+
ibus-qt (1.3.1-2) unstable; urgency=low
* Fix FTBFS: FTBFS on latest
.
+
+ [ Felix Geyer ]
+ * Add 04glu-include.dpatch to fix FTBFS with Qt 4.8.
+ * Add 05glu-link.dpatch to make libqglviewer-qt4 link against libGLU.
+ * Add Pre-Depends: ${misc:Pre-Depends} to libqglviewer-qt4-2.
+ * Mark libqglviewer-qt4-2 as Multi-Arch: same.
+
+ -- Scott Kitterman sc
/scidavis_pro.diff to include linking changes
+ needed to build with Qt 4.8
+
+ -- Scott Kitterman sc...@kitterman.com Wed, 09 May 2012 15:14:03 -0400
+
scidavis (0.2.4-3.2) unstable; urgency=low
* Non-maintainer upload.
diff -Nru scidavis-0.2.4/debian/patches/scidavis_pro.diff scidavis-0.2.4
)
+- Thanks to Andreas Moog from Ubuntu for the patch
+
+ -- Scott Kitterman sc...@kitterman.com Thu, 10 May 2012 17:39:10 -0400
+
mudlet (2.0-rc12-2) unstable; urgency=low
* Linked to yajl2 Closes: #653880
diff -Nru mudlet-2.0-rc12/debian/patches/ftbfs_qt4.8.patch mudlet-2.0-rc12/debian/patches
for libqwt_designer_plugin.so in libqwt-dev.install
+- Update build-depends version requirements for debhelper and libqt4-dev
+- Add misc:Pre-Depends for libqwt6
+- Bump compat to 8
+
+ -- Scott Kitterman sc...@kitterman.com Wed, 09 May 2012 15:24:37 -0400
+
qwt (6.0.0-1.1) unstable; urgency=medium
* Non
Can you rebuild calibre and see if that fixes it?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
/stddecorators_no_keywords.patch
+- Extend debian/patches/cmakebuildsystem.patch to compile with
+ -DQT_NO_KEYWORDS
+- Thanks to Felix Geyer for the patch
+
+ -- Scott Kitterman sc...@kitterman.com Wed, 09 May 2012 00:14:21 -0400
+
pythonqt (2.0.1-1) unstable; urgency=low
* Initial release
clam-networkeditor will now FTBFS in Unstable.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: libqxt
Version: 0.6.1-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Qt 4.8 changes some requirements for includes and linking. As a result,
libqxt will now FTBFS in unstable. No patch attached as the fix is already
in git.
--
To
Package: pyqwt5
Version: 5.2.1~cvs20091107+dfsg-6+b2
Severity: grave
Justification: causes non-serious data loss
5.2.1~cvs20091107+dfsg-6+b2 is rebuilt to work with Qt 4.8.1 and the current
python-qt4 in Unstable. It shouldn't migrate to Testing until they do as it
will be broken in Testing.
Since the problem is triggered by the Qt version changing, it's not clear to
me how to catch this automatically. I'll see what I can do about this case.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Queued binnmus for qscintilla2 which should deal with this.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
+Closes: #481072, LP: #520612
+- Patch from 'guyver.nkama' via Launchpad
+ * Really create $RUNDIR in init script if it doesn't exist (change from
+Ubuntu)
+ * Add $remote_fs to Required-Start and Required-Stop in
+debian/dk-filter.init
+
+ -- Scott Kitterman sc...@kitterman.com Fri, 23
to correct pyspf processing
+with CNAMES - already fixed in 2.0.7 in Wheezy/Sid (Closes: #663595)
+- Changes inline due to lack of existing patch system
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 13 Mar 2012 16:16:06 -0400
+
pyspf (2.0.5-2) unstable; urgency=low
[ Sandro Tosi ]
only
Already fixed upstream in 2.0.7-1. I'll look into an update for squeeze.
signature.asc
Description: This is a digitally signed message part.
I just built pyzmq without a problem locally on Sid/i386. Is this only an
amd64 problem?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
and the alternative of the
+railsless-deploy gem
+
+ -- Scott Kitterman sc...@kitterman.com Wed, 11 Jan 2012 16:45:07 -0500
+
capistrano (2.9.0-1) unstable; urgency=low
* New upstream release.
signature.asc
Description: This is a digitally signed message part.
For anyone looking for a solution to this problem, there are two choices:
1. Install rails
2. sudo gem install railsless-deploy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I believe I see what my mistake was.
Thanks,
Scott K
signature.asc
Description: This is a digitally signed message part.
Upstream says this Sip4 version only works with PyQt4 4.9, so I'll leave this
RC bug open against Sip4 to keep the new version out of Testing until we can
get PyQt4 (python-qt4) updated.
signature.asc
Description: This is a digitally signed message part.
I can confirm the bug, but it's a byproduct of the new sip4. Downgrading to
the sip4 in Testing produces a successful build.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
/changelog 2011-12-23 00:46:59.0 -0500
@@ -1,3 +1,11 @@
+kst (2.0.3-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add debian/patches/fix-qreal-vs-double-for-arm.diff from Peter Green to
+fix FTBFS on armel and armhf (Closes: #646423)
+
+ -- Scott Kitterman sc...@kitterman.com
) to dh_python2; closes: #617019.
+ * Add misc:Depends
+
+ -- Scott Kitterman sc...@kitterman.com Tue, 13 Dec 2011 23:46:13 -0500
+
python-pypcap (1.1.2+debian-2) unstable; urgency=low
* Patch setup.py to search pcap/pcap.h as well as pcap.h for needed
diff -u python-pypcap-1.1.2+debian
close 648956 1.10-2+b1
thanks
Fixed with binNMU.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
It's being addressed. See #647210.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Maybe #647210 is the same. I'll try to investigate if I have connectivity this
week.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Probably just qwt.
IIRC last time I updated python-qt4, qwt didn't like it either. I
believe qwt does a runtime check and aborts as you describe if the
version doesn't match what it was compiled again.
I don't think this is actually a python-qt4 bug, but a feature of qwt.
I will be
close 582307
Package removed from Unstable and Testing.
thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I rebuilt monkeystudio ovito juffed serna-free tora universalindentgui smokeqt
(skipping salome as previously mentioned) with the newest qscintilla2 from
upstream.
serna-free FTBFS for other reasons and is RC buggy (55) so I won't
consider it further.
ovito juffed tora universalindentgui
kscope FTBFS due to 631779, but gets to that stage with the new qscintilla2,
so is probably fine.
smokekde builds fine.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Great. I'll leave it to you then. All the other rebuilds seem to be going
well, so the way is clear whenever you're ready.
Thanks and sorry for the short notice.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
There's a new version of qscintilla2 that I hadn't packaged yet (waiting for
the python-dbus transition to finish) that properly bumps the soname/version to
6.1.0. I'll rebuild the packages that build-depend on libqscintilla2-dev. It
looks like the relevant pacakges are:
monkeystudio ovito
Package: pyqwt5
Version: 5.2.1~cvs20091107+dfsg-5
Severity: serious
Justification: fails to build from source
libqwt5-qt4-dev is no longer available in Sid due to qwt transitioning to
qwt6, so the package FTBFS.
-- System Information:
Debian Release: squeeze/sid
--
To UNSUBSCRIBE, email to
Package: guiqwt
Version: 2.1.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
python-qwt5-qt4 is currently broken and not expected to be fixed anytime soon.
The following packages have unmet dependencies:
python-qt4: Breaks: python-qwt5-qt4 (
Package: archivemail
Version: 0.8.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Using python and python-minimal from Experimental, the package FTBFS.
The last bit of the build log:
../test_archivemail
Patch attached.
Scott K
Fixes FTBFS with KDE 4.5 and later, patch from Ubuntu.
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/natty/kcheckgmail/natty/revision/18
diff -Nur -x '*.orig' -x '*~' kcheckgmail-0.6.0//doc/en/index.docbook kcheckgmail-0.6.0.new//doc/en/index.docbook
---
:20.0 -0400
@@ -1,3 +1,10 @@
+bsfilter (1:1.0.17-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add docbook-to-man to build-depends to fix FTBFS (Closes: #625195)
+
+ -- Scott Kitterman sc...@kitterman.com Thu, 05 May 2011 00:18:35 -0400
+
bsfilter (1:1.0.17-1) unstable; urgency
Package: subversion
Version: 1.6.16dfsg-1
Severity: serious
Justification: fails to build from source
The package FTBFS on ia64 and kfreebsd-* when binNMUed for the current Python
transition. Here are the relevant snippets from the build logs:
Tail of logs for subversion on ia64:
Test Summary
Package: quantlib-swig
Version: 1.0.0-1
Severity: serious
Justification: fails to build from source
This package was binNMUed as part of the transition to add python2.7 to
supported python versions. It failed on multiple archs. Here is an
excerpt of the build logs:
Now is a good time.
Package: python-omniorb
Version: 3.5-1
Severity: serious
Justification: fails to build from source
During a binNMU for the python-defaults transition, adding python2.7 and
dropping python2.5 in supported versions, python-onmiorb FTBFS. The relevant
build log snippet is:
Listing
Package: radare
Version: 1:1.5.2-3
Severity: serious
Justification: fails to build from source
During a recent binNMU to support changes in supported python versions, radare
FTBFS on all architectures. The relevant error from the build logs is:
radare (= 1:1.5.2-3) build-depends on missing:
-
znc is the last package in the archive that depends on python3.1. FYI, this
bug is blocking python3.1 removal.
signature.asc
Description: This is a digitally signed message part.
I can't actually test this in Debian due to this bug, but it looks like once
it's fixed there's a python2.7 compatibility issue that will need to be
addressed (fortunately with patch):
https://bugs.launchpad.net/pyopenssl/+bug/686804
signature.asc
Description: This is a digitally signed
This is blocking the python3.1 - 3.2 transition. see #617272 for details of
the transition.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: python-drizzle
Version: 1.0-1
Severity: serious
Justification: fails to build from source
python-drizzle was just binNMUed in support of the python3 transition. On all
archs where the new drizzle built, python-drizzle FTBFS. The relevant build
log excerpt is:
dh build --with
I'll have another look at it and get back to you. I suspect a copy/paste error
on my part as it built here. Is your planned upload published somewhere? Maybe
it interacts poorly with one of the other planned changes?
My diff was incomplete (needed to remove python3-apt-dbg.install too), but
since you've resolved it, I'll leave it be. Thanks.
801 - 900 of 966 matches
Mail list logo
