From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v12 1/1] squeezelite: new package
Date: Fri, 25 Sep 2015 15:22:53 +0100 [thread overview]
Message-ID: <560558BD.1030905@imgtec.com> (raw)
In-Reply-To: <560557BB.6080800@imgtec.com>
Hi everyone,
On 09/25/2015 03:18 PM, Vicente Olivert Riera wrote:
> Hi Thomas,
>
> On 09/25/2015 03:14 PM, Thomas Petazzoni wrote:
>> Hello,
>>
>> On Fri, 25 Sep 2015 10:12:58 +0100, Vicente Olivert Riera wrote:
>>
>>>>>>>> squeezelite v1.8 Downloading
>>>>> Doing shallow clone
>>>>> Initialized empty Git repository in
>>>>> /br/output/build/.squeezelite-v1.8.tar.gz.pb3XtQ/squeezelite-v1.8/
>>>>> remote: Counting objects: 82, done.
>>>>> Unpacking objects: 100% (82/82), done.
>>>>> warning: Remote branch v1.8 not found in upstream origin, using HEAD instead
>>>>> fatal: unable to read tree 668edec073bef579bedf43817f65aee3a592d0ef
>>>> Hmm...
>>>> I have been working on my cached source, so I did not realize it.
>>>> Yes, I can reproduce your problem with real clean buildroot tree.
>>>> Maybe something changed https://code.google.com/p/squeezelite repo
>>>> since my last fetch.
>>>> I'm considering to change SQUEEZELITE_SITE to github repo like:
>>>> https://github.com/sixeyed/squeezelite
>>>> Does this repo work for you too ?
>>>
>>> the fact that it works or not is not the problem. The problem is that
>>> right now there isn't any official repository for that project, so that
>>> repository could disappear tomorrow. And I don't know if the owner of
>>> that repository has made any change to the source code or not.
>>>
>>> Perhaps downloading the tarballs from Google Code and putting them in
>>> mirror.buildroot.org would be the best option. I have added Peter and
>>> Thomas on CC so they can tell their opinion about this issue.
>>
>> What do you want to do this instead of just using the Google Code
>> tarballs? Yes, I know Google Code will disappear in the future, but
>> right now, it works, and by the time it will be shut down, hopefully
>> this project will have found a new hosting.
>
> Because I don't see any tarball in Google Code which contains the
> sources. All I see are binary builds:
>
> https://code.google.com/p/squeezelite/downloads/list?can=1&q=
anyway, I think the git repo on Google Code started working again:
$ git clone https://code.google.com/p/squeezelite/
Initialized empty Git repository in /git-clones/squeezelite/.git/
remote: Counting objects: 845, done.
Receiving objects: 100% (845/845), 286.68 KiB, done.
Resolving deltas: 100% (570/570), done.
$
Regards,
Vincent.
> Regards,
>
> Vincent.
>
>>
>> Thomas
>>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2015-09-25 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 13:32 [Buildroot] [PATCH v12 1/1] squeezelite: new package kei-k at ca2.so-net.ne.jp
2015-09-24 14:28 ` Vicente Olivert Riera
2015-09-24 14:34 ` Vicente Olivert Riera
2015-09-25 3:04 ` kei-k at ca2.so-net.ne.jp
2015-09-25 9:12 ` Vicente Olivert Riera
2015-09-25 9:28 ` 川島 浩
2015-09-25 15:07 ` kei
2015-09-25 15:11 ` kei
2015-09-26 11:15 ` 川島 浩
2015-09-25 13:52 ` kei
2015-09-25 14:14 ` Thomas Petazzoni
2015-09-25 14:18 ` Vicente Olivert Riera
2015-09-25 14:22 ` Vicente Olivert Riera [this message]
2015-09-25 15:04 ` kei
2015-09-25 15:34 ` kei
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=560558BD.1030905@imgtec.com \
--to=vincent.riera@imgtec.com \
--cc=buildroot@busybox.net \
/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