buildbot failure in MacPorts on buildports-lion-x86_64

[William Siegrist]

On Nov 16, 2012, at 3:30 PM, Ryan Schmidt <ryandesign at macports.org> wrote:

> 
> On Nov 16, 2012, at 12:32, Bradley Giesbrecht <pixilla at macports.org> wrote:
> 
>> On Nov 16, 2012, at 9:45 AM, noreply at macports.org wrote:
>> 
>>> The Buildbot has detected a failed build on builder buildports-lion-x86_64 while building MacPorts.
>>> Full details are available at:
>>> http://build.macports.org/builders/buildports-lion-x86_64/builds/5901
>>> 
>>> Buildbot URL: http://build.macports.org/
>>> 
>>> Buildslave for this Build: apple-lion-x86_64-ports
>>> 
>>> Build Reason: scheduler
>>> Build Source Stamp: [branch trunk] 99758
>>> Blamelist: pixilla at macports.org
>>> 
>>> BUILD FAILED: failed status
>> 
>> The mythtv-core.25 port triggered this build but the failure is for dbus not being able to set the group of a file to a non-existent group.
>> 
>> The dbus Portfile has this:
>> ...
>> set dbus_user     messagebus
>> set dbus_group    messagebus
>> add_users         ${dbus_user} group=${dbus_group} realname=Message\ Bus
>> ...
>> post-activate {
>>   file attributes ${prefix}/var/run/dbus -group ${dbus_group} -owner ${dbus_user}
>>   file attributes ${prefix}/libexec/dbus-daemon-launch-helper -group ${dbus_group}
>> ...
>> 
>> 
>> Shouldn't this work on the buildbots?  If needed, shouldn't the group "message" be created by "add_users"; before post-activate?
> 
> The Snow Leopard and Lion buildbots were just reinstalled (yesterday?) on new (virtual) hardware. So they probably have no users created by MacPorts ports now and will be getting them recreated as ports are reinstalled.
> 
> The dbus port used to use adduser and addgroup in a pre-activate block. In r96635 this was changed to use add_users, but the port's revision was not increased, so the package the buildbot fetched did not contain this, and was still trying to use adduser and addgroup. I would have thought this should still have worked…
> 

I have not investigated this too closely yet, but the new slaves have a copy of the MacPorts files including the local copies of the archives/packages/tarballs. However, I did not create any local user accounts on the new hardware. So this may be due to MacPorts assuming the user accounts exist if the port had been installed previously? 

-Bill