From: Paul Simmons <mbatranch@gmail.com>
To: development@lists.ipfire.org
Subject: Re: Core 135 ISO
Date: Tue, 20 Aug 2019 13:42:21 -0500 [thread overview]
Message-ID: <add6dc7d-1404-a6ff-82c8-3f2c729b85b0@gmail.com> (raw)
In-Reply-To: <CA743D9A-607D-4A06-B400-406862C89B3F@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
On 8/20/19 1:09 PM, Michael Tremer wrote:
> Hello guys,
>
> I thought that we won’t really need the builds from master.
>
> But I enabled them now and they should show up in a couple of hours.
>
> Best,
> -Michael
>
>> On 20 Aug 2019, at 05:45, Kienker, Fred <fkienker(a)at4b.com> wrote:
>>
>> Yes, it was, and it is not there now. Perhaps it has been moved to a new location or not currently available?
>>
>> Best regards,
>> Fred
>>
>> From: Paul Simmons <mbatranch(a)gmail.com>
>> Sent: 19 August, 2019 19:22
>> To: development(a)lists.ipfire.org
>> Subject: Re: Core 135 ISO
>>
>> On 8/19/19 2:14 PM, Kienker, Fred wrote:
>> We experienced a few installation issues with C133 and C134 x86-64 ISO’s. I would like to download a C135 x86-64 ISO for testing purposes. Can anyone provide a link to the ISO?
>> Best regards,
>> Fred Kienker
>> It used to be at https://nightly.ipfire.org/master/latest/x86_64/ before the data center move...
>>
>> --
>> Pardon me for a moment, my blood alcohol level is too low.
>
Thank you! That makes my (testing) life easier.
Paul
--
Do not meddle in the affairs of politicians, for they are petty and full of malice.
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1761 bytes --]
prev parent reply other threads:[~2019-08-20 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <H000006e00519ef4.1566276341.mail.at4b.net@MHS>
2019-08-20 18:09 ` Michael Tremer
2019-08-20 18:42 ` Paul Simmons [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=add6dc7d-1404-a6ff-82c8-3f2c729b85b0@gmail.com \
--to=mbatranch@gmail.com \
--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