Launchpad PPA tracker.

[GoogleCodeExporter]

the new team url is:
https://launchpad.net/~globalmenu-team

and the ppa url is:
deb http://ppa.launchpad.net/globalmenu-team/ubuntu intrepid main
deb-src http://ppa.launchpad.net/globalmenu-team/ubuntu intrepid main

and the new project url is:
https://launchpad.net/globalmenu

When i get home from deployment i will be merging the current svn into the
LP project bazaar

DO NOT USE THE OLD PPA AS IT IS NOT BEING UPLOADED TO ANYMORE!!

Original issue reported on code.google.com by dwatson031@gmail.com on 3 Dec 2008 at 12:39

[GoogleCodeExporter]

revision 1678 has been uploaded to the ppa. successfully built for amd64, i386, 
and lpia

Original comment by dwatson031@gmail.com on 3 Dec 2008 at 12:47

• Added labels: Type-Packaging
• Removed labels: Type-Tracker, packaging

[GoogleCodeExporter]

To do; chqnge the homepqge and tutorial links. I can do the tutorial on friday. 
Don't
have admin rights for the frontpage, Rainwoodman has to do it.

Original comment by pierre.s...@gmail.com on 3 Dec 2008 at 12:59

[GoogleCodeExporter]

what modifi do you need?

Original comment by rainwood...@gmail.com on 3 Dec 2008 at 5:17

[GoogleCodeExporter]

Basically change the current Launchpad address to the first url dwatson031 
mentions
in this bug

Original comment by pierre.s...@gmail.com on 3 Dec 2008 at 6:41

[GoogleCodeExporter]

Is it OK now? I modifed the url.

Original comment by rainwood...@gmail.com on 3 Dec 2008 at 7:11

[GoogleCodeExporter]

the link is good on the main page now, thanks rainwoodman

Original comment by dwatson031@gmail.com on 4 Dec 2008 at 8:14

[GoogleCodeExporter]

question?

would i modify the makefile.am EXTRA_DIST section to have the schemas file 
added to
the source tarball. as i create a source tarball when building the package to 
upload
to the ppa....it eliminates the vala dep

Original comment by dwatson031@gmail.com on 4 Dec 2008 at 8:18

[GoogleCodeExporter]

lviggiani? Comment 7.

Original comment by rainwood...@gmail.com on 4 Dec 2008 at 9:32

[GoogleCodeExporter]

@dwatson031: well to be honest I'm not so familiar with makefile. BTW, you 
should
take into consideration what I added to makefile.am (source root):

schemadir   = @GCONF_SCHEMA_FILE_DIR@
schema_DATA = applet/gnome-globalmenu-applet.schemas

install-data-local:
    GCONF_CONFIG_SOURCE=$(GCONF_SCHEMA_CONFIG_SOURCE) gconftool-2
--makefile-install-rule $(srcdir)/$(schema_DATA)

..because you need to install the schema 
"applet/gnome-globalmenu-applet.schemas" by
executing the gconftool-2 --makefile-install-rule

You might refer to this ("Application developer information" paragraph):
http://projects.gnome.org/gconf/

Sorry for not being of further help.

Original comment by lviggi...@gmail.com on 4 Dec 2008 at 10:02

[GoogleCodeExporter]

@drwatson:
currently I recommend you to use

./configure --disable-schemas-install --disable-tests

for making packages.

the first one is recommended by Fedora packaging policies. They then ask the
packagers to write little scripts in RPM spec files for installing the gconf 
schemas.

I believe a similar policy also applies to ubuntu packaging. 

the second one can reduce the compiling time. and also because the test cases 
are
usually sort of prototypes, they may not even compile properly.

Original comment by rainwood...@gmail.com on 19 Dec 2008 at 8:27

[GoogleCodeExporter]

@rainwoodman
is this for the current trunk or, 0.7-devel branch....

also when do u anticipate to merge 0.7 into trunk....i havent made any new 
packages
lately, i was kind of waiting for the 0.7 branch...

Original comment by dwatson031@gmail.com on 19 Dec 2008 at 9:56

[GoogleCodeExporter]

That was only for 0.7-devel.

0.7-devel has been pushed to the trunk, therefore it also applies to the trunk 
now.

Original comment by rainwood...@gmail.com on 21 Dec 2008 at 10:33

[GoogleCodeExporter]

the old trunk was copied to branches/0.6, so please update the ppa.

I don't understand how ppa works, but the situation at googlecode is

branches/0.6, the old 0.6 trunk, no activities.
branches/0.7-devel, the old 0.7-devel branch, no more activities.
trunk, the active 0.7 branch.

The weird situation we have now is because there are no real 'Releases'. So 
much has
been rewritten for each new version, the trunk plays as something like a 
release tag.
but we also do bug fixes on this 'released' code because we always have so many 
bugs,
issues, and new features.

Perhaps from 0.8 and on we'll be able to correctly use 'releases'.

Original comment by rainwood...@gmail.com on 22 Dec 2008 at 6:43

[GoogleCodeExporter]

0.7.1 is pushed to svn/tags/v0.7.1. It is a bug fix for the never tagged 
release 0.7.0. 
Please build debs with this tag.

Original comment by rainwood...@gmail.com on 4 Jan 2009 at 1:51

• Changed title: Launchpad PPA tracker.
• Added labels: Type-Tracker
• Removed labels: Type-Packaging

[GoogleCodeExporter]

any updates on that ?

Original comment by pierre.s...@gmail.com on 7 Jan 2009 at 6:08

[GoogleCodeExporter]

Not yet. 

Original comment by rainwood...@gmail.com on 7 Jan 2009 at 7:44

[GoogleCodeExporter]

sorry guys, i have been busy as of late with missions and such....my deployment 
is
almost up.....as soon as i get a chance i will update the ppa....sorry it has 
been
awhile since i've update the ppa

Original comment by dwatson031@gmail.com on 8 Jan 2009 at 4:23

[GoogleCodeExporter]

https://edge.launchpad.net/~bmhm/+archive/ppa
It's built. It works here. Can anyone test it for 64 bits ?

Original comment by pierre.s...@gmail.com on 31 Jan 2009 at 1:28

[GoogleCodeExporter]

I've installed globalmenu using this PPA 
https://edge.launchpad.net/~bmhm/+archive/ppa
 and now the switcher part of the menu doesn't appear :(
Must I enable it by adding an extra string to my ~/.gnomerc ?
Also the preferences option, when I right click the applet, shows an empty 
window.

Regards,
Luis Davim

Original comment by luis.da...@gmail.com on 31 Jan 2009 at 7:31

[GoogleCodeExporter]

Are you an 64 bits ?

Original comment by pierre.s...@gmail.com on 31 Jan 2009 at 7:45

[GoogleCodeExporter]

$ sudo dpkg -i Desktop/gnome-globalmenu_0.7.2-ppa4_i386.deb  
(Reading database ... 212824 files and directories currently installed.)
Unpacking gnome-globalmenu (from .../gnome-globalmenu_0.7.2-ppa4_i386.deb) ...
dpkg: error processing Desktop/gnome-globalmenu_0.7.2-ppa4_i386.deb (--install):
 trying to overwrite `/usr/lib/gtk-2.0/modules/libglobalmenu-gnome.a', which is also
in package gnome2-globalmenu
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 Desktop/gnome-globalmenu_0.7.2-ppa4_i386.deb

Removing gnome2-globalmenu first works fine, but shouldn't it upgrade smoothly?

Will post testing results as another comment when I've logged in/out

Original comment by mailfor...@googlemail.com on 1 Feb 2009 at 1:20

[GoogleCodeExporter]

Right.

1. Before login/out, try and remove old globalmenu and add the new one. Nothing 
shows
up on Panel
2. Logout/in and the menu shows up, but with NO switcher, choosing preferences 
from
right click menu shows a tiny window that is empty when resized BUT menus are 
there
3. Remove the lines in .gnomerc that I had to make 0.6 work. Now when I 
logout/in the
menus don't show up at all, globalmenu is still in the panel (if I rich click 
it I
can open the same blank prefs window) but there is nothing to show that it is 
there.

For now I'm reinstalling 0.6 from the ppa - but I can do any more testing that 
you
want on the 0.7 package...

Original comment by mailfor...@googlemail.com on 1 Feb 2009 at 1:36

[GoogleCodeExporter]

Seems like the 0.7.2 deb is corrupted.

Original comment by rainwood...@gmail.com on 2 Feb 2009 at 5:10

[GoogleCodeExporter]

Same Issue I had. No preferences etc.
I thought this was a bug of globalmenu by itself, so I left it as it was.
I'll check it out. Seems that I missed some files of the original 7.2-release.

Original comment by bmarw...@gmail.com on 2 Feb 2009 at 6:09

[GoogleCodeExporter]

it's been built and working. 
check out https://edge.launchpad.net/~globalmenu-team/+archive/ppa
and leave a comment please.

Next thing to do would be a manpage and scripts

Original comment by bmarw...@gmail.com on 2 Feb 2009 at 7:02

[GoogleCodeExporter]

Which app should be man-pagized?

Original comment by rainwood...@gmail.com on 2 Feb 2009 at 7:10

[GoogleCodeExporter]

My comment: thumb up!

The pref issues shall have been fixed in trunk. a release of 0.7.3 will come 
soon.

Original comment by rainwood...@gmail.com on 2 Feb 2009 at 7:11

[GoogleCodeExporter]

phew, thanks. I got a little ambitious about this project.

well, a manpage for globalmenu of course!  We should have a manpage for users
(section 7 or 8 i think) and another one for devs (1 or sth).

Where else to explain how to enable it (like export  
GTK_MODULES=globalmenu-gnome).

Original comment by bmarw...@gmail.com on 2 Feb 2009 at 7:40

[GoogleCodeExporter]

If you can write some pages to begin with, I'll be more than happy to commit 
them to
the repo.

Original comment by rainwood...@gmail.com on 2 Feb 2009 at 7:59

[GoogleCodeExporter]

0.7.3 is out. what about announcing in ubuntuforum thread after the ppa is 
ready?

Original comment by rainwood...@gmail.com on 4 Feb 2009 at 4:27

[GoogleCodeExporter]

Nice idea! Can I have the honor?
(when will the PPA be ready?)

Original comment by lviggi...@gmail.com on 4 Feb 2009 at 6:37

[GoogleCodeExporter]

We may still wait a little until we've rewritten the doc and backported to 
Hardy.
bmarwell, is it possible to backport to Hardy ?

Original comment by pierre.s...@gmail.com on 5 Feb 2009 at 1:58

[GoogleCodeExporter]

Also, on a clean install, is there any extra step besides sudo apt-get install ?
On an old install, what lines need to be removed from the profile file. Can we 
leave
them alltogether ?

Original comment by pierre.s...@gmail.com on 5 Feb 2009 at 2:07

[GoogleCodeExporter]

Backporting should be no problem. Even a release for jaunty is easily possible 
using
Launchpad's buildservice. I will look into it.

Does ~/.gnomerc still need to be edited? I think at least the module line must 
be
inside (not tested yet without), allthough the news on the front-page tells us 
otherwise.

I will try to build a new release in my repo and tell you when it's done. Does 
any of
you use Hardy?

Original comment by bmarw...@gmail.com on 5 Feb 2009 at 7:43

[GoogleCodeExporter]

Ok I just thought there had been building issues with LP. None of us has hardy, 
but
what I'd suggest is build them both for hardy and jaunty, and let the user 
feedback come.

Original comment by pierre.s...@gmail.com on 5 Feb 2009 at 8:38

[GoogleCodeExporter]

Well yes, actually there are.

----------
For hardy:
After installing, the following source dependencies are still unsatisfied:
debhelper(inst 6.0.4ubuntu1 ! >= wanted 7) valac(inst 0.1.6-1 ! >= wanted 0.5.5)

Solution: Wait until the vala-ppa-team releases a package for hardy (I already 
asked
them - might be released soon)
--------

For jaunty:
./autogen.sh has to be executed for each distribution. See
http://code.google.com/p/gnome2-globalmenu/issues/detail?id=323#c3

--------

Until then: intrepid only.

Original comment by bmarw...@gmail.com on 8 Feb 2009 at 8:27

[GoogleCodeExporter]

So, I am still getting no prefs and no switcher, despite the recent update. Am 
I the
only one?

Original comment by mailfor...@googlemail.com on 8 Feb 2009 at 11:48

[GoogleCodeExporter]

That's so sad. :( Which update are you mentioning by 'the recent update'?

Original comment by rainwood...@gmail.com on 8 Feb 2009 at 11:55

[GoogleCodeExporter]

@bmarwell, Perhaps the recent 'no pref win' issue is related to the 
installation of
gconf schema files in your ppa builds. Would you like to take a look into it?

Original comment by rainwood...@gmail.com on 9 Feb 2009 at 2:55

[GoogleCodeExporter]

$apt-cache showpkg gnome-globalmenu
Package: gnome-globalmenu
Versions: 
0.7.3~svn2243~intrepid2
(/var/lib/apt/lists/ppa.launchpad.net_globalmenu-team_ubuntu_dists_intrepid_main
_binary-i386_Packages)
(/var/lib/dpkg/status)
 Description Language: 
                 File:
/var/lib/apt/lists/ppa.launchpad.net_globalmenu-team_ubuntu_dists_intrepid_main_
binary-i386_Packages
                  MD5: afd317d02f2a4d254da20d5fbf0a310d

Original comment by mailfor...@googlemail.com on 9 Feb 2009 at 3:51

[GoogleCodeExporter]

> installation of gconf schema files in your ppa builds.
I just wonder why it does work for some ppl (like me and friends of mine) and 
for
some it doesn't.

pbuilder just executes what the Makefile tells them. I even said 
--disable-schemes
for 0.7.3~svn2243, but it seems that it didn't work. On the other hand, the 
scheme
files do not contain data which should destroy the application's interface.

I'm puzzled. I will take a deeper look at the debian/rules-file.

Original comment by bmarw...@gmail.com on 9 Feb 2009 at 4:15

[GoogleCodeExporter]

Update:
I just switched to --disable-schemas-install (as in the docs). But it's still 
getting
compiled and installed - even using plain "make". Can you check that please?

On the other hand it won't build using pbuilder anymore:
----
Making clean in globalmenu
make[3]: Entering directory
`/tmp/buildd/gnome-globalmenu-0.7.3~svn2259~intrepid1/gtk-modules/globalmenu'
Makefile:450: .deps/libdyn_patch_la-dyn-patch-*.Plo: No such file or directory
make[3]: *** No rule to make target 
`.deps/libglobalmenu_gnome_la-module-main.Plo'. 
Stop.
----

Original comment by bmarw...@gmail.com on 9 Feb 2009 at 5:02

[GoogleCodeExporter]

@42: 

(1) No files are supposed to be installed with a plain make. From what message 
did
you tell the schema files were still installed? I'll also look into this issue.

(2) making failure: there has been no changes in that directory for a long 
time. The
dependency failure is mostly because of autotools. Checkout to a clean path and 
do a
autogen.sh throughly may solve the issue.

@41: (1) for some people it works, because the schema files have been installed
either via svn build or some other ways; where as for new users the schema 
files are
not installed.
(2) I am not sure how debian handle gconf schemas. The most important feature of
(notice it is schemas not schemes) --disable-schemas-install parameter is not to
install the schema with gconf-tool. Whether or not the schemas files are copied 
to
the directory doesn't matter in this context. (AKA two levels of install: i) 
copy
schema files ii) gconf-tool --make-install-rules. 

In Fedora, the rule for gconf schema install is always use 
--disable-schemas-install
to disable the stage ii) of the installation, then in the rpm post-install-rules
specifically invoke gconf-tool to install/uninstall the schemas.

I am not sure what happens in debian world.

Original comment by rainwood...@gmail.com on 10 Feb 2009 at 1:27

[GoogleCodeExporter]

As a reference:

The following message means the schema file is translated -- translation is 
always
done despite whether --disable-schemas-install is specified.
./autogen.sh --disable-schemas-install
----
make
.....
LC_ALL=C /usr/bin/intltool-merge -s -u -c ./po/.intltool-merge-cache ./po
gnome-globalmenu.schemas.in gnome-globalmenu.schemas
Found cached translation database
Merging translations into gnome-globalmenu.schemas.
----
This is the result for

make install DESTDIR=$PWD/_inst

in the project dir with trunk@2260.
Clearly the .schema file is installed. But gconf-tool is not invoked(since that 
tool
is supposed to work with root privilege or throw an error and stops make 
install)

tree _inst
_inst
`-- usr
    |-- lib
    |   |-- bonobo
    |   |   `-- servers
    |   |       `-- GlobalMenu_PanelApplet.server
    |   `-- gtk-2.0
    |       `-- modules
    |           |-- libglobalmenu-gnome-0.7.3.so
    |           |-- libglobalmenu-gnome.a
    |           |-- libglobalmenu-gnome.la
    |           `-- libglobalmenu-gnome.so -> libglobalmenu-gnome-0.7.3.so
    `-- local
        |-- etc
        |   `-- gconf
        |       `-- schemas
        |           `-- gnome-globalmenu.schemas
        |-- include
        |   `-- libgnomenu
        |       |-- globalmenu.h
        |       |-- gnomenu.h
        |       |-- helper.h
        |       |-- interface-item.h
        |       |-- interface-shell.h
        |       |-- keygrab.h
        |       |-- label.h
        |       |-- menu.h
        |       |-- menubar.h
        |       |-- menubarbox.h
        |       |-- menuitem.h
        |       |-- menushellutils.h
        |       |-- monitor.h
        |       |-- parser.h
        |       |-- serializer.h
        |       `-- window.h
        |-- lib
        |   |-- libgnomenu-0.7.3.so.2 -> libgnomenu-0.7.3.so.2.0.0
        |   |-- libgnomenu-0.7.3.so.2.0.0
        |   |-- libgnomenu.a
        |   |-- libgnomenu.la
        |   |-- libgnomenu.so -> libgnomenu-0.7.3.so.2.0.0
        |   `-- pkgconfig
        |       `-- libgnomenu.pc
        |-- libexec
        |   `-- GlobalMenu.PanelApplet
        `-- share
            |-- locale
            |   |-- es_ES
            |   |   `-- LC_MESSAGES
            |   |       `-- gnome-globalmenu.mo
            |   |-- fr_FR
            |   |   `-- LC_MESSAGES
            |   |       `-- gnome-globalmenu.mo
            |   |-- hu_HU
            |   |   `-- LC_MESSAGES
            |   |       `-- gnome-globalmenu.mo
            |   |-- it_IT
            |   |   `-- LC_MESSAGES
            |   |       `-- gnome-globalmenu.mo
            |   |-- ru_RU
            |   |   `-- LC_MESSAGES
            |   |       `-- gnome-globalmenu.mo
            |   `-- zh_CN
            |       `-- LC_MESSAGES
            |           `-- gnome-globalmenu.mo
            `-- pixmaps
                `-- globalmenu.png

Original comment by rainwood...@gmail.com on 10 Feb 2009 at 1:48

[GoogleCodeExporter]

refer to 
https://bugs.launchpad.net/ubuntu/+source/nemiver/+bug/175974

on ubuntu the default place for schemas are /usr/share/gconf/schemas/

If the schemas file is not installed to the correct location override it with
--with-gconf-schema-file-dir

Original comment by rainwood...@gmail.com on 10 Feb 2009 at 4:30

[GoogleCodeExporter]

No. Since 8.10 they changed to /etc.
However I noticed with prefix=/usr the schemas files are installed into 
/usr/etc.

Perhaps that's the reason why it is failing.

Refer to comment 6 in http://bbs.archlinux.org/viewtopic.php?id=37864 .
./configure --prefix=/usr --sysconfdir=/etc

should fix at least the location of the schema files.

for invoking gconftool,
I am attaching the control file for debian: gnome-panel-data 2.14 as a 
reference(this
is the best I can find). notice the lines in postXXXX.

Perhaps you should look into the control file for a ubuntu's recent version of
gnome-panel to get some ideas.

Original comment by rainwood...@gmail.com on 10 Feb 2009 at 5:26

Attachments:

• control.tar.gz

[GoogleCodeExporter]

Hi,

Thanks for the information. I will also see if I can invoke gconf manually. 
There are
postinstall-scripts just like those in a SPEC-file.
Good point about sysconfdir. I will also add it to the autogen-script.

I'm not sure if I can do it today, but probably by tomorrow.

Original comment by bmarw...@gmail.com on 10 Feb 2009 at 7:34

[GoogleCodeExporter]

On the Ubuntuforums we were asked to comment here about whether or no the 
proposed
schema fix worked to solve the empty pref panel problem. Sadly, it does not 
seem to
work. Even though the schema is in the correct directory, gconf simply doesn't 
seem
to pick it up (I can't find it with a search).

Original comment by ThomHolw...@gmail.com on 10 Feb 2009 at 9:37

[GoogleCodeExporter]

Hi, I just checked out the control.tar.gz.
I will try to get into the code so we get more packages: the main package, a 
data
package (as above) and a doc-package.

the control.tar.gz clears things up (regarding gconf-schemas). but first of 
all, I
will see if I can make a single working package.

Original comment by bmarw...@gmail.com on 10 Feb 2009 at 11:17

[GoogleCodeExporter]

did you notice:
http://code.google.com/p/gnome2-globalmenu/issues/detail?id=326

?

perhaps users will give information. you just have to comment in the right place
(thread) ;) found this thread just cause i wanted to vote on ubuntu brainstorm, 
got
linked to ubuntuforums.org and from there i got linked to this place. its hard 
to
help as a user if you have to search the needed information by yourself :) your 
work
is great, i want to use it =)

Original comment by christia...@gmail.com on 11 Feb 2009 at 11:57