Bug#1058802: bluez-qt: use udev.pc to place udev rules

[Chris Hofstaedtler]

Source: bluez-qt
Version: 5.107.0-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch using udev.pc to place the udev files
(using pkg-config). This works today in unstable and also for
bookworm, and is safe to do now.
Once udev.pc in unstable points to /usr/lib your package will
benefit automatically after a binNMU or any other upload.

If during the trixie cycle your package will undergo structural
changes or any other file moves, please see the wiki and upload
to experimental first when these changes are done.

Later during the trixie cycle I expect this bug class to raise in
priority.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -Nru bluez-qt-5.107.0/debian/changelog bluez-qt-5.107.0/debian/changelog
--- bluez-qt-5.107.0/debian/changelog	2023-06-18 16:08:24.0 +0200
+++ bluez-qt-5.107.0/debian/changelog	2023-12-16 19:29:22.0 +0100
@@ -1,3 +1,10 @@
+bluez-qt (5.107.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use udev.pc to place udev files. (Closes: #-1)
+
+ -- Chris Hofstaedtler   Sat, 16 Dec 2023 19:29:22 +0100
+
 bluez-qt (5.107.0-1) unstable; urgency=medium
 
   [ Aurélien COUDERC ]
diff -Nru bluez-qt-5.107.0/debian/control bluez-qt-5.107.0/debian/control
--- bluez-qt-5.107.0/debian/control	2023-06-18 16:05:36.0 +0200
+++ bluez-qt-5.107.0/debian/control	2023-12-16 19:29:22.0 +0100
@@ -11,11 +11,13 @@
extra-cmake-modules (>= 5.107.0~),
libqt5sql5-sqlite,
pkg-kde-tools (>> 0.15.15),
+   pkgconf,
qml-module-qttest ,
qtbase5-dev (>= 5.15.2~),
qtdeclarative5-dev (>= 5.15.2~),
qttools5-dev,
qttools5-dev-tools,
+   systemd-dev,
xauth ,
xvfb ,
 Standards-Version: 4.6.2
diff -Nru bluez-qt-5.107.0/debian/libkf5bluezqt-data.install bluez-qt-5.107.0/debian/libkf5bluezqt-data.install
--- bluez-qt-5.107.0/debian/libkf5bluezqt-data.install	2022-08-21 17:08:55.0 +0200
+++ bluez-qt-5.107.0/debian/libkf5bluezqt-data.install	2023-12-16 19:29:22.0 +0100
@@ -1,3 +1,3 @@
-lib/udev/rules.d/61-kde-bluetooth-rfkill.rules
+${env:deb_udevdir}/rules.d/61-kde-bluetooth-rfkill.rules
 usr/share/qlogging-categories5/bluezqt.categories
 usr/share/qlogging-categories5/bluezqt.renamecategories
diff -Nru bluez-qt-5.107.0/debian/libkf5bluezqt-data.lintian-overrides bluez-qt-5.107.0/debian/libkf5bluezqt-data.lintian-overrides
--- bluez-qt-5.107.0/debian/libkf5bluezqt-data.lintian-overrides	2023-06-17 07:37:36.0 +0200
+++ bluez-qt-5.107.0/debian/libkf5bluezqt-data.lintian-overrides	2023-12-16 19:29:22.0 +0100
@@ -1,2 +1,6 @@
+# begin-remove-after: released:forky
 # This only sets uaccess, we do not actually have hardware support here.
 libkf5bluezqt-data: appstream-metadata-missing-modalias-provide lib/udev/rules.d/61-kde-bluetooth-rfkill.rules
+# end-remove-after
+# This only sets uaccess, we do not actually have hardware support here.
+libkf5bluezqt-data: appstream-metadata-missing-modalias-provide usr/lib/udev/rules.d/61-kde-bluetooth-rfkill.rules
diff -Nru bluez-qt-5.107.0/debian/rules bluez-qt-5.107.0/debian/rules
--- bluez-qt-5.107.0/debian/rules	2023-03-16 22:42:01.0 +0100
+++ bluez-qt-5.107.0/debian/rules	2023-12-16 19:29:22.0 +0100
@@ -1,4 +1,5 @@
 #!/usr/bin/make -f
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
 
 # Disable fixfilepath, as it triggers build failures.
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all reproducible=-fixfilepath
@@ -7,7 +8,7 @@
 	dh $@ --with pkgkde_symbolshelper
 
 override_dh_auto_configure:
-	dh_auto_configure -- -DBUILD_QCH=ON
+	dh_auto_configure -- -DBUILD_QCH=ON -DUDEV_RULES_INSTALL_DIR=/${deb_udevdir}/rules.d
 
 override_dh_auto_test:
 	xvfb-run -a dbus-run-session dh_auto_test

Bug#1042932: ksshaskpass: Error message from ksshaskpass: QSocketNotifier: Can only be used with threads started with QThread

[Chris Hanson]

Package: ksshaskpass
Version: 4:5.27.5-2
Severity: minor
X-Debbugs-Cc: c...@chris-hanson.org

Dear Maintainer,

This has been happening since I installed Debian shortly after the
release.  I believe it's caused by ksshaskpass and not ssh because the
message goes away when the key is added to the ssh key agent.

I haven't tested this with a different askpass program but I think
it's pretty obvious that this is a qt/kde issue.

FWIW I'm running KDE on Wayland.

Please let me know if you need any other info.

Chris

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

Kernel: Linux 6.1.0-10-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ksshaskpass depends on:
ii  libc6 2.36-9+deb12u1
ii  libkf5coreaddons5 5.103.0-1
ii  libkf5i18n5   5.103.0-1
ii  libkf5wallet-bin  5.103.0-1
ii  libkf5wallet5 5.103.0-1
ii  libkf5widgetsaddons5  5.103.0-1
ii  libqt5core5a  5.15.8+dfsg-11
ii  libqt5widgets55.15.8+dfsg-11
ii  libstdc++612.2.0-14
ii  openssh-client1:9.2p1-2

Versions of packages ksshaskpass recommends:
ii  kwalletmanager  4:22.12.3-1

ksshaskpass suggests no packages.

-- no debconf information

gpgsm: UI asks insane, unanswerable trust questions

[chris]

Dear maintainer,

I've recently started to re-experience that bug (#888025), probably because 
someone is sending me emails using some "certificate".

It is in the form of a popups when Kmail is opened in the background. Those 
popups come randomly without user action.

I understand it would be useless to answer yes to the popup. Additionally, it 
doesn't seem legit/safe at all, for someone who doesn't have the necessary 
knowledge, to answer yes to "do you ultimately trust XXX to correctly certify 
user certificates?"

I've read the explanations/comments in the bug, but I didn't understand 
anything, sorry.

The certificate in the popup is the same as this one:

```
$ awk -v cmd='openssl x509 -noout -subject' '/BEGIN/{close(cmd)};{print | 
cmd}' < /etc/ssl/certs/ca-certificates.crt | grep 'Manchester.*AAA'
subject=C = GB, ST = Greater Manchester, L = Salford, O = Comodo CA Limited, 
CN = AAA Certificate Services
```

I've been told to try: `sudo dpkg-reconfigure ca-certificates`, but that didn't 
change anything.

It won't crash the system, but it's very very annoying/disruptive for the 
user.

Thanks,
Chris

Re: Plasma with Wayland: No ssh-agent started automatically?

[chris]

On Sunday, 19 February 2023 10:13:20 CET Martin Steigerwald wrote:
> Shmerl - 19.02.23, 04:21:16 CET:
> > I've been using KDE Wayland session for a while, but I also switched
> > to systemd boot for KDE, may be that helped with ssh-agent.

I've been using wayland for 3 years now and it's working perfectly well. It 
took me some time to have it working in the first place but it never failed me 
since. It's working at least as well as legacy x11 used to. x11 which I 
eradicated as much as I could, zotero6 is the only app I have, still using 
legacy xwayland, but I'll switch to zotero7 asap. On another, newer install, I 
ditched sddm for gdm which allows me to have no xorg server at all. Hope sddm 
0.20 will be available soon.

As for `eval "$(ssh-agent -s)"`, I can see in my bash history I start using it 
at least from 2022.

Cheers
Chris

> > 
> > Here are some details:
> > https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/
> > 
> > 
> > To enable it:
> > 
> > kwriteconfig5 --file startkderc --group General --key systemdBoot true
> > 
> > Not sure about kick-off issues, I'm using fullscreen Aplication
> > Dashboard, and it works fine.
> 
> Haha, no systemd running here.
> 
> But good tip that is could be related to the way Plasma is starting up.
> 
> > If you have some problems with Wayland session - better report bugs,
> > so they wouldn't get lost. I've reported a bunch in the past, and
> > they were fixed.
> 
> Sure. Just currently not much time for that, so much other stuff.
> 
> Best,
> 

Re: [X1 Tablet] How does it work with Plasma and Debian

[chris]

On Thursday, 22 December 2022 21:32:28 CET Martin Steigerwald wrote:
> chris - 22.12.22, 20:57:34 CET:
> > On Thursday, 22 December 2022 09:16:50 CET Martin Steigerwald wrote:
> > > I made an interesting experience regarding the current Qt
> > > transition: I updated a ThinkPad X1 Gen 1 Tablet with "apt upgrade"
> > > yesterday.
> > Did you manage to have your tablet fully functional in keyboard free
> > mode? I've experimented with an old Portege Tablet and many
> > applications couldn't be used without a keyboard or a mouse. I want
> > to use the tablet as a reader and Okular couldn't be used without
> > "mouse right click" or "keyboard control keys" which Maliit doesn't
> > (didn't) have. Example: you can go to full screen mode but you can't
> > leave it, because it would require a right click which I couldn't
> > manage neither by touch nor by stylus.
> 
> No. Already LUKS encryption password at boot requires a keyboard. AFAIR 
> I briefly researched whether that could be done with an on screen 
> keyboard, but quickly gave up on it.

Thanks for the answer, awesome. Tablets are awesome, we do so much reading on 
our phones, we should be able to do that too, with texts that are more 
involving, and require a larger screen, and with open source software and 
hardware that actually belong to us.

I think I've gone a little bit further than you in the configuration of the 
tablet, but I really wanted a keyboard free solution.

Regarding the LUKS password, I'm pretty sure there is a debian packages doing 
just that. Only it wasn't at the top of the priority queue so I didn't try it.

My priority was more about the ergonomic of the slate, that you actually could 
read, without distraction, no tinkering: for instance it is important that the 
full screen be covered by the text you are reading in order to avoid windows 
with different colors and different brightness which tend to hurt the eyes.

Too bad for the EFI battery thing and the F1 keypress. My system was pretty 
stable once started so I expected that once it would be usable it wouldn't need 
restarting too often.

I did do some bug reports at the time regarding the usability of both okular 
and maliit, and the okular bug has been accepted.

So there is hope it gets better soon.

Also I keep encouraging people to use wayland, because the more users the 
faster the bugs will get fixed; and x11 is "won't fix" so sticking to it won't 
help.

I don't use anything anymore that use x11 or even xwayland, save zotero. But 
zotero 7 is hopefully coming soon, using Firefox 102, instead of 66, and it 
will be able to comply with `MOZ_ENABLE_WAYLAND=1`. (my emacs is built from 
source with option pgtk and does not require xwayland.)

Happy Christmas,

> 
> Additionally after replacing the internal battery with a new lithium 
> polymer replacement battery and a full hardware reset the time was gone 
> and the UEFI firmware asked to hit F1 to continue. The firmware menu can 
> be used by touch, however the engineers seem to have forgotten about 
> that "no time is set" error.
> 
> I made sure I have a working attachable ThinkPad X1 tablet keyboard.
> 
> I can comfortably read PDFs on the tablet without keyboard, but for 
> special functions in Okular, I am not so sure. However there is a 
> "okular-mobile" package in Debian. So that might help.
> 
> > On the hardware side, everything was fully functional with pure
> > Wayland install. I use GDM3 instead of SDDM because the latter still
> > rely on X11/Xorg, when GDM3 can do without.
> > 
> > Touch screen and stylus (plain Wacom) fully functional.
> 
> This tablet is still an experiment at getting a fully functional tablet 
> with Linux. It is not that we have a plethora of options here.
> 
> There are several rough edges. Trackpoint on keyboard does not work 
> after boot, you need to detach and attach the keyboard once or hibernate 
> the machine.
> 
> I am using Wayland and some times the display just hung for whatever 
> reason. Thing is, that then I can not just hit the power button long 
> enough for a hard power off. That does not work on the tablet. Instead I 
> have to stick a straightened paper clip into the emergency reset role. 
> So I made sure I always have one of those with me when I am using the 
> tablet somewhere. Once I had a HID related boot time kernel oops and was 
> not able to enter the LUKS password. That also required that paper clip 
> procedure to recover from.
> 
> > But the applications were not ready to be used with tablet mode,
> > specially Maliit, imo, which is fine to insert text but doesn't do
> > keyboard shortcuts at all, which could atone for absence or right
> > click. Touchscreen

Re: [X1 Tablet] Careful with dist-upgrade in unstable at the moment

[chris]

On Thursday, 22 December 2022 09:16:50 CET Martin Steigerwald wrote:
> I made an interesting experience regarding the current Qt transition: I 
> updated a ThinkPad X1 Gen 1 Tablet with "apt upgrade" yesterday.

Did you manage to have your tablet fully functional in keyboard free mode?
I've experimented with an old Portege Tablet and many applications couldn't be 
used without a keyboard or a mouse. I want to use the tablet as a reader and 
Okular couldn't be used without "mouse right click" or "keyboard control keys" 
which Maliit doesn't (didn't) have. Example: you can go to full screen mode 
but you can't leave it, because it would require a right click which I 
couldn't manage neither by touch nor by stylus.

On the hardware side, everything was fully functional with pure Wayland 
install. I use GDM3 instead of SDDM because the latter still rely on X11/Xorg, 
when GDM3 can do without.

Touch screen and stylus (plain Wacom) fully functional.

But the applications were not ready to be used with tablet mode, specially 
Maliit, imo, which is fine to insert text but doesn't do keyboard shortcuts at 
all, which could atone for absence or right click. Touchscreen longpress-is-
rightclick is on a per application basis, so you (did) have it with Dolphin, 
but not with Okular. Same goes for stylus button configuration.

It was a few month ago so I'd be happy to hear how you solved it or if you 
stick with the physical keyboard.

Note, integrated Firefox pdf reader, and FF generally, was what was best tuned 
for pure tablet mode use, but it was both not very stable at the time, and it 
was killing my fanless "Y"-series i5.

I've tried Phosh: couldn't insert my password. Gnome: no better. Actually I 
did find some (old) extension of some Gnome keyboard that did provide control 
keys, but maybe it was not working with all applications, and also it was 
getting all Rube Goldberg, so I gave it back to the cupboard.

But I'm still interested in an open source e-reader working with plain device 
as the portege, and I don't want to use outdated technologies like X11/Xorg, 
unmaintained for years when Wayland is doing great.

Cheers,
Chris


> Ciao,
> 

Bug#1021985: sddm login screen changed to white and does not display the breeze theme any more

[Chris Nospam]

This bug was silently fixed in sddm-theme-breeze 4:5.26.0-2 .

Bug#1021985: sddm login screen changed to white and does not display the breeze theme any more

[Chris Nospam]

Control: reassign sddm-theme-breeze 4:5.25.5-1

Bug#1021985: Re. sddm login screen changed to white and does not display the breeze theme any more

[Chris Nospam]

I think I have identified the bug now. The breeze package (was upgraded, see 
above) changed the wallpaper file types from jpg to png. Now the default config 
of sddm/sddm-theme-breeze does not find it, as it wants a jpg in the file 
theme.conf .
Please fix theme.conf in package sddm-theme-breeze from

background=/usr/share/wallpapers/Next/contents/images/5120x2880.jpg

to

background=/usr/share/wallpapers/Next/contents/images/5120x2880.png

The controls, e.g., shutdown et al. are not visible as they are drawn white on 
default background white (this is a sperarate bug, if you are asking me). Maybe 
this could be more smart and detect such a border case.

Bug#1021985: sddm login screen changed to white and does not display the breeze theme any more

[Chris Nospam]

Here some entries from an sddm start in /var/log/syslog, filtered by grep sddm:

Oct 18 08:46:21 betty sddm[925]: Initializing...
Oct 18 08:46:21 betty sddm[925]: Starting...
Oct 18 08:46:21 betty sddm[925]: Logind interface found
Oct 18 08:46:21 betty sddm[925]: Adding new display on vt 7 ...
Oct 18 08:46:21 betty sddm[925]: Loading theme configuration from ""
Oct 18 08:46:21 betty sddm[925]: Display server starting...
Oct 18 08:46:21 betty sddm[925]: Adding cookie to 
"/var/run/sddm/{aa4bb32b-dbfe-438e-8bde-4348c400857f}"
Oct 18 08:46:21 betty sddm[925]: Running: /usr/bin/X -dpi 0 -auth 
/var/run/sddm/{aa4bb32b-dbfe-438e-8bde-4348c400857f} -background none -noreset 
-displayfd 17 -seat seat0 vt7
Oct 18 08:46:22 betty sddm[925]: Setting default cursor
Oct 18 08:46:22 betty sddm[925]: Running display setup script  
"/usr/share/sddm/scripts/Xsetup"
Oct 18 08:46:22 betty sddm[925]: Display server started.
Oct 18 08:46:22 betty sddm[925]: Socket server starting...
Oct 18 08:46:22 betty sddm[925]: Socket server started.
Oct 18 08:46:22 betty sddm[925]: Loading theme configuration from 
"/usr/share/sddm/themes/breeze/theme.conf"
Oct 18 08:46:22 betty sddm[925]: Greeter starting...
Oct 18 08:46:22 betty sddm-helper[1386]: [PAM] Starting...
Oct 18 08:46:22 betty sddm-helper[1386]: [PAM] Authenticating...
Oct 18 08:46:22 betty sddm-helper[1386]: [PAM] returning.
Oct 18 08:46:23 betty systemd[1388]: Cleanup lingering KCrash metadata was 
skipped because of a failed condition check 
(ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini).
Oct 18 08:46:23 betty systemd[1388]: Cleanup lingering KCrash metadata was 
skipped because of a failed condition check 
(ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini).
Oct 18 08:46:23 betty systemd[1]: Started Session 1 of User sddm.
Oct 18 08:46:23 betty sddm[925]: Greeter session started successfully
Oct 18 08:46:23 betty sddm-greeter[1408]: High-DPI autoscaling not Enabled
Oct 18 08:46:23 betty sddm-greeter[1408]: Reading from 
"/usr/share/xsessions/plasma.desktop"
Oct 18 08:46:23 betty sddm-greeter[1408]: Loading theme configuration from 
"/usr/share/sddm/themes/breeze/theme.conf"
Oct 18 08:46:23 betty sddm-greeter[1408]: Connected to the daemon.
Oct 18 08:46:23 betty sddm[925]: Message received from greeter: Connect
Oct 18 08:46:23 betty sddm-greeter[1408]: QFont::fromString: Invalid 
description '(empty)'
Oct 18 08:46:23 betty sddm-greeter[1408]: Loading 
file:///usr/share/sddm/themes/breeze/Main.qml...
Oct 18 08:46:23 betty sddm-greeter[1408]: QObject: Cannot create children for a 
parent that is in a different thread.#012(Parent is 
QGuiApplication(0x7fffced42270), parent's thread is QThread(0x55c623077060), 
current thread is QThread(0x55c62319ad10)
Oct 18 08:46:23 betty sddm-greeter[1408]: QObject: Cannot create children for a 
parent that is in a different thread.#012(Parent is 
QGuiApplication(0x7fffced42270), parent's thread is QThread(0x55c623077060), 
current thread is QThread(0x55c62319ad10)
Oct 18 08:46:23 betty sddm-greeter[1408]: QObject: Cannot create children for a 
parent that is in a different thread.#012(Parent is 
QGuiApplication(0x7fffced42270), parent's thread is QThread(0x55c623077060), 
current thread is QThread(0x55c62319ad10)
Oct 18 08:46:23 betty sddm-greeter[1408]: QObject::installEventFilter(): Cannot 
filter events for objects in a different thread.
Oct 18 08:46:23 betty dbus-daemon[674]: [system] Activating via systemd: 
service name='org.freedesktop.UPower' unit='upower.service' requested by 
':1.34' (uid=115 pid=1408 comm="/usr/bin/sddm-greeter --socket 
/tmp/sddm-:0-PRpPZo")
Oct 18 08:46:23 betty sddm-greeter[1408]: Failed to find a Kirigami platform 
plugin
Oct 18 08:46:23 betty sddm-greeter[1408]: 
file:///usr/share/sddm/themes/breeze/components/VirtualKeyboard.qml:12:1: Type 
InputPanel unavailable
Oct 18 08:46:23 betty sddm-greeter[1408]: 
qrc:/QtQuick/VirtualKeyboard/content/InputPanel.qml:127:5: Type Keyboard 
unavailable
Oct 18 08:46:23 betty sddm-greeter[1408]: 
qrc:/QtQuick/VirtualKeyboard/content/components/Keyboard.qml:38:1: module 
"QtQuick.VirtualKeyboard.Plugins" is not installed
Oct 18 08:46:23 betty sddm-greeter[1408]: 
file:///usr/share/sddm/themes/breeze/Background.qml:21:5: QML Image: Cannot 
open: file:///usr/share/wallpapers/Next/contents/images/5120x2880.jpg
Oct 18 08:46:23 betty sddm-greeter[1408]: Adding view for "HDMI-1" QRect(0,0 
1600x1200)
Oct 18 08:46:23 betty sddm-greeter[1408]: Qt Quick Layouts: Polish loop 
detected. Aborting after two iterations.
Oct 18 08:46:24 betty sddm-greeter[1408]: Message received from daemon: 
Capabilities
Oct 18 08:46:24 betty sddm-greeter[1408]: Message received from daemon: HostName

Bug#1021985: sddm login screen changed to white and does not display the breeze theme any more

[Chris Nospam]

Package: sddm
Version: 0.19.0-4
Severity: normal
X-Debbugs-Cc: chris...@gmx.de

Dear Maintainer,

immediately after upgrading my bookworm/testing installation on Monday October 
17th morning the sddm login screen shows a white background instead the breeze 
wallpaper. Further no controls different to the login prompt, i.e., shutdown, 
dropdown to choose desktop environment, etc., are displayed. The same happend 
to my bookwork kvm instance.
As far I can see there were von packages upgraded with sddm in its name, 
despite of kdm-config-sddm, see below snippet of apt's history.log.
I use the sddm-theme-breeze, which is the only one installed. It used to show 
the colored rocket the last months.
Please note, I did not change any configuration in KDE's SDDM settings app. The 
breeze theme shows up twice, but this is for many years the case (another 
bug?). Choosing the other one does not change anything.

> dpkg -l | grep sddm
ii  kde-config-sddm   4:5.26.0-1
  amd64KCM module for SDDM
ii  sddm  0.19.0-4  
  amd64modern display manager for X11
ii  sddm-theme-breeze 4:5.25.5-1
  amd64Breeze SDDM theme
> update-alternatives --display sddm-debian-theme
sddm-debian-theme - auto mode
  link best version is /usr/share/sddm/themes/breeze
  link currently points to /usr/share/sddm/themes/breeze
  link sddm-debian-theme is /usr/share/sddm/themes/debian-theme
/usr/share/sddm/themes/breeze - priority 30
> cd /usr/share/sddm/themes/
> ls -a
total 12
drwxr-xr-x 3 root root 4096 Nov 12  2020 .
drwxr-xr-x 7 root root 4096 Oct  9  2015 ..
drwxr-xr-x 4 root root 4096 Oct 17 18:49 breeze
lrwxrwxrwx 1 root root   35 Jun 25 11:59 debian-theme -> 
/etc/alternatives/sddm-debian-theme
> cd breeze/
> ls -la
total 780
drwxr-xr-x 4 root root   4096 Oct 17 18:49 .
drwxr-xr-x 3 root root   4096 Nov 12  2020 ..
-rw-r--r-- 1 root root   1391 Sep  6 14:35 Background.qml
-rw-r--r-- 1 root root   1627 Sep  6 14:35 KeyboardButton.qml
-rw-r--r-- 1 root root   5085 Sep  6 14:35 Login.qml
-rw-r--r-- 1 root root  23199 Sep  6 14:35 Main.qml
-rw-r--r-- 1 root root   1467 Sep  6 14:35 SessionButton.qml
drwxr-xr-x 4 root root   4096 Sep 25 14:36 components
-rw-r--r-- 1 root root   5681 Sep  6 14:35 default-logo.svg
drwxr-xr-x 2 root root   4096 Sep 25 14:36 faces
-rw-r--r-- 1 root root   2516 Sep  6 14:35 metadata.desktop
-rw-r--r-- 1 root root 717013 Sep  6 14:35 preview.png
-rw-r--r-- 1 root root208 Sep  9 23:22 theme.conf
> cat theme.conf
[General]
showlogo=hidden
logo=/usr/share/sddm/themes/breeze/default-logo.svg
type=image
color=#1d99f3
fontSize=10
background=/usr/share/wallpapers/Next/contents/images/5120x2880.jpg
needsFullUserModel=false
> cd usr/share/wallpapers/Next/contents/images/
> ls -la
total 31512
drwxr-xr-x 2 root root4096 Oct 17 08:36 .
drwxr-xr-x 4 root root4096 Oct 17 08:36 ..
-rw-r--r-- 1 root root  656342 Oct  6 14:07 1024x768.png
-rw-r--r-- 1 root root 1073831 Oct  6 14:07 1080x1920.png
-rw-r--r-- 1 root root  947830 Oct  6 14:07 1280x1024.png
-rw-r--r-- 1 root root  844607 Oct  6 14:07 1280x800.png
-rw-r--r-- 1 root root  876586 Oct  6 14:07 1366x768.png
-rw-r--r-- 1 root root 1011086 Oct  6 14:07 1440x900.png
-rw-r--r-- 1 root root 1270494 Oct  6 14:07 1600x1200.png
-rw-r--r-- 1 root root 1265636 Oct  6 14:07 1680x1050.png
-rw-r--r-- 1 root root 1463093 Oct  6 14:07 1920x1080.png
-rw-r--r-- 1 root root 1534398 Oct  6 14:07 1920x1200.png
-rw-r--r-- 1 root root 2245178 Oct  6 14:07 2560x1440.png
-rw-r--r-- 1 root root 2362192 Oct  6 14:07 2560x1600.png
-rw-r--r-- 1 root root 3125482 Oct  6 14:07 3200x1800.png
-rw-r--r-- 1 root root 3238221 Oct  6 14:07 3200x2000.png
-rw-r--r-- 1 root root  223019 Oct  6 14:07 360x720.png
-rw-r--r-- 1 root root 4097873 Oct  6 14:07 3840x2160.png
-rw-r--r-- 1 root root  135430 Oct  6 14:07 440x247.png
-rw-r--r-- 1 root root 5200588 Oct  6 14:07 5120x2880.png
-rw-r--r-- 1 root root  639660 Oct  6 14:07 720x1440.png
> cat /var/log/apt/history.log (shortened to that day)
root@betty:/temp# cat history.log
Start-Date: 2022-10-17  08:34:20
Commandline: apt-get dist-upgrade
Install: node-acorn:amd64 (8.8.0+ds+~cs25.17.7-1, automatic), 
polkitd-pkla:amd64 (121+compat0.1-6, automatic), node-cjs-module-lexer:amd64 
(1.2.2+dfsg-4, automatic), systemd-coredump:amd64 (251.5-2, automatic), 
node-xtend:amd64 (4.0.2-3, automatic), libduktape207:amd64 (2.7.0-1+b1, 
automatic), node-undici:amd64 (5.10.0+dfsg1+~cs18.9.18.10-2, automatic)
Upgrade: dpkg:amd64 (1.21.9, 1.21.9+b1), libkdecorations2-5v5:amd64 
(4:5.25.5-1, 4:5.26.0-1), breeze:amd64 (4:5.25.5-1, 4:5.26.0-1), 
libtext-unidecode-perl:amd64 (1.30-2, 1.30-3), librados2:amd64 
(16.2.10+ds-2+b2, 16.2.10+ds-2+b3), libnode108:amd64 (18.7.0+dfsg-5, 
18.10.0+dfsg-6), libcups2:amd64 (2.4.2-1+b1, 2.4.2-1+b2), libmailutils9:amd64 
(

Re: Wayland in current KDE

[chris]

On Monday, 4 April 2022 21:38:35 CEST Marc Haber wrote:
> On Mon, Apr 04, 2022 at 04:20:38PM +0200, chris wrote:
> > https://oftc.irclog.whitequark.org/wayland/[3])
> Do they know their way aroud KDE Plasma? I suspect that most of my
> issues are actually in KDE.

No, they don't. I just gave the information in case the issue was related to 
your GPU, or something not kde specific.
My wayland session works very well, but I don't use a 2fa-usb-key, so I 
wouldn't know. As for `ssh-agent` I always start it from command line.

Re: Wayland in current KDE

[chris]

On Sunday, 3 April 2022 17:59:44 CEST Patrick Franz wrote:
> Hi Marc,
> 
> Am Sonntag, 3. April 2022, 13:13:24 CEST schrieb Marc Haber:
> [...]
> 
> > If this should work, who needs to know about the bug?
> 
> I suggest upstream. They know much better which hardware configurations
> should work and which ones cause trouble under which circumstances.

There is a friendly and helpful irc channel on OTFC:
ircs://irc.oftc.net/#wayland[1]
(see also: https://wayland.freedesktop.org/[2])
They've helped me a lot for bug reporting in the past, and the bugs have been 
fixed since.
(There is a "whitequark" log: https://oftc.irclog.whitequark.org/wayland/[3])








[1] ircs://irc.oftc.net/#wayland
[2] https://wayland.freedesktop.org/
[3] https://oftc.irclog.whitequark.org/wayland/

Re: Digital clock widget and 24-hour format

[chris]

On Monday, 21 March 2022 02:46:11 CET local10 wrote:
> Mar 20, 2022, 18:59 by inkbottle...@gmail.com:
> > I've fixed that issue on my box about 6 month ago, I can't remember how I
> > did that exactly. The core of it however was that the `locales` were
> > defined in several places, like 2 or 3, and that one of them was
> > inconsistent with the others. And I've just deleted it.
> > 
> > 
> > 
> > Now my setting is, I have no local whatsoever, viz, I use `>
> > LC_ALL="C.UTF-8"` and that's it. Only "spell check" is "US-EN".
> I will have to look into that, I was fiddling with "LC_ALL" recently to to a
> different issue and now it is set to LC_ALL=en_US.UTF-8, LC_ALL was unset

For what I've observed, when using LC_ALL=en_US.UTF-8, it's very difficult to 
escape am/pm time format, "somewhere".

To have English language with "metric system" there is also en_dk, IIRC, which 
is friendly in that regard.

But, I really think LC_ALL="C.UTF-8", is already doing that.

> prior to that. Will report back when I try it.
> 
> Regards,

Re: Digital clock wizard and 24-hour format

[chris]

On Sunday, 20 March 2022 18:29:54 CET Shai Berger wrote:
> FWIW, my digital clock's "Time display" is set to "Use Region
> Defaults", not "24 hours", and I do get a 24 hour clock (which is what
> my region defines).

I've fixed that issue on my box about 6 month ago, I can't remember how I did 
that exactly. The core of it however was that the `locales` were defined in 
several places, like 2 or 3, and that one of them was inconsistent with the 
others. And I've just deleted it.

Now my setting is, I have no local whatsoever, viz, I use `LC_ALL="C.UTF-8"` 
and that's it. Only "spell check" is "US-EN".

Really my issue was with the screen saver time display. And there were no 
simple way to fix that. But with "consistent" locales, it really works smoothly.

And not every bits of kde software were looking in kde config for locales data, 
and there were the system wide locales, and the user's locales: that makes 
three.

Bug#1007803: plasma-pa: Could dependency on pulseaudio-module-gsettings be lessened?

[chris]

Package: plasma-pa
Version: 4:5.24.3-1
Severity: normal
X-Debbugs-Cc: inkbottle...@gmail.com

Dear Maintainer,

`plasma-pa` has `pulseaudio-module-gsettings` in its recommend dependencies and 
it is conflicting with `pipewire` / `wireplumber`, because it causes the 
installation of `pulseaudio`.

At the moment I don't have `pulseaudio-module-gsettings` installed, since it's 
only a recommend dependency, I'm not compelled to install it.

I've initially put that issue on `pulseaudio-module-gsettings` package, but the 
maintainer of this package said nothing could be fixed from his side. They also 
said that installing `pulseaudio` was not conflicting "per se" with `pipewire`. 
And I want to believe them. I think it does make more complicated to have 
`pipewire` working.


What you really want is the reverse dependencies (either
plasma-pa or paprefs) to not require gsettings, or get pipewire to
implement module-gsettings (and then add the alternative to each package).
See https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1066 and
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/771


Thanks,
Chris

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

Kernel: Linux 5.16.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-pa depends on:
ii  libc62.33-7
ii  libcanberra0 0.30-8
ii  libglib2.0-0 2.70.4-1
ii  libkf5coreaddons55.90.0-1
ii  libkf5globalaccel-bin5.90.0-1
ii  libkf5globalaccel5   5.90.0-1
ii  libkf5i18n5  5.90.0-1
ii  libkf5notifications5 5.90.0-1
ii  libkf5quickaddons5   5.90.0-1
ii  libpulse-mainloop-glib0  15.0+dfsg1-4
ii  libpulse015.0+dfsg1-4
ii  libqt5core5a 5.15.2+dfsg-15
ii  libqt5dbus5  5.15.2+dfsg-15
ii  libqt5gui5   5.15.2+dfsg-15
ii  libqt5qml5   5.15.2+dfsg-10
ii  libqt5quick5 5.15.2+dfsg-10
ii  libqt5widgets5   5.15.2+dfsg-15
ii  libstdc++6   12-20220313-1
ii  perl 5.34.0-3
ii  pipewire-pulse   0.3.48-1
ii  plasma-framework 5.90.0-2
ii  qml-module-org-kde-draganddrop   5.90.0-1
ii  qml-module-org-kde-kquickcontrolsaddons  5.90.0-1
ii  qml-module-qtquick-controls  5.15.2-2
ii  qml-module-qtquick-layouts   5.15.2+dfsg-10
ii  qml-module-qtquick2  5.15.2+dfsg-10

Versions of packages plasma-pa recommends:
ii  libcanberra-pulse0.30-8
pn  pulseaudio-module-gsettings  
ii  qml-module-gsettings1.0  0.2-4
ii  sound-theme-freedesktop  0.8-2

plasma-pa suggests no packages.

-- no debconf information

Re: Wayland in current KDE

[chris]

On Sunday, 6 March 2022 10:20:22 CET tv.debian wrote:
> Le 06/03/2022 à 04:19, chris a écrit :
> > Just a small related comment, with upgrade to 5.24 from a week or so ago,
> > the panel, wallpapers, etc switched between laptop monitor and external
> > monitor. Beside that I've noticed that there now is the possibility to
> > select a "primary" monitor in Setting/Wayland, which I think wasn't
> > possible before. Anyway, no big deal. But the primary monitor thing could
> > mean no more monitor swapping in the future. At the moment, the external
> > 4K monitor has been selected as primary: I don't know what would be the
> > behavior were I to unplug it.
> > 
> > On Saturday, 19 February 2022 19:49:23 CET Leonid.  wrote:
> >> 18.02.2022, 20:00, "Luc Castermans" :
> >> well...
> >> - on a laptop with integrated graphics controller it works :=)
> >> - on a desktop with separate NVDIA card it doesn't even start (!)
> >> 
> >> I suppose problem isn't in X-server, I think problem in user :)
> >> You should try start "ready to start" distribution for test Xorg, if you
> >> aren't sure in your configuration. For example... live-cd ubuntu image.
> 
> Same experience here, the external TV had the desktop attributes (bar,
> plasmoïdes...), but manually selecting the laptop screen got things back
> in order. After plugin/unplugin the secondary screen the marked primary
> screen stays stable.

In my case the attribution of screens is the other way around, the external 
monitor, has been automatically afaik, assigned as primary.
It seems legit since I never use the laptop screen. Laptop monitor is TN 
1366x768, external monitor is 4K, IPS.
In any case I won't try high risk experiment consisting in unplugging external 
monitor, or changing primary attribute.
The prospect of having to spend hours to fix it is way too scary.

> On several machines the shortcut that binds the app menu (using the full
> screen app launcher) to the "Windows" key was unbinded. Setting it to
> something random, then back to "alt+F1" did the trick. Minor stuff,
> otherwise good experience so far.

My keyboard must be very very old because it doesn't have a windows key, viz 
no meta key neither. I do and have done Alt + F1 from day one. I've assigned 
Alt+F11 to overview.

Generally Kwin/Wayland experience is the most awesome.

Re: Wayland in current KDE

[chris]

Just a small related comment, with upgrade to 5.24 from a week or so ago, the 
panel, wallpapers, etc switched between laptop monitor and external monitor. 
Beside that I've noticed that there now is the possibility to select a 
"primary" monitor in Setting/Wayland, which I think wasn't possible before. 
Anyway, no big deal. But the primary monitor thing could mean no more monitor 
swapping in the future. At the moment, the external 4K monitor has been 
selected as primary: I don't know what would be the behavior were I to unplug 
it.

On Saturday, 19 February 2022 19:49:23 CET Leonid.  wrote:
>  
>  
> 18.02.2022, 20:00, "Luc Castermans" :
> well...
> - on a laptop with integrated graphics controller it works :=)
> - on a desktop with separate NVDIA card it doesn't even start (!)
>  
> I suppose problem isn't in X-server, I think problem in user :)
> You should try start "ready to start" distribution for test Xorg, if you
> aren't sure in your configuration. For example... live-cd ubuntu image.
> -- 
>  

Re: Wayland in current KDE

[chris]

On Wednesday, 16 February 2022 09:40:25 CET Libor Klepáč wrote:
> On Út, 2022-02-01 at 20:09 +0100, chris wrote:
> 
> > On Monday, 31 January 2022 11:10:35 CET Marc Haber wrote:
> > 
> > > Hi,
> > > 
> > > I tried Wayland recently. Looked ok, but was hardly usable. The
> > > Panels
> > > show, but don't accept any mouse clicks (neither left nor right).
> > > "Leave" in the desktop's right-click menu didn't work either, had
> > > to
> > > Ctrl-Alt-Backspace myself out of the session.
> > > 
> > > Is this the expected beavior of a KDE Wayland session in current
> > > Debian
> > > unstable? If not, which package deserves the bug report?
> > 
> > 
> > Here on old lenovo laptop with intel integrated gpu and external 4k
> > monitor .
> > The experience is, all in all, way better than what it was with X11.
> > Chris
> 
> 
> Hi,
> how did you deal with screen layout changes when disconnecting laptop
> from external monitor?
> I mean - on xwindows, when i connect my laptop to dock, my primary
> screen moves to external monitor, when i disconnect it moves back.

Hum, my x230 is an old one with 1366x768 screen. With x11, when I was plugin 
the external monitor, it was very very bumpy.

Until you tell me, I didn't know you could unplug external monitor without 
having to reinstall the system altogether. I mean, I'm glad to hear that you 
can do that without too much struggle.

> 
> With wayland, all panels and windows stayed on laptop screen, when I
> plugged laptop to dock.

Yes, I think the primary screen feature is still missing on Wayland. Not long 
ago, after some system upgrade, builtin and external monitor, widget and all, 
swapped. At that time I didn't find a way to put that straight back, so I 
reconfigured the "look" from scratch. But at least the screen resolution was 
detected correctly.

Wayland is a work in progress. For what I've understood, x11 is no longer a 
work in progress. So I thought, if you have an issue with the compositor, 
switch to Wayland, and open an issue.

> 
> I wanted to try wayland, because my browsers (edge, chromium) sometimes
> does this
> https://www.youtube.com/watch?v=WRIkewXZga4
> 
> and i think it's xwindows related
> 
> Libor
> 
> 
> > 
> > 
> > > 
> > > Greetings
> > > Marc
> > 
> > 
> > 
> > 
> > 

Re: Wayland in current KDE

[chris]

On Monday, 31 January 2022 11:10:35 CET Marc Haber wrote:
> Hi,
> 
> I tried Wayland recently. Looked ok, but was hardly usable. The Panels
> show, but don't accept any mouse clicks (neither left nor right).
> "Leave" in the desktop's right-click menu didn't work either, had to
> Ctrl-Alt-Backspace myself out of the session.
> 
> Is this the expected beavior of a KDE Wayland session in current Debian
> unstable? If not, which package deserves the bug report?

Here on old lenovo laptop with intel integrated gpu and external 4k monitor .
The experience is, all in all, way better than what it was with X11.
Chris

> 
> Greetings
> Marc

Bluetooth headset "protocol not available". (Bug#998220)

[chris]

I was about to comment on Bug#998220, but I changed my mind.

I do have `pipewire` installed. For one thing `libpipewire` is in the 
dependencies of `kwin-
wayland`, so it's a requirement on my system.

After last upgrade (sid) a couple of days ago, bluetooth headset were refusing 
to connect, 
"Protocol not available". But they were willing to connect if I was before 
doing: (after each 
reboot)

`systemctl --user restart pulseaudio.service`

Then I decided to do some searches, and here is what came from it.
I'm putting it here because it's not sure at all that every bit of what I did 
was really 
necessary. Specifically, were the libraries `libspa-0.2-bluetooth` and 
`pipewire-audio-
client-libraries` really needed. Or even just `libspa-0.2-bluetooth`.

===


I do initially, have the following issue:


`otherwise device connections will fail with "Protocol not available".` 
(https://
wiki.debian.org/PipeWire) 

Here is an edited version of how I fixed it on #debian-next:

===

Giving the ubuntu tuto a try now 
(https://askubuntu.com/questions/1339765/replacing-pulseaudio-with-pipewire-in-ubuntu-20-04)
 

`sudo aptitude install libspa-0.2-bluetooth pipewire-audio-client-libraries` 

`systemctl --user daemon-reload` (as plain user, other terminal) 
`systemctl --user --now disable pulseaudio.service pulseaudio.socket` 

`systemctl --user mask pulseaudio` 
=> `Created symlink /home/chris/.config/systemd/user/pulseaudio.service → 
/dev/null.` 

`systemctl --user --now enable pipewire-media-session.service` 
=> `Failed to enable unit: Unit file 
/etc/xdg/systemd/user/pipewire-media-session.service is 
masked.`

Here I'm suggested to use the two pivotal following lines:

`sudo aptitude purge pipewire-media-session` 

`sudo aptitude reinstall wireplumber` 
=> "Created symlink /etc/systemd/user/pipewire-session-manager.service → 
/usr/lib/
systemd/user/wireplumber.service." 

I still have "device connections will fail with "Protocol not available"." 

`systemctl --user restart pipewire` 

There it is. 

Bottom line: 
I did not follow https://wiki.debian.org/PipeWire which contains things not 
possible to do. 
I followed 
https://askubuntu.com/questions/1339765/replacing-pulseaudio-with-pipewire-in-ubuntu-20-04
 
With `pipewire-media-session` replaced by `wireplumber`. 
I did do `apt purge --autoremove pipewire-media-session` and then `apt install 
--reinstall 
wireplumber` 
And `systemctl --user restart pipewire` 

I didn't do: `touch /etc/pipewire/media-session.d/with-pulseaudio`, nor did I 
do: `cp /usr/
share/doc/pipewire/examples/systemd/user/pipewire-pulse.* /etc/systemd/user/` 
(from 
https://wiki.debian.org/PipeWire) 

The line: "Install pipewire-pulse (which replaces pulseaudio and 
pulseaudio-bluetooth)" 
from https://wiki.archlinux.org/title/bluetooth_headset suggests that the two 
latter 
packages should be removed (not sure about that, just saying) 

I rebooted to see if it'd be still working: it auto connected very very 
quickly. And audio is 
working.

===

Packages: https://packages.debian.org/sid/libspa-0.2-bluetooth[1] and https://
packages.debian.org/sid/pipewire-audio-client-libraries[2] are saying that they 
are 
"experimental".

That could explain why they are not in the dependencies.

But they seem to work.

Bug#996670: Bug #998386 Plasma gets very slow when compositor is disabled on bare metal

[Chris Nospam]

Hi Norbert,

> But I guess you had, or some cosmic radiation induced bit switch did it
> for you on your hard disk ;-) The default for all installations is being
> on.

yeah, then lets say "maybe" or "probably" I did that, nevertheless, at least it 
was a couple of years ago and I cannot remeber ;-)

> > In my similar kvm virtualized installtion the switch also is/was off,
> > but there it seems to make no problems, even after a couple of changes and 
> > restartings.
>
> Hmm, that is indeed strange, though.
>
> I suggest that *you* create a bug report at upstream (I guess kwin?)
> because I cannot reproduce it on my systems (AMD based), and upstream
> devs will need detailed informations.

Ok, just did that now as suggested, see 
https://bugs.kde.org/show_bug.cgi?id=444940

Best,
Chris

Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma

[Chris Nospam]

Hi Norbert,

thanks to your repsonse!

> Can you try/check the following:
> * In the Plasma Settings app, go to
>   Display and Monitor > Compositor
>   and check whether
>   Enable compositor on startup
>   is selected (on).

Indeed, turning that switch to on and restarting helps. Great!!! I cannot 
remeber that I ever turned it on or off. However, if I turn it back to off, 
then the problems come back (immedeiately). So at least the latter seems to be 
a bug, right? (Personally I would not need any 3d effects).

In my similar kvm virtualized installtion the switch also is/was off, but there 
it seems to make no problems, even after a couple of changes and restartings.

>   Also the rendering backend etc is an important information.

Same on bare metal and in vm:

skaling method: exact
redering backend: OpenGL 3.1
latency: Balance of latency and smoothness
tearing: automatic
holding available window preview images:  only for visible windows
allow applications to block compositing: enabled

> If the above (after logout/login, or better reboot) does not help:
> * Is the behaviour reproducible with a **clean** **new** user?

Yes, as turning on Enable compositor on startup immediately helped, I did not 
try that.

Chris

Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma

[Chris Nospam]

Today all packages of plasma 5.23 migrated to testing, and it works fine in my 
(libvirt) vm. However, on bare metal mesa makes problems (see my bug report 
#998386), so in fact there plasma 5.23 stays unusable.

Re: KDE/Plasma/Wayland v5.23 and SDDM delay on reboot/restart

[chris]

On Sunday, 31 October 2021 02:52:15 CET Sedat Dilek wrote:
> So, the easiest way to workaround the 90 secs delay for me is to stop
> SDDM before reboot/shutdown from a VT different than
> KDE/Plasma/Wayland:

I logout before reboot/shutdown: no 90 s delay.


> 
> ( Change to VT #2 )
> root# systemctl stop sddm.service
> root# sync && sync && sync
> root# systemctl reboot
> 
> - Sedat -
> 
> On Sun, Oct 17, 2021 at 8:44 AM Sedat Dilek  wrote:
> > On Sat, Oct 16, 2021 at 9:40 AM Sedat Dilek  wrote:
> > > Hi,
> > > 
> > > I switched to KDE/Plasma v5.23 from Debian/unstable - mostly as
> > > middle-mouse-paste is now supported.
> > > 
> > > On reboot and restart I get a 90 seconds delay when SDDM service is
> > > shutdown.
> > > 
> > > Debian ships SDDM version 0.19 and upcoming 0.20 shall have Wayland
> > > support (see [1]).
> > > 
> > > Is there a workaround I do not know?
> > > 
> > > I might change DefaultTimeoutStopSec:
> > > 
> > > root# grep DefaultTimeout /etc/systemd/system.conf
> > > 44:#DefaultTimeoutStartSec=90s
> > > 45:#DefaultTimeoutStopSec=90s
> > > 46:#DefaultTimeoutAbortSec=
> > > 
> > > Alternatively, use a different GUI login-manager which supports
> > > Wayland properly?
> > > 
> > > Thanks in advance.
> > > 
> > > Regards,
> > > - Sedat -
> > > 
> > > 
> > > 
> > > [1] https://wiki.archlinux.org/title/SDDM
> > 
> > [ Please CC me explicitly as I am NOT subscribed to this ML, Thanks. ]
> > 
> > > Hi,
> > > 
> > > Does uninstalling kdeconnect, if it is installed, remove the delay?
> > > 
> > > Regards,
> > > David
> > 
> > Hi.
> > 
> > No.
> > First, I tried with a `killall kdeconnectd` and afterwards with
> > uninstalling kdeconnect.
> > Both did not help.
> > 
> > To confirm that this is an issue with *** KDE/Plasma + Wayland ***...
> > I logged into a *** KDE/Plasma + X11 *** session and then rebooted.
> > There was no 90 seconds delay.
> > 
> > So, this is an issue with SDDM and KDE/Plasma + Wayland.
> > 
> > As said in my initial posting SDDM version 20 shall have (better)
> > Wayland support.
> > 
> > Currently, I am interested in a workaround.
> > It is annoying to wait 90 seconds when doing reboots (or shutdown).
> > 
> > Thanks.
> > 
> > Regards,
> > - Sedat -

Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma

[Chris Nospam]

KDE/Plasma (package dependencies) are currently completely broken under 
testing. Is there currently a chance to (somehow simply) block the partial 
transition of plasma 5.23 to testing (so that not related package updates are 
easy)? Selectively upgrading single packages with dependencies one after the 
other from the mass provided in testing is rather cumbersome.

Currently I get the following (sorry for the german locale):

root@xxx:~# apt-get dist-upgrade
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
Die folgenden NEUEN Pakete werden installiert:
  libkdecorations2private9
Die folgenden Pakete werden aktualisiert (Upgrade):
  bluedevil breeze breeze-cursor-theme breeze-gtk-theme drkonqi
  kactivitymanagerd kde-config-gtk-style kde-config-sddm kde-config-updates
  kde-style-breeze kgamma5 kinfocenter kmenuedit kscreen ksshaskpass
  kwayland-integration kwin-style-breeze kwrited libkdecorations2-5v5
  libkf5screen-bin libkf5screen7 libpam-kwallet-common libpam-kwallet5 milou
  oxygen-sounds plasma-discover plasma-discover-common plasma-disks
  plasma-integration plasma-pa polkit-kde-agent-1
31 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 96,2 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 47,1 MB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n] n
Abbruch.

All packages shown above are from version 4:5.23.0 whereas the others would 
stay on 4:5.21.x. Unfortunately, it is not sufficient to set 
libkdecorations2-5v5 on hold, as it would remove plasma-desktop:

root@xxx:~# apt-mark hold libkdecorations2-5v5
libkdecorations2-5v5 auf Halten gesetzt.
root@xxx:~# apt-get dist-upgrade
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
  accountsservice apt-config-icons-hidpi apt-config-icons-large
  apt-config-icons-large-hidpi bluedevil bluez bluez-obexd breeze-gtk-theme
  bup bup-doc gtk2-engines-pixbuf ibus-data ieee-data kde-config-gtk-style
  kde-config-sddm kde-config-updates kgamma5 khotkeys khotkeys-data
  kinfocenter kmenuedit kscreen kup-backup kwrited libaccountsservice0
  libibus-1.0-5 libkpmcore11 libqt5designer5 libqt5help5 libscim8v5
  libxcb-record0 oxygen-sounds par2 partitionmanager plasma-desktop-data
  plasma-discover plasma-discover-common plasma-disks python3-fuse
  python3-pylibacl python3-pyqt5 python3-pyqt5.sip python3-pyxattr
  python3-software-properties python3-tornado qml-module-org-kde-activities
  qml-module-org-kde-kcm qml-module-org-kde-kitemmodels smartmontools
  software-properties-common software-properties-kde systemsettings
  xsettings-kde
Verwenden Sie »apt autoremove«, um sie zu entfernen.
Die folgenden Pakete werden ENTFERNT:
  kde-plasma-desktop plasma-desktop
Die folgenden Pakete sind zurückgehalten worden:
  breeze breeze-cursor-theme kde-config-gtk-style kde-style-breeze
  kwin-style-breeze libkdecorations2-5v5 plasma-integration
Die folgenden Pakete werden aktualisiert (Upgrade):
  bluedevil breeze-gtk-theme drkonqi kactivitymanagerd kde-config-sddm
  kde-config-updates kgamma5 kinfocenter kmenuedit kscreen ksshaskpass
  kwayland-integration kwrited libkf5screen-bin libkf5screen7
  libpam-kwallet-common libpam-kwallet5 milou oxygen-sounds plasma-discover
  plasma-discover-common plasma-disks plasma-pa polkit-kde-agent-1
24 aktualisiert, 0 neu installiert, 2 zu entfernen und 7 nicht aktualisiert.
Es müssen 14,9 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 14,9 MB Plattenplatz freigegeben.
Möchten Sie fortfahren? [J/n] n
Abbruch.

When will it be save to switch to 5.23 in testing, or what could be the 
indicator to do that? When kwin 5.23 will be available in the testing repos? Or 
would you be so kind to post a corresponding message, e.g., here?

Tanks,
Chris

Re: Broken KDE in Sid/Unstable

[chris]

On Sunday, 19 September 2021 16:19:09 CEST bruno zanetti wrote:
> Hi Miguel,
> 
> I assume you are on sid/testing and you did a dist-upgrade (or
> full-upgrade).
> This morning I tried to dist-upgrade sid but I eventually gave up since apt
> asked to remove plasma-desktop and other stuff I didn't think it was good
> to remove.

There is a small difficulty around `libqalculate22`, with `dist-upgrade`. And 
you might have to manually fix it. (It was the 16th, and `dist-upgrade` was 
removing a large part of kde).

I did:
`aptitude full-upgrade libqalculate20-`
and then:
`aptitude full-upgrade`

On `#debian-next`, someone did suggest:
`apt full-upgrade task-kde-desktop plasma-workspace kwin-x11`

(I use wayland, not sure it would have worked).


> Look at the logfiles in /var/log/apt and see if something got removed along
> with the upgrade.
> Just guessing.
> 
> Best
> 
> bz
> 
> 
> 
> Il giorno dom 19 set 2021 alle ore 14:28 Miguel A. Vallejo
> 
> ha scritto:
> > Hi!
> > 
> > This morning an apt update broke my kde. I can log in, but only to get
> > into a black screen with the mouse's cursor, even using a newly created
> > user.
> > 
> > I can't see any obvious error in syslog, but there is something in
> > .xsession-errors :
> > 
> > Kapplymousetheme ("breeze_cursors","24") exited with user code 255
> > 
> > And some lines below a lot of unrecognized keysims from kwin_xkbcommon, a
> > NULL argument for networkIdsList, a failed to parse kaccess.desktop, many
> > other errors ( sorry, I'm typing on phone) until a broken connection to
> > the
> > X11 server brings back the login screen.
> > 
> > Any ideas?
> > 
> > Thanks in advance.

Bug#981515: kcoreaddons: please replace fam with gamin

[Chris Hofstaedtler]

Hi Pino,

given we are now in the bookworm cycle - do you think kcoreaddons
could remove fam (or replace it with gamin if really needed)?

Do you want a wider audience informed of the change, or would the
change in kcoreaddons be self-contained enough?

Thanks,
Chris

Bug#990348: qtwayland-opensource-src: Accented and dead keys do not work.

[chris]

Source: qtwayland-opensource-src
Version: 5.15.2-2
Severity: normal
X-Debbugs-Cc: inkbottle...@gmail.com

Dear Maintainer,

There is a known bug with upstream fix, related to altgr-intl deadkey not 
working in
kde-app with kde-plasma-wayland session.

I understand there are workarounds, but the recommended way of fixing it would 
be to used
the patched qt.

Here the link to the patch:
https://codereview.qt-project.org/c/qt/qtwayland/+/338196

Here two bugs closed thank to this patch:
https://bugs.kde.org/show_bug.cgi?id=411729
https://bugs.kde.org/show_bug.cgi?id=405388

If you're trying to reproduce the bug, note that altgr-intl deadkey umlaut "o" 
cannot by
typed in konsole or konversation, but can be in firefox or emacs.

My system is "unstable" for the main part, and "experimental" for everything 
"qt-kde"
related. But I think it has no bearing on this issue.


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

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#983046: kjs: please make the opcodes.h file reproducible

[Chris Lamb]

Hi Norbert,

> Do you want that this is also included into unstable and uploaded now
> during the freeze, or is post-release fine?

Post-release would be totally fine… but I suppose if you do end up
uploading kjs for some other issue, it would be nice to include it.

(Not sure what the current Release Manager policy is regarding
including these kinds of fixes in unblock requests, mind you.)


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#983046: kjs: please make the opcodes.h file reproducible

[Chris Lamb]

Source: kjs
Version: 5.78.0-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
kjs could not be built reproducibly.

This is, in part, because it generates an opcodes.h file that embeds the
full path to its original filename which naturally varies on the original
build directory.

Patch attached that applies the equivalent of basename(3) to these values;
kjs doesn't use boost so I cannot use boost::filesystem, nor does it use
c++17 (?) so I cannot use std::filesystem::path either, alas.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible_build 1970-01-01 01:00:00.0 +0100
--- b/debian/patches/reproducible_build 2021-02-18 14:52:49.165246604 +
@@ -0,0 +1,49 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2021-02-18
+
+--- kjs-5.78.0.orig/src/kjs/bytecode/generator/filetemplate.h
 kjs-5.78.0/src/kjs/bytecode/generator/filetemplate.h
+@@ -46,6 +46,7 @@ struct FileTemplate {
+ {
+ isOK  = true;
+ lines = 0;
++  inFileBaseName = inFileName.substr(inFileName.find_last_of("/") + 1);
+ 
+ in.open(inFileName.c_str());
+ if (in.fail()) {
+@@ -60,7 +61,7 @@ struct FileTemplate {
+ }
+ 
+ if (isOK) {
+-out << "// WARNING: Portions of this file are autogenerated from 
codes.def and " << inFileName << ".\n";
++out << "// WARNING: Portions of this file are autogenerated from 
codes.def and " << inFileBaseName << ".\n";
+ out << "// (which is what the licensing terms apply to)\n";
+ out << "// Any changes you make here may be lost!\n";
+ handleUntilGenerate();
+@@ -77,7 +78,7 @@ struct FileTemplate {
+ // Goes until @generate..
+ void handleUntilGenerate()
+ {
+-out << "#line " << (lines + 1) << " \"" << inFileName << "\"\n";
++out << "#line " << (lines + 1) << " \"" << inFileBaseName << "\"\n";
+ while (!in.eof()) {
+ string line;
+ getline(in, line);
+@@ -92,7 +93,7 @@ struct FileTemplate {
+ 
+ void handleSuffix()
+ {
+-out << "#line " << (lines + 1) << " \"" << inFileName << "\"\n";
++out << "#line " << (lines + 1) << " \"" << inFileBaseName << "\"\n";
+ while (!in.eof()) {
+ string line;
+ getline(in, line);
+@@ -101,6 +102,7 @@ struct FileTemplate {
+ }
+ 
+ string   inFileName;
++string   inFileBaseName;
+ string   outFileName;
+ ifstream in;
+ ofstream out;
--- a/debian/patches/series 2021-02-18 12:56:03.551163060 +
--- b/debian/patches/series 2021-02-18 13:00:06.669560158 +
@@ -1 +1,2 @@
 install_missing_headers
+reproducible_build

Bug#982221: k3b: please stop using cdrkit

[Chris Hofstaedtler]

Package: k3b
Version: 20.12.2-1
Severity: important

Dear k3b Maintainers,

your package depends on wodim and genisoimage, both built from
cdrkit sources. cdrkit does not have a path forward, please switch
away from it rather soon. I'm told xorriso and libburnia are
alternatives and are alive and doing well.

It's been suggested cdrkit should not be in bookworm.

Chris

Bug#981515: kcoreaddons: please replace fam with gamin

[Chris Hofstaedtler]

* Pino Toscano  [210201 00:28]:
> In data lunedì 1 febbraio 2021 00:00:47 CET, Chris Hofstaedtler ha scritto:
> I wouldn't say that gamin is more maintained than FAM:
> - on the upstream side (gnome.org), it was moved the "Archive" section
>   of the gnome gitlab
> - during the migration to gitlab, all the bugzilla tickets were closed
>   instead of migrated too, because the project is archived
> - on the Debian side, gamin saw 4 uploads (one of them is an NMU) in
>   the last 10 years

This is certainly true, but its better to ship one unmaintained
thing than two.

> - #510368 prevents to switch from FAM to gamin, as it will build against
>   libgamin but still pulling libfam (or keep an old libfam as valid
>   package satisfying the dependency)

It will keep an old libfam as valid, yes. Maybe we can get that
fixed though.
 
> > Severity of this bug will probably raise over time.
> 
> What is "over time" implying, please? I really hope this is not for
> bullseye: we are so close to its freeze, and these FAM/gamin bits do
> not get much of use these days, so the risk of release regressions seems
> medium/high to me.

Not for bullseye, at least not if you don't feel like it.

But now I have to ask: why not drop the fam/gamin dependency, if it
"does not get much of use these days"? For bookworm, that is.

Chris

Bug#981515: kcoreaddons: please replace fam with gamin

[Chris Hofstaedtler]

Source: kcoreaddons
Version: 5.54.0-1

Dear Maintainer,

your package currently Depends on libfam0 (fam), which has
been requested to be removed in #966273. Please switch to gamin
instead. You can find more info, and an analysis of what probably
needs to be done for your package in this message from Glenn Strauss:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966273#15

Severity of this bug will probably raise over time.

Thanks,
Chris

Re: #966414: After upgrade to testing, VT1 is no longer usuable

[Chris Hofstaedtler]

Control: reassign -1 sddm

Per description this sounds like an ssdm issue, or at least
something the sddm maintainers could help diagnosing.

Chris

Bug#961731: sddm: Please remove Recommends: haveged

[Chris Hofstaedtler]

Package: sddm
Version: 0.18.1-1
Severity: wishlist

Dear Maintainer,

your package currently Recommends: haveged. On modern kernels, so
whatever will ship in bulleye, the kernel will provide enough entropy,
so there should be no need for haveged, except in exceptional
situations.

Please remove the Recommends: haveged.

Thanks,
Chris

Bug#944971: qtwebengine-opensource-src: the stack is executable, and forced upon linked programs

[Chris Wellons]

Source: qtwebengine-opensource-src
Severity: normal

The libQt5WebEngineCore.so shared object requests an executable stack
from the loader. You can see this using "readelf -l" and inspecting the
GNU_STACK program header. All programs linked against this library also
get an executable stack whether or not they need or want it. Affected
programs include several that parse hostile input from the internet,
such as KMail, Akregator, qutebrowser, and Akonadi. Other Qt and KDE
applications are also affected.

You can see the executable stack in affected programs by looking in
their /proc/PID/maps while they're running.

This isn't a security vulnerability in itself, but an executable stack
makes vulnerabilities in all these applications much easier to exploit.
Fortunately there's no need for an executable stack in QtWebEngine. It
only arises due to a compilation misconfiguration: A handful of object
files fail to use .note.GNU-stack to opt out an executable stack.

https://www.airs.com/blog/archives/518

I've attached a list of the offending object files. Each is an assembly
file, and all but one belong to BoringSSL. Either each of these each
need to be assembled with an empty .note.GNU-stack section, or the "-z
noexecstack" option needs to be supplied at link time.
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/aes128gcmsiv-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/chacha-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/x25519-asm-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/x86_64-mont5.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/sha256-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/x86_64-mont.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/vpaes-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/sha1-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/rdrand-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/sha512-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/p256-x86_64-asm.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/md5-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/rsaz-avx2.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/ghash-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/aesni-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/bsaes-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/aesni-gcm-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/aes-x86_64.o
./src/core/release/host/obj/third_party/boringssl/boringssl_asm/chacha20_poly1305_x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/x25519-asm-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/x86_64-mont5.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/vpaes-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/sha1-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/x86_64-mont.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/sha512-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/rdrand-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/sha256-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/p256-x86_64-asm.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/aesni-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/rsaz-avx2.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/md5-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/bsaes-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/ghash-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/aesni-gcm-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/aes-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/chacha20_poly1305_x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/chacha-x86_64.o
./src/core/release/obj/third_party/boringssl/boringssl_asm/aes128gcmsiv-x86_64.o
./src/core/release/obj/third_party/WebKit/Source/platform/heap/asm/asm/SaveRegisters_x86.o

Re: qtdatavis3d-everywhere-src_5.10.1-1_amd64.changes is NEW

[Chris Lamb]

Dear Pino et al.

> OK for the "please be patient" bit, but 6 months with no feedback
> whatsoever seem excessive to me.

It's nothing to do with how many source files it is, it's just a
big queue and not even enough time to onboard new people... Sorry
it took so long to process but I've processed it now.

Needless to say, the "please be patient" bit is some machine-
generated boilerplate and not to be taken personally or even
literally.


Regards,

-- 
      ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

latte-dock_0.7.4-1_amd64.changes REJECTED

[Chris Lamb]

(forwarding reject notes)

REJECT

* applets/* is GPL3+
* po/ca/* and others are LGPL 2.1 or 3, without generic or later clause
* some attributions missing

* software looks interesting 



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.

Bug#894476: rcc: please honour SOURCE_DATE_EPOCH

[Chris Lamb]

Thorsten,

> > far easier and clearer IMHO to statelessly state that clamping is not
> > required when using SOURCE_DATE_EPOCH. :)
> 
> OK, now I do not understand _that_…

(It's clearer to say "X is the situation" vs "when you said Y before
that was correct/incorrect")


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
     `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#894476: rcc: please honour SOURCE_DATE_EPOCH

[Chris Lamb]

Hi Thorsten,

> > It is not required.
> 
> I’m parsing this as “you were not incorrect”, right?

It doesn't really matter whether you were correct or incorrect in the
past and seems a little silly to debate that; far easier and clearer
IMHO to statelessly state that clamping is not required when using
SOURCE_DATE_EPOCH. :)

> > I've found that having a shared vocabulary is very useful so just in
> > case it helps we tend to use the term "clamping" when referring to
> 
> True… it’s just that I didn’t recall the word, as “clamping”
> is not something normally part of my English vocabulary […]

I might agree it's esoteric word/usage, but not only is it already "out
there", we have more problems with "reproducible" to worry about this
one too much alas.

> I’ll try to remember next time.

Again, no question of blame or apologies here… :)


Regards,

-- 
  ,''`.
     : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#894476: rcc: please honour SOURCE_DATE_EPOCH (was Re: RCC: provide option to encode EPOCH timestamp)

[Chris Lamb]

Hi Thorsten,

> AIUI, S_D_E is used as a *delimiter*, not as a timestamp *all* files
> are to be set to.

I've found that having a shared vocabulary is very useful so just in
case it helps we tend to use the term "clamping" when referring to
this MIN(a,b) concept rather than "delimiter" or similar.  eg. "foo
clamps the mtimes to SOURCE_DATE_EPOCH".

> Chris/H01ger, please correct me if I’m wrong, but this is
> how I understood S_D_E to work.

It is not required. Does the canonical specification not explain?

  https://reproducible-builds.org/specs/source-date-epoch/
  
I pedantically refer you to that /only/ because if it is not clear
enough then there is a need to revise it. :)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Re: kbackup_18.04.0-1_amd64.changes REJECTED

[Chris Lamb]

Hi Pino,

> It'd be *so* much more useful if, instead of rejecting a package just
> because of this, it'd be accepted with a RC bug for the issue.

Not quite sure why I've been added to the CC here. :)

I don't have anything deep — or even useful! -- to add here except
that when I am processing NEW I tend to weigh the decision to
outright REJECT versus ACCEPT-with-RC-bug a little differently
depending on whether the source package is entirely new.

Whether that justifies this particular case is a different question
that I will leave to Thorsten. :)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#894476: RCC: provide option to encode EPOCH timestamp

[Chris Lamb]

Hi Thomas,

> Maybe the solution is then not in rcc but in whatever generate the files 
> that the qrc that rcc processes refer to. For instance in the case of 
> ultracopier lrelease could have a mean if generating .qm files with the 
> same modified timestamp as the .ts file it processes

That sounds workable..


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#894476: RCC: provide option to encode EPOCH timestamp

[Chris Lamb]

Hi Sune,

> "normal circumstances" is rcc on a source file, as opposed
> to an autogenerated file

I'm not /entirely/ sure what the difference is as I'm not in the
Qt/RCC world too often these days (alas !), but why just not use
SOURCE_DATE_EPOCH *iff* it is exported?

Normal systems simply do not have this envvar set, so there is really
no danger of it leaking elsewhere or causing unintended side-effects.

It would also have the benefit of not having to differentiate between
the two... :)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#894476: RCC: provide option to encode EPOCH timestamp

[Chris Lamb]

Hi Sune!

> I don't think honouring SOURCE_DATE_EPOCH is the right idea under normal 
> circumstances

Can you elaborate on what you mean by "normal circumstances"? :)

How about e use S_D_E if it is setup/exported, otherwise use the mtime
of the file as before?

(This is the pattern/logic used extensively elsewhere in toolchains for
this very exact purpose; it would not be unique to rcc)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#894476: RCC: provide option to encode EPOCH timestamp

[Chris Lamb]

Hi,

> While investigating ultracopier's lack of build reproducibility, I found
> out that rcc encodes the timestamp of the files the QRC file being
> compiled references

Indeed, we've been tracking this for a while in the Reproducible Builds
project [0] but, without a patch, we did not wish to bother you with a
bug. :)

It is affecting at least 4 or 5 other packages. I had previously tracked
it down to [1].

Regarding the solution, I think I would actually prefer to see something
consuming SOURCE_DATE_EPOCH[1] rather than adding an option to set a
specific timestamp.

  [0] https://reproducible-builds.org/
  [1] 
https://sources.debian.org/src/qtbase-opensource-src/5.9.2+dfsg-12/src/tools/rcc/rcc.cpp/#L207-L212
  [2] https://reproducible-builds.org/specs/source-date-epoch/


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#892203: kwayland: Implement zwp_linux_dmabuf_v1

[Chris Lamb]

severity 892203 wishlist
severity 892204 wishlist
thanks

Downgrading these to wishlist; "important" is generally reserved for really
major bugs.  :)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#889808: plasma-discover: Incomplete debian/copyright?

[Chris Lamb]

Source: plasma-discover
Version: 5.12.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Matthias Klumpp <m...@debian.org>

Hi,

I just ACCEPTed plasma-discover from NEW but noticed it was missing 
attribution in debian/copyright for at least Jan Grulich, Kai Uwe
Broulik, etc

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#875847: qttools5-dev-tools: .qhc files not reproducible

[Chris Lamb]

Hi Laurent,

> It seems that qcollectiongenerator is generating files that are
> containing the creation time of the qhc file (LastRegisterTime and
> CreationTime), making them non-reproducible.

Curiously, I don't see that when I build locally. But I *do* see:

  - The buildpath being leaked into ".index" files. This is fixed with
the attached patch.

  - Some variation in the binary, not looked into.

Hope that helps a little.


Best wishes,

-- 
  ,''`.
     : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible_build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible_build.patch   2017-09-15 15:52:48.740202062 
+0100
@@ -0,0 +1,17 @@
+Description: Make the build reproducible
+Author: Chris Lamb <la...@debian.org>
+Last-Update: 2017-09-15
+
+--- qttools-opensource-src-5.9.1.orig/src/qdoc/qdocindexfiles.cpp
 qttools-opensource-src-5.9.1/src/qdoc/qdocindexfiles.cpp
+@@ -995,10 +995,6 @@ bool QDocIndexFiles::generateIndexSectio
+ const Location& declLocation = node->declLocation();
+ if (!declLocation.fileName().isEmpty())
+ writer.writeAttribute("location", declLocation.fileName());
+-if (!declLocation.filePath().isEmpty()) {
+-writer.writeAttribute("filepath", declLocation.filePath());
+-writer.writeAttribute("lineno", 
QString("%1").arg(declLocation.lineNo()));
+-}
+ 
+ if (!node->since().isEmpty()) {
+ writer.writeAttribute("since", node->since());
--- a/debian/patches/series 1970-01-01 01:00:00.0 +0100
--- b/debian/patches/series 2017-09-15 15:29:30.377680344 +0100
@@ -0,0 +1 @@
+reproducible_build.patch

Bug#873918: charmtimetracker: Missing binary dependency on libqt5sql5-sqlite

[Chris Lamb]

Package: charmtimetracker
Version: 1.11.4-1
Severity: grave
Tags: patch
Justification: Renders package unusable

Hi,

charmtimetracker appears to be missing a binary dependency on
libqt5sql5-sqlite. Installing libqt5sql5-sqlite manually moves
past this.

  $ charmtimetracker
  QSqlDatabase: QSQLITE driver not loaded
  QSqlDatabase: available drivers: 

Screenshot of UI error:

  https://i.imgur.com/1RLOZ4L.jpg


Patch attached.



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

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages charmtimetracker depends on:
ii  libc62.24-17
ii  libgcc1  1:7.2.0-1
ii  libqt5core5a 5.9.1+dfsg-9
ii  libqt5dbus5  5.9.1+dfsg-9
ii  libqt5gui5   5.9.1+dfsg-9
ii  libqt5keychain1  0.7.0-3
ii  libqt5network5   5.9.1+dfsg-9
ii  libqt5printsupport5  5.9.1+dfsg-9
ii  libqt5script55.9.1+dfsg-2
ii  libqt5sql5   5.9.1+dfsg-9
ii  libqt5widgets5   5.9.1+dfsg-9
ii  libqt5xml5   5.9.1+dfsg-9
ii  libstdc++6   7.2.0-1
ii  libxcb-screensaver0  1.12-1
ii  libxcb1  1.12-1

charmtimetracker recommends no packages.

charmtimetracker suggests no packages.

-- no debconf information


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/control b/debian/control
index 32ff76f..ebdba87 100644
--- a/debian/control
+++ b/debian/control
@@ -20,7 +20,7 @@ Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-kde/kde-extras/charmtimetracker
 
 Package: charmtimetracker
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, libqt5sql5-sqlite
 Description: Cross-Platform Time Tracker
  It is built around two major ideas - tasks and events.
  Tasks are the things time is spend on, repeatedly. Tasks

Bug#873917: charmtimetracker: Please drop "Cross-Platform" from package description

[Chris Lamb]

Package: charmtimetracker
Version: 1.11.4-1
Severity: wishlist

Hi,

The package description says "Cross-Platform" which means Windows,
Mac & Linux according to the homepage.

Given the context, it seems sensible to drop the "cross-platform"
bit given that, well, we are producing a GNU/Linux distribution. :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Wheezy update of kdepim?

[Chris Lamb]

Dear maintainer(s),

The Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of kdepim:
https://security-tracker.debian.org/tracker/source-package/kdepim

Would you like to take care of this yourself?

If yes, please follow the workflow we have defined here:
https://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

You can also opt-out from receiving future similar emails in your
answer and then the LTS Team will take care of kdepim updates
for the LTS releases.

Thank you very much.

Chris Lamb,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#846252: kf5-kdepim-apps-libs: FTBFS: recipe for target 'kaddressbookgrantlee/src/CMakeFiles/KF5KaddressbookGrantlee.dir/all' failed

[Chris Lamb]

Maximiliano Curia wrote:

> This should have been fixed with the upload of gpgmepp 16.04.3-2, but since 
> we 
> are planning to remove gpgmepp in favor of the c++ interfaces provided in 
> gpgme1.0 for stretch, we still need to work on this package.

Makes sense…

> Control: severity -1 important

…but I don't understand this? :)


Regards,

-- 
  ,''`.
     : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#846252: kf5-kdepim-apps-libs: FTBFS: recipe for target 'kaddressbookgrantlee/src/CMakeFiles/KF5KaddressbookGrantlee.dir/all' failed

[Chris Lamb]

es/KF5ComposerEditorNG.dir/composereditor.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/composerview.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/link/composerlinkdialog.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/link/composeranchordialog.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/private/composerview_p.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/pagecolor/pagecolorbackgrounddialog.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/pagecolor/pagecolorbackgroundwidget.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/extendattributes/extendattributesdialog.cpp.o
 
CMakeFiles/KF5ComposerEditorNG.dir/extendattributes/extendattributesbutton.cpp.o
 
CMakeFiles/KF5ComposerEditorNG.dir/extendattributes/extendattributeswidget.cpp.o
 
CMakeFiles/KF5ComposerEditorNG.dir/extendattributes/extendattributesutils.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/utils/composereditorutils.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/image/composerimagedialog.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/image/composerimageresizewidget.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/table/composertabledialog.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/table/composertableresizewidget.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/table/composertableformatdialog.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/table/composertablecellformatdialog.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/table/composertableactionmenu.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/table/composercellsizewidget.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/image/composerimageresizetooltip.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/list/composerlistdialog.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/helper/tablehelper.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/helper/listhelper.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/widgets/domtreewidget.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/widgets/findreplacebar.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/globalsetting_composereditorng.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/composereditorng_debug.cpp.o 
CMakeFiles/KF5ComposerEditorNG.dir/KF5ComposerEditorNG_automoc.cpp.o 
/usr/lib/x86_64-linux-gnu/libKF5WebKit.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5PimCommon.so.5.2.2 
/usr/lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5.2.2 
/usr/lib/x86_64-linux-gnu/libKF5AkonadiContact.so.5.2.2 
/usr/lib/x86_64-linux-gnu/libQt5WebKitWidgets.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libKF5AkonadiWidgets.so.5.2.2 
/usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5.2.2 
/usr/lib/x86_64-linux-gnu/libKF5ItemModels.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Contacts.so.5.2.2 
/usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libKF5TextWidgets.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Completion.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Service.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5SonnetUi.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5SonnetCore.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigGui.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Auth.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Codecs.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libQt5Xml.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libKF5I18n.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.7.1 
  cd «BUILDDIR»/obj-x86_64-linux-gnu/composereditor-ng/src && /usr/bin/cmake -E 
cmake_symlink_library libKF5ComposerEditorNG.so.5.2.2 
libKF5ComposerEditorNG.so.5 libKF5ComposerEditorNG.so
  make[4]: Leaving directory '«BUILDDIR»/obj-x86_64-linux-gnu'
  [ 95%] Built target KF5ComposerEditorNG
  make[3]: Leaving directory '«BUILDDIR»/obj-x86_64-linux-gnu'
  Makefile:141: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory '«BUILDDIR»/obj-x86_64-linux-gnu'
  dh_auto_build: make -j9 returned exit code 2
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target 
'pre_build_dh_auto_build' failed
  make[1]: *** [pre_build_dh_auto_build] Error 2
  make[1]: Leaving directory '«BUILDDIR»'
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target 
'debian/dhmk_build' failed
  make: *** [debian/dhmk_build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
     `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


kf5-kdepim-apps-libs.4:16.04.2-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#843197: kde-full: Baloo is not installed with kde-full

[Chris]

Package: kde-full
Version: 5:91
Severity: important



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.6 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kde-full depends on:
ii  kde-plasma-desktop  5:91
ii  kde-standard5:91
ii  kdeadmin4:15.08.0+5.91
ii  kdeartwork  4:15.08.3-2
ii  kdeedu  4:15.08.0+5.91
ii  kdegames4:15.08.0+5.91
ii  kdegraphics 4:15.08.0+5.91
ii  kdemultimedia   4:15.08.0+5.91
ii  kdenetwork  4:15.08.0+5.91
ii  kdepim  4:16.04.3-2
ii  kdeutils4:15.08.0+5.91

Versions of packages kde-full recommends:
ii  kdeaccessibility  4:15.08.0+5.91
ii  kdesdk4:15.08.0+5.91
ii  kdetoys   4:15.08.0+5.91
ii  kdewebdev 4:16.04.3-1

Versions of packages kde-full suggests:
pn  calligra  
pn  kde-l10n  
ii  xorg  1:7.7+16

-- no debconf information!

Bug#840067: kscreen: FTBFS: debug.h:24:25: fatal error: kscreen/log.h: No such file or directory

[Chris Lamb]

Source: kscreen
Version: 4:5.8.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kscreen fails to build from source in unstable/amd64:

  [..]

  cd /home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0 && 
/usr/bin/msgfmt -o 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu/nl-kscreen.gmo
 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/po/nl/kscreen.po
  [ 51%] Built target pofiles_5
  make -f CMakeFiles/pofiles_36.dir/build.make CMakeFiles/pofiles_36.dir/depend
  [ 52%] Generating ro-kcm_displayconfiguration.gmo
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu'
  cd 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu/CMakeFiles/pofiles_36.dir/DependInfo.cmake
 --color=
  [ 51%] Built target pofiles_21
  [ 52%] Generating ru-plasma_applet_org.kde.plasma.kscreen.gmo
  cd /home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0 && 
/usr/bin/msgfmt -o 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu/ru-plasma_applet_org.kde.plasma.kscreen.gmo
 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/po/ru/plasma_applet_org.kde.plasma.kscreen.po
  cd /home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0 && 
/usr/bin/msgfmt -o 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu/ro-kcm_displayconfiguration.gmo
 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/po/ro/kcm_displayconfiguration.po
  make -f CMakeFiles/pofiles_37.dir/build.make CMakeFiles/pofiles_37.dir/depend
  [ 53%] Generating pl-kscreen.gmo
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu'
  cd 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu/CMakeFiles/pofiles_37.dir/DependInfo.cmake
 --color=
  cd /home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0 && 
/usr/bin/msgfmt -o 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu/pl-kscreen.gmo
 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/po/pl/kscreen.po
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu'
  [ 54%] Generating nb-plasma_applet_org.kde.plasma.kscreen.gmo
  [ 54%] Generating nn-plasma_applet_org.kde.plasma.kscreen.gmo
  cd /home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0 && 
/usr/bin/msgfmt -o 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu/nb-plasma_applet_org.kde.plasma.kscreen.gmo
 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/po/nb/plasma_applet_org.kde.plasma.kscreen.po
  cd /home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0 && 
/usr/bin/msgfmt -o 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu/nn-plasma_applet_org.kde.plasma.kscreen.gmo
 
/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/po/nn/plasma_applet_org.kde.plasma.kscreen.po
  [ 54%] Built target pofiles_30
  make -f CMakeFiles/pofiles_40.dir/build.make CMakeFiles/pofiles_40.dir/depend
  Scanning dependencies of target pofiles_36
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu'
  make -f CMakeFiles/pofiles_36.dir/build.make CMakeFiles/pofiles_36.dir/build
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20161007225500.e6BH3mcF47.db.kscreen/kscreen-5.8.0/obj-x86_64-linux-gnu'
  cd 

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Chris Lamb]

Ximo Baldó i Soriano wrote:

> So... The ongoing Perl migration causes plasma-discover (or its backend) to 
> bypass user's decision to deinstall 347 packages from his system?

There is no bypassing -- your package manager would have declared its
intention to remove all those packages.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#838738: print-manager: FTBFS: KCupsRequest.cpp:284:75: error: 'cupsGetPPD2' was not declared in this scope

[Chris Lamb]

Source: print-manager
Version: 4:16.04.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

print-manager fails to build from source in unstable/amd64:

  [..]

  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20160924085609.eUOd4xr1Wj.db.print-manager/print-manager-16.04.1
  OLDPWD=/home/lamby/temp/cdt.20160924085609.eUOd4xr1Wj.db.print-manager
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building print-manager 16.04.1-2 on amd64  
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package print-manager
  dpkg-buildpackage: info: source version 4:16.04.1-2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Maximiliano Curia <m...@debian.org>
   dpkg-source --before-build print-manager-16.04.1
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.pl 
--with=kf5,pkgkde-symbolshelper 
  dpkg-buildflags --export=make > debian/dhmk_env.mk
  /usr/bin/make -f debian/rules dhmk_run_clean_commands DHMK_TARGET="clean"
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160924085609.eUOd4xr1Wj.db.print-manager/print-manager-16.04.1'
  dh_testdir  
  dh_auto_clean '--buildsystem=kf5' --parallel  
  dh_clean  
  rm -rf debian/man/out
  rmdir debian/man
  rmdir: failed to remove 'debian/man': No such file or directory
  /usr/share/pkg-kde-tools/qt-kde-team/3/debian-qt-kde.mk:73: recipe for target 
'cleanup_manpages' failed
  make[1]: [cleanup_manpages] Error 1 (ignored)
  rm -f debian/stamp-man-pages
  rm -f debian/dhmk-install-list debian/dhmk-package-list
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160924085609.eUOd4xr1Wj.db.print-manager/print-manager-16.04.1'
  rm -f debian/dhmk_rules.mk debian/dhmk_env.mk debian/dhmk_configure 
debian/dhmk_build-indep debian/dhmk_build-arch debian/dhmk_build
  # "clean" target is done
  -- SUCCESS making standard target 'clean'.
   debian/rules build
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.pl 
--with=kf5,pkgkde-symbolshelper 
  dpkg-buildflags --export=make > debian/dhmk_env.mk
  /usr/bin/make -f debian/rules dhmk_run_configure_commands 
DHMK_TARGET="configure"
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160924085609.eUOd4xr1Wj.db.print-manager/print-manager-16.04.1'
  dh_testdir  
  dh_auto_configure '--buildsystem=kf5' --parallel  
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON
  -- The C compiler identification is GNU 6.2.0
  -- The CXX compiler identification is GNU 6.2.0
  -- Check for working C compiler: /usr/bin/cc
  -- Check for working C compiler: /usr/bin/cc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /usr/bin/c++
  -- Check for working CXX compiler: /usr/bin/c++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Looking for __GLIBC__
  -- Looking for __GLIBC__ - found
  -- Performing Test _OFFT_IS_64BIT
  -- Performing Test _OFFT_IS_64BIT - Success
  -- Found CUPS: /usr/lib/x86_64-linux-gnu/libcups.so
  -- Found KF5Config: 
/usr/lib/x86_64-linux-gnu/cmake/KF5Config/KF5ConfigConfig.cmake (found version 
"5.25.0") 
  -- Found KF5ConfigWidgets: 
/usr/lib/x86_64-linux-gnu/cmake/KF5ConfigWidgets/KF5ConfigWidgetsConfig.cmake 
(found version "5.25.0") 
  -- Found KF5CoreAddons: 
/usr/lib/x86_64-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsConfig.cmake (found 
version "5.25.0") 
  -- Found KF5DBusAddons: 
/usr/lib/x86_64-linux-gnu/cmake/KF5DBusAddons/KF5DBusAddonsConfig.cmake (found 
version "5.25.0") 
  -- Found KF5IconThemes: 
/usr/lib/x86_64-linux-gnu/cmake/KF5IconThemes/KF5IconThemesConfig.cmake (found 
version "5.25.0") 
  -- Found Gettext: /usr/bin/msgmerge

Bug#835399: kiriki: FTBFS: dh_install: Cannot find (any matches for) "usr/share/appdata/org.kde.kiriki.appdata.xml" (tried in "." and "debian/tmp")

[Chris Lamb]

Source: kiriki
Version: 4:16.04.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kiriki fails to build from source in unstable/amd64:

  [..]

  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.pl 
--with=kf5,pkgkde-symbolshelper 
  dpkg-buildflags --export=make > debian/dhmk_env.mk
  /usr/bin/make -f debian/rules dhmk_run_clean_commands DHMK_TARGET="clean"
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160825112032.UrxwW8cDvF.db.kiriki/kiriki-16.04.0'
  dh_testdir  
  dh_auto_clean '--buildsystem=kf5' --parallel  
  dh_clean  
  rm -rf debian/man/out
  rmdir debian/man
  rmdir: failed to remove 'debian/man': Directory not empty
  /usr/share/pkg-kde-tools/qt-kde-team/3/debian-qt-kde.mk:73: recipe for target 
'cleanup_manpages' failed
  make[1]: [cleanup_manpages] Error 1 (ignored)
  rm -f debian/stamp-man-pages
  rm -f debian/dhmk-install-list debian/dhmk-package-list
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160825112032.UrxwW8cDvF.db.kiriki/kiriki-16.04.0'
  rm -f debian/dhmk_rules.mk debian/dhmk_env.mk debian/dhmk_configure 
debian/dhmk_build-indep debian/dhmk_build-arch debian/dhmk_build
  # "clean" target is done
  -- SUCCESS making standard target 'clean'.
   debian/rules build
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.pl 
--with=kf5,pkgkde-symbolshelper 
  dpkg-buildflags --export=make > debian/dhmk_env.mk
  /usr/bin/make -f debian/rules dhmk_run_configure_commands 
DHMK_TARGET="configure"
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160825112032.UrxwW8cDvF.db.kiriki/kiriki-16.04.0'
  dh_testdir  
  # Running override target (override_dh_auto_configure)
  test -z "`ls debian/*.debhelper.log 2>/dev/null`" || sed -i 
'/^override_dh_auto_configure[[:space:]]/d' debian/*.debhelper.log
  /usr/bin/make -f debian/rules override_dh_auto_configure 
DH_INTERNAL_OVERRIDE="dh_auto_configure"  
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160825112032.UrxwW8cDvF.db.kiriki/kiriki-16.04.0'
  dh_auto_configure '--buildsystem=kf5' --parallel  -- 
-DBIN_INSTALL_DIR=/usr/games
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON 
-DBIN_INSTALL_DIR=/usr/games
  -- The C compiler identification is GNU 6.2.0
  -- The CXX compiler identification is GNU 6.2.0
  -- Check for working C compiler: /usr/bin/cc
  -- Check for working C compiler: /usr/bin/cc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /usr/bin/c++
  -- Check for working CXX compiler: /usr/bin/c++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Found KF5CoreAddons: 
/usr/lib/x86_64-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsConfig.cmake (found 
version "5.25.0") 
  -- Found KF5Config: 
/usr/lib/x86_64-linux-gnu/cmake/KF5Config/KF5ConfigConfig.cmake (found version 
"5.25.0") 
  -- Found KF5Crash: 
/usr/lib/x86_64-linux-gnu/cmake/KF5Crash/KF5CrashConfig.cmake (found version 
"5.25.0") 
  -- Found KF5DBusAddons: 
/usr/lib/x86_64-linux-gnu/cmake/KF5DBusAddons/KF5DBusAddonsConfig.cmake (found 
version "5.25.0") 
  -- Found KF5DocTools: 
/usr/lib/x86_64-linux-gnu/cmake/KF5DocTools/KF5DocToolsConfig.cmake (found 
version "5.25.0") 
  -- Found Gettext: /usr/bin/msgmerge (found version "0.19.8.1") 
  -- Found PythonInterp: /usr/bin/python (found version "2.7.12") 
  -- Found KF5I18n: /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake 
(found version "5.25.0") 
  -- Found KF5ConfigWidgets: 
/usr/lib/x86_64-linux-gnu/cmake/KF5ConfigWidgets/KF5ConfigWidgetsConfig.cmake 
(found version "5.25.0") 
  -- Found KF5IconThemes: 
/usr/lib/x86_64-linux-gnu/cmake/KF5IconThemes/KF5IconThemesConfig.cmake (found 
version "5.25.0") 
  -- Found KF5XmlGui: 
/usr/lib/x86_64-linux-gnu/cmake/KF5XmlGui/KF5XmlGuiConfig.cmake (found version 
"5.25.0") 
  -- Found KF5: success (found version "5.25.0") found components:  CoreAddons 
Config Crash DBusAddons DocTools I18n ConfigWidgets IconThemes XmlGui DocTools 
  CMake Deprecation Warning at 
/usr/share/ECM/kde-modules/KDEInstallDirs.cmake:311 (message):
BIN_INSTALL_DIR is deprecated, use KDE_INSTALL_BINDIR instead.
  Call Stack (most recent call first):
/usr/share/ECM/kde-modules/KDEInstallDirs.cmake:399 (_define_relative)
CMakeLists.txt:29 (include)
  
  
  -- Looking for __GLIBC__
  -- Looking for __GLIBC__ - found
  -- Performing Test _OFFT_IS_64BIT
  -- Performing Test 

Bug#835282: rocs: FTBFS: dh_install: Cannot find (any matches for) "usr/share/appdata/org.kde.rocs.appdata.xml" (tried in "." and "debian/tmp")

[Chris Lamb]

60824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu'
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1'
  dh_install  
  dh_install: Cannot find (any matches for) 
"usr/share/appdata/org.kde.rocs.appdata.xml" (tried in "." and "debian/tmp")
  dh_install: rocs missing files: usr/share/appdata/org.kde.rocs.appdata.xml
  dh_install: missing files, aborting
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target 
'pre_install_dh_install' failed
  make[1]: *** [pre_install_dh_install] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1'
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target 
'debian/dhmk_install' failed
  make: *** [debian/dhmk_install] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


rocs.4:16.04.1-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#835053: kxmlgui: please make the build reproducible

[Chris Lamb]

> The value is (at least was until some time ago) added in bug reports in
> bugzilla, and that helps to know more about the environment in which
> a bug happens.

Mm, except that in the majority of cases it's going to tell you the uname
of the Debian buildd that made the package, not really the environment
in which the bug actually occurred.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#835053: kxmlgui: please make the build reproducible

[Chris Lamb]

Source: kxmlgui
Version: 5.25.0-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: uname
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], I noticed
that kxmlgui could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible-build.patch   2016-08-21 18:19:22.645111083 
+0100
@@ -0,0 +1,13 @@
+Description: Make the build reproducible
+Author: Chris Lamb <la...@debian.org>
+Last-Update: 2016-08-21
+
+--- kxmlgui-5.25.0.orig/src/config-xmlgui.h.cmake
 kxmlgui-5.25.0/src/config-xmlgui.h.cmake
+@@ -1,5 +1,5 @@
+ #define XMLGUI_DISTRIBUTION_TEXT "${XMLGUI_DISTRIBUTION_TEXT}"
+-#define XMLGUI_COMPILING_OS "${CMAKE_SYSTEM}"
++#define XMLGUI_COMPILING_OS "Generic"
+ #define XMLGUI_COMPILER_VERSION "${XMLGUI_COMPILER_VERSION}"
+ 
+ #define CMAKE_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}"
--- a/debian/patches/series 1970-01-01 01:00:00.0 +0100
--- b/debian/patches/series 2016-08-21 18:19:19.885060733 +0100
@@ -0,0 +1 @@
+reproducible-build.patch

Wheezy update of kde4libs?

[Chris Lamb]

Hello dear maintainer(s),

the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of kde4libs:
https://security-tracker.debian.org/tracker/CVE-2016-6232

Would you like to take care of this yourself?

If yes, please follow the workflow we have defined here:
https://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

Thank you very much.

Chris Lamb,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#828881: grantlee5: FTBFS: "Error: i18np_var tag takes at least four arguments, line 0, "

[Chris Lamb]

it code 2
  debian/rules:18: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160628205618.8aYpoeLb3r.grantlee5/grantlee5-5.0.0'
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


grantlee5.5.0.0-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#828878: charmtimetracker: FTBFS: qglobal.h:1087:4: error: #error "You must build your code with position independent code if Qt was built with -reduce-relocations. "

[Chris Lamb]

Source: charmtimetracker
Version: 1.10.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

charmtimetracker fails to build from source in unstable/amd64:

  [..]

  [ 21%] Built target CharmApplication_automoc
  make -f Charm/CMakeFiles/CharmApplication.dir/build.make 
Charm/CMakeFiles/CharmApplication.dir/depend
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu'
  [ 21%] Generating ui_TaskEditor.h
  cd 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm
 && /usr/lib/x86_64-linux-gnu/qt5/bin/uic -o 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm/ui_TaskEditor.h
 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/Charm/Widgets/TaskEditor.ui
  [ 21%] Generating ui_CharmPreferences.h
  cd 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm
 && /usr/lib/x86_64-linux-gnu/qt5/bin/uic -o 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm/ui_CharmPreferences.h
 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/Charm/Widgets/CharmPreferences.ui
  [ 22%] Generating ui_TaskIdDialog.h
  cd 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm
 && /usr/lib/x86_64-linux-gnu/qt5/bin/uic -o 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm/ui_TaskIdDialog.h
 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/Charm/Widgets/TaskIdDialog.ui
  [ 22%] Generating ui_FindAndReplaceEventsDialog.h
  cd 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm
 && /usr/lib/x86_64-linux-gnu/qt5/bin/uic -o 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm/ui_FindAndReplaceEventsDialog.h
 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/Charm/Widgets/FindAndReplaceEventsDialog.ui
  [ 23%] Generating ui_ConfigurationDialog.h
  cd 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm
 && /usr/lib/x86_64-linux-gnu/qt5/bin/uic -o 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm/ui_ConfigurationDialog.h
 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/Charm/Widgets/ConfigurationDialog.ui
  [ 24%] Generating ui_CommentEditorPopup.h
  cd 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm
 && /usr/lib/x86_64-linux-gnu/qt5/bin/uic -o 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm/ui_CommentEditorPopup.h
 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/Charm/Widgets/CommentEditorPopup.ui
  [ 25%] Generating ui_CharmAboutDialog.h
  cd 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm
 && /usr/lib/x86_64-linux-gnu/qt5/bin/uic -o 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm/ui_CharmAboutDialog.h
 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/Charm/Widgets/CharmAboutDialog.ui
  [ 26%] Generating ui_EnterVacationDialog.h
  cd 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm
 && /usr/lib/x86_64-linux-gnu/qt5/bin/uic -o 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm/ui_EnterVacationDialog.h
 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/Charm/Widgets/EnterVacationDialog.ui
  [ 26%] Generating ui_CharmNewReleaseDialog.h
  cd 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm
 && /usr/lib/x86_64-linux-gnu/qt5/bin/uic -o 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/obj-x86_64-linux-gnu/Charm/ui_CharmNewReleaseDialog.h
 
/home/lamby/temp/cdt.20160628205159.GmNhAZlqZC.charmtimetracker/charmtimetracker-1.10.0/Charm/Widgets/CharmNewReleaseDialog.ui
  [ 27%] Generating ui_IdleCorrectionDialog.h
  cd 

Bug#828114: kdewebdev: FTBFS: src/tidy/tidyx.h:52:20: fatal error: buffio.h: No such file or directory

[Chris Lamb]

Source: kdewebdev
Version: 4:15.08.3-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kdewebdev fails to build from source in unstable/amd64:

  [..]

   KNEWSTUFF_EXPORT_DEPRECATED KAction * standardAction(const QString ,
 ^
  
/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/klinkstatus/src/actionmanager.cpp:
 At global scope:
  
/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/klinkstatus/src/actionmanager.cpp:309:54:
 warning: unused parameter 'sessionWidget' [-Wunused-parameter]
   void ActionManager::initSessionWidget(SessionWidget* sessionWidget)
^
  [ 56%] Building CXX object 
kfilereplace/CMakeFiles/kfilereplacepart.dir/commandengine.o
  cd 
/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/obj-x86_64-linux-gnu/kfilereplace
 && /usr/bin/c++   -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=56 
-DKDE_DEPRECATED_WARNINGS -DMAKE_KFILEREPLACEPART_LIB -DQT3_SUPPORT 
-DQT3_SUPPORT_WARNINGS -DQT_NO_CAST_TO_ASCII -DQT_NO_STL -D_BSD_SOURCE 
-D_DEFAULT_SOURCE -D_REENTRANT -D_XOPEN_SOURCE=500 
-I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/obj-x86_64-linux-gnu/kfilereplace
 
-I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/kfilereplace
 -I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3 
-I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/obj-x86_64-linux-gnu
 -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns 
-I/usr/include/qt4/QtXml -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest 
-I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql 
-I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript 
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtHelp 
-I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative 
-I/usr/include/qt4/QtDBus -I/usr/include/qt4/Qt3Support 
-I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt 
-I/usr/share/qt4/mkspecs/default -I/usr/include/qt4  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -Wnon-virtual-dtor 
-Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith 
-Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common 
-Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden 
-Werror=return-type -fvisibility-inlines-hidden -DNDEBUG -DQT_NO_DEBUG -fPIC   
-D_GNU_SOURCE -D_LARGEFILE64_SOURCE -o 
CMakeFiles/kfilereplacepart.dir/commandengine.o -c 
/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/kfilereplace/commandengine.cpp
  [ 57%] Building CXX object 
klinkstatus/src/CMakeFiles/klinkstatuscommon.dir/automationconfig.o
  cd 
/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/obj-x86_64-linux-gnu/klinkstatus/src
 && /usr/bin/c++   -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=56 
-DKDE_DEPRECATED_WARNINGS -DMAKE_KLINKSTATUSCOMMON_LIB -DQT_NO_CAST_TO_ASCII 
-DQT_NO_STL -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_REENTRANT -D_XOPEN_SOURCE=500 
-I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/obj-x86_64-linux-gnu/klinkstatus/src
 
-I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/klinkstatus/src
 -I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3 
-I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/obj-x86_64-linux-gnu
 
-I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/klinkstatus/src/ui
 
-I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/klinkstatus/src/interfaces
 
-I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/klinkstatus/src/interfaces/engine
 
-I/home/lamby/temp/cdt.20160625082419.oAVucN6rm3.kdewebdev/kdewebdev-15.08.3/klinkstatus/src/interfaces/ui
 -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns 
-I/usr/include/qt4/QtXml -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest 
-I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql 
-I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript 
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtHelp 
-I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative 
-I/usr/include/qt4/QtDBus -I/usr/include/qt4/Qt3Support 
-I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt 
-I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -I/usr/include/threadweaver 
-I/usr/include/tidy  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align 

Bug#827811: signond: FTBFS: dh_makeshlibs: failing due to earlier errors

[Chris Lamb]

SessionDataELb1EE9ConstructEPvPKv@Base
 8.57+20150423
  - 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn5ErrorELb1EE6CreateEPKv@Base
 8.57+20150423
  - 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn5ErrorELb1EE6DeleteEPv@Base
 8.57+20150423
  +#MISSING: 8.57+20150423-3# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn5ErrorELb1EE6CreateEPKv@Base
 8.57+20150423
  +#MISSING: 8.57+20150423-3# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn5ErrorELb1EE6DeleteEPv@Base
 8.57+20150423

(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn5ErrorELb1EE8DestructEPv@Base
 8.57+20150423

(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn5ErrorELb1EE9ConstructEPvPKv@Base
 8.57+20150423
_ZN19AuthPluginInterface11qt_metacallEN11QMetaObject4CallEiPPv@Base 
8.57+20150423
  @@ -60,6 +62,9 @@
_ZN19AuthPluginInterface6resultERKN6SignOn11SessionDataE@Base 8.57+20150423
_ZN19AuthPluginInterface7refreshERKN6SignOn13UiSessionDataE@Base 
8.57+20150423
_ZN19AuthPluginInterface9refreshedERKN6SignOn13UiSessionDataE@Base 
8.57+20150423
  + _ZN4QMapI7QString8QVariantED1Ev@Base 8.57+20150423-3
  + _ZN4QMapI7QString8QVariantED2Ev@Base 8.57+20150423-3
  + _ZN4QMapI7QString8QVariantEaSERKS2_@Base 8.57+20150423-3
_ZN6SignOn5ErrorD0Ev@Base 8.57+20150423
_ZN6SignOn5ErrorD1Ev@Base 8.57+20150423
_ZN6SignOn5ErrorD2Ev@Base 8.57+20150423
  dh_makeshlibs: failing due to earlier errors
  /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:97: recipe for target 
'pre_binary_dh_makeshlibs' failed
  make[1]: *** [pre_binary_dh_makeshlibs] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160621105021.n38x92gR2k.signond/signond-8.57+20150423'
  /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:110: recipe for target 
'debian/dhmk_binary' failed
  make: *** [debian/dhmk_binary] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


signond.8.57+20150423-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#825891: Same here

[chris]

Same with my stretch/testing installation. Performed dist-upgrade today, 
4th of June.Thanks, Chris

Bug#826023: kdeedu-data: FTBFS: Failed call: qmake-qt5 -query "QT_INSTALL_PREFIX"

[Chris Lamb]

  CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=1
  //ADVANCED property for variable: CMAKE_OBJCOPY
  CMAKE_OBJCOPY-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_OBJDUMP
  CMAKE_OBJDUMP-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_RANLIB
  CMAKE_RANLIB-ADVANCED:INTERNAL=1
  //Path to CMake installation.
  CMAKE_ROOT:INTERNAL=/usr/share/cmake-3.5
  //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
  CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
  CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
  CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
  CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
  CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
  CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_SKIP_RPATH
  CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
  CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
  CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
  CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
  CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
  CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_STRIP
  CMAKE_STRIP-ADVANCED:INTERNAL=1
  //uname command
  CMAKE_UNAME:INTERNAL=/bin/uname
  //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
  CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: KDE_INSTALL_BINDIR
  KDE_INSTALL_BINDIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: KDE_INSTALL_CMAKEPACKAGEDIR
  KDE_INSTALL_CMAKEPACKAGEDIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: KDE_INSTALL_EXECROOTDIR
  KDE_INSTALL_EXECROOTDIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: KDE_INSTALL_LIBDIR
  KDE_INSTALL_LIBDIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: KDE_INSTALL_LIBEXECDIR
  KDE_INSTALL_LIBEXECDIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: KDE_INSTALL_SBINDIR
  KDE_INSTALL_SBINDIR-ADVANCED:INTERNAL=1
  
  dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_USE_RELATIVE_PATHS=ON returned exit code 1
  /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:97: recipe for target 
'pre_configure_dh_auto_configure' failed
  make[1]: *** [pre_configure_dh_auto_configure] Error 255
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160601163626.8UPWJgzloW.kdeedu-data/kdeedu-data-15.12.0'
  /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:110: recipe for target 
'debian/dhmk_configure' failed
  make: *** [debian/dhmk_configure] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


kdeedu-data.4:15.12.0-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#824586: networkmanager-qt: FTBFS: dh_makeshlibs: failing due to earlier errors

[Chris Lamb]

xDeviceE@Base 
5.1.1+git20141203.0020+15.04
_ZTIN14NetworkManager11WiredDeviceE@Base 5.1.1+git20141203.0020+15.04
_ZTIN14NetworkManager12BridgeDeviceE@Base 5.1.1+git20141203.0020+15.04
_ZTIN14NetworkManager12PppoeSettingE@Base 5.1.1+git20141203.0020+15.04
  @@ -1488,7 +1491,7 @@
_ZTIN14NetworkManager6DeviceE@Base 5.1.1+git20141203.0020+15.04
_ZTIN14NetworkManager7SettingE@Base 5.1.1+git20141203.0020+15.04
_ZTIN14NetworkManager8NotifierE@Base 5.1.1+git20141203.0020+15.04
  - _ZTIN14NetworkManager8WimaxNspE@Base 5.1.1+git20141203.0020+15.04
  +#MISSING: 5.16.0-1# _ZTIN14NetworkManager8WimaxNspE@Base 
5.1.1+git20141203.0020+15.04
_ZTIN14NetworkManager9GreDeviceE@Base 5.6.0
_ZTIN14NetworkManager9TunDeviceE@Base 5.6.0
_ZTIN14NetworkManager9VpnPluginE@Base 5.1.1+git20141203.0020+15.04
  @@ -1514,7 +1517,7 @@
_ZTSN14NetworkManager11SecretAgentE@Base 5.1.1+git20141203.0020+15.04
_ZTSN14NetworkManager11TeamSettingE@Base 5.6.0
_ZTSN14NetworkManager11VlanSettingE@Base 5.1.1+git20141203.0020+15.04
  - _ZTSN14NetworkManager11WimaxDeviceE@Base 5.1.1+git20141203.0020+15.04
  +#MISSING: 5.16.0-1# _ZTSN14NetworkManager11WimaxDeviceE@Base 
5.1.1+git20141203.0020+15.04
_ZTSN14NetworkManager11WiredDeviceE@Base 5.1.1+git20141203.0020+15.04
_ZTSN14NetworkManager12BridgeDeviceE@Base 5.1.1+git20141203.0020+15.04
_ZTSN14NetworkManager12PppoeSettingE@Base 5.1.1+git20141203.0020+15.04
  @@ -1544,7 +1547,7 @@
_ZTSN14NetworkManager6DeviceE@Base 5.1.1+git20141203.0020+15.04
_ZTSN14NetworkManager7SettingE@Base 5.1.1+git20141203.0020+15.04
_ZTSN14NetworkManager8NotifierE@Base 5.1.1+git20141203.0020+15.04
  - _ZTSN14NetworkManager8WimaxNspE@Base 5.1.1+git20141203.0020+15.04
  +#MISSING: 5.16.0-1# _ZTSN14NetworkManager8WimaxNspE@Base 
5.1.1+git20141203.0020+15.04
_ZTSN14NetworkManager9GreDeviceE@Base 5.6.0
_ZTSN14NetworkManager9TunDeviceE@Base 5.6.0
_ZTSN14NetworkManager9VpnPluginE@Base 5.1.1+git20141203.0020+15.04
  @@ -1569,7 +1572,7 @@
_ZTVN14NetworkManager11SecretAgentE@Base 5.1.1+git20141203.0020+15.04
_ZTVN14NetworkManager11TeamSettingE@Base 5.6.0
_ZTVN14NetworkManager11VlanSettingE@Base 5.1.1+git20141203.0020+15.04
  - _ZTVN14NetworkManager11WimaxDeviceE@Base 5.1.1+git20141203.0020+15.04
  +#MISSING: 5.16.0-1# _ZTVN14NetworkManager11WimaxDeviceE@Base 
5.1.1+git20141203.0020+15.04
_ZTVN14NetworkManager11WiredDeviceE@Base 5.1.1+git20141203.0020+15.04
_ZTVN14NetworkManager12BridgeDeviceE@Base 5.1.1+git20141203.0020+15.04
_ZTVN14NetworkManager12PppoeSettingE@Base 5.1.1+git20141203.0020+15.04
  @@ -1599,7 +1602,7 @@
_ZTVN14NetworkManager6DeviceE@Base 5.1.1+git20141203.0020+15.04
_ZTVN14NetworkManager7SettingE@Base 5.1.1+git20141203.0020+15.04
_ZTVN14NetworkManager8NotifierE@Base 5.1.1+git20141203.0020+15.04
  - _ZTVN14NetworkManager8WimaxNspE@Base 5.1.1+git20141203.0020+15.04
  +#MISSING: 5.16.0-1# _ZTVN14NetworkManager8WimaxNspE@Base 
5.1.1+git20141203.0020+15.04
_ZTVN14NetworkManager9GreDeviceE@Base 5.6.0
_ZTVN14NetworkManager9TunDeviceE@Base 5.6.0
_ZTVN14NetworkManager9VpnPluginE@Base 5.1.1+git20141203.0020+15.04
  dh_makeshlibs: failing due to earlier errors
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target 
'pre_binary_dh_makeshlibs' failed
  make[1]: *** [pre_binary_dh_makeshlibs] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160517195048.VlRK3bUjME.networkmanager-qt/networkmanager-qt-5.16.0'
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target 
'debian/dhmk_binary' failed
  make: *** [debian/dhmk_binary] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


networkmanager-qt.5.16.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#821324: kamera: FTBFS: The following REQUIRED packages could NOT be located on your system [..] gphoto2

[Chris Lamb]

  __KDE_HAVE_GCC_VISIBILITY:INTERNAL=1
  //Test __KDE_HAVE_W_OVERLOADED_VIRTUAL
  __KDE_HAVE_W_OVERLOADED_VIRTUAL:INTERNAL=1
  //Result of TRY_COMPILE
  _basic_compile_result:INTERNAL=TRUE
  //Result of TRY_COMPILE
  _compile_result:INTERNAL=TRUE
  
  dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_USE_RELATIVE_PATHS=ON returned exit code 1
  /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:97: recipe for target 
'pre_configure_dh_auto_configure' failed
  make[1]: *** [pre_configure_dh_auto_configure] Error 255
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160417184505.5Sge1Gl3ai.kamera/kamera-4.14.2'
  /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:110: recipe for target 
'debian/dhmk_configure' failed
  make: *** [debian/dhmk_configure] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


kamera.4:4.14.2-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#814766: signon-ui: FTBFS: xvfb-run -a ./tst_inactivity_timer \n Floating point exception (core dumped)

[Chris Lamb]

> I didn't get any segfaults, though I did get this warning.
> 
> signon-ui_0.17+15.10.20150810-2_amd64.build-libEGL warning: DRI2: failed to 
> open swrast (search paths /usr/lib/x86_64-linux-gnu/dri:
> ${ORIGIN}/dri:/usr/lib/dri)

Curiously, I get a *different* FTBFS now:

  Project ERROR: libnotify development package not found.

Full build-log (with packages) attached.


Regards,

-- 
  ,''`.
     : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


signon-ui.0.17+15.10.20150810-2.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#818943: possibly add -openssl-linked ./conifugre option for building Qt (issue with Mumble)

[Chris Knadle]

Lisandro Damián Nicanor Pérez Meyer:
> On Tuesday 22 March 2016 03:48:48 Chris Knadle wrote:
[...]
>> Lisandro Damián Nicanor Pérez Meyer:
>>> Actually the binary built can be installed in a private path alongside
>>> qtnetwork (in it's package) and might even be a private lib without
>>> headers. That should be enough to keep stuff in sync.
>>
>> I'm not sure I fully understand this, but it vaguely sounds good.
> 
> Easy: instead of creating a new package just ship a very very simple app 
> alongside libqt4-network/libqt5network5. This will make dh_shlibdeps add the 
> current version of libssl as a dependency of the package so we can warrant 
> two 
> things: the src package will get rebuilt with any libssl transition and an 
> appropriate version of libssl will be a hard dependency of each qtnetwork 
> package.
> 
> We just need to use the proper licensing for that dummy app :)
> 
> That being said I'm not having much time on my hands to code and integrate 
> the 
> app, although I would definitely do it if I happen to have it.

If you have an idea of what you'd like the result to look like, that would
at least give me an idea I might be able to work with.  [I might be able to
make time to try to build something if I know what it needs to be.]

>>> By the way, how is mumble's porting to qt5 going?
>>
>> That part is already ready.  Mumble 1.3.x (which doesn't yet have a release)
>> already builds with Qt5 fine and I've got the Debian packaging ready for
>> when there's a release to ship.  Mumble 1.3.x can be built with Qt4 or Qt5,
>> Mumble 1.4.x will be Qt5 only.
> 
> Excellent! Let's hope that happens in time for Stretch.

It should.  There's a somewhat pressing need for Mumble 1.3.x because Qt5 is
needed in order to support Perfect Forward Secrecy.  AFAIK the earliest
Stretch freeze is November 5th and there have been a number of 1.3.x
snapshots, so it seems like a release is close.

-- 
Chris Knadle
chris.kna...@coredump.us

Bug#818943: possibly add -openssl-linked ./conifugre option for building Qt (issue with Mumble)

[Chris Knadle]

Lisandro Damián Nicanor Pérez Meyer:
> First of all sorry for the formatting, I'm on the phone right now.

The mail seems to contain both HTML and TEXT, so no worries AFAIC.

> Second: thanks for digging this issue that much! I have now a quite clear
> (although I might need to re read something) idea of the issue.

I've been working on this problem since early November.  ;-)  It's been both
a frustrating and fascinating bug to work on, and I've learned a bit in the
process.  Thankfully I've also had a good bit of help -- there's no way I
would have figured this out on my own.

> Let's start with the configure option: the problem it's not a technical 
> one. If we forget about possible licensing problems then using the 
> necessary switch is just one upload away.
> 
> Now I can't decide whether it's safe or not to use this option 
> license-wide. As I understand this the RT is not the authoritative source
> for this, but the FTP team.

Yes another DD I commonly work with told me that [debian-legal] is just a
discussion list and that the FTP masters have final say concerning both
legal and licensing issues [concerning package uploads].  That seems like a
lot of responsibility.

> Even if I'm wrong wrt team's  responsabilities, I'm still uncertain wrt 
> the licensing issue. As far as I understand nothing has changed 
> license-wide, so Modestas' reply is still valid.
> 
> Sadly I can't also think of a way of marking qt to be rebuilt with some 
> libssl upload without linking to it...
> 
> I'm afraid the only suitable fix would be to fix ssl's licensing terms.

This is another interesting twist -- Kurt reported OpenSSL upstream is
looking to change the license (to the Apache2 license, sounds like) but
hasn't happened yet:

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804487#112

and if you see the message that follows it says that there are still likely
some GPLv2 licensing incompatibilities to consider.



Lisandro Damián Nicanor Pérez Meyer:
> On Monday 21 March 2016 21:47:50 Lisandro Damián Nicanor Pérez Meyer 
> wrote: [snip]
>> Sadly I can't also think of a way of marking qt to be rebuilt with some
>> libssl upload without linking to it...
> 
> Actually there is a **very** **hackish** way to let qt4/qtbase be rebuilt
> with the necessary libssl versions. It would be possible to code a very
> simple app that links against it with the proper licensing terms and ship
> it in it's own binary package. This app would be built from qt4/qtbase's
> src. Yes, that means a useless binary package in the archive...

Ooof.  A sort of "fake" package for metadata purposes.  Yeah I see it; thank
you for mentioning the idea.  If it comes to that naturally I'd want to
mention the bug reports in either a README file in the "fake" package and/or
the description in the debian/control file to make it clear why the package
exists.

This would shorten the length of time of the transition and so would either
shorten the time of Mumble breakage or the time where Mumble would double
load libssl/libcrypto versions, and leaves the dilemma of which of these to do.


Lisandro Damián Nicanor Pérez Meyer:
> Actually the binary built can be installed in a private path alongside
> qtnetwork (in it's package) and might even be a private lib without
> headers. That should be enough to keep stuff in sync.

I'm not sure I fully understand this, but it vaguely sounds good.

> By the way, how is mumble's porting to qt5 going?

That part is already ready.  Mumble 1.3.x (which doesn't yet have a release)
already builds with Qt5 fine and I've got the Debian packaging ready for
when there's a release to ship.  Mumble 1.3.x can be built with Qt4 or Qt5,
Mumble 1.4.x will be Qt5 only.

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Bug#818943: possibly add -openssl-linked ./conifugre option for building Qt (issue with Mumble)

[Chris Knadle]

Source: qt4-x11
Severity: normal

I'd like to know whether it would be possible to add the -openssl-linked
./configure option for building Qt.

   https://doc.qt.io/qt-4.8/ssl.html

I have a rather complicated problem concerning mumble (#804363) which
concerns Mumble breaking during OpenSSL transitions that have library
renames.  With the patch I'm currently using to mitigated the bug, due to Qt
using dlopen() to load libssl/libcrypto during these transitions two copies
of libssl/libcrypto with ABI differences between them both get loaded and we
believe both get initialized, so figuring out what will happen is
nontrivial.  The Debian OpenSSL maintainer says that this shold work but
that OpenSSL upstream is not likely to guarantee that it will.  Mumble
upstream wants to implement a patch which would cause Mumble to quit with an
error if it finds two copies of libssl/libcrypto loaded to ban this
possibility.  (https://github.com/mumble-voip/mumble/pull/2124)

Mumble has broken in a similar way before, and at the time it was thought
that linking Qt with libssl/libcrytpo would have licensing issues:

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623596#94

We've tried to find other possible mitigation methods and during this the
release team said they aren't sure that having Qt linked with OpenSSL would
cause further licensing issues:

   https://lists.debian.org/debian-release/2016/03/msg00409.html

Mumble upstream and the OpenSSL maintainer think that if Qt used the
-openssl-linked option it may handle the problem in (#804363) better:

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804487#102


So... I'm writing this bug to get input from the Qt maintainers as to
whether using the -openssl-linked ./configure option when building Qt is
possible (and whether it would help).

Thanks much.
  -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (150,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#815738: libspectre: FTBFS: spectre-gs.c:46:9: error: 'e_Fatal' undeclared (first use in this function)

[Chris Lamb]

Source: libspectre
Version: 0.2.7-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

libspectre fails to build from source in unstable/amd64:

  [..]

  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -I.. -I. -I.. -Wall -Wextra -Wsign-compare 
-Werror-implicit-function-declaration -Wpointer-arith -Wstrict-prototypes 
-Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Wpacked 
-Wswitch-enum -Wstrict-aliasing=2 -Winit-self -Wunsafe-loop-optimizations 
-Wdeclaration-after-statement -Wno-missing-field-initializers 
-Wno-unused-parameter -Wno-attributes -Wno-long-long -Winline -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c spectre-device.c  
-fPIC -DPIC -o .libs/libspectre_la-spectre-device.o
  spectre-gs.c: In function 'critic_error_code':
  spectre-gs.c:46:9: error: 'e_Fatal' undeclared (first use in this function)
  case e_Fatal:
   ^
  spectre-gs.c:46:9: note: each undeclared identifier is reported only once for 
each function it appears in
  spectre-gs.c:51:9: error: 'e_ExecStackUnderflow' undeclared (first use in 
this function)
  case e_ExecStackUnderflow:
   ^
  spectre-gs.c: In function 'spectre_gs_process':
  spectre-gs.c:112:20: error: 'e_NeedInput' undeclared (first use in this 
function)
 error = error == e_NeedInput ? 0 : error;
  ^
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -I.. -I. -I.. -Wall -Wextra -Wsign-compare 
-Werror-implicit-function-declaration -Wpointer-arith -Wstrict-prototypes 
-Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Wpacked 
-Wswitch-enum -Wstrict-aliasing=2 -Winit-self -Wunsafe-loop-optimizations 
-Wdeclaration-after-statement -Wno-missing-field-initializers 
-Wno-unused-parameter -Wno-attributes -Wno-long-long -Winline -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c spectre-page.c -o 
libspectre_la-spectre-page.o >/dev/null 2>&1
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -I.. -I. -I.. -Wall -Wextra -Wsign-compare 
-Werror-implicit-function-declaration -Wpointer-arith -Wstrict-prototypes 
-Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Wpacked 
-Wswitch-enum -Wstrict-aliasing=2 -Winit-self -Wunsafe-loop-optimizations 
-Wdeclaration-after-statement -Wno-missing-field-initializers 
-Wno-unused-parameter -Wno-attributes -Wno-long-long -Winline -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c 
spectre-exporter-ps.c  -fPIC -DPIC -o .libs/libspectre_la-spectre-exporter-ps.o
  Makefile:530: recipe for target 'libspectre_la-spectre-gs.lo' failed
  make[3]: *** [libspectre_la-spectre-gs.lo] Error 1
  make[3]: *** Waiting for unfinished jobs


  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


libspectre.0.2.7-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#814766: signon-ui: FTBFS: xvfb-run -a ./tst_inactivity_timer \n Floating point exception (core dumped)

[Chris Lamb]

Source: signon-ui
Version: 0.17+15.10.20150810-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

signon-ui fails to build from source in unstable/amd64:

  [..]

  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160215091107.y868q8N71x/signon-ui-0.17+15.10.20150810/tests/unit'
  ( test -e Makefile.tst_inactivity_timer || 
/usr/lib/x86_64-linux-gnu/qt5/bin/qmake 
/home/lamby/temp/cdt.20160215091107.y868q8N71x/signon-ui-0.17+15.10.20150810/tests/unit/tst_inactivity_timer.pro
 -nocache 'QMAKE_CFLAGS_RELEASE=-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 'QMAKE_CFLAGS_DEBUG=-g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2' 'QMAKE_CXXFLAGS_RELEASE=-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 
'QMAKE_CXXFLAGS_DEBUG=-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 
QMAKE_LFLAGS_RELEASE=-Wl,-z,relro QMAKE_LFLAGS_DEBUG=-Wl,-z,relro QMAKE_STRIP=: 
PREFIX=/usr CONFIG+=force-foreign-qwindow CONFIG+=use-ubuntu-web-view 
HTTP_WARNING_HELP=help:web-credentials/http-warning 
LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu -o 
Makefile.tst_inactivity_timer ) && make -f Makefile.tst_inactivity_timer check
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160215091107.y868q8N71x/signon-ui-0.17+15.10.20150810/tests/unit'
  xvfb-run -a ./tst_inactivity_timer
  Floating point exception (core dumped)
  Makefile.tst_inactivity_timer:333: recipe for target 'check' failed
  make[4]: *** [check] Error 136
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160215091107.y868q8N71x/signon-ui-0.17+15.10.20150810/tests/unit'
  Makefile:201: recipe for target 'sub-tst_inactivity_timer-pro-check' failed
  make[3]: *** [sub-tst_inactivity_timer-pro-check] Error 2
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160215091107.y868q8N71x/signon-ui-0.17+15.10.20150810/tests/unit'
  Makefile:209: recipe for target 'sub-unit-check_ordered' failed
  make[2]: *** [sub-unit-check_ordered] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160215091107.y868q8N71x/signon-ui-0.17+15.10.20150810/tests'
  Makefile:316: recipe for target 'sub-tests-check_ordered' failed
  make[1]: *** [sub-tests-check_ordered] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160215091107.y868q8N71x/signon-ui-0.17+15.10.20150810'
  dh_auto_test: make -j1 check returned exit code 2
  debian/rules:23: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  :     Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


signon-ui.0.17+15.10.20150810-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#814699: kcompletion: FTBFS: 25% tests passed, 3 tests failed out of 4

[Chris Lamb]

Source: kcompletion
Version: 5.16.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kcompletion fails to build from source in unstable/amd64:

  [..]

  /usr/bin/cmake -E cmake_progress_start 
/home/lamby/temp/cdt.20160214110029.3oA8xYQ1bO/kcompletion-5.16.0/obj-x86_64-linux-gnu/CMakeFiles
 0
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160214110029.3oA8xYQ1bO/kcompletion-5.16.0/obj-x86_64-linux-gnu'
  if ! test -d debian/man/out; then mkdir -p debian/man/out; fi
  for f in $(find debian/man -name '*.sgml'); do \
docbook-to-man $f > debian/man/out/`basename $f .sgml`.1; \
  done
  for f in $(find debian/man -name '*.man'); do \
soelim -I debian/man $f \
> debian/man/out/`basename $f .man`.`head -n1 $f | awk '{print $NF}'`; \
  done
  touch debian/stamp-man-pages
  # Running override target (override_dh_auto_test)
  test -z "`ls debian/*.debhelper.log 2>/dev/null`" || sed -i 
'/^override_dh_auto_test[[:space:]]/d' debian/*.debhelper.log
  /usr/bin/make -f debian/rules override_dh_auto_test 
DH_INTERNAL_OVERRIDE="dh_auto_test"  
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160214110029.3oA8xYQ1bO/kcompletion-5.16.0'
  xvfb-run -a dh_auto_test '--buildsystem=kf5' --parallel 
make -j9 test ARGS\+=-j9
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160214110029.3oA8xYQ1bO/kcompletion-5.16.0/obj-x86_64-linux-gnu'
  Running tests...
  /usr/bin/ctest --force-new-ctest-process -j9
  Test project 
/home/lamby/temp/cdt.20160214110029.3oA8xYQ1bO/kcompletion-5.16.0/obj-x86_64-linux-gnu
  Start 1: kcompletioncoretest
  Start 2: klineedit_unittest
  Start 3: kcombobox_unittest
  Start 4: ksortablelisttest
  1/4 Test #2: klineedit_unittest ...***Exception: Numerical  0.02 
sec
  
  2/4 Test #3: kcombobox_unittest ...***Exception: Numerical  0.02 
sec
  
  3/4 Test #4: ksortablelisttest    Passed0.02 sec
  4/4 Test #1: kcompletioncoretest ..***Exception: Numerical  0.05 
sec
  
  
  25% tests passed, 3 tests failed out of 4
  
  Total Test time (real) =   0.05 sec
  
  The following tests FAILED:
  1 - kcompletioncoretest (NUMERICAL)
  2 - klineedit_unittest (NUMERICAL)
  3 - kcombobox_unittest (NUMERICAL)
  Errors while running CTest
  Makefile:96: recipe for target 'test' failed
  make[3]: *** [test] Error 8
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160214110029.3oA8xYQ1bO/kcompletion-5.16.0/obj-x86_64-linux-gnu'
  dh_auto_test: make -j9 test ARGS+=-j9 returned exit code 2
  debian/rules:12: recipe for target 'override_dh_auto_test' failed
  make[2]: *** [override_dh_auto_test] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160214110029.3oA8xYQ1bO/kcompletion-5.16.0'
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target 
'pre_build_dh_auto_test' failed
  make[1]: *** [pre_build_dh_auto_test] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160214110029.3oA8xYQ1bO/kcompletion-5.16.0'
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target 
'debian/dhmk_build' failed
  make: *** [debian/dhmk_build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


kcompletion.5.16.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#809282: ktp-accounts-kcm: FTBFS: plugins/kaccounts/kaccounts-ui-provider.cpp:109:34: error: 'configUiReady' was not declared in this scope

[Chris Lamb]

-main-options-widget.cpp.o 
CMakeFiles/ktpaccountskcm_plugin_haze.dir/sipe-advanced-settings-widget.cpp.o 
CMakeFiles/ktpaccountskcm_plugin_haze.dir/ktpaccountskcm_plugin_haze_automoc.cpp.o
 ../../src/KCMTelepathyAccounts/libktpaccountskcminternal.so.15.08.3 
/usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0.0.9.6.1 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5Codecs.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigGui.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5Auth.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5ItemViews.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libKF5Service.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5I18n.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libQt5Xml.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.5.1 
-Wl,-rpath,/home/lamby/temp/cdt.20151228235755.r1AIyaFk9e/ktp-accounts-kcm-15.08.3/obj-x86_64-linux-gnu/src/KCMTelepathyAccounts:
 
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20151228235755.r1AIyaFk9e/ktp-accounts-kcm-15.08.3/obj-x86_64-linux-gnu'
  [ 98%] Built target ktpaccountskcm_plugin_haze
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151228235755.r1AIyaFk9e/ktp-accounts-kcm-15.08.3/obj-x86_64-linux-gnu'
  Makefile:141: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151228235755.r1AIyaFk9e/ktp-accounts-kcm-15.08.3/obj-x86_64-linux-gnu'
  dh_auto_build: make -j8 returned exit code 2
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target 
'pre_build_dh_auto_build' failed
  make[1]: *** [pre_build_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151228235755.r1AIyaFk9e/ktp-accounts-kcm-15.08.3'
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target 
'debian/dhmk_build' failed
  make: *** [debian/dhmk_build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
      ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#808740: kuser: FTBFS: dhmk.mk:110: recipe for target 'debian/dhmk_configure' failed

[Chris Lamb]

Source: kuser
Version: 4:4.12.2-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kuser fails to build from source in unstable/amd64:

  [..]

  //ADVANCED property for variable: X11_Xrandr_LIB
  X11_Xrandr_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xrender_INCLUDE_PATH
  X11_Xrender_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xrender_LIB
  X11_Xrender_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xscreensaver_INCLUDE_PATH
  X11_Xscreensaver_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xscreensaver_LIB
  X11_Xscreensaver_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xshape_INCLUDE_PATH
  X11_Xshape_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xt_INCLUDE_PATH
  X11_Xt_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xt_LIB
  X11_Xt_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xutil_INCLUDE_PATH
  X11_Xutil_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xv_INCLUDE_PATH
  X11_Xv_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xv_LIB
  X11_Xv_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_Xxf86misc_LIB
  X11_Xxf86misc_LIB-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_dpms_INCLUDE_PATH
  X11_dpms_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_xf86misc_INCLUDE_PATH
  X11_xf86misc_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: X11_xf86vmode_INCLUDE_PATH
  X11_xf86vmode_INCLUDE_PATH-ADVANCED:INTERNAL=1
  //Test _OFFT_IS_64BIT
  _OFFT_IS_64BIT:INTERNAL=1
  //Test __KDE_HAVE_GCC_VISIBILITY
  __KDE_HAVE_GCC_VISIBILITY:INTERNAL=1
  //Test __KDE_HAVE_W_OVERLOADED_VIRTUAL
  __KDE_HAVE_W_OVERLOADED_VIRTUAL:INTERNAL=1
  //Result of TRY_COMPILE
  _basic_compile_result:INTERNAL=TRUE
  //Result of TRY_COMPILE
  _compile_result:INTERNAL=TRUE
  
  dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_USE_RELATIVE_PATHS=ON returned exit code 1
  /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:97: recipe for target 
'pre_configure_dh_auto_configure' failed
  make[1]: *** [pre_configure_dh_auto_configure] Error 255
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151222120720.xSmIzdRgvf/kuser-4.12.2'
  /usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:110: recipe for target 
'debian/dhmk_configure' failed
  make: *** [debian/dhmk_configure] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


kuser.4:4.12.2-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808621: umbrello: FTBFS: qtestcase.h:293:30: error: cannot convert 'QString' to 'char*' for argument '3' to 'bool QTest::compare_helper(bool, const char*, char*, char*, const char*, const char*, c

[Chris Lamb]

gnu/libKF5ConfigCore.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5SonnetUi.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.5.1 
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20151221145637.utNwdYl7Jw/umbrello-15.08.2/obj-x86_64-linux-gnu'
  [ 99%] Built target TEST_basictypes
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20151221145637.utNwdYl7Jw/umbrello-15.08.2/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:782: recipe for target 
'unittests/CMakeFiles/TEST_pythonwriter.dir/all' failed
  make[3]: *** [unittests/CMakeFiles/TEST_pythonwriter.dir/all] Error 2
  [ 99%] Linking CXX executable TEST_optionstate
  cd 
/home/lamby/temp/cdt.20151221145637.utNwdYl7Jw/umbrello-15.08.2/obj-x86_64-linux-gnu/unittests
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/TEST_optionstate.dir/link.txt --verbose=1
  /usr/bin/c++   -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2  -std=c++0x 
-fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security 
-Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type  -Wl,--enable-new-dtags  -Wl,-z,relro -Wl,--as-needed 
-Wl,--no-undefined CMakeFiles/TEST_optionstate.dir/TEST_optionstate.cpp.o 
CMakeFiles/TEST_optionstate.dir/testbase.cpp.o 
CMakeFiles/TEST_optionstate.dir/TEST_optionstate_automoc.cpp.o  -o 
TEST_optionstate -rdynamic /usr/lib/x86_64-linux-gnu/libQt5Test.so.5.5.1 -lxml2 
-lxslt ../umbrello/libumbrello.a -lxml2 -lxslt 
/usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5Archive.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5Parts.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libKF5TextWidgets.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5Completion.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libQt5Svg.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5Service.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5I18n.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5Auth.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5Codecs.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigGui.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libQt5Xml.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libKF5SonnetUi.so.5.16.0 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.5.1 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.5.1 
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20151221145637.utNwdYl7Jw/umbrello-15.08.2/obj-x86_64-linux-gnu'
  [ 99%] Built target TEST_umlroledialog
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20151221145637.utNwdYl7Jw/umbrello-15.08.2/obj-x86_64-linux-gnu'
  [ 99%] Built target umbrello
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20151221145637.utNwdYl7Jw/umbrello-15.08.2/obj-x86_64-linux-gnu'
  [ 99%] Built target TEST_optionstate
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151221145637.utNwdYl7Jw/umbrello-15.08.2/obj-x86_64-linux-gnu'
  Makefile:141: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151221145637.utNwdYl7Jw/umbrello-15.08.2/obj-x86_64-linux-gnu'
  dh_auto_build: make -j8 returned exit code 2
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target 
'pre_build_dh_auto_build' failed
  make[1]: *** [pre_build_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151221145637.utNwdYl7Jw/umbrello-15.08.2'
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target 
'debian/dhmk_build' failed
  make: *** [debian/dhmk_build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


umbrello.4:15.08.2-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808529: kgamma: FTBFS: Unknown CMake command "check_include_files".

[Chris West (Faux)]

Source: kgamma
Version: 4:4.14.2-1
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

-- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success
-- Performing Test __KDE_HAVE_GCC_VISIBILITY
-- Performing Test __KDE_HAVE_GCC_VISIBILITY - Success
-- Found KDE 4.12 include dir: /usr/include
-- Found KDE 4.12 library dir: /usr/lib
-- Found the KDE4 kconfig_compiler preprocessor: /usr/bin/kconfig_compiler
-- Found automoc4: /usr/bin/automoc4
-- Found X11: /usr/lib/x86_64-linux-gnu/libX11.so
CMake Error at CMakeLists.txt:12 (check_include_files):
  Unknown CMake command "check_include_files".


CMake Warning (dev) in CMakeLists.txt:
  No cmake_minimum_required command is present.  A line of code such as

cmake_minimum_required(VERSION 3.4)

  should be added at the top of the file.  The version specified may be lower
  if you wish to support older CMake versions for this project.  For more
  information run "cmake --help-policy CMP".
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring incomplete, errors occurred!
See also "/kgamma-4.14.2/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
See also "/kgamma-4.14.2/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log".
"tail -v -n +0 CMakeCache.txt"
==> CMakeCache.txt <==
# This is the CMakeCache file.

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/kgamma.html

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

Re: Safe to upgrade?

[Chris Knadle]

Marc Haber:
> On Tue, Dec 08, 2015 at 06:56:45PM +0000, Chris Knadle wrote:
>> Marc Haber:
>>> On Tue, Dec 08, 2015 at 05:31:43PM +, Chris Knadle wrote:
>>>> However just within the last couple of weeks there's been a lot of work on
>>>> the KDE5 packages and Plasma 5 is now usable.
>>>
>>> I still regularly experience plasmashell taking 100 % CPU and needing
>>> a kill + restart. This especially happens over night when the machine
>>> is idling away in the lock screen.
>>
>> Hmmm!  I normally put my computer to sleep or hibernate for the night, so I
>> haven't seen this -- ick.  I wouldn't like to find that.
> 
> Actually, the current behavior is a 100 % improvement over August's
> state of KDE plasma 5 when it was still a complete crash, needing a
> remote login+ kill X to get the machine back after it was left idling
> over night.

Yeah, a couple of months ago I repeatedly had to break out to a text console
with Ctrl-Alt-F2 to restart X when I tried Plasma 5.

> I have not dared to suspend the machine since the KDE Plasma 5 update
> since if the current system doesn't even survive a night of idling,
> how could it possibly survive a suspend+resume cycle?

Well I don't think suspend/resume should break because of Plasma 5 per se;
each of these are supposed to resume to the same memory state and continue
from there.  I'm able to both suspend and hibernate and get back right now;
that's not to say that this works for everybody of course, it's just one
data point.  Only way to know if it works for you is to try it.

>>> I didn't report it yet since I use a locally compiled
>>> plasma-widget-addons with the quick launch widget backported from
>>> plasma 5.5.
>>>
>>> And the volume occasionally jumps up to 100 %, especially when one
>>> clicks on "leave" or does things in System Settings. My neighbors
>>> really love that.
>>
>> I have this "volume jumps to 100%" issue, but in my case it's a self-made
>> thing -- in my ~/.bashrc I have this:
>>
>># Restore local ALSA mixer settings
>>/usr/sbin/alsactl --file ~/.config/asound.state restore
> 
> Not in my case.

Yes, I assumed not.  The main reason I mentioned the above is a) it means if
I've ever had the same thing happen the data is convoluted with the running
of the alsactrl restore, b) just in case you might have done something
similar and had forgotten (I didn't think this likely).

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Re: Safe to upgrade?

[Chris Knadle]

Hey, Tim.

Tim Folger:
> Hi,
> 
> I'm running debian testing, with kde version 4.14.2, Given some of the 
> problems I've seen posted on this list, I've been hesitating to upgrade to 
> Plasma 5. What's the state of plasma 5 now in testing? Is it generally safe 
> to 
> upgrade?
> 
> Thanks for any input.

I've been occasionally trying Plasma 5 for many weeks in Sid/Unstable, so
I'll mention some of my observations.

Early versions of Plasma 5 were unusable -- far too quirky and unstable for
me to want to use.  I repeatedly experienced crashes of Konsole, the plasma
Panel, crashes that would bring me back to the login screen -- etc.  Way too
frustrating to use day-to-day.

Downgrading to KDE4 wasn't a good option because it required downgrading a
lot of other packages, and being that I'm on Sid/Unstable this wasn't a good
option -- so I had little choice but to use another Window Manger.
I settled on MATE.  I tried to use Konsole within MATE because when it works
I find Konsole more convenient -- for instance Alt- keyrpesses pass
through Konsole for switching channels in Irssi, but get caught by the MATE
terminal because in MATE terminal they're shortcuts for switching terminal
tabs, and re-assigning those shortcuts doesn't seem to let the keypresses
pass through.  Unfortunately Konsole under MATE was too unstable to use too.

However just within the last couple of weeks there's been a lot of work on
the KDE5 packages and Plasma 5 is now usable.  I still occasionally have
Konsole crash on me, and it as well as SystemSettings reliably Segfault on
closing -- but although it's not 100% it's to a point I can tolerate.  I've
loaded a lot of -dbg packages to try to track down the Segfaults, but so far
the results look more confusing than helpful... we'll see how that goes.

So before "making the jump", I'd suggest loading up a VM with Debian Testing
and trying Plasma 5 that way first.  You might find you're able to deal with
it (I suspect you might find it okay), but if not it will be a somewhat
painful downgrade.

  -- Chris

-- 
Chris Knadle, DM
chris.kna...@coredump.us

Re: Safe to upgrade?

[Chris Knadle]

Marc Haber:
> On Tue, Dec 08, 2015 at 05:31:43PM +0000, Chris Knadle wrote:
>> However just within the last couple of weeks there's been a lot of work on
>> the KDE5 packages and Plasma 5 is now usable.
> 
> I still regularly experience plasmashell taking 100 % CPU and needing
> a kill + restart. This especially happens over night when the machine
> is idling away in the lock screen.

Hmmm!  I normally put my computer to sleep or hibernate for the night, so I
haven't seen this -- ick.  I wouldn't like to find that.

> I didn't report it yet since I use a locally compiled
> plasma-widget-addons with the quick launch widget backported from
> plasma 5.5.
> 
> And the volume occasionally jumps up to 100 %, especially when one
> clicks on "leave" or does things in System Settings. My neighbors
> really love that.

I have this "volume jumps to 100%" issue, but in my case it's a self-made
thing -- in my ~/.bashrc I have this:

   # Restore local ALSA mixer settings
   /usr/sbin/alsactl --file ~/.config/asound.state restore

... so every time I open up a new terminal window, .bashrc gets invoked and
the ALSA mixer settings get reset back to what was last stored.

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Bug#803381: step: FTBFS: error: #error Eigen2-support is only available up to version 3.2.

[Chris Lamb]

Source: step
Version: 4:15.08.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

step fails to build from source in unstable/amd64:

  [..]

  [ 17%] Building CXX object
  stepcore/CMakeFiles/stepcore.dir/itemgroup.cc.o
  cd stepcore && /usr/bin/c++  
  -DEIGEN2_SUPPORT_STAGE40_FULL_EIGEN3_STRICTNESS -DQT_CORE_LIB
  -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_NO_DEBUG -DQT_XML_LIB
  -DSTEPCORE_WITH_GSL -DSTEPCORE_WITH_QT -D_GNU_SOURCE
  -D_LARGEFILE64_SOURCE -g -O2 -fstack-protector-strong -Wformat
  -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 
  -std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align
  -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith
  -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type
  -Wno-unused-local-typedefs -Wno-unused-parameter -I. -I../../stepcore
  -I../../ -I/usr/include/eigen3 -isystem
  /usr/include/x86_64-linux-gnu/qt5 -isystem
  /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
  /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem
  /usr/include/x86_64-linux-gnu/qt5/QtXml-Wall -fPIC -o
  CMakeFiles/stepcore.dir/itemgroup.cc.o -c ../../stepcore/itemgroup.cc
  In file included from ../../stepcore/object.h:29:0,
   from ../../stepcore/types.h:26,
   from ../../stepcore/itemgroup.h:30,
   from ../../stepcore/itemgroup.cc:20:
  /usr/include/eigen3/Eigen/Core:275:2: error: #error Eigen2-support is
  only available up to version 3.2. Please go to
  "http://eigen.tuxfamily.org/index.php?title=Eigen2; for further
  information
   #error Eigen2-support is only available up to version 3.2. Please go
   to "http://eigen.tuxfamily.org/index.php?title=Eigen2; for further
   information
^
  stepcore/CMakeFiles/stepcore.dir/build.make:161: recipe for target
  'stepcore/CMakeFiles/stepcore.dir/body.cc.o' failed
  make[4]: *** [stepcore/CMakeFiles/stepcore.dir/body.cc.o] Error 1
  make[4]: *** Waiting for unfinished jobs
  stepcore/CMakeFiles/stepcore.dir/build.make:113: recipe for target
  'stepcore/CMakeFiles/stepcore.dir/object.cc.o' failed
  make[4]: *** [stepcore/CMakeFiles/stepcore.dir/object.cc.o] Error 1
  stepcore/CMakeFiles/stepcore.dir/build.make:185: recipe for target
  'stepcore/CMakeFiles/stepcore.dir/objecterrors.cc.o' failed
  make[4]: *** [stepcore/CMakeFiles/stepcore.dir/objecterrors.cc.o]
  Error 1
  stepcore/CMakeFiles/stepcore.dir/build.make:89: recipe for target
  'stepcore/CMakeFiles/stepcore.dir/material.cc.o' failed
  make[4]: *** [stepcore/CMakeFiles/stepcore.dir/material.cc.o] Error 1
  stepcore/CMakeFiles/stepcore.dir/build.make:137: recipe for target
  'stepcore/CMakeFiles/stepcore.dir/item.cc.o' failed
  make[4]: *** [stepcore/CMakeFiles/stepcore.dir/item.cc.o] Error 1
  stepcore/CMakeFiles/stepcore.dir/build.make:209: recipe for target
  'stepcore/CMakeFiles/stepcore.dir/force.cc.o' failed
  make[4]: *** [stepcore/CMakeFiles/stepcore.dir/force.cc.o] Error 1
  stepcore/CMakeFiles/stepcore.dir/build.make:233: recipe for target
  'stepcore/CMakeFiles/stepcore.dir/joint.cc.o' failed
  make[4]: *** [stepcore/CMakeFiles/stepcore.dir/joint.cc.o] Error 1
  stepcore/CMakeFiles/stepcore.dir/build.make:257: recipe for target
  'stepcore/CMakeFiles/stepcore.dir/itemgroup.cc.o' failed
  make[4]: *** [stepcore/CMakeFiles/stepcore.dir/itemgroup.cc.o] Error 1
  make[4]: Leaving directory
  
'/home/lamby/temp/cdt.20151029132431.ygtbS1EbWf/step-15.08.0/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:208: recipe for target
  'stepcore/CMakeFiles/stepcore.dir/all' failed
  make[3]: *** [stepcore/CMakeFiles/stepcore.dir/all] Error 2
  make[3]: Leaving directory
  
'/home/lamby/temp/cdt.20151029132431.ygtbS1EbWf/step-15.08.0/obj-x86_64-linux-gnu'
  Makefile:141: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory
  
'/home/lamby/temp/cdt.20151029132431.ygtbS1EbWf/step-15.08.0/obj-x86_64-linux-gnu'
  dh_auto_build: make -j8 returned exit code 2
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target
  'pre_build_dh_auto_build' failed
  make[1]: *** [pre_build_dh_auto_build] Error 2
  make[1]: Leaving directory
  '/home/lamby/temp/cdt.20151029132431.ygtbS1EbWf/step-15.08.0'
  /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target
  'debian/dhmk_build' failed
  make: *** [debian/dhmk_build] Error 2

  [..]

The full build log is attached or (an alternate build) can be viewed
here:


https://reproducible.debian.net/logs/unstable/amd64/step_15.08.0-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


step.4:15.08.0-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#802861: kalzium: FTBFS: gasCalculator.h: error: expected unqualified-id before numeric constant

[Chris West (Faux)]

Source: kalzium
Version: 4:15.08.0-1
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

In file included from ../../src/calculator/calculator.h:27:0,
 from ../../src/kalzium.h:24,
 from ../../src/kalzium.cpp:13:
/usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h: In 
member function ‘void Eigen::internal::gebp_kernel::operator()(const DataMapper&, 
const LhsScalar*, const RhsScalar*, Index, Index, Index, 
Eigen::internal::gebp_kernel::ResScalar, Index, Index, Index, Index)’:
../../src/calculator/gasCalculator.h:31:11: error: expected unqualified-id 
before numeric constant
 #define R 0.08206
   ^
../../src/calculator/gasCalculator.h:31:11: error: expected unqualified-id 
before numeric constant
 #define R 0.08206
   ^
src/CMakeFiles/kalzium.dir/build.make:736: recipe for target 
'src/CMakeFiles/kalzium.dir/kalzium.o' failed
make[4]: *** [src/CMakeFiles/kalzium.dir/kalzium.o] Error 1
make[4]: Leaving directory '/kalzium-15.08.0/obj-x86_64-linux-gnu'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/kalzium.html

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

Bug#802107: phonon-backend-gstreamer: FTBFS: gst/gstconfig.h: No such file or directory

[Chris West (Faux)]

Source: phonon-backend-gstreamer
Version: 4:4.8.2-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

Generating moc_glrenderer.cpp
make[5]: Leaving directory '/phonon-backend-gstreamer-4.8.2/obj-qt4'
[  4%] Built target phonon_gstreamer_automoc
make -f gstreamer/CMakeFiles/phonon_gstreamer.dir/build.make 
gstreamer/CMakeFiles/phonon_gstreamer.dir/depend
make[5]: Entering directory '/phonon-backend-gstreamer-4.8.2/obj-qt4'
cd /phonon-backend-gstreamer-4.8.2/obj-qt4 && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /phonon-backend-gstreamer-4.8.2 
/phonon-backend-gstreamer-4.8.2/gstreamer 
/phonon-backend-gstreamer-4.8.2/obj-qt4 
/phonon-backend-gstreamer-4.8.2/obj-qt4/gstreamer 
/phonon-backend-gstreamer-4.8.2/obj-qt4/gstreamer/CMakeFiles/phonon_gstreamer.dir/DependInfo.cmake
 --color=
Scanning dependencies of target phonon_gstreamer
make[5]: Leaving directory '/phonon-backend-gstreamer-4.8.2/obj-qt4'
make -f gstreamer/CMakeFiles/phonon_gstreamer.dir/build.make 
gstreamer/CMakeFiles/phonon_gstreamer.dir/build
make[5]: Entering directory '/phonon-backend-gstreamer-4.8.2/obj-qt4'
[  8%] Building CXX object 
gstreamer/CMakeFiles/phonon_gstreamer.dir/abstractrenderer.cpp.o
cd gstreamer && /usr/bin/c++   -DPHONON_BACKEND_VERSION_4_7 
-DPHONON_EXPERIMENTAL -DPHONON_GST_VERSION=\"4.8.2\" -DPHONON_NO_GRAPHICSVIEW 
-D_BSD_SOURCE -Dphonon_gstreamer_EXPORTS -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2  
-Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall 
-W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS 
-fno-check-new -fno-common -Woverloaded-virtual -fvisibility=hidden 
-Werror=return-type -fvisibility-inlines-hidden -Wnon-virtual-dtor 
-Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W 
-Wpointer-arith -Wformat-security -fno-check-new -fno-common -fPIC -I. 
-I../../gstreamer -I/usr/include/KDE -I/usr/include/phonon 
-I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative 
-I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtDBus 
-I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtOpenGL 
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/phonon 
-I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtHelp 
-I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest 
-I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg 
-I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui 
-I/usr/include/qt4/QtCore -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2-o 
CMakeFiles/phonon_gstreamer.dir/abstractrenderer.cpp.o -c 
../../gstreamer/abstractrenderer.cpp
In file included from ../../gstreamer/abstractrenderer.h:21:0,
 from ../../gstreamer/abstractrenderer.cpp:18:
/usr/include/gstreamer-1.0/gst/gstelement.h:55:27: fatal error: 
gst/gstconfig.h: No such file or directory
compilation terminated.
gstreamer/CMakeFiles/phonon_gstreamer.dir/build.make:65: recipe for target 
'gstreamer/CMakeFiles/phonon_gstreamer.dir/abstractrenderer.cpp.o' failed
make[5]: *** [gstreamer/CMakeFiles/phonon_gstreamer.dir/abstractrenderer.cpp.o] 
Error 1
make[5]: Leaving directory '/phonon-backend-gstreamer-4.8.2/obj-qt4'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/phonon-backend-gstreamer.html

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

Bug#799992: kmix: FTBFS: The dependency target "kmixctrl_automoc" of target "kmixctrl" does not exist

[Chris Lamb]

Source: kmix
Version: 15.08.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kmix fails to build from source in unstable/amd64:

  [..]
  
  -- Configuring done
  CMake Error at /usr/lib/automoc4/Automoc4Config.cmake:248
  (add_dependencies):
The dependency target "kmixctrl_automoc" of target "kmixctrl" does
not
exist.
  Call Stack (most recent call first):
/usr/share/kde4/apps/cmake/modules/KDE4Macros.cmake:1036
(_automoc4_kde4_post_target_handling)
/usr/share/kde4/apps/cmake/modules/KDE4Macros.cmake:843
(kde4_add_executable)
CMakeLists.txt:352 (kde4_add_kdeinit_executable)
  
  
  CMake Error at /usr/lib/automoc4/Automoc4Config.cmake:248
  (add_dependencies):
The dependency target "kmix_automoc" of target "kmix" does not
exist.
  Call Stack (most recent call first):
/usr/share/kde4/apps/cmake/modules/KDE4Macros.cmake:1036
(_automoc4_kde4_post_target_handling)
/usr/share/kde4/apps/cmake/modules/KDE4Macros.cmake:843
(kde4_add_executable)
CMakeLists.txt:230 (kde4_add_kdeinit_executable)
  
  
  -- Generating done
  CMake Warning:
Manually-specified variables were not used by the project:
  
  CMAKE_INSTALL_SYSCONFDIR
  KDE_INSTALL_USE_QT_SYS_PATHS
  
  
  -- Build files have been written to:
  /tmp/buildd/kmix-15.08.1/obj-x86_64-linux-gnu
  dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr
  -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None
  -DCMAKE_BUILD_TYPE=Debian -DCMAKE_USE_RELATIVE_PATHS=ON
  -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON
  -DKMIX_KF5_BUILD=0 returned exit code 1
  debian/rules:6: recipe for target 'override_dh_auto_configure' failed

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/kmix_15.08.1-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Sep 19 14:51:58 GMT+12 2015
I: pbuilder-time-stamp: 1442717518
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team <pbuilder-ma...@lists.alioth.debian.org>
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: cmake (>= 2.8.12~), debhelper (>= 9), kde-sc-dev-latest (>= 4:4.12), 
kdelibs5-dev (>= 4:4.14), libasound2-dev, libcanberra-dev, libglib2.0-dev, 
libpulse-dev (>= 0.9.16), pkg-kde-tools (>= 0.12)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20256 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on cmake (>= 2.8.12~); however:
  Package cmake is not installed.
 pbuilder-satisfydepends-dummy depends on kde-sc-dev-latest (>= 4:4.12); 
however:
  Package kde-sc-dev-latest is not installed.
 pbuilder-satisfydepends-dummy depends on kdelibs5-dev (>= 4:4.14); however:
  Package kdelibs5-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libasound2-dev; however:
  Package libasound2-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libcanberra-dev; however:
  Package libcanberra-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libglib2.0-dev; however:
  Package libglib2.0-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libpulse-dev (>= 0.9.16); however:
  Package libpulse-dev is not installed.
 pbuilder-satisfydepends-dummy depends on pkg-kde-tools (>= 0.12); however:
  Package pkg-kde-tools is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing

Bug#799521: umbrello: FTBFS: Missing Build-Depends on libsoprano-dev

[Chris Lamb]

Source: umbrello
Version: 4:4.14.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

umbrello fails to build from source due to missing Build-Depends on
libsoprano-dev. This was previously pulled-in via a transitive
relationship.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#799519: svgpart: FTBFS: Missing Build-Depends on libsoprano-dev

[Chris Lamb]

Source: svgpart
Version: 4:4.11.3-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

svgpart fails to build from source due to missing Build-Depends on
libsoprano-dev. This was previously pulled-in via a transitive
relationship.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#799506: konsole4: FTBFS: Missing Build-Depends on libsoprano-dev

[Chris Lamb]

Source: konsole4
Version: 4:4.14.2-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

konsole4 fails to build from source due to missing Build-Depends on
libsoprano-dev. This was previously pulled-in via a transitive
relationship.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#799496: kde-baseapps: FTBFS: Missing Build-Depends on libsoprano-dev

[Chris Lamb]

Source: kde-baseapps
Version: 4:15.04.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kde-baseapps fails to build from source due to missing Build-Depends on
libsoprano-dev. This was previously pulled-in via a transitive
relationship.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#799494: kalgebra: FTBFS: Missing Build-Depends on libsoprano-dev

[Chris Lamb]

Source: kalgebra
Version: 4:4.14.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kalgebra fails to build from source due to missing Build-Depends on
libsoprano-dev. This was previously pulled-in via a transitive
relationship.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#799490: cervisia: FTBFS: Missing Build-Depends on libsoprano-dev

[Chris Lamb]

Source: cervisia
Version: 4:4.14.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

cervisia fails to build from source due to missing Build-Depends on
libsoprano-dev. This was previously pulled-in via a transitive
relationship.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#799499: kdevelop-php-docs: FTBFS: Missing Build-Depends on libsoprano-dev

[Chris Lamb]

Source: kdevelop-php-docs
Version: 1.7.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kdevelop-php-docs fails to build from source due to missing
Build-Depends on libsoprano-dev. This was previously pulled-in via a
transitive relationship.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#799500: kdewebdev: FTBFS: Missing Build-Depends on libsoprano-dev

[Chris Lamb]

Source: kdewebdev
Version: 4:4.14.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kdewebdev fails to build from source due to missing Build-Depends on
libsoprano-dev. This was previously pulled-in via a transitive
relationship.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#799497: kde-dev-utils: FTBFS: Missing Build-Depends on libsoprano-dev

[Chris Lamb]

Source: kde-dev-utils
Version: 4:4.12.2-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

kde-dev-utils fails to build from source due to missing Build-Depends on
libsoprano-dev. This was previously pulled-in via a transitive
relationship.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#799450: soprano: Causing FTBFS in reverse Build-Depends? ("No rule to make target '/usr/lib/libsoprano.so')

[Chris Lamb]

merge 799450 799362 799360
thanks

(Merging these other bugs so there's some link on their page)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-