Hi Charles,
On Mon, 21 Oct 2013, Charles Plessy wrote:
I indeed had a look. The problem of asking for help is that it reverses the
roles. I am not the one who wants staden-io-lib be built on mips, sparc, where
I think it is not useful, nor on hurd, where I think that working on such a
package is totally prematurate given the state of that port.
but this is Debian. Someone decided that there are several architectures
where all packages should be available. Isn't it the task of the
maintainer to care for his packages? Or at least ask others for help?
I think that te work has to be done by somebody running Debian on one of these
architectures, and genuinely interested in using staden-io-lib there.
Do you expect from a normal biologist that he is able to solve problems
with Debian packaging?
Or, for
me to volunteer to participate, I would like to receive at least one message
from a biologist explaining why he needs the package to be built there.
Lets assume I am such a biologist using that package on Wheezy.
Everything is fine but I am shy and don't want to send an email to the maintainer
thanking him for his work. If you just remove the package from my beloved
mips architecture, I will have problems after I got my new Jessie laptop.
My package is gone and than it is too late
Even if I am working with sid, I would never know that my package has any
problem that needs to be solved. I am just using the available software.
It is different for new packages, but already available packages will just
be used ...
I will not stand on the way of people who want to do the porting work, but
as I wrote at the beginning of my request for removal on mips and sparc, there
has been 70 days without anybody volunteering.
But how should anybody know that a package has a problem?
Anyway, I committed some patches. If you don't mind, I will upload the
package tomorrow ...
Thorsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
