This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
I had not needed to install it again, but I tried that now. It no longer
complains about signing issues.
--
netmask in dapper and edgy currently "cannot be authenticated"
https://bugs.launchpad.net/bugs/61275
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Thanks in advance.
** Changed in: debian-archive-keyring (Ubuntu)
Status
Running 'apt-get update' does not fix the situation. Can you give me a
quick reminder of the signing-chain. I remember it being something like
Release.gpg -> Release -> md5sum(Packages) -> md5sum(foo.deb) ?
--
netmask in dapper and edgy currently "cannot be authenticated"
https://launchpad.net/
Does runing apt-get update fix the situation?
--
netmask in dapper and edgy currently "cannot be authenticated"
https://launchpad.net/bugs/61275
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
'debian-archive-keyring' also shows up as unsigned, but that could be
something "special" to do with the debian keyring being signed by the
previous debian-archive signing key.
--
netmask in dapper and edgy currently "cannot be authenticated"
https://launchpad.net/bugs/61275
--
ubuntu-bugs mail
Confirmed for dapper
** Changed in: netmask (Ubuntu)
Status: Unconfirmed => Confirmed
--
netmask in dapper and edgy currently "cannot be authenticated"
https://launchpad.net/bugs/61275
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
mvo: I'm not sure how to start debugging this. What's the best way to
follow the signing chain backwards?
--
netmask in dapper and edgy currently "cannot be authenticated"
https://launchpad.net/bugs/61275
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
