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
rapid-photo-downloader: 0.9.13 -> 0.9.14 #59347
Conversation
@jfrankenau, as maintainer of rapid-photo-downloader, I'd appreciate your review. @dotlambda, you helped out with unblocking #56815, your review would also be appreciated. |
@GrahamcOfBorg build rapid-photo-downloader |
4013be5
to
a673f6f
Compare
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'm seeing
Ran 0 tests in 0.001s
Was this the case before? We should set doCheck = false
and add a comment with the reason if there are no tests.
The --- nocheck.txt 2019-04-14 19:37:14.927437916 +0100
+++ check.txt 2019-04-14 19:37:18.031466371 +0100
@@ -538,4 +538,33 @@
wrapping `/nix/store/...-rapid-photo-downloader-0.9.14/bin/analyze-pv-structure'...
Rewriting #!/nix/store/lmwk7mg8y79m3izdxdlckdn385x7jgl7-python3-3.7.3/bin/python3.7 to #!/nix/store/lmwk7mg8y79m3izdxdlckdn385x7jgl7-python3-3.7.3
wrapping `/nix/store/...-rapid-photo-downloader-0.9.14/bin/rapid-photo-downloader'...
+running install tests
+running test
+running egg_info
+writing rapid_photo_downloader.egg-info/PKG-INFO
+writing dependency_links to rapid_photo_downloader.egg-info/dependency_links.txt
+writing entry points to rapid_photo_downloader.egg-info/entry_points.txt
+writing requirements to rapid_photo_downloader.egg-info/requires.txt
+writing top-level names to rapid_photo_downloader.egg-info/top_level.txt
+reading manifest file 'rapid_photo_downloader.egg-info/SOURCES.txt'
+reading manifest template 'MANIFEST.in'
+warning: no files found matching '*.txt' under directory 'raphodo'
+warning: no previously-included files matching '*~' found anywhere in distribution
+warning: no previously-included files matching '*.pyc' found anywhere in distribution
+warning: no previously-included files matching '*~1~' found anywhere in distribution
+warning: no previously-included files matching '*~2~' found anywhere in distribution
+warning: no previously-included files matching '*bak' found anywhere in distribution
+warning: no previously-included files found matching 'raphodo/test.py'
+warning: no previously-included files found matching 'raphodo/test2.py'
+no previously-included directories found matching 'tasks'
+no previously-included directories found matching 'raphodo/tests'
+no previously-included directories found matching 'debian'
+no previously-included directories found matching 'images'
+writing manifest file 'rapid_photo_downloader.egg-info/SOURCES.txt'
+running build_ext
+
+----------------------------------------------------------------------
+Ran 0 tests in 0.000s
+
+OK
postPatchMkspecs ...and parts fail without --- check.txt 2019-04-14 19:37:18.031466371 +0100
+++ check-without-exiftool.txt 2019-04-14 19:38:00.453815232 +0100
@@ -562,6 +562,7 @@
no previously-included directories found matching 'images'
writing manifest file 'rapid_photo_downloader.egg-info/SOURCES.txt'
running build_ext
+ERROR:root:Unable to compare ExifTool version number:
----------------------------------------------------------------------
Ran 0 tests in 0.000s But as far as I can tell, there aren't any actual unit tests in the upstream source. The program does contain a bunch of doctests, but they don't appear to run by default, and at least one has a comment stating that it requires actual hardware plugged in before it will pass. ...that said, I'm not seeing a meaningful difference in build time with and without |
Please run these doctests in a |
I don't think that makes sense. If the author intended for them to run regularly, they'd be executed as part of
...which then goes on to test paths that are hardcoded to match the author's environment ( Making these tests run and pass in the general case would require nontrivial patches against upstream. |
Alright, then please set |
This updates Rapid Photo Downloader to 0.9.14 and fixes NixOS#56815 Support for RAW images is not currently functioning; the rawkit bindings are unmaintained and only support libraw <= 0.18, but nixpkgs ships 0.19
a673f6f
to
92c331f
Compare
Done. I still feel bad about disabling the check phase altogether as it adds trivial overhead, but if you think it's better this way, there it is. :) |
Btw, if someone is interested in RAW support, they should make a PR pinning |
This updates Rapid Photo Downloader to 0.9.14 and fixes #56815
Motivation for this change
exiftool
to be present in the user environmentlibmediainfo
Known issues:
Support for RAW images is not fully functional.
Rapid Photo Downloader uses Rawkit bindings to libraw.
Rawkit is unmaintained, and its most recent release does not support libraw 0.19. The nixpkgs collection has included 0.19 since mid-2018.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)