Oops, misread the test log - thanks for pointing out my error.
The patch looks good to me as a workaround, assuming it fixes the FTBFS
(I would expect it to).
I'll try to sort out a better fix for the next upstream release.
--
topercent2 test fail on i386 and lpia causing FTBFS
https://bugs.lau
I've just uploaded xapian-core 1.0.13-2 to Debian unstable, which should
fix this issue.
I'd suggest just syncing this version to karmic (at least if it does OK
on the debian buildds for the archs Ubuntu supports), but FYI this is
the patch I added (which also addresses another testsuite bug - the
Just to note that xapian-core 1.0.13-3 has now been synced from debian
and built successfully for all archs, so xapian-omega can now be synced
(currently debian has 1.0.13-1).
--
Please sync xapian-omega (1.0.12-1) from Debian unstable
https://bugs.launchpad.net/bugs/374171
You received this bug
This testcase is also failing for hurd-i386 on Debian, though with a
different backend (your failures are for flint, the hurd-i386 is for
remote-prog):
http://buildd.debian-ports.org/fetch.php?pkg=xapian-
core&arch=hurd-i386&ver=1.0.12-2&stamp=1241429577&file=log&as=raw
I haven't investigated thi
Thanks.
It seems that max_possible is out by a factor of almost exactly (1 +
DBL_EPSILON), and everything else is the same, so this doesn't seem to
indicate a real problem.
I'll try to find a fix for this, but I'd suggest just adding this to the
top of the testcase topercent2 for now:
SKIP_T
gutsy has now reached end of life, so there's no point at all this
staying open.
** Changed in: oprofile (Ubuntu Gutsy)
Status: New => Invalid
--
[SRU] for oprofile, edgy-updates: bashism in oprofile's opcontrol script
prevents user from setting any events
https://bugs.launchpad.net/bugs
wlx: That bug doesn't look connected to me.
This bug is that the patch Debian apply to libtool to stop it explicitly
linking with a library's dependencies hasn't been correctly updated to
work with libtool >= 2.2. The effect is that more libraries are linked
against than would be if the patch wor
Luca Falavigna has already uploaded a xapian-omega package with a
workaround:
https://launchpad.net/ubuntu/+source/xapian-omega
But this is a regression in the debian version of libtool which is
likely to make some other packages in intrepid FTBFS in a similar way
(if they've not been updated sin
** Attachment added: "Patch added in 1.0.7-4"
http://launchpadlibrarian.net/18515424/xapian-core-elite-set-excess-precision.patch
--
Please consider syncing xapian-core 1.0.7-4 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/282961
You received this bug notification becaus
Public bug reported:
I've recently uploaded xapian-core 1.0.7-4 to Debian unstable and it's been
accepted for lenny. It adds one small safe patch over 1.0.7-3 which intrepid
currently has, and I felt I should highlight it for consideration for intrepid
too,
even at this late stage.
In a nutshel
Public bug reported:
Binary package hint: update-manager
Starting the upgrade from hardy to intrepid I get an error dialog:
Not enough free disk space
The upgrade aborts now. The upgrade needs a total of 1260M free
space on disk '/'. Please free at least an additional 308M of disk space
It would be good to get this trivial fix into intrepid though...
--
distribution upgrade tool reports "kb/s" but is measuring "kB/s"
https://bugs.launchpad.net/bugs/189454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
I believe 1.0.3-3ubuntu1 fixed this bug (by adding zlib1g-dev to "Build-
Depends"):
http://changelogs.ubuntu.com/changelogs/pool/universe/x/xapian-omega
/xapian-omega_1.0.7-3ubuntu1/changelog
I would mark this as closed, but it was just triaged by Luca Falavigna
who also made the upload above, so
Public bug reported:
1.0.7-3 includes a backported fix from upstream SVN for a database corruption
bug.
It's not a bug which everyone will hit, but it has affected several users
independently.
The upstream bug report is: http://trac.xapian.org/ticket/287
Other than this, there are several less
Public bug reported:
1.0.7-3 fixes the following packaging-related Debian bugs which were all
present in 1.0.5-1 (the version currently in intrepid):
462106 [python-xapian] python-xapian: Laxist Depends: on libxapian15
493941 [php5-xapian] php5-xapian does not work out of the box, php config file
Just to note, xapian-bindings has a build dependency on libxapian-dev
(>= 1.0.7); libxapian-dev comes from xapian-core and xapian-core 1.0.7-3
was synced earlier today (LP#256759).
--
Please sync xapian-bindings 1.0.7-3 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/256915
Just to note a side-effect of creating these symlinks is that the
command-not-found package gives a somewhat suprising answer for gcc-4.3
and g++-4.3:
$ g++-4.3
The program 'g++-4.3' is currently not installed. You can install it by typing:
sudo apt-get install hardening-wrapper
bash: g++-4.3: co
Public bug reported:
Binary package hint: xapian-omega
1.0.7-3 fixes the following Debian bug which is present in 1.0.5-1 (the
version currently in intrepid):
484456 [xapian-omega] black on dark blue in search results can be hard
to read
Updating would also update the debian packaging to standa
Public bug reported:
Binary package hint: libsearch-xapian-perl
Updating would fix this Debian bug:
486138 crashes hard when asked to generate a stemmer for an unsupported
locale
Updating would also update the debian packaging to standards-version
3.8.0.
The upstream changes from 1.0.5.0-1 are
Public bug reported:
Binary package hint: foobillard
On hardy (8.04.1) on my laptop, foobillard 3.0a-3ubuntu1 always colours
the table cloth and cushions black, except for the "fB" logo in the
centre of the the cloth, which is correctly coloured according to the
current choice of table colour. I
Public bug reported:
Binary package hint: xapian-omega
For example:
http://launchpadlibrarian.net/16745494/buildlog_ubuntu-intrepid-lpia
.xapian-omega_1.0.7-3_FAILEDTOBUILD.txt.gz
A quick glance suggests to me that the issue is that the libtool 2.2.x
package in intrepid doesn't have the "don't
Sorry - will include changelog entries in future.
--
Please sync libsearch-xapian-perl 1.0.7.0-1 (universe) from Debian unstable
(main)
https://bugs.launchpad.net/bugs/257173
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
It does appear to be a bug in the "link_all_deplibs=no" patch in the
2.2.x libtool package. I have a patch which corrects the behaviour for
this case, though I don't know if it's the right fix. Anyway, I'll open
a separate bug for that.
Meanwhile, the attached patch for xapian-omega's debian/rul
Public bug reported:
Binary package hint: libtool
It appears that the link_all_deplibs=no patch hasn't been correctly
updated for libtool 2.2.x.
The binaries in xapian-omega link against libxapian which has a
dependency on libz, but the binaries don't require libz themselves. So
to avoid explic
** Attachment added: "Patch to fix link_all_deplibs=no"
http://launchpadlibrarian.net/16866050/ltmain.sh.patch
--
link_all_deplibs=no patch no longer working well
https://bugs.launchpad.net/bugs/258491
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
The xapian-omega FTBFS bug is LP257755.
--
link_all_deplibs=no patch no longer working well
https://bugs.launchpad.net/bugs/258491
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hmm, that didn't create a link automatically. See:
https://bugs.launchpad.net/ubuntu/+source/xapian-omega/+bug/257755
--
link_all_deplibs=no patch no longer working well
https://bugs.launchpad.net/bugs/258491
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
OK, the libtool bug is:
https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/258491
--
xapian-omega 1.0.7-3 FTBFS in intrepid
https://bugs.launchpad.net/bugs/257755
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Looks likely to be a bug in xapian-core, but without knowing the
parameters being passed in it's hard to see what's going wrong.
Is this repeatable if you rerun by hand from the command line:
sudo /usr/sbin/update-apt-xapian-index
--
update-apt-xapian-index crashed with SIGSEGV in
Xapian::Stem
That really has no connection with this ticket. Please don't hijack a
bug report with unrelated issues - open a new ticket instead.
--
free disk space check could actually carry out suggested ways to clear space
https://bugs.launchpad.net/bugs/291342
You received this bug notification because yo
Marking as "Fix Released" which doesn't quite fit, but I don't see a
better option.
** Changed in: foobillard (Ubuntu)
Status: New => Fix Released
--
Table cloth and cushions are black except for "fB" logo
https://bugs.launchpad.net/bugs/257479
You received this bug notification because y
Just tried to reproduce this on the same machine, now upgraded to
jaunty, and I no longer see it.
--
Table cloth and cushions are black except for "fB" logo
https://bugs.launchpad.net/bugs/257479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
xapian-core was recently sync-ed from debian:
https://launchpad.net/distros/ubuntu/+bug/52885
Could you also sync xapian-omega (a web search frontend build on Xapian)
and xapian-bindings (which allows use of Xapian from Python, PHP, Ruby,
and Tcl)? Neither is currently in U
Public bug reported:
Binary package hint: libc6
I'm running Ubuntu edgy on x86_64, upgraded from dapper (and before that
from breezy).
I've noticed that /etc/ld.so.conf contains:
/lib32
/usr/lib32
/usr/X11R6/lib32
include /etc/ld.so.conf.d/*.conf
But the only file in /etc/ld.so.conf.d
Looking at your log, some of the RPM URLs are no longer valid. I
suspect if you look at the downloaded RPM files, some probably actually
contain HTML 404 pages, or perhaps are just zero size. I'll try one of
the newer supported distros (suse10.0) and see if that works, but it
looks like the scrip
I've just successfully created a chroot for i686 suse10.0.
Looking at /usr/share/doc/rpmstrap/TODO, I think the problem you are
seeing is just this:
* The x86_64 (and other archs) are buggy or not yet supported.
Right now, only i[3456]86 is. These archs should be added.
--
rpmstrap using /bin/s
I think "dead" is overstating the case. The original author is no
longer interested in maintaining rpmstrap, and it would certainly
benefit from updating to support newer RPM-based distros, but that
doesn't mean that someone else can't take on the role of maintainer.
The page Cesare linked to indi
It occurred to me to check if there are any similar tools to rpmstrap,
but which are still actively supported upstream, and I quickly found
"mach":
http://thomas.apestaart.org/projects/mach/
This covers most of the distributions which rpmstrap does, and a few
others. The main comparative omissio
I've just run into this on gutsy.
I'm really just commenting to note that until the proposed fix gets to
the repository you can workaround the problem quite easily by running
explicitly using bash, like so:
sudo bash opcontrol --start --no-vmlinux
--
[SRU] for oprofile, edgy-updates: bashism in
It's not fixed in the gutsy RC. I imagine it should qualify for an
incremental update - rpmstrap currently just doesn't work if your
/bin/sh is dash, which is the Ubuntu default since edgy. Changing the
#! line to #!/bin/bash is pretty safe as the package would have been
running with /bin/bash on
I've just resubscribed ubuntu-universe-sponsors. There's a debdiff in
comment#6 which fixes this bug. If there's more you need, please say!
--
rpmstrap using /bin/sh when it should use /bin/bash
https://bugs.launchpad.net/bugs/64032
You received this bug notification because you are a member of
I've just tried bootstrapping chroots for gutsy i386 and amd64 (using
debootstrap --variant=buildd). In both cases, this mismatch still
occurs.
--
/etc/ld.so.conf and /etc/ld.so.conf.d/* mismatch
https://bugs.launchpad.net/bugs/70315
You received this bug notification because you are a member of
I added the line to sources.list and upgraded rpmstrap (but not the
other unrelated update from there).
This fixes this problem for me.
--
rpmstrap using /bin/sh when it should use /bin/bash
https://bugs.launchpad.net/bugs/64032
You received this bug notification because you are a member of Ubun
** Tags added: ftbfs
--
build dependencies not satisfied in hardy
https://bugs.launchpad.net/bugs/211621
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/m
Public bug reported:
In drivers/scsi/Kconfig:
config SCSI_ADVANSYS
is marked as:
depends on BROKEN || X86_32
I have a card which uses this driver - lspci reports it as:
01:07.0 SCSI storage controller: Advanced System Products, Inc ABP940-U
/ ABP960-U (rev 03)
My machine is x86_64 (a
I've tested with linux-image-2.6.24-1-generic and I can successfully use
my scanner with the advansys module. Excellent - thank you for sorting
this out.
--
advansys SCSI driver works on x86_64 but is disabled
https://bugs.launchpad.net/bugs/140993
You received this bug notification because you
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
advansys SCSI driver works on x86_64 but is disabled
https://bugs.launchpad.net/bugs/140993
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Reenabling and rebuilding the advansys module also works for me with
gutsy (kernel 2.6.22-14-generic).
--
advansys SCSI driver works on x86_64 but is disabled
https://bugs.launchpad.net/bugs/140993
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
Thanks for looking at this. I'm happy to test a fix.
Should it work OK to just install the hardy kernel package on gutsy and
reboot to use that kernel for testing? If not, any suggestions for how
best to go about this?
--
advansys SCSI driver works on x86_64 but is disabled
https://bugs.launch
Thanks for letting me know - I hope I'll be able to test it this coming
weekend.
--
advansys SCSI driver works on x86_64 but is disabled
https://bugs.launchpad.net/bugs/140993
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
I don't see where this is hardcoded in xapian-bindings - the only match
for a grep for pycentral is where we call "dh_pycentral". If there is
an error, please point out where it is and I will fix it in the debian
packages I'll be preparing shortly.
The buildd failure is due to you trying to build
Is it possible to unsubscribe xapian-developers from this bug, now that
it's acknowledged as not being a xapian bug? I can't see how to do it
for myself.
I'm getting rather a lot of irrelevant email from this bug right now
(and apologies to everyone else subscribed for this irrelevant email!)
--
> ScottK2: there are two rdepends... did the API change?
> (in an incompatible way)
Just to clarify (as debian packager and an upstream Xapian developer),
xapian-core 1.0.4 and 1.0.5 are both API and ABI compatible (in general,
Xapian 1.X.Y and 1.X.Z should be both ABI and API compatible, althou
d be avoided.
* debian/xapian-omega.prerm,debian/xapian-omega.postrm: prerm doesn't get
the "purge" action, so replace the prerm with a postrm so templates get
removed on purge. Closes: #455103
* debian/control.in: The "Homepage:" header is now official, so con
Just to add a confirmation, I just noticed this on a gutsy -> hardy beta
upgrade.
--
distribution upgrade tool reports "kb/s" but is measuring "kB/s"
https://bugs.launchpad.net/bugs/189454
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just noticed this upgrading from gutsy to hardy beta.
--
Error on startup: “Element not allowed”
https://bugs.launchpad.net/bugs/174148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Public bug reported:
xapian-core and xapian-omega have been automatically synced from Debian,
but xapian-bindings wasn't (perhaps because it's patched to drop php4
support).
So xapian-bindings is still 0.9.9-1, which will FTBFS against xapian-
core 1.0.1-1 (some deprecated features have been remo
Dan: I don't think Steve saw your last comment - he said: "please
resubscribe us where there is" and looking at the subscribers, I don't
see him or Ubuntu-universe-sponsors there currently...
I'm tempted to readd them myself, but I'm not sure what the etiquette is
here.
--
rpmstrap using /bin/sh
Indeed - it's just fallout from Ubuntu edgy making /bin/sh invoke dash
rather than bash. Linux distros have traditionally always used bash,
and coders have either just assumed that would always be true, or
accidentally used bash extensions without realising they weren't
portable (because they work
I wasn't really worrying about the lib32 directories (though now I think
about it, that's rather odd too), but rather suggesting that either the
include line in /etc/ld.so.conf should read:
include /etc/ld.so.conf.d/*
Or probably better, that /etc/ld.so.conf.d/x86_64-linux-gnu should
instead be n
I've just run into this too, and can also confirm that using bash
instead seems to allow rpmstrap to work correctly (I made a copy earlier
on my path than /usr/bin and changed the #! line to "#!/bin/bash").
--
rpmstrap using /bin/sh when it should use /bin/bash
https://launchpad.net/bugs/64032
-
Yes, this isn't a bug in xapian-core - you need to catch
QueryParserError, and you can call get_msg() on it to get an error
message to report to the user. You'll want to run the message through
i18n as it's always in English currently. The possible errors are:
Unknown range operation
parse error
Xapian ticket #22 is not related to this bug. This is not a bug in
Xapian, but in how it is being used.
** Changed in: xapian
Importance: Unknown => Undecided
** Changed in: xapian
Status: Confirmed => New
** Changed in: xapian
Remote watch: trac.xapian.org/ #22 => None
** Changed i
Sorry, your bug link is wrong, so I've removed it as it just confuses
the real issue. It's great to see people actively triaging tickets in
Launchpad, but please resist the temptation to latch onto likely
sounding upstream tickets without reading them carefully to see if they
are actually related.
Public bug reported:
Builds failed on ia64, armel, and sparc due to the same issue - the
testsuite fails due to running out of fds.
The testsuite harness deliberately limits the number of fds available to
catch leaks, but such leaks shouldn't be platform dependent, so this
seems almost certain to
** Attachment added: "replacement patch"
http://launchpadlibrarian.net/31116997/kill-ulimit-for-testsuite.patch
--
Fix xapian-core 1.0.15-2 FTBFS
https://bugs.launchpad.net/bugs/422493
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Please consider syncing xapian-core 1.0.18-1 from Debian unstable to
Ubuntu lucid.
I'm recommending this as an upstream Xapian developer and the Debian
maintainer of this package.
The main benefit of doing this is that 1.0.18 includes a fix which dramatically
speeds up addi
Public bug reported:
Ubuntu karmic has 1.0.14-1ubuntu1, Debian unstable has xapian-core
1.0.15-2.
The upstream microrelease incorporates the Ubuntu-specific changes, fixes a bug
(http://trac.xapian.org/ticket/392), allows the testsuite to work with the
latest valgrind release, and improves docu
** Attachment added: "Prined diff from current version to proposed version"
http://launchpadlibrarian.net/30995419/xapian-core-ubuntu-to-debian-pruned.diff
--
xapian-core: request for FF exception for karmic
https://bugs.launchpad.net/bugs/421306
You received this bug notification because yo
Oh, I failed to mention that 1.0.15-2 changes the build to use -g, which
means the -dbg package is a lot more useful...
--
xapian-core: request for FF exception for karmic
https://bugs.launchpad.net/bugs/421306
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Thanks.
I was indeed trying to suggest a sync from Debian - sorry for not saying
so more explicitly.
--
sync xapian-core from Debian
https://bugs.launchpad.net/bugs/421306
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
On Dapper, set to UK English:
System -> Preferences -> Menus & Toolbars
brings up a dialog which has a picker labelled "Toolbar button labels".
If I set this to "Text beside icons", the Preview shows:
[Document icon] New [Folder icon] [Floppy icon]
I would expect it to
Indeed.
And the wx-config man page is shipped in wx-common because wx-config is
managed by the alternatives system, and can be provided by
libwxbase3.0-dev or libwxgtk3.0-gtk3-dev (or by other versions of those
at times when we have more than one wxwidgets release series packaged).
So closing as
** Changed in: libpst (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1130751
Title:
readpst reports success on crash
To manage notifications abo
This was fixed upstream in 5.4.1, which is in artful.
** Changed in: therion (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667550
Title:
Edit line
This was fixed years ago in Xapian, but launchpad's bug watch on the
upstream ticket fails to pick up the status. I tried deleting the link,
but I still can't change the status of the ticket...
** Changed in: xapian
Importance: Unknown => Undecided
** Changed in: xapian
Status: Confirm
Fixed long ago.
** Changed in: wxwidgets2.8 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/361122
Title:
wammu crashed with SIGSEGV in PyErr_SetStri
Package was removed after xenial, so closing ("Fix released" seems the
least inappropriate resolution of the options available).
** Changed in: apache-mod-auth-ntlm-winbind (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Changed in: xapian
Importance: Undecided => Unknown
** Changed in: xapian
Status: New => Unknown
** Changed in: xapian
Remote watch: None => trac.xapian.org #180
** No longer affects: xapian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Trusty reach EOL several months ago, so closing this as it is no longer
actionable. There doesn't seem to be an entirely suitable status for
such a case though.
** Changed in: trusty-backports
Status: New => Fix Released
** Changed in: wxpython3.0 (Ubuntu)
Status: Confirmed => Fix
Not sure when this was fixed, but 3.14-2 says " Quick quit to
system"
** Changed in: freedink-dfarc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/486724
T
** Changed in: wxwidgets3.0 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573764
Title:
Cannot install both 32 and 64 bit versions of libwxGTK3
To manage
On Tue, Oct 03, 2017 at 07:56:42AM -, slodki wrote:
> > libwxgtk-webview3.0-dev : Depends: wx3.0-headers (= 3.0.3.1+dfsg-1) but
> 3.0.3.1+dfsg2-1 is to be installed
> > Depends: libwxgtk3.0-dev (= 3.0.3.1+dfsg-1) but
> 3.0.3.1+dfsg2-1 is to be installed
> +
> +
. (Closes: #719250)
[...]
-- Olly Betts Wed, 28 Aug 2013 10:25:35 +1200
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249161
Title:
package libwxgtk-media2.8-0 (not installed) failed to install
Public bug reported:
This package is obsolete now that xapian-bindings 1.4 has been synced from
Debian, and should be
removed. It's a development snapshot of upstream code so won't get any sort of
upstream support.
** Affects: xapian1.3-bindings (Ubuntu)
Importance: Undecided
Sta
Public bug reported:
This package is obsolete now that xapian-core 1.4 has been synced from Debian,
and should be
removed. It's a development snapshot of upstream code so won't get any sort of
upstream support.
** Affects: xapian1.3-core (Ubuntu)
Importance: Undecided
Status: New
I've not looked at how it was packaged, but the upstream code looks to
be compatible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660216
Title:
Package is obsolete and should be removed
To manag
Incidentally, please note that although launchpad lists me as
"maintainer" of this package, I had nothing to do with creating it - I
guess I'm listed there as it was forked from a package I maintain in
Debian, and someone was too slack to update the metadata properly.
--
You received this bug not
Hmm, there's no "outdated" or similar status available - the closest
seems to be "won't fix", but I can't select that (I guess it requires an
"Ubuntu Developer" bit) - can someone else please do the honours?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
The Ubuntu releases with vulnerable versions are all EOL, so making this
bug public and closing.
I find the lack of actual security support for the majority of packages
in Ubuntu rather disturbing - I don't run Ubuntu myself currently so
providing a tested debdiff isn't easy, but I did provide lin
** Changed in: xapian
Importance: Unknown => Undecided
** Changed in: xapian
Status: Confirmed => New
** Changed in: xapian
Remote watch: trac.xapian.org #346 => None
** No longer affects: xapian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It's a bug in that example script, but that script is shipped in the
documentation in the python-xapian package, so it is still a bug in the
package.
I've applied a fix upstream - here it is if you want to backport it:
http://trac.xapian.org/changeset/16480/branches/1.2/xapian-
bindings/python/do
** Bug watch added: Debian Bug tracker #603871
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603871
** Also affects: wv2 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603871
Importance: Unknown
Status: Unknown
--
libwv2 release package compiled with DEBUG flag
This patch (which I've just submitted to Debian too) fixes the issue.
--
libwv2 release package compiled with DEBUG flag
https://bugs.launchpad.net/bugs/645023
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Gah - the first attempt to attach the patch timed out, and when I hit
back and resubmitted, the patch was no longer attached.
So let's try that again...
** Patch added: "Patch to build with -DNDEBUG"
https://bugs.launchpad.net/ubuntu/+source/wv2/+bug/645023/+attachment/1736744/+files/wv2-buil
In 3.0.2.0+dfsg-1 in Debian I switched the package to use the .desktop
files upstream provides (presumably added more recently), which don't
have this issue, so syncing that version should fix this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
wily has 3.0.2.0+dfsg-1build1
** Changed in: wxpython3.0 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1419584
Title:
no icon for PyCrust .desktop file i
wxPython 3.0 is in source package wxpython3.0 - wxwidgets3.0 is just the
C++ library (for wx 2.8, both were in wxwidgets2.8).
** Package changed: wxwidgets3.0 (Ubuntu) => wxpython3.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
This is fixed in Debian by wxwidgets3.0 3.0.2-2 which I uploaded
yesterday, though it's currently in NEW (due to the new wx3.0-doc binary
package) and there's quite a backlog there so it may take a while to be
approved.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Changing the BD might be trivial, but isn't enough as it fails to
compile due to API changes between gstreamer 0.10 and 1.0.
There's a patch from mandriva on trac.wxwidgets.org, but I've not yet
tried it.
** Bug watch added: Debian Bug tracker #785924
http://bugs.debian.org/cgi-bin/bugreport.c
1 - 100 of 156 matches
Mail list logo
