SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2015-05-01 20:03:00

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

[SOLVED] There is no public key available for the following key IDs:

if it's not one thing it's another. Jessie wasn't working for me in a fresh install for whatever reasons -- DVD - SD CARD
some screwed up glitch to mess me up - so I did the change the sources.list to point to jessie then update - upgrade - dist-upgrade -- ran into problems there too -- so F*$&#*$#*K it do a fresh install #! then go from there -- grrr DVD scretchy had to polish that a few times to get it to work finally got it reinstalled nothing but the iso installed then removed tint2conf changed sources.list update got this again, as I got this no public key when I did a update with the orginal souces.list too


W: There is no public key available for the following key IDs:
9D6D8F6BC857C906
W: There is no public key available for the following key IDs:
7638D0442B90D010
 NO_PUBKEY CBF8D6FD518E17E1
W: There is no public key available for the following key IDs:
7638D0442B90D010

I don't want to play with this thing in doing things to it to try and fix it only to mess it up more until I get someone that knows what that is all about -- does this have to do with crunchbang no longer supported ???
how to fix it just do a install upgrade and it will go away?

Last edited by userx-bw (2015-05-01 23:00:45)


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

Help fund CrunchBang, donate to the project!

#2 2015-05-01 20:23:12

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: [SOLVED] There is no public key available for the following key IDs:

^ thought I fixed it with

sudo apt-get install debian-keyring

it downloaded someting and installed it still getting this

Reading package lists... Done
W: There is no public key available for the following key IDs:
9D6D8F6BC857C906
W: There is no public key available for the following key IDs:
7638D0442B90D010
W: There is no public key available for the following key IDs:
7638D0442B90D010
 NO_PUBKEY CBF8D6FD518E17E1

nope its not fixed mad

== mod edit ==
Please don't quote your on post in the very next post.

Last edited by Sector11 (2015-05-01 21:17:34)


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#3 2015-05-01 20:39:25

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [SOLVED] There is no public key available for the following key IDs:

https://wiki.debian.org/gpghowto

It may be that the #! repositories are causing the problems.

When I have the time (not tonight) I will be trying to install & update/upgrade my old (2013) #! DVD -- I'll post back then.

Offline

#4 2015-05-01 20:44:51

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: [SOLVED] There is no public key available for the following key IDs:

Head_on_a_Stick wrote:

https://wiki.debian.org/gpghowto

It may be that the #! repositories are causing the problems.

When I have the time (not tonight) I will be trying to install & update/upgrade my old (2013) #! DVD -- I'll post back then.

keuuuuul -

as far as keyrings how too to remove / fix them I'll prob try this page and google that too. thanks

I'm going ahead with the apt-get dist-upgrade right now as I type this. repos set to stable/main etc and not jessie/main trying that first.


and good luck with yours

Last edited by userx-bw (2015-05-01 20:47:22)


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#5 2015-05-01 20:55:33

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [SOLVED] There is no public key available for the following key IDs:

userx-bw wrote:

and good luck with yours

I'm only doing it to investigate problems reported by yourself and other forum members...

Offline

#6 2015-05-01 20:58:49

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: [SOLVED] There is no public key available for the following key IDs:

Head_on_a_Stick wrote:
userx-bw wrote:

and good luck with yours

I'm only doing it to investigate problems reported by yourself and other forum members...

I figured that it was because you wanted to see for yourself what was going on -- but I figured I'd just toss you  good luck for good mesure --


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#7 2015-05-01 21:00:03

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [SOLVED] There is no public key available for the following key IDs:

Thanks wink

EDIT: Sorry if I was a bit snippy; it's chaos in the Debian forums ATM and I'm chasing my tail trying to help in about 10 different threads...
hmm

Last edited by Head_on_a_Stick (2015-05-01 21:01:30)

Offline

#8 2015-05-01 21:15:53

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: [SOLVED] There is no public key available for the following key IDs:

Head_on_a_Stick wrote:

Thanks wink

EDIT: Sorry if I was a bit snippy; it's chaos in the Debian forums ATM and I'm chasing my tail trying to help in about 10 different threads...
hmm

you where just being honest -- and that's all good -- and thank you for going out of your way to help me and others --

cking libtbb2 (4.2~20140122-5) ...
Selecting previously unselected package libopencv-core2.4:amd64.
Preparing to unpack .../libopencv-core2.4_2.4.9.1+dfsg-1+b1_amd64.deb ...
Unpacking libopencv-core2.4:amd64 (2.4.9.1+dfsg-1+b1) ...
Selecting previously unselected package libopencv-flann2.4:amd64.
Preparing to unpack .../libopencv-flann2.4_2.4.9.1+dfsg-1+b1_amd64.deb ...
Unpacking libopencv-flann2.4:amd64 (2.4.9.1+dfsg-1+b1) ...
Preparing to unpack .../libgtkglext1_1.2.0-3.2_amd64.deb ...
Unpacking libgtkglext1 (1.2.0-3.2) over (1.2.0-2) ...
Selecting previously unselected package libopencv-imgproc2.4:amd64.

thats where I am atr right now with my situration waiting for that to finish before getting to the keyring thing

Last edited by userx-bw (2015-05-01 21:17:19)


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#9 2015-05-01 21:23:53

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [SOLVED] There is no public key available for the following key IDs:

so I did the change the sources.list to point to jessie then update - upgrade - dist-upgrade

Are you installing a #! Waldorf then upgrading to Jessie using John Raff's HowTo?


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#10 2015-05-01 21:35:51

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: [SOLVED] There is no public key available for the following key IDs:

Sector11 wrote:

so I did the change the sources.list to point to jessie then update - upgrade - dist-upgrade

Are you installing a #! Waldorf then upgrading to Jessie using John Raff's HowTo?

no not really -- just did a fresh install of #! removed tint3conf first then just installed a dev package I needed before I installed a program I wrote to ./configure make make install  first to get that in there to be sure I'd not have problems with it (my stuff) then when I did the update off of the fresh install of crunchbang I get no keyring for a few items -- then just changed my sorces.list to stable/main not jessie/main and now am in the process of finishing up a dist-upgrade to see what I get left with.

when I updated using unstable just before jessie was reliesed I had no problems wse going from unstable then to jessie. but just a minute (hour or so) ago I had major dependances problems that lead me to just a fresh install of #! that is now giving a no public keyring error when apt-get update is ran even with the orginal sources.list and the Waldorf commented out before running update.

I'll go peek at that how to again in a minute
edit
that one?
http://crunchbang.org/forums/viewtopic.php?id=38994&p=1

I can't get any media that has Jessie on it to work with my laptop SD CARD or DVD netinstall or a flat out debian jessie 8.0 lxde.iso the install never gets that far before erroring out if it even gets past the first options start screen

Last edited by userx-bw (2015-05-01 21:44:59)


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#11 2015-05-01 21:57:56

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: [SOLVED] There is no public key available for the following key IDs:

upDate:

the No Public Key Available went away after I ran apt-get dist-upgrade leaving me with these packages to remove. list added for the courious ones that like to read that stuff.


Use 'apt-get autoremove' to remove them.
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
userx@crunchbangerz:~$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  accountsservice apache2-bin apg bluez bluez-obexd cheese-common
  cracklib-runtime cups-pk-helper dleyna-server gir1.2-gnomebluetooth-1.0
  gir1.2-gnomekeyring-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0
  gkbd-capplet gnome-bluetooth gnome-control-center gnome-control-center-data
  gnome-desktop3-data gnome-online-accounts gnome-settings-daemon
  gnome-user-share gstreamer0.10-ffmpeg gstreamer1.0-clutter
  gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly
  gtk3-engines-unico hwdata libaccountsservice0 libamd2.2.0
  libapache2-mod-dnssd libapr1 libaprutil1 libaprutil1-dbd-sqlite3
  libaprutil1-ldap libarchive12 libass4 libbind9-80 libcheese-gtk23 libcheese7
  libclass-isa-perl libclutter-1.0-0 libclutter-1.0-common
  libclutter-gst-2.0-0 libclutter-gtk-1.0-0 libcogl-common libcogl-pango20
  libcogl-path20 libcogl20 libcolamd2.7.1 libcolord-gtk1 libcolord1 libcrack2
  libdconf0 libdevmapper-event1.02.1 libdirac-decoder0
  libdleyna-connector-dbus-1.0-1 libdleyna-core-1.0-3 libdns88
  libdrm-nouveau1a libdvbpsi7 libebml3 libelfg0 libffi5 libfftw3-3
  libfftw3-long3 libfluidsynth1 libgail-3-0 libgconf2-4 libgcr-3-1 libgd2-xpm
  libgdu0 libgee-0.8-2 libgeoclue0 libgeocode-glib0 libglew1.7 libglib2.0-bin
  libgmime-2.6-0 libgnome-bluetooth10 libgnome-bluetooth13
  libgnome-desktop-3-10 libgnomekbd-common libgnomekbd8 libgoa-backend-1.0-1
  libgoffice-0.8-8 libgoffice-0.8-8-common libgphoto2-2 libgphoto2-port0
  libgrilo-0.2-1 libgssdp-1.0-3 libgstreamer-plugins-bad1.0-0 libgupnp-1.0-4
  libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-6 libgweather-common
  libibus-1.0-5 libical1a libicu48 libimobiledevice2 libinput5 libisc84
  libisccc80 libisccfg82 libjim0debian2 libjson0 liblcms1 liblvm2app2.2
  liblwres80 libmagickcore5 libmagickwand5 libmatroska5 libmediaart-1.0-0
  libminiupnpc5 libmjpegutils-2.1-0 libmozjs10d libmozjs20d libmpc2
  libmpeg2encpp-2.1-0 libmpg123-0 libmplex2-2.1-0 libnss-myhostname
  libobrender27 libobt0 libopencv-calib3d2.4 libopencv-contrib2.4
  libopencv-core2.4 libopencv-features2d2.4 libopencv-flann2.4
  libopencv-highgui2.4 libopencv-imgproc2.4 libopencv-legacy2.4
  libopencv-ml2.4 libopencv-objdetect2.4 libopencv-video2.4 libopenjpeg2
  libpackagekit-glib2-18 libparted0debian1 libplist1 libpoppler19
  libpostproc52 libproxy0 libpthread-stubs0 libpwquality-common libpwquality1
  libquvi-scripts libquvi7 librtmp0 librygel-core-2.4-2
  librygel-renderer-2.4-2 librygel-server-2.4-2 libsbc1 libsgutils2-2
  libsidplay1 libsrtp0 libswitch-perl libsystemd-daemon0 libsystemd-login0
  libt1-5 libtar0 libtbb2 libtcl8.5 libtelepathy-glib0 libtotem-plparser18
  libts-0.0-0 libumfpack5.4.0 libupower-glib1 libusbmuxd1 libwacom-common
  libwacom2 libwebp2 libwxbase2.8-0 libwxgtk2.8-0 libx264-123 libx264-142
  libxdo2 libxfce4util4 libxklavier16 mousetweaks openbox-themes
  openssh-blacklist openssh-blacklist-extra packagekit packagekit-tools
  python-aptdaemon python-aptdaemon.gtk3widgets python-cups python-cupshelpers
  python-defer python-gnupginterface python-libxml2 python-pycurl python-smbc
  python-software-properties python-wxgtk2.8 realmd rygel
  system-config-printer system-config-printer-udev tcl8.5 tsconf
  ttf-dejavu-core udisks xulrunner-20.0
0 upgraded, 0 newly installed, 204 to remove and 0 not upgraded.
After this operation, 329 MB disk space will be freed.
Do you want to continue? [Y/n] y

ran it using this sources.list

## CRUNCHBANG
## Compatible with Debian Wheezy, but use at your own risk.
#deb http://packages.crunchbang.org/waldorf waldorf main
#deb-src http://packages.crunchbang.org/waldorf waldorf main

## DEBIAN
#deb http://http.debian.net/debian jessie main contrib non-free
#deb-src http://http.debian.net/debian wheezy main contrib non-free

# MULTIMEDIA
deb http://www.deb-multimedia.org jessie main non-free
deb http://www.deb-multimedia.org jessie-backports main

## DEBIAN SECURITY
#deb http://security.debian.org/ jessie/updates main
#deb-src http://security.debian.org/ wheezy/updates main

deb http://ftp.us.debian.org/debian stable main contrib non-free

deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free

now to see what problems I might have as a result of a fresh install of Crunchbang Waldorf then just change sources.list to stable/main to upgrade the system.


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#12 2015-05-02 00:38:37

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [SOLVED] There is no public key available for the following key IDs:

userx-bw wrote:

upDate:

deb http://ftp.us.debian.org/debian stable main contrib non-free

deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free

OH OH!  Post #7 HoaS's signature - read the part about not breaking Debin.


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#13 2015-05-02 00:41:43

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [SOLVED] There is no public key available for the following key IDs:

Sector11 wrote:
userx-bw wrote:

upDate:

deb http://ftp.us.debian.org/debian stable main contrib non-free

deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free

OH OH!  Post #7 HoaS's signature - read the part about not breaking Debin.

It's fine S11 -- Jessie is Stable now wink

The OP may have troubles when Stretch goes Stable but that's a while away yet...

Offline

#14 2015-05-02 01:04:31

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: [SOLVED] There is no public key available for the following key IDs:

Sector11 wrote:
userx-bw wrote:

upDate:

deb http://ftp.us.debian.org/debian stable main contrib non-free

deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free

OH OH!  Post #7 HoaS's signature - read the part about not breaking Debin.

Head_on_a_Stick wrote:

It's fine S11 -- Jessie is Stable now wink


The OP may have troubles when Stretch goes Stable but that's a while away yet...

yeah it been released already as stable -- I just did that for peace of mind because the word Jessie was causing me head aches so I wrote  stable instead .. big_smile sources.list already been changed fyi --


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#15 2015-05-02 13:08:01

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [SOLVED] There is no public key available for the following key IDs:

Well, I R the rez noob  big_smile


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#16 2015-05-02 14:29:25

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [SOLVED] There is no public key available for the following key IDs:

Sector11 wrote:

Well, I R the rez noob  big_smile

You are not a n00b -- your conky skills are incredible.

My .conkyrc runs to a grand total of eight lines...

Offline

#17 2015-05-02 15:05:56

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: [SOLVED] There is no public key available for the following key IDs:

Head_on_a_Stick wrote:
Sector11 wrote:

Well, I R the rez noob  big_smile

You are not a n00b -- your conky skills are incredible.

My .conkyrc runs to a grand total of eight lines...

Sector11 wrote:

Well, I R the rez noob  big_smile

Yeah you were just stuck in "whats wrong with this?"  mode is all. it shut down that part of the brain that makes you think a little harder so it misfired and caused you to act on half a thought and not the complete thought. It happens to the best of us. look at that guy over there ---->  ]:D he's always running on half a thought.  yikes

Last edited by userx-bw (2015-05-02 15:09:08)


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#18 2015-05-02 15:12:44

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [SOLVED] There is no public key available for the following key IDs:

Head_on_a_Stick wrote:
Sector11 wrote:

Well, I R the rez noob  big_smile

You are not a n00b -- your conky skills are incredible.

My .conkyrc runs to a grand total of eight lines...

Thank you - but, conky is not knowing the things under the hood in Linux like you do.

I have learned an incredible amount just reading your responses to other people.

If your conky runs a total of 8 lines it's because you want it to do that.  I'd bet a pension cheque it's not for lack of know how.  wink

Besides ... I really don't take being the "rez noob" in a bad way.  I do help when and where I can and I'm cool with that.


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#19 2015-05-02 15:16:32

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [SOLVED] There is no public key available for the following key IDs:

userx-bw wrote:

look at that guy over there ---->  ]:D he's always running on half a thought.  yikes

{looking ... over there ---->}
AWWWW CRAP!  A mirror! lol lol lol


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#20 2015-05-02 15:38:58

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: [SOLVED] There is no public key available for the following key IDs:

Sector11 wrote:
userx-bw wrote:

look at that guy over there ---->  ]:D he's always running on half a thought.  yikes

{looking ... over there ---->}
AWWWW CRAP!  A mirror! lol lol lol

Haha that too happens to the best of us --  ]:D  big_smile  big_smile vanity LoL


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#21 2015-05-02 16:48:21

tknomanzr
#! Die Hard
From: Heavener, OK
Registered: 2014-12-09
Posts: 777

Re: [SOLVED] There is no public key available for the following key IDs:

The human mind is a curiosity. It is strange how I can stare at an obvious error and my brain keeps transparently plugging in the correct value. This happened to me in menu.xml recently. It took me hours of code folding and comparing to figure out the problem, which turned out to be very simple. I had not capitalized an "Execute" action right at the point where the menu broke. I had probably seen it 1,000 times and never noticed the error.

The other day, I was going to post a scrot of the Visual Studio Code Editor running on my machine. I chose a python wallpaper rotator that  I have been working on. Almost immediately, a logical flaw in the error trapping of the program jumped out at me. It's no biggy since I have been intending a rewrite of the whole thing into a proper command line tool but I did have to take another scrot.

It is for this reason, I either have somebody else vet my stuff or sideline it long enough to forget about it (This time-frame seems to keep getting shorter as I age). While I don't quite qualify for the Over-The_Hill Crunchbang club, I am getting dang close. At any rate, I don't blame age and/or intelligence for this stuff. I blame our curious mental faculties.

Last edited by tknomanzr (2015-05-02 16:48:41)

Offline

#22 2015-06-17 00:57:18

mtnspine
Member
Registered: 2014-11-17
Posts: 10

Re: [SOLVED] There is no public key available for the following key IDs:

[Edit #2] Solved!  realized a second step to the debian-keyring trick.  I also installed debian-archive keyring.  And that solved it.  Silly really.  I'm actually glad nobody answered that for me.  I'm like a child who walks into the middle of a movie with no frame of reference to what is going on.  Slowly but surely, I will come to understand.

[Edit] I found a post from pvsage in another thread suggesting to use wheezy-backports and to remove /etc/apt/preferences. I thought, maybe that would be my ticket...  It wasn't.  [/edit]

I see that the thread is marked by [Solved], but I'm not getting it, (I'm actually the rez noob, sorry).   Can I safely ignore the lack of public keys?  Can this be easily fixed? I'm on a fresh Waldorf install pointed to Wheezy.  I've tried installing debian-keyring or something, as it was suggested somewhere (it was late).  I tried the sources.list, pointed toward Jessie, that was pasted in this thread, (which actually made my install unbootable). I also tried commenting out the CB repos, to no avail.  Most recently I tried the link to /gpghowtohttps://wiki.debian.org/gpghowto, replacing the key id in the how-to with the one that showed up in the dialogue.

This is a fresh install with the default sources.list.

Reading package lists... Done
W: There is no public key available for the following key IDs:
9D6D8F6BC857C906
W: There is no public key available for the following key IDs:
7638D0442B90D010
al@lappy386:~$ gpg --recv-keys 9D6D8F6BC857C906
gpg: directory `/home/al/.gnupg' created
gpg: new configuration file `/home/al/.gnupg/gpg.conf' created
gpg: WARNING: options in `/home/al/.gnupg/gpg.conf' are not yet active during this run
gpg: keyring `/home/al/.gnupg/secring.gpg' created
gpg: keyring `/home/al/.gnupg/pubring.gpg' created
gpg: no keyserver known (use option --keyserver)
gpg: keyserver receive failed: bad URI
al@lappy386:~$ gpg --export -a 9D6D8F6BC857C906 | sudo apt-key add -
gpg: WARNING: nothing exported
[sudo] password for al: 
gpg: no valid OpenPGP data found.
al@lappy386:~$ sudo apt-get update
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://security.debian.org wheezy/updates Release                          
Hit http://security.debian.org wheezy/updates/main amd64 Packages              
Hit http://security.debian.org wheezy/updates/main Translation-en              
Hit http://http.debian.net wheezy Release.gpg                                  
Hit http://http.debian.net wheezy Release                   
Hit http://http.debian.net wheezy/main amd64 Packages                          
Hit http://http.debian.net wheezy/contrib amd64 Packages                       
Hit http://http.debian.net wheezy/non-free amd64 Packages                      
Hit http://http.debian.net wheezy/contrib Translation-en                       
Hit http://http.debian.net wheezy/main Translation-en                          
Hit http://http.debian.net wheezy/non-free Translation-en                      
Get:1 http://packages.crunchbang.org waldorf Release.gpg [287 B]
Get:2 http://packages.crunchbang.org waldorf Release [7,022 B]
Get:3 http://packages.crunchbang.org waldorf/main amd64 Packages [31.4 kB]
Ign http://packages.crunchbang.org waldorf/main Translation-en_US
Ign http://packages.crunchbang.org waldorf/main Translation-en
Fetched 38.7 kB in 34s (1,127 B/s)
Reading package lists... Done
W: There is no public key available for the following key IDs:
9D6D8F6BC857C906
W: There is no public key available for the following key IDs:
7638D0442B90D010
al@lappy386:~$ 

Last edited by mtnspine (2015-06-17 04:05:13)

Offline

#23 2015-06-17 12:44:52

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: [SOLVED] There is no public key available for the following key IDs:

mtnspine wrote:

[Edit #2] Solved!  realized a second step to the debian-keyring trick.  I also installed debian-archive keyring.  And that solved it.  Silly really.  I'm actually glad nobody answered that for me.  I'm like a child who walks into the middle of a movie with no frame of reference to what is going on.  Slowly but surely, I will come to understand.

[Edit] I found a post from pvsage in another thread suggesting to use wheezy-backports and to remove /etc/apt/preferences. I thought, maybe that would be my ticket...  It wasn't.  [/edit]

I see that the thread is marked by [Solved], but I'm not getting it, (I'm actually the rez noob, sorry).   Can I safely ignore the lack of public keys?  Can this be easily fixed? I'm on a fresh Waldorf install pointed to Wheezy.  I've tried installing debian-keyring or something, as it was suggested somewhere (it was late).  I tried the sources.list, pointed toward Jessie, that was pasted in this thread, (which actually made my install unbootable). I also tried commenting out the CB repos, to no avail.  Most recently I tried the link to /gpghowtohttps://wiki.debian.org/gpghowto, replacing the key id in the how-to with the one that showed up in the dialogue.

This is a fresh install with the default sources.list.

Reading package lists... Done
W: There is no public key available for the following key IDs:
9D6D8F6BC857C906
W: There is no public key available for the following key IDs:
7638D0442B90D010
al@lappy386:~$ gpg --recv-keys 9D6D8F6BC857C906
gpg: directory `/home/al/.gnupg' created
gpg: new configuration file `/home/al/.gnupg/gpg.conf' created
gpg: WARNING: options in `/home/al/.gnupg/gpg.conf' are not yet active during this run
gpg: keyring `/home/al/.gnupg/secring.gpg' created
gpg: keyring `/home/al/.gnupg/pubring.gpg' created
gpg: no keyserver known (use option --keyserver)
gpg: keyserver receive failed: bad URI
al@lappy386:~$ gpg --export -a 9D6D8F6BC857C906 | sudo apt-key add -
gpg: WARNING: nothing exported
[sudo] password for al: 
gpg: no valid OpenPGP data found.
al@lappy386:~$ sudo apt-get update
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://security.debian.org wheezy/updates Release                          
Hit http://security.debian.org wheezy/updates/main amd64 Packages              
Hit http://security.debian.org wheezy/updates/main Translation-en              
Hit http://http.debian.net wheezy Release.gpg                                  
Hit http://http.debian.net wheezy Release                   
Hit http://http.debian.net wheezy/main amd64 Packages                          
Hit http://http.debian.net wheezy/contrib amd64 Packages                       
Hit http://http.debian.net wheezy/non-free amd64 Packages                      
Hit http://http.debian.net wheezy/contrib Translation-en                       
Hit http://http.debian.net wheezy/main Translation-en                          
Hit http://http.debian.net wheezy/non-free Translation-en                      
Get:1 http://packages.crunchbang.org waldorf Release.gpg [287 B]
Get:2 http://packages.crunchbang.org waldorf Release [7,022 B]
Get:3 http://packages.crunchbang.org waldorf/main amd64 Packages [31.4 kB]
Ign http://packages.crunchbang.org waldorf/main Translation-en_US
Ign http://packages.crunchbang.org waldorf/main Translation-en
Fetched 38.7 kB in 34s (1,127 B/s)
Reading package lists... Done
W: There is no public key available for the following key IDs:
9D6D8F6BC857C906
W: There is no public key available for the following key IDs:
7638D0442B90D010
al@lappy386:~$ 

What are you trying to do, an upgrade to Jessie, or what
Because when I an into this during an upgrade. I just paid it no mind then did the dist-upgrade installing Jessie from wheezy and that just went away. It fix itself


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#24 2015-06-17 19:38:15

mtnspine
Member
Registered: 2014-11-17
Posts: 10

Re: [SOLVED] There is no public key available for the following key IDs:

I'm just trying to stay with wheezy for now.  I've been distro-hopping a bit and wanted to come back to #! before BunsenLabs is stable.  It appears that everything is as it should be, except I removed tint2 just in case, so I'll have to get that set up the way I want.  I may upgrade to Jessie in the near future, (I'm still a little hesitant of systemd sad )

al@lappy386:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 7.8 (wheezy)
Release:	7.8
Codename:	wheezy

I installed debian-keyring and debian-archive-keyring.  This is my sources.list taken from a post by pvsage in another thread:

#security.list:
deb     http://security.debian.org/         wheezy/updates  main contrib non-fr$

#stable.list:
deb     http://ftp.us.debian.org/debian/    wheezy main contrib non-free
#deb-src http://ftp.us.debian.org/debian/    wheezy main contrib non-free

deb     http://ftp.us.debian.org/debian/    wheezy-backports main contrib non-f$
#deb-src http://ftp.us.debian.org/debian/    wheezy-backports main contrib non-$

Offline

Help fund CrunchBang, donate to the project!

#25 2015-06-17 19:45:21

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [SOLVED] There is no public key available for the following key IDs:

mtnspine wrote:

I may upgrade to Jessie in the near future, (I'm still a little hesitant of systemd sad )

If you upgrade from wheezy to jessie, you will find GRUB menu entries (in the "Advanced Options" section) to boot with SysVinit rather than systemd wink

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat

Debian Logo