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

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.

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

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 abov

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

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 ab

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

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

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

Update of sr #110199 (project administration): Status: In Progress => Need Info Open/Closed:Open => Closed ___ Follow-up Comment #34: Some files

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

Update of sr #110199 (project administration): Status: Need Info => In Progress Open/Closed: Closed => Open ___ Reply to this item at:

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

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: ___

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

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 nam

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

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: _

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

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: _

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

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:

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

Update of sr #110199 (project administration): Status: In Progress => Need Info Open/Closed:Open => Closed ___ Follow-up Comment #28: No response

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

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: "

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

Follow-up Comment #26, sr #110199 (project administration): Not yet, sorry. ___ Reply to this item at: ___ Message sent via Savannah https://s

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

Follow-up Comment #25, sr #110199 (project administration): Hi Ineiev, Any results from your discussions with Samuel? ___ Reply to this item at:

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

Follow-up Comment #24, sr #110199 (project administration): I'm discussing the situation with Samuel. ___ Reply to this item at: ___ Message sen

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

Follow-up Comment #23, sr #110199 (project administration): ping? ___ Reply to this item at: ___ Message sent via Savannah https://savannah.no

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

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

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

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 (ra

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

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 #4

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

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:

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

Follow-up Comment #18, sr #110199 (project administration): ping? ___ Reply to this item at: ___ Message sent via Savannah https://savannah.n

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

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

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

Update of sr #110199 (project administration): Status: Wont Do => In Progress Open/Closed: Closed => Open ___ Follow-up Comment #16: (For the re

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

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:

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

Follow-up Comment #13, sr #110199 (project administration): ping? ___ Reply to this item at: ___ Message sent via Savannah https://savannah.no

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

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 st

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

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

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

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: c

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

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

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

Follow-up Comment #8, sr #110199 (project administration): ping! ___ Reply to this item at: ___ Message sent via Savannah https://savannah.non

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

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) _

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

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) :( ___

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

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: c

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

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

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

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:

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

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. D

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

Update of sr #110199 (project administration): Status:None => In Progress Assigned to:None => ineiev ___ Follow-up Comment #1: So, since yo

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

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: