Location: https://codeload.github.com/umlaeute/v4l2loopback/tar.gz/v0.12.5 [following] --2020-08-17 11:20:57-- https://codeload.github.com/umlaeute/v4l2loopback/tar.gz/v0.12.5 Resolving codeload.github.com... 13.250.162.133 Connecting to codeload.github.com|13.250.162.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/x-gzip] Saving to: ‘/usr/portage/distfiles/v4l2loopback-0.12.5.tar.gz.__download__’ 0K .......... .......... .......... .......... .......... 4.20M 50K 7.55M=0.01s 2020-08-17 11:20:58 (4.21 MB/s) - ‘/usr/portage/distfiles/v4l2loopback-0.12.5.tar.gz.__download__’ saved [51468] !!! Fetched file: v4l2loopback-0.12.5.tar.gz VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 51468 !!! Expected: 51484 Refetching... File renamed to '/usr/portage/distfiles/v4l2loopback-0.12.5.tar.gz._checksum_failure_.d1xhg2ph'
Looks like the only change in the upstream tarball is renaming the top level dir umlaeute-v4l2loopback-44e1a90/ to v4l2loopback-0.12.5/ , FYI
Tarball on distfiles.gentoo.mirror contains a toplevel "umlaeute-v4l2loopback-44e1a90/" directory. Current upstream tarball contains a toplevel "v4l2loopback-0.12.5". Contents are identical.
Is maintainer dead? Why it takes so long to update a manifest file?
This is a very very minor issue since there is no problem for anyone with working GENTOO_MIRRORS setting (as there is by default) I can make this change soon, but I would also suggest that you fix your GENTOO_MIRRORS
I'm using one of official and current gentoo mirrors. However, the file seems missing on the mirror: >>> Fetching (1 of 1) media-video/v4l2loopback-0.12.5-r1::gentoo >>> Downloading 'http://mirror.rise.ph/gentoo/distfiles/78/v4l2loopback-0.12.5.tar.gz' --2020-10-25 10:00:52-- http://mirror.rise.ph/gentoo/distfiles/78/v4l2loopback-0.12.5.tar.gz Resolving mirror.rise.ph... 43.226.6.79 Connecting to mirror.rise.ph|43.226.6.79|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2020-10-25 10:00:52 ERROR 404: Not Found. >>> Downloading 'https://github.com/umlaeute/v4l2loopback/archive/v0.12.5.tar.gz' --2020-10-25 10:00:53-- https://github.com/umlaeute/v4l2loopback/archive/v0.12.5.tar.gz Resolving github.com... 192.30.255.113 Connecting to github.com|192.30.255.113|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://codeload.github.com/umlaeute/v4l2loopback/tar.gz/v0.12.5 [following] --2020-10-25 10:00:54-- https://codeload.github.com/umlaeute/v4l2loopback/tar.gz/v0.12.5 Resolving codeload.github.com... 13.112.159.149 Connecting to codeload.github.com|13.112.159.149|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/x-gzip] Saving to: ‘/usr/portage/distfiles/v4l2loopback-0.12.5.tar.gz.__download__’ /usr/portage/distfiles/v [ <=> ] 50.26K 312KB/s in 0.2s 2020-10-25 10:00:54 (312 KB/s) - ‘/usr/portage/distfiles/v4l2loopback-0.12.5.tar.gz.__download__’ saved [51468] !!! Fetched file: v4l2loopback-0.12.5.tar.gz VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 51468 !!! Expected: 51484 Refetching... File renamed to '/usr/portage/distfiles/v4l2loopback-0.12.5.tar.gz._checksum_failure_.3g77m366' !!! Couldn't download 'v4l2loopback-0.12.5.tar.gz'. Aborting. * Fetch failed for 'media-video/v4l2loopback-0.12.5-r1'
According to the mirrorstats page [1], that mirror is 277 days out of date (it hasn't received new files in that long). That matches the Jan 22 date I see on the dirs here: http://mirror.rise.ph/gentoo/ https://mirrorstats.gentoo.org/distfiles/
(In reply to Ben Kohler from comment #6) > According to the mirrorstats page [1], that mirror is 277 days out of date > (it hasn't received new files in that long). That matches the Jan 22 date I > see on the dirs here: http://mirror.rise.ph/gentoo/ > > https://mirrorstats.gentoo.org/distfiles/ This is half true. Yes, that http mirror is outdated (thanks for pointing out) but it's been synced just a few hours ago. Its "last stat" is also "OK". The same story with other Gentoo mirrors - 30% of them (102 were ok, 36 had no time) are out of sync. You will probably get 40% if you add mirror.rise.ph and few others with "OK" status. The point is, your statement "there is no problem for anyone with working GENTOO_MIRRORS setting (as there is by default)" is not realistic and mirrors are not reliable because 30-40% of them (as of today) are out of sync. Please fix the root cause asap.
I don't know what you are trying to prove to me, you are using a bad mirror. That 30% number isn't too relevant here, almost all mirrors are either very up to date, or completely unreachable. I'm sorry that there are so many unreachable/down mirrors still listed there, but it's not relevant here. The underlying v4l2loopback issue does need to be fixed, but it's much less urgent than you are suggesting, because anyone with a proper gentoo mirrors setup is not affected. Yes, the mirrorstats page says your mirror is reachable, but with stale data. I don't know why this gets marked as OK there, it is "not OK".
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=451ffeb436e7e9f42f7dd4043e1a523ce282a64d commit 451ffeb436e7e9f42f7dd4043e1a523ce282a64d Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2020-10-26 12:05:01 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2020-10-26 14:13:37 +0000 media-video/v4l2loopback: adjust manifest for slight tarball change Inspected new tarball, only difference is in the top level dir name. Bug: https://bugs.gentoo.org/737512 Package-Manager: Portage-3.0.8, Repoman-3.0.2 Signed-off-by: Ben Kohler <bkohler@gentoo.org> media-video/v4l2loopback/Manifest | 2 +- media-video/v4l2loopback/v4l2loopback-0.12.5-r1.ebuild | 1 - 2 files changed, 1 insertion(+), 2 deletions(-)
*** Bug 751457 has been marked as a duplicate of this bug. ***
This should be fixed now, can you open a bug report about your bad mirror though? Thanks
