Package: src:banshee-extension-mirage
Version: 0.5.0-2
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS this way:
| checking pkg-config is at least version 0.9.0... yes
| configure: error: Package requirements (banshee-1-thickclient >= 1.3.2) were
not met:
|
| Package taglib-sharp
tag 566289 pending
thanks
Raphael Geissert (22/01/2010):
> P.S. if this bug isn't fixed by one of the current BSPs I plan to
> fix it in the following days via a 1-day delay NMU. If you intend
> to fix it, in less than three days, say it NOW.
Is NOW still early enough? Feel free to provide us w
Hi,
please investigate removal of adolc, which has been RC-buggy since
August 2008 (#496490), without any single reply from the maintainer,
even though Neil Williams tried to give him a hand.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Package: libsndfile
Version: 1.0.21-1
Severity: serious
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
your package now FTBFS on kfreebsd-* since there are some symbols
issues. You can browse the build logs at the usual place:
https://buildd.debian.org/status/pack
Tanguy Ortolo (14/12/2009):
> It seems that toilet does not work at all, because it searches for
> libcucul.so.0, that does not exist anymore, replaced by libcaca, I
> think.
Well, see its Depends line. See libcaca0's contents.
> Here is the symptom:
> % toilet
> toilet: error while loading shar
Package: postgresql-plsh
Version: 1.3-2
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on various archs[1]:
| creating pgplsh.la
| (cd .libs && rm -f pgplsh.la && ln -s ../pgplsh.la pgplsh.la)
| . pgplsh.la && sed
"s,%filename%,/build/buildd/postgresql-plsh-1.3/debian/postgresql-
Package: ounit
Version: 1.0.3-4
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on all archs:
| Working on:
/build/buildd-ounit_1.0.3-4-hppa-lJs0GD/ounit-1.0.3/doc/manual/src/OUnit.xml
|
openjade:/build/buildd-ounit_1.0.3-4-hppa-lJs0GD/ounit-1.0.3/doc/manual/src/OUnit.xml:3:46:E:
Barak A. Pearlmutter (15/12/2009):
> > even though Neil Williams tried to give him a hand.
>
> He did? I'd be happy to have a co-maintainer.
He did: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496490#8
Mraw,
KiBi.
signature.asc
Description: Digital signature
John MacFarlane (08/12/2009):
> > [ 7 of 29] Compiling Text.Pandoc.ODT ( src/Text/Pandoc/ODT.hs,
> > dist/build/Text/Pandoc/ODT.o )
> >
> > src/Text/Pandoc/ODT.hs:49:24:
> > Template Haskell splice illegal in a stage-1 compiler
> > makeZip $ "data" "odt-styles"
> > make: *** [bui
Brian May (17/12/2009):
> See bug #561401.
See bug #557667?
Mraw,
KiBi.
signature.asc
Description: Digital signature
Package: subunit
Version: 0.0.4-1
Severity: serious
Justification: FTBFS
| configure: error: Package requirements (cppunit) were not met:
| No package 'cppunit' found
meh.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
Robert Collins (19/12/2009):
> Format: 1.8
> Date: Sun, 20 Dec 2009 10:30:19 +1100
> Source: subunit
> Binary: subunit libsubunit-perl python-subunit libsubunit0 libsubunit-dev
> libcppunit-subunit0 libcppunit-subunit-dev
> Architecture: source amd64 all
> Version: 0.0.4-2
> […]
> Changes:
> su
Robert Collins (20/12/2009):
> Thank you for drawing my attention to this bug.
You're very welcome.
> I'm not the maintainer, and uploaders don't get copied on new bugs,
> so I wasn't aware of it. I certainly shall address this promptly.
So what? Comaintainers are supposed to be subscribed to t
Package: guile-1.6
Version: 1.6.8-7
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on various archs (alpha, hppa, kfreebsd-amd64 as of
today, but some still are in Needs-Build state):
| /usr/bin/make check-TESTS
| make[3]: Entering directory `/build/buildd/guile-1.6-1.6.8'
| Testi
Robert Collins (20/12/2009):
> > So what? Comaintainers are supposed to be subscribed to the PTS
> > and receive mails related to the packages they're supposed to
> > maintain.
>
> It would be nice if the PTS mailed me, but it doesn't, for whatever
> reason.
Since you're not saying whether you a
Robert Collins (20/12/2009):
> > If you:
> > - start doing some QA checks before uploading your package;
>
> I already do such checks.
I'm wondering how the obviously missing B-D went unnoticed then. I
thought checking ones package builds fine in a clean chroot was
supposed to be on everyone's
Rob Browning (20/12/2009):
> OK, I'm looking in to it. The hppa failure is probably a mistake I
> made when pulling in the configure options changes; I'm not sure
> about the others yet.
If you need a testbuild on kfreebsd-amd64, I can perform it if you
provide me with either a patch against the
Package: geda-gaf
Version: 1:1.6.0-1
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on all buildds. Build logs at the usual place:
https://buildd.debian.org/status/package.php?suite=unstable&p=geda-gaf
Log excerpt:
| fail=0 ; \
| pass=0 ; \
| for file in ./*.sym; do
Package: scim-unikey
Version: 0.3.1+debian-1
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on all buildds:
| make[3]: Entering directory
`/build/buildd-scim-unikey_0.3.1+debian-1-alpha-dXKpPj/scim-unikey-0.3.1+debian/ukengine'
| /bin/bash ../libtool --tag=CXX --mode=compile g++
reopen 561908
found 561908 1.8-3
thanks
Debian Bug Tracking System (21/12/2009):
> Changes:
> potrace (1.8-3) unstable; urgency=low
> .
>* Add autoconf to Build-Depends (Closes: #561908)
You certainly didn't check your package was building fine before
uploading…
| autoreconf -i -s
| Can'
Package: njb-sharp
Version: 0.3.0-4
Severity: serious
Justification: FTBFS
Hi,
it looks like you're (now?) missing some Build-Depends:
| checking for mono... /usr/bin/mono
| checking for csc... no
| configure: error: Can not find "csc" in your PATH
| make: *** [config.status] Error 1
| dpkg-build
Hi.
Iain Lane (21/12/2009):
> a lot of packages will now FTBFS due to this. We will fix them all
> in parallel with the -dev transition that is also taking place
> currently.
Okay. I assume most of the mono packages are maintained under your
umbrella, so you probably will know about those FTBFSe
Hamish Moffatt (21/12/2009):
> This is a mystery to us and to upstream. The tests are comparing the
> output of the gsymcheck program with pre-prepared output via
> diff. From the diff output it looks like the newly built gsymcheck
> is producing no output at all.
>
> It behaves ok in pbuilder, a
Cyril Brulebois (04/12/2009):
> Package: rotter
> Version: 0.8-1
> Severity: serious
> Tags: patch
> Justification: FTBFS
I've just uploaded an NMU to fix this. Please find attached the source
debdiff.
Mraw,
KiBi.
diff -u rotter-0.8/debian/changelog rotter-0.8/debian/chan
أحمد المحمودي (21/12/2009):
> On Mon, Dec 21, 2009 at 08:49:47PM +0200, أحمد المحمودي wrote:
> > Yet, the failing test is in gsymcheck not in gnetlist !
And?
| HOME=/foo make -C gsymcheck/tests check
| make: Entering directory
`/srv/storage/kibi/hack/porting-2/geda-gaf-1.6.0/gsymcheck/tests'
| m
Package: cynthiune.app
Version: 0.9.5-9
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on both amd64 and kfreebsd-amd64:
| gcc CynthiuneHeaderCell.m -c \
| -MMD -MP -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1
-DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -D_REENT
Package: magics++
Version: 2.6.4~dfsg-1
Severity: serious
Justification: FTBFS
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hamish Moffatt (22/12/2009):
> Yes... the i386 autobuilder just succeeded on -3 so perhaps we have
> success at last.
Worked on my buildds too. ;)
As for -2 on armel, it might just be that the home directory is
writable? Anyway, never rely on HOME existing and being writable. ;)
Mraw,
KiBi.
s
Yavor Doganov (22/12/2009):
> Thanks for the report.
No problem.
> Does the package build successfully with noopt? I would put my bet
> that there's no ICE with -0O. If so, it would be hard [1] to figure
> out in which version the GCC regression occurred, because the last
> few successful buil
Yavor Doganov (22/12/2009):
> Thanks, I didn't know about this facility. But I'm not sure how it
> would help me in this particular situation.
In this very particular situation, I don't think it would help, but in
the general ICE case, it might be interesting to know whether early
4.4 releases w
Package: magics++
Version: 2.8.0.dfsg-1
Severity: serious
Justification: FTBFS
Congratz! You failed *yet again* to upload a buildable package!
| autoreconf -if
| configure.ac:79: error: possibly undefined macro: AC_DISABLE_STATIC
| If this token and others are legitimate, please use m4_patte
Yavor Doganov (23/12/2009):
> Don't bother, please -- I managed to reproduce the ICE on fencepost
> with a manually built GCC 4.4.2. Thanks for your efforts.
Okay. And you're welcome, again. ;)
> Now, what are the options to deal with this FTBFS until the GCC bug
> is fixed?
>
> 1) Compile wit
Yavor Doganov (23/12/2009):
> Therefore I plan to wait a few more days before resorting to 1).
Probably okay provided your package isn't entangled in a huge
transition and blocking migration to testing for a few dozens or
hundreds of packages. ;)
Mraw,
KiBi.
signature.asc
Description: Digital
Pino Toscano (22/12/2009):
> Excellent finding, I have prepared a patch that should make it build
> even with read-only home. Patch (with a bit longer explanation) is
> attached. Looks working correctly here, feel free to give it a
> test.
Seems to be working fine indeed:
- HOME=/doesnotexist d
Alastair McKinstry (23/12/2009):
> This is building fine locally under pbuilder. Rebuilding from a
> fresh install of sid ...
Your pbuilder chroot is broken then. It just can't be building fine
given the Build-Depends you're trying to use. (And since I tend to
doublecheck, I just reproduced this
og
+++ fontconfig-2.8.0/debian/changelog
@@ -1,3 +1,12 @@
+fontconfig (2.8.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Re-apply Riku's band-aid (introduced in 2.6.0-4.1 and 2.6.0-4.2, which
+were not ACK'd) to unbreak the buildds again: Use “set +e” in postinst
+
Package: defoma
Version: 0.11.10-3
Severity: grave
Justification: Fucks up fontconfig (at least), then buildds.
Hi,
dh_installdefoma leads to this kind of code in maintainer scripts:
test -x `which foo` && foo bar baz
The trick being that if foo isn't found by which, “foo bar baz” gets
execute
Keith Packard (30/12/2009):
> > I'm about to QA-upload defoma with this change in the various
> > debhelper-files/* files, but I wanted to open this bugreport for
> > reference.
Fortunately, I didn't do so, that wouldn't have helped (yay for
sleeping before uploading :)).
> Here's a patch which
Keith Packard (30/12/2009):
> I haven't received any mail about RC bugs today, and can't find any
> through the bugs.debian.org web interface.
I meant #559136 and #560252, opened for some weeks.
> > 2. optionally fix them;
>
> I'm trying, but it looks like dh_installdefoma is just plain busted
(Never heard of Cc'ing bug submitters?)
gregor herrmann (20/12/2009):
> > It looks like the clutter-doc package was missing from the last
> > upload (cfr. .changes files) but still exists in debian/control
> > and .dsc files.
>
> Rebuilding the package brings back to missing binary
> package. bi
YOSHINO Yoshihito (31/12/2009):
> Hello,
Hi,
> test -x "`which foo`" && foo bar baz
>
> returns status 1, which comes to an error if a script executed this
> as the last command. E.g. like #563121, prerm will exit with status
> 1 if defoma not found unless explicitly writing the last line "exit
Cyril Brulebois (31/12/2009):
> Current/common practice within debhelper seems to be:
> | if [ -x "`which foo 2>/dev/null`" ]; then…
>
> I think I'm going to upload with such a change once I'm up (for
> real, not vaguely opening eyes).
Hi again,
I've
Keith Packard (31/12/2009):
> Check out the 'bash' manual -- set -e explicitly excludes precisely
> this case from causing early termination of the script:
> […]
Alrighty. I must confess I'm not really keen on checking what happens
in the various shells, but that seems to be true under dash as we
Keith Packard (31/12/2009):
> Right, I didn't realize there was a bug in defoma as well which was
> causing this problem; having found an obvious bug in my packaging, I
> thought that would have fixed the bug; sorry for not testing it
> properly.
Oh well, since in the end, final fixes are flowing
Package: fuzz
Version: 0.6-9
Severity: serious
Tags: patch
Justification: FTBFS
Hi,
your package FTBFS on the buildds:
| dpkg-genchanges -B -mDebian Build Daemon
>../fuzz_0.6-9_alpha.changes
| dpkg-genchanges: arch-specific upload - not including arch-independent
packages
| dpkg-genchanges: e
Package: automoc
Version: 1.0~version-0.9.88-3
Severity: grave
Justification: Breaks many rbdeps.
Hi,
as mentioned on IRC, many qt/kde builds (e.g. kde-style-qtcurve or
kdiff3) are broken by this version of automoc. I also confirmed
reverting to squeeze's version (1.0~version-0.9.88-2) make those
Package: cyrus-imapd-2.2
Version: 2.2.13-17
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on the buildds for the +b1 binNMU round:
| applying patch 99-update-autoconf to ./ ...
| patching file config.guess
| patching file config.h.in
| patching file config.sub
| patching file conf
Package: linux-atm
Version: 1:2.5.1-1.1
Severity: serious
Justification: FTBFS
(NMUer X-D-Cc'd.)
Guess what, you failed:
| make: autoreconf: Command not found
Mraw,
KiBi.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
Package: dpkg-ruby
Version: 0.3.3
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS:
| mkdir -p ext/ruby1.9 ext/ruby1.8
| ruby1.9 -C ext/ruby1.9 ../debian_version/extconf.rb
| make[1]: ruby1.9: Command not found
Full build logs at the usual place:
https://buildd.debian.org/status/p
Package: cgdb
Version: 0.6.5-1
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS:
| dh_installinfo doc/cgdb.info
| rm: cannot remove
`/build/buildd-cgdb_0.6.5-1-alpha-1J96aG/cgdb-0.6.5/debian/cgdb/usr/share/info/dir':
No such file or directory
| rm
/build/buildd-cgdb_0.6.5-1-alpha-
Package: aptitude
Version: 0.6.1.3-2
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on various archs, including at the moment: alpha,
amd64, hppa, ia64, kfreebsd-amd64, sparc.
Log excerpt:
| if g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../.. -I../../src
-I../../intl -I/usr/i
Package: f-spot
Version: 0.6.1.5-1
Severity: serious
Tags: patch
Justification: FTBFS
Hi,
quoting the changelog for libflickrnet (1:2.2.0-2):
| libflickrnet (1:2.2.0-2) unstable; urgency=low
|
|* debian/control,
| debian/rules,
| debian/libflickrnet-cil-dev.install,
| debian/l
Iain Lane (21/11/2009):
> forcemerge 556802 557380
> tags 556802 + pending
> thanks
Oops, missed the other bug, looks like I was on bdo/f-spot rather than
bdo/src:f-spot. Sorry about that.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Yaroslav Halchenko (23/11/2009):
> Since networkx is shipped with nice unittests battery I would advise
> to make used of it while building the package -- might catch you
> before you upload not tested package :-P (or it does not fail on
> your box? just curious)
Do you mean that?
| Python 2.5.4
Yaroslav Halchenko (24/11/2009):
> […] 'installed' version unless 'nocheck' is provided in
> DEB_BUILD_OPTIONS... smth like
>
> install/python-nipype::
> ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
> PYTHONPATH=$(DEB_DESTDIR)/usr/lib/python2.5/site-packages python -c
> "import nipype;
Yaroslav Halchenko (24/11/2009):
> indeed weird why -2 is not there anywhere... I guess that is the
> one which would close this bug?
Obviously, yes. debcheckout is still your friend.
> ftp://ftp.upload.debian.org/pub/UploadQueue/ -- has no sign of it
> http://ftp-master.debian.org/deferred/ -
Package: libserf-0-0-dev
Version: 0.3.0-1
Severity: serious
Justification: Fails to install.
Hi,
it looks like your package is missing a Replaces or even a Conflicts
against older libserf-0-0 packages:
| Preparing to replace libserf-0-0-dev 0.3.0-0.3 (using
.../libserf-0-0-dev_0.3.0-1_kfreebsd-i
Package: libbft
Version: 1.1.1-2
Severity: serious
Tags: patch
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
it looks like the check is buggy and suffers from a tiny typo: a missing
_LONG. See the HAVE_LONG_LONG check the line before and the typedef on
long long th
Package: crawl
Version: 2:0.5.2-1
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS:
| Unpack source
| ─
|
| dpkg-source: warning: -sn is not a valid option for
Dpkg::Source::Package::V3::quilt
| gpgv: keyblock resource `/srv/buildd/.gnupg/trustedkeys.gpg': file open err
Guus Sliepen (27/11/2009):
> Do you have any idea how I could investigate this further?
Sure: #558233
Mraw,
KiBi.
signature.asc
Description: Digital signature
Package: xfe
Version: 1.32.1-1
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on almost all buildds:
https://buildd.debian.org/status/package.php?suite=unstable&p=xfe
Log excerpt:
| checking for gcc... ccache cc
| checking for C compiler default output file name...
| configure:
Cyril Brulebois (28/11/2009):
> Log excerpt:
> | checking for gcc... ccache cc
> | checking for C compiler default output file name...
> | configure: error: C compiler cannot create executables
While I'm at it, there's no way ccache should be specified in
debian/rule
Package: performous
Version: 0.3.2-1
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on various archs as can be seen on [1]. Currently
that means hppa and kfreebsd-* (where binNMUs got scheduled), but that
also happens in amd64 sid chroots, so that's not an arch-related oddity.
Prob
Package: vtk
Version: 5.2.1-13
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on various archs[1] with this error:
| -- Found MPI: /usr/lib/lam/lib/liblammpio.so
| CMake Error: The following variables are used in this project, but they are
set to NOTFOUND.
| Please set them or mak
Package: vtk
Version: 5.2.1-13
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on kfreebsd-* with this error:
| 65. ERROR in
/build/buildd-vtk_5.2.1-13-kfreebsd-i386-uedLVA/vtk-5.2.1/Build/java/vtk/vtkMPIController.java
(at line 47)
| public vtkMPIController CreateSubControl
merge 556843 558660
thanks
signature.asc
Description: Digital signature
Package: krb5
Version: 1.7+dfsg-2
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on buildds on both linux and kfreebsd-* archs with
the following output (e.g. on i386):
| dpkg-gensymbols: warning: new libraries appeared in the symbols file:
encrypted_challenge.so.0
| dpkg-gensymbo
Sam Hartman (29/11/2009):
> I realize it's not your job, but any ideas on how to convince
> dpkg-gensymbols to behave as it used to?
Let me try and reproduce this in a sid environment, I don't have any
build tree to play with yet. I'm no dpkg-* master, and I might fall
asleep before it completes,
Russ Allbery (29/11/2009):
> I suspect that the change is in dh_makeshlibs, which tells
> dpkg-gensymbols which libraries to generate symbols for. Excluding
> the file in dh_makeshlibs (using -X) would work.
Probably; and it indeed works:
| dh_lintian
| set -e ; for pkg in libkrb5-3 libgssapi-kr
Jonathan Yu (29/11/2009):
> An alternative arrangement I'd be open to is: /usr/bin/pip points to
> a sh script, which tells the user that `pip' has been renamed to
> perl-pip and python-pip in Debian. This way, neither pip gets the
> /usr/bin/pip name.
Mentioning $LANG in the binary is the way to
Package: cups
Version: 1.4.2-2
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on buildds:
| g++ -Wall -Wno-format-y2k -fPIC -Os -g -fstack-protector -D_GNU_SOURCE
-Ioprs -Iopvp -I../opvp -I../.. -I.. -D_CUPS_SOURCE -I/usr/include/poppler
-I/usr/include/poppler -DPDFTOPDF -g -O2
Package: netatalk
Version: 2.0.5-2
Severity: serious
Justification: FTBFS
While having a look on a porter box, I've noticed your package can't be
autoreconf'd, which it tries to do when autotools packages (autoconf*,
automake*, libtool) are installed:
| /usr/bin/make all-recursive
| make[2]: Ente
Jonas Smedegaard (01/12/2009):
> My builds using cowdancer+pbuilder on amd64 and i386 with a fully
> up-to-date Sid shows no such things.
Note I'm talking about porter boxes, so a bit more than just chroot +
Build-Depends.
> Perhaps some environment variables makes cdbs or libtool choke, or
> so
Frank Lahm (01/12/2009):
> You're (well not you, the Debian build infrastructure) messing up
> the autotools environment. Netatalk 2.0.5 comes with: $ ./libtool
> --version ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4
> (1.1220.2.365 2005/12/18 22:14:06)
Yes, that was the point of this bugrepor
Package: frama-c
Version: 20090901+beryllium+dfsg-2
Severity: serious
Justification: FTBFS
Your package FTBFS on all architectures with:
| ocamlc -c -w Ael -warn-error A -annot -g -I src/misc -I src/ai -I
src/memory_state -I src/toplevel -I src/slicing_types -I src/pdg_types -I
src/kernel -I s
Package: gpe-calendar
Version: 0.92-3
Severity: serious
Tags: patch
Justification: FTBFS
Hi,
it looks like libmimedir-gnome0-dev vanished without your being
notified. It also looks like today (since libmimedir-gnome 0.4.2-2)
one should be using libmimedir-gnome-dev instead.
Mraw,
KiBi.
--
To
Those trivial bugs have been around for quite some time. Any chance
to get them fixed? Some packages are blocked in the BD-Uninstallable
state because of those missing packages.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Package: rotter
Version: 0.8-1
Severity: serious
Tags: patch
Justification: FTBFS
Hi,
your package FTBFS since libmp3lame-dev isn't available. Given the
longstanding bug in sbuild when one Build-Depends on A|B (#403246), you
probably want to switch the order for this alternative. Tagging as patch
in once the SONAME is bumped again
+(Closes: #552712).
+ * Set urgency to “high” since it also affects testing: liboggz migrated
+already.
+
+ -- Cyril Brulebois Sat, 05 Dec 2009 02:40:22 +0100
+
libkate (0.3.7-1) unstable; urgency=low
* New upstream release.
diff -u libkate-0
reopen 555004
thanks
Debian Bug Tracking System (28/11/2009):
> This is an automatic notification regarding your Bug report
> which was filed against the r-base-core-ra package:
>
> #555004: Please remove build-dependency on xpdf-reader
>
> It has been closed by Dirk Eddelbuettel .
I'm probabl
Chris Lamb (08/08/2009):
> > During a rebuild of all packages in sid, your package failed to
> > build on amd64.
>
> I just tried building a newer upstream verison of uuagc (0.9.10) and
> it built fine using the debian/ directory from 0.9.6-1.
Thanks.
Arjan, any plan to fix this RC bug? Some ar
Dirk Eddelbuettel (04/12/2009):
> Great catch, thanks!
No problem, I'm just glad my tool to generate graphs of chains of
(build-)dependencies for GNU/kFreeBSD has the nice side-effect of
finding RC bugs that still apply. :)
> So the bug is now really closed with a fresh 1.8.2-2 upload with a
> f
Package: haskell-configfile
Version: 1.0.5-3
Severity: serious
Justification: FTBFS
Your package FTBFS:
| debian/hlibrary.setup build
| Preprocessing library ConfigFile-1.0.5...
| Preprocessing executables for ConfigFile-1.0.5...
| Building ConfigFile-1.0.5...
| [1 of 4] Compiling Data.ConfigFile.
Erik de Castro Lopo (05/12/2009):
> Unfortunately it is not as trivial as you make out.
From where I sit, that pretty much looks like a missing (versioned?)
Build-Depends or something similar. Which makes me call it “trivial”
indeed.
> The probelms I am still stuck with are:
>
> a) It won't
Package: hdbc-postgresql
Version: 2.2.0.0-1
Severity: serious
Justification: FTBFS
Lalalala:
| dh_installdirs: Compatibility levels before 5 are deprecated.
| # Add here commands to install the package into debian/tmp
| #/usr/bin/make install
DESTDIR=/build/buildd-hdbc-postgresql_2.2.0.0-1-kfreeb
Package: hdbc-odbc
Version: 2.2.0.0-1
Severity: serious
Justification: FTBFS
Lalalala:
| dh_installdirs: Compatibility levels before 5 are deprecated.
| # Add here commands to install the package into debian/tmp
| #/usr/bin/make install
DESTDIR=/build/buildd-hdbc-odbc_2.2.0.0-1-kfreebsd-i386-p7Vc
Package: sbuild
Version: 0.59.0-1
Severity: serious
Justification: Fucked my uploads.
Hi,
firstly, I'm aware of #529281, and I believe this might be different.
I really don't see why the resulting distribution should be “unstable”
when one uses:
$ sbuild -c experimental-amd64-sbuild -s -A foo.ds
Package: hpodder
Version: 1.1.5.0+nmu1
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS:
| Preprocessing executables for hpodder-1.1.5...
| Building hpodder-1.1.5...
| [ 1 of 20] Compiling Types( Types.hs,
dist/build/hpodder/hpodder-tmp/Types.o )
| Failed to load interfa
Hi Roger.
Roger Leigh (06/12/2009):
> Currently, the reason why your uploads default to unstable is
> because sbuild defaults to unstable unless you override it.
Yeah, I gathered that… :)
> I think the safest solution here is to simply not set it by default,
> and require the user to always spe
ython-dmidecode (3.10.7-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix missing Build-Depends: libxml2-dev (Closes: #548669).
+ * Also add python-libxml2 since it's needed for -lxml2mod.
+ * Use “>=” instead of single “>” in Build-Depends, the latter being
+deprec
Fernando M. Maresca (14/11/2009):
> I sent to Hamish for review and eventual upload. Hope it's ok.
Hi,
next time, you could link to a public .dsc (e.g. on mentors.debian.net
or on alioth), so that you could get sponsored if your usual sponsor
is busy. You could also mark this bug with patch & pe
-maintainer upload.
+ * Disable calling debian/mtcheck from debian/rules, boost no longer
+distinguishes between single-threaded and multi-threaded variants, so
+this check only generates FTBFSes (Closes: #545621).
+
+ -- Cyril Brulebois Sun, 06 Dec 2009 21:32:30 +0100
+
regina-normal (4.6-1) uns
Ben Burton (07/12/2009):
> Thanks for this
'Welcome.
Mraw,
KiBi.
signature.asc
Description: Digital signature
ev's #559771: add libgtkhtml3.14-dev
+to Build-Depends. That fixes the FTBFS due to missing gtkhtml/*.h
+includes when including
+ /usr/include/evolution-2.28/mail/em-format-html.h (Closes: #549745).
+
+ -- Cyril Brulebois Mon, 07 Dec 2009 01:30:33 +0100
+
mail-notification
after having looked into Ubuntu (Closes: #540669).
+ * Also fix FTBFS with new automake by matching automake1.11 in
+admin/cvs.sh, as suggested in the same bugreport.
+
+ -- Cyril Brulebois Mon, 07 Dec 2009 02:33:22 +0100
+
kflickr (0.9.1-2.1) unstable; urgency=medium
* Non-maintaine
Kurt Roeckx (15/08/2009):
> Source: kde-style-qtcurve
> Version: 0.65.1-1
> Severity: serious
I believe I found the issue: config.h's line 6 is about prefix. As can
be seen in a cowbuilder build log:
| -- Found automoc4: /usr/bin/automoc4
| ** PREFIX=/usr
| -- Configuring done
| -- Generating don
@ -1,3 +1,13 @@
+ktoon (0.8.1-4.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Fix FTBFS due to missing zlib.h by adding zlib1g-dev to
+Build-Depends. It was previously indirectly pulled in.
+ Thanks to Peter Green for the analysis (Closes: #527721).
+ * Set urgency to “high” s
virtual
+package on many architectures, and since versioned Provides aren't
+supported (Closes: #540427, #554638).
+
+ -- Cyril Brulebois Mon, 07 Dec 2009 03:49:49 +0100
+
jconv (0.8.1-1) unstable; urgency=low
* Initial release (Closes: #520083)
signature.asc
Description: Digital signature
eft it statically
+ included instead of dynamically regenerating.
+ - This fixes the FTBFS due to undefined references during linking
+ (Closes: #527732).
+ - This obviously also fixes the use of embedded code copy reported by
+ Stéphane Glondu (Closes: #550058).
+
+
Package: libfvm-dev
Version: 0.14.0-2
Severity: serious
Tags: patch
Justification: Broken shared objects
Hi,
as discussed quickly in #557020, libfvm might have some undefined
references. So I added -Wl,-z,defs to CFLAGS, and then noticed 900+
undefined references.
Please find attached a patch to
1301 - 1400 of 2925 matches
Mail list logo
