On Sun, Apr 07, 2024 at 08:22:37PM +0100, Peter Michael Green wrote:
> The following lines in the build log look like a likely culprit.
>
> > # The module(s) are linked against libruby2.x but use none of its
> > # symbols, so there's no dependency generated. That's unhelpful for
> > # users and
Thanks for reporting this.
On Sat, Mar 09, 2024 at 06:29:22PM +, James Addison wrote:
> Running a search for 'python removal' on the 'testing-changes' mailing list,
> ordered by most-recent-first, currently lacks any results from this year.
>
>
>
On Wed, Nov 08, 2023 at 08:10:26PM +0100, Martin Budaj wrote:
> On Tue, Nov 7, 2023 at 4:25 PM Wookey wrote:
>
> > It looks like moving to catch3 and adding:
> > target_link_libraries(test PRIVATE Catch2::Catch2WithMain)
> > in the test targets should do the trick.
> as we still need to
On Tue, Oct 10, 2023 at 12:12:49AM +0100, Tj wrote:
> A package search on the RedHat bugzilla shows other reports including
> tracking bugs for the referenced (security) bug #2064638.
>
> https://bugzilla.redhat.com/buglist.cgi?component=antiword=Fedora
Doesn't seem promising - there's no useful
On Mon, Oct 09, 2023 at 10:57:46PM +0100, Tj wrote:
> As requested here's a summary of one potential unsanitised input data
> issue that may be leading to this (or other) error(s).
>
> `vSetSummaryInfoOLE()` calls `pucAnalyseSummaryInfoHeader()` that does:
>
> `if (!bReadBuffer(pFile, ...
Package: mate-panel
Version: 1.27.1-2
Severity: normal
Frequently (but not every time) I unhibernate I get a pop up telling me
that mate-clock has crashed. I do at least get the option to restart
it, and doing so has always worked so far.
I'm seeing this on two different machines now, and both
Control: forwarded -1 https://github.com/cmauri/eviacam/issues/22
Control: severity -1 serious
I'm raising the severity since important is defined as "a bug which has
a major effect on the usability of a package, without rendering it
completely unusable to everyone", but this bug means the
Control: forwarded -1 https://github.com/wxWidgets/wxWidgets/pull/23764
On Mon, Jul 17, 2023 at 11:19:15AM -0400, Scott Talbert wrote:
> While evaluating this issue,
> it seems even a lot of native Gnome/GTK apps do not even provide a dark mode
> (e.g., even the gtk-demo application doesn't). So
On Tue, Aug 22, 2023 at 03:40:57PM +0200, Aurelien Jarno wrote:
> It appears that the failing tests are already filtered on some
> architectures, would it be possible to do the same on riscv64 until we
> have time to investigate the issue? The following patches enables the
> package to build
On Wed, Jun 07, 2023 at 09:27:13PM +0100, Olly Betts wrote:
> I think it'd be good to check with upstream if the "experimental" marker
> is out-dated, or still accurate, and if it's still accurate what the
> downsides of this are. I've opened a ticket:
>
> https://githu
Control: reassign -1 source:wxwidgets3.2
On Wed, Jun 07, 2023 at 09:49:19AM -0400, Scott Talbert wrote:
> I think it would be okay to enable xtest support even though it doesn't work
> under Wayland.
I think it'd be good to check with upstream if the "experimental" marker
is out-dated, or still
On Tue, Jun 06, 2023 at 02:12:50PM -0400, Maxim Cournoyer wrote:
> I researched the problem and found that the feature I wanted was implemented
> using XTest, which is detected at wxWidgets' build time [1]. Looking at the
> Debian
> package dependencies, I found it did *not* depend on the
: #1032398
+
+ -- Olly Betts Fri, 17 Mar 2023 11:20:07 +1300
+
xapian-core (1.4.18-3) unstable; urgency=medium
* debian/rules: Workaround testcase sensitivity to excess precision by
diff -Nru xapian-core-1.4.18/debian/patches/fix-db-corruption-on-ENOSPC.patch
xapian-core-1.4.18/debian/patches/fix-db
Source: xapian-core
Version: 1.4.18-3
Severity: critical
Tags: patch upstream
Justification: causes serious data loss
Control: fixed -1 1.4.22-1
Xapian database corruption on disk full is possible. It doesn't happen
in every case as ENOSPC needs to happen on a particular operation during
the
On Sat, Jan 14, 2023 at 12:07:21AM +0100, Bastian Germann wrote:
> I have just tested the patch and uploaded it as-is as NMU to DELAYED/10.
Thanks for the testing.
I'm not super happy that you've uploaded an NMU that appears to have
been done by me though:
Hi Jérémy,
On Mon, Dec 05, 2022 at 09:31:45AM +0100, Jérémy Lal wrote:
> as a Debian Games Team maintained package, I could do a team upload
> very soon.
Are you still intending to upload dolphin-emu? In order to be in
the bookworm release it would need to reenter testing by 2023-02-12:
On Wed, Sep 14, 2022 at 03:42:14PM -0400, s...@techie.net wrote:
> Please transition dolphin-emu from wxwidgets3.0 to wxwidgets3.2.
I've been looking through the handful of packages which are still
using wxwidgets3.0 with an eye to seeing if any can usefully be
NMUed to help them reenter testing
g 2021-10-01 16:26:49.0 +1300
+++ amule-2.3.3/debian/changelog 2023-01-09 13:00:46.0 +1300
@@ -1,3 +1,10 @@
+amule (1:2.3.3-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Update to use wxwidgets3.2 - new patch wx3.2.patch; Closes: #1019841
+
+ -- Olly Betts Mon,
; urgency=medium
+
+ * Non-maintainer upload.
+ * Update to wxwidgets3.2. (Closes: #1019791)
+
+ -- Olly Betts Thu, 05 Jan 2023 10:56:35 +1300
+
stimfit (0.16.0-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru stimfit-0.16.0/debian/control stimfit-0.16.0/debian/control
Control: tags -1 + patch
On Wed, Sep 14, 2022 at 03:42:14PM -0400, s...@techie.net wrote:
> Please transition freespace2-launcher-wxlauncher from wxwidgets3.0 to
> wxwidgets3.2.
Just a friendly note to highlight that this package needs to re-enter
testing to make it into bookworm, and that the
Just a friendly note to highlight that opencpn needs to re-enter testing
to make it into bookworm, and that the release freeze cut-off for
re-entering testing is 2023-02-12:
https://release.debian.org/testing/freeze_policy.html#summary
I think a package needs to actually *migrate* by that
On Wed, Dec 28, 2022 at 12:55:20PM -0500, Scott Talbert wrote:
> On Tue, 27 Dec 2022, Chow Loong Jin wrote:
> > Alright, I'll leave the slic3r-prusa as-is then. I'm guessing that a
> > binNMU will take care of things when we get there.
>
> wxwidgets3.2 has been rebuilt in unstable with EGL
On Wed, Nov 09, 2022 at 11:44:29PM +, Olly Betts wrote:
> On Wed, Nov 09, 2022 at 04:49:33PM +0100, Cesar Mauri wrote:
> > I've just merged a PR that add support for OpenCV 4.6.0 and (hopefully)
> > fixes the camera error
> >
> > https://github.com/cmauri/evi
: #1019837)
+
+ -- Olly Betts Thu, 05 Jan 2023 06:46:35 +1300
+
treesheets (1:1.0.2-1) unstable; urgency=medium
* New upstream release.
diff -Nru treesheets-1.0.2/debian/control treesheets-1.0.2/debian/control
--- treesheets-1.0.2/debian/control 2019-12-01 05:24:15.0 +1300
+++ treesheets
On Wed, Dec 21, 2022 at 11:21:03AM +0800, Chow Loong Jin wrote:
> I've fixed the segfault by applying the patch from [1], but there's one
> issue remaining -- PrusaSlicer fails to initialize GLEW due to [2],
> resulting in the plater screen not showing up, same as this SuperSlicer
> issue[3].
>
>
On Thu, Oct 27, 2022 at 09:07:42AM +, Andrius Merkys wrote:
> Control: tag -1 pending
>
> Hello,
>
> Bug #1019808 in openbabel reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
>
08:12:59.0 +1300
@@ -1,3 +1,11 @@
+golly (3.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/control: Switch to use wxwidgets3.2 (Closes: #1019810)
+ * Drop patch 0005-wxwidgets-inmature-yet.patch which is no longer required.
+
+ -- Olly Betts Sat, 26 Nov 2022 08
On Fri, Nov 18, 2022 at 11:06:07AM +0800, Bo YU wrote:
> On Fri, Nov 18, 2022 at 3:34 AM Olly Betts wrote:
> > Looking at upstream's SVN history I can see changes for wx3.2
> > compatibility so it looks like they're on top of this.
> >
> > Therefore I'd suggest tryi
On Sun, Oct 30, 2022 at 03:52:13PM +0800, Bo YU wrote:
> I have tried to build the package with libwxgtk3.2-dev, but
> unfortunately, it fails:
[snip]
> Could you help to have a look?
Looking at upstream's SVN history I can see changes for wx3.2
compatibility so it looks like they're on top of
:43.0 +1300
@@ -1,3 +1,11 @@
+openmsx-catapult (18.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/control: Update to build with wxwidgets-3.2 (new patch
+wx3.2-compat.patch) (Closes: #1019776)
+
+ -- Olly Betts Thu, 10 Nov 2022 15:40:43 +1300
+
openmsx-catapult (18.0-2
On Wed, Nov 09, 2022 at 04:49:33PM +0100, Cesar Mauri wrote:
> I've just merged a PR that add support for OpenCV 4.6.0 and (hopefully)
> fixes the camera error
>
> https://github.com/cmauri/eviacam/tree/master
Great. Will there be a new upstream release soon?
Cheers,
Olly
On Tue, Sep 20, 2022 at 09:18:52PM +, Dennis Braun wrote:
> Control: tag -1 pending
>
> Hello,
>
> Bug #1019806 in sooperlooper reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
>
300
+++ eviacam-2.1.4/debian/changelog 2022-11-09 10:14:08.0 +1300
@@ -1,3 +1,11 @@
+eviacam (2.1.4-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/control: Update to build with wxwidgets-3.2 (new patch
+wx3.2-compat.patch) (Closes: #1019790)
+
+ -- Olly Betts Wed, 09
to build with wxwidgets-3.2 (new patch
+wx3.2-compat.patch) (Closes: #1019829)
+
+ -- Olly Betts Mon, 07 Nov 2022 12:06:09 +1300
+
pgn2web (0.4-3) unstable; urgency=medium
* debian/control:
diff -Nru pgn2web-0.4/debian/control pgn2web-0.4/debian/control
--- pgn2web-0.4/debian/control
severity 1019833 serious
thanks
(I raised the severity of most of these yesterday, but missed packages
where an upload to experimental has closed the bug while it's not yet
fixed in unstable.)
Accounting for packages which are fixed in experimental or in git we're
now under 30 packages left to
Source: wxwidgets3.0
Version: 3.0.5.1+dfsg-5
Severity: serious
Justification: Opinion of package maintainer
We have packages of wxwidgets3.2 in unstable and testing, and a
transition is well under way:
https://release.debian.org/transitions/html/wxwidgets-3.2.html
The last upstream release of
severity 1019823 serious
severity 1019775 serious
severity 1019768 serious
severity 1019812 serious
severity 1019835 serious
severity 1019769 serious
severity 1019799 serious
severity 1019827 serious
severity 1019808 serious
severity 1019830 serious
severity 1019762 serious
severity 1019829
On Wed, Oct 12, 2022 at 10:40:29PM +0200, László Böszörményi (GCS) wrote:
> On Wed, Oct 12, 2022 at 10:36 PM Olly Betts wrote:
> > On Tue, Oct 11, 2022 at 11:28:53PM +0200, Sebastian Ramacher wrote:
> > > The following packages have unmet dependencies:
> > > li
title -1 libwxsqlite3-3.0-dev: not coinstallable
On Tue, Oct 11, 2022 at 11:28:53PM +0200, Sebastian Ramacher wrote:
> The following packages have unmet dependencies:
> libwxsqlite3-3.2-dev : Breaks: libwxsqlite3-3.0-dev but 3.4.1~dfsg-8 is to
> be installed
> E: Unable to correct problems, you
Control: reopen -1
Control: found -1 1.3.0.0-1
Control: severity -1 important
Resent to not -maintonly.
Thanks, but I don't think that was the problem - rather I'd used the
control@bugs.d.o syntax but hadn't Cc-ed control@. I'm not sure
control@ actually supports -1 for the bug number in
On Sat, Sep 24, 2022 at 09:50:10PM +0100, Olly Betts wrote:
> On Sat, Sep 24, 2022 at 06:09:31PM +0200, Andreas Metzler wrote:
> > wxwidgets and glew disagree over EGL support, glew is built without,
> > wxwidgets (since 3.2) with.
> >
> > That causes problems (cr
Control: reopen -1
Control: notfixed -1 3.4.1~dfsg-6
Control: found -1 3.4.1~dfsg-6
On Sat, Sep 24, 2022 at 10:53:31PM +0200, László Böszörményi (GCS) wrote:
> On Mon, Sep 19, 2022 at 7:48 AM Olly Betts wrote:
> > It appears that there's now only a single reverse dependency, codelite,
On Sat, Sep 24, 2022 at 10:53:31PM +0200, László Böszörményi (GCS) wrote:
> On Mon, Sep 19, 2022 at 7:48 AM Olly Betts wrote:
> > > wxsqlite3 (3.4.1~dfsg-6) experimental; urgency=medium
> [...]
> > Thanks for the upload to experimental.
> Recently I uploaded it to Sid.
On Sat, Sep 24, 2022 at 06:09:31PM +0200, Andreas Metzler wrote:
> wxwidgets and glew disagree over EGL support, glew is built without,
> wxwidgets (since 3.2) with.
>
> That causes problems (crashes, "Unable to init glew library") in
> software using glew and wxwidgets. Google finds multiple
Package: lintian
Version: 2.115.3
Severity: normal
I get:
I: xapian-omega: spelling-error-in-binary curren current [usr/bin/omindex]
That's not a spelling error though, it's from a list of HTML entity
names ( is "¤"):
Package: xmlcopyeditor
Version: 1.2.1.3-4.3
Severity: serious
Justification: makes the package in question unusable or mostly so
X-Debbugs-Cc: s...@techie.net
Since the update to use wxwidgets3.2, xmlcopyeditor pops up "An
assertion failed!" dialogs on startup, with similar messages on
stderr:
On Sun, Sep 18, 2022 at 06:03:32PM +, Debian Bug Tracking System wrote:
> Closes: 1019786
> Changes:
> wxsqlite3 (3.4.1~dfsg-6) experimental; urgency=medium
> .
>* Transition to wxwidgets3.2 (closes: #1019786).
>* Mark wxsqlite3-doc Multi-Arch foreign.
Thanks for the upload to
On Wed, Aug 10, 2022 at 09:17:02AM +0200, Thomas Lange wrote:
> in #1015198 I also reported useless search results
> similar to #658227 (still open since 2012).
Sorting by date is unlikely to help #658227 - it would prefer the newest
documents which mention the DFSG, and the social contract page
On Tue, Jul 19, 2022 at 04:32:41PM +0200, Antonio Terceiro wrote:
> > dh_install: warning: Cannot find (any matches for)
> > "usr/lib/python3*/*-packages/xapian/*.so" (tried in debian/tmp, debian/tmp)
> >
> > dh_install: warning: python3-xapian missing files:
> >
Control: severity -1 wishlist
Control: tags -1 +help
On Fri, Sep 20, 2013 at 04:15:29PM +0200, Sébastien Hinderer wrote:
> Hello Olly, thanks for your e-mail.
>
> > I'm not expecting absolute proof, but it'd be good to test it on a
> > selection of word documents, and compare output with and
Control: tag -1 +moreinfo
Control: severity -1 normal
On Thu, Mar 24, 2022 at 04:00:23AM +, Olly Betts wrote:
> On Tue, Mar 22, 2022 at 06:56:23PM +0800, Jieyong Ma @ tdhxkj.com wrote:
> > Backtraces:
> > Program received signal SIGSEGV, Segmentation fault.
> &g
Control: tags +help
On Tue, Dec 11, 2018 at 04:03:41AM +, Eric Wong wrote:
> I noticed Lua bindings are provided with Xapian upstream;
> but there's no Debian package for it.
>
> I'm not a Lua programmer, yet, but the availability of Xapian
> bindings would influence my choice to try it.
Control: reassign 919903 wnpp
Control: retitle 919903 ITP: wxwidgets3.2 -- wxWidgets Cross-platform C++ GUI
toolkit
Control: owner 919903 s...@techie.net
wxWidgets 3.1 has finally evolved into the stable wxWidgets 3.2.0
release.
Scott Talbert is already working on packaging it, so converting
On Tue, Mar 22, 2022 at 06:56:23PM +0800, Jieyong Ma @ tdhxkj.com wrote:
> Backtraces:
> Program received signal SIGSEGV, Segmentation fault.
> 0x00449515 in vAnalyseSummaryInfo (aucBuffer=0x6928f0 "t\001") at
> summary.c:225
> 225 switch (tPropID) {
That seems a
Control: tags -1 + fixed-upstream
On Tue, Feb 01, 2022 at 11:19:04PM +0100, Sebastian Ramacher wrote:
> survex FTBFS with ffmpeg 5.0 in experimental:
I've pushed a fix for this upstream (commit
44c4b7054885c2a5f25692547bf45fa33bcba1e8).
It looks like there are a huge number of packages still
On Tue, Nov 30, 2021 at 11:53:23AM -0800, Norman Rasmussen wrote:
> --- a/src/unix/stdpaths.cpp
> +++ b/src/unix/stdpaths.cpp
> @@ -260,6 +260,8 @@ wxString wxStandardPaths::GetDocumentsDir() const
> value.Replace(wxT("$HOME"), homeDir);
>
On Tue, Oct 26, 2021 at 05:35:48AM +0200, Sebastiaan Couwenberg wrote:
> PROJ 8.2.0 is scheduled for release next week, just wait for that.
Oh, I see this has been uploaded. I'll try to sort out updating the
survex package to use it.
Cheers,
Olly
On Tue, Oct 26, 2021 at 06:34:06PM -0300, Antonio Terceiro wrote:
> > rb=debian/tmp`/usr/bin/ruby3.0 -rrbconfig -e 'puts
> > RbConfig::CONFIG["vendorlibdir"]'`/xapian.rb; \
> > for v in 2.7; do \
> > if [ "$v" != "3.0" ] ; then \
> > set -e; \
> > rb_old=debian/tmp`/usr/bin/ruby$v
On Tue, Oct 26, 2021 at 05:35:48AM +0200, Sebastiaan Couwenberg wrote:
> PROJ 8.2.0 is scheduled for release next week, just wait for that.
OK.
> You also mentioned in the upstream issue that you need a solution for other
> users who cannot upgrade to PROJ 8.2.0, did you give up on that and made
On Fri, Oct 22, 2021 at 06:36:53AM +0200, Sebastiaan Couwenberg wrote:
> The proj transition has started, raising the severity accordingly.
As I noted in the upstream ticket (which I know you are subscribed to)
Survex requires a fix to make proj_factors() actually usable in the "new
PROJ" world.
Control: tags -1 + fixed-upstream
On Sat, Mar 14, 2020 at 07:13:21PM +0100, Guillem Jover wrote:
> It looks like this is the only header used by this package from libattr,
> so you should be able to drop the dependency on libattr entirely, as
> glibc should be providing all that is needed now.
I
Control: tags -1 + fixed-upstream
On Tue, Feb 18, 2020 at 06:10:38AM +0100, Helmut Grohne wrote:
> please consider applying the attached patch to fix the
> issue with calling pkg-config and close this bug when doing so.
I forwarded your report to the upstream author (via private email) and
Control: tags -1 + fixed-upstream
On Sun, Apr 05, 2020 at 03:19:35PM +0100, s...@debian.org wrote:
> For most purposes, the recommended replacement for dbus-glib is the
> GDBus family of APIs in GLib, found in .
I forwarded your report to the upstream author (via private email) and
it's been
On Fri, Jul 16, 2021 at 06:44:49PM +0200, Dennis Filder wrote:
> The attached patch seems to allow the "Converting images" step to
> succeed. I ran this only once though.
This looks reasonable to me (as an uploader of the package).
Wookey: Are you able to upload? I'm seriously lacking in spare
Hi Helmut,
On Sun, Mar 21, 2021 at 09:24:19AM +0100, Helmut Grohne wrote:
> xapian-core fails to cross build from source, because it fails running
> tests despite passing DEB_BUILD_OPTIONS=nocheck. Please consider
> applying the attached patch to fix that.
Sorry about this - I converted
On Tue, Feb 23, 2021 at 10:22:39PM +0200, Adrian Bunk wrote:
> On Tue, Feb 23, 2021 at 07:52:42PM +0000, Olly Betts wrote:
> >...
> > As you note, on i386 the test was only run with the SSE build before
> > the recent debian/rules modernisation, but that doesn't explain w
On Sat, Feb 20, 2021 at 07:24:52PM +, Olly Betts wrote:
> On Fri, Feb 19, 2021 at 11:36:46AM +0200, Adrian Bunk wrote:
> > With the old debian/rules the test was only run with
> > the SSE build.
> >
> > If exact results are required and the x87 excess prec
On Fri, Feb 19, 2021 at 11:36:46AM +0200, Adrian Bunk wrote:
> With the old debian/rules the test was only run with
> the SSE build.
>
> If exact results are required and the x87 excess precision is unwanted,
> test with the non-SSE build can be fixed with:
>
> --- debian/rules.old 2021-02-18
On Sun, Dec 01, 2019 at 10:08:49AM +0100, Gunter Königsmann wrote:
> After an
>
> export GTK_IM_MODULE=xim
>
> the combination GTK3.0, wxWidgets and any ribbon, nearly any list view
> and all scrolled windows flicker real bad. At least if the CPU power
> doesn't allow for a repaint before the
On Thu, Jul 26, 2018 at 01:30:56PM +0200, Matus UHLAR - fantomas wrote:
> 1. the "From " line contains full "From: " header, while it's supposed to
> contain only the address, without < and > brackets, with one space
> separating address and date (two spaces are used now).
I've fixed this in
Package: libemail-outlook-message-perl
Version: 0.919-1
Severity: normal
Tags: patch upstream
Forwarded: https://github.com/mvz/email-outlook-message-perl/pull/15
This module doesn't currently handle the "Internet Code Page" property,
nor use the appropriate default of "CP1252". Instead
On Fri, Aug 21, 2020 at 02:36:28PM +, Luca Borzacchiello wrote:
> running antiword with the attached file leads to an invalid read,
> causing a segfault.
There's no longer an active upstream for antiword. So while fuzzing it
is great and all, much more useful would be working on patches to
On Sat, Jul 11, 2020 at 11:31:51AM +0200, Michel Le Bihan wrote:
> I opened https://github.com/wxWidgets/wxWidgets/pull/1946. It is still
> very ugly, but at least the AUI caption text is readable.
This has now been applied upstream as:
On Fri, Jul 10, 2020 at 10:47:14PM +0200, Michel Le Bihan wrote:
> In dark GTK themes the caption background correctly changes to the dark color,
> but the text stays black resulting in it being unreadable. The text color
> should also change.
>
> I opened a PR upstream
On Sun, Mar 29, 2020 at 06:32:53PM -0700, Felix Lechner wrote:
> Not sure if Olly's problem with wxwidgets3.0 was related, but it ran
> fine. That log is attached as well.
I suspect it wasn't, but I think I didn't get a chance to investigate as
it didn't recur.
Cheers,
Olly
On Fri, Mar 27, 2020 at 10:33:33AM -0400, Sandro Tosi wrote:
> i think we're ready to drop python-xapian: the only 2 remaining rdeps
> are not in testing (because are RC anyway), so please do remove
> python-xapian at your earliest convenience (please note we're also
> going to proceed with the
On Sat, Mar 21, 2020 at 06:12:48PM -0400, Sandro Tosi wrote:
> > Having pondered, I'd suggest we just leave xapian-bindings as-is
> > until you're at the point of dropping python2 support from sphinx and
> > then I'll drop the sphinx-generated docs for the python2 bindings
> > from the Debian
On Sat, Mar 14, 2020 at 05:35:14PM -0400, Sandro Tosi wrote:
> This will help us in reducing the reverse dependencies of
> bin:python-sphinx, so that we can introduce a python3-only sphinx
> version in unstable.
Having pondered, I'd suggest we just leave xapian-bindings as-is
until you're at the
On Sat, Mar 14, 2020 at 05:59:42PM -0400, Sandro Tosi wrote:
> > The Python2 and Python3 bindings don't have exactly the same API (mostly
> > due to Unicode handling differences, but also the Python3 bindings don't
> > include various backward-compatibility features with older versions of
> > the
Control: tags -1 wontfix
On Sat, Mar 14, 2020 at 05:35:14PM -0400, Sandro Tosi wrote:
> from what i can see, xapian-bindings builds its documentation twice, one for
> the
> python2 bindings (and install that in bin:python-xapian) and one for the
> python3
> bindings (and install that in
On Tue, Feb 11, 2020 at 08:36:43AM +1300, Olly Betts wrote:
> I've noticed this message repeatedly appearing in the ci.debian.net logs:
>
> Can't "next" outside a loop block at /usr/bin/abi-compliance-checker line
> 10171.
>
> That's the "next"
Package: abi-compliance-checker
Version: 2.3-0.2
Severity: normal
I've noticed this message repeatedly appearing in the ci.debian.net logs:
Can't "next" outside a loop block at /usr/bin/abi-compliance-checker line 10171.
That's the "next" in this function:
sub exec_helper(@)
{
my ($reader,
Control: reassign -1 firefox
Control: found -1 72.0.1-1
On Tue, May 29, 2012 at 11:45:15PM +0100, Andrew Wigglesworth wrote:
>* What led up to the situation?
>
> I clicked on an "IRC link". ie. a irc:// style link.
>
>* What was the outcome of this action?
>
> I was offered use of a
Control: tags -1 +pending
On Wed, Feb 05, 2020 at 12:05:22PM -0300, Lucas Kanashiro wrote:
> We are planning to start the ruby2.7 transition and your package failed
> to build against ruby2.7. Check the full build log here:
>
>
Control: tags -1 +pending
On Thu, Feb 06, 2020 at 05:17:37AM +, peter green wrote:
> This build failure is fixed by upstream commit
> faaa552de9ec099184d131c08b76ae0b1ce4f5ec
Thanks for identifying this - will upload shortly.
I'll also suggest to upstream it's time they made a new release
On Sat, Jan 18, 2020 at 09:58:15PM -0500, Sandro Tosi wrote:
> This bug was closed, but the package has still some dependencies towards
> Python2 packages, in details:
>
> (binary:pinot)Recommends->python-docutils
>
> Re-opening, so that they can be taken care of.
The dependency is actually:
On Mon, Dec 23, 2019 at 06:21:53PM -0500, John Scott wrote:
> > It's not ABI stable, so it's just not suitable for packaging. Every new
> > 3.1.x release would mean a transition for everything built against it.
> > Even if we only uploaded to experimental with the aim to support local
> > builds,
user debian-pyt...@lists.debian.org
usertags 938834 + py2keep
thanks
On Fri, Aug 30, 2019 at 10:22:11PM +0100, Olly Betts wrote:
> user debian-pyt...@lists.debian.org
> usertags 938836 + py2keep
I just spotted that I typoed the bug number here (938836 is another
package I maintain whic
On Mon, Aug 19, 2019 at 11:08:55PM -0400, John Scott wrote:
> I'm having this issue both with 19.01.2-1 and 19.07.0-1. Backtraces and
> screenshots are from the latter.
Can you reproduce this with wxmaxima 19.07.0-1.1 (the version currently
in unstable and testing)? That's the version that
Shouldn't this discussion be in bug #922067 (and not Cc-ed to me -
I have no interest in winpdb beyond it having been a blocker for
a wxpython transition over 5 years ago)?
This bug was providing the debdiff for an NMU I did back then. There's
been a maintainer upload since (1.4.8-3) which
Control: tags -1 +pending
On Tue, Dec 17, 2019 at 01:55:54AM +, Olly Betts wrote:
> On Mon, Dec 16, 2019 at 04:33:58PM +0100, Benedikt Hallinger wrote:
> > It would be nice to recompile the package including the latest
> > upstream sources, thank you!
>
> We usually
On Mon, Dec 16, 2019 at 04:33:58PM +0100, Benedikt Hallinger wrote:
> Hello, i just wanted to inform you that therion still fails with the proj
> issue[1] on my system when installing from the new package 5.4.4ds1-4.
>
> Also the loch glx issue[2] was fixed recently in upstream (Olly did a patch
On Fri, Apr 12, 2019 at 11:13:51AM +0200, Bálint Réczey wrote:
> The 18.1 version is out and the package is in the works:
> https://salsa.debian.org/multimedia-team/kodi
>
> I can't upload it yet even to experimental because flatbuffers is not
> in the archive yet.
Just to note that's no longer
Source: opencpn
Version: 4.8.8+dfsg.2-1
Severity: grave
Justification: renders package unusable
opencpn build-depends on libwxgtk3.0-dev, but that's been dropped
(there are still some crufty remnants in unstable, but libwxgtk3.0-dev
is no longer built by the wxwidgets3.0 source package, and isn't
On Fri, Nov 22, 2019 at 11:30:00PM -0800, Steve Langasek wrote:
> Rather than adding a build-dependency on python, which is deprecated, I have
> attached a patch which moves the invocation to python3 instead and added a
> build-dependency on python3.
I do wish upstream would pick a scripting
Control: reassign -1 libwxgtk3.0-gtk3-dev/3.0.4+dfsg-1
Reassigning - the GTK2 flavour packages are gone from testing and only
present in unstable due to a handful of untransitioned rdeps.
On Thu, Sep 14, 2017 at 11:03:08PM +0200, Helmut Grohne wrote:
> Package: libwxgtk3.0-dev
> Version:
On Fri, Oct 25, 2019 at 09:27:48AM +1300, Olly Betts wrote:
> On Tue, Oct 22, 2019 at 08:58:42AM +1300, Olly Betts wrote:
> > * mrpt was updated but the build failed on mipsel due to running out of
> > memory and it's now entangled in auto-opencv. But it's due for AUTORM
> &g
On Tue, Oct 29, 2019 at 11:05:02PM -0400, Scott Talbert wrote:
> On Wed, 30 Oct 2019, Olly Betts wrote:
>
> > The same issue applies to memcpy() which is why it's deliberately from
> > lintian's list:
> >
> > https://sources.debian.org/src/lintian/2.31.0/data/binari
Control: tags -1 -moreinfo
On Sat, Feb 16, 2019 at 12:26:36AM +0100, Chris Lamb wrote:
> I will thus leave this bug as "moreinfo" awaiting input from others.
What's presumably happening here is that the size of the destination
buffer and size of the copy are known, so it's clear at compile time
On Tue, Oct 29, 2019 at 07:53:28AM -1000, David Prévot wrote:
> On Thu, Oct 24, 2019 at 02:45:22PM +1300, Olly Betts wrote:
> > This package seems to have an active upstream and a user base
> > in Debian so I'd much rather see it return to a usable state than remove
> > it.
&g
1 - 100 of 1359 matches
Mail list logo
