[Pkg-kde-extras] Processed: fixed 885143 in 1:6.4.0~alpha1-0reprotest1, notfixed 753930 in 19.08.0, fixed 753930 in 19.08.0-1 ...

2020-02-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # fix bug metadata to allow archival
> fixed 885143 1:6.4.0~alpha1-0reprotest1
Bug #885143 {Done: Rene Engelhard } [libreoffice-gtk2] 
libreoffice-gtk2: Drop gtk2 support
There is no source info for the package 'libreoffice-gtk2' at version 
'1:6.4.0~alpha1-0reprotest1' with architecture ''
Unable to make a source version for version '1:6.4.0~alpha1-0reprotest1'
Marked as fixed in versions 1:6.4.0~alpha1-0reprotest1.
> notfixed 753930 19.08.0
Bug #753930 {Done: Scarlett Moore } [yakuake] [yakuake] 
Program Crashes On Setting
There is no source info for the package 'yakuake' at version '19.08.0' with 
architecture ''
Unable to make a source version for version '19.08.0'
No longer marked as fixed in versions 19.08.0.
> fixed 753930 19.08.0-1
Bug #753930 {Done: Scarlett Moore } [yakuake] [yakuake] 
Program Crashes On Setting
Marked as fixed in versions yakuake/19.08.0-1.
> notfound 940161 2.60.6-2
Bug #940161 {Done: Andreas Henriksson } [src:glib2.0] 
glib2.0: New upstream stable release 2.62.x
No longer marked as found in versions glib2.0/2.60.6-2.
> notfixed 596392 1.7.0
Bug #596392 {Done: Olly Betts } [sooperlooper] sooperlooper: 
Reproducible segmentation fault
There is no source info for the package 'sooperlooper' at version '1.7.0' with 
architecture ''
Unable to make a source version for version '1.7.0'
No longer marked as fixed in versions 1.7.0.
> fixed 596392 1.7.0~dfsg0-1
Bug #596392 {Done: Olly Betts } [sooperlooper] sooperlooper: 
Reproducible segmentation fault
Marked as fixed in versions sooperlooper/1.7.0~dfsg0-1.
> fixed 936963 1.19~bzr494-1
Bug #936963 {Done: Sandro Tosi } [src:loggerhead] loggerhead: 
Python2 removal in sid/bullseye
Marked as fixed in versions loggerhead/1.19~bzr494-1.
> tags 876920 + experimental
Bug #876920 {Done: Andreas Tille } [src:brian] brian FTBFS: 
weave has been removed from scipy
Added tag(s) experimental.
> tags 936239 + experimental
Bug #936239 {Done: Andreas Tille } [src:brian] brian: Python2 
removal in sid/bullseye
Added tag(s) experimental.
> tags 937442 - bullseye sid
Bug #937442 {Done: Markus Koschany } [src:pygame-sdl2] 
pygame-sdl2: Python2 removal in sid/bullseye
Removed tag(s) sid and bullseye.
> reassign 942059 src:gcc-9
Bug #942059 {Done: Matthias Klose } [src:gcc-9-cross] 
gcc-9-cross: uses “long” as “time_t” leading to failure on most new 32-bit 
architectures
Bug reassigned from package 'src:gcc-9-cross' to 'src:gcc-9'.
No longer marked as found in versions gcc-9-cross/12.
No longer marked as fixed in versions gcc-9/9.2.1-10.
> affects 942059 + src:gcc-9-cross
Bug #942059 {Done: Matthias Klose } [src:gcc-9] gcc-9-cross: 
uses “long” as “time_t” leading to failure on most new 32-bit architectures
Added indication that 942059 affects src:gcc-9-cross
> fixed 942059 9.2.1-10
Bug #942059 {Done: Matthias Klose } [src:gcc-9] gcc-9-cross: 
uses “long” as “time_t” leading to failure on most new 32-bit architectures
The source 'gcc-9' and version '9.2.1-10' do not appear to match any binary 
packages
Marked as fixed in versions gcc-9/9.2.1-10.
> tags 937394 + experimental
Bug #937394 {Done: Nobuhiro Iwamatsu } [src:pybluez] 
pybluez: Python2 removal in sid/bullseye
Added tag(s) experimental.
> notfixed 835088 3.0-1
Bug #835088 {Done: Marco Nenciarini } [repmgr] repmgr: 
'repmgr standby clone' does not copy all crucial files.
There is no source info for the package 'repmgr' at version '3.0-1' with 
architecture ''
Unable to make a source version for version '3.0-1'
No longer marked as fixed in versions repmgr/3.0-1.
> fixed 835088 3.0.1-1
Bug #835088 {Done: Marco Nenciarini } [repmgr] repmgr: 
'repmgr standby clone' does not copy all crucial files.
There is no source info for the package 'repmgr' at version '3.0.1-1' with 
architecture ''
Unable to make a source version for version '3.0.1-1'
Marked as fixed in versions 3.0.1-1.
> reassign 925673 src:insighttoolkit4
Bug #925673 {Done: Gert Wollny } [src:elastix] elastix: ftbfs 
with GCC-9
Bug reassigned from package 'src:elastix' to 'src:insighttoolkit4'.
No longer marked as found in versions elastix/4.9.0-1.
No longer marked as fixed in versions insighttoolkit4/4.13.2-dfsg1-1~exp2.
> fixed 925673 4.13.2-dfsg1-1~exp2
Bug #925673 {Done: Gert Wollny } [src:insighttoolkit4] 
elastix: ftbfs with GCC-9
The source 'insighttoolkit4' and version '4.13.2-dfsg1-1~exp2' do not appear to 
match any binary packages
Marked as fixed in versions insighttoolkit4/4.13.2-dfsg1-1~exp2.
> affects 925673 + src:elastix
Bug #925673 {Done: Gert Wollny } [src:insighttoolkit4] 
elastix: ftbfs with GCC-9
Added indication that 925673 affects src:elastix
> notfixed 863360 zzzeeksphinx/1.3.0+ds1-1
Bug #863360 {Done: Piotr Ożarowski } [python-sqlalchemy] 
python-sqlalchemy: versioned build-dep on python-zzzeeksphinx
The source zzzeeksphinx and version 1.3.0+ds1-1 do not appear to match any 
binary packages
No longer marked as fixed in versions zzzeeksphinx/1.3.0+ds1-1.
> fixed 863360 

[Pkg-kde-extras] yakuake_19.12.2-1_amd64.changes ACCEPTED into unstable

2020-02-06 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Feb 2020 18:06:16 +0100
Source: yakuake
Architecture: source
Version: 19.12.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Aurélien COUDERC 
Changes:
 yakuake (19.12.2-1) unstable; urgency=medium
 .
   * New upstream release (19.12.2).
   * Refresh patch to fix version in about dialog.
Checksums-Sha1:
 c806897caf3e3fd89c350a3b94bf0cf6c8508a51 2936 yakuake_19.12.2-1.dsc
 b3c7c77d382d70c575fabfc8783ebef9207a0968 372232 yakuake_19.12.2.orig.tar.xz
 6c10447df817ca9be198b433795fb41debcb531a 488 yakuake_19.12.2.orig.tar.xz.asc
 68b84360cf2b07830563372aefa3979545d20e1d 12664 yakuake_19.12.2-1.debian.tar.xz
 3348aea23183788b88cf9ba85d3bcac2b066857e 23894 
yakuake_19.12.2-1_amd64.buildinfo
Checksums-Sha256:
 808cdf3742efcd4da169c7878fa28797de3372ea2b98c6ad0b4ea129625d15ed 2936 
yakuake_19.12.2-1.dsc
 f6dc8e05e1649cccd1702e5cc8e6f5e04d9860e67b864a4745945be50cee43ac 372232 
yakuake_19.12.2.orig.tar.xz
 8dfb36ece6455585ff8db3704d2d5e267e7f712c377539c588229b313586be4d 488 
yakuake_19.12.2.orig.tar.xz.asc
 36900d0b5a5c556042cc902eb86f93d61bc353f3c3fe9786793cd898a09d2272 12664 
yakuake_19.12.2-1.debian.tar.xz
 e8bc18322021f811a19cf084856349b9368688aef59f64f02259460744c12436 23894 
yakuake_19.12.2-1_amd64.buildinfo
Files:
 7c788bbaeded3fc6aa95dc4d3a931bb4 2936 kde optional yakuake_19.12.2-1.dsc
 feea4fcf8f6aca19aa4dabe424b5c6ac 372232 kde optional 
yakuake_19.12.2.orig.tar.xz
 f1a9c5295ffd801844b444b5b6a92f9c 488 kde optional 
yakuake_19.12.2.orig.tar.xz.asc
 c2562e1116d81c2b431e8ce5d59ec11b 12664 kde optional 
yakuake_19.12.2-1.debian.tar.xz
 9e3bf05f9219c9c253a351cac72b1879 23894 kde optional 
yakuake_19.12.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl48SFQTHGNvdWNvdWZA
ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJAyzEAC7EG3B+LNS6jWLeX5qyaWgHKEIl/Ad
UJyVj7Zvf2ye7775RZlI8X5JJOY7kDaUXSomrNwHeRJPewpJaNOKW9cKKEQk2fhd
dQzMF3anbAvEnjmnqQs9bKN9xY8H6OwK3clW0rLgpV61iohLd5fQmRNwIKaDlIqf
DvbLpltMZiD931A/UCZRkCVVNpP6Nu0/iVMxajWn8qyfqPkxVCqqCsfZvknHIa/p
WZI0z/FYjQKTq2iTD3aJS1HWmspR4tQnh2cKxUpWUvJM7tKzUlmIr5IRLT+p+bhR
Kab7ofYStXQFaNpHeQKe6RoQPSMFA1ti71GzsIkQYIM7KMVfxbaXIFc1ajWCl87l
Fy+h+OMi052JRsvryUfELzh8ouCbyqBA4XcF9mOAqBpcVvHLbqOoOYBiV61nF1ls
47HqM4JCxjwv1GFmHK9S7pvwC02A42guDUwkQOwJ85P/CgFhV/rc/TH6l2tEYJlH
2PisFno3DmeoF7YyjcGwpy8gl66m+XXRX2gmrFbRsbPu8l7Brcjez+kiTE2+R94N
8xOQxXES0lz2Ry6n+Kx3LGDp3QIaMA8wJJWkPh31/rre1tE9czFQzocZtmlxyTmi
pfHyagvlW7sWa28+ibv7XFTZr2+AzrBDlMoXulbzGQoDHuqfbohLSzgoH9RmB2ZB
gJh+VcLwGYCbIg==
=FC+f
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Processing of yakuake_19.12.2-1_amd64.changes

2020-02-06 Thread Debian FTP Masters
yakuake_19.12.2-1_amd64.changes uploaded successfully to localhost
along with the files:
  yakuake_19.12.2-1.dsc
  yakuake_19.12.2.orig.tar.xz
  yakuake_19.12.2.orig.tar.xz.asc
  yakuake_19.12.2-1.debian.tar.xz
  yakuake_19.12.2-1_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#927145: marked as done (digikam: Digikam should depend on libhdf5-100)

2020-02-06 Thread Debian Bug Tracking System
Your message dated Thu, 6 Feb 2020 18:01:29 +0100
with message-id 
and subject line This is fixed with 6.4.0
has caused the Debian Bug report #927145,
regarding digikam: Digikam should depend on libhdf5-100
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:5.9.0-1+b1
Severity: important

digikam 
digikam: error while loading shared libraries: libhdf5_serial_hl.so.100: cannot 
open shared object file: No such file or directory



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.111 (SMP w/2 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages digikam depends on:
ii  digikam-data  4:5.9.0-1
ii  digikam-private-libs  4:5.9.0-1+b1
ii  kipi-plugins  4:5.9.0-1+b1
ii  libc6 2.28-8
ii  libgcc1   1:8.3.0-6
ii  libkf5configcore5 5.54.0-1
ii  libkf5coreaddons5 5.54.0-1
ii  libkf5filemetadata3   5.54.0-1
ii  libkf5i18n5   5.54.0-1
ii  libqt5core5a  5.11.3+dfsg1-1
ii  libqt5gui55.11.3+dfsg1-1
ii  libqt5sql55.11.3+dfsg1-1
ii  libqt5sql5-mysql  5.11.3+dfsg1-1
ii  libqt5sql5-sqlite 5.11.3+dfsg1-1
ii  libqt5widgets55.11.3+dfsg1-1
ii  libstdc++68.3.0-6
ii  perl  5.28.1-6

Versions of packages digikam recommends:
ii  ffmpegthumbs4:18.12.0-1
ii  firefox-esr [www-browser]   60.6.1esr-1
ii  google-chrome-stable [www-browser]  70.0.3538.77-1
ii  konqueror [www-browser] 4:18.12.0-1
ii  w3m [www-browser]   0.5.3-37

Versions of packages digikam suggests:
pn  digikam-doc 
ii  systemsettings  4:5.14.5-1.1

-- no debconf information
--- End Message ---
--- Begin Message ---


--eric--- End Message ---
___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#842610: marked as done (digikam lost track of photos when renaming an album)

2020-02-06 Thread Debian Bug Tracking System
Your message dated Thu, 6 Feb 2020 17:12:53 +0100
with message-id <20200206161253.ga125...@agmartin.aq.upm.es>
and subject line Re: Bug#842610: digikam lost track of photos when renaming an 
album
has caused the Debian Bug report #842610,
regarding digikam lost track of photos when renaming an album
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
842610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:5.2.0-2
Severity: normal

  Hi,

  First, note that my digikam version is 4:5.2.0-2.1 instead of
4:5.2.0-2 because I recompile it locally with -DENABLE_MEDIAPLAYER=on
(see #834131).

  I'm using digikam with a mysql database (since a long time).
Today, I noticed a bug when renaming albums. It seems that this
renaming is not taken into account in all internal data
structure.
  Here is what happen for example:
1) I renamed an album from Bricolage2 to Bricolage
  Everything seems working. I still see the 3 photos in
  this album.
2) I renamed the 3 photos in this album (using 'F2' and
  automatic rules for mass renaming). The result is
  strange:
  * digikam still shows the thumbnails with the old name
  * on disk, the pictures have really be renames (with their
*.xmp files too)
  * when trying to see the photo in big size, I get a blank
page
  * In log log below, you can see that after the rename
from IMG_* to date_time_IMG_* of photo filenames,
digikam print:
digikam.database: Starting scan!
digikam.database: Folder does not exist or is not readable:  
"/home/vdanjean/photos/albums/Activités/Bricolage2"
This is not normal that a reference to Bricolage2 still exists
at this time. Then, access to photos (with the old name) fail:
digikam.dimg: File  
"/home/vdanjean/photos/albums/Activités/Bricolage/IMG_20130731_134231.jpg"  
does not exist
digikam.metaengine: Cannot load metadata from file   (Error # 9 :  
/home/vdanjean/photos/albums/Activités/Bricolage/IMG_20130731_134231.jpg : 
Impossible d'ouvrir la source de données : Aucun fichier ou dossier de ce type 
(errno = 2)
...

  If I quit digikam and restart it, it cleans up the mess itself,
printing in the logs:

digikam.metaengine: Cannot load metadata from file   (Error # 9 :  
/home/vdanjean/photos/albums/Activités/Bricolage/IMG_20130731_134231.jpg : 
Impossible d'ouvrir la source de données : Aucun fichier ou dossier de ce type 
(errno = 2)
digikam.general: scan mode: ScanDeferredFiles
digikam.general: total scan value :  73181
digikam.dimg: 
"/home/vdanjean/photos/albums/Activités/Bricolage/2013-07-31_13-42-31_img_20130731_134231.jpg"
  : JPEG file identified
digikam.database: Adding new item 
"/home/vdanjean/photos/albums/Activités/Bricolage/2013-07-31_13-42-31_img_20130731_134231.jpg"
digikam.database: Recognized 
"/home/vdanjean/photos/albums/Activités/Bricolage/2013-07-31_13-42-31_img_20130731_134231.jpg"
 as identical to item 245847
digikam.database: Scanning took 2 ms
digikam.database: Finishing took 4 ms
digikam.dimg: 
"/home/vdanjean/photos/albums/Activités/Bricolage/2013-07-31_13-43-31_img_20130731_134331.jpg"
  : JPEG file identified
digikam.database: Adding new item 
"/home/vdanjean/photos/albums/Activités/Bricolage/2013-07-31_13-43-31_img_20130731_134331.jpg"
digikam.database: Recognized 
"/home/vdanjean/photos/albums/Activités/Bricolage/2013-07-31_13-43-31_img_20130731_134331.jpg"
 as identical to item 245848
digikam.database: Scanning took 1 ms
digikam.database: Finishing took 2 ms
digikam.dimg: 
"/home/vdanjean/photos/albums/Activités/Bricolage/2013-07-31_13-43-35_img_20130731_134335.jpg"
  : JPEG file identified
digikam.database: Adding new item 
"/home/vdanjean/photos/albums/Activités/Bricolage/2013-07-31_13-43-35_img_20130731_134335.jpg"
digikam.database: Recognized 
"/home/vdanjean/photos/albums/Activités/Bricolage/2013-07-31_13-43-35_img_20130731_134335.jpg"
 as identical to item 245849
digikam.database: Scanning took 2 ms
digikam.database: Finishing took 2 ms
digikam.database: Removed items: (245847, 245849, 245848) related items: ()
digikam.database: items to tag ()
digikam.database: Complete scan took: 1091 msecs.

  Now, my album correctly show the 3 photos with the new name.

  Regards,
Vincent


Logs after I did the album rename:

digikam.general: Detected change, triggering rescan of 
"/home/vdanjean/photos/albums/Activités/"
digikam.database: Starting scan!
digikam.general: SELECTED URLS TO RENAME:  
(QUrl("file:///home/vdanjean/photos/albums/Activités/Bricolage/IMG_20130731_134231.jpg"),
 

[Pkg-kde-extras] Bug#628635: marked as done (Photo selection dialog makes it hard to select multiple photos)

2020-02-06 Thread Debian Bug Tracking System
Your message dated Thu, 6 Feb 2020 15:38:29 +0100
with message-id <20200206143829.ga65...@agmartin.aq.upm.es>
and subject line Re: Bug#628635: Photo selection dialog makes it hard to select 
multiple photos
has caused the Debian Bug report #628635,
regarding Photo selection dialog makes it hard to select multiple photos
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
628635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 2:1.2.0-7
Severity: wishlist

I'm uploading photos to a Gallery using Export->Export to Gallery then
Add Photos.  I'm using Digikam rather than the Gallery website
directly so that I can add multiple photos more quickly.  The dialog
has an 'Open' button to trigger the upload of the selected photos.
However, any button release on an image triggers an immediate upload
-- to select multiple images I need to drag an image somewhere else
(to avoid a button release event over an image) then shift-click the
end of a range of images (which immediately triggers an upload of all
the images in the selected range).

It would be more useful if button releases when selecting images had
no side-effect, so that I could easily select as many images as I
want, then use the explicit button to trigger an upload.

Thanks,

-- 
Moray

-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages digikam depends on:
ii  digikam-data2:1.2.0-7digikam architecture-independant d
ii  kdebase-runtime 4:4.4.5-1runtime components from the offici
ii  kdepim-runtime  4:4.4.7-1Runtime components for akonadi-kde
ii  libc6   2.11.2-10Embedded GNU C Library: Shared lib
ii  libgcc1 1:4.4.5-8GCC support library
ii  libglib2.0-02.24.2-1 The GLib library of C routines
ii  libgphoto2-22.4.6-3  gphoto2 digital camera library
ii  libgphoto2-port02.4.6-3  gphoto2 digital camera port librar
ii  libice6 2:1.0.6-2X11 Inter-Client Exchange library
ii  libjasper1  1.900.1-7+b1 The JasPer JPEG-2000 runtime libra
ii  libjpeg62   6b1-1The Independent JPEG Group's JPEG 
ii  libkabc44:4.4.5-2library for handling address book 
ii  libkdcraw8  4:4.4.5-2RAW picture decoding C++ library (
ii  libkde3support4 4:4.4.5-2+squeeze1   the KDE 3 Support Library for the 
ii  libkdecore5 4:4.4.5-2+squeeze1   the KDE Platform Core Library
ii  libkdeui5   4:4.4.5-2+squeeze1   the KDE Platform User Interface Li
ii  libkexiv2-8 4:4.4.5-2Qt like interface for the libexiv2
ii  libkfile4   4:4.4.5-2+squeeze1   the File Selection Dialog Library 
ii  libkhtml5   4:4.4.5-2+squeeze1   the KHTML Web Content Rendering En
ii  libkio5 4:4.4.5-2+squeeze1   the Network-enabled File Managemen
ii  libkipi74:4.4.5-2library for apps that want to use 
ii  libkjsapi4  4:4.4.5-2+squeeze1   the KJS API Library for the KDE De
ii  libknotifyconfig4   4:4.4.5-2+squeeze1   library for configuring KDE Notifi
ii  libkparts4  4:4.4.5-2+squeeze1   the Framework for the KDE Platform
ii  libkresources4  4:4.4.5-2the KDE Resource framework library
ii  libkutils4  4:4.4.5-2+squeeze1   various utility classes for the KD
ii  liblcms11.18.dfsg-1.2+b3 Color management library
ii  liblensfun0 0.2.4-1  Lens Correction library - Runtime 
ii  liblqr-1-0  0.4.1-1  converts plain array images into m
ii  libmarblewidget44:4.4.5-2Marble globe widget library
ii  libnepomuk4 4:4.4.5-2+squeeze1   the Nepomuk Meta Data Library
ii  libphonon4  4:4.6.0really4.4.2-1 the core library of the Phonon mul
ii  libpng12-0  1.2.44-1 PNG library - runtime
ii  libqt4-dbus 4:4.6.3-4Qt 4 D-Bus module
ii  libqt4-network  4:4.6.3-4Qt 4 network module
ii  libqt4-qt3support   4:4.6.3-4Qt 3 compatibility library for Qt 
ii  libqt4-sql  4:4.6.3-4Qt 4 SQL module
ii  libqt4-sql-sqlite   4:4.6.3-4Qt 4 SQLite 3 database 

[Pkg-kde-extras] Bug#542951: kipi-plugins: Separate plugins with extra dependencies

2020-02-06 Thread Agustin Martin
On Sat, Aug 22, 2009 at 02:39:43PM +0200, Eduardo Ramírez wrote:
> Package: kipi-plugins
> Version: 0.5.0-1
> Severity: wishlist
> 
> Currently installing kipi-plugins also installs libavahi-client3, 
> libavahi-common-data, libavahi-common3, libsane and libksane0; even though I 
> don't have a scaner o user avahi. 
> 
> Me suggestion is separate the plugins that depend on sane into a 
> kipi-plugins-sane package.

digikam 6.4.0 is already uploaded to Debian sid, and kipi stuff is no
longer shipped with it, so I guess we can safely close this bug report.
Do you agree?

Thanks for the feedback.

Regards,

-- 
Agustin

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#884949: digikam crashes on red eye removal

2020-02-06 Thread Agustin Martin
On Thu, Dec 21, 2017 at 09:50:18PM +0100, Torsten Crass wrote:
> Package: digikam
> Version: 4:5.3.0-1
> Severity: normal
> 
> Dear Maintainer,
> 
> the digikam version currenlty included in Stretch (4:5.3.0-1) consistently
> crashes when trying to apply red eye reduction to an image. This behaviour
> is known upstream and is fixed in version 5.4 according to
> https://mail.kde.org/pipermail/digikam-devel/2016-November/090029.html
> 
> Would it be possible to upgrade Stretch's digikam to 5.4.* -- or even
> backport 4:5.6.0* from testing/unstable?

Hi, Torsten,

I am triaging some digikam old bug reports. Since current versions in Debian
are 5.9.0 (stable) and 6.4.0 (sid) this problem should be fixed, or at least
I did not find it in a quick test with 5.9.0. Is this still a problem for
you or can this bug report be closed?

Thanks for the feedback,

Regards,

-- 
Agustin

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#628631: marked as done (Photo uploading should use existing selection)

2020-02-06 Thread Debian Bug Tracking System
Your message dated Thu, 6 Feb 2020 15:31:17 +0100
with message-id <20200206143117.ga64...@agmartin.aq.upm.es>
and subject line Re: Bug#628631: Photo uploading should use existing selection
has caused the Debian Bug report #628631,
regarding Photo uploading should use existing selection
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
628631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 2:1.2.0-7
Severity: wishlist

To reproduce:

Select images
Use Export->Export to Gallery then Add Photos

Expected behaviour:

Selected photos are uploaded

Actual behaviour:

Another dialog pops up to select photos to upload

-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages digikam depends on:
ii  digikam-data2:1.2.0-7digikam architecture-independant d
ii  kdebase-runtime 4:4.4.5-1runtime components from the offici
ii  kdepim-runtime  4:4.4.7-1Runtime components for akonadi-kde
ii  libc6   2.11.2-10Embedded GNU C Library: Shared lib
ii  libgcc1 1:4.4.5-8GCC support library
ii  libglib2.0-02.24.2-1 The GLib library of C routines
ii  libgphoto2-22.4.6-3  gphoto2 digital camera library
ii  libgphoto2-port02.4.6-3  gphoto2 digital camera port librar
ii  libice6 2:1.0.6-2X11 Inter-Client Exchange library
ii  libjasper1  1.900.1-7+b1 The JasPer JPEG-2000 runtime libra
ii  libjpeg62   6b1-1The Independent JPEG Group's JPEG 
ii  libkabc44:4.4.5-2library for handling address book 
ii  libkdcraw8  4:4.4.5-2RAW picture decoding C++ library (
ii  libkde3support4 4:4.4.5-2+squeeze1   the KDE 3 Support Library for the 
ii  libkdecore5 4:4.4.5-2+squeeze1   the KDE Platform Core Library
ii  libkdeui5   4:4.4.5-2+squeeze1   the KDE Platform User Interface Li
ii  libkexiv2-8 4:4.4.5-2Qt like interface for the libexiv2
ii  libkfile4   4:4.4.5-2+squeeze1   the File Selection Dialog Library 
ii  libkhtml5   4:4.4.5-2+squeeze1   the KHTML Web Content Rendering En
ii  libkio5 4:4.4.5-2+squeeze1   the Network-enabled File Managemen
ii  libkipi74:4.4.5-2library for apps that want to use 
ii  libkjsapi4  4:4.4.5-2+squeeze1   the KJS API Library for the KDE De
ii  libknotifyconfig4   4:4.4.5-2+squeeze1   library for configuring KDE Notifi
ii  libkparts4  4:4.4.5-2+squeeze1   the Framework for the KDE Platform
ii  libkresources4  4:4.4.5-2the KDE Resource framework library
ii  libkutils4  4:4.4.5-2+squeeze1   various utility classes for the KD
ii  liblcms11.18.dfsg-1.2+b3 Color management library
ii  liblensfun0 0.2.4-1  Lens Correction library - Runtime 
ii  liblqr-1-0  0.4.1-1  converts plain array images into m
ii  libmarblewidget44:4.4.5-2Marble globe widget library
ii  libnepomuk4 4:4.4.5-2+squeeze1   the Nepomuk Meta Data Library
ii  libphonon4  4:4.6.0really4.4.2-1 the core library of the Phonon mul
ii  libpng12-0  1.2.44-1 PNG library - runtime
ii  libqt4-dbus 4:4.6.3-4Qt 4 D-Bus module
ii  libqt4-network  4:4.6.3-4Qt 4 network module
ii  libqt4-qt3support   4:4.6.3-4Qt 3 compatibility library for Qt 
ii  libqt4-sql  4:4.6.3-4Qt 4 SQL module
ii  libqt4-sql-sqlite   4:4.6.3-4Qt 4 SQLite 3 database driver
ii  libqt4-svg  4:4.6.3-4Qt 4 SVG module
ii  libqt4-xml  4:4.6.3-4Qt 4 XML module
ii  libqtcore4  4:4.6.3-4Qt 4 core module
ii  libqtgui4   4:4.6.3-4Qt 4 GUI module
ii  libsm6  2:1.1.1-1X11 Session Management library
ii  libsolid4   4:4.4.5-2+squeeze1   Solid Library for KDE Platform
ii  libsoprano4 2.5.0+dfsg.1-1   libraries for the Soprano RDF fram
ii  libstdc++6  4.4.5-8  The GNU Standard C++ Library v3
ii  libtiff43.9.4-5+squeeze1 Tag Image File Format (TIFF) 

[Pkg-kde-extras] Bug#842610: digikam lost track of photos when renaming an album

2020-02-06 Thread Vincent Danjean
  Hi,

Le 06/02/2020 à 13:35, Agustin Martin a écrit :
> Triaging old bug reports. Is this still a problem with current digikam
> (6.4.0 in sid)? I tried some simple renamings with 6.4.0 and seems to work.

  I think that this particular bug can be closed. However, from times to
times, the digikam database become corrupted. But I do not know what
triggers this (renames or other things). I see the corruption when I
remark some images on disk but not displayed in Digikam.
  I keep on my disk these notes to help me to fix the database:

use digikamdb;

Cleanup Comments :
SELECT * FROM ImageComments i LEFT OUTER JOIN Images ON Images.id=i.imageid 
WHERE Images.name IS NULL;
DELETE i FROM ImageComments i LEFT OUTER JOIN Images ON Images.id=i.imageid 
WHERE Images.name IS NULL;
Cleanup Copyright :
SELECT * FROM ImageCopyright i LEFT OUTER JOIN Images ON Images.id=i.imageid 
WHERE Images.name IS NULL;
DELETE i FROM ImageCopyright i LEFT OUTER JOIN Images ON Images.id=i.imageid 
WHERE Images.name IS NULL;
Cleanup Information :
SELECT * FROM ImageInformation i LEFT OUTER JOIN Images ON Images.id=i.imageid 
WHERE Images.name IS NULL;
DELETE i FROM ImageInformation i LEFT OUTER JOIN Images ON Images.id=i.imageid 
WHERE Images.name IS NULL;
Cleanup Metadata :
SELECT * FROM ImageMetadata i LEFT OUTER JOIN Images ON Images.id=i.imageid 
WHERE Images.name IS NULL;
DELETE i FROM ImageMetadata i LEFT OUTER JOIN Images ON Images.id=i.imageid 
WHERE Images.name IS NULL;
Cleanup Tags :
SELECT * FROM ImageTags i LEFT OUTER JOIN Images ON Images.id=i.imageid WHERE 
Images.name IS NULL;
DELETE i FROM ImageTags i LEFT OUTER JOIN Images ON Images.id=i.imageid WHERE 
Images.name IS NULL;


Images without information :
select CONCAT(relativePath, '/', name) from Images LEFT OUTER JOIN 
ImageInformation on Images.id=ImageInformation.imageid LEFT OUTER JOIN Albums 
on Images.album=Albums.id where ImageInformation.imageid is NULL INTO OUTFILE 
'/var/lib/mysql-files/digikam.log' ;

RESTART:
sudo cat /var/lib/mysql-files/digikam.log | while read file ; do 
f="$HOME/photos/albums/$file"; if [ -f "$f"  ] ; then touch "$f" ; else echo 
"Missing $f" ; fi ; done
sudo cat /var/lib/mysql-files/digikam.log  | sed -e 's,/[^/]*$,,' | sort -u
 In digikam, reload metadata from files in these albums

Check that all info is loaded with
select CONCAT(relativePath, '/', name) from Images LEFT OUTER JOIN 
ImageInformation on Images.id=ImageInformation.imageid LEFT OUTER JOIN Albums 
on Images.album=Albums.id where ImageInformation.creationDate is NULL AND 
status != 3 ;

GOTO RESTART


And, to force film thumbnails regeneration in an album:
delete from UniqueHashes where thumbId in (select thumbId from FilePaths where 
path like "%17_Irlande/%.avi" );
describe Thumbnails ;
delete from Thumbnails where id in (select thumbId as id from FilePaths where 
path like "%17_Irlande/%.avi" );
delete from FilePaths where path like "%17_Irlande/%.avi" ;



That said, I just checked now. No rows have been reported at all
(and I do not run these commands since a long time), so the bugs
can have been fixed.

  Regards,
Vincent


> Regards,
> 


-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#842610: digikam lost track of photos when renaming an album

2020-02-06 Thread Agustin Martin
On Sun, Oct 30, 2016 at 08:38:03PM +0100, Vincent Danjean wrote:
> Package: digikam
> Version: 4:5.2.0-2
> Severity: normal
> 
>   Hi,
> 
>   First, note that my digikam version is 4:5.2.0-2.1 instead of
> 4:5.2.0-2 because I recompile it locally with -DENABLE_MEDIAPLAYER=on
> (see #834131).
> 
>   I'm using digikam with a mysql database (since a long time).
> Today, I noticed a bug when renaming albums. It seems that this
> renaming is not taken into account in all internal data
> structure.
>   Here is what happen for example:
> 1) I renamed an album from Bricolage2 to Bricolage
>   Everything seems working. I still see the 3 photos in
>   this album.
> 2) I renamed the 3 photos in this album (using 'F2' and
>   automatic rules for mass renaming). The result is
>   strange:
>   * digikam still shows the thumbnails with the old name
>   * on disk, the pictures have really be renames (with their
> *.xmp files too)
>   * when trying to see the photo in big size, I get a blank
> page
>   * In log log below, you can see that after the rename
> from IMG_* to date_time_IMG_* of photo filenames,
> digikam print:
> digikam.database: Starting scan!
> digikam.database: Folder does not exist or is not readable:  
> "/home/vdanjean/photos/albums/Activités/Bricolage2"
> This is not normal that a reference to Bricolage2 still exists
> at this time. Then, access to photos (with the old name) fail:
> digikam.dimg: File  
> "/home/vdanjean/photos/albums/Activités/Bricolage/IMG_20130731_134231.jpg"  
> does not exist
> digikam.metaengine: Cannot load metadata from file   (Error # 9 :  
> /home/vdanjean/photos/albums/Activités/Bricolage/IMG_20130731_134231.jpg : 
> Impossible d'ouvrir la source de données : Aucun fichier ou dossier de ce 
> type (errno = 2)
> ...
> 
>   If I quit digikam and restart it, it cleans up the mess itself,

Hi, Vincent

Triaging old bug reports. Is this still a problem with current digikam
(6.4.0 in sid)? I tried some simple renamings with 6.4.0 and seems to work.

Regards,

-- 
Agustin

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#546403: kipi-plugins: includes Adobe DNG SDK, with problematic license

2020-02-06 Thread Simon Frei
DNG support is still present in digiKam, COPYING-ADOBE is now found in
core/libs/dngwriter.

reassign 546403 digikam
thanks

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Processed (with 2 errors): Re: Bug#546403: kipi-plugins: includes Adobe DNG SDK, with problematic license

2020-02-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> DNG support is still present in digiKam, COPYING-ADOBE is now found in
Unknown command or malformed arguments to command.
> core/libs/dngwriter.
Unknown command or malformed arguments to command.
> reassign 546403 digikam
Bug #546403 [kipi-plugins] kipi-plugins: includes Adobe DNG SDK, with 
problematic license
Bug reassigned from package 'kipi-plugins' to 'digikam'.
No longer marked as found in versions kipi-plugins/0.6.0-1.
Ignoring request to alter fixed versions of bug #546403 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
546403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#799778: digikam: Not able to import pictures from CANON EOS350D after upgrading from 3.5

2020-02-06 Thread Agustin Martin
On Sun, Dec 20, 2015 at 10:57:05PM -0600, Steve M. Robbins wrote:
> On Tue, 22 Sep 2015 15:34:20 +0200 Etienne BRETTEVILLE 
>  wrote:
> 
> > After upgrading from LinuxMintDebianEdition LMDE 1 (based on debian 7) to 
> LMDE2
> > based on debian Jessie, digikam has been updated to 4.4.0 instead of 3.5.x.
> > 
> > Since then I'm no longer able to import my pictures from my CanonEOS350D 
> using
> > the importation tool from digikam.
> > 
> > You can see the error message in the screenshot here:
> > https://framapic.org/AiUtTFceoQN0/lexIQ4R7
> > 
> > What about introducing the latest revsion of digikam, 4.13.0?!
> 
> I just uploaded 4.14 today.  If you are in a position to try that out, I'd be 
> very glad to know if it fixes this issue.

Hi,

This was a while ago, currently in Debian we have 6.4.0 in sid and 5.9.0
in stable. Is this still a problem for you?

Also note that we do not have control on local changes that may have been
included in Mint.

Regards,

-- 
Agustin

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#546403: kipi-plugins: includes Adobe DNG SDK, with problematic license

2020-02-06 Thread Agustin Martin
On Sun, Sep 13, 2009 at 08:51:06AM +0300, Lars Wirzenius wrote:
> Package: kipi-plugins
> Version: 0.6.0-1
> Severity: severe
> Justification: presumed non-free license for included library
> 
> kipi-plugins contains a copy of the Adobe DNG SDK, which the ftpmasters
> (specifically, Joerg Jaspert) has deemed to have a problematic license,
> preventing it from being packaged in main. kipi-plugins includes a copy
> of the license in COPYING-ADOBE.

Hi,

As of 4:6.4.0+dfsg-1 kipi stuff is no longer shipped and its support seems
removed upstream. So, I guess this is no longer an issue.

Regards,

-- 
Agustin

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#927145: digikam: Digikam should depend on libhdf5-100

2020-02-06 Thread Agustin Martin
On Mon, Apr 15, 2019 at 04:48:38PM +0200, valette wrote:
> Package: digikam
> Version: 4:5.9.0-1+b1
> Severity: important
> 
> digikam 
> digikam: error while loading shared libraries: libhdf5_serial_hl.so.100: 
> cannot open shared object file: No such file or directory

Hi,

Steve has already uploaded digikam 6.4.0 to sid and I am looking at some of
the pending bug reports. Is this still an issue for you?

For 6.4.0 I cannot reproduce the problem and also do not see anything hdf
related in "ldd -v /usr/bin/digikam" output.

Regards,

-- 
Agustin

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] Bug#918478: Digikam imageeditor blank screen patch, backported from Digikam 6.0

2020-02-06 Thread Agustin Martin
On Sat, Nov 09, 2019 at 05:36:07PM -0500, Timothy E. Harris wrote:
> Because this bug affected me, I backported the patch from Digikam 6.0 to the
> buster digikam version

Hi,

Thanks for the patch. Steve has just uploaded digikam 6.4.0, which should
include the fix, to sid. I have minimally tested it and this problem seems
gone here.

¿Is it also fixed for you?

Regards,

-- 
Agustin

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras

[Pkg-kde-extras] krename_5.0.0-2_source.changes ACCEPTED into unstable

2020-02-06 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Feb 2020 08:43:18 +0100
Source: krename
Architecture: source
Version: 5.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Pino Toscano 
Changes:
 krename (5.0.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Switch Vcs-* fields to salsa.debian.org.
   * Add the configuration for the CI on salsa.
   * Bump the debhelper compatibility to 12:
 - switch the debhelper build dependency to debhelper-compat 12
 - remove debian/compat
 - remove --parallel for dh, as now done by default
   * Switch the transitional libfreetype6-dev build dependency to
 libfreetype-dev.
   * Bump Standards-Version to 4.5.0, no changes required.
   * Backport upstream commits ec90823494f5ec9bb2e8098f44209f383ef8c22a, and
 b22de9135ba2a5abdbd2b275a60933a50f074010 to properly detect exiv2 >= 0.27,
 and build with it; patches
 upstream_Use-cmakedefine01-instead-of-macro_bool_to_01.patch, and
 upstream_Fix-building-against-exiv2-0.27.patch.
 - add a lintian override for the spelling error in the upstream commit
   message
Checksums-Sha1:
 eb017f6d8e111718303c7f7450705d36d6540613 2309 krename_5.0.0-2.dsc
 9c43bdadb7be7413d2c860244958cfde868700c7 8784 krename_5.0.0-2.debian.tar.xz
 cbd691ac6f7e055e1478b9760a50d4a0e7bb045b 15198 krename_5.0.0-2_source.buildinfo
Checksums-Sha256:
 1fa58960015de0966c1983732434e2e9aaf40651766c4dbd012c82e687885ea4 2309 
krename_5.0.0-2.dsc
 55267cb30cb5949fad3495f1ca4698193b31afe9805086c68fbc1b9ae6813794 8784 
krename_5.0.0-2.debian.tar.xz
 2b76758aadbcfbfa33e1d0de406b5f2b7102595b8e5c57688289690e6e06476e 15198 
krename_5.0.0-2_source.buildinfo
Files:
 45de2686a88ed2792ac870d7fba489c1 2309 utils optional krename_5.0.0-2.dsc
 ebd5670051119b044a435b1b67434405 8784 utils optional 
krename_5.0.0-2.debian.tar.xz
 17d2bad97d781c8e6f53c6bc9ec00238 15198 utils optional 
krename_5.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl47w+AACgkQLRkciEOx
P002tA//XRLI1ts2skzP8sVSkpu0zUBBqnEeAqdx19kQd2+ncE/3820y3y0q5m3b
b+fYx10eNyQsF+MI0U95XrjDMAIMNhBGYD8ogi8tRAeM/rh3o8ln9vTZM+erOZqj
cT6UxFM4Lh1NwChH9z3XSYZn03+TTwbwNepduKFbpI07KP82J8iZjRH2QJxFBiWK
4NLMiyU812EKeM1wJljdBTuWICdLv3+IGlYVXPAzLa/F6nE8ittvfd4QU/uiJl8q
ZlYeOqsJqIZcCYHr75d82hYpU0NFczYHlFSSrT1/CQ0mSI3e/NLZqyGx8WKNh8eL
j+sZmb1bEPmiUugir+YoEcSVnggBVTaWOlo91fO/kNB07HT/NhAEXN6Ifjgt/84L
8srOGyqzb+zgA1gJ9BjhEkcGwvl2ZRZQdttyEqypOEsKpqpEXqtiO6y5KEIDMKeW
WPD9TfOBW82KcqmPP9LKIGEVd5JP+lgUbjGlXojb8ayEL/l0gZxFfGwut2JNCglm
39VjfbA/NiHxbHhpeZT+cg/7g7Q/77q/W6itC2hj/aOcS/P8ZlvD5/YAer7Jqfud
bIQBuD73qae9Rvc5pzt6E1IyNsJjOrUjYhoQB6uvBM3l8LfSM/IxVdy8AnWjEgPm
4h/E3UbNy0lIl8IRBckI7+MPXIIi+hOifW+G0LF3P/ABo39JV9M=
=IVvW
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras