Am Dienstag, 4. Juni 2019, 13:00:26 CEST schrieb Dominique Leuenberger / DimStar:

So, 'final call' - if somebody deeply cares for 'dumb', speak up now (and provide a fix).

The issues of this tools started long before: when it got its name in the first place... SCR. I've used it once, around 1991 on a Bull DPX/2 320. Let it pass by. Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, 2019-06-04 at 14:13 +0000, John Paul Adrian Glaubitz wrote:

On 6/4/19 1:00 PM, Dominique Leuenberger / DimStar wrote:

...

The package 'dumb' has been unresolvabled since February 1st, when allegro wa supdate to version 5.x.

I only see "BuildRequires: liballeg-devel" in the spec file.

Shouldn't that be a matter of rebuilding the package or am I missing something?

Nothing provides liballeg-devel since allegro was updated to version 5.0. And allegro 5.0 no longer provides allegro-config, so even using the new devel package won't do any good. So what would you propose we 'rebuild'? Anyway: fixing the package for the sake of it 'not failing' is not exactly what I'm after. This package is old/stale and as demonstrated,. unmaintained. Nobody even noticed it not building for 4 months. So unless there is actually a REASON to keep it, I'm not willing to just have a 'build fix' accepted. Cheers Dominique

On 6/4/19 4:34 PM, Dominique Leuenberger / DimStar wrote:

Nothing provides liballeg-devel since allegro was updated to version 5.0. And allegro 5.0 no longer provides allegro-config, so even using the new devel package won't do any good. So what would you propose we 'rebuild'?

So, allegro stopped being available as a shared library? That's an odd change which I wouldn't have expected. I have not looked into the details of the allegro package yet and just skimmed over the spec file of the dumb package. I'm well aware that rebuilds don't make missing build dependencies reappear. I just saw what OBS complaining about and those were just the runtime libraries when I took a quick look but I must have overlooked the message about "liballeg-devel" then.

Anyway: fixing the package for the sake of it 'not failing' is not exactly what I'm after. This package is old/stale and as demonstrated,. unmaintained. Nobody even noticed it not building for 4 months. So unless there is actually a REASON to keep it, I'm not willing to just have a 'build fix' accepted.

But fixing old stuff is fun. Deleting stuff is too easy :P. Adrian

On Tuesday 2019-06-04 17:09, John Paul Adrian Glaubitz wrote:

On 6/4/19 4:34 PM, Dominique Leuenberger / DimStar wrote:

...

Nothing provides liballeg-devel since allegro was updated to version 5.0. And allegro 5.0 no longer provides allegro-config, so even using the new devel package won't do any good. So what would you propose we 'rebuild'?

So, allegro stopped being available as a shared library? I have not looked into the details

I have not looked at the details, but I'll throw another hypothesis in the room: besides configure-time checks, that dumb 0.x may not be prepared for the Allegro 5.x API (possibly functions removed from 4.x). Subsequently, dumb 2.x may itself have a different API that _its_ downstream users are likewise unprepared for. And because no investigations to those ends were done since the start of FTBFS, the package is now on the way out.

But fixing old stuff is fun. Deleting stuff is too easy :P.

Pssst... if you can sell your build-fix as more than a build-fix to dimstar, that's all you will need. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org