Date: Mon, 22 Feb 2016 09:34:36 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 207376] [unbreak] devel/roboctl Restored distfile Message-ID: <bug-207376-13-H6ANfqvx8e@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-207376-13@https.bugs.freebsd.org/bugzilla/> References: <bug-207376-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207376 --- Comment #4 from Raphael Kubo da Costa <rakuco@FreeBSD.org> --- > BTW, I never received notification that the port was marked broken. Aren'= t maintainers normally notified automatically when a package build fails? = I checked my spam and trash folders:nothing. I _think_ you should get weekly nags from pkg-fallout when the cluster fail= s to build a port, though I don't see anything in the freebsd-pkg-fallout mailing list archives indeed. It might have been the case that bapt was overzealous= in port r403636 and marked it broken before it was caught by a cluster build (since that commit marks several ports broken). With that said, `make checksum' fails here with the new tarball uploaded to= the master site: =3D> Attempting to fetch http://acadix.biz/Ports/distfiles/roboctl-0.3.8.ta= r.xz fetch: http://acadix.biz/Ports/distfiles/roboctl-0.3.8.tar.xz: size mismatc= h: expected 270384, actual 270476 =3D> Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/roboctl-0.3.8.tar.xz roboctl-0.3.8.tar.xz 100% of 264 kB 122 kBps 00m= 03s --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-207376-13-H6ANfqvx8e>