Bug 11375

Summary:	[2021.1] foo-yc20 cannot compile against any faust 2.x.x release -> drop the package?
Product:	[ROSA-based products] ROSA Fresh	Reporter:	Giovanni Mariani <mc2374>
Component:	Contributed Packages	Assignee:	ROSA Linux Bugs <bugs>
Status:	RESOLVED FIXED	QA Contact:	ROSA Linux Bugs <bugs>
Severity:	normal
Priority:	Normal	CC:	survolog
Version:	All
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Platform:	2021.1	ROSA Vulnerability identifier:
RPM Package:	foo-yc20-1.3.0-7.src.rpm	ISO-related:
Bad POT generating:		Upstream:

Description Giovanni Mariani 2021-06-08 00:05:38 MSK

The Facts:
1) Trying to build foo-yc20 in rosa2019.1 fails with this error:
"include/foo-yc20.h:36:29: fatal error: faust/audio/dsp.h: No such file or directory".
This error derives from the fact that in faust 2.x.x the dsp.h header file was moved from faust/audio to faust/dsp...
But patching the source files and having them pointing to the new place is not enough: the build process fails a little later with the error:
"src/main-gui.cpp: In function ‘int main(int, char**)’:
src/main-gui.cpp:85:11: error: cannot declare variable ‘processor’ to be of abstract type ‘YC20Jack’ YC20Jack processor;"

2) In a discussion thread about the issue, the program maintainer says that the program only builds with faust 0.9.73 and that there are no plans to port foo-yc20 to faust 2.x.x; see:
https://github.com/sampov2/foo-yc20/issues/16#issuecomment-432207094.

3) In Rosa 2019.1 we have only faust 2.27.2 or later: then as-is foo-yc20 will never build.

4) Upstream has little activity since 2018.

5) The only other distributions providing foo-yc20 are Debian and Ubuntu.

The proposal: Drop foo-yc20 from 2019.1.

Comment 1 Giovanni Mariani 2021-06-26 12:03:37 MSK

Ping...
Can I do the removal myself?

BTW Dropping the package will require removing it from task-sound-studio meta-package (and this one in turn really needs an update, IMHO).

Comment 2 Grigorev Andrey 2021-06-28 16:17:49 MSK

I think that if the package does not look as required, you can delete it.
Or you can also create another project.
If something interferes with something, there is
%global __provides_exclude
%global __requires_exclude
or
Conflicts:
Or you can try to write to spec so that the project is not updated.
But there will still be a chance that someone will accidentally update it.

Comment 3 Giovanni Mariani 2021-06-28 16:37:36 MSK

(In reply to Grigorev Andrey from comment #2)
> I think that if the package does not look as required, you can delete it.
> Or you can also create another project.
> If something interferes with something, there is
> %global __provides_exclude
> %global __requires_exclude
> or
> Conflicts:
> Or you can try to write to spec so that the project is not updated.
What I would is removing it from 2019.1/Contrib and update task-sound-studio accordingly (ATM the meta-package is in repoclosure failed lists because of foo-yc20 and a bunch of other packages... I'm slowly fixing them).

> But there will still be a chance that someone will accidentally update it.
Even if removed from 2019.1 repository lists? The source tree will remain on ABF and the package on 2016.1 (basically outdated now and nearly not updatable), if need arises...

Comment 4 Giovanni Mariani 2022-01-18 17:25:08 MSK

Fixed with patch... (thaks Alexander).