scantailor maintainership and alioth
The current maintainer of scantailor filed a RFA (bug #816504) and I would like to take over maintainership. I have not packaged for Debian before but I think I mostly understand the process. I still have to fix a couple things, but I've managed to make a .deb for a recently released version that works and passes the lintian checks. I have a question about Alioth though. The debian package is being maintained at (http://anonscm.debian.org/cgit/collab-maint/scantailor.git). Can I get access to that, or do I need to upload this to github instead and change the Vcs fields in the debian/control file correspondingly? And sorry for the spam; accidentally sent this to the wnpp mailing list the first time.
pkg-fonts team needs help to maintain font-forge
Hello, looking at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745732 which has been languishing for two years, it looks like the pkg-fonts team could need some help to maintain this package. This new upstream version is needed by at least two other fonts, one of which has a serious bug (#822762) which is fixed in a new release that requires a newer font-forge. So your contribution to this team will be really useful and highly appreciated. Hopefully there are enough volunteers in the team to at least review/sponsor your work. If not, I can have a try at it. https://wiki.debian.org/Teams/pkg-fonts Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers
* Adam Borowski , 2016-04-27, 05:27: export DEB_BUILD_OPTIONS=parallel=`grep ^processor /proc/cpuinfo|wc -l` Refuse the temptation to parse /proc/cpuinfo. Use nproc(1) instead. -- Jakub Wilk
Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers
Hi, some general notes: Adam, do you plan to sponsor the package? in this case can I set you as owner? :) Fabian, why are you trying to package an upstream snapshot? (not asking to package 1.5.1, I'm just wondering about why a new library should eventually enter Debian in a snapshot form) cheers, G. Il Mercoledì 27 Aprile 2016 5:30, Adam Borowski ha scritto: On Tue, Apr 26, 2016 at 10:22:32PM +0200, Fabian Wolff wrote: > * Package name: libtcod I'm afraid that it builds only on 64-bit architectures (I tried amd64 and arm64), on 32-bit ones (x32 armhf i386) it fails with: dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libtcod0/DEBIAN/symbols doesn't match completely debian/libtcod0.symbols --- debian/libtcod0.symbols (libtcod0_1.6.0~pre1+dfsg-1_x32) +++ dpkg-gensymbolsZSmCIg2016-04-27 02:14:30.890101840 + @@ -1511,7 +1511,7 @@ (c++)"TCODSystem::newMutex()@Base" 1.6.0~pre1 (c++)"TCODSystem::newSemaphore(int)@Base" 1.6.0~pre1 (c++)"TCODSystem::newThread(int (*)(void*), void*)@Base" 1.6.0~pre1 - (c++)"TCODSystem::readFile(char const*, unsigned char**, unsigned long*)@Base" 1.6.0~pre1 +#MISSING: 1.6.0~pre1+dfsg-1# (c++)"TCODSystem::readFile(char const*, unsigned char**, unsigned long*)@Base" 1.6.0~pre1 (c++)"TCODSystem::registerSDLRenderer(ITCODSDLRenderer*)@Base" 1.6.0~pre1 (c++)"TCODSystem::saveScreenshot(char const*)@Base" 1.6.0~pre1 (c++)"TCODSystem::setClipboard(char const*)@Base" 1.6.0~pre1 @@ -1560,6 +1560,7 @@ (c++)"TCODZip::~TCODZip()@Base" 1.6.0~pre1 TCOD_CRenderer@Base 1.6.0~pre1 (c++)"TCOD_path_func(int, int, int, int, void*)@Base" 1.6.0~pre1 + _ZN10TCODSystem8readFileEPKcPPhPj@Base 1.6.0~pre1+dfsg-1 end_struct@Base 1.6.0~pre1 error@Base 1.6.0~pre1 internalListener@Base 1.6.0~pre1 So you need to adjust the symbols file. Also, it'd be nice if you added --parallel to the dh call, it massively speeds up builds[1] on any non-museal machine. It's default in upcoming debhelper 10. Meow! [1]. To actually make --parallel work, the person running the build needs to set: export DEB_BUILD_OPTIONS=parallel=`grep ^processor /proc/cpuinfo|wc -l` but this is outside the packaging. -- A tit a day keeps the vet away.
Re: Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers
On Wed, Apr 27, 2016 at 11:40:47AM +0200, Jakub Wilk wrote: > * Adam Borowski , 2016-04-27, 05:27: > >export DEB_BUILD_OPTIONS=parallel=`grep ^processor /proc/cpuinfo|wc -l` > > Refuse the temptation to parse /proc/cpuinfo. Use nproc(1) instead. Oh, that's something new (for the value of "new" of "added upstream on 2009-11-06, to Debian in 8.1-1 for squeeze"). Good to know. And it works with /proc not mounted. -- A tit a day keeps the vet away.
Bug#822672: RFS: freecell-solver/4.2.0-0.1 [NMU]
Control: owner -1 !
Am 26.04.2016 um 12:10 schrieb Shlomi Fish:
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "freecell-solver"
Hi Shlomi,
First of all thank you for updating freecell-solver. Your effort is much
appreciated. I intend to sponsor your package and to upload it to the
DELAYED/10 queue, should there be no reaction from the maintainer within
the next couple of days.
In general the changes look good to me but there is one serious issue
and a couple of smaller, non-intrusive ones which are already present in
the current package. While we are at it we should fix them.
You can use Lintian to detect them and by creating the lintianrc file in
~/.config/lintian/lintianrc
with the following content:
info=yes
display-info=yes
display-experimental=yes
pedantic=yes
show-overrides=yes
color=auto
verbose=yes
or by looking at this page
http://mentors.debian.net/package/freecell-solver
The serious one is the incomplete copyright file:
The copyright file states that all code is in the public domain. This is
not correct. There are source files with different license headers, e.g
Your own code is licensed under the MIT/Expat license.
board_gen/make_pysol_freecell_board.py (GPL-2+)
patsolve-shlomif/patsolve/ga/mt19937.c (LGPL)
Copyright (c) 2002 Tom Holroyd (Expat/MIT License)
Copyright (C) 2014 insane coder (http://insanecoding.blogspot.com/,
http://asprintf.insanecoding.org/)
+
+Permission to use, copy, modify, and distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Please update debian/copyright accordingly.
Optional: You could transform the file to copyright format 1.0.
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Other issues:
Only debian/control.in should be modified because the package uses
DEB_AUTO_UPDATE_DEBIAN_CONTROL from CDBS.
Dependency on debhelper should be debhelper (>= 9). Please remove the
duplicate entry debhelper (>= 7) in debian/control and update
debian/control.in accordingly.
debian/control.in: Please update the Vcs-fields to use Debian's
canonical URLs.
Vcs-Browser:
https://anonscm.debian.org/cgit/collab-maint/freecell-solver.git
Vcs-Git: https://anonscm.debian.org/git/collab-maint/freecell-solver.git
Please install the upstream changelog (NEWS.txt) in debian/rules with
DEB_INSTALL_CHANGELOGS_ALL := NEWS.txt
Since you are upstream for freecell-solver please consider to fix the
following minor issues:
There is a typo in main.c: explictly => explicitly
Please consider to write a man page for freecell-solver-config.
There is a spelling error in fc-solve.6 allows to => allows one to.
You could cryptographically sign your package, so that debian/watch can
verify its integrity.
https://lintian.debian.org/tags/debian-watch-may-check-gpg-signature.html
You might want to run check-all-the-things on your code. It executes
different checkers which may help you to improve freecell-solver.
e.g.
pep8 --ignore W191 . (Improvement suggestions how to style your code
according to pep8)
find -type f -iname '*.sh' -exec checkbashisms {} +
There are multiple *.sh files that don't seem to have a #! interpreter line.
There are more typos which can be found with
codespell --quiet-level=3
$ cppcheck -j1 --quiet -f . | grep -vF 'cppcheck: error: could not find
or open any of the paths given.'
[fc_pro_range_solver.c:429]: (error) Memory leak: binary_output.file
[state.h:32]: (error) Invalid number of character '{' when these macros
are defined: 'COMPACT_STATES'.
[state.h:32]: (error) Invalid number of character '{' when these macros
are defined: 'DEBUG_STATES'.
[state.h:32]: (error) Invalid number of character '{' when these macros
are defined: 'INDIRECT_STACK_STATES'.
Regards,
Markus
signature.asc
Description: OpenPGP digital signature
Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers
Control: owner -1 ! On Wed, Apr 27, 2016 at 09:45:18AM +, Gianfranco Costamagna wrote: > Adam, do you plan to sponsor the package? in this case can I set you as > owner? :) Sure, can do. I did most of the review already, and if we decide otherwise wrt 1.6-pre1, can always unset. > Fabian, why are you trying to package an upstream snapshot? > (not asking to package 1.5.1, I'm just wondering about why a new library > should > eventually enter Debian in a snapshot form) Upstream says: # Note that 1.6 is bleeding edge and still needs polishing before it can # replace 1.5. It is recommended you use 1.5. On the other hand, moving from SDL1.2 to SDL2 is a big change, so I understand wanting to use the new version already, both for programs using this library and to avoid doing this part of packaging twice. On the third hand, though, there's a significant risk the API/ABI might change before final 1.6. -- A tit a day keeps the vet away.
Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers
Hi Adam, >Sure, can do. I did most of the review already, and if we decide otherwise >wrt 1.6-pre1, can always unset. thanks a lot for that, it helps in avoiding double checking of packages :) and double reviews :D ># Note that 1.6 is bleeding edge and still needs polishing before it can ># replace 1.5. It is recommended you use 1.5. > >On the other hand, moving from SDL1.2 to SDL2 is a big change, so I >understand wanting to use the new version already, both for programs using >this library and to avoid doing this part of packaging twice. +1 for moving away from SDL1.2 >On the third hand, though, there's a significant risk the API/ABI might>change >before final 1.6. well, if 1.6 gets released in a short time, we might not even have reverse-dependencies in the archive, so... who cares? /me says something about putting the package on experimental cheers! and thanks Gianfranco
Bug#822770: RFS: pidgin-sipe/1.21.0-1 -- Pidgin plugin for MS Office Communicator and MS Lync
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for package "pidgin-sipe", whose source code is at: https://anonscm.debian.org/cgit/collab-maint/pidgin-sipe.git or you may also: dget -x http://mentors.debian.net/debian/pool/main/p/pidgin-sipe/pidgin-sipe_1.21.0-1.dsc It builds this binary package: pidgin-sipe - Pidgin plugin for MS Office Communicator and MS Lync Changes since the last upload: pidgin-sipe (1.21.0-1) unstable; urgency=medium * New upstream release. - Feature #91: Support embedded XML as buddy photo URL - Feature #90: Add AppStream metadata file - Feature #89: Improve "Join scheduled conference" dialog - Feature #87: Support multiple HTTP cookies - Feature #85: XML raw extract should ignore name space - Fixed #311: Crash when SIP transport becomes invalid - Fixed #293: Mandatory wsa:MessageID node missing - add support for Lync File Transfer protocol - add build options to "About SIPE plugin" message * Drop fix-hppa-ftbfs.patch (applied upstream). * Drop pidgin-sipe-dbg in favour of autogenerated debug package. * Remove obsolete build dependency on libzephyr-dev. * Enable bindnow hardening flag. -- Jakub Adam Wed, 27 Apr 2016 10:16:53 +0200 Regards, Jakub signature.asc Description: OpenPGP digital signature
Re: scantailor maintainership and alioth
On Wed, Apr 27, 2016 at 4:28 PM, Jason Crain wrote: > The current maintainer of scantailor filed a RFA (bug #816504) and I > would like to take over maintainership. I have not packaged for Debian > before but I think I mostly understand the process. I still have to fix > a couple things, but I've managed to make a .deb for a recently released > version that works and passes the lintian checks. Check out this page in case you need a refresh: https://mentors.debian.net/intro-maintainers > I have a question about Alioth though. The debian package is being > maintained at (http://anonscm.debian.org/cgit/collab-maint/scantailor.git). > Can I get access to that, or do I need to upload this to github instead > and change the Vcs fields in the debian/control file correspondingly? You can get access, see here: https://wiki.debian.org/Alioth/Git#Collab_Maint_project https://wiki.debian.org/Alioth/PackagingProject https://lists.debian.org/debian-devel-announce/2015/02/msg1.html -- bye, pabs https://wiki.debian.org/PaulWise
Re: Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers
* Adam Borowski , 2016-04-27, 12:02: export DEB_BUILD_OPTIONS=parallel=`grep ^processor /proc/cpuinfo|wc -l` Refuse the temptation to parse /proc/cpuinfo. Use nproc(1) instead. Oh, that's something new (for the value of "new" of "added upstream on 2009-11-06, to Debian in 8.1-1 for squeeze"). Good to know. For pre-squeeze, there's "getconf _NPROCESSORS_ONLN". And for stretch, there's "dpkg-buildpackage -Jauto" (not to be confused with -jauto, which is evil). -- Jakub Wilk
Re: [Pkg-fonts-devel] pkg-fonts team needs help to maintain font-forge
On Wed, Apr 27, 2016 at 4:49 PM, Raphael Hertzog wrote: > looking at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745732 > which has been languishing for two years, it looks like the pkg-fonts > team could need some help to maintain this package. There has been some efforts around this recently, check the pkg-fonts-devel archives. > This new upstream version is needed by at least two other fonts, one > of which has a serious bug (#822762) which is fixed in a new release that > requires a newer font-forge. The new upstream fontforge also breaks building at least one font. > So your contribution to this team will be really useful and highly > appreciated. Hopefully there are enough volunteers in the team > to at least review/sponsor your work. If not, I can have a try at > it. Indeed. -- bye, pabs https://wiki.debian.org/PaulWise
Re: Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers
On Wed, Apr 27, 2016 at 6:40 PM, Jakub Wilk wrote: > And for stretch, there's "dpkg-buildpackage -Jauto" (not to be confused with > -jauto, which is evil). -jauto replaces auto with the number of processors. Why is that evil? What does -Jauto do? -- bye, pabs https://wiki.debian.org/PaulWise
Bug#822672: RFS: freecell-solver/4.2.0-0.1 [NMU]
On Wed, Apr 27, 2016 at 6:19 PM, Markus Koschany wrote: > First of all thank you for updating freecell-solver. Your effort is much > appreciated. I intend to sponsor your package and to upload it to the > DELAYED/10 queue, should there be no reaction from the maintainer within > the next couple of days. Please note that the maintainer surfaced in the meantime: https://lists.debian.org/msgid-search/87a8kfv59x@errge.nilcons.com -- bye, pabs https://wiki.debian.org/PaulWise
Bug#822672: RFS: freecell-solver/4.2.0-0.1 [NMU]
Control: noowner -1 ! Am 27.04.2016 um 12:44 schrieb Paul Wise: > On Wed, Apr 27, 2016 at 6:19 PM, Markus Koschany wrote: > >> First of all thank you for updating freecell-solver. Your effort is much >> appreciated. I intend to sponsor your package and to upload it to the >> DELAYED/10 queue, should there be no reaction from the maintainer within >> the next couple of days. > > Please note that the maintainer surfaced in the meantime: > > https://lists.debian.org/msgid-search/87a8kfv59x@errge.nilcons.com > Thanks for the heads-up. Shlomi, I suggest that you coordinate the upload with Gergely now. Gergely, please see https://lists.debian.org/debian-mentors/2016/04/msg00600.html for my comments on the package available at http://mentors.debian.net/package/freecell-solver Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#822770: RFS: pidgin-sipe/1.21.0-1 -- Pidgin plugin for MS Office Communicator and MS Lync
control: owner -1 ! control: tags -1 moreinfo Hi Jakub, can you please explain the changes below (to me or in changelog) -usr/lib/*/purple-2/libsipe.so usr/lib/purple-2 -usr/share/locale/* -usr/share/pixmaps/* -DEB_CONFIGURE_EXTRA_FLAGS := --enable-purple --disable-telepathy --enable-openssl=no +DEB_CONFIGURE_EXTRA_FLAGS := --libdir=/usr/lib --enable-purple --disable-telepathy --enable-openssl=no + +export DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow 1) maybe you can try to hardening=+all and --libdir=/usr/lib seems a good way to avoid multiarch... why? 2) I see "libpurple-dev (>= 2.10.11-1.1)" and this on changelog: + - add support for Lync File Transfer protocol (Jakub Adam) + * requires libpurple >= 2.12.0 maybe you should bump the version? other stuff LGTM G. Il Mercoledì 27 Aprile 2016 12:30, Jakub Adam ha scritto: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for package "pidgin-sipe", whose source code is at: https://anonscm.debian.org/cgit/collab-maint/pidgin-sipe.git or you may also: dget -x http://mentors.debian.net/debian/pool/main/p/pidgin-sipe/pidgin-sipe_1.21.0-1.dsc It builds this binary package: pidgin-sipe - Pidgin plugin for MS Office Communicator and MS Lync Changes since the last upload: pidgin-sipe (1.21.0-1) unstable; urgency=medium * New upstream release. - Feature #91: Support embedded XML as buddy photo URL - Feature #90: Add AppStream metadata file - Feature #89: Improve "Join scheduled conference" dialog - Feature #87: Support multiple HTTP cookies - Feature #85: XML raw extract should ignore name space - Fixed #311: Crash when SIP transport becomes invalid - Fixed #293: Mandatory wsa:MessageID node missing - add support for Lync File Transfer protocol - add build options to "About SIPE plugin" message * Drop fix-hppa-ftbfs.patch (applied upstream). * Drop pidgin-sipe-dbg in favour of autogenerated debug package. * Remove obsolete build dependency on libzephyr-dev. * Enable bindnow hardening flag. -- Jakub Adam Wed, 27 Apr 2016 10:16:53 +0200 Regards, Jakub
Re: Bug#819395: RFS: stormlib-listfiles/2015-04-20-1 [ITP]
Hi Pali and mentors, (redirecting the question to -mentors, because I don't have a strong opinion on this) >Looks like we do not have exact license text as those file "were >generated" by brute-force methods by more people and put into public >domain. People names (or nick names) are already included in copyright >file. That is all what I know and cannot do more. If there are or there >are not law problems it is probably question for other people... there should be a verbatim copy of the license included in the upstream tarball look e.g. to https://ftp-master.debian.org/REJECT-FAQ.html License II and III sections so, either you have to document how the license is obtained, or how to reproduce the files generation. I know licenses are a waste of time for somebody (they were for me when I started my contributions in Debian :p )... but they are the best way to get your package rejected by ftpmasters! So, this point is really a showstopper for the inclusion in Debian of the tool (BTW if you want to ask ftpmasters about their opinion let me know their answer). I would like to avoid uploading and get a reject, but I would consider an upload with a ping to ftpmasters about this issue. cheers, Gianfranco Il Martedì 26 Aprile 2016 23:07, Pali Rohár ha scritto: On Thursday 21 April 2016 10:16:29 Pali Rohár wrote: > On Tuesday 19 April 2016 08:36:49 Gianfranco Costamagna wrote: > > Hi, > > > > >There is no more info about it just as it is public domain, no > > >more license texts... What to write into paragraph then?? > > > > everything is a license, and public domain is a license too. > > https://codesearch.debian.net/results/License:%20public-domain/page > > _0 > > > > G. > > Looks like we do not have exact license text as those file "were > generated" by brute-force methods by more people and put into public > domain. People names (or nick names) are already included in > copyright file. That is all what I know and cannot do more. If there > are or there are not law problems it is probably question for other > people... Gianfranco, what else needs to be done? I think I done everything what I was able to do... -- Pali Rohár pali.ro...@gmail.com
Bug#819394: RFS: stormlib/9.20-1 [ITP]
Hi, the packaging seems good now, I would like to ask you a final question: how do you feel about using the same license for debian packaging and upstream? (asking about changing GPL-3+ to MIT). Forwarding patches otherwise would be impossible without a relicense. and the copyright still needs to be updated: >So in this case, how to update copyright? Just for src/lzma? Or for all >other embedded libraries even when they are not used and needed? you have to list *every* copyright and license on copyright file, regardless of it being used or not. This is a showstopper for ftpmasters. let me know, Gianfranco Il Lunedì 18 Aprile 2016 22:24, Pali Rohár ha scritto: Now I updated stormlib package on mentors.debian.net. -- Pali Rohár pali.ro...@gmail.com
Bug#822770: RFS: pidgin-sipe/1.21.0-1 -- Pidgin plugin for MS Office Communicator and MS Lync
Hi Gianfranco, thanks for your review. On 04/27/2016 01:28 PM, Gianfranco Costamagna wrote: > can you please explain the changes below (to me or in changelog) > > -usr/lib/*/purple-2/libsipe.so usr/lib/purple-2 > -usr/share/locale/* > -usr/share/pixmaps/* After removing pidgin-sipe-dbg, pidgin-sipe remained the sole binary package that is generated from the source, and debhelper started installing the files directly under debian/pidgin-sipe instead of debian/tmp, so those lines in pidgin-sipe.install moving files from one location to the other aren't needed any longer. > +export DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow > > > 1) maybe you can try to hardening=+all I updated this in git and re-uploaded to mentors. > and --libdir=/usr/lib seems a good way to avoid multiarch... > why? Pidgin searches for protocol plugins only in /usr/lib/purple-2. Multiarch location doesn't work and thus I have to avoid it here. This change reflects the above mentioned line which used to be in pidgin-sipe.install: usr/lib/*/purple-2/libsipe.so usr/lib/purple-2 > 2) I see "libpurple-dev (>= 2.10.11-1.1)" > > and this on changelog: > + - add support for Lync File Transfer protocol (Jakub Adam) > + * requires libpurple >= 2.12.0 > > maybe you should bump the version? We don't have recent enough Pidgin (only 2.10.11) in Debian. I've raised a bug against the package [1] requesting an update. Until its maintainer makes a new upload, though, file transfer won't be available. Also I see I've made a mistake in the (upstream) changelog; it should be 2.10.12, not 2.12.0... Regards, Jakub [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822782 signature.asc Description: OpenPGP digital signature
Re: Bug#819394: RFS: stormlib/9.20-1 [ITP]
On Wednesday 27 April 2016 13:01:20 Gianfranco Costamagna wrote: > >So in this case, how to update copyright? Just for src/lzma? Or for all > >other embedded libraries even when they are not used and needed? > > you have to list *every* copyright and license on copyright file, regardless > of it being used or not. > This is a showstopper for ftpmasters. You may want to give "cme update dpkg-copyright" a try. See https://github.com/dod38fr/config-model/wiki/Updating-debian-copyright-file-with-cme HTH -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers
Hi everyone, thanks for the reviews! > Fabian, why are you trying to package an upstream snapshot? > (not asking to package 1.5.1, I'm just wondering about why a new library > should > eventually enter Debian in a snapshot form) I'm not packaging a random snapshot. I have based the package on the 1.6.0-pre1 upstream release that's hidden under "Tags" here: https://bitbucket.org/libtcod/libtcod/downloads > Upstream says: > # Note that 1.6 is bleeding edge and still needs polishing before it can > # replace 1.5. It is recommended you use 1.5. In an email conversation with Richard Tew, the upstream maintainer, he assured me that "1.6 is stable, and at least as stable as 1.5 codewise. Games have been released based on it, in places such as the google play store for android apps. The core thing I can recall holding it back is the need to rewrite the tutorial [...]." So I think it is fine to go for 1.6. Other than that, I will try to fix the problems with the symbols file as soon as possible. Again, thanks everyone for the reviews! Cheers, Fabian
Bug#822770: marked as done (RFS: pidgin-sipe/1.21.0-1 -- Pidgin plugin for MS Office Communicator and MS Lync)
Your message dated Wed, 27 Apr 2016 13:59:31 + (UTC) with message-id <210962072.5188270.1461765571288.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#822770: RFS: pidgin-sipe/1.21.0-1 -- Pidgin plugin for MS Office Communicator and MS Lync has caused the Debian Bug report #822770, regarding RFS: pidgin-sipe/1.21.0-1 -- Pidgin plugin for MS Office Communicator and MS Lync to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 822770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for package "pidgin-sipe", whose source code is at: https://anonscm.debian.org/cgit/collab-maint/pidgin-sipe.git or you may also: dget -x http://mentors.debian.net/debian/pool/main/p/pidgin-sipe/pidgin-sipe_1.21.0-1.dsc It builds this binary package: pidgin-sipe - Pidgin plugin for MS Office Communicator and MS Lync Changes since the last upload: pidgin-sipe (1.21.0-1) unstable; urgency=medium * New upstream release. - Feature #91: Support embedded XML as buddy photo URL - Feature #90: Add AppStream metadata file - Feature #89: Improve "Join scheduled conference" dialog - Feature #87: Support multiple HTTP cookies - Feature #85: XML raw extract should ignore name space - Fixed #311: Crash when SIP transport becomes invalid - Fixed #293: Mandatory wsa:MessageID node missing - add support for Lync File Transfer protocol - add build options to "About SIPE plugin" message * Drop fix-hppa-ftbfs.patch (applied upstream). * Drop pidgin-sipe-dbg in favour of autogenerated debug package. * Remove obsolete build dependency on libzephyr-dev. * Enable bindnow hardening flag. -- Jakub Adam Wed, 27 Apr 2016 10:16:53 +0200 Regards, Jakub signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi >thanks for your review. you are welcome! >Pidgin searches for protocol plugins only in /usr/lib/purple-2. Multiarch >location doesn't work and thus I have to avoid it here. This change reflects >the above mentioned line which used to be in pidgin-sipe.install: oh indeed, >We don't have recent enough Pidgin (only 2.10.11) in Debian. I've raised a bug >against >the package [1] requesting an update. Until its maintainer makes a new upload, >though, >file transfer won't be available. Also I see I've made a mistake in the >(upstream) >changelog; it should be 2.10.12, not 2.12.0... BTW a debdiff with the changes files shows this: -rw-r--r-- root/root /usr/share/appdata/pidgin-sipe.metainfo.xml you seem to have an extra file now, please consider removing it if you think it is useless. >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822782 this package is in lowNMU threshold, you might consider also proposing an NMU on the bug, and ping me to review it. you might consider starting from the Ubuntu package https://patches.ubuntu.com/p/pidgin/pidgin_1:2.10.12-0ubuntu5.patch in the ubuntu4 upload I minimized the delta with Debian, so you might want to take the orig tarball from there, pick the patches you think are good, and ping me back. (bonus point if you provide me a new debdiff for Ubuntu too!) signed and uploaded! cheers, Gianfranco--- End Message ---
Bug#822672: RFS: freecell-solver/4.2.0-0.1 [NMU]
On Wed, 27 Apr 2016 13:12:34 +0200 Markus Koschany wrote: > Control: noowner -1 ! > > Am 27.04.2016 um 12:44 schrieb Paul Wise: > > On Wed, Apr 27, 2016 at 6:19 PM, Markus Koschany wrote: > > > >> First of all thank you for updating freecell-solver. Your effort is much > >> appreciated. I intend to sponsor your package and to upload it to the > >> DELAYED/10 queue, should there be no reaction from the maintainer within > >> the next couple of days. > > > > Please note that the maintainer surfaced in the meantime: > > > > https://lists.debian.org/msgid-search/87a8kfv59x@errge.nilcons.com > > > > Thanks for the heads-up. Shlomi, I suggest that you coordinate the > upload with Gergely now. Gergely, please see > > https://lists.debian.org/debian-mentors/2016/04/msg00600.html > > for my comments on the package available at > > http://mentors.debian.net/package/freecell-solver > Thanks! Will do. And I appreciate your comments. Regards, Shlomi Fish > Regards, > > Markus > -- - Shlomi Fish http://www.shlomifish.org/ “So, who the hell is Qoheleth?” - http://shlom.in/qoheleth Emma Watson is not acting in films for money. She is acting in films for a shitload of money. — http://www.shlomifish.org/humour/bits/facts/Emma-Watson/ Please reply to list if it's a mailing list post - http://shlom.in/reply .
Bug#822794: RFS: ocrmypdf/4.0.7-2 -- add an OCR text layer to PDF files
Package: sponsorship-requests Severity: normal Control: block 822535 by -1 Dear mentors, I am looking for a sponsor for an update to ocrmypdf. * Package name: ocrmypdf Version : 4.0.7-2 Upstream Author : James R. Barlow * URL : https://github.com/jbarlow83/OCRmyPDF * License : Expat Section : graphics Changes since the last upload: * Switch to depend and build-depend on libjpeg-turbo instead of libjpeg8. Thanks to Pino Toscano for the suggestion. (Closes: #822535) * Fix autopkgtest: - Set SETUPTOOLS_SCM_PRETEND_VERSION. - Use pytest-runner. - Delete the .pc directory (and set rw-build-tree restriction). * Bump standards version to 3.9.8; no changes required. Download with dget: dget -x http://mentors.debian.net/debian/pool/main/o/ocrmypdf/ocrmypdf_4.0.7-2.dsc Or build it with gbp: gbp clone --pristine-tar https://git.spwhitton.name/ocrmypdf cd ocrmypdf git verify-tag debian/4.0.7-2 # if you have my key git checkout debian/4.0.7-2 gbp buildpackage Thanks. -- Sean Whitton signature.asc Description: PGP signature
Bug#822794: marked as done (RFS: ocrmypdf/4.0.7-2 -- add an OCR text layer to PDF files)
Your message dated Wed, 27 Apr 2016 15:44:29 + with message-id <20160427154429.ga6...@chase.mapreri.org> and subject line Re: Bug#822794: RFS: ocrmypdf/4.0.7-2 -- add an OCR text layer to PDF files has caused the Debian Bug report #822794, regarding RFS: ocrmypdf/4.0.7-2 -- add an OCR text layer to PDF files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 822794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Control: block 822535 by -1 Dear mentors, I am looking for a sponsor for an update to ocrmypdf. * Package name: ocrmypdf Version : 4.0.7-2 Upstream Author : James R. Barlow * URL : https://github.com/jbarlow83/OCRmyPDF * License : Expat Section : graphics Changes since the last upload: * Switch to depend and build-depend on libjpeg-turbo instead of libjpeg8. Thanks to Pino Toscano for the suggestion. (Closes: #822535) * Fix autopkgtest: - Set SETUPTOOLS_SCM_PRETEND_VERSION. - Use pytest-runner. - Delete the .pc directory (and set rw-build-tree restriction). * Bump standards version to 3.9.8; no changes required. Download with dget: dget -x http://mentors.debian.net/debian/pool/main/o/ocrmypdf/ocrmypdf_4.0.7-2.dsc Or build it with gbp: gbp clone --pristine-tar https://git.spwhitton.name/ocrmypdf cd ocrmypdf git verify-tag debian/4.0.7-2 # if you have my key git checkout debian/4.0.7-2 gbp buildpackage Thanks. -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On Wed, Apr 27, 2016 at 08:11:52AM -0700, Sean Whitton wrote: > I am looking for a sponsor for an update to ocrmypdf. Feel free to directly ping me for simple uploads of packages I've already sponsored you once :) (if you want to) > gbp clone --pristine-tar https://git.spwhitton.name/ocrmypdf uploaded. BTW, I'd kinda prefer to see `dpkg-parsechangelog -SVersion` instead of using sed in d/rules and in that d/t/test-suite. enjoy! :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message ---
Re: Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers
On Wed, Apr 27, 2016 at 12:40:59PM +0200, Jakub Wilk wrote: > * Adam Borowski , 2016-04-27, 12:02: > >>>export DEB_BUILD_OPTIONS=parallel=`grep ^processor /proc/cpuinfo|wc -l` > >>Refuse the temptation to parse /proc/cpuinfo. Use nproc(1) instead. > >Oh, that's something new (for the value of "new" of "added upstream on > >2009-11-06, to Debian in 8.1-1 for squeeze"). Good to know. > > For pre-squeeze, there's "getconf _NPROCESSORS_ONLN". At least one Debian derivative, Dyson, has: draconis:[~]$ dpkg --print-architecture illumos-amd64 draconis:[~]$ getconf _NPROCESSORS_ONLN getconf: Invalid argument (_NPROCESSORS_ONLN) so let's not advertise getconf, as -j`something with no stdout output` results in a fork bomb. On the other hand, nproc works everywhere I tried. -- A tit a day keeps the vet away.
Bug#822747: RFS: f-el/0.18.2-1 -- modern API for working with files and directories in Emacs Lisp
Hello, On Wed, Apr 27, 2016 at 06:52:18AM +, Gianfranco Costamagna wrote: > Hi, source-only uploaded :) Thanks. I'm sure you realised that I had you and mapreri in mind when I wrote "Note to sponsors using deb-o-matic" ;) > > I also think the bug is in DoM, so I would like to see how buildd > performs. > > Note: I do source uploads, because other Debian derivatives might rebuild > everything with buildds, so I think this way we are sure the package can > be safely binNMUed, avoiding later RC bugs :) It built successfully on the central buildd o/ -- Sean Whitton signature.asc Description: PGP signature
Re: Bug#816542: RFS: connman/1.31-0.1 [RC]
control: tags -1 pending control: tags -1 patch Hi, I followed up on 822393 and uploaded a patch on deferred/5. I did also import the new 1.32 release, dropping the two cherry-picks from the upstream git. the patch is the following Index: connman-1.32/src/firewall.c === --- connman-1.32.orig/src/firewall.c +++ connman-1.32/src/firewall.c @@ -25,6 +25,7 @@ #include +#define _LINUX_IF_H #include #include Index: connman-1.32/src/iptables.c === --- connman-1.32.orig/src/iptables.c +++ connman-1.32/src/iptables.c @@ -30,6 +30,7 @@ #include #include #include +#define _LINUX_IF_H #include #include and the explanation is on #822393 bug. TLTR: the fix is ugly, but the bug is in kernel 4.5. let me know if you have a better patch, otherwise that one will go in unstable. cheers, G. Il Lunedì 25 Aprile 2016 5:45, Adam Borowski ha scritto: On Sun, Apr 24, 2016 at 02:19:59PM +0200, Mateusz Łukasik wrote: > Pong back. > > http://mentors.debian.net/debian/pool/main/c/connman/connman_1.21-1.3.dsc > > I was tested it on Ubuntu 16.04 and all is fine. But alas, it doesn't build on current unstable. #822393 which looks like a problem between iptables-dev and libc6-dev rather than in connman -- but whatever the cause, uploading connman would be no good at the moment. -- A tit a day keeps the vet away.
Bug#816542: marked as done (RFS: connman/1.21-1.3 [RC])
Your message dated Wed, 27 Apr 2016 17:12:22 + (UTC) with message-id <2118046859.5312113.1461777142688.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#816542: RFS: connman/1.31-0.1 [RC] has caused the Debian Bug report #816542, regarding RFS: connman/1.21-1.3 [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 816542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: high Dear mentors, I am looking for a sponsor for my package "connman" * Package name: connman Version : 1.31-0.1 Upstream Author : Intel Corporation * URL : https://git.kernel.org/cgit/network/connman/connman.git * License : GPL-2 Section : net It builds those binary packages: connman- Intel Connection Manager daemon connman-dev - Development files for connman connman-doc - ConnMan documentation connman-vpn - Intel Connection Manager daemon - VPN daemon To access further information about this package, please visit the following URL: http://mentors.debian.net/package/connman Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/connman/connman_1.31-0.1.dsc Changes since the last upload: connman (1.31-0.1) unstable; urgency=medium * Non-maintainer upload. [ Shawn Landden ] * New upstream release (1.29) (Closes: #742408) - Drop 02-test-pbkdf2-sha1-maximum-salt-len-should-be-32-instead.patch * Conflict with resolvconf (Closes: #763628) * Conflict with wicd-daemon instead of wicd metapackage (Closes: #745874, #797638) * Enable pptp and l2tp vpn plugins (Closes: #751234) * debian/copyright: some files have moved, use kernel.org git url for source * debian/control: new upstream url http://01.org/connman [ Mateusz Łukasik ] * Take git changes from git to version 1.29 it never was upload to Debian. * New upstream release (1.31) (Closes: #813580, #813647) * Refresh 01-init-script-lsb-headers.patch. * debian/connman.install: update for new files. -- Mateusz Łukasik Fri, 12 Feb 2016 11:32:17 +0100 Regards, Mateusz Łukasik --- End Message --- --- Begin Message --- closing this one in the meanwhile. g. Il Mercoledì 27 Aprile 2016 19:11, Gianfranco Costamagna ha scritto: control: tags -1 pending control: tags -1 patch Hi, I followed up on 822393 and uploaded a patch on deferred/5. I did also import the new 1.32 release, dropping the two cherry-picks from the upstream git. the patch is the following Index: connman-1.32/src/firewall.c === --- connman-1.32.orig/src/firewall.c +++ connman-1.32/src/firewall.c @@ -25,6 +25,7 @@ #include +#define _LINUX_IF_H #include #include Index: connman-1.32/src/iptables.c === --- connman-1.32.orig/src/iptables.c +++ connman-1.32/src/iptables.c @@ -30,6 +30,7 @@ #include #include #include +#define _LINUX_IF_H #include #include and the explanation is on #822393 bug. TLTR: the fix is ugly, but the bug is in kernel 4.5. let me know if you have a better patch, otherwise that one will go in unstable. cheers, G. Il Lunedì 25 Aprile 2016 5:45, Adam Borowski ha scritto: On Sun, Apr 24, 2016 at 02:19:59PM +0200, Mateusz Łukasik wrote: > Pong back. > > http://mentors.debian.net/debian/pool/main/c/connman/connman_1.21-1.3.dsc > > I was tested it on Ubuntu 16.04 and all is fine. But alas, it doesn't build on current unstable. #822393 which looks like a problem between iptables-dev and libc6-dev rather than in connman -- but whatever the cause, uploading connman would be no good at the moment. -- A tit a day keeps the vet away.--- End Message ---
Re: request more advice: lintian warnings and python-tldp + ldp-docbook-stylesheets
Hi Martin, sorry for the lag >>For python-tldp (source) which creates python3-tldp (binary): >Rename the upstream or change the name of the source package in >debian/control to say 'tldp'? just the changelog and control file (Source section) the binary is good called python-tldp >OK. I will just leave the package building with that particular >lintian warning. wonderful >If I change debian/source/format to anything besides '3.0 (native)', >my package no longer builds from the working directory. > >Here's what works (right now): > > https://github.com/martin-a-brown/python-tldp/ > cd python-tldp > debuild -us -uc > >Can you help me replace the command 'debuild -us -uc' with another >that I can use after setting debian/source/format to '3.0 (quilt)'? >(Oh, and I'm happy to make any other changes necessary) print the error :) but I guess you need to have the orig tarball in the parent directory. dpkg-buildpackage will compare the sources, and bother you against adding patches in case the source trees differs from the pristine tarball. so, download the source tarball, call it tldp_version.orig.tar.whatever (I always dpkg-buildpackage, wait for the failure, and then copy-paste the name dpkg is expecting) >And, I certainly understand the reasoning for the watch file and the >separate responsibilities of the version and release values. I just >don't know how to handle that from a single source tree, it seems. you have to tag releases, and use them as orig tarballs, simple as that let me know if I can help more Gianfranco
Bug#814291: marked as done (RFS: libneo4j-client/0.9.0-1 [ITP])
Your message dated Wed, 27 Apr 2016 18:18:23 + (UTC) with message-id <1656210730.5389326.1461781103263.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#814291: RFS: libneo4j-client/0.8.0-1 has caused the Debian Bug report #814291, regarding RFS: libneo4j-client/0.9.0-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 814291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "libneo4j-client" Package name: libneo4j-client Version : 0.8.0-1 Upstream Author : Chris Leishman (myself) URL : https://github.com/cleishm/libneo4j-client License : Apache-2.0 Section : devel It builds those binary packages: libneo4j-client-doc - Documentation for libneo4j-client, a client library for Neo4j libneo4j-client5 - Client library for the Neo4j graph database libneo4j-client5-dev - Development files for libneo4j-client, a client library for Neo4j neo4j-client - Command line shell for the Neo4j graph database To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libneo4j-client Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libn/libneo4j-client/libneo4j-client_0.8.0-1.dsc More information about libneo4j-client can be obtained from https://git.io/libneo4j-client. Regards, Chris Leishman --- End Message --- --- Begin Message --- Hi, sponsoring with some changes: -remove autotools -one single changelog entry -add harderning flags in rules. attaching the debian directory to this email and uploading on deferred/5, to let you review my changes. cheers, G. Il Lunedì 25 Aprile 2016 13:30, Chris Leishman ha scritto: I believe these points have now been addressed. Would you mind reviewing again and giving any other feedback? Thanks a lot! Cheers, Chris On 1 April 2016 at 21:54, Gianfranco Costamagna wrote: control: owner -1 ! >control: tags -1 moreinfo > > > >hi, lets review > >changelog: single entry >control: std-version is 3.9.7 >please use dh-autoreconf (control, rules) >"libc6-dev" <-- why? > >check-all-the-things review >$ codespell --quiet-level=3 > >$ cppcheck -j1 --quiet -f . | grep -vF 'cppcheck: error: could not find or >open any of the paths given.' > >$ flawfinder -Q -c . > > >other stuff looks good to me. >I dind't run yet lintian and the package, will do when you fix the above > > > >Il Mercoledì 10 Febbraio 2016 2:30, Chris Leishman ha >scritto: > > > >Package: sponsorship-requests >Severity: wishlist > >Dear mentors, > >I am looking for a sponsor for my package "libneo4j-client" > >Package name: libneo4j-client >Version : 0.8.0-1 >Upstream Author : Chris Leishman (myself) >URL : https://github.com/cleishm/libneo4j-client >License : Apache-2.0 >Section : devel > >It builds those binary packages: > > >libneo4j-client-doc - Documentation for libneo4j-client, a client library for >Neo4j >libneo4j-client5 - Client library for the Neo4j graph database >libneo4j-client5-dev - Development files for libneo4j-client, a client library >for Neo4j >neo4j-client - Command line shell for the Neo4j graph database > >To access further information about this package, please visit the following >URL: http://mentors.debian.net/package/libneo4j-client > > >Alternatively, one can download the package with dget using this command: > >dget -x >http://mentors.debian.net/debian/pool/main/libn/libneo4j-client/libneo4j-client_0.8.0-1.dsc > > >More information about libneo4j-client can be obtained from >https://git.io/libneo4j-client. > >Regards, >Chris Leishman > libneo4j-client_0.9.1-1.debian.tar.xz Description: application/xz --- End Message ---
Bug#821220: marked as done (RFS: python-django-tagging [NMU] [RC])
Your message dated Wed, 27 Apr 2016 18:27:13 + (UTC) with message-id <614542862.5442518.1461781633546.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#821220: RFS: python-django-tagging [NMU] [RC] has caused the Debian Bug report #821220, regarding RFS: python-django-tagging [NMU] [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 821220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor to update the python-django-tagging package. The package fails to build from source, since December 2015. I updated the package to the latest upstream version, which required a bit of fixing with respect to the git-dpm metadata. This means that the package does build from source (fixing the RC bug). https://anonscm.debian.org/cgit/python-modules/packages/python-django-tagging.git/ Thanks, Chris signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Control: tags -1 patch control: tags -1 pending Hi, uploaded on deferred/5 let me know if I have to cancel or I can speed it up. I also tagged the git repo and pushed the changes. thanks for your contribution to Debian! Gianfranco Il Sabato 16 Aprile 2016 21:06, Christopher Baines ha scritto: Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor to update the python-django-tagging package. The package fails to build from source, since December 2015. I updated the package to the latest upstream version, which required a bit of fixing with respect to the git-dpm metadata. This means that the package does build from source (fixing the RC bug). https://anonscm.debian.org/cgit/python-modules/packages/python-django-tagging.git/ Thanks, Chris--- End Message ---
Bug#820543: marked as done (RFS: python-django-feincms [NMU] [RC])
Your message dated Wed, 27 Apr 2016 18:34:05 + (UTC) with message-id <1645436211.5475357.1461782045378.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#820543: RFS: python-django-feincms [NMU] [RC] has caused the Debian Bug report #820543, regarding RFS: python-django-feincms [NMU] [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 820543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-django-feincms Severity: important Dear mentors, I am looking for a sponsor to update the python-django-feincms package. The package has 3 RC bugs, the earliest dating back to June 2014 (nearly a year). I updated the package to the latest upstream version, did some general cleanup around 6 weeks ago, and contacted the Debian Python Modules Team, and the maintainer to inquire about uploading the package. The package can be found here: https://anonscm.debian.org/cgit/python-modules/packages/python-django-feincms.git/ I am yet to receive a response, so this is a more general request to update this package. Please note that the team policy is to contact the maintainer before uploading to get their approval, which has not happened yet. Thanks, Chris signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- control: tags -1 patch control: tags -1 pending Hi, uploaded the fix on deferred/5, please let me know if I have to cancel it or speed it up. I also tagged it and pushed the tag on git. thanks for your contribution to Debian! cheers, Gianfranco Il Sabato 16 Aprile 2016 21:15, Christopher Baines ha scritto: On 13/04/16 18:22, Gianfranco Costamagna wrote: > control: owner -1 ! > control: tags -1 moreinfo > > Hi Chris > >> I am looking for a sponsor to update the python-django-feincms package. >> The package has 3 RC bugs, the earliest dating back to June 2014 (nearly >> a year). >> > > before uploading I have some issues to raise. > > first python-django-tagging needs to be fixed. I see the fix is already on > git (you > did the import), so with this mail I'm contacting both maintainers to see if > they > want to upload it. I've now filed #821220 against sponsorship-requests for python-django-tagging. > Well, there is also a new changelog entry about fixing VCS fields, you should > really merge in the previous one, since it never hit unstable. Done. > that said, please fix before the tagging package, and then we will look at > this one > > https://launchpadlibrarian.net/165738145/python-django-feincms_1.7.4-1_1.7.4-1ubuntu1.diff.gz > what about this patch? I removed the patched line in this commit [1], with the reasoning that after the update to the new version, the file for which the permissions are being changed, no longer exists. 1: https://anonscm.debian.org/cgit/python-modules/packages/python-django-feincms.git/commit/?id=835fc3c05636254d546e8ea99fd8d8a6692f2038 > please note: I didn't do a full review, lets wait some time for maintainers > to react, and > then I'll be happy to sponsor the packages in the correct order (-tagging and > then -feincms). Great, thanks :)--- End Message ---
Bug#822524: marked as done (RFS: bliss/0.73-1 [ITA] - library to compute graph automorphisms and labelings)
Your message dated Wed, 27 Apr 2016 19:50:51 + with message-id <5721181b.5030...@rezozer.net> and subject line RFS: bliss/0.73-1 [ITA] - library to compute graph automorphisms and labelings has caused the Debian Bug report #822524, regarding RFS: bliss/0.73-1 [ITA] - library to compute graph automorphisms and labelings to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 822524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear Sponsor, I am looking for a sponsor for the Debian package bliss [1]. This package version brings to Debian the latest release and refresh the Debian material. Thanks in advance, Jerome [1] https://anonscm.debian.org/cgit/debian-science/packages/bliss.git/ -- System Information: Debian Release: Jessie* APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.7-ckt20-0001-mbp62 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) --- End Message --- --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Thanks to Andreas Tille, Jerome -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJXIRgbAAoJEIC/w4IMSybj5b8H/RDgQ+mYSTVySaFsYICDRvsa wFi0FVdHV9ffx95QvQfQbWw92zh0kYXkMIi2fcOF+DyXZNhrnUW/SuRsxVcbOMY5 igFCDkkfazwMQ1IJgZPyQuZGotcJr66oH4OdCZInM6QJ1GKiEGCjsQxwgqc6ZNfB CuopRl4sls0DO07QQJzGT5q8gFmMqNO0Ga3lU30n8izLyXdXbtEMFz8TPwSoe4Nj /L3++AOifrR2GJUok9Ic+FnXtlUC2zSiZaFjRH3pykZBW3ywKXd0uv2wsTDhKRHS fc8JFkslSTh14Ra9nh/Z61GQHy2+ST1LvPklpmEk+8k8YfXn+SoNVjZ+q1+fpUs= =n9gp -END PGP SIGNATURE End Message ---
Re: scantailor maintainership and alioth
On Wed, Apr 27, 2016 at 06:39:11PM +0800, Paul Wise wrote: > > On Wed, Apr 27, 2016 at 4:28 PM, Jason Crain wrote: > > > I have a question about Alioth though. The debian package is being > > maintained at (http://anonscm.debian.org/cgit/collab-maint/scantailor.git). > > Can I get access to that, or do I need to upload this to github instead > > and change the Vcs fields in the debian/control file correspondingly? > > You can get access, see here: > > https://wiki.debian.org/Alioth/Git#Collab_Maint_project > https://wiki.debian.org/Alioth/PackagingProject > https://lists.debian.org/debian-devel-announce/2015/02/msg1.html Sounds like I'll need a DM or DD to email a signed request before I can get access. I suppose I'll keep the Vcs fields pointing to Alioth, ask for an advocate when it's ready, and upload the project to github so they can review it. Daniel: would you, as the current maintainer, be willing to advocate Alioth access for me?
Re: request more advice: lintian warnings and python-tldp + ldp-docbook-stylesheets
Hello and greetings again Gianfranco, No problem at all. I wandered around a bit, have made a mistake or two, improved my package (I think), filed an RFS (in the wrong way [0]), and of course the ITP [1], but have started to get a feel for how the whole process is supposed to work. >just the changelog and control file (Source section) the binary is >good called python-tldp OK, great. I called it python3-tldp, given that the preferred Python support these days for Debian is Python3 (and I'm following tox and other examples). My package builds and tests against Python2, but I don't plan on bothering to release that for Debian, unless somebody asserts that it is a good idea. [I share this for others who may benefit, though, this stuff probably gets reposted often.] Since list week, I have learned that: * I should build my package against Debian 'sid' before submitting for RFS. * There are two manuals for packagers 'Debian New Maintainers' Guide' [2] and the 'Guide for Debian Maintainers'. * There's something called 'http://mentors.debian.net/'. I still don't know what to do with that, so I'll stay on the mailing list for now. * Though it is possible to generate a '3.0 (native)' package. When running 'lintian --pedantic', I read this: https://lintian.debian.org/tags/library-package-name-for-application.html I created debian/python3-tldp.lintian-overrides with this as the sole contents. (It seems I'm in good company, since there are 719 packages there.) So, skipping the "N:" lines, when I run 'debuild', I end up with: P: tldp source: debian-watch-may-check-gpg-signature O: python3-tldp: library-package-name-for-application usr/bin/ldptool I do not know how to add a GPG signature to the tagged release within the git history or via github.com, although I'd imagine it's possible, So, I'll try to learn that at some point. But, I'm hoping that is not a killer, since, as the upstream AND packager, I can sign the Debian package with my (new) 4096-bit RSA key (Mattia Rizzolo recommend this new key). >but I guess you need to have the orig tarball in the parent >directory. dpkg-buildpackage will compare the sources, and bother >you against adding patches in case the source trees differs from >the pristine tarball. Yes, I see that. And, I see that I have to always do this for a Debian release. >so, download the source tarball, call it >tldp_version.orig.tar.whatever (I always dpkg-buildpackage, wait >for the failure, and then copy-paste the name dpkg is expecting) I switched from debian/source/format: 3.0 (native) to 3.0 (quilt). I have a new possible release. My RSA key is available: gpg --recv-keys 0x329BC377 # --keyserver pgp.mit.edu fingerprint = 4F7F DCD6 241F CFC9 9BCE BF11 8CA4 3A8D 329B C377 Here's the revised package: dget -x http://linux-ip.net/debian.ITP-822181/tldp_0.7.10-1.dsc N.B. My key does not exist on the stock /usr/share/keyrings/debian-keyring.gpg, so, for me, dscverify complains that no public key is available. Running 'gpg --verify tldp_0.7.10-1.dsc' succeeds, however. Lastly, the newest tag (tldp-0.7.10) is available at the canonical location [4] with the subsequent changes to the ./debian/ directory to handle the packaging. What do I do next? -Martin [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822722 # RFS [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822181 # ITP [2] https://www.debian.org/doc/manuals/maint-guide/ https://www.debian.org/doc/manuals/maint-guide/maint-guide.en.pdf [3] https://www.debian.org/doc/manuals/debmake-doc/ https://www.debian.org/doc/manuals/debmake-doc/debmake-doc.en.pdf [4] http://github.com/tLDP/python-tldp.git -- Martin A. Brown http://linux-ip.net/
Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers
On Wed, Apr 27, 2016 at 05:27:37AM +0200, Adam Borowski wrote: > I'm afraid that it builds only on 64-bit architectures (I tried amd64 and > arm64), on 32-bit ones (x32 armhf i386) it fails with: > > [...] > > Also, it'd be nice if you added --parallel to the dh call, it massively > speeds up builds[1] on any non-museal machine. It's default in upcoming > debhelper 10. Both issues are fixed now. Here are the new build logs for - amd64: https://bitbucket.org/snippets/f-w/G6pBB - armhf: https://bitbucket.org/snippets/f-w/o6g5d I've reuploaded the fixed package to Mentors. Cheers, Fabian
Bug#822728: marked as done (RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers)
Your message dated Thu, 28 Apr 2016 03:08:09 +0200 with message-id <20160428010809.ga15...@angband.pl> and subject line Re: Bug#822728: RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers has caused the Debian Bug report #822728, regarding RFS: libtcod/1.6.0~pre1+dfsg-1 [ITP] -- graphics and utility library for roguelike developers to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 822728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "libtcod" * Package name: libtcod Version : 1.6.0~pre1+dfsg-1 Upstream Author : Richard Tew * URL : https://bitbucket.org/libtcod/libtcod * License : BSD-3-clause Section : libs It builds those binary packages: libtcod-dev - development files for the libtcod roguelike library libtcod0 - graphics and utility library for roguelike developers The build log for amd64 is available here: https://bitbucket.org/snippets/f-w/yKoK4 To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libtcod Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libt/libtcod/libtcod_1.6.0~pre1+dfsg-1.dsc More information about libtcod can be obtained from https://bitbucket.org/libtcod/libtcod Changes since the last upload: * Initial release. Closes: #704587 Regards, Fabian Wolff --- End Message --- --- Begin Message --- On Thu, Apr 28, 2016 at 12:23:32AM +0200, Fabian Wolff wrote: > On Wed, Apr 27, 2016 at 05:27:37AM +0200, Adam Borowski wrote: > > I'm afraid that it builds only on 64-bit architectures (I tried amd64 and > > arm64), on 32-bit ones (x32 armhf i386) it fails with: > > > > Also, it'd be nice if you added --parallel to the dh call, it massively > > speeds up builds[1] on any non-museal machine. It's default in upcoming > > debhelper 10. > > Both issues are fixed now. > I've reuploaded the fixed package to Mentors. Looks good, uploaded. It'd be nice to install the upstream changelog, but as the one in -pre1 looks useless, I uploaded without it. The current version has a detailed list of changes up to 1.5.2, then nothing but a placeholder for 1.6, and that's the only entry that's of real interest for readers. -- A tit a day keeps the vet away.--- End Message ---
