On Sun, Aug 21, 2016 at 11:27:14PM +0300, Adrian Bunk wrote:
> On Sun, Aug 21, 2016 at 09:55:26PM +0200, Santiago Vila wrote:
> > On Sun, Aug 21, 2016 at 10:49:22PM +0300, Adrian Bunk wrote:
> > > On Sun, Aug 21, 2016 at 09:05:19PM +0200, Santiago Vila wrote:
> > > > When a package fails to build f
On Sun, Aug 21, 2016 at 11:06:02PM +0300, Adrian Bunk wrote:
> What misled me was that the first build was successful and only the
> second build failed.
>
> The failure in the second build is:
> === RUN TestInotifyStress
> --- FAIL: TestInotifyStress (5.00s)
> inotify_test.go:236: Creat
On Sun, Aug 21, 2016 at 09:55:26PM +0200, Santiago Vila wrote:
> On Sun, Aug 21, 2016 at 10:49:22PM +0300, Adrian Bunk wrote:
> > On Sun, Aug 21, 2016 at 09:05:19PM +0200, Santiago Vila wrote:
> > > When a package fails to build from source, there are no runtime
> > > problems at all, because the b
Disclaimer:
I am not a maintainer of this package.
On Sun, Aug 21, 2016 at 09:21:15PM +0200, Santiago Vila wrote:
> On Sun, Aug 21, 2016 at 09:57:14PM +0300, Adrian Bunk wrote:
>
> > For the "cannot build twice in a row" issue please file yet another
> > (non-RC) bug.
>
> I think you misunders
On Sun, Aug 21, 2016 at 10:49:22PM +0300, Adrian Bunk wrote:
> On Sun, Aug 21, 2016 at 09:05:19PM +0200, Santiago Vila wrote:
> > Ok, sorry, but then please retitle the bug and drop the FTBFS word.
>
> I am just a random person going through RC bugs, but that sounds like a
> good idea so I'm doin
retitle 819452 golang-fsnotify: not working at all in ppc64el, arm64
thanks
On Sun, Aug 21, 2016 at 09:05:19PM +0200, Santiago Vila wrote:
> On Sun, Aug 21, 2016 at 09:57:14PM +0300, Adrian Bunk wrote:
>
> > Please don't hijack an existing bug for an obviously unrelated issue,
> > or actually for
On Sun, Aug 21, 2016 at 09:57:14PM +0300, Adrian Bunk wrote:
> For the "cannot build twice in a row" issue please file yet another
> (non-RC) bug.
I think you misunderstood my reference to reproducible builds completely.
When I said "fails on reproducible builds" I did not mean that the two
bui
On Sun, Aug 21, 2016 at 09:57:14PM +0300, Adrian Bunk wrote:
> Please don't hijack an existing bug for an obviously unrelated issue,
> or actually for two other issues that are both unrelated to this bug.
>
> #819452 is about runtime problems on 64bit ppc and ARM, build problems
> on other archi
severity 819452 important
thanks
On Fri, Aug 19, 2016 at 05:06:27PM +0200, Santiago Vila wrote:
> severity 819452 serious
> thanks
>
> I could not build this package while checking for "dpkg-buildpackage -A",
> and it also fails on reproducible builds:
>
> https://tests.reproducible-builds.org/d
severity 819452 serious
thanks
I could not build this package while checking for "dpkg-buildpackage -A",
and it also fails on reproducible builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-fsnotify.html
Raising severity accordingly.
Thanks.
On 29/03/16 00:17, Tianon Gravi wrote:
> Do you think it'd make sense to exclude ppc64el and arm64 from
> "Architectures" on this package until that upstream bug is resolved?
I think that would be a sane approach, it does not seem like there is
any obvious fix to this for now. You should exclude
forwarded 819452 https://github.com/fsnotify/fsnotify/issues/130
thanks
On 28 March 2016 at 10:30, Martín Ferrari wrote:
> As I reported upstream (https://github.com/fsnotify/fsnotify/issues/130),
> fsnotify does not seem to work at all in ppc64el. I noticed this when trying
> to
> solve a FTBFS
Source: golang-fsnotify
Version: 1.2.9-1
Severity: important
Tags: upstream
As I reported upstream (https://github.com/fsnotify/fsnotify/issues/130),
fsnotify does not seem to work at all in ppc64el. I noticed this when trying to
solve a FTBFS in prometheus, that can be tracked down to this module
13 matches
Mail list logo
