Package: ftp.debian.org
X-debbugs-CC: Simon Kelley <[EMAIL PROTECTED]>

According to its maintainer (see below), the slimserver package is too
outdated to be useful. New versions can't be uploaded to the archive
for copyright problems.

The maintainer then suggests that the package should be removed from
the archive....however did not request for such removal because he
lost his GPG key and can't get a new one in the keyring..


----- Forwarded message from Simon Kelley <[EMAIL PROTECTED]> -----

Date: Wed, 12 Mar 2008 11:29:54 +0000
From: Simon Kelley <[EMAIL PROTECTED]>
To: Christian Perrier <[EMAIL PROTECTED]>
Subject: Re: Intent to NMU slimserver to fix pending po-debconf l10n bugs
X-CRM114-Status: Good  ( pR: 46.9396 )

Christian,

The reason that I've not fixed these bugs is that the slimserver package
needs to be removed from Debian. It's very out-of-date, and copyright
problems prevent newer versions from going into Debian.

Slim Devices Inc. provide up-to-date Debian packages. Whilst the ideal
would be up-to-date and complete packages in Debian, that's not
available. It's better for users to get up-to-date packages from
Slim-devices than out-of-date ones from Debian.

The reason that I've not actioned the removal of the package, so far, is
that my GPG key is lost, and it's proving very difficult to get a new
one into the Keyring.

So, if you really want to solve this, don't NMU slimserver, either
remove it from the archive, or hassle the Keyring maintainers to fix my
key, The RT ticket number for the request is 324.


Cheers,

Simon.


Christian Perrier wrote:
> Dear Debian maintainer,
> 
> The slimserver Debian package, which you are the maintainer of, has
> pending bug report(s) which include translation updates or fixes
> for po-debconf, namely bug number 412049 (and maybe other similar bugs).
> 
> Even if we're still far from the release of the next Debian version,
> letting such bugs sleep in the BTS  is simply lowering
> the chances that your package interaction with its users may be done
> in something else than the English language. It is also not
> encouraging for translators.
> 
> I have the intention, as part of a more general action of the Debian
> i18n Task Force to build and possibly upload a non-maintainer upload
> for slimserver in order to fix this as well as all pending translations
> for the debconf templates.
> 
> Of course, an upload made by you would even be better...:-)
> 
> Such changes are always harmless, which explains why I safely consider
> building NMU's for such issues even though they're obviously non critical.
> 
> The schedule for the NMU (in case it happens, that is if you agree with it
> or if I don't receive any answer in 14 days) is roughly the following:
> 
>  Tuesday, March 11, 2008   : send this notice
>  Tuesday, March 25, 2008       : post a NMU announcement to debian-i18n with 
> you
>                  (maintainer) CC'ed
>  Friday, April 04, 2008       : deadline for receiving translation updates
>  Saturday, April 05, 2008       : build the package and upload it to 
> DELAYED/0-day
>                  send the NMU patch to the BTS
>  Sunday, April 06, 2008       : NMU uploaded to incoming
> 
> If you intent to upload yourself, please notify me so that I interrupt
> the process on my side.
> 
> In case I upload an NMU, I will subscribe to the Package Tracking System for
> slimserver and follow its life for 60 days after my NMU in order to fix
> any issue potentially introduced by my upload.
> 
> Let me know, as soon as possible, if you have any kind of objection to this
> process.
> 
> If you'd rather do the fix yourself, I will of course leave the package
> alone. Same if you have reasons not to do the update now.
> 

----- End forwarded message -----


Attachment: signature.asc
Description: Digital signature

Reply via email to