Bug#301951: developer.php: picks up wrong gpg key

2005-03-29 Thread Miros/law L. Baran
Package: qa.debian.org
Severity: normal

Hi,

The developer.php script shows bad key ID for the '[EMAIL PROTECTED]'
address; it lists the 9E080E1C (my jabber encryption key) where it
should list FC494FC4 (my main gpg key). Both have the id
'[EMAIL PROTECTED]' and in my jabber key it is the default id, but
anyways, it should not fail in that way. (Maybe it should try to
download key from the keyring.debian.org and only fall back to another
server when it could not find the key there?)

Kind regards
Jubal

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8
Locale: LANG=polish, LC_CTYPE=polish (charmap=ISO-8859-2)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



celestia, remove or QA maintain?

2005-03-29 Thread Andrew Pollock
Hi,

I'm inclined to reassign the WNPP bug for celestia to ftp.debian.org, on the
grounds that #174456 probably isn't going to get resolved whilst it is under
QA maintenance, but I wanted to see what others thought first.

regards

Andrew

-- 
linux.conf.au 2005   -  http://linux.conf.au/  -  Birthplace of Tux
April 18th to 23rd   -  http://linux.conf.au/  -   LINUX
Canberra, Australia  -  http://linux.conf.au/  -Get bitten!


signature.asc
Description: Digital signature


Re: celestia, remove or QA maintain?

2005-03-29 Thread Jeroen van Wolffelaar
On Wed, Mar 30, 2005 at 11:50:13AM +1000, Andrew Pollock wrote:
> Hi,
> 
> I'm inclined to reassign the WNPP bug for celestia to ftp.debian.org, on the
> grounds that #174456 probably isn't going to get resolved whilst it is under
> QA maintenance, but I wanted to see what others thought first.

Please let the wnpp bug age for a bit (so, QA maintain). It's orphaned
for only a couple of weeks yet.

--Jeroen

-- 
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl



1$BEPO?(B5000$B1_(B$B!z%"%U%#%j%(%$%H$N$*CN$i$;(B

2005-03-29 Thread $B$d$^$,$_(B
$BFMA3$N%a!<%k$K$F<:NiCW$7$^$9!#(B
(B886644$B%"%U%#%j%(%$%H%7%9%F%`!&C4Ev!';3>e$H?=$7$^$9!#(B
(B
$B@'Hs9-9p7G:\$r$*4j$$$7$?$/%a!<%k$r:9$7>e$2$^$7$?!#(B
(B
$BEvl9g$O%/%j%C%/[EMAIL PROTECTED]/@8$G$9"v(B
$B!J>\:Y6b3[$O(BHP$B$r$4Mw$/[EMAIL PROTECTED]&E&E&E&E&E(.(B( 
$B!&(B_$B!&(B)$B(0!K(B
(B
(B $B?75,$4;22C$NJ}$K%W%i%9(B
(B $B!J!J!J!J#3(B.$B#0#0#01_%W%l%<%s%H%-%c%s%Z!<%sCf!K!K!K!K(B
(B
$B#3G/4V$N1?1D<[EMAIL PROTECTED],$"$j$^$9$N$G!"0B?4$7$F$4;[EMAIL 
(BPROTECTED];W$$$^$9!#(B
(B
$B#P#C%5%$%H!&7HBS%5%$%H6&$K;22C2DG=$G$9!#(B
(B $B#12s$N\$7$/$O%3%A%i!,!&(B*:.$B!#(B. 
(B.$B!#(B.:*$B!&!,(B
(B $B!!(Bhttp://886644.com/view/pc/
$B(B $B!~!~7HBS$+$i$O%3%A%i!~!~(B
(B $B!!(Bhttp://886644.com/view/keitai/
(B
$B!&!#!&!,!z!&!#!&!#!y!&!,!&!#!&!,!#!&!#!&!,!z!&!#!&!#!y(B
$B>0!":#8e$40FFb$,ITMW$J>l9g$O$=$N;]$r2<5-%"%I%l%9$^$G(B
$B$4JV?.$/[EMAIL PROTECTED](B
(B<$BAw?.$B!!(B886644$B%"%U%#%j%(%$%H(B
(B<$B [EMAIL PROTECTED]
(B*$B!&!#!&!,!z!&!#!&!#!y!&!,!&!#!&!,!#!&!#!&!,!z!&!#!&!#!y(B
(B
(B
(B-- 
(BTo UNSUBSCRIBE, email to [EMAIL PROTECTED]
(Bwith a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: removal suggestion for openmosix from testing

2005-03-29 Thread Stephen Frost
* Martin Zobel-Helas ([EMAIL PROTECTED]) wrote:
> i am not sure if i overlooked your answer to my last mail. Is there anything 
> we
> can help on #232810? As we are going to freeze realy soon now (looks like both
> ends of the toolchain are fixed by now), i fear that openmosix will be 
> dropped 
> from sarge.

You could try to get OpenMosix upstream to release a patch for a 2.6
kernel...  Unfortunately I don't tend to use OpenMosix any more since
basically all of my systems run 2.6 now.  There's a 2.6 patch that's
been coming along but it's still missing some important parts (some of
which are userspace) to be useable, along with proper testing and
whatnot.

If someone's interested in OpenMosix for 2.4 and want to see it in sarge
I'd encourage them to hijack the package or contact me about getting the
issues fixed and be able to provide proper testing for .debs I build.  I
don't like uploading .debs I havn't been able to test decently.

Sorry about not addressing this sooner.

Stephen


signature.asc
Description: Digital signature