[opensuse-packaging] Please mention dependency changes in .changes
With at least two recent updates (patch and pam) new BuildRequires were added without mentioning this or a reason in the package .changes. Please put such changes in there together with a reason. Thanks, Richard. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 03.04.2009 16:08, Richard Guenther wrote:
With at least two recent updates (patch and pam) new BuildRequires were added without mentioning this or a reason in the package .changes.
Please put such changes in there together with a reason.
Thanks, Richard.
I hope I'm allowed to ask a question regarding changelog, because this is what I want to do by writing this e-mail ;) . I noticed that most of packages in Build Service no longer provide changelog seen by YaST (because of %changelog → .changes move?). Why does this look like this? "Changelog" in YaST shouldn't be option just because, it should be useful, so I'm still using %changelog. I can't believe YaST, that an update package released in april was modified in december '08 for the last time. It is a lie ;) . Please, help me/us/yourself with changelogs ;) . -- Best regards, Jakub 'Livio' Rusinek http://jakubrusinek.pl/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Jakub 'Livio' Rusinek schrieb:
On 03.04.2009 16:08, Richard Guenther wrote:
With at least two recent updates (patch and pam) new BuildRequires were added without mentioning this or a reason in the package .changes.
Please put such changes in there together with a reason.
I hope I'm allowed to ask a question regarding changelog, because this is what I want to do by writing this e-mail ;) .
I noticed that most of packages in Build Service no longer provide changelog seen by YaST (because of %changelog → .changes move?).
Why does this look like this? "Changelog" in YaST shouldn't be option just because, it should be useful, so I'm still using %changelog.
I can't believe YaST, that an update package released in april was modified in december '08 for the last time. It is a lie ;) .
Please, help me/us/yourself with changelogs ;) .
Hmm, the buildservice used to append the contents of *.changes to the spec's %changelog while building. I hope it still does and if so it would still show up in YaST (when the package is installed). A valid *.changes entry is mandatory for openSUSE:Factory. For outside of openSUSE:Factory the maintainer is responsible for doing it properly. Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 03.04.2009 16:52, Wolfgang Rosenauer wrote:
A valid *.changes entry is mandatory for openSUSE:Factory. For outside of openSUSE:Factory the maintainer is responsible for doing it properly.
Wolfgang
Did you mean that .changes is used only for Factory and outside %changelog should be used? If so, then it's not done this way for most packages and we see old changelog regardless the changes made after release mentioned in %changelog. -- Best regards, Jakub 'Livio' Rusinek http://jakubrusinek.pl/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Jakub 'Livio' Rusinek schrieb:
On 03.04.2009 16:52, Wolfgang Rosenauer wrote:
A valid *.changes entry is mandatory for openSUSE:Factory. For outside of openSUSE:Factory the maintainer is responsible for doing it properly.
Wolfgang
Did you mean that .changes is used only for Factory and outside %changelog should be used?
No, I mean that OBS in general creates %changelog from *.changes. I only maintain *.changes in all of my packages and it correctly gets propagated to the RPM's %changelog.
If so, then it's not done this way for most packages and we see old changelog regardless the changes made after release mentioned in %changelog.
Please specify where you see it? 11.1 Updates? Factory? Some other buildservice project? Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2009-04-03T17:16:55, Wolfgang Rosenauer
If so, then it's not done this way for most packages and we see old changelog regardless the changes made after release mentioned in %changelog. Please specify where you see it? 11.1 Updates? Factory? Some other buildservice project?
Part of the problem is that people are extremely lazy when it comes to updating the changelog. Maybe they'd do better if osc defaulted to using the new changelog entry as the commit message. Regards, Lars -- Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Sunday, 5 April 2009 20:24:01 Lars Marowsky-Bree wrote:
Part of the problem is that people are extremely lazy when it comes to updating the changelog.
Or they are simply humans and happen to forget something, as was actually the case here with at least one of the packages. Happens to most of us once in a while. Andreas -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Sun, 2009-04-05 at 20:24 +0200, Lars Marowsky-Bree wrote:
On 2009-04-03T17:16:55, Wolfgang Rosenauer
wrote: If so, then it's not done this way for most packages and we see old changelog regardless the changes made after release mentioned in %changelog. Please specify where you see it? 11.1 Updates? Factory? Some other buildservice project?
Part of the problem is that people are extremely lazy when it comes to updating the changelog.
Maybe they'd do better if osc defaulted to using the new changelog entry as the commit message.
As long as it doesn't force us to use the commit message for the changelog entry. In the GNOME team, not one single package gets in if the .spec file have been modified and it's not in the .changes file, so wouldn't want to do this twice :-) Cheers, Magnus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Sunday 05 of April 2009 20:24:01 Lars Marowsky-Bree wrote:
On 2009-04-03T17:16:55, Wolfgang Rosenauer
wrote: If so, then it's not done this way for most packages and we see old changelog regardless the changes made after release mentioned in %changelog.
Please specify where you see it? 11.1 Updates? Factory? Some other buildservice project?
Part of the problem is that people are extremely lazy when it comes to updating the changelog.
And another parts are: - Is there documentation about it on wiki? Because external maintainers probably don't know about it. - Do we have a osc vc, or it's just internal command? - Is osc helpful, or not? Because if we want changes, we could check them in commit, or merge the osc commit log with changes, ...
Maybe they'd do better if osc defaulted to using the new changelog entry as the commit message.
Well, I need to refresh my patches and try to get a write access to osc SVN asap, because I wrote it some time ago, but didn't submit it yet. Best regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Lars Marowsky-Bree
On 2009-04-03T17:16:55, Wolfgang Rosenauer
wrote: If so, then it's not done this way for most packages and we see old changelog regardless the changes made after release mentioned in %changelog. Please specify where you see it? 11.1 Updates? Factory? Some other buildservice project?
Part of the problem is that people are extremely lazy when it comes to updating the changelog.
Maybe they'd do better if osc defaulted to using the new changelog entry as the commit message.
That's a cool idea. So osc would parse the change log and propose the newes changes entry. For merges, it should also support/ease the merge of the change logs. S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (8)
-
Andreas Gruenbacher
-
Jakub 'Livio' Rusinek
-
Lars Marowsky-Bree
-
Magnus Boman
-
Michal Vyskocil
-
Richard Guenther
-
Susanne Oberhauser
-
Wolfgang Rosenauer