Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Matthew R. Becker
    @beckermr
    so if you remove that file and rerender, then you'll get global pins
    they are generally fine unless your package has special requirements
    so i'd just use them
    Mike Boyle
    @moble
    Okay. My only requirement is numpy >=1.13, which is presumably going to be safe nowadays. Thanks!
    Matthew R. Becker
    @beckermr
    :100:
    Uwe L. Korn
    @xhochy
    I think I asked it at least 3-4 times before: But where do I need to look to find all packages that use bazel in build or host?
    Seems like I should document that once I know how it works.
    Chris Burr
    @chrisburr
    There might be a better way I normally use ripgrep with a local clone of https://github.com/regro/libcfgraph
    Wolf Vollprecht
    @wolfv
    @xhochy we also have a metadata extractor plugin (same as used for libcfgraph) on the beta.mamba.pm instance
    we can run it over all packages and make the recipes "searchable"
    (but the github search in the libcfgraph repo might also work fine for the moment)
    Matthew R. Becker
    @beckermr
    you can load the graph itself to check
    agreed a searchable thing online would be much better
    I keep a notebook that loads the graph lying around
    can be useful for such tasks
    Jason Grout
    @jasongrout
    We're trying to figure out if there is a way to get the autobot to do prereleases or releases on branches other than the main branch of a feedstock (for example, previous release branches that are still in maintenance). Nick found something that seemed maybe relevant: conda-forge/jupyterlab-feedstock#267
    Chris Burr
    @chrisburr
    @jasongrout Not currently but it would be a really useful addition to the bot if you're able to look into making a PR
    (I think there is an issue somewhere for it, I'll look it up if you're interested)
    Jason Grout
    @jasongrout
    Where is the code for the bot? I looked for a while but couldn't find it
    Chris Burr
    @chrisburr
    Jason Grout
    @jasongrout
    Cool, thanks
    Billy K. Poon
    @bkpoon
    Does the version migrator try again later if it fails? It looks like there are several - could not hash URL template errors on the conda-forge status page. I updated my package today and that's the error I'm seeing. The URL with the updated version is working. Thanks!
    Michael Goerz
    @goerz
    I released on PyPI a version 0.5.0rc2 of my docs-versions-menu package which has an existing feedstock. So far, regro-cf-auotick-bot hasn't opened a PR on the feedstock for the new release. Is this expected? Some of the comments here seem to indicate that the bot doesn't react to pre-release version. Is there anything I can do to make the bot generate the new release of the conda package, or will have I have make my own PR by hand?
    Billy K. Poon
    @bkpoon
    My update PR showed up, thanks!
    Matthew R. Becker
    @beckermr
    yay!
    Wolf Vollprecht
    @wolfv
    hey, I just migrated the rhumba R package manager to OSX-ARM64. I had to put r-rcpp into the build section as well
    I guess that could also be automated, right?
    Ryan May
    @dopplershift
    Did something change in the bot? According to the logs, numpy failed the version migration, but nothing has changed in the recipe since the last successful autotick on March 28.
    Matthew R. Becker
    @beckermr
    hmmmm
    we put in one change but it should not have changed this
    Ryan May
    @dopplershift
    Well now that I'm capable of actually reading error messages:
    Matthew R. Becker
    @beckermr
    let's see if the bot fixes itself - could be an HTTP error
    Ryan May
    @dopplershift
    Looks like the last one worked
    Matthew R. Becker
    @beckermr
    nice
    Matthew R. Becker
    @beckermr
    The R migration is going to slam drone pretty hard
    Should we move some packages to emulated builds during it?
    Travis too
    maybe we should wait it out
    Uwe L. Korn
    @xhochy
    We can cross-compile nowadays, no need for emulation but that would need a more sophisticated migratory (i.e. the same code we do for the osx-arm64 migration).
    Matthew R. Becker
    @beckermr
    ah right
    plus testing goes off for that
    not sure how much we care
    let's let it ride
    Uwe L. Korn
    @xhochy
    We can test with QEMU. Builds are fast as native and testing is slow as with emulation. I think @isuruf at least started somewhere a PR to only skip tests on osx-arm64. Not sure where that went.
    I would though just wait though, it's hopefully just a weekend of slowish Drone and most feedstocks are already migrated away from Travis since the R 4.0 migration.
    Isuru Fernando
    @isuruf
    Should be a simple PR
    Matthew R. Becker
    @beckermr
    I did some hacking on the bot to make it tries prs without errors first. R migration was a bit stalled. Hooefully this helps