It is showing currently 809 packages broken/won’t install in x86_64, another 793 in i586. We don’t need a bug report on everyone of them, doing so makes maintaining bugzilla more work and takes away time from fixing broken packages.
We are working on getting some activity on fixing these. I’ll be participating myself. Problem is we don’t have enough manpower. Do you have any interest in learning how to fix broken packages yourself? We really do need the help.
Consulting the table of x86_64 packages with problems, I noticed the number of packages is probably greater than the number of broken dependencies. Is it true?
I am not able now to build a rpm package for OMV. I’ve done this in the past (10 years ago?) in another distro but things has changed fast and I would have first to make an effort to acquire updated skills for that. I am particularly interested in sagemath package (in the list), if I could help in another way …
Not asking for people to build rpm’s asking for people to fix broken packages. Not the same thing but would require willingness to learn. Fixing and building packages is done in ABF.
For example, libavcodec.so.56()(64bit) is listed as a broken dependency in more than ten packages. As far as I understand, if one build what provides libavcodec.so.56()(64bit) package, it will help building tens of packages …
lauro4 and brucepc thanks for your interest. I’ll be in touch in the near future. I’ve need to go through a learning process myself first. Maybe I started this thread before I was ready myself. Sorry about that.
Edit: Something Y’all could do is start reading in the wiki and signing up for mailing lists. Also you may wish to consider signing up for IRC. One thing you’ll see is we need help updating and maybe adding wiki pages as well. There is lots more that we need help with. That’s all a part of a small, all volunteer organization with no full time people, no employees.
Also you’ll see Cooker IRC and ML talked about as for the development process. That is true but because we are so few in number the Cooker IRC channel and ML are used for most communication.
lauro4 and brucepc thanks for your interest. I’ll be in touch in the near future. I’ve need to go through a learning process myself first. Maybe I started this thread before I was ready myself. Sorry about that.
Thanks for your interest. We need people willing to learn how to fix broken packages among other things. If you aren’t interested in this there must be other ways you’d be interested in helping. Best way to get started is to sign-up for a mailing list and ask questions there.