| Summary: | datetime error in python3-MythTV | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | Greg Woods <greg> |
| Component: | mythtv | Assignee: | Richard <hobbes1069> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | jarod, leigh123linux |
| Priority: | P1 | ||
| Version: | f32 | ||
| Hardware: | x86_64 | ||
| OS: | GNU/Linux | ||
| namespace: | |||
Sure, I thought it was more recent than that, but this year has gone by very quickly. The packages should make it into testing on the next packaging run. Thank you for the fast response. I will wait for the packages to show up in the repo. The packages filtered through testing and showed up in the repo, but when I try to update, I get this: Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): mythffmpeg x86_64 31.0-9.20200829gitab0c38a476.fc32 rpmfusion-free-updates 7.8 M python3-MythTV ]# dnf --disableexcludepkgs=mythtv* --best --allowerasing update Last metadata expiration check: 2:46:46 ago on Sat 05 Sep 2020 07:21:28 AM MDT. Error: Problem 1: cannot install the best update candidate for package mythffmpeg-31.0-3.20200527gitfc90482281.fc32.x86_64 - cannot install both mythffmpeg-31.0-9.20200829gitab0c38a476.fc32.x86_64 and mythffmpeg-31.0-3.20200527gitfc90482281.fc32.x86_64 - package mythtv-31.0-3.20200527gitfc90482281.fc32.x86_64 requires mythffmpeg(x86-64) = 31.0-3.20200527gitfc90482281.fc32, but none of the providers can be installed - problem with installed package mythtv-31.0-3.20200527gitfc90482281.fc32.x86_64 Problem 2: cannot install the best update candidate for package python3-MythTV-31.0-3.20200527gitfc90482281.fc32.noarch - cannot install both python3-MythTV-31.0-9.20200829gitab0c38a476.fc32.noarch and python3-MythTV-31.0-3.20200527gitfc90482281.fc32.noarch - package mythtv-frontend-31.0-3.20200527gitfc90482281.fc32.x86_64 requires python3-MythTV = 31.0-3.20200527gitfc90482281.fc32, but none of the providers can be installed - problem with installed package mythtv-frontend-31.0-3.20200527gitfc90482281.fc32.x86_64 (try to add '--skip-broken' to skip uninstallable packages) ...and none of the MythTV packages get updated. I have seen some cases where this type of brokenness can be resolved by erasing the old version so the new one can be installed, but then I get: ]# dnf erase mythffmpeg-31.0-3.20200527gitfc90482281.fc32.x86_64 Error: Problem: package mythtv-31.0-3.20200527gitfc90482281.fc32.x86_64 requires mythffmpeg(x86-64) = 31.0-3.20200527gitfc90482281.fc32, but none of the providers can be installed - conflicting requests - problem with installed package mythtv-31.0-3.20200527gitfc90482281.fc32.x86_64 (try to add '--skip-broken' to skip uninstallable packages) Is there a problem with declared dependencies in the mythtv packages or did I royally mess up my system somehow? I suppose I could try completely removing all the Mythtv packages and reinstalling the new version, but I'm a bit afraid to do that in the middle of the Stanley Cup Playoffs. No, I'll take a deeper look. I wouldn't uninstall anything just in case. Ok, I'm sure there's a reason it can't upgrade but untangling dnf's output can be very difficult. It's also somewhat hard to read with the wrapping BZ does to the output. Could you get a full log and attach it? dnf upgrade mythtv 2>&1 > upgrade.log or something like that. I just upgraded my home system and it seemed to update fine. The other option is to force erase mythffmpeg rpm -e --nodeps mythffmpeg Then updating mythtv should re-install it. I don't think it's your packages. I think, in the end, it is because running dnf with "--disableexcludes=main" and "--disableexcludepkgs=mythtv*" don't quite do the same thing. The latter does not actually prevent things like mythffmpeg or Python3-MythTV from being excluded, which causes the missing dependencies. So the second part of this issue was totally my fault. The reason for the excludes in the first place is that I didn't want dnf to update Myth or Bacula until I was ready to do it on all my systems at once. Both Myth and Bacula can fail to work properly if there is a version mismatch between client and server. This is complicated by the fact that some of my systems that use Myth and Bacula are not Fedora (I have a Raspberry Pi 4 front end for one). In the end, what worked was: # dnf --disableexcludes=main update mythtv\* That prevents Bacula packages from being updated, but allows it to pull in whatever the mythtv packages need. Thank you for getting the packages updated so quickly and sorry for the extra noise. |
I am trying to use the find_orphans.py script from the MythTV Wiki on my Fedora 32 system with MythTV packages from RPM Fusion. This is version 31.0-3.20200527gitfc90482281.fc32 . The script crashes with this traceback: Traceback (most recent call last): File "/usr/local/bin/find_orphans.py", line 230, in <module> main() File "/usr/local/bin/find_orphans.py", line 214, in main opt[1](opt[2]) File "/usr/local/bin/find_orphans.py", line 129, in delete_recs rec.delete(True, True) File "/usr/lib/python3.8/site-packages/MythTV/dataheap.py", line 377, in delete return self.getProgram().delete(force, rerecord) File "/usr/lib/python3.8/site-packages/MythTV/mythproto.py", line 975, in delete res = int(be.deleteRecording(self, force=force)) File "/usr/lib/python3.8/site-packages/MythTV/mythproto.py", line 671, in deleteRecording [command,program.toString()])) File "/usr/lib/python3.8/site-packages/MythTV/mythproto.py", line 965, in toString return BACKEND_SEP.join(self._deprocess()) File "/usr/lib/python3.8/site-packages/MythTV/altdict.py", line 178, in _deprocess data[i] = self._inv_trans[self._field_type[i]](v) File "/usr/lib/python3.8/site-packages/MythTV/altdict.py", line 113, in <lambda> lambda x: str(int(x.timestamp())), File "/usr/lib/python3.8/site-packages/MythTV/utility/dt.py", line 481, in timestamp return ((utc_naive - utc_epoch).total_seconds()) TypeError: can't subtract offset-naive and offset-aware datetimes This is apparently because Python 3.8 changed some things about how datetime values are handled. After some discussion on the MythTV users list, one of the developers says that this was fixed in MythTV in June 2020. The embedded date in the latest RPM Fusion version number is for May 27, 2020. Is there any way the MythTV packages could be updated? Thank you, --Greg