[arch-dev-public] Packages still containing rc.d scripts
Hi, I just noticed that a couple of packages that have been marked complete on the TODO list still seem to contain initscripts rc.d files: $ pkgfile -g '/etc/rc.d/*' | egrep -v '/(bftpd|ifplugd|ppp)$' extra/bluez extra/ntp extra/tomcat6 extra/x11vnc community/couchdb community/wesnoth I saw an updated version of bluez in [testing] that no longer contains these files. Can someone please have a look at ntp, tomcat6, x11vnc, couchdb and wesnoth? Regards, Lukas
On Wednesday 05 June 2013 12:37:54 Lukas Fleischer wrote:
I saw an updated version of bluez in [testing] that no longer contains these files. Can someone please have a look at ntp, tomcat6, x11vnc, couchdb and wesnoth?
I guess that those have been updated on trunk only. -- Andrea Arch Linux Developer
[2013-06-05 12:44:03 +0200] Andrea Scarpino:
On Wednesday 05 June 2013 12:37:54 Lukas Fleischer wrote:
I saw an updated version of bluez in [testing] that no longer contains these files. Can someone please have a look at ntp, tomcat6, x11vnc, couchdb and wesnoth?
I guess that those have been updated on trunk only.
That's indeed what I did with my packages (including ntp and x11vnc); there is no hurry to push this to the repos that I can see... -- Gaetan
On Wed, Jun 05, 2013 at 08:55:14PM +1000, Gaetan Bisson wrote:
[2013-06-05 12:44:03 +0200] Andrea Scarpino:
On Wednesday 05 June 2013 12:37:54 Lukas Fleischer wrote:
I saw an updated version of bluez in [testing] that no longer contains these files. Can someone please have a look at ntp, tomcat6, x11vnc, couchdb and wesnoth?
I guess that those have been updated on trunk only.
That's indeed what I did with my packages (including ntp and x11vnc); there is no hurry to push this to the repos that I can see...
Well, it is a bit inconsistent to rebuild all but 5 packages in our repositories. Also, I just wanted to make sure that people double-check their packages. If all of these still contain rc.d scripts due to removing them on trunk only, I am fine with that (as long as none of the packages in question are only updated once every decade).
-- Gaetan
On Wed, Jun 05, 2013 at 01:06:59PM +0200, Lukas Fleischer wrote:
On Wed, Jun 05, 2013 at 08:55:14PM +1000, Gaetan Bisson wrote:
[2013-06-05 12:44:03 +0200] Andrea Scarpino:
On Wednesday 05 June 2013 12:37:54 Lukas Fleischer wrote:
I saw an updated version of bluez in [testing] that no longer contains these files. Can someone please have a look at ntp, tomcat6, x11vnc, couchdb and wesnoth?
I guess that those have been updated on trunk only.
That's indeed what I did with my packages (including ntp and x11vnc); there is no hurry to push this to the repos that I can see...
Well, it is a bit inconsistent to rebuild all but 5 packages in our repositories. Also, I just wanted to make sure that people double-check their packages. If all of these still contain rc.d scripts due to removing them on trunk only, I am fine with that (as long as none of the packages in question are only updated once every decade).
Ok, looks like all of them are fine -- apart from couchdb. Sergej: Could you please check that the rc.d script is removed when upgrading to 1.3.0? Maybe you just forgot to rebuild 1.2.2-3 after adding the rc.d change to the PKGBUILD.
-- Gaetan
On 5 June 2013 13:34, Lukas Fleischer
On Wed, Jun 05, 2013 at 01:06:59PM +0200, Lukas Fleischer wrote:
On Wed, Jun 05, 2013 at 08:55:14PM +1000, Gaetan Bisson wrote:
[2013-06-05 12:44:03 +0200] Andrea Scarpino:
On Wednesday 05 June 2013 12:37:54 Lukas Fleischer wrote:
I saw an updated version of bluez in [testing] that no longer contains these files. Can someone please have a look at ntp, tomcat6, x11vnc, couchdb and wesnoth?
I guess that those have been updated on trunk only.
That's indeed what I did with my packages (including ntp and x11vnc); there is no hurry to push this to the repos that I can see...
Well, it is a bit inconsistent to rebuild all but 5 packages in our repositories. Also, I just wanted to make sure that people double-check their packages. If all of these still contain rc.d scripts due to removing them on trunk only, I am fine with that (as long as none of the packages in question are only updated once every decade).
Ok, looks like all of them are fine -- apart from couchdb.
Sergej: Could you please check that the rc.d script is removed when upgrading to 1.3.0? Maybe you just forgot to rebuild 1.2.2-3 after adding the rc.d change to the PKGBUILD.
-- Gaetan
extra/tomcat6 yes: already done in trunk. Will be shipped with next release that should not be long now.
[2013-06-05 13:06:59 +0200] Lukas Fleischer:
On Wed, Jun 05, 2013 at 08:55:14PM +1000, Gaetan Bisson wrote:
I guess that those have been updated on trunk only.
That's indeed what I did with my packages (including ntp and x11vnc); there is no hurry to push this to the repos that I can see...
Well, it is a bit inconsistent to rebuild all but 5 packages in our repositories.
And it is a waste of CPU, bandwidth, and time for everyone to rebuild packages simply to remove a worthless 4kB file. There is no reason not to wait for a proper rebuild to be actually required. As you can see, out of my 12 packages on that TODO list, in just 20 days, only two have not yet had another rebuild opportunity... -- Gaetan
On Wed, Jun 05, 2013 at 11:01:02PM +1000, Gaetan Bisson wrote:
[2013-06-05 13:06:59 +0200] Lukas Fleischer:
On Wed, Jun 05, 2013 at 08:55:14PM +1000, Gaetan Bisson wrote:
I guess that those have been updated on trunk only.
That's indeed what I did with my packages (including ntp and x11vnc); there is no hurry to push this to the repos that I can see...
Well, it is a bit inconsistent to rebuild all but 5 packages in our repositories.
And it is a waste of CPU, bandwidth, and time for everyone to rebuild packages simply to remove a worthless 4kB file. There is no reason not to wait for a proper rebuild to be actually required. As you can see, out of my 12 packages on that TODO list, in just 20 days, only two have not yet had another rebuild opportunity...
So dozens of developers and TUs wasted CPU, bandwidth and time because it was unclear how to do the rebuild/commit. I am not saying that everyone should rebuild their packages. What I am saying is that we could be a bit more consistent and add one simple sentence like * "Only fix in trunk -- no need to rebuild." * "Please rebuild and push to [staging]." * "Please rebuild and move directly to [core]/[extra]/[community]." to every TODO list. I know that is already done for a lot of TODO lists but at lease 4 out of the 10 latest lists to not include such information. Even in simple cases (such as SONAME bumps) where it is pretty obvious what to do, it might help new Trusted Users and developers who are unfamiliar with how we do rebuilds. And it avoids inconsistency in cases like this one. It is just one sentence. Literally takes 5 seconds to add it.
-- Gaetan
participants (4)
-
Andrea Scarpino
-
Gaetan Bisson
-
Guillaume Alaux
-
Lukas Fleischer