Bug#687438: marked as done (RFS: krazy2/0~git20120912-1)

2013-01-31 Thread Debian Bug Tracking System
Your message dated Thu, 31 Jan 2013 16:20:38 +
with message-id e1u0wsq-0007xs...@quantz.debian.org
and subject line closing RFS: krazy2/0~git20120912-1
has caused the Debian Bug report #687438,
regarding RFS: krazy2/0~git20120912-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
687438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package krazy2

 * Package name: krazy2
   Version : 0~git20120912-1
   Upstream Author : Alen Winter win...@kde.org
 * URL : http://www.englishbreakfastnetwork.org/
 * License : GPLv2 or later
   Section : devel

  It builds those binary packages:

krazy2 - KDE/Qt code source checker

  To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/krazy2


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/k/krazy2/krazy2_0~git20120912-1.dsc


  Changes since the last upload:

krazy2 (0~git20120912-1) unstable; urgency=low

  * New upstream release.
  * Upload to unstable.
  * Bump debhelper compatibility to 9.
  * Activate hardening flags using hardening-wrapper.
  * Bump Standards-Version to 3.9.3, no changes needed.
  * Set Vcs-* fields.
  * Update copyright file.
  * Drop this lintian override (no longer used):
- krazy2: extra-license-file usr/lib/krazy2/krazy-plugins/general/license

 -- José Manuel Santamaría Lema panfa...@gmail.com  Wed, 12 Sep 2012 
19:01:06 +0200

P.S. I'm not a newbie, I have been working on KDE packages since 4.5 (that's 
more than one and a half year, maybe even 2 years). I would appreciate if the 
sponsor allows me to set the DMUA flag.


  Regards,
   José Manuel Santamaría Lema


signature.asc
Description: This is a digitally signed message part.
---End Message---
---BeginMessage---
Package krazy2 has been removed from mentors.---End Message---


Bug#667904: RFS: mitlm/0.4-1 [ITP] -- MIT Language Modeling

2013-01-31 Thread Jakub Wilk

* Giulio Paci giuliop...@gmail.com, 2013-01-30, 03:27:
To improve the manpages I improved the command line help messages 
(1008_improve_command_line_help.patch)


Doesn't this patch break ABI?

Speaking of which, I had a look at the list of exported symbols, and 
it's kinda messy... Some symbols have very generic names. Upstream 
should consider putting them into a namespace.



1007_escape_filename.patch
The latter fixes .bz2 handling and should work on Windows as well 
(although I have not tested it yet on a real Windows system).


I would be surprised if decompression worked correctly, though I don't 
have access to a Windows system to test it.


^ is a cmd.exe escape character, but then the executed program does 
argument parsing on its own. It's usually done by the MSVC++ runtime: 
http://msdn.microsoft.com/en-us/library/ms880421.aspx


--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130131191055.ga1...@jwilk.net



Bug#699474: RFS: b43-fwcutter/1:017-1 [ITA]

2013-01-31 Thread Daniel Echeverry
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package b43-fwcutter

 * Package name: b43-fwcutter
 * Version : 1:017-1
 * Upstream Author : Martin Langer martin-lan...@gmx.de
 * URL : http://wireless.kernel.org/en/users/Drivers/b43
 * License : BSD-2-Clause
 * Section : utils

It builds those binary packages:

b43-fwcutter - Utility for extracting Broadcom 43xx firmware
firmware-b43-installer - Installer package for firmware for the b43 driver
firmware-b43legacy-installer - Installer package for firmware for the
b43legacy driver

To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/b43-fwcutter

Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/contrib/b/b43-fwcutter/b43-fwcutter_017-1.dsc

Changes since the last upload:

  * New upstream release.
  * New Maintainer. Closes: #698759
  * debian/control
+ Set myself as Maintainer.
+ Remove firmware-b43-lpphy-installer package. Closes: #657837
  + Firmware-b43-installer now supports BCM4312.
+ Update firmware-b43-installer description.
+ Change debhelper to 9 in B-D.
+ Bump Standard Versions 3.9.4.
+ Switch compat level 8 to 9.
+ Remove dm-upload field.
+ Remove conflict field.
+ Add po-debconf and debconf in B-D.
  * debian/rules
+ Add security Flags.
+ Use tiny rules.
  * Remove firmware-b43-lpphy-installer.* files.
  * Firmware-b43-installer now support BCM4331. Closes: #682427
  * Add debconf support. Thanks to Gaudenz. Closes: #698348
+ Allow installation without corresponding hardware.
+ Add es.po translation.
  * Update copyright file.
  * Remove debian/series file.
  * Update watch file.
  * Remove README.firmware-b43-lpphy-installer file.

Regards,
Daniel Echeverry

-- 
Epsilon
http://wiki.debian.org/DanielEcheverry
http://www.rinconinformatico.net
http://enchulatucelu.com
http://www.todopdf.net
http://www.fitnessdeportes.com
http://www.dragonjar.org
Linux user: #477840
Debian user


Bug#699474: RFS: b43-fwcutter/1:017-1 [ITA]

2013-01-31 Thread Anton Gladky
Hi Daniel,

it looks the package is ok for uploading. But is it ok for you,
if it will be uploaded into experimental, as we are in freeze now?

Thanks,

Anton


2013/1/31 Daniel Echeverry epsilo...@gmail.com:
 Package: sponsorship-requests
 Severity: normal

 Dear mentors,

 I am looking for a sponsor for my package b43-fwcutter

  * Package name: b43-fwcutter
  * Version : 1:017-1
  * Upstream Author : Martin Langer martin-lan...@gmx.de
  * URL : http://wireless.kernel.org/en/users/Drivers/b43
  * License : BSD-2-Clause
  * Section : utils

 It builds those binary packages:

 b43-fwcutter - Utility for extracting Broadcom 43xx firmware
 firmware-b43-installer - Installer package for firmware for the b43 driver
 firmware-b43legacy-installer - Installer package for firmware for the
 b43legacy driver

 To access further information about this package, please visit the following
 URL:

 http://mentors.debian.net/package/b43-fwcutter

 Alternatively, one can download the package with dget using this command:

 dget -x
 http://mentors.debian.net/debian/pool/contrib/b/b43-fwcutter/b43-fwcutter_017-1.dsc

 Changes since the last upload:

   * New upstream release.
   * New Maintainer. Closes: #698759
   * debian/control
 + Set myself as Maintainer.
 + Remove firmware-b43-lpphy-installer package. Closes: #657837
   + Firmware-b43-installer now supports BCM4312.
 + Update firmware-b43-installer description.
 + Change debhelper to 9 in B-D.
 + Bump Standard Versions 3.9.4.
 + Switch compat level 8 to 9.
 + Remove dm-upload field.
 + Remove conflict field.
 + Add po-debconf and debconf in B-D.
   * debian/rules
 + Add security Flags.
 + Use tiny rules.
   * Remove firmware-b43-lpphy-installer.* files.
   * Firmware-b43-installer now support BCM4331. Closes: #682427
   * Add debconf support. Thanks to Gaudenz. Closes: #698348
 + Allow installation without corresponding hardware.
 + Add es.po translation.
   * Update copyright file.
   * Remove debian/series file.
   * Update watch file.
   * Remove README.firmware-b43-lpphy-installer file.

 Regards,
 Daniel Echeverry

 --
 Epsilon
 http://wiki.debian.org/DanielEcheverry
 http://www.rinconinformatico.net
 http://enchulatucelu.com
 http://www.todopdf.net
 http://www.fitnessdeportes.com
 http://www.dragonjar.org
 Linux user: #477840
 Debian user


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CALF6qJmpB9m=-hf40JV6k=jmgbksnqaez5qsffqq20beqts...@mail.gmail.com



Bug#699474: RFS: b43-fwcutter/1:017-1 [ITA]

2013-01-31 Thread Daniel Echeverry
Hi Anton,

Right now Adrian is reviewing it, thanks for your offer.

Thank you very much!


2013/1/31 Anton Gladky gladky.an...@gmail.com

 Hi Daniel,

 it looks the package is ok for uploading. But is it ok for you,
 if it will be uploaded into experimental, as we are in freeze now?

 Thanks,

 Anton


 2013/1/31 Daniel Echeverry epsilo...@gmail.com:
  Package: sponsorship-requests
  Severity: normal
 
  Dear mentors,
 
  I am looking for a sponsor for my package b43-fwcutter
 
   * Package name: b43-fwcutter
   * Version : 1:017-1
   * Upstream Author : Martin Langer martin-lan...@gmx.de
   * URL : http://wireless.kernel.org/en/users/Drivers/b43
   * License : BSD-2-Clause
   * Section : utils
 
  It builds those binary packages:
 
  b43-fwcutter - Utility for extracting Broadcom 43xx firmware
  firmware-b43-installer - Installer package for firmware for the b43
 driver
  firmware-b43legacy-installer - Installer package for firmware for the
  b43legacy driver
 
  To access further information about this package, please visit the
 following
  URL:
 
  http://mentors.debian.net/package/b43-fwcutter
 
  Alternatively, one can download the package with dget using this command:
 
  dget -x
 
 http://mentors.debian.net/debian/pool/contrib/b/b43-fwcutter/b43-fwcutter_017-1.dsc
 
  Changes since the last upload:
 
* New upstream release.
* New Maintainer. Closes: #698759
* debian/control
  + Set myself as Maintainer.
  + Remove firmware-b43-lpphy-installer package. Closes: #657837
+ Firmware-b43-installer now supports BCM4312.
  + Update firmware-b43-installer description.
  + Change debhelper to 9 in B-D.
  + Bump Standard Versions 3.9.4.
  + Switch compat level 8 to 9.
  + Remove dm-upload field.
  + Remove conflict field.
  + Add po-debconf and debconf in B-D.
* debian/rules
  + Add security Flags.
  + Use tiny rules.
* Remove firmware-b43-lpphy-installer.* files.
* Firmware-b43-installer now support BCM4331. Closes: #682427
* Add debconf support. Thanks to Gaudenz. Closes: #698348
  + Allow installation without corresponding hardware.
  + Add es.po translation.
* Update copyright file.
* Remove debian/series file.
* Update watch file.
* Remove README.firmware-b43-lpphy-installer file.
 
  Regards,
  Daniel Echeverry
 
  --
  Epsilon
  http://wiki.debian.org/DanielEcheverry
  http://www.rinconinformatico.net
  http://enchulatucelu.com
  http://www.todopdf.net
  http://www.fitnessdeportes.com
  http://www.dragonjar.org
  Linux user: #477840
  Debian user




-- 
Epsilon
http://wiki.debian.org/DanielEcheverry
http://www.rinconinformatico.net
http://enchulatucelu.com
http://www.todopdf.net
http://www.fitnessdeportes.com
http://www.dragonjar.org
Linux user: #477840
Debian user


Bug#699474: RFS: b43-fwcutter/1:017-1 [ITA]

2013-01-31 Thread John Paul Adrian Glaubitz

On 01/31/2013 10:16 PM, Daniel Echeverry wrote:

Right now Adrian is reviewing it, thanks for your offer.

Thank you very much!


2013/1/31 Anton Gladky gladky.an...@gmail.com
mailto:gladky.an...@gmail.com

Hi Daniel,

it looks the package is ok for uploading. But is it ok for you,
if it will be uploaded into experimental, as we are in freeze now?


No, unfortunately the package is not ok yet. When I install the package 
b43-fwcutter, it will prompt the debconf question in Spanish.


Also, after installing b43-fwcutter, nothing further happens. I have to 
install the firmware-b43-debs manually which is very confusing. Ideally, 
the package b43-fwcutter should detect the hardware and prompt for the 
installation of the proper package or at least depend on them.


And there is also no need for experimental. The package doesn't have any 
RC bugs in testing, so we don't need to resort to experimental due to 
the freeze.


Cheers,

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/510ae137.6000...@physik.fu-berlin.de



Bug#699474: RFS: b43-fwcutter/1:017-1 [ITA]

2013-01-31 Thread David Prévot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

Le 31/01/2013 17:25, John Paul Adrian Glaubitz a écrit :
 
 And there is also no need for experimental.

Yes there is. Better safe than sorry.

 The package doesn't have any
 RC bugs in testing,

yet…

 so we don't need to resort to experimental due to
 the freeze.

That sound like a misguided advice.

Please, do not upload to unstable packages not aimed for Wheezy during
the freeze* (IOW, thanks to the sponsoree for proposing this upload to
experimental).

Regards

David

P.-S.: *except if they are not already present in Wheezy, or maybe if
the version in Sid is already messed up, which is not the case here.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRCvaDAAoJELgqIXr9/gnykfcP/RdyIr74/+CFgal8kwUml/Ux
VCZVvfk8wde99M4+QbnSGfx/KrFAyogg6VQEf6AG2L+fbsJu9zO6KCYlgrDJCAIj
L/5MxkOA/9mf+2kK2OCIGDYwFhv8pNAQdoEsLI3H0xuJFxcvXotUf5POm2mByUKN
6cTY3Fs2iV7pByySNxXtRgRFGFQzAQQflJoeEjJN2drHzd3rjH7IM7smzdNOWfTF
YrBAS8ykYJ5GhjiLf+h6UIH5QS6+U1qoWVfX3uKUVY8pv7qz1t+t94lmPUKRNnAQ
wB/73DDceoA8bV3njhIofb3j47AOA88j05vLbkLIvbVVQiZP+Zp2KT+sT/G8QI8E
rDB2ngWgNaDnGmeITs48KNt4WUPCy1inYgzqHBm7o333ZTp6+QYPka/yXc+DqSX8
kTV/gn5M3NmrwFsc7/hFAcLfcoTHGR+/ke9qWL4DtnfJaR9/sQqvFX+wf3Z+hEQc
n2wSPvGZG7THxAo9QXP8UdWDdJKazsRrqH5RzdsMD6LyBtHzPtlbxflr4iH0UnVq
Kkcu5fL6pYfnP6TCjZENU3fDUY3cG43KR1N6bVsQwRQ4Q1TMcCWKSD8FS9nhsTNh
QurI3Lxd+2brMqttku/bzh1DagvoH9kCMPseivudXXdAucw67bt/hy3kenQOmJhE
j7vKUeAVf4IPdGzES0rU
=jdlE
-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: http://lists.debian.org/510af683.3020...@tilapin.org



Bug#699474: RFS: b43-fwcutter/1:017-1 [ITA]

2013-01-31 Thread Paul Tagliamonte
On Thu, Jan 31, 2013 at 06:56:03PM -0400, David Prévot wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256
 
 Hi,
 
 Le 31/01/2013 17:25, John Paul Adrian Glaubitz a écrit :
  
  And there is also no need for experimental.
 
 Yes there is. Better safe than sorry.
 
  The package doesn't have any
  RC bugs in testing,
 
 yet…
 
  so we don't need to resort to experimental due to
  the freeze.
 
 That sound like a misguided advice.
 
 Please, do not upload to unstable packages not aimed for Wheezy during
 the freeze* (IOW, thanks to the sponsoree for proposing this upload to
 experimental).

If it's worth anything, I do agree as well.

A few nice things about not breaking unstable:

  - Important bugfixes can be folded in with an RC bugfix upload (sweet)
  - Your package updates will get testing through unstable users, rather
then no testing via TPU (and perhaps resulting in another upload to
TPU)
  - Being able to sleep at night knowing the release team isn't plotting
to frame you for something nasty

 
 Regards
 
 David
 
 P.-S.: *except if they are not already present in Wheezy, or maybe if
 the version in Sid is already messed up, which is not the case here.
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 
 iQIcBAEBCAAGBQJRCvaDAAoJELgqIXr9/gnykfcP/RdyIr74/+CFgal8kwUml/Ux
 VCZVvfk8wde99M4+QbnSGfx/KrFAyogg6VQEf6AG2L+fbsJu9zO6KCYlgrDJCAIj
 L/5MxkOA/9mf+2kK2OCIGDYwFhv8pNAQdoEsLI3H0xuJFxcvXotUf5POm2mByUKN
 6cTY3Fs2iV7pByySNxXtRgRFGFQzAQQflJoeEjJN2drHzd3rjH7IM7smzdNOWfTF
 YrBAS8ykYJ5GhjiLf+h6UIH5QS6+U1qoWVfX3uKUVY8pv7qz1t+t94lmPUKRNnAQ
 wB/73DDceoA8bV3njhIofb3j47AOA88j05vLbkLIvbVVQiZP+Zp2KT+sT/G8QI8E
 rDB2ngWgNaDnGmeITs48KNt4WUPCy1inYgzqHBm7o333ZTp6+QYPka/yXc+DqSX8
 kTV/gn5M3NmrwFsc7/hFAcLfcoTHGR+/ke9qWL4DtnfJaR9/sQqvFX+wf3Z+hEQc
 n2wSPvGZG7THxAo9QXP8UdWDdJKazsRrqH5RzdsMD6LyBtHzPtlbxflr4iH0UnVq
 Kkcu5fL6pYfnP6TCjZENU3fDUY3cG43KR1N6bVsQwRQ4Q1TMcCWKSD8FS9nhsTNh
 QurI3Lxd+2brMqttku/bzh1DagvoH9kCMPseivudXXdAucw67bt/hy3kenQOmJhE
 j7vKUeAVf4IPdGzES0rU
 =jdlE
 -END PGP SIGNATURE-
 
 
 -- 
 To UNSUBSCRIBE, email to package-sponsorship-requests-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/510af683.3020...@tilapin.org
 

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte paul...@debian.org
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature


Bug#667904: RFS: mitlm/0.4-1 [ITP] -- MIT Language Modeling

2013-01-31 Thread Giulio Paci
Il 31/01/2013 20:10, Jakub Wilk ha scritto:
 * Giulio Paci giuliop...@gmail.com, 2013-01-30, 03:27:
 To improve the manpages I improved the command line help messages 
 (1008_improve_command_line_help.patch)
 
 Doesn't this patch break ABI?

You are right, however upstream never provided shared libraries, we are still 
API compatible with upstream and the patch has been included upstream.
Can we break ABI in this case? Should we wait the first shared library released 
from upstream instead?

 Speaking of which, I had a look at the list of exported symbols, and it's 
 kinda messy... Some symbols have very generic names. Upstream should consider 
 putting them into a
 namespace.

I think I can work on this and have it included upstream.

 1007_escape_filename.patch
 The latter fixes .bz2 handling and should work on Windows as well (although 
 I have not tested it yet on a real Windows system).
 
 I would be surprised if decompression worked correctly, though I don't have 
 access to a Windows system to test it.
 
 ^ is a cmd.exe escape character, but then the executed program does 
 argument parsing on its own. It's usually done by the MSVC++ runtime:
 http://msdn.microsoft.com/en-us/library/ms880421.aspx

You are right, in fact I first implemented the command line parsing escape. 
Then I realized that I also needed cmd.exe escape. Then I guessed that I only 
needed cmd.exe
escape as  and  are breaking the command line. Testing on wine did not 
work, however testing on a real Windows proved that I was right. Stackoverflow
(http://stackoverflow.com/questions/11193691/batch-escaping-with-caret) also 
pointed out that | symbol requires double cmd.exe-style escaping.
So: the general case is a nightmare, but the way I implemented it should 
correctly work (and when I tested, it worked properly).

Bests,
Giulio.


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/510af824.8070...@gmail.com