Eric,
Thank you for the bug report. Per your question: I do indeed test before
uploading -- I've been using Digikam 7 since I uploaded last week.
On Monday, February 24, 2020 4:38:40 A.M. CST Eric Valette wrote:
> valette@tri-yann4:~$ digikam --version
> digikam: error while loading shared
Hello,
On Fri, 10 Jan 2020 11:35:09 +0100 Helge Bahmann wrote:
> The pkgconfig files supplied by upstream are not included in the installation
--
> having them available improves usability of the gtest for dev purposes. I
verified
> that this is still the case for 1.9.0 presently in testing.
On Mon, 20 Jan 2020 23:44:33 +1100 Hugh McMaster
wrote:
> Please update to version 6.2.0.
I've just uploaded to experimental and pushed the source changes to salsa.
Early feedback would be extremely helpful!
Thanks,
-Steve
signature.asc
Description: This is a digitally signed message part.
On Tue, 4 Feb 2020 21:20:59 +0800 YunQiang Su wrote:
> Package: src:gmp
> Version: 6.2.0+dfsg-3
>
> Since binutils/gcc meet some problem due to 2GB/3GB memory limitation
> on 32bit system.
Since GMP has built on all architectures, so I don't understand what problem
you are trying to solve.
On Tue, 4 Feb 2020 09:23:34 +0100 Christoph Berg wrote:
> Hi,
>
> the new gmp version makes postgresql-pgmp crash on arm64:
>
> https://ci.debian.net/data/autopkgtest/testing/arm64/p/postgresql-pgmp/
4173638/log.gz
> (linked from https://packages.qa.debian.org/g/gmp.html)
...etc. Thanks,
On Thursday, February 6, 2020 12:51:23 A.M. CST YunQiang Su wrote:
> Steven Robbins 于2020年2月6日周四 下午1:23写道：
>
> > On Tue, 4 Feb 2020 21:20:59 +0800 YunQiang Su wrote:
> > > Package: src:gmp
> > > Version: 6.2.0+dfsg-3
> > >
> > > Since binu
Hello Christoph,
On Thursday, February 6, 2020 3:43:41 A.M. CST Christoph Berg wrote:
> Re: Steven Robbins 2020-02-06 <4839510.uz11uGdL23@riemann>
>
> > > the new gmp version makes postgresql-pgmp crash on arm64:
> > >
> > > https://ci.debian.net/data/auto
On Tuesday, January 28, 2020 4:13:17 P.M. CST Hugh McMaster wrote:
> Hi Steve,
>
> On Sun, 26 Jan 2020 at 14:33, Steven Robbins wrote:
> > I've just uploaded to experimental and pushed the source changes to salsa.
> > Early feedback would be extremely helpful!
>
> Tha
On Fri, 13 Jan 2017 18:54:52 +0100 Guido =?iso-8859-1?Q?G=FCnther?=
wrote:
> Package: pristine-tar
> Version: 1.37
> Severity: normal
>
> Hi,
> Importing xz-utils fails
Importing new upstream of Digikam failed in the same manner:
steve@riemann:~/Packages/digikam/salsa$ gbp import-orig
On Monday, February 10, 2020 7:08:17 P.M. CST Christoph Anton Mitterer wrote:
> On Mon, 2020-02-10 at 12:56 +0100, Agustin Martin wrote:
> > Triaging some Debian bugs. Tried to reproduce this problem with
> > digikam
> > 4:6.4.0+dfsg-2 (currently in sid) but switching maps seems to work.
> > Is
On Sun, 09 Feb 2020 18:04:33 +0100 gregor herrmann wrote:
> Source: libmath-gmp-perl
> Version: 2.19-1
> Severity: serious
> Tags: upstream ftbfs sid bullseye
> Justification: fails to build from source (but built successfully in the
past)
I created a minimal pull request for this:
On Sunday, February 9, 2020 9:54:02 A.M. CST Marco Bodrato wrote:
> Ciao,
>
> From
> https://ci.debian.net/data/autopkgtest/testing/arm64/libm/libmath-gmp-perl/4
> 229384/log.gz I read the following:
>
> # Failed test 'Test worked: $x =
>
On Sunday, February 23, 2020 2:32:49 P.M. CST John Scott wrote:
> On February 23, 2020 3:11:46 PM EST, Marco Bodrato
wrote:
> >Ciao,
> >
> >Il Dom, 9 Febbraio 2020 9:34 pm, Steven Robbins ha scritto:
> >> On Sunday, February 9, 2020 9:54:02 A.M. CST Marco Bod
Hi Helmut,
I'm packaging a new Ipe version. I'd like to fix the bug you reported (below).
In order to test it: can you share the cross-build command you used?
Thanks,
-Steve
Bug 88522:
ipe fails to cross build from source, because its upstream build system
hard codes the build architecture
Hello Christoph,
As discussed in the bug, both Augustin and I have failed to reproduce your
symptoms. I noticed yesterday that you use a different locale than I, so I am
wondering whether that is part of the issue.
On Sun, 16 Apr 2017 15:44:44 +0200 Christoph Anton Mitterer
wrote:
>
On Wed, 04 Sep 2013 14:29:04 +0200 Johannes Rohr wrote:
> Package: digikam
> Version: 4:3.1.0-4
> Severity: normal
>
> Digikam saves the mysql password in ~/.kde/share/config/digikamrc. Instead it
should be stored securely in kdewallet
>
Confirmed that the issue remains in Digikam 7.0.0
>[ Steve Robbins ]
>* Update build-dep from swig3.0 --> swig3. Closes: #952599.
This is a typo: the build-dependency is just "swig", which is presently swig
4.
-Steve
signature.asc
Description: This is a digitally signed message part.
On Fri, 3 Jul 2020 22:14:18 +0200 Philipp Kern wrote:
> Would it be possible for googletest in Debian to ship these meson.build files
> alongside the source in the library packages? That way packages could
> build-depend on libgtest-dev without requiring them to use CMake.
It's a reasonable
On Thu, 6 Feb 2020 15:07:49 +0800 YunQiang Su wrote:
> Steven Robbins ?2020?2?6??? ??3:05???
> >
> > On Thursday, February 6, 2020 12:51:23 A.M. CST YunQiang Su wrote:
> > > Steven Robbins ?2020?2?6??? ??1:23???
> > >
> > > > On Tue,
On Wednesday, October 21, 2020 9:09:54 A.M. CDT Benjamin Eikel wrote:
> Package: googletest
> Version: 1.10.0.20201018-1
> Followup-For: Bug #972627
>
> Here is a minimal example that can be used to reproduce the problem:
Thanks! That's extremely helpful.
> Building with `g++ -std=c++20
On Tue, 16 May 2017 11:40:41 +0200 Adam Cecile wrote:
> Package: wnpp
> Severity: wishlist
> X-Debbugs-CC: debian-de...@lists.debian.org
>
> Package name: libjasper
> Version: 2.0.12
> Upstream: Michael David Adams
> License: JasPer License
> Description: This package has been scheduled for
On Sunday, June 21, 2020 6:29:11 A.M. CDT Antonio Radici wrote:
> Control: tag -1 +moreinfo
>
> On Mon, May 07, 2012 at 10:15:21PM -0500, Steve M. Robbins wrote:
> > Package: mutt
> > Version: 1.5.21-5+b1
> > Severity: important
> >
> > When viewing a message with attachments, 'v' to view
On Saturday, December 26, 2020 12:50:58 A.M. CST Keith Packard wrote:
> I've tagged version '1.0' of this repository and created some (not
> finished) debian packaging for it. This version has imported the mille
> sources from 'upstream' which include copyright information for the
> BSD-sourced
On Wednesday, January 6, 2021 12:43:52 P.M. CST R. Lemos wrote:
> Package: digikam
> Version: 4:7.1.0-1+b1
> Severity: normal
>
> The program crashes with message
>
> > digikam: symbol lookup error: /usr/lib/digikam/libdigikamcore.so.7.1.0:
> > undefined symbol:
Hello!
On Wednesday, January 6, 2021 3:05:38 P.M. CST R. Lemos wrote:
> In /usr/lib/x86_64-linux-gnu/libopencv_dnn.so.4.5.1 I've found a
> symbol `_ZN2cv3dnn14dnn4_v202011173NetC1Ev`. It differs from expected
> `_ZN2cv3dnn14dnn4_v202009083NetC1Ev` on `...20201117...` (expected
>
On Tuesday, December 15, 2020 11:10:32 A.M. CST Andreas Tille wrote:
> Hi again,
>
> sorry, I intended to respond to bug #977473 as well which really should
> be dealt with,
I had a look and can reproduce the build error.
(in fact my local build had more than just the one failure)
But this is
On Sunday, December 20, 2020 9:44:46 A.M. CST Adrian Bunk wrote:
> On Mon, Dec 07, 2020 at 09:12:23AM -0800, Keith Packard wrote:
> > Adrian Bunk writes:
> > > Keith, do you remember the copyright history of this code?
> >
> > I may have copied the underlying mille sources *before* copyrights
On Monday, February 22, 2021 5:46:05 A.M. CST Luca Boccassi wrote:
> Unless there are any objections, I'll upload an NMU to DELAYED/7 for
> buster-backports by the end of the week. Changelog bump is the only
> diff (debdiff will be attached).
Certainly no objection to your plan! I'll try to
On Tuesday, August 24, 2021 4:32:33 A.M. CDT Alain Bertrand wrote:
>
> Launching digikam
> digikam: symbol lookup error:
> /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5: undefined symbol:
> FT_Palette_Select and digikam exits
I have not encountered this myself.
A quick google suggested
On Wednesday, September 15, 2021 2:48:01 P.M. CDT Timo Röhling wrote:
> > Please add Depends: libgmock-dev to libgtest-dev.
>
> I just noticed that this bug not only breaks autopkgtest but also
> causes fastcdr to FTBFS.
>
> In case you're wondering, apparently this bug has been exposed by
>
On Wednesday, September 15, 2021 2:48:01 P.M. CDT Timo Röhling wrote:
> Control: tags 994419 + ftbfs
I thought this tag was for the case that the package fails to build from
source. ?? https://www.debian.org/Bugs/Developer
> I just noticed that this bug not only breaks autopkgtest
What
On Wednesday, September 15, 2021 2:25:49 P.M. CDT Timo Röhling wrote:
> Package: libgtest-dev
> Version: 1.10.0.20201025-1.1
I've discovered that upstream has released 1.11 -- which I'll package up.
> the GTestTargets.cmake that is shipped in libgtest-dev also exports
> the GTest::gmock and
> > It's a reasonable request. Where in the filesystem would you like to see
these
> > three files?
>
> The wrap is pretty specific in that googletest and googlemock have to be
> subdirectories. So effectively the wrap is unzipped today at the
> /usr/src/googletest level - which seems very
On Thursday, September 16, 2021 1:07:19 A.M. CDT you wrote:
> * Steven Robbins [2021-09-15 20:52]:
> >I thought this tag was for the case that the package fails to build from
> >source. ?? https://www.debian.org/Bugs/Developer
>
> I thought this is also transitively for
On Thursday, September 16, 2021 1:07:19 A.M. CDT you wrote:
> Sorry for the confussion, that also refers to fastcdr, which has a
> failing autopkgtest here:
> https://ci.debian.net/data/autopkgtest/testing/amd64/f/fastcdr/15272003/log.
> gz
So it looks like gtest 1.11.0 may well have fixed it.
On Wednesday, October 6, 2021 10:18:15 A.M. CDT Ghislain Vaillant wrote:
> * Package name: itk5
> Version : 5.2.1
Hi Ghislain. You surely know that ITK v4 is already in Debian. The salsa
project is called "insighttoolkit" and was where we had intended to put the
ITK v5
Hi,
I finally spent a few hours last night to get ITK v5 sources building. There's
still packaging work to do but I've pushed the interim results into salsa.
Note: as previously discussed, python bindings are removed.
On Tuesday, October 12, 2021 1:34:22 A.M. CDT ghisv...@gmail.com wrote:
>
On Monday, November 8, 2021 1:09:43 A.M. CST Andreas Tille wrote:
> Hi,
>
> this mail from Jose
>
> Am Sat, Nov 06, 2021 at 01:33:29AM +0100 schrieb Jose Luis Rivero:
> > Hello! Gazebo maintainer here, affected by this RC bug. Looking into
> > upstream repository there is a potential commit that
On Saturday, December 11, 2021 3:02:02 A.M. CST Étienne Mollier wrote:
> I considered pushing a change yesterday to disable those tests
> on insighttoolkit4,
Let's please agree to NEVER do that.
> not to hide dust under the carpet, but to
> give a chance to reverse dependencies to make it to
On Tue, 1 Feb 2022 21:01:39 +0100 Sebastian Ramacher
wrote:
> Source: digikam
> Version: 4:7.1.0-2
I have just uploaded Digikam 7.5.0 to unstable. If you have a chance to re-
try the build, would appreciate knowing if it now builds with new ffmpeg.
Thanks,
-Steve
signature.asc
Description:
On Mon, 03 May 2021 14:54:07 +0200 Philipp Marek
wrote:
> Package: digikam
> Version: 4:7.1.0-2
> Severity: normal
> X-Debbugs-Cc: phil...@marek.priv.at
>
> Just "apt-get install digikam -t testing" doesn't work - libcharls2 is
> left at 2.0.0+dfsg-1, but this digikam needs at least
On Saturday, January 22, 2022 12:15:25 P.M. CST Étienne Mollier wrote:
> Hi Andreas,
>
> Andreas Tille, on 2022-01-16:
> > I think the roadmap that ITK4 will be deleted as soon as possible
> > is clear. However, if it might serve as an intermediate means
> > to support some remaining
On Sunday, August 27, 2023 12:43:31 P.M. CDT Karine Crèvecœur wrote:
> (gdb) disassemble
>…
>0x76cc20e8 <+136>: movaps %xmm8,%xmm4
>0x76cc20ec <+140>: mov%edx,-0x4c(%rsp)
>0x76cc20f0 <+144>: mov0x38(%r9),%rdx
>0x76cc20f4 <+148>:
Package: wnpp
Severity: wishlist
Owner: "Steve M. Robbins"
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-...@lists.debian.org
* Package name: ubpm
Version : 1.9.0
Upstream Contact: Thomas Löwe
* URL : https://codeberg.org/LazyT/ubpm
* License : GPL v3
On Monday, October 23, 2023 1:00:09 P.M. CDT Thorsten Alteholz wrote:
> Hi,
>
> please ask upstream to add all licenses of embedded stuff like
> ./sources/plugins/shared/hidapi
Could you expand on this request? Each file notes "At the discretion of the
user of this library, this software may
Hi,
Just FYI: I applied the suggested patch (thanks Flavien!) to ITK. Let me
know if "sight" now builds.
-Steve
signature.asc
Description: This is a digitally signed message part.
On Saturday, August 19, 2023 11:53:35 A.M. CDT you wrote:
>Hi Steve,
>
>I'm afraid, it doesn't prevent digikam from crashing.
>
>Here is what I did (after fetching the latest updates from "testing" this
> morning):
[ ... ]
>Not sure if my approach is the preferred way to test
Hello Rainer,
Debian now has 8.1.0 uploaded to testing. I'm wondering if you can test that
and report back whether the issue persists or not.
Thanks,
-Steve
On Mon, 01 May 2023 23:37:00 +0200 Rainer Dorsch wrote:
> Comment 35 in upstream bugreport:
>
>
On Monday, August 14, 2023 8:52:14 A.M. CDT Steven Robbins wrote:
> So I'm back to square 1, very confused by your crash.
I have made a change to digikam and uploaded 8.1.0-3 last night. It should
avoid calling SSE 4 functions if only SSE 2 is detected. I'd appreciate if
you could
On Thu, 17 Aug 2023 11:34:56 +0200 Lucas Nussbaum wrote:
> Source: csh
> Version: 20110502-7
> Severity: serious
Is this really a serious enough issue to warrant removal from Debian?
>
> Hi,
>
> this package is maintained by ubuntu-devel-disc...@lists.ubuntu.com,
> which is not a suitable
On Saturday, April 23, 2022 7:23:48 A.M. CDT Hoareau Jean Pierre wrote:
> Package: digikam
> Version: 4:7.6.0-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
> I installed Debian "Bookworm" in order to test this version. When launching
> "Digikam" I get a
Hello,
On Wed, 22 Jun 2022 22:13:11 +0200 Sebastian Ramacher
wrote:
> ffmpeg got a new major release including API and ABI breakage. Hence, it
> needs a transition. The reverse dependencies are not yet ready, so this
> bug is just a heads up and should help to track progress. Due to
> ffmpeg's
control: severity -1 normal
On Fri, 25 Feb 2022 22:55:12 +0100 Sebastian Ramacher
wrote:
> On 2022-02-21 16:05:37 -0600, Steven Robbins wrote:
> > On Tue, 1 Feb 2022 21:01:39 +0100 Sebastian Ramacher
> > wrote:
> > > Source: digikam
> > > Version: 4:7.1.
On Saturday, July 9, 2022 8:26:21 A.M. CDT Christian Marillat wrote:
> Package: digikam
> Version: 4:7.7.0-1
> Severity: normal
>
> Dear Maintainer,
>
> Since the last version .heic files aren't
> displayed correctly. See attached screen capture.
I agree that does look odd. Can you share the
Hello,
Patrick suggested I chime in here, as the Digikam maintainer.
On Sat, 25 Jun 2022 23:42:47 +0200 Sebastian Ramacher
wrote:
> On 2022-06-25 20:45:37 +0200, Patrick Franz wrote:
> > Hi Sebastian,
> >
> > Am Samstag, 25. Juni 2022, 20:30:32 CEST schrieb Sebastian Ramacher:
> > [...]
> >
On Monday, July 11, 2022 1:02:23 A.M. CDT you wrote:
> (The more problems I see related to major library upgrades in debian,
> the less convinced I am that only supporting a single (major) version
> for all libraries really is a good idea. Then I again I am not the one
> doing the work, so I am
On Monday, July 11, 2022 1:38:31 A.M. CDT Christian Marillat wrote:
> After a rebuild under pbuilder, I confirm that libheif-dev is missing
> from Build-Depends. Adding libheif-dev in Build-Depends fix this issue.
Thank you for debugging this. I have uploaded -2 with the added build-
depends.
On Thursday, June 16, 2022 2:06:04 P.M. CDT Vincent Danjean wrote:
> According to the answer, this bug is already fixed in 7.7.0.
Digikam 7.7.0 was uploaded to Debian a few days ago; closing bug.
-Steve
signature.asc
Description: This is a digitally signed message part.
On Monday, June 6, 2022 6:11:38 A.M. CDT Bernhard Übelacker wrote:
> The recent dovecot upload contains this fix:
>
>dovecot (1:2.3.19+dfsg1-1) unstable; urgency=medium
> * [d223bbd] d/patches: add patch to support openssl 3.0 (Closes:
> #996273)
>
>
>
On Saturday, July 16, 2022 12:28:33 P.M. CDT Christian Marillat wrote:
> On 16 juil. 2022 12:02, Steven Robbins wrote:
>
> [...]
>
> > Certainly one can propose. However, one cannot really expect upstream to
> > change their architecture away from ffmpeg by a given ti
On Tue, 5 Jul 2022 10:13:20 +0200 Sebastian Ramacher
wrote:
> > > Reverse dependencies had 4 months to fix their bugs, so I'm going
> > > ahead with this one.
> >
> > Not even close to enough time for all affected upstream teams.
>
> The 4 months only reflects the Debian timeline. If
On Friday, July 15, 2022 6:27:51 P.M. CDT you wrote:
>Hi,
>
>This bug is rather anoying as I'm using digikam to manage my video.
I agree it is annoying. I feel the same pain.
Given the hard-transition of ffmpeg [1], it is not possible to build with video
in unstable today. Digikam
On Sunday, July 17, 2022 4:09:20 A.M. CDT you wrote:
> Le 16/07/2022 à 18:50, Steven Robbins a écrit :
> > I would say that there may well be others in your situation so if you do
> > find a method please report back to this bug.
>
>For my personnal use, until upstream p
On Thursday, July 21, 2022 11:24:03 A.M. CDT Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> > severity 1004769 important
>
> Bug #1004769 [src:digikam] Video support missing (FTBFS with ffmpeg 5.0)
> Severity set to 'important' from 'serious'
I had
Heads up for those following this bug: qtav appears to be unmaintained
upstream.
My only interest in the package was to enable video playback in digikam.
Digikam upstream has taken most of the qtav code, incorporated into digikam
source tree and fixed it up. The next release of digikam
On Mon, 22 Aug 2022 09:24:41 +0200 Sebastian Ramacher
wrote:
> > I can't reproduce this. The main difference between the one that built and
the
> > one that didn't is the new libc, so that's the most likely culprit.
>
> The 4th attempt on the buildds filed again:
Hi,
I'll start by a short digression. If you know the answer to this: what must I
do to get reliable replies to bugs sent to my email box? In my recollection
that was routine a number of years ago but nowadays I essentially never see
replies and only find them by happenstance -- when
On Thu, 8 Sep 2022 16:11:33 +0200 Paul Gevers wrote:
> With a recent upload of hdf5 the autopkgtest of libsis-jhdf5-java fails
> in testing when that autopkgtest is run with the binary packages of hdf5
> from unstable. It passes when run with only packages from testing.
I find the same holds
On Tue, 17 Mar 2015 14:53:06 +0100 Matthias Klose wrote:
> Package: src:insighttoolkit4
> Version: 4.6.0-3
>
> insighttoolkit is only built on amd64 and i386, while insighttoolkit3 worked
on
> some more architectures.
True. It became untenable to support other architectures and that hasn't
On Wednesday, December 7, 2022 4:12:09 A.M. CST Bas Couwenberg wrote:
> Package: ftp.debian.org
> Severity: normal
> User: ftp.debian@packages.debian.org
> Usertags: remove
> X-Debbugs-Cc: digi...@packages.debian.org
> Control: affects -1 + src:digikam
> Control: block 1025671 by -1
>
>
On Sunday, November 27, 2022 3:49:18 P.M. CST you wrote:
> Package: digikam
> Version: 4:7.7.0-3+b1
> Severity: normal
>
> Dear Maintainer,
>
> Would be nice to ave this version in bookworm
Will certainly get a new version into bookworm. It looks like there will be a
7.9.0 in the next week
On Sunday, January 29, 2023 11:10:22 A.M. CST Mathieu Malaterre wrote:
> On Tue, Nov 15, 2022 at 3:05 PM Steven Robbins wrote:
> > On Tuesday, November 15, 2022 7:44:13 A.M. CST Mathieu Malaterre wrote:
> > > jpeg-xl unit tests cannot be run on GNU/Hurd. It seems to be stuck
On Tuesday, November 15, 2022 7:44:13 A.M. CST Mathieu Malaterre wrote:
> jpeg-xl unit tests cannot be run on GNU/Hurd. It seems to be stuck for
> infinite time.
That is curious. It would help greatly if you had a minimal example.
-Steve
signature.asc
Description: This is a digitally signed
On Saturday, February 25, 2023 3:57:45 P.M. CST you wrote:
> Please don’t. I plan to upload the whole of Plasma 5.27.2 targeting
> bookworm.
Awesome, thanks!
> But please do follow-up on this and if the patch doesn’t make into the
> 5.27.2 upstream release you’re welcome to report it here so we
Just a note to say that I have used a Debian "testing" chroot environment and
can reproduce the reported crash. I will be investigating more in the coming
days.
-Steve
signature.asc
Description: This is a digitally signed message part.
Hi Rainer,
On Sun, 16 Apr 2023 09:38:07 +0200 Rainer Dorsch wrote:
> Let me elaborate a somewhat:
>
> The spash screen bug I found is visible in the backtrace in comment 5:
>
> https://bugs.kde.org/show_bug.cgi?id=466170#c5
>
> According to Maik, the bug is triggered by a race condition
On Tuesday, April 25, 2023 12:50:39 P.M. CDT Rainer Dorsch wrote:
> Am Dienstag, 25. April 2023, 03:51:44 CEST schrieben Sie:
> > I'd be interested to know if the issue persists on your system after
> > upgrading.
>
> Yes, it repros always.
OK.
> -- System Information:
> Debian Release: 12.0
>
On Fri, 14 Apr 2023 14:24:31 +0200 Rainer Dorsch wrote:
> Thanks Marco, that is a good link.
>
> I provided a backtrace and upstream acknowledged the bug to be fixed in
8.1.0:
Hello Rainer,
I've looked at the upstream bug, and all the information you provided. That's
awesome -- I wish that
On Friday, April 28, 2023 2:45:05 A.M. CDT Debian Bug Tracking System wrote:
> Processing control commands:
> > block 1034908 by -1
>
> Bug #1034908 [libabsl-dev] Update libabsl-dev to new upstream
> version/snapshot for newer protobuf 1034908 was not blocked by any bugs.
> 1034908 was blocking:
Hello,
Was looking yesterday for an RC bug to fix and noticed #1027965 against VTK --
a build failure in gdcm caused by missing dependency. The fix proposed by
Mathieu seems reasonable to me.
Anton: I'm writing to ask your opinion about the commits in salsa since the
last upload (June 2022);
There are a couple of odd things about this bug.
First: it doesn't seem like an RC bug because the test manifestly runs fine on
buildds -- see https://buildd.debian.org/status/package.php?p=sshfs-fuse
I'd suggest to downgrade the bug on this basis.
Second: the bug log shows python 3.9.2 is
On Sunday, February 5, 2023 7:04:26 P.M. CST Santiago Vila wrote:
> El 5/2/23 a las 21:54, Steven Robbins escribió:
> > the test manifestly runs fine on buildds
>
> Actually, that's not really true.
>
> The tests do not even *run* on the buildds, because they are skipped.
On Tuesday, July 4, 2023 10:03:27 A.M. CDT Peter Green wrote:
> Package: facet-analyser
> Version: 0.0~git20221121142040.6be10b8+ds1-3
> Tags: trixie, sid
> Severity: serious
> Justification: rc policy - "packages must be buildable within the same
> release" User: debian...@lists.debian.org
>
On Sunday, May 28, 2023 11:08:52 A.M. CDT Martin Hostettler wrote:
> [ Risks ]
>
> Steven Robbins described the problem the following way:
> > I couldn't say "harmless", but "mostly harmless", I'd think.
If it helps: Inventor is a system for visualizing 3D s
On Tue, 23 May 2023 10:21:29 +0200 Andreas Beckmann wrote:
> fonts-urw-base35 does not provide the old "numeric" font names
> gsfonts-x11 had.
Thanks for this. Do you happen to know of a package that does ship those
fonts, even if a different name?
> (gsfonts-x11 is now an empty transitional
tag 1024793 + wontfix
thanks
On Fri, 25 Nov 2022 11:18:41 +0800 zhangdandan wrote:
> Package: gmp
> Version: 6.2.1+dfsg1-1.1
> Severity: wishlist
> Tags: patch
> User: debian-de...@lists.debian.org
> Usertags: loongarch64
>
> Hi gmp maintainers,
>
> - update symbols for loongarch64.
> gmp
clone 1028507 -1
retitle -1 Create face-recognition data package
thanks
On Tuesday, July 18, 2023 5:38:21 A.M. CDT Gregor Riepl wrote:
> Would it be possible to create a separate Debian package with this data
> and add it as a Recommends: dependency?
Yes, and thanks for the reminder. The
On Thursday, July 27, 2023 3:23:07 A.M. CDT Detlef Matthiessen wrote:
> after updating digikam from 7.9.0-2 to 8.1.0-2, it crashes almost instantly:
> dm@fluke:~$ digikam
> Illegal instruction
>
> (...)
>
> If you need more information, please let me know.
Thanks -- we'll need a backtrace from
On Sun, 30 Jul 2023 10:22:19 +0200 Detlef Matthiessen
wrote:
> On 30.07.23 07:45, Detlef Matthiessen wrote:
> > 642QMatrix4x4 m = m1;
>
>On a related note: a quick search for "digikam" and "642" yields the
following bug report:
>
On Thu, 29 Jun 2023 13:40:42 +0300 Adrian Bunk wrote:
> 1153 | #error\
> | ^~
> 1154 | DCMTK was configured to use C++17 features, but your compiler does
not or was not configured to provide them.
> | ~
> ...
>
>
>
> This is due to:
>
On Monday, June 26, 2023 6:15:06 P.M. CDT Adrian Bunk wrote:
> Control: reassign -1 libinsighttoolkit5-dev 5.3.0-3
> Control: affects -1 src:plastimatch
>
> There are actually tow separate issues, both in libinsighttoolkit5-dev:
Thanks for bringing this to my attention.
> 1. The VTK build
forwarded 1028507 https://bugs.kde.org/show_bug.cgi?id=438317
thanks
On Thu, 12 Jan 2023 06:24:07 +0100 Christoph Anton Mitterer
wrote:
> Every time when starting digikam, a dialog pops up asking to download
> some engines for redeye removal and face detection from the internet,
> which would
Severity: normal
thanks
On Tue, 25 Apr 2023 22:49:03 -0500 Steven Robbins wrote:
> Given that no-one else has reported this,
> I'm leaning towards downgrading the severity to keep digikam in the upcoming
> release.
Setting severity to normal. If anyone reading this has encountered
On Monday, August 14, 2023 1:25:23 A.M. CDT Detlef Matthiessen wrote:
>Hi Steve,
>
>right after I replied to the bug report, I noticed:
>
> dm@fluke:/tmp$ diff test-no-sse4 test-sse4
> dm@fluke:/tmp$
>
>Can you confirm that the attached binaries are identical?
Nice catch. They are
On Sun, 30 Jul 2023 07:27:51 +0200 Detlef Matthiessen
wrote:
>
>Hi Steve,
>
>I've got:
>
> Program received signal SIGILL, Illegal instruction.
> 0x76cc20d3 in operator* (m1=..., m2=...) at
> /usr/include/x86_64-linux-gnu/qt5/
QtGui/qmatrix4x4.h:642
> Downloading source file
On Fri, 09 Feb 2024 16:08:00 +0100 Stephan Boettcher wrote:
> Package: ghostscript
> Version: 10.02.1~dfsg-3
> Severity: normal
>
> The version 10.0.0~dfsg-10 works and produces the expected output.
> 10.01.2~dfsg-1 works as well.
>
> 10.02.1~dfsg-3 does not:
>
> $ ps2epsi hvosc-doc_sch.ps
retitle 1022718 'ITA: ghostscript -- interpreter for the PostScript language
and for PDF'
owner 1022718 s...@debian.org
done 1036869
signature.asc
Description: This is a digitally signed message part.
severity 1057344 normal
thanks
On Sun, 3 Dec 2023 21:10:39 +0100 Vincent Lefevre wrote:
> Package: libgmp10
> Version: 2:6.2.1+dfsg1-1.1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
I understand the bug may have severe consequences but it doesn't appear to
On Mon, 24 Oct 2022 15:17:20 +0200 Jonas Smedegaard wrote:
> I have orphaned the ghostscript package, due to lack of time.
I'm willing to take on -- and hopefully, share -- the ghostscript maintenance.
If anyone wants to team up, let me know!
-Steve
signature.asc
Description: This is a
Package: lists.debian.org
Severity: normal
When reading lists via the web archive, there are three links below each
message that allow a reply. The reply contains the Subject and In-Reply-To
headers, but the message body is blank.
In contrast, the BTS archives provide the body of the message
1 - 100 of 134 matches
Mail list logo
