Hello Michael,

In June I was very lucky as I got the overtaken package 'capi4hylafax'
still in testing before freeze. Since then I have found some small
problems with the package and I searched for a way to update the package
in the freeze period (I am only DM).

Michael Gilbert wrote on 2012-10-30 16:41:

> As the maintainer of this package, it is your responsibility to set
> the appropriate bug severity so that the rest of us know how critical
> the issue is, and how important the sponsorship would be.

In theory I know I can change bug severities, but in respect to the person
who send a bug report I do it not often.
 
> Finally, I don't see a request on sponsorship-requests anyway:
> http://bugs.debian.org/sponsorship-requests

I uploaded to mentors.d.n at 05.08.2012 and wrote an RFS at 06.08.2012.
Then I had some responses from Bart Martens with questions to the fixes in
this package. It seemed the fixes are not so important for the wheezy
release. Then I have removed my update and the RFS where closed (by Bart
Martens at 19.08.2012).

Then I have started my request at 14.08.2012 to the release-team about
update permission of this package. In October Julien Cristau had answered
and asked some questions about the fixes of the updated packages. Some
changes seems to be irrelevant or must be resolved in another way. Finally
it remained only the fix because of the recommended package "isdnactivecards".

Now with the new bug report (the second about the same problem) it seems
this problem should be solved. On the other hand this problem creates no
problem while installing or using capi4hylafax.

And now I have the same question as weeks before: is it important enough
to ask again the release team about permission for an updated package? I
think only this item is not worth enough for an updated package. But on
the other side it is against the policy ...

---
Have a nice day.

Joachim (Germany)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to