Bug#736884: Bug#736885: RFS: gdal/1.10.1+dfsg-4

2014-01-27 Thread Sebastiaan Couwenberg
On 01/28/2014 08:03 AM, Andreas Tille wrote:
> On Tue, Jan 28, 2014 at 12:20:39AM +0100, Sebastiaan Couwenberg wrote:
>>> gdal is currently involved in the ongoing poppler transition. To
>>> not entangle the poppler and libepsilon transition, please talk to
>>> the Release Team and wait for their OK. (I don't know how many
>>> packages are involved in the libepsilon transition, but you might
>>> want to read [1] on how to coordinate transitions with the Release
>>> Team.)
>>
>> GDAL is already marked 'good' in the poppler transition, that doesn't
>> seem to be a problem. The openjpeg transition in which it's include
>> via poppler may be.
>>
>> Since only gdal and librasterlite need to be rebuild for the new
>> libepsilon skipping the release team was not protested. See:
>>
>> https://lists.debian.org/debian-gis/2014/01/msg00054.html
>>
>>> But anyway, this upload is not required. Once the new libepsilon
>>> got built and installed everywhere,
> 
> libepsilon is just uploaded

Thanks.

>>> it is enough to request
>>> binNMUs. reportbug release.debian.org has a template for that.
>>
>> Andreas, should we go this route instead?
> 
> Requesting binNMUs would do less stress test to my poor connection. :-)
> 
> I'd also like to say that you are asking for sponsoring 1.1~svn11-3 in
> #736884 but Git has only 1.1g-3 which is just in experimental.

Because master already has 1.1g, the changes for 1.1~svn-3 live in the
1.1_svn11 branch. But this won't be required anymore.

Kind Regards,

Bas

-- 
GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old)


-- 
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/52e757d6.6020...@xs4all.nl



Bug#736884: Bug#736885: RFS: gdal/1.10.1+dfsg-4

2014-01-27 Thread Andreas Tille
On Tue, Jan 28, 2014 at 12:20:39AM +0100, Sebastiaan Couwenberg wrote:
> > gdal is currently involved in the ongoing poppler transition. To
> > not entangle the poppler and libepsilon transition, please talk to
> > the Release Team and wait for their OK. (I don't know how many
> > packages are involved in the libepsilon transition, but you might
> > want to read [1] on how to coordinate transitions with the Release
> > Team.)
> 
> GDAL is already marked 'good' in the poppler transition, that doesn't
> seem to be a problem. The openjpeg transition in which it's include
> via poppler may be.
> 
> Since only gdal and librasterlite need to be rebuild for the new
> libepsilon skipping the release team was not protested. See:
> 
> https://lists.debian.org/debian-gis/2014/01/msg00054.html
> 
> > But anyway, this upload is not required. Once the new libepsilon
> > got built and installed everywhere,

libepsilon is just uploaded

> > it is enough to request
> > binNMUs. reportbug release.debian.org has a template for that.
> 
> Andreas, should we go this route instead?

Requesting binNMUs would do less stress test to my poor connection. :-)

I'd also like to say that you are asking for sponsoring 1.1~svn11-3 in
#736884 but Git has only 1.1g-3 which is just in experimental.

Kind regards

   Andreas.

-- 
http://fam-tille.de


-- 
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/20140128070327.gb9...@an3as.eu



Re: lintian usage and inconsistence problem

2014-01-27 Thread Niels Thykier
On 2014-01-27 23:41, Etienne Millon wrote:
> * T o n g  [140127 23:37]:
>> $ lintian -EviIL +pedantic --color auto --display-experimental
>>   ../*.dsc
>> [...]
>> I.e., when I invoke lintian manually, I didn't see problems reported
>> by debuild. 
> 
> Hi Tong,
> 
> Lintian can check both source packages (*.dsc) or binary packages
> (*.deb). By running it on the .dsc file, you only see the results of
> source checks.
> 
> The solution to this is to invoke lintian on the .changes file.
> As a consequence it will do both source and binary checks.
> 
> Hope that helps !
> 

Bonus hint: you can often omit the package argument for lintian, when
you run it from the unpacked source tree.  In that case, lintian will
guess what (changes) file you want to process based on
"debian/changelog" (which must then be available).

~Niels



-- 
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/52e74f6c.4020...@thykier.net



Bug#736839: marked as done (RFS: sosreport/3.1-1 ITP)

2014-01-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Jan 2014 04:27:29 +
with message-id 
and subject line closing RFS: sosreport/3.1-1 ITP
has caused the Debian Bug report #736839,
regarding RFS: sosreport/3.1-1 ITP
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.)


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

 * Package name : sosreport
   Version: 3.1-1
   Upstream Author   : Adam Stokes
 * URL : https://github.com/sosreport/sosreport
 * License: GPL-2
   Section : admin

  It builds those binary packages:

sosreport  - Set of tools to gather troubleshooting data from a system

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

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


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

dget -x 
http://mentors.debian.net/debian/pool/main/s/sosreport/sosreport_3.1-1.dsc

  More information about hello can be obtained from
https://github.com/sosreport/sosreport.

  Changes since the last upload:

sosreport (3.1-1) sid; urgency=low

  * New upstream release v3.1
Features include:
- Full Python 3 support
- Further modularized openstack plugins
  * debian/rules:
- Use pybuild
  * debian/control:
- Use X-Python-Version: >= 3.3

 -- Adam Stokes   Wed, 15 Jan 2014 16:58:54 -0500



  Regards,

Adam Stokes
--- End Message ---
--- Begin Message ---
Package sosreport version 3.1-1 is in unstable now.
http://packages.qa.debian.org/sosreport--- End Message ---


Bug#722224: marked as done (RFS: kqoauth/0.98-1 [ITP])

2014-01-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Jan 2014 04:27:29 +
with message-id 
and subject line closing RFS: kqoauth/0.98-1 [ITP]
has caused the Debian Bug report #74,
regarding RFS: kqoauth/0.98-1 [ITP]
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.)


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

 * Package name: kqoauth
   Version : 0.98-1
   Upstream Author : Johan Paul 
 * URL : https://github.com/kypeli/kQOAuth
 * License : LGPL-2.1+
   Section : libs

  It builds those binary packages:

 libkqoauth-dbg - Library for OAuth 1.0 authentication -- debugging symbols
 libkqoauth-dev - Library for OAuth 1.0 authentication -- development files
 libkqoauth0 - Library for OAuth 1.0 authentication

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

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


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

dget -x 
http://mentors.debian.net/debian/pool/main/k/kqoauth/kqoauth_0.98-1.dsc

  More information about kqoauth can be obtained from
https://github.com/kypeli/kQOAuth


  Changes since the last upload:

  kqoauth (0.98-1) unstable; urgency=low

* Initial release (Closes: #722219)

   -- Howard Chan   Sat, 07 Sep 2013 23:59:21 +0800



  Regards,
   Howard Chan
--- End Message ---
--- Begin Message ---
Package kqoauth has been removed from mentors.--- End Message ---


Bug#728059: RFS: gnome-shell-pomodoro/0.6.20131027-1 [ITA]

2014-01-27 Thread Vincent Cheng
Hi Joseph,

On Mon, Jan 20, 2014 at 2:33 PM, Joseph Herlant  wrote:

>> - Why "Architecture: any" if there aren't any arch-specific files in
>> your package?
>
> As it means any architecture supported by debian and that it is the "most
> frequently used" regarding debina policy 5.6.8. I thought it could
> stay like this.
> What's your advice for this?
> Use "all" instead of "any"?

Yes, use "all" instead. "any" will cause your package to be compiled
on all Debian release architectures and introduce different binary
packages of gnome-shell-pomodoro for every supported arch; "all" will
save buildd time and will only install a single binary package for use
on all archs.

>> - Description synopsis (the short one-liner) should be <60 chars (Policy 
>> 3.4.1)
>
> Actually it's 80 chars but You're right it was too long. I shorted it.

Ack, 80 chars, sorry.

It still doesn't abide by devref guidelines though; you should remove
"This" and the period at the end of your synopsis (devref 6.2.2 [1]).
Also, your description has a few other minor issues (e.g. inconsistent
capitalization of "Pomodoro Technique". You may wish to ask for a
review of your package synopsis and description via
debian-l10n-engl...@lists.debian.org (at this point I'm just being
pedantic, so ignore this if you want, I suppose, but ideally fix the
synopsis at least).

> The updated package has been updated to mentors:
> http://mentors.debian.net/debian/pool/main/g/gnome-shell-pomodoro/gnome-shell-pomodoro_0.8.0-2.dsc

Please merge your changelog entries into a single one (version
0.8.0-1). You also don't need to reference me in your changelog entry.
:)

Also, gnome-shell-pomodoro should not depend on intltool and
libglib2.0-dev. Those packages are needed to build
gnome-shell-pomodoro (hence why they are listed in build-depends), but
not for running g-s-pomodoro itself.

Regards,
Vincent

[1] 
https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis


-- 
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/CACZd_tBquN3wDWX2NNbuUu889ntxNkTT7J54D+d_XbJK=sn...@mail.gmail.com



Bug#736861: marked as done (Subject: RFS: mathjax/2.2-1~bpo70+1)

2014-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jan 2014 18:13:01 -0800
with message-id 

and subject line Re: Bug#736861: Subject: RFS: mathjax/2.2-1~bpo70+1
has caused the Debian Bug report #736861,
regarding Subject: RFS: mathjax/2.2-1~bpo70+1
to be marked as done.

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

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


-- 
736861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736861
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 a backport of "mathjax" to Wheezy.

This package is a dependency for another backport (Calibre). I've had no
response from the original maintainer in the last 4 weeks so I'm 
proceeding with the backport.


 * Package name: mathjax
   Version : 2.2-1~bpo70+1
   Upstream Author : MathJax (http://www.mathjax.org/contact/)
 * URL : http://www.mathjax.org/
 * License : Apache 2.0/OFL-1.1
   Section : web

It builds these binary packages:

  fonts-mathjax - JavaScript display engine for LaTeX and MathML (fonts)
  fonts-mathjax-extras - JavaScript display engine for LaTeX and MathML
 (extra fonts)
  libjs-mathjax - JavaScript display engine for LaTeX and MathML

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


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

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

  dget -x 
http://mentors.debian.net/debian/pool/main/m/mathjax/mathjax_2.2-1~bpo70+1.dsc


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

Changes since last version in Wheezy (1.1-2):

  mathjax (2.2-1) unstable; urgency=low

  * New upstream release.
  * Make debian/watch generate tarballs with correct extension.
  * Update debian/copyright: bump years, and transfer the copyright
from "Design Science, Inc" to "The MathJax Consortium" (following
upstream).
  * Install localization files and test HTML files.

 -- Dmitry Shachnev   Sun, 26 May 2013 15:07:53 +0400

  mathjax (2.1+20121028-2) unstable; urgency=low

  * Revert the Vcs-Git change, lintian doesn't like that.
  * Mark fonts packages as Multi-Arch: foreign, fixes a lintian warning.
  * Upload to unstable.

 -- Dmitry Shachnev   Thu, 09 May 2013 09:38:36 +0400

  mathjax (2.1+20121028-1) experimental; urgency=low

  * New upstream release.
  * Set Maintainer to myself.
  * Don't build libjs-mathjax-doc, it is now in a separate source.
  * Suggest fonts-stix.
  * Install images directory.
  * Replace current working directory while packing JS files.
  * Update Vcs-Git to point to git.debian.org.
  * Update debian/copyright:
+ Use full text of SIL Open Font License.
+ Use stand-alone header for Apache license.
  * Update debian/watch to the new GitHub URLs (thanks to
Andrew Starr-Bochicchio for the suggestion).
  * Split out the fonts to fonts-mathjax and fonts-mathjax-extras
packages.
  * Restore original compressed files in clean target (not build).
  * Make short descriptions different and a bit shorter.

 -- Dmitry Shachnev   Fri, 21 Dec 2012 16:31:21 +0400

  mathjax (2.0.3-2) experimental; urgency=low

  * Set priority to optional
  * Repack javascript files during build
- Build-depend on yui-compressor and perl
- Add debian/packer directory containing packing scripts
- Add debian/combiner directory containing scripts used for creating
"combined" configs

 -- Dmitry Shachnev   Sat, 25 Aug 2012 18:17:59 +0400

  mathjax (2.0.3-1) experimental; urgency=low

  * New snapshot from upstream git (Closes: #683966)
  * Use xz compression method (Closes: #683963, thanks to Julian Taylor
for the patch)

 -- Dmitry Shachnev   Wed, 08 Aug 2012 19:48:35 +0400

  mathjax (2.0-2) experimental; urgency=low

  * Split out libjs-mathjax-doc package
  * Build docs using python3 version of sphinx and dh_sphinxdoc
  * Update debian/copyright and fix Format URL

 -- Dmitry Shachnev   Thu, 26 Jul 2012 14:39:31 +0400

  mathjax (2.0-1) experimental; urgency=low

  * Set Maintainer to Debian Javascript Maintainers team
  * Add myself to Uploaders
  * New upstream release (Closes: #664673)
  * Clone the docs directory before building docs, to fix build failures
  when building twice in a row
  * Fix search not working in docs
  * Bump Standards-Version to 3.9.3, no changes needed
  * Bump debhelper compatibility level to 9
  * Some minor tweaks to the package description
  * Update debian/watch

 -- Dmitry Shachnev   Mon, 16 Jul 2012 13:37:23 +0400

Regards,
 Gary Preston
--- End Mes

Bug#736871: marked as done (RFS: calibre/1.14.0+dfsg-1~bpo70+1)

2014-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jan 2014 18:11:14 -0800
with message-id 

and subject line Re: Bug#736871: RFS: calibre/1.14.0+dfsg-1~bpo70+1
has caused the Debian Bug report #736871,
regarding RFS: calibre/1.14.0+dfsg-1~bpo70+1
to be marked as done.

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

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


-- 
736871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736871
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 a backport of the package
"calibre". The current calibre package maintainer has also
been made aware of this backport.

* Package name: calibre
  Version : 1.14.0+dfsg-1~bpo70+1
  Upstream Author : Kovid Goyal (ko...@kovidgoyal.net)
* URL : http://calibre-ebook.com
* License : GPL-3/GPL-2/BSD/LGPL2.1+/MIT/other
  Section : text

There are multiple licenses involved, see:

http://metadata.ftp-master.debian.org/changelogs//main/c/calibre/calibre_1.14.0+dfsg-1_copyright

It builds these binary packages:

  calibre- e-book converter and library management
  calibre-bin - e-book converter and library management

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


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

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

  dget -x 
http://mentors.debian.net/debian/pool/main/c/calibre/calibre_1.14.0+dfsg-1~bpo70+1.dsc


Calibre depends on a backport of "mathjax" which I'm also seeking a 
sponsor for (see bug #736861)


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

More information about calibre can be obtained from 
http://calibre-ebook.com/


Changes from last Wheezy version 0.8.51+dfsg1-0.1:

calibre (1.14.0+dfsg-1) unstable; urgency=low

  * New upstream release. (Closes: #731502)
  * Depend on python-pil | python-imaging now, upstream source is 
compatible

with both. (Closes: #731501)

 -- Martin Pitt   Fri, 06 Dec 2013 08:28:47 +0100

calibre (1.9.0+dfsg-1) unstable; urgency=low

  * New upstream release.
  * debian/calibre.install: Install new module.
  * Bump Standards-Version to 3.9.5, no changes necessary.

 -- Martin Pitt   Mon, 04 Nov 2013 11:02:15 +0100

calibre (1.5.0+dfsg-1) unstable; urgency=low

  * New upstream release. (Closes: #722962)
  * Drop removal of non-free fonts, they got removed upstream.
  * use_system_markdown.patch: Adjust for new upstream release.
  * Drop debian/local/calibre-mount-helper and its installation in
debian/rules, upstream removed the mount-helper.
  * debian/local/calibre-gui.desktop: Add GenericName, thanks Ronny
Standtke. (Closes: #662838)

 -- Martin Pitt   Mon, 14 Oct 2013 12:12:07 +0200

calibre (1.0.0+dfsg-1) unstable; urgency=low

  * New upstream release. (Closes: #720836)
  * debian/calibre.install: Drop usr/etc, not shipped by upstream any more.
  * debian/control: Add python-apsw dependency.

 -- Martin Pitt   Mon, 26 Aug 2013 07:33:55 +0200

calibre (0.9.41+dfsg-1) unstable; urgency=low

  * New upstream release.
  * debian/local/calibre.desktop: Rename to calibre-gui.desktop to 
match its

window class. (LP: #1206687)
  * Add debian/local/ebook-viewer.desktop, so that one can directly open
*.epub or *.mobi files in file browsers. Thanks Korey Lu!
(Closes: #664182)
  * Make it possible to auto-start calibre when connecting an e-book reader
device:
- Add debian/local/mime/calibre.xml MIME association, install in
  debian/calibre.install.
- debian/local/calibre-gui.desktop: Add MIME type and file argument.
- Thanks to Thanks Korey Lu! (Closes: #715246)

 -- Martin Pitt   Thu, 01 Aug 2013 18:17:22 +0200

calibre (0.9.31+dfsg-1) unstable; urgency=low

  * New upstream release.
  * Rebuild against current sip4 ABI, this makes the package installable
again. (Closes: #708613)
  * Bump Standards-Version to 3.9.4, no changes necessary.

 -- Martin Pitt   Tue, 21 May 2013 08:56:01 +0200

calibre (0.9.27+dfsg-1) experimental; urgency=low

  Upload to experimental as unstable's mathjax version is too old.

  [ Dmitry Shachnev ]
  * Remove non-free bundled copy of unrar. (Closes: #704977, #702816)
  * Remove bundled copy of mathjax. (Closes: #700838)
  * Remove bundled copy of python-markdown.
  * Make get-orig-tarball downloading the correct version.
  * Remove *.pyc, *.qrc, *.so and *_ui.py files in clean target.

  [ Martin Pitt ]
  * New upstream release.
  * dont_build_unrar_plugin.patch: Also remove "rar" as accepted file
extension.

 -- Martin Pitt   Tue, 23 Apr 2013 21:58:1

Bug#733578: hwinfo/21.0-1 needs updates / FTBFS of libx86emu

2014-01-27 Thread Johann Felix Soden
Hi Sebastien, hi Tomasz,

I have not yet completely reviewed hwinfo 21.0-1, but
there is at least one thing which needs to be fixed:

 - debian/libhd21.symbols is incomplete on i386. A fixed version is 
   attached.

And I found trailing whitespaces in old debian/changelog entries and
debian/libhd-doc.doc-base.

Since related, here some comments about libx86emu:

At the moment, it FTBFS on some architectures [mips, mipsel,
powerpc, ...] because of missing sys/io.h.
As the new hwinfo depends on it, this restricts the architectures where
it will be available. So this should be fixed before hwinfo is uploaded
- for example by fixing libx86emu itself or by reducing the dependency
to the architectures where it is really available.

Actually, the libx86 package contains a copy of libx86emu
and has therefore similar problems [1,2]. Please contact Anibal Monsalve
Salazar (ani...@debian.org) who maintains it. Especially for the
security team, it would be nice, if it could use the new libx86emu
package instead of including its own copy.

Best wishes
 Johann Felix

PS: Please update the git repositories where needed.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465721
[2] https://buildd.debian.org/status/package.php?p=libx86

--
Johann Felix Soden, DD
joh...@debian.org
libhd.so.21 libhd21 #MINVER#
 CDBISDN_DATE@Base 21.0
 CDBISDN_DBVERSION@Base 21.0
 Dir_xlate@Base 21.0
 add_disk_entry@Base 21.0
 add_hd_entry@Base 21.0
 add_joystick_details@Base 21.0
 add_mem@Base 21.0
 add_res_entry@Base 21.0
 add_str_list@Base 21.0
 assign_edd_info@Base 21.0
 (arch=i386)avm_a1_detect@Base 21.0
 canon_str@Base 21.0
 check_for_responce@Base 21.0
 cmp_hd@Base 21.0
 crc64@Base 21.0
 detect_smp_bios@Base 21.0
 dev_name_duplicate@Base 21.0
 device_class@Base 21.0
 dump_klog@Base 21.0
 edd_disk_signature@Base 21.0
 eisa_vendor_str@Base 21.0
 exists_hd_entry@Base 21.0
 float2str@Base 21.0
 free_devtree@Base 21.0
 free_disk_list@Base 21.0
 free_driver_info@Base 21.0
 free_hd_detail@Base 21.0
 free_mem@Base 21.0
 free_misc@Base 21.0
 free_res_list@Base 21.0
 free_scsi@Base 21.0
 free_str_list@Base 21.0
 gather_resources@Base 21.0
 get_cmd_param@Base 21.0
 get_cmdline@Base 21.0
 get_disk_crc@Base 21.0
 get_dsl_info@Base 21.0
 get_dvd_profile@Base 21.0
 get_isdn_info@Base 21.0
 get_probe_val_int@Base 21.0
 get_probe_val_list@Base 21.0
 get_probe_val_str@Base 21.0
 get_sysfs_attr@Base 21.0
 get_sysfs_attr_by_path2@Base 21.0
 get_sysfs_attr_by_path@Base 21.0
 get_vbe_info@Base 21.0
 get_video_mode@Base 21.0
 hal_add_new@Base 21.0
 hal_find_device@Base 21.0
 hal_get_any@Base 21.0
 hal_get_bool@Base 21.0
 hal_get_int32@Base 21.0
 hal_get_list@Base 21.0
 hal_get_str@Base 21.0
 hal_get_useful_str@Base 21.0
 hal_invalidate@Base 21.0
 hal_invalidate_all@Base 21.0
 has_something_attached@Base 21.0
 have_common_res@Base 21.0
 hd_add_driver_data@Base 21.0
 hd_add_id@Base 21.0
 hd_add_old_id@Base 21.0
 hd_apm_enabled@Base 21.0
 hd_attr_list@Base 21.0
 hd_attr_uint@Base 21.0
 hd_base_class_list@Base 21.0
 hd_boot_arch@Base 21.0
 hd_boot_disk@Base 21.0
 hd_bus_list@Base 21.0
 hd_busid_to_hwcfg@Base 21.0
 hd_cdbisdn_get_card@Base 21.0
 hd_cdbisdn_get_card_from_id@Base 21.0
 hd_cdbisdn_get_card_from_type@Base 21.0
 hd_cdbisdn_get_db_date@Base 21.0
 hd_cdbisdn_get_db_version@Base 21.0
 hd_cdbisdn_get_vario@Base 21.0
 hd_cdbisdn_get_vario_from_type@Base 21.0
 hd_cdbisdn_get_vendor@Base 21.0
 hd_cdbisdn_get_version@Base 21.0
 hd_change_config_status@Base 21.0
 hd_change_status@Base 21.0
 hd_clear_probe_feature@Base 21.0
 hd_color@Base 21.0
 hd_copy@Base 21.0
 hd_cpu_arch@Base 21.0
 hd_display_adapter@Base 21.0
 hd_dump_entry@Base 21.0
 hd_find_sysfs_id@Base 21.0
 hd_find_sysfs_id_devname@Base 21.0
 hd_fork@Base 21.0
 hd_fork_done@Base 21.0
 hd_free_hal_devices@Base 21.0
 hd_free_hal_properties@Base 21.0
 hd_free_hd_data@Base 21.0
 hd_free_hd_list@Base 21.0
 hd_free_manual@Base 21.0
 hd_get_device_by_idx@Base 21.0
 hd_get_hddb_dir@Base 21.0
 hd_get_hddb_path@Base 21.0
 hd_getdisksize@Base 21.0
 hd_hal_print_prop@Base 21.0
 hd_has_pcmcia@Base 21.0
 hd_hw_item_name@Base 21.0
 hd_hw_item_type@Base 21.0
 hd_is_hw_class@Base 21.0
 hd_is_sgi_altix@Base 21.0
 hd_is_shm_ptr@Base 21.0
 hd_is_uml@Base 21.0
 hd_is_xen@Base 21.0
 hd_join@Base 21.0
 hd_list2@Base 21.0
 hd_list@Base 21.0
 hd_list_with_status2@Base 21.0
 hd_list_with_status@Base 21.0
 hd_log@Base 21.0
 hd_log_hex@Base 21.0
 hd_log_printf@Base 21.0
 hd_mac_color@Base 21.0
 hd_manual_read_entry@Base 21.0
 hd_manual_write_entry@Base 21.0
 hd_mod_cmp@Base 21.0
 hd_module_is_active@Base 21.0
 hd_module_list@Base 21.0
 hd_move_to_shm@Base 21.0
 hd_pci_complete_data@Base 21.0
 hd_pci_read_data@Base 21.0
 hd_probe_feature@Base 21.0
 hd_probe_feature_by_name@Base 21.0
 hd_probe_feature_by_value@Base 21.0
 hd_read_cdrom_info@Base 21.0
 hd_read_config@Base 21.0
 hd_read_mmap@Base 21.0
 hd_read_properties@Base 21.0
 hd_read_sysfs_link@Base 21.0
 hd_report_this@Base 21.0
 hd_scan@Base 21.0
 hd_scan_bios@Base 21.0
 

Bug#736885: RFS: gdal/1.10.1+dfsg-4

2014-01-27 Thread Sebastiaan Couwenberg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 01/28/2014 12:01 AM, Sebastian Ramacher wrote:
> On 2014-01-27 23:34:25, Bas Couwenberg wrote:
>> Package: sponsorship-requests Severity: normal
>> 
>> Dear mentors,
>> 
>> I am looking for a sponsor for my package "gdal"
>> 
>> [...]
>> 
>> Changes since the last upload:
>> 
>> * Rebuild for libepsilon1.
> 
> gdal is currently involved in the ongoing poppler transition. To
> not entangle the poppler and libepsilon transition, please talk to
> the Release Team and wait for their OK. (I don't know how many
> packages are involved in the libepsilon transition, but you might
> want to read [1] on how to coordinate transitions with the Release
> Team.)

GDAL is already marked 'good' in the poppler transition, that doesn't
seem to be a problem. The openjpeg transition in which it's include
via poppler may be.

Since only gdal and librasterlite need to be rebuild for the new
libepsilon skipping the release team was not protested. See:

https://lists.debian.org/debian-gis/2014/01/msg00054.html

> But anyway, this upload is not required. Once the new libepsilon
> got built and installed everywhere, it is enough to request
> binNMUs. reportbug release.debian.org has a template for that.

Andreas, should we go this route instead?

Kind Regards,

Bas

- -- 
GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCgAGBQJS5unHAAoJEGdQ8QrojUrxixoP/AqoV2br/jAhbYYnUAOzwiYw
lgelFntsNGWQZ0o+xCgOwdk8enTiMNWB00je+PCqZ+v+KhXJOHZo1juR9+5GCNqb
XDGvbbqPXVdR1O79mTcaH27JlVprGM6sjN2Uy0LDf73PrtfBFHgqoCIA/poe9UPb
0CWPz+eH+Vu/hPf5nC6zbGU1tyuEnOBXoD94HTKWs8tRg1EP0pymPtu5DRIRisMP
YuHSg4ASPQKKcMbNzUgI1cLyd/LVyDBhNamAMz1j7MqxdQSWSpg9M1LfPAn2lZEn
9dSOKPllBPL51bBKtGp5kih4/MGWWveBzfEZ4eCujUHWV1M3856FHXs0x5LK2LLh
YsuQuyZo6JEVETxVHsSwvu1Ecib2cLU9mJ9AspePRD/S+8PnYQmgR8tyFuOQXsR+
JlyEq8vFM61Ovs/p/OE1OH5Iggtj/uAGn+9P1Qd/UIgjRxCnT4ZojIzqKrgibSsu
itGb7Pj5s/B/XkjkH6jMB8eSLeGFc/kb6y75rQzvqjUeOGBYJLuTIQlMV2rQMnyi
+WWQrx4coGqCBPkEkgc6zg2VQAtxNo6WCXyQlzFD86n/RMlQTuOg0QqPqtG/9LzW
9Q7PWnQLhsw98u4hbbmIPglzo2kpNZYSNn5Nhe1i/NINGIkARhxm+pbv2IPGmmCY
fkGYwq9Ja8te2maytzLD
=HbSZ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52e6e9c7.4010...@xs4all.nl



Bug#736885: RFS: gdal/1.10.1+dfsg-4

2014-01-27 Thread Sebastian Ramacher
On 2014-01-27 23:34:25, Bas Couwenberg wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "gdal"
> 
>  Package name: gdal
>  Version : 1.10.1+dfsg-4
>  Upstream Author : The GDAL/OGR project team, Frank Warmerdam 
> 
>  URL : http://www.gdal.org/
>  License : MIT
>  Section : science
> 
> It builds those binary packages:
> 
>  gdal-bin - Geospatial Data Abstraction Library - Utility programs
>  libgdal-dev  - Geospatial Data Abstraction Library - Development files
>  libgdal-doc  - Documentation for the Geospatial Data Abstraction Library
>  libgdal-java - Java bindings to the Geospatial Data Abstraction Library
>  libgdal-perl - Perl bindings to the Geospatial Data Abstraction Library
>  libgdal1-dev - Geospatial Data Abstraction Library - Transitional package
>  libgdal1h- Geospatial Data Abstraction Library
>  python-gdal  - Python bindings to the Geospatial Data Abstraction Library
>  python3-gdal - Python 3 bindings to the Geospatial Data Abstraction Library
> 
> To access further information about this package, please visit the following 
> URL:
> 
> http://mentors.debian.net/package/gdal
> 
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x 
> http://mentors.debian.net/debian/pool/main/g/gdal/gdal_1.10.1+dfsg-4.dsc
> 
> More information about GDAL can be obtained from http://www.gdal.org/.
> 
> Changes since the last upload:
> 
>  * Rebuild for libepsilon1.

gdal is currently involved in the ongoing poppler transition. To not
entangle the poppler and libepsilon transition, please talk to the
Release Team and wait for their OK. (I don't know how many packages are
involved in the libepsilon transition, but you might want to read [1] on
how to coordinate transitions with the Release Team.)

But anyway, this upload is not required. Once the new libepsilon got
built and installed everywhere, it is enough to request binNMUs.
reportbug release.debian.org has a template for that.

Regards

[1] https://wiki.debian.org/Teams/ReleaseTeam/Transitions
-- 
Sebastian Ramacher


signature.asc
Description: Digital signature


Re: lintian usage and inconsistence problem

2014-01-27 Thread Etienne Millon
* T o n g  [140127 23:37]:
> $ lintian -EviIL +pedantic --color auto --display-experimental
>   ../*.dsc
> [...]
> I.e., when I invoke lintian manually, I didn't see problems reported
> by debuild. 

Hi Tong,

Lintian can check both source packages (*.dsc) or binary packages
(*.deb). By running it on the .dsc file, you only see the results of
source checks.

The solution to this is to invoke lintian on the .changes file.
As a consequence it will do both source and binary checks.

Hope that helps !

-- 
Etienne Millon


-- 
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/20140127224110.GA4860@klow



Bug#736885: RFS: gdal/1.10.1+dfsg-4

2014-01-27 Thread Bas Couwenberg
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 Package name: gdal
 Version : 1.10.1+dfsg-4
 Upstream Author : The GDAL/OGR project team, Frank Warmerdam 

 URL : http://www.gdal.org/
 License : MIT
 Section : science

It builds those binary packages:

 gdal-bin - Geospatial Data Abstraction Library - Utility programs
 libgdal-dev  - Geospatial Data Abstraction Library - Development files
 libgdal-doc  - Documentation for the Geospatial Data Abstraction Library
 libgdal-java - Java bindings to the Geospatial Data Abstraction Library
 libgdal-perl - Perl bindings to the Geospatial Data Abstraction Library
 libgdal1-dev - Geospatial Data Abstraction Library - Transitional package
 libgdal1h- Geospatial Data Abstraction Library
 python-gdal  - Python bindings to the Geospatial Data Abstraction Library
 python3-gdal - Python 3 bindings to the Geospatial Data Abstraction Library

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

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


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

  dget -x 
http://mentors.debian.net/debian/pool/main/g/gdal/gdal_1.10.1+dfsg-4.dsc

More information about GDAL can be obtained from http://www.gdal.org/.

Changes since the last upload:

 * Rebuild for libepsilon1.


Regards,
 Sebastiaan Couwenberg


-- 
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/20140127223425.14126.13226.report...@osiris.linuxminded.xs4all.nl



lintian usage and inconsistence problem

2014-01-27 Thread T o n g
Hi, 

I'm having problem using lintian.

This was my previous question:

On Thu, 23 Jan 2014 15:49:31 -0500, Tong wrote:

> On Thu, Jan 23, 2014 at 7:50 AM, Eriberto 
> wrote:
>> You have a lintian message yet:
>>
>> I: shc: spelling-error-in-manpage usr/share/man/man1/shc.1.gz comand
>> command
>>
>> And your problem isn't lintian version, but the configuration. Please,
>> read this:
>>
>> http://eriberto.pro.br/blog/?p=1289
> 
> Strange, I've freshly installed my sid, done the above changes, but
> still am not seeing the spelling-error-in-manpage prompt. Putting
> everything on the command line, "lintian -EviIL +pedantic --color auto
> --display-experimental", I'm still not getting that one.

In short, using "lintian -EviIL +pedantic --color auto --display-
experimental" wouldn't let me see the lintian warnings others see. 

Now, on top of that, 

When using "debuild -us -uc", at the end, I see:

---
Now running lintian...
warning: the authors of lintian do not recommend running it with root 
privileges!
W: zh-autoconvert source: newer-standards-version 3.9.5 (current is 3.9.4)
W: libhz-dev: wrong-section-according-to-package-name libhz-dev => 
libdevel
W: libhz0: hardening-no-relro usr/lib/libhz.so.0.0
W: zh-autoconvert: binary-without-manpage usr/bin/autob5
W: zh-autoconvert: binary-without-manpage usr/bin/autogb
E: zh-autoconvert: pkg-has-shlibs-control-file-but-no-actual-shared-libs
W: zh-autoconvert: postinst-has-useless-call-to-ldconfig
W: zh-autoconvert: postrm-has-useless-call-to-ldconfig
Finished running lintian.
---

However, when I invoke lintian manually myself again, I get this:

---
$ lintian -EviIL +pedantic --color auto --display-experimental ../*.dsc
N: Unpacking packages in group zh-autoconvert/0.3.16-5
N: 
N: Processing source package zh-autoconvert (version 0.3.16-5, arch 
source) ...
I: zh-autoconvert source: quilt-patch-missing-description 00_zh-
autoconvert_0.3.16-3.diff
N: 
N:quilt patch files should start with a description of patch. All 
lines...
...
I: zh-autoconvert source: quilt-patch-missing-description 01_hardening-no-
relro.diff
... 
---

I.e., when I invoke lintian manually, I didn't see problems reported by 
debuild. 

What's wrong? 

Thanks





-- 
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/lc6mrl$g6q$1...@ger.gmane.org



Bug#736884: RFS: librasterlite/1.1~svn11-3

2014-01-27 Thread Bas Couwenberg
Package: sponsorship-requests
Severity: normal

Dear mentors,

As part of the libepsilon mini transition,
I am looking for a sponsor for my package "librasterlite"

For more information about this mini transition see the thread on debian-gis@
starting at https://lists.debian.org/debian-gis/2014/01/msg00054.html

Please not that the changes for this version live in the 1.1_svn11 branch
instead of the master branch.

 Package name: librasterlite
 Version : 1.1~svn11-3
 Upstream Author : Alessandro Furieri 
 URL : https://www.gaia-gis.it/fossil/librasterlite
 License : MPL-1.1 or GPL-2.0+ or LGPL-2.1+
 Section : libs

It builds those binary packages:

 librasterlite1- library supporting raster data sources for spatialite
 librasterlite-dev - library supporting raster data sources for spatialite - 
headers
 rasterlite-dbg- library supporting raster data sources for spatialite - 
debugging
 rasterlite-bin- command line tools for librasterlite

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

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


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

  dget -x 
http://mentors.debian.net/debian/pool/main/libr/librasterlite/librasterlite_1.1~svn11-3.dsc

More information about librasterlite can be obtained from 
https://www.gaia-gis.it/fossil/librasterlite.

Changes since the last upload:

 * Add myself to Uploaders.
 * Rebuild for libepsilon1.


Regards,
 Sebastiaan Couwenberg


-- 
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/20140127223143.13422.49641.report...@osiris.linuxminded.xs4all.nl



Bug#736882: RFS: libepsilon/0.9.2-1

2014-01-27 Thread Bas Couwenberg
Package: sponsorship-requests
Severity: normal

Dear mentors,

As part of the libepsilon mini transition,
I am looking for a sponsor for my package "libepsilon"

For more information about this mini transition see the thread on debian-gis@
starting at https://lists.debian.org/debian-gis/2014/01/msg00054.html

 Package name: libepsilon
 Version : 0.9.2-1
 Upstream Author : Alexander Simakov 
 URL : http://sourceforge.net/projects/epsilon-project/
 License : GPL3+ or LGPL3+
 Section : science

It builds those binary packages:

 epsilon-bin- Library for wavelet image compression - tools
 libepsilon-dev - Library for wavelet image compression - development files
 libepsilon1- Library for wavelet image compression

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

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


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

  dget -x 
http://mentors.debian.net/debian/pool/main/libe/libepsilon/libepsilon_0.9.2-1.dsc

More information about libepsilon can be obtained from 
http://sourceforge.net/projects/epsilon-project/.

Changes since the last upload:

 * New upstream release (no code changes, only build system).
 * Add myself to Uploaders.
 * Use canonical URLs for Vcs-* fields.
 * Change priority to optional.
 * Update copyright file format from dep5 to copyright-format 1.0.
 * Bump Debhelper compatibility to 9.
 * Support Multi-Arch.
 * Use dh-autoreconf for retooling.
   (closes: #735228)
 * Use dh_auto_configure with additional options instead of configure.
 * Don't start description synopsis with an article.
 * Rename libepsilon0 to libepsilon1 to match SONAME.
 * Add man pages for start_epsilon_nodes and stop_epsilon_nodes.
 * Add dependency on dsh for epsilon-tools, required for *_epsilon_nodes.
 * Add symbols file for libepsilon1.
 * Bump Standards-Version to 3.9.5, changes: Vcs-* URLs, copyright format,
   shared library.


Regards,
 Sebastiaan Couwenberg


-- 
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/20140127222602.12752.14915.report...@osiris.linuxminded.xs4all.nl



Re: Help: Bug#733407: maude: FTBFS: surface.yy:63:67: error: 'parseResult' was not declared in this scope

2014-01-27 Thread Niels Thykier
On 2014-01-27 22:31, Andreas Tille wrote:
> Hi Niels,
> 
> I guess you want to tell me that I want something like
> 
>
> http://anonscm.debian.org/gitweb/?p=collab-maint/mscgen.git;a=blob;f=debian/patches/language.y-parse-param.patch;hb=HEAD
> 
> applied to maude code.  I need to admit that I'm to weak with bison and
> can not really make some sense out of its bison input to approach this.
> 
> Any help would be welcome
> 
>   Andreas.
> 
> [...]

While I am convinced that the problem is caused by bison, I am not
certain that a similar patch will work in your case.  But at least we
can narrow it down from "help with C++" to "help make bison generate the
right code".  I won't claim to be bison-savvy enough to be able to help
you with that though, sorry.

~Niels



-- 
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/52e6d1c2.8060...@thykier.net



Re: Help: Bug#733407: maude: FTBFS: surface.yy:63:67: error: 'parseResult' was not declared in this scope

2014-01-27 Thread Andreas Tille
Hi Niels,

I guess you want to tell me that I want something like

   
http://anonscm.debian.org/gitweb/?p=collab-maint/mscgen.git;a=blob;f=debian/patches/language.y-parse-param.patch;hb=HEAD

applied to maude code.  I need to admit that I'm to weak with bison and
can not really make some sense out of its bison input to approach this.

Any help would be welcome

  Andreas.

On Mon, Jan 27, 2014 at 08:57:55PM +0100, Niels Thykier wrote:
> On 2014-01-27 20:30, Andreas Tille wrote:
> > Hi,
> > 
> > does anybody have a clue how to fix this C++ issue?
> > 
> > Kind regards
> > 
> >  Andreas.
> > 
> 
> It is not a C++ issue, but a change in bison you are looking at.  I had
> a similar issue with mscgen not too long ago[1].
> 
> ~Niels
> 
> [1] http://packages.qa.debian.org/m/mscgen/news/20131229T131907Z.html
> 
> 
> > - Forwarded message from David Suárez  -
> > 
> > Date: Sat, 28 Dec 2013 19:10:41 +0100
> > From: David Suárez 
> > To: sub...@bugs.debian.org
> > Subject: Bug#733407: maude: FTBFS: surface.yy:63:67: error: 'parseResult' 
> > was not declared in this scope
> > X-Debian-PR-Message: report 733407
> > X-Debian-PR-Package: src:maude
> > X-Debian-PR-Keywords: jessie sid
> > X-Debian-PR-Source: maude
> > 
> > Source: maude
> > Version: 2.6-4
> > Severity: serious
> > Tags: jessie sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20131226 qa-ftbfs
> > Justification: FTBFS on amd64
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> > 
> > Relevant part (hopefully):
> >> g++ -DHAVE_CONFIG_H -I. -I. -I../..  -I../../src/Utility 
> >> -I../../src/Temporal -I../../src/Interface -I../../src/Core 
> >> -I../../src/Variable -I../../src/FullCompiler -I../../src/Higher 
> >> -I../../src/CUI_Theory -I../../src/S_Theory -I../../src/NA_Theory 
> >> -I../../src/FreeTheory -I../../src/ObjectSystem -I../../src/Mixfix 
> >> -I../../src/BuiltIn -I../../src/MSCP10 -I../../src/IO_Stuff 
> >> -I../../src/ACU_Persistent -I../../src/ACU_Theory 
> >> -I../../src/AU_Persistent -I../../src/AU_Theory -I../../src/Meta 
> >> -I../../src/3rdParty -I../../src/FullCompiler -I../../src/StrategyLanguage 
> >> -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> >> -Wformat -Werror=format-security -c -o libmixfix_a-surface.o `test -f 
> >> 'surface.cc' || echo './'`surface.cc
> >> In file included from ../../src/Interface/term.hh:34:0,
> >>  from ../../src/Variable/variableTerm.hh:28,
> >>  from ../../src/Core/variableInfo.hh:30,
> >>  from ../../src/Core/preEquation.hh:30,
> >>  from ../../src/Core/rule.hh:28,
> >>  from userLevelRewritingContext.hh:34,
> >>  from surface.yy:54:
> >> ../../src/Core/termSet.hh:35:3: warning: access declarations are 
> >> deprecated in favour of using-declarations; suggestion: add the 'using' 
> >> keyword [-Wdeprecated]
> >>PointerSet::cardinality;
> >>^
> >> ../../src/Core/termSet.hh:36:3: warning: access declarations are 
> >> deprecated in favour of using-declarations; suggestion: add the 'using' 
> >> keyword [-Wdeprecated]
> >>PointerSet::makeEmpty;
> >>^
> >> surface.yy: In function 'int yyparse()':
> >> surface.yy:63:67: error: 'parseResult' was not declared in this scope
> >>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
> >> parseResult))
> >>^
> >> surface.yy:235:6: note: in expansion of macro 'PARSE_RESULT'
> >>   PARSE_RESULT = UserLevelRewritingContext::QUIT;
> >>   ^
> >> surface.yy:63:67: error: 'parseResult' was not declared in this scope
> >>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
> >> parseResult))
> >>^
> >> surface.yy:312:6: note: in expansion of macro 'PARSE_RESULT'
> >>   PARSE_RESULT = UserLevelRewritingContext::QUIT;
> >>   ^
> >> surface.yy:63:67: error: 'parseResult' was not declared in this scope
> >>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
> >> parseResult))
> >>^
> >> surface.yy:319:10: note: in expansion of macro 'PARSE_RESULT'
> >>   PARSE_RESULT = UserLevelRewritingContext::QUIT;
> >>   ^
> >> surface.yy:573:4: error: expected ';' before '}' token
> >> }
> >> ^
> >> surface.yy:1097:33: error: expected ';' before '}' token
> >>  command  : KW_SELECT  { lexBubble(END_COMMAND, 1) }
> >>  ^
> >> surface.yy:1102:33: error: expected ';' before '}' token
> >>| KW_DUMP   { lexBubble(END_COMMAND, 1) }
> >>  ^
> >> surface.yy:63:67: error: 'parseResult' was not declared in this scope
> >>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
> >> parseResult))
> >>  

Bug#719801: Acknowledgement (RFS: roundup/1.5.0-1)

2014-01-27 Thread Kai Storbeck
On 27/01/2014 04:25, Andrew Starr-Bochicchio wrote:
> On Thu, Oct 17, 2013 at 5:20 PM, Kai Storbeck  wrote:
>> I have updated roundup_1.5.0-1 per the 17th of October with a few
>> changes after getting feedback by Sebastian Ramacher.
> 
> Hi Kai,
> 
> I came across your package on mentors, and I am interested in
> sponsoring it. Though, I ran into a few issues that need to be fixed
> first.

Hello Andrew,

Thanks for your response. I've marked the package as "no need for a
sponsor", but your feedback is very welcome.

Perhaps my discussions with Sebastian should've been Cc'ed to this bug.

> 1) You seem to maintain the packaging in a VCS:
> 
>>   * Move to git-dpm packaging
> 
> In that case, it is very useful to include Vcs-{Git, Svn, Bzr} and
> Vcs-Browser fields in debian/control:
> 
> https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-VCS-fields

Perhaps you can help me with this.

Since I'm joining the python application packaging team, I'll be moving
to SVN. I'm probably going to import the last uploaded version (1.20-1
or 1.1?) to svn.debian.org with this command:

$ svn import -m "New import" roundup \
 svn+ssh://svn.debian.org/svn/python-apps/packages/roundup/trunk

Would that do the right thing? I presume I now have access to
svn.debian.org, being in the team listing on Alioth? Would you know that?

If you don't know, I'll ask on the debian-python listing.

> 2) There are minified version of JQuery and Bootstrap located in:
> share/roundup/templates/jinja2/static

Thanks. I'm aware of that; Sebastian pointed this out too. I've already
posted upstream to ask them to include a non-minified version.

For 1.5.0 I'm a bit in the dark on how to proceed. Can I remove those
files, and ship a symlink to jquery and bootstrap packages? Or should I
make a full-fledged _dfsg.tgz file, and build from that?

> As you already remove other copies of JQuery in other templates, you
> probably already know that you should use the system copies.
> Additionally, minified JavaScript objects that are installed with the
> binary package must be built from source. Same goes for the minified
> Bootstrap css files in that directory.

Ah. css too. Sometimes I think its less work to let upstream build a
package, and let it drop from debian.

> Also, as long as these files are shipped in the tarball, their license
> information needs to be documented in debian/copyright.

Ouch. They are using bootstrap 2.2.2. That tarfile is not downloadable
from getbootstrap.com anymore, so I can only guess that this was
licenced under Apache 2.0. Would that be enough?

So, what should I do: remove the not working template from 1.5.0, or
ship with a broken template? We're talking 1.5.0, since 1.5.1 is not
released yet, and I haven't heard words about estimates.

> 3) You seemed to remove some necessary bits from your postrm to clean
> up when purging the package. From piuparts:
> 
> 3m20.5s ERROR: FAIL: Package purging left files on system:
>   /etc/roundup/ owned by: roundup
>   /etc/roundup/service/ not owned
>   /etc/roundup/service/log/ not owned
> 
> 3m20.5s ERROR: FAIL: Installation, upgrade and purging tests.

I'm aware of that too. I hadn't started working on both issues, pending
my move to subversion.

> There maybe further issues. This is just as far as I got. I'd be happy
> to do a closer review and hopefully sponsor the package once these
> problems are fixed.
> 
> Thanks for your work on Debian!

Cheers. I find it quite a lot of work for a niche leave-package, and its
not an easy package to start out with. Sadly.

Regards,
Kai






signature.asc
Description: OpenPGP digital signature


Bug#736871: RFS: calibre/1.14.0+dfsg-1~bpo70+1

2014-01-27 Thread Gary Preston

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for a backport of the package
"calibre". The current calibre package maintainer has also
been made aware of this backport.

* Package name: calibre
  Version : 1.14.0+dfsg-1~bpo70+1
  Upstream Author : Kovid Goyal (ko...@kovidgoyal.net)
* URL : http://calibre-ebook.com
* License : GPL-3/GPL-2/BSD/LGPL2.1+/MIT/other
  Section : text

There are multiple licenses involved, see:

http://metadata.ftp-master.debian.org/changelogs//main/c/calibre/calibre_1.14.0+dfsg-1_copyright

It builds these binary packages:

  calibre- e-book converter and library management
  calibre-bin - e-book converter and library management

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


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

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

  dget -x 
http://mentors.debian.net/debian/pool/main/c/calibre/calibre_1.14.0+dfsg-1~bpo70+1.dsc


Calibre depends on a backport of "mathjax" which I'm also seeking a 
sponsor for (see bug #736861)


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

More information about calibre can be obtained from 
http://calibre-ebook.com/


Changes from last Wheezy version 0.8.51+dfsg1-0.1:

calibre (1.14.0+dfsg-1) unstable; urgency=low

  * New upstream release. (Closes: #731502)
  * Depend on python-pil | python-imaging now, upstream source is 
compatible

with both. (Closes: #731501)

 -- Martin Pitt   Fri, 06 Dec 2013 08:28:47 +0100

calibre (1.9.0+dfsg-1) unstable; urgency=low

  * New upstream release.
  * debian/calibre.install: Install new module.
  * Bump Standards-Version to 3.9.5, no changes necessary.

 -- Martin Pitt   Mon, 04 Nov 2013 11:02:15 +0100

calibre (1.5.0+dfsg-1) unstable; urgency=low

  * New upstream release. (Closes: #722962)
  * Drop removal of non-free fonts, they got removed upstream.
  * use_system_markdown.patch: Adjust for new upstream release.
  * Drop debian/local/calibre-mount-helper and its installation in
debian/rules, upstream removed the mount-helper.
  * debian/local/calibre-gui.desktop: Add GenericName, thanks Ronny
Standtke. (Closes: #662838)

 -- Martin Pitt   Mon, 14 Oct 2013 12:12:07 +0200

calibre (1.0.0+dfsg-1) unstable; urgency=low

  * New upstream release. (Closes: #720836)
  * debian/calibre.install: Drop usr/etc, not shipped by upstream any more.
  * debian/control: Add python-apsw dependency.

 -- Martin Pitt   Mon, 26 Aug 2013 07:33:55 +0200

calibre (0.9.41+dfsg-1) unstable; urgency=low

  * New upstream release.
  * debian/local/calibre.desktop: Rename to calibre-gui.desktop to 
match its

window class. (LP: #1206687)
  * Add debian/local/ebook-viewer.desktop, so that one can directly open
*.epub or *.mobi files in file browsers. Thanks Korey Lu!
(Closes: #664182)
  * Make it possible to auto-start calibre when connecting an e-book reader
device:
- Add debian/local/mime/calibre.xml MIME association, install in
  debian/calibre.install.
- debian/local/calibre-gui.desktop: Add MIME type and file argument.
- Thanks to Thanks Korey Lu! (Closes: #715246)

 -- Martin Pitt   Thu, 01 Aug 2013 18:17:22 +0200

calibre (0.9.31+dfsg-1) unstable; urgency=low

  * New upstream release.
  * Rebuild against current sip4 ABI, this makes the package installable
again. (Closes: #708613)
  * Bump Standards-Version to 3.9.4, no changes necessary.

 -- Martin Pitt   Tue, 21 May 2013 08:56:01 +0200

calibre (0.9.27+dfsg-1) experimental; urgency=low

  Upload to experimental as unstable's mathjax version is too old.

  [ Dmitry Shachnev ]
  * Remove non-free bundled copy of unrar. (Closes: #704977, #702816)
  * Remove bundled copy of mathjax. (Closes: #700838)
  * Remove bundled copy of python-markdown.
  * Make get-orig-tarball downloading the correct version.
  * Remove *.pyc, *.qrc, *.so and *_ui.py files in clean target.

  [ Martin Pitt ]
  * New upstream release.
  * dont_build_unrar_plugin.patch: Also remove "rar" as accepted file
extension.

 -- Martin Pitt   Tue, 23 Apr 2013 21:58:12 +0200

calibre (0.9.18+dfsg-1) unstable; urgency=low

  * New upstream release. (Closes: #699700)
  * Unfuzz patches.
  * Add new libqt4-private-dev build dependency, required by this version.

 -- Martin Pitt   Tue, 12 Feb 2013 16:45:34 +0100

calibre (0.9.11+dfsg-1) unstable; urgency=low

  * New upstream release.
  * Add missing python-cssselect dependency.
  * Add python_multiarch_inc.patch: Use python-config instead of
sysconfig.get_python_inc(), as the latter does not work with
multiarch-split include files. (LP: #1094246)

 -- Martin Pitt   Fri, 28 Dec 2012 14:31:49 +0100

calibre (0.9.0+dfsg-1) unstable; urgency=low

  * New upstream release.
  * debian/control, debian/rules: ttf-liberation is no more, move to
fonts-liberation. Thanks to Kan-Ru Chen! (Closes: #674838)
  * debian/c

Bug#736861: Subject: RFS: mathjax/2.2-1~bpo70+1

2014-01-27 Thread Gary Preston

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for a backport of "mathjax" to Wheezy.

This package is a dependency for another backport (Calibre). I've had no
response from the original maintainer in the last 4 weeks so I'm 
proceeding with the backport.


 * Package name: mathjax
   Version : 2.2-1~bpo70+1
   Upstream Author : MathJax (http://www.mathjax.org/contact/)
 * URL : http://www.mathjax.org/
 * License : Apache 2.0/OFL-1.1
   Section : web

It builds these binary packages:

  fonts-mathjax - JavaScript display engine for LaTeX and MathML (fonts)
  fonts-mathjax-extras - JavaScript display engine for LaTeX and MathML
 (extra fonts)
  libjs-mathjax - JavaScript display engine for LaTeX and MathML

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


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

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

  dget -x 
http://mentors.debian.net/debian/pool/main/m/mathjax/mathjax_2.2-1~bpo70+1.dsc


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

Changes since last version in Wheezy (1.1-2):

  mathjax (2.2-1) unstable; urgency=low

  * New upstream release.
  * Make debian/watch generate tarballs with correct extension.
  * Update debian/copyright: bump years, and transfer the copyright
from "Design Science, Inc" to "The MathJax Consortium" (following
upstream).
  * Install localization files and test HTML files.

 -- Dmitry Shachnev   Sun, 26 May 2013 15:07:53 +0400

  mathjax (2.1+20121028-2) unstable; urgency=low

  * Revert the Vcs-Git change, lintian doesn't like that.
  * Mark fonts packages as Multi-Arch: foreign, fixes a lintian warning.
  * Upload to unstable.

 -- Dmitry Shachnev   Thu, 09 May 2013 09:38:36 +0400

  mathjax (2.1+20121028-1) experimental; urgency=low

  * New upstream release.
  * Set Maintainer to myself.
  * Don't build libjs-mathjax-doc, it is now in a separate source.
  * Suggest fonts-stix.
  * Install images directory.
  * Replace current working directory while packing JS files.
  * Update Vcs-Git to point to git.debian.org.
  * Update debian/copyright:
+ Use full text of SIL Open Font License.
+ Use stand-alone header for Apache license.
  * Update debian/watch to the new GitHub URLs (thanks to
Andrew Starr-Bochicchio for the suggestion).
  * Split out the fonts to fonts-mathjax and fonts-mathjax-extras
packages.
  * Restore original compressed files in clean target (not build).
  * Make short descriptions different and a bit shorter.

 -- Dmitry Shachnev   Fri, 21 Dec 2012 16:31:21 +0400

  mathjax (2.0.3-2) experimental; urgency=low

  * Set priority to optional
  * Repack javascript files during build
- Build-depend on yui-compressor and perl
- Add debian/packer directory containing packing scripts
- Add debian/combiner directory containing scripts used for creating
"combined" configs

 -- Dmitry Shachnev   Sat, 25 Aug 2012 18:17:59 +0400

  mathjax (2.0.3-1) experimental; urgency=low

  * New snapshot from upstream git (Closes: #683966)
  * Use xz compression method (Closes: #683963, thanks to Julian Taylor
for the patch)

 -- Dmitry Shachnev   Wed, 08 Aug 2012 19:48:35 +0400

  mathjax (2.0-2) experimental; urgency=low

  * Split out libjs-mathjax-doc package
  * Build docs using python3 version of sphinx and dh_sphinxdoc
  * Update debian/copyright and fix Format URL

 -- Dmitry Shachnev   Thu, 26 Jul 2012 14:39:31 +0400

  mathjax (2.0-1) experimental; urgency=low

  * Set Maintainer to Debian Javascript Maintainers team
  * Add myself to Uploaders
  * New upstream release (Closes: #664673)
  * Clone the docs directory before building docs, to fix build failures
  when building twice in a row
  * Fix search not working in docs
  * Bump Standards-Version to 3.9.3, no changes needed
  * Bump debhelper compatibility level to 9
  * Some minor tweaks to the package description
  * Update debian/watch

 -- Dmitry Shachnev   Mon, 16 Jul 2012 13:37:23 +0400

Regards,
 Gary Preston


--
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/52e6ae18.3050...@mups.co.uk



Re: Help: Bug#733407: maude: FTBFS: surface.yy:63:67: error: 'parseResult' was not declared in this scope

2014-01-27 Thread Niels Thykier
On 2014-01-27 20:30, Andreas Tille wrote:
> Hi,
> 
> does anybody have a clue how to fix this C++ issue?
> 
> Kind regards
> 
>  Andreas.
> 

It is not a C++ issue, but a change in bison you are looking at.  I had
a similar issue with mscgen not too long ago[1].

~Niels

[1] http://packages.qa.debian.org/m/mscgen/news/20131229T131907Z.html




-- 
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/52e6ba54.1010...@thykier.net



Re: Help: Bug#733407: maude: FTBFS: surface.yy:63:67: error: 'parseResult' was not declared in this scope

2014-01-27 Thread Niels Thykier
On 2014-01-27 20:30, Andreas Tille wrote:
> Hi,
> 
> does anybody have a clue how to fix this C++ issue?
> 
> Kind regards
> 
>  Andreas.
> 

It is not a C++ issue, but a change in bison you are looking at.  I had
a similar issue with mscgen not too long ago[1].

~Niels

[1] http://packages.qa.debian.org/m/mscgen/news/20131229T131907Z.html


> - Forwarded message from David Suárez  -
> 
> Date: Sat, 28 Dec 2013 19:10:41 +0100
> From: David Suárez 
> To: sub...@bugs.debian.org
> Subject: Bug#733407: maude: FTBFS: surface.yy:63:67: error: 'parseResult' was 
> not declared in this scope
> X-Debian-PR-Message: report 733407
> X-Debian-PR-Package: src:maude
> X-Debian-PR-Keywords: jessie sid
> X-Debian-PR-Source: maude
> 
> Source: maude
> Version: 2.6-4
> Severity: serious
> Tags: jessie sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20131226 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
>> g++ -DHAVE_CONFIG_H -I. -I. -I../..  -I../../src/Utility 
>> -I../../src/Temporal -I../../src/Interface -I../../src/Core 
>> -I../../src/Variable -I../../src/FullCompiler -I../../src/Higher 
>> -I../../src/CUI_Theory -I../../src/S_Theory -I../../src/NA_Theory 
>> -I../../src/FreeTheory -I../../src/ObjectSystem -I../../src/Mixfix 
>> -I../../src/BuiltIn -I../../src/MSCP10 -I../../src/IO_Stuff 
>> -I../../src/ACU_Persistent -I../../src/ACU_Theory -I../../src/AU_Persistent 
>> -I../../src/AU_Theory -I../../src/Meta -I../../src/3rdParty 
>> -I../../src/FullCompiler -I../../src/StrategyLanguage -D_FORTIFY_SOURCE=2  
>> -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
>> -Werror=format-security -c -o libmixfix_a-surface.o `test -f 'surface.cc' || 
>> echo './'`surface.cc
>> In file included from ../../src/Interface/term.hh:34:0,
>>  from ../../src/Variable/variableTerm.hh:28,
>>  from ../../src/Core/variableInfo.hh:30,
>>  from ../../src/Core/preEquation.hh:30,
>>  from ../../src/Core/rule.hh:28,
>>  from userLevelRewritingContext.hh:34,
>>  from surface.yy:54:
>> ../../src/Core/termSet.hh:35:3: warning: access declarations are deprecated 
>> in favour of using-declarations; suggestion: add the 'using' keyword 
>> [-Wdeprecated]
>>PointerSet::cardinality;
>>^
>> ../../src/Core/termSet.hh:36:3: warning: access declarations are deprecated 
>> in favour of using-declarations; suggestion: add the 'using' keyword 
>> [-Wdeprecated]
>>PointerSet::makeEmpty;
>>^
>> surface.yy: In function 'int yyparse()':
>> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
>> parseResult))
>>^
>> surface.yy:235:6: note: in expansion of macro 'PARSE_RESULT'
>>   PARSE_RESULT = UserLevelRewritingContext::QUIT;
>>   ^
>> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
>> parseResult))
>>^
>> surface.yy:312:6: note: in expansion of macro 'PARSE_RESULT'
>>   PARSE_RESULT = UserLevelRewritingContext::QUIT;
>>   ^
>> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
>> parseResult))
>>^
>> surface.yy:319:10: note: in expansion of macro 'PARSE_RESULT'
>>   PARSE_RESULT = UserLevelRewritingContext::QUIT;
>>   ^
>> surface.yy:573:4: error: expected ';' before '}' token
>> }
>> ^
>> surface.yy:1097:33: error: expected ';' before '}' token
>>  command  : KW_SELECT  { lexBubble(END_COMMAND, 1) }
>>  ^
>> surface.yy:1102:33: error: expected ';' before '}' token
>>| KW_DUMP   { lexBubble(END_COMMAND, 1) }
>>  ^
>> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
>> parseResult))
>>^
>> surface.yy:1490:6: note: in expansion of macro 'PARSE_RESULT'
>>   PARSE_RESULT = UserLevelRewritingContext::RESUME;
>>   ^
>> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
>> parseResult))
>>^
>> surface.yy:1494:6: note: in expansion of macro 'PARSE_RESULT'
>>   PARSE_RESULT = UserLevelRewritingContext::ABORT;
>>   ^
>> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>>  #define PARSE

Bug#719801: Acknowledgement (RFS: roundup/1.5.0-1)

2014-01-27 Thread Bastien ROUCARIES
Le 27 janv. 2014 17:45, "Andrew Starr-Bochicchio"  a écrit :
>
> On Mon, Jan 27, 2014 at 2:04 AM, Bastien ROUCARIES
>  wrote:
> > Le 27 janv. 2014 04:27, "Andrew Starr-Bochicchio"  a
écrit :
> >> On Thu, Oct 17, 2013 at 5:20 PM, Kai Storbeck  wrote:
> >> > I have updated roundup_1.5.0-1 per the 17th of October with a few
> >> > changes after getting feedback by Sebastian Ramacher.
> >>
> >> Hi Kai,
> >>
> >> I came across your package on mentors, and I am interested in
> >> sponsoring it. Though, I ran into a few issues that need to be fixed
> >> first.
> >
> > I have just filled two rc severity bug against your package. Please
close
> > it.
>
> This isn't a particularly useful message. What are the issues you are
> filing bugs about? I see no RC bugs against roundup right now, did you
> really file these bugs? What are their numbers?

Src:roundup #736782

> The minified js files I pointed out only exist on mentors, not in the
> version in the archive. That's the only thing I can guess this is
> about.
>
> -- Andrew Starr-Bochicchio
>
>Ubuntu Developer 
>Debian Developer 
>PGP/GPG Key ID: D53FDCB1


Help: Bug#733407: maude: FTBFS: surface.yy:63:67: error: 'parseResult' was not declared in this scope

2014-01-27 Thread Andreas Tille
Hi,

does anybody have a clue how to fix this C++ issue?

Kind regards

 Andreas.

- Forwarded message from David Suárez  -

Date: Sat, 28 Dec 2013 19:10:41 +0100
From: David Suárez 
To: sub...@bugs.debian.org
Subject: Bug#733407: maude: FTBFS: surface.yy:63:67: error: 'parseResult' was 
not declared in this scope
X-Debian-PR-Message: report 733407
X-Debian-PR-Package: src:maude
X-Debian-PR-Keywords: jessie sid
X-Debian-PR-Source: maude

Source: maude
Version: 2.6-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I. -I../..  -I../../src/Utility -I../../src/Temporal 
> -I../../src/Interface -I../../src/Core -I../../src/Variable 
> -I../../src/FullCompiler -I../../src/Higher -I../../src/CUI_Theory 
> -I../../src/S_Theory -I../../src/NA_Theory -I../../src/FreeTheory 
> -I../../src/ObjectSystem -I../../src/Mixfix -I../../src/BuiltIn 
> -I../../src/MSCP10 -I../../src/IO_Stuff -I../../src/ACU_Persistent 
> -I../../src/ACU_Theory -I../../src/AU_Persistent -I../../src/AU_Theory 
> -I../../src/Meta -I../../src/3rdParty -I../../src/FullCompiler 
> -I../../src/StrategyLanguage -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o 
> libmixfix_a-surface.o `test -f 'surface.cc' || echo './'`surface.cc
> In file included from ../../src/Interface/term.hh:34:0,
>  from ../../src/Variable/variableTerm.hh:28,
>  from ../../src/Core/variableInfo.hh:30,
>  from ../../src/Core/preEquation.hh:30,
>  from ../../src/Core/rule.hh:28,
>  from userLevelRewritingContext.hh:34,
>  from surface.yy:54:
> ../../src/Core/termSet.hh:35:3: warning: access declarations are deprecated 
> in favour of using-declarations; suggestion: add the 'using' keyword 
> [-Wdeprecated]
>PointerSet::cardinality;
>^
> ../../src/Core/termSet.hh:36:3: warning: access declarations are deprecated 
> in favour of using-declarations; suggestion: add the 'using' keyword 
> [-Wdeprecated]
>PointerSet::makeEmpty;
>^
> surface.yy: In function 'int yyparse()':
> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
> parseResult))
>^
> surface.yy:235:6: note: in expansion of macro 'PARSE_RESULT'
>   PARSE_RESULT = UserLevelRewritingContext::QUIT;
>   ^
> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
> parseResult))
>^
> surface.yy:312:6: note: in expansion of macro 'PARSE_RESULT'
>   PARSE_RESULT = UserLevelRewritingContext::QUIT;
>   ^
> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
> parseResult))
>^
> surface.yy:319:10: note: in expansion of macro 'PARSE_RESULT'
>   PARSE_RESULT = UserLevelRewritingContext::QUIT;
>   ^
> surface.yy:573:4: error: expected ';' before '}' token
> }
> ^
> surface.yy:1097:33: error: expected ';' before '}' token
>  command  : KW_SELECT  { lexBubble(END_COMMAND, 1) }
>  ^
> surface.yy:1102:33: error: expected ';' before '}' token
>| KW_DUMP   { lexBubble(END_COMMAND, 1) }
>  ^
> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
> parseResult))
>^
> surface.yy:1490:6: note: in expansion of macro 'PARSE_RESULT'
>   PARSE_RESULT = UserLevelRewritingContext::RESUME;
>   ^
> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
> parseResult))
>^
> surface.yy:1494:6: note: in expansion of macro 'PARSE_RESULT'
>   PARSE_RESULT = UserLevelRewritingContext::ABORT;
>   ^
> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>  #define PARSE_RESULT (*((UserLevelRewritingContext::ParseResult*) 
> parseResult))
>^
> surface.yy:1498:6: note: in expansion of macro 'PARSE_RESULT'
>   PARSE_RESULT = UserLevelRewritingContext::STEP;
>   ^
> surface.yy:63:67: error: 'parseResult' was not declared in this scope
>  #define PARSE_RESULT (*((UserLevelRewritingCon

Bug#719801: Acknowledgement (RFS: roundup/1.5.0-1)

2014-01-27 Thread Andrew Starr-Bochicchio
On Mon, Jan 27, 2014 at 2:10 PM, Bastien ROUCARIES
 wrote:
>> > I have just filled two rc severity bug against your package. Please
>> > close
>> > it.
>>
>> This isn't a particularly useful message. What are the issues you are
>> filing bugs about? I see no RC bugs against roundup right now, did you
>> really file these bugs? What are their numbers?
>
> Src:roundup #736782

That bug seems to be about Src:roundcube. This thread is about
Src:roundup. Similar names, different packages.

Thanks,

-- Andrew Starr-Bochicchio

   Ubuntu Developer 
   Debian Developer 
   PGP/GPG Key ID: D53FDCB1


-- 
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/CAL6k_Ay4jwc14mRX0f_a-P+=aj-sr7lrbbbmssrmpb0ujwe...@mail.gmail.com



Bug#719801: Acknowledgement (RFS: roundup/1.5.0-1)

2014-01-27 Thread Andrew Starr-Bochicchio
On Mon, Jan 27, 2014 at 2:04 AM, Bastien ROUCARIES
 wrote:
> Le 27 janv. 2014 04:27, "Andrew Starr-Bochicchio"  a écrit :
>> On Thu, Oct 17, 2013 at 5:20 PM, Kai Storbeck  wrote:
>> > I have updated roundup_1.5.0-1 per the 17th of October with a few
>> > changes after getting feedback by Sebastian Ramacher.
>>
>> Hi Kai,
>>
>> I came across your package on mentors, and I am interested in
>> sponsoring it. Though, I ran into a few issues that need to be fixed
>> first.
>
> I have just filled two rc severity bug against your package. Please close
> it.

This isn't a particularly useful message. What are the issues you are
filing bugs about? I see no RC bugs against roundup right now, did you
really file these bugs? What are their numbers?

The minified js files I pointed out only exist on mentors, not in the
version in the archive. That's the only thing I can guess this is
about.

-- Andrew Starr-Bochicchio

   Ubuntu Developer 
   Debian Developer 
   PGP/GPG Key ID: D53FDCB1


--
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/cal6k_ax-95el9urdo3cxdtzga2jg6qd6oj1kqab_-tsqotx...@mail.gmail.com



Bug#736839: RFS: sosreport/3.1-1 ITP

2014-01-27 Thread Liang Guo
Hi, Adam,
On Mon, Jan 27, 2014 at 9:16 PM, Adam Stokes  wrote:
> Package: sponsorship-requests
>
>   Severity: normal
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "sosreport"
>
>  * Package name : sosreport
>Version: 3.1-1
>Upstream Author   : Adam Stokes
>  * URL : https://github.com/sosreport/sosreport
>  * License: GPL-2
>Section : admin
>
>   It builds those binary packages:
>
> sosreport  - Set of tools to gather troubleshooting data from a system
>

The latest standards version is 3.9.5, please bump to it.

Before uploading packages, you'd better use lintian and lintian4py to
check them, it can help you to find potential problems in your
package.

Thanks,
-- 
Liang Guo
http://guoliang.me/


-- 
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/cajwrgw7m04fscs6h2cxtfbwc_r0f0re5dzzwdt7ecg_sd_y...@mail.gmail.com



Bug#736839: RFS: sosreport/3.1-1 ITP

2014-01-27 Thread Adam Stokes
Package: sponsorship-requests

  Severity: normal

  Dear mentors,

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

 * Package name : sosreport
   Version: 3.1-1
   Upstream Author   : Adam Stokes
 * URL : https://github.com/sosreport/sosreport
 * License: GPL-2
   Section : admin

  It builds those binary packages:

sosreport  - Set of tools to gather troubleshooting data from a system

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

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


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

dget -x 
http://mentors.debian.net/debian/pool/main/s/sosreport/sosreport_3.1-1.dsc

  More information about hello can be obtained from
https://github.com/sosreport/sosreport.

  Changes since the last upload:

sosreport (3.1-1) sid; urgency=low

  * New upstream release v3.1
Features include:
- Full Python 3 support
- Further modularized openstack plugins
  * debian/rules:
- Use pybuild
  * debian/control:
- Use X-Python-Version: >= 3.3

 -- Adam Stokes   Wed, 15 Jan 2014 16:58:54 -0500



  Regards,

Adam Stokes


-- 
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/cakorv6xzxxy+9zgpqb1u12ujbvqqm8anppmacdyuv2tz73u...@mail.gmail.com



Bug#736288: RFS: libnftnl/1.0.0-1 [ITP]

2014-01-27 Thread Arturo Borrero Gonzalez
On 27 January 2014 03:13, Neutron Soutmun  wrote:
> Hello,
>
> FYI, as of the devscripts 2.14.0 [1] the keyring location for
> signature verification has been moved to debian/upstream/.
>

Thanks,

regards.

-- 
Arturo Borrero González


--
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/caoksjbjnryz6g-ordrirkbcentwmt3x5jqj3mohqjeraw8o...@mail.gmail.com



Bug#736671: RFS: asused/3.72-11 [ITA]

2014-01-27 Thread Raoul Bhatia

On 27.01.2014 02:03, Paul Wise wrote:

On Mon, 2014-01-27 at 01:44 +0100, Sebastien Badia wrote:


Therefore we do anything with this package? RoQA anyway?


Thanks for the explanation, it sounds like this package should remain in
Debian instead of being removed, good luck with finding a sponsor.


I also find asused a valuable tool for analyzing autonomous systems
other than the ones i have lir-portal-access to.

Cheers,
Raoul
--
DI (FH) Raoul Bhatia M.Sc. |   E-Mail.  ra...@bhatia.at
Software Development and   |   Web. http://raoul.bhatia.at/
System Administration  |   Tel. +43 699 10132530


--
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/52e61e6b.3040...@bhatia.at



Bug#736085: RFS: doublecmd/0.5.8-1 -- twin-panel (commander-style) file manager

2014-01-27 Thread Graham Inggs

Hi Paul

On 24/01/2014 11:42, Paul Gevers wrote:

Interesting that I have missed this the first time that you did this
work. Funny thing is that we are trying to get things related to
FreePascal into one team, so I invite you to have a look at pkg-pascal
on Alioth.


I'd be happy to maintain doublecmd and doublecmd-help packages as part 
of the pkg-pascal team.



Furthermore, there is a package called tuxcmd, which is also a
twin-panel file manager and also written in FreePascal. doublecmd
wouldn't be a fork of that project (which has stalled upstream)?


I checked with upstream and doublecmd is not a fork of tuxcmd, but 
rather a fork of Seksi Commander [1].
I believe the visual similarity of doublecmd and tuxcmd is simply due to 
them both being inspired by Total Commander and Midnight Commander.



If upstream of doublecmd is really active, maybe we should drop tuxcmd
altogether (it is orphaned). If we do, maybe we could help people
migrate in the next release by handling this properly.


Would/could we do this even if doublecmd is not a fork of tuxcmd?


Could you investigate (if you have the time of course) if tuxcmd has
features that are still lacking in doublecmd?


Is this still required, seeing that doublecmd is not a fork of tuxcmd?

Regards
Graham


[1] http://netcode.cz/projects/seksicmd/


--
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/52e60f8f.70...@nerve.org.za