Re: 20180210 IRC meeting wrap-up
On Wed, Mar 14, 2018 at 05:39:43PM +0300, Dmitry Shachnev wrote: > Hi Steve and all, > > On Wed, Mar 14, 2018 at 10:21:58AM -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: > > > Also: I am converting digikam from SVN -- also on alioth under kde-extras. > > > > At this step we want to be cautious because we want the SVN history to be > > kept > > as much as possible. Which tools did you use to convert the SVN repo to git? > > > > Without implying you did something wrong, I think Dmitry did very > > successful > > conversions from SVN to git. > > > > It would be real cool if we could check the import before pushing to the > > git > > repo. > > Right, my plan was to migrate all SVN repos at once. Great! I didn't realise anyone had planned to do this. I'll have a look at your migration results when I get home tonight. Thanks! -Steve signature.asc Description: PGP signature -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: 20180210 IRC meeting wrap-up
On Wed, Mar 14, 2018 at 10:21:58AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Hi Steve! > > El miércoles, 14 de marzo de 2018 01:33:47 -03 Steve Robbins escribió: > [snip] > > I have two more projects to place under kde-extras. > > > > I have a git repo (libmedialwiki) to migrate. It is presently on alioth > > under kde-extras so I would move it to the same on salsa. I guess I need > > to be a member of qt-kde-team first? (just requested access) > > Repo created, you have master permissions on it. I've imported it from alioth > so everything should be there already. Fantastic! Thank you! > > Also: I am converting digikam from SVN -- also on alioth under kde-extras. > > At this step we want to be cautious because we want the SVN history to be > kept > as much as possible. Which tools did you use to convert the SVN repo to git? > > Without implying you did something wrong, I think Dmitry did very successful > conversions from SVN to git. > > It would be real cool if we could check the import before pushing to the git > repo. Sure thing. I tarred up my work and put it on people.debian.org: file ~smr/convert-to-git-for-salsa.tar.gz I used svn2git with an authors file, following the "cut over migration" described here: https://salsa.debian.org/help/user/project/import/svn That document is literally the only thing I know about the process, so I would not be surprised if I goofed something up. Also: I would not be at all unhappy if someone else did the migration and import :-) Regards, -Steve signature.asc Description: PGP signature -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: Bug#834131: Video support still not working
On Wednesday, December 21, 2016 1:30:39 PM CST Lisandro Damián Nicanor Pérez Meyer wrote: > Well, the FRP was not done by a team member nor, as far as I know, anyone > one the team is thinking in packaging it. > > I'm CCing the RFP bug to see if he's still interested in packaging it. El se > I would suggest you to consider packaging it yourself. Having heard nothing, I will go ahead with packaging QtAV. I'd really rather do this as a team-maintained package. Is this something that would be suitable for KDE Extras? Thanks, -Steve signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: Bug#834131: Video support still not working
On Sunday, December 18, 2016 2:49:42 PM CST Simon Frei wrote: > [...] upstream has dropped QTmultimedia for video handling and uses > QtAV (which in turn is based of ffmpeg). Unfortunately QtAV is not yet > in debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737016), > however upstream provides debian packaging already, which worked almost > fine for me (buildep without -nc flag resulted in an error). This will > take effect in the upcoming 5.4.0 release due at the end of this month. Thanks for the heads-up on the change to QtAV. Question for the KDE maintainers: the RFP for QtAV is fairly old, which makes me wonder if there is any issue (technical or legal) that stands in the way of packaging it. ?? Thanks, -Steve signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Digikam 5.0.0 uploaded
Hi, I wanted to make people aware that I have uploaded Digikam 5.0.0 packages to Debian earlier today. I uploaded to experimental for staging for a few reasons: 1. To work through the build issues on various architectures. 2. The configuration files are in a new location, but digikam does no migration [1]. To the user, it appears you are starting from scratch and there is a risk of confusion -- the referenced bug is from someone who thought (mistakenly) that a migration procedure was required. The bug also references possibly using a KF5 function KConfig::copyTo() to migrate the files, but then concludes that some digikam 4 settings cause digikam 5 to crash. At this point, it seems that automatic migration is unsafe but that the initial configuration wizard should be augmented with text that describes the upgrade- from-4.x scenario better. I'm seeking suggestions on what might be the best approach here. 3. The showfoto internationalized docs are missing due to an upstream bug [2]. The bug is now patched upstream; however, the fix re-structures the source tarball so it is unclear whether this is easy to port into the current version; or better to wait for upstream 5.1.0 source tarball. Thanks, -Steve [1] https://bugs.kde.org/show_bug.cgi?id=364258 [2] https://bugs.kde.org/show_bug.cgi?id=365135 signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: Bug#810124: digikam: Does not show albums until kbuildsycoca is manually called
Sune, Thank you! That was a very, very helpful summary. On January 10, 2016 11:44:40 AM Sune Vuorela wrote: > (we iirc have a couple of similar bug reports open against other packages - > another workaround is to just start the application once more) OK, so it would be appropriate for me to simply close the bug, noting the workaround is to "quit and re-start digikam". Agree? Thanks, -Steve signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: Bug#810124: digikam: Does not show albums until kbuildsycoca is manually called
Hi, I recently picked up maintenance of digikam and haven't finished ramping up on KDE internals... I received the following bug report. I haven't noticed this problem myself, so it makes me wonder: 1. When, typically, is kbuildsyscoca run? The man page and google were unhelpful so far. 2. Is it true that "other Debian KDE packages" run kbuildsyscocoa4 -- noincremental on installation? Thanks, -Steve On January 6, 2016 07:05:51 PM you wrote: > Package: digikam > Version: 4:4.14.0-3 > Severity: important > Tags: patch > > Dear Maintainer, > > after installing digikam, no existing albums could be viewed. The error > message was: > > Couldn't create slave: "Unable to create io-slave: > klauncher said: Unknown protocol: digikamdates > > After calling > kbuildsycoca4 --noincremental > and > kbuildsycoca5 --noincremental > everything worked as expected. I didn't test it, but I assume, that the > latter command has been unnecessary, as digikamdates.protocol is located > in the KDE4 directory (/usr/share/kde4/services/). > > So please call > kbuildsycoca4 --noincremental > after normal package installation (as it is done in other Debian KDE > packages, although I do not know how it is done exactly). > > Kind regards > Patrick > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (900, 'testing'), (800, 'stable'), (500, 'unstable-debug'), > (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) > > Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages digikam depends on: > ii digikam-data4:4.14.0-3 > ii digikam-private-libs4:4.14.0-3 > ii kde-runtime 4:15.08.3-1 > ii libc6 2.21-6 > ii libgcc1 1:5.3.1-4 > ii libgphoto2-62.5.9-3 > ii libgphoto2-port12 2.5.9-3 > ii libkdcraw23 4:15.08.0-1+b1 > ii libkdecore5 4:4.14.14-1+b1 > ii libkdeui5 4:4.14.14-1+b1 > ii libkexiv2-114:15.04.3-1 > ii libkhtml5 4:4.14.14-1+b1 > ii libkio5 4:4.14.14-1+b1 > ii libkipi11 4:15.08.3-1 > ii libknotifyconfig4 4:4.14.14-1+b1 > ii libkparts4 4:4.14.14-1+b1 > ii libopencv-core2.4v5 2.4.9.1+dfsg-1.2 > ii libopencv-imgproc2.4v5 2.4.9.1+dfsg-1.2 > ii libphonon4 4:4.8.3-2 > ii libqt4-dbus 4:4.8.7+dfsg-5 > ii libqt4-sql 4:4.8.7+dfsg-5 > ii libqt4-sql-sqlite 4:4.8.7+dfsg-5 > ii libqt4-xml 4:4.8.7+dfsg-5 > ii libqtcore4 4:4.8.7+dfsg-5 > ii libqtgui4 4:4.8.7+dfsg-5 > ii libsolid4 4:4.14.14-1+b1 > ii libstdc++6 5.3.1-4 > ii libthreadweaver44:4.14.14-1+b1 > ii perl5.22.1-3 > ii phonon 4:4.8.3-2 > > Versions of packages digikam recommends: > ii chromium [www-browser] 46.0.2490.71-1 > ii iceweasel [www-browser] 43.0.2-1+b1 > ii kipi-plugins 4:4.14.0-3 > ii konqueror [www-browser] 4:15.08.3-1 > ii mplayerthumbs4:15.08.3-1 > ii w3m [www-browser]0.5.3-26 > > Versions of packages digikam suggests: > pn digikam-doc > ii systemsettings 4:5.4.3-1 > > -- no debconf information signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: Building DigiKam 4.14 with libkgeomanip and other former "extras"
[Since the conversation is now Debian-specific, I trimmed digikam-devel] On December 21, 2015 12:54:46 PM Lisandro Damián Nicanor Pérez Meyer wrote: > On Sunday 20 December 2015 17:22:07 Steve M. Robbins wrote: > > Question 1: Given that I'm building DigiKam 4.x, I presume I'll need a > > KDE4/Qt4 version of each extra. Is that the case? > > It should be, you can't mix Qt4 and Qt5 OK. Thanks for confirming. > > Question 2: If I can't use the latest kface, should I just go backwards in > > time to find the last release using KDE4 and use that with DigiKam? > > I'm afraid yes. > > Another solution could be to just build the 5.0.0 beta2 which, if I'm not > mistaken, uses Qt5/KF5. And maybe push it to experimental. I am aware of 5.x betas. I hesitate to use them right now because of the "beta" status. The announcement post itself [1] says "This version is for testing purposes. It’s not currently advised to use it in production." Maybe this is overcautious? Opinions welcome. If we do stick with the stable branch, we are probably stuck with it until next May [2]. So now the question is: for the "former extras" build-deps -- how do we co-exist the KDE4 and KF5 versions? Can the lib packages be made co-installable? Is there a package naming convention? From a quick build of libkface 15.04 (KDE4) and 15.12 (KF5) I can see the libraries are named differently (libkface.so / libKF5KFace.so). This gives me hope that at least the libs can remain co-installable. Additionally, the includes are in separate sub-dirs of /usr/include so maybe even the -dev packages can be co-installable? Thoughts / advice? Thanks, -Steve [1] https://www.digikam.org/node/749 [2] https://www.digikam.org/about/releaseplan signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: Digikam
Hi Lisandro, On December 20, 2015 01:18:31 PM Lisandro Damián Nicanor Pérez Meyer wrote: > On Saturday 19 December 2015 23:58:34 Steve M. Robbins wrote: > > I found the config file (commit-access-control.cfg). Who is able to edit > > this for me? > > I have just added you, just ping me if you still get problems. I see your change to svn+ssh://s...@svn.debian.org/svn/pkg-kde/scripts/svn- hooks/commit-access-control.cfg. However, the change didn't get propagated to the copy in the actual hooks directory on alioth (/svn/pkg-kde/hooks). I suspect this was supposed to be automatic, but it's possible a manual step was required. The permissions on files in the hooks directory are a bit odd; most are owned by root, but some have different owners. I suspect someone may have edited files directly in the past rather than relying on committing to "pkg- kde/scripts". In this specific instance, the file is not writeable by the group, which may be why your update was missed: smr@moszumanska:/svn/pkg-kde/hooks$ ls -l total 100 -rw-r--r--+ 1 pusling-guest scm_pkg-kde 4584 Nov 9 2014 commit-access- control.cfg -rwxrwxr-x+ 1 root scm_pkg-kde 11293 Oct 31 2003 commit-access- control.pl I took the liberty of updating the file manually using the filesystem -- so now it's owned by me :-( . However, I did set the group write bit; so hopefully can be maintained as normal in future. After that change, I was able to update digikam. Thanks for your help! -Steve signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
