What's the designated procedure to get this to happen? Isn't keeping packages at latest versions in Factory supposed to be automatic?
11.3 was released with mc 4.6.2 long after 4.7.0.4 was released, many iterations past the 4.6.2 that Factory still has, while as of today mc stable is at 4.7.0.9 and mc devel is at 4.7.4.
FWIW, https://bugzilla.novell.com/show_bug.cgi?id=571503 probably depends on some considerably newer mc version.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 09/07/2010 10:36 AM, Felix Miata wrote:
What's the designated procedure to get this to happen? Isn't keeping packages at latest versions in Factory supposed to be automatic?
11.3 was released with mc 4.6.2 long after 4.7.0.4 was released, many iterations past the 4.6.2 that Factory still has, while as of today mc stable is at 4.7.0.9 and mc devel is at 4.7.4.
FWIW, https://bugzilla.novell.com/show_bug.cgi?id=571503 probably depends on some considerably newer mc version.
This is a request you've consistently had. Do you have an OBS account? If so, update the package and create a submit request.
- -Jeff
- -- Jeff Mahoney SUSE Labs
On Tue, Sep 07, 2010 at 10:36:31AM -0400, Felix Miata wrote:
What's the designated procedure to get this to happen? Isn't keeping packages at latest versions in Factory supposed to be automatic?
11.3 was released with mc 4.6.2 long after 4.7.0.4 was released, many iterations past the 4.6.2 that Factory still has, while as of today mc stable is at 4.7.0.9 and mc devel is at 4.7.4.
FWIW, https://bugzilla.novell.com/show_bug.cgi?id=571503 probably depends on some considerably newer mc version.
Please feel free to submit the current stable version ... Its not hard. :)
Ciao, Marcus
Am Dienstag 07 September 2010 schrieb Marcus Meissner:
On Tue, Sep 07, 2010 at 10:36:31AM -0400, Felix Miata wrote:
What's the designated procedure to get this to happen? Isn't keeping packages at latest versions in Factory supposed to be automatic?
11.3 was released with mc 4.6.2 long after 4.7.0.4 was released, many iterations past the 4.6.2 that Factory still has, while as of today mc stable is at 4.7.0.9 and mc devel is at 4.7.4.
FWIW, https://bugzilla.novell.com/show_bug.cgi?id=571503 probably depends on some considerably newer mc version.
Please feel free to submit the current stable version ... Its not hard. :)
E.g. http://lizards.opensuse.org/2009/06/20/opensuse-factory-fixing-packages/ should still be pretty much uptodate.
Greetings, Stephan
Am Dienstag 07 September 2010 schrieb Felix Miata:
What's the designated procedure to get this to happen? Isn't keeping packages at latest versions in Factory supposed to be automatic?
No, it's not automatic at all. Updating software to the latest version is work and someone needs to be interested in doing that work.
Greetings, Stephan
On Tuesday 07 September 2010 17:05:58 Stephan Kulow wrote:
Am Dienstag 07 September 2010 schrieb Felix Miata:
What's the designated procedure to get this to happen? Isn't keeping packages at latest versions in Factory supposed to be automatic?
No, it's not automatic at all. Updating software to the latest version is work and someone needs to be interested in doing that work.
Greetings, Stephan
+1
In this case, I had a look at upgrading mc and in this case, if it were a simple version bump and perhaps a patch or two, I would have done it already.
This case shows why sometimes there is a fair amount of work to be done,even for an application which seems on the surface 'simple'. There are several patches which need review: Are they now upstream or not ? Will they apply with fuzz=0 which is the standard for 11.3+ ? Have the security fixes been applied for upstream. For a packager, that means parsing change logs of each release, perhaps the uprsteam bugtracker, then testing new builds, which might not always work.
In this case, yes I am motivated to upgrade it, but time is limited and I am only doing what I can in free time.
Cheers, Peter
On 2010/09/07 10:36 (GMT-0400) Felix Miata composed:
Isn't keeping packages at latest versions in Factory supposed to be automatic?
* Felix Miata (mrmazda@earthlink.net) [20100907 16:36]:
What's the designated procedure to get this to happen?
Either nudge the maintainer of mc or get an OBS account, branch and update mc and the submit a request to mege the changes.
Isn't keeping packages at latest versions in Factory supposed to be automatic?
No, it's not supposed to automatic as the maintainer must have the last word on which version is going to be used.
11.3 was released with mc 4.6.2 long after 4.7.0.4 was released
You already loudly complained about that.
many iterations past the 4.6.2 that Factory still has, while as of today mc stable is at 4.7.0.9 and mc devel is at 4.7.4.
Devel versions are seldomly used so it's irrelevant. And Factory is still at 4.6.2 because Factory was frozen at the time I updated mc in the devel project and just forgot to do the update. I've submitted the sr now so Factory should be at 4.7.0 soon. If you want a newer version, why don't you do the update yourself?
Philipp
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
[delayed sent]
On 2010-09-07 20:01, Philipp Thomas wrote:
- Felix Miata () [20100907 16:36]:
What's the designated procedure to get this to happen?
Either nudge the maintainer of mc or get an OBS account, branch and update mc and the submit a request to mege the changes.
That's what we are doing: nudging the maintainers ;-)
- -- Cheers / Saludos,
Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith))
On Tue, 7 Sep 2010, Philipp Thomas wrote:
[mc] I've submitted the sr now so Factory should be at 4.7.0 soon. If you want a newer version, why don't you do the update yourself?
Few good deeds go unpunished:
[Bug 639044] mc: /etc/profile.d/mc.sh: line 5: unexpected EOF
Gerald
On Mon, 13 Sep 2010 23:07:56 +0200 (CEST), Gerald Pfeifer gp@novell.com wrote:
Few good deeds go unpunished:
[Bug 639044] mc: /etc/profile.d/mc.sh: line 5: unexpected EOF
What great news to start into the next year of my life :( I'll look into it.
Philipp
* Philipp Thomas (Philipp.Thomas2@gmx.net) [20100914 09:32]:
I'll look into it.
Fixed. And while I was at it I also updated to 4.7.0.9. Felix, next time you complain you get to update it yourself :)
Philipp
On 2010/09/14 16:51 (GMT+0200) Philipp Thomas composed:
- Philipp Thomas (Philipp.Thomas2@gmx.net) [20100914 09:32]:
I'll look into it.
Fixed. And while I was at it I also updated to 4.7.0.9. Felix, next time you complain you get to update it yourself :)
I'm not a programmer. The time I would spend learning how would be time not spent doing what I already know how to do - finding Factory bugs and reporting them - so I'll have to pass on the OBS stuff. I already have a major shortage of round tuits as it is.
On 09/14/2010 at 5:30 PM, Felix Miata mrmazda@earthlink.net wrote:
I'm not a programmer. The time I would spend learning how would be time not spent doing what I already know how to do - finding Factory bugs and reporting them - so I'll have to pass on the OBS stuff. I already have a major shortage of round tuits as it is.
For most packages you do not have to be a programmer. If you manage to use ./configure make make install
on your machine, in many cases you are able to build a package out of it.
Just have a look at a very old blog post: http://dominique.leuenberger.net/blog/?p=5
It DOES work very often (not always.. but hey.. nothing is always the same).
For package updates, if the package is not cluttered with dozens of patches, very often it's not more than: - Branching in obs - Adding the new tarball, removing the old one - Chaning the version number in the .spec file - Writing the .changes entry
None of this requires ANY programmatic skill. (and for some parts we have nice plugins to osc, called collab)
Dminique
Le mardi 14 septembre 2010, à 17:46 +0200, Dominique Leuenberger a écrit :
On 09/14/2010 at 5:30 PM, Felix Miata mrmazda@earthlink.net wrote:
I'm not a programmer. The time I would spend learning how would be time not spent doing what I already know how to do - finding Factory bugs and reporting them - so I'll have to pass on the OBS stuff. I already have a major shortage of round tuits as it is.
For most packages you do not have to be a programmer. If you manage to use ./configure make make install
on your machine, in many cases you are able to build a package out of it.
Just have a look at a very old blog post: http://dominique.leuenberger.net/blog/?p=5
It DOES work very often (not always.. but hey.. nothing is always the same).
For package updates, if the package is not cluttered with dozens of patches, very often it's not more than:
- Branching in obs
- Adding the new tarball, removing the old one
- Chaning the version number in the .spec file
- Writing the .changes entry
None of this requires ANY programmatic skill. (and for some parts we have nice plugins to osc, called collab)
And friendly people are here to help if needed :-)
Vincent
On 2010/09/14 09:30 (GMT+0200) Philipp Thomas composed:
Gerald Pfeifer wrote:
Few good deeds go unpunished:
[Bug 639044] mc: /etc/profile.d/mc.sh: line 5: unexpected EOF
What great news to start into the next year of my life :( I'll look into it.
Thanks for your effort! :-)
If only broken umount.nfs could be fixed so fast. :-p
On 09/07/2010 04:36 PM, Felix Miata wrote:
What's the designated procedure to get this to happen? Isn't keeping packages at latest versions in Factory supposed to be automatic?
11.3 was released with mc 4.6.2 long after 4.7.0.4 was released, many iterations past the 4.6.2 that Factory still has, while as of today mc stable is at 4.7.0.9 and mc devel is at 4.7.4.
FWIW, https://bugzilla.novell.com/show_bug.cgi?id=571503 probably depends on some considerably newer mc version.
You can get 4.7.3 at : http://download.opensuse.org/repositories/home:/plater/openSUSE_11.3/ I'll most probably update it at a later stage as I'm busy with matters multimedia atm. Regards Dave P
-
Carlos E. R. -
Dave Plater -
Dominique Leuenberger -
Felix Miata -
Gerald Pfeifer -
Jeff Mahoney -
Marcus Meissner -
P Linnell -
Philipp Thomas -
Philipp Thomas -
Stephan Kulow -
Vincent Untz