[11:17] <lubot> [telegram] <RikMills> so calibre is now the issue?
[11:19] <lubot> [telegram] <RikMills> sorry I have not been able to look much. too many things going on :/
[11:19] <lubot> [telegram] <mitya57> It's https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007966. I talked to Stefano Rivera yesterday, he will try to fix it in Python.
[11:20] <lubot> [telegram] <RikMills> aha. good
[11:21] <lubot> [telegram] <mitya57> The same issue affected pyqt5, but I worked around it in sip6. I think patching every package that uses sysconfig to get Python headers path is not optimal, so let's wait a couple of days for Python fix.
[11:21] <lubot> [telegram] <RikMills> fair enough
=== RikMills__ is now known as RikMills
[18:51] <lubot> [telegram] <RikMills> might have to get the new telegram sync removed from proposed. it FTBFS
[18:51] <lubot> [telegram] <RikMills> I have pinged mattia who synced that
[18:52] <lubot> [telegram] <mitya57> Thank you
[18:54] <lubot> [telegram] <RikMills> To be honest packaging telegram-desktop seems a mad thing to do anyway, as it will rapidly be very out of date and lacking features compared to the upstream version
[18:55] <lubot> [telegram] <RikMills> this is why I use the upstream github binary for desktop, which autoupdates
[19:03] <lubot> [telegram] <X> But nobody can guarantee that it is not a spyware
[19:04] <lubot> [telegram] <Eickmeyer> Please, we don't need any tinfoil hat discussion here. (re @X: But nobody can guarantee that it is not a spyware)
[19:05] <lubot> [telegram] <X> We?
[19:30] <lubot> [telegram] <RikMills> mattia is talking to the TG maintainer, who may have a fix in time
[19:31] <lubot> [telegram] <RikMills> if not it will have to go from proposed, at least in the short term