<div dir="ltr"><div><div><div><div><div>Well Andreas,<br></div>basically I ment upstream Debian development not really taking over the development of dicompyler itself.<br><br></div>I think there are issues with the current Debian package but it can be useful for particular users to have it in Debian. I think I can fix in a month or so the problems regarding widgets and make it reasonable stable to the next stable Debian release. <br><br></div>So please lower the severity to important and I am OK with a git, I will set up some development branch and when it will be ready merge it to the master.<br><br></div>Kind regards,<br></div>Vojtech.<br></div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-10 10:55 GMT+01:00 Andreas Tille <span dir="ltr"><<a href="mailto:andreas@fam-tille.de" target="_blank">andreas@fam-tille.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Vojtech,<br>
<span class=""><br>
On Fri, Mar 10, 2017 at 10:23:35AM +0100, Vojtech Kulvait wrote:<br>
> If I were about to take care about this package in upstream what should I<br>
> do and what is the development timetable?<br>
<br>
</span>I'm not really sure what you need to take over upstream - probably the<br>
owner of the project needs to grant you commit permissions to the<br>
repository.<br>
<br>
Regarding the Debian package it is sufficient to develop a (quilt-)patch<br>
that lets the program work. If you prefer SVN over Git I can move the<br>
packaging to Git but you can also simply sent a patch here to this bug.<br>
The development time table is quite clear and the status page<br>
<br>
<a href="https://tracker.debian.org/pkg/dicompyler" rel="noreferrer" target="_blank">https://tracker.debian.org/<wbr>pkg/dicompyler</a><br>
<br>
says:<br>
<br>
Marked for autoremoval on 11 March: 854837<br>
<br>
Version of dicompyler is marked for autoremoval from testing on Sat<br>
11 Mar 2017. It is affected by 854837. You should try to prevent the<br>
removal by fixing these RC bugs.<br>
<br>
So well, this is tomorrow which is a bit dense to meet the next stable<br>
release. Removal from testing means the package will not be shipped<br>
with the next official Debian stable release. However, in case the<br>
package gets fixed I'd happily provide it via <a href="http://backports.debian.org" rel="noreferrer" target="_blank">backports.debian.org</a> and<br>
if the development continues in the next stable Debian release (usually<br>
about two years are inbetween two stable releases).<br>
<br>
BTW, there is one way to deliver the current dicompyler in next Debian<br>
Stable if you say: Well, it is buggy but has some practical use anyway.<br>
In this case we could lower the severity of the bug to "important" which<br>
is not release critical. Since I'm no user of the package I can not<br>
really decide what severity is correct in this case.<br>
<br>
Hope this explanation is helpful<br>
<span class="HOEnZb"><font color="#888888"><br>
Andreas.<br>
<br>
--<br>
<a href="http://fam-tille.de" rel="noreferrer" target="_blank">http://fam-tille.de</a><br>
</font></span></blockquote></div><br></div>