Skip to content

Updated snapcraft yaml #720

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

Merged
merged 5 commits into from
Oct 24, 2022
Merged

Updated snapcraft yaml #720

merged 5 commits into from
Oct 24, 2022

Conversation

kz6fittycent
Copy link
Contributor

@kz6fittycent kz6fittycent commented Oct 17, 2022

Changes:

  • Core20 (newer Ubuntu packages)
  • Added needed plugs
    • home
    • network
  • Adopt-info - easier snap versioning
  • License info

That said, I'm still getting the following error:

Traceback (most recent call last):
  File "/snap/maigret2/x1/bin/maigret", line 8, in <module>
    sys.exit(run())
  File "/snap/maigret2/x1/lib/python3.8/site-packages/maigret/maigret.py", line 726, in run
    loop.run_until_complete(main())
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "/snap/maigret2/x1/lib/python3.8/site-packages/maigret/maigret.py", line 717, in main
    db.save_to_file(db_file)
  File "/snap/maigret2/x1/lib/python3.8/site-packages/maigret/sites.py", line 304, in save_to_file
    with open(filename, "w") as f:
OSError: [Errno 30] Read-only file system: '/snap/maigret2/x1/lib/python3.8/site-packages/maigret/resources/data.json'

It's possible that the code isn't looking in /home/$USER to place the report - which poses a problem for the snap (read-only).

Anyway, I hope this helps in some way - I ran the scan and sheesh - that's kind of scary...

@soxoj
Copy link
Owner

soxoj commented Oct 24, 2022

Thank you!

@soxoj soxoj merged commit ec1aaac into soxoj:main Oct 24, 2022
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.

2 participants