Discussion:
next drop candidates
Stephan Kulow
2014-07-21 09:41:43 UTC
Permalink
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
--
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org
Marcus Meissner
2014-07-22 08:20:22 UTC
Permalink
Post by Stephan Kulow
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
--
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org
Robert Schweikert
2014-07-28 14:50:08 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
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
***@suse.com
***@ca.ibm.com
781-464-8147
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJT1mMgAAoJEE4FgL32d2UkXGkH/1IJ3OIzMIaqcwSRZoZjKeSx
RNqQzknZP6hlInVsCACSl1H9GU3sWGHnT3rWVdDtn4AS6FthSpvkGISMS70EYRed
IMRofTpQAWG5qvjwpxYIEmdN8+8DBWzGGP+ji6UTJKGTlm1FGINOeh8bMeUWgFDS
xQGo/tXKFoxQeUivc2n6z68BsXvPQ4leTv+zNHsEHPirZ3UmLr+wVdkLMahr1Mmg
rz4L0Q/pzxKEVbSyvdFcw7TLbZijtHbjMMn7NX7cjyWfUfBB8kXjPiHn/6hBOcW3
wD9BS+bgz5jNTYE7L3T1MXVxRQWiiD5CRbXsyA1RGWn66666C0MOlqYhViC7Gr4=
=fbXr
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org
Stephan Kulow
2014-07-28 16:16:08 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Post by Robert Schweikert
Hi,
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

***@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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlPWd0gACgkQwFSBhlBjoJagygCeN/niegZhV1guAoWzxoOWkYoe
XCgAnjavJjllmnfYenTzCeLRvzuZBkhi
=WJbP
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org
Robert Schweikert
2014-07-29 17:59:13 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Post by Stephan Kulow
Post by Robert Schweikert
Hi,
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
***@suse.com
***@ca.ibm.com
781-464-8147
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJT1+DxAAoJEE4FgL32d2UkSyMIAIH+YvE0ApnS7bhVc6/1JAAV
pmUyjnuil/R4nC9shdDLLBibjGT2EqolnLXLJkaq5zd5ahov0oX/RXOf+gkyAw/F
RZPRwZyR96STAq/+r4u/gD30vCMXrAg2qN63IWcqoxCv7EgD9KMRP0YevFwBDtuB
f7oI8XKThPXVVc6AgBmp0YjqVsvLSvlbB5dTUzhHizLrwJVAFqU6/TpFtQUZoFPF
6k4KbPUH22Ak5z/zVGVmX/t1dlkVc+acG9+cSZknMMkh7dMIh9TQl/A80RUhDf1B
Oy1HyHpR6k0fXcZ3PjnzGr7/UgdtJeYkSRBv46qNF4LTuoWg65eTIocTLW9Pc+o=
=tpfW
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org
Shawn W Dunn
2014-07-28 23:40:04 UTC
Permalink
Post by Robert Schweikert
Hi,
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.
Stephan Kulow
2014-07-29 05:21:50 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Post by 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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlPXL24ACgkQwFSBhlBjoJa/jwCgqVIDHNu3TSCdJ0MkA7407UuP
yfQAn2ht56jxPsvx770kSKUzyu1lLvyC
=Uijq
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org
Shawn W Dunn
2014-07-29 05:35:22 UTC
Permalink
Post by Stephan Kulow
Post by 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.
--
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org
Stephan Kulow
2014-07-29 07:58:21 UTC
Permalink
Post by Shawn W Dunn
Post by Stephan Kulow
Post by 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
--
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org
Shawn W Dunn
2014-07-29 13:28:59 UTC
Permalink
Post by Stephan Kulow
Post by Shawn W Dunn
Post by Stephan Kulow
Post by 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 =]
--
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org
Continue reading on narkive:
Loading...