Re: maemo 5 on OMAP3 dev board

2009-01-17 Thread Felipe Contreras
On Sun, Jan 18, 2009 at 8:14 AM, Ryan Abel  wrote:
> On Jan 17, 2009, at 8:13 PM, Mike Turquette wrote:
>
>> I'm a developer at Texas Instruments.  I'm interested in building as
>> many pieces of Maemo 5 (especially Hildon) as possible for some of our
>> OMAP3 development boards.
>
> Nokia is (or was, they've likely moved on to their own hardware by
> now) using Beagle Boards for internal testing, so it's certainly a
> feasible thing.

Some of us use beagle boards, but that's more of a personal endeavour.

According to Quim Gil, Juha Kallioinen is working on an experiment
precisely for this[1]

[1] http://www.mail-archive.com/maemo-developers@maemo.org/msg17757.html

-- 
Felipe Contreras
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: maemo 5 on OMAP3 dev board

2009-01-17 Thread Ryan Abel
On Jan 17, 2009, at 8:13 PM, Mike Turquette wrote:

> I'm a developer at Texas Instruments.  I'm interested in building as
> many pieces of Maemo 5 (especially Hildon) as possible for some of our
> OMAP3 development boards.

Nokia is (or was, they've likely moved on to their own hardware by  
now) using Beagle Boards for internal testing, so it's certainly a  
feasible thing.

> I'd prefer to use OpenEmbedded for building out of SVN, however a
> quick glance through Nokia's repositories is a bit overwhelming.  Is
> there an easy guide to way out,

Maemo has its own SDK, the version of which for Fremantle is currently  
in pre-alpha.[1][2]

> 1) what software in
> https://stage.maemo.org/viewcvs.cgi/projects/haf/trunk/?root=maemo is
> currently maintained and will be used in Maemo 5?

You want http://repository.maemo.org/pool/fremantle/ This table may  
also be useful, though: 
http://repository.maemo.org/unstable/fremantle/maemo4.1.1_vs_5.0prealpha_content_comparison.html

> 2) is there a document of any kind detailing how to build a root fs
> from these pieces, or is that left as an exercise ot the reader?

The current release of Maemo 5 is an SDK-only release, so it's meant  
to be used for development on a PC. A rootfs image that might be  
flashed onto a real device will likely be forthcoming once a real  
device is available.

For the time being, the pre-alpha doesn't contain all of the  
components that will be shipping with the final release. Most notably,  
it's still using the Diablo UI (the Fremantle UI will be revealed in  
May-ish when the Beta SDK is released).

> 3) is anyone doing anything like I am mentioning (specifically with
> OE)? I know there are some recipes for Maemo 4, but they are quite
> deprecated (though I've gotten a fair number of them to build with
> small modifications).


I don't know of anybody working with OE to build Maemo. Maemo has a  
fairly mature and workable SDK, so I can't see anybody being very  
inclined to put the work into hamming another build system into  
submission.

Probably what you really want to do is talk to the Mer guys, as their  
work coincides more closely with your goals, I think, than Nokia's.[3] 
[4]


[1]http://maemo.org/development/sdks/maemo5_prealpha_main/
[2]http://maemo.org/news/announcements/first_maemo_5_sdk_release_targeting_platform_developers/
[3]http://wiki.maemo.org/Mer_Blueprint
[4]http://wiki.maemo.org/Mer_Blueprint_New

--
Ryan Abel
Maemo Community Council chair

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


RE: SQLite3

2009-01-17 Thread maemo
On Sat, 17 Jan 2009, Dr. Nicholas Shaw wrote:

> If 3.4.1 is part of the Maemo distribution, I’m unaware of it.  I’ve 
> downloaded/installed the debs @ 
> repository.maemo.org/pool/Diablo/free/s/sqlite3/ and sqlite3 does not run.  
> Nor can you run sqlite3 and have it run.  This does work and so far I 
> haven’t had any problems.

Funny- this same conversation comes up every few months. The sqlite 
package in maemo does NOT have the command-line tools in it. I believe 
there's a bug open for that. I dont know if Diablo has it either - maybe 
someone else can correct me if Im wrong.


-- 
Aj.

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


maemo 5 on OMAP3 dev board

2009-01-17 Thread Mike Turquette
Hi all,

I'm a developer at Texas Instruments.  I'm interested in building as
many pieces of Maemo 5 (especially Hildon) as possible for some of our
OMAP3 development boards.

I'd prefer to use OpenEmbedded for building out of SVN, however a
quick glance through Nokia's repositories is a bit overwhelming.  Is
there an easy guide to way out,
1) what software in
https://stage.maemo.org/viewcvs.cgi/projects/haf/trunk/?root=maemo is
currently maintained and will be used in Maemo 5?
2) is there a document of any kind detailing how to build a root fs
from these pieces, or is that left as an exercise ot the reader?
3) is anyone doing anything like I am mentioning (specifically with
OE)? I know there are some recipes for Maemo 4, but they are quite
deprecated (though I've gotten a fair number of them to build with
small modifications).

I assume the Scratchbox and Maemo communities are mostly interested in
applications-level development, which would make sense.  However I'm
hopeful there are a few out there interested in these ideas.

Thanks much,
Mike
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: SQLite3

2009-01-17 Thread Kamen Bundev
What do you mean by "does not run"? It does work for me and other people.
The address you found it at is the official Diablo SDK repo. Check here to
see whats included in Diablo and the corresponding versions and changes from
Chinook:

http://repository.maemo.org/stable/4.1/4.1_vs_4.0.1_content_changes.html

Regards:
Bundyo

On Sat, Jan 17, 2009 at 9:21 PM, Dr. Nicholas Shaw wrote:

>  If 3.4.1 is part of the Maemo distribution, I'm unaware of it.  I've
> downloaded/installed the debs @
> repository.maemo.org/pool/Diablo/free/s/sqlite3/ and sqlite3 does not
> run.  Nor can you run sqlite3 and have it run.  This does work and so far I
> haven't had any problems.
>
>
>
> My next step is to create a deb package (need to learn how first…).
>
>
>
> Nick.
>
>
>
> *From:* Kamen Bundev [mailto:bun...@gmail.com]
> *Sent:* Saturday, January 17, 2009 11:56 AM
> *To:* Dr. Nicholas Shaw
> *Cc:* maemo-developers
> *Subject:* Re: SQLite3
>
>
>
> Hi,
>
> You can also get a source package from Debian and create a deb directly
> from it in scratchbox. The real problem is that Sqlite3 3.4.1 is part of the
> Maemo distribution and if you replace is for the user you may break
> something else (i think the db format is slightly different) and break it
> more if the user uninstalls your version. So, why don't you use 3.4.1?
>
> Regards:
> Bundyo
>
> On Sat, Jan 17, 2009 at 8:44 PM, Dr. Nicholas Shaw 
> wrote:
>
> Ok, I have sqlite3.6.8 up-and-running on my 810.  Here's what I did:
>
> 1.  Got scratchbox up-and-running.
> 2.  Under my user directory (logged in to scratchbox), created a directory
> called tmp. Then got out of scratchbox.
> 3.  Went to sqlite.org ( http://www.sqlite.org/download.html ) and
> downloaded the tarball of the complete source tree (sqlite-3 6 8-tar.gz) -
> or whatever version is current.
> 4.  Outside of scratchbox, I copied this file to the tmp directory I
> created.
> 5.  Back inside scratchbox, I unzipped/untared the file (this creates a new
> sqlite directory).
> 6.  Changed to the directory and compiled, ran make, and make install
> according to the README.
> 7.  Located where make install put the files and the permissions then put
> those files onto my 810, ran chmod +x on all and chown.  Here are the
> locations and ownerships:
>
>/usr/local/bin/sqlite executableuser:users
>/usr/lib and /usr/local/lib (same files)
>
>libsqlite3.aroot:staff
>libsqlite3.la   root:staff
>libsqlite3.so -> libsqlite3.so.0.8.6root:staff
>libsqlite3.so.0 -> libsqlite3.so.0.8.6  root:staff
>libsqlite3.so.0.8.6 root:staff
>
> 8.  Tested it on books.db (listing of my library). :-)
>
> Nick.
>
>
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>
>
>
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: Native gcc for development on N810

2009-01-17 Thread Klaus Rotter
Klaus Rotter schrieb:
> Add http://repository.maemo.org/sdk with components sdk/free and 
Wrong!
Native gcc for maemo/diablo is in
http://repository.maemo.org/ with components sdk/free and sdk/non-free.

-- 
  Klaus Rotter * klaus at rotters dot de * www.rotters.de
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: extras repository problems

2009-01-17 Thread Till Harbaum / Lists
Hi,

Am Samstag 17 Januar 2009 schrieb Graham Cobb:
> Presumably you are using dh_shlibdeps, so it is using data supplied by the 
Yes, i do.

> library.  The library tells it what the condition has to be, so it is 
> libgoocanvas which is forcing the "=".  You might want to complain to the 
> maintainer of that.  There may be a good reason but it does make life 
> difficult for packages which need to depend on libgoocanvas.
Ok, good to know who the culprit is.

> There you are, more than you ever wanted to know about how debhelper handles 
> shared library dependencies!
Thanks for the explanation. Sometimes it's really nice if someone summarizes the
man pages :-)

Thanks again,
  Till
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: Native gcc for development on N810

2009-01-17 Thread Klaus Rotter
Klaus Rotter schrieb:
> I want to install a gcc toolchain directly on the N810. 

Marat Radchenko mailed me the answer. It is in the sdk repository.
Add http://repository.maemo.org/sdk with components sdk/free and 
sdk/non-free.

-Klaus

-- 
  Klaus Rotter * klaus at rotters dot de * www.rotters.de
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


RE: SQLite3

2009-01-17 Thread Dr. Nicholas Shaw
If 3.4.1 is part of the Maemo distribution, I’m unaware of it.  I’ve 
downloaded/installed the debs @ 
repository.maemo.org/pool/Diablo/free/s/sqlite3/ and sqlite3 does not run.  Nor 
can you run sqlite3 and have it run.  This does work and so far I haven’t had 
any problems.

 

My next step is to create a deb package (need to learn how first…).

 

Nick.

 

From: Kamen Bundev [mailto:bun...@gmail.com] 
Sent: Saturday, January 17, 2009 11:56 AM
To: Dr. Nicholas Shaw
Cc: maemo-developers
Subject: Re: SQLite3

 

Hi,

You can also get a source package from Debian and create a deb directly from it 
in scratchbox. The real problem is that Sqlite3 3.4.1 is part of the Maemo 
distribution and if you replace is for the user you may break something else (i 
think the db format is slightly different) and break it more if the user 
uninstalls your version. So, why don't you use 3.4.1?

Regards:
Bundyo

On Sat, Jan 17, 2009 at 8:44 PM, Dr. Nicholas Shaw  wrote:

Ok, I have sqlite3.6.8 up-and-running on my 810.  Here's what I did:

1.  Got scratchbox up-and-running.
2.  Under my user directory (logged in to scratchbox), created a directory
called tmp. Then got out of scratchbox.
3.  Went to sqlite.org ( http://www.sqlite.org/download.html ) and
downloaded the tarball of the complete source tree (sqlite-3 6 8-tar.gz) -
or whatever version is current.
4.  Outside of scratchbox, I copied this file to the tmp directory I
created.
5.  Back inside scratchbox, I unzipped/untared the file (this creates a new
sqlite directory).
6.  Changed to the directory and compiled, ran make, and make install
according to the README.
7.  Located where make install put the files and the permissions then put
those files onto my 810, ran chmod +x on all and chown.  Here are the
locations and ownerships:

   /usr/local/bin/sqlite executableuser:users
   /usr/lib and /usr/local/lib (same files)

   libsqlite3.aroot:staff
   libsqlite3.la   root:staff
   libsqlite3.so -> libsqlite3.so.0.8.6root:staff
   libsqlite3.so.0 -> libsqlite3.so.0.8.6  root:staff
   libsqlite3.so.0.8.6 root:staff

8.  Tested it on books.db (listing of my library). :-)

Nick.


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

 

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


RE: SQLite3

2009-01-17 Thread Dr. Nicholas Shaw
Oops, I forgot two steps...

8.  cd /usr/bin
9.  ln -s /usr/local/bin/sqlite3.dat sqlite3 (creates a link)

Now you just call sqlite3 from wherever and you're up-and-running.

Nick.


-Original Message-
From: maemo-developers-boun...@maemo.org
[mailto:maemo-developers-boun...@maemo.org] On Behalf Of Dr. Nicholas Shaw
Sent: Saturday, January 17, 2009 11:45 AM
To: 'maemo-developers'
Subject: SQLite3

Ok, I have sqlite3.6.8 up-and-running on my 810.  Here's what I did:

1.  Got scratchbox up-and-running.
2.  Under my user directory (logged in to scratchbox), created a directory
called tmp. Then got out of scratchbox.
3.  Went to sqlite.org ( http://www.sqlite.org/download.html ) and
downloaded the tarball of the complete source tree (sqlite-3 6 8-tar.gz) -
or whatever version is current.  
4.  Outside of scratchbox, I copied this file to the tmp directory I
created.
5.  Back inside scratchbox, I unzipped/untared the file (this creates a new
sqlite directory).
6.  Changed to the directory and compiled, ran make, and make install
according to the README.
7.  Located where make install put the files and the permissions then put
those files onto my 810, ran chmod +x on all and chown.  Here are the
locations and ownerships:

/usr/local/bin/sqlite executableuser:users
/usr/lib and /usr/local/lib (same files)

libsqlite3.aroot:staff
libsqlite3.la   root:staff
libsqlite3.so -> libsqlite3.so.0.8.6root:staff
libsqlite3.so.0 -> libsqlite3.so.0.8.6  root:staff
libsqlite3.so.0.8.6 root:staff

8.  Tested it on books.db (listing of my library). :-)

Nick.


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: SQLite3

2009-01-17 Thread Kamen Bundev
Hi,

You can also get a source package from Debian and create a deb directly from
it in scratchbox. The real problem is that Sqlite3 3.4.1 is part of the
Maemo distribution and if you replace is for the user you may break
something else (i think the db format is slightly different) and break it
more if the user uninstalls your version. So, why don't you use 3.4.1?

Regards:
Bundyo

On Sat, Jan 17, 2009 at 8:44 PM, Dr. Nicholas Shaw wrote:

> Ok, I have sqlite3.6.8 up-and-running on my 810.  Here's what I did:
>
> 1.  Got scratchbox up-and-running.
> 2.  Under my user directory (logged in to scratchbox), created a directory
> called tmp. Then got out of scratchbox.
> 3.  Went to sqlite.org ( http://www.sqlite.org/download.html ) and
> downloaded the tarball of the complete source tree (sqlite-3 6 8-tar.gz) -
> or whatever version is current.
> 4.  Outside of scratchbox, I copied this file to the tmp directory I
> created.
> 5.  Back inside scratchbox, I unzipped/untared the file (this creates a new
> sqlite directory).
> 6.  Changed to the directory and compiled, ran make, and make install
> according to the README.
> 7.  Located where make install put the files and the permissions then put
> those files onto my 810, ran chmod +x on all and chown.  Here are the
> locations and ownerships:
>
>/usr/local/bin/sqlite executableuser:users
>/usr/lib and /usr/local/lib (same files)
>
>libsqlite3.aroot:staff
>libsqlite3.la   root:staff
>libsqlite3.so -> libsqlite3.so.0.8.6root:staff
>libsqlite3.so.0 -> libsqlite3.so.0.8.6  root:staff
>libsqlite3.so.0.8.6 root:staff
>
> 8.  Tested it on books.db (listing of my library). :-)
>
> Nick.
>
>
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


SQLite3

2009-01-17 Thread Dr. Nicholas Shaw
Ok, I have sqlite3.6.8 up-and-running on my 810.  Here's what I did:

1.  Got scratchbox up-and-running.
2.  Under my user directory (logged in to scratchbox), created a directory
called tmp. Then got out of scratchbox.
3.  Went to sqlite.org ( http://www.sqlite.org/download.html ) and
downloaded the tarball of the complete source tree (sqlite-3 6 8-tar.gz) -
or whatever version is current.  
4.  Outside of scratchbox, I copied this file to the tmp directory I
created.
5.  Back inside scratchbox, I unzipped/untared the file (this creates a new
sqlite directory).
6.  Changed to the directory and compiled, ran make, and make install
according to the README.
7.  Located where make install put the files and the permissions then put
those files onto my 810, ran chmod +x on all and chown.  Here are the
locations and ownerships:

/usr/local/bin/sqlite executableuser:users
/usr/lib and /usr/local/lib (same files)

libsqlite3.aroot:staff
libsqlite3.la   root:staff
libsqlite3.so -> libsqlite3.so.0.8.6root:staff
libsqlite3.so.0 -> libsqlite3.so.0.8.6  root:staff
libsqlite3.so.0.8.6 root:staff

8.  Tested it on books.db (listing of my library). :-)

Nick.


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: extras repository problems

2009-01-17 Thread Graham Cobb
On Saturday 17 January 2009 12:25:04 Till Harbaum / Lists wrote:
> > Actually, the autobuilder doesn't check installation dependencies, only
> > build
>
> It creates the dependencies. So everything required to build was definitely
> available during the build process and thus everything to run it was also
> there.

No, the autobuilder doesn't create dependencies -- the package debian/control 
file creates the dependencies and **can** specify anything you like.  

However, it **normally** includes "${shlibs:Depends}" to define dependencies 
on shared libraries.  ${shlibs:Depends} is (effectively) set up from commands 
in the debian/rules file.  If you are using the common debhelper calls your 
debian/rules will probably have a call to dh_shlibdeps which is what sets up 
${shlibs:Depends}.

You can read the man pages for dh_shlibdeps and dpkg-shlibdeps to see what 
that does but the bottom line is that it uses data supplied by the shared 
library itself to set the dependency.  So, if that is what is setting the 
dependency (instead of it being hard coded in debian/control) then it should, 
indeed, be being set correctly automatically during the build.  But this is 
not a function of the autobuilder -- it is a combination of your package 
files (debian/control and debian/rules) and the shared library you are 
depending on (libgoocanvas-common in this case).

> > It is a really bad idea for osm2go to have an exact version dependency
> > (the "=" in the dependency) because it means it will be broken if someone
>
> But that's being added automatically by the build process. The question is:
> How and why does this get added?

Presumably you are using dh_shlibdeps, so it is using data supplied by the 
library.  The library tells it what the condition has to be, so it is 
libgoocanvas which is forcing the "=".  You might want to complain to the 
maintainer of that.  There may be a good reason but it does make life 
difficult for packages which need to depend on libgoocanvas.

For your future information, libgoocanvas is probably using dh_makeshlibs to 
set up the dependency information.  Check out the man page for that (and 
the -V option in particular) if you want to see how that is used.

There you are, more than you ever wanted to know about how debhelper handles 
shared library dependencies!

Graham

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: extras repository problems

2009-01-17 Thread Till Harbaum / Lists
Hi,

Am Samstag 17 Januar 2009 schrieb Niels Breet:
> There was a problem with cron on the repository machine. That has been
> fixed now. You should see your packages in the repository now?
Great, thanks, looks like it's there.

> It should be available? I see it in Packages:
Yupp, i was just too stupid as i had some different version installed from 
a different repository (yes, i know, one shouldn't use other repositories :-)

> The new debmaster position will be filled soon, the community council is
> selecting the candidate at the moment. So I guess we will hear something
> about that real soon.
Great!

Thanks,
  Till
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: extras repository problems

2009-01-17 Thread Antonio Aloisio
Hi Niels,
Ok, I can see the new version of Qt on extra-devel
Thank you

Antonio

On Sat, Jan 17, 2009 at 2:36 PM, Niels Breet  wrote:

> On Sat, January 17, 2009 10:40, Till Harbaum / Lists wrote:
> > Hi,
> >
> >
> > i am having two problems with the maemo repositories:
> >
> > a) i uploaded osm2go-0.6-9 half a day ago and the logs show the autobuild
> > was successful: https://garage.maemo.org/builder/diablo/osm2go_0.6-9/
> > But the new version just doesn't show up in extras-devel.
> > How comes?
> >
>
> There was a problem with cron on the repository machine. That has been
> fixed now. You should see your packages in the repository now?
>
> >
> > b) The previous version also isn't installable anymore since it claims to
> > have a mssing dependency on libgoocanvas-common (= 0.9-2maemo0). How do
> > these things happen? Since this version also was built using the
> > autobuilder, the build mechanism sure had access to all these parts. How
> > comes they are gone now?
> >
>
> It should be available? I see it in Packages:
>
> Package: libgoocanvas-common
> Priority: optional
> Section: libs
> Installed-Size: 128
> Maintainer: Johannes Schmid 
> Architecture: all
> Source: goocanvas
> Version: 0.9-2maemo0
> Filename:
> pool/diablo/free/g/goocanvas/libgoocanvas-common_0.9-2maemo0_all.deb
> Size: 31966
> MD5sum: 9a3573d2989d4c889be3146a715eb415
>
>
> > I really think the repositories need a maintainer. There are so
> > many broken things in them ...
>
> The new debmaster position will be filled soon, the community council is
> selecting the candidate at the moment. So I guess we will hear something
> about that real soon.
>
> >
> > Till
>
>
> --
> Niels Breet
> maemo.org webmaster
>
>
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>



-- 

Natalie Wood  - "The only time a woman really succeeds in changing a man is
when he is a baby."
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: extras repository problems

2009-01-17 Thread Niels Breet
On Sat, January 17, 2009 10:40, Till Harbaum / Lists wrote:
> Hi,
>
>
> i am having two problems with the maemo repositories:
>
> a) i uploaded osm2go-0.6-9 half a day ago and the logs show the autobuild
> was successful: https://garage.maemo.org/builder/diablo/osm2go_0.6-9/
> But the new version just doesn't show up in extras-devel.
> How comes?
>

There was a problem with cron on the repository machine. That has been
fixed now. You should see your packages in the repository now?

>
> b) The previous version also isn't installable anymore since it claims to
> have a mssing dependency on libgoocanvas-common (= 0.9-2maemo0). How do
> these things happen? Since this version also was built using the
> autobuilder, the build mechanism sure had access to all these parts. How
> comes they are gone now?
>

It should be available? I see it in Packages:

Package: libgoocanvas-common
Priority: optional
Section: libs
Installed-Size: 128
Maintainer: Johannes Schmid 
Architecture: all
Source: goocanvas
Version: 0.9-2maemo0
Filename:
pool/diablo/free/g/goocanvas/libgoocanvas-common_0.9-2maemo0_all.deb
Size: 31966
MD5sum: 9a3573d2989d4c889be3146a715eb415


> I really think the repositories need a maintainer. There are so
> many broken things in them ...

The new debmaster position will be filled soon, the community council is
selecting the candidate at the moment. So I guess we will hear something
about that real soon.

>
> Till


--
Niels Breet
maemo.org webmaster


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: extras repository problems

2009-01-17 Thread Antonio Aloisio
Hi,
I had the same problem with Qt.
The building process finished successfully  at 5 o'clock and it's still not
available on extra-devel.

Antonio

On Sat, Jan 17, 2009 at 1:37 PM, Graham Cobb

> wrote:

> On Saturday 17 January 2009 09:40:11 Till Harbaum / Lists wrote:
> > a) i uploaded osm2go-0.6-9 half a day ago and the logs show
> > the autobuild was successful:
> >   https://garage.maemo.org/builder/diablo/osm2go_0.6-9/
> > But the new version just doesn't show up in extras-devel.
> > How comes?
>
> I am sure Niels or Ed will take a look and respond soon (although it is a
> weekend so maybe not).
>
> > b) The previous version also isn't installable anymore since
> > it claims to have a mssing dependency on libgoocanvas-common
> > (= 0.9-2maemo0). How do these things happen? Since this
> > version also was built using the autobuilder, the build mechanism
> > sure had access to all these parts. How comes they are gone
> > now?
>
> Actually, the autobuilder doesn't check installation dependencies, only
> build
> dependencies (this is necessary in case the dependencies are circular).
>  That
> is why, after building, it is important to test it can be installed.  There
> has been discussion of the promotion interface checking installation
> dependencies but, as far as I know, it doesn't do that yet.
>
> It is a really bad idea for osm2go to have an exact version dependency
> (the "=" in the dependency) because it means it will be broken if someone
> updates a new version of libgoocanvas-common.  However, 0.9-2maemo0 seems
> to
> be the current version in extras-devel so the problem must either be that
> you
> have some other version of libgoocanvas-common installed on your tablet or
> it
> cannot be installed for some reason.  You will need to use apt and dpkg
> from
> the command line to see why:
>
> dpkg -l libgoocanvas-common
>
> will tell you if you have libgoocanvas-common installed, and which version
>
> apt-get install libgoocanvas-common=0.9-2maemo0
>
> will tell you why you can't install it.
>
> > I really think the repositories need a maintainer. There are so
> > many broken things in them ...
>
> The whole purpose of extras-devel is to allow things like this to be found,
> before breaking extras.  That is why it contains broken things -- so they
> can
> be found and repaired!
>
> Graham
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>



-- 

Natalie Wood  - "The only time a woman really succeeds in changing a man is
when he is a baby."
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: extras repository problems

2009-01-17 Thread Till Harbaum / Lists
Hi,

Am Samstag 17 Januar 2009 schrieb Graham Cobb:
> I am sure Niels or Ed will take a look and respond soon (although it is a 
> weekend so maybe not).
It's not really urgent, i was just wondering ...

> Actually, the autobuilder doesn't check installation dependencies, only build 
It creates the dependencies. So everything required to build was definitely
available during the build process and thus everything to run it was also there.

> It is a really bad idea for osm2go to have an exact version dependency 
> (the "=" in the dependency) because it means it will be broken if someone 
But that's being added automatically by the build process. The question is: How
and why does this get added?

> dpkg -l libgoocanvas-common
> 
> will tell you if you have libgoocanvas-common installed, and which version
Thanks for that hint, i had some newer version from a different repository. 
Interesting that this didn't matter when i updated osm2go, just when i 
deinstall and re-install. Anyway, that hint was the solution. Thanks!

> > I really think the repositories need a maintainer. There are so
> > many broken things in them ...
> 
> The whole purpose of extras-devel is to allow things like this to be found, 
> before breaking extras.  That is why it contains broken things -- so they can 
> be found and repaired!
Yes, but a) some things are promoted to extras in this broken state and b)
there are so many packages in extras-devel that just sit there and collect 
dust. If your definition of extras-devel is right, then it should basically
be empty since broken things should be removed and working things
be promoted.

Thanks again,
  Till
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


Re: extras repository problems

2009-01-17 Thread Graham Cobb
On Saturday 17 January 2009 09:40:11 Till Harbaum / Lists wrote:
> a) i uploaded osm2go-0.6-9 half a day ago and the logs show
> the autobuild was successful:
>   https://garage.maemo.org/builder/diablo/osm2go_0.6-9/
> But the new version just doesn't show up in extras-devel.
> How comes?

I am sure Niels or Ed will take a look and respond soon (although it is a 
weekend so maybe not).

> b) The previous version also isn't installable anymore since
> it claims to have a mssing dependency on libgoocanvas-common
> (= 0.9-2maemo0). How do these things happen? Since this
> version also was built using the autobuilder, the build mechanism
> sure had access to all these parts. How comes they are gone
> now?

Actually, the autobuilder doesn't check installation dependencies, only build 
dependencies (this is necessary in case the dependencies are circular).  That 
is why, after building, it is important to test it can be installed.  There 
has been discussion of the promotion interface checking installation 
dependencies but, as far as I know, it doesn't do that yet.

It is a really bad idea for osm2go to have an exact version dependency 
(the "=" in the dependency) because it means it will be broken if someone 
updates a new version of libgoocanvas-common.  However, 0.9-2maemo0 seems to 
be the current version in extras-devel so the problem must either be that you 
have some other version of libgoocanvas-common installed on your tablet or it 
cannot be installed for some reason.  You will need to use apt and dpkg from 
the command line to see why:

dpkg -l libgoocanvas-common

will tell you if you have libgoocanvas-common installed, and which version

apt-get install libgoocanvas-common=0.9-2maemo0

will tell you why you can't install it.

> I really think the repositories need a maintainer. There are so
> many broken things in them ...

The whole purpose of extras-devel is to allow things like this to be found, 
before breaking extras.  That is why it contains broken things -- so they can 
be found and repaired!

Graham
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers


extras repository problems

2009-01-17 Thread Till Harbaum / Lists
Hi,

i am having two problems with the maemo repositories:

a) i uploaded osm2go-0.6-9 half a day ago and the logs show
the autobuild was successful:
  https://garage.maemo.org/builder/diablo/osm2go_0.6-9/
But the new version just doesn't show up in extras-devel. 
How comes?

b) The previous version also isn't installable anymore since
it claims to have a mssing dependency on libgoocanvas-common 
(= 0.9-2maemo0). How do these things happen? Since this
version also was built using the autobuilder, the build mechanism
sure had access to all these parts. How comes they are gone 
now?

I really think the repositories need a maintainer. There are so
many broken things in them ...

Till
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers