[ Closed ] 64bit testing (Page 2 of 7)

Hello!

One thing about "winff". I have tried a lot of method found on the net, but none worked for me.
When launching "winff" with a terminal I get this message:

Anybody got an idea of what this mean?
I'm not a power-user

A+

Francis.

astrocisco : I get the same warning/error message in the terminal when I use the terminal to launch WinFF, but it does seem to launch and work ok.

corenominal : I see that my Launchpad account, and I'm guessing every Launchpad account, offers to set up a PPA. Let me wrangle with that for a bit and see if I can get it set up, in the meantime, here's the full "ls" output of the directory I built the new package in, which files are you interested in me uploading to my now-hypothetical-but-soon-to-be-all-too-real-PPA?

flick@lil-spooky:~/lxpanelpackagebuild$ ls
lxpanel-0.3.7
lxpanel_0.3.7-1.diff.gz
lxpanel_0.3.7-1.dsc
lxpanel_0.3.7.orig.tar.gz
lxpanel-0.3.999
lxpanel_0.3.999-0ubuntu1_amd64.changes
lxpanel_0.3.999-0ubuntu1_amd64.deb
lxpanel_0.3.999-0ubuntu1.dsc
lxpanel_0.3.999-0ubuntu1_source.build
lxpanel_0.3.999-0ubuntu1_source.changes
lxpanel_0.3.999-0ubuntu1.tar.gz
lxpanel-0.3.999.orig.tar.gz
lxpanel-netstat-plugin_0.3.999-0ubuntu1_amd64.deb

corenominal : my PPA is live, now I've hit this snag : when I built my lxpanel updated package, I just used the -us -uc flags because I didn't have any gpg keys set up. Of course, now I learn that I cannot upload unsigned packages to my PPA. I assume this means I get to update/rebuild the package all over again on my own machine, this time using the gpg key I had to make for Launchpad, before I can upload to the PPA? Is there a way to just "sign" the already existing source package on my machine?

corenominal : tried moving into the working directory and issuing "debuild -S", all seemed to go well and then :

....bunch of other output...
Finished running lintian.
Now signing changes and any dsc files...
signfile lxpanel_0.3.999-0ubuntu1.dsc flick <flick@lil-spooky.wi.rr.com>
gpg: skipped "flick <flick@lil-spooky.wi.rr.com>": secret key not available
gpg: [stdin]: clearsign failed: secret key not available
debsign: gpg error occurred!  Aborting....
debuild: fatal error at line 1250:
running debsign failed
.......................................................................

I have a gpg key set up on this machine, my .bashrc references that key and has the DEBFULLNAME and DEBEMAIL fields filled in, I remembered to source my .bashrc after getting those fields set up.

Any other pointers would be great, I can't imagine what component I'm missing.

EDIT : Figured out my own mess. Updated and signed the package. Used dput to try sending it to my Launchpad PPA and I think I had success :

flick@lil-spooky:~/lxpanelpackagebuild$ dput my-ppa lxpanel_0.3.999-0ubuntu2_source.changes
Checking Signature on .changes
gpg: Signature made Wed 04 Mar 2009 08:22:28 PM CST using DSA key ID AFB09905
gpg: Good signature from "Cory Flick <flicck@gmail.com>"
Good signature on /home/flick/lxpanelpackagebuild/lxpanel_0.3.999-0ubuntu2_source.changes.
Checking Signature on .dsc
gpg: Signature made Wed 04 Mar 2009 08:22:03 PM CST using DSA key ID AFB09905
gpg: Good signature from "Cory Flick <flicck@gmail.com>"
Good signature on /home/flick/lxpanelpackagebuild/lxpanel_0.3.999-0ubuntu2.dsc.
Uploading to my-ppa (via ftp to ppa.launchpad.net):
  lxpanel_0.3.999-0ubuntu2.dsc: done.
  lxpanel_0.3.999-0ubuntu2.tar.gz: done.   
  lxpanel_0.3.999-0ubuntu2_source.changes: done.
Successfully uploaded packages.
Not running dinstall.

MORE EDIT :

Just got an email from Launchpad saying my package was rejected, the error is amusing to me because I am, obviously, on Launchpad, as Cory Flick, so I can't imagine why Launchpad cannot find me.

Rejected:
Could not find person 'Cory Flick'
Further error processing not possible because of a critical previous error.

Format: 1.8
Date: Wed, 04 Mar 2009 20:20:30 -0600
Source: lxpanel
Binary: lxpanel lxpanel-netstat-plugin
Architecture: source
Version: 0.3.999-0ubuntu2
Distribution: intrepid
Urgency: low
Maintainer: Andrew Lee <andrew@linux.org.tw>
Changed-By: Cory Flick <flicck@gmail.com>
Description:
lxpanel    - a lightweight desktop panel for X
lxpanel-netstat-plugin - network monitor plugin for lxpanel
Changes:
lxpanel (0.3.999-0ubuntu2) intrepid; urgency=low

EDIT THE THIRD :

Discovered my Launchpad ID may be "flicck" instead of "Cory Flick", changed my dput config accordingly, and tried uploading again, only to get this :

flick@lil-spooky:~/lxpanelpackagebuild$ dput my-ppa lxpanel_0.3.999-0ubuntu2_source.changes
Already uploaded to ppa.launchpad.net
Doing nothing for lxpanel_0.3.999-0ubuntu2_source.changes

So it looks like my Launchpad PPA has my source package but won't build it because it cannot find me, although it's me who uploaded the package. Enough fun for one night, I'll try tackling this again tomorrow.

Last edited by flicck (2009-03-05 02:58:04)

corenominal : PPA is up and running, I bumped the version of the package and dput successfully uploaded the source package to the PPA/build daemons, whereupon...the same package that builds fine on my machine failed to build on the PPA. Of course it did. )

I'm going through the "failed to build" logs from the PPA, and I think I found the issue in these lines :
configure: error: The intltool scripts were not found. Please install intltool.
make: *** [config.status] Error 1
dpkg-buildpackage: failure: debian/rules build gave error exit status 2

My machine, doing an aptitude search intltool, shows that it has that tool installed, I cannot imagine why the PPA build daemons do not. If, of course, that is the error causing the build to fail. I'll investigate and study some more, in the meantime, if you or anyone else familiar with building lxpanel has some insights, I'm all ears, or eyes on the forums, as the case may be.

If anyone wants to look at my PPA and scope out the build logs yourself, the PPA is at :
https://launchpad.net/~flicck/+archive/ppa

Added intltool as a build dependency. New error preventing successful build in the PPA, though again not on my machine :

make[3]: Entering directory `/build/buildd/lxpanel-0.3.999/data'
make[3]: *** No rule to make target `ui/panel-pref.ui', needed by `all-am'.  Stop.
make[3]: Leaving directory `/build/buildd/lxpanel-0.3.999/data'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/buildd/lxpanel-0.3.999'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/buildd/lxpanel-0.3.999'
make: *** [build-stamp] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2

For what it's worth, lxpanel is working fine for me. I installed using the CLI install, then ran the testing script. I only had two problems getting this setup:

1) My PC randomly froze during the installation of packages called by the !# script. Hard reboot, ran the script again, worked fine.
2) I had an empty xorg.conf, which means gdm gave me nothing but a black screen.
  -- Dropped to terminal, ran 'sudo dpkg-reconfigure xserver-xorg', answered the questions it asked.
  -- Modified the resulting xorg.conf to use the "vesa" driver. Restarted gdm and I had one working monitor. Downloaded the Nvidia drivers and used nvidia-settings to enable my dual-monitor setup.

I picked the "Lite" install, but this seems slightly different than the "Lite" install on my x86 laptop. For instance, the OB menu has more default entries Am I seeing the difference between 8.10 and 8.10.03?

flicck: You made me double-check that I'm running a 64-bit OS. Shame on you! Alas, I had to re-familiarize myself with the lxpanel issue. Indeed, the window icons are the standard gray window that others see.

So, disregard my previous statement about no problems with lxpanel. It's just not a problem for me because I'm not going to be keeping lxpanel for long!

I beg to differ. Good luck with the new packages!

corenominal : thanks for the kind encouragement, and sorry for hijacking this thread.

Tried building one of the other required packages, lxmenu-data. It won't build because the intltool version in Intrepid is too old, as shown by my pbuilder error here :

checking for intltool >= 0.40.0... ./configure: line 5545: intltool-update: command not found
found
configure: error: Your intltool is too old.  You need intltool 0.40.0 or later.
make: *** [config.status] Error 1
dpkg-buildpackage: failure: debian/rules build gave error exit status 2

This is getting to be too reminiscent of 90s era RPM dependency hell. I think it's time to give up on getting a fully functioning 64 bit lxpanel on the current Intrepid-based Crunchbang.

Time to go looking into that whole tint2 and trayer thing. )

rho : for the root windows are ugly problem, have a look at this and read the comments too : http://helpforlinux.blogspot.com/2009/0 … tiful.html

Last edited by flicck (2009-03-09 03:20:03)

Sorry, since it's still in testing we only have the scripts I'm afraid. Ask someone on this thread nicely, maybe they'll do a remastersys for you?