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

Bug#1031781: neurodebian-popularity-contest

7 views
Skip to first unread message

Jeffrey Mark Siskind

unread,
Feb 22, 2023, 10:10:04 AM2/22/23
to
Package: neurodebian-popularity-contest
Version: 0.41.2~nd100+1

I previously was running buster with neurodebian installed using the
instructions from

https://neuro.debian.net/

I upgraded to bullseye. That upgrade automatically did:

qobi@sapiencia>dpkg --get-selections|fgrep neuro
neurodebian-popularity-contest deinstall
qobi@sapiencia>

I then started getting cron messages of the form:

/etc/cron.daily/popularity-contest:
gpg: keyblock resource '/usr/share/popularity-contest/neurodebian-popcon.gpg': No such file or directory
gpg: 0x544665CB8B48DE1D: skipped: No public key
gpg: /var/log/popularity-contest.new: encryption failed: No public key
run-parts: /etc/cron.daily/popularity-contest exited with return code 2

Under advice from y...@dartmouth.edu, I did:

apt-get -y install neurodebian-archive-keyring

I also did:

apt-get -y install neurodebian

Now I have:

qobi@sapiencia>dpkg --get-selections|fgrep neuro
neurodebian install
neurodebian-archive-keyring install
neurodebian-popularity-contest deinstall
qobi@sapiencia>

But I still get the cron messages.

Jeff (http: //engineering.purdue.edu/~qobi)

Yaroslav Halchenko

unread,
Sep 1, 2023, 2:10:05 PM9/1/23
to
Sorry for the delay. Somehow I even didn't get any message on this bug
report being filed ... odd



On Mon, 20 Feb 2023, Yaroslav Halchenko wrote:
> > How do I get rid of this message?

> apt-get install neurodebian-archive-keyring

> ?

> Let me know how it goes... I will look more in detail later. If still
> observe the issue, reportbug neurodebian-archive-keyring to provide
> detail and so I don't forget about it

I was wrong about what package to implicate here:

you reported

> neurodebian-popularity-contest deinstall

and indeed that /usr/share/popularity-contest/neurodebian-popcon.gpg
is from that package. So I guess, you did/tried to

dpkg --remove neurodebian-popularity-contest

(not --purge) and that left the cron script present but without key
shipped in the package. That lead to the error.

To resolve it, just


dpkg --purge neurodebian-popularity-contest

which should also remove

/etc/popularity-contest.d/neurodebian.conf

and as a result to avoid that cron job script try to get that key and
report to our popcon server.

I think I have a fix...

FTR: here is a Dockerfile with which I have created a "test env"

(git)smaug:~exppsy[master]neurodebian-trash/debian-1031781
$> cat Dockerfile
FROM debian:buster

ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get -y update
RUN apt-get -y install eatmydata
RUN eatmydata apt-get -y install sudo gnupg wget locales

RUN wget -O /etc/apt/sources.list.d/neurodebian.sources.list http://neuro.debian.net/lists/buster.us-nh.li
bre && \
apt-key adv --recv-keys --keyserver hkps://keyserver.ubuntu.com 0xA5D32F012649A5A9 && \
apt-get update -qqq && \
apt-get install -y svgtune # just to pull in neurodebian-popularity-contest


and here is invocation to try a "fixed up" version:

docker run -it --rm -v $PWD/popcon/neurodebian.conf:/etc/popularity-contest.d/neurodebian.conf neurodebian-debug:1 bash -c 'set -x; echo PARTICIPATE="yes" >> /etc/popularity-contest.conf; dpkg --remove --force
-depends neurodebian-popularity-contest; ls -l /etc/cron.daily/popularity-contest /usr/share/popularity-co
ntest/neurodebian-popcon.gpg; ls -l /usr/share/doc/neurodebian-popularity-contest; bash -x /etc/cron.dail
y/popularity-contest'

--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW: http://www.linkedin.com/in/yarik
0 new messages