Hi list,
I recently got error messages for all my (three) packages stating a broken dependency:
ktorrent has broken dependencies in the development tree: On ppc: ktorrent-3.0.2-3.fc10.ppc64 requires /bin/sh On ...
I'm not sure what the cause of this is, and what I should do about. Should I add /bin/sh as a fixed dependency?
Roland
On Mon, 2008-05-19 at 17:47 +0200, Roland Wolters wrote:
I'm not sure what the cause of this is, and what I should do about. Should I add /bin/sh as a fixed dependency?
This was a bug in yum one day that caused filedeps to not resolve. This has since been fixed so you can safely ignore the broken dep report that you got.
Jesse Keating wrote:
On Mon, 2008-05-19 at 17:47 +0200, Roland Wolters wrote:
I'm not sure what the cause of this is, and what I should do about. Should I add /bin/sh as a fixed dependency?
This was a bug in yum one day that caused filedeps to not resolve. This has since been fixed so you can safely ignore the broken dep report that you got.
As this isn't the first time that this (broken deps reports citing missing /bin/sh etc.) has happened, would it not be possible to add a sanity check on the broken deps script to avoid the mails if "obvious" things like /bin/sh are seen not to be available?
Paul.
On Mon, 2008-05-19 at 17:14 +0100, Paul Howarth wrote:
As this isn't the first time that this (broken deps reports citing missing /bin/sh etc.) has happened, would it not be possible to add a sanity check on the broken deps script to avoid the mails if "obvious" things like /bin/sh are seen not to be available?
It's possible sure. Just not something I'm probably going to get time to do. The code is in the releng git repo, in the scripts/ dir
http://git.fedorahosted.org/git/?p=releng;a=summary
On Mon May 19 2008, Jesse Keating wrote:
On Mon, 2008-05-19 at 17:14 +0100, Paul Howarth wrote:
As this isn't the first time that this (broken deps reports citing missing /bin/sh etc.) has happened, would it not be possible to add a sanity check on the broken deps script to avoid the mails if "obvious" things like /bin/sh are seen not to be available?
It's possible sure. Just not something I'm probably going to get time to do. The code is in the releng git repo, in the scripts/ dir
I believe it is somewhere else because a "grep -Ri broken *" on a cloned repository did not show the "Broken dependencies" subject that the mails should have. I want to suggest to add a check whether or not the amount of broken packages is sane, e.g. up to 100. And in case it is not, the script could add a note to the mail sent to fedora-devel and maybe releng or whover would have to take a look then or only skip the individual reports.
Regards, Till
On Mon, 2008-05-19 at 20:23 +0200, Till Maas wrote:
I believe it is somewhere else because a "grep -Ri broken *" on a cloned repository did not show the "Broken dependencies" subject that the mails should have. I want to suggest to add a check whether or not the amount of broken packages is sane, e.g. up to 100. And in case it is not, the script could add a note to the mail sent to fedora-devel and maybe releng or whover would have to take a look then or only skip the individual reports.
Gah, you're right. buildrawhide is in releng, but spam-o-matic comes from mash.
http://git.fedorahosted.org/git/?p=mash
On Mon May 19 2008, Jesse Keating wrote:
Gah, you're right. buildrawhide is in releng, but spam-o-matic comes from mash.
Thanks, is it intended that there is no trac for mash? Where do I have to send patches to?
Regards, Till
On Mon, 2008-05-19 at 22:17 +0200, Till Maas wrote:
Thanks, is it intended that there is no trac for mash? Where do I have to send patches to?
Intended yes, Bill didn't want a trac page.
They could go to a bugzilla against the mash package, or to fedora-buildsys-list
Hi Jesse,
Once upon a time Jesse Keating wrote:
On Mon, 2008-05-19 at 17:47 +0200, Roland Wolters wrote:
I'm not sure what the cause of this is, and what I should do about. Should I add /bin/sh as a fixed dependency?
This was a bug in yum one day that caused filedeps to not resolve. This has since been fixed so you can safely ignore the broken dep report that you got.
Perfect, and thx for the quick information :)
Roland
packaging@lists.fedoraproject.org