Bug 351252 - lingering knode references
Summary: lingering knode references
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdepim
Classification: Applications
Component: general (show other bugs)
Version: GIT (master)
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-13 11:01 UTC by Harald Sitter
Modified: 2018-02-01 09:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Sitter 2015-08-13 11:01:54 UTC
apparently knode is no more yet there are still some references

./libkpgp/pics/CMakeLists.txt:install(FILES key_ok.png key_bad.png key_unknown.png key.png DESTINATION ${KDE_INSTALL_DATADIR}/knode/pics)
./README.packagers:KNode. This package should contain KNode from the knode/ directory, and the
./README.packagers:Kontact plugin from the kontact/plugins/knode directory. kontact/plugins/knode
./README.packagers:should not be installed when knode/ is not installed.
./importwizard/autodetect/thunderbird/thunderbirdsettings.cpp:            //TODO add config directly to knode
./importwizard/autodetect/thunderbird/thunderbirdsettings.cpp:            //TODO when knode will merge in kdepim
./doc/pimsettingexporter/index.docbook:  <!ENTITY knode "<application>Knode</application>">
./doc/pimsettingexporter/index.docbook:<member>&knode;</member>





Reproducible: Always
Comment 1 Denis Kurz 2017-06-23 19:58:50 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:49:21 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.