RFS: setserial -- Controls configuration of serial ports

2005-11-14 Thread Jonas Genannt


Hello,

I searching an sponsor for the setserial package.

* Package name  : setserial
  Version   : 2.17
* License   : GPL
  Description   : Controls configuration of serial ports

 Set and/or report the configuration information associated with
 a serial port. This information includes what I/O port and which IRQ
 a particular serial port is using.
 .
 This version has a completely new approach to configuration, so if you
 have a setup other than the standard ttyS0 and 1, you will have to get
 your hands dirty.
 .
 By default, only COM1-4 are configured by the kernel, using IRQ 3 and 
4.

 If you have other serial ports (such as an AST Fourport card), or
 if you have mapped the IRQs differently (perhaps COM3 and 4 to other
 IRQs to allow concurrent access with COM1 and 2) then you must have this
 package.



ITA: #285355


The new debian version of this package fixes some wish list bugs and 
some lintian errors.


You can find the source here:
http://jonas.capi2name.de/setserial/


Greets,
Jonas


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: setserial -- Controls configuration of serial ports (2nd try)

2005-03-13 Thread Philipp Kern
On 11 Mar 2005, at 08:29, Jan Zizka wrote:
BTW at least when I have re-duploaded those corrections to 
mentors.debian.net
the package was updated just fine even thow the revision didn't change.
I would actually expect what you have described but seems that it's not
like that.
Mentors uses the simple dinstall method but the Debian archive has a 
full-fledged dak running. So you would not be able to change something 
in a revision already uploaded to the official archives.

Regards,
Philipp Kern


PGP.sig
Description: This is a digitally signed message part


RFS: setserial -- Controls configuration of serial ports (2nd try)

2005-03-10 Thread Jan Zizka
Hi,

I would like to adopt existing setserial Debian package.
Could somebody check my new release of the package and sponsor it?

setserial
-
Controls configuration of serial ports.

Set and/or report the configuration information associated with 
a serial port. This information includes what I/O port and which 
IRQ a particular serial port is using.

This version has a completely new approach to configuration, so 
if you have a setup other than the standard ttyS0 and 1, you will 
have to get your hands dirty.

By default, only COM1-4 are configured by the kernel, using 
IRQ 3 and 4. If you have other serial ports (such as an AST Fourport 
card), or if you have mapped the IRQs differently (perhaps COM3 
and 4 to other IRQs to allow concurrent access with COM1 and 2) 
then you must have this package. 

setserial is released under GNU GPL.

New release 2.17-41 can be obtained sfrom following source archive:

deb-src http://mentors.debian.net/debian unstable main contrib non-free

(http://mentors.debian.net/debian/pool/main/s/setserial/)

For clarity here is changelog:

setserial (2.17-41) unstable; urgency=low

  * Closes: #276667: Czech translation of setserial debconf messages
Already fixed in 2.17-40, just closing bug report.
  * Added printing of 'divisor' when 'spd_cust' is set and -G
option is used. Based on patch attached by Ian Abbott 
[EMAIL PROTECTED] to bugreport [447228] 
at SourceForge.net
  * In upstream README file corrected chkconfig option -add to --add
  * New maintainer. (Closes: #285355: RFA: setserial -- Controls
configuration of serial ports)

 -- Jan Zizka [EMAIL PROTECTED]  Wed,  9 Mar 2005 20:51:16 +0200

I have already retitled bug report #285355 to ITA:.

Regards
   Ziza


signature.asc
Description: Digital signature


Re: RFS: setserial -- Controls configuration of serial ports (2nd try)

2005-03-10 Thread Matthew Palmer
On Thu, Mar 10, 2005 at 10:44:41PM +0200, Jan Zizka wrote:
 setserial (2.17-41) unstable; urgency=low
 
   * Closes: #276667: Czech translation of setserial debconf messages
 Already fixed in 2.17-40, just closing bug report.

Don't do this.  If it isn't fixed in the changes described by this
changelog, don't close the bug in the changelog.  Instead, mail
[EMAIL PROTECTED] and describe the reason why it should be closed as fixed
in 2.17-40 but not closed at upload.

   * New maintainer. (Closes: #285355: RFA: setserial -- Controls
 configuration of serial ports)

I'd be inclined to put this entry first, as it is common practice.

- Matt


signature.asc
Description: Digital signature


Re: RFS: setserial -- Controls configuration of serial ports (2nd try)

2005-03-10 Thread Jan Zizka
Hi,

On Fri, Mar 11, 2005 at 09:30:35AM +1100, Matthew Palmer wrote:
 On Thu, Mar 10, 2005 at 10:44:41PM +0200, Jan Zizka wrote:
  setserial (2.17-41) unstable; urgency=low
  
* Closes: #276667: Czech translation of setserial debconf messages
  Already fixed in 2.17-40, just closing bug report.
 
 Don't do this.  If it isn't fixed in the changes described by this
 changelog, don't close the bug in the changelog.  Instead, mail
 [EMAIL PROTECTED] and describe the reason why it should be closed as fixed
 in 2.17-40 but not closed at upload.

Thanks for pointing this out. I've done it only because I have seen this
in some other packages. Now I went back to developers reference [5.8.4]
and it's stated clearly there. Now the bug is closed.

* New maintainer. (Closes: #285355: RFA: setserial -- Controls
  configuration of serial ports)
 
 I'd be inclined to put this entry first, as it is common practice.

How about folowing:

setserial (2.17-41) unstable; urgency=low

  * New maintainer. (Closes: #285355: RFA: setserial -- Controls
configuration of serial ports)
  * Added printing of 'divisor' when 'spd_cust' is set and -G
option is used. Based on patch attached by Ian Abbott 
[EMAIL PROTECTED] to bugreport [447228] 
at SourceForge.net
  * In upstream README file corrected chkconfig option -add to --add

 -- Jan Zizka [EMAIL PROTECTED]  Wed,  9 Mar 2005 20:51:16 +0200

Originally I had that entry first, but seems that I have changed
the order during some editing (thow I used 'dch' mostly).

I have uploaded corrected sources to:

deb-src http://mentors.debian.net/debian unstable main contrib non-free

BTW was I supposed to increase the version number to something 
like 2.17-41.1 if previous package would have been put to official
archive?

Thanks :)
   Ziza



signature.asc
Description: Digital signature


Re: RFS: setserial -- Controls configuration of serial ports (2nd try)

2005-03-10 Thread Sven Mueller
Jan Zizka wrote on 11/03/2005 00:41:
BTW was I supposed to increase the version number to something 
like 2.17-41.1 if previous package would have been put to official
archive?
More like 2.17-42 I would say, but yes. Though I'm no DD myself, the way 
I understood the tools, you can't upload the same revision twice (with 
different content) without asking FTP-masters to remove the older 
version first. Uploading a new revision is much easier and straight-forward.

cu,
sven
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Re: RFS: setserial -- Controls configuration of serial ports (2nd try)

2005-03-10 Thread Jan Zizka
On Fri, Mar 11, 2005 at 12:50:45AM +0100, Sven Mueller wrote:
 Jan Zizka wrote on 11/03/2005 00:41:
 BTW was I supposed to increase the version number to something 
 like 2.17-41.1 if previous package would have been put to official
 archive?
 
 More like 2.17-42 I would say, but yes. Though I'm no DD myself, the way 
 I understood the tools, you can't upload the same revision twice (with 
 different content) without asking FTP-masters to remove the older 
 version first. Uploading a new revision is much easier and straight-forward.

Yes that would be other option, but actually I have been changing changelog 
entriese for 2.17-41 not adding anyhing new. I guess that I shouldn't
do this at all when dealing with official archive.

BTW at least when I have re-duploaded those corrections to mentors.debian.net
the package was updated just fine even thow the revision didn't change.
I would actually expect what you have described but seems that it's not
like that.

Regards
   Ziza


signature.asc
Description: Digital signature


RFS: setserial - Controls configuration of serial ports

2005-03-07 Thread Jan Zizka
Hi,

I would like to takeover the maintanence of setserial
package since it's current maintainer if looking for
a replacement.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285355

However I'm not a DD so I would need a sponsor.
Would there be anyone willing to help me?

Regards
 Ziza

- Forwarded message from Ola Lundqvist -

Hello

On Sun, Mar 06, 2005 at 06:50:11PM +0200, Jan Zizka wrote:
 Hi Ola,
 
 I have seen that you are looking for someone to take over
 the setserial Debian package. I'm Debian user for years
 and I would like to give something back. I use serial
 ports rather often, thow I don't have any special HW.
 I did not maintain any Debian package before, but as
 I checked this one is not very complex so it could be
 nice to start with it.

This sounds really nice. Please go ahead.

Some things though.

Are you a debian developer?
Or can you get someone else to sponsor you?

Regards,

// Ola

 Cheers
  Ziza

- End forwarded message -


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: setserial - Controls configuration of serial ports

2005-03-07 Thread Jan Zizka
Hi,

On Mon, Mar 07, 2005 at 07:43:06PM +0100, Bartosz Fenski aka fEnIo wrote:
 On Mon, Mar 07, 2005 at 07:03:59PM +0200, Jan Zizka wrote:
  I would like to takeover the maintanence of setserial
  package since it's current maintainer if looking for
  a replacement.
  
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285355
  
  However I'm not a DD so I would need a sponsor.
  Would there be anyone willing to help me?
 
 Request for sponsor for some package should contain:
 
 1) description of package

I thought that this is already debian package that I don't have
to repeat the same info, but here is link with description:

http://packages.debian.org/stable/base/setserial

 2) url to prepared package

non except official ones done by current maintainer.
http://packages.qa.debian.org/s/setserial.html

 and when it's adoption would be great to see
 
 3) changelog, preferably with some fixes for outstanding bugs

there are no outstanding bugs reported so there is nothing
to fix at the moment. Does this mean that we, me and current
maintainer, should wait for some outstadnig bug before he
could hand the package to me? Or what should be the procedure?

Cheers
 Ziza


signature.asc
Description: Digital signature


Re: RFS: setserial - Controls configuration of serial ports

2005-03-07 Thread Bartosz Fenski aka fEnIo
On Mon, Mar 07, 2005 at 09:49:45PM +0200, Jan Zizka wrote:
   However I'm not a DD so I would need a sponsor.
   Would there be anyone willing to help me?
  
  Request for sponsor for some package should contain:
  
  1) description of package
 
 I thought that this is already debian package that I don't have
 to repeat the same info, but here is link with description:
 
 http://packages.debian.org/stable/base/setserial

Well you're looking for sponsor right? You should prepare request that
will make it easier for eventual sponsors to get know as much as possible 
about package here.

At least that's my opinion ;)

  2) url to prepared package
 
 non except official ones done by current maintainer.
 http://packages.qa.debian.org/s/setserial.html

Why? If you're going to adopt it then please use procedure for this.
http://www.debian.org/devel/wnpp/

Hint: You should prepare package which will close RFA with changelog entry.
 
  and when it's adoption would be great to see
  
  3) changelog, preferably with some fixes for outstanding bugs
 
 there are no outstanding bugs reported so there is nothing
 to fix at the moment. Does this mean that we, me and current
 maintainer, should wait for some outstadnig bug before he
 could hand the package to me? Or what should be the procedure?

Procedure is mentioned at WNPP pages. And there is some bugreport against
setserial. Wishlist with updated translation, but it's still bugreport ;)

So the correct way of adopting would be to prepare new revision of package
with fixed bug and changelog entry which will close RFA.

regards
fEnIo
-- 
  ,''`.  Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo
 : :' :   32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland
 `. `'   phone:+48602383548 | proud Debian maintainer and user
   `-  http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001


signature.asc
Description: Digital signature


Re: RFS: setserial - Controls configuration of serial ports

2005-03-07 Thread Jan Zizka
Hi,

On Mon, Mar 07, 2005 at 09:45:07PM +0100, Bartosz Fenski aka fEnIo wrote:
   1) description of package
  
  I thought that this is already debian package that I don't have
  to repeat the same info, but here is link with description:
  
  http://packages.debian.org/stable/base/setserial
 
 Well you're looking for sponsor right? You should prepare request that
 will make it easier for eventual sponsors to get know as much as possible 
 about package here.
 
 At least that's my opinion ;)

Yes that correct. Thanks for the point, you are right.

   2) url to prepared package
  
  non except official ones done by current maintainer.
  http://packages.qa.debian.org/s/setserial.html
 
 Why? If you're going to adopt it then please use procedure for this.
 http://www.debian.org/devel/wnpp/
 
 Hint: You should prepare package which will close RFA with changelog entry.
  
   3) changelog, preferably with some fixes for outstanding bugs
  
  there are no outstanding bugs reported so there is nothing
  to fix at the moment. Does this mean that we, me and current
  maintainer, should wait for some outstadnig bug before he
  could hand the package to me? Or what should be the procedure?
 
 Procedure is mentioned at WNPP pages. And there is some bugreport against
 setserial. Wishlist with updated translation, but it's still bugreport ;)

Yes but that is already added in 2.17-40.

 So the correct way of adopting would be to prepare new revision of package
 with fixed bug and changelog entry which will close RFA.

Yes but for this I would have to be already a DD. Since I'm not I'll have
to find a sponsor first. But I'll try to seach if there is any other wish,
which I could implement and make the package fist and come back with it :))

Thanks a lot for your insight!

Cheers
  Ziza



signature.asc
Description: Digital signature


Re: RFS: setserial - Controls configuration of serial ports

2005-03-07 Thread Ola Lundqvist
Hello

On Mon, Mar 07, 2005 at 11:09:34PM +0200, Jan Zizka wrote:
*CUT*
 Yes but that is already added in 2.17-40.
 
  So the correct way of adopting would be to prepare new revision of package
  with fixed bug and changelog entry which will close RFA.
 
 Yes but for this I would have to be already a DD. Since I'm not I'll have
No actually not.

 to find a sponsor first. But I'll try to seach if there is any other wish,
 which I could implement and make the package fist and come back with it :))
 
 Thanks a lot for your insight!

So prepare a package that close that bug at least.

Regards,

// Ola

 Cheers
   Ziza
 



-- 
 --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering 
/  [EMAIL PROTECTED]   Annebergsslingan 37\
|  [EMAIL PROTECTED]   654 65 KARLSTAD|
|  http://www.opal.dhs.org   Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: RFS: setserial - Controls configuration of serial ports

2005-03-07 Thread Bartosz Fenski aka fEnIo
On Mon, Mar 07, 2005 at 11:09:34PM +0200, Jan Zizka wrote:
  Procedure is mentioned at WNPP pages. And there is some bugreport against
  setserial. Wishlist with updated translation, but it's still bugreport ;)
 
 Yes but that is already added in 2.17-40.

So I see no reason for keeping this bugreport open. It should be closed or
at least tagged as sarge related.  

  So the correct way of adopting would be to prepare new revision of package
  with fixed bug and changelog entry which will close RFA.
 
 Yes but for this I would have to be already a DD. Since I'm not I'll have
 to find a sponsor first. But I'll try to seach if there is any other wish,
 which I could implement and make the package fist and come back with it :))

No. It's not find sponsor and then work on package. 
It's actually inverse order.

Noone will sponsor you or even promise sponsoring if you have nothing to
show. You don't have to be DD for preparing new revision of package. 
Only uploading part needs DD access, and you should ask for sponsor having
something to upload.

regards
fEnIo
-- 
  ,''`.  Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo
 : :' :   32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland
 `. `'   phone:+48602383548 | proud Debian maintainer and user
   `-  http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001


signature.asc
Description: Digital signature