Bug 373931

Summary:	Incomplete KF5 installations in several distributions
Product:	[Applications] umbrello	Reporter:	Ralf Habacker <ralf.habacker>
Component:	general	Assignee:	Umbrello Development Group <umbrello-devel>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	luigi.toscano, simonandric5
Priority:	NOR
Version:	frameworks5
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Bug Depends on:
Bug Blocks:	373932

Description Ralf Habacker 2016-12-20 00:39:34 UTC

It has been reported that umbrello KF5 installations are incomplete.

https://mail.kde.org/pipermail/umbrello-devel/2016-December/020640.html
https://bugs.kde.org/show_bug.cgi?id=361479

Comment 1 Luigi Toscano 2017-09-29 21:34:11 UTC

This is a packaging problem, so a downstream problem. The need for KIO was already documented in the other bug (see https://bugs.kde.org/show_bug.cgi?id=361479#c9 )
I'm not completely sure about the scope of this bug, compared to the combination of https://bugs.kde.org/show_bug.cgi?id=361479 (already solved) and https://bugs.kde.org/show_bug.cgi?id=373854 (solved as well), which could have been duplicated. Anyway, closing this one as well.

Comment 2 Ralf Habacker 2017-09-29 22:07:20 UTC

(In reply to Luigi Toscano from comment #1)
> This is a packaging problem, 
I agree

> so a downstream problem.
Not complety. If the problem is not fixed in the distro as happened with https://bugs.launchpad.net/ubuntu/+source/umbrello/+bug/1585611 people will continue to report this bug to umbrello bug tracker, which is annoying.

Comment 3 Luigi Toscano 2017-09-29 22:23:00 UTC

(In reply to Ralf Habacker from comment #2)
> (In reply to Luigi Toscano from comment #1)

> > so a downstream problem.
> Not complety. If the problem is not fixed in the distro as happened with
> https://bugs.launchpad.net/ubuntu/+source/umbrello/+bug/1585611 people will
> continue to report this bug to umbrello bug tracker, which is annoying.

It is annoying, but it does not change the status of the issue as it is (still downstream).
It can happen that people reports the issue here, and it may depend on different factors:
- incomplete search before sending the bug
- more visible upstream bugtracker compared to the downstream one
etc

While some of this issues can be solved (some distributions suggests to file the issues on their bugtracker), it is impossible to solve all of them completely (it happens also to developers to file misplaced bugs). In that case, the new bugs will be closed as duplicated of one of this.