public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] wget
Date: Wed, 18 Nov 2020 15:23:13 +0100	[thread overview]
Message-ID: <87h7pmrbfy.fsf@Otto.invalid> (raw)
In-Reply-To: <87a6vfu7dw.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 17 Nov 2020 20:10:19 +0100")

Achim Gratz writes:
> Brian Inglis writes:
>> I dug up some Debian, Fedora, and OpenSuSE patches, and added them to the cygport.
>> OpenSuSE patches appear only to be available in their source package,
>> or online in their HTML page, for which I came up with a script to
>> grab a package's patch URLs, scrape those web pages for the patch
>> source, and convert from HTML to patch text. Do you know if there is
>> any way to access OBS patches as plain text?
>
> Nothing that I've used before, but it wouldn't hurt to ask.  There
> obviously is some sort of an API that the osc CLI is using (I don't know
> any details of that either), but how far that extends to plain HTTPS
> REST requests I don't know.

As I suspected, that problem isn't exactly new and one solution is this
Git repo that mirrors OBS:

https://github.com/bmwiedemann/openSUSE

It covers openSUSE Factory/Tumbleweed only, but that should suffice for
your purposes.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

  parent reply	other threads:[~2020-11-18 14:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 20:05 [ITP] wget2 - modern fast parallel file and recursive website downloader Brian Inglis
2020-07-08 20:28 ` Brian Inglis
2020-07-09 18:27   ` Marco Atzeri
2020-07-09 18:50     ` Yaakov Selkowitz
2020-07-10  1:38       ` Brian Inglis
2020-07-10  5:27         ` Marco Atzeri
2020-10-30 21:30           ` Brian Inglis
2020-10-30 21:34             ` Eric Blake
2020-10-30 21:57               ` [ITA] wget Brian Inglis
2020-10-31 12:50                 ` Marco Atzeri
2020-11-14 15:19                 ` Achim Gratz
2020-11-14 22:15                   ` Brian Inglis
2020-11-15  7:36                     ` ASSI
2020-11-15 17:32                       ` Brian Inglis
2020-11-16 17:23                         ` Achim Gratz
2020-11-16 21:35                           ` Brian Inglis
2020-11-17 19:10                             ` Achim Gratz
2020-11-17 23:23                               ` Brian Inglis
2020-11-18 14:23                               ` ASSI [this message]
2020-11-10  5:29           ` [ITP] wget2 - please review if anyone has time Brian Inglis
2020-11-24 21:06           ` [ITP] wget2 Brian Inglis
2020-11-27 17:57             ` Hamish McIntyre-Bhatty
2020-11-27 18:28               ` Brian Inglis
2020-11-30 14:51                 ` Hamish McIntyre-Bhatty
2020-11-30 18:29                   ` Achim Gratz

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=87h7pmrbfy.fsf@Otto.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.com \
    /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).