On 5 August 2015 at 13:36, gargamel 704 wrote:

The UEFI issue not only affects installing from an USB stick!

1. I also tried to install in legacy mode which resulted in a very unstable system (not sure why). 2. When I tried to update (zypper dup) the system did hang during booting. This alone make the issue much more severe than not being able to produce boot sticks capable of booting in UEFI mode!

There is a bug report for the UEFI issue in bugzilla, but there is no visible/communicated progress on the matter.

The only UEFI issue I've found is only related to USB sticks I'm talking to you from a Tumbleweed machine running UEFI (no Legacy) 2 out of 3 of my regular machines are UEFI only, and haven't had any problems on any recent snapshots So, what are the symptoms I should be experiencing?

The dependency issues are annoying but not a big issue as they usually get sorted out quickly after flagging an issue. One thing that has now been broken for months (at least until a couple of days ago, not sure about the current state): The java repo. zypper complains about broken link groups in the packages.

I know I've said this before but I'll say it again If you are using additional repos, you are NOT using Tumbleweed You're using Tumbleweed with additional Repos, and the responsibility for any issues caused by those additional repos can not, and should not, be put on the shoulders of Tumbleweed This is especially dangerous when you realise most additional repos are Devel repos, which, by design and definition, should contain BROKEN things before being submitted to Tumbleweed. They're untested, they're not guaranteed to work, don't blame Tumbleweed when an additional repo has a dependency problem. Wherever possible, stick to using just Tumbleweed If you need more packages in Tumbleweed that exist in some repo somewhere, encourage the maintainer to submit them to Tumbleweed and maintain them properly.

Suggestion: What about automating dependency issue reporting in zypper and yast? I think we would see then probably a lot more of these reports.

No, because it sounds like at least one of your dependency problem is at least partially your own fault by using non-standard repos.

Regarding the being part of the problem thing: You're completely right there. However reporting bugs should be made very easy and non-disruptive. KDE has for instance its own reporting tool that I used in the past for reporting issues. The eclipse IDE also has such a tool. All o those tools largely work without me having to do much except clicking "report bug" and I really think this is the best approach for this.

I'm sorry, but I don't buy that argument. Not everything is fixed by tooling, sometimes some people just have to do stuff Besides, the official link for reporting bugs on Tumbleweed makes the whole process pretty darn simple: http://bugzilla.opensuse.org/enter_bug.cgi?product=openSUSE+Factory&format=guided from https://en.opensuse.org/openSUSE:Submitting_bug_reports -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org