Update of packages by non-maintainer

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Update of packages by non-maintainer

Yasuhiro KIMURA
Hello all,

I would like to update some packages but I'm not maintainer of
them. Then what is proper way to update them? Is it OK to create
updated packages by myself and submit them? Or should I request to
maintainers and wait until they take action?

Best Regards.
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
Reply | Threaded
Open this post in threaded view
|

Re: Update of packages by non-maintainer

Cygwin list mailing list
On Wed, May 20, 2020 at 12:44 PM Yasuhiro KIMURA <[hidden email]> wrote:
>
> Hello all,
>
> I would like to update some packages but I'm not maintainer of
> them. Then what is proper way to update them? Is it OK to create
> updated packages by myself and submit them? Or should I request to
> maintainers and wait until they take action?
>
> Best Regards.

Hi Yasushiro,

usually you ask the maintainer on this list and wait for the feedback.

However if you are interested to become the single maintainer or the
co-maintainer of any package, you can do so on the cygwin-apps mailing
list.
Which packages are you interested in ? We have plenty of them
and new maintainers are always welcome:

https://cygwin.com/cygwin-pkg-maint

suggested reading
https://cygwin.com/packaging-contributors-guide.html

Regards
Marco
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
Reply | Threaded
Open this post in threaded view
|

Re: Update of packages by non-maintainer

Brian Inglis
In reply to this post by Yasuhiro KIMURA
On 2020-05-20 04:18, Yasuhiro KIMURA wrote:
> I would like to update some packages but I'm not maintainer of
> them. Then what is proper way to update them? Is it OK to create
> updated packages by myself and submit them? Or should I request to
> maintainers and wait until they take action?

You should discuss changes and intent on cygwin list, post patches on
cygwin-apps list.

You could also contact the upstream package maintainer, and skip Cygwin,
depending on the upstream package maintainer.

You can also just download the source packages, build with cygport, change,
create patches, rebuild, and keep track of your changes.

--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
Reply | Threaded
Open this post in threaded view
|

Re: Update of packages by non-maintainer

Yasuhiro KIMURA
From: Brian Inglis <[hidden email]>
Subject: Re: Update of packages by non-maintainer
Date: Wed, 20 May 2020 08:32:59 -0600

> You should discuss changes and intent on cygwin list, post patches on
> cygwin-apps list.

Thank you for reply. My first candidate is anthy. Original anthy
projet has been inactive since 2009. But Debian forked it and made
improvement and enhancement. So I would like to switch codebase to
that of Debian. I just checked out cygwin anthy git repository and
started working but I have one question.

After project fork by Debian, release version scheme has changed.
While latest version from original project (and one used by cygwin
package) is "9100h", latest one from Debian is "0.4". That is, version
number decreses if I chage codebase to Debian. I know that some
packaging systems assume version number basically increases and that
decrement causes package upgrade failure.  So I would like to know if
it also apply to Cygwin. And if it does then I also would like to know
how it should be handled.

Best Regards.

---
Yasuhiro KIMURA
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
Reply | Threaded
Open this post in threaded view
|

Re: Update of packages by non-maintainer

Andrey Repin
Greetings, Yasuhiro KIMURA!

>> You should discuss changes and intent on cygwin list, post patches on
>> cygwin-apps list.

> Thank you for reply. My first candidate is anthy. Original anthy
> projet has been inactive since 2009. But Debian forked it and made
> improvement and enhancement. So I would like to switch codebase to
> that of Debian. I just checked out cygwin anthy git repository and
> started working but I have one question.

> After project fork by Debian, release version scheme has changed.
> While latest version from original project (and one used by cygwin
> package) is "9100h", latest one from Debian is "0.4". That is, version
> number decreses if I chage codebase to Debian. I know that some
> packaging systems assume version number basically increases and that
> decrement causes package upgrade failure.  So I would like to know if
> it also apply to Cygwin.

It does. This is why you would see test and pre-release versions posted as
X.Y-0.Z and release versions posted as X.Y-Z.

> And if it does then I also would like to know how it should be handled.

An interesting question, given nonstandard original versioning.


--
With best regards,
Andrey Repin
Thursday, May 21, 2020 12:46:55

Sorry for my terrible english...

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
Reply | Threaded
Open this post in threaded view
|

Re: Update of packages by non-maintainer

Cygwin list mailing list
In reply to this post by Yasuhiro KIMURA
On 21.05.2020 06:47, Yasuhiro KIMURA wrote:

> From: Brian Inglis
> Subject: Re: Update of packages by non-maintainer
> Date: Wed, 20 May 2020 08:32:59 -0600
>
>> You should discuss changes and intent on cygwin list, post patches on
>> cygwin-apps list.
>
> Thank you for reply. My first candidate is anthy. Original anthy
> projet has been inactive since 2009. But Debian forked it and made
> improvement and enhancement. So I would like to switch codebase to
> that of Debian. I just checked out cygwin anthy git repository and
> started working but I have one question.

the anthy pkg maintainer, Yaakov, is reducing his activity
and if you are interested you can take over.

> After project fork by Debian, release version scheme has changed.
> While latest version from original project (and one used by cygwin
> package) is "9100h", latest one from Debian is "0.4". That is, version
> number decreses if I chage codebase to Debian. I know that some
> packaging systems assume version number basically increases and that
> decrement causes package upgrade failure.  So I would like to know if
> it also apply to Cygwin. And if it does then I also would like to know
> how it should be handled.

currently we have no solution. There were in the past discussion
to overcome such problem but they are not yet implemented.

We can follow these two points on the cygwin-apps mailing list,
please subscribe to it.


> Best Regards.
>
> ---
> Yasuhiro KIMURA

Regards
Marco

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple