Mailing List Archive: Maemo: Developers

Autobuilder problem with optified library

Index | Next | Previous | View Threaded

julle.luukko at quicknet

Oct 19, 2009, 11:46 AM

Post #1 of 10 (437 views)
Permalink

Autobuilder problem with optified library

Hello all,

I tried to build my application, fuelpad, with Fremantle autobuilder but
got an error in setting up the build system setup [1]. The relevant
lines in the log are:

Selecting previously deselected package libgtkextra-x11-2.0-1.
Unpacking libgtkextra-x11-2.0-1 (from
.../libgtkextra-x11-2.0-1_2.1.1-3.1maemo4_armel.deb) ...
dpkg: error processing
/var/cache/apt/archives/libgtkextra-x11-2.0-1_2.1.1-3.1maemo4_armel.deb
(--unpack):
trying to overwrite `/opt', which is also in package base-files
dpkg-deb: subprocess paste killed by signal (Broken pipe)

libgtkextra-x11-2.0 is almost directly from debian except for the
optification. It built fine in autobuilder and it is now in extras-devel
[2]. I believe that no other package is using it, at least that was the
case with diablo and chinook.

Needless to say, everything builds and install fine in scratchbox. Does
anybody have any clue what is wrong?

Regards,

Julius

[1]
https://garage.maemo.org/builder/fremantle/fuelpad_0.82-fremantle1/armel.root.log.FAILED.txt
[2]
http://maemo.org/packages/view/libgtkextra-x11-2.0-1
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

corsac at debian

Oct 19, 2009, 12:00 PM

Post #2 of 10 (415 views)
Permalink

Re: Autobuilder problem with optified library [In reply to]

On lun., 2009-10-19 at 21:46 +0300, Julius Luukko wrote:
> Selecting previously deselected package libgtkextra-x11-2.0-1.
> Unpacking libgtkextra-x11-2.0-1 (from
> .../libgtkextra-x11-2.0-1_2.1.1-3.1maemo4_armel.deb) ...
> dpkg: error processing
> /var/cache/apt/archives/libgtkextra-x11-2.0-1_2.1.1-3.1maemo4_armel.deb
> (--unpack):
> trying to overwrite `/opt', which is also in package base-files
> dpkg-deb: subprocess paste killed by signal (Broken pipe)
>
> libgtkextra-x11-2.0 is almost directly from debian except for the
> optification. It built fine in autobuilder and it is now in
> extras-devel
> [2]. I believe that no other package is using it, at least that was
> the
> case with diablo and chinook.

Just wondering if in one of these packages the /opt is a symlink and on
the other a real folder?

Cheers,
--
Yves-Alexis

Attachments:

signature.asc (0.19 KB)

bundyo at gmail

Oct 19, 2009, 12:26 PM

Post #3 of 10 (415 views)
Permalink

Re: Autobuilder problem with optified library [In reply to]

Well, on the device and probably in autobuilder the /opt folder is actually
a symlink to /home/opt... On the other hand maemo-optify produces direct
/opt folder.

Regards:
Bundyo

On Mon, Oct 19, 2009 at 10:00 PM, Yves-Alexis Perez <corsac [at] debian>wrote:

> On lun., 2009-10-19 at 21:46 +0300, Julius Luukko wrote:
> > Selecting previously deselected package libgtkextra-x11-2.0-1.
> > Unpacking libgtkextra-x11-2.0-1 (from
> > .../libgtkextra-x11-2.0-1_2.1.1-3.1maemo4_armel.deb) ...
> > dpkg: error processing
> > /var/cache/apt/archives/libgtkextra-x11-2.0-1_2.1.1-3.1maemo4_armel.deb
> > (--unpack):
> > trying to overwrite `/opt', which is also in package base-files
> > dpkg-deb: subprocess paste killed by signal (Broken pipe)
> >
> > libgtkextra-x11-2.0 is almost directly from debian except for the
> > optification. It built fine in autobuilder and it is now in
> > extras-devel
> > [2]. I believe that no other package is using it, at least that was
> > the
> > case with diablo and chinook.
>
> Just wondering if in one of these packages the /opt is a symlink and on
> the other a real folder?
>
> Cheers,
> --
> Yves-Alexis
>
> _______________________________________________
> maemo-developers mailing list
> maemo-developers [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>
>

corsac at debian

Oct 19, 2009, 1:01 PM

Post #4 of 10 (413 views)
Permalink

Re: Autobuilder problem with optified library [In reply to]

On lun., 2009-10-19 at 22:26 +0300, Kamen Bundev wrote:
> Well, on the device and probably in autobuilder the /opt folder is
> actually a symlink to /home/opt... On the other hand maemo-optify
> produces direct /opt folder.

That's the problem, dpkg won't replace a symlink by a real folder.

--
Yves-Alexis

Attachments:

signature.asc (0.19 KB)

corsac at debian

Oct 19, 2009, 2:43 PM

Post #5 of 10 (409 views)
Permalink

Re: Autobuilder problem with optified library [In reply to]

On lun., 2009-10-19 at 22:01 +0200, Yves-Alexis Perez wrote:
> On lun., 2009-10-19 at 22:26 +0300, Kamen Bundev wrote:
> > Well, on the device and probably in autobuilder the /opt folder is
> > actually a symlink to /home/opt... On the other hand maemo-optify
> > produces direct /opt folder.
>
> That's the problem, dpkg won't replace a symlink by a real folder.

I don't really know in that context, but I guess maemo-optify shouldn't
create a real folder if it's a symlink in the device.

Not sure I can help you more…

--
Yves-Alexis

Attachments:

signature.asc (0.19 KB)

marius.vollmer at nokia

Oct 19, 2009, 11:03 PM

Post #6 of 10 (401 views)
Permalink

Re: Autobuilder problem with optified library [In reply to]

ext Yves-Alexis Perez <corsac [at] debian> writes:

> On lun., 2009-10-19 at 22:26 +0300, Kamen Bundev wrote:
>> Well, on the device and probably in autobuilder the /opt folder is
>> actually a symlink to /home/opt... On the other hand maemo-optify
>> produces direct /opt folder.
>
> That's the problem, dpkg won't replace a symlink by a real folder.

If that would be true, wouldn't all optified packages be broken in the
same way? They clearly aren't, so something else must be going on...

I can't reproduce the problem locally either, so I have no clues to
offer.
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bundyo at gmail

Oct 19, 2009, 11:32 PM

Post #7 of 10 (401 views)
Permalink

Re: Autobuilder problem with optified library [In reply to]

GMail defaults to direct mails, resending to the mailing list. Sorry for the
spam.

On Tue, Oct 20, 2009 at 9:30 AM, Kamen Bundev <bundyo [at] gmail> wrote:

> Maybe the autobuilder fails on warnings? Here is the complete log:
>
> https://garage.maemo.org/builder/fremantle/tear_0.3.98-1/armel.root.log.FAILED.txt
>
> At first I was optifiying the dev package too, but after fixing it the
> problem remained.
>
> Regards:
> Bundyo
>
>
> On Tue, Oct 20, 2009 at 9:20 AM, Marius Vollmer <marius.vollmer [at] nokia>wrote:
>
>> ext Kamen Bundev <bundyo [at] gmail> writes:
>>
>> > You have to depend on an optified library.
>>
>> This is about installing a optified package into a system where /opt is
>> a symlink to /home/opt. It doesn't matter why that package is being
>> installed.
>>
>> Clearly, optified packages _can_ be installed on a N900, which does have
>> the symlink. So, "dpkg won't replace a symlink by a real folder" is not
>> what is causing trouble here.
>>
>
>

trippin1 at gmail

Oct 20, 2009, 12:04 AM

Post #8 of 10 (401 views)
Permalink

Re: Autobuilder problem with optified library [In reply to]

On Tue, Oct 20, 2009 at 7:03 AM, Marius Vollmer
<marius.vollmer [at] nokia> wrote:
> ext Yves-Alexis Perez <corsac [at] debian> writes:
>
>> On lun., 2009-10-19 at 22:26 +0300, Kamen Bundev wrote:
>>> Well, on the device and probably in autobuilder the /opt folder is
>>> actually a symlink to /home/opt... On the other hand maemo-optify
>>> produces direct /opt folder.
>>
>> That's the problem, dpkg won't replace a symlink by a real folder.
>
> If that would be true, wouldn't all optified packages be broken in the
> same way? �They clearly aren't, so something else must be going on...
>

The difference here is that these optified packages are being
installed as a build dependency of something else.
> _______________________________________________
> maemo-developers mailing list
> maemo-developers [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

marius.vollmer at nokia

Oct 20, 2009, 12:21 AM

Post #9 of 10 (401 views)
Permalink

Re: Autobuilder problem with optified library [In reply to]

ext Faheem Pervez <trippin1 [at] gmail> writes:

> On Tue, Oct 20, 2009 at 7:03 AM, Marius Vollmer
> <marius.vollmer [at] nokia> wrote:
>> ext Yves-Alexis Perez <corsac [at] debian> writes:
>>
>>> On lun., 2009-10-19 at 22:26 +0300, Kamen Bundev wrote:
>>>> Well, on the device and probably in autobuilder the /opt folder is
>>>> actually a symlink to /home/opt... On the other hand maemo-optify
>>>> produces direct /opt folder.
>>>
>>> That's the problem, dpkg won't replace a symlink by a real folder.
>>
>> If that would be true, wouldn't all optified packages be broken in the
>> same way? They clearly aren't, so something else must be going on...
>
> The difference here is that these optified packages are being
> installed as a build dependency of something else.

The difference is that they are installed into the build environment and
not into a N900.

But the point being made was that the buildbot and the N900
_both_ have the /opt -> /home/opt symlink and that this symlink is
causing dpkg to not install a optified package. That can't be true.

There clearly is something different about the buildbot which is causing
trouble, but it doesn't look like it is dpkg having trouble with
symlinks and directories.
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

julle.luukko at quicknet

Oct 20, 2009, 1:12 AM

Post #10 of 10 (403 views)
Permalink

Re: Autobuilder problem with optified library [In reply to]

Marius Vollmer wrote:
> ext Faheem Pervez <trippin1 [at] gmail> writes:
>
>> On Tue, Oct 20, 2009 at 7:03 AM, Marius Vollmer
>> <marius.vollmer [at] nokia> wrote:
>>> ext Yves-Alexis Perez <corsac [at] debian> writes:
>>>
>>>> On lun., 2009-10-19 at 22:26 +0300, Kamen Bundev wrote:
>>>>> Well, on the device and probably in autobuilder the /opt folder is
>>>>> actually a symlink to /home/opt... On the other hand maemo-optify
>>>>> produces direct /opt folder.
>>>> That's the problem, dpkg won't replace a symlink by a real folder.
>>> If that would be true, wouldn't all optified packages be broken in the
>>> same way? They clearly aren't, so something else must be going on...
>> The difference here is that these optified packages are being
>> installed as a build dependency of something else.
>
> The difference is that they are installed into the build environment and
> not into a N900.
>
> But the point being made was that the buildbot and the N900
> _both_ have the /opt -> /home/opt symlink and that this symlink is
> causing dpkg to not install a optified package. That can't be true.
>
> There clearly is something different about the buildbot which is causing
> trouble, but it doesn't look like it is dpkg having trouble with
> symlinks and directories.
> _______________________________________________

FWIW I call maemo-optify with

maemo-optify libgtkextra-x11-2.0-1

since I only want to optify the library, not the development files. But
this shouldn't make any difference to the optification, should it?

--
Julius
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads