public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Source for perl-URI-Encode is missing
Date: Sat, 18 Jun 2022 09:22:04 +0000	[thread overview]
Message-ID: <4978b8ce-6667-684b-5ba8-2e122c4821d3@ipfire.org> (raw)
In-Reply-To: <7878c39e-501b-ec6d-6ab9-716cd17bf52c@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

Hello Matthias,

thanks for your reply and resolving this. :-)

Ah, of course - I thought the primary source was GitHub, but for Perl, its CPAN.

Thanks, and best regards,
Peter Müller


> Hi,
> 
> I think I can help here:
> 
> Website:
> https://metacpan.org/dist/URI-Encode
> 
> https://cpan.metacpan.org/authors/id/M/MI/MITHUN/URI-Encode-v1.1.1.tar.gz
> 
> Checksum matches.
> 
> HTH,
> Matthias
> 
>  On 18.06.2022 10:05, Peter Müller wrote:
>> Hello Timo,
>>
>> I am sorry to inform you that the source tarball for perl-URI-Encode, a new package
>> included with the OpenVPN 2FA conglomerate, is missing.
>>
>> As I was unable to find any source tarball online with the same checksum, please
>>
>> (a) upload the source tarball to source.ipfire.org and
>> (b) drop me a line on where you got that tarball from - I will then include the URL in
>>     the LFS file, so this is somewhat documented.
>>
>> Kindly do so soon, as we are about to close Core Update 169 and the missing source
>> currently breaks the build on all architectures.
>>
>> Thanks, and best regards,
>> Peter Müller
> 

      reply	other threads:[~2022-06-18  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18  8:05 Peter Müller
2022-06-18  9:17 ` Matthias Fischer
2022-06-18  9:22   ` Peter Müller [this message]

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=4978b8ce-6667-684b-5ba8-2e122c4821d3@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.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