Please merge automake1.10 (1:1.10.2-2) from Debian unstable (and create automake1.10 package)

Bug #413928 reported by Savvas Radevic
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Undecided
Unassigned
automake1.10 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I have tried to build the new version of gnote (0.6.2-1 from the Debian archive) in the PPA for karmic, but it looks like in PPA the system installs automake 1.11-1 version, whereas in Debian unstable seems to build fine.

Example:
http://launchpadlibrarian.net/30351641/buildlog_ubuntu-karmic-amd64.gnote_0.6.2-1~ppakarmic1_FAILEDTOBUILD.txt.gz
https://edge.launchpad.net/~gnote/+archive/ppa-experimental

"
Build-Depends: cdbs, debhelper (>= 6), bzip2, automake (>= 1:1.10), automake (<< 1:1.11), autoconf (>= 2.53), pkg-config (>= 0.14.0), libgtk2.0-dev (>= 2.12), libglibmm-2.4-dev, libgtkmm-2.4-dev, libpanelappletmm-2.6-dev, libgtkspell-dev, libxml2-dev, libgconf2-dev, uuid-dev, libboost-dev, libboost-filesystem-dev, libboost-test-dev, libpcre++-dev, intltool (>= 0.35), gnome-doc-utils (>= 0.4.2), rarian-compat, libxslt1-dev
[...]
Get:117 http://ftpmaster.internal karmic/main automake 1:1.11-1 [559kB]
[...]
Setting up automake (1:1.11-1) ...
update-alternatives: using /usr/bin/automake-1.11 to provide /usr/bin/automake (automake) in auto mode.
[...]
Checking correctness of source dependencies...
After installing, the following source dependencies are still unsatisfied:
automake(inst 1:1.11-1 ! << wanted 1:1.11)
Source-dependencies not satisfied; skipping gnote
"

Perhaps the build-depends is wrongly defined for "automake (>= 1:1.10), automake (<< 1:1.11)"?

Related branches

Revision history for this message
William Grant (wgrant) wrote :

There is nothing broken here except the gnote package. It depends on a version of 'automake' that Karmic doesn't have any more: 1.10. You should probably replace "automake (>= 1:1.10), automake (<< 1:1.11)" with just "automake1.10".

Changed in launchpad:
status: New → Invalid
Revision history for this message
Savvas Radevic (medigeek) wrote : Re: [Bug 413928] [NEW] [ppa karmic] cannot use specific automake version (1.10) during build

Now that I look at it again, maybe it's a packaging error in
automake1.10 and/or automake1.11 ??

Revision history for this message
Savvas Radevic (medigeek) wrote : Re: [ppa karmic] cannot use specific automake version (1.10) during build

I see, thank you!

Revision history for this message
Savvas Radevic (medigeek) wrote : Re: [Bug 413928] Re: [ppa karmic] cannot use specific automake version (1.10) during build

William, I'm afraid I tried another package that has automake1.10
defined in build-depends:

https://edge.launchpad.net/~gnote/+archive/ppa-experimental/+build/1174724

http://launchpadlibrarian.net/30608631/buildlog_ubuntu-karmic-i386.dbus-c%2B%2B_0~20090718-1~ppakarmic1_MANUALDEPWAIT.txt.gz

dbus-c++_0~20090718-1~ppakarmic1.dsc exists in cwd
** Using build dependencies supplied by package:
Build-Depends: cdbs, debhelper (>= 7), libtool, automake1.10, autoconf
(>= 2.59), libdbus-1-dev (>= 0.60), libglib2.0-dev, libgtkmm-2.4-dev,
libexpat1-dev, doxygen
Checking for already installed source dependencies...
[...]
automake1.10: missing
automake1.10: does not exist
[...]
E: Couldn't find package automake1.10

It looks like it has to be defined as just "automake (>= 1.10)", but I
might be wrong.
Any ideas? :)

Revision history for this message
Savvas Radevic (medigeek) wrote :

According to rmadison, the only automake1.10 package is the source:
$ rmadison -u ubuntu automake1.10
automake1.10 | 1:1.10.1-2 | hardy | source
automake1.10 | 1:1.10.1-3 | intrepid | source
automake1.10 | 1:1.10.2-0ubuntu3 | jaunty | source
automake1.10 | 1:1.10.2-0ubuntu3.09.04 | jaunty-proposed | source
automake1.10 | 1:1.10.2-1ubuntu2 | karmic | source

$ rmadison -u ubuntu automake
  automake | 1:1.4-p6-9 | dapper | source
  automake | 1:1.4-p6-12 | hardy | source
  automake | 1:1.4-p6-13 | intrepid | source
  automake | 1:1.4-p6-13 | jaunty | source
  automake | 1:1.4-p6-13 | karmic | source
  automake | 1:1.10.1-2 | hardy | all
  automake | 1:1.10.1-3 | intrepid | all
  automake | 1:1.10.2-0ubuntu3 | jaunty | all
  automake | 1:1.10.2-0ubuntu3.09.04 | jaunty-proposed | all
  automake | 1:1.11-1 | karmic | all

But I wonder why the debian system builds them:
https://buildd.debian.org/pkg.cgi?pkg=dbus-c%2b%2b

Shouldn't the ppa build system and the debian build system be compatible?

Revision history for this message
William Grant (wgrant) wrote : Re: [ppa karmic] cannot use specific automake version (1.10) during build

Ubuntu's automake1.10 source has not yet been altered to produce an automake1.10 binary. Its old automake binary was clobbered by automake1.11, so automake1.10 is no longer Provided by automake. This is likely a bug in the Ubuntu automake1.10 source package.

If you don't need a particular version of automake, your suggestion is probably correct.

summary: - [ppa karmic] cannot use specific automake version (1.10) during build
+ Please create automake1.10 package for karmic
Revision history for this message
Savvas Radevic (medigeek) wrote : Re: Please create automake1.10 package for karmic

I'm sorry, I think I understand why it doesn't work:
- automake1.9 source package has a binary package automake1.9 defined.
- automake1.10 source package has a "automake" binary package, but also has "Provides: automaken, automake1.10".

I filed this under automake1.10 source package and changed the title. I hope I'm right, unless the ppa build system should read the "Provides" packages (?)

Revision history for this message
William Grant (wgrant) wrote :

The build system *does* read Provides. The flaw is in your statement about automake1.10.

The "automake1.10" source used to have an "automake" binary package with the properties that you described. But that "automake" binary has since been replaced by the one from the "automake1.11" source.

Revision history for this message
Savvas Radevic (medigeek) wrote :

Thanks for your help, much clearer now. :)

Revision history for this message
Julien Lavergne (gilir) wrote :

Confirmed, there is no automake1.10 package available. Necessary modifications was done on Debian with the revision 1:1.10.2-2. A merge should fix this.

Changed in automake1.10 (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
summary: - Please create automake1.10 package for karmic
+ Please merge automake1.10 (1:1.10.2-2) from Debian unstable (and create
+ automake1.10 package)
Revision history for this message
Savvas Radevic (medigeek) wrote :

Looks like a pretty straightforward merge, I'll give it a go. :)

Changed in automake1.10 (Ubuntu):
assignee: nobody → Savvas Radevic (medigeek)
Revision history for this message
Savvas Radevic (medigeek) wrote :

I think we're supposed to upload the diff.gz in this case, right?

http://launchpadlibrarian.net/30656173/buildlog_ubuntu-karmic-i386.automake1.10_1%3A1.10.2-2ubuntu1_FULLYBUILT.txt.gz

P.S. I added "(LP: #413928)" to debian/changelog in the uploaded diff.gz.

Changed in automake1.10 (Ubuntu):
assignee: Savvas Radevic (medigeek) → nobody
Revision history for this message
Colin Watson (cjwatson) wrote :

Reviewing.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package automake1.10 - 1:1.10.2-2ubuntu1

---------------
automake1.10 (1:1.10.2-2ubuntu1) karmic; urgency=low

  * Merge from debian unstable (LP: #413928), remaining changes:
    - python.m4: Update to the patch integrated upstream (LP: #377584).
      m4/python.m4 (AM_PATH_PYTHON): When computing pythondir and
      pyexecdir, pass the expanded prefix resp. exec_prefix as `prefix'
      to get_python_lib, so python can determine the name of the site
      directory depending on the install location. Afterwards, replace
      the directory names with the unexpanded values of $PYTHON_PREFIX
      resp. $PYTHON_EXEC_PREFIX again, to allow override according to
      the documentation. Fixes site directory computation for Debian
      and Ubuntu (`dist-packages' for a prefix of `/usr' or `/usr/local',
      `site-packages' elsewhere).
    - python.m4: Don't call the get_python_lib() with the unexpanded
      arguments.
    - Backport upstream commit f9a3dde93cbd6497966d45631ec1cf665b09e3a9 to
      fix regression vs 1.10.1 to fix a depfiles failure which rendered some
      source packages unbuildable. Thanks to Mirco Bauer for helping to
      investigate and isolate the fix. (LP: #356612)

automake1.10 (1:1.10.2-2) unstable; urgency=low

  * Convert package to automake1.10 now that automake 1.11 is released.

 -- Savvas Radevic <email address hidden> Sat, 15 Aug 2009 20:15:16 +0100

Changed in automake1.10 (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.