[opensuse-factory] new devel project for rpmlint
Hi, rpmlint updates bear a high risk of breaking other packages and even causing bootstrap issues due to it's use in the build root. Therefore rpmlint* and potentially also brp-check-suse and post-build-checks should be moved to a dedicated devel project to avoid annoying others in Base:System IMO. Where would be a better place? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday 20 April 2011, Ludwig Nussel wrote:
rpmlint updates bear a high risk of breaking other packages and even causing bootstrap issues due to it's use in the build root.
which can however easily be avoided or recovered in Base:System via osc wipebinaries and build-disablement of the rpmlint-mini package (then the one from factory is used which hopefully still works, unless the python version was switched in the middle where more issues have to be fixed again until it works again).
Therefore rpmlint* and potentially also brp-check-suse and post-build-checks should be moved to a dedicated devel project to avoid annoying others in Base:System IMO
I can understand that it might disturb other developments, but being able to test that bootstrap still works is essential precondition for submitting rpmlint to Factory. if you move it to a seperate project then it needs to have the same verification,namely that all base system packages that are needed for rebuilding rpmlint are in one devel project to ensure that we can recover from a fatal error. Thats easily possible by linking all the packages from Base:System of course,but in the end you have to refix the links every time something essential changes in Base:System. I would prefer if we can setup a project together with python, as the major python version updates where those that broke rpmlint every time and I was caught on surprise every time.
Where would be a better place?
it probably belongs into another separate project if Base:System is really that much offended by it (personally I haven't received any complains). I would suggest devel:tools:building:checks Thanks, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
El 20/04/11 07:00, Ludwig Nussel escribió:
Where would be a better place?
I think Base:System is OK, I hope nobody expects stuff to run perfectly and not have bugs during development, such expectations are unrealistic to say at least. ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Cristian Rodríguez
-
Dirk Müller
-
Ludwig Nussel