Hi, I want to remind people that on each Debian source package we have upstream metadata in debian/upstream/metadata that points to the correct project & component on https://bugs.kde.org (DEP-12). That information helped me already a lot to not do the search for the correct component upstream. Maybe someone knows a Debian tool to get this information via command line, that could improve the search for duplicates.
Regards, hefee -- On Donnerstag, 12. Dezember 2024 13:46:20 CET Martin Steigerwald wrote: > Hi Aurélien, hi. > > Aurélien COUDERC - 12.12.24, 13:19:34 MEZ: > > So I strongly advise to only report bugs upstream directly : > > - If the version of the Debian package matches the latest upstream > > release. That's currently the case for Plasma and kf6 in > > trixie/unstable but would never be the case for stable. > > Thanks! You are right. This is an important aspect. Upstream is overworked > as well. And there are way to help them. Actually as far as I saw so far, > almost every free software project is overworked on bug triaging. > > I focused this mostly on Plasma 6 and so on from unstable and forgot a bit > about the old stuff, so it is good you bring that in! But even with KDE > software from unstable: some is not yet up to date. For for example for > latest KDEPIM is in experimental, but not in unstable currently. As for > packages in experimental, it may be good to ask / report here first, before > reporting a Debian bug. > > It is not useful for upstream to report any issues on Plasma 5 or for that > matter for any KDE Gear stuff which still relies on KDE Frameworks 5 unless > they also happen in latest or almost latest upstream version. > > Diverging a bit from your recommendation I'd say if you run Plasma, let's > say 6.2.4 and upstream just released Plasma 6.2.5 a few days ago, an > upstream report may still be helpful, in case you have checked whether it > is reported already. Probably after also looking in upstream announcement > whether the issue has been fixed meanwhile. I think it would be > unreasonable to expect users to always be on the newest upstream release > on the day of release. Upstream themselves word it as: > > "...using relatively recent versions of KDE software (≤ 1 year old) or an > LTS supported version" > > Here you can find more information on upstream bug reporting: > > https://community.kde.org/Get_Involved/Issue_Reporting > > As well as triaging: > > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > This is really a great way to help out both in Debian and in upstream. And > you do not need to be a developer for that. Also you can help out in > little pieces as your schedule allows for it. > > > - Once you've double checked that no existing bug report in bugs.kde.org > > already describes the issue you're having. > > I mentioned that. But yes… please avoid duplicates in the upstream bug > tracker. > > Best,
signature.asc
Description: This is a digitally signed message part.
