Bug#1004922: Asking for new upstream release

[Victor Westerhuis]

I have retracted the current version of kmscon I had uploaded at 
mentors.debian.net to ask the upstream maintainer for a new release 
(https://github.com/Aetf/kmscon/issues/42), so I can prepare a proper 
release for Debian.


A new version of libtsm has just been accepted into the archive, closing 
the blocking bug #1004921, so there should be no further blocks once I 
get a new version of kmscon ready.

--
Victor Westerhuis 


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003976: New upstream release and armhf bug

[Ben Westover]

There has been a new upstream release 6.16.3 that my package has been 
updated to. It includes a fix for the armhf compilation issue.


There is a new issue, however; though it compiles properly on armhf, the 
program gives a bus error shortly after attempting to use it, and it 
exits. The problem seems to be with unaligned memory access attempts 
which are not possible on armhf, and thus the program crashes.
The bug has been reported at https://github.com/xmrig/xmrig/issues/2895, 
and until a fix is found, armhf has been removed from the supported 
architectures in debian/control.


OpenPGP_0xC311C5F54E89B698.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#968618: RFS: golang-github-creack-pty/1.1.11-1 -- new upstream release

[Ben Fiedler]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the package
"golang-github-creack-pty-dev",
found on salsa [1].

This update is mandatory for packaging aerc 0.4.0.

Changelog:

golang-github-creack-pty (1.1.11-1) unstable; urgency=medium

  * Team upload
  * New upstream release 1.1.11

 -- Ben Fiedler   Tue, 18 Aug 2020 00:43:38 
+0200


Regards,
Ben Fiedler

[1]: 
https://salsa.debian.org/go-team/packages/golang-github-emersion-go-smtp/-/merge_requests/1

Re: Bug#928099: RFS: shc/4.0.1 new upstream release

[Tong Sun]

On Mon, Apr 29, 2019 at 9:16 AM Tong Sun
 wrote:
>
> The RFS fixes all the following action items in the bug tracker
> (https://tracker.debian.org/pkg/shc):
>
>  A new upstream version is available: 4.0.1 high
>  Failed to analyze the VCS repository. Please troubleshoot and fix the
> issue. high
>  RFS: A sponsor is needed to update this package. normal
>  lintian reports 1 warning normal
>  Standards version of the package is outdated. wishlist
>
> ubuntu version: 3.9.6-1
> 1 bug
>
> Thanks
>
> On Sat, Apr 27, 2019 at 6:51 PM Tong Sun wrote:
> >
> > Package: sponsorship-requests
> > Severity: normal
> >
> > Dear mentors,
> >
> > I am looking for a sponsor for my package "shc".
> >
> > I've pushed it to Salsa:
> >
> >   https://salsa.debian.org/debian/shc
> >
> > The package was tested on both gbp and sbuild. It's also lintian-clean.
> >
> > here is the build log:
> > https://paste.debian.net/1080285/
> >
> > Could you please reviewing/sponsoring this?
> >
> > Any kind of reviews and suggestions are appreciated.

Now,

My upload of the package 'shc' to mentors.debian.net was
successful. The URL is:
https://mentors.debian.net/package/shc

The respective dsc file can be found at:
https://mentors.debian.net/debian/pool/main/s/shc/shc_4.0.2-1.dsc

Thanks

Re: Bug#928099: RFS: shc/4.0.1 new upstream release

[Tong Sun]

Trying again after 2 days.

The RFS fixes all the following action items in the bug tracker
(https://tracker.debian.org/pkg/shc):

 A new upstream version is available: 4.0.1 high
 Failed to analyze the VCS repository. Please troubleshoot and fix the
issue. high
 RFS: A sponsor is needed to update this package. normal
 lintian reports 1 warning normal
 Standards version of the package is outdated. wishlist

ubuntu version: 3.9.6-1
1 bug

Thanks

On Sat, Apr 27, 2019 at 6:51 PM Tong Sun - suntong...@gmail.com
 wrote:
>
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "shc".
>
> I've pushed it to Salsa:
>
>   https://salsa.debian.org/debian/shc
>
> The package was tested on both gbp and sbuild. It's also lintian-clean.
>
> here is the build log:
> https://paste.debian.net/1080285/
>
> Could you please reviewing/sponsoring this?
>
> Any kind of reviews and suggestions are appreciated.
>
>

Bug#928099: RFS: shc/4.0.1 new upstream release

[Tong Sun]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "shc".

I've pushed it to Salsa:

  https://salsa.debian.org/debian/shc

The package was tested on both gbp and sbuild. It's also lintian-clean.

here is the build log:
https://paste.debian.net/1080285/

Could you please reviewing/sponsoring this?

Any kind of reviews and suggestions are appreciated.

[uploaded] Re: RFS: ranger/1.9.2-1 (new upstream release)

[Mo Zhou]

Hi Vern Sun,

Thank you very much for you contribution to Debian!
I have uploaded this package to ftp-master with some further modifications,
to completely drop every bit about python2 and switch to py3.
As confirmed previously, I added myself to Uploaders to co-maint this package.
Please check git repo for detail.

Your autopkgtest scripts are working well, expect that you missed a
runtime dependency "procpc". I've already fixed that.

And thanks to Herbert Fortes for the hints!

P.S. Generally sending RFS to mentors/BTS is enough and there is no need
to CC other Chinese developers individually ... unless you know each
other in the real world.

Best.


ranger (1.9.2-1) unstable; urgency=medium

  [ Mo Zhou ]
  * Set up a project repository on Debian Salsa:
https://salsa.debian.org/debian/ranger
  * Add myself to uploaders.
  * Bump debhelper compat level to 11.
  * Fix Vcs-* fields and update homepage URL.
  * Move from python2 to python3:
- Completely drop python2 from rules.
- Drop all python2 dependencies.
* Patch makefile to use python3 tools. (+ make-use-py3tools.patch)
* Patch upstream python files to refer python3 in shebang.
  * Export TERM=linux in rules instead of upstream Makefile.
  * Export HOME=/tmp/ in rules to avoid test failure due to /sbuild-nonexistent
  * Autopkgtest test case missed runtime dependency: procps.
  * Convert copyright into machine-readable format.

  [ Vern Sun ]
  * New upstream release. (Closes: #908982)
  * Move to Python 3. (Closes: #910401)
https://www.debian.org/doc/packaging-manuals/python-policy/ch-python3.html
  * Enable sensible-pager again, no offence.
  * New CI tests, by reference to the GNU Screen.


On Sat, Oct 13, 2018 at 05:02:47PM +0800, Vern Sun wrote:
> Dear mentors,
> 
> I am looking for a sponsor for "ranger":
> 
>  * Package name: ranger
>  * Version : 1.9.2-1
>  * Upstream Author : 
> https://raw.githubusercontent.com/hut/ranger/master/AUTHORS
>  * URL : https://ranger.github.io/
>  * License : GNU GPL version 3 or any later version
>  * Section : utils
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x 
> https://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.9.2-1.dsc
> 
> Changes since the last upload:
> 
>   [ Mo Zhou ]
>   * Set up a project repository on Debian Salsa:
> https://salsa.debian.org/debian/ranger
> 
>   [ Vern Sun ]
>   * New upstream release. (Closes: #908982)
>   * Move to Python 3. (Closes: #910401)
> https://www.debian.org/doc/packaging-manuals/python-policy/ch-python3.html
>   * Enable sensible-pager again, no offence.
>   * New CI tests, by reference to the GNU Screen.
> 
> Cheers,
> -- 
> Vern
> vim -c ":s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??"
> 
> 

RFS: ranger/1.9.2-1 (new upstream release)

[Vern Sun]

Dear mentors,

I am looking for a sponsor for "ranger":

 * Package name: ranger
 * Version : 1.9.2-1
 * Upstream Author : https://raw.githubusercontent.com/hut/ranger/master/AUTHORS
 * URL : https://ranger.github.io/
 * License : GNU GPL version 3 or any later version
 * Section : utils

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

  dget -x 
https://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.9.2-1.dsc

Changes since the last upload:

  [ Mo Zhou ]
  * Set up a project repository on Debian Salsa:
https://salsa.debian.org/debian/ranger

  [ Vern Sun ]
  * New upstream release. (Closes: #908982)
  * Move to Python 3. (Closes: #910401)
https://www.debian.org/doc/packaging-manuals/python-policy/ch-python3.html
  * Enable sensible-pager again, no offence.
  * New CI tests, by reference to the GNU Screen.

Cheers,
-- 
Vern
vim -c ":s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??"




signature.asc
Description: PGP signature

Bug#883840: Retitling the bug report as per new upstream release of spglib

[Andrius Merkys]

retitle 883840 RFS: spglib/1.10.3-1 [ITP] -- C library for crystal symmetry 
determination
thanks

I have updated the package as per new upstream patch release of "spglib".

Andrius

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania

Bug#883840: Retitling the bug report as per new upstream release of spglib

[Andrius Merkys]

retitle 883840 RFS: spglib/1.10.2-1 [ITP] -- C library for crystal
symmetry determination
thanks

I have updated the package as per new upstream patch release of "spglib".

Andrius

-- 
Andrius Merkys
PhD student at Vilnius University Institute of Biotechnology, Saulėtekio al. 7, 
room V325
LT-10257 Vilnius, Lithuania

Bug#873136: New upstream release

[Adam Bilbrough]

Hi,I have uploaded a new xz tarball to mentors.debian.org version 0.5-1
~Adam

Re: xf86-input-tslib: new upstream release (and location)

[Martin Kepplinger]

Am 2017-04-28 um 14:58 schrieb Martin Kepplinger:
> Hi all,
> 
> xf86-input-tslib is kind of dying in Debian, see
> https://tracker.debian.org/pkg/xf86-input-tslib
> 
> tslib itself that this driver uses, has quite some users still. Now
> there is a new release, version 0.0.7 of this Xorg driver at a new
> location:
> https://github.com/merge/xf86-input-tslib/releases
> 
> Since there still is the old packaging repository:
> https://anonscm.debian.org/cgit/collab-maint/xf86-input-tslib.git/
> 
> Does one of you maintainers want to pick that up and create an 0.0.7-1
> for unstable? The patches that were included by Debian are not needed
> anymore.
> 

nevermind, I rewrote the packaging and it's on mentors, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861455

thanks,

  martin

xf86-input-tslib: new upstream release (and location)

[Martin Kepplinger]

Hi all,

xf86-input-tslib is kind of dying in Debian, see
https://tracker.debian.org/pkg/xf86-input-tslib

tslib itself that this driver uses, has quite some users still. Now
there is a new release, version 0.0.7 of this Xorg driver at a new 
location:

https://github.com/merge/xf86-input-tslib/releases

Since there still is the old packaging repository:
https://anonscm.debian.org/cgit/collab-maint/xf86-input-tslib.git/

Does one of you maintainers want to pick that up and create an 0.0.7-1
for unstable? The patches that were included by Debian are not needed
anymore.

thanks
   martin

encrypted.asc
Description: Binary data

Bug#850706: marked as done (RFS: libdebug/0.5.2-1 (new upstream release, packaging updates))

[Debian Bug Tracking System]

Your message dated Mon, 9 Jan 2017 16:58:32 + (UTC)
with message-id <643201752.2424866.1483981112...@mail.yahoo.com>
and subject line Re: Bug#850706: RFS: libdebug/0.5.2-1 (new upstream release, 
packaging updates)
has caused the Debian Bug report #850706,
regarding RFS: libdebug/0.5.2-1 (new upstream release, packaging updates)
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.)


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

Dear mentors,

I am looking for a sponsor for the new upstream version of my
package "libdebug":

 * Package name: libdebug
   Version : 0.5.2-1
   Upstream Author : Peter Pentchev <r...@ringlet.net>
 * URL : https://devel.ringlet.net/devel/libdebug/
 * License : BSD-3-clause
   Section : devel

It builds two binary packages that have been tested with sbuild, Lintian,
and cme:

  libdebug0  - Memory leak detection system and logging library
  libdebug0-dev - Development files for the debug library

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

  https://mentors.debian.net/package/libdebug

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libd/libdebug/libdebug_0.5.2-1.dsc

More information about libdebug can be obtained from its
development site: https://devel.ringlet.net/devel/libdebug/

Changes since the last upload:

libdebug (0.5.2-1) unstable; urgency=medium

  * Acknowledge NMU; thanks, Jakub Wilk.
  * Use the HTTPS scheme for various Debian and upstream URLs.
  * Fix the upstream metadata file: Bug-Submit should be an URL.
  * Use single quotes around a constant string the rules file.
  * Bump the year on my debian/* copyright notice.
  * Build-depend on debhelper 10 now that it's even in jessie-backports;
remove the Lintian override.
  * Switch the watch file back to pgpsigurlmangle, since pgpmode=auto may
silently ignore a missing upstream signature.
  * Use the v4 substitution variables in the watch file.
  * Re-enable PIE in the build hardening flags.
  * New upstream release:
- re-enable parallel building after it was fixed upstream
- update the upstream copyright years and merge the upstream
  copyright clauses

 -- Peter Pentchev <r...@ringlet.net>  Mon, 09 Jan 2017 16:00:25 +0200

Thanks in advance for your assistance!

G'luck,
Peter

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---


Hello

>libdebug (0.5.2-1) unstable; urgency=medium


sponsored

G.


dcut ftp-master dm --uid "r...@ringlet.net" --allow libdebug
Uploading commands file to ftp.upload.debian.org (incoming: /pub/UploadQueue/)
Picking DM Peter Pentchev <r...@ringlet.net> with fingerprint 
2EE7A7A517FC124CF115C354651EEFB02527DF13

You need a passphrase to unlock the secret key for
user: "Gianfranco Costamagna <locutusofb...@debian.org>"
4096-bit RSA key, ID 4E9F5DD9, created 2014-09-14

Uploading locutus-1483981028.dak-commands to ftp-master

signature.asc
Description: PGP signature
--- End Message ---

Bug#850706: RFS: libdebug/0.5.2-1 (new upstream release, packaging updates)

[Peter Pentchev]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the new upstream version of my
package "libdebug":

 * Package name: libdebug
   Version : 0.5.2-1
   Upstream Author : Peter Pentchev <r...@ringlet.net>
 * URL : https://devel.ringlet.net/devel/libdebug/
 * License : BSD-3-clause
   Section : devel

It builds two binary packages that have been tested with sbuild, Lintian,
and cme:

  libdebug0  - Memory leak detection system and logging library
  libdebug0-dev - Development files for the debug library

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

  https://mentors.debian.net/package/libdebug

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libd/libdebug/libdebug_0.5.2-1.dsc

More information about libdebug can be obtained from its
development site: https://devel.ringlet.net/devel/libdebug/

Changes since the last upload:

libdebug (0.5.2-1) unstable; urgency=medium

  * Acknowledge NMU; thanks, Jakub Wilk.
  * Use the HTTPS scheme for various Debian and upstream URLs.
  * Fix the upstream metadata file: Bug-Submit should be an URL.
  * Use single quotes around a constant string the rules file.
  * Bump the year on my debian/* copyright notice.
  * Build-depend on debhelper 10 now that it's even in jessie-backports;
remove the Lintian override.
  * Switch the watch file back to pgpsigurlmangle, since pgpmode=auto may
silently ignore a missing upstream signature.
  * Use the v4 substitution variables in the watch file.
  * Re-enable PIE in the build hardening flags.
  * New upstream release:
- re-enable parallel building after it was fixed upstream
- update the upstream copyright years and merge the upstream
  copyright clauses

 -- Peter Pentchev <r...@ringlet.net>  Mon, 09 Jan 2017 16:00:25 +0200

Thanks in advance for your assistance!

G'luck,
Peter

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


signature.asc
Description: PGP signature

Bug#819166: marked as done (RFS: libsass-python/0.11.0-1 (new upstream release ; *urgent* : fix for FTBFS))

[Debian Bug Tracking System]

Your message dated Fri, 25 Mar 2016 20:37:23 +0100
with message-id <56f59373.8080...@debian.org>
and subject line sponsored.
has caused the Debian Bug report #819166,
regarding RFS: libsass-python/0.11.0-1 (new upstream release ; *urgent* : fix 
for FTBFS)
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.)


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

Dear mentors, Gianfranco,

I am looking for a sponsor for an upgrade of the package "libsass-python".
This an upgrade of the previous version 0.9.3-1 which is marked for autoremoval
on 29 March because of FTBFS on some platforms. I worked with upstream to
provide a patch to libsass (which libsass-python depends on) and it has been
propagated in the lastest libsass 3.3.4-1 that got released in sid 2days ago.
Here is libsass-python/0.11.0-1 changelog :

libsass-python (0.11.0-1) unstable; urgency=medium

  * debian/rules : taking default python version into account in shebang and
adapting upstream check of libsass version.
  * debian/control : updated python3-libsass dependency. Closes: #811406
  * Renaming sassc to pysassc while waiting for upstream. Closes: #817139
  * Updating to new release. Closes: #814428

 -- Frederic Bonnard <fre...@linux.vnet.ibm.com>  Thu, 24 Mar 2016 10:26:12 
+0100


Package infos :

 Package name: libsass-python
 Version : 0.11.0-1
 Upstream Author : Hong Minhee
 URL : http://hongminhee.org/libsass-python
 License : MIT
 Section : python

It builds those binary packages:

  pysassc- SASS for Python: command line utility for libsass
  python-libsass - SASS for Python: a straightforward binding of libsass for 
Python
  python3-libsass - SASS for Python 3: a straightforward binding of libsass for 
Python3

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

  http://mentors.debian.net/package/libsass-python


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

dget -x 
http://mentors.debian.net/debian/pool/main/libs/libsass-python/libsass-python_0.11.0-1.dsc

More information about libsass-python can be obtained from 
http://hongminhee.org/libsass-python.

Regards,
 Frederic Bonnard
--- End Message ---
--- Begin Message ---
sponsored, even if it didn't fail locally and on DebOMatic, but everywhere else 
on buildds.


cheers,

G.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#819166: RFS: libsass-python/0.11.0-1 (new upstream release ; *urgent* : fix for FTBFS)

[Frederic Bonnard]

Package: sponsorship-requests
Severity: normal

Dear mentors, Gianfranco,

I am looking for a sponsor for an upgrade of the package "libsass-python".
This an upgrade of the previous version 0.9.3-1 which is marked for autoremoval
on 29 March because of FTBFS on some platforms. I worked with upstream to
provide a patch to libsass (which libsass-python depends on) and it has been
propagated in the lastest libsass 3.3.4-1 that got released in sid 2days ago.
Here is libsass-python/0.11.0-1 changelog :

libsass-python (0.11.0-1) unstable; urgency=medium

  * debian/rules : taking default python version into account in shebang and
adapting upstream check of libsass version.
  * debian/control : updated python3-libsass dependency. Closes: #811406
  * Renaming sassc to pysassc while waiting for upstream. Closes: #817139
  * Updating to new release. Closes: #814428

 -- Frederic Bonnard   Thu, 24 Mar 2016 10:26:12 
+0100


Package infos :

 Package name: libsass-python
 Version : 0.11.0-1
 Upstream Author : Hong Minhee
 URL : http://hongminhee.org/libsass-python
 License : MIT
 Section : python

It builds those binary packages:

  pysassc- SASS for Python: command line utility for libsass
  python-libsass - SASS for Python: a straightforward binding of libsass for 
Python
  python3-libsass - SASS for Python 3: a straightforward binding of libsass for 
Python3

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

  http://mentors.debian.net/package/libsass-python


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

dget -x 
http://mentors.debian.net/debian/pool/main/libs/libsass-python/libsass-python_0.11.0-1.dsc

More information about libsass-python can be obtained from 
http://hongminhee.org/libsass-python.

Regards,
 Frederic Bonnard

Bug#808411: marked as done (RFS: primesieve/5.6.0+ds-1 [new upstream release])

[Debian Bug Tracking System]

Your message dated Mon, 21 Dec 2015 01:53:26 +0100
with message-id <56774d86.2090...@rezozer.net>
and subject line RFS: primesieve/5.6.0+ds-1 [new upstream release]
has caused the Debian Bug report #808411,
regarding RFS: primesieve/5.6.0+ds-1 [new upstream release]
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.)


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


Dear Mentors:

I am looking for a sponsor for the package primesieve [1] that
I am maintaining on behalf of the Debian Science-Team.
This version brings to Debian the lastest upstream version.

Thanks,
Jerome

[1] https://anonscm.debian.org/cgit/debian-science/packages/primesieve.git

-- System Information:
Debian Release: Jessie*
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.7-ckt11-amd64-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Thanks to the uploader,
Jerome
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWd02GAAoJEIC/w4IMSybj4UAH/RL72EXhzBSVKoETsDHvXRpD
Z90l5vsVyfHlvq4O/FZPinmcNJVEC2TfDBHpyG8RqfFY3wGULiLSpt4h7ei1RO9z
7TFrQfO6xKLm7tRdHMVTzo1QyFnNgfR43s75GCM6gP11/TZcs9E5LWELaZAMOAeq
uP0MK6pkAZov2aUSqjTklUh1gMvsSs/sEABl2yBCqbeLNiCbZgMDnQgHGGJFQDCI
4TcAhU8q8DNa1/HonBbH85MkTvEre3ON+sa+tchIETQb3j/SQXWL8NUQy70mJb5v
cDxx3iYQS0hlTo2wwOkhJh09ykropg5YwG9PtwYl2IRtX3KsTHN5lXlmjG115Ic=
=IJNA
-END PGP SIGNATURE End Message ---

Bug#808411: RFS: primesieve/5.6.0+ds-1 [new upstream release]

[Jerome Benoit]

Package: sponsorship-requests
Severity: normal


Dear Mentors:

I am looking for a sponsor for the package primesieve [1] that
I am maintaining on behalf of the Debian Science-Team.
This version brings to Debian the lastest upstream version.

Thanks,
Jerome

[1] https://anonscm.debian.org/cgit/debian-science/packages/primesieve.git

-- System Information:
Debian Release: Jessie*
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.7-ckt11-amd64-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#808411: RFS: primesieve/5.6.0+ds-1 [new upstream release]

[Mattia Rizzolo]

control: tag -1 moreinfo

On Sat, Dec 19, 2015 at 09:55:00PM +0100, Jerome Benoit wrote:
>   I am looking for a sponsor for the package primesieve [1] that
>   I am maintaining on behalf of the Debian Science-Team.
>   This version brings to Debian the lastest upstream version.

why is the -dev package versioned?
This version changes the soname (as you know), and with that there might
be a multi-package transition (didn't checked).
It becomes unnecessarly hard to do a transition when you need to do
sourceful uploads of all the reverse build-deps to change the build-dep.

Usually -dev packages aren't versioned, and they just depends on the
last lib package.

This is how you do a library transition in debian:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions

Now, this might not apply to primesieve, since it's a quite new package
and there might be no r-deps yet, but I think it's sensible to take the
occasion and rename that versioned -dev package to the unversioned
counterpart.
Also check if there are r-deps, and if there are, please follow that
wiki page linked above.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#807789: RFS: 4ti2/1.6.7+ds-1 [New Upstream Release]

[Jerome Benoit]

Package: sponsorship-requests
Severity: normal

Dear Mentors:

I am looking for a sponsor for the package 4ti2 [1] that
I am maintaining on behalf of the Debian Science-Team.
This version is a `New upstream release' that fixes a broken
test and some cosmetic issues.

Thanks,
Jerome

[1] https://anonscm.debian.org/cgit/debian-science/packages/4ti2.git


-- System Information:
Debian Release: Jessie*
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.7-ckt11-amd64-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#807789: RFS: 4ti2/1.6.7+ds-1 [New Upstream Release]

[Mattia Rizzolo]

control: owner -1 !
control: tag -1 + pending

Hi,

On Sun, Dec 13, 2015 at 02:48:24AM +0100, Jerome Benoit wrote:
>   I am looking for a sponsor for the package 4ti2 [1] that
>   I am maintaining on behalf of the Debian Science-Team.
>   This version is a `New upstream release' that fixes a broken
>   test and some cosmetic issues.

I'm currently building it, and if it will I'll upload it as-is, but I
have a couple of question for you nontheless:

* why don't you try to use the git repository in a sane way?  just
  importing .dsc you build somehow else is not really a good use of it,
  you lost a lot of benefith of git and makes unnecessarily hard for
  sponsors to review the changes (=> I couldn't use it at all...)
* I guess
- debian/{patches,adhoc}/*:
  - test walk 344, revive;
  - refresh.
  means something to you, but pretty sure it does mean nothing to me,
  especially the "test walk 344, revive" line.  At least for the patches
  next time can you try to be more verbose on what you did?  what you
  added, what you dropped and why.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#807789: marked as done (RFS: 4ti2/1.6.7+ds-1 [New Upstream Release])

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2015 02:31:04 +
with message-id <20151213023104.gg3...@chase.mapreri.org>
and subject line Re: Bug#807789: RFS: 4ti2/1.6.7+ds-1 [New Upstream Release]
has caused the Debian Bug report #807789,
regarding RFS: 4ti2/1.6.7+ds-1 [New Upstream Release]
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.)


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

Dear Mentors:

I am looking for a sponsor for the package 4ti2 [1] that
I am maintaining on behalf of the Debian Science-Team.
This version is a `New upstream release' that fixes a broken
test and some cosmetic issues.

Thanks,
Jerome

[1] https://anonscm.debian.org/cgit/debian-science/packages/4ti2.git


-- System Information:
Debian Release: Jessie*
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.7-ckt11-amd64-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
On Sun, Dec 13, 2015 at 02:19:41AM +, Mattia Rizzolo wrote:
> I'm currently building it, and if it will I'll upload it as-is, but I
> have a couple of question for you nontheless:

Well, it built, so I uploaded it, though I'm still curious about the
questions below :)

> 
> * why don't you try to use the git repository in a sane way?  just
>   importing .dsc you build somehow else is not really a good use of it,
>   you lost a lot of benefith of git and makes unnecessarily hard for
>   sponsors to review the changes (=> I couldn't use it at all...)
> * I guess
> - debian/{patches,adhoc}/*:
>   - test walk 344, revive;
>   - refresh.
>   means something to you, but pretty sure it does mean nothing to me,
>   especially the "test walk 344, revive" line.  At least for the patches
>   next time can you try to be more verbose on what you did?  what you
>   added, what you dropped and why.
> 
> -- 
> regards,
> Mattia Rizzolo
> 
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  http://mapreri.org  : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-



-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---

Bug#807789: RFS: 4ti2/1.6.7+ds-1 [New Upstream Release]

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello Mattia:

On 13/12/15 03:19, Mattia Rizzolo wrote:
> control: owner -1 !
> control: tag -1 + pending
> 
> Hi,
> 
> On Sun, Dec 13, 2015 at 02:48:24AM +0100, Jerome Benoit wrote:
>>  I am looking for a sponsor for the package 4ti2 [1] that
>>  I am maintaining on behalf of the Debian Science-Team.
>>  This version is a `New upstream release' that fixes a broken
>>  test and some cosmetic issues.
> 
> I'm currently building it, and if it will I'll upload it as-is, but I
> have a couple of question for you nontheless:
> 
> * why don't you try to use the git repository in a sane way?  just
>   importing .dsc you build somehow else is not really a good use of it,

It is why I do NOT import dsc material, but I use the same kind of message.
And I group the git-commit to avoid numerous ones.


>   you lost a lot of benefith of git and makes unnecessarily hard for
>   sponsors to review the changes (=> I couldn't use it at all...)
> * I guess
> - debian/{patches,adhoc}/*:
>   - test walk 344, revive;

In the previous package version, the test named walk failed over a sample input 
data file
with generic name 344: it was frozen and I sent a report to the upstream 
maintainer team,
along other minor reports.
This version of 4ti2 mainly fixed the reported issues, see the (upstream) NEWS 
file for
more details. So I unfrozen this test and I performed some minor changes in the 
debian
material to reflect the fixes brought by the upstream team. Those changes are 
minor
in the sense that they mainly concern maintenance, but not end users.


>   - refresh.
>   means something to you, but pretty sure it does mean nothing to me,
>   especially the "test walk 344, revive" line.  At least for the patches
>   next time can you try to be more verbose on what you did?  what you
>   added, what you dropped and why.
> 

I try to be concise. I guess that what you mean is that I should git-commit 
more often.


Thanks,
Jerome
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWbNykAAoJEIC/w4IMSybj1zwH/1npmQv7jLv/HI8j9ISWDRIP
RZhBiKbpn3EGvD6wZX9Wy04p1o44AXuTM4XcsEbl/ex5C3GWKqWHhmDHc73FTgNX
MxII9xUQ4cdtCuezYCfGM0tsNBvUVpOaHIE4FjZcnz3oJSVyBi5U7quuf+YwXqkF
M55J6r7X1OeyXU9QyLH0zuJyhoxPpLXspdXRQKZIKsTgUkInu4s4h4GJABGQqyiJ
z/1EAkOP4Eop1E+j5xWWS1xUsReih9GFWMs3BWDf6iHZk0UNUz1dkxnhI09R8rb7
KWComjv3wnxSfTkX/hQqQ7PCb9LsvIlYYs2cw4WHb6khJ7wR2qmvcbJ6Nzlb0WI=
=yoZf
-END PGP SIGNATURE-

Bug#807789: RFS: 4ti2/1.6.7+ds-1 [New Upstream Release]

[Mattia Rizzolo]

On Sun, Dec 13, 2015 at 03:49:08AM +0100, Jerome BENOIT wrote:
> On 13/12/15 03:19, Mattia Rizzolo wrote:
> > * why don't you try to use the git repository in a sane way?  just
> >   importing .dsc you build somehow else is not really a good use of it,
> 
> It is why I do NOT import dsc material, but I use the same kind of message.
> And I group the git-commit to avoid numerous ones.

well, 1 huge incomprehensible commit for sure doesn't help either.
afetr all that's the debian packaging VCS, if you don't do little
commits what's the whole point of it?
I can create a nearly identical repository with
gbp import-dscs --debsnap 4ti2
which downloads all the historical releases and push them into a git
repository => nice for historical reasons, but nearly useless...

> > * I guess
> > - debian/{patches,adhoc}/*:
> >   - test walk 344, revive;
> 
> In the previous package version, the test named walk failed over a sample 
> input data file
> with generic name 344: it was frozen and I sent a report to the upstream 
> maintainer team,
> along other minor reports.


> This version of 4ti2 mainly fixed the reported issues, see the (upstream) 
> NEWS file for
> more details. So I unfrozen this test and I performed some minor changes in 
> the debian
> material to reflect the fixes brought by the upstream team. Those changes are 
> minor
> in the sense that they mainly concern maintenance, but not end users.
> 

I like something like:
- debian/patches:
  - name-of-that-patch: remove to re-enable the test walk with 344.
  - patch1, patch2, patch3: drop, applied upstream
  - patch4: add to do blablabla
  - refresh.

> I try to be concise. I guess that what you mean is that I should git-commit 
> more often.

It's important to be concise (something that honestly I fail to do
pretty often), but it also important to always have enough information,
and this is even more important given that the changes done are
impossible to obtain otherwise (you don't have a useful VCS) if you
don't want to read the huge debdiff.

It's not uncommon that in a far future somebody will be interested in
changes done now.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Re: RFS: ranger/1.7.2-1 (new upstream release)

[Paul Wise]

On Sun, Nov 1, 2015 at 9:01 PM, Vern Sun wrote:

> I am looking for a sponsor for "ranger":

I don't intend to sponsor this but here is a review:

Why is this patch marked as not needing forwarding? It fixes a bug in
the upstream code and so it should be fixed upstream.

0004-closes-772351-thanks-Raphael-Geissert.patch

According to debian/changelog this patch has been merged upstream, you
can remove it from debian/patches and remove the commented line about
it in debian/patches/series.

0003-honour-TMPDIR-environment-variable.patch

I expect this patch should not have been sent upstream as
sensible-utils is probably not installed very often outside of Debian
systems.

0002-make-sensible-decisions-on-which-pager-and-editor.patch

I would suggest running `wrap-and-sort -sa` to wrap and sort the
debian/control file and other files.

The Priority should probably be optional instead of extra.

HACKING.md doesn't need to be installed in the binary package (see
debian/docs) as it is a file for people who want to modify the source
code.

You might want to include some upstream metadata:

https://wiki.debian.org/UpstreamMetadata

doc/*.1 are generated files that should be built from source only.
Please ask upstream to generate them at build time and get them
removed from the upstream VCS and tarballs. If they refuse you should
remove them in both `debian/rules clean` and  `debian/rules build` and
generate them during `debian/rules build`.

Upstream has two CHANGELOG files that are identical apart from the
formatting and the 2015-10-04: version 1.7.2 entry, they probably
should delete CHANGELOG.md or decide which one they are going to use.

Generally the AUTHORS file only contains authors and license
information is placed in COPYING, you might want to suggest that to
upstream.

ranger/__init__.py and ranger/core/main.py probably have arbitrary
file overwrite vulnerabilities. Upstream should use either the user's
home directory or tempfile.TemporaryFile or
tempfile.NamedTemporaryFile instead of tempfile.gettempdir().

examples/plugin_ipc.py is creating FIFOs in /tmp, I would suggest that
should be fixed to use $XDG_RUNTIME_DIR or somewhere under the user's
home directory.

Upstream might like to rewrite the UI parts using urwid, which is a
high-level python console widget library. I imagine it would be more
pleasant to use than raw ncurses.

http://urwid.org/

./ranger/data/scope.sh uses env to find sh but it is always at /bin/sh
so upstream doesn't need to use env.

The upstream signing key uses a SHA-1 self-signature, you might want
to educate them about OpenPGP best practices, push out a key with a
SHA-2 self-signature and update the signing key in the
debian/upstream/signing-key.asc using export-minimal:

https://help.riseup.net/en/security/message-security/openpgp/best-practices
https://wiki.debian.org/debian/watch#Cryptographic_signature_verification

Also, lintian indicates that debian/watch is missing the things needed
to verify the upstream tarball using debian/upstream/signing-key.asc .

When you are contacting upstream, please mention the upstream guide:

https://wiki.debian.org/UpstreamGuide

Automatic checks:

lintian

P: ranger source: no-dep5-copyright
P: ranger source: debian-watch-may-check-gpg-signature

build

dpkg-gencontrol: warning: package ranger: unused substitution variable
${python:Versions}

check-all-the-things

$ cme check dpkg
...
Warning in 'control source Build-Depends:1' value 'dh-python (>= 1)':
unnecessary versioned dependency: dh-python >= 1. Debian has
wheezy-backports -> 1.20140511-1~bpo70+1; jessie-kfreebsd ->
1.2014-2; jessie -> 1.2014-2; stretch -> 2.20150826; sid ->
2.20150826;
Warning in 'control source Build-Depends:3' value 'ncurses-bin (>=
5.7+20100313-5)': unnecessary versioned dependency: ncurses-bin >=
5.7+20100313-5. Debian has squeeze -> 5.7+20100313-5; wheezy ->
5.9-10; jessie-kfreebsd -> 5.9+20140913-1+b1; jessie ->
5.9+20140913-1+b1; stretch -> 6.0+20150810-1; sid -> 6.0+20151024-1;
File debian/copyright line 1 has a syntax error:
DpkgSyntax error: Invalid line (missing ':' ?) : This is Debian's
prepackaged version of Ranger, A file manager with an ncurses

$ codespell --quiet-level=3
./CHANGELOG:117: noticable  ==> noticeable
./CHANGELOG:125: certian  ==> certain
./CHANGELOG.md:103: noticable  ==> noticeable
./CHANGELOG.md:111: certian  ==> certain
./ranger/gui/displayable.py:35: reccomended  ==> recommended
./ranger/gui/curses_shortcuts.py:18: faciliate  ==> facilitate
./ranger/config/rc.conf:139: Noticable  ==> Noticeable
./ranger/core/main.py:234: faciliate  ==> facilitate
./ranger/ext/keybinding_parser.py:74: cant  ==> can't
./examples/rc_emacs.conf:140: Noticable  ==> Noticeable
./doc/colorschemes.txt:91: maintainance  ==> maintenance
./doc/config/rc.conf:139: Noticable  ==> Noticeable

$ find -type f -iname '*.asc' -exec cat {} + | hot dearmor | hokey lint
...
Self-sig hash algorithms: [SHA1]

$ pep8 --ignore W191 .


$ pyflakes .


$ find 

RFS: ranger/1.7.2-1 (new upstream release)

[Vern Sun]

Dear mentors,

I am looking for a sponsor for "ranger":

 * Package name: ranger
 * Version : 1.7.2-1
 * Upstream Author : https://raw.githubusercontent.com/hut/ranger/master/AUTHORS
 * URL : http://ranger.nongnu.org/
 * License : GNU GPL version 3 or any later version
 * Section : utils

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

dget -x 
http://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.7.2-1.dsc

Changes since the last upload:

   * New upstream release.
   * Quilt patch(0003) has been merged to upstream, fixed.  

Cheers,
-- 
Vern
vim -c ":s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??"




signature.asc
Description: Digital signature

Bug#799529: RFS: shc/3.8.9b-1 new upstream release

[Gianfranco Costamagna]

>> -shc (3.8.7-2) unstable; urgency=medium

>> +shc (3.8.7-2) unstable; urgency=low
>
>> well your previous uploader uploaded with medium instead of low, please 
>> adapt the changelog accordingly
>
>
>Please, read this[1].
>
>
>[1] >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730343
>
>So, is right to use medium in revisions and for NEW too.



this 3.8.7-2 is *already on Debian*.
I'm not talking about the current version (yes, I'm aware of that bug lol).

In your previous upload you set the urgency low, but your sponsor or whatever 
else changed it to medium
when he did the upload

https://github.com/suntong/shc-build/blob/master/debian/changelog

vs

https://packages.qa.debian.org/s/shc/news/20140907T040337Z.html

So I'm not saying you need to upload this version in low priority, but change 
the previous one in medium,
because changing the changelog after an upload is considered a really *bad* 
pratice.

I hope I clarified my request now :)

and I hope you agree now :D

cheers!

G.

Bug#799529: RFS: shc/3.8.9b-1 new upstream release

[Tong Sun]

Hi Gianfranco,

Thanks for the review.

All have been fixed as instructed.  Ref
https://github.com/suntong/shc-build/commits/master

And new build is uploaded to

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

The respective dsc file can be found at:
http://mentors.debian.net/debian/pool/main/s/shc/shc_3.8.9b-1.dsc

Thanks


On Fri, Sep 25, 2015 at 7:44 AM, Gianfranco Costamagna
 wrote:
> Control: owner -1 !
>
>
> Hi, lets review:
>
> changelog: please be more verbose: e.g bump std-version,
> -add patches
> -remove patches
> -refresh patches
> -drop README.source
>
>
>
> changelog:
> -shc (3.8.7-2) unstable; urgency=medium
>
> +shc (3.8.7-2) unstable; urgency=low
>
>
> well your previous uploader uploaded with medium instead of low, please adapt 
> the changelog accordingly
>
> copyright:
> please update copyright years
>
> patches:
> they might be upstreamed, but maybe please use something like
> "?=" instead of "=" that way they will be assigned only if not already 
> assigned
>
> http://stackoverflow.com/questions/448910/makefile-variable-assignment
>
> the other patches should be upstreamed IMHO.
>
> cheers,
>
> G.

Bug#799529: marked as done (RFS: shc/3.8.9b-1 new upstream release)

[Debian Bug Tracking System]

Your message dated Sat, 26 Sep 2015 16:34:56 + (UTC)
with message-id <1792336195.1785517.1443285296145.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#799529: RFS: shc/3.8.9b-1 new upstream release
has caused the Debian Bug report #799529,
regarding RFS: shc/3.8.9b-1 new upstream release
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.)


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

Dear mentors,

I am looking for a sponsor for my package "shc"

 * Package name: shc
   Version : 3.8.9b-1
   Upstream Author : Francisco Rosales <fro...@fi.upm.es>.
 * URL : http://www.datsi.fi.upm.es/~frosal/
 * License : GPL-2.0
   Section : devel


It builds those binary packages:

shc   - Generic shell script compiler

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

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

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

dget -x http://mentors.debian.net/debian/pool/main/s/shc/shc_3.8.9b-1.dsc

Changes since the last upload:

   * New upstream release
   * Updated Standard-version to 3.9.6.
   * redo the makefile patching from scratch

More information about changes can be obtained from
https://github.com/suntong/shc-build/commits/master


Regards,

Tong Sun
--- End Message ---
--- Begin Message ---
Hi, Built, thanks for your nice contribution to Debian!

(next time maybe mention all the changes, like the copyright change, but well, 
the package
was good!)

cheers,

G.




Il Sabato 26 Settembre 2015 16:33, Tong Sun <suntong...@users.sourceforge.net> 
ha scritto:
Hi Gianfranco,

Thanks for the review.

All have been fixed as instructed.  Ref
https://github.com/suntong/shc-build/commits/master

And new build is uploaded to

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

The respective dsc file can be found at:
http://mentors.debian.net/debian/pool/main/s/shc/shc_3.8.9b-1.dsc

Thanks



On Fri, Sep 25, 2015 at 7:44 AM, Gianfranco Costamagna
<costamagnagianfra...@yahoo.it> wrote:
> Control: owner -1 !
>
>
> Hi, lets review:
>
> changelog: please be more verbose: e.g bump std-version,
> -add patches
> -remove patches
> -refresh patches
> -drop README.source
>
>
>
> changelog:
> -shc (3.8.7-2) unstable; urgency=medium
>
> +shc (3.8.7-2) unstable; urgency=low
>
>
> well your previous uploader uploaded with medium instead of low, please adapt 
> the changelog accordingly
>
> copyright:
> please update copyright years
>
> patches:
> they might be upstreamed, but maybe please use something like
> "?=" instead of "=" that way they will be assigned only if not already 
> assigned
>
> http://stackoverflow.com/questions/448910/makefile-variable-assignment
>
> the other patches should be upstreamed IMHO.
>
> cheers,
>
> G.--- End Message ---

Bug#799529: RFS: shc/3.8.9b-1 new upstream release

[Eriberto]

Hi Gianfranco,

2015-09-25 8:44 GMT-03:00 Gianfranco Costamagna :
> Control: owner -1 !
>
>
> Hi, lets review:
>
> changelog: please be more verbose: e.g bump std-version,
> -add patches
> -remove patches
> -refresh patches
> -drop README.source
>
>
>
> changelog:
> -shc (3.8.7-2) unstable; urgency=medium
>
> +shc (3.8.7-2) unstable; urgency=low
>
>
> well your previous uploader uploaded with medium instead of low, please adapt 
> the changelog accordingly


Please, read this[1].

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730343

So, is right to use medium in revisions and for NEW too.

Cheers,

Eriberto

Bug#799529: RFS: shc/3.8.9b-1 new upstream release

[Gianfranco Costamagna]

Control: owner -1 !


Hi, lets review:

changelog: please be more verbose: e.g bump std-version,
-add patches
-remove patches
-refresh patches
-drop README.source



changelog:
-shc (3.8.7-2) unstable; urgency=medium

+shc (3.8.7-2) unstable; urgency=low


well your previous uploader uploaded with medium instead of low, please adapt 
the changelog accordingly

copyright:
please update copyright years

patches:
they might be upstreamed, but maybe please use something like
"?=" instead of "=" that way they will be assigned only if not already assigned

http://stackoverflow.com/questions/448910/makefile-variable-assignment

the other patches should be upstreamed IMHO.

cheers,

G.

Bug#799529: RFS: shc/3.8.9b-1 new upstream release

[Tong Sun]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "shc"

 * Package name: shc
   Version : 3.8.9b-1
   Upstream Author : Francisco Rosales <fro...@fi.upm.es>.
 * URL : http://www.datsi.fi.upm.es/~frosal/
 * License : GPL-2.0
   Section : devel


It builds those binary packages:

shc   - Generic shell script compiler

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

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

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

dget -x http://mentors.debian.net/debian/pool/main/s/shc/shc_3.8.9b-1.dsc

Changes since the last upload:

   * New upstream release
   * Updated Standard-version to 3.9.6.
   * redo the makefile patching from scratch

More information about changes can be obtained from
https://github.com/suntong/shc-build/commits/master


Regards,

Tong Sun

Re: RFS: ranger/1.7.1-1 (new upstream release)

[Gianfranco Costamagna]

Hi, Built, the package is in a really good shape




:)

Just a nitpick, you might want to mention copyright changes in the changelog
(this wasn't a showstopper since the license didn't change, the changes were 
minimal)

keep up the good work!

cheers,

G.

New upstream release

[Daniel Echeverry]

Hi mentors.

Today, upstream announce a new maintenance release of Calamaris. I
updated the package in mentors with the new changes.

http://mentors.debian.net/debian/pool/main/c/calamaris/calamaris_2.99.4.2-1.dsc

Regards
Daniel

-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
Linux user: #477840
Debian user
Software libre


-- 
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/CAJi_FcjVYsJzRm=i5q7hhfn3jtpijt1zmus26exysbtbvuv...@mail.gmail.com

GBP and moving to a new upstream release...

[Darryl L. Pierce]

I've been following the steps as best I can here [1] to upgrade my
package (qpid-proton) to the latest upstream release (0.9). However,
these steps result in a merge commit (actually, they result in a huge
set of conflicts) and that strikes me as a Bad Thing (tm).

Why does GBP try to merge, rather than cherry pick, the upstream version
onto master? That will always result in an error since upstream only
holds the original code while master is interim changes to the package.

What is the right way to go about this?

[1] 
http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.NEW.UPSTREAM
-- 
Darryl L. Pierce mcpie...@gmail.com
http://mcpierce.blogspot.com/
Famous last words:
   I wonder what happens if we do it this way?


pgpYcETk6AXTX.pgp
Description: PGP signature

Re: GBP and moving to a new upstream release...

[Dominique Dumont]

On Thursday 09 April 2015 09:21:24 Darryl L. Pierce wrote:
 I've been following the steps as best I can here [1] to upgrade my
 package (qpid-proton) to the latest upstream release (0.9). However,
 these steps result in a merge commit (actually, they result in a huge
 set of conflicts) and that strikes me as a Bad Thing (tm).

I've seen such behavior. It always boiled down a previous mistake done with 
the git repo.

 Why does GBP try to merge, rather than cherry pick, the upstream version
 onto master? That will always result in an error since upstream only
 holds the original code while master is interim changes to the package.

No. There should be no conflict: packaging activity only modifies files in 
debian/ directory which is missing for upstream.

 What is the right way to go about this?

First, fix your git repo before attempting an import:
- watch file is broken
- several files have git merge artifacts (try a «ack ''» in your repo)
- upstream and pristine-tar branches are missing (you may have forgotten to 
push them).

If you want other people to contribute to this package, please make sure that 
tags do match the released packages (they don't: tag 0.7-2 is missing and the 
commit for this release is missing).

Hope this helps

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

signature.asc
Description: This is a digitally signed message part.

Re: GBP and moving to a new upstream release...

[Darryl L. Pierce]

On Thu, Apr 09, 2015 at 05:47:51PM +0200, Dominique Dumont wrote:
 On Thursday 09 April 2015 09:21:24 Darryl L. Pierce wrote:
  I've been following the steps as best I can here [1] to upgrade my
  package (qpid-proton) to the latest upstream release (0.9). However,
  these steps result in a merge commit (actually, they result in a huge
  set of conflicts) and that strikes me as a Bad Thing (tm).
 
 I've seen such behavior. It always boiled down a previous mistake done with 
 the git repo.
 
  Why does GBP try to merge, rather than cherry pick, the upstream version
  onto master? That will always result in an error since upstream only
  holds the original code while master is interim changes to the package.
 
 No. There should be no conflict: packaging activity only modifies files in 
 debian/ directory which is missing for upstream.
 
  What is the right way to go about this?

Which repo are you looking at? Mine [1] or the Debian one?

 First, fix your git repo before attempting an import:
 - watch file is broken

Done.

 - several files have git merge artifacts (try a «ack ''» in your repo)

 - upstream and pristine-tar branches are missing (you may have forgotten to 
 push them).

I'm not sure which repo you're looking at. My github repo has these
branches.

 If you want other people to contribute to this package, please make sure that 
 tags do match the released packages (they don't: tag 0.7-2 is missing and the 
 commit for this release is missing).

I contacted my mentor about this: I got an email about a week or two ago
saying that my packages were being deleted since I hadn't found a
sponsor after 20 weeks. Which is not correct as he is my sponsor on
this.
 
[1] http://www.github.com/mcpierce/debian-qpid-proton

-- 
Darryl L. Pierce mcpie...@gmail.com
http://mcpierce.blogspot.com/
Famous last words:
   I wonder what happens if we do it this way?


pgp4XJS4ev3p8.pgp
Description: PGP signature

Bug#750592: marked as done (RFS: pyformex/0.9.1-1 -- new upstream release, fixes #704458 #750351)

[Debian Bug Tracking System]

Your message dated Tue, 25 Nov 2014 16:23:45 +
with message-id e1xtiu1-0005l0...@quantz.debian.org
and subject line closing RFS: pyformex/0.9.1-1 -- new upstream release, fixes 
#704458 #750351
has caused the Debian Bug report #750592,
regarding RFS: pyformex/0.9.1-1 -- new upstream release, fixes #704458 #750351
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.)


-- 
750592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  I am looking for a sponsor for my package pyformex

 * Package name: pyformex
   Version : 0.9.1-3
   Upstream Author : benedict.verheg...@ugent.be
 * URL : pyformex.org
 * License : GPL3
   Section : science

  It builds those binary packages:

 pyformex   - program to create 3D geometry from Python scripts
 pyformex-extra - program to create 3D geometry from Python scripts (extras)
   pyformex-lib - program to create 3D geometry from Python scripts (libs)

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

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


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

dget -x
http://mentors.debian.net/debian/pool/main/p/pyformex/pyformex_0.9.1-3.dsc

  More information about pyformex can be obtained from http://pyformex.org

  Changes since the last upload:

New upstream release
Place architecture independent files under /usr/share
Fix bug #750351



  Regards,
   Benedict Verhegghe
---End Message---
---BeginMessage---
Package pyformex has been removed from mentors.---End Message---

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Eriberto Mota]

Perfect!

Thanks a lot for your work (as packager and as upstream).

Cheers,

Eriberto


2014-09-14 11:45 GMT-03:00 Dimitar Ivanov drim...@freeshell.de:
 Hi Eriberto,

 may be my last message was not very clear or visually well-formated with the
 statment that the pakcage can be downloaded also from mentors.d.n (it should
 be there since Fri Sep 5). And I just tested successfully :-) fetching it
 by:

 dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc


 Cheers,
 Dimitar


 On Sun, 14 Sep 2014, Eriberto wrote:

 Hi Dimitar,

 A good work. However, the VCS is for your control. Please, upload your
 package to mentors.d.n to make easier my work. As a tip for you, all
 packages needing review must be put in mentors.d.n.

 I will wait for you.

 Cheers,

 Eriberto




 A new package is uploaded:

 dget -x
 http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc



 Hi Eriberto,

 I finished now with the Git-integration of my package. The new repository
 is
 published under the collab-maint project on Alioth:

 http://anonscm.debian.org/cgit/collab-maint/stda.git

 All previous issues with the package should be fixed in the current
 version.
 Also the corresponding 'Vcs-Browser' and 'Vcs-Git' fields in the
 d/control
 file are defined respectively.

 Thanks a lot for you continuous support!

 Cheers,
 Dimitar





-- 
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/cap+dxjczlbpy-attbjqeq8qdiftgp_f98hyaksz4hmuozzd...@mail.gmail.com

Bug#753487: marked as done (RFS: stda/1.3.1-2 -- new upstream release (package already in Debian))

[Debian Bug Tracking System]

Your message dated Mon, 15 Sep 2014 17:36:39 -0300
with message-id 
cap+dxjczlbpy-attbjqeq8qdiftgp_f98hyaksz4hmuozzd...@mail.gmail.com
and subject line Re: Bug#753487: RFS: stda/1.3.1-1 -- new upstream release 
(package already in Debian)
has caused the Debian Bug report #753487,
regarding RFS: stda/1.3.1-2  -- new upstream release (package already in Debian)
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.)


-- 
753487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753487
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 stda

 * Package name: stda
   Version : 1.3.1-1
   Upstream Author : Dimitar Ivanov dimitar.iva...@mirendom.net
 * URL : http://gnu.mirendom.net/stda.html
 * License : GPLv3+
   Section : math

  It builds those binary packages:

stda  - simple tools for data analysis (stda)

Following programs are included in stda:
* maphimbu   - histogram builder for 1-d numerical and text data
* mintegrate - evaluate average/sum/integral/derivative of 1-d numerical 
data
* mmval  - find minimum and maximum value in a data set
* muplot - plot a multi-curve figure from multiple data by using Gnuplot
* nnum   - produce a series of equally separated integers or floats
* prefield   - prepare input file for 'muplot' to plot 2-d fields by arrows


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

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


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

dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-1.dsc


Regards,
Dimitar
---End Message---
---BeginMessage---
Perfect!

Thanks a lot for your work (as packager and as upstream).

Cheers,

Eriberto


2014-09-14 11:45 GMT-03:00 Dimitar Ivanov drim...@freeshell.de:
 Hi Eriberto,

 may be my last message was not very clear or visually well-formated with the
 statment that the pakcage can be downloaded also from mentors.d.n (it should
 be there since Fri Sep 5). And I just tested successfully :-) fetching it
 by:

 dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc


 Cheers,
 Dimitar


 On Sun, 14 Sep 2014, Eriberto wrote:

 Hi Dimitar,

 A good work. However, the VCS is for your control. Please, upload your
 package to mentors.d.n to make easier my work. As a tip for you, all
 packages needing review must be put in mentors.d.n.

 I will wait for you.

 Cheers,

 Eriberto




 A new package is uploaded:

 dget -x
 http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc



 Hi Eriberto,

 I finished now with the Git-integration of my package. The new repository
 is
 published under the collab-maint project on Alioth:

 http://anonscm.debian.org/cgit/collab-maint/stda.git

 All previous issues with the package should be fixed in the current
 version.
 Also the corresponding 'Vcs-Browser' and 'Vcs-Git' fields in the
 d/control
 file are defined respectively.

 Thanks a lot for you continuous support!

 Cheers,
 Dimitar


---End Message---

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Eriberto]

Hi Dimitar,

A good work. However, the VCS is for your control. Please, upload your
package to mentors.d.n to make easier my work. As a tip for you, all
packages needing review must be put in mentors.d.n.

I will wait for you.

Cheers,

Eriberto


2014-09-11 20:14 GMT-03:00 Dimitar Ivanov drim...@freeshell.de:

 On Wed, 27 Aug 2014, Dimitar Ivanov wrote:


 Starting to use external GIT repository means that I need to change my
 work flow and to integrate the .git-tree in my present source-tree (also
 adjusting Makefile, etc) and how to structure the branches and tags before
 pushing changes. So, I'm currently tying to find out what is a common way to
 do so when preparing a debian package (e.g. [1]). If you know some
 documentation describing the standard procedures or good practices, this
 will be very helpful.

 .
 .
 .


 A new package is uploaded:

 dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc



 Hi Eriberto,

 I finished now with the Git-integration of my package. The new repository is
 published under the collab-maint project on Alioth:

 http://anonscm.debian.org/cgit/collab-maint/stda.git

 All previous issues with the package should be fixed in the current version.
 Also the corresponding 'Vcs-Browser' and 'Vcs-Git' fields in the d/control
 file are defined respectively.

 Thanks a lot for you continuous support!

 Cheers,
 Dimitar



-- 
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/CAP+dXJdpK5Gk_F6DQEJnYwQ82M0OL2xurkWo=jvnxcbnjrc...@mail.gmail.com

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Dimitar Ivanov]

Hi Eriberto,

may be my last message was not very clear or visually well-formated with 
the statment that the pakcage can be downloaded also from mentors.d.n 
(it should be there since Fri Sep 5). And I just tested successfully :-) 
fetching it by:


dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc


Cheers,
Dimitar


On Sun, 14 Sep 2014, Eriberto wrote:


Hi Dimitar,

A good work. However, the VCS is for your control. Please, upload your
package to mentors.d.n to make easier my work. As a tip for you, all
packages needing review must be put in mentors.d.n.

I will wait for you.

Cheers,

Eriberto






A new package is uploaded:

dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc




Hi Eriberto,

I finished now with the Git-integration of my package. The new repository is
published under the collab-maint project on Alioth:

http://anonscm.debian.org/cgit/collab-maint/stda.git

All previous issues with the package should be fixed in the current version.
Also the corresponding 'Vcs-Browser' and 'Vcs-Git' fields in the d/control
file are defined respectively.

Thanks a lot for you continuous support!

Cheers,
Dimitar






--
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/alpine.deb.2.02.1409141630040.5...@freeshell.de

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Dimitar Ivanov]

On Wed, 27 Aug 2014, Dimitar Ivanov wrote:



Starting to use external GIT repository means that I need to change my work 
flow and to integrate the .git-tree in my present source-tree (also adjusting 
Makefile, etc) and how to structure the branches and tags before pushing 
changes. So, I'm currently tying to find out what is a common way to do so 
when preparing a debian package (e.g. [1]). If you know some documentation 
describing the standard procedures or good practices, this will be very 
helpful.

.
.
.


A new package is uploaded:

dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc




Hi Eriberto,

I finished now with the Git-integration of my package. The new repository 
is published under the collab-maint project on Alioth:


http://anonscm.debian.org/cgit/collab-maint/stda.git

All previous issues with the package should be fixed in the current 
version. Also the corresponding 'Vcs-Browser' and 'Vcs-Git' fields in the 
d/control file are defined respectively.


Thanks a lot for you continuous support!

Cheers,
Dimitar


--
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/alpine.deb.2.02.1409120054390.16...@freeshell.de

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Dimitar Ivanov]

Hi,

On Tue, 26 Aug 2014, Eriberto wrote:



Hi,

I saw you made a new revision (-2) of your package. However, the
1.3.1-1 not exist in Debian. So you must change 'unstable' by
'UNRELEASED' in d/changelog when saying about 1.3.1-1.



Done.



Well, but a short description is not a complete sentence, why should one put
a dot there? In my opinion it should stay as it is - see for example: [1]
http://sources.debian.net/src/tcputils/0.6.2-9/debian/control/
[2] http://sources.debian.net/src/cutils/1.6-3.1/debian/control/
Or maybe a semicolon ';' can be put at the end..



It is a rule of writting, a suggestion, not a Debian rule. You can use
semicolon too. Note that have several issues in several packages in

Done - I put a semicolon.


Debian. So, I can use them to justify all problems in a package. Sorry
but my intent is help you to release a package with good conditions.

Yes, and that's wath I respect much.



Ok, how about hosting a repository of the stda-package on Alioth within the
collab-maint project: would you like to support this? Otherwise I'll create
a git-repository within the GNU Savannah's hosting service - what do you
think?



Yes, I can be your advocate to get access to collab-maint. But you can
use an external service too.

Starting to use external GIT repository means that I need to change my 
work flow and to integrate the .git-tree in my present source-tree (also 
adjusting Makefile, etc) and how to structure the branches and tags before 
pushing changes. So, I'm currently tying to find out what is a common way 
to do so when preparing a debian package (e.g. [1]). If you know some 
documentation describing the standard procedures or good practices, this 
will be very helpful.


[1] http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html


Cheers,

Eriberto



A new package is uploaded:

dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc

Thanks,

Dimitar


--
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/alpine.deb.2.00.1408271815430.22...@freeshell.de

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Jakub Wilk]

* Eriberto Mota eribe...@debian.org, 2014-08-22, 13:07:
Sorry, but when I said punctuation, I meant to put a dot in end of each 
line. Example:


 * maphimbu   - histogram builder for 1-d numerical and text data.
 * mintegrate - evaluate average/sum/integral/derivative of 1-d numerical data.


I'd like to recommend both of you excellent “English for software 
localisation” by Justin B Rye:

http://www.xibalba.demon.co.uk/jbr/linux/esl.html#e5

--
Jakub Wilk


--
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/20140827174810.ga6...@jwilk.net

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Eriberto]

2014-08-25 12:21 GMT-03:00 Dimitar Ivanov drim...@freeshell.de:
 Hi Eriberto,

Hi,

I saw you made a new revision (-2) of your package. However, the
1.3.1-1 not exist in Debian. So you must change 'unstable' by
'UNRELEASED' in d/changelog when saying about 1.3.1-1.


 2. d/control:

 Sorry, but when I said punctuation, I meant to put a dot in end of
 each line. Example:

  * maphimbu   - histogram builder for 1-d numerical and text data.
  * mintegrate - evaluate average/sum/integral/derivative of 1-d numerical
 data.

 Well, but a short description is not a complete sentence, why should one put
 a dot there? In my opinion it should stay as it is - see for example: [1]
 http://sources.debian.net/src/tcputils/0.6.2-9/debian/control/
 [2] http://sources.debian.net/src/cutils/1.6-3.1/debian/control/
 Or maybe a semicolon ';' can be put at the end..


It is a rule of writting, a suggestion, not a Debian rule. You can use
semicolon too. Note that have several issues in several packages in
Debian. So, I can use them to justify all problems in a package. Sorry
but my intent is help you to release a package with good conditions.
But you can drop my suggestions, no problems. If no technical problems
in package mechanisms, no problem.


 You really need a VCS. It is very important to keep the package
 control across the versions. I suggest to use GitHub (easy). Please,
 put 'github tutorial' in Google. You need put, at least, the debian/
 directory under the VCS control. In d/control you need add Vcs-Browser
 and Vcs-Git fields. You can see an example here:

 http://sources.debian.net/src/mac-robber/1.02-3/debian/control/

 Ok, how about hosting a repository of the stda-package on Alioth within the
 collab-maint project: would you like to support this? Otherwise I'll create
 a git-repository within the GNU Savannah's hosting service - what do you
 think?


Yes, I can be your advocate to get access to collab-maint. But you can
use an external service too.

Cheers,

Eriberto


-- 
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/CAP+dXJd-mDJt38xf7GcONO4hN8X+66-0LxHx7udq57r4ckej=q...@mail.gmail.com

Bug#758966: RFS: confget/1.05-1 (new upstream release)

[Peter Pentchev]

On Sun, Aug 24, 2014 at 02:46:04AM -0300, Eriberto Mota wrote:
 tags 758966 moreinfo
 thanks
 
 
 Hi Peter.

Hi, and thanks a lot for looking at confget! :) (and at all the other
packages that you've sponsored or commented on recently!)

 Please,
 
 1. d/copyright: I suggest you contract all data about upstream to be
 less confused[1]. Example:
 
 
 Files: *
 Copyright: 2008-2013 Peter Pentchev r...@ringlet.net
 License: BSD-2-clause
 
 Files: makedep.sh t/t1.ini t/t2.ini
 Copyright: ?
 License: public-domain
   This file is hereby placed in the public domain.
 
 Files: debian/*
 Copyright: 2008-2014  Peter Pentchev r...@ringlet.net
 License: BSD-2-clause
 
 
 Note that I changed the copyright field in second block and added your
 email address to other blocks. Please, remove the field 'License' from
 header.
 
 [1] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#fields

Hmm.  Yes, I understand why you personally might prefer coalesced
blocks, but IMHO there's no harm in keeping the copyright file an
*exact* description of what the upstream source says.  It makes things
easier for an automated license check tool to make sure that I haven't
missed anything; sometimes I use something like:

  licensecheck --check=. --ignore='/debian/' -r --copyright -m . | sort -k2,20

So, if it's all the same to you, I'd really rather keep it this way -
mirroring the full information from the upstream source :)

As for the Copyright: ? line for the public domain file, I personally
think that a ? or even a N/A or similar notation is a bit less
descriptive than a piece of text that explicitly mentions public
domain.  Yes, it is explicitly mentioned on the next line, in the
contents of the License field, but IMHO again there's no harm in
putting it in the copyright field, too, and for me personally a ?
would be kind of confusing (hey, wait, does this mean that the package
maintainer intended to check what the copyright notice should be and
then later forgot to check? :))

About my e-mail address in the copyright notices: oof, good catch! :)
However, I do not think that this problem should be solved in the Debian
package's copyright file - once again, the copyright file should reflect
the information in the upstream source, and since I've forgotten to put
my e-mail address in the confget upstream source files, I shouldn't
claim otherwise in the copyright file :)  This will be fixed in
confget-1.06, but until then IMHO the copyright file should remain
as-is.

And about the license in the copyright file header - er, why?  From
the way I read the Machine-readable debian/copyright file standard,
there is an optional License field in the header, and IMHO it is a
very good way to make this information very easily visible - just one
look at the header of the copyright file tells you what the program is,
where it was downloaded from, who wrote it, and what is the license on
most (if not all) of its source files.  I've had it in all of my
packages ever since it was added to the DEP-5 draft, I've seen it in a
couple of others' packages, too, and I still believe that it's a good
idea :)

 2. d/rules: remove the second line. Why you used many options in
 rules?

Well, I happen to very much like the C compiler giving me many, many
warnings - both about my code and about others' code that I package for
Debian or FreeBSD or whatever :)  So I make a point of always building
all of my programs (and all third-party programs that I maintain) with
the strictest possible set of warning flags, and usually with -Werror,
too, so that those are not just warnings, but real errors.

One might ask confget is your program, why don't you put these flags in
the upstream source then?; the answer is that all of these warning
flags are GCC-specific - yes, they will work with Clang, but they may
not work at all on any other compiler that somebody wants to build
confget with.  So I cannot unconditionally add them to the upstream
Makefile, although I *do* always build with them when I'm working on
upstream confget (and stdsyslog, and timelimit, etc).

But when I build a Debian package of confget, I know that it will be
compiled with GCC (or with a compiler that understands most of GCC's
command-line options), so I can afford to use GCC-specific warning
flags.  When I build my Debian packages, I also have a local addition of
werror in the DEB_BUILD_OPTIONS environment variable, so the rules
file also adds -Werror and things break very quickly if I've messed up
:)  But yeah, I learned the hard way that releasing a Debian package
with -Werror by default leads to results that are just a little bit
harsher than releasing it without -Werror by default and reading the
logs.

Ah, yeah, now we come to the last important point - since these are just
warnings, what use are they at all?  Well, if you're as pedantic as I
am, they are actually useful - after any of my packages is uploaded to
the Debian archive, I open a tab in my browser, point it to

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Dimitar Ivanov]

Hi Eriberto,

On Fri, 22 Aug 2014, Eriberto Mota wrote:


2014-08-22 12:00 GMT-03:00 Dimitar Ivanov drim...@freeshell.de:

Hello Eriberto,


Hi!



I implemented most of the changes you requested.


1. d/compat: change to 9.


Done.



Not done. I can see 7.

Fixed.





2. d/control:
 - Set 9 to debhelper.
 - Consider change the priority to optional. Please, read it[1].
 - Create a VCS to control your debian/ versions. You can use github
or other. So, add the Vcs-Browser and Vcs-{Git|Svn|Cvs} to d/control.
 - Add a punctuation in each item in long description.

[1] https://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities


Done, except the VCS stuff.. Because I'm not sure what kind of a
VCS-entiries should I define in d/control, I'll write you a separate mail
related to what exactly and how it should be version-controlled. May be
presently you can review the new package which don't include VCS-entries,
and later I can produce a new debian-release where Vcs-Browser and
Vcs-{Git|Svn|Cvs} are defined in d/control.



Sorry, but when I said punctuation, I meant to put a dot in end of
each line. Example:

 * maphimbu   - histogram builder for 1-d numerical and text data.
 * mintegrate - evaluate average/sum/integral/derivative of 1-d numerical data.
Well, but a short description is not a complete sentence, why should one 
put a dot there? In my opinion it should stay as it is - see for example: 
[1] http://sources.debian.net/src/tcputils/0.6.2-9/debian/control/

[2] http://sources.debian.net/src/cutils/1.6-3.1/debian/control/
Or maybe a semicolon ';' can be put at the end..



You really need a VCS. It is very important to keep the package
control across the versions. I suggest to use GitHub (easy). Please,
put 'github tutorial' in Google. You need put, at least, the debian/
directory under the VCS control. In d/control you need add Vcs-Browser
and Vcs-Git fields. You can see an example here:

http://sources.debian.net/src/mac-robber/1.02-3/debian/control/
Ok, how about hosting a repository of the stda-package on Alioth within 
the collab-maint project: would you like to support this? Otherwise I'll 
create a git-repository within the GNU Savannah's hosting service - what 
do you think?




You need to learn about (git) clone, add, rm, commit and tag.

No problem.





4. d/rules: please, update to new (reduced) format. Your package is
very simple and it will work. Ask me if you have doubts. An example:
http://sources.debian.net/src/pcapfix/1.0.2-3/debian/rules/


Done.


You used a 'clean' target in your d/rules. The correct is use
'override_dh_auto_clean'. Please, 'man dh' and search by 'override'.
However, is easier use d/clean file (man dh_clean). But I think this
clean step in your package is unnecessary. Please, remove and test.
Thanks for you suggestion - I put now an empty 'override_dh_auto_clean' 
target. Without it, debhelper executes 'make clean' and then creates the 
man-pages again which is not required when building the debian packages - 
the pages are provided with the tarball.






5. d/watch: add escapes before tarball dot (\.tar\.gz). Your watch is
showing the version 1.3.1. I already read about it in previous
messages. I need the final program in your site to check the
integrity.


Well, since '.tar.gz' is at the end of the string, and since I'm not going
to create on my web-page some other package-related files with funny
filenames ending with some chartarsome_chargz, I think that .tar.gz
without escapes is ok - it is not 100% exact but it is more readable and
'uscan --verbose' works perfectly. But if you mind, I can change it as
requested.



Nop. It is a grep (dot == any character except newline). Your d/watch
I'm aware of the meaning of the dot-character in d/watch file. My point 
was that in this case the regex is precise enough and readability makes 
more sense. But anyway, I changed it.



can work but the correct is escape the dots. Please, read it[1] if you
need know more about the watch file.

[1] http://eriberto.pro.br/blog/?p=1459
Ok, the dots are escaped now. Thanks for the link to your comprehensive 
blog-article - it's an interesting read.






You can download the package source by:
wget http://gnu.mirendom.net/download.cgi/gnu/stda/stda-1.3.1.tar.gz


I think it was a mistake. Sorry.


I saw that your package depends of help2man to build. Please, add it
in d/control (Build-Depends).
Well, help2man is used to build as default the man-pages. But since I 
provide the man-pages in the tarball, it's not necessary to build them. 
Hence (as mentioned above) I override the dh_auto_clean target and I think 
that Build-Depends is not needed.


Currently a new package is uploaded:

dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-2.dsc



Thanks Dimitar.

Cheers,

Eriberto



Thanks a lot,
Dimitar


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

Bug#758966: marked as done (RFS: confget/1.05-1 (new upstream release))

[Debian Bug Tracking System]

Your message dated Mon, 25 Aug 2014 17:19:14 -0300
with message-id 
cap+dxjd-kow7cznwwohw3lud5r5v6gku+felkb0uotgpkgm...@mail.gmail.com
and subject line Re: Bug#758966: RFS: confget/1.05-1 (new upstream release)
has caused the Debian Bug report #758966,
regarding RFS: confget/1.05-1 (new upstream release)
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.)


-- 
758966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758966
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 confget

 * Package name: confget
   Version : 1.05-1
   Upstream Author : Peter Pentchev r...@ringlet.net
 * URL : http://devel.ringlet.net/textproc/confget/
 * License : BSD
   Section : text

It builds a single binary package, tested with sbuild, lintian and adequate:

  confget- read variables from INI-style configuration files

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

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

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

  dget -x 
http://mentors.debian.net/debian/pool/main/c/confget/confget_1.05-1.dsc

More information about confget can be obtained from
http://devel.ringlet.net/textproc/confget/

Changes since the last upload:

confget (1.05-1) unstable; urgency=medium

  * Update the copyright file:
- convert it to the 1.0 format
- separate lists of copyrighted files with whitespace, not commas
- bump the year of my copyright notice
- fix the upstream homepage location
  * Bump Standards-Version to 3.9.5 with no changes.
  * Bump the debhelper compatibility level to 9 with no changes.
  * Get the hardening options directly from debhelper:
- remove the build dependency on hardening-includes
- no longer include the hardening Makefile snippet into the rules file
- explicitly enable all the hardening features; they may be disabled
  in the future if confget should fail to build anywhere
- use DEB_CFLAGS_MAINT_APPEND to, well, append to CFLAGS
  * Enable parallel building - not that it matters a lot in this case :)
  * New upstream release:
- honors CPPFLAGS now, so the hardening flags may be passed as-is
- autodetects getline(3) support, so no need for CFLAGS_CONF
- renames PCRE_CFLAGS to PCRE_CPPFLAGS, so follow suit
- update the copyright years in the copyright file
- follow upstream and switch from -ansi to -std=c99
  * Remove the obsolete DM-Upload-Allowed field.
  * Drop the source compression options; dpkg-dev's defaults are good enough.
  * Update the watch file after the devel.ringlet.net website change.
  * Let uscan verify upstream's signature against my own key.

 -- Peter Pentchev r...@ringlet.net  Sat, 23 Aug 2014 12:07:22 +0300

Thanks in advance for your time!

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@freebsd.org p.penc...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Uploaded. Thanks.

Eriberto---End Message---

Bug#758966: RFS: confget/1.05-1 (new upstream release)

[Peter Pentchev]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package confget

 * Package name: confget
   Version : 1.05-1
   Upstream Author : Peter Pentchev r...@ringlet.net
 * URL : http://devel.ringlet.net/textproc/confget/
 * License : BSD
   Section : text

It builds a single binary package, tested with sbuild, lintian and adequate:

  confget- read variables from INI-style configuration files

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

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

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

  dget -x 
http://mentors.debian.net/debian/pool/main/c/confget/confget_1.05-1.dsc

More information about confget can be obtained from
http://devel.ringlet.net/textproc/confget/

Changes since the last upload:

confget (1.05-1) unstable; urgency=medium

  * Update the copyright file:
- convert it to the 1.0 format
- separate lists of copyrighted files with whitespace, not commas
- bump the year of my copyright notice
- fix the upstream homepage location
  * Bump Standards-Version to 3.9.5 with no changes.
  * Bump the debhelper compatibility level to 9 with no changes.
  * Get the hardening options directly from debhelper:
- remove the build dependency on hardening-includes
- no longer include the hardening Makefile snippet into the rules file
- explicitly enable all the hardening features; they may be disabled
  in the future if confget should fail to build anywhere
- use DEB_CFLAGS_MAINT_APPEND to, well, append to CFLAGS
  * Enable parallel building - not that it matters a lot in this case :)
  * New upstream release:
- honors CPPFLAGS now, so the hardening flags may be passed as-is
- autodetects getline(3) support, so no need for CFLAGS_CONF
- renames PCRE_CFLAGS to PCRE_CPPFLAGS, so follow suit
- update the copyright years in the copyright file
- follow upstream and switch from -ansi to -std=c99
  * Remove the obsolete DM-Upload-Allowed field.
  * Drop the source compression options; dpkg-dev's defaults are good enough.
  * Update the watch file after the devel.ringlet.net website change.
  * Let uscan verify upstream's signature against my own key.

 -- Peter Pentchev r...@ringlet.net  Sat, 23 Aug 2014 12:07:22 +0300

Thanks in advance for your time!

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@freebsd.org p.penc...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


signature.asc
Description: Digital signature

Bug#758966: RFS: confget/1.05-1 (new upstream release)

[Eriberto Mota]

tags 758966 moreinfo
thanks


Hi Peter.

Please,

1. d/copyright: I suggest you contract all data about upstream to be
less confused[1]. Example:


Files: *
Copyright: 2008-2013 Peter Pentchev r...@ringlet.net
License: BSD-2-clause

Files: makedep.sh t/t1.ini t/t2.ini
Copyright: ?
License: public-domain
  This file is hereby placed in the public domain.

Files: debian/*
Copyright: 2008-2014  Peter Pentchev r...@ringlet.net
License: BSD-2-clause


Note that I changed the copyright field in second block and added your
email address to other blocks. Please, remove the field 'License' from
header.

[1] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#fields

2. d/rules: remove the second line. Why you used many options in
rules? I think that your rules can be cleaned. It will work:


#!/usr/bin/make -f

%:
dh $@ --parallel

override_dh_auto_install:
dh_auto_install -- DESTDIR=${CURDIR}/debian/confget PREFIX=/usr \
MANDIR=/usr/share/man/man BINGRP=root MANGRP=root \
EXAMPLESDIR=/usr/share/doc/confget/examples

Thanks for your work.

Cheers,

Eriberto


2014-08-23 7:09 GMT-03:00 Peter Pentchev r...@ringlet.net:
 Package: sponsorship-requests
 Severity: normal

 Dear mentors,

 I am looking for a sponsor for my package confget

  * Package name: confget
Version : 1.05-1
Upstream Author : Peter Pentchev r...@ringlet.net
  * URL : http://devel.ringlet.net/textproc/confget/
  * License : BSD
Section : text

 It builds a single binary package, tested with sbuild, lintian and adequate:

   confget- read variables from INI-style configuration files

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

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

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

   dget -x 
 http://mentors.debian.net/debian/pool/main/c/confget/confget_1.05-1.dsc

 More information about confget can be obtained from
 http://devel.ringlet.net/textproc/confget/

 Changes since the last upload:

 confget (1.05-1) unstable; urgency=medium

   * Update the copyright file:
 - convert it to the 1.0 format
 - separate lists of copyrighted files with whitespace, not commas
 - bump the year of my copyright notice
 - fix the upstream homepage location
   * Bump Standards-Version to 3.9.5 with no changes.
   * Bump the debhelper compatibility level to 9 with no changes.
   * Get the hardening options directly from debhelper:
 - remove the build dependency on hardening-includes
 - no longer include the hardening Makefile snippet into the rules file
 - explicitly enable all the hardening features; they may be disabled
   in the future if confget should fail to build anywhere
 - use DEB_CFLAGS_MAINT_APPEND to, well, append to CFLAGS
   * Enable parallel building - not that it matters a lot in this case :)
   * New upstream release:
 - honors CPPFLAGS now, so the hardening flags may be passed as-is
 - autodetects getline(3) support, so no need for CFLAGS_CONF
 - renames PCRE_CFLAGS to PCRE_CPPFLAGS, so follow suit
 - update the copyright years in the copyright file
 - follow upstream and switch from -ansi to -std=c99
   * Remove the obsolete DM-Upload-Allowed field.
   * Drop the source compression options; dpkg-dev's defaults are good enough.
   * Update the watch file after the devel.ringlet.net website change.
   * Let uscan verify upstream's signature against my own key.

  -- Peter Pentchev r...@ringlet.net  Sat, 23 Aug 2014 12:07:22 +0300

 Thanks in advance for your time!

 G'luck,
 Peter

 --
 Peter Pentchev  r...@ringlet.net r...@freebsd.org p.penc...@storpool.com
 PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
 Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13

 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing
   APT policy: (990, 'testing')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386

 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
 Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash


-- 
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/cap+dxjdkpjsxejuzndtf1dbm0kkpev-gq59nktf7yr9du4w...@mail.gmail.com

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Dimitar Ivanov]

Hello Eriberto,

I implemented most of the changes you requested.

On Wed, 20 Aug 2014, Eriberto Mota wrote:


tags 753487 moreinfo
thanks


Hi Dimitar.

Please:

1. d/compat: change to 9.


Done.


2. d/control:
 - Set 9 to debhelper.
 - Consider change the priority to optional. Please, read it[1].
 - Create a VCS to control your debian/ versions. You can use github
or other. So, add the Vcs-Browser and Vcs-{Git|Svn|Cvs} to d/control.
 - Add a punctuation in each item in long description.

[1] https://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities
Done, except the VCS stuff.. Because I'm not sure what kind of a 
VCS-entiries should I define in d/control, I'll write you a separate mail 
related to what exactly and how it should be version-controlled. May be 
presently you can review the new package which don't include VCS-entries, 
and later I can produce a new debian-release where Vcs-Browser and 
Vcs-{Git|Svn|Cvs} are defined in d/control.



3. Update the d/copyright to 1.0 format. See it[2]. An example here[3].

[2] http://dep.debian.net/deps/dep5/
[3] http://sources.debian.net/src/gconjugue/0.7.5-2/debian/copyright/

Done.


4. d/rules: please, update to new (reduced) format. Your package is
very simple and it will work. Ask me if you have doubts. An example:
http://sources.debian.net/src/pcapfix/1.0.2-3/debian/rules/

Done.


5. d/watch: add escapes before tarball dot (\.tar\.gz). Your watch is
showing the version 1.3.1. I already read about it in previous
messages. I need the final program in your site to check the
integrity.
Well, since '.tar.gz' is at the end of the string, and since I'm not going 
to create on my web-page some other package-related files with funny 
filenames ending with some chartarsome_chargz, I think that 
.tar.gz without escapes is ok - it is not 100% exact but it is more 
readable and 'uscan --verbose' works perfectly. But if you mind, I can 
change it as requested.



You can download the package source by:
wget http://gnu.mirendom.net/download.cgi/gnu/stda/stda-1.3.1.tar.gz


6. Please, register all modifications in d/changelog.

Done.


Thanks for your work. I am waiting your package.

Cheers,

Eriberto



You can download the new package from m.d.n:

dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-1.dsc


Thanks,
Dimitar


--
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/alpine.deb.2.00.1408221343140.7...@freeshell.de

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Eriberto Mota]

2014-08-22 12:00 GMT-03:00 Dimitar Ivanov drim...@freeshell.de:
 Hello Eriberto,

Hi!


 I implemented most of the changes you requested.

 1. d/compat: change to 9.

 Done.


Not done. I can see 7.


 2. d/control:
  - Set 9 to debhelper.
  - Consider change the priority to optional. Please, read it[1].
  - Create a VCS to control your debian/ versions. You can use github
 or other. So, add the Vcs-Browser and Vcs-{Git|Svn|Cvs} to d/control.
  - Add a punctuation in each item in long description.

 [1] https://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities

 Done, except the VCS stuff.. Because I'm not sure what kind of a
 VCS-entiries should I define in d/control, I'll write you a separate mail
 related to what exactly and how it should be version-controlled. May be
 presently you can review the new package which don't include VCS-entries,
 and later I can produce a new debian-release where Vcs-Browser and
 Vcs-{Git|Svn|Cvs} are defined in d/control.


Sorry, but when I said punctuation, I meant to put a dot in end of
each line. Example:

  * maphimbu   - histogram builder for 1-d numerical and text data.
  * mintegrate - evaluate average/sum/integral/derivative of 1-d numerical data.

You really need a VCS. It is very important to keep the package
control across the versions. I suggest to use GitHub (easy). Please,
put 'github tutorial' in Google. You need put, at least, the debian/
directory under the VCS control. In d/control you need add Vcs-Browser
and Vcs-Git fields. You can see an example here:

http://sources.debian.net/src/mac-robber/1.02-3/debian/control/

You need to learn about (git) clone, add, rm, commit and tag.


 4. d/rules: please, update to new (reduced) format. Your package is
 very simple and it will work. Ask me if you have doubts. An example:
 http://sources.debian.net/src/pcapfix/1.0.2-3/debian/rules/

 Done.

You used a 'clean' target in your d/rules. The correct is use
'override_dh_auto_clean'. Please, 'man dh' and search by 'override'.
However, is easier use d/clean file (man dh_clean). But I think this
clean step in your package is unnecessary. Please, remove and test.


 5. d/watch: add escapes before tarball dot (\.tar\.gz). Your watch is
 showing the version 1.3.1. I already read about it in previous
 messages. I need the final program in your site to check the
 integrity.

 Well, since '.tar.gz' is at the end of the string, and since I'm not going
 to create on my web-page some other package-related files with funny
 filenames ending with some chartarsome_chargz, I think that .tar.gz
 without escapes is ok - it is not 100% exact but it is more readable and
 'uscan --verbose' works perfectly. But if you mind, I can change it as
 requested.


Nop. It is a grep (dot == any character except newline). Your d/watch
can work but the correct is escape the dots. Please, read it[1] if you
need know more about the watch file.

[1] http://eriberto.pro.br/blog/?p=1459


 You can download the package source by:
 wget http://gnu.mirendom.net/download.cgi/gnu/stda/stda-1.3.1.tar.gz

I think it was a mistake. Sorry.


I saw that your package depends of help2man to build. Please, add it
in d/control (Build-Depends).

Thanks Dimitar.

Cheers,

Eriberto


-- 
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/CAP+dXJfyUPWscwCM5QgER92jM7_2wrG=k3wzucdyntrwa7b...@mail.gmail.com

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Eriberto Mota]

tags 753487 moreinfo
thanks


Hi Dimitar.

Please:

1. d/compat: change to 9.

2. d/control:
  - Set 9 to debhelper.
  - Consider change the priority to optional. Please, read it[1].
  - Create a VCS to control your debian/ versions. You can use github
or other. So, add the Vcs-Browser and Vcs-{Git|Svn|Cvs} to d/control.
  - Add a punctuation in each item in long description.

[1] https://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities

3. Update the d/copyright to 1.0 format. See it[2]. An example here[3].

[2] http://dep.debian.net/deps/dep5/
[3] http://sources.debian.net/src/gconjugue/0.7.5-2/debian/copyright/

4. d/rules: please, update to new (reduced) format. Your package is
very simple and it will work. Ask me if you have doubts. An example:
http://sources.debian.net/src/pcapfix/1.0.2-3/debian/rules/

5. d/watch: add escapes before tarball dot (\.tar\.gz). Your watch is
showing the version 1.3.1. I already read about it in previous
messages. I need the final program in your site to check the
integrity.

6. Please, register all modifications in d/changelog.

Thanks for your work. I am waiting your package.

Cheers,

Eriberto



2014-07-02 9:43 GMT-03:00 Dimitar Ivanov drim...@freeshell.de:

 Package: sponsorship-requests
 Severity: normal

 Dear mentors,

 I am looking for a sponsor for my package stda

  * Package name: stda
Version : 1.3.1-1
Upstream Author : Dimitar Ivanov dimitar.iva...@mirendom.net
  * URL : http://gnu.mirendom.net/stda.html
  * License : GPLv3+
Section : math

   It builds those binary packages:

 stda  - simple tools for data analysis (stda)

 Following programs are included in stda:
 * maphimbu   - histogram builder for 1-d numerical and text data
 * mintegrate - evaluate average/sum/integral/derivative of 1-d numerical
 data
 * mmval  - find minimum and maximum value in a data set
 * muplot - plot a multi-curve figure from multiple data by using
 Gnuplot
 * nnum   - produce a series of equally separated integers or floats
 * prefield   - prepare input file for 'muplot' to plot 2-d fields by
 arrows


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

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


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

 dget -x
 http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-1.dsc


 Regards,
 Dimitar


 --
 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/alpine.deb.2.00.1407021439001.6...@freeshell.de



-- 
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/cap+dxjf1tut22eodgyb-4epg6cwstsixk+jhozikkbbhzek...@mail.gmail.com

Bug#740032: sweethome3d-textures: new upstream release 1.0.1

[Gabriele Giacone]

Control: reopen -1

Uploaded new upstream version 1.0.1:

http://mentors.debian.net/package/sweethome3d-textures

 dget -x 
http://mentors.debian.net/debian/pool/main/s/sweethome3d-textures/sweethome3d-textures_1.0.1-1.dsc

Thanks.


-- 
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/20140715084244.GA32007@jessie01

Bug#753813: marked as done (RFS: ngspice_26-1, a new upstream release)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jul 2014 08:36:52 +
with message-id 3024413.msMGNCaut2@hekla
and subject line RFS: ngspice_26-1, a new upstream release
has caused the Debian Bug report #753813,
regarding RFS: ngspice_26-1, a new upstream release
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.)


-- 
753813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753813
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 ngspice:

 * Package name: ngspice
   Version : 26-1
   Upstream Author : Paolo Nenzi, Holger Vogt
 * URL : http://ngspice.sourceforge.net/
 * License : MIT_MODERN, GPL-v2, SPICEDOC,...
   Section : electronics

  It builds those binary packages:

ngspice - Spice circuit simulator
tclspice- NGspice library for Tcl
ngspice-doc - Documentation for the NGspice circuit simulator

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

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


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

  dget -x 
http://mentors.debian.net/debian/pool/non-free/n/ngspice/ngspice_26-1.dsc

  Changes since the last upload:

  * New upstream release (Closes: #706821)
  * Bump standards version to 3.9.5
  * Make VCS field canonical
  * Change tcl version to 8.6
  * Remove part of patch, wish8.4 changed back to wish for tclspice examples
  * Add pdf manual
  * Remove DM-upload line from control
  * Add patch 03_fix_compilation.patch
(Thanks to Robert Larice)
  * Remove stripping of codemodel files
  * Add -BLT and -ltcl8.6 to configure for tclspice.
Needed by libtclspice
  * Remove ps manual
  * Remove hardening wrapper and exchange for dpkg-buildflags
  * Add dependency on libfftw3-dev


Regards,
Gudjon I. Gudjonsson
---End Message---
---BeginMessage---
Hi

Version 26-1 has already been uploaded by Andreas Tille so the bug should be 
closed.

Regards
Gudjon---End Message---

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Jakub Wilk]

[I don't indend to sponsor this package. Sorry!]

* Dimitar Ivanov drim...@freeshell.de, 2014-07-09, 00:27:

* URL : http://gnu.mirendom.net/stda.html

[snip]

There doesn't seem to be anything newer than 1.2.1 posted at that URL.


This is correct. The reason for this is that, since I'm the upstream 
author, first I'm trying to find a sponsor, or somebody who wants to 
review the package and could be a sponsor. Then I'll put the original 
tar on the URL. I just want this time that the upstream is released 
actually only if the package also will be put into Debian testing. If 
not, then I'll do not make a public release now, but in few months 
upgrade the package (bugs, new features, etc.) and try to find a 
sponsor again..


That's an odd workflow, if you ask me. But oh well. Here's my quick 
review:


+   sed -n '/BEGIN PGP SIGNATURE/,/END PGP SIGNATURE/p' \
+   $(PNAME)_$${dvers}_source.changes  $(PNAME)-$$vers.tar.gz.asc

I don't think you'll get a valid signature this way.

+  - default postscript canava set to landscape with size-ratio of 0.71

Typo? canava - canvas

+  - CONVFMT and OFMT varibles in 'awk' defined separately as %.17g

Typo: varibles - variables

+Remark: an user-defined function should have syntax conform to 'awk'.

Typos: an - a, conform - conforming

Changes to packaging are not documented in debian/changelog.

--
Jakub Wilk


--
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/20140710105617.ga6...@jwilk.net

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Dimitar Ivanov]

On Thu, 10 Jul 2014, Jakub Wilk wrote:



That's an odd workflow, if you ask me. But oh well. Here's my quick review:

+   sed -n '/BEGIN PGP SIGNATURE/,/END PGP SIGNATURE/p' \
+		$(PNAME)_$${dvers}_source.changes  
$(PNAME)-$$vers.tar.gz.asc


I don't think you'll get a valid signature this way.



You are right - I have changed this to:

gpg --armor --detach-sig $(PNAME)-$$vers.tar.gz


+  - default postscript canava set to landscape with size-ratio of 0.71

Typo? canava - canvas

+  - CONVFMT and OFMT varibles in 'awk' defined separately as %.17g

Typo: varibles - variables

+Remark: an user-defined function should have syntax conform to 'awk'.

Typos: an - a, conform - conforming

Changes to packaging are not documented in debian/changelog.

--
Jakub Wilk



The typos are fixed and the changes to packaging are record in 
debian/changelog. The new package with the same version number is uploaded 
to m.d.n:


dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-1.dsc


Thanks for reviewing,
Dimitar


--
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/alpine.deb.2.00.1407101701390.16...@freeshell.de

Re: Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Nicholas Breen]

On Wed, Jul 02, 2014 at 02:43:32PM +0200, Dimitar Ivanov wrote:
 I am looking for a sponsor for my package stda
 
  * Package name: stda
Version : 1.3.1-1
Upstream Author : Dimitar Ivanov dimitar.iva...@mirendom.net
  * URL : http://gnu.mirendom.net/stda.html
[snip]

There doesn't seem to be anything newer than 1.2.1 posted at that URL.


-- 
Nicholas Breen
nbr...@ofb.net


-- 
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/20140708210830.ga25...@ofb.net

Re: Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Dimitar Ivanov]

On Tue, 8 Jul 2014, Nicholas Breen wrote:


On Wed, Jul 02, 2014 at 02:43:32PM +0200, Dimitar Ivanov wrote:

I am looking for a sponsor for my package stda

 * Package name: stda
   Version : 1.3.1-1
   Upstream Author : Dimitar Ivanov dimitar.iva...@mirendom.net
 * URL : http://gnu.mirendom.net/stda.html

[snip]

There doesn't seem to be anything newer than 1.2.1 posted at that URL.


This is correct. The reason for this is that, since I'm the upstream 
author, first I'm trying to find a sponsor, or somebody who wants to 
review the package and could be a sponsor. Then I'll put the original tar 
on the URL. I just want this time that the upstream is released actually 
only if the package also will be put into Debian testing. If not, then 
I'll do not make a public release now, but in few months upgrade the 
package (bugs, new features, etc.) and try to find a sponsor again..


OK, should I put stda 1.3.1 at the URL?

Regards
Dimitar


--
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/alpine.deb.2.00.1407082328440.29...@freeshell.de

Bug#753813: RFS: ngspice_26-1, a new upstream release

[Gudjon I. Gudjonsson]

Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package ngspice:

 * Package name: ngspice
   Version : 26-1
   Upstream Author : Paolo Nenzi, Holger Vogt
 * URL : http://ngspice.sourceforge.net/
 * License : MIT_MODERN, GPL-v2, SPICEDOC,...
   Section : electronics

  It builds those binary packages:

ngspice - Spice circuit simulator
tclspice- NGspice library for Tcl
ngspice-doc - Documentation for the NGspice circuit simulator

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

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


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

  dget -x 
http://mentors.debian.net/debian/pool/non-free/n/ngspice/ngspice_26-1.dsc

  Changes since the last upload:

  * New upstream release (Closes: #706821)
  * Bump standards version to 3.9.5
  * Make VCS field canonical
  * Change tcl version to 8.6
  * Remove part of patch, wish8.4 changed back to wish for tclspice examples
  * Add pdf manual
  * Remove DM-upload line from control
  * Add patch 03_fix_compilation.patch
(Thanks to Robert Larice)
  * Remove stripping of codemodel files
  * Add -BLT and -ltcl8.6 to configure for tclspice.
Needed by libtclspice
  * Remove ps manual
  * Remove hardening wrapper and exchange for dpkg-buildflags
  * Add dependency on libfftw3-dev


Regards,
Gudjon I. Gudjonsson


-- 
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/2145318.jXK4ddUAHm@hekla

Bug#753487: RFS: stda/1.3.1-1 -- new upstream release (package already in Debian)

[Dimitar Ivanov]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package stda

 * Package name: stda
   Version : 1.3.1-1
   Upstream Author : Dimitar Ivanov dimitar.iva...@mirendom.net
 * URL : http://gnu.mirendom.net/stda.html
 * License : GPLv3+
   Section : math

  It builds those binary packages:

stda  - simple tools for data analysis (stda)

Following programs are included in stda:
* maphimbu   - histogram builder for 1-d numerical and text data
* mintegrate - evaluate average/sum/integral/derivative of 1-d numerical 
data
* mmval  - find minimum and maximum value in a data set
* muplot - plot a multi-curve figure from multiple data by using Gnuplot
* nnum   - produce a series of equally separated integers or floats
* prefield   - prepare input file for 'muplot' to plot 2-d fields by arrows


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

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


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

dget -x http://mentors.debian.net/debian/pool/main/s/stda/stda_1.3.1-1.dsc


Regards,
Dimitar


--
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/alpine.deb.2.00.1407021439001.6...@freeshell.de

Bug#750592: RFS: pyformex/0.9.1-3 -- new upstream release

[Benedict Verhegghe]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  I am looking for a sponsor for my package pyformex

 * Package name: pyformex
   Version : 0.9.1-3
   Upstream Author : benedict.verheg...@ugent.be
 * URL : pyformex.org
 * License : GPL3
   Section : science

  It builds those binary packages:

 pyformex   - program to create 3D geometry from Python scripts
 pyformex-extra - program to create 3D geometry from Python scripts (extras)
   pyformex-lib - program to create 3D geometry from Python scripts (libs)

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

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


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

dget -x
http://mentors.debian.net/debian/pool/main/p/pyformex/pyformex_0.9.1-3.dsc

  More information about pyformex can be obtained from http://pyformex.org

  Changes since the last upload:

New upstream release
Place architecture independent files under /usr/share
Fix bug #750351



  Regards,
   Benedict Verhegghe


-- 
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/538f7ce8.6040...@ugent.be

Re: RFS swiftmailer new upstream release

[Nicolas]

Hi IOhannes,


 On 2014-05-08 14:37, Nicolas wrote:
  so why did you change dh compat-level from 8 to 9 then?
 
 
  I don't know exactly. There's no change that affect my package and
  the others packages I work on used compat level 9

 that's a rather lame reason.
 if there is no change that affects your package, you should probably
 go for compat-level 8, to ease backporting.
 read: don't use overly tight (that is: more strict than needed)
 dependencies


You're perfectly right. My fault.



  Ok I understand. Do you think I should make a revert and add
  severals commits for that release or should I do it for next ones
  ?

 the latter.


Ok.



 thanks.
 looking at the mentors-page, it becomes quite obvious that by now
 there is a newer upstream version (5.2.0) available.
 you might want to package the newest version. (i'm aware that your
 initial request for sponsorship predates swift-5.1.0; but then was
 then and now is now :-))


Yes I saw. :-( And of course I want to package that new release but no
archive (zip or tar.gz) are provided. The upstream team intentionnaly do
that  We do not provide downloadable versions of Swiftmailer as of
Swiftmailer 5.2.0. They want developer to use composer instead.



 also: it's somewhat useless to mention tell lintian to not complain
 in your lintian-override
 also the override description might be a bit more to the point: what
 the script is used for, is not so interesting; what i find more
 interesting is why do you think it should stay non-executable? (the
 fact that upstream distributes it like this and that (afaict)  it is
 only used on an ad-hoc basis may be enough)

 Ok



 PS: i don't want to raise too many expectations; as i'm not into php
 (packaging), it's unlikely that *i* will sponsor your package; in any
 case, i hope that my comments will help bringing the package into a
 state that a potential sponsor will find more useful.


All your comments are usefull. Thanks. I will update my package with your
advice in mind.

Regards,
Nicolas

Re: RFS swiftmailer new upstream release

[IOhannes m zmoelnig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2014-05-08 14:37, Nicolas wrote:
 so why did you change dh compat-level from 8 to 9 then?
 
 
 I don't know exactly. There's no change that affect my package and
 the others packages I work on used compat level 9

that's a rather lame reason.
if there is no change that affects your package, you should probably
go for compat-level 8, to ease backporting.
read: don't use overly tight (that is: more strict than needed)
dependencies

 
 Ok I understand. Do you think I should make a revert and add
 severals commits for that release or should I do it for next ones
 ?

the latter.

 you might also upload your package to mentors.debian.net to ease 
 reviewing.
 
 
 Done.
 

thanks.
looking at the mentors-page, it becomes quite obvious that by now
there is a newer upstream version (5.2.0) available.
you might want to package the newest version. (i'm aware that your
initial request for sponsorship predates swift-5.1.0; but then was
then and now is now :-))

also: it's somewhat useless to mention tell lintian to not complain
in your lintian-override
also the override description might be a bit more to the point: what
the script is used for, is not so interesting; what i find more
interesting is why do you think it should stay non-executable? (the
fact that upstream distributes it like this and that (afaict)  it is
only used on an ad-hoc basis may be enough)


fgasdmr
IOhannes

PS: i don't want to raise too many expectations; as i'm not into php
(packaging), it's unlikely that *i* will sponsor your package; in any
case, i hope that my comments will help bringing the package into a
state that a potential sponsor will find more useful.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCAAGBQJTbn0BAAoJELZQGcR/ejb4CqIP/RR9NjjjP9O4sREFgr1QJgqj
4sLGc/V75USy6tRQZ5ASR2aVBZpuw6sGbRF6wmwnXVU1mJK56VxTDIRaqc96g+OD
ZxSjl09EdsQemcyVQznAgMYTTbdEA7lrSKA3PXHQ0CJ7VLej3Z/4Ev7sXapcZPTl
Q1ZvwO54q1Vxn8I3/OZQf/uxAQ0myTwTH27tmrfGNyBQ09w3x1Y6MAoSwsS2GV3d
vs2LtJqGbGb45C+crcLQHYkttv7wzS1IpHSRBnZ4iTFiBLFQWRl173g3i40ZDyyq
auI+OCvmxyXnmEoic8sUjPloaU9jyHMNMDRKTIbi6nH/jBX0eSDl8gWTe/OkhmZo
fEIzQ5ker45aTrzt7/5/6vvNtjBQ+PKtcW1CS7+BgNHWal0pNH19x06G+mrJYPH+
COATlOzJ+qQsDG54HcnQc15gWtybjgIOYFGCgLsFWs++JGkksU5Vv6D+1wze2cQS
rdBzYSx+ztHvWSQAGPVNC/Ozh4pEek3JMvlJFkaP6yxez/OsKKxh85peHIyfkxbP
nUoxo6hgH7U4F9HtsPq7wmTroxAy56yd3LOwX5f7TF8Favw0knocpsZThraj9US3
jPBnGpDYEoBimlTeL18eYKPIQTv6AKyyGsm78BuEmAeo6VchgjvyCAhD8vbldlvh
c9iCtP0kQto7ScUdabcy
=P7cV
-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/536e7d09.3010...@iem.at

Re: RFS swiftmailer new upstream release

[IOhannes m zmölnig (Debian/GNU)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2014-05-06 20:16, Nicolas wrote:
 Hi all,
 
 I'm looking for a sponsor for the package swiftmailer that is 
 already in debian. Upstream delivered a new release. There's no 
 major changes in debian packaging. I can build the package and 
 lintian did not complain

so why did you change dh compat-level from 8 to 9 then?

for reviewing i find it easier, if you would only submitted one change
per git-commit (e.g. do not bump standards version and
debhelper-compat level in a single commit; and don't put *all* changes
into a single sumbit)

 about errors.
 
 The package : SwiftMailer - licence : MIT - version : 5.1.0 - 
 project url : http://swiftmailer.org/ The package is maintain on 
 alioth : - Vcs-Git: git://anonscm.debian.org/collab-maint/swift.git
 - Vcs-Browser: 
 http://anonscm.debian.org/gitweb/?p=collab-maint/swift.git
 

you might also upload your package to mentors.debian.net to ease
reviewing.

fgmdsr
IOhannes

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCAAGBQJTa04cAAoJELZQGcR/ejb4zwcP/3BqvZCAj+J8jCK9/9c7ijrU
D8m7mQ3V10Jm78xtya3HyhoRFheovuwg+5tHaogjgaA0gqAst7Oa87KebHyWoldD
DmfMMnxxH66Y1p4FpEjgeN+Gz5X016io1n7nuQl04ro4EwCBRfvT24HK67M6dDjG
KaxeZYs8NZoWgymIpRPWuSWKEzezxLYzWwSXJMH1wUl2vTs3Y7uU95kwjHUsFsVX
hayNuF2KfsivlAxsx6fBKrKRC9wsgEF/NuCYRxpKLCND2kNcGyFHH1CZmLvFwiqY
C0HMIMoq+xNcsfXRAVJq2LKhGiWUUWZz0UoUHo9vWTHDvR18jfXMLKYoC/5bY5sR
Y5QbNOdvu1YwqpOi4xO772FGU74zG8fShMoz7HjCEepxbMBlcT0j3pfbZk7Ku7Vn
n8RTZDqD5BbJsSGvA9Yz7jS/V6+qxnlC18UcxSFGhg5E4wd03tsgEi+m1K+jGwPj
kr8uO6QMcd9iXjgnXu2MsN8V6tnZGZNuTfSNoVyhIGlDlai7iEy6GpMTsqBM396x
12eEvqKd/MD5QwYbpNpxAF1YKx/NFCMvaEfLY7FzbB8FwqqndlcS3qgm6lLnD2OO
okMruZkoR46Bax4qHHD4CHb7TIGQPLXc3+Cs2ETX7NPAwBMfcEB3vb10aZCJIKtW
nKiFfXcoPouIFdIzPkko
=qXtb
-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/536b4e20.80...@debian.org

Re: RFS swiftmailer new upstream release

[Nicolas]

  I'm looking for a sponsor for the package swiftmailer that is
  already in debian. Upstream delivered a new release. There's no
  major changes in debian packaging. I can build the package and
  lintian did not complain

 so why did you change dh compat-level from 8 to 9 then?


I don't know exactly. There's no change that affect my package and the
others packages I work on used compat level 9


 for reviewing i find it easier, if you would only submitted one change
 per git-commit (e.g. do not bump standards version and
 debhelper-compat level in a single commit; and don't put *all* changes
 into a single sumbit)


Ok I understand. Do you think I should make a revert and add severals
commits for that release or should I do it for next ones ?



  about errors.
 
  The package : SwiftMailer - licence : MIT - version : 5.1.0 -
  project url : http://swiftmailer.org/ The package is maintain on
  alioth : - Vcs-Git: git://anonscm.debian.org/collab-maint/swift.git
  - Vcs-Browser:
  http://anonscm.debian.org/gitweb/?p=collab-maint/swift.git
 

 you might also upload your package to mentors.debian.net to ease
 reviewing.


Done.

Thanks for your answer.

Regards,
Nicolas

RFS swiftmailer new upstream release

[Nicolas]

Hi all,

I'm looking for a sponsor for the package swiftmailer that is already in
debian. Upstream delivered a new release. There's no major changes in
debian packaging. I can build the package and lintian did not complain
about errors.

The package :
SwiftMailer
   - licence : MIT
   - version : 5.1.0
   - project url : http://swiftmailer.org/
   The package is maintain on alioth :
   - Vcs-Git: git://anonscm.debian.org/collab-maint/swift.git
   - Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/swift.git


Thanks for taking attention to my message,

Best regards,
Nicolas

Re: RFS: ranger/1.6.1-1 (new upstream release)

[Aron Xu]

On Fri, Mar 7, 2014 at 11:44 PM, Vern Sun s5u...@gmail.com wrote:
 Dear mentors,

 I am looking for a sponsor for ranger:

  * Package name: ranger
  * Version : 1.6.1-1
  * Upstream Author : Roman Zimbelmann h...@lavabit.com
  David Barnett davidbarne...@gmail.com
  Abdó Roig-Maranges abdo.r...@gmail.com
  * URL : http://ranger.nongnu.org/
  * License : GNU GPL version 3 or any later version
  * Section : utils

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

 dget -x 
 http://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.6.1-1.dsc

 Changes since the last upload:

 * Updated Standard-version to 3.9.5.
 * Upgrade compat magic number to 9.
 * Add upstream documents.

 Regards,
 --
 Vern
 vim -c :s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??

Uploaded, thanks for the work!

Regards,
Aron


--
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/CAMr=8w5pynkhdegbw0qde7hivglbizxwlhzk-vrkchyrcxz...@mail.gmail.com

RFS: ranger/1.6.1-1 (new upstream release)

[Vern Sun]

Dear mentors,

I am looking for a sponsor for ranger:

 * Package name: ranger
 * Version : 1.6.1-1
 * Upstream Author : Roman Zimbelmann h...@lavabit.com
 David Barnett davidbarne...@gmail.com
 Abdó Roig-Maranges abdo.r...@gmail.com
 * URL : http://ranger.nongnu.org/
 * License : GNU GPL version 3 or any later version
 * Section : utils

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

dget -x 
http://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.6.1-1.dsc

Changes since the last upload:

* Updated Standard-version to 3.9.5.
* Upgrade compat magic number to 9.
* Add upstream documents.

Regards,
-- 
Vern
vim -c :s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??


signature.asc
Description: Digital signature

Re: RFS: ranger/1.6.0-1 (new upstream release)

[Vern Sun]

Dear mentors,

I have a new version:
http://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.6.0-1.dsc

I am still looking for a sponsor.

on 2013-03-25(一) at 18:59(+0100), Jakub Wilk wrote:
 Does this meaning to use `/usr/share/foo` to instead of
 `/usr/share/pyshared/foo` look like below:
 
...
 
 No, that would be incorrect.
 
 The whole point of moving the modules to a private directory is to
 make them unavailable for import to other software. Adding symlinks
 pointing from dist-package to the private directory would defeat this
 purpose.
 
I guess I have fixed it. [^1]

 If TMPDIR is unset, you should fall back to /tmp.
 What about security? See last paragraphs of Policy §10.4.
 
fixed.

I am so thankful for your patient help and guidance many times.

[^1]: 
http://debian.2.n7.nabble.com/how-to-take-a-public-package-private-tt2047149.html#a2047155

Cheers,
-- 
Vern
vim -c :s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??


signature.asc
Description: Digital signature

RFS: xlog (new upstream release)

[Nanakos Chrysostomos]

Dear mentors,

I am looking for a sponsor for my package xlog

* Package name: xlog
  Version : 2.0.6-1
  Upstream Author : Andy Stewart
* URL : http://xlog.nongnu.org/
* License : GPL-3
  Section : hamradio

It builds those binary packages:

 xlog  - GTK+ Logging program for Hamradio Operators
 xlog-data  - data for xlog, a GTK+ Logging program for Hamradio Operators

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

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


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

 dget -x http://mentors.debian.net/debian/pool/main/x/xlog/xlog_2.0.6-1.dsc

More information about hello can be obtained from http://www.example.com.

Changes since the last upload:

  * Update debian/control
- Update to S-V 3.9.4
- added new package dependency: libjs-jquery
  * Update debian/rules
- added link to jquery library used by xlog manual
  * Added xlog-data.lintian-overrides concerning the manual
license and the two changelog files, xlog and xlog-data
  * New upstream release

Regards,
  Nanakos Chrysostomos


signature.asc
Description: Digital signature

RFS: xlog (new upstream release)

[Nanakos Chrysostomos]

Dear mentors,

I am looking for a sponsor for my package xlog

* Package name: xlog
  Version : 2.0.6-1
  Upstream Author : Andy Stewart
* URL : http://xlog.nongnu.org/
* License : GPL-3
  Section : hamradio

It builds those binary packages:

 xlog  - GTK+ Logging program for Hamradio Operators
 xlog-data  - data for xlog, a GTK+ Logging program for Hamradio Operators

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

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


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

 dget -x http://mentors.debian.net/debian/pool/main/x/xlog/xlog_2.0.6-1.dsc

More information about hello can be obtained from http://www.example.com.

Changes since the last upload:

  * Update debian/control
- Update to S-V 3.9.4
- added new package dependency: libjs-jquery
  * Update debian/rules
- added link to jquery library used by xlog manual
  * Added xlog-data.lintian-overrides concerning the manual
license and the two changelog files, xlog and xlog-data
* New upstream release

Regards,
  Nanakos Chrysostomos


signature.asc
Description: Digital signature

Re: RFS: ranger/1.6.0-1 (new upstream release)

[Jakub Wilk]

* Vern Sun s5u...@gmail.com, 2013-03-25, 00:35:

4. python modules, private / public

Are Python modules included by this package supposed to by used by 
other software?

I don't think so.


Otherwise, they should be moved to a private directory.
Does this meaning to use `/usr/share/foo` to instead of 
`/usr/share/pyshared/foo` look like below:


 - /usr/share/pyshared/foo:

   ./usr/share/pyshared/ranger/api/commands.py
   ...
   ./usr/lib/python2.6/dist-packages/ranger/api/commands.py - 
../../../../../share/pyshared/ranger/api/commands.py
   ...
   ./usr/lib/python2.7/dist-packages/ranger/api/commands.py - 
../../../../../share/pyshared/ranger/api/commands.py
   ...

 - /usr/share/foo:

   ./usr/share/ranger/api/commands.py
   ...
   ./usr/lib/python2.6/dist-packages/ranger/api/commands.py - 
../../../../../share/ranger/api/commands.py
   ...
   ./usr/lib/python2.7/dist-packages/ranger/api/commands.py - 
../../../../../share/ranger/api/commands.py
   ...


No, that would be incorrect.

The whole point of moving the modules to a private directory is to make 
them unavailable for import to other software. Adding symlinks pointing 
from dist-package to the private directory would defeat this purpose.



10. upstream /tmp = $TMPDIR [^2]

   fixed


If TMPDIR is unset, you should fall back to /tmp.
What about security? See last paragraphs of Policy §10.4.

--
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/20130325175925.ga7...@jwilk.net

RFS: libcommons-codec-java/1.7-1 (new upstream release)

[Emmanuel Bourg]

Hi,

I am looking for a sponsor for the package libcommons-codec-java

 * Package name: libcommons-codec-java
   Version : 1.7-1
   Section : java

  It builds those binary packages:

libcommons-codec-java - encoder and decoders such as Base64 and
hexadecimal codec
 libcommons-codec-java-doc - encoder and decoders such as Base64 and
hexadecimal codec - docum

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

  http://mentors.debian.net/package/libcommons-codec-java


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

dget -x
http://mentors.debian.net/debian/pool/main/libc/libcommons-codec-java/libcommons-codec-java_1.7-1.dsc

  Changes since the last upload:

  * New upstream release.
  * Remove the deprecated DMUA flag
  * d/control: Bump Standards-Version to 3.9.4 (no changes needed).


Regards,

Emmanuel Bourg



smime.p7s
Description: Signature cryptographique S/MIME

Re: RFS: ranger/1.6.0-1 (new upstream release)

[Vern Sun]

on 2013-03-23(六) at 12:45(+0100), Jakub Wilk wrote:
 (I don't intend to sponsor this package, sorry.)
 
I really appreciate your patience and your support.
Thank you very much!

I have a new version:
http://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.6.0-1.dsc

I am still looking for a sponsor.
Sorry for my poor english.

1. changelog
  - 1.5.3 fixed
  - 1.5.4 added

2. lintian, configuration files /usr = /etc

put the files in /etc/ranger and create symbolic links to those files [^1]

- rc.conf
- rifle.conf
- scope.sh
- mime.types

3. lintian4python

lintian4python emits (among others):
i: ranger source: python-provides-considered-harmful ranger
e: ranger: pyflakes-undefined-name 
usr/share/pyshared/ranger/core/loader.py:152: errno
e: ranger: pyflakes-undefined-name 
usr/share/pyshared/ranger/core/loader.py:152: errno

`e:' fxied.

N: Using profile debian/python.
N: Setting up lab in /tmp/temp-lintian-lab-nd73kmb6bq ...
N: Unpacking packages in group ranger/1.6.0-1
N: 
N: Processing changes file ranger (version 1.6.0-1, arch source all) ...
N: 
N: Processing source package ranger (version 1.6.0-1, arch source) ...
i: ranger source: python-provides-considered-harmful ranger
N: 
N: Processing binary package ranger (version 1.6.0-1, arch all) ...
x: ranger: pyflakes-import-star-used 
usr/share/pyshared/ranger/api/commands.py:10: ranger.api
x: ranger: pyflakes-import-star-used 
usr/share/pyshared/ranger/api/options.py:7: ranger.api
x: ranger: pyflakes-import-star-used 
usr/share/pyshared/ranger/colorschemes/default.py:5: ranger.gui.color
x: ranger: pyflakes-import-star-used 
usr/share/pyshared/ranger/colorschemes/jungle.py:4: ranger.gui.color
x: ranger: pyflakes-import-star-used 
usr/share/pyshared/ranger/colorschemes/snow.py:5: ranger.gui.color
x: ranger: pyflakes-import-star-used 
usr/share/pyshared/ranger/config/commands.py:79: ranger.api.commands
w: ranger: pyflakes-redefined-in-list-comp 
usr/share/pyshared/ranger/core/actions.py:332: f line 317

4. python modules, private / public

   Are Python modules included by this package supposed to by used
   by other software?
   
  I don't think so. 
  
   Otherwise, they should be moved to a private directory.
   
  Does this meaning to use `/usr/share/foo` to instead of
  `/usr/share/pyshared/foo` look like below:

  - /usr/share/pyshared/foo:

./usr/share/pyshared/ranger/api/commands.py
...
./usr/lib/python2.6/dist-packages/ranger/api/commands.py - 
../../../../../share/pyshared/ranger/api/commands.py
...
./usr/lib/python2.7/dist-packages/ranger/api/commands.py - 
../../../../../share/pyshared/ranger/api/commands.py
...

  - /usr/share/foo:

./usr/share/ranger/api/commands.py
...
./usr/lib/python2.6/dist-packages/ranger/api/commands.py - 
../../../../../share/ranger/api/commands.py
...
./usr/lib/python2.7/dist-packages/ranger/api/commands.py - 
../../../../../share/ranger/api/commands.py
...

5. debian/copyright

s/2009-2011/2009-2013/

6. suggest elinks-list = w3m | lynx | elinks| elinks-lite

fixed

7. upstream sys.version = sys.version_info

affirmative

8. upstream less = sensible-paper

fixed

9. upstream nano = sensible-editor

fixed

10. upstream /tmp = $TMPDIR [^2]

fixed

[^1]: 
http://docs.python.org/2/distutils/setupscript.html#installing-additional-files
[^2]: 
http://stackoverflow.com/questions/847850/cross-platform-way-of-getting-temp-directory-in-python

Cheers,
-- 
Vern
vim -c :s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??


signature.asc
Description: Digital signature

RFS: ranger/1.6.0-1 (new upstream release)

[Vern Sun]

Dear mentors,

I am looking for a sponsor for the package ranger

 * Package name: ranger
 * Version : 1.6.0-1
 * Upstream Author : Roman Zimbelmann h...@lavabit.com
 David Barnett davidbarne...@gmail.com
 * URL : http://ranger.nongnu.org/
 * License : GNU GPL version 3 or any later version
 * Section : utils

It builds those binary packages:

ranger - File manager with an ncurses frontend written in Python

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

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

Cheers,
-- 
Vern
vim -c :s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??


signature.asc
Description: Digital signature

Re: RFS: ranger/1.6.0-1 (new upstream release)

[Jakub Wilk]

(I don't intend to sponsor this package, sorry.)

* Vern Sun s5u...@gmail.com, 2013-03-23, 15:01:

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


A direct link to .dsc would have been helpful:
http://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.6.0-1.dsc

What happened to changelog entry for 1.5.4-1? Also, this change to 
1.5.3-1 entry looks unnecessary:

-  * New upstream release.
+  * New upstream release

Lintian emits:
I: ranger: unused-override script-not-executable 
usr/share/pyshared/ranger/data/ranger

There's also another override:

N: This script is considered a configuration file, so tell lintian to not
N: complain:
O: ranger: script-not-executable usr/share/pyshared/ranger/data/scope.sh

Wait... Configuration files must not reside in /usr. This is a serious 
violation of Policy §10.7.2.


The manpage says that configuration files are usually installed to 
/usr/lib/python*/dist-packages/ranger/config. Usually installed by 
who/what? I first thought that this file was included in the Debian 
package, but it's not... And then again, configuration files belong in 
/etc, not /usr.


lintian4python emits (among others):
i: ranger source: python-provides-considered-harmful ranger
e: ranger: pyflakes-undefined-name 
usr/share/pyshared/ranger/core/loader.py:152: errno
e: ranger: pyflakes-undefined-name 
usr/share/pyshared/ranger/core/loader.py:152: errno

(Although in this case it's rather s/harmful/useless/, because nothing 
will generate this substitution variable.)


Are Python modules included by this package supposed to by used by other 
software? If yes, then the package name should be python-ranger. 
Otherwise, they should be moved to a private directory.


Copyright years in debian/copyright don't look up to date. This change 
looks wrong:

-Copyright (c) 2009-2012, Roman Zimbelmann rom...@lavabit.com
+Copyright (c) 2009-2011, Roman Zimbelmann rom...@lavabit.com

Upstream uses sys.version (which is a string) for version comparison. 
Please recommend them using sys.version_info (a tuple) instead.


Shouldn't elinks-lite is Suggests be elinks | elinks-lite? Or maybe 
even w3m | lynx | elinks | elinks-lite.


DEFAULT_PAGER is set to less. It would be better to set it to pager, 
which is always available.


DEFAULT_EDITOR is set to nano. It would be better to set it to 
sensible-editor.


ranger doesn't honour TMPDIR; also, as far as I can see, it creates 
temporary files insecurely:


$ grep -r /tmp .
./ranger/__init__.py:LOGFILE = '/tmp/ranger_errorlog'
./ranger/core/actions.py:# self.previews['/tmp/foo.jpg'][(80, 24)] = 
the content...
./ranger/core/actions.py:# self.previews['/tmp/foo.jpg']['loading'] 
= False
./ranger/core/main.py:cProfile.run('ranger.__fm.loop()', 
'/tmp/ranger_profile')
./ranger/core/main.py:profile = pstats.Stats('/tmp/ranger_profile', 
stream=sys.stderr)
./ranger.py:tempfile='/tmp/chosendir'
./examples/bash_automatic_cd.sh:tempfile='/tmp/chosendir'
./examples/vim_file_chooser.vim:exec silent !ranger --choosefile=/tmp/chosenfile  . 
expand(%:p:h)
./examples/vim_file_chooser.vim:if filereadable('/tmp/chosenfile')
./examples/vim_file_chooser.vim:exec 'edit ' . system('cat 
/tmp/chosenfile')
./examples/vim_file_chooser.vim:call system('rm /tmp/chosenfile')

--
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/20130323114507.ga4...@jwilk.net

RFS: ranger/1.5.5-1 (new upstream release)

[Vern Sun]

Dear mentors,

I am looking for a sponsor for my package ranger

* Package name: ranger
  Version : 1.5.5-1
  Upstream Author : Roman Zimbelmann rom...@lavabit.com
David Barnett davidbarne...@gmail.com
  URL : http://ranger.nongnu.org/
  License : GNU GPL version 3 or any later version
  Section : utils

It builds those binary packages:

  ranger - File manager with an ncurses frontend written in Python

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

  dget -x http://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.5.5-1.dsc

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

Cheers,
-- 
Vern
vim -c :s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??


signature.asc
Description: Digital signature

Bug#676936: marked as done (RFS: presage/0.8.8-1 (updated package, new upstream release))

[Debian Bug Tracking System]

Your message dated Wed, 13 Jun 2012 04:14:17 +
with message-id e1seeyh-0007l7...@ravel.debian.org
and subject line closing RFS: presage/0.8.8-1 (updated package, new upstream 
release)
has caused the Debian Bug report #676936,
regarding RFS: presage/0.8.8-1 (updated package, new upstream release)
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.)


-- 
676936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676936
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 an update of my package presage.

This update packages a new upstream release, enables build
hardening and closes a wishlist bug (detect dbus-python via
Python).

  Package name: presage
  Version : 0.8.8-1
  Upstream Author : Matteo Vescovi matteo.vesc...@yahoo.co.uk
  URL : http://presage.sourceforge.net/
  License : GPL-2+
  Section : devel

It builds those binary packages:

  gprompter  - intelligent predictive GTK+ text editor
  gprompter-dbg - intelligent predictive GTK+ text editor (debugging 
symbols)

  libpresage-data - intelligent predictive text entry platform (data files)
  libpresage-dev - intelligent predictive text entry platform 
(development files)
  libpresage-doc - intelligent predictive text entry platform 
(documentation)

  libpresage1 - intelligent predictive text entry platform (shared library)
  libpresage1-dbg - intelligent predictive text entry platform (shared 
library debugg

  presage- intelligent predictive text entry platform (tools and demos)
  presage-dbg - intelligent predictive text entry platform (tools 
debugging symbo

  presage-dbus - intelligent predictive text entry platform (dbus service)
  pyprompter - intelligent predictive wxPython text editor
  python-presage - intelligent predictive text entry platform (Python 
binding)
  python-presage-dbg - intelligent predictive text entry platform 
(Python binding debugg


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


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


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

  dget -x 
http://mentors.debian.net/debian/pool/main/p/presage/presage_0.8.8-1.dsc


More information about hello can be obtained from http://www.example.com.

Changes since the last upload:

   * New upstream release.
   * Enable build hardening.
   * Detect dbus-python via Python. Closes: #673860


Regards,
 Matteo Vescovi


---End Message---
---BeginMessage---
Package presage version 0.8.8-1 is in unstable now.
http://packages.qa.debian.org/presage

---End Message---

Bug#676936: RFS: presage/0.8.8-1 (updated package, new upstream release)

[Matteo Vescovi]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for an update of my package presage.

This update packages a new upstream release, enables build
hardening and closes a wishlist bug (detect dbus-python via
Python).

  Package name: presage
  Version : 0.8.8-1
  Upstream Author : Matteo Vescovi matteo.vesc...@yahoo.co.uk
  URL : http://presage.sourceforge.net/
  License : GPL-2+
  Section : devel

It builds those binary packages:

  gprompter  - intelligent predictive GTK+ text editor
  gprompter-dbg - intelligent predictive GTK+ text editor (debugging 
symbols)

  libpresage-data - intelligent predictive text entry platform (data files)
  libpresage-dev - intelligent predictive text entry platform 
(development files)
  libpresage-doc - intelligent predictive text entry platform 
(documentation)

  libpresage1 - intelligent predictive text entry platform (shared library)
  libpresage1-dbg - intelligent predictive text entry platform (shared 
library debugg

  presage- intelligent predictive text entry platform (tools and demos)
  presage-dbg - intelligent predictive text entry platform (tools 
debugging symbo

  presage-dbus - intelligent predictive text entry platform (dbus service)
  pyprompter - intelligent predictive wxPython text editor
  python-presage - intelligent predictive text entry platform (Python 
binding)
  python-presage-dbg - intelligent predictive text entry platform 
(Python binding debugg


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


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


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

  dget -x 
http://mentors.debian.net/debian/pool/main/p/presage/presage_0.8.8-1.dsc


More information about hello can be obtained from http://www.example.com.

Changes since the last upload:

   * New upstream release.
   * Enable build hardening.
   * Detect dbus-python via Python. Closes: #673860


Regards,
 Matteo Vescovi



--
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/4fd4c7fc.5080...@yahoo.co.uk

Bug#671184: marked as done (RFS: usbmuxd/1.0.8-1 (new upstream release))

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2012 05:25:40 +
with message-id 20120525052540.ga30...@master.debian.org
and subject line RFS: usbmuxd/1.0.8-1 (new upstream release)
has caused the Debian Bug report #671184,
regarding RFS: usbmuxd/1.0.8-1 (new upstream release)
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.)


-- 
671184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671184
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 usbmuxd

 * Package name: usbmuxd
   Version : 1.0.8-1
 * URL : http://www.libimobiledevice.org/
 * License : LGPL 2.1  GPL 2
   Section : utils

  It builds those binary packages:

libusbmuxd-dev - USB multiplexor daemon for iPhone and iPod Touch devices - 
devel
 libusbmuxd2 - USB multiplexor daemon for iPhone and iPod Touch devices - librar
 libusbmuxd2-dbg - USB multiplexor daemon for iPhone and iPod Touch devices - 
debug
 usbmuxd- USB multiplexor daemon for iPhone and iPod Touch devices

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

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


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

dget -x 
http://mentors.debian.net/debian/pool/main/u/usbmuxd/usbmuxd_1.0.8-1.dsc

  More information about hello can be obtained from http://www.example.com.

  Changes since the last upload:

usbmuxd (1.0.8-1) experimental; urgency=low

  * New upstream release.
  * debian/patches:
   - 90-cve-2012-0065.patch: Remove, merged upstream.
   - 02-udev-usbmux-owner.patch: Refreshed.
   - 03-revert-ifdef-USBMUXD_DAEMON.patch: Refreshed.
  * debian/compat
   - Update to 9.
  * debian/control:
   - Update to match new SONAME.
   - Update Standards-Version to 3.9.3 (no change needed).
   - Build-depend on debhelper (= 9).
  * debian/rules:
   - Update to match new SONAME.
   - Use DEB_*_MAINT_APPEND.
  * debian/libusbmuxd*.install  debian/libusbmuxd*.symbols
   - Update to match new SONAME.
  * debian/libusbmuxd2.symbols:
   - Update with new symbols.
  * debian/watch:
   - Update location of the tarballs.
  * debian/copyright:
   - Update with new license on common/*.

  Regards,
   Julien Lavergne

-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-22-generic (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


---End Message---
---BeginMessage---
Uploaded.  Is in NEW now:
http://ftp-master.debian.org/new.html

---End Message---

RFS: ranger/1.5.4-1 (new upstream release)

[Vern Sun]

Dear mentors,

I am looking for a sponsor for my package ranger

* Package name: ranger
  Version : 1.5.4-1
  Upstream Author : Roman Zimbelmann rom...@lavabit.com
David Barnett davidbarne...@gmail.com
  URL : http://ranger.nongnu.org/
  License : GNU GPL version 3 or any later version
  Section : utils

It builds those binary packages:

  ranger - File manager with an ncurses frontend written in Python

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

  dget -x http://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.5.4-1.dsc

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

Cheers,
-- 
Vern
vim -c :s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??


signature.asc
Description: Digital signature

Bug#671184: RFS: usbmuxd/1.0.8-1 (new upstream release)

[Julien Lavergne]

Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package usbmuxd

 * Package name: usbmuxd
   Version : 1.0.8-1
 * URL : http://www.libimobiledevice.org/
 * License : LGPL 2.1  GPL 2
   Section : utils

  It builds those binary packages:

libusbmuxd-dev - USB multiplexor daemon for iPhone and iPod Touch devices - 
devel
 libusbmuxd2 - USB multiplexor daemon for iPhone and iPod Touch devices - librar
 libusbmuxd2-dbg - USB multiplexor daemon for iPhone and iPod Touch devices - 
debug
 usbmuxd- USB multiplexor daemon for iPhone and iPod Touch devices

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

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


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

dget -x 
http://mentors.debian.net/debian/pool/main/u/usbmuxd/usbmuxd_1.0.8-1.dsc

  More information about hello can be obtained from http://www.example.com.

  Changes since the last upload:

usbmuxd (1.0.8-1) experimental; urgency=low

  * New upstream release.
  * debian/patches:
   - 90-cve-2012-0065.patch: Remove, merged upstream.
   - 02-udev-usbmux-owner.patch: Refreshed.
   - 03-revert-ifdef-USBMUXD_DAEMON.patch: Refreshed.
  * debian/compat
   - Update to 9.
  * debian/control:
   - Update to match new SONAME.
   - Update Standards-Version to 3.9.3 (no change needed).
   - Build-depend on debhelper (= 9).
  * debian/rules:
   - Update to match new SONAME.
   - Use DEB_*_MAINT_APPEND.
  * debian/libusbmuxd*.install  debian/libusbmuxd*.symbols
   - Update to match new SONAME.
  * debian/libusbmuxd2.symbols:
   - Update with new symbols.
  * debian/watch:
   - Update location of the tarballs.
  * debian/copyright:
   - Update with new license on common/*.

  Regards,
   Julien Lavergne

-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-22-generic (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
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/20120502114543.26776.98199.reportbug@saviour

Re: RFS: ranger_1.5.3-1 (new upstream release)

[Vern Sun]

 Dear mentors,
 
 I am looking for a sponsor for the package ranger.
 

Cheers,
-- 
Vern
vim -c :s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??


signature.asc
Description: Digital signature

RFS: ranger_1.5.3-1 (new upstream release)

[Vern Sun]

Dear mentors,

I am looking for a sponsor for my package ranger.

  Package name: ranger
  Version : 1.5.3-1
  Upstream Author : Roman Zimbelmann rom...@lavabit.com
David Barnett davidbarne...@gmail.com
  URL : http://ranger.nongnu.org/
  License : GNU GPL version 3 or any later version
  Section : utils

It builds those binary packages:

  ranger - File manager with an ncurses frontend written in Python

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

  dget -x http://mentors.debian.net/debian/pool/main/r/ranger/ranger_1.5.3-1.dsc

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

Cheers,
-- 
Vern
vim -c :s(^(ZnQr8va1puvan.(|:s)\d\(\S\)) \U\1)g|:1 normal g??


signature.asc
Description: Digital signature

who-uploads (was: Bug#661498: marked as done (RFS: burp/1.3.1-1 -- Simple cross-platform network BackUp and Restore Program (new upstream release)))

[Florian Ernst]

Hello there,

some general info, we are on -mentors after all :-)

On Tue, Mar 06, 2012 at 02:33:06AM +, Debian Bug Tracking System wrote:
 [...]
 This bug appears to be done.
 
 Not sure who uploaded it, but the pts shows an upload.
 
 http://packages.qa.debian.org/b/burp/news/20120303T164731Z.html

:) fernst@fernst:~$ who-uploads burp
   
Uploads for burp:
1.3.1-1 to unstable: Bartosz Fenski fe...@debian.org
1.3.0+20120214git-1 to unstable: Bartosz Fenski fe...@debian.org
1.3.0-3 to unstable: Bartosz Fenski fe...@debian.org
:) fernst@fernst:~$ dpkg -S $(which who-uploads)
devscripts: /usr/bin/who-uploads

Alternatively, the maintainer's packages overview at
http://qa.debian.org/developer.php?login=b...@dikkenberg.net
provides a mouseover text for the version string.

Cheers,
Flo


-- 
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/20120306094014.ga7...@fernst.no-ip.org

Bug#661498: marked as done (RFS: burp/1.3.1-1 -- Simple cross-platform network BackUp and Restore Program (new upstream release))

[Debian Bug Tracking System]

Your message dated Mon, 5 Mar 2012 21:29:24 -0500
with message-id 
cao6p2qsaxgfbdcbf+gmqyjr01zwmlxflebhfxnwljt3oxo3...@mail.gmail.com
and subject line this appears to be done
has caused the Debian Bug report #661498,
regarding RFS: burp/1.3.1-1 -- Simple cross-platform network BackUp and Restore 
Program (new upstream release)
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.)


-- 
661498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661498
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 burp

 * Package name: burp
Version : 1.3.1-1
Upstream Author : Graham Keeling keel...@spamcop.net
 * URL : http://burp.grke.net/
 * License : AGPLv3
Section : utils

  It builds those binary packages:

burp  - Simple cross-platform network BackUp and Restore Program
   burp-dbg   - debugging symbols for Burp

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

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


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

dget -x http://mentors.debian.net/debian/pool/main/b/burp/burp_1.3.1-1.dsc

  More information about hello can be obtained from http://www.example.com.

  Changes since the last upload:

  * New upstream release version 1.3.1
  * Switched to Standards-Version 3.9.3 Debian bug: (Closes: #661001)
  * respect noopt in DEB_BUILD_OPTIONS. Debian bug: (Closes: #661281)
  * Fixed typo in logrotate script Debian bug: (Closes: #660964)
  * added debug package Debian bug: (Closes: #661267)
  * EFS support on Windows.
  * Move to using mingw-w64 for both 32bit and 64bit Windows builds.
  * Add 'exclude_fs =' option for Linux so that you can skip partitions
types (for example, tmpfs) without generating warnings.
  * If recovery method 'resume' is set, but the includes/excludes change,
switch to 'use', then start a new backup.
  * In the tests, check to see whether it looks like the server has finished
the backup before moving on, rather than just waiting a set amount of time.
  * Add man pages for bedup and burp_ca.
  * Add Bas van den Dikkenberg's tweaks for getting burp into official Debian
and Ubuntu repositories. Burp is now in debian sid and ubuntu precise.
  * Make the server tell the client what extra_comms features it supports, so
that, in future, old servers are more likely to work with new clients.
  * Improve 'make clean'.
  * Add option to strip off leading path components on restore.
  * Fix segfault that was happening on the server when SSL_accept() failed.
  * Move burp and bedup to /usr/sbin (you need to check that any cron jobs
are pointing there too).
  * Moved list of things to do to https://github.com/grke/burp/issues

  Regards,
   Bas van den Dikkenberg


---End Message---
---BeginMessage---
This bug appears to be done.

Not sure who uploaded it, but the pts shows an upload.

http://packages.qa.debian.org/b/burp/news/20120303T164731Z.html

Thanks,
Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq

---End Message---

Bug#661498: RFS: burp/1.3.1-1 -- Simple cross-platform network BackUp and Restore Program (new upstream release)

[Bas van den Dikkenberg]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package burp

 * Package name: burp
Version : 1.3.1-1
Upstream Author : Graham Keeling keel...@spamcop.net
 * URL : http://burp.grke.net/
 * License : AGPLv3
Section : utils

  It builds those binary packages:

burp  - Simple cross-platform network BackUp and Restore Program
   burp-dbg   - debugging symbols for Burp

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

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


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

dget -x http://mentors.debian.net/debian/pool/main/b/burp/burp_1.3.1-1.dsc

  More information about hello can be obtained from http://www.example.com.

  Changes since the last upload:

  * New upstream release version 1.3.1
  * Switched to Standards-Version 3.9.3 Debian bug: (Closes: #661001)
  * respect noopt in DEB_BUILD_OPTIONS. Debian bug: (Closes: #661281)
  * Fixed typo in logrotate script Debian bug: (Closes: #660964)
  * added debug package Debian bug: (Closes: #661267)
  * EFS support on Windows.
  * Move to using mingw-w64 for both 32bit and 64bit Windows builds.
  * Add 'exclude_fs =' option for Linux so that you can skip partitions
types (for example, tmpfs) without generating warnings.
  * If recovery method 'resume' is set, but the includes/excludes change,
switch to 'use', then start a new backup.
  * In the tests, check to see whether it looks like the server has finished
the backup before moving on, rather than just waiting a set amount of time.
  * Add man pages for bedup and burp_ca.
  * Add Bas van den Dikkenberg's tweaks for getting burp into official Debian
and Ubuntu repositories. Burp is now in debian sid and ubuntu precise.
  * Make the server tell the client what extra_comms features it supports, so
that, in future, old servers are more likely to work with new clients.
  * Improve 'make clean'.
  * Add option to strip off leading path components on restore.
  * Fix segfault that was happening on the server when SSL_accept() failed.
  * Move burp and bedup to /usr/sbin (you need to check that any cron jobs
are pointing there too).
  * Moved list of things to do to https://github.com/grke/burp/issues

  Regards,
   Bas van den Dikkenberg



-- 
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/269dc496-727d-4793-8636-3bcbcb87ab14@srv01.dikkenberg.local

Re: RFS: bibtool/2.54 (new upstream release) -- tool for BibTeX database manipulation

[lina]

On Sat, Feb 25, 2012 at 3:42 PM, Jerome BENOIT g62993...@rezozer.net wrote:
 Hi !

 I have just uploaded a revisited version:
 0] the typo were fixed;
 1] now the texdoc can find bibtool.pdf

There is a problem with bibtool (I installed by aptitude install
bibtool just now)

For the  journal= jbioch,

It transformed the Upper case into small case.

supposed to be journal = JBIOCH


 Thanks,
 Jerome


 On 25/02/12 05:45, Norbert Preining wrote:

 On Sa, 25 Feb 2012, Jerome BENOIT wrote:

 may I send you an email when the new version will be uploaded ?


 Sure.

 Best wishes

 Norbert
 
 Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
 JAIST, Japan                                 TeX Live  Debian Developer

 DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
 
 AHENNY (adj.)
 The way people stand when examining other people's bookshelves.
                        --- Douglas Adams, The Meaning of Liff



 --
 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/4f4890fa.8080...@rezozer.net



--
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/CAG9cJmmQvSt_WaE9iQkfOPvwbv87NEPTTd6SH+979=puhd7...@mail.gmail.com

Re: RFS: bibtool/2.54 (new upstream release) -- tool for BibTeX database manipulation

[lina]

On Sat, Feb 25, 2012 at 8:32 PM, lina lina.lastn...@gmail.com wrote:
 On Sat, Feb 25, 2012 at 3:42 PM, Jerome BENOIT g62993...@rezozer.net wrote:
 Hi !

 I have just uploaded a revisited version:
 0] the typo were fixed;
 1] now the texdoc can find bibtool.pdf

 There is a problem with bibtool (I installed by aptitude install
 bibtool just now)

 For the  journal        = jbioch,

 It transformed the Upper case into small case.

 supposed to be journal = JBIOCH

tried building from this one.
  dget -x 
http://mentors.debian.net/debian/pool/main/b/bibtool/bibtool_2.54+ds-1.dsc

It still handled it the same.






 Thanks,
 Jerome


 On 25/02/12 05:45, Norbert Preining wrote:

 On Sa, 25 Feb 2012, Jerome BENOIT wrote:

 may I send you an email when the new version will be uploaded ?


 Sure.

 Best wishes

 Norbert
 
 Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
 JAIST, Japan                                 TeX Live  Debian Developer

 DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
 
 AHENNY (adj.)
 The way people stand when examining other people's bookshelves.
                        --- Douglas Adams, The Meaning of Liff



 --
 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/4f4890fa.8080...@rezozer.net



--
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/CAG9cJmkg4KJ9MrpHoEaCcXZOW7dK9tZxfPz25=_-Xx=3j3x...@mail.gmail.com

Re: RFS: bibtool/2.54 (new upstream release) -- tool for BibTeX database manipulation

[Benoît Knecht]

Hi lina,

lina wrote:
 On Sat, Feb 25, 2012 at 8:32 PM, lina lina.lastn...@gmail.com wrote:
  There is a problem with bibtool (I installed by aptitude install
  bibtool just now)
 
  For the  journal        = jbioch,
 
  It transformed the Upper case into small case.
 
  supposed to be journal = JBIOCH
 
 tried building from this one.
   dget -x 
 http://mentors.debian.net/debian/pool/main/b/bibtool/bibtool_2.54+ds-1.dsc
 
 It still handled it the same.

But BibTeX is case insensitive when it comes to string names, and this
behavior is documented in the bibtool manual (section A.5, page 27); it
can be customized too.

-- 
Benoît Knecht


-- 
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/20120225130424.gc1...@marvin.lan

Re: RFS: bibtool/2.54 (new upstream release) -- tool for BibTeX database manipulation

[lina]

On Sat, Feb 25, 2012 at 9:04 PM, Benoît Knecht benoit.kne...@fsfe.org wrote:
 Hi lina,

 lina wrote:
 On Sat, Feb 25, 2012 at 8:32 PM, lina lina.lastn...@gmail.com wrote:
  There is a problem with bibtool (I installed by aptitude install
  bibtool just now)
 
  For the  journal        = jbioch,
  
  It transformed the Upper case into small case.
 
  supposed to be journal = JBIOCH

 tried building from this one.
   dget -x 
 http://mentors.debian.net/debian/pool/main/b/bibtool/bibtool_2.54+ds-1.dsc

 It still handled it the same.

 But BibTeX is case insensitive when it comes to string names, and this
 behavior is documented in the bibtool manual (section A.5, page 27); it
 can be customized too.

Thanks, I thought the bibtool was used to beautify (format) the
manually build .bib entries.
seems it has lots of functions I don't know.

Best regards,


 --
 Benoît Knecht


 --
 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/20120225130424.gc1...@marvin.lan



--
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/CAG9cJmnzpqS+STvqH13p9nbWNSvZOQ=4q0db9psfxqcyv59...@mail.gmail.com

Re: RFS: bibtool/2.54 (new upstream release) -- tool for BibTeX database manipulation

[Benoît Knecht]

lina wrote:
 On Sat, Feb 25, 2012 at 9:04 PM, Benoît Knecht benoit.kne...@fsfe.org wrote:
  lina wrote:
  On Sat, Feb 25, 2012 at 8:32 PM, lina lina.lastn...@gmail.com wrote:
   There is a problem with bibtool (I installed by aptitude install
   bibtool just now)
  
   For the  journal        = jbioch,
   
   It transformed the Upper case into small case.
  
   supposed to be journal = JBIOCH
 
  tried building from this one.
    dget -x 
  http://mentors.debian.net/debian/pool/main/b/bibtool/bibtool_2.54+ds-1.dsc
 
  It still handled it the same.
 
  But BibTeX is case insensitive when it comes to string names, and this
  behavior is documented in the bibtool manual (section A.5, page 27); it
  can be customized too.
 
 Thanks, I thought the bibtool was used to beautify (format) the
 manually build .bib entries.
 seems it has lots of functions I don't know.

Maybe you're looking for bibclean instead:

http://packages.debian.org/squeeze/bibclean

Cheers,

-- 
Benoît Knecht


-- 
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/20120225135907.gd1...@marvin.lan

Re: RFS: bibtool/2.54 (new upstream release) -- tool for BibTeX database manipulation

[lina]

On Sat, Feb 25, 2012 at 9:59 PM, Benoît Knecht benoit.kne...@fsfe.org wrote:
 lina wrote:
 On Sat, Feb 25, 2012 at 9:04 PM, Benoît Knecht benoit.kne...@fsfe.org 
 wrote:
  lina wrote:
  On Sat, Feb 25, 2012 at 8:32 PM, lina lina.lastn...@gmail.com wrote:
   There is a problem with bibtool (I installed by aptitude install
   bibtool just now)
  
   For the  journal        = jbioch,
   
   It transformed the Upper case into small case.
  
   supposed to be journal = JBIOCH
 
  tried building from this one.
    dget -x 
  http://mentors.debian.net/debian/pool/main/b/bibtool/bibtool_2.54+ds-1.dsc
 
  It still handled it the same.
 
  But BibTeX is case insensitive when it comes to string names, and this
  behavior is documented in the bibtool manual (section A.5, page 27); it
  can be customized too.

 Thanks, I thought the bibtool was used to beautify (format) the
 manually build .bib entries.
 seems it has lots of functions I don't know.

 Maybe you're looking for bibclean instead:

 http://packages.debian.org/squeeze/bibclean

Thanks, your guys are professional.
I fixed several unexpected value and unexpected/expected comma issue
by bibclean.

Best regards,

 Cheers,

 --
 Benoît Knecht


 --
 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/20120225135907.gd1...@marvin.lan



--
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/CAG9cJm=ep0KiSi2dsJ3qDg4uKcmq=7rmj4ceb4hkeao6mt5...@mail.gmail.com

Re: RFS: bibtool/2.54 (new upstream release) -- tool for BibTeX database manipulation

[Norbert Preining]

On Sa, 25 Feb 2012, lina wrote:
 For the  journal  = jbioch,
 
 It transformed the Upper case into small case.
 
 supposed to be journal = JBIOCH

Is JBIOCH a bibtex string defined via
@string{JBIOCH=...}
?

I am not sure but maybe @strings in bibtex are case insensitive ...
don't know, did you try?

If not, then this should be a proper bug report and does not
withhold any upload.

Best wishes

Norbert

Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live  Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094

`My doctor says that I have a malformed public-duty gland
and a natural deficiency in moral fibre, and that I am
therefore excused from saving Universes.'
 --- Ford's last ditch attempt to get out of helping
 --- Slartibartfast.
 --- Douglas Adams, The Hitchhikers Guide to the Galaxy


-- 
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/20120226001828.gc1...@gamma.logic.tuwien.ac.at

Re: RFS: bibtool/2.54 (new upstream release) -- tool for BibTeX database manipulation

[lina]

On Sun, Feb 26, 2012 at 8:18 AM, Norbert Preining prein...@logic.at wrote:
 On Sa, 25 Feb 2012, lina wrote:
 For the  journal      = jbioch,

 It transformed the Upper case into small case.

 supposed to be journal = JBIOCH

 Is JBIOCH a bibtex string defined via
        @string{JBIOCH=...}
 ?
Yes. Sure

 I am not sure but maybe @strings in bibtex are case insensitive ...
 don't know, did you try?
I don't know how to try.

 If not, then this should be a proper bug report and does not
 withhold any upload.

 Best wishes

Best regards,

 Norbert
 
 Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
 JAIST, Japan                                 TeX Live  Debian Developer
 DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
 
 `My doctor says that I have a malformed public-duty gland
 and a natural deficiency in moral fibre, and that I am
 therefore excused from saving Universes.'
                 --- Ford's last ditch attempt to get out of helping
                 --- Slartibartfast.
                 --- Douglas Adams, The Hitchhikers Guide to the Galaxy


--
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/cag9cjmmvnzew3tfbq44dfbjxgre7ayq6zxgp-aazycb4vxr...@mail.gmail.com

Bug#661213: RFS: bibtool/2.54 (new upstream release) -- tool for BibTeX database manipulation

[Jerome Benoit]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package bibtool.

 * Package name: bibtool
   Version : 2.54+ds-1
   Upstream Author : Gerd Neugebauer g...@gerd-neugebauer.de
 * URL : 
http://www.gerd-neugebauer.de/software/TeX/BibTool/index.en.html
 * License : GPL-1+
   Section : tex

   It builds those binary packages:

   bibtool- tool to manipulate BibTeX files

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

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

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

   dget -x 
http://mentors.debian.net/debian/pool/main/b/bibtool/bibtool_2.54+ds-1.dsc

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

   Kind regards,
   Jerome BENOIT



-- 
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/20120225034449.15761.55176.report...@nen.dnsalias.org

RFS: bibtool/2.54 (new upstream release) -- tool for BibTeX database manipulation

[Jerome BENOIT]

Dear Mentors, dear TeX Maintainers,

I am looking for a sponsor for my package bibtool.

 * Package name: bibtool
   Version : 2.54+ds-1
   Upstream Author : Gerd Neugebauer g...@gerd-neugebauer.de
 * URL : 
http://www.gerd-neugebauer.de/software/TeX/BibTool/index.en.html
 * License : GPL-1+
   Section : tex

   It builds those binary packages:

   bibtool- tool to manipulate BibTeX files

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

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

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

   dget -x 
http://mentors.debian.net/debian/pool/main/b/bibtool/bibtool_2.54+ds-1.dsc

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

   Kind regards,
   Jerome BENOIT


--
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/4f485acb.8070...@rezozer.net