Dale wrote:
> David Haller wrote:
>> Hello,
>>
>> On Tue, 27 Oct 2020, Dale wrote:
>>> This is what the conf file looks like now.  I took out the format
>>> option.  Add it back later when this current issue is settled. 
>>>
>>> --format
>>> 'bestvideo[ext=webm][width<=?1280]+bestaudio/bestvideo[ext=mp4][width<=?1280]+bestaudio/best'
>> Is that one or two lines? It think it should be one! I.e.:
>>
>> --format foo
>>
>> Try:
>>
>> --format 
>> 'bestvideo[ext=webm][width<=?1280]+bestaudio/bestvideo[ext=mp4][width<=?1280]+bestaudio/best'
>>
>> Or, I think it's equivalent:
>>
>> --format 'bestvideo[ext=webm,ext=mp4][width<=?1280]+bestaudio/best'
>>
>> HTH,
>> -dnh
>>
>
> It doesn't like that either.  The original is one line.  That said, I
> read where you can put one option on each line and have multiple lines. 
> The top line is what I already had so I tried the second one.  It gave
> me this.
>
>
> ERROR: 'ytdl-format=bestvideo[height<=?1280]+bestaudio/best' is not a
> valid URL. Set --default-search "ytsearch" (or run  youtube-dl
> "ytsearch:ytdl-format=bestvideo[height<=?1280]+bestaudio/best" ) to
> search YouTube
> [youtube] byTOZIvyXPo: Downloading webpage
>
>
> It seems to see something as a URL instead of a option.  Thing is, when
> I google, I find a lot of people using the exact same line.  I'm
> beginning to wonder if Arve has a point.  Maybe something else changed
> and that changed how youtube-dl works.  To test, I wanted to re-emerge
> youtube-dl.  When I tried, I got this little bit of spit up on my
> keyboard. 
>
>
> root@fireball / # emerge -a youtube-dl
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R   *] net-misc/youtube-dl-99999999::gentoo  USE="-test"
> PYTHON_TARGETS="python3_7 -python3_6 -python3_8" 0 KiB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
>
> Would you like to merge these packages? [Yes/No] y
>>>> Verifying ebuild manifests
>>>> Emerging (1 of 1) net-misc/youtube-dl-99999999::gentoo
>>>> Failed to emerge net-misc/youtube-dl-99999999, Log file:
>>>>   '/var/log/portage/net-misc:youtube-dl-99999999:20201028-012948.log'
>>>> Jobs: 0 of 1 complete, 1 failed                 Load avg: 2.00,
> 1.70, 1.60
>  * Package:    net-misc/youtube-dl-99999999
>  * Repository: gentoo
>  * Maintainer: j...@gentoo.org
>  * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
> python_targets_python3_7 userland_GNU
>  * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
>>>> Unpacking source...
>  * Repository id: ytdl-org_youtube-dl.git
>  * To override fetched repository properties, use:
>  *   EGIT_OVERRIDE_REPO_YTDL_ORG_YOUTUBE_DL
>  *   EGIT_OVERRIDE_BRANCH_YTDL_ORG_YOUTUBE_DL
>  *   EGIT_OVERRIDE_COMMIT_YTDL_ORG_YOUTUBE_DL
>  *   EGIT_OVERRIDE_COMMIT_DATE_YTDL_ORG_YOUTUBE_DL
>  *
>  * Fetching https://github.com/ytdl-org/youtube-dl/ ...
> git fetch https://github.com/ytdl-org/youtube-dl/ +HEAD:refs/git-r3/HEAD
> fatal: could not read Username for 'https://github.com': terminal
> prompts disabled
>  * ERROR: net-misc/youtube-dl-99999999::gentoo failed (unpack phase):
>  *   Unable to fetch from any of EGIT_REPO_URI
>  *
>  * Call stack:
>  *     ebuild.sh, line  125:  Called src_unpack
>  *   environment, line 3655:  Called git-r3_src_unpack
>  *   environment, line 2568:  Called git-r3_src_fetch
>  *   environment, line 2562:  Called git-r3_fetch
>  *   environment, line 2484:  Called die
>  * The specific snippet of code:
>  *       [[ -n ${success} ]] || die "Unable to fetch from any of
> EGIT_REPO_URI";
>  *
>  * If you need support, post the output of `emerge --info
> '=net-misc/youtube-dl-99999999::gentoo'`,
>  * the complete build log and the output of `emerge -pqv
> '=net-misc/youtube-dl-99999999::gentoo'`.
>  * The complete build log is located at
> '/var/log/portage/net-misc:youtube-dl-99999999:20201028-012948.log'.
>  * For convenience, a symlink to the build log is located at
> '/var/tmp/portage/net-misc/youtube-dl-99999999/temp/build.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/net-misc/youtube-dl-99999999/temp/environment'.
>  * Working directory: '/var/tmp/portage/net-misc/youtube-dl-99999999/work'
>  * S:
> '/var/tmp/portage/net-misc/youtube-dl-99999999/work/youtube-dl-99999999'
>  *
>  * The following package has failed to build, install, or execute postinst:
>  *
>  *  (net-misc/youtube-dl-99999999:0/0::gentoo, ebuild scheduled for
> merge), Log file:
>  *   '/var/log/portage/net-misc:youtube-dl-99999999:20201028-012948.log'
>  *
> root@fireball / #
>
>
> Is that because RIAA made them remove something or have I found a whole
> new problem?  o-O
>
> Dale
>
> :-)  :-) 
>


Howdy,

It's been rough since my last message.  My puter made a fairly loud pop
sound and then went dark.  Trust me, it went dark in here.  My monitors
and everything went black.  That's not something this room sees much. 
Anyway, my power supply decided to take a long nap.  The primary
capacitor went out.  It's still in tact and all but it is domed up
pretty good.  I'm not sure what made the pop sound since the cap is in
somewhat good shape.  It's domed enough I'm 99.99% sure it started the
mess.  I'm just glad I bought a good one since my mobo and all seems to
be fine.  Those protection circuits did a awesome job.  It was a
ThermalTake that was several years old.  I got my money's worth and then
some. 

I bought a new power supply.  It's a Evga 650 watt, same wattage as old
one.  Sticker says 100-N1-0650-L1.  I had to drive about 70 miles to get
to a big computer store.  The repair guy says he uses them a lot and has
only had one or two go out under warranty.  He said the protection
circuits work good on those and protected the mobo etc.  I'll do more
research later on and order a better one if needed. 

I'm thinking about replacing that cap and seeing if it works.  I've
repaired a few monitors that way but my question is, should I trust it
after replacing that cap even if it works??  Should it be load tested or
something?  Does the protection circuitry only work once? 

Trying to get things back going here.  Just glad my baby has that
annoyingly bright blue LED back on.  ROFL 

Dale

:-)  :-) 

Reply via email to