After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 166277 - Please add an unattended-install target.
Please add an unattended-install target.
Status: RESOLVED FIXED
Product: GARNOME
Classification: Deprecated
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: GARNOME Maintainers
garnome list
Depends on:
Blocks:
 
 
Reported: 2005-02-04 14:05 UTC by John Ellis
Modified: 2005-07-17 21:34 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
hack for UNATTENDED support (1.35 KB, patch)
2005-07-06 01:28 UTC, Karsten Bräckelmann 		none Details | Review

Description John Ellis 2005-02-04 14:05:59 UTC 
The root password request for gnome-system-monitor has bitten me again! I have
developed the habit of running paranoid-install for a new garnome release and
walking away, now I come back to find the garnome build stalled at "enter root
password:".

There should be a build target to bypass packages that need user interaction
during the build process. Now for every release I need to move
desktop/gnome-system-monitor to broken/gnome-system-monitor :/
Comment 1 Karsten Bräckelmann 2005-07-06 01:27:00 UTC 
OK, here we go!

The following attached patch adds a hack to support an unattended build. It does
this by not asking for the root password where needed, and follows the code path
as if the root password was not provided by the user instead. If UNATTENDED is
set in gar.conf.mk of course.

Can you please test this?


On a related note (although not actually related to this bug): Why did
desktop/libgnomesu go back into the LIBDEPS for desktop/gnome-system-monitor?
Comment 2 Karsten Bräckelmann 2005-07-06 01:28:10 UTC 
Created attachment 48699 [details] [review]
hack for UNATTENDED support
Comment 3 Bob Kashani 2005-07-17 21:34:43 UTC 
The unattended patch is now in unstable...as of snapshot garnome-2.11-20050714.1730.