From: Bryan Hundven <bryanhundven@gmail.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "andrew@ncrmnt.org" <andrew@ncrmnt.org>,
"crossgcc@sourceware.org" <crossgcc@sourceware.org>,
John Collis <John.Collis@alliedtelesis.co.nz>
Subject: Re: crosstool-NG Debian packaging
Date: Tue, 23 Feb 2016 04:37:00 -0000 [thread overview]
Message-ID: <5872238A-E588-4849-89DC-9B3A11CA801A@gmail.com> (raw)
In-Reply-To: <087085f5ddaf4f16ac4de0981719ae43@svr-chch-ex1.atlnz.lc>
[-- Attachment #1: Type: text/plain, Size: 2445 bytes --]
Chris,
> On Feb 22, 2016, at 7:55 PM, Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
>
> On 02/11/2016 10:43 AM, andrew@ncrmnt.org wrote:
>> 10 февраля 2016 г., 23:32, "Chris Packham" <Chris.Packham@alliedtelesis.co.nz> написал:
>>> Hi Bryan, Andrew,
>>>
>>> I see that there is some movement on packaging crosstool-NG for Debian.
>>> This is relevant to my interests and I have subscribed to your mailing
>>> list :).
>>>
>>> Is there an open Debian bug for this? I've found a few older ones but
>>> they all seem to have timed out due to lack of interest.
>>
>> Hi, Chris. Unfortunately, I'm not a debian maintainer and there's no open bug
>> for that in debian bugtracker. I've done the packaging for my own needs,
>> since it was waaay faster than opening a bug ;). So unless you know some debian
>> maintainers crosstool-ng won't land in debian repositories any time soon;)
>>
>
> So in a fit of optimism I thought I'd give submission to debian a go.
> Based on Andrew's work I've got packaging for the released 1.22.0 with
> some patches I need for my own selfish needs.
>
> Andrew are you happy to be listed in the debian/control as the
> maintainer or do you want me to put my name in there instead (or should
> I put Bryan).
I would say that Andrew is the one who submitted the debian/ directory. I already maintain the source, and I don’t always use any specific GNU/Linux distribution at any one time. (Although a long time debian user! ;) ) I’d rather keep a un-biased mindset about crosstool-ng, distribution wise, as some of what I work on is not for GNU/Linux at all (*BSD support, Mac OS X support, etc…)
> I also notice that the tarball from github[1] has some unfortunate paths
> in it, "crosstool-ng-crosstool-ng-1.22.0" which makes packaging it a bit
> of a pain (1.21.0 also seems to have the same issue).
You found the problem, you provide a patch. I have a ton of issues on my plate, and rarely still does anyone ever get around to reviewing my changes, even when I ask for it!
> Is there any way we can get that fixed? I have re-generated the tarball
> locally but if someone were to compare the md5sum of my tarball to the
> one from github they might think something malicious was going on.
>
> Thanks,
> Chris
> --
> [1] -
> https://github.com/crosstool-ng/crosstool-ng/archive/crosstool-ng-1.22.0.tar.gz
Cheers,
-Bryan
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2016-02-23 4:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 20:32 Chris Packham
2016-02-10 20:41 ` Bryan Hundven
2016-02-10 20:49 ` Chris Packham
2016-02-10 20:52 ` Bryan Hundven
2016-02-10 21:05 ` Chris Packham
2016-02-10 21:43 ` andrew
2016-02-23 3:55 ` Chris Packham
2016-02-23 4:37 ` Bryan Hundven [this message]
2016-02-23 4:40 ` Bryan Hundven
2016-02-23 21:15 ` Chris Packham
2016-02-23 13:05 ` Thomas Petazzoni
2016-02-23 15:41 ` Bryan Hundven
2016-02-23 21:26 ` Github tags (was Re: crosstool-NG Debian packaging) Chris Packham
2016-02-12 4:20 ` crosstool-NG Debian packaging Chris Packham
2016-02-12 19:49 ` Bryan Hundven
2016-02-14 19:42 ` Chris Packham
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=5872238A-E588-4849-89DC-9B3A11CA801A@gmail.com \
--to=bryanhundven@gmail.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=John.Collis@alliedtelesis.co.nz \
--cc=andrew@ncrmnt.org \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).