3:59 p.m.
Hello List,
I'm a newcomer to this list. My native language is french, so forgive me
if my English is not correct at all. I'm also a newcomer to the
packaging activity by becoming the co-maintainer of Sinha Ankur on
broadcom-wl and wl-kmod packages for Fedora 15. As suggested on the
contributors page of the RPMFusion site, here's the thread containing
the package change request:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1907)
As a newcomer, I need someone to sponsor me to this new activity. Maybe
my co-maintainer could accept to do so. Thanks in advance for sponsoring
me.
I will certainly have a few naive questions to ask after reading the
documentation on setting-up my environment to begin to contribute, most
probably on the ssh/cvs-connection part. Thanks in advance for your
advice.
All questions or comments on this subject are welcome.
Cordially,
--
Nicolas Viéville
6:22 p.m.
2011/10/16 Nicolas Viéville <nicolas.vieville(a)univ-valenciennes.fr>:
Hello List,
I'm a newcomer to this list. My native language is french, so forgive me
if my English is not correct at all. I'm also a newcomer to the
packaging activity by becoming the co-maintainer of Sinha Ankur on
broadcom-wl and wl-kmod packages for Fedora 15. As suggested on the
contributors page of the RPMFusion site, here's the thread containing
the package change request:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1907)
As a newcomer, I need someone to sponsor me to this new activity. Maybe
my co-maintainer could accept to do so. Thanks in advance for sponsoring
me.
I will certainly have a few naive questions to ask after reading the
documentation on setting-up my environment to begin to contribute, most
probably on the ssh/cvs-connection part. Thanks in advance for your
advice.
All questions or comments on this subject are welcome.
Hello Nicolas,
You need to create an account on fas.rpmfusion.org.
I will review your spec changes for the wl-kmod and broadcom-wl modules.
First it would be nice if you can make a unified diff from the
previous spec file.
If you have any question, you can ask on #fedora-devel-fr, ... in french.
Thx for joining RPM Fusion.
Nicolas (kwizart)
8:35 a.m.
Hello Nicolas,
You need to create an account on fas.rpmfusion.org.
I'll check the documentation to do that as soon as possible.
I will review your spec changes for the wl-kmod and broadcom-wl
modules.
First it would be nice if you can make a unified diff from the
previous spec file.
Thanks for your review and the tip. If I understand correctly the diff
command would be "diff -u old new" or you need some more switches in
general to the diff command (for example: diff -Naur)?
If you have any question, you can ask on #fedora-devel-fr, ... in
french.
I have to check that too! I'm not a regular user of IRC, so see you on
#fedora-devel-fr when all this will be ready.
Thx for joining RPM Fusion.
Thanks for your response and your help!
--
Nicolas
9:16 p.m.
Salut Nicolas !
Welcome !
++
----- Mail original -----
De: "Nicolas Viéville" <nicolas.vieville(a)univ-valenciennes.fr>
À: "RPMFusion Devlopers" <rpmfusion-developers(a)lists.rpmfusion.org>
Envoyé: Dimanche 16 Octobre 2011 17:59:12
Objet: Newcomer
Hello List,
I'm a newcomer to this list. My native language is french, so forgive me
if my English is not correct at all. I'm also a newcomer to the
packaging activity by becoming the co-maintainer of Sinha Ankur on
broadcom-wl and wl-kmod packages for Fedora 15. As suggested on the
contributors page of the RPMFusion site, here's the thread containing
the package change request:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1907)
As a newcomer, I need someone to sponsor me to this new activity. Maybe
my co-maintainer could accept to do so. Thanks in advance for sponsoring
me.
I will certainly have a few naive questions to ask after reading the
documentation on setting-up my environment to begin to contribute, most
probably on the ssh/cvs-connection part. Thanks in advance for your
advice.
All questions or comments on this subject are welcome.
Cordially,
--
Nicolas Viéville
12:22 a.m.
Nicolas Viéville wrote:
Thanks for your review and the tip. If I understand correctly the
diff
command would be "diff -u old new" or you need some more switches in
general to the diff command (for example: diff -Naur)?
diff -u is sufficient to diff 2 individual files.
The other letters in the often used -Naur are:
* -r = recursive, should always be used when diffing directories (i.e. use
diff -ur as a minimum in that case).
* -N = includes files which are only in either of the 2 directories,
treating them as added or removed. Needed if you added or removed any files,
but unwanted if one directory has object files, executables or some other
generated files and the other does not.
* -a = includes all files, even if diff thinks they're binary. Usually a bad
idea (especially if there are object/executable files or other such
generated binaries in your directories), but sometimes diff might think a
file is binary when it isn't really (e.g. because it's an FSF text file with
"form feed" characters in them (I haven't seen anybody else use form feeds
for years, but the FSF still uses them for some reason)).
Kevin Kofler
7:35 a.m.
On Wed, 2011-10-19 at 10:35 +0200, Nicolas Viéville wrote:
Hello Nicolas,
<snippy>
Hi Nicolas,
I'm sorry I've been a little aloof these couple of days. I was going
through wl-kmod last night when I came across this post.
If you need any assistance with the spec etc, please feel free to ping
me on the irc. I'm around on quite a few fedora channels and the
rpmfusion channel. My irc is "FranciscoD"
--
Thanks,
Regards,
Ankur: "FranciscoD"
http://fedoraproject.org/wiki/User:Ankursinha
http://dodoincfedora.wordpress.com/
10:11 a.m.
Hello Hankur,
I'm sorry I've been a little aloof these couple of days. I
was going
through wl-kmod last night when I came across this post.
If you need any assistance with the spec etc, please feel free to ping
me on the irc. I'm around on quite a few fedora channels and the
rpmfusion channel. My irc is "FranciscoD"
Thanks for your proposition for help. I would not miss to ping you if
needed!
I'll try to make the spec file these next days.
--
Nicolas Viéville
10:15 a.m.
Hello Kevin,
diff -u is sufficient to diff 2 individual files.
The other letters in the often used -Naur are:
* -r = recursive, should always be used when diffing directories (i.e. use
diff -ur as a minimum in that case).
* -N = includes files which are only in either of the 2 directories,
treating them as added or removed. Needed if you added or removed any files,
but unwanted if one directory has object files, executables or some other
generated files and the other does not.
* -a = includes all files, even if diff thinks they're binary. Usually a bad
idea (especially if there are object/executable files or other such
generated binaries in your directories), but sometimes diff might think a
file is binary when it isn't really (e.g. because it's an FSF text file with
"form feed" characters in them (I haven't seen anybody else use form feeds
for years, but the FSF still uses them for some reason)).
Thanks for this precision! I'll use your advises in the futur.
--
Nicolas Viéville
12:55 p.m.
Hello Nicolas,
You need to create an account on fas.rpmfusion.org.
I've done this. As the rpmfusion page for contributors mention it I've
also "Applied for the cvsextras group" and my status is for now
"none".
I think I must wait to be "approved" before posting my spec file to the
CVS?
Is there anything special about this procedure I should be warned about
before... proceeding?
Thanks in advance for your response.
Cordially,
--
Nicolas Viéville
1:21 p.m.
2011/10/24 Nicolas Viéville <nicolas.vieville(a)univ-valenciennes.fr>:
Hello Nicolas,
> You need to create an account on fas.rpmfusion.org.
I've done this. As the rpmfusion page for contributors mention it I've
also "Applied for the cvsextras group" and my status is for now
"none".
I think I must wait to be "approved" before posting my spec file to the
CVS?
No, you don't need to be in approved state to submit a spec file for review.
Once your modification will be approved and the reviewer considers you
are capable to maintain a package, you will be approved into RPM
Fusion cvsextras group of contributors. Then an ACL request need to be
done for you to commit your changes into a given module yourself.
Once that said, gaining ACL rights on a package may be optional. If
you only want to provide a quick update once, you may only request the
primary maintainer to apply your changes.
The problem with the wl-kmod package is about to know who is the
actual primary maintainer, and if none feels responsible maintaining
the package (such as answering bug reports and fixing bugs that
prevent continuation of service), then the package will be removed
because of lack of primary maintainer.
Nicolas (kwizart)
3:30 p.m.
Hi again,
> I think I must wait to be "approved" before posting my
spec file to the
> CVS?
No, you don't need to be in approved state to submit a spec file for review.
Once your modification will be approved and the reviewer considers you
are capable to maintain a package, you will be approved into RPM
Fusion cvsextras group of contributors. Then an ACL request need to be
done for you to commit your changes into a given module yourself.
Ok!
Once that said, gaining ACL rights on a package may be optional. If
you only want to provide a quick update once, you may only request the
primary maintainer to apply your changes.
The problem with the wl-kmod package is about to know who is the
actual primary maintainer, and if none feels responsible maintaining
the package (such as answering bug reports and fixing bugs that
prevent continuation of service), then the package will be removed
because of lack of primary maintainer.
As a newcomer, I'm not sure I'm the first person to be the primary
maintainer. But, if Ankur Sinha is Ok for that, I'll try to do this
(with his help probably). How do I proceed to ask for being the primary
maintainer?
I've tried to connect to the CVS as described in the rpmfusion
contributors page, but I get this message after a "cvs co common" :
ssh_exchange_identification: Connection closed by remote host
I have to precise that I've made a few tries before with no result,
because of a malformed CVSROOT environment variable. So maybe my account
is blocked. Is opening a new thread in this list is the procedure to
unblock it?
Thanks in advance for your responses!
To end with a positive note, as soon as it will be possible, I could
upload the wl-kmod.spec file and the broadcom-wl.spec file in their
upstream version (ie 5.100.82.111) for a review.
Cordially,
--
Nicolas Viéville
7:25 p.m.
New subject: Newcomer - Package Reviews
On 25/10/11 02:30, Nicolas Viéville wrote:
>> I think I must wait to be "approved" before posting
my spec file to the
>> CVS?
>
> No, you don't need to be in approved state to submit a spec file for review.
> Once your modification will be approved and the reviewer considers you
> are capable to maintain a package, you will be approved into RPM
> Fusion cvsextras group of contributors. Then an ACL request need to be
> done for you to commit your changes into a given module yourself.
Further to kwizart's response:
For a new or retired package, we review both the package and the
proposed maintainer via an RPM Fusion bug Review Request. An example is
here:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1992
and the process to follow is part of the page:
http://rpmfusion.org/Contributors
http://rpmfusion.org/Contributors#head-0df093adde5a77a5e0569b2460ff49d078...
So I would suggest the same method, even though this is an "almost"
existing package, ie post the .spec and srpm, and show that you have
built it in mock.
(Note that RPM Fusion's package maintenance process matches Fedora's old
process from quite a few years ago).
6 a.m.
New subject: Newcomer - Package Reviews
Further to kwizart's response:
For a new or retired package, we review both the package and the
proposed maintainer via an RPM Fusion bug Review Request. An example is
here:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1992
and the process to follow is part of the page:
http://rpmfusion.org/Contributors
http://rpmfusion.org/Contributors#head-0df093adde5a77a5e0569b2460ff49d078...
So I would suggest the same method, even though this is an "almost"
existing package, ie post the .spec and srpm, and show that you have
built it in mock.
(Note that RPM Fusion's package maintenance process matches Fedora's old
process from quite a few years ago).
Thanks! That's exactly what I was missing in the process, specially
informations from the example.
4573
days inactive
4582
days old
rpmfusion-developers@lists.rpmfusion.org
13 comments
6 participants
participants (6)
-
Agnes Jones -
Ankur Sinha -
deogracia＠free.fr -
Kevin Kofler -
Nicolas Chauvet -
Nicolas Viéville