Re: Status of Plasma 5.18/5.19?
Could I help ? Although I am just a humble non-Debian packager. Luc Op 26-07-2020 om 22:33 schreef Shmerl: Om Tue, 07 Jul 2020 08:20:48 -0700 Scarlett Moore wrote: > Again, help is gladly accepted as long as it is quality work > and not just a changelog entry.. > Thanks, Scarlett Hi Scarlett! If I understand correctly, it's primarily you alone working now on updating Plasma packages in Debian unstable / testing? If so, thanks for your work! Did you manage to use//Norbert's submissions after all? He said his merge requests are still available. It would be really great for KDE/Debian users if this could be resolved positively and in the manner that's productive and allows collaboration. This really needs to move forward, there are simply not enough resources not to share such efforts. Best regards, Shmerl. // -- m.vr.gr. Luc Castermans mailto:luc.casterm...@gmail.com
Re: Re: Status of Plasma 5.18/5.19?
Om Tue, 07 Jul 2020 08:20:48 -0700 Scarlett Moore wrote: > Again, help is gladly accepted as long as it is quality work > and not just a changelog entry.. > Thanks, Scarlett Hi Scarlett! If I understand correctly, it's primarily you alone working now on updating Plasma packages in Debian unstable / testing? If so, thanks for your work! Did you manage to use Norbert's submissions after all? He said his merge requests are still available. It would be really great for KDE/Debian users if this could be resolved positively and in the manner that's productive and allows collaboration. This really needs to move forward, there are simply not enough resources not to share such efforts. Best regards, Shmerl.
Processed: Bug#957734 marked as pending in qtwebengine-opensource-src
Processing control commands: > tag -1 pending Bug #957734 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: ftbfs with GCC-10 Added tag(s) pending. -- 957734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Okular no longer follows PDF links - resolved (with apologies)
On 2020-07-22 17:37, Gary Dale wrote: I'm running Debian/Testing (Bullseye) on an AMD64 machine. Up until a few days ago, a PDF I created with Scribus worked perfectly with Okular. I could click on a link in the table of contents and jump to that page. I have a lot of other internal links in the document as well, such as a table of committee chairs linking to their biography pages. They don't work either. It gets worse however. I have even more web links (web sites, e-mail addresses and even telephone numbers) that also don't do anything. Most pages contain a lot of these. I checked using the "Document Viewer" program and it works fine with the PDF. The links all work. The problem appears to be with Okular. I've dug through the configuration options (none of which I'd ever changed from the defaults) and can't find anything to turn this behaviour on or off. Is anyone else having this issue? OK, the problem was that I'd somehow clicked on the Zoom icon which makes the mouse into a zooming tool instead of a selection tool.
Bug#951674: [Debichem-devel] Building Kalzium with OpenBabel: bad CMake module
Hi,
On Fri, Jul 24, 2020 at 08:31:12AM +0300, mer...@debian.org wrote:
> On 2020-07-19 00:31, John Scott wrote:
> > See the bug hunting at [1]: it seems that even in OpenBabel 3.1.1,
> > the CMake module probably wrongfully hardcodes a path and makes it not work
> > on
> > Debian.
>
> Indeed, there seems to be a problem with paths in OpenBabel CMake
> modules. OpenBabel3Config.cmake seems suspicious: ${OpenBabel3_DIR} does
> not seem to be set anywhere, and the following paths too get incorrect
> values:
>
> * OpenBabel3_INCLUDE_DIRS: should be /usr/include/openbabel3
> * OpenBabel3_EXPORTS_FILE: should be
> /usr/lib//cmake/openbabel3/OpenBabel3_EXPORTS.cmake
> * OpenBabel3_LIBRARIES (maybe?)
>
> Not sure if this issue is relevant outside Debian, hence the upstream
> confusion. I would suggest patching OpenBabel CMake modules in Debian. I
> volunteer to do that if no one comes up with a better solution.
Without having looked at the problem in detail, it sounds like it's
worth filing an issue in OpenBabel upstream as well, or is there one
already?
Michael
