Your message dated Sun, 15 May 2022 16:34:23 +0000
with message-id <e1nqhcj-000hsf...@fasolo.debian.org>
and subject line Bug#1011019: fixed in telegram-desktop 3.7.3+ds-2
has caused the Debian Bug report #1011019,
regarding telegram-desktop FTBFS with libkf5wayland-dev 5.93.0
to be marked as done.

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

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


-- 
1011019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkf5wayland-dev
Version: 4:5.93.0-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:peony src:telegram-desktop

https://buildd.debian.org/status/logs.php?pkg=peony&ver=3.2.4-2%2Bb1

...
In file included from main.cpp:24:
waylandoutputmanager.h:28:10: fatal error: KWayland/Client/xdgoutput.h: No such 
file or directory
   28 | #include <KWayland/Client/xdgoutput.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...


https://buildd.debian.org/status/logs.php?pkg=telegram-desktop&ver=3.7.3%2Bds-1%2Bb1

...
/<<PKGBUILDDIR>>/Telegram/lib_base/base/platform/linux/base_linux_wayland_integration.cpp:16:10:
 fatal error: connection_thread.h: No such file or directory
   16 | #include <connection_thread.h>
      |          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [Telegram/lib_base/CMakeFiles/lib_base.dir/build.make:224: 
Telegram/lib_base/CMakeFiles/lib_base.dir/base/platform/linux/base_linux_wayland_integration.cpp.o]
 Error 1



Both issues can be "fixed" by downgrading libkf5wayland-dev to 4:5.90.0-1

--- End Message ---
--- Begin Message ---
Source: telegram-desktop
Source-Version: 3.7.3+ds-2
Done: Nicholas Guriev <guriev...@ya.ru>

We believe that the bug you reported is fixed in the latest version of
telegram-desktop, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1011...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicholas Guriev <guriev...@ya.ru> (supplier of updated telegram-desktop package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 15 May 2022 19:04:08 +0300
Source: telegram-desktop
Architecture: source
Version: 3.7.3+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Nicholas Guriev <guriev...@ya.ru>
Changed-By: Nicholas Guriev <guriev...@ya.ru>
Closes: 1011019
Changes:
 telegram-desktop (3.7.3+ds-2) unstable; urgency=medium
 .
   * New Include-KWayland.patch fixes build against the updated dependency.
     (Closes: #1011019)
Checksums-Sha1:
 5776883871a482c7f5771c02106d440d97b636c0 2567 telegram-desktop_3.7.3+ds-2.dsc
 a42b33d796c3ce811d76b5d172b3fd8fe6ddfa87 28200 
telegram-desktop_3.7.3+ds-2.debian.tar.xz
Checksums-Sha256:
 4510d1b14e7d73dbf5b22ab8ae27ec160e4b6fc285aba0d60d4125005bb98b43 2567 
telegram-desktop_3.7.3+ds-2.dsc
 e9497e85b8c703292648160be42fee51c2f40e07109eb69719ba4e6d06fddbe4 28200 
telegram-desktop_3.7.3+ds-2.debian.tar.xz
Files:
 497b4a07b838f1f78c40d64e7fb5fd08 2567 net optional 
telegram-desktop_3.7.3+ds-2.dsc
 f3b2c01010a9f74efd5013c4d60874d6 28200 net optional 
telegram-desktop_3.7.3+ds-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iIYEARYIAC4WIQQRm7llN8yxifaG60cF2qh9JI3wlQUCYoEn0BAcZ3VyaWV2LW5z
QHlhLnJ1AAoJEAXaqH0kjfCVAg4A/3cZ2zwtOyKGT86nfAmBF790ZroJmndMcH9J
DhLYTDTpAPwJmoUj32JlfBndfzUnNhoa95eGY0mHldpNfpVQLUM0Dw==
=ZnVw
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to