Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

E: Package 'vlc' has no installation candidate ...

214 views
Skip to first unread message

Albretch Mueller

unread,
Apr 28, 2022, 10:30:05 PM4/28/22
to
How do you install vlc on Debian BUllseye?

these are the relatively weird problems I am having and I couldn't
find much about them specifically online:

# time apt-get update
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Reading package lists... Done

real 0m0.955s
user 0m0.395s
sys 0m0.236s

# time apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
docbook-xml python3-distro sgml-base sgml-data xml-core yelp-xsl
Use 'apt autoremove' to remove them.
The following packages have been kept back:
libjavascriptcoregtk-4.0-18
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

real 0m0.221s
user 0m0.200s
sys 0m0.014s

# time apt-get install vlc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package vlc is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'vlc' has no installation candidate

real 0m0.127s
user 0m0.097s
sys 0m0.022s
#
~

lbrtchx

Greg Wooledge

unread,
Apr 28, 2022, 10:40:05 PM4/28/22
to
On Thu, Apr 28, 2022 at 09:27:11PM -0500, Albretch Mueller wrote:
> How do you install vlc on Debian BUllseye?

> # time apt-get install vlc
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Package vlc is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> E: Package 'vlc' has no installation candidate

Run these commands for additional information:

cat /etc/apt/sources.list
apt policy vlc

Charles Curley

unread,
Apr 29, 2022, 12:20:06 AM4/29/22
to
On Thu, 28 Apr 2022 21:27:11 -0500
Albretch Mueller <lbr...@gmail.com> wrote:

> # time apt-get update
> Hit:1 http://security.debian.org/debian-security bullseye-security
> InRelease Reading package lists... Done
>
> real 0m0.955s
> user 0m0.395s
> sys 0m0.236s

Odd. I would think you would show a few more repos. I see:

root@jhegaala:~# time apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Ign:3 http://repo.vivaldi.com/stable/deb stable InRelease
Get:4 http://repo.vivaldi.com/stable/deb stable Release [3,840 B]
Get:5 http://repo.vivaldi.com/stable/deb stable Release.gpg [833 B]
Get:6 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB]
Hit:7 http://apt.syncthing.net syncthing InRelease
Get:8 http://repo.vivaldi.com/stable/deb stable/main amd64 Packages [1,773 B]
Get:9 https://updates.signal.org/desktop/apt xenial InRelease [2,316 B]
Get:10 https://updates.signal.org/desktop/apt xenial/main amd64 Packages [10.5 kB]
Fetched 58.6 kB in 1s (53.4 kB/s)
Reading package lists... Done

real 0m2.018s
user 0m1.142s
sys 0m0.451s
root@jhegaala:~#

Is your sources.list file set up correctly?

(And why do I have two signal repos???)


--
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Tim Woodall

unread,
Apr 29, 2022, 12:30:05 AM4/29/22
to
On Thu, 28 Apr 2022, Charles Curley wrote:

> On Thu, 28 Apr 2022 21:27:11 -0500
> Albretch Mueller <lbr...@gmail.com> wrote:
>
>> # time apt-get update
>> Hit:1 http://security.debian.org/debian-security bullseye-security
>> InRelease Reading package lists... Done
>>
>
> Odd. I would think you would show a few more repos. I see:

Indeed, this looks like only the security updates are cobfigured.

>
> root@jhegaala:~# time apt-get update
> Hit:1 http://deb.debian.org/debian bullseye InRelease
> Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
> Ign:3 http://repo.vivaldi.com/stable/deb stable InRelease
> Get:4 http://repo.vivaldi.com/stable/deb stable Release [3,840 B]
> Get:5 http://repo.vivaldi.com/stable/deb stable Release.gpg [833 B]
> Get:6 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB]
> Hit:7 http://apt.syncthing.net syncthing InRelease
> Get:8 http://repo.vivaldi.com/stable/deb stable/main amd64 Packages [1,773 B]
> Get:9 https://updates.signal.org/desktop/apt xenial InRelease [2,316 B]
> Get:10 https://updates.signal.org/desktop/apt xenial/main amd64 Packages [10.5 kB]
> Fetched 58.6 kB in 1s (53.4 kB/s)
> Reading package lists... Done
>
> Is your sources.list file set up correctly?
>
> (And why do I have two signal repos???)
>

Do you? Isn't it the Release file and then the Packages file that are
fetched? Presumably you're up to date on the others (except vivaldi)

Tim

Charles Curley

unread,
Apr 29, 2022, 12:40:05 AM4/29/22
to
On Fri, 29 Apr 2022 05:23:57 +0100 (BST)
Tim Woodall <debia...@woodall.me.uk> wrote:

> > (And why do I have two signal repos???)
> >
>
> Do you? Isn't it the Release file and then the Packages file that are
> fetched? Presumably you're up to date on the others (except vivaldi)

Actually, I don't. I misread the output. And you are right, signal and
vivaldi have upgrades available. Thanks.

Albretch Mueller

unread,
Apr 29, 2022, 11:00:05 PM4/29/22
to
On 4/28/22, Greg Wooledge <gr...@wooledge.org> wrote:
> Run these commands for additional information:
>
> cat /etc/apt/sources.list
> apt policy vlc

# date; cat /etc/apt/sources.list
Fri 29 Apr 2022 09:44:06 PM CDT
# deb cdrom:[Official Debian GNU/Linux Live 11.2.0 lxde
2021-12-18T12:41]/ bullseye main

#deb cdrom:[Official Debian GNU/Linux Live 11.2.0 lxde
2021-12-18T12:41]/ bullseye main

deb http://security.debian.org/debian-security bullseye-security main
deb-src http://security.debian.org/debian-security bullseye-security main

# bullseye-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
# A network mirror was not selected during install. The following entries
# are provided as examples, but you should amend them as appropriate
# for your mirror of choice.
#
# deb http://deb.debian.org/debian/ bullseye-updates main
# deb-src http://deb.debian.org/debian/ bullseye-updates main

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
#

# date; apt policy vlc
Fri 29 Apr 2022 09:48:37 PM CDT
vlc:
Installed: (none)
Candidate: (none)
Version table:
#

It may all relate to the fact that I just installed bullseye.

lbrtchx

Albretch Mueller

unread,
Apr 29, 2022, 11:00:05 PM4/29/22
to
# apt-add-repository
-bash: apt-add-repository: command not found
#

Greg Wooledge

unread,
Apr 29, 2022, 11:20:04 PM4/29/22
to
On Fri, Apr 29, 2022 at 09:51:47PM -0500, Albretch Mueller wrote:
> On 4/28/22, Greg Wooledge <gr...@wooledge.org> wrote:
> > Run these commands for additional information:
> >
> > cat /etc/apt/sources.list
> > apt policy vlc
>
> # date; cat /etc/apt/sources.list
> Fri 29 Apr 2022 09:44:06 PM CDT
> [...]
> deb http://security.debian.org/debian-security bullseye-security main
> deb-src http://security.debian.org/debian-security bullseye-security main
> [...]
> # deb http://deb.debian.org/debian/ bullseye-updates main
> # deb-src http://deb.debian.org/debian/ bullseye-updates main

As others already guessed, the problem is that you have the
bullseye-security repository listed, but *not* the main bullseye
repository. You should add that.

Typically you'd use this line:

deb http://deb.debian.org/debian bullseye main

Add " contrib non-free" to it if you require firmware/microcode or
other packages from non-free on your system.

The commented-out bullseye-updates repository is optional. You can add
that if you want. It gives you early access to packages that will be
in the next point release, which aren't security updates.

Albretch Mueller

unread,
Apr 30, 2022, 2:20:05 PM4/30/22
to
I had just installed Debian 11 onto a pen drive and as soon as I
connected my computer to the Internet I started having such problems,
which makes me wonder if the original installation disk was OK.
lbrtchx

Albretch Mueller

unread,
Apr 30, 2022, 5:50:05 PM4/30/22
to
after editing it the unhashed line in my /etc/apt/sources.list are:

deb http://security.debian.org/debian-security bullseye-security main
deb-src http://security.debian.org/debian-security bullseye-security main

deb http://deb.debian.org/debian/ bullseye-updates main
deb-src http://deb.debian.org/debian/ bullseye-updates main

deb http://deb.debian.org/debian bullseye main contrib non-free
deb-src http://deb.debian.org/debian bullseye main contrib non-free

deb http://deb.debian.org/debian-security/ bullseye-security main
contrib non-free
deb-src http://deb.debian.org/debian-security/ bullseye-security main
contrib non-free

deb http://deb.debian.org/debian bullseye-updates main contrib non-free
deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free

and all seems to be fine and dandy.

lbrtchx

Charles Curley

unread,
Apr 30, 2022, 8:30:05 PM4/30/22
to
On Sat, 30 Apr 2022 16:45:01 -0500
Albretch Mueller <lbr...@gmail.com> wrote:

> and all seems to be fine and dandy.

Good to hear. A bit of fine tuning:

Unless you want the source for any package(s), comment out the deb-src
lines. Comment in the deb-src lines only for packages that interest you.

You have two security and two updates. One of each has contrib and
non-free as well as main, the other main only. The main only ones are
redundant.

Charlie

unread,
May 1, 2022, 1:20:05 AM5/1/22
to
On Sat, 30 Apr 2022 16:45:01 -0500
Albretch Mueller <lbr...@gmail.com> wrote:

Thank you for that update. I will give your sources list a try because
my new Asus desktop install won't accept the sources list from my
working laptop:

deb http://deb.debian.org/debian/ bullseye main non-free contrib

with this message:

Release file for http://deb.debian/dists/bullseye/InRelease is not
valid yet (invalid for another 5d 13h 52m 3s) Updates for this
repository will not be applied.

Because the installer configured the Ethernet connection but could not
access the mirror, I put in the above from my home lappy, but still no
joy. So will try your sources list, thank you.

Charlie
--
Registered Linux User:- 329524
***********************************************

It is well to remember that the entire population of the
universe, with one trifling exception, is composed of others.
-- John Andrew Holmes, Jr.

***********************************************

Debian GNU/Linux - Magic indeed.

-----------------------------------------------------

Andrew M.A. Cater

unread,
May 1, 2022, 7:20:05 AM5/1/22
to
On Sun, May 01, 2022 at 03:13:06PM +1000, Charlie wrote:
> >
>
> Thank you for that update. I will give your sources list a try because
> my new Asus desktop install won't accept the sources list from my
> working laptop:
>
> deb http://deb.debian.org/debian/ bullseye main non-free contrib
>
> with this message:
>
> Release file for http://deb.debian/dists/bullseye/InRelease is not
> valid yet (invalid for another 5d 13h 52m 3s) Updates for this
> repository will not be applied.
>
> Because the installer configured the Ethernet connection but could not
> access the mirror, I put in the above from my home lappy, but still no
> joy. So will try your sources list, thank you.
>
> Charlie
> --

Hi Charlie,

That error is symptomatic of another problem: what time/date does the
machine think it has.

If files come from the future, it could be that the time or date is
incorrectly set in firmware - or that something doesn't have a real
time clock.

That's fairly easily reset by using the date command and hwclock commands.

I always have to check the syntax of the date command:

date -u MMDDHHmmCCYY where u is for UTC

date -u 050111132022

would be round about now and would set the system time accordingly.

hwclock --systohc

would apply system time to the hardware clock (or --hctosys would go the other
way].

Hope this helps - with every good wish, as ever,

Andy Cater

Charlie

unread,
May 1, 2022, 8:30:05 AM5/1/22
to
Thank you Andy, you are the man. Hit the nail squarely on the head.

The hardware clock thought it was in 2005-01-01

Using the guidance you posted. It worked a treat and could update and
would install packages.

Thank you for your help, it is extremely much appreciated.

Charlie
--
Registered Linux User:- 329524
***********************************************

Whatever you can do or dream you can, begin it. Boldness has
genius, magic and power in it. Begin it now. ------Goethe

to...@tuxteam.de

unread,
May 1, 2022, 9:40:05 AM5/1/22
to
On Sun, May 01, 2022 at 10:19:25PM +1000, Charlie wrote:

[...]

> The hardware clock thought it was in 2005-01-01

Uh, oh. This looks as if your clock's battery is dying.

Cheers
--
t
signature.asc

Charlie

unread,
May 1, 2022, 6:10:04 PM5/1/22
to
Thank you Tomas, I thought that; will replace it.

Thanks
--
Registered Linux User:- 329524
***********************************************

The law will never make men free, it is men that have to make
the law free...Henry David Thoreau
0 new messages