remctl 2.13-1 FTBFS on Jaunty

Bug #307326 reported by Evan Broder
4
Affects Status Importance Assigned to Milestone
remctl (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

remctl 2.13-1 in Debian experimental fails to build on Jaunty because one of the tests fails to build.

Line 36 of tests/portable/daemon-t.c fails to pass a third argument to open(), which is required with O_CREAT.

I've attached a patch. With that patch, remctl builds without error on Jaunty.

Revision history for this message
Evan Broder (broder) wrote :
Revision history for this message
Evan Broder (broder) wrote :

Apparently this is the result of Jaunty's gcc setting -D_FORTIFY_SOURCE by default with -O2 (see LP #305901)

Revision history for this message
Evan Broder (broder) wrote :

Err, Anders points out that -D_FORTIFY_SOURCE has been set since Intrepid, and also that this bug and LP bug #305901 are both fallout from -D_FORTIFY_SOURCE, but aren't actually related.

Revision history for this message
Luke Yelavich (themuso) wrote :

It appears that this package has sucessfully built in intrepid, and therefore is available in jaunt. I have also attempted to rebuild it in jaunty amd64 and i386, and both have succesfully built.

In addition, the patch does not apply to the latest remctl package in either intrepid or jaunty.

I am closing this bug as invalid, but if you still think there is an issue, please re-open it and indicate where the fix needs to be made.

Changed in remctl:
status: New → Invalid
Revision history for this message
Evan Broder (broder) wrote :

Intrepid and Jaunty currently have version 2.12-1. This bug was filed against 2.13-1, which was in Debian experimental and not yet in Ubuntu. This bug is related to LP bug #306920, but I didn't feel it was appropriate to try and resolve the build issues in that bug.

The patch that I've attached has been applied and uploaded to Debian experimental as 2.13-2, and I intended to close this bug as soon as the sync in bug #306920 completed.

Changed in remctl:
status: Invalid → New
Revision history for this message
Russ Allbery (rra-debian) wrote : Re: [Bug 307326] Re: remctl 2.13-1 FTBFS on Jaunty

Evan Broder <email address hidden> writes:

> The patch that I've attached has been applied and uploaded to Debian
> experimental as 2.13-2, and I intended to close this bug as soon as the
> sync in bug #306920 completed.

The relevant LP closer is in the Debian changelog, so this bug will
probably be automatically closed once the import happens.

--
Russ Allbery (<email address hidden>) <http://www.eyrie.org/~eagle/>

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

Thanks Russ, yes, that will close this bug.

Changed in remctl:
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package remctl - 2.13-2

---------------
remctl (2.13-2) experimental; urgency=low

  * Call open() with the correct arguments when creating a sentinel file
    in the test suite. (LP: #307326)

remctl (2.13-1) experimental; urgency=low

  * New upstream release.
    - New PHP PECL bindings for libremctl (php5-remctl).
    - New Python remctl extension (python-remctl).
    - Add support for ACL methods to the remctld server.
    - Add the deny ACL method to reject authentication by certain users.
    - Add the princ ACL method, allowing direct specification of
      particular principals in the main configuration file.
    - When processing the include of a directory for configuration or ACL
      files, limit the files included to characters in [a-zA-Z0-9_-] to
      avoid editor temporary files. (Closes: #479481)
  * On new installations of remctl-server, add the inetd.conf line with
    the symbolic protocol name rather than the port number. Depend on a
    new enough version of netbase. Remove that line in prerm.
  * Add Vcs-Git and Vcs-Browser control fields.
  * Update standards version to 3.8.0 (no changes required).

 -- Evan Broder <email address hidden> Mon, 15 Dec 2008 14:10:21 +0000

Changed in remctl:
status: Confirmed → 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.