Questions on package adoption conventions

Questions on package adoption conventions

[Mark Geisert]

Q1: Does a new maintainer typically put out a new package version upon 
take-over, or can he/she run with the existing version number and just 
keep bumping the build number (e.g. for bug fixes)?

Q2: Does the location hosting a test build for external review have to be 
the same location used to host final builds?

Q3: What kind of external access is typically used for hosting final 
builds?  I've run a micro-ISP that allowed on-request FTP access, by IP 
address, to customers, but have not needed to run anonymous FTP to this 
point.  What about SSH/SFTP?  Is there such a thing as anonymous SFTP? 
Does HTTP and/or HTTPS access need to be provided?

Detailed suggestions for that last question would be welcomed.  I'd like 
to make it least-hassle for reviewers and whatever a source install of my 
packages would require, but still keep the hosting machine as secured as 
can be managed.

..mark

Re: Questions on package adoption conventions

[Marco Atzeri]

On 30/10/2015 22:48, Mark Geisert wrote:
> Q1: Does a new maintainer typically put out a new package version upon
> take-over, or can he/she run with the existing version number and just
> keep bumping the build number (e.g. for bug fixes)?

As needed.
If you are not changing the upstream source just bump the cygwin revision

> Q2: Does the location hosting a test build for external review have to
> be the same location used to host final builds?


https://cygwin.com/setup.htm

Test build are reviewed.
Final package are uploaded by each maintainer on www.cygwin.com

> Q3: What kind of external access is typically used for hosting final
> builds?  I've run a micro-ISP that allowed on-request FTP access, by IP
> address, to customers, but have not needed to run anonymous FTP to this
> point.  What about SSH/SFTP?  Is there such a thing as anonymous SFTP?
> Does HTTP and/or HTTPS access need to be provided?

Upload instructions:
https://sourceware.org/cygwin-apps/package-upload.html

>
> Detailed suggestions for that last question would be welcomed.  I'd like
> to make it least-hassle for reviewers and whatever a source install of
> my packages would require, but still keep the hosting machine as secured
> as can be managed.
>
> ..mark

Re: Questions on package adoption conventions

[Mark Geisert]

Thanks Marco.

On Fri, 30 Oct 2015, Marco Atzeri wrote:
> On 30/10/2015 22:48, Mark Geisert wrote:
>> Q3: What kind of external access is typically used for hosting final
>> builds?  I've run a micro-ISP that allowed on-request FTP access, by IP
>> address, to customers, but have not needed to run anonymous FTP to this
>> point.  What about SSH/SFTP?  Is there such a thing as anonymous SFTP?
>> Does HTTP and/or HTTPS access need to be provided?
>
> Upload instructions:
> https://sourceware.org/cygwin-apps/package-upload.html

D'oh, users download source packages from cygwin.com, of course.

I was confused by the SRC_URI= line in cygutils.cygport.  Does that merely 
indicate where this package came from at the time the .cygport file was 
written, or does it denote a commitment by the maintainer to continue 
hosting the package from that URI?  If the latter, that's why I was asking
about access methods.  Is SRC_URI required?

..mark

Re: Questions on package adoption conventions

[Marco Atzeri]

On 31/10/2015 00:25, Mark Geisert wrote:
> Thanks Marco.
>
> On Fri, 30 Oct 2015, Marco Atzeri wrote:
>> On 30/10/2015 22:48, Mark Geisert wrote:
>>> Q3: What kind of external access is typically used for hosting final
>>> builds?  I've run a micro-ISP that allowed on-request FTP access, by IP
>>> address, to customers, but have not needed to run anonymous FTP to this
>>> point.  What about SSH/SFTP?  Is there such a thing as anonymous SFTP?
>>> Does HTTP and/or HTTPS access need to be provided?
>>
>> Upload instructions:
>> https://sourceware.org/cygwin-apps/package-upload.html
>
> D'oh, users download source packages from cygwin.com, of course.
>
> I was confused by the SRC_URI= line in cygutils.cygport.  Does that
> merely indicate where this package came from at the time the .cygport
> file was written, or does it denote a commitment by the maintainer to
> continue hosting the package from that URI?  If the latter, that's why I
> was asking
> about access methods.  Is SRC_URI required?

It is required by Cygport to build the package, but it can
be a dummy one.

  SRC_URI=URL/package

just tell cygport to unpack "package" if already in the
working directory.
It can be used to download the package if not available.

cygutils is a cygwin only package, so in this case the upstream
source is in the package itself, there is no real distinction.

I do not see the strict need to have a a working URL,
but you can choose as you prefer.
If you want it, cygport supports http, ftp and more.

Regards
Marco







> ..mark

Re: Questions on package adoption conventions

[Jon Turney]

On 30/10/2015 23:25, Mark Geisert wrote:
> On Fri, 30 Oct 2015, Marco Atzeri wrote:
>> On 30/10/2015 22:48, Mark Geisert wrote:
>>> Q3: What kind of external access is typically used for hosting final
>>> builds?  I've run a micro-ISP that allowed on-request FTP access, by IP
>>> address, to customers, but have not needed to run anonymous FTP to this
>>> point.  What about SSH/SFTP?  Is there such a thing as anonymous SFTP?
>>> Does HTTP and/or HTTPS access need to be provided?
>>
>> Upload instructions:
>> https://sourceware.org/cygwin-apps/package-upload.html
>
> D'oh, users download source packages from cygwin.com, of course.
>
> I was confused by the SRC_URI= line in cygutils.cygport.  Does that
> merely indicate where this package came from at the time the .cygport
> file was written, or does it denote a commitment by the maintainer to
> continue hosting the package from that URI?  If the latter, that's why I
> was asking about access methods.  Is SRC_URI required?

SRC_URI is the URI for the upstream source.

cygport's fetch (aka download) subcommand will fetch the upstream source 
from the specified SRC_URI

cygutils is somewhat a special case as cygwin is the upstream :)

The sources are in CVS at 
pserver:anoncvs@sourceware.org:/cvs/cygwin-apps, but the tarballs seem 
to be hosted on fruitbat.org at the moment.

I think the best thing to do is to ask for that CVS to be migrated to 
git, then the cygport can be written to fetch the source directly from a 
specified tag in git, since this will avoid the need for you to make 
tarballs and work out where to host them.

Re: Questions on package adoption conventions

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2449 bytes --]

On Oct 31 00:18, Jon Turney wrote:
> On 30/10/2015 23:25, Mark Geisert wrote:
> >On Fri, 30 Oct 2015, Marco Atzeri wrote:
> >>On 30/10/2015 22:48, Mark Geisert wrote:
> >>>Q3: What kind of external access is typically used for hosting final
> >>>builds?  I've run a micro-ISP that allowed on-request FTP access, by IP
> >>>address, to customers, but have not needed to run anonymous FTP to this
> >>>point.  What about SSH/SFTP?  Is there such a thing as anonymous SFTP?
> >>>Does HTTP and/or HTTPS access need to be provided?
> >>
> >>Upload instructions:
> >>https://sourceware.org/cygwin-apps/package-upload.html
> >
> >D'oh, users download source packages from cygwin.com, of course.
> >
> >I was confused by the SRC_URI= line in cygutils.cygport.  Does that
> >merely indicate where this package came from at the time the .cygport
> >file was written, or does it denote a commitment by the maintainer to
> >continue hosting the package from that URI?  If the latter, that's why I
> >was asking about access methods.  Is SRC_URI required?
> 
> SRC_URI is the URI for the upstream source.
> 
> cygport's fetch (aka download) subcommand will fetch the upstream source
> from the specified SRC_URI
> 
> cygutils is somewhat a special case as cygwin is the upstream :)
> 
> The sources are in CVS at pserver:anoncvs@sourceware.org:/cvs/cygwin-apps,
> but the tarballs seem to be hosted on fruitbat.org at the moment.
> 
> I think the best thing to do is to ask for that CVS to be migrated to git,

Done:

  git clone git://sourceware.org/git/cygwin-cygutils.git

  Gitweb: https://sourceware.org/git/?p=cygwin-cygutils.git

Mark, if you're going to maintain the project, you probably want to
make changes to the git repo.  For that you need ssh access to
sourceware.org AKA cygwin.com.  Pleae use the form at

  https://sourceware.org/cgi-bin/pdw/ps_form.cgi

to request SSH access to sware.  Project is "cygwin-apps", Use my
email address for the approver field.

> then the cygport can be written to fetch the source directly from a
> specified tag in git, since this will avoid the need for you to make
> tarballs and work out where to host them.

E.g.

  GIT_URI="git://cygwin.com/git/newlib-cygwin.git"
  GIT_TAG="..."


HTH,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Questions on package adoption conventions

[Mark Geisert]

On Sat, 31 Oct 2015, Corinna Vinschen wrote:
> On Oct 31 00:18, Jon Turney wrote:
>> On 30/10/2015 23:25, Mark Geisert wrote:
>>> I was confused by the SRC_URI= line in cygutils.cygport.  Does that
>>> merely indicate where this package came from at the time the .cygport
>>> file was written, or does it denote a commitment by the maintainer to
>>> continue hosting the package from that URI?  If the latter, that's why I
>>> was asking about access methods.  Is SRC_URI required?
>>
>> SRC_URI is the URI for the upstream source.
>>
>> cygport's fetch (aka download) subcommand will fetch the upstream source
>> from the specified SRC_URI
>>
>> cygutils is somewhat a special case as cygwin is the upstream :)
>>
>> The sources are in CVS at pserver:anoncvs@sourceware.org:/cvs/cygwin-apps,
>> but the tarballs seem to be hosted on fruitbat.org at the moment.
>>
>> I think the best thing to do is to ask for that CVS to be migrated to git,
>
> Done:
>
>  git clone git://sourceware.org/git/cygwin-cygutils.git
>
>  Gitweb: https://sourceware.org/git/?p=cygwin-cygutils.git
>
> Mark, if you're going to maintain the project, you probably want to
> make changes to the git repo.  For that you need ssh access to
> sourceware.org AKA cygwin.com.  Pleae use the form at
>
>  https://sourceware.org/cgi-bin/pdw/ps_form.cgi
>
> to request SSH access to sware.  Project is "cygwin-apps", Use my
> email address for the approver field.
>
>> then the cygport can be written to fetch the source directly from a
>> specified tag in git, since this will avoid the need for you to make
>> tarballs and work out where to host them.
>
> E.g.
>
>  GIT_URI="git://cygwin.com/git/newlib-cygwin.git"
>  GIT_TAG="..."

This does seems like the best way to go, for several reasons.  I've sent 
in the SSH access request form.
Thanks much!

..mark

Re: Questions on package adoption conventions

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]

On Oct 31 21:15, Mark Geisert wrote:
> On Sat, 31 Oct 2015, Corinna Vinschen wrote:
> >On Oct 31 00:18, Jon Turney wrote:
> >>On 30/10/2015 23:25, Mark Geisert wrote:
> >>>I was confused by the SRC_URI= line in cygutils.cygport.  Does that
> >>>merely indicate where this package came from at the time the .cygport
> >>>file was written, or does it denote a commitment by the maintainer to
> >>>continue hosting the package from that URI?  If the latter, that's why I
> >>>was asking about access methods.  Is SRC_URI required?
> >>
> >>SRC_URI is the URI for the upstream source.
> >>
> >>cygport's fetch (aka download) subcommand will fetch the upstream source
> >>from the specified SRC_URI
> >>
> >>cygutils is somewhat a special case as cygwin is the upstream :)
> >>
> >>The sources are in CVS at pserver:anoncvs@sourceware.org:/cvs/cygwin-apps,
> >>but the tarballs seem to be hosted on fruitbat.org at the moment.
> >>
> >>I think the best thing to do is to ask for that CVS to be migrated to git,
> >
> >Done:
> >
> > git clone git://sourceware.org/git/cygwin-cygutils.git
> >
> > Gitweb: https://sourceware.org/git/?p=cygwin-cygutils.git
> >
> >Mark, if you're going to maintain the project, you probably want to
> >make changes to the git repo.  For that you need ssh access to
> >sourceware.org AKA cygwin.com.  Pleae use the form at
> >
> > https://sourceware.org/cgi-bin/pdw/ps_form.cgi
> >
> >to request SSH access to sware.  Project is "cygwin-apps", Use my
> >email address for the approver field.
> >
> >>then the cygport can be written to fetch the source directly from a
> >>specified tag in git, since this will avoid the need for you to make
> >>tarballs and work out where to host them.
> >
> >E.g.
> >
I forgot one line here:

> > GIT_URI="git://cygwin.com/git/newlib-cygwin.git"
> > GIT_TAG="..."
    inherit git

> This does seems like the best way to go, for several reasons.  I've sent in
> the SSH access request form.
> Thanks much!

Approved.  You should get a mail from sware overseers shorty.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Questions on package adoption conventions

[Mark Geisert]

I was able to 'git clone' the cygutils source tree and fix user-reported 
issues and my build issues.  I'm ready to push the updates but have hit a 
snag...
--------8<--------
<prompt> git push origin master
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
-------->8--------

I tried creating a git branch and pushing that instead; same error. 
Adding -v to the 'git push' command shows "Pushing to 
git://sourceware.org/git/cygwin-cygutils.git" which seems correct.

I suspect my login credentials are incorrect.  How/where do I specify what 
my sourceware login is?  Or maybe it's some other problem?

Separate from that, I will need to update the cygutils.cygport file which 
resides outside of this cygutils source tree.  How do I access that file?

And if that wasn't enough, here's another newbie question:  Am I really 
supposed to push to master or is there a review that should be done first? 
So pushing a revision branch is the right way to allow for a review?
Thanks for any hints,

..mark

Re: Questions on package adoption conventions

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]

On Nov  4 03:36, Mark Geisert wrote:
> I was able to 'git clone' the cygutils source tree and fix user-reported
> issues and my build issues.  I'm ready to push the updates but have hit a
> snag...
> --------8<--------
> <prompt> git push origin master
> fatal: Could not read from remote repository.
> 
> Please make sure you have the correct access rights
> and the repository exists.
> -------->8--------
> 
> I tried creating a git branch and pushing that instead; same error. Adding
> -v to the 'git push' command shows "Pushing to
> git://sourceware.org/git/cygwin-cygutils.git" which seems correct.

Uh, no, look here: https://sourceware.org/cygwin-apps/

The "git" access mode is read-only.  You have to change your write
mode to using ssh instead, e.g.

  git config --local remote.origin.pushurl cygwin.com:/git/newlib-cygwin.git

That will use the "git" access mode for pulling and "ssh" for pushing.

> I suspect my login credentials are incorrect.  How/where do I specify what
> my sourceware login is?  Or maybe it's some other problem?

You have to set the right private ssh key in ~/.ssh/config, e.g.

  Host cygwin.com sourceware.org
    User mgeisert
    IdentityFile ~/.ssh/id_rsa_cygwin

It should match the public key you sent in your request, but that goes
without saying.

> Separate from that, I will need to update the cygutils.cygport file which
> resides outside of this cygutils source tree.  How do I access that file?

You don't, it's not part of the project yet.  If you want to add your own
cygutils.cygport file to the project, feel free.

> And if that wasn't enough, here's another newbie question:  Am I really
> supposed to push to master or is there a review that should be done first?
> So pushing a revision branch is the right way to allow for a review?

This is your project now.  If you want to push to master, it's yours.
Unless you really screw up big and remove the older commits, which is
rather unlikely to do, you can't make a lot wrong.

As for reviewing, we'd prefer links to the produced tar files, e.g.

  cygutils-42.0-1.tar.xz
  cygutils-42.0-1-src.tar.xz
  cygutils-debuginfo-42.0-1.tar.xz


HTH,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Questions on package adoption conventions

[Achim Gratz]

Mark Geisert writes:
> I was able to 'git clone' the cygutils source tree and fix
> user-reported issues and my build issues.  I'm ready to push the
> updates but have hit a snag...
> --------8<--------
> <prompt> git push origin master
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> -------->8--------

Put this into your global .gitconfig:

--8<---------------cut here---------------start------------->8---
[url "git://sourceware.org/git/"]
        InsteadOf = cygwin:
[url "ssh://sourceware.org/git/"]
        pushInsteadOf = cygwin:
--8<---------------cut here---------------end--------------->8---

and then specify the remote as cygwin:cygwin-cygutils.git (the .git
suffix might be redundant, actually).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves