Re: Please criticize the package I have been working on, https://github.com/pelliott80/simplescreenrecorder-dpm.git

2015-03-20 Thread Riley Baird 
  d/changelog:
  +You should only list versions of the package that will actually be in
  Debian, so get rid of the vivid entry.
  +The changes you make before the initial release generally aren't
  important enough to go in the changelog.
  +Generally, new packages should have priority low.
  *Close the ITP bug.
 
 Yes, but remember I don't own this bug, I want to
 show these change to upstream and the bug owner.
 Perhaps they will clone, or pull these changes.
 
 If I get it working, let them have the fun of
 closing the bug.

Sorry, I wasn't clear enough. What I meant was that the bug should be
closed automatically by an entry in d/changelog. A lintian tag
new-package-should-close-itp-bug has been created for this purpose.

You can close the bug by including something like:

* Initial release (Closes: #)

In fact, this is really the only entry that you should have in your
changelog for a new package.

  
  d/control:
  *Where is simplescreenrecorder-lib?
 
 This is a very important point. Usually, libs
 are more difficult... But often initial version
 is not bad. it is a good idea to insure easy update.

I'm not sure if you can do this, but I'm not sure. Perhaps someone else
on the list can advise you whether or not this is allowed?


pgpT9REQq5xFk.pgp
Description: PGP signature

Bug#779667: RFS: node-bluebird/2.9.13+dfsg-1 [ITP]

2015-03-20 Thread Ross Gammon 
Control: tags -1 moreinfo

Okay - it turns out that for node-bluebird to work in Debian, we need to
build the javascript using their build script, and thus need lots of
extra dependencies packaged.

I am working on these other packages, so this RFS is on hold for a bit.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#777651: RFS: syncterm/20141022+dfsg-1 [ITP]

2015-03-20 Thread Antti Järvinen 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ragnarok wrote:
 I am looking for a sponsor for my package syncterm

Great. I'm no DD so I can't sponsor your package but I can give
comments nonetheless. So, I have following things I don't understand:
 - Is there specific need to list libncurses etc. dependencies in 
   debian/control, should ${shlibs:Depends} take care of that? Or 
   you want a very specific version? Ncurses is still fairly standard
   stuff. 
 - The zmodem license is interesting as they say don't distributed
   modifications - does a patch count as modification? As a sw 
   developer I would say yes but someone else needs to clarify
   that. Anyway, if they say no modifications and then we find 
   urgent need to patch zmodem (say, a serious security flaw) then
   the options are to remove zmodem or remove whole package? .. is
   zmodem still in active development? I remember having used that
   after x- and ymodem protocols went out of fashion some ~20 years ago :)
 - Good: watch file is present
   Bad: according to uscan --report it points to no sw version

In addition to that, nothing big plugs my eye. Sw even builds, too bad
my supramodem2400 is out of service so I can't really really try it
out.

- --
Antti, former sysop of costellobox+several others

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Processed by Mailcrypt 3.5.8 http://mailcrypt.sourceforge.net/

iD8DBQFVDHrpUTdja+nNMWMRAtxuAJwLoOjqjPC1nzAqEHRdNw7FghY7JQCggCMO
22MI+KjyGOoq5OxVlwGQBR0=
=fNUu
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/21772.31492.861362.319...@muikku.katiska.org