On Mon, Sep 23, 2013 at 6:35 PM,
wrote: Glenn,
You seem to have done the work. Why not just submit your package to
On Wed, 25 Sep 2013 11:50:59 -0400, Greg Freemyer
development repo?
Ie. The normal approach to updating a package you don't maintain is:
Branch a copy of development project to home project.
Update/test in home project.
Submit updated package back to development project .
Greg
Hello, Steps done: 1. Branched package system:packagemanager / smart 2. Added in newer package updates , amended spec file - smart (Project home:doiggl:branches:system:packagemanager)
Question: How do I submit updated package back to development project ? system:packagemanager / smart Thanks Glenn
Options on the page I see are: Branch package Submit package Edit description Delete package
From the GUI:
In the upper right corner you should see "could have a link diff".
I typically click that and review all of my changes. If they all look good at the bottom of the page full diffs is a submit button.
In your case your changes file is a little weak:
=============== ------------------------------------------------------------------- Wed Sep 10 14:22:37 CEST 2012
- update to version 1.4.1 - add smart-245344-takes_long_computing_upgrades.patch ===============
First, has it really been a year since you did the update?
Second, you should have your e-mail address after the date. Look at the other change entries to see the syntax
Third - It is preferred if you have sub-bullets under update to v1.4.1 that say what the changes are. I typically get that from the upstream changes file. It can be just a couple bullets up to 20 or so (that is a personal max, not a opensuse policy max)
See this changes entry as an example: === ------------------------------------------------------------------- Wed Sep 10 14:22:37 CEST 2008 - cthiel@suse.de
- update to version 1.1 * The curl-based fetcher backend was handling 404 errors improperly. * Handling of signed up apt-deb channels has been improved so that a behavior similar to that of APT may be obtained. - removed smart-order-test-packages.patch and smart--cast-test-sizes.patch, both included upstream ===
Then just so you know, some maintainers will require you to document the new patch with a one line comment. Given the existing 3 patches aren't documented the maintainer may let it slide.
http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
Greg
Hello, A list of changes can be found at https://launchpad.net/smart/+milestone/1.4.1 Someone else built the package. Question: Can a link to the listed changes, be put in the changes file ? --Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org