Zero6992 / chatGPT-discord-bot

Integrate ChatGPT into your own discord bot
GNU General Public License v2.0
2.63k stars 701 forks source link

Error getting debian source #304

Closed TaijiMonster closed 1 year ago

TaijiMonster commented 1 year ago

0 1.773 Err:1 http://deb.debian.org/debian bullseye InRelease

0 1.773 Could not connect to debian.map.fastlydns.net:80 (199.232.46.132). - connect (113: No route to host) Unable to connect to deb.debian.org:http:

0 1.773 Err:2 http://deb.debian.org/debian-security bullseye-security InRelease

0 1.773 Unable to connect to deb.debian.org:http:

0 1.773 Err:3 http://deb.debian.org/debian bullseye-updates InRelease

0 1.773 Unable to connect to deb.debian.org:http:

0 1.777 Reading package lists...

0 1.783 W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease Could not connect to debian.map.fastlydns.net:80 (199.232.46.132). - connect (113: No route to host) Unable to connect to deb.debian.org:http:

0 1.783 W: Failed to fetch http://deb.debian.org/debian-security/dists/bullseye-security/InRelease Unable to connect to deb.debian.org:http:

0 1.783 W: Failed to fetch http://deb.debian.org/debian/dists/bullseye-updates/InRelease Unable to connect to deb.debian.org:http:

0 1.783 W: Some index files failed to download. They have been ignored, or old ones used instead.

0 1.787 Reading package lists...

0 1.794 Building dependency tree...

0 1.795 Reading state information...

0 1.798 Package gettext is not available, but is referred to by another package.

0 1.798 This may mean that the package is missing, has been obsoleted, or

0 1.798 is only available from another source

0 1.798

0 1.798 Package build-essential is not available, but is referred to by another package.

0 1.798 This may mean that the package is missing, has been obsoleted, or

0 1.798 is only available from another source

0 1.798

0 1.798 Package libgdk-pixbuf2.0-dev is not available, but is referred to by another package.

0 1.798 This may mean that the package is missing, has been obsoleted, or

0 1.798 is only available from another source

0 1.798 However the following packages replace it:

0 1.798 libgdk-pixbuf2.0-bin libgdk-pixbuf-2.0-dev

0 1.798

0 1.798 Package libtiff5-dev is not available, but is referred to by another package.

0 1.798 This may mean that the package is missing, has been obsoleted, or

0 1.798 is only available from another source

0 1.798 However the following packages replace it:

0 1.798 libtiff-dev

0 1.798

0 1.798 Package python3-dev is not available, but is referred to by another package.

0 1.798 This may mean that the package is missing, has been obsoleted, or

0 1.798 is only available from another source

0 1.798

0 1.799 E: Package 'build-essential' has no installation candidate

0 1.799 E: Unable to locate package cargo

0 1.799 E: Package 'libgdk-pixbuf2.0-dev' has no installation candidate

0 1.799 E: Package 'gettext' has no installation candidate

0 1.799 E: Unable to locate package musl-dev

0 1.799 E: Unable to locate package libpango1.0-dev

0 1.799 E: Couldn't find any package by glob 'libpango1.0-dev'

0 1.799 E: Couldn't find any package by regex 'libpango1.0-dev'

0 1.799 E: Unable to locate package poppler-utils

0 1.799 E: Unable to locate package postgresql-client

0 1.799 E: Package 'python3-dev' has no installation candidate

0 1.799 E: Unable to locate package rustc

0 1.799 E: Package 'libtiff5-dev' has no installation candidate


failed to solve: executor failed running [/bin/sh -c apt-get update && apt-get install -y build-essential libcairo2-dev cargo libfreetype6-dev gcc libgdk-pixbuf2.0-dev gettext libjpeg-dev liblcms2-dev libffi-dev musl-dev libopenjp2-7-dev libssl-dev libpango1.0-dev poppler-utils postgresql-client libpq-dev python3-dev rustc tcl-dev libtiff5-dev tk-dev zlib1g-dev]: exit code: 100

Zero6992 commented 1 year ago

This is a network issue

some solutions: https://unix.stackexchange.com/questions/710615/apt-update-unable-to-connect-to-deb-debian-org https://github.com/docker/for-mac/issues/6030

TaijiMonster commented 1 year ago

A docker restart solved the issue.