Bug#921909: QCachegrind is not being packaged in KCachegrind 17
Package: qcachegrind Version: 4:17.08.3-2 Severity: important Dear Maintainer, QCachegrind is KCachegrind built without a KDE dependency. It is compiled as part of the KCachegrind build process, but not installed by default. It was packaged in Debian as part of KCachegrind 16 and present in stretch: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836937 However, it seems to have gotten lost when KCachegrind 17 was packaged. This means that QCachegrind is currently missing from buster and sid. Please resume building the QCachegrind binary package. https://tracker.debian.org/news/817634/accepted-kcachegrind-416083-1-source-into-unstable/ https://tracker.debian.org/news/872010/accepted-kcachegrind-417081-1-source-all-amd64-into-experimental/ Thank you. -nandhp -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
md4c_0.2.7+git17-gb9fcd47-1_amd64.changes is NEW
binary:libmd4c-dev is NEW. binary:libmd4c0 is NEW. binary:libmd4c-dev is NEW. binary:libmd4c0 is NEW. source:md4c is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Processing of md4c_0.2.7+git17-gb9fcd47-1_amd64.changes
md4c_0.2.7+git17-gb9fcd47-1_amd64.changes uploaded successfully to localhost along with the files: md4c_0.2.7+git17-gb9fcd47-1.dsc md4c_0.2.7+git17-gb9fcd47.orig.tar.xz md4c_0.2.7+git17-gb9fcd47-1.debian.tar.xz libmd4c-dev_0.2.7+git17-gb9fcd47-1_amd64.deb libmd4c0-dbgsym_0.2.7+git17-gb9fcd47-1_amd64.deb libmd4c0_0.2.7+git17-gb9fcd47-1_amd64.deb md4c_0.2.7+git17-gb9fcd47-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
Hello Adrian, maybe one of the installed source files lead to a bad gschemas.compiled file? Could you create a file with the md5sums of all the xml files that seem to get combined into that gschemas.compiled file. md5sum /usr/share/glib-2.0/schemas/* > ~/usr-share-glib-2.0-schemas-md5sums.txt Also you may attach the gschemas.compiled too? Kind regards, Bernhard
Processed: Re: sddm-theme-debian-maui: Maui decorations are missing after recent upgrades
Processing control commands: > reassign -1 desktop-base 10.0.0 Bug #921552 [sddm-theme-debian-maui] sddm-theme-debian-maui: Maui decorations are missing after recent upgrades Bug reassigned from package 'sddm-theme-debian-maui' to 'desktop-base'. No longer marked as found in versions sddm/0.18.0-1. Ignoring request to alter fixed versions of bug #921552 to the same values previously set Bug #921552 [desktop-base] sddm-theme-debian-maui: Maui decorations are missing after recent upgrades Marked as found in versions desktop-base/10.0.0. > severity -1 minor Bug #921552 [desktop-base] sddm-theme-debian-maui: Maui decorations are missing after recent upgrades Severity set to 'minor' from 'normal' > merge -1 921678 Bug #921552 [desktop-base] sddm-theme-debian-maui: Maui decorations are missing after recent upgrades Bug #921552 [desktop-base] sddm-theme-debian-maui: Maui decorations are missing after recent upgrades Added tag(s) pending. Bug #921678 [desktop-base] sddm-theme-debian-maui: After a recent system update the file background-nologo.svg disappeared Merged 921552 921678 -- 921552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921552 921678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921552: sddm-theme-debian-maui: Maui decorations are missing after recent upgrades
Control: reassign -1 desktop-base 10.0.0 Control: severity -1 minor Control: merge -1 921678 This is actually a bug with the new "futurePrototype" theme in desktop-base, to be fixed in an imminent upload. Kind regards -Steven
Processing of kopete_17.08.3-2.1_source.changes
kopete_17.08.3-2.1_source.changes uploaded successfully to localhost along with the files: kopete_17.08.3-2.1.dsc kopete_17.08.3-2.1.debian.tar.xz kopete_17.08.3-2.1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#916151: Fix, NMU
user debian-rele...@lists.debian.org usertag 916151 + bsp-2019-02-de-berlin usertag 920358 + bsp-2019-02-de-berlin thank you Dear maintainers, Greetings from the BSP at the DCSO office in Berlin. I have fixed this bug and NMU'd kopete/17.08.3-2.1 to DELAYED/2. Please feel free to reschedule or cancel my upload as you see fit. I have attached the diff. Cheers, -Hilko >From 0f24a751b7acc0952152739a5398c8140f02c098 Mon Sep 17 00:00:00 2001 From: Hilko Bengen Date: Sat, 9 Feb 2019 14:43:38 +0100 Subject: [PATCH] Add missing include, fixing FTBFS with glibc 2.28 (Closes: #916151, #920358) --- debian/changelog | 8 debian/patches/fix-glibc2.28-ftbfs.patch | 12 debian/patches/series| 1 + 3 files changed, 21 insertions(+) create mode 100644 debian/patches/fix-glibc2.28-ftbfs.patch diff --git a/debian/changelog b/debian/changelog index 8419975..af578c8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +kopete (4:17.08.3-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add missing include, fixing FTBFS with glibc 2.28 (Closes: #916151, +#920358) + + -- Hilko Bengen Sat, 09 Feb 2019 12:53:00 +0100 + kopete (4:17.08.3-2) unstable; urgency=medium * Team upload. diff --git a/debian/patches/fix-glibc2.28-ftbfs.patch b/debian/patches/fix-glibc2.28-ftbfs.patch new file mode 100644 index 000..9287177 --- /dev/null +++ b/debian/patches/fix-glibc2.28-ftbfs.patch @@ -0,0 +1,12 @@ +Index: kopete/protocols/jabber/libjingle/talk/session/phone/v4llookup.cc +=== +--- kopete.orig/protocols/jabber/libjingle/talk/session/phone/v4llookup.cc kopete/protocols/jabber/libjingle/talk/session/phone/v4llookup.cc +@@ -15,6 +15,7 @@ + #include + #include + #include ++#include + #include + + #include diff --git a/debian/patches/series b/debian/patches/series index 03598d1..41cc671 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1,3 +1,4 @@ kopete-17.08.3-openssl-1.1.patch fix-mediastreamer-ftbfs.patch kopete-srtp2.patch +fix-glibc2.28-ftbfs.patch -- 2.19.1
Re: akonadi-backend-mysql installs the mariadb service
Dear Yannick.
Yannick Roehlly - 09.02.19, 10:40:
> The akonadi-backend-mysql package changed its dependency from
> default-mysql- server-core to default-mysql-server.
>
> That means that is automatically installs a mariadb service. What was
> the problem with depending on the core package that only contains the
> binaries and does not launch the service ?
Just read the changelog.
Debian Bug report logs - #921389
akonadi-backend-mysql: akonadi fails to start creating new database/
config - ~/.local/share/akonadi/db_data/ not created
As soon as the core package again contain what is necessary, the work-
can be removed again.
akonadi (4:18.08.3-2) unstable; urgency=medium
* Team upload.
[ Sandro Knauß ]
* Rename {kubuntu_,}disable_secure_file_priv_check.diff.
* Update symbols from buildds for 4:18.08.3
[ Alf Gaida ]
* Replaced wrapper mysqld-akonadi with link mysqld -> mysqld-akonadi
(Closes: #921389)
* Replaced dependency for akonadi-backend-mysql:
- default-mysql-server-core -> default-mysql-server
- virtual-mysql-server-core -> virtual-mysql-server
-- Sandro Knauß <[…]> Wed, 06 Feb 2019 12:56:58 +0100
Thanks,
--
Martin
akonadi-backend-mysql installs the mariadb service
Hi, The akonadi-backend-mysql package changed its dependency from default-mysql- server-core to default-mysql-server. That means that is automatically installs a mariadb service. What was the problem with depending on the core package that only contains the binaries and does not launch the service ? Regards, Yannick -- Your time is limited, so don't waste it living someone else's life -- Steve Jobs (1955-2011)
Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
Dear Bernhard, thank you for your message. I have in fact installed gschemas.compiled: root@g6 (/usr/share/glib-2.0/schemas) % ls -la |grep compiled -rw-r--r-- 1 root root 557484 Feb 9 08:34 gschemas.compiled I tried setting the environment variable in /etc/environment which did not fix the issue. Still I can't login to a GNOME session from sddm or start any GTK/GNOME application when logging in to another window manager like FVWM. The shell says core dumped when trying to launch gedit for example. I have installed gesettings-desktop-schemas version: root@g6 (/usr/share/glib-2.0/schemas) % dpkg -l | grep gsettings-desktop-schemas ii gsettings-desktop-schemas 3.28.1-1 all GSettings desktop-wide schemas ii gsettings-desktop-schemas-dev:amd64 3.28.1-1 amd64Development files for GSettings desktop-wide schemas Do you now have an idea how to fix this bug? Thank you very much in advance. Yours sincerely, Adrian -- With many greetings from Leipzig, Germany. Adrian Immanuel Kieß Gothaer Straße 34 D-04155 Leipzig Administrator & programmer Unix ∧ Perl ∧ Java ∧ LaTeX 📪 — < adr...@kiess.onl > 🌍 — https://www.kiess.onl # Dem Ingenieur ist nichts zu schwör ☕ — https://arosusi.kiess.onl # Nickpage of Adrian Immanuel Kieß 🐇 — https://outanekka.kiess.onl # Outanekka online imagery --SYSTEM-- echo "Your fortune cookie: " && /usr/games/fortune -c -s > (work) % Please keep your hands off the secretary's reproducing equipment. echo "KIESS.ONL uptime: " && /usr/bin/uptime > 09:55:54 up 14 min, 2 users, load average: 1.26, 0.80, 0.45 On Mon, 2019-02-04 at 23:44 +0100, Bernhard Übelacker wrote: > Control: tags 920139 + moreinfo > > > Hello Adrian, > > Am 03.02.19 um 09:24 schrieb Adrian Immanuel Kiess: > > The bug is, like I see it, that the applications cannot find the > > gsettings schema directory. > > From my point of view it might be more the file gschemas.compiled > inside that directory. Does that exist on your system? > > > When setting export GSETTINGS_SCHEMA_DIR="/usr/share/glib- > > 2.0/schemas/" > > in my .xinitrc I can launch GTK and GNOME applications when the > > xsession ist started with startx. > > > > Therefor setting GSETTINGS_SCHEMA_DIR in /etc/environment maybe > > fixes > > the issue, which I have not tried yet. > > My previous test was inside a minimal buster amd64 VM where I > installed > just "systemd-coredump xserver-xorg sddm gnome-session" and there I > can > login in sddm to a "GNOME on Xorg" session without showing that > problem. > I searched that VM and could find no file setting that environment. > > I tried renaming that file gschemas.compiled and setting the > environment > like you did - but I still got the trap. > > Therefore you might also install a coredump collector > like systemd-coredump. > That way after such an unsuccessful logon attempt you can list with: > > coredumpctl list > > And produce an exact backtrace in which function that error is > thrown by this command: > > coredumpctl gdb [PID] > bt > > Best would be if debug symbol packages > gnome-session-bin-dbgsym libglib2.0-0-dbgsym > are installed like described in [1]. > > > Shall I resubmit the bug against gsettings-desktop-schemas package? > > If you mean with resumit to create a new bug, that should not be > needed > as this bug can be reassigned to another package too. > Which version of package gsettings-desktop-schemas have you > installed? > > dpkg -l | grep gsettings-desktop-schemas > > Kind regards, > Bernhard > > [1] > https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols signature.asc Description: This is a digitally signed message part
Bug#905697: Info received (Bug#905697: kdepimlibs: don't depend on libical)
I think the only API change that's relevant might be: is_utc to icaltime_is_utc() in icaltimetype For anyonne with a non-trivial C++ knowledge (i.e. not me), I suspect this wouldn't be too hard. Scott K
