Michael,
On 20/06/16 00:16, Michael Hudson-Doyle wrote:
> I suppose Built-Using on a -dev package lists source package versions
> that the -dev package is known to build/pass tests with, which is
> probably useful information. But it's not the information for which
> policy says Built-Using is to
Dmitry,
On 20/06/16 05:11, Dmitry Smirnov wrote:
> I think your procedure could be improved if "git merge upstream/2.1"
> is modified with "--squash" to produce one neat merge commit to "master"
> instead of flood of upstream commits that make it difficult to identify
> packaging-related commit
FYI: The status of the golang-github-kolo-xmlrpc source package
in Debian's testing distribution has changed.
Previous version: 0+git20150413.0826b98-1
Current version: 0+git20150413.0826b98-2
--
This email is automatically generated once a day. As the installation of
new packages into tes
FYI: The status of the dh-golang source package
in Debian's testing distribution has changed.
Previous version: 1.17
Current version: 1.18
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
lat
On 21 June 2016 at 17:57, Dmitry Smirnov wrote:
> On Tuesday, 21 June 2016 5:02:19 PM AEST Michael Hudson-Doyle wrote:
>> Currently in sid golang-github-coreos-pkg and
>> golang-github-coreos-go-systemd Build-Depend on each other. This is an
>> accurate reflection of the upstream situation
>> (git
On Monday 20 June 2016, at 21:05 +0200, Geert Stappers wrote:
> > The current description reads:
> > This is easily the library managing with JSON format. This can be
> > done easily the acquisition of reading and the value of the JSON
> > format. And this is add or remove key, and provides conv
