mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: <jon.bird@gd-ms.uk>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] dependencies not working in ptxdist-2017.01.0
Date: Thu, 9 Mar 2017 14:15:09 +0000	[thread overview]
Message-ID: <94D4A88F8AC34646A5288D11318F5D5B0D9E7106@GDUKADH841.uk1.r-org.net> (raw)
In-Reply-To: <20170308094653.nmoutv7khi7gcbru@pengutronix.de>

On 2017-03-08, Michael Olbrich wrote:

> Hi,
> 
> On Wed, Mar 01, 2017 at 11:31:13AM +0000, jon.bird@gd-ms.uk wrote:
>> On 2017-02-27, jon.bird@gd-ms.uk wrote:
>>> I'm attempting to perform an update from a project based around
>>> ptxdist-
>>> 2012.12.1 to the latest (2017.01.0) and am encountering a problem
>>> with package dependencies.
>>> 
>> [...]
>> 
>> Some further info on this, I've wound back through some older
>> versions of ptxdist releases and my initial testing shows that it
>> seems to be ok in
>> 2016.04.0 (in that for the specific package I mentioned it seems to
>> go off and start downloading the required packages) however from
>> 2016.05.1 it does not.
> 
> How did you test this? With PTXdist git? If yes, did you ran 'make' in
> ptxdist after checking out a new tag?
> 
> Michael
>

No, I just downloaded an assortment of the older versions, did the usual make/install and retried the build (reverting my project back to the 2012 settings each time) till I found a version that worked. It was purely a process of trial/error then attempt to narrow it down to the newest version I could use which didn't exhibit this problem.

Getting access to git servers is somewhat painful given the firewall here....

Rgs,


Jon.

--
Jon Bird, CEng MBCS
Software Engineer
Electronic Systems
General Dynamics United Kingdom Ltd.
Castleham Road, St Leonards on Sea, East Sussex, TN38 9NJ

Telephone: +441424798278
Email: jon.bird@gd-ms.uk
Website: www.generaldynamics.uk.com      


------------------------------------------------------------------------------

This email and any files attached are intended for the addressee and may contain information of a confidential nature. If you are not the intended recipient, be aware that this email was sent to you in error and you should not disclose, distribute, print, copy or make other use of this email or its attachments. Such actions, in fact, may be unlawful. In compliance with the various Regulations and Acts, General Dynamics United Kingdom Limited reserves the right to monitor (and examine for viruses) all emails and email attachments, both inbound and outbound. Email communications and their attachments may not be secure or error- or virus-free and the company does not accept liability or responsibility for such matters or the consequences thereof. General Dynamics United Kingdom Limited, Registered Office: 21 Holborn Viaduct, London EC1A 2DY. Registered in England and Wales No: 1911653.
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2017-03-09 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27  9:42 jon.bird
2017-03-01 11:31 ` jon.bird
2017-03-08  9:46   ` Michael Olbrich
2017-03-09 14:15     ` jon.bird [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=94D4A88F8AC34646A5288D11318F5D5B0D9E7106@GDUKADH841.uk1.r-org.net \
    --to=jon.bird@gd-ms.uk \
    --cc=ptxdist@pengutronix.de \
    /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