sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
sb0 has quit [Ping timeout: 245 seconds]
cr1901_modern1 has joined #m-labs
cr1901_modern has quit [Ping timeout: 240 seconds]
evilspirit has joined #m-labs
<whitequark> sb0: yes, if you build noarch packages you should use conda-lin64 only.
rohitksingh has joined #m-labs
<whitequark> sb0: regarding pyqt5: the qt package is now also called qt5
<whitequark> I think this is so that it can be installed in parallel with qt4
<whitequark> (whose package is called just "qt")
<whitequark> I do not have an opinion on this topic
<whitequark> Debian generally puts the ABI version into package name
<whitequark> but putting it just into version would also do
FabM has joined #m-labs
cr1901_modern1 is now known as cr1901_modern
key2 has joined #m-labs
sb0 has joined #m-labs
<GitHub56> [artiq] sbourdeauducq pushed 2 new commits to master: https://git.io/vgEQz
<GitHub56> artiq/master d1e54c8 Sebastien Bourdeauducq: gui/applets: log warning if IPC address not in command
<GitHub56> artiq/master f3f667b Sebastien Bourdeauducq: conda: fix pyqt package name
<bb-m-labs> build #203 of artiq is complete: Failure [failed conda_build] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/203 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<sb0> whitequark, ValueError: Empty version string.
<sb0> whitequark, can you look into pyqtgraph and why import quamash now fails on windows?
<sb0> bb-m-labs: force build --props=package=pyqtgraph conda-lin64
<bb-m-labs> build forced [ETA 12m29s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #45 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://m-labs-buildserver.lan/buildbot/builders/conda-lin64/builds/45
<whitequark> yes, it's the same conda bug
<whitequark> you need to copy the git tree of pyqtgraph into workdir
<sb0> what is workdir? and when do i need to do that?
<whitequark> and you need to do that when it breaks
<whitequark> I've tried to debug the root cause of this three times already, but gave up
<sb0> bb-m-labs: force build --props=package=pyqtgraph conda-lin64
<bb-m-labs> build forced [ETA 12m29s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #46 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://m-labs-buildserver.lan/buildbot/builders/conda-lin64/builds/46
<sb0> whitequark, where do i need to copy it, *exactly*?
<sb0> buildbot@m-labs-buildserver:~/slaves/debian-stretch-amd64-2/conda-lin64$ ls -l
<sb0> total 8
<sb0> drwx------ 4 buildbot buildbot 4096 Feb 7 23:49 build
<sb0> drwxr-xr-x 7 buildbot buildbot 4096 Feb 9 17:56 pyqtgraph
<whitequark> let me see
<whitequark> hm
<whitequark> it's already in the miniconda work directory
<whitequark> let's try a different thing
<whitequark> bb-m-labs: force build --props=package=pyqtgraph conda-lin64
<bb-m-labs> build forced [ETA 12m29s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #47 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://m-labs-buildserver.lan/buildbot/builders/conda-lin64/builds/47
<whitequark> nope
<whitequark> this git thing in the package version is /incredibly fragile/
<whitequark> ok, let me strace it once and for all
sb0 has quit [Quit: Leaving]
<whitequark> *facepalm*
<whitequark> sb0: this is a different bug with identical presentation
<whitequark> the bug is that conda-build doesn't look for git revision in the /source tree/
<whitequark> it looks in the uh
<whitequark> current directory, somehow??
<whitequark> but basically, it's not possible to do the thing you want from pyqtgraph while it doesn't live in its own repo
<whitequark> hm, I have a horrible idea for a fix
<whitequark> that ... worked
<whitequark> but it's too nasty to deploy
<whitequark> oh, ok, I found a better fix
<whitequark> sb0: this should also take care of that hack where someone had to copy workdir manually
<GitHub22> [buildbot-config] whitequark pushed 1 new commit to master: https://github.com/m-labs/buildbot-config/commit/5a0530595c7745d6fa15455230b57a6f84c9da4c
<GitHub22> buildbot-config/master 5a05305 whitequark: Work around conda breakage.
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<whitequark> bb-m-labs: force build --props=package=pyqtgraph conda-lin64
<bb-m-labs> build #48 forced
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> should still break
<whitequark> but in different ways
<bb-m-labs> build #48 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://m-labs-buildserver.lan/buildbot/builders/conda-lin64/builds/48
<whitequark> no? fuck
<whitequark> no. nope. doesn't work
<whitequark> there is no combination of existing conda flags that can make it do what i need
<whitequark> sb0: ok, updating conda-build fixed it
<GitHub109> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/5a9025224829228323617a9da0aa3e6846262cd9
<GitHub109> conda-recipes/master 5a90252 whitequark: Revert "pyqtgraph: fix empty version."...
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<GitHub190> [buildbot-config] whitequark pushed 1 new commit to master: https://github.com/m-labs/buildbot-config/commit/e2fcd5e0e627610ab1e7d5bfacd6832f43bc7f85
<GitHub190> buildbot-config/master e2fcd5e whitequark: Revert "Work around conda breakage."...
<whitequark> bb-m-labs: force build --props=package=pyqtgraph conda-lin64
<bb-m-labs> build #49 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #49 of conda-lin64 is complete: Exception [build exception] Build details are at http://m-labs-buildserver.lan/buildbot/builders/conda-lin64/builds/49
<whitequark> what
<whitequark> oh, right, i put that check here. good thing i did it
<whitequark> sigh
<whitequark> this is just completely insane
<whitequark> --output doesn't even bother to call git
<whitequark> hang on
<whitequark> HAHAHAHAHAHA
<whitequark> so
<whitequark> if I use 1.18.2, --output works properly
<whitequark> but build doesn't
<whitequark> if I use 1.19.0, build works properly
<whitequark> but --output doesn't
<whitequark> ok you know what, my life is too short to spend on this shit
<GitHub73> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/cf0e7c9eee83e1862f084f5fa334070e55660395
<GitHub73> conda-recipes/master cf0e7c9 whitequark: Work around conda breakage.
<whitequark> bb-m-labs: force build --props=package=pyqtgraph conda-lin64
<bb-m-labs> build #50 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #50 of conda-lin64 is complete: Success [build successful] Build details are at http://m-labs-buildserver.lan/buildbot/builders/conda-lin64/builds/50
<whitequark> #YOLO
<whitequark> bb-m-labs: force build --props=package=quamash conda-lin64
<bb-m-labs> build forced [ETA 18 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub2> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/45075f0a0c51285cb1fdf78d1736c852048fad94
<GitHub2> conda-recipes/master 45075f0 whitequark: quamash: fix dep.
<bb-m-labs> build #51 of conda-lin64 is complete: Failure [failed anaconda_upload] Build details are at http://m-labs-buildserver.lan/buildbot/builders/conda-lin64/builds/51
<whitequark> bb-m-labs: force build --props=package=quamash conda-lin64
<bb-m-labs> build forced [ETA 18 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #52 of conda-lin64 is complete: Success [build successful] Build details are at http://m-labs-buildserver.lan/buildbot/builders/conda-lin64/builds/52
<GitHub51> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/16e40fa29160f76b0e477264315fdf247c41cae1
<GitHub51> conda-recipes/master 16e40fa whitequark: quamash: bump.
rohitksingh has quit [Ping timeout: 264 seconds]
rohitksingh has joined #m-labs
evilspirit has quit [Ping timeout: 250 seconds]
evilspirit has joined #m-labs
evilspirit has quit [Ping timeout: 240 seconds]
evilspirit has joined #m-labs
sb0 has joined #m-labs
<sb0> whitequark, it uploaded noarch/pyqtgraph-0.9.10-py_0+git.tar.bz2
<sb0> so this doesn't trigger an update, the previous version was noarch/pyqtgraph-0.9.10-py_105+giteea3752.tar.bz2
<sb0> and quamash is still broken on windows.
<sb0> whitequark, it's not a quamash problem
<sb0> "from PyQt5 import QtCore" -> DLL load failed
sb0 has quit [Quit: Leaving]
kristian1aul has quit [Quit: Reconnecting]
kristianpaul has joined #m-labs
ylamarre has joined #m-labs
ylamarre has quit [Ping timeout: 240 seconds]
ylamarre has joined #m-labs
evilspirit has quit [Ping timeout: 240 seconds]
ylamarre has quit [Ping timeout: 248 seconds]
ylamarre has joined #m-labs
sb0 has joined #m-labs
<bb-m-labs> build #204 of artiq is complete: Failure [failed conda_build] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/204
<sb0> rjo, that's the conda problem I mentioned
key2 has quit [Ping timeout: 240 seconds]
rohitksingh has quit [Quit: Leaving.]
sb0 has quit [Quit: Leaving]
sb0 has joined #m-labs
ylamarre has quit [Quit: ylamarre]
sb0 has quit [Ping timeout: 245 seconds]
sb0 has joined #m-labs
<sb0> whitequark, why was that not a problem before?
rjo has quit [Ping timeout: 250 seconds]
rjo has joined #m-labs
sb0 has quit [Read error: Connection timed out]