-
Notifications
You must be signed in to change notification settings - Fork 397
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
fix unavailable repo for pi-rc522 #2075
Merged
pabera
merged 5 commits into
MiczFlor:future3/develop
from
AlvinSchiller:future3/fix/pi-rc522
Oct 10, 2023
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
eab4636
fix unavailable repo for pi-rc522. Use fix version to ensure compatib…
AlvinSchiller 606a317
build trigger
AlvinSchiller 923db30
REVERT build trigger
AlvinSchiller d1a2959
fixed sphinx gpiozero version for pyton < 3.8
AlvinSchiller 299641b
fixed sphinx gpiozero version for pyton >= 3.8
AlvinSchiller File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9 changes: 1 addition & 8 deletions
9
src/jukebox/components/rfid/hardware/rc522_spi/requirements.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,6 @@ | ||
# RC522 related requirements | ||
# You need to install these with `sudo python3 -m pip install --upgrade --force-reinstall -q -r requirements.txt` | ||
|
||
# pi-rc522 use latest version from Github | ||
# This is the original versions. Seems unmaintained for the moment | ||
# git+https://github.com/ondryaso/pi-rc522.git#egg=pi-rc522 | ||
|
||
# The fork of kevinvalk has some good improvements | ||
# https://github.com/kevinvalk/pi-rc522 | ||
# Get the kevinvalk fork yet again from a different fork which ensures compatibility with the Phoniebox | ||
git+https://github.com/ChisSoc/pi-rc522.git#egg=pi-rc522 | ||
pi-rc522==2.3.0 | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes me curious why ChisSoc had used their own fork instead of the fork from kevinvalk.
Since the dependency from ChisSoc has been deleted, we can't check if had updated some of the code. Let's hope were no major updates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it was for compatibility, so further changes to the kevinvalk fork wouldn't break things in phoniebox, as it was always the latest commit used. Ironically it was now the case with his fork.
With the specific release in the original repo this is not a problem anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will check if i have maybe an old installation somewhere on sd. Maybe there is a way to extract the files and compare them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unfortunately i dont have an old installation. Does someone of you maybe have one?
The installed files can be found at "/usr/local/lib/python3.9/dist-packages/pirc522" and copied for comparison.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pirc522.zip
Here is the content from a installation from June 4th. Hope it helps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was this a 2.x or 3.x installation? Looks like 2.x from the diff.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, 2.4.0. You needed 3.x? Then I'm sorry... 😢
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, was about 3.x.
But thanks anyway :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like to pick-up this older discussion as I realized a difference when not using ChisSoc's version. My Mifare Ultralight C sticker do not work on a minimal hardware setup (battery powered RPi Zero 2) with the current rc522 package, but were fine with ChisSoc's version. I was unable to identify the actual issue but found that using the read_id function of the current rc522 package does the job properly. See my suggestion #2214.