Re: packaging with cmake
Hi Jerome, On 14 April 2015 19:47:57 BST, Jerome BENOIT g62993...@rezozer.net wrote: Hello List, II am on my way to package normaliz [1] which can be built either with ready to use Makefile or with cmake. Since the cmake setup is the one advised by the upstream team (while on the other hand the furnished Makefile may need refreshment), I will first give a try to the cmake machinery. So I am looking for a well debiannized software that builts with cmake: any idea ? The latest version of Dynamips (in non-free) builds using CMake. -- Daniel Lintott -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/59563ae0-ed48-4907-bd72-4126ade50...@serverb.co.uk
Bug#770149: python-instagram
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11 April 2015 18:56:15 BST, Ross Gammon r...@the-gammons.net wrote: - The watch file is not working, but that is okay as upstream do not do releases or tags. It appears they make releases to pypi [1]. So that may be an option to use for the watch file as 1.3.0 appears to be the latest version anyway. [1] https://pypi.python.org/pypi/python-instagram - -- Regards, Daniel Lintott -BEGIN PGP SIGNATURE- iQJOBAEBCAA4MRxEYW5pZWwgTGludG90dCAoZGxpbnRvdHQpIDxkYW5pZWxAc2Vy dmVyYi5jby51az4FAlUpbbYACgkQyHJk111z7G4/xw/7B7uUv4TdaJWjP9Gyty3A GEg0hDshmajJ3+w5fDo5aieDlLUXXWDiRZlH8oEfIy7unEh/EpPBihQ5bDJfBszr Lg7L/00jG6vF7yOWMfbeOAnReN1GpvCcB065GyUEUvstImnZEMvbM4dcEmlhW4Qo 4a3zJKUGJy2lsHSA6wQrRfJlUEwRk0vPR6THpCsOBkNzfH+QolRFY0zpKkM4XJgy unhZpWTZGIdNHWksIXqihKuIcuFG/ABGe2mJlUrbiVMT1+vM6dPu5XJ55+uEU+Pv f+6WBlsiXnHLlpAHvpbliQ9zMCtV/M6TFU2jyrzUXF8E/CVmO4dUkqELN0Hj11IE Fdf7iPmFAhSv4tBfXamVCZtcvltyJ0dmMhaGMTQwr5vLherkHZ3cL+UPkpwB9+8H WmDBAXeBdfgtaSiCqb+WQSZ+MLA0HxJSmGV5aIYTfjPtZvBOnfGb1NXxWTwO6BmH I5h6EHAiEsvcC7yp1itUvistdoYcnHpa/1KvMlOHf2lh3tfMSorFZZ7iroDpW29g r/f8Fk2SLIiUwErT1BvJRrVwXMstFkJjvkZUu19J3jk92hTBl7IenGkhQzofs4qQ S5ZCVJjhKF7ZVbwZ+ujZ6xJregZPX03tNDvjweNEbFlc/uXV+nPyUed5y+h8dDpY DlGbYX4PCZQNBkhybrgAlQY= =rjQ7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/f73c2d69-ab0a-4bcf-aa3d-f67871288...@serverb.co.uk
Re: dep5-copyright-license-name-not-unique
Hi Helge, On Tue, Mar 03, 2015 at 03:59:31PM +0100, Helge Kreutzmann wrote: For goobox, the list of improper paragraph starts with: (paragraph at line 25) (paragraph at line 66) (paragraph at line 84) (paragraph at line 102) (paragraph at line 128) (paragraph at line 171) (paragraph at line 185) (paragraph at line 201) (paragraph at line 217) Looking at debian/copyright yields: 25: second use of GPL-2+ 66: Before third use of GPL-2+ 84: Before fourth use of GPL-2+ 102: Before fith use of GPL-2+ I attached my complete debian/copyright. Thanks for any pointers, ideas, mistakes. You don't need to duplicate the License text multiple times. You can simply specify the License field for the files covered by the license in question. For example: Files: debian/* Copyright: 2013-2014, Daniel Lintott dan...@serverb.co.uk License: GPL-2.0+ Then specify the license text seperately. License: GPL-2.0+ This package is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. [SNIP] Hope that helps, Daniel -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150303151813.ga6...@mail.serverb.co.uk
Re: Seeking help with submission of package
Hi Dave, On 11/01/15 14:04, Dave Maiorino wrote: Hello Daniel, Thanks for the quick reply! Looks like there is still some work that needs to be done ;) Thank you for the pointers, I need to go back and clean-up more. I have submitted to Pypi a while back, but have not kept that package up-to-date. No problem... Obviously from a user perspective having two different versions both of which look current would be very confusing. Also making sure all sources are upto date eases the job of a maintainer though obviously this doesn't apply as much since you're upstream. For starters, I will go ahead and submit the RFS. I will need a little more time to get the corrections in. In this case, is it better to follow-up with the RFS, or use this email thread instead? With revisions and corrections, are these usually tracked in the RFS? It is much better to follow up in the RFS bug, so the sponsoring process is logged in the BTS. A sponsor may also then like to mark the RFS bug as owned (or set other tags) to track the package state. Thanks again! No problem! Best of luck getting you package into Debian. Cheers, Daniel signature.asc Description: OpenPGP digital signature
Re: Seeking help with submission of package
Hi Dave,
NB: I'm not a DD, so cannot sponsor your package but I'll shall do my
best to give it a good review.
It would be great if you could file an RFS bug to track the sponsorship
of this package (https://mentors.debian.net/sponsors/rfs-howto)
On 10/01/15 12:24, Dave Maiorino wrote:
Hello Debian Mentors,
I apologize for the wide email, but I was looking for help with getting
my package submitted into the Debian repo.
You've come to the right place!
https://mentors.debian.net/package/tz-converter
Last year, I have received great help with correcting this package and
making it ready for building. I am wondering if there is anything else I
can do to help get this application submitted. The code is quite simple,
using Python3 and PySide to provide a GUI for time zone conversation.
If there is anything else I can help provide, please let me know. Thank
you!
Well here goes...
Checking on pypi[1], I can see you have a version 1.0.3 there but your
Github repository contains only version 1.0.0? Which is correct/latest?
Also using a source tarball generated by setuptools (python3 setup.py
sdist), will ensure the tarball doesn't contain any cruft eg:
- .git/
- .idea/ (I'd advise removing this from Git entirely as it creates
enormous diffs, add it to your .gitignore)
- .pc/
Currently the md5sum of the orig.tar.gz doesn't match the version 1.0.0
tarball from GitHub either. The source tarball uploaded to Debian should
be byte identical to the upstream source.
5acf31423683a9491c96fbf472e3e965 tz-converter_1.0.0.orig.tar.gz
c498a0d95301c8201b760751e0c420d0 tz-converter-tz-converter-1.0.0.tar.gz
debian/changelog:
- As this is the first release in Debian the version should
$UPSTREAM_VERSION-1 (e.g 1.0.0-1)
- The initial changelog for Debian should then contain just one entry
for the initial version stating:
* Initial release (closes: #754287)
- For the regular upload to Debian the package should always target
unstable (generally) as opposed to stable.
debian/control:
- You have a dependency on python-dateutil, I think that should be
python3-dateutil
- Drop the depends on python3, this will be automatically added by the
${python3:Depends} variable
- Long description has a spelling error: taked - taken
debian/copyright:
- Missing the Copyright header:
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: tz-converter
Source: YOUR_SOURCE_URL
debian/install:
- Use dh_installman to install the manpage
debian/py3dist-overrides:
- You can drop this file
debian/rules:
- Remove pointless comments
- Remove override_dh_auto_configure ???
- Remove override_dh_python3 ???
- Remove the clean target
debian/watch:
- Depending on my first comment, you may like to use pypi in the watch
file. This will also allow you to PGP sign the releases, which can then
be verified in the Debian package
As you are also upstream, you can easily fix the Lintian
no-upstream-changelog tag, by simply writing a CHANGELOG and placing it
in the source package.
Distutils also spits out a warning during the build process
running install_egg_info
Writing debian/tz-converter/usr/share/tz-converter/tz_converter-1.0.0.egg-info
/usr/lib/python3.4/distutils/dist.py:260: UserWarning: Unknown distribution
option: 'install_requires'
warnings.warn(msg)
I hope that helps, feel free to ask any questions and I'll do my best to
help you out.
Regards,
Daniel Lintott
[1] https://pypi.python.org/pypi/tz-converter
signature.asc
Description: OpenPGP digital signature
Re: FTBFS on powerpc/ppc64el
Hi Everyone! I'm back working on this problem again... On 20/10/14 11:55, Etienne Millon wrote: * Daniel Lintott dan...@serverb.co.uk [141020 12:38]: Okay.. that points me in the direction of the the common/dynamips_common.h line 83 [1]. #ifndef _unused /* Function that is never used */ #define _unused __attribute__((unused)) #endif Any ideas on where to go from here? Hi, I think that you can patch utils.h (and possibly other dynamips headers) so that it includes dynamips_common.h only after loading system includes (not tested). That way _unused will be undefined at the time sigcontext.h is included. So I have moved all the dynamips_common.h includes to after the system includes and got a lot further but have hit the error again later on in the build :( commit b4daab223d4d3d35075cd7d5290bb5e72f99b522 Author: Daniel Lintott dan...@serverb.co.uk Date: Mon Oct 27 17:31:44 2014 + Import dynamips_common.h after importing system headers :100644 100644 fd06b39... 466ff40... M common/dev_vtty.c :100644 100644 090e772... 1640b73... M common/net.h :100644 100644 7b52845... ef04385... M common/net_io.c :100644 100644 20a3645... 732bd78... M common/utils.c :100644 100644 86309b9... 006bad6... M stable/hypervisor.c :100644 100644 4e5a8b0... 9f4a294... M stable/utils.h :100644 100644 10ecfbb... 9447cb0... M unstable/hypervisor.c :100644 100644 9305935... 4109169... M unstable/utils.h And the build error I now hit: In file included from /usr/include/powerpc-linux-gnu/bits/sigcontext.h:28:0, from /usr/include/signal.h:339, from /home/daniel/workspace/dynamips/stable/utils.h:11, from /home/daniel/workspace/dynamips/common/dev_vtty.c:29: /usr/include/powerpc-linux-gnu/asm/sigcontext.h:17:23: error: expected identifier or ‘(’ before ‘[’ token (Though it is also quite bad that _unused is in global scope in the first place IMHO.) Can anyone elaborate on this? I understand the what is being said here, but my C skills aren't at that level! Can the scope be changed, so it's not in the global scope... or would it be a matter of choosing a different name for that definition. Cheers Daniel signature.asc Description: OpenPGP digital signature
Re: FTBFS on powerpc/ppc64el
On 06/12/14 13:43, Daniel Lintott wrote: Hi Everyone! I'm back working on this problem again... [...] (Though it is also quite bad that _unused is in global scope in the first place IMHO.) Can anyone elaborate on this? I understand the what is being said here, but my C skills aren't at that level! Can the scope be changed, so it's not in the global scope... or would it be a matter of choosing a different name for that definition. Okay after some trial and error, I have found the solution. I have renamed the re-definition of _unused to _Unused. The build now passes successfully! :) Regards, Daniel signature.asc Description: OpenPGP digital signature
Bug#771361: RFS: roxterm/2.9.5-1
Hi Tony, On 28/11/14 19:35, Tony Houghton wrote: I have also posted an unblock request which is #771358. Should I merge these two bugs? Keep the sponsorship and unblock requests separate as they are two separate items, handled by different people. Regards Daniel signature.asc Description: OpenPGP digital signature
Bug#771232: RFS: gns3/0.8.7-2 [RC]
Package: sponsorship-requests Severity: important X-Debbugs-CC: and...@shadura.me Dear mentors, I am looking for a sponsor for my package gns3 * Package name: gns3 Version : 0.8.7-2 Upstream Author : Jeremy Grossmann * URL : http://www.gns3.com * License : GPL-2+ Section : net It builds those binary packages: gns3 - Graphical Network Simulator To access further information about this package, please visit the following URL: http://mentors.debian.net/package/gns3 Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/contrib/g/gns3/gns3_0.8.7-2.dsc More information about gns3 can be obtained from http://www.gns3.com. Changes since the last upload: gns3 (0.8.7-2) unstable; urgency=medium * Do not install files needed by the program to /usr/share/doc (Closes: #771135) * Add dh-python to build-depends -- Daniel Lintott dan...@serverb.co.uk Thu, 27 Nov 2014 19:56:04 + I am aware that the standards version is still at 3.9.5, I haven't changed this due to needing an unblock from release team (see bug #771230) Regards, Daniel Lintott signature.asc Description: OpenPGP digital signature
Bug#771232: RFS: gns3/0.8.7-2 [RC]
FTR... The unblock request has just been approved by the release team pending the upload of this package Regards Daniel signature.asc Description: OpenPGP digital signature
Re: Bug#771232: RFS: gns3/0.8.7-2 [RC]
Control: tags 771232 - moreinfo
Hi Sebastian
On 27/11/14 21:09, Sebastian Ramacher wrote:
[...]
This does not seem to be the correct fix. Now it does not install at
all:
Setting up gns3 (0.8.7-2) ...
Error: The new file /usr/share/doc/gns3/gns3.ini does not exist!
dpkg: error processing package gns3 (--configure):
This file is still mentioned in debian/ucf. Did you forget to update
that reference?
I had indeed missed that... despite noting I needed to update it!
New package should be appearing on mentors shortly.
I've also attached the updated debdiff
Regards
Daniel
diff -Nru gns3-0.8.7/debian/changelog gns3-0.8.7/debian/changelog
--- gns3-0.8.7/debian/changelog 2014-07-08 17:30:56.0 +0100
+++ gns3-0.8.7/debian/changelog 2014-11-27 21:10:44.0 +
@@ -1,3 +1,11 @@
+gns3 (0.8.7-2) unstable; urgency=medium
+
+ * Do not install files needed by the program to /usr/share/doc
+(Closes: #771135)
+ * Add dh-python to build-depends
+
+ -- Daniel Lintott dan...@serverb.co.uk Thu, 27 Nov 2014 19:56:04 +
+
gns3 (0.8.7-1) unstable; urgency=medium
* Imported Upstream version 0.8.7
diff -Nru gns3-0.8.7/debian/control gns3-0.8.7/debian/control
--- gns3-0.8.7/debian/control 2014-07-08 17:30:56.0 +0100
+++ gns3-0.8.7/debian/control 2014-11-27 21:10:44.0 +
@@ -3,6 +3,7 @@
Priority: optional
Maintainer: Daniel Lintott dan...@serverb.co.uk
Build-Depends: debhelper (= 9),
+ dh-python,
libqt4-dev,
python
Standards-Version: 3.9.5
diff -Nru gns3-0.8.7/debian/docs gns3-0.8.7/debian/docs
--- gns3-0.8.7/debian/docs 2014-07-08 17:30:56.0 +0100
+++ gns3-0.8.7/debian/docs 2014-11-27 21:10:44.0 +
@@ -1,6 +1,3 @@
AUTHORS
-baseconfig.txt
-baseconfig_sw.txt
README
TODO
-debian/additional/gns3.ini
diff -Nru gns3-0.8.7/debian/install gns3-0.8.7/debian/install
--- gns3-0.8.7/debian/install 2014-07-08 17:30:56.0 +0100
+++ gns3-0.8.7/debian/install 2014-11-27 21:10:44.0 +
@@ -2,3 +2,4 @@
debian/additional/applications/* usr/share/applications/
debian/additional/icons/* usr/share/icons/
debian/additional/pixmaps/* usr/share/pixmaps/
+debian/additional/gns3.ini usr/share/gns3/
diff -Nru gns3-0.8.7/debian/patches/baseconfig_dir.patch
gns3-0.8.7/debian/patches/baseconfig_dir.patch
--- gns3-0.8.7/debian/patches/baseconfig_dir.patch 2014-07-08
17:30:56.0 +0100
+++ gns3-0.8.7/debian/patches/baseconfig_dir.patch 2014-11-27
21:10:44.0 +
@@ -4,16 +4,14 @@
Author: Daniel Lintott dan...@serverb.co.uk
Forwarded: Not needed, debian specific
---
-Index: gns3/src/GNS3/Config/Defaults.py
-===
gns3.orig/src/GNS3/Config/Defaults.py 2013-10-24 11:57:33.518105996
+0100
-+++ gns3/src/GNS3/Config/Defaults.py 2013-10-24 22:34:35.869585964 +0100
+--- a/src/GNS3/Config/Defaults.py
b/src/GNS3/Config/Defaults.py
@@ -48,7 +48,7 @@
elif sys.platform.startswith('win'):
BASECONFIG_DIR = ''
else:
-BASECONFIG_DIR = '/usr/local/share/examples/gns3/'
-+BASECONFIG_DIR = '/usr/share/doc/gns3/'
++BASECONFIG_DIR = '/usr/share/gns3/'
# Default path to qemuwrapper
if sys.platform.startswith('win'):
diff -Nru gns3-0.8.7/debian/patches/setup.py.patch
gns3-0.8.7/debian/patches/setup.py.patch
--- gns3-0.8.7/debian/patches/setup.py.patch2014-07-08 17:30:56.0
+0100
+++ gns3-0.8.7/debian/patches/setup.py.patch2014-11-27 21:10:44.0
+
@@ -2,16 +2,17 @@
Author: Daniel Lintott dan...@serverb.co.uk
Forwarded: Not needed, debian specific
---
-Index: gns3-0.8.6/setup.py
-===
gns3-0.8.6.orig/setup.py 2013-10-26 12:52:22.628993000 +0100
-+++ gns3-0.8.6/setup.py2013-10-26 13:34:26.477263931 +0100
-@@ -284,7 +284,5 @@
+--- a/setup.py
b/setup.py
+@@ -283,8 +283,7 @@
+ 'GNS3.Ui.ConfigurationPages',
'GNS3.Langs'],
package_data = { 'GNS3': ['Langs/*.qm', 'Dynagen/configspec'] },
- data_files = [ (wrapper_dir, ['qemuwrapper/qemuwrapper.py',
'vboxwrapper/vboxcontroller_4_1.py', 'vboxwrapper/vboxwrapper.py',
'vboxwrapper/tcp_pipe_proxy.py']),
+- data_files = [ (wrapper_dir, ['qemuwrapper/qemuwrapper.py',
'vboxwrapper/vboxcontroller_4_1.py', 'vboxwrapper/vboxwrapper.py',
'vboxwrapper/tcp_pipe_proxy.py']),
-('/usr/local/share/examples/gns3/',
['baseconfig.txt', 'baseconfig_sw.txt']),
-('/usr/local/share/doc/gns3/', ['README', 'COPYING',
'CHANGELOG']),
-('/usr/local/share/man/man1/', ['docs/man/gns3.1'])]
++ data_files = [ (wrapper_dir, ['qemuwrapper/qemuwrapper.py',
'vboxwrapper/vboxcontroller_4_1.py', 'vboxwrapper/vboxwrapper.py',
'vboxwrapper/tcp_pipe_proxy.py',
++'baseconfig.txt',
'baseconfig_sw.txt
Re: Depends on exact version
On Sun, Nov 16, 2014 at 02:39:15PM +0100, Andreas Metzler wrote: Daniel Lintott dan...@serverb.co.uk wrote: I have a package which is split into two sources (a server and gui). The server version should match the gui version (upstream version) at all times. Because of this when I'm creating the meta-package that will depend on both the gui and server, should be versioned to to be the same upstream version. [...] Hello, can you add a little bit more info? Are server and GUI running on the same machine? If they are, there is no need for the metapackage, the GUI package can simply depend on the server. OTOH if they can run (and usualy do run) on different machines a meta-package that syncs server and gui on a single machine would not help. The server and GUI *can* be run on the same machine (and most users probably will), but there is also the a high possibility that a user will want to run the server seperately from the GUI (maybe even running the GUI on Windows/Mac). The metapackage is needed to provide an upgrade route from the GNS3 0.8.x [1] to the new GNS3 1.x which is split into a gui/server. Obviouosly it's preferred for existing users of GNS3 to upgrade to the new version, as the old version (what will become gns3-legacy) is no longer in active development. But upstream (whom I'm involved with) are well aware that a user may wish to continure using the older version for, which is largely bug free (O bugs on Debain Bug Tracker). Hope that explains it! Regards Daniel [1] http://tracker.debian.org/gns3 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141117193852.ga...@mail.serverb.co.uk
Re: Depends on exact version
On 12/11/14 22:40, Andreas Cadhalpun wrote:
[...]
You require the exact upstream version (1.1).
This can't work, because there will always be the Debian revision added
(1.1-1~exp1).
I had a suspicion that this was why, but wasn't sure.
What should work better is '= ${source:Upstream-Version}'.
However, that is not enough to guarantee that the upstream versions
always match. One could then have e.g.:
gns3= 1.1-1
gns3-gui= 1.1-1
gns3-server = 1.2-1
If you want to prevent that, you can add appropriate Breaks:
gns3-server:
Breaks: gns3-gui ( ${source:Upstream-Version})
gns3-gui:
Breaks: gns3-server ( ${source:Upstream-Version})
I presume this should since is deprecated? Would this also need
breaks on the greater than side.
What I'm trying to ensure is that the upstream versions match, the
checks in the gui (that check server version) aren't worried about
Debian revision.
If it's possible to do this, without having to change the breaks
manually each time it would definitely be preferably!
Regards Daniel
signature.asc
Description: OpenPGP digital signature
Re: Depends on exact version
On 12/11/14 23:32, Henrique de Moraes Holschuh wrote:
On Wed, 12 Nov 2014, Roger Light wrote:
Could you try ${binary:Version} instead?
(= ${binary:Version}) can break binNMUs. Be careful.
Indeed, I am keen to try and avoid any breakages like that. I also don't
think the above would work for this for example:
GUI 1.1-1 and Server 1.1-1 = OK
GUI 1.1-2 and Server 1.1-4 = OK
GUI 1.1-1 and Server 1.2-1 = Not OK
Regards
Daniel
signature.asc
Description: OpenPGP digital signature
Depends on exact version
I have a package which is split into two sources (a server and gui). The
server version should match the gui version (upstream version) at all times.
Because of this when I'm creating the meta-package that will depend on
both the gui and server, should be versioned to to be the same upstream
version.
To try and achieve this I've used the following:
Depends: ${misc:Depends},
gns3-gui (= ${source:Upstream-Version}),
gns3-server (= ${source:Upstream-Version})
as I'm not worried about what the Debian revision is... but this doesn't
seem to work when it comes to aptitude.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
gns3 : Depends: gns3-gui (= 1.1) but it is not going to be installed
Depends: gns3-server (= 1.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
From apt-cache policy gns3-*:
gns3-gui:
Installed: (none)
Candidate: 1.1-1~exp1
Version table:
1.1-1~exp1 0
100 http://echo.internal.serverb.co.uk/debian/ experimental/contrib
amd64 Packages
gns3-server:
Installed: (none)
Candidate: 1.1-1~exp1
Version table:
1.1-1~exp1 0
100 http://echo.internal.serverb.co.uk/debian/ experimental/contrib
amd64 Packages
Any idea where I've gone wrong here?
Regards
Daniel
signature.asc
Description: OpenPGP digital signature
Binary package re-assignment
Hi mentors, I'm in the process of preparing new packaging for GNS3. Currently source package gns3 produces one binary package also named gns3. The newer version of the software has been split into a separate gui/server (separate source packages). For the new packaging I prose the following: Source : Binaries gns3-server : gns3-server gns3-gui: gns3-gui, gns3 (metapackage depending on gui/server) This creates a clash between the two gns3 binary packages. Therefore what I propose is to modify the packaging of the old version to create a gns3-legacy binary package, to give users the option of using the older version should they wish to do so. But at the same time providing an upgrade path from gns3 0.8.x to 1.x (using the new gns3 metapackage). Does this seem sane? Regards Daniel signature.asc Description: OpenPGP digital signature
Bug#768251: RFS: ip2location/7.0.0-1 [ITP]
On 06/11/14 10:03, Sven Hoexter wrote: On Wed, Nov 05, 2014 at 09:45:25PM -0800, Lim Chris wrote: Hi, Package name: ip2location Version : 7.0.0-1 Upstream Author : IP2Location URL : http://www.ip2location.com Is this tool of any use without the commercial database? Are there free databases available? Otherwise I think this belongs to contrib. Sven Looks like there is a lite version available here: http://lite.ip2location.com/ Daniel signature.asc Description: OpenPGP digital signature
Re: FTBFS on powerpc/ppc64el
On 20/10/14 02:26, Michel Dänzer wrote: Line 17 in /usr/include/powerpc-linux-gnu/asm/sigcontext.h is: unsigned long _unused[4]; My guess would be that either the dynamips build system, /home/daniel/workspace/dynamips/common/hash.c or one of the other header files it includes before /home/daniel/workspace/dynamips/stable/utils.h defines '_unused' as a macro. Okay.. that points me in the direction of the the common/dynamips_common.h line 83 [1]. #ifndef _unused /* Function that is never used */ #define _unused __attribute__((unused)) #endif Any ideas on where to go from here? Thanks, Daniel Lintott [1] https://github.com/GNS3/dynamips/blob/master/common/dynamips_common.h#L83 signature.asc Description: OpenPGP digital signature
FTBFS on powerpc/ppc64el
Hi, For one of my packages (dynamips) I've got a new FTBFS on Ubuntu (but is replicable on Debian as well). The last version of the package to compile successfully was 0.2.12 before upstream switched to using CMake (but I think that's a coincidence as I reproduce the FTBFS using the old Makefile with the new source) The error given in the buildlog[1] and from testing locally using qemu is: daniel@debian-powerpc:~/workspace/dynamips/build$ make ... [ 4%] Building C object stable/CMakeFiles/dynamips_nojit_stable.dir/__/common/hash.c.o In file included from /usr/include/powerpc-linux-gnu/bits/sigcontext.h:28:0, from /usr/include/signal.h:339, from /home/daniel/workspace/dynamips/stable/utils.h:13, from /home/daniel/workspace/dynamips/common/hash.c:16: /usr/include/powerpc-linux-gnu/asm/sigcontext.h:17:23: error: expected identifier or ‘(’ before ‘[’ token make[2]: *** [stable/CMakeFiles/dynamips_nojit_stable.dir/__/common/hash.c.o] Error 1 make[1]: *** [stable/CMakeFiles/dynamips_nojit_stable.dir/all] Error 2 make: *** [all] Error 2 I've had a look at the files and a search online but can't figure out what the problem is. Any help would be most appreciated. Regards Daniel [1] https://launchpad.net/ubuntu/+source/dynamips/0.2.14-1/+build/6462568/+files/buildlog_ubuntu-utopic-powerpc.dynamips_0.2.14-1_FAILEDTOBUILD.txt.gz signature.asc Description: OpenPGP digital signature
Bug#764261: RFS: librocket/1.3-1 [ITP]
Hi, On 14/10/14 17:51, whey bags wrote: On a side note, I had to delete and reupload the package to get it to update in the webui, and now http://mentors.debian.net/package/librocket says this bug doesn't belong to that package. For your fist point... you should be able to just upload the package without deleting the old one. The newest package will appear at the top of the page, with your earlier packages below it. This is because your package on mentors closes the wrong bug. In you packages changelog you should close bug #764252 (the ITP bug). Bug #764261 is your request for sponsorship, your sponsor will handle closing that when they upload your package. Regards Daniel Lintott signature.asc Description: OpenPGP digital signature
Bug#764261: RFS: librocket/1.3-1 [ITP]
Hi, On 14/10/14 18:14, whey bags wrote: I tried and it showed as having uploaded in the cli, but when I went on the webpage it was the old one. It does sometimes take a while for the upload to be processed and it appear on the webpage (it won't appear until you've received the email confirmation). The packages at [1][2], will give you an indication of how it will show up when you upload new versions. Regards Daniel [1] http://mentors.debian.net/package/yubikey-neo-manager [2] http://mentors.debian.net/package/openbox signature.asc Description: OpenPGP digital signature
Bug#762189: Bug#742344: Info received (Inclusion of German debconf template translation possible?)
Hi Helge On Mon, Oct 06, 2014 at 07:50:41PM +0200, Helge Kreutzmann wrote: Hello Daniel, on September 19th you marked this translation bug pending. Any ETA for an upload? Or should I arrange for an NMU? I have prepared a QA upload which includes all the new debconf translations and submitted an RFS [1] to both debian-mentors and debian-qa, but have received no feedback on this. Hopefully this ping may trigger, a DD to look at the prepared package and upload it! Regards, Daniel Lintott [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762189 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141006211705.ga26...@mail.serverb.co.uk
Re: gbp-create-remote-repo fails when using github
Hi Shawn, On 20/09/14 20:58, Shawn Sörbom wrote: Hi, when I try to use gbp-create-remote-repo for my Debian package I get the following error: gbp-create-remote-repo --remote-url-pattern=ssh://github.com/shsorbom/kcm-ufw- debian.git gbp: info: Shall I create a repository for 'kcm-ufw' at 'ssh://github.com/shsorbom/kcm-ufw-debian.git' now? (y/n)? Warning: Permanently added the RSA host key for IP address '192.30.252.130' to the list of known hosts. Permission denied (publickey). gbp:error: Error creating remote repository I checked at github and their documentation said that it was a problem with my RSA key. But, when I ran the test they recommended (ssh -vT g...@github.com ), everything worked fine. How can I make sure that gbp is actually using the right key? The problem here is that Github don't give shell access [1], so creating a repo isn't possible from the command line without using the GitHub API. So the workaround for this is to simply create an empty repo via the GitHub web interface and push to that. So if you already have you package prepared using Git: 1. git remote add origin g...@github.com:user/repo.git 2. git push -u origin master In addition you'll need to push any additional branches (pristine-tar, upstream) to GitHub. Hope that helps Daniel Lintott [1] http://stackoverflow.com/questions/2423777/is-it-possible-to-create-a-remote-repo-on-github-from-the-cli-without-ssh signature.asc Description: OpenPGP digital signature
Bug#762189: RFS: spamprobe/1.4d-13 [QA]
Package: sponsorship-requests Severity: normal X-Debbugs-CC: debian...@lists.debian.org Dear mentors, I am looking for a sponsor for my package spamprobe, which I prepared following a ping on a bug report[1]. * Package name: spamprobe Version : 1.4d-13 Upstream Author : Brian Burton bbur...@users.sourceforge.net * URL : http://spamprobe.sourceforge.net/ * License : QPL Section : mail It builds those binary packages: spamprobe - Bayesian spam filter To access further information about this package, please visit the following URL: http://mentors.debian.net/package/spamprobe Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/spamprobe/spamprobe_1.4d-13.dsc Changes since the last upload: spamprobe (1.4d-13) unstable; urgency=medium * QA upload. * Acknowledge non-maintainer upload. Thanks to Ondřej Surý * Updated translation of debconf template: + French, by Christian Perrier (Closes: #738805) + Danish, by Joe Dalton (Closes: #739763) + Japanese, by victory (Closes: #740363) + German, by Helge Kreutzmann (Closes: #742344) + Russian, by Yuri Kozlov (Closes: #743422) + Italian, by Luca Monducci (Closes: #759864) * Remove build-depend for xmlto (no longer used) * Convert copyright to DEP-5 format * Convert package to source format 3.0 (quilt) + Add patches for changes that had previously been made * Wrap-and-sort debian/control * Use debhelper compat 9 * Bump standards version to 3.9.5, no further changes necessary -- Daniel Lintott dan...@serverb.co.uk Fri, 19 Sep 2014 12:40:01 +0100 Regards, Daniel Lintott [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742344#10 signature.asc Description: OpenPGP digital signature
Bug#761687: RFS: abraca/0.8.0+dfsg-1 -- Simple and powerful graphical client for XMMS2
Hi Guys, On 16/09/14 07:23, Tobias Frost wrote: There are no indications that the package has been orphaned, so it likely hasn't. In case your not aware, it seems the package has now been orphaned[1] as of today (excellent work by Ricardo Mones). Regards, Daniel [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761830 signature.asc Description: OpenPGP digital signature
Bug#758538: Aw: Re: Bug#758538: RFS: pysdl2/0.9.3+dfsg1-1 [ITP] -- Python wrapper around SDL2 using ctypes
Hi, On 15/09/14 09:33, fay...@web.de wrote: Ok, new version is now uploaded. The new lintian warning looks like an error in lintian and not like an error in the copyright file. At least in my definition Zlib or CC0 is not a standard license name but the concatenation of two different ones. And according to DEP5, it is the correct way to do it with or Indeed this is/was a lintian bug (#760642) [1]. Looks like it's fixed in unstable so just a matter of mentors catching up the new version. Regards Daniel [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760642 signature.asc Description: OpenPGP digital signature
Bug#761687: RFS: abraca/0.8.0+dfsg-1 -- Simple and powerful graphical client for XMMS2
Hi Daniel, On 15/09/14 20:13, Daniel Svensson wrote: * Add me to Maintainers since old maintainer is M.I.A. Did the MIA Team actually orphan the package, as I can't find a WNPP bug for abraca? I may be wrong, but I believe unless the package is orphaned, it's not possible to become maintainer. I may be wrong here though Regards Daniel (another one) signature.asc Description: OpenPGP digital signature
Bug#761687: RFS: abraca/0.8.0+dfsg-1 -- Simple and powerful graphical client for XMMS2
On 15/09/14 20:49, Daniel Svensson wrote: On Mon, Sep 15, 2014 at 9:45 PM, Daniel Lintott dan...@serverb.co.uk mailto:dan...@serverb.co.uk wrote: Hi Daniel, On 15/09/14 20:13, Daniel Svensson wrote: * Add me to Maintainers since old maintainer is M.I.A. Did the MIA Team actually orphan the package, as I can't find a WNPP bug for abraca? I may be wrong, but I believe unless the package is orphaned, it's not possible to become maintainer. I may be wrong here though I'm not sure where I can see if a package is orphaned or not, but the maintainer doesn't reply to my emails and haven't updated the package even though I've provided all the changes needed to both the debian packaging and the software. I have no strong opinion in any direction on how to progress. I just want the package into testing again before the freeze and will comply with any recommendations you have to make this a smooth ride. I've just double-checked the WNPP package[1] to check for a bug for abraca... but can't see one, so it's possible it hasn't yet been orphaned. It can be frustrating when dealing with old packages and inactive maintainers. The process the MIA Team follow is laid in [2]. I'm not a DD myself, so I can't say I know the exact way to proceed... as a guess it may be worth dropping an email to the MIA Team [3] to find out what is happening. Sorry I can't be of more use Hopefully one of the DD's or more knowledgeable folk on here may have some better answers too. Regards Daniel [1] http://bugs.debian.org/wnpp [2] https://wiki.debian.org/qa.debian.org/MIATeam [3] https://wiki.debian.org/Teams/MIA signature.asc Description: OpenPGP digital signature
Bug#760884: RFS: astroquery/0.2.1-1 [ITP]
On 13/09/14 20:05, Andrey Rahmatullin wrote: Yes, looks like upstream broke their git repo. That tag and commits in it are not a part of any branch and the version is probably related to the version of -helpers. Unfortunately in DVCS there is no way to remove things you've published, even if they know about the problem. As that tag exists, and effectively breaks the uscan... why not just use pypi as the source for the watch file. I had to do this for a package I maintain due to lack of tags, you can see my watch file at [1] Regards, Daniel Lintott [1] http://anonscm.debian.org/cgit/users/dlintott-guest/buildnotify.git/tree/debian/watch signature.asc Description: OpenPGP digital signature
Re: [Help] strange 'missing-dependency-on-perlapi' lintian warning (Was: Bug#761134: libsbml5-perl: Depends on libperl5.18 but should be libperl5.20 now)
Hi Andreas,
I don't know the reason why, but I'll add the Debian Perl guys into the
loop... as they may well have more of an idea as I know they have doing
a lot of work in relation to the perl 5.20 transition
Regards
Daniel
On 11/09/14 21:31, Andreas Tille wrote:
Hi,
I would like to upload libsbml5 but despite the fact that
${perl:Depends} is specified and dh calls dh_perl automatically this
lintian error occures. To enable easy inspection I have uploaded the
preliminary packages to
https://people.debian.org/~tille/packages/libsmbl5/
Any help to fix this lintian problem is welcome
Andreas.
On Thu, Sep 11, 2014 at 09:27:39AM -0700, Steve Lane wrote:
Thanks very much. Now I guess I wait for it to show up on the webpage
and in the repo, yes..?
Best,
--
Steve Lane
On Sep 11 09:24, Andreas Tille wrote:
Hi,
I think a package rebuild should be sufficient to close this bug.
Thus I commited
* rebuild with latest libperl
Closes: #761134
to the changelog.
Ivo, it is *really* high time to upload libsbml if we want to deliver
it in Jessie. Do you have any idea why the current state of SVN does
not build on other machines. Please communicate your problems or lets
consult debian-mentors. We are really short in time before the freeze
(2014-11-05).
Kind regards
Andreas.
signature.asc
Description: OpenPGP digital signature
Bug#759311: RFS: node-base64-url/1.0.0-1 [ITP]
On 26 August 2014 08:46:27 BST, Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: Hi Joseph, Thanks for making the package for Debian! I'm not a DD, so I can't sponsor your package, but here's my review: d/control: -Don't put each dependency on a different line. This is actually common practice as having them on separate lines makes it easier to review a diff for future versions. --- Regards Daniel Lintott Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cd9ce277-d120-4ae5-b89d-33443448c...@email.android.com
Re: Bug#759296: RFS: psensor/1.0.4-1
Hi, On 26/08/14 11:03, Dariusz Dwornikowski wrote: I am not DD, I cannot sponsor you package but have a question, why is priority for psensor extra ? Should it not be optional ? [1] https://www.debian.org/doc/debian-policy/ch-archive.html According to the definition of 'optional': This is all the software that you might reasonably want to install if you didn't know what it was On the other hand the definition for extra is: The extra priority will usually work for new packages that conflict with others with non-extra priorities. Since your package is normal package and does not conflict with anything else, IMHO it should be optional. extra is fine for debugging symbols, maybe big manuals and so on. Your package is a GUI that can be optional. Policy also points to TeX as an example. You do not need it, it is optional, you can install it and it will not conflict with anything else. psensor is a GUI for monitoring hardware sensor, it displays graphs and raise alerts to users (AppIndicator, notify bubbles, tray icon). AFAIK, it is not required by any other packages. I don't see any reason why it should be installed if the user does not want to access himself information about fan speeds, CPU temperatures, etc. I don't believe that most users take care of this kind of information. Optional does not mean this. It just means hey you can install it if you want or need this package. It does not imply that you must install it or it is pulled by something. That is just my opinion, it would be the best that some DD would clarify this, thus I cc eriberto on this. I'm not a DD myself, but I was recently looking at this myself in relation to xdotool (which is extra). From my searching I came across a couple of postings that maybe shed some light on right way [1][2] Hope that helps Daniel [1] https://lists.debian.org/debian-devel/2005/07/msg00126.html [2] http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2013-December/035607.html signature.asc Description: OpenPGP digital signature
Fwd: Re: RFS: java-comment-preprocessor/5.3.3
Forwarding to debian-mentors as I forgot to earlier. Original Message Subject: Re: RFS: java-comment-preprocessor/5.3.3 Date: Mon, 18 Aug 2014 10:37:26 +0100 From: Daniel Lintott dan...@serverb.co.uk To: Eugene Zhukov jevgeni...@gmail.com CC: debian-j...@lists.debian.org Hi Eugene, On 18/08/14 09:52, Eugene Zhukov wrote: Hello, I packaged java-comment-preprocessor, which is a dependency for Saxon-HE 9.5.1.1. The ITP is 757093 (it also has a link to repo). The package is otherwise ready to be uploaded to NEW, but I need help with d/watch. I sent email about it to debian-java [1], but no response. [1] https://lists.debian.org/debian-java/2014/07/msg00036.html Quoted from [1] above: I have d/watch which looks like: version=3 https://code.google.com/p/java-comment-preprocessor/source/list?name=5.3.3 (.+)\.tar\.gz This won't work anyway... as it will always retrieve 5.3.3, which defeats the object of debian/watch which is to show when a new upstream release is available. When I run uscan I get: [...] https://java-comment-preprocessor.googlecode.com/archive/5.3.3.tar.gz failed: 500 Can't connect to java-comment-preprocessor.googlecode.com:443 However wget https://java-comment-preprocessor.googlecode.com/archive/5.3.3.tar.gz works just fine. What do I miss? The problem is https://java-comment-preprocessor.googlecode.com/archive doesn't actually exist, it's obviously being silently redirected in the background... and I can see no way to get a list of tags from a Google code project that uses mercurial. Looking at [2] they suggest using the downloads, which upstream have sort of used... but haven't made a release for 5.3.3 [3]. My suggestion would be to contact upstream and see if they are prepared to make a source package available via the download mechanism. Hope that helps, Daniel [2] https://wiki.debian.org/debian/watch#Google_Code [3] https://code.google.com/p/java-comment-preprocessor/downloads/list?can=1 signature.asc Description: OpenPGP digital signature
Re: RFS: java-comment-preprocessor/5.3.3
Hi Eugene, On 18/08/14 12:39, Eugene Zhukov wrote: On Mon, Aug 18, 2014 at 12:37 PM, Daniel Lintott dan...@serverb.co.uk wrote: [...] My suggestion would be to contact upstream and see if they are prepared to make a source package available via the download mechanism. Unfortunately that is not possible because of [1]. Are you sure there is no way to get a list of tags from a Google Code project that uses mercurial? Ack... I wasn't aware of that... Talk about crippling the service! I have looked all over the Google Code interface and can't find a suitable list anywhere. To me this is a fundamental flaw in their service, when you compare it with GitHub or BitBucket(which supports mercurial as well, should upstream want any suggestions). I guess I need to ask upstream to move downloads to Google Drive or elsewhere then. It would indeed seem that way unfortunately :/ Regards Daniel Lintott signature.asc Description: OpenPGP digital signature
Bug#758134: RFS: qpid-cpp/0.28-1 [ITA]
Hi Darryl, On 14/08/14 19:15, Darryl L. Pierce wrote: On Thu, Aug 14, 2014 at 10:48:31AM -0400, Darryl L. Pierce wrote: Package: sponsorship-requests Severity: normal Dear Maintainer, I am looking for a sponsor for my package qpid-cpp * Package name: qpid-cpp Version : 0.28-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License : [fill in] Slipped and didn't fill in these fields. Is there a way to update the fields, or should I resubmit the RFS? Just send an email to the bug report (758...@bugs.debian.org) with the information you missed. No need to resubmit the RFS. Also when you send a followup to the RFS (or any bug), there's no need to include the submit@b.d.o address. Regards Daniel signature.asc Description: OpenPGP digital signature
Bug#728220: RFS: fatcat/1.0.4-1 [ITP]
Hi Eriberto, Grégoire, I thought I'd just run a test build to see if I could reproduce the missing hardening... and I can't. I built the package using an unstable sbuild chroot, and have run both lintian and blhc on the results. Neither complained about any missing hardening. For reference I used: lintian v2.5.25~bpo70+1 blhc 0.04 (installed from bpo) Regards Daniel On 07/08/14 18:06, Eriberto wrote: Ok, sorry. Do you are using Debian Sid? Is it updated? Please, reply to me and to the bug (reply all) 2014-08-07 13:40 GMT-03:00 Grégoire Passault g.passa...@gmail.com: If you have a look to the log below, I run lintian about .changes .dsc and .deb signature.asc Description: OpenPGP digital signature
Bug#756331: RFS: aafigure/0.5-4 [ITA]
Hi Breno, On 07/08/14 17:49, Breno Leitao wrote: On 07/28/2014 06:52 PM, Daniel Lintott wrote: Hi, I'm not a DD so cannot sponsor your package. I haven't tried to build the package, but a couple of comments. Thank you, I addressed you concerns and I just uploaded a new package: http://mentors.debian.net/package/aafigure I've added the debian-python mailing list to the email, as per Scott's comments [1]: If you'd like to continue to maintain it within the team, it is relatively easy to get team sponsorship. If so, please update the package in the DPMT svn and then you can ask for sponsorship via the team ML or on IRC. I would say, it would be a good idea to liaise with them... especially as the package gives the VCS in the python-modules team. With regards to the VCS, from a quick look it looks like there is going to be some housekeeping needed... as the 0.5-4 version in Debian doesn't match 0.5-4 in VCS (and is UNRELEASED). I'm not familiar with the SVN packaging workflow, so I can't really comment more on what would be needed here, but I expect someone from the python-modules team will have the answer. Onto the package... 1. It's probably a good idea to add yourself to the debian/copyright under the debian/* section (and possibly add Super Nathan Weber as well, since he prepared the last version in Debian) 2. debian/compat debian/control - debhelper these should probably be bumped to 9 (or 8 at least) 3. debian/control - personally I would wrap-and-sort -s this which will split the Build-Depends, Depends, Recommends to one per line which makes it easier to diff. 4. debian/rules - this could probably be tidied up to use short-format dh, but I haven't tried this Apart from them, the package builds fine and it is lintian clean. Regards, Daniel Lintott [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756331#19 signature.asc Description: OpenPGP digital signature
Bug#750677: RFS: buildnotify/0.3.5-1 [ITP]
Hi Eriberto, Thanks for reviewing the package. On 03/08/14 03:36, Eriberto Mota wrote: Hi Daniel, Please: 1. d/buildinotify.desktop.example has 'Name[en_GB]=buildnotify.desktop.example' and 'Name=buildnotify'. Is right it? (I think that must be 'Name=buildnotify.desktop.example') I have made the two fields the same, both buildnotify (the program name) 2. In d/rules remove the line '# -*- makefile -*-'. It is a useless comment. 3. Your package doesn't builds twice. So, allow the content modification of the BuildNotify.egg-info/SOURCES.txt. To make it, create the file debian/source/options with this content[1]: extend-diff-ignore = ^BuildNotify.egg-info/SOURCES.txt$ Both done 4. I suggest you add to long description a bit more of information. I needed to access the upstream site to understand the program. Where applicable, words as Gnome, KDE, etc. will improve the results when doing an 'apt-cache search'. I have added the list of features from upstream. I will admit I'm not the best when it comes to writing text like that! I haven't added any Gnome, KDE etc keywords, as the applet is designed to work independent of the desktop manager, but I'm welcome to further suggestions. 5. In d/copyright, the better information is: Copyright: 2009-2014, Anay Nayak anayak...@gmail.com. This information can be viewed in upstream VCS[2]. Updated. Thanks for your work. No problem! I have uploaded a new package to mentors at the original location. https://mentors.debian.net/package/buildnotify http://mentors.debian.net/debian/pool/main/b/buildnotify/buildnotify_0.3.5-1.dsc Regards, Daniel signature.asc Description: OpenPGP digital signature
Bug#756331: RFS: aafigure/0.5-4 [ITA]
Hi, I'm not a DD so cannot sponsor your package. I haven't tried to build the package, but a couple of comments. On 28/07/14 21:49, Breno Leitao wrote: Dear mentors, I am looking for a sponsor for my package aafigure. This is a package that I want to adopt (under ITA) but I am not a DD, so, I would need a sponsor to upload this package. * Package name: aafigure Version : 0.5-5 Upstream Author : orphaned Upstream Author seems to be either aafigure-team or Chris Liechti * URL : https://launchpad.net/aafigure * License : specific license at LICENSE.txt That would be a BSD-3-Clause license Section : python It builds those binary packages: python-aafigure - ASCII art to image converter To access further information about this package, please visit the following URL: http://mentors.debian.net/package/aafigure Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/aafigure/aafigure_0.5-5.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: aafigure (0.5-5) unstable; urgency=low * Set myself as maintainer (closes: #719549). * Bump Standards-Version from 3.9.4 to 3.9.5 * Transition to dh_python2 -- Breno Leitao bren...@br.ibm.com Mon, 28 Jul 2014 19:27:41 + It seems there is some previous involvement with the Debian Python Modules team, where the packaging exists in SVN. It would probably be a good idea to liaise with them (I'm not a member myself, so don't how the team works). I have added them to the CC. The the mentors page there is one lintian info warning, which is trivial to fix. - vcs-field-not-canonical Regards, Daniel signature.asc Description: OpenPGP digital signature
Re: uscan: sf watch redirector update trouble for tth
On 15/07/14 03:30, Paul Wise wrote: On Tue, Jul 15, 2014 at 8:45 AM, Daniel Lintott wrote: Only advice I can give you can find in https://lists.debian.org/debian-mentors/2014/07/msg00153.html Negotiations with sourceforge are continuing but it looks like we may have to adopt the RSS based redirector code. Indeed it looks like that may be be the best way to proceed at least until SF.net can provide a solution. When I wrote the RSS parser script I have tried to make it seamlessly fit with the old redirector.. so it could be fitted in place of, but currently the is one difference. The links in the current redirector are written displayed (in source) as: a href='vpcs-0.5b0-src.tbz'vpcs-0.5b0-src.tbz/abr/ Which results in the following link: https://qa.debian.org/watch/sf.php/vpcs/vpcs-0.5b0-src.tbz For some reason (maybe server configuration difference) I wasn't able to achieve exactly the same in my RSS based redirector... So in the page source I have: a href='/debian/sf.php/vpcs/vpcs-0.5b2-src.tbz'vpcs-0.5b2-src.tbz/abr/ Note the addition of the directory and script name, which may break some of the regex's (it did for me). I had to add this in the source as I couldn't get the link displayed with the slash argument when I tested it on my servers. It may be that I've missed something obvious... so feel free to correct me! Regards Daniel signature.asc Description: OpenPGP digital signature
Re: Help with libquazip / Qt4-Qt5
Hi, On 14/07/14 15:07, Eric Maeker wrote: Please, Mentors, help me with these unlying questions. - should libquazip be build inside debian using Qt5 and/or Qt4? Both. for now. Ok. How can I manage this? Is it possible inside one unique source package? Debhelper does only have a qmake_qt4 buildsystem. Or should I create a duplicate of the current libquazip(-qt4) renamed as libquazip-qt5? This will lead to a double source packaging. I don't if this is necessarily exactly what your after but the idea seems similar to what your trying to do... the package gtk-vnc [1], builds against both gtk2 and gtk3, using the rules file at [2]. Hopefully, this might give you some pointers! Regards Daniel [1] https://tracker.debian.org/pkg/gtk-vnc [2] https://tracker.debian.org/media/packages/g/gtk-vnc/rules-0.5.3-1 signature.asc Description: OpenPGP digital signature
Re: uscan: sf watch redirector update trouble for tth
Hi... This bug is certainly starting to cause problems... On 15 July 2014 01:35:46 BST, Jerome BENOIT g62993...@rezozer.net wrote: Hello List ! It seems that the SourceForge watch redirector for tth [1] does not update properly: since a couple of weeks the latest upstream version of tth at SourceForge [2] has not been noticed. In short I am stuck, but I want to step forward: any idea ? Thanks in advance, Jerome [1] https://packages.qa.debian.org/t/tth.html [2] http://sourceforge.net/projects/tth/ Only advice I can give you can find in https://lists.debian.org/debian-mentors/2014/07/msg00153.html --- Regards Daniel Lintott Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/0bee1669-b2ad-4a75-a5dc-441aa901d...@email.android.com
Re: Lazarus watch file is broken
Hi, On 13/07/14 11:13, Abou Al Montacir wrote: Hi All, I've noticed that the PTS does not display the usual warning about Lazarus 1.2.4 released but not packaged. I've tried to investigate the issue and found that upstream has rearranged their repository layout under SF.net so that the watch site [1] does not work anymore for it. The new files could be found at [2] and the watch file we are using at [3]. How to proceed? 1) Ask upstream to go back? This is unlikely to happen. 2) Try to modify uscan parameters in [3] so that we look directly in sf.net? 3) Have [1] fixed? but how? I think your actually the following the bug at [1]. You can see the conversation I had with Paul in that bug report. Regards, Daniel Lintott [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752384 signature.asc Description: OpenPGP digital signature
Re: HEAnet sourceforge mirror is outdated (was Re: [Pkg-pascal-devel] Lazarus watch file is broken)
Hi Abou, On 13/07/14 12:40, Abou Al Montacir wrote: Hi Daniel, ... I have tested your tool for Lazarus and it looks working as expected. That's always good to know! I'd recommend to use this solution in [2] as it looks really easy to maintain/update with so few php lines. Also I don't know how much time it will took SF.net to come with a solution for [3]. BTW, do you expect one can rely on [1] and modify his wach file to use it instead of [2] until this bug get fixed? It shouldn't be a problem to use [1], there should be enough bandwidth to manage. So I would say.. go ahead and use it... but I do only intend this to be a temporary fix. How long it will take SF.net to come up with a solution is anyone's guess! But obviously if it looks like my script will be 'long-term' it would obviously be preferable to move it to a Debian server. [1] http://alpha.serverb.co.uk/debian/sf.php/lazarus [2] https://qa.debian.org/watch/sf.php/lazarus [3] http://sourceforge.net/p/forge/site-support/8064/ Regards, Daniel signature.asc Description: OpenPGP digital signature
Bug#750677: RFS: buildnotify/0.3.5-1 [ITP]
Just bringing this to the front again... to see if anybody is interested in sponsoring this? I have now been using the package ever since I packaged it and it has been working perfectly. Original Message Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package buildnotify * Package name: buildnotify Version : 0.3.5-1 Upstream Author : Anay Nayak anayak...@gmail.com * URL : https://bitbucket.org/Anay/buildnotify * License : GPL-3+ Section : devel It builds those binary packages: buildnotify - cruise control CI build monitor To access further information about this package, please visit the following URL: http://mentors.debian.net/package/buildnotify Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/b/buildnotify/buildnotify_0.3.5-1.dsc More information about buildnotify can be obtained from https://bitbucket.org/Anay/buildnotify. Changes since the last upload: buildnotify (0.3.5-1) unstable; urgency=low * Initial release (Closes: #750457) -- Daniel Lintott dan...@serverb.co.uk Thu, 05 Jun 2014 10:38:07 +0100 Regards, Daniel Lintott signature.asc Description: OpenPGP digital signature
Bug#753649: RFS: liblinux-inotify2-perl/1:1.22-1 [ITA] -- scalable directory and file change notification
Hi Eriberto, On 03/07/14 22:22, Eriberto wrote: * Package name: liblinux-inotify2-perl Version : 1:1.22-1 Upstream Author : Marc Lehmann schm...@schmorp.de * URL : http://software.schmorp.de/pkg/Linux-Inotify2.html * License : Perl Section : perl You may want to drop an email to the guys on the Debian Perl Group List(cc'd), and look at maintaining the package within the the team, if you are interested in that. I expect one of the DD's from the group... may well pick this up and fill in more of the details ;) Regards Daniel Lintott Debian Perl Group signature.asc Description: OpenPGP digital signature
Package priority
Hi Mentors, I happened to take a look at the debcheck status for the GNS3 package[1]. The package depends on xdotool, as it is used by GNS3... but from the debcheck output I've discovered the xdotool is priority extra. Looking at this it would seem to me, that it is xdotool that is in the wrong section. This seems to be confirmed by some past discussions of extra vs optional [2][3]. Before I went ahead and changed anything or filed a bug report, I thought I'd get the opinion from here. Regards, Daniel Lintott [1] http://qa.debian.org/debcheck.php?list=package=gns3arch=dist=sid [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731836 [3] http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2013-December/035607.html signature.asc Description: OpenPGP digital signature
Re: Help for watch file needed
Hi Andreas, On 29/06/14 14:05, Andreas Tille wrote: Hi Jakub On Sun, Jun 29, 2014 at 12:04:20PM +0200, Jakub Wilk wrote: You got it backwards. It should be: uversionmangle=s/-/./g No, I really want to substitute v2-0-1 to 2.0-1 as the tarball on the download page I don't know if this is the best method... but it seems to work. uversionmangle=s/(\d)-(\d-\d)/$1.$2/g Regards, Daniel Lintott signature.asc Description: OpenPGP digital signature
Re: How to do a test sbuild with additional package, not in the repositories?
On 28/06/14 20:37, Paul Elliott wrote: How do I get the one package that is not in unstable (libwxsqlite3-3.0-dev) into sbuild's list of packages for a test build? I thought I'd seen this on the Debian sbuild wiki page... but alas it's not there! The only thing I was able to find was this- http://www.wefearchange.org/2011/09/sbuild-with-local-newer-dependencies.html HTH Daniel Lintott signature.asc Description: OpenPGP digital signature
Bug#752782: RFS: kvmcs-server_0.4.0 server part in kvm client server environment
Hi Willem, NB: I'm not a DD so cannot sponsor your package But a couple of points to consider... On 26/06/14 15:21, willem kuyn wrote: I am looking for a sponsor for my package kvmcs-server: * Package name: kvmcs-server Version : 0.4.0 Upstream Author : willem kuyn; willemk...@gmail.com * URL : * License : GPL-3+ Section : comm It builds those binary packages: kvmcs-server To access further information about this package, please visit the following URL: http://mentors.debian.net/package/kvmcs-server Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/k/kvmcs-server/kvmcs- server_0.4.0.dsc There are 2 more packages available kvmcs-client and kvmcs-doc for client software and example documentation. They will be uploaded if this package is accepted. The full source of all packages is available at www.gitorious.org/kvmcs I think rather than using three separate source packages, it would be preferable to use one 'kvmcs' source package and create the 3 binary packages from that (and then version all three with the same version. I think it could get confusing if we have server 0.4.0 and client 0.4.1 (as seen on gitorious)) Is the software really only useful in Debian? My initial look tells me no... In which case the package shouldn't be native format Just a couple of pointers... I haven't looked at the package any closer as yet. Regards, Daniel signature.asc Description: OpenPGP digital signature
Bug#750771: RFS: python-fysom/1.0.15-1 [ITP] (bootstrap-vz dependency)
On 07/06/14 22:20, Alex Chernyakhovsky wrote: I've noticed you're using debhelper, and specify a compat level of 8. As far as I can tell, you're only using debhelper 7 features; perhaps consider setting the compat level to 7 (and depending on debhelper = 7) to ease backporting? That is unnecessary as oldstable has debhelper 8 [1] Regards, Daniel Lintott [1] http://packages.qa.debian.org/d/debhelper.html signature.asc Description: OpenPGP digital signature
Bug#750677: RFS: buildnotify/0.3.5-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package buildnotify * Package name: buildnotify Version : 0.3.5-1 Upstream Author : Anay Nayak anayak...@gmail.com * URL : https://bitbucket.org/Anay/buildnotify * License : GPL-3+ Section : devel It builds those binary packages: buildnotify - cruise control CI build monitor To access further information about this package, please visit the following URL: http://mentors.debian.net/package/buildnotify Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/b/buildnotify/buildnotify_0.3.5-1.dsc More information about buildnotify can be obtained from https://bitbucket.org/Anay/buildnotify. Changes since the last upload: buildnotify (0.3.5-1) unstable; urgency=low * Initial release (Closes: #750457) -- Daniel Lintott dan...@serverb.co.uk Thu, 05 Jun 2014 10:38:07 +0100 Regards, Daniel Lintott signature.asc Description: OpenPGP digital signature
Re: Starting an application on login
On 04/06/14 04:55, Paul Wise wrote: On Wed, Jun 4, 2014 at 2:54 AM, Daniel Lintott wrote: It only makes sense to start the application when the user logs in, which can be done using the $(HOME)/.config/autostart directory or adding an entry using the Startup Applications GUI. There are additional dirs that the package can install into: http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html Thankyou for the link... I had found the directories but that gives me the information on how to use them From the packaging perspective, is this something we should do when the package is installed... or should it be left to the user to configure how they start it? In general, things in Debian should work when they are installed so I would say autostart it. That was certainly my initial feeling Regards, Daniel signature.asc Description: OpenPGP digital signature
Re: Starting an application on login
On 04/06/14 06:24, Cameron Norman wrote: El Tue, 3 de Jun 2014 a las 9:03 PM, Eric Lavarde e...@lavar.de escribió: Hi Daniel, On 3 June 2014 20:54:58 CEST, Daniel Lintott dan...@serverb.co.uk wrote: Hi Mentors! I'm currently packaging a notification application, BuildNotify [1]. It only makes sense to start the application when the user logs in, which can be done using the $(HOME)/.config/autostart directory or adding an entry using the Startup Applications GUI. From the packaging perspective, is this something we should do when the package is installed... or should it be left to the user to configure how they start it? The thing is that a Linux system is potentially multi user, with users not interested in the application and others added after package installation, so the answer can only be that the users must configure it themselves. XDG autostart provides for both of these scenarios. You can (and should) install the autostart entry in /etc/xdg/autostart/ for system wide starting of the tray icon. Individual users can disable the entry by making one with the same name in ~/.config/autostart/ with a single line, Hidden=true, as the contents. I think users installing this piece of software will expect it to be started at boot, and we should do just that. Ack, I'm currently considering some sort of debconf scenario, which would give the option for a user to install but not autostart Regards, Daniel signature.asc Description: OpenPGP digital signature
Re: Starting an application on login
On 04/06/14 09:53, Ansgar Burchardt wrote: On 06/04/2014 07:24, Cameron Norman wrote: El Tue, 3 de Jun 2014 a las 9:03 PM, Eric Lavarde e...@lavar.de escribió: Hi Daniel, On 3 June 2014 20:54:58 CEST, Daniel Lintott dan...@serverb.co.uk wrote: Hi Mentors! I'm currently packaging a notification application, BuildNotify [1]. It only makes sense to start the application when the user logs in, which can be done using the $(HOME)/.config/autostart directory or adding an entry using the Startup Applications GUI. From the packaging perspective, is this something we should do when the package is installed... or should it be left to the user to configure how they start it? XDG autostart provides for both of these scenarios. You can (and should) install the autostart entry in /etc/xdg/autostart/ for system wide starting of the tray icon. Individual users can disable the entry by making one with the same name in ~/.config/autostart/ with a single line, Hidden=true, as the contents. I think users installing this piece of software will expect it to be started at boot, and we should do just that. BuildNotify lets you monitor multiple continuous integration servers with customizable build notifications for all projects. I would assume it will only do useful work after configuration. If that is the case, I think setting up the autostart bits should be done by BuildNotify when a user has entered something useful into the configuration. That is mostly correct... currently BuildNotify needs to be started/running to access the configuration GUI. I have found that this is then saved to a file in plain text, which would mean I could create a debconf scenario to perform the initial configuration and add the appropriate autostart scripts. Regards, Daniel signature.asc Description: OpenPGP digital signature
Re: Starting an application on login
On 04/06/14 11:40, Ansgar Burchardt wrote: On 06/04/2014 12:07, Daniel Lintott wrote: On 04/06/14 09:53, Ansgar Burchardt wrote: BuildNotify lets you monitor multiple continuous integration servers with customizable build notifications for all projects. I would assume it will only do useful work after configuration. If that is the case, I think setting up the autostart bits should be done by BuildNotify when a user has entered something useful into the configuration. That is mostly correct... currently BuildNotify needs to be started/running to access the configuration GUI. Well, then a user has to start it once manually. Subsequent starts will happen automatically. Okay. I have found that this is then saved to a file in plain text, which would mean I could create a debconf scenario to perform the initial configuration and add the appropriate autostart scripts. There is no per-user configuration done at package installation time. So I don't see where you plan to use debconf. Or does BuildNotify use a global configuration? Just let BuildNotify add itself to the per-user autostart once a user has configured it. No need for debconf or anything special in the packaging. This is something I presume that will need to be handled upstream as currently it doesn't provide a simple autostart option. Regards Daniel signature.asc Description: OpenPGP digital signature
Re: Starting an application on login
Hi Eric
On 04/06/14 22:17, Eric L. wrote:
Hi,
On 4 June 2014 07:24:27 CEST, Cameron Norman camerontnor...@gmail.com wrote:
I think users installing this piece of software will expect it to be
started at boot, and we should do just that.
Where I do not agree with your conclusion is that _users_ do not install
software, _admins_ (aka root) do. If one user requests the software, the
admin installs it and nine other users complain that this software is now
starting when they login, which means the admin has to explain how to _not_
start it, I'm not sure this is the right thing to do.
On the other hand, if one user requests the software, the admin installs it
and explains to the requester how to activate it, that sounds more like a
plan.
And I'm conscious that many users are sole user and admin on their desktop,
but that's not the unique use case (I'm personally user and admin on my PC
but I have other users and I don't want them to be impacted just because I
decide to install a package for my own usage).
This was the very situation I was imagining... so it would therefore
seem to lend itself to not be autostarted, but provide {documentation,
examples, README.debian} to provide further setup notes.
Regards,
Daniel
signature.asc
Description: OpenPGP digital signature
Starting an application on login
Hi Mentors! I'm currently packaging a notification application, BuildNotify [1]. It only makes sense to start the application when the user logs in, which can be done using the $(HOME)/.config/autostart directory or adding an entry using the Startup Applications GUI. From the packaging perspective, is this something we should do when the package is installed... or should it be left to the user to configure how they start it? If it's left to the user to configure how to start it, what is the best way of informing the user what they need to do? [1] http://bugs.debian.org/750457 Regards, Daniel Lintott signature.asc Description: OpenPGP digital signature
Build-Deps
Hi Mentors! Does anybody know if there is a way of checking whether the Build-Depends of a package would be able to be satisfied on a particular release e.g wheezy. For example: I take a package from testing to create a backport to wheezy and want to know if Build-Depends can be satisfied as the package is. I've had a look at dose-builddebcheck, but this doesn't seem to have an option for running on a single package. I believe the buildd's do something along these lines prior to building a package. Regards, Daniel Lintott -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/538a50e3.2060...@serverb.co.uk
Re: Build-Deps
On 31 May 2014 23:02:49 BST, Johannes Schauer j.scha...@email.de wrote: Hi, Quoting Daniel Lintott (2014-06-01 00:00:03) I've had a look at dose-builddebcheck, but this doesn't seem to have an option for running on a single package. dose-builddebcheck is what you are looking for and it can check a single package by using the --checkonly option. Okay... In fairness I haven't tried that as yet... But the option doesn't appear to mentioned in the manpage [0]. [0] http://manpages.debian.org/cgi-bin/man.cgi?query=dose-builddebcheckapropos=0sektion=0manpath=Debian+7.0+wheezyformat=htmllocale=en --- Regards Daniel Lintott Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/d4e18fb4-9b4c-468a-877d-855ac794a...@email.android.com
Bug#742050: RFS: gns3/0.8.6-3~bpo70+1
On 28/05/14 22:12, Joao Eriberto Mota Filho wrote: Hi, To get success, you should send your RFS to Backports list.[1] [1] http://backports.debian.org/Contribute/#index3h3 Regards, Eriberto Thanks for the reply... I had indeed sent the RFS to backports as well, but received nil response over there. I shall reupload the files and ping them again shortly! -- Daniel Lintott GPG Key: 4096R/5D73EC6E signature.asc Description: OpenPGP digital signature
Re: force CMake over automake
Hi Nico, On 08/05/14 16:21, Nico Schlömer wrote: Hi all, I've got a package here that supports both Cmake and automake configurations. How do I force the builder to use CMake in debian/rules? From experimenting with a package very similar to the scenario your in I found the following worked: In debian/rules: dh $@ --buildsystem=cmake Regards, -- Daniel Lintott GPG Key: 4096R/5D73EC6E signature.asc Description: OpenPGP digital signature
Re: git-buildpackage python3, python3.4: not found
And this time send it to the groups On 30 April 2014 17:37:56 BST, Daniel James dan...@64studio.com wrote: Hi Alex, I looked on some other python3 packages and for example I get a similar result for python-dnsq package My mistake, sid has python3.4 3.4.0+20140425-1 but you would not get that by installing python3, you would have to explicitly install python3.4. Although if I've read his control file correct the dependency on python3-all should pull in 3.3 and 3.4? --- Regards Daniel Lintott Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/163283da-f235-4012-b489-c8e776ce3...@email.android.com
Re: watch file help needed: Download page of mkgmap changed and is now hiding download files behind JavaScript code
On 24/04/14 09:04, Andreas Tille wrote: Hi, if you look at the HTML code of http://www.mkgmap.org.uk/download/ you see strings like: \mkgmap-r3226-src.tar.gz\: 1555754, \mkgmap-r3226-src.zip\: 2194070, and thus uscan stopped working. I guess it will be hard to convince upstream that their new shiny page is a bad idea for Debian and that they change back. Any idea how we could make uscan capable to detect and download the latest source anyway? Kind regards Andreas. Using something like this would seem to work, added to the opts downloadurlmangle=s/\.zip/-src.tar.gz/ Regards, -- Daniel Lintott GPG Key: 4096R/5D73EC6E signature.asc Description: OpenPGP digital signature
Re: watch file help needed: Download page of mkgmap changed and is now hiding download files behind JavaScript code
On 24/04/14 09:44, Daniel Lintott wrote: On 24/04/14 09:04, Andreas Tille wrote: Hi, if you look at the HTML code of http://www.mkgmap.org.uk/download/ you see strings like: \mkgmap-r3226-src.tar.gz\: 1555754, \mkgmap-r3226-src.zip\: 2194070, and thus uscan stopped working. I guess it will be hard to convince upstream that their new shiny page is a bad idea for Debian and that they change back. Any idea how we could make uscan capable to detect and download the latest source anyway? Kind regards Andreas. Using something like this would seem to work, added to the opts downloadurlmangle=s/\.zip/-src.tar.gz/ Regards, Having just tried this again.. it only half works... Output from uscan --verbose -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: opts=dversionmangle=s/0.0.0.svn//,downloadurlmangle=s/\.zip/-src.tar.gz/ http://www.mkgmap.org.uk/download/ mkgmap-r([\d]+)\.zip -- Found the following matching hrefs: /download/mkgmap-r3226.zip (3226) Newest version on remote site is 3226, local version is 0.0.0+svn2981 (mangled local version number 2981) = Newer version available from http://www.mkgmap.org.uk/download/mkgmap-r3226-src.tar.gz -- Downloading updated package mkgmap-r3226.zip -- Scan finished So it seems as if uscan is ignoring the downloadurlmangle when it comes to actually downloading the file! Regards, -- Daniel Lintott GPG Key: 4096R/5D73EC6E signature.asc Description: OpenPGP digital signature
Re: watch file help needed: Download page of mkgmap changed and is now hiding download files behind JavaScript code
On 24/04/14 10:32, Daniel Lintott wrote: On 24/04/14 09:44, Daniel Lintott wrote: On 24/04/14 09:04, Andreas Tille wrote: Hi, if you look at the HTML code of http://www.mkgmap.org.uk/download/ you see strings like: \mkgmap-r3226-src.tar.gz\: 1555754, \mkgmap-r3226-src.zip\: 2194070, and thus uscan stopped working. I guess it will be hard to convince upstream that their new shiny page is a bad idea for Debian and that they change back. Any idea how we could make uscan capable to detect and download the latest source anyway? Kind regards Andreas. Using something like this would seem to work, added to the opts downloadurlmangle=s/\.zip/-src.tar.gz/ Regards, Having just tried this again.. it only half works... Output from uscan --verbose -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: opts=dversionmangle=s/0.0.0.svn//,downloadurlmangle=s/\.zip/-src.tar.gz/ http://www.mkgmap.org.uk/download/ mkgmap-r([\d]+)\.zip -- Found the following matching hrefs: /download/mkgmap-r3226.zip (3226) Newest version on remote site is 3226, local version is 0.0.0+svn2981 (mangled local version number 2981) = Newer version available from http://www.mkgmap.org.uk/download/mkgmap-r3226-src.tar.gz -- Downloading updated package mkgmap-r3226.zip -- Scan finished So it seems as if uscan is ignoring the downloadurlmangle when it comes to actually downloading the file! Regards, After digging into even more... hate to leave a problem unsolved... I think I cracked it! In addition to the the downloadurlmangle, a filenamemangle is needed to save the downloaded file with the correct name. filenamemangle=s/\/download\/mkgmap-r([\d]+)\.zip/mkgmap-r$1-src.tar.gz/ Which removes the download directory and names the file correctly as a tar.gz Hope that helps... Regards, -- Daniel Lintott GPG Key: 4096R/5D73EC6E signature.asc Description: OpenPGP digital signature
Re: watch file help needed: Download page of mkgmap changed and is now hiding download files behind JavaScript code
On 24/04/14 12:32, Andreas Tille wrote: Hi Daniel, thanks for your continuous trials to help me. :-) No problem! I enjoy a good bit of problem solving! On Thu, Apr 24, 2014 at 11:22:22AM +0100, Daniel Lintott wrote: Hope that helps... Not really since I can not confirm that I get anything else but: no matching hrefs for watch line I guess we somehow need to go with Paul's hint. All your hints are based on changing the regexp for the source download by droping the '-src' part from the file name. Since we really want to fetch the source and not simply the binary jar this is not helpful. However, I somehow need to make some sense out of Paul's hint which I did not fully understand admittedly. What Paul was hinting at was using using the downloadurlmangle as per my first email. What happens here is we get the href for the binary download and then mangle it to get the source tarball, by replacing .zip with -src.tar.gz s/\.zip/-src.tar.gz/ Next we have to make uscan save the file it downloads with the correct filename... filenamemangle. filenamemangle=s/\/download\/mkgmap-r([\d]+)\.zip/mkgmap-r$1-src.tar.gz/ Here we replace /download/mkgmap-r.zip with mkgmap-r-src.tar.gz to match the name of the that is actually downloaded. I have also attached a copy of the watch file I used to test the mangles. Regards, -- Daniel Lintott GPG Key: 4096R/5D73EC6E version=3 opts=dversionmangle=s/0.0.0.svn//,downloadurlmangle=s/\.zip/-src.tar.gz/,filenamemangle=s/\/download\/mkgmap-r([\d]+)\.zip/mkgmap-r$1-src.tar.gz/ \ http://www.mkgmap.org.uk/download/mkgmap-r([\d]+).zip signature.asc Description: OpenPGP digital signature
Re: Real newbie ....
On 14/04/14 22:00, Barry Drake wrote: On 14/04/14 18:48, Tobias Frost wrote: Just debstrap yourself an Debian sid chroot for development :) Will be also easier to get support here, as there are differences to Ubuntu, and you spare yourself the dual-booting :) Haven't a clue as to how to do that. The information at [1] is a very good guide, especially using pbuilder-dist (from ubuntu-dev-tools). Picking out a piece of informaton from [1]: If you want to build Debian packages on Ubuntu, you need to install Debian archive keys and add Debian distribution name, Debian mirror and key location to pbuilder command line like this: sudo apt-get install debian-archive-keyring sudo pbuilder create --distribution unstable \ --mirror ftp://ftp.us.debian.org/debian/ \ --debootstrapopts --keyring=/usr/share/keyrings/debian-archive-keyring.gpg Running Ubuntu or any other Debian/Ubuntu based operating shouldn't in my opinion be a barrier to contributing to Debian. Currently I run Linux Mint and use chroots for Debian Wheezy, Testing and Unstable as well several Ubuntu releases. Regards, -- Daniel Lintott GPG Key: 4096R/5D73EC6E signature.asc Description: OpenPGP digital signature
Re: Real newbie ....
On 13/04/14 21:49, Barry Drake wrote: On 13/04/14 20:40, Wookey wrote: So the simple fix is to update your pbuilder chroot, or build with sbuild instead (which probably involves running sbuild-createchroot to set up an unstable chroot for it to use (and running sbuild-update --keygen once to make some keys for apt to use). Each build gives you a nice log file showing exactly what was installed to satisfy the build deps, so you shoul dbe able to see which libicu version was installed. I've not checked anything, so it could be more subtle than this, but that's my first guess. Thanks for such an amazingly quick reply guys. I've re-initilised the chroot environment, with no difference. My source is at: https://www.dropbox.com/sh/urhm7iekss5a6a4/I7FveejRSd and the packages it built are at: https://www.dropbox.com/sh/s748z00c3zxiupp/-SdnD2xcHR Regards, Barry. I've just attempted a build using both sbuild and pbuilder under Debian sid (unstable). sbuild - builds fine... and gets the libicu52 dependency Depends line from libsword9: Depends: libsword-common, libc6 (= 2.14), libclucene-core1 (= 2.3.3.4), libcurl3-gnutls (= 7.16.2), libgcc1 (= 1:4.1.1), libicu52 (= 52~m1-1~), libstdc++6 (= 4.6), zlib1g (= 1:1.1.4) pbuilder - doesn't build and fails with: dpkg-source: error: can't build with source format '3.0 (quilt)': non-native package version does not contain a revision As the correct version number should be: 1.7.3+dfsg-1 Not sure I can be much more help than that... but it would definitely seem to be an issue with your chroot. Regards, -- Daniel Lintott GPG Key: 4096R/5D73EC6E signature.asc Description: OpenPGP digital signature
Re: pbuilder --autocleanaptcache ???
On 20/03/14 14:27, Andreas Tille wrote: Hi, I tried to clean up only those debs from pbuilder apt cache which are outdated and not used any more. Since --autocleanaptcache only results in printing the help page I did some research and the only hint on the weg is this quite old bug in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/358264 Does this bug really remain active (and not reported in Debian) or am I simply to stupid to use this option?? Kind regards Andreas. It seems it's important where you place the flag. I've just run (using pbuilder-dist wrapper) pbuilder-unstable update --autocleanaptcache which definately seemed to clean up a LOT of obsolete .deb's... With literally hundreds of lines like this: I: obsolete cache content debhelper_9.20130921_all.deb removed So it seems like it should work Regards, Daniel signature.asc Description: OpenPGP digital signature
Bug#742042: RFS: dynamips/0.2.11-1~bpo70+1
Package: sponsorship-requests Severity: normal X-Debbugs-CC: debian-backpo...@lists.debian.org Dear mentors, I am looking for a sponsor for my package dynamips * Package name: dynamips Version : 0.2.11-1~bpo70+1 Upstream Author : Flávio J. Saraiva flaviojs2...@gmail.com * URL : http://www.gns3.net/dynamips * License : GPLv2 Section : net It builds those binary packages: dynamips - Cisco 7200/3600/3725/3745/2600/1700 Router Emulator To access further information about this package, please visit the following URL: http://mentors.debian.net/package/dynamips Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/non-free/d/dynamips/dynamips_0.2.11-1~bpo70+1.dsc More information about hello can be obtained from http://www.gns3.net/dynamips. Changes since the last upload: dynamips (0.2.11-1~bpo70+1) wheezy-backports; urgency=medium * Rebuild for wheezy-backports. * Correct my email address in d/copyright -- Daniel Lintott dan...@serverb.co.uk Tue, 18 Mar 2014 14:54:47 + Regards, Daniel Lintott signature.asc Description: OpenPGP digital signature
Bug#742050: RFS: gns3/0.8.6-3~bpo70+1
Package: sponsorship-requests Severity: normal X-Debbugs-CC: debian-backpo...@lists.debian.org Dear mentors, I am looking for a sponsor for my package gns3 * Package name: gns3 Version : 0.8.6-3~bpo70+1 Upstream Author : Jeremy Grossmann cont...@gns3.net * URL : http://www.gns3.net * License : GPL-2.0+ Section : net It builds those binary packages: gns3 - Graphical Network Simulator To access further information about this package, please visit the following URL: http://mentors.debian.net/package/gns3 Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/contrib/g/gns3/gns3_0.8.6-3~bpo70+1.dsc More information about gns3 can be obtained from http://www.gns3.net. Changes since the last upload: gns3 (0.8.6-3~bpo70+1) wheezy-backports; urgency=medium * Rebuild for wheezy-backports. * Bump standards version to 3.9.5 - no changes -- Daniel Lintott dan...@serverb.co.uk Tue, 18 Mar 2014 16:24:17 + Regards, Daniel Lintott signature.asc Description: OpenPGP digital signature
Bug#742042: Review of GNS3 and Dynamips for backports
Hi, I have had a reply from my usual sponsor, Andrew to say that he currently doesn't have backports access. Therefore I would be most grateful if someone else could review and upload these two packages. Dynamips - http://mentors.debian.net/package/dynamips GNS3 - http://mentors.debian.net/package/gns3 Regards, Daniel signature.asc Description: OpenPGP digital signature
Re: watch file help
On 17/03/14 22:21, Matt Zagrabelny wrote: Greetings, I am attempting to write a watch file, but am hitting some issues. I thought I would start with a pretty simple regex to grab the static upstream version: % cat debian/watch version=3 https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/OCSNG_UNIX_SERVER-(2.1).tar.gz But I am hitting an issue: % uscan --report --verbose -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/OCSNG_UNIX_SERVER-(2.1).tar.gz uscan warning: In watchfile debian/watch, reading webpage https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/ failed: 500 Can't connect to launchpad.net:443 -- Scan finished Not sure if uscan can handle launchpad.net's https. Any ideas or suggestions? Thanks! -mz I may be wrong, but I'm not sure if uscan allows the full url to be in the watch file... Looking at [1] there are quite a few packages that you could adapt to suit your watch file. I've just tried the following which seems to work: version=3 https://launchpad.net/ocsinventory-server/+download .*/OCSNG_UNIX_SERVER-(.+).tar.gz Though you will need to mangle the upstream versions, to sort the rc versions before the releases. I use the following in one of my packages [2]. Hope that helps, Daniel Lintott [1] http://codesearch.debian.net/search?q=launchpad+path%3Adebian%2Fwatch [2] http://sources.debian.net/src/gns3/0.8.6-3/debian/watch signature.asc Description: OpenPGP digital signature
Re: script-with-language-extension
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/03/14 00:26, gregor herrmann wrote:
On Sun, 09 Mar 2014 21:39:01 +, Dave Walker wrote:
Net::Frame::Device includes two scripts that are installed to
/usr/bin, but both have .pl extensions therefore giving me a
Lintian warning.
My initial thought on fixing this is to rename the files by
overriding dh_auto_install in debian/rules... but I'm
struggling to find out how to do this without explicitly
writing the file names, which wouldn't accommodate new files in
future releases.
So far I've got the following:
PACKAGE = $(shell dh_listpackages) TMP =
$(CURDIR)/debian/$(PACKAGE)
SNIP find $(TMP)/usr/bin -name '*.pl'
How about: find $(TMP)/usr/bin -name *.pl -exec rename
's/\.pl$//' {} + Just make sure you do it at build time, not
install time.
Looks good, and similar to existing examples which might be a bit
simpler:
libvm-ec2-perl/debian/rules:rename 's/\.pl//'
$(TMP)/usr/bin/*.pl libvm-ec2-perl/debian/rules:rename
's/\.pl//' $(TMP)/usr/share/man/man1/*
I knew I'd seen it somewhere, but for the life of me couldn't remember
which package it was in!
Thanks, for the help guys!
Cheers,
Daniel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBAgAGBQJTHZYLAAoJEMhyZNddc+xuhEwP/jgRWFFqTBJH7+Ss0RGL+x/k
o0r3vbxiOn1KDdtk4cQ3goYiAAuycKwphtZ2VOv1ovkUlMOM1fRtkKfAkYkLOE8+
9BxKvbYS2myHfeIoeT52koKob2xhXv7IJRxywlJTRmgtTgDQaq002K23zY1+Umap
XOo/A0Ek8iDlIfcr26v6ygm5AD7sPucMcCvHCwM5N7rchAFR//1rg1Pyi8r32COS
9OCXCsvU5/KDwnRJlZODpZbbBq3kLVLrOjuD7OA8fm0i3+ibM7+pNloQegAa0/UM
RKtoUL20b4A8tQA3tJG+3CHWzuTMOgbKgn0K234x08aSr7wtvUxQhJReUrNgCveL
j9WY3MN1fPOojjttH/RrrZ29IjhYCLwxBMZrsLR7kiSFQZUo0dQb6XN+JhrDXhXd
rNZlmXuKIW0tLENXCZPLWCVnStsO1/xC1hc1164Y12qlKAAiwLJRqJJG6qiU1H14
/HafDbGDKlZA6oEcEYh1s6fTSzC/tsCETjsJHByh9TBqkuaw/5jqk1Ee+LUOBqPJ
2J17GjKgqQYge7WEmN35rdnHIjvIzVxTRejlTsRzUmKHuxoscwIkY7GOy/8jV++G
dVyvO6A14Iq63ngEToJ5R/nfotRNvTHsVgnWqMFbi8FcpP/R8S6vWIKo3KTzPFLy
3l7d7HiQHfKeljLXdNG2
=MYWT
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/531d9614.5030...@serverb.co.uk
script-with-language-extension
Hi, I am in the process packaging Net::Frame::Device (libnet-frame-device-perl) as part of a the fix to a bug. Net::Frame::Device includes two scripts that are installed to /usr/bin, but both have .pl extensions therefore giving me a Lintian warning. My initial thought on fixing this is to rename the files by overriding dh_auto_install in debian/rules... but I'm struggling to find out how to do this without explicitly writing the file names, which wouldn't accommodate new files in future releases. So far I've got the following: PACKAGE = $(shell dh_listpackages) TMP = $(CURDIR)/debian/$(PACKAGE) SNIP find $(TMP)/usr/bin -name '*.pl' Which does identify the files correctly... I'm just not sure where to go from here! My second thought.. was to relocate the files to e.g /usr/share/$(PACKAGE) and then provide symlinks in /usr/bin, but this perhaps seems to more work than necessary Cheers, Daniel Lintott signature.asc Description: OpenPGP digital signature
Re: How to deal with reviews in mentors.debian.net and repositories for new packaging work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26 February 2014 09:55:44 GMT+00:00, Emmanuel Kasper emman...@libera.cc wrote: I have uploaded a package on mentors.debian.net, and I got some review of my package suggesting some modifications (http://mentors.debian.net/package/vmtouch) Now that I have done the suggested changes, should I rather: A) delete the old package, upload a new one with same version number (and lose the reviewing suggestions) B) keep the old package online, upload a new one with same version number (at the expense of some confusion in the mentors.debian.net page) C) delete the old package, upload a new one with a new revision number (even if the changes are minimal) Leave the version number the same and upload to mentors again. The new package will appear above the old on the package page. I have also read on the list that some mentors like to have a link to a VCS to review the pacaking work. Is it possibile to host the packaging work on alioth when you're not a Debian Developper ? I know for instance NetBSD has an extra CVS repo called pkgsrc-wip where all newbies can out their stuff before it's added to the real thing. If not I can use github/gitorious. I believe you could use collab-maint but I have no experience with it myself. As you say alternatively use github or similar, I have done that for 3 of my packages. Using git will also allow you to use git-buildpackage. Details are in the wiki... But I don't have the link to hand. Greetings Emmanuel - --- Regards Daniel Lintott Sent from my Android device with K-9 Mail. Please excuse my brevity. -BEGIN PGP SIGNATURE- Version: APG v1.0.9 iQFDBAEBCAAtBQJTDcCqJhxEYW5pZWwgTGludG90dCA8ZGFuaWVsQHNlcnZlcmIu Y28udWs+AAoJEMw/9yOWzAkJsOUH/jWtPfLrqy1RT6X9Tig1uCqC65CbQl6YGvE4 ZfCKtCU+jUIZn+QDyCD+WdZkhW+f+Ck+NrmrJ7gAd8JZZLZiqIKaNKqmc+Hs4kBk EZ9p4XwHvVvVK7+Dr8yy1P/hC5yZytMm3i2vEx/+/Oz2pt22SGCl8CpQgYhsiYxD ll2KJVNzkhdB0eDa5IfNqX+vmu+Sno75m6fRKD0U182mt1Wavdz12YLv6Esp0zD2 XxSfoTk0u35boU5jo3MhNwtUZY1Y0DWuv2xXZnwPPZtiEN7fMpsAGO3YoOoyb8FC D+Mkf6Cnqs0GV9GLTVzdeYAg5czwkIWjLnPRnAKgsfulrQ14THU= =r4Vf -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/887b8dad-b67b-43c1-bcfa-0f59dfe53...@email.android.com
Bug#739003: libsocket6-perl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/02/14 23:38, gregor herrmann wrote: On Sat, 15 Feb 2014 22:33:15 +, Daniel Lintott wrote: replace dh $@ with dh $@ --buildsystem=perl_makemaker then dh will use Makefile.PL etc. and everything looks good The only snag is still going to be the missing LDFLAGS (relro in particular) for Socket6.so Hm, I'm not sure about that. Neither lintian nor blhc complained when I tried this approach. (And usually debhelper with compat level 9 just passes all required flags, and they are used unless the upstream build system messes with %Config in some crazy way). How/where did you see the problem? When I build it again (with --buildsystem and without the override) I get: [SNIP] which looks quite ok to me :) -fstack-protector is there, and also -Wl,-z,relro. Would it be preferable to patch the config.pl.in and add all the LDDLFLAGS there as opposed to in the rules file? If it's necessary that's an option. A bit more idiomatic would be an override that just adds missing stuff, like (untested) override_dh_auto_configure: dh_auto_configure -- LDDLFLAGS=... Cheers, gregor, who might well be missing something ... And sorted! It was the override causing the problem with the missing flags, so that's now rectified. I have made the necessary alterations to d/rules, released the changelog and pushed the changes to git. I haven't tagged the build as yet, as I wasn't sure exactly when you wanted this done? Regards, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJTAKuEAAoJEMw/9yOWzAkJYUQH/0+MepUrTgJpW9GbJRQJ+uKs a0ao+AMoO8bLDaq59EDzC8VlzylD+Ad6SfncmMp4zRohifQgNU2BL3+Fm/mVT5Z3 NJ3YdHtC1mGhA/c5o7pfAt6pyggveMGl+dudgAfQMuxi+WjWkMY251x20BUbC0/J 0Sa+Je0XURilpX6WR5puX+oy4Z0OmeX3F53cB3djMArMDlivjXooETOuepAw8ZRT j+Cpx5rn16eIjr5cGDvCNHD/FxVhZnK4yd6jQi4XCT0B32Qxipo9yMDn4ar3p7Tt XCorC0wCF5VvdrJ8guiPqVaGkanOpK4lWK7bvqdyeiavw/pPGTkD4eiYyNsBp/c= =nDq+ -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/5300ab84.3010...@serverb.co.uk
Bug#739003: RFS: libsocket6-perl/0.25-1 [ITA]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Gregor, On 14/02/14 23:30, gregor herrmann wrote: On Fri, 14 Feb 2014 20:32:57 +, Daniel Lintott wrote: Dear mentors, I am looking for a sponsor for my package libsocket6-perl * Package name: libsocket6-perl Version : 0.25-1 Upstream Author : Hajimu UMEMOTO u...@mahoroba.org * URL : http://search.cpan.org/~umemoto/ * License : BSD,ISC Section : perl It builds those binary packages: libsocket6-perl - Perl extensions for IPv6 Have you considered joing the Debian Perl Group? We'd be happy to have you and this package in our ranks, and you'd get support and sponsors there. Cf. https://wiki.debian.org/Teams/DebianPerlGroup/Welcome Cheers, gregor I hadn't thought about it... but I will indeed join the group. I shall drop and email to the group with my Alioth details. Regards Daniel Lintott -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJS/0YtAAoJEMw/9yOWzAkJPNUH/R/LXw8Eb6OnNp6AP6grVpEq rVnluGsomj13HaV0a7NuvlczyDn3xJTPwBEZYdJTgftcQD7ZjUy8UjhTa34otCUf C+o/9qk/JklBeqOJ1DKrKbz4yjgEL7jZDsmmf8Gp+1lI3YJKTZA9VodCiiKGuksj 6l7+vVx72bRj5rNnJNWUzGUSoTYysMqlEnxYFiHJvAWH6ppVlNtlh+lYca/IDL0a GY2dflMiWvy5GkFMcicyN1jZUwXrsVozgDJZecxfrsWegEsZZJsiyKa05bGwXDrV qoM6ew5oq8s1YNyzHj3KMYEPhj/EOr6Cy57ptj2KKoUEK3QupTSmEpN+jHS40Zk= =4RPR -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/52ff4631.5000...@serverb.co.uk
Re: Bug#739003: RFS: libsocket6-perl/0.25-1 [ITA]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/02/14 12:27, gregor herrmann wrote: On Sat, 15 Feb 2014 10:49:21 +, Daniel Lintott wrote: I am looking for a sponsor for my package libsocket6-perl Have you considered joing the Debian Perl Group? We'd be happy to have you and this package in our ranks, and you'd get support and sponsors there. I hadn't thought about it... but I will indeed join the group. I shall drop and email to the group with my Alioth details. Cool, see you over there :) Cheers, gregor I have now updated the libsocket6-perl package to make it part of the Debian Perl Group and would like to find a sponsor. I have pushed the changes to the pkg-perl repo on Alioth [1], I have also updated the package on Debian Mentors [2]. Regards, Daniel Lintott [1] http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libsocket6-perl.git [2] https://mentors.debian.net/package/libsocket6-perl -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJS/67fAAoJEMw/9yOWzAkJSREH/2s4GoU6wFhjBw9p7CqbhJUP EksbJFcB3+oIHCiff15pZxpoRafZW7BenlXunjmH0uTVWoXfAbJW8KXfJpqwG632 OkZ0fCfXoVh168jYDUg05GecKx5ZogTmhtaK9qAwpPj1pk22fVp+ZQTEOkutveOa BRW5U6+IEWowX8A8PEBdTLJ+oX0HDvoOa52h7p4Vv+ikKOKUXi+u1UYVmCDGAYLf tVBVWQWTB466N6/BkbXA2U9vRG0FSmX5jtJd5nPYSkgEqxFyR6BiycRVeOdxRWr2 5qu8PGYBuShY+FxNxSsjeCZ+I1ZRa4A7J3rt75eVHl8l0Du1WA3Mt+ryEtJyOvU= =Vmto -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/52ffaee0.6060...@serverb.co.uk
Bug#739003: libsocket6-perl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/02/14 19:00, gregor herrmann wrote: On Sat, 15 Feb 2014 16:49:07 +, Daniel Lintott wrote: Please take a look at http://pkg-perl.alioth.debian.org/policy.html and http://pkg-perl.alioth.debian.org/git.html if you haven't done so already to get libsocket6-perl into our git repos with the minor changes needed for a team-maintained package. Looking forward to seeing it appear at http://pet.debian.net/pkg-perl/pet.cgi Many thanks gregor, I shall read through the documents and get the necessary changes made And the package is already in git -- thanks! I've now, as per our usual workflow, added some TODO items to the top of debian/changelog. Don't hesitate to ask on the list or on IRC if my comments are too cryptic :) Cheers, gregor It took a while but I think I got there in the end! I've had to leave override_dh_auto_configure as it was trying use the configure file and not the Makefile.PL. I've also added to this the LDFLAGS for relro that were missing. Everything else has been completed as per the TODO ;) Cheers, Daniel Lintott -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJS/+efAAoJEMw/9yOWzAkJm/EIAJ0xAsdol+SQDDxrby2XhWHd td3EcXYDBBkHTZrYxei0muVu2SilBC7dfEb+ZLzCt3rlZl/eQ/8AeHUFG9mtBsiv hL9eotbr9HGcE/A7LvCUXUeuQXworgsPGBE3gphyZ7O95SVi2fF+CgU3lmvIoVf1 5D1GqBd8F54T3ScPbelpiliZOszVqfEbTf/jrFCM5/m26f2YNtbPXKqD9xABY6d3 oVYvE8pVZEsLkcdaafUEMXMIEpBt+1oReLyBSuz4vWyP0fJhdfRLAKsW7z07EW8z 14WewFqxjM1o4ax8cuEBbWV9cp3iy4TWHimXUdOhO0REfyo1J2M6Q38JUhZhjvA= =GaJ9 -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/52ffe79f.6060...@serverb.co.uk
Bug#739003: libsocket6-perl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/02/14 22:26, gregor herrmann wrote: On Sat, 15 Feb 2014 22:18:07 +, Daniel Lintott wrote: It took a while but I think I got there in the end! Thanks, I was already looking at the changes :) I've had to leave override_dh_auto_configure as it was trying use the configure file and not the Makefile.PL. I've also added to this the LDFLAGS for relro that were missing. Ha, that was the only piece I was thinking about, and I've just added a note to d/changelog about it. I might as well paste the summary here: replace dh $@ with dh $@ --buildsystem=perl_makemaker then dh will use Makefile.PL etc. and everything looks good Everything else has been completed as per the TODO ;) Indeed, looks perfect. Maybe you can take a last look at d/rules and make the change with the buildsystem, if it works for you as well; and then set the distribution from UNRELEASED to unstable in d/changelog. The only snag is still going to be the missing LDFLAGS (relro in particular) for Socket6.so Would it be preferable to patch the config.pl.in and add all the LDDLFLAGS there as opposed to in the rules file? Cheers, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJS/+srAAoJEMw/9yOWzAkJSg4IAL4GZV0al1MgQ5ySKiW1UAh5 pZj4iUdhHI6+yofX7uJ3/RH0Rk5kI4JRKaf5I+rzknGxPf7obWwLZaOdm9AyHoWf GweEwr7shpefzBDNJTtoz7PdPaKJ/qmhGAvIouzgK6J7oaAP/DIIx0wJtb15S8iY UUlDSBj5vsjbWKBqmHpOdgpy/u1G9gBsiM8n4ggAZzP7sFeSTSeMTFmCQ5DD2v4Q XfTzt9Yd08sHyuglLUwB9TMju5aRk1INJlbjDwRYD1iceolm0+j+upkgf96HHLXN WPW2ORvVceMNiXA+7OJomiVPm6EbSdIYO9bfocILBP/W7jIEQnfjWekFksbGgX4= =MScV -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/52ffeb2b.40...@serverb.co.uk
Bug#739003: RFS: libsocket6-perl/0.25-1 [ITA]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package libsocket6-perl * Package name: libsocket6-perl Version : 0.25-1 Upstream Author : Hajimu UMEMOTO u...@mahoroba.org * URL : http://search.cpan.org/~umemoto/ * License : BSD,ISC Section : perl It builds those binary packages: libsocket6-perl - Perl extensions for IPv6 To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libsocket6-perl Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libs/libsocket6-perl/libsocket6-perl_0.25-1.dsc More information about libsocket6-perl can be obtained from http://search.cpan.org/~umemoto/Socket6-0.25/ Changes since the last upload: libsocket6-perl (0.25-1) unstable; urgency=low * Imported Upstream version 0.25 * New maintainer (Closes: #738885) * Bump standards version to 3.9.5 (no changes) * [11eaa0be] debian/control + Add homepage field * Install socket6(3) manpage (Closes: #694083) * [8ee3ba01] Import patch to add missing IPv6 constants (Closes: #569981 LP: #522191) Thanks to David Madore for the patch * [c5f9120a] Update debian/watch * [9b65edf1] debian/rules + Add LDFLAGS to configure script to fix hardening-no-relro warning on Socket6.so * [71f53f90] debian/control + Add VCS fields * [24b9fbe0] debian/copyright +Convert to machine readable format -- Daniel Lintott dan...@serverb.co.uk Fri, 14 Feb 2014 20:14:52 + Regards, Daniel Lintott -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJS/n15AAoJEMw/9yOWzAkJugcH+gKi90dRSV8mnfweZbXpT0P9 5o2yZj7/eS//j7oWT+8NFjGqqqEwRwFGaJ/nhhVG7AEFM9/wh+FbpYuiEx6/f4v0 qOVYiq6y2YSVqOIL7ZsWJXycF9I+ydenHStqgkQDLj1/EHfgLrTAaEi8K03e8HXC HWEjGUvLHdqzxji0SQoOF2X8Hek+Z+pade4BSanVwcTsnlrzAwgtCf6lKAGXBK/a LfijXMtHGIjBpHudw956MqzCDi+PcDE2zdRrJWRWgcg13OqKXYx/gqVGYuKs+LPT Z6ejCpzelmfLnMgyli51Ccpr8+GlOZPUsys61J979jI7ZpNvkRrz5L/8ZF5zoNA= =qiZC -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/52fe7d79.4040...@serverb.co.uk
Bug#738624: RFS: dynamips/0.2.11-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package dynamips * Package name: dynamips Version : 0.2.11-1 Upstream Author : Flávio J. Saraiva flaviojs2...@gmail.com * URL : http://www.gns3.net/dynamips * License : GPLv2 Section : net It builds those binary packages: dynamips - Cisco 7200/3600/3725/3745/2600/1700 Router Emulator To access further information about this package, please visit the following URL: http://mentors.debian.net/package/dynamips Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/non-free/d/dynamips/dynamips_0.2.11-1.dsc More information about dynamips can be obtained from http://www.gns3.net/dynamips https://github.com/GNS3/dynamips Changes since the last upload: dynamips (0.2.11-1) unstable; urgency=low * [ab3a8d82] Bump standards-version to 3.9.5 - no changes * [b792229e] debian/watch - Remove obsolete githubredir * [278818eb] Imported Upstream version 0.2.11 * [f1fec7b5] Drop patches applied upstream + 20-stableMakefileHardening + 30-arm_support.patch * [4a4ab133] Patches to fix architecture detection in Makefile + 10-Makefile-Architecture - removed + MakefileArchitecture.patch - added * [98e2662c] debian/rules + Remove override_dh_install (Makefile fixed for DESTDIR) * [4ec13364] Add patch to fix lintian warning: + manpage-has-errors-from-man hypervisor_mode.7.gz 310: warning: macro `Bvm' not defined -- Daniel Lintott dan...@serverb.co.uk Tue, 11 Feb 2014 11:20:41 + Regards, Daniel Lintott -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJS+gzgAAoJEMw/9yOWzAkJb7UH+wYv3sq2adQhmzoUHxFjtjP4 6Wtt/QpBPf9MpHBu2BmXjaJT9xjBbWSMAM9ve9ex7+UznapA6oaO8VwAWuIu9riK 762T4I4fgJOrz5B28NmctcLNfiSOGj6STRFnac9pnXsALxitWhcWu7f8+55GXZcU mpO9vmRc9EYpSVqlEsC4EkI8/BY/vIM0QJVbW7luFc9c8X6avW9JRDk5gF+ku7J6 UjEK/y8VndVU6Rf+88tOkicj3e9oYC2wnLqPSBNTPfiCW5KF+hCQ0rACt8mXYcMn 5WLnTvCsdWdzjs28srDe0BdW3x88qt2/rVJjMwoJMPmdx7aZwG+4ZsD3TTF7ZLA= =Wnry -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/52fa0ce0.3000...@serverb.co.uk
Bug#738671: RFS: whatmask/1.2-1 [ITP]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Nick, Disclaimer: I'm not a DD, so can't upload your package but have looked at it, as it is of interest to me. Generally the package seems to be in very good shape and builds in a clean chroot fine. Just touching on the couple of lintian warnings: X: whatmask source: deprecated-configure-filename I would forward this to upstream for their attention [1] I: whatmask source: debian-watch-file-is-missing I have attached a watch file that seems to work okay (other watch file guru's may be able to optimise it). As upstream sign their releases, you can get uscan to check [2] this as well. I have included the line to check this in the watch file (again, it might not be perfect) The releases have been signed with key ID: E8882FE3 I: whatmask: spelling-error-in-binary usr/bin/whatmask GNU PUBLIC LICENSE GNU General Public License This will be easy enough to patch and again forward upstream. The error appears in usage.c:60 Hope this review is helpful for you and aids you in finding a sponsor. [1] http://lintian.debian.org/tags/deprecated-configure-filename.html [2] https://wiki.debian.org/debian/watch/#Cryptographic_signature_verification -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJS+pgdAAoJEMw/9yOWzAkJg4AH/RiyxLX1IvkOCHGqfnAyhoED cLNI6BUp6TXHqa11//nySvrSoHrIhBgY+ZJvO+d1WmoUzMI0MShcTC91mUYKgOIi 2zJDOK9PapwK3e7PJGHnIJP9jGykD2OaeEvCIC4LMp2OeAw1sE5K1z2tBDHxCDHL ll6JU7pQsRPFBB/UpuaRvCUScyj+VVLbE1uX1XsK3TivI2naKOeQtuH/pKKiJcz+ VFrNLx6TZFPQe3v96e+RK+yUnwdNjTEaurXPKyiV/Rbk/bEvDIY5CWPQZNGWzZ0c 3P0CdQNF2Ci8kxaGTDyR1+1cza4GwRS9iFlqXZ/BSby92y3zzYZ4EpQD0//UDC8= =OtT3 -END PGP SIGNATURE- version=3 opts=pgpsigurlmangle=s/$/.asc/ \ http://downloads.laffeycomputer.com/current_builds/whatmask/ whatmask-([\d\.]+\d)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
Re: question about the packaging helpers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Roelof, On 29/01/14 18:48, Roelof Wobben wrote: Hello, Im trying to learn myself the debian way of packaging. My ultimate goal is to become the gnome maintainer of Tanglu. Now I wonder where detailed information can be found about the packaging helpers dh and dh7 ? Roelof As someone who had recently learnt packaging myself, it would be well worth you taking a look at the following page [1]. In particular the New Maintainers Guide is very useful, as is Lucas' Packaging Tutorial. Moving on from them you'll want to get a basic understanding of the Debian Policy [2]. Also if you want information on what the particular Debhelper commands do... Best bet is to look at there repsective manpages. Hope that is of some help to you. Regards Daniel [1] https://mentors.debian.net/intro-maintainers [2] http://www.debian.org/doc/debian-policy/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJS6VP7AAoJEMw/9yOWzAkJQ3UH/02mAWVspsFpAk1+U32onXZh MAt3BaqxarO6m8VixjKT3jKzURdFHZA4EHWuKpkoiCCaFkux8eFhFEhO2OKPS3gT EUxHd8fFUHycM+ZCBGdmEL1wYwpmP0nshcHUDmIVY3v/Br/fDU+q58TkHYVVHs/x GkXPgMKVSM3hgeaq2/CLmUCiX4Octyhx/e7R6tes/Xysq8HnUrHo//sLFFTeAaCL c6tgBtUOmcelOLJNK5u7BCDJEJREZVXKFlcu5QAvHpJ3r4qO8vGhjoYFNk162IMt pKgEGYrz2Slns8Vsv/9KttuH7KFDLFfw7aUCQnHvJEdlSexkC3ol6y/O4irFm4Q= =aHf5 -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/52e95400.5060...@serverb.co.uk
Correcting a version number
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I have realised that in an earlier package upload, I made a blunder with regards the version of the package. The package was versioned as 0.5b0-1, though I somehow missed, despite testing the watch file that this should have been 0.5~b0-1. I have seen some discussion on correcting the version number, either by using an epoch or by adding an additional part to the version number. - From what I can see, the only way to fix the version number here is to use an epoch, but from what I've this should be avoided if possible, so does anyone have any other suggestion on how to correct this version number? Regards Daniel Lintott -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSp1S6AAoJEMw/9yOWzAkJ5T0H/jq9Hnma75BsYIEPX+8AvuPa 0BA+pVS2rjeaE8xticH2HROAMSUNUPgf9rVELeIvZ8Kh1ZUMtmtrXhYq0wurUSMX SasPhsNcb0tDu3oLBescufStkcInK732WXpGiIc6t0P3T+G77k5FEvQnrOqq6EX2 jafRnnm7SeZCmlIhzasyyBTRV+y0AhoJiBcG3w2znQF3npHtNmZSkqZ9Svfuq/RV m5ttiXxwokR6DbcWdIhMzQSMQ+5KyrjXLdyXPW238tbITT3Up34iq5HOYgyKL5rr xxa1suI9ebaxad79i3cUIEwNhlyZPxJHJ8Qyxgw3Uehg/8WQgJXIc2SGuu0SqEY= =DzI8 -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/52a754bb.8090...@serverb.co.uk
Re: Correcting a version number
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/12/13 18:59, Dominik George wrote: Hi, I have realised that in an earlier package upload, I made a blunder with regards the version of the package. Where is that package now? On mentors, or in Debian? -nik The package is in Debian [1] and the watch file status [2] [1] http://packages.debian.org/sid/vpcs [2] http://qa.debian.org/cgi-bin/watch?pkg=vpcs_0.5b0-1 Regards Daniel Lintott -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSp2i1AAoJEMw/9yOWzAkJIywH/jRYWhUHJ2/CkUiGOCZT+4HI xI333jvqMHDYQUHEaic+Odhvt0MUmyZZ3xr1bUfIRlVTZuSsDCXqwwoDosxrWNDF slyOAEWpVW3bhzmsZiq2EwvEtKFRpv12i1wgRTcmEp4TnETTkehnwP4OnE3T8Anm gqLlsU/6xXnvyuL2yiuL/6HV+ZyBcKGPsgMgqtgTl1mGJ5Re1VIZdUl9g1WnbpIR R7XXF7U1o3C+eaBGJOaM8fbnNcLtxU6fanTZJ0DX+z0suP8XhZi595Lno6st99im UXnrO3fHxH0ncODFPJJ7KQl2sHxzaXHmvlpTwbcN8pt8LGmyE7NdUQR3YhQhkA4= =JPFw -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/52a768b5.9070...@serverb.co.uk
Re: Correcting a version number
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/12/13 19:21, Dominik George wrote: [2] http://qa.debian.org/cgi-bin/watch?pkg=vpcs_0.5b0-1 In that special case, I'd even say your versioning mistake is good because upstream's ~ notation is a mess. That char is reserved for Debian ;) (yes, that's false and not so humble ;))! Why not keep your version numbering as it is and use version mangling in the watch file instead to match.upstream? -nik The output from the above seems a little confusing (to me) as upstream don't use ~ which can be seen in the upstream-url, as well as on the upstream sf page [1] It's entirely possible that there is also a mistake in the watch file... which wouldn't help matters. Regards Daniel [1] http://sourceforge.net/projects/vpcs/files/0.5/beta/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSp2sUAAoJEMw/9yOWzAkJxoEH/3PoECk57dURUGsFKj0wyWP9 ee4vhNqruYY+qWYYFssBBxM1khx0JyRb/m8L8qIBYKjSbuE8ycnCE6xDpseX7ZC/ kvDESKkjQC3qz9AVd+/FgKIScMMIlGI+31DRS/r2EsBhyIEQMywmooOMG0Cwt6So wh85z6n8ySWZ/pUJAv0mOkzhi+avvX2gaiV55cLiV8HiDdpldQ1oXPpPtt+KmQ8v Jg3TeLVKkHH9ZdbVXPqkozi7pql14C18judWEfO16hNWLMKFvi3Ge3IvdGxXWOyG 37gfSVD8PujpnQfMHE8KikKl3q7hXdqQsz6CQbmH5h6uValYMKfEgrePdXFdS/I= =op0c -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/52a76b14.5090...@serverb.co.uk
Multiple Licenses
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Mentors, I've just begun packaging phpipam [1] and I'm now delving into completing the copyright file. The project itself is licensed under GPL-3 which is fine. I have substituted any embedded copies of code which are available in Debian, but am still left with a couple of PEAR modules, not present in Debian. Currently I'm a little unsure of the licenses of the remaining embedded code copies. For example functions/PEAR/OLE/* is licensed under PHP-2.02. I've found some talk about the PHP license in relation to Debian, but I'm unsure how it would apply in this case. Any advice would be welcome, before I continue with the packaging. Regards Daniel Lintott [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731713 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSpPmsAAoJEMw/9yOWzAkJ1b4H/jyicgLBpXoChtesEFtAqXDe n8iEXB4vOx0FITp4dFckgwQUqsNqViOUXE6X0mFq/x565QHyd/cSTVeijebLEHDo 2uKQsEeiu5idMnKSOA2so49w08DiAXbR1LLodFpyUmcRsOZ0Xodk77FXki+N6hDn p4z87GuljyCv15Rx3AofZwTsEMtactQWQFhj7g60eQMI+ETqL0PAX5unHIGEvbPK P1PBqQj/jrZinilX4iolNgdw/MsRv++8bZ/8e7NSN5D+Hl3ZwLuCIQ+pU9DA3OM+ zOp7wVxcE+emcs4D5JXF5rIfPUz+gNdlH91F4myS3m++0xj9t0jAhjna2qbPyeg= =mzfH -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/52a4f9ad.2060...@serverb.co.uk
Update a Qt Linguist Translation in GNS3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi mentors, I have just been working on a bug [1] in the GNS3 package. The issue turned out to be an error in the Spanish translation (one missing variable) GNS3 uses Qt4-Linguist for the translations, which take a .ts file and generate a .qm file The issue I currently face is that the .qm files aren't regenerated when the package is built, so simply patching the .ts won't actually fix the bug. How do I include the updated .qm in a new build? Regards Daniel Lintott [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714112 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSjjeXAAoJEMw/9yOWzAkJqPsIAKg/FIaQDwL/xxGumBCLd69C c4mO9YcAdPY/HqPyMMCRu0FglKY2nkVux0cAp1wp5hRyZpM7JRl7H/FziQqleGa+ Je7CyFDy0HGBYuFfISf40BfHcFdD/t+AcJnE6yVkTJuzYDnCb+Im8BiBGvwvQA22 gcaUxE2W9EG7D1vyqo/dmJVUl7LtVU/8UAjHEIHTQO4a14oU+zyb7wwWZm93CS8j GhcYIkYBS9oSemzFrwLwahcfV7+2tFGqVTMl5Ns9MRalbKIzoktEsunvTepZphY2 C0zTK+ZtM8/kACx2reBO0GFQ/G1Wm0jKHUsRsNcDztUSvs80DO4Gd34ajVsCcFA= =mYG/ -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/528e379b.4060...@serverb.co.uk
Bug#729091: RFS: gtkiostream/1.3.0
Hi Matt, On 09/11/13 23:21, Matt Flax wrote: You caught another bug, thank you. I have uploaded gtkiostream-1.3.0.fixedDeb2.tar.gz to the sf.net site. I have removed the machineGenerated directory from the source dist. by using 'nodist' tags in the Makefile.am. This should be the last of these types of bugs as there aren't any other machine generated directories in the project tooling ... I should have picked this problem up when I was fixing the last bug you reported. Thanks again for your help. Matt Getting much closer now! Different error this time, but still related to the machineGenerated code, though this time it's because it cannot find the file! I've attached a snippet of the log again, so you can see the exact failure point. Running a grep on the test folder finds the two following references: ./test/Makefile.am - line 75 ./test/Makefile.in - line 605 Regards Daniel g++ -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/gtk-2.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/harfbuzz -I../include -I../test/machineGenerated -I../src/machineGeneratedGtkiostream -g -O2 -c -o ORBTest-ORBTest.o `test -f 'ORBTest.C' || echo './'`ORBTest.C ORBTest.C:30:24: fatal error: ORBTestICE.H: No such file or directory #include ORBTestICE.H
Bug#729091: RFS: gtkiostream/1.3.0
Hi Matt, On 09/11/13 02:36, Matt Flax wrote: Hi again, I have now fixed this problem and uploaded the source code to sf.net, the new release file name is : gtkiostream-1.3.0.fixedDeb.tar.gz Attatched is the diff between the original source release and the one on sf.net. Thanks again for catching this bug. Please let me know of any others which you find. Matt Got further this time, then it hit another machine generated code error. I've attached the relevant portion of the build log for you. Regards Daniel g++ -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/gtk-2.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/harfbuzz -I../include -I../test/machineGenerated -I../src/machineGeneratedGtkiostream -g -O2 -c -o ORBTest-ORBTestICE.o `test -f 'machineGenerated/ORBTestICE.C' || echo './'`machineGenerated/ORBTestICE.C In file included from machineGenerated/ORBTestICE.C:21:0: ../test/machineGenerated/ORBTestICE.H:42:9: error: #error Ice version mismatch: an exact match is required for beta generated code # error Ice version mismatch: an exact match is required for beta generated code ^ machineGenerated/ORBTestICE.C:30:9: error: #error Ice version mismatch: an exact match is required for beta generated code # error Ice version mismatch: an exact match is required for beta generated code ^ machineGenerated/ORBTestICE.C: In member function 'virtual void ORBTEST::ORBTestICE::__writeImpl(IceInternal::BasicStream*) const': machineGenerated/ORBTestICE.C:378:47: error: no matching function for call to 'IceInternal::BasicStream::startWriteSlice(const string, bool)' __os-startWriteSlice(ice_staticId(), true); ^ machineGenerated/ORBTestICE.C:378:47: note: candidate is: In file included from /usr/include/Ice/OutgoingAsync.h:24:0, from /usr/include/Ice/Proxy.h:25, from ../test/machineGenerated/ORBTestICE.H:29, from machineGenerated/ORBTestICE.C:21: /usr/include/Ice/BasicStream.h:330:10: note: void IceInternal::BasicStream::startWriteSlice(const string, int, bool) void startWriteSlice(const std::string typeId, int compactId, bool last) ^ /usr/include/Ice/BasicStream.h:330:10: note: candidate expects 3 arguments, 2 provided make[3]: *** [ORBTest-ORBTestICE.o] Error 1
Bug#714310: RFS: polyphone/1.1-1 [ITP]' from 'RFS: polyphone/1.0-1 [ITP]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Davy, N.B: I'm not a DD, so cannot sponsor your package myself. I'm also fairly new to reviewing, so forgive me if I miss something! The Review: 1. As your package is not yet in debian, the entries in debian/changelog should be merged to a single entry, for the version of the package that will enter Debian. This will also ensure your ITP bug is closed correctly upon upload. 2. a. debian/compat - The current level is 9 b. debian/control - Build depend on dephelper can be changed to debhelper (= 9) 3. debian/rules - The dh_make comment can be removed from this file 4. The package builds successfully in my unstable chroot. Lintian reports the following: N: Processing binary package polyphone (version 1.1-1, arch amd64) ... I: polyphone: spelling-error-in-binary usr/bin/polyphone ment meant I: polyphone: spelling-error-in-binary usr/bin/polyphone INFORMATIONS INFORMATION I: polyphone: spelling-error-in-binary usr/bin/polyphone dONt don't Regards Daniel Lintott -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSfloQAAoJEMw/9yOWzAkJlgYIAKI7L6ra1NtSZH57B5Bd65Qr boXxT3Gt2X8nQT7e5hAVC7nl6dNiqFd63ob/KVHFUyBDIrGme1JzXtaS6DQns4hg T4LotybsGCn7sWVpdT94QbJwqtJBecK3RpB9pr87bJQDfOd+d71WtZrkj0mabt/T COvDUE/SwIVJdaxqIz48BFrzFDkWGbhKswKmJ78sz5b8b/Z2FlV5RWnQ6WMrvg2B 9QZDoSHaP2lCWFXGgIZlRG9h+er482LkL6/nz26erlrhArov7CqCjyfAVrfRH5dd ojpA3MJOW2TZN9d0foJn8O49Ssc3eKHUVl4N4xpeY/T+UzhvFgq/g2bqx7lY218= =rkOe -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/527e5a13.6070...@serverb.co.uk
Bug#729091: RFS: gtkiostream/1.3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/11/13 22:47, Matt Flax wrote: Thanks for the log. It looks the same as before. My suspicion is that the machineGenerated folder and containing files are still on your system. This would happen if the original source code was left on the system, it may be better to start from scratch... Is it possible to totally remove the gtkiostream directory and untar from the latest one on sourceforge ? Also it would be interesting to know which version of slice2cpp is being used ... flatmax@debian-packager:~$ slice2cpp -v 3.5.0 thanks Matt I did start fresh with the new tarball. I can see both before and after extraction there is a machineGenerated folder in the test folder. [...]/gtkiostream-1.3.0/test/machineGenerated As for the version of slice2cpp, it will be the latest version available in sid which is 3.5.0 according to packages.d.o My workflow for building the package is as follows: 1. First build a source only package (debuild -S) 2. Then build the binary using pbuilder which is loading a sid chroot to ensure it builds in a clean environment. Regards Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSfr/1AAoJEMw/9yOWzAkJYq4H/ij57nM9Hgz+zDWhGatbinUE gQztarEZEJM+mhnnsAVwtllOxWHxvGtbjoGuEGw7FzwvOO9ZSoK+DyMpO/YxUfdt HzGFtrOWZqtuz8eizGDGLPIXPFtnFeOU+rUn8Ye4Ptp3xeYrxAtnb2hCovh9dWwD uKB+UFHRni0GWvrlZKYkAD/FwfA0J+6dgATC1jsAiDRTRRBre+37boaMo0v5HJOz jwrdUmMfZFqRbNduzRT1nLMeAgu21ciQ5IgW8c7oGLAOX4tkAx7V9rEctsq1A8B5 Ipk1fyfjpZTk7qIbpU8ucdHZDHBpcDDy1fRc+IJtoouNz7cLd2DfoOb3BaJtYpc= =Qg+Y -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/527ebff5.90...@serverb.co.uk
Re: Sponsor for the gtkiostream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Matt, I'm not a DD myself, so can't upload your package but I shall give my review of it, in the hope it can help you to find a sponsor. It may be worth you filing an RFS bug against the pseudo-package sponsorship-requests [1] and the standard form for an RFS [2], this may also increase your chances of finding a sponsor. It is actually already packaged, the debian directory is distributed with the source code : https://sourceforge.net/projects/gtkiostream/ The generally accepted standard is to keep the Debian packaging separate from the upstream source. I'm not sure what the exact state would be since you are upstream as well [3] Reading some old posts on the debian-mentors list it should be sufficient to just drop the debian directory from the source tarball, but this would need clarification from someone with more experience than myself By sponsoring this package you will close the following bugs : Closes: #709641 Closes: #722527 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722527 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709641 You will also replace some very old packages of mine with much better and newer implementations : Replaces: wsola, mffm-fftw1, libaudiomask1 Replaces: wsola-dev, mffm-fftw-dev, libaudiomask-dev As it stands your package wouldn't automatically close these bugs as they are not closed in the latest changelog entry. Also as this package is not yet in Debian, you should merge the changelog entries to the single version being uploaded. Other Items - debian/compat - This should be 9 - debian/control - Build-Depends for debhelper should be debhelper (= 9) - debian/rules - You can remove the 'boilerplate' comment from here The package also failed to build for me in an unstable chroot using pbuilder. I have attached a log showing the build error. Running lintian against the source package, gives me the follwing: N: Processing source package gtkiostream (version 1.3.0-1, arch source) ... W: gtkiostream source: debhelper-but-no-misc-depends gtkiostream-doc I: gtkiostream source: debian-watch-file-is-missing Regards Daniel Lintott [1] http://mentors.debian.net/sponsors [2] http://mentors.debian.net/sponsors/rfs-howto/gtkiostream [3] https://wiki.debian.org/UpstreamGuide -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSfPoeAAoJEMw/9yOWzAkJIeAH/iKAaTaZTzgYqBke7VLdtrrP E1WXvytLmj1/SBrcmtqB/jk0C44bdIBSo3UQaxf8OqgXZ083TMf3JHDFud79uBgR h0Q/70HHfUpJew/LCvbgyZTqWOEhINo4TNNdfisOa0fYKTGCb0Eeivr7fO5ZpPK/ hExv0IWPBKItj5R5pUULhsTkw3aImsm36IA20EE+uL7sgFfaDE8d4lKRYbaWuRdm dYXc+HJ6sD5xw+8dheZf7ZaGVmy+dxvFA2kvCWINYzC3qzRP4GREFU8WUgilPfaU iAbgtEmqbC29oRlSB83Kwb6ZEE4xedDb4DeegfyGqZvcJ+cAeMzPGqVJYxsq9Mc= =f9kf -END PGP SIGNATURE- libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../include -ImachineGeneratedGtkiostream -I../../src/machineGeneratedGtkiostream -g -O2 -c machineGeneratedGtkiostream/ORBICE.C -fPIC -DPIC -o .libs/libORB_la-ORBICE.o In file included from machineGeneratedGtkiostream/ORBICE.C:21:0: machineGeneratedGtkiostream/ORBICE.H:42:9: error: #error Ice version mismatch: an exact match is required for beta generated code # error Ice version mismatch: an exact match is required for beta generated code ^ machineGeneratedGtkiostream/ORBICE.C:30:9: error: #error Ice version mismatch: an exact match is required for beta generated code # error Ice version mismatch: an exact match is required for beta generated code ^ machineGeneratedGtkiostream/ORBICE.C: In member function 'virtual void ORB::ORBICE::__writeImpl(IceInternal::BasicStream*) const': machineGeneratedGtkiostream/ORBICE.C:530:47: error: no matching function for call to 'IceInternal::BasicStream::startWriteSlice(const string, bool)' __os-startWriteSlice(ice_staticId(), true); ^ machineGeneratedGtkiostream/ORBICE.C:530:47: note: candidate is: In file included from /usr/include/Ice/OutgoingAsync.h:24:0, from /usr/include/Ice/Proxy.h:25, from machineGeneratedGtkiostream/ORBICE.H:29, from machineGeneratedGtkiostream/ORBICE.C:21: /usr/include/Ice/BasicStream.h:330:10: note: void IceInternal::BasicStream::startWriteSlice(const string, int, bool) void startWriteSlice(const std::string typeId, int compactId, bool last) ^ /usr/include/Ice/BasicStream.h:330:10: note: candidate expects 3 arguments, 2 provided make[3]: *** [libORB_la-ORBICE.lo] Error 1 make[3]: Leaving directory `/tmp/buildd/gtkiostream-1.3.0/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/gtkiostream-1.3.0' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/gtkiostream-1.3.0' dh_auto_build: make -j1 returned exit code 2 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build
Bug#729091: RFS: gtkiostream/1.3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Matt, Re: http://lists.debian.org/debian-mentors/2013/11/msg00068.html I have just attempted the build again and it fails in the same place as before, with the same error. This is using a fully updated Debian sid chroot. Regards Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSfWfBAAoJEMw/9yOWzAkJsQ8H/1ZsKr6z/PWJeN/cCTPIWCUd YncFDOBr9GtpC2bNCPHPcZV/RME4OQ9uvvBxLhxxPd3TUP1fFB6PpejghWipBwHN bhwldqAAZv5rtHNcpT+6kNU/TpeVF88qElXpDjBsyCALm1NZfZOOgz9q8I0ThKRF ovt/C+AyE9RlAAHrnRMV+eBRbyDoJyp+efsV5irHLniW9C9Y4nWrhOVcdLf8kdgA NusexLNnCDByx046jb+n65Amaly26l+L92hj+Z+3DlJWO0lEs2xOvapG/QinA2RQ cic06g5zRxUPG3EXDPoWk0tDZZzOcGBzijKQbxUX6M1BfWa39+OlJKS5KBfDU30= =WwES -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/527d67c2.6030...@serverb.co.uk
Question about Bugs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Mentors, I have a bug report that I've been working on from Ubuntu and have now managed to solve the issue. The bug in question also affects Debian, but there isn't a bug report in Debian for it. In the changelog I can close the Ubuntu bug with (LP: #XXX), but should I also file the bug report in Debian and close that as well? Regards Daniel Lintott -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSeQNbAAoJEMw/9yOWzAkJjicH/Rnaj+9Ls+n+0kAsV3/ccin1 ZLPX+Zfhr2QXj5wKxQEBEK6X25kWXDQu3XOyY6d30dYfyeeQiawRh9q6tpFABTwy NXR5gtW5QN4u9nFpmZ3MJ+7xlSiafGKaqzZRJug8WsY0U6ZM0QcjziJuBMyOWZOT voBrtRBVUU8I2JtvdGbQp096H3YVuIxiBgp3Mqo2nQdM4xnXuHJtY7PJSDtv0J6E XXnP1jLHhYLpn5sVJtYGg5AewNwqwkewRZ2cC4WK6vs9P4d5KAYnfnbCym/lglfx taIBtJgVG59bqoULvGJyVnMeBgjw0ehRo3Z/GtcNCqA1Zh9D7GlvZumpg0BCGes= =Ur1d -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/52790360.2020...@serverb.co.uk
Bug#725737: RFS: gns3/0.8.6-1 [ITA]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Andrew, On 24/10/13 21:52, Andrew Shadura wrote: [...] I believe it's a wrong approach. You shouldn't install anything under /usr/local unless absolutely required. Previous versions of the package didn't do that; please try to do it the same way here. I've just uploaded the updated package to mentors. It now includes a small patch to change where GNS3 looks to copy these files from, so they don't have to reside in /usr/local I've also removed any scripting that related to the use of /usr/local in the postinst, prerm, postrm scripts. Regards, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSal4HAAoJEMw/9yOWzAkJ2T8H/0KHr0xrm4BRjeOVBk00HjKh 10fBQpQZu6O393LqQ9HZMro7B6jyBbvDiNAiJcU7R+hnvU0MFj81p7YHvYE8dUrI rllRKvgk5N59oIA4dDXl/sT/PsySbcsfc17xdNALtZbhm9CiLvI+ZT9E3yrCxcBA Bt5w14V8gQNoDFRSkjOIhmM1m1EZM3df7AeMekT2F7MpiIX5riAI5OsDtnmaWEOt rKBEBUzd4fzHKKPt+UsuG2NKuj2UDCUpdCpDuCUpwJ/AaW2YboM14Y+fGR07KBk2 s0Fd7X0dXUhl0UNlxmw5xnxJ6csxV9G5HhRMyQMbIcdPpevb72u3xPlfKehS12s= =bXz8 -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/526a5e07.1030...@serverb.co.uk
Bug#725737: RFS: gns3/0.8.6-1 [ITA]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I have updated the gns3 package to the latest upstream version * Package name: gns3 Version : 0.8.6-1 Upstream Author : Jeremy Grossmann cont...@gns3.net * URL : http://www.gns3.net * License : GPL-2.0+ Section : net It builds those binary packages: gns3 - Graphical Network Simulator To access further information about this package, please visit the following URL: http://mentors.debian.net/package/gns3 Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/contrib/g/gns3/gns3_0.8.6-1.dsc More information about GNS3 can be obtained from http://www.gns3.net Changes since the last upload: gns3 (0.8.6-1) unstable; urgency=low * New maintainer (Closes: #725345) * [5d312bc7] Imported Upstream version 0.8.6 * [231483cb] Switch build-system to debhelper * [f0792800] Bump standards version to 3.9.4 * [f23759cf] Switch copyright to machine readable format (DEP-5) and update for new maintainer * [17f68dca] Update postinst, postrm scripts. Create prerm script * [26b1a6bd] Update debian/watch * [e2aef91e] Added dependencies for xdotool, xterm (Closes: #626464) * [4065b7d8] Add recommends: wireshark (Closes: #622159) * [44fe48e3] [rules] Add DH_ALWAYS_EXCLUDE=Lang_it.ts.gz * [117338f3] Update VCS Fields -- Daniel Lintott dan...@serverb.co.uk Thu, 24 Oct 2013 12:09:53 +0100 Regards, Daniel Lintott -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJSaSUJAAoJEMw/9yOWzAkJ/vUH/1GtSkizTIHY1iqstT7yNZG0 WtgN8Dnf6RAOdfuLABksUKFahszwzSTfjzLf/+ZQnjhrT+YcBLkhlD84uclTHjmZ hR2B/mHO7v+MfIbhbXpsLirPix5jyaXDisoCDXNQqa29ppeciUTCF9kqGwMEEC3q M4lMhr4/ISCiC3gUzAF6/uOPTSMKU2LvOJiSzee4wEQBrKFRdn+3Dhw9oWIQ7pPM HMb9dxwZuhr8oNRNNywBqL7PYGugqYt1sgV8wVn91U6sm0HrtOvg/QxH9xFb9z90 x2PtBsP75ovSiRJklX3r7y0Y7BCQZhV72wKPk7AqrdfQ90lPhq6HoMqtVW8m4m4= =bEbR -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/52692509.1010...@serverb.co.uk
