RE: Need working repo for Deb7 - wheezy
Hi @Michael Stone Thanks for your continuous support! I have installed the package now. We will let you know if any further assistance required. root@policijas-db:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 7 (wheezy)" NAME="Debian GNU/Linux" VERSION_ID="7" VERSION="7 (wheezy)" ID=debian ANSI_COLOR="1;31" HOME_URL="http://www.debian.org/"; SUPPORT_URL="http://www.debian.org/support/"; BUG_REPORT_URL="http://bugs.debian.org/"; root@policijas-db:~# cat /etc/apt/sources.list deb http://archive.debian.org/debian/ wheezy main contrib non-free deb http://archive.debian.org/debian-security wheezy/updates main contrib non-free root@policijas-db:~# root@policijas-db:~# cat /etc/apt/apt.conf APT::Get::AllowUnauthenticated "true"; root@policijas-db:~# dpkg-query -l sssd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--===-===-= ii sssd 1.8.4-2 amd64 System Security Services Daemon root@policijas-db:~# Regards, Aravinth kumar Linux Admin - Infrastructure operations -Original Message- From: Michael Stone Sent: Wednesday, August 10, 2022 11:36 PM To: Aravinth kumar Anbalagan Cc: Karthik Jeyabalan ; debian-user@lists.debian.org Subject: Re: Need working repo for Deb7 - wheezy On Tue, Aug 09, 2022 at 01:31:20PM +, Aravinth kumar Anbalagan wrote: >Hi @Michael Stone > >There are no proxy configured on the server. Please check the below error and >let us know how can we proceed further? > >root@policijas-db:~# cd /etc/apt/ >apt.conf.d/ preferences.d/ sources.list.d/ trusted.gpg.d/ >root@policijas-db:~# cd /etc/apt/apt.conf.d/ >root@policijas-db:/etc/apt/apt.conf.d# ls 00CDMountPoint 00trustcdrom >01autoremove 20apt-show-versions 20listchanges 70debconf >root@policijas-db:/etc/apt/apt.conf.d# cat * |grep -i prox >root@policijas-db:/etc/apt/apt.conf.d# > >Error: > >W: GPG error: >https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiv >e.debian.org%2F&data=05%7C01%7Caravinth.anbalagan%40tele2.com%7C474 >f1c7282394a3e89dc08da7afafe79%7C76431109ff8942c28781a07ca07a2d57%7C0%7C >0%7C637957515683777997%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ >IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tv >0EGY8sHCrL4kn4ecv6%2FFgtwyNyR7k9tDSWDcQuvBo%3D&reserved=0 squeeze >Release: The following signatures were invalid: KEYEXPIRED 1520281423 >KEYEXPIRED 1501892461 >W: GPG error: >https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiv >e.debian.org%2F&data=05%7C01%7Caravinth.anbalagan%40tele2.com%7C474 >f1c7282394a3e89dc08da7afafe79%7C76431109ff8942c28781a07ca07a2d57%7C0%7C >0%7C637957515683777997%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ >IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tv >0EGY8sHCrL4kn4ecv6%2FFgtwyNyR7k9tDSWDcQuvBo%3D&reserved=0 >squeeze-lts Release: The following signatures were invalid: KEYEXPIRED >1587841717 >W: Failed to fetch >https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsecuri >ty.debian.org%2Fdists%2Fsqueeze%2Fupdates%2Fmain%2Fsource%2FSources& >;data=05%7C01%7Caravinth.anbalagan%40tele2.com%7C474f1c7282394a3e89dc08 >da7afafe79%7C76431109ff8942c28781a07ca07a2d57%7C0%7C0%7C637957515683777 >997%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI >6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pggvWYuFhNP%2BBDp%2FL >xO36I07UfVgaThUVzpJFnSulNA%3D&reserved=0 404 Not Found [IP: >151.101.194.132 80] > >W: Failed to fetch >https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsecuri >ty.debian.org%2Fdists%2Fsqueeze%2Fupdates%2Fcontrib%2Fsource%2FSources& >amp;data=05%7C01%7Caravinth.anbalagan%40tele2.com%7C474f1c7282394a3e89d >c08da7afafe79%7C76431109ff8942c28781a07ca07a2d57%7C0%7C0%7C637957515683 >777997%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB >TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=kyVM1RGf5QlrFf9%2B >SYzy70bO5zJpR9IduKvuH3XD%2FUA%3D&reserved=0 404 Not Found [IP: >151.101.194.132 80] > >W: Failed to fetch >https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsecuri >ty.debian.org%2Fdists%2Fsqueeze%2Fupdates%2Fnon-free%2Fsource%2FSources >&data=05%7C01%7Caravinth.anbalagan%40tele2.com%7C474f1c7282394a3e89 >dc08da7afafe79%7C76431109ff8942c28781a07ca07a2d57%7C0%7C0%7C63795751568 >3777997%7CUnknown%7CTWF
Re: Need working repo for Deb7 - wheezy
On Tue, Aug 09, 2022 at 01:31:20PM +, Aravinth kumar Anbalagan wrote: Hi @Michael Stone There are no proxy configured on the server. Please check the below error and let us know how can we proceed further? root@policijas-db:~# cd /etc/apt/ apt.conf.d/ preferences.d/ sources.list.d/ trusted.gpg.d/ root@policijas-db:~# cd /etc/apt/apt.conf.d/ root@policijas-db:/etc/apt/apt.conf.d# ls 00CDMountPoint 00trustcdrom 01autoremove 20apt-show-versions 20listchanges 70debconf root@policijas-db:/etc/apt/apt.conf.d# cat * |grep -i prox root@policijas-db:/etc/apt/apt.conf.d# Error: W: GPG error: http://archive.debian.org squeeze Release: The following signatures were invalid: KEYEXPIRED 1520281423 KEYEXPIRED 1501892461 W: GPG error: http://archive.debian.org squeeze-lts Release: The following signatures were invalid: KEYEXPIRED 1587841717 W: Failed to fetch http://security.debian.org/dists/squeeze/updates/main/source/Sources 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/contrib/source/Sources 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/non-free/source/Sources 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/main/binary-amd64/Packages 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/contrib/binary-amd64/Packages 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/non-free/binary-amd64/Packages 404 Not Found [IP: 151.101.194.132 80] E: Some index files failed to download. They have been ignored, or old ones used instead. root@policijas-db:~# The original question was about wheezy, this is squeeze so the answers are a little different. You can use something like this as your sources.list: deb http://archive.debian.org/debian/ squeeze main contrib non-free deb http://archive.debian.org/debian-security squeeze/updates main contrib non-free deb http://archive.debian.org/debian squeeze-lts main contrib non-free (Note that everything is coming from archive.debian.org, not security.debian.org.) In /etc/apt/apt.conf you'll need: APT::Get::AllowUnauthenticated "true"; Because you *will get* warnings like the following: W: GPG error: http://archive.debian.org squeeze Release: The following signatures were invalid: KEYEXPIRED 1520281423 KEYEXPIRED 1501892461 W: GPG error: http://archive.debian.org squeeze/updates Release: The following signatures were invalid: KEYEXPIRED 1520281423 W: GPG error: http://archive.debian.org squeeze-lts Release: The following signatures were invalid: KEYEXPIRED 1587841717 Ignore anyone who talks about updating keys, *there are no current keys for squeeze because it's an unsupported release*. The change in apt.conf allows you to install packages regardless of the warnings. This is something you would not normally do, but if you're running an obsolete unsupported release (hopefully internally and without network-facing services) ignoring GPG warnings on the archive is the least of your problems.
Re: Need working repo for Deb7 - wheezy
On Wed, Aug 10 2022 at 01:41:46 PM, Aravinth kumar Anbalagan wrote: > Hi Thomas, > > Below is the output. > > root@policijas-db:~# gpg --keyserver keyserver.ubuntu.com --recv-keys 473041FA > gpg: requesting key 473041FA from hkp server keyserver.ubuntu.com > gpg: keyserver timed out > gpg: keyserver receive failed: keyserver error > root@policijas-db:~# > The HKP protocol uses port 11371 by default. You need to make sure connection requests to that port are allowed through your network. Alternatively, you need to instruct gpg to use port 80 explicitly, using hkp://keyserver.ubuntu.com:80 as the keyserver argument. > -- regards, kushal
RE: Need working repo for Deb7 - wheezy
Hi, Aravinth kumar Anbalagan wrote: > root@policijas-db:~# gpg --keyserver keyserver.ubuntu.com --recv-keys 473041FA > gpg: requesting key 473041FA from hkp server keyserver.ubuntu.com > gpg: keyserver timed out Looks like a problem between your network and keyserver.ubuntu.com. I get no reply from ping keyserver.ubuntu.com But gpg --keyserver keyserver.ubuntu.com --recv-keys 473041FA obviously can contact the server and learn that there is nothing to do after my previous download experiment: gpg: requesting key 473041FA from hkp server keyserver.ubuntu.com gpg: key 473041FA: "Debian Archive Automatic Signing Key (6.0/squeeze) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 This lasts less than a second. --- Maybe you can do something with https://ftp-master.debian.org/keys/release-7.asc But i lack experience with gpg and apt-key. So i cannot propose anything. Have a nice day :) Thomas
RE: Need working repo for Deb7 - wheezy
Hi Thomas, Below is the output. root@policijas-db:~# gpg --keyserver keyserver.ubuntu.com --recv-keys 473041FA gpg: requesting key 473041FA from hkp server keyserver.ubuntu.com gpg: keyserver timed out gpg: keyserver receive failed: keyserver error root@policijas-db:~# Regards, Aravinth kumar Linux Admin - Infrastructure operations -Original Message- From: Thomas Schmitt Sent: Wednesday, August 10, 2022 3:56 PM To: debian-user@lists.debian.org Cc: Aravinth kumar Anbalagan Subject: RE: Need working repo for Deb7 - wheezy Hi, Aravinth kumar Anbalagan wrote: > Received below error. Any other way to download the keys? > [...] > sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com $K [...] > Executing: gpg --ignore-time-conflict --no-options > --no-default-keyring --secret-keyring /tmp/tmp.3r9by2p9YX > --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg > --primary-keyring /etc/apt/trusted.gpg --keyring > /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg > --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg > --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg > --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg > --recv-keys --keyserver keyserver.ubuntu.com 473041FA > gpg: requesting key 473041FA from hkp server keyserver.ubuntu.com > gpg: keyserver timed out > gpg: keyserver receive failed: keyserver error (I don't want to mess with apt-key as long as apt-get is working fine here. Call me supersticious, especially in respect to system administration.) Not regarding for now the many gpg options used by apt-key, i'd say that "keyserver timed out" is an indication for network problems. Before studying man gpg i try a vanilla key download: $ gpg --keyserver keyserver.ubuntu.com --recv-keys 473041FA gpg: requesting key 473041FA from hkp server keyserver.ubuntu.com gpg: key 473041FA: public key "Debian Archive Automatic Signing Key (6.0/squeeze) " imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) So the server looks reachable from here and delivers some Debian related key. What do you get from this simple gpg run ? -- I guess there are other ways to download the keys from Debian directly, and to let apt-key take them. In https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmanpages.debian.org%2Fwheezy%2Fapt%2Fapt-key.8.en.html&data=05%7C01%7Caravinth.anbalagan%40tele2.com%7C6d2486c9cc264d4784ea08da7aba7aa6%7C76431109ff8942c28781a07ca07a2d57%7C0%7C0%7C637957238716527666%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=poCBI4IRt3eE7OiSxkTNPF%2BzNDFBDwQXHNsCzXz%2FvRM%3D&reserved=0 i see: add filename Add a new key to the list of trusted keys. The key is read from the filename given with the parameter filename or if the filename is - from standard input. update Update the local keyring with the archive keyring and remove from the local keyring the archive keys which are no longer valid. The archive keyring is shipped in the archive-keyring package of your distribution, e.g. the debian-archive-keyring package in Debian. (I get to the impression that those here who better understand apt-* don't want to be accessory to the crime of running Debian 7. So only ruthless amateurs like me consider to look for solutions. But let me add for consideration that qualified help could shorten the public pain caused by watching this endeavor.) Have a nice day :) Thomas IMPORTANT NOTICE The content of this e-mail is intended for the addressee(s) only and may contain information that is confidential and/or otherwise protected from disclosure. If you are not the intended recipient, please note that any copying, distribution or any other use or dissemination of the information contained in this e-mail (and its attachments) is strictly prohibited. If you have received this e-mail in error, kindly notify the sender immediately by replying to this e-mail and delete the e-mail and any copies thereof. Tele2 AB (publ) and its subsidiaries (“Tele2 Group”) accepts no responsibility for the consequences of any viruses, corruption or other interference transmitted by e-mail.
RE: Need working repo for Deb7 - wheezy
Hi, Aravinth kumar Anbalagan wrote: > Received below error. Any other way to download the keys? > [...] > sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com $K > [...] > Executing: gpg --ignore-time-conflict --no-options --no-default-keyring > --secret-keyring /tmp/tmp.3r9by2p9YX --trustdb-name /etc/apt//trustdb.gpg > --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg > --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg > --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg > --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg > --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg > --recv-keys --keyserver keyserver.ubuntu.com 473041FA > gpg: requesting key 473041FA from hkp server keyserver.ubuntu.com > gpg: keyserver timed out > gpg: keyserver receive failed: keyserver error (I don't want to mess with apt-key as long as apt-get is working fine here. Call me supersticious, especially in respect to system administration.) Not regarding for now the many gpg options used by apt-key, i'd say that "keyserver timed out" is an indication for network problems. Before studying man gpg i try a vanilla key download: $ gpg --keyserver keyserver.ubuntu.com --recv-keys 473041FA gpg: requesting key 473041FA from hkp server keyserver.ubuntu.com gpg: key 473041FA: public key "Debian Archive Automatic Signing Key (6.0/squeeze) " imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) So the server looks reachable from here and delivers some Debian related key. What do you get from this simple gpg run ? -- I guess there are other ways to download the keys from Debian directly, and to let apt-key take them. In https://manpages.debian.org/wheezy/apt/apt-key.8.en.html i see: add filename Add a new key to the list of trusted keys. The key is read from the filename given with the parameter filename or if the filename is - from standard input. update Update the local keyring with the archive keyring and remove from the local keyring the archive keys which are no longer valid. The archive keyring is shipped in the archive-keyring package of your distribution, e.g. the debian-archive-keyring package in Debian. (I get to the impression that those here who better understand apt-* don't want to be accessory to the crime of running Debian 7. So only ruthless amateurs like me consider to look for solutions. But let me add for consideration that qualified help could shorten the public pain caused by watching this endeavor.) Have a nice day :) Thomas
RE: Need working repo for Deb7 - wheezy
Hi @Thomas Schmitt Received below error. Any other way to download the keys? root@policijas-db:~# for K in $(apt-key list | grep expired | cut -d'/' -f2 | cut -d' ' -f1); do sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com $K; done Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.3r9by2p9YX --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg --recv-keys --keyserver keyserver.ubuntu.com 473041FA gpg: requesting key 473041FA from hkp server keyserver.ubuntu.com gpg: keyserver timed out gpg: keyserver receive failed: keyserver error Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.0KzcVB1oX0 --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg --recv-keys --keyserver keyserver.ubuntu.com B98321F9 gpg: requesting key B98321F9 from hkp server keyserver.ubuntu.com gpg: keyserver timed out gpg: keyserver receive failed: keyserver error Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.Ru0lGoWogc --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg --recv-keys --keyserver keyserver.ubuntu.com 46925553 gpg: requesting key 46925553 from hkp server keyserver.ubuntu.com gpg: keyserver timed out gpg: keyserver receive failed: keyserver error Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.EsJLGTUW7L --trustdb-name /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg --recv-keys --keyserver keyserver.ubuntu.com 65FFB764 gpg: requesting key 65FFB764 from hkp server keyserver.ubuntu.com gpg: keyserver timed out gpg: keyserver receive failed: keyserver error Regards, Aravinth kumar Linux Admin - Infrastructure operations -Original Message- From: Thomas Schmitt Sent: Tuesday, August 9, 2022 10:56 PM To: debian-user@lists.debian.org Cc: Aravinth kumar Anbalagan Subject: RE: Need working repo for Deb7 - wheezy Hi, Aravinth kumar Anbalagan wrote: > W: GPG error: > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchi > ve.debian.org%2F&data=05%7C01%7Caravinth.anbalagan%40tele2.com%7Cc > 62585afa67040bc7c7408da7a2c0d61%7C76431109ff8942c28781a07ca07a2d57%7C0 > %7C0%7C637956627431950382%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi > LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sda > ta=U7DXU4mhsCBHe5AKZQwX6tUSwN2EsIxWxvx9xvBjGu4%3D&reserved=0 > squeeze Release: The following signatures were invalid: KEYEXPIRED > 1520281423 KEYEXPIRED 1501892461 > W: GPG error: > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchi > ve.debian.org%2F&data=05%7C01%7Caravinth.anbalagan%40tele2.com%7Cc > 62585afa67040bc7c7408da7a2c0d61%7C76431109ff8942c28781a07ca07a2d57%7C0 > %7C0%7C637956627431950382%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi > LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sda > ta=U7DXU4mhsCBHe5AKZQwX6tUSwN2EsIxWxvx9xvBjGu4%3D&reserved=0 > squeeze-lts Release: The following signatures were invalid: KEYEXPIRED > 1587841717 $ date -u -d @1520281423 ; date -u -d @1501892461 ; date -u -d @1587841717 Mon Mar 5 20:23:43 UTC 2018 Sat Aug 5 00:21:01 UTC 2017 Sat Apr 25 19:08:37 UTC 2020 Maybe this 13 year old trick still works: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fserverfault.com%2Fquestions%2F7145%2Fwhat-should-i-do-when-i-got-the-keyexpired-error-message-after-an-apt-get-update&data=05%7C01%7Caravinth.anbalagan%40tele2.com%7Cc625
Re: Need working repo for Deb7 - wheezy
On Tue, Aug 09, 2022 at 07:26:19PM +0200, Thomas Schmitt wrote: > Greg Wooledge wrote: > > You are inside a corporate setting. Very, very corporate. > > This is probably on the level of the mail client, not of the network. > Microsoft Corp. installs itself between its Outlook users and the world. > Whenever the cloud thinks that the world is bad, the user gets warned. > See > > https://support.microsoft.com/en-us/office/advanced-outlook-com-security-for-microsoft-365-subscribers-882d2243-eab9-4545-a58a-b36fee4a46e2?ui=en-us&rs=en-us&ad=us > > https://security.stackexchange.com/questions/230309/is-a-safelinks-protection-outlook-com-link-phishing Oh, believe me, I'm aware. This is why I'm subscribed from my personal email address now, instead of my work address. My work address no longer goes directly to a Unix inbox. It goes to a Microsoft one now. And technical mailing lists are just not acceptable in that environment. I'm still betting on "workplace transparent [as mud] HTTP proxy is causing unencrypted HTTP to fail" as the primary problem. Seeing the Outlook mangling just reinforces my diagnosis.
RE: Need working repo for Deb7 - wheezy
Hi, Aravinth kumar Anbalagan wrote: > W: GPG error: http://archive.debian.org squeeze Release: The following > signatures were invalid: KEYEXPIRED 1520281423 KEYEXPIRED 1501892461 > W: GPG error: http://archive.debian.org squeeze-lts Release: The following > signatures were invalid: KEYEXPIRED 1587841717 $ date -u -d @1520281423 ; date -u -d @1501892461 ; date -u -d @1587841717 Mon Mar 5 20:23:43 UTC 2018 Sat Aug 5 00:21:01 UTC 2017 Sat Apr 25 19:08:37 UTC 2020 Maybe this 13 year old trick still works: https://serverfault.com/questions/7145/what-should-i-do-when-i-got-the-keyexpired-error-message-after-an-apt-get-update The --keyserver keys.gnupg.net is dead meanwhile. Try keyserver.ubuntu.com instead. Maybe somebody else with more GPG and/or Debian knowledge can deciper https://wiki.debian.org/SecureApt https://ftp-master.debian.org/keys.html Aravinth kumar Anbalagan's mail client wrote in a quote: > > > deb https://eur01.safelinks.protection.outlook.com/?url=... Greg Wooledge wrote: > You are inside a corporate setting. Very, very corporate. This is probably on the level of the mail client, not of the network. Microsoft Corp. installs itself between its Outlook users and the world. Whenever the cloud thinks that the world is bad, the user gets warned. See https://support.microsoft.com/en-us/office/advanced-outlook-com-security-for-microsoft-365-subscribers-882d2243-eab9-4545-a58a-b36fee4a46e2?ui=en-us&rs=en-us&ad=us https://security.stackexchange.com/questions/230309/is-a-safelinks-protection-outlook-com-link-phishing Have a nice day :) Thomas
RE: Need working repo for Deb7 - wheezy
On Tue, 9 Aug 2022, Aravinth kumar Anbalagan wrote: Hi @Michael Stone There are no proxy configured on the server. Please check the below error and let us know how can we proceed further? root@policijas-db:~# cd /etc/apt/ apt.conf.d/ preferences.d/ sources.list.d/ trusted.gpg.d/ root@policijas-db:~# cd /etc/apt/apt.conf.d/ root@policijas-db:/etc/apt/apt.conf.d# ls 00CDMountPoint 00trustcdrom 01autoremove 20apt-show-versions 20listchanges 70debconf root@policijas-db:/etc/apt/apt.conf.d# cat * |grep -i prox root@policijas-db:/etc/apt/apt.conf.d# Error: W: GPG error: http://archive.debian.org squeeze Release: The following signatures were invalid: KEYEXPIRED 1520281423 KEYEXPIRED 1501892461 W: GPG error: http://archive.debian.org squeeze-lts Release: The following signatures were invalid: KEYEXPIRED 1587841717 W: Failed to fetch http://security.debian.org/dists/squeeze/updates/main/source/Sources 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/contrib/source/Sources 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/non-free/source/Sources 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/main/binary-amd64/Packages 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/contrib/binary-amd64/Packages 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/non-free/binary-amd64/Packages 404 Not Found [IP: 151.101.194.132 80] E: Some index files failed to download. They have been ignored, or old ones used instead. root@policijas-db:~# You cannot use security.debian.org for this. This is what I have for wheezy: deb http://archive.debian.org/debian wheezy main deb http://archive.debian.org/debian-security wheezy/updates main deb-src http://archive.debian.org/debian wheezy main deb-src http://archive.debian.org/debian-security wheezy/updates main I assume stretch is similar. You also need Acquire::Check-Valid-Until "false"; in apt.conf. N.B. I assume you're fetching using squeeze - so perhaps you will need to download using a newer distro then re-sign the release file. I don't have such an old release even for experiments!
Re: Need working repo for Deb7 - wheezy
On Tue, Aug 09, 2022 at 01:31:20PM +, Aravinth kumar Anbalagan wrote: > > > -Original Message- > From: Michael Stone > Sent: Friday, August 5, 2022 9:53 PM > To: Karthik Jeyabalan > Cc: debian-user@lists.debian.org; Aravinth kumar Anbalagan > > Subject: Re: Need working repo for Deb7 - wheezy > > On Fri, Aug 05, 2022 at 07:42:20AM +, Karthik Jeyabalan wrote: > >deb > >https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiv > >e.debian.org%2Fdebian%2F&data=05%7C01%7Caravinth.anbalagan%40tele2. > >com%7C9d3f6b3fe3514b217a6e08da76fed4f5%7C76431109ff8942c28781a07ca07a2d > >57%7C0%7C0%7C637953134110939276%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA > >wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C& > >;sdata=yh13FhvbUKeLL%2Bo%2F87nweXTEdn3fYKeQjuUCWejSdPU%3D&reserved= > >0 wheezy main OK, you see this crap here? You are inside a corporate setting. Very, very corporate. I can only imagine that your corporate network infrastructure that mangles email in this way is also mangling HTTP. I wish you the best of luck, but I fear your road forward is going to be painful beyond imagining.
RE: Need working repo for Deb7 - wheezy
Hi @Michael Stone There are no proxy configured on the server. Please check the below error and let us know how can we proceed further? root@policijas-db:~# cd /etc/apt/ apt.conf.d/ preferences.d/ sources.list.d/ trusted.gpg.d/ root@policijas-db:~# cd /etc/apt/apt.conf.d/ root@policijas-db:/etc/apt/apt.conf.d# ls 00CDMountPoint 00trustcdrom 01autoremove 20apt-show-versions 20listchanges 70debconf root@policijas-db:/etc/apt/apt.conf.d# cat * |grep -i prox root@policijas-db:/etc/apt/apt.conf.d# Error: W: GPG error: http://archive.debian.org squeeze Release: The following signatures were invalid: KEYEXPIRED 1520281423 KEYEXPIRED 1501892461 W: GPG error: http://archive.debian.org squeeze-lts Release: The following signatures were invalid: KEYEXPIRED 1587841717 W: Failed to fetch http://security.debian.org/dists/squeeze/updates/main/source/Sources 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/contrib/source/Sources 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/non-free/source/Sources 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/main/binary-amd64/Packages 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/contrib/binary-amd64/Packages 404 Not Found [IP: 151.101.194.132 80] W: Failed to fetch http://security.debian.org/dists/squeeze/updates/non-free/binary-amd64/Packages 404 Not Found [IP: 151.101.194.132 80] E: Some index files failed to download. They have been ignored, or old ones used instead. root@policijas-db:~# Regards, Aravinth kumar Linux Admin - Infrastructure operations -Original Message- From: Michael Stone Sent: Friday, August 5, 2022 9:53 PM To: Karthik Jeyabalan Cc: debian-user@lists.debian.org; Aravinth kumar Anbalagan Subject: Re: Need working repo for Deb7 - wheezy On Fri, Aug 05, 2022 at 07:42:20AM +, Karthik Jeyabalan wrote: >deb >https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiv >e.debian.org%2Fdebian%2F&data=05%7C01%7Caravinth.anbalagan%40tele2. >com%7C9d3f6b3fe3514b217a6e08da76fed4f5%7C76431109ff8942c28781a07ca07a2d >57%7C0%7C0%7C637953134110939276%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA >wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C& >;sdata=yh13FhvbUKeLL%2Bo%2F87nweXTEdn3fYKeQjuUCWejSdPU%3D&reserved= >0 wheezy main > >deb >https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiv >e.debian.org%2Fdebian-security&data=05%7C01%7Caravinth.anbalagan%40 >tele2.com%7C9d3f6b3fe3514b217a6e08da76fed4f5%7C76431109ff8942c28781a07c >a07a2d57%7C0%7C0%7C637953134110939276%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM >C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C% >7C&sdata=%2FGRM08ZMxdfpHegm9SQhzIgwCgSQUTCDl%2BtZBVH%2Fnmo%3D&r >eserved=0 wheezy/updates main contrib non-free > >deb >https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiv >e.debian.org%2Fdebian%2F&data=05%7C01%7Caravinth.anbalagan%40tele2. >com%7C9d3f6b3fe3514b217a6e08da76fed4f5%7C76431109ff8942c28781a07ca07a2d >57%7C0%7C0%7C637953134110939276%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA >wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C& >;sdata=yh13FhvbUKeLL%2Bo%2F87nweXTEdn3fYKeQjuUCWejSdPU%3D&reserved= >0 wheezy main non-free contrib > >deb-src >https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiv >e.debian.org%2Fdebian%2F&data=05%7C01%7Caravinth.anbalagan%40tele2. >com%7C9d3f6b3fe3514b217a6e08da76fed4f5%7C76431109ff8942c28781a07ca07a2d >57%7C0%7C0%7C637953134110939276%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA >wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C& >;sdata=yh13FhvbUKeLL%2Bo%2F87nweXTEdn3fYKeQjuUCWejSdPU%3D&reserved= >0 wheezy main non-free contrib The first line is a partial duplicate of the third line. Other than that if I copy and paste this into sources.list on a wheezy machine it works fine for me, no 403 codes. You can look in /etc/apt/apt.conf and files in /etc/apt/apt.conf.d to see if you perhaps have a misconfigured proxy. You will also need to add Acquire::Check-Valid-Until "false"; to /etc/apt/apt.conf as the Release file has expired (as expected for an archived release). IMPORTANT NOTICE The content of this e-mail is intended for the addressee(s) only and may contain information that is confidential and/or otherwise protected from disclosure. If you are not the intended recipient, please note that any copying, distribution or any other use or dissemination of the information contained in this e-mail (and its attachments) is strictly prohibited. If you have received this e-mail in
Re: Need working repo for Deb7 - wheezy
Hello, On Sat, Aug 06, 2022 at 01:28:16PM -, Curt wrote: > On 2022-08-06, Andy Smith wrote: > > Anything between (and including) the OP's computer and > > archive.debian.org can [intercept and] deny the HTTP request. > > Is there no way of making this determination? Sure, there are lots of things the OP can do to work out what is going on, or at least get more of an idea. For example they could: - Check if they can browse the archive URL in a regular browser or from another machine, to try to localise the issue to their apt or computer, or not - Do a TCP traceroute or mtr in TCP mode or similar, using port 80, to see the path by which HTTP requests go. If it ends locally then they might have discovered a local intercepting proxy that doesn't like HTTP requests to archive.debian.org for some reason but all these things require participation by the OP, and we don't seem to have any. Someone said they're not subscribed to this list - I forgot to check with my previous reply. If not then they probably got very few of the replies. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Need working repo for Deb7 - wheezy
On Sat, Aug 06, 2022 at 01:28:16PM -, Curt wrote: > On 2022-08-06, Andy Smith wrote: > > Hello, > > > > On Sat, Aug 06, 2022 at 06:52:29AM -0400, Amn wrote: > >> Black listed?!! > >> How does that work? > > > > Anything between (and including) the OP's computer and > > archive.debian.org can [intercept and] deny the HTTP request. > > Is there no way of making this determination? The fact that nobody else is reporting any problems with archive.d.o strongly points toward either a client-side issue, or a transient issue that has already been fixed.
Re: Need working repo for Deb7 - wheezy
On 2022-08-06, Andy Smith wrote: > Hello, > > On Sat, Aug 06, 2022 at 06:52:29AM -0400, Amn wrote: >> Black listed?!! >> How does that work? > > Anything between (and including) the OP's computer and > archive.debian.org can [intercept and] deny the HTTP request. Is there no way of making this determination? > Cheers, > Andy > --
Re: Need working repo for Deb7 - wheezy
Hello, On Sat, Aug 06, 2022 at 06:52:29AM -0400, Amn wrote: > Black listed?!! > How does that work? Anything between (and including) the OP's computer and archive.debian.org can [intercept and] deny the HTTP request. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Need working repo for Deb7 - wheezy
Black listed?!! How does that work? Is Debian like Smack Over-daaw? On 2022-08-05 11:01 a.m., Tixy wrote: On Fri, 2022-08-05 at 11:10 +0100, Brian wrote: On Fri 05 Aug 2022 at 19:54:38 +1000, David wrote: [...] However archived repo snapshots are available via here: https://snapshot.debian.org/ which looks like it has sssd packages for wheezy. There is also http://archive.debian.org/debian/. Which is what the OP is using and getting a 403 Forbidden error. The URL they are using works for me in a web browser so it's either a transient issue or an issue with the OP's network being blacklisted or something.
Re: Need working repo for Deb7 - wheezy
On Fri 05 Aug 2022 at 18:30:16 +, Andy Smith wrote: > Hello, > > On Fri, Aug 05, 2022 at 12:27:19PM -0400, Timothy M Butterworth wrote: > > On Fri, Aug 5, 2022 at 8:20 AM Brian wrote: > > > W: GPG error: http://archive.debian.org/debian wheezy Release: The > > > following signatures couldn't be verified because the public key is not > > > available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY > > > 6FB2A1C265FFB764 > > > E: The repository 'http://archive.debian.org/debian wheezy Release' is > > > not signed. > > > N: Updating from such a repository can't be done securely, and is > > > therefore disabled by default. > > > N: See apt-secure(8) manpage for repository creation and user > > > configuration details. > > > root@test: > > > > > > According to the error messages you are missing the public signing key so > > the repos are being disabled. You will need to download and install the key. > > Just to be clear, you aren't replying to the OP. The OP has a > different problem. They need to work out why they are forbidden > (403) from browsing the wheezy repository. They can test if it works > in a regular web browser. Unfortunately, the OP has not subscribed to -user. He is possibly sitting back awaiting replies in his personal mailbox > In Brian's case it is expected that the wheezy repository on > archive.debian.org gives these errors as the key has expired and > there is no valid key anywhere at this point, so as already > mentioned if one wants to use archive,debian.org for wheezy one > needs to override these errors, not search for a working key. Exactly. I tested. It was hardly rocket science. -- Brian.
Re: Need working repo for Deb7 - wheezy
Hello, On Fri, Aug 05, 2022 at 12:27:19PM -0400, Timothy M Butterworth wrote: > On Fri, Aug 5, 2022 at 8:20 AM Brian wrote: > > W: GPG error: http://archive.debian.org/debian wheezy Release: The > > following signatures couldn't be verified because the public key is not > > available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY > > 6FB2A1C265FFB764 > > E: The repository 'http://archive.debian.org/debian wheezy Release' is > > not signed. > > N: Updating from such a repository can't be done securely, and is > > therefore disabled by default. > > N: See apt-secure(8) manpage for repository creation and user > > configuration details. > > root@test: > > > > According to the error messages you are missing the public signing key so > the repos are being disabled. You will need to download and install the key. Just to be clear, you aren't replying to the OP. The OP has a different problem. They need to work out why they are forbidden (403) from browsing the wheezy repository. They can test if it works in a regular web browser. In Brian's case it is expected that the wheezy repository on archive.debian.org gives these errors as the key has expired and there is no valid key anywhere at this point, so as already mentioned if one wants to use archive,debian.org for wheezy one needs to override these errors, not search for a working key. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Need working repo for Deb7 - wheezy
On Fri, Aug 5, 2022 at 8:20 AM Brian wrote: > On Fri 05 Aug 2022 at 07:41:31 -0400, Greg Wooledge wrote: > > > On Fri, Aug 05, 2022 at 07:42:20AM +, Karthik Jeyabalan wrote: > > > deb http://archive.debian.org/debian/ wheezy main > > > deb http://archive.debian.org/debian-security wheezy/updates main > contrib non-free > > > deb http://archive.debian.org/debian/ wheezy main non-free contrib > > > deb-src http://archive.debian.org/debian/ wheezy main non-free contrib > > > > > > > > > Unable to download repo, fails with below error message: > > > > > > W: Failed to fetch > http://archive.debian.org/debian/dists/wheezy/contrib/source/Sources > 403 Forbidden > > > > > > On Fri, Aug 05, 2022 at 11:10:18AM +0100, Brian wrote: > > > There is also http://archive.debian.org/debian/. > > > > > > I think the question is, "Why isn't http://archive.debian.org/debian/ > > working for me?" > > Indeed! > > I got > > root@test:~# apt update > Ign:1 http://archive.debian.org/debian wheezy InRelease > Get:2 http://archive.debian.org/debian wheezy Release [191 kB] > Get:3 http://archive.debian.org/debian wheezy Release.gpg [2,373 B] > Ign:3 http://archive.debian.org/debian wheezy Release.gpg > Reading package lists... Done > W: GPG error: http://archive.debian.org/debian wheezy Release: The > following signatures couldn't be verified because the public key is not > available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY > 6FB2A1C265FFB764 > E: The repository 'http://archive.debian.org/debian wheezy Release' is > not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > root@test: > > According to the error messages you are missing the public signing key so the repos are being disabled. You will need to download and install the key. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: Need working repo for Deb7 - wheezy
On Fri, Aug 05, 2022 at 07:42:20AM +, Karthik Jeyabalan wrote: deb http://archive.debian.org/debian/ wheezy main deb http://archive.debian.org/debian-security wheezy/updates main contrib non-free deb http://archive.debian.org/debian/ wheezy main non-free contrib deb-src http://archive.debian.org/debian/ wheezy main non-free contrib The first line is a partial duplicate of the third line. Other than that if I copy and paste this into sources.list on a wheezy machine it works fine for me, no 403 codes. You can look in /etc/apt/apt.conf and files in /etc/apt/apt.conf.d to see if you perhaps have a misconfigured proxy. You will also need to add Acquire::Check-Valid-Until "false"; to /etc/apt/apt.conf as the Release file has expired (as expected for an archived release).
Re: Need working repo for Deb7 - wheezy
On 2022-08-05, Tixy wrote: > On Fri, 2022-08-05 at 11:10 +0100, Brian wrote: >> On Fri 05 Aug 2022 at 19:54:38 +1000, David wrote: >> >> [...] >> >> > However archived repo snapshots are available via here: >> > https://snapshot.debian.org/ >> > which looks like it has sssd packages for wheezy. >> >> There is also http://archive.debian.org/debian/. >> > > Which is what the OP is using and getting a 403 Forbidden error. The > URL they are using works for me in a web browser so it's either a > transient issue or an issue with the OP's network being blacklisted or > something. > Or it could be something on the client side, as Greg mentioned.
Re: Need working repo for Deb7 - wheezy
On Fri, 2022-08-05 at 11:10 +0100, Brian wrote: > On Fri 05 Aug 2022 at 19:54:38 +1000, David wrote: > > [...] > > > However archived repo snapshots are available via here: > > https://snapshot.debian.org/ > > which looks like it has sssd packages for wheezy. > > There is also http://archive.debian.org/debian/. > Which is what the OP is using and getting a 403 Forbidden error. The URL they are using works for me in a web browser so it's either a transient issue or an issue with the OP's network being blacklisted or something. -- Tixy
Re: Need working repo for Deb7 - wheezy
On Fri, Aug 05, 2022 at 12:31:00PM -, Curt wrote: > On 2022-08-05, Brian wrote: > > On Fri 05 Aug 2022 at 07:41:31 -0400, Greg Wooledge wrote: > > > >> On Fri, Aug 05, 2022 at 07:42:20AM +, Karthik Jeyabalan wrote: > >> > deb http://archive.debian.org/debian/ wheezy main > >> > deb http://archive.debian.org/debian-security wheezy/updates main > >> > contrib non-free > >> > deb http://archive.debian.org/debian/ wheezy main non-free contrib > >> > deb-src http://archive.debian.org/debian/ wheezy main non-free contrib > >> > > >> > > >> > Unable to download repo, fails with below error message: > >> > > >> > W: Failed to fetch > >> > http://archive.debian.org/debian/dists/wheezy/contrib/source/Sources > >> > 403 Forbidden > >> > >> > >> On Fri, Aug 05, 2022 at 11:10:18AM +0100, Brian wrote: > >> > There is also http://archive.debian.org/debian/. > >> > >> > >> I think the question is, "Why isn't http://archive.debian.org/debian/ > >> working for me?" > > > > Indeed! > > > > Not only that, but one guy said the archive had been pulled down, > another guy said to go to snapshot.debian.org, and still another > validated the suggestion of using archive.debian.org, which brought us full > circle back to the OP. I'm wondering whether the OP is behind some kind of corporate or nation-state firewall that prevents the normal use of the Web, specifically unencrypted HTTP sessions. The only reason I mention this is because *I* work in such a place, and if I ever wanted to update one of my wheezy boxes, I'm not at *all* sure how I would go about it. HTTPS works, HTTP does not, and wheezy sources are only available in HTTP. So, it's a long shot, but maybe it's true for them as well.
Re: Need working repo for Deb7 - wheezy
On 2022-08-05, Brian wrote: > On Fri 05 Aug 2022 at 07:41:31 -0400, Greg Wooledge wrote: > >> On Fri, Aug 05, 2022 at 07:42:20AM +, Karthik Jeyabalan wrote: >> > deb http://archive.debian.org/debian/ wheezy main >> > deb http://archive.debian.org/debian-security wheezy/updates main contrib >> > non-free >> > deb http://archive.debian.org/debian/ wheezy main non-free contrib >> > deb-src http://archive.debian.org/debian/ wheezy main non-free contrib >> > >> > >> > Unable to download repo, fails with below error message: >> > >> > W: Failed to fetch >> > http://archive.debian.org/debian/dists/wheezy/contrib/source/Sources 403 >> > Forbidden >> >> >> On Fri, Aug 05, 2022 at 11:10:18AM +0100, Brian wrote: >> > There is also http://archive.debian.org/debian/. >> >> >> I think the question is, "Why isn't http://archive.debian.org/debian/ >> working for me?" > > Indeed! > Not only that, but one guy said the archive had been pulled down, another guy said to go to snapshot.debian.org, and still another validated the suggestion of using archive.debian.org, which brought us full circle back to the OP.
Re: Need working repo for Deb7 - wheezy
On Fri 05 Aug 2022 at 12:18:32 -, Curt wrote: > On 2022-08-05, wrote: > > > >> There is also http://archive.debian.org/debian/. > > > > Yep: I regularly use archive.debian.org to build retro packages (some > > customers are a bit slow upgrading). > > > > So does the OP. In my case being half asleep doesn't help :). -- Brian.
Re: Need working repo for Deb7 - wheezy
On Fri 05 Aug 2022 at 07:41:31 -0400, Greg Wooledge wrote: > On Fri, Aug 05, 2022 at 07:42:20AM +, Karthik Jeyabalan wrote: > > deb http://archive.debian.org/debian/ wheezy main > > deb http://archive.debian.org/debian-security wheezy/updates main contrib > > non-free > > deb http://archive.debian.org/debian/ wheezy main non-free contrib > > deb-src http://archive.debian.org/debian/ wheezy main non-free contrib > > > > > > Unable to download repo, fails with below error message: > > > > W: Failed to fetch > > http://archive.debian.org/debian/dists/wheezy/contrib/source/Sources 403 > > Forbidden > > > On Fri, Aug 05, 2022 at 11:10:18AM +0100, Brian wrote: > > There is also http://archive.debian.org/debian/. > > > I think the question is, "Why isn't http://archive.debian.org/debian/ > working for me?" Indeed! I got root@test:~# apt update Ign:1 http://archive.debian.org/debian wheezy InRelease Get:2 http://archive.debian.org/debian wheezy Release [191 kB] Get:3 http://archive.debian.org/debian wheezy Release.gpg [2,373 B] Ign:3 http://archive.debian.org/debian wheezy Release.gpg Reading package lists... Done W: GPG error: http://archive.debian.org/debian wheezy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY 6FB2A1C265FFB764 E: The repository 'http://archive.debian.org/debian wheezy Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. root@test:
Re: Need working repo for Deb7 - wheezy
On 2022-08-05, wrote: > >> There is also http://archive.debian.org/debian/. > > Yep: I regularly use archive.debian.org to build retro packages (some > customers are a bit slow upgrading). > So does the OP.
Re: Need working repo for Deb7 - wheezy
On Fri, Aug 05, 2022 at 07:42:20AM +, Karthik Jeyabalan wrote: > deb http://archive.debian.org/debian/ wheezy main > deb http://archive.debian.org/debian-security wheezy/updates main contrib > non-free > deb http://archive.debian.org/debian/ wheezy main non-free contrib > deb-src http://archive.debian.org/debian/ wheezy main non-free contrib > > > Unable to download repo, fails with below error message: > > W: Failed to fetch > http://archive.debian.org/debian/dists/wheezy/contrib/source/Sources 403 > Forbidden On Fri, Aug 05, 2022 at 11:10:18AM +0100, Brian wrote: > There is also http://archive.debian.org/debian/. I think the question is, "Why isn't http://archive.debian.org/debian/ working for me?"
Re: Need working repo for Deb7 - wheezy
On Fri, Aug 05, 2022 at 11:10:18AM +0100, Brian wrote: > On Fri 05 Aug 2022 at 19:54:38 +1000, David wrote: > > [...] > > > However archived repo snapshots are available via here: > > https://snapshot.debian.org/ > > which looks like it has sssd packages for wheezy. > > There is also http://archive.debian.org/debian/. Yep: I regularly use archive.debian.org to build retro packages (some customers are a bit slow upgrading). Cheers -- t signature.asc Description: PGP signature
Re: Need working repo for Deb7 - wheezy
On Fri 05 Aug 2022 at 19:54:38 +1000, David wrote: [...] > However archived repo snapshots are available via here: > https://snapshot.debian.org/ > which looks like it has sssd packages for wheezy. There is also http://archive.debian.org/debian/. -- Brian.
Re: Need working repo for Deb7 - wheezy
On Fri, 5 Aug 2022 at 19:45, Dan Purgert wrote: > On Aug 05, 2022, Karthik Jeyabalan wrote: > > We have few machines running EOL Debian 7- Wheezy and tried to connect > > deb repo by using below in sources.list, but they are not working. Can > > you please help to provide the working repo. > As far as I am aware, the repos are pulled down when the release > lifecycle ends (this was 2018 for Wheezy). The Wheezy end-of-life announcement is here: https://www.debian.org/News/2018/20180601 It looks like Wheezy is entirely unsupported by Debian. Unsupported, old software can be vulnerable to security exploits. However archived repo snapshots are available via here: https://snapshot.debian.org/ which looks like it has sssd packages for wheezy.
Re: Need working repo for Deb7 - wheezy
On Aug 05, 2022, Karthik Jeyabalan wrote: > Team Debian, > > We have few machines running EOL Debian 7- Wheezy and tried to connect > deb repo by using below in sources.list, but they are not working. Can > you please help to provide the working repo. As far as I am aware, the repos are pulled down when the release lifecycle ends (this was 2018 for Wheezy). -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860 signature.asc Description: PGP signature
