Bug#931750: telegram-desktop: Packace uninstallable due to alleged lack of dependency
It happens because you've installed some packages from the experimental repository where Telegram Desktop was built against Qt 5.11.3. Now you have to downgrade version of libqt5core5a. Install it from stable repo, for example. Also I would recommend you to decrease priority of the experimental repository.
Bug#926218: range-v3: FTBFS with gcc 8.3
Alexis Murzeau, thank you very much for the investigation. Then we can ignore that warning in a good conscience. To avoid "unrecognized command line option" errors, I've rewritten the ranges_append_flag macro used by CMake.
Bug#904133: t-d ftbfs with memory exhaustion on many targets
Hi, 20.07.2018 14:38, Matthias Klose пишет: > the package ftbfs at least on armel, and mips* in Debian It failed to build due to a missing linker option, -latomic. The fix is already available[1], but an issue is that the option may add an unneeded dependency. > Did you make any measurements how much better the code is with -flto? I'm > unsure if it's worth the trouble for a desktop application. Deactivation of LTO leads to more memory consumption during compilation. At least at my laptop building process without -flto requires 5.81 GB of virtual memory, takes two and a half hours and produces a binary of 29.7 MB size. In current state, building of the package requires 4.97 GB of virtual memory, takes about one hour and produces a binary of 23.2 MB size. To be honest, I have the laptop with 4 GB of RAM, so such a long time in the first case is understandable. Obviously, without LTO, results are less good, but we can try to disable link-time optimizations as an experiment. [1]: https://salsa.debian.org/debian/telegram-desktop/commit/d922c6628f2ee56bf3e896db64f20c41352d8246
Bug#926218: range-v3: FTBFS with gcc 8.3
Control: forwarded -1 https://github.com/ericniebler/range-v3/issues/856 Hi! Thank you for the report! Which hardware architecture do you use to build the package? There is something similar in upstream bug tracker.
Bug#940938: telegram-desktop: Could not start Telegram Desktop!
Severity: minor Tags: moreinfo Hi! 22.09.2019 12:41, Utkarsh Gupta пишет: > [2019.09.22 15:07:08] FATAL: Could not move logging to > '/home/utkarsh2102/.local/share/TelegramDesktop/log.txt'! Please check that Telegram can write to this file, especially that it isn't immutable. See lsattr(1), flag 'i'. Telegram Desktop needs its working directory to be fully accessible under your EUID. I'd recommend you to remove the ~/.local/share/TelegramDesktop directory (this will drop your current Telegram session) and then start telegram-desktop as unprivileged user, without sudo.
Bug#892548: dhelp: /usr/sbin/dhelp_parse broken with ruby 2.5
Control: tag -1 unreproducible Unfortunately, I can't reproduce this error. However, I've faced the other error related to dhelp's cron script. It fails to build a document index, and so search doesn't work. But at least the dhelp_parse utility can rebuild its documentation directory, and a home page is still available. It seems some of the next warnings aren't linked to dhelp. But these issues are already reported, see Bug#803342 and Bug#889651. (dhelp)root@barberry:/# sh -x /etc/cron.weekly/dhelp + [ -d /var/lib/dhelp ] + [ -x /usr/sbin/dhelp_parse ] + [ -x /usr/bin/index++ ] + rm --force /var/lib/dhelp/documents.index + /usr/sbin/dhelp_parse -r /usr/lib/ruby/vendor_ruby/debian.rb:223: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:224: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:227: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:230: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:233: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:236: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:348: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:557: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:577: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:578: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:743: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:753: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:763: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:772: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:799: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:1004: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument + /usr/sbin/dhelp_parse -i /usr/lib/ruby/vendor_ruby/debian.rb:223: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:224: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:227: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:230: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:233: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:236: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:348: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:557: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:577: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:578: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:743: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:753: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:763: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:772: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:799: warning: pa
Bug#892548: dhelp: /usr/sbin/dhelp_parse broken with ruby 2.5
tags 892548 - unreproducible reassign 892548 libruby2.5 forcemerge 892099 892548 stop It appears the bug with very similar issue was fixed in the libruby2.5 package so I merge these bugs. If your error still exists, let us know.
Bug#893554: range-v3 FTBFS
Hi, 19.03.2018 23:54, Adrian Bunk пишет: > Some recent change in unstable makes range-v3 FTBFS: > > https://tests.reproducible-builds.org/debian/history/range-v3.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/range-v3.html I can't reproduce these errors with gcc 7.3.0-15 or above. That version has fixed a bug[1] related to similar errors. Could you please rebuild the range-v3 package by yourself and tell about compilation results against the latest gcc-7 package? [1]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85118
Bug#887010: telegram-desktop segfaults on debian buster (amd64) using Gnome3
Hi, 12.01.2018 16:31, Robin пишет: > Versions of packages telegram-desktop depends on: ... > pn libtgvoip1.0 It seems you have no installed package with libtgvoip. This may have led to such crash. > Setting the environment variabel 'XDG_CURRENT_DESKTOP' to 'NONE' solves the > issue temporarily. Does I understand correctly, Telegram works fine *some time* and then crashes? This may be related to an incoming call that cannot be handle properly without libtgvoip, and it's unlikely affected by the XDG_CURRENT_DESKTOP environment variable.
Bug#887010: telegram-desktop segfaults on debian buster (amd64) using Gnome3
Control: severity -1 important Please send Telegram logs from the ~/.local/share/TelegramDesktop/log.txt file to debug this crash. 31.01.2018 12:34, Robin Mueller-Bady пишет: > Setting XDG_CURRENT_DESKTOP to NONE works fine all the time. If it is not > set, Telegram > won't start at all due to a SIGSEV. In both ways completely deterministic :-) If so and the program works (in any way), the bug should have important or normal severity because a workaround is found.
Bug#885459: telegram-desktop: FTCBFS on all architectures
Hello, 27.12.2017 15:16, Boyuan Yang пишет: > Package telegram-desktop FTCBFS on all architecture according to buildd > logs[1]. > > There are all kinds of reasons about build failures across different > architectures, including cc1plus internal compiler error, timeout, vmem > exhaustion, etc. > > Please investigate into this issue. I'm not sure what we can do, perhaps > the best plan is to force non-parallel compilation (instead of make -j4 > or whatsoever on buildds). I already found a fix[1] for memory exhaustion by GCC. If we look at a file where the RPL_CONSUMER_TYPE_ERASED_ALWAYS macro is used[2], we discover that the replacement of the auto keyword with more specific type solves the problem. But unfortunately there is another issue with linking on all architectures except for amd64 and i386. Once a solution is found, I'll prepare a new version of the package. That's example of the error: obj.target/liblinux_glibc_wraps.a(linux_glibc_wraps_64.o): In function `__wrap_clock_gettime': ./obj-powerpc64le-linux-gnu/./Telegram/SourceFiles/platform/linux/linux_glibc_wraps_64.c:27: undefined reference to `clock_gettime@GLIBC_2.2.5' /usr/bin/ld: Telegram: No symbol version section for versioned symbol `clock_gettime@GLIBC_2.2.5' /usr/bin/ld: final link failed: Nonrepresentable section on output collect2: error: ld returned 1 exit status I don't think that non-parallel build let us avoid the errors. [1]: https://anonscm.debian.org/git/collab-maint/telegram-desktop.git/commit/?id=4dc4aadc8497a996f91d75fa7d8b64884cf8b54c [2]: https://anonscm.debian.org/git/collab-maint/telegram-desktop.git/tree/Telegram/SourceFiles/rpl/consumer.h?id=4dc4aadc8497a996f91d75fa7d8b64884cf8b54c#n629
Bug#917315: libtgvoip: FTBFS on several arches (i386, mips, ppc64el, s390x) after recent upload
There are at least three different issues. The first thing you mentioned relates to SSE2 extension on i386 and already has a fix[1] in Git. The second one because of the lack of release architectures in files webrtc_dsp/rtc_base/system/arch.h and webrtc_dsp/typedefs.h. Actually, those lists need to be extended. The third issue is caused by system headers on GNU/Hurd and kFreeBSD. [1]: https://salsa.debian.org/debian/libtgvoip/commit/5bb9a8bdf260b528f589bd83400ade1476c94702
Bug#791770: dhelp: Depends on obsolete ruby-bdb
Control: owner -1 !
Please don't remove this package. I already work on patch to fix this
bug. I think I can perform migration from a module for Berkley DB to DBM
class from the Ruby standard library. I'm attaching my current draft.
Now I going to write migration scripts and test them.
By the way, can I check a previously installed version of the package in
postinst script?
=== modified file 'debian/changelog'
--- debian/changelog 2014-12-12 22:02:20 +
+++ debian/changelog 2017-04-24 20:23:36 +
@@ -1,3 +1,10 @@
+dhelp (0.6.21+nmu6ubuntu1) UNRELEASED; urgency=medium
+
+ * Migrate to a module from the standard library
+- Remove ruby-bdb dependency
+
+ -- Nicholas Guriev Mon, 24 Apr 2017 23:21:54 +0300
+
dhelp (0.6.21+nmu6) unstable; urgency=medium
* Non-maintainer upload.
=== modified file 'debian/control'
--- debian/control 2014-05-18 13:18:39 +
+++ debian/control 2017-04-24 20:20:58 +
@@ -11,7 +11,7 @@
Package: dhelp
Depends: perl-modules, libtemplate-perl, libhtml-parser-perl,
liburi-perl, liblocale-gettext-perl, libdata-page-perl,
- ruby | ruby-interpreter, ruby-bdb, ruby-debian, ruby-gettext,
+ ruby | ruby-interpreter, ruby-debian, ruby-gettext,
doc-base, swish++, pstotext, poppler-utils, ucf (>= 0.8),
${misc:Depends}
Recommends: www-browser | html2text
=== modified file 'devtools/list-dirs.rb'
--- devtools/list-dirs.rb 2012-06-12 21:50:00 +
+++ devtools/list-dirs.rb 2017-04-24 19:50:51 +
@@ -2,7 +2,7 @@
path = ARGV.shift || Dhelp::DOC_DIR_DATABASE
puts "Opening #{path}"
-ddd = Dhelp::DocDirDatabase.open(BDB::RDONLY, path)
+ddd = Dhelp::DocDirDatabase.open(DBM::READER, path)
ddd.each do |dir, doc_id, title|
puts "#{dir} -> #{doc_id} (#{title})"
end
=== modified file 'lib/dhelp.rb'
--- lib/dhelp.rb 2014-05-18 13:18:39 +
+++ lib/dhelp.rb 2017-04-24 19:57:08 +
@@ -18,7 +18,7 @@
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
=end
-require 'bdb'
+require 'dbm'
require 'pathname'
require 'fileutils'
@@ -239,23 +239,18 @@
# Database for doc-base directories. It contains base directories associated
# with the corresponding doc-base doc id and the document title.
- class DocDirDatabase < BDB::Hash
-def self.open(flags = BDB::RDONLY,
+ class DocDirDatabase < DBM
+def self.open(flags = DBM::READER,
name= DOC_DIR_DATABASE,
options = {},
mode= 0644)
- default_options = {"ffactor" => 8,
- "nelem" => 1,
- "cachesize" => 5000,
- "hash" => nil,
- "lorder"=> 0}
- super(name, nil, flags, mode, default_options.merge(options))
+ super(name, mode, flags)
end
# Traverse entire BD, passing directory, doc_id and title of each item to
# the block
def each
- super do |k,v|
+ each_pair do |k,v|
value = DocDirDatabaseValue.new(v)
yield DocDirDatabaseKey.new(k).dir, value.doc_id, value.title
end
@@ -266,19 +261,19 @@
def add(dir, doc_id, title)
key = DocDirDatabaseKey.new(:dir => dir)
value = DocDirDatabaseValue.new(:doc_id => doc_id, :title => title)
- put(key.to_raw_data, value.to_raw_data)
+ self[key.to_raw_data] = value.to_raw_data
end
def include?(dir)
key = DocDirDatabaseKey.new(:dir => dir)
- return super(key.to_raw_data)
+ return has_key?(key.to_raw_data)
end
# Returns an array with two elements, doc_id and title, for the registered
# doc-base document in the given directory
def info_for_path(dir)
key = DocDirDatabaseKey.new(:dir => dir)
- raw_value = get(key.to_raw_data)
+ raw_value = self[key.to_raw_data]
if raw_value.nil?
raise KeyNotFoundError, "Can't find information for path #{dir}"
end
@@ -448,10 +443,11 @@
# Registers a list of doc-base documents as part of Dhelp
def _register_docs(doc_list, user_opts={})
register_opts = {:regenerate_index => false}.merge(user_opts)
- open_flag = register_opts[:regenerate_index] ? (BDB::CREATE|
- BDB::TRUNCATE) :
- BDB::CREATE
- doc_dir_db = DocDirDatabase.open(open_flag, @doc_dir_database)
+ if register_opts[:regenerate_index]
+doc_dir_db = DocDirDatabase.open(DBM::NEWDB, @doc_dir_database)
+ else
+doc_dir_db = DocDirDatabase.open(DBM::WRCREAT, @doc_dir_database)
+ end
index_paths = []
doc_list.each do |doc|
doc.formats.each do |format|
=== modified file 'test/tc_dhelpdocumentpool.rb'
--- test/tc_dhelpdocumentpool.rb 2014-05-18 13:18:39 +
+++ test/tc_dhelpdocumentpool.rb 2017-04-24 20:19:29 +
@@ -1,6 +1,7 @@
require 'test/unit'
require 'dhelp'
require 'fileutils'
+require 'set'
class TC_Dhelp
Bug#859027: telegram-desktop: Incomplete debian/copyright?
Control: tag -1 + fixed 29.03.2017 20:18, Chris Lamb пишет: I just ACCEPTed telegram-desktop from NEW but noticed it was missing attribution in debian/copyright for at least: Telegram/Patches/qtbase_5_6_2.diff debian/patches/Avoid-depending-on-static-libraries.patch etc. (This is *not* exhaustive so please check over the entire package carefully and address these on your next upload.) I've add mentions about the first patch into debian/copyright. The second patch no longer includes foreign code, I moved all borrowings from Qt source into special file debian/qt_functions.cpp. I hope there are no other missing attributions. 29.03.2017 23:08, Mattia Rizzolo пишет: > Actually, Nicholas, what's the state of your endeavour to improve the > upstream situation, and reduce the patching done on the Debian site? They merged my last pull request [1], so I deleted d/p/Fix-desktop-integration-issues.patch. [1]: https://github.com/telegramdesktop/tdesktop/pull/3109
