From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Clemens Ladisch <clemens@ladisch.de>,
Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>
Cc: hayashi@clear-code.com,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
linux1394-devel@lists.sourceforge.net,
"ffado-devel@lists.sf.net" <ffado-devel@lists.sf.net>
Subject: Re: About planning of libhinawa ITP to debian project
Date: Sun, 7 Feb 2016 22:10:25 +0900 [thread overview]
Message-ID: <56B74241.6040803@sakamocchi.jp> (raw)
In-Reply-To: <56B6B599.2020002@sakamocchi.jp>
Hi,
On Feb 7 2016 12:10, Takashi Sakamoto wrote:
> Hi,
>
> On Feb 2 2016 23:04, Takashi Sakamoto wrote:
>> On Jan 31 2016 20:45, Takashi Sakamoto wrote:
>>> In this message, I explain about a plan of libhinawa ITP[0] to debian
>>> project. Fortunately, I got a help of a debian package maintainer,
>>> Kentaro Hayashi. He maintains groonga package[1] and experienced
>>> related works[2].
>>>
>>> Currently, we plan to work for it in next month, February 2016. I have
>>> no idea about when FTP master acked to our ITP and when the package is
>>> released from debian project.
>>
>> Today, we register this to Debian Bug report #813474.
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813474
>>
>> And start RFS (Request For Sponsorship).
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813489
>>
>> Thanks for Kentaro.
>
> A few days ago, we got a sponsor for the package and yesterday it's in
> new queue. Today, a few hours before, I received a notification that the
> package was granted and moved to Debian ftp-master server.
>
> In short, the package is in unstable repository and may be released
> within a few days. Thanks all.
Now it's in Debian unstable.
https://packages.debian.org/source/unstable/libhinawa
> Now I'm preparing for 'needs-packaging' request [3] to Ubuntu project.
> We have 10 days to FeatureFreeze[4] for Ubuntu 16.04 (Xenyal Xerus)[5].
In Ubuntu project, AutoSync bot imported it and the package is now
available.
https://launchpad.net/ubuntu/+source/libhinawa
Thanks for all ;)
>>> I with the package will be available as early as possible, and this work
>>> will be a part of his great work as a debian package maintainer.
>>>
>>> FYI,
>>>
>>> [0] ITP = Intent To Packaging
>>> [1] Debian -- Details of package groonga in sid:
>>> https://packages.debian.org/sid/groonga
>>> [2] Debian Bug report logs - #732055
>>> ITP: groonga -- Fulltext search engine
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732055
>
> [3] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
> [4] https://wiki.ubuntu.com/FeatureFreeze
> [5] https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule
Takashi Sakamoto
prev parent reply other threads:[~2016-02-07 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 11:27 The location of libhinawa and hinawa-utils for FireWire sound devices ? Takashi Sakamoto
2016-01-31 11:44 ` Meaning of the name 'hinawa' and the intension Takashi Sakamoto
2016-01-31 11:45 ` About planning of libhinawa ITP to debian project Takashi Sakamoto
2016-01-31 11:50 ` Takashi Sakamoto
2016-02-02 14:04 ` Takashi Sakamoto
2016-02-07 3:10 ` Takashi Sakamoto
2016-02-07 13:10 ` Takashi Sakamoto [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56B74241.6040803@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ffado-devel@lists.sf.net \
--cc=hayashi@clear-code.com \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox