[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Follow-up Comment #38, sr #110199 (project administration):

My wishes don't matter; what does matter is Savannah hosting requirements
explained on the page I referred to in comment #36, with references to GNU
legal guidelines.  If you see where my requests deviate from them, please show
me.



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #37, sr #110199 (project administration):

Hello,

Thank you for your reply. If I understand correctly all files under the BSD-3
licence have to contain a copy of the license text. Secondly for other
licences every file has to carry a copyright and license notice.

All of the above applies to files longer that 10 lines, according to the link
you gave above. What to do with such files?

I made an attempt to add a copyright file in every directory, listing all
files with their copyright and license information. This is what Debian does
for their packages. This solution does not seem to be accepted, right? Please
confirm and I'll make all changes according to your wishes. (Even if very
small files, > 10 lines, are cluttered with the license and copyright
information, making them harder to read). 

Thanks!


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Follow-up Comment #36, sr #110199 (project administration):

First, it isn't clear to me from your comment if you checked all files in your
tarball.  When I say 'all' I mean a procedure like find . -type f -print0 |
xargs -o0 $EDITOR and so on, and I implied that you would run it.  You should
be able to identify licensing issues without help of Savannah admins in order
to maintain software on Savannah.

Then, I must apologize.  I tried to explain one point, but didn't do that
satisfactorily.  The point is, there are two classes of license notices: the
notices that refer to the full text of the license, and the notices that _are_
the full text of the license. The former are used for longer licenses like GPL
and Apache 2.0; the latter are used for short lax permissive licenses,
including the Modified BSD license, and in that case, no separate copy of the
license in a dedicated file is needed.  As a circumstance that could excuse me
to a degree, I can point out that this is documented on our
[//savannah.gnu.org/maintenance/ValidNotices/ page describing copyright and
license notices] that had already shown up in this support request.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #35, sr #110199 (project administration):

Hi again,

The file COPYING in patches/PAM/hurd_no_setfsuid.diff was added by me. The
text in that file is now changed to:
Copyright (C) 2018 Steve Langasek. Linux-PAM is free software licensed under
the 3-clause BSD license, see the file ../../licenses/BSD-3. Is that better?

Any other issues with licences and copyright?

Thanks!


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Update of sr #110199 (project administration):

  Status: In Progress => Need Info  
 Open/Closed:Open => Closed 

___

Follow-up Comment #34:

Some files still lack valid license notices: in particular,
patches/Linux-PAM/hurd_no_setfsuid.diff refers to an absent ./COPYING; if the
license is permissive, it should be included entirely in the covered file.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Update of sr #110199 (project administration):

  Status:   Need Info => In Progress
 Open/Closed:  Closed => Open   


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #33, sr #110199 (project administration):

Hello, this issue seems to have a Closed status. Can somebody open it again?

Thanks!



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #32, sr #110199 (project administration):

Long time no see!

Attached is an updated tarball of hurd-cross (hurdX): Hopefully the we are
getting closer to upload now.

(file #54322)

___

Additional Item Attachment:

File name: hurd-cross.tar.gz  Size:64 KB




___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Samuel Thibault]

Follow-up Comment #31, sr #110199 (project administration):

Well, the latest comment from Ineiev was telling he was waiting for a new
fixed tarball.


___

Reply to this item at:

  

___
Message posté via Savannah
https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #30, sr #110199 (project administration):

Hi again.

Is this support issue still open? If so I plan to upload an updated tarball
RSN.

Thanks!


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #29, sr #110199 (project administration):

Hello,

Thanks for the heads up. A new tarball will be uploaded soon.

Thanks!

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Update of sr #110199 (project administration):

  Status: In Progress => Need Info  
 Open/Closed:Open => Closed 

___

Follow-up Comment #28:

No response, closing; feel free to submit a fixed tarball.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Samuel Thibault]

Follow-up Comment #27, sr #110199 (project administration):

Svante: perhaps there's a misunderstanding due to the common contribution
process.

You wrote: "I have now added Copyright and License information to all files
where it is needed."

The thing is: it's needed everywhere.

You also wrote: "If a patch for example does not
change the copyright and license information does not have to change at all.
Or do you mean the files I created?"

Even if a patch does not change the copyright/licence of the file it is
supposed to be applied on, there *is* copyright and licence information to be
given on the *patch* itself.

Usually when contributing to a project, people don't bother expliciting under
which licence the patch is provided under, and the assumption is that it's
under the licence of the file being patched.

But here you can't go that way, since the patch could remain for some time in
this proposed repo, and thus effectively living its own live, independently
from what happens to the file that it's supposed to patch.

So I guess there is a misunderstanding on *what* has to be maintained rather
than a question of commitment.

Put another way: yes, add a licence notice on each patch file (basically the
licence of the file being patched, as that licence was at the time when the
patch was created, since it is at that time that the creator of the patch read
and agreed the licence under which that file was). And add a copyright notice
on each patch file as well, to remember who created the patch and thus holds
copyright on the patch (which will be needed anyway when trying to merge the
patch upstream).


Note: yes, for instance Debian does not usually keep a licence note in the
patch queues that it maintains, but the GNU standards are higher than this.

___

Reply to this item at:

  

___
  Message posté via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Follow-up Comment #26, sr #110199 (project administration):

Not yet, sorry.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #25, sr #110199 (project administration):

Hi Ineiev,

Any results from your discussions with Samuel?

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Follow-up Comment #24, sr #110199 (project administration):

I'm discussing the situation with Samuel.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #23, sr #110199 (project administration):

ping?

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #22, sr #110199 (project administration):

Hi again.

I don't really understand what you mean by "confirm your commitment to
maintain these notices in the long run". If a patch for example does not
change the copyright and license information does not have to change at all.
Or do you mean the files I created? 

Of course I will maintain them long term. The idea is to maintain the
cross-hurd repository with git and update the involved packages consisting of
the environment regularly. For example glibc-2.30 is used in the tarball, but
2.31 is already released and will be upgraded to when the git repo is up and
running.
 
For your information, I have ported Ada, Go, etc to GNU/Hurd and contribute
regularly when additional patches are needed. Additionally, I have assigned
copyright to FSF for my contributions to Mig, GnuMach, Hurd, glibc gcc, and
gdb (if I remember correctly) and contribute to these packages regularly too.
Maybe Samuel Thibault  can help me to confirm my
commitment to GNU software.

Can you please be specific which files I missed and where the wrong things
are.

Thanks!

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Follow-up Comment #21, sr #110199 (project administration):

Yes, you've missed some files (and there are more wrong things).

You've made a few attempts to fix the issue; before you make further ones, I'd
like to see how you can confirm your commitment to maintain these notices in
the long run (rather than to fix just a single tarball in order to pass the
check).

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #20, sr #110199 (project administration):

Hi again. I have now added Copyright and License information to all files
where it is needed. Hopefully I have not missed any. Please let me know if I
did or if there is still something missing or in need of correction.

Thanks!

(file #49032)
___

Additional Item Attachment:

File name: hurd-cross.tar.gz  Size:80 KB




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Follow-up Comment #19, sr #110199 (project administration):

I believe this is my point: you are not sufficiently familiar with the task at
hand to understand the issue.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #18, sr #110199 (project administration):

ping?


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #17, sr #110199 (project administration):

Thanks for reopening #110199.

I don't really understand your comment #16. Do you mean that I should add
copyright and license information to all files in the patches directory? Or
the ones larger than 10 lines? If that is what you mean I'll do it.

(As a side note, Debian don't add these notices to their patches. Instead they
have a file called debian/copyright stating copyright and license for all
files in the source and debian directories of the package. In my opinion this
is more handy than to add that info to each file in the patches directory.
Maybe create a separate copyright file in the patches directory?)

Thanks!

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Update of sr #110199 (project administration):

  Status: Wont Do => In Progress
 Open/Closed:  Closed => Open   

___

Follow-up Comment #16:

(For the reference: I've just checked file #48879 from sr #110224.)

It seems to me that you are not ready to maintain these notices properly in
the long run.  If you thought this issue to be important, you most probably
would follow my directions from comment #1 (which are based on the
documentation I linked to).

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #15, sr #110199 (project administration):

Please, I did submit a new tarball after sending that message. And commented
on your feedback. Please reopen this issue.

Thanks!

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #13, sr #110199 (project administration):

ping?

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #12, sr #110199 (project administration):

You are right,

coreutils/coreutils-8.23-noman-1.patch does not have a license. Looking more
closely at applied patches I found out that it is not needed. Just remove it
from the tarball.

Regrading the patches for glibc README.patches states:
All patches below are Copyright FSF.
git-ONSTACK.diff: GPLv2.1+ Patch by Samuel Thibault.
tg-mach-hurd-link.diff: GPLv2.1+ Patch by Samuel Thibault.
tg-hurdsig-fixes.diff: GPLv2.1+ Patch by Jeremy Koenig.
tg-hurdsig-global-dispositions.diff: GPLv2.1+ Patch by Jeremy Koenig.
tg-hurdsig-SA_SIGINFO.diff: GPLv2.1+ Patch by Jeremy Koenig.
tg-hurdsig-fixes-2.diff: GPLv2.1+ Patch by Jeremy Koenig.
tg-sigstate_thread_reference.diff: GPLv2.1+ Patch by Richard Braun.
glibc.git-0b262ca4c64cd9042576ddb9969607c0ea1187d7.patch: GPLv2.1+ Patch by
me.

Is that not enough? Or do you want me to add Copyright and License information
to that patch (or all the above patches?)

Thanks!

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Follow-up Comment #11, sr #110199 (project administration):

glibc/git-ONSTACK.diff is more than 10 lines long, but it has no copyright and
license notices (neither has coreutils/coreutils-8.23-noman-1.patch, in fact).

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #10, sr #110199 (project administration):

Hi again,

As explained in patches/README.patches most patches are smaller than 10 lines,
and therefore does not need to have Copyright information. They are denoted
SHORT in that file.

The longer patches do have Copyright information:
coreutils/coreutils-8.23-noman-1.patch
gcc/fixinc_glimits.h.diff
glibc/local-remove-manual.diff
glibc/tg-hurdsig-SA_SIGINFO.diff

Thanks!

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Follow-up Comment #9, sr #110199 (project administration):

Sorry for the delay.

[comment #7 comment #7:]
> 
> This time I've tried to comply with all your requests of Copyright and
License info. Please le me know if something is still missing.
> Attaching an updated tarball: hurd-cross.tar.gz.

I'm afraid you haven't complied: patch files contain no copyright and license
notices.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #8, sr #110199 (project administration):

ping!

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #7, sr #110199 (project administration):

Hi again.

This time I've tried to comply with all your requests of Copyright and License
info. Please le me know if something is still missing.
Attaching an updated tarball: hurd-cross.tar.gz.

Thanks!

(file #48777)
___

Additional Item Attachment:

File name: hurd-cross.tar.gz  Size:75 KB




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #6, sr #110199 (project administration):

Hi Inieiev,

I'll make one more effort to to comply to your requirements. If you reject the
next tarball, I'll publish the project elsewhere, gitlab or github (god
forgive) :(



___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Follow-up Comment #5, sr #110199 (project administration):

Patches are text files, and their format easily allows for comments;
therefore, copyright and license notices should be written in each file
itself.

I'd like to note that patches/README.patches in fact contains no copyright
information: copyright lines look like

Copyright (C) 1989 John Smith


I think you should really read the documentation linked from my comment #1
carefully in order to learn how to properly arrange your files.  I just can't
write down all necessary details here.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #4, sr #110199 (project administration):

[comment #3 comment #3:]
> 
> [comment #2 comment #2:]
> > Regarding patches in the patches directory, it does not make sense to add
copyright notices.
> 
> Why not?

I have now added Copyright info to the patches directory, see
hurd-cross/patches/README.patches. I hope this is good so I can upload the
project to Savannah. I'm attaching an updated tarball: hurd-cross.tar.gz.

Thanks!

(file #48748)
___

Additional Item Attachment:

File name: hurd-cross.tar.gz  Size:80 KB




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Follow-up Comment #3, sr #110199 (project administration):


[comment #2 comment #2:]
> Regarding patches in the patches directory, it does not make sense to add
copyright notices.

Why not?

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

Follow-up Comment #2, sr #110199 (project administration):

Hello,

Regarding patches in the patches directory, it does not make sense to add
copyright notices. Therefore I have created the README.patches file under
patches. It is a lot of work to create a README.patches for every
sub-directory.

Do you want me to add a copyright notice in every READ.* file?

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Ineiev]

Update of sr #110199 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

So, since you attached your tarball, I've actually looked into it.

Please make sure that all copyrightable files in it, including READMEs and
patches, have valid copyright and license notices
.  The notices could only
be moved to a README file in the same directory with the files in question if
those files have a format that doesn't allow for comments.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/

[sr #110199] Cross-building of GNU/Hurd and additional packages

[Svante Signell]

URL:
  

 Summary: Cross-building of GNU/Hurd and additional packages
 Project: Savannah Administration
Submitted by: gnu_srs
Submitted on: Tue 18 Feb 2020 10:09:24 AM UTC
Category: Source code repositories - developer access
Priority: 5 - Normal
Severity: 3 - Normal
  Status: None
 Assigned to: None
Originator Email: svante.sign...@gmail.com
Operating System: GNU/Linux
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

hurd-cross is a project for cross-building GNU/Hurd and other packages using
e.g. an GNU/Linux host. It contains mainly of a number of bash scripts, for
download, bootstrap and compile dependant packages for GNU/Hurd, as well as
other packages to build and run on the built image. The scripts downloads and
patches source packages, bootstraps the dependant packages for building Hurd,
compiles and installs the cross-built packages and finally creates an image of
GNU/Hurd to be run e.g. in a Virtual Machine (VM). In an extension the number
of built packages can be cross-built to create other packages not yet
available natively on GNU/Hurd.



___

File Attachments:


---
Date: Tue 18 Feb 2020 10:09:24 AM UTC  Name: hurd-cross.tar.gz  Size: 74KiB  
By: gnu_srs



___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/