offer for adoption: sidplay and FreePascal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
unfortunately I'll neither can afford the time nor the bandwith to
work on my packages in the near future: I'll move to another part
of Germany, get a new job, write my dissertation, need to concentrate
on the more private parts of my life. So I can't foresee exactly when
these circumstances will change.
Hence, I offer my packages for adoption:
libsidplay (libsidplay1(-dev))
sidplay-base
xsidplay
fp-compiler
fp-docs
fp-units-api
fp-units-base
fp-units-db
fp-units-fcl
fp-units-gfx
fp-units-gtk
fp-units-misc
fp-units-net
fp-units-rtl
fp-utils
The packages are actually easy to maintain and aren't updated too often.
All fp-* packages build from the same source in one run. So they need
ONE maintainer. The sidplay packages should also stay together, I'd think.
There are only a few bugs - cosmetical as regards FreePascal (and/or fixed
in upstream CVS). However, there are serious bugs against the sidplay
packages - all of "cannot build from source"-type. I don't have the time
and ressource to work on these. The bug on HPPA architecture maybe
probably easily closed: The package will not work currently on HPPA
anyway.
xsidplay should probably be updated too (version 1.6.2 is available).
Upstream maintainers are very responsive and helpful.
If nobody adopts the packages I'll orphan them in about two weeks. Am I
right, that I need to upload the packages with Debian Q/A as maintainer
and report a bug against wnpp? Should I do this for all fp-* packages
or only for the source?
Greetings,
Ulf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
iD8DBQE7jPHavdGZ/EPkPdsRAuH4AKDfBkAm25lsSfk3FqkY+Ca+UzELNwCeOiKL
vmEFyiL8p2MNObWU8eS7ffo=
=aXcp
-----END PGP SIGNATURE-----
Reply to: