IWETHEY v. 0.3.0 | TODO
1,095 registered users | 1 active user | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New How to find out why a package was pulled from Debian

As part of my UNIX admin course this term, my students are setting up public key servers using pks. However, recently I noticed that the package has been pulled from stable/unstable/testing. (The pks proxy client and server were still there.)

I tried the usual sources (Google, Sourceforge, debian.org) to find out what was going on, but still not sure why this was pulled.

Any ideas? License dispute? Author request? Broken package? It's still available on Sourceforge, so I don't think the author pulled it.

I managed to snag a copy out of an apt cache and store it away for safekeeping but are there any particular places I can go to find out what happened?

Tom Sinclair

"While I'm still confused and uncertain, it's on a much higher plane, d'you
see, and at least I know I'm bewildered about the really fundamental and
important facts of the universe."
Treatle nodded. "I hadn't looked at it like that," he said, "But you're
absolutely right. He's really pushed back the boundaries of ignorance."
-- Discworld scientists at work
(Terry Pratchett, Equal Rites)
New Just ask on Debian Devel.
Especially ask Colin Watson or Steve Langasek (if they poke a nose in to answer), you'll never get an answer out of Troup or Remenant. Although both Steve and Colin are very busy wrangling Sarge right now.

You should really subscribe until you get an answer.

Ask a fully qualified question too, always helps.

Explain your situation, why it is important to you.
--
[link|mailto:greg@gregfolkert.net|greg],
[link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwethey
No matter how much Microsoft supporters whine about how Linux and other operating systems have just as many bugs as their operating systems do, the bottom line is that the serious, gut-wrenching problems happen on Windows, not on Linux, not on Mac OS. -- [link|http://www.eweek.com/article2/0,1759,1622086,00.asp|source]
Here is an example: [link|http://www.greymagic.com/security/advisories/gm001-ie/|Executing arbitrary commands without Active Scripting or ActiveX when using Windows]
New Thanks
Tom Sinclair

"While I'm still confused and uncertain, it's on a much higher plane, d'you
see, and at least I know I'm bewildered about the really fundamental and
important facts of the universe."
Treatle nodded. "I hadn't looked at it like that," he said, "But you're
absolutely right. He's really pushed back the boundaries of ignorance."
-- Discworld scientists at work
(Terry Pratchett, Equal Rites)
New 't was the package maintainer
[link|http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266139|http://bugs.debian.o...rt.cgi?bug=266139]

As the maintainer of the pks (PGP/GPG Public Key Server) I would like to request that it be removed from the archive.
My reasoning for this is that it is currently a buggy, unsupported implementation of a keyserver. It has difficulty with multiple subkeys (though at least doesn't mangle them like it used to). It doesn't support photoids (though I accept this is mainly cosmetic). Upstream is mostly dead (I speak as someone with commit access to cvs) and the
majority of keyserver hosts appear to be using other servers. I don't believe we should be releasing this as part of stable.
New Re: 't was the package maintainer

That explains that. Guess I'll have to look for a new keyserver package (or compile pks from source).

Tom Sinclair

"While I'm still confused and uncertain, it's on a much higher plane, d'you
see, and at least I know I'm bewildered about the really fundamental and
important facts of the universe."
Treatle nodded. "I hadn't looked at it like that," he said, "But you're
absolutely right. He's really pushed back the boundaries of ignorance."
-- Discworld scientists at work
(Terry Pratchett, Equal Rites)
     How to find out why a package was pulled from Debian - (tjsinclair) - (4)
         Just ask on Debian Devel. - (folkert) - (1)
             Thanks -NT - (tjsinclair)
         't was the package maintainer - (scoenye) - (1)
             Re: 't was the package maintainer - (tjsinclair)

Everything is chromed in the future!
55 ms