Bug#984540: libkf5incidenceeditor: Wrong homepage + new version
Source: libkf5incidenceeditor Version: 18.08.3-3 Severity: normal I have see that the project homepage do not respond anymore: https://pim.kde.org/ I think that the homepage is now: https://invent.kde.org/pim/incidenceeditor https://github.com/KDE/incidenceeditor I don't understand why there are two active repositories... I think that here there is a new version: 20.12.3 Ciao Davide Note: this is a simplified bug report that I use to report homepage problems found at https://repology.org/repository/debian_testing/problems
Bug#981515: kcoreaddons: please replace fam with gamin
On Thu, Mar 04, 2021 at 08:23:44AM +0100, Sune Stolborg Vuorela wrote: > > On 3/3/21 8:54 PM, Nicholas D Steeves wrote: > > > > thus FAM covers a use case that gamin does not, and this case is: users > > who want to receive inotify style events for files that have been > > remotely created or modified on NFS mounts. > > > > Also, IIRC gamin depends on Linux-specific features such as inotify > > where FAM provides fallbacks (eg: IIRC FAM is required on kfreebsd and > > hurd); this might not be significant, but I felt it was worth mentioning > > :-) > > > Please note that these features are what KCoreAddons (or more specifically > KDirWatch) uses FAM for. > > KDirWatch hooks up to inotify directly and prefers that if possible. FAM is > only used for fallback codepath for e.g. nfs-mounts, before KDirWatch > resorts to the last fallback; polling. > > Replacing with libgamin is basically making the inotify-free codepath depend > on inotify, so either keep using FAM, or skip both of them. > > > /Sune > > - who has been debugging KDirWatch and other parts of KCoreAddons over the > years. Sune, thanks for chiming in as someone using and debugging KCoreAddons! It bears repeating that KCoreAddons using FAM is ineffective over NFS unless the NFS server is also running and insecurely exposing FAM, which is hopefully not widely used on the open internet today. Sune, do you know if you were using KCoreAddons on networks that had FAM running on the NFS server? If so, would you recommend those configurations today (versus 20 years ago)? (Yes, it is possible to better secure with firewall rules and tunnels, but takes more effort and is still less appropriate for a multi-user system on which the users have shell access and are using KCoreAddons.) > Replacing with libgamin is basically making the inotify-free codepath depend > on inotify, so either keep using FAM, or skip both of them. I suggest the latter. I think removal of FAM and gamin from KCoreAddons is preferred. As a lighttpd developer, I replaced both FAM and gamin with inotify() on Linux and kqueue() on *BSD. There is a reasonable fallback in lighttpd when neither are available. Cheers, Glenn
[bts-link] source package qtdeclarative-opensource-src
# # bts-link upstream status pull for source package qtdeclarative-opensource-src # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #983597 (http://bugs.debian.org/983597) # Bug title: [PATCH] Segfault in libqt5quick5.so: QQuickItemLayer::~QQuickItemLayer() # * https://bugreports.qt.io/browse/QTBUG-91437 # * remote status changed: (?) -> Reported usertags 983597 + status-Reported thanks
Re: KDE Plasma v5.21.2
Dear Sedat. Sedat Dilek - 04.03.21, 10:10:54 CET: > No comment, see attachment. I appreciate your enjoyment about the new version. However I suggest not to post an image with a screenshot of the version number every time a patch release of Plasma is released. In my point of view it is needless internet traffic relayed to quite some mail boxes. If you like to share some nice information you can post the release announcement. It may contain useful information for some users: https://kde.org/announcements/plasma/5/5.21.2/ Of course, for all who want to review the changes of the major version, see here: https://kde.org/announcements/plasma/5/5.21.0/ By the way, I do have: Explanation: Automatically update experimental packages Package: * Pin: release a=experimental Pin-Priority: 200 in my /etc/apt/preferences. I do not recommend this for all users! You need to be careful to watch the output of apt / aptitude dist-upgrade in case you have experimental packages installed – an experimental package may have been built against other experimental packages and this can cause unwanted upgrades or breakages. For my use case of just installing Plasma and KDE Frameworks from experimental I expect this to be working fine. By all means keep the pin priority below 500! So or so… this is for experienced users who are willing to look carefully and also are willing to keep the pieces in case something breaks, in other words who are willing to accept that it is their responsibility to fix it up again then. Of course, you can ask here, and people may help. Ciao, -- Martin
Re: KDE Plasma v5.21.2
same, here. Easy upgrade :=) Thanks!! [image: afbeelding.png] Op do 4 mrt. 2021 om 10:27 schreef Sedat Dilek : > No comment, see attachment. > > - sed@ - > -- Luc Castermans mailto:luc.casterm...@gmail.com
KDE Plasma v5.21.2
No comment, see attachment. - sed@ -
Bug#981515: kcoreaddons: please replace fam with gamin
On 3/3/21 8:54 PM, Nicholas D Steeves wrote: thus FAM covers a use case that gamin does not, and this case is: users who want to receive inotify style events for files that have been remotely created or modified on NFS mounts. Also, IIRC gamin depends on Linux-specific features such as inotify where FAM provides fallbacks (eg: IIRC FAM is required on kfreebsd and hurd); this might not be significant, but I felt it was worth mentioning :-) Please note that these features are what KCoreAddons (or more specifically KDirWatch) uses FAM for. KDirWatch hooks up to inotify directly and prefers that if possible. FAM is only used for fallback codepath for e.g. nfs-mounts, before KDirWatch resorts to the last fallback; polling. Replacing with libgamin is basically making the inotify-free codepath depend on inotify, so either keep using FAM, or skip both of them. /Sune - who has been debugging KDirWatch and other parts of KCoreAddons over the years.
