libcue source tarball not bootstrapped

  • Done
  • quality assurance status badge
Details
3 participants
  • Andreas Enge
  • Leo Famulari
  • Ludovic Courtès
Owner
unassigned
Submitted by
Leo Famulari
Severity
normal
L
L
Leo Famulari wrote on 24 Dec 2015 18:34
(address . bug-guix@gnu.org)
20151224173450.GA19828@jasmine
Hi,

Can someone recommend a "template" email I can send to upstream
developers requesting that they bootstrap their release tarballs?

libcue recently moved from sourceforge to github and it seems that they
have forgotten to bootstrap the new tarballs. I'm not familiar enough
with the Autotools system to know what to ask them to do.
A
A
Andreas Enge wrote on 27 Dec 2015 14:09
(name . Leo Famulari)(address . leo@famulari.name)(address . 22232@debbugs.gnu.org)
20151227130946.GA14648@debian.fritz.box
On Thu, Dec 24, 2015 at 12:34:50PM -0500, Leo Famulari wrote:
Toggle quote (3 lines)
> Can someone recommend a "template" email I can send to upstream
> developers requesting that they bootstrap their release tarballs?

Here is what I sent recently to the numactl list:

Andreas
L
L
Leo Famulari wrote on 27 Dec 2015 15:45
(name . Andreas Enge)(address . andreas@enge.fr)(address . 22232@debbugs.gnu.org)
20151227144511.GA370@jasmine
On Sun, Dec 27, 2015 at 02:09:46PM +0100, Andreas Enge wrote:
Toggle quote (7 lines)
> On Thu, Dec 24, 2015 at 12:34:50PM -0500, Leo Famulari wrote:
> > Can someone recommend a "template" email I can send to upstream
> > developers requesting that they bootstrap their release tarballs?
>
> Here is what I sent recently to the numactl list:
> http://article.gmane.org/gmane.linux.kernel.numa/951

Thank you! This is exactly the email I was looking for. I will adapt it
as necessary.

Toggle quote (3 lines)
>
> Andreas
>
L
L
Ludovic Courtès wrote on 29 Dec 2015 00:20
(name . Leo Famulari)(address . leo@famulari.name)
87lh8e9n3i.fsf@gnu.org
Leo Famulari <leo@famulari.name> skribis:

Toggle quote (11 lines)
> On Sun, Dec 27, 2015 at 02:09:46PM +0100, Andreas Enge wrote:
>> On Thu, Dec 24, 2015 at 12:34:50PM -0500, Leo Famulari wrote:
>> > Can someone recommend a "template" email I can send to upstream
>> > developers requesting that they bootstrap their release tarballs?
>>
>> Here is what I sent recently to the numactl list:
>> http://article.gmane.org/gmane.linux.kernel.numa/951
>
> Thank you! This is exactly the email I was looking for. I will adapt it
> as necessary.

It might also be useful to point them at

Ludo’.
L
L
Leo Famulari wrote on 29 Dec 2015 02:36
(name . Ludovic Courtès)(address . ludo@gnu.org)
20151229013621.GA15460@jasmine
On Tue, Dec 29, 2015 at 12:20:49AM +0100, Ludovic Court�s wrote:
Toggle quote (16 lines)
> Leo Famulari <leo@famulari.name> skribis:
>
> > On Sun, Dec 27, 2015 at 02:09:46PM +0100, Andreas Enge wrote:
> >> On Thu, Dec 24, 2015 at 12:34:50PM -0500, Leo Famulari wrote:
> >> > Can someone recommend a "template" email I can send to upstream
> >> > developers requesting that they bootstrap their release tarballs?
> >>
> >> Here is what I sent recently to the numactl list:
> >> http://article.gmane.org/gmane.linux.kernel.numa/951
> >
> > Thank you! This is exactly the email I was looking for. I will adapt it
> > as necessary.
>
> It might also be useful to point them at
> <http://www.gnu.org/software/automake/manual/html_node/Basics-of-Distribution.html>.

It looks like upstream is preparing a new release that switches from
Autotools to CMake. I'll just wait for that. We can close this bug.
L
L
Ludovic Courtès wrote on 2 Jan 2016 21:47
control message for bug #22232
(address . control@debbugs.gnu.org)
877fjrzp2t.fsf@gnu.org
tags 22232 notabug
L
L
Ludovic Courtès wrote on 2 Jan 2016 21:47
(address . control@debbugs.gnu.org)
8760zbzp2k.fsf@gnu.org
close 22232 0.9.0+
?
Your comment

This issue is archived.

To comment on this conversation send an email to 22232@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 22232
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch