[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2015-07-21 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 Miroslav Suchý msu...@redhat.com changed: What|Removed |Added Blocks|177841 (FE-NEEDSPONSOR) | Referenced Bugs:

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-12-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 Ma Kai crtm...@gmail.com changed: What|Removed |Added Status|NEW |CLOSED

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-10-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 --- Comment #8 from Dominik 'Rathann' Mierzejewski domi...@greysector.net --- Hello Ma Kai, FPC member here. (In reply to Ma Kai from comment #4) Thanks for your review. tclbsd says it works under tcl8.5, But the guidelines indicated there

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-10-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 --- Comment #9 from Ma Kai crtm...@gmail.com --- (In reply to Dominik 'Rathann' Mierzejewski from comment #8) It's not forbidden to make a package that works with both 8.5 and 8.6. My bad... I misunderstood the guidelines. Sorry! Package now

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-10-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 --- Comment #7 from Ma Kai crtm...@gmail.com --- Thanks for your reviews. These problems are fixed. (I reported the permission problem to the upstream as well.) Spec URL: https://raw.githubusercontent.com/ekd123/fedora/master/tcl-tclbsd.spec

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-10-12 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 --- Comment #5 from Piotr Popieluch piotr1...@gmail.com --- Hi Ma Kai, Looks good! I've looked into the symbols issue, I don't really understand why it doesn't strip the library correctly... Don't think this is a blocker though. What you

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-10-12 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 Orion Poplawski or...@cora.nwra.com changed: What|Removed |Added CC|

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-10-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 --- Comment #1 from Ma Kai crtm...@gmail.com --- [mkai@localhost SPECS]$ rpmlint tcl-tclbsd.spec ../SRPMS/* ../RPMS/*/* tcl-tclbsd.x86_64: W: unstripped-binary-or-object /usr/lib64/tcl8.6/BSD1.6/libBSD1.6.so tcl-tclbsd.x86_64: W:

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-10-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 Ma Kai crtm...@gmail.com changed: What|Removed |Added Blocks||177841 (FE-NEEDSPONSOR)

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-10-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 --- Comment #2 from Ma Kai crtm...@gmail.com --- Just to clarify, though this library is intended originally for BSD, it does work well on Linux. Only one function isn't supported (according to my simple experiment). -- You are receiving

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-10-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 Piotr Popieluch piotr1...@gmail.com changed: What|Removed |Added CC|

[Bug 1151759] Review Request: tclbsd - Interfacing to various BSD UNIX system calls and routines

2014-10-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1151759 --- Comment #4 from Ma Kai crtm...@gmail.com --- Hi Piotr, Thanks for your review. tclbsd says it works under tcl8.5, But the guidelines indicated there is only one possibility for one package [1]. To avoid breaking the guidelines, I have to