[opensuse-packaging] RFC: reminder mails for factory work

older
[opensuse-packaging] New review...

Stephan Kulow

3 Feb 2012 3 Feb '12

09:55

Hi, During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages. Too many people complain to me that they have no idea that their packages fail in factory or that they haven't seen the mail about the request X being declined, etc. So I collect the infos for each individual and send out reminders - my current idea is to send it out e.g every tuesday, but I can send it more often or less often as people say so. As an example I attach the mail as I would send it right now to Richard (because it has all interesting things and still isn't too long and I know he reads this list :) I would like to hear from you suggestions if this is useful to you and/or if you would like to see changes to make it more useful. I only send mail to the package maintainer as defined by the OBS flags and only if there is no maintainer set, I send mail to the project maintainers. This leads to the rather sad state, that a lot of people will get mail about packages they have no relation to. This is not a problem of the script, but a problem of some of the devel projects ;( So one thing to make this more useful (or the whole reporting) would be to set all people that have touched a specific package in the past also as package maintainers and either leave or cleanup the project maintainers. But that's a general topic that we should discuss instead of people starting to filter these mails. That's basically my main concern: I only want to send out mails that are interesting to the people reading it - even if it's auto generated content. So if the content is too long or too uninteresting, we need to change it. More examples of reminder mails you can find at http://stephan.kulow.org/reminders/ Greetings, Stephan

Attachments:

rguenther.bat (text/plain — 2.0 KB)

Show replies by date

Richard Guenther

3 Feb 3 Feb

10:51

On Fri, 3 Feb 2012, Stephan Kulow wrote:

...

Hi,

During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Too many people complain to me that they have no idea that their packages fail in factory or that they haven't seen the mail about the request X being declined, etc.

So I collect the infos for each individual and send out reminders - my current idea is to send it out e.g every tuesday, but I can send it more often or less often as people say so.

As an example I attach the mail as I would send it right now to Richard (because it has all interesting things and still isn't too long and I know he reads this list :)

I would like to hear from you suggestions if this is useful to you and/or if you would like to see changes to make it more useful.

I only send mail to the package maintainer as defined by the OBS flags and only if there is no maintainer set, I send mail to the project maintainers. This leads to the rather sad state, that a lot of people will get mail about packages they have no relation to. This is not a problem of the script, but a problem of some of the devel projects ;(

So one thing to make this more useful (or the whole reporting) would be to set all people that have touched a specific package in the past also as package maintainers and either leave or cleanup the project maintainers. But that's a general topic that we should discuss instead of people starting to filter these mails.

That's basically my main concern: I only want to send out mails that are interesting to the people reading it - even if it's auto generated content. So if the content is too long or too uninteresting, we need to change it.

A single mail once a week would be ok I think. But - for the unsubmitted changes part, can you include the .changes file difference (of one .spec file only please ...)? Richard. -- Richard Guenther SUSE / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer

Stephan Kulow

10:57

On 03.02.2012 11:51, Richard Guenther wrote:

...

On Fri, 3 Feb 2012, Stephan Kulow wrote:

...
Hi,

During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Too many people complain to me that they have no idea that their packages fail in factory or that they haven't seen the mail about the request X being declined, etc.

So I collect the infos for each individual and send out reminders - my current idea is to send it out e.g every tuesday, but I can send it more often or less often as people say so.

As an example I attach the mail as I would send it right now to Richard (because it has all interesting things and still isn't too long and I know he reads this list :)

I would like to hear from you suggestions if this is useful to you and/or if you would like to see changes to make it more useful.

I only send mail to the package maintainer as defined by the OBS flags and only if there is no maintainer set, I send mail to the project maintainers. This leads to the rather sad state, that a lot of people will get mail about packages they have no relation to. This is not a problem of the script, but a problem of some of the devel projects ;(

So one thing to make this more useful (or the whole reporting) would be to set all people that have touched a specific package in the past also as package maintainers and either leave or cleanup the project maintainers. But that's a general topic that we should discuss instead of people starting to filter these mails.

That's basically my main concern: I only want to send out mails that are interesting to the people reading it - even if it's auto generated content. So if the content is too long or too uninteresting, we need to change it.

A single mail once a week would be ok I think. But - for the unsubmitted changes part, can you include the .changes file difference (of one .spec file only please ...)?

The full text in the mail? That will hide the real message I'm afraid because that's potentionally a lot of text - I added the link to the diff for that. But I can do that - I'm even open to implement different strategies and send different mails to different users. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Christian Boltz

12:44

Hello, Am Freitag, 3. Februar 2012 schrieb Stephan Kulow:

...

During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

I like the idea, and the frequency (once a week) also sounds good. However, I'd propose to change the layout of the mail. The top-level sorting by project is good, but the second level sorting should be by reason IMHO. This would also make the mail shorter without loosing information. I'd also include the "new upstream version" in each project instead of having it at the end of the mail for all packages. I'll give you an example from your TODO list http://stephan.kulow.org/reminders/coolo (limited to the KDE:Distro:Factory section) --------------------------------------------------------------------- Project KDE:Distro:Factory koffice2 fails for 3 months (undefined reference to `__glewBegin'): http://s.kulow.org/bf-koffice2 Declined submit requests - please check the reason: kalgebra - https://build.opensuse.org/request/show/101714 koffice2 - https://build.opensuse.org/request/show/101754 libmsn - https://build.opensuse.org/request/show/101772 okular - https://build.opensuse.org/request/show/101777 Packages with pending submit requests: foobar from home:foo:branches:foo - https://build.opensuse.org/request/show/123456 Packages with unsubmitted changes: amarok - http://s.kulow.org/rd-amarok kdepimlibs4 - http://s.kulow.org/rd-kdepimlibs4 kdesdk4 - http://s.kulow.org/rd-kdesdk4 phonon - http://s.kulow.org/rd-phonon Packages with new upstream versions: ktorrent - packaged: 4.1.3, upstream: 4.2rc1 --------------------------------------------------------------------- Some detailed comments: - build failures should have one section per package because they include technical details ("undefined reference to ...") - everything without technical details should be grouped by reason - for "new upstream versions", please include the currently packaged version - the sorting of the reasons should be by severity - first build failures, then declined SRs, then pending (incoming) SRs, then unsubmitted changes and finally new upstream versions It would also be nice to have a similar page ("my TODO list") in the buildservice (and a link to it in the mail) so that people could open one browser window and then middle-click all the links to open new tabs. I'd prefer that over 10 browser windows opened from my mail client ;-) Regards, Christian Boltz -- Vielleicht bei Leuten, die ihre Linux-Distri auf dem Hamburger Fisch- markt bei Kamäleon-Paule aus Nürnberg kaufen ("So, und jetz machen wir hier 'ne schöne Tüte Minimalinstallation für 90 Euro! Komm ma her hier, Muttern, hier gibt es Minimal-Linux! 90 Euro! Zu teuer? Denn pack ich dich noch'n Webserver dabei! Zack! Rin da! Und noch ne grafische Oberfläche, immer rin in die Tüte! Zack! Hier! Schriften! TrueType! PostScript! Immer rein die Box und rauf auf die Platte, hier is Suse, hier gibt reichlich, ran an den Speck und rauf auf die Mutti! Hier! Gnome! KDE! Beides mit rauf! Zack! Peng! Uuuuuund alles für 90 Euro, alles reichlich...") :-) [Ratti in fontlinge-devel] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Robert Schweikert

13:33

On 02/03/2012 07:44 AM, Christian Boltz wrote:

...

Hello,

Am Freitag, 3. Februar 2012 schrieb Stephan Kulow:

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

I like the idea, and the frequency (once a week) also sounds good.

Stephan, thanks for doing this. Once a week is a good frequency, IMHO. However, for build failures I think an immediate notification is in order. After all we want factory to build cleanly all the time as much as possible and not have broken packages for a week or more.

...

<snip>

...

It would also be nice to have a similar page ("my TODO list") in the buildservice (and a link to it in the mail) so that people could open one browser window and then middle-click all the links to open new tabs. I'd prefer that over 10 browser windows opened from my mail client ;-)

Yes, a web page containing the info in the mail would be great. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Marcus Meissner

13:42

On Fri, Feb 03, 2012 at 08:33:30AM -0500, Robert Schweikert wrote:

...

On 02/03/2012 07:44 AM, Christian Boltz wrote:

...
Hello,

Am Freitag, 3. Februar 2012 schrieb Stephan Kulow:

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

I like the idea, and the frequency (once a week) also sounds good.

Stephan, thanks for doing this. Once a week is a good frequency, IMHO. However, for build failures I think an immediate notification is in order. After all we want factory to build cleanly all the time as much as possible and not have broken packages for a week or more.

hermes can send immediate mails on that, but this is a neverending storm of e-mails :( Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Robert Schweikert

13:58

On 02/03/2012 08:42 AM, Marcus Meissner wrote:

...

On Fri, Feb 03, 2012 at 08:33:30AM -0500, Robert Schweikert wrote:

...
On 02/03/2012 07:44 AM, Christian Boltz wrote:

...
Hello,

Am Freitag, 3. Februar 2012 schrieb Stephan Kulow:

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

I like the idea, and the frequency (once a week) also sounds good.

Stephan, thanks for doing this. Once a week is a good frequency, IMHO. However, for build failures I think an immediate notification is in order. After all we want factory to build cleanly all the time as much as possible and not have broken packages for a week or more.

hermes can send immediate mails on that, but this is a neverending storm of e-mails :(

Well hermes is broken (731591), if we can get a reliable implementation that provides build failure messages I am all for it, even if I get 10 or more day. -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Michal Vyskocil

8 Feb 8 Feb

08:22

On Fri, Feb 03, 2012 at 02:42:42PM +0100, Marcus Meissner wrote:

...

On Fri, Feb 03, 2012 at 08:33:30AM -0500, Robert Schweikert wrote:

...
On 02/03/2012 07:44 AM, Christian Boltz wrote:

...
Hello,

Am Freitag, 3. Februar 2012 schrieb Stephan Kulow:

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

I like the idea, and the frequency (once a week) also sounds good.

Stephan, thanks for doing this. Once a week is a good frequency, IMHO. However, for build failures I think an immediate notification is in order. After all we want factory to build cleanly all the time as much as possible and not have broken packages for a week or more.

hermes can send immediate mails on that, but this is a neverending storm of e-mails :(

The main question is - does anyone use hermes? It's very sad, but with the ui it have/had I simply turned all emails off, because I was never able to realize how to configure it in a way, which will meet my needs. IOW with this great script, do we really need hermes nowadays? Especially when Klaas have joined ownCloud? Regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Stephan Kulow

08:28

On 08.02.2012 09:22, Michal Vyskocil wrote:

...

On Fri, Feb 03, 2012 at 02:42:42PM +0100, Marcus Meissner wrote:

...
On Fri, Feb 03, 2012 at 08:33:30AM -0500, Robert Schweikert wrote:

...
On 02/03/2012 07:44 AM, Christian Boltz wrote:

...
Hello,

Am Freitag, 3. Februar 2012 schrieb Stephan Kulow:

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

I like the idea, and the frequency (once a week) also sounds good.

Stephan, thanks for doing this. Once a week is a good frequency, IMHO. However, for build failures I think an immediate notification is in order. After all we want factory to build cleanly all the time as much as possible and not have broken packages for a week or more.

hermes can send immediate mails on that, but this is a neverending storm of e-mails :(

The main question is - does anyone use hermes? It's very sad, but with the ui it have/had I simply turned all emails off, because I was never able to realize how to configure it in a way, which will meet my needs.

IOW with this great script, do we really need hermes nowadays? Especially when Klaas have joined ownCloud?

That build failures happen often is hardly hermes's fault - and many users use digests for those. And digests are one of hermes' features you don't get otherwise. Hermes's interface is indeed very strange and I always happen to end up in the so called expert interface, there it's at least understandable what happens. My script is not a replacement for hermes, for one it will only summarize work related to factory. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Claudio Freire

3 Feb 3 Feb

14:43

On Fri, Feb 3, 2012 at 9:44 AM, Christian Boltz wrote:

...

Am Freitag, 3. Februar 2012 schrieb Stephan Kulow:

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

I like the idea, and the frequency (once a week) also sounds good.

However, I'd propose to change the layout of the mail.

The top-level sorting by project is good, but the second level sorting should be by reason IMHO. This would also make the mail shorter without loosing information. I'd also include the "new upstream version" in each project instead of having it at the end of the mail for all packages.

I agree. This is a very good idea, especially for build failures. Lots of times things change in factory and make my projects fail, but I don't even realize until very much later when I happen to log in to OBS for some other reason. And I agree, the second-level sorting should be reason. It reads a lot better. And the links are a must too. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Stephan Kulow

4 Feb 4 Feb

11:11

Am Fri 03 Feb 2012 01:44:47 PM CET schrieb Christian Boltz :

...

Hello,

Am Freitag, 3. Februar 2012 schrieb Stephan Kulow:

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

I like the idea, and the frequency (once a week) also sounds good.

However, I'd propose to change the layout of the mail.

Thanks for your feedback, I updated the script to take your suggestions into account: http://stephan.kulow.org/reminders/coolo - I only updated mine for now for you to recheck :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Christian Boltz

17:11

Hello, Am Samstag, 4. Februar 2012 schrieb Stephan Kulow:

...

Thanks for your feedback, I updated the script to take your suggestions into account: http://stephan.kulow.org/reminders/coolo - I only updated mine for now for you to recheck :)

Looks much better :-) One thing remains - the "Other new requests" section. I'm slightly confused because some requests are sorted into the projects' sections, but some are listed in the "Other new requests" section - why? If there isn't a good reason to keep them separate, you should include them in each project's section. Oh, and you could group the requests like this: (note the "->" instead of "to" which makes reading easier IMHO) Submit requests: home:olh:branches:system:install:head/hwinfo -> system:install:head https://build.opensuse.org/request/show/87584 home:olh:branches:system:install:head/installation-images -> system:install:head https://build.opensuse.org/request/show/89243 home:jreidinger:branches:openSUSE:Tools/obs-service-verify_file -> openSUSE:Tools https://build.opensuse.org/request/show/92988 Delete requests: openSUSE:Factory/kdeutils4 https://build.opensuse.org/request/show/101869 openSUSE:Factory/tin - https://build.opensuse.org/request/show/102179 After implementing this, you should do the most important change: make your TODO list shorter. If there's only one or two packages on your list, the formatting will become nearly irrelevant ;-)) Regards, Christian Boltz -- Das hier ist eine Anfängerliste. Ich will Dir auch erklären warum: Den 'Linux Profi' gibt es IMHO nicht. [Bernd Obermayr in suse-linux] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Stephan Kulow

18:21

Christian Boltz schrieb:

...

Hello,

Am Samstag, 4. Februar 2012 schrieb Stephan Kulow:

...
Thanks for your feedback, I updated the script to take your suggestions into account: http://stephan.kulow.org/reminders/coolo - I only updated mine for now for you to recheck :)

Looks much better :-)

One thing remains - the "Other new requests" section. I'm slightly confused because some requests are sorted into the projects' sections, but some are listed in the "Other new requests" section - why? If there isn't a good reason to keep them separate, you should include them in each project's section.

Oh, and you could group the requests like this: (note the "->" instead of "to" which makes reading easier IMHO)

Submit requests: home:olh:branches:system:install:head/hwinfo -> system:install:head https://build.opensuse.org/request/show/87584 home:olh:branches:system:install:head/installation-images -> system:install:head https://build.opensuse.org/request/show/89243 home:jreidinger:branches:openSUSE:Tools/obs-service-verify_file -> openSUSE:Tools https://build.opensuse.org/request/show/92988

Delete requests: openSUSE:Factory/kdeutils4 https://build.opensuse.org/request/show/101869 openSUSE:Factory/tin - https://build.opensuse.org/request/show/102179

After implementing this, you should do the most important change: make your TODO list shorter. If there's only one or two packages on your list, the formatting will become nearly irrelevant ;-))

Regards,

Christian Boltz -- Das hier ist eine Anfängerliste. Ich will Dir auch erklären warum: Den 'Linux Profi' gibt es IMHO nicht. [Bernd Obermayr in suse-linux]

-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Hi, The requests in the project list are for packages maintained by you in factory. The others might or might not be for your attention, I only include them because the package maintainership is not well defined. Greetings, Stephan -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Ralf Lang

6 Feb 6 Feb

10:43

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 03.02.2012 10:55, schrieb Stephan Kulow:

...

Hi,

During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

I like this feature as described. With 100+ packages in the pipeline, this helps me keep up. It would be cool if I could also see the current (or day-current) state as plain text file under some http(s) URL instead of mails. - -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8vrt4ACgkQCs1dsHJ/X7DK7QCg8y7TIAV2ltWCyOwRRghN4Tia zrkAnjeFo8gGzuz3FhnNQApOxxTHa0ah =mZk+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Johannes Meixner

8 Feb 8 Feb

08:41

Hello Stephan, On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...

During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much! Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Vitezslav Cizek

10:07

Hi, * V Středa 8. únor 2012, 09:41:19 [CET] Johannes Meixner napsal:

...

Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much!

I like it too. However, the script has problems with identifying versions numbers. From the script's output: Packages with new upstream versions: perl-Authen-SASL - packaged: 2.15, upstream: 2.1401 perl-Convert-UUlib - packaged: 1.4, upstream: 1.34 These versions aren't newer. -- Vita Cizek

Stephan Kulow

10:09

On 08.02.2012 11:07, Vitezslav Cizek wrote:

...

Hi, * V Středa 8. únor 2012, 09:41:19 [CET] Johannes Meixner napsal:

...
Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much!

I like it too.

However, the script has problems with identifying versions numbers. From the script's output:

Packages with new upstream versions: perl-Authen-SASL - packaged: 2.15, upstream: 2.1401 perl-Convert-UUlib - packaged: 1.4, upstream: 1.34

These versions aren't newer.

Hmm, that's not my script. I just report what the "cpan digger" puts in the attribute. We might improve *that* script though. Greetings, Stephan -- To be trusted is a greater compliment than to be loved. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Marcus Meissner

10:29

On Wed, Feb 08, 2012 at 11:09:13AM +0100, Stephan Kulow wrote:

...

On 08.02.2012 11:07, Vitezslav Cizek wrote:

...
Hi, * V Středa 8. únor 2012, 09:41:19 [CET] Johannes Meixner napsal:

...
Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much!

I like it too.

However, the script has problems with identifying versions numbers. From the script's output:

Packages with new upstream versions: perl-Authen-SASL - packaged: 2.15, upstream: 2.1401 perl-Convert-UUlib - packaged: 1.4, upstream: 1.34

These versions aren't newer.

Hmm, that's not my script. I just report what the "cpan digger" puts in the attribute. We might improve *that* script though.

It is really hard to differentiate that these versions are not numbers though. Or are there specific rules? Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Michael Schroeder

10:33

On Wed, Feb 08, 2012 at 11:29:53AM +0100, Marcus Meissner wrote:

...

It is really hard to differentiate that these versions are not numbers though. Or are there specific rules?

Rule: Perl uses floating point (more or less) ;) M. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Stephan Kulow

10:39

On 08.02.2012 11:29, Marcus Meissner wrote:

...

On Wed, Feb 08, 2012 at 11:09:13AM +0100, Stephan Kulow wrote:

...
On 08.02.2012 11:07, Vitezslav Cizek wrote:

...
Hi, * V Středa 8. únor 2012, 09:41:19 [CET] Johannes Meixner napsal:

...
Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much!

I like it too.

However, the script has problems with identifying versions numbers. From the script's output:

Packages with new upstream versions: perl-Authen-SASL - packaged: 2.15, upstream: 2.1401 perl-Convert-UUlib - packaged: 1.4, upstream: 1.34

These versions aren't newer.

Hmm, that's not my script. I just report what the "cpan digger" puts in the attribute. We might improve *that* script though.

It is really hard to differentiate that these versions are not numbers though. Or are there specific rules?

The rule is simple - if this outputs 1 the version is higher perl -e 'use version; print version->parse("2.15") <=> version->parse("2.1401"); But for cpan, all versions not in the modules file should not be packaged and that is 2.15, so I would just scratch that attribute. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Richard Guenther

11:10

On Wed, 8 Feb 2012, Vitezslav Cizek wrote:

...

Hi, * V Středa 8. únor 2012, 09:41:19 [CET] Johannes Meixner napsal:

...
Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much!

I like it too.

However, the script has problems with identifying versions numbers. From the script's output:

Packages with new upstream versions: perl-Authen-SASL - packaged: 2.15, upstream: 2.1401 perl-Convert-UUlib - packaged: 1.4, upstream: 1.34

These versions aren't newer.

Yeah, for gcc46 it says we package 4.6 and upstream is 4.6.1 (we package the 4.6 branch, currently at 4.6.3 and upstream is 4.6.2, Version is 4.6.2_20111212) Richard.

Stephan Kulow

11:13

On 08.02.2012 12:10, Richard Guenther wrote:

...

...
These versions aren't newer.

Yeah, for gcc46 it says we package 4.6 and upstream is 4.6.1 (we package the 4.6 branch, currently at 4.6.3 and upstream is 4.6.2, Version is 4.6.2_20111212)

You're mixing two things up. It talks about "gcc" and in all fairness, you can't expect our scripts to understand that our gcc package has little to do with the upstream gcc [which is packaged in gcc46] :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Petr Uzel

12:17

On Wed, Feb 08, 2012 at 09:41:19AM +0100, Johannes Meixner wrote:

...

Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much!

Same here - good job, Coolo! Petr -- Petr Uzel IRC: ptr_uzl @ freenode

Mariusz Fik

16:32

Dnia środa, 8 lutego 2012 09:41:19 Johannes Meixner pisze:

...

Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much! Me too ;)

What about dropping info about Contrib since it's over? -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

Peter Linnell

9 Feb 9 Feb

02:29

On 02/08/2012 08:32 AM, Mariusz Fik wrote:

...

Dnia środa, 8 lutego 2012 09:41:19 Johannes Meixner pisze:

...
Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much! Me too ;)

What about dropping info about Contrib since it's over?

well not everything is migrated into Factory, so please no. Thanks, Peter -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

todd rme

07:07

On Thu, Feb 9, 2012 at 3:29 AM, Peter Linnell wrote:

...

On 02/08/2012 08:32 AM, Mariusz Fik wrote:

...
Dnia środa, 8 lutego 2012 09:41:19 Johannes Meixner pisze:

...
Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much!

Me too ;)

What about dropping info about Contrib since it's over?

well not everything is migrated into Factory, so please no.

Thanks, Peter

What about the opposite, sending reminders to the package maintainers to move the packages out? Or is that already done? -Todd -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Stephan Kulow

09:51

On 08.02.2012 17:32, Mariusz Fik wrote:

...

Dnia środa, 8 lutego 2012 09:41:19 Johannes Meixner pisze:

...
Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much! Me too ;)

What about dropping info about Contrib since it's over?

The info about Contrib is dropped from the list as soon as you revoke your submit requests to it. declined requests are still hot and so I include them - if you do no longer care for Contrib, revoke them. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Greg Freemyer

8 Feb 8 Feb

17:58

On Wed, Feb 8, 2012 at 3:41 AM, Johannes Meixner wrote:

...

Hello Stephan,

On Feb 3 10:55 Stephan Kulow wrote (excerpt):

...
During the last week I worked on a project that I have on my TODO list for just too long: sending out mails about the state of factory packages.

Today I got the first of those mails and I like it very much!

I also just got my first one. It should be helpful, but I'd like to more changes. 1) Please add a couple clear identifiers at the top and bottom of the boilerplate. ie. ====> Start of boilerplate <==== existing intro text ====> End of boilerplate <==== That way, it is easy to slide right past all the intro stuff which will get boring to read in a hurry. 2) At least for me I'd like to have a list of what I have in factory. My list is only 15 or so packages long, but for others doing this might not be reasonable. Anyway speaking as a packager with only a handful of packages, I'd like to see the full list added to the email. ie. You have the following packages in factory for which you are the maintainer: package1, package2, package3, .... -- That's it and thanks again for the new functionality. Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Stephan Kulow

19:19

Am 08.02.2012 18:58, schrieb Greg Freemyer:

...

ie. You have the following packages in factory for which you are the maintainer:

package1, package2, package3, ....

If you can help me understand what this is good for, I'd add it. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Greg Freemyer

20:20

On Wed, Feb 8, 2012 at 2:19 PM, Stephan Kulow wrote:

...

Am 08.02.2012 18:58, schrieb Greg Freemyer:

...
ie. You have the following packages in factory for which you are the maintainer:

package1, package2, package3, ....

If you can help me understand what this is good for, I'd add it.

I currently have about 30 packages in various devel projects. I'd like to eventually get them all to factory, but many are missing Requires: packages so that can't be submitted until those preliminary packages get in. So far my deepest dependency chain is 3 packages deep, but I imagine it gets worse for some packages. Currently I'm not aware of anywhere I have a list of what's already in factory. So when I want to see what else I need to queue up for factory, I go thru the "My Projects" page on the webui one at a time and see if the description says it is a devel project for factory. I'm hoping for a more efficient way to say. Damn, I haven't got package15 in factory yet, I guess I need to do that. Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Vincent Untz

9 Feb 9 Feb

07:39

Le mercredi 08 février 2012, à 15:20 -0500, Greg Freemyer a écrit :

...

On Wed, Feb 8, 2012 at 2:19 PM, Stephan Kulow wrote:

...
Am 08.02.2012 18:58, schrieb Greg Freemyer:

...
ie. You have the following packages in factory for which you are the maintainer:

package1, package2, package3, ....

If you can help me understand what this is good for, I'd add it.

I currently have about 30 packages in various devel projects.

I'd like to eventually get them all to factory, but many are missing Requires: packages so that can't be submitted until those preliminary packages get in. So far my deepest dependency chain is 3 packages deep, but I imagine it gets worse for some packages.

Currently I'm not aware of anywhere I have a list of what's already in factory. So when I want to see what else I need to queue up for factory, I go thru the "My Projects" page on the webui one at a time and see if the description says it is a devel project for factory.

I'd say just submit to Factory and say in the sr message "Note that it needs package X, which is submitted as XXXX". The packages will be held in review until all deps get in. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Stephan Kulow

08:05

On 09.02.2012 08:39, Vincent Untz wrote:

...

Le mercredi 08 février 2012, à 15:20 -0500, Greg Freemyer a écrit :

...
On Wed, Feb 8, 2012 at 2:19 PM, Stephan Kulow wrote:

...
Am 08.02.2012 18:58, schrieb Greg Freemyer:

...
ie. You have the following packages in factory for which you are the maintainer:

package1, package2, package3, ....

If you can help me understand what this is good for, I'd add it.

I currently have about 30 packages in various devel projects.

I'd like to eventually get them all to factory, but many are missing Requires: packages so that can't be submitted until those preliminary packages get in. So far my deepest dependency chain is 3 packages deep, but I imagine it gets worse for some packages.

Currently I'm not aware of anywhere I have a list of what's already in factory. So when I want to see what else I need to queue up for factory, I go thru the "My Projects" page on the webui one at a time and see if the description says it is a devel project for factory.

I'd say just submit to Factory and say in the sr message "Note that it needs package X, which is submitted as XXXX". The packages will be held in review until all deps get in.

Right. If that's your use case, then submit all packages you intend to package and use the list of (declined) requests as TODO list. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Guido Berhoerster

8 Feb 8 Feb

10:09

Hi, could you make the mails a bit more filter-friendly, e.g. by adding a unique and stable X- header? Other than that I find them quite useful. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Graham Anderson

10:11

On Wednesday 08 Feb 2012 11:09:07 Guido Berhoerster wrote:

...

Hi,

could you make the mails a bit more filter-friendly, e.g. by adding a unique and stable X- header? Other than that I find them quite useful.

+1 That would be a useful addition -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

4460

Age (days ago)

4466

Last active (days ago)

List overview

Download

33 comments

19 participants

participants (19)

Christian Boltz
Claudio Freire
Graham Anderson
Greg Freemyer
Guido Berhoerster
Johannes Meixner
Marcus Meissner
Mariusz Fik
Michael Schroeder
Michal Vyskocil
Peter Linnell
Petr Uzel
Ralf Lang
Richard Guenther
Robert Schweikert
Stephan Kulow
todd rme
Vincent Untz
Vitezslav Cizek