Re: RFS: command-not-found

2007-07-04 Thread Joe Smith


Michael Vogt [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]

On Sun, Jul 01, 2007 at 10:46:13PM +0200, Julian Andres Klode wrote:

Christoph Haas wrote:
 On Sun, Jul 01, 2007 at 10:08:47PM +0200, Julian Andres Klode wrote:
 Dear mentors,

[..]

 It builds these binary packages:
 command-not-found - Suggest installation of packages in interactive 
 bash sessions

 command-not-found-data - Set of data files for command-not-found

 I just built and installed it. There is some funny whitespace in 
 between

 the messages:

 ===
 $ inetd
 Command 'inetd' is available in '/usr/sbin/inetd'
 The command could not be located because '/usr/sbin' is not i ncluded 
 in the PATH environment variable.
 This is most likely caused by the lack of administ rative priviledges 
 associated with your user account.

 bash: inetd: command not found
 ===

 i ncluded - included
 administ rative - administrative
 priviledges - privileges
Fixed.


I would like to merge the fix. Do you maintain the package is some
version control system? We use bzr so it might be a good fit for you
too to make merging easy.


 Did you talk to the Ubuntu maintainer already? Perhaps it make sense to
 join forces so that only one package is built?
He's CCed, so: mvo: What's your opinion?


I would really like to, but this can only work if we have a seperate
command-not-found-data source package because the mapping of
binary-package will differ from ubuntu to debian (even if it is
only a very minor difference in most cases).



As far as policy concerns, while it is not terribly common for -data 
packages to have sperate source packages, it is entriely allowable.
The main package can (assuming no differenced in Debian/Ubuntu policies) can 
automatically migrate from debian unstable (or however that system works), 
or have the same packed re-uploaded to Ubuntu.
One potential inconvience is that users are likely to report bugsd on the 
wrong package in the BTS in some cases (main package wehn the bug is in the 
data package), but that is not really a problem. Bugs can be re-assigned 
fairly easily.





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



Re: RFS: command-not-found

2007-07-03 Thread Michael Vogt
On Sun, Jul 01, 2007 at 10:46:13PM +0200, Julian Andres Klode wrote:
 Christoph Haas wrote:
  On Sun, Jul 01, 2007 at 10:08:47PM +0200, Julian Andres Klode wrote:
  Dear mentors,
[..]
  It builds these binary packages:
  command-not-found - Suggest installation of packages in interactive bash 
  sessions
  command-not-found-data - Set of data files for command-not-found
  
  I just built and installed it. There is some funny whitespace in between
  the messages:
  
  ===
  $ inetd
  Command 'inetd' is available in '/usr/sbin/inetd'
  The command could not be located because '/usr/sbin' is not i ncluded in 
  the PATH environment variable.
  This is most likely caused by the lack of administ rative priviledges 
  associated with your user account.
  bash: inetd: command not found
  ===
  
  i ncluded - included
  administ rative - administrative
  priviledges - privileges
 Fixed.

I would like to merge the fix. Do you maintain the package is some
version control system? We use bzr so it might be a good fit for you
too to make merging easy.

  Did you talk to the Ubuntu maintainer already? Perhaps it make sense to
  join forces so that only one package is built?
 He's CCed, so: mvo: What's your opinion?

I would really like to, but this can only work if we have a seperate
command-not-found-data source package because the mapping of 
binary-package will differ from ubuntu to debian (even if it is
only a very minor difference in most cases).

Cheers,
 Michael


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



Re: RFS: command-not-found

2007-07-02 Thread Julian Andres Klode
Justin Pryzby wrote:
 How does it compare with auto-apt?  This a shell-only implementation
 whereas auto-apt will find things which are accessed otherwise
 (perhaps not bad).
 
 
command-not-found is very similar to auto-apt check, but command-not-found
is easier and targeted at the end user. And it gives
more detailed output, like instructions on how to install the package.

-- 
Julian Andres Klode

IRC Nickname:   juliank (Debian/OFTC + Freenode)
Fellow of FSFE: https://www.fsfe.org/en/fellows/jak (No. 1049)
Debian Wiki:http://wiki.debian.org/JulianAndresKlode
Ubuntu Wiki:http://wiki.ubuntu.com/JulianAndresKlode
In Launchpad:   https://launchpad.net/~juliank
Packages Overv: http://qa.debian.org/[EMAIL PROTECTED]
Languages:  German, English, [bit French]



signature.asc
Description: OpenPGP digital signature


RFS: command-not-found

2007-07-01 Thread Julian Andres Klode
Dear mentors,

I am looking for a sponsor for my package command-not-found.

* Package name: command-not-found
  Version : 0.2.4+debian-1
  Upstream Author : Zygmunt Krynicki [EMAIL PROTECTED]
Michael Vogt [EMAIL PROTECTED]
* URL : https://launchpad.net/command-not-found
* License : GPL
  Section : admin

It builds these binary packages:
command-not-found - Suggest installation of packages in interactive bash 
sessions
command-not-found-data - Set of data files for command-not-found

The package appears to be lintian clean.

The upload would fix these bugs: 418613

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/c/command-not-found
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/c/command-not-found/command-not-found_0.2.4+debian-1.dsc

I would be glad if someone uploaded this package for me.

Kind regards
 Julian Andres Klode

-- 
Julian Andres Klode

IRC Nickname:   juliank (Debian/OFTC + Freenode)
Fellow of FSFE: https://www.fsfe.org/en/fellows/jak (No. 1049)
Debian Wiki:http://wiki.debian.org/JulianAndresKlode
Ubuntu Wiki:http://wiki.ubuntu.com/JulianAndresKlode
In Launchpad:   https://launchpad.net/~juliank
Packages Overv: http://qa.debian.org/[EMAIL PROTECTED]
Languages:  German, English, [bit French]



signature.asc
Description: OpenPGP digital signature


Re: RFS: command-not-found

2007-07-01 Thread Christoph Haas
On Sun, Jul 01, 2007 at 10:08:47PM +0200, Julian Andres Klode wrote:
 Dear mentors,
 
 I am looking for a sponsor for my package command-not-found.
 
 * Package name: command-not-found
   Version : 0.2.4+debian-1
   Upstream Author : Zygmunt Krynicki [EMAIL PROTECTED]
 Michael Vogt [EMAIL PROTECTED]
 * URL : https://launchpad.net/command-not-found
 * License : GPL
   Section : admin

Not sure. Perhaps shell as a section might match better.

 It builds these binary packages:
 command-not-found - Suggest installation of packages in interactive bash 
 sessions
 command-not-found-data - Set of data files for command-not-found

I just built and installed it. There is some funny whitespace in between
the messages:

===
$ inetd
Command 'inetd' is available in '/usr/sbin/inetd'
The command could not be located because '/usr/sbin' is not i ncluded in the 
PATH environment variable.
This is most likely caused by the lack of administ rative priviledges 
associated with your user account.
bash: inetd: command not found
===

i ncluded - included
administ rative - administrative
priviledges - privileges

Did you talk to the Ubuntu maintainer already? Perhaps it make sense to
join forces so that only one package is built?

 Christoph
-- 
Peer review means that you can feel better because someone else
missed the problem, too.


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



Re: RFS: command-not-found

2007-07-01 Thread Julian Andres Klode
Christoph Haas wrote:
 On Sun, Jul 01, 2007 at 10:08:47PM +0200, Julian Andres Klode wrote:
 Dear mentors,

 I am looking for a sponsor for my package command-not-found.

 * Package name: command-not-found
   Version : 0.2.4+debian-1
   Upstream Author : Zygmunt Krynicki [EMAIL PROTECTED]
 Michael Vogt [EMAIL PROTECTED]
 * URL : https://launchpad.net/command-not-found
 * License : GPL
   Section : admin
 
 Not sure. Perhaps shell as a section might match better.
 
 It builds these binary packages:
 command-not-found - Suggest installation of packages in interactive bash 
 sessions
 command-not-found-data - Set of data files for command-not-found
 
 I just built and installed it. There is some funny whitespace in between
 the messages:
 
 ===
 $ inetd
 Command 'inetd' is available in '/usr/sbin/inetd'
 The command could not be located because '/usr/sbin' is not i ncluded in the 
 PATH environment variable.
 This is most likely caused by the lack of administ rative priviledges 
 associated with your user account.
 bash: inetd: command not found
 ===
 
 i ncluded - included
 administ rative - administrative
 priviledges - privileges
Fixed.

 
 Did you talk to the Ubuntu maintainer already? Perhaps it make sense to
 join forces so that only one package is built?
He's CCed, so: mvo: What's your opinion?

-- 
Julian Andres Klode

IRC Nickname:   juliank (Debian/OFTC + Freenode)
Fellow of FSFE: https://www.fsfe.org/en/fellows/jak (No. 1049)
Debian Wiki:http://wiki.debian.org/JulianAndresKlode
Ubuntu Wiki:http://wiki.ubuntu.com/JulianAndresKlode
In Launchpad:   https://launchpad.net/~juliank
Packages Overv: http://qa.debian.org/[EMAIL PROTECTED]
Languages:  German, English, [bit French]



signature.asc
Description: OpenPGP digital signature


Re: RFS: command-not-found

2007-07-01 Thread Justin Pryzby
On Sun, Jul 01, 2007 at 10:08:47PM +0200, Julian Andres Klode wrote:
 Dear mentors,
 
 I am looking for a sponsor for my package command-not-found.
 
 * Package name: command-not-found
   Version : 0.2.4+debian-1
   Upstream Author : Zygmunt Krynicki [EMAIL PROTECTED]
 Michael Vogt [EMAIL PROTECTED]
 * URL : https://launchpad.net/command-not-found
 * License : GPL
   Section : admin
 
 It builds these binary packages:
 command-not-found - Suggest installation of packages in interactive bash 
 sessions
How does it compare with auto-apt?  This a shell-only implementation
whereas auto-apt will find things which are accessed otherwise
(perhaps not bad).


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