Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [psa] various server software upgrades
Date: Wed, 02 Dec 2015 09:43:35 +0100	[thread overview]
Message-ID: <874mg1i6ko.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAKAx1chQju2g1-wf6PDEeiQ0D1KJPfar9Js2z7oWdu8ejZSqLg@mail.gmail.com> (Lionel Orry's message of "Wed, 2 Dec 2015 08:58:56 +0100")

>>>>> "Lionel" == Lionel Orry <lionel.orry@gmail.com> writes:

Hi,

 > Hi,
 > On Wed, Dec 2, 2015 at 8:35 AM, Mike Frysinger <vapier@gentoo.org> wrote:

 >> the busybox.net software has been languishing for quite a long time,
 >> so i gave it a strong kick today.  just about every piece of software
 >> has been upgraded on the box including bugzilla.  my various testing
 >> looks like it still works, but if you guys notice anything weird, feel
 >> free to let me know.
 >> -mike

Thanks for doing the update Mike! We had some issues with old (dsa) ssh
keys, but that is fixed now.

 > ?Thank you for that. I don't know if it's related but the "Recent commits"
 > and "Recent discussions" streams normally displayed on?

 > ?the buildroot homepage are empty...

I don't think this is related. Looking closer, it seems like the Google
API the website used is no longer available :/

E.G.:

https://www.google.com/uds/Gfeeds?callback=google.feeds.Feed.RawCompletion&context=0&num=30&hl=en&output=json&q=http%3A%2F%2Frss.gmane.org%2Ftopics%2Fexcerpts%2Fgmane.comp.lib.uclibc.buildroot&key=notsupplied&v=1.0&nocache=1449045352617

Returns:

/* callback */google.feeds.Feed.RawCompletion('0', null, 403, 'This API is no longer available.', 200)

The API page (https://developers.google.com/feed/) says:

This API is officially deprecated. See our deprecation policy in our
Terms of Service for details.

Angelo, any idea how to fix this? Googling around I see:

http://blog.superfeedr.com/google-feed-api-alternative/

But ideally we shouldn't depend on any extra external API for this.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2015-12-02  8:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02  7:35 [Buildroot] [psa] various server software upgrades Mike Frysinger
2015-12-02  7:58 ` Lionel Orry
2015-12-02  8:43   ` Peter Korsgaard [this message]
2015-12-02  9:25 ` Nikolay Dimitrov
2015-12-02  9:28   ` Nikolay Dimitrov
2015-12-02 17:31   ` Mike Frysinger
2015-12-02 18:38     ` Nikolay Dimitrov
2015-12-06 21:42 ` Yann E. MORIN
2015-12-06 22:00   ` Peter Korsgaard
2015-12-07  1:55     ` Mike Frysinger
2015-12-07  6:34       ` Peter Korsgaard
2015-12-07 18:51         ` Mike Frysinger
2015-12-07 20:37           ` Peter Korsgaard
2015-12-07 21:55             ` Mike Frysinger
2015-12-07 22:16               ` Peter Korsgaard
2015-12-07 22:54                 ` Mike Frysinger
2015-12-07 23:02                   ` Yann E. MORIN
2015-12-07 23:22                     ` Mike Frysinger
2015-12-08  7:52                       ` Peter Korsgaard
2015-12-08 16:40                         ` Mike Frysinger
2015-12-08 16:43                           ` Peter Korsgaard
2015-12-08 17:27                             ` Mike Frysinger
2015-12-08  7:50                   ` Peter Korsgaard
2015-12-08  0:17                 ` Mike Frysinger
2015-12-08  7:55                   ` Peter Korsgaard
2015-12-08 16:38                     ` Mike Frysinger
2015-12-07  8:00       ` Peter Korsgaard
2015-12-07  8:23         ` Peter Korsgaard
2015-12-07 18:52         ` Mike Frysinger
2015-12-07 19:57           ` Mike Frysinger
2015-12-07 19:59             ` Yann E. MORIN
2015-12-07 23:52               ` Mike Frysinger
2015-12-07 20:42           ` Peter Korsgaard

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=874mg1i6ko.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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