FYI: The status of the kpmcore source package
in Debian's testing distribution has changed.
Previous version: 4.0.1-2
Current version: 4.1.0-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
binary:projecteur is NEW.
binary:projecteur is NEW.
source:projecteur is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
projecteur_0.7-1_amd64.changes uploaded successfully to localhost
along with the files:
projecteur_0.7-1.dsc
projecteur_0.7.orig.tar.gz
projecteur_0.7-1.debian.tar.xz
projecteur-dbgsym_0.7-1_amd64.deb
projecteur_0.7-1_amd64.buildinfo
projecteur_0.7-1_amd64.deb
Greetings,
Your
gammaray 2.11.0-2 is marked for autoremoval from testing on 2020-03-01
It is affected by these RC bugs:
949903: gammaray: gammaray ftbfs on s390x
___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
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
Greetings from miss Sera toress Nice to meet you please can I talk with you.
___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gammaray | 2.11.0-2 | s390x
gammaray-dev | 2.11.0-2 | s390x
gammaray-plugin-bluetooth | 2.11.0-2 | s390x
gammaray-plugin-kjobtracker | 2.11.0-2 | s390x
On 24/02/2020 12:47, Agustin Martin wrote:
This bug has already been reported by me and fixed for 6.4
To be honest, it just disappeared for 6.4, bit I could not find an action
leading to that. According to "ldd -v /usr/bin/digikam" output digikam 5.9.0
had a dependency on
On Mon, Feb 24, 2020 at 11:38:40AM +0100, Eric Valette wrote:
> On 24/02/2020 10:50, Simon Frei wrote:
>
> > The error message you quote refers to so-version 100, while the required
> > one is 103. That suggests you aren't running the digikam binary from the
> > package, but something else (maybe
On 24/02/2020 12:57, Agustin Martin wrote:
Hi,
According to https://packages.debian.org/source/experimental/hdf5 there is a
new "libhdf5-hl-100" package in experimental. Looking into it, seems that
libhdf5_serial_hl.so.100 has been moved there, so installing that new package
should help in
On Mon, Feb 24, 2020 at 12:09:58PM +0100, Simon Frei wrote:
> On 24/02/2020 11:38, Eric Valette wrote:
> > On 24/02/2020 10:50, Simon Frei wrote:
> >
> >> one is 103. That suggests you aren't running the digikam binary from the
> >> package, but something else (maybe you self-compiled at some
Processing commands for cont...@bugs.debian.org:
> fixed #927145 4:7.0.0~beta2+dfsg-1
Bug #927145 [digikam] digikam: Digikam should depend on libhdf5-100
Marked as fixed in versions digikam/4:7.0.0~beta2+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> fixed #927145 4:6.4.0+dfsg-3
Bug #927145 [digikam] digikam: Digikam should depend on libhdf5-100
Marked as fixed in versions digikam/4:6.4.0+dfsg-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
927145:
On 24/02/2020 11:38, Eric Valette wrote:
> On 24/02/2020 10:50, Simon Frei wrote:
>
>> one is 103. That suggests you aren't running the digikam binary from the
>> package, but something else (maybe you self-compiled at some point?).
>> Check the output of which digikam.
>
>
> Did you just test
Your message dated Mon, 24 Feb 2020 11:44:12 +0100
with message-id <20200224104412.ga12...@agmartin.aq.upm.es>
and subject line Re: Bug#729217: digikam: Digikam crashes when importing from
mtpfs mounted Android device
has caused the Debian Bug report #729217,
regarding digikam: Digikam crashes
On Mon, 24 Feb 2020 10:14:54 +0100 Eric Valette
wrote:
> digikam
> digikam: error while loading shared libraries:
libhdf5_serial_hl.so.100: cannot open shared object file: No such file
or directory
>
> Has already been reported.
Did you just copy the error message from there, or did this error
Package: digikam
Version: 4:7.0.0~beta2+dfsg-1
Severity: grave
Justification: renders package unusable
digikam
digikam: error while loading shared libraries: libhdf5_serial_hl.so.100: cannot
open shared object file: No such file or directory
Has already been reported.
But in addition,
17 matches
Mail list logo
