Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#45408 closed update (fixed)

autoconf-archive @2013.06.09: update to @2014.10.15

Reported by: cooljeanius (Eric Gallager) Owned by: ryandesign (Ryan Schmidt)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: autoconf-archive

Description

Announcement email: http://lists.gnu.org/archive/html/autoconf-archive-announce/2014-10/msg00001.html

Besides the new version number and checksums, the Portfile update should also deal with the following change:

The Archive no longer creates release tarballs compressed with gzip and
  bzip2; only tarballs compressed with xz and lzip are distributed.

(We will probably want to set use_xz yes in the Portfile)

Also, livecheck confirms the update:

$ port -v livecheck autoconf-archive
autoconf-archive seems to have been updated (port version: 2013.06.09, new version: 2014.10.15)

(autoconf-archive is nomaintainer btw)

Change History (7)

comment:1 in reply to:  description ; Changed 5 years ago by ryandesign (Ryan Schmidt)

Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned

Replying to egall@…:

(We will probably want to set use_xz yes in the Portfile)

We already did this last year in r109317.

comment:2 Changed 5 years ago by ryandesign (Ryan Schmidt)

Resolution: fixed
Status: assignedclosed
Version: 2.3.1

comment:3 in reply to:  1 Changed 5 years ago by cooljeanius (Eric Gallager)

Replying to ryandesign@…:

Replying to egall@…:

(We will probably want to set use_xz yes in the Portfile)

We already did this last year in r109317.

Oh, I see that now... I swear I checked for that line before mentioning it, but I guess I must have just been looking too quickly and missed it...

Replying to ryandesign@…:

r126873

Thanks!

Last edited 5 years ago by cooljeanius (Eric Gallager) (previous) (diff)

comment:4 Changed 5 years ago by cooljeanius (Eric Gallager)

Actually wait a second... why was the conflict with gnome-common introduced?

comment:5 Changed 5 years ago by ryandesign (Ryan Schmidt)

Because both ports try to install a file of the same name.

comment:6 in reply to:  5 Changed 5 years ago by cooljeanius (Eric Gallager)

Replying to ryandesign@…:

Because both ports try to install a file of the same name.

Well yeah, that's why ports usually are marked as conflicting in general, but what was the specific file in this case? I suppose I can try to guess:

$ port contents gnome-common
Port gnome-common contains:
  /opt/local/bin/gnome-autogen.sh
  /opt/local/bin/gnome-doc-common
  /opt/local/share/aclocal/ax_check_enable_debug.m4
  /opt/local/share/aclocal/ax_code_coverage.m4
  /opt/local/share/aclocal/gnome-code-coverage.m4
  /opt/local/share/aclocal/gnome-common.m4
  /opt/local/share/aclocal/gnome-compiler-flags.m4
  /opt/local/share/gnome-common/data/omf.make
  /opt/local/share/gnome-common/data/xmldocs.make

I assume it was one of the macro files starting with the "ax_" prefix? If that is the case, I would recommend removing gnome-common's copies of those macros and having it depend on autoconf-archive instead, as the "ax_" macros are from the autoconf-archive in the first place.

comment:7 Changed 5 years ago by ryandesign (Ryan Schmidt)

Yup, I'll file a bug report for the gnome-common port.

Note: See TracTickets for help on using tickets.