Re: no response Fwd: Bug#905080: O: as31 - Intel 8031/8051 assembler
Please send this to the debian-mentors list instead of exclusively to
me. I did not mean to imply that I personally would be offering
mentorship or sponsorship, and in any case, my abilities are limited
since I am not a DD.
On 2019-04-11, Albert van der Horst <albert@spenarnc.xs4all.nl> wrote:
> Jason Crain schreef op 2019-04-09 19:35:
> > On Tue, Apr 09, 2019 at 07:05:29PM +0200, Albert van der Horst wrote:
> > > I followed up on a "orphaned bug" by adding a message to the bug
> > > 905080.
> > > This got never a response. Did I make a mistake with respect to the
> > > Debian protocols?
> > > I seem to remember that I got a confirmation that in "due course" a
> > > Debianist would
> > > respond.
> > > And no, the 8051 is not dead by a long stretch. So deleting from the
> > > Debian distribution is not good.
> >
> > If you are intending to adopt the package, you should rename the O
> > (Orphaned) bug to ITA (Intent To Adopt) and create an updated package
> > fixing some of the issues and naming yourself as maintainer. Then, if
> > you need a sponsor, upload the package to mentors.debian.net and create
> > a RFS (Request For Sponsorship) bug to request that a Debian Developer
> > review and upload the package for you.
>
> If there were issues, I would solve all of them. before uploading a package.
> There are no technical issues, that I would tackle gladly,
> only a very nasty formalistic one.
> "Although it is known that it is licensed under BSD, there is only an
> assumption that it is "3-clause" BSD."
> I see that the maintainer commented on the issue, but did not classify
> it. I think that the first thing to do for an issue is to classify it.
> Now I've no idea how important it is to solve this issue.
In addition to the license issue, I see a few minor things listed on the
tracker page https://tracker.debian.org/pkg/as31, including a warning
that the VCS repository is out of date, a lintian warning about a
deprecated debhelper version, a build log warning about hardening flags,
and a note that the standards version is out of date. I don't know how
easy some of those will be to fix, but you should try to fix the ones
that you can.
The license is probably not that big of an issue, since I think any
version of the BSD license would be free, but you could try to contact
upstream to see if they will clarify the license.
> I've just been through the painful process of getting a package in a
> formally acceptable state, just to find out that there is no one willing
> to sponsor. Can you or anyone give an idea of the chance this would happen
> again?
> I've no connections to speak of in the Debian community.
> The orphaner got my message but didn't warn a newbee that renaming of the
> bug
> was necessary to get things rolling. Is that a bad sign or
> is there a chance that the orphaner would for a limited time be willing to
> sponsor?
Yes, you can ask the orphaner if he is willing to sponsor your package,
but he may decline or not respond for many reasons, including lack of
available time. If he won't, you should file a sponsorship bug as
described at https://mentors.debian.net/sponsors. Though note that since
Debian is in a freeze, your package will probably not be uploaded to
unstable until Debian Buster is released, possibly several months from
now.
I'm sorry that you were not able to find a sponsor for your previous
package. I haven't had too much trouble finding sponsors before, so my
only advice is to try again.
> If I'd rid the package of some technical defect and it wouldn't be accepted,
> that would not
> mean a great deal to me, because the effort is not really wasted, as long as
> I publish it somewhere. However if after a long e-mail exchange I finally
> managed to fix a copyright message and it would not be accepted I
> would be really depressed. Same if the only change was to list myself as
> as maintainer.
>
>
> Groetjes Albert
>
> --
> Suffering is the prerogative of the strong, the weak -- perish.
> Albert van der Horst
Reply to: