https://bugzilla.novell.com/show_bug.cgi?id=700267https://bugzilla.novell.com/show_bug.cgi?id=700267#c0
Summary: openSUSE:Factory:Contrib/cruisecontrol: Bug
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Platform: Other
OS/Version: openSUSE 11.4
Status: NEW
Severity: Normal
Priority: P5 - None
Component: 3rd party software
AssignedTo: graham(a)andtech.eu
ReportedBy: rozelak(a)volny.cz
QAContact: opensuse-communityscreening(a)forge.provo.novell.com
CC: opensuse-contrib(a)opensuse.org
Found By: Other
Blocker: No
Dear developer.
We decided to use cruisecontrol on 'encfs'-encrypted path, which is not well
supported by your init scripts (cruisecontrol-2.8.4-1.1.noarch.rpm).
Therefore, I'm sending changes we made. They are not perfect, but please, have
a look at them and consider the proposed generalizations in order to simplify
transfer of CC to other path (ideal case is only to change settings in
/etc/default/cruisecontrol).
Unfortunatelly, I cannot append a file with changed files and diffs from
..2.8.4-1.1 rpm. But if you want, I can send it to you to graham(a)andtech.eu
e-mail.
-----
/etc/default/cruisecontrol:
# Run CruiseControl as this user ID (default: ccontrol)
#
# Set this to an empty string to prevent CruiseControl from starting
# automatically. Think to stop CruiseControl before setting an empty string ;o)
#
CRUISE_USER="cruise"
CRUISE_SPOOL=/home/cruise
CRUISE_PID=${CRUISE_SPOOL}/cc.pid
# Port used for the JMX Http Console
CRUISE_JMX_PORT=8000
# Port used for RMI
CRUISE_RMI_PORT=1099
# Port used for HTTP
CRUISE_WEB_PORT=8080
# The home directory of the Java development kit (JDK).
#JAVA_HOME="/usr/lib/jvm/java-1.5.0-sun"
# Arguments to pass to the CruiseControl script
CRUISE_OPTS="-Xmx256m -Xms256m -server -Xincgc
-Dcc.config.file=${CRUISE_SPOOL}/config.xml -Dcc.artifacts=${CRUISE_SPOOL}
/artifacts -Dcc.projects=${CRUISE_SPOOL}/projects
-Dcc.logdir=${CRUISE_SPOOL}/logs -Dcc.ajp13port=8009 -Dlog4j.configurat
ion=file://${CRUISE_SPOOL}/log4j.properties"
-----
/etc/init.d/cruisecontrol:
#!/bin/bash
#
# Init file for CruiseControl server daemon
#
# chkconfig: 2345 20 80
# description: CruiseControl server daemon
#
### BEGIN INIT INFO
# Provides: cruisecontrol
# Required-Start: $local_fs $network $syslog
# Should-Start: java
# Required-Stop: $null
# Default-Start: 3 5
# Default-Stop: 0 1 2 4 6
# Short-Description: CruiseControl
# Description: CruiseControl
### END INIT INFO
# source function library
if [ -f /lib/lsb/init-functions ]; then
. /lib/lsb/init-functions
fi
if [ -f /etc/default/cruisecontrol ]; then
. /etc/default/cruisecontrol
fi
# DT: Must use values defined in /etc/default/cruisecontrol
CRUISE_PID=${CRUISE_PID:-/var/spool/cruisecontrol/cc.pid}
CRUISE_SPOOL=${CRUISE_SPOOL:-/var/spool/cruisecontrol}
start() {
# DT: /etc/cruisecontrol/cruisecontrol.xml replaced by
${CRUISE_SPOOL}/config.xml
# DT: must go to the directory, otherwise CC is started somehow strange ...
# It may be enough to set CCHOME, but I'm not sure ...
CMD="cd $CRUISE_SPOOL; JAVA_HOME=${JAVA_HOME:-/usr}
PATH=${JAVA_HOME:-/usr}/bin:$PATH CC_OPTS=\"${CRUISE_OPTS:-}\" /u
sr/bin/cruisecontrol -configfile ${CRUISE_SPOOL}/config.xml -jmxport
${CRUISE_JMX_PORT:-8000} -rmiport ${CRUISE_RMI_PORT:
-1099} -webport ${CRUISE_WEB_PORT:-8080} -webapppath
/usr/share/cruisecontrol/webapps/cruisecontrol -dashboard /usr/share
/cruisecontrol/webapps/dashboard >/dev/null &"
pgrep -f cruisecontrol-launcher.jar >/dev/null
PROCESS_EXIST=$?
if [ $PROCESS_EXIST -ne 0 ]; then
if [ "`whoami`" == "${CRUISE_USER:-cruise}" ]; then
echo -n "Starting Cruise Control..."
eval ${CMD}
elif [ "`whoami`" == "root" ]; then
echo -n "Starting Cruise Control..."
su -s /bin/sh ${CRUISE_USER:-cruise} -c "${CMD}"
echo "started."
else
echo "You are not root or ${CRUISE_USER:-cruise}, not starting"
fi
else
echo "Cruise Control already started."
exit
fi
}
stop() {
# DT: will fail, if $CRUISE_PID is not accessigle (e.g. encfs-crypted CC
home ...)
if [ -f $CRUISE_PID ]; then
PID=`cat $CRUISE_PID`
fi
PID_EXISTS=-1
if [ ! -z $PID ]; then
ps -p $PID >/dev/null
PID_EXISTS=$?
fi
# DT: If PID not found, use pgrep instead (exactly as in start() section
# TODO: check the user -u ${CRUISE_USER:-cruise} as well?
if [ $PID_EXISTS -ne 0 ] ; then
PID=$(pgrep -f cruisecontrol-launcher.jar)
PID_EXISTS=$?
fi
if [ $PID_EXISTS -eq 0 ] ; then
echo "Stopping Cruise Control (process $PID)..."
kill $PID
else
echo "Cruise Control not running..."
fi
}
case "$1" in
start)
start
;;
stop)
stop
;;
restart)
stop
sleep 5
start
;;
force-reload)
;;
status)
;;
*)
echo "Usage: $0 [start|stop|restart|force-reload|status]"
exit 1
esac
exit 0
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-contrib+help(a)opensuse.org
Hello,
I wish to contribute a new package to the {opensuse contrib or opensuse
factory contrib} repository for anyone to use.
Questions:
1. Which repository should the package go in ? {opensuse contrib or
opensuse factory contrib}
2. What is the osc command I use in getting the new package submitted and
reviewed into the above repository ?
The steps I have done so far are:
- built the package in Opensuse build service [obs] located at [1].
- package builds, installs and uninstalls ok.
- provided for i586 and x86_64 platforms.
- test it works ,which it does.
- Provided package information and how it is built.
- The package gets upgraded-rebuilt when new version of the patch is made
available.
- package announcements are made at [2] as well.
Thankyou,
Glenn
[1]
https://build.opensuse.org/package/show?package=kernel-reiser4&project=home…
[2] https://reiser4.wiki.kernel.org/
--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org
Hi,
By de-digesting the FreshMeat [fm] digest, I have found the (apparently)
new version 0.2.3.8-alpha of your package tor. (Old version last
notified/in tree was 0.2.3.3-alpha).
(This is just for your information. You decide whether to upgrade a package or
not.)
Location:
Extra Information:
[015] TOR 0.2.3.8-ALPHA
Project Tags: Internet, Proxy Servers, Communications, Security, Networking, Utilities
Description:
Tor is a network of virtual tunnels that allows people and
groups to improve their privacy and security on the Internet.
It also enables software developers to create new
communication tools with built-in privacy features. It
provides the foundation for a range of applications that allow
organizations and individuals to share information over
public networks without compromising their privacy.
Individuals can use it to keep remote Websites from tracking
them and their family members. They can also use it to
connect to resources such as news sites or instant
messaging services that are blocked by their local Internet
service providers (ISPs).
Release Notes:
This release fixes some crash and assert bugs, including a
socketpair-related bug which has been bothering Windows users. It adds
support to serve microdescriptors to controllers, so Vidalia's network
map can resume listing relays (once Vidalia implements its side)
and adds better support for hardware AES acceleration. Finally, it
starts the process of adjusting the bandwidth cutoff for getting the
"Fast" flag from 20KB to (currently) 32KB. Preliminary results show
that tiny relays harm performance more than they help network capacity.
Release Tags: Unstable, Bugfixes
License: BSD Revised
http://freecode.com/projects/tor
========================================================================
Today's news on the web:
http://freecode.com/today
Change your subscription:
http://freecode.com/account/edit
Geeknet, Inc. | 594 Howard Street, Suite 300 | San Francisco, CA 94105
Privacy Policy: http://geek.net/privacy-statement
Ciao, FreshMeat De Digester
(/suse/meissner/projects/caldera-tools/packagehunter/fm/filter_freshmeat.pl)
--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org
https://bugzilla.novell.com/show_bug.cgi?id=731295https://bugzilla.novell.com/show_bug.cgi?id=731295#c
Raymond Wooninck <rwooninck(a)opensuse.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|opensuse-contrib(a)opensuse.o |rwooninck(a)opensuse.org
|rg |
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org
https://bugzilla.novell.com/show_bug.cgi?id=731832https://bugzilla.novell.com/show_bug.cgi?id=731832#c8
Raymond Wooninck <rwooninck(a)opensuse.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution| |WONTFIX
--- Comment #8 from Raymond Wooninck <rwooninck(a)opensuse.org> 2011-11-25 18:23:09 UTC ---
I will close this bugreport as a wontfix. The reason for this is that after the
above discussion, I checked the Chromium release management and it is stated
there that Chromium does not have any releases and that every distribution is
free to select which package to provide to their users.
Based on this I raised the question which chromium version should be provided
to the openSUSE users in the opensuse-Packaging and opensuse-project
mailinglists. Also we have to take into account that bringing the version of
Chromium down to 15.0.894, would be impossible as that would cause issues with
opening of the profiles, etc as that they were created with a newer version.
The outcome of the discussion on the mailinglist was that everybody prefers to
have the latest version available for openSUSE.
I can very well understand your point, however I do not have the time to keep
two versions of Chromium alive. However I would welcome any help that I can get
and if you want you could take the maintenance of the Stable version of
Chromium. I would gladly provide you with the necessary scripts, etc to do so.
Regards
Raymond
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org
https://bugzilla.novell.com/show_bug.cgi?id=731295https://bugzilla.novell.com/show_bug.cgi?id=731295#c7
--- Comment #7 from Raymond Wooninck <rwooninck(a)opensuse.org> 2011-11-25 18:07:12 UTC ---
Ben,
openSUSE_12.1 was added as repositories to network:chromium and both V8 and
Chromium are building fine. I also submitted the latest tarball to
opensuse:12.1:Update:Test, but so far nothing moved there.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org
State of delete-request #93372 was changed by worldcitizen:
new -> accepted
Comment:
From version 4.2.0 onwards fwbuilder doesn't have a separate libfwbuilder package any more.
https://build.opensuse.org/request/diff/93372
--
Hermes messaging (http://hermes.opensuse.org)
openSUSE Build Service (https://build.opensuse.org/)
--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org
openSUSE:Factory:Contrib/libfwbuilder
https://build.opensuse.org/request/show/93372
Description: fwbuilder 5.0 doesn't need a seperate libfwbuilder anymore
old:
----
libfwbuilder-4.1.3.tar.bz2
libfwbuilder.spec
spec files:
-----------
++++++ deleted spec files:
--- libfwbuilder.spec
other changes:
--------------
++++++ deleted files:
--- libfwbuilder-4.1.3.tar.bz2
To REVIEW against the previous version:
osc request show --diff 93372
To ACCEPT the request:
osc request accept 93372 --message="reviewed ok."
To DECLINE the request:
osc request decline 93372 --message="declined for reason xyz (see ... for background / policy / ...)."
To REVOKE the request:
osc request revoke 93372 --message="retracted because ..., sorry / thx / see better version ..."
--
Hermes messaging (http://hermes.opensuse.org)
openSUSE Build Service (https://build.opensuse.org/)
Collaboration: http://en.opensuse.org/Build_Service/Collaboration
--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org
https://bugzilla.novell.com/show_bug.cgi?id=731832https://bugzilla.novell.com/show_bug.cgi?id=731832#c7
Cristian Rodríguez <crrodriguez(a)opensuse.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |crrodriguez(a)opensuse.org
--- Comment #7 from Cristian Rodríguez <crrodriguez(a)opensuse.org> 2011-11-23 15:50:14 CLST ---
People complain when things work and when they dont, we cannot please everyone,
My take is to ignore this kind of ridiculous complains but do address _real_
bugs presented, "I do not like the current version number" is not a valid bug
report.
Valid bug reports contain information about crashes, misbehaviours or missing
features, not ramblings about possible theorical scenarios.
Present facts not speculations, theories or dooms day scenarios.
Otherwise it is a waste of people's time and resources for no reason
whatsoever.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org