from:"Ineiev"

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

2021-01-29 Thread Ineiev

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

2023-02-09 Thread Ineiev

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

2023-02-13 Thread Ineiev

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

2023-02-17 Thread 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 ab

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

2023-02-23 Thread 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.

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

2020-02-18 Thread Ineiev

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

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

2020-02-19 Thread 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:

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

2020-04-05 Thread 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: c

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

2020-04-13 Thread 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

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

2020-04-14 Thread 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

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

2020-04-21 Thread Ineiev

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

2020-04-28 Thread 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:

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

2020-05-21 Thread 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 (ra