Hi,
mtr fails for 113 days jpilot fails for 99 days python-hacking fails for 98 days
I'm also sending another round of reminder mails.
Greetings, Stephan
On Mon, Jul 21, 2014 at 11:41:43AM +0200, Stephan Kulow wrote:
Hi,
mtr fails for 113 days jpilot fails for 99 days python-hacking fails for 98 days
I'm also sending another round of reminder mails.
I fixed mtr.
Ciao, Marcus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
On 07/21/2014 05:41 AM, Stephan Kulow wrote:
Hi,
mtr fails for 113 days jpilot fails for 99 days python-hacking fails for 98 days
I'm also sending another round of reminder mails.
Greetings, Stephan
Wasn't there some work going on to "fix" and or replace hermes?
I think the crux of this type of problem is that maintainers do not get notified if their packages fail in factory. Thus, things fail forever until "fix it or else" e-mails are necessary.
A gentler, probably more effective, system would be to notify package maintainers when their package fails in factory. Maintainers can then take appropriate action in a timely fashion.
Packages in factory that have no maintainer should go away. That will partially solve the "e-mail to nowhere" problem. For those maintainers that no longer care the notification can serve as a reminder to offer the packages up for another maintainer to take over.
Later, Robert
- -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 28.07.2014 16:50, schrieb Robert Schweikert:
Hi,
On 07/21/2014 05:41 AM, Stephan Kulow wrote:
Hi,
mtr fails for 113 days jpilot fails for 99 days python-hacking fails for 98 days
I'm also sending another round of reminder mails.
Greetings, Stephan
Wasn't there some work going on to "fix" and or replace hermes?
I think the crux of this type of problem is that maintainers do not get notified if their packages fail in factory. Thus, things fail forever until "fix it or else" e-mails are necessary.
A gentler, probably more effective, system would be to notify package maintainers when their package fails in factory. Maintainers can then take appropriate action in a timely fashion.
python-hacking was part of several reminders - as was jpilot. And if you wanted, you can enable notifications for failed packages in OBS you maintain.
Greetings, Stephan
coolo@gertrude#checker>grep -rl python-hacking reports-201* reports-2013-10-31/aspiers.txt reports-2013-10-31/bmwiedemann.txt reports-2013-10-31/dirkmueller.txt reports-2013-10-31/iartarisi.txt reports-2013-10-31/jdsn.txt reports-2013-10-31/jfehlig.txt reports-2013-10-31/-miska-.txt reports-2013-10-31/mvidner.txt reports-2013-10-31/rhafer.txt reports-2013-10-31/saschpe.txt reports-2013-10-31/scarabeus_factory.txt reports-2013-10-31/tserong.txt reports-2013-10-31/vuntz.txt reports-2014-01-29/-miska-.txt reports-2014-01-29/aspiers.txt reports-2014-01-29/bmwiedemann.txt reports-2014-01-29/dirkmueller.txt reports-2014-01-29/iartarisi.txt reports-2014-01-29/jdsn.txt reports-2014-01-29/jfehlig.txt reports-2014-01-29/mvidner.txt reports-2014-01-29/rhafer.txt reports-2014-01-29/saschpe.txt reports-2014-01-29/scarabeus_factory.txt reports-2014-01-29/tserong.txt reports-2014-01-29/vuntz.txt reports-2014-03-03/aspiers.txt reports-2014-03-03/bmwiedemann.txt reports-2014-03-03/dirkmueller.txt reports-2014-03-03/iartarisi.txt reports-2014-03-03/jdsn.txt reports-2014-03-03/jfehlig.txt reports-2014-03-03/jsuchome.txt reports-2014-03-03/-miska-.txt reports-2014-03-03/rhafer.txt reports-2014-03-03/saschpe.txt reports-2014-03-03/scarabeus_factory.txt reports-2014-03-03/tserong.txt reports-2014-03-03/vuntz.txt reports-2014-05-12/aspiers.txt reports-2014-05-12/bmwiedemann.txt reports-2014-05-12/dirkmueller.txt reports-2014-05-12/iartarisi.txt reports-2014-05-12/jdsn.txt reports-2014-05-12/jfehlig.txt reports-2014-05-12/jsuchome.txt reports-2014-05-12/-miska-.txt reports-2014-05-12/rhafer.txt reports-2014-05-12/saschpe.txt reports-2014-05-12/scarabeus_factory.txt reports-2014-05-12/tboerger.txt reports-2014-05-12/tserong.txt reports-2014-05-12/vuntz.txt reports-2014-06-25/aspiers.txt reports-2014-06-25/bmwiedemann.txt reports-2014-06-25/dirkmueller.txt reports-2014-06-25/iartarisi.txt reports-2014-06-25/jdsn.txt reports-2014-06-25/jfehlig.txt reports-2014-06-25/jsuchome.txt reports-2014-06-25/-miska-.txt reports-2014-06-25/rhafer.txt reports-2014-06-25/saschpe.txt reports-2014-06-25/scarabeus_factory.txt reports-2014-06-25/tboerger.txt reports-2014-06-25/tserong.txt reports-2014-06-25/vuntz.txt reports-2014-07-21/aspiers.txt reports-2014-07-21/bmwiedemann.txt reports-2014-07-21/dirkmueller.txt reports-2014-07-21/iartarisi.txt reports-2014-07-21/jdsn.txt reports-2014-07-21/jfehlig.txt reports-2014-07-21/jsuchome.txt reports-2014-07-21/-miska-.txt reports-2014-07-21/rhafer.txt reports-2014-07-21/saschpe.txt reports-2014-07-21/scarabeus_factory.txt reports-2014-07-21/tboerger.txt reports-2014-07-21/tserong.txt reports-2014-07-21/vuntz.txt
- -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn.
On Monday 28 July 2014 10:50:08 Robert Schweikert wrote:
Hi,
On 07/21/2014 05:41 AM, Stephan Kulow wrote:
Hi,
mtr fails for 113 days jpilot fails for 99 days python-hacking fails for 98 days
I'm also sending another round of reminder mails.
Greetings, Stephan
Wasn't there some work going on to "fix" and or replace hermes?
I think the crux of this type of problem is that maintainers do not get notified if their packages fail in factory. Thus, things fail forever until "fix it or else" e-mails are necessary.
A gentler, probably more effective, system would be to notify package maintainers when their package fails in factory. Maintainers can then take appropriate action in a timely fashion.
Packages in factory that have no maintainer should go away. That will partially solve the "e-mail to nowhere" problem. For those maintainers that no longer care the notification can serve as a reminder to offer the packages up for another maintainer to take over.
Later, Robert
I personally wouldn't be opposed to seeing some sort of list, if possible, of packages in need of maintainers. at least at present, I'm not working a day job, so I've got some extra time.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 29.07.2014 01:40, schrieb Shawn W Dunn:
I personally wouldn't be opposed to seeing some sort of list, if possible, of packages in need of maintainers. at least at present, I'm not working a day job, so I've got some extra time.
Then don't become maintainer, but fix the build failures we see or do version updates. The list is on http://s.kulow.org/factory-status
Greetings, Stephan
- -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn.
On Tuesday 29 July 2014 07:21:50 Stephan Kulow wrote:
Am 29.07.2014 01:40, schrieb Shawn W Dunn:
I personally wouldn't be opposed to seeing some sort of list, if possible, of packages in need of maintainers. at least at present, I'm not working a day job, so I've got some extra time.
Then don't become maintainer, but fix the build failures we see or do version updates. The list is on http://s.kulow.org/factory-status
Greetings, Stephan
--
Excellent, will do.
On 29.07.2014 07:35, Shawn W Dunn wrote:
On Tuesday 29 July 2014 07:21:50 Stephan Kulow wrote:
Am 29.07.2014 01:40, schrieb Shawn W Dunn:
I personally wouldn't be opposed to seeing some sort of list, if possible, of packages in need of maintainers. at least at present, I'm not working a day job, so I've got some extra time.
Then don't become maintainer, but fix the build failures we see or do version updates. The list is on http://s.kulow.org/factory-status
Greetings, Stephan
--
Excellent, will do.
Just so this is not misunderstood: if you see a package you care for and it appears outdated, feel free to grab maintainership - there is a button on the webui for that :)
But don't do it because you have free time *right now* - maintainership means commitment into the future.
Greetings, Stephan
On Tuesday 29 July 2014 09:58:21 Stephan Kulow wrote:
On 29.07.2014 07:35, Shawn W Dunn wrote:
On Tuesday 29 July 2014 07:21:50 Stephan Kulow wrote:
Am 29.07.2014 01:40, schrieb Shawn W Dunn:
I personally wouldn't be opposed to seeing some sort of list, if possible, of packages in need of maintainers. at least at present, I'm not working a day job, so I've got some extra time.
Then don't become maintainer, but fix the build failures we see or do version updates. The list is on http://s.kulow.org/factory-status
Greetings, Stephan
--
Excellent, will do.
Just so this is not misunderstood: if you see a package you care for and it appears outdated, feel free to grab maintainership - there is a button on the webui for that :)
But don't do it because you have free time *right now* - maintainership means commitment into the future.
Greetings, Stephan
Aye, That was why I wanted to know what was unmaintained, as I have interest in maintaining certain things, and not others. Much like anybody else =]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/28/2014 12:16 PM, Stephan Kulow wrote:
Am 28.07.2014 16:50, schrieb Robert Schweikert:
Hi,
On 07/21/2014 05:41 AM, Stephan Kulow wrote:
Hi,
mtr fails for 113 days jpilot fails for 99 days python-hacking fails for 98 days
I'm also sending another round of reminder mails.
Greetings, Stephan
Wasn't there some work going on to "fix" and or replace hermes?
I think the crux of this type of problem is that maintainers do not get notified if their packages fail in factory. Thus, things fail forever until "fix it or else" e-mails are necessary.
A gentler, probably more effective, system would be to notify package maintainers when their package fails in factory. Maintainers can then take appropriate action in a timely fashion.
python-hacking was part of several reminders - as was jpilot. And if you wanted, you can enable notifications for failed packages in OBS you maintain.
IMHO notifications for failing builds in Factory should not be opt in. If the build fails in factory the maintainer gets a message. If maintainers choose not to get messages about build failing in a devel project that's one thing, but for factory there should not be an option. It is after all our shiny new rolling release.
Later, Robert
- -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147
-
Marcus Meissner -
Robert Schweikert -
Shawn W Dunn -
Stephan Kulow