Github messages for voidlinux
 help / color / mirror / Atom feed
From: gorecki3 <gorecki3@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: VLSub not automatically loading subs
Date: Tue, 18 Jul 2023 02:06:42 +0200	[thread overview]
Message-ID: <20230718000642.qRgEg7GjIS_P53bmPEKrMbrK-6C8gIRO5aNtdtrJRyQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45045@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

New comment by gorecki3 on void-packages repository

https://github.com/void-linux/void-packages/issues/45045#issuecomment-1639059820

Comment:
 
>Thus, he did not have a cached user agent, compared to other linux distros he tried previously, which, I presume, were deployed before 2022-06-15, thus had the time to do "registration of new user agents" before 2022-06-15.

Apologies if I misunderstood, but when you mention "registration," are you referring to the creation of an account? Because as far 
as I know, I didn't have one. 

>What he could do, instead, would be to deploy another linux distro (Clean state, absolutely no files imported from anywhere else) which he knows previously worked, and see if VLSub works. If it fails like on Void Linux, it may indeed be that "registration of new user agents is stopped" and thus, without a cached user agent, it can't work.

I will attempt to do that. Currently, I have an installation of MX Linux 'Wildflower' on a persistent USB drive where vlsub does work. Later, I plan to create a virtual machine and verify if it functions properly on it.

By the way, I must commend you on your excellent and thorough analysis of the entire situation.

  parent reply	other threads:[~2023-07-18  0:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 21:42 [ISSUE] " gorecki3
2023-07-15  3:18 ` gorecki3
2023-07-15 14:08 ` TeusLollo
2023-07-16 16:09 ` gorecki3
2023-07-16 16:10 ` gorecki3
2023-07-17 20:41 ` TeusLollo
2023-07-18  0:06 ` gorecki3 [this message]
2023-07-18  1:26 ` TeusLollo
2023-07-18  1:28 ` TeusLollo
2023-07-18 12:40 ` gorecki3
2023-07-18 12:42 ` gorecki3
2023-07-18 12:47 ` gorecki3
2023-07-18 12:47 ` gorecki3
2023-07-18 13:10 ` TeusLollo
2023-07-18 13:10 ` TeusLollo
2023-07-18 21:37 ` gorecki3
2023-07-18 22:06 ` gorecki3
2023-07-18 23:30 ` TeusLollo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230718000642.qRgEg7GjIS_P53bmPEKrMbrK-6C8gIRO5aNtdtrJRyQ@z \
    --to=gorecki3@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).