On Sun, 16 Sep 2012 22:06:19 -0400 Mike Frysinger <[email protected]> wrote:
> On Sunday 16 September 2012 11:01:00 Alexis Ballier wrote: > > also, you are missing some bug # for the 'broken deps' part. > > packages that have gained broken deps when the profile was marked > > 'dev', or that you committed with your profile.desc locally > > modified, do not count and are your fault actually... > > wrong. if i'm version bumping a package and i see broken amd64-fbsd > deps, that is not my problem. sounds like i'll simply de-keyword it > in the future and let someone else pick up the pieces. > > do a repoman on the tree. there are multiple packages coming back > right now with broken amd64-fbsd deps. now that the repoman run has finished, lets analyze it: dev-vcs/git/git-1.7.12-r2.ebuild: ~amd64-fbsd(default/bsd/fbsd/amd64/9.0) ['app-text/highlight'] x11-base/xorg-drivers/xorg-drivers-1.13.ebuild: ~amd64-fbsd(default/bsd/fbsd/amd64/9.0) ['x11-drivers/xf86-video-chips', 'x11-drivers/xf86-video-rendition', 'x11-drivers/xf86-video-tseng'] both added and unnoticed when the profile was marked as dev net-misc/wget/wget-1.14.ebuild: ~amd64-fbsd(default/bsd/fbsd/amd64/9.0) ['sys-apps/util-linux'] bumped by you, earlier, probably when you made your local change. util-_linux_ not being keyworded on fbsd is not what I would call a broken dep. uuid functions are provided by either e2fsprogs-libs or the libc on freebsd. maybe it would be a good idea to drop keywords and ask for rekeywording to the arch team in that case ?
