Re: Multiarch and architecture specific headers

[Boris Pek]

Hi Thomas,

> I am looking for a solution to fix the following bug:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707754
>
> A package I maintain contains a configuration header (vpConfig.h)
> which differ depending on the architecture we are (here the dependencies are
> not the same on i386 and powerpc).
>
> So far, the only solution I can think of is moving this header into
> /usr/include/
> and patching the .pc file accordingly.
>
> I saw that some packages are already putting headers in this directory
> but I never
> heard of this strategy on the Debian wiki.
>
> Is this considered good practice? Is there another solution to deal
> with this bug?

I think you are searching for these links:
http://wiki.debian.org/Multiarch/TheCaseForMultiarch
http://wiki.debian.org/Multiarch/LibraryPathOverview
https://wiki.ubuntu.com/MultiarchCross

Best wishes,
Boris


-- 
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/1483141368430...@web11e.yandex.ru

Bug#707580: Re[2]: RFS: hyphen-ru/20030310-1 [ITP]

[Eriberto]

Ok Ilyas! You need a sponsor to upload the package.
You should wait now.

Best regards,

Eriberto

2013/5/13 Ильяс Гасанов :
> On Thu, 9 May, 2013 at 18:21:30 -0300, Eriberto wrote:
> Hello and thank you.
>
> Done, now lintian displays that the package is clean. However, the
> upstream distribution has no changelog at all so I had to analyze all
> the previous versions released and write it myself. Also, it would be
> rather good if the "description too short" warning was cleaned from most
> other hyphen-XX packages already in repository as well. Ideally, I think
> their descriptions should be uniform.
>
> By the way, I'm running lintian on my machine as:
>
> lintian -vEL ">=pedantic/wild-guess"
> .changes
>
> So it basically does show the same messages with a few more.
>
> Regards,
>
> Ilyas


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

Bug#707580: Re[2]: RFS: hyphen-ru/20030310-1 [ITP]

[Andrew Shadura]

Hi,

On 13 May 2013 11:27, Ильяс Гасанов  wrote:
> Done, now lintian displays that the package is clean. However, the
> upstream distribution has no changelog at all so I had to analyze all
> the previous versions released and write it myself. Also, it would be
> rather good if the "description too short" warning was cleaned from most
> other hyphen-XX packages already in repository as well. Ideally, I think
> their descriptions should be uniform.

You don't need to write a changelog, it's an upstream issue. I'd not
care at all, it's their decision, and it's not something totally wrong
that urgently needs fixing.

-- 
WBR, Andrew


--
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/CAMb-mAzuT-o6YU=YzOf4KaNzRNhiB2nR9ik3kfxMM_dsyOu=y...@mail.gmail.com

Bug#697142: marked as done (RFS: libgetoptionkit-php/1.2.1-1 [ITP] - CLI option parser for PHP)

[Debian Bug Tracking System]

Your message dated Mon, 13 May 2013 16:23:07 +
with message-id 
and subject line closing RFS: libgetoptionkit-php/1.2.1-1 [ITP] - CLI option 
parser for PHP
has caused the Debian Bug report #697142,
regarding RFS: libgetoptionkit-php/1.2.1-1 [ITP] - CLI option parser for PHP
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.)


-- 
697142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libgetoptionkit-php"

 * Package name: libgetoptionkit-php
   Version : 1.2.1-1
   Upstream Author : Yo-An Lin 
 * URL : https://github.com/c9s/GetOptionKit
 * License : GPL v3
   Section : php

It builds those binary packages:

libgetoptionkit-php - Commandline options parser for PHP 5.3.

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


  http://mentors.debian.net/package/libgetoptionkit-php


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

dget -x 
http://mentors.debian.net/debian/pool/main/libg/libgetoptionkit-php/libgetoptionkit-php_1.2.1-1.dsc



This is the best maintained option parser for PHP I've found - and I 
will need it as a dependency for other PHP package.


I am a DM and would like to get the appropriate DM upload permission set 
at some point.


Regards,
Tomasz Muras
--- End Message ---
--- Begin Message ---
Package libgetoptionkit-php has been removed from mentors.--- End Message ---

Re: Advice on packaging SWIG generated python bindings and more

[Anton Gladky]

Hi Srećko,

the package looks ok for me. Just a couple of notes:
1) Please, add "--parallel" to dh to get a faster building.
2) Is it difficult to add some kind of auto-test? Better to add one more
target into makefile (you patch it anyway), so it can be picked up by
dh_autotest.
3) Do you plan to add some more binaries (java-libaria or something
like that)? After adding a binary to an existing package, it should go
to new queue. So if you are planning to add something else, please do it
now not to bother ftp-master to look at your package after each upload.

When you are ready, no need to upload a package to mentors. I can take
it from VCS.

Cheers,

Anton

On 05/08/2013 11:32 AM, Srećko Jurić-Kavelj wrote:
> Dear mentors, Anton,
> 
> I've recently updated my package "libaria"
> 
>  * Package name: libaria
>Version : 2.7.5.2-3
>Upstream Maintainer : Reed Hedges 
>  * URL : http://robots.mobilerobots.com/wiki/ARIA
>  * License : GPL-2
>Section : libs
> 
>   It builds those binary packages:
> 
>   libaria-demo - C++ library for MobileRobots/ActivMedia robots (demo example)
>   libaria-dev - C++ library for MobileRobots/ActivMedia robots (devel)
>   libaria-dev-doc - C++ library for MobileRobots/ActivMedia robots (devel 
> docs)
>   libaria2 - C++ library for MobileRobots/ActivMedia robots
>   python-libaria - C++ library for MobileRobots/ActivMedia robots
> (Python bindings)
> 
>   To access further information about this package, please visit the following
>   URL:
> 
>   http://mentors.debian.net/package/libaria
> 
> 
>   Alternatively, one can download the package with dget using this command:
> 
> dget -x 
> http://mentors.debian.net/debian/pool/main/liba/libaria/libaria_2.7.5.2-3.dsc
> 
>   Changes since the last upload:
> 
>   * Removed statically linked library.
>   * Corrected Multi-Arch config for the doc package.
>   * Building python-libaria package (SWIG generated bindings)
>   * Building libaria-demo package
> 
> I've named the python package python-libaria, but the packaged module
> is named AriaPy. Debian Python Policy states that the package name
> should be the module name prefixed by python-, but on the other hand,
> package names should be lower case (Debian Policy). Compromise would
> be python-ariapy, but it seems redundant.
> 
> Also, I've added only the default python version to Build-Depends.
> Hope this is OK.
> 
> Furthermore, I've packaged an example binary using the library in a
> separate package (because of the Multi-Arch support). I've renamed it
> from demo to aria-demo.
> 
> And last, libaria-dev-doc packages CPP examples for using the library.
> I've also provided a Makefile there, that builds those examples in
> /tmp (default).
> 
> PS I've tried to build the package in squeeze environment (for
> backporting), and while it did succeed after adding backports
> repository (for debhelper, lintian, ...), python package wasn't
> correctly generated (uses dh_python2). Also, lintian complained about
> Hardening, which should be handled by the backported debhelper 9,
> right? Anyway, even if I do succeed in generating the package for
> squeeze, would it be of any good (since I've locally added backports
> to my squeeze environment).
> 
> Best regards,
> 
> Srećko Jurić-Kavelj, dipl.ing. (Ms.E.E)
> Research and Teaching Assistant at University of Zagreb
> (Faculty of Electrical Engineering and Computing, Department of
> Control and Computer Engineering)
> 
> Phone: +385 (0)1 6129 529
> Fax: +385 (0)1 6129 809
> E-mail: srecko.juric-kav...@fer.hr
> URL: http://www.fer.hr/srecko.juric-kavelj
> 
> Sanctus Hieronymus: "Parce mihi, Domine, quia dalmata sum!"
> 




signature.asc
Description: OpenPGP digital signature

Re: Multiarch and architecture specific headers

[Russ Allbery]

Thomas Moulard  writes:

> A package I maintain contains a configuration header (vpConfig.h) which
> differ depending on the architecture we are (here the dependencies are
> not the same on i386 and powerpc).

> So far, the only solution I can think of is moving this header into
> /usr/include/
> and patching the .pc file accordingly.

There should be no need to modify the *.pc file.  (Indeed, I think that
would be incorrect.)  /usr/include/ is part of the default search
path for the compiler for exactly this purpose.

> I saw that some packages are already putting headers in this directory
> but I never heard of this strategy on the Debian wiki.

That's mostly because multiarch for -dev packages isn't really
well-documented yet.  But I believe this is the right approach.

-- 
Russ Allbery (r...@debian.org)   


-- 
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/87vc6me5ut@windlord.stanford.edu

CFLAGS/CPPFLAGS/LDFLAGS

[Nathan Owens]

I get W-dpkg-buildflags-missing|CPPFLAGS 25 (of 25), CFLAGS 25 (of 25), 
LDFLAGS 25 (of 25) missing|
 when I do blhc --build and I was wondering how to get the CPPFLAG. I 
tried overriding auto build  and do make CFLAGS+=$(shell dpkg-buildflags 
--get CFLAGS) and same with CPPFLAGS but it still doesn't work.


I tried also just setting CFLAGS and CPPFLAGS in debian/rules but it 
gives no results



--
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/51915333.9050...@gmx.us

Re: CFLAGS/CPPFLAGS/LDFLAGS

[Paul Wise]

Please show us your debian/rules file and a full build log with
DH_VERBOSE=1 set.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
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/caktje6fxoju5bcr71cuoq3btr6yjhb5qgquurt6c+uvfz3i...@mail.gmail.com

Re: need a mentor.

[Aníbal Monsalve Salazar]

On Sun, May 12, 2013 at 10:02:55PM -0700, Vincent Cheng wrote:
>Please upload your package on mentors.debian.net and/or provide a link
>to your .dsc, [...]

http://mentors.debian.net/debian/pool/main/a/aafigure/aafigure_0.5-3.1.dsc


-- 
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/20130514020759.ga4...@master.debian.org

Re: Bug#706361: gti review

[Felix Crux]

Hello,

Thank you very much for the detailed review of the package. I've taken some
time to address your feedback, as well as share some improvements upstream.

You can get the latest version of the package with
  dget -x http://mentors.debian.net/debian/pool/main/g/gti/gti_1.1.0-1.dsc
(note the version change)

Or you can browse the packaging work repository at
  https://gitorious.org/deb-packaging/gti-deb-packaging
or
  https://github.com/felixc/gti-deb-packaging

Some inline point-by-point responses to your comments:

> There is unnecessary lintian-override for "no-upstream-changelog".
> Please remove it.

Removed. I take it it is not customary to provide overrides for "pedantic"
warnings?

> By the way why you didn't forward man page upstream yet?

No reason, I was just focusing on getting the packaging work done. I have
now forwarded the man page upstream, where it has been accepted. The updated
package now reflects that.

> Package version looks a little bit unconventional. Although it's not a
> problem I would suggest to use just version "1.0.4-1" and backport
> patches from unreleased upstream commits if necessary.

Yes, I was very uncertain about the version number. I consulted with an
acquaintance who is a Debian Maintainer, and he suggested the format
incorporating the git commit hash and date. In any case, upstream has bumped
the version number, and I am now using the new version directly, so the
problem has gone away.

> ## debian/watch

Thanks to the new upstream version, debian/watch now works properly.

> debian/rules contains unnecessary comments (dm-make template
> remnants?) -- please consider removing 'em.

Removed!

> To save some space you might want to compress .deb file with xz
> instead of gz.

Changed! Thanks for this info, I hadn't seen any documentation on this
option, but it makes a lot of sense, so I'm glad to know about it now.

> License name "MIT" is incorrect even though upstream may refer to this
> license as such. "MIT" is considered ambiguous by the Free Software
> Foundation.

Yes, I saw that, which is why I included the full license text. I assumed
that would disambiguate it. Does the "ambiguous" designation mean that the
name "MIT" should simply not be used? I have changed it to "MIT Old Style".

> Priority "extra" is probably better changed to "optional"

Good point; I re-read the policy details on priorities and now agree with
the "optional" level.

> IMHO "Suggests: sl" is incorrect because it suggests unrelated package.
> I would replace it with "Enhances: git".

I again went back to re-read the documentation on this, and now can see
why Enhances is the better choice. Updated.

> Versioned build-depends on "dpkg-dev (>= 1.16.1~)" is unnecessary and
> may be completely dropped.

I suspected this might be the case, but wasn't sure. Removed.

> Specifically I think it is a good practice to maintain "Forwarded" and
> "Last-Update" headers.

All patches now have these.

> debhelper 9 in compat 9 mode automatically export build flags which
> makes unnecessary to include "/usr/share/dpkg/buildflags.mk" or set
> "DPKG_EXPORT_BUILDFLAGS" as we used to do with dh 8 to import
> hardening flags.

Oh, that's excellent. It certainly makes the Makefile much cleaner. I have
also forwarded the relevant Makefile changes upstream.

Again, thank you for your review. I appreciate all the information you've
shared, and I think the package is much improved after these changes.

All the best,

Felix



signature.asc
Description: Digital signature

Bug#708203: RFS: libcidr/1.2 [ITP] -- IPv4 and IPv6 address parsing and manipulation library

[Daniil Baturin]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "libcidr":

* Package name: libcidr
  Version: 1.2
  Upstream Author: Mathew Fuller
* URL: http://www.over-yonder.net/~fullermd/projects/libcidr
* License: BSD
  Section: contrib/libs

It builds those binary packages:

libcidr0 - IPv4 and IPv6 manipulation library
libcidr0-dev - Development headers, documentation and examples for 
libcidr


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


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


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


  dget -x 
http://mentors.debian.net/debian/pool/contrib/libc/libcidr/libcidr_1.2+nmu1.dsc 



  More information about libcidr can be obtained from 
http://www.over-yonder.net/~fullermd/projects/libcidr


  Changes since the last upload:

Initial release (Non-maintainer upload). (Closes: #702773)


  Regards,
  Daniil Baturin


--
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/5191ba47.3080...@baturin.org

Re: Bug#708203: RFS: libcidr/1.2 [ITP] -- IPv4 and IPv6 address parsing and manipulation library

[Nicholas Breen]

On Tue, May 14, 2013 at 11:15:03AM +0700, Daniil Baturin wrote:
>   Changes since the last upload:
> 
> Initial release (Non-maintainer upload). (Closes: #702773)

If you intend to be the maintainer of this package, why are you uploading it as
a NMU?  The package appears to list the upstream libcidr maintainer as the
package maintainer instead of yourself, which is (presumably) not correct;
these are two different things.

Please review the list of lintian warnings and correct them if possible.


-- 
Nicholas Breen
nbr...@debian.org


-- 
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/20130514044654.gp30...@ofb.net

Re: CFLAGS/CPPFLAGS/LDFLAGS

[Andrey Rahmatullin]

On Mon, May 13, 2013 at 08:55:15PM +, Nathan Owens wrote:
>  when I do blhc --build and I was wondering how to get the CPPFLAG.
> I tried overriding auto build  and do make CFLAGS+=$(shell
> dpkg-buildflags --get CFLAGS) and same with CPPFLAGS but it still
^^
CPPFLAGS

-- 
WBR, wRAR


signature.asc
Description: Digital signature

Bug#707674: marked as done (RFS: gcc-4.8-doc/4.8.0-1 [ITP])

[Debian Bug Tracking System]

Your message dated Tue, 14 May 2013 04:22:43 +
with message-id 
and subject line closing RFS: gcc-4.8-doc/4.8.0-1 [ITP]
has caused the Debian Bug report #707674,
regarding RFS: gcc-4.8-doc/4.8.0-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.)


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

Dear mentors,

  I am looking for a sponsor for my package gcc-4.8-doc, with is based
on gcc-4.7-doc, also maintained by me. A git repo was set up to track
the packaging work[1].

[1] http://anonscm.debian.org/gitweb/?p=users/yixuan-guest/gcc-doc.git

 * Package name: gcc-4.8-doc
   Version : 4.8.0-1
   Upstream Author : FSF
 * URL : http://gcc.gnu.org
 * License : GFDL-1.3+, with invariant sections
   Section : doc

  It builds those binary packages:

 cpp-4.8-doc - documentation for the GNU C preprocessor (cpp)
 gcc-4.8-doc - documentation for the GNU compilers (gcc, gobjc, g++)
 gccgo-4.8-doc - documentation for the GNU Go compiler (gccgo)
 gcj-4.8-doc - documentation for the GNU Java tools (gcj, gij)
 gfortran-4.8-doc - documentation for the GNU Fortran Compiler (gfortran)
 gnat-4.8-doc - documentation for the GNU Ada 95 Compiler (gnat)

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

  http://mentors.debian.net/package/gcc-4.8-doc

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

dget -x
http://mentors.debian.net/debian/pool/non-free/g/gcc-4.8-doc/gcc-4.8-doc_4.8.0-1.dsc

  Changes since the last upload:

 gcc-4.8-doc (4.8.0-1) unstable; urgency=low
 .
   * New upstream branch. (Closes: #707673)
   * debian/patches:
 - Synced patches with gcc-4.8, 4.8.0-5.
 - Dropped alpha-ieee-doc-clarification.diff and gccgo-direntry.diff,
   which is already in from-debian-gcc-alpha-ieee-doc.diff and
   from-debian-gcc-rename-info-files.diff.
 - Refreshed fix-direntry.diff.
 - fix-value-gcc.diff to correct variable names.
   * debian/control:
 - start building gnat-4.8,
 - stop building gcc-doc-base
 - Removed Samuel from uploaders.

Many thanks,

GUO Yixuan
--- End Message ---
--- Begin Message ---
Package gcc-4.8-doc version 4.8.0-1 is in NEW now,
and the package at mentors is not newer (2013-05-10) than the package in NEW 
(2013-05-10),
so there is currently no package to sponsor.

http://ftp-master.debian.org/new/gcc-4.8-doc_4.8.0-1.html
http://mentors.debian.net/package/gcc-4.8-doc

Please remove the package from mentors or mark it "needs sponsor = no".
If for some reason you need to replace the package in NEW,
then you can upload an updated package to mentors
and feel free to reopen this RFS 707674 or open a new RFS.--- End Message ---