I’m can’t fix it, I’m to dumb
I keep getting this error from the PPA-buildsystem:
chmod: cannot access `/build/buildd/notify-osd-0.9.14/./configure’: No such file or directory
I don’t know how to correct that. I’ve tried it six times already. If you want to waste your weekend, please… be my guest:
bzr branch lp:~macslow/notify-osd/ubutu
June 20th, 2009 at 5:11 pm
Are you sure that you should not call ./autogen.sh BEFORE releasing a package? maybe cdbs refuses to build a package that has not been autogen-ed
June 20th, 2009 at 5:19 pm
Do you actually have a configure script in your tarball?
Also, it looks like you don’t have an orig.tar.gz for the build in your PPA. Are you actually building from a tarball created with “make dist” or “make distcheck”?
June 20th, 2009 at 5:36 pm
You have to run ./autogen.sh (this will create the configure file and then run configure).
June 20th, 2009 at 5:38 pm
The source requires you to run autogen.sh before the configure script is available, for autotools-based trunk pulls.
June 20th, 2009 at 5:55 pm
Well, the there *is* no configure.
Just autogen.sh, if you run that you get the Makefiles.
So you need to haXX0r your rules file (cdbs sucks btw)
June 20th, 2009 at 6:03 pm
99% sure you need to define the following in your rules:
DEB_CONFIGURE_SCRIPT := ./autogen.sh
DEB_MAKE_CLEAN_TARGET := distclean
June 20th, 2009 at 7:19 pm
Your source is currently correct, you just need to tune up your workflow as you\’re mixing upstream and packaging duties. I suggest you to act as follow: from the current checkout run `./autogen.sh` and then `make dist`, this will produce your pristine tarball. Now work on that, rename it to get your .orig.tar.gz, extract it and copy your debian/ dir among the sources. Then `debuild -S` there to produce the full source to upload, along with the dsc. Meanwhile, I think you need to fix up your examples/Makefile.am, as example-utils.h is missing from the tarball and build is failing there.
June 20th, 2009 at 8:09 pm
Hi guys, I get this error:
checking for GLIB… configure: error: Package requirements (glib-2.0 >= 2.16.0 gthread-2.0 gconf-2.0 gio-2.0) were not met:
No package ‘gconf-2.0′ found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables GLIB_CFLAGS
and GLIB_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Some help?
June 20th, 2009 at 10:16 pm
Hi, I cloned your repo and tried to build your package on my PPA. It seems to me that all that was missing were some packages (gnome-common, mono-devel and libnotify0.4-cil) on the Build-depends section of debian/control. My version looks like this:
Package: notify-osd
Architecture: any
denis@vbox:~/Projects$ more ubutu-control
Source: notify-osd
Section: x11
Priority: optional
Maintainer: DX Team
Build-Depends: cdbs (>= 0.4.41),
debhelper (>= 5),
libglib2.0-dev (>= 2.4),
libgtk2.0-dev (>= 2.4),
libdbus-1-dev (>= 0.36),
libdbus-glib-1-dev (>= 0.60),
libwnck-dev,
libnotify-dev,
libgconf2-dev,
intltool,
gnome-common,
mono-devel,
libnotify0.4-cil
Standards-Version: 3.8.0
Vcs-Bzr: http://bazaar.launchpad.net/~ubuntu-desktop/notify-osd/ubuntu
Homepage: https://launchpad.net/notify-osd
Package: notify-osd
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, human-icon-theme (>= 0.33)
Conflicts: notify-daemon, alsdorf (<< 0.8-0ubuntu2)
Replaces: notify-daemon, alsdorf (<< 0.8-0ubuntu2)
Provides: notification-daemon
Description: daemon that displays passive pop-up notifications
The Desktop Notifications framework provides a standard way of doing
passive pop-up notifications on the Linux desktop. These are
designed to notify the user of something without interrupting their
work with a dialog box that they must close. Passive popups can
automatically disappear after a short period of time.
It took me a few iterations to find out, see this build log:
https://launchpad.net/~denis-fuenzalida/+archive/ppa/+build/1085514/+files/buildlog_ubuntu-karmic-i386.notify-osd_0.9.14-0ubuntu1~ppa10_FULLYBUILT.txt.gz
Kind regards,
Denis
June 20th, 2009 at 11:04 pm
Looks like you didn’t include gnome-common as a build dependency (for the -ppa9 version).
June 21st, 2009 at 3:55 am
Ooops, I noticed that on the previous build I reported I ran ./autogen.sh before debuild and dput.
I grabbed a new copy off the repo; added gnome-common, mono-devel and libnotify0.4-cil as build dependencies; also added the references to example-util.h on examples/makefile.am as Luca Bruno suggested, and it builds correctly on my machine, even dpkg-buildpackage works, but doesn’t build on the PPA.
However, if you run ./autogen.sh again and run debuild and dput, the PPA build works
(see https://launchpad.net/~denis-fuenzalida/+archive/ppa/+sourcepub/656189/+listing-archive-extra)
Kind regards,
Denis
June 21st, 2009 at 7:52 am
I get this alot in my autotools based packages. If your using cdbs, you can just add this to your rules file:
makebuilddir/first-package-name::
NOCONFIGURE=true ./autogen.sh
P.S. Some autogens don’t use the noconfigure variable, but I add it just to be safe, no reason to run ./configure more than once.