Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 0.4.0 #148

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open

Conversation

paul-mannino
Copy link

Preparing a 0.4.0 release, as requested in #147. Built & tested examples on Ubuntu 18.04.

Let me know if there's any work I missed.

@paul-mannino
Copy link
Author

failing in CI for freebsd, but the way the error message reads, it seems like it's not related to the pull or the state of the codebase. Looks like it might be CI config related & has been failing for a while now.

@delehef
Copy link

delehef commented Jul 20, 2020

failing in CI for freebsd, but the way the error message reads, it seems like it's not related to the pull or the state of the codebase. Looks like it might be CI config related & has been failing for a while now.

Hi,

I just tested it for confirmation on a clean FreeBSD 12.0-RELEASE VM I have, and it builds, runs and tests perfectly. The error in the CI looks like it stems from a misconfiguration of FreeBSD's pkg.

Thanks for your work!

@zargony
Copy link
Owner

zargony commented Jul 29, 2020

Thanks for your help. Actually I was expecting to release 0.4.0 based on the 0.3.0 branch since changes in master are pretty much under development, a lot of things are in a flux and I don't think it's ready for a release yet (E.g. there's two different Filesystem traits, a lot of duplicate types because of the introduced lowlevel module). It's supposed to be cleaned up once #126 is ready, but this isn't the case yet.

@zargony
Copy link
Owner

zargony commented Jul 29, 2020

@delehef do you think it's a misconfiguration on Cirrus CI's side or on our side? Unfortunately I'm not so familiar with the FreeBSD package system. Do you have an idea how this could be fixed?

@delehef
Copy link

delehef commented Jul 29, 2020

@delehef do you think it's a misconfiguration on Cirrus CI's side or on our side? Unfortunately I'm not so familiar with the FreeBSD package system. Do you have an idea how this could be fixed?

Definitely looks like their pkg (FreeBSD's package manager) configuration is borked, I don't see how it could be on our side.

Do you have an idea how this could be fixed?

11.0 is relatively old, Could Cirrus be setup to use a more recent FreeBSD release?

@delehef
Copy link

delehef commented Jul 29, 2020

Looks like tokio met the same problem, and updating to FreeBSD 12.1 fixed it!

@zargony
Copy link
Owner

zargony commented Jul 29, 2020

Looks like tokio met the same problem, and updating to FreeBSD 12.1 fixed it!

Thanks! Should be fixed with #149

@paul-mannino paul-mannino force-pushed the release-4.0 branch 2 times, most recently from 8ae837b to 591f7a4 Compare August 4, 2020 02:22
@paul-mannino
Copy link
Author

@zargony I realize I forgot to ping you on this, but I prepared something that is hopefully closer to what you were looking for. I cherry-picked/backported changes off master that were related to bug fixes or removing that deprecated time dependency. Left this up as a PR even though obviously this wouldn't be merged.

@oxalica
Copy link

oxalica commented Oct 21, 2020

Any update here? I'm also waiting for 0.4.0

@theduke
Copy link

theduke commented Nov 23, 2020

@zargony friendly ping, also waiting for this.

@theduke
Copy link

theduke commented Nov 23, 2020

FYI: there is an actively maintained fork of this project here: https://github.com/cberner/fuser

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants