[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#822360: marked as done (RFS: sequitur-g2p/0.0.r1668-3 -- Grapheme to Phoneme conversion tool)

Your message dated Sun, 24 Apr 2016 12:14:18 +0200
with message-id <CA+zRt5FLDVKAy7eSLWSVkq13n2qEGfdJfYSkPrWiTybR_O8qDg@mail.gmail.com>
and subject line Re: Bug#822360: RFS: sequitur-g2p/0.0.r1668-3 -- Grapheme to Phoneme conversion tool
has caused the Debian Bug report #822360,
regarding RFS: sequitur-g2p/0.0.r1668-3 -- Grapheme to Phoneme conversion tool
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
822360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822360
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: Jakub Wilk <jwilk@debian.org>

Dear Jakub,

I am looking for a sponsor for an updated version of my package "sequitur-g2p"

 * Package name    : sequitur-g2p
   Version         : 0.0.r1668-3
   Upstream Author : Maximilian Bisani <bisani@informatik.rwth-aachen.de>
 * URL             : http://www-i6.informatik.rwth-aachen.de/web/Software/g2p.html
 * License         : GPL-2
   Section         : science

It builds those binary packages:

   sequitur-g2p - Grapheme to Phoneme conversion tool


You can download the package with git using this command:

   git clone git://anonscm.debian.org/collab-maint/sequitur-g2p.git

More information about sequitur-g2p can be obtained from http://www-i6.informatik.rwth-aachen.de/web/Software/g2p.html.

Would you like to review and upload it?

Regards,
 Giulio

--- End Message ---
--- Begin Message ---

Il 24/apr/2016 11:59, "Christian Kastner" <ckk@debian.org> ha scritto:
>
> On 2016-04-24 01:30, Giulio Paci wrote:
> >> What update was that? From the other commits, I can deduce that this was
> >> merely a refreshing of d/control from d/control.in, and the actual
> >> changes -- namely bumping Standards-Version, and updating Vcs-* --
> >> happened earlier. This was a bit confusing, so being explicit about this
> >> could be helpful.
> >
> > You are perfectly right.
> > I think "Refreshed" is a much better word in this case, so I will use this word in future.
>
> In hindsight, something like "Regenerated X from X.in" might be even
> better -- that would make it even clearer from the subject that this
> commit can probably be ignored.

I perfectly agree, so I think I will use this formula. Thank you for it.
Indeed I just drop it from the changelog. I mostly use it as a marker of the fact that I think that there are no issues with control file anymore.
In the same way I tend to use changelog updates as a marker of the fact that I completed some work on the package.

> And just for comparison, here's another approach: the Nautilus team
> seems to be doing it by committing both changes at the same time, and
> also adding a warning header to the generated file:
>
>   https://anonscm.debian.org/viewvc/pkg-gnome?view=revision&revision=48120
>   http://sources.debian.net/src/nautilus/3.20.0-1/debian/control/

I think I should take from here at least the idea of the warning header from here. Although, probably, the best option is to change cdbs so that this will automatically happen for all automatically generated files.
@Jonas: what do you think?

> >>   * d/patches:
> >>     - Please consider making the headers DEP3-compliant (although it's
> >>       not a "hard" requirement): http://dep.debian.net/deps/dep3/
> >
> > Can you point me to what the current headers are missing in order to be DEP3-compliant?
> > Did I miss some mandatory field?
>
> Please disregard my comment. I thought DEP3 headers had to be terminated
> with an empty line, but I was mistaken.

No problem. :-)

> >> Your package built cleanly and without lintian errors or warnings, so as
> >> soon as you address the above issues, I'd be ready to upload.
> >
> > I just pushed the changes to the repository.
>
> Built, signed, and uploaded.
>
> Thank you for your contribution!

And thank you for sponsoring it. :-)


--- End Message ---
Reply to: