Re: Problems: Stability: 1.4.0

On Wed, Feb 4, 2009 at 11:30 AM, Chris Giles <[email protected]> wrote:

> I just retested this issue and figured out its cause.  Dependency checking
> and retrieving works fine with AP v1.4.0 when my spec file has the following
> line:
>
>    - AutopackageTarget: 1.2.6
>
> However, dependencies aren't even tested if my spec file has either of the
> following lines:
>
>    - AutopackageTarget: 1.4
>    - AutopackageTarget: 1.4.0
>
> I'm guessing that this problem should be relatively easy to fix.


You're right, it was pretty easy to fix. Thank you so much for finding this.
I don't know why I haven't noticed it. It was caused by using the wrong
variable and I fixed it in revision 2543:
http://trac.autopackage.org/changeset/2543


> apkg-bashlib: line 595: echo: write error: Broken pipe
>>>
>>
>> Don't know what causes this, happens quite often for me, too.
>
> When creating my packages, I receive the following non-fatal warnings:
>
> This problem seems to have magically disappeared today, but I wonder if
> anyone knows the cause and resolution.  Just in case it resurfaces, perhaps
> we should create a bug ticket with a low priority.
>

I think Eugene is right, this is related to #43.

cp: cannot stat `/usr/libexec/autopackage/autopackage-curl': No such file or
>> directory
>>
>
> Strange, this shouldn't happen. Are you sure that you installed the
> Autopackage Development Environment 1.4.0 and not 1.2.5?


> Yeah, AP v1.4.0 was installed since the problem doesn't exist with v1.2.6.
> Do we know why this file is missing?
>

Ah, I just found out. I missed to add it to the makefile which installs the
development files. Also fixed in r2543.


> Since both of my Linux applications are written in Python-Qt4, perhaps I'm
> the logical guy to takeover the development of the AP-Qt front-end.  I hate
> programming in C++, but I'll take a look at the AP-Qt code when I get some
> free time.  My first two goals would be to: upgrade the code from Qt3 to
> Qt4, if necessary; port the recent AP-GTK changes across to AP-Qt.
>

Great! But before you upgrade the code from Qt3 to Qt4 wait till I posted
some news about my plans for Autopackage >=1.5. It contains some major
changes which should make it possible for you to program in python-qt4.

For now we should concentrate on getting the Qt3 front-end to work. Do you
think it would be okay if we release 1.4.0 without the Qt3 front-end and add
it later on?

I will build Autopackage again in the next days and fix a last bug I've
found (package can't be found after installing the support code).
Unfortunately I'm in my last year of school and most of the time busy
studying.